← Back to the start page

How the engine works

Synthetic leads: how they come about

A synthetic lead is not a bought contact and not a list. It comes about when the engine assembles several signals about one company, attaches the evidence and turns it into a suggestion your sales team can call.

How the engine works

What the engine does

The signal engine continuously watches external sources (press, registers, public tenders, the web) and your internal data (ERP, CRM, order history, functional mailboxes). When a trigger meets your target profile, a signal is created with source, date and quote. Scoring ranks it by target profile, freshness and time window. Above the threshold it becomes a suggestion for the rep who owns the account: whom to contact, how to open. One click turns the suggestion into a lead in the CRM. The rep’s verdict feeds back into the next scoring.

Your CRM records what happened. The engine shows what is coming up, and writes its results back into your CRM.

How the engine works

Two directions, one picture

External: what the market reports

Public sources, watched continuously, every report with a source link on the signal.

  • Press and trade media per industry and region
  • Registers, public tenders, calls for bids
  • Openings, construction projects, expansions, leadership changes
  • Public web sources and directories

Internal: what your data knows

The biggest lever usually sits in house, unused in existing systems.

  • Order history: who went quiet, whose rhythm stopped
  • ERP and CRM: stock, cases, contacts
  • Functional mailboxes: enquiries and replies
  • Your team’s verdicts: hit or miss

How the engine works

From signal to lead

  1. 1

    Signal with evidence

    The engine detects a trigger and attaches the evidence directly: source, date, quote. Nothing guessed.

  2. 2

    Scoring

    Does the company fit the target profile, how fresh is the trigger, how open is the time window? Only above the threshold does it go on.

  3. 3

    Suggestion for the rep

    Whom to contact, how to open. In the call plan on your cadence, per rep.

  4. 4

    One click to lead, one verdict back

    Accepting is enough: a lead in the CRM with context. Hit or miss sharpens the next scoring.

Your data stays yours

Every client runs in its own cell, separated at database level. Researched contacts, signals and analyses belong to you, even if the collaboration ends.

Humans decide, the machine prepares

Sending and important steps happen with approval by your team. The engine proposes and explains; your team has the last word.

The difference

What Veygar does differently

Much of this exists on its own: sourced signals from data vendors, ERP-based recommendations from AI assistants, pilots from appointment agencies. Veygar combines it into one service for your own sales team: trigger, plan and proof from one hand.

ComparedSignal and contact dataAI assistant on ERP dataCRM with AI featuresAppointment agency, AI SDRVeygar
External triggers with source (press, registers, tenders)yesnopartlypartlyyes
Your own order history as a sourcenoyespartlynoyes
Call plan for your own sales repspartlyyespartlypartlyyes
Monthly value report: customers touched, ordersnopartlypartlypartlyyes
Entry via a pilot with success criteriapartlypartlypartlyyesyes
Free lookback on your data before the startpartlypartlynonoyes

Every row exists somewhere already. The combination as an operated service for your own sales team, with a lookback up front and a value report afterwards, is our offer.

Classification by the publicly described services of typical providers per category, checked in October 2026: data vendors with trigger events and list upload, AI assistants on ERP data for wholesale, CRM prospecting agents, appointment agencies with pilot packages. No statement about individual vendors. "Partly" means: available, but not in this form.

Built to order

Backend, frontend, data integration

The engine is the core product. Around it we build what sales and operations need beyond that. Everything here runs today, for clients or for ourselves.

  • Backend and frontend

    Live CRM with ERP integration

    Deal pipeline, contacts and inventory data from the ERP, change log per record, map view of locations.

  • Platform

    Revenue engine with client portal

    Scoring, map view, press signals, roles per key account, mailbox integration, usage log. Access via client ID and password.

  • Data

    Venue radar

    Around 1,000 leisure venues screened, verified and tagged with a dated trigger, as a target list for machine placement.

  • Tool

    Sales tool with call list

    Radar of documented target accounts, call script and pipeline. We sell with it ourselves.

  • Automation

    Quote and invoice automation

    Quotes, invoices and follow-up emails are generated automatically and only go out after approval.

  • In progress

    Dealer website with stock integration

    Consumer site for a dealer: machines and availability straight from the wholesaler’s stock.

FAQ

Frequent questions about the engine

A CRM records what happened: contacts, notes, closed cases. The engine shows what is coming up: it watches sources, detects triggers and presents sourced suggestions to the team. Both complement each other; the engine writes back into the existing CRM and does not replace it.

Contact

Which signals does your market send?

15 minutes is enough. Or request the lookback on your own data first.