How to Engage

Three ways to work with us. One delivery standard.

Project, retainer, or embedded pod. The shape of the contract changes; the seniority, rituals, and accountability do not.

The Mix

How Our Clients Engage Us.

Most arrive on a project. Most stay on a retainer.

Numbers from the last fiscal year of Vybog Services engagements. The shape of the model matters less than the delivery rhythm inside it — but here is what most clients pick.

43%
Start on a Project
38%
Stay on a Retainer
19%
Run with a Pod
92%
Renew the relationship
Three Models

Project, Retainer, or Pod.

The shape that fits the work. Most engagements start in one model and move into another as the relationship deepens. Switching is friction-free; we explain the tradeoffs in writing.

Project · Fixed scope, fixed fee

A defined deliverable, milestone-billed, with a written scope memo signed by both sides. Best for greenfield builds, migrations, and bounded modernization work.

  • Discovery sprint (1–2 weeks, flat fee)
  • Milestone-based billing tied to demo acceptance
  • Written change-order discipline; no hourly surprises
Most common

Retainer · Monthly capacity

A reserved block of senior hours per month, used flexibly across features, fixes, and growth work. The default model for clients moving from a project to long-term operation.

  • Monthly hour bucket, rolls forward up to 25%
  • Bundled improvements, no per-ticket quoting
  • 30-day notice to pause, change, or close

Pod · Embedded team

A full pod (3–7 people) embedded in your repo, your standup, your release rituals. Tech lead, engineers, QA, and a delivery lead, all named, all senior.

  • 3–7 named engineers + tech lead + QA
  • Joins your standups, your Slack, your sprint rituals
  • Monthly retainer; 30-day scale-up or scale-down
In Every Model

Six things that do not change with the contract shape.

Project, retainer, or pod — these six rituals stay constant. The contract changes; the delivery discipline does not.

Senior-only delivery

The expert pitching is the expert delivering. No farm-out to a junior pool. No surprise hand-off to a third tier two months in.

Two-week sprint rhythm

Planning Monday, demo Thursday, retro Friday. Same cadence whether you booked a 4-week migration or a 12-month platform build.

Weekly demo, recorded

Every Thursday a working build is demoed live. Recording up by Friday morning, indexed by feature card.

Telemetry on day one

Traces, metrics, structured logs, dashboards — wired before the first feature ships. Owned, reviewed monthly.

Security from kickoff

Secrets in a vault, least-privilege IAM, threat model before launch. Not a checklist at the end — designed in from day one.

Portable on day one

Repo access, runbooks, docs, telemetry credentials — yours from week one. No code lock-in, no hostage knowledge.

When Each Fits

Picking the shape of the contract.

If you cannot decide, start with the project model and graduate to a retainer or pod once the work is steady-state. We will tell you honestly when you are reaching for the wrong shape.

Model · When to pick it · What it includes
1
Project — Greenfield build
Defined deliverable. Fixed scope, fixed fee. Milestone billing.
2
Project — Migration
Platform-to-platform, time-boxed. Run-rate post-migration moves to retainer.
3
Retainer — Operate & grow
Monthly capacity for features, fixes, and proactive improvements.
4
Retainer — On-call + SRE
Production support, incident response, SLO ownership.
5
Pod — Product team extension
3–7 named engineers embedded in your sprint, your repo, your standup.
6
Pod — Platform build-out
Long-running platform work; tech lead + engineers + QA + delivery lead.
Three models side by side

What changes. What stays the same.

The decision matters less than people think — the rituals carry through. But here is the honest comparison.

Project Retainer Pod
BillingMilestone, fixed-feeMonthly, hours-basedMonthly, headcount-based
Engagement length4–14 weeks typical3–24 months6–24 months
Scope flexibilityFixed; change orders in writingFlexible within hoursFully flexible, your roadmap
Notice to changePer milestone clause30 days30 days
Team you getSenior lead + engineersReserved senior hoursNamed pod, embedded
Sprint ritualsYes — same cadenceYes — same cadenceYes — joined to yours
Best forGreenfield, migrations, auditsOngoing operate & growContinuous product work
Standards we hold ourselves to

Same audits, every model.

CMMI L5Process maturity
ISO 9001Quality management
ISO 27001Information security
SOC 2 IIAnnual audit
Pick a path

Tell us what you are trying to ship. We will recommend the shape.

Project, retainer, or pod — we will write a one-page recommendation and credit the discovery against the first invoice.