Concept case studyProfessional Services

From scattered enquiries to one connected growth system.

How NairobiX would redesign the path from first interaction to qualified opportunity, sales follow-up and measurement for an established, referral-led firm.

Concept engagement — illustrative scenario, not historical client results.

A professional standing at the head of a table, talking with seated colleagues in a bright office. — Illustrative composition of the designed system: a photograph of the kind of business, with interface fragments from the proposed system.

Industry: Professional Services
Focus: Growth system
Solution areas: Growth Strategy & Analytics Digital Marketing CRM & Sales Systems Business Automation Web & Digital Solutions
Reading time: 10 min

02The context

A business that works — up to a point.

Consider an established professional services firm in Nairobi — an advisory, accounting, legal or consulting practice. It has built its reputation over years of good work. Most new clients arrive through referrals from existing clients and partners, and the partners are well known in their sectors.

Growth has started to require more than reputation. The firm wants to win work beyond its existing network, runs occasional search and LinkedIn campaigns, and has a website that describes its services well. Enquiries now arrive through WhatsApp, email, the website form, phone calls and introductions at events.

Nothing is broken, exactly. Clients are served well. But the path from a first interaction to a signed engagement has grown informally, one channel at a time, and nobody has designed it as a whole.

What already works

A strong reputation and a loyal referral base
Partners who sell well once they are in the room
A capable delivery team
A website that explains the services clearly

What the team manages by hand

Logging enquiries in a spreadsheet — when someone remembers
Deciding, case by case, who follows up each enquiry
Chasing proposals that have gone quiet
Compiling a monthly picture of new business by hand

03The problem

Not a lead problem. A system problem.

Asked what is wrong, the firm would probably say “we need more leads.” Looked at as a system, the picture is different: demand already exists, but at every layer it is harder to see, harder to act on and harder to learn from than it should be.

Marketing
Campaigns and articles run, but it is unclear which of them produce clients rather than clicks.
Budget decisions rest on reach, not on revenue.
Capture
Enquiries arrive through five channels, each held somewhere different.
There is no single count of demand.
Qualification
The important context — the need, the timing, who decides — stays inside individual conversations.
Partners spend time on poor-fit enquiries and miss good ones.
Follow-up
Responsibility for the next step is informal; proposals are chased when someone remembers.
Opportunities cool without anyone deciding to let them go.
Sales
Opportunity status lives in partners' heads and inboxes.
Nobody can see the pipeline or forecast new work with confidence.
Reporting
New-business figures are assembled by hand, if at all.
Management cannot see where demand is being lost.

Recognise some of this in your own business?

See where your business stands→Talk to Us→

04The opportunity

The opportunity is not simply to generate more enquiries. It is to create a connected path from attention to qualified opportunity — and to learn from every step of it.

For a referral-led firm, the first gains usually come from the middle of the path: capturing every enquiry, qualifying consistently and making the next step visible. Better acquisition is worth more once the system below it can hold the demand.

That ordering matters. It means the first phase of work strengthens what already works — referrals and partner relationships — before money is spent adding new sources of demand. Marketing investment then lands on a system that can show what it produced.

01
Attention
02
Capture (focus of this engagement)
03
Qualify (focus of this engagement)
04
Nurture (focus of this engagement)
05
Convert (focus of this engagement)
06
Deliver
07
Retain
08
Measure (focus of this engagement)

Where this engagement concentrates first, within the NairobiX growth system.

05The system design

The architecture, layer by layer.

The proposed architecture has nine layers. Each exists because of a specific problem in the layer map above, and each passes something to the next. Select a layer to see why it exists, what moves through it and what happens next.

Why it exists
To add a predictable source of demand alongside referrals — aimed at the work the firm actually wants, not everything it could do.
What moves through it
Campaign and source information, carried in tagged links.
What happens next
Visitors arrive on a landing experience written for their specific need.

Layer 01 of 09

Marketing

Targeted search and LinkedIn campaigns, referral-partner content and articles on the services the firm most wants to grow.

Why it exists: To add a predictable source of demand alongside referrals — aimed at the work the firm actually wants, not everything it could do.
What moves through it: Campaign and source information, carried in tagged links.
What happens next: Visitors arrive on a landing experience written for their specific need.

Every business needs a different version of this architecture.

See what this could look like for your business→Talk to Us→

06Before / after

From a disconnected pattern to a connected one.

The same people and much of the same technology — organised as one system instead of several.

Before · current operating pattern

Website form → shared inboxWhatsApp on partners' phonesSpreadsheet, sometimes updatedIntroductions at eventsProposals in email threadsA monthly report built by hand

