From a single HTML page to a site that feeds the CRM

About this project

Global Technologists were winning work that their website actively undersold. The entire site was one basic HTML page, which is a difficult thing to send a prospective client to.

We rebuilt it properly in WordPress with a clean, professional design, gave them somewhere to show their work and their client feedback, and connected the contact form to HubSpot so an enquiry becomes a tracked record in the CRM instead of an email somebody has to remember to follow up. The contact page is the one doing that job, and the site itself is live if you want to see what replaced the single HTML file.

That last part is the bit worth pointing at. A contact form that goes to an inbox is where most small-business enquiries quietly get lost. Connecting it to the system that tracks the sale costs very little at build time and is the difference between a lead and a missed one.

Why the CRM join is worth doing at build time

An enquiry that arrives as an email depends entirely on a person to survive. It gets read on a phone, half-actioned, and then it is below the fold. Nobody decided to ignore it. There was simply nothing in the process that insisted on an answer.

Wiring the form into a CRM changes the default. The enquiry becomes a record with an owner and a state, so "did anyone come back to them?" is a question with an answer rather than a shrug. The same submission can carry which page it came from, so over a few months you can see which parts of the site are actually producing work.

None of that is difficult. It is a mapping between the fields on the form and the properties on the contact record, a check that a repeat enquiry updates the existing contact rather than creating a duplicate, and somewhere sensible for the failures to go if the CRM is ever unreachable. An hour or two of thought at build time.

The reason to do it then rather than later is that retrofitting means going back into a site somebody else has since edited, reconstructing what the form does now, and migrating whatever history exists in an inbox. That is the expensive version of the same job. This is the general shape of most of our system integration work: the join between two tools is cheap while one of them is being built and awkward afterwards.

Where this sits in what we do

This is a website rather than a bespoke software build, and we say so. But if your business is running quotes, jobs or scheduling on spreadsheets, that is a different conversation, and it is the one where our software work pays for itself. Our guide to spotting when a spreadsheet has become a liability is the place to start if that sounds familiar.