Shape the product before it ships — on your real supplier portfolio.
Free or compute-cost. You bring the portfolio and the feedback; your supplier files take shape while you steer what ships. The application below is six questions and takes under three minutes.
Design partners, not beta testers.
The pilot cohort is a small group of mid-market companies in NIS2 scope who will use Vittnor — Supply Chain Assurance for the mid-market — against their real supplier portfolios while we are still shaping the product for production-ready release in Q4 2026. Their feedback decides what ships, what gets refined, and what gets cut.
This is not a public beta. It is a small number of named partners we agree to work with intentionally, because the value of the cohort comes from depth of engagement on both sides. And the workflow you shape is the one your team runs at V1.
You do not need a worked-out supplier-assurance programme to apply — arriving with a spreadsheet, or with nothing but the obligation, is a normal starting point. The workflow supplies the structure: scope first, then suppliers, then evidence. What the cohort needs is your real portfolio and honest feedback, not maturity.
A working file — and four written commitments.
No vague "benefits." The file is the outcome; the four commitments below it go into the pilot agreement explicitly.
A working supplier file, not a sandbox
You run your real portfolio from the first review — suppliers scoped, evidence recorded with reviewer attribution, every decision landing in the trace. NIS2-shaped exports work from day one, so what builds up during the pilot is the supplier file you'd otherwise still be assembling in spreadsheets.
Free or compute-cost access
No license fee for the pilot. You cover only the Azure compute your tenant consumes.
Founder-level engagement
A direct line to the founder through the engagement. Slack channel, weekly availability, no support-tier escalation.
Roadmap influence
Pilot members shape what ships at production-ready. The most-requested capabilities from the cohort are what the development team builds first.
First-cohort terms
Your pilot terms and pricing preference are recorded at kickoff — settled together before V1 commercial launch.
Run a review yourself — two minutes.
Before you apply, click through one supplier review: answer the triage, build the questionnaire, decide on each piece of evidence. Every click writes to an audit log — the same trail the product keeps for real. Fictional data, no signup.
Three modest commitments — nothing punitive.
- A one-hour kickoff
Set expectations on both sides — your portfolio shape, the milestones for the cohort, the cadence we will work to.
- Monthly check-in
Thirty minutes once a month — what is working, what is missing, what has hit you that we should design for.
- Optional case-study consent
No requirement. If the engagement goes well and you want to be a reference, we agree the framing in writing — never silently.
Three steps, no surprises.
- Step 01
The founder reads your application
Personally and quickly. We confirm fit (or honestly say if you would be better served by the Assessment first).
- Step 02
30-minute scoping call
NDA-first. We walk through your supplier portfolio shape, your NIS2 stage, and what onboarding would look like for you specifically.
- Step 03
Decision and onboarding
If both sides agree it fits, we send the pilot agreement and schedule the kickoff. If it does not fit, we say so and route you elsewhere.
Six questions. Under three minutes.
The information here is what the founder needs to scope the call honestly. We do not collect anything we will not use in the engagement.
Not sure if pilot is the right fit? See the productized advisory engagements — sometimes the Assessment makes more sense as a starting point.
Or just want to talk first? Send a quick message instead.
Reads every application himself.