Product Positioning Key Focus Customer Needs Typical Scenarios Sales Principles Integration Drive Value Proposition Objection Handling Partner CRM
● SolutionMall Sales Training Guide

Computer & Server
Sales Mastery
Training Guide

Equip your sales team and channel partners with the knowledge, language, and strategy to confidently position, pitch, and close computer and server solution deals across every industry vertical.

🛒 Browse Products 📋 Submit Request
5
Product Tiers
7
Sales Scenarios
6
Core Principles
10
Objection Scripts
8
Core Messages
5
Languages
Section 1 Product Positioning

What Is a Universal Gateway — And Why It Matters

The first thing a salesperson must communicate is not "what device it is" but "what problem it solves in the system." A universal gateway is the connectivity hub between field devices, control systems, platform systems, and business applications.

Gateway Architecture

Not a Simple Relay — It's the System Access Layer

Customers are not buying a "protocol converter box." They are acquiring the capability to truly connect, deliver, and sustain long-term system operation.

Not a Supporting Role — It's a Critical Node

Whether devices can be unified, data continuously uploaded, alerts closed-loop, and platforms linked — these are often determined by the gateway, not the front-end devices.

Value Is in Choosing the Right One

Many projects already have gateways — but the wrong ones. The result: initially seems to work, but later becomes unstable, hard to expand, and costly to maintain.

Engineering Product First, Commodity Second

Customers who evaluate only by unit price often underestimate the gateway's decisive impact on system delivery, stable operation, and future scalability.

Section 2 Key Focus

Product Classification — Build Your Product Map

Don't memorize spec sheets. Build a clear product map and match products to customer scenarios and project roles — not model numbers.

Gateway Product Classification
Frontend Access Gateway

Category 1: Frontend Access Gateways

Solves the fundamental question: "How do field devices connect to the system?" This is the most common entry point for most projects and the broadest market segment.

Multi-port Serial Industrial Acquisition Gateway
Modbus Protocol Gateway (RTU/TCP)
BACnet Gateway (for HVAC, Building Systems)
KNX / OPC UA Gateway
CAN Bus Gateway
I/O Acquisition Gateway
Wireless Remote Gateway

Category 2: Wireless Remote Access Gateways

Solves the challenge: "What if there's no stable wired network on site?" Common in scattered sites, unmanned stations, and retrofit projects where value is immediately clear to customers.

4G Industrial Gateway with Remote Management
5G High-Bandwidth Gateway
LoRaWAN Gateway for Long-Range IoT
NB-IoT Access Gateway
Wi-Fi / Ethernet Dual-Mode Gateway
Edge Computing Gateway

Category 3: Edge Computing & Linkage Gateways

Solves the challenge: "The site doesn't just need data collection — it needs local judgment, buffering, and linkage." More complex but higher value. The key to upgrading from "selling hardware" to "selling system capability."

Edge Computing Gateway with Local Processing
Local Linkage Control Gateway
Data Buffer & Retransmission Gateway
Edge AI Fusion Gateway
Platform Integration Gateway

Category 4: Platform Integration Gateways

Solves the challenge: "Once front-end devices are connected, how do we integrate with BMS, EMS, IoT platforms, and business systems?" Best for solution-type expressions rather than pure price competition.

MQTT Cloud Access Gateway
API Interface Gateway
Database Write Gateway
BMS / EMS Platform Integration Gateway
Video-IoT Fusion Gateway
Security Gateway

Category 5: Security & High-Reliability Gateways

Solves the challenge: "Can the system run stably long-term? Can it connect securely?" In hospitals, energy storage, data centers, and critical facilities, these products demonstrate the highest professional value.

Dual-Network Isolation Security Gateway
High-Reliability Redundant Gateway
VPN Secure Remote Maintenance Gateway
RTU Remote Terminal Gateway
Installation Environment Gateway

Category 6: Installation Environment Gateways

Solves the challenge: "Can this gateway actually be deployed in the project site and run long-term?" The right form factor is essential for real-world deployment success.

DIN-Rail Industrial Gateway (for Control Cabinets)
Outdoor Weatherproof Gateway (IP65+)
Rack-Mount Aggregation Gateway
Sales Focus

