FROM THE TEAM AT
Start a conversation

OPERATING & M&A ADVISORY

Closer to
the business. Clearer on what comes next.

We help owners and leadership teams improve reporting, grow their businesses and prepare for a sale or acquisition. We work with healthcare companies and other businesses, within the Altitude portfolio and beyond.

Explore our practices
One rising path from today’s business to the next moveNEXT MOVETODAY’S BUSINESS

Our practices

Run the business. Prepare for what’s next.

Operating advisory

Work alongside your team to improve how the business runs, through a focused project or ongoing support.

M&A advisory

Prepare for a sale, evaluate an acquisition and plan what happens after closing.

Put the owner’s objectives and the realities of running the business at the center of a transaction.

Explore M&A advisory

Flight Plans

White papers and worksheets for running, growing or selling a business.

Before the ModelA checklist for choosing an AI or analytics project your team can put to work.

An owner does not need a larger list of AI tools. The more useful starting point is a business question that takes too long to answer or a recurring piece of work that consumes too much attention.

Can the team explain where referrals disappear? Can it see capacity by location? Can management reconcile the board's revenue view to the operating team's activity? Can a workflow move forward without someone copying information between systems?

These questions create a practical way to evaluate analytics, automation and AI. They identify the answer or action the business needs before choosing the technology that might provide it.

Start with a decision someone owns

Write down the decision in a sentence. “We need better reporting” is too broad. “The operating leader needs to decide where to add capacity next month” identifies a user, an action and a time horizon.

Then identify the minimum information that could change the decision. A complete data warehouse may be a sensible longer-term investment. It is rarely the first definition of a useful result.

For the capacity question, management might need the same-period view of available slots, completed visits, cancellations, provider hours and demand by location. The first assignment is to establish which of these measures exists, whether it is trustworthy and whether the relevant people interpret it consistently.

That work has value even if the best first solution is a simpler report or a changed operating process. The technology earns its place by helping the team act.

Make the definitions inspectable

A dashboard can make inconsistent numbers more attractive without making them more reliable.

Take a measure such as conversion. Does the denominator include every inquiry, only qualified inquiries or only people contacted? Is the result a scheduled appointment, an attended appointment, a completed sale or collected cash? Which time period connects the starting event to the outcome?

The useful definition records the event, population, period, exclusions, source and owner. It also says how corrections are handled. Without that agreement, a new system can turn a familiar disagreement into an automated one.

Use a small metric dictionary for the first question. The purpose is not to document every field in the company. It is to make the measures that support the next decision unambiguous enough to use.

Trace the path from source to answer

For each important measure, trace where it starts and what happens to it before someone sees it in a meeting.

  • Which source system records the event?
  • Who can explain the field's meaning and limitations?
  • What export, transformation or manual adjustment happens?
  • Where can records be duplicated, omitted or delayed?
  • How is the final answer reconciled to the source?
  • Who will investigate when the number looks wrong?

The result is a map of the work, not merely a list of software. It often reveals that the bottleneck is an inconsistent workflow or an unclear responsibility. A technical build should account for those conditions rather than bury them in a reporting layer.

Choose the intervention after understanding the work

Several interventions can address a recurring operating problem. They ask for different kinds of evidence.

Analytics can make a defined question easier to answer. The test is whether the user can understand and use the answer, including its limitations.

Rules-based automation can move repeatable work through a known path. The test includes correct handling of exceptions, not just the happy path.

AI can help with work involving language, classification, synthesis or other variable inputs. The test needs a relevant evaluation set, a way to recognize failure and a defined human review path where the consequence warrants it.

These approaches can work together. A business might use a governed data foundation for reporting, conventional automation for routing and an AI component for summarizing an unstructured document. That does not make every part of the system an AI project.

NIST's AI Risk Management Framework offers a useful external reference for organizing AI risks across governance, context, measurement and management. It should be adapted to the actual use case; citing a framework does not prove that a deployed system meets it.

NIST AI Risk Management Framework.

Define the exception before expanding the workflow

Imagine an illustrative intake process that reads a document and suggests a category. The first demonstration correctly handles the examples the team expected.

