Build. Grow. Repeat.

Your agent can build almost anything now. So why did my projects still move in bursts?

Because the agents were never the slow part. I was. With several projects and a full calendar, a project only moved when I sat down with it – and sometimes that meant a whole week without progress. In this episode I show what changed it: one roadmap per project. Two jobs stay with me: deciding what gets built next, and reviewing it before a customer sees it. Everything in between is the agent's.

You'll see it in practice: one idea for Customer Magic that became a roadmap item, a brief the agent wrote itself after talking to my compliance session, and a finished trust page I only had to review. Then why the deciding stays human, what a roadmap holds in four stages, and three places to keep it – an artifact in Claude Code, a page in your codebase, or a tool like Linear.

This is not theory. I run four projects this way and check in about twice a day.

WHO THIS IS FOR

A founder with several projects where one always waits
A vibe coder whose agent builds fast, in no clear direction
Anyone who starts every session by explaining again what comes next
A small team that wants steady progress without a project manager

IN THIS EPISODE

00:00:00 – Your agent needs a roadmap from you
00:00:36 – The bottleneck is you
00:01:38 – Two jobs stay with you
00:02:04 – One idea, from message to finished page
00:05:07 – Why deciding stays human
00:06:58 – What a roadmap holds
00:07:51 – Three places to keep it
00:11:17 – Deciding what's next, twice a day
00:13:31 – Give your agent a roadmap
00:14:48 – Upcoming events and the Pirate Forge

DEEP DIVE LINKS

📖 Full Article + the starter prompt: https://pirateskills.com/insights/agent-roadmap

🧪 Pirate Lab – 21 October: https://pirateskills.com/pirate/lab/2026-10-21

🧭 AI Compass – 28 October: https://pirateskills.com/aicompass/2026-10-28

🏴‍☠️ Vibe Coding Cologne – 4 November: https://pirateskills.com/events/vibe-coding-cologne/2026-11-04

🛠️ Vibe Hackathon Cologne – 20 November: https://pirateskills.com/events/vibe-hackathon-cologne/2026-11-20

⚓ Pirate Forge: https://pirateskills.com/pirate/forge

🎧 Spotify: https://open.spotify.com/show/7kFl0BJiOYih8yqQTRR9SN

🍎 Apple Podcasts: https://podcasts.apple.com/us/podcast/build-grow-repeat/id1870561487

🗓️ All upcoming events: https://pirateskills.com/events

💬 Connect with me on LinkedIn: https://www.linkedin.com/in/bensufiani/

What if a full-time designer was never out of reach for a small team – you just didn't have the process yet?

Two weeks ago, screen designs looked dead to me: the old Figma chain where a product manager briefs a designer who briefs a developer. Then one weekend on a design canvas changed that. Nine hours, 77 messages and 79 versions later there was a brand for Zawq, my new project – and not one line of product code. The agent serves the buffet, you are the curator.

You'll see the whole canvas: the first six website directions that all sucked, the gardening idea that stuck, the low-poly 3D scene built with Three.js, and the landing page at draft nine. Then the logo that could never have been briefed – from generic wordmarks to an app-icon bonsai in the Moyogi shape, and why the 2D version only worked after going 3D first. And what gets decided before any code exists: colors, dark mode, accessibility checks, a component library and a few app screens.

This is not done. The real app isn't built, and the 3D scene still has to run on an average phone. My own design level is a solid six out of ten – so find a friend with real design chops and let them tell you what's still weak.

This is not theory. The new homepage went live today: https://zawq.ai

WHO THIS IS FOR

A founder who ships straight into code and ends up with a generic-looking product
A vibe coder who has never run a design round before building
A small team that can't afford a designer or an agency back-and-forth
Anyone starting a new product who wants a real brand from day one

IN THIS EPISODE

00:00:00 – The design process I got addicted to
00:01:43 – Screen designs are back
00:04:17 – One weekend, one canvas
00:08:57 – Nine hours, 77 messages, 79 versions
00:10:46 – How a design round works
00:12:30 – The logo I couldn't have briefed
00:17:45 – Decide it before it's code
00:20:58 – What's not built yet
00:22:05 – Your vibe design weekend
00:25:06 – Upcoming events and the Pirate Forge

DEEP DIVE LINKS

📖 Full Article + the starter prompt: https://pirateskills.com/insights/vibe-design-process

