What every guide is made of
Drawn in code, not filmed
The email, the ransom screen, the claim form: drawn in the page, so it loads fast on a prepaid bundle, stays sharp on any screen, and changes when your product changes.
Scroll, tap or press Play
Each step changes what the drawing shows. The customer controls the pace. Anyone who prefers reduced motion gets the same steps without the animation.
Ends in the action you want
A WhatsApp message, a booking or a quote request, pre-filled with what the customer chose and tried, so your staff start at the answer instead of the questions.
You see what it produced
Plays, hand-offs and "it fixed it" taps are counted in your own analytics, after visitor consent. The monthly report shows you what the guide did, in numbers.
Case study · MobiDokta, device repair
A repair shop's homepage that shows customers the fix before they message.
The problem
A repair shop hears the same messages all day: a frozen screen, No Service, an app that will not close. A force restart clears some of those without a repair. The rest need a technician, and the customer only finds out which after trying.
What we built
An iPhone 17 Pro Max drawn in code acts out the force restart: volume up, volume down, then holding the side button past the power-off slider until the Apple logo. Visitors drive it by scrolling, tapping a step or pressing Play, and the steps note the different method for older iPhones. If the restart does not fix it, one button opens MobiDokta's WhatsApp with a message that already says so, next to a free-diagnosis booking. No video; each play and each WhatsApp tap is counted.
Results
Measured from September 2026: demo plays, WhatsApp messages from the section, and customers who tell MobiDokta the restart fixed it without a visit. We publish the numbers after four full weeks of data. Until then, this shows what was built, not what it achieved.
Guide 01 · Protect clients from payment fraud
"New banking details? Check before you pay."
Built for a law firm or conveyancer to put on its own site. In a payment-diversion scam, a client receives an email that looks like it comes from the firm, with new banking details and a reason to pay today. The guide walks the client through that email and ends in the one check that stops it: a phone call to a number they already have.
The message your client sends you
On a firm's site this opens the firm's WhatsApp with the message ready to send, so the client never replies to the suspicious email. Here it goes nowhere.
Demonstration · fictional firm and addresses · nothing stored or sent
Sources: SABRIC, how to stay safe · SAnews, SABRIC warns of the change-of-banking-details scam · BusinessTech, law firm ordered to pay over R5.5 million to a victim of email fraud
Guide 02 · Incident response
"There's a ransom note on my screen." What to do first.
Built for an IT provider's client page or a company's staff intranet. The first minutes decide how far ransomware spreads and whether the evidence survives, and the person at the desk is rarely the one trained for it. The steps follow CISA's ransomware response guidance, in the order someone without IT training can carry out, and end in a message that tells the responders what has already been done.
The message your responders receive
On an IT provider's page this opens their emergency line with the message ready to send. Here it goes nowhere. In a live incident at your business now, go to data breach response.
Demonstration · general first steps, not a substitute for incident response · nothing stored or sent
Sources: CISA, #StopRansomware guide · No More Ransom, Crypto Sheriff · POPIA section 22 · What we do after these first steps: ransomware response
Where a guide earns its keep
The businesses we build for have one thing in common: somebody explains the same thing over and over, or a customer leaves because they did not understand the product. On the first call we ask for the number that proves it, so that after 30 days we can show whether the guide moved it.
| Business | The guide | The number we would track |
|---|---|---|
| Law firms and conveyancers | A "before you pay us" guide: how to confirm the firm's banking details by phone | Clients who phone to confirm before paying |
| Medical and dental practices | Before-your-visit, consent and how-we-handle-your-records walkthroughs | Reception calls a day |
| Accounting and tax practices | A document checklist for each return or engagement | Submissions held up by missing documents |
| Insurance brokers | A step-by-step claim guide with a document checklist | Claims sent back for missing documents |
| IT providers and their clients | Incident first steps, and the resets staff can do themselves | Tickets that were a simple reset |
| Device and IT repair shops | Self-fix steps, then a hand-off to a paid repair | WhatsApp chats a day that are basic questions |
Insurance guides explain a client's own claims process only. ASi Imperium is not an authorised financial services provider; insurance decisions require a licensed broker.
How we start: one guide, one outcome
Starting prices are below. The final price is set on the outcome we agree on the first call, such as questions answered or leads gained, not on hours. The first three pilots are discounted in exchange for letting us publish their numbers as a case study. Own it outright, rent-to-own or lease, as with everything we build.
One guide, one outcome
- One guide fitted into your existing site
- One hand-off: WhatsApp, booking or quote
- Counting set up in your analytics
- A 30-day report against the number you named
From R8,000
Built in 1–2 weeks
Kept current, month by month
- Everything in the pilot guide
- A monthly report
- Copy, product and price updates
- One small new step each month
From R1,500 / month
Ongoing, monthly
Buy, set up, troubleshoot
- Three to five linked guides
- One shared design across them
- A dashboard for every guide's numbers
From R35,000
Built in 4–6 weeks
Prices in ZAR, ex VAT.
Questions owners ask
How is an interactive guide different from a video or an FAQ page?
A video plays at its own pace and costs data; an FAQ page makes the customer find their own answer. A guide changes with what the customer tells it, works at their pace by scroll or tap, loads in tens of kilobytes rather than megabytes, and ends in one message or booking that already carries what they tried.
Will it work on our existing website?
A guide is a self-contained block of HTML, CSS and a small script. Custom-coded and WordPress sites take it directly, and most site builders accept a custom HTML block. Where one does not, we host the guide on its own page and link to it.
Does the guide collect personal information?
No. The guide runs in the visitor's browser and stores nothing. The hand-off opens WhatsApp or your booking form with a pre-filled message the customer can read and edit before sending. Usage is counted through your existing analytics, only where the visitor has consented. See our privacy policy for how this site handles consent.
Do you have results from guides already running?
Not yet. Our first guide went live on MobiDokta's homepage in September 2026. We publish its numbers after four full weeks of measurement, and we will not quote a percentage we have not measured.
Who owns the guide?
Your choice, as with everything we build: own it outright with the code handed over, rent-to-own over an agreed term, or lease it with hosting and updates handled by us and convert to ownership when you are ready. See how we build.
What would a guide do for your business?
Twenty minutes. We ask what customers ask you most, what it costs you to answer, and what they misunderstand that loses you a sale. If a guide will not move that number, we will say so.
More to try: live demos · websites we build · WhatsApp automation