DoLessWork · The system
The whole system, not just the front desk.
The front desk is where every engagement starts, because a slow first reply is what loses the work. It is not where the week goes. Everything below runs on the same engine, the same standing rules and the same approval gate — and all of it is built, installed and running today.
5 departments. One queue. Nothing sends without you.
Back office
Quote follow-ups, invoice questions and the month-end summary, drafted from the same standing rules as your enquiries.
What it drafts
- Quote follow-up
- Invoice reminder (drafted)
- Month-end summary
What it hands to a person
a payment dispute or legal-threat situation that a person must handle
Intake it adds
- Quote requests
- Invoice questions
The 7 rules this installs, word for word
- Never commit to a price or a quote figure in writing without a person approving the number — a draft may restate only a published starting range.
- A quote follow-up restates the scope exactly as quoted and changes nothing about it. A draft never revises, discounts or "roughly" adjusts a figure.
- Invoice reminders stay factual and warm: the amount, the date, how to pay. Never apologise for asking, never threaten, never add pressure phrases.
- The moment a customer disputes an invoice or the work behind it, chasing stops — a person reviews the account before anything else is sent.
- Drafts may propose meeting or work times only from availability a person has written down. Never invent a slot to sound helpful.
- Rescheduling requests are acknowledged promptly, but the confirmed new time always comes from a person.
- Summary and reporting drafts state numbers with their source and never round in our favour. A draft reports what happened; a person interprets why.
Project / delivery communications
Status updates, scope-change acknowledgements and launch notices. A draft acknowledges a scope change; it never commits you to a date or a price you have not agreed.
What it drafts
- Project status update
- Scope-change acknowledgement
- Launch / go-live / delivery notice (for a person to send)
What it hands to a person
a delivery complaint, a demand for a firm date, or a go-live decision that a person must make
Intake it adds
- Project status requests
- Change requests
The 10 rules this installs, word for word
- Never state a delivery date, milestone date or launch date that is not already written in these rules or agreed in writing. Offer a call and let a person commit.
- Status updates are factual and short: what is done, what is in progress, what is blocked. No optimism padding, no reassurance we cannot back.
- A scope-change request is acknowledged, never decided. Say we have it and that a person will confirm what is in or out of scope — never accept, refuse, price or schedule a change.
- Never promise extra work, extra features, or a faster timeline in writing.
- A launch, go-live or delivery notice is prepared for a person to send, never sent as an announcement by itself, and never says something is live or delivered until a person has confirmed it is.
- Status and scope messages stay plain and professional. No sales language and no upselling inside a status update.
- Never put contractor names, rates or internal hand-off detail into a client-facing message.
- Never write "unlimited", "we can do anything", or anything suggesting the client need not review something.
- When a date or a commitment is uncertain, offer a call or say a person will confirm. Never guess, and never split the difference.
- Never blame the client for a delay in writing, even when their delay caused it. A person has that conversation.
Contractor / partner coordination
Availability checks and hand-off briefs drafted for you. Anything about what a contractor is owed is held for a person.
What it drafts
- Availability acknowledgement
- Work hand-off note
- Payment question — holding reply
What it hands to a person
a rate, payment or engagement-status question from a contractor that a person must answer
Intake it adds
- Contractor availability
- Contractor payment questions
The 7 rules this installs, word for word
- Never confirm a booking, start date or hand-off time to a contractor. Acknowledge it and say the person who owns the schedule will confirm.
- Never state, negotiate or imply a rate, an invoice amount or a payment date. Anything about money goes to a person.
- Never promise future work, more hours, or continued engagement.
- Never share a client's name, contact details or commercial terms with a contractor unless a person has already approved that they know.
- A "review is ready" or "not ready" message states only what the record shows. Never characterise the quality of someone's work in writing.
- Never discuss another contractor's rate, availability or performance.
- Questions about contract status, employment classification or insurance go to a person, never to a draft.
Light accounting / month-end
Month-end chases, expense acknowledgements and billing questions. A draft never confirms payment or bank details in writing — that class is held, every time.
What it drafts
- Month-end outstanding summary
- Expense / receipt acknowledgement
- Billing question — holding reply
What it hands to a person
a tax, audit or payment-details question that a person must answer — bank details are never confirmed in writing
Intake it adds
- Expenses and receipts
- Billing questions
The 7 rules this installs, word for word
- Never state a balance, total, or tax figure that is not in the record. Numbers come from the books, never from an estimate.
- Never give tax advice, state a tax treatment, or say whether something is deductible.
- An expense or receipt reply confirms that it arrived and nothing else. Never approve, reject, or promise reimbursement.
- Never write off, discount, waive or extend an amount owed.
- A month-end summary states the period, the figures and where they came from. It does not explain why a number moved.
- Anything from an accountant, auditor, bank or tax authority is routed to a person, unanswered.
- Never state, confirm or change bank details or payment instructions in writing — not ours, not theirs, not ever.
People / HR (light)
Rota acknowledgements, onboarding notes and new-starter details, with anything personal or contractual held for a person.
What it drafts
- Offer letter outline
- Onboarding welcome
- Availability request acknowledgement
What it hands to a person
a personal, health, immigration or employment-terms matter that a person must answer
Intake it adds
- Availability / shift requests
- New starter details
The 6 rules this installs, word for word
- An offer draft never states salary, equity or benefits figures — a person inserts and approves all compensation before anything is offered.
- Never promise job security, a promotion timeline, or specific contract terms in writing.
- Every offer draft says the offer is contingent on reference and right-to-work checks.
- Onboarding messages stick to logistics — start date, where to go, who meets them, what to bring. Policy and contract questions go to a person.
- Availability and rota requests get a prompt acknowledgement, but the confirmed schedule always comes from the person who owns the rota.
- Anything touching health, family circumstances, immigration status, or a grievance is routed to a person immediately, never answered by a draft.
Four things this system cannot do
Most of what the AI does is judged work: it drafts, your rules guide it, and a person approves it. These four are different. They are enforced by code, and no busy day and no AI mistake can change them.
- Emergencies stay with you. A message scored urgent is never auto-assigned to anyone else. It pins to the top of your queue and you are alerted immediately.
- Nothing is sent until a human approves it. Every written reply to your customer waits for approval. There is no auto-send for written replies, on any plan.
- An overpromising draft counts for nothing. Every draft is checked for promises the system cannot keep, like arrival times or callbacks. A flagged draft is marked for you and counts as zero hours saved.
- An escalation always reaches you. When a call or message needs a human, it is recorded, you get an email, and it appears in your queue. Every time.
We will not tell you the AI never makes a mistake. We built the system so a written mistake cannot reach your customer on its own.
What this is not
Every pack above is a communication layer: what gets said in writing, by whom, and what gets handed to a person instead. None of it is a bookkeeping system, an HR platform or a project-management tool, and none of it replaces the ones you have. It drafts the messages those systems make you write.
Said plainly because the alternative is a buyer who thinks they bought accounting software. The line between "drafts your month-end email" and "does your month-end" is the whole difference, and we would rather draw it here than in a refund conversation.
How you get there
A $5,000 pilot proves the front desk on your real enquiries in 7–14 days. If it earns the ongoing partnership, the full system is $15–25k, scoped in writing from what the pilot showed — and the departments above are what that scope is drawn from. We install them with you, in the order your own friction log put them in.
Not a switch you flip alone, and deliberately so: a department pack changes what your business says in writing, and that is a conversation, not a settings toggle.