How I work
how i work
On getting started, finishing and handing over, and what to expect from one builder.
Getting started
start small, start for real
No months of prep work. We pick a bounded piece of work that can go live fast, and that's the first milestone: working software in your environment. After that we decide step by step whether and how to continue.
Expectations
one person, not a team
You get no account manager, no junior and no layer in between; you get me. That means focus and speed, but also honesty: I take on no more than I can finish myself, and I say no when something fits someone else better.
Handover
systems that carry on without me
Everything I build ships with a living knowledge base: documentation that people and AI can work from. Your team or your next partner can continue without calling me. I train your team to run the maintenance themselves and the work folders are transferable. The exit is built in, not a risk.
Tools
what I work with
SAP Customer Experience, Salesforce, monday.com, Supabase, Make, Claude, Playwright and my own fikst. The process picks the tool, not the other way around.
Questions
honest answers
- What company size do you work for?
- From service SMBs to enterprise. The method scales: for an installation company I build in days, at a corporate I plug into the programs already running.
- Do you do maintenance too?
- I build systems that need little maintenance, and I stay around when something gets stuck. Ongoing maintenance only when it's really needed; I'd rather make your team self-sufficient.
- How fast can something go live?
- The first working version is up in days to weeks, not months. That's possible because I work with AI agents and a fixed build method, and because I start small.
- How does pricing work?
- Fixed agreements up front per piece of work, no surprises afterwards. No open-ended hourly billing: you know the cost before I start.
- Do you work on site?
- Hybrid. For workshops and go-lives I come over; building happens wherever the work moves fastest.
- Can I run it myself afterwards?
- Yes, that's the goal. The knowledge base and the handover are part of every delivery; you're never dependent on me to move on.
- And if you're not around for a while?
- Then the work doesn't stall. Every project ships with a living knowledge base that people and AI both work from, and I hand it over to you. I train your team to run the maintenance themselves, and the complete work folders are transferable: someone else picks it up without months of archaeology first. Whether I'm heads-down on something else or away for a bit, little changes for you. The handover is built in.