cl1ck
Ramp Hackathon. Automates automation.
The problem
Finance teams retype the same invoice data into the same forms hundreds of times a month. Each person builds private shortcuts that never reach the rest of the team, and nobody has time to write automation rules by hand.
Constraints
- Automations touch money, so nothing can run unproven.
- People should not have to configure anything: it should learn by watching.
- Model calls should be the exception, not the engine.
How it works
Capture: A DOM recorder observes how people fill forms.
Key decisions
Deterministic core
String alignment, counting and rule checks do the work. Claude is only used for unfamiliar layouts and plain-English edits, which keeps runs fast, cheap and explainable.
Prove before acting
A workflow has to match past work before it is allowed to run, so trust is earned with evidence instead of assumed.
Results
- Learns workflows by watching, with no rules written by hand
- Replays against past work before running
- Blocks duplicate invoices and over-limit bills
What I'd do next
Recording more varied document layouts to measure how often the deterministic path handles a new vendor without a model call.