61. Pricing and Negotiation

Pricing is not only a number. It is a theory of value.

Your price tells you what customers believe the problem is worth, how urgent the pain is, who has budget, what alternatives exist, and whether the company can become healthy. Early pricing will be imperfect, but avoiding price conversations is worse.

Negotiation is not about winning every rupee or dollar. It is about protecting value, scope, cash flow, and trust.

The core pricing and negotiation question is: can you connect price to customer value, protect scope, and close terms that make the business healthier?

What It Covers

This chapter covers:

• Early pricing
• Negotiation
• Pricing mistakes

The founder’s job is to learn what value the customer recognizes and to build a commercial model that can survive.

Price Is A Learning Instrument

Early pricing should answer:

• Which customer segment values the product most?
• Which outcome do they believe is worth money?
• Which pricing model matches how value is created?
• What budget category do they use?
• What objection appears when price is named?
• What price creates seriousness without killing the deal?
• What delivery cost makes a customer unhealthy?

Do not wait for perfect pricing. The market will not give you pricing truth until you ask for money.

Early Pricing

There are several ways to set an early price. None is perfect.

Model	When useful	Risk
Cost-plus	Services, implementation, or work with clear delivery cost	Underprices software value
Competitor-based	Category has known alternatives	Anchors you to the wrong category
Value-based	Outcome is measurable	Requires clear ROI and buyer belief
Usage-based	Value scales with transactions, volume, seats, calls, or data	Can create bill shock or unpredictable revenue
Tiered	Different segments need different capability	Too many tiers confuse buyers
Pilot pricing	Early proof with limited scope	Can become permanent discount
Enterprise pricing	High value, support, security, procurement	Slow cycles and custom scope

Early founders often underprice because they fear rejection. But price rejection is useful data. If every buyer says yes immediately, you may be too cheap or selling to the wrong segment.

Pricing Floors And Ceilings

Think in three numbers:

Number	Meaning
Floor	The minimum price that covers delivery, support, infrastructure, founder time, and gross margin
Target	The price that reflects customer value and supports a healthy business
Stretch	A higher price to test when the buyer has strong pain, urgency, and budget

Many founders only think about the floor. That creates fragile businesses. Your price must fund product, support, sales, taxes, refunds, failures, and future growth.

Cost-Plus

Cost-plus pricing is simple: cost plus margin. It works for services, custom implementation, or agency-style work. It is weak for software because customers buy outcomes, not your engineering hours.

Use cost-plus only as a floor. Your price should not be lower than the cost to deliver, support, and retain the customer.

Competitor-Based

Competitor pricing helps you understand market expectations. But copying competitors can trap you. They may have different brand, features, costs, funding, support, or customer segment.

Use competitor pricing as context, not as truth.

Value-Based

Value-based pricing asks: what economic value does the customer receive?

Examples:

• Saves 20 hours per month for a finance team.
• Reduces failed deliveries.
• Improves sales conversion.
• Prevents compliance penalties.
• Recovers revenue leakage.
• Reduces support tickets.

The more measurable the value, the easier it is to defend price.

Build A Basic ROI Story

Your ROI story does not need to be fancy. It needs to be believable.

Example:

Current process:
- 2 finance people spend 2 days per month on reconciliation.
- Founder reviews exceptions for 3 hours.
- Month-end reporting is delayed by 2 days.

Value if solved:
- 60-70 percent less manual effort.
- Faster close.
- Fewer payout errors.
- Less founder involvement.

Price:
- Annual plan at [price], including onboarding and support.

This is stronger than “our tool saves time.” Buyers pay for specific value, not vague improvement.

Usage-Based

Usage-based pricing works when customer value grows with usage. It can be powerful for APIs, infrastructure, automation, communication, data, and AI products.

But it requires cost control and predictability. If customers cannot estimate the bill, they may hesitate.

Tiered Packaging

Packaging should make buying easier.

