Sales Vibe Coding
The Definitive Guide for Sales People to Learn Vibe Coding
Vibe coding for sales people is what happens when reps use AI to turn customer pain into something concrete fast. Goal: sales to become PMs and devs. What the f—-: why? I gotta hit quota man! Have you seen the job market out here? Is this one of those fads? No. Here's why you should keep reading.
The number 1 reason top reps lose deals is lack of features. This was true before AI. Before AI, you couldn’t do a damn thing about that. Now you can.
TL;DR
Vibe coding for sales people helps reps move faster from customer pain to something the team can see, share, and act on. The point is not to become a full-time engineer; it is to use AI to prototype, clarify, and prove what a buyer really needs.
Why keep reading
Why vibe coding for sales people matters
#1: You want to make money. If the buyer needs a feature and you cannot do anything about it, you lose leverage. AI changes that. It gives you a way to show something, validate something, or at least make the customer feel heard before the deal dies.
#2: You want to keep making money. Future proof your career. The secret with AI is that it makes you better at other jobs, not just your own. That matters because the reps who can translate a buyer need into a prototype or a crisp product case are harder to replace.
#3: It's so much damn fun, it's literally addicting. Creating is fun. People who used to code say the reward cycle is back, only faster. If you have spent years in a role where you mostly explain problems you cannot solve, building something is a different kind of brain chemistry.
AI 201 for Sales Reps
Think of this as AI 201 for sales reps
I assume you are already using ChatGPT, AI in your existing products, and maybe even Claude or Codex. That's covered in the 101 course that everyone has created. This is the next level. If you get through these projects, you can do anything except coordinate multiple AI agents working well autonomously. I haven't figured that one out yet.
The whole point is to move from consumer of AI output to operator of AI workflows. That means building tiny things, understanding what they do, and reusing the same muscles in customer conversations.
Rules guiding us
Rules guiding us and my promise to you
No bullshit: I will only walk through the things I do and that work for me. Other things make work for other people, but they don't for me.
Practical: theory will sometimes come in, but this will mostly be lessons and ideas you can use right now.
Swearing: I will swear. If you do not like it, let me know, I'll try to do it less.
Perfect is the enemy of good
You will lose 90% of your time on 10% of the task. So stop at 90 percent. Practically, only go three prompts deep.
Don't be afraid of code
It's just words, man. You can cold call thousands of strangers. You can read the code that tells a computer what to do.
Come with a problem to solve
Before you start, know exactly what problem you want to solve and what success looks like. AI will always want to push you further.
Transparency
Conflicts and transparency stuff
I have no paid deals with anyone or anything. Arkweaver is my company, and I will mention it. This problem and you are why I'm building Arkweaver.
That matters because the whole reason this page exists is not to pretend sales reps should become engineers overnight. It is to show that the wall between selling and building got thinner, and the revenue consequences are real.
Program
What we will cover in this program
Step 1
AI to make you better at your sales job.
Potential gains: eh, 10 percent. You are already pretty good at it.
Step 2
AI to make you better at other jobs…which will make you close more deals.
Potential gains: massive, maybe 50 percent.
Question you may ask: We have programs that do this AI stuff, why am I building my own? AI, more than anything, is learning by doing. You cannot take a course, it will be outdated within a month. The only thing you can do is do.
Question 2 you may ask: is this just AI slop? Your GD right some of it is! My fingers hurt. I got kids and a company to run so I will use AI sometimes.
Things to download
Things to download
Here are the things I use. If you want to use Claude Cowork or whatever that's fine. But do not over think this, you will get AI Fomo.
- Cursor: this is how you write and, more important, view code.
- Add Claude or Codex in the right side. If your computer is slow, yes, these things use a lot of memory.
Lesson 1
How to use AI to make you a better sales person
I want to start you with something to get you over your fear.
Open Cursor
Go to Codex or Claude on the right side.
Ask it to build a simple app
Build me an app where I can enter how many calls I made and emails sent and then give me a pie chart where it will show how I spent my day.
Ask how to run it
In Cursor, click Terminal in the top toolbar. The terminal is where you tell your computer to do things in computer speak.
Add one feature
Play with the app. Add a log of each day's activities. Then change one word in the code and save it. Then look at your app. It changed.
GitHub and Vercel
How to push code up to GitHub and share it
Type to Codex or Claude: how do I add this to GitHub? assume I'm a complete novice. If it gives you a wall of text, don't be intimidated. That's what happened to me, so I replied, "Whoa way too hard, can you do it for me."
It will walk you through some steps. You will have to create a GitHub account. Do it. Conquer your fear. It means more money.
Then sign up for Vercel. Connect the GitHub you created. It will create a link for your app. Now other people can actually use your work.
Sales use cases
Let's make you a better sales person with AI
There are a ton of LinkedIn posts with best practices for this and I've tried damn near all of them. Here's my experience. Not to call out these companies because other people get a lot of use out of them. Could be the user, i.e. me, who messed up.
Clay
Very high learning curve. I spent multiple days on it only to find out mass cold emails don't get replies.
N8N
Automation platform for connecting agents. Same issue. Don't waste your time if you aren't a developer yet.
Dripify
Good product, but I got nothing except a really messy LinkedIn that I needed to clean up.
Call Recording
Lightfield and Gong. If they are any good, they are the best use of AI.
Sales emails
How best to use AI for sales emails
What works for me:
- Follow-up post meeting from a transcript: “Write a follow-up email to them, short and sweet.”
- Prep for second meeting with person: “What did I talk about last time with this person?”
- Trying some ideas out cold emails with people, titles, companies, and a subject line.
- Email finding and enrichment waterfall: that is Clay's bread and butter.
What doesn't work:
- 90+ percent of cold email personalization.
- The 10 percent that does work is if you have a personal connection. Build a rules document and refer to it every time.
Customer research
AI uses for customer research
What works for me:
- Macro and complex research of a company: tell me the latest earnings and the main problems mentioned in earnings calls.
What doesn't work for me:
- Personalized research on a person. I find it's too rough around the edges.
AI uses for LinkedIn outreach
What works for me:
- LinkedIn posts from transcripts. They perform better. I usually edit the shit out of them though.
What doesn't work for me:
- LinkedIn automation. I have ceased trying because it is hard and can get you banned.
Note: I have never found full email, LinkedIn, sms message automation to work for sales outreach. That may just be my bias, but I have wasted dozens of hours trying to crack this and nothing.
Project
Building LinkedIn automation that will work for sales people
Goal: I like to follow up with people on their LinkedIn after I've emailed them. It's the red billboard theory of making sure they see you many times. I don't trust a machine to do it.
What my automation does: it looks at who I emailed yesterday, looks at a spreadsheet of all the people I'm targeting, creates a webpage with their profiles and recent activity, and opens it for me so I can comment where relevant.
Gmail metadata
How to connect Gmail metadata to your vibe coded app
This is advanced. It involves API keys, which is where this stuff gets intimidating. But if you stick with it, it unlocks lots of workflows.
- Go to Google Cloud Console and create a new project.
- Enable Gmail API and Google Sheets API.
- Set up OAuth consent and create a desktop OAuth client.
- Generate a refresh token with Gmail metadata and Sheets scopes.
- Add credentials to your .env and verify access.
Side note: this will need access to Gmail metadata. I will not let it read all my email. Metadata shows who I send to, but not the email content.
Advance
How a sales person should use AI to become good at other roles
This is where the massive gains are. If you are reading this, you are probably a pretty good sales person. So anything to optimize your existing sales will have marginal impact because you have already done a lot of it.
The goal isn't to make you a good Product Manager or Developer. It's to make you an average one. That will go incredibly far and it's exactly what AI is good at.
Prototype features
How a Sales Person Can Become a Product Manager and Developer
The #1 reason you are losing a deal is lack of features. What does that mean in practice? How do you solve it? You need to nail what the customer is asking for and convince engineers that it is worthwhile to build now.
This is what a product manager does. You can do that now.
Step 1: take a screenshot of your product and ask Codex to recreate it as an HTML front end with fake data. Step 2: look at the differences. The icons are probably a little different or missing. The order isn't 100 percent correct.
That is why a prototype is only step one. If you send this to an engineer, they need to know exactly which parts you meant to change, which were AI mess ups, and which AI changed with you.
Arkweaver exists because this exact gap is the problem: sales hears the feature, product needs the request in product language, and engineering needs something precise enough to build.
Ask questions like a product manager. What problem does this help you solve? It will be hard to convince my team, but if we build this will you sign? Do any of our competitors do this?
Then make a case to your eng/product with this product we created. Try to find 2 other customers who want this.
Level of effort
A word on level of effort
How valuable a feature is matters. The other thing that matters is how hard it is to achieve that feature. The benefit of building a feature yourself is that you get a pretty good idea how hard it is to build.
Keep an eye on how many files were changed. That's a decent proxy for complexity. Most importantly, your eng team will be able to see the complexity of the feature.
PM questions
Ask questions like a Product Manager
What problem does this help you solve?
It forces the conversation out of feature request land and into business value.
Will you sign if we build this?
If they can make that decision, now you know whether the issue is real buying pressure.
Do any competitors do this?
That question tells you whether the buyer is asking for preference or parity.
Management
How a Sales Person can Become a Manager with AI
"I want to be a manager, I just need the chance man!" Manage yourself. No seriously. Upload your sales transcripts every time and have ChatGPT give you a grade.
Create criteria to judge yourself. Did you follow your methodology? Did you ask the right questions? How likely is the customer to close? Then get better every call.
AI is never satiated. Don't think of it like a game with a clock that you can win. It's a game that keeps changing the rules. Use it, don't let it use you.
Conclusion
What this is really about
Look, I'm not here to tell you that typing a few prompts into a chat box is going to turn you into Mark Zuckerberg. That is the kind of AI slop the gurus are peddling.
What I am telling you is that the wall between "I sell the thing" and "I build the thing" has been knocked down to a hurdle. If you're tired of losing deals because your product is missing a button, or if you're terrified that a GPT-wrapper is coming for your commission, there is only one move: start doing.
Build a shitty app. Break the terminal. Get your hands dirty with some code. Once you realize that code is just words and AI is just a tool to help you arrange them, you stop being a salesperson and start being a creator.
FAQ
Frequently asked questions
What is vibe coding for sales reps?
It is using AI coding tools to create simple, useful artifacts that help a rep sell, learn, or prove a feature request.
Do I need to be technical?
No. You need enough confidence to describe the problem clearly and enough patience to iterate three prompts deep.
Why not just use a demo tool?
Because most demo tools show what already exists. This page is about what happens when the buyer asks for what does not exist yet.
What should I build first?
Build something tiny and useful: a call tracker, a day summary app, or a prototype of a requested feature.
How does this connect to Arkweaver?
Arkweaver is the bridge between the customer request and the codebase, so the feature does not get lost in translation.
What is the real end goal?
The goal is not to turn every rep into a developer. It is to make them dangerous enough to move a deal forward with proof.
Why Arkweaver exists
Stop saying "it's on the roadmap"
Arkweaver connects to your existing codebase and lets you create features and share them. It happens fast enough to show a customer live on a demo, and it keeps the customer context attached to the request.
That means you can stop saying “it’s on the roadmap” and start showing something real.