Method
Scope the problem before choosing the tool.
A business might ask for a website, app, automation, IT cleanup or security review. The first job is making sure that is actually the work that needs doing.
Working rules.
- Diagnosis first. The problem is named before the tool is chosen.
- Written boundaries. Scope, access, assumptions and exclusions are recorded before work starts.
- Evidence over opinion. Reports include findings, proof and recommended next action.
- Small releases. Work is delivered in usable stages where the job allows it.
- Handover included. You should know what was built, where it runs and what you own when the job ends.
Why the scope matters
Business systems rarely fail in one category.
A slow quote process might need a better form, a small internal app, a CRM handoff, cleaner email, or all of those in the right order. A security issue might be a permissions problem, a backup problem, a vendor problem, or a system that was never designed for how staff use it now.
I scope work across those boundaries so the quote matches the problem, not just the first service category that sounded close.