Why Your Company Should Be Recording More Meetings

Haghani describes Circleback as a tool that records and transcribes meetings, creates notes, and assigns action items. It can also extract custom information for apps such as a CRM, issue tracker, or Slack, and answer questions across a team’s conversations. His desk setup is minimal; he highlights a quiet Topre keyboard and a small toy he kept after nearly buying several items through a Temu promotion.

Haghani uses Circleback to track recruiting follow-ups, candidate interviews, and the company’s conversations with people at YC. Before this interview, he asked it to prepare a summary using past meetings, emails, and his calendar. He also starts recordings with his phone’s action button and says a watch app is in beta.

Haghani has separate OpenClaw agents for general tasks, finance, customers, and people operations, and is moving some workflows into Slack so the team can share customer support and sales context. He describes engineers taking turns handling incoming support. Circleback can retrieve customer feedback from recorded meetings, answer questions about it, and help draft a follow-up email.

Haghani says he is spending less time coding because the company needs more people to increase its capacity for product decisions. He uses coding agents for most implementation and reviews their work, with different agents checking code quality, architecture, product choices, and copy. The team uses evals for measurable outcomes, such as avoiding action items that were already completed, and checks note quality as prompts and models change.

Haghani says agents may draft emails and product copy, but people should review before anything is sent or shipped. Engineers should design systems involving data access and security, while agents can help implement or review them. He expects companies to record more conversations so agents have useful context, while giving customers control over who can access what was captured.