Skip to content
AtheronLABS

You're visiting from the United States. Prices are shown in US dollars. Not right?

labs@atheron:~/industries/faith-community$ gather --members --volunteers --giving

Community software

Less paperwork for the people who keep it running.

Your community runs on volunteers, a treasurer with a spreadsheet and a members list somebody built years ago. We build the small, sturdy systems that take the weekly admin off those people: giving and receipts, rooms and rotas, records kept private, and announcements in the languages your members speak.

// what you are up against

The problems we hear most.

01

Receipts at year end

Gifts arrive by cash, cheque, e-transfer and card, and the treasurer matches them by hand every winter to issue receipts.

02

A members list nobody can open

Family and member records sit in an old database or a shared spreadsheet, with no clear rule on who may see what.

03

Rooms and rotas by group chat

Halls, kitchens and classrooms are booked by message, and volunteer shifts are filled by whoever answers first.

04

Members who speak several languages

Announcements go out in one language, and newcomers or older members miss what matters to them.

// example projects

Systems we could build for you.

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
Example projectWeb app

Members register, rebuilt

Hypothetical. Not a client, not a result.

// The problem

A community centre keeps its members and families in an old Access database on one office computer, with no backup and no record of who has looked at what.

// What we would build

We move every record out of the old database, check it with your office team, and rebuild the register as a small web app with roles, so a group leader sees only their group, the office sees what it needs, and every change and export is logged.

// What is in it

  • Every member, family and group moved out of the old database, and checked with you
  • Roles so group leaders see only their own group
  • A log of every change and export
  • Consent recorded for photos, mailing lists and directories
  • Backups every night, and the old database kept read-only until you retire it

// Stack

  • Next.js
  • PostgreSQL
  • Access and spreadsheet import
  • DigitalOcean Toronto

// estimate

Build
≈ US$61,200 to US$93,600, delivered within 16 weeksCAD 87,200 to 133,300
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
Design approved
2.9 to 4.4 weeks
Core features
1.9 to 3.4 weeks
Full build
1.4 to 2.4 weeks
Testing and fixes
0.9 weeks
Moved records checked with your office
0.9 weeks
Launch
0.9 to 1.4 weeks

How it is paid

Deposit 20%
CAD 17,440 to 26,660
Discovery 6.8%
CAD 5,929.60 to 9,064.40
Design approved 6.8%
CAD 5,929.60 to 9,064.40
Core features 20.4%
CAD 17,788.80 to 27,193.20
Full build 13.6%
CAD 11,859.20 to 18,128.80
Testing and fixes 6.8%
CAD 5,929.60 to 9,064.40
Moved records checked with your office 8.7%
CAD 7,586.40 to 11,597.10
Launch 6.9%
CAD 6,016.80 to 9,197.70
Holdback, 30 days after launch (10%)
CAD 8,720 to 13,330
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
Example projectWeb appAIFrontier model

Multilingual site with an assistant

Hypothetical. Not a client, not a result.

// The problem

A mosque's website is in one language, its announcements live on social media, and the office answers the same questions about times, classes and services by phone every day.

// What we would build

A new website in the languages your members speak, edited by your office, with an assistant that answers visitors from your own pages and announcements, cites the page it used, and hands anything personal to a person. It answers practical questions only, never matters of belief.

// What is in it

  • A website designed for your community, in two or more languages
  • Announcements and events edited by the office in one place
  • An assistant that answers from your own pages and names its source
  • Anything personal or pastoral handed to a person
  • A set of real visitor questions, run before every change

// Stack

  • Next.js
  • Claude API
  • PostgreSQL with pgvector
  • Headless CMS
  • DigitalOcean Toronto

// estimate

Build
≈ US$90,700 to US$139,000, delivered within 23 weeksCAD 129,200 to 197,500
Hosting
≈ US$218 a monthCAD 310 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.

AI route
Frontier model
Model running cost
≈ US$42 a monthCAD 60 a month

Timeline by milestone

Discovery
2.9 to 3.4 weeks
Specification and evaluation plan
0.4 weeks
Design approved
3.9 to 6.4 weeks
Core features
1.4 to 1.9 weeks
Full build
0.9 to 1.4 weeks
Working pilot
3.9 to 6.4 weeks
Testing and fixes
0.9 to 1.9 weeks
Launch
0.9 to 1.4 weeks
Production
0.9 to 1.4 weeks

How it is paid

Deposit 20%
CAD 25,840 to 39,500
Discovery 2%
CAD 2,584 to 3,950
Specification and evaluation plan 10.2%
CAD 13,178.40 to 20,145.00
Design approved 2%
CAD 2,584 to 3,950
Core features 6.2%
CAD 8,010.40 to 12,245.00
Full build 4.1%
CAD 5,297.20 to 8,097.50
Working pilot 30.7%
CAD 39,664.40 to 60,632.50
Testing and fixes 2%
CAD 2,584 to 3,950
Launch 2%
CAD 2,584 to 3,950
Production 10.8%
CAD 13,953.60 to 21,330.00
Holdback, 30 days after launch (10%)
CAD 12,920 to 19,750
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
Example projectWeb app

