Nobody in a growing manufacturer or distributor was hired to chase. The buyer was hired to buy well. The office manager was hired to run the office. The senior salesperson was hired to sell. Yet sit with any of them for a week and a pattern emerges: a startling share of the day goes to work that is simple, endless and nobody's actual job — emailing suppliers for dates, checking invoices against orders line by line, rebuilding quotes in spreadsheets, and answering the phone to say where an order is. This is a time audit of that invisible week, and of what it costs before anyone decides to fix it.

Job one: the chase

Every open purchase order carries a question — when will it actually arrive? — and until a supplier answers it, production plans, customer promises and cash-flow guesses all carry an asterisk. So someone chases: an email Monday, a follow-up Wednesday, a phone call Friday. Multiply by every open PO and the chase becomes a standing tax on the buyer's week. Wynura's savings model uses six hours a week of supplier chasing as its reference case — a deliberately ordinary figure for a business running a few hundred open orders a year. Six hours a week is 312 hours a year: nearly eight working weeks of a skilled person's time, spent asking a question a machine can ask on a schedule, over plain email, without forgetting a single follow-up.

Job two: the match

Supplier invoices arrive and someone checks them — against the purchase order, against what actually showed up on the dock. Done by hand, an invoice costs real money to process: published benchmarks put hand-processing at $10–22 per invoice, with APQC's median at $21.40, against $0.50–$1.00 fully automated. At 300 supplier invoices a month — the reference case in Wynura's published calculator — that gap is $32,400 to $77,400 a year. (That is a labelled example, computed from the benchmark range on those inputs; the calculator on this site runs the same arithmetic on any volumes you enter.) The cost is not only the processing. It is the variance found late — the invoice paid at the wrong price because the check was rushed, or the short delivery paid in full because nobody matched it against the receipt.

Job three: the quote

Distributor quotes that take 15 to 45 minutes by hand are assembled from price lists, stock positions and margin judgement that live in three different places. The quote itself is skilled work; the assembly is not. Worse is what happens after it is sent: nothing. Quotes die unanswered in inboxes at a rate every sales manager recognises and few measure, because the follow-up depends on the same person who built the quote remembering, days later, in a week that has already filled up with chasing and matching.

Job four: the answer

"Where is my order?" is, on published support data, roughly 18–50% of all customer tickets. Each one is small — a lookup, a reply — and each one interrupts whatever the day was supposed to be. The information exists; it is in the order record. The cost is the interruption, repeated dozens of times a week, always landing on a human because the customer has no other door to knock on.

What the four jobs have in common

Look at the four jobs together and a structure appears. None of them requires judgement at the moment it is performed. All of them require a complete, current record — the PO, the invoice, the receipt, the stock position, the order status. And all of them fail the same way when a person is unavailable: they wait. That is the profile of machine work. It is also why Wynura's Operations Stack is sequenced the way it is: Product, Market & Customer Analysis first, so the operation aims at real demand; then Purchase Order Chase & Tracking; Invoice Checking & 3-Way Match; Stock Alerts & Reorder; Quotes & Follow-Up; and "Where Is My Order?" Answers — every module reading and writing one shared record, so the quote, the PO, the invoice and the delivery can never disagree with each other.

Integration, stated plainly — including your CRM

The stack connects to the systems you already run — accounting, inventory and email — through its Integration layer, and reaches suppliers and customers over plain email, so nobody outside your business needs an account or a portal. That includes your CRM: if you already run one and require the stack connected to it, that integration is arranged during the proof of concept and deployment, so customer and order history stay in step with the shared record. If you run no CRM, nothing is missing — the stack works standalone on its own record. No rip-and-replace, no migration project, no second system to babysit.

What an audit should produce

You do not need software to run this audit; you need a week of honesty. Count the open POs and the hours spent asking about them. Count the supplier invoices and time ten of the checks. Count the quotes built, and how many were ever followed up. Count the order-status questions. The totals will either say the hand-work is cheap — in which case, genuinely, keep doing it by hand — or they will say what they say in most 10–200-person operations: that the business is spending its best people's scarcest resource on its most automatable work. Wynura's calculator exists to put a benchmark range on exactly those counts before any conversation starts.

Fourteen days to a measured answer

The alternative to arguing about the audit is running one. The 14-day proof of concept takes the stack live on a business's real orders, invoices and stock, scoped to the modules the business picks, and measures the chase hours, match rate and answer load before and during. Fourteen days later the decision is arithmetic, not opinion — which is the only kind of decision an operations week this full has time for.