Davello & Co.

Why a growing business loses margin to operating rules it no longer maintains.

the signals

The signals are visible.
The pattern is not owned.

Margin bridges keep changing the driver mix. Working capital protects service. Cash clears slower. Headcount grows where exceptions are handled.

Each recent margin reconstruction names a different mix of drivers: freight leakage one quarter, expedite cost the next, then substitute cost, credit memo clusters, rebate accruals that did not realize, and service labor that never sat in the original price. Each piece is real. Each explanation holds on its own. None of them aggregates into a single owned explanation.

Working capital is heavier than revenue growth explains cleanly. Some of it protects customer dates. Some protects against supplier lead times nobody fully trusts. Some sits in slow-moving stock tied to account treatments, project commitments, or branch-level judgment nobody wants to unwind without risking service. DSO has drifted by enough days to matter as disputed lines, credit memos, and invoice exceptions take longer to clear. Headcount has climbed in customer service, planning, pricing support, and accounting cleanup faster than throughput.

Revenue is rising. Customers are reordering. The board sees a company still moving.

The standard responses are already in motion. A new commercial leader is in place. A system project is underway. A pricing council is meeting. A commercial operations team is routing exceptions. Each one makes real local change. The same pattern returns.

Mid-market industrial businesses with real commercial complexity (distributors, regulated suppliers, manufactured-to-order shops, project-attached service operations) reach a point where each new dollar of revenue takes more to carry than the one before. More of the work behind it now runs on inventory, exception handling, credit cleanup, and senior judgment. The senior team feels it before the reports can connect it.

the rules

Built for a smaller, simpler version of itself.

The customer exception, supplier lead time, pricing override, and billing treatment all made sense when a few people could still hold the detail.

The business was not built wrong. It was built around a smaller range of customers, products, suppliers, branches, and exceptions. The pricing matrix, lead-time fields, customer rules, freight assumptions, and billing logic were enough for the version of the company they were built to serve.

Then the company kept moving. A customer exception became normal treatment. A supplier lead time changed, but the old assumption stayed in the file. An override protected a renewal and kept getting reused. A billing treatment lived in one person’s memory because encoding it was never urgent. An acquired branch brought its own account habits, supplier terms, and ways of making the order work.

None of this was reckless. At smaller scale, experienced people could close the gap. The senior CSR knew the account. The branch manager knew when to walk the row before promising availability. The pricing analyst knew which spreadsheet sat beside the matrix. The controller knew which credit memo had to be hand-walked against the right PO line.

That local handling did real work. It protected service, preserved revenue, and kept the business moving.

At the next stage, the same handling stops being occasional. It repeats across more customers, more branches, more SKUs, more channels, more acquisitions.

At smaller scale, people filled the gaps. At this scale, the business runs on the gap-filling.

Revenue keeps rising. Margin, cash, and working capital do not follow. Each new dollar takes more to earn than the last.

the order

The order enters already decided.

The price, date, freight assumption, spec, and customer treatment are set before the rest of the chain has to make them true.

An order does not enter the business as demand alone. It enters with decisions already attached. The price the rep quoted. The date the customer was promised. The freight assumption built into the price. The spec accepted. The terms attached to it. Sometimes a documentation requirement, a packaging condition, a ship-complete rule, or a service obligation the business has accepted for that customer.

At the point those decisions are made, the picture is partial. The pricing matrix reflects what was loaded, plus overrides learned over time. Availability is what the system showed when the order was accepted. The lead-time field reflects an assumption that may or may not still hold. The freight assumption may be built around a sourcing point the order will not actually ship from. The customer treatment may live in notes, memory, or an old renewal history rather than where the order release can use it.

Nothing has gone wrong yet. The order can look clean at entry: priced, dated, accepted, complete enough to move. But each decision now has to be made real by another part of the business.

Purchasing has to source what the lead time promised. Operations has to deliver what the system said was available. Logistics has to ship at the freight the price assumed. The warehouse has to honor the packaging or ship-complete rule the customer expects. Billing has to invoice what was delivered against what was quoted. AR has to collect what the customer agreed to pay against the invoice that landed.

The order is not wrong.

It was accepted against the picture available at the time. The problem is that the picture can be locally true and still incomplete for the whole chain. Stock was available when quoted, then gone when picked. A supplier lead time was still in the file, but no longer matched how the supplier is behaving. A substitute clears spec, but changes cost. Freight splits across branches after the price assumed one shipment. A billing treatment is known by the account team, but not visible where the invoice is created.

