1. Snapshot
Client: A two-sided service provider marketplace (anonymised)
Founder: Solo founding director with a background in product development and community services
Industry: Technology / Marketplace / Informal Sector Services
Geography: Kenya
Business age at engagement: Under 2 years at engagement start
Team size at engagement: Small – under 10
Engagement date: 2022 – 2024
Growth stage: 01 — Strategic Direction through 04 — Momentum
Entry point: Execute – then Diagnose and Architect as engagement deepened
What they came asking for: Social media support
Pattern: The build encoded the wrong assumptions, and the data being collected was not informing anything
2. Executive Summary
A two-sided marketplace connecting informal sector service providers with customers who needed them came to the engagement with a growth problem it was describing as a marketing problem. Downloads were coming in. Users were registering. But the side of the marketplace that needed to grow – the customer side, the side that generated bookings and commercial activity – was not converting at the rate the model required.
The engagement began as social media support. It became something different when the questions that came from doing the execution work surfaced structural problems that execution alone could not fix: a product name encoding the wrong promise, a user journey that was not converting where it mattered most, data being collected daily that was informing no decisions, and new partnerships being added before the core commercial problem was solved.
The work that followed – slowing the business down enough to examine what it was actually building, confirming the user journey before amplifying noise, building the data infrastructure that made commercial decisions possible, rebranding from a name that was attracting the wrong users to a name that described what the platform actually delivered – produced a significantly larger, better-classified, and more commercially useful user base.
Without this work, the platform would have continued growing its user base on the strength of name confusion and a competitor’s advertising budget – attracting the wrong audience at scale, with data being collected that was informing nothing and a user journey that was converting the easier side of the marketplace while the commercially critical side went unsolved.
3. The Situation They Recognised
The founder had spent two years building before the engagement began. The idea was real – born from a specific, lived moment of needing a skilled service provider in a remote location and having no reliable way to find one. Her network had confirmed the idea was strong. Building had started.
What had not happened was formal market validation. The product existed because the problem was real, the founder was credible, and momentum was moving. Funding was needed to prove the concept and grow, which meant growth metrics mattered – and downloads were coming.
What the downloads were not revealing was that the product name was doing work the business had not intended. The name was producing a specific and consistent misread – new users were arriving expecting something different from what the platform offered. The misread was not occasional. It was structural: the name, combined with the activity of a competitor operating in the same space, was pulling in an audience the platform was not designed to serve.
On the other side of the marketplace – customers booking service providers – the problem was different. Trust. A customer looking for a skilled fundi was being asked to trust someone they had never met, through a platform they had just discovered, for work that would happen in their home or business. That trust problem had not yet been systematically addressed. The infrastructure for trust had not been built.
The business knew something was not working. The response had been to keep moving.
4. The Moment of Risk
Several decisions were already in motion or recently made when the engagement deepened beyond social media support.
Downloads were growing – partly because a competitor operating in the same space with a larger paid ads budget was driving discovery for both platforms. SEO and ASO work was being done to filter out the wrong users, but the filtering was fighting a current rather than changing the channel.
A new partnership had been added in response to user behaviour data – a high volume of a specific type of enquiry – without a full examination of what that signal meant for the product direction. The partnership was real and was being communicated to users, but it risked pulling the product’s identity in a direction that had not been deliberately chosen.
More broadly, data was being collected. Daily reports existed. But the reporting was manual, without a dedicated person to build dashboards or draw commercial conclusions. The data existed and was informing nothing.
The business was adding to a system that had not been confirmed to work. Each addition – the new partnership, the continued SEO and ASO spend, the social media execution – was building on top of a user journey that had not been examined from the side of the marketplace that mattered most.
The risk was not any single decision. It was the cumulative cost of building faster than the foundation could hold.
5. What We Found
Finding 01 — The name was encoding the wrong promise at scale
The product name was producing a specific and consistent misread. New users arrived expecting something the platform did not offer. The misread was not occasional. It was structural – the name, the competitor’s advertising, and category associations were all pointing in the same direction.
Every user acquired under the original name arrived with a prior expectation the product could not meet. Reorienting them required effort the team was spending instead of converting the right audience. The name was doing active commercial harm at scale.
Finding 02 — The customer side of the marketplace was the commercial constraint and was receiving the least attention
Service providers were joining the platform. But customers booking service providers was where the commercial model depended, and this side was harder.
Trust was the specific barrier. The infrastructure for trust – visible ratings on profiles, galleries showing past work, customer service standards, a resolution process when things went wrong – had not been fully built.
The team was small. Attention was split across acquisition, partnerships, and product development. The customer side of the marketplace was being managed rather than solved.
Finding 03 — The data was being collected but was not informing anything
Daily reports existed. Numbers were tracked. But the reporting was manual, produced on spreadsheets, without a dedicated person to analyse it or a dashboard that translated raw numbers into decisions.
The volume of a specific type of enquiry – which had triggered the new partnership decision – was visible in the data. But what that volume meant, what proportion of the user base it represented, how it compared to other enquiry types, and what it implied for the product direction had not been examined.
Data was present and inert. The cost of that inertia was not the absence of information. It was decisions being made from a partial view of what the information was actually showing.
Finding 04 — The business was moving at a speed its infrastructure could not yet support
Each new addition – partnerships, SEO and ASO spend, social media, new product features – was being added to a system whose core conversion problem had not been solved. The additions were real responses to real signals. But they were applied before the signal had been properly read.
The business was not failing. It was building on assumptions that had not been examined because the pace of building had not left room for examination.
6. What Changed
The fundamental shift was a deliberate slowing down – not to stop the momentum, but to examine what was being built before more was built on top of it.
Specific decisions that became possible:
The decision to rebrand was made from an examined position. A new name was chosen – one that described what the platform actually delivered, to the right audience, with a commercial promise the product could keep. The rebrand was not cosmetic. It was a repositioning. User volumes shifted after launch. The quality of users who came through was stronger.
The SEO and ASO strategy changed. The decision to pause significant spend deliberately – naming the risk of amplifying noise rather than solving the conversion problem – required naming the problem clearly enough that a founder who had been moving fast agreed to slow down.
A CRM system was implemented from scratch. The spreadsheet-based daily reporting was replaced with a contact classification system that made the data useful – not just visible. The volume and type of enquiries, previously noted but unactionable, became the basis for commercial decisions. The new partnership, for example, could now be evaluated against actual data rather than from the impression that the enquiry volume was significant.
The customer side of the marketplace received dedicated attention. Galleries were built into the platform so service providers could show their work. Ratings infrastructure was developed. Customer service training materials were produced – because the trust problem on the customer side was partly a service standards problem that training could address. The infrastructure for trust was built rather than assumed.
What was not possible before the engagement:
Making product decisions from data rather than impression. Examining the user journey on the customer side before adding more to the service provider side. Rebranding from a commercial position rather than a reactive one. Slowing the SEO and ASO spend with a clear rationale rather than continuing to filter out the wrong audience at cost.
7. The Result
Commercial: A significantly larger and better-classified user base on a confirmed foundation – with users reoriented through a deliberate rebrand, a classified contact system, and a customer journey that had been examined rather than assumed. The commercial model demonstrated enough proof of concept that the founder could evaluate the next phase of the business from an informed position rather than from accumulated momentum.
The majority of the user base consists of service providers who had been verified, classified, and trained. When the business subsequently reoriented toward a B2B model – connecting businesses and project managers with trusted service professionals at scale – those verified providers were the asset the pivot was built on. The trust problem that was hard to solve retail became an asset wholesale.
Operational: The business had data infrastructure for the first time. The CRM replaced manual spreadsheet reporting. Contact classification meant the enquiry patterns, booking behaviour, and service provider activation rates were all visible and actionable rather than collected and inert. Decisions that had previously been made from impression could now be made from evidence.
Confidence: The engagement gave the founder the evidence base to make a significant commercial decision – the rebrand – from an examined position. The name change was not reactive to the competitor. It was the result of understanding what the product actually was, who it was for, and what the name needed to communicate to the right audience. That is a different kind of decision from one made under pressure.
8. What This Prevented
Growing the user base at scale on a user journey that was not confirmed to convert. The SEO and ASO spend was driving volume. Pausing it deliberately – naming the risk of amplifying noise rather than solving the conversion problem — prevented a significant investment in acquisition that would have produced more users at the same conversion rate on an unexamined journey.
Data remaining inert while decisions were made from impression. The specific enquiry volume that triggered the new partnership was real. Whether it was the signal it appeared to be – whether it represented a strategic direction worth pursuing – required the kind of analysis that was only possible once the data infrastructure existed. The CRM implementation made that examination possible. Without it, the partnership would have continued to be evaluated from impression rather than evidence.
A rebrand made under competitive pressure rather than from commercial examination. The competitor with the same operational space and a larger paid ads budget was a real commercial problem. The reactive response would have been to rebrand quickly to escape the confusion. The examined response was to understand what the product actually was, confirm the audience it needed to reach, and choose a name that described the promise the product could keep. A reactive rebrand would likely have produced a different name with the same unexamined foundation underneath it.
The trust problem on the customer side remaining unsolved while the service provider side continued to grow. A two-sided marketplace where one side is growing faster than the other is a structural imbalance that compounds over time. More service providers on a platform with insufficient customer trust produces a worse experience for the service providers – fewer bookings, more waiting, less retention. Building the customer trust infrastructure addressed the imbalance before it became the reason service providers stopped engaging.
QALLANN NOTE
The engagement began as social media support. It became something different because the questions that came from doing the execution work surfaced structural problems that execution alone could not fix. That is how most of the work at this level actually starts – not from a fractional CMO brief, but from someone close enough to the work to see what the work is building on.
What the engagement produced was a verified, classified user base on a confirmed foundation. What has happened since – the reorientation toward a B2B model – is the founder’s decision, made from an informed position. The trust problem that was hard to solve at the consumer level became an asset at the B2B level: a verified network of trained service professionals that businesses could access at scale.
That is what an engagement that produces a real foundation looks like when the founder uses it well. The commercial model evolved. The asset the engagement built did not.
The pattern this engagement exemplifies is one of the most common in early-stage product companies: a founder with a real idea, genuine momentum, and a pace of building that outstrips the examination of what is being built. The data is collected but not read. The user journey is growing but not confirmed. The additions are applied to a system whose core conversion problem has not been solved. Slowing down enough to look is not a failure of confidence. It is the condition that makes the next phase of building worth doing, whatever form that next phase takes.