Updated 2026-08-30. Written by Christopher Gilliland, founder of ZynVoss LLC — Fort Pierce, FL.
Why integrations fail
Duplicate contacts, missing webhooks, and “who owns the truth?” fights. Decide a system of record before writing code.
Integration patterns
- Form → CRM lead create
- Call transcript → CRM note
- Won deal → project tool
- Invoice paid → unlock portal access
We wire these often under systems integration.
FAQ
Zapier or custom?
Zapier for simple glue. Custom when volume, security, or complex rules matter.
Next steps
Your CRM is not the business unless you decide it is
Most small Florida shops did not “implement Salesforce.” They have a form on the website, a shared Gmail, a cell phone, and a spreadsheet named leads-final. Then someone buys HubSpot or Jobber and now there are three copies of Mrs. Alvarez. Integrations fail because nobody named the system of record.
Pick one. Website forms create or update that record. Calls attach notes to it. Won work opens a job. Paid invoices unlock a portal. Everything else is a report. ZynVoss LLC will not wire five two-way syncs that fight all night.
Patterns that actually hold
- Public form → CRM lead with the landing page and the campaign, or “direct.”
- Phone transcript → a note, not a second contact.
- Won deal → a job or project with a stable ID you can find in both systems.
- Invoice paid (Stripe webhook) → entitlement in the app. Do not poll a human to “remember to turn them on.”
Zapier is glue for low volume. Custom code when the rule is “if county is St. Lucie and job type is X, assign Y, else wait for a human.” Also custom when you cannot put API keys in a third-party toaster, or when you will hate the per-task bill at 10,000 events.
Duplicates and the merge rule
Match on phone first, email second, name last. Write the merge rule down. If two staff can both “own” a lead, the CRM will lie. Permissions: sales should not delete accounting’s invoices because a zap ran backwards.
We do this under systems integration. Related: API basics. Fort Pierce number: (772) 971-4448.
A week-one wiring plan
Day 1: name the system of record. Day 2: export a CSV and look at duplicates with your own eyes. Day 3: map five fields, not fifty. Day 4: a test form that creates one lead you can find. Day 5: turn off the second inbox or you will ignore the CRM. ZynVoss LLC will not start custom code until those five days exist, even if they happen in one afternoon.
Phone numbers in Florida get written ten ways. Normalize to digits before you match. If two leads share a number, merge with a rule you wrote down, not a vibe. Permissions: sales does not delete invoices because a zap ran backwards. Logs: keep the payload for 30 days so we can see what the vendor actually sent.
When Zapier’s per-task bill shows up, that is the moment to talk custom. Not because custom is fashionable. Because you are paying a third party to copy the same five fields a million times. See API basics.