What to Prioritize — Don't Spread Effort Equally

The products that create the most project value and generate the largest sales opportunity are not the cheapest basic connectors. Focus your energy here.

01

Industrial Protocol Conversion & Multi-Protocol Gateways

The most common, stable, and broadly demanded category. Factories, buildings, energy, water, and retrofit projects all need this. The best entry point for sales conversations.

02

4G/5G Remote Gateways & RTU Remote Access

Ideal for scattered sites, unmanned stations, and outdoor projects. Value is clear and tangible — customers immediately understand "remote maintenance cost savings."

03

Edge Computing / Edge Linkage Gateways

More complex but higher value. Essential for local linkage, offline buffering, and alert loop-closure. The key to upgrading from hardware sales to system capability sales.

04

Platform Integration & Cloud-Edge Gateways

When customers already have a platform or need BMS/EMS/IoT integration, these products enable solution-type positioning rather than pure price competition.

05

Security & High-Reliability Gateways

In hospitals, energy storage, data centers, and critical facilities — these products demonstrate professional capability and project value at the highest level.

💡

Sales Memory Principle

Categorize by role first, then by type: Access type? Remote type? Edge type? Platform type? Security type? Once the customer describes their scenario, you can instantly map the right product.

Section 3 Customer Needs

Who Buys & Why They Buy

Customers don't buy gateways because they "want a gateway." They buy because real problems have already appeared in their projects.

Customer Consultation
🛠

System Integrators

Weak-current integrators, M&E contractors, automation integrators, building automation integrators, energy management integrators. They care most about compatibility, delivery efficiency, project risk, and long-term maintenance difficulty.

📄

Equipment Operators & O&M Teams

Campus O&M, property management, energy station operators, water utility operators, chain store maintenance teams. They prioritize remote management, stable operation, alert response, and maintenance efficiency.

🏢

End-User Owners

Factory owners, campus owners, commercial complexes, hospitals, universities, transportation facility managers. They may not understand protocol details but care deeply about long-term stability and future expandability.

🏭

Equipment Manufacturers & OEM Customers

They embed gateways as part of their complete product offering — for remote after-sales service, remote maintenance, and platform connectivity. Gateway becomes a key differentiator in their product line.

Key Industries & Project Types

Manufacturing Smart Buildings Public Infrastructure Industrial Parks Energy Storage Solar / Photovoltaic Water Utilities Transportation Municipal Services Cold Chain Logistics Warehousing Data Centers
Section 4 Typical Scenarios

What to Emphasize in Different Scenarios

Never pitch a gateway without context. The same product delivers entirely different value in different scenarios. Wrong scenario = wrong pitch = lost deal.

🏭

Factory & Industrial Equipment Networking

▼
Factory Scene
✅
Multi-protocol, multi-brand compatibility
✅
Experience with PLCs, meters, drives, workstation devices
✅
Edge buffering and data continuity
✅
Integration with SCADA, MES, industrial platforms
✅
Minimizing downtime and rework in retrofit projects
💡
Key insight: Customers don't fear "slightly more expensive" — they fear "can't connect," "unstable connection," and "chaos when we modify the site."
🏠

Buildings, Hospitals & Commercial Complexes

▼
Building Scene
✅
Multi-subsystem unified access
✅
HVAC, energy, lighting, access control integration
✅
BMS / EMS platform integration capability
✅
Long-term O&M and expansion convenience
✅
Delivery stability during multi-discipline commissioning
💡
Key pitch: "It can truly integrate the building's multiple systems — not just each system running in isolation."
📍

Scattered Sites: Pump Stations, Water, Roads, Solar

▼
Remote Site Scene
✅
4G/5G remote access capability
✅
Offline buffering and data retransmission
✅
Remote alerts and remote maintenance
✅
Outdoor protection, lightning resistance, wide temperature range
✅
Reducing on-site visits and lowering O&M costs
💡
Key insight: Customers care most about: "Sites are remote, environments are harsh — can we know quickly when something goes wrong? Can we reduce on-site trips?"
🔒

High-Reliability: Energy Storage, Data Centers, Hospitals

