How It Works
A free demo first.
Then one part at a time.
A working demo around how your company runs, then the whole picture, then the part that hurts most, first.
- 1Nothing to pay
A free working demo
Tell us how your company runs and what you’d want it to do, on a short video call or with a few examples; a rough idea is enough. We build a working demo around it and change it until it fits.
- 2The price
The whole picture, one fixed price
We map the whole system with you and agree, in writing, what it covers and one fixed price, before work starts. Then we start where it hurts most.
- 3Included
Implementation, included
Set up for how you work, the data you already have cleaned up and loaded (paper too), tested on your own documents, your people trained.
- 4Yours
It goes live, and it’s yours
In a cloud account in your company’s name, on top of the systems you already run. The system and the code are yours.
- 5Your call
Later, more if you want it
Anything you add later runs on the same platform, so nothing is rebuilt and nothing is typed twice.
How long? On the first call we tell you roughly how long the demo and the build will take. The timeline is agreed in writing with the price, and the first part goes live before the rest.
How Each Part Is Delivered
Every step leaves you with something.
All of it is part of the price.
| Step | What happens | You get | |
|---|---|---|---|
| 1 | Blueprint | How you work today, how it will work, where the data comes from and how it will be accepted, written down point by point. | The blueprint |
| 2 | Data map and loading | The spreadsheets, documents and email you already have, sorted out and loaded. On day one the system is full, not empty. | A data map |
| 3 | Setup and connections | Logins by role, reading tuned to your own documents, drafts in your voice, your mailboxes and systems connected. | The system, set up for you |
| 4 | Acceptance on your own documents | Checked item by item against your own documents and email. It goes live once it is right. | An acceptance record |
| 5 | Training and go-live | Everyone who uses it is shown how, and whoever looks after it gets the technical documentation. It goes live part by part, in use from the first part on. | Training material and technical documentation |
| 6 | After go-live | We adjust it until it fits how you work, and fix anything that doesn’t work as agreed. | A follow-up list |
On Your Side
What it takes from you: not much.
What we need
- For each part, one person who knows the work — the one who does it today
- Access to the mailboxes, folders and systems the work touches, granted by you and read-only unless you choose otherwise
- A cloud account in your company’s name, with the keys held by you
What you don't have to do
- Write a requirements document — the demo is the requirements: you tell us what’s wrong, we change it
- Install software on everyone’s PC
- Move your data over yourselves — we clean it up and load it in, paper included
- Pay extra for implementation or training — both are part of the price
Afterwards
There's no handover. It was always yours.
From the first day of the real build, everything runs in a cloud account in your company's name, under credentials you hold. When we finish, nothing moves; we just stop having access. Everything we build is yours: the system and the code. If we’re ever not around, your own people or anyone you choose can keep it running.
If you have an IT department, they create the cloud account, hold the credentials and can see everything we do. If you don't have one, we handle the setup with you. What IT will want to know →
Get a free demo