Trial month · 3 days on site + 1 month
One programme. One process. Your engineers.
Your customer review process, in production on one programme in 3 days.
We don't sell you a tool to configure. A Koddex engineer spends three days on your site with one of your engineers and starts from how you work today: your customer requirements, your BOM, your tests. Then your team runs it for a month on a real programme or delivery project.
On site, with one of your engineers
We model your programme with your champion: requirements, parts, tests and approvals, imported from your documents and your BOM. No migration, no CAD write-back.
On a real programme
Not a sandbox: your team works in Koddex on a live customer programme or delivery project, with the model, workflows and agents already set up for it.
Success criteria written together
For example: the compliance matrix of the programme up to date, a customer review prepared in under a day, the impact of a change known in under an hour. The trial is paid and deducted from the annual subscription when they are met. Your data stays exportable at any time.
One programme, and the process that costs you most.
One customer programme, never the whole company. We choose the process with you before coming on site: the one where your team loses the most days, or where a gap is found too late.
How the trial runs.
Before
Scope and criteria
We agree on the programme, the process and the 3 success criteria, in writing.
01Days 1 to 3
On site
A Koddex engineer and your champion put the process into production on your data.
02Weeks 1 to 4
Your team at work
Your engineers run the programme in Koddex. We follow up every week.
03End of month
Review against the criteria
Criteria met: the trial is deducted from the annual subscription.
04
What runs during the month.
During the month, your team works on the same technology as our customers in production.
- Every customer requirement linked to its part and its testRequirements, parts, tests and revisions are linked in one model, in your vocabulary. Change one, and you see everything it touches before you approve.
- AI agents that do the engineering legworkAgents read your documents, build models, fill the BOM and trace the impact of a change, through the Koddex MCP.
- With the rigour engineering needsAgents act with the user's rights, on branches. Every action is logged, every change is traced, every release can be frozen.
Example · a first week
▸
Koddex agent
Every agent action logged · scoped to the user's permissions
Bring one programme. We put its review process into production in 3 days.
Start with a conversation about your programme. If there is a fit, we fix the scope and the 3 success criteria together, then come on site for three days.
Before
Scope + 3 criteria
3 days
On site
1 month
Real programme