Concept

What happens in this phase

The idea becomes a plan that your team and our team understand.

• 02.01 Requirements Engineering

  Requirements Engineering

  What happens

  We write user stories with acceptance criteria and priorities, discussed together.

  What you get

  A requirements document with no gaps and no silent assumptions.

  • User stories
  • Acceptance
• 02.02 UI/UX Design

  UI/UX Design

  What happens

  We design the screens in Figma and test a clickable prototype with real users.

  What you get

  A clickable prototype you can experience and evaluate before we build it.

  • Figma
  • Prototype
  • User tests
• 02.03 System architecture

  System architecture

  What happens

  We define the data model, API design and stack decisions, and justify them.

  What you get

  A documented architecture, built to last for years.

  • Data model
  • API
• 02.04 Accessibility

  Accessibility

  What happens

  We set the level your product needs and write it into the acceptance criteria: contrast, focus order, keyboard paths, labels. The design is built that way from the start.

  What you get

  An agreed level with testable criteria, reflected in the design and priced into the quote.

  • WCAG 2.1
  • Screen readers
  • Accessibility Act
• 02.05 Security & privacy

  Security & privacy

  What happens

  We work through which personal data occurs, where it lives and who may see it. From that come roles, retention periods and the server location.

  What you get

  A data concept with roles and retention periods, plus the template for the processing agreement.

  • GDPR
  • Processing agreement
  • Roles
• 02.06 Fixed price offer

  Fixed price offer

  What happens

  We turn the agreed scope and effort into a binding quote.

  What you get

  A fixed-price offer: you know what it costs, we know what we're building.

  • Fixed price
  • Clarity