Sopact Sense is the intelligence engine. Your stack — BI, warehouse, MCP, GenAI tools like Claude — is the actionable layer. Two engines, one operating system for impact data. Custom dashboards in minutes, not weeks.
By Unmesh Sheth · Sopact
§ 5.0 · Where this chapter sits
Where this chapter sits
From canonical reports to custom anything.
Chapter 04 gave you four canonical report types straight out of Sense.
This chapter is how everything downstream of those reports gets built
— by your team, in your stack, in minutes.
Chapters in Beyond the Survey
00Introduction8 pages
01Workflow22 pages
02Data Design17 pages
03Data Collection16 pages
04Intelligent Suite18 pages
05Actionable Insightyou are here
The library
Book 01 · this book
Beyond the Survey
The foundational field guide — methodology for the AI era.
One unified intelligence layer across many programs.
2
CHAPTER · 05
Actionable Insight.
Sense produces stakeholder intelligence — clean, structured, multi-language,
live. What you do with it is the actionable layer, and it's bigger
than any single tool. It's your BI, your warehouse, your AI agents,
your automations — all working from the same source of truth.
What you'll learn
01.The two engines — Stakeholder Intelligence vs Actionable Insight
02.Export · BI · warehouse — the outbound layer
03.MCP, API + GenAI — custom dashboards in minutes with Claude
04.Three worked examples that extend the Ch 04 reports
Time to read
14 min
16 pages · 26 illustrations
3
§ 5.1 · The two engines
Chapter 05 · §5.1
Two engines. One operating system.
Most teams confuse the two. They want their survey tool to also be their
dashboard tool, their warehouse, their decision engine. It can't — and shouldn't.
Each engine has a job. Together they form how impact data actually moves through
your organization.
ENGINE 01 · BUILT BY SOPACT
Stakeholder Intelligence
One platform: Sopact Sense.
DOES ONE JOB · DOES IT WELL
Captures four channels into one clean dataset
Analyzes qual + quant on collection (not weeks later)
Exports to CSV · XLS · Google Sheets · Zapier flows
Connects to Tableau · Power BI · Looker Studio · Snowflake
Exposes via MCP + API — readable by Claude + AI agents
Unifies with external sources — Salesforce · Stripe · government data
BUILT FOR
Unique, evolving needs
SPEED
Minutes · ad-hoc
One engine produces stakeholder intelligence. The other turns it into
any action your team needs. Sequential, not competitive.
4
§ 5.2 · The handoff
Chapter 05 · §5.2
A clean handoff, and the fan-out begins.
The intelligence engine produces a single artifact: a clean, structured,
audit-ready dataset (and the canonical report alongside it). From that one
artifact, the actionable layer fans out — to BI dashboards, automations,
AI agents, and ad-hoc custom views. One source of truth, many destinations.
What stays in Sense
Collection, cleaning, qual+quant analysis, the four canonical reports.
The work that should be standardized.
What moves to the actionable layer
Custom dashboards, decision automations, ad-hoc Claude analyses, BI
joins with your CRM and warehouse. The work that should evolve.
5
§ 5.3 · Outbound · table stakes
Chapter 05 · §5.3
Outbound, four ways. Table stakes.
Before the BI and AI layers, the simplest exits. Every data grid in Sense
flows out as a file or a triggered event. No "data download as a service" fee.
⬇
CHANNEL 01
CSV · XLS
One click on any data grid → flat file in your downloads folder.
USE WHEN · ad-hoc analysis · email to a collaborator · feed an old spreadsheet workflow
⊞
CHANNEL 02
Google Sheets
Live sync. Sheet updates as new responses arrive — no manual export.
USE WHEN · team works in Sheets · ops dashboards · joining with manually-entered data
⚡
CHANNEL 03
Zapier
Trigger flows on every submission · pipe to Slack, Notion, Salesforce, 6,000+ apps.
USE WHEN · route to CRM · alert staff · log to records system · no-code automations
{ }
CHANNEL 04
API · Webhooks
Programmatic access · webhook on submit · full payload to your service.
USE WHEN · custom integrations · feed your warehouse · build product features on Sense data
Every grid in Sense ships out four ways — and each path keeps the
stakeholder_id intact so downstream systems can join cleanly.
The next page is what most people mean when they say "actionable": BI and warehouse.
6
§ 5.4 · BI + warehouse
Chapter 05 · §5.4
Your BI team already has dashboards.
Most enterprises run on Tableau, Power BI, or Looker — and behind them, a
Snowflake / BigQuery / Redshift warehouse. Sense feeds straight into that
stack. Your impact data joins your finance data, your CRM data, your
program data — in the dashboards your team already opens every Monday.
WHAT THIS UNLOCKS · 01
Cross-functional joins
Impact data joins finance, CRM, and ops data in the same dashboard.
WHAT THIS UNLOCKS · 02
Existing dashboards extend
No "impact reporting tool" — impact rows land in the views you already use.
WHAT THIS UNLOCKS · 03
Enterprise governance
Warehouse access controls + audit logs apply to impact data automatically.
7
§ 5.5 · MCP + API
Chapter 05 · §5.5
MCP-native. Your data, readable by AI.
MCP — the Model Context Protocol — is the emerging standard for how AI agents
read data from external tools. Sense speaks it. Which means Claude (and any
MCP-compatible agent) can read your impact data the same way your dashboards do,
over the same secure API.
WHY MCP MATTERS
AI agents don't want CSV exports. They want a live API they can query
conversationally. MCP is how Claude reads your Sense data, asks follow-up
questions, and builds custom views — all without leaving the chat.
SECURITY & SCOPE
Every MCP token is scoped: which records, which fields, which actions.
Same governance as a dashboard share. Audited per query.
8
§ 5.6 · GenAI dashboards
Chapter 05 · §5.6 · the killer combo
Claude + MCP + your data. Build in minutes.
The most powerful part of the actionable layer doesn't come from a BI tool.
It comes from pairing your clean Sense data with a GenAI agent — most teams
use Claude — over MCP. You ask in plain English. The dashboard materializes.
The next question reshapes it.
CLAUDE · WITH SENSE MCP CONNECTED
From the Spring 2026 cohort, show me confidence delta broken down by demographic — and overlay placement rate at +6 months.
CLAUDE
Reading Spring 2026 cohort via Sense MCP… joining on participant_id… building chart. Done.
→ dashboard ready · 1.4s
Filter to first-gen learners only. And add the confidence quotes.
MCP READ
DASHBOARD · GENERATED LIVE
Spring '26 · confidence × placement
→ click any bar to drill to the 12 underlying responses
90s
TIME FROM QUESTION TO DASHBOARD
Two prompts, one drill-down. No BI ticket, no consultant.
previous tool stack: ~3 days
9
§ 5.7 · Data unification
Chapter 05 · §5.7
Sense is one source. The full picture needs several.
The actionable layer's superpower isn't building dashboards faster — it's
joining sources. Sense brings clean stakeholder data. Your CRM brings
relationship history. Stripe brings transactions. Government datasets bring
context. Unified, they become evidence; siloed, they stay anecdote.
The join key is everything. Sense's stakeholder_id is the spine
that every external source attaches to — Salesforce's contact_id, Stripe's
customer_id, your warehouse's user_uuid. Match once at the join,
unify forever.
10
§ 5.8 · Example 1 · workforce + wage
Worked example 01 of 03 · extends Ch 04 §4.9.1
Girls Code + wage data.
The Ch 04 cohort report already shows confidence delta + skill gain.
Adding alumni wage data unlocks "did the program move incomes?" — the
question every workforce funder eventually asks.
Adds
LinkedIn / Indeed wages
Via
MCP + Claude
Time to build
~15 minutes
PREVIOUS · CH 04 §4.9.1
Cohort report
conf Δ +2.4 · skill Δ +1.7
47 learners · 12 wks
+
ADD · VIA MCP
Wage data
CLAUDE · prompt
"Pull current titles + wages for the 47 alumni from LinkedIn, joined on email."
→ 42 / 47 matched
+ T-6mo wage column
=
NEW · BUILT IN CLAUDE
Confidence × wage gain
$18k median wage gain
+ drill to alumni list
The result
Sense's cohort report kept the canonical "skill + confidence" structure
intact. Claude — with the Sense MCP connected — pulled LinkedIn wages
on demand and built the confidence × wage scatter that the foundation funder
actually wanted to see. 15 minutes from question to share-ready link.
11
§ 5.9 · Example 2 · ESG + emissions
Worked example 02 of 03 · extends Ch 04 §4.9.4
ESG portfolio + emissions actuals.
Ch 04's ESG dashboard reads each company's claims from sustainability
PDFs. Joining the warehouse's emissions actuals in Snowflake produces the
chart every board chair now asks for: claim vs. reality.
Adds
Snowflake emissions rows
Via
Warehouse join + Power BI
Time to build
~30 minutes
PREVIOUS · CH 04 §4.9.4
PDF claims
scored from disclosures
+
ADD · SNOWFLAKE
Emissions actuals
SQL · join on company_id
SELECT sense.score, wh.scope1_actual, wh.scope2_actual FROM sense_esg s JOIN warehouse.emissions wh ON s.cid = wh.cid;
→ 8 / 8 matched · monthly
=
NEW · POWER BI
Claim vs. actual
⚠ Delphi · 50% gap
→ drill to evidence
The result
The PDF-claims scoring from Sense stays the source of one half of the chart.
Snowflake's emissions actuals are the other half. The join — on company_id —
is one SQL statement.
Power BI's existing portfolio dashboard now shows the gap, every month, automatically.
12
§ 5.10 · Example 3 · application + alumni
Worked example 03 of 03 · extends Ch 04 §4.9.3
Application panel + alumni outcomes.
Ch 04's scholarship panel scores 500 applicants in days. Joining the
alumni team's outcomes log (kept in Google Sheets) reveals which
application traits predict alumni success. The selection rubric updates
itself.
Adds
Alumni outcomes log
Via
Sheets sync + Tableau
Time to build
~2 hours · once
PREVIOUS · CH 04 §4.9.3
500 applicants
applicantscore
a_001 · Chen87
a_002 · Diaz84
a_003 · Patel61
… +497
AI brief + rubric per app
+
ADD · GOOGLE SHEETS
Alumni outcomes
SHEET · alumni-log
app_id · outcome_5yr
a_001 · founder
a_002 · academic
a_003 · founder
… maintained by alumni team
→ live sync · 312 alumni tracked
=
NEW · TABLEAU
Predictive rubric
rubric self-updates · annually
The result
Sense's per-applicant briefs stay the source of truth at intake. The
alumni team's Sheet (their tool, their workflow) joins on
application_id. Tableau builds the predictive overlay. Next year's
rubric incorporates what the data has been quietly teaching for five years.
The selection process gets smarter without anyone re-training it manually.
13
§ 5.11 · The accelerant
Chapter 05 · §5.11
Sense ships clean data. Skills ship the bridge.
The actionable layer needs a bridge. Skills in Sense generate that bridge —
the MCP exposures, the BI connectors, the unified joins, the Claude-ready
prompts. So your team isn't writing integration boilerplate; they're working
on the question that matters.
THE INTELLIGENCE ENGINE
Sopact Sense
Stays the same job: capture clean, analyze on collection, produce the
canonical reports. Everything in this chapter consumes what Sense produces.
Exports · 4 channels
CSV · XLS · Google Sheets · Zapier triggers on every grid.
BI · native connectors
Tableau · Power BI · Looker Studio · Snowflake outbound.
MCP server · scoped
Claude + custom agents · same audited API as your dashboards.
REST + GraphQL API
Programmatic access for product engineers + ops automations.
THE ACCELERANT
Skills
Prepackaged playbooks for the actionable layer. They take the boilerplate
out of integrations so your team works on the question, not the wiring.
{ }bi-bridge
Wires Sense as a live source to Tableau / Power BI / Looker.
{ }mcp-exposer
Generates scoped MCP tokens for Claude + AI agents · per-record access.
{ }data-unifier
Joins Sense's stakeholder_id with Salesforce, Stripe, warehouse keys.
{ }claude-co-pilot
Drafts MCP-ready prompts for ad-hoc dashboards built in Claude.
↑
Why this compounds
Cohort 1 teaches Sense your join keys, your BI vocabulary, your Claude prompts.
Cohort 2 inherits all three. By cohort 5, your team's "intelligence + actionable"
loop runs faster every quarter — because both engines have been quietly
learning from each other the whole time.
14
§ 5.12 · Recap + Up Next
Chapter 05 · §5.12
Six lessons to carry forward.
1
Two engines, one OS.
Stakeholder Intelligence (Sense) and Actionable Insight (your stack + AI). Sequential, not competitive.
2
Four exits, table stakes.
CSV · Sheets · Zapier · API. Every grid ships out, every record stays joined.
3
BI + warehouse · massive.
Tableau, Power BI, Looker, Snowflake. Impact rows land in dashboards your team already opens.
4
MCP makes it AI-readable.
Claude + other agents read your data via the same secure API as your BI tools.
5
Dashboards in minutes.
Claude + MCP + clean Sense data = ad-hoc views built conversationally, not by ticket.
6
Unification is the multiplier.
Sense + CRM + warehouse + LinkedIn + government data — joined on stakeholder_id, none siloed.
UP NEXT
Chapter 06 · Application Management
The book closes with a full lifecycle worked example — application intake
to onboarding — applying both engines to one domain. Also the teaser for
Book 06.
06
15
End of Chapter 05
END OF CHAPTER 05 · BOOK 01
Two engines. One operating system. Built for the AI era.
Sense produces stakeholder intelligence. Your stack + AI produces actionable
insight. The handoff between them is one clean dataset, and the work above
runs from there.
BOOK 01
Beyond the Survey
You are here
BOOK 03
Grant Management
Industry guide
BOOK 04
Impact Investment
Industry guide
BOOK 05
Workforce Training
Industry guide
BOOK 05
Nonprofit Programs
Industry guide
BOOK 06
Application Management
Industry guide
"One engine produces stakeholder intelligence. The other turns it into
any action your team needs. Sequential, not competitive."