One implementation programme, with explicit gates.
The five-phase institutional pathway and the earlier 30–60 day view describe the same indicative programme. The week and day windows below are paired so they cannot be mistaken for two different promises. Actual timing depends on the feeds, controls and decision pace agreed with the customer.
Five phases from scope to cutover
1. Sponsor and control alignment
Week 1 · Days 0–7
Owners: Customer sponsor, Operations and InfoSec · FVI delivery lead
Agree the first reconciliation, decision criteria, security review and environment boundary.
Exit: Signed evaluation scope, owners and measurable proof-of-value criteria.
2. Data and connectivity
Weeks 2–3 · Days 8–14
Owners: Customer data engineering · FVI solutions engineering
Inventory source feeds, approve connection paths, map fields and validate representative data quality.
Exit: Representative data can be traced from source to normalized output.
3. Rules and governance
Weeks 3–5 · Days 15–30
Owners: Customer reconciliation SME and controller · FVI product team
Configure match keys, tolerances, exception categories and human-approval policy.
Exit: First reconciliation and its decision path are reviewed against agreed test cases.
4. Shadow and parallel run
Weeks 5–7 · Days 31–45
Owners: Customer Operations and Risk · FVI delivery lead
Compare results with the incumbent process, investigate divergence and record baseline measures.
Exit: Operations and control owners accept a documented pilot result or change the scope.
5. Controlled cutover
Weeks 7–9 · Days 46–60
Owners: Customer change authority and sponsor · FVI delivery and support
Complete contractual and operational gates, agree rollback, rehearse support and authorize the production cutover.
Exit: The customer approves a bounded go-live with named support and review owners.
What changes the timeline
The reference programme assumes a single in-scope reconciliation and timely decisions from customer engineering, operations, risk and procurement. More products, legal entities, feeds or regions change the schedule. A production date is set only after the control gates, pilot results and rollback plan are agreed.
Review the platform boundary · Start the due-diligence discussion.
Discuss a scoped evaluation with the Falcon Veritas team. Product outcomes and commercial commitments are agreed for each engagement.
Book a 30-min demo