A man writing in a notebook at a dark desk, lit by a small green lamp

/work_/Kleos

Capable people lose on LinkedIn to people who post more. So I built what shows up for them.

A managed LinkedIn service built as software. AI drafts in the client’s own voice, a person checks every draft, the client says yes in twenty minutes a week.

What
My own product. Brand, site, client portal, operator console, and the engine underneath.
Status
A business. Past MVP, proven with one design partner. Invite only.
Since
Clean build April 2026. First design partner May 2026.
Live
thekleos.co ↗
Kleosthekleos.co

/how-i-think_

Show up every week without selling yourself.

Having something worth saying and knowing how to say it on this particular wall are two different skills. Kleos supplies the second.

  1. 01

    Voice before volume.

    Nothing is written until the voice is real. A structured interview surfaces how the client thinks and what people actually pay them for.

  2. 02

    A person between the model and the name.

    Every draft passes under human eyes before the client sees it. Does it sound like them, is it grounded in something real, would they put their name on it?

  3. 03

    The correction is the product.

    A client’s note is not a fix to one post. It becomes an upgrade to their voice profile, so next week’s draft needs less of me.

  4. 04

    Build for the clients you have.

    One design partner means no dashboards for fifty. Each piece is cut to what runs end to end for one real person.

/the-journey_

Five months, eight moments.

From the first clean build to the first published case. Dates are from the workspace’s own session logs.

  1. 01/14 Apr 2026

    A clean build starts.

    The first version is frozen. Everything after this is v2.

  2. 02/6 May

    The client portal ships.

    Voice profile, weekly review, approve or send back with a note.

  3. 03/15 May

    First design partner.

    Nayyer’s account starts. From here it runs for a real person every week.

  4. 04/28 May

    The rule.

    Build for the clients you have, not the agency in the plan.

  5. 05/11 Jun

    The engine learns.

    A client’s correction becomes a proposed upgrade to their voice profile.

  6. 06/16 Jun

    The soul, written down.

    The gallery, the silenced artist, the hand on the brush.

  7. 07/14 Jul

    The workspace finishes itself.

    Five rooms, five doors, gates that block stale status and design bleed.

  8. 08/23 Aug

    The first case.

    Four months of Nayyer’s own LinkedIn export, written up and published.

/the-week_

Machines draft. People say yes.

Every client, every week, and where the lesson goes afterwards. The gates in terracotta are human.

Drag sideways to follow it

EVERY WEEK, LEFT TO RIGHTTHEN THE LESSON COMES BACK, RIGHT TO LEFT

Publishing without me: not yet. Earned by measurement, not by a switch. The fifth phase.

RESEARCH

What the wall rewards

This week, on this platform.

TOPIC

Picked, not random

Scored on the client’s ICP and goals.

THREE WRITERS

Same brief, three drafts

Seeded from a real story of theirs.

SCORED

Voice match, brand fit

Six sub-scores, with reasons.

HUMAN GATE

I read every draft

Steer, regenerate, or pass it on.

HUMAN GATE

The client says yes

Or sends it back with a note.

PUBLISHED

Under their name

Nothing goes out without a yes.

THE NOTE

“My sentences run longer”

The most valuable thing made all week.

DISTILLED

A durable lesson

Not a fix to one post.

HUMAN GATE

I approve the upgrade

Nothing rewrites a voice on its own.

VOICE PROFILE

Sharper next week

Every turn compounds.

/the-product_

Drawn first, then built.

I draw the screen before the agent writes a line. The console is dark with one lime stroke, for me. The client’s side is lit.

The console, drawn in May 2026

Topic on the left, draft on the right, scores under both. The layout the console was then built to.

Design frame for the Kleos console client page: selected topic beside the generated post, scores for ICP match, goals fit, voice match and brand fit

The client’s home, drawn in June 2026

One post at a time: read it, approve it, or send it back. A working prototype with sample content, now in build.

Design prototype of the Kleos client portal home: a greeting, one post that needs review with approve and send back, and this week’s posts on the right

The console, live

Two agents with a review queue each. Nothing they propose applies until I approve it.

The Kleos console, Agents page: Expertise Brain with 17 approved principles, Learning Loop with 0 pending

The learning loop, live

A client’s note lands here as a proposal to their voice profile, not as a fix to one post.

The Kleos console, Learning Loop page: pending review, nothing waiting

/the-soul_

Every platform is a gallery. Kleos is the hand on the brush.

In June I wrote the brand down as a self-portrait, in my own words, so no later decision could drift from it. Two panels.

The ache

Having something worth saying and knowing how to say it on this wall are two different crafts.

Kleos self-portrait, the ache: every platform is a gallery, but it hands the canvas to people who never learned to paint

Why it gets better

You react, it distils, a human approves, it compounds.

Kleos self-portrait, why it gets better: and the hand learns. You react, it distils, a human approves, it compounds

/how-i-build_

I am not a developer. I design, and the agent builds to it.

I design first, then hand the agent my taste and what I know about how people use a screen. What makes that hold is the folder around the model: a mission, a map, a method, a room per part of the business, and gates the machine checks so I do not have to remember.

Drag sideways to follow it

LOADED EVERY SESSIONONE DOOR PER ROOM. WALK IN, GET BRIEFED, GET A NEXT MOVE.CHECKED BY THE MACHINE, NOT BY MEMORYME

Plain English

Not a developer. I say what it should do and what it must never do.

THE AGENT

Claude Code

Plans, builds, tests, and writes the log at the end of the session.

COMPASS

The mission

One north star, in my words.

MAP

Where things live

Rules, and what to load before touching what.

METHOD

How work ships

Branch, verify, preview, approve, merge.

MEMORY

Every correction, a rule

Read before the next session starts.

ROOM

Console

ROOM

Engine

ROOM

Client portal

ROOM

Marketing

ROOM

Design studio

STATE

Live board

STATE

Live board

STATE

Live board

STATE

Live board

STATE

Live board

GATE

No done without the output on screen

GATE

Stale status cannot be committed

GATE

Design systems never cross

GATE

No invented stories, in code or copy

/the-proof_

One coach, twelve months, and the month it changed.

Nayyer Abdul Rab, executive coach in Riyadh, is the first design partner. Kleos took over his LinkedIn in May 2026. In month four a stranger who had been reading his posts asked to be coached. Every bar is from his own LinkedIn export.

Monthly impressions, Aug 2025 to Aug 2026

AugSepOctNovDecJanFebMarAprMayJunJulAug
Read the Nayyer case study →

/where-it-stands_

It works, and it is a business.

One design partner served end to end for four months, my own account running through the same pipeline. Invite only, no paid marketing, design partners before pricing. One thing said to every prospect before they sign: authority compounds over six to twelve months, not six weeks.

/you_

Is this you?

A consultant, coach, or partner with standing and no time to post. Or someone who wants to build Kleos with me.

Write to me →