Engagement
6–12 weeks
Services/01
Custom
software..
Software shaped around how your business actually runs — not how a SaaS company thinks it should. Replacing the spreadsheet, the paper agenda, or the off-the-shelf tool that <em>almost</em> works but never quite did. Web or desktop, whichever fits the desk it'll sit on.
— Overview
Most small businesses I work with don't need more software — they need less, but right. A spreadsheet that grew teeth. A SaaS subscription that costs more than it saves. A system invented by a previous employee who left.
I sit with the people who'll actually use the thing. I watch the workflow as it really happens — the second tab nobody admits to, the sticky note on the monitor, the WhatsApp group where the real coordination lives. Then I build software that turns those workarounds into the system.
Boring on purpose. No buzzwords, no AI that wasn't asked for, no migration to the cloud just because. The goal is software you forget about because it works.
How it goes.
— How it goes01
Shadow
A day or two next to the people who'll use it. Notes, screenshots, the workflow as it actually happens — including the parts nobody puts in a brief.
02
Mirror
Build the existing flow in code, almost exactly. No improvements yet. Just the friction taken out.
03
Trim
Once it works, we delete what nobody uses. Fewer screens, fewer fields, fewer clicks. The version you keep is the one you didn't have to argue for.
04
Hand off
Live, documented, owned. A README that reads like it was written for a human, plus a walkthrough call so you can add a column without filing a ticket.
What you get.
— Deliverables01A tool people openDaily-use software, not dashboard theater. Fast, keyboard-friendly, no tour modal.
02Single source of truthOne database, one login, one place to look. Replace the four-tool tax with one.
03Source code, yours to keepFull repository handover, no vendor lock-in, all dependencies in your name.
04Owner-friendly handoffA README, a video walkthrough, and a 60-minute call so you (or whoever's next) can extend it without me.
FlutterTypeScriptSQLitePostgreSQLDesktopWebCross-platform
"The best small-business software is the one nobody complains about."— Operating principle, Iruoy
Common questions.
— FAQWill I own the code?
Yes. The repository ends up in your name, with full IP transfer in the contract and all dependencies registered to your business. I keep nothing.
Do I need to be technical to work with you?
No. I'll explain what matters in plain language and won't bury you in jargon. You'll know what we're building because you'll have shaped it — not because I sent you a Notion page nobody reads.
What happens if I need changes after launch?
For the first 30 days after launch, anything that's broken in what we agreed to build gets fixed at no extra cost. After that, small tweaks and questions are billed by the hour and invoiced when they add up to something worth invoicing — no monthly minimum, no retainer. New features get a fresh quote so we both know what we're agreeing to.
How long does a project really take?
Most projects run 6 to 12 weeks calendar time, with the work itself happening evenings and one weekend day. If something looks like it'll need more than that, I'll say so before we start — not after.