Have you ever looked at reviews for restaurants you’ve already been to? Am I the only weirdo who does that?

I know I’m an oddball. But humor me and go do it.

You’ll find a few surprises, I’m willing to bet. I’ve always been dumbfounded by some of the reviews I land on.

“This omakase was not worth the money and I was still hungry leaving the restaurant.”

“The waiter we had was snooty and the pasta lacked flavor.”

My experiences at those restaurants couldn’t have been more different. The reviewed sushi spot was one of the best I’d ever been to. And the described Italian place delivered an elaborate pasta tasting menu at their chef’s counter.

 Over the past decade, hundreds of founders and startup operators have come to me for coaching on their sales and go-to-market challenges. And I’ve done my best to help. In the series unfolding in the coming weeks, we’ll cover the essentials needed for a sturdy sales process, and the factors to consider when you go about designing it. You’ll walk away with the necessary tools to start engineering your process from scratch, and the things to look out for as you take it to market for refinement. So sit tight. Tune in. And, as always, be loud with your questions. Here’s your fourth installment.

What I’ve come to realize over the years is that people’s opinion of the same product or service can vary wildly. It depends on the lens through which they look at life. Their relationship to money. Their current mood. The quality of their day leading up to the experience.

What some interpret as pretense, others consider elegant. What some view as refined, others see as finicky. What some experience as delicate, others miss altogether.

My point? When we rely on people’s feelings to define success, we don’t get a singular view of the same experience. We get a wide variety of different perceptions.

Which is a problem. Especially in a pilot or free trial.

Last week, we talked about controlling the sale. Selling the next step. The Account Optimization Call as a forcing function. Arming your champion when you can’t be in the room. All of it driven by the same north star: tightening the screws everywhere you can, because variance is the enemy of repeatability.

This week, and next installment, we’re zooming in on two of the highest-leverage moments where founders quietly hand control back to the prospect. Today: pilots and free trials. Next time: the proposal review.

Let’s get into it.

 

Here’s the trap most founders and startup operators fall into. The prospect makes it into a pilot or a free trial. They’re excited. And the founder — wanting to be customer-centric and helpful — asks some version of, “What would you like to accomplish during this pilot?”

Sounds reasonable. Collaborative, even.

And yet, it’s a disaster.

Because now you’re back in the restaurant review section. You’re asking ten different humans, with ten different lenses, ten different relationships to your problem space, to define success. And they will. In ten incompatible ways.

You’ll find yourself contorting yourself, trying to satisfy a kaleidoscope of expectations. Some achievable. Others regrettably not. Some on-product. Others off.

Not a role you want to play.

You want to be the one defining success. Not asking the customer to define it for you.

Flash back to early Whitetruffle

After Mike Morrell’s advice on keeping our motion lightweight. After I’d instituted the Account Optimization Call as a forcing function to get qualified prospects onto the trial. We’d gone from two-thirds of qualified prospects ghosting the signup link, to most of them showing up and getting onboarded.

I set my sights on a new problem I was now facing down-funnel.

I had qualified prospects on a 14-day credit-card-activated free trial. And I needed them to convert. Automatically. Through the magic of credit card processing, on day 15, if they were satisfied.

So I asked myself: ‘How do I make sure we convert a large chunk of trials into paid customers? How can I set expectations? Expectations we’d clear often. That also feel valuable to our customers?’

I needed to control the sale during the trial, the same way I’d controlled it everywhere else.

The first place I turned was our analytics dashboard. If ARR was our number one company metric, introductions were a close second.

Quick refresher for newer readers: Whitetruffle was a tech talent sourcing platform. We called ourselves a “dating site for tech talent.” Our algorithm matched software engineers, product managers, UI/UX folks and designers with companies looking to hire them. Employers, our paying customers, would get daily matches. Any match they said “Yes” to triggered a message to the candidate: “Yelp is interested in chatting with you. Want to get connected?” If the candidate said “Yes,” an introduction was made through the platform.

Classic double opt-in. And introductions were critical, because they were the leading indicator of marketplace liquidity. The more intros we delivered, the more value both sides were getting.

I dug in and looked at how many intros our trial customers were getting on average during the 14-day window. The number was 4 to 5.

So on the Account Optimization Call, I started telling new trial customers something specific:

“You can expect to get 2-3 intros during your fourteen-day free trial with us.”

Narrative for success: set.

From that moment on, about 60% of our trials converted to paid. Perhaps the part of the funnel I was most proud of.

Why it worked

Three things were doing the work. And these three components are what you could try to recreate for your own product.

