Our Approach

Honest about the platform

Progress OpenEdge is a mature platform. New systems are rarely started on ABL today, and we will not pretend otherwise. It is also actively maintained: Progress continues to ship long-term support releases and new tooling. What matters to you is narrower. The application runs the business, a rewrite is usually the most expensive and riskiest option, and the useful work is to get onto a supported release, keep the database healthy and modernize the parts that actually hurt, while you decide on your own timetable whether to replace the system.

Read first, recommend second

Every engagement starts by reading what is there: the code, the schema, the configuration files, the batch schedule and the deployment scripts. Recommendations come after that, and they are written down with the reasoning behind them.

Rehearse anything irreversible

Database conversions, dump and loads, and cutovers are rehearsed on copies of production until the timings and the checks are predictable. Each one has a written rollback plan and a clear point of no return. Nothing is run on production for the first time.

Both halves of the estate

Application code and the database are looked at together. Slow screens are traced from the ABL query through the index choice to the buffer pool, rather than being handed between a developer and a DBA.

Small, reversible steps

Modernization happens module by module. Each change is small enough to ship and roll back on its own.

Knowledge transfer is part of the job

Every engagement includes documentation and working sessions with the people who will run the system afterwards. The goal is that your team needs us less over time, not more.

Senior, US-based, hourly

The engineers you speak to are the engineers who do the work. Engagements are billed hourly as time and materials, with scope, staffing and timeline agreed in an initial conversation, and there is no framework or tooling licence attached to working with us.