How it works
How we work.
Four steps: an intake, a proposal, building in short rounds, and then delivery and upkeep. You don't need any technical knowledge for it.
From first conversation to software that runs.
- 01
Intake
An hour of conversation, no obligation. You show us what still happens by hand: which file comes from where, who retypes what, where it goes wrong. We keep asking until we understand the process — and we'll say so if software isn't the answer here.
Bring a real quote, order or drawing. We'll ask about volumes, exceptions and who works with it.
- 02
Proposal
You get one proposal on paper: what we build, in which rounds we deliver it, and the monthly fee it runs on afterwards. Hosting, maintenance and upkeep are part of that fee. You read it and say yes or no.
No quote full of options for you to pick from. One proposal, one fee, one schedule.
- 03
Building in short rounds
You see something working early instead of a hand-over months later. Every round delivers a version you can try yourself; whatever isn't right, we adjust in the next round. That way we build in your way of working, not our assumption of it.
What it costs you: looking and responding. Half an hour per round is enough to keep us on course.
- 04
Delivery and upkeep
The software ends up where it belongs: on your own site, in your own systems, with your own people. After that we host, maintain and manage it. One point of contact — you never have to work out who to ask.
It keeps running without you thinking about it: updates, backups, security and someone looking into it when something's off.
What you can expect from us
This is always part of it, without you having to ask.
-
One point of contact
You talk to the person who actually builds your software. No ticket number, no account manager in between.
-
Hosting, maintenance and upkeep
Servers, updates and security are part of the monthly fee. We keep it running, you use it.
-
We'll say so if it can't be done
If software isn't the right answer, or it's less work than you thought, you hear that during the intake — not halfway through.
-
Your data stays yours
Whatever sits inside the software is your property. You get it in a common format whenever you ask for it.
What we need from you
Not much — but these three, or we end up building on assumptions.
-
Someone who knows the process
One person on your side who knows how it works today and can decide how it should work tomorrow. No committee needed.
-
Real examples
A quote, an order, a drawing, an export file. Real cases show you where it pinches straight away; made-up ones don't.
-
A response each round
Look at what's there and say what isn't right. That's what sets the pace — not us.