2.1.2 - Where the User First Feels Value Is Where to Start Building

First value moment

Where do users first feel real value in this flow?

The call

Find the first moment value lands. Otherwise AI helps you build a longer path to a reward users never reach.

Sharpen the first value moment with AI

This is a Build idea, so there are two AI moves: first Sharpen the first value moment 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 first value moment and keep the instruction exactly as visible here. It helps you put your build/first-value-moment.md together by refining your three lines until two people would make the same product decision from them.

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

Think of the first moment a meal feels worth it: the smell of garlic hitting the pan, or the first warm bite. That is the point where everyone is glad they waited. A meal whose only reward comes after an hour of prep and a sink full of washing up loses people long before they taste anything.

Your first value moment is that first good smell. Find the earliest point the user feels real reward and build the short path that gets them there first. Do not make them earn it through a long setup, the way a good cook gets something delicious going early so the kitchen smells like dinner within minutes.

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

The first value moment is not the full product promise. It is the earliest point where the user can feel that this was worth starting. Until you can name one user, one first value moment and the step that gets them there, the flow will stay vague. AI can help shorten the path, but it cannot decide where value begins.

Make the first value moment concrete

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

• Too vague: Users feel value once they start using the search tool.
• Concrete enough to test: A content creator feels value when the first search result reflects what they have already published, right after they enter their first question with saved context.

The second version lets two people optimise the same step from it.

Check the first value moment

• Pass: You can point to the moment the user first feels relief or progress and the step immediately before it.
• Fail: If value still means the product feels useful in general, it is not specific enough yet.

Do not move into feature, onboarding or optimisation 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/first-value-moment.md written and sharpened: the first value moment 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 first-value-moment.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/first-value-moment.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: Adding setup work before users experience value, which increases drop-off and weakens trust in the product.
• Mitigation: Define one first-value signal and reject any change that delays that signal without clear user benefit.

Key takeaway

Do not move forward until you can point to the moment the user first feels relief or progress and the step immediately before it.

How to document your first value moment

Write your first value moment 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.

# First value moment

## Answer
User: [who first feels value]
First value moment: [the first moment they feel relief or progress]
Step right before it: [the step immediately before that moment]

## 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
User: A hungry guest waiting for dinner
First value moment: The smell of garlic hitting the pan
Step right before it: The pan gets hot and the garlic goes in

## Evidence
Guests always perk up the moment the garlic hits the pan, well before anything is on a plate.

## Decision
Optimising for that first hit of smell early. Saying no to prep that delays getting something aromatic going.

## Risk
Rushing the garlic in on a cold pan gives no smell. Get the pan properly hot first.

## AI instruction
The first value moment is the smell of garlic hitting a hot pan. Get to it early, and make sure the step right before it, heating the pan, is done well.

Common questions

1. Where is that moment on a content site?
   The first piece someone finds when they were looking for something else, that turns out to be exactly right. Everything after that, the list and the email, only works because that moment landed. It is why content is the foundation in Your Ghost site.
2. Where is it in an app?
   The first screen that does the thing, not the sign-up before it. If someone has to get through setup before feeling anything, build the feeling first and the setup after. Build your product calls that the thinnest thing that proves it.

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.