SLKone Website Positioning Plan

Source Signal

This plan translates the Management Workshop positioning and branding discussions into website changes for this Jekyll site.

Primary workshop conclusions:

Workshop language to preserve internally:

Most of our clients already know what needs to happen. The decision’s been made. What’s missing is the connection between that and it actually happening.

That’s the gap we close. We embed - small team, deep in the work, aligned on your actual priorities. We get to know how the business really operates, figure out where the leverage is, and then we move. We use AI the way we once used Excel, except it compresses weeks into hours. Your team can’t move at that speed without outside help.

We’re not an AI company. We’re a delivery firm that uses AI better than anyone else. Our clients don’t pay for decks. They pay because things actually change.

Messaging Architecture

Primary Position

SLKone helps leadership teams make the right call, align the business, and turn priority decisions into measurable results.

Use this on the homepage and services entry points. It is broader and more durable than an AI-first headline, while still making room for AI as the current acceleration wedge.

Supporting Points

Words To Use

Words To Avoid

1. Homepage

Files:

Change the hero from broad consulting language to the new execution-gap position.

Recommended hero copy:

hero:
  title: "Make the right call. Make the change real."
  description: "SLKone embeds with your team to clarify priorities, align the business, and turn high-stakes decisions into measurable revenue, cost, and cycle-time outcomes. We use AI the way strong operators use any practical tool: to understand the work faster, find leverage sooner, and help changes actually land."
  cta_text: "See how we work"
  cta_link: "/services"

Replace “What sets SLKone apart” points with workshop-aligned points:

Add a short proof band below the hero or before services:

We are not an AI company. We are a delivery firm that uses AI to move faster inside real business problems.

Use this as a positioning link into services and case studies.

2. Services Page

File:

Reframe the services page around the operating promise rather than the catalog.

Recommended subtitle:

Leadership teams rarely need another abstract recommendation. They need the right decision, a practical path, and the operating capacity to make change real. SLKone works inside that gap.

Recommended big paragraph:

We combine management consulting, operating experience, analytics, and AI-enabled delivery to move from diagnosis to implementation quickly. The service lines below are not isolated offerings; they are the lenses we use to help clients grow revenue, reduce cost, shorten cycle times, and sustain the change after we leave.

3. Digital Strategy and Technology

Files:

Current copy is tool-forward. Reframe it as AI-enabled workflow improvement.

Priority change:

Recommended AI Enablement angle:

We help teams identify where AI can improve real work, not where AI sounds interesting. Then we design the governance, build the MCP tools and integrations, and create the skills, agents, and automations needed to make the workflow actually improve.

AI Enablement should include:

4. Case Studies

Files:

The workshop repeatedly says the pitch is incomplete without proof. The site should surface 2-3 reference examples near the new positioning. Use approved or anonymized public-safe proof, not internal tool names.

Bridge proof strategy:

AI and analytics proof points from the MCP knowledgebase / insights:

Add tags or intro language that makes these examples findable as “AI-enabled delivery” or “execution gap” proof, even where older cases used Power BI, analytics, or automation rather than GenAI.

5. Insights

Files:

Recommended near-term article topics:

These should support the new pitch without turning the homepage into a thought-leadership essay.

Do not publish paid discovery as a thought-leadership article. Use Business Value Assessment as a focused lead-gen / sales landing page instead.

6. Navigation

File:

No immediate navigation change is required.

Possible later change:

Avoid adding a top-level AI nav item first. That would work against the workshop conclusion that SLKone is not an AI company.

Implementation Sequence

  1. Update homepage copy in _data/homepage.yml.
  2. Update services.md subtitle and big paragraph.
  3. Rewrite _services/Digital-Strategy-and-Technology.md to make AI a delivery accelerant.
  4. Rename/rewrite _sub-services/genai-readiness.md around AI Enablement. Prefer visible rename immediately; handle URL migration carefully.
  5. Add a proof band or curated case-study section on the homepage.
  6. Tag or rewrite 2-3 existing case studies to support the new proof narrative.
  7. Adapt the Business Value Assessment page as a public lead-gen and sales landing page. Use it as a secondary homepage CTA unless the team decides it should be the primary conversion path.
  8. Build the site with npm run build:css:prod and bundle exec jekyll build.

Open Decisions