What we build next.
Suggest ideas, vote for the ones you need and follow their status. The most voted move up the list.
CRM: Two-way sync with HubSpot so a team can use both during a migration
HubSpot: Data sync keeps HubSpot and another app in step in one or both directions, with field mappings, filters and conflict rules (https://knowledge.hubspot.com/integrations/connect-and-use-hubspot-data-sync). Today: lib/crm-import-jobs.ts:16-24 (re-import updates through crm_external_ids); lib/groups-hubspot-sync.ts:1-25 syncs company properties for Lines only. Moving a sales team takes weeks; during that time both CRMs must show the same contacts, companies, deals and activity. First scope: connect a HubSpot private app token from CRM settings, preview what would sync, keep contacts, companies and deals fresh from HubSpot, then write changes back with per-property conflict rules, a status page with errors and retry, and a switch to pause everything.
CRM: Start new workspaces with the HubSpot default pipeline and a HubSpot-style setup option
HubSpot: The default Sales pipeline has seven stages with preset probabilities (https://knowledge.hubspot.com/object-settings/set-up-and-customize-pipelines). Today: lib/seed.ts:20-22, :34-40. A team that arrives from HubSpot expects the stages and names it knows. First scope: seed the seven HubSpot default stages with their probabilities for new workspaces (or as a Use HubSpot defaults button in pipeline settings), and review menu names against HubSpot (goals, recycle bin, properties). Also covers the parity rows nav-structure.
CRM API: search with filters, batch endpoints, and endpoints for properties and owners
HubSpot: CRM API: objects, properties, associations, owners, pipelines, lists, search and batch endpoints (https://developers.hubspot.com/docs/api-reference/latest/crm/using-object-apis.md). Today: app/api/v1/crm/{contacts,companies,deals,leads,objects,tasks,activities,products,quotes,pipelines,associations,tags,sequences,forms,email-templates}. Integrations written for HubSpot rely on search and batch calls; without them every sync is one request per record. First scope: POST search on contacts, companies and deals with the filter rules of the UI, batch create, update and read of up to 100 records, and read endpoints for property definitions and workspace members.
CRM: Audit log of exports, imports, bulk deletes and settings changes
HubSpot: Account audit logs list who exported, deleted, imported or changed settings, with an export history page (https://knowledge.hubspot.com/account-management/view-and-export-account-activity-history). Today: lib/crm.ts:433 property events; lib/crm-trash.ts; no CRM audit module among lib/*-audit.ts (board, chat, docs, groups, track). When data leaves or disappears an admin needs to know who did it. First scope: a CRM audit table and page (admins only) with exports, imports, bulk edits and deletes, merges, permission and pipeline changes, with who and when, never the record contents.
CRM: Permissions per object for view, edit and delete (all, team, owned), with export and import switches
HubSpot: Permissions per object: view, edit and delete, each set to everything, team only, owned only or none, plus export, import and bulk delete, saved as permission sets (https://knowledge.hubspot.com/user-management/hubspot-user-permissions-guide). Today: lib/crm-visibility.ts:19 one MEMBER_VISIBILITIES setting for the workspace; lib/roles.ts:11. A HubSpot admin limits who can edit or delete other people records and who can export the database. Today whoever sees a record can delete it. First scope: per role or per person, for contacts, companies, deals and tasks: view, edit and delete each set to all, team, owned or none, plus switches for export, import and bulk delete, enforced in the same place as ownerScope.
CRM: More workflow actions: rotate owner, create a deal, remove from a list, several branches
HubSpot: Actions include Rotate record to owner, Create record, Edit record (incl. associated records), Add to and Remove from static list, Send internal notifications, branches with many paths (https://knowledge.hubspot.com/workflows/choose-your-workflow-actions). Today: lib/crm-workflows.ts:57-69 ACTION_TYPES; branch semantics at :917-925. These are the actions HubSpot sales workflows use most after tasks and emails. First scope: rotate owner among a team (reusing round-robin assignment), create a deal or a task on the associated record, remove from a static list, set a property on associated records, and a branch with more than two paths.
CRM: Enroll in a workflow by filter criteria, with re-enrollment, for companies too
HubSpot: Enrolment triggers can be filter criteria (property values, list membership, activity) evaluated continuously, with optional re-enrolment and enrolling existing records (https://knowledge.hubspot.com/workflows/set-your-workflow-enrollment-triggers). Today: Triggers are events with a small config (form, score threshold) (lib/crm-workflows.ts:36-54, :816-825); no criteria or re-enrolment setting. HubSpot workflows start with When a record meets these conditions. First scope: trigger conditions built with the list filter builder on contact, company and deal workflows, checked on record changes and on a schedule, an Enroll existing records option, and a re-enrollment switch. Also covers the parity rows workflow-company-objects.
CRM: Delays in workflows
HubSpot: Delay actions wait a set time, until a date, a day and time, or until an event happens (https://knowledge.hubspot.com/workflows/choose-your-workflow-actions). Today: No delay or wait in ACTION_TYPES (lib/crm-workflows.ts:57-69); only sequences have wait steps (lib/crm-sequences.ts:23). Most HubSpot workflows wait between steps (send, wait 3 days, create a task). Without delays they cannot be rebuilt. First scope: a delay action (minutes, hours, days, until a date property) backed by a scheduled run claimed from the minute cron, visible in the run log, cancelled when the record no longer exists.
CRM: Two-way Google Calendar sync and scheduling a meeting from the record
HubSpot: With Google Calendar or Outlook Calendar connected, meetings created on a record go to the calendar with invites, and calendar events with contacts are logged on the record (https://knowledge.hubspot.com/integrations/use-hubspots-integration-with-google-calendar-or-outlook-calendar). Today: lib/crm-integrations.ts:166 (Cal bookings), lib/crm-outlook-sync.ts; no Google Calendar read in lib/crm-email-sync.ts. Meetings are the main logged activity for most sales teams and today only Cal bookings and Outlook events arrive. First scope: read Google Calendar events with contacts into the timeline (the Gmail connection already exists), and a Meeting action on the record that creates the event with attendees on the connected calendar.
CRM: BCC address to log email from any client, and a never-log list
HubSpot: Each account has a BCC address (logs outgoing mail) and a forwarding address (logs received mail) that work from any mail client (https://knowledge.hubspot.com/connected-email/log-email-in-your-crm-with-the-bcc-or-forwarding-address). Today: No BCC or forwarding address in lib/crm-email.ts, lib/crm-email-sync.ts or lib/crm-extension.ts. Not everyone connects an inbox; the BCC address is the fallback HubSpot users know, and the never-log list keeps private and internal mail out. First scope: a per-workspace inbound address that logs the message on the contacts in To and Cc, plus a list of addresses and domains that sync, the extension and BCC all skip. Also covers the parity rows email-never-log.
CRM: Named task queues, a tasks table with views, and reminders
HubSpot: Task queues: named queues a rep fills and then works one task after another; any filtered task view can be started (https://knowledge.hubspot.com/tasks/create-tasks). Today: lib/crm-work-queue.ts:11-12 scopes due, overdue, today; components/crm/QueueFilters.tsx (scope and owner). Reps organise their day in HubSpot with queues (calls to make, follow-ups) and the tasks table. First scope: queues a person creates and adds tasks to, Start tasks from any filtered task view, a table view of tasks with type, priority, queue and associated record columns and bulk edit, a reminder time on a task and a daily email with the tasks of the day. Also covers the parity rows tasks-index, task-reminders.
CRM: Tickets object with a support pipeline
HubSpot: Tickets are a standard CRM object with a support pipeline (New, Waiting on contact, Waiting on us, Closed), a board and associations (https://knowledge.hubspot.com/object-settings/set-up-and-customize-pipelines). Today: No ticket table among the CRM tables (lib/crm-schema.ts, lib/schema/baseline.ts:69-380). Tickets exist only inside Lines (app/api/v1/groups/tickets). Teams that use HubSpot tickets for onboarding or support cannot leave without them. First scope: tickets with name, pipeline and status, priority, owner, source and description, a board and a table, associations with contacts, companies and deals, the timeline, and the HubSpot default support pipeline (New, Waiting on contact, Waiting on us, Closed).
CRM: Associate an activity with several contacts, companies and deals
HubSpot: An activity can be associated with many contacts, companies, deals and tickets; logging on a contact also associates its primary company and up to five recent open deals (https://knowledge.hubspot.com/connected-email/log-email-in-your-crm-with-the-bcc-or-forwarding-address). Today: crm_activities has single contact_id, company_id and deal_id columns (lib/schema/baseline.ts:172-174). A meeting with three people from one account shows on one contact today. HubSpot shows it on all of them and on the deal, and imported activities lose links. First scope: an association table for activities (keeping the current columns as the primary link), auto-association with the contact company and open deals when logging, and an Associated with picker in the composer.
CRM: Admin-defined association labels, also between deals and contacts
HubSpot: Association labels describe the relationship between any two records (Decision maker, Billing contact...); admins create single and paired labels per object pair (https://knowledge.hubspot.com/object-settings/create-and-use-association-labels). Today: lib/crm-constants.ts:38-45 six fixed contact to company labels; lib/crm-assoc.ts:41-44 rejects others; crm_deal_contacts has no label (lib/schema/baseline.ts:153-157). Deal contact roles (decision maker, champion, billing) are how HubSpot teams run multi-threaded deals, and the sync has to keep them. First scope: labels defined per object pair in settings (the six current ones become the defaults for contact and company), a label on deal to contact and deal to company links, shown and editable on the association cards.
CRM: One properties page per object with built-in and custom properties, search and descriptions
HubSpot: Settings › Properties lists every default and custom property of an object with search, filters by group, type and creator, usage, archive and restore, and export (https://knowledge.hubspot.com/properties/create-and-edit-properties). Today: components/crm/CustomFieldsPanel.tsx; lib/crm.ts:3119-3200. Read in code, not seen running. Admins coming from HubSpot manage everything from Settings › Properties. First scope: list built-in and custom properties together per object with type, group, description and where they are used, with search; descriptions show as help text next to the field.
CRM: Let admins edit the options of lead status, source, priority, industry and deal type
HubSpot: Lead status is an editable dropdown with eight defaults: New, Open, In progress, Open deal, Unqualified, Attempted to contact, Connected, Bad timing (https://knowledge.hubspot.com/records/use-lifecycle-stages). Today: lib/crm-constants.ts:14-22 LEAD_STATUSES is a const list. Every HubSpot portal has its own lead status list; a fixed list forces the team to change process during the migration and makes the sync lose values. First scope: store the options of built-in dropdowns per workspace (seeded with the HubSpot defaults, Attempted to contact included), editable in Settings › Data, with a migration of existing values. Also covers the parity rows standard-property-options.
CRM: Editable lifecycle stages that move on their own when a deal is created or won
HubSpot: Eight default lifecycle stages (Subscriber, Lead, Marketing qualified lead, Sales qualified lead, Opportunity, Customer, Evangelist, Other); admins can add and edit stages (https://knowledge.hubspot.com/records/use-lifecycle-stages). Today: lib/crm-constants.ts:5-13 LIFECYCLE_STAGES is a const list. HubSpot moves the contact and company to Opportunity and Customer automatically; without it lifecycle reports go stale after the migration. First scope: add the Other stage, let admins add and rename stages, and a setting (on by default) that sets Opportunity on deal create and Customer on deal won, never moving a record backwards. Also covers the parity rows lifecycle-auto-sync.
CRM: Add the HubSpot default properties that are missing on contacts, companies and deals
HubSpot: Contacts ship with about 200 default properties, including Mobile phone number, Street address, State/Region, Postal code, Time zone, LinkedIn URL, Number of times contacted and the Became a ... date for each lifecycle stage (https://knowledge.hubspot.com/properties/hubspots-default-contact-properties). Today: lib/schema/baseline.ts:69-87, lib/crm.ts:756-787 ContactInput, lib/crm-activity-dates.ts:1-12. Imports and the sync have to map these somewhere, and reps look for them. First scope: contacts get mobile phone, state or region, street address, postal code, time zone and LinkedIn URL; companies get annual revenue, type, state or region, postal code, street address and time zone; deals get deal type, next step and closed won reason. All show in forms, columns, filters, import mapping and the API. Also covers the parity rows default-company-properties, default-deal-properties.
CRM: Create the company from the contact email domain when it does not exist
HubSpot: With the setting on, HubSpot creates a company from the contact email domain and associates it automatically. Today: lib/crm.ts:816-837 findCompanyByDomain links only; no create. HubSpot teams rely on companies appearing on their own. First scope: a workspace setting (off by default) that creates the company from a business domain on contact create, using the existing enrichment to name it.
CRM: Additional email addresses on a contact
HubSpot: A contact can hold a primary email plus additional emails; all of them match incoming mail, forms and dedupe (https://knowledge.hubspot.com/records/add-multiple-email-addresses-to-a-contact). Today: One email column per contact (lib/schema/baseline.ts:74). People change jobs and write from two addresses; HubSpot keeps them on one contact and matches mail and dedupe on all of them. First scope: a secondary emails list on the contact, used by email sync matching, dedupe, merge (the losing email becomes a secondary one) and search.
CRM: Stop a second contact with the same email from being created
HubSpot: HubSpot deduplicates contacts by email: creating a contact with an email that exists is blocked in the form and updates the existing record in imports, forms and the API (https://knowledge.hubspot.com/records/deduplication-of-records). Today: createContact inserts without checking the email (lib/crm.ts:827-861); the index on email is not unique (lib/schema/baseline.ts:90). Only the CSV import and the API migration dedupe (lib/crm-import.ts:439). Email is the identity of a contact in HubSpot, and the two-way sync needs the same rule on our side or every sync creates duplicates. First scope: the create form and quick create show the existing contact and block the save; the API returns 409 with the existing id; forms, Cal bookings and chats update the existing contact; a unique index per workspace on the lowercased email once existing duplicates are merged.
CRM: Lists of companies and deals
HubSpot: Active and static lists (now called segments) for contacts, companies, deals and custom objects (https://knowledge.hubspot.com/segments/create-active-or-static-lists). Today: crm_list_members references contacts only (lib/schema/baseline.ts:227-231); lib/crm.ts:2832-3040. HubSpot segments exist for contacts, companies and deals; account-based teams keep company lists. First scope: an entity on the list (the column exists) honoured by members, dynamic filters and the list page, for companies and deals.
CRM: Export the current view with its columns and filters, to CSV or Excel
HubSpot: Export a view or all records to CSV, XLS or XLSX, choosing the view columns or all properties and including associations (https://knowledge.hubspot.com/import-and-export/export-records). Today: app/api/crm/export/route.ts:46-68 fixed COLUMNS per entity, csv or json. The export today has a fixed column list per object. First scope: export what the table shows (filters, columns incl. custom properties) or all properties, in CSV or XLSX, with the associated record names.
CRM: Import Excel files and several objects in one file, with an import history and undo
HubSpot: Import one or several objects from a file, map columns to properties, dedupe by email, domain or Record ID, and associate the objects of each row (https://knowledge.hubspot.com/import-and-export/import-objects). Today: lib/crm-import.ts:97 one entity per import; :10 and :58-92 company and contact link columns; :439, :514 dedupe. Teams leaving HubSpot export XLSX files with contacts and their companies or deals in one sheet. First scope: accept .xlsx, let one file create contacts plus companies plus deals with the associations of each row, add an Imports page with the result of each import, a downloadable error file and Delete imported records. Also covers the parity rows import-xlsx, import-history.
CRM: Select every record that matches the filter for bulk actions
HubSpot: Select rows or all records in the view, then Assign, Edit any property, Delete, Create tasks, Add to list, Enroll in sequence (https://knowledge.hubspot.com/records/bulk-edit-records). Today: lib/crm-bulk-fields.ts:10-14 BULK_FIELDS; components/crm/ContactsTable.tsx:120-137 enroll; no select-all-matching found in ContactsTable.tsx or BulkEditControls.tsx. Reassigning 2,000 contacts today means 20 pages of selecting. First scope: a Select all N records link that sends the filter to the bulk route instead of ids, with a confirmation that shows the count, plus bulk task creation.
CRM: Add is known, is any of, relative dates and AND/OR groups to filters
HubSpot: Operators depend on the property type: is any of, is none of, contains, is known, is unknown, is between, is more or less than X days ago, rolling date ranges and more (https://knowledge.hubspot.com/segments/determine-filter-criteria). Today: lib/crm.ts:159-162 TEXT_OPS, NUMBER_OPS, SELECT_OPS, DATE_OPS; :204-300 buildRuleCondition. Views and lists copied from HubSpot use these operators all the time (no owner, lead status is any of, last activity more than 30 days ago). First scope: extend buildRuleCondition with known and unknown, any of and none of, not contains, greater or equal, relative date ranges, then OR between groups of AND rules, then filters on the primary company of a contact and the contacts of a deal. Also covers the parity rows filter-groups, filter-associated.
CRM: Make saved views hold columns and sort, update in place and share with a team
HubSpot: Saved views keep filters, columns and sort; they can be updated, cloned, pinned as tabs and set as default (https://knowledge.hubspot.com/records/create-and-manage-saved-views). Today: lib/crm.ts:3050-3080 create, list and delete only; app/api/crm/views/route.ts has no update; lib/schema/baseline.ts:244-251. A HubSpot team rebuilds its views on day one of a migration. First scope: store columns, column order and sort in the view (server side), an Update view action, a visibility of private, team or everyone, and drag to reorder columns. Also covers the parity rows view-columns, view-sharing.
CRM: Load the whole timeline and filter it by type, person and text
HubSpot: The timeline loads older activity as you scroll, grouped by month, with no cap (https://knowledge.hubspot.com/records/filter-activities-on-a-record-timeline). Today: app/[locale]/app/crm/contacts/[id]/page.tsx:255-256 limit: 100; no load-more in components/crm/Timeline.tsx. After a migration records carry years of history and the page stops at the latest 100 items. First scope: cursor pagination in listTimeline with a load-more at the end, a multi-select of activity types, a filter by person or team, a search box, and formatting (bold, lists, links) in notes. Also covers the parity rows timeline-filters, rich-text-notes.
CRM: Rebuild the record page in three columns (properties, activity, associations)
HubSpot: Every record has a left sidebar (actions and About this record properties), a middle column (Overview and Activities tabs) and a right sidebar (association cards and tools) (https://knowledge.hubspot.com/records/work-with-records). Today: components/crm/recordTab.ts:1 RECORD_TABS; app/[locale]/app/crm/contacts/[id]/page.tsx:140-246 header, :263-380 activity tab with aside. This is the page a sales rep lives in. First scope: on contacts, companies and deals at desktop width, a left column with the record name, the action buttons and the editable About properties (the existing PropertiesPanel in compact mode), the timeline in the middle and association cards (companies, deals, contacts, lists, files) on the right; at 390px the columns collapse to the current tabs. Also covers the parity rows record-sidebar-inline-edit.
CRM: Propose stakeholders and pain points from deal notes and call transcripts
HubSpot now scans notes and call or meeting transcripts on a deal and adds stakeholders and pain points as structured signals on the associated company record (https://martech.org/hubspots-june-2026-updates-agents-get-more-access-revenue-hub-starts-connecting-the-dots/). We have an AI summary card and call summaries in lib/crm-ai.ts, but their output stays as text on the timeline and nothing is written to properties or associations. A first scope is a button on the deal that proposes people mentioned in notes as contacts with a role label and a short list of pain points, applied only after the user confirms each one.
CRM: Add a unique-value option to custom properties to block duplicate IDs
HubSpot custom properties can be marked as unique identifiers so two records cannot share the same value, which keeps external IDs and tax numbers clean (https://knowledge.hubspot.com/properties/create-and-edit-properties). Our custom field definitions in lib/crm-custom-fields.ts have no uniqueness rule, so the same external ID can be saved on two contacts and only the duplicate finder catches it later. A first scope is a unique flag on text and number fields that rejects the save in the UI, the CSV import and API v1 with a message naming the record that already has the value.
CRM: Group custom properties into named sections
HubSpot organizes properties into property groups that appear as sections in forms, record pages and imports (https://knowledge.hubspot.com/properties/create-and-edit-property-groups). Our custom fields in crm_custom_fields have a name, label, type and position with no grouping, so a workspace with 20 fields gets one flat list in components/crm/CustomFieldsPanel.tsx. A first scope is an optional group name on each field, shown as collapsible sections on the record page and the settings screen, with a migration that keeps existing fields ungrouped.
CRM: Let admins arrange the cards and properties of the record sidebar
HubSpot admins customize record layouts under Settings > Objects > Record Customization, adding cards and choosing which properties show in the About card, and each user can reorder cards (https://knowledge.hubspot.com/object-settings/customize-records). In our CRM the contact, company and deal pages show a fixed set of panels under app/[locale]/app/crm. Teams with many custom fields end up scrolling past properties they never use. A first scope is a per-object list of visible properties and their order for the side panel, stored per workspace, with a reset to default.
CRM: Add calculated rollup properties (count, sum, min, max) from associated records
HubSpot lets admins create rollup properties that compute count, sum, min, max or average over associated records, optionally filtered by association label, plus calculation properties built from an equation or time-between logic (https://knowledge.hubspot.com/properties/create-calculation-properties). Our custom fields in lib/crm-custom-fields.ts are all typed inputs entered by hand, and companyRollup in lib/crm.ts is a fixed set of totals. A small team wants 'total won revenue' on a company or 'open deals' on a contact as a column and a filter without building a report. A first scope is a read-only property type on companies and contacts with count and sum over associated deals, recomputed when a deal changes, usable as a column, sort and filter.
CRM: Separate the permission to create records from the permission to edit
HubSpot admins can allow a role to edit records without letting it create new ones (https://knowledge.hubspot.com/user-management/hubspot-user-permissions-guide). Our visibility rules in lib/crm-visibility.ts and lib/crm-field-perms.ts control what a person sees and which fields they change, not whether they can add records. This stops interns or guests from filling the CRM with duplicates. First scope: a per-role create toggle for contacts, companies and deals checked by the POST routes under app/api/crm.
CRM: Add formula properties that calculate from other properties
HubSpot calculation properties compute a number, date or text from other properties on the record (https://knowledge.hubspot.com/properties/create-calculation-properties). We only have stored custom fields in lib/crm-custom-fields.ts. A small team uses this for margin, days to close or weighted amount without a report. First scope: a formula field type with arithmetic over number and currency fields, computed on read, usable in table columns and filters.
CRM: Set default values for properties on new records
HubSpot admins can set a default value per property that applies on manual creation, workflows and the API (https://knowledge.hubspot.com/object-settings/set-default-property-values). Our custom fields have no default, so every new contact starts blank and people forget the same field. First scope: a default per custom field and per core property such as source or priority, applied in createContact, createCompany and createDeal in lib/crm.ts when the value is missing.
CRM: Make custom properties required on the create form
HubSpot properties can be marked required so a record cannot be created without them (https://knowledge.hubspot.com/object-settings/set-required-properties-for-records). Our custom fields in lib/crm-custom-fields.ts only support types and options, and stage rules in lib/crm-stage-rules.ts cover deals entering a stage, not creation. For a small team this keeps owner, source or region from being empty in reports. First scope: a required flag per custom field, enforced in the create forms and the v1 API with a clear error.
- 0
CRM: Clone a deal with its associations from the record menu
HubSpot lets you clone a deal, contact or company from the record actions menu (https://knowledge.hubspot.com/records/clone-records). We had no way to copy a record, so repeat deals meant retyping every property. First scope: Clone deal in the More menu at app/[locale]/app/crm/deals/[id]/page.tsx, copying properties, contacts and companies but not notes, tasks or line items; contacts and companies come later.
- 0
CRM: Import a whole HubSpot or Pipedrive account by API, with a preview and safe re-runs
Teams leaving HubSpot or Pipedrive need owners, custom properties, pipelines, companies, contacts, deals, associations and activities to come over in one go, not CSV by CSV. Paste a private app or API token, review counts and owner matching, then import in resumable chunks. Re-running updates instead of duplicating.
- 0
CRM: Make the whole board column a drop target and move deals between stages with the keyboard
In HubSpot and Pipedrive you drop a deal anywhere in a column. Our board only accepts drops on the card list (updateDrag in components/crm/DealsBoard.tsx looks for .kb-cards), so releasing over the column header, the '+ Add deal' button or the empty space below silently puts the deal back. There is also no keyboard way to change stage from the board (reaching a card took 35 Tab presses). First scope: treat the whole column as the drop zone (append at the end when below the last card), highlight it while dragging, show a toast with undo after the move, and add arrow-key focus between cards plus Shift+←/→ to move a focused card one stage. Priority: medium. Effort: S. Compared with HubSpot deal board and Pipedrive pipeline view.
- 0
CRM: Let workspaces define their own objects with fields, associations and views
Attio is built on custom objects from its free plan (3 objects free, 12 on Pro: https://attio.com/pricing); HubSpot reserves them for Enterprise. Teams that track partners, properties, candidates or subscriptions next to deals have nowhere to put them in our CRM and fall back to custom fields on companies. First scope: an object editor (name, icon, fields from the existing custom field types), records with the same table, record page, timeline and associations to contacts, companies and deals, ⌘K search, CSV import, API under /api/v1/crm/objects. Priority: medium. Effort: L. Compared with Attio objects and HubSpot custom objects.
- 0
CRM: Add playbooks with call scripts that write answers back to properties
HubSpot playbooks give reps a script or qualification guide on the record and save answers as notes or properties (5 on Starter, 5,000 on Pro with property embedding: https://www.hubspot.com/pricing/sales/starter). We have no guided content on the record. First scope: playbooks built from Docs pages with embedded property questions (text, select, number), opened from the record header or the call composer, answers saved to the record and a note on the timeline, usage counts per playbook. Priority: medium. Effort: M. Compared with HubSpot playbooks.
- 0
CRM: Ship a Gmail / Chrome extension that shows the contact and logs emails from the inbox
HubSpot Sales Extensions work inside Gmail, Outlook and any web page: contact panel, log and track toggles, templates and sequences from the compose window (https://www.hubspot.com/products/sales, HubSpot Sales Extensions). Our tracking, templates and sequences only work from the CRM timeline. First scope: a Chrome extension with an API key (crm scopes) that shows the sender's contact, company, open deals and last activity in a Gmail side panel, a 'Create contact' button, and insert template / enroll in sequence from compose. Priority: medium. Effort: M. Compared with HubSpot Sales Extension and Pipedrive's Chrome extension.
- 0
CRM: Add forecast categories and a per-rep forecast submission with manager roll-up
HubSpot's forecasting tool lets each rep put deals in categories (pipeline, best case, commit, closed) and submit a number per period, with team hierarchies in Pro (https://www.hubspot.com/pricing/sales/starter, Forecasting). Our forecast is the probability-weighted amount in reports and the board header; there is no commit/best case and no way for a rep to submit or a manager to adjust. First scope: a forecast category property on deals (defaulted from the stage), a Forecast page per month or quarter grouped by owner and sales team with commit / best case / pipeline totals against quotas, and a submitted value per rep with history. Priority: medium. Effort: M. Compared with HubSpot forecasting and Pipedrive revenue forecast.
- 0
CRM: Turn Cal meetings into a recap on the timeline (transcript, summary, next steps)
HubSpot Notetaker does meeting prep, recap and conversation intelligence with tracked terms (https://www.hubspot.com/pricing/sales/starter, Notetaker section). Our Cal bookings already create a meeting activity on the contact, but after the call nothing lands there unless someone writes a note. First scope: upload or link a recording (or import a transcript from the video provider) on the meeting activity, generate a summary with next steps and suggested property updates when AI is enabled, and offer to create the follow-up tasks; later, a bot that joins the call. Priority: medium. Effort: L. Compared with HubSpot Notetaker and Attio Call Intelligence.
- 0
CRM: Add a daily work queue that steps through due tasks and sequence steps one by one
HubSpot's Prospecting / Sales Workspace gives reps one screen with today's tasks, sequence steps and leads to work, and a mode that opens each task in order (https://www.hubspot.com/products/sales, Prospecting Workspace; https://vantagepoint.io/blog/hs/hubspot-sales-workspace-update-april-2026-preparation-guide). Our Tasks page has Overdue, Today and Upcoming buckets, but each task opens on its own and manual sequence steps aren't mixed in. First scope: a 'Start queue' button on Tasks that opens the first due item with the contact's timeline beside it, complete or snooze with a key, auto-advance to the next, and a counter of what's left; include manual sequence steps and calls due. Priority: high. Effort: M. Compared with HubSpot Sales Workspace and Pipedrive's activity focus.
- 0
CRM: Call from the browser with recording, transcription and automatic logging
Sales Hub Starter includes 500 calling minutes, a HubSpot number and transcription; Pro raises it to 3,000 minutes and 3 numbers (https://www.hubspot.com/pricing/sales/starter). We only open tel: and wa.me links and ask for an outcome afterwards (lib/crm-calls.ts). First scope: bring-your-own Twilio account (keys in Settings), click-to-call from the record header and the phone cell, call widget with mute and notes, recording stored as a file on the call activity, transcription and a short summary when AI is enabled, outcome and duration logged on the timeline and counted by lead scoring and reports. Priority: high. Effort: L. Compared with HubSpot calling, Pipedrive Caller and Attio Call Intelligence (Pro).
- 0
CRM: Sync and send email through Outlook / Microsoft 365, with an IMAP/SMTP fallback
HubSpot connects Gmail or Outlook inboxes from Starter (https://www.hubspot.com/products/sales, Sales Extensions for Gmail and Outlook). We only sync and send through Gmail (lib/crm-email-sync.ts), and until the Google app is verified for gmail.readonly only test users can connect. A team on Microsoft 365 gets no email on the timeline, no sequences sent as themselves and no reply detection. First scope: Microsoft Graph OAuth (Mail.Read, Mail.Send) reusing the Gmail sync shape (incremental delta, thread grouping, contact matching, reply detection for sequences); then a generic IMAP/SMTP connection with app passwords as a fallback that does not depend on Google's verification. Priority: high. Effort: L. Compared with HubSpot Sales Hub, Pipedrive (email sync on Growth) and Attio (email accounts per user).
- 0
CRM: Show records as cards on phones with one-tap call, WhatsApp and note, and make the CRM installable
HubSpot ships a mobile app on every plan, and reps log calls and notes from the phone (https://www.hubspot.com/pricing/sales/starter lists the mobile app in Starter). At 390px our contacts, companies and deals tables keep the desktop columns and scroll sideways inside their wrapper: on Contacts only Name and Email fit, and row actions sit off-screen. The board shows one and a half columns. First scope: below 520px render list rows as cards (name, company, lifecycle or stage, owner, next activity) with one-tap call, WhatsApp (reuse PhoneTouch outcomes) and quick note; a stage picker on deal cards instead of drag; a web app manifest so the CRM installs on the home screen. Offline reading can come later. Priority: high. Effort: M. Compared with HubSpot Sales Hub Starter/Pro, Pipedrive and Attio mobile apps.
- 0
CRM: Show company logos and prefill basic company data from the domain
Attio enriches company records from the domain on its Free plan, logo included, as soon as a record is created (https://attio.com/help/reference/managing-your-data/enriched-data), while HubSpot moved enrichment to paid Breeze Intelligence and turned it off by default (https://knowledge.hubspot.com/records/get-started-with-data-enrichment). We store name, domain, industry and employees typed by hand (lib/schema/baseline.ts:92) and show no logo anywhere. Logos make lists and the board scannable, and free enrichment is a visible differentiator against HubSpot. First scope: logo from the domain favicon (cached, no third-party tracking) on company rows, cards and headers, plus an optional fetch of the site's title and meta description into empty fields. Priority: low. Effort: S. Compared with HubSpot.
- 0
CRM: Attach files to notes and records, not only to tasks
HubSpot has an Attachments card on every record and an attach button in the note and activity editor (https://knowledge.hubspot.com/records/add-and-remove-attachments-from-records). We only store files for tasks (crm_task_files, components/crm/TaskFiles.tsx); notes are a plain textarea with no attachments (components/crm/Timeline.tsx:380), and contacts, companies and deals have no files panel. Signed contracts, briefs and screenshots end up in Drive with no link to the deal. First scope: generalize crm_task_files into activity and record attachments, an attach icon in the note composer, and an Attachments side panel on record pages that respects record visibility. Priority: low. Effort: M. Compared with HubSpot.
- 0
CRM: Add an AI summary card on contact, company and deal pages
HubSpot's Breeze record summary card generates on record load from activities, notes and ownership, can be refreshed, and is also a workflow action (https://knowledge.hubspot.com/records/summarize-records). Our only AI touch in the CRM is 'Draft with AI' for emails (components/crm/Timeline.tsx:432, app/api/crm/emails/draft); there is no record summary. Before a call, a founder wants 'where is this deal and what was promised' without scrolling a long timeline. First scope: when AI is enabled, a cached summary card above the timeline built from the last N activities, emails and stage changes, with a refresh button and a 'next step' suggestion; no automatic writes. Priority: low. Effort: M. Compared with HubSpot.
- 0
CRM: Log calls and WhatsApp touches from phone links with configurable outcomes
HubSpot lets admins define up to 30 custom call and meeting outcomes used when logging, in reports and in workflows, and calls can be started from a record's phone number (https://knowledge.hubspot.com/calling/create-custom-call-and-meeting-outcomes). We render phone numbers as plain tel: links (components/crm/ContactsTable.tsx:247, components/crm/RecordPreview.tsx:237) that leave no trace, and call outcome is free text (lib/crm-schema.ts:195), so it cannot be filtered or reported. HubSpot has no native WhatsApp logging (only third-party apps), and our LatAm-heavy users sell over WhatsApp daily. First scope: a workspace list of call outcomes, a 'Log this call?' prompt after clicking tel:, a WhatsApp (wa.me) action next to phones that opens the chat and logs a 'WhatsApp' touch, and outcome as a report dimension. Priority: medium. Effort: S. Compared with HubSpot.
- 0
CRM: Require chosen properties before a deal can enter a stage
HubSpot pipelines let admins mark properties as required per stage (conditional stage properties), so a deal cannot move to 'Proposal' without amount and close date; this sits in Sales Hub Professional (https://knowledge.hubspot.com/object-settings/set-up-and-customize-pipelines). Our crm_stages only store name, probability, position and won/lost flags (lib/schema/baseline.ts:119), and the move endpoint accepts any drag (app/api/crm/deals/[id]/move). Forecasts and reports are only as good as amounts and close dates, and small teams have no ops person cleaning data. Offering this for free is a cheap differentiator. First scope: required_fields JSON on crm_stages edited in PipelinesEditor, a modal on board drag or stage change that asks for missing values, enforced server-side in the move route and the v1 API. Priority: medium. Effort: M. Compared with HubSpot.
- 0
CRM: Count synced emails toward deal rotting and make the threshold per stage
Pipedrive lets each stage define its own 'Rotting in (days)', and sending or receiving linked emails, notes, files and done activities all reset the clock (https://support.pipedrive.com/en/article/the-rotting-feature). Our board flags a deal as rotting after a hard-coded 14 days (components/crm/DealsBoard.tsx:373), and idle time comes only from crm_activities with that deal_id or the deal's updated_at (lib/crm.ts:1531, app/[locale]/app/crm/deals/page.tsx:86). Inbound replies stored by Gmail sync never create activities (lib/crm-email-sync.ts), so a deal with an active email thread is still marked rotting, which teaches reps to ignore the badge. Fix: include the latest crm_emails sent_at for contacts associated to the deal in last activity, and add an optional rotting_days column on crm_stages editable in PipelinesEditor. Priority: medium. Effort: S. Compared with HubSpot.
- 0
CRM: Add multi-select, URL, phone, currency and user field types to custom fields
HubSpot properties support single and multiple checkboxes, dropdowns, radio, number with currency formatting, date, file, HubSpot user and more (https://knowledge.hubspot.com/properties/property-field-types-in-hubspot). Our custom fields accept only text, number, date, select and boolean (lib/crm-schema.ts:276, components/crm/customPropFields.ts). Common small-team fields like 'Products of interest' (multi), 'LinkedIn URL', 'Secondary phone' or 'Account manager' (a user) end up as free text that cannot be filtered or clicked. First scope: multiselect (JSON array, 'contains any' filter), url and phone (clickable), currency-formatted number, and user (member picker, filterable like owner). Priority: medium. Effort: M. Compared with HubSpot.
- 0
CRM: Support @mentions in notes and tasks with in-app and email notifications
HubSpot lets users @mention teammates in activities and comments on contacts, companies and deals, and the mentioned user gets a notification if they can see the record (https://knowledge.hubspot.com/records/mention-a-user-on-a-record). Our note and task composer is a plain textarea (components/crm/Timeline.tsx:380) with no mention parsing, although lib/notifications.ts already exists and is used by lead assignment (lib/crm-assignment.ts:152). Handing a deal to a teammate today means pinging them in another tool. First scope: @ autocomplete of workspace members in the timeline composer, store mentions on the activity, notify via createNotification respecting record visibility (lib/crm-visibility.ts). Priority: medium. Effort: M. Compared with HubSpot.
- 0
CRM: Let tasks repeat on a daily, weekly or monthly schedule
HubSpot tasks have a 'Set to repeat' option that creates the next task in the series, also exposed through a Task series API (https://knowledge.hubspot.com/tasks/create-tasks, https://developers.hubspot.com/docs/api-reference/latest/crm/activities/task-series/guide.md). Our tasks are single crm_activities rows with due_at and done only (lib/schema/baseline.ts:159), and grepping lib/crm*.ts and components/crm finds no recurrence. Small teams use recurring tasks for account check-ins, monthly invoicing calls and renewals. First scope: a repeat rule (every N days/weeks/months) on the task form; when a task is completed, create the next one with the same owner, record links and project. Priority: medium. Effort: S. Compared with HubSpot.
- 0
CRM: Find and merge duplicate companies by domain and name
HubSpot merges any two records of the same object, companies and deals included, keeping activities and associations (https://knowledge.hubspot.com/records/merge-records). We only detect and merge contacts (app/api/crm/contacts/duplicates, app/api/crm/contacts/merge); app/api/crm/companies has no duplicates or merge route. Companies get duplicated easily through CSV imports, forms and Chat (company by name), and duplicate companies split deal roll-ups and the hierarchy. First scope: duplicate groups by normalized domain or exact name, a merge that moves contact/deal associations, child companies, activities, tags and custom values, reusing the contact merge pattern. Priority: medium. Effort: S. Compared with HubSpot.
- 0
CRM: Show owner and custom fields as sortable columns in record tables
HubSpot index views let you add any property, default or custom, as a column and sort or filter by it, and the 2026 index redesign adds conditional highlighting on top (https://offers.hubspot.com/streamlined-index-views-resource-center). Our column toggle only exposes a fixed set: contacts get name, email, phone, company, lifecycle, lead status, source, score, tags, created (components/crm/ContactsTable.tsx:50-59), with no owner column and no custom fields in ContactsTable or DealsTable, even though the filter builder already supports custom fields (lib/crm.ts:187). Teams that add a 'Plan' or 'Region' field cannot see it in the list without opening each record. First scope: owner column on all three tables plus one column per custom field in ColumnToggle, persisted in saved views, sortable via the existing custom-field SQL expression. Priority: high. Effort: S. Compared with HubSpot.
- 0
CRM: Track last contacted, last activity and next activity date on every record
HubSpot maintains Last activity date, Last contacted, Next activity date and Number of times contacted automatically on each contact (https://knowledge.hubspot.com/properties/hubspots-default-contact-properties), and Pipedrive builds its workflow around a Next activity date with a warning on deals that have nothing scheduled (https://support.pipedrive.com/en/article/activities). We only compute last_activity_at for deals on the board query (lib/crm.ts:1531); contacts and companies have no such fields, the contacts table columns stop at created (components/crm/ContactsTable.tsx:50-59), and the board card shows no next step. For a small team the daily question is 'who have I not talked to and what is my next step', which we cannot answer from a list. First scope: derived last_contacted_at, last_activity_at, next_activity_at on contacts, companies and deals (updated on activity/email write), sortable and filterable columns, and a 'no next activity' marker on board cards. Priority: high. Effort: M. Compared with HubSpot.
- 0
CRM: Bulk edit any property and reassign owner on contacts, companies and deals
HubSpot's index pages let you select records and edit any property value, assign owners or add to segments in one action (https://knowledge.hubspot.com/records/bulk-edit-records). Our contacts and companies bulk endpoints only accept set_lifecycle and delete (app/api/crm/contacts/bulk/route.ts, app/api/crm/companies/bulk/route.ts), and the deals table bulk bar only offers tags (components/crm/DealsTable.tsx:245). When a rep leaves or territories change, a small team has to reassign owners one by one. First scope: a 'Set property' bulk action (owner, lead status, source, stage, close date and custom fields) on all three tables, recorded in crm_property_events and firing the same workflow triggers as single edits. Priority: high. Effort: M. Compared with HubSpot.
- 0
CRM: Add a recycle bin that restores deleted records and activities for 90 days
HubSpot keeps deleted contacts, companies, deals and activities in a restore tool for 90 days, filterable by date, user or workflow (https://knowledge.hubspot.com/records/restore-deleted-records). We hard-delete: deleteContact and bulkDeleteContacts run DELETE FROM crm_contacts directly (lib/crm.ts:767, :886), there is no deleted_at column on any CRM table (lib/schema/baseline.ts), and cascades wipe associations, emails links and enrollments. One mis-click on bulk delete (up to 500 rows) is unrecoverable for a team without a DBA. First scope: deleted_at on contacts, companies, deals and activities, exclude soft-deleted rows in list/search/report queries, a Settings > Deleted records page with restore, and a daily cron purge after 90 days. Priority: high. Effort: M. Compared with HubSpot.
- 0
CRM: Keep synced emails, enrollments and form history when merging contacts
HubSpot merges keep activities, associations and most property values from both records (https://knowledge.hubspot.com/records/merge-records). Our mergeContacts in lib/crm.ts moves contact_id on crm_emails but never repoints crm_email_contacts, and then deletes the dropped contact, so its rows cascade away (lib/schema/migrations.ts:995) and those emails disappear from the kept contact's timeline, which reads through crm_email_contacts (lib/crm-email.ts:777) and also feeds lead scoring. Sequence enrollments cascade-delete, form submissions lose their contact (ON DELETE SET NULL), property history stays orphaned, and empty fields on the kept contact are not filled from the dropped one. A small team merging a duplicate silently loses its email history. Fix: repoint crm_email_contacts, crm_sequence_enrollments, crm_form_submissions and crm_property_events inside the same transaction, fill blank fields from the dropped record, and add a regression test next to tests/unit/crm.test.ts 'merge de contactos'. Priority: high. Effort: S. Compared with HubSpot.
- 0
CRM: automatic Gmail sync, templates and open/click tracking
Emails sync in the background, templates with variables, and opens and clicks on the contact timeline.
- 0
CRM: follow-up sequences
Multi-step email and task sequences that stop when the contact replies or books a meeting.
- 0
CRM: products, line items and quotes
A product catalog, line items on deals and a public quote page your customer can accept.