How to Keep Revenue Steady Between UX Consulting Engagements

The Gap Problem Every Independent UX Consultant Knows

If you have been doing independent UX work for any real length of time, you know the pattern. You finish an eight-week engagement (maybe a product discovery sprint or a design system audit), and suddenly your calendar is empty. The next project is not signed yet. The pipeline you neglected while you were heads-down on deliverables has gone cold.

Two weeks pass. Then four. You start refreshing your inbox like it owes you money.

I have been an independent UX consultant for over a decade. For the first several years, I treated the gaps between engagements as an unavoidable tax on freelance life. Something you just endure. I would scramble to line up the next project, lower my rates to close faster, or take on work that was not a good fit just to keep the lights on.

What changed everything was building a set of relationships that generate income even when I am not actively delivering UX work. Not side projects. Not productized offerings. Referral relationships (structured ones) with dev shops, product managers, and other freelancers who need UX expertise on demand.

This post covers exactly how I built those relationships and how they work in practice.

Why UX Consulting Has a Revenue Gap Problem in the First Place

Most UX consultants sell their time in blocks. A six-week research engagement. A three-month design sprint. A four-week usability audit. When the block ends, so does the revenue, immediately.

Unlike a SaaS product or a retainer-based marketing agency, there is no recurring revenue smoothing out the dips. Every project is a discrete sale. And the sales cycle for UX consulting is not fast. Enterprise clients take four to eight weeks from initial conversation to signed statement of work. Startups move faster but pay less, and their budgets disappear without warning.

The result is a revenue curve that looks like a mountain range: peaks during active engagements, valleys between them. The valleys are where most solo UX consultants lose money, lose confidence, and make bad decisions about what work to accept next.

Building Referral Relationships with Dev Shops That Need UX on Demand

The most consistent source of between-engagement income I have found is partnering with development agencies and software shops that do not have in-house UX capability.

This is more common than you might think. A lot of dev shops (especially teams of 8 to 30 engineers) win contracts to build products but have no researcher, no interaction designer, and no one who can run a usability test. Their clients need UX work done before development starts, or alongside it, and the dev shop needs to bring someone in.

If you are that someone, you get pulled into projects as a subcontractor without having to do any sales work yourself. But the relationship goes both ways. Sometimes you are the one who attracts a lead that needs both design and development. When that happens, you refer the development portion to the dev shop, and earn a referral fee when the project closes.

How to find the right dev shop partners

• Look for agencies that build custom products but lack design staff. Browse their websites. If the team page is all engineers and project managers with no designers listed, they are outsourcing UX or skipping it entirely. Both are opportunities for you.
• Check their portfolio for UX quality. If their case studies show functional but clearly undesigned interfaces, they need a UX partner. If the design work looks polished, ask who did it. It might have been an external consultant like you, which tells you they already pay for this.
• Start with a direct conversation. Reach out to the founder or a project lead and explain what you are proposing: you do UX consulting, you occasionally attract leads that need development, and you are looking for a development partner you can refer those leads to in exchange for a referral fee. In return, you are available to sub on their projects when they need UX support.
• Keep the list short. You do not need ten dev shop partners. Two or three that you trust to deliver solid work is enough. Your reputation travels with every referral you make, so quality matters more than quantity.

What the arrangement typically looks like

In my experience, the economics work like this:

• When a dev shop pulls me in as a UX subcontractor on their client project, I bill my standard day rate to the dev shop. They mark it up and pass it through to the client. I do the UX work, they manage the client relationship. This fills gaps between my own direct engagements.
• When I refer a lead to the dev shop (say a startup that needs both UX and engineering but I can only do the UX portion), we agree on a referral fee upfront, typically 5% to 10% of the development engagement value. If the dev shop closes a $100,000 build from my introduction, a 7% fee is $7,000 for an email introduction and a couple of calls.

The key is that both sides benefit. The dev shop gets a qualified lead they did not have to find. I get paid for an introduction I would have made anyway, because I was already talking to the client.

Partnering with Product Managers Who Need UX Expertise

Product managers (especially those at mid-stage startups or companies without a dedicated design team) are another excellent source of referral income. They sit at the intersection of business strategy and product execution, and they constantly encounter situations where UX research or design expertise is needed but not available on their team.

The referral dynamic here works differently than with dev shops. Product managers rarely send you work directly in exchange for a fee. Instead, the relationship is more reciprocal:

• A PM you have worked with moves to a new company. They need a UX consultant for a specific initiative: an onboarding flow redesign, a new feature discovery, a competitive UX audit. They bring you in because they trust your work. No formal referral fee here; this is direct project work that fills your calendar.
• That same PM also talks to other PMs. When a PM in their network asks “do you know a good UX consultant?” your name comes up. These warm introductions convert at a much higher rate than cold outreach because the recommendation carries the weight of a shared working history.
• Occasionally, a PM will bring you a project that is outside your scope: maybe it requires a full research team, or it is in a domain you do not cover. You refer it to a UX agency or another consultant, with a referral fee arrangement in place. The PM gets credit internally for solving the problem quickly, you earn a fee, and the agency gets a qualified lead.

