Software for engineering and trades

The quote is on a laptop, the job is on a van, and the paperwork is in a folder.

Engineering

What usually goes wrong

If two or three of these sound like your week, the rest of this page is about fixing them.

  • Quotes are built in a spreadsheet that only one estimator fully understands.
  • Nobody can say what stage a job is at without ringing the site.
  • Site reports come back as photos in a message thread.
  • Timesheets arrive on paper at the end of the week, if at all.
  • Invoicing waits on paperwork that is sitting in a van.

The work

What we build here

Most projects are two or three of these rather than all of them. Each one links through to how that kind of work runs.

  • Quoting that reuses what you already priced

    A rate library, standard assemblies and past jobs, so a quote takes an hour instead of a day and comes out consistent whoever builds it.

    Custom Software
  • Job tracking from enquiry to invoice

    One record per job carrying the quote, the schedule, the site reports, the variations and the final invoice. Anyone in the office can answer "where is it up to".

    Custom Software
  • Site reports from a phone, offline

    Photos, readings, sign-off and hours captured on site with no signal, syncing when the van gets back to a connection.

    Mobile Apps
  • Paperwork read automatically

    Supplier invoices, delivery notes and purchase orders read and matched to the job, with a person approving anything that does not match.

    AI Agents & Automation
  • Accounts package connected properly

    Invoices, purchases and payments flowing between the job system and the accounts package instead of being keyed in twice.

    Integrations & Migrations

Fits around you

Works with what you already run

We build around the systems you already pay for and your team already knows, rather than asking you to replace them. Where a connection is not possible, we say so before you commit.

  • Accounting packages
  • CAD and drawing stores
  • Supplier and merchant portals
  • Payroll systems
  • Fleet and GPS tracking
  • Document management systems

Questions we get asked about engineering

Our engineers work where there is no signal. Does that break it?

It is designed around it. The app works fully offline, keeps what was entered, and syncs when a connection comes back. Anything that needs a live connection to record a job is unusable in a plant room.

Will the team on site actually use it?

Only if it is faster than what they do now. A site report should be a few taps and a photo, not a form. We build it with the engineers, and if they will not use it, it does not work.

Can it handle our pricing, which is complicated?

Usually. Complicated pricing is normally a set of consistent rules living in one person's head and a spreadsheet. Writing those rules down is most of the job.

We already have a job management product and it is not great. Rebuild or fix?

Depends on where it hurts. Often the answer is to keep it and fix the two things that cost you time, which is far cheaper than a rebuild. We will tell you honestly which it is.

The same problems turn up in the other trades we build for, usually wearing different words. See who else we build for.

Next step

Tell us what is not working.

Describe the problem in your own words. We reply with an honest read on whether it is worth building, roughly what it takes, and what we would do first.