Bulk Workflow Automation
Straight-through processing on a legacy platform with no API, and an audit trail.
Browser automation across a legacy ASP.NET platform - frame-aware handling, postback-safe waits, error recovery and CSV audit logging - converting repetitive reviewer steps into straight-through processing while leaving compliance a record of exactly what ran.
Internal enterprise tool; not publicly demonstrable.
At a glance
The constraint
The platform has no API. It is a legacy ASP.NET application with nested frames and full-page postbacks, which breaks naive automation in a specific way: the script races ahead of a postback, acts on a stale DOM, and either fails loudly or - far worse - succeeds on the wrong record.
How it is built
Frame-aware element resolution rather than flat selectors. Postback-safe waits that key off the actual page lifecycle instead of a fixed sleep. Error recovery that returns the session to a known state rather than aborting mid-sequence. And a CSV audit log of every action taken, with its target and outcome.
Why the audit log is the point
In a regulated workflow, automation without an audit trail is not usable regardless of how well it works - you cannot answer the question "what did it do on this case" six months later. The log is the deliverable as much as the automation is. This is the pattern I bring to any legacy-platform automation: assume you will have to prove what happened.
Built with
Next case study
IronSight AI →
A private, in-house machine-learning analytics platform. Roughly 93 programs and 31,000 lines, built and operated solo.