B2B SaaSClient work
Reading site paperwork so the team does not have to
A management SaaS for construction companies. I built the pipeline that receives a supplier invoice by email, reads it with an LLM, weeds out duplicates and files it against the right site.
- Role
- Lead full-stack developer
- Client
- Construction SaaS company
- Year
- 2025 – 2026
- merged pull requests in fifteen months
- 337
- document types read by the pipeline
- 23
- developers led
- 5
Context
Invoices, company registrations, social-security certificates: paperwork arrived as scans and photos, and every company had its own approval chain.
What I built
- 01Expense pipeline: email in, storage, background job, LLM reading, duplicate check
- 02Automatic matching of expenses to sites, with a confidence score
- 03Document analysis generalised to 23 types, from company registrations to technical specifications
- 04A dry-run mode for the workflow engine
Key decisions
No client's data in another's view
Switching company in the app briefly showed the previous company's data. I made it cancel in-flight requests, evict every tenant's cache and invalidate the copy kept in the browser.
Hiring on evidence
A dozen take-home tests reviewed to build the team. Two of the hires went on to be among the product's biggest contributors.
Outcome
Paper approval chains became configurable workflows, and paperwork is read without retyping.