Operating systems for contractors

Your own software, without your own software team.

Most roofing companies run on four or five tools that were built for somebody else, and a lot of re-typing in between. We replace that with one system, shaped to the way your company already works — and it belongs to you.

Starting with roofing

Score your operation What we build

You get a score out of 100, a breakdown across eight areas, and the three things costing you the most. On screen, straight away — no email required.

01 / The problem

Your business runs on you. That is the ceiling.

Ask a roofing contractor where a job lives and you will get a tour. It starts in a text thread. The measurement is in one place and the estimate in another. Photos are on somebody's phone. The claim is in an email chain. The invoice is in QuickBooks, which never saw the job — only the bill.

Every one of those is a perfectly reasonable tool. None of them is the problem. The problem is the gaps between them, and the gaps are staffed by a person typing the same information in for the second and third time.

You do not have a software problem. You have a seams problem — and you are paying somebody's wage to be the seam.

That is why buying another tool rarely helps. It gives you a fifth place for a job to live and one more handoff for something to fall through. And things do fall through: not inside a tool, where somebody would notice, but in the space between two of them, where nobody owns it.

02 / The cost

What it is actually costing

Three things, and none of them show up as a line on your P&L.

Money that was earned and never billed

The change order made on a Friday afternoon and remembered at invoicing, or not. The supplement nobody caught because catching supplements depends on who is running the claim that week. That is not a bookkeeping problem — that is work you did for free.

Pricing set by instinct

If job profit arrives weeks after the job, you have already priced the next four like the last one. Instinct is right until materials move or a crew slows down, and then you find out in the spring.

You

Every answer routes through one person, so the business grows exactly as far as one person's attention reaches and no further. The honest test is not whether you could take a holiday. It is whether you could hire someone next month and have them be useful — because if everything worth knowing is in your head, there is nothing to hand them.

03 / Why now

Why that last one is getting worse

The work is not going anywhere. Roofing contractors in the US are a $100.5 billion market in 2026, up on the year before. Demand is not the constraint.

People are. The construction workforce averages 42 years old, roughly one in four workers is over 55, and only about one in ten is under 24. Industry reporting puts more than 40% of the current workforce within a decade of retiring, against a shortfall already measured in the hundreds of thousands.

A business that only works because one person remembers everything cannot absorb a new hire. In a trade running out of people, that stops being an inconvenience and becomes the ceiling.

Which is the real argument for building the process into a system rather than leaving it in somebody's head. Not efficiency. Not doing more with less. Being a company somebody can actually join.

04 / How we solve it

One system, and it belongs to your company.

Your jobs, your customers, your claims, your photos, your invoicing — built around the way you already work rather than something you have to reorganise around. Your language on the screens. Your job flow. Your crews using it on a Tuesday without a training course.

Estimate → Scheduled → In progress → Completed → Invoiced The job pipeline

The job pipeline board in Pontura Roofing OS, with jobs in five columns: estimate, scheduled, in progress, completed and invoiced. Each card shows the customer, the job type and the value.

The job pipeline in Pontura Roofing OS. Real screens, demonstration data — the customers are invented.

No re-typing

Entered once

A measurement becomes an estimate becomes an invoice without anybody keying it in again. The seam is gone because there is nothing to seam.

Your shape

Your stages, your words

The stages on the board are the ones your company already uses, named the way your crews already name them.

Yours to keep

Your domain, your data

It runs on your domain and the database is yours — always, not just while you are a customer.

What the system actually contains →

05 / Who it is for

The company that has outgrown the whiteboard.

There is a stage a roofing company hits somewhere on the way to ten million. The work is there. The crews are there. There are people in the office now. And the systems that got the company this far — a spreadsheet, a shared inbox, and two people who remember everything — have quietly become the thing holding it back.

That is who this is built for. Not the one-truck operation, which does not need it yet and should not be paying for it. Not the hundred-person regional, which already has an ops department and a five-year contract with somebody. The company in between, where the revenue is real, the headcount is real, and the process is still living in somebody's head.

You will recognise it if any of these are true. You hired someone and found there was nothing to hand them. Two people in the office are each half-sure who is doing what. You can feel a ceiling and it is plainly not demand.

If that is not you yet, the evaluation will still tell you where you stand, and it costs nothing. Come back when it starts to sound familiar.

A single-family home on a suburban street, seen from the pavement. — The house at the other end of the job. Stock photography, not a customer.

Where does yours sit?

Twenty-five questions, about fifteen minutes. You get a score out of 100, the eight areas it breaks into, and the three things costing you the most — with the arithmetic shown. No email wall and nothing to unlock, and now that is actually true.

Score your operation

06 / What it costs

Published, because nobody else will.

Almost nobody in this category will tell you what their software costs without putting you through a sales call first. We will, and here it is.

A build starts at $6,500 and is quoted on the size and shape of your company. After that it is from $450 a month, flat — not per seat, so putting your whole crew in it does not move the price. That covers hosting, support, and a set amount of change work every month, because the fitting never really stops.

Every competitor charges by the seat, which means hiring a crew raises your software bill. Ours does not.

If what you need is a rebuild rather than a fit, that gets quoted separately and we will tell you before you have committed to anything.

The full breakdown, and what stays yours →

07 / Who you are hiring

No company between you and the work.

No sales team. No ticket system. No roadmap vote you lose to a company ten times your size. When something breaks you will be speaking to the person who built it.

Nothing here has been sold to a hundred roofers yet. Pontura is early. If you would rather buy something with a decade of case studies behind it, that is a fair call and there are companies that have one.

How the work runs, start to finish →
What it costs, and what stays yours →
Who you are hiring →