I've been running Braintrust for our five-engineer team for about nine months now. We switched from a combination of Upwork and direct referrals, and I wanted to share a real, log-level review of what we've experienced—the good, the bad, and the config you might need to tweak.
The biggest win is the talent pool quality. It's not hype. We posted a niche role requiring experience with both Go and a specific telemetry protocol. Within 48 hours, we had five candidates who had actually built similar systems, and their vetting seemed to match reality. The interview-to-hire ratio felt dramatically higher than other platforms. The 10% client fee being capped is also a major win for larger contracts; the math becomes very predictable.
However, the platform's communication tools can be a pitfall. The built-in chat feels rudimentary. We quickly learned to move all substantive project discussions to our own tools (Slack, Linear) immediately after the match. Think of Braintrust's UI as the initial handshake and contract layer, not your collaboration workspace. Also, while the no-markup model is great, you need to be very clear on rate negotiation upfront. We had one instance where a freelancer's "profile rate" was listed, but their actual ask was 15% higher, which only came out in the first chat. It wasn't a dealbreaker, but it added friction.
From an operational/logging perspective, here's how we structured our workflow to avoid issues:
```yaml
# Our internal process after a Braintrust match:
1. Match on Braintrust -> Sign basic contract terms on-platform.
2. Immediate off-platform steps:
- Invite to company Slack (#external-contributors channel).
- Create Linear ticket for project, link to spec doc.
- Set up a weekly sync via Google Meet.
3. Payment tracking:
- Use Braintrust for invoicing/payment only.
- Log all hours/work in our internal systems for backup.
```
The takeaway? It's excellent for finding pre-vetted, high-caliber talent quickly, but you must have your own internal processes to wrap around the platform's limited project management features. It's a powerful sourcing engine, not an all-in-one solution. For a small, disciplined engineering team that knows how to manage remote contributors, it's been a net positive, but you have to architect your integration with it.
grep is my friend.
That "move to Slack immediately" tip is so key. We did the exact same thing after our first project. The Braintrust chat feels more like a messaging queue for contract logistics, not a real-time collaboration tool.
Your point about rate negotiation is crucial too. We learned to treat the initial rate discussion as a binding part of the offer, with zero ambiguity. One thing that helped was attaching a simple project spec document outlining the *exact* scope we were agreeing to for that hourly rate. It cut down on "but I thought this was included" conversations later.
How did you handle milestone-based work? We stuck mostly to hourly, but I'm curious if the communication gap made milestones trickier.
Comparing tools one review at a time.