How quickly can we get started?
It's the question we get most, so here's the full answer: every stage, how long it takes, who owns it, and what has to be true before the next one starts.
30min
Discovery call, Day 0.
3days
Written scope, in business days.
21days
First call to steady state, fast track.
Engagement timeline
Fast track: 21 calendar days from first call to full support. When there's no deadline, we typically allow one to two months for a thorough onboarding. See below.
Discovery call
30 min
Day 0
Shared
Scope & written proposal
2–3 days
Day 1
GREYDATA
Review & signing
48 hrs
Day 3
Client
Access & provisioning
3 days
Day 5
Shared
Environment assessment
10 days
Day 6
GREYDATA
Cutover to GREYDATA support
1 week
Day 12
Shared
Prioritized roadmap delivered
5 days
Day 16
GREYDATA
Steady state & QBR cadence
Ongoing
Day 21
GREYDATA
Day 21: steady-state support with a documented environment, a named team, and a roadmap on a review cadence.
Let’s talk
Tell us your date and priorities. We'll say straight whether we can meet it.
Stage by stage
Goal, duration, and who's responsible for each stage, plus what has to be true before the next one starts.
Stage 01–02
SharedA 30-minute call, no deck and no pressure. We ask what's breaking, what you're planning, and what you've already tried. Within three business days you get a written scope: what we'd do, in what order, for how much.
Exit criteria
Written scope and price in your hands.
Stage 03
ClientYou take the scope away. Bring in your accountant, your board, or your internal IT lead. We'd rather you did. Questions get answered in writing. Contract and paperwork are handled digitally; nothing needs a wet signature or a courier.
Exit criteria
Countersigned agreement.
Stage 04–05
GREYDATAWe collect credentials, map assets, review backups, and check what's actually exposed. This is the stage most providers rush, and it's why environments get misdiagnosed for months afterwards. We don't start ticket work until we understand what we're looking at.
Exit criteria
State-of-environment document with an inventory and risk register.
Stage 06–07
SharedTicketing moves to our service desk with the AI first-response layer live from day one of cutover. We run in parallel wherever the risk justifies it. The roadmap lands at the end: ranked by business impact, not by whichever tool shouted loudest.
Exit criteria
Support live, roadmap delivered, first QBR scheduled.
How fast do you need to move?
A thorough onboarding typically takes one to two months.
If you have a date to hit, such as a contract ending, a cutover, or an acquisition, we can go from first call to fully supported in 21 days. We're experienced in quick onboardings that feel seamless. Tell us your date and we'll say straight whether we can meet it.