🏴‍☠️ Vibe Coding Cologne – 7 October: https://pirateskills.com/events/vibe-coding-cologne/2026-10-07

🧪 Pirate Lab – 21 October: https://pirateskills.com/pirate/lab/2026-10-21

🧭 AI Compass – 28 October: https://pirateskills.com/aicompass/2026-10-28

🛠️ Vibe Hackathon Cologne – 20 November: https://pirateskills.com/events/vibe-hackathon-cologne/2026-11-20

⚓ Pirate Forge: https://pirateskills.com/pirate/forge

🎧 Spotify: https://open.spotify.com/show/7kFl0BJiOYih8yqQTRR9SN

🍎 Apple Podcasts: https://podcasts.apple.com/us/podcast/build-grow-repeat/id1870561487

🗓️ All upcoming events: https://pirateskills.com/events

💬 Connect with me on LinkedIn: https://www.linkedin.com/in/bensufiani/

In many companies, nobody can name the person responsible for their AI. So the answer defaults to "no".

Nur Aslan founded IADM, the International Academy for Digitalization and Management – a CPD-accredited academy that trains Certified AI Officers. She came to AI governance from HR: for her doctorate she surveyed 397 HR professionals across Europe and kept finding the same gap between AI adoption and AI readiness.

In this episode we pick up where the conversation with Dr. Alexa Scheffler ended. Alexa answered "can we use AI for this?". Nur answers the people side: who is responsible, and how do they need to be trained?

We talk about why big companies say no to AI for months – in one case, a year and a half – why governance should be an enabler and not a brake, and why a small team doesn't need to hire an AI officer. By the end of the episode, I'm the AI officer at Pirate Skills.

Nur's Monday list for a new AI officer: list your AI tools, classify them by risk, name who is responsible for anything high risk, and get technical help where it gets technical.


IN THIS EPISODE
00:00 Welcome – a compliance academy incorporated in England
02:50 The gap between AI adoption and AI readiness
06:31 Governance vs compliance – what's the difference?
08:18 Why big companies say no to AI
11:03 Does a small company need an AI officer?
17:02 Training your team: risk classes and the AI inventory
18:29 Building the academy: from live Zoom to AI avatars
24:28 Is there a Claude skill for the EU AI Act?
27:02 The Monday list for a new AI officer
32:02 Why Europe needs to move faster
34:50 See you at Vibe Coding Cologne


DEEP DIVE LINKS
– The companion article: https://pirateskills.com/insights/navigating-ai-governance
– Part one, with Dr. Alexa Scheffler: https://pirateskills.com/insights/navigating-ai-compliance
– Pirate Forge – Build phase starts this Wednesday, 30 Sep: https://pirateskills.com/pirate/forge/q4-26
– Meet Nur live at Vibe Coding Cologne, 7 Oct: https://pirateskills.com/events/vibe-coding-cologne/2026-10-07
– Connect with Nur: https://www.linkedin.com/in/nurgul-aslan-70600833b/
– Connect with Ben: https://www.linkedin.com/in/bensufiani/

A native mobile app, built in one weekend and running on my own iPhone – with my kids over for most of it.

Two years before Pirate Skills, at Maple Apps, a designer and three full-time developers still needed two weeks to get from finished screen designs to the App Store – and that was a high-performing team. The industry standard is months of work and tens of thousands of euros you'll probably never make back. This time it was one founder and Claude Code, and that was fascinating to me: it's truly possible now.

You'll see the Maple Apps rule – no line of code before 1,000 people are on the waitlist – and why an app is not your business but one more door into it. There's the choice between going fully native (Swift and Kotlin) and React Native with Expo, and why that took a weekend instead of a debate. You'll see screen designs made with Claude Design, the first screens on the phone through Expo Go, and the moment the app was really installed, on an hour-long ride to a kids' birthday party.

To be honest about where we are: it's not in the App Store yet. The Apple and Google developer accounts are waiting for approval, then come the store rules and the review. Test users are planned for Vibe Coding Cologne on 7 October, with the app live in the stores by November at the latest.

The push to finally try came from a first-time builder at our hackathon who shipped her first app without any technical background. If she can do it, and I can do it, you can too.


IN THIS EPISODE

