← Back to Notes
Product & Engineering · Jun 2026

Startups Don't Buy Code

If you're a founder, you probably don't actually want a developer. You want progress.

You want customers finishing onboarding. Fewer support tickets. Users who stop dropping off. Revenue that grows.

But when you hire 'a developer', you often get exactly that: someone who builds what's on the list. Weeks later the feature ships, and the number you cared about hasn't moved.

Code is only valuable when it moves the outcome you care about.

When I started on African Students' Network, the brief could have been 'build a platform.' The real need was simpler: students needed to find opportunities on expensive mobile data, without the site failing them. Building around that need led to an offline-first design that cut data usage by 40%, on a platform with a reach of 12,000+.

That's the difference between someone who asks 'what should I build?' and someone who asks 'what are we trying to change?'

Sometimes the answer is new software. Sometimes it's simplifying a workflow, removing a feature, or automating something your team does by hand. The right person will tell you which, even when the answer is less code.

So when you're hiring, it's worth asking not just what someone can build, but how they'd figure out what's worth building.

Have something
worth solving?

Hiring an engineer, building a product, or dealing with a problem you haven't figured out yet — start with the problem.

Tell me what you're trying to make happen.