Most software founders, particularly in B2B, need to get radically better at sales. @Steli , who is the best person for explaining the scrappy stages in the beginning and then building out a team with scripts and processes, wrote a guide to:

For technical founders it is irrationally, obscenely hard to reverse years of programming (ba dum bum) that sales is a value-destroying activity. Sales is CLEARLY a value-creating activity, contingent on you have a value-creating product.
The world will not drop what they are doing to adopt your work. This is particularly true in B2B, where simply building a better mousetrap won't overcome the activation energy required to get people with additional non-mice problems to prioritize changing mousetraps today.
This is very non-obvious for founders because founders are not often people who *want* to be sold to. We often come from a background where trying out tools is a bit of a fun hobby. We like looking at all the options, making charts, and ripping out partially complete tests.
"This week I unsuccessfully trialed four software options for automating that thing that has been killing us. Our actual production process remains the same as last week. Don't worry; this was a great use of time." is not a thing you want to write in a progress report to manager.
The process of sales pushes the burden for understanding the market and distilling it from the customer to the sales person. That is a very valuable thing; it is why almost all businesses buy almost all of their big-ticket purchases (including e.g. employees) from sales.
(A candidate is absolutely doing a sales job when attempting to get hired by a company. This is one of the things that both sides of that market are frequently in denial about, but I digress.)
Simply getting oneself to be comfortable with sales (or at least present as being comfortable for a phone call or two) unlocks a crazy amount of success for founders, because founders have a few advantages over every other sales rep.
One is that they present as being almost irrationally obsessed with the market. Founders tend to live and breath the product for a few years, and it often shows, mostly in positive ways.

Unlike most sales reps, founders can credibly promise tight feedback loops for product.
Stealing a line from @asmartbear which has paid for at least a year or two of my kids' education:

"If you go with BigCo, you can call them at 3 AM. Someone will listen to you politely, explain they have no solution, and open a ticket. If you call at 3 PM, same answer."
"You can't get a useless answer from me at 3 AM in the morning. But when I'm up, your business *really is* important to me. I am the engineering team. I will push fixes so fast you will be amazed. I *will* get this right because it *actually matters* to my business that I do."
Founders have to sell.

