Sample · Workflow readiness write-up

What the write-up looks like

A composite example, written to show the format. The firm below is invented and so are its numbers. Yours is written from the workflow you describe, and any figure in it is one you gave us.

The firm

Who: a 30-person accounting and advisory practice
Stack: Microsoft 365, a practice platform, one very important spreadsheet
Biggest cost: client onboarding and document chasing
Scale: about 18 hours a week across the team, every week
What broke last: a new client's paperwork bounced between three inboxes for eleven days
Approvers: the managing partner and the operations lead

Ranked automation candidates

1 · Build first

Client onboarding and document chasing

An intake that assembles the checklist per client type, sends the requests, chases what hasn't arrived on a schedule, and files what comes back where it belongs. A person reviews the completed file before the client is told they're done. It is first because the firm named it as its own biggest cost, not because of a figure anyone calculated.

2 · Next

Meeting notes into the system of record

Client calls produce follow-ups that live in whoever attended. Transcripts drafted into file notes and task lists, approved by the person who was in the meeting before anything is saved or assigned.

3 · Later

Recurring status reporting

The monthly client status emails are assembled from data the firm already has. Drafted automatically, sent only after review. Smaller win, so it waits its turn.

What stays human

Anything a client reads gets approved by a named person before it goes out. Advice stays human entirely. Software that runs the mechanical part of the work still should not speak for the firm.

The boundary

Not automated, by design: anything touching the tax filing system of record, and anything under the firm's professional review obligations. The write-up draws this line explicitly, worded the way the firm described it. It records the boundary. It does not rule on whether the firm is meeting its obligations, which is a question for the firm's own advisors. Yours will name your own lines: supervision, audit scope, whatever cannot leave the building.

What would have to be true first

Before any of it
The checklist that varies by client type has to be written down somewhere other than one person's memory. Nothing can be built around a rule nobody has recorded.
Before the first
A named approver for outbound client messages, and agreement inside the firm that the approval step stays in place once volume rises rather than being the first thing dropped.
Before the second
A decision about whether call recordings and transcripts may be stored at all. That is a question about the firm's own obligations, and it is not one we answer for them.

Where our products fit

The real write-up names which Simple Intelligence products address the candidates above, what state each one is in today, and what would have to be true before it could be used. Where nothing we make fits, it says so plainly. That section is blank in this sample because it depends entirely on the workflow being described, and a sample answer to it would be a sample of a guess.

Want yours?

Start with the two-minute readiness check. It answers you on the spot, with nothing to book. The longer assessment covers the same ground in more detail and is also free.

Take the readiness check