Core system
CRM & integrations
Making sure every enquiry lands where your team already works.
What it is
The plumbing between the website and everything else you run — CRM, spreadsheets, email, messaging. Enquiries stop living in an inbox and start appearing in the system your sales team already opens every morning, with retries when something upstream fails.
How we build it
What makes ours work
Store first, sync second — an enquiry is never lost
The cardinal sin of website-to-CRM integration is posting the enquiry straight to the CRM and hoping. CRMs go down, tokens expire, fields change. Every lead we capture is written to the platform’s own database first, then synced onwards — so an upstream failure delays a lead’s appearance in the CRM but can never lose it. The record of what happened, and when, lives on your side.
Field mapping is agreed like a contract
Integrations decay when nobody can say what maps to what. Before we write sync code, we document the mapping — this form field to this CRM field, this course selection to this deal property, this consent checkbox to this compliance flag — and review it with whoever owns the CRM. The PITC build syncs registrations, brochure downloads and contact enquiries to Zoho with distinct mappings per form, because they mean different things to the sales team.
Sync status is visible, and retry is one click
When a sync fails silently, trust in the whole system dies. Our integrations surface their own health: an admin view shows each lead’s sync status, failures are flagged rather than swallowed, and re-sending is one click rather than a support ticket. PITC’s lead console shows exactly which records reached Zoho and lets the team retry any that did not — self-healing on a schedule, human-fixable on demand.
Proof
Where we've built this
Every build below contains this system. Open any one and click through it — the fastest way to judge whether we can do what you need.
Questions
Asked about crm & integrations
The questions that come up when we scope this system. Anything else, ask us directly.
Which CRMs do you integrate with?
Zoho is the one we run in production today, and the same architecture applies to HubSpot, Salesforce, Pipedrive and most systems with an API. Because leads are stored on the platform first and synced second, swapping or adding a CRM later is a change to the sync layer, not a rebuild of the capture. If your “CRM” is currently a spreadsheet, we sync to Google Sheets with the same reliability rules.
What happens if the CRM is down when someone enquires?
Nothing is lost. The enquiry is already stored on the platform; the sync retries automatically on a schedule, and the admin console shows it as pending rather than silently missing. Your team can also see and work the lead directly from the platform in the meantime — the CRM being down never means the lead is invisible.
Can we know which campaign or source each lead came from?
Yes — attribution is captured at the moment of enquiry and carried through the sync. UTM parameters, landing page and click identifiers are stored with the lead and mapped into CRM fields, so “which campaign produced this customer?” is answerable in the system your team already uses. This is also the foundation for feeding real outcomes back into ad platforms.
Can alerts go to WhatsApp instead of email?
Yes. Email alerts are standard, and for teams that live in WhatsApp we can deliver new-enquiry notifications there too, with enough of the lead’s details to act on immediately. The alert is a pointer to the stored record, not the record itself — so however it arrives, the lead is already safe in the system.
Need this in your project?
Tell us what you are building and we will show you the closest thing we have already made — then quote the real version.
Tell us what you need built
We'll put together a free working prototype of your project so you can click through it before paying anything.