"How do product-led companies think about pricing when they cross into enterprise territory?"

Tell me what's top of mind for you on this topic right now — what are you wrestling with?

Right now the thing I keep coming back to is the gap between how a product-led company presents itself at the self-serve layer versus what it actually needs to look like when we're evaluating it at the enterprise level. We're on the buying side of this fairly often — a vendor comes in that's clearly grown up through PLG, has great adoption among individual users internally, and then when procurement and legal get involved, there are real gaps. Compliance documentation isn't ready, the contract structure is still very consumption-based in a way that doesn't fit how we budget, and the brand experience shifts noticeably once you're off the main product surface. The other thing is pricing credibility. When I see a tool that's been $50 a seat and suddenly wants to have an enterprise conversation at a much higher number, there's a positioning problem that's hard to paper over. The price point signals something about how the vendor sees itself, and that matters when I'm eventually explaining this purchase to a board that's already skeptical of new spend.

What's the most important thing you need to understand or solve here?

For us, the core tension is that product-led companies are built around self-serve discovery — the product speaks for itself, pricing is transparent, land-and-expand is the whole motion. But when you cross into true enterprise, that model breaks down pretty quickly. You're dealing with procurement, legal, security reviews, sometimes a six-to-twelve month cycle, and none of that maps to "sign up and upgrade when you're ready." So the thing I'm trying to understand is where the handoff actually happens — at what point does the PLG motion stop carrying the deal and the enterprise sales infrastructure need to take over? Because if you get that timing wrong, you either leave money on the table or you spook the buyer by not looking ready. The other piece, which is more directly my problem, is brand credibility. Enterprise procurement committees are evaluating you before anyone's even logged into the product. If the positioning and pricing don't signal the right tier, you're already losing.

What does 'good' look like to you — and how far are you from that today?

For us, "good" means a pricing model that actually reflects the value we deliver at the enterprise level — not one that's been stretched awkwardly from a self-serve tier that was built for a completely different buyer. It means procurement, legal, and security can all get what they need without the process falling apart, and it means our board sees a clear line between what we charge and the outcomes we're producing. How far are we from that? Closer than we were 18 months ago, but still not there. The compliance infrastructure has gotten more mature — SSO, audit logs, that kind of thing — but the pricing architecture itself still has some legacy self-serve logic baked in that doesn't hold up well when we're in a room with enterprise procurement. That's the gap I'd most want to close right now.

What would change your perspective on this entirely?

That's a fair question. I think if I saw consistent data showing that enterprise buyers were genuinely comfortable with usage-based or consumption pricing at the contract stage — not just in the PLG motion leading up to it — I'd revisit some of my assumptions. Right now my instinct is that procurement committees and finance teams want predictability, so they push back on anything that feels variable. But if that behavior shifted meaningfully, the whole conversation around how you structure enterprise tiers would look different. The other thing that would change my view is seeing a PLG company successfully skip the credentialing phase — the SOC 2, the SSO, the security reviews — and still close enterprise deals at scale. I haven't seen that happen cleanly yet.

What question are you not being asked that you wish someone would ask?

That's a fair question. I'd probably want someone to ask more about what happens to brand equity when a PLG company moves upmarket too fast without building the credibility infrastructure first. The pricing conversation tends to dominate — "what's your enterprise tier, how do you structure it" — but the harder problem is that procurement committees are judging your product before anyone logs in. If your positioning, your security documentation, your overall presence still reads as "self-serve startup," no price point fixes that. The deal dies upstream. We've had vendors come to us in that exact situation — the product is genuinely good, but the enterprise wrapper isn't there yet, and my team can't champion it internally when it looks that way to our legal and procurement groups.

Tell me what's top of mind for you on this topic right now — what are you wrestling with?

Right now the thing we're actively wrestling with is — we've built a pretty clean self-serve motion, freemium to paid, and it's working reasonably well for smaller teams. But we're starting to get inbound from companies that are genuinely enterprise-sized, and the pricing model we have doesn't really translate. Like, our current tiers were built around individual and small-team usage patterns. When a 2,000-person org comes in, they don't fit anywhere cleanly, and we end up in these ad hoc conversations that feel a little improvised on our end. The number we quote them, we're not always confident we're leaving value on the table or not. The other piece is — and this is something I've been reading and thinking about a lot — enterprise isn't just a bigger price tag. It's SOC 2, it's SSO, it's procurement cycles that run six months or longer, security questionnaires. We're not fully ready for all of that, and I'm trying to figure out where the right threshold is to actually lean in versus continuing to go deeper on our core self-serve segment. That's genuinely unresolved for us right now.

What's the most important thing you need to understand or solve here?

