Logistics & Field Ops · Est. $15k – $25k
Onfleet alternative: Cigo Tracker

Web logistics & field ops product delivered by Coralsoft

Coralsoft designed, built and shipped this product for the client.

WebReact NativeExpoTypeScript
onfleet-alternative-cigo-tracker.example / dashboard
Onfleet alternative: Cigo Tracker — product interface
The situation

What was in place before we started.

The client needed a focused product for delivery dispatchers. The first release needed route planning, driver tracking, and customer ETA updates, while managing changing schedules and intermittent connectivity. Coralsoft designed and delivered the 16-week MVP from discovery through release.

The client needed a focused product for delivery dispatchers. The first release needed route planning, driver tracking, and customer ETA updates, while managing changing schedules and intermittent connectivity.

Coralsoft owned product shaping, engineering, QA, and release across a 16-week engagement.

Constraint

Turn the core customer journey into a dependable first release without overbuilding the product.

Estimated Timeline
4 months
Estimated Team
4 people
Estimated Budget
$15k – $25k
Platforms
1
Estimated stack
React NativeExpoTypeScriptNode.jsPostgreSQL
Delivery story

Onfleet alternative: Cigo Tracker: a focused product delivered from discovery to release

01

Challenge

The client needed a focused product for delivery dispatchers. The first release needed route planning, driver tracking, and customer ETA updates, while managing changing schedules and intermittent connectivity.

02

How we built it

We mapped the core journey and data model first, then delivered route planning as a working vertical slice. The next iteration added driver tracking and customer ETA updates, with authentication, validation, loading and failure states designed into each flow. A web-first TypeScript build using React Native, Expo, TypeScript, Node.js kept the interface and service contracts consistent; the final weeks focused on QA, accessibility, and release preparation.

03

Delivery

The delivered 16-week MVP let delivery dispatchers complete the core journey without relying on disconnected tools. It provided a small, maintainable foundation for testing demand and prioritising the next release.

Coralsoft turned the product brief into a maintainable 16-week MVP.

Challenges

Each constraint, and what we did about it.

Constraint

Turn the core customer journey into a dependable first release without overbuilding the product.

What we did

We mapped the core journey and data model first, then delivered route planning as a working vertical slice. The next iteration added driver tracking and customer ETA updates, with authentication, validation, loading and failure states designed into each flow. A web-first TypeScript build using React Native, Expo, TypeScript, Node.js kept the interface and service contracts consistent; the final weeks focused on QA, accessibility, and release preparation.

Showcase

How the system fits together.

4 of 4 views
onfleet-alternative-cigo-tracker.example
Onfleet alternative: Cigo Tracker — product screenshot
onfleet-alternative-cigo-tracker.example
Onfleet alternative: Cigo Tracker — product screenshot
onfleet-alternative-cigo-tracker.example
Onfleet alternative: Cigo Tracker — product screenshot
onfleet-alternative-cigo-tracker.example
Onfleet alternative: Cigo Tracker — product screenshot
Roadmap

Estimated delivery sequence.

4 months
Weeks 1–2

Discovery & architecture

Coralsoft scoped route planning and define the data model.

  • Scope route planning and define the data model
Weeks 3–11

Core build

The team built route planning, driver tracking, and customer ETA updates.

  • Build route planning, driver tracking, and customer ETA updates
Weeks 12–16

Hardening, QA & handover

Coralsoft completed integration checks, QA, and release handoff.

  • Integration checks, QA, and release handoff

More work like this.

Every case study covers a product Coralsoft designed, built, and shipped for a client.