The order still clears. The customer may still be satisfied. Cash may still arrive.

But the economics change along the way.

The difference is carried by people, inventory, expediting, credits, side files, and senior judgment between order entry and cash arrival. One order can be handled this way. At the next stage of growth, more products, more customers, more branches, more channels, and more inherited practices make that carrying recurring.

the difference

Growth adds difference, not just volume.

The terms, the inventory depth, and the handling that win the account are the same things the order has to carry.

Volume alone does not usually create this. A business running twice as many of the same orders to the same customers gets better at carrying them. The warehouse picks from the same bins. Buying hits the volume brackets that trigger the supplier rebate. Freight consolidates onto standard lanes with regular carriers. Invoices match the contract table without a price dispute.

These businesses do not usually grow by repetition. They grow by adding difference: new products, customer-specific terms, service attached to the product, new channels, and acquired branches that arrive with their own history.

The unit stays familiar while the work under it changes. A SKU stays a SKU until it carries a heat number, a country of origin the customer restricts, a revision level, or an approved-manufacturer list that decides whether it clears the customer’s receiving dock. A customer stays a customer until it has twenty ship-to sites, each with its own barcoding, receiving window, and split-shipment rule, and an EDI mapping that rejects the whole invoice over one mismatched character. A branch stays a branch until it carries local pricing nobody wrote down, its own units of measure, and supplier lines the central system never mapped.

A single order can pull from all three at once. Stock shows available across branches on the screen, then disappears before the pick ticket prints. The quoted price fits the rep’s side spreadsheet but conflicts with the ERP contract table. The rebate depends on a lot certificate the warehouse forgets to attach. Each is small; together they are what the order now has to clear.

None of that variation is waste. It is the reason customers buy. They buy because the stock is actually there, because it ships complete and on time, because the company bends to their terms: the payment schedule, the EDI mapping, the invoice built to pass their audit. They buy the service attached to the material and the branch that knows the problem before their own buyer does. They are paying for a business that bends so they do not have to.

So accepting the order was never the mistake. The problem is where the variation is held. When it lives in memory, side spreadsheets, stale fields, exception calls, and senior judgment instead of in rules the business can run on, growth turns the differentiation into recurring drag.

The work is not to remove the complexity. It is to make the rules and routines carry it.

the reports

The reports show what shipped, not what was promised.

Revenue reads clean; margin scatters across freight, substitutes, rebates, and credit memos, each in a different ledger.

The cost reaches the reports eventually. It just does not arrive as one condition. It arrives after the work has run, split across the numbers the business already reviews.

Revenue is the cleanest number. More orders. More customers. More shipped volume. By that measure, the company is still moving.

Margin is harder, because the leakage never sits in one place. Off-matrix quotes bypass the purchasing paths that would hit the volume brackets, so the supplier rebate goes unclaimed. A price deviation authorized to protect a renewal becomes a permanent, untracked baseline in the customer file. Freight leakage lands in one COGS line, substitute cost in another, credit memos in AR. By the time the controller assembles the bridge, the order that produced the cost is several steps removed.

Service metrics point outward. OTIF, backorders, returns, and escalations send attention to operations, supply, and the warehouse floor. A routine order pulls stock the system had allocated to a contractual account, and the warehouse picks what the ticket prints. Those teams can fix the immediate miss. They cannot show why the order entered in a shape that made the miss likely.

Cash and working capital tell their version later. DSO lengthens by weeks, and the cause is rarely collections. An unmapped unit of measure or a price mismatch makes the customer’s AP system reject the whole invoice run, and the money sits in disputed aging while clerks hand-walk credit memos to clear it. Inventory stays high with safety stock added branch by branch, because planning no longer trusts the system’s lead-time fields.

Headcount tells another version. The business quietly staffs the friction: more pricing support, more data cleanup, more expediters, more billing coordinators. Each hire is rationalized on its own. The backlog was backing up. The close ran late. The account needed a hand. The company is buying people to carry what the rules cannot.

None of these reports is wrong. They are built to show outcomes after the work has run. They are not built to show how much of the business is now spent correcting, translating, and settling each order on the way through.

So leadership gets several explanations. Pricing discipline. Supplier reliability. Warehouse execution. Billing accuracy. Customer behavior. Inventory policy. Sales mix. Each is partly true, and each points to a different owner. The order is not.

