Connecting a site to a CRM: the minimal plane

A CRM integration is often sold as "we will connect a widget". The widget sends the lead nowhere if the fields did not match, a duplicate was not recognised, and the error looked like a green tick to the person. The minimal plane is small, but it has to be provable: a lead from the site is visible in the CRM to the right person.

What the minimum includes

• Fields required in the CRM exist on the form. The rest is not invented as empty values.
• The source and the page they came from. Otherwise there is nothing to compare the ads with.
• A duplicate rule: the same email or the same phone updates the card instead of spawning a fifth one.
• An owner and a notification. A card with no person is an archive, not work.
• A delivery failure is visible. A retry or a mail saying "it did not leave" is better than a lost lead.

The integration key should be able to create a lead and should not have to read the whole database. It does not belong in public code. When the CRM changes fields, the plane needs one test lead, not a wait for a live customer.

Lexora assembles this minimum and stops until it is stable. Statuses, invoices and stock are the next queue, once leads are no longer getting lost.