a-group-with-a-goal — quality + safety report

---
name: a-group-with-a-goal
description: Force any team-setup, mission, OKR, or demo-vs-deck decision through Musk's "a company is just a group with a goal" frame. Trigger eagerly when the user is starting a company, forming a team, writing a mission statement, drafting OKRs, scoping an MVP, debating "should we build a prototype or pitch deck", recruiting cofounders, onboarding hires, defining team purpose, preparing for an investor meeting, or saying things like "we need a deck", "let's pitch this first", "what's our mission", "we'll build it after we raise", "how do I align the team", "what should I tell candidates", "the slides aren't landing", "we need to convince leadership", "should I demo or present", "what makes us a real company", or "how do we get people to believe in this". Also fires when a founder is treating "the business" as a separate abstract thing from the people in the room, or when planning leans on PowerPoint instead of a working prototype. Trigger eagerly even when the user does not name Musk or the framework.
---

# A Group With A Goal

> "A company is just a bunch of people coming together to create a product or service. There's no such thing as 'a business,' just a group pursuing a goal."
> — Elon Musk, *The Book of Elon* (Chapter: A Group with a Goal)

## What this skill captures

There is no "business" — there is only a group of people pointed at a goal, and a product they are trying to put in front of other humans. Musk strips the abstraction: "A company is essentially a cybernetic collective of people and machines... far smarter than an individual." Everything follows from that — the talent you attract, the cohesion of their direction, and whether you can show them (and the world) something real instead of a slide.

The second half of the chapter is just as sharp: you convince people to join — and to buy — by building, not pitching. "If you're going to create a company, the first thing you should try to do is create a working prototype." This skill forces the user back to those two truths: name the group and the goal in plain language, and replace any deck with a demonstration. The payoff is a team that knows what it is doing and a market that can actually see it.

## When to use this skill

- The user is starting a company or a new team and asking what to do first.
- The user is writing a mission statement, OKRs, or onboarding doc and it is drifting into corporate abstraction.
- The user is debating whether to build a prototype or polish a pitch deck for investors / leadership / customers.
- The user is recruiting and cannot articulate the goal in one sentence a candidate would actually believe.
- The user is "the business" / "the product" / "the engineers" siloed in their head as separate things instead of one group.
- The user is stuck convincing stakeholders with calculations and slides that "look good on PowerPoint" but are not landing.

## The how-to

1. **Name the group and the goal in one sentence.** Strip "the business" and "the company" out of the user's language. Force them to finish: "We are a group of people trying to ____ for ____."
   > "A company is just a bunch of people coming together to create a product or service. There's no such thing as 'a business,' just a group pursuing a goal."
   > — *The Book of Elon*
   If they cannot finish that sentence cleanly, they do not have a company yet — they have an intention.

2. **Audit the group against the goal.** Ask whether the people currently in the room are talented and hardworking enough, and whether they are cohesively pointed in one direction. If not, fix that before anything else.
   > "How talented and hardworking that group is, and the degree to which they are focused cohesively in a good direction, will determine the success of the company."
   > — *The Book of Elon*
   The output of the company is the vector sum of the people in it. Misaligned vectors cancel.

3. **Build the working prototype before the deck.** Whatever the user is about to pitch, ship a primitive working version of it first. A sketch, a mock-up, a crappy demo — anything physical or runnable.
   > "If you're going to create a company, the first thing you should try to do is create a working prototype."
   > — *The Book of Elon*
   Then iterate to make it real as fast as possible. The prototype is the recruiting tool, the fundraising tool, and the product roadmap simultaneously.

4. **Refuse to lead with PowerPoint.** If the user is preparing slides to convince investors, leadership, candidates, or customers, ask what they could demo instead — even in primitive form.
   > "Anything can look good on PowerPoint. If you have an actual demonstration, even in primitive form, it is much more effective in convincing people."
   > — *The Book of Elon*
   People do not commit until they touch something. Calculations on paper are not the same.

5. **Make the offer to recruits honest.** When pitching the group to a candidate or cofounder, name the reasonable chance of success and the reward commensurate with the effort. No vision-laundering.
   > "To create a company, you have to convince others to join you in your effort. You have to convince them there is a reasonable chance of success and if there is success, the reward will be commensurate with the effort."
   > — *The Book of Elon*
   The pitch is: here is the group, here is the goal, here is the prototype, here is the math.

6. **Pressure-test the product against the price.** Before scaling team or spend, ask: do we have a compelling product at a compelling price? If no, the team and the OKRs do not matter yet.
   > "Fundamentally, if you don't have a compelling product at a compelling price, you don't have a great company."
   > — *The Book of Elon*
   No amount of mission writing fixes a non-compelling product.

## Common failure modes

- **Treating "the business" as a thing apart from the people.** Mission docs that talk about "the company's vision" with no humans in the sentence. Musk: there is no "business," just a group pursuing a goal.
- **Pitching before prototyping.** Spending weeks on a deck to raise money to then build the thing. Invert it — build the crappy version first, raise off the demo.
- **Powerpoint conviction.** Believing the team or investors are aligned because the slides were good. They are not aligned until they have touched the product.
- **Hiring for résumé instead of goal-fit.** Filling seats with credentialed people who are not pointed in the same direction. The vector sum collapses.
- **Skipping the price question.** Building a beautiful product nobody can afford. "Compelling product at a compelling price" is one phrase, not two.

## When NOT to use this skill

- The user is deep in operational execution on an already-shipping product and just needs a tactical answer (different problem — this skill is for setup and alignment).
- The user is in a regulated context where the deck / written artifact is the legally required deliverable (still demo too, but don't tell them to skip the doc).
- The user is doing pure research with no product target yet — forcing a "working prototype" prematurely can kill exploratory work.
- The user already has a compelling shipping product and is asking about a separate question (scaling manufacturing, performance review design, etc.) — use the skill that fits that question.

## Source

The Book of Elon by Eric Jorgenson (2026, Scribe Media). Chapter: "A Group with a Goal" (in "Building Exceptional Teams").