Business Applications
The systems your operations actually run on.
Every company of your size has a system everyone complains about, and a standing suggestion to replace it. Sometimes that is right. More often the platform is adequate and the problem is configuration, process, or training, and a replacement would spend seven figures to reproduce the same frustration on newer software.
Core system decisions are the largest discretionary technology spend most mid-sized companies ever make, and the hardest to reverse. Getting the diagnosis right before the purchase is worth more than any negotiation.
What good looks like at your size
We score against this benchmark, meaning what a well-run company of 50 to 500 employees should reasonably have in place, rather than against theoretical perfection.
The system carries the process
Work happens inside the platform rather than beside it. Shadow spreadsheets exist for genuine edge cases, not because the system cannot do the job.
Supported versions with an owned upgrade path
Each core platform runs on a supported release, and a named person owns the plan for staying current, including what it costs and when it happens.
Data moves without people
Systems that need each other’s data are integrated. Re-keying is rare, deliberate, and measured rather than assumed to be free.
Customization is minimal and documented
What was customized is written down and justified, and none of it blocks an upgrade or depends on one individual’s memory.
Licenses match reality
Seat counts are reconciled against active users at each renewal, and the modules you pay for are ones your teams actually opened this quarter.
What we typically find
Patterns common enough to name. None of them indicate a bad team. They are what happens when a company grows faster than the decisions that shaped its technology.
A blamed platform that is not the problem
The system everyone wants to replace turns out to be under-configured and under-trained. Replacing it would move the same failure to a new vendor at very large expense.
Operations running in spreadsheets
Critical processes live in files that shadow the system of record, held together by one person’s discipline, with no audit trail and no continuity if that person leaves.
An implementation that stopped halfway
Phase one went live years ago; phase two never happened. Nobody decided to stop. Attention simply moved, and the business has been operating in the gap ever since.
Customizations tied to one person
The modifications that make the system usable were built by a consultant or a former employee, undocumented, and now nobody will touch them, which is why the upgrade keeps slipping.
Paying for people who left
Seats provisioned for departed staff, sometimes for years, across several platforms at once. It is the single most common line of recoverable spend we find.
How we assess it
Where a document does not exist, that is itself a finding, and we say so plainly rather than treating the gap as an obstacle.
- Core platforms such as ERP, CRM, and line-of-business systems: fit, version, and support status
- Integration map: where data flows automatically and where people re-key it
- Customization debt that locks you into old versions or single individuals
- Adoption: what you pay for versus what your teams actually use
- Application inventory with version, support status, cost, and business owner
- Integration map and interface documentation, including the manual hand-offs
- License counts compared against active usage data
- Process walkthroughs with the teams who use each system daily
- Any pending implementation or upgrade plans, and the history of the ones that stalled
Questions the readout answers
Is the platform every vendor wants to replace actually the problem, or is it configuration?
What is the true cost and risk of the big system decision we keep deferring?
What this domain contributes to your report
- A fit assessment for each core platform: keep, fix, or replace, with the reasoning stated
- The integration and manual-effort map, with the cost of that manual work quantified
- A defensible recommendation on the system decision you have been deferring
- Named license savings, with the risk of each cut made explicit
How this domain is scored
Every domain is scored 0–10 on the same scale, so the scorecard shows you where to look first rather than a single undifferentiated grade.
Something here can hurt the business now. These findings lead the roadmap.
Functioning, but behind where a company of your size and stage should be.
In good shape. Worth maintaining rather than investing further right now.
A genuine strength, and often something to build on elsewhere.