Account-based sales runs on things that get said once. A champion mentions their new manager on a Tuesday call. A pricing objection lands as a throwaway line in a webinar Q&A. A commitment slips out on a demo, then reappears three weeks later as a churn signal that nobody connected back to the moment it started.

The pipeline that captures those moments is the pipeline that closes. The pipeline that misses them is the pipeline your forecast lies about.

Actionary treats every touchpoint as substrate. Meetings, uploads, forms, emails — all land in the same store, all carry the same visibility rules, all reach the embedded agent through the same tools the rest of the CRM uses. The account record is where they converge.

A signals inbox per account

Every account has its own signals feed. The mail connector reads Microsoft 365 every few minutes; an LLM step classifies what matters; the platform creates the right CRM records against the right accounts. The same template covers any adapter the tenant installs.

Champion changes surface as signals. Pricing objections surface as signals. Missed commitments surface as signals. The workflow engine is idempotent by construction — durable queueing on step claims, and a per-source uniqueness key on every signal — so the same email replayed twice produces exactly one signal.

The inbox is scoped to the account you’re on. Nothing about Instant shows up on the Acme record. Read the signals surface for the mechanism.

Uploads the agent reads

Every PDF, PowerPoint, Word doc, meeting recording, and Zoom export the tenant uploads lands in one library. Each asset is broken into small windows (~500 tokens, 50-token overlap), converted into a searchable form, and stored on the same vector index the agent queries. Retrieval scales from thousands of documents to millions with no manual tuning.

A citation is a moment. “On page 14 of the Q4 board pack.” “At 08:42 in the acme-discovery.wav call.” Paginated formats retrieve with a 1-indexed page or slide number; audio and video retrieve with a real second-offset. The agent pulls the exact chunk, quotes it, and hands the account owner a link that lands on the timestamp. Read the agent surface.

Every retrieval passes through the same visibility rules the account list applies. An asset the caller cannot see stays invisible everywhere — the list, the search, the agent’s answer. Revoke a grant, and the very next request drops the caller from downstream retrieval.

Unified deals with partner attribution

One deals table. Direct pipeline and channel-sourced pipeline share the same schema. Each deal carries the partner who sourced it, and the partner portal at portal.{base}/<tenant>/partner shows each partner exactly the deals attributed to them — nothing more, nothing less.

The mechanism is the same visibility grant every other share uses. Revoking a partner’s access is one soft-revoke. The partner login only works on the partner portal domain and physically cannot reach the admin API — two separate cookie scopes, two separate permission models, enforced by the browser and by a server-side filter that scopes every query by the current partner session.

No separate partner CRM. No second permission model to keep aligned.

Context that carries

The load-bearing property is that nothing important disappears. A champion change captured six months ago is one query away. A pricing objection surfaced in a demo lives on the account as a signal with the transcript chunk attached. A missed commitment tagged in a call reaches the account owner before the renewal conversation.

The agent reasons over all of it in one turn. It reads what it learned in prior turns, retrieves the top-K chunks from the upload library, pulls the signals feed for the account, and produces the answer with citations that a human can click into. Read the substrate.

The takeaway

Pipeline coverage stops being a spreadsheet metric when nothing important disappears. Every touchpoint is a row. Every row carries its provenance. Every claim the agent makes about an account anchors to a specific page, slide, or second-offset. The account owner asks “what changed on Acme this quarter?” and gets a specific answer with a specific chunk from a specific call. Read what this means for a CRO.