Interviews · 12 min read

YC Interview Questions About Your Pricing Model

Short answer

Pricing questions in a YC interview are not primarily about whether your price is right. They are about whether you understand why your price is what it is — how you arrived at it, what it tells you about your user's willingness to pay, and what would happen to your business if you changed it. Founders who have thought carefully about pricing answer these questions with specificity and confidence. Founders who set a price by copying a competitor or picking a round number reveal that pricing is an afterthought rather than a deliberate business decision.

Why YC Partners Ask Pricing Questions

This page covers every pricing question asked in YC interviews, what each one probes, and the exact framework for answering with the specificity partners are looking for.

Pricing is one of the densest signals available in an early-stage company. A single pricing answer can reveal:

Whether you understand your user's economics. A price that is too low for the value you deliver, or too high for the purchasing power of your specific user, reveals a mismatch between how you understand your product and how your user actually experiences it.

Whether you have validated willingness to pay. Founders who set prices by asking users what they would pay, by running pricing tests, or by observing what users currently spend on alternatives have evidence. Founders who set prices by benchmarking competitors or picking a comfortable number have assumptions.

Whether your unit economics work. Your price, your gross margin, your CAC, and your LTV must combine into an economics model that is eventually sustainable. Partners check whether founders understand this model and whether the pricing decision reflects it.

Whether you are leaving money on the table. A common early-stage mistake is underpricing — charging less than users would willingly pay because founders are uncomfortable with higher numbers. Partners specifically probe for this.

The Answer Layer: Every Pricing Question With Response Frameworks

"What do you charge?"

What partners probe: The exact number and the structure. Not "around ₹2,000" — the exact price, the billing interval, and whether it is per seat, per usage, per transaction, or flat rate.

Framework: State the price, the structure, and one sentence of context.

"₹2,500 per pharmacy per month, billed monthly, flat rate. No setup fee, no per-transaction fee."

"How did you decide on that price?"

What partners probe: Whether pricing was a deliberate, evidence-based decision or an assumption.

Framework: Name the method you used to arrive at the price.

"We ran a Van Westendorp pricing survey with 40 pharmacy owners — the acceptable range was ₹1,500 to ₹4,000, with the optimal point at ₹2,500. We also checked what pharmacy owners currently spend on their closest alternative — a Marg ERP desktop license runs ₹8,000-12,000 per year, making our ₹30,000 per year price look extremely cheap by comparison. We started at ₹2,500 and have not needed to discount once."

"What would happen if you doubled your price?"

What partners probe: Your understanding of price elasticity for your specific user, and whether you are underpricing. This is one of the most revealing pricing questions because most founders have never tested it.

Framework: Name your honest assessment based on your user evidence.

"Honestly, we think most of our customers would stay at ₹5,000. The problem we solve — catching expired stock before it becomes a loss — saves the average pharmacy ₹15,000-20,000 per month. At ₹5,000, our price-to-value ratio is still very strong. We have not tested it yet. It is on our roadmap for Q2 — we want more retention data before moving price."

If you believe a price increase would cause significant churn: "We think we would lose 30-40% of customers at double the price based on what they have told us in conversations. Our current segment is price-sensitive family-run pharmacies. We are deliberately keeping price low to build the customer base and the data, with plans to introduce a premium tier for larger independent pharmacies at ₹5,000-8,000 once we have enough network data to justify the premium."

"What is your gross margin?"

What partners probe: Whether you understand the difference between revenue and profit, and whether your business model is fundamentally sound.

Framework: State the percentage and the two largest cost line items in your COGS.

"Gross margin is approximately 78%. Our direct costs are hosting at ₹3,000 per month and one part-time support person at ₹12,000 per month — against ₹64,400 MRR. No other direct costs."

"Why not charge more?"

What partners probe: Whether you have thought about the ceiling of your pricing, and whether your current price is a deliberate strategic choice or just timidity.

Framework: Name your specific reasoning — either a deliberate growth strategy justification or an honest acknowledgment that you plan to increase price.

"We deliberately priced to minimize friction at the entry point. Our primary barrier is not willingness to pay — it is habit change. Pharmacy owners have used notebooks for 20 years. We want to make the cost objection irrelevant so we can focus on demonstrating value. Once they are using the product and have seen the expiry savings, the renewal and upsell conversation becomes easy. Our plan is to introduce a ₹5,000 premium tier with distributor integration in Q3."

