Skip to main content

Custom Systems

Mobile-first storefronts with M-PESA STK push, stock visibility, and order capture so WhatsApp shoppers can finish a purchase without calling.

See what is included
Tailor for

Typical first build

KES 120k - 350k

Timeline

3 - 6 weeks

Includes

Discovery, build, launch, and a 30-day post-launch window for adjustments.

Range covers most retail projects in this pillar. Final scope and price come out of a planning call.

Common use cases

When this becomes useful for Retail

Mobile storefront with M-PESA

A retailer or D2C brand whose customers shop and order from a phone but currently do it through DMs and call-backs.

Outcome

Customers browse, ask, order, and pay with M-PESA STK push, with a clean record for the team.

Stockist or wholesale portal

A distributor or supplier whose B2B customers reorder through phone calls, WhatsApp, or shared spreadsheets.

Outcome

Stockists log in, reorder, see balances, and submit POs without anyone retyping the order.

Loyalty and customer account hub

A retailer with returning customers who reorder, ask about delivery, and want offers but currently get treated like first-time buyers.

Outcome

Customers log in to see past orders, track delivery, and unlock offers, without the team manually pulling history.

Sound like your situation?

A 30-minute planning call gets you scope, timeline, and a budget range you can act on.

Problems we hear most often from Retail

If any of these sound familiar, this pillar is the right place to start.

Customers ask the same product, price, and delivery questions on WhatsApp because the site cannot answer them

Orders captured in DMs get lost or partially recorded by the time the team fulfils them

M-PESA collection is manual, with payment confirmations missed during busy periods

No mobile-first experience for the 80%+ of shoppers arriving from a phone

What is included

Capabilities for Retail

Mobile-first product catalogues and storefronts

M-PESA STK push and card checkout

Stockist and supplier ordering portals

Order confirmations on WhatsApp

Workflow example

How it changes for Retail

The useful question is not only what feature gets built - it is what changes in how customers, staff, payments, and records move through the business.

1

Before

Customers find a basic site, ask product and price questions on WhatsApp, wait for a reply, then pay manually after several follow-ups.

2

Build

We design the storefront, wire M-PESA STK push, add stock visibility, and capture orders into a record the team can act on.

3

After

Orders close on the site or via WhatsApp with consistent records, and reconciliation stops eating evenings.

Want a workflow mapped for your business?

We will sketch the before/build/after for your specific operation on the call.

Infrastructure inside this pillar

The rails we wire in when the workflow needs them

Good fit when

  • The business gets regular enquiries, orders, bookings, or account requests.

  • Customers need to take action on mobile without calling first.

  • Payment, WhatsApp, SMS, or email needs to be part of the journey.

Not the best starting point when

  • The offer is not clear enough yet to turn into a customer journey.

  • You only need a static brochure page with no forms, payments, portal, or workflow.

Example deliveries

What this looks like for Retail

Retail storefront with M-PESA checkout

Faster, clearer storefront with product discovery, M-PESA STK push, and a simpler path to purchase.

Scoping inputs

What makes planning faster

You do not need perfect documentation before a call. These are the practical details that help us recommend the right starting build and avoid unnecessary scope.

Your main customer actions: enquire, book, order, pay, download, or log in.

Current customer questions and where the team answers them today.

Payment, messaging, CRM, spreadsheet, or email tools that already exist.

A clear owner who can approve copy, flows, and launch decisions.

Buyer questions

Questions that come up from Retail

Can the site take M-PESA payments directly?

Yes. We integrate M-PESA STK push and (where useful) Paybill or Till, with confirmations posting against the order so reconciliation is automatic.

What about stockists and wholesale customers?

We can add a B2B portal with credit terms, reorder lists, and balances alongside the public storefront, so retail and wholesale share one system.

Will it work well on cheap Android phones?

Yes. We design and test on the devices and connections customers actually use, with mobile-first layouts and minimal data weight.

Where most retail operators start

Custom Systems first, then AI + Communication and Operations Systems

Most retailers start by giving customers a working mobile storefront with M-PESA so phone orders convert cleanly. Once volume justifies it, AI on WhatsApp removes the repeat questions and operations tools take stock and reconciliation off spreadsheets.

You are looking at the recommended starting pillar Then AI + Communication Then Operations Systems

Industries we know best for this pillar

Built around how operators actually work

Ready to scope a custom systems project?

Where customers find you, decide, and pay. Tell us the bottleneck and we will point at the right scope, timeline, and budget range.

  • Free 30-minute planning call
  • Scope, timeline, and budget range
  • WhatsApp, phone, or email available