Why I Deleted My Custom "Crew" Logic Mid-Build

I was deep into building a custom "Crew" management system for my Next.js SaaS, a job and invoice tracker for small businesses. Everything was all set. My hooks were in place state was wired up and my UI components were all working. I looked closer at my auth layer and realized my provider better-auth 's native organization plugin already handled multi-tenant access control. This was the exact problem I was solving from scratch. The Mid-Build Pivot At that point I had two choices: Keep the custom implementation and own it long-term Adopt better-auth's native organization plugin and retire my abstraction The trade-off was obvious. My custom "Crew" layer duplicated what better-auth was already handling; the member schema, tenant context, permission propagation. Keeping it meant owning edge cases, permission logic, and future schema drift. The Pivot meant letting the library handle what it was built for. Why the Native Approach Won I wasn’t evaluating a dozen alternatives. I was already o