"Do you offer discounts?"

What partners probe: Whether your pricing is firm or whether you are discounting to close deals, which signals weak pricing confidence and creates bad customer expectations.

Framework: Be direct about your policy and the reason for it.

"No. We made a deliberate decision early on not to discount. Every discount we give sets a precedent with that customer and creates pressure to discount for the next one. Our price is already well below the value we deliver — if a customer objects to the price, we address the value question, not the price question. We have closed all 23 customers at full price."

"How does your pricing compare to competitors?"

What partners probe: Whether you know your competitive pricing landscape and whether your price positioning is deliberate.

Framework: Name the specific competitor prices and your specific positioning relative to them.

"Marg ERP charges ₹8,000-12,000 per year plus a ₹15,000 setup fee — total Year 1 cost of ₹23,000-27,000. Vyapar charges ₹3,500 per year. We charge ₹30,000 per year with no setup fee. We are priced above Vyapar and below Marg ERP's total Year 1 cost, and we deliver 10x faster onboarding than both. Our positioning is: premium to the lightweight tools, affordable relative to the full ERP suite."

The Data Layer: Pricing Patterns That Indicate Strong vs. Weak Business Models

Indicators of strong pricing:

  • Gross margin above 60% for software businesses
  • Price arrived at through direct user research (willingness-to-pay tests, Van Westendorp, direct asking)
  • No discounting since launch, or a clear policy explaining exceptions
  • Price-to-value ratio where users save or earn 5-10x the price
  • A planned price increase or tiering strategy based on usage data

Indicators of weak pricing:

  • Price set by copying the nearest competitor without independent validation
  • Gross margin below 40% for a software business
  • Regular discounting to close deals
  • Inability to answer "what would happen if you doubled your price"
  • Price below the cost of the problem being solved (signals misunderstanding of user economics)

The Context Layer: Why Founders Get Pricing Questions Wrong

The timidity problem. Most early-stage founders underprice because higher prices feel presumptuous. They have not yet internalized that price signals value — a product priced too low raises questions about quality rather than gratitude about affordability. Partners probe for this specifically because underpricing is one of the most common and most correctable early-stage mistakes.

The competitor-benchmarking trap. Setting your price by looking at competitors is not pricing strategy — it is pricing abdication. Competitors may have set their prices wrong, may be targeting a different user, or may have cost structures that justify a price that does not work for you. Your price should be derived from your user's economics and your product's value delivery — not from what someone else decided to charge.

The "we'll figure out pricing later" problem. Some founders treat pricing as a detail to be resolved after product-market fit is established. In reality, pricing is part of the product — it determines who can buy, what the unit economics are, and what the business model ultimately looks like. Founders who cannot answer basic pricing questions in a YC interview signal that pricing has not been given the attention it deserves.

Keep reading

More on Interviews

Go deeper

Want the full data behind this answer?

Our YC database tracks 5,000+ companies, every batch, with application patterns, founder backgrounds, and pivot stories — the raw material we built this answer on.

FAQ

Frequently asked questions

