You’ve been doing good work for the marketing team at a mid-sized company for eight months. The CMO knows your name, the results are measurable, and the relationship is solid. Meanwhile, the sales team in the same building is dealing with a conversion problem that you could solve in your sleep. Nobody connects these two things, because nobody thinks to.
This is the most common missed expansion opportunity in freelance consulting. The clients who could benefit from your work in adjacent roles are already in a company you have access to. Your champion knows them personally. The trust that took you eight months to earn in marketing is transferable, not fully, but substantially, to an introduction in the next department.
The only thing standing between you and double the account value is one conversation with your champion and one meeting with their colleague. Most freelancers never have this conversation because it feels presumptuous or overly commercial. It doesn’t have to. The framing makes all the difference.
Identifying the Adjacent Team
Not every department adjacency is worth pursuing. The best cross-department expansion targets share two characteristics: they deal with a problem in your category of expertise, and they are organizationally connected to your current champion in a way that makes an introduction natural.
Map the departments that are adjacent to where you currently work:
Marketing → Sales: Both care about pipeline, messaging, and customer acquisition. A marketing engagement often produces insights directly applicable to sales enablement.
Marketing → Product: If you’ve worked on user-facing messaging, the product team cares about the same user behavior through a different lens.
Operations → Finance: Efficiency work in one department often surfaces financial modeling needs in the other.
HR → Communications: Employer brand work bridges these two departments almost perfectly.
IT → Security or Data: Technical infrastructure work in one domain frequently exposes needs in the adjacent one.
The rule is specificity: don’t approach adjacent departments in general. Identify the specific problem your work with the current department has surfaced, and connect it to a KPI the adjacent team cares about. “Your sales team might be losing deals because of a messaging gap we just identified in marketing” is a precise, actionable pitch. “I also work with sales teams” is not.
The Intro-Engineering Ritual
The intro request has three components. Run them in sequence, don’t combine them into a single message.
Step 1: Establish the finding. In a conversation with your champion (after a win), mention what you’ve noticed: “One thing that came up while we were working on the [specific deliverable] is that it has a direct parallel in how the sales team handles [related issue]. I don’t know if that’s on anyone’s radar internally.”
This plants the seed without asking for anything. You’re demonstrating that you see the whole picture, not just your department’s corner of it.
Step 2: Wait for the champion to respond. In most cases, they’ll say something like “yeah, I’ve thought about that” or “actually, [sales lead’s name] mentioned something similar.” This is your opening. If they don’t bite, wait a week and revisit: “Have you given any more thought to the sales angle we were talking about?”
Step 3: Make the ask. Once the champion has acknowledged the connection:
“If you thought it would be useful, I’d be happy to have a quick conversation with [sales lead or relevant person] to share what we found and see if there’s a fit. I don’t want to overstep, but if you think the intro would be welcome, I’m happy to take it from there.”
The phrase “I don’t want to overstep” is load-bearing. It signals respect for the champion’s judgment about their internal relationships, which removes the pressure and makes them more likely to offer the intro.
The intro that lands is framed as a resource you’re offering to their colleague, not a revenue opportunity you’re pursuing. “I think I could help [name] with [specific problem]” converts. “I’d love to explore working with other teams here” does not. The distinction is entirely about whose benefit you’re centering.
The Intro Email Template
If your champion agrees to make the introduction, offer to draft the intro email for them. This is a professional courtesy that makes it easier for them and ensures the message is accurate:
“Hi [New Contact Name],
I wanted to connect you with [Your Name], who has been working with our team on [brief description]. We just wrapped [specific result], and in the process, we noticed that some of the same dynamics apply to [adjacent problem relevant to their team].
[Your Name] has a good sense of where the leverage is and could give you a quick overview of what we found. Thought it might be worth a 20-minute conversation if you’re interested.
[Champion Name]”
This template does the right things: it leads with a result (credibility by proxy), connects explicitly to the new contact’s domain, and frames the meeting as low-commitment (20 minutes) rather than a full pitch.
When you follow up to the new contact directly (after the champion intro), add one line that connects to their specific KPIs: “Based on what [Champion] shared with me about your team’s focus on [specific metric], I think there’s a relevant angle here. Happy to walk you through what we found in 20 minutes.”
Adapting the Pitch to Different KPIs
The first meeting with the adjacent team is not a replay of your marketing pitch. It’s a re-framing of the same work through the lens of their priorities.
Before the meeting, ask your champion: “What’s [new contact’s name] most focused on right now? What are they measured on?”
Then rebuild your opening:
Marketing to Sales example: “What we found in the marketing audit is that the conversion story breaks down at a specific point in the funnel, and that break-down is probably showing up in your team’s close rate on [specific deal type]. Here’s what we saw and why it’s relevant to your pipeline.”
Marketing to Product example: “The user research we did on the marketing side surfaced a pattern about when users drop off in the acquisition flow. The same drop-off is probably happening in product onboarding, different context, same underlying behavior.”
You’re not selling new services. You’re showing the new contact that the work you’ve already done has implications for them, and that you understand those implications well enough to have a useful conversation. The sale follows from the usefulness.
The Timing Rules
Ask only after a visible win. A champion who is uncertain about your value will not put their credibility on the line with a colleague. A champion who is delighted by a specific result will introduce you enthusiastically. Wait for the win.
Ask within 2-4 weeks of the win. The enthusiasm window is real. After 4-6 weeks, the champion has moved on to other priorities and the specific win feels less immediate. The same introduction request lands differently in week 2 versus week 8.
Never ask during a difficult moment in the current engagement. If there’s a deliverable running late, a miscommunication being resolved, or any friction in the current relationship, wait. Cross-department expansion requires a champion who is fully comfortable advocating for you. Fix the current relationship first.
After a failed intro, wait 90 days. If the adjacent team didn’t convert, don’t circle back in a month with a different angle. Wait 90 days, then reapproach with new context: “I’ve been working on something relevant to [their specific challenge] and thought of you, would it be worth a quick catch-up?”
The best cross-department expansions don’t feel like expansions, they feel like the natural extension of work that was already happening. When your champion introduces you, it’s because the introduction makes sense to them. Your job is to make the connection obvious and the ask easy.
Measuring Expansion Success
Track three metrics for your cross-department expansion efforts:
- Intro conversion rate: Of intro requests made to champions, what percentage result in an actual introduction? Target 60-70%.
- Meeting conversion rate: Of intro meetings held, what percentage convert to a proposal or engagement within 90 days? Target 40-55%.
- Account value multiplier: For accounts where cross-department expansion worked, what’s the revenue multiple versus before the expansion? Most successful cross-department expansions add 50-150% to account value.
These numbers compound. An account that starts at $8,000/year and expands cross-department to a second team at $6,000/year is now a $14,000 account. Expand to a third team, and the account becomes $20,000, without any new client acquisition work.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
