CompanyOS Operating Partner: CREW

Overview

Your CompanyOS is built. The only question now is whether it stays a living system that keeps getting more valuable, or slowly drifts back toward the old chaos the moment we step away.
This stage is how we keep it growing. It's closer to having an experienced operations team: a visionary, an integrator, and a support team in one, plus an army of AI agents working alongside them. You get an entire ops department for a fraction of what one senior hire costs.
Our job from here is to keep the system aligned to where the business is actually going, keep expanding what it does, and keep your team and your agents benefiting from it every day.

What We've Built So Far

Over the last 90 days we built CrewOS: one operating system in Notion where the work, the knowledge, and the record of what was promised all live in the same place. Your team is moving off Asana and are now going to Notion first.
Here is what is live, and what each piece changes.
What's live
What it changes
Event operating system. Events database, summit and meetup templates, vendor records linked to each event, and a task engine with a full event planning timeline.
Crew runs 25 to 30 meetups and two flagship summits a year. Event status is now visible in the system instead of being read out loud at the start of a leadership meeting.
Sponsorship OS. 21 sponsorship package pages standardized around deliverables, pricing, past sponsors, and reference contacts, connected to a live pipeline and an inventory tracker showing slots available, sold, and remaining per event.
At deal sizes from $1,000 to $40,000, what was sold and what was promised is now visible to the people delivering it before the event instead of after. Nashville was seeded with 15 inventory rows, so fill rate is visible package by package.
Sponsorship fulfillment agent. When a sponsorship moves to Closed Won, an AI agent creates the fulfillment task and its deliverable checklist automatically.
Post-sale logistics come off Jeff's plate, and nothing promised to a sponsor depends on someone remembering it.
One task engine. A single Tasks database covering internal work, event work, sponsor fulfillment, and member onboarding, with types, templates, and filtered views by owner.
The whole team works from one list instead of four tools. This is the piece that made the move off Asana possible.
Knowledge base and role clarity. SOPs organized by role, a staff directory with documented ownership, a mission and identity page, and a membership tier reference.
The knowledge that lived in individual heads and personal folders is written down and findable. That is the difference between a key person leaving and a key person leaving with the playbook.
Agreements database. Contracts stored and reviewable, with a filtered view of contracts inside each event.
Signed agreements are no longer sitting in one person's personal folder.
Member Sales Pipeline. Your membership and CRM data syncing into Notion daily.
This is the data foundation everything on the AI side runs on.
Access structure. Leadership and Staff groups configured across CrewOS.
People see what they should see, and adding a team member is a permission change instead of a project.

Goals

This next stage of the engagement will help you:
  1. Keep the operating system current as the business, the team, and the priorities change
  2. Keep expanding what it does with new workflows, dashboards, automations, and agents
  3. Grow your digital workforce by adding AI agents against your biggest operational bottlenecks
  4. Remove individual team member dependency so decisions and execution keep running through the system, not through you
  5. Keep adoption high so everything we build gets used instead of sitting on the shelf
The outcome: a living system that does more every month, that your team keeps using daily, that your AI agents run on, and that your future hires onboard into from day one.

The Ongoing Operating Partnership (Month-to-Month)

Your operating system is built. Left alone, most systems drift back toward the old chaos the moment the builder steps away. This stage is how we keep yours alive and getting more valuable. We stay in the seat as your operating partner and work at two levels at once. On strategy, we keep vision, focus, and the system aligned to where the business is actually going. On execution, we keep expanding and refining it. And we provide always-on support and enablement so your team actually adopts everything.
This is the layer that turns "we have a system" into "the system does more every month."

Pillar 1: Strategy: Your Fractional Head of Operations

We stay in the seat between your vision and your day-to-day, so the system keeps pace with where the company is heading right now.
  • Translate your vision into quarterly and monthly focus, pressure-test priorities, and keep the OS aligned to the business.
  • Your leadership gets a direct line for the decisions that matter.

Pillar 2: Execution: A Continuous Build Engine

A continuous build engine run against your priorities.
  • One active build in development at all times: a new workflow, dashboard, AI agent, automation, or integration, worked to completion before we pull the next.
  • Every request is sized when it goes in. Small items ship in days, larger ones in a couple of weeks. You always know the timeline before we start.
  • No cap on size. You decide whether a slot goes to three quick wins or one major build. Bigger builds simply hold the focus longer.

