A simple calendar change took 11 months. That was the moment a communications manager at a US residential community stopped waiting on her software vendor and started looking for a new one. "When I ask for functionality changes on something very simple, it can take 9 to 12 months," she told us on a discovery call in September 2026.
Her situation is the one most "how to choose a software development partner" guides skip. She has a live product, residents who use it every day, a vendor who holds the code, and a client who pays for all of it. The checks that matter for her are contract-level ones: who holds the keys, what the first paid step costs, and how she leaves if it goes wrong. Below are the 8 checks we would put to any vendor, us included, with the terms we sign on each.
TL;DR: For a product that's already live, choose a software development partner on 8 contract-level checks: comparable live projects, long-running references, a fixed-price first step, repository ownership, milestone payments, a security plan, an SLA and an exit clause. Ask every vendor the same 8 questions in writing. Our first step is a software audit at $5,000 (5 business days) or $9,900 (10 business days), and you keep the written recommendation whether or not you continue with us.
Choosing a partner for a live product is a different decision
The standard checklist is written for a founder with an idea and no code: browse the portfolio, read the Clutch reviews, match the tech stack, compare hourly rates. That works when nothing exists yet. Once customers pay for the product every month, each of those questions changes shape.
The portfolio question becomes "show me a product that kept earning while you changed it." The pricing question becomes "what do I pay before I see working software." And the support question becomes "on what day do I hold the repositories, the hosting and the credentials." A vendor who answers the first version well can still fail all three.
The engagement model is a separate decision, covered in our comparison of a fractional engineer, a freelancer and an agency. For a proptech shortlist, start with our list of proptech software development companies, and read how to choose a proptech software development company for the vertical detail [link: E16].
Run 2 checks on yourself before you shortlist anyone
The first check is whether you need a development partner at all. The same manager drew that line for her own community: "If our site was just basic, if it was information sharing only, I probably would just use a system and build something myself." Bookings, roles, payments and integrations pushed her past it. A page of announcements would not have.
The second check is a needs document in 3 columns: needs to have, nice to have, do not need. Add a screen recording of each workflow that breaks today. A vendor who receives that document can give you a real estimate after one call, and a vendor who still can't is telling you something about how they scope.
If your current vendor is the one leaving, list what you need from them before the last invoice. Our vendor handoff checklist covers it item by item [link: E13].
The 8 checks, with the terms we sign
We asked AI assistants 9 times in October 2026 what to check before signing with a development company for property management software. All 9 answers gave these 8 checks. Below, each one is a question you can send to every vendor on your shortlist, followed by our own answer.
1. Comparable projects: a product that kept trading while the vendor changed it
Ask: "Show me a live product you rebuilt or took over without stopping it." For Lake, a vacation rental marketplace, we replaced the WordPress back end with a Next.js and NestJS application in 3 months, kept WordPress for the homepage, blog and city pages so search traffic held, and connected properties grew from 500 to 40,000 once the property-management sync worked. For CondoGenie, we built a new codebase in 2018 and moved 9 years of users, data and histories across from GeniePad, the platform its founder wrote in 2009.
2. References still in production: clients who stayed for years
Ask: "Which clients have worked with you for more than 3 years, and may I call one?" A client who stays tells you about year 4. CondoGenie has worked with us since 2018 and now serves over 550 condominium and HOA associations and over 80,000 registered users. AreaButler, a German proptech, has had our engineer in its own team since 2022.
"The Brocoders team has fully adapted to our schedule and is always available." <Alexander Timper> Founder and CEO, AreaButler
3. Paid discovery: a fixed-price first step whose output you keep
Ask: "What does the first paid step cost, how long does it take, and what do I keep if I stop there?" Ours is a software audit at a fixed scope. Essential is $5,000 for 5 business days and covers one application on up to 2 repositories, or a stalled build. Standard is $9,900 for 10 business days and covers a production platform on several services or repositories. You keep the written recommendation whether or not you continue with us.
The audit exists because of projects like HeyPractice. In October 2021 we checked its repository and staging before quoting anything, found no backend tests and no setup documentation, and recommended keeping the database and rebuilding the application around it.
4. IP and repository ownership: the keys sit in your accounts
Ask: "On what date do the repositories, hosting and credentials move into accounts I control?" A vendor who can't name a date is holding your product as leverage, whether they mean to or not. On our project takeover engagements, the repositories, hosting and credentials move into your accounts within 5 business days of kickoff.
5. Milestone payments: money follows working software
Ask: "What do I pay before I see something running?" Get the payment schedule in writing, tied to delivered milestones you can test, and compare how much each vendor asks for before the first demo. The smaller that number, the less you risk finding out in month 3 that the team can't deliver.
6. A security plan: who touches production data
Ask: "Where does my production data sit during the work, and who can see it?" Ask for a named access list, a data processing agreement and the rule for copies of production data on developer machines. A live product carries real customer records, so a vague answer here is a reason to stop.
7. An SLA: response times in the contract
Ask: "When production breaks at 2 a.m. on a Saturday, how fast do you respond, and where is that written?" Get the response time in hours, per severity level, in the contract. An SLA that lives only in a sales call won't help you in the incident.
8. An exit clause: how you leave with everything
Ask: "If I end this in month 4, what do I walk away with, and how long is the handover?" If access already sits in your accounts (check 4), the exit question is about people and documentation. Ask for a handover period in writing and for documentation as a deliverable, so the next team starts with notes. Our guide to red flags in an inherited codebase lists what that next team will look for [link: E15].
How one founder chose from 150 vendors
"The main issue was that property pricing and availability data didn't synchronize," says David Ciccarelli, Lake's CEO and founder. He looked at 150 vendors for the fix. The deciding question was one he did not ask.
"He was the only one of 150 vendors who asked to speak with the integration partner that we were working with." <David Ciccarelli> CEO and founder, Lake
Through the build, our team worked directly with the API team at Calry, the middleware between Lake and the property-management systems. "Andrei, Brocoders' CEO, took the most amount of time to understand the problem, and this is really important," Ciccarelli said. Work started on 25 February 2025, and the rebuilt platform went live 3 months later.
Turn it into a ninth check: did the vendor ask to speak with the people your product depends on? Your payment provider, your integration partner, the person who runs support. A vendor who scopes from your spec alone will find those dependencies after you've signed.
What the first 10 business days look like
If you start with us, the first 5 or 10 business days are the audit. Our architects read the code, the repository history and whatever documentation exists, then write down what is complete, what is reusable and what has to be rebuilt. You get that recommendation and a quote for the next step, and you decide with the document in hand.
If you continue, the repositories, hosting and credentials move into your accounts within 5 business days of kickoff, and you get a written report every week. When the audit shows the product needs a rebuild, that work runs as application modernization, with the product live throughout.
Choose the partner whose answers you can hold them to
A good vendor can talk well about process. For a product that's already live, the answers that count are the ones with a date, a price or a number attached, written down before you sign. If you want to see ours on your own code, book the software audit.
Frequently Asked Questions
Put the same 8 questions to every vendor in writing, from comparable live projects to the exit terms. Choose the vendor whose answers carry a date, a price or a named client.
Show me a live product you changed without stopping it. Which clients have stayed more than 3 years? What does the first paid step cost and what do I keep? On what date do I get the repositories and credentials? What do I pay before I see working software? Who can see my production data? What is your response time when production breaks? What do I walk away with if I leave in month 4?
The first step should have a fixed price. Ours is a software audit at $5,000 for 5 business days or $9,900 for 10 business days, and the quote for the takeover or rebuild comes after it, based on what it finds.
If your product only shares information, an off-the-shelf system and some of your own time is usually enough. Once it handles bookings, user roles, payments or integrations with other systems, a custom software development company starts to pay for itself, because each of those breaks in ways a website builder can't fix.
Access should move first. On our takeover engagements the repositories, hosting and credentials move into your accounts within 5 business days of kickoff. At HeyPractice, the audit ran in early October 2021, the contract was signed on 21 October 2021, and 4 engineers were working on the product within the first week.