00:00:00 – A native mobile app in a weekend
00:01:05 – Maple Apps: 1,000 sign-ups before a line of code
00:03:30 – Two weeks vs. months and tens of thousands of euros
00:04:15 – The app is one door, not the business
00:06:19 – Native or React Native + Expo
00:08:36 – Friday: a protected API and new screen designs
00:11:21 – Saturday: the first screens on my phone
00:12:52 – Installed for real, on the way to a birthday party
00:14:39 – Not in the App Store yet
00:15:46 – Your weekend: the step-by-step guide
00:19:41 – Upcoming events and the Pirate Forge


DEEP DIVE LINKS

📖 Full Article + the starter prompt: https://pirateskills.com/insights/mobile-app-in-a-weekend

⚓ Pirate Forge – 30 September : learn vibe coding and vibe marketing by building a real app alongside me: https://pirateskills.com/pirate/forge

🎧 Spotify: https://open.spotify.com/show/7kFl0BJiOYih8yqQTRR9SN

🍎 Apple Podcasts: https://podcasts.apple.com/us/podcast/build-grow-repeat/id1870561487

🗓️ All upcoming events: https://pirateskills.com/events

💬 Connect with me on LinkedIn: https://www.linkedin.com/in/bensufiani/

Your users can now send their own AI agent to get what you offer: find an event, sign up, search your knowledge, even prepare a checkout. They never have to open your website.

Most vibe-coded Next.js apps can't do that yet. Your website is a teller who needs to see a face: the code behind every button checks the browser's login cookie first, and an agent calling from ChatGPT, Claude or a server has no cookie. So it gets turned away. Not because it isn't allowed, but because the teller can't see a face.

On 13 September I connected pirateskills.com to my own Claude.ai, sent one chat message, and it registered me for an event. Here is how we got there, explained for people who vibe-code, not for senior engineers.

First, build the vault once. Each valuable action (discover events, register, search the knowledge, start a checkout) becomes one server function that is told who is asking, with the same AI SDK tool card for every door.

Then open thin doors onto it. The Captain, our on-page chat built with the Vercel AI SDK and the AI Gateway. An MCP server with OAuth sign-in for Claude, ChatGPT and Codex. API keys you create and revoke yourself. And a CLI for anyone in a terminal, you or your coding agent.

Why not stop at MCP? I personally am annoyed that these types of connections rarely hold. An agent running in the cloud, on OpenClaw, Hermes or a scheduled job, has nobody there to click "allow". OAuth is the convenience. The key is the guarantee.

A public SKILL.md is the treasure map: which door, when to use each tool, and an explicit yes before anything that changes something. And for money, the crew prepares the Stripe checkout and you sign. No tool can charge a card.

You don't need five doors. One vault and one door is the whole first version, and the article has the six steps plus a prompt to hand your coding agent.

IN THIS EPISODE

00:00:00 – Open your vault to agents

00:01:52 – The teller problem: six clicks to join an event

00:02:49 – Demo: signing up for the AI Compass from Claude

00:04:26 – What's in your vault

00:06:02 – Five doors into one vault

00:08:58 – How to build it with Next.js and the Vercel AI SDK

00:11:59 – Your own chat, MCP, and why an API key holds

00:15:45 – The skill: a map for your users' agents

00:17:52 – Agentic commerce: the agent prepares, you pay

00:20:26 – Open your first door, with a live build

00:26:26 – Where to go from here

DEEP DIVE LINKS

📖 Full Article (with the four doors, the handshake-vs-key table and the prompt for your coding agent): https://pirateskills.com/insights/open-your-vault

🎧 Spotify: https://open.spotify.com/show/7kFl0BJiOYih8yqQTRR9SN

🍎 Apple Podcasts: https://podcasts.apple.com/us/podcast/build-grow-repeat/id1870561487

🗓️ All upcoming events: https://pirateskills.com/events

💬 Connect with me on LinkedIn: https://www.linkedin.com/in/bensufiani/

Your product can keep fixing itself while you sleep — and so can your marketing.

For two weeks pirateskills.com has run on a loop I set up inside Claude Code: a scout that reads every data source once a day, a fixer that works the queue every four hours, and me answering a question only when the system is unsure, changing product direction, or about to do something risky. 142 passes, 38 product fixes, 39 signals watched, a test suite that more than doubled.

PostHog proposed the self-driving product. This goes one step further. The same shape watches your marketing, your funnel and your money path, not just your code — which is why I've started calling it the self-driving startup.

