An honest 2-minute check on the software your business runs on, and it won’t tell you to rip it out if you don’t need to.
What this 2-minute check tells you
Answer eight quick questions about the software your business runs on, and get a straight, honest read. No sign-up, no sales pitch.
You will land on one of four outcomes:
Keep it: it is doing its job. Leave it alone.
Fix it: sound foundations, a few fixable friction points.
Replace it: it is holding the business back; time to plan a move.
Act first: an urgent risk, such as unsupported software or a compliance gap, to close before anything else.
We build and support business systems for a living, and we will happily tell you to keep what you have when that is the right answer.
Free · about two minutes · no email needed to see your result · your answers stay private.
How often does your team fall back on spreadsheets or manual workarounds to do things the system can't?Rarely, it does what we needSometimes, for a few thingsDaily, we run half the business in spreadsheetsWhen you need a new report or a small change, can you get it?Yes, easilyWith effort, time or costBasically neverHow much time does your team lose to double-entry, re-keying, or chasing data across systems?Little to noneSomeA lot, it's a real dragIs the software still actively supported and getting updates?Yes, fully supportedI'm not sureNo / the vendor's gone / end-of-lifeIf the one person who really knows this system left tomorrow, how exposed would you be?We'd be fineSome disruptionSerious problem, it lives in their headIf you wanted ALL your data out of it, could you get it?Yes, easilyIt'd be hardLocked in, or I don't knowDoes it talk to your other tools: accounting, CRM, and the rest?Well connectedPartly / some manual bridgingIt's an islandIs a change coming (growth, new compliance, a new product or market) that it probably can't handle?No, we're steadyMaybeDefinitelyRoughly how old is the core system?Under 5 years5–10 years10–20 years20+ years, or no ideaWhen your team talks about the system, it's usually…Fine, it's not a topicA gripeA running joke, or 'the thing that blocks us'How often does it break, freeze, or need a nudge to keep going?RarelyOccasionallyRegularly, we plan around itDoes it comfortably meet your current security & compliance obligations?YesNot sureNo / we're stretching itAre you paying for capacity, modules or licences you've outgrown or barely use?No, it fitsSomewhatA lot, we're paying for the wrong thingCould it comfortably handle 2–3× your current volume?EasilyWith strainNoKeep it: it's pulling its weight.On the signals that matter, your system is doing its job. The niggles are minor and the risks are low. Replacing it would cost you money and disruption for very little gain.Keep it current: updates, backups, and a restore you've actually tested. | Write down how it works, so it doesn't all live in one person's head. | Fix the one or two things that annoy you, a small change beats a rebuild. | Reassess in 12–18 months, or sooner if a big change lands.Something specific still bugging you?Even on a healthy system, one well-placed fix can save hours. Ask us. No pitch.It's straining, but don't rush to replace.There's real friction here, but the signals point to fixable problems, not a dead system. A full replacement is likely overkill (and risky). Targeted work (a few integrations, some automation, the missing features) could buy it years for a fraction of the cost.Map where the time and friction actually go: the workarounds are the clue. | Tackle the top 2–3: an integration, a missing report, a bit of automation. | Cut the key-person risk: document and cross-train. | Reassess once the fixes are in. Replace only if it still can't keep up.Fix or replace: which is really cheaper for you?That's exactly the call we help people make. Tell us your situation and we'll give you a straight read. No pitch.You've outgrown it. Time to plan a replacement.This isn't a few niggles: the system is holding the business back on several fronts, and patching it further is throwing good money after bad. The real question now isn't whether to replace it, but how to do it without a painful, over-budget disaster.Start with what you actually need, not with software demos. | Get a full export of your data. Own it before you move. | Plan a phased migration, not a big-bang switch-over. | Budget for the real cost: build + migration + training + a buffer. | Pick a partner who'll tell you when off-the-shelf is the smarter buy.Replacing a core system is where most of the risk lives.Talk it through with us before you commit: we'll tell you the honest way to do it (and when not to). No pitch.Close the exposure, before anything else.Whatever else is going on, you flagged something that makes this urgent. Running the business on it is a risk you don't want to sit on: a security incident, a vanished vendor or an audit could force your hand at the worst possible moment.Get a full export of your data now. Don't wait for a reason to need it. | Pin down exactly what's unsupported or exposed, and the quick mitigations. | Treat any security or compliance gap as this-quarter, not someday. | Then decide fix vs replace with clear eyes, but close the exposure first.This one's worth a conversation sooner rather than later.Tell us what you flagged and we'll help you shut the risk down fast. No pitch.Start the check →Want a sharper read? Six more questions on age, reliability, security and growth, and a more detailed breakdown.Sharpen it: 6 more →What's driving thisA quick guide, not a formal audit. For a real read on your situation, talk to us.We recommend your next move includesEmail me my resultI'd like Creative Intersection to get in touch about my result.Optional. We'll email your result. No spam, ever.Prefer to talk now?Get a second opinion →you@company.com.au↺ Start over