How to differentiate when features are free
When a competitor includes your features for free, treat that free option as the real alternative. Name the cost the buyer still pays in time, risk, gaps, or a person who has to run it. Put your difference on the customer, the workflow depth, the data, or the service the free tool leaves unfinished.
On this page
A free tool is a competitive alternative
April Dunford puts competitive alternatives first. They are what the buyer would do if your product did not exist. A free tier, a suite that bundled the feature, an open source project, or a spreadsheet all count. The price of that option can be zero and it can still be the thing you have to beat. The page on competitive alternatives is how to find which one your customers actually use. The page on when competitors copy you is the related case, where a feature you used to own becomes common. This page is the case where the common feature is already free.
Free still has a cost
Buyers who pick the free option are paying with something else. That cost can be time, a person who checks the work, a gap in the workflow, or the risk that the free tool misses a rule the business runs on. Your difference has to be one of those costs, stated in their words, with proof you can show. Dunford’s value step asks what a unique attribute lets the customer do. "We have the feature too" fails that step. "The dispatcher stops rechecking delivery windows by hand" can pass it, if that is true and the free tool leaves the rechecking in place. Lasting differences tend to sit in focus on one customer, data you alone have, a process or a service, a business model, or depth in one workflow. A feature checklist is the part a free bundle can match.
Change what the buyer scores
Dunford writes that you can use what is unique about the product to change the way buyers think about the market category. If the scorecard is "who has route stops," and a free map just added route stops, that scorecard now favors the free map. A frame that names the job the free map still leaves open gives the buyer a different scorecard. The market category page is how you pick a frame buyers already understand. For a developer tool, the free alternative is often a library or a platform default. The value proposition for developer tools page writes that line. For an open source project, the free code and the paid offer have to be sayable as two different things. The open source page covers that split.
What to put on the page
| On the page | Why it helps | What to skip |
|---|---|---|
| The free option, named plainly | The buyer already has it in mind | Pretending the market starts at your price |
| The job the free option leaves | This is the cost of zero dollars | A feature grid that matches the free tool line for line |
| Who feels that leftover job | Narrows the best-fit customer | "Everyone who needs the feature" |
| Proof they can check | A workflow, a sample, a limit you will state | Adjectives such as robust or modern |
Fictional walkthrough
Fictional. Acme Route is not a client. It plans delivery routes for small distributors. A free maps product adds route stops and a share link. The feature list now looks the same, and the maps product is already on the dispatcher’s phone. The founder reads the last six won deals. In four of them the buyer had tried the free map. They came to Acme Route because the map did not know the truck that was in the shop, the weight limit on a bridge they use, or the delivery window the customer was promised. The dispatcher was still checking those by hand after the map drew the line. The founder writes the difference as that leftover work. Customer: dispatchers at distributors with more than one truck and promised delivery windows. Alternative: the free map, plus a person rechecking the rules. Value: the route respects the windows and the truck that is actually available. Category: route planning for small distributors, so the buyer is shopping for that job and the free map sits in the "what we use today" column. An illustrative line: "Route planning for distributors whose delivery windows do not fit on a free map." The homepage shows one route with a window that would have broken, and the rule that caught it. The founder leaves the share-link feature off the first screen. The free map already has one. The incumbent page is the same shape when the free feature sits inside a suite the buyer already pays for.
Steps
Name the free option
The tool, the suite, the library, or the spreadsheet they would use.
Ask what they still do by hand
From won and lost deals, in their words.
Write that leftover work as the value
One job the free option leaves on their desk.
Name who feels it every week
That person is the best-fit customer.
Pick a category that makes the job obvious
A frame where the free tool is the old way, and your product is the fit.
Put proof next to the claim
A sample route, a rule, a before and after from your own product. Skip borrowed numbers.
FAQs
Should we cut our price to match the free tool?
A lower price can be a business model choice. It is a weak position if the page still says you have the same features. Name the job the free tool leaves unfinished, and charge for that job if customers pay for it.
Should the homepage name the free competitor?
Name it when buyers already compare you to it. On the first screen, the job and the customer come first. A comparison page or a sales answer can name the product.
What if the free tool really does the whole job?
Then the gap is the product, and positioning can only make a real difference obvious. Talk to customers who pay you and write down the job they still need.
Is open source the same situation?
It is one version of it. The free project is an alternative. Your paid offer has to say what the project leaves for the buyer to staff. The open source page on this site is that split.
Sources
See this on your own homepage
In no time at all Blake sent us the copy and positioning we've been looking for.