The next questions matter more. What happens when the document is incomplete? When two categories are plausible? When the format changes? When a person corrects the suggestion? When a source system is unavailable?

Write down who reviews uncertain cases, how a correction reaches the process owner and which decisions the tool is allowed to influence. Then evaluate a sample that represents the actual range of work. The point is to learn whether the system is dependable in its intended role, rather than prove that it can produce an impressive example.

This is an illustrative workflow, not an Altitude client result.

A first-assignment scorecard

Use these questions before approving a larger build:

| Question | A usable answer |

| --- | --- |

| What decision or task changes? | A named user, action and decision horizon |

| What is the baseline? | A checked view of the current time, error, throughput or other relevant measure |

| Where does the evidence come from? | Named sources, definitions and reconciliation steps |

| What can fail? | Known exceptions and the way they reach a responsible person |

| What will the team own? | Access, documentation, maintenance responsibilities and handover |

| How will we decide whether to continue? | An agreed review point and evidence of usefulness |

Do not treat the scorecard as a universal maturity score. A low-risk internal summary and a workflow affecting a consequential decision do not need identical controls. The scope should reflect the actual use and consequences.

Measure usefulness without confusing it with savings

If an assignment reduces report assembly time, measure the change against a consistent baseline. Record which tasks stopped, which tasks remained and whether review work increased elsewhere.

Time made available is not automatically cash saved. It may create capacity for better analysis, faster follow-through or work the team could not previously complete. A reduction in spending requires separate evidence that a cost was actually removed.

The same distinction applies to revenue. A better answer may support a better decision. It does not, on its own, establish that the technology caused a financial result. Keep the chain of evidence visible.

The next useful question

Before asking which model the business should use, ask: Which operating question should our team be able to answer reliably, and what would change if it could?

That is a practical first conversation for AI and analytics. Bring the question, the current reports and the person responsible for acting on the answer.

Explore AI and analytics.

A tool to take into the meeting

A metric definition card (CSV) is an illustrative blank template. Add your own definitions and evidence locally. It contains no client data and sends nothing to Altitude.

The Owner’s Reporting PackWhat belongs in a monthly pack that connects results, cash and decisions.

A management pack can be accurate, detailed and delivered on time while leaving the most important question unanswered: What should we do differently?

The problem is often a gap between financial results and operating responsibility. One page explains revenue, another shows activity, another forecasts cash. The people in the room have to reconstruct the connections before they can make a decision.

A useful pack reduces that translation work. It gives management a shared view of what happened, why it happened, what may happen next and who owns the response.

Begin with the meeting, not the template

Before redesigning the pack, list the decisions the meeting is supposed to support.

An operating review may need to decide where to add capacity or which referral pathway needs attention. A finance review may need to decide whether to change a hiring assumption or the timing of a commitment. A board may need to understand a change in the forecast and the choices management is making in response.

Those decisions have different information needs. A standard template can help organize them, but it should not decide them.

Ask each regular participant which part of the existing pack changes a decision. Ask which important question still needs a separate spreadsheet or a follow-up email. The answers identify what deserves space in the next version.

Build a connected sequence

One practical reporting structure moves through five questions.

1. What changed?

Show a small set of financial and operating measures against the relevant comparison. State the period and whether the numbers are final, preliminary or revised.

Avoid using a favorable comparison simply because it is available. A month affected by a timing difference may need an additional view before management can interpret it. Explain the reason rather than allow the page to imply a trend it does not establish.

2. Why did it change?

Connect the variance to drivers the team understands: volume, mix, price, staffing, capacity, timing or another relevant factor.

Distinguish an observed explanation from a hypothesis. If the team believes a referral change caused a revenue movement but has not checked the path, label it as something to test. The pack should make the uncertainty visible enough to resolve.

3. What is likely to happen next?

Connect the forecast to explicit assumptions. Who owns each material assumption? What evidence would change it? When will it be reviewed?

A forecast does not become more useful simply by extending the spreadsheet further into the future. Its usefulness depends on whether management can see how the assumptions connect to the business and to the decisions it controls.

4. What does it mean for cash?

Show the timing of receipts, payments and commitments in a form appropriate to the business. Separate an accounting result from the timing of cash and explain important differences.

