Blog › Lead Generation

Why Tech Builders Struggle to Market and Sell Their Own Product

By Joseph Maina · · 4 min read

Laptop screen filled with lines of code above the keyboard

A developer spends six months building something genuinely useful. It works, it is fast, the code is clean. Then it launches, and almost nobody notices. This is one of the most common stories I see among technical founders, and it is rarely about the quality of the product. Building and selling are different skills, and the habits that make someone good at the first can get in the way of the second. It is a pattern, not a rule: plenty of builders sell brilliantly. But if you recognise yourself below, you are in large company.

"Build it and they will come" is the first mistake

Builders are trained to solve problems, and a finished product feels like the end of the problem. For a buyer, it is the beginning of a new one: they have never heard of you, they do not know whether you can be trusted, and they already have a way of doing things, even if that way is a notebook and a WhatsApp group.

Finding customers is a separate piece of work, with its own skills, its own time and its own failures. Treating it as something that will happen on its own after launch is why so many good products stall.

Builders describe the machine, buyers describe the problem

Look at the website of a typical technical product and you will often find the stack, the architecture and a list of features. A shop owner in Nairobi is not asking whether the system is cloud-based. They are asking whether it will stop stock going missing and whether it helps with their tax records.

The same product, described two ways

Builder language

  • "Cloud-based, API-first inventory platform"
  • "Real-time sync across devices"
  • "Built on a modern stack"

Buyer language

  • "Know what is in the shop, without counting"
  • "See today's sales from your phone"
  • "Your stock and M-Pesa payments in one place"

Illustrative wording. Use the words your own customers use.

Six gaps I see most often

None of these is a character flaw. They are habits that make sense when you build things, and cost you when you sell them.

The gapWhat it looks likeA better move
Features before problemsA page listing tools and featuresLead with the problem and the result
Waiting until it is readyMonths of building before a single customer conversationTalk to buyers in the first week
Hiding the price"Contact us" for everythingShow a starting price
UnderpricingCharging little because "it is just code"Price on the value of the problem solved
No distribution planA launch post, then silencePick one channel and use it every week
Hoping people sign up aloneWaiting for strangers to find the siteDemos, calls and WhatsApp conversations

Why this bites harder with Kenyan small businesses

In my experience, many Kenyan SME owners buy on trust. They want to see the thing working in their own shop, hear from someone they know, and be able to message a real person when something breaks. A polished sign-up page and a documentation site do not provide any of that.

The problems that sell tend to be practical ones: knowing the stock count, matching M-Pesa payments to sales, keeping tax records in order. If your product solves one of these, say so in those words, and show it.

Selling is a skill, and it can be learned

Many builders avoid selling because it feels pushy. It does not have to be. At its best, selling is a structured conversation that finds out whether you can really help, and says so honestly if you cannot. The part builders skip most is the ask: a clear next step at the end of every conversation.

A simple sales conversation
  1. Ask how they do it today: Listen more than you talk.
  2. Find what the problem costs them: Lost stock, lost time, lost sales.
  3. Show only the part that solves it: Skip the rest of the features.
  4. Handle the real objection: Usually price, trust or switching effort.
  5. Ask for a small next step: A trial, a deposit or a second meeting.

Get the first ten customers by hand

Before any advertising, sell to the first ten customers manually. Talk to people, demo in person, set up their account yourself and watch what confuses them. You will learn more about your product and your market than any analytics tool can tell you, and those early conversations become your marketing copy.

Expect a long funnel. The numbers below are illustrative, not a benchmark, and yours will differ. The point is that most conversations do not become customers, so plan for enough of them.

A manual funnel for a business software product (illustrative figures)
  1. Conversations: 100
  2. Demos: 30
  3. Trials: 10
  4. Paying customers: 4

The marketing basics a builder actually needs

You do not need a campaign to start. You need a handful of things done properly, in this order.

  • One clear page that says who it is for, what problem it solves and what it costs, as I set out in my landing page guide.
  • Proof: a customer's words, a number or a short video of it working.
  • Content that answers the questions buyers type into Google, starting with local searches, as in my local keyword research guide.
  • A quick, human follow-up on every enquiry, using a system like the one in my WhatsApp lead follow-up guide.
  • A weekly look at where customers came from, so you know what to repeat.

Who should do the selling?

There are three honest options. Learn the basics yourself, because the first customers should hear from the person who built it. Bring in a co-founder or partner who enjoys selling. Or hire help for the parts you do not want to do, and keep control of the accounts and the data.

Building is a skill and selling is a different skill. Neither is harder, but only one of them is waiting for you after launch.

Related articles