How to stay top-of-mind with PMs

Product managers change jobs frequently. The average tenure at a startup is about two years. That means the PM you worked with in 2024 is probably at a different company by 2026, and possibly in need of a UX consultant again.

• Keep a lightweight list of every PM you have worked with. Name, company, what you worked on together, and a rough date. When you see them post about a new role on LinkedIn, reach out with a genuine note. Not a pitch, just a “congrats, let me know if I can ever help.”
• Share useful things. If you come across a usability study, a design pattern analysis, or an industry report that is relevant to a PM’s product area, send it to them with a short note. This keeps you in their world without being transactional.
• Deliver exceptional work. This sounds obvious, but the best business development strategy for a UX consultant is being the person PMs actually want to work with again. Deliver clear, actionable outputs. Communicate well. Be easy to bring into a team. PMs remember consultants who made their lives easier.

Creating a Network of Complementary Freelancers Who Send Work Both Ways

This is the strategy that took me the longest to figure out, and the one that has had the biggest long-term impact on my revenue consistency.

The idea is simple: build relationships with freelancers who do adjacent work (not competing work), and structure those relationships so you send leads to each other. The execution requires intention.

Who counts as a complementary freelancer for a UX consultant

• Front-end developers. Clients who hire you for UX and UI design often need someone to build what you designed. If you have a front-end developer you trust, you refer the build work to them. They refer UX work back to you when a client comes to them with a product idea but no design.
• Content strategists and UX writers. Many UX projects need content strategy, microcopy, or information architecture work that goes beyond what a visual designer typically delivers. A content strategist who specializes in product copy is a natural partner.
• Brand designers. Some clients approach you for UX but also need identity work, visual branding, or marketing design. That is not your wheelhouse. A brand designer handles it, and when their clients need product UX, they send them to you.
• User researchers. If you focus primarily on interaction design or UI, partnering with a dedicated researcher means you can offer a more complete package to clients who need both. The researcher sends you projects that need design execution; you send them projects that need foundational research.
• Product strategists and business analysts. These professionals scope product roadmaps and define requirements. They regularly encounter moments where the client says “we need someone to design this.” Be the designer they recommend.

How to structure reciprocal referral relationships

The difference between a casual “I will keep you in mind” and a relationship that actually generates revenue is structure. Here is what works:

1. Have the conversation explicitly. Do not assume a freelancer you worked with once will think of you when a lead comes in. Reach out and say: “I regularly get clients who need front-end development after the design phase. Would you be open to a referral arrangement where I send those leads your way and we agree on a fee?”
2. Agree on terms before any leads change hands. Percentage of project value, what triggers the fee (project closes, first payment received), and payment timeline. A simple email exchange confirming these terms is enough to start. The point is that both sides know what to expect.
3. Start by referring first. The fastest way to activate a reciprocal relationship is to send someone a qualified lead before you ask for anything in return. That gesture demonstrates your value as a referral partner and creates natural momentum for reciprocity.
4. Keep each other informed. When you refer a lead, follow up a week later to ask how it went. When someone refers a lead to you, report back on the outcome. This accountability is what separates a real referral network from a collection of business cards.

The compounding effect

What makes this powerful over time is that referral networks compound. The front-end developer you refer work to also knows a project manager, who knows a startup founder, who needs a UX audit. Each person in your network has their own network. As your reputation as someone who sends good leads and delivers excellent work spreads, the inbound volume increases without any additional marketing effort on your part.

I started with two referral partners. Today I have five core relationships that generate consistent deal flow. Between them, they account for roughly a third of my annual project pipeline. More importantly, those referrals tend to arrive during the gaps between my direct engagements, because the freelancers in my network are working on different project cycles than I am.

Earning Referral Fees When You Connect Clients with Specialists

Not every lead that finds you is work you should take. Sometimes the project is outside your specialty. Sometimes the scale is wrong. Sometimes the client needs capabilities you do not have: motion design, accessibility remediation at enterprise scale, multilingual content strategy.

The instinct for most consultants is to say “sorry, I am not the right fit” and move on. That instinct is leaving money on the table.

How referral fees work in UX consulting

When you connect a client with a specialist or agency who can do the work, and that introduction leads to a closed engagement, a referral fee compensates you for the value of that introduction. Here is what the arrangement looks like in practice:

• Typical fee range: 5% to 15% of the engagement value, depending on how warm the lead is and how much qualification you did before making the introduction.
• When the fee is earned: Tied to the engagement closing: meaning the client signs the statement of work and the specialist receives initial payment. Not when you make the introduction.
• Payment timeline: Usually within 30 days of the engagement closing. Some specialists prefer to pay after receiving their first milestone payment from the client.
• Scope: The fee typically covers the initial engagement. Some arrangements extend to follow-on work with the same client within a defined period, such as 12 months.

The numbers behind this

