Borough Builder
One permission-aware assistant for people, giving, events, communications, civic life, and the documents behind every decision.
Managed pilot · Web, iPhone, and iPad experiences · Public store release pending
Real product captures with demonstration church data.
Three client layers
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.
The pathway
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.
Inside the product
Real screens from the current product, shown with demonstration church data.
Available records and actions vary by role, organization, and connected providers.
A connected operating system
Borough Builder connects operational records instead of turning every ministry into a separate app and a separate export.
People, households, membership stages, classes, groups, interactions, and follow-up tasks share one history.
Events, volunteer slots, communications, goals, and staff dashboards stay tied to the people doing the work.
Giving uses the church's connected Stripe account. Borough Builder charges no platform percentage; normal processor fees still apply.
Civic analysis, cited Vault answers, Commerce referrals, and church-to-church workflows preserve source and access context.
Enterprise trust
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.
Security is an ongoing operating practice, not a badge. Pilot customers should review their role setup, connected providers, and data-handling requirements during onboarding.
For verified 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 waitlistPublish 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.
Early access
Every path starts with a short questionnaire stored securely for Matt's review. 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.
Questions
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 above. 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