PRIMA CRM

These notes cover every PRIMA CRM release up to 1.6.1, newest first. Each entry describes what changes for you. The notes leave out changes that only affect how GenAI Skills Academy builds and maintains the product.

1.6.1

Released on 14 October 2026, this version fixes problems found while writing the user documentation. The database schema does not change.

• Failed calls report as failures. A tool error used to reach Claude as a success. Every error now carries the error marker, so Claude can tell a call failed.
• Approve and reject with the short ID. crm_sync accept and discard now take the eight-character ID that crm_sync review shows, or the full ID. A prefix that matches nothing or more than one item returns an error and changes nothing. See Email, Calendar and Meeting Sync.
• Sync status tells you what is built. crm_sync status used to report a connected Proton Mail, Google Calendar or Zoom account as Active. No provider fetch code exists in this release, so these now report as Not built yet with “Nothing syncs yet”.
• The legacy dormant status is refused. crm_company add and update now reject dormant and point you to active, past and crm_company stale. Search still finds rows that carry it, so you can correct them.
• Correct requirement. PRIMA CRM needs only the AI Business OS project register, .claude/state/state.json, which the installer puts in place and /setup fills in. The README and start-up message used to say it needed PRIMA Project Management.
• Install contents. The package now includes start.sh and the scripts/ folder, which the install and the dashboard need.
• Documentation. The README now explains how the server finds your workspace, gives the dashboard command with the installed script path, and lists the sync states.
• Licence and support. The product now ships the GenAI Skills Academy Software Licence, and the README states that it is built and tested on macOS and that support is purchased separately.

1.6.0

Released on 15 September 2026, this version stops treating every company as a sales prospect. It also ships the review, lead detection and dashboard work held back since 1.5.0.

• Relationship on every company. Each company now has a relationship, which is client, supplier, partner, internal or other. Where you have not set one, the CRM works it out from the company’s project links. See Companies.
• Stale replaces dormant. A company is stale when it is active and its last interaction is older than its contact cadence. Default cadences are 30 days for clients, 60 for partners, 90 for suppliers and never for internal and other, and you can override them per company. Leads and past companies are never stale, and crm_company stale and crm_contact stale list what has lapsed. See Stale Clients and Contact Cadence.
• Engagements replace deals. crm_engagement replaces crm_deal and adds a type, which is sale, purchase, partnership or other. Only sales count in the pipeline and won totals, and purchase engagements show as commitments on the company profile. See Engagements.
• Setup seeds every named company. crm_setup now seeds a company from every project that names one and is not archived, whatever its category, and links it to the project.
• Review before anything is written. Every item an automated sync finds now passes a check first. A known contact’s email writes at once, somebody unknown at a known company waits for your review, and newsletters and automated senders are discarded. Contacts are never created during a sync.
• Lead detection. A message from an unknown sender that looks like a person making contact now surfaces as a possible new lead, with the reasons shown. Approving it creates the company, the contact and the interaction.
• Sync not yet connected. No release up to 1.6.1 includes the code that fetches from an email, calendar or meetings service, so the two checks above apply once that code ships. See 1.6.1.
• CRM dashboard. A generator writes one HTML file with Overview, Pipeline, Clients, Needs Attention, Activity and Sync tabs. See The CRM Dashboard.
• Won and lost dates. You can now set won_date and lost_date, and an engagement created at won or lost gets a date, so it counts in won-this-year figures.
• Renamed summary fields. crm_summary now reports open_sales, stale_companies and open_commitments_value.
• One tool fewer. crm_dormant is removed and its work moves to the stale actions, which leaves PRIMA CRM with nine tools.

1.5.0

Released on 14 September 2026.

• crm_sync status. A new tool reads .claude/config/integrations.json and reports which email, calendar and meetings services your workspace has connected, and which need repair. It writes nothing and makes no network calls.
• Untouched settings read as unanswered. Template values in integrations.json no longer show up as connected services.

1.4.0

Released on 14 September 2026.

• No duplicate interactions from a sync. crm_interaction log now accepts the source system’s own ID for an email, event or meeting, and the same item is never written twice. Interactions you log by hand are not affected.
• Sync run records. The CRM now records each automated pass with counts written and skipped, so the next pass starts from the last successful one.

1.3.2

Released on 2 September 2026.

• Merging companies needs confirmation. crm_company merge now runs as a dry run that reports what would move. Nothing changes until you repeat the call with confirm=true.
• Merging keeps project link details. Where both companies linked to the same project, the merge now keeps the department, relationship and notes from both links.
• Status filters fixed. Filtering companies by status now returns the right rows, and an unknown status returns an error.

1.3.1

Released on 2 September 2026.

• Dormant company lists work. The list of companies with no recent contact failed with an error in every earlier version. It now works, and filtering contacts by company status takes effect.

1.3.0

Released on 2 September 2026.

• Merge duplicate companies. crm_company merge moves every contact, interaction, engagement and project link from a duplicate record to the one you keep, then deletes the duplicate. Contacts move as they are, so you decide whether two similar contacts are the same person.

1.2.0

Released on 2 September 2026.

• Project relations. A new tool, crm_project_relation, records how one project connects to another, with the types informs, supersedes, shares-scope and part-of. See Projects and Relations.
• Relations on the company profile. crm_company get now shows how the company’s projects relate to each other and to other companies’ projects.
• Correct version number. The server now reports its own version.

1.1.0

Released on 27 August 2026.

• Link companies to projects directly. crm_company gains link, unlink and for_project, with a department, relationship and notes on each link.
• Live project state on the company profile. crm_company get now shows each linked project’s current status, task progress, last worked date and latest action, read at the moment you ask.
• Both state formats. The CRM reads project state whether your workspace keeps it in one state.json file or splits it into separate project files.

1.0.1

Released on 10 April 2026.

• Documentation correction. The README described four command integrations that did not exist. It now marks them as planned.

1.0.0

Released on 13 March 2026, the first release provided tools for companies, contacts, deals, interactions, segments, dormant companies, a summary and setup. crm_setup seeded the CRM from client projects in state.json.