Context before form
Proposition, audience, content and objectives are organised before a visual direction is set.
——
Freelance WordPress designer: a bespoke WordPress build with a clear editorial base, so the team can maintain it and grow it.
WordPress
The approach is defined before it becomes a set of screens.
The project starts with the decision the digital presence needs to support, the information behind it and the operations the team needs to sustain. This way, design and technology respond to a specific need.
Proposition, audience, content and objectives are organised before a visual direction is set.
Navigation, content and actions are shaped around the questions that arise throughout the journey.
The system is prepared so the team can maintain and extend it with sound judgement.
Strategy, content, design and implementation are organised around the organisation’s context. Decisions are documented so the team has a clear foundation for launch, maintenance and future development.
Bespoke does not mean rebuilding what WordPress already solves. It means the theme is your own, the content types answer to your business rather than a demo, and every field in the editor exists because someone will use it. The core, user management, revisions and the media system are used as they come: they are good and have twenty years of testing behind them. What gets built is the layer where one company differs from another.
A market template costs sixty euros and looks like an obvious saving. The cost shows up later: it arrives ready for any business, so it carries features you will not use but that load anyway, and its structure imposes decisions that should be yours. When the catalogue grows or a CRM has to be connected, you end up fighting the theme instead of the problem. To validate something small and fast it is a legitimate choice; for a site meant to last five years, it is expensive.
Optimising at the end means removing weight from something already built, and it always stops halfway. Deciding up front means setting a weight budget at the same time as the grid: how many typefaces, what each third-party script earns its place with, which images are served and in what format. Done that way there is no optimisation phase, because the site is born light. And later improvements are measured against the journey that matters, not an abstract score.
Not resolved — gathered. The current site, who you are addressing, what you offer, what material exists and who decides. The first phase separates what blocks progress from what can be settled while building.
By journeys and decisions, not by number of screens. We agree what a person has to be able to do, what content supports it and what stays out of this phase. That is what gets costed.
Less than feared, but at specific moments. Two or three decision sessions and access to whoever knows the business. The rest moves forward without status meetings that decide nothing.
The journeys that matter are tested on mobile and desktop, along with forms, real-world speed, accessibility and anything that has moved since the previous site. The checklist comes from the scope, not from a generic template.
By the quality of the enquiries that arrive and by what the team manages on its own. More traffic without better conversations is not an improvement, and it is worth saying so up front.
You get documentation on how each part is edited and a prioritised list of what was deferred. From there, either the team runs it or we agree a phased follow-up.
A selection of work showing context, decisions and outcomes.
Tell us where things stand and we can assess the most useful approach for the project.
