TTransparentLaunch public shell

TR-2522 self-serve trial path

Start free trial

Use this path when your church wants to begin a self-serve or migration-aware evaluation without entering a sales-first process.

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

Choose this path when

  • Best when your team wants to explore quickly and keep control of the pace.
  • Still supported if migration, setup, or documentation questions appear during evaluation.
  • Does not remove the option to request guided help later.

What happens next

  • You submit a short structured intake instead of an open-ended sales request.
  • Transparent returns a routing preview and next-step posture for evaluation.
  • Later tranches should connect this path to account start, setup guidance, and migration help.

Structured intake

Start free trial

Use this path to begin a self-serve or guided evaluation without changing the public pricing posture. The intake stays short, keeps sensitive details out of free text, and returns a structured onboarding 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 lead into account start, setup expectations, and migration guidance 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.

Need guided help without abandoning self-serve?

The launch posture should keep both routes first-class.

You can start here and still request grounded help later. Self-serve should not mean unsupported, and choosing guided help later should not reset the evaluation conversation.

Switch to guided demo path →

Want the first-run path before you submit?

The onboarding shell should explain what comes next without pretending everything is already automated.

If your team wants to see the recommended onboarding sequence first, review the getting-started guide. It explains trial posture, migration choices, support paths, and where explicit approval still matters.

Open getting-started guide →

Need a narrower route instead?

Trial intake should not absorb questions that belong in support, billing, or hardship lanes.

Pricing or billing question

Use the narrower billing route when the real issue is account-sensitive pricing or invoice context.

Open billing intake →

Hardship request

Use the hardship route when affordability is the real conversation and you want the calmer restricted path first.

Open hardship intake →

Blocked setup or product issue

Use structured support when the real need is troubleshooting, a bug report, or a routed support case.

Open support intake →