The first? The narrative was anchored to an objective metric tied to value derivation from our product. There’s no arguing with a metric. As a matter of fact, when trial customers would reach out mid-trial complaining about their lack of intros, I’d pull up their account. If they were doing well objectively, I’d respond, “You guys are seven days into your trial and already have 3 intros. That’s a lot more than most. You’ve gotten the number of intros we’d expect for the entire trial! Candidates are responding very well to you guys. You’re a sexy company.” That helpful reframe would most often get the trial customer to calm down and rethink how they’d initially perceived their experience.

The third: we deflated the number artificially. The real average was 4 to 5 intros for a 14-day trial. We told them to expect 2 to 3. I wasn’t sandbagging for the sake of it. I was making sure we cleared our own bar more often than not. We turned the trial outcome into a layup rather than a three-pointer. And nobody was disappointed. Because the customer was still getting three distinct moments of value.

Engineering your own version

Let’s face it. My Whitetruffle story only goes so far. It’s got some compelling pieces. A pattern you might be able to see and appreciate. And even use. But you’re going to have to build out your own version. So let’s get to the takeaways you might want to apply to your startup.

Start with the anchor metric. This is the foundation. Get it wrong and nothing else matters. A good anchor metric has three properties. It’s objective, so there’s no debating it. It’s tied to value derivation, meaning it represents your product doing the thing the customer hired it to do — not engagement, not activity, but outcome. And it fires inside the trial window, often enough to be felt. If your value moment only shows up at day 45 and your trial is 14 days long, you have a different problem to solve before you ever get to the Success Narrative.

What disqualifies a metric? Anything the customer has to self-report. Anything lagging. Anything that lands too late in the trial to matter. Anything they have to interpret subjectively to even know it happened. Logins don’t count. Neither do dashboard views. “They seem to like it” doesn’t qualify.

For a marketplace like Whitetruffle, the metric was introductions. For a horizontal workflow tool, it might be the number of core workflow actions completed by some number of teammates. For a vertical SaaS, it could be something like the number of domain-specific transactions processed end-to-end. For a PLG bottoms-up product, it might well be the number of teammates invited and active. The pattern is consistent: the metric represents the product doing its job.

Then comes the conditioning. The metric does its job if the customer is looking for it when it happens. Otherwise the aha moment fires and they don’t even notice. We conditioned our trial users on the Account Optimization Call. By the time the prospect hung up, they knew intros were the thing to watch for. They knew why intros mattered. They knew what one would look like when it landed. So when it did, the value got attributed to the product, not to luck or timing or some other vendor they were also testing. If you don’t have an onboarding call, the conditioning has to happen somewhere — your activation email sequence, your in-app welcome, your kickoff doc. The channel matters less than the fact that someone, somewhere, is telling the customer what to look for, why it matters, and what it’ll look like when it shows up.

Finally, we’ve got the deflation. Take your honest average and shave a meaningful chunk off the public number. Whitetruffle was at 4 to 5; we said 2 to 3. If your data is noisy or your sample is small, shave more. You can always over-deliver. You can rarely walk back a miss. And remember why you’re doing this: not to lowball the customer’s experience, but to make sure the trust-building moment lands. Trust converts. Stretch goals that miss do not.

Where this falls apart

A few failure modes I see all the time.

The metric is too lagging. Founders pick something that technically represents value but doesn’t fire until the trial is nearly over. Customer hits day 12, hasn’t seen it yet, panics, churns. The fix: pick a metric that fires early and often, even if each unit of value feels smaller.

The conditioning never happens. The metric exists. The customer hits it. And they don’t notice. Because no one told them to look. The “aha” moment evaporates without leaving a fingerprint. The fix: build the conditioning step in like you’d build a feature. It’s not considered optional.

The number gets picked by vibes. Someone in a meeting suggests a round number that sounds good. It has no relationship to actual customer behavior. Half your trials miss it. The fix: pull the data first. Always. If you don’t have the data yet, run a few trials with no public number and watch carefully before you set one.

And the worst failure mode of all: no narrative at all. Just hope. “We’ll see how they get on with the product.” That’s not a sales process. That’s wishful thinking.

Pulling it together

When you’ve got the three components in place — anchor metric, pre-trial conditioning, deflated target — something quiet but powerful happens. You stop running around trying to satisfy a variety of customer expectations. You’re now running one play. For everyone.

That’s what makes it engineerable. And it’s teachable to the next salesperson you hire. That’s what makes it scale.

If you want me to take a look at the Success Narrative you’re crafting for your own product, you know where to find me: paul@gassee.com.

We’re done for this week. We’ve now covered Driving the Success Narrative during a pilot or free trial. A critical component if you want folks to convert from testing your product to being outright buyers. Our next installment will be dedicated to the proposal review call. A good proposal review can help you close a lot of deals. As opposed to dropping the ball at the most crucial time: right when you’re at the goal line. See you soon.