SaaS development

It depends on how much product you need before you can charge. A scoped first version sits in a very different range than a platform with several roles and integrations. On the first call I give you a range and the variables that move it, so you decide with numbers and not with a feeling.

A first version that already lets you charge usually takes two to three months. The timeline is set mostly by how much gets left out, and we have that conversation before starting, not halfway through.

The minimum for someone to use it and pay you. Everything else goes on a list and comes later, once users say what is actually missing.

• Signup, login and account management.
• The feature that justifies someone paying.
• Plans and recurring billing working.
• An admin panel so you can operate without asking me for anything.

Usually Stripe, which covers plans, trials, plan changes, failed payments and invoices. If your case calls for another gateway, I integrate that instead. What matters is that billing does not depend on someone checking anything every month.

That is what I recommend almost every time. We build the version that lets you validate and charge, and the product grows from what users ask for. What matters is that the first version does not force you to throw it all away once it works.

You do. The repository, the servers and the service accounts are in your company’s name from day one. No hidden dependencies, no vendor lock-in.

Yes, if you want. I can run maintenance and evolution on a monthly fee, or leave the project documented for your team to continue. You decide, and it can change along the way.

They sit outside the development cost and I tell you about them up front. A small SaaS starts with low infrastructure costs and grows with usage, so the bill normally goes up once you are already charging.