01
Site architecture
Sitemap, page types and content model, before anyone opens a design tool.
You get: an architecture your developers can build.
The thinking, without the build.
For teams with their own developers who need the thinking, not the build. Site architecture, UX direction, conversion strategy, and a roadmap your team can follow.
Is this for you
For teams that build in house.
You have developers or an agency, but nobody owns the plan.
You’re planning a redesign and want it right the first time.
Your design team needs a process, not just more designers.
Probably not for you if you want someone to build the whole site. Have a look at the website service instead.
What’s included
Thinking you can build from.
I lead production and train designers at Webtec. The same systems that keep quality high there can work for your team.
02
UX direction
Flows, wireframes and design reviews for your team’s work.
You get: feedback that’s specific and kind.
03
Conversion strategy
What each page should get people to do, and how to measure it.
You get: a conversion plan with goals.
04
Roadmap
What to build first, what can wait, and who owns each part.
You get: a roadmap your team works from.
05
Design team training
Training for your designers on UX, structure and quality. I’ve trained and guided over 30 at Webtec.
You get: sessions and material your team keeps.
06
Production and QA process
Checklists and review steps that catch problems before clients do.
You get: a QA system set up for your team.
07
Design to build handoff
Rules so what gets built in WordPress matches what was designed in Figma.
You get: handoff guidelines.
08
Platform advice
WordPress, Elementor, JetEngine or something else: what fits what you need.
You get: a recommendation with the reasons.
09
Workshops
A working session with your team to agree goals and priorities.
You get: decisions written down.
A typical roadmap
Six workstreams. One plan.
Each bar is a part of the work. Pick one to see what happens in it.
A typical shape. The real roadmap and its timeline come after the first call.
How it runs
Plan with you. Build with them.
- Free call
Your team, your site, and what isn’t working.
- Proposal
What I’ll deliver, by when, at a fixed price or by the hour.
- Work sessions
Regular sessions with your team, with notes after each.
- Handoff
The roadmap and guidelines, owned by your team.
Price
By the hour, or fixed.
Hourly for ongoing advice. A fixed price when the work has a clear end, like an architecture or a roadmap.
Hourly
For ongoing advice and reviews.
€75an hour
- Design and UX reviews
- Questions answered in writing
- Book hours as you need them
Fixed project
Most askedFor work with a clear end.
From €1,900per project
- Architecture, roadmap or training
- Scope and price agreed up front
- Handoff session with your team
Questions
Before you book.
Do you work with our agency or developers?
Yes. That’s the point of this service. I do the thinking and reviews, they build, and we agree how to work together on the first call.
Can you train our designers?
Yes. I train designers at Webtec on UX, structure and quality, and the material can be adapted to your team and tools.
Do we need to use WordPress?
No. Architecture, UX and conversion work doesn’t depend on the platform. Platform advice is there if you want it.
How do we start?
A free call. If it fits, you get a written proposal with what I’ll deliver, by when, and the price.
Give your team a plan.
Tell me about your team and your site. A free call, about 30 minutes.