Skip to content
dvnt.io

SUBSCRIPTIONS · PAYMENTS · MANY CLIENTS

SaaS applications

We build SaaS applications from MVP to a product with paid plans: separated customer data, subscriptions and invoices, sign-up without a sales call, and your customers' branding where they need it.

Multi-tenant · subscriptions · Stripe · KSeF · white-label

Architecture

N tenants

one platform, many customers, each with its own data

SAAS OR CUSTOM SYSTEM

How a SaaS application differs from a custom system

From the outside they look alike: login, dashboard, data. The difference is how many companies the system works for.

  • CUSTOM SYSTEM

    One company, its processes

    It serves one company and fits the way it works. Its users are that company's staff and customers, and the quote starts from a list of features.

  • SAAS APPLICATION

    Many companies, each with its own data

    You sell it to many companies on a subscription. Each has its own data, users and plan, and the system has to keep them apart. That is why a SaaS quote starts with how many customers it must serve a year from now, not only with its features.

// WHAT A SAAS PRODUCT NEEDS · SIX ELEMENTS

Six things a SaaS needs to work as a business

Product features are half the work. The other half is everything that lets you sell it to many customers without handling each of them by hand.

  • MULTI-TENANT

    Separated customer data

    Each company sees only its own data, even when all of it sits in one database.

  • SUBSCRIPTIONS

    Plans and recurring payments

    Plans, free trials, mid-cycle plan changes, invoices — all automatic.

  • SIGN-UP

    Start without talking to sales

    Customers create an account, pick a plan and start working on their own. Sign-in with an e-mail link or with Google.

  • LIMITS

    Plan limits enforced by the system

    The number of users, records or requests comes from the plan — and the system enforces it, not the support team.

  • WHITE-LABEL

    Your customers' branding where they need it

    Logo, colour, message sender, own domain — when your customers' clients should see their brand, not yours.

  • UPDATES

    Changes without downtime

    A new version reaches all customers at once, with no maintenance window and no manual migrations for each of them.

MULTI-TENANT · DATA SEPARATION

Multi-tenant: how we separate customer data

Multi-tenant is an architecture in which one instance of the application serves many customers (tenants) while their data stays separated.

  • SHARED DATABASE

    One database, every record assigned to a customer

    The most common variant and the cheapest to maintain. In the AI chat platform every data collection has a customer field, and data access goes through a single layer that always applies that filter — it cannot be forgotten in an individual query.

  • SEPARATE DATABASES

    A separate database for each customer

    We consider it when a customer requires physical data separation, has its own data residency requirements, or is large enough that its load should not affect the others.

  • FROM DAY ONE

    Architecture for many customers from the MVP

    Adding customer separation to a finished application means rebuilding every query. That is why we build it in from the start, even when there is only one customer at launch.

SUBSCRIPTIONS AND PAYMENTS

Subscriptions, payments and invoices

Payments in SaaS are not a “Buy” button but a whole cycle: free trial, renewals, plan changes, failed payments, invoices.

  • DVN LINKS

    Pricing in the admin panel, not in the code

    Plans with limits are stored in the database and synchronised with Stripe: saving a plan creates or updates the product and price. Changing the pricing is an edit in the panel, not a deployment. The Pro plan's free trial uses the same limit logic, so nothing is duplicated.

  • DOMYKO

    Payments and invoices in KSeF

    Subscriptions for accounting firms through Stripe (payment, customer portal, taxes), with VAT invoices issued automatically by inFakt and sent to KSeF. The price depends on the number of the firm's clients.

PROJECTS · THREE SAAS APPLICATIONS

SaaS application examples

Three working products: each solves a different problem and each shows a different part of SaaS architecture.

  • DVN LINKS

    Link shortener with QR codes and statistics

    From a single-user tool to a SaaS platform: accounts, plans and payments, three domains with plan-dependent access, sign-in with an e-mail link or with Google.

    Link safety is checked when the link is created, not in a separate process after the fact. A free plan and paid plans.

  • DOMYKO

    Client portal for accounting firms

    The firm sees which documents are missing from each client, and the system sends reminders on its own — by e-mail, SMS and a link that works without logging in. Clients describe their purchase invoices from KSeF in the portal.

    Everything under the firm's brand: logo, colour, message sender.

  • AI CHAT

    AI chat with a company knowledge base

    A chat widget for your website that answers from the company's knowledge base and hands the conversation to the team's shared inbox when a person is needed.

    It runs on digitalvantage.pl and will soon run on other portals — each deployment with its own data.

// FROM MVP TO PRODUCT

MVP first, then the full product

Most SaaS products start with a narrow MVP: one main user journey, payment, dashboard.

  • MVP

    A version to test the market with

    Scope limited to what the customer pays for from day one. Reports, extensive settings and edge cases come after the first paying customers.

  • PRODUCT

    Growth without a rewrite

    Production-ready technology from the start, so growth means adding features, not rebuilding the system.

B2B SAAS · SPECIFICS

B2B SaaS: teams, roles and security

A business customer buys differently from a consumer: pays for a team, needs an invoice and asks about data security.

  • TEAMS

    Company accounts, teams and roles

    A company account with multiple users, roles and invitations — in Domyko the firm manages its team and its clients separately.

  • INVOICES

    VAT invoices without being asked

    Invoices issued automatically after every payment, with the company details from the account, also through KSeF.

  • SECURITY

    Sign-in and data under control

    Sign-in with an e-mail link, two-factor authentication, credentials for external systems encrypted with a separate key for each company.

PRICING

How much a SaaS application costs

The price depends mainly on the MVP scope and the number of integrations. We quote further development in stages, based on what already works.

  • LEAN MVP

    from PLN 10,000

    The smallest version of the product for first validation, on technology you will build on later.

  • MVP

    from PLN 30,000

    A version with payments, company accounts and a dashboard — ready to sell to your first customers.

  • MAINTENANCE

    PLN 450–800 / month

    Ongoing technical support after launch, depending on scale.

FAQ

Questions about SaaS applications

How does a SaaS application differ from a custom system?

A custom system serves one company. A SaaS application is sold to many companies on a subscription — each has its own data, users and plan.

The difference lies in the architecture: separated customer data, recurring payments, plan limits and sign-up without the team's involvement.

One database for all customers or separate ones?

Usually one database with every record assigned to a customer — cheaper to maintain and simpler to update. We consider separate databases when a customer requires physical data separation or its load should not affect the others.

Who owns the code?

You do. The code is in your repository from day one, with documentation that lets another team develop the product.

How long does it take to build an MVP?

A typical MVP project takes 6–8 weeks. We set the exact schedule after the analysis (discovery) stage, once we know the scope.

Which payments can you handle?

Monthly and annual subscriptions, free trials, plan changes and VAT invoices — through Stripe, with invoices also sent to KSeF.

RESOURCES · BEFORE WE TALK

Before we talk

// Next step

Describe your project. We reply within 24 h.

A few sentences are enough: what should work, what it connects to and by when. No brief, no commitment.

What happens next

  1. We read your message and reply within one working day.
  2. We set up a short call about the scope, with no sales pitch.
  3. You get proposed stages and a price range.
Meeting date (optional)

Time

CET

Checking free times…

Budget (net)

By sending this form, you accept the Privacy Policy.