The pilot

Two weeks to a decision.

A pilot is twenty-five laptops in the firm’s own environment, pushed through Intune or Jamf in an afternoon, silent for the people using them. Two weeks later the firm decides on evidence, not a vendor deck.

25
laptops in the first ring. Enough to see real patterns, small enough to be an easy yes.
1
standard MDM push. The same motion IT uses for any other software.
0
changes for employees. Same tools, same logins, same replies.
14
days to the review. Three things on the table, one decision.
How it runs

The fourteen days, as they actually go.

Day 0

One push

IT sends one signed package to a twenty-five device group. Intune or Jamf, the same push as any other software rollout. Employees notice nothing.

Day 1

The map starts filling

Every AI tool, site, and agent in actual use begins to show up, usually including a few nobody expected.

Week one

The first catches

Client identifiers, account numbers, and deal terms are stripped before prompts leave the device and put back in the replies. Every event signs to the record.

Week two

The picture settles

Which tools carry real work, what they cost, what sits idle. The record deepens without anyone tending it.

Day 14

The review

Three things on the table, generated from the firm’s own two weeks. The decision gets made on evidence.

What the firm holds

Three things, on the table.

01 · The usage map

Every AI tool actually in use

Browser tools, desktop apps, coding agents, and the wrappers in between, with first-seen dates and adoption counts. Aggregate numbers, never employee dossiers. Most firms meet at least one tool they had never heard of.

02 · What almost left

The catches, itemized

The client name in a prompt, the account number in a pasted table, the deal term in an uploaded file. Each one caught before it reached the model, restored in the reply, and signed onto the record. This is the page that settles the should-we-worry debate.

03 · The Evidence Pack

The two weeks, exported

What ran, what was protected, and the signed record behind both, in one document. Ready for a client questionnaire, an examiner, or the board, and verifiable offline without taking Proxara’s word for any of it.

The honest mechanics

What IT does. What employees notice.

For IT

One signed package and one configuration profile, pushed to a device group with the tools already in place. macOS and Windows. About an hour of real work, most of it watching devices check in green.

Deployment in detail
For everyone else

Nothing to install, nothing to learn. The same AI tools answer the same way. Sensitive details are stripped on the way out and put back in the reply, with a quiet confirm in the browser. The pilot never blocks anyone.

What a pilot asks of the firm: one decision-maker’s yes, one pass through the security documentation, one hour from whoever runs the MDM.

After day fourteen

Both endings are clean.

If the firm continues

Scope widens from twenty-five devices to the fleet through the same MDM motion. Nothing reinstalls, and the record carries forward, so the evidence shown to an examiner next year starts on pilot day one.

If it walks away

The same push removes the agent cleanly, and pilot data is deleted on a stated schedule. That commitment goes in writing before anything installs.

Start with twenty-five laptops.

Tell us about the firm. The install package, the security documentation, and the pilot plan come to you.

Book a call