Planning / Questions / Before the project
Good Questions. Better work.
Scope / Budget / Process / CMS / Launch
Start with the problem. The specification can wait.
01 / Before we beginDecisions / Not formulas
Less uncertainty / More clarity
Good projects begin with better questions.
Before I write a proposal, I want to know what you need, what already exists and how people use it. These are the questions that come up first, with the answers I usually give.
02 / Frequently askedShort answers
Clarity from day one.
What people usually ask before they commit.
Do I need a complete brand before the website?
No. I can start from the identity you have, or do the brand in the same project if the business needs one.
Can an existing site be redesigned incrementally?
Often, yes. A review of the current site shows which content, parts and hosting can stay and what has to change.
Will the site include a CMS?
If someone needs to edit the content, yes. Which one depends on who edits, what permissions they need and what it has to connect to. I don’t pick one before I know that.
Can it support multiple languages?
Yes, as long as we decide at the start which markets it covers, who translates, who owns each language’s content, and how the addresses work.
What about accessibility and performance?
Both are requirements from the first day. We agree on criteria that can be measured. I don’t guarantee a Lighthouse score.
Who handles DNS, deployment and email setup?
I can, if it is in the scope. The accounts are set up in your name, and the logins stay yours.
How do we establish scope and price?
I look at the goals, what you already have, the features that matter, the integrations and how delivery would run. Then I quote.
What happens after launch?
We agree on what happens next: maintenance, monitoring, content changes and further work. Or your team takes it over.
03 / Preparing the briefThe useful information
Bring the context. I’ll find the form.
The real problem.
What is not working and who is affected?
Your audience.
Who is using the service, and what do they need?
What already exists.
Logo and brand files, content, systems, and technical limits.
The desired outcome.
What success looks like, and how you’d recognise it.
04 / The collaborationWhat happens next
What happens after you write.
01 / Discover
Understand.
Goals, users and the practical limits.
02 / Define
Shape.
Agree on priorities, scope and the design direction.
03 / Build
Make it real.
Design, build, test, and adjust as we go.
04 / Evolve
Keep improving.
Launch, with clear ownership and a plan for what comes next.
05 / Getting startedReal experiences / Different needs
A first conversation commits you to nothing.
New product or an old one that needs work, a good first conversation makes every later decision easier.
Initial brief / Discovery / Next steps
A good problem / A better response
Have a good Problem?
Send what you have, even if it is three lines.
Start a project