You'll see my actual screen: the loop's setup and the cloud routines it runs on, the Linear board the agent manages on its own, the Vercel runtime logs and PostHog events it reads, the database advisors and Stripe checkouts it checks, and the skill file that decides how far it may go without me.

The shape matters more than the tools. Many sources feed one queue. Two roles, finders and finishers. A verification bar instead of a reviewer. A human who answers questions instead of doing tasks. And re-measurement, so what ships changes what the loop reads next.

You don't need my setup to start. One source, one queue, one agent working it is the whole first version — and the last stretch of the video is the seven steps to build it this week.

IN THIS EPISODE

00:00:00 – Beyond the self-driving product
00:01:25 – What you don't see happening in your own app
00:04:02 – The shape: one scout, one fixer
00:06:41 – The numbers after two weeks
00:08:56 – Source one: your runtime logs
00:13:18 – Source two: analytics and the money path
00:17:04 – Database, payments and dependency updates
00:19:22 – The same loop for marketing, and moving it to the cloud
00:23:24 – Linear is the inbox, and the rules the agent lives by
00:33:51 – Build your own: the seven steps
00:39:01 – Where to go from here

DEEP DIVE LINKS

📖 Full Article (with the live coverage map, the one-day timeline and the free 7-day checklist): https://pirateskills.com/insights/self-driving-startup

📈 The Meta Ads Loop — the marketing half of this shape, in detail: https://pirateskills.com/insights/meta-ads-loop
⚓ Pirate Forge — Q4 cohort starts Wednesday, 30 September: six weeks to vibe code your first revenue-ready SaaS, then six weeks to vibe market it: https://pirateskills.com/pirate/forge
🎧 Spotify: https://open.spotify.com/show/7kFl0BJiOYih8yqQTRR9SN
🍎 Apple Podcasts: https://podcasts.apple.com/us/podcast/build-grow-repeat/id1870561487
🗓️ All upcoming events: https://pirateskills.com/events
💬 Connect with me on LinkedIn: https://www.linkedin.com/in/bensufiani/

Marcus Haas is a mechanical engineer. Paul Anduschus is a former event manager who studied business psychology. Together they run DreamyTales, selling personalised AI-generated books, songs and videos in more than ten countries — and neither writes code.

This is the conversation I've wanted to record for a year: how do you actually find a positive-ROI campaign instead of guessing, and how much of that can you hand to an agent?

They cancelled Triple Whale and rebuilt blended ROAS themselves. Meta comes in through the Meta Ads MCP, Shopify through an app they built, and three skills merge the data into a dashboard that runs every morning inside Codex. No database. Why two sources? Because Meta only shows you 60 to 70 percent of the truth.

The most interesting part is how the automation was built. Paul already had rules for scaling, killing and creating campaigns. He talked them out loud, had AI turn them into a document, and that document became skills.

That's the real lesson: the ceiling on your automation isn't your technical skill. It's how much of your own judgment you've made explicit.

They haven't gone fully automatic. The agent creates campaigns, but Paul still approves daily budget moves because his rules still have gaps. Marcus supervises the big steps while openly admitting the model makes fewer mistakes than he does.

And on creative, AI is good at describing what's in a competitor's winning ad but, in Paul's words, “really bad at describing the aesthetics of it.” So the humans work out why it performs, and the machine generates ten videos per prompt.

IN THIS EPISODE

00:00 – What a €90 subscription actually costs the people selling it
01:22 – Meet Marcus and Paul: a mechanical engineer and a jack of all trades
08:08 – Running a whole backend without being a developer
15:17 – Three years of organic didn't work. One euro of paid did.
23:00 – The Triple Whale problem every D2C brand has
28:23 – Meta only tells you 70% of the truth
30:15 – The three skills that replaced the dashboard
32:25 – "We are not operators anymore. We are supervisors."
35:51 – Where they give the agent the leash, and where they don't
49:22 – The creative pipeline: from the Ad Library to ten videos
1:01:08 – The real superpower isn't finding the secret ingredient

DEEP DIVE LINKS

