Procore alternatives for small UK contractors

What is Procore actually built for?

Large contractors running many concurrent projects with dedicated commercial and document-control staff. It covers project financials, budgets and forecasting, RFIs, submittals, drawings with formal revision control, quality and safety workflows, and a long list of integrations. The depth is real and so is the implementation effort.

Pricing is quote-only and scales with project volume, headcount and which modules you take. That's a reasonable model for a business with a procurement process, and a poor fit for a firm where the person evaluating it is also the person on site.

Its answer to the people outside the business is the collaborator login: subcontractors, architects, engineers and owners get their own account on the project at no extra cost, and use it to respond to RFIs, submit quotes and work submittals. On a large job with a document controller that works, because somebody's job is to make the collaborators use it. On a small job it's one more account the architect never activates.

Why do smaller contractors bounce off it?

Cost is the obvious one, but it's rarely the whole story. The second reason is that the modules a small firm would use are a fraction of what is being bought, and the third is that platforms of that depth need someone to own them. If nobody in the business is responsible for keeping the system tidy, it degrades into an expensive file store within a year.

The honest test is whether you have a person whose job includes running it. If you do, the depth pays. If the answer is "we all sort of do", you want something that stays useful without an owner.

There is a fourth reason that has nothing to do with size. The people whose decisions hold up a small job are outside the business: the client who has to approve the variation, the architect who has to sign the detail, the subcontractor who has to accept the day rate. A platform that gives each of them a login has solved the problem for the firm that can make them use it. The firm that can't is back to email, and email is where the "I never agreed to that" conversation is lost.

What do you actually need instead?

For most firms in this bracket the real requirement is narrower than the shortlist suggests. Write down what would change if the tool vanished tomorrow, and it's usually the same short list.

Notice what isn't on it. Nobody in a firm this size misses the forecasting module or the submittal register, because nobody was using them. What they miss is the signed variation they could not find, and the drawing revision the architect swears was never the one approved.

• Decisions from the client, the architect and the subcontractors, signed, so nobody can say they never agreed
• One place the current drawings and documents live, with the version history when a revision is questioned
• Site photos filed against the job rather than in a phone
• Reports you would be happy to hand to a client
• The client able to see their part of the job without ringing you, and without a login they will never use
• A record of who did what, for when a question lands later

Where does Portal Worx fit?

It covers that list and stops there, and it starts with the first item. You upload the drawing, the variation or the certificate to the job and send one person a link. They open it on their phone with no account and nothing to install, read the file itself, leave a note or ask a question, and approve or decline with a drawn signature. If you asked for it, they enter a one-time emailed code first, which proves whoever signed had control of that inbox at that moment. The record comes back dated, signed and pinned to the exact file they saw with its SHA-256 fingerprint, and it stays on the job. A new revision supersedes the old one and the old approval stays on the record. Unanswered requests are chased from the same screen.

Behind that: documents in categories with their own access and a version history, site photos in folders, share links to a file or a whole folder with an expiry, reports built from templates that export to a PDF with your logo, threaded messaging, a year-long activity trail filtered so nobody sees an entry for something they cannot open, and an AI summary of where a job stands.

Pricing is published, from £29 a month, with unlimited users and unlimited sign-off requests on every plan, no quote and no per-seat maths. It also needs no owner. There's nothing to configure before it's useful beyond creating a project and sending the first request.

Who should stay with Procore?

If you need RFIs, submittals, formal drawing revision control with transmittals, budgets and forecasting, or commercial workflows, Portal Worx has none of them and isn't a smaller Procore. It also has no scheduling, no estimating, no job costing and no invoicing.

Being blunt about it: if you genuinely run the commercial side of large projects through software, and you have somebody whose job is to run it, pay for the platform that does it. Stay too if your architects and subcontractors already work inside your Procore projects, because then the collaborator login is doing its job.

The firms this suits are the ones who wanted the document side and the sign-off and could not justify a suite to get it. Two limits to know before you decide: one person approves one request, with no chain of approvers and no delegation; and the code step proves control of an email inbox, not identity, so a document that needs proof of who a person is needs a notary rather than us.

How should you run the comparison?

Trial the shortlist on one real job at the same time, with real drawings and one real person from outside your team: the architect, or the client. Send them one thing to approve on each finalist and watch what they do with it. A demo project proves nothing, because the failure mode you're testing for is what happens in week three when everyone is busy and the architect hasn't created the account.

And price the whole crew rather than one seat, including the people you don't employ. Whether clients and everyone else on the job are billable, and whether they have to become users at all, changes the total more than the headline rate does.

Last, count what you are holding at the end of the trial. If the architect's approval is a status somebody on your side clicked, you have a note. If it's a dated, signed record pinned to the exact revision they opened, with the file's fingerprint on it, you have evidence. Only one of those ends an argument.

Common questions

Is Portal Worx a smaller version of Procore?

No. It covers sign-off from clients, architects and subcontractors who never log in, plus documents with version history, site photos, reports, messaging and the activity trail. There are no RFIs, submittals, budgets, forecasting or commercial workflows.

Why doesn't Procore publish a price?

It prices on project volume, headcount and module selection, which requires a sales conversation. That suits a business with a procurement process and suits a small contractor much less.

Does the architect or subcontractor need a login?

Not on Portal Worx. They open a link on their phone, read the file, and approve or decline with a drawn signature. Procore gives collaborators their own account instead, which works when somebody's job is to make them use it.

What does Portal Worx cost?

Published on the site, from £29 a month with 20 per cent off annually, with unlimited users and unlimited sign-off requests on every plan. The trial is 14 days on Professional with no card.

Does it need someone to administer it?

No. There's nothing to configure before it's useful beyond creating a project and sending the first request. Permission fine-tuning exists on Professional and Business if you want it.

Related

• Buildertrend alternatives for UK builders
• Construction document management software
• Design approval from a client who will never log in