Guide

Do lead qualification yourself or have it done?

Much of what's involved in lead qualification can be built in-house — the question is whether it pays off. When internal effort makes sense, where the limit is, and which route is the most expensive.

Quote upon request2 to 4 weeksStatus 2026
In short

Building lead qualification yourself makes sense when the project stays small, someone in your business has time for it, and no one depends on it running by a specific date. Once other systems need to be involved or someone is liable if it fails, external implementation is usually cheaper — the most expensive route is the half-finished one.

01 — In-house effort

Build yourself or have it built?

  • Building yourself makes sense when someone in the business has the time and interest, the project stays small, and no one depends on it being live by a specific date.
  • Ready-made platforms get you to a first result quickly, but hit limits where custom processes, custom data, or integrations with existing systems come into play.
  • Having it done makes sense once lead qualification needs to communicate with other systems, once someone is liable if it doesn't work, or once internal effort becomes more expensive than external implementation.
  • The most expensive path is the halfway one: built in-house for months on the side, then abandoned and rebuilt externally. If you decide on in-house effort, set a time budget and an abort point.
  • Hybrid approach: concept and setup external, maintenance internal. For lead qualification, this is often the most economical route — provided the handover is documented.

02 — Requirements

What you need for automatic lead qualification

  • A clearly defined trigger. Not “we should do something with AI,” but a process that demonstrably costs time or orders today.
  • Existing content or data. Lead qualification works with what's already there. The more complete the starting point, the shorter the setup.
  • Access to the systems involved. Whoever manages the credentials needs to be involved from the start — this is, in our experience, the most common cause of delays.
  • One decision-making contact person. One, not three.
  • Willingness to refine after launch. The first weeks in real operation show what was missing in the concept. That's normal and accounted for.

03 — Calculation

How to calculate it

Four numbers are enough: How often does the process occur? How long does it take? What does an hour cost internally? And what does the solution cost — one-time plus operation over three years?

An example: A process that occurs twice a week and takes 40 minutes each time ties up around 69 hours per year. At an internal hourly rate of 45 euros, that's roughly 3,100 euros per year locked in there. If a solution reduces this effort by two-thirds, it often pays for itself — depending on the actual quote — within one to two years. We'll give you the exact figure for your case after the initial meeting.

This calculation is deliberately conservative: it only accounts for the time saved, not the errors avoided or the orders that come through due to faster response. In practice, the benefit is usually higher — but you shouldn't count on it before you've measured it.

04 — Questions

Frequently asked questions

Won't we filter out good customers with this?

That's why nothing is automatically rejected, only sorted. Every inquiry remains visible, it's just not on the same pile anymore.

How long does setting up the scoring logic take?

One to two weeks for the criteria and the form, then a test run on your recent inquiries before anything goes live — misclassifications show up right there.

Don't more form fields scare people off?

Yes — that's why it's not about more fields, but different ones. Two well-crafted questions bring more clarity than six required fields and cost fewer conversions. Which ones those are, we test on your real inquiries.

Does this need integration with our CRM?

Useful, but not mandatory. Without CRM integration, scored inquiries land structured in your inbox; with integration, a record with scoring is created directly in the system.

What if our criteria change over time?

The scoring rules are in a table you can adjust yourself without changing any code. A new criterion is one line, not a project.

Will we lose inquiries from smaller customers because of this?

No, only the order of processing is sorted, not acceptance. Every inquiry remains visible and answerable — the sorting only decides which one is handled first.

What's a realistic scoring approach?

Points for hard criteria you can actually verify: region within your service area, scope within your service range, timeframe feasible. Everything else is guesswork and leads to nobody trusting the scoring.

05 — Decision

How to move forward

The most affordable next step is a conversation, not a quote. Twenty minutes is usually enough to clarify whether a project makes sense, what scope it involves, and whether we're the right fit.

If we're not, we'll say so. An honest no costs less than a project you abandon after three months — for both sides.

Next step

Let's talk briefly about whether this makes sense for you.

A twenty-minute conversation is usually enough to clarify whether a project makes sense. If not, we'll say so — that's cheaper for both sides than an offer nobody needs.