Six tools, one business, and a person in the middle moving data between them.

Who this is for

Growing service companies with real operational complexity and a stack that accumulated rather than was chosen. Trades and contracting, cleaning and facilities, landscaping, events, logistics, agencies, maintenance, and anything where a job moves through quote, schedule, deliver and invoice.

The size that matters is not headcount but coordination. Small enough that the owner still holds the whole operation in their head and software is usually premature. Large enough to employ someone whose job is systems, and you have in house capacity to direct that we are not assuming here.

How to tell you have outgrown the patchwork

A short diagnostic, because this is the category where people most often cannot tell whether the problem is big enough yet:

• Someone’s main job is moving information between systems
• You have been told “that’s in the other system” this week
• A customer has been asked for information you already had
• Month end requires assembling data from more than two places
• A new hire needs to learn tools rather than a process
• You have stopped trusting a report enough to act on it without checking

Three or more and the coordination cost is probably larger than a focused build. Fewer than three and it is probably not, and we would rather you spent the money elsewhere.

What usually goes wrong

The tools are individually fine. The failure is at the joins: each product owns part of the truth and none owns the job. So the job exists as a row in four places, and reconciling them is somebody’s week.

The second failure is visibility. When no system owns the job, nobody can ask a simple question without asking a person, and the business runs on interruption.

What Goldstone may build

• One job record from enquiry to invoice, with everything hanging off it
• Lead intake from phone, web and email into that record
• Quoting with versions, approval and a status that is actually tracked
• Scheduling and dispatch tied to the job rather than kept beside it
• Job status that customers and staff can see without ringing anyone
• A billing handoff carrying complete information into the accounting package
• Reporting that answers the weekly questions without assembly

Usually keeping the accounting package, the calendar and the payment processor. The build is the connective layer that owns the job.

Integrations and data sources

Accounting, almost always kept. Calendars. Payments. Email and SMS. Sometimes a specialist tool for a trade that genuinely does its job well and should stay.

AI opportunities

Reading inbound enquiries and turning them into structured jobs. Extracting data from supplier documents. Drafting routine customer communication for review. Narrow, at the edges, with rules doing the workflow.

Where ordinary automation is better

Almost all of the workflow. Status transitions, scheduling constraints, reminders, overdue chasing, escalation, recurring reports. If the rule can be written in a sentence, it should be code and not a model.

When custom software makes sense

When the way you quote, schedule or deliver is genuinely yours and the products force you to work around them. When the integration tax, annualised, is approaching the build price.

When it does not: if a vertical product exists for your trade and fits, buy it. Those products are good, and a first version of anything custom will not beat a mature one on features.

Typical engagement and investment

Most start as a focused business system and add layers. Published pricing ranges are on the pricing page, and the configurator will price a scope directly.

Next step

Describe what is going wrong and you will get a preliminary plan with the bottlenecks named, including when the answer is to fix a process rather than buy software.