+24 Commodity PressureMarketing leans on generic 'AI' and 'text-to-schedule' language that reads easily copyable into a model feature, though bespoke integrations and controls push back a bit.
'AI-powered', 'AI Scheduling Assistant', 'Text-to-schedule' repeated across the siteGeneric marketing slogans: 'The future of software is custom'High-level claims with no public pricing or full case study detail
+24 Model DependencySite explicitly lists third‑party model providers (AWS Bedrock, Google Vertex, OPC) and markets copilot-style features; per-customer model claims reduce but don't eliminate reliance.
Explicit listing of model providers: AWS Bedrock, Google Vertex, OPCRepeated copilot-style claims: 'AI Scheduling Assistant', 'text-to-schedule''No Cross-Customer Model Training' indicates per-customer model posture while still using external providers
-12 Workflow OwnershipScheduling is framed as the single source of truth with real-time replanning, collaboration and export/integration into established delivery workflows — a central, repeatable operational touchpoint.
Real-time disruption alerts and instant replanningSchedule collaboration / single source of truth across teamsCustom progress update workflows and export to P6
-4 Distribution EmbeddednessDistribution appears enterprise and sales‑led (book a call), with channel hooks via Primavera and SSO, but no broad platform or marketplace ubiquity shown.
SSO through Microsoft Entra ID (Azure AD)Oracle Primavera Cloud permissions / P6 exportSales-led flow ('Book a call') and single-tenant deployment options
-8 Integration DepthConcrete, technical integrations (P6 permissions, CAD time-space links, custom in-house system connectors) indicate deep product entanglement with clients' systems of record.
Oracle Primavera permissions / P6 exportCAD model linking to schedule (time-space visualization)Custom integrations with in-house contract & delivery management software
-12 Enterprise TrustStrong enterprise security and deployment signals: ISO 27001, Cyber Essentials Plus, single‑tenant VPCs, regional data residency and audit logging support procurement for regulated customers.
ISO 27001 certifiedCyber Essentials PlusSingle-tenant VPC deployments · Data residency options · Audit logging
-12 Switching CostData gravity and collaboration lock-in look real: centralized schedule, parametric templates, integration with Primavera and bespoke control towers make migration painful.
Single source of truth across teams · Schedule collaborationParametric template instantiation and portfolio-level templatesIntegrations attaching to Primavera and in-house delivery systems
-3 Monetization MaturityEnterprise sales and named industry customers signal real revenue motion, but hidden pricing and a consultative 'book a call' funnel limit transparency and scale signals.
Trusted by industry leaders · Tier 1 US Energy Utility · Leading Netherlands Specialist ContractorPricing hidden; sales-led onboardingCase examples and founders' domain experience cited
+4 Category BaselineVertical workflow products start safer than generic assistants.
vertical workflow
-4 Relative PlacementNet safer: substantive enterprise integrations, compliance, single‑tenant deployments and real workflow lock‑in outweigh marketing/model wrapper risk.
Deep technical integrations (Oracle Primavera P6 export/permissions; CAD time‑space linking) suggest high product entanglement and migration pain.Enterprise trust signals (ISO 27001, Cyber Essentials Plus, single‑tenant VPCs, data residency, audit logging) enable procurement in regulated buyers.'No Cross‑Customer Model Training' plus explicit per‑customer model posture and named providers (Bedrock, Vertex) reduce pure commoditized model risk.