Engagement options

Match the engagement to what is known.

Do not buy a large build to answer a small question. Start where uncertainty lives, create evidence, and expand only when the next investment has a defensible reason.

Find the right starting point Compare options

01 / Diagnose

Deployment Diagnostic

Turn a promising but uncertain use case into a grounded delivery decision.

Duration: Two weeks
Best when: The outcome matters, but scope, data, workflow, or architecture is not yet trustworthy.

Core outputs

Outcome, users, workflow, and baseline
Prioritized requirements and use cases
Data, access, security, and technical assessment
Architecture direction and key decisions
Delivery options, risks, milestones, and estimate range
Proceed, reshape, or stop recommendation

02 / Build

Embedded Build

Prove one valuable workflow with production constraints in the room.

Duration: Six weeks
Best when: A sponsor, use case, users, and access path exist, and a bounded release can create value.

Core outputs

Working increments and weekly demonstrations
Acceptance criteria and evaluation evidence
Representative-data integration and technical notes
Decision, risk, issue, and change records
Handoff notes and production-path recommendation
Measured evidence and follow-on options

03 / Deploy

Production Deployment

Take a validated workflow through production readiness, launch, and operational acceptance.

Duration: Twelve weeks
Best when: The workflow has evidence behind it and now needs integration, controls, adoption, and a dependable release.

Core outputs

Production architecture and delivery plan
Integration, controls, and release evidence
Monitoring, incident paths, and runbook
Weekly status and executive reporting
Stakeholder, vendor, and dependency coordination
Training, acceptance, and transition plan

04 / Optional extension

Stabilize & Transfer

Strengthen reliability, adoption, and client ownership after the production release.

Duration: Four weeks
Best when: The system is live and focused support will reduce transition risk or accelerate internal ownership.

Core outputs

Production observation and issue triage
Runbook and support-path refinement
Operator coaching and user enablement
Knowledge-transfer evidence
Final performance and risk review
Closeout or follow-on recommendation

Commercial guardrails

Clear enough to govern. Flexible enough to learn.

Scope

Each engagement names the outcome, in-scope workflows, deliverables, assumptions, exclusions, and acceptance process.

Cadence

Working sessions and demonstrations are scheduled up front. Written status makes decisions, risk, cost, and progress visible.

Changes

New facts can reshape the work. Material scope, timeline, or cost changes are documented and agreed before they are taken on.

Ownership

Client data, systems, policies, approvals, and operational decisions remain under client control. Deliverable rights are defined in the signed agreement.

Timing and structure are planning ranges, not commitments. Final scope, staffing, fees, expenses, intellectual-property terms, security obligations, and acceptance terms are defined in a mutually executed agreement.

How selection works

Use the smallest engagement that can create a responsible decision.

Use the Deployment Diagnostic when access, ownership, or value is uncertain. Use the Embedded Build for one bounded workflow. Use Production Deployment when the workflow is validated and ready for the controls, integration, and adoption work that production requires. Add Stabilize & Transfer only when post-launch needs justify it.

Run the readiness check →