01 / The context
The problem behind the project.
A legal-marketing business needed a repeatable path from public court records to attorney marketing letters. The work began as a bounded build, then became an ongoing production responsibility within a decade-long subcontract relationship.
02 / The contribution
How I approached it.
- Built the court-records collection and letter-generation workflow during 2013–2014, using browser emulation to work with the available source interface.
- Connected recurring collection with document production so the daily process did not depend on rebuilding the workflow by hand.
- Operated and supported the production system over the following decade, including a weekend production-server rebuild.
- Maintained the system through the consultancy relationship. This case describes the engineering only; no individual records, correspondence, addresses, or letter contents are reproduced.
03 / The result
What the work made possible.
A daily production system supported through 2023. The case illustrates the long maintenance life that can follow a relatively contained automation project, and the responsibility of keeping the workflow dependable after its initial delivery.
10 yearsproduction operating history
Dailyrecurring workflow
End to endcollection through documents
