For corporate venture and enterprise innovation teams

Build a shortlist you can defend.

You need to know which companies deserve a closer look. And you need to explain why.

Assess opportunities against your criteria. Examine the supporting evidence. Bring your organization’s available relationship history into the conversation. [1] [3]

See the workflow behind your next recommendation.

What you’re working toward

Know where to focus.

Put your evaluation effort behind the opportunities that fit your criteria.

Explain your recommendation.

Bring the reasoning into the room, not just the ranking.

Build on what’s known.

Check available history before repeating research or starting another conversation.

The work before the decision

Your next review shouldn’t become another research assignment.

You have a promising company on the shortlist. But before you recommend it, you need to establish whether it fits the brief, whether the evidence holds up, and whether someone inside your organization has already evaluated it.

When those answers are scattered, the meeting becomes a request for more work. Another search. Another message to a colleague. Another version of the same report.

Does it fit the brief?

Can you trace the evidence?

Who already knows this company?

Spend the conversation deciding what happens next, not reconstructing how you got here.

Your starting point

What are you trying to get done?

Start with the job in front of you. Follow the path that moves your work forward.

These paths connect the available workflows. They are not a promise that every workflow is a separately purchasable module.

Service and offering lanes

Get the support your next decision needs.

A starting list. A closer assessment. A clearer view of work already happening inside your organization.

The lanes below organize Nucla’s published capabilities. Commercial packaging and delivery scope must be confirmed.

Scouting and discovery

Find companies against your brief.

Relevant to your selected path

Start with the opportunity you are pursuing and the criteria that matter. Use thesis-based discovery to build a pool for further evaluation. [1]

Your working output
Companies to investigate against a defined brief.
Your intended outcome
More of your search effort goes toward relevant opportunities.
Explore discovery in your demo

Company triage and assessment

Give your long list an order of attention.

Relevant to your selected path

Bring a company name or a list. Examine fit scores and the reasoning behind them against your thesis. [2]

Your working output
A scored list with assessment reasoning.
Your intended outcome
A clearer basis for deciding what deserves deeper investigation.
Explore assessment in your demo

Decision briefs and review preparation

Explain why a company belongs on your shortlist.

Relevant to your selected path

Use assessment reasoning and sourced evidence to prepare your recommendation. Bring the case into the discussion so colleagues can examine it. [2]

Your working output
A brief your team can review and challenge.
Your intended outcome
A conversation centered on the substance of your recommendation.
Explore decision briefs in your demo

Relationship intelligence and shared knowledge

Know what your organization already knows.

Relevant to your selected path

Check available relationship owners, notes, reports, and activity before you start again. Access depends on the information available to your group and its permissions. [3]

Your working output
Relevant history and people to consult.
Your intended outcome
Less avoidable repetition and a more informed handover.
Explore relationship context in your demo

Company monitoring and portfolio tracking

Keep important companies in view.

Relevant to your selected path

Follow relevant companies and review available updates, including internal contributions and changes supplied by connected data providers. [3]

Your working output
Updates on the companies you follow.
Your intended outcome
A reason to revisit an opportunity when information changes.
Explore monitoring in your demo

Optional hands-on support

Need help making this part of your team’s work?

Proposed service lanes. Availability, staffing, fees, and delivery scope must be confirmed before these are sold.

Implementation and enablement

Get your team ready to use it.

Discuss the workflow, relevant data connections, access requirements, and onboarding your team would need. Agree on responsibilities and a successful launch before work begins.

Discuss your setup needs

Managed research and reporting

Get help maintaining the work.

Discuss the companies or themes to cover, the review cadence, and the reporting requirements. Separate human research support from software automation and retain ownership of your decisions.

Discuss your delivery needs

Software access, one-time setup, and recurring human work should be scoped separately. Do not assume a subscription includes managed research.

Inspect the work

See the work behind your recommendation.

Before you change how your team works, examine what you would need to make a useful decision.

Assessment structure

Illustrative structure, not a live product output.

Fit

Why does this company deserve a closer look?

Start with the decision and the criteria. A score becomes useful when you can examine the reasoning behind it.

Your evaluation thesis
The criteria the opportunity needs to be assessed against.
The fit reasoning
The explanation you need to inspect before relying on a score.
Your reviewer questions
What you still need to confirm before recommending action.

Evidence

Can someone else follow your reasoning?

Your recommendation needs something another person can check. Separate the supporting material from the conclusions you draw.

