Step 02 of 04

Agree on priorities

We agree on the scope, costs and responsibilities before work begins.

A practical starting point, with priorities your team understands and a written scope you can decide on.

What this step is for

After the introductory conversation, we identify what needs attention first and what can wait. We explain the work, costs, dependencies and provider responsibilities so you can make an informed decision before implementation.

What we look at

What we review changes with the business, but these are the areas that shape the work.

Problems that cannot wait

Active outages, unreliable systems, sign-in problems, administrator accounts that are too exposed, and other issues stopping safe, productive work.

Problems that keep coming back

Patterns behind repeated support requests, unreliable computers, mismatched settings, and workarounds that have quietly become permanent.

One dependable standard

Keep work computers updated, protect them from harmful software, look after email and backups, and address unreliable office connections.

Clear ownership and help

Who handles each system, which vendor owns each problem, and how employees get help when something breaks.

How French Broad IT does it

Direct communication, practical priorities, and work that can be explained and maintained.

  1. 01

    Rank the priorities together

    We weigh immediate risks, recurring interruptions, and upcoming changes with your team to decide what needs attention first and what can wait.

  2. 02

    Put the scope and costs in writing

    We explain the proposed work, pricing, timing, and dependencies, including any decisions or access needed from your team and other providers.

  3. 03

    Agree on ownership before starting

    We confirm who approves the work, who handles each responsibility, and how your team will get help before you commit to the next step.

What it means for your business

  • Agreed priorities that reflect the needs of the business
  • A written scope and price to review before committing
  • Named owners and clear support arrangements
  • A practical starting point with timing and dependencies understood