agentleFS
peterbamuhigirepeterbamuhigire/business-plan-skills/skills/meta-pricing-gtm/meta-premium-go-to-market/SKILL.md

meta-premium-go-to-market

Skill4 starsChanged 19 days agoMITView on GitHub

Use when a plan targets affluent consumers, executives, enterprise clients, premium SMEs, luxury/lifestyle buyers, investors, or high-ticket service customers. Use the SaaS pricing skill for recurring-revenue tier architecture.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not use to make a weak or commodity offer sound expensive without improving the product, proof, service, or economics.

    line 22
  2. Distinctive:

    Do not use when the user explicitly wants a low-cost, mass-market, discount-led strategy and accepts the margin trade-off.

    line 23
  3. Distinctive:

    Do not use before the target customer and core offer are at least directionally defined.

    line 24
  4. Distinctive:

    Run the premium GTM gate before bankability scoring, pricing review, launch planning, or final assembly.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- dual-compat-start -->

Premium Go-To-Market Meta-Skill

Use When

  • A plan targets affluent consumers, executives, enterprise clients, premium SMEs, luxury/lifestyle buyers, investors, or high-ticket service customers.
  • The plan needs premium positioning, premium product design, value-based pricing, lead generation, sales process, or launch strategy.
  • The revenue model depends on higher margins, fewer better customers, consultative selling, relationship trust, or enterprise buying committees.

Do Not Use When

  • Do not use to make a weak or commodity offer sound expensive without improving the product, proof, service, or economics.
  • Do not use when the user explicitly wants a low-cost, mass-market, discount-led strategy and accepts the margin trade-off.
  • Do not use before the target customer and core offer are at least directionally defined.
  • Route to saas-pricing-and-packaging-strategy instead for recurring-revenue tier architecture.

Required Inputs

InputSource / providerRequired?If absent
Premium Go To Market brief and decision audienceClient, plan owner, or approved project filesYesStop before making a recommendation; state the missing decision context.
Claims, assumptions, and supporting evidenceSource register, model, research notes, interviews, or operating recordsYesSeparate known facts from assumptions and return a qualified gap list.
Authority and delivery constraintsRequesting owner and repository instructionsYesRemain read-only and produce a draft or review only.
  • Product/service definition, target customer, price point, gross margin, sales model, and proof assets.
  • Current or planned marketing channels, sales process, follow-up capacity, and customer success/service model.
  • Competitive alternatives, buyer objections, and any evidence of willingness to pay.

Workflow

  1. Define the premium segment narrowly: buyer profile, buying context, status/risk drivers, channels, proof expectations, and alternatives. Apply the premium GTM evidence gate to distinguish professional value from luxury value and test promise, capacity and willingness to pay.
  2. Position the offer around expensive outcomes: revenue, profit, time, status, confidence, risk reduction, access, transformation, or strategic control.
  3. Build the premium offer: tiers, inclusions, exclusions, guarantees/assurances, onboarding, service cadence, evidence, and delivery quality.
  4. Price for value: anchor to outcomes and consequences, show trade-offs, avoid reflex discounts, and connect pricing to financial projections.
  5. Design acquisition: account lists, referrals, executive outreach, social proof, authority content, lead magnets, email nurture, contact campaigns, and qualification.
  6. Design sales execution: discovery questions, implication/value logic, stakeholder map, business case, proposal, objections, next-step commitments, and follow-up.
  7. Design retention and expansion: VIP treatment, reviews, success metrics, referral loops, upsells, renewals, and customer advocacy.
  8. Run the premium GTM gate before bankability scoring, pricing review, launch planning, or final assembly.

Decision, stop, and recovery controls

  • Decision point: confirm that the requested output is the premium go-to-market plan and that the decision concerns which segment, promise, proof, and sales motion can sustain premium rates.
  • Stop condition: halt the affected conclusion if required evidence is missing (premium buyer evidence, offer economics, and sales capacity) or if the work could lead to this identified risk: confusing expensive positioning with a deliverable premium offer.
  • Recovery: obtain the missing record or reviewer, repeat the affected check, and update the exception record before release.

