Case study: East Tennessee District

The first district running on Naz.tools — and the one we built it with.

The starting point

Like most districts, ETNDI ran its operations on a stack of separate tools that never quite talked to each other. Camp registrations went through a generic event platform. Waivers were paper, then PDFs, then sometimes lost. Payments to the right ministry treasury required manual reconciliation. Monthly attendance numbers came in by email, into a spreadsheet, with someone chasing down the late churches by phone. The district leadership page on the website showed two-year-old photos of three former committee members.

None of those tools were bad in isolation. The cost was the seams between them.

What changed

Naz.tools replaced the seams with one suite. ETNDI now runs on four integrated components that share one source of truth for churches and people:

One household can register a family of five for Family Camp, sign waivers for the children, pay the correct auxiliary account, and check in via QR code when they arrive at Foothill — all from one login, against the same church record their pastor uses to file the monthly attendance report.

“Placeholder for a real quote from an East Tennessee District leader. We'll add this with permission before the site goes fully public — likely from a District Superintendent, a treasurer, or a camp director who has used the system end-to-end.” — Pending approval

What's running today

What we learned (that informs the product for everyone else)

If you're a similar district

If your district runs camps or family events, has more than one ministry that needs its own treasury, or has gotten burned by a missing waiver — the shape of the problem is the shape we've already solved here.

Request beta access