Your content lives behind their API
Hosted builders own the database, the CMS schema, the SEO settings. Want to migrate? You start from scratch — codebase, content, URLs — none of it leaves with you.
Your code, your DB, your server. Export anytime.
Brand websites, booking systems for salons and studios, corporate sites, B2B portals, marketplaces. Architecture scoped to your case, fixed price after the brief.


Same brochure-website + CMS benchmark, all five platforms. Numbers and features come from real builds, not marketing pages.
My Stack covers landing pages, brand sites, corporate websites and ecommerce — same architecture, scoped per project. WordPress is closest to ownership on a traditional CMS, but pays for it with plugin sprawl and ongoing maintenance.
Most websites have issues with the same five things: ownership, speed, hidden costs, SEO loss on migration, and ads that burn money without sales. Most builders treat them as someone else's problem. I ship around them by default. Scroll through the cards to see how.
Hosted builders own the database, the CMS schema, the SEO settings. Want to migrate? You start from scratch — codebase, content, URLs — none of it leaves with you.
Your code, your DB, your server. Export anytime.
Heavy page builders load in 3+ seconds on mobile. Every extra second cuts conversion by ~7% — and Google demotes slow pages in search results.
Sub-1s page load on real devices, not just the lab.
Plan upgrades, paid apps, extra seats, ecommerce add-ons. The €15/mo plan you started on quietly grows into €600+/yr on the platform alone — before paying anyone to make changes.
Flat hosting €150/yr for existing clients. Source code is yours. No surprise add-ons.
Switching builders typically drops 30–60% of organic traffic for months. Lost URL structures, no redirect map, missing hreflang, broken sitemaps — search engines treat the new site as a stranger.
Full redirect map, hreflang, sitemap and JSON-LD preserved on every migration.
Page builders are fine until your business needs real logic — bookings, B2B pricing, CRM/ERP integrations, custom workflows. Then you're fighting the platform, paying for plugins that half-fit, or told it's simply «not possible».
Architecture built for your case — custom modules, real integrations, logic that fits your business instead of the other way round.
Most custom requests fall into one of these three categories. Each has its own page with a detailed description and cases.
Visual-first sites for fashion, design, lifestyle and creative brands. Editorial layouts, lookbooks, optimized for image-heavy presentations.
Online booking for salons, studios, medical centers, schools. Calendar, reminders, deposit payment, CRM sync.
Multi-page, multi-language sites for businesses. Services, case studies, team, careers, lead forms connected to your CRM. Built to scale.
If your project doesn't fit the usual categories — that's not a problem, it's normal custom work. I take on:
Step by step and transparent. No code is written before the contract is signed, no mockup is drawn before the deposit.
Interactive brief at /brief, ~10–15 min. You describe the business, goals, technical requirements, integrations.
Optional 30-minute call to clarify details. I come back with a written scope, timeline, milestones and a fixed price within 24h.
References, mood, content model — in conversation. No mockups at this stage.
Contract with a legal entity or ENI. 50% is non-refundable if you cancel after the start.
2 mockups of key pages (for projects with UI). After approval — build, integrations, testing. Bi-weekly demos on staging.
Deployment to your VPS or mine. Acceptance by sign-off. Monitoring and backups configured.
B2B service — contract with a legal entity or ENI. Payment in stages, with the option to split for large projects.
A side-by-side comparison of the five ways to build an online store in 2026 — with real Lighthouse scores, 3-year cost projections, and a decision tree.
Why headless storefronts hit Lighthouse 90+ where Shopify and WooCommerce cap at 70 — with the specific techniques behind production scores of 96/100.
A WooCommerce builder's honest take on moving to headless in 2026 — structural differences, real performance numbers, and when not to switch.