SaaSCron: Business Software

Project management SaaS: types, pricing models and how to choose one

2026-10-31T17:00:00-04:00

You run projects in a spreadsheet and a chat thread, and deadlines slip because nobody can see who is doing what. A project management tool fixes that only if you pick the kind that matches how your team works, at a price that still makes sense when the team grows. Every tool here is rented as a subscription, the model explained in What is SaaS?.

This guide maps the four kinds of project management software, shows how free tiers, seat minimums and billing terms change what you pay, and ends with a checklist for your trial. Vendor figures come from the vendors’ own pages, checked in October 2026. For a general method to compare vendors, see How to evaluate SaaS solutions.

Project management software in plain terms

Think of the ticket rail in a restaurant kitchen. Each order is pinned in a row, moved along as the dish is prepared and taken down when it leaves the pass. Anyone in the kitchen can see what is waiting, what is cooking and what is late.

A project management tool is that rail for office work. Each task is a ticket with an owner, a due date and a status. The tool shows the same tasks in different views: a list, a board with a column per status, or a calendar. A timeline, often called a Gantt chart, draws tasks as bars across dates so you can see which ones depend on others.

The four kinds

Kind	Built for	What it adds	Watch for
Task management	Small teams with simple to-dos	Lists, boards, due dates, comments	Outgrowing it once projects depend on each other
Agile and software delivery	Development teams working in sprints	Backlogs, sprint boards, links to code	Too rigid for non-technical teams
Work management	Several departments sharing one tool	Custom fields, automations, many views	Setup time; someone has to own the templates
Portfolio management	Leaders tracking many projects at once	Roll-ups across projects, goals, capacity	Price; usually on the top tiers only

Most products cover more than one row, and the vendors use the labels loosely. Decide which row is your main need, then check that the tier you can afford includes it. Asana, for example, lists “Timeline and Gantt views” on its Starter plan, while “Unlimited portfolios” and “Goals” appear on Advanced.

How the price is built

Asana and monday.com both price per user (seat) per month. Three details move the bill:

Free-tier limits. Asana’s free Personal plan is limited to 2 users. Jira’s Free plan allows up to 10 users. monday.com’s free plan allows up to 2 seats and up to 3 boards.
Seat minimums. monday.com says its paid plans start at 3 seats, so a 2-person team on a paid plan pays for 3.
Billing terms. Asana lists Starter at $10.99 per user per month billed annually and $13.49 billed monthly. Advanced is $24.99 annually and $30.49 monthly.

Example: a 12-person team chooses Asana Starter, then considers Advanced for portfolios.

Starter, billed annually: 12 x $10.99 = $131.88 a month, or $131.88 x 12 = $1,582.56 a year.
Starter, billed monthly: 12 x $13.49 = $161.88 a month, or $161.88 x 12 = $1,942.56 a year.
Cost of monthly billing: $1,942.56 - $1,582.56 = $360.00 a year, which is $360.00 / $1,582.56 = 22.7% more than annual.
Advanced, billed annually: 12 x $24.99 = $299.88 a month, or $299.88 x 12 = $3,598.56 a year.
Cost of the upgrade: $3,598.56 - $1,582.56 = $2,016.00 a year, or $2,016.00 / 12 = $168.00 per person per year.

The upgrade question then becomes concrete: is a portfolio view worth $168 per person per year to your team? If only 2 managers need it, ask the vendor whether a workspace can mix tiers before you upgrade everyone.

Monthly billing makes sense while you are still deciding. Once the tool has survived a quarter of real use, annual billing costs $360 a year less for the same 12 seats.

Checklist

Run this during the trial, with real work, not a demo project:

Your main kind of work (from the table) is covered on the tier you can afford.
Two people outside the project lead can create, assign and close tasks without help.
The views your team uses most, such as board and timeline, are on that tier.
You know the free-tier user limit and what happens when you pass it.
You know the seat minimum and whether guests or viewers need paid seats.
The tool connects to your chat, calendar and file storage.
You can export all tasks, comments and attachments in a usable format.
Single sign-on and user provisioning are available on your tier, if your company needs them.
You have priced the next tier up for the whole team, not only for one feature.
One person owns templates, statuses and fields after rollout.

Asana, for example, lists SAML sign-in and SCIM user provisioning on its Enterprise plan. For how to run the rollout once you pick, see SaaS implementation.

Common mistakes