A scenario should identify what changed, rather than present several unlabeled versions of the same workbook. Management needs to know which assumption drives the difference and which action it can take.

5. What happens now?

Close the loop with a decision or an explicit reason to wait. Record the owner, next action, expected review date and evidence needed.

The action log should return at the next review. Otherwise, the pack becomes a history of discussions rather than a means of managing the business.

Give every important measure a definition

Financial and operating teams can use the same word for different things. Revenue may mean booked, billed or collected. A new customer may be counted at an inquiry, a contract or the first completed service.

A compact metric dictionary makes these differences inspectable. For each core measure, record:

  • The event or balance being measured.
  • The population and exclusions.
  • The time period and comparison.
  • The source and reconciliation method.
  • The person responsible for quality and explanation.
  • The way corrections or restatements are communicated.

Use the dictionary to resolve the first meaningful disagreements. Do not postpone a useful pack until the company has documented every possible metric.

Separate assembly from judgment

Map the work required to create the current pack. Which steps collect data? Which reconcile it? Which interpret it? Which merely reformat something already available?

Reducing repetitive assembly can make room for better review. It does not remove the need for a responsible person to understand the numbers. A pack that updates automatically still needs checks for source changes, incomplete periods and unusual events.

The handover should explain how the pack is produced, which parts require judgment and what to do when a reconciliation fails. That is part of making reporting dependable rather than dependent on one person.

An illustrative decision page

Consider a company where demand is increasing but completed work is flat. A financial page alone shows the result. An activity page alone shows the demand. A connected decision page might show the path between them.

It would align inquiries, scheduled work, completed work and available capacity over a consistent period. It would state which parts of the comparison are incomplete. The operating owner would explain the likely constraint and propose the next check or intervention.

The useful outcome is not an attractive chart. It is a decision about where to investigate or act, with someone accountable for returning with evidence.

This example is illustrative. It is not a claim about an Altitude engagement or a measured client outcome.

A pack review checklist

| Test | Question to ask |

| --- | --- |

| Decision | What decision does this page help someone make? |

| Definition | Could two readers calculate the measure the same way? |

| Reconciliation | Can the result be traced to its source? |

| Explanation | Is the driver observed, inferred or still unknown? |

| Ownership | Who can explain the result and act on it? |

| Follow-through | What will return at the next meeting? |

If a page cannot pass the decision test, shorten it, move it to supporting detail or remove it. If a decision lacks a usable page, design the information around that need.

Make scrutiny easier

Consistent definitions, supporting schedules and a record of changes also help the business respond to outside questions. They can make the information easier to understand when lenders, buyers or advisers ask for support.

Preparation is different from an independent audit, review or quality-of-earnings opinion. Define the role of management and each adviser clearly. A reporting project should not imply assurance it does not provide.

A practical first assignment

Start with one reporting cycle. Review the existing pack, identify the unanswered decisions and agree a first version of the metric dictionary. Give the reporting calendar an assembly owner, a review owner and a clear action rhythm.

The pack earns its place when it helps the people in the room understand the same business and decide what happens next.

Explore financial reporting.

A tool to take into the meeting

A reporting decision log (CSV) is an illustrative blank template. Add your own definitions and evidence locally. It contains no client data and sends nothing to Altitude.

Find the Growth ConstraintHow to tell whether demand, conversion or capacity is holding growth back.

When growth slows, adding demand is an understandable response. More outreach, more referral activity or a larger campaign can make the top of the funnel look healthier.

The business still has to turn that activity into completed, economically useful work. If the constraint sits elsewhere, more demand can create a larger queue rather than a better result.

A useful growth conversation follows the path from source to outcome and asks where the next unit of attention would make a difference.

Draw the actual pathway

Choose one important source of demand. Map the steps an opportunity passes through before the business recognizes a useful outcome.

In a healthcare example, the path might include referral received, patient contacted, appointment scheduled, visit completed and payment collected. In another business, the equivalent steps may be inquiry, qualification, proposal, contract and delivery.

The map must match the operation. Do not impose a generic funnel stage that no person or system actually owns.

For each step, identify the recording system, responsible team, expected next action and reason an opportunity might stop. Note the time between stages. A conversion rate without a time definition can mix a new cohort still progressing through the funnel with an older cohort that has already reached an outcome.

