Short answer

Before building a website, assess five connections: forms to CRM, bookings to calendars, payments to order fulfilment, analytics to meaningful actions, and newsletters to subscription and unsubscribe processes. Plan every dependency you need, but implement only those with a defined process, a responsible person and an acceptance criterion.

The process first, the tool second

An integration makes sense when it removes a specific problem: enquiries get lost in the inbox, appointments are copied manually, or a paid service waits for someone to notice the bank transfer. “It might be useful one day” is not a sufficient project scope. Every connection also means maintenance, data access and a response to failures.

My recommendation: for each feature, complete the sentence “when the customer does X, the system passes Y to Z, and a named person is responsible for what happens next”. If you cannot finish it, ask for the process to be designed first. This guide helps you choose what to commission; it is not a supplier ranking or a promise of increased sales.

1. Forms and CRM: when an enquiry needs follow-up

Consider connecting a form to CRM when several people handle enquiries or you need to keep track of follow-up contacts. The CRM should receive the information needed to reply and the appropriate handling stage. HubSpot’s documentation shows that form fields save information to specified CRM properties. This mapping needs planning; do not assume every message automatically becomes a correctly described contact.

Separate the form, notification and database record in the quote. Agree what happens when the same email address submits again and when the CRM is unavailable. The acceptance test should show where the content arrived, who received the task and whether a transfer failure can be detected. A green message on the website does not prove that an employee has seen the enquiry.

Postpone expansion if one person efficiently handles a small number of messages and does not need a shared history. A thoroughly tested form and an organised inbox may be enough initially. Do not add automatic lead scoring without rules the team actually understands.

2. Bookings and calendars: when customers choose an available appointment

Online booking suits consultations, appointments and other services with a predictable duration. Before implementation, agree the meeting length, breaks, time zone, cancellation rules and the person providing the service. Calendly distinguishes calendars checked for conflicts from the calendar receiving new bookings. A visible calendar widget alone does not confirm these settings are correct.

Ask for tests of an unavailable appointment, rescheduling, cancellation and the confirmation message. If you serve several locations or specialists, add allocation rules. Also check what customers see if the calendar connection breaks. Convenient booking cannot depend on the assumption that nobody will ever change a password or permissions.

Do not implement it just in case if every job needs an individual assessment before its duration can be agreed. A qualifying form may be more honest than offering appointments that later have to be cancelled. You can allow for future booking functionality without buying the entire system immediately.

3. Payments and fulfilment: when customers can genuinely buy on the website

Online payment makes sense for a defined product, package, deposit or another clearly described commitment. First decide what the customer pays for, when confirmation arrives and what starts fulfilment. Integrating a payment provider does not replace refund rules, sales documents or the organisation of customer service.

In Stripe’s documentation, webhooks support responses to asynchronous events, such as a bank confirming payment. Therefore, do not release a service solely because the customer returns to a “thank you” page. The provider should explain how the system determines payment status, verifies notifications and avoids performing the same operation more than once.

Include successful, interrupted and failed payments, plus repeated notifications, in the acceptance scenarios. Test them in the payment provider’s test environment, without accidentally charging real customers. Postpone payments if every order first requires an individual quote and agreement on terms anyway.

4. Analytics and customer actions: when you know what to measure

Plan analytics before implementation because event names and triggers follow the customer journey. Google lists generate_lead for a form submission or request for information, and purchase for a completed purchase. Clicking a contact button and receiving an enquiry are not the same outcome.

Agree a minimal event list, how its accuracy will be confirmed and who will use the report. Include the privacy and consent requirements of the chosen solution. Do not send enquiry content or email addresses as convenient measurement labels. Installing a tool alone is not acceptance of an analytics implementation.

Postpone unnecessary complexity: several trackers and dozens of events without a business decision behind them only make verification harder. First define what counts as a properly handled enquiry, then choose an extensive dashboard if needed. Measurement does not guarantee complete data or better results.

5. Newsletters and consent: when you have a reason for regular contact

A newsletter subscription needs a specific promise: what content you intend to send and to whom. Do not treat a contact form as automatic marketing consent. Agree the required legal information, how subscriptions are documented and how opt-outs are handled, according to your process and legal requirements.

Mailchimp describes double opt-in as an additional email-address confirmation step. It is a subscription-process option, not a universal answer to every legal obligation. The acceptance test should cover subscribing, any confirmation, subscribing again with an existing address and unsubscribing. Also check that the contact joins the correct list rather than an unintended audience group.

Postpone the newsletter if nobody is responsible for content and there is no sending plan. A form alone does not build a relationship. It is better to leave room for connecting a tool later than collect addresses without a clearly defined purpose.

A decision matrix for your conversation with the provider

This table is my scope recommendation, not a mandatory package of five implementations. On a phone, it can be scrolled horizontally. For each selected item, add the account owner and the person accepting the test.

ConnectionCommission it now when…Acceptance criterion
Form → CRMYou need shared history and enquiry allocationCorrect fields, a responsible person and detectable saving failures
Booking → calendarThe customer can choose a genuinely available appointmentConflicts, changes and cancellations follow the agreed rules
Payment → fulfilmentThe purchase scope and terms are defined before paymentConfirmed status and no duplicate fulfilment
Website → analyticsYou have defined actions and data-informed decisionsEvents reflect actions without unnecessary personal data
Subscription → newsletterYou have content, a subscription purpose and someone responsibleThe correct list, confirmation as configured and effective unsubscribe

How to compare quotes without buying “everything”

Ask for implementation, supplier fees and ongoing maintenance to be separated. Check whether the feature you need is available in the chosen tool’s plan. Do not compare integration counts alone: an embedded calendar link and full synchronisation for several employees are different scopes of work.

Record the direction of data flow, required fields, failure handling, tests and access handover in the order. A business account should have an agreed owner, and access keys must not appear in public website code. Specify who checks operation after an update or a supplier-plan change.

Divide the scope into “essential at launch”, “prepare for a future connection” and “revisit after collecting data”. Preparation does not mean installing unused add-ons. In the website brief, describe current tools and the manual tasks you want to reduce. This makes it easier to price specific work without invented savings or an unnecessary subscription.

Sources and limits of the recommendations

The described features were checked in the documentation for HubSpot forms and CRM properties, Calendly calendar connections, Stripe notifications, recommended GA4 events and Mailchimp double opt-in. These are examples of mechanisms, not a recommendation to buy all these services. The selection order, matrix and acceptance criteria are the author’s recommendations. This guide contains no fictional implementation results or legal advice.

Agree the integrations you need before requesting a website quote

In the brief, list your current tools, the website’s purpose and tasks performed manually. This is a starting point for agreeing scope, not an automatic quote or a statement of savings.

Open the website brief (in Polish) ↗