Choosing by feature list, not by workflow. A tool with every view still fails if the team works in sprints and the tool thinks in projects. Why it happens: comparison pages count features. Instead: pick the row of the table that matches your main work first.
Paying monthly after the decision is made. In the example, monthly billing costs $360 a year more for 12 people. Why it happens: nobody revisits the plan after the trial. Instead: switch to annual billing once the tool has survived a quarter.
Planning around the free tier. Asana’s free plan stops at 2 users and Jira’s at 10, and teams grow during projects. Why it happens: free feels like a trial without an end date. Instead: price the paid tier for your expected headcount in a year before you invite everyone.
Letting everyone design statuses and fields. Ten people create ten ways to say “blocked”, and reports stop making sense. Why it happens: work management tools make customizing easy. Instead: name one owner for templates and statuses. For how seat licenses are counted at renewal, see SaaS licensing.

Sources

Asana, Pricing, checked October 2026.
Atlassian, Explore Jira Cloud plans, checked October 2026.
monday.com, Pricing, checked October 2026.

In three sentences

Project management SaaS comes in four kinds, task, agile, work and portfolio management, and the right one depends on how your team works more than on the feature count. Free-tier limits, seat minimums and billing terms move the price: 12 people on Asana Starter pay $1,582.56 a year billed annually, $360 more billed monthly and $2,016 more on Advanced. Trial the tool with real work, price the next tier for the whole team and name one owner for templates before you roll it out.

SaaS analytics: cloud BI tools and analytics for your own SaaS product

2026-10-30T12:00:00-04:00

You searched for SaaS analytics and found two kinds of answers: business intelligence tools you rent in the cloud, and dashboards that show a SaaS company how its own product is doing. Both are real, and your company probably needs a bit of each. The same pipeline sits behind both, and the cost surprises come from the same places. If SaaS itself is new to you, start with What is SaaS?.

The first meaning is cloud BI: tools such as Microsoft Power BI or Google BigQuery that you use as a service to analyze your company’s data. The second is product analytics for a SaaS business: the numbers that tell you whether customers use, keep and expand what they pay for. This guide covers the pipeline, prices a small BI rollout and lists the product metrics worth tracking.

The analytics pipeline in plain terms

Think of a restaurant kitchen. Deliveries arrive from several suppliers and go into one pantry, and the cooks plate dishes from what is in the pantry. Nobody cooks straight off the delivery truck.

Each part of a data pipeline has a kitchen equivalent:

Sources are the deliveries: your app database, billing system, CRM and help desk.
ELT (extract, load, transform) is the delivery route. You copy raw data out of each source, load it into one store, then clean and join it there. Its older cousin, ETL, transforms the data before loading it.
The data warehouse is the pantry: a database built for large analytical queries rather than for running an app.
The BI layer is the plating: the dashboards and reports people actually read.

Small teams sometimes skip the warehouse and point a BI tool straight at the app database. That works until a heavy report slows down the app your customers are using.

Meaning 1: cloud BI bought as SaaS

Cloud BI tools follow the SaaS pattern: subscriptions, a browser interface and servers the vendor runs. Two pricing shapes are common, and many companies pay both.

Per seat for the BI layer. Microsoft lists Power BI Pro at $14.00 per user per month and Premium Per User at $24.00, both paid yearly. A free account can build reports but must upgrade to share them.
Per use for the warehouse. Google’s BigQuery charges by the data your queries process. Its free tier covers 1 TiB of processed query data a month. Its sandbox adds a lifetime 10 GiB of storage, with tables that expire after 60 days.

Prices and limits are from Microsoft’s and Google’s own pages, checked in October 2026.

Example: a 12-person company wants one shared sales dashboard on Power BI, with data in BigQuery. Assume all 12 people need a Pro license to work with shared reports; check Microsoft’s licensing terms for your own setup.

Seats: 12 x $14.00 = $168.00 a month.
A year, paid yearly: $168.00 x 12 = $2,016.
Queries: the dashboard refreshes scan 25 GiB a day. Over a 30-day month that is 25 x 30 = 750 GiB.
Free allowance: 1 TiB is 1,024 GiB, so 750 / 1,024 = 73% of the monthly free compute.
Now the team adds hourly refreshes and scans 50 GiB a day: 50 x 30 = 1,500 GiB, which is 1,500 - 1,024 = 476 GiB above the free tier, billed at the on-demand rate on Google’s pricing page.

The seat line is predictable; the query line is not. More frequent refreshes doubled the scanned data without anyone adding a user.

Meaning 2: analytics for your own SaaS product

If you run a SaaS product, your questions are about accounts, not sales regions. These five metrics cover most of them:

Metric	Question it answers	Where the data lives
Activation rate	Do new sign-ups reach the first useful outcome?	Product events
Active accounts, weekly or monthly	Is the product used, not just paid for?	Product events, per account
Feature adoption	Which features do paying accounts use?	Events tagged by feature and plan
MRR and churn	Is recurring revenue growing, and who leaves?	Billing system
Net revenue retention	Do existing customers spend more over time?	Billing, by cohort

