Doku Infrastructure
Back to design partner program
Optional paid diagnosticOne gate, one change class

Power-Critical Gate Diagnostic

Buy the decision before buying the deployment.

For an independent ERCOT data-center developer that sees a real power-critical risk but needs bounded evidence before approving the 90-day design partnership.

Request a 25-minute fit reviewReturn to the full program

No project files are required for the fit review. No paid work or restricted evidence exchange begins without an accepted proposal and the approved legal and security boundary.

10 business daysFrom approved kickoff to outcome review
$15K-$25KTypical diagnostic fee
One gateOne project and one change class
100% default creditWhen the 90-day program is signed within 30 days

When to use it

A smaller paid decision for a buyer who is not ready to approve the full deployment.

The diagnostic is optional. It is useful when the executive has a credible live gate, a consequential interface risk, and access to the responsible team, but needs a documented case before committing $100K-$150K.

Strong diagnostic fit

  • A real power-critical decision is expected within 3-9 months.
  • The consequence crosses at least two organizations or source systems.
  • An executive sponsor and accountable technical authority can participate.
  • The buyer needs evidence to approve, reject, or scope a larger deployment.
  • The minimum necessary evidence can be shared under an approved boundary.

Skip the diagnostic when

  • ·The buyer is already ready to scope and approve the 90-day program.
  • ·There is no live project gate, decision date, or accountable owner.
  • ·The request is generic strategy, document search, or engineering certification.
  • ·The project cannot provide enough evidence to examine one consequence chain.
  • ·The buyer expects guaranteed savings, schedule recovery, or technical approval.

Ten-business-day scope

One bounded investigation. One documented decision.

Doku reconstructs only what is necessary to understand the chosen gate and test one cross-system consequence chain.

$15K-$25K typical feeDefault conversion credit is 100% of the accepted diagnostic fee toward a design partnership signed within 30 days. The customer-specific proposal and signed agreement control.
Days 1-2

Confirm the decision boundary

Name the upcoming gate, responsible executive, accountable technical authority, current process, decision date, and minimum evidence.

Days 3-5

Reconstruct the current state

Map the selected facts, source authority, relevant artifacts, owners, open assumptions, and existing closure path.

Days 6-8

Trace one consequence chain

Test how one changed fact could propagate into engineering, equipment, agreement, schedule, construction, or commissioning decisions.

Days 9-10

Make the proceed or stop decision

Review the evidence gaps, exposure range, proposed 90-day scope, customer burden, security boundary, and recommendation.

Acceptance deliverables

The diagnostic ends with artifacts the sponsor can review.

Gate decision brief

The live decision, date, owner, technical authority, current basis, and unresolved assumptions.

Current-state and authority map

The minimum facts, sources, versions, organizations, and accountable reviewers relevant to the gate.

Illustrative consequence chain

One documented change path across the affected artifacts, decisions, owners, deadlines, and evidence.

Exposure and evidence assessment

A transparent range of schedule, rework, equipment, carrying-cost, or readiness exposure, with assumptions stated.

Proceed or stop recommendation

A decision memo stating whether a 90-day deployment is justified and, if so, its scope, measures, participation, and prerequisites.

Acceptance rule

Each listed deliverable is provided in the agreed format.Sources, assumptions, limitations, and evidence status remain visible.The sponsor can choose stop, wait, or proceed without buying another service.No project outcome, technical approval, or savings result is guaranteed.

Customer participation

A defined burden for the people who hold the facts and decisions.

Executive sponsor

One 45-minute interview to confirm the decision, consequence, budget context, and approval path.

Working team

Two to four focused interviews with the people who own the relevant facts, artifacts, reviews, and closure process.

Outcome review

One 60-minute review with the sponsor and accountable project team to accept the deliverables and choose the next step.

Minimum evidence schedule

Start with a precise request, not a project data room.

The fit review uses no project files. If the diagnostic is proposed, its evidence schedule names the smallest facts and artifacts needed to test one consequence chain.

Gate record

The decision, deadline, owner, technical authority, current basis, and known open assumptions.

Source index

A list of only the relevant systems, files, versions, dates, organizations, and source owners.

One changed fact

The prior and current value, source, effective date, known reason, and any already identified consequence.

Review and decision trail

The existing owners, reviewers, approvals, open actions, deadlines, and closure evidence for the selected chain.

Evidence boundary

Share the minimum evidence only after the rules are approved.

Before evidence

  1. Confirm the contracting partyIdentify the buyer, sponsor, signatory, and accountable technical authority.
  2. Approve legal and security termsUse the accepted NDA, SOW, data schedule, and transfer path.
  3. Minimize the requestExchange only the facts and artifacts required for the chosen gate.

During and after

  1. Preserve source authorityCurrent systems and accountable experts remain authoritative.
  2. Record evidence statusObserved, inferred, proposed, and customer-confirmed information remain distinct.
  3. Complete the agreed exitReturn, retain, or delete information according to the signed terms.

What the accepted proposal must settle

Contracting parties, buyer, sponsor, technical authority, and authorized signatoriesGate, change class, inclusions, exclusions, delivery dates, and customer participationMinimum evidence schedule, permitted transfer path, access, retention, export, and deletionFive deliverables, delivery format, acceptance rule, and documented limitationsFinal fee, payment schedule, approved expenses, written change control, and conversion creditConfidentiality, intellectual property, security, liability, insurance, termination, and exit terms

This public page is planning information. Work begins only after the customer-specific proposal and agreement are accepted.

Outcome review

A paid diagnostic does not force a larger purchase.

01

Stop

The problem, timing, evidence, authority, or value does not justify a Doku deployment. The diagnostic closes with the delivered findings.

02

Wait

The need is credible but the gate, project, team, or evidence is not ready. The decision memo records the condition for re-entry.

03

Proceed

The buyer and Doku agree a customer-specific 90-day scope, measures, participation model, diligence path, and proposal.

Start with fit

Bring the gate. Keep the first conversation high level.

Use 25 minutes to establish the decision, timing, current process, likely consequence, responsible people, and whether the diagnostic is the smallest justified next step.

Request the fit reviewReview commercial boundaries

This page is a public, non-binding summary. Only an accepted customer-specific proposal and signed agreement create an engagement.