Pillar 3: Support & Enablement

  • Direct support channel for your team's day-to-day "how do I…" questions, tweaks, and fixes.
  • Training & documentation on everything we build. Every new workflow or agent ships with a walkthrough…either a Loom and/or reference docs. Adoption is part of the work, never an afterthought.

Continuous Build Engine: What Comes Next

Everything below surfaced in your team's own sessions over the last 90 days. We work together to set the order to give you the most impact.
  1. The member intelligence layer. Andy named this one himself: search the community and get real answers. Which member recently took a company public, who has done an acquisition in excess of $100 million, who has expanded to Europe, who has expertise in a specific area. Built on structured member data and surfaced to members inside your own branded experience. What it unlocks: it makes Crew membership measurably more valuable than the app alone. That is a retention and pricing argument, not a convenience feature.
  2. An AI sales agent for Jeff. A large backlog of prospects never said no, they went quiet. An agent works that list on a systematic cadence, with full context on each conversation. What it unlocks: revenue out of pipeline you have already paid to create.
  3. Member health and renewal protection. A weekly digest flagging members at renewal risk with engagement history, last event attended, and a suggested outreach angle, plus soft re-engagement of members who have gone quiet. Renewal outreach moves from reactive at 45 days to proactive at 90. What it unlocks: protection of recurring revenue, the most valuable number in the business.
  4. An executive dashboard for Leadership. Membership, sponsorship, event, and revenue status in one current view. What it unlocks: you get the picture without asking anyone for an update or sitting through a meeting to hear it.
  5. Event capacity and standardization. A repeatable launch process with sponsorship packages ready from day one, AI support for event planning, a structured Nashville debrief, and the full cutover so 100% of event and sponsorship work lives in CrewOS. Especially relevant with the outsourced meeting planner coming off contract. What it unlocks: more events without more people.
  6. Onboarding automation. Closed Won triggers the onboarding tasks, the LinkedIn announcement draft, and the cohort placement recommendation automatically, retiring the Asana and Zapier chain. What it unlocks: what currently takes two to three days of back and forth across three people runs in minutes.
  7. Integration and risk cleanup. Connect Copper, Circle, so member data flows instead of being re-entered, and close the single points of failure we flagged in discovery. What it unlocks: the foundation items one through three depend on, and the removal of risks that would stall operations if one person were unavailable.
All of it lives on a running wishlist inside your workspace, and we rank it together each month.

The Operating Rhythm

Cadence
What happens
Monthly
Strategy session (45–60 min): priorities and roadmap
Biweekly
Execution / ops sync (45 min): progress, feedback, unblock
Ongoing
Direct support channel, answered within one business day
Continuous
One active build always moving
  • A living wishlist you control. We both keep a running wishlist inside your workspace: ideas, requests, and enhancements added anytime. Nothing gets lost.
  • Priorities set together, monthly. Each strategy session ranks the wishlist against your goals. You decide what matters most, and we guarantee it's always moving. You can re-rank anytime.
  • Proof of value every month. A short monthly recap of what we shipped, what's in progress, and what's queued next. Your investment is always visible.

What's Included

Included
What it means
Strategic consulting
Monthly strategy session to set focus, plus strategic input on decisions as they come up between sessions. Your fractional head of operations.
Continuous building
One active build always in motion: new workflows, dashboards, and continuous refinement of what's already live.
Automation & AI
New agents and automations are first-class citizens in your build queue. Prioritize an agent exactly like any other build.
Training & enablement
Onboarding, live rollout sessions, saved Loom walkthroughs, and reference docs for everything we build.
Ongoing support
A direct channel where your team brings questions and gets unblocked, answered within one business day.


Investment

$4,250 per month, payable by credit card.
  • Month-to-month. Stay as long as it keeps creating value. Give 30 days' notice if you ever decide to pause.
  • No separate build fees. Strategy, the continuous build engine, new agents and automations, training, and support are all covered by the monthly investment.
What you're really getting for that. A full-time head of operations who could run this is $120,000–$180,000+ a year, and even then they couldn't stand up the AI layer or train your team alone. You get the strategist, the build engine, the support desk, and an army of AI agents. That's an entire ops team for roughly the cost of a single junior hire.

Getting Started

Once we're aligned, this is what happens next:
  1. We confirm your start date and your monthly investment.
  2. We stand up your wishlist inside your workspace and book your first strategy session.
  3. We rank your priorities together, and the build engine picks up the first one seamlessly.