Ideal pilot profile
A representative Microsoft BI estate with SQL Server, SQL Agent, SSISDB, SSRS, and SSAS Tabular where access can be coordinated.
Pilot assessment
A bounded first assessment, not a separate product.
A pilot is the first practical version of an assessment walkthrough: confirm the estate slice, run the evidence workflow where access allows, and test whether the outputs are useful enough for modernization planning.
What it validates
Connector coverage, warning visibility, scoring usefulness, recommendation clarity, reporting outputs, and security handoff.
What the client gets
Inventory, dependency evidence, coverage gaps, complexity/risk signals, recommendations, CSV exports, and printable summary.
What remains honest
Partial access, unsupported patterns, and low-confidence dependencies are surfaced as caveats rather than hidden.
Current pilot posture
Core collection, ingestion, scoring, reporting, and end-to-end validation flows are in place; representative live estate validation is next.
Go/no-go
Proceed when the assessment produces useful evidence, explainable gaps, and enough output to plan next modernization steps.
How it differs from a walkthrough
The walkthrough is the conversation. The pilot is the scoped run.
The assessment walkthrough reviews fit, output shape, access model, and security posture. A pilot starts only when there is a bounded estate, agreed validation criteria, and a practical collection path.
Service relationship
It sits inside assessment services.
Pilot scope, evidence review, roadmap interpretation, and executive or partner readout support should be handled as explicit services around the TangleMap evidence.
Review servicesNext step
Scope a first pilot
If the estate slice is already clear, start the pilot conversation directly. The first step is confirming target systems, access model, collector host, expected outputs, and validation criteria.