G2

Gorav A.

Catalog Management Executive

Mid-Market (51-1000 emp.)

10/30/2026

"Big time-saver for data work, but usage limits hurt"

4.5/5

What do you like best about Claude?

I use Claude every day at work, mostly through Claude Code and the desktop app, and the best part is that it plugs into the tools our team already uses. With the Metabase, Slack, Notion and Google Drive connectors it can query our data, pull context and then write up the findings in one place, so I'm not copying between tabs. I use it for root cause analysis on our funnel metrics (leads, bookforms, traffic), writing and checking SQL and building business review decks. Custom skills let our team save repeatable workflows, so a weekly RCA or a partner report follows the same steps every time instead of being rebuilt from scratch. It also handles long, multi-step tasks well and explains its reasoning, which makes the output easy to check before I share it. Review collected by and hosted on G2.com.

What do you dislike about Claude?

The biggest frustration is usage limits. On heavy days, especially long analysis or coding sessions, I hit the limit partway through a task and have to wait or split the work up, which breaks my flow at the worst moment. It would help to see more clearly how much usage is left before starting a big job. The second issue is connectors that sometimes fail to connect or need to be re-authenticated. When a data source drops mid-task, I have to stop, reconnect and rerun the step, and the error messages don't always make the cause obvious. More reliable connections and clearer errors would make it much smoother for day-to-day work. Review collected by and hosted on G2.com.

What problems is Claude solving and how is that benefiting you?

Before Claude, a lot of my time went into manual, repetitive analysis: pulling numbers from Metabase and Tableau, writing SQL by hand, digging into why a metric dropped week over week, and then turning all of it into a report or deck for stakeholders. Claude now does most of that legwork. I describe the question, it queries the data through our connectors, checks the likely causes, and drafts the write-up, so I spend my time reviewing and deciding instead of assembling. It also takes over tedious tasks like collecting property details from partner websites for onboarding and formatting quarterly business review decks. The main benefit is speed: work that used to take most of a day now usually takes a fraction of that, and I can answer ad hoc data questions from the team much faster. For what we pay, the time saved across the team makes it easy to justify. Getting started was also simple, because our team set up shared skills and connectors, so new people can follow the same workflows from day one. Review collected by and hosted on G2.com.