SELF-GUIDED REGIONAL DIAGNOSTIC
Know exactly where your NSF Engine should act next
A data-grounded tool that diagnoses your industry and ecosystem performance benchmarked against peers, and a set of hypotheses and first moves you can defend.
A kickoff call with us, self-paced work in My Compass, a synthesis call. Pick a step to see what to expect.
STEP 1 · CALL
YOU'LL LEAVE WITH
Your NSF Engine's Compass configured, and a clear sense for how TBP can support your process.
COMPASS CONFIGURATION SUMMARY
1
Core industry
2
Geography
3
Peer regions
4
Starting hypothesis
STEP 2 · SELF-PACED IN MY COMPASS
YOU'LL LEAVE WITH
A summary of your analysis and a draft framework for action
DIAGNOSTIC DOCUMENT
1
Industry Definition
2
Industry Trajectory
3
Ecosystem Assessment
4
Ecosystem Diagnosis + NSF Engine Role
5
Priorities, Narratives, and First moves
STEP 3 · CALL
YOU'LL LEAVE WITH
A finalized narrative document (5-6 pages) you can use directly with partners and funders, and a clear view of what's next.
Finalized, Integrated Narrative Document
1
The AI-powered analysis
2
TBP and NSF Engine joint synthesis
3
Narrative overlay for partners
The firms, relationships and history behind the numbers. You make the calls: which pattern fits, which barriers are real, what comes first.
Built on the Compass framework and public / private data we have supplied the tool (nothing else). No fabricated metrics, no generic assumptions, and honest acknowledgement of what the data can't see.
They run the kickoff and synthesis calls, review your diagnosis before you set priorities, and step in whenever you want a thought partner.
Dig deeper: frameworks, process, and what the data can do for you.
How much time does this really take?
It depends on your team and your deadline. Two calls with us bookend the work; the middle is self-paced, so a team with a date to hit can move quickly and a team without one can take the time it needs. You'll set a cadence with your navigator at kickoff.
What if we only get through the first milestone?
You'll still leave with an Industry Definition Statement, a data-grounded answer to "how big is this, really?" in the terms partners use. Many NSF Engines find that alone answers the question they keep being asked. Nothing later is wasted if you stop there.
Do we need a data scientist?
No. AI-powered data analytics does the retrieval and the arithmetic; the TBP navigator and data analyst handle sources. You need someone who knows your region's firms and institutions well enough to challenge a chart, and a lead willing to be challenged.
What if the data is wrong about us?
It will be, somewhere: suppressed defense employers, misclassified firms, trade secrets that never patent. The first milestone is designed to surface exactly that. When a correction changes the picture, you get an explicit revised read.
Can we get help partway through?
Yes, anywhere. Every milestone has an "I want a thought partner here" flag; the highest-stakes moment, the diagnosis, has review built in; and you can move to the guided track at any point.
Who sees our data and outputs?
Your analytics run on a dedicated instance that is blind to other NSF Engines. Documents go to a shared folder your TBP navigator can review asynchronously. Nothing is published without you.
