aaron

Good call on keeping this beginner-friendly — turning dense topics into visual maps only works if the steps and tools are simple and repeatable.

Hook: If you want fast clarity from dense material, a concept map gives you a visual outline you can act on in minutes, not days.

Problem: Dense documents, long articles or technical papers bury relationships and priorities. You end up with notes that don’t help decision-making.

Why this matters: Visual maps reduce cognitive load, make gaps obvious, speed onboarding, and turn content into shareable strategy assets.

What I’ve learned: Start with extraction, then structure, then visual layout. AI is best at extraction and tagging; you handle the judgement calls about importance and connections.

Step-by-step (what you’ll need, how to do it, what to expect)

1. What you’ll need: source text (PDF or URL), an AI assistant (ChatGPT/GPT-4 or similar), and a mapping tool (Miro, MindMeister, Obsidian/Excalidraw, or even PowerPoint).
2. 1 — Define the goal (5–10 minutes): write the question you want the map to answer (e.g., “How do components X, Y, Z interact to cause outcome A?”).
3. 2 — Extract concepts with AI (10–20 minutes): paste 1–2 paragraphs or a section and ask the AI to list 8–12 key concepts with 1-line definitions and relationships.
4. 3 — Group & prioritize (10 minutes): combine similar nodes, label three priority tiers (core, supporting, examples).
5. 4 — Draft relationships (10 minutes): decide which nodes connect and whether the link is causal, hierarchical, or associative.
6. 5 — Build the visual map (15–30 minutes): place core nodes centrally, use directional arrows for causality, color-code tiers, add short notes on hover or beside nodes.
7. 6 — Validate & iterate (10 minutes): get one colleague to read the map and mark confusing parts; revise once.

Copy-paste AI prompt (use this exactly)

“Read the following text and return: 1) a numbered list of up to 12 core concepts, each with a one-sentence plain-English definition; 2) for each concept, list related concepts and the type of relationship (causes, enables, is part of, contrasts with); 3) suggest 3 priority tiers (core/supporting/example). Output as plain text, ready to paste into a concept-mapping tool.”

Metrics to track

• Time to map (target: under 90 minutes)
• Number of core concepts (target: 5–10)
• Comprehension lift (quick 3-question quiz before/after; target: +30% correct)
• Revision count after feedback (target: 1)

Common mistakes & fixes

• Too many nodes — fix: merge similar concepts, enforce a 12-node cap.
• Vague labels — fix: force one-line definitions using plain language.
• No hierarchy — fix: label core vs supporting before mapping layout.

1-week action plan

1. Day 1: Pick one dense article, define the map question.
2. Day 2: Run the AI extraction prompt and refine concepts.
3. Day 3: Group, prioritize, and draft relationships.
4. Day 4: Build the visual map in your chosen tool.
5. Day 5: Share with one person for feedback; revise.
6. Day 6: Create a one-page summary from the map.
7. Day 7: Measure comprehension lift and decide next topic.

Your move.

Nice call on keeping it small — 3–5 habits and a single daily or weekly view is exactly the right simplicity.

Problem: dashboards become busywork when they demand time or technical skills. That kills consistency, and without consistency you don’t get behaviour change.

Why this matters: a dashboard that takes 1–2 minutes a day and gives an immediate win produces momentum. Momentum means progress, and progress is measurable.

What I’ve learned: start minimal, automate the interpretation, and get a single actionable next step each day. You don’t need integrations to get value — a simple spreadsheet plus an AI prompt you paste weekly will do 80% of the work.

1. Decide scope — pick 1 goal and up to 3 supporting habits. Choose daily or weekly tracking, not both.
2. Build the sheet (10–15 minutes):
   1. Columns: Goal | Habit | Target (e.g., 4/7) | Mon–Sun (checkboxes) | Progress % | Streak | Next Action.
   2. Formula: Progress % = checked boxes / total required. Streak = consecutive weeks/days meeting target.
   3. Conditional formatting: Green when Progress >= target, yellow when 75–99%, red when <75%.
3. Add light AI interpretation (manual): once per week copy the habit rows and paste into an AI assistant using the prompt below. The AI returns a one-sentence summary and up to three clear next actions.
4. Daily habit: open sheet, check boxes (60–90 seconds), act on the single Next Action for the day.

Copy-paste AI prompt (use with ChatGPT or similar)

“Here is my weekly habit data. For each habit give: one-line summary of performance, one reason why it succeeded/failed (likely cause), and one clear next action for the coming week. Data: [paste rows like: Habit: Walk 20min | Target 4/7 | Checks: Mon,Tue,Thu = 3/7 | Streak: 2]. Keep each habit to one short paragraph.”

Metrics to track (KPIs)

1. Completion rate (%) — primary KPI (target >= 75%).
2. Streak length — weeks/days in a row meeting target.
3. Update time — daily seconds to update (goal ≤120s).

Common mistakes & fixes

• Mistake: Tracking too many habits. Fix: Drop to 1–3 and add new ones only after 4 consecutive weeks of success.
• Mistake: No next action listed. Fix: Use the AI prompt above weekly to create one actionable step.
• Mistake: Making progress use subjective measures. Fix: Use checkboxes and percentages for objective tracking.

1-week action plan

1. Day 1 (30 min): Create the sheet with columns and one habit row. Add conditional formatting and a simple progress formula.
2. Day 2–7 (1–2 min/day): Open sheet, check today’s box, and follow Today’s Next Action. Log time to update.
3. End of week (10 min): Copy the week’s rows into the AI prompt above. Update Next Actions based on the AI output.

Your move.

Hook: Stop guessing what visitors want — serve the exact message that matches their intent and watch conversions climb.

The problem: Most sites treat everyone the same. That wastes attention, reduces conversions, and lengthens the buyer journey. AI lets you match content to intent in real time, without rewriting the whole site.

Why it matters: Relevant content shortens decision time, increases engagement and lowers acquisition cost. Even a 10–20% uplift on key pages compounds across traffic and lifetime value.

My lesson from doing this: Start simple, measure fast. Rules get you results quickly; AI scales nuance. I’ve seen teams double demo requests on pricing pages by swapping one headline and CTA based on referral source.

What you’ll need

• Basic analytics (GA4 or similar) and access to page templates.
• Real-time signals: UTM, referrer, landing page, clicks, time on page (use a tag manager).
• A simple personalization layer (feature flag, server-side switch, or a personalization tool).
• An LLM or copy generator (optional at start) and an A/B testing tool.

1. Define 3–4 intent buckets — Research, Compare, Purchase, Support.
2. Map signals to intents — e.g., blog + >3 minutes = Research; price page + cart clicks = Purchase.
3. Create 2–3 content variants per intent — headline, one-line subhead, CTA.
4. Deploy rule-based swaps — swap hero headline or CTA based on signals; render async to avoid latency.
5. Measure — run A/B tests vs baseline for 2–4 weeks.
6. Add LLM for nuance — generate microcopy for lower-traffic segments once rules prove out.

Step-by-step (how to do it)

1. Pick one high-traffic page (pricing or product).
2. Implement signal capture (UTM, referrer, time on page) via tag manager.
3. Build 3 simple variants and implement server-side swaps for hero content.
4. Run A/B test for 14–28 days, measure lift, iterate.

What to expect: Quick wins in 2–4 weeks, clearer winners by month two. Expect small behavioral changes first (time on page, CTR), then conversion lift.

Metrics to track

• Primary: Conversion rate on target page (lead, trial, purchase).
• Secondary: Click-through rate on CTAs, bounce rate, time-on-page.
• Operational: Page load impact, false-positive personalization rate.

Common mistakes & fixes

• Mistake: Over-personalizing with noisy signals. Fix: Use conservative, high-precision signals first (referrer, landing page).
• Mistake: Slowing pages. Fix: Load personalized blocks asynchronously and cache results for session.
• Mistake: Skipping A/B tests. Fix: Always test personalization vs baseline before scaling.

Copy-paste AI prompt (use with your LLM)

“You are a concise website copywriter. Given this visitor intent and signals, write a 6–8 word headline, one-sentence subhead, and a 2–3 word CTA label that drives the next step. Keep tone helpful and direct. Visitor intent: {intent}. Signals: {referrer}, {landing_page}, {time_on_page}, {previous_actions}. Output as plain text with lines: HEADLINE:, SUBHEAD:, CTA:.”

1-week action plan

1. Day 1: Choose target page and define intents (30 mins).
2. Day 2: Configure signal capture in tag manager (60–90 mins).
3. Day 3: Write 3 variants per intent (use the AI prompt) and prepare swaps.
4. Day 4: Deploy rule-based personalization (staged rollout).
5. Days 5–7: Run quick A/B test seed, monitor metrics daily, fix any latency or mismatch.

Your move.

Quick yes: Good call — the scaffold (headline + three points + one example) is the highest-leverage move. That small structure is what turns chaos into publishable content fast.

The problem: Messy notes sit inactive. You lose ideas, momentum and time trying to make sense of noise.

Why it matters: Convert notes into posts reliably and you build audience, authority, and reusable content without marathon writing sessions.

My point-of-view: I coach busy owners to treat notes like raw materials — extract a single angle, create a 3-point skeleton, and use AI to draft the first full pass. That routine cuts drafting time dramatically and raises publication velocity.

Step-by-step (what you’ll need and how to do it):

1. Grab one page/photo of notes, open a doc, set a 10–20 minute timer.
2. Scan 2 minutes: pick one clear angle and write a one-line angle statement.
3. Extract 5 minutes: write a headline and three bullets (Problem / Quick fix / Benefit).
4. Draft 5–10 minutes: either expand each bullet into 1–3 sentences or paste notes + prompt into an AI tool (prompt below).
5. Polish 5 minutes: add one concrete example, tighten headline, add one-line CTA. Save as draft and schedule publish or repurpose.

Metrics to track:

• Drafts created per week (target: 3–5)
• Time per draft (target: <30 minutes)
• Published pieces per month (target: 4)
• Engagement signal: opens/reads or social interactions per post

Do / Do not checklist:

• Do pick one angle before using AI.
• Do keep posts short — aim for 250–400 words for quick reads.
• Do save the original note and draft separately.
• Don’t feed raw, unfocused notes to AI — that adds rewrites.
• Don’t wait for perfect — publish then iterate.

Mistakes & fixes:

• Mistake: No angle. Fix: force a one-line angle before drafting.
• Mistake: Over-polishing. Fix: two passes only — clarity then voice.
• Mistake: No CTA. Fix: add a one-line next step for the reader.

Worked example:

Messy note: “5-min headline, weekly review, newsletter saved time, bullets better than paragraphs”

Polished output: Headline: “Write Faster: A 5-Minute Headline Routine” — Bullets: Problem: Long drafting sessions. Quick fix: 5-min headline + 3 bullets. Benefit: Publishable draft in 20 minutes. Intro paragraph and three short sections follow, ending with a one-line CTA to try the routine this week.

Copy‑paste AI prompt (use as-is):

Here are messy notes: [paste notes]. Use this angle: [paste one-line angle]. Produce: 1) one clear headline, 2) a 3-bullet outline (Problem / Quick fix / Benefit), and 3) a 250–350 word friendly blog post in a warm, practical tone with one concrete example and a one-line CTA. Keep reading time ~2 minutes.

7-day action plan:

1. Day 1: Pick one page, follow steps, publish a short post.
2. Days 2–4: Repeat with new notes — 15–20 minutes each day.
3. Days 5–7: Review drafts, pick one for expansion or newsletter inclusion.

Your move. — Aaron

Make your methodological appendix clear, reproducible and review-ready — in hours, not weeks.

The problem: methodological appendices are often inconsistent, vague about parameters, and hard for reviewers or other teams to reuse.

Why it matters: poor appendices cause reviewer pushback, slow replication, and increase the risk of misinterpretation. That costs time, credibility, and funding.

What works (short lesson): use AI to standardize structure, expand shorthand into explicit steps and parameter tables, and auto-generate reproducibility checks — then validate with a quick human review.

1. Prepare what you’ll need
   • Raw notes, code snippets or scripts, data schema, software/version list, key parameters and thresholds.
2. Create a template
   • Sections: Overview, Data sources, Sampling, Preprocessing, Variables, Models/Analyses, Parameters, Code & environment, Validation checks, Limitations, Change log.
3. Use AI to draft and standardize
   • Feed AI the template plus your notes; ask for explicit parameter tables, step-by-step scripts, and reproducibility checks.
4. Validate
   • Run the generated scripts in a clean environment or ask a colleague to follow the steps. Fix gaps and re-run the AI to tighten wording.
5. Finalize
   • Include versioning, change log, and a one-paragraph reproducibility statement (what to expect when someone follows the steps).

Copy‑paste AI prompt (use as-is)

“You are an expert research methodologist. I will provide: (A) a short set of notes/bullets about data, preprocessing, and analysis; (B) my target audience (e.g., journal reviewers, internal audit). Convert this into a clear methodological appendix that includes: an overview, data sources and permissions, sampling procedure, step-by-step preprocessing with parameter values, variable definitions, model or analysis steps with exact commands or pseudo-code, software and versions, validation checks to run, and a short limitations paragraph. Output: 1) full appendix text, 2) a table of parameters with default values and rationale, 3) a 3-step checklist for someone reproducing the work.”

Prompt variants

• Concise: ask for a 1-page appendix suitable for policy reports.
• Technical: ask for runnable code snippets and Docker/conda environment instructions for reproducibility.

Metrics to track

• Time to produce appendix (target: <8 hours)
• Reviewer clarifying questions (target: reduction ≥50%)
• Successful reproduction runs by a third party (target: 90% success)
• Number of iteration cycles with AI (target: 1–2)

Common mistakes & fixes

• Missing parameter values → include a parameter table and rationale.
• Ambiguous preprocessing steps → convert bullets into numbered commands or pseudocode.
• No environment spec → add exact software versions and a simple environment file.

1‑week action plan

1. Day 1: Gather notes, scripts, data schema; set objectives (audience, depth).
2. Day 2: Run the AI prompt to produce first draft.
3. Day 3: Run generated scripts or have colleague test; collect failures.
4. Day 4: Iterate with AI to fix gaps and produce parameter table.
5. Day 5: Finalize appendix, add versioning and change log.
6. Day 6: Prepare 1‑page summary for non-technical stakeholders.
7. Day 7: Submit to reviewer/internal QA; log questions for next cycle.

Your move.

Cut the friction. Use AI to design a safe, progressive plan in minutes, log in seconds, and adjust weekly. That’s how people over 40 win: steady progress, protected joints, predictable results.

The gap: most plans ignore recovery, logging is messy, and progression is guesswork. Why it matters: without clean data and conservative progressions, you stall or get hurt. AI fixes all three—if you give it the right inputs and commands.

• Do: Start with low joint stress, 2–3 compound moves/session, and simple progressions (reps first, then load).
• Do: Track effort (RPE 1–10), pain (0–10), sleep (hours), and adherence (% sessions done).
• Do: Review every 2–4 weeks and insert a deload when RPE drifts up or pain/sleep drift down.
• Do not: Chase heavy numbers if form or recovery slips.
• Do not: Treat AI as medical advice. New/sharp pain = stop and consult a professional.

Insider play: run a simple “traffic light” system weekly. If median RPE ≤7, pain ≤2/10, and sleep ≥7h → Green: add 1 rep/set next week. If one metric slips → Yellow: repeat last week. If two slip → Red: reduce volume 20% for 7 days (deload). Expect AI to output a one-page plan, a log template, and color-coded adjustments when you feed it your data.

1. What you’ll need: age, current level, injuries/limitations, meds that affect recovery; goals (pick 1–2); constraints (days/week, minutes/session, equipment); and a tracker (notebook or spreadsheet).
2. Build the plan (10 minutes): ask AI for a 6–8 week, 3x/week plan with warm-up, 2–3 strength moves, 5–10 minutes mobility, 10–15 minutes low-impact cardio, and a deload in week 5. Demand clear sets/reps, RPE targets, and knee/shoulder-friendly swaps if needed.
3. Create the tracker (5 minutes): columns: Date | Workout | Exercise | Sets x Reps @ Weight | RPE | Pain (0–10) | Sleep (h) | Notes. Keep it to one page.
4. Run it: follow the plan exactly for 2 weeks. Progression rule: add one rep per set each session until the top of the rep range while RPE ≤7; then increase load 2.5–5% and reset reps to the bottom of the range.
5. Review with AI: paste your last 6 sessions and ask for traffic-light classification plus next-week adjustments. Insert deloads proactively when metrics trigger red.

KPIs worth tracking (weekly)

• Adherence: sessions completed ÷ sessions planned (target ≥85%).
• Median RPE: aim 6–7 for main lifts; rising trend without progress = deload signal.
• Set volume: 6–12 hard sets per muscle group/week; increase slowly (10–15% per block).
• Pain score: stay ≤2/10; any spike = swap exercise or reduce load.
• Sleep hours: target ≥7; Yellow if <7 for 3+ nights.
• Cardio recovery: 1-minute heart rate drop post-cardio improving over time = better conditioning.
• Waist or weight trend (optional): pick one measure; review every 2–4 weeks.

Common mistakes & fast fixes

• Too much novelty: new program every week. Fix: keep the same 6–8 lifts for 8 weeks; adjust sets/reps/load only.
• No deloads: grind until soreness wins. Fix: 20–30% volume drop every 4–6 weeks or on red signals.
• Skipping logs: no data, no adjustments. Fix: 60-second post-session log using the template.

Copy-paste AI prompt (planner)

“I’m a [age]-year-old, currently [activity level], with [injuries/limitations, if any]. I can train [days]/week for [minutes]/session with [equipment]. Goals: [pick 1–2, e.g., functional strength and mobility]. Build a conservative 8-week program: each session includes warm-up, 2–3 compound strength lifts, 5–10 min mobility, 10–15 min low-impact cardio. Provide sets/reps, target RPE, knee/shoulder-friendly alternatives, and a deload in week 5. Include a one-page tracking table with columns: Date, Workout, Exercise, Sets x Reps @ Weight, RPE, Pain (0–10), Sleep (h), Notes. Keep instructions clear for a non-expert.”

Copy-paste AI prompt (weekly review)

“Here are my last 6 sessions (paste logs). Assess adherence, median RPE, pain, and sleep. Classify my week Green/Yellow/Red using: Green = median RPE ≤7, pain ≤2/10, sleep ≥7h; Yellow = one metric off; Red = two or more off. Then provide next-week adjustments: Green = add 1 rep/set; Yellow = repeat last week; Red = reduce total sets by 20% and keep RPE ≤6. Suggest any exercise swaps for joint comfort.”

Worked example (3x/week, Week 1)

• Workout A: Goblet squat 3×8 @ RPE 6, Incline push-up 3×8 @ RPE 6, Seated row 3×10 @ RPE 6, 5 min hip mobility, 10 min brisk walk.
• Workout B: Romanian deadlift 3×6 @ RPE 6, Half-kneeling press 3×8 @ RPE 6, Lat pulldown 3×10 @ RPE 6, 5 min thoracic mobility, 10 min bike.
• Workout C: Split squat 3×8/side @ RPE 6 (box-supported if knees cranky), Chest-supported row 3×10 @ RPE 6, Farmer carry 3x30s, 5 min ankle mobility, 10 min easy cardio.
• Progression: next week add 1 rep/set (if RPE ≤7). When you hit 10–12 reps, increase weight 2.5–5% and drop reps to 6–8.
• Sample log row: 2025-11-22 | A | Goblet squat | 3×9 @ 20 kg | RPE 6 | Pain 1 | Sleep 7.5 | Knee OK, add 1 rep next time.

7-day action plan

1. Day 1: Run the planner prompt with your specifics. Save the program and the tracker.
2. Day 2: Do Workout A exactly. Log within 60 seconds post-session.
3. Day 3: Light walk/mobility 20 minutes. Confirm next session times.
4. Day 4: Do Workout B. Log RPE, pain, and sleep.
5. Day 5: Recovery focus: 7–8 hours sleep, gentle mobility 10 minutes.
6. Day 6: Do Workout C. Log fully.
7. Day 7: Paste the week’s 3 logs into the weekly review prompt. Follow Green/Yellow/Red adjustments.

Score the week by adherence, median RPE, and pain. If the dashboard is green, push one notch; if not, hold or deload. Simple, sustainable, compounding.

Your move.

Nice point — flavor packs are the multiplier you need. Cook once, season twice turns three bases into a week of variety without extra hours in the kitchen.

