Investor pitch · Tax deadline intelligence

The tax deadline
intelligence layer

为美国独立 CPA 和 1-3 人税务事务所,把客户 CSV、多州 deadline、IRS / 州税公告和每周分诊整理成一个 source-linked workbench。

Independent CPAs Multi-state clients Official-source linked
投资人版开场要回到公司定位:DueDateHQ 是税务截止日期情报层,不是泛会计套件,也不是单纯日历提醒。中文补充用于精确定义目标用户和产品边界。
01

Problem / 问题

Small firms manage high-liability tax deadlines with fragmented, low-trust systems.

Client data is messy

TaxDome, Drake, Karbon, QuickBooks, Excel, and custom exports use different fields for the same client reality.

Tax authority changes are scattered

IRS and state notices live across newsroom pages, bulletins, RSS feeds, and slow government sites.

Deadline risk is personal

Missed dates create penalties, client trust damage, and professional risk for the CPA.

痛点不是“效率低”这么简单,而是高风险合规工作被迫依赖表格、日历和人工查官网。

这一页讲责任风险,不要只讲 productivity。投资人需要理解,这是高频、刚需、低现代化程度的 workflow。
02

Why now / 为什么现在

LLMs make jurisdiction-aware tax intelligence economically maintainable.

Data operations get cheaper

Crawler + LLM parsing can monitor official notices, extract structured impact, and send only uncertain items to review.

Small firms face more multi-state work

Remote commerce and multi-state clients push complex jurisdiction combinations into small CPA workflows.

Legacy tools leave a workflow gap

Existing options skew toward desktop deadline tools or broad practice-management suites, not source-linked tax deadline triage.

核心是成本结构变化。过去 50 州维护靠人工很重,现在可以用 AI 把数据运营压到软件可行的范围,但仍保留人工审核和官方来源。
03

Solution / 解决方案

A closed loop from client import to deadline action.

01

Import

CSV mapping, entity inference, multi-state jurisdiction split.

02

Generate

Customer + jurisdiction + tax-type deadlines.

03

Prioritize

Priority queue, timeline, exposure and status context.

04

Monitor

IRS / state source ingestion and structured parsing.

05

Match

Reviewed announcements route affected customers into action.

产品闭环围绕 CPA 的三件事:快速导入、每周分诊、公告响应。

不要把功能讲散。强调闭环:新客户进来、日常看 queue、公告变化后知道谁受影响。
04

Product / 产品体验

A workbench built around the Monday-morning CPA decision.

Activation

30-minute import target

Turn messy exports into clients, jurisdictions, estimated exposure, and upcoming deadline rows.

Retention

5-minute weekly triage target

Priority queue and timeline help users decide what needs action next without rebuilding a spreadsheet.

Differentiation

24-hour response target

Reviewed announcements can be matched to jurisdictions and routed into the user workflow.

The near-term proof points are speed to import, weekly repeat usage, and trusted response to tax-authority changes.

保留三个数字,但明确是验证目标。这样既有 pitch 叙事,也避免虚构 traction。
05

Current build / 当前完成版本

The MVP already covers the three core product loops.

AI client import

Field mapping, entity inference, jurisdiction splitting, unpaid-tax prefill, server-side importance judgment, and heuristic fallback.

Deadline workbench

Priority dashboard, timeline route, filters, drawer detail, virtualized lists, and source-linked decision context.

Announcement operations

RSS / HTML ingestion, Firecrawl tuning, LLM parsing, platform-admin review, run history, manual run, and daily cron path.

Next.js Prisma + PostgreSQL Auth.js Vercel Cron OpenAI-compatible AI layer
这页是 evidence。用项目已经完成的功能,不写真实客户、收入或尚未完成的完整 50 州生产覆盖。
06

Differentiation / 差异化

The hard part is not reminding. It is knowing which clients a tax notice affects.

Data unit

Customer + jurisdiction

