labs@atheron:~/industries/faith-community/data$ query --warehouse --dashboards

Outreach reporting

Funder reports from the records, with no names in them.

Outreach programmes are asked for numbers by every funder, each in its own format. We record visits and programmes once, keep personal details private, and build a dashboard and exports that answer each funder's questions from the same records.

Start a project See the example projects

// what matters here

What is different in this industry.

Recorded once

Visits and programmes entered at the door on a tablet, not on paper sheets typed up later.

No names in reports

Reports and dashboards show counts and trends only; personal details never leave the records.

Each funder's format

Exports shaped to the questions each funder asks, from the same records.

Shared between pantries

Where several organisations work together, a shared record of transfers between them.

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

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

Start from this example

// questions

Questions we get about this.

Can a funder log in and see our numbers?

If you want, with a read-only view of the totals you choose and nothing personal.

What do we have to ask the people we serve?

Only what you decide. We build the intake around your questions and record consent.

Can it handle several sites or programmes?

Yes. Each site and programme is recorded separately and added up in the dashboard.

Back to the industry: Faith and community organisations About the service: Data and analytics

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