R128 · Agent principles and patterns › Harness building blocks

Sales artifacts from an agent: context, templates and a stop rule

Read the original

agent-harnesscontext-engineeringself-reviewhuman-in-the-loopenterprise-agents

Source: LangChain's LinkedIn post (2026-11-17) and its blog post "How our GTM Agent builds consistent, high-quality sales artifacts" (Nick Bray, 2026-11-10). Vendor-written; all numbers are LangChain's internal, self-reported figures.

What it claims

LangChain's internal go-to-market agent, which already drafts outreach and surfaces account signals in Slack, was extended to build customer-facing sales documents: account plans, proof-of-value documents, proposal decks and onboarding plans. Over 12 weeks it produced 1,540 artifacts (about 100 a week). The headline numbers:

The central claim is that quality came mostly from context around the model, not from prompt tuning: leadership-owned templates, call transcripts and CRM records, the company's sales stages, and the exit requirements for each stage.

Architecture

The post lists the primitives the system needed:

The generation path is fixed: a trigger (a rep asks, or the agent offers during meeting prep), read the account (CRM record and the shared Drive folder), ask the rep for missing inputs such as success criteria or the economic buyer, copy the leadership-owned template into the sandbox, fill it with python-pptx, render to PDF with LibreOffice, rasterize and read the pages back as images, fix and re-render, then convert to native Google Slides/Docs/Sheets in the account folder and hand the rep a preview with flags on anything a human must still fill.

Two design choices stand out:

The stop rule

Visual self-review raised quality but, with no stopping condition, the agent re-reviewed pages that were already fine, sometimes dozens of times. The fix was a rule to ship as soon as one review pass finds no real defect. On a one-pager this cut a run from 18 minutes to 7. This is the most transferable lesson in the post: any generate-render-critique loop needs an explicit termination criterion, or it converts quality budget into latency and cost.

Proactivity and process enforcement

Because the agent knows each deal's stage and which artifacts clear each stage gate, it can notice before a customer call that the right document is missing and tell the rep which one to bring. Tasks can be assigned to the account executive to produce the expected artifact, built by the agent or by hand. An artifact hub shows every deal, its stage, which artifacts exist and which should come next. The post frames the agent as a distribution channel for both enablement and process.

Measurement

The team tracks four numbers for every agent job: volume (how many generated), utilization (how many shared outside the company), leverage (rep hours saved relative to run cost), and outcomes (pipeline touched). Human taste is treated as the truest quality signal: weekly reviews with each artifact's owning leader, office hours, and Slack feedback channels. Long recorded walkthroughs with an owner were handed straight to coding agents to scope improvements.

How to read the numbers

Tradeoffs

Failure modes

Review checklist

Connections

See R128 on the knowledge map

Part of the Research notes on nowucca.com. Figures and claims are the source's own unless the summary says otherwise.