Common SaaS types include CRM, ERP, accounting, project management, hosted CMS and ecommerce, communication, HR, and billing applications. These describe the work the software supports. Horizontal and vertical describe its target market; seat-based and usage-based describe how it charges. One product can have all three labels.
Software as a Service (SaaS) delivers access to a provider-operated application. Users may access it through a browser, desktop client, mobile app or API. SaaS is commonly distinguished from infrastructure as a service (IaaS) and platform as a service (PaaS), which leave more of the application stack for the customer to manage.
Pricing may be subscription-based, seat-based, usage-based, transaction-based or a combination. A recurring payment alone does not make software SaaS; the service delivery and operating model matter.
Use the function to define the recurring task, the market to define the buyer, and the pricing unit to test the commercial model. Do not treat those labels as competing product categories.
For founders, SaaS decisions now depend on category, market, and operating model. Compare vertical SaaS vs horizontal SaaS, the SaaS market in KSA, and related enterprise options like cloud ERP software before choosing a product direction. Once the category is clear, the next question is whether the product is showing SaaS product-market fit.
Hapy’s SaaS category lens
We would not choose a SaaS category because it sounds large. We would ask:
- Who owns the urgent pain? A broad horizontal product needs a specific initial customer task. A vertical product needs evidence of an industry-specific need.
- How specific is the workflow? Check which industry rules, records and integrations a general tool cannot support.
- Where does the data live? Identify the system that owns records, approvals, billing and customer communication. Plan how a new product will exchange data with it.
- What makes the product defensible? Test distribution, workflow coverage, integrations and service quality. The category label alone does not prove demand.
What makes an application SaaS?
AWS describes SaaS as provider-operated software delivered over the internet. A SaaS provider operates the hosted application and agreed infrastructure. Customers still configure accounts, access, integrations and data handling, and may need to install or update client software. The division of work depends on the product and contract.
Define shared responsibilities before adoption. The provider should explain its availability, security and recovery commitments; the customer must assign administrators, enforce appropriate permissions, manage users and verify export or recovery needs. Microsoft’s shared responsibility guidance keeps customer data, identities and access under customer responsibility, including with SaaS. The service contract must make the remaining boundaries clear.
Horizontal and vertical SaaS are market choices
Horizontal SaaS addresses a function across industries, such as project coordination. Vertical SaaS focuses on an industry’s workflows, such as property management. Neither category is inherently more successful, affordable or easy to distribute. A horizontal tool faces broad competition; a vertical tool may need deeper domain, integration and support work.
Classify one product on separate axes
A category list is useful only if it explains what the label changes. Record these choices separately before comparing products or defining a new one.
| Classification | Question it answers | Possible labels |
|---|---|---|
| Business function | What recurring work does it support? | CRM, accounting, project management |
| Target market | Does it serve one industry or several? | Vertical or horizontal |
| Customer segment | Who buys and administers it? | Small business, mid-market or enterprise |
| Charging unit | What causes the bill to change? | Seat, workspace, usage, transaction or a combination |
Consider a hypothetical maintenance service for property managers. Its function is work-order management. Its market is vertical because it serves property operations. Its buyer is an operations manager. A price per managed property is a hypothesis to test, not an automatic consequence of being vertical SaaS.
Before choosing that unit, check what a property count includes, how empty properties are treated, and whether support or message costs rise without a matching increase in properties. A seat-based plan might discourage inviting contractors; a property-based plan might underprice a small portfolio with unusually high support needs. Test these possibilities with prospective buyers and realistic cost assumptions. This is a decision example, not a measured customer result.
How category changes the business model
This matrix describes possible commercial patterns for hypothetical products. It is not a statement of current vendor pricing or an industry benchmark.
| Product example | Buyer | Pricing unit to test | Acquisition route to test | Retention and cost considerations |
|---|---|---|---|---|
| Horizontal project tool | Team lead or operations buyer | Active seat or workspace | Self-serve trial and team invitations | Recurring collaboration; support and storage costs |
| Enterprise CRM | Sales leadership with IT/procurement | Seat, edition and implementation | Sales-assisted evaluation | Data quality and workflow adoption; integration and onboarding cost |
| Cloud ERP | Finance/operations executive | Modules, users and deployment scope | Partner or enterprise sales | Operational dependence; migration and support burden |
| Accounting tool | Owner or finance team | Entity, plan and feature tier | Accountant referrals or self-serve | Regular reconciliation; jurisdiction-specific updates |
| Vertical property workflow | Property operator | Unit, location or portfolio | Industry channels and pilots | Daily operational fit; local integration and service needs |
| Usage-based developer service | Developer champion and budget owner | Metered API usage plus commitment | Documentation and technical trial | Reliable integration; infrastructure cost and usage volatility |
| Ecommerce service | Merchant | Subscription plus relevant transaction/service fees | Self-serve setup or agency partner | Merchant success; payment, apps and support economics |
For a hypothetical accounting tool, a monthly subscription is plausible because reconciliation recurs. For a rarely used one-off utility, repeated billing may not fit customer value. Test the value metric, purchasing authority and repeat-use pattern before choosing a plan structure.
Measure acquisition cost against contribution after hosting, third-party services, support and onboarding. For usage pricing, test whether revenue rises with cost and whether customers can predict the bill. For enterprise sales, include implementation and procurement time. Retention should reflect continued value, not merely difficulty exporting data.
Different Types of SaaS Solutions
The following eight groups classify applications by function. They are useful examples, not an exhaustive standard. Products can span more than one group; an ERP may include accounting, and an ecommerce platform may include content and billing features.
1) Customer Relationship Management (CRM) software
CRM software manages customer and prospect records and the work around those relationships. Salesforce’s CRM explanation covers sales, service and marketing uses. A CRM label does not prove that every customer record or integration is included.
CRM systems can serve B2B and B2C organizations. Sales, marketing and service teams use them to manage customer information and workflow. Suitability depends on permissions, data quality, integrations and adoption. Examples to investigate include:
2) Enterprise Resource Planning (ERP) Software
ERP connects business processes such as finance, procurement and supply-chain operations. Cloud ERP is one delivery option; ERP software is not always SaaS.
Check which modules share records and which still need integrations. A broad suite can require substantial migration, configuration and training. A product category does not establish that the selected package covers a particular compliance requirement.
ERP product families to investigate include:
For the wider operating context, compare what an enterprise application does and the main enterprise application categories.
3) Accounting Software
Accounting SaaS supports work such as invoices, bills and reconciliation. Xero’s accounting product illustrates those functions. Payroll, tax support, bank connections and reporting vary by product, plan and jurisdiction.
Check the records your accountant needs, the supported entities and currencies, and the route for correcting an imported transaction. Automated imports still need reconciliation and review.
Examples of accounting software are:
4) Project Management Software
Project-management SaaS coordinates tasks, owners and progress. The useful test is whether the team can see a blocked dependency and decide who must act. A task list alone does not establish resource availability or a reliable delivery forecast.
Project-management services can support both small teams and larger organizations. Evaluate how the tool handles ownership, dependencies, reporting and collaboration for your workflow.
Examples of project-management services are:
5) CMS and E-commerce Platforms
A content management system supports publishing and editing content. An ecommerce platform adds commerce workflows such as catalog and order management. Editors may use visual tools, while custom templates, integrations and migrations can still require technical work.
WordPress.com explains the difference between its hosted service and self-hosted WordPress software, where the site owner or hosting arrangement carries more operational responsibility. Shopify and Webflow are other hosted platforms to investigate for their supported use cases; check the relevant plans and limits.
A hosted CMS can reduce some infrastructure work, but configuration, content quality, access and integrations still need an owner. Cost, maintenance and scalability depend on the platform and workload, and the category does not guarantee SEO performance.
Hosted content and commerce examples include:
6) Communication platforms
Communication SaaS supports conversations through features such as messaging, calls and shared channels. Slack’s feature guide illustrates messaging, collaboration and integrations. Check guest access, retention, notifications and export before making a service the main place for project decisions.
Decide which messages need an accountable owner and a durable record. A conversation can notify a team about a decision without replacing the system that records its approval or final status.
Examples of communication SaaS are:
7) HR/HRM solutions
HR services can help the people responsible for employee and applicant records, whether or not the business has a separate HR department. Define access carefully because those workflows may contain sensitive information.
HR products can cover employee records, leave, recruitment or performance reviews. These are different workflows; a tool that handles one does not necessarily handle payroll or every local employment requirement. Check the selected modules and country coverage.
Before adoption, confirm who can see compensation, applicant records and review notes. Include access removal and data export in the acceptance checks.
Examples cover different scopes: Rippling offers HR software, WorkTango focuses on employee experience, and monday.com is a broader work platform with HR use cases. Do not treat them as interchangeable HR systems.
8) Payment Gateways and Billing Solutions
Payment gateways support payment acceptance. Billing software manages amounts due, invoices or subscriptions. An accounting system records and reconciles the result. A provider may offer several of these functions, but the labels are not interchangeable.
A payment provider can reduce the merchant’s direct handling of card data, depending on the integration. It does not remove the possibility of compromise. Merchants still need secure accounts, correct access, appropriate checkout integration, transaction reconciliation and applicable compliance work.
Check the supported payment methods, countries, settlement and refund behavior for the intended transaction. Do not infer capacity, fraud protection or complete billing support from the gateway label. The business still needs a way to reconcile a payment when the application receives an incomplete or delayed result.
What evidence should the category lead you to check?
Use the product category to choose a realistic trial. In the hypothetical property-maintenance service, ask a requester to create a work order, a contractor to accept it, and an administrator to close and export it. Include a removed contractor and a failed notification. Record who can see each property and who resolves an exception.
The expected evidence is an observable workflow, a clear access boundary, an understandable bill and an export that preserves useful records. These are proposed acceptance checks, not tests Hapy has performed. A successful demonstration of the main screen is insufficient if an important exception still has no owner.
Choose the model around the buyer
Write a short classification for the product: function, market, buyer, charging unit and critical operating constraint. Then use the SaaS product development guide to turn that choice into a bounded first release.
Hapy sells MVP development services. If you need delivery help, bring that classification and the trial evidence to the scope discussion.
