Roadmap & feedback

Home · Docs

We publish the order of future work so you can see what is coming next and tell us what should move up. Feedback is not a formality here: it is how the roadmap changes, and roadmap changes go through an independent engineering review before they are locked in.

1 · Held legal finish

legal_notice {ref, version, text} + /terms

Finalize the legal notice shape, then publish binding terms only after the legal facts are cleared and the founder signs off.

2 · Roadmap input

Support / feedback / changelog

Add a durable support path so blockers, requests, and release notes can reshape what ships next.

3 · First-call onboarding

Quickstart + checklist

Improve the first-call path and clarify what to do when a request declines.

4 · Document workflow

Upload documents → JSON envelopes

Add a document-upload path that returns structured JSON envelopes people can inspect, store, and pass to downstream systems.

5 · Broader trust surfaces

Docs, marketplace, envelope depth

Expand the docs and marketplace copy, then deepen the supported envelope where the feedback says it matters.

How to influence the order

Tell us what blocked a first successful call.
Call out a gap in docs, examples, onboarding, or decline clarity.
Tell us whether document upload and JSON envelope output should move up next.
Say whether a roadmap item needs an independent engineering review before it advances.
Say which roadmap item should move up and why.
Include the API surface, workflow, or screen that made you hesitate.

Email roadmap feedback Contact support

What to send

A good note is short and specific: the task you were trying to complete, the point where the product copy or behavior fell short, and the one change that would make you trust or adopt the product faster.

Subject: Tax MCP roadmap feedback

I tried to:
I got stuck when:
The next thing I need is:
If you reorder one item, make it: