Video summary

Engenharia de Produtos de Alto Ticket

Main summary

Key takeaways

Business

Product vs. Offer (core differentiation)

  • Offer = the outcome / transformation promised Example: “lose 9 kg in 9 months”

  • Product = the vehicle / delivery system used to deliver that offer Examples: ebook, course, mentoring, coaching, consulting, done-for-you execution, etc.

Key principle: customers don’t buy content/lessons/info—they buy transformation. The product is how that transformation is delivered.

Value drivers for high-ticket products

Value (and therefore pricing power) depends on two variables:

  • Transformation magnitude (state-to-state change) Example: income lift from X → Y

  • Delivery format + personalization/proximity How close the delivery is to the client, and how tailored it is.

Practical example logic (income)

  • If you help someone go from 100k → 500k/month, that’s ~R$5M/year difference → far higher willingness to pay.
  • If you help someone go from minimum wage → R$3,000/month, that’s ~R$15k/year → much lower willingness to pay.

Therefore: ticket price increases with both:

  1. transformation size
  2. perceived delivery value

Inverse Value Ladder (premium-first pricing strategy)

Instead of starting cheap and moving up, the strategy is to:

  • Start from the highest proximity/personalization
  • Move down only after validation

Why: it’s easier and more profitable to find fewer buyers paying more, and it speeds up feedback loops.

Congruence / pricing psychology

Avoid “non-congruent” pricing where the offer format and price don’t “feel aligned” (e.g., selling mentorship too cheaply triggers skepticism).

Recommended strategy:

  • Give lower-tier assets (ebooks/courses) for free
  • Sell the high-proximity ongoing/implementation mentorship, where trust and reciprocity are built

Customer effort reduction = higher pricing power

Charging more is justified when you:

  • Reduce client effort (you do calls, execution, meal planning, shopping, etc.)

  • Increase follow-up intensity (“infinite coastline” analogy: more monitoring/granularity → more support → higher perceived value)

  • Increase customization personalization per client/business

Ticket ladder mechanics: proximity + personalization, not promise changes

The speaker claims all products share the same promise, e.g.:

sell to more people, at higher prices, more often, increasing revenue and reducing acquisition costs

What changes across tiers:

  • How close the support is done-for-you vs scripts vs group vs recorded

  • How personalized it is tailored actions, templates adapted to niche, individual execution/training

“Infinite feedback” loop (validation before scaling)

A central execution loop:

Input → Output → Feedback → Input (repeated)

Cheap price cycle vs prosperity cycle

  • Cheap price cycle (bad): low revenue → low motivation/resources to invest in success → poor client results → weak evidence → you “eat cheaply.”
  • Prosperity cycle (good): charge a fair/high price → invest more (team/tools/time) → force client results → evidence/social proof → charge more.

Validation principle

  • Proof comes before promise.
  • Launch new products by validating with a small number of high-paying clients to iterate quickly.

How to validate the product (S-rank first, then iterate)

Fast validation approach:

  • Start with a high-proximity, high-personalization “S-rank” offer
  • Conduct sales meetings quickly and use early customer feedback to refine
  • Emphasis:
    • don’t spend a month building a potentially ineffective product
    • use early paid pilots to learn what the market truly wants and what iteration is needed

Replicability constraint

Transformation must be controllable and repeatable (standardizable variables).

Contrast:

  • Uncontrollable outcomes (rare/individual special cases) vs.

  • a controllable methodology that a delivery team can replicate

Product tiers / “S, A, B, C” framework (a playbook)

S — Highest proximity, highest personalization (“done for you” / execution)

  • Purpose: cash flow + client understanding + rapid validation
  • Example formats:
    • individual in-person consulting
    • mentoring/execution with very close involvement
    • “done-for-you” implementation

A — Semi-personalization / standardized delivery with some individualization

  • Purpose: scale stability while maintaining quality
  • Requires:
    • methodology + standardization + delivery processes
  • Examples:
    • semi-collective mentoring (group + individual tasks/submissions)
    • group mentoring + coaching elements
    • in-person events for subsets

B — Recorded training / courses (scaling via standard systems)

  • Purpose: increasing scale and also acquiring new clients via recorded content
  • Examples:
    • recorded training sessions
    • challenges
    • webinars / multi-day webinars
    • “Closer X 10X challenge” (example mentioned: 7 days of live 4-hour classes/day)

C — Infinite scalability assets (acquire/qualify/filter/educate)

  • Examples:
    • ebooks, audio, checklists
    • prompts/templates

C is framed as top-of-funnel and education/qualification.

Methodology requirement (no mentorship without a mechanism)

Mentorship should have a unique mechanism (not just “live content”).

Need:

  • clear processes
  • guidelines
  • internal nomenclature/protocols

If you only teach “how you do it” without naming/standardizing it, it becomes “a way,” not a mechanism.

Operational goal: prevent the founder from being a bottleneck—CS/delivery team must know the methodology.

Scaling operations by licensing the mechanism + building a delivery team

Transition logic:

  • Licensing the mechanism lets more people get results without linear founder effort.
  • As scale increases:
    • founder becomes less involved personally
    • price increases for the remaining high-proximity access
    • group/personalized delivery remains in tiers, but founder involvement declines

Follow-up cadence example

  • The team checks in every two days to force feedback and accountability.

Concrete pricing examples (ticket jumps by format)

Same underlying content can support very different pricing depending on delivery:

  • Ebook: ~R$97
  • Course: ~R$1,000
  • Group mentorship (weeks/modules): ~R$5,000
  • Individual consultation (personalized action plan): ~R$10k–R$30k (example ~R$20k)
  • In-person day of build/execution: ~R$50,000
  • “Done-for-you execution”: ~R$100,000/year mentioned

His own journey (proof via social evidence)

  • Ticket moved from ~R$6,000 up to ~R$40k–R$50k based on results and social proof.
  • Mentions multiple purchases (e.g., 8 ticket purchases in <2 years) to build confidence via evidence.

When the client can’t afford the top tier (downsizing guidance)

If the client can’t do S-tier, the recommendation is to:

  • shape rather than hard-downgrade to B/C

Example:

  • If individual mentoring is R$3,000 for 10 meetings, sell ~3 meetings at ~R$1,000 (maximum deliverable matching what they can pay).

Only move to B/C when needed; creating B takes time.

Recommendation: product stack / cross-selling (“main vehicle + accessories”)

Menu concept:

  • Main vehicle = highest-impact format (consulting/mentoring/coaching)
  • Bonuses = supporting materials (ebooks, scripts, prompts, worksheets, checklists, workshops, audios, recorded training)

Bonuses should:

  • enhance results faster/with less effort
  • not replace the main vehicle

Warning:

  • giving too much content can reduce perceived need for the paid tier.

Segmentation for personalization (example: nutritionist)

Example segmentation:

  • Location + demographics Example: women with gluten allergies in Jardins neighborhood, São Paulo

Rationale:

  • better ability to pay
  • more relevance/personal fit

Effort-reduction add-on example (“shopping/shipping to home”):

  • base monthly fee: R$500
  • delivery/shopping add-on: additional ~R$200–R$250/month
  • value justification: reduces decision friction and prevents impulse purchases

KPIs / targets explicitly mentioned (limited but present)

Not a formal KPI table, but explicit numeric benchmarks and operating targets:

  • Tier movement threshold: considered when reaching ~R$800k–R$1M/month revenue (he says: “when hitting some… 800, 900, 1 million per month, I’ll think about B”)

  • Cadence: follow-ups every two days

  • Success rate example: “over 50% success rate” when scaling with good outcomes
  • Validation timing/process example:
    • “first 10 meetings” generate the learning needed
    • improvements after around meeting 4 when he reports closing

High-level actionable playbook (condensed)

  • Define the offer as the measurable transformation (state X → Y).
  • Build the product as the delivery vehicle (promise stays consistent across tiers).
  • Start with S-tier (highest proximity + personalization) to validate quickly.
  • Force results using structured follow-up/accountability loops (Input → Output → Feedback).
  • Capture proof/social evidence, then increase price based on transformation + effort reduction.
  • Move to A/B/C only when you can standardize:
    • A: semi-collective / small individualization with method + delivery team
    • B: recorded training (scale + pipeline acceleration)
    • C: infinitely scalable assets to attract/qualify/filter
  • Operationalize with:
    • documented methodology
    • clear processes
    • delivery/CS team licensing to reduce founder bottleneck

Presenters / sources

  • Presenter/speaker: Igor (main instructor)
  • Referenced/mentioned individuals:
    • Francisco (background presence; meeting)
    • Francisco (Chico) (named in discussion)
    • Gabriel / Gabriel Cordeiro (examples)
    • João Víor (example question)
    • Mateus (participant question)
    • Bruno (referenced in a Q&A moment)
    • Enzo (example client)
    • Luiz (case example referenced in ads discussion)
    • Benhara and Quinta Moda (“experts” mentioned for script/objection-handling example)
    • Mari (referenced for price/ticket history)
    • Guilherme (participant; referenced for a point about transitioning)
    • TNS (referenced as the creator’s earlier subscription school context)

Original video