Decide with evidence, not frustration. First work out why the project is late: scope creep, a capability gap or thin resourcing. Then have someone independent measure what is actually built against what was promised. If the estimate to finish is credible and the team can show working software, push through with tighter controls. If not, move on, as long as you own the code and can hand it over cleanly.
Sunk cost should not drive the call. What matters is the time and cost to finish with this team compared with finishing with another. A one-week technical audit gives you that comparison. If you are also weighing who to bring in, read who to hire for a Shopify Plus build.
Find the cause first
Late projects usually fall into one of four patterns, and each one points to a different fix.
| What you see | Likely cause | What to do |
| Change orders arrive after new requests from your side | Scope creep, partly shared | Freeze scope, log new asks for a later phase and reprice the remaining work. |
| The same defects return and estimates keep missing | Capability gap | Audit the code and test the team on a hard feature. |
| Work stalls, people rotate and questions go unanswered | Resourcing | Ask for named staffing and a capacity plan. |
| Change orders cover items in the original SOW | Weak scoping or padding | Compare every order to the signed SOW line by line. |
Check what is really built, not what is claimed
Progress reports describe effort. The checks below show output.
Do: list every feature and mark it built, partly built or missing.
Do: click through real flows: checkout, B2B, search, integrations and mobile.
Do: review commit history, theme structure, custom apps and how Functions and integrations are written.
Do: check burn-down, open defects and how many fixes were reopened.
The one-week audit that answers it
A short, independent audit turns opinions into numbers.
- Day one: secure repository, staging and admin access.
- Days two and three: review theme, apps, custom code, integrations and performance.
- Day four: test core flows and log defects by severity.
- Day five: deliver percent complete by feature, a defect list, an estimate to finish and a risk register.
Cost of switching versus finishing
Compare the paths on the same three measures.
| Path | Cost | Time | Main risk |
| Push through | Remaining SOW work plus controlled change orders | Shortest, if the audit estimate is credible | Repeats if the cause was capability |
| Switch partner | Audit, onboarding and some rework of weak code | Ramp-up plus finish | Handover quality and code ownership |
| Rebuild weak modules only | Rewrite the weakest parts | In between | Needs clean module boundaries |
If the audit’s estimate to finish with the current team is credible and below the cost of replacing the weak parts, finish. If not, switch.
Your contractual position
Read these clauses before any difficult conversation.
- Code and IP ownership for work completed so far.
- Admin and repository access for your team now.
- Milestone payments tied to accepted deliverables.
- Written estimates and approval before any change order starts.
- Notice periods and handover duties on termination.
What the audit hands back
A good report gives you a decision, not a debate.
Shows: what is done, partly done and missing, mapped to the original scope.
Shows: what blocks launch and what can wait for a later release.
Shows: the time and cost to launch, plus the risks that could move them.
Share your SOW, current staging link and the latest change orders, and our Shopify Plus development agency team will run an independent audit and tell you whether to push through or switch.
Frequently Asked Questions
Match each change order to the signed SOW line by line. Items already in scope should be fixed at no charge, and genuinely new work needs a written estimate before it starts.
Check your contract first. Payments tied to accepted milestones give you a stronger position, but withholding money without a clear breach can escalate the dispute. Take legal advice before you do.
An independent Shopify Plus developer or agency with no stake in the outcome, given repository, staging and admin access. Our Shopify Plus development agency team can run one.
Yes, if the code is clean enough to extend. The audit shows which parts to keep and which to rewrite. For timing benchmarks, see how long a Shopify Plus build takes.
Raise it immediately. Check the contract for IP clauses and ask for repository access. Without code access, switching partners becomes much harder.
