How Microsoft Consulting Firms Charge: Hourly, Retainer, and Fixed-Price Models Compared

Published 2026-08-02 | Updated 2026-08-02

Microsoft consulting firms charge through three primary structures. Time and materials bills hourly or daily rates and leaves scope risk with you. Fixed price carries a defined deliverable at a defined number, so delivery risk sits with the firm against a signed scope. Retainers and subscriptions buy standing senior capacity or standing outcomes, billed monthly or quarterly. Most enterprise Microsoft consulting engagements combine two of the three, and the useful comparison is never the rate card. It is where the risk sits when scope moves.

Time and materials. You pay for hours worked at agreed rates. It fits genuinely uncertain work: discovery, rescue triage, or a backlog whose shape changes weekly, which is also where senior Microsoft staffing models live. Its weakness is structural, not moral. Nobody on the vendor side is paid to finish. If a firm proposes time and materials for a well-defined build, ask why the scope cannot be signed.

Fixed price. The firm commits to a deliverable, a schedule, and a number. It fits work that can be specified: an architecture document, a governance framework, a bounded modernization. The discipline that makes it work is change control. Scope moves through a written change order with its own number, not through drift. At i3solutions, fixed-scope engagements for architecture documentation, governance framework build, or bounded modernization typically run $85,000 to $245,000 against signed scope and signed delivery schedule.

Retainer or subscription. You buy standing access to senior capacity, or a standing outcome, on a recurring bill. It fits the operate phase: governance that must be maintained, an estate that keeps evolving, decisions that need a named senior architect on call. Governance subscription engagements at i3solutions typically start at $18,000 per month covering ongoing governance framework maintenance, compliance alignment monitoring, and named senior architect availability.

Larger programs stack these models in sequence, the same way platform-specific budgets such as Dynamics 365 implementation costs break into phases. A focused engagement pairing assessment with a reference architecture document and governance framework, at 8 to 12 weeks, typically scopes between $150,000 and $350,000 for mid-sized regulated enterprises. Full implementation of a target architecture, covering integration pattern deployment, testing, governance framework operationalization, and knowledge transfer, ranges from $250,000 to $800,000 or more depending on estate complexity. The assessment is fixed price. The implementation is fixed price against the design the assessment produced. Operations run on subscription. Each phase has an exit ramp.

Rate cards do not differentiate firms. These questions do.

Where does the risk sit when scope moves? On time and materials, with you. On fixed price, with the firm, if and only if the scope is signed. A fixed bid against a vague scope is time and materials with extra steps.

What triggers a change order, and who prices it? A firm with a real change-control discipline can answer in one sentence. A firm without one will talk about partnership.

Who owns the artifacts? Architecture documents, runbooks, and source belong to you. Any model that meters access to your own deliverables is a lock-in mechanism, not a billing structure.

What does the last invoice look like? Ask for the shape of a final month on a comparable engagement: what was delivered, what was handed over, and who on your side could run it afterward.

A Microsoft discovery assessment is a fixed-scope, fixed-fee engagement, typically $10K to $25K depending on scope, not an open-ended hourly meter, and the roadmap it produces is yours to execute with or without the firm that wrote it. i3Solutions runs its Risk and Roadmap Assessment as a one-week structured engagement that produces a business case anchored on your specific environment, your specific compliance frameworks, and your executive-cycle timing. Because the deliverable is a defensible plan rather than a dependency, you can hand it to your own team and run the build yourselves, bring i3Solutions back only for the workstreams you choose, or keep senior delivery through go-live. There is no lock-in clause and no requirement to buy the implementation to receive the assessment output. When you do want a senior engineer on the roadmap, i3Solutions routes a senior U.S.-based engineer to a client call usually within one to two weeks.

Two quotes arrive for one Power Apps request, priced differently. Price a Power Apps build fixed when the integration surface is enumerated, Dataverse and governance scope is settled and the requirement is written down; price it time and materials while any of the three is open; hold a retainer once the work is continuous change, not a build.

