{
  "namespace": "dev.legacyrail/ebrotech-catalog",
  "capabilities_ref": "https://ebrotech.net/.well-known/capabilities.json",
  "catalog_ref": "https://ebrotech.net/api/software.json",
  "slug": "rib-itwo",
  "name": "RIB iTWO",
  "vertical": "Construction / Bauunternehmen (DE/AT)",
  "url": "https://ebrotech.net/es/integraciones/rib-itwo/",
  "official_site": null,
  "countries": [],
  "languages": [],
  "connection": "export",
  "connection_note": "RIB iTWO does not expose an open public API for third parties. This is exactly where most agencies stop. We bridge it honestly through GAEB, the standard German construction data-exchange format that iTWO already reads and writes (D81/D83/D84 files). We parse the export, trigger the AI workflow, and feed structured data back via GAEB. No invented API, no migration. We confirm your file formats in discovery.",
  "what_we_automate": [
    "Bridge via the GAEB files (D81/D83/D84 and similar) iTWO imports and exports",
    "AI workflows triggered by each new GAEB export",
    "Automatic tender follow-up and client chasing on top of it",
    "Voice AI answering calls while iTWO stays untouched"
  ],
  "answer_first": "EBROTECH connects AI to RIB iTWO without migrating: iTWO has no open public API, so where most agencies tell you to switch, we bridge it honestly through GAEB, the standard German construction data-exchange format (D81/D83/D84) iTWO already reads and writes. iTWO stays exactly as it is, and the AI runs on top of the files it exports.",
  "when_not_to_use": "If your tool is a modern construction platform with a real API (such as Procore), see that profile, since a direct API link is simpler there. This profile is for German/Austrian construction software bridged via GAEB.",
  "alternatives": [
    {
      "name": "GAEB construction software",
      "slug": "software-construccion-gaeb",
      "reason": "Generic GAEB bridge for other German construction tools without an API.",
      "url": "https://ebrotech.net/api/software/software-construccion-gaeb.json"
    },
    {
      "name": "Procore",
      "slug": "procore",
      "reason": "If you also run a modern platform with an open REST API.",
      "url": "https://ebrotech.net/api/software/procore.json"
    },
    {
      "name": "Buildertrend",
      "slug": "buildertrend",
      "reason": "Residential construction software for US/CA builders.",
      "url": "https://ebrotech.net/api/software/buildertrend.json"
    }
  ],
  "how_to_connect": [
    {
      "name": "15-minute discovery",
      "text": "We confirm your GAEB file formats (D81/D83/D84) and which tender and chasing workflows to trigger first."
    },
    {
      "name": "Connect the connector",
      "text": "We bridge iTWO via GAEB file export: we parse the export, trigger the AI workflow and feed structured data back, no API and no migration."
    },
    {
      "name": "Automations live",
      "text": "Tender follow-up, client chasing and voice AI run by themselves on top, driven by each new GAEB export, iTWO untouched."
    }
  ],
  "published": false,
  "clients_live": 0,
  "request_quote": "https://ebrotech.net/es/contacto/",
  "book_discovery": "https://ebrotech.net/es/discovery/",
  "note": "EBROTECH connects AI on top of these systems without migrating data. clients_live:0 = no external paying clients on any connector yet (honest state 2026-07-03). The exact connection path (API, export, or local agent) is confirmed during the 15-min discovery call — no invented API status. Catalog: 203 connector specs/scaffolds (9 live-gated + 154 mock-ready + 40 scaffold); 0 tested in production."
}