Process
How I work
A free consult, a written scope and price before code, tested builds, then a handover. You keep your accounts, hosting and domain.
One engineer, from first message to handover
You work with me directly, and I write the code. This page describes the steps of a project and what you can expect at each one. The same steps apply to a WordPress site, a mobile app or a larger platform.
Step 1: free consult and a one-page recommendation
You tell me about your idea, or about the system you already run, using the contact page or the consult form. I reply with a one-page written recommendation:
- a suggested stack, and why
- the rough build approach and the cost drivers
- the main risks
- what to build first
There is no pitch and no obligation. The plan is yours, even if you decide to build it with someone else.
Step 2: written scope and price before code
If you want me to build it, I write down the scope and the price. The scope lists what is included and what is not. You read it, ask questions, and approve it. I do not start coding before that.
A written scope protects both sides. It keeps the work focused, and it gives us a clear reference if a new idea comes up later. New ideas are welcome, and they become a change to the scope with their own price.
Step 3: build with milestones and tested releases
I build in milestones, so you see real progress and not a long silence. Each release is tested before it goes out. For risky changes I take a backup first, verify the result after the release, and keep a way back to the previous version.
Step 4: handover
The project ends with a handover, so you can run what I built.
- The tested release, live or ready to go live.
- A rollback plan, so a bad release can be undone.
- Documentation that the next developer, or you, can follow.
- Your accounts, hosting and domain stay with you. I work inside them with the access you give me, and nothing is locked to me.
Ways to work together
Fixed scope. One project, one written scope, one price. This fits a business site, a plugin, an app or a feature with a clear end.
Part-time support. Ongoing help on an existing system: fixes, updates, small features and maintenance. The arrangement is agreed per client after the consult.
Rates are on request. After the consult I give you a price for the scope in writing. If you prefer a platform with buyer protection, you can also order through Fiverr or Contra.
Questions people ask
What do I get from the free consult?
A one-page written recommendation. It names a suggested stack and why, the rough build approach and cost drivers, the main risks, and what to build first. There is no obligation, and you keep the plan whoever builds it.
Do I see the price before you start?
Yes. I write down the scope and the price, and you approve both before I write any code.
Who owns the accounts, hosting and domain?
You do. Your accounts, hosting and domain stay with you, and I work inside them with the access you give me.
Do you guarantee search rankings, traffic or app downloads?
No. I do not guarantee rankings, traffic, downloads or store approval. Search engines decide rankings, and Apple and Google decide whether an app is approved. I build and prepare the work properly, and I say this before we start.
What happens if a release goes wrong?
Every release has a rollback plan. I take a backup before a risky change, check the result, and can go back to the previous version.
Start with the consult
To see what I build, open the [demo showcase](/demo/) or read [about me](/about/). When you are ready, tell me about your project.
Book the free consult