Supporting material
The source behind an important claim or assessment.
Freshness
When the information was published or last checked.
Gaps and uncertainty
What is missing or awaiting further confirmation.

Context

What does your organization already know?

The next conversation should benefit from the work that came before it. Review the information you are permitted to access.

Relationship ownership
The relevant people inside your organization to consult.
Previous evaluations
Available reports, notes, and lessons from earlier work.
Recent activity
Information worth checking before starting another approach.

The connected path

Move forward.
Keep the reasoning.

You are working toward a recommendation your colleagues can examine, not simply another document to circulate.

  1. Start with the decision.

    Define what you need to decide and the criteria that will guide the evaluation.

  2. Find or bring the companies.

    Begin with a discovery brief, an existing shortlist, or a single company.

  3. Examine fit and context.

    Review the assessment and consult available organizational information.

  4. Make your recommendation.

    Explain what deserves further work, what does not, and what remains uncertain.

  5. Revisit when things change.

    Use relevant updates to decide when another look is warranted.

A client perspective

The reason for doing the work.

“…learn more about the startups in our ecosystem, look for potential partners…”

Lauren Thaman P&G Ventures · Speaking about the Innovation Challenge May 28, 2020 · Consumer Goods Technology

Consumer Goods Technology reported that P&G Ventures used KITE SRM to recruit, evaluate, and select Innovation Challenge finalists.

Read the original reporting

Historical KITE SRM program context. This quotation describes the program’s purpose. It is not a current Nucla product testimonial or evidence of today’s AI performance.

Institutional reference

Nucla is listed in Fresco Capital’s portfolio.

View the portfolio listing

An investor reference, not independent product-performance evidence.

Outcomes worth testing

Judge the value by what changes in your work.

Choose a workflow. Set your baseline. Decide what a useful improvement would look like for your team.

You get preparation time back.

Compare the time needed to produce a reviewed assessment, including checking and corrections.

You give more companies a proper look.

Compare evaluation capacity at an agreed quality standard, within the same amount of team time.

You can explain your recommendation.

Check whether reviewers can find the evidence and understand the reasoning without rebuilding the research.

You stop repeating avoidable work.

Record specific cases where existing research or relationship history was reused.

Your knowledge survives the handover.

Check whether previous reports, notes, and context remain useful when responsibilities change.

You know when to look again.

Review whether relevant updates reach the right person and prompt a useful reassessment.

These are proposed evaluation goals, not reported customer results or guaranteed improvements. Agree on the standard before you judge the result.

Before you commit

Your questions, answered.

Know what you’re evaluating, what your team needs to provide, and what still needs to be confirmed.

Can you start with companies you already have?

Yes. Nucla describes single-company and uploaded-list assessment against your thesis. Confirm the supported format and relevant limits during your demo. [2]

Does a fit score make the decision for you?

No. Use it as an input. Examine the supporting information, test important assumptions, and complete the further investigation your decision requires.

Do you have to abandon your existing tools?

Nucla documents relationship information shared across tools and groups. Confirm the connections, permissions, and setup your team would need rather than assuming every system is supported. [3]

What can your IT and security team review?

Nucla publishes a security overview covering encryption, access controls, and enterprise single sign-on. Request the documentation relevant to your deployment and AI-data handling before connecting sensitive information. [4]

Can you see an example without sharing confidential information?

Ask to begin with a public-company example. Keep confidential documents out of the booking form and agree on an appropriate sharing process before providing restricted material.

How are software and hands-on services scoped?

Treat software access, implementation work, and recurring research support as separate scope decisions. Confirm which services are available, who does the work, and what is included.

The hands-on service lanes on this prototype are proposed packaging, not confirmed commercial offers.

What will it cost?

Confirm pricing for the software scope, included usage, any setup work, and recurring services. An introductory assessment and an enterprise subscription should have clearly stated, separate terms.

This prototype does not publish an unverified price, free-trial duration, or outcome guarantee.

Your next recommendation

Make your next recommendation easier to explain.

Bring a company, a shortlist, or the brief you’re trying to answer.

  1. See the workflow that matches the job in front of you.
  2. Examine the reasoning rather than accepting a score.
  3. Discuss what your team would need to use it in practice.

Your assessment demo

Your starting point: find relevant companies.

Your demo request

Prototype mode: this form previews your request locally. It does not send your details or book a meeting.