The first three rows live in product events and the last two in billing. The useful answers come from joining them, and that join is the main reason to have a warehouse. For the retention formulas, see NDR and GRR in SaaS.

Example (hypothetical): in one month, 400 accounts sign up for a trial. Of those, 140 reach the first useful outcome, such as sending a first invoice.

Activation rate: 140 / 400 = 35%.
Of the 140 activated accounts, 20% pay after the trial: 140 x 20% = 28 customers.
Of the 400 - 140 = 260 that never activate, 2% pay: 260 x 2% = 5.2, so about 5 customers.
Total: 28 + 5 = 33 new customers from 400 trials, or 8.25%.
Raise activation to 45% (180 accounts): 180 x 20% = 36, plus 220 x 2% = 4.4, about 4, for 40 customers.

Ten more points of activation adds 7 customers a month without one more sign-up. That is the kind of answer you get only when product events and billing sit in the same place.

Choosing the pieces

Your stage	Reasonable setup
A few sources, standard reports	One BI tool with built-in connectors
Billing and product data need joining	Add a warehouse and an ELT tool
Several teams build their own dashboards	Add shared metric definitions owned by one person

An ELT tool that copies data out of your other SaaS tools goes through their APIs, so their rate limits and sync schedules apply. See SaaS integration for that arithmetic.

Common mistakes

Reporting straight from the production database. A heavy query slows the app for paying customers. Why it happens: the data is already there and a warehouse feels like overhead. Instead: copy data to a warehouse, or at least to a read-only replica, before the first big report.
Two definitions of “active”. Sales counts logins, product counts actions, and the numbers never match. Why it happens: each team defines the metric in its own tool. Instead: write one definition per metric and use it in every dashboard.
Tracking every click without a plan. Thousands of unnamed events, and nobody can find the one that matters. Why it happens: tracking everything feels safe. Instead: list the questions first, then the events that answer them, with a naming rule.
Forgetting that refreshes cost money. Hourly refreshes on a usage-priced warehouse multiply the scanned data, as the example shows. Why it happens: the seat price is the only cost on the purchase order. Instead: set refresh schedules per dashboard and review the query bill monthly.

Sources

Microsoft, Power BI pricing, checked October 2026.
Google Cloud, BigQuery sandbox and BigQuery pricing, checked October 2026.

In three sentences

SaaS analytics means two things: BI tools you rent as a service, and the product metrics a SaaS company tracks about its own customers. In the example, 12 Power BI Pro seats cost a predictable $2,016 a year, while doubling dashboard refreshes pushed BigQuery queries past the free 1 TiB a month. Define each metric once, keep reports off the production database and join product events with billing, because that join shows which customers stay.

E-commerce SaaS: hosted platforms vs open source vs headless

2026-10-23T17:00:00-04:00

You want to sell online, or your current store has outgrown its setup, and every agency you ask recommends a different platform. You need to know what you are really choosing between and what each choice costs once the work is counted. There are three models: a hosted e-commerce SaaS platform, self-hosted open-source software, or headless commerce, where a separate front end sits on top of a commerce back end.

The choice decides who keeps the store running at 2 a.m. on a sale day, and that cost can be larger than the license fee. This guide explains the three models, works through a three-year cost comparison and ends with a decision table by store size. If SaaS is new to you, start with What is SaaS?.

The three models in plain terms

Think of it like opening a shop. You can rent a unit in a shopping mall: the mall handles security, cleaning and the electricity, and you follow its rules on signs and opening hours. You can buy a building and run it yourself: no landlord, but the roof is your problem. Or you can rent the mall’s stockroom and checkout and build your own storefront next door, designed exactly as you want.

Hosted e-commerce SaaS is the mall unit. The vendor runs the software, the servers, security updates and checkout. You pick a theme, add products and pay a monthly fee. Shopify is one example.
Self-hosted open source is the building you own. The software is free to download and change, and you or your developer run the hosting, updates and security. WooCommerce describes itself as “the world’s top open-source platform”, “powered by WordPress”, with no “monthly platform fees” (WooCommerce). Hosting is a separate bill.
Headless commerce is the custom storefront. Shopify’s developer documentation puts it in one line: “Headless commerce separates your storefront’s frontend from its backend” (Shopify, headless). The back end still handles products, cart and checkout; your developers build everything the customer sees.

How each model works in practice

Hosted SaaS. You pay a subscription, usually in tiers, and buy extra functions as apps from the vendor’s marketplace. Payment processing is charged per transaction. The vendor ships new features to every store at once. You cannot change the core code, so anything the platform and its apps do not support is hard to add. That marketplace model is what makes a product a platform, as What is a SaaS platform? explains.

