SaaS
Choosing a SaaS development partner: 6 checks
With Codestep I was the development partner myself, building software for start-ups and established companies. These are the six things I would check before hiring one.
In short
Six checks for assessing a development partner for your SaaS product before you sign anything. Each one comes with questions for the first meeting and a warning sign to watch for. The list runs from the choice of technology through SaaS experience and communication to what happens after launch.
- 1
The stack follows your product
Your tech stack decides how your product scales and how painful maintenance gets two years from now. So run a test. Describe your product and your budget to the team, deliberately name no technology, and see what comes back. A good partner asks about user numbers, data volumes and who will look after the software later, and only then makes a recommendation. PriceFeed had to handle large volumes of data, so we chose with that in mind. For a product with other requirements, we would have decided differently.
Questions to ask
- What questions do you ask me before you propose a technology?
- When would you choose a different stack from your usual one?
- Who will still be able to maintain this stack in two years?
Warning signThe team wants to build everything in its favorite stack, whatever your product actually needs.
- 2
The team has built SaaS before
A SaaS product needs things an ordinary website does not have. Several customers share one system and must not see each other's data. On top of that come billing, user management and updates while the system is running. Ask to see a comparable product the team has built, and ask why for every technical decision.
Questions to ask
- How did you handle data isolation between tenants?
- Which billing system did you integrate?
- How do you deploy without downtime?
Warning signThe answers stay vague. In that case, the team will learn at your expense.
- 3
The partner pushes back
A good partner disagrees with you. They ask who a feature is for and suggest what you could leave out. Try it in the meeting. Put your feature list on the table and ask which parts belong in the first version. If everything gets a yes, the team is thinking about its own utilization.
Questions to ask
- How would you test this idea more cheaply before we build for six months?
- Which feature on my list would you cut?
Warning signEverything gets a yes, and the billing is by the hour.
- 4
You talk to the people who write your code
The experienced people sit in the pitch. Before you sign, ask who will work on your project afterwards, and have them give you names. Talk to at least one person from development. Notice whether they explain things clearly and how much time they will have for you. The size of the agency tells you nothing about that.
Questions to ask
- Who works on my project once the pitch is over?
- Who do I talk to when a technical decision comes up?
- How many projects does that person handle at the same time?
Warning signThe senior developer from the pitch is never seen again after the contract is signed.
- 5
Communication has a set structure
Every software project runs into problems nobody saw coming. What counts is how quickly you hear about them. Agree on weekly demos, a shared task board and a clear escalation path from day one, and put these points in writing, ideally in the contract. In the demo you see running software, every single week. For years I led teams remotely across several time zones, so I know how fast a project without a fixed rhythm goes quiet.
Questions to ask
- How will I find out what is done, what is blocked and where you need my input?
- Who do I turn to when something goes wrong?
Warning signUpdates only come when you ask for them.
- 6
The partnership doesn't end at launch
After launch come feature work, security patches, performance tuning and infrastructure scaling. A new team would first have to understand your entire code base. So clarify before you start how maintenance and further development are billed, and who responds when production goes down. Settle the breakup scenario too. The source code lives in a repository that belongs to you, and access to servers and services is in your company's name.
Questions to ask
- What does our collaboration look like in year two?
- Who owns the repository, servers and accounts?
Warning signLaunch is treated as the end of the project.
I tell the full story behind these six checks in the blog article.
How to find the right SaaS development partner