Discussion about this post

User's avatar
Jordan Gronk's avatar

Pattern Engine and Context Layer as separate concepts is a good frame to use.

In case it helps, I'll elaborate on how I'm thinking about these and seeing them in practice (open to feedback, don't have all the answers).

- Examples of the pattern engine: We have an agent that synthesizes product data into hypotheses and natural-language "facts" about usage. The hypotheses power downstream rep actions, while the facts can be used as downstream context (e.g. did the action items we discussed in the last meeting with the customer actually come through in their usage? Or a deal risk agent can pull in usage facts, as right now it only has Gong transcripts and opp data). Similarly, we have agents that research accounts and product facts about them, such as whether they contribute to open-source projects, which can be used for account-based campaigns and rep lists.

- Examples of the context layer: We have agents that craft highly personalized emails, much better than any rep does, getting 10+% reply rates. The agent identifies the persona, use case, and product in order to write. All those are vector stored documents. I'm using a combination of Octave for the email writing and context library, n8n for data pipelines and evals, and customer.io as the MAP/email platform. Octave wants to create a feedback loop where new use cases are dynamically inserted based on opportunity data, i.e. context creating itself, pretty cool!

- I want to build a company-wide GTM context and pattern stores. I'm still learning about how this will come together both technically and strategically, but conceptually here is what will live in those layers. Super open to feedback on what to include and how to build it!

• Data models available to agents in the data warehouse with metadata (model description, dimension definitions).

• Facts / pre-processed data, similar to the first example I shared. Another example: Key contacts in an account, based on transcripts, emails, and opps.

• Tools (MCP servers and custom API functions).

• Something akin to Claude skills, but basically a repo of prompts with metadata on the tools accessible to the skill.

• Deterministic workflows.

Some open questions:

- What architectural patterns are most useful for different use cases? (https://www.anthropic.com/engineering/building-effective-agents) I love how autonomous Cursor is, how do we get there for internal GTM use cases?

- How does observability work for these systems?

No posts

Ready for more?