Marapone ScopeGuard

01

Reading exclusions, not just inclusions

The commercially dangerous sentence in a subcontractor proposal is almost never a line item. It is a clause: “excludes winter concreting” on a structure running November to March, or “fire alarm verification by others” on work that cannot be occupied without it.

The engine reads the master documents and every proposal, then cross-references them — missing scope, required scope explicitly excluded, double coverage between trades, interface grey zones, unusable pricing, and addenda that were never acknowledged.

02

Every finding is citable

A finding nobody can check is worse than no finding, because it costs an estimator an hour to disprove. So each one carries a plain-language explanation, a citation on both sides — the clause in the master documents and the page and line in the sub's letter — a confidence score, and a cost exposure range with its stated basis.

That structure is what makes the output usable in a buyout meeting rather than just interesting.

03

Proven on a real package

The app ships with a full Toronto buyout — a project manual, three addenda and fourteen real subcontractor proposals — that runs through the same reader, extractor and cross-reference engine a customer's own documents go through. Nothing about the demo is canned.

On that package it finds, among other things, an excluded fire pump that explains why the sprinkler price looks sharp, an air-barrier tie-in that both the glazing and envelope trades excluded, firestopping that nobody carried at all, and four proposals that never acknowledged Addendum 3.