Agentic Commerce2026

Every chat is a checkout.

Hero image for Every chat is a checkout.

Role

Founding Design Engineer

Timeline

2025–2026

Team

AI Engineer
GTM & Operations

Skills

Conversational UX

Agentic AI

Design Systems

Overview

Every competitor built a dashboard. I bet on the chat.

Every competitor was building sellers a dashboard to log into and abandon. I bet the opposite: you should run an entire business from a chat.

Chidi is an AI assistant that runs a seller’s shop inside the chat their customers already use, answering, taking orders, handling payments, while the seller stays in control just by chatting back.

The hard part was never the replies. It was letting software act on its own and still be trusted with the money, so I designed and shipped it in code, where voice and mechanics can’t drift apart.

An assistant that sells for you is only useful if you can trust it with the money.
MP4 · placeholdera customer self-serving in Telegram, ask → order → bank details → receipt, while the seller sleeps.hero-demo.mp4

The problem

Sellers run a whole business from a DM, until it breaks at fifty orders.

Across Lagos, Accra, and Nairobi, tens of millions of sellers run a business inside Telegram and WhatsApp DMs, often on patchy data.

It works until it doesn’t. A buyer messages “abeg, the red Adidas still dey?” at midnight and gets no reply. Orders live in someone’s head, and there’s no record of who paid. Fast at five orders, drowning at fifty.

Every tool answers by bolting on a CRM the seller never opens. My constraint was harsher: if a feature made the seller leave the chat, or broke when the network did, it didn’t ship.

IMAGE · placeholdera flooded DM inbox at fifty orders, half of them unanswered overnight.flooded-dms.png

Research

Three cities, the same shop running on a DM and a patchy signal.

I didn’t start with screens. I shadowed how sellers in Lagos, Accra, and Nairobi actually run a shop: a phone, a WhatsApp or Telegram thread, a notebook for orders, a bank app to confirm transfers. The chat already was the storefront, the catalogue, the checkout, and the customer record, all in one thread, on a connection that could drop mid-sale.

The same few behaviours showed up in every city. They became the rules the product wasn’t allowed to break.

What the sellers taught me

They sell while they sleep.

Buyers message long after the shop closes, and the unanswered midnight question is the most common lost sale. Whatever I built had to be the one awake.

They won’t open a second app.

The chat is the only surface they tend; the notebook is the backup, abandoned past fifty orders. A separate dashboard goes unopened.

Proof of payment is the product.

A sale closes when the buyer screenshots a clean confirmation, the receipt, not the product page, is what gets forwarded to the next buyer.

IMAGE · placeholderfield notes / the real seller setup, phone, chat thread, notebook, bank app.field-notes.png
IMAGE · placeholderthe synthesis, three behaviours that became the rules the product couldn’t break.research-synthesis.png

Exploring directions

Three forks settled the product: where it lives, how far it acts, where it starts.

Three decisions shaped everything after.

The three forks

Where it lives

A standalone app is one more login to forget. I chose to live inside the chat the seller already trusts, accepting someone else’s interface as the price of zero behaviour change.

How far it acts

Fully manual is just a nicer inbox; fully autonomous loses the seller the first time it’s wrong about money. So I drew the line at the money: act freely, pause on anything that pays.

Where it starts

Telegram first, its bot platform lets a seller go live in minutes, with WhatsApp and Instagram next.

IMAGE · placeholderthe directions explored, app vs chat, manual vs autonomous, channel order.directions.png
IMAGE · placeholderlo-fi sketches of the chat surface, the buyer and seller sides.chat-sketches.png

Run it from a chat

One assistant runs both sides of the chat, the buyer’s and the seller’s.

Chidi works both sides of the conversation, the same assistant on each.

Underneath is one brain and one source of truth, customers, catalogue, orders, payments, and a memory of every buyer’s history, so a returning customer is greeted, not re-interrogated.

If you can chat, you can run the whole business.

Both sides of the chat

For the buyer