For us, the biggest question is really: at what point does your PLG motion actually break down, and what does enterprise pricing need to look like when it does? We've been growing through self-serve — developers and small teams find the product, try it, pay for it. That works well up to a point. But when we start getting interest from larger organizations, the deal dynamics are completely different. It's not one person deciding anymore, it's procurement, security, legal, maybe a VP of Eng or CTO signing off. And the pricing model that made sense for a $50/month self-serve user doesn't translate cleanly to a $100k annual contract with custom terms. So the core thing I'm trying to figure out is how to build a pricing structure that doesn't confuse the enterprise buyer but also doesn't undermine the self-serve motion that got us here in the first place.

What does 'good' look like to you — and how far are you from that today?

For us, "good" looks like a pricing model that actually maps to how different customer segments get value — where the self-serve tier is genuinely useful on its own, not just a teaser, and the enterprise tier reflects real incremental value like SSO, admin controls, audit logs, compliance stuff. Not just "pay more for a dedicated Slack channel." Where we are today is... somewhere in the middle. We've got a free tier and a mid-market plan that are reasonably well-calibrated, but our enterprise motion is still pretty immature. We haven't fully figured out the procurement and compliance overhead — SOC 2, security questionnaires, that whole layer — and until we do, I don't think we can credibly sell at true enterprise price points. And if you can't support the deal operationally, the price doesn't matter anyway. The gap I feel most acutely is that our pricing tiers were built around our costs and feature bundles rather than what customers actually value. We haven't done enough discovery with the buyers who are actually cutting the checks at larger orgs versus the users who championed us internally. Those are often very different people with very different value frameworks.

What would change your perspective on this entirely?

For us, the thing that would really shift my view is if we saw a clean, repeatable case where a PLG company moved upmarket without having to rebuild significant chunks of the product. Right now every example I can point to — whether it's something we've studied internally or just observed from the outside — involves a pretty meaningful reinvestment in things like SSO, admin controls, audit logs, compliance infrastructure. That's not a PLG motion anymore, that's a separate product track. If someone could show me a company that threaded that needle without bifurcating their roadmap, I'd rethink how I advise scoping the enterprise push. But I haven't seen that example yet, so I default to treating it as a genuine strategic shift rather than a pricing adjustment.

What question are you not being asked that you wish someone would ask?

That's a good one to end on. I think the question I'd want more people to ask is: "How do you keep your PLG motion from actively undermining your enterprise pricing?" Because once you've trained thousands of users to think of your product as free or near-free, anchoring a procurement committee to a six-figure ACV is genuinely hard. The self-serve tier that got you to scale can become a liability when you're trying to close a deal that involves legal, security reviews, and a 6-month procurement cycle. We've felt some version of that tension internally — the SMB users who love the product sometimes become the loudest voice against the enterprise price point, even though enterprise is a completely different value exchange. Most conversations I have are about how to build the enterprise motion. Fewer people ask how to protect the enterprise motion from the PLG past you've already built.

Tell me what's top of mind for you on this topic right now — what are you wrestling with?

Right now the thing I keep coming back to is that we're being approached by more vendors who started as self-serve tools — someone on our team signed up, used a credit card, and now the vendor wants to convert that into an enterprise contract. And the jump in price is just... significant. We're talking about going from maybe a few hundred dollars a month to something that resembles a real software line item. What I'm wrestling with is whether that price increase reflects actual value delivered at scale, or whether it's just the vendor's recognition that they're now in a procurement process and they can charge differently. Because once you're in that room — with legal, IT security, compliance — the vendor is getting something real from that relationship too. They're getting credibility, they're getting a reference account. So I want to understand what I'm actually paying for. The other piece is headcount. These tools often come in promising efficiency, but I need to see that in the numbers eventually. Not immediately, but there has to be a path.

What's the most important thing you need to understand or solve here?

For us, the core question is always whether the pricing model actually maps to how we derive value from the tool. When a product-led company shows up wanting to sell us an enterprise contract, I need to understand what I'm really paying for — because a lot of times you're paying for hand-holding, compliance infrastructure, and SLAs, not the product itself. That's legitimate, but I want it spelled out clearly. The other piece is total cost of ownership. The sticker price on these deals rarely tells the whole story once you factor in procurement time, security reviews, internal IT burden, and whatever custom work they're going to charge us for later. I've been through enough of those cycles to know the annual contract number is just the starting point.

What does 'good' look like to you — and how far are you from that today?

For us, "good" means a vendor relationship where the pricing model is actually tied to value we can measure — not just seats or modules that procurement negotiated two years ago and nobody's revisited. Good is when I can look at a contract renewal and point to a specific workflow improvement or headcount offset and say the spend justified itself. Where we are today? Probably a B-minus. We've got a few software relationships that were sold to us on a PLG motion — someone in engineering started a free trial, it spread, and by the time it hit my desk we were already operationally dependent on it. The pricing conversation at that point is not a conversation, it's a hostage situation. That's the dynamic I want to get ahead of earlier in the process.

