FININ2MIN · BUSINESS PLAYBOOKS · PCJ-44
Small-business SaaS & Vertical Software
India guide to Small-business SaaS & Vertical Software: business models, setup, conditional approvals, operating steps, cash planning, contracts and practical answers.
General business education, not a permit, signed professional opinion or investment recommendation.
The decision in two minutes
A vertical SaaS business sells a repeatable software outcome to a narrowly defined group of organisations. It differs from a custom automation agency: the product, support model and pricing should remain reusable across customers. A defensible starter scope might solve one scheduling, reconciliation or asset-record problem without holding client funds or making regulated decisions. The model here is a general B2B subscription product, not a fintech, medical-device or surveillance platform.
The opportunity is a costly recurring workflow that buyers will pay to improve. A large software market or successful demo is not evidence of retention, manageable support effort or a profitable product.
Interview 15 organisations in one trade, observe the same recurring workflow with permission and recruit three paid design partners. Deliver a bounded version with an export route and a clear support commitment. Measure actual usage, time saved against an agreed baseline, support hours and willingness to renew without bespoke development for every customer.
Choose the operating model
| Model | Commercial and operating consequence |
|---|---|
| Single-workflow subscription | Narrow scope can improve onboarding and support; prove recurring use before broadening features. |
| Subscription plus implementation | Separate one-time setup from ongoing access, with acceptance and change pricing. |
| Regulated-industry software | Sector rules, professional decisions and customer contracts may add requirements beyond generic software and privacy controls. |
Treat the following programme as a proposed operating design, not as a statutory deadline. Move to a larger scope only when paid demand, competence, authority and cash capacity support it.
From paid pilot to reliable operations
Choose one repeatable buyer problem
Define the user, approving buyer, existing workaround, cost of failure and measurable outcome. Avoid building a broad suite from unrelated feature requests. Write explicit exclusions for regulated advice, money movement and autonomous high-impact decisions. Sell only what the team can maintain after the initial demonstration, including an honest path for customer data export.
Design a responsible data map
Inventory data collected, purpose, access, hosting, subcontractors, retention and deletion. Distinguish the customer’s business records from information needed for your billing and support. Plan privacy and security controls now while matching each statutory obligation to its effective date; the DPDP commencement notification is staged, not an assertion that every duty already applies. MeitY — DPDP Act phased commencement, G.S.R. 843(E)
Build tenant separation and recovery
Use a controlled architecture with least-privilege access, separated customer data, tested backup and a rehearsed recovery process. Keep production credentials out of source repositories and demo accounts. Test restoration with a representative dataset before promising recovery times. Obtain authorised security testing; do not scan customers’ unrelated systems without permission.
Agree product terms and scope
Define features, user or usage limits, support hours, availability commitments, exclusions, data ownership and export format. Separate implementation acceptance from ongoing subscription service. State how price changes, renewals, suspension and refunds work. Do not promise unlimited storage or 24-hour support unless capacity and staffing genuinely support those obligations.
Onboard without uncontrolled migration
Validate a sample export and agree field mapping, duplicate handling and reconciliation with the customer. Keep an auditable import log and retain a rollback option. Let an authorised customer user approve the opening data. Do not silently overwrite disputed balances or represent a migration script as a professional certification of the customer’s records.
Measure active use and support load
Track whether customers complete the target workflow, not merely whether they log in. Categorise tickets as defects, training, configuration or new scope. Give a predictable escalation route and communicate known limitations. Time-box custom requests and assess whether they belong in the common product before committing developer capacity.
Price the cost of serving each segment
Include hosting, messaging, payment processing, third-party licences and support effort in unit economics. Review large customers that consume disproportionate usage. Separate recurring subscription revenue from one-off implementation fees. When annual cash is collected upfront, track the remaining service obligation and avoid counting the full receipt as one month’s recurring revenue.
Operate an incident-response process
Name an incident owner, preserve relevant logs, assess covered regulatory reporting and communicate accurate facts to affected customers. For entities and incidents within the CERT-In directions, the prescribed reporting window needs an operational response, not a wait for a finished forensic report. Use competent security and legal support for scope and follow-up. CERT-In — directions of 28 April 2022, CERT-In — explanatory FAQs, May 2022
Review retention and release quality
Monitor customer cohorts, cancellations, recurring revenue, support cost and failed deployments. Test upgrades before rollout and maintain rollback procedures. A product can add new customers while losing its most valuable accounts; review both logo churn and revenue loss. Do not insert assumed growth into the financial plan to compensate for unmeasured retention.
Scale or exit with portable customer records
Expand only when the same onboarding and support process works repeatedly. Revisit contracts and capacity before entering regulated sectors or adding sensitive data. For closure, give an orderly notice, export period and deletion process, preserve required business records and refund unused commitments where due. Avoid locking customers into an abandoned system.
Permissions, professional scope and evidence
| Decision | What must be established | Record to retain |
|---|---|---|
| Privacy timing and role allocation | Map the data and actual role, then match the relevant DPDP provision to the Gazette’s phased commencement. Contractual and existing legal duties require separate assessment; a future commencement date is not permission to ignore security. MeitY — DPDP Act phased commencement, G.S.R. 843(E) | Record the actual authority, instrument, form, fee basis, applicability reason and completion evidence. |
| CERT-In reporting and system logs | For covered entities, Annexure-I cyber incidents must be reported to CERT-In within six hours of noticing them or being informed of them. Establish the designated point of contact, accurate system time, incident evidence and 180-day rolling ICT-system logs maintained within Indian jurisdiction. Scope an event against Annexure I; customer notification and regulatory reporting are separate workflows. CERT-In — directions of 28 April 2022 | Record the actual authority, instrument, form, fee basis, applicability reason and completion evidence. |
| Sector perimeter | Adding credit decisions, health recommendations, payments or other controlled functions may change the regulatory analysis. Obtain specialist review before launch; calling the product software does not settle the issue. National Single Window System — approval discovery | Record the actual authority, instrument, form, fee basis, applicability reason and completion evidence. |
| Export-of-services evidence | Test all five IGST section 2(6) conditions: supplier in India, recipient outside India, place of supply outside India, qualifying foreign-exchange/RBI-permitted INR receipt, and supplier/recipient not merely establishments of the same person. Keep the contract, recipient/location evidence and payment trail. A foreign billing address or a foreign-currency invoice alone does not satisfy the whole test. CBIC — Circular 202/14/2023–GST, export-of-services payment condition | Record the actual authority, instrument, form, fee basis, applicability reason and completion evidence. |
| Enterprise identity | Use the proper entity and official registration routes where applicable. Udyam registration is not a software security certification, a sector licence or an approval to handle customer funds. Ministry of MSME — official Udyam registration | Record the actual authority, instrument, form, fee basis, applicability reason and completion evidence. |
A commercial process guide does not grant a licence. Complete the actual entity, premises, equipment and jurisdiction facts before deciding whether a form or permission is required. Fees depend on the selected route: record government charges, refundable deposits and professional costs separately; a blank fee is not zero.
Contract terms that protect delivery
- Define product features, usage caps, implementation acceptance and separately priced custom work.
- Allocate data rights, security responsibilities, subprocessors, export and deletion procedures.
- Set measurable support and service-level commitments with realistic exclusions and remedies.
- State renewal, price changes, suspension, cancellation and unused-service treatment.
- Include IP/licence terms and a controlled transition if the product is sold or discontinued.
Use these as negotiation issues, not a pre-signed contract. The final agreement should match the actual parties, governing law and service. Keep the approved version, variations and acceptance evidence together; an informal scope change can alter both cost and responsibility.
Unit economics, funding and the cash trap
The model counts active paying organisation-months, not registered users or free trials. Hosting, licensed APIs and direct support belong in variable cost; product development and a working founder’s salary belong in the stated fixed or initial cash assumptions. Tax capitalisation is not inferred from that grouping. The forecast holds base volume flat and does not model acquisition/churn cohorts or annual prepaid revenue; use the separate cohort record before relying on growth.
| Input/result | Amount or units | Meaning |
|---|---|---|
| Billable monthly output | 100 active paying organisation-months | Accepted output, not enquiries or bookings. |
| Net unit price | ₹5,000 | Illustrative; excludes indirect tax. |
| Variable cost per unit | ₹1,000 | Consistent unit; preserve decimals. |
| Fixed operating cash cost | ₹300,000 | Include working owner remuneration; excludes finance, tax and depreciation. |
| Unit contribution | ₹4,000 | Net price less variable cost. |
| Monthly operating surplus | ₹100,000 | Before collection/payment timing, interest, tax, depreciation and capex. |
| Break-even units | 75 | Rounded up only for the planning threshold. |
| Illustrative capacity | 180 | Not a legal capacity approval. |
Worked calculation: 100 × (₹5,000 − ₹1,000) = ₹400,000 contribution; less ₹300,000 fixed operating cash cost gives ₹100,000.
| Startup use / source | Illustrative INR |
|---|---|
| Equipment / fit-out | ₹900,000 |
| Pre-opening costs | ₹250,000 |
| Refundable business deposits | ₹50,000 |
| Opening stock investment | ₹0 |
| Opening operating reserve | ₹1,200,000 |
| Total opening cash uses | ₹2,400,000 |
| Opening debt | ₹200,000 |
| Initial equity needed | ₹2,200,000 |
The 12-month base illustration has a lowest closing cash balance of ₹1,142,111.11. The stated opening reserve funds this base case. Delayed collections, lower prices or higher costs can still create an additional funding requirement.
Taxes are a separate input. Zero tax cash does not mean exemption. Purchases equal consumed variable costs, opening receivables/payables are zero, and collection/payment delays use whole months. Add actual stock, project milestones, annual-service deferrals and refund schedules before relying on the forecast.
Invoice, tax and accounting decisions
Do not label every overseas subscription an export. Identify the recipient actually receiving the service and the applicable place-of-supply rule, then test all five section 2(6) conditions. Payment must be received in convertible foreign exchange or in INR where RBI permits it; CBIC’s 2023 clarification addresses eligible Special Rupee Vostro settlement. Preserve the agreement, customer/location evidence, invoices and bank trail. Decide registration, LUT/refund procedure and foreign tax exposure separately from this export-definition test. CBIC — Circular 202/14/2023–GST, export-of-services payment condition
Annual cash collection is not twelve months of immediately earned recurring revenue. Separate subscription, implementation and usage fees in the contract and obligation ledger; follow the relevant accounting recognition basis. For taxable services, section 13 can nevertheless bring GST forward to the receipt/invoice timing. Track advance tax cash, remaining service, cancellations, credit notes and payment-processor deductions independently, so a prepaid year does not conceal later support costs. India Code — Central Goods and Services Tax Act, consolidated 11 June 2026
Keep net charges, indirect tax, credit notes, customer withholding and bank deductions separately reconcilable. Select the applicable tax year and current forms; the workbook is not a statutory return. Obtain transaction-specific advice before the first filing. Income Tax Department — e-filing and form navigation, GST portal — registration and filing entry
A difficult decision in practice
An apparently attractive annual contract requires a unique feature, unlimited usage and constant support. Separate the implementation fee from recurring price, estimate support and third-party costs and assess whether the feature harms the common roadmap. A large upfront receipt is not profit when the business must fund a year of service and potential refunds.
Do not cross this boundary
No unlicensed regulated services, covert surveillance, unauthorised access, reuse of client data for unrelated AI training, guaranteed zero downtime or invented security certifications. A payment gateway integration is not authority to hold funds as a payment intermediary.
A practical 30 / 60 / 90-day plan
| Stage | Business-specific action | Exit evidence |
|---|---|---|
| Days 1–30: validate | Interview 15 organisations in one trade, observe the same recurring workflow with permission and recruit three paid design partners. Deliver a bounded version with an export route and a clear support commitment. Measure actual usage, time saved against an agreed baseline, support hours and willingness to renew without bespoke development for every customer. | Approved scope and actual paid-demand evidence; required permissions before operation. |
| Days 31–60: deliver a controlled cycle | Complete agree product terms and scope, onboard without uncontrolled migration and price the cost of serving each segment. Use the working records to compare accepted output, cost and customer approval. | A reconciled accepted job/contract and documented exceptions. |
| Days 61–90: decide the next commitment | Review paying organisations completing the target workflow and restoration tests and unresolved high-risk defects. Apply the adverse cash scenarios before expanding staff, assets or stock. | A written go, revise or stop decision with funded obligations. |
These dates are planning targets, not government processing promises. Required permissions and safety conditions take precedence over a launch date.
Operating scorecard and launch checks
- Paying organisations completing the target workflow
- Gross revenue retention before expansion
- Support hours and cloud cost per active organisation
- Implementation-to-first-value time
- Restoration tests and unresolved high-risk defects
0 of 10 launch decisions reviewed.
The checklist operates in this page session only; no response is submitted or stored on the Finin2min server. Save the working records in your own secure system.
Closure, transfer and unresolved obligations
Export customer data in agreed usable formats, provide a tested transition window, reconcile unused subscriptions and delete copies according to lawful retention and contract requirements. Revoke credentials, close subcontractor access and preserve necessary tax, incident and dispute records. A product acquisition must address data transfer and continuing obligations rather than treating customer records as unrestricted inventory.
Questions founders and operators ask
24 questions available
How is this different from an AI automation agency?
A SaaS product should serve multiple customers through a reusable product and support model. An agency may deliver bespoke workflows and projects. Keep custom implementation separately priced, and test whether each new customer needs expensive unique development. Calling project work a subscription does not make its economics repeatable.
What should the first paid product solve?
One recurring, costly workflow for a clearly defined buyer. Observe the current process with permission, agree an outcome and recruit a few paid design partners. Avoid building a broad feature list before proving actual use and renewal. A successful demonstration is not evidence of sustained customer value.
Should I offer a free trial or a paid pilot?
A trial can test usability, while a paid pilot tests willingness to pay and the buying process. Define limits, support and data handling for either approach. Measure conversion to a sustainable contract, not registrations alone. Do not use sensitive customer data in an unsecured prototype to make the demonstration more impressive.
How should implementation fees be separated?
Define the setup deliverable, migration, training and acceptance independently from recurring access. Price custom work through a change process. This prevents a low subscription from hiding a large implementation loss and helps the customer understand what remains available after setup. Accounting and tax timing still require actual analysis.
What is the most useful retention measure?
Review paying customer cohorts and gross recurring revenue retained before expansion, alongside actual workflow use. A flat customer count can hide valuable customers leaving and smaller ones arriving. Track cancellations, downgrade reasons and support burden. The workbook’s flat-volume base is not a prediction that churn will be zero.
Can annual subscriptions be treated as monthly profit immediately?
The cash receipt and the period of service are different. Maintain the remaining service obligation and refund exposure under the contract and applicable accounting. Do not inflate monthly recurring revenue with a whole annual receipt. The base cash model does not assume annual advances fund operations.
How should usage-heavy customers be priced?
Measure hosting, API, messaging, storage and support costs by segment, then define transparent usage limits or tiers. Warn customers before overage charges and avoid surprising bills. A large customer paying the same flat fee can be less profitable than several small ones if it consumes most of the infrastructure and support.
What data should the product collect?
Only what is needed for the stated service, billing, security and other lawful purposes. Map access, vendors, retention and deletion. Distinguish customer records from your own business data. Match specific privacy obligations to their effective dates rather than describing all DPDP provisions as already operational. MeitY — DPDP Act phased commencement, G.S.R. 843(E)
Is choosing an Indian cloud region enough for compliance?
No single hosting choice settles all contractual, sector, security or privacy obligations. Assess actual data, processing roles, access, transfers and customer requirements. A cloud provider’s certification does not automatically certify your application or configuration. Record the decision and its scope without making a blanket compliance claim.
Can customer data be used to train an AI feature?
Do not assume permission from a general subscription contract. Assess the specific purpose, rights, data sensitivity, legal basis and customer commitments before any reuse. Prefer appropriately authorised or synthetic development data. Keep an auditable decision and do not quietly send production records to an external AI service.
What should a service-level agreement promise?
Measurable availability, support response and recovery commitments that the team can actually meet, with clear exclusions, reporting and remedies. Test backup restoration before promising recovery times. Distinguish a response target from a guaranteed resolution time. Unlimited support wording is risky when the product is staffed by a small team.
How should customer migration be accepted?
Agree field mapping and reconciliation rules, test a sample, preserve a rollback path and have an authorised customer user approve the result. Record exceptions rather than silently changing disputed values. A successful import means the agreed transfer worked; it is not a professional certification that the source records were correct.
What is the response to a serious cyber incident?
Contain the incident through competent procedures, preserve evidence and activate the named response owner. For covered entities and Annexure-I incidents, CERT-In requires reporting within six hours of noticing or being informed; do not wait for a complete forensic report. Keep contractual customer notices separate. Maintain the required point of contact, time synchronisation and 180-day system-log arrangements. CERT-In — directions of 28 April 2022
Can a founder promise that the product is completely secure?
Avoid an absolute guarantee. Describe actual controls, testing scope, known limitations and incident processes accurately. Independent testing or certification should be named only when genuinely obtained and relevant. Security is an ongoing operational responsibility, not a one-time marketing badge.
Should regulated features be added to win a large client?
Review the actual function before committing. Credit decisions, payments, medical recommendations and other controlled activities can change obligations and professional responsibilities. A client contract does not itself authorise the provider. Price the necessary specialist work and reject scope that the business cannot lawfully or competently support.
How are customer funds different from subscription payments?
Receiving payment for your own service does not automatically authorise holding or settling money for third parties. Design the flow with appropriate regulated providers where needed and obtain specialist advice for the actual role. Do not describe a payment-gateway integration as a universal financial-services approval.
Which costs are often hidden in SaaS margins?
Onboarding, customer support, incident response, licensed APIs, payment fees, failed collections, refunds, security work and a working founder’s salary. Separate recurring cost from one-time development, but do not assume tax capitalisation from that split. Review costs per active paying organisation, not per registered account.
Does a foreign SaaS customer automatically make the subscription an export?
No. Check the supplier and recipient locations, the place of supply, qualifying receipt of payment and the rule that the parties are not merely establishments of the same person. All five section 2(6) tests matter. An overseas email address or USD invoice alone is insufficient; preserve the actual customer, contract and bank evidence. CBIC — Circular 202/14/2023–GST, export-of-services payment condition
What should the customer export contain?
The agreed business records in a usable documented format, with identifiers, relationships and relevant attachments needed for migration. Test that an authorised customer can open and reconcile the export. State exclusions transparently. An export button that produces incomplete or unreadable files is not a credible exit route.
What happens if the product closes?
Give an orderly notice, maintain a realistic export window, settle unused commitments and close vendor access. Preserve necessary tax, incident and dispute records while deleting customer copies according to lawful requirements and contract. Do not abandon customers in a locked system or sell their data as an unrestricted asset.
How does the PCJ-44 illustrative contribution calculation work?
At 100 active paying organisation-months per month, net price ₹5,000 less variable cost ₹1,000 gives ₹4,000 per unit. Multiplying by 100 gives ₹400,000 contribution; subtracting ₹300,000 fixed operating cash cost leaves ₹100,000 before interest, tax, depreciation and capital spending. These are original assumptions, not current market quotations or promised earnings.
What is the illustrative break-even point for small-business saas & vertical software?
Fixed operating cash cost ₹300,000 divided by unit contribution ₹4,000 requires 75 equivalent units, rounded up. Compare that with the assumed monthly saleable capacity of 180. The workbook displays NOT VIABLE rather than zero break-even when contribution is non-positive. This operating break-even excludes debt service and tax; cash break-even needs the full forecast.
How much opening funding does the PCJ-44 example require?
The assumptions are ₹900,000 equipment/fit-out, ₹250,000 pre-opening cost, ₹50,000 business deposits, ₹0 opening stock and ₹1,200,000 operating cash. Total initial uses are ₹2,400,000. With ₹200,000 assumed opening debt, initial equity is ₹2,200,000. Later forecast deficits are additional needs; neither customer deposits nor unapproved subsidies are included.
How should I stress-test cash before committing to small-business saas & vertical software?
Reduce accepted volume and net price, increase direct and fixed costs, and delay credit collections independently before combining the shocks. The base assumes 30% of revenue on credit and a 1-month collection lag; replace both with actual contract evidence. Enter tax cash and later capex explicitly. A zero tax default is unresolved, not an exemption, and the model does not automatically borrow to eliminate a shortfall.
Editable working records
Twelve CSV records and a specialist-review brief are included for this business. These are original operating templates, not government-prescribed forms or pre-approved legal documents. Keep completed customer information private.
Official sources and authority routes
MeitY — DPDP Act phased commencement, G.S.R. 843(E)
Different provision groups commence immediately, after one year and after eighteen months from Gazette publication. Match the specific duty and date.
Read the official document or authority guidance
CERT-In — directions of 28 April 2022
Covered entity/incident reporting, coordination and logging duties. Apply the actual scope and later clarifications.
Read the official document or authority guidance
CERT-In — explanatory FAQs, May 2022
Explanation of the cyber-security directions, read with the directions rather than as a separate amendment.
Read the official document or authority guidance
National Single Window System — approval discovery
Identify Central/State authority routes. Confirm municipal and activity-specific requirements with the competent authority.
Read the official document or authority guidance
Income Tax Department — e-filing and form navigation
Select the tax year and operative form/provision; portal distinguishes earlier-year dues and Tax Year 2026–27 onward.
Read the official document or authority guidance
Ministry of MSME — official Udyam registration
Official free registration route. An enterprise registration is not a sector operating permit.
Read the official document or authority guidance
CBIC — Circular 202/14/2023–GST, export-of-services payment condition
Reproduces the five IGST section 2(6) export tests and clarifies eligible INR settlement through Special Rupee Vostro Accounts, subject to RBI/FTP conditions.
Read the official document or authority guidance
India Code — Central Goods and Services Tax Act, consolidated 11 June 2026
Scoped provisions on deposits as consideration, composite/mixed supplies, service time of supply, blocked gift credit and retention of the registered person’s own GST records. Apply notifications and the actual transaction separately.
Read the official document or authority guidance
GST portal — registration and filing entry
Official transactional entry; use the applicable notification/rule for actual classification, registration, credits and liability.
Read the official document or authority guidance
Apply the document to the actual activity, jurisdiction and date. A directory identifies the responsible authority; it does not grant an approval. Commercial examples are illustrative Finin2min analysis.