Notes on running a business on one system.
Practical material about connected business software — the assessment, the rollout and the parts that usually go wrong. We are publishing these as they are written.
In progress.
These are the guides being written. If one of them is the question you have today, ask us directly rather than waiting for it.
Where re-entry actually costs you
A short method for finding the places information is retyped between systems, and what each one costs per month.
Sequencing a suite rollout
Why operations or sales usually comes first, and what makes a second product worth switching on.
What identity resolution actually does
The difference between deduplicating a list and resolving a customer, and why reporting disagreements usually trace back to it.
Automating a handoff without breaking it
How to move a manual process into a workflow while keeping the human judgement that made it work.
Cross-functional reporting without a data project
Which questions need a warehouse, and which only needed a shared customer key all along.
Evaluating AI for business software
A set of questions worth asking any vendor about what their assistant can actually see.
How a rollout is usually sequenced.
This is the shape most implementations take. Timings vary with how much history you bring and how many people need training.
- Week 0Map the re-entryList every place data is retyped. This becomes the priority order.
- Weeks 1–2Configure the first productFields, workflows and permissions to match how you already work.
- Weeks 2–4Migrate what mattersCustomers, open transactions and balances. Not fifteen years of history.
- Weeks 4–6Run parallel, then switchOne cycle alongside the old process, then retire it deliberately.
- OngoingAdd the next productWhen the handoff to the next team is the thing costing you time.