Website form → shared inbox
WhatsApp on partners' phones
Spreadsheet, sometimes updated
Introductions at events
Proposals in email threads
A monthly report built by hand

Each channel works on its own. Nothing connects them, so nothing can be counted end to end.

After · designed future-state system

01Campaigns & referrals
02Landing experience
03Capture
04CRM
05Qualification
06Follow-up
07Sales pipeline
08Onboarding
09Reporting

One path, one record, one view — and a loop back to marketing.

An architectural comparison of operating patterns — not a record of measured results.

07The customer journey

One customer, through the designed system.

What the customer experiences at each step, and what the system does behind it. Names and details are illustrative.

What the customer experiences

What happens in the system

01
Discover
Customer
A finance director searches for help with a specific compliance question — or hears the firm's name from a peer.
System
The search campaign or the referral partner's link carries its source.
02
Explore
Customer
She lands on a page about that exact service: who it is for, how an engagement works, what happens first.
System
The page is built to answer the questions buyers ask before they make contact.
firm.co.ke/advisory/tax-compliance
Tax & compliance advisory
Clarity on your obligations before the deadline, not after.
For finance teams in growing companies. A first conversation, then a fixed-scope proposal.
Discuss your situation →
03
Enquire
Customer
She taps the WhatsApp link. The opening line is already written; she adds one sentence of context.
System
The pre-filled message identifies the service page, so the source is not lost.
Firm · Business account
Hi, I found your tax compliance page. We're a logistics company and need help before the next filing.
Thank you. Wanjiku from our advisory team will reply by 11am today.
Automated acknowledgement
04
Capture
Customer
She receives an honest acknowledgement: who will reply, and when, in working hours.
System
A contact and an enquiry are created in the CRM, with source and service attached, and an owner is assigned.
Enquiry · Logistics companyNew
Service
Tax & compliance
Source
Search → service page → WhatsApp
Owner
Wanjiku M.
Next action
First reply · today 11:00
05
Qualify
Customer
In the first conversation she is asked a few useful questions: scope, timing, who else is involved.
System
The answers are recorded; the enquiry is marked qualified and becomes an opportunity.
06
Follow up
Customer
After the discovery meeting, the proposal arrives when promised, and a short check-in follows a few days later.
System
If the proposal has had no response, the owner receives a reminder task — and decides how to follow up.
Follow up: proposal to logistics company
Due tomorrow · Owner: Wanjiku M.
No client activity since the proposal was sent 4 working days ago. Suggested check-in template attached — edit before sending.
07
Convert
Customer
She raises one question about scope; the partner answers it the same day.
System
The opportunity moves to Negotiation, then Won, with the agreed scope recorded.
New business pipeline
Proposal sent
Manufacturer · Advisory
Negotiation
Logistics co. · Tax
Won
NGO · Payroll
08
Deliver
Customer
Her first week is organised: engagement letter, kickoff meeting, a named contact.
System
Onboarding tasks are created from the won opportunity, carrying what was agreed in the sale.
09
Measure
Customer
Months later she refers a colleague, who arrives with a known source.
System
The monthly report shows the campaign, the service page and the referral in one line of sight.
Qualified opportunities by source · layout
- Referrals
- Search · service pages
- LinkedIn
- Events
Illustrative layout — not data

08The technology layer

Technology, chosen last.

Technology comes last — once the requirements are clear. For this scenario a modest, well-integrated stack is enough; a larger one would add cost and maintenance without adding capability the firm needs yet.

Proposed stack · example architecture

Each technology fills a capability the system design called for. Remove the requirement, and the tool goes with it.

CRM: Zoho CRM
Messaging: WhatsApp Business Platform
Search & analytics: Google Ads & Analytics
Web platform: Next.js
Design: Figma

Business requirement
System design
Technology

CRM
Zoho CRM
CRM · Follow-up · Pipeline · Reporting
Role
System of record for contacts, opportunities, activity and onboarding tasks.
Why it fits
Mature pipeline and workflow features at a cost that suits a firm of this size, and a documented WhatsApp integration.
Messaging
WhatsApp Business Platform
Capture · Follow-up
Role
The conversation channel most prospective clients already prefer.
Why it fits
Connected through the Platform, conversations can be logged against the CRM record instead of living on personal phones.
Search & analytics
Google Ads & Analytics
Marketing · Reporting
Role
Search campaigns for priority services, and measurement of how visitors use the site.
Why it fits
Buyers search for specific problems. Campaign parameters carry the source through to the CRM.
Web platform
Next.js
Landing experience · Capture
Role
The landing experience: fast, focused service pages with forms that post directly to the CRM.
Why it fits
Control over performance, forms and tracking — the parts of the site that do conversion work.
Design
Figma
Landing experience
Role
Designing the service pages and the enquiry path before they are built.
Why it fits
The firm can review the journey and the wording early, while changes are still cheap.

