StackOne Gateway

What do you like best about the product?

I connected Claude to Notion and Google Drive through StackOne and had it working the same afternoon. Now I ask it to pull our planning docs together without opening five tabs.

What do you dislike about the product?

Honestly nothing so far, it has done what I needed.

What problems is the product solving and how is that benefiting you?

We're a small founding team, so time is tight. One place where the assistant can read our docs means less copying and pasting between tools.

What do you like best about the product?

I manage seven Account Executives across UK Public Sector and Ireland, so my week is one to ones and pipeline reviews. I connected Claude to my Salesforce, Gmail and Slack through StackOne. Before each one to one I ask for that rep's latest deal threads and what's due, and I walk in with the picture already pulled together.

What do you dislike about the product?

Hard to find fault so far, and the StackOne team have been quick whenever I've had a question.

What problems is the product solving and how is that benefiting you?

Coaching is the part of my role that matters most. Less of the week goes on digging through inboxes and notes, so more of it goes on the reps.

What do you like best about the product?

I look after operations for our Zero Bills Homes partnerships, which means a lot of housebuilders, sites and handovers to keep track of. I connected Claude to Google Sheets, HubSpot and Slack through StackOne. Now I ask where a site is up to and it pulls the tracker, the latest partner emails and the Slack thread together. Each connector took a couple of clicks.

What do you dislike about the product?

Nothing that has slowed us down so far.

What problems is the product solving and how is that benefiting you?

Nothing that's slowed us down so far.

What do you like best about the product?

Most of my week goes on brands looking at sponsoring the T100 Triathlon World Tour, and the admin around each deal adds up. I connected Claude to HubSpot, Gmail, Teams and Zendesk, so before a call it can pull the deal history, find the last email thread, support tickets. This gives me the most up to date information before going into a sales convo. Each connector only took a few clicks to add.

What do you dislike about the product?

No complaints so far, it has been reliable every time I've used it.

What problems is the product solving and how is that benefiting you?

Getting ready for a sponsor meeting used to mean digging through HubSpot, my inbox and old decks. Now StackOne helps Claude brings it together and drafts the follow-up email, and I check it before it goes. That leaves more time for the conversations that close partnerships.

What do you like best about the product?

Not having to worry about optimising my agents' token spend when using external tools e.g. Jira

What do you dislike about the product?

It's an extra tool to add to my stack, which has a modest learning curve, but makes up for it by replacing others

What problems is the product solving and how is that benefiting you?

Solving our AI spendature, which is becoming more and more important as time goes on.

What do you like best about the product?

What I like is that it takes some of the admin out of using AI across our engineering tools. I don't want every new connection to turn into another bit of glue code we have to look after. Having the connections and permissions in one place makes that side of things easier.

The visibility is useful too. I can see which person an action belongs to and which tools are getting used. That gives me a clearer picture of how the team is using AI as we open it up to more people, and helps me work out where it's actually useful.

What do you dislike about the product?

I'd like more practical examples of how to use the connected tools together. Once someone has access, they still need to work out which tasks are worth trying with AI. A few short walkthroughs for everyday engineering jobs would make it easier to get people started and save us having to explain the same workflows each time. For example, showing how to bring an issue, the related code changes and a team discussion into one task would be a useful starting point.

What problems is the product solving and how is that benefiting you?

At Gravity Sketch, we build a Unity app for VR and desktop. Investigating a bug can mean pulling together a ticket, code changes and team discussions. Connecting AI to that context is useful, but maintaining separate integrations adds work for engineering.

StackOne gives us one place to manage connections and individual access. That means less integration maintenance and more time to focus on the app. Being able to trace actions back to each user also helps us understand how the tools are being used.

What do you like best about the product?

Very responsive to requests. Great team to work with.

What do you dislike about the product?

Nothing, the team has been very supportive and responsive to requests.

What problems is the product solving and how is that benefiting you?

A centralized place for MCP connectors. We’re able to manage access by setting up and controlling permissions, which makes administration much easier.

What do you like best about the product?

I'm an early user of StackOne. Currently, every Monday I pull together what campaigns we sent, what's coming up and what press we picked up. I added StackOne into ChatGPT, and it can now read the plans in Google Drive, checks the team's updates in Slack and drafts the round-up as a Google Slides deck. I tidy it and share it. Setting up each connection took a couple of minutes. This is all stuff ChatGPT can do, but I like having it managed in one place, where I can track the success of each tool call. I find the dashboard very intuitive to use, which allows me to develop my connectors further

What do you dislike about the product?

Would be cool to have more detail on the connector roadmap on the webs

What problems is the product solving and how is that benefiting you?

The round-up used to take most of Monday morning. Now there's no more copying between tools, and it's ready before our first meeting, so the whole team starts the week knowing what's live and what's next. I've started using the same setup for event briefs. When I had a question early on, the StackOne team got back to me the same day.

What do you like best about the product?

We hold a lot of drivers' personal details, so before any AI touched our tickets I wanted to know exactly what it could see. StackOne let me lock that down field by field, and there's a log of every action the agent takes, which kept our security team happy. I connected it to Claude in an afternoon and it now works across Zendesk, HubSpot and Slack, including the bits Claude has no native connector for.

What do you dislike about the product?

Nothing so far, it's done what we needed.

What problems is the product solving and how is that benefiting you?

A charger or tariff query used to mean checking the ticket, the order and the install notes, then chasing the right team in Slack. Now Claude pulls it together and drafts the reply for us to check. It only loads the tools it needs for each question, so token use stays down as more of the team get on it.

What do you like best about the product?

I added StackOne’s MCP to ChatGPT and connected Gmail, Google Drive, and Slack. I can ask it to pull together the week’s coverage from my inbox, match it against the plan in Drive, and draft the client update. On top of that, connecting each account took virtually no time at all.

What do you dislike about the product?

Nothing really, maybe a few more ready-made examples for comms work.

What problems is the product solving and how is that benefiting you?

As a one-person consultancy, admin eats into client time. The Friday report used to take most of the afternoon and is now a quick check. Any questions I've had, the team answered quickly.