A Dynamics 365 app that turns an implementation's scope into a defensible, role-costed, week-by-week estimate — scope, staffing, pricing, and approval in one connected workflow.
Why scoping a Dynamics 365 implementation is hard, how Microsoft's Business Process Catalog frames scope, and what a structured estimate fixes. Plain English, eleven slides — the context the role guides build on.
One continuous run through the real tool, photographed at every step — from an empty Project form to a staffed, priced, phased estimate ready for approval. Fifteen screens, seven stages, and at each one: what you fill in, what it's for, and what the tool builds behind the scenes.
If you only read one page on this site, read this one.
From a first draft to a signed-off estimate and into the SOW — and who picks it up at each hand-off. The estimator builds and submits; the approver reviews and approves or rejects; a rejection loops back to the estimator to revise and re-submit; once approved, the scope and pricing are copied into the SOW.
Each role's steps become a track — pick yours below.
The site is organized by goal and by the hand-offs between people — not by feature. New here? Start with Get Started. Otherwise jump straight to your track.
What it is, how it flows, the vocabulary, and how to get in.
From nothing to a scoped, staffed, priced, phased estimate.
Tune staffing, rebalance the plan, run what-ifs, re-version, re-price.
Receive, review, and decide — and how routing works.
Produce a client-safe scope & pricing table and copy it into the SOW.
Maintain the catalog, cards, policies, and rules everything reads from.
Read the commercial shape and the approval record across estimates.
A single model-driven app over a Dataverse data model, extended by server-side compute (custom APIs + plugins) and Power Automate, with a couple of light external edges. No external system of record — the estimate lives entirely in Dataverse.
The HSO Estimator is a Dynamics 365 model-driven app for HSO US pre-sales and delivery. This page is the entry point for everyone who needs to understand how an estimate is scoped, staffed, priced, validated, and approved.
Create the estimate, select scope from the process catalog, generate lines, roles, and team.
Lay staffing across phases and weeks, build the timeline, and validate against configured rules.
Cost and price every role from controlled cards, with the source of each rate on the record.
Policy-based, multi-level sign-off routed automatically by cost, price, and margin thresholds.
A factor-driven model that turns an entity inventory into a defensible migration estimate.
The process catalog, templates, rules, security, and customer-review surface it all rides on.
A short guide per role — what the Estimator means for you and where to go — each linking to its slide deck. Plus a business primer for everyone.
The primary guide: scope from the process catalog, generate lines, roles, and team, price from rate cards, plan the WBS, and submit for approval. How the tool builds the estimate so you can judge it.
One continuous run through the real tool: create a project, type the estimate header, scope it in the Deliver Rollup, generate roles and team, lay out the timeline and WBS, add data migration, and submit for approval — with every field's purpose and what each step builds behind the scenes.
The case for a single estimation platform: consistency by construction, controlled pricing, and policy-based approval at scale. Outcomes, not mechanics.
What sales sold you, in a structure you can run a project from: the WBS and timeline as your resourcing baseline, how the hours were derived, the margin envelope, and the approval record.
Why scoping a Dynamics 365 implementation is hard, how the Microsoft Business Process Catalog frames scope, and what a structured estimate fixes. Read this before the role guides.
28 narrative feature guides across the six pillars, prev/next navigable, each grounded in the real tables, custom APIs, and PCF controls behind it. Plus six pillar overview pages.
