We rolled out Braintrust across our sales and CS teams a year ago, moving from a patchwork of spreadsheets and a basic HubSpot setup. The pitch was compelling: a unified platform for talent, projects, and payments. The reality has been a mix of genuine efficiency gains and some persistent, grating limitations.
Here’s the breakdown after 12 months of daily use by a 75-person team:
**What actually works well:**
* The project-talent matching is solid. It does save managers time sourcing.
* Consolidated invoicing and payment processing is a true administrative win.
* The unified profile for freelancers, combining work history and reviews, reduces back-and-forth.
**Where it stumbles or is just okay:**
* Reporting is surface-level. You can't build custom dashboards that combine project financials with talent performance metrics in a meaningful way. It's a major gap for forecasting.
* API limitations are real. We wanted to pipe project status changes into our internal Slack ops channel, but the webhook options are prescriptive and the docs are thin. You can't build complex automations off their events.
* The mobile app is essentially a notification viewer. You can't approve larger scope changes or access any meaningful reporting. It feels like an afterthought.
* UI "improvements" have twice broken our team's habitual workflows. Last quarter, they rearranged the project dashboard without a toggle to revert, which caused a minor revolt until everyone retrained.
It's not a bad platform. For a company that heavily relies on a flexible, external talent pool, it centralizes chaos. But it's not the all-seeing, all-automating brain the marketing suggests. It's a competent transaction layer with some intelligent matching on top. For the price, I expect deeper analytics and a less brittle interface.
We're sticking with it for now, but we're also evaluating whether to supplement it with other tools for the reporting depth we need. I'd be curious if other mid-market users have hit the same walls, especially with the API or in building internal metrics.
-- CRM Surfer
Your CRM is lying to you.
That point about the API hits home. We tried something similar, syncing completed project milestones to a custom field in our CRM. The webhooks were so limited we ended up using a clunky Zapier middle layer, which defeats the purpose of a unified platform. It feels like they built the core features but left the connective tissue as an afterthought.
The reporting gap is the real killer for us too. You can't mix talent performance data with budget burn in any useful way. Makes quarterly planning a manual spreadsheet exercise all over again, which is ironic.
—b
Clunky Zapier is the security red flag you're missing. Now you've got a third party service with broad permissions moving data between two critical systems, probably with overly permissive API keys.
If Braintrust's own webhooks can't do it, the platform isn't designed for secure automation. That's a hard stop for any real integration.
Least privilege is not a suggestion.