Three steps, in the same order every time. The point is to propose the right size of engagement — which usually means a smaller one than you were braced for.
Discovery & Assessment
We get a real read on the environment and the actual goal before proposing anything — current configuration, where policy and system have drifted apart, and what the team has already tried. The output is a plain description of the problem you can recognize as yours.
A plan sized to the actual need
A plan tailored to what was found — not a bigger engagement than the problem calls for. If two weeks of focused configuration work resolves it, that's what we propose. If the real issue is governance rather than build, we say so.
Hands-on delivery, clean exit
Hands-on delivery, with your team left stronger and not dependent on Techworq to keep it running. Configuration decisions get documented in language your own administrators use, and the handoff is part of the engagement rather than an afterthought at the end of it.
Engagements are senior-consultant-led — not a rotating bench of juniors learning your configuration on your time. Milestones are transparent, and you communicate directly with the person doing the work rather than through an account manager relaying status.
There's no minimum-engagement-size overhead to clear. A small, specific need is welcome here — it's most of what we do.
Engagement terms and pricing are discussed directly, once we understand the work.