How I priced a $300K engagement without a sales team

The contract that put my consultancy on the map was $300,000 over roughly eight months. It was signed without a single in-person meeting. No deck. No salesperson. No proposal longer than one page. This is how the conversation actually went, what the price was built from, and what I'd say to anyone trying to do the same thing without a sales team behind them.

A note on the client first. Mid-market e-commerce, central Europe. Mature product, mature team, a CTO who could read code, a CFO who could read contracts. They were not looking for a vendor. They were looking for someone who would tell them when their idea was wrong. That distinction matters. We'll come back to it.

The build of the price

The price wasn't a guess. It was the sum of four separate envelopes, each with a defined scope.

Discovery phase — weeks 1–2 — $10,000. Two weeks of structured work. The output was a single document. Not a deck. Not a slide deck dressed up as a document. A real document. It contained the problem stated in their own language, a candidate architecture, a list of things I would explicitly not do, a risk register, a success metric we would both sign off on, and a recommended go/no-go decision. The $10K was real money. If the document said no-go, they paid it and we walked away. The number was high enough to be taken seriously, low enough that "no" was an acceptable answer.

Build phase — weeks 3–30 — $240,000. Twenty-eight weeks of execution. Mostly me, solo, with an occasional contracted senior engineer brought in for narrow pieces of work — roughly 200 hours of sub time across the build. No hourly billing. If we got the work done in 26 weeks, the price was still $240,000. If it took 30, same number.

Stabilization — weeks 31–34 — $30,000. Four weeks of aftercare. Defined scope: paging support, internal team enablement, runbook authoring, knowledge transfer sessions. This is the phase consulting shops underprice or skip. I had skipped it on a previous engagement and watched the client struggle for six months afterward. Never again.

Change-order reserve — $20,000. Not part of the base price. Available, with mutually-agreed scope changes, up to that ceiling. We used $5,000 of it for one scope addition in week 19. The remaining $15,000 was returned to the client at close.

Total contracted: $300,000. Actual billed: $305,000.

The discovery document

The single-page proposal is, in my experience, the most controversial part of this approach. Most consulting work involves multi-page proposals with branding, sample work, methodology slides, case studies. I do none of that.

The proposal the client signed off on was structured like this:

ENGAGEMENT PROPOSAL
[Client name] / [Engagement name]
[Date]
 
