EC Founder OS · Internal — what we're building

One operating system for every founder we serve

A founder tells us everything when they apply and onboard — their goals, their gaps, their capital picture, the advisor they wish they had. Today that intelligence sits in forms. The Founder OS activates it: every answer a founder gives us becomes capital matched, curriculum shaped, advisors paired, and progress tracked.

Cohort: Fall 2026 (data complete, 8/24)  ·  Spine: ClickUp  ·  Approved: Dakota, 7/24  ·  Access: @ec.co staff only

The idea in one paragraph

This started with the Turner call (VelocityTX, July 22): one programs coordinator, no coding background, built a founder CRM + funding matcher that runs his whole portfolio. Our version is bigger because our data is bigger — 122 companies this fall, every onboarding record joined to its full application. The principle came out of that call and hasn't changed: don't let founder information sit static on a form. Activate it. A founder should never tell us something twice, and nothing a founder tells us should fail to come back to them as help.

The trade every founder makes

What they give us (already collected)

  • 6–12 month goals, why now, the key question they need answered
  • Capital picture — raised, revenue, MRR, what they're seeking
  • Top challenges + the support they want
  • The advisor they wish they had, in their own words
  • Topics & speakers they want; skills they can teach others
  • Stage, team, customers, hours-per-week

What the OS gives back

  • A ranked capital shortlist they actually qualify for
  • A goal record staff work against all cohort long
  • Sessions built from what the room said it needs
  • An advisor cabinet matched to their stated gap
  • Peer connections from skills-to-share overlaps
  • A progress story we can tell at graduation

The raw material — already in hand

122
Fall 2026 companies — TakeOff 67 · InFlight 24 · Project Healthcare 17 · PreFlight 14
122/122
onboarding records joined to their full application — the complete picture per founder
190
advisors on the roster — 96% carry expertise tags (77-tag taxonomy, avg 12 tags each)
44
deferred applicants = the Spring 2027 pipeline, already identified

The four systems

1

Capital

Match every founder to money they qualify for
Proven on 2025 data

The matcher tests each founder against every funding source's real rules — identity eligibility, revenue floors and ceilings, business age, geography — and produces a ranked shortlist. Anything it can't verify goes to a human, never asserted. Proof run on the 2025 Spring cohort: 44 of 90 founders had an actionable best-fit grant, ~3 each. Dakota approved.

Runs on

  • 62-grant internal database (identity + eligibility structured)
  • Per-founder capital block: raised, revenue, MRR, seeking 122/122
  • Demographics, purpose-bound to eligibility only

Where it goes

  • Fall run as cohort opens — matches land in ClickUp for staff to work
  • Investor-shaped next: most of our founders seek angel/VC, not grants — an angel/VC source database is the v2 unlock
  • Project Healthcare federal-grant scraper (that vertical is grant-shaped)
2

Goals

What each founder came here to do — tracked, not filed
Designed — new scope

Every application answers five questions we currently read once and never look at again: 6–12 month goals · why now · problem evidence · support areas · the key question they need answered. The OS turns that into a living goal record on each founder — visible to staff, referenced at check-ins, measured at midpoint and graduation. "Did we answer their key question?" becomes a reportable number.

Runs on

  • application.goals — filled at intake 122/122
  • Stage ladder (6 levels) + product readiness + customer status
  • Engagement log entries as evidence of progress

Where it goes

  • Per-founder goal card in the OS founder record
  • Midpoint + final survey answers land next to the original goal
  • Graduation: a founder-facing progress story, drafted from the record
3

Curriculum

Teach what the room actually asked for
Designed — new scope

Founders told us their top challenges, the topics and speakers they want, and — the underused half — the skills they're willing to teach each other. Aggregated across a cohort, that's a session plan: the challenge clusters say what to program, the speaker asks say who to invite, and skills-to-share turns 122 companies into faculty for each other. Programming stops being a best guess.

Runs on

  • cohort_inputs: challenges, support wanted, topics & speakers onboarding
  • skills_to_share + industry expertise per founder
  • Peer-group and book-club opt-ins

Where it goes

  • Cohort-level "what this room needs" view for Dakota's team, per program
  • Founder-teaches-founder slots surfaced from the overlap
  • Next cycle: compare what we programmed vs. what was asked
