Engagement options
Match the first engagement to the decision.
Discovery and advisory create the evidence for a platform or governance decision. Selection and sourcing follow only when justified; resale occurs only where authorization is documented. FDE carries approved choices into integration, migration, build, adoption, optimization, and support.
01DiscoverVerify the decision, use cases, estate, constraints, and owners.
02AdviseDefine target capabilities, options, evidence, and tradeoffs.
03Select / SourceChoose through diligence; resale only where authorized.
04Implement via FDEIntegrate, migrate, build, govern, test, and transfer.
05Adopt / Optimize / ExpandMeasure quality, cost, risk, adoption, and value.
Discovery and advisory entry
Two buyer decisions. One specialist control layer.
AI trackAI Platform Decision Sprint
A bounded engagement for use cases, model access, knowledge and retrieval, agents, evaluation, safety, adoption, and cost.
- Priority use-case and readiness map
- Capability and architecture options
- Evaluation, risk, and sourcing criteria
- Recommendation and FDE implementation brief
Explore AI Platforms & Adoption →Data trackData Platform Decision Sprint
A bounded engagement for lakehouse or warehouse, integration, streaming, catalog and lineage, quality, security, semantics, data products, and FinOps.
- Estate, workload, and constraint map
- Target capabilities and migration options
- Evaluation, operating, and sourcing criteria
- Recommendation and FDE implementation brief
Explore Data Platforms & Management →Specialist trackGovernance & Assurance
Use this as the primary track when ownership, approvals, controls, evidence, monitoring, or assurance is the material decision.
- Inventory, maturity, and risk classification
- Operating model and decision rights
- Controls, evidence, monitoring, and exceptions
- Standards and regulatory mapping starters
Explore Governance & Assurance →
Governance & Assurance packages
Preserved specialist engagements.
These packages remain available as a focused governance track and as proportionate control-layer modules inside AI or Data work.
- Duration
- Two weeks
- Best when
- Inventory, ownership, risk, evidence, or immediate exposure is unclear.
Core outputs
- Priority system and use-case inventory
- Current-state maturity and evidence review
- Initial risk tiers and material gaps
- Containment actions and decision brief
02 / DesignOperating Model Design
Define the lifecycle, decisions, controls, and evidence the organization will own.
- Duration
- Four weeks
- Best when
- Leadership needs one usable model across business, technology, data, risk, and assurance.
Core outputs
- Lifecycle, forums, decision rights, and RACI
- Risk tiers and gate criteria
- Policy, standards, and control starters
- Evidence model and 90-day activation plan
- Duration
- Eight weeks
- Best when
- The model is agreed and owners need working records, controls, monitoring, and acceptance.
Core outputs
- Populated inventory, cards, and assessments
- Configured gates, decisions, and evidence
- Evaluation, monitoring, and oversight plans
- Exercises, training, runbook, and transfer
- Duration
- Monthly
- Best when
- The operating model is live and disciplined reviews, evidence, and change management are needed.
Core outputs
- Portfolio, gate, control, and exception reviews
- Indicator and incident reporting
- Evidence and remediation tracking
- Quarterly renewal or expansion decision
Select and source
Capabilities before products.
Existing agreements, architecture, identity, data boundaries, portability, security, evidence, operating ownership, adoption, and total cost shape the shortlist. Representative technologies are reference options—not partners, endorsements, certifications, implementation-experience claims, or required products.
Commercial boundaryPlatform selection and sourcing is available. Resale, procurement routing, pricing rights, or partner benefits are discussed only where current authorization is documented.
Implementation handoff
Move the approved decision into FDE.
A decision brief becomes an implementation backlog, architecture and decision records, access plan, acceptance evidence, adoption plan, and operating handoff. FDE can cover integration, migration, application or data-product build, validation, adoption, optimization, and ongoing support within a separately agreed scope.
See Forward Deployed Engineering →
Commercial guardrails
Bounded enough to decide. Flexible enough to learn.
BoundaryName workloads, systems, uses, data, jurisdictions, vendors, environments, and exclusions.
AuthorityClient owners retain business, risk, legal, security, privacy, procurement, and deployment decisions.
EvidenceRecommendations and controls link to current evidence. A product field or policy alone does not prove effectiveness.
ChangeNew autonomy, data, vendors, jurisdictions, integrations, economics, or obligations trigger review.
Packages and sprint descriptions are planning ranges—not guarantees of compliance, certification, regulatory approval, model behavior, risk reduction, cost savings, or business outcome. Final scope, fees, acceptance, and review responsibilities belong in an executed agreement.
Selection rule
Use the smallest engagement that can create a responsible next decision.
Choose AI when adoption and AI-platform capability are central. Choose Data when the estate, movement, quality, or product layer is central. Choose Governance when accountability and assurance are the decision. Combine them when the boundaries are inseparable.
Choose a starting path →