DEV Community

Ujjwal Dubey
Ujjwal Dubey

Posted on

Designing for the Owner Who Never Opens the Dashboard

#smallbusiness

I work at NxFlowAI. These are notes from building automations for owners who run everything from their phone.

A recurring lesson from small-business projects: the owner will not log in to your dashboard. They run a shop, a clinic or a studio. Their attention lives in WhatsApp. If your system needs a browser tab to be useful, the approvals will sit unread.

Put the interface where the owner already is

Instead of a dashboard, I now default to three message types sent to the owner's chat:

  1. Approval requests. A short summary, the proposed reply, and two actions: approve or edit.
  2. A daily digest. What came in, what was handled automatically, what is waiting.
  3. Exception alerts. Something failed, or a customer asked for a human.

Each should be readable in under half a minute on a phone screen.

Anatomy of a good approval request 

Customer: Meera (Instagram)
Asked: custom size for the tan tote + discount for two
Draft: "Thanks Meera, checking with our maker and will reply today."
Needs from you: size feasibility, price
[Approve draft] [Edit] [Call customer]
Enter fullscreen mode Exit fullscreen mode

Short, specific, with the decision isolated. No raw conversation dumps.

Make the digest boring and consistent

Same time each day, same format, same order. The owner learns where to look. Include the unanswered count first. If it is zero, say so. A digest that sometimes changes shape gets ignored.

Handle absence

Owners travel, fall ill, or switch off on festivals. Build in:

  • A named backup approver.
  • A timeout rule: if nobody approves within the agreed window, send the safe holding reply again or escalate to the backup.
  • A pause switch the owner can flip from the same chat.

Roll it out in small steps

Start with approvals only, for one reply type. Add the digest once the owner is answering approvals reliably. Add exception alerts last, and only for failures the owner can actually act on. Each step earns attention before you ask for more of it.

What to avoid

  • Notification volume that trains people to mute the chat.
  • Approval requests without the original customer message available one tap away.
  • Anything that requires the owner to remember a password under stress.

Instrument it

Log how long approvals wait. If items age, the problem is usually design, not laziness: too many requests, unclear summaries, or the wrong time of day.

If you are mapping this kind of setup for a client, it helps to start with who actually makes each decision. Our overview of what we build describes how we approach that, working remotely from Mumbai.

The best interface for a busy owner is the one that feels like a message from a reliable colleague.

Top comments (0)