The problem

Most people either overcomplicate prep with too many recipes or give up because leftovers go bland by day four. That wastes time, money and appetite.

Why it matters

Modular bases + finish-at-serve flavor packs cut cooking time, reduce waste and keep meals interesting — so you stick with the system and free up evenings.

Short lesson from practice

Limit to 3 neutral bases, create 4 flavor packs (one can be a bright garnish), and convert sauces into frozen flavor cubes for instant variety. Track two KPIs first: prep time and meals consumed without extra cooking.

Step-by-step (what you need, how to do it, what to expect)

1. What you’ll need: phone/computer with an AI chat, 2–3 hours, sheet pan, large pot, frying pan, 12 airtight containers (2- & 4-cup), labels, ice cube tray.
2. 5-minute inventory: number of adults, meals needed, dietary limits, container count, fridge/freezer space and key pantry items.
3. Ask AI for a modular plan: 3 neutral bases, 4 flavor packs, grouped shopping list, 15-minute overlapping prep timeline, storage map and reheat instructions.
4. Prep day flow: preheat oven, start grains, roast protein, sheet-pan veg, blitz sauces and pour into trays/ice-cube molds, cool shallow, portion into containers leaving sauces separate.
5. Serve: reheat base, add a flavor pack and a fresh element (acid/crunch/herb) for brightness.
6. Expect: 2 hours → 10–14 meals; midweek you’ll need only 5–10 minutes to finish meals.

Copy-paste AI prompt (use as-is)

Design a one-week modular meal-prep for 2 adults: 10 lunches and 6 dinners. I have 2 hours on Saturday, 12 airtight containers (eight 2-cup, four 4-cup), limited freezer space for 6 flat packs, budget modest. Diet: omnivore, one gluten-free, no dairy. Deliver: 1) 3 neutral bases that scale; 2) 4 flavor packs (include 3 ice-cube sauce recipes); 3) grouped shopping list by store section with quantities; 4) 15-minute overlapping prep schedule; 5) storage map by day (what to fridge vs freeze) and reheat methods; 6) portion guide and fresh garnish suggestions. Ask up to 5 clarification questions if needed.

Metrics to track

• Prep time (target ≤2 hours)
• Meals prepped per hour (target 5–7)
• Food cost per meal (compare week before vs after)
• Food waste (containers discarded/uneaten)
• Eating satisfaction (1–5 scale)

Common mistakes & fixes

• Too many recipes: cap at 3 bases — ask AI to reuse leftovers.
• Soggy meals: keep sauces separate; add at serve-time.
• Under-seasoned bases: season lightly, then finish with sauce or acid when serving.
• Fridge overflow: tell AI exact container count and freezer slots before it plans.

1-week action plan — next steps (crystal clear)

1. Today (10 min): do the 5-minute inventory and count containers.
2. Today (5 min): paste the AI prompt above into your chat; answer clarification questions.
3. Tomorrow: shop with the grouped list.
4. Prep day (90–120 min): follow the 15-minute schedule, portion, label and refrigerate/freeze per map.
5. Midweek: track KPIs, note 2 wins + 1 tweak, ask AI for a midweek remix if needed.

Your move.

Quick win (5 minutes): Open your AI tool, paste the prompt below, and get a 3-tier offer with prices, headlines, and onboarding copy you can publish today. Pick one, set it live, and start testing.

The problem Most Notion templates fail not because of features, but because the offer is vague and the price isn’t anchored to value. Too many variants, no measurable outcome, weak onboarding.

Why it matters Price and packaging drive profit more than features. A crisp outcome + value-based price + simple onboarding will lift conversion, reduce refunds, and speed learning loops.

Lesson from the field The winners ship a lean core, frame it around a time/money outcome, and run a two-price smoke test. They turn feedback into sharper copy within a week, not a rebuild.

Copy-paste AI prompt (offer + pricing, ready to use)

