Engagements from $25,000Five delivery pathsScope controlled by SOW

Packages + commercial structure

Choose the next useful layer.

Four published packages create a path from focused validation to a complete operating layer. Enterprise programs sit above the $250,000 reference deployment and are priced after discovery.

Five delivery paths

A package ladder built around operating maturity.

Prices are reference package amounts before applicable taxes. Final SOWs define included systems, workflows, licenses, hardware, support, dependencies, and acceptance criteria.

Foundation01
$25k4–6 week sprint

One priority use case, tested enough to make the next investment decision with evidence.

  • Readiness and process assessment
  • One controlled workflow prototype
  • Risk and data-access register
  • Training and implementation roadmap
Workflow Launch02
$75k8–12 week implementation

One operating team, one core system, and a focused automation lane released with controls.

  • Up to three approved workflows
  • One core-system integration
  • Scoped Hermes agent
  • Training and 60-day support
AI Operations03
$100k3–4 month implementation

A cross-functional knowledge, agent, and workflow layer spanning more than one system.

  • Business knowledge retrieval
  • Up to five approved workflows
  • Up to two core integrations
  • Training and 90-day support
EnterpriseAbove reference scope
Contact salesCustom program

For multi-site, multi-entity, regulated, high-availability, or broader transformation programs beyond the $250,000 deployment.

  • Custom architecture and rollout plan
  • Multiple agents, teams, and integrations
  • Expanded governance and security evidence
  • Negotiated support and service levels

Hardware is included only when expressly scheduled. Third-party licenses and usage are subject to vendor terms and package allowances. Enterprise pricing is not published because architecture, rollout, and operating obligations vary materially.

$250k Operating Layer allocation

One full-deployment total. Six distinct categories.

This planning allocation applies to the $250,000 package and is mirrored in the sample invoice. It is not the allocation for the $25,000, $75,000, $100,000, or custom Enterprise scopes.

CategoryReference amountWhat it coversClassification note
Equipment$36,000Two Mac Studio allowances plus approved storage, backup, network, power, and security accessoriesPhysical items only; final BOM and vendor quotes control
Software / API allowance$24,000Named third-party access for up to one year where listed in the final scheduleLicenses and usage allowances; not DGM-owned software
Engineering + integration$116,000Discovery, design, local AI, knowledge retrieval, Hermes configuration, CRM integration, automations, and functional workflowsProfessional implementation services
Training$24,000Role-based training, administrator enablement, user materials, and agreed session recordingsTraining services
Support + maintenance$30,000Six-month issue intake, maintenance, in-scope defect support, and operating guidanceSupport services with defined targets and exclusions
Program + acceptance$20,000Project governance, security documentation, test coordination, asset reconciliation, and closeoutProject and acceptance services
Total$250,000Operating Layer reference packageBefore applicable tax; executed documents control
Hardware allowances are not current Apple price quotes. Final models, configurations, quantities, warranty selections, taxes, and delivery costs are approved during design and supported by available vendor documentation before purchase.

If financing is pursued

The financing decision is separate from the DGM scope.

A client may choose to discuss financing with independent financing sources. Those parties determine eligibility, collateral treatment, financed amount, documentation, pricing, term, payment, and approval.

Due-diligence support

Documents that reconcile to one another.

Final versions are produced from the executed commercial and technical scope. Repository samples are outlines for review—not signed agreements.

01

Commercial evidence

Itemized invoice, payment schedule, vendor quotes where available, equipment ownership, taxes, shipping, and named allowances.

02

Delivery evidence

Statement of work, bill of materials, implementation schedule, delivery gates, acceptance criteria, and client responsibilities.

03

Ongoing obligations

Software and license schedule, account ownership, renewal responsibility, support and training terms, exclusions, and change control.

Consistency rules

Every final document should tell the same story.

These rules reduce ambiguity for the buyer, vendor, delivery team, accountant, and any independent financing source.

01

Names + dates match

Contracting entity, client entity, addresses, effective dates, term, and payment schedule are consistent across executed documents.

02

Categories reconcile

Equipment, licenses, services, training, and support amounts reconcile to the signed order and invoice without re-labeling.

03

Specifications are traceable

Each physical item maps to the approved BOM and available quote; each license maps to the software schedule.

04

Acceptance maps to scope

Each deliverable has a responsible party, planned date, measurable criterion, evidence record, and acceptance process.

Payment structure

Every package becomes binding only in the executed agreement.

DGM and the client must agree package selection, payment timing, deposits, procurement treatment, change orders, taxes, late payments, suspension rights, and cancellation terms before work begins.

No web-page offer: This page provides a reference commercial model only. A binding offer requires a written proposal or order form accepted by authorized representatives, together with the controlling terms and statement of work.