The situation
Where they started.
Every client sends placement files in its own layout. A person and a half spent their days turning those files into the one upload format the thirty-year-old collection system accepts. A failed system conversion the year before had made the agency rightly cautious: whatever came next could not touch the system of record.
What FlatClaw does
What was built.
- The agent watches the drop locations, reads each incoming placement file, and maps its columns onto the house schema using rules the intake team helped write.
- Anything it is unsure about is flagged, not guessed; the whole batch waits in an approval queue where a reviewer sees the mapping and the exceptions before release.
- Output is exactly the upload file the collection system already accepts, so nothing about the system of record changes.
- Runs entirely on hardware inside the agency's building.
Results
What changed.
- Intake becomes a review step instead of a data-entry job.
- New client layouts are handled by adding a mapping, not by retraining a person.
- Zero changes to the legacy system that the business depends on.
- Every release is auditable: who approved which batch, and what was flagged.