A problem, not a generic promise.
Decision to prepare, excluded uses, people to involve, constraints, and information and technical prerequisites.
A clear way in, an agreed scopeDon’t start with everything.
Don’t start with everything.
Start from a decision.
The pilot is there to test COGI’s usefulness on a concrete problem. Before launch, we agree objectives, people, data, timescales, reports and investment.
What are you buying?
A defined applied programme: method, configured tools and accompaniment. The scope is set out in the proposal.
When will you see something?
The first report has a deadline to be agreed. Measuring the effects on the process may require a later review.
How much commitment and cost?
Contacts, availability, prerequisites and investment are defined up front. Any model costs must be made explicit.
Prepare the first conversationTell us
Tell us
what needs
to become clearer.
You don’t need a formal specification. The context, the decision still open and the constraint that makes it difficult are enough.
This process prepares your request.
Nothing is sent until you confirm. You can send it from here, or copy it or open it in your email client. Do not enter health data, third-party personal data or confidential information.
Or write to hello@cogi.co Nothing is sent until you confirm. You can send it from here, or copy it or open it in your email client. Do not enter health data, third-party personal data or confidential information.
STEP 01 / 03 · THE CONTEXT
Which organisation are you starting from?
What to agree in the proposalBefore launch,
Before launch,
everything must be readable.
These items describe the scope to be defined, not a package already priced or availability already attested.
Deliverables and acceptance criteria.
Dossier of the discussion, alternatives, evidence, disagreements and verification conditions. What is included is made clear.
A timetable with start conditions.
Duration, availability of contacts, responsibilities and the deadline for the first report. Delivery is kept distinct from the effects on the process.
A hypothesis that can be disproved.
Indicators, baseline and conditions for continuing, revising or stopping the process. No improvement is taken for granted.
Before we meetThe questions
The questions
most often asked.
Is integration with our corporate systems needed straight away?
It is not assumed as a universal prerequisite. The need for integrations, the data required and how they are handled are defined according to the chosen scope and the configuration actually available.
Can we start with just one process?
That is the proposed way to set up the trial: a contained problem, relevant people and agreed verification criteria. Extension is not automatic and requires a later assessment.
Who should take part in the first conversation?
A contact with responsibility for the process, people who know how it works, and technical contacts when the scope involves data or systems. The composition is adapted to the case.
What happens if the pilot does not show usefulness?
The conditions for stopping and revising are agreed in advance. A negative outcome must not be turned into a success story: it is information for deciding whether and how to continue.