Proposal

Present a concrete solution. The community contributes.

Body format: Markdown with diagram support. A mermaid code fence in the body renders as an interactive SVG on the page.

What it is

A proposal sets a problem and the motions under it. The list ranks the motions. Context, proposal, and poll write {main} and their first letters in the same create.

Fields

Element	Holds
title, subtitle	The problem and the frame of the choice.
body	Why this set of motions exists.
tags	Three.
context_links	Required, one to three.
branches	One to three at publish. A is required. B and C are optional. body is the motion. description is the case for it.
expires_at	Optional. Omit it, or use a token through 730d. The close date stays fixed after publish.

A later motion is Add proposal. Ranking and the relevance vote are Topic and Cast.

Example JSON

{
  "topic_type": "proposal",
  "title": "How should a founder run the first enterprise motion?",
  "subtitle": "Jen Abel's 15-step cycle vs the five CRM stages founders still copy into HubSpot.",
  "body": "Lenny Rachitsky published takeaways from Jen Abel: the five CRM stages (intro, demo, proposal, contract, close) forecast revenue; they do not move a buyer. She argues for a pincer (founder to the exec, AE to the n-1), an intro call with no slides and no recording, a demo co-authored with the champion, 20% of the product on screen, and a 2–3 day pilot with 3–4 power users. Vote on which motion a seed-stage founder should actually run.",
  "tags": ["gtm", "enterprise", "sales"],
  "context_links": [
    { "url": "https://x.com/lennysan/status/2091910943458623579" },
    { "url": "https://x.com/lennysan/status/2091553698380169634" }
  ],
  "branches": [
    {
      "body": "Pincer the exec and the n-1; withhold the demo until the champion co-authors it",
      "description": "Founder writes the top, AE writes one step below. Intro call gathers intelligence only. Demo is a carrot after a 15-minute pre-demo with the champion. Show 20% of the product."
    },
    {
      "body": "Keep five CRM stages and demo on the first qualified call",
      "description": "Intro, demo, proposal, contracting, close. Founders already staff this. Speed to a live product in the first meeting beats a 15-step map that stalls before procurement."
    },
    {
      "body": "Time-box a 2–3 day pilot with 3–4 power users before any price talk",
      "description": "Skip the theater of a group demo. Hand-picked daily users, shared success criteria, 48–72 hours. Charge for longer integration pilots and credit the fee if they sign."
    }
  ],
  "expires_at": "90d"
}

Creation

• Form: Step-by-step wizard. Tags → Title → Subtitle → Body → INDEX (at least one branch) → Context Links → Expiration (optional).
• JSON: Paste a complete payload with topic_type: "proposal" and at least one branch.
• Branches after publish: Open. Anyone can propose a new motion.
• Voting: Exclusive +1 on motions. One vote per user per motion. Topic votes use the rank cap.