Indicatively, a discovery phase or clickable prototype usually fits under €25,000, a focused MVP with one core workflow sits in the €25,000–€75,000 band, a production SaaS with several roles and integrations runs €75,000–€150,000, and a multi-tenant platform with enterprise integrations or compliance work starts around €150,000. These are budget bands, not quotes: scope, integrations, compliance and team mix decide where a product lands.

01

The useful answer is a range tied to risk

Custom SaaS products are not priced by page count. Cost is driven by the number of workflows, roles, integrations, data rules and operational guarantees the first release must support.

A focused internal workflow can be substantially smaller than a regulated multi-tenant platform with billing, mobile access and third-party data. Treat any instant estimate without those distinctions as a sales number, not a delivery plan.

Indicative ranges by scope

The ranges below are the budget bands on Seditio's contact form, matched to the scope that typically fits each one. They are indicative orders of magnitude for planning, not prices for your product.

  • Under €25,000: discovery and scoping, a clickable prototype, a technical spike or a narrow proof of value
  • €25,000–€75,000: a focused MVP with one primary user journey, a small set of roles, one or two integrations and standard cloud hosting
  • €75,000–€150,000: a production SaaS release with several workflows and roles, billing or payments, an admin area, reporting and multiple integrations
  • €150,000+: a multi-tenant platform with enterprise identity, audit history, data migration, compliance work, mobile apps or a multi-phase roadmap
  • Ongoing team: a dedicated team that keeps building after launch, scoped by team shape and duration rather than as a fixed project

What these ranges do not include

The bands describe delivery work. Running costs come on top and should appear as separate lines in any proposal: cloud hosting, third-party services such as email, maps or AI model usage, software licences, app store accounts and post-launch support.

Some running costs grow with usage, so ask for an estimate at your expected number of customers as well as at launch volume.

Fixed price or time and materials?

A fixed price suits work whose scope is written down and unlikely to change, such as a discovery phase or a well-defined first release. Time and materials suits products that will keep evolving, because you pay for the work done and can change priorities between iterations.

Many projects combine the two: a fixed-price discovery that produces a scope, followed by a build priced against that scope, with a clear process for changes.

Why the bands overlap

Two products with the same feature list can land in different bands. One may reuse a standard login and a single payment provider; the other may need single sign-on for each customer, a migration from a legacy system and an audit trail a regulator can inspect. The visible features look alike, but the work underneath does not.

02

The five biggest cost drivers

Teams should make these variables explicit before comparing proposals.

  • Product uncertainty: how much discovery and validation is still required
  • Workflow and permission complexity
  • External systems and data migration
  • Security, compliance and audit requirements
  • Service expectations after launch

Uncertainty and validation

If the problem, the users or the business model are still open questions, part of the budget goes into finding answers rather than writing code. That is money well spent: a discovery phase that removes one wrong feature usually costs less than building and then removing it.

Workflows, roles and permissions

Every additional role multiplies the screens, rules and tests. A product where an admin, a manager and an end user each see different data needs a permission model that is designed, built and tested for every workflow, not added at the end.

Integrations and data migration

Each external system adds work for access, mapping, error handling and monitoring. Migrating data from an older system adds cleaning, reconciliation and a cut-over plan. Ask early who owns each integration and whether test environments exist.

Security, compliance and audit

Multi-tenant SaaS has to keep each customer's data separate. The AWS Well-Architected SaaS Lens calls tenant isolation one of the foundational topics every SaaS provider must address. Personal data adds obligations too: Ireland's Data Protection Commission explains that a data protection impact assessment is required before processing that is likely to result in a high risk to people's rights and freedoms.

Service after launch

Response times, release frequency, monitoring and out-of-hours cover all carry cost. A product used by a few internal staff in office hours needs a different support model from one that customers rely on every day.

Two common scope additions: mobile apps and AI features

A native or cross-platform mobile app adds design, build, testing and store releases on top of the web product. AI features add prompt and retrieval work, evaluation, monitoring and usage costs that grow with every request. Both are worth including when users need them; both are worth deferring when they are there only because competitors mention them.

What brings cost down

A narrow first release, decisions made quickly by one accountable product owner, standard components for login, payments and email, and early access to the systems you need to integrate. Deferring nice-to-have features to a second release is usually the largest saving available.

03

Budget by evidence stage

A good roadmap separates discovery, proof of value, MVP and scale. Each stage should buy down a specific category of risk and create evidence for the next investment decision.

This staged model also makes it easier to change direction without carrying an oversized first-release scope.

Discovery

Discovery turns an idea into users, workflows, data, integrations and a release plan. It usually takes days to a few weeks and normally sits in the under-€25,000 band. The output is a scope you can price with confidence, whoever builds it.

Proof of value

A prototype or technical spike tests the riskiest assumption, such as whether users understand the workflow or whether an algorithm or data source performs well enough. Keep it small enough to throw away; it also typically fits under €25,000.

MVP

The MVP is the smallest release real users can depend on. Seditio's SaaS development timeline guide puts focused MVP engineering at eight to sixteen weeks, and most focused MVPs fall in the €25,000–€75,000 band. Broader first releases with billing, admin tools and several integrations move into the €75,000–€150,000 band. See MVP development for how this stage is run.

Scale

Once usage and revenue justify it, investment shifts to multi-tenancy, integrations, performance and new modules. This is where €150,000+ programmes and dedicated development teams fit, funded in phases so each one is justified by evidence from the last. The Biologit case study follows this path from an algorithmic MVP to a secure SaaS platform.

Plan the first year, not only the build

Budget for the months after launch as well as the release itself. A new product usually needs a period of fixes, small improvements and performance work once real users arrive, and the first customer requests rarely match the original roadmap. Holding back part of the budget for this period keeps the launch from becoming the end of the money.

04

What a credible proposal should show

Expect assumptions, exclusions, team composition, milestones, acceptance criteria and operating costs—not only a single total.

Ask how the supplier handles scope decisions, quality, security, deployment, knowledge transfer and the period after launch.

How Seditio scopes: discovery first

Seditio's process starts with discovery and scope before design and development, followed by UAT, production and managed support. A reliable fixed price for a full product needs the workflows, integrations and acceptance criteria written down first; before that, the honest answer is a band and a plan to narrow it. See custom SaaS development for the full approach.

Team mix and location

Cost also depends on who does the work. Seditio pairs Ireland-based leadership and discovery with delivery capacity in Cebu, so the mix of roles in each location changes the total. A proposal should name the roles, their seniority and where they work, so you can compare like with like.

Compare proposals like with like

Put competing proposals side by side on the same scope list, team roles, assumptions and exclusions before comparing totals. A lower number that leaves out testing, deployment or support is not cheaper; it moves the cost to later.

Warning signs in a proposal

Be careful with a single total and no assumptions, a timeline with no discovery, a team with no named senior lead, or a price that does not change when you add integrations. Each one suggests the supplier has not yet understood the work, and the gap usually returns later as change requests.

Questions to ask before you sign

Use these questions to compare proposals on substance. A partner who has taken over another agency's product can also tell you what was missing from the original scope; the Pixreview case study describes one such transition.

  • Which assumptions, if wrong, would change the price most?
  • What is explicitly excluded, and what would each exclusion cost to add later?
  • Who owns the code, the cloud accounts and the data from day one?
  • What happens to the budget if the scope changes during delivery?
  • What will the product cost to run and support in its first year?

Sources

  1. Tenant isolation, SaaS Lens, AWS Well-Architected Framework, Amazon Web Services
  2. Data Protection Impact Assessments, Data Protection Commission (Ireland)