Self-hosted open source. The license costs nothing, but nothing else is free. You choose a host, install the software, add extensions, apply security updates and fix what breaks. You can change anything, because you hold the code. The real cost is developer time, every month, for as long as the store runs.

Headless. The commerce engine can be a SaaS back end or an open-source one. On Shopify, the Storefront API “serves products, collections, search, and the cart, and hands customers off to checkout”. Hydrogen is “Shopify’s headless toolkit” and Oxygen is “Shopify’s hosting for Hydrogen storefronts”. Shopify’s own page states that a headless storefront “costs more to build and run than a theme”. You get full control of speed and design, and a front end that needs a development team.

Worked example: three years of running costs

Platform prices change often and differ by region, so this example uses labeled assumptions, not any vendor’s price list. Replace each line with the quotes you receive.

Example: a labeled hypothetical. A store with about 2,000 products and steady sales compares three years of costs. Payment processing is left out, because it applies to all three models at similar rates. Developer time is priced at $75 an hour.

Cost line (assumed)	Hosted SaaS	Self-hosted open source	Headless
Platform or license fee	$100 a month	$0	$100 a month (SaaS back end)
Hosting	included	$80 a month	$50 a month
Apps or extensions	$150 a month	$100 a month	$150 a month
Developer upkeep	none	8 hours x $75 = $600 a month	20 hours x $75 = $1,500 a month
Monthly running cost	$250	$780	$1,800
Three years of running	$250 x 36 = $9,000	$780 x 36 = $28,080	$1,800 x 36 = $64,800
One-time build (assumed)	$3,000	$8,000	$40,000
Three-year total	$12,000	$36,080	$104,800

Read the developer row first. The license fee is the smallest line in the self-hosted column, and labor is 77% of its running cost ($600 / $780). In the headless column, labor is 83% ($1,500 / $1,800). The hosted platform looks expensive only if you compare license fees and ignore people.

The comparison turns when the store needs something the hosted platform cannot do. If a custom checkout step or a product configurator would add sales worth more than the extra cost, the open or headless model pays for itself. Put that number on paper too, before you switch.

Decision table by store size

The table is a starting point, built from the trade-offs above. Your catalog, your team and your sales plan decide the final answer.

Store stage	Usually fits	Why	Watch for
First store, one or two people	Hosted SaaS	No servers, no developer, fast launch	App fees that add up month by month
Growing store, small team, standard needs	Hosted SaaS on a higher tier	Same platform, more staff accounts and reports	Features you cannot add without code
Unusual products or processes, a developer on hand	Self-hosted open source	Full control of the code and the data	Security updates and downtime are yours
Large brand, in-house developers, design and speed matter	Headless	Custom front end, any framework	Two systems to run and a team to keep

Moving between rows is possible but slow. A store migration touches products, customers, order history, URLs and search rankings. Choose the row you expect to be in for the next three years, not the one you are in today.

Common mistakes

Comparing license fees instead of total cost. The free license looks cheapest until developer hours are added; in the example, they are 77% of the open-source running cost. Why it happens: the license is the only number on the download page. Instead: price three years, including people, as in the table.
Going headless for speed alone. A custom front end can be fast, but so can a light theme on a hosted platform. Why it happens: headless is sold on performance. Instead: go headless when you need a design or experience a theme cannot deliver, and have the team to run it.
Installing apps without a budget. Each app adds a monthly fee and code that runs on your pages. Why it happens: apps fix problems in minutes. Instead: list every app with its monthly cost, and review the list every quarter.
Ignoring the exit. Product data, customer accounts and order history must move with you if you change platforms. Why it happens: nobody plans a move on day one. Instead: test a full export from the platform before you commit, and keep URL redirects in the migration plan.

For how monthly fees, tiers and usage charges are built, see SaaS pricing models.

Sources

WooCommerce, product page, checked October 2026.
Shopify, Headless commerce developer documentation, checked October 2026.

In three sentences

You can run an online store on a hosted e-commerce SaaS platform, on self-hosted open-source software or on a headless setup with a custom front end over a commerce back end. In the labeled example, three years cost $12,000 hosted, $36,080 self-hosted and $104,800 headless, and developer time is most of the difference. Start hosted unless you need something the platform cannot do, and price people, apps and the exit before you choose.

HRMS SaaS: what cloud HR software covers and how to evaluate it

2026-10-21T12:00:00-04:00

Your company just passed 20 employees. Onboarding runs on email and a shared folder, time-off requests live in a chat thread, and someone asked last week where the signed Form I-9 for a new hire is filed. You have been asked to find HR software, and every vendor’s page claims to do everything.

An HRMS (human resource management system) is software that holds your employee records and runs the HR processes built on them: hiring, onboarding, time off, payroll data, performance and offboarding. As SaaS, the vendor hosts and updates it, and you rent it per employee. If SaaS itself is new to you, start with What is SaaS?.

