Step 01 of 04

Understand the business

We learn how your business works before recommending what should change.

A clear picture of what you have, what is getting in the way, and what deserves attention first.

What this step is for

Technology problems rarely live in isolation. A recurring login issue may mean nobody is sure who owns an account. A slow application may be caused by the office network, an outside vendor, or an aging computer. We start by understanding the work around the technology so the plan reflects the business—not a generic checklist.

What we look at

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

People and daily work

Who uses each system, where work slows down, how support happens now, and which interruptions cost the team the most time.

Who can access what

Work email, shared files, who can change important settings, and what happens when employees join or leave.

The tools and providers you depend on

Computers, office networks, essential business software, service providers, renewals, and the connections your operation depends on.

Risks and repeat frustrations

Known security gaps, fragile workarounds, repeat support issues, and systems, vendors, or people the business cannot operate without.

How French Broad IT does it

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

  1. 01

    Start with a working conversation

    We speak with the people responsible for the business and, when useful, the employees closest to recurring problems.

  2. 02

    Create one useful record

    We organize systems, account access, vendors, owners, and open questions into a record that can guide real decisions.

  3. 03

    Prioritize by impact

    Findings are separated into urgent risks, day-to-day problems, and longer-term improvements so the next step stays proportionate.

What it means for your business

  • A shared understanding of the current technology setup
  • Clear ownership and fewer hidden surprises
  • A prioritized plan instead of an oversized package
  • A sensible starting point for dependable systems, better security, or ongoing support