Engagement

How we engage & tools

Methodology, operating modes, and the AI toolchain we run daily.

How we work with you

How Viteus works with you. Most engagements start with a forward-deployed build: engineers embed in your team and ship a new AI application to production. Once something is live, the ARME lifecycle covers how we assess, fix, run, and grow it.

How we deliver

Forward-deployed engineers, not a spec thrown over a wall

A product engineer works on one capability for many customers. A forward-deployed engineer works on many capabilities for one customer — yours. Our engineers work inside your repos, your cloud accounts, and your sprint cadence, because the part of an enterprise workflow that resists a discovery call is exactly the part that's left to build.

You cannot infer from a discovery call how a specific company closes its books. So we don't try — we sit with the people doing the work and learn what your business actually calls things and how those things actually move. Almost none of that is written down.

  1. Embed

    Engineers join your repos, cloud accounts, SSO, and ceremonies. Week one is spent learning your systems and the real process — not the documented one.

  2. Discover

    We find the workflow worth automating and pressure-test whether it needs AI at all. If deterministic software is the better answer, that's the recommendation you get.

  3. Build

    Working software on your real data inside a short time box. A single agent with well-scoped tools first; more architecture only where it earns its keep.

  4. Prove

    A versioned eval set and a calibrated judge, wired into CI so every prompt, model, and retrieval change is scored before it ships.

  5. Harden

    Layered guardrails, tool risk ratings, human checkpoints on irreversible actions, audit logging, and OWASP LLM Top 10 coverage before real users arrive.

  6. Transfer

    Source code in your repo with named commit attribution, documented architecture, and your engineers coached to own it. The exit is part of the engagement.

See how a build engagement is scoped

ARMEAudit, Rescue, Run, EvolveOnce the app is live

The post-launch lifecycle for applications already in production — whether we built them or your team did.

App-level lifecycle (ARME)

Build · Manage

Select Audit, Rescue, or Run for phase proof — trust highlights, hardening depth, and operations SLAs. Evolve follows the same delivery model once the foundation is stable.

Grow

Evolve

Features on a predictable cadence without rebuilding a fragile foundation.

Continuous feature delivery once the foundation is stable

How delivery works

From first conversation to live support

Mobilize when leadership needs alignment first; otherwise we move straight into assessment, team assembly, and execution. Sequencing flexes to urgency and size.

  1. Mobilize (optional)

    Executive masterclass or PM / architect / engineering bootcamp to align leadership before tactical delivery.

  2. Assess

    Capability audit (maturity) plus portfolio audit (per-app risk). Outputs: capability roadmap and per-app treatment plan.

  3. Per-app audit

    Sized technical review—architecture, security, performance, coverage, and AI-appropriate test scope.

  4. Team assembly

    POD matched to stack and complexity for Build or Manage; test leadership assigned.

  5. Onboarding & sprint zero

    Tooling, repos, comms; baseline test plan, CI/CD, monitoring, stakeholder handoffs.

  6. Execute + transfer

    Sprints, health metrics, shadowing → pairing → leading against an explicit transfer model.

Delivery runs through Viteus — forward-deployed engineering pods based in Vietnam, with a Viteus Delivery Lead as your single point of contact.

Delivery model

Team Composition

Whether you Build or Manage, Viteus assigns a delivery team in a POD format — senior oversight plus Vietnam delivery talent, sized to your roadmap. Same bench discipline for greenfield build, managed evolution, or backlog acceleration.

  • Tech lead / architect

    Part-time (typ. 20–40%)

    English-facing technical direction, reviews, and alignment to your roadmap.

  • Test manager / test lead

    Full-time or part-time

    Owns test strategy, planning, controls, environments, data, and defect governance.

  • Full-stack developer(s)

    Full-time

    AI-native delivery using modern agent workflows daily; refactors, features, fixes.

  • QA / test engineer(s)

    Full-time

    Functional, regression, E2E, performance, and AI-specific tests per the AI Vibe Test Framework.

  • BA / product liaison

    Part-time

    Requirements, acceptance criteria, bridge to your PM ownership.

  • DevOps engineer(s)

    Shared (typ. 10–20%)

    Infra, CI/CD, monitoring, incident response—shared across pods for efficiency.

Know what you want to build? Let's scope it.

Describe the workflow and we'll give you a straight read on what we'd build first, how we'd embed, and what it would take.

Book my 20-min scoping call

Free. No deck, no pitch — a straight read on your situation.

If the workflow doesn't warrant an AI application, we'll tell you that too — and you'll have it in writing.

  • NDA before access
  • Read-only & revocable by you
  • Named engineers
  • Code deleted after engagement

How we handle your code →

Already have something live? Start with the Express Audit →