Epoch

Epoch is a San Francisco-based employee experience platform that helps people teams plan, promote, and measure internal events and programs in one place. Founded by University of Waterloo alumni, the company raised a US$3.6M seed round led by Rally Ventures and serves 30+ enterprise companies running thousands of internal events every month.

I joined as a Product Analyst with a mandate to deliver monthly feedback reports and quarterly business reviews. The role quickly expanded into automation, product launches, and sales outreach as the team grew.

The core of my work at Epoch was the client reporting pipeline. Every month, enterprise clients received a Feedback Report summarizing how their employees engaged with internal events. Every quarter, they received a comprehensive Business Review. These weren't templated PDFs. Each report was custom-built from multiple data sources and tailored to the client's specific program.

I created 40+ Feedback Reports over the term, each summarizing participation, popular events, timezone breakdowns, and post-event survey feedback so stakeholders could see not just attendance, but what employees thought and where programs could improve.

I built 20+ Quarterly Business Reviews, each tailored to the client's metrics, goals, and time ranges. I pulled data from our internal metrics sheet, SQL queries, and web app tooling, then packaged verified metrics into presentation slides with linked graphs that updated as the underlying data changed.

I maintained the CX Metrics Sheet, the internal source of truth for client health. Every week, I updated KPIs across all active accounts: activated accounts, unique participants, total employees, percentage of employees activated, total participants, and total events hosted.

After creating dozens of FBRs manually, the inefficiency became impossible to ignore. I documented the entire workflow from end to end: pulling participant data from SQL, event engagement from domain insights, and activation metrics from our CX sheet, then formatting everything in Figma before delivery. A single report took 2–3 hours, and across 40+ clients per month, reporting alone was consuming most of the CX team's time. The bigger issue was the error surface, where every copy-paste was another chance for a wrong number, a mismatched client name, or a missed timezone.

I partnered with engineering to centralize the entire FBR data pipeline into Retool, mapping where each metric lived in PostgreSQL and building queries that replaced the manual work across five tools. The app surfaced participant data, feedback responses, timezone breakdowns, and engagement metrics by client and date range, with engineering handling the heavier calculations in Python where raw SQL would have been too expensive.

The result was a single Retool dashboard where you could select a client, choose a date range, and get every metric needed for an FBR in one view. What previously took hours of context-switching across Figma, SQL, spreadsheets, and domain pages now took minutes. I also documented the entire dashboard and query logic in Confluence so future co-ops could extend or debug the system without starting from scratch.

Epoch launched a new Communities feature that let enterprise clients organize employees into ERG-based groups within the platform. I was responsible for rolling this out to the first wave of enterprise clients.

Each Communities launch meant working directly with client stakeholders to understand how their ERGs were structured, which communities they wanted to stand up, and how the feature would fit into their existing workflow. From there I configured communities on their domains, synced the right employee groups, and ran admin training for their people ops teams. It went beyond configuration: some clients had formal ERG programs with designated leads, while others had informal groups we were structuring for the first time, and the onboarding had to work for both.

I launched Communities for 5+ enterprise clients. Each rollout followed the same general pattern but required client-specific customization: different community structures, different employee sync requirements, and different levels of admin familiarity with the platform.

The role was scoped around data reporting, but I wanted to understand how the broader business worked. Halfway through the term I started supporting outbound sales: building targeted outreach cadences, researching accounts, and doing in-person outreach to people ops teams at prospective clients. It wasn't in the job description, but it gave me a view into how a B2B SaaS company finds and closes enterprise customers.

The work spanned reporting, automation, product, and sales, touching every part of the business over four months.