An HRMS in plain terms

Think of a school’s front office. It keeps one file per student, a calendar of absences and a drawer of forms for enrollment, field trips and transfers. When a student leaves, the office knows which papers to keep and for how long. An HRMS is that front office for your employees, with the forms filled in online and the calendar shared with every manager.

Vendors use three names for overlapping products, and the boundaries are loose:

HRIS (human resource information system): the core database of employees, jobs and pay, with reports.
HRMS: the database plus processes such as onboarding, time off and performance reviews.
HCM (human capital management): the widest label, usually adding recruiting, talent and workforce planning. Workday, for example, lists Human Resource Management, Talent Management, Talent Acquisition, Workforce Management, Payroll, and Analytics and Reporting under its HCM product (Workday HCM).

Ignore the label and check the modules. The table below is the place to start.

What the modules do, and the dates they track

Much of an HRMS’s value is remembering obligations you would otherwise track in a calendar. The rightmost column gives examples of United States federal rules each module touches, from the agency’s own pages.

Module	What it does	A federal rule it helps you track
Employee records	One profile per person: job, manager, pay, documents	Form I-9 kept for 3 years after hire or 1 year after employment ends, whichever is later (USCIS)
Onboarding	Offer letter, forms, equipment and accounts for new hires	Form I-9 completed for each new hire
Payroll (often an add-on)	Pay runs, deductions, tax filings	Form 941 due April 30, July 31, Oct. 31 and Jan. 31 (IRS)
Year-end	Wage statements for each employee	Forms W-2 to employees and to the SSA by Jan. 31 (IRS)
Time off	Requests, approvals, balances	Your own policy and state rules
Performance	Review cycles, goals, one-on-ones	None federal; your own process
Offboarding	Access removal, final pay, document retention	The I-9 retention date above

This is a summary for orientation, not legal advice. State rules add their own deadlines, and your payroll provider or accountant confirms the ones that apply to you.

Worked example: two retention dates

The I-9 rule sounds simple until you apply it to real people. Example: two employees leave in 2025.

Employee A was hired March 1, 2024 and left June 30, 2025. Three years after hire: March 1, 2027. One year after leaving: June 30, 2026. The later date wins, so the form is kept until March 1, 2027.
Employee B was hired January 15, 2020 and left September 30, 2025. Three years after hire: January 15, 2023, already past. One year after leaving: September 30, 2026. The form is kept until September 30, 2026.

The two people left three months apart, yet their forms expire five months apart, in the opposite order. An HRMS that stores hire and end dates can compute this for every former employee. A shared folder cannot.

How HRMS is priced

HR software is commonly priced per employee per month (PEPM), sometimes with a base fee or a flat rate for small teams. Two vendors publish enough to work with, as of October 2026:

BambooHR: for companies with 25 or fewer employees, a flat $250 a month for Core, $425 for Pro and $650 for Elite. Above 25, the plan cards show $10, $17 and $25 per employee per month; the FAQ on the same page lists $10.25 for Core and $17.50 for Pro. Payroll is an add-on (BambooHR pricing).
Rippling: “plans start at $8 per employee per month, with a monthly base fee”; the base fee is not published (Rippling pricing).

Example: BambooHR Core as a company grows.

Employees	Monthly cost	Cost per employee
12	$250 flat	$250 / 12 = $20.83
25	$250 flat	$250 / 25 = $10.00
40, plan-card price	40 x $10 = $400	$10.00
40, FAQ price	40 x $10.25 = $410	$10.25

At 40 employees the year costs $400 x 12 = $4,800 or $410 x 12 = $4,920, depending on which figure the quote uses, before payroll. Two lessons follow. Flat small-team pricing is expensive per head at 12 people and cheap at 25. And when one page shows two prices, the quote is the number to budget, so ask for it in writing.

Checklist for an HRMS trial

Import 20 real employee records, including one part-time, one contractor and one former employee, and check every field.
Run one full onboarding: offer, forms, Form I-9 section 1, equipment and account requests.
Submit and approve a time-off request as an employee and as a manager on a phone.
Ask whether payroll is included or an add-on, and in which states the payroll product files taxes.
Check how the system stores end dates and whether it can report documents past their retention date.
Test the permissions: can a manager see salaries of people outside the team?
Export all records to a file and open it. You need a working exit before you sign.
Confirm the price per employee at your size today and at your size in 12 months, in writing.

For more business software delivered as SaaS, see SaaS examples. For the same buying logic applied to sales tools, see CRM SaaS. For what the vendor runs and what stays your job, see SaaS in cloud computing.

Common mistakes

