CHITI STUDIO SYSTEMS v2.4
0%
Back to all work
NetQ Command
Product Design, UX Strategy, Interface Direction

NetQ Command — Infrastructure Monitoring Product

Translating technical monitoring into a product that both operators and business clients can understand

Product DesignUX StrategyDashboardSaaS
2026
Product Design

2

Interface Views

5

Persona Types

V3

Design Phase

Ops + Business

Stakeholders

The Problem

NetQ Command started from a familiar enterprise problem: the system could surface technical data, but it did not help different stakeholders understand what that data meant. Small and mid-sized IT service providers needed two things at the same time: a reliable command environment for operators working with infrastructure data, and a clearer way to explain service value to business clients who do not think in uptime graphs and latency spikes. The gap was not only visual. It was a product-framing problem. Technical metrics were visible, but business value was still invisible.

System Overview

We treated the product as a translation layer, not just a dashboard. The interface had to support raw system operations while also producing a second level of meaning for decision-makers. The resulting structure connects five layers: command and signal intake, validation and classification, execution and remediation, business translation, and reporting and client communication. This let the same underlying system serve both technical work and business storytelling without splitting into unrelated tools.

System architecture diagram
Key Challenges
01

Preserving technical credibility while simplifying the language for non-technical users

02

Designing feedback patterns that reduce command anxiety and execution mistakes

03

Showing business impact without making the product feel like a marketing layer detached from operations

04

Creating a system that could move between normal monitoring and incident response without losing clarity

Design Decisions

How We Solved It

01

Dual-view structure

We separated the product into a technical view and a business view. The technical layer stays close to operations, while the business layer reframes the same signals into outcomes such as risk, continuity, and value protected.

02

Smart Translation Engine

Instead of showing 'CPU Load: 45%', the business view displays 'Experience Risk: Low — your customer-facing services are running smoothly'. '12 Active Alerts' becomes '3 Business Risks — potential revenue impact if unaddressed: ₹45,000'. This mapping from technical metrics to business outcomes is powered by a configurable translation layer that adapts to each client's industry.

03

Immediate command feedback

The interaction model emphasizes validation, status visibility, and structured output. Instead of treating the interface like a passive console, it behaves like a guided command surface with clearer confirmation states.

04

Incident simulation

One key concept was a simulation mode that demonstrates how the system reacts under stress. A 'Loss Prevented' counter shows real-time revenue impact during demos, turning an abstract monitoring product into something easier to explain during sales conversations.

05

Client Management & Revenue Visibility

We added a dedicated client management dashboard with per-client health scores, monthly revenue tracking, and active risk monitoring. An ROI card prominently displays current revenue, average per-client value, and growth indicators — reinforcing the business value for the service provider themselves.

06

Industry-specific views

The product supports five client types — ISP Providers, IT Agencies, SaaS Companies, Hospitals, and Factories — each with specialized terminology and alert thresholds. This lets service providers speak the language of each client's industry without manual configuration.

Interface Screens

The Work

The screens below show the main interface directions: a dense operations dashboard, a translated business layer, and an incident state used to explain product value during demos.

Operations dashboard concept — Shows the dual-view architecture where operators see real-time signal intake and validation. Addresses command anxiety by making next action explicit.
Click to expand

Operations dashboard concept — Shows the dual-view architecture where operators see real-time signal intake and validation. Addresses command anxiety by making next action explicit.

Business impact layer concept — Translates technical signals into business outcomes (risk, continuity, value protected). Shows how the same system speaks to non-technical stakeholders.
Click to expand

Business impact layer concept — Translates technical signals into business outcomes (risk, continuity, value protected). Shows how the same system speaks to non-technical stakeholders.

Incident simulation concept — Demonstrates system behavior under stress for demos and onboarding. Helps sales teams explain product value without technical jargon.
Click to expand

Incident simulation concept — Demonstrates system behavior under stress for demos and onboarding. Helps sales teams explain product value without technical jargon.

Key Features

What We Delivered

Dual-view architecture — technical operations layer and business impact layer

Smart Translation Engine — maps technical metrics to business outcomes (e.g. 'CPU Load' → 'Experience Risk')

Immediate command feedback with validation and status visibility

Incident simulation with 'Loss Prevented' counter for demos and onboarding

Business-impact framing that translates raw events into customer outcomes

Client Management Dashboard with per-client health scores, revenue tracking, and active risks

ROI Visibility Card showing monthly revenue, active clients, and growth indicators

White-label deployment (NetQ → Partner Command) for MSP resale

Multi-client simulation mode for sales demonstrations

Smart Alerts with business impact context and suggested actions

Impact
01

Reframed the product from a technical utility into a stronger service platform story

02

Created a clearer relationship between infrastructure health and business impact

03

Reduced ambiguity in how operators read system state and next actions

04

Gave the product a more convincing narrative for client demos and white-label deployment

05

Enabled IT providers to switch from hourly billing to retainer models with visible ROI

06

Multi-client simulation turned abstract monitoring into a demonstrable sales tool

Reflection

This project reinforced that complex products are often communication problems before they are styling problems. The most useful design move was not adding more surface polish. It was structuring the interface so the same system could speak clearly to two very different audiences without becoming fragmented. The translation layer — mapping technical events to business outcomes — proved to be the highest-leverage feature, turning an operational tool into a revenue-generating platform.

Development Journal

Process & Progress

Foundation & Design System

Design Token Architecture

Created comprehensive design token system aligned with Chiti UDS v3.0.0: dark theme colors (Background, Surface1, Surface2), brand tokens (Primary Purple, Secondary Cyan), semantic tokens (Success, Info, Warning, Error), DataViz palette (WCAG AAA, color-blind safe), 8pt grid spacing, typography (Outfit for display, Inter for body, JetBrains Mono for code), motion tokens with duration and easing curves, and elevation tokens (shadow-sm through shadow-2xl).

Component Library & Motion System

Built a component library with Button (5 variants: cinematic, glass, saas, error, ghost), Card with loading states, Skeleton with reduced motion support, Badge/StatusBadge, and Input/SearchInput. Implemented staggered entrance animations with Framer Motion, haptic feedback using Web Audio API, and full accessibility compliance with focus-visible rings and ARIA labels.

Core Architecture & Views

Dual-View Architecture

Developed two separate interface modes — a Technical View for operators with real-time signal intake, validation, and execution, and a Business View that translates the same infrastructure data into business outcomes (risk, continuity, value protected). The toggle lets the product serve both audiences without splitting into separate tools.

Revenue & Client Management

Client Management Layer

Added a Clients page with per-client health scores, active risk counts, monthly revenue tracking, and system counts. Each client card shows status (Healthy/Warning/Critical), industry type, and quick actions for viewing dashboard or running simulations.

Revenue Visibility & Pricing

Built a Revenue Card prominently displayed on the business dashboard showing active clients, average per-client value, monthly revenue, and growth indicators. Added a Pricing & Earnings Calculator in settings with real-time projections: 'With 15 clients at ₹3,000/month → ₹45,000/month, annual: ₹5,40,000'.

Sales Enablement

Transformed the product into a sellable asset for IT service providers. Features include white-label mode (NetQ → Partner Command), multi-client incident simulation with 'Loss Prevented' counter, Smart Alerts with business impact context, and trust signals ('Used by IT providers managing 100+ systems', 'Average downtime reduced by 32%').

Tech Stack
React
TypeScript
Node.js
D3.js
WebSocket
REST API
PostgreSQL
Docker

Ready to evolve your digital infrastructure?

Limited intake for Q2. We prioritize partnerships that demand excellence and strategic innovation.