Codes corporate card and bill-pay transactions against federal grant cost rules (2 CFR 200) and flags unallowable spend before drawdown; nonprofits and fiscal sponsors pay for compliance automation. · Grant compliance software
DEAD SLOW · CAUTIOUS
6.4 ShipScore / 10
Automated compliance engine scores well on time; thin demand evidence keeps need unproven.
Condition: Finance leads at federally funded nonprofits or fiscal sponsors must confirm they would pay for pre-drawdown flagging beyond their fund-accounting suite.
Part I — The Verdict what the instruments read
01 — The ShipScore breakdown
Control
6
Relies on card/bill-pay feeds and ledger integrations; several vendors, none irreplaceable.
Entry barriers
6
2 CFR 200 rules engine is a modest moat; no funded rival tracked.
Need
6
Established paid category, but only ZUUZ's $8k MRR tracked; no Reddit pain.
Time-freedom
8
Rule-based transaction coding is productizable SaaS; onboarding may need hand-holding.
Scale
6
US federal grantees only; large nonprofit base but single-country regulation.
What the five commandments measure
C — Control
Do you own the customer, or does a gatekeeper stand between you and revenue?
E — Entry
How hard is this to copy once it works? A rival's existence isn't the question — the durability of their advantage is.
N — Need
Is demand proven with money rather than vibes?
T — Time
Can income detach from your hours, or did you buy yourself a job?
S — Scale
How far does it reach without linear cost?
Scored on the evidence below, against CENTS as we've adapted it plus a Buffett-style moat reading of every rival — the same referee for every idea, including the ones we generate ourselves. The verdict follows the arithmetic: we never relabel a score to make it read better, and the weakest commandment is always named. The exact rubric stays in-house so the scale can't be written for.
02 — The pace test — $1M/yr
At $300/mo (assumed category price), you need 278 subscribers for a $1M/yr pace.
Misclassification liability if flagged-clean spend is later disallowed in audit.
Card platforms could add grant-coding themselves.
06 — Kill switches — what kills this with one decision
Card/spend platforms (e.g., Ramp, Brex) launching native grant coding — Removes the need for a separate layer at the transaction source.
OMB revisions to 2 CFR 200 — Major rule changes force costly rule-engine rework; manageable, not fatal alone.
Part III — The Plan if you insist on proceeding
07 — What this scan can't tell you
Cannot tell whether ZUUZ actually competes on grant compliance or is adjacent.
No evidence on how many grantees use corporate cards vs. AP-only spend.
Cannot gauge willingness to pay against existing auditor/consultant spend.
Scores judge the market and business model — not your ability to execute. Verified MRR = independently tracked revenue; reviews/upvotes = platform-reported. Judged 2026-10-25.
08 — The wedge & the next step
Fiscal sponsors managing many federally funded projects, flagging unallowable card spend before drawdown.
Cheapest next step: Interview 10 fiscal-sponsor finance directors about recent disallowed costs and test a $300/month pre-order.
Not quite it? Spin the model
Business-model variations of this idea, engineered to beat 6.4 — different vertical, audience, model, or wedge. Same harsh scale. Pro feature.
One evidence-backed gap a day, free
Close — but conditional. Every morning the engine files one mined gap, scored on the same harsh scale as this one. Free at 7am AEST, unedited.
Free forever · one email a day · unsubscribe in one click.