▼
Data Center Scene
✅
High-reliability access and redundancy
✅
Security isolation and access control
✅
Log retention and traceability
✅
Local linkage stability under abnormal conditions
💡
Critical reminder: "You're not buying a communication component — you're buying a risk control node." Downtime costs far exceed device price differences.
🔄

Legacy System Upgrade & Retrofit Projects

▼
Legacy Upgrade Scene
✅
Backward compatibility with existing equipment
✅
Dual-system parallel operation during transition
✅
Minimizing original system modifications
✅
Reducing downtime and retrofit risk
✅
Maximizing utilization of existing assets
💡
Key pitch: Not "how many new features" but "how to upgrade smoothly, how to minimize changes to the existing system."
☁

Cloud Platforms, Enterprise Groups & Multi-Site Projects

▼
Cloud Platform Scene
✅
Unified access standards across all sites
✅
Remote batch management capability
✅
Unified device registration, upgrade, log, and config management
✅
Future scalability and platform openness
💡
Key pitch: Customers are not just buying a gateway — they're buying "a sustainable, scalable access architecture for the future."
Section 5 Integration Drive

Product Ecosystem & Cross-Selling Strategy

Universal gateways rarely sell in isolation. They are connector products, bridge products, and system products — both driving and being driven by the broader product ecosystem.

Product Ecosystem
🔌

Sensors, Meters & Instruments

The fundamental need in most projects is "data collection." Gateways naturally appear alongside front-end devices. When customers buy sensors, gateways follow.

📶

Industrial Switches & Wireless Devices

Gateways depend on reliable network links. Especially in remote sites and outdoor projects, communication accessories are critical companions.

⚡

I/O Modules & Edge Controllers

Many projects don't just collect data — they need linkage and control. I/O modules and relay output modules extend gateway capability.

🔋

Power Supplies, UPS & Surge Protection

Gateways installed in field environments depend on power quality and protection. Power accessories directly determine operational stability.

🛠

Enclosures, Cabinets & DIN Rail Hardware

Real project delivery means placing gateways in actual environments for long-term operation — not just on a desk. Installation hardware completes the solution.

☁

Platform Systems & Software

BMS, EMS, IoT platforms, SCADA, O&M platforms, alert systems, databases, and business systems. Without platform integration, much of the gateway's value remains unrealized.

The Gateway's Role in the Project

🎯

In Small Projects

The gateway can be the main product — e.g., a remote site needing data collection and transmission only.

🔗

In Medium Projects

The gateway is a critical supporting product — not the only product, but the project can't run without it.

🌏

In Solution Projects

The gateway is the connectivity hub — connecting the entire solution in cloud-edge coordination, campus linkage, energy monitoring, and platform integration.

Section 6 Value Proposition

Core Values & Key Messages to Repeat

These are your high-frequency talking points — use them in presentations, proposals, and every customer conversation.

🔌

Unified Access

Heterogeneous devices from different brands, protocols, and eras all enter the same unified system — no more islands of data.

📈

Stable Transmission

Data is not "sometimes visible" — it is continuously available, reliably transmitted, and always accessible when needed.

⚡

Edge Coordination

Even during network outages or abnormal conditions, the site remains controllable through local edge intelligence and autonomous operation.

🔗

Platform Integration

Devices, platforms, and business applications form a closed loop — data flows seamlessly from field to cloud to business decisions.

📱

Remote Management

Projects upgrade from "deliverable" to "sustainably maintainable" — remote visibility, remote diagnostics, remote control.

🚀

Open Scalability

Today's access capability won't become tomorrow's retrofit obstacle — open standards, flexible expansion, future-proof architecture.

💡 Core Viewpoints to Repeat in Every Conversation

A universal gateway is not a single networking device — it is the system access layer.
Customers are not buying protocol conversion — they are buying system deliverability.
Gateway value is not realized on purchase day — it's realized across the entire project lifecycle.
The more devices, protocols, and sites involved, the more a professional gateway system is needed.
Wrong gateway selection appears to save money upfront but costs far more in delivery and maintenance.
In high-reliability scenarios, downtime costs typically far exceed device price differences.
Never pitch a gateway without context — wrong matching directly impacts delivery and long-term value.
Section 7 Sales Principles

Sales Principles & Boundaries

What to always do — and what to never do when selling universal gateway products.

