2.3.1 - Where the Real Differentiation Actually Lives in Your Build

Name the real differentiation: point to the advantage, show where the user feels it and say what should remain standard.

Real differentiation

Where does real differentiation show up for users?

The call

Name the advantage before building around it. Otherwise AI helps you add features that look different but feel the same as every alternative.

Sharpen the real differentiation with AI

This is a Build idea, so there are two AI moves: first Sharpen the real differentiation using the prompt below, then Build it with AI, vibeCoding the thinnest working code that tests the decision.

New here? Let your AI do this with you. Paste your problem into Guide me and it builds a prompt that walks you through this in ChatGPT or Claude. You do not need to know how to prompt.

Prefer to drive the AI yourself? Give ChatGPT or Claude this page and ask it to help. For skill.txt, the Claude Code plugin and other ways in, see how to use vibe2value.

Or copy this prompt into AI chat, replace the bracketed lines with your real differentiation and keep the instruction exactly as visible here. It helps you put your build/differentiation.md together by refining your three lines until two people would make the same product decision from them.

You are checking whether this real differentiation is clear enough before you move forward.

Constraint:
The real differentiation must be specific enough that two people would invest in the same custom work from it.

Example of the standard:
Vague: "Our differentiation is that we use AI to make search better."
Sharp: "Our differentiation is that a content creator gets search results shaped by what they have already published. The context layer is the custom work. Everything else, auth, database, hosting, stays standard."
The sharp version is specific enough that two people would invest in the same custom work. The vague one is not.

Working draft:
Real advantage: [what the real advantage is]
Where the user feels it: [where the user feels that advantage]
What stays standard: [what should remain commodity or standard]

Task:
Decide whether this real differentiation is specific enough that two people would invest in the same custom work. If it already is, say so. If it is vague, rewrite it to meet the standard in the example above.

Check:
- Would two people interpret this the same way?
- Does it stay concrete enough to guide the next step?
- Does it meet this bar: You can point to the advantage, show where the user feels it and say what should remain standard

Return:
- Verdict: clear, or needs work
- The corrected three lines, or the original three if already clear
- What was vague, and the one change that fixed it

Copy this into AI chat. Replace the bracketed parts. Keep the rest unchanged. AI will likely suggest refinements based on what you enter. Use those to sharpen your thinking, not replace it.

There are six ways to work with AI across a build. This idea's AI moves are noted above. See Working with AI for all six and where each fits.

The same idea on a recipe card

Everyone can boil pasta. The reason people come to your table is the sauce, the one handed down with a spice blend nobody else quite gets right. Buying fancier plates and a new tablecloth makes the meal look different, but it tastes the same as every other table in town.

Your real differentiation is that sauce. Name the one thing the user genuinely cannot get from the obvious alternative, the place it shows up and what should stay plain and standard. Put your effort into the sauce and not the tablecloth, so people can actually taste the difference and not just see it.

The recipe card is just a simple example, using everyday cooking ideas everyone understands, to make the concept clear. See the recipe card.

What it really means

Real differentiation is not a pile of features. It is the specific advantage the user cannot easily get from the obvious alternative. Until you can name one real advantage, one place it shows up and one thing that should stay standard, the product will blur. AI can help generate ideas, but it cannot choose what deserves custom effort.

Make the real differentiation concrete

Compare the broad version with a version you can actually test.

Too vague: Our differentiation is that we use AI to make search better.
Concrete enough to test: Our differentiation is that a content creator gets search results shaped by what they have already published. The context layer is the custom work. Everything else, auth, database, hosting, stays standard.

The second version lets two people invest in the same custom work from it.

Most of what a product does is table stakes that everyone has. The real differentiation is the narrow thing only you do, and knowing exactly where it lives tells you where to spend effort and where to just match the standard.

Check the real differentiation

Pass: You can point to the advantage, show where the user feels it and say what should remain standard.
Fail: If differentiation still sounds like AI-powered or better experience in general, it is not clear enough yet.

Do not move into roadmap, feature or platform work until this passes.

What you'll walk away with

This post is about the framing decision: the words that pin down what this idea actually means for your build, before any code. You'll come out with your own knowledge-base/build/differentiation.md written and sharpened: the real differentiation pinned down as a decision, three worked examples to map against your own surface and an AI prompt that pressure-tests it until two people would make the same call.

Write it down

Your differentiation.md is a real file in your project. The AI forgets everything between sessions. It reads this file each time to pick up what you already decided, on this idea or another part of the build. Write it down once instead of explaining it again.

knowledge-base/shape-build-launch/build/differentiation.md is just a suggested name and place for this information. The name and the location are just how we organise this type of documentation, not something you have to follow. Call the file and put it wherever suits your project. What matters is that it is written down in a format that is easily understood by both people and the AI.

The .md ending is markdown, a plain text format often used for documents kept in a code repository like GitHub. It is just the common way people store this kind of writing alongside their code.

Writing it down is how you keep good context for your AI. See Keep the signal, not the noise for why this matters across a whole build.

Risk and mitigation

Risk: Confusing extra features with real differentiation, which adds complexity while the core value stays unclear to users.
Mitigation: Choose one user-critical signal of differentiation and use it to accept or reject every build decision.

Key takeaway

Do not move forward until you can point to the advantage, show where the user feels it and say what should remain standard.

How to document your real differentiation

Write your real differentiation up in full so your AI has the whole picture: the answer, why you believe it, what you are optimising for, where you might be wrong and the standing instruction it should follow. Keep it in a file with your project like this.

# Real differentiation

## Answer
Real advantage: [what the real advantage is]
Where the user feels it: [where the user feels that advantage]
What stays standard: [what should remain commodity or standard]

## Evidence
Why you believe this. Conversations, examples, tickets, your own experience.

## Decision
What you are optimising for and what you are saying no to.

## Risk
Where you might be wrong and what would tell you.

## AI instruction
The standing note your AI reads on this project.

Here is one filled in so you can see what good looks like, grounded in the recipe card idea from earlier.

## Answer
Real advantage: The handed-down sauce with a spice blend nobody gets right
Where the user feels it: The first taste at the table
What stays standard: The boiled pasta, the plates and the tablecloth

## Evidence
Guests always ask about the sauce and never about the pasta or the plates, which are the same as anywhere.

## Decision
Optimising the sauce that nobody else gets right. Saying no to spending effort on the pasta, plates and table.

## Risk
I might polish the standard parts and neglect the sauce. Protect the time and care the sauce needs first.

## AI instruction
The real advantage is the handed-down sauce with its spice blend, felt at the first taste. Keep the pasta, plates and tablecloth standard and put the care into the sauce.

Common questions

What is the differentiator when the thing I am making is a site?
Your voice and your judgment, which is to say the writing. The platform is identical to everyone else's and it should be. Nobody subscribes because of the software. Your Ghost site is about getting that voice found and read.
And in a product?
The one capability that is yours, which is usually a fraction of the code. Everything around it is plumbing worth buying. If you cannot name the fraction, you are about to spend months on the plumbing. Build your product is pointed at that fraction.

What now?

Apply it. Guide me turns what you are building into a prompt that walks you through this idea.

Get all 27. The guide is a free coffee-length read with the whole method. Join free and it is yours to download.

Get a hand. Work with me and we will work out together what is worth doing. The first conversation is free.