Borough Builder · Your Church Assistant
One permission-aware record for people, giving, events, communications, civic context, and the documents behind every decision — for the staff who keep the place and the members who call it home.
Managed pilot · Web, iPhone, and iPad experiences · Public store release pending
The staff console, captured from the current pilot build with demonstration church data.
Stop one · Who it's for
Tell the page who you are and every path on it points to the right door. Nothing is hidden — your part just steps forward.
Bring staff operations and the member experience onto one shared record, with role-based access throughout.
Use Civic, trusted business referrals, private connections, and Circles before your church is on Borough Builder.
Coordinate with eligible churches across licensed states without taking over a congregation's voice.
Stop two · The assistant
The assistant searches permitted records, summarizes, reports, and drafts. Permissions are applied before anything is retrieved, so a volunteer coordinator and a pastor asking the same question get different, correct answers.
Changes are applied only after a person reviews and confirms them. People stay responsible for anything that goes out or moves money.
Scripted demonstration with sample church data — no live AI runs on this page. Roles shown are one example setup; churches define their own.
Who are our highest recorded givers this year?
Here are this year's highest recorded givers, grouped by household, with the funds each gift was directed to. I can prepare this as a report for the treasurer to review, or narrow it to one fund.
Giving · fund ledgerHouseholds
Searches, summarizes, reports, drafts.Changes and sends wait for a person.
Inside the product
Real screens from the current staff console, shown with demonstration church data. Pick a screen.
Available records and actions vary by role, organization, and connected providers.
One record, all week
Borough Builder connects operational records instead of turning every ministry into a separate app and a separate export. Scroll the week and watch one person's story assemble.
No paper card, no re-typing. The card lands on the record with a timestamp and where it came from.
Whoever owns visitor follow-up sees it, tied to the household it belongs to.
Borough Builder takes no platform percentage. Stripe's normal processing charges still apply.
Volunteer slots, events, and communications stay tied to the people doing the work.
The answer cites the card, the follow-up, the gift, and the team — because they were never in four different apps. Try the question →
Stop three · Giving
Giving runs through your church's own connected Stripe account. Donors can direct a gift to a fund and give once or on a schedule. We don't take a platform percentage; the processor's normal fee is the only deduction, and it's Stripe's, not ours.
Stop four · The member app
The pilot member app carries the same record into the week: the assistant, giving, the schedule, and what's happening in the state. Real captures; store release pending.
Pilot member-app captures with demonstration church data.
Stop five · From one believer to a church
An Individual account is not a dead end — it is the on-ramp. The same record you start alone becomes the seed of a congregation.
Civic context, trusted Commerce referrals, and private connections for one believer — no church required yet.
Invite believers near you into a private Circle while the gathering is still a living room and a shared meal.
Move into the church-plant workspace with the full staff console and member experience from day one.
People, records, and giving history carry over. Your Individual subscription ends when you join a church account.
Circle coordination and assisted account transfer are part of the current Individual pilot; public enrollment remains waitlisted.
Stop six · Security
The product is designed around church authority, scoped access, and human decisions rather than autonomous action.
Server-side authorization and database row policies keep ordinary church records inside the signed-in organization.
Assistant retrieval applies the user's permissions before records are queried or included in an answer.
Assistance can search, summarize, report, and draft. Staff review external communications and users confirm financial actions.
Care and discipline documents use narrower access rules, are excluded from AI surfaces, and retain access history.
Illustrative roles. Each church configures its own; care and discipline records keep narrower rules for everyone.
Security is an ongoing operating practice, not a badge. Pilot customers should review their role setup, connected providers, and data-handling requirements during onboarding.
Stop seven · Nonprofits
Statewide coordination is built as a church-controlled layer. Verified nonprofits can publish events, prepare staff messages, and sponsor petitions while each church decides what its people see and share.
Join the nonprofit waitlistNonprofit messages reach church staff, never members directly. Each church controls its feed, mute settings, and what it shares.
Publish timely events to eligible churches in licensed states, with source organization and date details intact.
Send accountable staff-only messages with inspected PDF attachments. Churches retain inbox controls and mute settings.
Fund and publish petitions with transparent sponsorship, verified state eligibility, and auditable support.
A village still being built
Pilots run on trust, so this page volunteers what is ready and what is not.
No published price funnel, checkout, or automated sales sequence. How pricing works →
Stop eight · The waitlist
Every path starts with a short questionnaire, read by a real person. No published price, checkout, or automated sales funnel.
For established congregations, church plants, and church networks evaluating the staff console and member app.
Join the church waitlistFor people starting on their own, joining trusted connections, or gathering a Circle that may grow into a church.
Join the Individual waitlistFor verified organizations coordinating statewide events, staff messages, and petition campaigns with churches.
Join the nonprofit waitlistEach path opens a five-question form. The confirmation screen appears only after your request is safely stored.
Things travellers ask
The staff console, API, and a pilot member app build are being used and refined through managed pilots. Public app-store distribution and open Individual enrollment are not available yet.
No. The platform percentage is 0%. Giving is routed through the church's connected Stripe account, and Stripe's normal processing charges still apply.
Choose the church, Individual, or nonprofit path on this page. Complete the short questionnaire; the site confirms that your request was saved and its notification accepted for delivery.
It can search permitted records, summarize, report, and prepare drafts. Permissions are applied before retrieval, and people remain responsible for external communications and financial actions.
No. Some provider workflows require operator credentials and church configuration. Pilot onboarding confirms the exact providers available before making a migration promise.
No. Nonprofit messages are delivered to eligible church staff. Each church controls its statewide feed, mute settings, and what it chooses to share with members.
Public and signed-in surfaces are separate. Internal records require authentication and appropriate organization access; staff permissions further narrow sensitive operations and records.
Managed pilot onboarding