Many, many technical founders of my acquaintance want to offload this to someone ASAP. I've never seen this work: you need to have a deep understanding of your market and customers to arm that first non-founder salesperson. It is gained by doing.
(And even if you don't do sales day-to-day anymore, you still have to sell candidates, investors, and partners on the desirability of using your company. Though most B2B SaaS CEOs that I know still very much have an account in their CRM and talk to "opportunities" frequently.)
The transition from founder-driven sales to founder-assisted sales generally starts with hiring a "maverick" sort of salesperson; someone who is comfortable extracting what you know about the market, iterating rapidly on scripts, and doing "things that don't scale" to win.
This may often be a necessary step, but it generally doesn't last for growing companies, partly because there is a crushing market undersupply of very effective mavericks.

These folks are capable of writing their own ticket and then, by construction, getting folks to buy it.
So eventually one tends to hire a VP of Sales who has done this before. They'll immediately start hiring reps under them, and start systematizing what you've learned about sales into scripts and playbooks.
You'll see this maturity model start to creep into all parts of the funnel, too, which will probably actually be written down for the first time somewhere around this stage.

Sophisticated, mature processes for marketing to pass leads over to sales for qualification.
Sophisticated, maturing processes for sales to actually physically close deals. ("What, you mean we don't just edit a few things in Word and then ask them to print, sign, scan, and send back?") Defined, scheduled startup calls, onboarding, and handover to AMs / CS aftewards.
(Sales, like many professions, benefits from specialization of labor. One that happens early is splitting the team into "account executives" (AEs) focused on getting new accounts and "account managers" (AMs), focused on keeping existing customers happy and expansion revenue.
(Some companies even split their AM teams into dedicated subteams for doing true expansion, for cross-selling products, for winning renewals, and for the generic "I want the direct contact information for someone at your company because our business must be important enough" job)
If you're at all interested in these topics, the people to read a heck out of are Steli and @jasonlk (who writes ).

Steli is so effective at sales he has closed deals he wasn't even a party to. My favorite anecdote about this:
At a previous company I had invited myself out to lunch with a software CEO, with intent to get them to sign up, but was not really sure where we were at end of lunch.

"Hey apropos of nothing: do you know Steli?"
"Oh yeah he's great."
"He is. Steli wouldn't let me leave lunch...
... until you explicitly tell me you're going to use our product."
"He wouldn't, would he."
"He wouldn't."
"OK then; we will."
"Great! Email me and we'll figure out logistics."
That is called "asking for the sale" and, while that is a very unconventional way to ask for the sale, a *ridiculous* portion of all energy expended in the art of sales is to get conversations to the point where someone has to actually say yes or no.
Relatedly: in the highly likely event that you get an answer which is not a yes or no, effective salespeople follow up until the sun goes nova waiting for either a yes or no.

More from Patrick McKenzie

More from Tech

You May Also Like

#ஆதித்தியஹ்ருதயம் ஸ்தோத்திரம்
இது சூரிய குலத்தில் உதித்த இராமபிரானுக்கு தமிழ் முனிவர் அகத்தியர் உபதேசித்ததாக வால்மீகி இராமாயணத்தில் வருகிறது. ஆதித்ய ஹ்ருதயத்தைத் தினமும் ஓதினால் பெரும் பயன் பெறலாம் என மகான்களும் ஞானிகளும் காலம் காலமாகக் கூறி வருகின்றனர். ராம-ராவண யுத்தத்தை

தேவர்களுடன் சேர்ந்து பார்க்க வந்திருந்த அகத்தியர், அப்போது போரினால் களைத்து, கவலையுடன் காணப்பட்ட ராமபிரானை அணுகி, மனிதர்களிலேயே சிறந்தவனான ராமா போரில் எந்த மந்திரத்தைப் பாராயணம் செய்தால் எல்லா பகைவர்களையும் வெல்ல முடியுமோ அந்த ரகசிய மந்திரத்தை, வேதத்தில் சொல்லப்பட்டுள்ளதை உனக்கு

நான் உபதேசிக்கிறேன், கேள் என்று கூறி உபதேசித்தார். முதல் இரு சுலோகங்கள் சூழ்நிலையை விவரிக்கின்றன. மூன்றாவது சுலோகம் அகத்தியர் இராமபிரானை விளித்துக் கூறுவதாக அமைந்திருக்கிறது. நான்காவது சுலோகம் முதல் முப்பதாம் சுலோகம் வரை ஆதித்ய ஹ்ருதயம் என்னும் நூல். முப்பத்தி ஒன்றாம் சுலோகம்

இந்தத் துதியால் மகிழ்ந்த சூரியன் இராமனை வாழ்த்துவதைக் கூறுவதாக அமைந்திருக்கிறது.
ஐந்தாவது ஸ்லோகம்:
ஸர்வ மங்கள் மாங்கல்யம் ஸர்வ பாப ப்ரநாசனம்
சிந்தா சோக ப்ரசமனம் ஆயுர் வர்த்தனம் உத்தமம்
பொருள்: இந்த அதித்ய ஹ்ருதயம் என்ற துதி மங்களங்களில் சிறந்தது, பாவங்களையும் கவலைகளையும்

குழப்பங்களையும் நீக்குவது, வாழ்நாளை நீட்டிப்பது, மிகவும் சிறந்தது. இதயத்தில் வசிக்கும் பகவானுடைய அனுக்ரகத்தை அளிப்பதாகும்.
முழு ஸ்லோக லிங்க் பொருளுடன் இங்கே உள்ளது
சூரியன் உலக இயக்கத்திற்கு மிக முக்கியமானவர். சூரிய சக்தியால்தான் ஜீவராசிகள், பயிர்கள்
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.