React gets the agency attention. Vue gets the team-fit and team-velocity.
Buyers already on Vue aren't looking for an agency to migrate them off it. They're looking for an agency that can ship into the codebase they already have.
Shipped Vue components in production
- EasyshipRate calculator card
100+ calculators · 550+ couriers · server-rendered per country pair
- OntickTicket tier selector
Adult Weekend · Adult Saturday · Adult Sunday · Child Saturday
- PESTender comparison row
Supplier responses normalised · best-deal surfacing · 300 clients
- All White LaserContract status pill
$5M in contracts · 500 docs · daily-operator UI
What you get
Six engagements.
We pair Vue with whatever the backend already is, most often Laravel, sometimes Node, sometimes a Python service. The pattern works.
Greenfield Vue 3 + Nuxt 3
TypeScript, Pinia, Vue Router. Composition API throughout. No options-API legacy unless we're upgrading something.
Vue + Laravel (our most-shipped pairing)
Inertia, REST, or GraphQL depending on the project's posture. We've shipped this combination on Ontick, PES, and AWL in production.
Vue + Node
Where the team's preference is Vue but the rest of the stack is JS. Same Vue UI patterns, JS-native backend.
Vue 2 to Vue 3 migration
Options API to Composition API without burning the codebase. Incremental conversion, dual-rendering safety nets, behavioural parity tests.
Performance work on grown-up Vue
Code splitting, lazy loading, render audit, virtual list for large data UIs. The work that keeps a 50-component app from regressing.
Nuxt SSR / SSG
SEO-sensitive marketing surfaces, calculator landing pages, product directories. Server-rendered Vue with the cache-key discipline of Next.
The stack pairings matrix
Where Vue actually wins.
Frequency of Vue use across backend and product-surface combinations, based on our actual portfolio. Dot size is how often we reach for it. An empty cell means it's a fit, just not a default.
| Backend / Surface | Greenfield SaaS | Internal Tool | Calculator / pSEO | E-com Frontend | Mobile Web |
|---|---|---|---|---|---|
| Laravel | 2 of 3 | 3 of 3 | 1 of 3 | 2 of 3 | 1 of 3 |
| Node.js | 2 of 3 | 2 of 3 | 2 of 3 | 2 of 3 | 2 of 3 |
| Python | 1 of 3 | 2 of 3 | 1 of 3 | 0 of 3 | 0 of 3 |
| WP REST | 0 of 3 | 1 of 3 | 2 of 3 | 1 of 3 | 1 of 3 |
| Sanity | 1 of 3 | 0 of 3 | 2 of 3 | 1 of 3 | 1 of 3 |
Vue + Laravel against Internal Tool is the densest cell: that's PES, AWL, and Ontick's customer side. Calculator / pSEO is where Nuxt + Sanity / WP REST also lands (Easyship).
Evidence
Four named platforms, each with a different reason Vue was the right call.
Vue for data-dense UIs
$40M-valuation shipping SaaS. 550+ courier integrations. 100+ calculators with country-pair landing pages. Vue's component model fits dense, repeating components with shared interaction logic: exactly what a courier ranking interface is.
Vue + Laravel ticketing
UK event management portal. £90K+ in sales, 230K+ tickets booked. Laravel handles ticket-tier and multi-day-event logic. Vue handles the high-touch ticketing UI. Deliberate pairing, not a one-off.
Vue inside a custom ERP
Three integrated modules (Tenders, CRM, Accounting). Tender module's automated supplier-response analysis surfaced through Vue. Around 300 industrial and commercial clients, $1M in tenders, 800+ broker hours saved.
Vue inside contract operations
All White Laser
$5M in contracts, 500 contract documents. Vue-heavy UI because operators live in it daily. Laravel underneath. We also built the Cloudflare R2 media migration scripts for this client.
Inline: Ontick case study, and adjacent engagements on Laravel, programmatic SEO (the calculator-engine pattern), and Cloudflare edge (the AWL R2 scripts).
Good fit if
When Vue is the right call
- Teams already on Vue who want an agency that ships into the codebase they already love
- SaaS products with data-dense UIs: calculators, rankings, tender comparisons, contract grids
- Vue 2 codebases stuck on Options API needing Vue 3 modernisation without a rewrite
- SSR-required marketing surfaces (Nuxt) where SEO matters and the team prefers Vue
Probably not a fit
We'll tell you when React is the better call
- Greenfield apps with no team preference. React is fine, we'll build it on React
- Mobile-first cross-platform apps. React Native has a stronger pattern library
- Codebases mid-migration in the other direction (Vue to React) where we'd be reversing the call
Stack we ship on
Vue 3 + Composition API. Nuxt when SSR matters.
Vue.js & Nuxt
Bring the repo. We'll ship into it, not around it.
More in Web & SaaS
Web & SaaS
Mobile Apps
E-commerce & Payments
WordPress
CMS & Platforms
37 services across 7 practice areas.