# Layered context injection for AI answers

> Feed the model the user's current page state, schema, and account context before it answers so the AI can act like part of the product instead of a detached chatbot.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/layered-context-injection-for-ai-answers/
- Source: [newsletter.posthog.com](https://newsletter.posthog.com/p/what-weve-learned-about-building)
- GrowthDex source hub: [PostHog Newsletter](/sources/posthog-newsletter-newsletter-posthog-com-2/)
- Last checked: 2026-05-26
- Rarity: rare
- Budget: medium
- Channels: Product, Onboarding, AI Search
- Stages: ai products, activation, ux, context


## Why this can grow

Users do not experience your product as a blank prompt. They arrive from a page, a role, a dataset, and a business context. When the agent receives that context up front, it can produce answers that fit the real task instead of generic best guesses. This lowers the amount of clarification the user has to provide, makes outputs feel more native to the product, and gives the AI a real advantage over a general model tab.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. For activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where layered context injection for ai answers can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Product and Onboarding channel.
3. Use the evidence from newsletter.posthog.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

PostHog says Max AI receives current dashboard state, visible insights, filters, role, schema details, account tier, timezone, and retention context so requests like why signups dropped last week can be answered inside the product context instead of from a blank chat.

## Adjacent tactics in the same lane

- [Suggested prompts in the empty AI state](/growth-ideas/suggested-prompts-in-empty-ai-state/) - same source, 1 shared channel, 3 shared stages
- [MCP server before custom agent](/growth-ideas/mcp-server-before-custom-agent/) - same source, 2 shared channels, 1 shared stage
- [AI install wizard for 90-second setup](/growth-ideas/ai-install-wizard-for-90-second-setup/) - same source, 2 shared channels, 1 shared stage
- [Task-based model routing for AI speed](/growth-ideas/task-based-model-routing-for-ai-speed/) - same source, 1 shared channel, 2 shared stages

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [AI products stop feeling smart when they hide their context](/blog/ai-products-stop-feeling-smart-when-they-hide-their-context/) - AI products, product-led growth, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.