Done-With-You, spelled out
Every session, hour, and deliverable in the $2,950 tier · Last updated 2026-07-24 · Ousios LLC
Done-With-You is a 90-day guided rollout for one team of up to 10 people. Composa's assessment maps your team and generates the plan; a strategist then runs that plan with you against your real tools, real tasks, and real people. This page is the full scope — so you know exactly what $2,950 buys before you ever get on a call.
What's included
| Before you pay | Booking call (30 min). We check fit honestly — including reading when you shouldn't buy Composa together — then walk the written agreement and the guarantee terms. If this tier isn't right for you, we'll say so and point you at the $149 self-guided option. |
| Week 0 | Kickoff (60 min). Your team takes the 90-second assessment (participation is voluntary per person — see below). We review your team mesh and strategy mode, and your 2–3 success metrics are agreed and countersigned before day 1. |
| Week 1 | Leadership alignment session (60–90 min). What the assessment can and can't see, the never-for-hiring commitment (signed, not just read), your team's composition at the team level, and what leadership specifically owns during the rollout. |
| Days 1–30 | Workflow build-out session (90 min) + async build. Three workflows from your team's recommendations, rebuilt for your actual tools and data — each interviewed, rewritten, and sandbox-tested with sample data before anything touches live work. Delivered as copy-paste kits in your console. |
| Day 30 | Check-in call (30 min). Two numbers: workflows still running, hours recovered. What's not sticking gets swapped, not forced. |
| Day 60 | Check-in call (30 min). Course-correct, expand what's working, log the numbers. |
| Day 90 | Outcome review (60 min). Team-level re-assessment, measured numbers against your kickoff metrics, guarantee adjudication, and the next quarter's plan. |
| Throughout | Office hours (two scheduled 30-minute slots per month) and async support with responses within 2 business days. Plus each team member's personalized archetype guide. |
That's roughly 7 hours of live strategist time plus the build work behind it. Additional custom workflows beyond the three included are priced add-ons — $500 each, agreed in writing — so scope never drifts silently. The deeper multi-week team systems shown in the previews below (a workflow library, a pulse pipeline, a postmortem flywheel…) are a bigger build than a workflow: they're available as priced add-ons, or — electable at kickoff — one of them can be your entire build-out in place of the three workflows.
What it looks like for a team like yours
Composa classifies teams into six standard compositions. The previews below aren't marketing copy — each one is computed by the same engine that will run your rollout: the strategy mode, readiness, and even who gets named adoption champion come straight from the app, applied to each composition's defining archetypes. Your team's actual mix (assessed at kickoff) will sharpen all of it.
Explorer Team
Built around The Pioneer · The Maverick · The Visionary
“You move fast and see far — but you leave a lot on the table when no one cleans up after you.”
What the engine computes for this composition: Generative co-pilot, light guardrails (Clear fit) · readiness Build-up (52/100) · adoption champion: The Pioneer · systematization owner: The Maverick.
The three builds we'd start from (customized to your actual stack in the build-out session):
- Unified Tool Scouting Protocol — ~2.5 hrs/wk per person it serves · Notion AI + Claude
- Same-Day Prototype → Handoff Template — ~3 hrs/wk per person it serves · Claude + Linear
- Vision Artifact Sprint — ~3.5 hrs/wk per person it serves · Claude + Gamma
Days 31–90 can grow toward: Shared AI Toolchain Repo (4–6 wks) and Experiment-to-Decision Pipeline (6–8 wks) — because the gap for teams like this is consistency and knowledge capture. These are the deeper team systems: priced add-ons, or electable at kickoff as your entire build-out (see "What's included").
Success metrics teams like this typically pick (yours are yours to define): workflow survival (do the prototypes still run at day 14?) and time on a target task. The app's illustrative estimate for this composition is ~9.5 hrs/week recovered team-wide — a planning reference, not a promise (how we calculate).
Builder Team
Built around The Architect · The Craftsman · The Guardian
“You build things that last — but you under-communicate and over-invest in internal quality at the expense of speed.”
What the engine computes for this composition: Process automation, human judgment on top (Moderate fit) · readiness Moderate (69/100) · adoption champion: The Architect · systematization owner: The Architect.
The three builds we'd start from (customized to your actual stack in the build-out session):
- Architecture Decision Records (Architect) — ~2.5 hrs/wk per person it serves · Claude + Notion AI
- AI Pre-Screen for Code Review (Craftsman) — ~2 hrs/wk per person it serves · GitHub Copilot + Claude
- Risk Audit Before Every Launch (Guardian) — ~2.5 hrs/wk per person it serves · Claude + Notion AI
Days 31–90 can grow toward: Team Quality Benchmark System (3–4 wks) and Automated Compliance Monitoring (Guardian) (6–8 wks) — because the gap for teams like this is communication and stakeholder alignment. These are the deeper team systems: priced add-ons, or electable at kickoff as your entire build-out (see "What's included").
Success metrics teams like this typically pick (yours are yours to define): turnaround time on reviews and output quality, judged blind. The app's illustrative estimate for this composition is ~7.5 hrs/week recovered team-wide — a planning reference, not a promise (how we calculate).
Connector Team
Built around The Weaver · The Catalyst · The Sage
“You align people and synthesize knowledge better than anyone — but you're drowning in communication overhead that should be automated.”
What the engine computes for this composition: Communication & alignment layer (Borderline fit) · readiness Build-up (54/100) · adoption champion: The Catalyst · systematization owner: The Weaver.
The three builds we'd start from (customized to your actual stack in the build-out session):
- Async Meeting Recap (Weaver) — ~2 hrs/wk per person it serves · Fireflies.ai + Claude
- Stakeholder Update Templates (Catalyst) — ~2.5 hrs/wk per person it serves · Claude + Notion AI
- Research Synthesis (Sage) — ~4 hrs/wk per person it serves · Claude
Days 31–90 can grow toward: Cross-Team Alignment System (Weaver) (3–4 wks) and Team Pulse Analytics Pipeline (Catalyst + Sage) (4–6 wks) — because the gap for teams like this is analytical rigor and concrete deliverables. These are the deeper team systems: priced add-ons, or electable at kickoff as your entire build-out (see "What's included").
Success metrics teams like this typically pick (yours are yours to define): turnaround time (meeting-end to recap-sent) and time on a target task. The app's illustrative estimate for this composition is ~8.5 hrs/week recovered team-wide — a planning reference, not a promise (how we calculate).
Driver Team
Built around The Closer · The Pioneer · The Catalyst
“You ship and win — but your speed creates a wake of undocumented decisions and underaligned stakeholders.”
What the engine computes for this composition: Balanced augmentation, start narrow (Borderline fit) · readiness Build-up (53/100) · adoption champion: The Pioneer · systematization owner: The Closer.
The three builds we'd start from (customized to your actual stack in the build-out session):
- Auto Monday Dashboard (Closer) — ~1.25 hrs/wk per person it serves · Claude + Linear
- Same-Day Prototype (Pioneer) — ~4 hrs/wk per person it serves · Claude + v0.dev
- Change Narrative Drafts (Catalyst) — ~3 hrs/wk per person it serves · Claude + Notion AI
Days 31–90 can grow toward: Experiment-to-Postmortem Flywheel (Pioneer + Closer) (4–6 wks) and Automated Deal Qualification (Closer) (3–4 wks) — because the gap for teams like this is documentation, knowledge retention, and sustainable pace. These are the deeper team systems: priced add-ons, or electable at kickoff as your entire build-out (see "What's included").
Success metrics teams like this typically pick (yours are yours to define): workflow survival and turnaround time. The app's illustrative estimate for this composition is ~10.5 hrs/week recovered team-wide — a planning reference, not a promise (how we calculate).
Analyst Team
Built around The Sage · The Architect · The Guardian
“You produce the most rigorous work in the organization — but it takes too long and lands too late to change decisions.”
What the engine computes for this composition: Balanced augmentation, start narrow (Borderline fit) · readiness Moderate (66/100) · adoption champion: The Architect · systematization owner: The Architect.
The three builds we'd start from (customized to your actual stack in the build-out session):
- Research Synthesis Sprint (Sage) — ~4 hrs/wk per person it serves · Claude
- Claims & Assumptions Audit (Sage) — ~2 hrs/wk per person it serves · Claude + Notion AI
- Risk Register Before Every Decision (Guardian) — ~2.5 hrs/wk per person it serves · Claude + Notion AI
Days 31–90 can grow toward: Decision Briefing System (Sage + Architect) (4–6 wks) and Automated System Dependency Map (Architect) (6–8 wks) — because the gap for teams like this is speed and communication. These are the deeper team systems: priced add-ons, or electable at kickoff as your entire build-out (see "What's included").
Success metrics teams like this typically pick (yours are yours to define): time on a target task (question to credible answer) and output quality, judged blind. The app's illustrative estimate for this composition is ~7 hrs/week recovered team-wide — a planning reference, not a promise (how we calculate).
Balanced Team
Built around a deliberate mix across all five style families
“You have every capability in the room — and the hardest job of any team type: coordinating without collision.”
What the engine computes for this composition: Balanced augmentation, start narrow (Moderate fit) · readiness Moderate (59/100) · adoption champion: The Pioneer · systematization owner: The Closer.
The three builds we'd start from (customized to your actual stack in the build-out session):
- Cross-Style Meeting Recap (Weaver) — ~2 hrs/wk per person it serves · Fireflies.ai + Claude
- Decision Brief Standard (Sage + Architect) — ~2.5 hrs/wk per person it serves · Claude + Notion AI
- Weekly Dashboard for All (Closer) — ~1.25 hrs/wk per person it serves · Claude + Linear
Days 31–90 can grow toward: Shared Workflow Library (6–8 wks) and Cognitive-Style Communication Guide (Weaver + Sage) (4–6 wks) — because the gap for teams like this is coordination overhead and cognitive-style translation. These are the deeper team systems: priced add-ons, or electable at kickoff as your entire build-out (see "What's included").
Success metrics teams like this typically pick (yours are yours to define): opt-in rate (the trust metric) and workflow survival. The app's illustrative estimate for this composition is ~8 hrs/week recovered team-wide — a planning reference, not a promise (how we calculate).
What we ask of your team
"Done with you" is literal — the guarantee is conditioned on the parts only you can do:
- Assessments done by end of week 1, with at least ~70% of the team participating. Participation is voluntary per person; your team gets notice and a genuine opt-out before anything starts.
- A named champion by day 14 (the app suggests one from your team's own archetypes).
- Show up: the sessions above are where the rollout actually happens.
- Log the numbers at day 30 and 60 — the guarantee is scored on data, and both sides agree the numbers as they're logged, not at the end.
Who delivers it
One strategist — the same person who built Composa. That's a feature and a constraint, and we treat it honestly the same way our security page does: Done-With-You runs a maximum of three concurrent engagements, so the person on your calls is the person doing the work. If illness or emergency interrupts, clocks pause and sessions reschedule — your 90 days don't silently burn.
How the 90-day outcome guarantee works
At kickoff, you define 2–3 success metrics in writing — from the same menu as the 2-week pilot (time on a target task, turnaround, workflow survival, output quality judged blind) or your own equivalents, each with a named data source. Both sides sign them before day 1, including how pass, partial, and miss will be decided — so day 90 is arithmetic, not argument.
If the metrics are missed at day 90 and your team held up its side (the list above), the engagement extends at no charge for up to 60 days. If it's still unmet after that, we refund 50% of the tier price — the guarantee ends in money, not just more effort. Full terms are published in the Done-With-You section of the terms and restated in your countersigned agreement before purchase. The standard 14-day refund applies from purchase as usual.
How buying works
| 1 | Book the call. We qualify honestly — both directions. |
| 2 | Review and countersign the written agreement: scope, schedule, your obligations, metrics process, guarantee terms, and data handling (including how your team's sample data is protected during workflow builds — redacted or synthetic by default). |
| 3 | Pay by card — we send a Stripe payment link after the agreement is countersigned. Kickoff is scheduled within 21 days of payment. |