The working problem
An incoming lead is not yet a client. Mission Control is araNET’s private operations tool, and this design note concerns its public sample presentation. The example dashboard contains fictional amounts, counts and tasks.
The distinction matters in a small-screen overview. A list of enquiries answers “who might need a response?” An active-client record answers “what work have we agreed to do?” Combining them into one total would hide that difference before someone even opened a record.
A mobile-specific direction
The sample dashboard groups four summaries above a daily-work list: collected, outstanding, active clients and open work. The labels carry the meaning. A zero collected amount is paired with its month and paid-record count; an outstanding amount is paired with the number of open invoices. These are sample values, not araNET revenue.
That pairing makes the summary more inspectable. An invoice count and an amount answer different questions. Likewise, an active-client count should not quietly include every CRM relationship. The sample distinguishes active clients from the larger CRM record count rather than presenting one ambiguous customer total.
Daily tasks appear separately, with a date, time and next-action arrow. The tradeoff is deliberate: the dashboard introduces the work while individual records hold its detail. The bottom navigation keeps Command, CRM, Inbox, Work and Calendar available without turning every summary into an edit form.
What we can show
The original sample capture shows hierarchy and labels. It cannot establish whether a tap opens the correct record, whether invoice totals reconcile or whether permissions hide another person’s work. Those need separate interaction and data checks.
For a similar business dashboard, review one handoff: an enquiry arrives, someone decides whether to accept the work, and an accepted relationship receives its project context. Write down who can make that decision and where an unaccepted enquiry remains visible. Then check that the overview counts use those same definitions.
The useful design lesson is to make each summary lead to a specific question and record. A phone overview can remain short when its labels preserve the difference between relationships, agreed work and money owed.
