Fractional ops for a category design studio.
Gold Front is the category design studio helping groundbreaking startups define entirely new markets. It operates as a small team of full-timers, complemented by a regular freelancer bench. The founder wanted to step back from Executive-Producing the work while remaining the firm’s leader. As a fractional ops consultant, my work centered on identifying major bottlenecks in the studio’s operations.
The situation
I was hired to harden Gold Front’s delivery side ahead of a leadership handoff. The founder was bringing on a new Executive Producer and needed the project management spine to work without himself in the middle of every decision. The studio was running on ClickUp, but Slack was carrying most of the briefing and handoff load. The founder still sat in the critical path of nearly every active engagement.
My scope was explicit from day one: focus on Delivery only, automate as many workflows as possible, add AI where it makes sense. The win condition was a system where the founder could step back from EP-level work and hand a well-oiled operating rhythm for the Delivery function to the incoming partner.
What I built
As I often do at the start of a new engagement, I ran a non-anonymous, structured Q&A with all team members on the studio’s flagship engagement at the time. I transposed, categorized, and synthesized the raw responses into a strengths vs. improvements analysis that the founder and incoming partner could act on.1
Key initiatives that followed:
- Evaluation of the Project Briefing & Kickoff Process. I made five concrete recommendations for how the studio’s project initiation SOP should be improved, as a direct result of how I saw the flagship engagement being delivered: a templated kickoff kit, automated tool onboarding (Granola, ClickUp, Drive, Slack), a standard RACI per project type, a self-serve scheduling layer, and a single Project Briefing Hub to replace Slack as the source of truth.
- Variance instrumentation in ClickUp. I added planned vs. actual end-date fields and visualizations to project templates to give leadership visibility into schedule slippage at the phase and project level instead of inferring it from Slack.
- Roles and responsibilities framework. Co-defined the operating model for agency R&D and resource management across six layers: System Rules, User Rules, Automations, System Alerts, Dashboards, and Loom-based checklists and documented how-tos that any new team member could follow. This gave studio leadership a clear surface to own without renegotiating it project by project.2
The outcome
The founder got an outside read on his delivery org that named the founder-bottleneck problem in his team’s own words, with the receipts attached. The new EP hire walked into the role with a defined operating surface instead of a vague mandate. ClickUp went from a per-project improvisation to a workspace with templated variance tracking and cleaner ownership, and the studio’s most visible live project got a documented kickoff playbook to reuse on the next one.
Over the course of my engagement the conversations with the founder shifted from “we need a better PM system” to “let’s automate as much as we can and deploy AI smartly”, which demonstrated how quickly the agency ops conversation matured.
- Top themes surfaced: Founder as bottleneck, process inconsistency and bypassed SOPs, handoff friction between phases.
- System Rules: programmatic rules enforced by the tooling itself. User Rules: the agreements people make about who does what based on role. System Alerts: triggers when people operate outside the user rules.