For RTI dealers & CEDIA integrators
Spec in. Macro out.
Roommacro removes the programmer handoff that was never yours.
You already know the room, sources, devices, and drivers —
turn the job sheet into a working .apex and finish in Integration Designer.
The gap between the job spec and an Integration Designer project is where time and margin die. Rough-in is done; trim-out waits on a programming pass you shouldn’t need for the shell. Roommacro closes that gap so the same dealer keeps the work — and the margin.
Rooms, sources, devices, remotes, and drivers — the same language you already use on site.
.apex
Get a project file generated for Integration Designer — macros scaffolded, placeholders where IR still belongs in ID.
Test, finish drivers, and trim out. Spec sheet in; working system path out — no separate programmer in the pipeline.
RTI dealers and CEDIA integrators who own the room: processors, remotes, sources, devices, drivers, and macros. If you write the brief and commission the system, Roommacro is the missing middle — not a different job.