Let me put concrete figures on it. Say you turn away three leads over the course of a year because they are not the right fit for your practice. Instead of saying no and moving on, you refer each one to a specialist you trust:

• Lead 1: A startup needs a full design system build. You refer it to a UX agency. Engagement closes at $80,000. Your 8% fee: $6,400.
• Lead 2: A product team needs dedicated user research for six months. You refer it to a researcher in your network. Engagement closes at $45,000. Your 10% fee: $4,500.
• Lead 3: A company needs accessibility remediation across their product suite. You refer it to an accessibility specialist. Engagement closes at $60,000. Your 7% fee: $4,200.

That is $15,100 in referral income from three introductions. You did not deliver any of the work. You did not manage any of the projects. You made email introductions to people you already know and structured the arrangement so you get paid when it closes.

For a solo UX consultant, $15,000 can cover one to two months of operating expenses. That is the difference between a stressful gap and a comfortable one.

4 Rules That Keep Referral Revenue Flowing

1. Qualify before you refer. Only send leads that are genuinely ready for an engagement: real budget, stakeholder buy-in, a defined problem. Sending unqualified leads wastes your partner’s time and erodes your credibility as a referral source. After a couple of bad leads, partners stop prioritizing your introductions.
2. Agree on terms before sharing the lead. This is non-negotiable. Before you give a partner any identifying details about the client, have a clear agreement on the fee percentage and payment terms. A simple email exchange works. The point is that both sides have committed before the introduction happens.
3. Provide context with every introduction. When you connect a partner with a lead, include what the client needs, their timeline, who the decision makers are, and why you think this partner is the right fit. The more useful context you provide, the higher the close rate, and the more your partner values the relationship.
4. Follow up after the introduction. Check in a week or two later. Ask how the conversation went. Offer to help if the client has questions. This shows you care about the outcome, not just the fee. It also gives you visibility into whether the engagement closed, so you know when to expect payment.

Putting It All Together: What Steady Revenue Actually Looks Like

Here is a realistic picture of how these strategies work in combination over the course of a year for a solo UX consultant:

• Direct client engagements: 7 to 9 months of billable project work, with gaps of 2 to 5 weeks between engagements.
• Dev shop subcontracting: 3 to 6 weeks of subcontractor work pulled in during gaps, billed at your standard rate.
• Referral fee income: 2 to 4 introductions per year that close, generating $8,000 to $20,000 in referral fees total.
• Reciprocal freelancer network: 2 to 3 inbound project leads from complementary freelancers, some of which become direct engagements and some of which generate referral fees in return.

None of these revenue sources require you to build a product, hire a team, or fundamentally change what you do. They are extensions of the relationships and reputation you already have. The only difference is that you structured those relationships so the value flows in both directions, including financially.

Common Mistakes That Undermine Referral Income

I have made most of these mistakes at some point. Sharing them so you can avoid them:

• Making introductions without an agreement. I did this early on and the fee never materialized. Once you have shared the client’s information, you have no leverage. Get the agreement first.
• Referring to people you have not vetted. The client will remember who connected them with someone who missed deadlines or delivered subpar work. Your name is attached to every referral you make.
• Being passive about reciprocity. If you are sending leads to someone and getting nothing back, the relationship is not reciprocal. It is charity. Have a direct conversation about what you are looking for in return.
• Letting relationships go cold. Referral partners forget about you if you disappear for six months. A quick check-in message every quarter, even when you do not have a lead to send, keeps you visible and keeps the relationship active.
• Taking on bad-fit projects out of desperation. The whole point of building referral income is to give you the financial cushion to be selective. If you still accept every project during gaps, you are undermining the strategy. Refer the bad-fit projects out, earn the fee, and wait for the right engagement.

Getting Started This Month

If this approach is new to you, here is what I would do in the next 30 days:

1. Identify one dev shop that does not have in-house UX. Reach out to their founder or project lead. Propose a mutual arrangement: you are available for subcontractor UX work, and you occasionally have leads that need development. Agree on referral fee terms.
2. Reach out to two freelancers whose work complements yours. A front-end developer and a content strategist are good starting points. Have an explicit conversation about sending leads to each other and what the terms would look like.
3. Send a check-in message to three PMs you have worked with. Not a pitch. Just a “how is the product going?” message that keeps you in their orbit.
4. The next time a lead comes in that is not the right fit, refer it. Find a specialist who can do the work, agree on a fee, make the introduction with full context, and follow up.

The first referral arrangement takes the most effort because you are building trust from scratch. After that, the pattern becomes familiar. You have proven partners, clear terms, and a track record that makes every subsequent conversation easier.

If you want a straightforward way to manage referral agreements and payment coordination with your professional partners, take a look at what PureIntro offers for tech and digital professionals.

This post reflects one professional’s experience and is for informational purposes only. It is not business, legal, financial, or professional advice. Results described are individual and not guaranteed. Referral fee arrangements may be subject to state and local regulations. Consult a qualified professional for guidance specific to your situation. PureIntro facilitates referral tracking and payment processing but does not guarantee payments between users or any particular business outcome.