FB Founder Board
AI-native founders Real-world collaborators Equity-first

Find the human your AI-coded startup is missing.

A job-posting board for founders who can ship with agents, but need people for judgment, field testing, design taste, sales, operations, trust, and domain context.

These are not normal salary postings. They are collaboration asks for builders who want documented ownership upside, clear project scope, visible founder accountability, and a useful way for agents to read, filter, and summarize opportunities.

View pilot board Submit a listing Open JSON Agent map
Compensation
Equity or revenue share, not salary by default
Best-fit founders
AI-coding solo founders with real user validation needs
Agent surface
HTML, JSON feed, agent rules, and llms.txt
Important boundary

This pilot treats postings as founder collaboration opportunities, not guaranteed employment offers. Equity, vesting, advisor shares, revenue share, and IP terms must be documented before work starts.

Open collaboration postings.

The current local MVP uses sample seed listings so the product flow, filters, metadata, and agent feeds can be reviewed before production launch. Replace these with approved founder submissions before public promotion.

3 pilot listings Use structured feed
Pilot listing 001 Pilot

Product operator for an AI invoice review tool

A solo founder has a working AI-coded prototype that extracts invoice anomalies and contract mismatches. The missing human is an operator who can test real procurement workflows, interview users, and turn rough agent output into trusted review steps.

Ideal collaborator
Operations, procurement, AP, QA, or workflow documentation
AI stack
Cursor, Claude/Codex-style coding agents, OCR, spreadsheet export
Compensation
No salary. Proposed 2-5% equity after scope and vesting terms are documented.
Commitment
6-8 hours weekly for a 4-week operator sprint
Human QA B2B ops Workflow testing
Apply or request intro
Pilot listing 002 Prototype

Design partner for a local services estimator

The founder can build the estimation engine with AI, but the app still feels like a prototype. They need a collaborator who can make quoting, scope review, and customer trust feel believable to local contractors and service-business owners.

Ideal collaborator
Product design, service business ops, sales enablement, or UX writing
AI stack
Next.js prototype, agent-written copy, pricing rules, CRM export
Compensation
No salary. Proposed 1-3% equity or milestone revenue share after written terms.
Commitment
Two review calls weekly plus async design and copy feedback
Design taste Local business Trust layer
Apply or request intro
Pilot listing 003 Customer discovery

Domain collaborator for an automotive service copilot

An AI-coded service advisor copilot needs reality checks from people who understand shop flow, technician notes, customer explanation, and what should never be automated without human review.

Ideal collaborator
Service advisor, apprentice tech, shop coordinator, or dealership operator
AI stack
Static prototype, note summarization, checklist flows, agent-safe exports
Compensation
No salary. Proposed advisor equity or revenue share only after role scope is written.
Commitment
3 structured workflow reviews and one written product teardown
Automotive Service lane Safety review
Apply or request intro
Founder intake

Post a collaboration ask that agents and humans can trust.

Good listings state the actual project, the human skill gap, the current traction, the time ask, the compensation boundary, and the documentation plan. Vague "cofounder wanted" posts do not belong here.

1. Project truth What exists today, who needs it, and what proof you have.
2. Human gap The judgment, domain access, sales motion, or taste AI cannot supply.
3. Terms boundary Cash salary yes/no, equity range, vesting intent, and IP ownership plan.
4. Safe next step Intro call, trial sprint, written scope, and how applications are handled.
Submit listing by email

Agent access is part of the product.

The board is built so AI assistants can fetch listings, respect compensation boundaries, compare opportunities, and draft outreach without inventing salary, traction, or legal terms.

Endpoint

Structured listings

Use postings.json for normalized fields like stage, equity range, salary boundary, AI stack, collaborator profile, and application route.

Endpoint

Agent rules

Use agents.json for allowed actions, field meanings, attribution rules, and what an assistant must not infer from a listing.

Endpoint

LLM map

Use llms.txt for the site-level summary, canonical routes, contact boundary, and machine-consumption notes.