CRM
Every email, task, quote and invoice points at the same contact. Your processes are modules of their own, with their own stages and fields — recruitment does not look like sales.
Notes, email, calls, SMS, tasks, stage changes and form submissions — on one record, in order. Tags, attachments, and an email address belongs to at most one live contact per company, which is why duplicate detection works on phone number and name + company instead.
A module owns its stages, its fields and its vocabulary. Six templates to start from — sales, recruitment, project, support, property, blank — a drag-and-drop board, and every stage change recorded, because the reports read from that history.
Tasks bound to a record, with priority and a due date, grouped by when they are due. Monthly, weekly and daily calendar where tasks, events and approved leave share one grid. ICS subscription for Google, Outlook and Apple Calendar.
Text, number, date, select, checkbox and the rest — with a bilingual label, attached to contacts, companies, deals or one module. They appear on forms, in views, in import and in export, not only on the edit page.
A property, a machine, a contract — things that are not a contact, a company or a deal. A record type has an owner, links to a contact, company and deal, and the same access rules, search, export and audit log as the built-in entities.
Roles with a permission set, module access per team or per person, and an "own records only" scope enforced in lists, search, export and every picker. Unassigned records stay visible to everyone — a new lead must not vanish.
CSV import with column mapping — it reads Hungarian Excel semicolons and accents, and merges duplicates.
Pick a template — sales, recruitment, project, support, property — or build your own.
From then on the correspondence files itself, and the team can see where things stand.
The same thing step by step, in the help centre.
What the three steps after registration ask, and what depends on the answers.
Column mapping, the email uniqueness rule, and what happens to duplicates.
Why a pipeline is a module, how the six templates work, and what a stage of your own is.
When a field is enough, and when you need a whole record type.
Roles, sharing and classification — in plain words.
Here they are the same thing: a pipeline owns its stages and its custom fields, which is why we call it a module. Two modules may use the same field key for different things — recruitment's "deadline" is not sales' "deadline".
The Team plan has no ceiling. Exports stream rather than truncating at a size limit, and search runs on trigram indexes rather than row-by-row comparison.
Entering their last day revokes access, their records stay, and their open work is handed to a colleague in one step. Closed deals stay with whoever closed them.
14 days, no card. If it doesn't suit you, export everything and leave — the data stays yours.