Accessible by construction, not by audit

Consulting-grade documents, generated and print-correct

Describe the document. tokaido. writes it, lays it out on a real grid, and returns a tagged PDF checked against veraPDF — every figure carrying the source it came from and the description a screen reader reads. For client work, compliance filings, policy papers and anything else that gets read closely.

1 → 3
formats from one master
1 → 4
audience variants
PDF/UA-1
tagged, and checkable by a stranger
The problem

The thinking is the work. The document should not be.

Whether you are one person writing a proposal, a team of five shipping a client report, or a practice with a procurement questionnaire to answer — the same four things go wrong.

The document takes longer than the thinking

The analysis was finished on Tuesday. It ships on Friday, because someone spent three days moving boxes, re-cutting charts and fixing page breaks.

Describe it once and it lays itself out

Type the brief, pick the kind of document. Pagination, grid, type scale and figure placement are decided by the template, not by you at midnight.

Every number lives in four places

A figure changes upstream and it has to be found in the chart, the summary line, the caption and the covering email. One of them gets missed.

Claims stay bound to their data

Each sentence that asserts something about a number keeps a link to it. Change the data and the ones that no longer hold are flagged rather than left to be discovered by the client.

The PDF is a picture of a document

No tags, no reading order, no alternative text. It fails procurement, it fails a screen reader, and it fails the accessibility clause already in the contract.

Tagged output, checked every render

Structure tree, reading order and alt text are written as the document is built, then checked against veraPDF when you export. Findings are reported with the file, not promised in a footer.

Good design is a person you have to hire

A solo operator or a team of four does not have a designer. The deliverable ends up in whatever template came with the software, and it looks it.

The design decisions are already made

Nine templates across four design systems, each derived from published consulting work. You supply the argument and your brand; the typography and grid are not your problem.

Who uses it

Built for consulting-grade work. Used by anyone who has to hand something over.

The bar is set by published consulting documents, because that is the hardest case. Everything below it gets the same grid, the same type scale and the same tagged output.

Solo operators

Consultants, coaches and fractional executives who are also the design department.

  • Proposals
  • Client reports
  • Case studies
  • One-pagers

Small teams

Four people, no designer, and a deliverable due on Thursday.

  • Investor updates
  • Pitch collateral
  • Research briefs
  • Board packs

Consultancies

Practices whose deliverable is the product, and whose name is on it.

  • Whitepapers
  • Diagnostics
  • Benchmark studies
  • Executive summaries

In-house teams

Marketing, strategy and finance groups producing documents that get audited.

  • Annual reports
  • Policy documents
  • Tender responses
  • Internal standards

Everything a consulting deliverable needs, and the parts nobody enjoys doing

Tagged PDF, not a picture of one

Structure tree, reading order, alt text on every exhibit, and a ToUnicode map that survives ligatures. Checked against veraPDF when you export, and the verdict travels with the file — pass, fail, or not checked. The last one is a real answer, not a silence.

  • H1
  • P
  • P
  • Figure
  • Caption

A real grid

Type sized as a fraction of the page, columns derived from the measure. One template serves A4, Letter and 16:9 without being redrawn.

Figures that cite themselves

Every exhibit carries its source line and a description generated from its own data.

Nine templates, four design systems

Whitepaper, report, executive summary, brief, article, case study, brochure, board pack. Pick the kind; see that kind's templates.

Four minutes to your first document. Nothing to install.

Start free — no credit card

Three steps, start to finish

  1. Describe it

    One paragraph of plain language. Pick a kind — whitepaper, board pack, brief — and the template that suits it.

  2. Watch it compose

    The preview paginates as you type: real page breaks, real figures, the same engine that writes the PDF.

  3. Ship it

    Export a tagged PDF, a DOCX, or a deck. Every claim in the prose stays bound to the data behind it.

The whole path, start to finish

It is a thorough process rather than a fast one — research, drafting, layout and a conformance check, in that order. You watch it happen instead of waiting on a spinner.

What you type

A whitepaper on how mid-sized firms cut month-end close time with automation.

That is the entire required input. Everything below is optional and has a default.

  1. You write

    One paragraph, in plain language. Nothing else is required to start.

  2. You choose, or you do not

    Kind, template, vertical, language, audience and depth all have sensible defaults. Attach your own sources — PDF, DOCX, PPTX, XLSX or a URL — and it will ground the figures in them.

  3. It researches, then writes

    Sources are found and read before a word is drafted, and what it found is kept, scored for relevance and reusable for the next document. The preview paginates as it goes: real page breaks, real figures, the engine that writes the PDF.

  4. You get the files

    A tagged PDF checked against veraPDF, a DOCX, a deck. Each figure carries its source and its alternative description, and each export carries a code anybody can verify.

