Service · Vue
Vue and Nuxt consulting for production teams
Senior Vue work for teams shipping at scale. Architecture, performance, Vue 2 to Vue 3 migrations and hands-on delivery, drawn from the Vue book and years of production code.
Vue projects tend to age in two directions. Either the team rides the Composition API forward and the codebase stays clean, or Options API and Vuex pile up until every new feature feels like a negotiation with the old code.
The hard part is usually not the framework. It's the choices around it. Stores that should be slices. Composables that should be components. Watchers that should be computed properties. SSR turned on without a plan for hydration cost. Once a few of those land, the team slows down.
We work with you to untangle the tricky bits. The first job is a clear read of the code, the data flow and the build. The second is moving the parts that hurt most to a cleaner shape. The third is leaving a team that can keep going on their own.
What we do
Vue engagements, four ways
Pick the shape that matches what you need this quarter.
Architecture review
A full read of the project structure, the Pinia stores, the composables and the data flow. You get a written report with the trade-offs called out and the refactor backlog ranked.
- Composition API patterns and composable boundaries
- Pinia store design, splitting and persistence
- Routing, layouts and code-splitting strategy
Performance optimisation
Bundle audits, hydration profiling and render work that moves the numbers. We work in DevTools, Vue DevTools and real-user metrics, not synthetic scores in isolation.
- Bundle analysis, dynamic imports, async components
- Hydration cost, partial hydration, islands strategy
- Image, font and asset pipeline tuning
Vue 2 to Vue 3 migration
A staged plan for moving off Vue 2 without freezing feature work. We cover the breaking changes, the Pinia move and the script-setup shift, and we run the upgrade alongside your team.
- Compat-mode plan with progressive cutover
- Vuex to Pinia, with store shape preserved
- Options API to script setup, file by file
Hands-on senior delivery
Feature work on Vue 3 and Nuxt 3/4 with the patterns from the Vue book. We slot into your sprint cadence, review pull requests and bring the juniors along.
- Vue 3, Nuxt 3 and Nuxt 4, with TypeScript
- Pull request review with written feedback
- Async-friendly, EU/UK/US timezones
How an engagement looks
Short discovery, written scope, then real work. No long sales process.
- 1
Discovery call
A free 30-minute call. You walk us through the codebase, the team and the deadlines. We ask the awkward questions early so the scope is honest.
- 2
Written scope and proposal
Within two business days you get a written scope with deliverables, timeline and a fixed price or weekly rate. Nothing locked in until you sign off.
- 3
Architecture review or sprint kickoff
Audits run for one week of deep reading and a written report. Delivery work starts inside your sprint cadence from the first day.
- 4
Weekly delivery and code review
A weekly check-in, async PR reviews and a Slack channel for the day-to-day. You always know what's shipping next.
FAQ
Common questions
What's the typical Vue 2 to Vue 3 migration scope?
It depends on store usage and component count. Smaller apps (under 100 components) tend to move in two to four weeks. Larger codebases run alongside feature work for one to three months using the compat build, so the team never freezes.
Do you work with Nuxt?
Yes. Nuxt 3 and Nuxt 4 are the default for new projects we ship. This site itself runs on Nuxt 4 with i18n, sitemap, robots and schema markup. See the Nuxt consulting page for the detail.
Pinia or Vuex?
Pinia for anything new. For existing Vuex codebases we plan a staged move that keeps the store shape stable so feature work is not blocked. The Vue book covers the patterns we use.
SSR or SPA, which should we pick?
It depends on the audience. SSR helps content-heavy pages and SEO-driven traffic. SPA is fine for app-shell, behind-login dashboards. Most projects we ship are hybrid: SSR for marketing pages, client-side for the app.
Composition API on an existing Options API codebase?
Yes. The two coexist in Vue 3 with no penalty. We typically migrate the high-churn files first, leave the stable ones alone, and write all new code in script setup.
Can you audit my Pinia stores?
Yes. Store shape, action boundaries, persistence strategy and selector patterns are part of the standard architecture review. See Vue: The Road To Enterprise for the patterns we apply.
Last updated: 2026-05-20
Next step
Vue codebase that needs senior eyes?
Tell us about the team, the stack and the timeline. We reply within two business days.