Marie Kerner
- Roof area
- 128 m²
- Postcode
- 53111 Bonn
- Deal value
- 3.200 €
websiteMK
CRM
A CRM for lead generation, 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.
- A new record type is a form you fill in, not a migration
- Board and list are one dataset, not two exports
- Timed against a seeded 50,000-record account
- Bought on its own, on its own billing cycle
The tools were never the problem
The CRM was good at being a CRM. What it was not good at was the fields your business actually has, so they became custom fields, and the automation that used them was one tier up. Everything past that went out through a middleware tool, which meant a second copy of the record that had to be kept honest.
We ran a lead generation business on six of them. This is the part that cost us the most and showed up on no invoice.
- You pay per seam
- Every tool in the chain has its own subscription, and the one feature you actually needed is usually one price tier up.
- A field is not one change
- Add it in one place and it has to be added in the others. Miss one and nothing fails loudly: it fails the next time somebody filters on it.
- Someone else's release is your outage
- An API changes, a mapping stops matching, a webhook starts returning something new. You hear about it from the person who was waiting.
The record
One record, and everything else reads it
The record opens as a panel from the right: stage and owner at the top, and below them the fields, the history, the notes, the documents and the tasks. There is exactly one of it. Automation acts on it, distribution reads its fields, a campaign takes it through the same filter you use in the list, and the invoice at the end of the month counts the same line.
- Documents hang on the record. The quote, the proof, the photo, including the one a step generated.
- Tasks have a due date and a person. They stay open until somebody closes them, not until somebody forgets.
- The history answers “who was that”. A field change, a run, a message that went out, in one trail.
- A filter is the same filter everywhere. A view in the list, an audience in a campaign, a condition in routing.
Marie Kerner
opened from the board
QualifiedOwner:Marie KernerMK
FieldsHistoryNotesDocumentsTasks
- Company
- Nordkontor Vertrieb GmbH
- Roof area
- 128 m²
- Postcode
- 53111 Bonn
- Shading
- None
- Deal value
- 3.200 €
Rooftop DE
entity and its fields
| Field | Type | Role |
|---|---|---|
| First name | Text | — |
| Text | ||
| Phone | Text | Phone |
| Roof area | Area | — |
| Preferred date | Date | — |
| Shading | Choice | — |
| Permit | File | — |
Entities and fields
Your data model, not ours
A record is whatever your business calls one: a lead, a case, a listing, a claim. You define the fields, the types, the validation and the stages, and nothing about that is a code change or a support ticket.
- Entities are records, not an enum. Add one and it exists everywhere the same afternoon.
- Field roles. Mark which field is the name, the email, the number that gets summed.
- Where a field is used. Before you delete one, the system lists every place that reads it.
- Soft delete with findings. Nothing disappears while an automation still points at it.
- Address and area as field types. With a map where a map says more than a line, if the location module is booked.
What arrives
The same person, twice, from two sources
Records come in through the API, one at a time or in batches, from a form, an ad account or the system you are leaving. Two of them are the same human being. What happens then is your decision per entity, taken before anything else runs, and the intake log tells you whether anything is arriving from a source at all.
- Duplicate checks per entity. Which field counts, and what happens to the second submission.
- Idempotent intake. A sender that posts twice does not produce two records.
- Field roles, not field names. The platform knows which of your fields is the email without it being called that.
- A log for “is anything arriving”. The question that comes up constantly, with a surface that answers it.
Duplicates
decided per entity, before anything runs
Field
Email
If the same value arrives again, it counts as the same case.
On match
Update the existing recordDiscard the submissionCreate anywayNo check
RecordsLead98 recordsFilter: noneRecord
| 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 |
7 of 98 · sorted by created, newest firstLoad more
Board and list
Two views, one dataset
The board is for the case in front of you. The list is for the four hundred behind it: sortable, filterable, exportable, and fast at page four hundred because it pages by cursor and not by offset.
- 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.
- Saved per user. Your columns, your filters, remembered on the server, not in a browser.
- Export is a right, not a button. CSV and XLSX, and every export lands in the change log.
Working together
Who owns it, who may see it
Assignment, watchers and roles decide what a person finds when they open the account. Access follows responsibility rather than a flat “is admin” question. The navigation itself only shows what the rights allow.
- Roles you edit. A matrix of rights per object, not three fixed levels.
- Watchers. Someone can follow a record without owning it.
- Notes, timeline, documents. On the record itself, page by page, with who and when.
- Change log. Every change with actor and time, including the ones made by a script.
Team
who may see which records
| Name | Role | Sees | Status |
|---|---|---|---|
| Marie Kerner | Administrator | all records | owner |
| Sven Delmar | Agent | only assigned | active |
| Carla Nowak | Agent | assigned + unassigned | active |
| Anselm Roth | Analyst | all records | pending |
The CRM and the data model, article by article
What a stage carries, how the board totals a column, how a record looks up close, and how the fields under all of it are defined. The same text the product shows beside the screen you are on.
18 articles, written against the product and shown inside it too.
BoardThe board shows the records of one entity spread across the stages of a pipeline. Every column is a stage, every card a record. It reads left to right, as a path.PipelinesA pipeline is your way of working, written down as a row of stages. The board shows them as columns. A pipeline always belongs to one entity.Setting up a stageEvery column of the board has settings of its own: a description, a colour, optionally its own sum field, and two switches that decide where a record starts and where it ends.Record listEvery case in your account is here, as a table. You can sort, filter, select several rows at once and decide which columns to show.Working a recordThe record opens as a panel from the right. Stage and assignee sit at the top, and below them five tabs: Fields, History, Notes, Documents, Tasks.FiltersSearch finds a record you already have in mind. A filter describes a set: everyone in Leipzig who has been sitting untouched for two weeks and is assigned to nobody.Bringing data inRecords arrive through the API, one at a time or in batches. A wizard that reads a spreadsheet and maps its columns is designed and not yet built.ExportRecords as CSV or XLSX, with the scope and columns you choose. Every export lands in the change log, along with its scope and row count.DocumentsQuotes, supporting papers, photos: whatever belongs to a case hangs off it as a document. Documents arrive through the API, are produced from a template, or are uploaded on a file field.TasksA task is something someone still has to do, with a due date and an assignee. It stays open until somebody ticks it off.EntitiesAn entity describes what a record consists of. It is the first thing to exist in a new account, because everything else hangs off it: forms, lists, filters, automations and passing records to partners.Field typesA field is one detail on a record: phone, order value, preferred date. The type decides what may be written into it, how the value is shown and what you can filter by later.Field rolesParts of the application need to know which of your fields holds the email address. A field role answers that once instead of asking in every place.DuplicatesThe same person submits the form twice, or a source delivers a record again. You decide what the application recognises that by and what should happen then.NotesWhat does not fit into a field: the outcome of a phone call, a remark for a colleague, the sentence "wants to think it over". You write one through New note at the foot of the record, and read them in the Notes tab.HistoryWho changed what and when, which automation ran, when a message went out. The history answers that without anyone having to keep minutes.Document templatesA PDF on which you mark the spots that get filled with a record's values when the document is produced. That is how quotes, confirmations and contracts come about without anyone retyping.Who sees a recordNot everyone in the account sees every record. Three things decide it: the reach of the role, the assignee, and an explicit share on the single record.
Pricing
What the CRM costs
Buy just the CRM. There is no base plan underneath it to pay for as well, and nothing else has to be switched on for it to work. One price covers the CRM and Automation together, and it goes by how many people use it and how many records you keep. Cancel it later and your records stay: you can still search them and export them.
CRM & Automation, 1 user
$57.50/mo
billed yearly · $69.00/mo billed monthly
Save 17% vs monthly
Create your account- 1 user
- 2,000 records
- Board, list, pipelines, idle time
- Every trigger and step, no add-on
Above that: $0.02 a record
Most popular
CRM & Automation, 3 users
$82.50/mo
billed yearly · $99.00/mo billed monthly
Save 17% vs monthly
Create your account- 3 users
- 5,000 records
- Board, list, pipelines, idle time
- Every trigger and step, no add-on
Above that: $0.02 a record
CRM & Automation, unlimited
$99.92/mo
billed yearly · $149.00/mo billed monthly
Save 33% vs monthly
Create your account- Unlimited users
- 10,000 records
- Board, list, pipelines, idle time
- Every trigger and step, no add-on
Above that: $0.01 a record
Packages, everything else you can buy, and what is in every planPrices in USD, excluding VAT. Reverse charge applies inside the EU.
Questions people ask
If the answer you need is not here, the help center has the long version.
- What about GDPR, deletion periods and proving it?
- Every body of data in the platform carries a retention rule: a period, and what happens when it is up, which is delete, anonymise or keep. The deletion run shows you what it would remove before it removes it, a record under legal hold survives it and says why, and what was deleted stays on file after the data is gone. A table with no rule fails the build rather than an audit. The security page goes through all of it.
- Can I move my existing leads in?
- Yes. The intake API takes a payload in whatever shape you already send, and there is a CSV import for a one-off move. Records keep their original identifier so a second import updates rather than duplicates.
- Is the CRM usable without the other modules?
- Yes. The core carries entities, fields, records, intake, search, export, retention, the change log and document templates. The CRM adds pipelines, the board, the list and idle time. Distribution, automation, campaigns and signatures are separate and separately booked.
- How fast is the list with a lot of records?
- A seed script builds a 50,000-record account and a measuring script runs the list queries against it, with an upper bound per query that fails the run when it is exceeded. Paging uses a cursor rather than an offset, so page four hundred costs what page one costs.
- What happens to my data if I cancel the CRM module?
- The records stay. They belong to the core, not to the CRM. What goes is the pipeline view. You can still see, search and export every record, and you can export before you cancel.
Bring the month you would rather not talk about
Set up your own entity, your own fields and one routing rule, and see what it does with a record you put through it.