Simple plans that scale with your team.

It becomes the database. The import runs in seven steps, upload, map columns, preview, detect duplicates, review historical notes, import, then evaluation. Every record enters with status New, and every note that came with the file is stored verbatim against its record with the source filename attached.

No. Notes are appended, never edited. A remark like “Left the company in 2025” is kept as a historical note and displayed beside the current status rather than becoming it. Duplicates are flagged for review, merging keeps every associated person, note and activity event, and each record keeps the company name it arrived with.

Ten weighted signals: job title, company size, industry fit, e-commerce presence, website quality, brand maturity, international presence, marketing activity, digital presence and estimated consulting need. The breakdown is visible on every lead, so you can see which factor moved the number.

No, and keeping them separate matters. Status describes where a record sits in the process. Priority describes how much it is worth. A brand-new lead can be the highest-priority one in the database.

Gmail, Google Calendar, Google Meet, Google Contacts, Google Drive, Google Sheets, Outlook, Microsoft Calendar, Slack, WhatsApp, LinkedIn, SMTP and outgoing webhooks. Connections use OAuth, no password is ever entered into kanês, and only the scopes listed on each integration card are requested.

Yes. Automations are plain IF → THEN rules you build yourself, and each one can be paused. Nothing runs that you have not switched on, and every run is logged on the affected record.

In your workspace. Enterprise plans can specify data residency. Access tokens for connected services are held server-side and never rendered in the interface.