We built Pikorua Security after a missing CG 20 37 cost a contractor its tender.

In 2024, Ananya Rao was managing subcontractor risk transfer for a large US general contractor. A water intrusion claim surfaced fourteen months after a roofing subcontractor finished its scope. The contractor tendered the claim to the roofer's carrier as an additional insured. The carrier denied it.

The certificate on file had the additional insured box checked and had been marked compliant in a spreadsheet. The endorsement behind it was a CG 20 10 in the 04 13 edition, which covers only ongoing operations. Nobody had asked for, or checked for, the CG 20 37 that would have extended coverage to completed work. The contractor's own policy and self-insured retention paid the defense.

It was the third denial like it in two years, on different projects with different trades. Each time the paperwork looked fine at the front page. Ananya teamed up with Siddharth Menon, who had spent years building document AI for scanned insurance and financial forms, and in 2025 they started building the platform with a narrow thesis:

• A certificate confers no rights. The ACORD 25 says so in its own header. Verification has to reach the endorsement pages and their edition dates.
• Most chasing is a communication problem. The project manager, the subcontractor and its broker usually want the same outcome. A precise notice with the missing form number and an upload link resolves most deficiencies without a phone call.
• Compliance only counts if it is enforced. A flag that does not reach the payment step in Procore or Yardi, or the badge reader at the gate, is a note in a file.

Today Pikorua Security is built by a team of risk engineers and software engineers who sit together in Delhi and work with US customers every week. Our risk engineering group maintains the edition rules for every form we check, and publishes the reasoning in the free ISO Endorsement Library.