Skip to content
DeutschBook an intro call

Software development

SaaS development, from MVP to operations

Multi-tenant, privacy by design, export-ready for the EU Data Act. For founders and companies with a product idea.

Updated November 2026

See packages

You’ll talk to the engineer who will build your project.

Who it’s for
Founders, specialist firms with a product idea, and small and mid-sized companies that want to turn an internal tool into a product
Timeline
Estimates: discovery sprint 5–10 business days, SaaS MVP 8–12 weeks. The schedule in your quote is binding.
Price
Fixed price after analysis
You get
User flows, a clickable prototype, architecture and a fixed price; then a multi-tenant MVP with subscription billing, data export, documentation and an SBOM
Rights
Repository (where your source code lives) and cloud account in your name from day one; usage rights pass to you on full payment
Payment
Payment terms in your quote

What’s included in SaaS development?

We build your SaaS product from the first analysis to operations. That includes tenant isolation (each customer sees only its own data), roles and permissions, and subscription billing. You also get data export in open formats and hosting in your own cloud account. After a discovery sprint, we build your MVP, the first sellable version, at a fixed price.

Your MVP should be as small as possible and stable enough for paying customers. You get the code, accounts and documentation in a form your own team can take over later. If the software is for your own processes and not for sale to other companies, custom business software is the better fit.

Our guide What is SaaS? explains what makes a product SaaS and how an idea becomes an MVP.

Before you commission a provider, ask each one the same 12 questions for choosing a software developer.

Datafalke is based in Bottrop, Germany.

Software development overviewAll services
  • Your idea has been tested with customers, but you don’t have an in-house engineering team.
  • You want to turn an internal tool into a product for other companies.
  • Early customers are asking about data export, data processing agreements or security evidence.
  • Quotes you’ve received have no fixed price or don’t say where the code will live.

What you get

Discovery sprint

Target users, the core feature, user flows, a clickable prototype and the architecture, then a fixed price for the MVP.

MVP at a fixed price

The first sellable version of your software, with weekly demos and repository access from day one. Estimate: 8–12 weeks.

Multi-tenant from day one

Multiple customer companies in one app, cleanly separated, each with its own users and permissions.

Billing, roles and permissions

Subscription billing through a payment provider of your choice, with roles for your customers and for your team.

Data export for the EU Data Act

Export of your customers’ data in common, machine-readable formats, so they can switch providers.

Operations and ongoing development

Hosting in your own cloud account with a provider of your choice, preferably EU-based, plus software care with updates and monitoring.

How do we separate your customers’ data?

We use one of three basic models, which we choose with you in the discovery sprint. The options are shared tables with a customer ID on every row, a separate database for each customer or a separate deployment for each customer. As a rule, the stronger the isolation, the higher the cost and effort per customer.

As a rule, stronger isolation means higher cost per customer
As a rule, stronger isolation means higher cost per customer Three models, one below the other. With shared tables, all customers share the app and the database, and every row carries its customer’s ID; the cost per customer is lowest. With a separate database per customer, customers share only the app; the cost per customer is higher. With a separate deployment per customer, nothing is shared and costs grow with every customer. The table below compares the models in detail. Shared tables One app for all customers One database for all customers Rows with ID A Rows with ID B Rows with ID C Lowest cost per customer Separate database per customer One app for all customers Database Customer A Database Customer B Database Customer C Higher cost per customer Separate deployment per customer App Database Customer A App Database Customer B App Database Customer C Costs grow with every customer
Three basic models of tenant isolation
ModelHow the data is separatedCost and operationsA good fit when
Shared tablesEvery row carries the ID of the customer it belongs to. The app filters every query by that ID, and row-level security policies in the database can add a second safeguard.Lowest cost per customer, with a single database to back up and update. Restoring one customer’s data from a backup takes extra work.You have many customers with similar requirements
Separate database per customerEach customer’s data sits in its own database, while all customers share the app.Higher cost per customer. Every change to the data model has to roll out to all databases automatically.Customers require their own encryption keys, their own backup rules or a specific storage location
Separate deployment per customerEach customer gets its own environment, and nothing is shared.Costs grow with every customer, and updates and reporting across all customers take more work.You have a few large customers with strict requirements

Source: Microsoft, Azure Architecture Center (external site),

Mixed models are common: most customers share a database, while some pay extra for their own. AWS’s architecture guidance (external site) calls the shared model pool, the separate model silo and the mixed model bridge.

In every model, one customer must never be able to see another customer’s data. If someone can retrieve another customer’s records by changing an ID in a request, access control is broken. This class of vulnerability ranks first in the OWASP Top 10:2025 (external site).

Our explainer What is a multi-tenant SaaS architecture? covers how the models differ and when each one pays off.

Who it’s for, and who it isn’t

Good fit

  • Founders with an idea that’s been tested with customers
  • Specialist firms that want to turn an internal tool into a product
  • Software companies inside or outside the EU whose EU customers ask about the GDPR and the Data Act

Not a fit

  • Ideas no one has tested with customers yet; we’d suggest customer interviews first
  • Products that need a large engineering team from day one
  • Anyone wanting a fixed price without a discovery sprint

