Skip to main content
Co-Build TableA FIN GROUP mission

The framework

Four tracks, one outcome, two hours

Everyone at the table is working a different thing. What keeps it from becoming a coffee chat is a shared structure: you pick a track, you declare one outcome, and you report back before you leave.

Track 01 · Career

Job and career track

  • Determining career, business, or side hustle options based on your situation
  • Resume, portfolio, LinkedIn, certifications
  • Target list, outreach messages, follow-ups
  • Interview prep and salary research

Track 02 · Model

Business model and plan

  • Customer definition, offer, and pricing
  • Business plan sections and financial assumptions
  • Revenue model, costs, and break-even math

Track 03 · Build

Scale, apps, services, products

  • Prototypes, app builds, and tooling
  • Testing with real users and iterating
  • Launch checklist, timeline, and first customers

Track 04 · Market

Website, brand and marketing

  • Name, positioning, and message
  • Website copy and landing pages
  • Email list, social, and first campaign

Worked example

What the tracks look like in practice — FIN Group

Abstract frameworks stall. So sessions use a real one Cory built: a consulting practice that turned into three software ventures. Each piece below is a template you can fill in for your own idea.

Business model

Who pays, for what, how often

FIN Group started as compliance consulting for investment firms — a defined customer (RIAs and broker-dealers), a recurring retainer, and a clear reason to renew. At the table you write your version: one customer, one offer, one pricing line.

Service

A repeatable engagement, not custom every time

Annual reviews, filings, and mock audits became a standard scope with a standard checklist. Turning your service into a repeatable package is a single session's outcome.

Product

The service that became software

Reg Review packaged the same compliance calendar the consulting team ran by hand. The pattern to copy: find the task you repeat for every client, then productize that one task first.

Marketing strategy

Narrow audience, plain language, one channel

Speak to a niche you already know, name the pain in their words, and pick one channel you'll actually keep up — a site page, an email list, or a referral loop. Write the landing page before you build the thing.

App concept

Scope it to one job the user hates

AD Scanner does one job: check an ad against the rules in seconds. Invest Prep does one job: fund reporting without five vendors. Write your app as a single sentence in that shape, then prototype it in a session.

The two hours

What a session actually looks like

  1. Step 1

    First 20 minutes

    Arrive and set one outcome

    Coffee, seats, and a quick round the table. Each person names the single thing that will be finished by the end of the block. Not a goal — an outcome someone else could verify.

  2. Step 2

    Middle 90 minutes

    Ninety minutes of build time

    Heads down, side by side. Quiet by default, with a designated corner for the conversation you need to have — a second opinion on pricing, a pass over your resume, a sanity check on scope.

  3. Step 3

    Last 10 minutes

    Share-out and next commitment

    What moved, what stalled, and the one thing you'll bring to the next session. Stuck counts as an answer — that's how the group knows where to help.

Ground rules

How we keep the table useful

One outcome, out loud

Vague intentions stay vague. Saying the outcome to four other people is most of the work.

No pitching, no selling

This is a build group, not a lead list. Help freely; keep your offers for a different room.

Progress over polish

A rough draft that exists beats a perfect plan that doesn't. Ship the increment.
See session details