The Pull
MNTN was trying to make meetings and customer-facing conversations useful across teams.
Their current setup blocked them because call recording alone did not solve the enterprise workflow. Different teams had different needs, and IT/admin needed governance that could support scale.
BuildBetter unblocked parts of the workflow with meeting capture, summaries, searchable context, and flexible use cases — while surfacing the enterprise controls required for broader adoption.
The Catalyst
“I had difficulties with Zembly — searching for notes, sharing recordings — I hope BuildBetter addresses these issues.”
— Anne Hoang, MNTN
Before BuildBetter
MNTN had meeting and customer context across:
- internal meetings,
- product and engineering calls,
- revenue conversations,
- customer success discussions,
- Gong / Zoom-style tools,
- Zimbly / Zembly workflows,
- Highspot / enablement workflows,
- Jira / Asana,
- Slack,
- People Ops programs.
The problem was not meetings. The problem was governable meeting intelligence.
The Blocker
Different teams needed different outcomes:
- product and engineering wanted action items and handoff into Jira / Asana,
- CS wanted sentiment, severity, reporting, and customer context,
- managers wanted visibility into team blockers,
- revenue teams already had Gong-style tooling,
- IT needed SAML, SSO, permissions, private-meeting behavior, and safe data access.
The scaled rollout surfaced enterprise blockers around permissions, privacy, recording access, admin controls, and tool consolidation.
MNTN showed both sides of enterprise pull: teams wanted the product, but enterprise controls determined whether it could scale.
The BuildBetter Workflow
Cross-functional meeting or customer call
↓
BuildBetter capture and summary
↓
Searchable team context
↓
Governed access and admin controls
↓
Team workflow, report, or migration
What Changed
- more teams could capture and review meeting context,
- PMO could explore a broader operational use case,
- product, engineering, CS, and revenue stakeholders could evaluate team-specific workflows,
- People and culture teams found unexpected uses,
- IT/admin requirements surfaced what enterprise controls BuildBetter needed,
- the relationship remained constructive through consolidation and offboarding.
“Various teams were using BuildBetter creatively — our People’s team was using it for Music Monday and Soul Wednesday meditation recordings, linked to Highspot so people could watch later.”
— Crystal Mckinley, MNTN
