Private pre-seed narrative · working draft

The missing layer in tax document delivery.

CivicTax Cloud is designed to help tax offices receive a complete, consented document package without owning the citizen’s portal or changing the document provider’s brand.

3protected roles in the pilot: source, citizen, office
6synthetic source-document categories demonstrated locally
0real taxpayer documents permitted in the pilot
The problem

Tax documents arrive everywhere. The authorized package arrives nowhere.

Preparation begins with collection: documents from payroll, work platforms, brokers, banks, health marketplaces, and local tax sources must be found, verified, organized, and shared safely.

For citizens

Lost emails, repeated uploads, unclear requests, and limited visibility into who needs what.

For tax offices

Manual follow-up, incomplete checklists, attachment risk, and delayed preparation.

For document sources

No neutral, narrow way to deliver an authorized record without revealing an open customer folder.

The solution

One consented path. Separate roles. Clear accountability.

01
Source deposits

Each employer, bank, broker, insurer, or platform uses its own restricted credentials.

02
Citizen receives

The private vault organizes arrivals and tells the citizen what reached the case.

03
Citizen approves

The office, purpose, year, and specific document categories are visible and revocable.

04
Office reviews

Only the permitted package becomes available for preparation and human review.

The starting wedge

Start where the coordination pain is immediate: the independent tax office.

The pilot is intentionally narrow: three participating tax offices, three document-source partners, synthetic records first, controlled feedback, and no assumed third-party software integration.

Tax office value

Case checklist, clear status, fewer missing-document chases, and auditable authorization.

Source value

One limited delivery workflow that keeps each source’s customer portal and relationship intact.

Citizen value

Arrival notifications, a readable vault, and the ability to approve, limit, or revoke sharing.

What the local MVP proves

A functional controlled flow — not a production claim.

Already demonstrated locally

Separate source credentials, synthetic document routing, private citizen visibility, explicit office consent, audit-oriented API design, and office access after approval.

Must be proven in a pilot

Participant onboarding, real operational usefulness, workflow adoption, authorized integrations, support needs, and the right pricing model.

Requires production readiness

Cloud landing zone, independent security review, contracts, privacy program, monitoring, incident response, and formal vendor approvals.

Pre-seed objective

Fund the proof, not a premature promise.

Capital should turn the local prototype into a narrow, secure, measured pilot — then use pilot evidence to earn official partnerships and larger distribution conversations.

Product hardening
Production-grade authentication, multi-tenant controls, storage, monitoring, and operability.
Pilot operations
Onboarding, controlled test environments, feedback collection, support, and measurement.
Security & legal readiness
Security program, policies, contracts, data-processing terms, and specialist review.
Partner development
Tax offices first; source and software integrations only when formally authorized.

Investment amount, valuation, instrument, ownership, revenue, and market-size claims belong in a separate founder-approved financial model and should be reviewed by counsel and finance professionals.