TLG Solutions Book an assessment

Prepare for the first conversation

Six short questions about your data, your estate, your people and the decision in front of you. The result is a brief to share with colleagues, written as the questions worth settling first.

Your answers stay in this browser. Nothing is stored or sent unless you choose to send it.

Six questions, one brief.

Choose what applies, skip what does not, and change any answer before the brief is prepared.

Private AI scoping questions ยท tlgsolutions.co.uk/decision-brief.html

Tick what applies, then print this page to share it, or send your answers to info@tlgsolutions.co.uk.

01Your data

Where data lives, and what it contains, decide where a model may read it.

Where do the documents and data live today?
What does it include?

Questions to settle

  • Which documents should a model never read, whatever the safeguards?
  • Who owns each source, and who may approve its use?
  • Will a data protection impact assessment be needed?

02Your estate

The estate you already run and audit is usually the natural place for a private platform to live.

What do you run today?
Do you have GPU capacity?

Questions to settle

  • Where could a platform run, and who would operate it?
  • Is a model on compute you control required, or is a managed model in your own subscription acceptable?
  • What does your change process require before new infrastructure is deployed?

03People and access

A platform must never become a way round the permissions you already have.

Who would use it?
Should everyone see the same documents?

Questions to settle

  • Which identity provider would people sign in through?
  • Do existing groups match who should see what?
  • Should conversation history be kept, and who may read it?

04Your documents

What it must do, and how fresh it must be, shape the retrieval design and how answers are tested.

What should it do with documents?
How often do the documents change?

Questions to settle

  • What happens if an answer is wrong, and does a person check it before it is used?
  • Which real questions, with known answers, could test it?
  • How quickly must a changed document appear in answers?

05Assurance

Knowing who must be satisfied tells you which documents and tests the work has to produce.

Who will need to review or approve it?

Questions to settle

  • What will your security team need to see before go live?
  • Should prompts and answers be logged in full, as metadata only, or briefly?
  • Which policies on AI already apply?

06Your decision

A first conversation is most useful when it is aimed at the decision you actually have to make.

Which decision is in front of you?
Who makes it?

Questions to settle

  • What would make the answer no?
  • What do the decision makers need to see, and in what form?
  • What would need to be true for this to be worth pursuing?

How an engagement starts

Every engagement opens the same way, whichever offer it leads to. Nothing is built, and none of your data is read, until the scope is agreed.

  1. 01

    A first discussion

    You tell us what you want AI to do and where your data has to stay. If you have prepared a brief on this page, bring it. We sign a mutual NDA first if you ask.

  2. 02

    An agreed scope

    We come back with a scope: what is in it, what is not, and what you receive at the end. Each offer has a fixed scope, set out in writing before work starts.

  3. 03

    Access and data handling, decided first

    Before we see any system or document, we agree which ones we may read, who we speak to, which data is off limits, and how findings are classified and shared. Any access uses accounts your organisation issues.

  4. 04

    Named work products

    The scope names what you receive, such as written findings, use cases ranked by value and by risk, an architecture pack or a working application on your own data.

  5. 05

    Review by your colleagues

    Work products are written for your security, data protection and risk colleagues to review. Open decisions are listed with their options, not settled for you.

  6. 06

    Handover

    What we write for you is yours: code, configuration and documentation, in your own systems. When the work ends, our access is removed and any credentials we used are rotated.

What each offer covers, and what you decide

For your colleagues

The pages a security, risk or procurement colleague will want, in one place.

Ready to talk it through?

Bring the brief, or simply tell us what you are trying to do.

We use these details only to reply to you. Read our privacy notice.

Prefer email? Write to info@tlgsolutions.co.uk.

Thank you. Your request is on its way. We will reply from info@tlgsolutions.co.uk to arrange a first discussion.

That did not send. Please email info@tlgsolutions.co.uk instead, and we will reply from there.