Custom Client Portal vs SaaS: What 3 Years Actually Costs

You have a Q4 list and a 2027 budget, and a client portal is on it. There are two ways to get one: pay a monthly subscription or build your own. The custom client portal vs SaaS debate usually gets settled on the first month's price, which is the wrong number. This post adds up three years, counting seats and add-ons. It uses Softr's published plans as the subscription example and our published custom range as the other side. It is one part of our guide to client portals for small service businesses. Short version: for a simple portal with a few dozen clients, a subscription usually costs less. The math tips when your client count grows or the portal has to read from your CRM.

What a subscription costs over 36 months

Softr is a no-code builder, meaning you assemble an app from blocks instead of writing code. We use it as the example because it publishes seat prices openly. As we read Softr's pricing documentation on October 5, 2026, the Pro plan is $99 a month billed annually, or $119 billed monthly. Business is $329 a month billed annually, or $395 billed monthly. Annual billing is paid upfront for 12 months.

The sticker price covers a fixed number of people. Per the same documentation, Pro includes 10 team users and 50 client users. Extra team users are $3 each and extra client users are $1 each, capped at 50 and 250. Business includes 30 team users and 100 client users, with extras at $5 and $2, capped at 100 and 500. A "seat" here means one named login. Past the cap you move to a custom Enterprise quote.

Here is the arithmetic for three scenarios. These are our calculations from the list prices above. They assume annual billing, that the per-user rates are monthly, and that prices hold for 36 months, which no vendor promises.

Subscription cost over 36 months, built from Softr's list prices as read on October 5, 2026

Scenario	Monthly cost	36-month total
Pro, 50 clients, 10 staff (nothing extra)	$99	$3,564
Pro, 120 clients, 15 staff (70 extra client users at $1, 5 extra team users at $3)	$184	$6,624
Business, 200 clients, 40 staff (100 extra client users at $2, 10 extra team users at $5)	$579	$20,844

One caution on those numbers: metering changes. An earlier pricing update on Softr's blog merged internal and external users into one count and said extra users were billed in packs of 10. The current documentation counts team and client users separately. Confirm how your bill rounds before you budget.

What the subscription bill leaves out

The table is the platform fee. It is not the cost of having a working portal. Four lines sit outside it, and we cannot put a dollar figure on any of them for you.

• Build time. Someone has to design the pages, set permissions and load the data. That is your hours or a contractor's, and it recurs every time your process changes.
• Connections. If the portal needs to show data from your CRM or accounting tool, you either re-key it by hand or add a connector. Connectors can carry their own monthly fee.
• Double entry. A portal that cannot read your internal systems becomes a second place your staff update. That cost shows up as payroll hours, not a software line.
• Exit cost. The layout, permissions and logic live inside the vendor's platform. Leaving means rebuilding them, even if you can export your data.

None of this makes a subscription a bad deal. So the real three-year figure is the table total plus your own labor. Write that labor down before comparing.

What a custom build costs, without the soft focus

Our custom-app cost post publishes tiers running from $15,000 to $100,000+. A client portal lands somewhere in that range depending on scope. The drivers are logins and roles, file exchange, status tracking, payments, CRM connections and reporting. We will not pin your portal to one number in a blog post. The proposal does that after we see your process.

Compare it honestly. The low end of that range is more than twice the Pro scenario in the table. So on cost alone, a subscription wins for a small, simple portal. Against the Business scenario, a low-end build costs less than the subscription total. Both comparisons leave out hosting and support on the custom side, and build labor on the subscription side.

Those recurring lines are real. Hosting, third-party subscriptions (payments, email sending, maps) and ongoing support sit outside the build and are scoped separately in the proposal. We do not resell hosting. Hosting costs can also rise with usage, so ask for them as a separate line.

What the build price buys

Two things a subscription cannot give you. First, ownership: under the project agreement, the code and data belong to you. Second, no per-seat meter. Adding the 201st client does not change a platform bill. Our custom customer service software work covers support portals, case workflows and client dashboards. All of it connects to your CRM and operating process.

