Get a website your team can actually scale.
Most websites look right after launch. Six months later, new pages drift off-brand, publishing slows down, and the site starts quietly accumulating decisions nobody documented.
My Website System is built to prevent that. Brand strategy, UX/UI design, and Webflow development — combined into a clear, modular structure, reusable components, and governance your team can operate autonomously.
Typically 5-7 weeks.
Projects start at €7,000.
Strategy → Design → Webflow → Handover.
A site is a collection of pages. A system is the structure behind them — the components, templates, rules, and CMS architecture that make every future page build faster and more consistent than the last.
Before: Publishing a new page means starting from scratch, eyeballing previous designs, and hoping nothing looks off.
After: The patterns are already defined. Your team works within a structure that keeps things consistent by default.
The handover is part of the deliverable — not an afterthought. Documentation, usage guidance, and a walkthrough so your team understands not just what was built, but how to extend it without slowly breaking it.
What’s included: From strategic foundation to launch.
A clear decision-making frame for the project: brand positioning refinement, brand tonality and target persona definition, messaging structure, page goals, and information architecture — so every design and build decision has a reason behind it.
Reusable sections, components, layouts, and responsive design rules. Not isolated page designs — a visual system that creates consistency by default as the site grows. Handover via Figma.
A clean, structured Webflow build with a modular component system, scalable page patterns, and a CMS architecture your team can extend without introducing technical debt.
Collections, templates, content relationships, and an editor experience anyone on your team can use without prior experience — structured for reuse, not patchwork.
Key landing pages and reusable page structures built for future expansion — not one-off designs that can't be replicated without starting over.
Documentation, usage rules, and a recorded walkthrough. Your team understands what was built, why it was built that way, and how to extend it safely.
Optional add-ons
- Copywriting for cornerstone pages
- Advanced animations and interactions
- Multi-language setup
- Publishing process development with your team
- Ongoing iteration support after launch
Not in scope by default
- Full copywriting for large sites
- Full production of visual assets
- Custom app development
- SEO campaign content production
- Long-term site management beyond agreed support
Brand strategy alignment
We define what the site actually needs to do — business goals, brand strategy, visual identity, target audience, constraints, and what success looks like. This becomes the decision-making frame for everything that follows, and it's what prevents scope creep and late-stage pivots.
Map the system
I structure the information architecture, identify the key page types and messaging structure, and define the component logic and CMS foundation that will support growth. You see the structure before any design starts.
Design for reuse
Instead of designing isolated pages, I build a modular UX/UI system — layouts, components, and patterns that create consistency by default. Every element is designed with future pages in mind.
Build in Webflow
The system is implemented in Webflow with scalability and maintainability as primary constraints — so the site works well both at launch and after handover, when your team is operating it independently.
Handover and governance
You receive documentation, usage guidance, and a walkthrough of how to extend the system without slowly breaking it. This is not a nice-to-have — it's a core deliverable enabling your team.
Expand if useful
If there's appetite after launch, we can continue with a focused improvement phase — refining, extending, and improving based on real use data rather than pre-launch assumptions.
Frequently asked.
Do you offer only strategy, only design, or only Webflow development?
Yes — we can scope those separately. The strongest results usually come when all three are considered together as one system, but if you have a specific gap, reach out and we'll find the right scope.
Do you work with existing brand guidelines?
Yes. I can work within an existing identity, refine what's already there, or help translate it into a scalable digital system. You don't need to start from scratch.
What if we already have a site and don't want a full rebuild?
That depends on the foundation. In some cases, the better route is to improve and restructure what exists rather than rebuild. If you're unsure, an audit is the right starting point — it gives you a clear verdict before you commit to anything larger.
Will our team be able to edit and extend the site after handover?
Yes — that's a core goal of the process. The governance documentation and handover walkthrough are specifically designed to leave your team with a system they can operate and extend independently.
How confident can we be in the timeline?
Most projects run 5–7 weeks. Larger or more complex scopes may run longer — and we'll map that out clearly before you commit, not after. Timeline depends primarily on page count, CMS complexity, and how quickly feedback rounds move.
Do you write all the website copy?
Not by default. I can support messaging structure, refine copy you provide, and advise on hierarchy and clarity. Full copywriting for large sites can be scoped as an add-on.
Do you offer support after launch?
Yes. Ongoing support can be scoped as focused implementation help or a lighter iteration retainer — depending on what your team needs after launch.