Example:

• Starter: narrow use case, limited volume, basic support.
• Growth: core workflow, integrations, team use, reporting.
• Enterprise: security, procurement, advanced support, permissions, custom terms.

Do not create five plans because competitors do. Create packages around buyer maturity and value.

Pilot Pricing

Pilot pricing should not become a trap.

Good pilot pricing:

• Has a clear scope.
• Has a clear timeline.
• Has a fee or meaningful commitment.
• Credits the pilot fee toward the annual plan when useful.
• Names the post-pilot price upfront.

Weak pilot pricing:

• Free forever.
• No conversion price.
• Custom work without payment.
• “We will discuss later.”

If the buyer refuses to discuss post-pilot pricing, they may be looking for free work rather than a decision.

Enterprise Pricing

Enterprise pricing must account for more than software usage:

• Security review.
• Legal review.
• Procurement time.
• Implementation support.
• Custom reporting.
• Data migration.
• Training.
• SLA expectations.
• Payment delays.
• Account management.

If you price enterprise deals like self-serve SaaS, you may win logos and lose money.

Negotiation

Negotiation begins before procurement. It begins when you frame the problem and value.

Common negotiation levers:

• Price.
• Scope.
• Seats.
• Usage.
• Support.
• Implementation.
• Timeline.
• Payment terms.
• Annual commitment.
• Multi-year commitment.
• Reference rights.
• Case study.
• Product roadmap requests.

If the customer asks for a discount, do not panic. Ask why. Sometimes the objection is budget. Sometimes it is uncertainty. Sometimes it is procurement habit.

Diagnose The Objection

Not every price objection means price is too high.

Objection	Possible meaning	Founder response
”Too expensive”	Value not clear, budget mismatch, or negotiation habit	Ask compared to what and restate value
”No budget”	Wrong buyer, wrong timing, or no category	Ask how similar tools are funded
”Can you do a discount?”	Procurement habit or real constraint	Trade discount for commitment
”We need approval”	Buyer is not economic buyer	Map approval process
”Let us start free”	Trust gap or weak intent	Offer bounded pilot with criteria
”Competitor is cheaper”	Category comparison	Clarify scope, support, and outcome

The founder’s job is to understand the objection before reacting.

Discount Control

Discounts should trade for something.

Examples:

• Annual payment.
• Faster signature.
• Reduced scope.
• Public testimonial.
• Reference call.
• Multi-year commitment.
• Fewer custom requirements.
• Pilot fee converting into annual contract.

Never discount only because silence feels uncomfortable.

Write discount rules before the call. For example:

• Up to 10 percent for annual payment.
• Pilot fee credited only if annual contract signs within 30 days.
• No discount for custom support unless scope is reduced elsewhere.
• Founder-approved exception only for strategic reference customers.

Rules protect you from emotional negotiation.

Anchoring

The first serious price shapes the conversation. If you anchor too low, it is hard to climb. If you anchor absurdly high without value proof, you lose trust.

Anchor with value:

“The current process costs roughly 80 finance hours per month and delays closing by four days. Our annual price is [X], including onboarding and support.”

Procurement

Procurement is not the enemy. It is a process with incentives.

Prepare:

• Business case.
• Security answers.
• Legal entity and GST details where relevant.
• Payment terms.
• Scope and deliverables.
• Data handling answers.
• References if available.
• Renewal and cancellation terms.

If procurement appears late, the deal can slow suddenly. Ask about it early:

If the business team wants to proceed, what procurement, finance, legal, or security steps would follow?

Payment Terms

Payment terms affect cash flow. A deal booked but not collected can still hurt the startup.

Think through:

• Upfront vs monthly.
• Annual prepay.
• Net 15, net 30, net 60.
• Setup fees.
• GST and invoicing.
• Late payment process.
• Refund terms.
• Renewal date.

For early startups, cash collection matters as much as contract value.

