About Nuxt IT

The Team Behind
Every Line of Code

We're not an agency. We're a boutique software shop of 5 senior engineers who've shipped production systems together for over three years. No account managers. No offshore handoffs. Just engineers who care about what they build.

Meet the Team →Work With Us
Founded
2021
Senior Engineers
5
Projects Shipped
20+
Industries Served
5
Delivery Rate
100%
Abandoned Projects
Zero
Our Story

Built From Frustration With How Software Gets Made

Nuxt IT started because we kept seeing the same story: a client hires a large agency, gets handed off to a junior team, watches the project inflate in scope and cost, and receives software that nobody can maintain six months later.

We decided to do it differently. Five engineers who'd worked together — and respected each other's work — formed Nuxt IT LLC in 2021. No hierarchy. No account managers in the middle. You talk directly to the engineers writing your code.

Three years later, every project we've started, we've shipped. We've never walked away from a client. That's not a marketing claim — it's the one metric we actually care about.

Company timeline

  1. 2021
    Nuxt IT LLC Founded

    Five engineers who'd shipped production systems at other companies decided to work together on their own terms. First client signed within 60 days.

  2. 2022
    First Industrial Client — Mining & Chemical

    Replaced a company's entire Excel-based production tracking with a real-time web system. Zero downtime migration, launched on schedule.

  3. 2022
    Mobile Practice Launched

    Added Flutter to the stack. Shipped our first offline-first field operations app for a mining site — fully functional underground with no connectivity.

  4. 2023
    20+ Production Systems

    Crossed 20 production deployments across web, mobile, and automation. Every single one is still running. Not one client has called to say their system broke.

  5. 2024–Present
    Expanding — Still Small on Purpose

    We've turned down growth that would require hiring people we don't know. Quality over headcount. Every engineer on your project has shipped production code before.

What We Believe

The Principles We Actually Work By

Not the kind that live in a PDF on a company intranet. The kind that shape every project decision we make.

  • Direct access, always

    The engineer writing your code is the person you talk to. No project managers relaying messages. No knowledge lost in translation. If you have a question, you ask the person who knows the answer.

  • Ship what we say we'll ship

    We don't start projects we can't finish. Before we write a line of code, we scope carefully. That means sometimes we push back on timelines that aren't realistic. That's not pessimism — it's respect.

  • Code you can hand off

    We'll never be your only option for maintenance. Every system we build is documented, tested, and written as if a competent engineer who's never seen it will have to maintain it tomorrow. Because they might.

  • Solve the actual problem

    We ask "why?" before we start building. The best software we've shipped was often simpler than what the client originally asked for — because we understood the underlying problem better than the proposed solution.

  • Boring where boring is right

    We don't add a new framework to a project because it's interesting. We choose technologies that are mature, well-documented, and that the client's future team will be able to hire for. Excitement belongs in product features, not infrastructure.

  • No bad news surprises

    If something is going to be late, cost more, or isn't going to work — you hear it from us first, before it becomes a crisis. We'd rather have a hard conversation early than a catastrophic one at the end.

The Team

5 Engineers. No Middlemen.

Everyone listed here writes production code. Everyone has shipped systems that are still running today.

  • Available
    Nuxt Lead
    Senior Frontend Engineer

    4+ years building SSR and hybrid-rendered applications with Nuxt and Vue. Owns the frontend architecture on every project — from routing strategy to component system design. Has a particular focus on Core Web Vitals and accessibility.

    • Nuxt.js
    • Vue 3
    • TypeScript
    • SSR/SSG
    • Core Web Vitals
  • Available
    React Engineer
    Senior Frontend Engineer

    Specialises in complex, data-heavy React and Next.js applications. Has built admin dashboards, analytics platforms, and multi-tenant SaaS UIs that handle real production load. Strong opinions on component architecture and state management patterns.

    • React
    • Next.js
    • TypeScript
    • React Query
    • Data viz
  • Available
    Backend Architect
    Senior Backend Engineer

    Designs the data layer and API architecture for every project. Deeply experienced with Laravel and PostgreSQL — including complex multi-tenant schemas, queue-heavy workloads, and reporting systems that run over large datasets without hitting timeouts.

    • Laravel
    • Go
    • PostgreSQL
    • Redis
    • API design
  • Available
    Mobile Engineer
    Senior Mobile Engineer

    Leads every Flutter project from architecture to App Store submission. Has built offline-first apps for environments with no connectivity, barcode-scanning warehouse tools, and GPS-tracked field reporting apps. Knows the Flutter widget tree better than most people know their own living room.

    • Flutter
    • Dart
    • React Native
    • SQLite
    • Offline sync
  • Tech Lead
    Tech Lead & Architect
    Full-Stack · System Design · DevOps

    The person who shapes how a project gets built before anyone writes a line of code. Defines the architecture, sets up the CI/CD pipeline, makes the technology stack decisions, and reviews everything before it ships. Has run full-stack projects from requirements through to production handover — and has the scar tissue to prove it.

    • System design
    • Laravel
    • Go
    • Vue / React
    • Docker
    • CI/CD
    • AWS / Hetzner
    • PostgreSQL
How We Work

A Process That Actually Works

Simple, transparent, and designed to keep you informed at every step.

  1. Discovery Call

    We ask hard questions before we agree to anything. What's the real problem? Who are the users? What does success look like in 6 months?

  2. Scope & Plan

    A clear MVP, a realistic timeline, and a budget you can count on. We push back on scope creep before the project starts, not mid-delivery.

  3. Build & Iterate

    Two-week sprints. Live demos. A shared project board. You see every decision as it's made — nothing is hidden until the final reveal.

  4. Ship & Support

    Full deployment, documentation, and a post-launch support window. We don't disappear after go-live. We care whether it actually works.

FAQ

Questions About Working With Us

Things people actually ask before they hire us.

How big is the team, really?
5 engineers. That's it. We haven't grown beyond that deliberately — every person on your project is someone whose work we've reviewed and trusted. When you hire us, you're not getting a surprise team of people you've never met.
Where are you based?
Dhaka, Bangladesh — but we work with clients across Europe, the Middle East, and Southeast Asia. We're remote-first and have never found timezone differences to be a real obstacle for well-run projects. We accommodate async communication as a default, not an afterthought.
Do you take on projects of all sizes?
We focus on projects where we can make a real difference — typically 4-week MVPs up to 4-month full-platform builds. We don't do single-page brochure sites or tiny bug-fix engagements; our minimum engagement is one sprint. We also don't take on more than two major projects simultaneously, because attention quality degrades otherwise.
Can I hire one engineer rather than the whole team?
Yes — we offer individual engineer placements for clients who need to augment an existing team. You get one of our engineers working within your process, your tools, and your sprint rhythm. Minimum 4-week engagement. Contact us with what you're looking for.
What's your typical engagement model — fixed price or T&M?
Both, depending on the project. Well-defined projects with clear requirements are better suited for fixed-price contracts — we can commit to a scope and a number. Evolving products or discovery-heavy projects work better on a time-and-materials basis with sprint-by-sprint planning. We'll tell you honestly which we'd recommend after the discovery call.
Do you do ongoing maintenance after launch?
Yes. We offer monthly retainer packages for ongoing development, bug fixes, and feature additions. You can also opt for a one-time handover with full documentation and a 30-day support window. Every project gets at least the 30-day window — we don't disappear right after launch.
Let's Work Together

Want to Meet the Team?

Book a 30-minute call. No pitch. No deck. Just an honest conversation about what you're building and whether we're the right team to help.

Book a Free Call →Send an Email

Response within one business day. Always from an engineer, never from a bot.