SECTOR EXPERTISE
Four sectors where we already know which questions matter.
Sector knowledge is not a service and it is not an audience. It is what shortens the distance between a first look and a decision, because the questions that decide value in a sector are usually known before anyone opens the data room. This page states what we know in each of four sectors and what it changes in a mandate.
WHY THIS SITS HERE
Sectors substantiate a mandate, they do not replace one.
A buyer does not purchase sector coverage. They purchase a buy-side, sell-side, or financing mandate, and sector knowledge is what makes that mandate faster and better argued. That is why this page sits under M&A Advisory rather than beside it.
What follows is not a transaction tombstone grid. Each section states what we understand about how the sector works, which transaction patterns recur, and the operating or technology questions that decide what an asset is worth.
SOFTWARE AND TECH-ENABLED
Where the revenue renews, and where it only appears to.
The value of a software or tech-enabled business sits in whether the revenue renews, what it costs to keep it renewing, and whether the product can carry the growth the model assumes without a rebuild nobody priced. Reported ARR and durable ARR are frequently different numbers, and the gap between them is where most of the diligence argument happens.
In compliance-heavy software the same questions carry a regulatory weight. Access boundaries, audit logging, and the evidence a customer or auditor will ask for are either an operating fact or a policy document, and a buyer's diligence team can tell the difference in a morning.
Recurring revenue and retention
Gross and net retention by cohort, what is contracted against what renews by habit, and how much of the reported recurring revenue would survive a contract review.
Product and engineering capacity
Whether the roadmap in the investment case can be built by the team that exists, and how many critical services depend on a single engineer who can deploy them.
Architecture and scalability
Whether the system supports the customer growth the plan assumes, and what the capital expenditure looks like if it does not.
Data and AI readiness
Whether the data is governed well enough to support the analytics and AI claims in the thesis, and what a control plane over regulated data would cost to build.
Security and compliance posture
The control set, the access model, the audit trail, and whether evidence is collected continuously or assembled the week before an auditor arrives.
Concentration and pricing power
Where the revenue sits by customer and by channel, and whether price increases have held or been discounted back at renewal.
HEALTHCARE AND MED-TECH
Regulatory exposure priced, not assumed away.
In healthcare the operating model and the regulatory model are the same model. Reimbursement decides the revenue, payer and referral concentration decide the risk in it, and the handling of patient data decides an exposure that shows up as remediation cost, indemnity, or a buyer walking.
The questions are answerable before close where the target can produce evidence. Where it cannot, that is itself the finding, and it belongs in the price rather than in a footnote.
Reimbursement and payer mix
Where the revenue comes from, what has changed in the reimbursement environment, and how much of the margin depends on a rate that is set by someone else.
Referral and customer concentration
The concentration behind the volume, the contractual basis for it, and what the model does if the largest source changes.
Regulatory exposure
Licensure, billing compliance, and the open items a buyer inherits, sized rather than listed.
Data and security posture
How protected health information is handled, who can reach it, whether access is logged, and whether the vendors touching it are inventoried and under current agreements.
Operating complexity
Staffing, scheduling, and throughput in a business where labor availability frequently caps growth before demand does.
AI on regulated data
Where models touch regulated data or consequential decisions, what governs them, and whether the record exists to show a regulator or an acquirer what the model saw.
INDUSTRIAL
The floor holds the answer, not the boardroom deck.
On an industrial target the operating reality is visible on the plant floor and rarely visible in the management presentation. Schedule attainment, maintenance practice, and whether the floor can see its own performance decide whether a margin-improvement thesis is a plan or a hope.
Safety sits above the rest of the read rather than beside it. A material safety or environmental finding can override an otherwise favorable operational view, which is why it is screened on every industrial engagement even when no concern is expected.
Asset intensity and capital plan
Asset condition, process capability, and the capital expenditure the plan requires against the capital expenditure the seller has been deferring.
Maintenance and asset reliability
Downtime and maintenance practice read against the schedule the plant is trying to hold, and where a reactive regime is quietly taxing throughput.
Operational data and visibility
Whether production attainment, downtime, scrap, and quality data exist and are retained, or whether the margin thesis depends on visibility the systems cannot produce as they stand.
OT and ICS exposure
Plant-floor network segmentation, machine connectivity, and control-system posture, where a flat network turns a single incident into a floor-wide stoppage.
Safety and environmental
A cross-cutting screen covering visible unsafe activity, machine guarding, and lockout practice, with permits, incident history, and remediation exposure routed to specialist confirmatory work rather than assumed away.
Supply chain and working capital
Inventory discipline, critical-spares exposure, and the working-capital effects that appear on the floor before they appear in the model.
BUSINESS SERVICES
Whether the work is repeatable, or whether it is the founder.
Business services assets are priced on whether the delivery can be repeated by people other than the ones who built it. Where the process lives in a system, the business scales with demand. Where it lives in a handful of long-tenured staff, growth is capped by hiring and the multiple reflects it.
Add-on strategies in this sector fail on integration more often than on sourcing, so how cleanly an acquisition folds into the platform is a pricing question rather than a post-close one.
Customer concentration and contract quality
How the revenue is distributed, what the contracts commit to, and how much of the base is on a rolling arrangement that renews by inertia.
Labor and process scalability
Whether delivery depends on documented process or on individual experience, and what the hiring plan implies about margin at the next revenue level.
Commercial repeatability
Whether new business comes from a repeatable motion or from relationships that leave with the person holding them.
Add-on integration
What it takes to move an acquisition onto the platform's systems and pricing, and what the integration costs before it contributes.
Pricing and margin discipline
Whether price has held through the last two renewal cycles, and where scope has been absorbed without a rate change.
Systems behind the service
Whether the operating systems support the reporting a sponsor will expect at the first board meeting, or whether that is the first hold-period project.
WHERE THE PATTERN COMES FROM
Operating history, not a positioning exercise.
Sujit Maharana ran engineering, security, and compliance for a PE-backed education-data company, a category where the data is regulated, the customers are institutions, and the audit is never optional. Student records sit under FERPA the way patient data sits under HIPAA. The statute differs and the discipline does not.
That seat included taking the organization through SOC 2 Type II org-wide, carrying the CISO scope alongside the engineering roadmap, and integrating acquisitions without breaking the compliance posture customers depended on. Current work in healthcare runs under NDA, so we describe the discipline here rather than the deals.
Nothing on this page is a composite or a projection. The record above is the operating history the technology side of these sector reads is built on, and the engagements under NDA stay that way.
TECHNOLOGY & AI
Where the sector question is a technology question.
Several of the value questions above are read by the Technology & AI practice rather than by the deal team: architecture and scalability, data and AI readiness, security and compliance posture, and operational technology exposure on an industrial floor.
That work is separately scoped with its own engagement letter. An M&A mandate does not require it, and it is brought in where the answer changes price, downside protection, or the value-creation plan.
HONEST ANSWERS
What sector coverage does and does not mean.
- Do you only work in these four sectors?
- No. These are the four where we start with pattern recognition rather than building it during the mandate. Outside them we say so at the first call, and we say what that costs in time. A mandate in an unfamiliar sector is slower and it is not automatically a mandate we decline.
- How is this different from an operations consultant's benchmarking deck?
- A benchmarking deck tells you how the target compares. It rarely tells you what the gap does to the offer. We read the operating reality, size what it does to earnings, and translate every finding into purchase price, escrow, a hundred-day priority, or a walk-away.
- On an industrial target, do you need to stop the line to assess it?
- No. The floor observation is non-intrusive: walkthroughs, segmentation checks, machine connectivity review, and passive asset discovery. We do not perform active probing of live control systems or safety-instrumented systems.
- How does safety factor into an industrial read?
- It sits above the scored dimensions as a gate rather than beside them. A material finding can override an otherwise favorable read. We screen it on the floor and route environmental, workers' compensation, and remediation matters to specialist confirmatory workstreams, named explicitly rather than assumed away.
- Can you cover a multi-plant footprint before close?
- We scope the priority plant for the on-site assessment and screen the remaining sites through operating data and management interviews, with full validation sequenced after close. Footprint-consolidation synergies stay out of the base case until the remaining plants are validated.
- Who does the technology and compliance parts of a sector read?
- The Technology & AI practice, under its own engagement letter. It is scoped when the questions arise and no M&A mandate requires it.
Send a mandate
Tell us the sector and the situation.
A few lines about the business and the transaction is enough. We will tell you what we already know about the sector, what we would have to learn, and what that means for the timeline.
Bass reads every brief. If the sector is one where we would be learning on your deal, we will say so.