What's New

v1.0 — HotCRM, the CRM that rewrites itself

The first launch. HotCRM v1 is for teams who are sick of waiting on their CRM vendor to add the field they need next quarter. You add the field; the AI uses it the next time you ask. Three things in this release make it different from every CRM you've used before.

✨ Wow #1 — Live schema, live AI

Add a field in the admin console. Ten seconds later, ask the AI assistant a question about it. It already knows. No retraining, no restart, no redeploy — the platform re-reads metadata on every agent turn and the Copilot's describe_object tool returns your new field as soon as it's saved.

Try it in 30 seconds with the script we ship:

HOTCRM_TOKEN=... ./scripts/wow1-live-schema.sh

💬 Wow #2 — Chat-first record pages

Open any account, opportunity, case, or contract. The Copilot is always one click away in the floating chat bubble — and it already has the live schema and this record in scope. Ask:

• "Give me the full picture of this account."
• "Draft a follow-up email to the primary contact."
• "What are the next 3 actions I should take?"

The discussion feed at the bottom of every record page captures the back-and-forth so it stays as institutional memory, not a Slack thread that nobody can find next quarter.

🛠️ Wow #3 — Honest about what's in the box

We don't pretend the platform does things it doesn't. The natural- language flow builder is a platform capability we've designed (ADR-0010) and is on the roadmap, but doesn't ship in v1. What does ship: every business object, view, page, dashboard, role, and seed record is a plain TypeScript file you can edit, diff, and commit — and the AI sees those edits the moment you save.

What's in v1.0

• 15 business objects across Sales / Service / Marketing / Revenue.
• Sales Copilot with 5 skills: live data, lead qualification, email drafting, revenue forecasting, customer 360°.
• Executive Dashboard + 9 pre-built reports.
• Slimmed nav — 5 core surfaces (Sales, Service, Insights, Approvals) so a new user can find their way around in 30 seconds.
• Demo seed — Acme Corporation is a fully-formed customer (3 opps, 2 cases, 1 contract, 3 narrative tasks, a 1KB strategic brief) so the Copilot has real material to summarize the moment you log in.

Ready to try? pnpm install && pnpm demo:reset && pnpm dev, then open http://localhost:4001 and create the first admin account.

v3.0.0 — Latest release

HotCRM 3.0.0, running on ObjectStack 17.1.0 across every @objectstack/* package. The app manifest declares the matching ^17.1.0 protocol range, so a runtime on a different protocol major refuses the load up front with a structured diagnostic instead of failing deep in a schema parse.

This page does not keep a second release table. The release-by-release history is CHANGELOG.md in the repository, compiled from the .changeset/ entry every pull request adds. The versions between v1.0 and 3.0.0 are recorded there and are deliberately not re-listed here — a hand-maintained copy of that history is exactly how this section came to advertise a "v5.0" that was never an app version, on a platform major that never shipped it.

Upgrading from 2.x — Owner is now one field

3.0.0 is a major because reassigning Owner now moves access. Before it, every business object carried two owners: the Owner on forms, views and reports, and a separate hidden column the platform used for every access decision. Nothing kept them in step — changing Owner moved the record in every list and report and moved no access at all. The previous owner kept it; the new owner never got it.

HotCRM now has exactly one Owner: the platform's ownership column.

What this means for an existing deployment:

• Reassignment is gated separately from edit rights. Because it really does transfer access, changing Owner is its own permission rather than a side effect of being able to edit the record.
• Run the backfill once. Deployments where somebody reassigned an Owner under 2.x have the two columns out of step; pnpm backfill:owner reconciles them. It never blanks an existing owner and is safe to re-run — and it needs an administrator account, because a bulk transfer is what it performs. If nobody ever reassigned an Owner, the columns already agree and the backfill reports zero divergences.

The full entry — including the per-persona reassignment table — is the Major Changes section of CHANGELOG.md.

Where the current shape of the product is written down

Rather than restate the inventory here — where nothing would check it — each area is described on the page that owns it, and those pages are held to the registered metadata by the repository's docs-drift guard:

• What ships in the box — Introduction.
• Dashboards, reports, and the datasets underneath them — Analytics.
• Profiles, positions, and sharing — Sharing & security.
• The AI surface — AI assistant. HotCRM ships skills only; they attach to the platform assistant, and the app defines no agent of its own.

Roadmap

What we're working on next:

• Forecasting AI improvements — better confidence intervals, what-if scenarios.
• Service workforce management — agent scheduling and capacity planning.
• Marketing journey designer — multi-step nurture campaigns.
• Mobile app — native iOS and Android for field reps.
• More connectors — Slack, Microsoft Teams, Google Workspace, HubSpot import.

Suggestions? File an issue on GitHub.