How the project runs

  1. Intro call

    SaaS development starts with a conversation, by video or in person at your office if you’re in the Ruhr area of Germany. It’s free, and you talk directly to the engineer who will build your product.

    Timeline
    30 minutes
    Result
    Target users, core feature, timeline
  2. Discovery sprint

    We define your target users and core feature, map the user flows and build a clickable prototype you can show to potential customers. We also decide on the architecture, the data model and the tenancy model.

    Timeline
    5–10 business days (estimate)
    Result
    User flows, clickable prototype, architecture as system context and container diagrams (C4 model, levels 1–2), data model, risk list, fixed-price quote
  3. Development in sprints

    We work in short cycles and show you where things stand every week. The code is in your repository from the start.

    Timeline
    8–12 weeks (estimate)
    Result
    Weekly demo with budget status, repository access from day one
  4. Sign-off

    You review the MVP against the criteria we agreed on in writing. At sign-off, you receive the documentation and the software bill of materials.

    Result
    Sign-off against written criteria, documentation, SBOM
  5. Operations and ongoing development

    After that, if you’d like, we keep looking after the software and develop it further as planned. Your team or another provider can also take over.

    Timeline
    monthly
    Result
    Software care S or L, planned further development

Worked examples from our articles

We built, ran or documented these examples for our articles. The PostgreSQL example uses test data rather than client data.

All examples come from our own project or from test data. None of them comes from client work.

You can carry on without us if you need to. Code, hosting account and domain are under your control from day one, and every sign-off includes documentation another team can work from.

  • Accounts from day one

    Repository, cloud account, domain and credentials are in your name. We work with delegated access.

  • Documentation included

    Architecture docs (arc42, C4), decision records, an operations manual and a software bill of materials (SBOM) come with every sign-off.

  • Handover commitment

    If we part ways, we hand over all documentation to your team or new provider. Your contract sets out how the handover works.

  • Standard technology

    We use widely adopted open-source frameworks, not homegrown tools only we understand.

Mohammad Alboush

Mohammad Alboush is a software engineer and the owner of Datafalke. He’s your direct line to the team, from the intro call to sign-off. He replies to requests within one business day (Monday to Friday).

Pricing and packages

If your project is a fit, you’ll get a price range or a recommended first step after the free intro call. The discovery sprint is a paid entry offer with its own deliverable; we tell you its price before you order and quote the fixed price for your MVP after the sprint.

Discovery sprint

Founders and companies with a product idea

You get
user flows, clickable prototype, architecture (C4, levels 1–2), data model, risk list, fixed-price quote
Timeline (estimate)
5–10 business days

Price in your quote

SaaS MVP

Founders and companies with a SaaS idea

You get
multi-tenant, roles, subscription billing, data export, admin area, documentation, SBOM
Timeline (estimate)
8–12 weeks

Fixed price after discovery

What drives the price

  • Number of roles and core features
  • Billing model and payment provider
  • Tenant isolation model
  • Integrations with other systems
  • Data migration from existing systems
  • Security and compliance evidence requirements
  • User interface languages

Software care and changes after sign-off

Software care S covers updates, monitoring and two hours of work a month, for at least three months. Software care L is by agreement. Changes outside the fixed price start only once you approve them.

Contact us

Frequently asked questions

How much does a SaaS MVP cost?

For SaaS MVP development, we quote the fixed price after the discovery sprint. The price depends mainly on the number of roles and core features, the integrations, the billing model and the tenant isolation model. An MVP stays small when it delivers one core feature to one group of users; we plan everything else for later releases. Our cost guide How much does it cost to build a SaaS product? gives market prices in euros and worked examples.

Who owns the code?

The repository is in your account from day one. The exclusive usage rights to the code we write for you pass to you on full payment. Open-source components keep their own licenses.

Where is the data stored?

In your own cloud account, with a provider of your choice, preferably EU-based and under a data processing agreement (DPA). We set up the account with you and work in it with delegated access.

What if our requirements change?

Then we change the plan, but never silently. New requests go into a prioritized backlog. What they cost in time or money is set out in a change request before we start work on them.

Won’t we be locked in?

No. We use widely adopted open-source frameworks instead of homegrown tools, and every SaaS MVP includes data export. Your code and accounts are under your control from the start, and every sign-off includes documentation. So you can carry on at any time with your own team or a different one. Our colophon shows the technology we use ourselves.

Is there funding for this?

Grants are rare. For digitalization projects, there are loans from the German development bank KfW (external site) (in German). They’re open to companies based in Germany and to German subsidiaries or branches of foreign companies. Companies subject to tax in Germany can claim the research allowance (external site) (Forschungszulage, in German) for genuine R&D, but routine software development doesn’t qualify. Of Germany’s state programs, we’ve only reviewed those in North Rhine-Westphalia, and we haven’t looked at programs in other countries. As of November 2026.

Do you also build the product website?

Yes, if you’d like. We build it with SEO and generative engine optimization (GEO), so Google and AI assistants can read what you offer and describe it accurately.

Website development

Related insights

Your next step

Planning a SaaS product?

Tell us who it’s for and what it must do. In the intro call, we’ll work out what a sensible MVP looks like.

Menu

Book an intro callDeutsch