Case Study: Umbrella HQ — Grant Tracking Nonprofits Can Take to an Audit

Grant money comes with strings. Federal grants come with strings, footnotes, and a regulation numbered 2 CFR §200.430. This is the story of how we built Umbrella HQ, a custom grant management system for a nonprofit bookkeeping firm that manages grants for multiple organizations — and why their spreadsheets never stood a chance.

The client and the problem

Our client is a nonprofit bookkeeping firm that handles grant administration for several nonprofits at once. Each organization has its own grants. Each grant has its own funder, its own budget categories, its own reporting schedule, and its own rules. Federal awards add another layer: expenditure reports on the funder's timeline, schedules of federal spending at audit time, and written certification that staff time charged to a grant matches time actually worked.

All of this lived in spreadsheets. Budgets in one workbook, monthly reimbursement requests in another, personnel splits in a third, and the reporting calendar in somebody's head. Every month meant rebuilding the same reports by hand; every audit meant a scramble to reconstruct who approved what, and when.

If that sounds familiar, here are the signs you've outgrown spreadsheets. The team wasn't disorganized — they were over-organized in a tool that can't enforce rules or remember history.

What we built

Umbrella HQ is a web app the whole team signs into, protected by passwords plus passkeys, so Touch ID or Face ID gets the team in. The structure underneath is simple: client organizations, their grants, and the monthly submissions against each grant.

• Grant and budget tracking. Every grant carries its funder, award amount, budget categories (personnel, travel, operating, equipment, contract, training, indirect, and so on), status, and the signed grant agreement attached right to the record.
• A real approval workflow. Monthly reimbursement requests move from draft to internal review to approved, then on to the funding agency and finally to paid. Each grant has a named preparer, reviewer, and submitter, and nothing skips a step.
• An audit trail for everything. Every edit, approval, rejection, and certification is logged with the person, the timestamp, and any note attached. When an auditor asks "who changed this and why," the answer is one click, not one weekend.
• Federal reporting built in. The system generates the schedule of federal expenditures auditors ask for, pre-fills federal financial report figures, and handles time-and-effort certification, with each signed certification frozen as a snapshot so later edits can never quietly rewrite the record.
• A reporting calendar that nags. Every grant's deadlines feed a shared calendar and dashboard reminders, color-coded by urgency, with a daily email digest so nothing slides past its due date. Approving a report automatically rolls the next deadline forward.
• AI where it saves real time. Upload an expense report (even a scanned one) and the system reads it, extracts the line items, and matches each to the grant's budget categories for review. Snap a photo of a receipt and it becomes a documented line item, file attached.
• Reports people can hand over. Everything exports as a PDF or a spreadsheet, including a full submission packet with line items, receipts, and comments in one document.

Why grant software has to be custom

Off-the-shelf grant tools assume every funder behaves the same way. They don't. One funder pays on reimbursement, another pays in advance. One wants monthly reports, another quarterly. Some money isn't a grant at all — it's a contract with different spending rules. A generic tool forces you to fudge those differences, and "fudge" is not a word you want in an audit finding.

Because Umbrella HQ was built around this team's actual workflow, the software encodes their rules: which funding can be spent past a period end date, who's allowed to create or delete a grant, exactly which review steps a submission passes through. The tool matches reality instead of the other way around — which, as it happens, is the entire argument for custom software.

What changed

We could invent an impressive percentage here, but the plain comparison is damning enough. Before: grant data scattered across workbooks, reports rebuilt by hand each month, and audit prep as an archaeology project. After: every grant, budget, submission, approval, and certification in one place, with a complete history behind it.

The records are built to be ready when an auditor asks: every approval and certification is logged as it happens instead of reconstructed at quarter-end. Deadlines announce themselves instead of ambushing anyone. And once the team was using it on real grants, their feedback (a status label here, a smarter import there) shipped in days, not release cycles. That's the quiet advantage of software that's built and maintained for you: it keeps getting better in your direction.

Frequently asked questions