adl.church

Church discovery, CRM, and planting strategy

Church Intelligence For South Australia

Build the map, the CRM, and the strategy layer together.

adl.church is set up to become a serious operating system for church discovery and planting strategy, not just a static directory. The repo now has a working app shell, Cloudflare deployment path, and Supabase-ready foundation.

Searchable public directory

Search by suburb, denomination, affiliation, ministry mix, church age, service pattern, and planting history.

Research-grade CRM

Track source-backed assertions, claim requests, follow-up tasks, confidence, and internal notes without mixing them into the public experience.

Permission-aware AI

Let pastors and leaders bring their own OpenAI, Anthropic, or Google AI keys and reason over the records they are allowed to see.

Strategic Filters

Built For Real Planning Work

Identity and structure

6 filters

Model denomination, organisation type, multi-site structure, and family-of-churches relationships cleanly.

DenominationTradition familyOrganisation kindMulti-site church

Networks and affiliations

6 filters

Surface presbyteries, dioceses, Acts 29, funders, training bodies, and other strategic ecosystems.

Acts 29Spark-funded plantsGenerate PresbyteryNetwork membership

Gatherings and accessibility

6 filters

Make it easy to discover where and when churches actually gather, including evening options and language diversity.

Evening gatheringAM gatheringWeeknight gatheringLanguage offered

Age and planting history

6 filters

Track age basis carefully so users can search for church plants under 2, 5, 10, or 25 years with confidence.

Under 2 years oldUnder 5 years oldUnder 10 years oldUnder 25 years old

Current Build Sequence

What Happens Next

  1. 1

    Bootstrap the app shell, environment model, and Cloudflare deployment path.

  2. 2

    Connect Supabase auth, schema, and the first live explore queries.

  3. 3

    Import legacy Adelaide church data into staging and promote verified records.

  4. 4

    Ship map clustering, saved segments, and denomination-by-denomination curation flows.