Founder toolsIn development

Launching OS

Tell a founder what to do next, what evidence they are missing, and how to become more fundable.

Role
Founder. Product, design and build.
Team
Solo
Timeline
2026
Stack
Next.js 15, TypeScript, Tailwind, Supabase (Postgres, Auth, RLS), an OpenAI-compatible API with a deterministic grounded fallback, Vercel
Year
2026
In development
founder workspaces with readiness scoring, an evidence vault and a track record
Status, not a metric
0 moves
of data between products without the founder’s own action
Design rule

The problem

Early-stage founders keep their company in decks, documents and their heads. When a mentor program or an investor asks how ready they are, there is no evidence-backed answer and no clear next step.

Launching OS gives the founder a private workspace: a venture profile, a launch plan of milestones and tasks, an evidence vault, a narrative studio, a fundability assessment scored by dimension, and an investor target list.

Key decisions

Constraint

Advice from a model is only useful to a founder if the reasoning is visible.

Options

A free-form chat, or structured outputs grounded in the workspace.

Decision

A copilot that drafts and analyzes only from workspace context, with a deterministic fallback when no model is available, so every recommendation shows the evidence it rests on.

Trade-off

Less magic in the demo. More trust from the person whose company it is.

Constraint

Founders arrive by referral from mentor programs, and those programs promise that only their own team sees an application.

Options

Shared accounts, an API sync, or link-out only.

Decision

Link-out only between Launching OS, Mentor Intelligence and the founder tools. A referral is an email the staff member sends; nothing moves without the founder’s own action.

Trade-off

No automatic hand-off. In return, a privacy promise that program staff can repeat word for word.

The work

launchingos.com
Launching OS welcome screen with a readiness score of 69 out of 100 for a demo venture
The welcome screenA readiness score worked out by fixed rules, the areas that moved it, and the evidence behind it. Demo venture.
Launching OS dashboard for the demo venture Kettlewick
The dashboardReadiness level, fundraising target and open tasks, why the score changed, and the top gaps to close. Demo venture.
launchingos.com
Launching OS readiness page with a level for each area
ReadinessA level for each area, what it is backed by, and what the next level needs. The weakest area sets the overall level. Demo venture.
launchingos.com
Launching OS evidence vault with approved notes
The evidence vaultInterview notes, letters, usage numbers and files, each approved before it counts toward the score. Demo venture.
launchingos.com
Launching OS track record with dated check-ins
The track recordA dated record of what the venture has done and who recorded it, ready for a re-application or an investor meeting. Demo venture.
launchingos.com
Launching OS about page explaining who it is for and what it does
The about pageWho it is for, and the four things it does, in plain language.

How it was built

  1. 01DiscoverCalls and walk-throughs with the people who would use it
  2. 02CompileTranscripts, files and constraints in one requirements brief
  3. 03SpecifyA detailed, sourced spec from Perplexity, reviewed and locked
  4. 04BuildDesigned and built with the latest AI models, in the production stack
  5. 05TestUser testing on every preview, with real users on real tasks
  6. 06IterateFindings turned into the next round of changes, worst problems first
  7. 07ShipTests, security review and release, then back to testing and iterating↻ Back to Test
How I work, step by step →

Where AI was used

Copilot drafting and analysis through an OpenAI-compatible API, grounded in the workspace; a deterministic fallback keeps the product usable with no model at all.

What’s next

Integration-ready links to Global Funding Studio, so an onboarded venture gets investor and program suggestions with reasons.