Scope
Name the outcome
Start from the trigger - a lease date, a growth milestone, a platform end-of-life - and the specific outcome that has to be true when the project ends.
IT projects
A project needs a start and an end - and a plan for what happens after.
An office move or a platform migration is real work that doesn't fit a flat monthly rate. Here is how a project actually gets scoped, priced, delivered, and folded back into ongoing service.
How a project moves
Five stages, one visible owner from start to handback.
Price
Plan and price it separately
A project gets its own price, timeline, and acceptance criteria instead of being absorbed into the monthly rate or quietly deprioritized behind ticket work.
Coordinate
Sequence every dependency
Network cabling, ISP circuit timing, device relocation, and vendor scheduling are sequenced against the same date, not handled as separate surprises.
Test
Prove it before cutover
Connectivity, access, and the applications that matter are checked at the new location or on the new platform before the old one is decommissioned.
Hand back
Return it to recurring service
Once stable, the new environment folds back into the same managed maintenance, support, and vendor coordination as everything else - not left as a one-time favor nobody owns afterward.
A necessary boundary
Recurring service and project work are different commitments.
Recurring service
Day-to-day support, existing device and account maintenance, and vendor coordination for problems inside the current environment.
Project work
Office moves, network builds at a new location, platform or server migrations, and major deployments - each with its own scope, price, and timeline agreed before work starts.
Honest limit: this page does not publish a fixed project price or timeline. Office moves and migrations vary too much by square footage, carrier lead times, and application count to quote sight unseen.
Before the move starts
Questions worth answering before a date gets set.
- What is the hard date, and what has to be true by then?
- Who is the single point of contact across the ISP, landlord or building management, and any specialty vendors?
- Is there a tested fallback if the new circuit or platform isn't ready on time?
- What does "done" actually look like, and who signs off that it's been reached?
Connect the work
See what standard the new location or platform should meet.
Reach the team
Tell us what needs an owner
Share your team size, current support setup, and the responsibilities you want clarified. We will use that to figure out whether an MSP introduction makes sense.
Online requests are not available right now. No message is sent from this page.