A company website with integrations — CRM, calendar, forms and automation
Most companies do not need a site “integrated with everything” on day one. They need a site that explains the offer and leads a person to the next step. Sometimes that step is an email. Sometimes it is a CRM record, a calendar slot, or a message that goes out after the form is sent.
Below is how I separate those cases. The decision belongs in the quote, not on a shopping list of tools.
Contents
- What integrations on a company website are
- Email form vs CRM form
- Calendars and bookings
- Newsletter and marketing automation
- CRM and the sales pipeline
- Webhooks and API
- When to integrate immediately
- When to leave it for later
- How integrations change the quote
- Scenarios for service firms and B2B
What integrations on a company website are
An integration is a connection that stops the visit from ending in one place only. A form, a booking button or a newsletter signup starts something in a tool the company already uses: an inbox, a CRM, a calendar, a mailing system.
That is not the same as embedding a widget because it looks modern. A widget is an integration only when it is clear where the data goes, who receives it, and what happens if the other side does not answer.
A sound first version explains the offer, collects the right enquiry and hands it to someone who can reply. The integration shortens the path between “send” and that person. It does not replace the offer or the decision about who owns the conversation.
If you are still shaping scope, write that next step into a website brief. The path from goal to launch is in how to build a website step by step.
Email form vs CRM form
An email form is enough when:
- one person or a small shared inbox handles enquiries,
- there are few enough each week that nothing disappears,
- there is no CRM yet, or nobody actually uses one,
- the first contact becomes a conversation anyway, not an automatic status.
Ask only for what the reply needs: name, email, an optional phone number and a short note. Say what happens next. An on-page confirmation and a copy to the sender answer most “did it arrive?” worries.
A CRM form makes sense when the lead needs an owner, a source and a status before anyone replies. A typical record is who wrote, which service, where they came from (site, campaign, referral) and who should make first contact. Without those fields the CRM is a second inbox that costs more to keep.
The work is different. With email you test delivery. With a CRM you test field mapping, duplicates, a failure on the other side, and who still sees the enquiry if the connection drops. A backup email still earns its place.
Calendars and bookings
A calendar on the site pays off when the product is a time slot: a consultation, an appointment, a pickup, a short qualification call. The client picks an hour and the team does not retype it from an email.
Leave the calendar for later when:
- a salesperson still sets the time after a short call, because every meeting has a different scope,
- staff calendars are not up to date,
- there are no rules: duration, buffer, who hosts it, which time zone.
A plugin does not solve cancellations, reminders or bookings outside working hours. Those are business rules. Write them down before the “Book” button exists.
Newsletter and marketing automation
A newsletter signup is an integration only when the list, the consent and the content have an owner. A “leave your email” box with no explanation of what the person will receive, and no way to unsubscribe, collects addresses you should not use.
A sound start is one field, a clear consent and one sending tool. Automation — a sequence after signup, a mail after a download, a nudge after a quiet lead — comes later, when the first useful message is known. An empty “five educational emails” sequence with no offer and no one to maintain it is not a sales process.
If the list lives in another system, the quote includes consent, confirmation and which data is not passed on.
CRM and the sales pipeline
A CRM helps when sales has stages, not a single “thanks for your message” email. A pipeline answers: new enquiry, call booked, proposal sent, won, lost, no decision. The site can create the first opportunity. It should not pretend to be the whole CRM.
A service firm usually needs a few fields: service, size of the job, timing, source, contact person. The team fills in the rest after the call. Trying to collect a full brief in the public form cuts submissions and still does not replace the conversation.
If the CRM already works, the site should match it: the same service names, the same statuses, the same lead owner. If the CRM is “to be chosen someday”, do not build an integration for a tool nobody has picked.
Webhooks and API
A webhook is a message that something happened: form sent, slot booked, consent stored. An API is how the site, or a service in between, asks another system for data or asks it to create a record.
On a company website the usual need is one direction: from the site into the tool. Two-way sync — statuses coming back to the site, a service catalogue pulled from the CRM, customer accounts — is a different scope, closer to an application than to a brochure site.
What matters is not only whether the first message arrived. It is what happens on a retry, on an error, and when fields change on the other side. The technical side of that connection is in system integration via API.
When to integrate immediately
Build it in the first version when the process already breaks without it:
- several people handle enquiries and nobody knows who replied,
- time slots are the product and a manual calendar causes mistakes,
- campaign leads need a source, or you cannot tell what works,
- the CRM is in place and the team really works in it,
- a specific, already written message must go out after the form — not “automation in general”.
Then the site is part of sales, not a brochure beside sales. The integration belongs in the launch scope, including a test of what the client sees and what the team sees when delivery fails.
When to leave it for later
Leave it for a later stage when:
- the tool is not chosen or the account does not exist,
- the team will keep working from the inbox and will not move to a CRM just because the site is connected,
- volume is low and one person can reply the same day,
- “integration” means three systems nobody uses the same way,
- the current site may disappear or the offer may change, and a new site or a modernisation is still an open decision.
Postponing is not quitting. The first version can deliver the lead by email and still have a clear goal in the copy and in analytics. A CRM or calendar slot can be added when the process is real. What fails more often is three connections of which one survives launch, because the others had no owner.
How integrations change the quote
The contact form itself is part of the site. An integration is extra because the work sits outside the layout:
- account access and permissions, not a password on a slip of paper,
- the field list and its match in the CRM or calendar,
- consent, if data goes to a newsletter or another party,
- failure behaviour: backup email, message to the user, who gets the alert,
- a test on a trial account before a real lead is sent,
- who maintains the connection when the vendor changes the API.
“We will connect HubSpot” without field names and without a working account cannot be quoted like another page. It can be estimated, or written as a stage after the site launches. Those answers belong in the brief before you compare proposals.
There is no price list here. Two projects with the same number of pages can differ exactly in what should happen after “Send”.
Scenarios for service firms and B2B
A practice, a consultant, a B2B freelancer. A few enquiries a week, one person replies. A short email form and a phone number are enough. A CRM arrives when a second person appears or proposals start getting lost.
A service firm with sales and delivery. The form creates a CRM opportunity: service, city or segment, source. The salesperson gets a task. The calendar can wait if the first meeting is still chosen by hand.
A studio, clinic or timed service. Booking, or at least choosing the visit type, belongs in the first version. An offer with no free slot pushes the client into an email the team will retype into a calendar anyway.
B2B with a longer cycle. The site does not close the sale. It should qualify the topic enough that the first call does not start from zero: industry, scale, what the enquiry is about. The pipeline lives in the CRM. The site only opens the record.
A firm that wants a newsletter but has no content yet. Leave the automation. Start with the offer and the enquiry form. Add the list when there is a concrete piece to send and a person who will send the second one, not only store the first address.
You can look at how such a site is structured — offer, trust, contact — as industry concepts in the showroom. Those are directions, not a finished project for your company.
If you want the first version to collect enquiries without promising integrations that do not exist yet, see website development.