Scoring live traffic right now

Stop fake leads before they hit your CRM.

Between your form and the CRM. Once routing is on, clean leads pass through and bad or doubtful ones wait for a person.

Your sales team is triaging bots by hand.

Every open form is an invitation. Scrapers, competitors and fraud farms fill it out just as fast as real buyers do. By the time someone notices, junk leads are already skewing pipeline numbers and wasting a rep's morning.

Observe first every new project starts scoring-only: nothing is held until you switch routing on
Inline each submission is scored before the lead is saved, not after
4 categories every lead lands in, from certain spam to certain legit

What one caught fake lead is worth.

A junk lead still costs the minutes someone spends before it is obvious. Set that time, what the hour costs, and how many you catch.

A month$2706 hours

A year$3,24072 hours

One lead12 min$9

A layer between the form and the CRM.

You keep the form. You keep the CRM, or the script that already posts to it. Motacé stands in the middle and decides what is allowed to continue.

Form

The visitor submits

Your page, as it is. One tag on a static form, or POST JSON from React, Vue or Next. The submission hits Motacé first, not the CRM.

script, fetch()

Motacé

The layer in the middle

Motacé scores the submission before your CRM, or your own script, ever sees it.

  • Certain legitThrough
  • Likely legitWaits
  • Likely spamWaits
  • Certain spamHeld

Normal lead

It flies through

Once routing is on, certain legit is queued to the webhook you already trust, with retries, or returned to your script. Sales sees the lead they would have seen anyway.

through to CRM

Bad or doubtful

A person takes it

With routing on, certain spam is held. Likely spam and likely legit wait until a person sends one on or leaves it. Held leads do not go to the CRM by themselves.

person, then maybe CRM

Works with the CRM you already run.

A native connector creates the deal and, where the platform supports it, reports the outcome back. Anything else receives the lead through a configurable webhook. Every connector sits behind the same queue, retries and delivery log.

Native connectors

Built in, with a test delivery before you switch them on.

  • amoCRM / Kommo Live

    Deal and contact created when the lead is routed. Durable queue, retry, dead letter, manual retry.

  • Meta Conversions API Pilot

    QualifiedLead and Purchase sent after a person confirms the outcome, with one shared event id so Meta can deduplicate.

Any endpoint that takes HTTP

For a CRM, automation tool or your own script.

  • Configurable webhook Live

    Map fields to whatever the receiver expects, send JSON or a form body that tools like Albato can read, and open the exact request each delivery made.

  • Score breakdown included Live

    Every payload carries the rules that fired, so the receiving system can act on why a lead scored the way it did.

Next on the list

Not available yet. We build these in this order, starting with the CRMs customers ask for.

  • CRM
  • HubSpot
  • Pipedrive
  • Salesforce
  • Zoho CRM
  • Automation
  • Zapier
  • Make
  • n8n
  • Ad conversions
  • Google Ads
  • TikTok

Need a different one? Tell us which system your sales team lives in.

Request an integration

Built for the fraud patterns that actually show up in forms.

Identity portraits

Motacé recognizes the same person or bot coming back under a new email or phone number across all the projects of your own organization, not just within one form. Portraits never cross to other customers: there is no shared blacklist.

A board that shows who has looked

Likely spam and likely legit wait for a person. A card nobody has opened keeps a frame in the column colour until the first look, and the newest lead sits at the top. Certain spam and certain legit can be dragged to the archive or on to the CRM.

CRM webhooks, with the request

Map fields however the CRM expects them, including a form body tools like Albato can read. Open the exact request a delivery sent. A certain-legit lead can be sent again once a webhook is ready to take it.

Telegram on the person, not the company

Each person links their own Telegram and chooses which projects to hear about. The alert names the project and carries buttons to send the lead to CRM, hide it, or overturn a certain verdict. Email still carries the same breakdown.

One board, the project on the card

Your site forms, or any system that can post to the ingest API, land in the same queue. A mixed board prints the project beside the lead. Star the projects you return to, and narrow everything from one filter field. A phone with a country code shows its flag.

Start with a pilot

Plans are sized by leads processed per month, with limits on projects and users. We begin with a paid pilot on one project. See Pricing.

The weights every project starts from

Each signal adds its points. A project can change them. Zero means that signal never fires.

  • Bot trap filled 100
  • Identity blacklisted 100
  • Email domain cannot receive mail 60
  • Throwaway email 40
  • Email on a spam list 40
  • Submitted too fast 30
  • Unusable phone number 30
  • Name is not a name 25
  • VPN or datacenter address 25
  • Too many submissions 20
  • Identity seen before 20
  • Country does not match the IP 15
  • Near-duplicate of another lead 15

Built to sit in the lead path, with explicit boundaries.

Lead intake runs independently from the dashboard, and every integration has an explicit boundary.

Authenticated ingestion

Each project receives its own API key. Browser submissions are scoped to the public intake endpoint.

Idempotent delivery

Retry the same submission safely with an idempotency key without creating duplicate leads.

Encrypted CRM credentials

Webhook authorization headers are encrypted at rest, with delivery history available for review.

Privacy-aware signals

Device fingerprinting is opt-in. Core scoring works without enabling it.

Priced by the leads you process.

Pick the plan by monthly lead volume. Projects and users are limits of the plan, not extra line items. Prices are per month, without VAT, billed by invoice. We begin with a paid pilot and set the project up together with you.

Starter

€79per month

10,000 leads a month

  • 3 projects, 3 users
  • 1 CRM connection per project
  • Routing, review board, Telegram and email alerts
  • 30 days of lead history

Beyond the volume: €8 per extra 1,000 leads.

Ask about Starter

Growth

€249per month

50,000 leads a month

  • 10 projects, 10 users
  • Several CRM connections per project
  • Everything in Starter
  • 90 days of lead history

Beyond the volume: €5 per extra 1,000 leads.

Ask about Growth

Agency

€699per month

200,000 leads a month

  • 40 projects, 30 users
  • Several CRM connections per project
  • Everything in Growth
  • 365 days of lead history

Beyond the volume: €3.50 per extra 1,000 leads.

Ask about Agency

Enterprise, from €1,990 a month

From 500,000 leads a month, with project, user and retention limits agreed in a contract and a volume rate for extra leads.

Start with a pilot

€149 for 60 days, up to 25,000 leads and 5 projects. We connect the form and the CRM with you and measure the baseline before any automation is switched on.

Try it free

The sandbox takes 500 leads a month on one project, with 7 days of history and no CRM routing.

What teams ask before connecting a form.

Do we need to replace our forms?

No. The script is a layer in front of what you have. Add it to the form, or send the submission from your own code. Your CRM, or your script, still receives only the leads Motacé lets through.

What happens when a lead is uncertain?

It stays on the board, in Likely spam or Likely legit, with its score and the heaviest rule. A person decides. It does not go to the CRM until someone sends it. A certain-spam lead is held the same way: it does not fly in on its own.

Can a dashboard deployment interrupt lead intake?

No. Intake, dashboard and public sites are deployed as separate services, so a frontend or dashboard release does not restart submission processing.

Can we retry a submission?

Yes. Send an Idempotency-Key header and repeated delivery returns the original result instead of creating a second lead.

Which CRMs can we connect?

Use a configurable webhook for any CRM that accepts HTTP requests. There are built-in connectors for amoCRM/Kommo and the Meta Conversions API, with test delivery before activation. HubSpot, Pipedrive, Salesforce and Zoho are next; see Integrations or ask for yours.

Open the demo, or start your own.

The demo board is already live: made-up leads, the real product. Sign up when you want a company of your own.