Spreadsheet replacement
Replace the consulting delivery spreadsheet with a connected AI workflow.
Move consulting teams coordinating client work in sheets from fragile spreadsheet handoffs into a focused workflow with clearer ownership, live context, and connected execution.
Introduction
Delivery run from a sheet the client never sees.
Almost every consulting delivery process starts in a spreadsheet, and for a while that is the right call. A sheet holding engagements, workstreams, consultant allocation, milestones, and utilisation costs nothing, takes an afternoon, and fits the process exactly — because the person who built it is the person who runs it.
Each engagement gets its own copy of the same template, so there is no way to see across the portfolio without somebody manually consolidating twelve files. The sheet works while one partner runs every engagement and knows where each stands. It fails at the point where engagements outnumber what one person tracks, because overruns become visible only when the invoice is prepared.
What follows covers that transition for consulting teams coordinating client work in sheets: what the sheet holds, why it fails, what the replacement records instead, and — set out plainly further down — the case for leaving it where it is.
The problem
Four ways a consulting sheet costs margin.
A consulting sheet records hours and the business runs on margin per engagement, which is hours against a scope against a fee. The sheet holds the first and leaves the other two implicit, so a scope change absorbed in week three is invisible until the numbers are added up at the end.
Consultants log time weekly from memory, the engagement lead updates the status tab, and neither can see whether the engagement is actually profitable while it is still running.
The sheet holds engagements, workstreams, consultant allocation, milestones, and utilisation, and the authoritative version of most of it already lives in Google Drive or Slack. The time sheet says 140 hours, the engagement was scoped at 100, and the difference includes work that was agreed in a call nobody recorded.
You're likely here because
- Whether an engagement made money is known only after it ends
- Each engagement gets its own copy of the same template, so there is no way to see across the portfolio without somebody manually consolidating twelve files.
- When a row is stale, a consultant is double-allocated because two engagement sheets did not know about each other
The operating problem
Why the current process stops scaling.
Move consulting teams coordinating client work in sheets from fragile spreadsheet handoffs into a focused workflow with clearer ownership, live context, and connected execution.
Failure mode 1
Scope changes are absorbed silently
Work agreed in a conversation and never recorded is the most common source of margin erosion in consulting, and it is completely invisible in a hours-only sheet.
Failure mode 2
Margin is known only at the end
By the time the numbers are added up, the engagement is over and nothing can be done. The information arrives after the moment it would have been actionable.
Failure mode 3
Utilisation is tracked instead of outcomes
A fully utilised team on unprofitable engagements looks healthy in every measure the sheet holds, which is how service businesses grow revenue and lose money.
Failure mode 4
Knowledge stays with the consultant
What was learned on an engagement lives in a deliverable and a person. The next similar engagement starts from scratch at senior rates.
The record model
What the replacement holds that the sheet cannot.
- Engagement scope with a fee basis
- So hours can be read against what was agreed rather than in isolation, which is the only way margin becomes visible while it can still be acted on.
- Scope change with an agreement record
- Because work agreed in a conversation and never recorded is the largest quiet source of margin erosion in this business.
- Live margin position
- Hours against fee against scope, current rather than computed at the end, which is the difference between information and history.
- Time logged near the event
- Rather than reconstructed weekly from memory, since reconstructed time is both inaccurate and systematically under-recorded.
- Deliverable state
- So an engagement waiting on a client review is visibly waiting rather than appearing to be behind.
- Reusable component
- What repeats across engagements, captured, since rebuilding the same framework at senior rates is exactly what clients resent paying for.
- Recommendation outcome
- Whether advice was acted on, which is the most persuasive material available at renewal and which almost no consultancy records.
How it works
From tracking hours to tracking outcomes.
Step 01
Describe the consulting delivery process
Model the engagement as scope, fee, and hours together rather than as a time log. Margin is a relationship between the three and a sheet holds only one of them.
Step 02
Connect the systems of record
The calendar supplies where time actually went, the document store holds deliverables, the accounting system holds what has been invoiced. Reading the calendar makes time logging far less lossy.
Step 03
Build the operating surface
Engagements with live margin, scope-change records, and deliverable states. The live margin is what turns end-of-engagement information into a mid-engagement decision.
Step 04
Migrate the workflow, not just the data
Live engagements move with their current position. Closed ones stay as an archive, though their final margin is worth extracting as a baseline.
Step 05
Route the exceptions
An engagement crossing a margin threshold, or a scope change with no agreement record, surfaces to the engagement lead while it can still be addressed.
Step 06
Measure milestones delivered on their committed date
Margin per engagement against plan, and unrecorded scope changes found. Both are direct money and both are invisible today.
Implementation path
Instrumenting delivery without adding admin.
- 01
Record scope changes as first-class events with an agreement reference. It is the single largest recoverable margin item in most consulting businesses.
- 02
Compute margin live rather than at close. Information that arrives after the engagement ends is history rather than management.
- 03
Baseline final margin per engagement for the last year from the sheet. The distribution is usually wider than the partners expect and it changes what gets sold.
- 04
Capture what repeats across engagements as you go. Reusable structure is the difference between a practice and a business, and it can only be accumulated during delivery.
- 05
Run it alongside the sheet for one full cycle, then retire the file only after the parallel run holds.
Controls
Controls that matter.
Control 01
Scope changes recorded with an agreement reference, since work agreed verbally and delivered anyway is the largest quiet margin loss
Control 02
Live margin per engagement, so an overrun is a decision during the work rather than a discovery afterwards
Control 03
Client confidentiality enforced structurally across engagements, because reusable components raise the risk of cross-client exposure
Build with Launch
Turn the operating requirement into working software.
- • Build a consulting delivery app
- • Add forms, views, status, and workflow logic
- • Create role-specific dashboards
Operate with Grow
Keep the workflow connected after the interface exists.
- • Attach follow-up where the workflow touches revenue
- • Keep customer context connected
- • Measure activity through the same context
Connected context
Keep systems of record. Fix the gaps between them.
These are representative connections. UbiGrowth supports 700+ connections across business systems. Connection availability and permissions depend on workspace configuration.
The case against
When the spreadsheet is still the right answer.
If one partner runs every engagement and knows where each stands, the sheet is a record and that is enough. The trigger is engagements outnumbering what one person can track.
Examples
Three engagements that stop overrunning.
The extra workstream nobody billed
A scope-change record with an agreement reference converts absorbed work into either a variation or a deliberate concession, and both are better than an invisible one.
The engagement that lost money
Live margin makes an overrun visible in week three when the conversation is possible, rather than in week ten when it is a post-mortem.
The framework rebuilt for the fourth time
Capturing what repeats means the next engagement starts from a structure rather than a blank document, which is where consulting leverage actually comes from.
Measurement
Measure the workflow, not the demo.
Choose a baseline before implementation so speed, quality, exceptions, and downstream impact can be compared using the same definitions.
Model the value of moving repetitive spreadsheet work into a connected workflow.
Use the ROI calculator with your own workload, lead volume, close rate, and deal assumptions. The result is illustrative, not a guaranteed outcome.
Open the ROI calculator →Limitations and considerations
What tracking will not do for the work.
- Tracking does not improve advice. It protects the economics around the advice, which is what determines whether the practice can afford to keep giving it.
- Time logged near the event is more accurate and still imperfect. Treat margin figures as directional at the individual level and reliable in aggregate.
- Reusable components applied outside the situations they were designed for produce confident and wrong output. Bound their applicability rather than letting availability decide.
- Connector coverage varies: Google Drive, Slack, Google Calendar are representative rather than guaranteed, and the fields exposed depend on your workspace permissions.
Keep people in control of consequential decisions.
Automate bounded, observable work first. Keep explicit approvals, escalation paths, permissions, and auditability around financial, legal, clinical, employment, coverage, or other consequential decisions. The goal is faster execution with clearer control—not unbounded autonomy.
FAQ
Questions teams ask before moving off the sheet.
What is the largest recoverable item?
Unrecorded scope changes. Work agreed in a conversation and delivered anyway is the most common margin erosion in consulting, it is entirely invisible in an hours sheet, and recording it costs one field.
Why does live margin matter if we bill fixed fee?
Because a fixed fee makes the overrun yours. Knowing in week three rather than at close is the difference between a conversation about scope and a write-off, and only one of those is available while the work is running.
Should consultants log time differently?
Nearer the event and with less ceremony. Weekly reconstruction from memory is both inaccurate and systematically under-recorded, and reading the calendar removes most of the reconstruction.
How do we build reusable components without commoditising the work?
Productise the scaffolding and keep the judgement attributed and human. Clients pay for interpretation; what they resent is a senior person rebuilding a framework they have built four times before.
Do we still need Google Drive?
Yes. Google Drive stays authoritative for what it owns, and the new surface reads it through a governed connector rather than storing a second copy.
How do we know whether it actually worked?
Measure milestones delivered on their committed date against the baseline you took before switching, alongside manual updates removed and how often a record turns out to be stale.
Start with ARIA
Ask ARIA to build the replacement.
Describe what the spreadsheet is really doing. ARIA plans the operating surface, connects the systems that stay authoritative, builds it, and keeps it running.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Rebuild the consulting delivery workflow, not the file.
Record scope changes as events, compute margin live rather than at close, and capture what repeats while you are delivering it.