RODGERS INTELLIGENCE GROUP · DENVER, COLORADOFree intake Test Kit →
Menu
Illustrative photograph of printed worksheets and a laptop on a wooden desk
Private AI

A USEFUL AI WORKFLOW INSIDE YOUR OWN BOUNDARY.

You cannot send client information to public AI services, and the work still needs a useful AI workflow.

Discuss this
Who it is for

CLIENT INFORMATION STAYS INSIDE THE FIRM.

Firms that cannot send client information to public AI services. The engagement covers one workflow in one agreed environment on your own hardware or a private host. The first discussion uses a sample workflow and test data.

Send a brief
What you get

WHAT THE ENGAGEMENT DELIVERS.

Scope memorandumWhat the workflow does, where it runs, and what is out of scope, written down first.Send a brief →
One workflow, your environmentOne AI workflow on the firm's own hardware or a private host.Send a brief →
Memory record and acceptanceAn inspectable memory record with documented update rules, and a written acceptance check before any live data is considered.Send a brief →
An illustrative photograph of an office at dusk with desk lamps on
How the engagement runs

ASSESS. PILOT. HAND OVER.

One workflow, one agreed environment, agreed before work starts.

01

Assess

Own machine or private host, proposed workflow, recovery needs.

02

Pilot

Connect one agreed workflow to a reviewable memory store.

03

Hand over

Acceptance checks, operator documentation and support boundaries agreed before work starts.

Send a brief
Worked example

WHAT THE MEMORY RECORD SHOWS.

DEMONSTRATION, NOT A CLIENT RESULT

Sample memory record, illustrative only

  • Scope: the one workflow the record is allowed to hold.
  • Update rules: how entries are added, corrected and retired.
  • Acceptance check: the written test before live data is considered.
  • Operator documentation: who runs it and how failures are handled.
Illustrative sample, not a client result.
Illustrative photograph of a desk with a laptop, a monitor and an open notebook

Illustrative sample, not a client result. Photos on this page are illustrative, not clients.

Talk to Mike →
Scope and exclusions

What is included. What is not.

Included
  • One workflow, one agreed environment; hardware fit, hosting, access rules, retention, integrations and support agreed per engagement
  • Scope memorandum, inspectable memory record with documented update rules, written acceptance check before any live data
Not included
  • Not a security certification and not a promise that an environment is already deployed
  • Bounded tooling tests do not prove a production rollout, a recovery time, fit with your hardware, memory accuracy, privacy assurance or a security certification
Price

Scoped after a short brief

Questions

REAL QUESTIONS, PLAIN ANSWERS.

Do we need to send client files to start?

No. The first discussion uses a sample workflow and test data.

Is this a security certification?

No. It is not a security certification, and it is not a promise that an environment is already deployed.

What does it cost?

Scoped after a short brief.

What do we get at the end?

A scope memorandum, an inspectable memory record and a written acceptance check agreed before live data runs.

Delivery confidence

WHAT IS DELIVERED. WHO DELIVERS IT. CHECKED HOW.

Named accountability and written checks, agreed before work starts. What you can inspect is named below.

What is deliveredA scope memorandum covering what the workflow does, where it runs and what is out of scope; one AI workflow on the firm’s own hardware or a private host; an inspectable memory record with documented update rules. Handover: acceptance checks, operator documentation and support boundaries.
Who delivers itMike Rodgers, Rodgers Intelligence Group, Denver.
By whenTimeline agreed in the written scope before work starts.
Acceptance checksA written acceptance check before any live data is considered. Acceptance checks, operator documentation and support boundaries are agreed before work starts.
If a check failsIf a written acceptance check fails, the failure is documented and reworked before handoff.
What you get to inspectThe “What the memory record shows” block is a labeled demonstration: DEMONSTRATION, NOT A CLIENT RESULT, an illustrative sample, not a client result. The first discussion uses a sample workflow and test data, so no client files are needed. Demonstrations on this page are illustrative, not client results. The free Client Intake Failure-Test Kit is available to run yourself.
PrerequisitesOne workflow and one agreed environment agreed before work starts; hardware fit, hosting, access rules, retention, integrations and support agreed per engagement.
Out of scopeNot a security certification and not a promise that an environment is already deployed. Bounded tooling tests do not prove a production rollout, a recovery time, fit with your hardware, memory accuracy, privacy assurance or a security certification.
Next step

SEND THE BRIEF.

The workflow you need inside your boundary, and the environment it must run in. Test data is enough to start.

What to send
  • The workflow that needs to stay inside the firm.
  • Where it must run.
  • What recovery looks like.
Photos on this page are illustrative, not clients.