A. Front-end dev hire from Three Ships
What this isA former colleague from Three Ships. Experienced front-end dev. Available to interview.
Why nowWeb dev workload (Webflow, content engine, microsites) is bottlenecked on me and one or two part-time hands.
Ask of Sarah
Decision Green-light an interview, or pass.
B. Stand up a Marketing Operations team
What this isA dedicated MarOps function covering AI, CRM, data and reporting, and audits.
Why nowThese functions are scattered across people who already have day jobs. Output is uneven and dependent on whoever has bandwidth that week.
Ask of Sarah
Input Do you see the case for a dedicated team, and what would the first hire look like.
C. Website strategy
What this isThe overall website call we have been deferring: Webflow vs. alternative, central vs. per-practice, agency vs. in-house.
Why nowEvery workstream that touches the web (SEO, content engine, Gen4 brand rollouts, Innovative) is stuck waiting for this.
Ask of Sarah
Decision Where is your head, and can we land on a direction this week.
D. Content engine roadmap
What this isA clear, written roadmap for the content engine that we both align on.
Why nowThe work is moving reactively right now. Too often it shifts to "look at this thing someone else has built" instead of executing against a plan. Building SaaS sustainably requires a roadmap we commit to, with scope and sequencing locked, so Mike is not context-switching every time something new surfaces.
Ask of Sarah
Decision Align on the roadmap and a change-control rule (what gets added vs. parked) so we can build sustainably.
E. Kim Middleton engagement and cosmetic strategy
What this isTwo related items. First, lock the scope of Kim Middleton's engagement. Second, frame our broader cosmetic strategy.
Why nowWorth setting the cosmetic frame before more provider conversations open up (e.g., Dr. Field), so each one gets evaluated against a strategy rather than case by case.
Ask of Sarah
Decision Lock Kim this week. Then schedule a separate working session on cosmetic strategy.
F. Leadership operating rhythm
What this isA proposed cadence to get us through this transition period and establish a sustainable rhythm afterward.
Why nowWe are losing time to ad hoc check-ins and reactive pulls. A clear rhythm gives the team room to execute and gives leadership room to lead.
Proposal
Daily leadership quick syncs (Dakota, Mike, Amy) through the transition period. Short, status-driven, surface blockers.
Tuesday and Thursday deep dives. Backlog-driven. Used to close out projects and move specific workstreams forward.
Team Monday and Friday meetings. Standing agenda: key priorities, what is blocked or needed from the team, ad hoc discussion items at the end.
Ask of Sarah
Decision Approve the rhythm, adjust it, or propose an alternative. Goal is to start next week.