Most freelancers present a roadmap and wait for approval. The client reads it, finds one thing they don’t like, and the whole thing stalls. You go back and forth on scope and pricing for three weeks. Half the time, nothing gets approved at all.
The fix is not a better proposal. It’s a different process. When clients co-design the roadmap, when they choose the priorities, sequence the work, and put their own language on the milestones, they can’t reject it. They wrote it. The psychology here is basic: people defend what they create. A plan they helped build is their plan, not yours.
This is not soft facilitation advice. It’s a structured 90-minute session with specific pre-work, a specific agenda, and a specific deliverable. Run it at the right time and it will surface expansion naturally, not because you pitched, but because they saw the gap.
Why Presenting a Roadmap Fails (and What to Do Instead)
When you hand a client a roadmap, you’ve created an adversarial dynamic. They’re the buyer evaluating a proposal. You’re the seller defending it. Every objection is a negotiation. Every change request is a loss for one of you.
Co-design flips this. You walk in without a finished roadmap. You bring a framework, some options, and data about what’s worked. The client brings their priorities. You build the document together in the room. By the end of the session, the roadmap exists, and it belongs to both of you.
The practical difference: when a client asks “why is this in scope?” after a co-design session, the honest answer is “you added it in month 3 of our workshop.” That’s a much shorter conversation.
Run this session between months 3 and 4 of a new engagement. Earlier, you don’t have enough wins to anchor the conversation. Later, inertia has already set in and expansion feels like a surprise.
The Pre-Work: Send Them Their Own Words
Two days before the session, send this email:
Subject: Pre-work for Thursday’s strategy session
Before Thursday, I pulled together the goals you shared when we started working together:
- [Goal 1 verbatim from onboarding notes]
- [Goal 2 verbatim]
- [Goal 3 verbatim]
I also put together a quick summary of what we’ve shipped in the first 90 days and the results we’ve hit. [Attach a 1-pager.]
In our session, we’ll figure out what comes next. No need to prepare anything, just bring your current thinking on priorities.
This pre-work does three things. It shows you were listening from day one. It anchors the session in their goals, not your ideas. And it creates a subtle accountability, they said they wanted X, and now they’re showing up to a meeting about it.
Don’t skip this step. The session without pre-work is a sales call. The session with pre-work is a strategy conversation.
The 90-Minute Workshop Agenda
Minutes 1–15: Review the wins
Open with what’s been accomplished. Not to celebrate, to establish a baseline of trust. Cover 3–5 concrete results from the last 90 days with numbers where possible. “We shipped the onboarding flow. Completion rate went from 34% to 61%. That’s the kind of change we’ll build on.”
Minutes 15–35: Surface their current priorities
Ask: “Given everything on your plate right now, what are the 3 things you most need to make progress on in the next 12 months?”
Write their answers verbatim on a shared doc or whiteboard. Don’t editorialize. Don’t suggest. Just capture. When they’re done, ask: “Anything you’re worried about that isn’t on that list?”
This surfaces the hidden priorities, the problems they’re embarrassed to bring up, or the concerns that feel outside your scope. These are often where expansion lives.
Minutes 35–60: Build the roadmap
Lay out 4 columns: Q1, Q2, Q3, Q4. Ask: “If we’re going to make real progress on these priorities, what needs to happen first?” Let them sequence. Your job is to add constraints (“that depends on X being done first”), flag risks (“that’s aggressive for Q1 given what we’ve got going”), and introduce options they haven’t considered (“one way to approach this faster would be Y”).
By the end of this segment, you have a rough 12-month map of initiatives, with their priorities, their sequencing, their language.
Minutes 60–80: Assign owners and metrics
For each initiative: Who owns it? What does success look like? What’s the measurement? This is where you introduce what your involvement would be. Not “here’s what I charge”, “here’s what I can take off your plate on this one.”
Minutes 80–90: Close with a shared next step
“I’ll clean this up and send you a shared doc by Friday. You review it, adjust anything, and we’ll lock in the Q1 priorities next week.” That’s a natural next meeting scheduled, with a document that needs their approval.
The expansion you’re looking for isn’t in your pitch deck, it’s in the gap between what they said they need and what your current scope covers. A co-design session makes that gap visible to both of you at the same time, which means you’re solving a shared problem, not selling an upgrade.
The Deliverable: A Shared 12-Month Roadmap
The output is a single shared document with four sections:
- Goals, their top priorities, in their words, unchanged from the workshop
- Milestones, what gets delivered by when, who owns each item
- Metrics, how you’ll both measure progress at 90-day intervals
- Investment, what the engagement looks like across the year, phased by quarter
Keep the investment section honest and phased. Q1 might look the same as your current retainer. Q2 might expand. Q3 might introduce a new workstream. Showing the full year at once makes expansion a plan, not a surprise.
Send the document within 48 hours of the session. Add a note: “I left the investment section in draft, want to talk through Q2 before we finalize numbers. Does [date] work?” That’s your expansion meeting, already scheduled.
The Buy-In Math: Why This Works at Scale
There’s a well-documented principle in behavioral economics: people feel ownership over things they helped create. This applies to decisions, plans, and products. When clients co-author a 12-month roadmap, they don’t evaluate it the way they evaluate a vendor proposal. They defend it. They advocate for it internally. They align their team around it.
This has practical implications beyond the current engagement. A client who co-designed a roadmap with you will bring that roadmap into their annual budget conversations. Your name is in the document. The work you’re doing is mapped to their stated priorities. That’s a very different position than being a line item on a vendor list.
Run this session every year with every retainer client. It is the single highest-leverage 90 minutes you’ll invest in the relationship.
What to Do When They Say “We Don’t Have Budget for the Full Year”
Acknowledge it directly: “That’s useful to know. Let’s build the roadmap around what we know you can commit to in H1, and we’ll leave H2 flexible. If results in Q1 and Q2 are strong, we’ll have a natural conversation about Q3.”
This is not a concession. It’s a time-bound plan with a built-in review point. You’re not getting a smaller engagement, you’re getting a 6-month engagement with a scheduled expansion conversation baked in.
Never negotiate the roadmap down to nothing to close it faster. A vague plan with no commitment is worse than no plan at all. If the budget isn’t there for the full year, sequence clearly and lock in the first phase with a hard review date.
The Compound Effect of Running This Every Year
The first co-design session builds a roadmap. The second one, 12 months later, reviews what happened and designs what’s next. By the second session, you’re reviewing whether the goals from year one were met, and the client is already thinking about year three.
This is how 2-year retainers happen. Not because you asked for a 2-year contract, but because the client looked at the roadmap and said “if we finish this in month 10, we’ll want to start the next phase by month 12.”
Set a recurring reminder the day after you deliver any engagement: schedule the co-design session for month 3. That single habit will do more for your expansion revenue than any proposal template or pricing strategy you implement.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