Annual Plans And Multi-Year Contracts

Annual plans help cash flow and retention. Multi-year contracts help predictability, but they should match confidence.

Trade carefully:

• Annual prepay can justify a discount.
• Multi-year can justify price protection.
• Long payment terms should not come with deep discounts.
• Early cancellation rights should affect price.
• Heavy implementation should have setup fees or upfront payment.

Do not celebrate a large contract if payment arrives late and scope is unlimited.

Scope Boundaries

Many pricing problems are scope problems. A customer asks for a discount while also asking for custom work, extra support, integrations, reporting, and special terms.

Separate price from scope:

“We can reduce price if we keep this to the standard workflow. If we include custom integration and weekly support, the price needs to reflect that.”

Use a trade table:

If customer asks for	You can trade with
Lower price	Annual payment, reduced scope, faster signature
Custom feature	Paid implementation, roadmap commitment only after contract
More support	Higher tier or paid support package
Longer pilot	Pilot fee or narrower scope
Flexible payment	Higher total price or shorter contract
Case study restriction	Less discount

Negotiation becomes healthier when every concession has a matching trade.

India Angle

Indian customers may negotiate hard, delay payment, ask for custom terms, or expect founder availability. Do not interpret negotiation as disrespect. It is often part of buying culture.

But be clear:

• What is included.
• What is extra.
• When invoices are raised.
• GST treatment.
• Who approves payment.
• What happens after pilot.
• When renewal happens.

For SMBs, cash flow and trust may matter more than formal ROI. For enterprise, procurement, vendor onboarding, payment terms, security, legal, and internal approvals can slow collection.

Price sensitivity does not mean no willingness to pay. It means the value and trust must be sharp.

Indian founders should pay close attention to:

• GST and invoicing: Know whether you need GST registration, tax invoice format, purchase order, or vendor onboarding.
• Collections: A signed agreement is not the same as collected cash.
• Founder promises: Buyers may expect direct founder access. Define what support is included.
• Customization: Many customers ask for “small changes.” Small changes can become a services business if not priced.
• References: Local references can reduce price pressure by increasing trust.
• Payment cycles: Net 30 may become net 60 or longer in larger companies. Price and cash planning should reflect this.

When selling internationally from India, also consider currency, tax forms, payment method, security requirements, data processing terms, and support hours. A dollar contract can still be operationally expensive if terms are loose.

Common Mistakes

• Pricing too low from fear.
• No packaging.
• Discounting without getting anything back.
• No ROI story.
• No renewal thinking.
• Custom pricing chaos.
• Free pilots with no conversion.
• Ignoring collections and payment terms.
• Letting procurement define product scope.
• Treating every customer as the same segment.
• Naming a price before understanding value.
• Giving custom pricing to every prospect.
• Letting a pilot price become the permanent price.
• Agreeing to unlimited support in order to close.
• Celebrating revenue without checking gross margin.

Pricing Hypothesis

Write this before your next ten sales calls:

Question	Your answer
Who is the customer segment?
What pain are they paying to solve?
What does the current alternative cost?
What value do we create?
What pricing model fits value?
What is the first package?
What discount rules apply?
What payment terms do we prefer?
What evidence would change the price?

Pricing improves through conversations. Do not debate it forever internally.

Pricing Decision Memo

When pricing starts to feel confusing, write a one-page pricing decision memo. This prevents every deal from becoming a custom emotional negotiation.

Use this structure:

Section	What to write
Target customer	Which segment this price is for.
Value driver	The main outcome the customer pays for.
Packaging	What is included and excluded.
Unit	Seat, account, usage, transaction, location, project, or annual platform fee.
Floor price	Minimum healthy price after support and delivery cost.
Target price	Price you want qualified customers to accept.
Stretch price	Price to test with high-urgency, high-value buyers.
Discount rule	What the customer must give in exchange for discount.
Payment terms	Monthly, quarterly, annual, advance, milestone, or other.
Review trigger	When this price should be revisited.