“You are an offer designer and pricing strategist for digital templates. Build a 3-tier Notion product offer. Inputs: Audience = [e.g., independent consultants], Core problem = [e.g., scattered weekly planning], Outcome = saves [X] hours/month, Typical hourly rate = [$75–$150]. Do 7 things: 1) Propose tier names (Entry/Core/Premium), 2) Set price points anchored to outcome and hourly rate (justify in one sentence each), 3) List 3 benefits per tier (plain-English, outcome-first), 4) Write a hero headline (under 12 words) and a 30–50 word description, 5) Draft a 60-second onboarding script and 5-step quick-start checklist, 6) List top 3 buyer objections with concise rebuttals, 7) Recommend one Premium bonus that increases perceived value without extra build time. Return everything as clear bullet lists.”

What you’ll need

• Notion template (duplicate link ready).
• Payment page (Gumroad/Payhip/Stripe) and a simple Google Sheet.
• Screenshots/GIF (3 images + 60–90s demo).
• AI assistant for copy, pricing rationale, and objections.

Step-by-step to build and price

1. Define the outcome + anchor: State a measurable benefit (e.g., saves 4 hours/month). Anchor to buyer’s hourly rate (e.g., $100/hr → $400/month of value).
2. Shape the offer tiers: Entry = core pages, Core = databases + filtered views + examples, Premium = same + onboarding checklist, video, and a bonus pack. Keep Premium as no/low-build extras.
3. Set initial prices: Use the anchor to choose Entry $9–$15, Core $19–$39, Premium $59–$99. Expect Core to be the best seller.
4. Run a two-price test: Publish two near-identical listings (Entry hidden). Test Core at Price A vs Price B (e.g., $24 vs $29) for one week each or 150 visits each, whichever comes first.
5. Onboard to first result fast: Add a 5-step quick start and a pre-filled example so users get value in under 3 minutes.
6. Collect structured feedback: After purchase, ask two questions: “What almost stopped you?” and “What result are you after?” Use this to adjust copy and screenshots, not the database schema.
7. Add a team license decoy: Offer “Team (up to 10 seats)” at 3–5× Core. You’ll sell a few and anchor the Core price as fair value.

Insider levers that move revenue

• Outcome line under the price: “Typically saves ~4 hours/month → pays for itself in week 1.”
• Decoy effect: Premium priced close to Core (e.g., $29 vs $39) with high-perceived extras (video, checklist, templates). Drives Core selection.
• Guarantee copy: “If you don’t save 2+ hours in 7 days, email for a full refund.” Reduces friction, boosts conversion more than refunds rise.

Metrics to track (weekly)

• Visit-to-checkout click rate: Target 5–15% from product page.
• Checkout-to-purchase conversion: Warm traffic 3–8%; cold 1–3%.
• AOV (average order value): Aim $22–$45 early. Add-ons and Premium lift AOV.
• Refund rate: Keep under 5% with clear onboarding and guarantees.
• Time-to-first-value: Under 3 minutes to set up and use one view.

Common mistakes and fixes

• Overbuilding: Don’t add advanced relations/rollups until asked. Fix: ship the simplest version that achieves the outcome.
• Pricing by effort: Hours you spent are irrelevant. Fix: anchor to outcome × hourly rate; round to a fair fraction (5–15%).
• Vague listing: “Beautiful template” doesn’t sell. Fix: lead with quantifiable benefit and a 60s GIF.
• One-size license: You miss B2B buyers. Fix: add a team license and a simple usage note.

1-week action plan (with targets)

1. Day 1: Run the prompt above. Lock your outcome, anchor, and 3-tier offer. Output: final headline, bullets, prices.
2. Day 2: Ship the MVP template and a 5-step quick start. Output: duplicate link.
3. Day 3: Create 3 screenshots + 60s demo. Output: product visuals.
4. Day 4: Publish two Core price variants (A/B). Output: two live links, identical copy.
5. Day 5: Soft launch to 50–200 warm contacts. Target: 100+ visits, 3–8% checkout conversion from warm traffic.
6. Day 6: Review metrics, read all buyer feedback, tighten headline and objection handling. Change one variable only.
7. Day 7: Pick the winning price. Add Premium and Team license. Target: AOV +15–30% vs Day 5.

Bonus prompt (objection crusher)

“Act as a skeptical buyer of this Notion template. Give me the 7 strongest objections (price, complexity, fit, Notion skills, refunds, updates, team usage). For each, write a one-sentence rebuttal and a proof point I can show in one screenshot or a 10-word caption.”

Your move.