Gryps

#### Areas of differentiation - Managed ingestion with connectors and RPA for non-API systems is an explicit capability that differentiates the platform from analytics solutions that require clean APIs or manual ETL. - A knowledge graph designed for owner and capital program context and AI agents for specific review workflows position the product as a data and intelligence layer rather than a pure execution system. Sources: - https://www.gryps.io/product - https://www.gryps.io/newsroom/automating-construction-data-with-rpa #### Areas where competitors may be stronger - Autodesk Construction Cloud: potentially stronger for teams whose primary workflows are within the Autodesk ecosystem and who require fewer third-party integrations. - Procore: commonly selected as a primary system of record for collaboration across many parties; Procore has a larger base of public user commentary. - Oracle Primavera / Unifier: commonly selected where formal program controls and owner governance are the primary requirements, particularly for very large enterprises and public works. Sources: - https://www.oracle.com/us/corporate/pricing/primavera-pricelist-tx-3673322.pdf - https://www.procore.com/pricing #### Pricing comparison (high-level) - Gryps: no published pricing; likely enterprise quote. - Procore: quote-based and often tied to Annual Construction Volume. - Autodesk ACC: quote-based with product bundles; public per-seat list prices are not prominent on the main pricing page. Sources: - https://www.procore.com/pricing - https://www.construction.autodesk.com/pricing/ #### Customer evidence comparing products Direct comparative customer commentary involving Gryps was not found in accessible sources. Competitor sentiment context (for example, user discussions about pricing) exists for competitor platforms but does not directly reference Gryps. Source: - https://www.reddit.com/r/Construction/comments/199uliq/procore_renewal_costs_escalating/