Choosing by the label instead of the modules. An “HCM suite” may lack the payroll you assumed was included. Why it happens: vendors use HRIS, HRMS and HCM loosely. Instead: list the modules you need and tick them against the plan you would buy.
Forgetting that payroll is often separate. The HR price looks low until payroll is added. Why it happens: payroll sits under “add-ons” on many pricing pages. Instead: price HR and payroll together, including any bundle discount.
Deleting former employees’ records too early, or never. Both are mistakes: one breaks retention rules, the other keeps personal data longer than needed. Why it happens: nobody owns the purge date. Instead: store hire and end dates and review records past their retention date each quarter.
Letting every manager see everything. Default roles can expose pay and personal data. Why it happens: setup is rushed to go live. Instead: test the permissions with a manager account before inviting the whole company.

Sources

USCIS, Retaining Form I-9, checked October 2026.
IRS, Employment tax due dates, checked October 2026.
BambooHR, Pricing, checked October 2026.
Rippling, Pricing, checked October 2026.
Workday, Human capital management, checked October 2026.

In three sentences

A cloud HRMS holds your employee records and runs hiring, onboarding, time off, performance and offboarding, with payroll often sold as an add-on. At BambooHR’s October 2026 prices, Core costs $250 a month flat up to 25 employees, which is $20.83 per head at 12 people and $10.00 at 25. Compare vendors by modules rather than labels, get the per-employee price for your size in writing and let the system track deadlines such as the Form I-9 retention date.

ERP SaaS: cloud ERP vs on-premise, costs and migration

2026-10-18T07:00:00-04:00

Your finance team closes the month in spreadsheets exported from an old accounting system, and someone has proposed “moving the ERP to the cloud”. You need to know what that means, what it costs and what can go wrong. ERP (enterprise resource planning) software keeps a company’s core records in one system: the general ledger, purchasing, inventory, orders and often projects. ERP SaaS is that same system run by the vendor and rented by subscription, instead of installed on your own servers.

The choice matters because an ERP sits under almost every other process. A bad migration stops invoicing, not just one team. This guide explains what cloud ERP covers, the three ways it is delivered, a cost example from a published price list and the migration risks to plan for. For the basics of the delivery model, see What is SaaS?.

ERP in plain terms

Think of a restaurant kitchen with one shared order rail. Every ticket goes on the same rail, so the cooks, the cashier and the person ordering tomorrow’s vegetables all read the same orders. Without the rail, each station keeps its own notes and the numbers never match at closing time.

An ERP is that rail for a whole company. A sales order reduces stock, creates an invoice and posts revenue to the ledger in one step, because every module reads and writes the same database. Typical modules:

Financials: general ledger, accounts payable and receivable, bank reconciliation.
Supply chain: purchasing, inventory and warehouse.
Sales and service: quotes, orders and invoicing.
Projects and manufacturing: in the products and editions that offer them.

Cloud ERP does not change what the modules do. It changes who runs the servers, who applies upgrades and how you pay.

Three ways to run an ERP

The US National Institute of Standards and Technology (NIST) defines SaaS as using “the provider’s applications running on a cloud infrastructure”. You do not manage the servers, the operating system “or even individual application capabilities”, apart from limited settings (NIST SP 800-145, September 2011). NIST also describes resource pooling, where the provider’s resources “are pooled to serve multiple consumers using a multi-tenant model”.

That definition separates three models that vendors often sell under the same word, “cloud”:

Question	Multi-tenant ERP SaaS	Single-tenant hosted ERP	On-premise ERP
Who runs the servers	Vendor, shared by many customers	Vendor or a hosting partner, one instance for you	You
Who decides when to upgrade	Vendor, on its release calendar	Usually you, within the vendor’s support window	You
How deep you can customize	Configuration and extension tools	Deeper, sometimes including code changes	Anything, including core code
How you pay	Subscription per user	Subscription plus hosting and services	License, yearly maintenance, hardware and staff
Main risk	Less room to change standard processes	Upgrades postponed until they pile up	Old versions fall out of support

The table summarizes how the three models usually work. It does not describe one vendor; the contract decides the actual terms.

The upgrade row is where you feel the difference. SAP describes S/4HANA Cloud Public Edition as “a ready-to-run cloud ERP” with “automatic upgrades”, and lists its major releases in February and August (SAP Learning). You test before each release. You do not choose whether it happens. In return, you never fall years behind.

What cloud ERP costs

Most ERP SaaS is priced per user per month, often with a cheaper license for people who only read or approve. Microsoft’s price list for Dynamics 365 Business Central (as of October 2026) shows three user types, each priced “user/month, paid yearly”:

Essentials: $80.00.
Premium: $110.00.
Team Members: $8.00.

Microsoft notes that these prices are informational and that the actual price appears at checkout.

