Strategy
Part of Accounting services strategy for assessing MTD support
Where accounting strategies go wrong, starting with calling every business a customer
Avoid eight accounting services strategy mistakes in England involving market size, scope, competence, deadlines, pricing, software and growth.
What to take away
- Define one reachable customer segment and state which cases it excludes before selling.
- Test whether a new requirement creates paid demand with eligible customers, not just a count.
- Separate bookkeeping, payroll, accounts, tax, advice and management reporting in the engagement.
- Model deadline peaks, absence and corrective work, then pause intake before review capacity fails.
- Record each strategic assumption with evidence, owner, threshold and review date.
1. Calling every business a target customer
Legal form, activity, records, deadlines and competence alter delivery. Define one reachable segment and the cases it excludes. A broad ONS count is context, not demand for the proposed service.
For example, the segment might be single-director companies in England with turnover under £250,000, VAT registered, using cloud bookkeeping, and with no subsidiaries or stock. Exclusions: groups, charities, solicitors, clients with overdue Companies House filings, and anyone needing statutory audit.
2. Treating a new requirement as guaranteed revenue
The 2027 MTD cohort is a real event, but not everyone within the published threshold needs the same paid service. The published threshold for the 2027 cohort is qualifying income above £30,000. Check current HMRC MTD guidance, then test readiness needs and willingness to pay with eligible customers.
3. Selling vague "full-service" accounting
Customers and staff need to know which records, reviews, filings and decisions are included. Separate bookkeeping, payroll, accounts preparation, tax work, advice and management reporting in the engagement.
4. Assuming titles prove all competence
A qualification or membership does not authorise every service or demonstrate current specialist experience. Map each task to a competent performer and reviewer. Verify statutory-audit registration separately when that activity is claimed. For statutory audit, check the register held by ICAEW, ACCA or another recognised supervisory body.
5. Pricing routine work while giving away exceptions
Late records, clean-up, extra entities and technical questions consume experienced time. Define volume and quality assumptions, sample records before quoting and use a written scope-change process. A scope-change clause might say: 'Additional entities, clean-up of records older than 12 months, or work outside the agreed software are charged at the firm's published hourly rate after written approval.'
6. Automating an uncontrolled process
Software can move incorrect data faster. Preserve source, transformation, review, approval and submission evidence. HMRC's agent standard expects reasonable steps over third-party input within its scope.
7. Measuring leads instead of deliverable work
Count qualified enquiries, accepted engagements, correct completion, review findings, write-offs and retention by channel. A campaign that fills the pipeline with ineligible deadlines is not growth.
8. Expanding beyond review capacity
Processing capacity and competent review are different constraints. Model deadline peaks, absence, system failure and corrective work. Pause intake before the reviewer queue removes the margin needed to detect errors.
Test the strategy and update decisions under pressure
Run three cases: an ordinary customer, a record clean-up and a late high-risk enquiry. Follow each through acceptance, evidence gathering, review, approval and closure. Identify where staff improvise or responsibility becomes unclear. When a source or rule changes, update the affected decision without rewriting history.
Have a second person inspect completed files and compare promised scope with actual work. Ask clients where they repeated information or misunderstood their responsibility. Strategy becomes practical when it says when to narrow, refer, delay or refuse.
Use a pre-mortem before approval
Ask the team to imagine that the service failed after one reporting cycle. Each person should write the most plausible cause independently, then connect it to a prevention control and early indicator. Include a delivery practitioner, reviewer, commercial owner and someone responsible for information security.
Rank failure modes by consequence and detectability, not by how easy they are to fix. Missing reviewer capacity, ambiguous client responsibility and untested data migration deserve attention. Set one owner and deadline for each response, then retest the affected workflow with a realistic file. If leaders accept the risk, record their rationale and review date.
Before you act
- Define one reachable segment and its exclusions.
- Check HMRC MTD guidance and test willingness to pay.
- Map each task to a competent performer and reviewer.
- Sample records before quoting and use written scope changes.
- Run three pressure cases through acceptance to closure.
- Hold a pre-mortem and assign one owner per response.
Common questions
How can a firm test whether the 2027 MTD cohort will pay for a service?
The 2027 cohort covers qualifying income over £30,000, so firms should check HMRC MTD guidance and test readiness and willingness to pay with eligible customers, rather than assuming the threshold means paid demand.
What should a firm do when pricing routine work but giving away exceptions?
Late records, clean-up, extra entities and technical questions consume experienced time. Define volume and quality assumptions, sample records before quoting and use a written scope-change process. This prevents routine pricing from funding exception work.
