← All cases
Docs platform · Paid sprint

Exchange Student Company's document system, built from a real cohort's WhatsApp history.

Student records, document approval, visa tracking, host-family placement, flights, insurance, and role-based access for agents, managers, parents, and students, replacing a process that lived in WhatsApp groups and someone's memory.

Engagement
Paid sprint
Timeline
4 weeks, then ongoing
Stack
Multi-role access, Google Drive sync, automated backups
Exchange Student Company's document system, built from a real cohort's WhatsApp history.
The challenge

Exchange Student Company places Brazilian students into US exchange programs, through ICES and sponsors like Troika ISE and Master Studio, but the real process lived in scattered WhatsApp messages: documents sent as photos, powers of attorney typed by hand inside a group chat, vaccine pending items as loose texts, and no answer to “where's my kid's passport” beyond someone remembering to reply.

The approach

We read the literal WhatsApp history of a real cohort, 15 group chats, and turned every repeated pain point into a field, screen, or alert. The first prototype already shipped student registration, Google Drive sync, Notion-sourced partner guides, and login with password recovery; visa workflow, a shared calendar, and centralized manager/master_admin permissions followed over the next two weeks. A concentrated wave then shipped eight parallel improvements, planned and executed across seven isolated worktrees and merged in one pass, while a real cohort was actively arriving, so most of the roadmap was answering a specific family's problem that same week, not a hypothetical one.

What shipped

Built from the commit history, not a feature wishlist.

Documents
  • Upload by category, with approval/rejection and reviewer comments
  • Bulk import from Google Drive, with a preview before applying and full dedupe
Visa & travel
  • A post-interview state machine (approved, denied, 221g administrative processing)
  • Host-family placement, flights parsed automatically from the ticket, and a boarding checklist
Roles & access
  • Six isolated roles (agent, manager, master_admin, sales, parent, student), with an automated isolation check required before every deploy
  • Invite-only accounts, with two-step approval from pre-registration to master_admin sign-off
Infrastructure
  • Automatic deploy to Hostinger, with validated daily backups of the database, files, and environment config
  • Audit logs visible only to master_admin
The result
150
commits from prototype to a live, multi-sponsor system
15
real WhatsApp group chats read to shape the product
100%
of student records now in one system, no more scattered WhatsApp threads
Since launch
⚠
Sponsors have since come on with their own document rules, and bulk student enrollment now runs through GitHub Actions with no student data touching the repository. An automated role-isolation check runs before every deploy — what used to be a hope is now a gate.
Let's talk

Tell us what you want to ship next.
We'll show you how fast it moves.

A 30-minute diagnostic call, no deck, no pitch, just the project.