Choosing who builds your software is one of the highest-leverage decisions a founder or business owner makes — it determines whether you end up with a product you can run and grow, or a half-finished codebase you have to pay someone else to untangle. The hard part is that everyone sounds competent in a sales call. This checklist is the set of concrete questions and signals that actually separate a studio that can ship from one that cannot.
1. Can they show you working software they built and run?
The strongest signal is shipped, live software — ideally things the company itself owns and operates, because that proves they can carry a product all the way to production and keep it running, not just write code for a demo. Ask to see real, usable products and poke at them. We point clients to our own live products — SocialPatra, CodeBrainery, ContentBuffer, Thumbnail Art Studio, and Linq List — precisely because you can go use them today. See them on our products page. Talk is cheap; a running product is not.
2. Who is accountable when it breaks in six months?
Ask directly: if this breaks in production half a year from now, who fixes it? A studio that builds andruns software has an answer. A team that hands off code and disappears does not. Continuity matters more than almost anything — the “bus factor” of a single freelancer who stops replying is a real risk to your business. We wrote a fuller comparison in our studio vs freelancers guide.
3. Do they ask about the business, or just the features?
A good partner asks who your users are, how you make money, and what the one workflow is that has to work perfectly at launch — before they quote you. A weak one just takes your feature list and prices it. The difference shows up later: a partner who understands the business pushes back on features that waste your budget and protects the ones that matter. If nobody on their side is curious about why you are building this, be cautious.
4. Is the scope and price honest?
Be wary of two extremes: a suspiciously cheap fixed price on a vague scope (it will return as change requests and resentment), and an open time-and-materials arrangement with no estimate and no accountability. The healthy version is a clear scope with a real plan, timeline, and price — fixed price for well-defined work, time-and-materials with a tight feedback loop only for genuinely exploratory work. We break down how to scope budgets honestly in our cost-to-build-a-SaaS and cost-to-build-a-mobile-app guides.
5. Do they cover the full stack you need?
Most real products need several disciplines — backend, frontend, design, deployment, and increasingly AI. Coordinating four freelancers across these means you are doing the integration job yourself. Confirm your partner can cover what you need under one plan. Our work spans SaaS development, websites, mobile apps, and AI solutions for this reason — one accountable team rather than a stitched-together cast.
6. How do they handle ownership and handover?
You should own your code, your accounts, and your infrastructure — full stop. Confirm that the source lives in a repository you control, that third-party accounts (hosting, payments, email) are in your name, and that you can take the project elsewhere if you ever need to. A studio confident in its work has no problem with this. One that locks you in with code or accounts you cannot access is a red flag.
Red flags to walk away from
- No live work to show. Slides and mockups are not shipped software.
- A price with no plan behind it. A number without a scope is a guess you will pay for later.
- No clear answer on who maintains it.“We build it and you take it from there” is a handoff, not a partnership.
- Lock-in. If you cannot access your own code or accounts, you do not own your product.
- Promising everything, questioning nothing. A partner who never pushes back is selling, not advising.
The one question that cuts through it
If you only ask one thing, ask: “Show me something you built that is live, and tell me who runs it.” The answer reveals capability, accountability, and honesty in a single move. Everything else on this checklist is detail around that core.
If you are evaluating who should build your product and want a straight, no-pressure conversation — including an honest take on whether we are the right fit — tell us about the project at info@kodetra.com or reach us through our contact page.