/ Method
What architects should ask their integrator before specifying anything
Quick answer
Before specifying an integrator, architects should test three things in a thirty-minute call: who programmes the controllers (in-house, or out-sourced), what the cabling pathway looks like before plaster, and what the AMC structure actually contains. The answers separate an integrator who will respect the architecture six months later from one who is selling a transaction.
We meet a lot of architects after the integrator has already been chosen by the client, and the first conversation is often a stress-test of choices made before the architect was in the room. A short pre-engagement briefing — a thirty-minute call before signature — usually saves a substantial amount of friction later. Below are the questions we recommend the architect ask, drawn from the patterns we have observed over fifteen years.
First: who programmes the controllers? An integrator who programmes Rako, Fibaro and KNX in-house can adjust the system in a morning when you ask for a change six months later. An integrator who outsources programming to a sub-contractor will frequently discover that the original sub-contractor is unavailable, the file is unmodifiable without their original toolchain, and a small change becomes a forensic exercise.
Second: what does the cabling pathway look like before plaster? A good integrator opens this conversation at the architectural drawing stage and is happy to share marked-up plans. An integrator who waits until the carcass stage will be retrofitting cable in places the architecture did not invite, and the install will look retrofit even if the hardware is reference-grade.
Third: what is the AMC structure? Is it written down? Is there a calendar of preventive checks? Are spares held against this specific deployment, or does the integrator hold a generic spares pool? The answers to these questions decide whether the system stays a quietly working asset or becomes a recurring maintenance file that someone has to manage.
/ Frequently asked
Quick answers from the practice.
- How early should the integrator be engaged on a project?
- At schematic-design stage — well before structural drawings are stamped. The integrator's cabling pathway, panel locations, riser routing and acoustic envelope are architectural decisions that cost almost nothing at design and cost five to ten times more at carcass stage.
- What documentation should the integrator deliver at handover?
- Calibration report (RP-22 for cinema, channel-test for cabling, commissioning report for fire-alarm cause-and-effect), as-built drawings, labelled patch schedule, operations manual written for the building's actual users, configuration baselines retained offline, and an AMC programme calendar.
- How do I assess an integrator's programming maturity?
- Ask for the names of the team members who programme Rako / KNX / Crestron / AMX in-house and the AVIXA / CEDIA / vendor-specific certifications they hold. Ask to see a recent .pro file or .esd file from a comparable project (redacted of customer detail). Outsourced programming surfaces in this question.
- What separates a turnkey integrator from a point-supply contractor?
- Single-contract delivery, single accountability for the seams between disciplines (automation / AV / ELV / IT / BMS), in-house programming and commissioning labour, and an AMC programme that survives the original sub-contractors moving on. Point-supply contractors typically optimise for low capital cost at the expense of lifecycle outcomes.
- Can TechnoGuru act as the architect's integrator-consultant during specification?
- Yes — we engage as pre-bid technical advisor on projects where the engagement is structured to avoid a conflict of interest at bid stage. The advisory work is a billable service in its own right; the protection it gives the architect's procurement is significant.
/ What to do next
Three next steps for architects
- Read our seven-stage delivery method →Brief through 36-month AMC — what every stage delivers and what the architect signs off.
- Run the project phase visualiser →Realistic week-by-week Gantt across our seven stages.
- Send a project brief to the studio →Six structured questions; written response within two working days from a project lead.
/ Services this article informs
Read the discipline pages.
/ Reference work
Projects where this engineering shows up.
/ Discuss your project
If this article matches a brief you are working on, the next step is a thirty-minute call with a project lead.
We do not run sales pipelines. The first reply comes from a project lead, within two working days, and it goes straight to the engineering question rather than a brochure.