Company
Hello Tractor
Role
Product Designer (In-house)
Timeline
3 Weeks
Teams Involved
Product, Engineering
Tractor owners need to monitor their machines
Hello Tractor is an AgTech platform operating across 20+ African countries, helping connect tractor owners with farmers who need access to mechanized farming services.
To manage their machines, tractor owners use Hello Tractor’s fleet management mobile app to monitor live activity, track operators, manage geofencing, and keep their tractors active across different farming regions.
Many of these services depended on an active subscription.
But before this redesign, subscription management existed almost entirely outside the app — making it difficult for owners
to track renewals, understand subscription status, or know what happened when access expired.
The current system had some issues
Early discussions with the product and operations teams revealed that most subscription issues weren’t caused by payment failures themselves.
The bigger problem was visibility.
Owners often didn’t know:
when subscriptions were expiring
whether payments had been confirmed
what features would stop working
what to do once tracking access changed
Existing app experience before the redesign:
Existing app was difficult to navigate and subscription management had little to no visibility within the app.
The persona helped uncover how subscription issues affected daily operations in the field.
Exploring ways to make subscription status more visible
Before moving into high-fidelity screens, I explored different ways to surface subscription information more clearly inside the app experience.
The goal wasn’t to add more features.
It was to make important system states easier to notice, understand, and act on quickly.
Designing inside an already active product ecosystem
Because the app was already being actively used across different regions, the redesign needed to work within existing technical and operational constraints.
This included:
multiple subscription states
engineering limitations within the current product structure
different payment behaviors across markets
existing navigation patterns
Bringing subscription management into the product experience
The redesign introduced a dedicated in-app subscription experience where owners could:
monitor subscription status
receive renewal reminders
manage tractors under different states
renew subscriptions directly inside the app
use payment methods familiar to their region
The experience focused on reducing uncertainty before operational access became disrupted.
Subscription states became visible directly inside the navigation experience.
Renewal reminders were introduced before service disruption.
Active and unsubscribed tractors were separated to reduce operational confusion.
Payment methods were localized based on regional usage patterns.
Recovery flows focused on restoring confidence and visibility quickly.
Extending the visual language of the app
What working on this product taught me
Designing this flow changed how I think about clarity in operational systems. Users rarely experience products as isolated features.
They experience them during moments of uncertainty:
when access changes
when they don’t know what happens next
when systems fail silently
when navigation feels unclear
And in those moments, clarity becomes more important than just beautiful interfaces.
