Pricing that suits a subbie’s books

Subcontractors, specifically. You can run a subbie business on Procore or Buildertrend — you get your own jobs and your own cost codes, and that part works. The catch is what they don't cover: pricing off your own rates, committed cost by code, progress claims and forecast margin. Most subbies fill that gap with an Excel template beside the software and reconcile the two by hand. Subino was built for subcontractors from the start, so the half you were doing in Excel is the product.

It was built in a façade, cladding and carpentry business, and that shows in the examples — but nothing in it is cladding-specific. The cost codes are yours, the rates are yours, and a scope is whatever you price as one thing. If your work is priced by scope against cost codes, quoted to a head contractor and claimed progressively, it fits. If you invoice on completion for small domestic jobs, it is more machinery than you need.

One person quoting and running their own jobs is a real use of it — that is the Solo plan, and it is how the product started. Where it earns its keep fastest is the moment you are carrying more than about five live quotes at once, because that is the point where remembering which one needs a phone call stops working.

You enter a scope and its price on the estimate. When you win the job, that same number becomes the budget, the claim line and the labour target — per cost code, with nothing re-typed. Change a rate on the estimate and everything downstream moves with it. Zero double entry.

Two things: your cost codes, and enough of your rates to price a job. Everything else fills itself in as you work — the rate library builds from the lines you price, and templates come from the jobs you have already done. You do not have to load your history to start; the sensible first move is to price your next real job in it alongside your spreadsheet and compare the two.

Yes — you don't start from zero. You can import your jobs, contacts, purchase orders and bills from a spreadsheet, and coming off Buildertrend you export those four and paste them into the template, so your live jobs and budgets come with you. Your rates and cost codes are the part worth keeping, and they come with you first.

No, and we'd talk you out of it. Jobs already half-run in a spreadsheet are usually better finished there. Start with the next job you price, so the first thing you see is the estimate feeding the budget rather than a migration.

Migration assistance, onboarding and training sit on the plans rather than as a separate invoice — which plan they sit on is part of what is being finalised. Ask on the demo and we will put it in writing.

Yes. Connect Xero once per company, push a supplier bill through to it against the right account, and the paid status and payment dates come back — so the job's actual cost and your ledger tell the same story. MYOB is not supported today; if that is a blocker, say so on the demo rather than after.

Yes, properly. Retention percentage and a cap, taken on each progress claim, with the amount already held carried forward from the previous claim rather than recomputed — so a variation later in the job cannot silently restate retention you took six months ago.

Claimed by percentage complete against the same scopes and cost codes you priced, with the split a head contractor expects: original contract sum, approved variations, contract sum to date, less retention, less previously claimed. The schedule of values is frozen when you claim, so last month's claim stays exactly what it was.

Prices are held ex GST and GST is shown where it belongs — on the proposal, the claim and the bill. Where a supplier's quote is read in from a PDF, the GST is read off the document and shown to you rather than assumed.

That is the point of it. Budget, committed, actual and forecast on every cost code, so you see a code sliding in the week it happens. Across the book there is a work-in-progress view — what you have earned against what you have actually billed — which is the number that tells you whether you are funding the builder.

Plans and billing terms are being finalised — the figures on this page are placeholders while that happens. Book a demo and we'll tell you exactly what is on the table today, in writing, in Australian dollars.

Yes — clocking on against a job and a scope, the site diary with photos, tasks and drawings are all built for a phone first. They are the screens most likely to be opened in a car park with one hand.

Permissions are enforced in the database, not hidden in the interface. The crew, the office and management each see what their role allows and nothing else — so margin stays with the people who are supposed to see margin, even if somebody goes looking.

No. You share a variation, an order or a claim as a secure link. They open it, see only what you shared, and approve or decline it there. Their answer lands back on the job with a timestamp, and the link can be revoked.

Yes, and it is enforced at the database rather than by the application asking nicely — each company's rows are fenced by row-level security, and the isolation is tested by an automated probe rather than assumed. Your competitors cannot be shown your rates by a bug in a screen.

It is yours. Cost sheets, budgets and timesheets export to CSV from the screens you use them on, and if you leave we will get you a copy of the rest rather than making you scrape it out. Nothing about your rates or your history is held hostage.

Book a demo. We'll walk through your own estimating and job-costing workflow, ideally on a live job of yours, so you see how your numbers behave in Subino before you commit to anything. There is no self-serve trial today — the first conversation is with the person who built it.