Dualsell

June 2026 to Present

You and 6 others viewed

I led product and strategy for Dualsell, turning an observed problem in small-business sales into a clearer product direction.

Small shops often record sales manually (or not at all) even when the order and payment already happened digitally. We redirected Dualsell around that behaviour: capturing useful sales data through familiar actions instead of asking the business owner to maintain another system.

Rethinking how Dualsell captures sales data: customer orders through WhatsApp, QR or staff become one record of items, customer, payment and fulfilment. AI insights use the same records.
Product direction, currently in development.

Moving the point of data entry

We started with an AI CRM. The idea was for business owners to enter their orders, then ask the assistant what sold and how the day went. I focused on the step that made those answers possible: how the data gets there.

Original direction
  1. Customer orders
  2. Seller types it in again
  3. AI answers questions
The direction I set
  1. Customer orders
  2. Order creates the record
  3. AI uses that record

Capture it while it happens.

The change was at the beginning of the flow. Customers already provide order details when they buy; those details should become the business record.

What I did

  • Redirected the product toward the manual sales-data entry problem
  • Designed a WhatsApp-native order-capture and payment-confirmation flow
  • Shaped a QR storefront that fits existing customer behaviour
  • Connected product decisions to positioning and an early go-to-market path

Start where the customer already is

I made WhatsApp an order-entry point because that is where many customers already buy. A QR storefront would let walk-in customers choose for themselves, while staff-assisted entry would cover counter and phone orders. All three would feed the same order system.

WhatsApp, QR storefront and staff-assisted orders feed one Dualsell order engine. Product, size, quantity, delivery and payment details become one order record in a shared seller inbox for sales, inventory and insights.WhatsApp, QR storefront and staff-assisted orders feed one Dualsell order engine. Product, size, quantity, delivery and payment details become one order record in a shared seller inbox for sales, inventory and insights.

Understanding how buyers shop helped me rethink how Dualsell captures sales data. I shifted the point of data entry to where buyers already live, from WhatsApp conversations to walk-in purchases.

Here’s how the buyer flow works:

Buyers pick items, choose pickup or delivery, create an order with payment pending, then pay by Paystack or cash. Dualsell records these details along the way, keeping order, payment and fulfilment statuses separate.Buyers pick items, choose pickup or delivery, create an order with payment pending, then pay by Paystack or cash. Dualsell records these details along the way, keeping order, payment and fulfilment statuses separate.
From a customer’s choice to a recorded sale. The order exists before payment is confirmed.

I also separated order, payment, and fulfillment status. An order code identifies an order. Online payment needs confirmation from Paystack, and cash needs confirmation from an authorized staff member. A paid order can still be waiting for pickup.

Explore an example order
Three entry points. One order record.Illustrative flow

An order starts in a conversation

  1. Choose from the live product list
  2. Select size, flavour, and quantity
  3. Choose pickup or delivery
Dualsell order

A cake for pickup

Example order
Channel
WhatsApp
Item
Chocolate cake
Quantity
1
Receive by
Pickup

The conversation captures the details the seller would otherwise copy into the CRM.

OrderSubmitted
PaymentPending
FulfillmentTo prepare

An order code is not payment proof. Wait for trusted payment confirmation.

Switch between the proposed entry points, then simulate a payment confirmation. Only the payment status changes; the order still needs to be prepared and handed over. Example details are illustrative.

What we’re building now

We’re developing WhatsApp ordering, the QR storefront, staff-assisted orders, and payment confirmation concurrently. WhatsApp and the QR storefront are our main priorities. I specified a shared order model so each channel can use the same products, payment rules, and order history.

  • WhatsApp ordering

    Main priority: capture product choices and order details within the conversation.

  • QR storefront

    Main priority: let walk-in customers browse, choose, and create an order by scanning a code.

  • Staff-assisted orders and payment confirmation

    Being developed alongside both entry points, using the same order records and payment rules.

Current development priorities, September 2026. The AI assistant is intended to use the same order, payment, stock, and fulfillment data.
Behind these visuals

Adapted from my product-direction document dated 22 July 2026, particularly “The point of data,” “The buyer flow,” and “The three things we must keep separate.” The development priorities reflect our current focus in September 2026. These are illustrations of the product direction, rather than screenshots of the live product.

What I learned

A product gets sharper when the team stops defending its first idea and follows the real behaviour underneath the problem.
Role
Co-Founder, Product & Strategy
Period
June 2026 to Present