This memo does not need board-level precision. It needs enough clarity that the founder can negotiate without panic.

Packaging Before Price

Many pricing problems are packaging problems. If the buyer does not understand what is included, the number will feel arbitrary.

Clarify:

• What problem this package solves.
• Who it is for.
• What support is included.
• What usage or limits apply.
• What onboarding includes.
• What is explicitly not included.
• What upgrade path exists.

For example, “Rs. X per month for software” is weaker than:

“Starter package for marketplace reconciliation: up to three marketplaces, monthly payout matching, exception report, email support, and one onboarding session. Custom ERP integration is not included.”

The second version protects scope and makes price easier to judge.

Negotiation Script

When a buyer asks for a discount:

I understand price matters. Before changing the number, can I ask what is driving the concern: budget, uncertainty about value, procurement expectations, or comparison with another option?

If budget is real:

We can look at reducing scope or moving to annual payment. I do not want to reduce price while keeping the same scope and support because then implementation becomes unhealthy for both sides.

If value is unclear:

Let us revisit the value. You mentioned [pain] currently costs [time/money/risk]. If we cannot create enough value against that, we should not move forward at this price.

If procurement is asking:

We can work with procurement, but our discount needs to trade for something: faster signature, annual prepay, reduced scope, or reference rights.

This keeps the founder calm and commercial.

Negotiation Guardrails

Founders should decide guardrails before the call. Negotiating live without rules turns every confident buyer into your pricing committee.

Use these guardrails:

Guardrail	Rule
Discount ceiling	Maximum discount allowed without changing scope or term.
Scope exchange	Any lower price must remove scope, support, usage, or timeline.
Cash exchange	Discount can trade for annual prepay or faster payment.
Proof exchange	Discount can trade for reference, case study, or testimonial only if allowed and written.
Time limit	Proposal expires on a clear date.
Custom work	Customization requires paid implementation or higher plan.
Payment risk	Work does not start until payment, PO, or written approval reaches the agreed stage.

If the customer asks for a concession, ask for a trade. This is not being difficult. It teaches the buyer that value has structure.

What Not To Trade Away

Be careful with these concessions:

• Unlimited support.
• Custom features without price.
• Broad usage rights.
• Very long payment delays.
• Informal approval without written confirmation.
• Public reference rights that the customer cannot actually give.
• Security or compliance promises you cannot support.
• Price lock without renewal terms.

Some concessions close the deal but damage the company. A good negotiation protects future delivery.

Early Pricing Review

Every 10-15 serious conversations, review:

• Which segment accepted price fastest?
• Which segment negotiated hardest but still converted?
• Which segment had high support cost?
• Which objections repeated?
• Which package was easiest to explain?
• Which deals collected cash quickly?
• Which deals looked good but became operationally heavy?

Raise price when:

• Close rates are high among qualified buyers.
• Customers say yes too quickly.
• Support and implementation cost is higher than expected.
• Value is clearer than before.
• The product has stronger proof.

Do not raise price randomly. Raise it as learning improves.

Collections Discipline

Pricing does not matter if cash does not arrive.

For every deal, track:

Stage	Meaning
Verbal yes	Buyer said they want to proceed.
Commercial agreement	Price, scope, and term agreed.
Contract or email approval	Written confirmation exists.
PO or vendor setup	Customer process has started where required.
Invoice raised	Billing has happened correctly.
Payment received	Cash is in the bank.
Product adopted	Customer is actually using the product.

A founder should never confuse the first stage with the sixth. In India especially, vendor onboarding, GST details, PO creation, finance approvals, and payment cycles can stretch the gap between excitement and cash.

Price-Quality Signal

Price also signals confidence and quality. If the price is too low for a serious business problem, buyers may worry that the product is immature, support will be weak, or the founder does not understand enterprise delivery.

