Accountants manually figure out the optimal order to work through complex returns (K1 first, then RSUs, then Schedule C, etc.) and struggle to stage work when dependencies block progress
An intelligent workflow tool that ingests client tax situations at intake, identifies all required forms and dependencies, auto-generates an optimal work sequence, flags blocking items early, and triggers the extension conversation at the right time
subscription - monthly SaaS fee, tiered by practitioner count
The pain is real and voiced by practitioners — complex returns with interdependent forms genuinely cause sequencing headaches, rework, and client management friction. However, experienced accountants have internalized these sequences as tacit knowledge. The pain is acute during tax season (Jan-Apr) but less so the rest of the year. It's a 'hair on fire' problem for 3-4 months, then a mild annoyance.
There are roughly 90K accounting firms in the US, but the target is solo practitioners and small firms handling complex individual returns — a subset of a subset. Estimating 15-30K firms that regularly handle multi-form complex returns and would pay for this. At $50-100/month that's a TAM of $9-36M/year. It's a viable niche business but not a venture-scale market without expansion into adjacent areas like firm-wide practice management.
Accountants are accustomed to paying for practice management software ($50-100/user/month is normal). However, this solves a narrow problem — form sequencing — which many practitioners handle mentally or with simple checklists. Willingness to pay a standalone fee for just sequencing intelligence is uncertain. Bundled into broader practice management, it's compelling. As a standalone tool, you need to prove the time savings justify an additional subscription on top of their existing stack.
The core dependency graph logic (which forms depend on which, optimal sequencing) is well-defined and finite — there are a known set of IRS forms with known dependencies. An MVP could use a rules engine rather than ML. Intake could be a structured questionnaire. The hard part is getting the dependency rules right (domain expertise needed) and integrating with existing tax prep software. A solo dev with tax domain knowledge could build an MVP in 6-8 weeks. Without tax expertise, add 3-4 weeks for research.
This is the strongest signal. Every existing competitor treats workflows as generic task templates or checklists. None of them understand tax form dependencies at the form level. None can ingest a client situation and auto-generate an optimized work sequence. The gap between 'generic workflow tool' and 'tax-form-aware intelligent sequencing' is significant and defensible with deep domain logic.
SaaS subscription works naturally — accountants need this every tax season and for extensions year-round. However, usage is heavily seasonal (peak Jan-Apr, extension season Aug-Oct). Risk of annual churn if firms only want to pay during busy season. Monthly subscription with annual discount is the right model, but expect seasonal usage patterns that could affect retention metrics.
- +Clear gap in existing tools — no competitor offers tax-form-aware intelligent sequencing
- +Well-defined domain with finite rules — IRS forms and their dependencies are knowable and stable
- +Accountants are proven SaaS buyers already paying $50-100/user/month for practice tools
- +Pain is voiced in practitioners' own words with specific examples of sequencing frustration
- +Low technical risk — rules engine, not ML, which means deterministic and trustworthy output
- !Narrow standalone value — form sequencing alone may not justify another subscription; likely needs to expand into broader intake/practice management to retain
- !Seasonal usage creates churn risk — firms may subscribe Jan-Apr and cancel, making unit economics challenging
- !Domain expertise barrier — getting the dependency rules right requires deep tax knowledge; wrong sequences destroy trust instantly
- !Integration dependency — value multiplies if connected to tax prep software (Lacerte, Drake, UltraTax) but those integrations are gated and slow to build
- !Tacit knowledge replacement resistance — senior practitioners pride themselves on knowing the right sequence and may not see the value; junior staff who need it most don't choose the tools
Practice management platform for tax and accounting firms with workflow automation, client management, document collection, and task tracking
Workflow and practice management for accounting firms with task management, client communication, and team collaboration
Workflow management built specifically for accounting firms, with recurring job templates and deadline tracking
All-in-one practice management for tax pros with CRM, client portal, document management, e-signatures, invoicing, and basic workflow
Workflow management solution for tax and accounting firms, part of the Thomson Reuters ecosystem, focused on tracking returns through completion
Web app with structured intake questionnaire (income sources, entity types, document checklist). Rules engine maps answers to required IRS forms, builds dependency graph, outputs a sequenced work plan as a printable/shareable checklist. Include red flags for blocking items (e.g., K1 not yet received) and a simple extension deadline calculator. No integrations in V1 — just the intelligence layer. Target 10 beta firms during the Oct extension season.
Free tier: 5 returns/month with basic sequencing → Pro at $49/practitioner/month: unlimited returns, blocking alerts, extension triggers, client communication templates → Team at $79/practitioner/month: multi-practitioner dashboards, workload balancing, firm-wide analytics → Eventually: API/integration tier connecting to Lacerte/Drake/UltraTax for auto-ingestion
3-5 months. Build MVP in 6-8 weeks, beta test with 5-10 firms during summer/early fall, convert to paid by October extension season. First real revenue test is January when tax season begins — that's the make-or-break moment for proving value under pressure.
- “He came in thinking this would be a two hour appointment. We are now on our third touchpoint”
- “start with the K1 and RSU basis work first since those have the longest tail”
- “getting close to the point where I need to have the extension conversation”
- “it's basically document triage and expectation setting”