Modernize your old systems one piece at a time They're aged, not failed, so we start beside them
AS/400 · since 19989 modules
- Customers
- Pricing
- Billing
- Policy
- Claims
- Reporting
- Payments
- Agents
- Documents
New stackBilling
412 rules written downEach rule named in the new code
Outputs that match the old system4,210 of 4,210
Start with what the old system costs each team The workarounds people live with, and the pieces of the system behind them
Who feels itWhat they live withWhat it costs
FinanceMonth-end needs a billing report only one person can run.Every close waits on that person
OperationsA price change needs a release and three months.Competitors change prices weekly
SalesNew products wait for the core to catch up.Launches slip by a quarter
CustomersThere's no portal, so they call or email.Your team keys in what they send
ITThe people who know the code are retiring.Knowledge leaves with each of them
Risk and auditAuditors ask for a trail the system never kept.The trail is rebuilt by hand
Then keep, wrap, rebuild or replace each piece Billing works poorly and changes often, so Billing gets rebuilt
Changes oftenWorks wellWorks poorly
Works well, changes oftenWrap
Keep the core and put connections and agents around it, so new work happens outside it.
PolicyCustomersWorks poorly, changes oftenRebuild
Write its rules down and rebuild it, proved against the old output.
BillingPricingWorks well, rarely changesKeep
Leave it. It earns its place, and moving it pays nothing.
PaymentsWorks poorly, rarely changesReplace
Buy a package. There's nothing here worth building again.
DocumentsReportingRebuild it by writing every rule down first AI is good at reading old code, so that's where we start
- Week 1ReadAgents read the billing code and write its 412 rules in plain language.
- Week 2AgreeYour people confirm the rules and correct the ones the code got wrong.
- Weeks 3 to 8RebuildThe new piece carries each rule's name, so anyone can trace it back.
- Until it matchesProveOld and new run on the same inputs until every output matches.
Then switch over only when every output matches Old and new run side by side on months of real inputs
RapidIT, our AS/400 accelerator| Same input | Old system | New billing code | Match |
|---|---|---|---|
| Policy 88104, renewal | $1,284.50 | $1,284.50 | Match |
| Policy 88231, mid-term change | $316.20 | $316.20 | Match |
| Policy 90017, cancellation | −$442.75 | −$442.75 | Match |
| Policy 90452, late fee | $25.00 | $25.00 | Match |
Billing took over once all 4,210 outputs matched the old system.
Bring the system you'd most like to replace
We'll map it in five days, and you keep the map either way.