How it works

Your team builds the context. Every agent uses it.

The people who know what your data means are the ones who define it — by clicking, not by filing a ticket.

What's in the full context

Data, semantics, and process.

An agent needs more than your records. It needs the knowledge that isn't in any field, and it needs to know how your team does the work. Three artifact families carry those three things, and instructions run across all of them.

Entities

The records

Curated fields, rollups over child records, filtered related lists, the parent record, and computed signals — assembled into one view. This is what is true right now.

Briefs

The business knowledge

How you segment, what a stage means, how you sound, what your policies are. The knowledge that isn't in any field — the frame a record has to be read in.

Skills

How the work gets done

The steps your team follows, with stop conditions, so every agent does it the same way. A skill references a definition by name, so the definition can change underneath without the skill needing an edit.

Instructions, across all three

Instructions carry the judgment your team applies without thinking: what a value means, when it matters, and how it may be used. They attach per field, per entity, and per domain — so the same field can read one way in a pipeline view and another in a renewals view.

Who writes them, and how

An instruction, as written

“Health score below 60 warrants outreach. Sourced from the customer success platform, refreshed nightly — internal only, never quote to a customer.”

Building your context layer

An easy-to-use app for business users — not a job for developers.

The people who own the meaning do this themselves, start to finish. We help you get going, and once it is live the app shows you how your context is being used, so the team that built it is the team that keeps it right.

01

Build your entities

Start from the page layout the object already has, keep the fields that matter, and write an instruction against the ones that need one. Rollups over child records, filtered related lists, and computed signals get added the same way.
How entities get built
02

Add briefs and skills

Briefs carry the knowledge that is in no field — how you segment, what a stage means, how you sound. Skills carry how your team does the work, so every agent does it the same way.
What's in the context
03

Preview against real records

See exactly what an agent will receive, rendered from a record you choose, before anything is activated.
Building and previewing
04

Package into domains

A domain is a named lens: this set of entities, these briefs, these skills, for a team or an agent. Finance and Sales look at the same records through different domains without either maintaining a second copy.
Domains and ownership
05

Deploy to your AI tools and agents

Pick where the domain is delivered — Agentforce, an MCP client, Prompt Builder, Flow, Apex. Adding another later is a connection, not a rebuild.
Connecting each surface

ContextWorks · Build

Opportunity 360

Active

A deal as RevWorks sees it. Reach for this when judging whether a deal is healthy, stuck, or about to slip.

Core record

Opportunity

The same object, at the depth the question needs.

List 6fields

Standard 15fields

Detailed 15fields

Enrichment

Deal Health scored

Sales Process status

Stage Progression trend

Activity Timeline recent

Computed on the way out. None of it is stored on the record.

Referenced object

Account embedded at standard level

Related objects

Products OpportunityLineItem 25 rows max

Contacts & Roles OpportunityContactRole 10 rows max

The two lists that matter, capped — not the whole tree.

Metrics

Open Tasks count of Tasks IsClosed = false

Counted in the query. The agent gets one number, not every task.

Where it shows up

Where your users and agents already work.

You did the work once. It turns up everywhere your team asks a question — and the answer is the same in all of them, because they are reading the same definitions.