A self-service shop inside Telegram: browse, ask “how much to Lekki?”, get an instant answer, and order 24/7, awake or not. Chidi checks stock, sends bank details, and matches the transfer to the order.

For the seller

No dashboard to learn. They run the business by chatting: “add 12 earbuds at ₦24k,” “who hasn’t paid?”, “broadcast the new drop.” A morning brief reads back what Chidi handled overnight.

MP4 · placeholderbrowse → ask → order → pay → receipt, in Telegram.buyer-self-serve.mp4
Buyer self-serve
MP4 · placeholder“add 12 earbuds at ₦24k” → “Done. Stock now 47.”ask-chidi.mp4
Run it by chat
IMAGE · placeholderwhat Chidi handled overnight, chased payments, sent thank-yous.morning-brief.png
Morning brief

An agent you can trust with money

Chidi acts on its own, but the money waits for the seller.

Letting software answer customers is easy. Letting it touch money is the real design problem, and testing early builds with real sellers put the line exactly where it belongs: they loved the replies, but froze the moment Chidi might confirm a payment they hadn’t seen.

The guardrail

Chidi is autonomous, with the line drawn at the money. It replies, reserves stock, and drafts the next step on its own, but anything that moves money waits for the seller’s tap: a payment, a refund, a price change, a broadcast.

Every action leaves a quiet receipt with See and Undo, so the seller can always see what happened and pull it back.

The receipt

The payment is the trust moment. When a transfer is matched, through Paystack or bank reconciliation, the buyer gets a confirmation formatted like proof, not a chat bubble, the thing they screenshot.

It is the pattern the rest of my work is moving toward: an agent that acts, with a human holding the keys to the money.

I won’t move money or send a broadcast without your OK.
IMAGE · placeholderthe approval guardrail holding a payment confirmation for the seller’s tap.approval-guardrail.png
IMAGE · placeholderthe branded receipt, formatted like proof, the moment a buyer screenshots.receipt.png
IMAGE · placeholderhow Chidi reads a message, intent → check stock → prepare → the money guardrail → act.intent-flow.png

Built for a bad network

On patchy data, a missed message is a missed sale.

The second hard call was the network. These sellers work on patchy data, and a missed message is a missed sale.

So Chidi is offline-first. The inbox keeps working with no connection: every action, reply, fulfilment, broadcast, payment-confirm, drops into a local outbox, and everything syncs the instant the connection returns. No lost orders, no “message failed.”

IMAGE · placeholderthe offline inbox, messages queued, “3 will sync the moment you reconnect.”offline-inbox.png
IMAGE · placeholderthe offline-first outbox, every action queued locally and drained on reconnect.sync-diagram.png
IMAGE · placeholderthe component library in Storybook, built in code alongside the product.design-system.png

Outcomes

Sellers stay, because Chidi runs the shop while they sleep.

Sellers adopted Chidi without changing how they work, the chat stayed the same, the business behind it got real. Active sellers retain at 71% by day 30, across three markets: Lagos, Accra, and Nairobi.

I can ask Chidi what someone bought, their size, what they asked about before. When I follow up, it feels personal, like I remembered everything myself.Amadi K., eyewear, Lagos

In Nairobi, a seller raised her best product 12% after Chidi flagged she was underpricing. Zero complaints, more orders.

Next: WhatsApp and Instagram on the same brain, and deeper cross-border reconciliation.

IMAGE · placeholdera returning buyer greeted by name, the timeline carrying their history.returning-buyer.png

Reflection

What I learned.

Chidi is where I first shipped an agent that handles a real business’s money, with the controls to make it safe, the exact problem I’m now building Tabs around.

Trust is the product, not a feature.

With an agent that touches money, where you draw the line between acting and asking is the design. Everything else sits on that one call.

Build for the network you have.

Offline-first wasn’t a nice-to-have; it was the difference between a tool sellers could rely on and one more thing that fails at the worst moment.

Design and code, one pass.

Designing and shipping the front-end myself closed the gap between right in Figma and right in a live thread, in hours, so voice and mechanics never drifted apart.