What pricing questions does YC ask in interviews?
The most common YC pricing questions are: "What do you charge?", "How did you decide on that price?", "What would happen if you doubled your price?", "What is your gross margin?", and "Why not charge more?" These questions collectively test whether your pricing is evidence-based, whether you understand your user's willingness to pay, and whether your unit economics are sound.
How should you explain how you arrived at your pricing?
Name the specific method: a pricing survey with real users, a test where you offered different prices to different cohorts, direct conversations asking users what they currently pay for alternatives, or observation of what the problem costs them in time or money. "We looked at what competitors charge" is not a sufficient answer — partners want to know what your specific users told you about what they would pay. If you have not done pricing research, that is worth acknowledging and describing as an upcoming priority.
What is the "what would happen if you doubled your price?" question actually testing?
It tests whether you have thought seriously about your price ceiling and whether you are currently underpricing. Most founders have not tested price increases and cannot answer this question with data. The best answer names your honest assessment — whether you believe users would stay or leave — with a specific reason based on what you know about your user's economics. If you believe most would stay, that is a strong signal you should raise your price. Partners use this question to identify founders who are leaving significant revenue on the table out of pricing timidity.
Should you discuss future pricing changes in a YC interview?
Yes, when you have a specific plan. If you are currently at a low introductory price with a plan to raise it or introduce premium tiers, describe that plan specifically — the timing, the trigger (a specific metric you want to hit first), and the expected price point. Vague statements about "eventually charging more" are less credible than "we plan to introduce a ₹5,000 premium tier with distributor integration in Q3 once we have 50 customers on the base tier." Specific plans demonstrate that pricing is a deliberate strategy, not a placeholder.
How do you answer pricing questions if you have not launched a paid product yet?
Tell partners what pricing you plan to test at launch and why. Name the user research that informed the price point, even if you have not yet collected payment. "We have not launched paid yet. Based on 40 user interviews, our users currently spend ₹8,000-15,000 per year on manual processes for this problem. We plan to launch at ₹3,000 per month — well below the manual cost and below the only direct competitor — and test whether that price clears or whether we can charge more." This answer demonstrates pricing thoughtfulness even without payment data.
What is a good gross margin for a software startup at YC interview stage?
Above 60% is the general benchmark for software businesses, with 70-80%+ being strong. Gross margin measures revenue minus direct costs of goods sold — for software, this is primarily hosting, infrastructure, and any human cost directly required to deliver the product to each customer. Partners ask about gross margin to confirm that the business model is fundamentally sound — a software business with 30% gross margin suggests either significant human-delivered service components or infrastructure costs that do not scale efficiently.
How should you handle the pricing question if your model is usage-based rather than subscription?
Describe the pricing structure clearly: what the usage unit is, what the per-unit cost is, and what a typical customer spends per month. "We charge ₹0.50 per inventory scan. Our average customer runs 1,800 scans per month — ₹900 per month in practice. Our largest customer runs 4,200 scans per month — ₹2,100. We are monitoring whether a usage cap or flat-rate option would better serve our heaviest users." Usage-based pricing requires communicating both the unit economics and the actual typical spend so partners can understand the real revenue profile.
What if a YC partner disagrees with your pricing strategy?
Engage with the challenge specifically rather than defending your current price reflexively. "You might be right — we have not tested ₹5,000 and it is possible our users would accept it. Our concern has been that the price objection would slow our early adoption before we have enough product data to defend the higher price confidently. We are open to testing it — what metrics would you want to see before making that move?" This response demonstrates intellectual honesty, openness to revision, and the ability to engage constructively with pushback.
How do enterprise and B2C pricing questions differ in a YC interview?
Enterprise pricing questions focus more on contract structure, negotiation dynamics, and whether pricing is per-seat, per-usage, or outcome-based. Partners will ask about your typical contract value, your sales cycle length, and whether pricing is agreed before or after the pilot. B2C pricing questions focus more on conversion rates at the current price point, trial structure, and whether there is a meaningful free tier. The core questions — how did you arrive at this price, what would happen if you raised it, what is your gross margin — apply to both, but the context differs significantly.
Is it a red flag if you have changed your pricing multiple times?
No, if you describe each change as a deliberate test with a specific outcome. "We launched at ₹500, found that customers who paid ₹500 churned at higher rates than we expected — possibly because low price signals low value. We moved to ₹2,500 in month 3 and churn dropped from 12% to 4% month-over-month. We believe the higher price set better expectations." That narrative demonstrates pricing as a learning process rather than pricing instability.
What does it signal if a founder cannot answer what their gross margin is?
It signals that the founder does not have a clear picture of their own unit economics — which raises questions about their operational grip on the business. Gross margin is a basic financial metric that any founder should know. Not knowing it suggests either that financial tracking is not happening systematically or that the founder has not connected revenue and cost in a way that produces operational clarity. Partners interpret this as a signal that needs to be addressed before the company scales.
How important is pricing relative to other metrics in a YC interview?
Pricing is one component of the unit economics picture — alongside CAC, LTV, and gross margin — that collectively determines whether the business model is fundamentally sound. Individually, it is less important than traction (customer count and revenue growth) or retention. But a founder who cannot explain their pricing rationale specifically raises a question that colors the rest of the interview: if they have not thought carefully about pricing, what else has not been thought through carefully?

An independent resource · Not affiliated with Y Combinator · Last updated 2026-08-04