Files are the contract language of contracting

When we started PaperTight, the obvious product to build was the one everyone expects: replace the spreadsheets. Turn the timesheet into a form, the invoice into structured fields, the whole billing pack into a database. It’s the instinct of every software team that looks at an industry running on Excel.

We decided not to. Here’s the thesis we built the company on instead: in contracting, the file is the shared language. Don’t replace it — control it.

Why Excel and PDF won

A timesheet in Excel isn’t a limitation people are stuck with. It’s a format every party already understands. The subcontractor fills it out, the accountant reads it, the auditor accepts it, and the client’s finance team opens it without a login or a tutorial. A PDF invoice is legible on a decade-old laptop and a phone on a construction site alike. These formats didn’t survive by accident — they survived because they’re the neutral ground where everyone can meet.

Ask everyone in that chain to abandon the file for your web form, and you’re not removing friction — you’re asking an entire industry to learn a new language so your database can be tidy.

The real problem was never the file

Look closely at the pain and it’s never the spreadsheet itself. It’s the layer around the spreadsheet that’s missing: which version is current, whether it’s been approved, who changed it, what’s still outstanding for the period. That’s not a formatting problem. It’s a control problem — and control is a layer you can add without touching the file.

So that’s what PaperTight is. Your Excel, Word, and PDF stay exactly as they are, the source of truth. Around them we add the missing layer:

• ·Version control per document slot, so “current” is never a guess.
• ·An approval workflow, so nothing counts as done until the right person signs off.
• ·Readiness tracking, so a period’s status is a number, not a hunch.
• ·An activity trail, so who-did-what is a record, not a memory.

Meet the industry where it works

This is a quieter product than “rip out Excel,” and we think that’s the point. The teams we build for don’t want a revolution in their file formats; they want the month to close without a reopened spreadsheet and a dozen chase emails. You get that by respecting the language everyone already speaks and fixing the thing that was actually broken — the control around it.

Files are the contract language of contracting. We’re not here to translate them away. We’re here to make sure everyone’s reading the same page.