Reference solution for taking one request for intelligence about a target account through interpretation, internal account-context retrieval, external signal discovery, evidence normalization, analysis, optional validation, and a business-facing account brief.
Unit event
Account Intelligence Request
ACCOUNT_INTELLIGENCE_REQUESTOne request for intelligence about a target account, combining available internal account context and external signals into a business-facing account brief.
Design variant
Twenty internal records, six external searches, twelve source summaries, two analysis passes, one validation pass, a richer strategic brief.
Every value this design resolves, and who owns it. Change an editable value and the figures recalculate. The pricing engine answers, not this page: nothing here multiplies anything, and until it answers the figures beside you are the ones you were already looking at, labelled as such.
58 fields
How much of the account identity this step reads.
How long the incoming request is.
Input tokens eligible for cached-input treatment.
How long the research plan runs.
How much of the surrounding request context this step reads.
The instructions this step is given.
How many CRM and account records were read. A workload fact: §3 forbids mapping an internal read to Remote Tool Access, File Search or Web Fetch without canonical invocation authority.
How much internal context was assembled.
How many internal systems were consulted. Explanatory only.
How much of the account identity this step reads.
How much of the research plan this step reads.
Input tokens eligible for cached-input treatment.
The instructions this step is given.
How much signal summary the model writes.
How many external sources were summarized. Explanatory only.
How much of the request this step reads.
How long the issued search queries are.
How much of the returned search results this step reads.
How many Web Search queries this step issues. The Service's own metered quantity.
How large the merged evidence is — the sum of what the two retrieval steps produced, so normalization neither invents content nor loses it.
How much of the external signals this step reads.
How much of the internal context this step reads.
The instructions this step is given.
Input tokens eligible for cached-input treatment.
How much analysis the model writes.
How much of the evidence this step reads.
How much of the request this step reads.
How much of the insights this step reads.
Input tokens eligible for cached-input treatment.
How many validation notes are expected.
How much of the evidence this step reads.
The instructions this step is given.
How much of the insights this step reads.
The instructions this step is given.
Input tokens eligible for cached-input treatment.
How long the brief runs.
How much of the evidence this step reads.
How much of the request this step reads.
How much of the validation notes this step reads.
Where the direct unit cost comes from. Expand an operation for the activities inside it and how each one resolved.
Interpret the request and plan what to find out.
Interpret Account Intelligence Request
PricedNormalize the request and state what to find out about the account.
A pricing request was made and returned an amount.
Read what the business already knows about the account. Application data access, and unpriced.
Retrieve Internal Account Context
No pricing requestRead the CRM and account records the business already holds. Enterprise data access, not a purchased service.
This activity does not price. No request was made, so there is no amount — not an amount of zero.
Search externally and summarize what was found.
Discover External Account Signals
PricedSearch externally for developments about the account and summarize what was found.
A pricing request was made and returned an amount.
Normalize the evidence, then reason over it.
Normalize Account Evidence
No pricing requestMerge, deduplicate and order the internal and external evidence. Deterministic application logic.
This activity does not price. No request was made, so there is no amount — not an amount of zero.
Analyze Account Intelligence
Priced×2Reason over the evidence for the account's situation, signals, opportunities, risks and open questions.
A pricing request was made and returned an amount.
Check the insights against the evidence that supports them.
Validate Account Insights
PricedCheck that the insights are supported by the evidence. A consistency check, not a truth score and not a recommendation ranking.
A pricing request was made and returned an amount.
Write the account brief.
Produce Account Brief
PricedWrite the account brief: snapshot, internal context, external developments, risks and open questions.
A pricing request was made and returned an amount.
Direct unit total
0.2884 USDBars show each operation’s share of the stated direct unit total. An operation with no priced activity shows no amount, which is not an amount of zero.
Activity states not exercised by this configuration
The read model reports these so their absence reads as absence rather than as coverage.
Issues
The runtime reported none for this configuration.
Technical detail and reproducibility