Skip to content

Approach

Every stepends with somethingyou can review.

You do not wait until the end of the project. After every step there is a result on the table: something to read, click through or try out. Then you decide whether and how to continue.

Four steps,no black box.

Every step shows two things: what happens, and what you hold in your hands afterwards.

  1. Step 1

    Intro call

    You tell us what should change and how things work today. We ask questions and say openly whether and how we can help.

    From youAbout 30 minutes, by phone or video. You need no documents.

    Afterwards

    An honest recommendation

    Even when it says: build nothing for now.

  2. Step 2

    Clarification

    Before anything is built, we clarify scope, workflow and open questions. This is a separate, bounded engagement. What it covers is agreed in writing beforehand.

    From youOne person who knows today’s workflow and answers our questions.

    Concept & proposal

    Customer portal for a wholesaler

    • Stage 1: sign-in and order overview.
    • Stage 2: delivery status from the inventory system.
    • Not included: invoices. The document says so explicitly.

    You decide: build, refine or stop. The concept is yours either way.

  3. Step 3

    Build

    We build stage by stage. After each stage you try a working version, not slides.

    From youYour feedback on each version.

    Afterwards

    A version to try

    At a test address. You say what fits and what is missing.

  4. Step 4

    Operation or handover

    Your system goes live. Code, data and access belong to you. So you can choose: we run it for you, or we hand it over completely to your team or another provider.

    From youOne person who gives approvals, for example for larger updates.

    Afterwards

    Operations plan and monthly report

    Or the handover package: source code, access, documentation, onboarding.

    Operations & support
A customer portal for a wholesaler.

First the consequences.Then the decision.

New wishes come up along the way. That is normal. Before we change anything, we say what it means for scope, timing and price. Then you decide: now, later or not at all.

Before we change anything, this is written down:

  • ScopeWhat comes in, and what waits for it.
  • TimingWhich stage moves, and by how much.
  • PriceWhat the change costs, before you decide.

Without your decision we change nothing about the agreed scope.

Tell uswhat should change.

We get back to you and arrange the intro call. Afterwards you know which starting point fits your project, even when the answer is: build nothing for now.

To start, we need: your goal, how things work today and who decides on your side. Please do not send login details or customer data through the form.

You talk to

  • Patrick HofbauerInterface design, full-stack, mobile
  • Luc ThieryAutomation, AI & RAG, backend