How We Killed the Weekend Slide Scramble with Reviews

It's Sunday evening, you're staring at a blank Google Slides deck, and you need a polished weekly team sync ready by Monday morning. You're pinging your Head of Sales for pipeline numbers, asking your engineering lead which features shipped, and cross-referencing last week's metrics in a completely different deck to calculate deltas.

This was my life for the better part of a year. As of this past Monday, it isn't anymore.

We started using our own Reviews product to run our weekly team sync — and the shift has been dramatic enough that I wanted to document it.

The Old Way: Death by a Thousand DMs

I was the human API. Every week I'd open a fresh slides deck, then fan out across Slack DMs to five or six people. Message Sales for pipeline movements. Ping Engineering for features shipped and demos. Circle back to the CEO for kudos and focus areas. Every data point required a conversation.

Work was happening around the clock. We're an AI startup spread across two time zones: the US and India. When it's Friday afternoon in Seattle, it's Saturday morning in Chennai and work is still shipping. The freshest picture of the week doesn't exist until Saturday at the earliest — which means Sunday night is the first realistic moment to assemble anything accurate.

Data was stale by default. We were reconciling numbers across HubSpot, spreadsheets, and slide decks. Monday's presentation was often outdated by the time we presented it.

Version control was a nightmare. Over six months I sent dozens of unique Google Slides links — a new deck nearly every week, each a snapshot frozen in time. Comparing metrics week-over-week meant hunting down a different deck and manually computing deltas. No continuity, no living document.

The meeting itself suffered. So much energy went into assembling information that there was little time to analyze it.

The Turning Point

At the beginning of the year, we started using our own Reviews product for the Monday morning team meeting. No more Google Slides link. No more "ping me once you're done so I can review." Just a single, live dashboard created through Rhythms' AI chat, connected to Slack, Linear, GitHub, and HubSpot, that everyone could access anytime.

How It Works Now

Every Sunday night, the dashboard is regenerated. Rhythms pulls from our integrated systems: Linear for engineering work, HubSpot for sales, our OKRs for goal progress. The Features Shipped section — which used to require a weekly back-and-forth with our engineering lead — is populated automatically, complete with Linear tickets and engineer attribution.

It helps build the agenda. The product suggests feature demos to share with the team based on recently completed work. When an engineer finished a Review Template Management feature, the system flagged it. I just selected from a shortlist instead of asking around.

Review creation is semi-automated with AI. Department heads no longer build their sections from scratch or cobble them together using disjointed tools. When our CEO wanted to swap "Blockers & Risks" for "Goals & Progress," I prompted Rhythms' AI chat and it was instantly reflected for everyone.

No more stale data. Numbers update in real time. When a deal closes Friday afternoon, it shows up Monday without anyone lifting a finger.

What I Got Back

Weekly prep went from three to four hours down to 30 to 45 minutes. But the bigger win is qualitative.

I stopped being the bottleneck. The dashboard exists independently of my availability. The information is there whether I curate it or not.

The team engages differently. The meeting becomes a conversation rather than a presentation. Less time reading slides aloud, more time discussing what the data means.

It's not just me who feels the difference. Our Engineering Lead, Satya, put it bluntly:

"Us really using Reviews for our weekly meeting is a big milestone — personally, for me and for the team. I really loved it when I was editing it. And I hated PPT. It used to take so many hours just to edit and get the formatting right."

The "Export to Powerpoint" feature covers the cases where you still need slides. Why build slides from scratch when the information already exists and just needs to be assembled intelligently?

Leadership gets what they actually want. The goal of our weekly sync was always to build energy for a distributed team and keep everyone aligned on the big picture. A live dashboard with rich context, not just static numbers, solves that in a way a static deck never could.

Advice for Other Operators

Start with your most painful recurring meeting. Pick the one where you spend the most time collecting and assembling information.

Map your data sources. Write down where every number in your current deck comes from. You'll find it scattered across four or five tools. That map becomes your integration checklist.

Don't replicate your slides. A dashboard is not a slide deck, and that's the point. You need the same insights delivered in a way that's connected, current, and collaborative.

Let the tool suggest, then curate. The Chief of Staff role shifts from data assembler to editorial curator — a much better use of the job.

The Meta Moment

There's something deeply satisfying about using your own product to solve your own problems. Every friction point became a bug report. Every moment of delight confirmed we're building something that matters.

We built Rhythms to replace the manual overhead of running a business — the endless check-ins, the stale decks, the information trapped in silos. I just didn't expect the most convincing proof point to come from my own Monday mornings.