Equipment
Ordered items received, serial numbers recorded, approved configuration verified, and physical condition documented.
Deployment method
One controlled method. A timeline matched to scope.
Every package moves from evidence to design, implementation, validation, and acceptance. Focused tiers combine gates; the $250,000 Operating Layer uses the complete six-month sequence; Enterprise uses a custom rollout plan.
Package timelines
Controls stay consistent as delivery depth changes.
Reference durations begin after contracting and required access. Client delays, hardware availability, vendor dependencies, changed requirements, and technical findings may change the schedule.
| Package | Reference duration | Delivery shape | Primary acceptance record |
|---|---|---|---|
| Foundation · $25k | 4–6 weeks | Discover, assess, prototype, evaluate, roadmap | Prototype evidence and prioritized implementation plan |
| Workflow Launch · $75k | 8–12 weeks | Discover, design, integrate, test, train, stabilize | Approved workflow tests, documentation, and handoff |
| AI Operations · $100k | 3–4 months | Design knowledge and agent layer, connect systems, release workflows, enable teams | Retrieval, agent, integration, workflow, and training evidence |
| Operating Layer · $250k | Six months | Complete six-gate infrastructure, integration, adoption, and transition program | G1–G6 package and final acceptance record |
| Enterprise · Contact sales | Custom | Program roadmap with workstreams, waves, dependencies, and negotiated governance | Milestone and rollout acceptance defined in the Enterprise SOW |
$250k Operating Layer schedule
From discovery to managed transition in six controlled gates.
This complete sequence is the reference for the $250,000 package. Smaller packages combine relevant gates; Enterprise expands them into a custom program plan.
Month 01 / Discover
Business and technical baseline
Confirm executive sponsor, priority use cases, current systems, data classes, access constraints, workflow owners, success measures, and known risks.
Month 02 / Design
Architecture and scope baseline
Finalize bill of materials, target architecture, data-flow map, access matrix, model and license candidates, workflow specifications, evaluation set, project plan, and acceptance criteria.
Month 03 / Install
Compute and local AI foundation
Receive and inventory equipment, configure the two nodes, establish access, install the approved runtime, configure storage and backup, load the initial knowledge collection, and complete baseline tests.
Month 04 / Integrate
Hermes, CRM, and workflow staging
Configure the agent’s approved role and tools, connect named systems, implement priority automations, create exception paths, and test in a staging or otherwise controlled environment.
Month 05 / Validate
User acceptance and training
Execute the agreed test cases, address severity-ranked defects, run role-based training, confirm operating procedures, and obtain acceptance or a written punch list for each release candidate.
Month 06 / Transition
Stabilization, documentation, and handoff
Monitor agreed workflows, address in-scope defects, complete documentation, verify support contacts, reconcile licenses and assets, and close final acceptance against the executed criteria.
Delivery gates
Evidence required to move forward.
These are reference gates. The final project plan may combine, reorder, or expand them based on the approved environment.
| Gate | DGM evidence | Client decision | What it does not prove |
|---|---|---|---|
| G1 · Discovery complete | Inventory, use cases, owners, risk log | Confirm priorities and assumptions | That every requested use case is feasible |
| G2 · Design approved | Architecture, BOM, licenses, tests, schedule | Approve design and purchasing basis | Future vendor pricing or availability |
| G3 · Foundation ready | Asset record, runtime checks, backup evidence | Accept installed baseline | Business workflow acceptance |
| G4 · Integration ready | Connector and workflow test results | Authorize controlled user testing | Error-free operation in every scenario |
| G5 · Production release | UAT record, training, open-issue list | Approve release or documented punch list | Revenue, savings, or ROI guarantee |
| G6 · Final acceptance | Final inventory, documentation, closeout record | Sign acceptance or cite unmet criteria | Performance of third-party services after close |
Acceptance model
Functional tests, not vague satisfaction.
The lender-supporting acceptance outline in the repository provides a starting point; the executed SOW replaces it with client-specific tests.
Systems
Named model, retrieval, agent, CRM, and workflow tests pass the agreed criteria or are listed on an accepted punch list.
Enablement
Required training, operating guides, administrative access, license records, and support contacts are delivered.
Acceptance is not a business-outcome warranty. It confirms delivery against agreed technical and service criteria. AI output quality remains probabilistic, and third-party uptime and policy changes remain outside DGM’s control.
Shared responsibilities
What the client must provide.
Delays in these dependencies may change the schedule through the contract’s change-control process.
Executive sponsor + owners
A decision-maker, day-to-day project contact, workflow owners, subject-matter reviewers, and administrators for connected systems.
Authorized access
Timely access to approved systems, test accounts, APIs, documentation, facilities, networks, and relevant vendor support.
Lawful data
Data the client is authorized to provide and process, with required notices, consents, retention decisions, and subject-matter validation.
Review + decisions
Feedback, approvals, user testing, training attendance, and acceptance decisions within the time windows agreed in the project plan.
Before scheduling
Match the package to the next operating outcome.
A scoping call confirms priorities, systems, data sensitivity, purchasing constraints, internal ownership, and whether the selected package has the right boundary.