A scoping note within ten working days
Whether a ninety day pilot is possible, what would be tested, and what would have to be true at the end for it to count. Or a plain statement that we cannot help.
GOVERNMENT AND PUBLIC BODIES
A pilot with a decision date, not a memorandum.
If you are a ministry, an agency, a region or a public innovation body, you are usually offered cooperation agreements and delegations. What you need is one problem tested against real technologies, inside one budget cycle, ending in a decision you can defend. KyoLink finds the candidate technologies on the other side of the corridor, runs the pilot as one programme, and writes down what happened whether or not it worked.
Four things, and a memorandum is not one of them
Candidate technologies, researched and approached
Named organisations on the other side that fit the problem, approached properly, with the same facts given to both sides in their own language.
One programme, several tracked requirements
Each technology becomes its own requirement with its own counterparty and its own evaluation. They are run as one pilot with one timetable, so your team has one conversation and not five.
One written decision on day ninety
Continue, scale, hand over or stop, with the reason. Counted from the day the pilot starts, and not moved because the answer is inconvenient.
Your policy is yours. The corridor process is ours.
- The cross-border process
- Problem definition, candidate research, approach, preparation, the pilot timetable and the record of what was agreed.
- The accuracy of what each side is told
- A Japanese supplier and a European public body do not share assumptions about procurement, liability or timing. Making those explicit before anyone meets is the work.
- Three roles, written down before anything starts
- Who runs the work, who signs, and who pays. These are three questions with three possible answers and none of them is assumed from another.
- Not funding
- We do not provide the pilot's budget and we do not promise that a programme will fund it. Where a funding route genuinely fits, we say so and the eligibility is checked before anybody writes anything.
- Not procurement advice
- Your rules are yours. We work inside the instrument you choose and we do not advise you on how to run your own procedure.
- Not a result you can announce in advance
- A pilot that fails is a pilot that answered the question. If you need a success to announce on a fixed date, this is the wrong instrument and we will say so at the scoping stage.
- Not a delegation or a memorandum
- Both are available everywhere and neither tests anything. If that is what is needed, there are better partners for it than us.
HOW IT WORKS
Ninety days, counted from the day it starts
A pilot is a container. It produces several requirements, each with its own counterparty and its own evaluation, and it carries one decision over all of them. That is the difference between a pilot and a procurement: a procurement asks who is cheapest at a thing you have already decided on, and a pilot asks whether the thing works here at all.
Before the first day, three things are agreed in writing: who runs the work, who signs the contract, and who pays. For a cross-border pilot these commonly have three different answers, and leaving any of them implicit is how a programme arrives at month four with two organisations each assuming the other was responsible.
The decision date is ninety days from the start. It is counted, not chosen, and it does not move because a supplier is late or because the answer is awkward. On that day the decision is written down: continue, scale, hand over, or stop, with the reason. A pilot that stopped is recorded in the same words as one that continued.
What is published about any of it, afterwards, is published only with your written permission, and nothing names your organisation without a separate permission given for that purpose.
WHERE TO START
Start with the problem, not the technology
The most useful first message describes a problem your organisation already has, in your own words, with the constraint that makes it difficult. You do not need to know which technology would solve it. Finding that is the part we do.
If the question is whether a pilot is even possible, the scoping note answers it in ten working days and costs nothing. It is a short written assessment, not a proposal, and it is as likely to say no as yes.
One problem is enough to start
Send the problem and the constraint. You will have a written answer within ten working days, either way.