How we work.
Four predictable steps, no surprises. Applies equally to a 2-week Platform Review and a multi-year managed continuation. Selective intake, no consulting theater. The discipline is sustained first on our own sovereign platform — infrastructure as code, centralized identity, controlled secrets, encrypted backups and documented recovery procedures.
Five firm rules.
- 01
Closed scope, milestones and price.
We prefer proposals with closed scope, milestones and deliverables. When a project does not allow it from the start, we frame a discovery phase or a block-based proposal before execution. If rescoping is needed, it is done explicitly and in writing.
- 02
NDA when applicable.
Mutual, standard template or yours. We sign before the first technical session when scope information is already sensitive.
- 03
Visibility of the work.
Visibility of the work and milestones. Where applicable we share repositories, changelogs and progress evidence; where not, we report on artifacts and deliverables transparently.
- 04
Acceptance criteria upfront.
Each milestone has objective checks. Signed before we start, not at the end.
- 05
No unnecessary lock-in.
We prioritize open components and deliver configuration, documentation and runbooks to ease handover. Continuity and exit conditions are agreed by contract from the start.
Four steps. No surprises.
- 01 1 week
Discovery
Technical call with your team. NDA if applicable. We confirm fit and preliminary scope. If it doesn't fit, we tell you before charging anything.
- 02 1-2 weeks
Assessment / Proposal
If a technical Assessment fits, we start it. If not, a closed proposal with scope, milestones, acceptance criteria, price and timeline.
- 03 4-36 weeks
Delivery
Weekly or biweekly sprints, demo at the end of each. Visibility on progress through the agreed channel (repository, changelogs or reporting). Technical meetings as needed, not by agenda.
- 04 Ongoing or transfer
Operation / Handover
If managed continuation applies (selective intake): recurring operation under formal contract. Default path: documented handover with runbooks, configs, accesses.
What you receive, you receive seriously.
- 01
Code and configuration
Where applicable, we deliver infrastructure-as-code, versioned configurations and operational documentation under version control.
- 02
Reference architecture
Up-to-date architecture diagram, recorded technical decisions (ADRs), documented dependencies.
- 03
Operational runbooks
Deployment procedures, common incidents, backup/restore, upgrade, capacity planning.
- 04
Remediation plan or roadmap
In Reviews and Assessments. Prioritized findings (P0/P1/P2), estimated effort, dependencies.
- 05
Reporting
Reporting focused on operational state, risks, changes and next steps. When managed continuation is contracted: monthly cadence and quarterly review with CISO/CIO.
Three ways to engage.
- 01
As prime contractor
Kverno signs directly with the client. Standard for regulated private firms, law firms and European projects.
- 02
As SI subcontractor
We work under a large SI (Indra, GMV, etc.) on public-sector tenders. We bring the platform and operations; the SI keeps the contractual relationship.
- 03
As Filigran technical partner
For clients reaching us via Filigran and needing on-premise deployment. Direct technical coordination with their Customer Success team.
Let's talk.
If you fit any of the three models, we'll confirm quickly. If not, we'll point you elsewhere.