Most software projects
begin somewhere else.
A new customer. An acquisition. A deadline. A key person leaving. Software enters the conversation when the business can no longer work around the constraint.
What changed?
The same symptom can have very different commercial stakes. Choose the event that made continuing as before more dangerous than changing.
Growth
Growth should make the business stronger. Why is it making the operation harder to control?
When every new customer, site or service adds administration faster than capacity, the operating model has become the constraint.
D/02Acquisition
You acquired a business. You also inherited every system holding it together.
The value in the deal depends on making two operations work together without flattening what made either one worth buying.
D/03A new service
The market is ready. Your systems aren't.
A new offer can create advantage only if the operation can price, sell, deliver and measure it before the opportunity passes.
D/04A major customer
Winning the account is only half the risk. Can the operation keep the promise?
A strategically important customer can justify change, but a hurried workaround can become the most expensive account the business serves.
D/05Margin pressure
Your margin isn't disappearing in one place. It's leaking between systems.
Repeated entry, late decisions, errors and manual reconciliation create an operational tax that standard reports rarely expose.
D/06Regulatory change
The rules changed. Your accountability didn't.
New evidence, control and reporting requirements expose systems that cannot explain what happened or change at the required pace.
D/07A key person leaving
When they leave, what leaves with them?
A resignation or retirement exposes the rules, exceptions and recovery knowledge the company never made part of the system.
D/08Vendor end-of-life
The system has an expiry date. Your operation doesn't.
A withdrawal of support turns a tolerated dependency into a deadline and forces the business to decide what should replace it.
D/09Systems that won't cooperate
You bought the tools. You're still doing the joining up.
When information crosses systems through people, the operation inherits delay, ambiguity and failure nobody can see end to end.
The event creates the question. It does not dictate the answer.
The right response may be to change the process, configure a product, connect existing systems, modernise one part or build something the business should own.
Change the process
Remove a rule, handoff or exception that no longer earns its place before encoding it in software.
Buy or configure
Use a standard product where the work is standard and accepting its operating model creates no strategic loss.
Integrate
Keep capable systems and make the event, ownership, exception and recovery between them explicit.
Modernise
Reduce risk around a valuable system in controlled production slices instead of replacing everything at once.
Build and own
Create a capability when the rules, experience or ability to change are important enough to control directly.
Your strategy should survive contact with delivery.
ORBN works with advisers who understand the change and need a product and engineering partner to carry it into production.
Bring the change.
We'll help frame the systems decision.
The useful starting point is what happened, what is now at stake and who inside the business understands the operation.