Page 255 of 506 · Back to latest writing
Procurement improves when agents turn incomplete requests into governed vendor objects: clarifying fields, checking duplicates and contracts, identifying risks, and preparing approval packets. The boundary is firm—agents may recommend, but authorized humans must create financial commitments.
Finance is the natural starting point because its work already depends on evidence and reconciliation. Agents can classify exceptions, gather support, and prepare decisions, reducing unresolved issues and manual reconstruction while humans retain authority over ambiguous approvals.
Back-office transformation begins by replacing modern-looking ticket queues with governed operational loops. Each loop needs a named object, states, evidence, authoritative systems, and decision rights so agents resolve missing context instead of simply forwarding work to overloaded specialists.
Revenue alone cannot reveal account quality in AI businesses. This sequence connects model costs, support, implementation, roadmap drag, expansion, and pricing to a practical review for deciding when to reprice, automate, redesign, or exit.
Customer profitability matters only when a cross-functional operating review turns segment economics, account exceptions, and workflow costs into decisions. Shared analysis can expose margin leaks, distinguish strategic learning from poor fit, and drive repricing, redesign, or sharper targeting.
Poor-margin customers require different remedies: reprice value that outgrew its contract, automate repeated service burdens, redesign product-created costs, or exit structurally mismatched accounts. The right test is which action would improve the segment if repeated at scale.
Pricing is an operating filter that attracts particular customer behaviors. Aligning price and packaging with usage, implementation, support, governance, and delivery costs helps a company select customers its model can serve profitably instead of turning growth into margin pain.
Expansion quality depends on economics, not contract growth alone. Added users or workflows are healthy when margins hold and service burden stays controlled; expansion that activates disproportionate AI costs, support, governance, or custom work can make a larger account worse.