BenjaminSchleier
Blog

SaaS

How to find the right SaaS development partner

Benjamin Schleier · October 6, 2024 · 3 min read

You cannot judge a software project by a development team's hourly rate alone. Who will actually work on it later? How are decisions made? And who takes care of bugs and changes after launch? I would settle these questions before signing anything.

1

The stack matters. Dogma doesn't.

The technology decides how expensive maintenance gets two years from now and how easily you will find developers later. A good team therefore asks about your product first. How many users, what data, and who looks after the software after launch? If someone proposes a language or an architecture in the first meeting, ask for the reason and for the alternatives they ruled out. PriceFeed had to handle large volumes of data, so we chose with that in mind. For a booking portal with a few hundred users, the same choice would be overkill.

2

Experience with similar products

A SaaS application is more than a website with a login. Several customers share one system, and none of them may see the others' data. On top of that come billing, user management and updates rolled out while the system is running. Not every product needs all of that on day one. But your partner should know which of it is coming your way. Ask them to show you a product they built, and ask how customer data is kept apart in it. The answer tells you quickly whether someone has done this before.

3

Some pushback is useful

Be wary of a team that says yes to every feature. Whoever bills by the hour earns money on every line of your wish list. The better partner asks who needs a feature and what happens if it is missing. Sometimes they will suggest dropping half of it and first seeing whether anyone uses the product. That conversation is less comfortable. It saves you from spending half a year on something nobody would have missed.

4

It comes down to the actual team

The agency's most experienced developer often sits in the pitch. Who works on your project afterwards is a different question. Ask it before you sign. Have them give you names, and talk to at least one person who will write your code. Find out how many projects that person works on at the same time. Whether the agency has ten people or two hundred tells you nothing about your three developers.

5

Agree how you will work together

Requirements change, and something always takes longer than planned. That is normal. It becomes a problem when you find out on the delivery date. So agree on a fixed rhythm, ideally a weekly demo of the running software. Add a task list both sides can see, and a named person for when something goes wrong. A team that reports bad news early is worth more than one that always says everything is on track.

6

Maintenance after launch

Launch is where the longer part of the work begins. Security updates arrive, bugs turn up and the first customers have requests. Agree beforehand who handles all that and what it costs. The breakup needs rules too, and the time to set them is while you still get along. Your company should own the repository with the source code, and servers and services should run on your accounts. Then you can switch partners without having to ask for your own product.

  • SaaS
  • Partnership
  • Software
  • Development

Let's talk.

Write me two sentences about what you need. Or pick a time for a 20-minute video call.

What is it about?

I use your details only to reply to you. More in the privacy policy.