You Just Bought a Small Factory. What Software Should You Fix in the First 90 Days?
Use the first 90 days to trace real orders, identify record owners and improve one handoff the factory can test.

Keep current work moving
On the second Monday after a hypothetical acquisition, a customer asks whether order 1864 can ship on Thursday. Sales has the promised date. Production has the traveler. A buyer has a supplier email that moves one component to Friday. The useful first software decision is to make that exception reach the person who owns the promise.
A new owner may feel pressure to replace the ERP, accounting system, or spreadsheets straight away. Give the team time to explain which records they trust and why. First, keep the business running: customers need clear dates, suppliers need accurate orders, people need to be paid, and production needs to know what to make next.
Make a short list of live commitments: open customer orders, promised dates, material shortages, jobs in progress, expected receipts, shipments that need invoices, and payroll dates. Add the name of the person who can confirm each item. Acquisition planning treats day-one readiness as a coordination task because several parts of the business must keep working through the change. [1]
Meet people in sales, purchasing, planning, finance, maintenance, and production early. Ask what must not stop, what goes wrong often, and which workarounds help the team keep orders moving. That gives you a useful first view without asking one person to explain the whole factory.
Follow a few real orders
Choose three or four recent orders. Include a straightforward job and one that had a changed due date, a split shipment, or a material substitute. Follow each one from quote and customer approval through purchasing, production, shipment, and invoicing.
Compare a few important details at each step: the drawing revision, quantity still due, material status, promised date, and current owner. If the ERP says material is available but the operator is waiting for inspection, record the difference. Do not quietly choose one version and discard the other.
Start with the business records because they show what the company promised. Check them against conversations with the people doing the work. A schedule is useful only when it reflects what can actually run on the floor.
Fix one important handoff
After tracing the orders, choose a repeated gap that causes avoidable follow-up. It might be a customer change that never reaches purchasing, a receipt that is not visible to planning, or a shipment quantity that finance has to confirm by email.
Before connecting software, agree on which record is trusted, who can approve a change, and who handles an update that fails. Test the handoff with a real but controlled example. Include a correction or missing detail so the team can see how the process behaves when information is incomplete.
Set a sensible 90-day target
A useful result may be a current list of open commitments, a map of the main systems and record owners, a short list of gaps that affect decisions, and one improved handoff tested with the people who use it. A full system replacement is not required to make progress.
Keep unresolved differences visible and assign someone to confirm them. That is more useful than making uncertain information look tidy. It also gives you a better basis for deciding what to change next.
For order 1864, trace who receives the new supplier date and who can change the production promise. Quindart’s supplier-update walkthrough shows how to test that particular handoff. [2]
| Checkpoint | Evidence to collect | Decision to make |
|---|---|---|
| First two weeks | Open orders, shipment records and the buyer’s current supplier confirmations | Agree who can change the promise and where the change is recorded. |
| By day 45 | Three traced orders, including one exception | Choose the handoff where missing information first changed a decision. |
| By day 90 | One repeat test with the affected planner, buyer and operator | Keep the improvement if the right person sees and can act on the change. |