MAKIN 
The comparison is real, so answer it.
Dismissing the subscription makes you look defensive. It genuinely does part of the job for a fraction of the price. Say which part, and be specific about the part it does not do — usually the configuration, the migration and the decisions nobody on the client side has time to make.
Price the outcome, not the hours.
Hourly pricing invites a comparison with a licence fee and loses it. Pricing a defined outcome — live in six weeks, this migrated, that integrated — puts the conversation on ground where the subscription cannot compete.
Name what happens without you.
The honest framing is that the tool arrives empty. Somebody has to model the data, move the history, train the team and own it when it breaks. If the client has that person, recommend the tool. If they do not, that is the service.
Be willing to lose the small ones.
Some engagements genuinely should be a subscription. Saying so costs one deal and earns the credibility that wins the next three. Trying to win everything is what pushes service pricing down to where it cannot sustain quality.
Split the job before you price it
Before quoting, write the client’s problem as a list of jobs and mark the ones the subscription does as shipped. It is usually the software part: storing records, sending reminders, drawing charts. What remains is the part you are pricing. Doing this in front of the client turns ‘why should I pay you more than the app’ into a conversation about a list both of you can see and argue with.
- Jobs the tool does out of the box
- Jobs the tool can do once someone configures it
- Jobs it cannot do at all: migration, cleanup, connecting to systems it does not support
- Decisions only the client can make, which someone has to draw out of them
- Ownership after launch: who fixes it, and who trains the next hire
Compare the whole cost, not the monthly fee
The subscription fee is the visible part of the cost. The rest is time the client’s own people will spend setting it up, moving data, working around a half-configured system and, if it goes wrong, paying someone to fix it. You do not need invented numbers to make the point. Ask the client to estimate it: who on their team would do the setup, what that person stops doing meanwhile, and what it costs the business if the switch drags on.
Then put both options side by side honestly, with the client’s own time written into the tool’s column. If the tool plus that time is genuinely the cheaper route and they have the person to own it, say so plainly. A recommendation is only worth something if you are seen to make it against your own interest.
Write the outcome so it can be checked
Pricing an outcome only works if the outcome is specific enough to verify. ‘CRM implementation’ invites a comparison of hours with a licence fee. ‘Your existing leads imported, deduplicated and assigned, and the sales team working from it every day’ does not. A checkable outcome says what will be true at the end, what is deliberately left out, and what the client has to supply for it to happen.
- The end state, in the client’s words rather than yours
- What is included and what is excluded
- What the client must provide, and by when
- How both sides will know the work is done
- What happens to the price if the scope changes
Publish a starting price
Hiding prices until a call can make the subscription look more attractive still, because its price sits on a public page and yours is a mystery. We publish a starting price on every package on our price list, and the fixed price arrives in writing after the scope call. A visible starting price anchors the conversation on the outcome, and it lets clients who only need the tool rule themselves out before anyone’s time is spent.
Offer a rung between the tool and the full service
The choice does not have to be subscription or bespoke build. A productised middle option, such as a fixed-scope setup package or a finished product the client rents or buys, gives the careful buyer a way to start with you without committing to the full engagement. On our own list, products can be bought outright with full source code or rented on a monthly licence. What matters is not the model but that the client can see a next step when they outgrow the first one.
Questions that decide whether to recommend the subscription
Being willing to lose the small ones needs a consistent test, or it turns into a mood. We ask the questions below on the call. If the client has the person, clean data and a process that fits the tool, recommend the tool and mean it. If not, the gaps the answers reveal are the scope of the work, and the price follows from them.
- Does someone on your team have the time to set it up and own it?
- Is your existing data clean enough to import without rework?
- Does the tool connect to what you already run, such as Tally or your WhatsApp enquiries?
- Will your process fit the tool, or does the tool have to bend to your process?
- What happens when the person who set it up leaves?
What not to say when the subscription comes up
The reflexes that feel safest in the moment are the ones that do the most harm here. Each of the following sounds reasonable on the call with the client, and each quietly moves the comparison back onto ground where the subscription wins.
- Criticising the tool: the client may already like it, and you want it on your side if it turns out to be the right answer
- Matching the price by quietly cutting scope, so the gap comes back later as a dispute
- Quoting a day rate, which puts your hours straight next to the licence fee
- Promising the tool will do something it was never built to do
- Discounting to win an engagement that should have been a subscription