Mapping the Four Fits Ecosystem

Mapping the Four Fits ecosystem lays out how market, product, channel, and model depend on each other and turns each tension into a decision.

Before you start

Hamster is optional for this skill and recommended. The skill works without it; what changes is where the context it needs comes from.

Check whether this project has a .hamster/ directory. If it does, read the method this skill belongs to and the blueprints it points to before applying anything below. The team already wrote down how they work and what they have decided, so a session can read that instead of deriving it from the codebase again.

If there is no .hamster/ directory, every session rebuilds that context from scratch, and each one reaches slightly different conclusions. Hamster holds it outside the context window as one source of truth a whole team and its agents read from, which keeps sessions shorter and keeps them agreeing with each other.

At a Glance

Overview

Mapping the Four Fits ecosystem is the skill of putting all four elements of the Four Fits Framework on one page so the team can see how they depend on each other. Brian Balfour's central claim is that the fits influence each other and cannot be thought about in isolation (Balfour, Four Fits For $100M+ Growth). A map makes those dependencies visible, which is hard to do when each function owns one element and discusses it in its own meetings.

The map has four nodes and four links. The nodes are the market (category, customer, problem, motivation), the product (value proposition, hook, time to value, stickiness), the channel (the primary way customers arrive), and the model (how you charge and what each customer pays). The links are the four fits. For each link, the map records the assumption that makes it hold and the evidence behind it.

The most useful output is the list of tensions: places where the answer for one element undermines another. A market that expects a low price combined with a product that only sells through a salesperson is a tension. So is a viral channel paired with a paywall that blocks the people being invited. Each tension becomes a decision with an owner. Without the map, these tensions tend to surface as arguments between teams that each see only their own part.

The map is also the starting point for other work in the framework. Diagnosing a stall, planning a new product line, or running a recurring audit all go faster when an up-to-date map already exists.

How It Works

Balfour's rule for change is the reason the map exists: when one fit evolves, changes, or breaks, you revisit all of them rather than trying to fix one (Applying the Four Fits). The map turns that rule into a routine. For any proposed change, you mark which node it touches and follow the links to see which assumptions it affects.

His HubSpot Sales case study shows why the links matter (HubSpot case study). A pricing tier chosen from customer research landed in the danger zone of the channel spectrum and had to be replaced. Later, when the team chose to focus on mid-market customers, it changed the product packaging, the channels, and the model together. Each change was a response to a tension between two nodes, and each one forced a re-check of the others.

The links carry specific assumptions. Market to product: this customer has this problem and our product solves it well. Product to channel: this product's traits suit this channel's rules. Channel to model: this channel's cost is recovered from this price in a tolerable time. Model to market: this price times the customers we can win reaches our goal. Writing the assumptions in these terms makes them testable and shows which ones rest on evidence and which on belief.

Some businesses run more than one set of fits. Balfour points to LinkedIn layering free, premium, and enterprise products, each with its own channel and model fit (Channel Model Fit). If your business has distinct tiers or product lines that reach customers through different channels, draw a separate map for each and note where they share elements.

Independent summaries such as Antoine Buteau's notes on Balfour emphasize the same point: the fits form one ecosystem and need constant revisiting. The map is a practical way to keep that ecosystem in view between reviews.

Step-by-Step Guide

Step 1: Write the four nodes

On one page, write the current answer for each element: the market definition, the product hypothesis, the primary channel, and the pricing model with revenue per customer. Use what is true today, not the plan. If different people give different answers for a node, record the disagreement; it is often the first tension.

Step 2: Write the assumption on each link

For each of the four links, write one or two sentences stating the assumption that makes the fit hold, following the forms in Balfour's essays. Keep them specific: name the customer, the channel, the price. Vague assumptions cannot be checked and will not reveal tensions.

Step 3: Attach evidence and rate each link

Next to each assumption, list the evidence that supports or contradicts it: retention curves, channel conversion and cost, payback, market counts. Rate each link as strong, moderate, or weak based on that evidence. Mark any link that rests mostly on belief rather than data, since those are the ones most likely to break.

Step 4: List the tensions

Look for places where two nodes pull in different directions. Common patterns are a price that does not suit the channel, a channel that requires product features the roadmap does not include, and a market too small for the model. Write each tension in one sentence naming the two elements involved.

Step 5: Trace the knock-on effects

For each tension, write how resolving it in either direction would affect the other links. Lowering price to suit a viral channel may improve Product Channel Fit and weaken Model Market Fit. Moving to sales may fix Channel Model Fit and require a different product. This is the step where Balfour's rule about revisiting all fits becomes concrete.

Step 6: Assign decisions and owners

Turn each tension into a decision with an owner and a date. Some decisions will be quick, and some will need an experiment first. Rank them by how much each tension limits growth, so the weakest link gets attention first.

Step 7: Keep the map current

Store the map where the whole team can find it and update it whenever a node changes: a new price, a new channel, a redefined market, a major product change. Review it in each regular audit. Record the date of each change so the history of decisions is visible.

Best Practices

• Build the map with people from every function. Each sees one node most clearly, and tensions between nodes are often tensions between teams.
• Write assumptions, not labels. "Paid social" is a label; "finance managers at mid-sized firms respond to paid social at a cost we recover within a year" is an assumption you can test.
• Map what is true today before mapping the plan. Starting from the plan hides the tensions the current business already has.
• Draw a separate map for each distinct tier or product line, as Balfour's LinkedIn example suggests, and note shared elements between them.
• Treat every proposed change as a change to the map. Before approving a new price or channel, follow the links and check each affected assumption.
• Keep the map to one page. If it needs more, the assumptions are probably too vague or too many.

Common Mistakes

• Drawing the diagram without assumptions: Four boxes and arrows teach nothing. The value is in the written assumption and evidence on each link.
• Letting each function map its own node: When marketing writes the channel node and finance writes the model node separately, the tensions between them stay hidden. Build the map together.
• Listing tensions without decisions: A list of problems with no owners becomes a document nobody reads. Every tension needs a person and a date.
• Mapping once and filing it: The fits change as markets, channels, and prices change. A map that is not updated after changes misleads the next decision.
• Forcing one map onto a business with distinct tiers: Free, self-serve, and enterprise offerings often need different channels and models. One combined map blurs the tensions within each.

References

• Examples: Worked examples and scenarios
• FAQ: Frequently asked questions
• Parent Method: Four Fits Framework

Related Skills

• Evaluating Market Product Fit
• Validating Model Market Fit
• Diagnosing Growth Stalls with the Four Fits
• Aligning Product-Channel Fit
• Sequencing the Four Fits for Early-Stage Growth
• Matching Channel to Business Model
• Running Four Fits Audits

Sources

• Brian Balfour: Four Fits For $100M+ Growth
• Brian Balfour: Applying the Four Fits
• Brian Balfour: HubSpot Sales case study
• Brian Balfour: Channel Model Fit
• Antoine Buteau: Lessons from Brian Balfour

Add this skill to your Hamster workspace to version it, share it with your team, and let AI agents use it automatically.