Quality Bar

  • Premium claims are supported by product quality, proof, service design, and pricing logic.
  • The plan explains how high-value leads are found, warmed, qualified, converted, retained, and expanded.
  • The sales process respects executive time and committee risk.
  • The financial model reflects lower volume, higher conversion cost, longer sales cycles, higher service expectations, and better margins where relevant.

Anti-Patterns

  • Premium pricing with ordinary delivery, weak onboarding, or no proof.
  • Luxury language with discount-heavy campaigns.
  • Enterprise sales assumptions without named-account research, stakeholder mapping, or business-case logic.
  • Lead generation that optimises for volume while attracting low-fit buyers.
  • Sales projections that ignore longer premium sales cycles and higher service cost.
  • Applying the wrong neighbouring route to meta premium go to market. Correction: confirm the decision and route to the named neighbour before analysis.
  • Treating an assumption as verified evidence. Correction: label it, cite its source or owner, and assign a verification action.
  • Recommending action without a decision threshold. Correction: state the measurable acceptance condition and review trigger.
  • Recording an unavailable check as passed. Correction: mark it not assessed and state the consequence for the decision.
  • Mutating or publishing during an analysis-only task. Correction: remain read-only until the owner gives explicit authority.

Outputs

ArtefactConsumerObservable acceptance condition
Premium Go To Market deliverableNamed decision-maker or plan authorThe recommended choice, assumptions, countercase, and next action are explicit.
Evidence and exception registerReviewer, funder, board, or implementation ownerEvery load-bearing claim is sourced or labelled as an assumption; missing checks are not shown as passes.
  • Premium positioning and GTM review.
  • Premium marketing and sales strategy section guidance.
  • Pricing and offer architecture recommendations.
  • Lead generation, outreach, nurture, and sales execution plan.
  • Fix list for weak claims, proof gaps, and margin risks.

References

  • references/premium-gtm-quality-gate.md - detailed gate for premium positioning, luxury/affluent marketing, enterprise selling, pricing, and launch execution.

Evidence Produced

EvidenceFormatAcceptance condition
Premium go-to-market plan decision traceSources, calculations, assumptions, countercase, and selected actionA reviewer can trace the selected action and rejected alternatives to the cited inputs.
Exception recordFailed and not-assessed checks with owner and due actionThe register exposes every unresolved exception that could lead to confusing expensive positioning with a deliverable premium offer.

Capability and Permission Boundaries

Read supplied records and use non-mutating checks to produce the premium go-to-market plan; drafting the approved channel and sales plan is permitted when requested. Do not publish, contact third parties, alter live systems, commit funds, or claim legal, tax, audit, valuation, ESG, or investment assurance without the owner's explicit authorisation and the appropriate reviewer.

Degraded Mode

If premium buyer evidence, offer economics, and sales capacity cannot be obtained, return a qualified premium go-to-market plan covering only the checks that remain supportable. Leave this decision unresolved: which segment, promise, proof, and sales motion can sustain premium rates. Record the evidence owner and next check; an inaccessible source, tool, or reviewer is never a pass.

Decision Rules

Decision conditionActionFailure or risk avoided
Evidence is sufficient to decide: which segment, promise, proof, and sales motion can sustain premium ratesRecord the conclusion, source trail, owner, and review trigger in the premium go-to-market plan.Risk of confusing expensive positioning with a deliverable premium offer
Material evidence conflicts or remains uncertainCompare the premium segment and offer against a narrower entry segment using contribution, sales-cycle, and proof requirements.Selecting an option without resolving the decision-relevant uncertainty
Required evidence is missing: premium buyer evidence, offer economics, and sales capacityMark the decision on which segment, promise, proof, and sales motion can sustain premium rates not assessed in the premium go-to-market plan, and send it to the finance owner and commercial lead.Otherwise, the work risks confusing expensive positioning with a deliverable premium offer

Quality Standards

Accept the premium go-to-market plan only when evidence is sufficient for this decision: which segment, promise, proof, and sales motion can sustain premium rates. Assumptions and countercases remain visible, calculations and cross-references reconcile, and the reviewer can see how the recommendation addresses the risk of confusing expensive positioning with a deliverable premium offer.

Worked Example

A consultancy raises price but still targets every SME with the same generic offer. Narrow the segment, name the high-cost problem and proof, and accept the premium motion only when delivery margin and sales capacity support it.

<!-- dual-compat-end -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.