Building a global mobility vertical: why infrastructure beats internal scraping
The meeting where the decision gets made
You are at a global mobility company — maybe an EOR, maybe a relocation platform, maybe a corporate travel service. Your product lead has identified visa-appointment reliability as the single biggest gap between your promise ("hire anywhere in 48 hours") and your reality ("…unless your new engineer is Nigerian and needs a UK visa, in which case good luck").
The question on the whiteboard is: do we build this ourselves, or do we license an infrastructure partner? Your CTO wants to default to "build" because internal tools are usually cheaper and more bendable. Your finance lead wants a TCO model. This guide gives you both.
What 'internal scraping' actually costs to build
Head-to-head: build vs license
Our customers who migrated from internal scrapers put the reclaimed engineers on core product work — their actual differentiator. That's where the real ROI hides: not in the budget line you eliminate, but in the product surface you finally ship because your engineers aren't maintaining a Cloudflare bypass.
The hidden costs build-it-yourself teams forget
1. The portal-change tax. VFS updated its Turnstile integration in early 2026 and broke every in-house scraper we know of for 2–3 weeks. TLS Contact has upgraded Cloudflare Managed Challenge twice in the last year. Each event is a week of engineering downtime plus a week of client-visible breakage. Opaige absorbs that cost across every customer; you absorb it yourself if you build.
2. The legal and compliance surface. An in-house scraper means your company is the data controller for thousands of passport numbers, addresses, and portal credentials. Your Head of Legal now has to sign off on your Turnstile bypass technique. That conversation is not fun. Licensing Opaige means we're the processor, you're the controller, the DPA is standardised, and your Legal team signs it once.
3. The reputation-risk layer. When your in-house scraper gets flagged by a portal and blocks your users, the support ticket lands in your inbox. When Opaige has a portal incident, we post on /status, we fix it, and we wear the reputation cost. You get to tell your customers "our partner is handling it" — which is a much easier conversation than "our engineers are debugging it."
When building in-house actually makes sense
We're not going to argue you should never build. A few situations where in-house is the right call:
- You're operating at 10,000+ bookings a month. The pricing curves flip; your per-booking cost drops below the licensing fee.
- You have a regulatory reason that mandates on-premises data processing (some EU member-state public-sector contracts).
- Visa automation is your actual product, not a supporting feature. In that case you're in our space, and we'd rather talk about a partnership than a licensing deal.
For everyone else — EORs, relocation platforms, corporate travel services where visa booking is one of many features — the maths says license. The time your team saves compounds into whatever differentiator actually wins your market.