A GTM engineer portfolio that gets replies | Mine, as the example

For a long time, I didn't have a portfolio. I had a list of tools.

Clay. Instantly. Smartlead. Make. HubSpot. I put them on my profile and waited for people to be impressed.

Nobody was. Because everyone has the same list.

I've built more than 30 outbound systems since then, and I finally built my own website, with a work page where every result sits next to the unedited screenshot it came from. This post walks through what a GTM engineer portfolio that actually gets replies looks like, using mine as the example, and how to build yours even if you've only done one campaign.

Why tool lists don't work

Think about it from the other side. A founder posts a GTM role and gets 100 applications in a week. Ninety of them list Clay, Instantly and n8n.

The tools line can't help them choose, because it's identical on almost every application. So they skip it and look for the one thing that's different: proof that you've done the job.

A portfolio is that proof. Nothing more, nothing less.

What goes in a portfolio that gets replies

1. A proof strip at the very top

Before anything else, your three or four best numbers, in one line. Someone gives your portfolio about five seconds before deciding whether to keep reading. Those five seconds should land on numbers.

Mine could read:

806 opportunities · $3.3M in pipeline · 10 roles in 7 countries · every one won cold

You don't need numbers that big. You need numbers that are real. "4 meetings from 1,200 emails" is a perfectly good proof strip if it's true.

2. Real campaigns, with the whole funnel

Don't just show the best number. Show the full path. This is what separates people who've done the work from people who've watched it.

These are four campaigns from my work page:

Notice the first row has a low reply rate, 1.47%. I show it anyway, because more than half of those replies were people who actually wanted to talk. That tells a hiring manager I understand which numbers matter. A portfolio full of only perfect numbers looks fake.

3. Screenshots, unedited

Claims are easy to make. Screenshots are hard to fake.

Every case study on my work page has the real dashboard screenshot next to it. Client names are blurred. Numbers aren't.

A screenshot changes the question a client asks. Without it, they wonder "is this real?" With it, they start asking "can you do this for us?"

4. What you built, in plain words

For each campaign, a few sentences: who it targeted, how you built the list, what the infrastructure looked like, what the copy angle was. Keep it short. They want to see that you thought about it, not read an essay.

5. One thing that broke

This is the part almost nobody includes, and it's the most persuasive section you can have.

One of my campaigns sent 5,000 emails and got 17 replies and zero interested. I'd launched into the US summer holidays. Over 100 out-of-office replies told me so. I wrote about it publicly, including what I'd do differently.

That story has done more for me than some of my wins. It shows I can diagnose a failure honestly, which is exactly what a client needs when their campaign goes quiet.

6. A short Loom

Two minutes, your screen, your voice. Walk through one Clay table or one campaign setup. Explain why things are in the order they're in.

A Loom does something text can't: it shows you understand the system well enough to explain it simply. It also shows you're a real person, which matters more than people think when you're working with clients across the world.

7. How to reach you

Make it easy. Email, LinkedIn, WhatsApp. If someone is impressed and can't find how to contact you in five seconds, you've lost them.

If you only have one campaign

Good. Start with one.

One real campaign is enough for a first portfolio. Here's how to present it:

1. The goal: who you targeted and why
2. The build: list, infrastructure, copy
3. The numbers: sent, replies, positives, meetings
4. What broke and what you changed
5. A screenshot
6. A two-minute Loom

That's a complete portfolio. It's more than most applicants have.

If you haven't run a campaign yet, build one for a real business, even for free. A local software company, a friend's agency, anyone with a real product. You're not doing it for the money. You're doing it for proof. I explain exactly how in how to become a GTM engineer from Pakistan.

Where to put it

At the start: a single Notion page. Free, fast, and perfectly good.

Later: your own website. Mine took longer to build than any campaign I've run. Writing about your own work is harder than doing it. But it's worth it, because a website can rank on Google, carry your whole story, and keep working for you while you sleep.

Then link it everywhere: your LinkedIn profile, your Upwork profile, the first line of your applications, your email signature.

The mistakes I see most

• Only showing perfect results. Looks fake. Show the real range
• No numbers at all. "Helped a client with outbound" proves nothing
• Too long. If it takes ten minutes to understand, nobody will
• No contact details. You'd be surprised how often this happens
• Lying. Never claim a result you can't back up on a call. It always comes out

What a portfolio is really for

A portfolio isn't about looking impressive. It's about making it easy for someone to trust you.

When I was starting out from Pakistan with no network and no famous companies on my CV, trust was the only thing I didn't have. My portfolio is how I built it, one real result at a time.

You can do the same. Start with whatever proof you have. Add to it with every campaign. In a year, you won't recognise it.

Want feedback on your portfolio?

If you've built a portfolio and it's not getting replies, or you're not sure what to include from the work you've done, message me on WhatsApp.

Send me what you have, even if it's rough. I'll tell you honestly what's working and what I'd change.