Illustrative technology choices for this concept scenario. They are not a record of a client implementation, imply no partnership with any vendor, and are not the only suitable stack.

09The automation layer

Rules first. Then workflows. Then automation.

Automation here is deliberately narrow. It carries the routine steps that currently depend on memory — and hands every judgment back to a person.

Process: The sequence of work the business agrees to follow.
Rule: A condition written down — “if no reply in three days”.
Workflow: A rule connected to the actions it should cause.
Automation: The workflow running without anyone starting it.
Technology: The tools that carry it out.

New enquiry

Trigger
A website form is submitted, or a new WhatsApp conversation starts.
Rule
Check that contact details and the service of interest are present; if not, flag the record for completion.
Action
Create or match the contact, and create an enquiry carrying its source and service.
Notification
Assign an owner by service line and notify them.
Follow-up
Send an acknowledgement saying who will reply, and when.
Human
The owner reads the context and replies personally.
Measure
Record the time to first response and, later, the enquiry's outcome.

10Designed outcomes

What the system is designed to improve.

01
Clear ownership
Every enquiry has a named owner from the moment it arrives.
02
Visible follow-up
Open proposals and overdue next steps are visible to the person responsible, and to management.
03
Less manual coordination
No retyping between inbox, spreadsheet and report.
04
A consistent client experience
Every prospective client receives the same standard of response, whichever channel they use.
05
Management visibility
Demand, conversion and pipeline can be seen by source and by service.
06
Marketing connected to sales
Campaign decisions can be based on qualified opportunities, not clicks.
07
Useful business data
Sources and loss reasons accumulate into knowledge about what works.
08
Ready for what comes next
Clean records and defined stages make further automation, or AI assistance, practical.

Design objectives the system is built around — not measured client results.

11Measurement framework

What we would measure.

No invented numbers — a plan for knowing whether the system is working, set before it is built.

Acquisition

Visits by source: Visits to service pages by channel and campaign.
Qualified enquiries: Enquiries that meet the agreed criteria, by source.
Cost per qualified enquiry: Where paid campaigns are used.

Conversion

Enquiry → qualified: Share of enquiries that meet the criteria.
Qualified → opportunity: Share that reach a discovery meeting or proposal.
Opportunity → engagement: Share won, by service and source.

Operations

Time to first response: From enquiry to first human reply, in working hours.
Follow-up completion: Share of due follow-ups completed on time.
Pipeline hygiene: Open opportunities with an owner, a stage and a next action.

Client

Onboarding completion: New engagements that complete the agreed onboarding steps.
Repeat and referred work: New work from existing clients and from their referrals.

System

Workflow exceptions: Automations that failed or needed manual correction.
Data completeness: Records with source, service and outcome filled in.

12The human layer

Where people stay responsible.

A person in a suit holding a folder of documents while seated.

Technology supports people who make decisions.

The system is designed to support the firm's judgment, not to replace it. Technology preserves context and prompts action. People decide — and in a firm whose value is its advice, that line matters more than anywhere.

What the system does

The CRM preserves the history of every relationship, so nothing depends on one person's memory.
Automation creates the task, the reminder and the acknowledgement.
Reporting shows where demand comes from and where it is lost.

What the team decides

Whether an enquiry is a good fit for the firm
What to propose, and at what fee
How to respond to a sensitive or confidential matter
When a client needs a partner's call rather than a message
Which lost opportunities are worth revisiting

13What we would build

One system, built in stages.

01
Strategy
Growth architecture, qualification criteria and a pipeline designed around how the firm wins work.
02
Digital
Service landing pages and a clear conversion path for each priority service.
03
CRM
Contact, opportunity and onboarding structure, configured to the firm's real stages.
04
Automation
Enquiry routing, acknowledgements and follow-up reminders.
05
Analytics
Source tracking from campaign to CRM, and a monthly demand-and-pipeline report.
06
Later phase
AI — later
Summaries of discovery calls and first-draft proposals, once clean records and consistent stages are in place. Not in the first phase.

Components of one system, built in stages and connected to each other — not a list of separate services.

In this scenario, the firm doesn't need a bigger budget first. It needs the demand it already has to be visible, owned and measured.

Related thinking

14 · The next step

Your business probably has a different version of this problem.

Every business has a different starting point. The right system depends on your goals, requirements, customers, processes and existing technology.

Find Your Version of This Problem→Talk to Us→

← All case studies Next concept caseReal Estate Lead-to-Sales System