Example: a distributor with 25 people. Twenty need full finance and inventory access on Essentials. Five only approve purchase orders and read reports. Assume Team Members licenses cover what those five do; check Microsoft’s licensing guide before you buy. At list price:

Full users: 20 x $80 = $1,600 a month.
Light users: 5 x $8 = $40 a month.
Subscription: $1,600 + $40 = $1,640 a month, or $1,640 x 12 = $19,680 a year.
If all 25 people got Essentials instead: 25 x $80 = $2,000 a month, or $24,000 a year.
Assigning the right user type saves $24,000 - $19,680 = $4,320 a year, which is 18% of the all-Essentials price.

The subscription is rarely the whole bill. Implementation partners, data migration, training and add-on apps usually come on top, and none of them appear on a vendor’s price list. Before you compare a subscription with the license you already own, ask for a written estimate of each one.

Migration: where ERP projects go wrong

The software is only one part of a migration; the data and the timetable are the others. Four risks deserve a line in your plan:

Dirty master data. Duplicate customers, retired products and old account codes move with you unless you clean them first.
Customizations with no cloud equivalent. Code added to an on-premise ERP over the years may have no place in a multi-tenant product. SAP, for example, says its public cloud edition is typically a strong fit for customers with “limited customization requirements”.
Integrations. Banks, online stores, payroll and the sales system all connect to the ERP, and each connection must be rebuilt and tested. For one system that feeds an ERP, see CRM SaaS.
Cutover timing. Switching in the middle of a period leaves two ledgers to reconcile. Switch at a period end and keep the old system read-only for audit.

Support deadlines set the timetable too. On February 4, 2020, SAP announced mainstream maintenance for its Business Suite 7 core applications “until the end of 2027”. Optional extended maintenance runs to the end of 2030, at a premium of two percentage points on the maintenance basis. SAP has since published a separate transition option for customers that move to its private edition before the end of 2030, with terms updated on October 13, 2026. If you run an older on-premise ERP from any vendor, find the equivalent date before you plan.

Checklist

List every module you use today, and every module you pay for but do not use.
Count users by type: full, light (approve or read only) and none.
List every customization and mark the ones the cloud product covers with configuration.
List every integration and the person who owns it.
Get the vendor’s release calendar and the testing window before each release.
Get written estimates for implementation, data migration and training.
Pick a cutover date at a period end, and keep the old system read-only afterwards.

Common mistakes

Calling a hosted single-tenant system SaaS. Why it happens: both are “in the cloud” and both are billed by subscription. Instead: ask who decides when upgrades happen and whether your instance is shared. The answers tell you how much control and how much upgrade work you keep.
Licensing every person as a full user. In the example, that costs $4,320 a year for 25 people. Why it happens: one license type is the simplest order to place. Instead: count light users before you sign, and check what each license type allows.
Moving the data as it is. Why it happens: cleaning feels like a task for after go-live. Instead: clean and archive master data before the migration, while the old system is still the reference.
Rebuilding old customizations by reflex. Why it happens: users ask for the screens they know. Instead: for each customization, ask whether a standard process in the new product does the same job.

For how per-user pricing compares with other structures, see SaaS pricing models. For where SaaS sits among the cloud service models, see SaaS in cloud computing.

Sources

NIST, SP 800-145, The NIST Definition of Cloud Computing, September 2011, and the CSRC glossary entries for SaaS and resource pooling.
Microsoft, Dynamics 365 Business Central pricing, checked October 2026.
SAP Learning, Introducing SAP S/4HANA Cloud Public Edition, checked October 2026.
SAP News, maintenance announcement, February 4, 2020, and transition option update, August 4, 2025, updated October 13, 2026.

In three sentences

ERP SaaS is a company’s shared record of finance, inventory and orders, run and upgraded by the vendor and paid for by subscription. At Microsoft’s list prices, 20 full Business Central users and 5 light users cost $1,640 a month, $4,320 a year less than licensing all 25 as full users. Plan the migration around clean data, fewer customizations, rebuilt integrations and your current vendor’s support deadline, because no subscription covers those parts for you.

CRM SaaS: how cloud CRM works and how to choose one

2026-10-17T07:00:00-04:00

Your sales team tracks deals in a shared spreadsheet, two people overwrote each other’s notes last week, and you have been asked to pick a CRM before the next quarter starts. A cloud CRM (customer relationship management software delivered as SaaS) is a hosted database of your customers and deals, with a workflow on top that tells each salesperson what to do next. You rent it per user, per month, and the vendor runs everything else.

Choosing one is mostly about two things: whether its model of a sale matches yours, and what it will really cost once every seat and fee is counted. This guide covers both. If SaaS itself is new to you, start with What is SaaS?.

A CRM in plain terms

