The tools stopped fitting, and there's no one on staff to fix it.
I build the software that replaces them: the system your staff run the work from, and the site your members or clients log in to. You need a number you can put in a budget and defend to a board, so the first week settles what gets built and what it costs. After that the build is a flat $8,000 a month, usually for three to six months.
It usually looks like one of these.
Client records in spreadsheets and inboxes.
Human services nonprofits: intake, case management, donors, volunteers. Sensitive data, handled by hand, and no one on staff who can scope a build or judge a quote.
A membership system that almost fits.
Trade and professional associations: membership, credentials, events, continuing education. A system that nearly does the job, and a decade of spreadsheets filling the gaps.
The workaround everyone depends on was built by someone who left.
Established businesses: the tools were outgrown years ago, someone patched a fix, and nobody left can explain it. It needs replacing with something that will last.
What it looks like afterward.
From a stack of spreadsheets everyone was afraid to touch, to one system.
Before: a whole season of shows, actors, and scheduling ran on Google Sheets wired together with custom code. The person who built it had quit, and it broke constantly with no one able to fix it.
After: one secure web application. The work they did by hand is automated, and shows, actors, scheduling, and scripts live in a single place they can trust.
From fundraisers cancelled overnight, to fundraisers that run online.
Before: funding came largely from in-person events. When COVID-19 ended those overnight, the organization was at real risk of closing.
After: one focused tool, not a big platform: a web app where donors buy raffle tickets in real time. The first one raised tens of thousands of dollars and kept them open. I've run their software ever since.
Neither started as a request for custom software. Each started as a problem the organization couldn't keep working around. Read the full stories →
Most organizations shouldn't build. Here's how to tell.
Buy it when a product already fits.
If something off the shelf matches how you work, buy it. It costs less, and someone else keeps it running. Sometimes the fix isn't software at all: a process change, a renegotiated contract, or setting up something you already pay for.
Build it when the workarounds have become the job.
You've tried the products, and your staff spend their days filling the gaps between them: retyping records from one system into another, keeping the spreadsheet that holds what the system can't, depending on a fix only one person understands. Custom software is built around how your organization already works, so that labor goes away.
Not sure which side you're on? That's what Discovery settles, and it's free. If the answer is “don't build,” I'll tell you before you've spent anything.
Discovery
About a week, before any code and before you pay anything. We decide what the software needs to do, what waits for later, what moves over from the old system, what it connects to (membership or case-management system, accounting, donor database), and any rules your field has to follow. The week is interviews with the people who'll use it, a look at what you have now, and mockups of the main screens. Most first versions are three times bigger than they need to be. Cutting them is the cheapest work in the whole engagement.
- A proposal, in plain English, with a price you can put in a budget
- Mockups of the main screens, so you see it before you sign
- A month-by-month build plan, in priority order
- How many build months it takes, so the budget is arithmetic
- What moves over from the old system, and what it connects to
- What waits for version two, written down
- What's the smallest version worth shipping?
- What will it cost, as a number I can put in a budget?
- Keep, fix, or replace what we already have?
- What happens to ten years of spreadsheets?
- Should we build this at all?
You see what you're getting before you pay for anything. If the answer is that you shouldn't build at all, I'll say so, and it costs you nothing to hear it.
- Duration
- About 1 week
- You get
- A proposal + mockups of the main screens
- Terms
- Free, no obligation
What the proposal contains.
Written in plain English, with mockups alongside:
- What we're buildingVersion one, argued down to what it needs, with the reasoning so you can push back.
- What it looks likeMockups of the main screens your staff and members will use.
- The technical approachThe tools, the hosting, and what it costs to run each month.
- What it connects toWhat moves over from the old system and spreadsheets, what it talks to (membership, accounting, donors, payments), and any rules your field follows, such as HIPAA or grant reporting.
- The build planWhat ships in month one, month two, and so on, in priority order.
- The budgetHow many months at $8,000, with the reasoning, and what gets cut first if the estimate slips.
- RolloutHow staff get trained and how the switch from the old system happens.
- What waitsEverything cut from version one, set aside where it can't inflate the budget.
Build
Built to the proposal you signed: the site your members or clients log in to, the screens your staff run it from, the records moved over, the connections to the systems you keep, and the training and rollout at the end. Each month starts with a planning session and ends with something usable in your hands and a written summary of what shipped. That summary restates how many months remain. If the plan is slipping, you read it there, with time to cut scope or add a month at the same price. The estimate came from the person doing the work, so it's a number I have to live with.
- A flat $8,000 a month, invoiced in advance
- You set the priority order; I ship what fits, in that order
- No change orders. Anything added goes on a later month's list, at a price you already know
- Three months to start, then month to month with 30 days' notice. $24,000 is the smallest total
- Every monthly summary restates the months remaining, so an overrun is a decision made early
The code, the designs, the accounts, and the rights, with documentation, so you're never locked in to me. I don't resell software or take vendor commissions.
- Your marketing site
- New features after launch. That's a build month
- Your hosting, payment, and vendor accounts, opened in your name, and any legal or regulatory sign-off
Everything is documented as it's built and every account is in your name, so a handoff doesn't depend on me. For overflow or a gap I have contractors I trust, brought in only with your knowledge and with me still responsible. I carry general and professional liability insurance and will sign a business associate agreement where your data requires one.
The month count comes out of Discovery, so I'm planning from a proposal I wrote, not guessing. If a grant, an RFP, or a regulator requires a fixed total, I can quote one against that proposal, from $20,000. The FAQ explains when that applies.
Maintenance
Software isn't finished when it ships. Once it's live, a maintenance retainer keeps it running: security updates, bug fixes, monitoring, small changes, and a standing technical person for whatever crosses your desk. Up to ten hours a month for $2,500, or twenty for $4,000. The price buys more than the hours: monitoring that runs whether or not anything breaks, a reply within a business day, and outages worked the same day. Hourly work comes with none of that. Hosting and outside services are billed at cost to accounts in your name. Anything that needs a scope conversation is a build month, and as-needed work outside the retainer is $200 an hour with no promise of availability.
- Updates, monitoring, and fixes, often before you notice
- A reply within one business day; outages worked the same day
- A standing technical person for what crosses your desk
- Hosting and vendor bills stay in your name, at cost
Preston Center of Compassion has been on a retainer since 2020. Six years on, I still run their fundraising apps, email, and donor database.
Hours don't roll over, and I'll tell you before a month runs past its allowance. Month to month; stop whenever it stops being worth it.
Every price is on this page for a reason. If a number rules me out, you've saved us both a meeting.
Everything starts with Discovery.
A build can't be planned before the discovery work is done, so Discovery comes first, and it's free. It puts a month count on the build before you commit, weeds out the projects that shouldn't happen, and shows you mockups of what you'd be getting. The first step is a conversation, not a contract.
What clients say.
We've worked with Frank for over six years now. He created our virtual fundraisers that kept us open and serving the Bronx when COVID threatened to shut us down.
- Preston Center of Compassion
- Candle House
- Miirror Health
- Inside Outside Health
- Rensselaer Center for Open Source
Questions people ask before signing.
What if the answer is “don't build”?
Then I'll tell you, before you've paid anything. Plenty of problems that look like software problems aren't. Often the fix is a process change, a renegotiated contract, or setting up something you already pay for. I'd rather tell you that in week one than start a build I don't believe in.
What exactly do I get from Discovery?
A proposal and mockups of the main screens, before you pay anything. The proposal covers version one argued down to what it needs, the technical approach in plain English, what moves over from your current system and what it connects to, any rules you have to follow, a month-by-month plan, and an estimate of how many build months it takes. The budget is $8,000 times a number you've seen the reasoning for, and the mockups show what that number buys.
Can we skip Discovery and go straight to a build?
Discovery comes first for every engagement, and it's free. A build can't be estimated before the discovery work is done, and a month count built on a guess punishes us both. If you already have notes, board minutes, or a document from another developer, bring them. Good input makes Discovery faster, not unnecessary.
Why a monthly price instead of a fixed one?
A fixed price only works when the requirements hold still, and they rarely do. Priorities shift the moment staff see working software, and a fixed-price contract turns each shift into a change order and a negotiation. The retainer fixes the price and the pace and leaves the contents of each month to you. For a budget, it's a predictable line item instead of one large capital request, and you can stop at any month boundary holding working software.
What if the build runs past the estimate?
You'll see it coming. Every monthly summary restates months shipped and months remaining, so a slip shows up in writing the month it starts. When it does, the choice is yours and the price isn't: cut what's left to hold the budget, or add a month at the same $8,000. The monthly price can't rise, and you can stop at any month boundary with working software you own. Most first versions land in three to six months.
We need a fixed total for a grant or an RFP. Can you do that?
Yes, when the fixed total is imposed from outside: a grant deliverable, an RFP, a regulator, or a partner's specification. Then I quote a fixed fee against the Discovery proposal, from $20,000, paid in three stages: 35% to start, 30% mid-build, and 35% on completion. Anything outside the proposal is priced as a change order before the work happens. It's the exception, because a fixed price has to be padded against unknowns a monthly arrangement absorbs.
How do payments work?
Discovery is free. The build is $8,000 a month, invoiced at the start of each month. The first three months are a commitment on both sides, so the smallest total is $24,000. After that it's month to month with 30 days' notice either way. No change orders: anything added goes on a later month's list. Once the product is live, maintenance is $2,500 a month for up to ten hours or $4,000 for up to twenty, month to month.
How is this different from hiring an agency?
With an agency, one person sells the project, another manages it, and a third builds it, and what ships has been translated twice. With me, you explain it once, to the person who builds it. The trade-off: I'm one person, I can't put five engineers on a deadline, and I'll say so when a project is bigger than I should take on. In exchange you get software that matches what you described, and someone who'll tell you when a feature isn't worth the money.
What happens if you're unavailable?
Less than you'd fear. Everything is documented as it's built, and the code, designs, and accounts are in your name, so another developer can pick it up from the documentation. For overflow or a gap I have contractors I trust, brought in only with your knowledge and with me still responsible. I carry general and professional liability insurance, certificates on request, and will sign a business associate agreement where your data requires one.
Will I own what you produce?
Yes, all of it. Code, designs, documents, and the rights, plus documentation so you're never locked in to me. I don't resell software or take vendor commissions, so nothing I hand you steers you toward a product that pays me.
What's not included?
Two things people assume are included and aren't: new features after launch, which are a build month or as-needed work at $200 an hour, and your marketing site. A few things stay yours: the hosting, payment, and vendor accounts, opened in your name; the decision about which records move over from the old system; and any legal or regulatory sign-off. I'll help with all of them, but the agreement says plainly that they're yours.
Can I talk to a reference first?
Yes, and I'd encourage it. I'll put you in touch with clients who've been through this, including the ones named on this site. Some engagements are confidential and can't be discussed publicly, but I'm glad to talk specifics privately.
Do you discount for nonprofits?
The price doesn't move, but the scope does. A good share of my work is with nonprofits, and the way to meet a smaller budget is a smaller first version or fewer months, not a cheaper month. I'll show you what comes out and what it costs to leave it out. Every client pays the price on this page, which is what makes it a number you can carry to a board.
Book a free consultation.
No technical experience needed. We talk through what you want built, I explain how the process works, and we decide together whether and where to start. Pick a time below.
Calendar not loading? Open the scheduler in a new tab →
Rather write than talk?
Email me and you'll get me: no form, no one in between. Tell me what you want built and I'll tell you whether I'm the right person for it, or whether you should build at all.
frank@matrangacode.worksOr call (518) 217-8298