Grentech
Public service platform

FuelFinder

A clear, accessible service that helps people find essential fuel information when it matters most.

The challenge

During periods of fuel supply uncertainty, people struggled to find clear, current information about availability — relying on rumour, social media, and word of mouth, which created unnecessary pressure on local infrastructure.

Our approach

We designed a focused, accessible web service prioritising clarity and speed over feature breadth: a simple information model, resilient architecture for traffic spikes, and an interface usable by people under stress on any device.

From chaos to clarity

Explore how the workflow changed stage by stage — or read the full plain-text version below.

Before Grentech

  • Fragmented, unofficial information sources
  • No single place to check current status
  • Manual updates via social media posts

After Grentech

  • One authoritative, accessible information source
  • Resilient service during peak demand
  • Simple update workflow for administrators

The challenge

People had no single trustworthy place to check current information.

What users needed

Find accurate, current information in seconds, from any device.

The Grentech feature

A single, focused information service with minimal cognitive load.

Operational benefit

Reduced reliance on rumour and unofficial channels.

Read the full plain-text version
  1. Discovery

    Challenge: People had no single trustworthy place to check current information.

    User need: Find accurate, current information in seconds, from any device.

    Feature: A single, focused information service with minimal cognitive load.

    Benefit: Reduced reliance on rumour and unofficial channels.

  2. Peak demand

    Challenge: Traffic could spike suddenly and without warning.

    User need: The service needed to stay fast and available under load.

    Feature: Resilient, cache-friendly architecture built for demand spikes.

    Benefit: Consistent availability when it mattered most.

  3. Ongoing updates

    Challenge: Administrators needed to update information without developer support.

    User need: A simple way to publish accurate updates quickly.

    Feature: A lightweight content workflow for non-technical staff.

    Benefit: Faster, more accurate updates with less operational overhead.

Product capabilities

  • Real-time information display
  • Accessible, low-bandwidth-friendly interface
  • Resilient architecture for demand spikes
  • Content update workflow for administrators

Technology

  • Next.js
  • TypeScript
  • PostgreSQL
  • AWS

Outcomes

  • A calm, accessible experience during a high-stress public situation
  • Architecture that stayed reliable under high concurrent traffic
  • A content workflow non-technical staff could update directly

Have a similar challenge?