4

Advisors

The right cabinet around every founder
In build — with Amy

Two sides, both already structured. Founders state the advisor they wish they had, in their own words. The roster answers with 190 advisors, 96% tagged across a 77-skill taxonomy, self-sorted into three seat types — subject-matter expert, industry expert, been-there entrepreneur — with real capacity history (who's been asked, who said yes, who's tapped out). The matcher assembles a cabinet per founder instead of the same twelve names getting every call.

Runs on

  • Advisor roster w/ expertise tags, seat types, narratives 183/190 tagged
  • cohort_inputs.advisor_wanted — the founder's own ask
  • Capacity signals: prior asks, responses, oversaturation status

Where it goes

  • Proposed cabinet per founder; Amy confirms — judgment stays human
  • Load-balancing so the generous few stop absorbing every ask
  • Pairings recorded in ClickUp → next cycle learns from this one

How it holds together

Founder tells us once
application + onboarding — already collected, 122/122 joined
ClickUp — the system of record
where the team edits, independently, no dev in the loop
↓ ↑
Founder OS — the experience layer
founder record · capital shortlist · goal card · cohort curriculum view · advisor cabinet · engagement log

The OS reads and writes ClickUp; it never becomes a second source of truth. Machine fields are Claude's; staff status and notes are never overwritten. If the OS breaks, the data is safe and editable where it always was.

The flywheel — what compounds

Every touchpoint logs itself

Engagements recorded at the moment they happen rebuild "founders served," jobs, and capital numbers for the annual report and funders — with zero year-end reconstruction. The reporting is a byproduct, not a project.

Every cohort teaches the next

44 deferred applicants are already a named Spring 2027 pipeline. Advisor pairings, goal outcomes, and curriculum asks all persist — so next fall starts from evidence, not memory.

The rules that hold regardless

Non-negotiables

  • Nothing in this dataset is publishable. Revenue, capital, team size, demographics, goals — internal, used to serve the founder. The public directory is a separate, consent-gated pipeline.
  • Demographics are purpose-bound to identity-grant eligibility. Never surfaced in an interface, export, or summary.
  • Application ≠ consent. The 140 not-enrolled applicants signed nothing about media or promotion.
  • Real founder data never enters the code repo. App shell only; live data reaches the OS at runtime, behind @ec.co login (Cloudflare Access).
  • Every automated output is advisory. Scores prep humans, matches propose, staff decide. Nothing auto-contacts a founder.
  • Numbers are founder-stated, not verified. Treat them as testimony, not audit.

Where the build stands

PieceStateNext step
Fall 2026 datasetComplete — 122 companies, apps joined, refreshable from ClickUpStays current via one-command refresh
Capital matcherProven on 2025 cohort; Dakota approvedRun against Fall 2026; write matches to ClickUp
Advisor matcherData validated both sides; build session with AmyBlind-test against Amy's answer-key cabinets
Goals systemData in hand (122/122) — new scope, needs design sign-offDefine the goal card + midpoint/final check-in flow
Curriculum viewData in hand — new scope, needs design sign-offCluster fall challenges/topics into a per-program readout
OS interfaceWorking prototype (anonymized data), @ec.co gating speccedWire to live ClickUp behind Cloudflare Access
Field cleanupChecklist with DakotaGate for wiring the OS to live data

Open questions — the gaps to check

Does this cover everything? Read against your goals:

  1. Goals & Curriculum are new scope — they were not in the approved v1 (dashboard + record + matcher). Confirm they're in, and whether they're fall features or built during fall for spring.
  2. Who owns each system day-to-day? Capital and curriculum look like Dakota's team; advisors is Amy; goals needs an owner for the check-in cadence.
  3. Investor matching: most fall founders seek angel/VC. The grant matcher is proven, but the investor-side source database doesn't exist yet. In scope for fall, or spring?
  4. Founder-facing or staff-only? Everything above is staff-facing. Does any slice (their own goal card? their capital shortlist?) ever get shown to the founder directly — and if so, that's a consent + design decision to make deliberately.
  5. PreFlight's fit: 14 idea-stage companies with thinner records — do all four systems apply to them, or a lighter version?