Skip to content
Case study · IT and security

A growing firm’s IT, run end to end: a faster network, work from anywhere, every shared drive copied every night, and an alarm if the copy goes quiet.

An established, growing architecture practice in Austin, Texas, with eight to ten people, a client since September 2026. This is what we run for it, why we set it up that way, and what the record shows as at 29 October 2026. If you are a small firm with no IT person, it is the same service we would set up for you.

The bottom line

Eight to ten people got one place to send every request, a faster and filtered network, work from anywhere, and every shared drive copied each night to a disk the firm owns, with an alarm that rings when the copy goes quiet. The part worth copying is not the equipment. It is four decisions about the backup, and the habit of asking who would know if it stopped.

Facts as at 29 October 2026. Document reissued 31 October 2026 with the questions below and three figures; the facts did not change.

As at 29 October 2026, read from our CRM, help desk and backup monitor. The firm is not named, at its request.

The situation

A practice of eight to ten people that runs on design software and shared files. Its network came from the internet provider, its files lived in one cloud service, and IT was something members of the firm handled alongside their own work. The firm wanted two things: one place to send the team first for everything day to day, and a way to know if its nightly backup ever stopped working.

What we delivered

Two pieces of work, one for the people at their desks and one for the people who are not.

What we run for it

Four jobs, in the order a firm meets them.

  1. 1 · Ask

    One place to ask. A request raised in the portal gets a ticket number, and every reply carries it with a link back.

  2. 2 · Run

    Laptops installed and set up, Google Workspace accounts and settings administered, Wi-Fi and the network looked after.

  3. 3 · Copy

    Every shared drive and every person's own drive copied each night to a disk the firm owns, on its own network.

  4. 4 · Watch

    Each run reports in. If a night goes quiet for 26 hours, a ticket opens by itself.

What the team has asked us for

  • Laptop setup3
  • Wi-Fi and network2
  • Google account1
  • Software1
  • Question1
  • Not yet sorted2
10 requests raised through the help desk since 17 September, counted by kind. Counts only.

What the copy covers

  • 10 shared drives and 9 personal drives, 19 jobs in all.
  • Kept for 30 days, so a file deleted by mistake can still be found.
  • Browsed by staff read-only, from the firm’s own network.
  • Reported to a dashboard we watch after every run.

Four decisions, and why

The backup is where the choices mattered most, because it is the part nobody sees until the day it is needed.

The record

The first full copy ran over a weekend, from the evening of 23 October. Since then, the four nights on record have each taken under twenty minutes.

  • 16.5 min26 Oct19/19 jobs · 0.7 GiB new
  • 18.5 min27 Oct19/19 jobs · 8.2 GiB new
  • 16.8 min28 Oct19/19 jobs · 2.4 GiB new
  • 16.9 min29 Oct19/19 jobs · 2.9 GiB new
The four nightly runs on record, read from the backup monitor on 29 October 2026. A run copies only what changed since the night before, which is why the second night wrote more than the others. These are completion figures: they show the copies run and report, not that a file has been restored from them.
  1. 5 Sep
    The firm's first message reaches us, on a referral.
  2. 12 Sep
    We open the written quotation.
  3. 17 Sep
    The firm accepts it. Its first help-desk request, a laptop setup, arrives the same day.
  4. 18 Sep
    Two service policies are set up in the help desk: one for laptop installs, one for everyday IT.
  5. 21 Sep
    The new network goes live.
  6. 23 Oct
    The backup appliance is installed on the firm's network and the first full copy starts that evening.
  7. 26 to 29 Oct
    Four nightly runs are on record, and each reports all 19 jobs complete, in about 17 minutes.

What to take from this case

Five decisions you can copy, whoever looks after your IT. Each is something the record supports; none is the engineer’s own figure.

  1. 1

    One place to ask, with a number on every reply

    Everything day to day goes to one portal. Each request gets a ticket number and every reply carries it with a link back, so nothing lives in a personal inbox.

  2. 2

    A second copy on a disk the firm owns

    Then its files depend neither on one cloud provider nor on the firm that looks after its IT.

  3. 3

    Staff can read the copy and cannot change it

    A copy that anyone can edit is a second place to lose work.

  4. 4

    Silence is the alarm

    Each run reports success, and a night that goes quiet for 26 hours opens a ticket without anyone remembering to look.

  5. 5

    One ticket per outage

    An alert that repeats every hour gets filtered, and then it is not an alert.

What this is not

Six questions to put to your own provider

Write down what they say. A good answer is specific and can be shown. If any answer is “I would have to check”, that is where a review starts. The guide Setting Up IT for a Small Firm has the restore test, an inventory sheet and the rest of the questions.

  1. 1

    Where is the second copy of our shared files, and who owns the disk it is on?

    A good answer sounds like
    A named place and a named owner, and it is not the same cloud account as the originals.
    A warning sign sounds like
    I would have to check.
  2. 2

    Who can change or delete the copy?

    A good answer sounds like
    Staff can read it, named administrators can change it, and a deleted file stays for a stated number of days.
    A warning sign sounds like
    Anyone with the login.
  3. 3

    Who would know within a day if it stopped, and how?

    A good answer sounds like
    Each run reports in, and a missing report opens a ticket by itself.
    A warning sign sounds like
    We would get an email if it failed.
  4. 4

    How many alerts does one outage make?

    A good answer sounds like
    One ticket, until it is resolved and a good run arrives.
    A warning sign sounds like
    One an hour, so we filter them.
  5. 5

    If I need help this afternoon, where does the team send the request?

    A good answer sounds like
    One place, and every reply carries a ticket number and a link back.
    A warning sign sounds like
    Call whoever you know.
  6. 6

    When did you last restore a file in front of us?

    A good answer sounds like
    A date, a file and the time it took.
    A warning sign sounds like
    The backups ran last night.

A look inside the report

Three pages as they are. Press a page to open it full size.

Is this your firm?

If you have between five and fifty people, no one whose job is IT, and shared files you could not afford to lose, the starting point is a review of what you run today. It is the same first step we took here.

Start with a review of your IT.

Give us one piece of work and read access to one system. We map it and come back with what we found, what we would build and what it would take — before any commitment. You decide using our output, not our pitch.

Talk to us