Pontura
Take the evaluationScorecard
Menu

Pontura

One system, and it belongs to your company.

Not a fifth place for a job to live. The place it lives, from the first call to the final invoice.

We are not consultants. Nobody is going to hand you a process document, a slide deck, or a recommendation to run leaner. We write software.

What that buys you is not a longer feature list. It is the removal of the handoffs — the moments where a job leaves one tool and has to be carried into the next one by a person who might be busy, or off that week, or new.

01  /  The system

What is actually in it

Six things, and the point is not that any one of them is clever. The point is that they are the same system, so nothing has to be typed in twice and nothing sits in the gap between two tools where nobody owns it.

Jobs

One place a job lives

From the first call through to the final invoice, in the stages your company already uses rather than somebody else's idea of a pipeline.

Customers

The whole history

Every job, every conversation, every document against the customer it belongs to — not spread across a phone, an inbox and a filing cabinet.

Claims

Not dependent on who is on

The claim sits on the job with the paperwork attached to it, so catching a supplement is not a matter of who happened to be running it that week.

Photos

Filed, not texted

Shot on the roof and attached to the job on the way past, so they are there when the adjuster asks rather than on somebody's camera roll.

Invoicing

Billed from the job it came from

The change order made on a Friday afternoon is on the job, so it reaches the invoice whether or not anybody remembers it three weeks later.

Your numbers

Job profit while it matters

Not a report you request. What a job actually made, close enough to the job that it can still change how you price the next one.

02  /  The difference

Built for one company, not for the average of everybody

The software you can buy off the shelf was built for a thousand roofing companies at once, which means it was built for the average of them. Every one of those thousand has to bend a little to fit it. The bending is invisible until you count the workarounds.

A system built for one company does not need a workaround, because there is nothing to work around.

That is also why a feature you need is not a request that joins a queue. There is no queue. There is your system and the changes you want made to it.

How the work actually runs →
What it costs →

Start with where you actually stand

Fifteen minutes, scored, results on screen immediately. It is the fastest way to find out whether any of this applies to you.