Mesa CRM

The problem

Sales, purchasing, production, shipping and accounting each ran in a different program. The same data was typed in several times and the real cost of a job only surfaced at month end — and every new need meant touching the software again.

What I built

I built the chain on a single data set: quotes and orders, purchasing, bills of materials and work orders, batch costing, shipping, warehouse, service and HR. The structure is fully parametric — fields, process steps and permissions are defined from the screen — with accounting, fleet-tracking and marketplace systems connected through integrations.

• Sales, quoting and purchasing flow
• Bills of materials, work orders and batch costing
• Shipping, courier and delivery tracking
• Warehouse, stock movements and service jobs
• HR side: staff, leave and timesheets
• Accounting, fleet-tracking and marketplace integrations
• Parametric setup: fields, processes and permissions defined on screen

The result

Data is entered once and cost is visible before the job ends. When a new process or field is needed, a parameter changes instead of the code — so no one waits on development for every request.