Replace the spreadsheet that runs the company

Custom software has a bad reputation in the mid-market and it is mostly earned. Projects arrive late, cost more than the number in the approval memo, and land on users who were never asked what they do all day. Half the features go unused. The vendor’s team disperses. Two years later the thing is a legacy system with no owner.

Almost all of that traces back to the first six weeks. Requirements written from a conference room instead of from the floor. Success defined as delivery instead of adoption. No plan for who maintains it.

IT21 builds and extends systems: custom applications, integrations between things that were never meant to talk, workflow that replaces a chain of spreadsheets and email approvals, and enterprise resource planning (ERP) build and extension work. Running those systems day to day is Technology Managed Services. The control layer over an ERP — segregation of duties, change approval, access review — sits under Operational Governance.

What you get:

• A requirements document written from watching the work happen, not from a wish list meeting
• A build plan with phases, so something usable ships before the budget conversation reopens
• Integration to the systems you keep, so data is entered once
• Testing evidence, version control and a documented release process from day one
• Handover that includes documentation and training, so the system survives the departure of whoever championed it

Assess starts with observation. What the process genuinely is, including the workarounds people have stopped mentioning because they have become the process. Transform is the build, staged so you see working software early and can redirect while redirecting is still cheap. Optimize is the period after go-live that most projects treat as the end: the fixes, the second wave of training, the reports people ask for once they understand what is possible.

We build with the audit in mind, which is unusual and occasionally annoying during a project. Change control from the first sprint. Approvals recorded. Test evidence kept. Access designed so one person cannot both create a payment and release it. Retrofitting those things into a finished system costs several times what building them in costs, and someone will eventually ask for them — an auditor, a bank, a customer’s security team, or an insurer.

[PROOF: application or ERP development engagement — sector, region, what was built, what it replaced — supply]

If a build is on the table, the IT Risk & Readiness Assessment is a reasonable first hour spent. Measured against a recognized technology-governance framework, it shows what you already run, what it costs to keep, and whether the problem in front of you calls for a build, a configuration change, or a different product entirely. Sometimes the answer is that you do not need us to build anything.