AMPLIS
Book a demo
AMPLIS
Book a demo
Your field builds the work. Your office bids and bills it. The margin dies in the gap between them — and every system in this industry makes the field report to the office instead of closing it.
Both halves of your company are doing their jobs. The problem is that nothing carries what one of them knows across to the other — so the field does work it never gets paid for, and the office bids on numbers nobody has verified in years.
Every other system in this industry makes your crews report to the office. That's the wrong direction.
A daily log is worth something on its own. But the same record, once it crosses into the office, does a second job nobody else in this industry is doing: it becomes the measured history of what your crews actually produce. That history prices your next bid. Every day you run the circuit it gets more accurate — and it belongs only to you.
Rock, wet ground, a sub who showed up late, a machine down two hours. Everything that decides whether this job makes money happens out here — and today almost none of it survives the drive home.
Field data never reaches the office because capturing it has always been the foreman's problem. AMPLIS makes it a thirty-second problem — he types it the way he'd text you, and the software asks for what he left out.
I started in the trench and worked my way into the project manager's chair. What follows is the same company, the same week, the same job — seen from each end. Every pair below cost us real money.
Same company. Same week. Same job. Two halves that never spoke to each other — and it was slowly bleeding a good company to death.
So I built the thing that carries one side across to the other.
Change these to match your operation. The math is yours, not ours — every assumption is a dial you control, and we'd rather show you the arithmetic than a testimonial.
Total contract volume you put in the ground each year.
Share of volume that becomes extra work — rock, dewatering, GC delays, differing site conditions.
Be honest. Of that extra work, how much reaches a ticket with enough backup that the GC pays it?
Work your crews performed, that you paid for in labor, fuel and iron, and that nobody ever invoiced.
An estimate from your own numbers, not a guarantee. It also counts only one side of the circuit — it makes no attempt to price what accurate production rates are worth on next year's bids.
Not ten tools that share a login. Everything on the left feeds everything on the right, and the band across the bottom is where the compounding happens.
A rough note in, a complete log out — with AMPLIS prompting for the crew, the iron and the quantities he forgot.
Crew hours and machine hours captured against the cost code the day they happen.
Snap it, tag it, assign it. The sub gets a secure link, fixes it, uploads proof. No account, no app.
Near-misses and toolbox talks captured in thirty seconds, categorized and date-stamped.
Installed quantities roll from the field into your pay application for review, instead of reconstruction.
Vendor invoices checked against the executed subcontract. Unit price mismatches flagged before the check goes out.
Every sub quote for a package side by side, with exclusions pulled out of the fine print and scope gaps flagged.
Bids built on what your crews actually produced, instead of what the last estimator's spreadsheet assumed.
Raised in the field, routed to the GC with a secure link, tracked to signature.
Budget, committed and actual down to the cost code — at 2pm on a Tuesday, not at month-end.
Plans, specs and geotech answerable in plain language with the page cited — same answer in the trailer and the trench.
The measured record of what your crews really do, in your ground, building quietly every day.
No, and we'd tell you not to. AMPLIS sits alongside what you already run. It captures clean, structured field data and hands it off to your accounting system to cut checks. If you eventually decide it replaces something, that's your call to make later — it isn't a condition of getting started.
So did the ones this was built for. That's the entire design constraint. There is nothing to install and no cost codes to memorize. He types a couple of rough sentences the way he'd text you, hits Format, and answers three short questions. The office does the reviewing; the field just says what happened.
Honest answer: it compounds. We start from your recent bids and your rate sheet, so you aren't beginning from zero — but the rates get meaningfully better once your own crews have logged against them for a season. The documentation side pays for the software long before that happens, which is why we lead with it.
Flat annual rate with unlimited field users. We don't charge per seat and we don't raise the price because you grew from $20M to $50M — punishing a contractor for winning work is a strange way to run a software company. The exact number depends on the size of your operation, and we'll give it to you on the first call.
A working heavy civil project manager who built it for his own jobs, plus a small engineering team. That's a real trade-off worth being honest about: you get someone who has stood in the trench and will answer his own phone, not a support queue at a company with two hundred employees.
Your production rates and unit costs are the most competitively sensitive numbers your company owns. They're isolated to your account at the database level and are never pooled, benchmarked or shared with another contractor. Hosted on AWS, exportable at any time. If you leave, you leave with your data.
Not a discovery call and not a slide deck. Tell us about one job that went sideways, and we'll show you exactly where it fell through the gap.