How I work
From the first call to a system your team uses every day
No departments or project managers in the middle. You talk directly to the person building it, see progress every week or two, and end up with a system you fully own.
The steps
- 01
Intro call
A 30–60 minute call: what the business does, what hurts today, and what success looks like. Already on this call I'll tell you whether and how I'd build it — and whether a ready-made product would serve you better.
What you get: A clear direction and a first estimate of scope
- 02
Spec
We map the process, roles and screens together, and write a short, clear document: what's in, what's out, and what goes into the first version.
What you get: A spec, a screen list and a proper quote
- 03
Design and prototype
Before building, you see how it will look. Key screens or a clickable prototype, so we can change direction while it's still cheap.
What you get: Approved designs for the main screens
- 04
Build in stages
Short sprints. At the end of each one there's a live version you can log into, try and comment on. No surprises at the end.
What you get: A live version updated every week or two
- 05
Launch and rollout
Data migration, go-live and team training. In the first weeks I'm available for quick fixes and questions.
What you get: A live system and a team that knows how to use it
- 06
Maintenance and improvement
After launch the real insights arrive. We continue with ongoing support, fixes and new features — as you need them.
What you get: A system that keeps improving with the business
My principles
Work directly
You talk to the person writing the code. No broken telephone.
Small and working before big and perfect
A first version of the core process, then expand.
Transparency
A live version all along, and regular updates on what's done and what's next.
Simple to use
Screens are built for the people who use them daily, not for a presentation.
Security from day one
Server-enforced permissions, secrets outside the code, and security headers — not an afterthought.
No lock-in
The code and accounts are yours. Continue with me, or with any other developer.
What stays with you
- The full source code, in a repository you own
- Hosting, database and service accounts — in your name
- Your data, exportable at any time
- Short documentation: how the system is built and how to run it
Contact
Have a system or app in mind? Let's talk.
Tell me what your team needs and I'll tell you how I'd build it. Call, message me on WhatsApp, or send an email.