What Is a Decision Topic in DataBlueprint?
A Decision Topic is a business area DataBlueprint watches and decides about over time. It is not a dashboard, not a query, not a one-off chat. Here is how to think about it.
If you spend any time in DataBlueprint you will hear the term Decision Topic constantly. It is the central object in the product, and it is intentionally not a dashboard, a metric, or a chat thread.
A working definition
A Decision Topic is a business area you want DataBlueprint to watch and decide about, continuously, over time. Examples we see often:
- Field Tech Profitability
- Customer Lifetime Value Risk
- Cash Flow and Receivables
- Pipeline Conversion Health
- Service Margin by Region
A Topic persists. It does not expire monthly. Once you create it, a private LLM powered by AWS Bedrock keeps reasoning over your Knowledge Graph against that Topic, and produces a fresh Decision Brief on every refresh — daily, weekly, or whatever cadence you set.
Why not just a dashboard?
A dashboard shows numbers. A Topic produces a recommendation and the reasoning behind it. The Decision Brief that comes out of a Topic looks like the memo a senior analyst would write you — here is what changed, here is why, here is what we recommend, here is the evidence.
That is the distinction. Dashboards describe. Topics decide.
Why not just a chat session?
Chat is reactive. You have to remember to ask. A Topic is proactive. It runs on its own schedule, fires alerts when thresholds are crossed, and (on Business tier) can hand work directly to your CRM, PSA, or ticketing system through a webhook — no human in the middle.
How many Topics should you have
Most teams start with one or two: the question their leadership is most tired of answering manually. From there, every additional Topic costs less in attention because the underlying Knowledge Graph is already built.
Where Topics live in the pricing
Free Forever includes 1 Topic. Growth and Business tiers expand the count. See the pricing page for current limits.
Frequently Asked Questions
Why not just a dashboard?
A dashboard shows numbers. A Topic produces a *recommendation* and the *reasoning* behind it. The Decision Brief that comes out of a Topic looks like the memo a senior analyst would write you — *here is what changed, here is why, here is what we recommend, here is the evidence.* That is the distinction. Dashboards describe. Topics decide.
Why not just a chat session?
Chat is reactive. You have to remember to ask. A Topic is proactive. It runs on its own schedule, fires alerts when thresholds are crossed, and (on Business tier) can hand work directly to your CRM, PSA, or ticketing system through a webhook — no human in the middle.