labs@atheron:~/industries/faith-community/apps$ build app --web --mobile

Software for congregations

Giving, rooms, rotas and outreach in one place.

A community's software has to be simple enough for a volunteer to run on a Sunday, a Friday or a festival day, and sturdy enough to keep going when that volunteer moves on. We build small systems with clear roles, plain screens and records that stay private.

Start a project See the example projects

// what matters here

What is different in this industry.

Built for volunteers

Screens a new volunteer can use after five minutes, with the coordinator able to change rotas and rooms without calling us.

Private by default

Members and families are seen only by the roles that need them, and every export is logged.

In your members' languages

Screens, reminders and messages in two or more languages, with translations your community supplies or approves.

Neutral across faiths

We build tools for the work, not the belief. Nothing in the software speaks for your tradition.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb app

Online giving with receipts

Hypothetical. Not a client, not a result.

// The problem

A congregation takes gifts by cash, cheque, e-transfer and card, and its volunteer treasurer spends weeks each winter matching them to donors and typing receipts.

// What we would build

A giving page and donor accounts with card and recurring gifts through Stripe, cash and cheque entry for counters after each service, year-end receipts generated in the format your treasurer and advisers approve, and gift totals posted to QuickBooks Online, built on its API. We build to the receipt rules your advisers set; we give no tax advice.

// What is in it

A giving page with one-off and recurring gifts by card
Cash and cheque entry for the counting team, with two people signing off
Donor accounts where members see their own gifts and update their details
Year-end receipts generated from the records, in the format your treasurer approves
Gift totals by fund posted to QuickBooks Online

// Stack

Next.js
PostgreSQL
Stripe
QuickBooks Online API
DigitalOcean Toronto

// estimate

Build: ≈ US$72,500 to US$111,000, delivered within 21 weeksCAD 103,200 to 157,700
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$1,000 a monthCAD 1,425 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Data mapping and sandbox connection: 0.4 weeks
Design approved: 2.4 to 3.4 weeks
Receipt format approved by your treasurer: 1.4 to 1.9 weeks
Core features: 1.9 to 2.9 weeks
Full build: 1.4 to 1.9 weeks
Sync built and reconciled in sandbox: 1.4 to 2.4 weeks
Testing and fixes: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks
Live cutover: 0.9 to 1.4 weeks
Hypercare: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

Payment processor account in your organisation's name: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 20,640 to 31,540
Discovery 4.5%: CAD 4,644.00 to 7,096.50
Data mapping and sandbox connection 3.4%: CAD 3,508.80 to 5,361.80
Design approved 4.5%: CAD 4,644.00 to 7,096.50
Receipt format approved by your treasurer 8.7%: CAD 8,978.40 to 13,719.90
Core features 13.5%: CAD 13,932.00 to 21,289.50
Full build 9%: CAD 9,288 to 14,193
Sync built and reconciled in sandbox 10.2%: CAD 10,526.40 to 16,085.40
Testing and fixes 4.5%: CAD 4,644.00 to 7,096.50
Launch 4.5%: CAD 4,644.00 to 7,096.50
Live cutover 3.4%: CAD 3,508.80 to 5,361.80
Hypercare 3.8%: CAD 3,921.60 to 5,992.60
Holdback, 30 days after launch (10%): CAD 10,320 to 15,770

Start from this example

Example projectWeb appBot with a web dashboard

Rooms and volunteer rotas

Hypothetical. Not a client, not a result.

// The problem

A temple books its halls and kitchen by text message, and volunteer shifts for festivals and weekly meals are filled from a group chat that nobody can search.

// What we would build

A booking calendar for rooms and equipment with approval by the office, volunteer rotas people sign up to themselves, and a Telegram bot that sends shift reminders and lets volunteers swap shifts, in the languages your members use.

// What is in it

Rooms, kitchens and equipment booked on one calendar, with approval
Volunteer rotas for weekly programmes and festivals
Self sign-up and shift swaps, with the coordinator told
A Telegram bot for reminders and swaps
Messages in two or more languages

// Stack

Next.js
PostgreSQL
Telegram Bot API
DigitalOcean Toronto

// estimate

Build: ≈ US$46,100 to US$70,600, delivered within 16 weeksCAD 65,700 to 100,600
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$1,000 a monthCAD 1,425 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Commands agreed: 0.4 weeks
Design approved: 2.4 to 4.4 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.9 weeks
Working in a test server: 0.9 to 1.4 weeks
Testing and fixes: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

How it is paid

Deposit 30%: CAD 19,710 to 30,180
Discovery 5%: CAD 3,285 to 5,030
Commands agreed 3.5%: CAD 2,299.50 to 3,521.00
Design approved 5%: CAD 3,285 to 5,030
Core features 15.2%: CAD 9,986.40 to 15,291.20
Full build 10.1%: CAD 6,635.70 to 10,160.60
Working in a test server 7.1%: CAD 4,664.70 to 7,142.60
Testing and fixes 5%: CAD 3,285 to 5,030
Launch 9.1%: CAD 5,978.70 to 9,154.60
Holdback, 30 days after launch (10%): CAD 6,570 to 10,060

Start from this example

Example projectWeb appMobile app

Outreach and food bank records

Hypothetical. Not a client, not a result.

// The problem

A gurdwara's food bank and outreach programmes record visits on paper sign-in sheets, and the volunteers rebuild the numbers by hand for every funder report.

// What we would build

A tablet app for intake and visits that asks only what you need, inventory for donated food, and a dashboard that turns the records into the figures your funders ask for, with personal details kept private and out of every report.

// What is in it

Intake and visits on an Android tablet, in the languages your volunteers speak
Only the questions you choose, with consent recorded
Donated food received, stored and given out
A dashboard of visits and programmes for funder reports, with no names in it
Exports in the formats your funders ask for

// Stack

Next.js
Kotlin for Android
PostgreSQL
Metabase
DigitalOcean Toronto

// estimate

Build: ≈ US$79,600 to US$122,000, delivered within 27 weeksCAD 113,400 to 173,500
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 4 to 5 weeks
Design approved: 5 to 8 weeks
Core features: 2 to 3.5 weeks
Full build: 1.5 to 3 weeks
First build on devices: 3.5 to 5.5 weeks
Testing and fixes: 1 to 1.5 weeks
Store submission: 1.5 to 2 weeks
Launch: 1.5 to 2 weeks

Outside our hands, and added to the calendar

App store review: 1 week

How it is paid

Deposit 20%: CAD 22,680 to 34,700
Discovery 9.1%: CAD 10,319.40 to 15,788.50
Design approved 9.1%: CAD 10,319.40 to 15,788.50
Core features 9.2%: CAD 10,432.80 to 15,962.00
Full build 6.1%: CAD 6,917.40 to 10,583.50
First build on devices 18%: CAD 20,412 to 31,230
Testing and fixes 3%: CAD 3,402 to 5,205
Store submission 6%: CAD 6,804 to 10,410
Launch 9.5%: CAD 10,773.00 to 16,482.50
Holdback, 30 days after launch (10%): CAD 11,340 to 17,350

Start from this example

// questions

Questions we get about this.

Can volunteers use it on their own phones?

Yes. Rotas, sign-ups and reminders work in a phone's browser and through a Telegram bot, with no app to install.

Who in our community can see member records?

Only the roles you choose. Group leaders see their group, the office sees what it needs, and every change is logged.

Can it run on a small budget?

Usually, by starting with one part, such as giving or rooms, and adding the rest later. The estimator shows what each part costs.

Back to the industry: Faith and community organisations About the service: Web and mobile apps

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call