Our Take
Open Visa is pitching automation speed (months to minutes) without publishing independent benchmarks or naming a single deployed government customer.
Why it matters
Immigration processing is a genuine bottleneck with public cost data (UK spends £5.7B annually on asylum alone at £12,000 per application). If automation claims hold up, the margin for displacement is real. Right now, they're a capability claim without proof of traction.
Do this week
GovTech buyers: Request a live pilot case study or reference customer from Open Visa before contracting; vendor-only performance claims in this sector carry high implementation risk.
Open Visa targets legacy immigration outsourcers with AI automation
Christopher Claudius, CEO of Open Visa, told CB Insights the company operates in the immigration processing sector, competing to displace legacy business process outsourcers (BPOs) like VFS Global, Silver Bell Group, TLScontact, and Capita. The global market for visa applications, right-to-work checks, and asylum processing exceeds £15 billion annually (company-reported). The UK alone outsources over £1 billion per year to these incumbents.
Open Visa's stated approach centers on AI-native automation. The company claims to ingest unstructured visa applications into a processing pipeline, allow governments to configure custom fusion models for application intelligence, and connect outputs to existing government databases and APIs. Claudius told CB Insights the company aims to compress processes currently lasting days to months into seconds and minutes.
The pitch rests on incumbent inertia. Legacy BPOs, Claudius said, have held market position for decades without significant innovation investment. The UK's asylum processing backlog underscores the scale: the Home Office spent approximately £5.7 billion last year processing asylum applications, at a reported cost of £12,000 per application, with a typical processing time of 12 months (government-reported figures cited by Claudius).
The cost structure is real; the automation proof is not yet public
Government immigration processing is a rare GovTech segment where the financial case is transparent and severe. A 12-month application cycle at £12,000 per case creates measurable incentive for faster, cheaper alternatives. If Open Visa or any vendor can demonstrate a working reduction in either cost or processing time against a named public agency, the narrative shifts from pitch to deployment.
To date, Claudius has articulated the problem cleanly but has not published performance benchmarks, named a live customer, or disclosed pilot results. Vendor-reported speed claims (months to minutes) without independent verification or customer reference are baseline expectations in enterprise software sales, not evidence of capability. GovTech procurement also involves regulatory sign-off, interoperability testing, and data governance constraints that product speed alone does not address.
The competitive angle is sound. Legacy BPOs operate on margin-optimized labor arbitrage, not algorithmic efficiency. A new entrant with modern AI tooling and no installed base of slow processes has a structural advantage in cost structure. Whether that advantage survives actual government deployment, security audit, and data residency requirements remains unproven.
Government procurement officers evaluating immigration processing vendors
Demand live customer references or a published pilot outcome before issuing RFPs. Speed claims (months-to-minutes) require evidence: a named agency, a baseline process time, a measured outcome, and independent validation. If Open Visa or competitors cannot provide this, the pitch is positioning, not proof. Secondly, clarify what "fusion models" and pipeline automation cover in practice. Immigration processing involves legal determinations, interview scheduling, and document verification. Automation may compress clerical steps without touching the critical path. Ask for a process map showing where time is actually saved, who validates the automation output, and who bears liability for errors.