Plaid Nexus Logo
The Chaos

From WhatsApp Chaos to Plaid Nexus

The journey to building Plaid Nexus was fueled by a shared frustration familiar to every graduate student at CMU-Africa: the crushing weight of information overload.

We're all juggling an exceptionally demanding academic workload, battling late nights, and managing the high stakes of maintaining our scholarships. The last thing we need is for critical campus information, a facility closure, a career service event, or a research opportunity, to be lost in a torrent of two dozen WhatsApp groups or buried beneath an overwhelming stream of email. We realized the very fabric of our connected, collaborative campus was being undone by fragmented communication.

This wasn't just an inconvenience; it was a systemic problem costing us time, opportunities, and mental energy that should have been spent on innovation.

What Inspired Us: The Cost of Missing Out

The primary inspiration came directly from the pain points we experienced and validated through early research: the high friction of daily student life. We saw the duality of the CMU-Africa experience, immense prestige and opportunity alongside immense pressure. We recognized that while the institution offers world-class education, its support systems for day-to-day operations and proactive wellness were often reactive.

We were inspired to use our technical skills to create a proactive, centralized solution that reflected the excellence of the university's mission. We wanted to build something that was, at its core, a strategic investment in our human capital.

How We Built Plaid Nexus

Our solution, Plaid Nexus, became a focused effort to create a single, reliable source of truth and a hub for engagement.

Defining the MVP

We aggressively scoped the project down to a set of high-impact, achievable modules: Verified Announcements, Events, Opportunities, Structured Feedback, and a simple Chat.
We deliberately focused on quality and flawless execution over feature quantity, ensuring each component delivered immediate value.

The Codebase

Leveraging our engineering skills, we built the entire MVP as a highly polished, responsive web application (using HTML, Vanilla JS, and Tailwind CSS). This allowed us to iterate quickly and demonstrate advanced functionality without the complexity of a backend database.

Core Innovation

Our biggest technical challenge, and greatest triumph, was perfecting the Accountability Loop.
We engineered the logic for the Required Acknowledgment on announcements and the Priority Sorting that surfaces unacknowledged critical posts to the very top. This functionality, along with the Visible Ticket Tracking for feedback, transformed the app from a simple communication tool into a governance and service platform.

The Opportunities Hub with its filtering and saving capabilities, and the interactive Tartans Chat, further cemented Plaid Nexus as a comprehensive student engagement platform.

What We Learned

The hackathon process was an intense crucible, mirroring the pressure of graduate life itself.

User-Centricity is Non-Negotiable

We learned that simple ideas must have deep utility.
Features like filtering events by "My RSVP'd" status and creating intuitive filters for the Opportunities Hub were added after initial testing, proving that listening to user feedback is the fastest path to product-market fit.
The simulated Tartans Chat was added to address the need for informal peer connection within the hub.

The Power of Focus

When we faced competing ideas, we learned to double down on our unique differentiators: the Accountability Loop and the Institutional Buy-in (validated by our mentors' quotes).
This sharp focus is what gives Plaid Nexus its competitive edge, even as we expanded to include essential features like opportunities and chat.

Challenges Faced

Our primary challenges lay in balancing complexity with the short timeframe:

Simulating Persistence

Building features like Acknowledgment, RSVP tracking, the Opportunities 'Save' function, and even the basic chat input without a live database required clever use of local browser storage and in-memory updates.
Ensuring this logic was robust and bug-free across the various features was technically demanding.

Information Hierarchy

Achieving the complex sorting logic in the Announcements tab, prioritizing unacknowledged posts while maintaining reverse chronological order within those priority blocks, was the most challenging algorithm to perfect within the deadline.

Scope Management

We intentionally excluded features like complex chat history persistence (beyond the initial mock data) and full financial integration to deliver a polished, bug-free MVP.
Sticking to this strict scope, even with new additions, was the key to our success.

Ultimately, Plaid Nexus is more than just code; it's a testament to the fact that when CMU-Africa students identify friction, they build the solutions needed to sustain their resilience and fulfill their mission.

What's Next for Plaid Nexus: The Path to Institutional Integration

Winning the hackathon is just the first step.
The true mission for Plaid Nexus is to transition from a validated prototype to a core operational tool that services the entire CMU-Africa community.

Phase I: Institutionalization (Post-Hackathon - 3 Months)

Secure Institutional Partnership: Formalize mentorship and funding with the CMU-Africa administration and the Industry Innovation Lab (IIL).
Database Integration & Security: Migrate the mock data to a scalable, secure database (e.g., Firebase or Supabase). Integrate with CMU's Identity Provider for Single Sign-On (SSO) via Andrew ID verification, ensuring robust security and role-based access control.
Admin Console Development: Build a simple, robust web console for faculty and administrators to easily post verified announcements, manage event approvals, and triage feedback tickets.

Phase II: Feature Expansion & Utility (3-9 Months)

Full Chat Functionality: Implement persistent message history, direct messaging (DM), and role-based moderation for the "Tartans" chat.
Bridging Connector Engine: Develop a utility that allows authorized staff to seamlessly import curated summaries of essential information from official email digests or established WhatsApp groups into the verified channels.
IIL Partnership Feature: Enhance the Opportunities Hub to include direct integration with IIL project postings and an application tracking system, making it the official pipeline for student-industry connection.

Phase III: The Tartan Hub Vision (9+ Months)

Mobile App Development: Build native iOS and Android applications (using Flutter, for example) to ensure maximum accessibility and utility for the student body.