# How Consulting Leaders Balance Client Delivery and Business Development - Published: 2026-10-21 - Author: [Consultant Magazine](https://consultantmagazine.co/author/consultantmagazine-co.md) - Topics: [Q&A](https://consultantmagazine.co/qa.md) - Source: https://consultantmagazine.co/qa/how-consulting-leaders-balance-client-delivery-and-business-development/ - Publisher: Consultant Magazine ### Enforce a Sixty-Forty Growth Split I protect a fixed block of time for business development first, and I only trade it away for client delivery when a deadline is truly at risk. We are an 11-person company, self-funded since 2018, so slow demand is not abstract for me. A few years back, a quiet quarter made me pull everyone into fulfillment work because it felt productive. It was the wrong call. Two months later our pipeline was thin and we had to rush to refill it. Now I use a simple rule. When demand slows, I move to a 60/40 split: 60% of leadership time on outreach and 40% on delivery, and I review it weekly. The slow period is when relationships can be rebuilt, old customers can be thanked, and new channels can be tested. We send handwritten notes to past clients during these windows, and the reply rate is high enough that it often fills the gap on its own. The checkpoint that keeps it honest: each Friday I ask, "Did anyone outside the company hear from us this week?" If not, delivery is eating the pipeline. Client work still gets done, but it does not get to quietly crowd out the work that creates the next quarter. --- ### Honor Commitments, Cultivate Tomorrow’s Demand I would not wait for the pipeline to become empty before making time for business development. By then, you are usually reacting rather than managing the situation. My rule is to protect enough capacity for business development even when client work is busy, but never at the expense of a commitment that is already important to a client. I think of it as maintaining the pipeline rather than chasing work. We use a similar principle at spectup when thinking about investor relationships. I would rather start conversations early and let relationships develop over time than suddenly need introductions when a company is already fundraising. The same applies to consulting demand. If client work slows, I would increase business development activity, but I would not immediately fill every newly available hour with sales calls. Some of that capacity should go toward improving the offering, following up with relevant relationships, and understanding where demand is moving. The decision becomes easier when you separate short term utilisation from long term pipeline health. A consulting business can look busy today and still have a weak pipeline several weeks later. Conversely, a temporarily quieter period can be useful if you use it to build relationships before you need them. I also think delivery quality has to remain non negotiable. A new opportunity is rarely worth damaging trust with an existing client. So my decision rule is fairly simple: protect current commitments first, then use the remaining capacity to strengthen the pipeline before the pressure becomes visible. That creates a healthier balance because business development becomes part of operating the firm rather than something you panic about when demand falls. --- ### Let Live Proposals Trump Extra Polish When demand slows I move straight into protecting business development time, not polishing delivery that's already good enough. My rule is simple, if I can't point to live conversations or proposals out, business development wins that week. I learned this when a decade of steady income from my own site stopped almost overnight, because I'd let pipeline work slide while delivery felt more urgent. Even then I still keep every client deadline and reply to their emails the same day, I just stop adding anything extra. --- ### Scale Lead Effort With Calendar Gaps Protect client delivery first and give business development a fixed, protected share of the week. When demand slows, the temptation is to spend all day chasing leads. That backfires, because a weak delivery experience kills referrals, the cheapest source of new work. Split the time by the size of the gap. If your calendar is 80 percent full, give business development one half-day a week. If it falls to 50 percent, raise that to two days, and move back down as work returns. Put those blocks on the calendar as client meetings, because you won't cancel them for urgent work. Spend the time in order of speed to revenue. Start with past clients and ask about their next project, since they already trust you. Then contact warm leads that went quiet. Then reach out to new prospects. Past clients convert faster than any cold outreach. Relationships and referrals matter most in slow periods. Ask three happy clients a week who else they know with the same problem, and offer a direct introduction. Track three numbers weekly, which are conversations started, proposals sent and proposals won. If conversations fall, add time. If proposals don't convert, improve the offer. --- ### Batch Outreach Windows, Experiment With Channels Separate your selling days from your delivery days. When you try to cold call between client meetings, both suffer. Block full days for outreach and you'll book more qualified appointments because you're not constantly switching gears. Try two-week sprints where 70% of your non-client time goes to testing new outreach approaches. Map your week around maker days and seller days, then protect that structure unless a client emergency pops up. --- ### Require Accountability Before Cadence Cancellations During a slowdown, allocation should follow commitments made, not fear felt. Fear makes leaders overprotect work to avoid complaints, then overcompensate with outreach when the pipeline looks worse. That oscillation is costly because clients experience inconsistency and partners see an organization that appears when it needs something. We set a minimum viable business-development cadence and review it alongside client health. The cadence is small enough to survive delivery pressure, but enough to sustain relationships and market intelligence. Any request to cancel it must identify the client outcome at risk, the owner covering it, and the date the time will be restored. That condition matters. It turns a tradeoff into an accountable exception, rather than allowing urgent work to consume the future. --- ### Automate Routines, Free Expansion Room When work slows down at Tutorbase, I look for recurring tasks and turn them into templates or code. It might push a delivery back a day now, but it saves hours every week after that. My team gets time back to focus on growth instead of just keeping up. When demand returns, we handle it without scrambling. --- ### Trigger Sales Allocation Through Conversation Thresholds Every week I check one number in my pipeline that has nothing to do with revenue. It's the count of active conversations with potential clients who could sign within 60 days. When that number drops below a threshold I've set for myself, I move business development time up regardless of how busy my current delivery load looks. I used to wait until delivery hours thinned out before picking up the phone, and by then I was already two months behind on building relationships, with desperation coloring every conversation. Now I protect a baseline of business development activity even during peak delivery weeks. If my 60-day pipeline count is healthy, I keep that baseline modest. If it dips, I bump development hours up and redistribute delivery tasks across my team or adjust timelines with clients who have flexibility. I've found I can absorb a small scheduling adjustment with a client if I'm transparent about it, but a warm lead that goes cold because I was too buried to follow up costs me far more than a minor delivery delay I communicated proactively. The pipeline count gives me a leading indicator rather than a lagging one, so I'm making the tradeoff before the slow period hits my calendar. --- ### Tie Market Research to Performance Pacing Having managed over $100M in ad spend across 200+ companies, my rule is simple: BD time is protected strictly against live performance pacing, not arbitrary calendar blocks. If active client accounts are pacing ahead on their revenue milestones, leadership automatically shifts dedicated weekly hours into prospect market research and pipeline generation. We rely on 24/7 live reporting dashboards and marketing automation to track account health without generating manual reporting overhead. If an active campaign dips in Google Ads or organic performance, BD hours are immediately pulled back to prioritize client optimization. This safeguard ensures we maintain intense, performance-first execution--like running full-funnel overhauls across SEO, PPC, and conversion rate optimization--while keeping our pipeline active during industry slowdowns. --- ### Build New Business Around Client Trust When client demand slows, my first instinct is not to fill every available hour with business development. I look at current client commitments first. The people who have already trusted me with their business should never feel a decline in service because I am looking for the next client. My decision rule is simple: protect the commitments already made, then intentionally assign a portion of the capacity that opens up to creating future business. I learned this long before starting Willowcross Consulting. In operations and sales, I have seen how easy it is to become so focused on current work that business development stops altogether. Then a project ends, a transaction closes or the market shifts, and suddenly there is nothing behind it. The opposite is equally dangerous. Chasing new business while existing clients are waiting for deliverables is a good way to damage the reputation you are trying to grow. When demand slows at Willowcross, I look at actual capacity rather than reacting emotionally to an open calendar. I identify what current clients need, what deadlines are firm and what work requires my direct attention. The remaining capacity can then be deliberately used for relationship building, follow-up, content, networking, refining offers and other activities that can generate future revenue. I also prefer business development that creates more than one benefit. Writing about a recurring operational problem, for example, can educate a prospective client, demonstrate expertise and sharpen how I communicate a Willowcross service. Improving an assessment or process can support current clients while also strengthening what I offer the next one. The tradeoff becomes much easier when I stop thinking about business development as something I do only when client work disappears. It needs a protected place in the business during busy periods and slower ones. The amount of time may change, but the activity should never completely disappear. For me, current client trust is the floor. Business development gets built around it. --- ### Use Coverage Metrics to Schedule Calls I run Alpha Coast, where we've helped 400+ coaches and consultants move from referral-driven demand to predictable booked calls. My rule is: if your pipeline depends on hope, business development gets protected before you feel "available." The decision rule I use is calendar coverage: do I have enough qualified conversations already scheduled to support the next 30-90 days of revenue? If not, I protect BD time daily, but I separate it from delivery by assigning fixed blocks instead of letting sales work leak into client hours. For many consulting leaders, that might mean keeping mornings for delivery and protecting a non-negotiable afternoon block for offer refinement, follow-up, and sales conversations. In our model, clients often need roughly 2 hours per day for discovery calls while the system handles sourcing, messaging, and booking. One example: Sandy Spencer came to us after a 26-year career business slowed down unexpectedly. Once we rebuilt her positioning, lead flow, and sales process, she hit a record $33,605 month by month three, during what had historically been her slowest season. --- ### Preserve One Day in Five The rule I use is simple. Business development gets a fixed block on the calendar, set before demand dips, and it doesn't move for delivery crunches or for slow weeks. I put it at roughly one day in five. When pipeline gets thin, I don't invent a new number in a panic. The block already exists, so a slowdown just means I use it harder. The reason is that a slow quarter is almost always the echo of a quiet one two or three months earlier. Consultants stop selling while they're busy, then wonder why the calendar empties. If the time only shows up when you're worried, you're already late. For delivery, I look at what's actually due. If a deliverable has a hard date, it wins that day and the block moves to the next morning, never off the week. If it's just open-ended work that could expand forever, it gets capped so it can't eat the block. Most overruns come from perfectionism on work that was already good enough. When demand drops, the extra hours go to follow-up with past contacts before anything new. Old conversations close faster than cold ones. Speed matters there too. MIT research found you're 21x more likely to qualify a lead if you respond within five minutes, so I answer inbound the same hour whenever I can. The confidence comes from the decision being made once, in calm conditions, instead of re-argued every time revenue wobbles. --- ### Define Exceptions for Future Reserves I frame the choice as a portfolio decision rather than a calendar conflict. Current clients represent commitments already earned, while business development represents the next set of commitments. Ignoring either side creates concentration risk, especially when demand changes without warning. The rule is to maintain a minimum future-pipeline allocation unless client delivery reaches a predefined exception level, such as a missed milestone, a serious quality concern, or an unresolved executive escalation. That threshold keeps temporary pressure from consuming all forward-looking work. It also makes exceptions explicit and reversible. Once the issue is resolved, growth time returns automatically. This gives leaders confidence because the decision is governed by observable conditions, not by whoever speaks most urgently. --- ### Showcase Prototypes to Win AI Accounts When AI consulting projects slow down, my team and I don't just wait around. We use the free time to build small AI prototypes and show them to potential clients we've been wanting to work with. That simple shift has paid off big time. Instead of wasting the downtime, we got in early with a few accounts and ended up landing new work because of it. --- ### Run Focused Sprints for Partner Trials When client work slows, I block whole days just for business development. Mixing both in one day always meant more stress and less actual progress. Last quiet stretch, we ran a two-week sprint testing a new partner approach. We kept what brought in clients, dropped the rest. Batch your work modes and run short experiments to find what actually works. --- ### Shift Leaders at Six-Week Queue When the pipeline gets thin, I block off business development time completely, like we do in real estate with closing buffers. At Capstone Land Transfer, we moved mid-level managers onto routine work so leadership could focus on outreach. Awkward at first, but it kept us stable when volume dropped. Pick a hard number, like six weeks of backlog, so you know exactly when to shift focus. --- ### Hold Utilization Within a Healthy Range I keep my utilization between 60% and 75% at MDConsultingNY. Never above, never below. When client work slowed last year, I blocked extra time on my calendar for outreach and ran a couple pilot projects. Delivery didn't slip because I had the bandwidth. Every freed hour went to calls and meetings. Growth stayed steady instead of scrambling when pipeline dried up. --- ### Map Team Bandwidth Before Innovation Blocks In my role leading Social Design House since 2009, I handle this by first running open team check-ins to map exact deadlines and capacity before carving out any business development hours. We treat those conversations like the ones Lauren described, where team members flag real plate loads so we avoid pushing creative work into off-peak times that slow delivery. When the map shows breathing room, I protect blocks for exploring new tools and side experiments that feed future client work, just as we did when testing vibe coding workflows without touching client data. That rule keeps delivery on track while turning slower periods into direct pipeline activity through honest prioritization rather than guessing at tradeoffs. --- ### Expand Visibility When Quarter Ahead Falls Short Protect business development by a calendar rule, not by how busy the week feels, and set that rule before demand drops. The rule I use as a consultant who builds marketing departments for clients: delivery keeps its committed hours, and business development gets a fixed weekly block that grows when pipeline coverage for the next quarter falls short. The trigger is pipeline, not mood. When demand slows, the two common mistakes are over-serving current clients to feel safe, or cutting delivery quality to chase new work. Both cost you. What works better is business development that reuses delivery thinking: turning a solved client problem into a public case note, a short talk, or a defined entry offer. At BMD, the paid Diagnostic plays that role, so a slow month has a clear first step for new clients instead of open-ended pitching. Current clients never feel the shift, because the visibility work comes from thinking they already paid for. --- ### Turn Local Presence Into Referrals My rule is that current clients come first, because the work they see is my best business development. When demand slows, I don't pull hours off delivery to go chase leads. I protect the client work and add business development that can run alongside it. That rule comes from how Hennhouse got started. I didn't have a pipeline. I joined a local Facebook group that cost $25 a month, which led to an in-person coffee event, then a networking group, then my first customer. That first client led to referrals, and those referrals led to more. If that first client had felt like an afterthought while I was out looking for the next one, the chain would have stopped there. So when things get quiet, the time I add goes to showing up locally: networking, sponsoring community events, and my podcast, where I interview local business owners and operators. None of that competes with a client deadline, and it keeps me in front of the people most likely to refer someone. Cold outreach that pulls me away from delivery is the first thing I'd cut. Tyler Henn, Founder & Lead SEO Strategist, Hennhouse (henn.house), Marietta, GA --- ### Delegate Repetition, Own Strategic Interviews Having spent nearly 20 years in business media before founding WONDERFISH, I rely on the "10-80-10" delegate and elevate rule. You protect your calendar by only owning the first 10% of strategic positioning and the final 10% of closing deals, while delegating the middle 80% of prospecting and content generation. When consultant Scott Abbott needed to drive authority for *BOS-UP Moments* while managing his coaching community, he didn't sacrifice delivery hours to run manual outreach. He protected his client schedule by outsourcing the booking and content repurposing, showing up only for high-impact conversations. My decision rule is simple: if a business development task requires manual, repetitive execution that threatens client focus, automate or outsource it. Protect your delivery by investing BD hours exclusively into high-leverage assets--like strategic interviews--that compound in value without requiring daily maintenance. --- ### Maintain Half Availability for Nonbillables I started keeping my non-billable time around 50% and it changed everything. Business development and client work finally balanced out. In finance, that matters. When deals slow down, I don't wait around. I get out and meet developers and lenders instead. The panic about empty weeks basically disappeared. Having a rule for how to shift my time keeps me from burning out or spiraling every quiet week. --- ### Reclaim Admin Space for Ideal-Fit Reach My rule is that business development time is protected before the slowdown, not negotiated during it. In my consulting practice I keep a fixed block every week for the work that creates future clients — educational content, follow-up with past prospects, staying visible in the industry — and that block does not get handed to client delivery just because a busy week shows up. When demand does slow, I do not ask whether to do development work; I ask whether the hours I already protect are aimed at the right people, because a slow month is exactly when a consultant is tempted to chase anybody instead of the right fit. The tradeoff resolves itself once you see the two jobs clearly: current clients get the attention their engagement requires, full stop — that is never the source of development time. The source is everything else: low-value administration, meetings without a decision, work that feels busy and produces nothing. Protect the pipeline in good months and a slow month becomes a timing problem, not a survival problem. --- ### Cap Delivery to Pursue Alliances When client work slows down, I block time for outreach before my week fills with delivery. When our Amazon projects dried up, I capped delivery at 70% of my calendar and used the leftover hours for partnership calls and fixing our sales process. Ended up finding some solid SaaS clients during what would've been a rough stretch. --- ### Forecast Selling Effort Against Distant Backlog A full calendar is not equal to a healthy pipeline. Allocate business development time against the future revenue gap, not today's workload. If winning new work takes 90 days, protect selling time based on what your backlog looks like 90 days out. The tie-breaker for time conflicts: Would moving this hour jeopardize a client commitment or simply reduce extra polishing? Protect the commitment. Redirect the polishing. ## Related - [Consulting Capacity Triage When Demand Surges](https://consultantmagazine.co/qa/consulting-capacity-triage-when-demand-surges.md) - [Win Better Work with a Strong Go/No-Go for Consulting Proposals](https://consultantmagazine.co/qa/win-better-work-with-a-strong-gono-go-for-consulting-proposals.md) - [Capacity Planning for Professional Services Teams](https://consultantmagazine.co/qa/capacity-planning-for-professional-services-teams.md) - [How Consultants Keep Client Projects Moving](https://consultantmagazine.co/qa/how-consultants-keep-client-projects-moving.md)