B2B lead generation: one system from first click to CRM

For most B2B companies the first problem is leakage, not volume. Inquiries arrive through the website, email, events and the phone, and some are never answered or never traced back to where they came from. Before you spend more on ads or an agency, connect what you already have: one capture point per channel, one CRM record per inquiry, one owner and one follow-up rule. Build custom parts only where your routing or qualification logic does not fit a standard tool.

Should you buy a platform, connect your tools or build?

If your sales process is standard and you have no CRM yet, an all-in-one marketing and CRM platform is the fastest start. If you already run a CRM, a website and an email tool, connecting them properly usually beats replacing them. A custom build pays off when routing, scoring or data rules are specific to your business, or when several systems must agree on one customer record.

	All-in-one platform	Connect existing tools	Custom lead system
Best when	No CRM yet, standard B2B funnel	CRM, website and email tool already in use	Routing or scoring rules no tool supports
Time to first result	Fastest	Fast, if the APIs are decent	Longest
Fit to your process	You adapt to the tool	Good, within each tool’s limits	Built around your process
Running cost pattern	Per-seat or per-contact subscription	Existing subscriptions plus upkeep of the connections	Hosting and maintenance, no per-contact fees
Main risk	Paying for modules nobody uses	Connections that fail silently without monitoring	Scope creep without a clear first version

How is the system put together?

A form submission sends the contact details, the answers and the tracking data (UTM parameters, referrer, landing page) to the CRM through its API or a webhook. The CRM creates or updates the contact, opens a deal in the right pipeline and assigns an owner by rule. The prospect gets a confirmation within a minute. The owner gets a task with a deadline, and if no call is logged by then, the sales manager is notified.

The chatbot follows the same path, with its transcript stored on the contact. Every connection is logged and retried on failure, so a broken webhook shows up as an alert, not as a missing lead three weeks later.

We have built a more demanding version of this pipeline for a SaaS client: a daily process that finds prospects, verifies contact data, scores each lead, runs a personal email sequence that stops on any reply and pushes positive replies into the client’s CRM. The startup discovery and outreach platform describes the engineering behind it.

Example: an industrial supplier with three language regions

Illustrative scenario, not a client project.

A 30-person company in the canton of Aargau sells and services industrial cooling equipment across Switzerland. Inquiries come through a contact form, a service request form, trade fairs and phone calls. Today they all go to one info@ address, and whoever reads them first forwards them.

After the project, both forms feed the CRM. Service requests go to the service desk with the machine type attached; sales inquiries become deals. French-language inquiries go to the salesperson who covers Romandy, Italian ones to the colleague for Ticino, the rest by postcode. Trade-fair contacts are scanned into the same CRM with the event as source. After a few weeks the sales manager can see which channel produces qualified deals; after a quarter, which one produces orders.

What do consent rules mean for lead generation?

Answering an inquiry is not advertising, so you can always reply to the person who contacted you. Newsletters and promotional sequences are different. Under the Swiss Unfair Competition Act (UCA Art. 3 para. 1 let. o), mass advertising by email or SMS needs prior consent, a correct sender identity and a free, easy opt-out. The rule applies to messages sent to companies as well as to consumers. EU countries set comparable rules under the ePrivacy Directive.

In practice: a separate, unticked consent checkbox, the timestamp and wording stored in the CRM, and opt-outs honored in every tool that sends. The FDPIC’s guidance on advertising explains the existing-customer exception. The revised Federal Act on Data Protection (FADP), in force since 1 September 2023, requires your privacy notice to say what you collect and why, and to name the countries involved if your CRM or email tool stores data outside Switzerland; the GDPR sets similar transparency duties for people in the EU.

How does a project run?

1. Discovery. We list every lead source, the current CRM fields and owners, and where inquiries get lost. You get a flow diagram and a prioritized list.
2. Architecture. Data model, routing rules, consent handling, and a decision on which tool does what and what, if anything, gets built.
3. Build. Forms, CRM configuration, integrations, sequences and chatbot on a staging setup, tested with dummy leads.
4. Launch. Channel by channel, with monitoring on every connection.
5. Iterate. After the first weeks we review the source-to-deal report with sales and adjust scoring and routing.

After discovery you receive a fixed-price or phased proposal. The full sequence is described on how we work, and the next step after a qualified lead is covered in sales automation.