Think of a shared address book glued to a whiteboard. The address book holds every person and company you deal with, with notes on each conversation. The whiteboard has columns, “contacted”, “demo”, “proposal”, “won”, and each deal is a sticky note that moves from left to right.

A CRM is that pair, with three additions a whiteboard cannot offer. It records every email and call against the right contact. It reminds people of the next step. And it adds up the board into a forecast. The main objects are the same in almost every product:

Contacts and companies: the people and organizations you sell to.
Deals (or opportunities): a possible sale, with a value and an expected close date.
Pipeline: the ordered list of stages a deal passes through.
Activities: calls, emails, meetings and tasks, linked to a contact or deal.

How a cloud CRM works

Because it is SaaS, the CRM runs on the vendor’s servers and you reach it through a browser or a mobile app. The vendor handles hosting, updates and backups of the system; you handle your data, your users and your settings. The same split applies to every SaaS product, as SaaS in cloud computing explains step by step.

The value comes from connections. A CRM linked to your email and calendar logs activity without typing. Linked to your website forms, it creates contacts from inquiries. Linked to your billing tool, it shows which customers have paid. Each connection depends on the plan: many vendors keep API access or certain integrations for higher tiers.

How cloud CRM is priced

Almost every CRM charges per seat: one price per user per month, in tiers. Lower tiers cover contacts, deals and a pipeline. Higher tiers add automation, forecasting, custom reports and more API access. That is the classic per-seat model, with its usual side effect: every new colleague who needs access adds a line to the bill.

Two details change the total more than the headline price. Billing period: many vendors discount annual billing against monthly. One-time fees: some charge a required onboarding fee on higher tiers.

Worked example: a 10-person sales team that grows

One vendor’s public price list is enough to show how the bill moves. Salesforce lists Starter Suite at $25 per user per month (billed monthly or annually) and Pro Suite at $100 per user per month, billed annually (Salesforce pricing, as of October 2026). Other vendors follow the same tiered, per-seat shape; take their numbers from their own price lists, not from articles about them.

Example: you start with 10 users on Starter Suite. In year two the team grows to 15 and needs the automation of the higher tier, so you move to Pro Suite.

Scenario	Calculation	Yearly cost
Year one, 10 users on Starter Suite	10 x $25 x 12	$3,000
Year two, 15 users on Pro Suite	15 x $100 x 12	$18,000
Alternative: 10 users on Pro Suite from day one	10 x $100 x 12	$12,000

Two things stand out. The per-seat price rises four times ($25 to $100), while the yearly bill rises six times ($3,000 to $18,000), because the tier change and the new seats multiply. And the entry price is not the number to budget. If you expect to need automation or forecasting within a year, price the higher tier for the team you will have.

Checklist for comparing CRMs before a trial ends

Import a real sample of your data (500 contacts and 50 open deals) and check that nothing is lost or mapped to the wrong field.
Rebuild your actual pipeline stages and see if the product follows them without workarounds.
Connect email and calendar for two users and confirm activity is logged automatically.
Check which tier includes API access and the integrations you need, not only whether they exist.
Set up roles: can a salesperson see only their own deals if you need that?
Export everything to a file and open it. You need a working exit before you sign.
Read the contract for seat reductions: can you lower the seat count at renewal, or mid-term?
List every one-time fee and every add-on you will need, and add them to the per-seat price.
Ask the team who will use it daily to run one real week in it, not only the buyer.

Common mistakes

Comparing entry-tier prices only. The features most teams want later, such as automation and forecasting, sit in higher tiers. Why it happens: the entry price is the largest number on the pricing page. Instead: price the tier you expect to need in 12 months, as in the example.
Forgetting one-time and annual-commitment terms. A required onboarding fee or an annual-only price changes the first-year total. Why it happens: fees sit in footnotes. Instead: calculate the first-year and second-year totals separately.
Importing messy data and blaming the CRM. Duplicates and blank fields make any CRM look broken. Why it happens: the spreadsheet is copied in as it is. Instead: clean and deduplicate before the import, and decide which fields are required.
Buying seats for people who only read reports. Every seat costs the full per-user price. Why it happens: everyone asks for access. Instead: check whether the vendor offers read-only or lower-cost seats, or share reports by email.

For more familiar SaaS products grouped by function, see SaaS examples.

Sources

Salesforce, Sales Cloud pricing, checked October 2026.

In three sentences

A cloud CRM is a hosted database of contacts and deals with a pipeline workflow on top, rented per user per month while the vendor runs the system. At Salesforce’s October 2026 list prices, 10 users on Starter Suite cost $3,000 a year, and 15 users on Pro Suite cost $18,000. Compare the tier you will need in a year, including one-time fees and billing terms, and test your real data and an export before the trial ends.