HEYGUS · Software built around how your business actually works

The shape of the problem

The shape of the problem, not the list of problems.

What our clients have in common is not what they sell, and not what they needed built. It is the shape of it.

Work done by hand

The same thing typed into three systemsEntered once, then again, then again. Nobody decided it should work this way.
Priced off a spreadsheet one person maintainsWhen they are away, quoting slows down or goes out wrong.
Paperwork that comes back on paperJob sheets, signatures and photographs, retyped by somebody in the office.
Documents read one at a timeInvoices, delivery notes, certificates. Opened, read and typed out by eye.
The list somebody builds before anyone can startThe first hour of the day goes on a list that could build itself.

Money that leaks quietly

Quotes nobody chasedSent, then silence. It was nobody's job to follow them up.
Work done and never invoicedThe extra half day, the parts off the van, the callback nobody logged.
The enquiry that came in after hoursNobody answered. They rang somebody else.
Repeat work nobody was reminded to bookServices, renewals and inspections that only happen if a person remembers.

People waiting

Customers ringing to ask what you already knowWhere is it, when is it coming, has it been booked in. The answer is in a system.
Staff waiting on somebody else's fileWork stops because the person who owns the spreadsheet has not updated it.
A simple question, a two day answerNobody can say how last month went until somebody builds a report.

The difference

Most automation is a catalogue. Your problems are not on it.

Two ways of buying software. Only one of them starts with your business.

Buying from a catalogue

Building around the business

CatalogueYou pick from a fixed list of features.

HEYGUSWe start from how the work already happens.

CatalogueIf your problem is not on the list, you change how you work.

HEYGUSIf it is not on anybody's list, that is usually why you rang.

CatalogueYou pay every month for the features you never use.

HEYGUSYou pay once for the thing you asked for.

CatalogueThe roadmap belongs to somebody else.

HEYGUSYou keep the code and the documentation.

CatalogueYou are one account among thousands.

HEYGUSWe learn how your business runs before anything gets written.

What we build

No two of these are the same job.

There is no product here. There is whatever the business turned out to need. This is the range of the work, not a list to choose from.

A quote that prices itself from live costs, and books the work the moment it is accepted.
A place customers can look for themselves, instead of ringing to ask.
Something for staff on site that works with no signal and syncs when it finds one.
Stock that counts itself, so nobody arrives at a job without the part.
Certificates and records that file themselves and chase their own renewals.
Hours that come off the job rather than off somebody's memory on a Friday.
Supplier invoices matched to orders without anybody opening a PDF.
Repeat work that books itself a year ahead and reminds the customer it is coming.
A number you can trust on a Monday morning, without waiting for a report.

Most of what we build is not on this page. It is whatever the business actually needed.

How it works

Four steps, and you can stop after the second.

There is no discovery phase you pay for before you know what you are getting.

A call

Half an hour. You describe the part of the week that should not still be manual. We tell you honestly whether it is worth building, including when it is not.

A written scope

What gets built, what it costs, how long it takes, and what is deliberately not included. You read it before anything is agreed, and you owe nothing if you walk away.

The build

Small releases you can actually use, not one delivery at the end. You see it working early enough to change your mind while changing it is still cheap.

It is yours

The code, the documentation and the accounts are in your name. Support afterwards if you want it, and nothing stops working if you do not.

Before you ask

The questions everybody asks on the call.

What kinds of business do you work with?

We are not defined by an industry. The businesses we work with run on jobs, vans, engineers and paperwork: trades, field service, installation, maintenance, logistics, hire, and plenty that do not fit any of those words. What they have in common is the shape of the problem, not what they sell.

What does it cost?

A fixed price, quoted after a written scope. We do not give a number before we understand the systems involved, because any number given at that stage is a guess, and guesses get corrected upwards later. The scope and the price come before you commit to anything.

How long does it take?

The scope says so before you agree to it. Work goes out in small releases rather than one delivery at the end, so you see something working early and can change direction while it is still cheap to do.

Do I own what you build?

Yes. The code, the documentation and the accounts are yours. There is no licence to keep paying and nothing that stops working if you stop working with us.

Do you replace the systems we already have?

Usually not. Most of the work is making what you already own talk to itself. Replacing a working system is expensive, disruptive, and rarely the actual problem.

What if the honest answer is that we should not build anything?

Then that is what you will be told on the call. Some problems are a process problem, or a training problem, or a setting that nobody ever switched on. Selling you a build in those cases would be easy and wrong.

Your business runs on half a dozen systems and people filling the gaps.