Engagement stages
How a WebRidge consulting engagement moves from first call to handover — without becoming a permanent shadow team.
Scoping call
Forty-five minutes with a WebRidge advisor. We learn the journey or domain under pressure, who owns decisions, and whether refactoring, tuning, or a written review is the honest first move.
Access and artefacts
You grant read-only access to diagrams, metrics, and the repositories that matter. We list what we will not touch. No production write access is ever required for advisory work.
Discovery
We rebuild the real service and data map, not the aspirational one. Discrepancies become agenda items for workshops or the review document.
Working sessions
Boundary workshops, latency deep-dives, or stakeholder interviews — depending on the consultation type. Sessions are scheduled around your release calendar, not against it.
Plan and readout
You receive a written plan or review, then a readout with the people who will execute. Recommendations name owners and sequencing; they do not invent a second roadmap.
Optional follow-up
A short check-in two to four weeks after handover is available if you want a second set of eyes on early implementation choices. It is never automatic billing.
Who should be in the room
Bring the people who can change service ownership and release policy — usually a principal engineer, the domain product lead, and someone from operations who lives with on-call. Sponsors who only attend kickoffs slow every later decision.
Where we work
Discovery and tuning often run remote across Australia. Boundary workshops benefit from a Brisbane or client-site room when more than four people need whiteboards at once. Travel outside Southeast Queensland is quoted separately.