How it works
One job, fixed properly.
We start with a free conversation. If there is a worthwhile fix, we agree the price, the measure and the test in writing, build it on your systems and hand it over. If there isn’t, we say so.
The first conversation
About your problem, not a product.
It is a conversation between two people who know how a service runs.
- Bring
- The job that eats your week, the systems it crosses, roughly how long it takes, and what better would look like.
- You get
- An honest view of whether there is a fix worth paying for, and what it would need from you.
- If not
- We say so. A problem that isn’t worth fixing yet is still worth knowing.
Some jobs build a tool we can reuse with other venues. Those run under their own written terms, agreed before anything starts.
If there is a fix
Agreed first, then built.
Nothing starts, and we touch none of your systems or data, until the terms are agreed in writing.
- 01
Map the job
How it really runs today, with the people who do it, and a starting measure written down.
- 02
Agree the test
The check that will show the fix works on your real data.
- 03
Build the smallest fix
AI and plain software on the systems and data you already have.
- 04
Prove it works
Your team runs it for real; we run the agreed test together.
- 05
Hand it over
You own it. One later reading of the same measure shows what changed.
Terms for a one-off fix
No surprises, no retainer.
- Price
- A fixed price for the piece of work, agreed in writing before it starts. It cannot overrun.
- Payment
- Half when we book, half when the agreed test passes.
- From you
- A named person on your side with a few hours a week, read-only access to the data the job uses, and your team running it in the test week.
- Ownership
- Once paid, you own the fix outright. We keep our general methods and tools.
- After handover
- For 21 days we fix anything that doesn’t do what we agreed. Anything new is quoted separately before it starts. There is no monthly plan.
- Your data
- Read-only where possible, only after written terms, and if the job involves personal data the terms cover how it is handled first.
Some jobs build a tool we can reuse with other venues. Those run under their own written terms, agreed before anything starts.
Kaplink has not yet published a client case study. The first will appear after delivery, an agreed impact reading and the client’s written approval.
Compare notes
Bring one repeated job.
Tell us the job, the systems it crosses and what better would look like.
Email hello@kap.link · how we handle your data
Email Ollie