Requirement Assessment · Enterprise Fleet Billing · VMS Pro

Project Simplex

An enterprise fleet-billing requirement, answered line by line.

Grameenphone Ltd. issued a requirement for an automated fleet billing system — requisition to invoice, with two-way integration into their internal OneGP platform. Rather than answer with a brochure, we took every one of its 90 line items and checked each against VMS Pro, our live in-production fleet platform. The finding: roughly 65% is already built and running, and the requirement is deliverable in full. This piece is that assessment — what exists, what we build, and the two problems that actually decide whether a project like this succeeds.

Role Analysis & Solution Lead Sector Enterprise Fleet · Telecom Requirement from Grameenphone Ltd. Platform VMS Pro · Autonemo Items assessed 90
90Requirement items assessed
~65%Already built & live in production
100%Deliverable in full
10–12Weeks · indicative for the delta
The idea

Answer the requirement honestly, and the timeline means something.

Anyone can reply to an enterprise requirement with "yes, we support that." We did the opposite: every line was verified against the running system and marked one of three ways — already available, partially there, or a new build. Where something only half exists, we said so. Where it doesn't exist at all, we said that too.

That honesty is what makes the rest credible. It also surfaced the insight that reframes the whole project: what's being asked for is vendor-payable billing — what the company pays its vehicle owners — not client billing. Getting that direction wrong is the single biggest risk in any billing build, and our platform already points the right way, in production. The remaining work is additive, not a restructuring.

The two challenges we named in writing, before quoting anything: the OneGP integration is a dependency risk rather than a technical one, and "GPS distance or logbook distance?" is a commercial decision wearing a technical mask — settle it in the contract or argue about it every billing cycle.

The document

The assessment, end to end.

Opens in a new tab — including an interactive matrix of all 90 requirement items, filterable by status and section.

The same problem, in a lot of large organisations.

Automated fleet billing, vendor-payable reconciliation, requisition-to-invoice integration, GPS-versus-logbook disputes — any enterprise running a large vendor-supplied fleet eventually hits this exact wall. It's solvable, and usually faster than you've been told.

Related work
Mahfuz Akandমূল সাইটে ফিরুন