Fixed price. A fixed number is the right instrument when the boundary of the app is already drawn: the screens are specified, the data source is decided, the integrations are named one by one, and the acceptance test exists before the number is quoted. The part that resists bounding is the integration surface. A connector that turns out to need an on-premises gateway, a legacy system whose owner has not agreed to be read from, a Dataverse model that has to change because the source data does not normalize the way the workbook implied: each of those is a scope event, and under a fixed price the firm carries it and prices for carrying it. Ask the firm which integrations are inside the number, and what happens to the price when one of them needs a gateway or a premium connector.

Time and materials. An open meter is the honest instrument while the requirement is still being discovered, which on a Power Apps build often means the workbook or the paper process is the only specification anyone has, and the early weeks are as much analysis as construction. The scope risk sits with you. That is tolerable when the meter is short and the exit is defined, and expensive when it is neither. Ask the firm what deliverable ends the discovery phase, and what it needs from you to quote the build fixed once that deliverable exists.

Retainer. A retainer fits after go-live rather than before it. Once the app is in production the work becomes a stream of small changes, a new screen, a changed approval path, a field the compliance team now wants logged, and pricing each of those as its own fixed-scope engagement costs more in administration than in build. A retainer reserves capacity you direct, which is why it is the wrong shape for original construction: it prices availability, not a deliverable. Ask the firm what happens to unused capacity in a lighter month, and who decides whether a request sits inside the retainer or becomes a new build.

The models themselves, and where each one fits generally, are set out above in What Each Model Is, and Where It Fits, and the questions that expose which model a firm actually runs are in The Questions That Expose a Billing Model; both apply to a Power Apps build unchanged. A per-project band for Power Apps development work is published separately, on Can AI Build Me a Power App?. The licence price Microsoft charges for the app is a different line item from the build, and it is set out on Power Apps Premium vs Per App: What Actually Differs, and Where the Break-Even Sits.

i3solutions delivers Power Platform with senior US-based teams, available through its IT staff augmentation services, for exactly the regulated contexts where residency and clearance govern.

Fixed price is the wrong instrument even on a small app when the data it will run on has never been profiled, or when nobody has yet been given authority to decide which environment it lives in, because the number will be firm and the change orders will still arrive against an unknown that was never in scope. Time and materials is the wrong instrument even on a large one when the requirement is written, the acceptance test is signed and the integrations are enumerated, because at that point an open meter charges you for certainty the firm already holds.

Is a lower hourly rate cheaper overall?

Not by itself. A lower rate with a longer runway and no finish incentive costs more than a senior fixed-scope team on comparable work. Compare the cost of the outcome, not the cost of the hour.

What is the difference between a retainer and a subscription?

A retainer reserves capacity, and you direct it. A subscription commits to an outcome, such as a maintained governance framework with compliance monitoring, and the firm directs the work to keep that outcome true. Subscriptions transfer more responsibility to the vendor.

How do fixed-price engagements handle unknowns?

Through the scope document and change control. Unknowns discovered inside the signed scope belong to the firm. Unknowns outside it become priced change orders you approve before work continues. The signed scope is what makes the number real.

Which billing model fits a program rescue?

Assessment first, at fixed price, so you get an honest map before anyone bills toward a destination. The remediation that follows is fixed-scope against that map. Paying time and materials to diagnose and repair the same problem rewards the diagnosis for growing.

Can we run the roadmap ourselves after a discovery assessment?

Yes. A discovery assessment is fixed-scope and its deliverable is a plan you own. You can execute it with your internal team, engage i3Solutions only for selected workstreams, or retain senior delivery through go-live. The assessment does not obligate you to buy the implementation.

What are the pricing models for Power Apps development services from U.S.-based firms?

Three: fixed price, time and materials, and a retainer. Readiness chooses between them, not size. Price a build fixed once the integrations are enumerated, the Dataverse and governance scope is decided and the requirement is written. While any of the three is still open, time and materials is the honest instrument. A retainer fits continuous change after go-live.

If you are building the internal case for an engagement and need numbers your committee can compare, a 30-minute scoping call puts model, scope, and price band against your actual program before you commit. Schedule a 30-minute scoping call.