Home/Use cases/Cleantech project developers
Illustrative scenario

Reaching cleantech project developers while the project is still being specified

A controls supplier sells into solar and battery storage projects. The buyers are developers, and the same developer hides behind many project companies. This scenario shows how a clean account list and a role by role campaign fit that.

Illustrative scenario, not a client story. Voltmere Controls, its target developers and every row below are made up, with reserved .example domains. We describe the work and the deliverables. We claim no results, no pipeline and no market figures.

The situation

Voltmere Controls, a fictional supplier of monitoring and control software for battery storage sites, has a four person commercial team. It sells to independent developers of utility scale solar and storage in three regions of Europe. A deal needs a technical champion and a budget owner to agree.

The team used a generic energy company list, went to two conferences and ran broad ads to anyone in renewables. The list mixed installers, utilities and consultants. The ads reached engineers at large utilities who buy through framework contracts.

Three frictions that stall it

The buying committee is split

The development lead, the technical director, the investment side and procurement each hold a different veto. One message to one title rarely moves a deal.

Timing follows the project

A developer may be a year from needing a controls supplier and then need a shortlist in weeks, after permitting or grid connection moves. The calendar is no guide.

One developer, many names

Projects often sit in separate project companies under a parent. A raw list shows the same buyer under several names and misses the real account.

The goal

Good looks like one account per developer, the right roles named at each, and a campaign that reaches several of them early.

  • A clean list of parent developers, with project companies merged into them
  • Two or three buying roles named per account, such as development, engineering and investment
  • A visible hint of project stage, with the month it was found
  • A campaign per region and language group, so messages stay local

The audience we would define

Small to mid size developers in three regions, with roles chosen by what each person can veto. The options come from the segments we can target and the industry guide.

DimensionChoice for this case
IndustriesEnergy and utilities, construction and engineering (project developers only)
Company size11 to 50, 51 to 200 and 201 to 500 employees
RegionsDACH, Southern Europe, Central and Eastern Europe, one audience each
Titles and seniorityOwner or founder, Head of, Director, VP
DepartmentsOperations, engineering, finance, procurement
Role keywordsProject development, grid connection, asset management, procurement
Signals to watchNew project announced, funding announced, expansion into a new country, hiring development roles

How the list narrows

Energy sector companies in three regions

Developers, not installers or utilities

Merged under parent companies

With two or three roles named

Schematic only. Real counts are tested before you commit.

What billion.lt builds

Six steps. The merge rules and the role map are agreed with the commercial team on a sample first.

Brief

Product, project types, regions and the roles that decide, plus the accounts already in conversation.

List

Developers identified from open-source company information and public project announcements, then split by region.

Merge

Project companies rolled up to parents, duplicates removed, customers and partners marked.

Roles

Two or three roles per account found and checked, so each message reaches a role that can act.

Audience

Company lists matched per region, then narrowed by title and seniority filters. We size each audience first.

Review

A weekly read of replies by role, and new project announcements merged into the accounts.

Illustrative deliverables

An account sheet, role map and audiences, one per region.

Developer (parent)DomainProject companiesRoles namedStage hint
Sunmere Renewablessunmere-renewables.exampleSeveral, mergedDevelopment, engineeringNew project announced
Altbach Energiealtbach-energie.exampleSeveral, mergedDevelopment, financeFunding announced
Costa Solis Energiacosta-solis.exampleSingleFounder, engineeringHiring grid engineer
Vistula Storagevistula-storage.exampleSeveral, mergedDevelopment, procurementEntering a new country
Nordhang Powernordhang-power.exampleSingleFounderNo signal yet

Illustrative rows on reserved .example domains. Real lists are built to your brief.

The audience card

  • Accounts: parent developers, per region
  • Roles: development, engineering, investment
  • Language: one audience per language group
  • Excluded: utilities, installers and customers

A Conversation Ad opener

The weekly review

  • Replies by role and region
  • Which signals came before a reply
  • New project announcements, merged into accounts
  • Roles still missing at active accounts

Where the value comes from

No figures here, because nobody can promise them. This is the reasoning for this case.

Time saved

No one reconciles project companies to parents by hand or hunts for the technical director behind each name. The commercial team starts from accounts, not from a pile of entities.

Waste avoided

No ads to large utilities that buy through other channels, to installers who are not developers, or twice to the same developer under two names.

Risk reduced

Each region has its own audience and its own message. We keep to business information, flag signals with a date and keep the ad account in your hands.

Focus

Business development talks to a committee early, with the right opening for each role, instead of building spreadsheets before every campaign.

Is this your situation?

A good fit

  • You sell to project developers early in a project
  • A deal needs two or more roles to agree
  • You can handle replies in the local language or in English
  • Your target list is hundreds of accounts, not a handful

Probably not a fit

  • You sell to homeowners or small installers
  • You only target the very largest utilities, a short list you can build by hand
  • You need exact project stage, which public information cannot give

You stay responsible for your own outreach rules in each country. We work from public professional information and business details only.

Questions from this sector

How do you tell developers from installers?

By what the company says it does and by the projects it announces publicly. We confirm the split on a sample with you before the full list.

Can you cover several countries?

Yes. We build one audience per country or language group, so each message reads as local.

Do you know the project stage?

Only what is public, such as announcements the company itself makes. We treat it as a hint with a month attached, never as certainty.

Selling into developers?

Send the regions, the project types and the roles that decide. We reply with a scope and a sample of the account list.