How projects work

Engagement process

Every engagement has a clear starting point, written scope, agreed price, regular communication, and a tested result.

Flexible starting points

Start with troubleshooting, an assessment, a roadmap, implementation, or ongoing advisory support. If discovery is needed, we define it as a useful first phase with its own deliverables.

The project path

Project stages

If the problem is not yet clear, we can begin with a focused assessment. You receive the findings, priorities, and a practical recommendation for what to do next.

01

Initial brief

Tell us what is happening, who is affected, what the business needs, what has already been tried, and any timing or access constraints. We capture the facts and identify the best starting point.

02

Scope and price

We agree deliverables, systems, data, responsibilities, exclusions, timing, price, acceptance criteria, and change handling. Security testing also requires signed authorization and rules of engagement covering IP addresses and domains, allowed methods, test windows, emergency contacts, and stop conditions.

03

Work and communication

We complete the agreed work, coordinate dependencies, and maintain a decision record. Anything that changes cost, timing, risk, or scope is raised before the related action is taken.

04

Validation

We test the result against the acceptance criteria. For security work, the record separates supported findings, limitations, completed remediation, and agreed retest results. Other work may require configuration review, mail-flow testing, restore verification, or a guided walkthrough.

05

Handoff and continuity

Your handoff includes the agreed files, configuration notes, diagrams, ownership details, operating steps, and recovery information. We can close the project cleanly, support the next phase, or continue in an ongoing advisory role.

Before work starts

Scope and authorization

  • What business result must the work produce?
  • Which systems, accounts, providers, and data are included?
  • What assumptions, dependencies, and responsibilities affect delivery?
  • What access and decisions are required, and from whom?
  • What are the milestones, timing, price, and payment schedule?
  • How will the result be tested and accepted?
  • How will changes be evaluated and approved?
  • What documentation, ownership information, and support are included at handoff?

Secure access: Access is arranged after the scope and authorized contact are confirmed. Do not send passwords, recovery codes, private keys, or credentials through the inquiry form.

Request a scope

We will help define the right engagement and show what information is needed to scope it.

Describe what you need