Customers

Case studies, with names on them

Most of our customers are anonymised on this site, and that stays the default. When a customer agrees to be named, the full story goes here: what they asked for, what we built, and what changed, measured from production.

Published with permissionMeasured from productionFull write-ups as PDFs
Industry
Commercial coffee roasting equipment
Systems kept
Odoo Online, Ramp
Service
AI agent development

AI agents inside the ERP they already run

The problem

Odoo was already reading Diedrich’s vendor bills, and people were still retyping them: zero quantities on purchase-order bills, due dates and account splits fixed by hand, and a CSV round trip for every batch of Ramp card charges. They wanted the retyping gone without changing systems, and nothing posted to the books that could not be proven right.

What we did

  • A bill reviewer that checks Odoo’s draft against the document field by field and writes back only the fixes
  • A card feed that turns Ramp charges into coded Odoo expenses, receipts attached, with no CSV
  • Every held bill goes to the AP specialist as an Odoo To-Do, with the reason
  • Scoped from three screen recordings; writing to the live books eleven days later
456bills graded field by field against what staff actually posted
96–99%right on vendor, invoice number, bill date and total
176card expenses created in Odoo with receipts attached
89%of would-be unattended posts right in every field, so posting stays with a person
Five pages: the problem, the build, the safeguards, and the results, including where it is not yet good enough.
Industry
Student and group travel
Replaced
WordPress, a billing app, a legacy quoting tool, spreadsheets
Service
Custom modules · Portals

One connected system for a student-travel business

The problem

A single school trip touches sales, pricing, suppliers, rooming, families, waivers and payments, and at Adventure Student Travel each of those lived somewhere different: a WordPress site, a separate billing app, a quoting tool on an office server, a hosted database of 158 tables and a set of spreadsheets. Staff spent their days re-keying the same trip from one tool to the next.

What we did

  • A trip-building ERP: sales pipeline, proposal pricing with rooming and free-adult rules, budgets, payables approval and branded itineraries
  • A CRM with years of client history, agent task lists and calendars, reading trips live from the ERP, on one login
  • A branded portal where families register, sign waivers on screen and pay by card against a schedule
  • A new website that kept the old site’s links, with an AI chat assistant, all in five weeks
5 weeksfrom first concept to the website, family portal, trip builder and CRM in daily use
888,510legacy records exported, mapped and brought across
79,004bookable products priced in the trip builder
7,868old website URLs redirected, so links and search rankings carried over
Six pages: the problem, the four systems we built, how families’ money and data are protected, the rollout, and the results.

Want a story that looks like yours?

Tell us your systems and the work your team retypes. We will tell you what an agent can take, what it should hand back to a person, and how you would know it is right.