SaaS platform framing
Tenant admin language changes the pitch from internal tool to platform product, which broadens its case-study value.
Recovery and Collections/admin/debtors5 screens
The Collector - Multi-Tenant Collections Platform
Collections platform with debtor imports, status handling, payments, finance, and messaging inside a multi-tenant admin view.
Screen walkthrough
A fuller gallery for the product story.
This gallery is meant to show progression, not just a single hero frame. Use it to talk through navigation depth, records, analytics, and workflow context during a call.
/admin/debtors
Screen 01
Primary interface capture used for the listing card and story lead.
Overview
This product has a stronger SaaS operations story than a single-institution collections tool because the interface explicitly references tenant administration. The debtors screen exposes account imports, reminder status progression, payments, finance, and AI operations in one command surface.
Strongest story angle
Use this one to show that the portfolio can cover both collections workflow design and multi-tenant platform architecture.
Observable modules
DashboardAccountsPaymentsFinanceMessagesCollectionsAI OperationsImport DebtorsAll StatusesReminder stages
Why this one works
Three angles worth carrying into the final write-up.
Collections workflow depth
The visible reminder states and debtor import flow show process depth rather than a shallow reporting-only dashboard.
Operations plus finance
Payments, finance, and messaging sit together, which supports a fuller narrative about end-to-end recovery handling.
Motion outline
This sequence can still become a short teaser.
- 01
Open with the multi-tenant collections title and debtors view.
- 02
Animate import, status progression, and finance callouts across the interface.
- 03
Finish on the platform story: one collections engine serving multiple operating contexts.
Next publishing pass
The structure is now cleaner: better screenshots, stronger conversion paths, and shared page chrome that behaves correctly. The next layer is adding repository-backed build notes and verified outcome data.
Still worth adding
- 1. Verified repository context for stack and architecture notes.
- 2. Approved proof points to replace generic performance language.
- 3. Short teaser renders once the repository evidence is in place.