Guidepost

Contact us

Tell us how your organization is structured.

That is genuinely the most useful thing you can lead with. The hierarchy is the part of Guidepost most worth testing against reality, and it shapes everything we would show you.

Send a message

Get in touch

Everything except your name and email is optional — but the more you tell us, the less generic our reply will be.

If your environment has constraints we should know about — a closed network, an accreditation requirement, a records-retention policy — mention them here and we will address them directly rather than generally.

Email us directly

Prefer email?

info@guidepost-lms.com

The form and this address reach the same place. Use whichever suits how your organization handles correspondence.

What to expect

A reply from a person

We answer the question you actually asked, in your own terms — not with a brochure and a calendar link. If your question is technical, the answer will be technical.

If we do not think Guidepost is the right fit for what you have described, we will say so rather than book a call to find out slowly.

Available on request

Evaluation materials

  • A detailed feature walkthrough
  • Technical documentation and architecture overview
  • A full deployment and security handoff guide
  • Answers to the specific questions your review process raises

Tell us what your evaluation needs to cover and we will send what matches it, rather than everything.

How this usually goes

From a first message to a pilot.

Nothing here is a commitment. Each step exists so the next one is worth taking.

  1. You tell us how you're structured

    Divisions and departments, roughly how many courses, whether training is in-person, online or both, and how it is administered today. A paragraph is plenty.

  2. We reply with something specific

    An answer to what you asked, plus an honest read on whether the parts of Guidepost you would actually rely on are the parts it does well.

  3. A walkthrough against your shape

    Pointed at the hierarchy you described and the roles your people actually hold — not a generic tour of a demonstration dataset arranged to look tidy.

  1. Documentation for your review

    Technical overview, deployment and security handoff guide, and direct answers to whatever your procurement or accreditation process raises.

  2. A scoped pilot in your environment

    A defined pilot on your own infrastructure, with a real course and real staff. The organizational hierarchy is the part most worth testing against reality, and a sandbox nobody has a stake in tests it least.

  3. Deployment and handoff

    Guidepost is administered by your institution, not by us. The handoff guide exists so that is genuinely true rather than nominally true.

A note on closed environments. If your training network has no route to the public internet, say so early. It changes nothing about whether Guidepost will work — closed and air-gapped networks are the design target — but it does change what a pilot looks like logistically, and that is worth planning rather than discovering.

Before you write

The FAQ may already answer it.

Structure and roles, the student experience, authoring, deployment and security — the questions we get most often are answered there in full.

Read the FAQ Browse the features