Hire Nuxt.js developers who stay on after launch

They work as part of your team. A typical week is building pages, shared layouts and reusable pieces in a current Nuxt project, plus the small server behind it and the wiring to your editing tool or an internal tool. They decide how each page is served and chase the odd fault that comes from a page being built twice, once on the server and again in the browser. They join your catch-ups, take jobs from your board and put changes forward for your people to approve. If you would rather hand over one self-contained piece and take it back finished, we price it that way instead.

Faster than a hiring round, because the slow parts of a hiring round are not in it. After the first call you get the job, the dates and the figure in writing, and the start date is one of the things written down. What sets that day is who is free, how big the piece of work is and how long your own access approvals take. There is no advertising, no shortlist, no notice period and no agency fee. If we cannot staff your work in a sensible time we say so on the call rather than hold the slot.

We quote one fixed figure for one agreed job rather than publishing a daily rate, because the number depends on what the engineer is being asked to own. After the first call you get it in writing: what gets built, in what order, by when and the price. You approve that before any code is written. If what you want changes partway through, we quote again in writing rather than letting hours quietly stack up. Anything ongoing once the site is live is a separate monthly fee, sized to what we are looking after.

Yes. By default we work inside your codebase, your automatic checks, your branches and your approval process. Your team approves everything, so nothing lands that your engineers have not seen. We follow your formatting rules, your naming habits and your commit style rather than bringing our own. If you have no rules written down yet, we propose a set at the start, write them down and stick to them, so the project stays consistent long after we have left.

Yes, and we treat it as a mapped piece of work rather than a rebuild. We take stock first: which add-ons have no equivalent any more, where the way you store information has to change, which pieces rely on the old style of writing and which pages will misbehave once they are built on the server. You get a page by page plan with the risky areas named up front, so the site keeps earning while the move happens. We would rather tell you a move is not worth making than begin one that stalls half way.

You can take the code and run it yourself. It is your project, and the handover includes the notes, the settings for putting it live and the automatic checks. Or you can leave it with us. The monthly arrangement covers watching it, fixing within agreed times, applying updates, small improvements and a monthly report on uptime, page speed and what we did. The point is that the people who built the site are the ones keeping it alive, so there is no cold handover to a support desk that has never seen it.