# Start Ideal Client Profile

> Builds an Ideal Client Profile from real situations in your past roles, naming the situation and trigger that makes someone need you, the job they hire you for, who decides as roles and the red flags you can observe on a first call. Use for "run start-ideal-client-profile", "who is my ideal client", "I can do anything I did in my old job", "who am I really for", "I would say yes to anyone", "write my ideal client profile", "red flags in a first call", part of the Claude Guide for New Founders Pack by 90n.

- Skill: `polar-bear-org/start-ideal-client-profile` (Agent Skill)
- Install (CLI): `npx get-skill add polar-bear-org/start-ideal-client-profile`
- Raw SKILL.md: https://api.skillmd.com/api/skills/polar-bear-org/start-ideal-client-profile/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: polar-bear-org (https://skillmd.com/u/polar-bear-org)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/polar-bear-org/start-ideal-client-profile

---


# Ideal Client Profile

## When To Use
You would say yes to anyone who asked, because you can do anything you did in your old job. That sounds flexible and reads as vague. This answers one question: in what situation does someone need exactly you, and what tells you early that the work will go wrong?

## When Not To Use
If you know who you are for and nobody can repeat why you, go to Positioning Statement. If you have not yet listed your past work, run Career Proof Inventory first; a profile with no real situations behind it is a wish.

## Inputs
- 3 to 5 situations from your past roles where your work mattered most, and 2 or 3 you would never repeat: an internal client, a customer, a project. No names needed.
- What the people you served said about why they came to you, as you remember it or from notes addressed to you.
- Your Career Proof Inventory, if you have it.
If you have none of this, I start from two situations you remember well, one good and one bad, and mark the output as a first draft.

## Approach
Jobs to Be Done, as the Christensen Institute describes it: people do not buy a service, they hire it to make progress in a particular circumstance. A new founder has no past clients, but has years of people who came to them with a problem; those are the circumstances to read. The failure it prevents is the profile written from imagination, a client you wish you had, which filters out the people who already trust you with exactly this.

## Workflow
1. Ask at most three questions: which past situations count as best and worst for you (your reasons, not mine), what kind of work you want more of this year, and what you would never take on again.
2. For each best situation, find the circumstance: what had just happened when they came to you (a change, a deadline, a failure, a new person in a role). Write it as a trigger you could spot from outside, then look for the two or three that repeat.
3. Write the job in three dimensions: functional (the work that had to get done), emotional (how the person wanted to feel), social (how they wanted to be seen by their boss, board or team). Anything I infer is marked "my reading, to check".
4. Translate from inside to outside: an internal sponsor becomes "the person who owns this problem"; note what changes when that person has to pay an invoice for help they used to get from a colleague.
5. Map who decides, as roles in a decision: who feels the problem, who signs, who can block, who uses the work. Never a judgement of the people in them.
6. From the worst situations, write red flags you could notice in a first call, such as "nobody owns the budget". You mark which mean walk away and which mean ask more.
7. Test the draft on one situation you loved. If it would have screened that one out, it is wrong.

## Output Format
```markdown
# Ideal Client Profile
Drawn from: [number] best and [number] worst situations in my past roles
## Situation and trigger
| Trigger I could spot from outside | Seen in | What waiting costs them |
|---|---|---|
| [what had just happened] | [situation A, situation C] | [their words, or "unknown"] |
## The job they hire me for
- Functional: [the work that has to get done]
- Emotional: [how they want to feel]
- Social: [how they want to be seen, and by whom]
## Who decides
| Role in the decision | What they care about | Seen in |
|---|---|---|
| [feels the problem / signs / can block / uses the work] | [from my notes] | [situation] |
## Red flags for a first call
| Signal I can observe | Seen in | Walk away or ask more |
|---|---|---|
| [signal] | [situation] | [my call] |
## Decision
[Your name] decides which red flags are walk-away rules and tests the profile on the next [number] conversations, by [date].
```

## Done When
- Every trigger, job and red flag traces to a real situation from your past roles.
- The profile describes situations and roles, never a size, sector or type of organisation.
- Each red flag is something you could observe in a first call.
- The test against a situation you loved passes.

## Quality Bar
- Situations, not labels: "a new leader inherited a stalled project" beats any category.
- Inferences are marked; nothing is presented as said unless it was said.
- Decision roles describe a part in a decision, never a person's character or worth.
- You set which flags mean walk away; I only list what the situations show.
- Built from your real career, never from imagined clients; you decide who you are for.

## Next
Run start-point-of-view (Point of View Statement) to write down what you believe about this work.

## About the makers

This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).