📖 Full article — the argument, not a recap, with every quote timestamped to this episode: https://pirateskills.com/insights/vibe-code-ad-reportin
🏴‍☠️ Vibe Coding Cologne — Wednesday 2 September, 18:30–21:00, STARTPLATZ Cologne: Paul and Marcus are on stage on agentic performance marketing. Free: https://pirateskills.com/events/vibe-coding-cologne/2026-09-02
🎁 DreamyTales Marcus and Paul's company: https://www.dreamytales.de
🔗 Marcus on LinkedIn: https://www.linkedin.com/in/marcus-haas-212a77215/
🔗 Paul on LinkedIn: https://www.linkedin.com/in/paul-anduschus-912060190/
🗓️ All upcoming events: https://pirateskills.com/events
💬 Connect with me on LinkedIn: https://www.linkedin.com/in/bensufiani/

Dr. Alexa Scheffler builds the software that answers one question for large companies: are we actually allowed to use AI for this? Her reading of the EU AI Act is close to the opposite of the one most German companies are operating on.

She spent years inside corporates watching good ideas die at the compliance step — not because anyone could produce the rule that forbade them, but because nobody in the room had read far enough to say otherwise. So she built REGULIGHT: a chat agent that asks only the questions it actually needs, and a workflow that keeps the evidence tidy for whenever an audit shows up.

The part of this conversation I keep coming back to is what the Act asks for first. Not a ban, not a registry, not a consultant. It asks that the people in your company are educated with AI — and that you write down who was trained, when, and on what. Two names, a date, a topic. Her words: "Write it down and then you're safe. It's not that difficult."

We also get into where the risk actually lives. Fully automated credit decisions and hiring with no human in the loop are high risk, deliberately and for good reason. But move the human back into the decision and the same tool changes category — which means most of the time you aren't asking permission, you're choosing a design. And the question that unlocks the meeting isn't "are we allowed?" but "is this a manageable risk?", because that one hands the call back to whoever owns the outcome.

The second half is her own build story, and it rhymes with the first. Computer science degree, then almost a decade without hands-on code, waiting — in her phrase — for "this magical technical co-founder" to make her ideas happen. Vibe coding ended that. We compare setups, argue about terminal versus desktop, and she explains why she sends coding work to Claude and strategy work to Codex using a classroom metaphor I've stolen since.

She closes on the cost of waiting, and she has a specific word for it: falling behind.

IN THIS EPISODE

00:00 – Why German companies move with the brakes on
02:30 – How the EU AI Act sorts risk, and what's actually high risk
05:13 – The better question: is this a manageable risk?
06:45 – The Act's first requirement is AI literacy
09:09 – The questionnaire that became REGULIGHT
11:24 – A computer science degree and a decade without code
12:32 – No more waiting for the magical technical co-founder
14:55 – From Cursor to the terminal: Alexa's setup now
23:11 – Claude, OpenAI, Gemini: the classroom metaphor
25:36 – Obsidian: the markdown vault your agent reads
38:09 – The only woman in the room

DEEP DIVE LINKS

📖 Full Article: https://pirateskills.com/insights/navigating-ai-compliance
🏴‍☠️ Vibe Coding Cologne — Wednesday, 2 Sep, STARTPLATZ Cologne: Alexa is on stage, showing REGULIGHT. Free: https://pirateskills.com/events/vibe-coding-cologne/2026-09-02
⚖️ REGULIGHT — Alexa's product: https://regulight.io
🔗 Alexa on LinkedIn: https://www.linkedin.com/in/dr-alexa-scheffler/
🗓️ All upcoming events: https://pirateskills.com/events
💬 Connect with me on LinkedIn: https://www.linkedin.com/in/bensufiani/

Gianna Hodel sells software she built by talking to Claude Code. No developer background, no course, no permission slip — and the first version was written from a converted school bus in Mexico with Starlink on the roof.

She's a freelance marketer. She got sick of copying numbers out of one marketing tool and into a spreadsheet, tried for hours to make a chatbot do it for her, failed, and decided to build the thing herself instead. That dashboard became Hebelytics, a product other people now pay a monthly subscription for.

What makes this conversation useful isn't that it worked. It's how ordinary each step was. Prompting, in her words, is just briefing — say what the problem is, what you want to see, what the outcome should look like, then give feedback. When Claude told her to connect GitHub, she asked what GitHub was, looked it up, and kept going. Hosting, backend, deployment: all learned one question at a time, in the middle of doing the work.

We also get into the part nobody puts in a founder story. Getting Google's read-only API approval, so that any customer could connect their own data, took her roughly six weeks of paperwork — including recording a video to walk the reviewers through the login flow. The code was never the hard part.

