When an off-the-shelf solution doesn't exist or holds you back more than it helps.
Internal systems, portals with user accounts, SaaS products and mobile apps. I build them from scratch, in phases, with you there every week.
Do you recognise yourself in any of these?
Your process runs through a spreadsheet, email and three people
Data gets retyped by hand, someone is always working on an old version, and nobody knows where the current state lives. That isn't a problem a new spreadsheet solves.
The tools you use don't talk to each other
Each does its own job well, but between them stands a person copying from one into the other. That person is the most expensive part of the system.
You have a product idea but no technical co-founder
You need someone who will say what the smallest version worth building is, and then build it, instead of building everything at once.
The system has outgrown what it started on
It worked while there were three of you. Now it falls over under traffic, and every change takes a week and a prayer.
What exactly you get.
Concrete, with no "and much more". If something on the list isn't for you, it leaves the scope and it leaves the price.
- Written specification and a proposed architecture
- Clickable prototype before the first line of code
- Web application (Next.js, Node.js, PostgreSQL)
- Mobile app for iOS and Android (React Native)
- User accounts, roles and access rights
- Integrations with the tools and systems you already run
- Repository, documentation and every access credential at handover
The process for this service.
At every step you know what we're doing, why we're doing it and what comes next.
Intro call
30 min · no charge
We talk about what you're building, where you are now and where you're going. By the end you know whether this is work for me at all, and if it isn't, I'll tell you who to call.
Discovery and specification
We go deeper: users, processes, integrations and risks. The output is a written specification, a proposed architecture, a phase plan and a fixed proposal, along with the Project plan, the Contract and an NDA. That document is yours even if we don't work together after it.
Design and prototype
A clickable prototype before a single line of code is written. Changing your mind here costs an hour. Three weeks later it costs three weeks.
Building in weekly cycles
Every week you see the progress on a live version and tell me what's off. No three months of silence followed by a big reveal at the end.
Testing and launch
Functionality, speed, security, SEO and analytics. Handover includes every access credential, the documentation and a recorded walkthrough, so the site is yours and not mine.
After launch
We measure what works, fix what doesn't and keep building. A support package with a fixed number of hours, or work as needed, whichever suits you.
You don't have to take my word for it. Here's what is already live.
Investment
Payment runs in phases, tied to deliverables, not in full up front. Scope, deadline and price are set in the contract before anything starts.
The things people usually ask at the third meeting.
From three months up, depending on scope. An MVP with a clearly bounded scope usually fits into three or four months. The exact deadline comes with the fixed proposal after discovery, not before it.
React Native, so one codebase for iOS and Android. For most business apps that's half the price and half the maintenance time at the same quality of experience. If a project genuinely needs native, I'll tell you and point you on rather than charge for it.
For most people a good web app that also works on a phone is enough. A mobile app pays off when you need push notifications, offline use, the camera or location. If you need none of those, I'll tell you not to build an app.
I plan for it, which is why the project runs in phases. Smaller changes fit inside the agreed scope. Larger ones get a separate estimate before I start on them, so you decide whether it happens now, later or never.
You do. The repository, the database, the access credentials and the documentation go to you at handover. If you carry on with someone else tomorrow, they pick up where it stopped.
Me, if you want, through a support package with a fixed number of hours a month. If you want someone else or your own team to take it over, the handover includes documentation written for that situation, not for me.
Do you actually need something else?
If you have an idea worth doing properly, the first step is a 30 minute conversation.
No proposal and no pressure. You tell me what you're building, I ask the questions nobody has asked you yet, and by the end you know whether it's feasible, roughly what it costs and what the next step is. Whether or not we end up working together.
