Questions, answered plainly

No, and we'd advise against it. Most churches start with one area — usually Finance — connect the systems they're keeping through Tara Connect, and consolidate more only when a Tara module genuinely replaces something they're paying for.

If one person keeps the books off the side of their desk, the Essentials plan is built for that — and it is a broad core rather than a stripped tier: finance, giving, people and a basic Ministry Hub are all included.

Multi-campus, multi-entity, restricted and designated funds, and consolidated reporting are all part of the model rather than add-ons. If you're a network or denomination, talk to us — roll-up needs vary enough that we'd rather scope with you than publish a guess.

It depends on what you're bringing and what you're keeping. The guided implementation exists precisely so that answer comes from a conversation about your actual systems rather than a number on a web page.

Tara Finance, Ask Tara, Tara Vault and Tara Connect are real software we demonstrate live — labelled Preview, meaning pre-general-availability. Giving, People, Ministry and Engage are designed and committed but not yet usable, and are labelled Coming Soon everywhere they appear.

No. Accounting connections are deliberately read-only: Tara reads your books and explains them, and never posts entries back. That's an architectural decision, not a limitation we're working around.

No. Ask Tara reads through the same permissions as the person asking, cites the records behind every answer, and cannot modify financial or sensitive data. AI proposes, governed systems determine, and humans approve anything consequential.

We don't publish a date. Giving is built and visible in the product, and deliberately not processing money until our payment-partner, privacy and receipting reviews are complete. We'd rather be late than move real donations through an unreviewed path.

No. We hold no security certifications today and we won't imply otherwise. The security page sets out what's in the product now — tenant isolation, deny-by-default permissions, audit logging, a payment-data boundary — and what's still ahead, including an independent penetration test that blocks our own launch.

Only people you grant access to. Permissions are deny-by-default and per-capability, so "finance" access doesn't imply donor access, and sensitive categories like pastoral notes are separately gated.

Yes. Full export of your organization's records is a commitment, not a setting we might add — it's on the security page as planned work with a gate attached, and it will be in place before any church's real data lands.

Giving processing is priced separately from your subscription, per transaction, when it goes live. We haven't finalized rates, so we don't publish them.

For a short while, realistically — that's true of any migration. Tara Connect exists to keep that window short and useful rather than wasted.