Standalone product boundary, not folded into another app
Structured to stay simple, reviewable, and compatible with the launch planning set.
Transparent church management software
Church software with clearer pricing, calmer migration, and support you can trust.
Transparent is being built to give churches a modern system without vague commitments, pressure-heavy sales patterns, or confusing migration promises.
Launch-scope homepage contract
- Month-to-month launch posture
- Two-month free trial
- Active-people pricing explanation
- Migration-aware and bilingual launch planning
This slice keeps the first public shell honest while the deeper product build catches up.
Built around high-trust product boundaries
The first public shell stays conservative. It reflects the launch contracts for pricing clarity, tenant separation, support boundaries, and practical AI assistance without claiming unfinished product depth.
Next.js public shell aligned to a web-first launch
Structured to stay simple, reviewable, and compatible with the launch planning set.
Support, billing, and admin surfaces kept intentionally separate
Structured to stay simple, reviewable, and compatible with the launch planning set.
Pricing clarity comes before pricing theatrics
Transparent launch pricing is monthly, starts with a two-month free trial, and scales by active people. We are keeping the structure simple so churches can understand what changes, when it changes, and why.
What churches should understand fast
- Pricing is shaped by active people, not hidden feature traps.
- The trial stays visible and bounded.
- Support and demo help remain available without forcing a sales gauntlet.
What this tranche does not claim yet
- No fake pricing numbers before final publication.
- No implied billing automation beyond the launch contracts.
- No inflated trust claims that outrun the actual product build.
Migration should feel realistic, not hand-waved
Transparent is being shaped for churches that need a careful move off older systems. Public messaging stays grounded, and guided help remains available when your migration questions are more complex than a self-serve walkthrough can cover.
Self-serve when it helps
Churches that want to evaluate quickly should be able to start without waiting on a salesperson.
Guided when it matters
Complex migration or stakeholder alignment needs should route cleanly into a demo and support path.
AI is support, not authority
Transparent can use AI to help with setup, documentation, and evaluation guidance. It should never pretend to make high-consequence church decisions on its own or silently replace canonical billing, record, or access truth.
Practical launch posture
Use AI to explain, guide, and surface answers. Do not let it quietly become the truth source for billing, record state, or permissions.
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.
FAQ
Address the main objections with calm, bounded answers.
Is Transparent already a finished product?
No. This first implementation slice creates the initial public shell and pricing structure. More product surfaces will land in later tranches.
Will we need a long contract to evaluate it?
Launch planning is built around a month-to-month posture with a two-month free trial, not hidden annual-lock-in assumptions.
Can we request human help before committing to a trial?
Yes. Requesting a demo is intended to remain a first-class path for churches that want guided evaluation or have more complex migration needs.
Start with the public launch surface, then add the deeper product flows deliberately.
The first build tranche focuses on a clean shell, honest pricing language, and clear next steps.
Want the first-run sequence before you start? Review the getting-started guide →