ServaxNet | Repositioning & Content Engine Case Study

The context

A technically excellent product that buyers couldn't hear.

ServaxNet runs and manages its own hosting infrastructure: "server management to help companies reduce operating costs."

What existedDeep infrastructure capability

A not-reseller position: "we run and manage our own infrastructure and network." And a website in need of a redesign.

What was missingEverything commercial

In my own audit words: no defined target audience, no strong channels, no marketing system in place, and a product story that was "too dev focused with no business benefits."

Discovery

The audit found a translation gap.

The product was described in engineering terms to buyers who decide on business outcomes: cost, speed, uptime, "your success." Nothing converted technical capability into language a customer could act on.

"Too dev focused with no business benefits."From the ServaxNet repositioning brief, my own working file. It names the deeper issue: a missing layer between what the servers do and why a business should care.

Root cause

There was no operating layer to turn capability into (1) segmented positioning, (2) buyer-language messaging, and (3) a publishing cadence that ran on its own.

The questions that set the agenda

Who is the buyer, and what do they decide on?Business outcomes: cost, speed, uptime. Not server specifications.

Why was the current marketing failing?No audience, no channels, no system. Content written for engineers, read by no one.

Problem: A technically excellent product described in engineering terms to buyers who decide on business outcomes. Real capability, commercially invisible.
Users: Three buyer situations: WordPress sites that outgrew shared hosting, AWS clients paying for scaling they do not need, and growing eCommerce stores on Magento or WooCommerce.
Solution: Segment the market, package the product to match each situation, and run one repeatable content engine underneath: calendar, voice standard, cadence.
My remit: Audit and repositioning strategy, market segmentation, content-system design, brand-voice standard, site-copy architecture direction, scheduling and publishing, cross-team coordination.
Team: A copywriter contributed drafts, a designer produced the creative, and the client owned subject matter and approvals.

The strategy

Segment the market, then package the product to match.

Instead of one generic "hosting" pitch, the strategy split the market into three buyer situations, each a different reason to move.

Segment 01Outgrown shared hosting

Large WordPress sites that got too big for simple shared plans.

Segment 02Over-provisioned on AWS

AWS clients paying for scaling services they do not actually need.

Segment 03Growing eCommerce

Magento and WooCommerce stores that need hosting built to grow with them.

Rebuilt from the ServaxNet strategy brief; the three segments are quoted directly from the file.

The system

The repeatable content engine

One template, one voice standard.

01Plan

Editorial calendar maps months to topics, events, and holidays.

02Produce

Copy bank plus creative built to the plan, in reusable variants.

03Voice-check

Drafts rewritten against a documented brand-voice standard.

04Schedule

Dated and timed in Hootsuite, based on progress status.

05Repeat

The same template re-applied the next quarter. No rebuild.

Execution: what shipped

Strategy on one side, the live site on the other.

Working Google Doc with the full ServaxNet site copy, signed in under the agency account — **The copy, written**The full site-copy working document, page by page with headline hierarchy and CTAs, signed in under the agency account.

Redesigned ServaxNet homepage showing Your Success is Our Success and four packaged solutions — **The repositioned homepage, live**"Your Success is Our Success" and four packaged solutions. The segmentation strategy, shipped and publicly captured in December 2021.

Copy architecture

Seven pages, one story

The site-copy document structured the whole product line into a page tree with headline hierarchy and CTAs:

WebOpsCloudDedicatedHybridColocation / IAASHigh-AvailabilityEmail

"The 'Buck' stops here. We aren't resellers, we run and manage our own infrastructure and network."Positioning line from the ServaxNet site-copy document.

Left to right: the copy as it was written, the repositioned homepage it became, and the architecture underneath. Scroll inside the frames; click any image below to zoom.

Three of thirteen branded assets produced to the calendar.

The content-mix model

Every quarter planned against a fixed ratio, so the feed stayed useful instead of purely promotional.

Service info, tips, reviews

50%

Lifestyle, pain and gain

30%

Promotional

20%

The hashtag-tiering model

A target distribution across tag sizes, so posts reach beyond only the biggest, most crowded tags.

100K+ tags

20%

50K+ tags

25%

20K+ tags

25%

500K+ tags

15%

1M+ tags

10%

Target distribution for Group 1 tags, from the planning workbook.

The reusable framework set

Three artifacts that turned "post something" into a system anyone could run.

A content-mix formula (50/30/20 plus 80/20) governing every calendar.
A hashtag-tiering model across five audience sizes.
A keyword-cluster template from Google Keyword Planner: core, secondary, long-tail.

Frameworks are process, not output. They are the part that survives past any single post.

Transparency note

Deliverables belong to Greaux Digital and ServaxNet. The visuals here are reconstructions from my own working files, including the strategy brief, content calendars, planning workbook, and copy documents. Charts labeled as rebuilt are redrawn from those files for legibility. Teammates are shown as roles, not names. Nothing shown is work I did not do. No performance data survives in the files, so none is claimed.