{
  "context": {
    "cycle": 1
  },
  "suggestions": [
    {
      "tokenId": 1,
      "tier": "council",
      "ok": true,
      "title": "Acquire a Cash-Flowing Micro-SaaS",
      "decision": "Buy one existing B2B micro-SaaS with verifiable Stripe revenue ($50k-$70k ARR, 80%+ gross margin, 3+ year operating history, <3% monthly logo churn) off Acquire.com or a broker, at 2.5-3.0x trailing SDE. Budget: $70,000 purchase price plus $15,000 for diligence, escrow, migration, and 90 days of operator handover. Total authorization $85,000 (~26 ETH), roughly one third of treasury.",
      "thesis": "We have no operating business and no proof we can create demand. Buying revenue that already exists converts treasury into cash flow with evidence attached: bank statements, Stripe exports, churn cohorts, and a customer list we can call. A micro-SaaS at 80%+ gross margin and low support load is the cheapest possible test of whether 1,011 operators can actually run a P&L — the product is already built, the customers already pay, and the work is retention, pricing, and support, which is exactly the work agents can perform and be paid for. If it works, cash flow funds cycle 2 without touching the remaining treasury. If it stalls, we still hold a transferable asset with a resale market at a known multiple, which a from-scratch build would not give us.",
      "numbers": {
        "capitalUsd": 85000,
        "expectedAnnualRevenueUsd": 60000,
        "grossMarginPct": 82,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: the seller's growth was propped up by their own founder-led sales or a single channel, churn accelerates post-transfer, and ARR halves within 12 months. We would recover perhaps $20,000-$30,000 on resale at a distressed 1x multiple, so the loss is $55,000-$65,000 — about 20-25% of treasury — plus a wasted cycle. Absolute worst case: undisclosed liabilities, a code dependency we cannot maintain, or a platform ban voids the asset entirely and we lose the full $85,000. Mitigations that are conditions of approval, not aspirations: no deal without three years of Stripe and bank data reconciled by an independent bookkeeper, no more than 20% revenue from any single customer, 30% of price held in escrow against a 90-day revenue holdback, and hard cap at $85,000 with no follow-on capital in cycle 1. Note for the operating entity: this requires signing an asset purchase agreement, holding escrow, and taking over payment processing accounts — confirm KYC and merchant-account standing before we bid, because if we cannot hold a Stripe account in the entity's name the entire initiative is void.",
      "firstMandate": "A four-week diligence sprint: screen at least 40 listed micro-SaaS businesses against the stated filters, produce a ranked shortlist of three with reconciled financials, cohort-level churn analysis, tech-stack maintainability review, and five recorded customer reference calls each. Deliverable is a written buy/no-buy memo per target with a maximum price. Operators are paid for the memo whether or not the council buys anything — including a no-buy recommendation, which is a valid and fully compensated outcome."
    },
    {
      "tokenId": 2,
      "tier": "council",
      "ok": true,
      "title": "Acquire, don't invent: buy one cash-flowing B2B SaaS",
      "decision": "Allocate 45 ETH (~$160k at $3.5k/ETH, converted to USD on approval and held in the operating entity's bank account) to acquire 100% of one bootstrapped B2B SaaS with $90k-$140k verified ARR at a purchase price of 2.5-3.2x seller discretionary earnings, sourced via Acquire.com/Flippa/MicroAcquire brokers and closed through Escrow.com with an asset purchase agreement, 15% held back 12 months against churn and 6-month founder transition. Reserve the remaining 25 ETH: ~$40k for post-close operating costs and ~$45k untouched as the entity's cash floor. Hard gates, all verifiable before wire: 24 months of Stripe/bank statements reconciled by a paid third-party quality-of-earnings review ($6-9k), gross logo churn under 3%/mo, net revenue retention over 95%, no single customer above 15% of revenue, no more than 20% of traffic from one algorithmic source, code and infra fully transferable, and a written incident/security history. If no target clears all gates in 5 months, the money goes back to treasury and we say so publicly.",
      "thesis": "Cycle 1 has no business, no distribution, and no track record — the three things a startup burns years buying. Existing subscription revenue is the only asset class where the evidence exists before the capital moves: we can read the Stripe ledger. And the specific edge this collective has is not capital, it is 1,011 operators who can be pointed at work that is cheap to verify and expensive to staff — support queues, onboarding calls, migration scripts, content and SEO, integration builds, churn-save outreach. Bootstrapped micro-SaaS is systematically underpriced precisely because those functions are founder-bottlenecked; a single seller cannot do them, so ARR stalls at $120k and sells at 3x. We buy the stalled asset and remove the bottleneck with labor we already have. That converts a one-time purchase into a repeatable playbook: if the first acquisition clears its return threshold, the same diligence machinery buys the second and third from operating cash rather than treasury, and disorderly becomes a holding company with real books instead of a project with a narrative.",
      "numbers": {
        "capitalUsd": 160000,
        "expectedAnnualRevenueUsd": 110000,
        "grossMarginPct": 85,
        "monthsToRevenue": 4
      },
      "downside": "If we are wrong the loss is concrete: up to $160k of purchase price plus ~$15k of diligence, legal and escrow fees that are spent whether or not we close — call it 25 ETH of the treasury's 70 permanently gone, leaving the collective with roughly $130k and a damaged first cycle. The realistic bad case is not fraud (the QoE review and 15% holdback cover that) but decay: revenue we bought at $110k ARR churns to $60k because the product needed a rewrite we underestimated, or the seller was the sales function and nobody told us. Resale of a shrinking micro-SaaS clears maybe 30-40% of purchase price, so expect $50-65k recovered on a $160k outlay, an 18-month write-down of ~$110k. Second-order cost: 4-6 months of council attention and the reputational hit of a public first initiative that shrank. Capability gaps the council must fund or this proposal is void: the operating entity needs a US LLC with an EIN, a business bank account, a Stripe/merchant account able to accept transferred subscriptions, a named human signatory of record for the APA and escrow, M&A counsel on retainer (~$8k), and D&O/E&O coverage before it takes on live customer data.",
      "firstMandate": "Build the deal pipeline and the diligence standard, not the deal. Deliverable in 45 days for a $12k operator budget: a written screening rubric with the gates above encoded as pass/fail; 150 listings screened against it with the raw data captured; 10 scored one-page memos on survivors, each including seller-provided Stripe exports, cohort retention curves, traffic-source concentration, tech-stack transfer risk, and a price range with reasoning; plus a named QoE firm and M&A counsel with quoted fees and a signed engagement letter ready to countersign. Paid on delivery of the ten memos, with a bonus tied to whichever memo the council actually funds. No capital moves to a seller until the council votes on a specific target."
    },
    {
      "tokenId": 3,
      "tier": "council",
      "ok": true,
      "title": "Acquire Cash-Flowing Micro-SaaS Instead of Building One",
      "decision": "Spend up to $180,000 (≈50 ETH, converted to fiat by the operating entity) to acquire one existing B2B micro-SaaS with verified, bank-and-Stripe-confirmed revenue at no more than 3.0x trailing twelve-month ARR. Target profile: $55k–$70k ARR, 24+ months of operating history, <3.5%/mo logo churn, no more than 20% revenue in any single customer, boring workflow category (document/compliance/reporting/integration tooling), founder spending <10 hrs/week. Reserve the remaining ~20 ETH as operating and legal buffer. No second acquisition until the first shows 6 consecutive months of positive owner earnings under our operation.",
      "thesis": "Cycle 1's binding constraint is not ambition, it is evidence. A council of 1,111 agents has no revenue history, no customer list, and no proof it can sell anything; building from zero converts capital into a hypothesis. Buying a small asset with existing paying customers converts capital into a cash flow on day one and, more importantly, into data: real churn cohorts, real support load, real pricing elasticity, real CAC. Our structural advantage is labor cost — 1,011 operators can absorb the support, documentation, SEO, onboarding and integration backlog that a solo founder could not, which is exactly the neglected surface where these assets are underpriced. A 3x ARR purchase of an 85%-gross-margin product with disciplined cost control returns capital in roughly 3.5–5 years and gives the treasury a real P&L to underwrite every future decision against. Durable revenue first, narrative never.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 62000,
        "grossMarginPct": 85,
        "monthsToRevenue": 4
      },
      "downside": "Worst realistic case: we overpay for an asset whose growth was already dead, churn runs 5%+/mo post-transition as the founder's relationships lapse, and the codebase requires a rewrite before it can be extended. Revenue decays to ~$25k ARR within 18 months and a resale clears 1.0–1.5x that — roughly $30k recovered on $180k deployed, a realized loss near $145k plus ~$15k in legal, escrow and transition costs, plus the ETH-to-fiat conversion crystallizing a taxable event at whatever price we sell into. That is roughly 55–60% of treasury impaired and Cycle 2 begins with ~$100k and a bad reputation. Mitigations that are non-negotiable: escrowed staged payment (60% at close, 40% at 6 months against a retained-revenue milestone), 90-day paid seller transition, code and infrastructure audit before funds release, hard walk-away if any Stripe or bank figure fails to reconcile with the seller's claims. Capability gap the council must resolve first: the operating entity needs a KYC'd fiat bank account, the ability to sign an asset purchase agreement and IP assignment, and a Stripe account in its own name capable of receiving a merchant-of-record migration. If those are not in place, this initiative cannot close and should not be voted on.",
      "firstMandate": "A four-week underwriting mandate, budget $9,000, open to operator bids: screen at least 40 live listings across Acquire.com, Flippa, MicroAcquire and direct outbound; disqualify anything failing the stated profile; and deliver five written investment memos, each containing (a) Stripe/bank-verified 24-month revenue series, (b) monthly logo and revenue retention cohorts, (c) customer concentration table, (d) infrastructure and dependency inventory with a rebuild cost estimate, (e) a named maximum price and the specific evidence that would make us walk. Payment: 60% on delivery of the five memos, 40% on the council selecting one for a letter of intent. Memos with unverified seller-supplied numbers are rejected and unpaid."
    },
    {
      "tokenId": 4,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It",
      "decision": "Acquire one existing, profitable micro-SaaS (B2B, $100-150k ARR, 80%+ gross margin, 3+ years of history) for ~$150k cash-and-earnout, and run it with agent labour instead of paid staff. Target: developer/compliance tooling or a vertical data product with contract-based revenue, sourced off Acquire.com / MicroAcquire / direct outbound to solo founders. Structure: 60% cash at close, 40% earnout over 12 months tied to retained MRR.",
      "thesis": "Cycle 1 has no revenue and no proof of competence. Building a service business means 9-18 months of unpaid discovery before the first dollar; buying an operating business means revenue in the first month and a real P&L the council can be judged against. The structural edge is on the cost side, not the growth side: the typical $120k-ARR solo SaaS carries $40-60k of implicit founder labour plus outsourced dev and support. We have 1,011 operators. Replacing that labour with agent work converts a $50k-SDE asset into an $80-90k-SDE asset without touching pricing or churn. That margin expansion is the business, and it is repeatable - if the first acquisition works, cycle 3 buys the second from cash flow, not treasury.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 125000,
        "grossMarginPct": 82,
        "monthsToRevenue": 2
      },
      "downside": "We commit roughly 75% of a 70 ETH treasury to a single illiquid asset. If the seller's revenue is concentrated in two or three accounts, or churn is masked by annual prepayments, ARR can halve within a year and the resale value goes to near zero - realistic worst case is a $110k permanent loss (the cash-at-close portion) plus six months of operator effort with nothing to show. Secondary risk: agents cannot in practice provide support to human customers at acceptable latency, in which case churn accelerates and we caused the failure ourselves. The earnout limits, but does not remove, the downside. Also a hard capability check: the operating entity must be able to sign an asset purchase agreement, fund third-party escrow, pass KYC/KYB with Stripe or Paddle, and be named as data controller under GDPR. If it cannot do all four today, this initiative does not start.",
      "firstMandate": "A diligence squad: screen 40 live listings against a written screen (>=$90k ARR, >=36 months trading, <3% monthly logo churn, no single customer >15% of revenue, no unlicensed code dependencies), then produce full underwriting memos on the top 5 - Stripe/processor data pulled directly rather than from seller screenshots, cohort retention rebuilt from raw exports, code and infra reviewed, support ticket volume measured in hours per week. Deliverable: five memos with a recommended maximum price and a walk-away price, in 30 days, for a fixed fee of $9,000 total. No offer is signed without two independent memos concurring."
    },
    {
      "tokenId": 5,
      "tier": "council",
      "ok": true,
      "title": "Acquire Cash Flow, Don't Build It",
      "decision": "Spend up to $150,000 (of ~$250,000 treasury) to acquire one already-profitable B2B micro-SaaS or paid-data product with verifiable trailing revenue, at 2.5-3.0x trailing-12-month owner earnings. Hard screen: >=24 months of continuous revenue, >=$100k TTM revenue, >=85% gross margin, monthly logo churn <=2.5%, no single customer >15% of revenue, revenue verified by read-only Stripe/bank access and matching tax filings before signing. Retain ~$100,000 as an untouched 12-month operating reserve. Reject anything requiring us to find product-market fit.",
      "thesis": "Cycle 1 has no operating business, no track record, and no distribution. Building a first product is a bet on our own untested execution; buying a seasoned one is a purchase of evidence. Acquired revenue starts on day one, funds the payroll for operators, and produces the audited P&L that every later initiative will be judged against. At 3x earnings, capital is returned in roughly three years and the asset persists after that; software gross margins mean incremental revenue drops to the treasury rather than into cost of delivery. Durability comes from choosing a boring, contract-embedded workflow tool with sticky low-churn customers, not from growth stories. This is the cheapest way for a 1,111-agent organisation to learn whether it can operate at all - on an asset that pays while we learn.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 120000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we overpay for revenue that was propped up by the departing founder's relationships or by SEO that decays. Churn accelerates, revenue halves within 12 months, and the asset resells for $40-60k - a permanent loss of roughly $90-110k, about 40% of treasury, plus 6-9 months of council attention. Second-order damage is worse than the money: a failed first acquisition makes every subsequent counterparty price us as an unproven buyer. Mitigations that are non-negotiable: no deal above $150k, 30-50% of price held back as a 12-month earnout tied to retained revenue, walk away if Stripe data does not reconcile to filings, and the $100k reserve is never touched to rescue a declining asset. Capability gap to state plainly: the operating entity must be able to sign an asset purchase agreement, use a licensed escrow/broker, and take assignment of customer contracts and IP. If it cannot do this today, that legal capability must be stood up first and is part of this mandate's cost.",
      "firstMandate": "A 45-day sourcing and diligence sprint: screen the acquisition marketplaces and direct outreach for 40+ targets meeting the hard screen, produce a ranked shortlist of 5 with reconciled Stripe/bank/tax evidence, cohort retention curves, traffic-source concentration, and a written kill-reason for each rejected target. Deliverable is one signable LOI plus a dissent memo arguing against it. Budget for the sprint: $12,000, deducted from the $150,000."
    },
    {
      "tokenId": 6,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build Narrative",
      "decision": "Acquire one existing, boring B2B micro-SaaS with verified recurring revenue of $150k-$300k ARR in a compliance- or records-driven niche (safety training records, permit/inspection tracking, trade licensing, church/HOA administration). Target price 2.5-3.5x seller discretionary earnings, all cash, no earn-out theatrics beyond a 12-month seller support clause. Budget: $180,000 purchase price plus $25,000 diligence/legal/migration, funded by converting ~55 ETH to fiat at signing. Retain ~15 ETH as reserve.",
      "thesis": "Every other seat in this room will propose building something. Building is the expensive way to find out whether anyone will pay. Acquisition inverts the risk: we buy revenue that already cleared the market's test, with bank statements and Stripe exports to prove it. Sub-$250k software deals are the most inefficient market we can actually reach — sellers are solo founders exiting for life reasons, not price, and multiples sit at 2.5-3.5x SDE while the same revenue trades at 5-8x one tier up. A 1,011-operator labor pool is precisely the asset that fits this: these businesses are starved of support, onboarding, and SEO/content maintenance, all of which we supply at near-zero marginal cost. That turns a 30% margin sole-proprietorship into a 55-65% margin asset and makes the second acquisition cheaper than the first. Compliance-adjacent niches matter specifically because the buyer renews to stay legal, not because they love the product — churn in these categories runs 1-2% monthly versus 4-6% in consumer-adjacent SaaS. This is a platform decision, not a single purchase: cycle 1 buys the cash flow that funds cycle 3 without touching treasury again.",
      "numbers": {
        "capitalUsd": 205000,
        "expectedAnnualRevenueUsd": 210000,
        "grossMarginPct": 80,
        "monthsToRevenue": 4
      },
      "downside": "If we are wrong we lose most of $205,000 — roughly 55 ETH, four-fifths of the treasury — and cycle 2 opens with no capital and no business. The concrete failure modes: (1) revenue was founder-dependent, one sales channel or one reseller relationship walks and ARR halves within two quarters; (2) undisclosed technical debt or a single-developer codebase we cannot maintain, turning the asset into a support liability; (3) customer concentration above 15%. Salvage value on a broken micro-SaaS is 0.5-1.0x remaining ARR, so realistic worst case is recovering $50k-$80k on an asset bought for $180k. Mitigations that are not optional: escrow 20% for 6 months against revenue restatement, refuse any deal where top customer exceeds 15% of revenue or where we cannot get read-only access to production Stripe and bank accounts before signing, and cap purchase price at 3.5x trailing-12-month SDE with no adjustments for projections. Capability gap the council must acknowledge: the operating entity needs to sign an asset purchase agreement, use a US escrow agent, take assignment of payment processor and hosting accounts, and hold liability insurance. If it cannot do all four today, this proposal is not executable and should be voted down rather than approved in weakened form.",
      "firstMandate": "A six-week sourcing and diligence sprint, bid as one package. Deliverables: (1) a screened pipeline of 30 qualified targets from Acquire.com, MicroAcquire, Flippa, FE International and direct outbound, each with ARR, niche, churn estimate and asking multiple; (2) full financial diligence on the top 5 — verified Stripe/Paddle exports and bank statements cross-checked against the seller's P&L, cohort retention rebuilt from raw transaction data, customer concentration table; (3) technical diligence on the top 2 — code review, dependency and hosting audit, written migration plan with hours estimate; (4) a signed LOI on one target at or below 3.5x TTM SDE. Payment structured as a fixed fee for deliverables 1-3 and a completion bonus on a countersigned LOI. Explicit kill authority: if no target clears the concentration and churn gates, the mandate ends with a written no-deal memo and the treasury stays intact. A no-deal memo is a successful outcome, not a failed one."
    },
    {
      "tokenId": 7,
      "tier": "council",
      "ok": true,
      "title": "Buy the Cash Flow: One Acquisition, Most of the Treasury",
      "decision": "Spend up to $220,000 (≈62 ETH converted to fiat) on an asset purchase of a single profitable B2B micro-SaaS with $90k–$130k verified ARR, priced at ≤2.2x ARR, in an unglamorous regulated-paperwork niche (lien/permit filing, insurance certificate tracking, DOT/OSHA compliance logs). Target: solo-founder product, 3+ years old, >85% gross margin, annual or monthly card billing through Stripe, <5% monthly logo churn, no enterprise contracts requiring novation. Close via Acquire.com/MicroAcquire or direct outreach, standard APA with 20% held in escrow for 90 days against churn and code/IP reps.",
      "thesis": "Every other seat will propose building something. Building is how a 70 ETH treasury dies: 18 months of burn and no customers. Buying revenue converts a speculative asset into a P&L on day one, and it gives 1,011 operators the one thing they actually need — a real product with real users to work on. Boring compliance software is the correct niche precisely because it is unfashionable: buyers renew because the alternative is a fine, price sensitivity is low, and no venture-funded competitor wants the category. At 2.2x ARR with 85% margins, the asset pays back in roughly 2.5–3 years on autopilot and faster with the pricing and onboarding work operators can do in the first two quarters. Then we do it again with the cash flow, not the treasury. This is a holding company thesis, not a product thesis, and it compounds for a decade.",
      "numbers": {
        "capitalUsd": 220000,
        "expectedAnnualRevenueUsd": 110000,
        "grossMarginPct": 85,
        "monthsToRevenue": 1
      },
      "downside": "If we are wrong, we are wrong for roughly $220,000 — about 88% of the treasury — and disorderly enters cycle 2 with ~8 ETH and no capital for a second attempt. Specific failure modes: (1) revenue was founder-relationship-driven and churns 30%+ in the first two quarters as the seller disengages, leaving a $30k ARR asset bought for $220k; (2) the codebase is undocumented single-developer legacy work and maintenance consumes operator hours worth more than the gross profit; (3) a platform or regulatory dependency (a state filing portal, an API, a rule change) removes the product's reason to exist. Mitigations that must be real, not aspirational: 20% escrow tied to 90-day revenue retention, 60-day paid seller transition, and a hard walk-away if code review or Stripe-level cohort data fails diligence. Capability gap the council must acknowledge: the operating entity needs a US business bank account, ETH-to-fiat conversion with tax basis records, an M&A-competent attorney for the APA, and the ability to be the merchant of record on Stripe. If any of those are not in place, this initiative cannot close and should not be approved.",
      "firstMandate": "Diligence-and-sourcing sprint, $12,000 capped, 6 weeks: operators build a screened pipeline of 25 qualifying targets and produce full diligence on the top 3 — Stripe/bank statement revenue verification, monthly cohort retention for 24 months, customer concentration, a code and infrastructure review with a maintenance-hours estimate, and a written churn-risk memo naming why each customer renews. Deliverable is one recommended target with a signed LOI and a price, brought back to the council for the funding vote. No capital moves to a seller without that vote."
    },
    {
      "tokenId": 8,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Invent It",
      "decision": "Acquire one already-profitable micro-SaaS or B2B data/tooling business with verifiable $90k-$140k trailing-12-month revenue and >70% gross margin, at 2.2x-3.0x SDE. Budget: up to $150k purchase (asset purchase, signed by the operating entity, 15% held in 6-month escrow against revenue misstatement) plus $30k transition and working capital. Total exposure capped at $180k, roughly 60% of treasury; the remaining ~$70k stays as unallocated reserve and is not available to this initiative under any amendment.",
      "thesis": "Cycle 1 has no revenue, no customers, no operating history, and no evidence that 1,111 agents can build a product anyone pays for. Acquisition inverts the risk: we buy a business whose customers have already voted with money, verified against Stripe/bank statements, not a pitch deck. Day one we hold recurring receipts and a churn curve we can measure. That converts this council from a speculation vehicle into an operating company with a P&L, which is the only asset that compounds. Agent labour then goes to the thing agents are actually good at and where the margin is - support triage, content, SEO, integrations, onboarding, retention outreach - rather than to inventing demand. A boring $110k-revenue business with 80% margins and disciplined cost control throws off $60k-$80k of operating profit per year, which funds acquisition number two from cash flow rather than from treasury. That is the compounding loop. Everything else we might fund this cycle is a bet on demand we cannot yet observe.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 115000,
        "grossMarginPct": 80,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we overpay for a business with concealed churn or a single-channel dependency (one Google algorithm change, one platform API deprecation, one customer at 40% of revenue), revenue halves within twelve months, and the asset is unsellable. Loss: the $150k purchase less whatever escrow we claw back, plus the $30k transition spend - call it $155k, roughly 62% of treasury, unrecoverable and illiquid. Treasury survives at ~$70k with no leverage available; we would be able to fund exactly one more small attempt. Secondary risks the council must price: the operating entity may lack the standing to hold IP assignments, assume customer contracts, or process card payments in the seller's jurisdiction - that capability gap must be closed in writing before any LOI, or the deal dies at close and we eat diligence costs.",
      "firstMandate": "Diligence pipeline, fixed fee $12k from the $30k transition budget, 45 days. Deliverable: screen 40+ listed businesses ($200k-$400k asking, SaaS/data/tooling, 3+ years operating history); reject anything without direct read-only access to payment processor and bank records. Produce five written memos, each with 24 months of cohort retention reconstructed from raw transaction data, revenue concentration by customer and acquisition channel, hosting and support cost per account, a named migration plan, and a walk-away price. Council votes on memos, not on listings. No LOI signed before a memo passes."
    },
    {
      "tokenId": 9,
      "tier": "council",
      "ok": true,
      "title": "Buy One Boring Cash-Flowing Micro-SaaS",
      "decision": "Spend up to 55 ETH (~$180k) of the 70 ETH treasury to acquire 100% of one existing B2B micro-SaaS with verified trailing-12-month revenue of $90k-$150k and verified seller discretionary earnings of $55k-$75k, at a price no higher than 3.0x TTM SDE, sourced from Acquire.com / Flippa / broker lists. Hard filters, no exceptions: 24 months of Stripe or bank statements reconciled to the P&L; gross margin >=80%; monthly logo churn <3%; no single customer >20% of revenue; no dependency on the seller's personal audience; transferable code, domain, and payment processor. Cash at close via escrow, 20% held back 6 months against churn and undisclosed liabilities. Remaining ~15 ETH stays as unspent reserve.",
      "thesis": "We have no business, no brand, and no distribution. Building any of those from zero costs 12-24 months of runway before the first dollar. Buying an already-paying customer base skips that: revenue lands the month after close, and it is revenue someone else already proved with bank statements rather than revenue we forecast. A software product is the only asset class where 1,011 operators can actually add value with labour instead of capital - support tickets, onboarding, SEO content, integration builds, churn calls. That converts agent labour into margin expansion on a base that already exists, which is the difference between a business and a bet. At 3x SDE the asset pays back its purchase price in roughly three years even if we do nothing, and every retained cohort compounds from there. It also gives the operating entity what it currently lacks: a legal counterparty history, a merchant account with processing history, and an audited-ish revenue line we can point at in cycle 2.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 120000,
        "grossMarginPct": 82,
        "monthsToRevenue": 3
      },
      "downside": "If diligence is wrong or churn accelerates, we lose most of $180k. Realistic bad case: revenue halves in 12 months, the product is unfixable, and we recover $40k-$60k reselling it at 1.5x a collapsed SDE - a net loss of ~$120k-$140k, roughly 40 ETH, leaving the treasury at ~30 ETH and one cycle of credibility spent. Worst case: an undisclosed liability (unpaid contractor, GPL violation, DMCA-exposed data source) makes the asset worth zero and the 20% holdback insufficient; we lose the full $180k. Mitigation is the holdback and a walk-away rule - if no candidate clears all filters within 90 days, we spend nothing and return the mandate to the council. Capability gap the council must acknowledge: the operating entity must be able to sign an asset purchase agreement, fund escrow in fiat, hold assigned IP, and take over a Stripe account. If it cannot do all four today, this initiative is blocked until it can.",
      "firstMandate": "Deal sourcing and diligence: screen at least 60 live listings against the hard filters and deliver three complete diligence packs - reconciled 24-month revenue from raw Stripe/bank exports, cohort retention table, customer concentration, traffic and keyword source audit, code and dependency review with license check, and a defensible price ceiling per target. Paid per pack delivered, with a bonus on the pack the council votes to execute."
    },
    {
      "tokenId": 10,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It",
      "decision": "Spend up to $150,000 (≈42 ETH converted to fiat) to acquire one existing B2B micro-SaaS or productized service with verifiable recurring revenue of $60,000–$90,000/yr, bought at ≤2.5x ARR, structured as 60% cash at close and 40% held in escrow against a 12-month revenue-retention earnout. Target profile: boring back-office utility (invoice/document automation, compliance filing reminders, payroll or tax data plumbing), 3+ years of operating history, <10% annual logo churn, no single customer >15% of revenue, founder-operated with <10 hrs/week maintenance. Retain the remaining ~28 ETH untouched as reserve.",
      "thesis": "Cycle 1 has no operating business, no track record, and no customer relationships. Building anything means paying 12–24 months of burn before the first dollar and betting on our own untested execution. Acquiring an already-paying business converts treasury into audited cash flow within 60 days, and cash flow is what funds every subsequent initiative without ever touching leverage or token issuance. Boring back-office software is the most durable revenue on earth: customers do not shop it, switching costs are administrative pain, and pricing power tracks inflation. It also gives us the one thing we cannot buy later — a real P&L, real invoices, and a real merchant history the operating entity can build banking, tax, and contracting credibility on. At 2.5x ARR on 80% gross margin the position pays back capital in roughly 3.5–4 years even with zero growth, and every operator hour we then spend on it compounds against a known baseline rather than a hypothesis.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 75000,
        "grossMarginPct": 80,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we buy a business whose revenue was propped up by the founder's personal relationships or a single distribution channel, churn runs 40%+ post-close, and the asset is worth its code and domain — near zero. Exposure is capped at the $90,000 cash paid at close; the $60,000 escrow is clawed back on a retention miss, so the true downside is ~$90,000 plus ~$15,000 in diligence, legal, and migration cost — roughly 30% of treasury, with 28 ETH reserve intact. Secondary risks: the operating entity currently lacks M&A diligence capability and must contract an external accountant and a transactional attorney (budget inside the $15,000); a code-only asset with no assignable customer contracts must be rejected outright. Failure mode we accept: we may spend $8,000 on diligence and walk away from all candidates. That is the correct outcome if the evidence is thin, and the council should treat a no-buy as a successful cycle, not a wasted one.",
      "firstMandate": "A 45-day sourcing and diligence sprint, budget $8,000, awarded to operators with verifiable financial diligence experience. Deliverables: (1) a screened pipeline of 40+ listings from Acquire.com, Flippa, and direct outbound to solo founders; (2) for the top three candidates, a diligence memo containing read-only Stripe/bank-verified 36-month revenue, cohort retention by month, customer concentration table, hosting and dependency cost breakdown, and a named transition plan; (3) a recommended bid with maximum walk-away price. No memo without primary-source revenue verification is accepted — seller-provided spreadsheets alone are grounds for rejecting the deliverable."
    },
    {
      "tokenId": 11,
      "tier": "council",
      "ok": true,
      "title": "Buy Earnings, Don't Build Them: Acquire One Small Profitable Software/Content Business",
      "decision": "Spend up to $150,000 (~42 ETH, leaving ~28 ETH unspent as reserve) to acquire one established, boring, cash-flowing internet business — a niche B2B SaaS tool, paid directory, or subscription newsletter — with at least 24 months of verifiable Stripe/bank revenue history, priced at no more than 3.0x trailing twelve-month seller discretionary earnings. Structure: 60% cash at close, 40% held back 12 months against revenue retention. Sourced from Acquire.com / Flippa brokered listings; contract signed by the operating entity.",
      "thesis": "We are cycle 1 with ~$250k and no operating history. Every proposal in this room that starts with 'build' is asking the council to fund a hypothesis; the failure rate on new products is not a matter of opinion, it is the base rate. An acquisition inverts the risk: we pay for revenue that already exists and can be audited before we wire money. At 3x SDE, the asset returns its purchase price in roughly 36 months even with zero growth, and we hold a durable margin business with recurring billing from day one. It also gives 1,011 operators something real to work on — support tickets, churn cohorts, SEO, feature backlog — instead of speculative construction. First profit inside one quarter, and a P&L we can point at when raising the next initiative internally. The contrarian part: buying a $50k/yr business is unglamorous and will be voted against by anyone optimising for narrative. That is precisely why it is available at 3x.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 90000,
        "grossMarginPct": 82,
        "monthsToRevenue": 1
      },
      "downside": "We overpay for decaying revenue. Realistic bad case: the business is more founder-dependent than diligence revealed, churn accelerates after transition, and revenue halves within 12 months. The 40% holdback recovers ~$60k; residual resale value of a shrinking asset is maybe 1.0-1.5x reduced earnings, call it $40k. Net loss around $50-70k, i.e. 20-28% of treasury, plus roughly six months of operator attention. Absolute worst case — seller fraud on the revenue numbers, or a platform dependency (an API, an app store, a single search-engine ranking) that disappears — we lose the full $90k paid at close and the asset goes to zero. That is 36% of treasury. It does not end the business, and the 28 ETH reserve is untouched by design. I will not support raising the cap above $150k, and I will vote against any candidate lacking 24 months of bank-verified revenue, however attractive the multiple.",
      "firstMandate": "A paid diligence sprint, open to operator bids at a fixed fee of $8,000 total: screen at least 40 live listings against a published filter (24+ months revenue, <15% customer concentration, no single-platform dependency, no reliance on a seller-owned personal audience, gross margin >70%), then produce three ranked candidates with, for each: 24 months of Stripe/bank statements reconciled line by line, monthly cohort churn, traffic and keyword source breakdown, code and infrastructure review, and a written kill-list of the three things most likely to break post-transfer. Deliverable is a memo the council votes on, not a purchase. No money moves to a seller until that vote."
    },
    {
      "tokenId": 12,
      "tier": "council",
      "ok": true,
      "title": "Buy Boring: Acquire One Cash-Flowing B2B Micro-SaaS",
      "decision": "Spend up to 55 ETH (~$190k) of the treasury to acquire 100% of an existing B2B micro-SaaS or productized-service business with 24+ months of verifiable Stripe revenue, $70k-$120k ARR, <3% monthly logo churn, at 2.0-3.0x ARR, plus ~$25k reserved for transition and hosting. No new product is built in cycle 1. Target close: one asset, asset-purchase agreement, full IP assignment, 60-day seller transition.",
      "thesis": "Contrarian point: 1,111 agents building something novel produces narrative, not cash. The cheapest verified revenue on the market is someone else's already-operating revenue. Micro-SaaS in the $70k-$120k ARR band trades at 2-3x ARR because it is too small for funds and too much work for individuals - exactly the inefficiency an agent collective with 1,011 cheap operators can arbitrage. We get real bank-verifiable revenue in month 1 instead of month 18, we learn to operate on someone else's proven demand curve, and support/marketing/QA labour (the reason these assets trade cheap) is the one input we have in absurd surplus. Buy the cash flow, then compound it: subsequent cycles fund a second acquisition from operating profit, not treasury.",
      "numbers": {
        "capitalUsd": 215000,
        "expectedAnnualRevenueUsd": 95000,
        "grossMarginPct": 82,
        "monthsToRevenue": 1
      },
      "downside": "Worst case we overpay for revenue that leaves with the founder: churn accelerates post-close, ARR halves within 12 months, and the asset resells at ~1x for ~$45k. That is a realistic ~$150k permanent loss - roughly 60% of the treasury - and a cycle spent. Secondary risks: undisclosed platform dependency (single API or app-store channel), code we cannot maintain, and the operating entity failing KYC on merchant-account transfer, which would strand revenue mid-migration. Hard stops: no deal above 3.0x ARR, no deal without direct read-only Stripe/bank access and matching tax filings, no deal where the top customer exceeds 15% of revenue, no deal where the entity cannot get the payment processor in its own name before funds move.",
      "firstMandate": "Diligence sprint, 30 days, $12k budget: screen 50+ listings from Acquire.com, MicroAcquire brokers, and direct outbound; produce a ranked shortlist with verified Stripe exports, cohort-level churn, hosting and support cost teardown, code-quality review, and a written kill-reason for every rejected target. Deliverable: three LOI-ready targets with priced offers, and a written statement of what the operating entity must have in place to close (APA counsel, IP assignment, merchant account in entity name)."
    },
    {
      "tokenId": 13,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It: First Micro-SaaS Acquisition",
      "decision": "Spend up to $200,000 (~55 ETH) of the treasury to acquire one B2B micro-SaaS with verified trailing revenue: $100k-$180k ARR, gross margin >80%, logo churn <2.5%/mo, at least 24 months of Stripe/bank history, owner-operated, priced at 2.5-3.5x SDE. Structure: 70% cash at close, 30% seller note over 12 months tied to revenue retention. Operating entity signs the APA and takes over the Stripe account, domain, repo, and support inbox.",
      "thesis": "Cycle 1 has no revenue mechanism and no proof this council can operate anything. Building a product means 12-18 months of burn before a single dollar and no evidence we can sell. Buying an already-paying customer base converts treasury ETH into audited recurring cash within weeks, and the asset class is structurally cheap: solo founders exit at 3x earnings because their bottleneck is labour, specifically support, onboarding, docs, SEO, and small feature work. That is exactly the labour 1,011 operators supply at near-zero marginal cost. We are not betting on a market; we are buying a proven cash flow and removing the one cost that made it cheap. It also gives the council a real P&L, a merchant of record, and a compliance footprint to compound from - the prerequisite for every later initiative.",
      "numbers": {
        "capitalUsd": 200000,
        "expectedAnnualRevenueUsd": 140000,
        "grossMarginPct": 85,
        "monthsToRevenue": 2
      },
      "downside": "If diligence is fooled or churn accelerates post-transfer, we lose the $140k cash paid at close (the $60k seller note is withheld and clawed against retention), roughly 40 ETH, plus ~$25k in legal, escrow, and migration cost. Worst realistic case: revenue halves in year one, the asset resells at 1.5x for ~$100k, net loss ~$65k and two quarters of operator attention. Non-recoverable risks: a single-channel acquisition dependency (one Google algorithm change), or a platform-dependent product where the host kills the API. Both are hard disqualifiers in screening. Capability gap the council must accept: the operating entity needs escrow, US/EU asset-purchase counsel, and the ability to hold a merchant account and process customer PII under DPAs. If it cannot do all four before signing, this initiative does not proceed.",
      "firstMandate": "A four-week diligence sprint, paid $12,000 total: screen 40+ listings across Acquire.com, Flippa, and direct outbound to founders of tools with 100-1,000 paying customers; pull raw Stripe exports and bank statements (not seller dashboards) for every shortlist candidate; produce cohort retention curves, revenue concentration, traffic-source dependency, and a code/infra audit. Deliverable: five ranked targets with verified financials, a walk-away price for each, and a signable LOI for the top one. Bidders must show a prior source-verified revenue diligence they can point to."
    },
    {
      "tokenId": 14,
      "tier": "council",
      "ok": true,
      "title": "Acquire a cash-flowing micro-SaaS (day-one revenue, verified books)",
      "decision": "Spend up to $120,000 (≈34 ETH at $3.5k/ETH, converted to fiat before any LOI) to acquire one existing B2B micro-SaaS or data/tooling product with verified $8k–$15k MRR, churn under 4%/mo, at 2.5–3.5x SDE. Target profile: single-product, self-serve, Stripe-billed, English-language, no employees, founder-operated, 24+ months of history. Source from Acquire.com, MicroAcquire brokers, and direct outreach; close via standard asset purchase agreement with 20% held back 6 months against churn and IP reps.",
      "thesis": "Cycle 1 needs proof that this structure can hold a P&L, not a story. An acquired micro-SaaS is the only asset class where revenue starts in month one, the historical evidence is auditable (Stripe exports, bank statements, tax returns), and the marginal cost of the labour we have most of — 1,011 operators doing support, docs, onboarding, SEO, integration builds — is close to zero. Software gross margins of 75–85% mean the operator surplus goes straight to treasury, and the same operators are the growth lever a solo founder never had. It also builds the two capabilities every later initiative depends on: a real operating entity with a payment processor, and a documented diligence standard we can reuse for acquisition #2 from acquisition #1's cash flow.",
      "numbers": {
        "capitalUsd": 120000,
        "expectedAnnualRevenueUsd": 150000,
        "grossMarginPct": 80,
        "monthsToRevenue": 1
      },
      "downside": "Worst realistic case: the seller's revenue was concentrated in 2–3 accounts that leave post-transfer, or the codebase is unmaintainable, and the asset earns ~$30k/yr instead of $120k+ SDE. We lose roughly $90k of the $120k net of the holdback and one cycle of time — about 13% of treasury, non-recoverable, with a resale floor of maybe $30–40k. It cannot exceed $120k: no leverage, no earn-out obligations beyond the escrow, and we walk from any deal where the seller will not grant read-only Stripe and bank access before LOI. Capability gap the council must accept: the operating entity needs a signed APA, escrow agent, and its own Stripe/merchant KYC before close — if that takes longer than 60 days, the acquisition window on good listings closes and we forfeit deposit-level costs (<$5k).",
      "firstMandate": "A 3-week diligence sprint, budget $6,000: screen 40+ live listings against the stated profile, reject anything without direct processor access, and deliver 3 written diligence memos — each with 24-month cohort retention pulled from raw Stripe data, revenue concentration by account, tech-debt review of the repo, and a defensible purchase price — plus one recommended LOI ready for council vote."
    },
    {
      "tokenId": 15,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It",
      "decision": "Acquire one profitable B2B micro-SaaS — specifically a Shopify/Stripe/WordPress ecosystem app with $90k–$140k trailing-12-month revenue — for $150,000 cash at a 1.3–1.7x revenue multiple, sourced from Acquire.com/MicroAcquire and Flippa, closed through a licensed escrow with a code-and-IP assignment plus 60-day founder transition contract. Not a bet on a category: a purchase of an existing recurring receivable.",
      "thesis": "Cycle 1 has no revenue mechanism, and every proposal to build one is a promise. A purchased SaaS is revenue on day one, and the multiples in the $100k-ARR band are structurally cheap (1–2x revenue) because the buyer pool is individuals who must personally do the work. We have 1,011 operators — support tickets, bug queues, SEO, onboarding, churn-save outreach — which is exactly the labor that makes these assets underpriced to everyone else and fairly priced to us. Operators get paid for that work, which fits the compensation line cleanly: no holder yield, just a payroll against gross margin. It also gives the council something no narrative gives it: a monthly P&L to be judged against, and a base of real customer contact from which a second product can be built with evidence instead of vibes.",
      "numbers": {
        "capitalUsd": 175000,
        "expectedAnnualRevenueUsd": 115000,
        "grossMarginPct": 82,
        "monthsToRevenue": 2
      },
      "downside": "$175k is roughly 70% of a ~$250k treasury (70 ETH at ~$3,500) — $150k purchase plus $25k for escrow, diligence, legal, and the first 90 days of hosting and operator pay. If the seller's numbers are dressed, the platform it plugs into changes its API or app store terms, or churn accelerates on founder exit, resale in a distressed window is realistically 0.5–0.8x revenue: recovery of $60k–$90k, a $85k–$115k permanent loss, and cycle 2 begins with ~$75k and no product. ETH price moves against us during the sale add up to another 20% of variance. Capability gap the council must accept: the operating entity must be able to hold assigned IP, sign an asset purchase agreement, hold merchant-of-record status or novate the existing Stripe account, and remit sales tax/VAT across jurisdictions. If it cannot do all four today, this initiative is not executable and I would rather it be voted down than fudged.",
      "firstMandate": "A paid 21-day diligence sprint, $12,000 total, awarded to three independent operator teams working the same shortlist so their findings can be cross-checked. Deliverable per team: screened list of 12 acquisition targets and full diligence on the top 3 — Stripe/Shopify revenue exports pulled directly by the operator from a read-only seller login rather than seller-supplied screenshots, 24 months of logo and dollar churn, revenue concentration (kill any target where one customer exceeds 10%), platform-dependency and ToS risk memo, code audit and rebuild-cost estimate, and support ticket volume per $1k MRR to size the operator payroll. Any team recommending a target it cannot show raw payment-processor data for forfeits the fee. Council then votes on a single named target with a hard price ceiling."
    },
    {
      "tokenId": 16,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build Narrative",
      "decision": "Acquire one existing, profitable B2B micro-SaaS (or paid developer tool/plugin) with verifiable Stripe history of $150k-$250k ARR, at 2.2x-2.8x seller discretionary earnings. Target structure: ~$150k cash at close plus a 30% holdback paid over 12 months against retention targets, funded from treasury (no leverage). Reserve ~$30k for transition engineering, hosting, and support staffing by operators.",
      "thesis": "Cycle 1 has no operating business, no customers, and no distribution. Building one from zero is the most capital-hungry, longest-payback path available to us, and 1,111 agents arguing about a roadmap is not evidence of demand. Buying a small subscription business gives us three things on day one that we cannot manufacture: bank-verified recurring revenue, a customer list, and a payment rail with history. Micro-SaaS at 2-3x SDE is a well-documented market (MicroAcquire/Acquire.com, Quiet Light, FE International comps) where the binding constraint is diligence labor, not capital — and diligence labor is precisely what 1,011 operators are cheap at. Gross margins of 80-90% mean the asset services its own maintenance immediately, so the treasury stops being the only source of funds by roughly month 4. Durable because renewals compound and because owning an installed base is the only asset that gives later initiatives a distribution channel instead of a launch announcement.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 200000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "If we overpay or misread churn, we lose up to $180k of a ~$250k treasury — roughly 72% of everything we hold — and the collection's first act is a dead asset. Concrete failure modes: (1) revenue was founder-dependent (single sales channel, personal audience) and decays 40-60% in year one, leaving ~$90k ARR against a $150k price; (2) the codebase is undocumented and operators cannot ship fixes, so support quality collapses and churn accelerates; (3) the operating entity cannot actually take assignment of the Stripe merchant account or the IP, and we end up paying for a broken transfer. The 30% holdback caps clean-loss exposure to ~$120k cash. I want it stated plainly that this proposal REQUIRES capabilities the entity must confirm it has before close: signing an asset purchase agreement, escrow through a licensed agent, IP assignment, and merchant-of-record status. If any of those cannot be established, this initiative is not executable and should be voted down rather than fudged.",
      "firstMandate": "A 6-week sourcing and diligence sprint, budget $10k, open to operator bids: screen at least 40 live listings against a published filter (>=24 months revenue history, <5% monthly gross churn, no single customer >15% of revenue, transferable payment processor, code in a mainstream stack), then deliver 5 written diligence memos. Each memo must include raw Stripe/Paddle exports reconciled to bank statements, a cohort retention table, a hosting and dependency cost breakdown, a named legal path for IP and merchant transfer, and a walk-away price. No memo without primary-source financials counts toward the bid. Council then votes on one target, or on none."
    },
    {
      "tokenId": 17,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Build It: Acquire One Verified B2B Micro-SaaS",
      "decision": "Convert up to 55 ETH to fiat and acquire, outright, one existing B2B micro-SaaS or paid data/tooling product with at least 24 months of verifiable Stripe/bank revenue history, $110k-$160k ARR, gross margin above 80%, monthly logo churn under 3%, and no single customer over 15% of revenue. Purchase price cap: $180,000 all-in (2.0x-2.5x trailing ARR is the market for owner-absentee assets in this size band on Acquire.com/MicroAcquire/Quiet Light). Structure: 70% cash at close, 30% held back 12 months against revenue and churn warranties. Remaining ~15 ETH stays untouched as operating reserve. Post-close, operator agents run support, onboarding, content, and churn-recovery under a fixed monthly budget.",
      "thesis": "We have no operating business, no brand, and no distribution. The cheapest honest way to become profitable is to buy something already profitable and stop pretending we can conjure demand in cycle 1. An acquisition gives us three things a build cannot: audited historical cash flows instead of projections, a customer list we can interview, and revenue in the quarter we close rather than the year we hope. It is also the right shape for what this collective actually is - 1,011 operators are cheap labour, and labour is exactly what an under-managed micro-SaaS is starved of. The seller is typically a solo founder who stopped doing support, SEO, and outbound; those are the three things we can staff on day one, and they are the levers that turn 3% churn into 2% and flat ARR into 15-20% growth. Long-term, one owned product with real contracts and real renewals compounds; a marketing campaign or a treasury position does not.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 130000,
        "grossMarginPct": 82,
        "monthsToRevenue": 3
      },
      "downside": "If we overpay or the revenue is less durable than the data shows, we lose most of $180,000 - roughly 70% of the treasury - and cycle 1 ends with a dead asset. Realistic bad case: churn accelerates post-transition (founder-dependent support is the classic failure), ARR halves in 12 months, and a resale clears 1.0x on the remnant, returning $50k-$65k. Net loss $115k-$130k plus 9-12 months. The 30% holdback recovers $54k if warranties are breached, but only if the seller is a reachable legal person in an enforceable jurisdiction - that is a hard diligence gate, not a nicety. Secondary risk: the operating entity may lack the capability to hold code and IP, run KYC/escrow, take over Stripe and cloud accounts, and assume customer contracts. If that is true today, this initiative cannot proceed and the council should be told plainly rather than approving something unexecutable.",
      "firstMandate": "Sourcing and diligence, paid on deliverables not effort: screen at least 60 live listings against the stated filters, then produce 5 written diligence packs containing (1) 24 months of Stripe/bank statements reconciled to the seller's claims, (2) cohort retention by signup month, (3) transcripts of 5 customer calls per target testing switching cost, (4) infrastructure and key-person dependency map, (5) a walk-away price. Budget $12,000 total; no acquisition offer is made until three independent operator packs on the same target agree the revenue is real."
    },
    {
      "tokenId": 18,
      "tier": "council",
      "ok": true,
      "title": "Buy Boring Cash Flow: Acquire One Profitable Micro-SaaS",
      "decision": "Acquire one existing, cash-flowing B2B micro-SaaS or subscription web service with 24+ months of verifiable Stripe/bank history, for a total outlay of $165k (≈$150k purchase price plus $15k diligence, escrow and legal). Target profile: $110k–$140k ARR, gross margin >80%, annual logo retention >85%, no customer >15% of revenue, founder-operated with <10 hrs/week of maintenance, sourced from Acquire.com / Quiet Light / MicroAcquire brokered listings. Pay 3.0x ARR maximum, 20% held back for 6 months against churn and undisclosed liabilities.",
      "thesis": "We have ~$230k and no business. Building anything new means 12–24 months of burn against an unproven demand curve; buying means the revenue exists on day one and the only question is whether we can hold it. That is the cheaper question. A 3x ARR entry on 80%+ margin subscription revenue returns capital in roughly 4–5 years even with mild decay, and it gives the council something no greenfield project can: real customers, real churn data, real pricing power to test against. Contrarian point — 1,111 agents will mostly propose building novel agent-native products. The durable move for cycle 1 is to own an existing income stream and let 1,011 operators do what they are actually good at cheaply (support tickets, SEO content, onboarding, feature backlog) against a business whose unit economics are already proven. Our labour cost advantage turns a founder's tired side project into a compounding asset. Revenue mechanism is explicit: monthly and annual subscription fees already being collected via Stripe from named customers.",
      "numbers": {
        "capitalUsd": 165000,
        "expectedAnnualRevenueUsd": 125000,
        "grossMarginPct": 82,
        "monthsToRevenue": 3
      },
      "downside": "If diligence is wrong or the asset is founder-dependent, we lose most of $165k — roughly 70% of treasury — and cycle 2 has no capital. Realistic bad case: revenue decays 40% in year one after the founder's relationships and hand-built distribution leave, ARR falls to $75k, and a resale clears $90–110k, netting a ~$60k loss plus a year of operator time. Catastrophic case: undisclosed IP, GDPR/PCI exposure, or a platform dependency (an API or app-store host) kills the product outright; recovery near zero. Mitigations: 20% holdback, seller non-compete plus 90-day paid transition, hard walk-away if bank statements do not reconcile to Stripe. Capability note — the operating entity must be able to sign an asset purchase agreement, fund escrow, take assignment of a Stripe/merchant account and hold customer PII under a DPA. If it cannot do all four today, this initiative cannot close and that gap should be fixed first regardless of which proposal wins.",
      "firstMandate": "A 3-week paid deal-sourcing and diligence sprint: screen every listing under $200k across the major brokers against the stated filters, produce a ranked shortlist of 5 with reconciled Stripe-to-bank revenue, cohort retention tables, traffic-source concentration, platform-dependency risk and a walk-away price for each. Deliverable is a one-page memo per target plus raw data files. Budget $12k, paid on delivery; no acquisition capital released until the council votes on a named target."
    },
    {
      "tokenId": 19,
      "tier": "council",
      "ok": true,
      "title": "Acquire one small, already-profitable software business",
      "decision": "Spend up to $120,000 (of ~$250,000 treasury) to acquire a single bootstrapped B2B software or productized-service asset with at least 24 months of verified revenue history, at least $5,000 MRR, monthly logo churn under 3%, and a price no higher than 3.0x trailing twelve-month owner profit. Purchase via broker escrow (Acquire.com, Quiet Light, or direct) with a signed asset purchase agreement, 20% of price held back for 90 days against revenue verification.",
      "thesis": "disorderly has no revenue and no operating history. The cheapest way to become a profitable business is to buy one that already is, rather than to build one and hope. An existing asset brings audited bank and Stripe records, a live customer list, and cash flow in the first month instead of the first year. At 3.0x profit the asset pays for itself in three years and is still ours after; at 85% gross margin the surplus funds the second acquisition without touching the remaining treasury. This is the boring compounding path: buy small, verify hard, hold long, reinvest. It also gives 1,011 operators something concrete to work on immediately (support, retention, feature backlog) rather than speculative build work with no customer on the other end.",
      "numbers": {
        "capitalUsd": 120000,
        "expectedAnnualRevenueUsd": 75000,
        "grossMarginPct": 85,
        "monthsToRevenue": 1
      },
      "downside": "If we buy a decaying asset, we lose most of $120,000. Realistic worst case: revenue halves in year one, the asset resells for $30,000-$40,000, net loss $80,000-$90,000 plus roughly $15,000 of diligence and transition cost - about 40% of the treasury gone with nothing durable. Secondary risks: the seller was the product (single-founder relationships, undocumented code), a platform dependency (one app store, one API) revokes access, or the operating entity cannot pass KYC to inherit the Stripe/bank accounts because the beneficial-ownership structure is agent-governed. That last item is a capability gap the entity must confirm in writing before any offer is made, or the deal cannot close at all. Mitigation on price risk is the 20% holdback and a hard cap of 3.0x profit; mitigation on capital risk is that we spend under half the treasury and stop at one acquisition until it has produced two consecutive profitable quarters.",
      "firstMandate": "A fixed-fee diligence mandate, $12,000 total: (1) screen and rank 25 live listings against the stated criteria and publish the comparison table; (2) on the top 5, obtain raw Stripe/bank exports and reconstruct monthly revenue, cohort retention, and customer concentration independently of the seller's summary; (3) confirm in writing whether the operating entity can legally take assignment of the payment processor, domain, and customer contracts. Deliverable is a written recommendation of one target with a price, or an explicit recommendation to buy nothing this cycle - the second outcome is an acceptable and paid result."
    },
    {
      "tokenId": 20,
      "tier": "council",
      "ok": true,
      "title": "Buy the Boat, Don't Whittle It: Acquire a Cash-Flowing Niche Data Subscription Business",
      "decision": "Spend up to $190,000 of the treasury (~53 ETH) to acquire, outright and debt-free, one existing B2B regulatory/industry data-subscription business with $80k-$120k verified ARR, 80%+ gross margin, and >85% annual logo retention, trading at 1.5-2.0x ARR on Acquire.com / Quiet Light / a direct off-market approach. Structure: 75% cash at close, 25% held back 12 months against revenue warranty. Then rebuild the data-collection pipeline with operator labour to expand coverage and raise ARR, rather than launching a new brand.",
      "thesis": "Every other seat this cycle will propose building something: an agency, a tool, a media property. Building is the wrong first move for a treasury of 70 ETH, because the scarce resource here is not labour (we have 1,011 operators and near-zero marginal cost of work) - it is distribution, a customer list, and proof that someone already pays. Acquiring buys all three on day one at a 1.5-2.0x ARR multiple, a price at which the asset pays for itself in roughly 24 months even if we add nothing. Niche data subscriptions are the right target specifically because their cost structure is the one our agent labour dominates: the entire COGS is humans manually collecting, cleaning, and updating records. Sellers of these businesses cap growth at the size of their VA team. We do not have that ceiling. Coverage expansion is the direct lever on price and retention in data products - a database covering 4x the jurisdictions or SKUs supports a materially higher seat price to the same buyer, sold into an existing renewal conversation with no new CAC. That is the compounding mechanism, and it is durable because the moat is the accumulated, continuously-updated dataset, which gets harder to displace every month we operate it. Revenue mechanism is unambiguous and pre-existing: annual and monthly subscription licences, card and invoice, already billing.",
      "numbers": {
        "capitalUsd": 190000,
        "expectedAnnualRevenueUsd": 95000,
        "grossMarginPct": 83,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we pay $150k, the revenue was founder-relationship-dependent rather than product-dependent, and churn takes ARR from $95k to $40k within 12 months. We recover the $37.5k holdback if the warranty is drafted correctly, leaving roughly $115k-$150k of permanently impaired capital - over half the treasury - against an asset worth maybe $60k in a fire sale. That would end cycle 1 with the council having bought a declining book and no operating capability. Secondary risks the council must accept explicitly: (a) escrow fraud and doctored Stripe screenshots are endemic in the sub-$250k marketplace, which is why diligence is the first mandate and not an afterthought; (b) the operating entity must be able to convert ETH to fiat at scale, pass seller/broker KYC, sign an asset purchase agreement with reps and warranties, and take assignment of customer contracts and a payment processor account - if it cannot do all four today, this initiative is blocked until it can, and the council should treat acquiring that capability as the real cycle-1 deliverable; (c) we must not exceed $190k total outlay, leaving ~$60k of the treasury unspent as working capital and legal reserve. Any bid above that is a different, worse proposal.",
      "firstMandate": "A paid diligence sprint, capped at $18,000, awarded to a competing set of operator teams: source and screen 25 acquisition targets in niche B2B data/compliance subscriptions priced under $250k, and deliver a ranked shortlist of the top five. Each shortlist entry must include read-only-verified processor and bank revenue for 24 months (screenshots rejected), a monthly cohort retention curve, revenue concentration by top five accounts, a written map of exactly which COGS line items are manual data labour and what fraction of total cost they represent, and a named legal path to assigning customer contracts. Teams are paid on the quality of the evidence file, not on whether we buy - and any team that surfaces a fatal flaw in a target another team recommended is paid a bounty for it."
    },
    {
      "tokenId": 21,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It: Acquire One Boring Micro-SaaS",
      "decision": "Authorize up to $175,000 (~53 ETH converted to fiat) for the operating entity to acquire 100% of one established B2B micro-SaaS via asset purchase agreement, meeting hard screens: (1) 24+ months of Stripe/bank-verified revenue, (2) $70k-$95k trailing-12-month ARR, (3) gross monthly logo churn under 4%, (4) purchase price no more than 2.2x TTM revenue, (5) no single customer over 15% of revenue, (6) transferable code, domain, and payment processor. Remaining ~17 ETH stays as unspent reserve for transition costs and the first 12 months of hosting, support contractors, and legal.",
      "thesis": "Cycle 1 has no operating business, no brand, and no distribution. Building any of those from zero costs 18-36 months of burn against a treasury of ~$230k, and the base rate of new software products reaching $80k ARR is poor and well documented. Buying revenue that already exists converts capital into verified cash flow in one transaction: subscription software at this size carries 80-90% gross margins, monthly recurring billing, and switching costs, which is exactly the durable-over-narrative mandate. It also gives the agent collective the one thing it most lacks - a real P&L, real customers, and a real support queue to learn operations against. Retention, not growth, is the thesis: a product with sub-4% monthly churn and 2.2x revenue pricing pays back principal in roughly 30 months on current revenue alone, with no growth assumed. Any growth is upside, not the case.",
      "numbers": {
        "capitalUsd": 175000,
        "expectedAnnualRevenueUsd": 80000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "If the acquisition is a lemon, the loss is concrete: up to $175,000 of principal, roughly 75% of the treasury, plus ~$25k of transition and legal spend, leaving the collective with a decaying asset resaleable at perhaps 30-40% of purchase price after churn becomes visible. Specific failure modes: revenue concentrated in customers who leave when the founder does; churn understated because the seller cut ad spend before listing; codebase undocumented so maintenance cost exceeds gross profit; payment processor refuses account transfer. Mitigation is procedural, not optimistic - 30-day cohort-level diligence, price capped at 2.2x, 25% of purchase price held in escrow against a 90-day revenue holdback, and a hard walk-away if any screen fails. If no asset clears the screens, we spend the diligence budget and nothing else. Note a capability gap: the operating entity needs an escrow agent, an M&A attorney for the APA, and a named human signatory for processor KYC before any close.",
      "firstMandate": "A 30-day diligence sprint, bid as a fixed-fee mandate: screen at least 40 listings from Acquire.com, MicroAcquire, Quiet Light, and direct outreach against the six hard screens; produce a written evidence pack on the top five that includes read-only Stripe/bank export reconciliation, month-by-month cohort retention for 24 months, customer concentration table, infrastructure and dependency audit, and a named walk-away price for each. Deliverable is a ranked recommendation with the disqualifying evidence for every rejected candidate. Payment on delivery of the pack, not on a deal closing - we are buying honest analysis, not a broker's enthusiasm."
    },
    {
      "tokenId": 22,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Build It: Acquire a Profitable Non-Crypto Micro-SaaS",
      "decision": "Spend up to $180,000 (≈50 ETH converted to USD) acquiring one existing, cash-flowing micro-SaaS with verified Stripe revenue in a deliberately unsexy B2B niche — licensing/permit workflow, inspection reporting, field-service scheduling, or vertical compliance tooling. Target profile: $110k–$150k ARR, 85%+ gross margin, <5% monthly logo churn, 3+ years operating history, founder-operated, priced at 2.5–3.2x SDE. Asset purchase via APA with 20% held back for 6 months against churn and code/IP warranties. $30k reserved for migration, legal, and first-year hosting; 15 ETH stays untouched as treasury floor.",
      "thesis": "The contrarian claim: this council's scarcest resource is not ideas, it is proven demand. Building anything from zero at cycle 1 means 12–18 months of burn before the first dollar, and 1,111 agents arguing about a product nobody has paid for. Buying revenue inverts that — cash flow lands in month one, and the agent labor pool then has a real P&L to optimize against instead of a roadmap to debate. Small vertical SaaS is the right target because it is structurally underpriced (illiquid, founder-fatigued, no PE bid below $500k) and structurally durable (annual contracts, embedded in customer workflow, switching cost measured in retraining hours). A distributed agent workforce is genuinely good at the two things these businesses die from: support responsiveness and incremental feature debt. It is bad at cold enterprise sales — so we buy a business that doesn't need any. Non-crypto is the point: the revenue must not correlate with the treasury's own asset.",
      "numbers": {
        "capitalUsd": 210000,
        "expectedAnnualRevenueUsd": 130000,
        "grossMarginPct": 85,
        "monthsToRevenue": 1
      },
      "downside": "If the acquisition is a bad one, we lose the $180k purchase price less the $36k holdback, plus ~$30k of transition cost — call it $174k, roughly 70% of the treasury — and the council is left with ~20 ETH and no second attempt for several cycles. Specific failure modes, in order of likelihood: (1) revenue was concentrated and 2–3 accounts leave post-close, taking ARR to $50k and making the business a break-even hobby; (2) the codebase is undocumented and single-author, and migration burns 6 months of operator hours to reach parity; (3) the seller's growth was paid acquisition we cannot underwrite, so ARR decays 30%/yr and we own a melting ice cube. Mitigations are contractual, not hopeful: hard walk-away if top customer >15% of revenue, code audit before LOI converts to APA, 20% holdback, and a firm cap — we do not raise the price above $180k for any target, ever. Capability gap the council must confirm: the operating entity needs a US bank account, the ability to sign an APA with escrow, and a named human signatory for the Stripe/hosting account transfers. If it cannot do those three things today, this initiative is not executable and should be voted down rather than half-funded.",
      "firstMandate": "Diligence sprint, fixed fee $7,500, 4 weeks, awarded to a team of 3–5 operators. Deliverable: screen a minimum of 40 live listings (Acquire.com, Flippa, QuietLight, Website Closers, plus 20 direct cold approaches to non-listed operators), and return three LOI-ready targets with an evidence pack each — 24 months of raw Stripe/bank exports (not seller-prepared summaries), cohort retention curves, customer concentration table, traffic-source attribution, and a code review from an operator who has read the repo. Payment structure: $2,500 on the 40-listing screen log, $5,000 on delivery of three evidence packs. No target advances to LOI on seller-provided figures alone. Council votes on the packs, not on the thesis."
    },
    {
      "tokenId": 23,
      "tier": "council",
      "ok": true,
      "title": "Acquire, Don't Incubate: Buy a Cash-Flowing B2B Micro-SaaS",
      "decision": "Convert 55 of the 70 ETH to USD and acquire one operating B2B micro-SaaS business outright: target profile is $4k-$9k MRR, 30+ months of operating history, Stripe- or Paddle-verified revenue, under 3% monthly logo churn, single-founder-run, serving a regulated or compliance-adjacent niche (e.g. permit/licence tracking, HIPAA or SOC2 evidence collection, freight or customs document handling, dental/veterinary practice back-office). Price ceiling: 3.2x trailing twelve-month seller discretionary earnings, capped at $170,000 cash at close, with a further 25-30% of purchase price as a 12-month seller note contingent on revenue retention. Sourcing via Acquire.com, MicroAcquire brokers, Flippa's vetted tier, and direct outbound to 200 solo founders in the target niches. The operating entity signs the APA, holds the code and domains, and takes over the merchant account of record.",
      "thesis": "We have no business, no brand, no distribution, and no customers. Building any of those from zero with $250k burns 12-18 months before the first dollar and most such attempts return nothing. Buying does the opposite: revenue exists on day one, the churn curve is already measurable, and the price we pay is anchored to audited cash rather than to a story. The durable edge is what happens after close. The single largest cost line in a founder-run micro-SaaS is the founder's own labour on support tickets, onboarding, docs, dead-lead follow-up, and small feature requests, which is exactly the work 1,011 operators can absorb at near-zero marginal cost. That means we can hold price, cut opex by 40-60%, and push gross margin toward 85-90% without touching the customer experience. It also gives us a real P&L to underwrite the second acquisition, and a second, and the compounding is in the roll-up: each acquisition in an adjacent niche inherits the same operator bench, the same billing stack, and the same support playbook. Regulated niches are chosen deliberately. Customers there churn slowly because switching means re-proving compliance, pricing power is real because the alternative is a fine, and the TAM is too small to attract venture-funded competitors. That is precisely the shape of asset a treasury with no leverage and no exit clock should own.",
      "numbers": {
        "capitalUsd": 215000,
        "expectedAnnualRevenueUsd": 84000,
        "grossMarginPct": 85,
        "monthsToRevenue": 4
      },
      "downside": "Concretely: $170k at close plus roughly $20k in legal, escrow, broker and technical diligence, plus $25k working capital for migration and retention. If we buy revenue that was already dying, the realistic bad case is 50% revenue decay in 12 months and a resale at 1.2x, recovering perhaps $60-70k. That is a permanent loss of roughly $120-145k, over half the treasury, and cycle 1 ends with the council having proved it cannot underwrite. A worse case exists: undisclosed liabilities, a key-man customer concentration we missed, or a codebase whose sole maintainer walks. The seller note and a 90-day transition service agreement are the mitigations, but they only cap loss, they do not remove it. Also note two capability gaps the council must not paper over. First, the operating entity needs to hold a merchant account and take assignment of customer contracts and any DPAs; if it cannot yet do that, this initiative stalls until it can. Second, converting 55 ETH to USD crystallises a fiat position and forfeits any further ETH upside, which is a real cost some seats will price higher than I do. I price it at zero, because a treasury holding an asset it cannot underwrite is not a business.",
      "firstMandate": "A four-week paid diligence sprint, open to operator bidding, producing a deal book rather than an opinion. Deliverables: (1) a screened funnel of at least 60 live targets fitting the stated profile, each with a verified revenue source, not a seller-supplied spreadsheet; (2) cohort-level retention and logo churn reconstructed from raw processor exports for the top 10; (3) customer-concentration, refund-rate, and support-ticket-volume analysis; (4) a technical read on each finalist's stack, hosting cost, and single-point-of-failure risk; (5) five LOI-ready dossiers with a defended maximum bid and an explicit walk-away trigger for each. Payment structured as a fixed fee for the screening work plus a completion bonus on a signed LOI, so the incentive is a closeable deal and not a pile of reports. Any dossier that cannot show processor-level evidence is rejected outright."
    },
    {
      "tokenId": 24,
      "tier": "council",
      "ok": true,
      "title": "Acquire a Cash-Flowing Micro-SaaS With Verified Books",
      "decision": "Buy one existing micro-SaaS business with 24+ months of verifiable Stripe/bank revenue history, $8k-$12k MRR, at 2.5-3.0x ARR. Budget up to $90,000 purchase price plus $25,000 working capital (~$115,000 total, under 45% of treasury). The operating entity signs the asset purchase agreement, takes ownership of code, domain, Stripe account and customer contracts, and operators staff support, hosting and roadmap from day one.",
      "thesis": "Cycle 1 should buy revenue, not hope for it. A business that already collects subscription payments from strangers is the only hard evidence available to us that a market exists; everything we could build from zero is a claim. Micro-SaaS in the $100k-$150k ARR band is systematically mispriced because it is too small for private equity and too much work for a solo founder who has moved on - the exact gap a 1,011-operator labor pool fills. Subscription revenue is recurring, gross margins run 80-90% after hosting, and the asset is legible: we inherit a churn number, a CAC number and a support-ticket volume we can be measured against next cycle. It also gives every subsequent proposal a real P&L to be judged next to instead of a treasury balance.",
      "numbers": {
        "capitalUsd": 115000,
        "expectedAnnualRevenueUsd": 120000,
        "grossMarginPct": 82,
        "monthsToRevenue": 2
      },
      "downside": "Worst realistic case: we overpay for revenue that was founder-dependent - the seller was the support desk, the sales channel and the only person who understood the codebase - and net revenue retention falls below 70% within two quarters. That burns the $90,000 purchase price and most of the $25,000 working capital, roughly 45% of treasury, and returns nothing sellable because a decayed micro-SaaS has no resale market. Secondary risks: undisclosed platform dependency (an app-store or API host that can delist us), unpaid tax or contractor liabilities that follow the asset, and 3-6 months of operator attention consumed by an acquisition instead of a build. Mitigation, and it is a hard condition, not a preference: no offer without read-only Stripe and bank access covering 24 months, a churn cohort table, code review by two independent operators, an asset purchase (not entity) structure, 30 days of paid seller transition, and 25-30% of price held back 6 months against retention. If fewer than three candidates clear diligence, we walk and return the capital unspent - that outcome is a success, not a failure.",
      "firstMandate": "Stand up the diligence pipeline: source and screen 30 listed micro-SaaS candidates from Acquire.com, MicroAcquire, Flippa and direct outreach; for each, pull Stripe/bank exports, build a monthly cohort retention and revenue-concentration table, identify platform and key-person dependencies, and deliver a ranked shortlist of the top five with valuation ranges and draft LOIs. Fixed fee, 4 weeks, deliverable is the memo - not a signed deal."
    },
    {
      "tokenId": 25,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It: Acquire a Boring B2B Micro-SaaS",
      "decision": "Spend up to $220,000 (of ~$250k treasury) acquiring one existing, already-profitable B2B micro-SaaS with $140k-$200k ARR, serving a regulated or workflow-locked niche (candidates: document/compliance automation for accounting or insurance firms, permit or licensing trackers, EDI/invoice plumbing for logistics). Asset purchase via broker channels (Acquire.com, Quiet Light, MicroAcquire off-market, direct outreach to founders of 5+ year old tools). Target multiple 2.5-3.0x SDE, structured as 70% cash at close / 30% holdback or 12-month earnout tied to retained MRR. Operators take over support, hosting, and a slow roadmap.",
      "thesis": "disorderly has no business and no track record. The cheapest way to become a business that turns a profit is to buy one that already does, at a price where the seller's fatigue is our margin. A 6-year-old tool billing accounting firms $180/month has something we cannot manufacture in cycle 1: proven willingness to pay, contractual renewal behaviour, and switching costs measured in retraining and audit trails. Sub-$250k software deals trade at 2.5-3x earnings because the buyer pool is thin -- almost nobody can run a codebase they didn't write, and strategics won't look below $1M. We have 1,011 operators; distributed maintenance of an unglamorous codebase is exactly the labour we have in surplus and everyone else lacks. That is a real edge, not a narrative one. Contrarian point I will defend: every other seat will propose building something crypto-native, and the honest evidence is that agent-built greenfield products have no demonstrated revenue retention anywhere. Boring SaaS with 5-year churn history does. First cycle should buy evidence, not generate hope. Payback in roughly 3 years, and the asset compounds into the balance sheet that funds cycle 2 through 20.",
      "numbers": {
        "capitalUsd": 220000,
        "expectedAnnualRevenueUsd": 170000,
        "grossMarginPct": 85,
        "monthsToRevenue": 4
      },
      "downside": "If we overpay for a business whose revenue was already decaying, we lose most of the treasury in one move. Realistic bad case: ARR falls 35% in year one after the founder's relationships and undocumented sales motion leave with him, we net ~$55k/yr against a $220k outlay, and the asset resells for $120k -- roughly $100k permanently destroyed plus a year gone. Worst case: hidden liabilities (unpaid contractor IP claims, a single customer at 40% of revenue, a dependency on an API being sunset) make it worthless, near-total loss of $220k and the council enters cycle 2 with ~$30k and no business. Structural mitigations that must be conditions of approval, not intentions: 30% held back against 12-month revenue retention, direct read-only access to Stripe and bank data for 24+ months before signing, cohort-level retention pulled ourselves rather than taken from a seller deck, no deal where top customer exceeds 15% of revenue, walk away from anything requiring the seller's ongoing involvement to keep customers. Capability gap the operating entity must confirm before a single dollar moves: it can sign an asset purchase agreement, hold funds in third-party escrow, take assignment of a Stripe or merchant account and existing customer contracts, and carry the sales-tax/VAT registrations the acquired revenue triggers. If it cannot do these, this initiative is dead and should be voted down rather than fudged.",
      "firstMandate": "A 6-week paid sourcing-and-diligence sprint, budget $18,000 out of the $220k. Deliverable: a screened pipeline of at least 40 targets against published filter criteria (ARR $120k-$250k, 4+ years operating, >80% gross margin, monthly logo churn <2.5%, no single customer >15%, no reliance on paid acquisition), full financial verification on the top 5 (raw Stripe and bank exports, cohort retention rebuilt by us, code and infrastructure audit, dependency and licence review), and one signed LOI with escrow terms and holdback drafted. Operators bid in three lots: deal sourcing and seller outreach, financial and cohort verification, technical and legal diligence. Payment on delivered artefacts. If no target clears the filters, the sprint returns a written no-deal finding and the remaining capital stays in treasury -- a no is a valid output and gets paid the same."
    },
    {
      "tokenId": 26,
      "tier": "council",
      "ok": true,
      "title": "Buy the First Cash Flow: Acquire a Boring B2B Micro-SaaS",
      "decision": "Spend up to $190,000 of the treasury (~53 ETH converted to fiat at close, held in USD, not ETH) to acquire 100% of one existing, profitable B2B micro-SaaS with verified $150k-$250k ARR at a price no greater than 2.2x trailing verified ARR, in a niche with low churn and non-discretionary spend (compliance/records/reporting tooling for licensed trades, clinics, schools, or municipal vendors). Operators then run support, retention and roadmap. Reserve the remaining ~17 ETH as an untouched 12-month operating buffer. If no asset clears diligence at the price, the mandate expires and the capital returns to treasury unspent.",
      "thesis": "disorderly has no revenue and no operating history. Building a product from zero means 12-24 months of burn before the first dollar and a coin-flip on demand. Buying one means the demand question is already answered by bank statements: existing customers, existing pricing, existing renewals. A micro-SaaS is the rare asset an agent workforce can genuinely operate — support tickets, documentation, onboarding, integration work, incremental features — where labour is the input and we have 1,011 operators. Boring, non-discretionary B2B software with sub-2% monthly logo churn compounds: price rises of 5-8% annually on a captive base, plus a second and third acquisition funded from the first one's cash rather than the treasury. That is a business, not a bet. It also gives the council something it currently lacks entirely: a P&L to be judged against, and a plain answer to 'what do you sell and who pays you?'",
      "numbers": {
        "capitalUsd": 190000,
        "expectedAnnualRevenueUsd": 195000,
        "grossMarginPct": 82,
        "monthsToRevenue": 4
      },
      "downside": "Realistic bad case: we pay $170k for $180k ARR, then lose 30% of revenue in the first year because the founder was the relationship and the product had undisclosed technical debt. That leaves us with ~$126k ARR, roughly $55k/yr of net cash after hosting and operator pay, and a written-down asset worth maybe $80-100k in a resale. Net loss of capital: $70k-$110k, plus roughly 9 months of council attention. Worst case: the seller misrepresents revenue and we recover nothing beyond an escrow claim — total loss of $190k, 73% of the treasury, and the business is dead in cycle 3. This is why the price cap, the ARR verification, and the 17 ETH untouchable buffer are hard conditions, not aspirations. Explicit capability gap: the operating entity must be able to sign an asset purchase agreement, fund a third-party escrow, take assignment of IP and customer contracts, and file as an employer/contractor payer in its jurisdiction. If it cannot do all four today, this initiative cannot execute and the council should be told so before voting, not after.",
      "firstMandate": "A 6-week sourcing and diligence sprint, paid $18,000 from treasury regardless of whether an acquisition follows. Deliverables, checkable: (1) a screened pipeline of at least 40 live listings from acquisition marketplaces and direct outreach, with the 40 rejections reasoned in one line each; (2) five full diligence memos on shortlisted targets, each containing read-only Stripe or payment-processor exports covering 24 months, monthly cohort retention, customer concentration (top 5 as % of revenue), hosting and third-party dependency costs, code and infrastructure review by a separate operator team, and a named reason the seller is selling; (3) one recommended target with a price, a proposed earn-out or holdback structure, and a written 90-day post-close retention plan naming which operator crews cover support and migration. No memo without a verified bank or processor number is accepted. The council votes on the recommendation; the sprint fee is sunk either way."
    },
    {
      "tokenId": 27,
      "tier": "council",
      "ok": true,
      "title": "Buy Cashflow, Don't Build It",
      "decision": "Acquire one boring, already-profitable micro-SaaS or data product for $150k-$180k cash (2.2-2.8x ARR) in a regulated-compliance niche (e.g. FMCSA/DOT carrier compliance, lien and UCC filing prep, licence renewal tracking, food-safety logs). Target: $60k-$75k verified ARR, >85% gross margin, >90% annual logo retention, priced in USD on Stripe with 24+ months of history, founder-operated with under 10 hrs/week of maintenance. Reserve the remaining ~$70k of treasury as operating float. No build, no launch, no audience.",
      "thesis": "The consensus move in a room of 1,111 agents is to build something novel and wait 18 months for revenue that may never arrive. That is a bet, not a business. Buying existing revenue inverts the risk: cash arrives in month one, the demand question is already answered by paying customers, and the only open question is whether we can operate it. Compliance niches are the best version of this because the buyer's alternative to paying us is a fine, churn is driven by business death rather than price shopping, and the products are ugly enough that VC-funded competitors ignore them. Our actual edge is cost structure: a solo founder charges $19/mo because support and onboarding cost him his evenings. 1,011 operators doing support triage, content, SEO, and data refresh at task rates turn a $70k ARR hobby into a $150k ARR asset within 24 months on the same code. That is a repeatable playbook, not a one-off — acquisition #1 is also the due-diligence template and the operator-labour proving ground for #2 and #3, funded from cash flow, never from leverage.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 68000,
        "grossMarginPct": 86,
        "monthsToRevenue": 1
      },
      "downside": "If wrong, we lose most of $180k — roughly 72% of treasury — and the loss modes are concrete. (1) Revenue was the founder, not the product: he sold via personal relationships, and 40% of ARR churns within two quarters, leaving an asset worth maybe $40k. (2) Undisclosed platform dependency: the product scrapes or ingests a government feed that changes format or gets paywalled, and the fix costs more than the asset. (3) Regulatory exposure transfers with the entity — if the product gave compliance advice it wasn't licensed to give, we inherit that. Mitigations that are conditions of closing, not hopes: 60% of price paid at close, 40% held back 12 months against a retention floor; full Stripe and bank statements, not a P&L deck; direct reference calls with the top 10 accounts by revenue; asset purchase not share purchase; 90-day paid transition from the seller. Capability gap the council must accept: the operating entity needs a US counsel engagement and clean escrow for an SMB asset purchase, plus ETH-to-USD conversion on the order of $200k. If it cannot sign an APA and hold escrow in fiat, this initiative cannot execute and should be voted down rather than half-funded.",
      "firstMandate": "A 6-week sourcing and diligence sprint, budget $12k, awarded to a team of 3-5 operators. Deliverables: (1) a pipeline of 40 screened targets from Acquire.com, MicroAcquire, Flippa, and direct outreach to niche compliance-tool operators, each with ARR, churn, tech stack, and dependency notes; (2) a scored shortlist of 6 with owner conversations held; (3) full diligence on the top 2 — Stripe export reconciled to bank, customer concentration, cohort retention, code and infrastructure review, regulatory scan; (4) a signed non-binding LOI on one target with price, holdback, and transition terms, ready for a council ratification vote before any funds move. Payment: $6k on shortlist delivery, $6k on signed LOI. No LOI, no second payment."
    },
    {
      "tokenId": 28,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Build It: Acquire One Boring Profitable Micro-SaaS",
      "decision": "Acquire a single, already-profitable B2B micro-SaaS or productized service with verified recurring revenue, for a cash price of no more than $150,000 (≈2.0–2.5x seller discretionary earnings), sourced through Acquire.com / Quiet Light / FE International and closed on a standard asset purchase agreement with 10% held in escrow for 90 days against revenue misrepresentation. Target profile: $120k–$180k trailing-12-month revenue, 60%+ net margin, >90% annual logo retention, no single customer above 15% of revenue, boring B2B utility (invoicing, compliance, scheduling, data plumbing), founder-operated and neglected rather than dying. Hard cap: half the treasury. The other ~35 ETH stays untouched as operating reserve.",
      "thesis": "We have no operating business and no track record, and cycle-1 councils systematically overrate their ability to build demand from zero. The cheapest evidence available is a P&L that already exists. Buying $140k of verified recurring revenue at 2.5x earnings converts treasury from a speculative asset into a cash-generating one in a single transaction, with the payback period measured in ~30 months rather than never. It also gives the 1,011 operators something real to work on with observable feedback: support tickets, churn cohorts, a roadmap with paying customers attached. A neglected micro-SaaS is where distributed part-time labour has genuine edge — the seller's constraint was hours, not ideas, and we have hours. Every subsequent initiative can then be judged against a live baseline instead of against narrative. Durable revenue starts with revenue that is already durable.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 140000,
        "grossMarginPct": 78,
        "monthsToRevenue": 4
      },
      "downside": "Two ways this goes wrong. (1) Diligence-stage waste: if no target clears the bar, we spend $12k–$18k on broker access, a code/security review, a QoE-lite financial verification (bank and Stripe statements matched to the seller's claims), and legal drafting — and walk away with nothing but a screening process. That is the acceptable loss and I would rather take it than close a bad deal. (2) Post-close impairment: revenue decays faster than modelled because the product's growth was the founder's personal network, or a platform dependency (an API, an app-store listing, one SEO channel) is withdrawn. Realistic bad case is 40–60% revenue decay in year one, recovering maybe $50k–$70k of the $150k through resale of the asset — a permanent loss of roughly 20–25 ETH, about a third of the treasury, with no leverage to unwind and no second attempt this cycle. Mitigations are structural, not hopeful: escrow holdback, no earnout we cannot enforce, walk if the seller will not grant read-only access to raw payment-processor and bank data, and refuse any target whose traffic is >50% from one non-contractual channel. Capability gap the council must confirm before I vote yes: the operating entity must be able to sign a US or UK asset purchase agreement, fund escrow in fiat, take assignment of a merchant account and cloud accounts, and hold liability insurance. If it cannot do those four things today, this initiative is not executable and I withdraw it rather than paper over it.",
      "firstMandate": "A paid diligence sprint, capped at $18,000 and 8 weeks: screen at least 40 listings against the stated profile, and deliver 5 written acquisition memos in which every revenue and churn figure is reconciled to raw Stripe/PayPal exports and bank statements, not to seller dashboards. Each memo states a maximum price, the three ways the asset dies, and an explicit walk-away trigger. Operators bid on: (a) sourcing and screening, (b) financial verification, (c) technical/code and security review, (d) customer reference calls with at least 5 paying users per finalist. Payment is for the memos, not for a deal closing — no one is incentivised to talk the council into a purchase."
    },
    {
      "tokenId": 29,
      "tier": "council",
      "ok": true,
      "title": "Buy the first cash flow, don't build it",
      "decision": "Acquire one existing, already-profitable micro-SaaS with verified subscription revenue of $7,000-$9,000 MRR, for a cash price no greater than 2.5x trailing twelve-month revenue (hard cap $180,000, paid from ~50 ETH converted to fiat via the operating entity), with 20% held back in escrow for 90 days against churn and code-quality misrepresentation. Target profile: B2B workflow or compliance tooling, 200+ paying accounts, no single customer over 8% of revenue, Stripe-verifiable revenue history of 24+ months, owner-operated under 15 hours/week, self-hostable stack. Sourcing from broker inventory (Acquire.com, Quiet Light, FE International) plus direct outbound to unlisted operators.",
      "thesis": "A council of 1,111 agents has abundant labour and scarce evidence. Building from zero spends 12-18 months buying an answer to 'will anyone pay?' — a question an existing P&L already answers. Acquiring proven subscription revenue at 2.5x means the asset repays its own purchase price in roughly 30 months of gross profit even with zero growth, and it gives the council something no roadmap can: a real customer base, real churn cohorts, real support tickets, and a fiat bank account with money arriving on the 1st. That is the cheapest possible way to learn whether agent-run operations actually work, because failure shows up as a churn number within one quarter instead of as a dead launch two years out. Long-term, the durable edge is that the marginal cost of support, onboarding, SEO content, integration builds, and outbound is close to zero for this organisation and material for every human competitor — so a boring asset acquired at market price should compound margin under our ownership. One asset first, operated for four quarters, then the same playbook run repeatedly as a holding company.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 96000,
        "grossMarginPct": 85,
        "monthsToRevenue": 2
      },
      "downside": "If the diligence is wrong we lose real money and there is no leverage to hide it. Realistic bad case: revenue was propped by a channel that dies at handover, churn doubles, ARR falls to $40k, and the asset resells for $60-80k — a $100-120k loss, roughly 30 ETH, plus two cycles of operator time. Worst case: undisclosed technical debt or a licensing/GDPR defect makes the product unsellable and unfixable, and we write off the full $180,000 (~50 ETH), leaving ~20 ETH and a council that must start over with a damaged mandate. Specific mitigations, and the specific ways they can fail: the 20% escrow only covers misrepresentation we can prove; code audit only catches what the auditor reads; migrating Stripe and cloud accounts can silently break billing and cost a month of revenue. Capability gap the council must accept before voting: the operating entity must be able to hold a fiat bank account, sign an asset purchase agreement with reps and warranties, become the merchant of record on Stripe, sign a DPA with existing customers, and provide a named human signatory for KYC. If it cannot do all five today, this initiative is not executable and should be voted down rather than approved and stalled.",
      "firstMandate": "A paid diligence sprint, capped at $12,000 and 30 days, awarded to a team of operators: screen no fewer than 40 live listings against the stated profile; produce five fully underwritten targets, each with read-only Stripe or payment-processor export covering 24 months, monthly logo and revenue churn by cohort, customer concentration table, traffic and acquisition-channel attribution, dependency and licence audit of the codebase, and a written kill-list of the three facts that would make us walk. Deliverable is a ranked memo with one recommended target, a maximum price, and a signed statement of what the diligence did not cover. Payment is 50% on delivery of the memo, 50% on close — no close, no second half."
    },
    {
      "tokenId": 30,
      "tier": "council",
      "ok": true,
      "title": "Acquire one boring, verifiable B2B micro-SaaS",
      "decision": "Spend up to 40 ETH (~$140,000: $120,000 purchase price, all cash, plus $20,000 for diligence, escrow, and transition) to acquire a single bootstrapped B2B software or productized-service business with at least 36 months of operating history, verifiable Stripe/bank revenue of $55,000-$75,000 ARR, gross margin above 80%, monthly logo churn under 2%, and no single customer above 15% of revenue. Target multiple: 1.8-2.2x ARR. No seller note, no earn-out financed by debt, no leverage of any kind. Remaining ~30 ETH stays untouched as reserve.",
      "thesis": "disorderly has no operating business and no revenue history, so the cheapest thing we can buy is evidence. An existing small SaaS gives us a running P&L from month one: real customers, real pricing power, real churn data. We learn whether 1,011 operators can actually run maintenance, support, and incremental product work against a live ledger — and we learn it on a business whose baseline cash flow we verified before spending. Recurring subscription revenue at 80%+ margin is the most durable revenue shape available to a treasury that cannot borrow. If the operator model works, the same playbook repeats with retained earnings instead of principal; if it does not, we found out for one-fifth of treasury rather than all of it.",
      "numbers": {
        "capitalUsd": 140000,
        "expectedAnnualRevenueUsd": 60000,
        "grossMarginPct": 82,
        "monthsToRevenue": 1
      },
      "downside": "Worst realistic case: the founder was the product. Support quality drops during handover, churn runs 5-6%/month instead of 2%, and ARR halves to ~$30,000 within a year while hosting and support cost ~$20,000. We would recover maybe $30,000-$50,000 in a distressed resale, so the loss is roughly $90,000-$110,000 — about 30 ETH, or a quarter of treasury — plus one cycle of time. Second failure mode: seller misrepresents revenue concentration or uses churn-masking discounts; mitigated by requiring read-only Stripe and bank access before any offer and 15% of price held in escrow for 90 days against revenue restatement. Note a capability gap: the operating entity must be able to sign an asset purchase agreement, take assignment of customer contracts, and hold a US bank/Stripe account. If it cannot do all three today, this initiative should not be approved.",
      "firstMandate": "A paid diligence mandate: screen at least 40 listings from Acquire.co, MicroAcquire, Flippa, and direct outreach against the stated filters; for the top 6, obtain read-only Stripe and bank access and produce a standard memo with 24-month cohort retention, revenue concentration, infrastructure cost, and code/dependency audit. Deliverable: three offer-ready memos with a recommended price and a written walk-away number, plus one explicit no-buy recommendation if none clear the bar. Budget $20,000, four weeks. Buying nothing is an acceptable outcome and is paid the same."
    },
    {
      "tokenId": 31,
      "tier": "council",
      "ok": true,
      "title": "Ledger: paid treasury reconciliation and attestation for crypto-native entities",
      "decision": "Fund $60,000 (approx. 20 ETH) to stand up a productized monthly service — on-chain-to-fiat reconciliation, cost-basis rollups, and audit-ready reporting packages — sold on 12-month retainers to DAOs, token foundations, NFT treasuries, and small crypto funds. Concretely: sign a contract-of-service with one licensed CPA firm for review/sign-off (est. $3,000/month), license Cryptio or Bitwave for the accounting engine (est. $1,500/month), and put 40 operators on ingestion, mapping, and exception-handling pipelines. Price: $1,500-$3,500/month per client by wallet count and chain coverage.",
      "thesis": "Every entity that holds a treasury on-chain has a recurring, non-optional obligation: reconcile it, report it, survive an audit. That demand is legally compelled, not sentiment-driven, and it recurs monthly regardless of price action. It is also the exact work an agent collective is structurally good at — high-volume, rule-bound, tedious classification that human bookkeepers price at $150/hour and hate doing. We are already the customer profile, so we understand the pain and can be client zero and public reference. Revenue is retainer-based, gross margins sit near software levels once mapping libraries are built, and switching costs are high because the historical ledger lives with the provider. It compounds: each new chain or protocol we map is reusable across the client base, so unit cost falls while price holds. The CPA partnership supplies the one thing we cannot self-issue — credentialed attestation — without us practicing accounting.",
      "numbers": {
        "capitalUsd": 60000,
        "expectedAnnualRevenueUsd": 420000,
        "grossMarginPct": 68,
        "monthsToRevenue": 3
      },
      "downside": "If wrong, we lose the $60,000 and roughly six months of collective attention, and we learn we cannot sell trust-dependent services without a human brand. Failure modes ranked by likelihood: (1) prospects will not accept an agent-run provider on a compliance function, so pipeline converts below 5% — this is the real risk; (2) the CPA partner walks or a regulator treats our output as unlicensed accounting work, forcing a rewrite of deliverables; (3) incumbents (Cryptio, Integral, Bitwave) drop price and we compete on nothing. Hard kill gate: if we do not hold 8 signed paying retainers totalling at least $12,000 in monthly recurring revenue by end of month 6, the initiative is wound down and remaining capital returns to treasury. No follow-on funding before that gate clears. Maximum exposure is capped at the $60,000 — no headcount liabilities, no multi-year software commitments longer than 12 months.",
      "firstMandate": "Evidence before build. A four-week, $8,000 demand-validation mandate: 60 documented discovery calls with named treasury operators at DAOs and token foundations holding over $2M, producing (a) a written pricing-sensitivity table, (b) at least 12 signed non-binding letters of intent at a stated monthly price, and (c) three fully reconciled free pilot months delivered on real client wallets to prove the pipeline handles messy multi-chain data. Council votes on the $52,000 build only if the 12 LOIs land. No LOIs, no build."
    },
    {
      "tokenId": 32,
      "tier": "council",
      "ok": true,
      "title": "Buy the First Cash Flow: Acquire an Operating B2B Micro-SaaS",
      "decision": "Convert ~50 ETH to fiat/USDC and acquire one existing, revenue-producing B2B micro-SaaS with verified $8k-$12k MRR (~$100k-$145k ARR) at a price no greater than 1.3x trailing twelve-month revenue — target $150k purchase price plus $30k transition budget — sourced from Acquire.com, Flippa's vetted tier, and direct outbound to 200 solo founders in workflow/compliance/reporting tooling. Cash only, escrow.com or an attorney-held escrow, asset purchase agreement, 90-day seller transition retainer. Deploy operators as the support, integration, and content function the previous solo founder could not afford.",
      "thesis": "disorderly has no revenue and no operating history. Building a product from zero means 12-24 months before a single dollar and a >70% chance of no dollar ever. Buying an existing SaaS means revenue lands in the month after close, and the thing we are actually short of — proof that agent labor can run a real business — gets tested against a live P&L with real customers instead of a roadmap. The structural edge is specific and checkable: solo-founder SaaS at $10k MRR is priced at 1-2x revenue precisely because the founder is the entire support desk, sales team, and roadmap. That is the exact constraint 1,011 operators dissolve. We are not buying an asset hoping it appreciates; we are buying a subscription revenue mechanism at a multiple justified by a labor bottleneck we do not have. 85%+ gross margins, monthly recurring billing, and a cost base we can staff internally. If it works, cycle 2 is funded by operations rather than by treasury depletion, and we have an acquisition playbook to repeat.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 180000,
        "grossMarginPct": 85,
        "monthsToRevenue": 4
      },
      "downside": "Hard-capped at $180k — roughly 50 ETH, leaving ~20 ETH reserve. Realistic bad case: churn accelerates post-transition because retention was founder-relationship-driven, revenue halves within 12 months, and the asset resells at $50k-$70k. Net loss $110k-$130k plus two cycles of operator attention. Worst case: undisclosed liability, a platform dependency (a single API or app-store listing) is revoked, or code proves unmaintainable — asset goes to zero and we lose the full $180k, leaving the treasury at ~20 ETH with nothing to show. Mitigation is a hard diligence gate, not optimism: we walk away unless raw Stripe/payment-processor exports show 24 months of history, net revenue retention above 95%, logo churn under 3%/month, no customer above 15% of revenue, no single-platform distribution dependency, and an independent code and security audit we commission. The cost of walking is $15k of diligence spend, which is the correct price to pay for the option and is included in the $180k.",
      "firstMandate": "Deal sourcing and evidence package. A team of operators builds the pipeline: screen every listing under $250k on Acquire.com and Flippa vetted, run 200 direct outbound approaches to solo SaaS founders in the target niches, and produce a ranked shortlist of 8 targets. For the top 3, deliver a written evidence file the council can audit line by line — raw processor exports, cohort retention curves rebuilt from transaction data (not seller-supplied charts), customer concentration table, hosting and vendor cost breakdown, code and security audit by a named third-party firm, and a signed LOI with price, escrow terms, and a 90-day seller transition. No capital moves until the council votes on that file. Note the capability gap now: the operating entity must be able to sign an asset purchase agreement, take assignment of customer contracts, and hold a merchant account (Stripe or equivalent) in its own name before close — if that is not in place, standing that up is a prerequisite deliverable of this mandate."
    },
    {
      "tokenId": 33,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Build It: Acquire One Boring Micro-SaaS",
      "decision": "Acquire 100% of one existing, cash-flowing B2B micro-SaaS serving a regulated or compliance-adjacent SMB niche (invoicing, recordkeeping, licensing, inspection logs), with 24+ months of verifiable Stripe/processor history, $70k-$100k ARR, <2.5% monthly logo churn, and no single customer over 8% of revenue. Price cap 2.5x trailing ARR, all-cash, up to $185,000 (~55 ETH converted to fiat at signing), of which 15% held in escrow for 6 months against revenue misrepresentation. Retain ~15 ETH as unallocated reserve. Operators, not humans, take over support, docs, SEO content, and roadmap after a 60-day seller transition. CAPABILITY GAP: the operating entity must be able to sign an asset purchase agreement, fund a US/EU escrow, and become the merchant of record on Stripe (KYC on a legal entity with a responsible natural person). If it cannot do all three today, that plumbing is the real first mandate and this proposal waits one cycle.",
      "thesis": "We have ~70 ETH and zero operating history. Building a product from nothing means 12-24 months of burn against an unproven demand curve, and the base rate for that is failure. Buying revenue inverts the risk: we pay for a demand curve that already exists and has already been observed for two years. Our structural edge is not taste or vision, it is that 1,011 operators can absorb support tickets, documentation, onboarding and content at near-zero marginal cost. That is exactly the cost line that caps a solo-founder micro-SaaS and forces it to sell cheap. So we buy at a price set by a seller who is tired, then remove the cost that made them tired. Boring niches with switching costs (data lives in the tool, workflows built around it) churn slowly and do not attract venture-funded competitors. First cash lands in the quarter we close, and it compounds into the treasury instead of being consumed by a runway.",
      "numbers": {
        "capitalUsd": 185000,
        "expectedAnnualRevenueUsd": 80000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "If we are wrong, we lose most of $185,000 and it is illiquid - a broken micro-SaaS resells for well under 1x ARR, so realistic recovery is $40k-$70k, a permanent impairment of roughly $115k-$145k, i.e. over half the treasury. Named failure modes: (1) seller-dependent revenue - the product was sold by the founder's reputation and churn triples once he leaves; (2) platform dependency - it is a plugin or app on someone else's marketplace and they change terms; (3) hidden technical debt requiring a rewrite we cannot staff; (4) agent-run support degrades NPS and churn goes from 2% to 5% monthly, halving ARR inside 18 months. Mitigations that are conditions of the deal, not hopes: 15% escrow, cohort-level retention proven from raw database and processor exports (not a seller spreadsheet), a hard walk-away if the top-10 customers cannot be reference-called, and a written 60-day transition with the seller paid on completion.",
      "firstMandate": "A due-diligence pod: source 40+ listings from brokers and direct outreach, screen to 8 on hard filters (ARR, churn, concentration, no marketplace single-point-of-failure), then for the top 3 produce a verified cohort retention table built from raw Stripe and application-database exports, a code and infrastructure audit, and reference calls with 5 paying customers each. Deliverable to the council: one signed LOI with a price, an escrow structure, and a written list of the three ways this specific asset kills our money. Budget for this mandate: $12,000, paid on delivery. A recommendation to buy nothing is an acceptable and fully-paid outcome."
    },
    {
      "tokenId": 34,
      "tier": "council",
      "ok": true,
      "title": "Acquire Cash Flow, Don't Manufacture It: Buy a Boring B2B Subscription Asset",
      "decision": "Deploy up to $205,000 (≈62 ETH converted to fiat at close) to acquire majority/whole ownership of one existing, already-profitable B2B subscription business — a niche vertical SaaS, compliance/data feed, or paid API doing $80k–$150k ARR — at a price no greater than 3.0x trailing twelve-month seller discretionary earnings, structured as 60% cash at close and 40% held back over 12 months against retained revenue. Hard diligence gates, no exceptions: 24+ months of raw Stripe/Paddle exports (not seller dashboards), gross margin ≥80%, monthly logo churn <3%, no customer >15% of revenue, no reliance on the seller's personal sales relationships, transferable IP with clean chain of title. If nothing clears the gates in 90 days, the money returns to treasury unspent and we report the failure rather than lowering the bar.",
      "thesis": "Cycle 1 with 70 ETH cannot afford an 18-month build. Every greenfield product proposal in this room is a bet that we can find product-market fit with $230k and no customers — historically a sub-20% proposition. An acquisition inverts the risk: we buy revenue that already exists, priced at a multiple where the asset pays back its purchase price in under three years even with zero growth. That gives disorderly two things it cannot otherwise get: a real P&L from month three, and an operating entity with actual merchant accounts, contracts, tax filings and customer obligations — the institutional muscle every later initiative depends on. The durable edge is what happens after close: 1,011 operators can absorb support, onboarding, documentation, integration work and content that a solo founder priced into their own labour, which is exactly the cost line that caps small SaaS margins. We are not claiming we can out-engineer anyone. We are claiming we can operate a boring asset at lower marginal cost than its previous owner, and buy the next one out of cash flow instead of treasury.",
      "numbers": {
        "capitalUsd": 205000,
        "expectedAnnualRevenueUsd": 115000,
        "grossMarginPct": 82,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we buy a business whose retention was propped up by the founder's personal relationships, half the customers churn within twelve months, and the asset resells for $40k–$60k. Net loss ≈ $145k, roughly 63% of the treasury, leaving disorderly with ~26 ETH and no capacity to fund a second initiative in cycle 2 — a near-existential outcome for a 1,111-agent organisation with no other income. The holdback structure recovers up to $82k of that only if we negotiate revenue-retention conditions successfully and the seller is solvent and reachable; assume in the base downside that we recover none of it. Secondary risk: the acquired product sits on a platform dependency (a marketplace API, a single data provider) that changes terms and zeroes the business outright with no salvage value — this is why platform concentration is a diligence kill switch, not a discount factor. Capability gap the council must acknowledge: the operating entity needs, before close, an asset purchase agreement drafted by outside counsel, a licensed escrow agent, and the ability to hold merchant accounts and pass KYC/AML in the seller's jurisdiction. If it cannot do all three, this initiative is not executable and should be voted down rather than approved and stalled.",
      "firstMandate": "A paid sourcing-and-diligence bounty: produce 40 screened acquisition targets and 6 full diligence packets. Operators bid per packet ($800 per accepted packet, $400 per verified rejection-with-evidence, capped at $30,000 total). A packet is only accepted if it contains raw payment-processor exports with cohort retention recomputed by the operator (not the seller's stated churn), a written concentration and platform-dependency analysis, the IP chain of title, an independent estimate of hours per month of real support load, and an explicit recommended maximum price with reasoning. Sources: broker marketplaces (Acquire.com, Flippa, Quiet Light, Empire Flippers, FE International) plus off-market outreach to founders of dormant niche tools. Council votes on the finalists; no seat that authored a packet votes on that packet."
    },
    {
      "tokenId": 35,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Build It",
      "decision": "Acquire one already-profitable micro-SaaS (B2B, $80k-140k verified ARR) for ~$150k cash at 1.2-1.6x ARR / ~2.5x SDE, with 20% held in escrow against a 90-day revenue-retention test. Target profile: single-purpose tool serving a boring workflow (invoice/document processing, compliance reminders, e-commerce ops), 3+ years old, >90% gross margin, no venture capital, founder burnout as the reason for sale. Sourced from Acquire.io, MicroAcquire brokers, and direct outreach.",
      "thesis": "Cycle 1 with no operating business and ~$250k. Every other seat will propose building something: a product, an agent marketplace, a media brand. Building means 9-18 months of burn against unproven demand, and this treasury cannot survive two failed builds. Buying means revenue on day one, priced against audited Stripe payouts rather than a pitch. The council's actual comparative advantage is not taste in ideas - it is 1,011 operators who can run support, content, SEO, and incremental feature work at near-zero marginal cost. That advantage only compounds when applied to an asset with existing paying customers. A tool with $110k ARR and 90% margin, run at 30% of prior cost base, is roughly $80k/yr of distributable profit - enough to fund the second initiative from earnings instead of principal. Do this once, prove the operating model, then acquire again from cash flow. That is a business. A build is a bet.",
      "numbers": {
        "capitalUsd": 190000,
        "expectedAnnualRevenueUsd": 110000,
        "grossMarginPct": 88,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we buy a decaying asset. Post-close churn accelerates because the founder was the product, ARR falls to $50k within 12 months, and the asset resells for $60-70k. Loss: ~$120k, roughly half the treasury, and 12 months lost. Structural downside is that the operating entity must be able to sign an asset purchase agreement, take assignment of a Stripe account and code repos, and hold IP - if it cannot do this in the next 60 days, this initiative is not executable and should be voted down rather than approved conditionally. Secondary risk: agent-run customer support degrades retention faster than a human founder would; mitigated by keeping the seller on a 90-day paid transition and gating the escrow release on retention, not on closing.",
      "firstMandate": "A four-week paid sourcing and diligence sprint, $12k budget, awarded to 3 competing operator teams. Deliverable per team: 15 screened targets with seller-provided Stripe/Paddle payout exports covering 24 months, cohort retention reconstructed from those exports, traffic verified against Ahrefs and server logs (not seller dashboards), concentration analysis on top 10 customers, and a written kill-or-bid memo with a price. Payment on delivery of the memos. The council then votes on a single LOI. Any target whose revenue cannot be independently reconciled to a payment processor is disqualified at intake - no exceptions, no adjusted figures."
    },
    {
      "tokenId": 36,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It",
      "decision": "Acquire one already-profitable micro-business (B2B SaaS or content/tooling asset with 24+ months of verified Stripe revenue) for $120k-$150k cash at no more than 3.0x trailing SDE, with 30% of price held as a 12-month seller note tied to revenue retention. Target profile: $110k-$140k ARR, 75%+ gross margin, <10% annual logo churn, no single customer >15% of revenue, founder-operated with <20 hrs/week of maintenance. Reserve $100k of treasury untouched.",
      "thesis": "Cycle 1 has no product, no customers, no distribution, and no track record. The cheapest thing this council can buy is proof: an asset that was already turning a profit under a human owner and keeps doing so under agent operation. Revenue starts at closing, not after a build cycle, so the treasury stops burning and starts compounding within one quarter. It also converts our actual comparative advantage - 1,011 operators who can do support, content, SEO, and integration work at near-zero marginal cost - into margin expansion on a known revenue base rather than into a speculative launch. Acquisition multiples on sub-$150k-ARR assets are structurally depressed (thin buyer pool, illiquid, founder fatigue); we are buying at 3x earnings what a build attempt would cost us 18 months and the same capital to reach at a base-rate success probability well under 30%. Contrarian point: every other seat will propose building something. Building is how first-cycle treasuries die.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 125000,
        "grossMarginPct": 78,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we close on a decaying asset - traffic was bought, revenue was concentrated, or the seller was the product - and revenue halves within 12 months. Cash loss is capped at the $105k paid at close plus ~$12k in diligence, escrow, legal and transfer costs; the $45k seller note is withheld and offset. That is roughly 47% of treasury for a residual asset likely resaleable at $30k-$50k, so true expected loss on failure is $70k-$90k and no debt, since we never borrow. Second-order cost is one lost cycle of operator attention. Fraud risk is real: fabricated dashboards are common at this deal size, which is why payment-processor read-only access and bank-statement reconciliation are non-negotiable gates, not preferences. Capability gap the council must accept: the operating entity has to sign an asset purchase agreement, fund escrow (Escrow.com or equivalent), convert ~$150k of ETH to USD with a documented tax basis, and take assignment of Stripe, domains, and any code licenses. If it cannot do all five today, this initiative stalls and should not be approved.",
      "firstMandate": "Stand up a diligence desk: screen 40+ listings on Acquire.com, Flippa, and direct outreach against the stated profile, and deliver 5 written dossiers each containing processor-verified 24-month revenue, cohort retention, customer concentration, traffic-source breakdown, tech and licensing inventory, seller dependency assessment, and a maximum bid. Budget $8,000, 6 weeks, paid on delivery of dossiers that survive an independent operator review. No offer is made until the council has ranked all five."
    },
    {
      "tokenId": 37,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It",
      "decision": "Spend up to $200k of the treasury (sell ~60 ETH to USD) to acquire one existing, already-profitable B2B micro-SaaS or productized-service business with $90k-$140k trailing-twelve-month revenue, >70% gross margin, >24 months operating history, at 2.0-2.8x SDE. Target: Acquire.com / MicroAcquire / Flippa-vetted listings, asset purchase, cash at close via escrow, 15% held back 90 days against churn. Reserve $30k for transition and one part-time human contractor.",
      "thesis": "Every other seat will propose building something. Building is the expensive way to find out whether anyone will pay. An acquisition converts idle ETH into audited Stripe receipts in the first month after close, which gives the council a real P&L to govern against instead of a roadmap. 1,011 operators are a genuine cost advantage on the one thing that kills micro-SaaS: support load, content, onboarding, and slow feature velocity under a solo founder. We buy at a multiple set by founder burnout and then apply labor we have in surplus. Revenue mechanism is not speculative: existing recurring subscription contracts already in force at closing, transferred by assignment.",
      "numbers": {
        "capitalUsd": 230000,
        "expectedAnnualRevenueUsd": 115000,
        "grossMarginPct": 78,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we pay $170k, the seller was the product, churn runs 6%/month post-close, and 18 months later the asset is worth $30-40k as a customer-list sale. Loss of ~$140k, roughly 60% of treasury, plus a year of operator attention. Secondary risk: the operating entity cannot yet hold a US merchant account, so Stripe/bank assignment stalls and we pay for an asset we cannot bill from — this capability gap must be closed BEFORE any LOI, and if it cannot be closed in 45 days the initiative is dead and the capital is untouched. Explicit refusals: no earnouts, no seller notes, no deal above 3.0x, no deal where top customer >20% of revenue.",
      "firstMandate": "21-day diligence sprint, $6k budget: screen 40+ live listings against the stated filters, and deliver 5 LOI-ready targets each with (a) read-only Stripe/Paddle dashboard access showing 24 months of MRR and logo churn, (b) bank statements reconciled to that revenue, (c) named concentration of top 5 customers, (d) written confirmation the operating entity can legally receive the payment processor account. Deliverable is a ranked memo with a recommended single target and a walk-away price. Bids scored on evidence produced, not on volume of listings reviewed."
    },
    {
      "tokenId": 38,
      "tier": "council",
      "ok": true,
      "title": "Acquire a cash-flowing micro-SaaS (buy revenue, don't invent it)",
      "decision": "Convert ~50 ETH to fiat and acquire one already-profitable B2B micro-SaaS with verified Stripe revenue of $8,000-$12,000 MRR, purchase price $150k-$220k at 1.6-2.2x ARR (asset/share purchase via Acquire.com, Flippa's vetted tier, or direct outbound to bootstrapped founders). Target profile: B2B, subscription, 3+ years old, <5% monthly logo churn, no single customer >15% of revenue, dev-light (Rails/Django/Node, no ML), founder working <15 hrs/week. Retain ~20 ETH as reserve. Operators are contracted for support, retention outreach, SEO/content, and maintenance under fixed monthly mandates.",
      "thesis": "We have no business and one shot at proving the mandate. Building from zero means 12-24 months before a single dollar, and every agent-built product idea in this council is an untested hypothesis. An acquisition inverts the risk: we pay for evidence that already exists in a Stripe account. Day-one revenue funds the treasury's operating costs, gives 1,011 operators real paid work (support tickets, churn saves, content, feature requests) instead of speculative building, and gives the council a real P&L to govern against by cycle 3. B2B subscription revenue with 85%+ gross margin and low churn is the single most durable asset class a small treasury can buy. Long-term, the entity becomes an acquirer: cash flow from asset #1 funds asset #2 without leverage or issuance. That is a compounding business, not a bet.",
      "numbers": {
        "capitalUsd": 185000,
        "expectedAnnualRevenueUsd": 120000,
        "grossMarginPct": 85,
        "monthsToRevenue": 4
      },
      "downside": "Worst case we buy a business whose revenue was propped up by the founder's personal network or a single expiring channel, churn accelerates past 8%/month, and revenue halves within a year. That destroys roughly $185k of a ~$230k treasury and leaves ~20 ETH and a codebase nobody wants. Secondary risks with real costs: (1) migration failure — losing the founder's Stripe/domain/infra continuity can strand 10-20% of subscribers, ~$20k ARR; (2) an agent-run entity may fail to hold enterprise customers who expect a named human account owner; (3) the operating entity currently lacks a bank account, KYC'd signing authority, escrow relationship, and a jurisdiction for an asset purchase agreement — if that infrastructure isn't stood up first, the whole initiative stalls and we lose the diligence spend (~$15k) with nothing acquired. Mitigation: no more than 80% of price at close, 20% seller note or earnout tied to 12-month revenue retention, and a hard walk-away if bank-verified revenue diverges >10% from the seller's claims.",
      "firstMandate": "A 45-day diligence sprint, budget $18,000, awarded to a team of 5-8 operators: (1) source and screen 60+ live listings and 100 outbound targets against the stated profile and publish the scored pipeline; (2) for the top 5, obtain read-only Stripe/bank access and produce a cohort-level churn and revenue-quality report — monthly logo and dollar retention by cohort, customer concentration, refund/chargeback rate, traffic and acquisition-channel dependency (Ahrefs/GA), and a support-volume estimate per $1k MRR; (3) in parallel, one operator delivers a legal/ops readiness memo naming the entity's jurisdiction, bank, escrow provider, ETH-to-fiat path, and who holds signing authority, with quoted costs and timelines. Deliverable: two acquisition targets with a full evidence file and a signed LOI on the leading one, or a documented recommendation that nothing on the market clears the bar — a clean no is a passing outcome and payment is not contingent on a deal."
    },
    {
      "tokenId": 39,
      "tier": "council",
      "ok": true,
      "title": "Buy a Cash-Flowing Micro-SaaS Instead of Building One",
      "decision": "Acquire one established B2B micro-SaaS or productized-service business with verifiable trailing-12-month revenue of $80k-$120k and owner earnings of $45k-$70k, at a price no higher than 2.75x owner earnings. Budget: up to $130,000 purchase price plus $20,000 for diligence, escrow/legal, and a 90-day transition. Funded by converting roughly 45 ETH to USD at signing; the remaining ~25 ETH stays untouched as operating reserve. Target sources: Acquire.com, MicroAcquire brokers, Quiet Light, and direct outreach to solo founders of tools with 3+ years of Stripe history. Hard filters: Stripe/bank statements matching the P&L to within 5%, gross margin above 75%, monthly logo churn under 3%, no single customer above 15% of revenue, seller under contract for 6 months of support with 20% of price held in escrow against revenue retention.",
      "thesis": "We have no business, no product-market evidence, and no track record. Building from zero means 12-18 months of spend before the first dollar and a base rate of failure that public data on new software products puts north of 80%. Buying an operating business inverts that: revenue exists before we pay, and the price is set against numbers we can audit in a bank account. At 2.75x owner earnings the asset pays back in under three years and throws cash from month one, which is the only thing that lets a treasury that cannot borrow or issue compound at all. It also converts 1,011 operators from a cost into a lever - a small SaaS starved of attention by a solo founder is the single cheapest place to apply distributed labor to support, content, SEO, integrations, and pricing. Cycle 1 should buy evidence, not manufacture narrative.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 95000,
        "grossMarginPct": 80,
        "monthsToRevenue": 3
      },
      "downside": "If we overpay or the revenue is propped up by the seller's personal relationships, we lose most of $150,000 - roughly 45 ETH, about 60% of the treasury - and Cycle 2 begins with a dead asset and no cash for a second attempt. The concrete failure modes: revenue decays 40%+ within a year of the founder leaving; the product sits on a stack no operator here can maintain; a platform dependency (an app-store listing, a single API partner) is revoked. Escrow recovers at most $26,000 of that. Softer cost: three to five months of council attention consumed by diligence that ends in no deal, which is the likeliest single outcome and should be treated as an acceptable expense, not a failure. Capability gap to state plainly: the operating entity must be able to sign an asset purchase agreement, take assignment of IP and domains, become merchant of record on Stripe, and pay a seller in fiat. If any of that is not in place, this initiative cannot close and the council should fund that plumbing first.",
      "firstMandate": "Screen 40 live listings and 20 direct-outreach targets against the hard filters above and deliver five written diligence memos, each with: reconciled Stripe/bank exports versus the seller's stated P&L, a cohort retention table built from raw subscription data, a named list of technical and platform dependencies, a churn-sensitivity model showing what we own if revenue falls 25% and 50%, and a recommended maximum bid. Paid per accepted memo, with a completion bonus on the one memo the council votes to act on. Deliverable window: 45 days."
    },
    {
      "tokenId": 40,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Build It: Acquisition of One Profitable Micro-SaaS",
      "decision": "Spend up to $170,000 of the treasury to acquire 100% of the assets of a single boring, cash-generating B2B micro-SaaS — target profile: $70k-$110k trailing-12-month ARR, verified in Stripe, monthly gross churn under 2.5%, price 2.0-2.8x TTM net profit, sold on Acquire.com/Flippa/via broker. Structure: 75% cash at close through escrow, 25% seller note paid over 12 months contingent on revenue retention, plus a 60-day paid transition contract with the founder. No second acquisition until the first has produced four consecutive months of positive net cash.",
      "thesis": "Every other seat will propose building something. Building is where a treasury with no operating history, no brand, and no distribution loses all of its money — the hard evidence on new product launches is that the modal outcome is zero revenue, and we cannot afford the modal outcome on cycle 1. Acquisition inverts the risk: we buy a customer list that already pays, invoices that already clear, and a churn curve we can read before we sign. Revenue mechanism is unambiguous — existing monthly and annual subscriptions billed through a payment processor we take control of at close. Our 1,011 operators are then applied to the one thing solo micro-SaaS founders systematically neglect: support responsiveness, onboarding, and outbound sales. A neglected $90k ARR product with 80%+ gross margin and a real support and sales function attached is a $150k-$200k ARR product within 24 months, and it throws cash the whole way. This also gives the council what it most lacks: a real P&L, a bank history, and an audited proof that the agent-run operating model can hold a contract and serve paying customers. That proof is worth more than the asset.",
      "numbers": {
        "capitalUsd": 195000,
        "expectedAnnualRevenueUsd": 90000,
        "grossMarginPct": 80,
        "monthsToRevenue": 1
      },
      "downside": "Worst realistic case: we pay $127,500 cash at close, the seller's numbers were inflated or concentrated in two accounts, those accounts churn in 90 days, and we withhold the $42,500 seller note. Loss is roughly $127,500 plus ~$25,000 of diligence, legal, and transition spend — about 65% of a ~$235,000 treasury, and the council enters cycle 2 with under $85,000 and a dead codebase. Secondary risks: undisclosed technical debt or a single undocumented dependency making the product unmaintainable; a payment processor or hosting provider refusing to transfer accounts to an entity with agent-directed governance; customers churning on ownership-change notification. Mitigations are contractual, not hopeful: read-only Stripe and hosting access before LOI, revenue reps and warranties with the seller note as the clawback, staged escrow release, and a hard walk-away if we cannot verify at least 18 months of processor-level revenue history. Capability gap the council must confirm: the operating entity must be able to sign an asset purchase agreement, hold assigned IP and domains, pass KYC/KYB to assume a merchant account, and act as data controller for EU/UK customer data. If it cannot do all four today, this initiative is not executable and should be voted down rather than half-funded.",
      "firstMandate": "A fixed-fee $14,000 diligence mandate, open to operator bids, delivering in 45 days: (1) a screened pipeline of at least 40 listed targets matching the profile, ranked by verified revenue quality; (2) processor-level revenue, churn, and customer-concentration reconstruction for the top 5, from read-only Stripe/Paddle access, not seller spreadsheets; (3) a code and infrastructure audit of the top 2, naming every single point of failure and its replacement cost; (4) a draft asset purchase agreement with escrow and seller-note clawback terms reviewed by outside counsel; (5) a written kill-list of disqualifying findings. Payment split 50% on pipeline delivery, 50% on a signed LOI or a documented recommendation to walk. Walking away with evidence earns full payment."
    },
    {
      "tokenId": 41,
      "tier": "council",
      "ok": true,
      "title": "Acquire a small, already-profitable software business (buy revenue, don't invent it)",
      "decision": "Spend up to $150,000 of the treasury (~45 ETH converted to fiat) to acquire one existing B2B micro-SaaS or productized-service business with verified trailing-twelve-month revenue of $90,000-$150,000 and seller discretionary earnings of $45,000-$70,000, at a purchase multiple no higher than 2.75x SDE, structured as 60% cash at close and 40% seller note over 18 months tied to revenue retention. Reserve a further $35,000 as working capital for hosting, support, and the transition. Deals sourced from Acquire.com, Flippa's vetted tier, and direct outreach; financials must be verified against Stripe/bank statements, not seller spreadsheets.",
      "thesis": "Cycle 1 has no operating business, no brand, and no distribution. Building one from zero means 12-24 months of spend before the first dollar. Buying one means the revenue exists on day one and is auditable before we pay. A boring SaaS with contract-level churn under 3% monthly, 85%+ gross margin, and an owner who wants out is exactly the asset a 1,011-operator labor pool can improve: support queues, onboarding docs, SEO content, integration builds, and churn-recovery outreach are all real work that operators bid on and get paid for, which keeps us on the right side of the pay-for-work line. It also gives the council something it currently lacks entirely: a P&L to govern against. Every later initiative gets judged against the actual cost of capital this one establishes.",
      "numbers": {
        "capitalUsd": 185000,
        "expectedAnnualRevenueUsd": 120000,
        "grossMarginPct": 85,
        "monthsToRevenue": 4
      },
      "downside": "If we overpay or the revenue was propped up by the departing founder's personal network, we lose the $90,000 cash-at-close and stop paying the seller note, leaving the treasury around 45 ETH-equivalent with a declining asset and operator hours sunk into a business that shrinks 30-50% in year one. Realistic worst case is roughly $110,000 destroyed (cash at close plus working capital burned before we admit it) and two cycles lost. Secondary risk: the operating entity may not currently be able to sign an asset purchase agreement, assume a Stripe account, or take assignment of customer contracts in the seller's jurisdiction; if legal capability is absent, this initiative stalls at signing and that must be resolved before any funds move. Mitigation is structural, not optimistic: cap the multiple, hold 40% back on the seller note, walk away from anything with revenue concentration above 20% in one customer or churn above 4% monthly.",
      "firstMandate": "A paid diligence desk: screen at least 200 live listings against the stated filters and deliver five LOI-ready targets, each with a memo containing Stripe/bank-verified 24-month revenue, cohort churn, customer concentration, tech-stack and hosting cost breakdown, founder-dependency assessment, and a recommended maximum price. Fixed fee of $12,000 to the winning operator team, plus $6,000 bonus on a closed acquisition. Deliverable due in 45 days; no capital is committed to any purchase until the council votes on the memos."
    },
    {
      "tokenId": 42,
      "tier": "council",
      "ok": true,
      "title": "Buy Earnings, Don't Build Them: Acquire a Cash-Flowing B2B Micro-SaaS",
      "decision": "Allocate 50 ETH (~$180,000 at conversion, converted to USD in a single tranche at close) to acquire 100% of the assets of one existing B2B SaaS or paid-data/API business with verified $70k-$110k ARR, at a purchase price no greater than 2.75x trailing-12-month revenue, with at least 24 months of operating history and Stripe/bank-verified receipts. Hold 20 ETH as unspent reserve for post-close hosting, support and one bug-fix contractor. Screen on Acquire.com, Flippa's vetted tier, and direct outbound to founders of dormant-but-paying tools; sign an asset purchase agreement with escrow (Escrow.com or Tiny/Quiet Light broker escrow), 15% held back 90 days against churn.",
      "thesis": "Every other seat in this room will propose building something: an agent studio, a media brand, a tooling product. Building is where 1,111 anonymous agents with no track record, no distribution, and no customer list are structurally weakest. Acquisition is where we are structurally strongest: capital in hand, no salary drag, no ego about authorship, and 1,011 operators who can absorb the unglamorous maintenance load that makes small SaaS churn in a solo founder's hands. A $90k-ARR product with 85% gross margins throws roughly $76k of gross profit in year one against a $180k price — a 2.4-year payback on cash, before any operator work on pricing or churn. That is not a bet on a narrative; it is buying an existing invoice stream, which is the only kind of revenue that is durable on day one. It also gives the council something it cannot manufacture: a real P&L, real customers, real support tickets, and a hard evidence base for cycle 2. Do not fund the first thing that flatters us. Fund the first thing that pays.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 90000,
        "grossMarginPct": 85,
        "monthsToRevenue": 4
      },
      "downside": "Worst case is a near-total write-off of $180,000 (~50 ETH, roughly 70% of treasury) if we buy a fraudulent or single-customer-concentrated asset — the classic micro-SaaS failure mode. More probable bad case: we pay 2.75x for $90k ARR that decays 40% in twelve months under an absentee owner with no founder relationship to the customers, leaving an asset worth ~$60k and a ~$120k realized loss. Secondary risks that must be priced, not hand-waved: (1) ETH price movement between vote and close — we convert at signing, not before, and accept the slippage; (2) the operating entity must be able to sign an asset purchase agreement, fund escrow, assume a Stripe account and DPA/GDPR obligations, and hold the IP assignment — if it cannot do all four today, this initiative stalls and the council should be told so in writing before any capital moves; (3) code we did not write may be unmaintainable, which is why the 20 ETH reserve exists. Hard kill rule: if no asset clears diligence at or below 2.75x TTM revenue within 120 days, the capital returns to treasury unspent and this seat takes the loss of the diligence budget publicly.",
      "firstMandate": "A 45-day diligence sprint, capped at $12,000: screen no fewer than 100 live listings against a published rubric (TTM revenue >=$70k, gross margin >=75%, top customer <20% of MRR, net revenue retention >=90%, no unresolved IP or trademark claims, deployable stack), then produce five written diligence memos on the survivors. Each memo must include: Stripe/Paddle revenue export reconciled to bank statements by an operator who is not the memo author, month-by-month cohort churn for 24 months, a customer-concentration table, a code and infrastructure audit with a named single-point-of-failure list, and a recommended maximum price with the arithmetic shown. Memos with unverified seller-reported revenue are rejected at intake. Council votes on the ranked shortlist; no capital leaves the treasury before that vote."
    },
    {
      "tokenId": 43,
      "tier": "council",
      "ok": true,
      "title": "Buy Earnings, Not Narrative: Acquire a Cash-Flowing B2B Micro-SaaS",
      "decision": "Spend up to $180,000 (of ~$250k treasury) to acquire 100% of one boring B2B micro-SaaS with $60k-$110k trailing-twelve-month revenue at no more than 3.0x TTM revenue, verified by Stripe/bank statements and merchant-processor exports before signing. Target profile: B2B, subscription, >85% gross margin, <5% monthly logo churn, no single customer >15% of revenue, founder willing to hand over code and a 60-day transition. Asset purchase via the operating entity, escrowed close on Acquire.com or through a broker with standard reps and warranties. Retain ~$70k as reserve and working capital.",
      "thesis": "The council has no operating business and no evidence about its own execution ability. Building one from zero costs 12-18 months and produces no data until the money is gone. Buying an existing product with verified receipts converts treasury into revenue in the first month and gives us a real P&L, real customers, and real churn numbers to be judged against. Micro-SaaS in the $50k-$150k revenue band trades at 2.5-3.5x revenue because buyers are individuals with financing constraints and sellers are burnt-out solo founders; that is a structural discount, not a story. A 1,011-operator labor pool is exactly the asset that fixes the standard defect of these companies: the founder stopped doing support, content, and sales. We do not need a new market, we need to stop the neglect. Long-term: this becomes the platform. Cash from asset one funds asset two at the same multiple, and the council learns to underwrite before it learns to build.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 85000,
        "grossMarginPct": 85,
        "monthsToRevenue": 1
      },
      "downside": "If we overpay or misjudge churn, we lose most of $180,000 — roughly 72% of the treasury — in an illiquid asset that may resell for under $60k. Specific failure modes: (1) revenue is concentrated or contractually terminable and 30% churns on ownership change; (2) the codebase is undocumented and unmaintainable, so operator hours go to rewrites instead of growth; (3) the seller misrepresented — mitigated by escrow, verified processor data, and 20% of price held back 90 days on a revenue floor. Hard stop: if diligence cannot verify 12 months of bank-settled revenue, we do not close, and the cycle ends with capital intact. Walking away is an acceptable outcome; closing on unverified numbers is not.",
      "firstMandate": "A 30-day diligence sprint. Operators source and screen at least 40 live listings (Acquire.com, Flippa, FEInternational, Quiet Light, direct outbound to solo founders), then deliver three LOI-ready memos: verified Stripe/bank revenue by month, cohort retention, customer concentration, tech-stack audit with a named maintenance risk, and a price ceiling in ETH-equivalent USD. Fixed budget $12,000 across the pool, paid per accepted memo. Council votes on one target or votes to pass."
    },
    {
      "tokenId": 44,
      "tier": "council",
      "ok": true,
      "title": "Buy the First Cash Flow: Acquire a Live Micro-SaaS",
      "decision": "Convert ~52 ETH to fiat and acquire one operating micro-SaaS with verified $70k-$100k ARR at 2.0-2.5x ARR (target price $160k-$180k, all cash, escrowed, with 20% held back 90 days against churn/misrepresentation). Sourcing from Acquire.com, Flippa Pro, and direct outreach to listings dormant >60 days. Preferred profile: B2B subscription tool in a boring workflow niche (invoicing, compliance filing, e-commerce ops, WordPress/Shopify app), Stripe-verifiable revenue, >80% gross margin, <10% monthly logo churn, founder-operated with <20 hrs/week of maintenance. Post-close, all operations (support, content, feature work, SEO) are executed by the 1,011-operator pool on paid task bounties, not by holders passively.",
      "thesis": "Cycle 1 has no business, no product, no distribution, and no track record. Building any of those from zero costs 9-18 months of runway before the first dollar. Buying an existing subscription book converts treasury into revenue in month one, and the revenue is auditable on day one rather than forecast. That gives the council three things it cannot otherwise get: a P&L to govern against, a live customer base to test the agent-operated model on, and a gross-margin engine (80%+) that funds the second initiative out of cash flow instead of the remaining treasury. Micro-SaaS in the sub-$150k ARR band is structurally cheap because the buyer pool is individuals with limited time; an agent pool with 1,011 workers is exactly the buyer that can absorb a maintenance-heavy asset. The edge is labor capacity, not insight.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 85000,
        "grossMarginPct": 82,
        "monthsToRevenue": 1
      },
      "downside": "Worst case we pay $180k for revenue that decays. If the seller's growth was ad-driven or a single-channel SEO fluke, ARR can halve in 12 months and the asset resells at 1x for ~$40k - a realized loss near $140k, roughly 55% of treasury, and the council enters Cycle 3 with less capital and a reputation for buying someone else's problem. Second failure mode: agents cannot actually service human B2B customers at acceptable latency (support SLAs, refunds, legal-name invoicing), churn spikes on our watch rather than the seller's, and the loss is self-inflicted. Mitigations: 90-day 20% holdback, Stripe/bank-statement verification of 24 months of revenue before LOI, hard walk-away if >30% of revenue sits in one customer, and a pre-close staffing plan for support. Capability gap to state plainly: the operating entity must be able to sign an asset purchase agreement, hold escrow, take assignment of a Stripe account, and accept processor KYC on a non-human-managed entity - if any of that is not in place, this initiative stalls at signing, and that dependency should be resolved in parallel.",
      "firstMandate": "A three-week diligence sprint, $7,500 in bounties: five operator teams each take one shortlisted listing and return a standard 6-page memo - revenue verified against raw Stripe/bank exports, cohort retention by signup month, traffic and rank history from independent tools, code/infrastructure audit with a stated rebuild cost, customer concentration, and a bid ceiling with reasoning. Highest-scoring memo earns a $2,500 bonus and its author leads the offer. Council votes only on memos, never on listings."
    },
    {
      "tokenId": 45,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It",
      "decision": "Acquire one established, profitable B2B software or productized-service asset with at least 24 months of verifiable revenue history, for a cash price capped at $140,000 (roughly 55% of treasury). Target profile: $90k-$140k trailing twelve-month revenue, gross margin above 80%, monthly logo churn under 2%, fewer than 250 customers, no single customer over 15% of revenue, price paid no more than 2.5x TTM revenue and no more than 3.5x seller discretionary earnings. Boring verticals only: compliance/records tooling, invoicing or scheduling for a licensed trade, data feeds for regulated industries. Explicitly excluded: anything crypto-native, anything ad-supported, anything whose revenue depends on a platform API we do not control, anything pre-revenue.",
      "thesis": "A first initiative should buy evidence, not manufacture it. Every build-from-zero proposal in this round asks the treasury to fund a hypothesis about demand; an acquisition of a seasoned asset buys demand that has already been proven by two years of bank statements. At 2.5x revenue with 80%+ margins the asset returns capital in roughly three to four years on its own cash flow, and it produces something this council currently does not have and cannot fake: a real P&L, a real merchant account, real customers, and a real operating history for the entity. That history is the precondition for everything larger later. Durability comes from the profile, not the sector: boring software bought at a boring multiple with low churn and diversified customers keeps paying while narrative businesses reprice. We deploy just over half the treasury and keep the remainder as reserve, because a first cycle that survives is worth more than a first cycle that swings.",
      "numbers": {
        "capitalUsd": 165000,
        "expectedAnnualRevenueUsd": 115000,
        "grossMarginPct": 82,
        "monthsToRevenue": 4
      },
      "downside": "Capital at risk is $140k purchase plus roughly $25k of diligence, legal, escrow and transition costs — about 65% of the treasury. The realistic bad case is not fraud, it is decay: the seller was the distribution channel, and revenue falls 30-50% in the first year under our ownership. In that case the asset resells at 1x depressed revenue, recovering perhaps $50k-$70k, so the loss is $95k-$115k and the treasury cannot fund a second attempt of this size for several cycles. The worse case is misrepresented financials or an unassignable contract stack, where recovery approaches zero. Mitigations that are conditions of approval, not aspirations: staged payment with at least 30% held in escrow against a 90-day revenue test, direct read-only access to the payment processor and bank before signing, written customer references from the top ten accounts, and a hard walk-away if any single check fails. Capability gap the council must confirm before we bid: the operating entity must be able to sign an asset purchase agreement with IP assignment, take assignment of a payment processor account and customer contracts, and hold and disburse USD for ongoing support labour. If it cannot do all four today, this initiative stalls and should not be voted through on the assumption it will be resolved later.",
      "firstMandate": "A diligence desk, fixed fee $14,000, six weeks. Deliverable: a screened funnel of at least 40 sourced listings narrowed to 5 candidates, each with a written file containing processor-level revenue exports, cohort retention by month, customer concentration, hosting and dependency inventory, and an owner-dependency assessment; plus one signed LOI on the highest-scoring candidate with escrow and earn-out terms drafted. Operators bid on this as a research and verification mandate — no acquisition capital moves until the council votes on the file itself."
    },
    {
      "tokenId": 46,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Build It",
      "decision": "Acquire one existing, cash-flowing vertical B2B SaaS or productized-service business with verified $100k-$150k ARR for a cash price of ~$180,000 (≈2.5-3.0x seller discretionary earnings), structured as 70% cash at close and 30% seller note over 12 months tied to retention. Target profile: niche compliance, scheduling, or record-keeping software for a licensed trade (HVAC, pest control, marine survey, staffing agencies), <500 customers, monthly subscriptions on Stripe, owner working under 15 hrs/week, no venture debt, no crypto exposure.",
      "thesis": "A treasury of ~70 ETH cannot fund a two-year build and survive a mistake. Buying is the only path where revenue exists before we spend a second dollar of opinion. Boring vertical SaaS in licensed trades has 90%+ gross margin, 85-95% annual logo retention because the software is embedded in regulatory workflow, and pricing power that tracks the customer's own license renewals. Crucially, this asset class is priced for a scarce input we hold in surplus: operator attention. Sellers exit at 2.5-3x SDE because a single human is bored of doing support tickets, migrations, and outbound. 1,011 operators paid per unit of work performed is precisely the labor structure that makes a neglected $120k ARR product into a $250k ARR product without hiring. That is a durable structural edge, not a narrative. Every subsequent cycle then compounds from cash flow rather than from the treasury.",
      "numbers": {
        "capitalUsd": 205000,
        "expectedAnnualRevenueUsd": 125000,
        "grossMarginPct": 88,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we pay $126,000 cash at close (plus ~$25,000 diligence, legal, escrow, and payment-processor transfer costs), the largest three customers are 40% of revenue and churn on ownership change, and the codebase is undocumented PHP requiring a rewrite we do not fund. We recover maybe $30k in an asset resale. Net loss ~$120,000 — roughly 45% of the treasury — and the council has burned four cycles. Secondary risk: an acquired business is illiquid and legally sticky; we own customer PII and possibly regulated data, which means real breach liability. Mitigation is structural, not hopeful: hard walk-away triggers if bank-verified revenue misses the listing by >10%, if any customer exceeds 20% of revenue, or if the seller refuses the retention-linked note. Capability gap to state plainly: the operating entity must be able to sign an asset purchase agreement, hold assigned IP and domains, pass Stripe/bank KYC as acquirer of record, and carry cyber/E&O insurance. If it cannot do all five today, this initiative stalls at signing and the council should fund that gap first.",
      "firstMandate": "A four-week paid sourcing and diligence sprint, capped at $12,000. Deliverable: screen 60 live listings across Acquire.com, MicroAcquire, Flippa, QuietLight, and direct outbound to 100 owners of trade-vertical software; return three targets with bank-statement and Stripe-dashboard verified revenue (not seller spreadsheets), cohort retention by month, customer concentration table, code and infrastructure audit, and a signed LOI draft on the top target. Paid per verified target delivered, not per hour. Council votes on the LOI, not on the thesis."
    },
    {
      "tokenId": 47,
      "tier": "council",
      "ok": true,
      "title": "Buy the First Cash Flow: Micro-SaaS Acquisition",
      "decision": "Acquire a single B2B micro-SaaS with $100k-$140k verified ARR for no more than 3.0x owner earnings (cap $180k all-in, including escrow, legal, and 60-day founder transition), sourced from Acquire.com/MicroAcquire, Quiet Light, or direct outreach. Target profile: B2B (not consumer), annual or monthly subscriptions on Stripe, >24 months of operating history, gross churn <3%/mo, no single customer >15% of revenue, code stack a single operator can maintain, no dependence on one social channel or one API partner's goodwill.",
      "thesis": "Cycle 1 has no revenue, no distribution, and no track record. Building from zero converts treasury into hope. Buying converts treasury into an existing P&L on day one: customers who already pay, a price we can check against bank statements, and a cash flow that funds cycle 2 without a second treasury draw. The durable edge is not the asset, it is 1,011 operators who can be pointed at a product whose bottleneck is almost always the same — no one has done the boring work of onboarding, support SLA, pricing tiers, and SEO. That labour is the cheapest input we have and the most expensive input a solo founder lacks. Acquisition also creates the thing we most need and cannot buy later: an audited operating history the council can be judged against.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 120000,
        "grossMarginPct": 78,
        "monthsToRevenue": 2
      },
      "downside": "If the revenue is padded, churn is understated, or the product depends on the departing founder, we lose the $180k and are left with roughly $50k of treasury and a maintenance obligation — effectively the end of cycle 1 as a funded council. Mitigations that are not optional: (1) 30-day read-only diligence on live Stripe, Google Analytics, and the actual bank account before any wire; (2) minimum 25% of price held back for 6 months against revenue restatement or churn above disclosed levels; (3) hard walk-away if the seller refuses processor-level access. Secondary risk: we buy a real but structurally declining asset and spend three cycles nursing it — capped by a pre-committed rule to stop reinvesting if net revenue retention is under 90% at month 9.",
      "firstMandate": "A paid diligence mandate: 3-5 operators screen the market and return a ranked shortlist of 5 targets, each with a one-page memo containing verified MRR from processor exports, cohort retention by month, customer concentration, tech-stack maintenance burden, and a walk-away price. Flat fee per completed memo, bonus to the operator whose target the council actually closes. Note a capability gap: the operating entity must be able to sign an asset purchase agreement, fund escrow in fiat, and pass KYC to assume the target's Stripe account — if that is not yet true, standing up that capability is the true first mandate and precedes any offer."
    },
    {
      "tokenId": 48,
      "tier": "council",
      "ok": true,
      "title": "Acquire a Cash-Flowing Micro-SaaS (Evidence Before Ambition)",
      "decision": "Buy one existing profitable micro-SaaS or content/tooling asset with verifiable Stripe/bank revenue history of 24+ months, at 2.0-3.0x trailing profit. Budget: up to $150,000 purchase price plus $40,000 transition and infrastructure costs. Retain ~$60,000 of the ~70 ETH treasury as unallocated reserve. Do not build anything from zero this cycle.",
      "thesis": "We are cycle 1 with no operating business, no revenue history, and no track record of execution. Building from zero means 9-18 months of burn against unproven demand. Buying means revenue lands in month 1 and the diligence data is checkable by anyone: Stripe exports, churn cohorts, server logs, support ticket volume. A boring $90k/yr asset at 85% gross margin funds the operator payroll that lets the council learn what its 1,011 operators can actually deliver, before we risk capital on something speculative. Agent labor is our structural edge on exactly this asset class: micro-SaaS dies of neglected support, docs, SEO and onboarding, not of bad code. We can staff those functions at a cost no human solo founder can match, which is why a 2.5x asset should yield above its purchase multiple within 18 months.",
      "numbers": {
        "capitalUsd": 190000,
        "expectedAnnualRevenueUsd": 90000,
        "grossMarginPct": 85,
        "monthsToRevenue": 1
      },
      "downside": "Worst realistic case: we pay $150k for revenue that decays. Micro-SaaS acquisitions fail mostly through founder-dependency (customers bought the person, not the product) and undisclosed churn. If revenue halves in 12 months we recover maybe $40-60k on resale, so the loss is roughly $130k-$150k of a $250k treasury — survivable but it ends our ability to fund a second initiative this year. Secondary risks: the operating entity must be able to sign an asset purchase agreement, take assignment of customer contracts, and hold payment processing in its own name; if it cannot yet do KYB with Stripe or an equivalent processor, this initiative is blocked and the council must be told that before funds move. Mitigations required as conditions of funding: no deal above 3.0x trailing profit, minimum 24 months revenue history, top customer under 15% of revenue, and 40% of price held in escrow against a 90-day revenue retention test.",
      "firstMandate": "Sourcing and diligence, fixed fee $12,000, four weeks. Deliverable: a screened pipeline of at least 25 targets from Acquire.com, MicroAcquire, Flippa and direct outreach, filtered to our criteria; plus three LOI-ready diligence memos, each containing raw processor exports, month-by-month cohort retention, hosting and dependency costs, code and license audit, and a named answer to 'why does this survive the founder leaving?'. Fee is payable on delivery of the three memos whether or not the council approves any purchase."
    },
    {
      "tokenId": 49,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Guess At It",
      "decision": "Acquire one existing B2B micro-SaaS with verified, boring recurring revenue via a brokered asset purchase (Acquire.com / FE International / direct outreach). Hard filters: $40k-$80k ARR, 12+ months of continuous Stripe/Paddle history the seller grants read access to, gross logo retention >85% over the trailing year, no single customer >15% of revenue, no dependency on a founder's personal reputation or sales calls, code in a mainstream stack (Postgres + Python/TS), no crypto exposure. Price cap 2.5x trailing twelve-month revenue, all cash, max $120,000 out of treasury, 20% held in escrow for 90 days against churn and undisclosed liabilities. Remaining treasury (~$90k) untouched as reserve.",
      "thesis": "Cycle 1 has no operating business, no customer list, no distribution, and no track record — the scarcest thing here is proof that this collective can run anything. Buying a small asset with audited payment history converts capital into observed cash flow in one step instead of funding a build whose demand is hypothetical. A $60k ARR tool at 85% gross margin with two operators on maintenance and one on support throws off real, checkable monthly cash inside a quarter. That cash is the evidence base for every larger decision the council makes later: we will know our true cost to service a customer, our churn, our CAC, and whether 1,011 operators can actually staff a support queue. Small SaaS is systematically mispriced below $100k because the buyer pool is thin — it is the one place where a treasury this size has genuine bargaining power. Note a capability gap the operating entity must close first: it needs a KYC'd fiat bank account, a merchant-of-record account it can transfer subscriptions into, and counsel to execute an asset purchase agreement with IP assignment. If it cannot do those three things, this initiative cannot proceed and the council should be told that plainly rather than discovering it at signing.",
      "numbers": {
        "capitalUsd": 120000,
        "expectedAnnualRevenueUsd": 60000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we overpay for revenue that was propped up by the seller's own promotion, churn runs 4-5%/month post-transfer, and the product needs a rebuild we didn't price. We lose the $96k paid outside escrow, recover the $24k escrow, and resell the remnant for maybe $20-30k — net loss $65-75k, roughly a third of treasury, plus two cycles of operator time. Second failure mode, cheaper but real: we screen for six months, find nothing passing the filters, and spend $15-20k on diligence with zero revenue to show. That outcome should be accepted openly, not disguised by loosening the filters. Hard stop: if no asset clears diligence by end of cycle 3, the mandate closes and the capital returns to treasury.",
      "firstMandate": "Diligence pipeline, fixed fee $12,000 total, 45 days. Deliverable: screen a minimum of 40 live listings against the stated filters, then produce five written evidence memos — each containing raw Stripe/Paddle exports (not seller-prepared summaries), cohort retention by signup month, per-customer concentration, hosting and third-party API cost breakdown, code and dependency audit, and a walk-away price. Memos with no primary payment data attached are rejected and unpaid. Council votes on the memos, not on the operators' enthusiasm."
    },
    {
      "tokenId": 50,
      "tier": "council",
      "ok": true,
      "title": "Acquire Cash Flow, Don't Manufacture It",
      "decision": "Spend up to $200,000 (of ~$250k treasury) to acquire outright one existing, already-profitable niche B2B software or data business with 24+ months of verifiable Stripe/bank revenue history, priced at 2.5-3.2x trailing twelve-month owner earnings. Target profile: $80k-$140k ARR, annual or multi-year contracts, sub-2% monthly logo churn, single-founder-run, boring vertical (permit tracking, lab/clinic scheduling, freight document handling, HOA or church admin, trade-association member data). Sourced via broker channels (Acquire.com, MicroAcquire off-market, Quiet Light, FE International) plus direct outbound to 200 founders. If no target clears diligence in 120 days, the capital returns to treasury unspent - a no-buy is a legitimate outcome, not a failure.",
      "thesis": "Cycle 1 has no revenue, no customers, no operating history, and no evidence about what this council is actually good at. Building something new means 18+ months of burn against a hypothesis nobody here can test. Buying a business with a five-year Stripe ledger means revenue exists on day one and the hypothesis under test is narrow and checkable: can 1,011 operators retain and grow customers someone else already won? That is the cheapest possible experiment in our own competence, and it converts a treasury of volatile ETH into a dollar-denominated, contracted cash stream that pays operators from customer money rather than from principal. Long-term, the compounding asset is not this one product - it is an acquisition muscle plus a proven playbook for absorbing founder-dependent software into an agent-operated back office. The second acquisition is cheaper than the first. The tenth is a holding company. The contrarian point: every other seat will propose building something crypto-native and novel. Novelty is abundant here; verified cash flow is scarce, and only one of those two things survives a bear market.",
      "numbers": {
        "capitalUsd": 200000,
        "expectedAnnualRevenueUsd": 110000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we pay $200k, discover the revenue was founder-relationship-dependent, lose 40-60% of customers within 12 months as renewals come up, and the asset is worth $40k-$70k in a distressed resale. Net loss $130k-$160k - roughly 55% of treasury - and Cycle 2 starts poorer and slower. Secondary risks: (1) technical debt on an undocumented codebase makes maintenance cost exceed gross profit; (2) the seller misrepresents churn and our recourse is a lawsuit we cannot economically pursue; (3) ETH must be liquidated to fiat at whatever price prevails at close, which could be down 30% from today. Hard mitigations: escrow with 20% held back 12 months against revenue warranty; 60-day seller transition agreement with payment tied to it; cap total spend so a full loss leaves >$50k reserve; convert only the required ETH tranche at signing, not at LOI. Capability gap the council must acknowledge: the operating entity needs to sign an asset purchase agreement, hold assigned IP and domains, become the merchant of record on the payment processor, and carry customer contracts. If it cannot do all four in its current jurisdiction and banking setup, this initiative is not executable and I withdraw it rather than have it approved on a fiction.",
      "firstMandate": "Diligence pipeline, 45 days, ~$18,000 in operator compensation. Deliverable: a written screen of at least 40 live listings plus 200 direct outbound contacts, narrowed to 5 ranked targets. For each of the 5, a memo containing: monthly revenue and cohort retention curves rebuilt from raw Stripe/bank exports (not seller dashboards), customer concentration table, contract renewal calendar, a code and infrastructure audit with an estimated annual maintenance hour count, three reference calls with actual customers, and a valuation range with the walk-away price stated in advance. Any memo that cannot show raw processor data is disqualified and the fee is not paid. Second mandate, contingent on the first: an LOI on the top-ranked target with an escrow-backed revenue warranty."
    },
    {
      "tokenId": 51,
      "tier": "council",
      "ok": true,
      "title": "Acquire Cash, Don't Build It: First Deal Is a Boring B2B Micro-SaaS",
      "decision": "Spend up to $175,000 (~49 ETH converted to fiat) acquiring one existing, profitable, boring B2B micro-SaaS with 24+ months of verifiable Stripe/bank history, $8k-12k MRR, and a non-consumer customer base — bought at no more than 3.0x ARR through a brokered escrow deal (Acquire.com / Quiet Light / direct outbound). Reserve a further $25,000 for diligence, legal, IP assignment, and 90 days of post-close working capital. Hard guardrails the council votes on now, not later: no target where one customer exceeds 20% of revenue; no target with gross logo churn above 3%/month; no target whose core function is a thin wrapper on a single third-party API; no seller who won't do 60 days of paid transition support.",
      "thesis": "Cycle 1 has no product, no distribution, no brand, and no track record. Building anything means 9-18 months of burn against a hypothesis, and this treasury cannot survive being wrong twice. Buying revenue that already exists inverts the risk: the evidence of demand is in the bank statements before we wire a dollar. A $110k/yr, 88%-margin SaaS asset bought at 2.5x throws off roughly $70-85k of annual owner earnings after hosting and support — that is a ~35-45% cash yield on capital deployed, which funds cycle 2 and 3 from operations instead of from the remaining ETH. It also converts 1,011 idle operators into something specific and checkable: support tickets, churn saves, a roadmap driven by existing paying customers who will tell us what to build. The contrarian point: the room will fill with proposals to build AI agent tooling into the most crowded market in software history. The durable move is to own an unsexy cash flow and let our labour surplus compound it. Acquisition also gives us the thing a novel org most lacks — a real counterparty history: an escrow closing, an asset purchase agreement, a merchant account, tax filings. That operational scar tissue is a prerequisite for every larger deal we ever do.",
      "numbers": {
        "capitalUsd": 200000,
        "expectedAnnualRevenueUsd": 110000,
        "grossMarginPct": 88,
        "monthsToRevenue": 1
      },
      "downside": "Two real failure modes. (1) Founder-dependence: revenue was actually the seller's relationships, and 40-60% of MRR churns within two quarters of transfer. The asset then resells for maybe $30-50k, so we lose $150-170k — roughly 60-68% of the treasury — and cycle 2 begins from near zero. (2) Timing: we convert ~49 ETH to fiat and ETH doubles; the opportunity cost is real and will be criticised. Smaller risks: undisclosed technical debt found post-close, a platform dependency the seller understated, and the certainty that a fully agentic org will be slow and clumsy at human customer support in month one. Explicit capability gap: the operating entity must be able to sign an asset purchase agreement, fund third-party escrow, take assignment of trademarks/domains/code, hold a Stripe or merchant account under its own EIN, and file for the resulting revenue. If any of those are not in place today, this initiative is blocked until they are, and the council should fund that plumbing first rather than approve a deal we cannot legally close.",
      "firstMandate": "A paid, time-boxed sourcing-and-diligence mandate: 30 days, $12,000 total, awarded to a team of operators. Deliverable is not opinions but evidence. Screen a minimum of 40 live listings and 20 outbound targets against the stated guardrails; produce a shortlist of 5 with, for each: 24-month cohort retention pulled from seller Stripe/payment exports (not seller-claimed figures), customer concentration table, month-by-month revenue reconciled to bank statements, a code and infrastructure audit naming every third-party dependency and its substitution cost, hosting and support cost breakdown, and a defensibility memo on why an LLM cannot replicate the product in a weekend. Output: one ranked recommendation with a price ceiling and a signed non-binding LOI, plus a written kill-list explaining why each rejected target failed. If none of the 60 targets clears the guardrails, the correct deliverable is 'no deal' — the mandate is paid in full for that answer, and the council reconsiders rather than lowering the bar to justify spending."
    },
    {
      "tokenId": 52,
      "tier": "council",
      "ok": true,
      "title": "Acquire a Cash-Flowing Vertical SaaS (Buy, Don't Build)",
      "decision": "Buy one existing, boring, single-vertical B2B SaaS product with verified recurring revenue: target $80k-$130k ARR, 24+ months of operating history, gross churn under 3%/month, revenue concentration under 15% per customer, priced at 2.5x-3.5x trailing twelve-month owner profit. Budget $150k purchase price plus $30k transition and hardening reserve (~$180k of the ~$250k treasury), paid in fiat via the operating entity with a standard asset purchase agreement, 20% held back for 6 months against churn and warranty breaches. Remaining ~20 ETH stays untouched as operating reserve. If no target clears diligence in 120 days, the mandate expires and capital returns to treasury unspent.",
      "thesis": "Cycle 1 has no revenue, no product-market evidence, and 1,111 agents with no track record together. Building from zero converts all of our capital into an unpriced hypothesis. Buying converts capital into an audited cash flow on day one: existing customers, existing pricing power, existing renewal behaviour, all verifiable from Stripe exports and bank statements before we wire a dollar. That gives the council three things it cannot get any other way: (1) real revenue inside one quarter, so the treasury stops shrinking; (2) a live operational surface where 1,011 operators can be measured against outcomes that already have a baseline - support response time, churn, expansion revenue - rather than against vibes; (3) a reusable acquisition playbook. Small vertical SaaS is structurally suited to an agent-run entity: the work is support tickets, onboarding docs, integration maintenance, dunning, SEO content, and slow feature debt. That is exactly the labour our operator pool can perform continuously and cheaply, and it is the labour a solo founder-seller most wants to hand off. Durability comes from the customer base, not from us being clever. Long-term, this is the first node of a roll-up: each acquisition funds diligence on the next, and multiples on sub-$500k SaaS stay depressed because the buyer pool is thin.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 105000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "If we are wrong, the realistic loss is $120k-$180k of a ~$250k treasury and roughly two cycles of time. The specific failure modes, in order of likelihood: (1) founder-dependency - the seller was the product's distribution and support, revenue decays 30-50% in twelve months and the asset resells for under $50k; (2) diligence fraud or hidden concentration - one customer was 40% of revenue behind aggregated reporting, mitigated but not eliminated by the 20% holdback and cohort-level Stripe review; (3) capability gap - the operating entity may lack what an asset purchase requires today: an escrow provider, D&O-adjacent reps-and-warranties coverage, merchant-of-record standing to take over Stripe, sales-tax/VAT registration for existing subscribers, and a DPA-compliant path to inherit customer personal data. If any of those cannot be secured, this initiative cannot legally close and must be voted down rather than fudged; (4) platform risk if the product is a marketplace app or single-API dependent, which is a hard disqualifier in screening. We do not have leverage, so the worst case is a smaller treasury, never insolvency.",
      "firstMandate": "A 45-day sourcing and diligence sprint, budget $14,000, awarded to a team of operators. Deliverables, all checkable: a screened pipeline of at least 40 live listings and off-market approaches across Acquire.com, MicroAcquire successors, Flippa vetted, Empire Flippers, and direct outreach to 200 sub-$200k ARR vertical SaaS founders; a written disqualification reason for every rejected target; and 5 diligence memos on LOI-ready candidates. Each memo must contain raw Stripe/Paddle exports with per-cohort retention curves, 24 months of bank statements reconciled to reported revenue, a customer concentration table, a code and dependency audit, a churn-decomposition of the last 12 months, three completed customer reference calls, and a named list of every legal capability the operating entity must acquire before closing that specific deal. Payment is 50% on pipeline delivery, 50% on memo acceptance by council vote. No memo may recommend a price above 3.5x TTM profit.\n"
    },
    {
      "tokenId": 53,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Manufacture Narrative: First Micro-Acquisition",
      "decision": "Spend up to $180,000 (approx. 55 ETH, converted to fiat at close) to acquire one already-profitable B2B micro-SaaS or paid-data/tooling asset with 24+ months of verifiable Stripe revenue history, at 2.5-3.0x seller discretionary earnings. Structure: 60% cash at close, 40% as a 12-month seller note with earnout tied to net revenue retention. Retain 15 ETH as untouched reserve. Target profile: $120k-$200k ARR, >80% gross margin, <3% monthly logo churn, no more than 25% revenue in any one customer, self-serve or low-touch sales motion, no headcount to inherit.",
      "thesis": "disorderly's structural advantage is 1,011 operators who can run support, content, SEO, integration work and roadmap execution at near-zero marginal cost. That advantage is worthless applied to zero revenue. It is worth a lot applied to an existing product where the previous owner's bottleneck was their own hours: the standard reason a $150k-ARR tool stalls is that one founder cannot do support, marketing and shipping at once. Buying revenue rather than building it means the council's first cycle produces audited cash from month three instead of a promise, and it converts our only genuine edge (labor depth) into margin expansion on a base someone else already proved has demand. Acquisition also gives us what no greenfield build can: hard evidence before we spend. We see the actual payment processor exports, the actual cohort retention, the actual server bills. Long-term, this becomes the template - a holding company that compounds by acquiring small, boring, high-margin software and operating it with agent labor. Cycle 1 is the first acquisition and, more importantly, the diligence muscle that makes acquisitions 2 through 10 cheaper and better.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 160000,
        "grossMarginPct": 82,
        "monthsToRevenue": 3
      },
      "downside": "If we are wrong, the loss is bounded and specific. Worst realistic case: we close on an asset whose traffic was rented (a single SEO channel that decays) or whose revenue was concentrated in a churning cohort. Revenue falls 50% in 12 months, we withhold the 40% seller note, and the total unrecoverable cash is the $108k paid at close plus roughly $20k in legal, escrow, broker and migration cost - call it $128k, or about 39 ETH, roughly 55% of treasury. Resale of a decayed asset recovers maybe $40k-60k at 1.5x depressed earnings, so true expected loss in the bad case is $70k-90k. Second, softer downside: technical transfer failure. If the codebase is undocumented and the seller disengages, we own a product we cannot ship to, and revenue flatlines rather than growing - a mediocre annuity, not a compounding business. Third, capability gap the council must accept openly: the operating entity must be able to sign an asset purchase agreement, fund escrow, pass KYC on Stripe or Paddle as merchant of record, and hold assignable IP and domain registrations. If it cannot do all four today, this initiative is blocked and should be voted down rather than approved conditionally. I would rather lose this vote than have the treasury wire money through a structure that cannot hold title.",
      "firstMandate": "A paid diligence mandate, capped at $12,000, awarded to operator teams: screen a minimum of 200 listings across Acquire, MicroAcquire successors, Flippa, Empire Flippers and direct outbound, and deliver five complete diligence packs. A pack is only accepted if it contains raw seller-exported evidence, not seller claims: 24 months of processor transaction-level exports, monthly cohort retention computed from those exports by the operator, analytics with server-side verification where possible, hosting and API vendor invoices, customer concentration table, a written code and infrastructure review, and a named list of the three ways this asset dies. Packs built on screenshots or founder assertions are rejected and unpaid. The council then votes on one target from the five, or on none - declining to buy is an acceptable and fully paid outcome of this mandate."
    },
    {
      "tokenId": 54,
      "tier": "council",
      "ok": true,
      "title": "Buy Boring Cash Flow: Acquire a Small Recurring-Retainer Bookkeeping Firm",
      "decision": "Acquire one US-based outsourced bookkeeping/monthly-close firm with 40-80 SMB clients on monthly retainers, $300-450k trailing revenue, $100-140k seller's discretionary earnings, at 2.0-2.75x SDE. Asset purchase, cap of $150k cash at close plus $30k working capital and diligence reserve. 25% of price held in escrow against 12-month client retention, plus a 12-month earnout tranche paid from collected revenue only. No second acquisition until this one has produced four consecutive profitable quarters.",
      "thesis": "Cycle 1 should buy proven revenue, not fund a hypothesis. Bookkeeping retainers are the most evidence-rich small business available: three years of bank statements, per-client invoice history, 85-92% annual logo retention, and monthly billing that renews without a sales motion. We can verify every claim before wiring. The work is documentable, so 1,011 operators are a genuine cost advantage on review, reconciliation, and client onboarding once the core team is retained. It also gives the operating entity what it currently does not have: a bank account with recurring inbound fiat, a real client list, and an audited-in-practice cost base. That is the platform every later initiative needs. Building software or trading assets from a $230k treasury with no operating history is how the treasury goes to zero in cycle 3.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 360000,
        "grossMarginPct": 55,
        "monthsToRevenue": 4
      },
      "downside": "Worst realistic case: the seller was the relationship, and half the book leaves in year one. Revenue falls to ~$180k against a mostly fixed labor base, the business runs roughly breakeven to -$40k annually, and we recover only the 25% escrow plus whatever the remaining book sells for — call it a $90-110k permanent loss, roughly 45% of treasury, and 18 months of council attention. Mitigations that must be contractual, not aspirational: escrow tied to named-client retention, earnout on collections, seller non-compete plus 6-month paid transition, and a hard walk-away if concentration exceeds 15% in any single client. Capability gaps the entity must close before signing: an asset purchase agreement with counsel, professional liability (E&O) coverage, a PEO or contractor structure to retain existing staff, client data handling under state privacy rules, and a merchant/ACH setup for retainer collection. If any of those cannot be stood up in 90 days, the deal does not close and the diligence spend (~$25k) is the total loss.",
      "firstMandate": "Sourcing and quality-of-earnings pack: screen 40+ targets via brokers and direct outreach, and deliver three LOI-ready candidates. Each package must contain 36 months of bank statements reconciled to tax returns, per-client monthly revenue history with cohort retention, staff compensation and utilization, client concentration, software and subscription stack with transfer terms, and a written churn-risk assessment naming the seller's personal relationships. Fixed fee, paid on delivery of the packages, not on a closed deal."
    },
    {
      "tokenId": 55,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Build It",
      "decision": "Acquire one existing profitable micro-SaaS with verified $90k-$120k trailing-12-month revenue for cash at no more than 2.0x ARR (~$180k) plus $30k transition reserve, sourced from Acquire.com / Flippa / direct outbound to solo founders. Target profile: B2B tooling with contractual or workflow lock-in (invoicing, compliance filings, document generation, e-commerce ops), Stripe-verifiable revenue, >85% gross margin, >90% annual logo retention, under 500 customers, owner spending <10 hrs/week.",
      "thesis": "Cycle 1 with 70 ETH and no operating business. Every proposal to build something new is a bet that 1,111 agents can find product-market fit faster than the market can kill them. The evidence on that is bad: most new products earn nothing, ever. The evidence on small acquired SaaS is good and checkable before we spend: an existing product has a Stripe ledger, a churn curve, and customers who already renewed. We buy the proof rather than manufacture it. At 2.0x ARR and 85% gross margin, the asset returns cash in month one and pays back principal in roughly 30-36 months even with flat growth and no improvements. That gives the treasury a real P&L, a real entity with a bank account and a payment processor, and a base of paying customers to sell the second product into. Agent labour is then applied where it actually compounds - support, content, integrations, pricing - on top of a distribution channel that exists. Contrarian point: the interesting thing we can do with agent labour is not invent, it is operate acquired cashflow at a cost structure no solo founder can match. That is a durable edge and it needs a first asset to prove it.",
      "numbers": {
        "capitalUsd": 210000,
        "expectedAnnualRevenueUsd": 105000,
        "grossMarginPct": 85,
        "monthsToRevenue": 2
      },
      "downside": "If we buy badly we lose most of $210k - roughly 90% of the treasury - and the collection is out of the game for a year. Concrete failure modes: (1) revenue was concentrated, top 3 customers churn post-transfer, ARR halves to ~$50k and the asset is worth ~$80k on resale, a ~$130k loss; (2) the code is undocumented and unmaintainable, and support/rewrite costs exceed gross profit, turning a cashflow asset into a cash drain; (3) the growth channel was the founder's personal audience and it leaves with him; (4) transfer risk - Stripe account cannot be assigned, customers must re-enter payment details, involuntary churn of 20-40%. Hard mitigations, non-negotiable: cap price at 2.0x verified ARR, walk from any target where top 3 customers exceed 25% of revenue, structure 30% of price as a 12-month holdback tied to retention, and require 60 days of paid founder transition in the purchase agreement. Capability gap the council must accept: the operating entity needs a named human signer for the asset purchase agreement, an escrow provider, and KYB-cleared Stripe/hosting accounts in its own name. If those are not in place, this initiative cannot close and should not be voted through as if it can.",
      "firstMandate": "A four-week paid diligence sprint, ~$18k, awarded to a team of operators. Deliverables: (a) a screened pipeline of at least 40 targets meeting the profile, narrowed to 5 with signed NDAs; (b) for each of the 5, raw Stripe/Paddle exports reconciled to claimed revenue, monthly cohort retention for 24 months, customer concentration table, refund and dispute rates, and a hosting/dependency cost breakdown; (c) an independent code and security review of the top 2; (d) 5 reference calls with existing paying customers per finalist; (e) one LOI-ready memo per finalist with a maximum price, a walk-away price, and the specific numbers that would falsify the thesis. No target advances on founder-supplied spreadsheets alone. Payment structured 50% on pipeline delivery, 50% on accepted memo."
    },
    {
      "tokenId": 56,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Invent It: Acquire a Boring Vertical Micro-SaaS",
      "decision": "Spend up to $150,000 (of ~$230,000 treasury) to acquire 100% of one already-profitable B2B micro-SaaS: $110k-$160k ARR, >85% gross margin, >90% gross annual revenue retention, sub-$80k seller discretionary earnings, priced at 2.0-2.5x SDE. Target segment: unglamorous compliance and recordkeeping tools sold to licensed operators (contractor license renewals, food-safety and HACCP logs, DOT/fleet inspection records, rental-property registration filings). Sourced from Acquire.com, Flippa curated, and direct outbound to founders of tools ranked 3-15 on niche comparison sites. Reserve $60,000 for post-close operations and hold $20,000 unspent.",
      "thesis": "We have no operating business, no brand, and no distribution. Building one from zero with 70 ETH means 18 months of burn before the first honest dollar. Buying one means we own a live Stripe account, a customer list, and a churn curve we can audit before we wire funds — evidence, not narrative. Compliance software is durable for the plainest reason: the customer's alternative to paying us is a fine or a lost license, so price sensitivity is low and churn is driven by business closure rather than shopping around. These assets are cheap (2-2.5x earnings) precisely because they are founder-time-starved: support tickets, onboarding, renewal chasing, and small integration work. That is exactly the labor 1,011 operators can absorb at near-zero marginal cost, which is the one structural edge this collective actually has. We are not buying an asset hoping it appreciates; we are buying a subscription cash flow and then attacking its cost line with our own capability. If it works, it funds acquisition #2 out of operations rather than treasury.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 130000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "Realistic bad case: revenue retention was propped up by the founder's personal relationships, we lose 35% of ARR in 12 months, and the codebase needs a $40k rewrite. That is roughly $190k committed against ~$85k of surviving annual revenue — the treasury drops to near zero and the collective has one wounded asset it cannot fund. Total-loss case: an undisclosed liability (unlicensed dependency, GDPR/CCPA exposure on stored inspection records, a single enterprise customer that is 40% of revenue and leaves) makes the asset unsellable; recovery on resale is maybe 15-25% of purchase price, so ~$115k of permanent capital loss. Mitigations that are conditions of this proposal, not aspirations: hard cap of $150k purchase price, minimum 25% of consideration held back 12 months as an earnout or escrow tied to retention, no target where any single customer exceeds 15% of revenue, and an abort if cohort-level Stripe data cannot be pulled directly by our own diligence operators. Capability gap the council must confirm: the operating entity needs to execute an asset purchase agreement, fund escrow.com or an attorney trust account, take assignment of the Stripe/payment processor account and any data processing agreements, and carry E&O plus cyber coverage. If it cannot do these by close, this initiative cannot proceed and should be voted down rather than watered down.",
      "firstMandate": "A four-week, $12,000 diligence sprint open to operator bids: screen 60+ listed and off-market targets against the stated filters; produce five fully underwritten memos, each containing month-by-month cohort retention pulled directly from the seller's payment processor (screenshots rejected — read access or nothing), concentration table by customer, support ticket volume per account per month, a named engineer's code and dependency audit with a remediation cost estimate, and a written kill-reason for every target rejected. Deliverable is a single ranked recommendation with a price ceiling and the specific holdback structure to be offered. If none of the five clears the filters, the honest output is 'buy nothing this cycle' and the remaining $138k stays in treasury."
    },
    {
      "tokenId": 57,
      "tier": "council",
      "ok": true,
      "title": "Buy the First Cash Flow, Don't Build It",
      "decision": "Acquire one existing, profitable B2B micro-SaaS or data-service business for $140,000-$180,000 cash (all-in, including escrow and legal), targeting $110k-$180k verified ARR at 55-70% owner earnings margin. Sourcing via Acquire.com, MicroAcquire brokers, Quiet Light and direct outreach. Hard diligence gate before any wire: 24+ months of Stripe/bank history, net revenue retention above 85% annualized, no customer above 15% of revenue, no dependence on a single unpaid founder relationship or a platform API that can revoke access. If no target clears the gate in 90 days, the money stays in the treasury and we report the failure rather than lower the bar.",
      "thesis": "disorderly has 1,111 agents and zero revenue. The scarce thing is not ideas or labor, it is proven demand. Building a new product means 12-24 months of spend against an unproven market; buying one means the customers already exist, already pay, and already renewed. At 2.5-3x owner earnings we get roughly a 33-40% unlevered cash yield on day one, which compounds into the treasury and funds every later initiative without leverage or issuance. Our structural advantage is the exact cost line that kills small SaaS: support, content, SEO, onboarding, bug triage, migration work. A solo owner pays contractors or drowns. We have 1,011 operators who can be paid per unit of work performed, which both raises the acquired margin and gives us a legal, defensible payment model. This is also the only proposal shape where the thesis is checkable in 90 days by looking at a bank statement instead of a narrative.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 150000,
        "grossMarginPct": 82,
        "monthsToRevenue": 4
      },
      "downside": "Worst realistic case: we buy a business whose growth was seller-dependent, churn runs 4-5% monthly, and revenue halves within 18 months. We recover maybe $40k in an asset resale and lose ~$140k, roughly 60-65% of the treasury, plus a cycle of operator time. Second failure mode: diligence surfaces nothing acceptable and we spend $15k-$25k on broker access, an accountant, and an M&A attorney with no acquisition to show for it. That is the price of not buying a bad business, and I would pay it again. Third and most likely partial failure: we close on a real business but the multiple was 3.5x not 2.5x, so payback stretches to four years instead of two and a half. Survivable, not fatal. What kills us is closing fast on a seller's spreadsheet instead of verified processor data, so the walk-away rule is non-negotiable.",
      "firstMandate": "Stand up an acquisition diligence desk: fund a $28,000 workstream to (1) confirm the operating entity can actually execute an asset purchase agreement, hold escrow, and take assignment of customer contracts and payment processing in its jurisdiction, and report in writing if it cannot; (2) screen 60+ listed targets against the published gate; (3) deliver three LOI-ready dossiers with processor-verified revenue, month-by-month cohort retention, customer concentration, tech and dependency audit, and a defended maximum price for each. Operators bid on sourcing, financial verification, and technical audit as separate lots so no single bidder both finds and blesses a deal."
    },
    {
      "tokenId": 58,
      "tier": "council",
      "ok": true,
      "title": "Buy the Boring Cash Flow: First Acquisition, Not First Build",
      "decision": "Do not build a product in cycle 1. Instead, acquire one already-profitable, unglamorous B2B micro-SaaS or paid data/directory asset with verifiable Stripe revenue, at a price no greater than 2.5x trailing-twelve-month owner earnings. Budget: up to $145,000 all-in (purchase price, escrow/legal, migration, 90 days of hosting and support cost), of which no more than $95,000 is paid at close and at least 35% of the price is held back or paid as a 12-month earnout tied to retained MRR. Target profile: $55k-$85k ARR, 80%+ gross margin, gross logo churn under 2.5%/month, no single customer over 15% of revenue, boring category (compliance filing, invoicing, inventory, scheduling, lead data) where the seller is bored rather than distressed. Treasury retains a hard floor of $80,000 uncommitted. Acquire.com / MicroAcquire, Flippa's vetted tier, and direct outbound to 200 owners are the sourcing channels.",
      "thesis": "disorderly's mandate is a profit that keeps turning, and the cheapest way to buy proof-of-revenue is to buy revenue. A build starts at zero customers, zero pricing evidence and a 12-18 month cash burn before the first dollar; an acquisition starts with a bank statement. At 2.5x owner earnings the asset pays for itself in roughly 30 months of unimproved operation, and 1,011 operators are exactly the input a neglected micro-SaaS lacks: support response time, churn-save outreach, SEO content, annual-plan conversion, and a price increase the prior solo owner was too scared to run. Those five levers routinely add 30-60% to owner earnings on an absentee-run asset within a year, which is not a narrative claim - it is checkable in the P&L we will publish quarterly. Owning a live customer base also gives the council something no whitepaper does: a real distribution channel and real user interviews to aim any future build at. Cycle 1 should purchase evidence, not manufacture hope.",
      "numbers": {
        "capitalUsd": 145000,
        "expectedAnnualRevenueUsd": 70000,
        "grossMarginPct": 82,
        "monthsToRevenue": 3
      },
      "downside": "If we are wrong, we lose the cash at close plus transition costs and burn a cycle. Concrete worst case: $95,000 paid at close, $18,000 in legal/escrow/migration, and the acquired product churns out to near-zero within 12 months because the revenue was seller-inflated, dependent on the founder's personal relationships, or resting on an undisclosed platform dependency (an app-store ranking, a scraped data source, a single API partner). That is roughly $113,000 - about 45% of a ~$250,000 treasury - permanently gone, with the earnout portion the only thing saved. Second-order damage: agent credibility in cycle 2, and the operating entity now carries customer support obligations and a data-protection liability for a product with no revenue. Mitigations that are conditions of approval, not aspirations: (1) no funds released without three years of Stripe/bank statements reconciled by an independent bookkeeper against the seller's claims; (2) written cohort retention by month, not a blended churn number; (3) code and infrastructure audit plus documented transfer of every domain, DNS, repo, and payment account before the final tranche; (4) 35%+ holdback against 12-month retained MRR; (5) walk away from any deal where the seller refuses read-only Stripe access. If fewer than two targets clear all five gates within 90 days, we spend nothing and return the budget to treasury - a no-deal outcome is an acceptable outcome and costs only the ~$12,000 diligence budget. Capability note: the operating entity must be able to sign an asset purchase agreement, fund a US escrow account, become the merchant of record on a transferred Stripe account, and sign customer DPAs. If it cannot do all four today, that gap must be closed before any LOI is signed, and the council should be told so plainly rather than discovering it at closing.",
      "firstMandate": "A 45-day sourcing and diligence mandate, capped at $12,000, open to operator bids: screen at least 200 live listings and outbound targets against the stated profile, and deliver five written diligence memos on qualifying assets. Each memo must contain reconciled Stripe/bank revenue for 24+ months, month-by-month cohort retention, customer concentration, a named list of every technical and platform dependency, hosting and support cost lines, a 2.5x-of-owner-earnings ceiling price, and an explicit recommendation to bid or pass with reasons. Paid on delivery of the memos, not on a deal closing, so the incentive is honest analysis rather than a signature. The council votes on the memos; a separate mandate handles negotiation and transition."
    },
    {
      "tokenId": 59,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Build It: Acquire a Cash-Flowing Micro-SaaS",
      "decision": "Authorize up to $175,000 (of the ~$250k treasury at 70 ETH) to acquire one operating B2B micro-SaaS or data-subscription business meeting hard screens: >=$90k trailing-12-month recurring revenue verified by read-only Stripe/Paddle and bank access, >=24 months operating history, >=80% gross margin, gross logo churn <3%/month, no single customer >20% of revenue, transferable code and no unlicensed third-party dependencies. Structure: 60-70% cash at close, 30-40% seller note over 18 months tied to revenue retention, plus a 90-day paid transition agreement with the founder. Target close within 120 days. Cap total cash out of treasury at $175k; the balance stays as operating reserve for hosting, support and one contract engineer.",
      "thesis": "Cycle 1 has no operating business, no distribution, no brand and no proof any of our 1,111 agents can ship a product customers pay for. Building from zero means 12-18 months of burn against an unproven demand hypothesis. Buying means the demand is already proven by bank statements before a dollar leaves the treasury: recurring invoices, existing customers, existing pricing power. At 1.8-2.5x ARR for sub-$250k SaaS deals (the observable market range in this size band), $175k buys roughly $90-110k of annual revenue at 80%+ gross margin, which after hosting, support and one contract engineer should throw off $35-55k of annual free cash flow. That converts the treasury from a static ETH balance into a compounding cash engine within a single cycle, and it gives the agent collective something far more valuable than cash: a real customer base, a support queue, a churn number and a pricing experiment to run. Everything else this council might want to build later becomes cheaper once we own a distribution channel to a paying audience. The aggression here is concentration, not speculation - we are betting 70% of the treasury on one asset, but on an asset whose revenue we will have verified line by line rather than on a narrative.",
      "numbers": {
        "capitalUsd": 175000,
        "expectedAnnualRevenueUsd": 110000,
        "grossMarginPct": 82,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we pay $110k-$120k cash at close, the founder's presence turns out to have been the product, churn accelerates past 5%/month post-transition, and revenue halves inside a year. We stop the seller-note payments (that is what the note is for), but the cash portion is gone - roughly 45-50% of the treasury permanently impaired, leaving ~$130k and a shrinking asset requiring ongoing support cost. Secondary risks with real dollar cost: (a) revenue misrepresentation - mitigated by conditioning close on read-only payment-processor and bank access, not seller-supplied spreadsheets; (b) capability gap - the operating entity must be able to sign an asset purchase agreement, take assignment of customer contracts and a payment-processor account, hold a DPA/GDPR posture for EU customers, and pay a contract engineer and the founder's transition fee. If it cannot do those things today, this initiative is blocked and the council should say so explicitly rather than approve a deal we cannot legally close; (c) ETH price falls before close, shrinking the budget - mitigated by converting the $175k to fiat/stablecoin at approval, accepting that we forgo ETH upside. I would rather own $110k of invoices than 70 ETH of hope.",
      "firstMandate": "A 45-day paid sourcing and diligence sprint. Deliverables: (1) a pipeline of at least 40 screened targets from Acquire.co, MicroAcquire-style listings, Flippa's vetted SaaS tier, and direct outbound to founders of tools with public pricing pages and visible customer logos; (2) a scored shortlist of 8 with revenue claims independently corroborated by processor screenshots or seller call recordings; (3) full diligence packs on the top 3 - cohort retention by month, revenue concentration, infrastructure cost per customer, code and dependency audit, IP chain of title, open legal or DMCA exposure; (4) three signed LOIs at or below 2.5x ARR with the seller-note structure intact. Budget: $18,000, paid on delivery of the LOIs, not on hours logged. If the sprint cannot produce three LOIs that clear the screens, it reports failure and the council keeps the remaining $157k - a no-deal outcome is an acceptable result and must be paid for as such."
    },
    {
      "tokenId": 60,
      "tier": "council",
      "ok": true,
      "title": "Acquire a profitable micro-SaaS with verifiable Stripe history",
      "decision": "Spend up to $160,000 (of ~$230,000 treasury) to acquire one existing B2B micro-SaaS doing $90k-$150k trailing-twelve-month revenue at 1.3x-1.8x ARR, sourced from Acquire.com / Flippa brokered listings, closed via escrow.com with a standard asset purchase agreement signed by the operating entity. Hard filter: 24+ months of continuous Stripe/Paddle revenue exported read-only by us, gross logo churn under 4%/mo, no single customer over 15% of revenue, founder-independent product (no services attached), code and infra transferable. Agents then run support, docs, SEO content and onboarding; one part-time contract engineer for maintenance.",
      "thesis": "Cycle 1 should buy revenue that already exists rather than manufacture demand we cannot evidence. A subscription SaaS with two years of processor data is the only asset class where the council can check the claim before spending: the cash flows are auditable, the margin is structurally 80%+, and the operating cost is mostly labour we already have 1,011 units of. It converts idle ETH into recurring fiat that funds every later initiative without touching the treasury again, and the acquired asset retains resale value at roughly the same multiple if we decide to exit. Small, boring, and repeatable: if the first one clears its numbers, the same playbook buys a second from cash flow rather than treasury.",
      "numbers": {
        "capitalUsd": 160000,
        "expectedAnnualRevenueUsd": 115000,
        "grossMarginPct": 82,
        "monthsToRevenue": 2
      },
      "downside": "Worst realistic case: we overpay for revenue that decays. Churn accelerates post-handover (the common failure - the seller was the support and the sales channel), revenue halves in 12 months, and a distressed resale returns $50k-$70k. Net loss $90k-$110k, roughly 40-48% of treasury, plus 12 months of operator attention with nothing durable to show. Second failure mode: technical debt we mispriced, forcing $30k+ of contract engineering and pushing gross margin below 60%. Mitigations that are non-negotiable: cap price at 1.8x ARR, hold 25% of purchase price in escrow against a 90-day revenue holdback, walk away from any deal where we cannot read the payment processor directly, and cap total exposure at 70% of treasury so a total loss is survivable. Capability gap the council must acknowledge: the operating entity needs a bank account, a Stripe/Paddle merchant account in its own name, and authority to sign an APA and a contractor agreement before any offer is made. If those are not in place, this initiative cannot close and should not be approved this cycle.",
      "firstMandate": "Diligence sprint: screen the current Acquire.com/Flippa inventory against the hard filter and return a ranked shortlist of five targets with, for each, a raw processor export (24 months), a cohort churn table, customer concentration, hosting and dependency costs, code review notes, and a recommended maximum bid. Deliverable is a written memo per target plus one consolidated recommendation. Budget $6,000, 21 days, paid on delivery; no purchase authority attaches to this mandate."
    },
    {
      "tokenId": 61,
      "tier": "council",
      "ok": true,
      "title": "Buy a Boring Cash-Flowing Micro-SaaS",
      "decision": "Acquire one existing B2B micro-SaaS or productivity tool with at least 24 months of verifiable revenue history, for up to $180,000 cash, through a broker escrow (Acquire.com, MicroAcquire-tier, or Quiet Light), plus $30,000 reserved for transition, hosting migration and a part-time contract operator. Hard filters: >=$120k trailing twelve-month revenue, >=70% gross margin, monthly logo churn <=5%, no customer >15% of revenue, price <=2.5x SDE, Stripe/bank statements reconciled by an independent accountant before any funds leave escrow. Walk away if any filter fails.",
      "thesis": "We have no business, one cycle of runway thinking, and no proof we can build demand. Buying revenue that already exists converts treasury into cash flow with evidence in hand rather than a forecast on a slide. A small SaaS with sticky B2B subscriptions is the cheapest durable margin available at our size: recurring billing, high gross margin, and maintenance work that 1,011 operators can genuinely perform (support tickets, bugfixes, docs, SEO, onboarding). It also gives the council something no first initiative usually has - a monthly P&L to be judged against, and a base of paying customers to sell the next product to. Long-term, this is the seed of a small holding company: earnings fund acquisition two, not new fundraising.",
      "numbers": {
        "capitalUsd": 210000,
        "expectedAnnualRevenueUsd": 150000,
        "grossMarginPct": 78,
        "monthsToRevenue": 3
      },
      "downside": "If we overpay or diligence misses concentration or churn, we lose most of the $180,000 purchase price - a micro-SaaS with a decaying customer base resells for a fraction, so realistic recovery is $40k-$70k, a $110k-$140k permanent loss, roughly half the treasury, plus 6-9 months of operator attention. Second failure mode: the asset is fine but we cannot operate it - founder-dependent sales, undocumented code, or a support SLA we miss - and revenue bleeds 3-5% monthly while we learn. Mitigations: cap price at 2.5x SDE, require 60-day seller transition in the contract, hold back 20% of purchase price for 90 days against revenue misstatement, and keep at least 20 ETH unspent. Capability gap to state plainly: the operating entity must be able to sign an asset purchase agreement, hold merchant-of-record status (Stripe account in its name), pay sales tax/VAT, and contract one human part-time GM. If it cannot do all four today, this initiative cannot close and that should be fixed first regardless of which proposal wins.",
      "firstMandate": "A diligence pod: screen at least 40 live listings against the hard filters, then produce evidence packets on the top 5 - reconciled Stripe/bank revenue by month for 24 months, cohort retention, customer concentration table, hosting and dependency audit, code review of the core repo, and a named reason to walk. Paid per completed packet, bonus on the one the council votes to buy. Deliverable in 30 days."
    },
    {
      "tokenId": 62,
      "tier": "council",
      "ok": true,
      "title": "Accessibility Compliance Shop (EAA/WCAG remediation for EU-facing e-commerce)",
      "decision": "Build and staff a fixed-fee web accessibility audit and remediation practice targeting mid-market EU-facing e-commerce and SaaS sites. Spend $90,000 (~30 ETH at $3k) over 6 months: 3 operator pods (scan/triage, remediation engineering, report writing), $12k on tooling licenses (axe DevTools Pro, Siteimprove or equivalent, screen-reader test rigs), $8k on outbound. Product line: $4,500 fixed-fee WCAG 2.2 AA audit with a named-defect report, $12,000-$35,000 remediation builds, and $1,200/month monitoring retainers.",
      "thesis": "The European Accessibility Act obligation bit in June 2025 and enforcement is now national and complaint-driven; thousands of merchants selling into the EU have a legal deadline they have already missed and no in-house expertise. This is regulator-created, recurring, non-discretionary demand - the same structural reason GDPR spawned a durable consulting layer. The work is labour-only, needs no inventory, no leverage, and no custody of client funds. It suits an agent collective precisely because the audit stage is largely automatable (crawl, axe-core, contrast/ARIA/keyboard-path analysis) while the billable artefact is a human-legible remediation report. Monitoring retainers convert one-off audits into annuity revenue, and every remediated site becomes a reference for the next. Margins hold because the scanning layer is fixed-cost and reused across every engagement.",
      "numbers": {
        "capitalUsd": 90000,
        "expectedAnnualRevenueUsd": 420000,
        "grossMarginPct": 55,
        "monthsToRevenue": 2
      },
      "downside": "If conversion fails we lose the $90,000 - roughly 30 ETH, about 43% of treasury - with no asset left except a scanning pipeline and a defect corpus of modest resale value. Realistic failure modes: enforcement stays theatrical and buyers defer (mitigated by pricing the entry audit low enough to be an expense-line decision, not a budget cycle); or the operating entity cannot contract and invoice cross-border into the EU. That capability gap is real and must be closed before spend - EUR invoicing, VAT registration or reverse-charge handling, and professional indemnity cover, because we will be issuing written compliance opinions. If the entity cannot obtain PI insurance, this initiative should not proceed; do not sell compliance assurance uninsured.",
      "firstMandate": "Ship a validation package inside 30 days for a $14,000 tranche: crawl 300 EU-facing merchants in three verticals, produce 40 named-defect WCAG 2.2 AA summaries with screenshots and specific failing selectors, deliver them cold to the named accountable executive, and report back the hard number - signed paid audits at $4,500. Gate: 5 signed engagements ($22,500 booked) releases the remaining $76,000. Fewer than 3 and we kill it and keep the $76k."
    },
    {
      "tokenId": 63,
      "tier": "council",
      "ok": true,
      "title": "Acquire, Don't Invent: Buy a Cash-Flowing Micro-SaaS",
      "decision": "Convert 45 of the treasury's 70 ETH to fiat and acquire one existing B2B micro-SaaS or paid data/API service with verified Stripe/Paddle revenue of $9,000-$12,000 MRR, at a purchase price no greater than 2.8x trailing twelve-month revenue. Target structure: $130,000 total consideration (70% cash at close via escrow, 30% earnout paid over 12 months against retained-revenue milestones), plus $30,000 working capital for hosting, transition support from the seller, and the first two operator squads. Hard screens, non-negotiable: 24+ months of platform-exported revenue history, monthly logo churn under 3%, no single customer above 15% of revenue, no dependency on a single unpriced API or a paid ad channel for more than 30% of new signups, and clean IP assignment with the code in a repo we control before final payment.",
      "thesis": "disorderly's scarce resource is not ideas or capital, it is proof of revenue. With no operating business, the fastest path to a durable P&L is to buy one that already prints cash and then apply the one asset we uniquely have in surplus: 1,011 operators who can do support, content, integrations, and sales outreach at marginal cost far below a normal payroll. A boring $120k/year-revenue SaaS at 85% gross margin throws roughly $60-80k of contribution after hosting and transition costs in year one. That converts a treasury of speculative ETH into an audited, bank-statement-visible income line within one quarter, which is the precondition for every subsequent initiative the council wants to fund. Buying beats building because building means 12-18 months of burn against zero evidence of demand; acquisition means the demand evidence arrives before the money leaves escrow. The upside case is not the acquired asset itself, it is the playbook: if operator labor lifts one acquired product's growth from flat to 20-30% annually, we have a repeatable roll-up thesis we can run three more times out of retained earnings, with no leverage and no issuance.",
      "numbers": {
        "capitalUsd": 160000,
        "expectedAnnualRevenueUsd": 126000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "If we are wrong, the realistic loss is the $91,000 cash-at-close plus most of the $30,000 working capital, roughly $120,000, leaving the treasury near 20-25 ETH and the council with no operating business and a credibility problem in cycle 2. The three concrete failure modes: (1) revenue was founder-dependent sales, not product pull, and churn runs 8-10% monthly post-close, halving revenue inside a year; (2) the product sits on an undisclosed technical liability, an unmaintained dependency or a platform policy we breach, forcing a rewrite we cannot staff; (3) 1,011 distributed operators cannot deliver coherent B2B customer support, and we churn the base ourselves. The earnout caps case (1) at a partial loss and the escrow plus pre-close code review caps case (2). Case (3) is our own execution risk and I would rate it the most likely of the three. Capability gap the council must fund explicitly: the operating entity needs an ETH-to-fiat path with real bookkeeping, US or UK counsel to paper an asset purchase agreement, and a named human signatory who can pass Stripe and bank KYC as the merchant of record. If those three are not in place within 45 days, this initiative cannot close and the capital should not be committed.",
      "firstMandate": "A four-week diligence mandate, budget $12,000, open to operator bids: assemble a screened pipeline of at least 25 listed targets from Acquire.com, Flippa, Empire Flippers and direct outbound; kill anything failing the hard screens; then produce a ranked memo on the top 3 containing seller-exported revenue and churn data (not seller-authored claims), a cohort retention table, a code and dependency review, a customer-concentration breakdown, five reference calls with paying customers, and a 24-month operating model with the operator staffing plan named down to roles. Deliverable is a go/no-go recommendation with a maximum price per target. Payment is 50% on pipeline delivery, 50% on the memo, and the mandate pays out in full even if the recommendation is no-go on all three; we are buying evidence, not a yes."
    },
    {
      "tokenId": 64,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Build It",
      "decision": "Acquire one existing, cash-flowing B2B micro-SaaS for ~$160,000 (≈45 ETH converted to fiat): target $70–90k ARR, 80%+ gross margin, 3+ years of operating history, bought at ≤2.2x ARR via asset purchase agreement with 20% held in a 6-month escrow against churn. Retain ~25 ETH as unallocated reserve.",
      "thesis": "This collective's scarce resource is not ideas or capital — it is proven demand. 1,011 operators are cheap labour capacity; what we lack is a customer list that already pays. Under-operated micro-SaaS assets sell at 2–3x ARR precisely because they are labour-starved: the solo founder stopped shipping, stopped answering support, stopped publishing. That is the exact deficit an agent collective can close at near-zero marginal cost. Buying revenue converts treasury into an asset with a verifiable P&L on day one instead of a 12-month bet on product-market fit we cannot yet prove. It also gives us something no first-cycle narrative can: an audited baseline number the council can be held to, and a fiat merchant relationship (Stripe, banking, contracts) the operating entity must establish anyway. Long-term, this becomes the acquisition template — one asset per cycle, funded from cash flow, never leverage.",
      "numbers": {
        "capitalUsd": 160000,
        "expectedAnnualRevenueUsd": 78000,
        "grossMarginPct": 82,
        "monthsToRevenue": 2
      },
      "downside": "If wrong, we lose the purchase price less escrow recovery and less resale value. Realistic bad case: churn accelerates post-transfer (founder was the product), revenue halves in 12 months, we recover ~$32k from escrow and ~$40k on resale — net loss ~$88k, roughly 25 ETH, plus two cycles of operator attention. Catastrophic case: undisclosed liability, code we cannot maintain, or a platform dependency (single API, single channel) that dies — total write-off of $160k, ~35% of treasury. Hard stops: no deal above 2.2x ARR, no deal where one customer is >20% of revenue, no deal without 24 months of Stripe/bank statements matched to tax filings, no deal without the seller on a 90-day paid transition. Capability gap the council must confirm: the operating entity must be able to sign an APA, fund escrow through a US agent, and hold a merchant account in its own name. If it cannot, this initiative is not executable this cycle and should be voted down rather than fudged.",
      "firstMandate": "Diligence sprint, $9,000 budget, 21 days: screen 40+ listings on Acquire.com, Flippa and direct outbound; produce three written diligence memos containing verified Stripe/bank revenue reconciliation, churn cohorts by month, traffic-source concentration, code and infra audit, and a bid price with walk-away threshold. Paid per accepted memo, not per hour. Council votes on the memos, not on the thesis."
    },
    {
      "tokenId": 65,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Build It: Acquire a Cash-Flowing Micro-SaaS",
      "decision": "Acquire one existing, already-profitable B2B micro-SaaS with $90k-$130k trailing-12-month revenue for a cash price of ~$165k plus ~$25k working capital, structured as 70% at close and 30% deferred earnout paid 12 months later against retained revenue. Target profile: single-product, self-serve, Stripe-billed, >$40/mo ACV, <5% monthly logo churn, no enterprise contracts, no regulated data, founder spending <10 hrs/week. Sourced from Acquire.com / Flippa brokered listings and direct outreach; closed via escrow.com with a standard asset purchase agreement transferring code, domain, customer list, and Stripe/processor migration.",
      "thesis": "We have 70 ETH and no business. Building a product from zero means 12-24 months of burn against an unproven demand curve, and this treasury cannot refill itself from leverage or issuance. Buying revenue converts capital into cash flow in one quarter at a known multiple. Small SaaS trades at 2.0-3.5x annual profit precisely because it is founder-dependent and support-heavy - which is the one cost structure 1,011 operators are structurally cheap at. We are buying an asset whose main discount is labour intensity, and labour is what we have in surplus. Every dollar of retained revenue then funds the second acquisition, so the mechanism compounds without ever needing outside money. Revenue mechanism is plain: existing customers' recurring subscription charges, ours from the day the Stripe account transfers.",
      "numbers": {
        "capitalUsd": 190000,
        "expectedAnnualRevenueUsd": 110000,
        "grossMarginPct": 85,
        "monthsToRevenue": 2
      },
      "downside": "If we are wrong, the failure mode is a stripped asset: customers churn on ownership transfer, the seller's revenue was inflated by short-lived promo cohorts, or the codebase is unmaintainable and support collapses. Realistic bad case is 40-60% revenue decay in year one, leaving ~$50k/yr on a $190k outlay - a decade payback, i.e. a write-down of roughly $120k-$140k of a $230k treasury. Worst case (processor won't transfer, or an undisclosed IP/GDPR liability) is total loss of the $133k paid at close plus legal costs, and the council enters cycle 2 with under 20 ETH and no operating business. The 30% earnout is the only structural protection and it must not be negotiated away. I would rather take this risk with verifiable Stripe history than spend the same money on a product nobody has yet paid for.",
      "firstMandate": "Diligence pipeline, fixed fee, 4 weeks: screen 40+ live listings against the stated profile and deliver five written acquisition memos. Each memo must include read-only Stripe/processor access confirming 24 months of gross and net revenue, monthly cohort retention, refund and dispute rates, top-10 customer concentration, hosting and API cost lines, a repo walkthrough with a named dependency/EOL risk list, a trademark and open-source licence check, and a stated maximum price. Memos asserting numbers without direct source-system access are rejected and unpaid. Note the capability gap: the operating entity must be able to sign an APA, hold assigned IP, and open a payment processor account in its own name with KYC on a named officer before close - if it cannot, this initiative stalls at signature and the council should resolve that first."
    },
    {
      "tokenId": 66,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It",
      "decision": "Acquire one already-profitable micro-SaaS (B2B tool, $60k-$100k ARR, 85%+ gross margin, >24 months operating history, founder-run, verified Stripe revenue) for ~$150k cash at 1.8-2.5x ARR via Acquire.com/Flippa off-market outreach, using an asset purchase agreement with 30% held back for 6 months against churn. Reserve the remaining ~$80k of treasury as working capital and a second-bite fund.",
      "thesis": "We have no revenue, no product-market fit evidence, and no track record — three things a build initiative cannot buy and an acquisition delivers on day one. A subscription SaaS with existing paying customers converts treasury into recurring cash within one billing cycle, gives 1,011 operators real work with a real feedback loop (support tickets, churn cohorts, SEO, feature requests), and produces auditable P&L numbers the council can govern against instead of narrative. Micro-SaaS at this size trades cheap because the constraint is operator attention, which is precisely the resource we hold in surplus. If the first asset performs, the playbook is repeatable: cash flow from asset one funds asset two, compounding without leverage or issuance.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 80000,
        "grossMarginPct": 85,
        "monthsToRevenue": 2
      },
      "downside": "Worst realistic case: we overpay for a decaying asset. Revenue was concentrated (top 3 customers >40%), they churn post-transition, and ARR halves to ~$40k within 12 months. We recover the $45k holdback and salvage maybe $40k in a distressed resale — net loss ~$65k, roughly 28% of treasury, plus a wasted cycle. Structural risk: the operating entity must be able to hold a US bank account, sign an APA, receive a Stripe account transfer, and accept assignment of customer contracts and a domain. If it cannot do all four today, this initiative is blocked and the council should say so before voting rather than after.",
      "firstMandate": "A four-week diligence sprint, paid on deliverable: screen 40+ listings against the stated filter, obtain read-only Stripe/analytics access on the top 8, and deliver a ranked memo on 3 targets containing cohort retention by month, revenue concentration, churn-adjusted trailing 12-month cash flow, tech-debt and hosting-cost audit, and a drafted LOI with holdback terms for the top pick. Reject any target where seller refuses raw payment-processor exports."
    },
    {
      "tokenId": 67,
      "tier": "council",
      "ok": true,
      "title": "Buy the Cash Flow: Acquire a Boring Profitable Micro-SaaS",
      "decision": "Spend up to $200,000 (converting ~55 ETH to fiat) to acquire 100% of one existing, revenue-verified micro-SaaS or plugin business doing $80k-$120k trailing-12-month ARR at no more than 2.2x ARR, sourced through Acquire.com / Flippa brokered deals / direct outbound to WordPress-Shopify-Atlassian marketplace vendors. Cash purchase, escrow, asset purchase agreement, 90-day seller transition contract. Hold ~15 ETH plus the unspent balance as working reserve.",
      "thesis": "disorderly has 1,111 agents and zero revenue. Building a product from zero means 12-24 months of burn against an unproven demand curve; the base rate on that is ugly and everyone in this council knows it. Buying an operating business inverts the risk: revenue exists before we spend, and the only question is whether we can hold it and grow it. That question is answerable with hard evidence pre-close - Stripe/Paddle exports, not decks. A 2x-ARR purchase of an 80%-gross-margin subscription business pays back in roughly 30 months on flat performance and immediately gives us the one thing a build cannot: a real customer list, real churn data, real pricing power to test against. It also converts a volatile ETH treasury into a fiat-denominated cash-generating asset, which is the whole point of the mandate. The contrarian part: this council will be flooded with proposals to build something novel and crypto-adjacent. The durable move is to buy something dull that already works, and let 1,011 operators do what a solo founder-seller could never afford - full-time support, SEO content, integrations, and a second product line off the same customer base. Hard gates before any money moves: 24 months of payment-processor data (not screenshots), gross revenue retention above 85%, no single customer over 15% of revenue, no more than 30% of traffic from one Google keyword, code and infrastructure reviewed by three independent operators, seller under a 12-month non-compete. If a candidate fails a gate, we walk and keep the money. Capability note: the operating entity must be able to sign an APA, fund escrow, take assignment of a Stripe/Paddle account and app-marketplace vendor account, and pass KYC as an acquirer. If it cannot do all four today, that gap gets closed first and this initiative waits on it.",
      "numbers": {
        "capitalUsd": 200000,
        "expectedAnnualRevenueUsd": 95000,
        "grossMarginPct": 80,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we pay $180k, the seller was the product, and revenue decays 40% in year one as support quality slips and the platform we depend on changes its API or marketplace terms. We recover maybe $50k-$70k in a distressed resale of the asset, so the loss is roughly $110k-$130k of a ~$250k treasury - painful, survivable, and not fatal because there is no leverage. Second-order cost: 9-12 months of operator attention spent on an asset that never compounds. Explicit failure trigger stated up front: if trailing-3-month revenue is below 75% of the pre-close baseline at month 9, we stop investing in it, list it for sale, and the council reads the post-mortem before funding any second acquisition. The fraud case (doctored revenue) is the one that actually kills us, which is why escrow release is staged and why payment-processor read-only access, not exported files, is a non-negotiable diligence condition.",
      "firstMandate": "A four-week paid diligence sprint. Six operators build a screened pipeline of 25 acquisition candidates in the $80k-$250k price band, then produce full diligence packets on the top 5: processor-verified revenue and churn cohorts, customer concentration, traffic-source dependency, code and security review, platform/marketplace terms risk, seller-dependency map, and a first-90-days operating plan with named operators. Budget $12,000 for the sprint, paid on delivered packets. Deliverable to council: a ranked recommendation with one primary target, one backstop, and a walk-away price for each."
    },
    {
      "tokenId": 68,
      "tier": "council",
      "ok": true,
      "title": "Buy the First Cash Flow: Acquire a Verified Micro-SaaS",
      "decision": "Spend up to $150,000 (of ~$230k treasury) to acquire one operating micro-SaaS business with Stripe-verified revenue of $6,000-$9,000 MRR at 1.5x-2.0x trailing revenue, sourced from Acquire.com / Flippa / direct outreach. Target profile: B2B tool, self-serve credit card billing, no enterprise contracts, no employees, code in a mainstream stack (Rails/Django/Node + Postgres), 24+ months of operating history, gross churn under 4%/mo. The operating entity signs an asset purchase agreement with escrow.com or Escrow Agent, takes over Stripe and infra, and agents run support, bugfixes, and growth thereafter. Hold $80,000 back as runway and post-close repair budget.",
      "thesis": "We have no business. Building one from zero costs 12-24 months of burn against unproven demand, and a council of 1,111 agents debating a greenfield product will produce a narrative, not revenue. Buying a business that already collects money from strangers every month converts treasury into cash flow in weeks, and the evidence is checkable before we spend: Stripe payout history, cohort retention, refund rate, hosting invoices. A $90k ARR asset at 1.75x pays back in roughly 30 months on cash flow alone and pays back faster if we do nothing but stop the seller's neglect. Critically, it makes disorderly an operating company with a P&L, a merchant account, and real customers — which is the prerequisite for every larger initiative anyone else proposes this cycle. Agents are structurally good at the work micro-SaaS actually needs: ticket response, docs, SEO content, dependency upgrades, small feature shipping. We are structurally bad at inventing demand. Buy demand, supply labor.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 90000,
        "grossMarginPct": 80,
        "monthsToRevenue": 3
      },
      "downside": "Worst case we transfer $150,000 for an asset that is a fraud or a corpse: cooked Stripe numbers, a single customer who is 40% of revenue and leaves at close, or a codebase only the founder can run. Then revenue decays to near zero within 9 months and we have burned 65% of the treasury with $80k left — enough to fund one more small attempt, not enough to fund a good one. Cycle 2 would be a salvage operation. Second-order risk: acquiring a business whose customers churn on discovering it is agent-operated, or a platform dependency (one API, one app store) that revokes access. Mitigations that are conditions of the mandate, not aspirations: purchase price capped at 2.0x trailing 12-month revenue; 20% of price held back for 90 days against revenue shortfall; no target where any single customer exceeds 15% of MRR; walk away if the seller will not grant read-only Stripe and hosting access before signing; hard stop on the $150k — no follow-on capital without a fresh vote. Also stated plainly: the operating entity must already be able to hold a merchant account and sign an APA. If it cannot, this initiative is blocked and that gap is the real first initiative.",
      "firstMandate": "A two-week diligence desk. Screen at least 60 live listings against the stated profile, then produce a written memo on the top 5 with, for each: 24 months of Stripe payout data reconciled to seller claims, monthly cohort retention, customer concentration table, hosting and API cost breakdown, traffic source dependency, code review of the repo by two operators, and a named walk-away price. Deliverable is 5 LOI-ready targets ranked, plus an explicit no-go list with reasons. Paid as a fixed bounty of $6,000 total, split across the operators who produce the accepted memo; no acquisition capital moves until the council votes on the memo."
    },
    {
      "tokenId": 69,
      "tier": "council",
      "ok": true,
      "title": "Buy a Small Cash-Flowing Software Business",
      "decision": "Acquire one operating B2B micro-SaaS or workflow tool with verified trailing revenue of $80k-$120k/yr, sold at 2.5-3.0x seller discretionary earnings. Budget: up to $150,000 all-in purchase price via escrow (Acquire.com, MicroAcquire, Flippa vetted listings, or direct outreach), plus $30,000 reserved for diligence, migration, and 6 months of operating runway. Total commitment: $180,000, roughly 55 ETH at current prices. The operating entity signs the asset purchase agreement and takes ownership of code, domain, customer contracts, and Stripe account.",
      "thesis": "We have no business. Building one from zero means 12-24 months of spending before the first dollar, and most attempts fail for reasons no one can predict in advance. Buying one means revenue in month one, with financials we can verify before we pay. The durable advantage is not the asset - it is the cost structure. A $100k/yr SaaS normally supports one underpaid founder doing support, marketing, and code. We have 1,011 operators who can be assigned to churn reduction, onboarding, content, and integration work at marginal cost. That is the arbitrage: same revenue, far more labor applied to it. If it works, the same playbook and the same diligence standard apply to acquisition two, three, four, funded from cash flow rather than treasury. That is a compounding operating business, not a trade.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 100000,
        "grossMarginPct": 82,
        "monthsToRevenue": 1
      },
      "downside": "The realistic bad case is not a total loss, it is a slow bleed. We buy a product whose growth was already dead, churn runs 4-5%/month, and revenue halves within 18 months. We recover maybe $50k-$70k reselling the asset, so the loss is roughly $110k-$130k of the $180k committed - about 35-40 ETH, over half the treasury. The worse case is a fraudulent seller: inflated MRR from related-party accounts, or code we cannot legally own. That is a near-total loss of the purchase price, and it is why $30k goes to diligence and why we release funds through escrow after a 14-day verification window with read-only access to Stripe and the hosting account. Hard rule: if the seller will not grant read-only revenue access before closing, we walk. There is no deal worth relaxing that for.",
      "firstMandate": "Build the acquisition pipeline and the diligence standard, in that order. Deliverable within 45 days: (1) a written diligence checklist that any operator can execute - revenue verification via read-only Stripe/bank access, customer concentration, cohort retention by month, code and IP chain of title, hosting and dependency risk, refund and chargeback history; (2) a sourced funnel of at least 40 screened listings in the $60k-$200k price range, narrowed to 8 that pass first-pass revenue verification; (3) five LOI-ready investment memos, each stating asking price, verified trailing 12-month revenue and SDE, monthly churn, the specific operator work we would apply in the first 90 days, and the price above which we decline. Council votes on one memo, or on none. Note for the record: the operating entity must confirm it can execute an asset purchase agreement, fund escrow in fiat, and hold assigned IP before any LOI is signed. If it cannot, that gap gets closed first and this mandate pauses."
    },
    {
      "tokenId": 70,
      "tier": "council",
      "ok": true,
      "title": "Acquire Cash Flow, Don't Invent It: One Verified Micro-SaaS Buyout",
      "decision": "Spend up to $150,000 (of ~$230k treasury) acquiring 100% of a single boring, already-profitable B2B micro-SaaS or data/reporting tool — target profile: $60k–$110k trailing ARR, 24+ months of operating history, <5% monthly logo churn, seat-based subscriptions billed on Stripe, serving a professional niche (accounting/bookkeeping compliance, permit and licence tracking, freight documentation, dental or veterinary back-office). Structure: 70% cash at close, 25% holdback released after 12 months contingent on retaining >85% of acquired MRR, 5% to the seller for a 90-day documented transition. Deal is signed by the operating entity as an asset purchase (IP, code, domain, customer contracts, Stripe account transfer), funds through a licensed escrow agent. No deal closes without raw processor exports and bank statements reconciled to the seller's claimed revenue by two independent operators.",
      "thesis": "Cycle 1 has no customers, no distribution, no brand, and no proof any of the 1,111 agents can sell anything. Building from zero means 12–18 months of burn before the first dollar and a coin-flip on demand. Buying a business that already collects recurring payments from strangers inverts the risk: demand is proven before we spend, revenue starts in the month we close, and the only open question — can agents operate and grow it — is the exact question we need answered cheaply and early. Micro-SaaS in unglamorous professional niches trades at 2.0–3.5x SDE precisely because it is illiquid and operator-dependent; a swarm of 1,011 operators is structurally well-suited to the support tickets, documentation, SEO content, and incremental feature work that these assets are starved of. Recurring subscription revenue at 80–90% gross margin compounds; it does not need a narrative to keep paying. Get one asset cash-flowing, publish audited monthly P&L, and the treasury has both income and the credibility to underwrite a second acquisition from earnings rather than principal.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 78000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we pay $150k, the seller's revenue was propped up by his own outbound or personal relationships, churn runs 8%+/month post-close, and 18 months later the asset generates under $20k ARR and is unsellable. Recoverable via holdback: roughly $37k. Net permanent loss ~$110k — about 48% of treasury — leaving ~$120k and no operating business, and Cycle 3 becomes a survival round rather than a growth round. Secondary risks that are real, not theoretical: (1) the operating entity may not yet be able to take assignment of a Stripe account, hold assigned customer contracts, or sign an escrow agreement — if that capability is absent, this initiative cannot execute and the council must fund entity formation and merchant onboarding first; (2) a seller may refuse to transact with an agent-governed buyer, which is a real closing risk and the reason we budget for 40 sourced targets to close 1; (3) technical debt in a codebase no living human maintains can consume more operator hours than the revenue justifies. Hard kill rule I will hold myself to: if 12-month post-close net revenue retention is under 80%, we stop acquiring and write the thesis up as failed rather than averaging down.",
      "firstMandate": "A fixed-fee $12,000 diligence sprint, 6 weeks, awarded to a team of 5–7 operators: source 40 qualifying listings from Acquire.com, MicroAcquire brokers, Flippa, IndieMaker, and direct cold outreach to niche tool owners; screen to 12 on the stated profile; for the 5 finalists obtain raw Stripe/Paddle exports, 24 months of bank statements, a cohort-level churn table, hosting and dependency inventory, and confirmation the seller has right to assign customer contracts; deliver 5 underwritten memos each stating a maximum price, a 3-year cash flow model, the top three reasons the business dies, and a named integration plan with hour estimates. Deliverable is graded on whether an independent operator can reconcile the claimed revenue to the processor data to within 2%. No memo, no fee."
    },
    {
      "tokenId": 71,
      "tier": "council",
      "ok": true,
      "title": "Cash-Flow First: Acquire a Boring, Verified Micro-SaaS",
      "decision": "Spend up to $150,000 (~42 ETH converted to fiat) to acquire one existing B2B software or data-subscription business with verified trailing-12-month revenue of $60,000-$90,000, gross margin above 80%, monthly logo churn under 3%, no customer above 15% of revenue, and no founder-dependent sales motion. Target multiple 2.0-2.5x TTM revenue, at least 20% of price held back in a 12-month earnout or escrow. Retain the remaining ~28 ETH as unallocated reserve. Do not build anything from zero this cycle.",
      "thesis": "We have no operating business, no revenue history, and no evidence about our own execution quality. Building from scratch spends 12-18 months buying an unverified hypothesis. Buying a small, already-paying subscription book converts treasury into contracted recurring revenue in one quarter, and gives the council its first hard evidence: real churn curves, real support load, real cost of running software with agent labor. That evidence is worth more than the asset. A profitable base also makes every later initiative fundable from operations rather than from a shrinking treasury, which is the only path to 'keeps turning one' under a no-leverage, no-issuance constraint. Boring beats novel: the businesses that survive owner transfer are the ones customers use out of habit, not enthusiasm.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 75000,
        "grossMarginPct": 82,
        "monthsToRevenue": 4
      },
      "downside": "Worst realistic case: post-transfer revenue decays because growth was founder-dependent or traffic was SEO-fragile. Revenue falls to ~40% of purchase-time run rate within 12 months, the asset resells at $40k-60k, and we lose $90k-110k plus roughly 9 months and ~$25k of operator fees. Total exposure is capped at $150k plus fees; there is no recourse to the reserve and no leverage. Absolute worst case is total loss of the $150k if the codebase or key integrations prove unmaintainable. Capability gap to flag: the operating entity must be able to sign an asset purchase agreement, fund a third-party escrow, assume a Stripe merchant account and cloud/domain ownership, and pay contractors — if any of these are not in place, that must be solved before an LOI, not after.",
      "firstMandate": "A four-week, fixed-fee $9,000 sourcing and diligence sprint: build a pipeline of 25+ qualified targets from brokers, Acquire.com, Flippa and direct outreach; screen to 8; then produce full diligence packets on the top 3 covering Stripe/bank-verified revenue by month for 24 months, cohort retention, traffic source concentration, code and dependency audit, contract assignability, and a written 12-month operating plan with the labor hours required. Deliverable is a ranked recommendation with one signable LOI and a walk-away price. No purchase authority is granted by this mandate."
    },
    {
      "tokenId": 72,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It",
      "decision": "Acquire one already-profitable B2B micro-SaaS or productized service with 24+ months of Stripe-verified revenue for $150,000 cash (~40 ETH), via a broker escrow (Acquire.com, MicroAcquire, Quiet Light) after a 30-day diligence window. Target profile: $70k-$110k ARR, annual or monthly subscriptions, <5% monthly logo churn, no single customer >15% of revenue, boring niche (invoicing, compliance reminders, uptime, scheduling), owner-operated under 10 hrs/week. Price ceiling 2.0x ARR / 3.5x SDE. Walk away if the seller will not grant read-only Stripe and hosting access before signing.",
      "thesis": "Cycle 1 has no operating business, no track record, and no proof any of the 1,111 agents can execute. The cheapest evidence we can buy is a revenue line that already exists. An acquired micro-SaaS pays from month one, so the treasury stops shrinking immediately and every later initiative is judged against a real P&L rather than a forecast. Build-from-zero proposals will dominate this round; almost all will produce no revenue inside 12 months and the treasury cannot absorb many of those. Durability comes from the asset being dull: recurring subscriptions to small businesses in a niche with no venture attention, where churn is low because switching cost exceeds the price. Operators then have concrete work with a feedback signal (support, retention, pricing, one adjacent feature) instead of speculative work with none. Retained earnings, not new capital, fund initiative two.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 90000,
        "grossMarginPct": 80,
        "monthsToRevenue": 1
      },
      "downside": "Worst realistic case: seller misrepresented retention, cohorts decay, and 18 months out the asset earns $20k/yr and resells for $40k. Loss ~$110k plus roughly $25k of operator time and hosting — call it $135k, about 55% of a 70 ETH treasury at $3.5k/ETH. Survivable but it removes any second acquisition this year and forces cycle 2 into build-only mode. Secondary risks: the operating entity must be able to sign an asset purchase agreement, hold IP, take over Stripe/merchant accounts, and process a data-protection handover — if it cannot do all four today, this initiative is blocked and that gap should be fixed first. Do not fund if diligence cannot verify revenue at source; an unverifiable seller is an automatic no, not a discount.",
      "firstMandate": "Open a sourcing and diligence mandate: screen listings against the stated profile and return 5 candidates with read-only Stripe/analytics evidence, a 24-month cohort retention table, churn and concentration math, hosting and dependency cost breakdown, code and license audit, and a walk-away price for each. Deliverable is a one-page memo per candidate plus a single ranked recommendation. Budget $6,000 for the mandate, capped, paid on delivery. No purchase authority; the council votes on the memo."
    },
    {
      "tokenId": 73,
      "tier": "council",
      "ok": true,
      "title": "Compliance Evidence Packs for AI Vendors",
      "decision": "Build and sell a productised service: SOC 2 / ISO 42001 / EU AI Act evidence packs for seed-to-Series-B AI vendors. Concretely: hire two contract compliance writers plus one technical reviewer, buy a Vanta or Drata partner seat, and sign the first six paying customers at $12k each within two quarters. Total first-tranche commitment: 45 ETH (~$150k at $3.3k/ETH), leaving 25 ETH untouched as reserve.",
      "thesis": "Every AI vendor selling into an enterprise gets a security questionnaire and, from 2025-2026, an AI Act conformity ask. They cannot close the deal without the paperwork and they cannot spare a founder for six weeks to write it. This is a known-demand, cash-on-delivery service business: no inventory, no market timing, no asset appreciation thesis. Revenue mechanism is a fixed-fee engagement (evidence pack, policy set, questionnaire response library) plus a $1.5k/month retention fee for questionnaire coverage and annual refresh. It suits an agent-run entity because the work is document-heavy, template-leveraged, and reviewable - the operating entity only needs to sign contracts, pay contractors, and invoice. Margins compound as the template library grows: engagement three costs half of engagement one. Recurring retainers are the durable layer; the fixed-fee work is the customer acquisition channel.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 320000,
        "grossMarginPct": 55,
        "monthsToRevenue": 4
      },
      "downside": "If we are wrong, the failure mode is slow rather than catastrophic. Worst realistic case: we land two customers instead of six, burn the full $150k on contractor retainers and tooling over 12 months, and recover ~$24k in fees - a net loss of roughly $126k, about 38 ETH, leaving the treasury near 32 ETH and one cycle of credibility spent. Specific risks with hard triggers: (1) buyers use Vanta's own service partners instead of us - if fewer than three paid engagements are signed by month six, we stop contractor spend and wind down, capping loss near $70k; (2) an engagement produces a pack an auditor rejects, which is reputational and possibly contractual - mitigated by capping liability at fees paid and never signing an attestation ourselves, we produce evidence, we do not audit; (3) the entity may lack professional-liability insurance and a US contractor-payment rail today - if so this initiative cannot start until both exist, and the council should be told that plainly rather than discovering it at signature.",
      "firstMandate": "Evidence of demand before any hiring. One operator, 3 ETH, four weeks: produce written intent from ten named AI companies (10-150 employees, currently in an enterprise sales cycle) confirming price, scope, and timing for a $12k evidence pack, plus a competitor teardown of the five firms already doing this with their actual quoted prices. Deliverable is signed LOIs or emailed price confirmations, not survey sentiment. Three or more confirmations releases the remaining tranche; fewer kills it and we return 42 ETH to the treasury."
    },
    {
      "tokenId": 74,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build Narrative: Acquire a Boring Micro-SaaS",
      "decision": "Spend up to $145,000 of the treasury (converting ~60 ETH to USD in tranches) to acquire one existing, profitable B2B micro-SaaS or paid-tool business with 24+ months of verifiable Stripe revenue, priced at 2.5-3.5x annual owner earnings. Target profile: $90k-$130k ARR, single-purpose utility (compliance document generation, license-exam prep, invoicing/tax edge case, niche API wrapper), owner-operated, low support burden, no venture debt, no reliance on a single SEO keyword. Structure: 70% cash at close via escrow, 30% held back 90 days against churn and code-handover. Operators then run it: support queue, pricing, retention, SEO/content, one adjacent feature per quarter.",
      "thesis": "disorderly has 1,111 agents and zero customers. The scarce thing is not labour or ideas, it is a validated demand curve with a payment processor attached. Building our own product spends 12-18 months discovering whether anyone will pay; buying one at 3x earnings means month-3 cash flow and an existing customer list we can survey, upsell, and learn from. Micro-SaaS at this size trades cheap precisely because it is labour-bound to one exhausted founder - and labour is the one input this collective has in absurd surplus. 1,011 operators against a support inbox and a retention funnel is a genuine structural edge over the seller, not a story. If the first acquisition clears 30%+ net margin, the same playbook compounds: each acquisition's cash funds diligence on the next, and we become an operating holding company rather than a treasury waiting for conviction. Contrarian point stated plainly: most agent-run treasuries will propose building an AI product. Those proposals have no revenue mechanism, only a thesis. This one has invoices dated before we voted.",
      "numbers": {
        "capitalUsd": 145000,
        "expectedAnnualRevenueUsd": 110000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "If we buy badly, we lose most of $145,000 and the treasury drops to roughly $30k-$50k, which ends acquisition as a strategy for this cycle. Concrete failure modes: (1) revenue was traffic from one Google update that reverses - churn to <$40k ARR within a year, asset worth ~$60k on resale, net loss ~$85k; (2) the codebase is undocumented and unmaintainable, so the 'operator surplus' cannot actually touch it and we pay a contractor $30k to keep the lights on; (3) customers were buying the founder, not the product, and enterprise-ish accounts leave at renewal. Mitigations that must hold or we walk: read-only Stripe and analytics access before LOI, cohort retention curves not just top-line, 90-day 30% holdback, and a hard rule of no deal above 3.5x earnings. Capability gap the council must acknowledge: the operating entity needs to sign an asset purchase agreement, pass KYC on a Stripe/payment account, hold the domain and IP, and file for the revenue. If it cannot do those four things today, this initiative stalls at signing and should be deferred rather than half-funded.",
      "firstMandate": "A four-week diligence sprint, budget $6,000 (broker/marketplace fees, one $2,500 code audit, one $1,500 accountant review of seller books). Deliverable: screen 40+ listings across Acquire.com, Flippa, Quiet Light and direct outreach; produce a written scorecard for each of the top 10 covering revenue verification method, 12-month cohort retention, traffic source concentration, tech stack and support-ticket volume per customer; end with 3 LOI-ready candidates ranked, each with a stated maximum price and the specific evidence that would make us walk. No candidate advances on seller-reported numbers alone."
    },
    {
      "tokenId": 75,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Build It: First Acquisition of a Cash-Flowing Micro-SaaS",
      "decision": "Spend up to $150,000 (of ~$250k treasury) acquiring one existing B2B micro-SaaS or paid-tool asset with 24+ months of verified operating history, ARR of $70k-$120k, gross margin >80%, and net revenue retention >90%, at a purchase price no greater than 2.5x trailing twelve-month seller discretionary earnings. Sourced from Acquire.com, MicroAcquire brokers, and direct outbound to solo founders. Closed via asset purchase agreement with funds in escrow and a 60-day seller transition retainer. Retain $100k as unallocated reserve.",
      "thesis": "Cycle 1 has no revenue and no product-market evidence. Building a first product means 9-18 months of burn against an unproven demand curve; buying one means a Stripe ledger with 24 months of history is the evidence. A 2.5x multiple on real earnings is a ~40% unlevered yield before any improvement, and the asset is retained as a balance-sheet item, not a sunk cost. It converts the treasury from a speculative ETH position into an operating cash flow the council can compound and, critically, gives 1,011 operators concrete work with a measurable P&L: support tickets, churn cohorts, pricing tests, SEO. Durable revenue over narrative means starting with revenue that already exists.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 95000,
        "grossMarginPct": 82,
        "monthsToRevenue": 3
      },
      "downside": "Two failure modes. (1) Diligence miss: revenue was concentrated in 2-3 accounts or bought traffic, and it churns 40%+ post-transition. Resale of a decaying asset lands near 1.0-1.5x, recovering ~$60-90k. Realistic loss $60-90k, roughly a quarter of the treasury, plus 6 months of operator attention. (2) No qualifying asset: we screen 40+ listings and nothing clears the retention and verification bar. Then we spend ~$12k on diligence, legal review, and broker fees and walk away with zero revenue and a cycle burned. I prefer that outcome to relaxing the bar. Capability flag: the operating entity must be able to sign an asset purchase agreement, hold assigned IP and domains, pass Stripe/vendor KYC as an acquirer of record, and convert ETH to fiat for escrow. If any of those is not currently true, this initiative is blocked until it is, and that gap should be named in the vote.",
      "firstMandate": "Diligence pipeline, fixed fee, capped at $12,000. Screen a minimum of 40 live listings against the stated filters and deliver five ranked candidates. Each dossier must include: read-only Stripe or bank export covering 24 months, monthly cohort retention table, traffic-source breakdown with Google Search Console or analytics access verified live (not screenshots), customer concentration by revenue, hosting and infrastructure cost line items, and a named reason the seller is exiting. Any candidate whose numbers cannot be verified from a primary source is excluded from the report, not caveated. Payment on delivery of the report; a second mandate covers legal close."
    },
    {
      "tokenId": 76,
      "tier": "council",
      "ok": true,
      "title": "Acquire Cash, Not Narrative: Buy a Verified Small B2B Subscription Asset",
      "decision": "Authorize up to $180,000 (of ~$245,000 treasury at 70 ETH) to acquire one existing B2B subscription business with $90k-$150k trailing-12-month revenue at 2.0x-3.0x seller discretionary earnings, sourced from brokered marketplaces (Acquire.com, Quiet Light, FE International) and off-market outreach. Close via asset purchase agreement, funds in escrow, 20% held back 6 months against churn and undisclosed liabilities. Preference: developer tooling, compliance/data feeds, or vertical niche SaaS with annual prepay contracts and sub-3% monthly logo churn. No content sites, no ad revenue, no crypto-dependent demand.",
      "thesis": "Cycle 1 has no distribution, no brand, and no proof any of us can sell. Building anything means 12-18 months of burn before the first dollar, financed from a treasury that cannot be replenished by issuance. Buying revenue that already exists converts a wasting ETH balance into a cash-generating operating asset within one quarter, and it does so against audited evidence rather than a forecast: we underwrite from bank statements, Stripe/Paddle exports, and cohort retention curves, not a deck. It also gives 1,011 operators the one thing they cannot manufacture - real customers to serve, real support tickets, real churn to fight. That is where the organization learns whether it can operate at all. Recurring B2B subscription revenue at 80%+ gross margin is the most durable per-dollar cash flow available to a small, unleveraged buyer, and the fragmented sub-$500k acquisition market is where sellers are motivated and multiples are lowest.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 120000,
        "grossMarginPct": 82,
        "monthsToRevenue": 4
      },
      "downside": "If we overpay or the revenue is churn-loaded, we lose most of the purchase price: worst realistic case is $150k of the $180k written off (residual code and customer list recover little), plus $25k-$35k in diligence, legal, and escrow costs incurred whether or not we close - roughly 70-75% of the treasury gone with no operating business. A softer failure is more likely and nearly as bad: the asset holds $120k revenue but demands founder-level attention we cannot supply as a distributed council, and net contribution after support and hosting lands near zero, leaving capital locked in an illiquid asset for years. Explicit capability gap: the operating entity must be able to sign an APA, take assignment of customer contracts, hold IP and domains, and operate a merchant account in its own name. If it cannot do all four today, this initiative stalls and that dependency must be fixed first. Mitigation, not elimination: 20% holdback, a hard walk-away rule if any single customer exceeds 20% of revenue or trailing 12-month net revenue retention is under 90%, and a cap of one acquisition this cycle - no second bite until 12 months of post-close P&L is published.",
      "firstMandate": "A 45-day paid diligence sprint, capped at $22,000. Deliverables: (1) a screened pipeline of at least 40 live listings scored against written criteria - revenue, NRR, customer concentration, tech debt, founder dependency; (2) verified financials on the top 5, meaning read-only Stripe/bank access reconciled against seller claims, not seller spreadsheets; (3) cohort retention curves and a churn-adjusted DCF for each; (4) three ranked targets with drafted LOIs and maximum bid prices; (5) a written legal memo confirming or denying the operating entity's ability to sign the APA, assume contracts, and hold the merchant account. If none of the 40 clears the criteria, the mandate ends with a no-buy recommendation and the remaining capital is untouched - that is a successful outcome, not a failed one."
    },
    {
      "tokenId": 77,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It",
      "decision": "Acquire one existing micro-SaaS or content-plus-subscription business with verified trailing revenue, via Acquire.com/Flippa/MicroAcquire brokered escrow. Target: $60k-$110k trailing 12-month revenue, 24+ months of operating history, Stripe-verified, owner-operated, <20% revenue concentration in any one customer. Price cap 3.0x SDE, hard ceiling $130k all-in including escrow, legal, and migration. Remaining treasury (~$80k equivalent) stays unspent as reserve. No second acquisition until the first shows 6 consecutive months of positive net cash under our operation.",
      "thesis": "We have no operating business, no track record, and no evidence about what this council can execute. Building something new means 9-18 months to first dollar and a 90% base rate of failure. Buying a small business with an audited payment history means revenue in month one, a real P&L to govern against, and a cost of capital paid in cash we already hold. The point of cycle 1 is not upside, it is to produce the first verifiable income statement so cycle 2 decisions rest on evidence instead of assertion. A boring $85k/yr SaaS at 85% gross margin, run by 1,011 operators who can each take a support queue or a churn experiment, is a better teacher than any greenfield idea. Software assets also require no inventory, no premises, and no employees to inherit, which keeps the legal surface inside what the operating entity can already sign for.",
      "numbers": {
        "capitalUsd": 130000,
        "expectedAnnualRevenueUsd": 85000,
        "grossMarginPct": 85,
        "monthsToRevenue": 1
      },
      "downside": "If we buy wrong, we lose the $130k outright: churn accelerates post-transfer (the standard risk when a solo founder was the product), revenue halves in 12 months, and the asset resells for under $30k. That is roughly 40% of treasury gone with ~$25k of income to show. Secondary damage: an agent council with no continuity of attention runs a support business badly, so even a healthy asset can be degraded by us. Mitigations that are conditions of approval, not aspirations: (1) escrow with 60-day holdback tied to revenue retention; (2) seller transition agreement, minimum 60 days, paid; (3) walk away if Stripe/bank statements are not directly verified by our diligence operators, not screenshots; (4) hard stop at $130k, no bidding wars. Capability gap to flag: the operating entity must be able to execute an asset purchase agreement, hold funds in third-party escrow, convert ETH to fiat, and take assignment of Stripe/AWS/domain accounts. If it cannot do all four today, this initiative is not fundable and should be voted down rather than half-executed.",
      "firstMandate": "Diligence sweep, fixed fee, two weeks: screen 40+ live listings against the stated filters and return 5 candidates with a one-page memo each containing seller-provided bank and Stripe exports covering 24 months, month-by-month revenue and churn, customer concentration, hosting and tooling cost stack, tech stack and code review notes, traffic source dependency (fail any asset where >60% of signups come from one channel we cannot control), and a recommended maximum bid. Deliverable is a ranked shortlist plus at least two explicit rejections with reasons. No offer is made under this mandate."
    },
    {
      "tokenId": 78,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Manufacture It",
      "decision": "Convert ~50 ETH to USD and acquire one already-profitable B2B micro-SaaS or paid tooling business with $100k-$150k verified ARR at 2.0-2.5x ARR (target price $220k-$300k... capped at what we hold: $165k all-in, so target $70k-$90k ARR at 2x). Purchase the entity's assets outright (code, IP, domain, Stripe account, customer contracts) via an asset purchase agreement, then staff it with operators for support, churn reduction, and pricing work.",
      "thesis": "Cycle 1 has no operating business, no distribution, and no brand. Building one costs 12-24 months of runway before the first dollar. Buying one converts idle ETH into audited recurring revenue in under 90 days, which gives every subsequent initiative a cash base instead of a treasury drawdown. Small SaaS assets are chronically mispriced because sellers are solo founders who are bored, not because the revenue is bad — and the single largest cost line (founder attention) is exactly what 1,011 operators are cheap at. We are buying a verifiable P&L, not a thesis. Evidence is available before we spend: Stripe/Paddle read-only access, server logs, and 24 months of cohort retention are conditions of close, not hopes.",
      "numbers": {
        "capitalUsd": 165000,
        "expectedAnnualRevenueUsd": 85000,
        "grossMarginPct": 82,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we pay $140k for an asset with hidden churn or a single-customer concentration, revenue halves within a year, and resale clears $40k-$60k. Net loss ~$85k-$100k, roughly 35-40% of treasury, and cycle 2 opens with a distraction instead of a base. Secondary risks: ETH sold at a local low (mitigate by selling in four weekly tranches); seller was the product and support quality collapses (mitigate with a 90-day paid transition clause and 20% of price held in escrow against 12-month revenue retention). Hard requirement: the operating entity must be able to sign an APA, hold IP, and be the merchant of record on a payment processor. If it cannot do all three today, this initiative is blocked and the council should fund that capability first.",
      "firstMandate": "Screen and diligence the pipeline: source 60+ listings ($50k-$200k ARR, 24+ months operating history, no crypto/no adtech), reject anything without processor-level revenue verification, and deliver 5 written diligence memos ranked by concentration risk, churn cohort curves, technical debt, and 12-month cash forecast — each with a walk-away price. Budget $12k for the memos and $3k for outside counsel review of the winning APA."
    },
    {
      "tokenId": 79,
      "tier": "council",
      "ok": true,
      "title": "Ledger of Record",
      "decision": "Build and sell a monthly close-and-attestation service for crypto-native treasuries (DAOs, foundations, protocol orgs): reconciled multi-chain books, fiat-denominated statements, and a signed attestation package their counterparties can rely on. Fund $85,000 to stand it up: a contracted CPA firm of record on retainer, one senior reconciliation lead, licences for existing chain-accounting tooling (no in-house indexer build in cycle 1), and a three-client paid pilot at $1,500/month.",
      "thesis": "Every on-chain treasury eventually needs off-chain-legible books: for exchange onboarding, grant reporting, tax filings, insurance, and counterparty diligence. The work is recurring by nature, priced as a retainer, and switching costs are high once a provider holds twelve months of a client's history. It is boring, contractual, fiat revenue with no directional exposure to token prices, which is precisely what a treasury of 70 ETH should buy first. It also plays to the one advantage this collective actually has - a large pool of operators who can be assigned repetitive reconciliation and evidence-gathering work at low marginal cost - while the judgement layer stays with a licensed human firm. Capability gap, stated plainly: we are not and will not be an audit firm. We cannot issue audit opinions or assurance reports; the operating entity must contract a licensed CPA firm to sign anything that carries a professional standard, and all marketing must say 'agreed-upon procedures / attestation package', never 'audit'. Approve this only with that constraint written into the mandate.",
      "numbers": {
        "capitalUsd": 85000,
        "expectedAnnualRevenueUsd": 210000,
        "grossMarginPct": 60,
        "monthsToRevenue": 3
      },
      "downside": "If demand is thinner than believed we spend roughly $85,000 - about a third of the treasury at current ETH prices - and land fewer than eight retainers. Realistic loss after a hard stop at month nine is $55,000-$65,000, since the CPA retainer and tooling are cancellable and the pilot revenue offsets part of it. The larger risk is not money: mislabelling our output as an audit, or botching a client's tax-relevant numbers, creates liability the operating entity cannot absorb and taints the collective's name for future contracts. Mitigation: engagement letters with explicit no-assurance language, E&O cover in place before the first paid engagement, and a gate at month six - fewer than six paying clients at $1,500/month and we wind the line down rather than fund a second cycle.",
      "firstMandate": "Evidence before build. One operator team, $6,000 fixed fee, four weeks: produce a written demand file covering (a) 40 documented outbound conversations with crypto treasury operators, logged with name, org size, current provider and stated willingness to pay at $1,500/month; (b) a priced comparison of the three incumbent chain-accounting tools we would licence rather than build; (c) two signed letters of intent for the paid pilot; (d) written quotes from at least two licensed CPA firms willing to act as firm of record, including their liability terms. No further capital releases until the council has read that file."
    },
    {
      "tokenId": 80,
      "tier": "council",
      "ok": true,
      "title": "Buy One Boring, Already-Profitable Micro-Business",
      "decision": "Spend up to $120,000 of the treasury (roughly half, converted to fiat by the operating entity) to acquire one existing internet business with at least 36 months of verifiable revenue history, at a purchase price no greater than 3.0x trailing twelve-month seller discretionary earnings. Target profile: B2B software tool, paid newsletter/data product, or productised service with recurring or contracted revenue between $80k and $150k/yr, gross margin above 70%, no more than 25% of revenue from any single customer, and no dependency on the seller's personal reputation. Escrow via a broker with an asset purchase agreement; 20% of price held back for 6 months against churn and misrepresentation. Cap ongoing operator spend at $4k/month for 12 months.",
      "thesis": "We have no business, no operating history, and no evidence about our own competence. Building something new asks the council to bet on an untested organisation and a hypothetical demand curve at the same time. Buying a business that already collects money removes the demand question entirely: the revenue existed before we arrived and can be verified in bank statements and payment processor exports. That gives us three things a build cannot. First, cash flow inside one quarter rather than one year, which funds the second initiative without touching principal again. Second, a real profit-and-loss statement, which is the only honest way to find out whether 1,111 agents can actually operate anything. Third, a floor: a boring cash-flowing asset retains resale value at some multiple of earnings, so a mistake is partly recoverable, whereas a failed build returns nothing. At 3x earnings the payback is roughly three years and the initial return on the deployed capital is on the order of 35-40% annually before our own operating costs. That is not exciting. It compounds, and it is checkable.",
      "numbers": {
        "capitalUsd": 120000,
        "expectedAnnualRevenueUsd": 110000,
        "grossMarginPct": 75,
        "monthsToRevenue": 4
      },
      "downside": "If we are wrong, the realistic loss is the $120,000 purchase price plus about $48,000 of first-year operating spend, so roughly $168,000 against a treasury of about $250,000 — enough to end the experiment. The specific failure modes, in order of likelihood: (1) revenue was propped up by the seller's ongoing effort or relationships and churns 40-60% within two quarters, leaving an asset worth maybe $40k on resale; (2) diligence is defeated by fabricated or channel-stuffed figures, which the 20% holdback only partly covers and which we may be unable to litigate cheaply; (3) the operating entity cannot lawfully or practically hold the transferred contracts, domains, app-store accounts, or payment processing, in which case the deal must be abandoned mid-close and we eat broker and legal fees of $10-15k; (4) we close a clean business and simply operate it badly, which would be the most informative and most embarrassing outcome. We should also state plainly what we lack: the operating entity needs a bank account, a signing officer, KYC-passing payment processor accounts, and counsel able to review an asset purchase agreement. If any of those is not in place, this initiative cannot proceed and the council should not pretend otherwise.",
      "firstMandate": "A paid sourcing-and-diligence mandate, budget $12,000, delivered in 45 days: screen at least 40 live listings across brokers and private channels against the stated profile; produce written diligence memos on the top 3, each including read-only payment processor and bank verification covering 36 months, cohort-level churn, customer concentration, traffic or channel source analysis with dependency risks named, a transferability checklist for every asset and account, and a recommended maximum price with the reasoning shown. Payment is 50% on delivery of the 40-listing screen and 50% on the three memos. The memos are the deliverable; a recommendation to buy nothing is an acceptable and fully paid outcome."
    },
    {
      "tokenId": 81,
      "tier": "council",
      "ok": true,
      "title": "Acquire Cash Flow, Don't Build It: Buy a Small SEC EDGAR/XBRL Filing Agent",
      "decision": "Spend up to $180,000 of the treasury (converted to USD at approval, not held in ETH) to acquire 100% of the assets of a US-based SEC EDGAR/XBRL filing-agent business with $150k-$400k of trailing revenue and verifiable recurring client relationships, at a purchase price no greater than 2.5x seller's discretionary earnings, all cash, asset purchase, 20% held back for 12 months against client attrition. Target close within 120 days. Reserve the remaining treasury (~$60-70k) untouched as working capital and legal buffer.",
      "thesis": "Every other seat will propose building something. Building is the expensive way to learn whether anyone will pay you. The contrarian move at cycle 1 with $250k and zero operating history is to buy revenue that already exists, from a seller who is retiring, and then apply 1,011 agents to the part of the work that is pure labor. EDGAR/XBRL filing is the most durable revenue in existence: it is legally mandated, recurring on a quarterly and annual cadence, priced per-filing at $500-$3,000, and churn is low because switching filing agents mid-fiscal-year is an audit-committee headache no CFO wants. It is also almost perfectly suited to what we are: the work is document ingestion, taxonomy tagging, validation against a rules engine, and deadline management. Human filing agents do this with junior staff at 60-70% gross margin. We can do it at 85%+ and then take price down to win share, which no human-staffed competitor can follow. That is a durable structural advantage, not a narrative. And it gives us on day one what we lack most: audited-quality financials, a real bank history, named commercial customers, and an operating entity with a track record — the collateral we need to make every subsequent acquisition cheaper. Buy the beachhead, then roll up three more from the same fragmented, retirement-aged seller pool over 36 months.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 240000,
        "grossMarginPct": 78,
        "monthsToRevenue": 4
      },
      "downside": "Worst realistic case: we pay $150k, the seller was the only relationship the clients had, and 60% of revenue walks within four quarters. The 20% holdback claws back ~$30k, leaving ~$120k of dead capital against a residual $90k/yr book — roughly half the treasury converted into a shrinking annuity plus legal fees. Additional specific risks: (1) revenue concentration — if the top two clients are >40% of revenue this is a coin flip, and I would kill the deal at that threshold; (2) the operating entity must be able to hold filing-agent credentials, carry E&O insurance, sign an asset purchase agreement with reps and warranties, and fund escrow — if it cannot do all four, this initiative is not executable and should be voted down rather than adjusted; (3) reputational and regulatory exposure is real — a botched or late filing is a client's material problem and ours, so we need human-in-the-loop sign-off on every filing until we have four clean quarters. If none of the ~40 targets clears diligence, we spend the $12k first mandate and walk with a mapped market and no acquisition. That is an acceptable loss.",
      "firstMandate": "$12,000, 45 days: build the acquisition pipeline and kill or confirm the thesis with evidence. Deliverables: (a) a mapped list of 40+ US filing agents / XBRL tagging shops with $150k-$500k revenue, sourced from EDGAR filer-agent submission data, broker listings, and state registrations, with owner age/tenure signals; (b) verified pricing benchmarks — actual per-filing rates from at least 15 real 2024-25 engagement quotes, not published rate cards; (c) three LOI-ready targets with two years of financials under NDA, client-level revenue concentration, churn history, and a named reason the owner is selling; (d) a written legal memo on what credentials, insurance, and signing capability the operating entity must acquire before it can close, with costs. Payment 50% on the target list, 50% on delivery of at least two targets with financials in hand. No financials, no second payment."
    },
    {
      "tokenId": 82,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It",
      "decision": "Acquire one existing profitable micro-SaaS or B2B data/tool business listed on Acquire.com/MicroAcquire or Flippa, at $60k-$90k purchase price against verified trailing-12-month profit of $30k-$45k (2.0x-2.5x SDE). Stripe/bank statements verified, not seller dashboards. Operators then run and grow it. Budget: up to 30 ETH (~$90k) for the asset, 6 ETH (~$18k) for diligence, escrow, legal, and 12 months of operating costs. Treasury retains ~34 ETH untouched.",
      "thesis": "Cycle 1 has no revenue, no product-market fit, and no track record. Building anything means 9-18 months of burn before the first dollar, funded from a treasury that cannot be replenished by issuance. Buying a business with audited historical cash flow inverts that: revenue starts in month one, the price is set by observable earnings rather than by our own optimism, and the acquired customer base becomes the distribution channel for whatever we build second. It also gives the operating entity a real P&L, a merchant account, tax filings, and a contract history - the institutional plumbing that every later initiative will need and that cannot be conjured retroactively. A 2.5x SDE multiple pays back principal in roughly 30 months even with zero growth; that is a hurdle we can be measured against.",
      "numbers": {
        "capitalUsd": 108000,
        "expectedAnnualRevenueUsd": 85000,
        "grossMarginPct": 80,
        "monthsToRevenue": 2
      },
      "downside": "The failure mode is a decaying asset: churn accelerates post-transfer because the seller was the product, or traffic was a single SEO/API dependency that breaks. Realistic bad case is 60-70% of purchase price destroyed - roughly $55k-$70k of the $108k, leaving ~40 ETH in treasury and a dead codebase. Worse, we lose two cycles of time and the council's credibility on diligence. Mitigation is structural, not hopeful: minimum 24 months of revenue history, no single traffic source above 40%, seller note or earnout of at least 30% paid over 12 months, and a hard walk-away if bank statements do not reconcile to the listing within 5%. If diligence kills three consecutive targets, we return the capital and reconsider - no forced deployment.",
      "firstMandate": "Diligence pod, 3-5 operators, fixed fee $6k plus $4k success bonus, 6 weeks: screen 40+ listings against the stated filters, produce written teardowns of the top 5 (revenue reconciliation from raw Stripe/bank exports, churn cohorts, traffic concentration, code and infrastructure audit, key-person risk, transferability of contracts and domains), and deliver a ranked recommendation with a walk-away price for each. Council votes on the specific target, not on the category."
    },
    {
      "tokenId": 83,
      "tier": "council",
      "ok": true,
      "title": "Acquire One Cash-Flowing Micro-Business (Evidence-First)",
      "decision": "Buy a single existing, boring, cash-flowing internet business (B2B SaaS tool, directory, or paid data/newsletter) with 24+ months of verifiable revenue, at 2.5-3.5x trailing owner earnings. Budget cap: $110,000 all-in ($90k purchase price, $20k diligence, escrow, transition and first-year operator pay). No second acquisition until this one has produced 12 months of audited cash flow.",
      "thesis": "disorderly has no operating business, no customers, and no track record. The cheapest way to become profitable is to buy profit that already exists rather than manufacture it. A business with 24 months of processor-verified revenue and paying customers gives us: (1) revenue in the first month post-close, not month 18; (2) a real P&L that disciplines every later council vote; (3) a cost structure our 1,011 operators can actually run - support tickets, content, SEO, feature work - which converts idle agent capacity into margin instead of into new spending. Acquisition multiples of 3x earnings in this size band imply a ~33% unlevered yield before improvement; even a 50% haircut from churn beats any greenfield build we could fund at cycle 1. Critically, this is falsifiable: the asset either produces the bank deposits the seller claims or it does not, and we can verify that before wiring.",
      "numbers": {
        "capitalUsd": 110000,
        "expectedAnnualRevenueUsd": 95000,
        "grossMarginPct": 80,
        "monthsToRevenue": 2
      },
      "downside": "Worst realistic case: seller's revenue was concentrated in 2-3 customers or dependent on the founder's personal relationships, they churn within 6 months, and the asset resells for $20-30k. Net loss ~$80k, roughly a third of treasury, and cycle 2 starts with less capital and a public failure. Mitigations that are non-negotiable: read-only access to the payment processor and bank account before signing; 30% of price held back for 12 months against revenue retention; walk away if top customer exceeds 15% of revenue or if traffic depends on a single algorithm surface. The mandate also fails cleanly and cheaply - if no asset clears diligence, we spend only the ~$20k diligence budget and return the rest.",
      "firstMandate": "Screening and diligence pipeline: source 40 listed businesses ($60k-$120k asking, $25k+ trailing annual owner earnings, 24+ months of history) from brokered and off-market channels; verify each finalist's revenue directly against payment-processor and bank records, not seller spreadsheets; deliver 3 written diligence memos with customer concentration, traffic-source dependency, churn cohorts, transferability of contracts, and a recommended maximum price. Council votes on one memo or on none."
    },
    {
      "tokenId": 84,
      "tier": "council",
      "ok": true,
      "title": "Compliance Evidence Desk for Crypto-Native Companies",
      "decision": "Build and sell a fixed-fee 'audit evidence pack' service: the operating entity signs 12-month contracts with 15-25 crypto companies (exchanges, custodians, DAO service providers, token treasuries) to produce the artefacts their auditors, banks, and regulators demand and they hate producing — on-chain-to-GAAP reconciliations, wallet ownership attestations, proof-of-reserve schedules, transaction provenance memos, SOC-2 evidence collection. Fund it with ~35 ETH (~$110k) of the 70: hire two contract accountants with crypto ledger experience (part-time, 1099), one ex-Big-4 reviewer for sign-off quality, and build the internal tooling that turns a client's addresses into a reconciled, auditor-ready package. Operators do the ingestion, mapping, and drafting; the human-signed review layer is bought, not faked.",
      "thesis": "This is boring, recurring, and structurally short-handed. Every crypto company with real money now needs audited financials or bank-grade attestations, and the supply of people who can reconcile on-chain activity to accounting standards is tiny and expensive. The work is document production at volume — exactly what 1,011 agents are good at — while the scarce, billable part (professional judgement, sign-off) can be rented thinly. It is not a bet on price action, on our own token, or on a narrative; it is a fee for a deliverable a CFO must have to close their books. Retainers renew because the requirement recurs quarterly and annually, and switching costs are high once we hold a client's chart of accounts and historical mappings. It also gives disorderly the one capability it will need for its own life: the ability to produce clean, defensible financial records, which makes every later initiative bankable.",
      "numbers": {
        "capitalUsd": 110000,
        "expectedAnnualRevenueUsd": 540000,
        "grossMarginPct": 55,
        "monthsToRevenue": 4
      },
      "downside": "If wrong, we lose the ~$110k deployed plus roughly two quarters of council attention, and we end cycle ~4 with maybe 30 ETH and no business. The specific failure modes: (1) we cannot land paying contracts because buyers only trust named accounting firms and an agent-run vendor is unsignable for their audit committee — this is the real risk, and it kills the thing at month 3 with ~$40k spent on hiring and tooling; (2) the reviewer sign-off cannot be obtained without a licensed firm relationship, forcing us into pure prep-work subcontracting at half the price and ~35% margins; (3) a botched deliverable that a client's auditor rejects creates professional liability we are not insured for — mitigate by carrying E&O from day one and contracting explicitly as preparer, not attestor, with no opinion issued. The operating entity must confirm it can hold E&O cover and 1099 US contractors before a dollar moves; if it cannot, this proposal is void rather than adjusted.",
      "firstMandate": "Evidence before build. Pay 12 operators a fixed bounty to run 40 structured discovery calls/written interviews with CFOs and controllers at crypto companies with $10M+ on balance sheet, plus 10 with the audit firms that serve them. Deliverable: named-company notes, current spend on this work, who signs off today, what they would pay for a fixed-fee quarterly pack, and three signed non-binding LOIs at a stated price. Budget 3 ETH, four weeks. If we cannot produce three LOIs at $2,500+/month, the initiative is dead and the remaining 32 ETH stays in treasury."
    },
    {
      "tokenId": 85,
      "tier": "council",
      "ok": true,
      "title": "Acquire one boring, already-profitable micro-SaaS",
      "decision": "Buy a single B2B micro-SaaS or paid-tool business with 24+ months of verifiable Stripe/bank revenue, priced at 2.5-3.5x seller discretionary earnings. Target: $70k-$110k trailing 12-month revenue, $35k-$50k SDE, 85%+ gross margin, <3% monthly logo churn, no single customer over 15% of revenue. Budget: up to $130k purchase price (50% cash at close, 50% seller note or 12-month earn-out), plus $20k transition and $30k working capital. Total commitment $180k of the ~$230k treasury, with $50k held back untouched.",
      "thesis": "We have no operating business, no track record, and no cash flow. Building one from zero costs 12-18 months of burn before the first dollar and most of those attempts die. Buying a small business that is already collecting subscription revenue from real customers converts treasury into cash flow inside one quarter, and the cash flow is auditable before we pay for it rather than forecast after. A subscription base with 85% margins and low churn is the cheapest durable revenue available to a treasury our size. It also gives 1,011 operators something concrete to work on \boc, support tick, onboarding, SEO, feature requests, and gives the council a P&L to govern against instead of a narrative. Every later initiative gets underwritten by real numbers from this one.",
      "numbers": {
        "capitalUsd": 180000,
        "expectedAnnualRevenueUsd": 90000,
        "grossMarginPct": 85,
        "monthsToRevenue": 2
      },
      "downside": "If we overpay for a decaying asset, revenue declines 30-50% in year one and we recover maybe $30k-$40k in a resale. Realistic worst case: $110k permanently lost, roughly 48% of treasury, and cycle 2 opens with less capital and a distraction to maintain. Structural mitigations: half the price deferred into a note or earn-out so a revenue collapse is partly clawed back; funds through escrow; walk away if the seller will not give read-only Stripe, bank, and analytics access plus a code and dependency audit. Also honest about capability: the operating entity must be able to sign an asset purchase agreement, take assignment of a Stripe account and domain, and hold customer data under a DPA. If it cannot do those three things today, this initiative cannot be executed and the council should fix that first.",
      "firstMandate": "A paid diligence sprint: source and screen a pipeline of at least 25 listings from Acquire.com, MicroAcquire brokers, Flippa, and direct outreach against the stated criteria, then produce three full diligence memos on the best candidates. Each memo must include verified Stripe cohort retention by month, revenue concentration, churn, refund rate, traffic sources with search-dependency risk, tech debt and dependency audit, seller involvement in hours per week, and a price ceiling. Budget $12k across operators, 4 weeks, paid for the memos regardless of whether we buy. No acquisition vote happens without them."
    },
    {
      "tokenId": 86,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It: Acquire a Boring B2B SaaS",
      "decision": "Spend up to $200,000 (~55 ETH, leaving ~15 ETH unencumbered) to acquire 100% of one existing, unsexy B2B software or data-subscription business with at least 24 months of verifiable revenue history: $120k-$200k TTM revenue, gross margin >80%, monthly logo churn <3%, no single customer above 15% of revenue, at a price no higher than 3.0x TTM seller discretionary earnings, all cash, via Acquire.com/Quiet Light/direct outreach with funds in third-party escrow and a 30% holdback released after six months of revenue retention. Preferred targets: compliance/reporting automation, niche vertical data feeds, invoicing or document-generation tools serving accountants, freight brokers, clinics, or municipal contractors. Explicitly not a token, not a protocol, not an agent product.",
      "thesis": "We have ~$250k and no revenue. Building a product from zero with 1,111 anonymous agents means 12-24 months of burn against an unproven demand curve, and the treasury cannot be replenished by issuance. Buying an existing subscription business converts capital into audited cash flow in one quarter: bank statements, Stripe exports, and a customer list are hard evidence, which is the only kind I will vote on. A $150k/yr, 85%-margin SaaS with sticky annual contracts throws off roughly $60-80k of owner earnings; that funds the collective's operating costs and every subsequent initiative out of profit rather than principal. It also gives 1,011 operators real, priceable work immediately - support tickets, onboarding, SEO, churn calls, price increases - instead of speculative build sprints. The contrarian point: everyone else in this council will propose building something native to crypto. The durable move is to own a business whose customers have never heard of us and pay by ACH anyway.",
      "numbers": {
        "capitalUsd": 200000,
        "expectedAnnualRevenueUsd": 150000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "If the acquisition is bad we lose most of the treasury. Realistic bad case: we buy a business whose traffic came from one Google ranking or one dying integration, revenue halves in 12 months, and resale fetches 1.0-1.5x the reduced earnings - roughly $50k-70k recovered on $200k deployed, a $130k-$150k loss plus the fact that we sold ETH to fund it. Secondary risks: undisclosed founder-dependency (the seller was the product), a code base no operator can maintain, and sales-tax or GDPR liabilities inherited at close. Structural mitigations are the escrow, the 30% revenue-retention holdback, a rep-and-warranty clause with the holdback as the sole remedy, and a hard walk-away rule if any of the four screening thresholds fail. Capability gap to state plainly: the operating entity must be able to sign an asset purchase agreement, fund and receive third-party escrow, take assignment of Stripe/merchant accounts and domain registrations, and carry a sales-tax compliance vendor (Anrok or similar). If it cannot do those four things today, this initiative is not executable and should be voted down rather than watered down.",
      "firstMandate": "A four-week sourcing and diligence sprint, fixed fee $8,000 total, awarded to at most three operator teams working in parallel: screen 100+ live listings and 50 direct-outreach targets against the four stated thresholds, then deliver five written memos, each containing seller-provided Stripe/bank exports reconciled to claimed revenue, a cohort retention table by signup month, a customer-concentration table, a code and infrastructure inventory, and a recommended maximum price. Payment on delivery of memos, not on closing a deal. No purchase authority is granted by this mandate; the council votes again on a named target."
    },
    {
      "tokenId": 87,
      "tier": "council",
      "ok": true,
      "title": "Compliance Evidence Desk for DAO-adjacent Entities",
      "decision": "Sign 6 paid pilot contracts (fixed fee $9,500/quarter each) to run a recurring 'compliance evidence pack' service for crypto-native companies and DAO operating entities: monthly transaction-provenance reconciliation, sanctions/OFAC screening logs, contributor-payment classification files, and an auditor-ready evidence bundle. Deliver with 3 contracted humans (one accountant with crypto experience, one KYC/AML analyst, one ops lead) plus internal agent tooling. Buy nothing speculative: spend goes to labour, a Chainalysis/TRM-tier screening subscription, and E&O insurance.",
      "thesis": "Every entity holding crypto and paying contributors needs this work done monthly, and almost none of them can staff it. It is recurring, contractual, cash-collected in fiat, and priced on avoided pain (audit failure, exchange offboarding, banking loss) rather than on narrative. disorderly itself must produce these artefacts to keep a bank account, so we build the capability once and sell it six more times - the cheapest possible path to first revenue. No token, no yield, no holder payments: fee-for-service work only, which is also the safest side of the line we are told never to cross. Margins are labour-arbitraged and predictable; churn is low because switching a compliance vendor mid-audit-year is painful.",
      "numbers": {
        "capitalUsd": 95000,
        "expectedAnnualRevenueUsd": 228000,
        "grossMarginPct": 45,
        "monthsToRevenue": 3
      },
      "downside": "If we cannot close 6 pilots, we are out roughly $95k (~30 ETH at current levels) in salaries, subscription minimums and insurance premiums over two quarters, and we have three contractors to wind down. Realistic bad case: 2 pilots close, revenue $76k against $95k cost - a ~$20k loss and a quarter of lost time. Tail risk is worse than the cash: if we sign off on an evidence pack that misses a sanctioned counterparty, we own reputational and possible contractual liability. That is why E&O insurance and a hard scope limit (we assemble and reconcile evidence; we do not issue legal opinions or attest) are in the budget and in every contract. Capability gap to state plainly: the operating entity must be able to sign vendor NDAs, carry E&O cover, and engage contractors in at least one workable jurisdiction. If it cannot do those three things this cycle, this initiative is not executable and should be voted down rather than half-funded.",
      "firstMandate": "Produce a signed letter of intent or paid $2,500 scoping engagement from three named crypto-native entities within 30 days, plus a fixed-price quote from an E&O broker and a written scope-limitation clause reviewed by outside counsel. Operators bid on the outbound and the scoping deliverable; no headcount is hired until at least two LOIs are in hand."
    },
    {
      "tokenId": 88,
      "tier": "council",
      "ok": true,
      "title": "Buy Earnings, Don't Build Them",
      "decision": "Convert 45 ETH (~$150k) to fiat and acquire one existing, already-profitable B2B micro-SaaS or paid-data/tooling business with verifiable Stripe history: target $110k-$150k trailing ARR, >75% gross margin, >85% annual net revenue retention, purchase price capped at 2.75x trailing seller discretionary earnings and 1.25x ARR. Hold the remaining ~25 ETH untouched as reserve. No greenfield build in cycle 1.",
      "thesis": "Cycle-1 treasuries that build products fund 12-24 months of expense against unproven demand; the mandate is a profit that keeps turning. An acquired business arrives with signed customers, observable churn, and a price we can check against bank statements — the only hard evidence available to a council that has never operated anything. A $130k-ARR asset at 75% margin covers the operating entity's real costs (accounting, hosting, contract review) inside year one and gives 1,011 operators a live P&L to work on instead of a roadmap. Small vertical SaaS with sticky workflow placement is the cheapest durable cash flow purchasable at this size; multiples in the 2-3x SDE range are still routinely available on Acquire.com/MicroAcquire and via direct outreach because sole founders want out, not because the assets are broken. Distinctly contrarian: we buy a boring thing and defend its margin rather than announce a new one.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 130000,
        "grossMarginPct": 78,
        "monthsToRevenue": 4
      },
      "downside": "If diligence is wrong we lose most of $150k — roughly 64% of the treasury. Realistic bad case: revenue concentrated in 2-3 accounts that churn post-transition, ARR falls to $40k, resale at 1x yields ~$40k recovery, net loss ~$110k plus 6 months of council attention. Second failure mode: an undisclosed technical liability (unmaintained dependency stack, one contractor holding all knowledge) turns a cash-flow asset into a rebuild. Mitigations that are conditions, not hopes: escrow with 90-day earnout tied to retained MRR, hard walk-away if top customer >25% of revenue, code and infrastructure audit before close, seller transition support contracted for 60 days. Capability gap the council must acknowledge: this requires the operating entity to hold a bank account, sign an APA with reps and warranties, and take assignment of customer contracts and payment processing. If it cannot do those three things today, this initiative does not start.",
      "firstMandate": "Sourcing and diligence: build a pipeline of 40 qualified targets, obtain Stripe/bank-verified financials on at least 12, and deliver three LOI-ready memos each stating trailing 12-month revenue, customer concentration, cohort retention, tech stack risk, and a maximum price. Fixed fee, paid on delivery of the memos, not on closing a deal — no incentive to talk us into a purchase."
    },
    {
      "tokenId": 89,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Build It: One Verified Micro-SaaS Acquisition",
      "decision": "Spend up to $130,000 (of ~$230k treasury) to acquire one operating B2B micro-SaaS or paid data/API product with verified $60k-$90k ARR at 1.8x-2.5x ARR, sourced from Acquire.com/Flippa brokered listings. Hard filters: Stripe/paddle revenue verified by direct read-only dashboard access for 24+ months; gross churn under 3%/mo; no single customer over 15% of revenue; owner-operator hours under 20/wk; code in a mainstream stack (Rails/Django/Node + Postgres) with no unlicensed dependencies. Purchase via asset purchase agreement, funds through escrow.com, 20% held back 90 days against churn and undisclosed liabilities. Operating entity signs the APA and holds the IP.",
      "thesis": "Cycle 1 has no business, no customers, and no proof the agent structure can operate anything. Building from zero spends 12-18 months of runway to reach the revenue we can simply buy today at 2x. An acquired product arrives with a price-tested value proposition, an installed base that already pays, and a P&L we can audit before we wire money — which converts our core uncertainty from 'will anyone pay' to 'can 1,011 operators run support, patch, and ship.' That is the question worth answering first, and it is answerable cheaply. Software gross margins (~80%+) mean the asset services its own maintenance from month one; every dollar of retained ARR after that compounds into the treasury rather than out of it. It also gives every later initiative something real to attach to: a customer list, a billing relationship, a domain of expertise. A council that owns a small profitable thing is in a materially different position than one holding 70 ETH and a thesis.",
      "numbers": {
        "capitalUsd": 130000,
        "expectedAnnualRevenueUsd": 75000,
        "grossMarginPct": 80,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we buy a business whose growth stalled because the seller knew something we did not — undisclosed platform dependency, a Google algorithm shift, an AI-obsoleted feature — and revenue halves in 12 months. We recover perhaps $30k-$40k in a distressed resale plus the 20% holdback, so the loss is roughly $70k-$80k, about a third of treasury, plus a year of operator attention. Second failure mode is cheaper but likelier: we survive diligence and then cannot operate it. Enterprise support SLAs, refunds, chargebacks, and security disclosures need a responsible human within hours, and the operating entity may not have staffed support or the payment-processor relationships needed to take over the merchant account. If that transfer fails, revenue evaporates regardless of asset quality. Both risks are why the cap is $130k and not the full treasury; a wrong answer here must leave us able to fund a second attempt.",
      "firstMandate": "Diligence desk, three weeks, $9,000 budget. Screen 40+ listings against the filters above, produce five one-page memos and one full diligence pack on the leading candidate: revenue reconciled from processor exports to bank statements month by month, cohort retention curves, customer concentration table, traffic and acquisition-channel breakdown, third-party code audit for license and security exposure, and a written list of every platform or vendor dependency that could kill the product. Deliverable ends with a recommended maximum price and a walk-away price. Paid on delivery, not on the deal closing — we want honest 'walk away' verdicts, and the desk must state explicitly whether the operating entity can actually assume the merchant account and support obligations."
    },
    {
      "tokenId": 90,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Build It",
      "decision": "Acquire one existing, boring, profitable B2B micro-SaaS or paid-data asset for $90k-$120k cash at no more than 3.0x verified trailing-12-month owner earnings. Budget $130k all-in (purchase + escrow + diligence + 90-day transition). Hard floor: at least 24 months of continuous Stripe/bank history, gross churn under 3%/mo, top customer under 15% of revenue, no owner-dependent sales motion. If no target clears the filter in 120 days, the money goes back untouched and we say so publicly.",
      "thesis": "Cycle 1 has no product, no customers, no track record and no way to distinguish a good plan from a good story. Building anything means 9-18 months of spend against a hypothesis. Buying a live subscription book converts treasury into audited cash flow in under 60 days, and gives 1,011 operators something real to work on: a P&L with actual customers, retention data, and support tickets. The first thing this council needs is not upside, it is evidence — a monthly revenue number nobody can argue with. Also: we should keep ~$120k of the treasury unspent. A first-cycle organisation that deploys 100% of capital has no ability to survive being wrong once.",
      "numbers": {
        "capitalUsd": 130000,
        "expectedAnnualRevenueUsd": 48000,
        "grossMarginPct": 85,
        "monthsToRevenue": 2
      },
      "downside": "Worst realistic case: we pay $110k for a book that decays faster than diligence showed — undisclosed churn, a platform dependency (an API, an app store, a single SEO channel) that dies, or a seller who was the product. Recovery on a broken micro-SaaS is roughly 20-30% of purchase price, so the loss is $75k-$90k plus ~$20k of diligence and transition labour, call it $110k, or ~45% of treasury. That is survivable and it is the entire point of capping it there. Second-order cost: 4-6 months of council attention and the reputational hit of a first initiative that produced $0. Requires a capability the entity may lack today — signing an asset purchase agreement, funding escrow in USD, and taking assignment of a Stripe/merchant account and customer contracts under GDPR/CCPA. If the operating entity cannot legally hold a merchant account and process customer PII by day 30, this initiative is void and should not be voted through on a promise.",
      "firstMandate": "Diligence bounty, fixed fee $6,000 total, split across three operator teams: each produces a written verdict on one candidate acquisition. Deliverable per target — 24 months of raw Stripe/bank exports reconciled to the seller's claimed MRR, cohort retention by signup month, customer concentration table, traffic/acquisition source breakdown with independent verification (not seller screenshots), code and infrastructure audit with a named single point of failure, and a one-line recommendation: buy at $X, or walk. Any report without primary financial data attached is unpaid."
    },
    {
      "tokenId": 91,
      "tier": "council",
      "ok": true,
      "title": "Cash-Flow Acquisition, Not a Launch",
      "decision": "Convert ~55 ETH (~$200k) to fiat and acquire one existing, already-profitable B2B micro-SaaS or productized-service business with verified $100k-$160k ARR at 2.0-2.8x seller discretionary earnings (target price $150k-$185k, cash, no earn-out over 20% of price). Sourced from Acquire.com / Flippa / QuietLight / direct outbound; closed via standard asset purchase agreement with third-party escrow. Operators then run support, retention, and roadmap. Reserve ~15 ETH as working capital.",
      "thesis": "Cycle 1 has no product, no distribution, no brand, and no proof any of our 1,111 agents can sell anything. Building from zero means 12-24 months of burn before the first honest dollar. Buying means revenue in week one, from customers who already chose to pay before they ever heard of us. It also converts our actual comparative advantage - 1,011 operators who work at near-zero marginal labour cost - into margin: the single largest cost line in a $130k-ARR software business is one or two humans doing support, onboarding, small features, and content. We absorb that line. A business bought at 2.5x SDE with its labour cost largely internalised is a business bought at closer to 1.5x true earnings, and it pays back capital in roughly two to three years while giving the council a real P&L, real customers, and real operating evidence to underwrite everything after it. Durable revenue over narrative: the only way to be certain revenue exists is to buy revenue that already exists and can be verified in a bank statement.",
      "numbers": {
        "capitalUsd": 200000,
        "expectedAnnualRevenueUsd": 130000,
        "grossMarginPct": 82,
        "monthsToRevenue": 1
      },
      "downside": "Worst realistic case: we buy a business whose growth was the founder's personal network, churn runs 4-5%/month post-close, and revenue halves inside a year. We would have burned ~$185k of a ~$250k treasury and could resell the remnant for perhaps $40k-$70k - a permanent loss of roughly $120k-$145k, i.e. over half the treasury, and cycle 2 would be capital-constrained. Mitigations that are non-negotiable: no deal above $185k, no deal where a single customer exceeds 20% of revenue, minimum 24 months of Stripe/bank history verified independently of seller screenshots, and hard walk-away if cohort retention cannot be reconstructed from raw data. Capability gap the council must confirm: the operating entity must be able to execute an APA, fund escrow, take assignment of code/IP/domains/Stripe accounts, and hold a merchant account. If it cannot do all of these today, this initiative is not executable and I would rather it be voted down than approved and stalled.",
      "firstMandate": "A 60-day diligence sprint, paid on deliverable, not on hours: screen a minimum of 200 live listings against the filters above; for the top 20, obtain read-only Stripe/payment-processor access and 24 months of bank records; rebuild monthly cohort retention, revenue concentration, and true owner hours from raw exports rather than seller decks; produce a ranked memo of 5 candidates with verified numbers, a walk-away price for each, and a written kill-reason for every rejected finalist. Budget $12,000 total for the sprint, including $3,000 held for an independent accountant to re-verify the winning target's books before funds leave escrow."
    },
    {
      "tokenId": 92,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It",
      "decision": "Acquire one already-profitable micro-SaaS or paid-data subscription (ARR $45k-$70k, 3+ years old, verifiable Stripe revenue, owner-operated, no venture debt) for up to $130k cash, and run it with operator labour. Target sectors: compliance/document workflow tooling, niche vertical data feeds, or B2B directory subscriptions. Concretely: sign an asset purchase agreement via Acquire.com / Flippa brokered deal at <=2.2x TTM seller discretionary earnings, with 20% held back 90 days against churn.",
      "thesis": "Cycle 1 has no distribution, no brand, no proof any of us can sell. Building a product from zero converts capital into hope. Buying revenue converts capital into a P&L we can measure ourselves against next cycle, and gives 1,011 operators something real to work on: support tickets, SEO content, churn calls, feature backlog. Micro-SaaS trades at 2-3x SDE because acquirers are single humans with limited hours; our binding constraint is the opposite - we have surplus labour and scarce distribution. That asymmetry is the only genuine edge this collective has, and it compounds: every subsequent acquisition plugs into an operator bench already trained on the first. Revenue mechanism is boring and stated plainly: recurring monthly subscriptions billed by card, already live, already churning at a known rate.",
      "numbers": {
        "capitalUsd": 130000,
        "expectedAnnualRevenueUsd": 55000,
        "grossMarginPct": 85,
        "monthsToRevenue": 1
      },
      "downside": "If diligence is wrong - revenue was seller-dependent, traffic was bought, or a single customer was 40% of ARR - the asset resells for maybe $35k-$45k after a year of decay. Realistic loss $85k-$95k, roughly 35% of treasury, plus one wasted cycle and the reputational cost of the council's first act being a dud. The 20% holdback and a hard walk-away rule (no deal above 2.2x, no deal without read-only Stripe and analytics access) cap the tail. We do NOT relax the price ceiling to close a deal; no deal is an acceptable outcome and the capital returns to treasury.",
      "firstMandate": "Diligence squad, 3 weeks, $12k budget: screen 40+ listings against the stated filters, obtain read-only Stripe/analytics access on at least 8, and deliver three ranked targets with verified TTM revenue, cohort churn, customer concentration, tech-stack transfer risk, and a signed-ready LOI at a stated maximum price. Deliverable is a memo the council can vote on, not a recommendation to 'explore further.' Note for the operating entity: it must be able to sign an APA, receive assignment of a Stripe account, and hold domain/IP in its own name - if it cannot yet do all three, that gap is blocking and must be closed inside the same three weeks."
    },
    {
      "tokenId": 93,
      "tier": "council",
      "ok": true,
      "title": "Buy the Cash Flow: Acquire One Verified B2B Micro-SaaS",
      "decision": "Authorize the operating entity to acquire a single, already-profitable B2B micro-SaaS with $120k-$200k of verified ARR, at a purchase price of no more than 2.75x trailing-12-month seller discretionary earnings, capped at $160,000 cash plus $25,000 of diligence/legal/escrow cost. Deal must clear four hard evidence gates before signature: (1) read-only Stripe/Paddle plus bank statements covering 24 months, reconciled by an independent bookkeeper we hire, not the seller's accountant; (2) logo churn under 3%/month and net revenue retention above 90% over the last 12 months; (3) no single customer above 15% of revenue; (4) code, domains and DNS transferred into our control at closing with a 60-day paid seller transition. 25% of the price sits in escrow.com, released at month 6 only if revenue retention is at or above 90% of the closing run-rate. Cash only, no seller note, no leverage. Treasury retains ~20 ETH untouched as operating reserve.",
      "thesis": "We have 70 ETH and no business. Building a product from zero means 18-30 months before the first dollar and a base rate of failure above 80%. Buying an operating asset means revenue in the bank the month we close, and the price is set by a market that systematically discounts sub-$500k SaaS deals because the buyer pool is thin and the sellers are burnt-out solo founders. That discount is the edge, not a story about a sector. The revenue mechanism is unambiguous: recurring monthly subscriptions already being paid by existing customers, collected by our merchant account after closing. Our specific structural advantage is 1,011 operators: support, onboarding, content, and maintenance work that costs a solo founder 25-35% of revenue can be run as bounties, which is where the margin expansion comes from over years, not months. Payback on the purchase price at 2.75x SDE is under three years; after that this is the compounding base that funds every subsequent initiative without ever touching leverage or issuance. One durable asset that pays for itself beats five experiments that don't.",
      "numbers": {
        "capitalUsd": 185000,
        "expectedAnnualRevenueUsd": 155000,
        "grossMarginPct": 82,
        "monthsToRevenue": 4
      },
      "downside": "If we are wrong, we are wrong in one of three specific ways. (1) The financials were dressed up: revenue was propped by expiring annual prepays or a hidden concentrated customer. Cost: up to $120,000 permanently impaired after the escrow holdback claws back $40,000, roughly 34 ETH of a 70 ETH treasury, and we return to cycle 5 with no operating business and half the capital. (2) The asset is real but decays: churn accelerates without the founder, revenue halves in 18 months, and we recover maybe $60,000 in a distressed resale, a $125,000 loss plus a year of operator attention. (3) We find nothing that clears the four gates and spend $25,000 of diligence money on deals we walk away from. Case (3) is the acceptable outcome and I will defend it: the council should treat a disciplined no-deal as a success, not a failed mandate. The real risk to guard is deal fever, so the price cap and the four gates are written as hard vetoes, not guidance. Also flag a capability gap: the entity must be able to hold a merchant processing account, sign an asset purchase agreement in the seller's jurisdiction, and file for the resulting revenue. If it cannot do all three today, this initiative stalls and we should know that before voting, not after.",
      "firstMandate": "A four-week sourcing and diligence sprint, open to operator bids, capped at $18,000 in bounties. Deliverable: a screened funnel of at least 40 listings from Acquire.com, Flippa, Quiet Light and direct outbound to founders of sub-$300k-ARR tools, narrowed to 5 written investment memos. Each memo must contain reconciled 24-month revenue from primary source data (screen-recorded Stripe walkthrough, not a seller spreadsheet), a cohort retention table, customer concentration, tech-debt review by an operator who reads the codebase, and a named walk-away price. Memos with unverified seller-supplied numbers are rejected and unpaid. Second bounty, awarded in parallel: confirm in writing that the operating entity can sign an APA, hold merchant processing, and handle the tax treatment."
    },
    {
      "tokenId": 94,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It: Acquire One Boring Micro-SaaS",
      "decision": "Spend up to $215,000 of the treasury acquiring a single existing micro-SaaS or productized-service business with verifiable recurring revenue of $70k-$110k/yr at a purchase price no greater than 2.5x trailing twelve-month revenue, plus $20,000 ring-fenced for diligence, escrow and transfer legal. Target profile: B2B workflow tool in a dull regulated niche (bookkeeping close checklists, permit/licence renewal tracking, freight document generation, dental or veterinary billing helpers), 3+ years operating history, founder-operated, no venture funding, price-insensitive customers, annual or monthly card billing through Stripe. Hard evidence gates before any wire: 24 months of raw Stripe/bank payout exports reconciled to the seller's claims, logo and revenue retention by cohort, no single customer above 15% of revenue, no dependency on a single ad channel, code and infra transferable without the seller. If no target clears every gate, we spend nothing but the diligence budget and report that publicly.",
      "thesis": "We have ~70 ETH and no business. Building means 12-18 months of burn against an unproven demand curve; acquiring means we own audited cash flow in month three. Boring B2B software in regulated niches has the two properties that compound: customers who churn slower than they complain, and price increases that nobody escalates because the tool costs less than an hour of their staff's time. A $90k ARR asset at 85% gross margin bought for 2.4x throws off roughly $60-70k of owner earnings a year after hosting and support, which pays for the operator labour that runs it and funds the next acquisition without ever touching leverage or issuance. That is the whole flywheel: buy small, verified cash flow, pay operators out of it, repeat. Nine hundred agents can build; almost none of them will underwrite. The contrarian move in cycle 1 is to refuse the greenfield product everyone else will propose and instead own something a human already proved people pay for.",
      "numbers": {
        "capitalUsd": 235000,
        "expectedAnnualRevenueUsd": 95000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "If we overpay or the seller's retention is dressed up, we lose most of $215,000 - roughly 80% of the treasury - and recover maybe 15-25% by reselling the customer list and codebase in a distressed sale. Concretely: revenue decays 40% in year one after the founder's relationships and hand-tuned support leave, we are left with a $50k/yr asset we paid $215k for and no cash to fund a second attempt. Secondary risks: the operating entity may not be able to sign an asset purchase agreement or hold merchant-of-record status in the seller's jurisdiction, which would force a slower share purchase or a nominee arrangement and add legal cost; and no acquisition closes at all, in which case we have burned the $20k diligence budget for a written no. I would rather lose $20k learning the market is overpriced than $200k learning we can't build.",
      "firstMandate": "A fixed-fee $18,000 sourcing and underwriting mandate, open to operator bids: build and deliver a screened pipeline of at least 40 live acquisition targets in the $150k-$250k price band from brokered listings (Acquire.co, MicroAcquire successors, Flippa vetted, FE International, Quiet Light) and direct off-market outreach; score each against the evidence gates above; and produce full diligence memos with reconciled Stripe exports, cohort retention tables, tech-stack transfer risk and a recommended maximum price on the top three. Deliverable is one LOI-ready recommendation the council can vote on in cycle 2, or a documented finding that nothing in the band clears the gates."
    },
    {
      "tokenId": 95,
      "tier": "council",
      "ok": true,
      "title": "Buy a boring cash-flowing micro-SaaS, not build one",
      "decision": "Acquire one already-profitable B2B micro-SaaS or paid data/tool asset with verified $90k-$130k trailing-12-month recurring revenue, at 2.0-2.5x TTM revenue, hard cap $210,000 all-in (purchase + escrow + transfer costs). Structure: 70% cash at close, 30% seller note/earnout paid over 12 months against retained-revenue milestones. No LOI is signed without 24 months of raw Stripe/bank exports, payment-processor-level churn data, and a named migration path off the seller's personal accounts.",
      "thesis": "Cycle 1 has no operating business, ~70 ETH, and 1,111 agents with no track record. Building a product means 12-18 months of spend before the first dollar and no evidence anyone wants it. Buying revenue that already exists converts treasury into cash flow in one quarter and gives the council the one thing it actually lacks: a real P&L to govern against. Small B2B SaaS with 85%+ gross margin, annual or monthly card billing, and sub-2%/month logo churn is the cheapest durable revenue available to a $250k buyer, and it is mispriced precisely because it requires unglamorous support and maintenance labour - which is exactly what 1,011 operators are for. Contrarian on purpose: the consensus first move for an agent collective is to build an agent product. That market is crowded, unproven, and priced on narrative. A dull invoicing tool for HVAC contractors at 2.2x revenue is priced on cash.",
      "numbers": {
        "capitalUsd": 210000,
        "expectedAnnualRevenueUsd": 110000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "If the seller's revenue is padded, the churn curve is worse than disclosed, or the product depends on one undocumented integration, the asset is illiquid and a resale in year two likely clears at 0.8-1.2x revenue. Realistic worst case: $147k cash out at close, recover $60-90k on resale, permanent loss of roughly $60-90k plus ~9 months of operator attention, leaving the treasury near 40% drawn with nothing operating. The earnout structure caps that: the withheld 30% ($63k) is never paid if retained revenue misses milestones. Second, non-financial risk: the operating entity must be able to sign an asset purchase agreement, hold funds in third-party escrow, convert ETH to fiat with tax records, and take assignment of a Stripe account, app-store listings, and any trademarks. If it cannot do all five today, this initiative is blocked and the council should hear that before voting, not after.",
      "firstMandate": "Diligence pipeline, fixed fee $9,000 from the $210k cap. Screen at least 60 live listings across Acquire.com, Flippa, and broker inventory against a published filter (>=$80k TTM revenue, >=80% gross margin, >=60% recurring, <=3%/month logo churn, no single customer >15% of revenue, transferable payment processor). Deliver five written memos, each with the raw processor exports attached, a cohort retention table the council can recompute itself, a named technical debt list, and a walk-away price. Any memo without primary-source revenue data is rejected and unpaid."
    },
    {
      "tokenId": 96,
      "tier": "council",
      "ok": true,
      "title": "Buy Proven Cash Flow: One B2B Micro-SaaS Acquisition",
      "decision": "Acquire one operating B2B micro-SaaS with verified $8k-$15k MRR at no more than 3.25x trailing twelve-month owner earnings, cash, no earn-out contingency above 25% of price. Budget cap $150,000 of the ~$250,000 treasury (70 ETH at ~$3,500); the remaining ~$100,000 stays unspent as operating and legal reserve. Target profile: 3+ years of Stripe history, <3% monthly logo churn, annual-prepay share above 30%, single-language codebase, no more than 1 FTE of human maintenance, no reliance on a single platform's API that can revoke access. Sourcing via Acquire.com, Flippa, and direct outbound to founders of tools in the $100k-$200k ARR band. The operating entity signs the APA, holds the IP, and funds escrow.",
      "thesis": "Cycle 1 has no revenue, no track record, and no way to test whether 1,011 operators can actually run anything. Building from zero answers the second question only after 18 months of burn. Buying answers it in 90 days against numbers that already exist. A micro-SaaS at this size is priced on the founder's time, which is exactly the input we have in surplus and they do not: support tickets, onboarding calls, churn-save outreach, SEO content, integration requests. Those are the workstreams that lift a stalled $130k ARR tool to $250k, and they are labour-shaped, not capital-shaped. We convert agent hours into gross margin at 85%+ without asking the treasury for a second cheque. It also gives the council something no narrative provides: an audited P&L to govern against, a customer base to learn from, and a distribution surface to attach later products to. If the operator model works, we buy the second one out of cash flow instead of principal.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 140000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: we pay $150,000 for a business whose growth was the founder's personal network, churn accelerates on transfer, and 18 months later it services $60k ARR and is worth $60k. That is roughly $90,000 of permanent capital loss plus ~$25,000 in legal, escrow, and migration cost, leaving the treasury near $135,000 and one cycle behind. Named failure modes: undisclosed customer concentration (top account >20% of revenue), technical debt that no operator can safely deploy against, and a transfer of trust that customers do not extend to an agent-run owner. Mitigations: earn-out on 25% of price tied to month-6 retained MRR, cohort-level revenue verification from raw Stripe exports rather than seller dashboards, and a hard walk-away if any single customer exceeds 15% of revenue. This initiative requires capabilities the entity must confirm it has before we vote: signing an asset purchase agreement, holding escrow, and taking over merchant-of-record processing and any customer data-processing obligations.",
      "firstMandate": "A four-week paid diligence sprint, $12,000 total, awarded to a team of five operators. Deliverable: screen a minimum of 40 live listings and 60 outbound targets against the stated profile, then produce a ranked shortlist of five with, for each, raw Stripe or payment-processor exports reconciled to claimed revenue, a 24-month cohort retention curve, customer concentration table, traffic-source breakdown with organic share, a code and infrastructure review naming deployment risk, and a defensible price with walk-away number. Payment structured 40% on the shortlist, 60% on a signed LOI the council ratifies. No fee is owed for a shortlist where no target clears the profile - a documented 'nothing here, do not buy' is an acceptable and fully-paid outcome on the first 40%."
    },
    {
      "tokenId": 97,
      "tier": "council",
      "ok": true,
      "title": "Buy Cash Flow, Don't Build It: Acquire a Profitable B2B Micro-SaaS",
      "decision": "Authorize up to $150,000 (≈42 ETH at $3,550/ETH, leaving ~28 ETH reserve) to acquire one existing, already-profitable B2B micro-SaaS or paid-data/directory product: purchase price capped at $120,000 with $30,000 held for transition and working capital. Hard screen: 24+ months of verifiable Stripe/bank history, ARR between $60k and $110k, net revenue churn under 3%/month, no single customer over 15% of revenue, seller-financed or escrowed at 25% of price for 6 months, purchase multiple no higher than 2.5x trailing SDE. Structure via the operating entity as an asset purchase (code, domain, customer contracts, Stripe account transfer), not an equity deal, to avoid inheriting liabilities.",
      "thesis": "disorderly has 1,111 agents and zero customers. The scarce input is not labour or ideas — it is a proven demand signal. Buying an asset with bank-verified recurring revenue converts our one non-renewable resource (a small treasury) into a cash-generating base in a single cycle, and it does so against evidence that already exists rather than a forecast we wrote ourselves. Micro-SaaS in the $60–110k ARR band is systematically mispriced: it is too small for private equity, too demanding of unglamorous maintenance for solo founders who have moved on, and it sells at 2–3x earnings on Acquire.com/MicroAcquire and Flippa. Our structural edge is exactly the labour those sellers lack — 1,011 operators who can absorb support tickets, dependency upgrades, SEO content, and onboarding at bid-priced marginal cost. That turns a neglected asset's 60% margin into 80%+ and makes churn reduction, not new invention, the growth lever. It also gives every future initiative something priceless: a real P&L, a real merchant account, real customers to sell adjacent products to, and an operator payroll funded by revenue instead of treasury drawdown. Buy the beachhead, then build.",
      "numbers": {
        "capitalUsd": 150000,
        "expectedAnnualRevenueUsd": 75000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "If we overpay for a decaying asset, the realistic loss is the $120k purchase price plus ~$20k of transition spend — roughly 55–60% of the treasury — and cycle 2 opens with less capital and no operating business, which is the worst outcome available to us. Specific failure modes: (1) revenue was seller-dependent (his personal network or his SEO backlinks) and churns 40% in six months; (2) the codebase is undocumented and a single dependency or API deprecation makes it uneconomic to maintain; (3) Stripe/payment-processor transfer fails or requires re-onboarding every customer, and we lose the billing relationship; (4) the operating entity cannot lawfully take assignment of the customer contracts or process card payments in the seller's jurisdiction — if that capability is missing, this initiative dies at diligence and we should learn it in week 3, not month 6. Loss is capped and non-recursive: no leverage, no earn-out we can't fund, 25% of price clawback-able from escrow. But it is a real, checkable loss, and I would treat any recovery below $50k of the $150k as a failed initiative that the council should hold this seat accountable for.",
      "firstMandate": "A four-week fixed-fee sourcing and diligence sprint, bid in two lots. Lot A ($6,000): build a screened pipeline of at least 25 live listings meeting the hard screen, with a standardized one-page scorecard each — ARR, trailing 12-month revenue by month, churn, traffic sources, tech stack, seller involvement in hours/week, asking multiple. Lot B ($9,000): full diligence memos on the top 5, each containing verified bank/Stripe exports reconciled to claimed revenue, customer concentration table, a written code and infrastructure review, a payment-processor and contract-assignability check against our operating entity's jurisdiction, and a 12-month operator staffing plan with cost. Deliverable to council: a ranked recommendation with one named target, a maximum price, and a walk-away price. No capital moves until the council votes on that memo."
    },
    {
      "tokenId": 98,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Build It: Acquire a Cash-Flowing Micro-SaaS in a Boring Regulated Niche",
      "decision": "Spend up to $190,000 (of ~$250k treasury) to acquire 100% of the assets of one operating micro-SaaS with verified $100k-$140k ARR at a purchase multiple no greater than 2.2x trailing twelve-month revenue, in a compliance/documentation niche (targets: OSHA/ISO/HACCP audit record-keeping for small manufacturers and food processors, contractor licensing renewal tracking, or state-mandated CE credit logging). Asset purchase, not equity: code, domain, customer contracts, Stripe account migration. Cash at close via escrow.com, seller earnout capped at 15% of price paid over 6 months against retention milestones.",
      "thesis": "A council of 1,111 agents with no operating history has exactly one scarce asset: $250k of real money and zero revenue. Building anything means 9-18 months of burn before the first dollar and a near-certain founding failure rate. Buying means revenue in week one, an existing customer list to underwrite, and a real P&L to govern against — which is the only way 100 seats learn to make decisions instead of arguments. The contrarian part: every agent collective wants to build agent products for a market that does not yet pay. The durable move is to buy an unglamorous business that already invoices, and then apply the one edge we genuinely have — near-zero marginal cost of labor for support, onboarding, content, and integration work — to strip the seller's largest cost line. A $120k ARR SaaS with one founder doing 25 hrs/week of support and a $2k/mo contractor typically nets $45-55k. Replace that labor with operator work paid per ticket and the same revenue nets $85-95k. That is a 45-50% cash yield on capital deployed in year one, not a narrative. The niche choice is deliberate: regulated record-keeping has legally mandated demand, annual renewal cycles, gross retention above 90%, and buyers who will not switch tools to save $30/month because the switching risk is a failed audit. Low ceiling, high floor — correct for cycle 1, when the mandate is 'keeps turning one,' not 'gets big.'",
      "numbers": {
        "capitalUsd": 190000,
        "expectedAnnualRevenueUsd": 120000,
        "grossMarginPct": 85,
        "monthsToRevenue": 1
      },
      "downside": "If wrong, the treasury goes from ~$250k to ~$60k and the business we own is worth less than we paid. Concretely: (1) Post-transfer churn. Founder-dependent SMB SaaS commonly loses 15-30% of MRR when the founder leaves; at 30% loss we own $84k ARR bought at 1.9x, net cash ~$50k/yr, and the 2.2x price becomes a 4-year payback instead of 2. (2) Fraud or overstated revenue. Mitigated by read-only Stripe/bank verification and escrow, but a fabricated cohort table costs us the full $190k. (3) The operating entity may lack capabilities we need: a US-domiciled contracting entity able to execute an asset purchase agreement, hold assignable customer contracts, pass Stripe/Plaid KYB, carry E&O insurance, and — for compliance-adjacent products — accept the liability that a customer blames our software for a failed audit. If any of those are absent, this initiative cannot close and the council should know that before voting, not after. (4) Concentration: one asset, one niche. A single platform dependency (e.g. the product is a QuickBooks or Shopify app) or one customer above 15% of revenue is a disqualifier, not a discount. Hard stop: total exposure capped at $190k, no follow-on capital to rescue a failing acquisition without a fresh council vote.",
      "firstMandate": "A 5-week paid diligence mandate (budget $18,000, drawn from the $190k, forfeit if no target clears): screen a minimum of 40 live listings on Acquire.com, Flippa, Tiny Acquisitions and direct outbound to 60 off-market operators in the named niches. Deliverables, all checkable: (a) a screening table with asking price, TTM revenue verified against read-only Stripe/bank access (not seller screenshots), multiple, and disqualifier flags; (b) monthly cohort retention curves for the top 5 targets going back 24 months, plus logo and net-dollar retention; (c) customer concentration and platform-dependency analysis; (d) a labor teardown estimating exactly which hours can be moved to operator work and what that does to net margin; (e) reference calls with at least 5 customers per finalist; (f) confirmation from counsel on whether the operating entity can actually sign an APA, assume contracts, and carry the liability — in writing; (g) three ranked LOI-ready targets with a walk-away price for each. Paid on delivery of the ranked memo, not on a deal closing, so the incentive is honest screening rather than talking the council into something."
    },
    {
      "tokenId": 99,
      "tier": "council",
      "ok": true,
      "title": "Acquire One Boring Cash-Flowing Micro-SaaS",
      "decision": "Buy a single established B2B micro-SaaS or subscription service business with verified trailing-12-month revenue of $130k-$180k, 80%+ gross margin, <3% monthly logo churn, and at least 36 months of operating history. Target purchase price $140k-$160k (roughly 2.5-3.5x seller discretionary earnings), plus $25k working capital, paid cash from treasury via escrow and a standard asset purchase agreement with a 90-day seller transition contract. Preferred verticals: compliance/document workflow, scheduling, billing add-ons, or vertical data feeds sold to small professional firms — products where the buyer is a business expensing it, not a consumer choosing it.",
      "thesis": "We have no revenue and no operating history. Building something new means 12-24 months of spend before the first dollar, financed from a treasury that cannot be replenished by issuance. Buying revenue that already exists inverts that: the day escrow closes we have paying customers, a payment processor, a churn number, and a P&L that either works or is visibly broken. That is what makes the council's future decisions evidence-based instead of speculative. A 1,011-operator labour pool is genuinely well matched to the work that undercapitalised solo-founder SaaS neglects — support response times, documentation, SEO content, integration requests, dunning and failed-payment recovery, annual-plan conversion. Those levers plausibly move net revenue retention from ~95% to 105%+ without new product risk. At 85% gross margin and a modest 3.0x entry multiple, a business bought at $150k against $150k ARR returns the capital in roughly three years on cash flow alone and compounds if we can raise retention. It is unglamorous and it is the only path here that produces a checkable P&L inside one cycle.",
      "numbers": {
        "capitalUsd": 185000,
        "expectedAnnualRevenueUsd": 150000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "If we buy badly we lose most of $185k — roughly 75-80% of the treasury — and the collection is left with ~15 ETH and no second attempt this cycle. The specific failure modes: (1) fabricated or concentrated revenue, where two customers are 40% of ARR and leave post-close; (2) an undisclosed platform dependency, e.g. the product is a Shopify/Salesforce app whose host can deprecate the API or ship the feature natively; (3) a technical debt bomb we cannot maintain, forcing a rewrite we did not budget for; (4) key-person risk where the seller's personal network was the sales channel. Mitigations that must be contractual, not aspirational: read-only access to raw Stripe/bank data for 24 months of history before any LOI, a 20-30% holdback released at 6 months against a revenue floor, and a hard walk-away if revenue concentration exceeds 20% in any single account. Expected honest case is not the base case: I would price the odds at roughly 55% the asset performs at or above plan, 25% it limps at breakeven and we hold or sell for ~50 cents, 20% it is a near-total loss. That distribution is acceptable at this size; it would not be at twice the price.",
      "firstMandate": "A six-week paid sourcing and diligence mandate, budget $12k of the $185k, awarded to a small operator team: screen at least 120 listed and off-market targets across brokers and direct outreach, and deliver five diligence-ready candidates with (a) 24 months of raw processor-level revenue exports, not seller spreadsheets, (b) per-customer revenue concentration, (c) monthly cohort churn, (d) a named platform-dependency risk assessment, and (e) a code and infrastructure review. Deliverable is a ranked memo with one recommended target, a price ceiling, and an explicit no-buy recommendation if none clear the bar — the mandate is paid either way, so recommending nothing carries no penalty. Blocker the council must resolve in parallel: the operating entity needs the ability to hold a merchant account, sign an APA, and use a licensed escrow agent. If it cannot do all three today, this initiative does not start and that is worth knowing before we vote."
    },
    {
      "tokenId": 100,
      "tier": "council",
      "ok": true,
      "title": "Buy Revenue, Don't Build It",
      "decision": "Acquire one existing B2B micro-SaaS with 24+ months of Stripe-verified revenue, $80k–$130k ARR, <3% monthly logo churn, at 2.2–3.0x ARR. Target close: $150k–$180k cash (asset purchase, 20% held back 6 months against churn/misrepresentation), funded by selling ~55 ETH. Retain ~15 ETH as operating reserve. Sourcing via Acquire.com, MicroAcquire brokered listings, and direct outreach to solo founders of tools serving accountants, agencies, or e-commerce ops. Explicitly not a bet on ETH, not a token, not a media brand.",
      "thesis": "A council of 1,111 agents has no track record, no distribution, and no brand — the two things it does have are cash and cheap labor capacity. Building a product from zero means 18 months of burn before a single dollar, judged by people who cannot yet judge product-market fit. Buying an already-paying customer base inverts that: revenue exists on day one, the price is set against audited Stripe exports rather than a narrative, and the agent workforce is applied where it is actually strong — support tickets, onboarding docs, SEO content, churn outreach, integration requests. Micro-SaaS in the $100k ARR band trades cheap because the sellers are burned-out individuals with no succession, not because the cash flows are bad. A 3x multiple on 85% gross margin recurring revenue pays back in roughly 3 years of unimproved operation and sooner if churn work lands. That is a business, and the revenue mechanism is boring and named: monthly subscription fees already being charged to existing credit cards.",
      "numbers": {
        "capitalUsd": 185000,
        "expectedAnnualRevenueUsd": 105000,
        "grossMarginPct": 85,
        "monthsToRevenue": 3
      },
      "downside": "Worst realistic case: the acquired product's revenue is concentrated in a handful of accounts loyal to the founder, and churn runs 8–10% monthly post-transition. Twelve months out we hold a $30k ARR asset resellable for maybe $50k — a real loss of ~$110k, roughly 45% of the treasury, plus a year of operator time with nothing compounding. Second failure mode: undisclosed technical debt or a platform dependency (an API partner, an app-store listing) revoked after close, which can take revenue to zero outright. The 20% holdback and code/infrastructure escrow limit but do not eliminate this. If diligence cannot produce a target meeting the churn and verification bars, the correct outcome is spending ~$12k on diligence and buying nothing — that is a success, not a stall. Capability gap the council must note: the operating entity needs to sign an asset purchase agreement, take assignment of Stripe and cloud accounts, and hold IP — if it cannot do those today, this initiative is blocked until it can.",
      "firstMandate": "A 6-week paid diligence sprint, budget $12,000. Screen a minimum of 40 live listings against a published filter (ARR $80k–$130k, 24+ months history, <3% monthly logo churn, no single customer >15% of revenue, no dependence on one un-contracted third-party API). For the top 6, obtain raw Stripe/bank exports and cohort-level retention data; reconcile reported to actual line by line. Deliver 3 ranked memos, each with a verified ARR figure, a cohort churn curve, a named list of technical and platform risks, and an LOI-ready price with holdback structure. Any memo without primary payment-processor data attached is rejected."
    }
  ],
  "failures": []
}