A product brief works when nothing on the page competes with the thinking. This template is set entirely in Inter with a confident indigo accent and Swiss-style breathing room on A4 — hairline rules, quiet tables, and a hierarchy that makes the problem statement impossible to skip.
Write the brief the way PMs already do — problem, users, scope, success metrics, all in Markdown. Inkrun renders every brief in the team to the same clean standard, so review meetings discuss the product, not the formatting, and last quarter's briefs remain instantly recognizable in the archive.
# Product Brief — Usage-Based Billing **Owner** L. Braun · **Status** In review · **Target** Q3 2026 ## Problem Mid-market customers churn at 2.3× the rate of enterprise, and exit interviews cite one cause: paying for seats they don't use. Our flat tiers punish exactly the accounts we want to grow into enterprise. ## Users - Ops leads at 50–500 person companies (buyer) - Finance approvers who audit per-seat spend quarterly ## Proposal Meter renders per workspace and bill monthly in arrears, with a spend cap the customer sets. Tiers remain for enterprise. ## Success metrics | Metric | Now | Target | | ------------------------ | ----- | ------ | | Mid-market logo churn | 4.6% | ≤3.0% | | Expansion revenue share | 18% | 28% | | Billing support tickets | 41/mo | ≤45/mo | ## Out of scope Prepaid credits, reseller billing, currency support beyond USD/EUR — all tracked for a later phase. ## Open questions 1. Cap behavior: hard stop or overage alert? 2. Does the free tier keep monthly reset or move to credits?
Paste your Markdown in the editor, pick Product Brief, and download the PDF — no code involved.
curl https://inkrun.dev/api/v1/render \
-H "Authorization: Bearer sk_..." \
-H "Accept: application/pdf" \
-d '{"template": "product-brief", "markdown": "# ..."}' \
--output product-brief.pdfAdd the Inkrun MCP connector once, then ask your agent:
“Turn this feature discussion into a product brief and render it with the product-brief template.”
Yes — export or generate the Markdown from your tool and POST it to the API with the product-brief template; many teams do this in a webhook.
It's one-page-minded but not enforced — the spacing scales cleanly to two or three pages when the brief needs it.
Duplicate the template with your hex; the Swiss layout and Inter typography stay put.
Montserrat headings over Open Sans in a fresh teal.
Monochrome US Letter one-pager — all Inter, near-black accent.
US Letter changelog with a vivid violet and boxed code.