What would change your perspective on this entirely?

That's a fair question. If a vendor came in with real, auditable data showing what comparable manufacturers in our revenue range actually paid — not just what they saved in theory, but full cost of ownership including the implementation lift, the internal headcount required to manage it, and how pricing shifted after year one — that would move the needle for me. Right now most of what I see is case studies that are essentially marketing materials. The other thing would be cleaner pricing structures at the enterprise tier. When I'm sitting across from a procurement committee trying to justify a number, and the vendor can't tell me with a straight face why the enterprise price is what it is — other than "that's what the market will bear" — it creates friction internally that's hard to recover from. If the logic behind the pricing actually tied back to value delivered in a way I could explain to my CEO, that changes the conversation.

What question are you not being asked that you wish someone would ask?

That's a fair question. I'd say nobody really pushes on the total cost of compliance when a vendor moves upmarket. Vendors come in pitching their per-seat price or their annual contract value, but the internal cost we absorb — security reviews, procurement cycles, legal review of MSAs — that's real spend that never shows up in the vendor's number. For us in manufacturing, adding an enterprise SaaS relationship isn't just a software line item. It's headcount time from IT, legal, sometimes outside counsel. I'd like to see more interviewers and analysts actually dig into that fully-loaded cost of adoption, not just what's on the invoice.

Tell me what's top of mind for you on this topic right now — what are you wrestling with?

Right now the thing I'm wrestling with is the handoff point — like, when does a product-led motion actually hand off to a sales-led motion, and who owns that conversation? We're seeing more vendors come into our space that started with a free tier or a self-serve model, and now they're trying to sell to enterprise. And honestly the seams show. The pricing conversation gets weird because they built their model around volume and low friction, and then suddenly they're trying to justify a six-figure contract to a procurement committee. For us on the sales side, it creates a credibility problem. Our buyers will say "well we can just sign up for the free version" — and I have to re-anchor the whole conversation around what enterprise actually gets them. That's a harder sell when the vendor hasn't done the work to clearly separate the two tiers.

What's the most important thing you need to understand or solve here?

For us, the biggest thing is figuring out where the self-serve motion ends and the sales motion begins. When a PLG company tries to move upmarket, there's usually this awkward middle zone where a champion inside an enterprise has already been using the product on a personal card, and now they're trying to get it through procurement. That's where deals get weird. The stuff that breaks is almost always the same — no SSO, no SOC 2, security questionnaires they can't answer, and no one on their side who's actually done an enterprise deal cycle before. The product might be great, but the buying experience falls apart when it hits a real procurement committee. From where I sit, I need to understand whether these PLG companies actually have the infrastructure to support a proper sales motion, or whether they're just hoping bottom-up adoption will carry them into six-figure contracts on its own.

What does 'good' look like to you — and how far are you from that today?

For us, "good" is when the pricing model actually maps to how customers get value — so when we're landing a PLG-origin account and converting them to enterprise, the jump from self-serve to a contract doesn't feel like we're making up a number based on what we think they'll pay. That's the version I want. Where we are today? Somewhere in the middle. We've gotten better at anchoring enterprise deals to real usage data from the self-serve motion, which helps. But the procurement cycle still introduces a lot of noise — security reviews, SSO requirements, custom SLAs — and that stuff adds cost we struggle to consistently price in. So "good" for me is also when the deal structure reflects that complexity without us discounting our way through it just to close.

What would change your perspective on this entirely?

That's a fair question. I think if I saw a product-led company actually nail the enterprise transition — not just land a few logos, but sustain it with real retention and expansion — without rebuilding their entire go-to-market, that would shift my thinking. Right now my experience is that the ones who try to coast on PLG momentum into enterprise end up with deals that stall in procurement because they're not set up for the security questionnaires, the SSO requirements, the 6-month cycles. If someone showed me a clean playbook where the self-serve motion genuinely feeds enterprise pipeline without a full sales overlay, I'd pay attention. But I haven't seen it hold up consistently at scale.

What question are you not being asked that you wish someone would ask?

That's a good one. I'd say — what does the comp plan actually look like when a PLG company goes upmarket? Because everyone talks about the product motion and the pricing tiers, but nobody asks how you're incentivizing the sales team to work those expansion accounts versus just hunting new logos. In my world, that's where things break down. The structure of the plan determines behavior, full stop. If you're not measuring the right things — commits, consumption thresholds, whatever the right metric is for that motion — you're going to have reps ignoring the self-serve tail entirely and cherry-picking the deals that look like traditional enterprise. That misalignment is a real problem and I don't hear it talked about enough in these conversations.