Founders ask Collective 54 this 3 times in our records, 1 of them in 2026. The productize and cross-selling answers on this site cover turning a service into a repeatable package and who sells more to existing clients; this page covers combining two or more services into a single offer.
The service offering development chapter of the 2020 book explains where the pressure comes from. Growth from existing clients is key to scale, and that requires having more to offer them over time, because clients become fatigued if you keep bringing them the same thing. Greg Alexander describes SBI starting with one offering, a method for hiring salespeople. As the firm performed, clients asked for help with territories, quotas, compensation plans and sales channels. He chose to build those services in-house rather than refer the work out for a fee. SBI eventually had more than one hundred offerings, launched about ten a year, and packaged them into a trademarked offering called the Revenue Growth Methodology. He says the firm sold for 30 percent above comparable firms, in part because of the robustness of the offering.
As an inference, a good bundle does what that packaging did: it turns a list of services into one thing a client can understand and buy, and it is harder to compare with a competitor selling one piece of it.
The service design essay says a well-designed service answers a set of questions at once: what specific problem it solves and for whom, why a buyer will prioritize and fund it now, what exactly is being sold and what is explicitly not, how value is created and measured, how it is delivered consistently without heroics, and where customization adds value and where it destroys margin. It says the offer should be defined in terms of outcomes, not activities.
As an inference, the test for a bundle is whether you can name the single result it produces. A strategy engagement plus an implementation engagement is two services. A defined change in a client result, delivered through both, is one. If the only link between the parts is that the same client might buy both, keep them separate and let your account team sell them in sequence.
The essay says that in an AI-native firm services are modular by design, assembled from repeatable components, with clear boundaries around where customization adds value and where it destroys economics. Its list of responsibilities includes identifying components that can be reused across clients and services, designing repeatable methods that can be taught and enforced, and defining rules for customization rather than allowing ad hoc variation.
As an inference, take each existing service apart into its components, such as a diagnostic, an analysis, a design, a rollout and a measurement step, and build the bundle from the ones that serve the outcome. You will usually find overlap: two diagnostics, two kickoff phases, two sets of interviews. Removing the duplication is where a bundle becomes better value for the client and better margin for you at the same time.
The essay calls for explicit scope boundaries, what is in and what is out, and for clarifying the role the client must play for the service to succeed. The proposals answer on this site describes the out list and the customization rule that give scope its edges.
As an inference, bundles need this more than single services, because the client sees a larger promise and assumes everything nearby is included. Write down what the bundle does not cover, which parts can flex and who approves a change.
The essay says services should make money by design, not by hope. It assigns choosing the value metric pricing is tied to, choosing the pricing model, modeling expected and acceptable margins, forecasting cost to serve across human, AI and tooling components, and testing sensitivity to discounting and scope creep. It says beautiful services that cannot sustain margin are design failures, not sales failures.
The pricing chapter of the 2020 book adds two rules: charge the most for the service features clients want most and the least for those they care little about, and use price versioning so clients choose their own price. As an inference, avoid pricing a bundle as the sum of the parts minus a discount. That teaches the client to value each piece separately and invites them to remove the ones they think they can do themselves. Price the outcome, and offer two or three versions of the bundle at different scopes rather than a menu of parts.
The essay says many service designs collapse at delivery, because designers assume delivery will figure it out and delivery teams inherit promises they did not help design, which produces friction, rework and margin erosion. It says delivery feasibility should be simulated before launch.
As an inference, a bundle often joins services run by different people. Decide who owns the whole engagement, how the handoff between components works and how one budget is tracked across them. The scope changes answer on this site covers keeping one person accountable for the economics of an engagement.
The essay assigns responsibility for ensuring new services reinforce rather than dilute the existing portfolio, making explicit decisions to build, adapt or retire services, modeling how services affect revenue concentration and risk, and assessing whether services increase or reduce dependence on specific individuals.
As an inference, ask whether the bundle replaces the separate services or sits beside them, whether it will pull the firm toward a narrower or wider set of clients, and whether it only works when one senior person delivers it. A bundle that depends on the founder adds revenue and key-person risk at the same time.
The pricing role essay says most pricing breakdowns happen through packaging drift rather than headline prices, and calls for clear boundaries between offers, consistency in what is included, visibility into how often packages are customized, and alerts when exceptions become norms. As an inference, once the bundle is live, track how often it is sold as designed. If most clients get a custom version, the design is wrong or the sales team is not selling it.
Collective 54 publishes no bundle template, discount for bundles, number of components or naming convention. The published positions are growth from existing clients requiring more to offer, the SBI account of building offerings in-house and packaging them into one methodology, services defined by outcomes, modular services built from repeatable components with customization rules, explicit scope and the client role, pricing designed before launch and tested against discounting and scope creep, charging most for what clients value most and versioning, delivery feasibility simulated before launch, services that reinforce the portfolio, and packaging discipline.
If clients buy the two services at different times or from different buyers, as an inference, a bundle may slow the sale, and selling them in sequence is better.
If one service is a commodity and the other is differentiated, a bundle can protect the price of the commodity part, provided the outcome is real.
And if a partner firm delivers one of the components, the vendor and subcontractor terms in your contracts need review before you sell it as one offer.
Build the bundle around one outcome the client is buying, not around two services you happen to sell. Assemble it from repeatable components of your existing services, remove the duplication, and write down what is in, what is out and where it can flex. Price the outcome rather than the parts, offer versions at different scopes, and test the price against discounting and scope creep before launch. Decide who owns the combined engagement and check delivery can run it. Make sure it strengthens your portfolio rather than adding dependence on one person, and track whether it is sold as designed.
Collective 54 publishes no bundle discount. As an inference, pricing a bundle as the sum of its parts minus a discount teaches clients to value each piece separately. The service design essay says to tie pricing to a value metric and test its sensitivity to discounting before launch.
As an inference from the service design essay, they belong together when you can name a single outcome the combination produces for a specific buyer. If the only link is that the same client might buy both, sell them in sequence instead.
The 2020 book says SBI grew to more than one hundred offerings, packaged them into a trademarked methodology, and sold for 30 percent above comparable firms, in part because of the robustness of the offering.
The service design essay warns about services that cannot sustain margin, customization without rules and delivery teams inheriting promises they did not design. The pricing role essay adds packaging drift, where exceptions quietly become the norm.
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 account of building services in-house rather than earning referral fees, more than one hundred offerings launched at about ten a year, the trademarked Revenue Growth Methodology, and the sale at 30 percent above comparable firms partly due to the robustness of the offering; chapter 15 for charging most for the features clients want most and price versioning. Greg Alexander, The AI-Native Boutique Firm (Advantage Books, January 2027), specifically The AI Service Design Manager for the questions a well-designed service answers, offers defined by outcomes, modular services assembled from repeatable components with boundaries on customization, reusable components and customization rules, explicit scope and the client role, pricing designed before launch with margin, cost to serve and sensitivity to discounting and scope creep, services that cannot sustain margin as design failures, delivery feasibility simulated before launch, and services that reinforce rather than dilute the portfolio, concentration and dependence on individuals; The AI Pricing Manager for packaging drift and packaging discipline. Related Collective 54 answers on this site: how do I productize our services into repeatable, packaged offerings; who should own cross-selling and upselling on our accounts; how do I write proposals and scope engagements so I get paid; how do I manage scope changes without letting them blow the budget; how do I set the right pricing strategy for my firm. Note on scope: Collective 54 publishes no bundle template, discount or naming convention. The single outcome test, breaking services into components and removing duplication, the warning against pricing as parts minus a discount, versions of the bundle, ownership of the combined engagement, the portfolio questions, tracking whether it sells as designed, 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.