I posted the first three editions and grew to 5 subscribers!

It is a small number but very cool!

To all 5 subscribers, thanks a lot for being here.

Writing about go-to-market and my work at Baseloop also gave me ideas for LinkedIn posts.

Baseloop is our data enrichment platform.

So I turned some editions into LinkedIn posts and vice versa.

They brought me 4802 impressions so far this month.

The posts reached 1789 people on LinkedIn.

My best-performing post was about the start of this Substack.

Now I need to get my LinkedIn readers to subscribe here.

That is my goal for the coming month.

For all the new people here, these are the topics I wrote about this month:

• My start at Baseloop and everything I will talk about on this Substack.

• How I let Claude interview me before I build any GTM flow.

• What Benny, my AI personal assistant, does for me every day and how I make him better every week.

Next up: on Tuesday I publish my first long read and playbook for paid subscribers.

I will talk about how to turn your old CRM data into new pipeline opportunities.

Let me know if you want to talk about a specific use case via a direct message.

On to the next 5 subscribers on Substack!

Subscribe now

How do you work with AI the way you work with a co-worker?

The answer is the same as for a co-worker: they need to know what you know.

A team only works when everybody knows the same facts before the next campaign, cold call or ad.

So I started with a Second Brain: a folder of plain text files my AI reads before it does anything.

It holds what the AI needs to prep my day or draft a mail: who my clients are and how I write.

Example: every morning I get an email from Benny, the AI assistant I built, with everything I need to do that day.

• Who to call and what to talk about.

• What to ask my team.

• Which email or Slack message is still waiting on me.

He writes the draft too.

Benny knows exactly how I like my emails and warns me about the things I forget.

Like a second follow-up or a last-minute change in my calendar.

Why does Benny know how to prep my day?

I wrote down a Standard Operating Procedure, SOP for short, in plain English: how to do this exact task.

Write a lot of those task explanations (SOPs) and you have a Second Brain.

No idea where to start?

I made a Skill (a task file for your Claude or Codex) that interviews you. You set it up together with your AI.

Subscribe I will send it to you for free!

Connect on LinkedIn

Therefore you need a very well written spec.

Short for: Technical Specifications.

The reason you need a spec is simple. It is like the architecture of a house.

You need to make sure the foundation is made for the weight of the roof.

In order to know what kind of foundation you must build, you must know what roof will be put on top.

In short: Get the full picture of the automation only then automate.

Before I dive into a very technical boring story. I’ve made it as simple as possible.

Together with the Baseloop plugin it will build the whole ‘spec’ for you.

Click here to start with Baseloop in Claude

Give the following 10 points to your Claude or Codex and ask it to interview you.

1. Name of the automation. One sentence what you want to solve

2. Data in. Where the data come from and in which format.

3. Data out. Where the data needs to sync into a sequencing tool or your CRM

4. Volume. How many records/leads do you want at the end

5. Where it stops. The last thing the automation does

6. How it works today. Who does it, in which tool, how many hours per week and the exact steps you do manually

7. Run conditions. What needs to keep running and what needs to be excluded.

8. Trigger. What starts a run and should it run on auto-on.

9. Success metric. When is the workflow a success.

10. Important details. Special rules, not in the points above but are important context to make this automation work.

Don’t forget to use Claude Opus 5 or GPT 5.6 Sol as your model.

Fable and Astra for the real players!

Share GoToMarket.md

It was the time I would ask my boss to build it for me.

He would spend several hours building a very neat workflow that did the job.

But he could also spend it on growth or retention. So we worked half automated, half manual.

Today I’m making the most crazy workflows that give me time to do more of the stuff that drives growth.

Like selling Baseloop, our data enrichment platform.

One example. A cold call ends. The transcript lands in Baseloop, the HubSpot task is created and the follow-up email is drafted before I have the next prospect to call.

I say what I want out loud, Claude Code reads it and builds the workflow straight into Baseloop. I never build in the Baseloop platform manual.

My name is Vincent van der Plas. Not a sales guru. Not the developer coding crazy stuff. Just a go-to-market enthusiast who can prompt but not code, building the workflows I use every day to e.g. call, follow up and book demos.

This is for RevOps, GTM engineers and for the AEs and sales leaders the workflows are build for.

Abonneer nu

We will never replace the rep with AI.

But everybody on the revenue side should get the boring half of the job done for them. Spend more time calling prospects and giving demos instead of doing the admin afterwards.

In this series we will speak about how to leverage AI every day. Combining all the popular tools like Claude, LinkedIn Sales Nav, Baseloop and your CRM to make your go-to-market a bit more automated.

How I:

• Never miss a follow-up after a cold call, demo or follow-up call

• Turn demo calls into a product roadmap for our developers

• Re-activate your CRM into a gold mine for new pipeline.

Every week I share my insights on go-to-market for free.

For €12 per month we will have co-build sessions, in-depth articles and all the playbooks I use during my work.

This only works if you tell me what to build. So let me know what you want to talk about and what workflows are on your mind.

Deel GoToMarket.md

Connect on LinkedIn