Builder.
Leader.

TechnologyProductDelivery

13+ years leading technology and product delivery across agriculture, international development, education and enterprise environments. I turn complex operational problems into products, platforms and systems people actually use — working across discovery, product strategy, architecture, engineering, delivery and adoption.

My work has supported 50,000+ farmers and 6,000+ mechanization service providers, while unifying 100,000+ operational records into trusted reporting.

Explore the work →Let's talk →

Behind the technology

About

I'm Feranmi — a technology executive, product builder, and engineer who has spent the last 13 years working on a simple question: how can technology make difficult things easier for people?

My career has taken me from software development into technology leadership, product development, organisational transformation, and public-facing technology work — for businesses, development organisations, agricultural programmes, and the field teams who actually use what gets built.

Take something complicated. Understand it deeply. Build something that works. Make it useful to people.

That structure holds across two organisations right now — deliberately, not by accident:

TracTrac — Full-time, primary role

Ikore — Technology leadership, advisory role

How this tends to go

I tend to get called when technology gets complicated.

Developer

Problem solver

Product builder

Technology leader

Systems architect

A three-month WordPress contract was supposed to be exactly that — three months. While I was there, I started quietly fixing everyday IT problems nobody had assigned to me: laptops, printers, systems nobody else wanted to touch. When the contract ended, every other developer on it moved on. I got asked back — not to build more websites, but to become the organisation's only technology lead. That pattern has repeated throughout my career.

Five kinds of impact

The scale is only part of the story.

Product

Products taken from problem through launch and adoption.

Data

100,000+ operational records unified into one trusted system.

People

Technology teams led, engineers mentored, users trained at scale.

Transformation

Enterprise systems and workflows redesigned end-to-end.

Field

Technology built for real conditions — patchy connectivity, pressure, scale.

Selected work

The work

Product · Field system

Case study 01

TracTrac Plus

Head of Technology — TracTrac · Full-time

Bringing farmers, mechanization service providers, machinery, and programme operations into one connected digital ecosystem.

50,000+ farmers · 6,000+ MSPs onboarded

Google Play →App Store →

Data · Architecture

Case study 02

The Single Source of Truth

Technology & Systems Architecture

Data existed across systems, spreadsheets, and processes. The challenge wasn't collecting more — it was building a foundation people could actually trust.

100,000+ operational records unified

Google Play →

Platform · Operations

Case study 03

TracTrac Camp Platform

Product Strategy · Architecture · Engineering · Delivery

Large-scale training programmes create hundreds of small operational problems — registration, attendance, assessment, reporting. TCP brought it into one system.

Visit TCP →Organisational login required

Offline-first · Field tech

Case study 04

VITAL 2

Field Technology Architecture

Connectivity isn't guaranteed. Devices vary. Users work under pressure. VITAL 2 was designed around those realities, not around ideal conditions.

Offline-first field technology

Google Play →Internal tool

Transformation

Case study 05

Microsoft 365 Transformation

Enterprise Technology Leadership

Technology transformation isn't always about building something new. Sometimes the biggest impact is changing how an organisation works every day.

56 users migrated

Civic tech · Community

Case study 06

CleanSweep

Feexet · Product & Technology Lead

Built for communities, not committees. Volunteers spot pollution and refuse sites directly in the app, then sign up for the cleanups that follow — turning willingness to help into coordinated action.

Google Play →

AI · Solar energy

Case study 07

Solar Afric

Feexet · Product & Technology Lead

An AI-powered companion for solar users — troubleshoot issues on the spot, work through self-guided courses, or connect directly with a verified technician or vendor.

View more projects →

Product thinking

I don't just build products. I think about why they should exist.

My engineering background taught me how to build. Product leadership taught me to ask a different question first — should we build this at all?

Discover

What problem are we solving?

Define

What should we build?

Build

How should we build it?

Deliver

How do we get it into people's hands?

Measure

What happened?

Learn

What did we learn?

Iterate

What changes next?

From strategy to shipped

Good ideas don't create impact. Execution does.

Building the right thing is only half the job. The other half is getting it delivered, adopted, and improved.

Plan

Scope · Roadmap · Dependencies · Resources

Deliver

Teams · Milestones · Risks · Releases

Adopt

Launch · Training · Feedback · Iteration

The big idea

More than building software.
Building systems that work.

Some problems don't need another app. They need someone willing to understand the entire system first — the people, the processes, the technology, and where they break.

Sometimes that means building a product. Sometimes transforming an organisation. Sometimes cleaning up 100,000+ records into a source of truth everyone can trust — and standing in front of the people who'll actually use it, making it part of how they work.

The technology is only successful when the people and the system around it are better because it exists.

Builder.
Leader.

About