A phone page that tells consultants who to call next

A screen of totals doesn’t tell a consultant who to ring. How a whiteboard sketch became a read-only phone page with a ranked call list, and why most other screens were cut.

27 Oct 2026 4 min readCase study · AI growth agent

The problem

Consultants needed to know who to call next, not another screen of totals.

The solution

A read-only phone page per consultant, copied from a whiteboard sketch, with a ranked call list.

7 dayswith nothing logged puts a deal on the list
~140on-screen figures matched by separate SQL
0writes back to Zoho

A screen of totals tells a sales consultant how the month is going. It doesn’t tell them who to ring this morning. AHA’s consultant page was built for that: a single page on a phone, in plain words, with a short list of who to call first.

Start from a whiteboard, not a schema

The current page began as a whiteboard sketch, and the build copied it top to bottom. Two rules shaped it: phone first (every tab checked at 320, 375 and 430 px wide) and read-only. The page never writes to Zoho. Wrong deals get fixed in Zoho, and the page catches up on the next refresh.

A consultant’s login opens their own page; the admin can switch between consultants or see the whole team. I directed the work, and Claude Code wrote much of the code.

What’s on the page

  • The target bar. Closed, likely to close and still missing for the month, with a line marking the days gone. Under it, a best case (closed plus likely) and a worst case (closed only).
  • Closing date passed. Open deals whose closing date is behind them, in red, with one instruction: move the date in Zoho or close the deal. Left alone, such a deal drops out of every projection.
  • Closing probability. Open deals by the consultant’s own call: this month, the next two or three months, or no timing yet.
  • Your week. Demos, proposals and wins since Monday, against the same days last week.
  • Ask for a referral. Clients whose deal closed two to four months ago.
  • Architects and designers. Partners named on the consultant’s deals, with the quiet ones (a past win, nothing in 90 days) marked as worth a call.

Call these first

It’s a ranked list:

always first:  deals waiting for the advance
then, after 7 days with nothing logged
(no note, call, stage change or demo):
  called for this week or this month
  a fresh demo still waiting for a proposal
  a proposal or a negotiation
  rated 4 or 5
order:  by step, then the bigger deal
card:   top five, the rest one tap away

Each row has a tag saying what to do, such as “Collect the advance” or “Call once more”, and one line on why it’s there. No call buttons, no phone numbers: an earlier Today screen with call and WhatsApp buttons was retired because the BI is a report, not a CRM.

Why 7 days? For every deal open on 1 June, 1 July and 1 August 2026, we compared how often it was won within two months against how long it had gone with nothing logged. The odds dropped sharply after a week of silence and kept falling. It’s a correlation, not proof that calling saves deals, but a sensible line.

The scoreboard and the review

The second tab, Closed, is the scoreboard: won against lost for the period and the one before, split by rating, source, value, the consultant’s call and time. At its foot, a review of lost deals shows every Zoho note on the deal and its lead, and flags the ones worth a second look, such as a note written after the loss (the client may be back). Since 15 Oct, each consultant’s login shows the review for their own deals.

What got cut

More screens were built than kept: Growth Brief mock-ups, an Explore drill-down, follow-up queues that became the Today screen, an ad-spend screen, a funnel, an Ask chat, and a 3D map tab, rolled back. Each went when it didn’t earn its place; Funnel, Ads and Ask went in one decision, so the effort could go into one page.

Checking what the phone shows

A preview mode loads made-up deals under a red “made-up numbers” ribbon, as a consultant or as the admin, so layouts get tested without real data.

On 16 Oct, Claude Code read about 140 figures off the rendered page, for the whole team and one consultant over two months, and recomputed each with separate SQL. Every figure matched. The check still caught two small things: a tile and the review below it counting different groups under one label, and a split that silently dropped a deal with no lead date. Both were fixed. The rules behind the numbers are in One meaning per number.

What I’d keep

  1. Draw the page before querying anything.
  2. End in an action. A ranked list with reasons beats another chart.
  3. Stay read-only. The CRM stays the one place to fix a deal.
  4. Cut screens that don’t earn their place, even finished ones.
  5. Check the rendered page, not just the query.

More problems, more solutions.

All posts

Non-brand clicks are the SEO number that matters

+183% non-brand clicks

A path-traced showroom in a TV browser

22 renders, path-traced offline in about 2 hours