Skip to content
GuideAgent setupIntermediate

Maintaining the artifact library

The library you maintain and every agent reads from. Eight kinds of artifact, drafts that never touch what is published, and why it is a quarterly RevOps item.

RRRevTech RevOpsRevenue operations team 3 minUpdated
Part 1 of 5

The library you own

Artifacts, reached from the header of the AI Agents hub, is the canonical place for the material your revenue team runs on: how you describe the company and its tone, your products, your ideal customer, your sales process, your references and proof points. Agents reference these when they generate work.

The sentence that matters most: they do not fill this library in for you. Setup drafts a first version of each with you, and from then on what you keep here is what they have to work from, which makes this the one surface in the product where the quality ceiling is set entirely by you.

RevTech: The artifact library lists approved business context with publishing status, owner and version.
The artifact library lists approved business context with publishing status, owner and version. Captured from the current application with illustrative sample data. Screenshot of the RevTech application; sample data.
The artifact library lists approved business context with publishing status, owner and version.
Part 2 of 5

Eight kinds of artifact

Every artifact has a kind, and there are eight: Company Overview, Company Tone & Brand, Product Overview, Technical Product Deep Dive, Ideal Customer Profile, Sales Process, Customer References, and Proof Points & Wins. The kind tells the agents what the document is for. An Ideal Customer Profile needs criteria before it can be published.

The failure mode is leaving the first drafts as they are and concluding that agent output is generic. It is generic because the Company Overview still describes a generic company.

Part 3 of 5

Drafts, publishing and the audit trail

Add Artifact opens a full-screen editor, and a new artifact starts life as a draft, never published. Every save creates the next draft version and never changes what is published. Publishing is a separate, explicit step with its own confirmation, because it authorizes that version for the agents to ground on. The list shows each artifact's status, when it was last published, who published it and its version, and names a newer unpublished draft beside a published artifact.

Version history lets you open any draft, published or archived version and read exactly what it said. That gives you something more useful than a backup: a record of how your operating model actually evolved, with dates. When agent output changes character and nobody can say why, the version history on the artifact it draws from is usually the answer.

When an agent proposes a change to an artifact, it arrives in the Action Center as a review card. Approve & publish puts it live, Request changes sends it back with your reasons, and Reject records that it should not go out. Each is a recorded decision.

Part 4 of 5

One source, everywhere it shows up

The artifact you publish here is the one the agents ground on wherever they draw on it, campaign collateral included. That is the point of a library rather than a folder. A messaging change lands everywhere at once, and there is no second copy quietly disagreeing with it.

It also means a bad artifact propagates just as efficiently as a good one, which is the argument for the review rhythm below rather than an argument against the design.

Part 5 of 5

The quarterly rhythm

Keeping artifacts current is what keeps agent output on-message, and it is work that belongs to a person rather than to the system. Treat the highest-leverage artifacts, the Ideal Customer Profile, the Sales Process and the Product Overview, as quarterly review items in your RevOps cadence.

Those three are named specifically because they feed the most downstream work. An out-of-date reference produces one awkward email; an out-of-date Ideal Customer Profile quietly misdirects targeting, scoring and campaign generation at the same time.

What to take away

  • Agents reference this library. They do not fill it in for you.
  • Agents ground on the published version. A saved draft changes nothing until someone publishes it.
  • Every save creates a new draft version, so the library is an audit trail of how your operating model changed.
  • One artifact, everywhere it appears — every agent that draws on it reads the same published version.
  • Put the Ideal Customer Profile, Sales Process and Product Overview on a quarterly review. Those move the most output.
Demo

See how the work gets done.

Explore how agents prepare work across your revenue teams, and how people review it, guide it and decide what happens next. Fictional data. Real product.

Explore the demo