390 lines
5.9 KiB
Markdown
390 lines
5.9 KiB
Markdown
# Queue North Website Redesign Strategy
|
||
|
||
```
|
||
Status: Current
|
||
Owner: _null
|
||
Last reviewed: 2026-08-18
|
||
Governs: brand positioning, tone, and the messaging standard every page is
|
||
written against
|
||
Review trigger: Any change to how Queue North positions itself, or to the
|
||
audience the site is written for
|
||
```
|
||
|
||
> The positioning argument behind the rebuild, written before it started. It is
|
||
> still the standard: the open content issues in `Batch 12 — Enterprise content
|
||
> rewrite` (#199–#209) are all defects measured against this document.
|
||
>
|
||
> `OVERHAUL_PLAN.md` says what the site should look like. This says what it
|
||
> should *sound* like, and why the previous one lost trust in seconds.
|
||
|
||
# Core Problem
|
||
|
||
Current website branding feels:
|
||
|
||
* too abstract
|
||
* too technical
|
||
* too personal
|
||
* too experimental
|
||
|
||
The site currently resembles:
|
||
|
||
* a developer portfolio
|
||
* infrastructure hobby project
|
||
* underground tech blog
|
||
|
||
Instead of:
|
||
|
||
* a mature B2B UCaaS provider
|
||
* managed IT partner
|
||
* enterprise communications company
|
||
|
||
This creates trust friction immediately.
|
||
|
||
Business buyers need confidence within seconds.
|
||
|
||
---
|
||
|
||
# Business Positioning
|
||
|
||
Queue North should position itself as:
|
||
|
||
## Primary Identity
|
||
|
||
Reliable business communications and IT infrastructure partner for SMB and enterprise clients.
|
||
|
||
## Supporting Identity
|
||
|
||
Modern, technically competent, responsive, security conscious.
|
||
|
||
Not:
|
||
|
||
* hacker aesthetic
|
||
* underground engineering lab
|
||
* mysterious tech collective
|
||
|
||
---
|
||
|
||
# Recommended Brand Direction
|
||
|
||
## Desired Feel
|
||
|
||
The website should feel:
|
||
|
||
* modern
|
||
* clean
|
||
* stable
|
||
* operationally mature
|
||
* enterprise capable
|
||
* technically sharp
|
||
* trustworthy
|
||
|
||
Think:
|
||
|
||
* RingCentral
|
||
* Zoom
|
||
* Cloudflare
|
||
* Cisco Meraki
|
||
* Dialpad
|
||
* 8x8
|
||
* Microsoft business products
|
||
|
||
But less corporate and less soulless.
|
||
|
||
Human but competent.
|
||
|
||
---
|
||
|
||
# Homepage Structure
|
||
|
||
# 1. Hero Section
|
||
|
||
## Goal
|
||
|
||
Instant clarity.
|
||
|
||
User should immediately understand:
|
||
|
||
* what Queue North does
|
||
* who it serves
|
||
* why it matters
|
||
|
||
## Recommended Headline
|
||
|
||
Business communications and IT that actually work.
|
||
|
||
Alternative:
|
||
|
||
Modern UCaaS and managed IT for businesses that cannot afford downtime.
|
||
|
||
## Supporting Text
|
||
|
||
Queue North delivers cloud communications, networking, managed IT, and infrastructure support for SMBs and enterprise teams.
|
||
|
||
## CTA Buttons
|
||
|
||
* Schedule Consultation
|
||
* View Services
|
||
|
||
Optional secondary:
|
||
* Contact Support
|
||
|
||
---
|
||
|
||
# 2. Trust Signals Section
|
||
|
||
This section should appear immediately after hero.
|
||
|
||
## Include
|
||
|
||
* uptime guarantees
|
||
* support response times
|
||
* certifications
|
||
* vendor partnerships
|
||
* years in business
|
||
* client industries
|
||
* deployment count
|
||
* SLA metrics
|
||
|
||
## Example Metrics
|
||
|
||
* 99.99% uptime
|
||
* 24/7 support
|
||
* multi site deployments
|
||
* secure cloud infrastructure
|
||
* enterprise grade failover
|
||
|
||
This is critical.
|
||
|
||
B2B buyers purchase risk reduction, not technology.
|
||
|
||
---
|
||
|
||
# 3. Services Section
|
||
|
||
## Recommended Layout
|
||
|
||
Clean enterprise card grid.
|
||
|
||
## Service Categories
|
||
|
||
### UCaaS
|
||
|
||
* hosted VoIP
|
||
* business phones
|
||
* call routing
|
||
* conferencing
|
||
* remote workforce support
|
||
|
||
### Managed IT
|
||
|
||
* endpoint management
|
||
* helpdesk
|
||
* patching
|
||
* infrastructure monitoring
|
||
|
||
### Networking
|
||
|
||
* SD WAN
|
||
* VPN
|
||
* firewall management
|
||
* switching
|
||
* wireless deployments
|
||
|
||
### Security
|
||
|
||
* MFA
|
||
* endpoint protection
|
||
* backups
|
||
* compliance
|
||
* monitoring
|
||
|
||
Each card should explain business outcomes, not technical jargon.
|
||
|
||
Bad:
|
||
"Kubernetes managed SIP orchestration"
|
||
|
||
Good:
|
||
"Reliable business communications with centralized management and failover"
|
||
|
||
Humans love inventing incomprehensible wording and then wondering why sales calls disappear.
|
||
|
||
---
|
||
|
||
# 4. Industry Use Cases
|
||
|
||
Very important for B2B trust.
|
||
|
||
## Example Industries
|
||
|
||
* healthcare
|
||
* logistics
|
||
* retail
|
||
* manufacturing
|
||
* legal
|
||
* finance
|
||
* distributed offices
|
||
|
||
Each section should explain:
|
||
|
||
* operational problems
|
||
* compliance needs
|
||
* uptime requirements
|
||
* remote work needs
|
||
|
||
---
|
||
|
||
# 5. Why Queue North
|
||
|
||
## Focus On
|
||
|
||
* responsiveness
|
||
* reliability
|
||
* technical depth
|
||
* direct support
|
||
* proactive monitoring
|
||
* vendor neutrality
|
||
|
||
## Avoid
|
||
|
||
Generic corporate fluff like:
|
||
|
||
* innovative solutions
|
||
* digital transformation
|
||
* next generation synergy nonsense
|
||
|
||
Every B2B site writes this garbage and nobody believes any of it anymore.
|
||
|
||
---
|
||
|
||
# 6. Testimonials / Case Studies
|
||
|
||
Mandatory.
|
||
|
||
Enterprise buyers need validation.
|
||
|
||
## Include
|
||
|
||
* measurable outcomes
|
||
* reduced downtime
|
||
* migration success
|
||
* support quality
|
||
* deployment scale
|
||
|
||
Even 2 or 3 strong case studies massively improve credibility.
|
||
|
||
---
|
||
|
||
# 7. Support & Operations
|
||
|
||
This is where technical sophistication can appear.
|
||
|
||
## Good Technical Signals
|
||
|
||
* network operations center visuals
|
||
* uptime dashboards
|
||
* support workflows
|
||
* monitoring systems
|
||
* escalation paths
|
||
|
||
## Bad Technical Signals
|
||
|
||
* hacker visuals
|
||
* terminal cosplay
|
||
* random code snippets
|
||
* obscure infrastructure references
|
||
|
||
Technical competence should feel controlled and operational.
|
||
|
||
Not chaotic.
|
||
|
||
---
|
||
|
||
# Visual Design Recommendations
|
||
|
||
# Colors
|
||
|
||
## Base
|
||
|
||
* white
|
||
* dark slate
|
||
* muted blue
|
||
* graphite
|
||
|
||
## Accent
|
||
|
||
* blue
|
||
* teal
|
||
* restrained cyan
|
||
|
||
Avoid:
|
||
|
||
* neon green
|
||
* hacker black/red
|
||
* cyberpunk palettes
|
||
|
||
Those aesthetics destroy enterprise trust surprisingly fast.
|
||
|
||
---
|
||
|
||
# Typography
|
||
|
||
## Recommended
|
||
|
||
* Inter
|
||
* Geist
|
||
* IBM Plex Sans
|
||
|
||
Professional sans serif.
|
||
|
||
Monospace only for tiny UI accents if needed.
|
||
|
||
---
|
||
|
||
# Layout Style
|
||
|
||
## Use
|
||
|
||
* large spacing
|
||
* strong hierarchy
|
||
* clean sections
|
||
* restrained motion
|
||
* clear CTAs
|
||
|
||
## Avoid
|
||
|
||
* excessive animations
|
||
* overloaded visuals
|
||
* scrolling gimmicks
|
||
* terminal-first design
|
||
|
||
Enterprise sites should feel efficient.
|
||
|
||
---
|
||
|
||
# Recommended Technical Stack
|
||
|
||
## Best Option
|
||
|
||
### Astro or Next.js
|
||
|
||
With:
|
||
|
||
* Tailwind
|
||
* Framer Motion lightly used
|
||
* CMS integration
|
||
* fast performance
|
||
* accessibility focus
|
||
|
||
---
|
||
|
||
# Key Messaging Shift
|
||
|
||
## Current Impression
|
||
|
||
"Interesting technical person"
|
||
|
||
## Required Impression
|
||
|
||
"Reliable communications and IT partner for serious businesses"
|
||
|
||
That distinction changes everything about the design language. |