Skip to content

How we work

Clear scope. Weekly proof. Software that holds up.

Every VAUG project runs on the same rhythm: diagnose first, agree the outcome, show working software every week and stay after launch.

  • Diagnose first
  • Weekly demos
  • Friday update
  • One accountable lead
Book a strategy callSee case studies

Illustrative example

Our philosophy

Most projects fail quietly, long before launch.

They fail when nobody questions the brief, when progress lives in status reports instead of software, and when the team that built it disappears the week after go-live.

So we start by diagnosing the real problem, we show working software every single week, and we stay on to measure what happens next. AI makes us faster. Engineering discipline makes that speed safe.

Commitments

Six commitments on every project. 

  • One accountable lead

    A single senior person owns your project, answers your questions and never passes you around.

  • Weekly demos

    Working software on screen every week, so you judge progress by what you can click.

  • A Friday update

    A short written note every Friday: what shipped, what's next, risks and decisions we need.

  • Your code, your accounts

    Repositories, cloud and third-party accounts are in your name from week one.

  • No surprise invoices

    Changes are scoped and priced before any work starts. Fixed means fixed.

  • We stay after launch

    Monitoring, fixes and improvements, with a care plan agreed before go-live.

Before we start

From first call to kickoff. 

Eight steps, usually done in one to two weeks. Nothing is signed until you've seen a clear scope and price.

01

30 minutes, free

First call

Tell us what you want to build or automate. We ask a lot of questions and tell you honestly if we're the right fit.

1 / 8

Delivery cycle

The delivery cycle, every week. 

Five stages on a loop. Each lap ends with working software and a written update.

Week1and repeat

Stage 1 of 5

Align

Agree this week's goals with you, based on last week's demo and what we learned.

What you get

  • Weekly goals
  • Priorities
  • Risks

Quality

Our quality checklist. 

Nothing reaches production without passing these nine checks.

  1. 01Peer code review on every pull request
  2. 02Automated tests run in CI before any merge
  3. 03Accessibility checked against WCAG 2.2 AA
  4. 04Performance budgets for page speed and API latency
  5. 05Security scan for dependencies and secrets
  6. 06AI features tested with evals and edge cases
  7. 07Staging demo signed off by you
  8. 08Monitoring and alerts set up before launch
  9. 09Handover docs and runbooks written as we go

AI with guard rails

Where AI helps, and where people decide. 

We use AI across the whole lifecycle. We never let it make the calls that matter.

AI accelerates

  • First drafts of boilerplate, tests and migrations
  • Reading large, unfamiliar codebases quickly
  • Generating test data and edge cases
  • Drafting documentation and release notes
  • Spotting likely bugs and code smells
  • Research and comparison of libraries and APIs

Humans review and decide

  • Architecture, data models and security design
  • Every line of code before it merges
  • What ships, and when
  • Anything touching payments, health or personal data
  • Trade-offs discussed with you
  • Final QA and sign-off before release

Engagement models

Six services. One way of working. 

The same AI-first delivery, whichever service fits. Pick one, or combine them.

Questions We Hear Often. 

  • How quickly can you start?

    Most projects kick off within one to two weeks of the first call. Dedicated developers can often start within days.

  • Who will I talk to day to day?

    One accountable lead, who is senior, technical enough to answer real questions, and responsible for your project from kickoff to after launch.

  • What happens if my requirements change?

    We scope the change, tell you the effect on time and cost, and only start once you agree. On a fixed-price build the original scope and price never move.

  • Do you use AI to write the code?

    We use AI tools to move faster, then review every line. Architecture, security and anything sensitive is designed and checked by senior engineers.

  • Who owns the code and IP?

    You do. Our contracts assign IP to you, and the code lives in your repositories from the first week.

  • How do you report progress?

    A live demo every week and a short written update every Friday: shipped, next, risks and decisions needed. You also get access to the board and repository.

  • Can you work with our in-house team?

    Yes. We regularly join existing teams, follow their processes and tools, and share our demo and update rhythm if it helps.

  • What happens after launch?

    We agree a care plan before go-live: monitoring, fixes, updates and improvements, on a monthly plan or as needed.

Get in touch

Tell us what you're planning.

Share a few lines about your idea, workflow or project. A senior lead replies within one business day.

  • Free 30-minute strategy call
  • NDA on request
  • Proposal within 48 hours
hello@vaug.in Our offices

We reply within one business day. No spam, ever.

Keep exploring

More about VAUG. 

See how we'd run
your project.

Free 30-minute strategy call · NDA on request · Proposal within 48 hours

Book a call