Known · Shared knowledge, kept by coding agents and teams

Everything your company knows, out of the noise.

Decisions buried in threads, numbers scattered across tools, context that lives in one person's head. Known keeps what matters as a model of your company, with schemas it enforces, links between everything, and the history of every change. Your team, your agents and your software all work from the same signal.

Runs inClaude Code,Codex,Grok Build,Pi.Answers inSlack,Microsoft Teams,Telegram.

AAcmehandbook

decisions · billing

Annual billing refunds

Changed 3h ago by pi · agent, run by Brock · 4 revisions · 0 notes open · verified

Annual plans refund in full within 30 days of the term start. After 30 days there is no refund and no proration. Decided in #finance on 12 September by Dana and Brock.

Why

Annual plans bill up front, see decisions/annual-billing. Support had two tickets waiting on a window; finance chose 30 days to match the card network dispute period, so a refund and a chargeback never disagree.

What it changes

The refund flag in engineering/billing ships off until finance turns it on. Support answers from this page; the template is in runbooks/invoice-template. Proration stays open as a question for monthly plans only.

Owners

people/dana owns the policy. people/sam owns the flag.

# finance

12 members · Known added

  • Dana 9:41 AM

    Did we ever settle the refund window for annual plans? Support has two tickets waiting on it.

  • Brock 9:43 AM

    @Known what did we decide about annual refunds?

  • Known App 9:43 AM

    Annual plans refund in full within 30 days of the term start. Decided in this channel on 12 September by Dana and Brock; the flag in acme/billing is still off until finance turns it on. The two support tickets can be answered with the 30-day window.

    Verifieddecisions / annual-billing-refunds#finance · 12 Sepacme/billing #412

    2 repliesLast reply 4 minutes ago

Message #finance
Slack shown · the same answer, from the same record, arrives in Microsoft Teams and Telegram
01The BrowserRead, review, and keep the wiki. History, diffs, notes, and structured data on every page.02The CLIOne command line that carries your identity into any agent. Sign in once per organization.03The HarnessOne memory system for your whole fleet of agents and the team that runs them. In Claude Code, Codex, Grok Build, or Pi the agent reads the record first and writes back what it decided.04The Team ChatMention Known in Slack, Microsoft Teams, or Telegram and it answers in the thread. The channels you route feed the record.05The Conversational UIAsk Known in the browser and get the answer the company already has, with the evidence behind it.

Get started

Sign in, connect your agent, and the knowledge starts keeping itself.

Pricing