Case Study · Foundry Logistics
Tuesdays became Tuesdays.
Replaced a 6-person manual reconciliation with an event-driven pipeline that flags exceptions only.
Industry3PL / Logistics
Engagement10 weeks
StackPython · Postgres · Slack API
Result−92% reconciliation hours
The brief
Foundry's accounting team spent every Tuesday reconciling carrier invoices against shipment events. The work was correct, painful, and structurally pointless: every event had a unique ID; every invoice cited that ID. We just needed the two systems to talk.
What we built
An ingest service that watches both feeds, matches by carrier + ID, and posts mismatches to a Slack channel only when human judgment is needed.
Production in 11 days. Tuned for 6 weeks.
Results
- 120 hours/month reclaimed across the team
- 6 people freed from Tuesday reconciliation
- Exceptions only — the system is silent when everything matches
- 11 days to first production deploy
Book a call
Fifteen minutes to figure out if we're a fit.
Bring the messiest thing you're dealing with. If we can't help, we'll tell you — and usually recommend someone who can.
- No sales deck, no follow-up sequence
- Walk away with a written plan of attack
- Free, zero-obligation, 15 minutes max
Reply within
24 hours · usually 2
01 · Scope02 · Time03 · Confirm
What do you need help with?
How would you like to work?
Sprint (4 weeks, fixed)
Retainer (monthly)
Custom / not sure yet
What's hurting?
Automate manual work
Unify data / reporting
Build an internal tool
Connect systems
Process audit
Something else