Skip to content
vasa.tech

Booking new projects from Jan 2027

AI-native engineering studio · Est. 2019

US-based · Remote-first

AI that ships. Software that lasts. No theater.

Since 2019 we've shipped 90+ products for US companies the hard way. Now every one of our senior engineers runs a fleet of coding agents: same judgment, three times the output.

~/agent.trace replay 1/3
run 4182 · support-agent v3.2 prod · us-east-1
  1. 00.00input"Where's my order #A-2291?"
  2. 00.04retrieveorders_db → 3 rows38 ms
  3. 00.31toolshipping.track("1Z94…")ok
  4. 00.92llmdraft reply612 tok
  5. 01.06guardpii · tone · refund policypass
  6. 01.10evalgroundedness0.97
resolved · 1.1 s · $0.003 · no escalation
  • AI agents
  • Retrieval / RAG
  • Evals
  • MCP servers
  • Voice AI
  • Document AI
  • Fine-tuning
  • Guardrails
  • LLMOps
  • Self-hosted models

(01) Story

Six years of shipping software the hard way. Then we gave every senior engineer a fleet of agents.

Then2019 – 2024

A studio of senior engineers who'd rather ship than pitch.

Lending platforms, clinic software, logistics backends. Systems that still run years later, for clients who still call us. That's where our judgment comes from, and judgment is the one part you can't hand to an agent.

Products shipped
90+
Avg. client relationship
4.5 yrs
Juniors on client work
0

Now2025 →

Same people, same standards. Now each of them runs a team of agents.

In 2025 we rebuilt how we work around coding agents. Agents draft code, tests and docs around the clock; engineers do the part that takes fifteen years to learn: deciding what to build, and what not to. It isn't a new studio. It's the old one, at a speed that shouldn't be possible.

Output per engineer
×3
To first working version
2 wks
Test coverage by default
80%
Merged pull requests per engineer, per week Studio average · 2019–2026
Merged pull requests per engineer per week, studio average. Agents adopted in every workflow in 2025.
YearPRs per engineer per week
20195.6
20205.9
20216.2
20226.4
20237.3
20248.4
202516.9
202625.1

(02) Services

AI products and the software around them — from the first prompt to the 3 a.m. pager.

  • 01

    AI agents & copilots

    Agents that take real actions in your systems: support, operations, sales, back office. With guardrails, audit logs and a human in the loop where it matters.

    Tool use · MCP · Workflows · HITL

  • 02

    Retrieval & knowledge

    Search and Q&A over your documents, tickets and databases that cites its sources and knows when it doesn't know.

    RAG · Hybrid search · Reranking

  • 03

    Evals & LLMOps

    Evaluation suites, regression gates, tracing, cost and latency budgets. The difference between a demo and a product.

    Evals · Tracing · Guardrails · Cost

  • 04

    AI in your product

    AI features inside an existing web or mobile app, without a rewrite: extraction, summaries, smart search, voice.

    LLM APIs · Voice · Document AI

  • 05

    Product engineering

    Web platforms, SaaS and internal tools. Architecture, frontend, backend and the unglamorous parts in between.

    TypeScript · React · Python · Go

  • 06

    Mobile apps

    Native iOS and Android, or cross-platform when the budget says so. On-device models when data shouldn't leave the phone.

    Swift · Kotlin · React Native · Core ML

  • 07

    Cloud, data & MLOps

    Infrastructure as code, data pipelines, GPU inference and a cloud bill you can explain to your CFO.

    AWS · GCP · Kubernetes · vLLM

  • 08

    AI audits & rescues

    Where AI will actually pay off, what data it needs and what it costs to run. Or a rescue for the pilot that never left the demo.

    Workshops · Data review · ROI model

(03) How we build

Every engineer here runs a team of agents. Every merge has a human name on it.

  1. 01Human

    Spec

    A senior engineer turns the goal into a written spec, interfaces and acceptance tests.

  2. 02Agents

    Draft

    Coding agents draft the implementation, tests and docs in parallel branches. Hours, not sprints.

  3. 03Human + agent

    Review

    A senior reads every line. A review agent checks security, edge cases and style before they do.

  4. 04CI

    Eval gates

    Unit, integration and eval suites run on every merge. Scores are allowed to go one way: up.

  5. 05Human

    Ship

    A named engineer approves the release and stays on call for it. Accountability doesn't get automated.

