The Fractional Playbook + You Don’t Need Case Studies to Start Fractional Work

You Don’t Need Case Studies to Start Fractional Work

I made about $750k in my first year of fractional work without case studies.

You Don’t Need Case Studies to Start Fractional Work

My first year I made about $750k doing fractional work without case studies.

I assumed that meant I should hurry up and add them.

Turns out almost nobody read them.


Key takeaways

• Long case studies are rarely the best first impression

• Most people are just trying to answer one question: can this person help us?

• AI makes polished portfolios easier to produce, so polish alone means less

• A simple proof format works better: sentence, result, visuals

• Big numbers help, but shipping still counts


Someone asked me recently how to move into fractional work.

They were smart, experienced, and willing to put in the work.

But they were stuck on the same thing almost everyone gets stuck on.

“I need a portfolio.”

And what they usually mean is:

“I need to write case studies.”

Design, marketing, finance, product, engineering, ops. Same pattern.

Long writeups. Full breakdowns of the process.

Not because the work is bad.

Because most people are not going to read it.


I learned this the hard way

When I first put up my website, it barely had anything on it.

Just three things:

• a clear explanation of who I sell to

• a bit about what they get

• a few tiny thumbnails of work

That was it.

No case studies.

Not for the first year.

And the whole time I thought I needed them to look legitimate.

So eventually I added them.

Then I watched the data.

Almost nobody clicked into them.

Almost nobody read them.

A few people did.

Most didn’t.

That taught me something useful.

Most people are not trying to study your work process.

They just want enough proof to decide if you might help.


People are moving fast

Founders, hiring managers, and recruiters are usually trying to answer one question:

Can this person help us?

If your work takes ten minutes to understand, a lot of people will skip it.

So the goal is not to tell the full story.

The goal is to make the point quickly.


Why this matters even more now

AI makes it easier to make work look impressive.

A nice case study.

A better website.

Smart sounding copy.

A polished portfolio.

That kind of presentation is much easier to produce now.

So polish by itself is not a strong signal anymore.

You can make something sound more intelligent than it really is.

But it’s still hard to fake real work.

A screenshot.

A shipped page.

A before and after.

A real doc.

A real result.

Those tell people more than five pages explaining the process.


What works better: the 3-piece proof

Good proof of work can be simple.

Usually you only need three things.

1) One sentence

What did you ship or change?

Who was it for?

What problem did it solve?

2) One result

Something concrete:

• shipped in two weeks

• cut steps from 10 to 4

• got the first 20 users

• replaced a manual process

• made something clearer

• took something from idea to live

3) A few visuals

Give people something they can scan quickly.

3 to 6 items is usually enough:

• screenshots

• before and after

• dashboards

• docs

• short clips

• diagrams


Example

Sentence

Shipped a new onboarding flow for a B2B tool so users reached the useful part faster.

Result

Cut steps from 9 to 4. Shipped in 12 days.

Visuals

Before and after screens plus a 30-second walkthrough.

That is often more useful than five pages explaining how you got there.


“But I don’t have big results yet”

That is normal.

A lot of early proof is not about huge numbers.

It is about shipping something real.

Smaller proof still counts:

• speed

• completeness

• a clear before and after

• something that is now live

• something manual that became automated

• something confusing that became easier

Shipping is proof.


A simple format you can copy

Project name

What it is

Sentence

What you did and why it mattered

Result

What changed, what shipped, how fast, what happened

Visuals

3 to 6 screenshots or artifacts

Link

Live site, prototype, doc, or walkthrough

That is enough.


Examples by role

Design

Before and after screens, onboarding flow, shipped UI, release notes

Marketing

Landing page before and after, funnel snapshot, email results

Finance

Model snapshot, runway dashboard, forecast vs actual

Engineering

Shipped feature list, architecture diagram, performance improvement

Product

PRD excerpt, release notes, experiment result, customer quotes

Ops

Process map before and after, automation, cycle time improvement

You are not proving you can write.

You are proving you can deliver.


Do this instead

Post one piece of proof each week.

Keep it short.

Make it easy to skim on mobile.

Put it somewhere people will actually see it:

• LinkedIn

• a single Notion page you can reuse

• your website under “Proof” or “Work”

You do not need a fancy site.

You need a place where someone can land, scan, and quickly understand what you do.


The main idea

Long case studies are not useless.

They just usually are not the first thing people care about.

AI makes polished presentation easier.

So people care more about what is real.

Make your work easy to scan:

One sentence.

One result.

A few visuals.

That is often enough for someone to think:

“This person can probably help.”


Thanks for reading!

Gev