Published by Linux Stewards · Last reviewed 23 August 2026

How We Scope a Small IT Job Before You Pay

1 min readPopular fixes

The idea is simple: we agree what the job is and what it costs before any work begins. This page explains the actual steps so you know what to expect.

The process

  1. 1You send the issue — a description, plus a screenshot, link, file or error message where you have one.
  2. 2We inspect the evidence — we look at what you sent rather than asking you to diagnose it.
  3. 3We identify the likely scope — the smallest useful solution, and whether it fits a fixed tier or needs a quote.
  4. 4We ask only necessary questions — to confirm scope, not to gather data for its own sake.
  5. 5We confirm the price — you agree the scope and price before work starts.
  6. 6We do the work and verify the result — including testing that it actually works.
  7. 7You approve or receive the result — and we explain anything you need to keep using it.

What this protects

  • No surprise costs after the work is done.
  • No turning a small job into a large project without asking.
  • A clear understanding of what “done” means before we begin.

No invented statistics

We describe the process as it is, without fabricated testimonials, customer numbers or success percentages. The evidence for whether we are a good fit is a correctly scoped, clearly priced first job.

What to send us

Send a sentence about the problem and anything that shows it. We will come back with a clear scope and price, or tell you honestly if it needs more investigation.

Need a hand with this?

Send the problem. We confirm the scope and price before work begins.

Request a Quick Check