Concept case studyE-commerce & Retail
From paid traffic to a connected customer lifecycle.
How NairobiX would connect acquisition, the shopping experience, order communication, retention and measurement for a growing online retailer.
Concept engagement — illustrative scenario, not historical client results.
Woven storage basket · Large
Handwoven sisal · 45cm
KES 3,200
Add to cart- Nairobi delivery: next working day
- Pay by mobile money or card
- Free returns within 7 days
Your order is on its way. Your rider, Kevin, will call when he's 10 minutes away.
Order update · automated
Perfect, thank you!
- Industry
- E-commerce & Retail
- Focus
- Customer lifecycle
- Solution areas
- Web & Digital SolutionsDigital MarketingBusiness AutomationGrowth Strategy & Analytics
- Reading time
- 9 min
02The context
A business that works — up to a point.
Consider a Nairobi-based online retailer selling home and lifestyle products. It has an online store, an active Instagram and TikTok presence, and a WhatsApp number customers use to ask about sizes, stock and delivery. Customers pay by mobile money or card; Nairobi orders go out by rider, and orders to other towns by courier.
Growth so far has come from content that people share and from paid social campaigns. Traffic is healthy. The team is busy — much of it answering the same questions, confirming orders and sending delivery updates by hand.
What the business doesn't have is a view of its customers over time: who bought once and never returned, who buys every season, and which channels find the customers worth having.
What already works
- Products people want and share
- A recognisable brand on social media
- A store that takes orders reliably
- Customer service that customers like
What the team manages by hand
- Answering the same stock, sizing and delivery questions on WhatsApp
- Confirming orders and sending delivery updates one by one
- Reconciling payments against orders
- Remembering who the loyal customers are
03The problem
Not a lead problem. A system problem.
Growth has mostly meant buying more traffic. Looked at as a system, the business pays to acquire a customer and then lets most of the relationship end at the first order.
Marketing
Campaigns are judged on clicks and platform-reported purchases.
Decisions rest on partial data, and on first orders rather than customers.
Experience
Product pages don't answer delivery, sizing and returns questions, so buyers leave to ask on WhatsApp.
Friction appears exactly at the moment of intent.
Checkout
Checkout is longer than it needs to be on a phone, and abandoned checkouts receive nothing, or a generic email.
Demand that reached the till is lost.
Communication
Order confirmations and delivery updates are sent by hand.
An inconsistent experience and a heavy daily workload.
Retention
Customer information is split between the store, WhatsApp and a spreadsheet.
Repeat purchases depend on customers remembering the brand.
Measurement
There is no view of customer value over time.
The business cannot tell which channels find valuable customers.
Recognise some of this in your own business?
04The opportunity
The opportunity is to treat the first order as the beginning of a relationship — and to measure the business by customers, not just transactions.
Acquisition is the most expensive part of a retail business's growth, and it is the part the business controls least. Every improvement after acquisition — a clearer product page, a shorter checkout, a reliable delivery update, a well-timed second purchase — makes every shilling of marketing worth more.
The design therefore works backwards from the customer's second order: what would have to be true for a first-time buyer to come back without being paid to?
01
Attention (focus of this engagement)
02
Capture
03
Qualify
04
Nurture
05
Convert (focus of this engagement)
06
Deliver (focus of this engagement)
07
Retain (focus of this engagement)
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 eight layers, following the customer from first impression to repeat purchase, with measurement closing the loop. Select a layer to explore it.
- Why it exists
- Channel decisions need to be based on customers acquired, not on clicks.
- What moves through it
- Source and campaign for every visit and order.
- What happens next
- Visitors land on product pages built to answer their questions.
- Why it exists
- Every question a page answers is one fewer reason to leave it.
- What moves through it
- Product viewed, and questions asked.
- What happens next
- The shopper adds to cart and checks out.
- Why it exists
- Most shoppers are on phones; every extra step is a chance to abandon.
- What moves through it
- Order, payment status and delivery details.
- What happens next
- Order communication begins; abandoned checkouts enter recovery.
- Why it exists
- Reliable updates reduce “where is my order?” messages and build trust for the next purchase.
- What moves through it
- Order status and delivery events.
- What happens next
- Delivered orders move into post-purchase care.
- Why it exists
- Retention is impossible if the business doesn't know who its customers are.
- What moves through it
- Purchase history, value and consent status.
- What happens next
- Segments feed retention.
- Why it exists
- A second order from an existing customer usually costs less to win than a first order from someone new.
- What moves through it
- Segment, message and response.
- What happens next
- Returning customers re-enter the purchase path.
- Why it exists
- Good service is part of retention — and it is faster when context is on screen.
- What moves through it
- Conversations, issues and resolutions.
- What happens next
- Issue patterns inform product pages and operations.
- Why it exists
- It shows what a customer is actually worth, and which channels find the valuable ones.
- What moves through it
- Everything above, over time.
- What happens next
- Budget moves toward the channels that produce lasting customers.
Layer 01 of 08
Acquisition
Social content, paid campaigns and search, with tagged links and purchase tracking set up correctly.
- Why it exists
- Channel decisions need to be based on customers acquired, not on clicks.
- What moves through it
- Source and campaign for every visit and order.
- What happens next
- Visitors land on product pages built to answer their questions.
Every business needs a different version of this architecture.
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
- Store admin
- Instagram direct messages
- WhatsApp on one phone
- Payment statements
- Rider calls and courier slips
- A spreadsheet of “good customers”
Each tool holds a fragment of the customer. None holds the relationship.
After · designed future-state system
- 01Acquisition
- 02Product experience
- 03Checkout
- 04Order updates
- 05Customer record
- 06Retention
- 07Service
- 08Measurement
A lifecycle, not a transaction — measured end to end.
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 customer sees a woven basket in an Instagram video and taps through.
System
The tagged link records the campaign that brought her.
02
Explore
Customer
The product page tells her the size, the material, when it would arrive and how returns work.
System
The questions that used to arrive on WhatsApp are answered on the page.
Product page · mobileWoven storage basket · Large
Handwoven sisal · 45cm × 40cm
KES 3,200
Add to cart- Nairobi delivery: next working day
- Pay by mobile money or card
- Free returns within 7 days
03
Ask
Customer
She wants to know if it comes in natural colour, and taps the WhatsApp button on the page.
System
The message arrives with the product named, and whoever replies can see it.
04
Buy
Customer
Checkout takes a minute on her phone. She pays by mobile money.
System
The order and payment are recorded against her customer profile.
05
Receive
Customer
She gets a confirmation, a dispatch message and a note from the rider before arrival.
System
Each update is triggered by the order's status — nobody types them.
Store · Business accountOrder confirmed — thank you! We'll message you when it's dispatched.
Automated
Your order is on its way. Kevin will call when he's 10 minutes away.
Automated
06
Care
Customer
A week later: a short note on caring for sisal, and an easy way to report any problem.
System
Post-purchase care goes to delivered orders in this category.
07
Return
Customer
Two months later, a new collection she'd like — sent because she opted in and bought from that range.
System
A consented, relevant message to a small segment — not a blast to everyone.
Customer · Njeri W.Returning- First channel
- Instagram · spring campaign
- Orders
- 2 · home & storage
- Messaging consent
- Yes · WhatsApp
- Segment
- Home — seasonal
08
Service
Customer
When a delivery runs late, she gets an honest update before she has to ask.
System
Delivery exceptions create a task for the service team, with the order on screen.
09
Measure
Customer
She has become a repeat customer.
System
Reporting shows customer value by first channel — and the Instagram campaign that found her looks different now.
Repeat customers by first channel · layout
Search
Instagram
Paid social
Illustrative layout — not data
08The technology layer
Technology, chosen last.
The store platform, the ad accounts and WhatsApp are already in place in a business like this. The work is configuring them properly and connecting them around the customer record.
Proposed stack · example architecture
Each technology fills a capability the system design called for. Remove the requirement, and the tool goes with it.
Commerce platform: Shopify
Social acquisition: Meta — Instagram & Facebook
Analytics & search: Google Analytics & Search
Messaging: WhatsApp Business Platform
Design: Figma
- Business requirement
- System design
- Technology
Commerce platform
Shopify
Product · Checkout · Customer record
Role
Store, checkout, orders and the core customer record.
Why it fits
A mature commerce platform with the checkout, customer and order data the rest of the system builds on.
Social acquisition
Meta — Instagram & Facebook
Acquisition · Measurement
Role
Content, paid campaigns and purchase signals sent back to the ad platform.
Why it fits
Where much of the demand starts; accurate purchase signals let campaigns optimise for buyers.
Analytics & search
Google Analytics & Search
Acquisition · Measurement
Role
Site behaviour, funnel drop-off and search campaigns for high-intent products.
Why it fits
Shows where shoppers abandon the path, independently of any single ad platform.
Messaging
WhatsApp Business Platform
Communication · Service · Retention
Role
Order updates as utility templates, service conversations and consented marketing messages.
Why it fits
Customers prefer it; connected to the store, updates can run from order status.
Design
Figma
Product experience · Checkout
Role
Designing the product page and mobile checkout improvements before they reach the store.
Why it fits
Changes to the buying path can be tested with the team before customers see them.
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.
Retail automation is mostly about status: when an order, a checkout or a delivery changes state, the right message or task follows. People handle the exceptions.
- 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.
Order to delivery
- Trigger
An order is paid.
- Rule
Payment is confirmed and the delivery address is complete; if not, flag for the service team.
- Action
Send an order confirmation and create a fulfilment task.
- Notification
The fulfilment team sees the order in its queue.
- Follow-up
Send dispatch and delivery updates as the order status changes.
- Human
The team resolves stock, address and delivery exceptions.
- Measure
Track order-to-dispatch time and delivery exceptions.
10Designed outcomes
What the system is designed to improve.
01
Fewer questions at the moment of intent
Product pages answer what shoppers need to know to buy.
02
Recovered demand
Abandoned checkouts receive a single, useful reminder — and high-value ones a human offer of help.
03
Reliable order communication
Every customer receives the same confirmation and delivery updates, without manual typing.
04
One view of the customer
Orders, channel, preferences and consent in one record.
05
Repeat purchases by design
Retention runs as a system, not as a memory.
06
Channel decisions on customer value
Budget can follow the channels that find lasting customers.
07
Time back for the team
Less routine messaging, more time for product, content and service.
08
Respectful marketing
Consent is recorded and honoured, so messages stay welcome.
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
- Sessions and orders by source
- Where first orders come from.
- Cost per first order
- For paid channels.
Conversion
- Product view → add to cart
- By product and source.
- Checkout → paid
- And where in checkout shoppers leave.
- Checkout recovery
- Share of abandoned checkouts recovered.
Operations
- Order-to-dispatch time
- From payment to handover to rider or courier.
- Delivery exceptions
- Late, failed or damaged deliveries.
- Service response time
- For WhatsApp questions and issues.
Customer
- Repeat purchase rate
- Customers who buy again within a set period, such as 90 days.
- Customer value by first channel
- What customers found by each channel spend over time.
- Returns and reasons
- What product pages or operations should fix.
System
- Message delivery and opt-outs
- Template failures and unsubscribe rates.
- Consent coverage
- Customers with a recorded messaging preference.
12The human layer
Where people stay responsible.
Technology supports people who make decisions.
A retail brand lives in its taste, its voice and how it treats people when something goes wrong. The system takes the routine off the team so those things get more attention, not less.
What the system does
- Automation sends confirmations, updates and reminders when order status changes.
- The customer record puts history and preferences in front of whoever replies.
- Measurement shows which channels and products build lasting customers.
What the team decides
- Which products to buy, and which to promote
- How to handle a delayed or damaged delivery
- When a refund or an exception is the right call
- The brand's voice in every template
- When a customer needs a person, not a message
13What we would build
One system, built in stages.
01
Strategy
The customer lifecycle map and a measurement plan built around repeat customers.
02
Digital
Product page and mobile checkout improvements that answer questions before they're asked.
03
CRM
One customer record with consent, segments and purchase history.
04
Automation
Order communication, checkout recovery and post-purchase care.
05
Analytics
Purchase tracking per channel, cohorts and customer value over time.
06
Later phase
AI — later
Answering common product questions from the catalogue, with a clear handover to the team.
Components of one system, built in stages and connected to each other — not a list of separate services.
In this scenario, the retailer doesn't need more traffic first. It needs the traffic it already buys to turn into customers who come back.
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.