Your GC uses Procore. Do you need your own system?

The question usually arrives as a complaint. “We already pay for nothing and we’re in Procore every day — why would we buy our own software?”

It deserves a straight answer rather than a sales one, so here is the straight answer. The GC’s platform and a sub-side system are not competing for the same job. One is the project’s record. The other is your company’s record. Most subs who are frustrated are frustrated because they are trying to run the second out of the first, and it was never built for that.

What the GC platform is genuinely good at

Worth saying clearly, because a lot of vendor content on this topic is dishonest about it.

Procore is a serious piece of software and it is one of the most widely used GC-side project management platforms, and it earned that. For the things it exists to do, it is excellent and you should use it rather than working around it:

• The current drawing set. The single best reason to be in it. One place that holds the live revision, so your foreman is not building from a superseded sheet somebody printed in March.
• RFIs and submittals. A real workflow with dates and accountability on both sides. Materially better than an email chain, and the date stamps protect you as much as the GC.
• The schedule. Visible, updated, in one place.
• Daily reports rolled up across every trade. Genuinely useful to a GC trying to see a whole site.
• Photos, inspections and meeting minutes tied to the project.

If your GC runs it and you ignore it, that is your own unforced error. The drawing revision alone justifies logging in.

As of October 2026, Procore also sells products aimed at subcontractors, including cost management, and they are not a joke — if you are evaluating, evaluate them properly. This article is about the structural question, not a product comparison.

The structural fact that does not change

The project in the GC’s platform belongs to the GC.

That is not a criticism. It is the design, and the design is correct — it is their project. But four consequences follow from it, and all four land on you:

1. You are a guest with the permissions they grant. What you can see, export and report on is their configuration decision, and it changes without consulting you.
2. Access tracks the job, not your company. When the project closes out, depending on how the GC configures it, your window into it can narrow or shut. Your retainage conversation often outlives your access by months.
3. One project, one platform, one GC. You do not have one project. You have eleven, across six GCs, four of whom are on different platforms and two of whom still want a PDF emailed to a project accountant.
4. Your costs were never in there. Not your burdened labor rates, not your rate lists, not your margin on the job. The GC’s system knows what they owe you. It does not know what the work cost you, and it has no reason to.

Point 3 is the one that does the damage. The information your owner needs is a portfolio number, and every GC platform is organized by project. No GC’s instance gives you a view that spans the GCs, because no single GC’s instance can see the others.

The four questions nothing on the GC side can answer

Not “answers badly.” Structurally cannot answer, because the data lives on your side of the line.

Which of my jobs is losing money, right now? This needs your committed costs, your labor burden and your billed-to-date in one place. Three different GC platforms hold a third of the billing each, and none of them has ever seen your payroll. Tracking labor hours by job and cost code is the half of this most subs are missing entirely.

What is my total pending change order exposure? You have a change order submitted 64 days ago in GC #3’s portal, one sitting in an email thread with GC #7, and two approved last month that nobody has billed yet. The total is a real number your owner needs weekly, and assembling it means opening six systems and remembering the seventh. The change order process from the sub’s seat is a chase across platforms, not within one.

What is every GC’s billing deadline this month? Every GC has a different cutoff, a different submission method and different required backup. That calendar is yours to run, and it spans all of them. Running them all at once is the article on this, and the answer is never “check each portal.”

Where is my retainage, on jobs that closed? Held money on a job finished eight months ago, where your platform access has lapsed and the only person who remembers the number has left. It is some of the most commonly lost money in the trade.

When you honestly do not need your own system

Stated plainly, because the opposite claim is where this kind of article usually loses credibility.

You probably do not need one if: you run one or two jobs at a time, for one GC, with a crew small enough that you know everybody’s hours without looking them up, and your accountant handles the billing out of your accounting package. A spreadsheet and a shared folder is a perfectly rational system at that size. Buying software to run two jobs is buying overhead, and anyone who tells you otherwise is selling.

