Watch the same designed sample move through the practice’s tracker, approval route, inbox and folders — all nine stages, with the checkpoints where people decide.
It is a front-end simulation—not a customer case study, live integration, or proof of delivered results. Named live deployments live on the Results page.
Front-end simulation with sample data; not a customer case study, live integration, operating test or proof of delivered results.
The storyboard below plays the whole week: the stale tracker, the identified record, the held draft, the human approval, the reply, the filing, the judgement call that stops with a person, and the Friday summary.
A quiet week · working demonstration
Simulation · sample data · 29 sec
Stage 1 of 9 Monday · 08:47 · The mess
01
The tracker is stale, the inbox is full, and two records are still missing from the same client case.
Same case QQ-SIM-042 · Expected · not yet found June bank statement Tracker · 2 records outstanding
Practice tracker8 days stale
Priya SharmaApril–June 2026 records
2 missingBuried replies · unclear ownership · no reliable Friday view
02
The agreed tracker—not a new Mach Lilies dashboard—provides the client, period, record and owner.
Same case QQ-SIM-042 · Identified · missing June bank statement Agreed tracker row
Priya SharmaJune bank statementApril–June 2026 records
MissingRule matched · record missing · approved chase template available
03
The wording follows the agreed template and stays held as a draft.
Same case QQ-SIM-042 · Chase drafted · held June bank statement Practice inbox · no message sent
Morning Priya — we’re still missing your June bank statement and receipt bundle. Could you send them over? Reply here and we’ll take care of filing.
04
Every client-facing message starts here. The demonstration can use a clearly labelled sample reviewer; a live launch cannot skip this gate.
Same case QQ-SIM-042 · Approval gate · held June bank statement Sample reviewer · Operations lead
Morning Priya — we’re still missing your June bank statement and receipt bundle. Could you send them over? Reply here and we’ll take care of filing.
Approved by sample reviewer · Operations leadSample role · Operations lead
05
The approval, wording, recipient and send time become part of the same audit history.
Same case QQ-SIM-042 · Approved chase · sent June bank statement Practice address · approval recorded
Morning Priya — we’re still missing your June bank statement and receipt bundle. Could you send them over? Reply here and we’ll take care of filing.
Approved by sample reviewer · Operations leadSample role · Operations lead
06
There is a document, a promise about the remaining receipts, and a question that needs professional judgement.
Same case QQ-SIM-042 · Attachment · received priya-sharma-june-statement.pdf Client reply · case QQ-SIM-042
June statement attached. I’ll send the receipts next week. Also, is the van repair an allowable expense?
priya-sharma-june-statement.pdfJune bank statement07
The attachment is stored in the agreed location, where technically feasible, and the same tracker row changes from two outstanding to one.
Same case QQ-SIM-042 · Attachment · filed priya-sharma-june-statement.pdf Clients / Priya Sharma / 2026–27 / Bank statements
Clients / Priya Sharma / 2026–27 / Bank statementsAgreed document location
08
The helper does not answer the expense question. It routes the message with context and takes no further action.
Same case QQ-SIM-042 · Document filed · question split priya-sharma-june-statement.pdf File retained · question routed to Kelly · client team
Exception · professional judgementStopped
“Is the van repair an allowable expense?”
Routed to Kelly · client teamClient question · source reply attached · no answer sent
The operating workflow stops where professional judgement begins.
09
The practice sees what moved, what remains outstanding, what needs a human, and the available history captured by the specified action record. Connected-system gaps remain visible rather than being assumed away.
Same case QQ-SIM-042 · Friday state · inspectable priya-sharma-june-statement.pdf Clients / Priya Sharma / 2026–27 / Bank statements · 1 record still outstanding
What moved, what is stuck, and what needs a human.
Front-end simulation with sample data; not a customer case study, live integration, operating test or proof of delivered results.
Mon · 09:04Client-facing action
Every client-facing message stays held throughout the live launch pilot. Only after that pilot is reviewed may the practice consider a workflow-specific, tested, written change for later operation.
Tue · 14:33Professional judgement
The system stops. The named human gets context, and the question stays with the qualified people at the practice.
The installed workflow has things you can inspect. These sample formats all come from case QQ-SIM-042.
The exact chase, reviewer, recipient and send time.
priya-sharma-june-statement.pdf
Clients / Priya Sharma / 2026–27 / Bank statements
The client’s question, why it stopped, and the named owner.
What moved, what remains outstanding, and what needs a human.
Quiet Quarter is scoped around familiar work surfaces first. Exact access, any direct integration and any extra tooling are confirmed before build.
These are familiar work surfaces, not a fictional Mach Lilies dashboard. Complex API work is scoped separately.
Implementation timing is confirmed in the signed proposal after access, scope, dependencies, and the live approval-mode pilot are reviewed. This page does not promise a delivery date. Delayed access, unsupported systems or scope changes can extend it.
We look at the chase volume, tools and client mix. If the workflow is not worth automating, we say so.
Agree who is chased, in what tone, who approves, where records go and what must stop for a person.
Run a controlled pilot with client-facing messages held for your team.
Review the outputs and exception rules before another workflow is added.
Week 1
Every client-facing message stays held for your team throughout the live pilot. Launch does not include autonomous sending.
Week 2
We review attempted and completed writes against separately agreed approval, reconciliation, and failure rules. A permitted write can still fail or need correction.
Week 3
We tune which replies are escalated to staff, such as unclear, sensitive, angry, unusual, or out-of-scope messages.
Week 4
You review the available evidence against the signed acceptance plan. Only after this live approval-mode pilot may the practice consider a specific, tested, written change for later operation.
The clock starts at go-live, means live days rather than working days, and the period is measured in human-approval mode.
Bring us one repeatable chase loop. We will tell you whether it is worth installing, what can move safely, and what must stay human-led.