Choose a software development company by how clearly it answers, not just by price. Before you sign, get in writing whether you'll own the code or hold a perpetual license, whose name the data and accounts are in, who will work on your project, how scope changes are priced, and what happens if you leave. Vague answers to any of these are a red flag.
The problem? Most buyers compare quotes and portfolios, then find out too late that they've walked into the "Vendor Trap": depending on a vendor without ever deciding to, with software that works but that they aren't sure they can move, change, or understand without the firm that built it.
What is the Vendor Trap, and how do you know you're in it?
It's the dependency that never shows up in the quote and nobody explained. The usual signs:
- You don't know whether you own the code or only have the right to use it.
- Your data, the domain, or the app store listing are in the vendor's name without you agreeing to it.
- Nobody outside the vendor knows how to deploy or fix the system.
- There's no documentation, or nobody has updated it.
- You're charged to hand over data or access that was already yours.
None of these is easy to fix mid-project. All of them are easy to prevent before you sign.
Who owns the source code: full ownership or a perpetual license?
Whoever your contract says, and there are two valid models. Depending on the scope of the project, Andes lets you choose:
| Full code ownership | Perpetual license | |
|---|---|---|
| What you get | The copyright in the code written for you | The right to use the software forever, on the agreed terms |
| Fits when | The software is the core of your business and you want any team to be able to change it | The system is built on components the vendor already has and reuses |
| Cost | Usually higher, because the vendor can't reuse that work | Usually lower, because you build on an existing foundation |
| What you take on | You decide who maintains and evolves it | The vendor keeps maintaining the foundation and its improvements |
Neither is better on its own. The question is which one fits your project, and that the decision is yours and deliberate, not something you discover when you try to switch vendors.
If you choose full ownership, ask for:
- Assignment to your company of the copyright in the code written for you.
- Source code delivered continuously to a repository in your name, not as a zip file at the end.
- A list of third-party and open source components, with their licenses.
If you choose a perpetual license, spell out:
- What you can do with the software: which users, sites, or companies it covers, and whether you can modify it.
- How support and updates work, and what they cost.
- How you get access to the code if the vendor stops operating.
Under either model, define whose name your data and your cloud, domain, and app store accounts are in.
What about the law? According to the US Copyright Office, a commissioned work is a "work made for hire" only in nine categories, and software isn't one of them, so without a written agreement an outside firm generally keeps the copyright. Honduras' copyright law (Decree 4-99-E) sets its own presumptions about computer programs. Either way, don't rely on defaults: put the model in writing. This is general information, not legal advice; have an attorney review your contract.
What questions should I ask a software development company?
Take these 12 into the meeting:
| Topic | Question | A good answer sounds like |
|---|---|---|
| Ownership | Will I own the code, or hold a perpetual license? | They explain both models and what each means, and put your choice in writing. |
| Cloud | Whose name are the servers in? | "Your account; we use access you can revoke." |
| Team | Who will actually work on my project? | Names and roles, not "a team of experts." |
| Continuity | What happens if a key person leaves? | "Everything is documented, and more than one person reviews the code." |
| Documentation | What documentation do you deliver? | Setup, deployment, architecture, and a user guide. |
| Scope | How do you price changes? | A written process, with an estimate before the work starts. |
| Quality | How do you test before release? | A staging environment, code review, and acceptance criteria. |
| Security | How do you handle passwords and sensitive data? | A secrets manager, least-privilege access, and MFA. |
| Delivery | How often will I see working software? | "Every two weeks, in an environment you can test." |
| Support | What happens after launch? | A support agreement with response times. |
| References | Can I talk to a client with a similar project? | Yes, or a documented case with measurable results. |
| Exit | If I leave, what do I get? | Your data, your access, the documentation, and whatever your chosen model includes, with an orderly handover. |
In a regulated industry like banking or healthcare, add the security questions from our guide to choosing a technology partner for banking and healthcare.
What are the red flags when choosing a software development company?
- They can't name who will be on your team.
- They resist putting the code in your repository until the final payment.
- The first estimate arrives with no questions about your business.
- They promise a fixed date and price on a scope nobody has written down.
- Every reference is "confidential" and there's no documented case to read instead.
Software agency vs freelancer: which should I hire?
| Option | Works when | Watch out for |
|---|---|---|
| Freelancer | The project is small and well defined | If they get sick, take a job, or disappear, nobody else knows the system |
| Agency | The system is critical and has to last for years | Getting a different team than the one that sold you |
| In-house team | Software is the core of your business | Salaries, turnover, and how hard senior hires are to find |
Fixed price vs time and materials: which contract is right?
Fixed price fits a scope that's fully defined and won't change; the vendor prices in risk to protect itself. Time and materials fits an uncertain scope, as long as you see working software every couple of weeks and approve estimates before changes. In Texas, the model affects sales tax too: if the developer keeps the rights and licenses the program to you, the charge is taxable, while contract programming that transfers all rights to you is a nontaxable service. Ask how the contract is written, and confirm with a Texas tax professional. We compare the models, with price ranges, in how much custom software costs.
How do I find the best software development company in Austin?
Skip the "best of" lists. Any firm publishing a ranking puts itself first, and a directory's order doesn't tell you whether a firm fits your project. Use the 12 questions, ask to speak with a client whose project looks like yours, and check whether the case studies show measurable results. And don't rule out a remote team on time zone alone: Honduras stays on Central Standard Time all year, so its workday matches Austin's in winter and runs one hour behind during daylight saving time.
If you're open to a nearshore team in Central America, read how to evaluate nearshore development in Honduras, including the time zone overlap and the risks.
Already stuck with a vendor?
You can get out, though it costs more than prevention. Start by recovering access: repository, servers, domain, and accounts. Then get a technical audit to see what's worth rescuing and what's cheaper to rebuild. It's work we can take on through our cloud, security and operations work. One honest caveat: if you don't have the code or clear rights to it, rebuilding is sometimes the cheaper path.
How does Andes handle ownership?
We hold ourselves to the same list. Depending on scope, we let you choose between full code ownership and a perpetual license, and we explain what each one means before you sign, so the decision is yours. For US clients, the contract and invoicing go through Andes Dev LLC, our sister company in Central Texas. For a Central Texas home builder that chose full ownership, the site runs in the client's own AWS account and the code is 100% theirs (see the case). For an insurance agency, along with the system we delivered a private training site so their team could run it on their own (see the case).
We want clients to stay on the Sidekick model because it adds value every month, not because they're stuck. Ask us the same 12 questions.
Want to know which model fits your project?
We'll review the scope with you, walk you through both options and their costs, and put it in writing before we start. If you already have a system, we'll also check what rights you hold today and whose name your accounts are in. Explore custom software development.
Sources
- U.S. Copyright Office, Circular 30: Works Made for Hire (revised August 2024): https://www.copyright.gov/circs/circ30.pdf
- Honduras Copyright and Related Rights Law, Decree 4-99-E, articles 32 and 33: https://sice.oas.org/int_prop/nat_leg/Honduras/lautor.asp
- 34 Texas Administrative Code §3.308, Computer Programs (Cornell LII): https://www.law.cornell.edu/regulations/texas/34-Tex-Admin-Code-SS-3-308