Software built around how you already work.
A written quote before any build starts, and you own everything when it ends.
What I build
Five kinds of software.
- Desktop apps
- Installed on a computer. Works on local files, online or off.
- Web apps
- Opens in a browser, with logins and a database behind it.
- Internal tools
- A screen your staff use in place of a shared spreadsheet.
- AI agents
- Reads a request and picks the next step, inside limits you set.
- Automations
- A fixed rule. When one thing happens, another follows.
How a build works
From first call to software you own.
- Free
Intro call
20 minutes to decide whether a session is worth your money.
- $150
Session and verdict
75 minutes. You keep the verdict and roadmap.
- In writing
Scope and quote
What gets built, the milestones and one price. The session fee comes off it.
- Running software
Milestones
Each one ends with something you can open and use.
- Yours
Handoff
Code, accounts and a guide to running it.
What you own
The code and the accounts are in your name.
- Source code
- In your repository, from the first commit
- Accounts
- Hosting, domains and services are opened in your name
- Documents
- The scope, the quote and a guide to running it
- After
- Any developer can pick it up. You are not tied to me
Fit
Projects I take, and projects I turn down.
A good fit
- BY HANDA job your team does by hand every week.
- VERSION ONEA product idea that needs a first usable version.
- STALLEDA build that stopped part way.
- ONE PERSONYou want to deal with the person who writes the code.
Questions
What people ask before a build.
What does custom software cost?
It depends on what gets built, so I don't publish a number. The session finds the pieces. The written quote gives one price for a written scope, and you read it before any build starts.
How long does a build take?
The quote lists the milestones in order. I give dates once the scope is written, because a date given before that is a guess.
Do I need a spec before we talk?
No. Tell me what you want in your own words and send whatever exists. Writing the scope is my job.
Who owns the code?
You do. The repository is yours from the first commit, and hosting, domains and paid services are opened in your name.
Do you use AI to write the code?
Yes, every day. I keep passwords and keys away from the AI, and I read and test its work before it reaches you.
Can you finish something another developer started?
Bring the repository to a session. I read it beforehand, and the verdict says whether to repair it or start again, and why.
What happens after handoff?
You have the code, the accounts and a guide, so any developer can take it from there. If you want me to keep working on it, we agree that separately and in writing.
What if an AI feature gets something wrong?
I build for that case. For anything that matters, the software drafts and a person approves. It passes what it should not handle to a person, and it keeps a log you can read.
Open for sessions
Tell me what you want built.
The quote comes after one session.