agentleFS
NickKostovnyNickKostovny/marketing-playbooks/skills/saddles-positioning/SKILL.md

saddles-positioning

Skill0 starsChanged 2 months agoMITView on GitHub

Apply at strategic positioning moments — when Nick is wrestling with "what are we actually selling," "what business are we in," "how do we position against X," "are we a [LIMS/PAT tool/data platform/instrument]," "what's our pitch frame for [investors/major customer]," or any conversation about customer journey, onboarding friction, first-use experience, repositioning, category framing, or major launches. Also trigger on product strategy decisions evaluated through a marketing lens (pricing, packaging, roadmap, sales motion). Use proactively when conversations operate at "what are we?" altitude rather than "how do we say it?" altitude. Do NOT fire on content review, copy editing, channel decisions, or tactical campaigns — those belong to brand-marketing-framework, content-proportion-check, defensibility-check, writing-craft, or hamming-taste-principles. One level upstream of those.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    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:

    When the conversation is about a tactic (a campaign, a deck, a landing page, a sales script, a pricing model, a roadmap decision), the …

    line 42
  2. Distinctive:

    If the answer is no, the positioning is describing the product, not the transformation.

    line 64
  3. Distinctive:

    The discipline: When Nick is making a strategic decision — a positioning move, a campaign theme, a customer journey choice, a product …

    line 98
  4. Distinctive:

    This question is a generative tool, not a tagline: Don't use the answers as marketing copy verbatim — they're often too aspirational and …

    line 103
  5. Distinctive:

    When a positioning insight emerges from practitioner conversations or content tests, ask: *does this change anything we should be doing in …

    line 119
  6. Distinctive:

    When a product decision is being made (a feature, a workflow change, an onboarding step), ask: *does this serve the transformation we're …

    line 122
  7. Distinctive:

    If the assertion sits untested for a meaningful period, prompt for low-cost validation: a few practitioner conversations, a content test, a …

    line 202
  8. Distinctive:

    When in doubt about precedence: this skill's principles are inputs to other skills' decisions, not overrides of them.

    line 233
  9. Distinctive:

    When this skill triggers, the move is usually one of these:

    line 242
  10. Distinctive:

    Pull the altitude up: If the conversation is at the tactical level ("how should this landing page read?") but the strategic question hasn't …

    line 244
  11. Distinctive:

    Force the right-side answer: If Nick is making a positioning claim, ask him to express it as *what changes for the practitioner* — not as …

    line 248
  12. Distinctive:

    Run the becoming question: When a strategic decision is being made, ask: *which version of the practitioner does this serve?* Use the …

    line 251
  13. Distinctive:

    Test the category assertion: When Nick or anyone else asserts a category position, ask whether it's been validated and on what evidence.

    line 254
  14. Distinctive:

    Apply the execution-tolerance test: When a customer-facing surface is being designed or reviewed, run the hangry-skeptic check.

    line 258
  15. Distinctive:

    Watch for one-way thinking: When marketing is being treated as a downstream translation of product decisions, name the dialectic.

    line 261

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Saddles Positioning

Source: Stewart Butterfield's July 31, 2013 memo to the Tiny Speck team, "We Don't Sell Saddles Here," written two weeks before Slack's preview release. Steve Blank called it "still the best description" of how to position a disruptive product.

This skill encodes a specific strategic discipline: forcing the question of what Invert is actually selling into conversations that would otherwise drift to how Invert says what it sells. It is deliberately higher-altitude than the marketing layer skills. When it fires, it should reframe the conversation, not contribute another principle to a content review.


The Core Move

What you sell ≠ what you ship.

  • Slack ships group chat software. Slack sells organizational transformation.
  • Acme ships saddles. Acme sells horseback riding.
  • Lululemon ships athletic wear. Lululemon sells yoga.
  • Harley ships motorcycles. Harley sells freedom.
  • Invert ships software for bioprocessing data. What does Invert sell?

The skill's job is to make Nick answer the right side of that equation, in concrete terms, before he answers any tactical question downstream of it.

When the conversation is about a tactic (a campaign, a deck, a landing page, a sales script, a pricing model, a roadmap decision), the right side of the equation is the test: does this tactic deliver the transformation Invert is selling, or only the product Invert ships?


The Four Moves

1. Sell the Transformation, Not the Product

Butterfield's claim: "People buy software to address a need they already know they have... we will find many more buyers" if Invert sells a result, not a feature set.

For Invert, the transformation is something like: "From data fragmentation and tribal knowledge to a state where any practitioner can see their process clearly, in context, fast enough to act." The exact phrasing is Nick's to refine — but the move is to express it as what changes for the practitioner, not what the software does.

The test for any positioning claim:

"Could a practitioner who has never seen Invert read this and say what's different about their work life if they adopt us?"

If the answer is no, the positioning is describing the product, not the transformation.

