Notes from real projects: how I build and check systems.
One application, several lenders: why a deal per lender, not per client
Three decisions from the CRM of a property-purchase service: a separate deal for every lender, validation at the form and tags as the single language between the CRM and the emails.
When the buyer is not the user: two purchase paths in one funnel
How I built the sales path in GoHighLevel for a tech-support service for older people that is often bought by their adult children: a separate gift flow, separate order forms and reminders before the rebill.
How to check a data migration when mistakes are expensive
Six rules from moving a psychiatric practice's support desk: 14,299 tickets, no notifications to patients and an independent count instead of the importer's own report.
Testing an AI receptionist: check the whole path, not the reply
How I tested a clinic's AI receptionist in GoHighLevel: three scenarios end to end and the five things I checked in each, from the AI answer to the reminders.