Getting a catering company off legacy software it had outgrown
A catering business ran on a legacy vertical package. Everything the company knew lived inside a tool that would not let it out. I moved 947 events and 903 client records into a modern stack and built an agentic communications and reporting layer on top.
- 947
- Events migrated
- 903
- Client records migrated
- 1
- Legacy systems replaced
The situation
The company ran on a vertical software package built for catering operations. It held every event, every client, and every piece of history the business had. It was also the reason nothing else could be automated.
What was actually broken
- The operational history of the business was locked inside a tool with no practical way to get it out or build on top of it.
- Reporting meant exporting and rebuilding the same spreadsheets by hand, every time.
- Client communication was manual, so follow-up quality depended on how busy the week was.
What I built
- A full migration of 947 events and 903 client records into GoHighLevel, including the record structure to hold them.
- An agentic AI communications layer that works against live event data instead of a static template.
- A business intelligence layer on Postgres, so reporting reads from a real database rather than an export.
What changed
- The operational history of the business now sits in a system other software can reach.
- Reporting comes from a database instead of a manual export.
- Client communication runs from event data, so it does not degrade when the calendar gets busy.
Stack
GoHighLevel PostgreSQL Python Agentic AI workflows
This client is not named. If you want a reference before signing, ask on the call and I will arrange one where the client has agreed to it.