Invert-specific application:

  • The instrument framing (already in brand-marketing-framework) is the how of this move — Invert shows up in the practitioner's methodology. This skill governs the what — the larger result the practitioner is buying. The two are complementary: instrument framing protects against vendor-y language; transformation framing protects against feature-y substance.
  • The transformation differs by ICP segment:
    • For CDMOs: throughput, fewer hours on data wrangling, faster reporting cycles — the transformation is operational leverage.
    • For development teams: seeing things they couldn't see before, surfacing findings they weren't looking for — the transformation is scientific reach.
  • Marketing that picks the wrong transformation for the audience fails harder than marketing that uses the wrong words for the right transformation.

The anti-pattern to watch for: Conversations that start strategically ("what are we selling?") but collapse to feature lists within ten minutes. When that happens, this skill should pull the conversation back up.

2. Ask "Who Do We Want Our Customers to Become?"

Butterfield's framing: every product asks something of its customers — to do things differently, to think of themselves differently. The reward for that ask has to be commensurate with the cost.

The generative question is: who is the practitioner becoming when they adopt Invert?

For Invert, candidate answers worth Nick testing:

  • A scientist who can answer questions about their process in minutes instead of weeks
  • A tech transfer lead who walks into review meetings with the data already organized
  • An MSAT engineer who is the person their team comes to when something goes wrong, because they can see the whole batch history at once
  • A CMC specialist whose regulatory submissions are built from the same data their process development teams trust day-to-day

The discipline: When Nick is making a strategic decision — a positioning move, a campaign theme, a customer journey choice, a product priority — this skill prompts him to ask: which version of the practitioner does this decision serve? If the answer is "all of them, generically," the decision is under-specified.

This question is a generative tool, not a tagline. Don't use the answers as marketing copy verbatim — they're often too aspirational and too inward-facing. Use them to anchor what Invert is trying to deliver, then let the language layer (content-proportion-check, defensibility-check) translate it into practitioner-defensible prose.

3. Work Product and Market as a Dialectic

Butterfield: "The product itself and the way people use it should suggest new ways of articulating the value — and refinements to how we communicate the value should lead to principles which clarify decision-making around product features and design."

This is two-way. Most marketing frameworks treat the relationship as one-way: product gets built, marketing translates. The Saddles frame says: marketing insights about how customers receive Invert should change product decisions, and product realities should constantly refine the messaging.

The discipline for Nick:

  • When a positioning insight emerges from practitioner conversations or content tests, ask: does this change anything we should be doing in the product? That question is appropriate for Nick to raise even though he's not running product.
  • When a product decision is being made (a feature, a workflow change, an onboarding step), ask: does this serve the transformation we're selling, or does it serve the software we're shipping? The two are not always aligned.

The compounding effect: The marketing layer becomes a feedback channel into product, not just a downstream translation layer. This is one of the few legitimate places where a marketer in a practitioner-dominated company can earn credibility with the founders — by closing the loop between how customers actually receive the product and what the product should become.

4. Apply the Execution-Tolerance Principle

Butterfield: "When you want something really bad, you will put up with a lot of flaws. But if you do not yet know you want something, your tolerance will be much lower."

This is the move with the sharpest implications and the least overlap with anything else in the skill library.

The principle: Invert's prospects are mostly in the "don't yet know they want it" bucket. They have working tools. Their current fax machine works fine. Every petty irritation in the first fifteen minutes of contact with Invert — a slow page, a confusing label, a broken email link, a demo that requires too much setup, a sales call that doesn't connect to their work — is more expensive than it would be for a known-want product.

The discipline: Apply ruthless beginner's mind to every customer-facing surface. Not just content — the whole experience.

Concrete tests:

  • The hangry-skeptic test: imagine the practitioner who was forced into a demo by their boss, hasn't had breakfast, and has a deadline this afternoon. Does the experience reward their attention or punish it?
  • The first-fifteen-minutes test: from the moment a practitioner first encounters Invert (a tweet, a conference booth, a cold email, a referral) to fifteen minutes later, what is the cumulative signal? Every touchpoint either pulls them along or gives them a reason to drop out.
  • The petty-irritation inventory: when Nick uses Invert's website, demo flow, sales materials, onboarding sequence, or first-run experience, what irritates him? Those irritations are larger for a skeptical first-timer than they feel for an insider.

Why this principle is uniquely valuable for Nick's role: Most of these irritations aren't marketing's job to fix in the strict sense — they're product, sales, ops. But because Nick's seat sits at the intersection where strangers first meet Invert, he is the person most likely to see them and most credibly positioned to escalate them. The skill's job is to make that escalation a habit, not an occasional act.


The Category Question (Hypothesis-Grade)

Status: hypothesis-grade. Treat as an open question, not a settled position.

Butterfield's most aggressive claim is "the best possible way to find product-market fit is to define your own market." That worked for Slack because internal team comms was a real greenfield — the existing tools (email, IRC, Hipchat) didn't constitute a coherent category.

