Customers

What we actually built for people who run things.

These are live deployments, written up with the customer's permission and without their names. No logos, no invented percentages, no quotes nobody said. What's left is the shape of each business, the mechanics we built, and the counts we can verify from the systems themselves — including the parts that went wrong first.

01 — The stories

Three builds, three different problems

One replaced a scheduling vendor across eight legal entities. One sat down beside an accountant's chart of accounts. One migrated a retail loyalty program off a platform we used to pay for ourselves.

Live

An 8-location shipping & print franchise

32 active employees, a separate legal entity per store, previously on Deputy with payroll assembled by hand in a spreadsheet. PIN identity on a counter tablet, a time clock, person-per-store scheduling, and a real .xlsx payroll workbook that mirrors the one they already used — plus the counter tooling that decided the whole fit.

Read: replacing Deputy across 8 franchise stores

Live

A sports-facility construction firm

Already running Autodesk Build with Cost Management and QuickBooks, with a bookkeeper coding spend and PMs classifying against budgets. We built the connective tissue: QuickBooks→Autodesk expense sync, truck-QR receipt capture, geofenced site check-in with a Spanish option, travel pay that pays passengers, and daily logs that land in the Autodesk Daily Report.

Read: job costing between Autodesk Build and QuickBooks

Live

The founding supplement retailer

An independent supplement store that migrated off TapMango and now runs the loyalty engine, kiosk check-in, carrier-compliant SMS, a member portal and app, InBody scan programs with a leaderboard, and an in-store TV mirroring scan results. Every release ships here first.

Read: migrating a supplement store off TapMango

02 — Also running on it

Deployments without a write-up

Not every tenant gets a case study. Three more are live and worth naming by shape, briefly, because they're the reason certain features exist at all.

  • The founding supplement store. Ours. It's the one with a full write-up above, and it's also the staging environment: the kiosk, the campaign sender, and the Shopify points sync all broke on its Saturday traffic before they shipped to anyone else.
  • A nutrition retailer running InBody scan programs. Body-composition scans post straight from the scanner into member records, and the scan-to-store mapping exists because this retailer has more than one location and one shared results feed. Its programs are why the member portal shows scan history next to points.
  • A community wellness organization. Member-facing programs and communications on the same multi-tenant platform, on its own subdomain and its own brand. Nonprofit-shaped rather than retail-shaped, which is a useful stress test for anything we assume about a “store.”

All of it runs on one platform with one database per tenant — the architecture is described on the platform page, and the full module list, including what's still early access, is on the roadmap.

03 — How we write these

The rules we hold ourselves to

Case studies are the easiest page on a software site to fake, so here's the standard. Counts come out of the live systems: 8 locations, 32 active employees, 87 imported user records, 208 imported subcontractor and vendor records, 37 connected construction projects. Mechanics are described at the level of what a button does. And where a build hit something ugly — a camera that couldn't read a dense barcode, a third of an import that was misfiled, an API endpoint whose field names had moved — the write-up says so.

What you won't find: revenue lift percentages, retention deltas, or a quote in someone's voice. We didn't measure those, so we don't publish them. If you want the honest version of a fit question, that conversation is the demo, and pricing — published for retail, quoted for workforce and construction — is on the pricing page.

04 — Questions

Straight answers.

Why are the case studies anonymized?

Because that is what our customers agreed to. Their payroll structure, pricing margins, and job costing are competitive information in small markets. We describe each business by shape and keep the mechanics and the real counts — the parts that tell you whether the platform fits.

Why are there no revenue numbers or quotes?

Because we do not have ones we can stand behind. We publish counts we can verify from the systems themselves — locations, employees, imported records, connected projects — and we do not publish percentage lifts we did not measure or testimonials nobody gave us.

Can I talk to an existing customer before signing?

Ask on the demo call. Some will take a reference call and some will not, and it depends on whether you are in their market. What we will always do is show you the live system doing the thing you care about.

Is every build this custom?

The loyalty, kiosk, SMS, and workforce core is the same product for everyone. The custom part is the shape of the paperwork it has to match — a quoting form, a payroll workbook, a stamp log. Retail pricing is published at $200/mo plus a one-time $500 setup; workforce and construction work is quoted per site and headcount.

05 — Next step

Bring us your version of the mess.

Book a 20-minute demo. Bring the spreadsheet, the paper form, or the vendor invoice you're unhappy about — those are the conversations that go somewhere.

$200/mo platform · 5,000 texts included · no contracts · ops & construction quoted per site