1. Snapshot
Client: East Africa compliance and standards consultancy
Industry: Professional Services – Compliance, Standards and Capability Development
Geography: Kenya / Africa
Business age at engagement: Over 10 years
Team size at engagement: 5 to 15
Engagement date: January 2025 – October 2026
Growth stage: 02 – Positioning / 03 – Offer Architecture
Entry point: Execute (presented); Diagnose (actual)
What they came asking for: Complete our website. We have outstanding pages and need the build finished.
Pattern: The build was already in progress when the positioning gap became visible
2. Executive Summary
This client is a specialist compliance and standards consultancy operating across Africa, with over a decade of work and eleven distinct expertise domains ranging from Food Safety to Laboratory Management to Leadership. They came to Qallann with a website project already in progress: several pages built, several still outstanding, a developer engaged, and a deadline in sight.
Every time the build reached a new page, it stalled. The content questions could not be answered. Not because the team was unavailable or the writing was difficult, but because the organisation had never confirmed what each offer was, who it was for, or how a buyer should understand it.
The real constraint was not incomplete content. It was unconfirmed positioning that made every content decision an implicit strategic one.
The engagement surfaced the structural problem: the organisation had been built around how it worked rather than what buyers came looking for. It identified the navigation architecture that matched buyer logic, named the positioning gap that was stopping the build, and produced both a self-service content guide and a formal proposal for a structured positioning engagement.
Without this work, the client would have published a technically complete website that failed to convert, then spent months debating why the build was not delivering results that the build was never capable of delivering.
3. The Situation They Recognised
The website had been running for over a year. The About page was done. The Courses page was done. Several other sections were done or close. The project had been delayed more than once, but the team had kept showing up, sending spreadsheets, answering questions, trying to move it forward.
From where they sat, the problem was execution. The pages were not finished. The content had not been written. The developer was waiting. What was needed was for everyone to focus, submit what was outstanding, and get the thing across the line.
They had deep expertise. Eleven distinct domains of knowledge, built over a decade of work with organisations across Kenya and the region. Clients came back. Referrals came in. The work was real and the reputation was real. They knew what they did.
What they could not do was write it down in a way that held together. Every time the build reached a new page, the descriptions felt wrong. The Business Solutions section especially. Five different service lines, each one real, each one hard to explain in a way that a visitor could read and understand. The team would send drafts, Qallann would review them, something would not land, and the page would sit.
They believed the problem was that they had not yet found the right words. The real problem was that they had not yet made the decisions the words depended on.
4. The Moment of Risk
Five pages of Business Solutions were being built around delivery modes: Training, Coaching, Assessments, Consultancy, Data Analysis. Each page would need a description, a value proposition, an explanation of who it was for and what a client would get from it.
None of those questions had been answered, because none of them had been asked at the strategic level. They had been sent down to the content layer, where individual team members were expected to write descriptions of offers that the organisation had never formally defined.
The Courses page had the same problem. A spreadsheet with hundreds of courses across eleven categories, some fully described, some with titles only, several in development. The build proceeded with what was available. The gaps remained.
If the build had been completed on that foundation, the website would have gone live organising the business by how it worked rather than by what buyers came looking for. A compliance professional researching whether the client could help with a food safety gap would have landed on a page about Training, not on a page about Food Safety. They would have had to understand the organisation’s internal structure to find what they needed.
A new engagement for the next set of pages would have hit the same wall. A rebrand, a pitch deck, a grant application: any downstream piece of communication would have inherited the same unresolved questions.
The build was being pushed to completion. The positioning questions it depended on had never been asked.
5. What We Found
Finding 01 – The organisation was structured by how it works, not by what buyers come looking for.
The client’s five Business Solutions pages corresponded to delivery modes: Training, Coaching, Assessments, Consultancy, Data Analysis. These are real and distinct ways of working. But buyers do not arrive at a compliance consultancy with a delivery mode in mind. They arrive with a problem in a specific domain: a food safety gap, a management standards audit coming up, a leadership challenge in a team under pressure.
The eleven domains visible in the Courses file represented the actual buying triggers: Food Safety, Management Standards, Quality, Health and Safety, Environment, Risk Management, Laboratory Management, Supply Chain Management, Leadership, Customer Service, Financial Management. None of them had a page. None of them were in the navigation. The structure that served buyers was absent from the website entirely.
The website was organised for the people who built it, not for the people who needed to use it.
Finding 02 – Compliance was being treated as a product when it was the outcome of everything the organisation offered.
Compliance appeared in the navigation as a standalone Business Solutions page. In conversations, the team described compliance as what their clients came for, what they helped clients achieve, and what everything the organisation did was ultimately in service of. It was framed as a product in the architecture and as a purpose in the conversation.
Those two things cannot both be true at once. A page about compliance as a product describes a deliverable. Compliance as the outcome of a decade of expertise across eleven domains is something far more powerful: it is the reason the organisation exists. Naming it as a standalone page shrank it.
Compliance was the through-line of the whole website, not a menu item within it.
Finding 03 – The content questions could not be answered because they were positioning questions in disguise.
Every page that stalled did so at the same point: when someone had to articulate what a visitor would understand about the offer, who it was for, and why they would choose this organisation over another. Those are not content questions. They are positioning questions. Content describes what has already been decided. Positioning is the decision.
The team was experienced and capable. They were not struggling because they lacked the information. They were struggling because they were being asked to write copy for positions the organisation had not yet taken.
The stall was not a writing problem. It was a strategy problem that had been sent to writers.
6. What Changed
What decision became possible that was not possible before?
The client could now see that the website structure itself was the problem, not the missing pages within it.
Specific decisions that became possible:
- The decision to restructure the navigation around two distinct sections: How We Work (the delivery modes) and Our Expertise (the eleven domains). Buyers could now enter through their problem, not through the organisation’s internal structure.
- The decision to remove Compliance from the navigation entirely and position it as the homepage through-line. The most powerful claim the organisation could make became the premise of the whole website, not a page competing for attention.
- The decision to pause the build and commission a structured positioning engagement before writing another line of copy. For the first time, the team had a name for the problem and a path through it.
- The decision by the founder to join the positioning sessions personally. The engagement identified that positioning decisions at this level could not be delegated, and the founder confirmed this.
What was not possible before the engagement:
Writing the Business Solutions pages without the same stall repeating. Briefing a copywriter or a future developer from the existing structure. Explaining to a client why certain descriptions were hard to write. Identifying whether the problem was content or strategy.
7. The Result
Commercial: The client now has a confirmed navigation architecture that matches how buyers actually enter the market. The new structure opens the door to domain-specific pages that can be built, refined, and used in client conversations. The positioning engagement, if confirmed, gives the organisation the foundation for all downstream commercial communication: website copy, tender responses, partner introductions.
Operational: The build has a clear path forward. The pages that stalled are no longer blocked by unresolvable content questions. The self-service content guide gives the team a structured way to write what is needed. The positioning engagement gives the founder a process for making the decisions the guide cannot make for them.
Confidence: The founder and team had been holding a sense that something was wrong without being able to name it. The engagement named it. The compliance mirror moment in the October session, where the founder’s own description of what clients came for was reflected back as the case for removing Compliance from the navigation, landed differently from an external recommendation. It was recognisable. The shift was not persuasion. It was recognition.
8. What This Prevented
- A completed website that organised a decade of genuine expertise around the wrong logic. The five Business Solutions pages, had they been finished, would have gone live as a delivery-mode map of a buyer-domain problem. The website would have been complete. It would not have converted.
- A rebranding or redesign engagement commissioned to fix results that the design was not responsible for. Websites that do not convert often get redesigned. The next brief would likely have been for a new look or better copy, when the actual constraint would still have been structure and positioning.
- A copywriter given an unresolvable brief. If the team had brought in external writers rather than continuing to try internally, those writers would have hit the same wall. You cannot write compelling positioning copy from a structure that has not made its positioning decisions. The cost would have been time and money spent on outputs that could not hold together.
- An organisation that believed its website was done, and could not understand why it was not working. The most expensive version of a positioning gap is the one you never name. It compounds quietly, in client conversations that do not quite land, in tenders that almost win, in referrals that never quite convert. Naming the problem does not solve it. But it makes it possible to solve.
- A further twelve months of the same stall, applied to a larger set of pages. The engagement did not stop the build prematurely. The build had already stalled. The engagement named why, and gave a path forward that the build alone could not provide.
QALLANN NOTE
This engagement began as an execution project and became a diagnostic one. That is not unusual. The build is often where the gap becomes visible, because the build is the first time every positioning decision must be made explicit.
What this engagement produced is a named problem, a confirmed architecture, and a clear proposal for the work that comes next. It did not produce a completed website. It did not produce confirmed positioning copy. Those require the positioning engagement, which at the time of writing has not yet been confirmed.
The gap that remains is the gap between what the client now understands structurally and what is available to a buyer on the live site. That gap will close through the positioning engagement, if it proceeds. Until it does, the website reflects the old structure.
The pattern here appears in organisations that have been operating successfully for years: expertise is real, clients return, the work is recognised. The website becomes the first moment anyone tries to explain it to a stranger, and it surfaces a question that the internal certainty has never had to answer. That question is not ‘what do we do?’ It is ‘what does a buyer need to hear from us, in what order, starting from nothing?’ Those are different questions. The second one is harder. And it is the one the website asks.
We are in the second question with this client.