Skip to content

Lighthouse offer · Switzerland

Build a B2B pipeline system your team actually owns.

In 90 days, devlo works with your team to design a focused prospecting system for the Swiss market, test it within an agreed scope, and transfer the data, rules and procedures needed to operate it.

For complex-sale B2B companies with an internal sales owner, a CRM, and an offer that is already being sold.

Field proof · German-speaking Switzerland

Three systems tested in the field, across three demanding B2B contexts

From Swiss solar to DACH HR tech and cybersecurity, these public cases show how devlo turns targeting, messaging and data into measurable operations.

und du AG

Solar installation on a Swiss industrial site supported by und du AG

01

und du AG logo

1,025

leads created

Solar · Switzerland

Building, owner and contact data structured for three ICPs, with German and English sequences, Salesforce tracking and handover to the internal team.

12 MQLs · 4 SQLs · 3 Converted statuses

See the transferred system

CareerLunch

02

CareerLunch logo

54

qualified meetings

HR tech · DACH

A focused German-language campaign across DACH, systematically excluding companies that had already been contacted.

516 prospects · 19% reply rate · 10% interest

See the CareerLunch case

Saporo

03

Saporo logo

4,500

companies prequalified

Cybersecurity · DACH and international

More than ten campaigns to identify and prequalify cybersecurity leaders across several markets, including DACH.

10+ campaigns · 41% reply rate · 4% interest

See the Saporo case

A demanding pilot, not a one-off campaign

Work starts only when the team can make decisions, provide the agreed access, and take over the system at the end.

01

Defined offer and market

You already sell a high-value B2B offer and can name the accounts that fit — and those that do not.

02

Internal owner

One person on the client side validates targeting, messages and acceptance criteria, then takes over operations.

03

Auditable data

Sources, transformations, decisions and exclusions remain visible. The system does not rely on an opaque list.

Acceptance criteria

Two measurable decisions before discussing scale

The pilot advances through evidence. Each phase can be accepted, corrected or stopped against criteria agreed at launch.

01 · Day 0–30

Prove the system can be operated

We lock the segment, data, qualification rules, message proposition and CRM workflow within a limited scope.

  • Documented ICP and exclusions
  • Traceable data sources and rules
  • Testable review and launch workflow
  • Day-30 criteria signed at launch

02 · Day 31–90

Prove the team can take it over

We operate, correct and document the system through the final quality, economics and handover review.

  • Decision and change log
  • Dashboard for the agreed signals
  • Operating and control procedures
  • Day-90 review and handover to the internal owner

At Day 90, the assets stay with you

The pilot is not successful if it makes devlo indispensable. It succeeds when your team receives a system it can understand, control and operate.

  • Working data and lists
  • ICP definitions and qualification rules
  • Messages, variants and decision log
  • Agreed CRM workflows and dashboards
  • Procedures, controls and handover documentation

What this offer commits to — and what it does not

We commit to a scope, a method and verifiable deliverables. Commercial outcomes also depend on the market, offer, deliverability and your team’s follow-up.

01

Verifiable commitment

A system defined, tested and transferred against the agreed Day-30 and Day-90 criteria.

02

No meeting guarantee

We do not guarantee a volume of meetings, pipeline or revenue.

03

Controlled change

A new market, language or segment changes the scope and must be decided explicitly.

Five answers must be clear before launch

If one is missing, the consultation first qualifies the problem — it does not force a pilot.

  1. 01Which offer is already being sold, and to whom?
  2. 02Which Swiss segment do we test first?
  3. 03Who decides, and who will own the system?
  4. 04Which access and data can be provided?
  5. 05What makes Day 30 and Day 90 acceptable?

Frequently asked questions

Is this an appointment-setting service?

No. The primary deliverable is a documented, transferable pipeline system. Sales conversations are a validation signal, not a volume promise.

Can you launch several countries and languages?

Yes, we can deploy the pilot across several countries and languages, including French, German and English, when the execution languages, language operator and QA owner are confirmed for each engagement during scoping. The agreed scope defines the countries, languages and segments covered.

Which tools do you use?

The stack depends on your CRM, access and constraints. Tools support the workflow; they are not the deliverable.

What does it cost?

The pilot costs CHF 36,000 for 90 days. The price covers the qualified base scope; any extension requires an explicit scope change.

Who owns the data and procedures?

The client retains the agreed assets: working data, rules, messages, workflows, dashboards and handover documentation.

Is your context ready for a 90-day pilot?

We check the segment, internal owner, available data and acceptance criteria before proposing a scope.