Industries
Six people, forty volunteers. Records you answer for.
We build the tools a small team runs on — donor records, grant tracking, volunteer sign-up — so three jobs each becomes two.
Free · Ten minutes · The report is yours either way
From the gift to the board packet
Four spreadsheets, one record. The board report follows.
Donations, grant deadlines and volunteer shifts in one system instead of four files — and a quarterly report assembled from those same records, not rebuilt on a Sunday.
The spreadsheets stop being the system
Donors, gifts, grant dates and volunteer sign-up in one place — instead of four files and a question about which one is current.
- Donor list — three versions
- Gifts this year — one laptop
- Grant deadlines — somebody’s copy
- Volunteer sign-ups — in email
- Records
- Donations · Grants · Volunteers · Board reports
- One place, not four files
A gift is entered once
It reaches the receipt, the donor’s giving history and the year-end letter without anybody typing it again.
- A monthly gift comes in · entered once
- Receipt — sent
- Giving history — updated
- Year-end letter — on the list
- Recorded once, on the giving page. Everything under it comes off that entry.
- Nobody types it twice
The board report assembles itself
Every section comes from the records the office already keeps, so the quarter stops being two days of working it out.
- Board report · Third quarter
- Giving this quarter — from the donor records
- Grants and deadlines — from the grant board
- Volunteer hours — from the shift list
- Report ready for the board · no retyping
- Not rebuilt on a Sunday
Every funder date on one screen
Reports, renewals and site visits, weeks before a funder has to ask where they are.
- Grant deadlines
- Report due — Oct 15
- Renewal — Nov 3
- Site visit — Dec 2
Shifts with an end date
People claim a shift and get a reminder — and the season’s access ends when the season does.
- Volunteer shifts
- Saturday · 9–12 — Claimed
- Sunday · 1–4 — Open
- Access ends when the season does
Monthly beside one-time, same size
A giving page that asks for the monthly gift first, and no account to make before giving.
- Make a gift
- Monthly · One time
- No account to make
Donors fix their own card
Giving history, last year’s receipts, and the expired card updated by the donor instead of by you.
- Your organization · Your giving
- Giving history
- Last year’s receipts
- Update card
A gift is entered once and reaches the receipt, the giving history and the year-end letter. A funder’s date sits on a screen weeks before anybody has to ask for it. And the quarter’s report comes out of records everybody already agrees on, instead of two days of working them out.
Ten minutes on a call, then a written plan of what to build first — often less than somebody told you.
What we build
We build it. Then we keep it running.
Web applications, client portals, booking systems and the small tools that take a job off somebody’s desk — designed and built for nonprofits and foundations, then supported by the same people who wrote them.
One firm. The people who built it are the ones who answer afterwards.
A giving page with monthly first
The monthly button sits beside the one-time button, same size, and no account to make.
A supporter sign-in page
Giving history, last year’s receipts, and the expired card fixed by the donor instead of by you.
Volunteer shifts with an end date
People claim a shift, get a reminder, and lose the season’s access when the season ends.
A grant deadline board
Every report, renewal and site visit on one screen, weeks before a funder has to ask.
Bring it to the same ten minutes. We’ll tell you whether it is worth building before we quote it.
A nonprofit runs on people who stayed late. The director rebuilds the board report on a Sunday, out of a spreadsheet nobody else opens.
What breaks is rarely dramatic. A pledge recorded in one place and not the other. A grant deadline nobody logged. A form that arrives as email.
10 min
on a call, no charge
Weeks
to something you can use
Yours
the code, and the data
If you hire us
How the first build goes.
01First weeks
We read what is there
Whatever runs your work today keeps running while we learn how it is actually used.
02The first piece
Something you can use
One useful part, shipped early, instead of one delivery at the end you cannot see until it lands.
03After that
The people who built it
The same team keeps it running, so a change is a conversation rather than a project.
Ten minutes on a call. You keep the plan either way.
What we handle
What we build for you.
The same foundations underneath, shaped to how your week runs.
The spreadsheet stops being the system
Names, gifts and history in one record, not four files and a question about which is current.
A gift is entered once
It reaches the receipt, the donor record and the year-end letter without anybody typing it again.
The board packet stops eating weekends
Your numbers come from one place everybody agrees on, instead of two days of working it out.
Sign-up stops arriving as email
What a volunteer fills in lands on the list itself, so nobody copies it across on Monday.
The treasurer’s number matches yours
The gift you record and the figure in the books stop being two different numbers.
Volunteers see shifts, not donors
Who can open giving history is decided in the build, not by who knows the login.
Other industries we build for
Start with the review. Ten minutes.
Start with ten minutes on a call, then a written plan of what to build first — and often the answer is you need less than somebody said.
Or ten minutes on the phone first
About half the reports say you’re in decent shape. If that’s you, we say so and leave.