the ceiling

Never a crisis, which is why it becomes a ceiling.

Carried by the COO’s calendar, by overrides on overrides nobody owns, and by working capital climbing faster than revenue.

The business does not break. It holds, and it costs more to hold every year. The cost is paid now, before any report shows it, and it is paid in three places at once: by the people, by the systems, and on the balance sheet.

People carry the first share, and the cost is no longer where it started. The absorption that used to sit with a senior rep or a branch manager has climbed into the senior team. The COO’s week fills with allocation calls a rule should have settled. The CFO’s close runs late because half the margin bridge is reconciled by hand. Each new hire takes on the same exception load as the last, so headcount grows ahead of throughput. The more expensive cost is the one nobody books: the senior time that should be building the next phase goes to holding this one together.

Systems carry the next share. The ERP did not break; it bent. Custom fields piled onto the customer master and the item master to hold what the standard record could not. The pricing matrix runs on overrides on overrides nobody owns. The CPQ carries hardcoded exceptions for accounts the original setup never anticipated. Side spreadsheets run in parallel because the planner, the rep, and the pricing analyst cannot trust the same record.

Capital carries the rest, and on the balance sheet it reads as prudence. Inventory turns fall because supply gets positioned defensively against lead-time fields nobody trusts. Receivables age into the older buckets as disputed lines and documentation holds take longer to clear. Working capital climbs faster than revenue because both ends of the cycle thicken at once. Supplier rebates accrue and then sit unrealized, because the fragmented, off-matrix buying never hits the volume thresholds the plan assumed. Each new dollar of growth needs more capital behind it than the last.

On paper, all of this looks routine. The headcount sits in SG&A. The inventory and the working capital sit on the balance sheet. The expedited freight sits in cost of goods. None of it is labeled what it actually is: the cost of holding the business together one transaction at a time.

Customers do not always leave. They learn. They learn which dates hold and which slip, which invoices to dispute, which terms to tighten at the next renewal. Their AP systems start short-paying the deviations by default. A missed date that once drew a phone call becomes a compliance penalty written into the renewal. The next RFQ comes back with a little less margin and a little more service expected. The customer is not punishing the business. They are pricing the patterns they have learned to expect.

Suppliers learn too. They learn which forecasts hold, which buyers carry defensive inventory, which POs change after they are cut. Discretionary pricing support gets harder to win when the actual mix keeps drifting from the forecast. When capacity is tight, allocation goes to the accounts that are cleaner and cheaper to serve. The supplier base looks the same on paper. The terms behind it have moved.

A business carrying this can grow for years. Revenue rises, customers keep buying, the senior team keeps showing up. Nothing fails cleanly enough to force a correction. The cost is not catastrophic in any single year, which is why it persists. Each local call stays rational on its own: the safety stock protects the date, the credit memo clears the dispute, the overnight freight saves the account.

But this is not a slowdown. It is a ceiling forming under the next phase of growth. The move the senior team would make next runs straight into the conditions already straining today’s volume. An add-on brings another customer master, another item master, and another history of promises made before close into a layer already spent on manual handling. A new digital channel puts pricing and availability in front of the customer directly, and removes the people who used to fix the data before the customer ever saw it. What is holding the business back is no longer the market. It is how the business runs.

The ambition is still there. The capacity is not.

What is missing is not on this year’s P&L. It is the markets not entered, the moves not made, and the company the business does not become.

the fixes

The standard responses do not reach the layer.

A new leader, a new system, a commercial operations team: real local change, and the matrix still drifts.

At this point the senior team acts. It does not ignore the condition. It changes leadership, funds systems, builds operating cadence, and stands up teams to catch what keeps leaking through. Each response is real, and each improves what sits around the order. None of them, by itself, changes what the next order inherits.

The first response is usually a new leader. A new CRO, a new COO, sometimes a CFO or CEO, someone who has done this before. The leader makes real changes within the role’s authority. Territories get realigned. Compensation changes. Pricing approvals tighten. Forecast reviews sharpen. Credit discipline gets more attention. Decisions move faster where the role can enforce them.

Those changes are real, and they can lift behavior within a quarter or two. But six quarters later the working capital is still climbing, the pricing matrix is still drifting, and the side spreadsheet is still on the analyst’s desk. The leader has not failed. The leader changed the levers the role controls, and the next order still depends on the records, rules, and handoffs underneath them: the item masters, the customer rules, the freight assumptions, the substitution logic, the billing treatments that were never encoded cleanly. Rebuilding those crosses functions, systems, and branches, and it has to happen while the business still sells, ships, invoices, and collects every day.