And her one regret isn't technical either: she'd have shown it to twenty people early instead of letting one or two clients be the only feedback.

IN THIS EPISODE

00:00 – It's 2026 — why am I still doing this in Excel?

01:18 – A school bus in Mexico, with Starlink on the roof

07:46 – Teaching yourself to build when nobody's teaching you

09:24 – Prompting is briefing

10:40 – Why nine out of ten go looking for a course instead

16:51 – Building the dashboard for one client

19:25 – The API paperwork nobody warns you about

24:09 – The moment a third person says "I've never seen this"

29:18 – What marketers build that developers don't

44:40 – How much do you actually need to understand?

49:45 – If you're still the one in Excel

DEEP DIVE LINKS

📖 Full article — the argument, not a recap, with every quote timestamped to this episode: https://pirateskills.com/insights/build-it-for-one
📊 Hebelytics (Gianna's product — connect your marketing tools, find the leak): https://hebelytics.de

🏴‍☠️ Vibe Coding Cologne — Wednesday 2 September, 18:30, STARTPLATZ Cologne: Gianna is on stage giving a live demo of the thing she built. She came to the last one as an attendee. Free: https://pirateskills.com/events/vibe-coding-cologne/2026-09-02

🔗 Gianna on LinkedIn: https://www.linkedin.com/in/gianna-maria-hodel/
🎧 Spotify: https://open.spotify.com/show/7kFl0BJiOYih8yqQTRR9SN
🍎 Apple Podcasts:https://podcasts.apple.com/us/podcast/build-grow-repeat/id1870561487
🗓️ All upcoming events: https://pirateskills.com/events
💬 Connect with me on LinkedIn: https://www.linkedin.com/in/bensufiani/

There's a whole level past ChatGPT, and it opens the moment you stop learning tools and start handing over tasks.

The same sentence comes up over and over at the vibe coding events I host in Cologne: I've been messing around with ChatGPT, and I'm here to learn what happens beyond. This is the answer to that sentence, recorded for exactly those people. Beginner-friendly.

The mindset shift comes first: don't think in tools, think in the tasks you repeat every week. From there it's three levels — Chat is a genuine thinking partner that has never seen your actual work. Co-Work gives an agent a folder and connectors and hands back mostly finished work. Code stops doing the task and builds the tool that does it. Same chat window every time. Nothing to relearn.

You'll see all three inside Claude and ChatGPT side by side, the connector list behind the co-work level (Attio, Gmail, Calendar, Drive, Linear, Notion, Slack, Stripe), and the real Claude Code conversations that run Pirate Skills — ads, CRM, campaigns, events, funnel, security review. Plus one starter prompt per level, and the five checkboxes that tell you whether you've hit the chat ceiling already.

Not everyone needs level three. Every business has a floor, and level two unlocks a lot on its own.


IN THIS EPISODE

00:00:00 – Beyond ChatGPT: who this is for
00:00:50 – Stop thinking in tools, start thinking in tasks
00:02:02 – Chat, Co-Work, Code: the three levels
00:02:25 – Level 1 (Chat): what it's great at, and where it runs out
00:03:53 – The ceiling test: five signs you've outgrown chat
00:05:17 – Pick one recurring task, and name your business model
00:06:44 – The same task at all three levels
00:08:45 – Level 2 (Co-Work): treat the AI like a colleague
00:11:39 – Level 3 (Code): little machines that run without you
00:16:05 – One environment, three levels — nothing to relearn
00:16:33 – AI Compass, the 7-day plan, and where to go next


DEEP DIVE LINKS

📖 Full Article (with the interactive Task Walker, the ceiling test and the 7-day plan): https://pirateskills.com/insights/beyond-chatgpt

🧭 AI Compass — Wednesday 26 August, 18:00–19:00 Berlin: free online session, once a month, same spine every time. Bring one recurring task, find your floor, and leave knowing which level you actually need: https://pirateskills.com/aicompass/2026-08-26

🎧 Spotify: https://open.spotify.com/show/7kFl0BJiOYih8yqQTRR9SN

🍎 Apple Podcasts: https://podcasts.apple.com/us/podcast/build-grow-repeat/id1870561487

🗓️ All upcoming events: https://pirateskills.com/events

💬 Connect with me on LinkedIn: https://www.linkedin.com/in/bensufiani/