Quiet Quarter checks what is missing, prepares and follows up on client requests, classifies replies, attempts agreed filing and tracker updates, and routes exceptions to your team—inside the inboxes and systems you already use.
Ready to talk? Book an AI workflow assessment. No client records or system access needed.
Client-facing messages held for your team. See the control evidence and limits.
Simulation · sample data · 15 sec loop
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.
Named deployment evidence
These are adjacent deployments, not promised UK Quiet Quarter results. Each card keeps its source and transferability limits beside the metric.
1-800Accountant
From unread query to review-ready response.
Client-reported and not independently audited; measurement period, sample detail, source detail not held, and calculation formula not supplied. This adjacent live deployment is not Quiet Quarter, not a UK-practice result, and not MTD proof. The $666K figure is estimated annualised gross staff-capacity value, not an independently audited cash saving; it is not cash saved, payroll reduction or revenue.
The Helpers prepare drafts; people retain control of client-facing decisions.
inDinero
Two AI Helpers coordinate the payment chase.
Client-reported and not independently audited; measurement period, sample detail, source detail not held, and calculation formula not supplied. This adjacent live deployment is not Quiet Quarter, not a UK-practice result, and not MTD proof. The 1,780 figure is reported network population, not cases; the 21-person team and two Helpers are wider-process scope, not replacement scope, and financial validation, approval and release remain human-controlled.
Financial validation, exceptions and payment decisions remain with people.
This designed sample shows where the AI-supported workflow acts, where a person approves, and where professional judgement stops the workflow. It is not a customer case, live integration or result.
AI agent execution trace
Illustrative demo Synthetic data Not live proof
See how a bounded AI agent could move routine records work forward while a human keeps client-facing approval and professional judgement.
Execution log
· Read
The agent reads only the agreed source and fields for this run.
Quarterly records tracker
· Compare
The tracker state is compared with the agreed period and reminder rule.
Rule match
June bank statement remains missing after the sample cut-off.
Proposed next action: draft a reminder. No message is sent at this stage.
· Draft
The draft is grounded in the tracker finding and held for review.
· Review
A person remains accountable for the recipient, evidence and wording.
Approval record
Approved by sample reviewer
· Classify
The response is separated into record, promise and judgement routes.
Synthetic reply
“June is attached. I’ll send May on Friday. Can I claim the van repair?”
· Write
Only the agreed destination and tracker fields are eligible for an attempted write.
Permitted changes
File destination/Sample client Alpha/2026 Q2/Bank/June-statement.pdf
Illustrative attempted write under an agreed rule; not universal system authority.
· Escalate
The agent stops where professional judgement begins.
Judgement queue
Client question: “Can I claim the van repair?”
Status: Awaiting accountant review
No answer drafted, no answer sent and no tax position recorded by the agent.
Operating boundary
AI-assisted
Within named sources, fields, destinations and approval rules.
Human-owned
With a visible hand-off whenever the workflow reaches its boundary.
Illustrative execution demo using synthetic data; not a customer case study, live integration, operating test or proof of delivered results. Real access, permissions, approval and write rules are agreed and tested before use.
Inspect the complete Monday-to-Friday workflow and implementation path →
After the reminder
A scheduled reminder covers the send; Quiet Quarter is scoped around the subsequent agreed loop—when a reply arrives, under written rules and with professional judgement left to the practice.
Scope summary. After an approved request or reminder is sent, Quiet Quarter is scoped to handle an agreed reply loop: identify in-scope contents, attempt permitted filing and tracker writes, route exceptions to a named person and produce the agreed Friday summary. Client replies and write completion are not promised, and professional judgement stays with the practice.
At launch, every client-facing message is held for practice approval. Once approved, the agreed request or reminder is sent through the scoped route.
If a reply arrives through the agreed inbox route, it enters the scoped workflow. Client response is not a controllable workflow output.
In-scope contents are classified under the written rules. Unclear, sensitive, unusual or out-of-scope material becomes an exception.
A permitted filing write is attempted under separately agreed approval, reconciliation and failure rules, and only where technically feasible.
A permitted tracker write is attempted under its separately agreed approval, reconciliation and failure rules. A failed or unavailable write becomes an exception.
The workflow stops and hands the item, source context and available status to the named human owner. It does not make the professional decision.
The agreed Friday progress summary reports available workflow outputs, outstanding items and named exceptions. It is an operating output, not proof of a customer outcome.
This is the approved service scope, not evidence that a particular workflow has executed or that every step completes. The scope does not promise a client reply. Filing and tracker writes are permitted attempts under separately agreed approval, reconciliation and failure rules; filing is attempted only where technically feasible. Exact access, connection methods and limitations are confirmed before build. Professional judgement stays with the practice.
Price the full chase drain — direct hours plus context switching, rework and proofreading — then compare it with retained approval work and a credible destination for released capacity.
A rough cost model that starts at zero. Enter the hours you can see on the chase work itself — then we price the full drain, not just the clocked minutes.
Starting state: workload and cost fields are blank; the calendar conversion and cash-destination share are labelled illustrative presets.
Leave blank if unknown. Decimal values are accepted.
Use a loaded staff cost; leave blank if unknown.
Illustrative calendar preset; change it if your planning convention differs.
Outputs start from the values in these fields. Full chase-loop cost applies a labelled ×3 modelling factor; advanced released-capacity figures stay on direct hours. No practice workload or saving is assumed.
Why full cost is higher than clocked time
Direct hours × 3. Modelling assumption for hidden drag around each chase — not a measured result for your practice, and not applied to released-capacity or cash-effect figures below.
Under 8 staff hours a week, a paid setup rarely earns its keep — a good checklist and an off-the-shelf assistant are usually the better buy, and we say so.
Between 8 and 22 hours a week the case depends on your loaded rate and chase volume. The readiness scorecard gives you a structured read before a chase-loop assessment.
At 23 or more hours a week, the workload sits squarely in the band Quiet Quarter is built for. The scorecard or a chase-loop assessment is the sensible next step.
Owner-approved screening model · not observed proofThese are owner-approved screening rules and modelling assumptions, not evidence of typical workload, savings, customer outcomes or delivery capacity.
Extend your numbers across the initial term: the whole fee, your own setup and approval time, and the difference between released-capacity value and a possible cash effect. Every figure here is arithmetic on your inputs — a planning aid, not a promised outcome.
Subtracted from each released-capacity scenario and added to gross break-even.
Valued once at the hourly cost you entered.
Illustrative preset. Raise it only where released time has a credible cash destination.
Optional. Leave blank when there is no software route to compare.
Time becomes cash only where it displaces paid cover — overtime, temporary help, a planned hire — or becomes billable work. Start at half unless you have a firmer plan.
If software you already run solves this safely and economically, keep it — we say so.
| Scenario | Share | Modelled gross hours/week | Net released capacity/week | Released capacity value/month | Possible cash effect/month |
|---|---|---|---|---|---|
| Conservative | 30% | — | — | — | — |
| Planning | 50% | — | — | — | — |
| Strong | 70% | — | — | — | — |
The configured initial-term fee is £8,789, excluding VAT: eleven paid monthly periods after the free measured period, with the configured setup treatment applied.
Owner-approved derived tariff total£8,789 excludes VAT and is the configured initial-term fee from eleven paid monthly periods after the free measured period; proposal-specific third-party costs remain separate where stated.
Twelve monthly fees at the current tariff total £9,588, excluding VAT; this is an arithmetic comparison, not the initial-term invoice total or a customer outcome.
Owner-approved derived tariff total£9,588 excludes VAT and is an arithmetic twelve-month tariff comparison at the current monthly fee; it is not the first-term invoice total or a statement of customer outcome.
The first 30 live days are free and measured in human-approval mode.
Owner-approved current termThe clock starts at go-live, means live days rather than working days, and the period is measured in human-approval mode.
The 12-month initial agreement starts at go-live.
Owner-approved current termThe initial term starts at go-live; the signed agreement governs termination, dependencies and any contract-specific consequences.
On your numbers, the full initial-term cost needs — gross hours a week; the recurring fee needs —. If 50% has a cash destination, the recurring cash-effect break-even needs — gross hours a week.
| Scenario | Possible cash-effect position / initial term | Modelled cumulative payback |
|---|---|---|
| Conservative | — | — |
| Planning | — | — |
| Strong | — | — |
Priced software route: — a month (— across the modelled initial term). On that route your team still owns sending, classifying, filing and exceptions.
A monitored setup still costs your team time — approvals, exceptions and the weekly summary. Every scenario nets your weekly approval estimate out of the released hours.
Released capacity value and possible cash effect are separate: Time released and realised cash effect are different things. The released-capacity column prices every net hour; the possible-cash-effect column keeps only the share you entered for time with a credible cash destination. Recovered minutes scattered across a week do not automatically create a saving.
We do not yet publish measured results for this workflow. Where a useful baseline exists, an estimate may be reviewed in the chase-loop assessment, but it is not a promised saving. The measured launch-period review against a signed acceptance plan, not this page, is the evidence that matters for your practice.
This calculator is illustrative only. It does not promise a number of hours released. The ×3 full-cost factor models context switching, rework and proofreading around each chase; it is not itself a saving and is not used to inflate released-capacity value. Actual impact depends on workflow scope, data quality, staff usage, approval speed and client behaviour.
Every output is arithmetic on user inputs and explicit assumptions. Time released is not cash saved, payroll reduction, revenue, avoided headcount or a promised outcome.
Illustrative only; no outcome is promised. Use your workload in the calculator →
A managed AI agent that runs an agreed client-record chase loop with human approval at launch.
Price and commitment, plainly
Quiet Quarter costs £799 per month, excluding VAT.
Owner-approved current tariff£799 per month is excluding VAT, applies to the signed scope, and is not a was-price comparison or a statement of total customer cost.
Setup included
Owner-approved current tariffSetup is included in the current offer; proposal-specific third-party or tool costs are separate where stated in the signed scope.
The first 30 live days are free and measured in human-approval mode.
Owner-approved current termThe clock starts at go-live, means live days rather than working days, and the period is measured in human-approval mode.
The 12-month initial agreement starts at go-live.
Owner-approved current termThe initial term starts at go-live; the signed agreement governs termination, dependencies and any contract-specific consequences.
Live day 60 is the dependency-adjusted output-floor review that can open the approved conditional exit process.
Owner-approved conditional exit termExit is not unconditional: it requires a recorded miss within Mach Lilies' responsibility, five business days' notice and an unsuccessful ten-business-day cure review; the signed agreement controls.
Read the complete commercial timeline and signed-term boundaries →
One signed, staged chase workflow across agreed inboxes, trackers and document locations.
Recurring email-led chasing, a reliable tracker, useful weekly volume and a named owner.
No source of truth or owner, mainly offline chasing, very low volume, or unsupervised sending and professional judgement.
Workflow one launches first in human approval mode. Each additional workflow included in the signed scope launches only after the preceding workflow passes its stability review; dates are proposal-specific.
See the complete inclusions, exclusions and signed-term boundary →
The scorecard applies the same versioned rule set as the full fit criteria — exact bands, thresholds and edge cases included.
See the controlled implementation path and first live period →
The agreed workflow can move chasing, replies, permitted write attempts and exceptions. Professional judgement and every launch approval stay human-owned.
A managed AI agent, not another dashboard. Mach Lilies installs and operates the agreed workflow around familiar tools; your practice retains every professional decision.
Every client-facing message is held for your team’s approval during the first 30 live days.
Operating commitment · control evidence pendingThis is an approved service boundary, not completed control-test evidence. Approval rules, write actions and any later autonomy are contract-specific and require separate written approval.
Reminder software
A human-controlled AI agent that progresses the agreed chase.
Evidence and limitations stay engagement-specific. Inspect the complete control framework →
No. Quiet Quarter handles the chasing, filing, tracking and reporting around client records. Judgement — tax treatment, accounting decisions, anything regulated — stays with the qualified people at your practice.
At launch, every client-facing message is held for approval by your team. That remains the rule throughout the live approval-mode pilot. Only after that pilot is reviewed may the practice consider a workflow-specific, tested, written change for later operation.
Not necessarily. The starting point is your existing inbox, tracker, and document locations. The chase-loop assessment confirms whether they can support a controlled workflow and what access, integration, or extra tooling would be required. No software change is assumed or promised before that review.
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.
The approved recurring tariff and setup treatment are stated below. Proposal-specific scope and third-party costs remain governed by signed terms.
The current new-order tariff is £799 per month, excluding VAT, and applies to the proposal-specific scope.
Owner-approved current tariff£799 per month is excluding VAT, applies to the signed scope, and is not a was-price comparison or a statement of total customer cost.
The current Quiet Quarter offer has a £0 separate setup fee because setup is included; proposal-specific third-party or tool costs can still be separate.
Owner-approved current tariffSetup is included in the current offer; proposal-specific third-party or tool costs are separate where stated in the signed scope.
The approved launch-period and conditional-exit terms are stated below. The signed agreement governs how they apply to the scoped workflow.
From go-live, the first 30 live days are free and measured in human-approval mode before the first invoice on live day 31.
Owner-approved current termThe clock starts at go-live, means live days rather than working days, and the period is measured in human-approval mode.
On live day 60, cumulative dependency-adjusted evidence is reviewed against the signed controllable output floor. A recorded supplier-responsible miss can open a process requiring notice within 5 business days and an unsuccessful 10-business-day cure review; the signed agreement controls.
Owner-approved conditional exit termExit is not unconditional: it requires a recorded miss within Mach Lilies' responsibility, five business days' notice and an unsuccessful ten-business-day cure review; the signed agreement controls.
The data-safety page is a proposed control framework, not a completed due-diligence pack or compliance determination. Actual suppliers, processing locations, retention, access, action-record coverage, incident contacts, and contractual terms are confirmed for the scoped workflow and put into signed documents before access is granted.
Phone, paper, and messaging-app chasing stays with your team unless a separate safe workflow is agreed. The chase-loop assessment checks whether enough of your repeatable chase loop runs through a controllable inbox to make Quiet Quarter worthwhile.
More questions — offer mechanics, acceptance reviews, edge cases and data handling — are answered on Pricing and Data safety.
Use your own workload to see what the AI agent could handle, what must stay human, and whether the economics justify a conversation.