Custom software & cloud services — delivered remotely across Europe

Home  /  How we work

How we work

From first conversation to live system: what actually happens, in what order, and what we need from you along the way.

A fountain pen, glasses and drawing tools on sheets of paper

Step 01

Brief & scope

Every project starts with the requirement, not the technology. We ask what has to work, for whom, and what success looks like — then write that down and check it with you.

  • A short call or email exchange to understand the goal
  • We map what exists today and what will have to change
  • You get a written scope — not a vague estimate

Step 02

Plan & quote

Scope gets turned into an approach and a price. The plan stays visible for the whole project: when something needs to change, we go back to it rather than improvising.

  • Written approach with stages and deliverables
  • A quote in euros (€), approved before work starts
  • Change requests are priced before they are built
A hand-drawn building sketch on a plan sheet
A close-up of a circuit board with electronic parts and capacitors

Step 03

Build & show

We build in stages and show progress as it happens — so decisions are made with something real in front of you, not in the abstract.

  • Regular previews you can actually click through
  • Feedback rounds built into the schedule
  • No big reveal at the end, no surprises

Step 04

Launch & support

Launch is a step, not the finish line. We deploy carefully, hand over properly, and stay available afterwards.

  • Deployment planned to avoid disruption
  • Accounts, code and documentation handed to you
  • Support and maintenance arrangements if you want them
A meeting room with a long table and rows of chairs

What we need from you

Projects go well when three things are clear. That is usually all it takes.

Access

Accounts, systems and the people who know them — shared when the work needs them.

Decisions

One decision-maker on your side, so feedback rounds are quick.

Feedback

Honest reactions at each stage — early feedback is cheaper than late changes.

Start a project

Scroll to Top