Skip to main content
GullySystem
A practical guide

Everyone likes the idea but nobody pays: what the pilot is telling you

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 4 min read

In this guide 6 sections
The short answer

Praise without payment means the problem is mild, the buyer is someone else, the price or timing is off, or a free rival already exists. Put a real charge in the first release. Then sort each refusal by its reason: price, timing, role or alternative.

Compliments cost nothing

People say “this is great” to be kind, to end a call or to keep a door open. Nothing is lost by saying it. A payment, a signed purchase order or a deadline set by the user costs them something, which is why it counts.

Sort what you hear into three piles. Praise is words. Interest is effort, such as sharing data, bringing a colleague or asking when it launches, and intent is money, a signed letter or a date they will switch.

Most pilots overflow the first pile and starve the third. That gap is the finding.

  • Words: “looks good”, “we should use this”
  • Effort: uploads data, invites a teammate
  • Commitment: pays, signs, sets a switch date

Put a real charge into the first release

You cannot read willingness to pay from a free product. Add a checkout step to the release, even a payment link behind a button. Ask for the full price rather than a token amount that makes refusal feel silly.

Present the charge plainly. State what they get, for how long, and what happens if it does not work for them, since a refund promise lowers the fear of saying yes.

Track three counts: users who saw the price, users who started paying and users who finished.

Read each refusal by price, timing, role or rival

Ask every user who declines one short question and write the answer word for word. You will find four families of reasons, and each points to a different fix.

Price refusals say the value does not match the figure. Timing refusals say the problem is real but not this quarter. Role refusals say the person who liked it cannot approve spending. Rival refusals say a spreadsheet already does enough.

Do not argue. A refusal explained is worth more than a sale won through persuasion.

  • Price: value not clear at this figure
  • Timing: budget or season is wrong
  • Role: user cannot approve spending
  • Rival: current workaround is good enough

Find the real buyer

In many businesses the person who uses the product and the person who pays for it are different. A warehouse supervisor may love a dispatch screen while the owner decides on spending. Your pilot may have recruited the wrong person.

Ask who signs off, who pays and who loses if the problem continues. Then ask for ten minutes with that person, supervisor present, and show a one-page result from the pilot rather than the app.

If the payer sees no pain, the idea may be a feature, not a product.

Decide what the pattern says

Count refusals by family. A cluster in price may call for a smaller first plan. A cluster in role calls for a different target customer. A cluster in rival is the hardest, because your product must beat free.

Set a rule before the next round: how many paid users, out of how many invited, would convince you to continue. Writing the number down stops hope from moving the goal.

Then run a second, tighter pilot with one change only. That way the result can be traced.

Pilot refusal log

A one-page log with a row per pilot user. Columns are name, role, whether they pay or approve, price shown, the exact words of the answer, refusal family (price, timing, role, rival) and next step. A summary box below counts each family and records the continue threshold you set beforehand.

Open a blank worksheet to print

Questions owners ask

How many pilot users do I need before the result means something?

There is no magic number. Ten to thirty well-chosen users who match the real buyer give a clearer signal than a hundred curious ones. Look at who they are before counting how many.

Should I lower the price when nobody pays?

Not first. Learn why they refuse. If the reason is price, test a smaller plan. If it is role or rival, a lower price will not change the answer and only weakens your position.

What if users say they will pay later?

Ask for a date and a small deposit or signed note. A vague later usually means no. A named date with a person attached is a real commitment.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Share Your Requirements