← All workCASE STUDY · MINDXBRIDGE · ACADEMIC MENTORING & PUBLICATION
One system for a business that runs on approvals, where each role sees only its part.
MindxBridge had outgrown an earlier prototype. I ran requirements sessions with the owner, wrote the rules down, and am building the ERP in Next.js on a committed five-week plan.
- ROLE
- Full-stack & AI engineer (contract)
- TIMELINE
- Aug 2026 – ongoing · 5-week plan
- STACK
- Next.js, TypeScript, role-based access control
- WAY OF WORKING
- Weekly deliverables, owner sign-off
THE BRIEF
Replace the prototype with software that follows the business's real rules.
The business runs on approvals: projects, payments and new mentors all need sign-off from the right people. The earlier prototype couldn't carry that, so the first job was to agree the rules before writing any code.
RULES WE AGREED FIRST
- A project goes live only after both QMP and CEO approval.
- Payment requests move from CEO approval to paid, and each role sees only the amounts it should.
- New mentors can register themselves, but only start after approval.
- Notifications arrive in the app first, then by email when a request stalls.
WHAT I BUILT
- One Next.js app with four role-based dashboards: CEO, Operations, QMP and Mentor.
- A two-step project approval workflow.
- Payment requests with per-role visibility of amounts and statuses.
- Approval-gated mentor self-registration.
- Live task timers.
- Escalating notifications: in-app first, email when something stalls.
HOW IT FITS TOGETHER
CEOFinal approvals, payments
OperationsDay-to-day running
QMPFirst project approval
MentorOwn tasks and timers
PROJECT
Created
QMP approves
CEO approves
Live
PAYMENT
Requested
CEO approves
Paid
NOTIFICATION
In-appSent first
Stalled?No action taken
EmailEscalates
DECISIONS
DECISIONPlain code for approvals and money, not AIWHYThese rules must behave the same way every timeTRADE-OFFAI comes in the next phase, on top of solid rules
DECISIONRules written down with the owner firstWHYMost ERP rework comes from rules nobody agreedTRADE-OFFSessions before the first line of code
DECISIONWeekly deliverables on a five-week planWHYThe owner sees progress and steers earlyTRADE-OFFScope is fixed per week, changes queue for the next
WHAT'S NEXT
The next phase is scoped with the owner: Claude-based messaging automation and an AI voice caller, built on top of the ERP.
RESULTS
4role dashboards in one app: CEO, Operations, QMP and Mentor
2sign-offs before a project goes live, QMP and CEO
1app replacing the earlier prototype