FablePool: Public AI Crowdfunding as Infrastructure

An investment memo on why decentralized, transparent software funding powered by AI agents could redefine open-source economics.

What FablePool Actually Is

FablePool is a marketplace where anyone can pool capital behind a software idea, and Claude Fable builds the project in public. Users collectively fund a bounty. Backers watch the project materialize through daily commits, livestreams, and decision-logs. Fable executes the build autonomously, asking for guidance when blockers arise. If the project ships, backers gain early access, board seat, or equity stake (depending on tier). If it fails, the ledger stays public. No hidden sunk costs. No developer radio silence.

This is not GitHub Sponsors crossed with Kickstarter. It is something distinct: a marketplace that uses AI agency to make the build process itself transparent and investors can follow and influence the software creation in real time.

Why This Is Interesting

Three structural reasons:

Inverts information asymmetry. In traditional venture, investors bet on a founder's pitch and then wait 18 months to see if code exists. Here, the code is visible daily. Backers see velocity, taste of architecture, handling of scope creep, and pivot decisions live. Risk pricing becomes real, not speculative.
Unbundles software funding from venture risk. A $5K project run by Fable doesn't need a $2M raise. Users who want a small tool can fund it directly. Removes the pressure to bleed into enterprise or IPO. Some software can profitably stay small.
Creates new psychology of ownership. Backers aren't customers yet; they're co-investors in the process. They have skin in the game. When the project ships, they're not finding a new tool; they're seeing their own capital and patience rewarded. Retention, pricing power, and community all shift upward.

Why the Landing Page Cannot Capture This

The FablePool MVP homepage shows the concept, the gallery of projects, the pricing tier. What it does not show:

The economics of a single $10K project from funding close to ship (unit economics, runway math)
How Fable handles scope scope creep when a backer asks for a feature
What happens if the core architecture hits an unexpected limitation at week 3
The psychology of being a backer watching daily builds (is the transparency calming or anxiety-inducing?)
Competitive response: will GitHub, Stripe, or Patreon build something like this first?
Regulatory: if money is pooled, are backers securities holders?

These questions require depth. A concept essay allows us to think through them seriously instead of dodging them in marketing copy.

The Realistic Product Shape (Year 1 to 18 Months)

Months 1-3: Founder Validation. Launch with 20 small projects ($2K-$10K bounties). Use Wes's network to recruit first founders who are already willing to build in public. Measure: backer retention, project completion rate, cost per ship.

Months 4-6: Expand Tiers. Add a Team tier (agencies, studios pooling projects internally). Add a fund-raising tier (projects that target $50K+). Introduce a Fable+Human hybrid (Fable drives, founder supervises). Launch backer dashboard showing real-time P&L on their pooled capital.

Months 7-12: Go to Market or Pivot. Two paths:

Path A (Marketplace Play): Raise a larger round ($2M-$5M). Build for teams and agencies. Position as a "bring-your-own-fable" platform where any org can launch public builds internally or client-facing. Sell enterprise pricing (white-label, custom terms). Compete with Stripe, Anvil, Zapier.
Path B (SaaS Pivot): If marketplace unit economics are brutal, pivot to a smaller TAM. Become software-building-as-a-service for non-technical founders. Charge per project, remove the crowdfunding element, and focus on execution quality and speed. Compete with Bubble, no-code platforms, offshore dev.

The decision hinges on whether unit economics support take-rate at marketplace scale or if margin is only achievable through direct-service models.

Who Builds This and Why

Candidate A: Wes + a full-stack founder (1-2 years runway). Lean team. High execution risk, high optionality. Better for Path B pivot. Wes's credibility on Claude Fable, his Sales Connector playbook, and his network unlock founder recruitment. A seasoned co-founder handles product, ops, fundraising.

Candidate B: Early-stage venture studio or CLI tools team. They have fundraising infrastructure and belief in AI-native tools. They understand the technical requirements (build orchestration, logging, payment splitting). Lower execution risk, higher capital intensity. Better for Path A (marketplace at scale).

Candidate C: Anthropic or Claude ecosystem play. Claude Fable is the core engine. FablePool becomes the canonical use-case and revenue driver. Anthropic gets the data on how Fable performs across 100+ small projects and the narrative of the AI agent as a reliable builder, not just a chatbot.

Most likely: Candidate A or B. Candidate C would require internal prioritization that may not exist yet. FablePool is best positioned as a founder-led experiment that proves or disproves the market hypothesis, then either scales within a larger company or stands alone if unit economics work.

An Honest 12-Month Case

Revenue scenario (bullish): 15 projects funded, $8K average pool, 5% take-rate, $6K total revenue. Runway for founder: ~1 month at $6K. Unsustainable. Requires either larger pools (proving backer confidence) or more volume (proving marketplace fit).

Revenue scenario (realistic): 30 projects, $3K average (more small bets), 8% take-rate (less competition for growth), $7.2K revenue. Same problem: does not support payroll. The marketplace thesis requires either 10X volume, 3X pool size, or 15% take-rate. None are given.

The insight: FablePool cannot bootstrap from transaction fees alone. It requires either VC capital (Path A) or a freemium or hybrid model (Path B, where the founder makes money on implementation services, not marketplace take). The marketplace *economics* are secondary to the psychological and logistical proof. The real question is: will founders use it? Will backers return? Unit economics come after product-market fit, not before.

Five Questions Wes Should Answer Before Full Commitment

1. Is the transparency actually a feature or a liability? Backers may love seeing the build but hate watching failed attempts or architectural pivots. Will daily transparency drive higher retention or churn? Test with the first 5 projects before scaling.

2. What does a refund look like? If the project fails mid-build, do backers get capital back, or a credit toward the next project, or nothing? This policy will set the risk-taking tone of the entire platform.

3. Can you acquire founders faster than you lose them? Do you have 50 ideas ready to fund in month 1, or will you launch with 5 and pray more come? Founder liquidity is the constraint, not capital.

4. What is Fable's success rate on new categories? FablePool works if Fable can handle diverse codebases (frontend SPA, backend CLI, data pipeline, mobile app). Test this with 3 fundamentally different project types before you market FablePool as a general platform.

5. Is this better than hiring a contractor? A founder can hire a $5K developer on Upwork for 2 weeks. Why would they instead pool capital, invite 20 strangers, and live-stream the sausage-making? The psychological or financial advantage must be crystal clear, or FablePool is a curiosity, not a business.

Closing Frame

FablePool is not a technology product; it is a market hypothesis wrapped in an AI agent and a payment processor. The technology (Claude Fable) is the easy part. The market (will founders and backers show up) is the question. This essay argues it is worth exploring seriously because the structural dynamics (transparency, decentralized funding, AI-driven execution) are novel enough to attract early adopters and bold enough to reshape how software gets built.

The next step is not to raise $5M. It is to launch with 20 projects, measure completion rate and backer repeat rate, and let the data decide the strategy (marketplace scale vs. SaaS pivot vs. sunsetting). That experiment costs <$100K and clarifies everything.