Choosing a software company feels like a technical decision everyone assumes is about code. In practice it is a question of whether and fit — and both are visible if you ask the right questions. This is the checklist we recommend clients use, including on us.
Before you meet
Look for running software. Anyone can say "we build POS platforms". The stronger signal is a real system: a store counter running right now, a website worth visiting, a deployment you could be shown today. A small honest portfolio beats a polished impressive one.
Check the actual demo. Watch whether the review shows real screens with real, messy data — returns, price overrides, edge cases — or a slide deck of ideal states. Software lives in the messy screens.
Listen for scoping-first talk. "We should map your workflows and suppliers before we estimate" is the sound of a careful partner. "We can build that, no problem" with zero questions is a warning.
Three things that decide the future
The change process. Scope changes are normal in software; they must be priced and scheduled by written process, not negotiated mid-build. Ask what happens when you want a new report after the third week.
Ownership. Your data, credentials, and business knowledge are yours. The contract should say who owns the code and data — and it should be you for anything you commissioned.
The reaction to mistakes. Before signing, talk to a reference and ask: "When something went wrong, what did they do that week?" Teams that respond with fixes and clarity are the teams to keep for years.
Speaking about money
Software pricing in Kenya should be built from visible components: scope, people, infrastructure, support, timeline. Vague quotes with "miscellaneous" lines end badly. Our pricing is published honestly on the pricing section — each project starts from a written scope, not from a number on the phone.
The question that shows the future
Ask the partner directly: "Show me the documentation on how you communicated when the last project went over time." A straight answer with a plan is a keeper.
Software partnerships like this end well when they start with clear small tests. If our approach suits you, start a conversation — we usually make the scope visible in the first week, risks included.