← All our services

Web app & SaaS

Your web application.
Ready to evolve.

A customer portal, service platform or SaaS: we build the product and integrations that let your users work online.

Let’s discuss your project

USE CASES BEFORE TECHNOLOGY

What we can build.

01

Customer portals

Accounts, service access, documents and request tracking.

02

SaaS platforms

Organisation, role, subscription and user journey management.

03

Partner portals

Shared data, communication and access tailored to each stakeholder.

Clear journeys. An architecture that can evolve.

We define roles, data and flows before building. Authentication, any payments and hosting constraints are part of product and technical decisions.

FOR OUR FIRST CONVERSATION

Your product.
Its first use case.

Before expanding the platform, let’s identify who it serves and what an initial version needs to enable.

WHAT TO SHARE WITH US
01Users and their roles
02The service you want to offer
03The data and tools to connect

You don’t need a complete specification to get started.

HOW IT WORKS

A platform.
Multiple roles, one product.

A SaaS product is more than its screens. Permissions, organisations and data flows shape how it works.

CONCEPT DIAGRAM · ACCESS TAILORED TO EACH USER
  1. 01

    Your users

    Clients, teams and administrators.

  2. 02

    The workspaces

    Journeys and access based on roles.

  3. 03

    Business logic

    APIs, rules, services and subscriptions.

  4. 04

    The data

    Organisations and integrations.

Data separation between organisations and access rights are designed around your platform model.

DECISIONS TO MAKE TOGETHER

The choices that
make the difference.

Concrete decisions, before turning them into development work.

01Product & initial scope

We distinguish features essential to initial use from future development. The backlog makes trade-offs visible: priority journeys, dependencies and acceptance criteria.

To agree: what the first version needs to enable.
02Organisations & permissions

Can a user belong to several organisations? Who invites, administers or views data? These rules structure accounts, workspaces and access controls.

To agree: roles, scopes and data separation.
03Payments & third-party services

Where the product requires it, we define subscriptions, payment events, notifications and connections to your other tools. Failure cases are addressed alongside normal journeys.

To agree: chosen services and operating rules.
04Hosting & operations

We specify environments, deployment, backups and monitoring needs. Expected volumes and recovery constraints guide the architecture.

To agree: operating context and responsibilities.

A DEFINED PROJECT, VISIBLE PROGRESS

From the first conversation
to launch.

Our agile method
  1. 01

    Define the product

    Use cases, initial scope, roles and prototype.

    You validate

    The product’s roles, journeys and priorities.

  2. 02

    Build in iterations

    Interfaces, business logic, data and integrations.

    You see

    Usable features at each iteration.

  3. 03

    Prepare the launch

    Acceptance testing, deployment, documentation and operational requirements.

    You receive

    The product, configuration and documentation.

DELIVERY & HANDOVER

What you
receive.

  • Interfaces and source code for the agreed scope
  • Documented data model and integrations
  • Deployment configuration and acceptance test results
  • Next-phase backlog and handover documentation

The scope and deliverables are specified in the proposal.

Your questions.
Practical answers.

Can we start with an MVP?

Yes. We define an initial scope that fits the use case to test. Further features are prioritised in a backlog based on your feedback and product constraints.

Can payments and subscriptions be integrated?

Yes, according to your business model and chosen services. Payment journeys, access rights and billing events are defined before development.

Can the platform connect to our existing tools?

Yes, depending on available APIs, access and formats. We review flows, volumes and failure cases before defining the integrations to build.

How do you avoid building a platform that is hard to take over?

Architecture choices, access, the data model and deployment requirements are documented. Handover is prepared with the people who will maintain the product.

Your project.
Let’s talk.

Describe your needs