✅ Core Principles to Uphold

DO

Professional products are not sold as simple single items. True deal logic is a comprehensive solution to access + O&M + platform + delivery challenges.

DO

Always connect products to specific scenarios and application requirements. The same gateway has completely different requirements in factories, buildings, pump stations, energy storage, and cold chain.

DO

Look beyond purchase price to long-term cost and risk. One fewer site visit, one fewer downtime, one fewer system rework often exceeds the initial price difference.

DO

Consider the complete delivery and closed-loop implementation. Don't just ensure "devices can ship" — assess whether the project can achieve stable access, commissioning, and closed-loop delivery.

DO

In high-reliability scenarios, guide customers from "unit price comparison" to "system risk comparison." Security, stability, and continuous operation value often exceeds the apparent price difference.

❌ Boundaries You Must Know

DON'T

Don't push overly complex projects beyond the team's delivery capability. If a project involves extensive custom protocols or complex control logic the team can't handle, never over-promise to win the deal.

DON'T

Don't prioritize ultra-low-end, price-only products with no value space. If customers only want the cheapest "converter box" and completely disregard compatibility, stability, O&M, and platform capability, this is not a priority target.

DON'T

Don't focus on directions that don't align with company positioning or can't form complete delivery. Don't just look for opportunities to sell one gateway — assess whether it can form follow-on packages, solution extensions, and brand value.

DON'T

Don't make arbitrary commitments on high-risk control boundaries. Remote control permissions, energy storage linkage logic, critical device start/stop, hospital continuous system control — these must be confirmed by pre-sales or engineering teams.

DON'T

Don't let customers treat gateways as universal replacements for everything. Gateways solve access, conversion, edge processing, and management problems — they don't solve all field problems. Never pitch them as a "one-device-fixes-everything" solution.

Section 8 Objection Handling

Common Objections & How to Respond

Every objection is an opportunity to demonstrate expertise and build trust. Use these response frameworks to guide customers toward better decisions.

Sales Training
Q

"The price is too high. I just want something cheaper."

A

Don't argue about price — shift the conversation from "unit price" to "total cost." Remind customers: gateways are not one-time consumables. Post-deployment debugging, maintenance, site visits, downtime, and expansion issues often cost far more than the initial price difference.

Q

"I just want to buy the simplest single product."

A

Acknowledge the starting point, but help the customer understand that a single device is only part of the access solution. If the field devices, platform, network, installation environment, and O&M requirements aren't considered together, the single device may connect initially but fail in practice.

Q

"We just need it to connect — don't need anything complex."

A

Validate "connecting" as the first step, then explain that the real challenge is not day-one connectivity but stable long-term operation. Help customers anticipate: network cuts, power failures, abnormal recovery, remote maintenance, platform linkage, and future expansion.

Q

"We already have a supplier."

A

Don't directly challenge the existing supplier. Enter from a complementary value angle — emphasize strengths in multi-protocol integration, remote site access, high-reliability scenarios, platform integration, or edge linkage. Position as filling gaps in the existing system, not replacing it entirely.

Q

"We used simple converters before and they worked fine."

A

Affirm that they "worked" — but distinguish between "worked" and "suitable for long-term projects." Simple converters handle basic connections, but for multi-protocol, multi-site, remote maintenance, buffer retransmission, platform coordination, and security control, professional gateways show their true value.

Q

"Our project budget is limited."

A

Don't push the full high-end configuration. Help customers identify which capabilities are essential to preserve and which can be phased. Emphasize: with limited budgets, it's even more important to prioritize capabilities directly related to stable operation, data continuity, and future expandability.

Q

"We don't prioritize remote maintenance or security right now."

A

Don't tell customers they're wrong. Remind them: many projects don't prioritize these initially because the scale is small and problems haven't surfaced. Once sites multiply, time passes, and systems grow complex, remote maintenance and security rapidly become critical requirements — not optional extras.

Q

"It's just a small project — we don't need anything this professional."

A

Acknowledge that not every small project needs the most complex solution — but remind customers that small doesn't mean basic correctness can be ignored. Even small projects need protocol matching, environmental adaptation, stable power, and basic maintainability. Professional means avoiding obvious mistakes from the start.