System Lab
See connected workflows in action
Three lightweight, interactive demonstrations showing how business information can move through a clear process — with a record, a status, an owner and a next action at every stage. Built to be understood without any technical explanation.
How to read these demonstrations
Demo 1 — Primary industry
Solar enquiry-to-installation workflow
Select an enquiry record and advance it through the pipeline. Watch how each stage change updates the record, the pipeline counts and the activity history — the things a real solar business needs to answer “what happened to this enquiry?”
Pipeline stages
- New Enquiry1
- Qualified0
- Site Visit1
- Quotation Sent1
- Follow-up0
- Installation0
- After-sales0
Enquiry records
Amina Bello · L-231
Source: Website form · Current stage: New Enquiry
Enquiry detail
5kVA hybrid system enquiry — residence in Abuja. Budget indicated: mid-range. Timeline: within 6 weeks.
Activity — how updates flow through the record
- Enquiry captured from website form and recorded as L-231.
Illustrative demonstration using sample data. “Sahel Solar Supply” and all records above are fictional. A real system would adapt stages, qualification questions and notifications to your actual sales process.
What it shows
One record per enquiry, captured from any channel, with qualification detail, a stage and a full activity trail.
Why it matters
Quotations stop disappearing into chat threads, and follow-up becomes a visible, owned action instead of a memory.
Real-world adaptation
Stages, questions and notifications are matched to your actual sales process during discovery — distributors, installers and retailers differ.
Demo 2 — Booking
Enquiry-to-booking workflow
Walk through a booking as a customer would: choose a service, pick an available slot, confirm — and see the confirmation, reminder and follow-up actions the system queues behind the scenes.
- Choose service
- Pick a slot
- Confirm & reminders
Illustrative demonstration using sample data for the fictional “Meridian Consults”. Nothing you enter is stored or transmitted. A real booking system is adapted to the business's service model, channels and availability rules.
Demo 3 — Operations
Order-to-dispatch workflow
A dispatch board for a fictional delivery business. Select an order and update its status — the board, the record and (in a real system) the customer notification all move together, with no re-typing.
Today's dispatch board
- Received
- 1
- Assigned
- 1
- Picked up
- 1
- In transit
- 1
- Delivered
- 1
ORD-881 — Bisi Stores
2 × cement (50kg) · Drop-off: Yaba · Rider: unassigned
- Received
- Assigned
- Picked up
- In transit
- Delivered
Each update changes the record, the board counts and — in a real deployment — the message the customer receives, without anyone re-typing information.
Illustrative demonstration using sample data for the fictional “Harmattan Dispatch”. All customers, riders and orders are synthetic. Statuses, assignment rules and customer notifications are adapted per business.
Beyond the demos
Prefer a demonstration shaped like your business?
During a fit assessment or paid audit, we can walk through a demonstration built around your actual workflow — your stages, your channels, your roles. That conversation, not a generic demo, is where the real design begins.
Recognise your workflow in one of these demos?
Tell us which pattern matches your business — and where it breaks today. The assessment is free, honest and short.