From the tool your team relies on to a product others pay for
Multi-tenant architecture, subscription billing, roles, dashboards and APIs, built so that your fiftieth customer is as easy to onboard as your first.
SaaS web application development is building software that many customer organisations use through a browser, each paying a recurring subscription and seeing only its own data. We work with founders, often business owners who built a tool for their own operation, who now want to sell it to other businesses.
- Starting from
- ₹1,50,000
- Typical range
- ₹1,50,000 – ₹5,00,000
- Timeline
- 8–16 weeks
What we build
- 01
Tenant isolation
Each customer organisation's data is separated at the database level, so one firm can never see another's records.
- 02
Subscription billing
Plans, trials, upgrades and renewals through Razorpay in India and Stripe or Curlec abroad, with invoices raised automatically.
- 03
Roles and permissions
Owner, manager and staff roles inside every customer account, adjustable by the customer without a developer.
- 04
Self-service onboarding
Sign-up, email or OTP verification, a guided first setup and sample data, so a sales call is optional.
- 05
Founder console
A super-admin view of every tenant, plan, failed payment and usage pattern across the product.
- 06
Customer dashboards
Reports and exports for each customer, plus aggregate figures across all tenants for you.
- 07
APIs and webhooks
Documented endpoints and event notifications so customers can connect your product to their own systems.
- 08
Plan limits
Seats, records or storage capped per plan, with upgrade prompts instead of abrupt failures.
Who this is for
A chartered accountancy practice in Salem built itself a tracker for GST and TDS deadlines across a few hundred clients. It worked well enough that two other CA firms asked to use it. That moment, when a tool built for one business starts attracting others, is where this service begins. The software usually exists in some form already, as spreadsheets, a no-code app or a script someone in the office wrote, and it solves a real problem. Turning it into a product that other firms will pay for every month is a different job from building it for yourself, and the differences decide whether the product survives.
What changes when a tool becomes a product
- Multi-tenancy: every firm that signs up is a tenant whose clients, staff and documents must be invisible to every other tenant. We enforce that in the database itself, with PostgreSQL row-level security or a schema per tenant, instead of trusting every screen to remember a filter. That is what separates genuine multi-tenant software from a single-customer system with extra logins.
- Recurring billing: monthly and annual plans, free trials, mid-cycle upgrades, failed-payment retries and reminder emails. In India that means Razorpay subscriptions on UPI AutoPay or card mandates; abroad, Stripe or Curlec.
- Roles inside each customer: a partner sees everything, an article assistant sees only assigned clients, and each firm decides who is who without asking you.
- Self-service onboarding: a stranger must be able to sign up, verify, import their data and see value without a phone call from your team.
- Dashboards and APIs: customers expect their own reports, and larger ones will ask to connect your product to their accounting or CRM tools.
Billing, tax and hosting in India
Indian buyers of business software are price-conscious and expect to pay by UPI. Recurring debits run on mandates under the RBI e-mandate framework: the customer approves once, is notified before each charge and can cancel from their own UPI app, and your billing logic has to handle all three cleanly. Domestic invoices carry GST, while invoices to overseas customers are usually raised as zero-rated exports under a Letter of Undertaking, which your CA should confirm. Hosting cost grows with usage, so we design for cheap idle tenants: a firm that logs in twice a month should cost you almost nothing to serve.
How the build runs
We follow our usual six-step process with one addition: before any code, we agree the smallest version a second customer would pay for. That usually means setting aside half the wish list and keeping billing, tenancy and the one workflow that made the original tool valuable. Weekly demos run on a staging server holding two dummy tenants, so isolation is tested from the first sprint. The closest work in our portfolio is the CertTulen Academy platform, which handles cart, payments, HRD Corp claims and certificates for learners in India, Malaysia and Singapore; the payment, role and document problems it deals with are the ones a SaaS product meets early.
What a first release costs
A first release with tenancy, subscription billing, roles and one core workflow sits in the same band as a complete management system, ₹1,50,000 to ₹5,00,000, built over 8 to 16 weeks. The biggest drivers are the number of core workflows, integrations with accounting tools, WhatsApp or government portals, any mobile app on top of the web app, and data migration for early customers. A SaaS product never feels finished, so fixed scope matters more here than anywhere: the first release is scoped and priced on its own, and later releases are quoted as they are planned. Our guide to what custom software costs in India gives the wider picture.
When you do not need SaaS yet
If only one or two other firms want your tool, you do not need SaaS yet. Run a separate copy for each, or give them restricted logins to your existing system, and watch whether demand grows. If you have not yet shown that strangers will pay, a no-code prototype or a well-built spreadsheet sold as a service is a cheaper test. Once demand is proven, our account of going from idea to launch in 90 days shows how a first release is built week by week. Build genuine multi-tenant SaaS with VS Tech Builders when you have evidence of demand and good reason to think the tenth customer will look like the first.
CertTulen Academy
A web platform for a Microsoft Training Services Partner — certificates, reports, HRD Corp claims, complete cart with geo-routed payments, and a full learning management backend.
Read the case studyFrequently asked questions
Should each customer have a separate database?
Usually not at the start. A shared database with strict row-level isolation is cheaper to run and simpler to update, and suits products with many small customers. A database per tenant makes sense when customers are large, contractually require physical separation, or need their data held in a particular country. The design can allow a big customer to be moved to its own database later without rewriting the application.
Can customers pay every month by UPI automatically?
Yes, through UPI AutoPay mandates set up with Razorpay. The customer approves the mandate once in their UPI app, receives a notification before each debit, and can pause or revoke it from the same app. Card mandates work in a similar way. Annual plans paid upfront by UPI or bank transfer avoid mandate complications entirely and are worth offering at a discount, since they also help your cash flow.
Who owns the code if the product takes off?
You do, completely. When the final payment for an engagement is made, the source code, database, design files, cloud accounts and documentation are transferred to you, with no royalty, revenue share or licence fee. This matters more for SaaS than for most projects, because investors and acquirers will ask who owns the intellectual property, and the only acceptable answer is your company.
How do we bill customers in Malaysia or Singapore?
Billing sits in its own layer, separate from the core product, so each region can have its own currency, gateway and tax treatment. Curlec handles Malaysian payments, Stripe suits Singapore and other international cards, and Razorpay stays for India. Prices show in the visitor's currency, and the founder console reports revenue by region. Tax registration in those countries is a question for an accountant there.
What belongs in the first version, and what can wait?
The first version needs sign-up, tenant isolation, billing, roles and the single workflow customers are paying for. Custom reports, integrations, white-labelling, a mobile app and a public API can usually wait until paying customers ask for them. Building features nobody has requested is an easy way to spend a SaaS budget before launch, so expect us to question the wish list during discovery.
Related services
- Web DevelopmentDashboards & Reporting
Role-based dashboards built on the data you already hold in billing software, Tally or spreadsheets, with drill-down, exports, WhatsApp alerts and a layout made for the phone.
- Web DevelopmentWeb Portals
Customer, vendor, student and employee portals with OTP logins, document uploads, live status, payments and notifications, connected to the systems you already run.
- Web DevelopmentProgressive Web Apps
Installable web apps with offline support and push notifications, built once for Android, iPhone and desktop, with a straight answer on when a native app would serve you better.
Built for businesses like yours
- Chartered accountant firms
Client documents, the compliance calendar, staff assignments and fee collection in one system, so filing season runs from a screen instead of a whiteboard and a dozen WhatsApp chats.
- Coaching centres
Enquiries, batches, fee instalments, attendance, weekly tests and parent updates on WhatsApp, plus an online test portal for students who practise on their phones.
- Recruitment and manpower agencies
A searchable candidate database, requisition and interview tracking, placement invoices, and attendance and payroll for staff placed at client sites.
Further reading
Planning saas web apps? Get a fixed quote.
Describe your business and the problem in a few lines. We reply within one business day with an honest recommendation, a scope and a fixed price.