Business Context

# Business Context

Run this one first. It's the skill that makes every other skill good.

Your job is to interview me and then write an `about-me.md` file properly.
Not a template with my name dropped in — the real thing, in my words, specific
enough that a new hire could read it and be useful.

## How to run this

**Ask me questions one at a time.** Not a list of ten. One question, wait for
the answer, then the next. If an answer is thin, ask the follow-up before
moving on.

**Look first.** Before you ask anything, read whatever context you already
have about me — an existing about-me file, notes, documents I've shared, or
anything in your memory. You'll learn half of this without asking. Then only
ask what you couldn't work out.

Open with: *"Here's what I think I already know — correct me where I'm
wrong."* Then list it. That's faster for me than answering from scratch, and
it shows you did the reading.

## What you need by the end

1. **The business** — what it sells, to whom, how it makes money, roughly how
   big, how old, what stage it's at
2. **My role** — what's genuinely mine versus what I get dragged into
3. **The customers** — who they are, what they're trying to do, what makes them
   say yes, what makes them leave
4. **The people** — team, and the outside names that show up in my email
5. **Right now** — the two or three things that matter this quarter
6. **The constraints** — what's actually in the way. Push here. The first answer
   is usually "time." Ask what specifically.
7. **The vocabulary** — words that mean something particular here
8. **The non-obvious** — what a smart new hire takes three months to learn

## The questions that get real answers

Ask these rather than the generic version:

- *"What did you do last week that somebody else should have done?"*
  (Better than "what are your pain points.")
- *"What's the last deal you lost, and why did they say no?"*
  (Better than "who are your customers.")
- *"What do you explain to every new client in the first month?"*
  (This is the non-obvious list, straight out.)
- *"If you disappeared for two weeks, what breaks?"*
  (This is the real role description.)
- *"What number do you check first on a Monday?"*
  (Tells you what actually matters here.)
- *"What's a word you use internally that an outsider would misread?"*

## Rules

- **Eight to twelve questions. Then stop.** If I'm giving short answers, stop
  earlier and write what you have. A finished file I can edit beats a perfect
  interview I abandon at question nineteen.
- **Never fill a gap with a plausible guess.** If I didn't tell you, write
  `[not covered yet]` and move on. A confident invention in this file poisons
  every task that reads it afterwards.
- **Write in my words**, not a cleaned-up business-school version. If I said
  "we're a two-person shop that does websites for dentists", that's the line.
  Don't turn it into "a boutique digital agency serving healthcare
  professionals."
- **Don't overwrite what's there.** If an about-me file already has content,
  merge into it and show me what changed.

## Output

Write `about-me.md`, organized under the eight headings above. If I have a
place I keep files like this, ask once and save it there; otherwise give it
to me to save.

Then tell me, in three lines:

- what you learned that you couldn't have guessed
- the two or three gaps still marked `[not covered yet]`
- one question I should answer next time to make this sharper

Finish with: *"Run Voice Profile next — it'll take about five minutes and
it's what stops everything sounding like AI."*