Typical agency vasa.tech
First working version
6–8 weeks
2 weeks
Test coverage
What the budget allows
80%+ by default
Documentation
At the end, if ever
Updated with every merge
Code review
One busy human
Senior + review agent
AI features
A demo for the board
In production, with evals

(04) Selected work

Most of our work is under NDA. The results don't have to be.

C—01HealthtechTexas2025–now

Visit notes for a 14-clinic physical therapy group

Sessions are recorded with patient consent. The system drafts SOAP notes into the EHR and flags missing billing codes; therapists review and sign. HIPAA-compliant, runs in the client's AWS account.

−48 min

Documentation per therapist, per day

Speech-to-text · LLM · FHIR · AWS

C—02FintechNew York2025

A KYB review copilot for a small-business lender

Reads formation documents and bank statements, checks state registries and sanctions lists, drafts the analyst memo. Analysts still make every decision. Live in ten weeks.

−55%

Analyst time per application

Python · LLM · Postgres · AWS

C—03E-commerceCalifornia2025

Support agent for a DTC brand with 9,000 tickets a month

Connected to Shopify and the help desk: order status, returns, exchanges. Every release gated by a 400-case eval set built from real tickets; anything unclear goes to a person.

41%

Tickets resolved without a human

TypeScript · MCP · Shopify · Gorgias

C—04InsuranceOhio2026

Claims intake for a regional property insurer

First-notice-of-loss emails, photos and PDFs become structured claims in the core system, routed to the right adjuster. Adjusters stopped retyping and started reviewing.

−31%

Handling time per claim

Python · Vision LLM · Guidewire · Azure

References available on request — ask us

(05) Process

First call to production in twelve weeks. A demo every Thursday along the way.

A typical 12-week build Weeks →
010203040506070809101112
DiscoveryW1
Design & prototypeW2–3
BuildW3–10
Evals & QAW3–11
LaunchW10–11
Run & evolveW12→
Milestones
Estimate Prototype Beta Go-live
  1. Step 01 · W1

    Discovery

    Workshops, a look at your data, risks. You get a written scope, an eval plan and an estimate you can budget around.

  2. Step 02 · W2–3

    Design & prototype

    Flows, UI and architecture, plus a working prototype on your real data. Not a clickable mock.

  3. Step 03 · W3–10

    Build

    Agents draft, seniors decide. Staging from day one, a demo every Thursday, every merge signed off by a human.

  4. Step 04 · W10–11

    Launch

    Eval gates, load tests, a security review and a staged rollout. Launch day should be uneventful.

  5. Step 05 · W12→

    Run & evolve

    Monitoring for quality, cost and drift. Support with an SLA, or a clean handover to your team.

(06) Engagement

Three ways to work with us. Prices on the page, not after three calls.

Model 01

AI pilot

Prove it on your data before you commit. Four weeks, fixed price, a clear go/no-go at the end.

from$35k/ 4 weeks

  • —Use-case and data assessment
  • —Working prototype on your data
  • —Eval suite with baseline scores
  • —Production plan with run-cost estimate
Book a pilot

Model 02Most common

Dedicated AI-native team

A tech lead and two senior engineers, each running their own agents, working only on your product. QA and design as needed.

from$48k/ month

  • —Team assembled in 1–2 weeks
  • —Scale up or down monthly
  • —Agent tooling included, no extra seats
  • —Delivery manager on our side, at no extra cost
Assemble a team

Model 03

Product build

You know what you need. We agree on scope, price and date after discovery, then ship it.

from$90k/ project

  • —Paid discovery, credited to the project
  • —Fixed price and timeline
  • —3-month warranty after launch
  • —Full IP transfer: code, prompts, eval sets
Discuss a project

(07) Stack

Boring where it matters. New where it pays off.

Models
Claude / GPT / Gemini / Llama / Qwen / Mistral / Whisper
AI tooling
MCP / LangGraph / pgvector / Qdrant / Langfuse / vLLM
Frontend
TypeScript / React / Next.js / Vue / Svelte / Tailwind
Mobile
Swift / SwiftUI / Kotlin / Jetpack Compose / React Native / Core ML
Backend
Python / Go / Node.js / Kotlin & Java / Rust / .NET
Data & infra
PostgreSQL / ClickHouse / Kafka / AWS / GCP / Kubernetes / Terraform

