What shipped, and what we wrote down

Surfaces around the agreement

The same list the splash page names. A surface appears here because it ships, not because it is this week's news.

• Tasks & projects — Turn agreements into action with an Overview dashboard, drag-to-reschedule Gantt timelines and a WIP-aware Kanban board.
• Two-way Google Calendar — Deadlines, signings and meetings sync both ways with Google Calendar — with conflict detection and per-calendar controls.
• AI assistant — Draft clauses, summarize long threads and surface risk in plain language, grounded in your own documents.
• Analytics — See cycle times, negotiation velocity and signing throughput so you can find and fix every bottleneck.
• Email & contacts — A built-in inbox and lightweight CRM keep every counterparty, thread and relationship in context.
• Rooms & mobile — Organize deals into secure rooms and keep momentum on the go with a fast, native-feeling mobile app.

From the blog

Newest first. Each note is a real post; this page does not reprint it.

• Welcome back: Paqt’s AI-powered app is here — A celebratory launch note for the new Paqt — chat, documents, negotiation, signing, and an AI assistant that lives where the work happens.
• Why chat matters for business — Email still has a job. For live deals, chat is faster, clearer, and easier to turn into a signed agreement — if the messenger is built for work.
• AI agents in messaging: why they belong in the chat — Agents that sit in the same thread as your counterparties can draft, summarize, and follow through — with Paqt’s room context, not a blank prompt box.
• AI agents and permissions: guardrails before magic — Powerful agents need the same access control as a junior teammate — roles, room permissions, and a clear line for what AI is allowed to do.
• One hub for messaging, documents, negotiation, and signing — Paqt’s unique bet: the chat is the deal. Create, negotiate, and sign in the same place you already talked.

A surface is not a ship date

The splash band names what exists. The blog is where a change gets a date and an explanation. Mixing them into one invented changelog is how this page would go stale.

• Surfaces — Tasks, calendar, the assistant, analytics, email and rooms. Generated from the same module the splash band reads, so the two cannot disagree.
• Dated notes — The published blog, newest first. A note exists here because it exists at /blog, not because someone copied a title onto a marketing page.
• The agentic work — The assistant, bot negotiation and MCP have their own pages. They are not restated here as if they had just landed.

What this page will not do

A what's-new page that restates every feature as if it were this week's news is a changelog nobody can trust.

• No roadmap: If it is not in the product, it is not on this page
• No roadmap: If it does not have a blog note, it does not get a date
• No second catalog: Surfaces are not retyped here
• No second catalog: Blog titles are not retyped here

Questions about what's new

• Is this the product changelog? It is the public one. Dated entries come from the blog. Surfaces come from the same list the splash page uses. Internal release notes are not mirrored here.
• Why isn't every feature listed? Clause negotiation, signature, security and the rest have their own pages under Platform. This page is for what changed around that core, and for the notes we actually published.
• How do I see the full article? Each dated note links to its blog post. This page does not reprint them.