1. Home
  2. How We Work
How we work

How we work: from discovery to long-term care

A clear process keeps software projects on time and on budget. Here's what happens at each stage — and what you receive.

01

Discovery

Workshops with your team to understand goals, users, workflows and data. We also review your existing systems.

What you receive
  • Requirements document
  • Scope & feature priorities
  • Cost and schedule estimate per phase
02

Design & prototype

User flows and key screens are designed in Figma, then turned into a clickable prototype users can test.

What you receive
  • Wireframes & UI design
  • Interactive prototype
  • Approval before development
03

Iterative development

Work is split into sprints. Each sprint ends with a demo, and you can try the result on a staging server.

What you receive
  • Staging access
  • Regular demos and progress reports
  • A project coordination group
04

Test & launch

Functional, security, speed and device testing. Once approved, the app is released to your server or the stores.

What you receive
  • User acceptance testing (UAT)
  • Production release
  • Training and documentation
05

Care & growth

After launch we monitor, fix and build new features through yop/care.

What you receive
  • Monitoring & backups
  • Fixes and updates
  • Next-feature roadmap
Engagement models

Choose the way of working that fits

Fixed-scope project

Features, schedule and cost agreed up front. Good for websites and apps with clear needs.

Phased (MVP, then grow)

Release the core first, then add features in phases based on real use.

Dedicated team (retainer)

Monthly team capacity for products in continuous development.

Maintenance (yop/care)

Updates, backups, monitoring and support for systems already running.

See pricing & estimates
FAQ

Questions about our process

Didn't find your answer? Ask us on WhatsApp.

How often will I get updates?

Every sprint ends with a demo, and day-to-day progress is shared in the project coordination group. Meeting schedules are agreed at the start.

What if requirements change midway?

Change is normal. We note the impact on schedule and cost, and you decide whether it goes in now or in a later phase.

Do we need our own IT team?

Not necessarily. We can handle servers, releases and maintenance. If you have an IT team, we work with them and hand over documentation.