Week 7: Raising Dead Features and the Magic of SDKs

Welcome back to week seven! If you remember all the way back to my Week 3 blog post, I used a mathematical framework called RICE to ruthlessly cut features from our product roadmap. One of the biggest casualties of that process was the “In-App Communication Hub.”

Even though creators and brands desperately wanted a place to chat without using scattered email threads, building a real-time messaging system from scratch (complete with WebSockets, message persistence, and UI rendering) was going to take a month of engineering time. For an early-stage, resource-constrained startup like SideShift, that was simply too expensive. So, I sent the chat feature to the backlog graveyard.

Or so I thought.

My core research thesis asks how startups can maintain agility when building features. This week provided the ultimate case study. Following my massive pivot to the Whop API for payments last week, I was reading through their documentation and discovered a goldmine: Whop recently released their own plug-and-play In-App Chat SDK (Software Development Kit).

Suddenly, the math changed. By leveraging their existing chat infrastructure, the “Effort” variable in my RICE calculation dropped from 4.0 weeks of custom coding to just a few days of integration work. The feature’s RICE score skyrocketed, and just like that, the Communication Hub was resurrected and pulled into this week’s active sprint. This is exactly what startup agility looks like in the real world: your roadmap isn’t a static document, but rather a living entity that shifts the moment new technology becomes available.

I spent the first half of the week integrating the Whop React SDK directly into our new Campaign Dashboard. I wrote the logic to map the chat channels 1:1 with our Firebase campaign documents. Now, when a creator clicks on a specific project, they immediately see a secure, isolated chat room dedicated solely to that brand and that specific deliverable.

But of course, nothing works perfectly on the first try. During integration testing, I found a frustrating user-experience bug. If a creator used our new dropdown menu to update the campaign status to “COMPLETED” (triggering the escrow payment), that action didn’t reflect in the chat log. A brand could be sitting in the chat waiting for an update, completely unaware the project was finished.

To fix this, I wrote a Firebase Cloud Function acting as a sort of robotic moderator. Now, whenever the database detects a status change or pending payment, it automatically injects a system message directly into the Whop chat stream (e.g., “Handles sent for approval” or “Payment of $150.00.has been transferred for your work on [CAMPAIGN]”).

With the chat feature officially working alongside the earnings dashboard and status tracker, our core ecosystem is finally complete. I spent my Friday jotting all of these insights down to next week wire all of these wild technical pivots into the “Development Process” section of my academic case study. Next week, it’s time to start polishing the UI and squashing bugs as we head toward full beta testing!