Confidential-data AI assessment

We find the work AI can take on, starting from the information you handle.

Contracts, meeting minutes, customer information, quotes, internal know-how. Your company holds plenty of information AI could use, yet you can't tell whether it is safe to hand it to an external AI as is. This assessment is for executives and back-office teams at small and mid-sized companies, and we think it through with you from there.

Common themes by industry

Every industry gets stuck for different reasons. Our industry pages cover the usual problems and how Cor. works alongside you.

  • Organizing clinical data, patient response, information security, AI strategy

  • Contract review, applications & registration, deadline management, subsidy applications

  • Labor management, design changes, safety checks, passing on know-how

  • Visual inspection, passing on know-how, equipment maintenance, inventory management

  • Test workload, parent communication, surveys & reports, ICT roster management

Is this where you are stuck?

  • You don't know whether confidential data can go to an external AI.
  • You don't know where to start, and time keeps passing.
  • When you ask a vendor, the talk jumps straight to a large development project.

Terms used on this page

Cloud AI
Generative AI provided by an outside vendor. What you enter is sent outside your company.
Local LLM
Generative AI that runs in your own environment, without sending data outside your company.
PoC
Proof of concept: a small trial before production to check that something works.

How we proceed

We don't start by building. Instead of opening with technology, we first put into words what to handle and how.

  1. On-site interviews

    We hear how your work flows and what is getting in the way.

  2. Taking stock of tasks

    We look at your current work and list the tasks AI could take on.

  3. Classifying data

    We sort the data you handle by how confidential it is.

  4. Separating cloud AI and local LLM use

    We separate what may go to an external cloud AI from what should stay with a local LLM.

  5. Sorting out risks

    We review four points: where to draw the line on information given to AI (input boundaries), access rights, operation logs, and human approval.

  6. Setting a direction

    We set a direction on whether to move on to a PoC.

What you have after the assessment

When the assessment ends, you have documents you can use for the next decision.

  • An inventory of tasks that are candidates for AI
  • Your data classified, with how to handle each kind
  • Risks and how to address them
  • A proposed direction if you move on to a PoC

Choosing what comes next

  • Move on to a local LLM / AI infrastructure PoC
  • Move on to a small-scale production build
  • Decide not to build anything yet

The assessment may conclude that it is better not to build yet. We tell you that conclusion plainly too. Whichever you choose, the assessment is designed to give you the material to decide your next step.

Cost

Costs vary depending on the problem and scope. Our estimates make the assumptions, risks, and scope of work clear; the formal price and schedule are confirmed after requirements review.

Related work and case studies

See all work and case studies

Other services

Start by checking the information you handle.

Discuss a confidential-data AI assessment

The button takes you to our contact page, where our AI receptionist Cloudia will ask what you need.