PROBLEM (in client's words)
[Two paragraphs]
 
WHAT I WILL DO
[Five bullet points]
 
WHAT I WILL NOT DO
[Five bullet points — usually longer than the "will do" list]
 
SUCCESS METRIC
[One sentence, measurable, agreed-upon]
 
RISKS
[Three top risks, each with a mitigation]
 
PRICE AND TIMELINE
[Four lines — discovery, build, stabilization, reserve]
 
TERMS
[Standard MSA reference + key exceptions]

That's the whole document. About 700 words. Fits on one page in a sensible font.

If a client needs forty pages to be convinced, the engagement will need forty meetings to ship. Both are misalignment signals. The single page filters out the clients who want vendor theater and keeps the ones who want execution.

The "without a sales team" mechanics

The lead came in through a referral. The referrer was a former colleague of a previous client of mine. Not a previous client — a colleague of one. Two degrees away. That distance is, in my experience, the strongest signal a lead can carry. First-degree referrals are sometimes returning favors. Second-degree referrals are about the work.

The conversations:

First call — 30 minutes. He explained the problem. I asked four questions. The questions were about constraints, not technology. "What can't change?" "Who internally has to be convinced?" "What does the current solution cost, both in money and in pain?" "What happens if you do nothing for another six months?" I did not pitch anything. I did not describe what I do. I asked, I listened, and at the end I said, "Let me think about this for a few days."

Second call — 90 minutes. This was the one that mattered. I walked them through a candidate architecture I had sketched. Not a diagram — just spoken. Here is what I think the shape of this should be. Here is what I would build first. Here is what I would not build until you've proven the first thing works. I said no three times in that conversation. No to building one of their existing internal tools into the new system. No to integrating with a vendor they already used. No to a "phase 2" idea they wanted me to commit to in writing. Two of those nos were the reason I got the contract.

Third call — 45 minutes with their CTO. This was the pricing call. I sent the four envelopes in advance — discovery, build, stabilization, reserve. The conversation was almost entirely about scope edges. "What counts as discovery versus build?" "What triggers a change order?" "What's the path if we want to extend beyond stabilization?" Twenty minutes of that. Then he asked, "Is this number negotiable?" I said, "The number is built from four things. We can move scope, which moves the number. We cannot move the rate."

Fourth — contract signed. Standard MSA, three exceptions, signature.

Four conversations. 165 minutes total. No deck. No proposal longer than one page. No follow-up sales emails. From first contact to signature: 23 days.

The math of the rate

$300,000 over roughly eight months. Let's lay out the hours.

34 weeks × 40 hours/week ≈ 1,360 hours total on the engagement. Mostly my own time, with roughly 200 hours of a contracted senior engineer mixed in for narrow build work.

$300,000 ÷ 1,360 ≈ $220/hour blended rate.

That's the realistic senior end of boutique consulting rates for production-grade engineering work in central Europe. Not crazy. Not cheap. The price is anchored to the value of the system being built, not to the hours.

This matters because the math is defensible. If the CTO had asked me "why $300K?", I could have shown him these numbers. He didn't ask. The number was already inside his expected band before we ever talked about it.

What the CTO told me at signing

The single most important sentence said to me in this engagement was on the signing call. The CTO said:

"I'd rather pay $300K for someone who tells me no three times in discovery than $100K for someone who says yes to everything."

That sentence is the entire value proposition of high-end consulting, said better than I would have said it. The cheap version of this work is someone who agrees with you. The expensive version is someone who disagrees with you, on the record, in writing, before the work starts.

If you cannot price the willingness to say no, you are doing volume consulting, not engagement consulting. Both are valid businesses. They are not the same business.

The actual delivery

I'm not going to put detailed metrics in writing for an anonymized client. The shape of what shipped:

An agentic system handling several million queries per month, with cost-per-query the CFO confirmed was an order of magnitude below their previous solution. A second-tier human review process for the small percentage of queries the agent could not confidently handle. Monitoring, paging, runbooks, internal training material. Knowledge transfer to a four-person internal team that continued to maintain and extend the system after I left.

The engagement ended on week 34, on schedule. The single change order added $5,000. The CTO sent a brief email at close: "On time, on price, on scope. We'll be calling you."

They called eleven months later for a follow-up engagement at roughly double the size. That's a different post.

The counter-intuitive part

No sales team is not "I don't know how to sell." It is "I sell by demonstrating thinking, not by demonstrating eagerness."

The traditional sales motion is this: prove you want the deal. Send the deck, follow up, build the relationship, lower the price, throw in a bonus, sign before quarter-end.

The boutique motion is the inverse. Prove you don't need the deal. The questions in the first call are not "what can we do for you" — they are "what shouldn't you do, and why are you sure you should do anything at all?" The candidate architecture in the second call is not the most ambitious version — it's the smallest version that would still be worth doing. The price in the third call is not negotiated down — it is structured into envelopes the client can choose between.

The unspoken signal is this: I am not afraid of you walking away. Therefore I am safe to listen to.

Clients buying real work can feel that distinction in the first 30 minutes. The ones who can't aren't your clients.

One thing I would tell anyone trying to do this

The hardest part of this engagement was the day I had to send the email saying we'd hit a wall. That email was 380 words. It saved the project. The next contract was double the size.

If you cannot send that email, you cannot run engagements at this size. The willingness to deliver bad news on time, with a plan, and without softening it, is the only thing that makes a $300K contract different from a $30K contract. Everything else — the architecture, the team, the documents — flows downstream of that one capability.

Most consulting failure modes I've watched, in friends and in my own past mistakes, come down to the unsent email. The one where you knew at week 14 that the original plan was wrong and waited until week 22 to say so.

Send the email on week 14. It will feel wrong in your hand. You will reread it once before pressing send. Choosing not to become the person who avoids that email is something you do over and over, in every contract. The client will respect you more in week 14 than the version of you who said nothing until week 22.