One record for every customer and job
All 41 files now sit in one database, in Aire Tech’s own account.
Case study · HVAC · Philippines
Aire Tech installs and services air conditioning in Cabanatuan, Philippines. We moved six years of records out of spreadsheets and built the tools the team now works in.
Excel files moved into one system.
jobs imported, with 2,961 customers.
technician names cleaned to the real crew.
from first build day to a working version.
[01] The starting point
Every job since 2020 was typed into Excel. Nobody could see who was due for a cleaning or who still owed money.
[02] What we built
All 41 files now sit in one database, in Aire Tech’s own account.
Sales, service and quotes go in one form with pick lists, so new records stay clean.
A home screen shows today’s jobs, money received and money owed. A sales report is texted to the owner each morning.
The system drafts a text when a customer is due. A person approves each batch, and replies land in a shared inbox.
A website, order emails and a small shop all feed the same records.
Commercial jobs and tenders are tracked on one board, each with a draft proposal.
[03] The hard problems
The import came to 7,656 records on a plan that allows 1,000. We moved the whole app to Postgres that same night.
In the Philippines, a text sent under a business name cannot receive a reply. So two-way texts go through an Android phone with a local SIM, and replies land in the shared inbox.
Some customers were in the old sheets more than once. Every texting rule now follows the phone number, so nobody gets a wrong or repeated text.
[04] Results so far
[05] Tech used
Next.js, Postgres on Supabase, Vercel, Python, n8n, Slack, Semaphore, SMS Gateway for Android, Resend, Cloudflare.
Your records
Show us the messy version. We will tell you what we would clean first and what we would build on it.