Delivery model

Pod, not person

Every engagement is staffed as a pod with a named backup, run against fixed quality gates, and delivered into infrastructure the customer already owns.

Pod compositions

Sized to the engagement

A pod scales from a minimum team to a larger one for bigger engagements. Exact roles and headcounts publish here once confirmed.

Minimum pod

set at agreement

Large pod

set at agreement

Ownership

The customer owns the workspace

Customer owns the workspace — A Build organization on the customer's own GitHub repo, and their own AgentOS tenant.

No personal-account credentials — No delivery credentials live on a personal account.

Quality gates

The same discipline on every engagement

Spec agreed first — Scope and acceptance criteria are agreed with the customer before delivery starts.

Revisions until met — Work goes through revisions until the agreed spec is met — no partial acceptance.

Two-person QA — Every deliverable passes review by a second pod member before it ships.

Gates never bypassed — The delivery lead configures Build's own quality gates for the engagement, and they are never bypassed.

Live status board — Every engagement has a live status board the customer can see.

Backup named at kickoff — A backup pod member is named at kickoff, so no engagement depends on one person.

Assembly

Matched, not assigned

Interactor matches pod inputs to the engagement, and the client chooses from 2–3 candidate profiles within 10 business days.

Artefact policy

Who owns what

Generalized artefacts — Connectors and templates built during delivery may be offered back to Interactor for a bounty or account credit — never required.

Customer code — The customer's own code is the customer's.

Example manifest

What a delivery manifest looks like

Roles deployedDM-2026-000

Build builds itself

Every feature Interactor Build ships to its own product goes through the same goal → task → PR engine sold to customers — no separate fast path for the team that built it.

Build operator · 1
Reviewer · 1

Product telemetry

Merged goal PRs: 2,018GitHub search, InteractorOSS/product-manager · measured 2026-09-04
Incident post-mortems: 7docs/incidents/, InteractorOSS/product-manager · measured 2026-09-04
Runbooks written: 53docs/runbooks/*.md (top-level), InteractorOSS/product-manager · measured 2026-09-04

ResultShipped 2,018 goal PRs to its own product — each reviewed and merged through the same engine it sells.

Have a delivery in mind?

Talk to us about staffing a pod for your engagement.

← Back to Partner Program overview