Low price can help in self-serve or highly price-sensitive markets. But in B2B, a very low price can attract customers who need too much support and do not value the outcome. Test this carefully.

Ask:

• Does price match the customer’s perceived risk?
• Does the buyer expect implementation and support?
• Does the price fund the promised service level?
• Does discounting attract worse-fit customers?
• Does the price make the product easier or harder to trust?

The goal is not to be expensive. The goal is to price consistently with value, trust, and delivery.

Renewal Thinking

A sale is not complete when the contract is signed. Price and scope should set up renewal.

Before closing, define:

• What value will be visible before renewal?
• Who will judge success?
• What usage or outcome must happen in the first 30-90 days?
• What expansion path exists?
• What support expectation has been promised?
• What would make the customer churn?

A discount that closes the first year but creates a disappointed, unsupported customer is not a win.

Reader Action

Choose one customer segment. Offer the same package to the next ten qualified prospects, with one clear price and one discount rule. Track reactions:

• Immediate yes.
• Pushback.
• Budget objection.
• Value objection.
• Procurement objection.
• No decision.

Use the pattern to adjust packaging, not your confidence.

Also write a discount policy before the next pricing call. It should fit on five lines. If you cannot write the rule in advance, you are likely to negotiate from fear in the moment.

Pricing Packaging Ladder

Early pricing becomes easier when the founder separates package levels instead of inventing a new deal every time.

Example ladder:

Package	Best for	Includes	Boundary
Diagnostic	Buyer is unsure and pain needs mapping.	Audit, workshop, findings, recommended next step.	No ongoing implementation.
Pilot	Buyer wants proof in one workflow.	Fixed scope, timeline, success criteria, support.	No unlimited customization.
Standard plan	Pain and use case are clear.	Core product, onboarding, support, agreed usage.	Feature requests go to roadmap.
Implementation package	Setup effort is meaningful.	Data cleanup, integration, training, reporting.	Separate from subscription price.
Enterprise plan	Risk, security, support, or scale is high.	Procurement support, security review, SLA, success plan.	Priced for delivery burden.

The ladder helps buyers choose. It also protects the startup from giving enterprise service at pilot prices.

Negotiation Give-Get

Never give a concession without receiving something that improves the deal.

If customer asks for	Possible get
Discount	Faster payment, annual commitment, narrower scope, reference after success.
Free pilot	Shorter timeline, clear success criteria, named buyer, reference rights.
More support	Implementation fee, longer contract, reduced custom requests.
Custom feature	Paid implementation, broader commercial commitment, roadmap fit review.
Longer payment terms	Higher price, signed PO, reduced discount, clear collections date.

Give-gets are not tricks. They keep the relationship balanced and make sure the startup can actually deliver what it promises.

Negotiation Prep Sheet

Before a pricing call, write the negotiation boundaries.

Field	Founder note
Customer pain	What outcome are they buying?
Business value	What time, revenue, risk, or cost is affected?
Buyer	Who can approve?
Anchor price	What price will you present first?
Walk-away point	Below what price or scope is the deal unhealthy?
Discount rule	What concession is allowed and in exchange for what?
Payment terms	Monthly, annual, upfront, milestone, or invoice cycle?
Implementation burden	What setup/support must be priced separately?
Success metric	What will make renewal likely?

Founders negotiate badly when they enter pricing calls with only hope. The prep sheet creates calm.

Objection Diagnosis

When a customer says price is high, diagnose the objection.

Objection type	What it sounds like	Founder response
Value	”I don’t see why this costs that much.”	Reconnect price to outcome and current cost.
Budget	”We do not have budget.”	Ask about current spend, timing, and budget owner.
Authority	”I need approval.”	Map the decision process and help with internal business case.
Trust	”We are not sure you can deliver.”	Offer proof, pilot, reference, or lower-risk scope.
Comparison	”Competitor is cheaper.”	Compare scope, implementation, support, and outcome.
Procurement	”Our process takes time.”	Ask for steps, documents, vendor setup, and realistic close date.

