Questions we get
before anyone
says yes.

Retainer engagements typically start at $2,000/month and scale based on hours committed and scope. Most ongoing fractional COO engagements run $2,000–$5,000/month for 15–40 hours per week of embedded operational leadership.

Fixed-scope Systems Architecture projects are priced per engagement — typically $3,000–$8,000 depending on team size and complexity.

We do not quote on the first call. After the discovery conversation, we send a specific engagement proposal within 48 hours.

Most engagements are structured as monthly retainers with a defined hour commitment. This gives you predictable cost and gives us the embedded presence to actually get work done — not just answer emails when you need something.

Some short-term and project-based engagements are billed hourly with a defined scope. We decide together which structure fits the work.

We ask for a 90-day minimum on retainer engagements. Real operational change takes time — the first 30 days is diagnosis and foundation, the next 60 is where the systems actually get built and embedded. You will not see meaningful results in 30 days and we will not pretend otherwise.

For fixed-scope projects, timelines vary by deliverable. A full SOP suite might take 4–6 weeks. A complete systems architecture build can take 8–12 weeks.

If there is a fit, fast. Most engagements kick off within 1–2 weeks of the proposal being signed. We do not have a long onboarding process on our end — we embed and start learning your business from Day 1.

Current availability is listed on the Contact page.

It depends on the engagement structure. Fractional COO retainers typically run 15–40 hours per week. Operations Lead roles are usually 15–20 hours. Systems Architecture projects are more intensive at the start and taper as delivery completes.

We define hours clearly in the proposal so there is no ambiguity about what you are getting.

We plug into your existing communication tools — Slack, email, project management platforms — whatever your team already uses. We do not ask you to adopt new tools just to work with us.

Most engagements include a weekly check-in with leadership, daily touchpoints with the operations layer, and async availability throughout the week. We build the communication cadence into the engagement structure from the start.

Month one is almost entirely diagnostic and foundation-setting. We map every workflow, every tool, every handoff point. We talk to your team. We find out where things actually break, not where the founder thinks they break.

By Day 30, you have a full operational audit, a priority stack for the build phase, and the first SOPs in place. The output is visible and documented — not just a set of conversations.

Our deepest experience is in field service businesses, content media and digital operations, and financial services. We have also worked across e-commerce and professional services.

The operational problems we solve — founder bottleneck, broken accountability, disorganized process — appear in almost every industry. Vertical matters less than the fact that you have real revenue, a real team, and a real operations problem.

A consultant diagnoses and recommends. They hand you a report and a roadmap, then leave. You are responsible for making it work.

We embed and build. We own the operational layer, execute alongside your team, and do not leave until the system holds on its own. The measure of success is not a deliverable — it is a functioning operation that your team runs without us in every conversation.

If you want advice, hire a consultant. If you want it built, talk to us.

Typically no. We work best with businesses that have real revenue, a real team, and a real operations problem — usually $500K+ in annual revenue with 3 or more team members.

Pre-revenue or early-stage startups usually need product-market fit, not operational infrastructure. Building systems before you have something worth systematizing is a distraction, not a solution.

That is the whole point of the work. Every system we build is documented. Every process is owned by a person on your team, not by us. Every handoff is trained before we step back.

A successful engagement ends with your team running the operation without us in every conversation. If that is not true, we have not finished the work.

Many clients continue to a second engagement or bring us in for a specific build. Some become long-term partners. None of that is the goal — the goal is that you do not need us to operate.