The questions to ask before you hand anyone your idea and your budget.
Handing someone your idea and your budget is a big decision, and the wrong partner can cost you months and thousands. These are the questions we'd ask if we were in your seat.
Who will actually do the work?
Ask who writes the code, not who's on the sales call. Senior engineering and a junior bait-and-switch produce very different results. You want the people building it to be the people you trust.
Can they explain things in plain language?
If they can't explain their approach without hiding behind jargon, that's a warning sign, not a sign of expertise. Clarity is a feature, and you'll be living with this relationship for months.
Do you get a real plan before committing?
A good partner will scope and plan before asking for a big commitment. If the pitch is 'just trust us and pay,' be careful. Insist on a blueprint you actually understand.
Will you own everything?
Make sure you'll own the code, the documentation, and the accounts, in your name, with no lock-in. Ask directly. The answer should be an easy, unambiguous yes.
How do they handle things going wrong?
Software always hits surprises. Ask how they communicate when something slips and who's accountable. How a partner handles bad news matters more than how they handle good news.
Can they show how they work?
You want evidence of process, visible phases, testing, documentation, not just a portfolio of screenshots. Ask to see how a typical project actually runs, week to week.
Do their incentives match yours?
Be wary of anyone who profits from dragging the project out or locking you in. The best partners are the ones whose success depends on you actually shipping and succeeding.
Trust your read on communication
After a couple of conversations, you'll know whether they listen, whether they're straight with you, and whether you'd want them in the room when something breaks. Trust that read.