Daily work surface
The modules point to a product meant for operators who manage cases, money movement, and communication throughout the day.
Recovery and Collections/admin5 screens
Kyle & Smith - Debt Collection Platform
Debt collection admin workspace with debtors, clients, payments, messages, and AI operations presented from one recovery desk.
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
Screen 01
Primary interface capture used for the listing card and story lead.
Overview
The Kyle & Smith platform reads like a daily operator system for a legal collections team. The visible navigation spans debtors, clients, payments, messaging, and AI operations, while the dashboard shows collections by institution, outstanding balances, and recent activity.
Strongest story angle
Tell this story as a recovery desk built to coordinate portfolio oversight, debtor handling, and operator action from one screen.
Observable modules
DashboardDebtorsClientsPaymentsMessagesAI OperationsCollections by InstitutionDebt by Status
Why this one works
Three angles worth carrying into the final write-up.
Collections visibility
Top-level dashboard language focuses on collected versus outstanding value and activity tracking, which is exactly the story collections teams care about.
AI assisted operations
The dedicated AI operations area gives the case study a modern workflow angle without needing to overclaim automation outcomes.
Motion outline
This sequence can still become a short teaser.
- 01
Introduce the legal collections brand and admin shell.
- 02
Pan across debtors, payments, messages, and AI operations with metric overlays.
- 03
Close on the recovery desk story: one command surface for collections teams.
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.