Founders ask Collective 54 this 2 times in our records, none of them in 2026. The new service line, drop service lines and niche answers on this site cover launching, retiring and focusing; this page covers the request in front of you: a client asking for something next to what you do.
The service offering chapter of the 2020 book makes the case for saying yes. Existing client revenue growth is key to scale, and that requires having more to offer clients over time; if you keep bringing them the same thing, they become fatigued. The chapter tells the SBI story. The firm launched in 2006 with one offering, a method for interviewing and hiring salespeople. As it performed, clients asked for more: designing sales territories, setting quotas, building compensation plans, optimizing sales channels. The author had two choices: refer the business to partners for a quick referral fee, or develop the capability in-house, costly in the short term and lucrative in the long term. He chose to build. When he left, the firm had more than one hundred offerings, launched about ten a year, packaged them into a trademarked methodology, and sold for about 30 percent above comparable firms, in part because of the robustness of the offering. He writes that without new offerings he would be running a little lifestyle business.
The service design essay in the newer book describes the other side. Brilliant service designers say yes too often, out of curiosity, client pressure or intellectual enthusiasm. Firms add customization to save deals and pay for it later in margin. They expand offerings to satisfy loud clients and then struggle to support the complexity. Over time, the portfolio drifts, becoming less intentional, harder to manage and more founder-dependent. As an inference, both stories are true, and the difference between them is whether each yes was a decision or a reflex.
As an inference from the chapter, every service SBI added served the same buyer, the head of sales, with problems that buyer already owned. The firm did not wander into new buyers or new industries. It went deeper with one buyer. That is the most useful definition of adjacent: the same person, a neighboring problem. Work that needs a different buyer, a different delivery team or a different kind of engagement is not adjacent, however close the subject sounds.
The service design essay calls this category strategic focus and says to decide what not to design with the same discipline used to decide what to build. It evaluates every potential service against five constraints. As an inference, each becomes a question you can ask about a client request:
Ideal client fit. Is this for the buyer you serve best, or would it pull you toward a different buyer?
Portfolio coherence. Does it reinforce what you already sell, so that each service makes the others easier to sell, or does it dilute the story?
Revenue concentration. Does it deepen your dependence on one large client, or could it be sold to many?
Founder dependency. Can someone other than you deliver it, or would it put you back on every engagement?
Scalability. Could it become a repeatable service, or will it always be custom?
As an inference, a request that passes all five is a candidate for a new service. One that fails two or more is usually a distraction, however attractive the fee.
The service design essay says services should make money by design, not by hope, and that beautiful services that cannot sustain margin are design failures, not sales failures. It asks for pricing and margin to be modeled before commitment, cost to serve forecast across people, AI and tools, and sensitivity tested against discounting and scope creep. It also warns that delivery teams often inherit promises they did not help design, and that services which cannot be delivered without heroics are not finished designs.
As an inference, before saying yes to adjacent work, ask who on your team would deliver it, whether they have done it before, and what margin you expect. If the honest answers are the founder, no and unknown, you are not adding a service; you are adding a favor.
The engagement chapter of the 2020 book describes two kinds of firm: those built around a small number of clients each spending a lot, and those built around many clients each spending a little. It says boutiques that offer both have a high failure rate, because matching revenue and expenses across both is very hard, and advises picking one. As an inference, adjacent work that changes your engagement type, such as a long implementation firm adding small one-off projects, or the reverse, deserves extra caution even when the subject matter fits.
The SBI story shows that the choice is not only yes or no. As an inference, there are three answers to a request for adjacent work.
Build it, when it passes the focus tests, the economics work and you expect to be asked again. Start with a pilot at a real price and compare the result to the model, as the new service line answer on this site describes.
Refer it, when the client need is real but the work fails the tests. A trusted partner keeps the client well served and keeps your team focused. The referral answers on this site cover how to make those relationships work in both directions.
Decline it, when the work is a poor fit and no partner would serve the client well. Saying no clearly protects the relationship more than doing the work badly.
The chapter recommends direct primary research to find what clients need: an advisory board of current and former clients, post-project reviews, satisfaction surveys, win-loss interviews and the conferences your clients attend. It says the losses often reveal holes in the offering. The service design essay adds market truth: how often a problem appears, whether it is urgent or merely interesting, and whether there are real signals of willingness to pay.
As an inference, a request from one client is an anecdote. The same request from several clients, or a gap that keeps showing up in lost deals, is a signal worth building for. Keep a simple log of requests you turn away and review it every quarter.
The service design essay says services should be treated as assets with life cycles, with explicit decisions to build, adapt or retire them, and that what works in a 3 million dollar firm breaks at 15 million. As an inference, the signs that adjacent work has turned into drift are a service list nobody can explain in a sentence, sellers unsure what to lead with, and engagements that only the founder can scope. When you see them, the drop service lines answer on this site applies.
Collective 54 publishes no rule for how many services a firm should offer and no threshold for when a request becomes a service. The published positions are expanding offerings to grow existing clients, the SBI choice to build rather than refer, the 30 percent premium for a robust offering, client research as the source of new services, saying yes too often as a common failure, the five strategic focus constraints, modeling economics before commitment, delivery feasibility, services as assets with life cycles, and choosing one engagement type.
If the firm is young and still finding its footing, as an inference, some adjacent work keeps cash flowing while you learn what clients value; just know which work you are doing for cash and which you are building on.
If one large client is asking, the work may be worth doing as a one-off, but price it as custom and do not call it a service.
And if you are preparing to sell, coherence matters more than breadth, because buyers pay for a transferable engine, not a collection of favors.
Take adjacent work when it serves the same buyer with a neighboring problem, passes the five focus tests in the service design essay, makes money by design and can be delivered by someone other than you. The 2020 book shows the upside: SBI built the services its clients asked for and sold for about 30 percent above its peers. The essay shows the risk: firms that say yes too often bloat their portfolio and erode margin. Build, refer or decline each request deliberately, pilot before you commit, and build for patterns across clients rather than for a single loud request.
As an inference from the 2020 book and the service design essay, say yes when the work serves the same buyer, reinforces your existing services and can be delivered profitably without the founder. Otherwise refer it or decline it.
The service design essay tests every potential service against ideal client fit, portfolio coherence, revenue concentration, founder dependency and scalability.
The 2020 book tells how SBI chose to build rather than take referral fees, and grew to more than one hundred offerings. As an inference, build when you expect repeat demand and the economics work, and refer when they do not.
The service design essay warns that service designers say yes too often and portfolios bloat. Treat services as assets with life cycles and decide explicitly to build, adapt or retire each one.
Sources: Greg Alexander, The Boutique: How to Start, Scale, and Sell a Professional Services Firm (Advantage, 2020), chapter 19 for existing client growth requiring more to offer, client fatigue, the SBI story of one offering growing to more than one hundred, the choice to build rather than refer for a fee, about ten launches a year, the trademarked methodology, the price about 30 percent above comparable firms, and direct primary research through advisory boards, post-project reviews, satisfaction surveys, win-loss programs and client conferences; chapter 7 for the two engagement types and the high failure rate of firms that offer both. Greg Alexander, The AI-Native Boutique Firm (Advantage Books, January 2027), specifically The AI Service Design Manager for service designers saying yes too often, customization added to save deals, offerings expanded for loud clients, portfolio drift, strategic focus and its five constraints, services as assets with life cycles, market truth, services making money by design, modeling economics before commitment, delivery feasibility and finished designs, and services that work at 3 million dollars breaking at 15 million. Related Collective 54 answers on this site: how do I go to market with a new service line; how do I decide which service lines to drop or phase out as we reposition; should we niche down further or broaden our focus; how do I bundle or pair complementary services into one offering; how do I build a system to generate more referrals. Note on scope: Collective 54 publishes no service count or threshold. Defining adjacent as the same buyer with a neighboring problem, the five questions, the build, refer or decline choice, the request log, the signs of drift, and the flips are inferences used here to organize the source material rather than published Collective 54 positions.
Collective 54 is the private community for founders and executives of boutique professional services firms between $5M and $50M in revenue. Members work these answers against their own numbers.