Before I started my company, I was on the other side of a common founder’s problem. I needed a development team, but I couldn’t find one I trusted, and every vendor I talked to had the same pitch: fast timelines, reasonable rates, great results. What I actually got was no transparency on what they were building, shifting costs, and a product that didn’t do what I needed it to do.
In retrospect, I built AppMakers because I couldn’t find the partner I was looking for. So, I understand this problem from the inside, not just from watching it happen to other people. And trust me, I watch it happen constantly.
The app-creation challenge
The thing about hiring a development team is that you don’t find out if you made the right call for six months, sometimes even a year. By the time the problems show up, you’re deep in, the product is out, users are depending on it, and unwinding the decision is expensive in every direction. I got caught in exactly this situation myself.
That’s what makes it so easy to get wrong and so hard to recover from.
The mistake I see most often isn’t due to the typical “Well, that’s because you’re going offshore!” That’s not the problem. I’ve seen offshore development work well. The mistake here is treating vendor selection like a commodity decision.
You post a spec, collect quotes, pick the lowest number, and assume the output will be roughly equivalent regardless of who builds it. That assumption is what gets founders in trouble.
The 2020 CHAOS report on IT product outcomes says that only 16% of U.S. software projects succeed outright by finishing on time and within budget. Around 84% were canceled or challenged, while roughly one-third failed completely.
In my experience, it’s almost never because the engineers wrote bad code, but misaligned expectations, vague contracts, and vendor selection made on price alone.
4 questions to ask before you sign on
Here are four simple questions I tell every founder to ask before signing anything:
1. Can you show me a project similar to mine, and can you give me a contact I can actually call?
Most shops can show you a portfolio. The real test is whether they’ll connect you with a client who’ll talk candidly about how the work went and what they’d do differently. This reference tells you more than any polished case study. If a vendor stalls on setting up the call, treat it the same way you’d treat a stalled request to meet the engineers.
2. What happens to the code and the repository if we end the engagement?
I’ve seen founders get to a fundraise or an exit conversation and discover the contract wasn’t clear about who owned the code, and vague enough to create real legal problems. Not because anyone was being shady, just because nobody reviewed the contract carefully before signing. That’s a decision made in week one showing up as a problem in year two.
3. Who specifically will work on my project, and can I talk to them before we sign?
This question feels awkward to ask, but it’s the most important one. Any vendor worth working with will let you talk to the engineers before you commit. If that request gets deflected or stalled, that’s your answer.
4. How much direction will you, as a vendor, provide?
Founders often overestimate direction. Offshore development can be successful if the client side writes clear requirements, reviews deliverables, and pushes back when things drift. It falls apart when founders expect the vendor to figure out the product direction on their own. That’s not what they’re hired to do.
If you don’t have a technical cofounder or a chief technology officer involved, hire part-time senior technical leaders—often called fractional leadership—before you start the vendor conversation.
What to ask if you already have an app
If you already have an app with problems, the instinct is usually to patch it. Add someone to fix bugs, keep shipping features, and deal with issues as they come. I understand that instinct.
We tell every client to decide whether to fix or rebuild the app, upfront. At some point, it’s faster and cheaper to rebuild the parts that can’t be fixed than to keep working around them. Founders who figure that out early spend much less than the ones who figure it out after another year of building on a shaky foundation.
Even when we’ve stabilized buggy, unstable code on a tight budget, building atop weak architecture adds to what must get untangled later.
If everything on the list above checks out, the rate becomes almost secondary. If any of them don’t, no discount makes up for it.
Daniel Haiem is the CEO at AppMakers USA.