One week. Then something runs.
Your people already use AI. Are you getting what's in it?
Almost no one can answer that. Not because nothing is happening, but because it is nowhere recorded, measured or shared.
The sprint in brief
One fixed price, one working week
5 working days
From a chosen job to a working prototype in your own environment.
€ 5.000
Fixed price. Intake, the sprint itself, implementation in your environment, handover and evaluation.
Real data
On your own process and your own data, with real users. Not a demo on a laptop.
Choose afterwards
Run it yourself or hand it to us. Cancellable monthly.
Sound familiar?
Why it usually stops at that one experiment
There’s one person in the office who’s handy with it
You know exactly who I mean. Someone in administration or in work preparation who figured it out and is genuinely good with it. They do in ten minutes what used to take an hour.
And that’s where it stops. What she knows, nobody else knows. If she’s away for a week, everyone goes back to the old way. That’s not her fault: it sits in one person instead of in your company, and nobody ever came by to change that.
What ends up on the table doesn’t fit
You’ve been hearing for two years that you have to do something with AI. And what ends up on the table is a presentation, or a three-month engagement with a quote for forty thousand euros. So you don’t do it. Completely fair.
We come by for two hours, not just to you but to the people who do the work. We pick one thing that really costs time and agree on how we’ll measure whether it works. That same week we build it.
Prototype first, then production-ready
At the end of the week there’s a working prototype in your own environment, with real data and real users. That is deliberately a prototype and not a production system: security, test coverage, continuity and support belong to production and cost more than five days.
If the outcome is good, we make it production-ready. If it turns out to be nothing, you’ve known that after a week instead of after a quarter.
How it goes
Four steps to a working prototype
The first three steps cost you a couple of hours in total. Then the week begins.
Digital introduction
A short conversation in which we test your question. If it doesn't fit in a week, we say so here.
Digital intake
A questionnaire you fill in yourself. That's where the ideas from your side of the process come from.
Preparation call
A briefing on what we expect from each other and how we'll measure it at the end of the week.
The sprint
Five working days of building. Monday two hours on site and one thing chosen, Monday afternoon we start, Friday it's live with someone at your end who manages it and a bill you can follow.
Examples
What we usually build
Search across your own documents
Contracts, quotes and manuals in one search box, with the source attached so you can check the answer.
Quotes and reports
that lay themselves out, from your own data, every time in the same format.
Minutes you no longer have to write up
from meeting to agreements and actions, without anyone typing it out afterwards.
Making Microsoft 365 usable
Unlocking everything that's already in there, instead of scattered across folders and inboxes.
FAQ
Frequently asked questions
One week. Then something runs. Talk it through with Bas. Ask yourself: what would you hand over straight away if you got two days a week of administrative help? Send a few lines about what costs you too much time, and within a day you'll hear whether it fits in a week. And if it doesn't, we'll just say so. Book a moment with Bas or one of the team.
-
The introduction, the digital intake, the preparation call, five working days of building, the implementation in your own environment, the handover and the evaluation. Integrations that need an external vendor to open something up fall outside it; we test that in the introduction, not halfway through the week.
-
A working prototype in your own environment, with real data and real users. Deliberately not a production system: security, test coverage, continuity and support belong to production and don’t fit in five days. If the outcome is good, we make it production-ready.
-
You choose. It sits in your own account under your own name, so you can manage it yourself and pay only your AWS usage. Or we manage it, from € 350 per month by number of modules, with model usage passed on at cost and without a mark-up.
-
Keeping it running, growing along with new versions, and every month one A4 with what ran, what it cost and what it delivered. Including up to two hours of support per month, also to chase your software vendor on your behalf. Building new functionality falls outside it; that’s what the prepaid-strip card is for.
-
One small, well-defined job of the kind that now sits in someone’s diary: a file that has to be fetched every Monday, chasing hours, a message that the delivery is on its way. You say which, we build it, and it keeps running afterwards. Not used is not expired; strips carry over to the next month.
-
Because we don’t start over every time. The foundation and the generic building blocks are already there, and we only build the part that’s about your company. Those building blocks improve over time; your data and your processes stay yours and are not shared with other clients.
-
If no one has time that week to answer our questions, it won’t work; say so beforehand, that saves us both a week. And if no one can name what you measure to tell whether it delivers, we don’t build it. Then you’d be paying for something no one can point to and say what it does.
Further reading
Where to read on
Get started
One week. Then something runs.
TechNative in Amersfoort has been building and running the systems behind companies that can't afford to let them slip for years. For us AI is software engineering, not a stray experiment.