How embedded is "embedded"?

Inside the team's calendar, the team's tools, the team's room. Daily standups, decision logs maintained in writing, the founder's 1:1 every other week.

Three months, with an optional three-month extension. The scoped exit is planned from day one.

Do you take a title and decision ownership?

For the engagement, yes — an interim COO / head of product operations mandate over the operating system: PDLC, planning cadence, launch readiness, and org design. Product vision and the roadmap stay with the founder and CPO; people-management and final calls stay with the founder unless we scope otherwise, and the seat is handed to your permanent hire at exit.

Practice — Memorandum No. II — Embedded Partnership

A working seat inside the operator's team.

A three-month engagement as your interim COO / head of product operations: on the executive team, installing the operating system, hiring your permanent operations leader, and exiting into a structured handoff. Operator, not consultant — with the pattern recognition that comes from shipping at Tinder, Strava, Snowflake and Twitter.

This is the Embedded Operator Model in practice: not advisory, not staff-aug — a senior operator who owns outcomes and leaves the system running without them.

No. 1 — Premise

Why this exists.

The founder's problem

The Series B+ founder's missing layer. The team can ship; the founder is making strategy calls; what's missing is the tissue between them: written status, decision logs, cross-functional cadence. The work an operator-grade Director of Product Ops would run, before the role is hired.

The practice's response

An embedded fractional operator. Three months inside the founder's team: daily standups, weekly written status, bi-weekly founder 1:1, quarterly off-site, decision logs maintained in writing. Pattern recognition from Tinder, Strava, Snowflake and Twitter, applied to one founder's quarter at a time.

No. 2 — Cadence

How it works.

Daily standup attendance Inside the team's morning ritual: escalations, blockers, written follow-ups.
Weekly written status A short note from the operator: what shipped, what's drifting, what's next.
Bi-weekly founder 1:1 A standing seat next to the founder, for strategic counsel and quiet escalations.
Mid-engagement off-site A working day on what comes after the engagement: strategy, hires, operating cadence.
Decision logs What was decided, deferred, rejected, kept in writing, week over week.
Close-out review A written ledger of the engagement: what shifted, what landed, what is next.

No. 3 — Artefacts

What it produces.

Roadmap drafts Working drafts the founder can react to before they go to the team.
Decision logs Maintained in writing for memory, for board, for the next operator.
Operating cadence The week-by-week shape: standups, status, off-sites, reviews.
OKR shaping memos Drafts that turn the founder's strategy into team-readable objectives.
Cross-functional rituals Standups, retros, off-sites, built so the team runs them after I leave.

No. 4 — Prerequisite

Standing required.

For Series B+ consumer-tech founders in the Gulf with a three-month horizon and the founder's standing buy-in for an embedded operator. Embedded means inside the team's calendar, the team's tools, the team's room. Not outside, not on top.

Not for

Engineering management This seat shapes the operating layer. The engineering org is not in scope.
Standing advisory This is a hands-on operating seat, not a monthly counsel retainer — that is the Advisory Retainer.

No. 5 — Sister engagements

For shorter standing or quarter-by-quarter counsel.

Execution Diagnostic — A short written read on the operator's quarter. Two to four weeks, founder-shaped questions, written diagnostic. Advisory Retainer — A standing seat across the operator's quarter. Monthly memos, twice-monthly calls, quarter-close reviews.

No. 6 — Regard

“One of the best Program Managers I know.”

Mike Manoske, PCC · Executive Coach

Open an intro call