Built hot.Made to last.

QUALITECH Inspections is a French inspection company. Every report an inspector sends in has to be matched to the right client, locked with a password, emailed out and filed. By hand, that is slow and easy to get wrong.

We built the flow in Make.com. Inspector emails with PDF reports are routed automatically. Each report's client code is looked up in a Google Sheets registry, the PDF is password-protected through PDF.co, sent to the client and archived in Google Drive. A second phase colors each job in Google Calendar as its report moves from pending to sent. Then a production issue surfaced: emails with several reports attached were only delivering one. Two things caused it. A calendar step was stopping the loop over attachments, and Drive uploads were timing out. We moved the calendar step out of the loop, added error handling to the fragile steps and rebuilt the send, so every protected PDF now goes out together in one email.

✓Reports reach clients password-protected and archived automatically, with every attachment in a single email.

Cook In Rio runs cooking classes across 33 cities in Latin America, booked through Bókun. Every booking email had to turn into the right calendar event for the right chef and the right lead in Kommo CRM. The automation doing that ran on Relay.app, and the client wanted it rebuilt on Make.com, with the old system kept running as a safety net during the switch.

The client's own import had seventeen modules that arrived empty, and the product-to-calendar lookup table didn't exist yet, so it had to be rebuilt from scratch across 99 products before anything else could work. Two bugs were already live in the Relay system, quietly causing problems. Updated bookings renamed the calendar event but never moved its time, so a guest changing their date could leave a chef scheduled on the wrong day. And WhatsApp links built from the phone number field were stripping the leading plus sign, so some links didn't open at all. The rebuild runs on Gmail's own search, filtering for new, updated and cancelled booking subjects, so forwarded test emails work the same way as live ones. Gemini extracts the structured fields from each email, and the city, tour code and tour type all moved out of the AI prompt into the lookup table, so the client can update his own product list without editing prompt text. Four safety guards were added at the points most likely to fail silently: a booking with no matching product or no tour date now stops before it can miscalendar, rather than emailing an empty match into fifty calendars at once. One incident during rollout, a product missing from the table, showed exactly why that guard mattered. Provenance tags were added throughout, since both systems ran side by side during the transition: every calendar event and Kommo lead created by the new build carries a marker showing which system made it.

✓Twenty modules live, proven end to end against real bookings across new, updated and cancelled paths. The client now maintains his own product-to-city mapping in one table instead of two places, and the timezone handling that Relay got wrong is fixed at the source.

The owner runs two lodges and needed one place to manage both, including the lease documents that go with each property.

We built a property management app on Lovable with a Supabase backend, using row level security so each user sees only the data they should. The app generates lease PDFs from the records in the system. Every change was verified in a clean room: temporary test accounts and data, created for the test and fully deleted afterwards. Generated PDFs were checked by extracting their text, to confirm only the intended changes had landed. Bugs we found during paid feature work were fixed at no extra charge. The client's Lovable credits were limited, so changes were batched to get the most out of every pass.

✓Two lodges run from one dashboard, and a client who has come back for project after project.