The second response is a new system. A new ERP, a CPQ, a CRM, a BI platform, a customer portal, any of them, or several at once. The business gets mapped. Workflows get documented. Master data gets reviewed. Approval paths get designed.

Then the blueprint meets the real business. The standard configuration wants clean item masters, stable units of measure, structured customer rules, and disciplined exception paths. Forcing that design too fast would break service, disrupt accounts, or strip out the local treatments customers already rely on. So the build makes room for the exceptions instead. Custom fields get added. Middleware connects what does not connect on its own. Exception tables hold the account treatments the standard model cannot. The pricing matrix comes back with a cleaner interface and the same inherited overrides. The portal exposes the same availability and documentation gaps in a cleaner screen.

The system does not fix the operating logic. It runs whatever logic it is given, and it asks the business to supply the decisions it has not made: which exceptions are valid, which rules should change, which records can be trusted. Where those decisions are still open, the system encodes the ambiguity or pushes the work back outside the platform. The business gains control in one place, and in another it builds a new dependency: simple changes now have to move through custom fields, middleware, and approval paths wired around the old workarounds. It is harder to change than before.

The third response is to stand up commercial operations. A deal desk, a pricing council, forecasting routines, dashboards, exception tracking. The visibility is real, and this is the closest of the three to the actual work, because commercial operations sits right next to the rules, the handoffs, and the decisions that shape the order before it moves.

But governing the exceptions is not the same as owning the records that produce them. The team can catch an exception earlier, route it better, and show the pattern more clearly. If it cannot change the customer record, the pricing logic, the freight assumption, the substitution rule, or the decision right that created the exception, it becomes one more place where the workaround is managed well.

So the dashboard improves and the council meets. Exceptions get tagged. Deals run through review. Reps learn which parameters trip an escalation and which ones can be worked around. The analyst keeps the side spreadsheet alive because the quote window still has to be protected. The critical order still gets pushed through by hand when the formal route cannot move fast enough. The team adds discipline and the first real view of the condition, but standing it up does not install the logic it was created to govern.

The leader improves the behavior. The system improves the control. The team improves the governance. None of the three, on its own, changes what the next order inherits. That is why the conditions continue. The responses are not wrong, and they are often necessary. They simply leave the same records, rules, handoffs, and decision rights sitting in the path, waiting for the next order to run through them.

The work is not one more response built around the order. It is changing what the order has to rely on in the first place.

the layer

The work that has not been done.

It starts at the pricing matrix, the supply card, the substitution authority, and the billing treatment.

That work sits at the layer the standard responses do not reach: the rules and routines that decide what the business is allowed to commit to, on what terms, and how the commitment is carried through the chain to cash.

It is rebuilding the pricing matrix as maintained logic instead of an accumulation of overrides. It is moving the customer’s shipping, documentation, and billing requirements out of a CSR’s memory and into the workflow where order release can use them. It is reconciling the item and customer masters across acquired branches so the business stops running parallel structures under one name. It is maintaining supplier lead times, allocation assumptions, and units of measure as owned records rather than periodic cleanup. It is defining substitution authority plainly: which substitutions are approved rules, which need review, and which are margin leakage to retire. It is settling price, availability, freight, documentation, and billing at order release, before the downstream teams have to make the order true.

None of this is novel. All of it is hard, because the business has avoided it for years and the debt is now load-bearing. The override protected a renewal. The side spreadsheet keeps the quote moving. The custom field prevents a service miss. Each workaround had a reason the day it was made. Together, they became the structure the business now runs on.

So the real decision is not about systems at all. The first question is not whether a system can carry the rule. It is which rule the business is prepared to make true. The business can keep paying people, systems, and working capital to translate every order after it enters the chain. Or it can rebuild the records and the rules the order depends on, so the next order enters cleaner than the last.

This work does not begin with a new market, a new org chart, a new system, or a new operating model. It begins in the specific places where the business commits before it can deliver: the pricing matrix, the supply card, the customer file, the order-release condition, the substitution rule, the documentation requirement, and the billing treatment.

Each new dollar can stop costing more than the last.

That is where Davello & Co. works: in the records the business already uses, alongside the people who have been holding the exceptions, until the order no longer has to be carried by hand.