Site and livestream page, looked after

Hypothetical. Not a client, not a result.

// The problem

A church's website and livestream page were set up years ago by a volunteer who has since moved, nobody has the passwords, and nothing has been updated or backed up.

// What we would build

We recover access, move the site and the livestream page to managed hosting in Canada, set up backups, monitoring and updates, and look after it month by month, so the office can edit the pages and nobody has to be the person who knows the passwords.

// What is in it

  • Access recovered and handed to your office, with passwords in a shared vault
  • The site and livestream page moved to managed hosting in Canada
  • Backups, updates and monitoring, with alerts to us
  • A short guide for whoever edits the pages
  • Help each month under a support plan

// Stack

  • Next.js
  • YouTube embed
  • DigitalOcean Toronto
  • Uptime monitoring

// estimate

Build
≈ US$28,700 to US$43,800, delivered within 13 weeksCAD 40,800 to 62,300
Hosting
≈ US$176 a monthCAD 250 a month
Support
≈ US$5,010 a monthCAD 7,135 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
Design approved
2.4 to 3.4 weeks
Core features
1.4 to 2.4 weeks
Full build
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 12,240 to 18,690
Discovery 6.6%
CAD 2,692.80 to 4,111.80
Design approved 6.6%
CAD 2,692.80 to 4,111.80
Core features 20%
CAD 8,160 to 12,460
Full build 13.3%
CAD 5,426.40 to 8,285.90
Testing and fixes 6.6%
CAD 2,692.80 to 4,111.80
Launch 6.9%
CAD 2,815.20 to 4,298.70
Holdback, 30 days after launch (10%)
CAD 4,080 to 6,230
Example projectWeb appBlockchain

Shared record between pantries

Hypothetical. Not a client, not a result.

// The problem

Several independent food banks run by different congregations pass surplus food between them, and each keeps its own list of what was sent and received, which never quite match.

// What we would build

A shared web app where each pantry records food sent and received, with every transfer recorded on a private permissioned ledger that each organisation runs a node of, so no single member holds the record. A shared database run by one host often does this job; the ledger helps when the members want no one organisation in charge.

// What is in it

  • Transfers between pantries recorded by both sides
  • Each transfer written to a private ledger with a node per organisation
  • Totals by pantry and month for each member's own reports
  • No personal details of the people served, ever
  • A plain read-out of the record any member can download

// Stack

  • Next.js
  • Hyperledger Besu (private, permissioned)
  • PostgreSQL
  • DigitalOcean Toronto

// estimate

Build
≈ US$84,100 to US$129,000, delivered within 22 weeksCAD 119,800 to 183,100
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
2.9 to 3.4 weeks
Architecture
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.4 weeks
Devnet
2.4 to 3.9 weeks
Testing and fixes
0.4 weeks
Testnet
2.9 to 3.4 weeks
Launch
0.9 to 1.4 weeks
Mainnet
0.9 to 1.4 weeks

How it is paid

Deposit 20%
CAD 23,960 to 36,620
Discovery 2.5%
CAD 2,995.00 to 4,577.50
Architecture 6.7%
CAD 8,026.60 to 12,267.70
Design approved 2.5%
CAD 2,995.00 to 4,577.50
Core features 7.5%
CAD 8,985.00 to 13,732.50
Full build 5%
CAD 5,990 to 9,155
Devnet 20.2%
CAD 24,199.60 to 36,986.20
Testing and fixes 2.5%
CAD 2,995.00 to 4,577.50
Testnet 13.4%
CAD 16,053.20 to 24,535.40
Launch 2.5%
CAD 2,995.00 to 4,577.50
Mainnet 7.2%
CAD 8,625.60 to 13,183.20
Holdback, 30 days after launch (10%)
CAD 11,980 to 18,310

// questions

What buyers in this industry ask us.

Do you work with communities of every faith?

Yes, and with secular community centres and cultural associations. We build tools for the work and stay neutral on belief.

Where are you, and who do you work with?

We are in British Columbia and work with communities anywhere; we set our working hours around yours. Prices are in Canadian dollars.

How do payments work?

A deposit to start, then payments at agreed milestones, with 10% held until 30 days after launch. The deposit is a smaller share on larger projects.

Who owns the software?

You do, once the work is paid for, including your data and the content of your site.

// where we work

Find your market.

We work from Kelowna with clients across Canada, the United States and further afield. Each market page covers working hours, hosting, the privacy law that applies, and prices in your currency.

// 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.

Software for faith communities, community centres and cultural associations | Atheron Network Labs