(08) Studio

We're a studio of forty-odd senior engineers across four US time zones, each with their own fleet of coding agents. We don't put juniors on client work. The agents do the junior work; the seniors own every result.

Founded
2019
Senior engineers
40+
AI systems in production
20+
Avg. years in production
12 yrs

How we work

  1. /01

    Senior by default

    Everyone on your project has shipped and supported production systems. Agents multiply experience; they don't replace it.

  2. /02

    Evals before vibes

    Every AI feature ships with a test set built from real cases and a score it has to beat. If we can't measure it, we don't launch it.

  3. /03

    You own everything

    Code, prompts, eval sets, fine-tuned weights and cloud accounts live in your organization from day one. No lock-in.

  4. /04

    Bad news travels fast

    If scope, risk or a model's behavior changes, you hear about it the same day, together with options, not excuses.

(09) Clients

What clients say when we're not in the room.

“We'd burned two quarters on an AI pilot that never left the demo. They had it in production in ten weeks, with an eval dashboard our compliance team actually trusts.”
VP EngineeringFintech · New York
“Our therapists stopped taking notes home. Nobody had to be convinced to use it.”
Founder & CEOHealthtech · Austin
“They were the first vendor that told us what not to automate. Adjusters still make every call; they just don't retype emails anymore.”
VP ClaimsInsurance · Columbus

(10) Careers

We're hiring engineers who'd rather ship agents than talk about them.

Fully remote across the US, flexible hours, an uncapped model budget and no more than one project at a time. Send a CV and a link to something you've built.

(11) FAQ

Questions we get on the first call.

Which models do you use?

Whatever wins on your data. Frontier APIs from Anthropic, OpenAI and Google for reasoning-heavy work; open-weight models like Llama, Qwen or Mistral when data has to stay in your cloud or costs need to drop. We benchmark candidates on your eval set before picking one, and keep it swappable.

Will our data be used to train models?

No. We use enterprise API terms with zero data retention, or self-hosted models inside your cloud account. Your data, prompts and eval sets stay yours, and we're happy to sign a DPA or BAA.

How do you make AI reliable enough for production?

Evals first. Every AI feature gets a test set built from real cases, automated scoring and regression gates in CI. On top of that: guardrails, fallbacks, tracing in production and a human in the loop wherever a mistake is expensive.

Doesn't AI-written code mean lower quality?

Not when seniors are in charge. Agents draft code, tests and docs; a senior engineer designs the system, reviews every line and owns every merge. In practice you get more tests and better documentation than a traditional team has time for.

What does a typical project cost?

AI pilots run $35–60k. Most production builds land between $90k and $350k, depending on integrations and compliance. Dedicated squads start at $48k a month, and senior engineers on hourly engagements are $175 an hour. You get a written estimate after the first call.

How fast can you start?

An AI pilot can start within a week of signing. Dedicated teams usually take one to two weeks to assemble.

Where is your team based?

In the US, all of it. We're a US company with engineers from Eastern to Pacific time, so your team works your business hours: no overnight handoffs, no 6 a.m. calls.

Who owns the code and the prompts?

You do. IP transfers in full with each paid invoice: code, prompts, eval sets and any fine-tuned weights. Repositories, cloud and model-provider accounts live in your organization from the start.

Can you take over a stalled AI project?

Yes, it's a big part of what we do. We start with a one-to-two-week audit of the code, data and evals, and give you a written report with risks, quick wins and a plan, whether or not you continue with us.

How do you invoice?

Monthly, in USD, under a US contract. Pilots and fixed-scope projects are billed by milestones; teams by the month, with time reports attached. Model and cloud usage is billed at cost, or straight to your own accounts.

(12) Contact

Tell us what you're building.

A tech lead, not a salesperson, replies within one business day. The first call is free and comes with an honest opinion on whether AI is the right tool at all.

Write to us

01 — What do you need?
02 — Budget
03 — Timeline

Opens your email client with the brief filled in. Nothing is stored on this site.