One lead generation platform, from the lead coming in to the invoice going out
Capture, qualification, mail, documents, routing, delivery, returns and partner billing sit on one data model, so adding a field costs one change instead of six, and month end stops being a spreadsheet.
Set up your own entity and one routing rule. Everything on this page is what runs behind it.
- Keep your form: the intake API takes its payload as it is
- Selection, delivery and billing are one module, not three tools
- ZUGFeRD and XRechnung out of the box
- Modules booked one at a time, each on its own cycle
- Hosted in the EU, deletion you can prove
One platform. Three steps. No data silos.
Every lead runs from arrival through qualification to payment on a single entity-driven model, with no manual transfers and nothing to keep in sync.
Capture
Leads arrive through the intake API: from the form you already run, from an import, or from any other source. Each one becomes a structured record, not a message in an inbox.
Qualify and automate
Work them on a board, or let an automation do it. When a record moves, the flow fires: mail, webhook, assignment, a change of stage, or straight into distribution.
- Assign to the rota
- Send the confirmation mail
- Distribute lead
Monetize
Deliver to the buyers the rules picked, with caps and duplicate checks respected. Invoices are generated, corrections settle themselves, and partners have their own portal.
What is in it
Four parts, bought separately. Most people start with one and add the next when the manual work shows up.
The front of an entity, not a second data model
Every field on the form points at a field on the entity. There is no mapping screen, because there is nothing on the form that does not already exist on the record. Two lines on your page and submissions arrive as structured records.
- Conditional logic. Show or hide a field, or a whole page, based on the answers so far.
- Styled from your stylesheet. Colours, corners and fonts through variables, so the brand lives in one place.
- Embedded without a frame. It takes your page's width, not a scrollbar inside a box.
- Or keep the form you have. Point it at the intake API and skip this module entirely.
Your roof
Four questions, then we know whether it is worth a call.
| Name | Stage | Deal value | |||
|---|---|---|---|---|---|
| Marie Kerner | New | 128 m² | 53111 Bonn | 3.200 € | MK |
| Pia Lindqvist | Qualified | 164 m² | 99084 Erfurt | 4.100 € | AR |
| Anselm Roth | Handed over | 210 m² | 45127 Essen | 5.250 € | AR |
| Tobias Behrens | Qualified | 88 m² | 89073 Ulm | 2.200 € | MK |
| Sven Delmar | New | 92 m² | 24103 Kiel | 2.300 € | TB |
| Carla Nowak | Handed over | 143 m² | 59065 Hamm | 3.575 € | TB |
| Hanna Brauer | Lost | 74 m² | 07545 Gera | 1.850 € | MK |
Your pipeline, and the numbers under it
Define what a record is: the fields, the stages, the order. Then work it on a board or as a list. The two are the same data with two sets of eyes, one for the case in front of you, one for the four hundred behind it.
- Entities you define. A new record type is a form you fill in, not a migration.
- A sum per column. Point it at any number field and the board totals it as you work.
- Idle time per stage. The card says how long it has been sitting there, before you have to ask.
- Measured, not hoped. The list queries are timed against a seeded 50,000-record account, and a regression fails the run.
The part of the day you should not be doing
Confirmation mail on arrival, three follow-ups when nobody picks up, hand-over when the record is ready. You build it once in a flow you can read, and afterwards you only look when something got stuck.
- Twenty-one triggers. Created, field changed, stage entered and left, idle, date reached, by hand, reply received, form submitted, and more from Distribution, Signatures and Appointments.
- Twenty steps. Branch, wait, webhook, mail, SMS, document, calculate, assign, distribute.
- Step output chaining. A later step reads what an earlier one got back from your API.
- No step pretends. One without an implementation cannot be selected, so nothing reports a success it did not have.
| Document | Partner | Period | State | Amount |
|---|---|---|---|---|
| 2026-0184 | Nordkontor Vertrieb GmbH | 52 × 40 € | paid | 2.080,00 € |
| 2026-0185 | Rheinwerk Süd GmbH | 31 × 120 € | open | 3.720,00 € |
| 2026-0186 | Vialux Solar B.V. | 44 × 95 € | overdue | 4.180,00 € |
| preview | Alpsol Handels GmbH | 61 × 250 € | preview | 15.250,00 € |
A preview still changes. An invoice carries a number and does not.
Who gets it, what it costs, and the invoice at the end
The half that usually falls back to a spreadsheet. Rehearse the routing before anything leaves, deliver it, take it back when a buyer is entitled to, and let the month close itself.
- Rules with teeth. Four kinds of cap, time windows, duplicate checks, three strategies.
- Delivery you can audit. Webhook or mail, retried at 5, 15 and 60 minutes, a key on every attempt.
- Invoicing built in. Gapless numbering, four tax cases, credit notes, ZUGFeRD and XRechnung.
- A portal for your buyers. Their leads, their returns, their invoices, without a mail to you.
What to look for in a lead platform
If you are comparing, these are the six questions that decide whether you end up with one system or six again. They are worth asking of us too.
How we answer them, and what to ask anyone elseStart with the part that costs you the most time
Start with the one of the six that costs you the most time. Set that module up with your own field names, and let the rest follow when you are ready for it.
Book what you use
The core is always there: entities, fields, records, intake, search, export, retention, change log and document templates. Everything else is a module on its own billing cycle. One you have not booked is not greyed out with a price on it; it is not in your account.
Or take a package
Three bundles that carry all four parts. If you only need one module, the single price list is on that module’s own page.
- CRM: 1 user, 2,000 records
- Automation: every trigger and step, no add-on
- Distribution: 50 leads a month
- Form builder: 1 form
- CRM: 3 users, 5,000 records
- Automation: every trigger and step, no add-on
- Distribution: 200 leads a month
- Form builder: 3 forms
- CRM: unlimited users, 10,000 records
- Automation: every trigger and step, no add-on
- Distribution: 1,000 leads a month
- Form builder: unlimited forms
It fits what you already run
There is no marketplace of four hundred logos here. There are four doors, they are documented, and everything on this page goes through one of them.
Leadflip has no industry of its own
Entities, fields, pipelines and rules are yours to define, so the vocabulary on your screens is the one your buyers already use. These are the places where lead selling happens to be common.
Questions people ask before the demo
Do I have to move off my current form?
No. Point it at the intake API and keep everything else as it is. Leadflip does not currently build forms, and we would rather say so than sell you a migration.
What happens to my data if I cancel a module?
The records stay. They belong to the core, together with fields, documents, the change log and the API, so cancelling the CRM takes the board and the pipelines and not the data under them. What a module takes with it is its own surface: its pages answer with not found and its steps leave the automation catalogue. You can export before you cancel, and afterwards.
Can my partners send a lead back?
Inside the return deadline, yes, and without asking you: the return produces a credit note on the next invoice. After the deadline they can only ask. The request then sits above the delivery list with whatever they wrote, and you decide. That is the difference between a right and a request, and the interface says which one you are looking at.
Do I still need a middleware subscription?
Not for what happens between the parts you have here. The webhook step runs inside the flow rather than beside it, so a later step can read what your system answered. Middleware earns its money when you connect two systems that both belong to somebody else, and that case does not go away.
Where is the data hosted?
Application and database run in EU regions, and nothing is replicated outside them. Backups sit with the database provider inside the same region. The security page says what else we do, and names the one claim our predecessor made that is not true here.
Does it do ZUGFeRD and XRechnung properly?
Both, and both follow EN 16931. ZUGFeRD is a PDF with the data embedded invisibly, XRechnung is the data on its own. They are off by default and switched on per partner, because a badly built e-invoice is worse at the receiving end than none at all: it gets read in and lands in the wrong place.
Are process mails, texts and documents extra tools?
No, and none of them carries its own price here. Mail leaves over the SMTP you configure, as a step in the flow rather than as a second subscription. A document comes from a PDF you upload once with the spots marked that get filled from the record, so a quote or a contract is produced without anyone retyping it. An SMS is a step like any other and takes the number from whichever field carries that role; the one thing it needs from outside is your own account with a text provider, and you settle that bill with them.
Who owns the partner relationship?
You do. The portal shows a partner their own records, their own invoices and their own settings, and of the records only the fields you released for partners. There is no marketplace behind it and no second contract: your buyers stay yours, and they never see anyone else.
Worth reading before you talk to us
How to build the routing, how to invoice the buyers, and why the five-tool stack costs more than it looks. None of them needs an account.
How to Build a Lead Distribution System in 2026
Routing is the easy part. What decides whether a distribution system survives contact with real buyers is whether you can explain, months later, why a given lead went where it went.
Read itHow to Invoice Lead Buyers and Automate Partner Billing in 2026
An invoice number is a boundary. Before it, a draft can change silently; after it, every correction needs its own document. The decisions that follow from that, including the two most home-built billing systems get wrong.
Read itConsolidating a Lead Generation Stack: What to Merge, What to Keep
Three seams in a lead generation stack cost real money, and the rest are fine. Which parts belong in one system, which tools to keep, and how to count what the gaps actually cost you.
Read itBring the month you would rather not talk about
The one with the most returns and the ugliest invoice run. Put it through Leadflip and see what the routing rules and the billing run would have done with it.
