Operations

PENTAGON

PENTAGON started almost by accident. I co-founded it with my partner, and as demand grew we had to turn that accidental start into something that could actually run. We grew the operation to seven people and 38 seats, then eventually transferred it to a new owner.

Context

As the operation grew, we needed to understand what products actually cost, what was selling, how much capacity we had, where staffing pressure was building and what the operation could realistically handle.

The Problem

Turn an accidental business into an operation that could grow without losing control of capacity, staffing, information or day-to-day decisions.

My Role

Owned

  • Operational design
  • Capacity and staffing systems
  • Sales and cost visibility
  • Menu and product costing tools
  • HR and capacity tools
  • Workflow design

How It Worked

  1. 01Demand
  2. 02Sales + cost information
  3. 03Capacity
  4. 04Staffing
  5. 05Workflows
  6. 06Operating tools
  7. 07Decisions
  8. 08Repeatability
  9. 09Transfer

Key Decisions

  1. Capacity before growth

    Demand only mattered if physical space, people and throughput could support it.

  2. Add people without adding chaos

    The team grew from zero to seven, which required clearer responsibilities, handoffs and working methods.

  3. Make the operation measurable

    Market tools mostly gave us generic information, so I built tools around the actual decisions we needed to make: product costs, sales, staffing, HR and capacity.

  4. Make the operation less founder-dependent

    Processes and information had to move out of our heads and into the operation.

  5. Build something that could be handed over

    The final proof was transferring the operation to a new owner.

Inside the Work

  • Menu and product costing
  • Sales control
  • HR and capacity tools
  • Inventory and operating data
  • 0→7 team
  • 38 seats
  • €400K+ in sales

Result

  • 0→7 team.
  • 38 seats.
  • €400K+ in sales.
  • Operation transferred to a new owner.