The 60-day node pilot

From possibility to a working node.

A bounded engagement that installs one right-sized appliance, connects one useful workflow, establishes the trust boundary, and leaves behind evidence you can inspect.

The promise

Small enough to finish. Real enough to matter.

The pilot does not attempt to automate the organization. It chooses one consequential working loop and proves that local custody, useful AI assistance, governed memory, and inspectable evidence can live together.

The path

Five phases. One continuous record.

Days 1–7

Frame

Walk the real workflow. Define purpose, users, authority, data boundaries, failure conditions, and success criteria.

  • working-system map
  • trust-boundary statement
  • pilot acceptance criteria
Days 8–21

Prepare

Source or confirm hardware, burn in the node, harden access, establish backup, and prepare approved content.

  • appliance build record
  • configuration baseline
  • content intake register
Days 22–32

Install

Place the node, connect the approved workflow, establish identities and roles, and demonstrate the first bounded loop.

  • installed node
  • first workflow
  • operator orientation
Days 33–52

Prove

Use it with real work. Tune retrieval and interfaces. Test refusal, failure, recovery, export, and human review.

  • use and issue log
  • evidence receipts
  • recovery demonstration
Days 53–60

Decide

Review outcomes, hand over the operating record, and decide whether to steward, expand, redesign, or stop cleanly.

  • verification report
  • 30/60/90 roadmap
  • expansion decision

What the client receives

Not just a demonstration.

Every claim in the pilot should resolve to an artifact the client can inspect, export, and hand to leadership, staff, auditors, vendors, or future operators.

01Installed node and configuration summary
02Authority, access, and trust-boundary map
03Approved content register and source map
04One configured working workflow
05Backup, recovery, and export procedure
06Staff orientation and operator notes
07Attested demonstration and verification report
0830/60/90-day improvement roadmap

A good first workflow

Consequential, bounded, and already understood by the people doing it.

  • Repeats often enough to learn from
  • Depends on documents, decisions, or handoffs
  • Has a human owner who can review output
  • Benefits from continuity across staff or time
  • Can be demonstrated without exposing prohibited data
  • Has an honest stopping condition

Not the first pilot

Do not begin with everything.

We will not propose autonomous authority, enterprise-wide ingestion, unrestricted memory, or a silent replacement for a regulated system of record as the first move.

One useful loop is enough to establish the truth.

Commercial path

The appliance sets the starting envelope.

See appliance details
Micro

From CAD $5,400

Appliance, onboarding, and first month. Then $400/month.

Pro

From CAD $10,750

Appliance, onboarding, and first month. Then $750/month.

Server

From CAD $30,000

Appliance, onboarding, and first month. Then $2,500/month.

Complex environments

Scoped proposal

Rack, multi-site, regulated, or sovereign systems receive a written discovery and implementation scope.

Planning starting prices in Canadian dollars before applicable tax. Hardware, travel, integrations, regulatory requirements, and local installation conditions are confirmed before signature.

Begin with the real work

Show us the workflow that cannot afford to forget itself.

We will walk it with you, identify the smallest honest node, and return a bounded pilot scope.

Scope a pilot