Enkaji started with a frustration we heard repeatedly: Kenyan businesses struggle to find reliable suppliers, and Kenyan suppliers struggle to find steady buyers. A construction company in Nakuru needs cement delivered on schedule. A hotel in Mombasa needs produce every Monday. A school in Kisumu needs stationery each term. The buyers exist. The suppliers exist. What is missing is a trustworthy place for them to meet, agree on terms, and transact. We built Enkaji to be that place.

The problem we set out to solve

Kenya's informal economy runs on relationships and phone calls. A buyer calls three suppliers, compares quotes by WhatsApp, hopes the truck shows up, and pays by M-Pesa. It works, but it does not scale. There is no central directory of verified suppliers, no standard way to compare prices, no record of who delivered what and when. For buyers, that means stockouts and overpaying. For suppliers, it means uneven demand and bad debt. Enkaji digitizes that layer: a directory of verified suppliers, transparent pricing, order tracking, and payment reconciliation.

Who it is for

Enkaji serves two sides. On the buy side: contractors, hotels, schools, clinics, retailers, and property managers — anyone who procures goods regularly. On the sell side: wholesalers, manufacturers, distributors, and agri-processors with inventory to move. The marketplace works because both sides have a pain point worth solving: buyers need certainty of supply, suppliers need predictable demand.

How we approached the build

We started narrow. Instead of building an "Amazon for Kenya," we picked one category — building materials — and one region. That let us solve the hard problems verifying suppliers, handling M-Pesa callbacks, and coordinating deliveries without boiling the ocean. The tech stack is straightforward: a Next.js frontend, a Node.js API, PostgreSQL for orders and inventory, and M-Pesa STK Push for payments. The hard part was not the code; it was the trust layer onboarding suppliers, verifying business registration, and handling disputes when a delivery goes wrong.

The trust layer is the product

A marketplace without trust is just a directory. Every supplier on Enkaji is verified: business registration, tax compliance, physical location, and references. Buyers see ratings and delivery history, not just a profile picture. Orders are tracked from quote to delivery, and payments are held until the buyer confirms receipt. That structure costs more to run than a classifieds site, but it is what makes transactions happen.

What surprised us

Suppliers were more skeptical than buyers. A supplier with a steady roster of long-term customers did not see why they needed a marketplace. Buyers, on the other hand, signed up quickly — procurement pain is acute and constant. Our lesson: in a two-sided marketplace, the side with the acute pain adopts first. You subsidize and court the other side until liquidity kicks in.

Where Enkaji stands now

Enkaji is live and processing orders. The early data confirms the hypothesis: buyers reorder when delivery is reliable, and suppliers value the steady demand more than the margin they give up. We are expanding categories and regions deliberately, not explosively. A marketplace that grows faster than its trust layer collapses.

What we would do differently

We would verify suppliers sooner and invest in onboarding support earlier. We assumed suppliers could self-serve; many could not. A marketplace is a service business wearing software clothing, and the service part training, support, dispute resolution cannot be automated away.

Build what comes next

Want to explore what these ideas could mean for your business? Start a conversation with our team.