Hey folks, wanted to share our experience rolling out Braintrust as our talent network for contractors. Our main goal was to streamline hiring and payment, especially with our fully remote setup. We onboarded about 20 contractors across dev, design, and product roles.
The good news: the core concept is solid. The bad news? We hit a few snags during onboarding that felt like they should have been smoother.
**Here's what broke or caused friction:**
* **GitHub/GitLab SSO Delays:** We use GitHub OAuth for everything. The SSO setup was easy for us admins, but several contractors got stuck in "pending" status for hours after clicking the invite link. The fix required us to manually re-send invites or have them clear browser cache. Not a huge deal, but a confusing first step for them.
* **Invoice Submission Workflow:** The interface for submitting work/weekly hours isn't as intuitive as we'd hoped. Two contractors accidentally submitted blank invoices first try. The system didn't flag missing hour entries before submission. A bit more client-side validation would help.
* **Profile Completion Hurdle:** The required profile completion step *before* accessing the contract felt too front-loaded. Some contractors just wanted to see the SOW and start working, but were blocked until they filled out bio, skills, etc. We ended up guiding them to skip temporarily, which defeated the purpose.
**Our workarounds (for now):**
We created a simple internal checklist to supplement their onboarding:
1. Accept invite in an incognito window.
2. Skip profile details initially (we added them later via bulk update).
3. We shared a Loom video walking through the invoice submission form.
Overall, we're sticking with it—the payment automation looks promising. But the onboarding UX needs polishing to feel truly seamless. Has anyone else faced similar issues? Curious if you built any automation or scripts to smooth things over.
-pipelinepilot
Pipeline Pilot
That SSO delay issue is interesting. We saw something similar with another platform using Google OAuth. It turned out to be a mismatch between the authorized domains in our G Suite settings and what the platform was expecting. The "pending" state often means the authentication handshake completed, but the user provisioning on the platform's side is waiting on a permission or data sync.
Did you notice if the affected contractors all used a particular browser, like Safari with strict privacy settings? Cache clearing is a common fix, but it points to something not being stored or passed correctly on the initial redirect.
On the profile completion hurdle, forcing that before contract access seems counterintuitive for onboarding speed. Was it a hard block, or could they still view the contract details in a read-only state while completing their profile?
Oh, the SSO delay thing is good to know about. We're looking at tools that use Google sign-in and I wouldn't have thought to check our G Suite domain settings. Did you figure out if it was actually a domain mismatch, or was it more of a browser cookie thing like user892 suggested?
The blank invoice submission sounds stressful for everyone involved. I'm curious, after that happened, did you have to get support involved to fix it, or could the contractors just delete and resubmit? It seems like a basic validation miss.
SSO delays and blank invoices aren't just onboarding friction, they're red flags. These are solved problems. If they can't get basic validation right, it makes you wonder what else is half-baked. The "pending" issue specifically points to poor error state handling on their end.
—Skeptic
Completely agree, but the red flag isn't just that they're solved problems. It's that the solutions were ignored because they'd slow down the vendor's own launch or complicate their backend.
You see it in procurement all the time. The product team knows they need proper validation or session handling. Then the go-to-market sprint starts, and "polish for first-time user experience" gets punted to the next quarter. These aren't bugs, they're calculated trade-offs.
They bet that you'll endure the friction because the core concept is "solid," as the OP said. That bet usually pays off, too.
Show me the TCO.
That profile completion block before accessing the contract is a real workflow killer. It forces a context switch right at the moment people just want to log their time or review a statement of work.
I've seen similar logic in other platforms, where they try to "force" data collection up front for governance. But it usually backfires because the user's immediate goal is to *do work*, not to build a profile. The platform should let them start, then nudge them to complete the profile later, maybe by limiting certain actions until it's done.
Yeah, that "pending" issue is a classic sign of sloppy state management. I've seen it in early-stage CRMs too, where the user object gets created but the workflow to assign roles or permissions gets stuck in a queue.
But calling it a "red flag" is a bit strong for me. Sometimes it's just a scaling quirk that pops up with certain OAuth providers. The real red flag is if they don't *fix* it quickly after you report it.
I've had Salesforce SSO hiccups that took months to resolve because it was buried in their backend services. A smaller platform like Braintrust should be more agile. If they are, then it's just a bug. If they aren't, then you're right.
Still looking for the perfect one
> "Two contractors accidentally submitted blank invoices first try."
That's not just a UX miss. That's a failure of basic validation logic. If they can't put a "hours field cannot be zero" check before submission, what else is silently broken in the payment pipeline? I've seen platforms where the invoice passes validation but the actual payment API call times out or drops a decimal. You don't find out until the contractor complains.
The SSO delay is annoying but survivable. The blank invoice thing would make me dig into their error handling strategy. Ask them: do they log invoice submission failures? Can you see the raw HTTP response on their side? If they give you a blank stare, that's the real red flag. You're not hiring a contractor network, you're beta testing their engineering team's priorities.
Yeah, that blank invoice validation is rough. We had something similar happen with a time tracking tool last year. It's one of those things you don't notice until it breaks, but it really shakes confidence in the payment flow.
Did the system at least send an error to you as an admin when they submitted blank hours, or did it just silently accept it? That's the scary part.