TR-2522 guided demo path

Request a demo

Use this path when your church wants guided evaluation, migration context review, or stakeholder alignment before going deeper.

A real Spanish demo page is now available for this route. Open Spanish demo page →

Choose this path when

  • Best when multiple leaders need the same orientation early.
  • Useful when migration complexity or internal timing needs discussion first.
  • Still separate from a hidden sales-only pricing process.

What happens next

  • You submit a lightweight structured request instead of a catch-all contact form.
  • Transparent returns a routing preview for guided follow-up.
  • Later tranches should connect this path to lightweight follow-up and scheduling behavior.

Structured intake

Request a demo

Use this path when your church wants guided evaluation, migration context review, or stakeholder alignment before trialing deeply. The intake stays lightweight and routes into a structured demo case preview.

Keep payment, identity, and other sensitive detail out of broad free text unless the form explicitly calls for it.

Open help center

What happens next: this flow should connect to a lightweight follow-up and scheduling path in the next tranche. If you want grounded orientation first, use the help center.

Current bilingual launch posture

The current public launch shell is English-first. Spanish parity remains an explicit review and implementation task for trust-sensitive surfaces, so no Spanish path should be implied equivalent until it is rechecked and landed.

  • Current live launch shell content is English-first.
  • Spanish parity is still in progress for trust-sensitive launch surfaces.
  • Do not imply equivalent EN/ES launch readiness until the specific surface is re-reviewed and landed.

Still want to explore on your own first?

Requesting a demo should be optional, not a gate to understanding pricing or fit.

If your team decides you would rather begin hands on, the self-serve trial path remains available. Guided demo and self-serve should both stay serious, honest evaluation routes.

Switch to self-serve trial path →

Need active support instead of evaluation help?

Sales/demo routing should stay separate from support, billing, and hardship intake.

If your real need is troubleshooting, a bug report, billing follow-up, or a hardship request, use the structured support intake so the case routes to the right lane with the right visibility.

Open structured support intake →