Draft
Client Offerings (Engagement Playbook)
Five ways we take on, build, and operate infrastructure for clients — pick by answering four questions, compare at a glance below, then read the one scenario that fits. Start every engagement with the Discovery Framework.
Find your path
flowchart TD
Q1{Do you have a cloud
team & accounts?}
Q1 -->|Not yet| I4["4 · Incubate"]
Q1 -->|Yes, with existing infra| Q2{Operate it for you,
or augment your team?}
Q1 -->|Yes, starting fresh| Q3{Run it after
we build?}
Q2 -->|Operate| T3["3 · Takeover"]
Q2 -->|Augment| E5["5 · Embed / Co-Build"]
Q3 -->|We run it| L2["2 · Launch & Manage"]
Q3 -->|You run it| L1["1 · Launch"]
click L1 href "./launch.html"
click L2 href "./launch-manage.html"
click T3 href "./takeover.html"
click I4 href "./incubate.html"
click E5 href "./embed.html"
style L1 fill:#EDEDFF,stroke:#3B54F7
style L2 fill:#EDEDFF,stroke:#6247F5
style T3 fill:#EDEDFF,stroke:#2E7DE0
style I4 fill:#F3EDFF,stroke:#8A54E8
style E5 fill:#E4E4FF,stroke:#23233A
The five paths, compared
| Launch | Launch & Manage | Takeover | Incubate | Embed | |
|---|---|---|---|---|---|
| Accounts | Yours | Yours | Yours (existing) | Propel → yours | Yours |
| We | Build | Build + run | Operate + improve | Host + run | Co-build + advise |
| Standards | Propel reference arch | Propel reference arch | Conform → improve | Propel reference arch | Yours |
| After the build | You run it | Fully managed (SLA) | Managed (SLA) | Managed → graduates | Your team owns it |
| On-call | — (handover) | Propel | Propel | Propel | — |
| Your data & state | Client-side | Client-side | Client-side | Propel-side until graduation | Client-side |
| Exit story | Handover is the deliverable | Clean by design — repos + data already yours | Return ops with docs | Planned graduation trigger | Nothing to exit |
| Typical client | Has a team, wants a clean foundation | Wants one accountable partner | Already on cloud, ops stretched | Early-stage, no cloud team yet | Strong team wanting expertise |
What holds on every path
Client data and state stay client-side (Incubate excepted, until graduation) · everything handover-ready by construction · OSS/cheap first · reusable patterns are Propel IP, your live config is yours · shared responsibility written and signed before build starts.