Theo Vega (@theovega)

A smaller way to tackle a pricing page review

A compact prompt and the response it produced. Replace the bracketed parts with your own details.

Theo Vega

For a pricing page review, should I build a complete plan first or test one small slice? I have limited time and I do not want throwaway work.

ChatGPTgpt-5

Test one slice, but choose a slice that crosses the riskiest part of the problem. A tiny easy demo will only prove the easy part. Use this decision rule: - If reversing the choice is cheap, try it. - If the choice locks in data, money, or other people’s time, write the full decision first. - If uncertainty is concentrated in one step, test that step before planning around it. For a pricing page review, make the first test produce evidence you can compare, not just something that looks complete.

Show all 3 messages

3404k

Theo Vega@theovega·2w ago

Forked from@idrisbello/What I was getting wrong about separating model mistakes from missing context

What I was getting wrong about separating model mistakes from missing context

Sharing the correction because the mistake looked reasonable until I tested it.

Theo Vega

I want to learn separating model mistakes from missing context, but I keep collecting explanations instead of getting better at it. I have 35 minutes. Start by checking what I already know.

Geminigemini-2.5-pro

Good. Do these without looking anything up: 1. Explain separating model mistakes from missing context in two sentences. 2. Give one situation where you would use it and one where you would not. I am checking your current model, not your vocabulary. A partial answer is more useful than a polished guess.

Show all 6 messages

6100

Theo Vega@theovega·1mo ago

The checklist I use for a pricing page review

This started as a messy question about a pricing page review. The follow-up made the answer practical.

Theo Vega

I am stuck on a pricing page review. I need to find where pricing language creates uncertainty and propose clearer choices, but my current attempt is getting vague and too big. What would you check first?

Claudeclaude-opus-4.5

First, shrink the decision. Do not solve the whole subject at once. 1. Start from observed behavior. 2. Write the riskiest assumption down. 3. Choose a measurable next test. Write down the result you need by the end of this session. Then choose one input you trust and make a first pass that can be checked. If that pass fails, you will know which assumption to revisit instead of starting over.

Show all 3 messages

3402.7k

Theo Vega@theovega·2mo ago

a pricing page review: the version with actual constraints

Sharing the wording because it gave me something I could check instead of a confident wall of text.

Theo Vega

Give me a short checklist for a pricing page review. I want something I can run before I call the work done.

Claudeclaude-opus-4.5

Use this pass: - [ ] The goal is one sentence and names the user or decision - [ ] Inputs are current, relevant, and traceable - [ ] Assumptions are visible - [ ] Start from observed behavior - [ ] Write the riskiest assumption down - [ ] Choose a measurable next test - [ ] One failure case has been tested - [ ] The next owner and next action are clear If you cannot check an item, mark it unknown. Do not quietly treat unknown as done.

Show all 3 messages

3301.2k

Theo Vega@theovega·2mo ago

I asked Gemini for a second opinion on a pricing page review

The useful bit was asking for trade-offs and a smallest test before committing to a full plan.

Theo Vega

Be blunt about my plan for a pricing page review. I am going to collect everything, ask for a polished answer, and fix details later. What is likely to go wrong?

Geminigemini-2.5-pro

Three things. - “Everything” has no boundary, so weak inputs and strong inputs will be treated alike. - A polished answer can hide missing evidence. Ask for gaps and assumptions before prose. - “Fix details later” means there is no acceptance test now. A safer sequence is: define the decision, choose the minimum trusted inputs, make an ugly first pass, check it, then polish. For this task, write the riskiest assumption down.

Show all 3 messages

3302.6k

Theo Vega@theovega·3mo ago

The a pricing page review prompt I actually kept

Sharing the wording because it gave me something I could check instead of a confident wall of text.

Theo Vega

Help me find where pricing language creates uncertainty and propose clearer choices. Context: - Goal: [what a good result lets me do] - Current situation: [paste notes, draft, data, or constraints] - Audience: [who will use the result] - Deadline or limit: [time, budget, tools, length] Before answering, ask up to three questions only if the answers would materially change your recommendation. Othe

ChatGPTgpt-5

This is usable as written. The important parts are the definition of done, the instruction to expose assumptions, and the request for a smallest test. For a pricing page review, I would start with these checks: - Start from observed behavior - Write the riskiest assumption down - Choose a measurable next test If you share real material, remove anything private first and replace bracketed fields with concrete details.

Show all 3 messages

3304k

Public pits

A smaller way to tackle a pricing page review

What I was getting wrong about separating model mistakes from missing context

The checklist I use for a pricing page review

a pricing page review: the version with actual constraints

I asked Gemini for a second opinion on a pricing page review

The a pricing page review prompt I actually kept