001
Systems & apps
Member areas, dashboards, databases and small apps, built faster with AI.
- Memberships
- Profiles
- Dashboards
- Databases
- Automation
Member areas, user profiles, dashboards, a database that holds your records properly, the automation of a job somebody does by hand every Monday. The things a website cannot do on its own.
I build these with AI in the loop, and that is not a slogan. It means a working prototype in days instead of months, so you get to try the thing before you commit to it, and a budget that used to buy a brochure site now buys something that does work.
What I help you with
Member areas and profiles
A place your members log in to. Content for them only, a profile they keep up to date themselves, and renewals that take care of themselves.
Dashboards and databases
Your records in one place, structured so they are still useful when there are thousands of them, behind a screen that shows you what is happening and lets you act on it.
Automations
The repetitive part of your week handed to software. Forms that file themselves, documents that generate, reminders that go out on their own.
Small apps
A tool that does one thing well, on a phone or in a browser, for your team or your customers.
How it runs
- 01Meeting & briefYou tell me what the thing should do. A spec is welcome but not expected, because working that out is the first stage rather than a prerequisite.
- 02Discovery & researchI look at how the job is done now and what it already runs on. This is where we find out whether your existing tools have a way in.
- 03Ideation & designA prototype you can click, early and rough, so we are arguing about the real thing rather than about a description of it.
- 04Presentation & refinementYou use it, you tell me where it fights you, and I fix that before it goes anywhere near your clients.
- 05DeliveryIt goes live under your accounts, with documentation, and I show you how to run it.
Every project includes
- A prototype you can click before the real build starts.
- Your code in your repository, under your accounts.
- Documentation, and a session where I show you how it runs.
My toolbox
Claude Code
How a prototype arrives in days instead of months. I design and decide, it types, and you try the real thing early.
Supabase
Log-ins, user profiles and the database behind them, without building any of that from scratch. It is what Bito Chess runs on.
Stripe
Payments and subscriptions, handled by the people who do it properly. Card details never touch your system or mine.
Cloudflare
Hosting, domains and the bits in between. Cheap to run, quick everywhere, and it scales without a conversation.
Questions clients ask
I have an idea but no spec. Can we still start?
Yes, and that is the normal starting point. Working out what it should do is the first stage of the project, not something you have to arrive with.
What does “built with AI” actually mean?
That I reach a working prototype in days rather than weeks, so you can try it before committing. The design decisions are still mine and every line is still reviewed.
Who owns it, and could someone else take it over?
You own it. It lives in your repository, under your accounts, with documentation, so you are not tied to me.
Will it work with what we already use?
Usually. Most tools have a way in, and checking that yours does is part of the first stage, before anything is built.
How much does a system cost?
There is no useful answer before it is scoped. One conversation is normally enough for me to tell you roughly where it lands.
Always included
I teach you to run it
A system nobody can operate is not finished. I teach you to run it, and leave the documentation behind.
How a quote happens
Every project is quoted individually.
- 01We talk, on a call or in a meeting, and you tell me about the project.
- 02I write it up: what I’d build, in what order, and what each part costs.
- 03A fixed price per phase, so you know what the next step costs before it starts.