When a subscription is the right answer

We build custom software for a living, and we still tell some owners to rent. Rent instead of build when most of these are true:

• You have roughly 50 clients or fewer, and the portal does standard things: share files, show a status, take messages.
• Your process is still changing. Do not freeze a workflow in custom code before you know it.
• You need something running quickly. A subscription is usually faster to stand up than a build. If your deadline is year-end, read whether a client portal can be in service before December 31. We do not promise delivery dates for custom builds.
• Nobody on your team will own a custom system after launch.
• The portal supports a project with an end date, such as a single engagement or a one-year program.

If four of those five describe you, start with a subscription. Keep a record of what clients ask for and what staff work around. That list becomes the specification if you build later.

When a custom build pays for itself

The case for building is that the portal should be a window into the system you already run, not a copy of it. Look for these signals.

• The data lives in your CRM or operations system. The portal should read it live. Our WRAPT wholesale operations platform is the clearest example. It joins a 9-stage lead-to-delivery pipeline, a client portal and an omnichannel support hub in one platform. The hub includes a web-chat agent called TAMI.
• Your client count is large or climbing. Per-seat pricing grows with your success. A build charges you once, then hosting and support.
• Your workflow is unusual. Multi-party approvals, role rules by project, or quoting logic tend to strain template portals.
• You want to own the asset. If the portal is part of how clients experience your brand, renting it means a vendor controls your front door.

There is also a middle path. Run a subscription for a year, export your data regularly and treat the limits you hit as the spec for a build. We do not know of a rule that says when to switch. The trigger is usually the day staff spend more time feeding the portal than it saves.

A one-page test before January

Bring these six answers to your planning meeting. Together they take about an hour to gather.

1. How many clients need a login today, and how many in 36 months?
2. How many staff need access, and do any of them need different permissions?
3. Which systems must the portal read from or write to?
4. Who will own it day to day: configuring, fixing, answering client questions?
5. What would a 50 percent price increase on the platform do to your budget?
6. If you left in year two, what would you have to rebuild?

Then price both paths using the table method above. Use list prices for the subscription and a written scope for the build. Put the answer next to the rest of your plan in our guide to sizing your 2027 small business software budget. Some South Jersey service businesses will find the subscription wins, and that is a fine outcome. Ask your own accountant how each option is treated for tax, since that varies by business.

Frequently Asked Questions

Is a custom client portal cheaper than SaaS over three years?

It depends on client count and integrations. Using Softr's published pricing as read on October 5, 2026, a Pro plan with 50 clients totals $3,564 over 36 months. Our custom-app tiers start at $15,000. A subscription is cheaper for small, simple portals. Custom gets competitive as seats climb or the portal must connect to your CRM.

How much does a custom client portal cost for a small business?

Our custom-app cost post publishes tiers from $15,000 to $100,000+. Where a portal falls depends on logins, roles, payments, file handling and connections to your other systems. Hosting, third-party subscriptions and ongoing support are scoped separately in the proposal. We give a figure only after reviewing your process, not from a blog post.

Do I own a portal built on a subscription platform?

Usually you rent access. Your data is often exportable, but the pages, permissions and logic live in the vendor's platform, so leaving can mean rebuilding. Read the vendor's terms on data export before you commit. With a custom build from us, the code and data belong to you under the project agreement.

How many clients can a portal subscription handle before the price jumps?

It varies by plan. In Softr's documentation as read October 5, 2026, Pro includes 50 client users and caps at 250. Business includes 100 and caps at 500. Past the cap you need a custom quote, so check ceilings too.

Prices in this article are starting ranges published on iolab.co/pricing. Hosting, third-party subscriptions and ongoing support are scoped separately in your proposal.

Get your three-year numbers

Send us your client count, your staff count and the systems a portal would need to touch. We will tell you whether a subscription covers it. If not, we will say whether a build makes sense, often starting from a custom CRM that holds the data. If a subscription is the right answer, we will say so.