Pricing a Done-With-You Service — The Constraint That Makes It Work
Most people who try to price a done-with-you service reach for one of two familiar models and get burned by both. Hourly pricing turns you into a meter the client watches instead of a guide they trust. Project pricing turns "we'll get this done" into "we'll get this done, plus these twelve things you didn't scope." Both models work fine for other businesses. Both actively sabotage DWY delivery — and understanding why is the entire pricing problem.
The fix is a constraint. Not a pricing model, exactly — a structural decision that makes the right pricing model inevitable. Fixed sessions, fixed scope, fixed price. Everything else follows from that.
Why Hourly Pricing Kills DWY
Hourly billing creates a perverse dynamic where the client is incentivized to rush you and you're incentivized to slow down. Neither of you will admit that's happening, but it is. The client starts watching the clock at minute 15. You start feeling pressure to move faster than the material allows. The session becomes about time management instead of skill transfer — which is the one thing a DWY engagement is supposed to deliver.
There's a deeper problem. Hourly pricing anchors the conversation to your time instead of the client's outcome. When you charge $200/hour, the client is buying hours. When they're buying hours, every minute feels like spend, and the natural response to spend is to minimize it. They'll skip the pre-work to save a session. They'll rush through the working block because the clock is running. They'll skip the recap because "we're almost out of time." Every shortcut they take degrades the deliverable, and the degraded deliverable is what they'll judge you by.
The worst part is what hourly pricing does to referrals. A client who paid $200/hour for four hours will tell a friend "I paid $800 for some coaching sessions." A client who paid $5,000 for a complete AI workflow setup will tell a friend "I paid $5K and now my content pipeline runs itself." Same engagement, completely different story — and the story is what sells the next one.
Why Project Pricing Kills DWY
Project pricing sounds better on paper. You name a deliverable, you name a price, the client agrees, and you work until it's done. The problem is the word "done." In a done-for-you engagement, you control the definition of done because you control the work. In a done-with-you engagement, the client is doing the work, which means the client is constantly discovering adjacent problems, new requirements, and things they "also want to cover while we're at it."
This isn't bad faith. It's the natural consequence of someone learning a new system in real time. They didn't know about the email automation edge case until you showed them the automation builder. Now they want to handle that edge case. They didn't realize their CRM data was messy until session two, and now they want to clean it up before session three. Each of these is reasonable in isolation. In aggregate, they double your delivery time while the price stays fixed.
Project pricing also creates an unhealthy finish-line problem. The client has a fixed price in their head, and they want to extract maximum value from it. You have a fixed price in your head, and you want to deliver the minimum viable outcome that satisfies the agreement. These two impulses collide in every DWY engagement that uses project pricing, and the collision usually ends with one party feeling shortchanged.
The Constraint That Works
Here is the model: "We meet X times. Each session is 60-90 minutes. By the end, you have [specific deliverable]. The investment is $Y." That's the entire pricing conversation.
The fixed session count is the constraint that makes everything else work. It forces you to define the deliverable tightly enough to fit in the sessions. It forces the client to do their pre-work because wasted sessions don't get replaced. It prevents scope creep because there's nowhere for scope to creep to — the sessions are the sessions, and the deliverable is the deliverable.
The constraint also solves the "what if they need more" problem before it arises. They buy another package. Not an extension, not a discounted add-on, not "just one more call." A new package with a new scope and a new price. This boundary protects both of you — the client gets a clear decision point instead of an ambiguous slide into more spend, and you get a clean engagement with a defined end.
How to Set the Number of Sessions
Start with the minimum number of sessions required to deliver the outcome reliably for a competent, motivated client who does their homework. That's your baseline. Now add one buffer session — not for scope creep, but for the inevitable moment when something doesn't work as expected and you need to troubleshoot live.
For most AI tool setup engagements, the number is four. Session one: audit the current workflow and identify where AI fits. Session two: select and configure the tools. Session three: integrate with existing systems and test. Session four: handoff, troubleshoot, confirm the client can maintain it independently. Some engagements need five or six — complex multi-tool setups, clients with legacy systems, anything involving custom integrations. Very few need more than six. If you're consistently going past six sessions, your scope is too wide.
The session count should feel slightly tight. That's by design. A DWY engagement that has room for leisurely exploration is a DWY engagement where the client never develops urgency about the pre-work. Slight time pressure keeps everyone focused on the deliverable instead of the process.
How to Set the Price
The price anchors to the value of the outcome, not the hours you spend. This is the single most important sentence in this article, and most people will nod at it and then go price based on hours anyway. So here's the concrete version.
Ask yourself: what is this outcome worth to the client over the next 12 months? If you're setting up an AI content pipeline that saves a business owner 15 hours per week, that's roughly 750 hours per year. If their time is worth $100/hour — a conservative estimate for most business owners — the outcome is worth $75,000 over 12 months. Charging $5,000-$10,000 for that outcome is 7-13% of its annual value. That math is easy for any rational buyer to accept.
The conversation structure matters as much as the number. You talk about the outcome first, the investment second. Never lead with price. The sequence is: "Here's what we'll build. Here's why it matters for your business. Here's what it's worth to you over a year. Here's the investment." By the time you say the number, the client has already anchored to the value. The $5,000 feels like a fraction of what they're getting, because it is.
One more thing about the price conversation — if you feel uncomfortable saying the number, it's too low. A price you can state calmly and then stop talking is a price you believe in. A price you immediately follow with justifications, discounts, or "but we can work something out" is a price you don't. The client can hear the difference. Set a price you can say once and then be silent.
The "What If They Need More" Protocol
They buy another package. That's it.
No extensions. No "let's add one more session at a discount." No "I'll throw in an extra call since we're close." Every one of those concessions trains the client to expect flexibility on boundaries, and the boundaries are what make DWY work. The moment the boundary flexes, you're no longer running a structured engagement — you're running an open-ended consulting relationship, and open-ended consulting relationships are where burnout lives.
The protocol for handling "but I need more" is straightforward. Acknowledge the need. Explain what a second package would cover. Quote the price. Let them decide. Most clients who genuinely need more will buy more — they've already seen the value of the first package. Clients who balk at paying for a second round were hoping to get more from the first one for free, and that's exactly the dynamic the constraint exists to prevent.
What This Looks Like in Practice
A concrete example. You offer a 4-session AI workflow setup package for $5,000. The deliverable is a fully configured content pipeline — from ideation to draft to published post — using Claude, n8n, and the client's CMS. Each session is 90 minutes. Between sessions, the client has homework and access to a shared doc for async questions (time-boxed to 15 minutes of your time per day).
Session one: you audit their current process, identify the bottlenecks, and map the tool stack. Session two: they configure Claude Projects and n8n workflows with you steering. Session three: integration testing — they run the full pipeline start to finish while you watch and troubleshoot. Session four: handoff — they demonstrate they can run it independently, you document any remaining gotchas, and the engagement ends.
Total time investment for you: six hours of sessions, maybe four hours of async support, two hours of prep. Twelve hours for $5,000 — roughly $416/hour on your end. That's the DWY math working as designed. The client got a working system and the knowledge to maintain it. You got paid like an expert because you delivered like one. And neither of you spent a single minute watching the clock.
This is part of CustomClanker's Done-With-You series — turning AI skills into client revenue.