// For subcontractors
You sent the RFI eleven days ago. The GC didn't respond. The work proceeded around you. Now there's a delay claim with your name on it for something that wasn't your scope. Marapone builds private AI that tracks every RFI you sent, logs every delivery, and pre-builds the claim documentation you wish you had three months ago. You own the model. You own the data. No subscription.
Built for mech, EC, and finishing trades running concurrent jobs across multiple GCs · Toronto + Rome
// The four things that quietly cost you money
PAIN 01
You sent the question on day three. It's day fourteen. No response. Your guys are standing around or guessing. When it finally comes back you've already eaten the delay — and the GC says you should have proceeded.
→ FIX: RFI Intelligence (sub-side) tracks every RFI you've issued, ages it, and pre-drafts the follow-up note plus the impact statement if it's not answered in time.
PAIN 02
Three months later the GC claims your gear arrived late. Your foreman knows it didn't. The signed slip is somewhere — maybe a crumpled photo on his phone, maybe the supplier's portal. By the time you find it the back-charge is in the contract closeout.
→ FIX: Daily Log Synthesizer turns the foreman's two-minute voice memo into a structured log with deliveries, photos, and timestamps. Defensible from the day it happens.
PAIN 03
The GC issues a $40k back-charge for controls wiring you never priced and never agreed to. You know it wasn't in your scope. Proving it now means digging through six months of email and the original bid documents.
→ FIX: Subcontractor Scope Gap Finder reads your original scope letter against the spec and the GC's contract, and surfaces exactly where the line was drawn.
PAIN 04
You know you had four weeks of delays caused by missing information. Your file has three emails and a calendar entry. The PM left. The foreman's notebook is half-legible. You write off the claim because you can't make it stand up.
→ FIX: The build keeps a continuous, timestamped record of RFIs sent, responses received, and field impact — so when you need a claim, the file already exists.
// What we build for subcontractors
Most sub builds bundle these three modules. Trained on your scope letters, your standard pricing, and the way you actually work in the field. Not a generic chatbot.
BUILD 01
Tracks every RFI you've issued, ages it against the contract response window, and drafts the follow-up note plus the impact statement when the GC goes silent. Your record stops being a guess.
BUILD 02
Your foreman talks for two minutes. The system writes a structured log: crew, deliveries, blockers, photos with timestamps. The defensible field record you needed three projects ago, finally available without any extra typing.
BUILD 03
Reads your original scope letter against the spec, the GC's contract, and any directives that came after. When a back-charge lands, you have a clean answer on whether the work was actually yours.
// What subs say after the build
"We used to lose 60-70% of back-charge fights because the documentation just wasn't there. Now the file is built as we go. We've successfully pushed back on three back-charges this quarter that we would have eaten last year."
// Free, real, no obligation
Pick one open back-charge or disputed scope item — your scope letter, the GC's claim, and any relevant emails. We'll run it through the same system we'd build for you and send back a draft response pack plus a short walkthrough, usually within 24 hours.