Most common questions

Every project starts with an obligation-free 30-minute video call. Tell me what you have in mind, I ask questions, and by the end you’ll know whether I’m the right person and roughly what it would cost. Nothing is bought or committed on that call, and there’s nothing to prepare.

No. For a website or a store, the 30-minute call is usually enough to scope the work and quote it. For AI tools, automation, MCP servers and internal tools it usually isn’t, because the thing you’re describing hasn’t been built yet and nobody has mapped what it touches. That’s what steps 1 and 2 exist for, and they’re the only way either of us can commit to a fixed number.

The audit decides whether to spend anything at all. The plan decides what to spend it on. An audit answers “what’s possibly wrong, and what’s worth doing about it”, and hands you findings ranked by impact against effort plus a roadmap. A plan answers “what exactly are we building, and what does each part cost”, and hands you an architecture, a design, a scope and a priced build plan. Different questions, different deliverables.

Yes. Every plan is written so that someone who has never spoken to me could build from it.

The price is the price. If the work takes me longer than I thought, that’s my problem, not yours. That’s what fixed-price means, and it’s the reason scope gets agreed carefully before anything starts.

No. All prices on the site exclude VAT.

Yes, against a build package over 5,000 €, booked within 30 days of the previous step being delivered. So if the audit leads to a plan first, the clock runs from the plan, and taking time to specify things properly doesn’t cost you the credit.

No. The audit is a step that works out whether there’s a job worth doing. A plan is a deliverable you own and can hand to anyone, including a different developer. It has value whether or not I build the thing, and that’s the whole argument for being able to buy it on its own.

Set in each contract, because they depend on the size and length of the project. Typically it’s instalments: a share at the start, a share at agreed milestones, and the balance on delivery. Invoicing is through Stripe, 14 days net. You’ll have the full schedule in writing before you commit to anything.

I can’t tell you before I know what the build is. A website I can estimate on the call. An AI automation or an MCP server I can’t, because the answer depends on what it has to talk to and what condition that’s in, which is exactly what the audit and the plan exist to find out. What I can commit to is the sequence: you’ll know what it costs and when it lands before you sign anything or pay anything.

I handle the vast majority of the work myself: design, code, marketing, and sales. There are no account managers here. If I need to bring in trusted outside help or a subcontractor to speed up the schedule or save you money, I’ll always tell you upfront. Even then, you never have to deal with them: you only ever communicate directly with me, which means nothing gets lost in a handover.

Every project includes 30 days of launch support at no cost: bugs, questions and small adjustments. After that it’s up to you. You can buy a block of prepaid development days, an annual care package, or a quarterly review, and use them when you actually need them. No monthly retainer and no card charged automatically in the background.

Because most retainers bill for availability rather than work, and both sides end up resenting it: the client for paying in a quiet month, me for the month where the work far exceeds the fee. Prepaid days solve the same problem. You buy the time, you use it when you need it, and nothing expires quietly in the background.

By default you supply the copy, images and product data. I can write it, and that’s priced separately, per page and by how much work the page actually is. A contact page and a long cornerstone sales page are not the same job.

You do. The website, the store, the tool, the automation, the assistant, including the source code I wrote for you. What I don’t transfer is what was never mine to transfer: third-party frameworks, libraries and platforms keep their own licences, and those are the reason it can be built at that price at all.

Yes. That’s what owning it means, and it’s why plans and codebases are written to be handed over. Nothing I build depends on me staying involved.

You do, on your own accounts, in your own name. I don’t resell anything and I don’t bill anything through. I’ll tell you exactly what you need and which provider I’d choose, and set it up with you, and then you pay them directly. It’s cheaper, and more importantly nothing about your business sits inside an account I control.

Mostly Next.js, React and TypeScript on the web side, Python and Node for automation and AI work, and whatever the actual problem calls for beyond that. I don’t sell a stack, I pick one and I’ll tell you why on the call.

Yes, as a tool, the same way I use an editor or a compiler. It makes some parts much faster and it doesn’t make the thinking, the architecture or the design decisions for me. What you’re paying for is the judgement about what to build and how, which is the part that doesn’t come out of a prompt.