Most people open Claude the same way they opened Google ten years ago: a blank box and a hope. Then they decide the model is "mid" because the first answer sounded like a press release.

The model isn't the bottleneck. Context is. If Claude doesn't know who you are, what you run, what "done" looks like, and how you write, it will invent a generic professional and write for that person. You will spend the rest of the year fighting the generic professional.

This is the setup I actually use. Five steps. None of them are clever. All of them compound.

1. Put a real name and job on the account

In Claude's settings, fill in your name, role, and company the way a chief of staff would introduce you — not the way a LinkedIn headline would. "Managing Director, International. I run growth, tech, and operator enablement for a global real estate network" is useful. "Entrepreneur | AI | Real Estate" is not.

This is not branding. It is a prior. Every later answer will be slightly more relevant because the model isn't guessing your altitude.

2. Write custom instructions like an SOP, not a vibe

Custom instructions are the cheapest leverage in the product. Most people paste "be concise and helpful." That is already the default. Write the rules you would give a new hire on day one:

Who I am: [role, team size, what you actually own].
How I decide: speed over completeness; flag risk; never invent numbers.
How I write: short sentences, no filler, no "I'd be happy to", no em dashes for drama.
Hard rules:
- If you don't know, say so.
- Separate facts from inference.
- Ask up to 3 clarifying questions before a big deliverable.
- Never send, publish, or delete anything on my behalf.

Keep it under 400 words. If you cannot fit it, you don't have a system — you have a diary. Cut until a stranger could follow it.

3. Create one Project for the work that repeats

A Project is a folder with memory. Put the documents you reuse every week in it: your offer, your org chart, your brand voice, three examples of writing you actually sent, last quarter's priorities. Then stop opening a fresh chat for that work.

I keep a single "Operating" project for anything that touches the business, and smaller projects for builds (a dashboard, an agent, a course). Mixing them is how you get a listing description in the middle of a board memo.

4. Connect the tools you already live in

Gmail, Calendar, Drive or Notion. Connectors are not a party trick. They are how Claude stops asking you to paste the thing it could have read. Connect one inbox and one calendar first. Do not connect everything on day one. More access without a workflow is just a larger attack surface for sloppy asks.

5. Run a 15-minute calibration, then lock it

Give Claude three recent pieces of work you liked and one you hated. Ask: "Extract the rules. Don't compliment me. Write instructions I can paste back into settings." Then paste the good parts. This is the step 99% of people skip because it feels like extra homework. It is the whole job.

If Claude still sounds generic after this, you skipped a document, not a prompt. Go back and add the missing context. Do not buy another tool.

When this is done, prompting gets quieter. You stop restating your life every morning. That is the entire point of setup.