The firm — one principal, one engagement at a time

The platform

The wall was not the platform.

The pricing matrix carried years of overrides nobody had sorted into rules or leakage.

The principal spent years inside platform implementations in mid-market B2B technical distributors and manufacturers running complex, multichannel supply networks. Ecommerce projects, ERP modernizations, CRM rollouts, CPQ implementations, BI initiatives, customer portal builds. Different systems, different companies, different project teams. The work kept stopping at the same unfinished layer of the business.

The implementation would reach the moment when the system needed an answer the business had never settled. Which price should this account get when the order falls outside the matrix. Whether the freight exception was still valid. Who was allowed to override availability. Whether the customer’s lead-time promise was a real commitment or a habit sales kept honoring. Where the answer should live so the next quote, order, shipment, invoice, and dispute did not have to rediscover it.

The pricing matrix was only part of the truth. Beside it sat accumulated overrides, side files, and rep memory. Customer-specific behavior governed service but did not live anywhere the system could reliably find it. Inventory truth still depended on someone walking the row. Supplier lead times had not been maintained. Master data carried the same physical product set up different ways across acquired branches.

The work was to force those answers into the open. Keep the freight exception, price it, or stop honoring it. Make the ship-complete rule visible before the order releases. Decide who can override availability and when. Tie the lead-time promise to the supply rule the planner actually uses. Put the customer treatment somewhere the next rep, warehouse lead, billing clerk, and collector can all see before the same exception becomes the same dispute again.

Project after project, the wall was not the platform. The platform was capable.

The wall appeared when the system was asked to know that one customer always ships complete, another gets freight waived after a certain order size, a third has a lead-time promise sales keeps honoring, and a fourth receives a packaging treatment the warehouse learns only when someone remembers to tell them.

Those were not configuration gaps. They were business commitments without a governed place to live: not priced, not owned, not maintained, and nowhere the next person handling the order could find them.

That condition is structural to these businesses at this stage of growth. The business has outgrown memory, workarounds, and local judgment, but has not yet turned them into governed rules.

That is the layer the firm exists to work in.

The shape

It is a shape, not a sector.

The rules the business runs on live in people, inventory, and exception work, not the system.

These are private, mid-market businesses built on physical goods and recurring B2B accounts. They carry deep catalogs, capital tied up in inventory, supplier constraints, and sales that run through reps, branches, counters, portals, EDI, dealers, distributors, and direct accounts. The commitments they make have to hold from quote to cash.

As they grow, the rules get more granular. Customer price files. Freight terms. Return rules. Service expectations. Documentation requirements. Substitution logic. Branch exceptions. The business does not become simpler with volume; it accumulates more conditions that the next order has to respect.

The shape appears across technical distribution and industrial supply, building materials and construction supply, specialty manufacturing and assembly, regulated and compliance-heavy supply, and equipment businesses with service attached.

A fastener or fluid-power distributor with a six-figure SKU base. A building-materials dealer serving contractors through branches and counter desks. A specialty manufacturer quoting assemblies whose actual cost depends on routing, revision, and labor. A regulated supplier where the product is not complete without the right lot, certificate, or traceability record. An equipment business where the sale, installation, repair, and field support are economically inseparable.

The product categories differ. The operating condition does not.

The customer rarely buys only an item. It buys a price that has to survive the order, a delivery date operations has to protect, a substitute that still has to fit the application, a freight treatment someone has to honor, a packaging or documentation rule the warehouse has to see, and an invoice the customer’s AP team will accept.

The ERP may hold the item, the customer, the price, and the order. It may not hold the account habit, the branch constraint, the supplier date nobody trusts, the substitute the customer will accept, or the packaging rule that determines whether the shipment leaves cleanly.

Across these businesses, the recurring question is not whether the company has enough technology. It is whether the rules behind the order are explicit enough for the next person, branch, system, invoice, and cash cycle to carry them without rediscovering the exception.

The condition is not vertical-specific. The products change, the channels change, the end markets change. The same operating shape recurs across them.

The principal

The judgment stays close to the work.

The record, the workaround, the person carrying it, and the cost stay in one field of view.

The problem the firm works on is never in one place. A single customer commitment can live in the price exception in the account file, the delivery date sales gave to hold the order, the supplier date planning no longer trusts, the workflow that releases the order anyway, and the credit AR issues weeks later to settle what the system never carried cleanly. Read any one alone and it looks like a local exception.

Read together, they are one rule the business never decided. The record, the workaround, the person carrying it, and the cost have to stay in the same field of view.

That is the structure of the firm.

The firm is run by one principal. The principal stays in the work directly, not above it. There is no junior layer turning the business into summaries before the judgment is applied. The detail is not collected by one group, interpreted by another, and presented upward for a decision made at a distance.

Some operating questions require depth the principal does not carry alone. Manufacturing operations. Supply-chain design. Business systems. Data structure. Branch and field execution. Regulated documentation.

When that depth is needed, the firm brings in known senior practitioners from prior working relationships. They enter for defined parts of the problem: to test a routing, read replenishment logic, examine a data break, pressure-check a workflow, or understand the constraint inside a branch, plant, warehouse, service route, or system path.

