AI & automationFor small businesses and founders who need software that doesn’t exist yet
Custom tools and first versions, built to be used
A small internal tool for your business, or the first version of a product: built around one job, live in accounts you own, with a person approving each release.
First version Eight to twelve weeks
Not sure where to start? AI consulting
What a first version includes
- The jobThe one thing the tool does, working end to end.
- AccountsSign-in, if it needs it.
- DataA real database, not a spreadsheet.
- HostingLive on your domain, in accounts you own.
- ChecksAutomated tests, and my sign-off before each release.
- HandoverThe code, and a guide to running it.
You get a working tool, the code, and a list of what to build next.
What you get
- One job, working end to end
- Sign-in and accounts, if it needs them
- Your data in a real database
- Hosting in accounts you own
- Tests and release checks
- The code and a handover guide
Best fit: internal tools, web tools, and focused products. Not a fit: safety-critical, medical, or payments infrastructure.
How it works
Scope
What’s in the first version, in writing.
Build
You see working software every week.
Test
Real users try it before launch.
Launch
Live, in your accounts, with a handover.
Where I’ve done this
Live product
Pathway Builder
Software I built so community-college teams can map programs, courses, and competencies into routes they can see, from short-term training to a degree. Right now I’m adding a place to weigh new program ideas with evidence.
Read the story
Where we start
First version
Timeline Eight to twelve weeks
Included
- The scoped first version, working end to end
- A weekly build you can try
- Hosting and a database in accounts you own
- Automated tests and release checks
- The code and a handover guide
Not included
- Safety-critical, medical, or payments infrastructure
- Native apps for both platforms at once
- Ongoing product management
Not sure where to start? AI consulting
Questions people ask
What counts as a small tool?
A scheduling board, a quote builder, an intake form that feeds a dashboard, a customer portal: one job your spreadsheet or inbox does badly, built properly.
Do you write the code yourself?
I design the product and direct AI coding agents to build it, under a release process where I approve everything before it ships.
What stack do you build in?
Next.js, TypeScript, and Postgres, hosted on Vercel. I’ll say so when a no-code tool would do the job for less.
Who owns the code?
You do: the code, the accounts, and the data. If we part ways, another developer can pick it up.
What happens after launch?
You get a list of what to build next, in order. I can keep building, or hand over to your own developer.