Separate the user journeys
Provide parent-facing access and administrator views appropriate to each role.
INTERNAL TOOLS / Invictus Nashville
An AI-assisted app for tuition plans, Stripe payments, voucher credits, and reconciliation.
SEE THE WORK
One family's month, with vouchers applied automatically and exceptions set aside.
| Date | Description | Amount | Status |
|---|---|---|---|
| Oct 3 | Family installment 1 of 2 | $37.50 | Paid |
| Oct 6 | State voucher · Batch 14 | $155.77 | Applied · emailed |
| Oct 13 | State voucher · Batch 15 | $155.77 | Applied · emailed |
| Oct 17 | Family installment 2 of 2 | $37.50 | Paid |
| Oct 20 | State voucher · Batch 16 | $155.77 | Applied · emailed |
| Oct 27 | State voucher · Batch 17 | $155.77 | Expected |
Recreation of the admin view from the portal I built on Supabase with Stripe payments. The family and card are fictional (4242 is Stripe’s public test card). The structure is real: $750 monthly tuition, voucher coverage that varied by family up to 100%, credits posted in weekly state batches, and an email to the family each time showing what was covered and what they owed.
| Received | Payer | Amount | Suggested match | |
|---|---|---|---|---|
| Oct 20 | another@example.com | $37.50 | No match | Assign |
Recreation of the reconciliation view. Payers and amounts are fictional. Voucher credits and scheduled payments posted on their own, with families notified by email, so nothing routine waited on staff. Only a payment the system couldn’t place, like one from an unrecognized email, landed here.
THE STARTING POINT
Tuition administration spans several connected tasks: setting up a plan, helping a family make a payment, associating payments with the correct account, and investigating exceptions. The application brings those tasks into a shared workflow.
THE WORK
Provide parent-facing access and administrator views appropriate to each role.
Build workflows for tuition plans, family records, autopay setup, and payment information.
Provide a reconciliation queue for unmatched payments, with options to associate a payment or dismiss an unrelated entry.
Include permissions, audit logging, and account-recovery workflows.
HOW AI FIT IN
This was my most AI-driven build. AI wrote much of the code and helped design the database on Supabase, deployed through GitHub and Vercel. I defined what the system had to do, reviewed every output, and pushed back until it matched how payments actually worked. Everything was built and tested with sample data; no real family names or payment amounts went into AI tools.
THE RESULT
HOW THE WORK CONNECTS
A simplified illustration of the application’s family and administrator workflows.