Know your people. Measure engagement.
Nobody decides to leave a church. They just stop coming, quietly, and by the time anyone notices it’s been four months. Foldmetric turns your service check-in into a named follow-up list — while there’s still a relationship to keep.
No app to install · works on any phone · 2 minutes to set up
| Member | Attended | Dates |
|---|---|---|
| Grace Adeyemi | 0 of 4 | 4 in a row |
| Daniel Okonkwo | 1 of 4 | Mar 01Mar 08Mar 15Mar 22 |
| Ruth Mensah | 2 of 4 | Mar 01Mar 08Mar 15Mar 22 |
| Samuel Boateng | 4 of 4 | Mar 01Mar 08Mar 15Mar 22 |
Your attendance report says 214 came. Foldmetric tells you which 37 didn’t — and which of them missed three services running.
One QR code in, a list of names out.
Most attendance systems fail because somebody has to keep feeding them. Foldmetric takes one scan at the door and turns it into a picture of who is actually turning up — and, the part nobody else gives you, who has quietly stopped.
They scan the code
A QR by the door is the only data entry point there is. One field — phone number or email — on whatever phone they own. Nothing to install, no account, no password, about 80 kB on a saturated church wifi.
Foldmetric matches them — or adds them
0803 123 4567and+234 803 123 4567are one person, matched to one record, once per service, so a double-tap cannot inflate a count. A number that isn’t on the roster doesn’t hit a dead end: they register themselves, and you get a first-timers list instead of a stranger nobody wrote down.Every service adds to the picture
One Sunday is a headcount. Twenty Sundays is engagement. Foldmetric keeps the record per person and per service, so you see an x of y ratio, a run of consecutive misses, and how long since anyone last saw them.
You get the list, by name
Day, week or month, with an x of y ratio per person and a flag on anyone who has missed several running. Export it as CSV, one column per service date, and hand it to whoever makes the calls.
That is the whole product today: the code, the matching, and a list of names you did not have before. Automated follow-up — reaching those people on WhatsApp, SMS or email and recording what they say back — is what we are building next, and it is included from Core when it lands.
The visitor who came once and was never written down
Every church loses people it never had. Somebody visits, nobody catches their number, and the only record is a face two people half-remember. The same QR code fixes it without a clipboard, a welcome card, or anyone being sent to hover by the door.
They add themselves
A number the roster has never seen is asked for a name, and that is the whole form. No dead end, no “see the desk”, no queue behind them.
You can tell them apart
Everyone who arrived this way is marked as self-registered, so a first-timers list is a filter rather than a guess — and the office knows which names it has never verified.
Then the same clock starts
A visitor who comes twice and stops is exactly the person a church means to follow up and never does. From their first scan they are counted like anybody else, so the second absence is visible instead of invisible.
Three misses in a row is a different problem from three scattered.
One is someone drifting away. The other is shift work, a new baby, or travel. A headcount can’t tell them apart, and neither can a list of names with no shape to it.
Foldmetric shows the pattern: the ratio, the exact dates, and whether the gap is consecutive. That’s the difference between a report and a triage list — and it’s the whole reason the product exists.
Daniel — 1 of 4
Drifting — three consecutive. Call this week.
Ruth — 2 of 4
Alternating — probably a rota or a commute. Leave it.
Then somebody actually hears from you
A list is a report. A list that sends the message is a follow-up. Foldmetric reaches the office and the member on the channels your church already uses — nothing goes out until check-in closes, and nothing goes out without your say-so.
Email, to the office
Who wasn’t there, in an inbox after each service — or once a week as a summary with the drift ratios for the whole period. Free on every plan, including the free one.
WhatsApp, to the member
In most congregations this is the one people actually read. Sent to the names on your absence list, one at a time or as an assigned round for a care team.
SMS, to the member
For the phone that isn’t a smartphone, and the member who never installed anything. Same list, same round, nothing to install at their end either.
You choose the channels once, for the church — and when someone qualifies: after three consecutive misses by default, or whatever number you set. Messaging the congregation starts on Core and is billed as credits, or connect your own Twilio or WhatsApp Business account.
Built for a real service
Whenever yours meets — Sunday morning, Saturday sabbath, Friday evening, or all three. Every one of these exists because something went wrong at an actual service, in an actual church, with actual people queueing at the door.
Any service day, any timezone
Sunday, Saturday sabbath, Friday evening, or four services across a weekend. Set the days and an optional time window; the schedule is evaluated in your own IANA timezone.
The clock isn't the phone's
Check-in opens on the server’s clock, never the device’s. Changing your phone’s date does nothing — otherwise "Sunday only" would be a suggestion.
Self-registration at the door
A first-time visitor who isn’t on file adds their name and is counted in the same step. No queue at the welcome desk. Everything that let itself in is flagged for review.
"That’s not my name"
Members can dispute the name they were greeted with. Corrections land in an inbox for the office and are never applied automatically.
Your directory stays private
The congregation’s contact details are never readable from a browser. The public check-in path can confirm a person; it can’t enumerate the roster.
One person, one record
Record IDs are derived from the phone number, so the office adding someone, a self-registration and a spreadsheet import all converge on one row instead of three.
Roster import
Bring the spreadsheet you already keep. Import replaces the directory cleanly and reports exactly what it changed before you commit.
CSV export, always
Every view exports, with one column per service date. Your data leaves as easily as it arrives — no export fee, no lock-in.
Layered anti-spam
Per-connection throttling that counts only failures, so a crowd on one church wifi never locks itself out. Optional reCAPTCHA for a busy door.
Priced for where your church actually is
Software priced in dollars for a Lagos or Nairobi congregation isn’t a product, it’s an insult. Foldmetric is priced regionally, bills in local currency, and takes local payment rails — while running on the same infrastructure everywhere.
Local phone formats
Numbers are matched the way people actually type them, per country, and stored in one canonical form so lookups never miss.
Your timezone, your sabbath
The service schedule is yours to define. Nothing in Foldmetric assumes Sunday morning in the Americas.
Pay how you pay
Card, bank transfer, or local rails like Paystack and Flutterwave. Card-only checkout excludes most of the world.
Find out who you’re losing.
Set up your church in about two minutes. Free under 100 members, and your data exports the day you decide it isn’t for you.