Three Lines of business logic. Twenty Weeks to Go Live.

A cargo airline needed a simple change. A surcharge exception for a specific commodity on a specific outbound route. Business logic: three lines. Time to go live: twenty weeks.

Here is what happened between those two points.

The sequence

Day one: revenue management sends the request to IT. In a legacy cargo platform, pricing rules sit inside the codebase. Three lines of logic still means a development task. The ticket enters the backlog.

Week two: developer assigned. Requirements meeting. The rule seems simple but the pricing engine has dependencies that need to be mapped before anyone writes a line of code. A second meeting. A third.

Week four: code written and reviewed. QA verifies the change does not affect other pricing rules. Three days of testing.

Week five: change goes to staging. Revenue management reviews. They identify a scenario they had not considered. New requirement. Back to development.

Weeks eight to ten: change is ready for production. Next release window is two weeks out.

Week twenty: the exception is live. Revenue management had been handling it manually since week two.

What this actually cost

Developer time: approximately five days. Total cost when you account for internal coordination, meetings, and QA: significant. Revenue impact during the twenty weeks: real, and untracked.

The team did nothing wrong. They worked correctly inside a platform that was not designed for this pace.

The pattern behind this

This is not an exceptional case. It is the standard output of legacy cargo platforms when pricing and operational logic requires development work to change.

The business learns to work around it. Manual overrides become normal. The gap between what the system says and what the operation actually does quietly widens.

How Nexlog approaches this

We built Nexlog to close that gap.

Changes that are business decisions should move at business speed. That shaped every architectural choice we made, from the first line of code to how we structure implementations today.

Gollog, the cargo operation of Gol Linhas Aéreas and the largest air cargo operator in Latin America, implemented Nexlog across a full, complex operation in six months with no operational disruption. Smaller carriers structured their operations from scratch in weeks.

In both cases, changes that previously required long development cycles were handled at the pace the revenue management and ops teams actually needed. The cost of those changes was also a fraction of what they had experienced with previous platforms.

A common objection

“Our changes do not take twenty weeks.”

Some do not. But most teams, when they trace a specific change from request to production, find the elapsed time longer than they remember. The wait becomes routine. Routine becomes invisible.

A simple check

Pick one pricing or operational change from the last six months. Trace it from the day the business requested it to the day it went live in production.

Then ask: what would it be worth if that took days instead of weeks?