Skip to main content

Custom software for Calgary businesses

On site, a client's representative wants one clear field ticket to sign before the crew leaves. We build the tool a small Calgary field-service firm uses to hand it over and invoice from it.

Software for the crews that work Alberta's fields

A small Calgary field-service firm with good crews can be asked to go further: northern Alberta, Saskatchewan, north-east British Columbia, and across the border, where operators look for contractors who are easy to deal with on paper. What has kept such a firm close to home is the paper. The further the job, the later the ticket gets back, and the invoice waits for it. None of that calls for a move. The firm stays at its Calgary address with the office staff it already has. What travels to the job is the ticket, filled in and signed where the work was done.

Every job these crews do, testing, hauling, welding, maintenance or cleanup, ends with a field ticket listing hours, equipment and materials, signed on site by the client's representative. On paper, that ticket rides in a truck for days. Some arrive illegible and some never arrive. Back in Calgary someone types it up, looks up the rates agreed with that client, adds the client's coding, and finds out later whether the invoice was rejected.

We would put that ticket on the crew lead's phone or tablet, working with or without a signal. Hours, units and materials are priced from the agreed rates as they are entered, and the client's representative signs on the screen. When the phone next finds a signal the office has the ticket, and the invoice is raised from it with the client's coding carried through. Crews, equipment and invoices are all read from the same tickets, so a question about any job can be answered from the office. The owner sets the rates. A ticket that does not match them, or that is missing a code, is held for a person in the office to settle before any invoice goes out. If the firm already pays for a field-ticket product, we start from that and build only what it lacks. A trade contractor in the city, with work orders and sign-off on site, would start from the same place. Scope and price are fixed in a brief before building starts.

What you receive

  • Internal tools that replace spreadsheets and manual steps.
  • Customer portals where your clients see their own information and act on it.
  • Connections between systems that do not talk to each other.
  • A first product, from an idea to a release real users can try.

How it runs

  • We map the work: who uses it, what they need to get done, the records and rules involved.
  • We define the smallest useful release and check whether an existing product can do part of the job.
  • We build in pieces you can review, testing real tasks, permissions and what happens when something fails.
  • We release and hand over, with operating notes and a plan for what comes next.
Everything that is included

Scope and investment

Start with the brief: C$3,500. We write down what the software has to do, list the screens and give you a fixed price and a timeline. The C$3,500 is credited in full when you complete the build with us.

Work you can inspect

The Tucker CPA website home page, built by Butler Agency

Tucker CPA

We built the brand, the website and a national content system for a new CPA firm, and we handle its SEO.

Read the case study
The Beyond the Bedside Foundation website home page, built by Butler Agency

Beyond the Bedside Foundation

A website for a new children’s foundation, built for families, student volunteers and supporters.

Read the case study

Questions before we start

Our crews work on lease roads with no signal. Does the ticket still work?

Yes. It is filled in and signed offline and sent when the phone next finds a signal. A half-finished ticket is saved as it goes, so a dead battery does not lose it.

Each operator wants its own codes on the invoice. Can it handle that?

Yes. Each client's codes and approval steps are set up once, and every ticket for that client follows them.

We already pay for a field-ticket product. Would you replace it?

Only if it is the problem. We look at what it does first. If the tickets are fine and the retyping happens between the ticket and the invoice, we would build that link and leave the rest alone.

What would you like your business to do next?

Tell us where the work gets stuck or where you want to grow. We will help you choose a practical first step.

Discuss your project