Separate four different problems

Demand

Is there enough relevant demand from sources the business can serve? Which sources produce opportunities that fit the offering, location, payer or customer mix?

Activity measures can help explain the work, but they are not the result. A count of calls or visits does not establish that qualified demand increased.

Conversion

Does the team consistently move an appropriate opportunity to the next stage? Can it explain why opportunities are lost, delayed or declined?

A gap may come from a process, a system, an access problem or an unclear responsibility. It should not automatically be attributed to individual performance without checking the conditions.

Capacity

Can the business deliver the work it is trying to win? The relevant constraint may be staffing, scheduling, geography, equipment, provider availability or another operating condition.

The capacity view should match the period and service mix of the demand view. Aggregate availability can hide a specific shortage where the demand actually exists.

Economics

Does growth improve the business after accounting for what it takes to deliver? More revenue, more completed work and more cash contribution are related but distinct measures.

The first analysis does not need to answer every economic question perfectly. It should identify which assumptions are known, which are estimated and which could change the growth decision.

Check the definitions before comparing performance

Two locations may appear to have different conversion rates because they use different stage definitions. One records a referral when a message arrives; another records it only after a person has checked eligibility.

Reconcile the definitions before ranking locations or assigning causes. Align the starting population, time window, exclusions and outcome. Preserve genuine differences in service mix or operating conditions rather than flattening them into one number.

The goal is a comparison that helps the team choose an action. A precise-looking percentage can be less useful than a smaller, well-understood sample.

An illustrative first experiment

Imagine a referral pathway with inconsistent follow-up. The hypothesis is that some appropriate referrals fail to reach scheduling because responsibility for the next contact is unclear.

The first experiment could define one owner for the handoff, establish an agreed follow-up window and record a small set of standardized stop reasons. The team would review the same pathway over a defined period and check both conversion and the work required to achieve it.

Before starting, record what would support the hypothesis, what would weaken it and what other conditions might influence the result. If capacity changes at the same time, preserve that context. A before-and-after comparison alone may not isolate the intervention's effect.

This is an illustrative operating experiment. It is not a measured client case or a claim of a particular revenue increase.

Make referral development part of the operating system

A referral development plan should connect relationship activity to the pathway the operation can serve.

The field team needs clear priorities and a way to understand what happens after a referral arrives. The operating team needs visibility into demand, expectations and the capacity implications. Both need a common review rhythm.

A useful review can ask: Which relationships are sending appropriate opportunities? Where is the path slowing? What feedback should return to the source? Which operational issue needs attention before the next growth push?

That creates a connection between market-facing activity and delivery, rather than treating each as a separate report.

Choose the expansion question carefully

Once the current pathway is understood, the business can compare different ways to grow. Organic improvement, a new location and a tuck-in acquisition ask for different resources and create different operating demands.

Compare them against a shared set of assumptions: customer need, capacity, staffing, time to readiness, management attention, information quality and economic contribution. Record which assumptions can be checked before committing further.

An expansion model should reveal the important tradeoffs. It should not conceal an operating uncertainty behind a single forecast.

A constraint review for the next meeting

  • Which specific growth outcome are we trying to improve?
  • What is the source-to-outcome pathway?
  • Where is the strongest evidence of a constraint?
  • Which definitions or missing records could change that conclusion?
  • What is the smallest useful intervention we can evaluate?
  • Who owns the action, the measurement and the review?
  • What could get worse elsewhere if the intervention works?

The last question matters. Removing a conversion constraint can create a capacity constraint. More demand in one service can change mix elsewhere. Growth work should keep the whole business in view.

The next move

Before increasing activity, choose one pathway and understand where its opportunity goes. The resulting map can make the next growth decision more specific, whether the answer is more demand, a better handoff, more capacity or a different expansion choice.

Explore growth.

A tool to take into the meeting

A growth constraint worksheet (CSV) is an illustrative blank template. Add your own definitions and evidence locally. It contains no client data and sends nothing to Altitude.

Before the TransactionA practical checklist for diligence preparation and the first month after close.

A potential transaction creates work before a formal process begins. Information has to be explained, responsibilities have to be assigned and the business has to keep operating while management answers a different set of questions.