Do not answer every price objection with a discount. Many price objections are actually trust, urgency, or authority objections.

Collections Operating Checklist

For Indian founders, closing is not complete until payment is collected or the agreed commercial process has started.

Track:

• GST details collected.
• PO or written approval received where required.
• Invoice raised correctly.
• Payment terms confirmed.
• Accounts payable contact known.
• Payment reminder dates scheduled.
• Service start tied to commercial agreement.

Avoid starting large delivery work before the commercial path is clear. A founder can be busy, praised, and unpaid at the same time.

Renewal And Expansion Pricing

Think about renewal before the first invoice.

Ask:

• What usage or outcome should be visible by renewal?
• What expansion trigger would justify a higher plan?
• Which stakeholder must see value?
• Which support promises are included in the price?
• Which custom work should be charged separately later?

Early price is not only about closing the first customer. It teaches the customer what kind of relationship this will be: product, service, partnership, implementation-heavy solution, or low-touch tool.

If the first price promises too much for too little, renewal becomes painful. Price the first deal so you can serve the customer well and still survive.

Pricing Exception Review

Early founders sometimes need exceptions: strategic logos, references, pilots, unusual implementation, or learning deals. Exceptions are acceptable only when they are explicit and reviewed.

Before approving an exception, answer:

Question	Why it matters
Why are we making an exception?	Prevents fear-based discounting.
What do we get in return?	Keeps the exchange balanced.
What is the true delivery cost?	Prevents hidden services work.
Will this create a bad precedent?	Protects future pricing.
Does this customer match the ICP?	Avoids custom work for low-learning accounts.
What is the renewal or expansion path?	Avoids one-time unhealthy revenue.
Who approved it?	Creates accountability.
When will we review the result?	Turns exception into learning.

Exception Log

Keep a simple log:

Customer	Exception	Reason	Give/get	Renewal risk	Lesson
	Discount / custom scope / payment term / free pilot

If exceptions become common, pricing is no longer a strategy. It is improvisation. Review the log monthly and turn repeated exceptions into clearer packaging, better qualification, or stricter boundaries.

Price Protection System

Early founders discount because they want the deal, fear losing momentum, or feel guilty charging before the product is mature. Some flexibility is fine. Uncontrolled discounting teaches the market that your price is fictional.

Use a price protection system:

Rule	Example
Discount requires give/get	Lower price only for annual payment, faster decision, reference, case study, reduced scope, or useful feedback access.
Discount expires	A special price has a decision date.
Discount is tied to scope	If the customer wants more scope, price changes.
Founder approval required	No one improvises discounts alone.
Exceptions are logged	Every exception has a reason and review date.
Renewal path is named	The customer knows the normal price or future package.

Discounts are not always bad. Discounts without exchange are bad. If the customer asks for price movement, ask what can move on their side: payment timing, scope, term length, reference, implementation effort, or decision speed.

Price Conversation Script

When price comes up early:

The normal range for this kind of workflow is [range], depending on scope and volume. Before I quote precisely, I want to understand the workflow, success criteria, and implementation load so we do not underprice or over-scope it.

When the buyer says it is expensive:

I understand. Is the concern total budget, uncertainty of value, comparison with an existing tool, or timing? The answer changes what we should adjust.

When they ask for a discount:

We may have some flexibility, but I would want to trade it for something that helps both sides: annual payment, a narrower scope, a faster decision, a reference if successful, or a defined pilot. Which of those is realistic?

When they compare to a cheaper alternative:

That may be the right option if the requirement is only [basic job]. The reason customers choose us is [specific value]. If that value is not important here, I do not want to oversell you.

This kind of language keeps the founder calm. It also shows buyers that the price is connected to value, scope, and risk, not founder anxiety.

