Echo the cost of inaction
Quote back what they said the current problem costs them in hours, leads, or sleep. Then the price.
How-to — — by Mahmoud Zalt
How to handle pricing questions from prospects without killing the deal: when to share the number, how to anchor value, and where AI sales replies fit in.
Pricing questions arrive earlier than founders expect, and the first reply almost always decides whether the conversation survives. When you blurt the number on the first message, you hand the prospect a yes-or-no decision they cannot answer because they do not yet know what they are buying. When you dodge it entirely, you read as evasive and the prospect leaves to find a competitor who quotes openly. The deals that close start with a third path: you treat the price question as a signal that the prospect is interested but anxious, slow the conversation by exactly one beat, and use that beat to learn enough to frame the number against their actual outcome. Solo founders lose more deals to a panicked one-line price reply than to the price itself, which is the part that hurts to admit but is easy to fix once you see it.
Timing is the whole game on pricing. Share too early and the prospect compares a number to nothing. Share too late and they feel hostage to a process. The pattern that works is a tight five-beat sequence: confirm you heard the price question so they do not feel ignored, ask one short qualifier that reveals the use case, mirror their goal back in their own words, share a price range that brackets their likely fit, and offer a concrete next step that does not require committing to the number. Each beat is a single sentence on chat or email; the entire exchange takes under two minutes of writing. The point is not to delay the price, it is to make the price legible by the time it lands. Founders who get this right tend to write the sequence once, save it as a snippet, and only customise the qualifier line per prospect so the rest stays steady.
Value anchoring is not a magic phrase, it is a tiny piece of math the prospect can run in their head. Before the number lands, they need a frame that makes the number feel small relative to the outcome. The trick is to do this in their language, not yours: if they said they are losing two hours a day to inbox triage, anchor against that exact pain. If they said they are missing out on leads while travelling, anchor against the leads. Skip the generic value props, skip the ROI calculator, skip the case study link on the first reply. One sentence in their words, then the number. Done well, the price reads as the cheap option, even if it is higher than what they expected, because you sized the alternative for them first.
Quote back what they said the current problem costs them in hours, leads, or sleep. Then the price.
Compare to one hire, one agency retainer, one freelancer day rate. Lets the number feel small instantly.
A monthly price split by four feels human. A per-day split feels even smaller without sounding gimmicky.
If they want one extra demo per week, frame the spend against that one demo. Outcome-shaped pricing.
Share the band, then say the most common fit. Subtle steer that respects their autonomy.
The reason solo founders struggle with this is volume, not skill. You can write one beautiful pricing reply on a calm Tuesday morning, but the next eleven inbound leads land while you are on a call, on a flight, or asleep. By the time you reply, the anchor has cooled and the prospect has either bought elsewhere or stopped caring. The cost of slow replies on pricing questions is the single biggest unseen leak in early-stage sales. You only see it in the conversion rate, never in the inbox, which is why most founders never realise it is the problem they have.
If you want to see what a five-beat pricing reply looks like in practice on your own inbound traffic, the easiest path is to let an AI sales employee handle every first-touch pricing question for a week. You stay in the loop on the qualified replies, you skip the unqualified ones entirely, and you get to read back the transcripts on Friday to see where the anchor worked and where it slipped. That is the cheapest possible audit of your current pricing conversation, and the section below covers what the AI is actually doing in those replies.
Yes, and this is the cleanest first task to hand to an AI sales employee because the reply pattern is repeatable, the data it needs is small, and the cost of getting it wrong is bounded. The AI does the five-beat sequence on every inbound, every time, in under thirty seconds. It pulls the prospect's stated pain from the prior message, mirrors the language back, and surfaces the right price band from a tiny config you maintain. You step in only when the prospect asks something the AI flagged as out of scope, which is usually about contracts, custom volume, or compliance. The result is a sales front door that never sleeps and never panics, even when fifteen inbound leads arrive in one hour after a launch. The compounding part is the transcripts: every reply becomes a tiny training signal you can read back on Friday and tune.
| Dimension | Traditional | With Sista |
|---|---|---|
| Median first-reply time | Six hours, often next morning | Under one minute, twenty-four seven |
| Consistency of the five-beat pattern | Drifts with mood, calendar, energy | Same shape on every inbound, every time |
| Anchor in the prospect's language | Forgotten when juggling other replies | Mirrors the exact words from the prior message |
| Handling out-of-scope questions | Risk of overcommitting on contracts or volume | Flags out of scope, hands off to founder cleanly |
| Friday transcript review | Lost across email threads and chat tabs | All conversations in one feed for one weekly review |
Discount requests are a different beast from pricing questions, and they deserve a different reply pattern. The reflex to say yes burns margin you cannot get back, and the reflex to say no flatly burns the deal. The clean middle is a five-step pushback that protects the price without slamming the door. You acknowledge the request without flinching, name what the standard price already includes, ask what they would remove to hit a lower number, offer a trade that is cheap for you and valuable for them, then restate the original price as the recommended fit. Done well, this lets the prospect either accept the original price with their dignity intact or walk away on terms that do not poison the relationship for a future quarter. The founders who hold price longest do not push back harder, they just push back the same way every time, so the pattern wears in until saying no on price feels routine.
For most early-stage products, yes, at least a starting price or a tight range. Hiding pricing entirely filters out small qualified prospects who would have closed and signals you do not know your own offer well enough to publish a number. The exception is bespoke enterprise work, where ranges still help even when the final number depends on scope.
Then they were never going to convert in a conversation either. Quote the number, then offer one short next step. If they leave anyway, you saved both sides hours. The prospects who stay after the number are the ones worth running the full five-beat sequence with on the second touch.
Ask what they are comparing against. Nine times out of ten, 'too expensive' means 'I do not yet see the outcome that justifies the spend', not 'your price is mathematically high'. Mirror their stated goal, restate the cost of the alternative they implied, and let them re-frame the price themselves.
Yes, with reasonable accuracy. An AI sales employee flags signals like vague use cases, refusal to share team size, and comparison shopping in the first three messages. You still make the call on whether to qualify them out, but the flag arrives in real time instead of in next quarter's lost-deal review.
For your standard plans, yes. For custom contracts, volume deals, or annual commitments, the AI should surface the range and route to you for the close. The cheap path is a small config of standard prices the AI is allowed to quote, and anything outside that band becomes a handoff.
Once you have the pricing-reply pattern dialled in, the next compounding move is to wire the same AI sales employee into the rest of your inbound flow: prospecting, follow-ups, qualification, and meeting booking. Pricing is the highest-leverage entry point because it shows up on almost every inbound, but the same employee that nails first-touch pricing can also run the rest of the loop without you context-switching twenty times a day. The deeper read on how that actually works in a Sistava setup is one click away.
The honest take after running both sides of this on my own pipeline: the price question is rarely the bottleneck people assume it is. The bottleneck is the time between the question and a reply that mirrors the prospect's own words back. Solo founders cannot win that speed game manually past a handful of inbound leads a week, and discounting your way through it just trains the next batch of prospects to ask for the same break. The cheap fix is to script the five-beat reply, let an AI sales employee carry it on every inbound, then spend your time on the conversations that survive the anchor. Most founders find out after two weeks that the conversations getting through are warmer than the ones they were chasing manually, which is the part that quietly changes how the rest of the business runs.