To hire a software development company without getting burned, verify four things before you sign anything: real shipped work you can actually use, a contract that makes you the owner of the code, a transparent process with frequent working demos, and a concrete plan for support after launch. Most horror stories — abandoned projects, surprise invoices, software held hostage — trace back to skipping one of those four checks.
Custom software is not a one-time purchase. It is the start of a working relationship that usually outlasts the build itself, so the vetting you do up front matters more than the pitch deck you are shown.
What Should You Look for in a Portfolio?
A polished website proves a company can market itself, not that it can ship software. Dig one level deeper:
- Ask for live products you can click through, not screenshots or mockups. Anything real should be usable in front of you.
- Look for problems similar in shape to yours — same scale, same kind of workflow — even if the industry is different. A scheduling tool for a clinic and one for a logistics fleet share more DNA than you would think.
- Ask who actually wrote the code. Some firms quietly subcontract the work, which adds a layer between you and the people building your product.
- Ask whether they run any software of their own in production. A team that operates its own systems daily has felt the pain of outages, updates, and support — and builds differently because of it.
- Request two or three references and actually call them. Ask what went wrong, not just what went right.
Who Owns the Code When the Project Ends?
This is where businesses get burned most often. Get the answers in writing:
- The contract should state that the work is done for hire and all intellectual property transfers to you on payment.
- The source code should live in a repository — the version-controlled folder where code is stored, typically on a platform like GitHub — that you can access, ideally under an account your business controls.
- Domains, hosting, databases, and third-party accounts should be registered in your name from day one, not the vendor's.
- Be wary of proprietary frameworks or licensed components that only work if you keep paying that specific vendor. That is a leash, not a feature.
If a company hesitates on any of these, walk away. Ownership questions are only awkward for firms that plan to use lock-in as a retention strategy.
What Does a Good Development Process Look Like?
- Discovery before a quote. Serious firms ask hard questions about your workflows before pricing anything. A confident number in the first meeting is a guess you will pay for later.
- Small milestones with working software every couple of weeks — not a single big reveal at the end.
- A named point of contact who answers you directly.
- A staging environment: a private copy of the software where changes are tested before real users see them.
- Written scope, and a clear process for handling changes to it. Scope will change; the question is whether changes are negotiated openly or buried in overruns.
What Happens After Launch?
Software is never finished. Frameworks get updated, security patches land, browsers change. Before signing, confirm:
- A defined warranty window for fixing defects at no charge.
- Support and maintenance terms agreed up front, not negotiated under pressure after something breaks.
- Documentation and a handover plan good enough that a different developer could take over. That is the real test of whether you own your software.
What Are the Red Flags?
- A firm quote before anyone has asked detailed questions about your business.
- Vague or missing language about code ownership.
- No repository access for you during the build.
- Pressure to sign quickly, or reluctance to provide references.
- Answers that amount to trust us instead of demos you can see.
The honest takeaway: hiring well is mostly about verifying ownership, process, and support before money moves — not about finding the cheapest bid. TradeWeave builds custom software and runs its own production systems every day, so if you want a second opinion on a proposal you have received, we are happy to give one.