How we turned five tools into one platform for InvoNexus
InvoNexus was running sign-ups, mentor bookings, events and job posts across forms and WhatsApp. Here's how we put it all in one place, and why the admin panel mattered most.
When we first got on a call with the InvoNexus team, they showed us how they were running things.
Bootcamp sign-ups came through a Google Form. Mentor bookings happened in WhatsApp. Events and job posts were also handled in WhatsApp or by hand. One person was basically keeping all of it in sync.
It worked. But you could tell it wouldn't for much longer.
The real problem wasn't the tools
Each tool on its own was fine. A form is fine. WhatsApp is fine. The problem was everything in between:
- copying details from one place to another
- checking who paid and who didn't
- answering the same questions again and again
- one person being the only one who knew where everything was
When a small team grows, this is usually where things start to break. Not because anyone is doing a bad job, but because the setup depends on one person remembering everything.
What we built
We put it all in one platform.
For students:
- book paid 1:1 sessions with mentors
- grab a seat in a workshop or bootcamp
- sign up for events
For companies:
- post jobs
- look through the talent pool
For the InvoNexus team:
- one admin panel to run all of it
Why the admin panel got the most attention
The admin panel is the part I spent the most time on.
It's easy to focus on what students and companies see, because that's the part that looks good in a demo. But a platform like this only stays useful if the team can keep it fresh.
If adding a new mentor means messaging a developer, the platform goes stale fast. New bootcamps don't get added. Old events stay up. People stop trusting what they see.
So the goal was simple: the team should be able to do the everyday work on their own, the same day. Add a mentor, open a new bootcamp, post an event, update a job. No developer needed.
The stack
We built it with Next.js, NestJS and PostgreSQL. Nothing fancy, on purpose. These are well known tools, so the platform is easy to keep running and easy to hand over.
If your team is in the same spot
If you're juggling a few tools and wondering whether it should all be one product, here are a few honest questions to ask first:
- Is one person holding it all together? If they're away for a week, does the work stop?
- Are you copying the same details between tools? That's usually the first sign.
- Can your team make everyday changes without a developer? If not, any new system needs a good admin side, not just a nice front end.
Not every team needs a custom platform. Sometimes a couple of good tools connected together is enough. But if the answers above are mostly yes, it's worth a conversation.
If you'd like to talk it through, book a short call or send us a brief. You can also see the live site at invonexus.pk.