How to Find the Right App Developer

You do not need another glossy portfolio of foreign banking apps. You need someone who can ship an app your cashiers, field officers, or members will use on a mid-range Android phone with uneven data - and who will still answer the phone after launch. Finding the right app developer is less about who codes the fastest demo and more about who fits your risk, budget, and process.

If you are still deciding whether custom is the right path at all, read the complete guide to custom software for SMEs in Kenya first.

Decide what “right” means for you

Before you Google agencies, write three constraints on one page:

1. Outcome - what must be true in six months (fewer stock errors, faster collections, members self-serving balances).
2. Constraints - Android-only vs both stores, offline needs, M-Pesa, bilingual UI, launch date that is real.
3. Working style - fixed weekly calls, English/Kiswahili preference, need for on-site workshops in Nairobi or remote.

Without that page, every developer looks “good” in a pitch.

Where Kenyan SMEs actually find developers

Common channels, with trade-offs:

• Referrals from operators like you - still verify; ask what went wrong, not only what looked nice.
• Agencies and product studios - clearer process, usually higher cost, better for multi-role systems.
• Freelance marketplaces - useful for small modules; risky as sole owner of a core business system.
• University / bootcamp talent - strong for junior capacity under senior direction; weak as lone vendor for payments and compliance.

Match channel to risk. Payment-heavy SACCO tools are not a “weekend Upwork experiment.”

A practical vetting sequence

Step 1 - Shortlist on evidence, not energy

Ask for:

• Two projects similar in complexity (roles, offline, payments), not just industry logo match
• Who on the team will actually build yours (names and roles)
• A sample of written scope or acceptance criteria from a past job (redacted is fine)

Energy in the meeting is cheap. Evidence of process is not.

Step 2 - Technical fit interview (even if you are non-technical)

You can ask useful questions without writing code:

• How do you handle M-Pesa failure states and reconciliation?
• How do you ship updates without breaking users mid-shift?
• What does staging vs production mean in your process?
• How do you test on low-end Android devices?
• What happens if the lead developer leaves midway?

Vague answers (“we use agile best practices”) are a smell. Concrete answers with trade-offs are a green light. Pair this with red flags when hiring a custom software developer.

Step 3 - Process fit

Clarify:

• Written scope before big build invoices
• Sprint demos you can refuse (“this is not what we meant”)
• Change-request rules
• Warranty after go-live
• Source code and account ownership

If they resist writing scope, they are selling hours, not outcomes.

Step 4 - Commercial fit

Compare apples to apples: same feature list, platforms, integrations, and support months. Lowest bid with half the testing is not a saving. For company-level checks beyond a lone freelancer, see what makes a good mobile app development company.

Checklist: signals of a solid partner

• Names the v1 cut and the later phases without prompting
• Asks about your staff devices and connectivity, not only Figma dreams
• Explains hosting ownership in plain language
• Includes UAT time in the timeline
• Offers a maintenance path after launch (retainer or rate card)
• Comfortable saying “no / later” to a feature that inflates risk
• Provides references you can actually call

Checklist: signals to walk away

• Guarantees a fixed date and fixed price with undefined scope
• Refuses to discuss who owns the code
• Demo accounts that only work on the salesperson’s laptop
• “We will figure out M-Pesa in phase two” when payments are core to day one
• Pressure to pay 100% upfront

Kenya context that should show up in the conversation

A developer who works well here usually raises:

• Mid-range Android as the default target
• Mobile money edge cases (timeouts, double callbacks, partial payments)
• SMS cost awareness for OTPs and alerts ([VERIFY] current gateway rates before launch)
• Training for staff who are phone-first, not desktop-first
• Data sensitivity for member or customer records

If the pitch assumes US-style always-on Wi-Fi and card-first checkout, keep looking.

Freelance vs company - a blunt comparison

Factor	Solo freelancer	Established team / company
Cost	Often lower day rate	Higher, more predictable process
Bus factor	High (one person leaves, project stalls)	Better coverage if staffed honestly
Process docs	Varies wildly	More likely to have templates
Best for	Small modules, prototypes	Core operational apps

Many SMEs start with a company for the core system and freelancers for later polish - that can work if ownership and APIs are clean.

What to send before the first serious meeting

Save everyone time. Share:

• One-page problem statement
• Who will use the app (roles)
• Must-have vs later list
• Integrations named
• Rough budget band in KES ([VERIFY] internally first)
• Decision date

Good developers use that to propose a realistic shape. Weak ones ignore it and sell a generic package.

Bottom line

To find the right app developer, define the outcome, demand process evidence, and score commercial clarity as high as UI polish. Treat red flags as exit signs, not negotiation colour. When you need the wider hire-and-build map, return to the custom software guide for Kenyan SMEs, then pressure-test vendors with red flags for custom software developers and the company checklist in what makes a good mobile app development company.