Help a Founder Examine Pricing Before Choosing a Move

Pricing questions often arrive as a request for one answer. A founder asks whether prices should rise, fall, or move into new packages. The request feels urgent because a number looks simple. Price sits beside customer expectations, delivery effort, sales behavior, and growth plans. A consulting partner earns trust by slowing discussion enough to name the decision before anyone argues for a number.

Start with the event behind a request. Ask what happened during recent sales calls, renewals, or planning meetings. A founder who says competitors offer lower prices might refer to one lost deal, a pattern among smaller buyers, or an account team using price before exploring needs. Each situation leads toward different work. A narrow question keeps one loud recent event from becoming company policy.

Ask for a decision sentence. A team might need to choose whether enterprise work deserves a separate offer, whether discount approval needs attention, or whether current pricing covers delivery effort. Write one sentence on a shared page: “We need to decide whether our enterprise offer matches delivery work.” Such wording sorts later evidence. Facts linked with another question belong on a parking page rather than inside an unfocused debate.

The first meeting gathers signals rather than settles price. Ask sales leaders which customer groups request discounts, when requests occur, and what buyers compare. Ask delivery leaders where extra work begins, who performs such work, and whether similar accounts need similar effort. Ask finance how leaders view revenue and delivery costs today. Ask product leaders which requests reflect a shared need versus a special commitment for one account.

Good questions name a time period and an observable event. “Are customers price sensitive?” invites opinion. “During the past quarter, which opportunities changed after price entered discussion, and what did each buyer request?” invites records. “Do enterprise accounts cost more?” stays broad. “Which enterprise commitments added work after signature, and where does delivery record hours?” gives a team a place to look. An early call does not require every record. Agreement on a route toward evidence matters first.

In a fictional call, founder Anika says, “Our competitors are cheaper. Tell me how much to cut.” Partner James replies, “Before choosing a number, I want to understand which customers compare price, what each receives, and where delivery effort rises. What decision do you need from this review?” Anika says enterprise buyers request custom reporting, extra meetings, and unusual approval steps. She worries sales teams accept requests without seeing later workload.

James avoids calling enterprise work unprofitable after one statement. He asks Anika to name two recent deals: one renewal with heavy custom work and one sale where a buyer accepted a standard offer. Anika agrees. James asks her sales lead for proposal versions, discount notes, and call notes from both deals. He asks the delivery lead for an account of work beyond standard service. Finance brings an internal view leaders already use for revenue and delivery costs. Nobody needs a polished analysis before examining an underlying story.

Prepare a small evidence pack before a working session. Include customer group, offer sold, list price, approved discount, requested additions, delivery effort noted, renewal status, and open questions. Leave blank cells where records offer no answer. A blank field tells leaders where knowledge ends. Confident guesses create false agreement and later friction.

Treat each item as a prompt for a decision rather than proof for a preferred outcome. Suppose six enterprise customers received different custom reports. Ask whether reports reflect one recurring need, several distinct requests, or exceptions leaders no longer wish to accept. A repeated request points toward a defined service tier. Unrelated requests point toward a clearer change process. One unusual request needs a deliberate exception decision. Evidence informs leadership choices, yet leaders still decide what an offer means.

Sales behavior deserves separate attention. Discounting sometimes signals price pressure. Discounting also follows unclear authority, end of quarter urgency, missing value discussion, or a proposal built around an unsuitable offer. Review how a seller reached a discount. Did a buyer ask early? Did a seller offer one without a request? Did a manager approve an exception? Did anyone record what changed after approval? Answers show whether pricing needs attention or sales process choices need sharper guidance.

Use a simple meeting rhythm. Restate a decision sentence. Review two customer stories before opening a spreadsheet. Stories expose sequence, promises, and handoffs. Compare records for patterns afterward. Name support from evidence, uncertainty, and follow up needed. End each topic with an owner and due date. This structure prevents a meeting where each leader repeats a view without moving toward a decision.

In this fictional example, Anika's team finds one enterprise renewal with twelve extra reporting requests across four months. Sales described reports during an early discussion, though signed offer language named no agreed scope. A second enterprise account paid list price and used a standard monthly report. The contrast changes Anika's question. She stops asking for an across company cut. She asks whether enterprise proposals need a named reporting option and a visible approval point for work outside standard delivery.

James helps leaders compare options without presenting one as inevitable. One option keeps current prices and clarifies proposal language. Another creates an enterprise reporting option with a separate price decision. A third route sends extra reporting through exception review. For each route, leaders write intended customer group, work included, evidence needed, operational effect, owner, and review date. Tradeoffs become visible. A lower starting price brings a different expectation about service. A separate option simplifies sales discussion yet needs product and delivery work.

Avoid pretending precision where none exists. Early analysis rarely supplies a perfect price. A more honest outcome might involve a limited test inside upcoming proposals, subject to normal company approval. State what useful learning looks like. A team might review whether buyers understand an option, whether sellers present scope consistently, and whether delivery sees a promised handoff. Leaders inspect results before calling any review successful.

Partner language matters during tension. If Anika asks, “Are you saying our sales team caused this?” James replies, “We have two deal records with different promises and delivery patterns. Let us examine how each promise entered a proposal before assigning a cause.” His reply acknowledges concern and returns attention to observable events. He does not become an advocate for one function against another.

Before a session ends, write a decision record in plain language. Name a question, people present, records reviewed, points of agreement, open points, chosen next action, responsible person, and review date. A short record prevents later claims about an approval someone believed existed. Send participants a factual note soon after a meeting. Invite corrections for missing facts or unclear ownership.

At 3:30 p.m. on Thursday in this fictional example, Anika opens two upcoming enterprise proposals beside sales and delivery leads. She circles every reporting promise, writes whether each promise belongs inside a standard offer or needs separate approval, then assigns James a Monday meeting for unresolved items. The group leaves each proposal with a named next action rather than an unsupported new price.