Building a SaaS product without a full engineering team?

What should a first SaaS version actually include?

Enough to charge for, and no more. In practice that's authentication, one core workflow done properly, billing, and the admin view you need to support customers.

Everything else - teams, integrations, granular permissions, analytics - is easier to add once real users have told you which of them they actually want. Most roadmaps written before launch are rewritten after it.

How do you handle subscriptions and billing?

Stripe for most products: subscriptions, trials, proration, invoices, failed-payment recovery and the webhook handling that keeps your database honest when payments change state.

Billing is where teams underestimate the work. The happy path takes a day; the edge cases - a card failing mid-cycle, a plan changing halfway through a month - are the part that takes real care.

Will it scale?

Products rarely break under traffic. They break under revision - the fourth feature the data model never anticipated, the integration wired straight into the interface.

So the effort goes into boundaries: a data model that tolerates new features, service edges that can be split later, and a multi-tenancy decision made deliberately on day one rather than discovered on day three hundred.

Do you build CRM software for real estate?

Yes, and it is work we have already shipped. PropDesk is a white-label property platform where each real estate agency gets its own branded site, a private admin portal and a subscription plan. Every agency's data is isolated, so one agency can never see another's leads.

The centre of a real estate CRM is the lead pipeline. PropDesk tracks each enquiry through nine stages and records where it came from, whether that was a web form, WhatsApp, a call or a chatbot. That source tracking is what tells an agency which channel is worth paying for.

If you run or serve real estate businesses in Ahmedabad, Gujarat or elsewhere in India, we can build a CRM shaped around how your team actually works, rather than asking your team to adapt to a generic tool.

What does the engagement look like?

Two-week sprints against a live staging environment you can use yourself. You see real progress each fortnight rather than a status document.

At handover you get the code, the infrastructure as code, the deployment pipeline, the runbook and every account. Bringing it in-house later should be a decision, not a negotiation.