They add depth where the work needs it, without moving the center of judgment. They extend the field of view, not the engagement.

The engagement

The engagement is bounded to stay coherent.

Following one commitment from price through availability, workflow, invoice, and cash.

The engagement is a bounded piece of work inside one company’s operating reality, not advisory coverage running beside the business.

The principal works directly with leadership and with the people who carry the order: the teams that price, release, source, ship, bill, collect, maintain the records, and keep the system moving when the formal path does not hold.

The work moves through actual artifacts. The pricing table the quote uses. The customer file where the treatment should live. The supplier record the planner no longer trusts. The branch transfer that protects the date and damages the margin. The workflow that lets the wrong order release. The report the controller uses to reconstruct what happened after the fact.

The point is not to inspect those materials from above. It is to follow the commitment through them. A price set in sales becomes a fulfillment decision. An availability promise becomes a substitute, an expedite, or a branch transfer. A missing rule becomes a billing exception, then an AR dispute, then a credit memo that quietly pays for the original ambiguity.

All of it has to come from one coherent engagement. Leadership needs to see the pattern. Operators need a rule they can use. Systems need a decision specific enough to build or change. Finance needs the economic consequence tied back to the operating cause.

The firm runs one engagement at a time because the work has to stay coherent. The next engagement begins when the current one is complete.

The account

Half of what the account runs on is nowhere in the system.

Some is real customer requirement; some is margin leakage nobody priced.

A plant account places what looks like a routine order.

The same product family. The same rep. The same branch. The same customer part numbers the account has used for years. The quote goes out cleanly enough, and the order is accepted.

Then the order starts changing.

The item the customer asked for is not available at the home branch. A substitute is available, but only one manufacturer is approved for that application. The ERP shows stock at another branch, though the branch checks the floor before anyone trusts the number. The supplier date in the record has not matched actual delivery for months. The customer needs the full order before a maintenance window, so a partial shipment will cause more trouble than the delay. Freight is waived because that is how the account has always been handled, though no one can point to where the rule lives.

The rep knows most of this. The CSR knows how the order usually gets saved. The branch knows what can actually ship. Purchasing knows which supplier date to ignore. Billing sees the freight treatment after the shipment, and AR sees it again when the customer short-pays.

No one is inventing the complexity. Half of what governs the account lives in the system. The rest is in email, in side files, and in the people who know how the order gets saved, knowledge the business has never turned into an operating rule.

The firm follows the last several orders through the people and records that touched them: the quote, the customer file, the price override, the item cross-reference, the branch transfer, the supplier record, the shipment, the invoice, the short-pay, and the credit memo.

The account still looks valuable, and the revenue is real. But the order has been collecting payment from the business in other places. A substitute protects the customer and costs margin. A branch transfer saves the date and adds freight. Inventory sits against a promise no one priced. A credit memo closes the issue without ever showing where the cost began.

By the time the account is reviewed, no single line shows what the business paid to keep the promise.

The work is not to document the exception and move on. It is to determine what the exception actually is.

Some of it is real. If the wrong manufacturer stops the customer’s line, the substitute approval is customer-specific complexity, and the rule belongs in the operating path. If the customer is buying against a shutdown, the delivery window is real, and the order cannot be run like standard replenishment.

Some of it is not. The freight waiver may be an accommodation the business never priced. The branch transfer may be necessary some weeks and wasteful others, with a workflow that cannot tell the difference. The supplier date may be a system limitation the planner has been quietly working around. The account habit may simply be older than whatever once justified it.

Then each piece goes where it belongs. The approved substitute becomes part of the customer rule. The delivery window is tied to the order so it is not run as routine replenishment. The freight waiver is priced or stopped. The branch-transfer condition is made explicit. The untrusted supplier date goes to IT as a decided business rule, not a vague request to fix the account. Billing sees the treatment before the invoice leaves, and AR stops receiving the same dispute as if it were new.

Leadership sees what had been hidden inside normal service. The decision becomes explicit: what to keep, what to price, what to stop funding, and what the system needs to carry.

The next person handling the account inherits workflow, not folklore. The next order carries the rule before the mistake repeats.

The door

The conversation starts with what keeps repeating.

A direct email to the principal, confidentiality first where records are involved.

The first step is not a polished problem statement.

It may be the account that keeps producing the same credit. The pricing rule nobody owns. The supplier date planning ignores but the system still shows. The invoice dispute that returns every month. The portfolio company where the numbers still hold while the operating reality underneath keeps requiring compensation.

If the substance cannot be discussed cleanly without opening records, confidentiality comes first. Account files, pricing history, supplier agreements, and portfolio-company records often need that boundary before the real issue can be named.

The first conversation begins with the condition itself: what keeps repeating, where it appears, who is carrying it, which records it touches, and what the business has already tried.

The question is whether the situation is specific, material, and close enough to the firm’s work to read clearly.

If it is, the work can begin there.

Email the principal directly: consult@davelloandco.com. Bring the condition that keeps repeating.