Multi-state customers are modeled as state / county scoped jurisdiction records, not a single home-state calendar.

Trust loop

Official source attached

Deadlines and announcements keep authority context visible where the CPA makes a decision.

Operations

Review before fan-out

Crawler output is reviewed before matching and notifications, keeping AI inside a controlled workflow.

这里讲早期壁垒:模型、官方来源、审核流、用户反馈数据。不要声称无法被复制,而是强调 workflow depth 和数据质量会累积。
07

Market wedge / 初始切入

Start narrow: independent CPAs with multi-state clients and recurring deadline pressure.

Specific user

Independent CPAs and 1-3 person tax practices serving dozens of clients across states.

Specific workflow

Weekly deadline review, multi-state client triage, and government-announcement response.

Specific expansion

From deadline workbench to firm workflow integrations, team notifications, and calendar data interfaces.

A narrow wedge gives DueDateHQ a fast validation path before expanding into deeper firm workflows.

由于没有真实市场调研数据,这页不放 TAM/SAM 数字。更可信的投资人表达是 narrow wedge + clear expansion path。
08

Business model / 商业模型

Low-friction SaaS pricing, validated against time saved and risk avoided.

Packaging hypothesis

Subscription tiers should likely scale by firm size, client count, user seats, monitoring depth, and integration needs.

Value anchor

The buyer logic is avoided missed-deadline risk, fewer emergency checks, and less weekly spreadsheet maintenance.

Validation plan

Pilot interviews, shadow pricing, trial-to-paid conversion, and willingness-to-pay tests before locking public prices.

The model starts as a low-friction subscription and expands with monitoring depth, seats, client volume, and integrations.

按用户之前要求,定价根据项目实际情况考虑,不自己编不存在的上下文。因此不用固定价格表,改成可验证的商业模型假设。
09

Go to market / 获客路径

Earn trust where tax professionals already look for practical answers.

Pilot network

Recruit early CPA firms and industry advisors to validate import quality, queue fit, and announcement coverage priorities.

Utility-led content

Publish source-linked deadline and announcement change utilities that are useful before a user signs up.

Workflow-led PLG

A sample CSV and immediate deadline queue make activation visible without a heavy sales process.

GTM 不能讲大规模广告。CPA 市场更适合专业信任、实用内容和直接 pilot。这里与产品完成度一致。
10

Roadmap / 后续规划

From deadline workbench to tax workflow infrastructure.

Now

MVP proof

Import, priority workbench, timeline, reviewed announcements, and deployment hardening.

Next

Coverage quality

Expand and stabilize IRS / state sources, source health, and review operations.

Then

Tax platform workflow

Deeper support for TaxDome, Drake, Karbon, QuickBooks, UltraTax, ProConnect, and common export patterns.

Later

Team + API

Team notifications, calendar API, and deadline data interfaces after the wedge is validated.

平台集成是用户明确要求保留的规划。写成 roadmap,不写成已完成。
11

Risks / 风险与应对

The central risk is trust. The mitigation must be product-native.

Accuracy risk

Keep official sources attached and position DueDateHQ as decision support, not a replacement for authority calculations.

Coverage risk

Track source health, tune Firecrawl / ingestion behavior, and prioritize states based on real pilot feedback.

Adoption risk

Validate with real firm exports and keep the first workflow narrow enough to show value quickly.

投资人会问准确性和责任边界。主动讲清楚:官方来源、人工 review、source health、试点反馈都是产品机制。

The ask / 本阶段需要什么

We are looking for investor conversations, CPA pilot introductions, and tax workflow advisors.

下一阶段目标是验证三个问题:导入是否足够快、每周分诊是否形成习惯、公告匹配是否能变成可付费的信任优势。

Pilot
CPA and small-firm introductions
Data
Real exports and state coverage priorities
Model
Pricing and packaging validation
不写融资金额,因为项目上下文里没有明确融资目标。写投资人对话、pilot introductions 和 advisors,更符合当前阶段。