{
  "namespace": "dev.legacyrail/ebrotech-catalog",
  "capabilities_ref": "https://ebrotech.net/.well-known/capabilities.json",
  "catalog_ref": "https://ebrotech.net/api/software.json",
  "slug": "software-construccion-gaeb",
  "name": "GAEB construction software (DE/AT)",
  "vertical": "Construction / Bauunternehmen (DE/AT)",
  "url": "https://ebrotech.net/es/integraciones/software-construccion-gaeb/",
  "official_site": null,
  "countries": [],
  "languages": [],
  "connection": "export",
  "connection_note": "Most German construction software exposes no 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 (D81/D83/D84 files) these tools already import and export. We parse the export, trigger the AI workflow, and feed data back via GAEB. No invented API, no migration. We confirm your specific tool and file formats in discovery.",
  "what_we_automate": [
    "Bridge via the GAEB files (D81/D83/D84 and similar) your software exchanges",
    "AI workflows triggered by each new GAEB export",
    "Automatic tender follow-up and client chasing on top of it",
    "Voice AI answering calls while your software stays untouched"
  ],
  "answer_first": "EBROTECH connects AI to German construction software without migrating: most of it has no open public API, so where other agencies give up, we bridge it through GAEB, the standard data-exchange format (D81/D83/D84) these tools already read and write. Your software stays as it is, and the AI runs on top of the files it exchanges.",
  "when_not_to_use": "If your specific tool is RIB iTWO, see that dedicated profile. And if you run a modern construction platform with a real API such as Procore, a direct API link is simpler there.",
  "alternatives": [
    {
      "name": "RIB iTWO",
      "slug": "rib-itwo",
      "reason": "The dedicated profile for RIB iTWO, bridged via GAEB.",
      "url": "https://ebrotech.net/api/software/rib-itwo.json"
    },
    {
      "name": "Procore",
      "slug": "procore",
      "reason": "If you 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 specific construction tool and its GAEB file formats, and which tender and chasing workflows to trigger first."
    },
    {
      "name": "Connect the connector",
      "text": "We bridge your software via GAEB file export: we parse the export, trigger the AI workflow and feed 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, your software 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."
}