The threshold where it changes is not revenue. It is these four, and it is usually two or three arriving together:

• More than one GC, on more than one platform or process.
• More than about four concurrent jobs, so no single person holds the whole picture.
• Self-performed labor, which means your largest cost is also your least visible one.
• Change order and T&M volume, which means money is decided in the field and lost in the office.

If none of those is true, keep the spreadsheet. If three of them are true, you are already paying for a system — in the form of someone’s weekends, and in the draws that go out light.

We wrote the honest comparison against spreadsheets on exactly this basis.

What a sub-side system actually has to do

Vendor-neutral, so you can hold anything up against it, including us:

1. Span every GC. One list of your jobs regardless of whose platform each one lives in. If it organizes by project the way the GC’s does, it has copied the wrong shape.
2. Hold your schedule of values and your draws, so your record of what you billed does not live only in their portal.
3. Separate drawn, certified and received. Billed is not agreed and agreed is not collected; one “billed to date” column hides both gaps.
4. Track retainage past closeout, past the point where you still have access to anything of theirs.
5. Carry your costs, so budget versus actual is readable while you can still act on it.
6. Be usable by the field for free. If every foreman needs a paid seat, nobody logs anything, and the system is decorative.
7. Not pretend to be the GC’s system. Anything claiming to replace the drawing set and the RFI log is overreaching, and you will end up running both anyway.

How SubMark fits — and where it stops

SubMark is built for one side of that relationship, which is yours.

• One schedule of values per job, locked when the first draw is submitted, with approved change orders added to it automatically.
• Draws through Draft, Drawn, Certified and Received, with retainage held per draw, across every GC in one table.
• A draw calendar carrying each job’s cutoff day, due day and submission method, with a reminder before the date.
• Change orders with status and aging, so pending exposure is a screen rather than an afternoon.
• T&M tags priced by the office off your own rate lists and e-signed by the GC’s superintendent on site, with a month of signed tags converting into one change order.
• Daily logs with weather, narrative, labor, materials and photos, filed from a phone.
• Job costing — labor, material and subs against the job, with QuickBooks Online bills and purchases pulling in hourly once auto-pull is on, so cost sits against the right job.
• A trade pack for 29 trades that sets the thing up in your own terminology at setup.

Now the limits, because they are the reason to trust the rest:

There is no Procore integration. None. No Textura, no GCPay, no owner-side portal. You still submit in whatever system each GC requires, exactly as you do today, and you log what you submitted. If a vendor tells you they will submit your billing into your GC’s platform for you, make them demonstrate it on your GC’s instance before you sign anything.

SubMark does not hold the drawing set, the RFI log or the submittal register. Procore is better at those and it is where your GC wants them. Use it for that. We are not trying to win that argument.

SubMark does not produce the owner-standard payment application or continuation sheet as a PDF or in any other format, and it is not on the roadmap. What it holds is your own record of the billing. If your GCs require that format, here is how SubMark fits alongside it — honestly, including the case for buying a form product instead.

Lien waivers are tracked, not generated — which ones you sent up the chain, which are signed, and which draw is waiting on one.

Pricing, since it is the next question: you pay one company subscription with your first few office users included, then per office user after that. Field users and the subs you invite are free and unlimited, which is deliberate — a system the field cannot afford to use is a system nobody updates. The pricing page has the whole breakdown, and it is the only place we quote the figures so they can never drift out of date here.

The answer, in two lines

Your GC’s platform is the project’s record, and it is good at being that. Keep using it.

What it cannot be is your company’s record, across every GC, including the jobs that closed. If that record currently lives in a spreadsheet and one person’s memory, the question is not whether you need a system. It is how much the current one has already cost you.

Procore is a registered trademark of Procore Technologies, Inc. SubMark is not affiliated with, endorsed by or integrated with Procore. Product details reflect Procore’s public pages as of October 2026.