Case study · Church governance · New Zealand

Good Church: from MVP to public sign-up in about four weeks

Good Church, a New Zealand church-governance start-up, now lets any church sign up and ask its own policies questions in plain English, with the clause cited, after we took its AI advisor from a single-user MVP to a multi-tenant platform in about four weeks.

Good Church's public worked example: "Do two adults need to be present at every youth event?" answered from a Child Protection Policy, with section 4.2 cited
Client
Good Church Ltd
Industry
Church governance and compliance
Location
New Zealand
What we did
Phase 2 platform build, hosting and ongoing development

In numbers

  • ~4 wksfrom developer handover to public sign-up
  • 350+automated tests behind the platform
  • 3official sources checked monthly for law changes

The short version

  • Good Church had a working MVP that answered governance questions, but only for one user and without each church's own documents.
  • We turned it into a platform any New Zealand church can sign up to, with walled-off documents, role-aware cited answers, law-change monitoring and safeguarding alerts.
  • Public sign-up went live in July 2026, about four weeks after handover, backed by more than 350 automated tests.

The problem

A working MVP that could not hold each church's own documents

Clare Pattison and Dan Cooper started Good Church in late 2025 to get what a church board has already decided into its people's hands, fast.

They had a working MVP from another developer. It answered questions against shared church-sector content, for a single user, with no way for a church to upload its own policies.

Phase 2 had to turn it into a product any church can sign up to, with its own walled-off documents, safeguarding alerts, law-change monitoring and billing.

The solution

Churches now sign themselves up and bring their own policies

From handover to public sign-up in about four weeks, in July 2026.

Good Church sign-up form with a "Find your church" field that searches the Charities Register by name
Sign-up

Churches sign themselves up

Find your church on the Charities Register, upload your own documents and approve your own team.

Good Church FAQ: "Is my church's data isolated?" - every church's documents, questions and members are scoped to that church at the database level
Platform

Walled off, and billed per church

Row-level security in Postgres keeps each church's data separate. Stripe plans are capped by how many people log in.

Good Church feature card: "Stay ahead of law changes", with recommended wording ready for the board to review and approve
Compliance

Law changes, drafted for approval

Monthly checks of legislation.govt.nz, WorkSafe and the Privacy Commissioner. Claude drafts wording per church size, and an admin approves it.

Backed by more than 350 automated tests.

Every answer comes from that church's own policies, clause cited

The answering pipeline came with the MVP. We tuned answers to the asker's role and turned its safeguarding flags into alerts a leader reviews.

  1. Someone asksA board member, leader or volunteer, in plain English
  2. Search their own documentsHybrid search finds the right clause in that church's policies only
  3. Claude answers, clause citedPitched to the asker's role, from governance depth to practical steps
  4. A leader follows upCare, protection or safety questions email the church's safeguarding contacts

The rule for every AI feature: stay inside the documents the board has signed off, and keep a person in the loop where it matters.

The result

Any New Zealand church can sign up and get cited answers today

  • Public sign-up has been live at goodchurch.co.nz since July 2026.
  • Each church's documents, questions and members are walled off at the database level.
  • Answers cite the clause they came from, pitched to the person asking.
  • Care, protection and safety questions reach the church's safeguarding contacts by email.
  • Law changes arrive as drafted wording for an admin to approve, not as a surprise.
The Good Church home page: "Your decisions. In seconds." with a sign-up button
The public site at goodchurch.co.nz, built in Phase 2.

Answers are only as good as the documents behind them

In September we reworked how uploaded documents are split into sections, so long constitutions and manuals break into their clauses and questions reach the right policy.

Draft documents now stay out of answers until the church marks them as adopted. Next is tuning the few longest sections so they retrieve even more precisely.

Questions people ask

How long did the Good Church build take?

About four weeks from developer handover to public sign-up, in July 2026. We have hosted and kept developing the platform since.

What did the Good Church team have to do?

Clare and Dan set the priorities, reviewed each piece as it landed and supplied the domain records for go-live. Good Church owns its own Stripe account, AI provider account and code repository, so the product stays theirs.

Is each church's data kept separate and safe?

Yes. Every church's documents, questions and members are scoped to that church at the database level. The AI answers only from documents the board has signed off, and safeguarding flags go to a person, not an automated reply.

How do we start something similar?

Get in touch with the documents your people ask about most. We scope a first version around them, have it answer only from your own material, and keep a person in the loop wherever it matters.

More case studies

Got a document-heavy compliance problem?

Policies, procedures and legislation that keeps moving. If your people need fast answers from your own documents, we can build it, host it and keep it running.

Last updated 29 September 2026