Outsourcing, Module mode
A block of work for your team.
You supply the specification of a defined part of your system. We build it at a fixed price and hand it over.
Handed over
What you take over from us.
Tests
An increment you can accept.
Logging
You see what is happening.
Handled errors
They end in a controlled way, not by chance.
Failure description
What happens when it goes down.
We cannot supply a runbook for someone else's infrastructure. A failure description for our own piece, yes.
Rules
What applies.
Design
Your team owns it. We build to it.
Price
Fixed for a defined scope.
Acceptance
Verifiable criteria, agreed in advance.
Change of scope
We price it in advance, never after the fact.
After handover
The module is entirely yours. We do not run it.
From the blog
Keep reading
6 min read
How to define a project so the price is not argued about afterwards
Scope as a list of what is and is not in the price, acceptance agreed in advance, changes priced before they are made, and why a fixed price given blind is a bet.
Read the articleBlog
All articles
When your own solution pays off, what to check at handover and how to avoid arguing about the price.
To the blog
Let us start now
Not sure exactly what you want? But you want it now?
Click the first answer. Four quick questions, we will sort out the rest together.
What do you have in hand?
Pick one option. It moves you straight on.