01
Small fix or rescue task
For focused bugs, broken pages, cleanup tasks, or smaller pieces of rescue work.
EUR 60-180
Pricing
This page exists so you can judge commercial fit before reaching out. These are the prices I quote most often. If the work is still unclear, it starts with a smaller paid review.
Common ranges
These numbers are for work that is already clear enough to scope.
Payment and support rules
Smaller first steps are prepaid.
Build work usually starts with a deposit.
Ongoing maintenance stays scoped to systems I already know.
New feature work is quoted separately from maintenance.
01
Small fix or rescue task
For focused bugs, broken pages, cleanup tasks, or smaller pieces of rescue work.
EUR 60-180
02
Working session or diagnostic
For planning, review, rescue triage, training, or the first paid step when the real scope is still hidden.
EUR 60-150
03
Astro landing page
A smaller launch-focused build, usually from existing copy or a clear scope.
EUR 300-900
04
Small business site or rebuild
For a fuller site, migration, or rebuild with multiple pages, content, and deployment.
EUR 900-2,000
05
Automation setup
n8n flows, AI-assisted helpers, internal tools, or integrations that replace repeated manual work.
EUR 300-1,500
06
Monthly maintenance
For updates, small improvements, monitoring, and cleanup on systems I already know well enough to support.
EUR 60-250/month
How billing works
I keep public pricing as ranges because most buyers care about total cost, not a hidden timer.
When the scope is clear, I prefer fixed scope or a defined task band.
When the system needs mapping first, I start with a paid diagnostic.
Calls, research, planning, debugging, documentation, and coordination are part of the work.
Questions
01
Sometimes for smaller tasks or existing clients. Publicly I show ranges because total cost is usually more useful than a bare hourly number.
02
I suggest a diagnostic so the job can be priced instead of guessed.
03
Inherited ecommerce, payment gateways, multi-service hosting, and anything where the technical risk is still not visible enough to price cleanly.
04
Yes, but mainly for systems I built or already stabilized. It stays limited and clearly scoped.
Next step
Share the goal, the timing, and the budget boundary. I will tell you whether it fits these price bands or needs a smaller first step.
live chat
online