Web application for Fuel Movement Registration between states and vendors

In a nutshell

A complete tool streamlining communication between trading partners, transporters and state fuel tax agencies, automating the enrolment of fuel loads and licensing in one system. The engagement began with a code audit of existing work and grew into a lasting partnership covering development, launch, maintenance and support, built on AWS, Java and React.

Challenges

The founders of Petroleum Tax Tools initially came to us for something narrow: an audit of the code that had been written so far. The review showed the existing results were not meeting their expectations, and on the strength of that assessment they decided to hand the entire development of the project to our team.

What they needed was a web application with an infrastructure capable of handling every procedure and operation running between vendors, in a domain where accuracy is not optional because tax reporting depends on it. Alongside the application itself, they needed a landing page for a product that was new to the market and tailored closely to its requirements.

Our approach

The audit in October 2019 did more than surface problems – it produced a clear outline of what the project should become. The full collaboration began in January 2020, and knowing exactly what was missing let us move quickly: we gathered the remaining information about scope and the features that had to be part of the design, created the backlog, and put our designer on UX while development got underway. The MVP was delivered three months later.

From there the work continued as a partnership rather than a handover. Working closely with the founders, we developed further features and took full responsibility for maintaining the product. Satisfied with how the collaboration was running, they later entrusted us with setting up their inbound marketing operations as well.

Starting from an audit rather than a rewrite

Beginning with a code review changed the economics of the whole project. Instead of committing to a full rebuild on an assumption, both sides had an evidence-based picture of what existed and what it was worth keeping. That is why the MVP could be delivered in three months: the scoping work had effectively been done before the contract for development was signed.

Outcomes