01
Estimating and quoting
Measure, price and send a quote in your own format in minutes, using your rates, your margins and your wording. Every quote logged, every price traceable, nothing rebuilt from scratch in a spreadsheet.
Bespoke software · A division of Construction Sites
Software built around how your company actually works.
Estimating, client portals, applications for payment, job management: whatever the business keeps running into, we build it for you. Bespoke every time, at a fixed price, for established construction companies only.
The argument
Every construction company runs on a system nobody designed.
A quoting spreadsheet that only one person understands. Photos in five WhatsApp groups. Job sheets re-typed into invoices. Three subscriptions that each do sixty percent of the job. It works, until the company grows and it quietly stops working.
Off-the-shelf software is built for the average firm. Yours is not average, and the parts that make it different are exactly the parts the products do not handle. So we build the tool around the company, not the other way round.
What we build
02
Client login areas and portals
Your clients log in on your own web address and see their job: progress, dated photos, certificates, warranties, invoices and sign-off. Fewer chasing calls, and a level of service most competitors cannot match.
03
Applications for payment
Monthly valuations, per-element progress with photo evidence, variations and payment-notice deadlines in one place, with the handover pack generated at the end. Built for firms working under main contractors.
04
Job and site management
From enquiry to completion: survey app on the phone, scheduling, team logins, RAMS and method statements generated from the job data. Replaces the pile of off-the-shelf tools that never quite fit.
05
Planned maintenance and renewals
Service contracts, inspection reminders and renewals that run themselves, so the recurring income the business already has is visible, chased and kept.
06
Tender and pre-qualification library
Every policy, certificate, case study and standard answer kept current in one place, so the next PQQ or tender is assembled in an afternoon rather than a fortnight.
If what you need is not on this list, that is normal. Most of what we build starts with a problem nobody has made a product for. Tell us the problem and we will tell you honestly whether software is the answer.
How a build runs
The build is the easy part. The brief and the aftercare are the work.
01
The discovery
Half a day, on site
We spend half a day with the person who does the job today and watch how it is actually done, not how it is described. That is where the real requirement lives: the workarounds, the re-typing, the spreadsheet nobody else understands.
- The problem written down in plain English
- What the software must do, and what it must not
- A fixed price and a delivery date
02
The one-page specification
Signed before any money changes hands
One page, in plain English, that both sides sign. It covers the ninety percent of cases the business runs on, and it is the document the build is judged against. Anything outside it is a change request, priced separately, so the fixed price stays fixed.
- One page, no jargon
- Fixed price agreed from the spec
- Deposit only once the spec is signed
03
The build
Weeks, not quarters
You see working software early and often, on your own data, and the people who will use it every day get their hands on it before it is finished. Feedback goes straight into the build rather than into a backlog.
- Working versions to try, not slide decks
- Your team involved throughout
- Delivered to the date on the spec
04
The switchover
Delivered, not left to you
Existing data is migrated, the office is moved across, the team is trained and the old spreadsheets are retired. From then on the software is hosted, monitored and supported by us, as part of the arrangement, with someone to call when a question comes up.
- Data migrated and checked
- Team trained on the real thing
- Ongoing hosting and support
Who this is for
Built for companies with a team and a problem that repeats.
Bespoke software makes sense when the same job is costing real hours every week and no product on the market fits the way the company does it.
A strong fit
- An established company with a team, usually ten people or more
- A repeated problem that costs real hours every week
- Off-the-shelf tools that have been bent out of shape to fit
- Owners who want to own the software, not rent it
Probably not yet
- A start-up idea or an app to sell to other people
- Anything a spreadsheet already solves well
- A brief that is still changing every week
On cost, briefly
One fixed price, agreed from a one-page spec, before we start.
No day rates and no open-ended invoices. The specification fixes what is being built, the price and the date, and a deposit is only taken once it is signed. Hosting and support run alongside as a plain monthly arrangement, so the software is looked after for as long as you use it. It makes sense for a firm with a team and a problem that costs real hours every week; for anything smaller we will say so.
Tell us the problemQuestions, answered straight
Do we own the software?
Yes. The software, the data and the code are yours. We host, monitor and support it under the arrangement, and if you ever wanted to take it elsewhere, you could.
We already use Tradify, SimPRO or JobLogic. Does that matter?
No. Most builds either do the thing those tools do not, or replace a stack of them with one system that fits the company. Either way, your existing data comes across as part of the switchover.
How long does a build take?
Weeks for a focused tool such as a client portal or an estimating system; a few months for a full operations system. The delivery date is written on the specification and agreed before we start.
What if we want changes once it is live?
Small changes are part of support. Anything that changes what the software does is a change request, scoped and priced on its own, so the original fixed price stays fixed.
Does it run on our own web address?
Yes. A client portal or login area sits on your own web address, under your brand, and it can share a login with the website we build or run alongside a site someone else built. Internal tools sit behind a private login for your team.
Why does a website company build software?
Because we already know the trade. We have built more than a thousand websites for construction companies, and our own business runs on software we built ourselves: onboarding, agreements, client reporting and support. The software division is that same capability, pointed at your company.
Start with the problem. We will tell you if software is the answer.
Describe the thing the business keeps running into, in your own words. If it is a fit, the next step is half a day with the person who deals with it today.