Inconvo vs Versatile

There is no shared feature surface here. Versatile's capabilities are all physical-world: passive capture from tower and crawler cranes with no crew workflow change, a Control Center dashboard for pace/progress/problems, piece matching that verifies steel deliveries against the erection plan, a 4D Viewer for installation progress over time, objective utilization and overtime analytics, and a mobile app for on-site viewing. The differentiator is that hardware lives on the crane, so data compounds across multi-month jobs without anyone logging anything. Inconvo's capabilities are all software-infrastructure: a semantic layer with computed columns, table prompts and agent rules; query validation before execution; multi-tenancy with tenant scoping and row-level security; per-user context scoping; conversation state for multi-turn follow-ups; response streaming; agent traces and a usage-analytics dashboard; a feedback API; and MCP server deployment with OAuth. It integrates with PostgreSQL, MySQL, SQL Server, Redshift, BigQuery, Supabase, Assistant-UI and the Vercel AI SDK. One captures steel going up; the other answers English questions against a database safely. The only abstract overlap is "turning messy operational reality into trackable data" — the buyers, deployment model and day-to-day use are entirely disjoint.

The two pricing models aren't just different numbers — they're different economics. Versatile is contact-sales: you're buying installed hardware plus software, which means per-crane setup cost, installation, and an ROI calculation that only makes sense if crane work is your binding constraint. Its own not-for list flags that short one-off crane jobs won't pay back the hardware setup — so the effective price is high-but-amortized over multi-month erection projects. Inconvo costs nothing to license: it's an open-source codebase you self-host and fork. That shifts the cost from a line item to engineering time — someone on staff has to own the fork, and the docs route you through npx inconvo@latest dev to run it locally. The pricing tradeoff is therefore concrete: Versatile = capex plus a vendor relationship; Inconvo = zero license fee plus a maintainer you must supply. The July 2026 news that Inconvo is joining Attio reinforces this — the open-source codebase stays available, but you're buying into a project whose commercial sponsor just changed hands, so budget for the possibility that you maintain the fork yourself long-term.