Configurable to the point of being yours

Not a theme picker. The design system, the grid, the typographic scale and the language conventions are all addressable — and a design captured from one of your own PDFs becomes a system you can generate into.

9
templatesWhitepaper, report, executive summary, brief, article, brochure, case study, board pack.
4
design systemsGrid, palette and typographic scale as one unit — plus 9 more captured from real documents.
21
verticalsThe vocabulary, section shapes and exhibit conventions the sector actually uses.
6
languagesTranslated document furniture, over 18 typographic profiles for quotes, decimals and expansion.
  • Brand kits. Palette, fonts and logo stored once and applied to everything the workspace generates.
  • Designs captured from a PDF. Upload a document you already like; its grid, palette and type scale become a system you can write into.
  • Per-block styling. Any single block can override the system without forking the document.

Built for work that gets audited

Isolation enforced by the database
Row-level security, not application code remembering to filter. A query without a tenant returns nothing.
Your content is not training data
Briefs and sources are used to produce your document and for nothing else.
Erasure that leaves evidence
Deleting a tenant removes its documents, assets and users, and records what went and when.

Used for

  • Management consulting
  • Accounting & advisory
  • Financial services
  • Public sector & tenders
  • Healthcare
  • Technology
For teams and platforms

It answers to your systems, not just to a person typing

Single sign-on and roles

OIDC sign-in with scopes per role, and every tenant isolated at the database by row-level security rather than by a WHERE clause somebody has to remember.

Built for agents

An MCP server exposing the product as tools, governed by the same scopes as everything else. Your agent drafts, renders and exports without a human in the loop.

An OAuth provider, not an API key

Dynamic client registration, token exchange and a JWKS endpoint, so a partner's software authenticates as itself and can be revoked on its own.

Webhooks on document events

Signed deliveries into your systems when a document is generated, versioned or exported.

Embeds behind single-use tickets

Put a live document in your own product or portal without making it public and without handing over a login.

Versions, redlines and attestations

Every version kept and diffable, and every export carrying a receipt that verifies with no account and no access to your workspace.

The integration surface is documented in the Developer Center.

Start free. Pay when it is doing the work.

Export is never gated behind an active subscription — your documents leave with you.

Free

$0

For a first document and a real look at the output.

  • 3 documents a calendar month
  • All nine templates
  • Tagged PDF export
  • No watermark
Start free
Most chosen

Practice

$39/month

For the independent consultant shipping client work every week.

  • Unlimited documents
  • Your brand, fonts and palette
  • DOCX, PPTX and PDF ingestion
  • Version history and shareable links
  • veraPDF check on export, with the verdict reported
Start free — no credit card

Firm

$89/user/month

For teams with procurement, an SLA and an accessibility clause.

  • Everything in Practice
  • SSO and role-based access
  • Shared brand kits and templates
  • Signed DPA
  • Priority support
Start free — no credit card

Enterprise

Talk to us

For regulated work, private deployment, or volume nobody bills by the seat.

  • Everything in Firm
  • Private or on-premise deployment
  • Tenant isolation review
  • Custom retention and residency
  • Named support
Talk to us

Questions worth asking

Is the PDF actually accessible, or just exported?

Actually accessible. tokaido. writes the structure tree, reading order, and alternative text itself, then checks the file against veraPDF — the ISO reference implementation for PDF/UA-1 — when you export it. Where a document has findings, they are reported rather than hidden, and if the checker cannot be reached the export says so instead of implying a pass.

Can I use my own brand?

Yes. Colours, wordmark, cover treatment and chart palette are yours. The grid and type scale come from the template, which is what keeps a branded document from becoming a differently-branded mess.

What happens to my data?

It stays in your tenant, isolated at the database level by row-level security. Documents you do not save are never written to disk.

Can I start from something I already have?

Yes — paste a spreadsheet or transcript, or open a Word document, PowerPoint deck or PDF. Every block comes back with a confidence score, and anything uncertain is listed for review rather than quietly accepted.

Do I need to know design?

No. You pick the kind of document; the template decides the page format, the type scale and the grid together.

Write the brief. Keep the afternoon.

Write one paragraph. Get back a tagged PDF with every figure sourced.

Nothing to install. Export whenever you like.