How Do You Price Your First Enterprise Deal With No Enterprise Pricing?

A buyer far bigger than your usual client wants a quote. What do you charge?

More than your rate card says, and for different reasons than you expect. You are not pricing more hours. You are pricing coordination, risk and the cost of being answerable to a company with a procurement process. Start from what the engagement will demand of you, not from your usual number.

This moment arrives for almost everyone who sells services or software, and it is genuinely disorienting. The work looks similar to work you have done. The buyer looks nothing like a buyer you have had. Your instinct is to quote your normal price with a bit added, and that instinct is usually wrong.

I price fixed fee, and most of my projects land between one thousand and ten thousand dollars. So I have had this conversation with myself more than once, and here is how I now think it through.

Why does your existing price list stop working at this size?

Because it was built for a buyer who decides alone. Your rate card silently assumes one decision maker, a short contract, quick payment and a scope you can renegotiate over a message. A larger buyer breaks every one of those assumptions at once, and none of the breakage is in the work itself.

Think about what actually changes. There are more people to align. There is a legal review. There may be a security questionnaire asking about SOC 2, an NDA, an MSA, a data processing agreement. There is an invoicing process that does not care about your cash flow. None of that is delivery, and all of it is time.

A price list priced for delivery cannot absorb that. If you quote your usual number, you have accidentally agreed to do the coordination work for free, and the coordination work on a large account is frequently bigger than the build.

What are you actually pricing when the buyer is large?

Three things: the work, the coordination around the work, and the risk that the scope is not what either of you currently thinks it is. Most people price only the first, then absorb the other two silently and conclude afterwards that enterprise work is not worth doing.

Coordination is calls you did not need with smaller clients, reviews by people who were not in the original conversation, and rework caused by a stakeholder appearing in week three. It is predictable in kind even when it is unpredictable in amount, which means it belongs in the price rather than in your evenings.

Risk is the harder one. With a larger buyer you usually have less visibility into their internal mess before you commit. You are pricing the possibility that what looked like one system turns out to be four, and only one person still understands the fourth.

Should you quote a number in the first conversation?

No. Say you will come back with a number and a scope, and then ask the questions that let you build one. Quoting live is how people end up anchored to a figure they invented under pressure, and an anchor you set badly is very hard to move later.

This feels evasive the first time you do it and it is not. A buyer with a procurement process expects a written proposal, and giving them a verbal figure that later changes damages trust more than a short delay ever would. Take the time. It is the normal, professional move.

What you should do in that first conversation is find out how they buy: who signs, what the approval steps are, what the payment terms look like, whether a purchase order is involved. Those answers shape the price as much as the requirements do, and asking them early signals that you have done this before.

How do you find the number without a pricing model?

Estimate the delivery work the way you always do, then add for coordination and for risk as separate, named amounts. Keeping them separate is the whole trick. It stops you fudging one number upwards and lets you explain the price if you are asked to.

For coordination, I estimate the meetings, reviews and admin the engagement realistically needs and price them as work, because they are. For risk, I think about what I do not yet know, and I price the version of the project where the unclear part turns out to be worse than described.

Then I check the result against a simple test: if this project goes badly, will I resent it? If the answer is yes, the number is too low, regardless of what the spreadsheet says. That test has saved me more money than any pricing framework, and it is the reason I price fixed fee rather than hourly.

What happens if you price it too low?

Two bad things, and the second is worse. First, you do a large amount of work for too little. Second, you set a reference price for every future conversation with that buyer and anyone they refer you to, and reference prices are extremely difficult to move.

There is also a credibility effect people underestimate. A number well below what a company of that size expects to pay can read as a signal that you have misunderstood the scope. Buyers at that level are not only looking for value, they are looking for evidence that you know what you are agreeing to.

The honest version of a discount, if you want to offer one, is to reduce the scope rather than the price. That keeps your rate intact, keeps the reference price honest, and forces a conversation about what actually matters most, which is a better conversation anyway.

How do you protect yourself from scope you cannot see yet?

Price a small paid discovery phase first, deliver something useful from it, and quote the main engagement afterwards with real information. This is the single most effective thing I have found, because it converts an unknown into a known before either side is committed to a number.

The output has to be genuinely valuable on its own. A discovery phase that produces only a proposal is a sales document the client paid for, and buyers see through it. A discovery phase that produces an audit, a plan or a working prototype earns its fee whether or not the larger project happens.

It also tests the relationship cheaply. You learn how they make decisions, how fast they respond and how much internal disagreement exists, all before you take on delivery risk. That is the same logic behind pricing a pilot so it can become a contract.

When should you walk away from an enterprise deal?

When the payment terms would break you, when nobody will name a decision maker, or when the scope keeps growing while the budget does not. Any one of those is a warning. Two together is usually a no, however good the logo would look on your site.

Payment terms deserve special attention if you are small. Net 60 or longer is normal at large companies and survivable if you plan for it, but agreeing to them without planning is how a profitable project becomes a cash flow problem. Ask about terms before you fall in love with the project.

Walking away is easier when you have other work, which is the real argument for keeping a steady pipeline rather than a perfect one. I would rather lose a deal I could not price safely than win it and spend four months discovering why the price was wrong.

What should you do next?

Before your next large quote, write down your delivery estimate, your coordination estimate and your risk allowance as three separate numbers, then add them. Seeing the three parts is what makes the total defensible, both to the buyer and to yourself.

Then decide in advance what your payment terms floor is, so you are not negotiating that under pressure at the end. A position decided calmly beforehand is worth far more than a position improvised during a contract review, and it also tells you what your pricing page should say to buyers of that size.

If you are staring at a quote right now and you are not sure whether your number is brave or foolish, send me the shape of it. I will tell you honestly what I would charge. Let's chat.