Before any contract is signed, procurement teams and plant managers want to know how an intranet project will affect their daily operations. The questions are rarely about features. They are about downtime, data boundaries, and who is responsible when something breaks at 2 a.m. during a shift change.
The most common question is about integration with existing systems. Most multinational corporations run SAP, custom ERP modules, and legacy databases that have been patched for a decade. Clients want to know whether the intranet will sit alongside these systems or replace parts of them. Our answer is always the same: the intranet is a layer, not a replacement. It pulls data from existing sources and presents it in a unified interface, so the underlying systems stay untouched.
Another frequent question concerns access control. In heavy industry, not everyone should see everything. A plant operator in Kedah does not need visibility into procurement contracts for a facility in another country. Clients ask how we handle role-based permissions across multiple sites. We explain that identity is federated through their existing directory, and each site gets its own policy boundary. This is not a theoretical design; it is how we structure every deployment.
Security audits come up early in the conversation. Large corporations have compliance teams that review every vendor. They ask about encryption standards, audit logs, and whether the platform can be deployed on-premises if needed. We walk through our architecture: encrypted traffic end to end, immutable audit trails, and a deployment model that works both in the cloud and behind their firewall. The goal is to remove uncertainty, not to add more slides.
Finally, clients ask about training. A corporate intranet is only useful if people actually use it. Field operators are not going to read a 40-page manual. We design interfaces that work on tablets and rugged devices, with dark mode and high-contrast accents for low-light environments. Training is built into the rollout, not bolted on afterward. That is the difference between a portal that gets adopted and one that gets ignored.
If you are preparing for a first conversation about your own intranet, it helps to know what to bring and what to expect. We wrote a short guide on that here: What to Prepare Before a First Consultation. And if you want to hear how other clients describe the process, the reviews page has direct quotes from the people we have worked with.