Spec out your system

Four questions. As you answer, we work out what would need building, what it would connect to, and the first piece we’d build in a three-week sprint. Nothing is sent until you press send.

What does the business do?

Roughly. It sets the words we use for the work.

How big?

Approximate is fine. It tells us how many people the first piece has to work for.

What does it run on today?

Pick every one that applies. Each one is something we keep, connect to, or retire.

What hurts most today?

The job that takes the most time. This becomes the first piece we build.

What happens after you send it

  1. A thirty-minute call. We go through the spec you just built, correct our assumptions and agree the first piece.
  2. A written scope within two working days. The fixed price, the piece, what it connects to and what “done” means on day 15, on one page. Yours to keep whether or not you sign.
  3. Kickoff with your team. Sprints usually start within four weeks of signing. Day one is spent with the people who do the job today.

Common first pieces

The first sprint takes whichever job is slowest today. These are the ones that come up most.

Quotes from your own price book

Built from your price list and past jobs, sent from the phone. The accepted quote becomes the job.

The week on one board

Who is where, on what, with what kit. Changes reach the people affected without a phone call.

Job to invoice, typed once

The sheet filled on site lands in the accounts package as a draft invoice the same day.

Certificate and compliance register

Every expiry date in one place, flagged thirty days out, with the evidence attached.

Numbers from source data

The Monday report built from the system rather than assembled by hand, with every figure traceable.

Customer status page

Customers see where their order or job is and stop ringing to ask.

Get in touch

Book a thirty-minute call or email mal@asgharian.ie. We’ll say on the call whether a sprint makes sense.