Expansion And Renewal From Day One

Price the first deal with the second deal in mind. Expansion and renewal are easier when the first package has clear boundaries.

Before closing, define:

Boundary	Why it matters
Included users or teams	Prevents unlimited internal spread without pricing.
Included volume	Protects cost and value alignment.
Included workflows	Avoids custom expansion disguised as support.
Included support	Prevents high-touch service from hiding inside product price.
Data or integration scope	Controls implementation load.
Review date	Creates renewal and expansion conversation.
Upgrade trigger	More volume, teams, branches, workflows, automation, analytics, or support.

Expansion should feel like the customer growing into more value, not like the founder suddenly asking for more money. The cleanest way to do that is to define package boundaries before the first invoice.

When To Raise Price

Raise price when at least two of these are true:

• Customers accept the current price too easily.
• Delivery cost or support burden is higher than expected.
• The product creates measurable revenue, savings, speed, or risk reduction.
• New customers need less persuasion than before.
• Existing customers expand usage.
• The market anchors higher for comparable value.
• Discounts are common because packaging is unclear, not because value is weak.

Do not wait until everything is perfect. Early pricing should evolve as evidence improves.

Discount Approval System

Discounting is not always bad. Undisciplined discounting is bad. A discount should buy something useful: speed, annual cash, reference value, expansion path, reduced scope, or strategic learning.

Use approval rules:

Discount reason	Acceptable only if
Annual prepay	Cash is collected upfront and churn risk is reasonable.
Logo/reference	Customer is truly referenceable and representative.
Pilot	Scope, timeline, success criteria, and conversion path are written.
Multi-seat/team	Expansion is real, not imagined.
Competitive deal	The customer is in ICP and switching reason is strong.
Budget constraint	Scope or service level is adjusted accordingly.

Every discount should record:

List price:
Discounted price:
Reason:
What we get in return:
Approval:
Renewal price:
Expansion path:

If the discount does not buy anything, it is fear.

Payment Terms Negotiation

Payment terms are pricing. A customer asking for 90-day payment terms is effectively asking the startup to finance them.

Negotiate:

Customer ask	Founder response
Long payment terms	Offer smaller start, annual prepay discount, or milestone billing.
Pay after full rollout	Tie payment to kickoff or first value, not indefinite adoption.
Heavy custom work before payment	Charge implementation or setup fee.
Procurement delay	Ask for PO timeline, billing contact, and internal owner.
Discount plus late payment	Avoid giving both unless strategic value is clear.

In India especially, collections discipline can be the difference between growth and stress. A signed deal with weak payment terms can still hurt runway.

Price Increase Communication Plan

Founders often avoid price increases until the business is strained. Communicate with clarity.

Plan:

Step	Action
Segment	Decide which customers are affected and why.
Reason	Explain product value, support, inflation, usage, or package change honestly.
Timing	Give reasonable notice.
Options	Offer annual lock-in, lower tier, reduced scope, or migration help where appropriate.
Internal script	Sales/support should know how to explain the change.
Risk list	Identify customers likely to object or churn.

Price increases should be connected to value and communicated like a trust moment, not sprung like a penalty.

Value Metric Selection

Pricing becomes clearer when the unit of pricing matches the unit of value. Early founders should test value metrics, not copy competitors blindly.

Value metric	Works when	Watch out for
Per user	Value expands with team adoption.	Can punish collaboration if too expensive.
Per account or company	Buyer wants predictability.	May underprice heavy usage.
Usage-based	Value scales with transactions, records, messages, orders, or workflows.	Customers may fear bill shock.
Outcome-based	Result is measurable and trusted.	Attribution and disputes can be hard.
Tiered packages	Segments have different needs and willingness to pay.	Too many tiers confuse buyers.
Setup plus recurring	Implementation effort is real.	Setup fee must feel connected to value.
Pilot fee to annual	Buyer needs proof before larger commitment.	Pilot must have conversion path.

