The seven stages
behind every project.

A serious project begins with a serious conversation. We meet — at our Lachit Nagar office, at your site, or by video — and we listen first. The questions we ask early are the ones that decide everything afterwards: who will use the building, when, in what mood, against what brief from your architect, against what operational reality your facilities team will be expected to maintain.

We do not present a slide deck on the first call. We take notes. By the end of the meeting we will have a working sense of the brief, the budget envelope, the architectural constraints, the timeline, and whether what you are asking for is actually what you need.

From the first conversation, we write a one-document brief: scope, constraints, success criteria, risks, exclusions and the budget envelope you have agreed. The document goes to you for review and amendment. It sits underneath every subsequent decision and protects both of us from the slow drift that turns reasonable projects into unreasonable ones.

If the brief is clear, the work that follows is fast. If the brief is unclear, we will say so before we sign anything. We will not chase a budget against a moving target.

Design is where the project earns its premium. We produce a complete engineering pack — architectural-coordination drawings, single-line diagrams, panel and rack layouts, cable schedules, controller programming pseudo-code, acoustic and lighting calculations, BMS points lists, surveillance and storage calculations, written cause-and-effect matrices for life-safety. We attend the architect's coordination meetings as a discipline lead, not a vendor.

Every system is designed to the longest meeting, the largest event, the loudest film, the worst-case fire — and then tuned to feel effortless against that ceiling for everyday use. We design for the building as it will exist in year three, not on launch day.

We work across forty-plus manufacturer ecosystems selected by project fit, availability and client requirements. Procurement runs through our central desk in Guwahati; international shipments are routed through Jebel Ali (Dubai) customs into the destination market. We coordinate factory lead times, cross-border customs and last-mile freight against the architect's commissioning calendar so the build never stops waiting on us.

Brand selection follows the project, never the other way round. Our compensation is unaffected by which brand we recommend. Where two brands are equally suitable, we will say so and let you choose; where one is decisively right, we will recommend it and explain why, in writing.

Installation is staged against your civil contractor's calendar. Our cable-pull engineers, panel-build technicians, network technicians and AV riggers work to a published shop-drawing schedule, with site supervision by a named project lead who is on-site daily during active phases and whose number you have. We label, document and photograph every installation against the as-built drawing pack — the document that will protect your maintenance team five years from now when somebody needs to find a specific termination.

Commissioning is where the system is born. We test against a written test plan with documented pass criteria for every device, every cause-and-effect link, every interlock, every redundancy path. We calibrate cinema rooms with measurement microphones, balance audio chains to reference, run live fire-cause-and-effect drills, and stress-test the network against year-three load. The commissioning report is signed by our project lead and your representative; it is the document you will hold us to.

Handover is not a relief; it is a transition. We deliver a documentation pack — as-built drawings, panel and rack labelling schedules, controller configuration files, calibration reports, software-licence registers, AMC enrolment and an operations manual written for the people who will actually use the system. We train your team on-site, with follow-up sessions scheduled in the first quarter.

Every install we hand over is enrolled, by default, into a documented support programme. Calendars for preventive checks. Response targets in writing. Spares held in our Lachit Nagar office for active deployments. Firmware-and-config baselines stored offline so we can recover any controller from a clean slate. After handover is when integration begins.