Readiness starts with the owner's objective. It is a way to identify the work that would make a future decision more credible and manageable, without assuming a transaction should happen now.

Define the intended outcome

An owner considering a sale may be balancing liquidity, continued involvement, the team's future and the time required for a process. A buyer may be testing whether an acquisition fits its operating model and management capacity.

These objectives shape the preparation. A generic data request list cannot settle them.

Write down the decision horizon, the outcomes that matter and the tradeoffs still unresolved. Identify who must participate in the decision and who has authority to make it. Revisit that view as the situation changes.

Make the business understandable

A credible explanation connects financial results to the way the business operates. Management should be able to describe what drives revenue, what creates cost, how cash moves and which conditions make the results more or less repeatable.

The practical work may include consistent reporting definitions, supporting schedules, reconciliations and a clear record of changes. It may also include an operating view of customer or referral concentration, capacity, staffing and service mix.

Do not treat a polished presentation as a substitute for support. The explanation should survive a reasonable question about where the number came from and what it includes.

Separate information gaps from operating issues

Some readiness problems are primarily informational. A supporting schedule may exist but require reconciliation. A definition may need to be documented. A report may need to be produced consistently.

Other issues require operating work. The business may depend on one person, have an unresolved capacity constraint or lack a reliable management rhythm.

Give these issues different owners and workplans. More presentation work will not resolve a substantive operating dependency. Conversely, a documentation gap does not necessarily establish that the underlying business is performing poorly.

Protect management's attention

A transaction process can create a second operating calendar. Requests, analysis, discussions and decisions arrive alongside the work of running the company.

Map the responsibilities before the calendar fills. Who assembles information? Who checks it? Who speaks to the operating explanation? Who decides whether a request changes scope or timing?

Maintain a record of what has been provided and which version is current. Escalate questions to the person who can answer them. That discipline helps preserve consistency without assuming every question belongs in the chief executive's inbox.

Bring the transition into view early

A close is a milestone. The business still needs to operate the next day.

The relevant transition questions depend on the situation. They may concern leadership responsibilities, reporting, systems, customer relationships, decision rights or the integration of an acquired business.

Identify which questions must be settled before close and which can be worked through afterward. Assign a responsible person to each. Preserve the assumptions that informed the transaction decision so the operating team can recognize when reality differs.

A practical readiness map

| Area | First question | Useful output |

| --- | --- | --- |

| Owner objective | What outcome is being considered, and why? | A decision and tradeoff summary |

| Financial information | Can management explain and support the results? | A reporting and reconciliation workplan |

| Operating evidence | What makes the performance repeatable? | A driver and dependency map |

| Management capacity | Who can run the process while the business runs? | A responsibility and review calendar |

| Transition | What must work immediately after the ownership change? | A prioritized transition agenda |

Use the map to sequence work. Avoid turning it into a score that suggests a company is ready merely because every box has been marked.

Define the advisers' roles

Transaction preparation can involve management, an M&A adviser, legal counsel, accountants and other specialists. Clear role definitions reduce the risk of confusing coordination or preparation support with an independent assurance opinion or legal advice.

The first assignment should specify what the team is doing, who relies on the work and which questions belong with another adviser. The transaction mandate and terms need to fit the actual situation.

This brief does not recommend a sale, acquisition, valuation or financing decision. It provides a preparation framework for the conversation.

The next move

Choose one intended outcome and work backward. Identify the information, operating work and management responsibilities that would improve the quality of the decision.

Preparing early can be useful even if the owner ultimately decides to keep building the business.

Explore M&A advisory.

A tool to take into the meeting

A readiness register (CSV) is an illustrative blank template. Add your own definitions and evidence locally. It contains no client data and sends nothing to Altitude.

Watch & listen

NASHVILLE ENTREPRENEUR CENTER · 2025

Stuart McWhorter on Circle Back

Listen to the interview ↗

TENNESSEE HEALTH CARE HALL OF FAME · 2015

Clayton McWhorter’s Hall of Fame remarks

Watch the remarks ↗

What needs to
move forward?

A business decision. A reporting problem. A possible transaction.

Start a conversation