Straight answers,
no sales waffle.

A straightforward plot-and-stage job takes about twenty minutes. A guided wizard walks you through the payment structure, VAT, CIS, retention and payment terms, explaining each option in plain English. If your plots repeat — and on a housing site they always do — you build a house type once and apply it to every plot of that type in one go.

No, and we'd advise against it. Start with one live site, run it alongside your spreadsheet for a month, and see whether the numbers agree. Add the rest when you trust it.

Then use the bill of quantities instead. Build a BQ with sections and subsections, claim against quantities and percentages, and produce a BQ application pack. Same applications, same reports, different way of measuring.

No. It's built for the person actually running the job — usually the owner. If anything, it exists because most subbies don't have a QS and are doing this on a Sunday night in Excel.

No. SubbyWise models the way housebuilders and main contractors already work. You set your cut-off day, payment terms, retention rules and CIS position per project, and the app follows your contract — not the other way round.

Standard mode is: you send your application, they pay what they decide, and you match the remittance to see what actually landed. QS certification mode is: you claim, the QS certifies a figure, and you invoice against the certified amount — with the variance between claimed and certified shown so you can challenge it. Your mode locks once you raise the first application, so nothing switches mid-project.

They don't have to. Your client never needs an account. They receive the same documents they get today — an application, an invoice, a statement — just produced in seconds and on your headed paper.

Give them their own external QS login. They prepare and submit applications inside the system, so you can see exactly what went out, when it went, and when payment is due — without handing over your whole account.

You match the remittance to the stages it was meant to cover, and anything that doesn't reconcile is flagged as underpaid or overpaid. The payment variance report then gives you a line-by-line breakdown you can send back to the client — every line marked matched, underpaid, overpaid or pending.

They are tracked separately from the main application, with their own references and approval statuses. Variations can carry their own VAT and retention rules where the contract treats them differently, and contra charges are recorded against the project so you can see the effect before it lands on a remittance.

Yes, including the parts that usually get fudged. The deduction is taken on labour only — materials are recorded against the application and removed from the CIS base — and CIS is handled correctly on retention release, when the money finally comes back years later.

Set it on the project and every application and invoice carries the correct treatment and wording. Variations and customer upgrades can be set differently where they are billed on another basis.

Yes — Sage 50, Xero, QuickBooks Online, or a plain accountant CSV. You map your nominal codes and tax codes once in settings (including the reverse-charge code for whichever package you use) and after that it is pick the format, pick the period, download. Retention, variations and contra charges come through as their own lines.

No, and it is not trying to. SubbyWise is where your applications, payments and contract position live; your accounts package is still where your accounts live. The export is the bridge, so nothing gets typed twice.

Yes. Quick invoices cover day works, small jobs and materials, with a saved client address book you can import from your accounting package.

Retention is held per valuation at your rate, capped by value or percentage if your contract says so, and tracked through to first and second release. You get alerted as release dates approach, and the final account sets out the whole retention position when you close the job.

27 document types out of the box: insurance (employers’ liability, public liability, product, professional indemnity, contractors all risks, plant), SSIP accreditations (SMAS, Constructionline, CHAS, SafeContractor, Acclaim), cards (CSCS, CPCS, NPORS) and training tickets (SMSTS, SSSTS, first aid, asbestos awareness, IPAF, PASMA, face fit, fire marshal and more). If a contractor asks for something unusual, you add your own type.

No. Operatives are person records, not accounts — the labourer who will never open a laptop still appears on the training matrix. If someone does have a field login, you can link the two so they stay in step.

Before it matters. Insurance warns at 60, 30, 14 and 7 days; accreditations from 90 days out, because scheme renewals are slow; training tickets from 60 days. Alerts appear in the app and the cardholder can be emailed directly.

Either a branded PDF pack — cover page, company details, insurance summary, accreditations, training matrix, and the real certificates merged in behind it — or a live link that shows your current position whenever they open it, with an expiry date, a revoke button and a view count.

The old record is archived, not overwritten. So when somebody asks in two years whether you were covered in March, you can still answer.

Yes. It installs on an Android or iPhone like an app, and the whole booking flow works offline. Assessments queue on the phone and sync the moment signal comes back — nothing is lost in a basement.

No. Field users see the payment matrix for the projects you allow them, and they mark stages complete. They cannot see applications, invoices, values, clients, settings or reports.

They can't book below what has already been claimed, so numbers only move forward. Everything they submit is reviewed in the office before it becomes an application.

No. Multi-company support keeps them completely separate, each with its own branding, numbering, settings and data, under one account.

Only people you invite into your company. Every record is scoped to your company, field users are restricted to assessment, and an external QS only sees what they need to prepare applications. Certificates are stored privately and served behind your login — never on a public URL.

It goes to a recycle bin rather than disappearing, and application lifecycles are protected so a certified claim cannot be casually unpicked. There is also a nightly integrity check that verifies the figures across applications, payments and ledgers still agree.

It is yours. Every report exports to PDF and Excel, and your invoice data exports to Sage, Xero, QuickBooks or CSV, so you can take a full copy out at any time while your account is open.

On UK/EU cloud infrastructure, over HTTPS, with encrypted backups. We do not sell or share your data with anyone.