Invert's situation is different. Bioprocessing data analysis is not unserved. It's served by a patchwork: Excel, JMP, Spotfire, batch records, LIMS systems, MES platforms, manual analysis, tribal knowledge. The "current fax machine works fine" dynamic applies. But Invert isn't creating a category from whole cloth — it's collapsing several existing categories into one frame.

The reframe Nick should test: What if Invert isn't defining a new category, but collapsing existing ones? Possible collapses to test:

  • Data infrastructure + analytics + reporting → one practitioner-facing instrument
  • Process development tools + tech transfer tools + manufacturing oversight → one continuous data layer that follows the molecule
  • Spreadsheet-based ad-hoc analysis + formal LIMS workflows → one environment where rigor is the default rather than the ceiling

Why this matters strategically: The "create a new category" stance and the "collapse existing categories" stance lead to different marketing investments:

  • Create a new category → invest heavily in evangelism, education, defining vocabulary, conference talks that name the new thing, content that asserts a new way
  • Collapse existing categories → invest in displacement narratives, comparative content that shows why the patchwork is the problem, customer stories that demonstrate what becomes possible when the seams are gone

The right answer changes the marketing strategy materially. This skill's job is not to settle the question — it's to keep the question live.

When Nick or others assert a category position with confidence, this skill should ask: have we validated which of these we're actually doing? With which practitioners? On what evidence?

If the assertion sits untested for a meaningful period, prompt for low-cost validation: a few practitioner conversations, a content test, a sales-call analysis on how prospects describe what Invert replaces.


How This Skill Relates to the Rest of the Library

This skill sits upstream of the marketing layer. The relationship:

  • brand-marketing-framework governs how Invert shows up in the world (instrument positioning, awareness, trust, intrigue, content as genuine value). This skill governs what Invert is showing up to sell. When both apply, this skill answers first; brand-marketing-framework executes against the answer.
  • content-proportion-check governs whether claims in specific content are proportional and evidence-grounded. This skill governs whether the underlying thing being claimed is the right thing. A piece of content can pass proportion-check and still be selling the wrong thing.
  • hamming-taste-principles governs the emotional register of Invert's content — aspirational, hypothesis-grade. This skill governs the strategic register of Invert's positioning — also hypothesis-grade in places (the category question), but more load-bearing than taste.
  • strategy-decisions (Hoffman's two rules) governs how Nick makes decisions under uncertainty. This skill governs the substance of one specific class of decisions — positioning decisions. They compose: use Hoffman's framework to decide whether to commit to a positioning move; use this skill to decide what positioning move is worth committing to.
  • defensibility-check and writing-craft govern sentence-level quality. This skill never fires at sentence level.

When in doubt about precedence: this skill's principles are inputs to other skills' decisions, not overrides of them. If this skill's transformation framing conflicts with a content-proportion-check proportion test, proportion-check wins — because a true transformation poorly substantiated is still unshipped.


How to Apply in Conversation

When this skill triggers, the move is usually one of these:

  1. Pull the altitude up. If the conversation is at the tactical level ("how should this landing page read?") but the strategic question hasn't been answered ("what are we selling on this page?"), name the gap and pull the conversation up before going down.
  2. Force the right-side answer. If Nick is making a positioning claim, ask him to express it as what changes for the practitioner — not as what Invert does. If he can't, that's the work.
  3. Run the becoming question. When a strategic decision is being made, ask: which version of the practitioner does this serve? Use the candidate answers from Move 2 above as anchors.
  4. Test the category assertion. When Nick or anyone else asserts a category position, ask whether it's been validated and on what evidence. Prefer the collapse reframe over the greenfield reframe until evidence says otherwise.
  5. Apply the execution-tolerance test. When a customer-facing surface is being designed or reviewed, run the hangry-skeptic check. Surface petty irritations as strategic, not cosmetic.
  6. Watch for one-way thinking. When marketing is being treated as a downstream translation of product decisions, name the dialectic. Ask what the marketing layer is learning that should change product, and what the product is learning that should change marketing.

When NOT to Apply

This skill should not fire when:

  • Nick is reviewing copy or content for language quality (use content-proportion-check, defensibility-check, writing-craft).
  • Nick is choosing among marketing tactics or channels (use brand-marketing-framework).
  • Nick is sending an internal status update (use uncertainty-killer).
  • Nick is editing a Slack message or email (use writing-craft, pre-send-checkpoint).
  • The conversation is firmly inside an already-settled positioning frame and the work is execution.

The skill earns its keep by triggering rarely and well. Triggering on every marketing conversation would make it noise.


Closing

"There's no point doing this to be small."
— Butterfield

The Saddles memo's deepest move is one of seriousness — the insistence that the work be aimed at something larger than itself, and that every detail be in service of that larger aim. For Invert, that means refusing to settle for "we built bioprocessing software that works." The standard is whether practitioners' working lives change.

This skill exists to keep that standard in the room.

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.