Skip to content

People

Team roster and decision authority. Names and ownership. Update on hire, depart, or role-change.

Leadership

Paul Troiano — Managing Partner / President / CEO

Holding-company leader. Owns the overall enterprise: capital structure, strategic direction, investor relations, and the org as a whole.

  • Title used externally: "Managing Partner, Metrognome Holdings, LLC"
  • Title used internally: CEO + President
  • Primary contact for: investors, lenders (e.g. OnPoint), major partnerships
  • Email: paul@metrognome.com

Aaron Hogan — CTO

Owns the entire Platform → Enable function — all technology systems that power the company's three pillars. Per CTO JD V0.3:

  • Owns all customer-facing applications across the three business lines (monthly, hourly, SESHN).
  • Owns all systems for product delivery and ops (reservations, billing, physical access control, communications).
  • Owns marketing technology infrastructure and digital channels.
  • Owns business intelligence + dashboards for leadership, finance, prop ops, member experience, marketing.
  • Leads AI integration across internal workflows, member experience, and asset acquisition/management.
  • Makes build-vs-buy decisions for technology investments.

Reports to Paul. Email: aaron@metrognome.com.

Field operations + shared services

Juan — Community Management Director

Pillar 02 (Studios). Owns Community Management at the director level — the function that runs day-to-day field operations and member experience across locations. Surfaces field signal in roadmap conversations (in-person sales / payment friction, legacy member transitions, on-site sign-up workflow).

Nic — Director of Operations

Operations leadership across the org. Surfaces operational signal in roadmap conversations (member content collection, member activation, comms beyond transactional).

Additional team

The active team is small. Roster beyond the four named above to be filled in by Paul + Aaron during their next pass. Outside advisors, fractional roles, and contractors should be listed here when they apply to ongoing work.

Decision authority — how to route a question

Role-based, not person-based. Update if titles change.

Question type Default owner
Capital structure, fundraising, investor relations, big strategic moves CEO (Paul)
New-location selection, lease vs buy, build-out standards (Pillar 01 Development) CEO (Paul); CTO consults on tech / data implications
Technology, data, AI, product, marketing-technology infrastructure CTO (Aaron)
Marketing brand voice, copy, paid channels Marketing function (see docs/marketing/)
Day-to-day field ops at a specific location (Pillar 02 Studios) Community Management Director / City Manager / Studios team
Cross-location operations, vendor relationships, facility infrastructure Director of Operations
SESHN community programming SESHN function (Pillar 03)

When in doubt: anything cross-pillar or strategic → CEO. Anything technical / data / system → CTO.

CTO authority

Authority the CTO has explicitly per the role definition:

  • Make build-vs-buy decisions for technology investments.
  • Define and execute product roadmap for digital touchpoints.
  • Lead AI integration efforts across the org.
  • Establish security practices for customer + payment data.

Authority the CTO does not have:

  • Capital decisions, distributions, fundraising.
  • Lease / acquisition signing.
  • Marketing strategy / brand decisions (CTO consults; Marketing owns).
  • Hiring outside the technical team without CEO sign-off.

Working norms

  • Weekly team huddle. Cross-team operational decisions and field signals. Notes captured in Drive (search "MG: Wkly Team Huddle").
  • Recurring CEO / CTO syncs. Strategic and product-direction conversations.
  • Architectural decisions are recorded as ADRs in docs/decisions/.
  • Asana is the canonical task tracker for product work. Backlog lives in Asana ("MG.com" project), not GitHub Issues.
  • Slack is primary intra-team chat.

Outstanding items

  • [ ] Roster beyond Paul, Aaron, Juan, Nic — names + titles + which pillar/function.
  • [ ] External advisors / fractional roles / contractors worth listing.
  • [ ] Any deliberate openings being hired (vacancies in the org).