You don't have an engineer yet. That's what I'm for.
You've raised the money and done the homework, and now a real product has to exist. You're deciding what it is, who builds it, and what it should cost, with no engineer on your side of the table. I build first products for founders in exactly that spot, and the first thing I'll do is argue yours smaller.
Three ways founders end up on this page.
Nothing exists yet
You've done the homework: conversations, a waitlist, a spreadsheet someone is already using. Now the product has to exist, and there's no one to build it.
You inherited a mess
An agency, a contractor, or a team of students built you something. It half works, it costs more every month than it should, and nobody left can explain how it fits together.
You're about to hire
Your first engineer, or a dev shop with a convincing deck. Either way you're making a technical judgment call with no technical person on your side of the table.
What these have in common: something has to get built, it has to be built right the first time, and there's no one on your side of the table who builds. That's the gap I fill.
I've done the job you're hiring for.
At OnePay, a venture-backed fintech, I was an engineer on a mobile banking app used by tens of millions of people and moving tens of billions of dollars a year. Then I led the engineering team at Huml Health, a healthtech startup building wearables for patients in substance-abuse detox and recovery — where making the call, owning the roadmap, and answering for the outcome were mine, because there was no one above me to escalate to.
So when I tell you a feature can wait, a quote is too high, or the thing you inherited isn't worth saving, it's a call I've made before with my own name on it. And because the person estimating your product is the person building it, the estimate is one I have to live with.
One week to define it. Then a flat monthly price to build it.
Early-stage products change direction; that's what the stage is for. A fixed-price contract punishes you for learning something, and everyone ends up arguing about scope. I work on a monthly retainer instead: the price and the pace are fixed, the contents of each month are yours to set, and you can change direction between months without renegotiating anything.
Discovery
One week before any code, and before you pay anything. We settle what the product needs to do and what gets cut from version one, how it will be built and what it will cost to run each month, whether it lives in the App Store or on the web, and any rules your industry adds. You get a proposal with mockups of the main screens, a ranked list of what gets built in what order, and an estimate of how many build months version one takes, so you see what you're buying before you sign.
Build retainer
A month buys a fixed slot in my working time, on a product I'm taking on alongside only a few others. You own the priority order and I ship what fits, in that order, so something usable is deployed every month and you get a written summary of what shipped. If you stop after month three you have working software, not a construction site. Reprioritize freely between months; added scope is next month's list, at a price you already know.
Projects in highly regulated industries — healthcare, financial services — carry a premium.
Maintenance retainer
Once you're live, this keeps it that way: hosting and security updates, bug fixes, monitoring, small changes, and a standing technical person for what crosses your desk, from the contractor's estimate to the engineer you're about to make an offer to. Requests are acknowledged within a business day. New features are a build month; as-needed work outside a retainer is billed at $200/hour. Month to month, until you hire in-house.
- Billed in advance — the month starts when payment clears
- A planning session sets the month's list; you set the priority order, I ship what fits
- Something usable is deployed every month, with a written summary
- Three-month initial term, then month to month with 30 days' notice either way
Code, designs, accounts, and the intellectual property, with documentation — so an investor doing diligence gets the right answer, and your first engineering hire can pick it up on day one.
The sequence matters more than the prices. Discovery is where I earn the right to tell you what not to build; the monthly retainer is what keeps a change of direction from turning into a contract negotiation.
Most first versions are three times bigger than they need to be. My first job is arguing yours down — even though the smaller one bills less.
A clinically-governed mental health product, shipped to the App Store.
Miirror Health · a prototype nobody could run, rebuilt simpler and compliant from the start.
An early-stage startup building a digital platform for eating-disorder recovery — clinical care with serious safety obligations, not a normal app. The founder had inherited a platform built by students: over-engineered, unmaintainable, and already costing hundreds of dollars a month before it had even launched. They needed a straight answer on whether it was worth saving.
It wasn't. The product carried far more complexity and cost than an early-stage company should, with no realistic path to maintain it. I recommended starting over with something deliberately simple and cheap to run, and, because this is healthcare, meeting the privacy rules (HIPAA) from the first day rather than bolting them on later.
Shipped to the App Store for beta: the patient app, the dashboard clinicians use to control what each patient sees, and the tools behind both, with the content safety rules built exactly to what their clinical advisory board approved.
- Preston Center of Compassion
- Candle House
- Miirror Health
- Inside Outside Health
- Rensselaer Center for Open Source
Questions founders ask first.
How small should the first version be?
Smaller than you think, and it's the first thing we'll argue about. Most first versions carry three times the features they need, which triples the cost and delays the only thing that matters — putting something in front of real users. My job early on is to find the shortest path to a product you can learn from, and build that. The rest waits until someone outside your organization has told you it's missing.
I inherited an app someone else built. Is it worth saving?
Yes, and it's a common way founders start with me. That's what Discovery is for: a free week, before any proposal, that ends in a straight answer — keep it, fix it, or start over — with numbers attached to each. Sometimes what you inherited is fine and just needs an owner. Sometimes it carries far more complexity and cost than an early-stage company should, and the right recommendation is to rebuild something much simpler. I've given both answers.
What if the build takes more months than the estimate?
Then you decide whether to keep going, at a price you already know. That's the point of the structure: added scope is a decision you make with a number in front of you, not a surprise invoice after the fact. I'll tell you we're heading that way before we get there, not after. And stopping is always available at any month boundary — what shipped in the months you did pay for is working software you own.
Why is each month paid in advance?
Because a month reserves a fixed slot in the only capacity I have. I take on a small number of products at once, so booking you means turning someone else away from that slot — and if a month is cancelled halfway through, I can't refill it. Paying in advance is what makes that arrangement possible. Each month starts when payment clears. The first three months are a commitment on both sides; after that it's month to month, and either of us can end it with 30 days' notice.
What if our direction changes completely?
Reprioritize between months at no cost — that's the whole reason the engagement is shaped this way instead of as a fixed-price contract. Reorder the list, cut things, add things, and next month works down the new list. But if the direction is changing that fundamentally, it's worth saying out loud: we should talk about whether you're ready to build at all, or whether another round of talking to users is a better use of $8,000.
Do you take equity instead of cash?
No. I work for a fee, and that's deliberate — it means I have no stake in your product growing bigger than it needs to be. If a build is out of reach at your stage, say so on the call. I'd rather scope it down to something you can afford than take a position in your company.
Who owns the code?
You do — all of it. Code, designs, documents, accounts, and the intellectual property, plus documentation so you're never locked into working only with me. This matters more for you than for most of my clients: an investor doing diligence will ask, and “our contractor owns it” is not an answer you want to give.
Can you work with our existing developers?
Yes — though not as a build engagement. If you already have developers and what you're missing is someone senior enough to make the calls, that's an advisory retainer: the same $8,000 a month and the same capped time as a build month, spent on direction, architecture, and build-versus-buy calls instead of on code. Some people would call that a fractional CTO. It isn't a product I sell off a page — tell me the situation on a call and we'll work out whether it fits.
What's not included?
Two things founders often assume are included, and aren't: ongoing feature development after launch — that's another build month, or as-needed work outside a retainer billed at $200/hour — and your marketing site. A few things stay your responsibility rather than mine: the App Store developer account, the business entity, the terms of service, and any regulatory or clinical sign-off your product needs. I'll help you navigate all of them, but they're yours, and the agreement says so plainly.
What happens when we hire our own engineers?
That's the goal, and I build for it from the start — no clever tricks, documented as I go, built with standard tools a new engineer will recognize on day one. When you're ready to bring the work in-house I hand it over and help your first engineer find their footing. I'm glad to sit in on those interviews too; judging a technical hire is not something a non-technical founder should have to do alone.
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.
Book a free consultation.
Bring the messy version: the half-formed idea, the app you're afraid to touch, the quote you don't know how to read. We'll talk through where you are, I'll walk you through how I work, and together we'll figure out which of these, if any, fits. Pick a time below.
Calendar not loading? Open the scheduler in a new tab →
Rather write than talk?
Email me and you'll still get me — no form, no one in between. Tell me what you're building and where you're stuck, and I'll tell you whether I'm the right person for it.
frank@matrangacode.worksOr call (518) 217-8298 · find me on LinkedIn →