IT Project Cost Estimation for a Half-Finished Setup

Ask What Is Working Before Asking Who Caused It

Open with a practical question: 'What can your team still do, what has stopped, and what changed before that happened?' Record the answer as the client's account. Have the engineer distinguish what has been verified from what still needs investigation.

Ask who is currently changing the environment and who can authorize your involvement. A half-finished setup needs a clear handoff, including the work already attempted. Don't let your assessment run alongside an uncoordinated change by another party.

Use this proposed wording: 'Before we start, we'll agree who controls changes and how we receive the existing records. If someone else is still working on the system, we need that in the plan.' You don't need to blame the previous person to establish the state your team is taking over.

Justin Esgar sees rescuing a failed migration as a possible way to build a client relationship. Ryan Grimes accepts that possibility but says his firm prefers not to displace planned work for a stressful rescue start. Those are their different intake preferences; neither makes a rescue an automatic good fit for your MSP.

Separate Assessment From Emergency Work

If the client needs immediate recovery, establish whether you have the people and capability to offer that work. Give the authorized client a defined decision about scope and charges. Don't describe urgent implementation as assessment and then let the commercial boundary emerge from the invoice.

I'd explain it this way: 'The assessment produces a verified state record and recommended next steps. If you need us to make an immediate change, we'll explain that action and agree its approval separately.' Keep the engineer's assigned task consistent with the offer.

Confirm what access the assessment requires and how it will be provided through your approved process. Keep credentials out of the proposal itself. Where the engineer identifies an incident or a specialist problem outside your capability, route the decision to the appropriate response rather than continuing a routine cleanup sale.

Sell a Deliverable the Client Can Use

An assessment needs an output even if the client doesn't buy the cleanup. Give them a record that supports the next decision. I'd put these deliverables in the assessment offer:

• Describe the current state your engineer verified, separating it from the client account and untested assumptions.
• Identify the remaining work required for the agreed outcome, with dependencies and unresolved questions.
• Explain the proposed sequence and the checks that would establish completion.
• Provide the basis for a remediation estimate, with any work that requires further investigation kept visible.
• Record what remains outside your responsibility and what the client must decide next.

Keep the assessment's completion test about those outputs. Don't imply that documenting a problem means it has been corrected. The client should be able to see which proposal covers the investigation and which covers changes to the live environment.

What do you say when the client asks for a price before the assessment? Say: 'I can price the investigation now because we can define that work. I can price the remaining implementation once we've checked what is there and what needs to change.' Then show the assessment scope rather than defending an unexplained fee.

Build the Remediation Quote From Verified Tasks

Have the engineer turn the findings into tasks before sales commits to the price. Include the work needed to verify completion and hand the result over. Put an unverified dependency beside the task it affects so the client can see what still prevents a firm commitment.

The model uses a blended project rate of $185 an hour. For a labor-only illustration, calculate the direct-labor allowance per priced hour as $185 multiplied by one minus the 50% project gross-margin target. Use the hours your engineer estimates for this environment, then check actual delivery cost and any other direct costs before approving the quote.

Don't borrow the duration of a different rescue or invent a percentage contingency. Where the uncertainty still matters, investigate it or quote a clearly bounded stage with an approval point before the next commitment. Explain what new information would change the estimate.

Use this talk track: 'This price covers the work we've listed against the state we verified. These unresolved items need a decision before we can include them. If the scope changes, we'll show you the effect before agreeing the additional work.' Keep that wording consistent with the actual proposal and approval process.

Answer the Request for a Cheap Fix

Say the prospect proposes fixing only the visible symptom. Ask the engineer whether that narrower outcome is technically supportable and what would remain unresolved. Sales should not turn an unexamined limitation into a promise that the environment is ready for ongoing service.

You can say: 'We can quote that narrower result if the engineer can define and verify it. We'll also state what it leaves untouched, so you can decide whether that outcome meets your need.' If it doesn't, explain the required work or decline the promise.

I don't buy generic advice to give away the fix so you can win the subscription. In an MSP, that can commit engineering work before the environment and the future service cost have been checked. Make the initial offer useful and bounded instead of promising unspecified labor as a closing technique.

Decide Separately Whether to Take the Ongoing Service

Completing a rescue doesn't automatically put the environment in your managed plan. Review the resulting setup against your standard service requirements and the actual work still needed. Agree the monthly scope and fee separately if both sides want that relationship.

The model treats onboarding as a quoted concession waived for a signed agreement. Keep that future onboarding decision separate from the assessment and remediation work you are selling now. Don't rename an already promised free onboarding task as paid assessment merely to recover its cost.

Send the prospect the assessment scope with a clear approval route. Put the authorized investigation on the board, and have the engineer return the state record before you promise the cleanup. That gives your next sales conversation something concrete to price.