Collect survey-style feedback on GitHub Issues and RFCs.
Today, invoice state is mutated in place, which makes refunds and proration hard to audit. Moving to an append-only ledger gives us a replayable source of truth and unblocks usage-based pricing.
Most reviewers favor freezing the schema first; the dissent centers on refund replay edge-cases worth a follow-up spike.
Issues and PRs give you a comment thread, not structured feedback from the people who need to weigh in.
By comment sixty, the issue is archaeology: “+1”s, nits, and lost threads, with the actual decision buried somewhere in the middle. Inkling turns the same review into a handful of questions people answer.
The people who should shape the call — customers, partners, another team, an exec — usually can't even see the issue. Inkling shares the same doc as a scoped link, so you widen the circle without handing out repo access.
Write in Markdown, paste an RFC, or import a PDF — or let your agent pull a GitHub issue straight in over MCP. Inkling parses it into a clean doc, with headings, code blocks, and embeds intact.
Turn a proposal into a short list of decisions. Reviewers answer the questions that matter instead of leaving scattered nits.
Give customers the context to weigh in early. A scoped link gathers structured input you can take to the roadmap.
Make the call without the meeting. Async, attributed answers replace the messy single-issue comment pile.
Build a resource that teaches and checks understanding in the same place — and shows you where it landed.
Every one is a live document — open it to see the questions, the tallies, and the call they reached.
For trying Inkling on your next doc.
For teams running reviews on the regular.
For orgs that have outgrown limits.
Draft, embed your questions, and share a link in minutes. Free to start.