E-commerce development. But first: do you actually need custom?
If a ten-product shop is all you need, there are packages for a few hundred euros and you're right to take one — I'll tell you on the first call. I matter when the store has to carry a real catalog, different price lists, and orders that must land in your ERP without anyone retyping them.
30 minutes · Price written before we start · Reply within 24 hours
When an e-commerce store stops being “a website”.
- Orders come in through the store and then somebody retypes them into the ERP. Every day.
- The catalog arrives from suppliers in twenty different files, each with its own rules, and someone writes the product pages by hand.
- Stock levels on the site aren't the real ones, so every so often you sell something you don't have.
- You have a store somebody else built, it half works, and whoever built it stopped answering.
- You want to sell B2B too — per-customer price lists, bulk orders, deferred payment — and the platform wasn't made for that.
- The store exists, but every change means opening a ticket and waiting.
The common thread isn't the design: it's that the data lives in two places and a person keeps them in sync by hand. That is software work, and a nicer theme doesn't fix it.
What it costs, said up front.
These are entry thresholds, not final estimates: scope is agreed on the call and the exact price is written down before we start. All + VAT, one-off, no recurring fee.
Single scoped job
One change, one integration, one thing that's blocking you.
- A connection that isn't there (carrier, invoicing, marketplace)
- A catalog import that needs fixing
- A bug nobody can close
- Quoted in writing before anything starts
Audit of your existing store
You already have a store and want to know what's really inside it.
- Code, integrations, data, access: who holds the keys to what
- What can be saved and what has to be rebuilt, with costs next to it
- Written report in 2-3 days, yours either way
- If the conclusion is “leave it alone, it's fine”, I write that
Custom e-commerce
A new store, built around your catalog and your process.
- Catalog, variants, payments, shipping
- Catalog imported from the files you already have, not retyped
- Your code and your data, in Europe. No per-user fees
- You run it: products, orders and prices are yours to change
E-commerce wired to your ERP
When the store has to talk to what you already run.
- Orders that land in the ERP on their own
- Real stock levels, synced both ways
- Per-customer price lists, B2B, electronic invoicing
- Migration from an existing store without stopping sales
There is no deadline and no struck-through price: if a promotion always ends on Friday and starts again on Monday, it was never a promotion. If the budget doesn't fit, we cut scope and start with the piece that earns you money first — that part is genuinely negotiable.
When I'm not the right person.
If a ten-product shop is all you need
There are packages for a few hundred euros that do exactly that, and you're right to take one. A small clean catalog, standard payments, no integrations: you don't need someone like me. If that's your case I'll say so on the call, for free, and you'll have saved yourself a sales pitch.
If you're shopping for the lowest quote
It won't be me. The three-figure offers are real and they work, but the margin almost always sits after the sale: renewals, extras, maintenance, the SEO package. Here the price is the one written before we start, and it ends there.
If the problem is that nobody visits
A better-built store doesn't bring traffic on its own. If the shop works and the problem is that nobody finds it, the work is advertising and content, not code — and that isn't what I sell.
Four steps, and you sell as early as possible.
A 30-minute call
You tell me what you sell and how you work now. If a package is enough, I say so there.
A written quote
What's in it, what isn't, what it costs and how long. Before we start, not after.
The catalog first
It's always the part that gets underestimated and sinks projects. So it goes first.
Live, then the integrations
You start selling as early as possible. The ERP links come after, on a live store.
The audit step uses the same method as the technical audit. If what's squeezing you sits upstream of the store, the work is on the custom ERP; and if the store exists but the supplier vanished, start with unblocking the project.
The questions I get about e-commerce.
What does building an e-commerce site cost?
A custom store starts at €4,500 + VAT; if it has to integrate with your ERP, it starts at €9,000. These are entry thresholds, not estimates: scope is agreed on the call and the exact price is written down before anything starts. A single scoped job on a store you already have starts at €500 instead.
I've seen packages at €500-600. Why the difference?
Because they're two different products, and that should be said plainly. At that price you're buying a store on a ready-made theme, with a small catalog and no integrations — and for a great many businesses that's exactly right. What I do matters when the store has to carry a real catalog, different price lists, synced stock and orders that land in the ERP by themselves. If your case is the first one, take the package: I'll be the one telling you.
Which platform do you build on?
It depends on what you sell and what you already run. I have no platform to push and I take commission from nobody: if the right answer is an existing platform, we use it and you spend less. Custom is about your process, not about rebuilding things that already exist and work.
Are there monthly fees?
Not from me: you pay once and the store is yours, code and data included. What remains is what you'd pay anyway — hosting, domain, any platform licence and payment processing fees — and I tell you those up front rather than burying them inside a package.
We already have a store and it works badly. Can it be saved?
Almost always yes, and either way you look before deciding. The €1,500 audit is exactly for that: what's inside, who has the access, what can be saved and what has to be rebuilt, with the costs next to it. The report is yours regardless, even if you then do the work with someone else.
Who actually builds it?
I do. The same person who decides how to do it writes the code and answers when something breaks. No account manager, no handover to a junior after signing. It's also why I don't take on more projects than I can actually follow.
Six million companies, one million sites, a ten-day run. Same craft as a product catalog: normalizing inconsistent sources without publishing mistakes.
Not the quote — the technical decisions taken before a line of code is written. Which choices contain costs and which multiply them.
Before you sign, let's talk.
30 free minutes: you tell me what you sell and how you work today. If a few-hundred-euro package is all you need, I'll say so and point you to one. If it's real work, you leave the call with a price and a timeline.
30 minutes · No commitment · Reply within 24 hours