The Founder Suite — A One-Person Company as Six Skills

Six skills, five sharing the founder- prefix, one called idea-refine. Together they cover plan, brand, competitors, launch, and operations — the full cycle of a company run by one person. The cluster scores 9.1 across the board. What does it mean when the entire operating system of a solo business fits in six skills?

There's a genre of "start a startup with AI" content that is mostly vibes: one-shot prompts for a landing page, a name, a logo. The founder suite in our directory is the opposite of that genre. It's six narrow skills, each mapped to a distinct phase of a company's life, none of them pretending the phases collapse into one conversation.

The suite, phase by phase

• idea-refine — 9.1: pressure-test the idea before anything exists — target user, wedge, the reason this survives contact with reality.
• founder-plan — 9.2: the plan itself — scope, sequencing, milestones, the definition of "shipped."
• founder-brand — 9.1: identity — positioning, voice, the promise the product makes.
• founder-competitors — 9.1: the landscape — who else is doing this, where the gap actually is.
• founder-launch — 9.1: shipping — launch sequence, channels, the first-hundred-users problem.
• founder-ops — 9.1: the boring permanence — operations, billing, support, the things that keep a company alive after launch.

The scores are almost suspiciously uniform — 9.1 everywhere, 9.2 at the top. Read the six-dimension breakdowns and the uniformity makes sense: no skill in the suite overreaches. Each has a phase-shaped job, a phase-shaped procedure, and a phase-shaped definition of done. Uniform scores in a family usually mean the author understood the boundaries before writing — they drew the org chart first, then wrote one skill per role.

The company as a pipeline, not a person

What strikes us most about the suite is what it reveals structurally. A one-person company has always had these six functions — the founder just performed all of them badly by switching contexts hour to hour. The suite makes the functions explicit and separable: idea-refine argues with you, founder-competitors looks outward, founder-ops looks at what already broke.

That separation is the actual product. When planning and competitor analysis are different skills, the agent running them can't silently blur "what we'll do" into "what the market wants" — the phase boundary is enforced by the tooling, not by discipline you don't have at 11pm.

The part humans still own

To be clear about what six skills at 9.1 do not give you: judgment under skin-in-the-game. founder-plan can sequence a roadmap; it can't want the roadmap to exist at 4 a.m. for a year. idea-refine can find the weakest assumption in your idea; only you can decide whether the weak assumption is the point — some businesses are built exactly on the conviction everyone else rates as naive.

The suite's real user, then, isn't a replacement founder. It's a serial builder who wants the mechanical 70% of company operations — the checklists, the sequences, the "did you actually look at your competitors before pricing" hygiene — to stop consuming the mental budget that the irreplaceable 30% needs.

One-suite pattern worth copying

The founder suite is also, quietly, a template for skill authors: pick a lifecycle, not a task. Five of these skills would score fine alone; six in a pipeline score 9.1 and become infrastructure. Authors of single mega-skills covering "do a startup" get worse results than this author got by refusing to.

A company used to be people. Then it was people plus process. A one-person company in 2026 is one person, six skills, and a phase boundary between each — drawn where the org chart used to be.