The site was built without a brief
It looked right at launch. Over time, no one could explain what it was for or why some pages worked and others did not.
Digital Strategy and Execution
Strategy before design is what makes a rebuild pay off.
I define what your site is for, who it serves, and how it should be structured before any designer opens a tool. The strategy comes first.
The engagement
The default engagement is strategy-first work. The work produces a working reference document that resolves your site’s structure, purpose, and audience before the build begins. Your build team works from that document, whether it is an agency, a developer, or your own staff. It tells them what the site is for, who it serves, how its pages relate to each other, and what each page needs to do. Most build teams have never had a brief this complete before they started.
For clients who want a single point of accountability from strategy through to launch, I handle the implementation directly. The strategy phase and the deliverable are the same. I build the site on WordPress with Bricks Builder rather than handing off the document to someone else. The CMS is configured so your editorial team can update content, add pages, and manage media without developer support. One person carries the strategy into the build. Nothing gets lost between what the document says and what the site actually becomes.
Either way, the strategy phase runs first. That is not a default I adjust based on timeline pressure. A build that starts without a defined purpose, audience, and information architecture will produce a site that looks right and performs badly. I have watched this happen with clients who skipped it. Without exception, they rebuilt within eighteen months.
The situations I see most often
Most site problems are strategy problems in disguise.
The business has moved on but the site has not
New services, different audience. The site still reflects 2020 positioning. Visitors who should convert leave.
The last rebuild looked great. Visitors disagreed.
Design polished. Developers on time. Six months later, bounce rate was up, enquiries flat. The problem was upstream.
What you walk away with
Three deliverables that mean your team can brief designers, build with confidence, and maintain the site long after the engagement ends.
A documented strategy before any designer opens a tool
Purpose, audience, messaging, and IA defined in writing. Everyone on the build works from the same document. No one has to guess what the site is supposed to do, because the answer is already written down and agreed.
A site architecture built around how visitors navigate
Structured around the decisions visitors need to make and the actions you want them to take.
A build your team can maintain independently
Covers the content model, navigation logic, and the reasoning behind every structural choice. Your team updates pages, adds sections, and extends the site without calling you or me. That independence is the point.
How it works
Four phases, typically three to four weeks for the strategy work. Build oversight runs as long as the build does.
Discovery
Audit of the existing site, stakeholder conversations, competitor review, and audience research. What the site does, where it fails.
Strategy definition
Positioning, audience, messaging hierarchy, IA, URL structure, and content model. The deliverable is a working reference your team builds from, not something that sits in an inbox after a presentation.
Build oversight
Design and development reviewed against the strategy as the build progresses. Issues caught during build cost far less than after launch.
Handover
Content model, navigation rationale, and guidance for future pages. Team walkthrough so they understand the decisions and can act on them going forward.
Teams that skip the strategy phase and go straight to wireframes almost always end up redesigning twice. The first version looks right but performs badly, because no one defined what “perform” meant before the designers started. I have watched this happen with enough clients to consider strategy-first non-negotiable.
Let's work out what the site actually needs to do.
Most strategy engagements start with a single conversation. Bring your situation and we will figure out the right approach together.
What clients say about the work
From clients across strategy, execution, and advisory engagements. Different sectors, different problems.
“Working with him was straightforward and collaborative. He is very detailed, reliable, and quick to translate discussions into clear, actionable steps. He also takes the time to guide and teach the team, which really helped build our internal capability. I can see why people describe him as a “walking Google” — he brings a wide range of knowledge and connects things quickly.”
Melissa Jailani
Digital Experience & Marketing Lead
“…every decision for the web site is always based on our side and Yassir best experience on the do’s and donts. The price you pay is what you get. Before production, during production and after production it is worth every ringgit spend. Hands down, the best experience and he knows what he is doing. My advice, don’t just get a web site, but get the web site. Great job Yassir, appreciate your work. The best.”
Elisa
Real Estate Negotiator
Common questions
Answers to the questions I get asked most often.
How is this different from hiring a web agency?
An agency executes briefs. An account manager routes deliverables between specialists, and the quality of what you get depends largely on the quality of the brief you provide. This engagement starts before the brief exists. The strategy work defines what the brief should say, and the same person who wrote it carries that context through to the finished site. Agencies are effective when the brief is solid. Most briefs are not solid, because no one did the strategy work first.
Do I need to use a specific CMS or platform?
No. This is platform-agnostic strategy work. The deliverable informs architecture decisions regardless of what you build on.
What does the strategy deliverable include?
A positioning summary, audience definition, messaging hierarchy, information architecture with URL structure, and a content model covering page types and the relationships between them.
Do you handle the build as well?
Two options. Build oversight is included in every strategy engagement. I review your agency or developer’s design and development work against the strategy as the build progresses. For clients who want a single provider from strategy through to launch, I handle the implementation directly. The scope of what that includes is covered in the next question.
What does an implementation engagement include?
The site is built on WordPress with Bricks Builder. I handle design direction, development, and content population. Copywriting is a separate service. Technical QA runs across devices and browsers before launch. The CMS is configured so your editorial team can update content, add pages, and manage media without developer support. Handover includes a structured CMS walkthrough and editorial workflow review so your team is set up to work independently from day one.
What happens after launch?
Handover documentation means your team can make content and structural updates independently. Clients who want ongoing strategic input for a new service launch, a repositioning, or an SEO push can continue on a retainer basis. Most engagements close cleanly with the handover.
How long does this take?
The strategy phase is typically three to four weeks, depending on how much existing research and documentation is available. Build timeline depends on scope, design complexity, and your team’s capacity. For implementation engagements, the build typically adds four to eight weeks beyond the strategy phase, depending on scope and content volume. I will give you a realistic estimate at the start.
Before the brief goes out
The strategy conversation should happen before you commission design work. If you are planning a rebuild in the next few months, this is the right time to talk.