Bespoke helpdesk software

A ticket system built around your business.

Off-the-shelf helpdesks charge you per seat, forever, for software that only half fits. We build you your own — shaped to the way your team actually works, hosted for pennies, and yours to keep.

Book a 30-minute call See what we built for ourselves

Fixed price No per-seat fees You own the code

Open tickets 14 open · 3 unassigned

#4032 Sage won't open after the update Northgate Dental · Chapel Allerton New 4m

#4029 Re: New starter — laptop and mailbox Halloway Group · Head office Customer reply 18m

#4024 Card machine offline since 8am Ravensworth Pharmacy · Site 3 Attention 1h

#4019 Wi-Fi dropping in the back office Marsden Care · Beech House Scheduled 3h

#4011 Quote for eight replacement laptops Kelsall & Byrne In progress 1d

#4008 Printer jam cleared, driver reinstalled Northgate Dental · Roundhay Resolved 1d

Red means one thing in a Precinct system, and it never means anything else: a customer is sitting there waiting for you.

Choose the mark Click one — it swaps the logo in the top-left. Tell me which you want and I'll delete this strip.

37,147 tickets carried across from the old system, with every note and attachment

4 days from first live ticket to the whole team working in it

£26 a month to run, down from over £1,000 a month in licences

0 per-seat fees, now or later — hiring costs you nothing extra

The honest version

Off-the-shelf works until the day it doesn't.

There is nothing wrong with buying a helpdesk. Most businesses should. But there comes a point — usually somewhere between the fifth engineer and the five hundredth customer — where the tool starts telling you how to run your business.

The bill

You rent it forever

Ten people on a £40-a-seat plan is £4,800 a year. Grow to fifteen and it's £7,200. After five years you've spent the price of a small car and you own nothing — not a line of code, not the database.

The fit

It only half fits

Every helpdesk assumes a shape of business. When yours is different — one customer with forty sites, a single shared inbox, engineers who work from a van — you spend your days working around the software instead of in it.

The exit

Your history isn't yours

Years of tickets, time entries and email conversations live in somebody else's database. Exportable in theory. In practice, the thought of leaving is exactly what keeps you paying.

What we build

A proper helpdesk, not a form with a database behind it.

Bespoke doesn't mean starting from a blank page. We've already built and proven the hard parts — email, migration, telephony, the customer model. Your system is assembled from working components and then shaped to your business.

Email in and out

Your support inbox becomes the ticket queue. Replies thread properly, attachments arrive intact, and nothing lands in a black hole.

A customer model that fits

Company, then site, then contact. So "the Wi-Fi is down" tells you which building, not just which company — and your reporting finally adds up.

AI triage on arrival

Every new ticket gets read the moment it lands: a plain summary, a suggested priority, and the questions you'll need answered before you can start.

Phone calls on the ticket

Calls recorded, transcribed and attached to the job they belong to. When a customer says "I rang about this last month", you can see exactly what was said.

Desk phones that know who's calling

An incoming call puts the customer, their site and their open tickets on screen before anyone picks up. Click a number to dial it.

A customer portal, no passwords

Your customers see their own tickets by clicking a one-time code sent to their email. No accounts for you to create, reset or revoke.

Time, diary and templates

Log hours against the job, book work into the shared calendar, and answer the fifty questions you get every week with a saved reply.

An open door to your own data

A read API from day one, so the dashboards, billing sheets and reports you already rely on keep working — pointed at your system instead of a vendor's.

Not every business needs all of this, and we won't sell you the ones you don't. The discovery day exists to work out which half of this list is actually yours.

Proof

We built the first one for ourselves.

Precinct exists because a UK IT support company — eight engineers, five hundred–odd customers — was paying over a thousand pounds a month for a helpdesk that could not tell the difference between a customer and one of their forty buildings. Nearly a third of their tickets sat under a single flat record.

So we stopped complaining about it and wrote our own.

The first ticket landed on day one. One engineer worked in it alone for a day to shake out the rough edges. The evening after that, the support mailbox was pointed at the new system for good, and the following morning all eight staff moved across. The old system was kept running alongside as a fallback and quietly went unused.

It has been the only route a customer email takes into that business ever since — email, attachments, phone calls, triage, the customer portal, the lot.

Do this for us

The migration, in full

Tickets carried across37,147

Time entries carried across63,009

Customer contacts2,041

Call recordings indexed1,492

Staff moved over8

Days to full changeover4

Old licence cost£1,000+ / mo

New running cost≈ £26 / mo

History left behindNone

How it works

Four stages, and you can stop after the second.

Nothing gets built until you've seen the whole scope and the whole price. If the proposal isn't worth it, you've lost a day and we've lost a day.

A day with your team

We sit with the people who answer the phone and watch how work actually arrives — not how the process document says it does. That's where the requirements really are.

A fixed-price proposal

One document: what your system does, what it doesn't, what it costs to build, what it costs to run. One number, not a day rate. Say no and you owe us nothing further.

Build and migrate

We build it and move your history into it — every ticket, note, attachment and logged hour. You get a working copy to poke at long before anyone depends on it.

Go live, with a net

Your old system stays switched on alongside until your team stops reaching for it. Then we hand over the code, the database and the documentation.

What it costs

One price to build it. Pennies to run it.

We can't put a figure on this page honestly, because the honest figure depends on what you need. What we can tell you is the shape of the deal, and it doesn't change.

The build One fixed price

Quoted after the discovery day, before a line of code is written. Not a day rate, not an estimate that drifts.

Per user Nothing, ever

Add your tenth engineer, or your fiftieth. The bill doesn't move. This is the whole point.

Running cost A server and a domain

A system carrying nearly forty thousand tickets runs comfortably on a £12-a-month server. Ours costs about £26 a month all in, and we pay it, not you.

Afterwards Support if you want it

An optional monthly retainer for changes and fixes. Cancel it and your system carries on working — it's yours.

Before you ask

The questions everyone asks first.

Who owns it when it's finished?

You do. The code and the database are yours, handed over with documentation. That's not a concession we make reluctantly — it's the reason to do this instead of renting.

What happens if you disappear?

You still have a working system, the source code and the database, on a server in your name. Any competent developer can pick it up. Compare that with what you'd have on the day your current vendor puts their prices up.

How long does it take?

Ours went from nothing to eight staff working in it in four days — but that was our own business, our own engineers, and we already knew exactly what was wrong. For yours, plan in weeks. We'll give you a real date in the proposal, not a range.

We've got years of history. Does it come with us?

All of it. Tickets, notes, attachments, contacts, logged time, closed jobs from six years ago. We move it before you switch, and you check it before you commit. Nothing gets cancelled at the old vendor until you've seen your own data in your own system.

Will it work with the tools we already use?

Usually, yes. Microsoft 365 mail and calendars, VoIP phone systems, and your existing spreadsheets and dashboards through the read API. Anything with a documented interface is a conversation rather than a problem.

Where does the data live?

On a server in London by default, under your organisation's name. If you need it somewhere specific for a contract or a policy, say so on the discovery day and that's where it goes.

Is this just for IT companies?

No. It started in IT support because that's the business we know, but a ticket is a ticket: anything where work arrives by email or phone, gets assigned to somebody, and has to be chased until it's done.

Next step

Tell us what your current system won't let you do.

Half an hour on the phone, no slides. If buying off the shelf is the right answer for you, we'll say so and you'll have lost thirty minutes.

Book a 30-minute call Ask a question by email