A fractional practice that takes three calls and two weeks to scope a sprint cannot survive its own sales cost. The practice that can close a sprint on a single 45-minute intake has radically different economics. Here is the structure of that call, the questions that determine whether the engagement is real, and the one-page SOW that goes out the same afternoon.
Why one call, not three
The conventional consulting sales cycle has three phases. A discovery call (30-60 minutes) where the prospect explains their situation. A proposal phase (1-2 weeks) where the consultant writes a custom SOW. A closing call (30-60 minutes) where the proposal is discussed and negotiated.
For a $40K sprint, that cycle costs the consultant 3 to 6 hours of time plus the proposal-writing overhead, across a 2-week window in which the prospect can cool, delay, or disappear. The cycle is designed for custom, bespoke consulting work where each engagement is genuinely different. The cost is absorbed because the deal size justifies it and the consulting firm has more than one salesperson pushing deals through the funnel at once.
A solo fractional operator cannot afford that cycle. Running it for a single deal costs three productive days across two weeks. Running it for three deals means half the operator's month is sales overhead. At that rate, the practice caps at its sales capacity, not its delivery capacity.
The one-call version cuts the sales cost to 45 minutes plus a 30-minute SOW draft. Three deals worth of sales fit inside a single afternoon. The deal close rate is higher because the prospect does not have two weeks to cool. The operator's calendar reclaims the delivery time that the three-call cycle consumed.
The trick is that this only works for sprints. Advisory retainers, ops-lead seats, and truly bespoke engagements need longer conversations because the scope is genuinely uncertain. Sprints have a repeatable pattern underneath. The call is not discovering the scope. It is matching the prospect to the pattern.
The pre-call filter
Before the call happens, the prospect has filled out an intake form. The form is the gate. If the form is empty or incomplete, the call does not happen. If the form reveals that the prospect is looking for a different shape of engagement, the call is rescheduled as a shape conversation, not a sprint scoping call.
The form captures about 12 fields. What's the problem you want solved, what have you tried, what's your current stack, what's your budget range, what's your timeline, who will be your primary contact, what does success look like in 90 days. Plus five or six fields that are sprint-pattern-specific (e.g., for a CAPI sprint, questions about current pixel setup, server-side tracking state, consent mode, audience match goals).
The form takes the prospect 10-15 minutes. That time is the first filter. A prospect who won't fill out a form is usually not ready to commit to a sprint. They want a conversation. That's fine, but it's a different engagement shape. The form filters for prospects whose problem is concrete enough to be described in writing.
The form also gives the operator time to prepare. Before the call, I spend 20 minutes reading the form, looking at the prospect's public-facing surface (their site, their store, their stack if I can identify it), and writing three hypotheses about what the right scope for the sprint would be. The call tests those hypotheses.
The 45-minute agenda
The call follows a defined structure. Each segment has a time budget and a purpose.
Minutes 0-3: frame the call
Opening: "Thanks for the form. Based on what you shared, this call has three goals. First, I want to confirm I understand the problem. Second, I want to walk you through what the sprint would look like if we're a fit. Third, by the end of the call, we should both know whether this is a yes or a no. That okay?" The prospect almost always agrees. The frame sets expectations: this is a decision call, not an exploratory one.
Minutes 3-15: confirm the problem
I restate what I understood from the form, in specific terms. "You're running a $4M/year DTC brand on Shopify Plus. Your Meta attribution has been degrading since iOS 17. You've tried the Shopify native pixel setup but the CAPI events aren't deduplicating. Does that match?" The prospect confirms or corrects. Corrections are valuable: they surface the gap between what the prospect wrote and what they actually mean.
This segment asks the five disqualifying questions if the form hasn't already answered them. The questions are designed to surface deal-killers early so neither side wastes time.
Minutes 15-30: walk the sprint pattern
Having confirmed the problem, I walk through what the sprint would actually look like. The weeks, the deliverables, the checkpoints. I'm not improvising here. I'm describing a sprint pattern that has run before, with the prospect's specific variables swapped in. "Week 1, we do X. Week 4, you get Y. Week 8, the midpoint review shows you Z."
If the prospect's variables genuinely don't fit the pattern, I surface that explicitly in this segment. "Your setup has this specific constraint that means week 5 and 6 would need to change. Here's what they'd look like instead." I do not hide fit problems to close the deal. The fit problems always surface later in delivery, and they're worse when the prospect feels surprised.
Minutes 30-40: price, terms, and decision
With the scope walked, I say the price. Not a range. A specific number. "$48,000, paid in three installments, deliverable in 90 days from signature." I stop talking after the number and wait. The silence is intentional. The prospect has to sit with the number before I fill the space.
Common responses and how I handle them:
- "That's more than we expected." Reasonable. The sprint is scoped to what was described. Either we adjust the scope to match a different budget, or this isn't the right engagement. Both are valid.
- "That's about what we expected." Good. Let's talk about next steps.
- "Can you break that down?" Yes, but the number is fixed. Breaking it down for transparency is fine. Breaking it down to negotiate it is a different conversation.
- "We need to think about it." Also reasonable. I'll send the one-page SOW this afternoon. Decision within 5 business days works well for both sides.
Minutes 40-45: close and next steps
If the call is heading toward yes, the next steps are specific. I send the one-page SOW today. The prospect reviews with their team tomorrow or Monday. Signed agreement back by end of week. First deposit within 3 business days of signing. Kickoff the following Monday.
If the call is heading toward no, the close is clean. "Sounds like this isn't the right fit right now. Thanks for the time. Stay in touch." No pressure, no follow-up pitch. A prospect who said no cleanly is a better future lead than a prospect who was pushed into a weak yes.
The five disqualifying questions
These questions reveal whether the prospect is actually buyable within the sprint shape. They're asked in the confirm-the-problem segment if the form didn't already surface the answers.
Question 1: Who signs the contract?
If the prospect isn't the decision-maker, the sprint won't close on this call. The decision-maker needs to be in the room for a one-call close. If they're not, the call is reframed: "Let's plan for a second call with [the decision-maker] within a week. This call will tee that one up." That's an acceptable compromise, but it's no longer a one-call close.
Question 2: Where is the budget coming from?
If the prospect hasn't identified the budget, the engagement is speculative. Budget identification is different from budget approval. A prospect who says "we have $50K allocated for this in Q2" is buyable. A prospect who says "we'd need to see what the price is and then figure out where to pull from" is not.
Question 3: What have you tried?
Prospects who have tried nothing are a different engagement than prospects who have tried multiple things. The former might need a different shape. The latter is usually sprint-ready, because they've validated the problem is real enough to pay for.
Question 4: What does success look like at day 90?
If the prospect can't articulate success, the sprint's deliverable is at risk. A concrete answer ("CAPI events deduplicated, match quality above 80%, and the first dashboard operational") gives us the scope test. A vague answer ("we'd like to see improvements across the board") is a warning. If that's all they have, I explore further before quoting.
Question 5: Who on your team will be on the hook?
A sprint requires client-side capacity. If there's no one on the client team to receive handoffs, answer questions, review deliverables, the sprint can't ship. The answer has to be a specific named person with real calendar time, not "our team."
The one-page SOW
The artifact that goes out at the end of the call is a one-page SOW. Not a proposal. Not a pitch deck. An SOW the prospect can read in 5 minutes, understand, and sign.
The one-page SOW has six sections. Scope (bulleted list of inclusions). Out of scope (bulleted list of exclusions). Deliverables and timeline (week-by-week table). Price and payment terms. Client responsibilities. Agreement (signature block).
That's it. The marketing language, the case studies, the "about me" section all live elsewhere. The call sold the engagement; the SOW is just the contract.
The template for the one-page SOW takes 15-30 minutes to fill in for any given sprint because 80% of the content is boilerplate from previous sprints. Only the specifics change. The productized SKU article in this cluster goes deeper on why this boilerplate works: the sprint pattern is repeatable, so the SOW can be templated.
“The call sold the engagement. The SOW is just the contract.
”
The follow-up cadence
After the SOW goes out, the follow-up is specific and bounded. One email confirming the SOW was sent, timestamped. A follow-up 3 business days later: "Any questions before you decide?" A second follow-up on day 7: "Let me know if this is still on your radar. Happy to answer any questions." That's it.
If there's no response by day 10, the deal is dead. I don't chase it. Dead deals can revive later (sometimes months later, with different circumstances). Chasing them hard damages that future revival. Letting them go clean keeps the door open.
How this call fits the practice
The one-call scoping move is a structural choice about how the practice runs. It requires productized sprint patterns underneath, or the call can't compress scope into 45 minutes. It requires confidence in the pricing, because a range won't close in the moment. It requires the discipline to decline deals that don't fit the pattern.
The intake pattern is one of the templates distributed inside the Operator's Stack, which packages the full intake-to-close flow for fractional operators across the product suite. In exchange, the practice spends 1% of its time on sales and 99% on delivery. The contrast with a consulting practice that spends 30% of its time on sales is radical. The practice OS article covers the full infrastructure that makes this sales model possible; the intake form, SOW template, and follow-up sequences are artifacts of the system, not inventions made per engagement.
The one-call move also filters buyers. Prospects who need three calls and a custom proposal are self-selecting out of the sprint product. That's appropriate. Those prospects belong in the advisory or ops-lead shapes, not the sprint shape. The four engagement shapes article covers the matching logic.
Frequently asked questions
Doesn't this feel pushy to the prospect?
Most prospects prefer it. Three-call sales cycles are exhausting for both sides. A 45-minute call that produces a clear yes-or-no is respectful of the prospect's time. The ones who don't like it are usually the ones who were going to deliberate for weeks and then say no anyway. Filtering those out at intake saves everyone.
What if the prospect asks for a custom proposal anyway?
The answer depends on their shape. If they want a different engagement shape (retainer, ops-lead seat), the sprint pattern doesn't apply and a custom conversation is appropriate. If they want a custom version of the sprint, I decline and offer the productized SKU or a bespoke engagement at higher pricing. The productization article covers this boundary.
Can I do this for sprints I haven't run three times yet?
Not reliably. The first-time and second-time sprints need more conversation because the scope isn't stable. Use the three-call cycle for new sprint patterns. Compress to one call once the pattern has run enough times that you can describe the weeks from memory.
How do I handle objections in the moment?
Most objections fall into three buckets: price, timeline, scope. For price, either the scope adjusts or the deal doesn't fit. For timeline, same. For scope, the disqualifying questions earlier in the call should have surfaced the issue; if they didn't, there's a gap in the intake form. Update the form for next time.
What's the close rate on one-call scoping?
Higher than three-call cycles in my experience, because prospects who arrive at the call have already self-filtered through the intake form. The close rate on the call itself is around 50-60%. Prospects who don't close on the call rarely close later.
Sources and specifics
- The 45-minute agenda structure is the one I currently run. Each segment's time budget is empirical, adjusted over several dozen intake calls.
- The five disqualifying questions are the ones that most reliably surface deal-killers. They're asked in every call where the intake form didn't already answer them.
- The one-page SOW template has been refined across Q4 2025 and Q1 2026. Earlier versions were longer and closed less reliably.
- The follow-up cadence (day 3, day 7, dead at day 10) is the bounded loop that replaces endless drip campaigns.
- The fractional practice hub frames where this sales mechanism fits in the broader practice architecture.