Skip to content
Taking 2 projects at a timeBook a 20-min call
Book a 20-min callhello@theweb0.com

FAQ

The answers, before the call.

40 questions people ask before the call, in 7 groups. Write yours on the line and the pen ticks the answers that fit.

The short version

Fixed price
From €8k
Week one
€3,000, refundable
At a time
2 projects
First call
20 min, free

Price

A fixed price for a fixed scope, agreed in writing before I start. A landing page starts at €8k, a website at €16k, and every other scope has its own starting price on the pricing page. Ongoing work is a monthly retainer, from €7.5k a month. Prices excl. VAT.

See the prices

Because the scope sets the price. “From” is where a scope starts. After our call I put the scope and the exact figure in writing, before any work starts. Once it’s in writing, the number doesn’t move.

Then it costs me, not you. The price on the quote is the price. If I underestimated, that is my cost.

In stages. Week one is a fixed fee of €3,000, counted toward the project. After that you pay per stage and can stop after any stage. The quote lists every stage with its amount, and invoices are due within 7 days.

Week one is the first week of the project, sold as its own sprint: a fixed fee of €3,000, counted toward the project. Stop at the end of it and I refund it in full. The work from that week stays with me.

Week one, day by day

As many as it takes inside the agreed scope. Changes inside the agreed scope of a stage are included until you sign it off. A change that adds scope gets a price first, and you decide before I build it.

Yes. Marathon is a monthly retainer for ongoing design and development, from €7.5k a month. It runs month to month and you can pause it for up to 45 days.

How the retainer works

I can’t promise a return, and I’d be wary of anyone who does. What I can do is show the arithmetic. The payback calculator runs on your own numbers, and every case on the work page shows its arithmetic next to the figure.

Run your payback

Time

A landing page takes 1–2 weeks, a website 3–5 weeks, a product or MVP 4–8 weeks. Every scope has its usual weeks on the pricing page. If yours needs longer, you’ll know before we start, not halfway through.

See where the dates would land

That depends on when one of my two slots frees up. I take two projects at a time, so I won’t squeeze yours in beside a third. On the call you get a real start date, not a vague “soon”.

In week one. You see real designs within days of starting, not a strategy deck, and from then on you review the work on a live preview link every week.

Tell me early. I can shape the scope around your date and keep it realistic. If the date can’t be met, I’ll say so on the call, before you’ve paid anything.

Less than managing a team. I need one person who can say yes, notes on the preview link within a day or two, and access to what already exists: brand files, code, accounts.

Working with one person

Yes. You talk to me and I do the design and the code. No account managers, no handoffs, no juniors learning on your project.

Yes. I’m a design engineer at Supabase and I take web0 projects next to it. That’s why there are two slots and not ten. If your dates need more of me than I have, I’ll tell you on the call.

You hear it from me. Holidays are planned well ahead, so nothing launches the day I’m gone. If I’m ill you hear it that morning: the dates move with me, and a fixed price stays fixed. From week two your code and design files live in your accounts, so the project never depends on my laptop.

When I’m away or ill

You’d keep everything made so far: from week two it lives in your accounts. Any developer can pick it up from there.

Slack for day to day, short updates, and a call when something is faster to show than to type. I reply within one working day, usually the same day.

Yes. I can lead, co-design, or build alongside your team, and I’ll match your tools and workflows.

Yes. The quotes on the work page carry real names and companies. If you’d like to speak to one of them before you sign, say so on the call and I’ll ask them.

See the work

Someone with an idea nobody has paid for yet. Test it in a no-code builder first and come back when it earns. And anyone who needs ten people on site. I’m one person, on purpose.

AI

Yes, to move faster: research, first passes and boilerplate code. I don’t hand you its first draft. Every design decision and every line that ships goes through me.

It is cheaper and faster than it used to be. That’s how one person ships a website in 3–5 weeks. What you pay for is the judgment: what to build, what to cut, and catching the output that looks right and isn’t. The price is fixed for the result, not for the hours.

For testing an idea, a builder is the cheapest route, and I’ll say so on the call. What it won’t give you is the judgment: which page matters, what to leave out, and the part that looks almost right but isn’t. That part is what I’m paid for.

Not without you agreeing to it. I use AI tools on my own drafts, research and code. Confidential client material stays out of them unless we’ve agreed otherwise in writing, and I can sign an NDA that says so.

No. Every design decision is mine. This site is the sample, and it was drawn, not generated.

Ownership

You do, once it’s paid. Week one’s work becomes yours when you carry on; stop in week one and it stays with me, and you get the fee back. After that, each stage’s work and its IP are yours once that stage is paid, and I keep no rights to them. I treat your business information as confidential and can sign an NDA.

Read the terms

In your accounts from the day you carry on past week one: your repository, your hosting, your domain, your design files. I work inside them, so nothing has to be handed over at the end.

Everything from the stages you’ve paid for. The one exception is week one: stop there and I refund the fee in full, and the work from that week stays with me.

Figma for design. Webflow, Framer, Next.js, React or Expo for the build. If your team already has a stack, I work in yours.

After launch

I ship clean files and documented builds, and I walk your team through what was delivered.

Yes. A website comes with a CMS and a handover, so your team changes text and pages without waiting for me.

Your choice. Your team can take it over, since everything is documented and already in your accounts. Or I stay on with a Marathon retainer for improvements, new features and support, from €7.5k a month.

Health data

Yes. I built a multi-clinic platform with patient records. It is private work, so the site shows it with screens recreated for confidentiality and no public link.

See the clinic platform

Your clinic. I build the software. Your clinic stays the data controller, and we sign a data processing agreement before I see real patient data.

Hosted in an EU region you choose, on providers that publish their security attestations. Access by role, a log of who opened which record, and encryption in transit and at rest.

No, and I won’t claim a certificate I don’t hold. What you get is the paperwork a clinic needs from its builder: a data processing agreement and the data map for your DPIA. The assessment is yours to sign. I haven’t done US patient-data work yet. If you need a BAA, raise it on the call and we settle it before anything else.

Whether a feature makes software a medical device depends on what it is meant to do. I check that with you feature by feature, before I build it, and with a regulatory adviser when it is close.

AI features are labelled as AI, a person decides, and they make no clinical calls.

Built to WCAG 2.2 AA and tested with a keyboard and a screen reader.

More on health projects

Ask me the one I missed.