Ask:

What unit grows as the customer gets more value?
What unit does the buyer already understand?
What unit is easy to forecast?
What unit avoids punishing healthy usage?
What unit protects our cost to serve?

The right value metric should make the customer think, “If this works, paying more makes sense.”

Negotiation Give-Get Menu

Do not give concessions for free. If the customer asks for something, ask for something that improves commitment, cash, learning, or reach.

Customer asks for	Founder can ask for
Discount	Annual prepay, faster signature, reference call, narrower scope, or case study permission.
Custom feature	Paid implementation, longer contract, clear roadmap priority, or design partner commitment.
Longer pilot	Paid pilot extension, specific success criteria, or buyer review meeting.
Flexible payment terms	Higher price, smaller scope, upfront setup, or milestone billing.
Extra support	Defined support package, onboarding fee, or success owner.
Logo/reference use	Better commercial terms, faster payment, or executive sponsor.

The purpose is not to be rigid. It is to keep the deal honest. A buyer who asks for many concessions but gives no commitment may be teaching you that the pain is not strong enough.

Use this sentence:

We can consider that if we also agree on the commitment that makes this worthwhile for both sides.

Negotiation is not a fight. It is a test of whether both sides value the outcome enough to protect the work.

Pricing Exception Register

Every early startup makes pricing exceptions. The danger is forgetting them. Forgotten exceptions become messy renewals, unfair customer treatment, and confusing revenue quality.

Track every exception:

Field	What to record
Customer	Name, segment, and buyer.
Exception	Discount, custom scope, payment terms, free pilot, extra support, special feature, or reference right.
Reason	Strategic logo, cash urgency, learning, annual prepay, reduced scope, or founder mistake.
Give-get	What the customer gave in return.
Renewal path	Normal price, review date, or expansion trigger.
Risk	Margin, precedent, support burden, customer expectation, or internal fairness.
Owner	Who approved and who must revisit it.

Use this sentence before approving:

This exception is acceptable because it buys [specific value], and we will review it on [date] before it becomes permanent.

If a pricing exception has no review date, it is not an exception. It is the new price.

Bad Deal Detector

Early founders often celebrate any signed customer. That is understandable, but some deals create hidden damage: low margin, custom scope, slow payment, team distraction, weak references, or product commitments that pull the company away from the market.

Before signing, run this detector.

Signal	Why it is dangerous	Founder response
Customer wants a large discount and long payment terms	You lose both price and cash flow.	Trade discount only for upfront payment, narrower scope, or meaningful commitment.
Pilot has no buyer, date, or success criteria	It becomes free consulting.	Add buyer sponsor, timeline, success metric, and conversion price.
Custom feature is needed before payment	The customer is shifting product risk to you.	Charge setup/implementation or move it after contract.
Procurement starts after verbal yes	The deal is not as close as it feels.	Map approval, PO, vendor onboarding, legal, and payment owner.
Buyer says the product is strategic but refuses commitment	Words and budget disagree.	Ask for paid pilot, executive review date, or smaller paid scope.
Customer is outside ICP but revenue is tempting	Support and roadmap may bend around the wrong segment.	Treat as a deliberate exception with owner and review date.
Deal depends on founder heroics	Revenue will not scale beyond founder time.	Define support limits, onboarding owner, and post-sale process.
Reference value is vague	”Big logo” may not become trust or pipeline.	Get explicit reference, case study, testimonial, or intro terms if that is part of the trade.

Use the final question:

If we signed ten more customers exactly like this, would the company become healthier or more fragile?

If the answer is “more fragile,” the price is not the only problem. Fix scope, payment terms, customer fit, delivery model, or walk away. Revenue that teaches the wrong company how to exist is expensive.

Related Links

• 56. Founder-Led Sales
• 60. Demos and Pilots
• 28. Business Model Strategy
• 137. Pricing Test Playbook