Advisory Services / Customer-Specific Work at Scale
I used to think all custom work was a sign that something had gone wrong. I no longer believe that. Custom work can be strategic. What matters is how much of your capacity it uses and whether you measure it. Most companies do not, because implementation work sits in queues that never reach the roadmap.
The direct answer
Customer-specific work scales inside a product organization when it is measured as a share of product capacity, classified separately from core roadmap work, approved by a named owner before the promise is made and rebalanced each planning cycle.
There is no universal target ratio. What matters is knowing your own and being able to explain it.
Interactive example
A fictional quarter with 40 engineer-weeks of product capacity. Move the slider to change the custom share and see which core work leaves the quarter.
Condition: a bespoke ledger integration delivered this quarter. Six engineer-weeks to build.
After the build year come three years of upgrades and support, and a customer who now has a say in your release schedule. Roughly $35k a year. No one has been named to maintain it.
Fictional quarter and deal. There is no universal target. What matters is knowing your own ratio and having a named person approve each exception before a promise is made.
When to address it
Implementations, migrations and expedited features arrive through different queues, so the full demand never reaches the roadmap.
Each commitment looks worthwhile alone, while the accumulated work crowds out reliability and broadly valuable features.
The deliverable ships, then its support and upgrade costs disappear from the business case.
The working model
It starts by classifying the work that actually happens across product, engineering, implementation and support queues. There is no universal target. The aim is a ratio the company measures and can explain.
Core and custom effort gets tagged the same way everywhere, including implementation work done by product development teams.
Leadership agrees on a target mix and a buffer for real customer obligations, and records which core work cannot be displaced in the period.
Each request is compared on immediate revenue, reusable value, maintenance cost, capacity and the longer-term product goal it supports or delays.
The actual mix is measured every cycle, variances are explained and the company moves toward its target in steps the business can absorb.
Illustrative example
The ask. A strategic account offers a $420k renewal if a ledger integration ships this quarter. Six engineer-weeks, with the scope set by one customer.
Classify and price. It is classified as Custom for this decision. The build plus three years of upgrades and support is priced next to the two core items it would push out.
Decide in the open. Sales, product, success and finance review it together. The CEO approves the exception, with a named service owner and a plan to generalize the connector.
Measure. The actual mix is checked against the target. The connector either becomes a core capability for two more customers, or the team records why it should not be repeated.
A composite of common situations. Names and figures are illustrative.
What you leave with
For the full reasoning, the examples and the quarter-by-quarter rebalancing method, read How to Own Your Roadmap. This page is about applying it inside your company.
The more services-heavy the company, the more its product work leans toward custom. The bigger problem is usually not knowing the ratio at all.
Common starting points
How an engagement starts
Where custom work comes from today, which queues it hides in and the deal that is on your mind.
A Two-Day Intensive ($2,500) tags a representative slice of backlog and queues. A Sprint Advisory ($6,500) builds the full baseline and a commitment policy.
As a Fractional CPO ($8,000 a month) I run the exception reviews and quarterly rebalancing until your team owns them.
Two-Day Intensive and Sprint Advisory fees are credited toward the first month of Fractional CPO. Onsite in the New York City area, remote everywhere else. See pricing. Specialists join only when the work needs them: meet the bench.
Common questions
No. Custom work can open an account or a market that matters strategically. The question is whether the company sees and chooses the full tradeoff.
Work whose scope or timeline is driven by one customer or a minority stakeholder rather than by healthy product practice. Implementation done by product engineers counts, even when nobody books it that way.
There is no universal target. Most B2B and B2B2C companies I have worked with, between $5m and $500m in revenue, sit between 40:60 and 70:30 core to custom, and services-heavy companies lean further toward custom. Start with your actual mix, pick a target that fits the business model and move toward it in steps.
Treat them as a deliberate capacity choice. They can sit outside product development or inside a measured Custom allocation. Either way, define how customer learning informs the product roadmap.
Often the answer is yes, with the cost made visible: what it displaces, who maintains it and whether it becomes reusable product. When the answer is no, that same information makes it easier for sales to explain to the customer.
Start with a real deal
Or bring the implementation queue no one measures. In 45 minutes we can sketch your current mix and a realistic target.
Book a discovery call