We shipped GitHub integration. Any GitHub issue can become an Inkling proposal: embedded questions, scoped sharing links, and structured responses that get posted back to the issue as a summary comment.
This is where Inkling is heading.
Why GitHub
Most product and engineering teams already write their thinking in GitHub issues. RFCs, design docs, proposals, decision logs. It's where the work happens.
The problem is what comes after. You write an issue, then need input from people who can't see it. Customers, partners, other teams, an exec without repo access.
So you copy the content into a Google Doc or a Notion page or an email. Now the conversation is split across 2 places, the feedback is unstructured, and you're manually pulling comments into something you can act on.
Inkling collapses that loop. Your issue stays in GitHub. Inkling pulls it in, lets you bolt on questions, and generates shareable links for specific audiences. Responses come back structured and attributed, with a summary posted right back to the issue thread.
Work where you work
Nothing moves. Your issue doesn't migrate to another platform. Your team doesn't learn a new tool. The proposal is the issue, rendered for external consumption with embedded questions.
Install the Inkling GitHub App and every issue in connected repos becomes a proposal source. Content stays synced. Close the issue, the proposal stops accepting responses.
Share without opening up GitHub
GitHub's permission model is binary: someone has repo access or they don't. There's no "let this customer read issue #482 and answer 3 questions about it."
Scoped links fix this. Each link is tied to a set of email addresses, can require verification, and can be revoked independently. Share a different link with your engineering team, your customers, and your partners. Each tracked separately, none requiring GitHub access.
The external participant sees a clean document with embedded questions. No account needed. They can't see your repo, your other issues, or anyone else's responses.
What comes next: workflows
Structured responses from known audiences are a foundation you can build on.
We're working toward automated workflows triggered by responses. 80% of reviewers approve a migration plan? Close the issue and create the implementation tickets. A customer flags a concern? Route it to the PM. An RFC reaches quorum? Generate the decision summary and post it to Slack.
None of this works when feedback lives in comment threads. It needs structured data: questions with answers, attributed to people, with clear completion criteria.
Getting started
If your team writes RFCs or proposals in GitHub issues, install the Inkling GitHub App and try it on your next review. Setup takes a few minutes.
The gap between "write the doc" and "make the call" is where decisions stall. We're trying to make it shorter.