BC TECH
Saved by @zmbnski

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 https://t.co/7FpEMvXdLZ ).

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

Patrick McKenzie
Patrick McKenzie
@patio11
The payments wars in Japan are heating up and one of the battlegrounds is convenience store coffee.

“Coffee? What does that have to do with payments?” I’m glad you asked.

Convenience stores are low net margin businesses, which sell some high gross margin goods/services but a lot of low ones, and have high fixed costs and a low ticket size. The typical transaction is under 500 yen ($5) and many are about $1.

They need repeat custom.

A few years ago, all of the chains had a good idea for increasing frequency of use: make a minor capital investment in automatic coffee machines. Sell access to them for the price of a cup / ice; customers self-serve with the machine.

The price point is $1 to about $2.

Coffee quickly became one of the most frequently repurchased items at convenience stores, in no small part because it’s the one thing they can sell which is phameceutically habit forming but totally unregulated. (Just telling it like it is.)

But the coffee is not very defensible

The problem, such that it is, is that competing chains are everywhere and *all* of them serve Thoroughly Adequate Coffee at similar prices, so you’re back into the brutal economics of “Who is 3 meters closer to 40 customers at 1 office?”

Enter payment apps.
FINANCE
Patrick McKenzie
Patrick McKenzie
@patio11
If an employer is willing to be abusive to you prior to hiring you, when you have maximum leverage and they are maximally incentivized to play nice, I think that gives you *extremely actionable* signal as to how they'll treat you when you're working there and dependent on them.

For candidates: evaluate prospective employers accordingly.

For startups employing e.g. engineers: given that your candidates should evaluate you accordingly, be *extra special* careful to operate like professionals with regards to e.g. interviewing, offers, and negotiation.

"Can you be more explicit about 'abusive' here?"

Not without violating a confidence, but as someone who has been on hiring side of table and is a capitalist, there are *clearly* things you could do which would be "sharp operating, but we're all sharp operators" in some contexts.

Hiring employees is often not one of those contexts. The nature of the relationship, the asymmetry in power, and the social contract strongly counsel you to be a lot better there than you are minimally required by law / contract.

A thing which aesthetically frustrates me is that a lot of the things I've heard companies do here serve *no legitimate business purpose.* In some cases it's getting tens of dollars of advantage. TENS! On an engineering candidate!
ALL
Advertisement
Patrick McKenzie
Patrick McKenzie
@patio11
A thing which I unironically and enthusiastically believe which is unpopular among smart people of my acquaintance: financial engineering has in the recent past and present contributed substantially to human welfare. We should hope to see more of it.

Maybe more geeks need to meet someone who says “My job is teleporting value across time and space.”

Financial engineering is sort of a squishy term. I don’t primarily mean payments infrastructure or financial rails, although both of those involve substantial engineering.

I mean more “We took a thing and performed some alchemy, and now have a new thing.”

Except instead of alchemy it is generally quite a bit of math, a huge amount of contract law and due diligence, often an impressive amount of ops work, and a dusting of technology that web devs would recognize as such.
ALL
Patrick McKenzie
Patrick McKenzie
@patio11
There are a *lot* of software shops in the world that would far rather have one more technical dependency than they'd like to pay for one of their 20 engineers to become the company's SPOF expert on the joys of e.g. HTTP file uploads, CSV parsing bugs, PDF generation, etc.


Every year at MicroConf I get surprised-not-surprised by the number of people I meet who are running "Does one thing reasonably well, ranks well for it, pulls down a full-time dev salary" out of a fun side project which obviates a frequent 1~5 engineer-day sprint horizontally.

"Who is the prototypical client here?"

A consulting shop delivering a $X00k engagement for an internal system, a SaaS company doing something custom for a large client or internally facing or deeply non-core to their business, etc.

(I feel like many of these businesses are good answers to the "how would you monetize OSS to make it sustainable?" fashion, since they often wrap a core OSS offering in the assorted infrastructure which makes it easily consumable.)

"But don't the customers get subscription fatigue?"

I think subscription fatigue is far more reported by people who are embarrassed to charge money for software than it is experienced by for-profit businesses, who don't seem to have gotten pay-biweekly-for-services fatigue.
STARTUPS
Patrick McKenzie
Patrick McKenzie
@patio11
This lunch is 500 yen ($4.80) at Sukiya, a Japanese fast food restaurant which belongs to a category with about three big competitors.

I love the aesthetics of this category and they’re under remarked upon.


I think people underestimate QSRs in terms of social utility, but Sukiya et al describe themselves as mission-oriented enterprises. I believe this is largely sincere, and goes back to the 60s and 70s, when the clientele was primarily manual laborers who had migrated to work.

Japan was not a rich nation at the time, and day laborers in particular were both unlikely to be able to cook for themselves and unlikely to have much of a food budget, and so the chains sprung up offering an honest-to-goodness cooked meal delivered in under a minute for cheap.

This heritage continued over the years, even after Japan became a much more wealthy nation, and these chains function as social support and dignity for folks in diminished circumstances.

They also are a wee bit of a cartel, and I appreciate the aesthetics of the cartel:

Back when I was first in Japan, in the mid 2000s, there was an increase in the price of beef.

And the heads of the three chains got together, and decided that the price of the basic beef bowl needed to increase, but given the economic circumstances how could they hold the line.
FOOD

More from Tech

Loren Brichter
Loren Brichter
@lorenb
So it turns out that Google Chrome was making everything on my computer slow *even when it wasn’t running*, because it installs something called Keystone which is basically malware.

I made a website because this shouldn’t

Wired first reported on how bad Keystone was 11 years ago when they put it into Google Earth (they seem to put it in all their popular

The fact that Keystone hides itself in Activity Monitor is bizarre. (The only sign of it was excessive CPU usage of WindowServer which is a system process).

I don’t know if Google was doing something nefarious with Keystone, or a third party figured out how to (which Wired warned about). But either way, I’m not inclined to give Google-the-organization the benefit of the doubt (despite the many good people who work on Chrome)...

...since it's been a decade+ and this still hasn't been "fixed".

There is no reason for auto-update software to need to do what Chrome/Keystone was doing. It also has a long history of crashing Macs.
TECH
Luca Hammer
Luca Hammer
@luca
Two years ago on a weekend, I built a tool to make it easier to evaluate Twitter accounts. Since then 36590 people used it to analyze 55390 different Twitter accounts.

Over the last months @mmkaradeniz and I made a new version. We launched it last night:

@accountanalysis doesn't use machine learning or AI „magic“. Instead of telling users if an account is authentic or not, it helps them to evaluate the accounts themselves.

It visualizes the different features (date, time, type, app, etc.) of Tweets to make them interpretable. /1

@accountanalysis The core concept is still the same, but it looks much better and is easier to operate. Not only for the users, but us developers as well. Enabling us to continuously roll out new features in the future.

Side-by-side screenshots of the old and new version. /2


@accountanalysis Some people had questions what different charts displayed and how they could be interpreted. There are now explanations for all charts, that can be toggled on and off at any time. /3


@accountanalysis The selected/retrieved Tweet count moved to the top to make it clear that not all Tweets of an account are analyzed. 3200 is the API limit by Twitter. It's possible to get more through the Premium API, but I don't think people would pay $100+ for the analysis of one account. /4
TECH
Advertisement
Jared Spool
Jared Spool
@jmspool
A common misunderstanding about Agile and “Big Design Up Front”:

There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.

You’re allowed to think about a desired outcome from the beginning.

It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.

It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.

It’s not BDUF if you help every team member know what success looks like.

Agile is about reducing risk.

It’s not Agile if you increase risk by starting your sprints with complete ignorance.

It’s not Agile if you don’t research.

Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.

It would be a mistake to assume this research should only be done by designers and researchers.

Product management and developers also need to be out with the team, conducting the research.

Shared Understanding is the key objective


Big Design Up Front is a thing to avoid.

Defining all the functionality before coding is BDUF.

Drawing every screen and every pixel is BDUF.

Promising functionality (or delivery dates) to customers before development starts is BDUF.

These things shouldn’t happen in Agile.
TECH
Tagir Valeev
Tagir Valeev
@tagir_valeev
Ever wondered how the JVM debugger 'Evaluate' feature works in IDEs? Long ago I thought that the Java debug interface (JDI) actually allows you to specify the expression and get back its value.


However, this is not quite possible: there's no Java language compiler inside the JVM. When the process is paused JDI allows you to read or write any variables and fields or even execute an existing method with given arguments. But nothing like addition or multiplication.

On the other hand, #IntelliJIDEA debugger allows you to evaluate even statements! You can write there `for`, `if`, `while`, `switch` - whatever. You can even declare local variables. So how this works?


The answer is simple: IDEA debugger has a built-in interpreter for Java! If you access an existing variable or a field, call a method or instantiate an object, it queries JDI. Otherwise, IDE itself does all the calculations.

The amusing thing is that debugger authors didn't bother to make it as strict as Java itself, so the language inside the interpreter is a much more permissive version of Java. For example, you don't need to initialize variables there! Default values like 0 are used automatically.
TECH
Trung Phan \U0001f1e8\U0001f1e6
Trung Phan 🇨🇦...
@TrungTPhan
For decades, Jeff Bezos shunned ads.

But now, Amazon’s ad business is huge: it’s on a $30B+ annual run rate (more than 2x the combined sales of Twitter, Snap and Pinterest).

Here’s how it happened 🧵


1/ Amazon doesn’t break out its ad business separately in financial filings. However, most analyst believe ads make up the majority of its “Other” revenue segment.

This figure has exploded from $1B in 2015 to a current annual run rate of ~$32B.


2/ In 2009, Bezos said “ads are the price you pay for a crappy product”.

But the business is so lucrative that Amazon’s interface has been swamped with ads:

◻️ First 3-7 search results (left in red)
◻️ Most of the product page (right in blue)


3/ Prior to the rise of ads, Amazon set out to build the ultimate organic customer recommendations engine.

The approach was codified in a famed 2003 research paper: “Amazon Recommendations: Item-to-Item Collaborative Filtering.”


4/ In recent years, Amazon organic recommendations:

◻️"Customers who bought this also bought this"
◻️"Customers who viewed also viewed"

Have been replaced w/ ads:

◻️ "Sponsored products related to"
◻️ "Brands related to this category"
TECH

You May Also Like

Homestays & Villas
Homestays & Villas
@thehomestays
Best resort on the Ganga at Rishikesh
TRAVEL , TRAVELINDIA , PLACES 2TRAVEL
Novid Houellebecq (That's Hollaback)
Novid Houellebecq (Tha...
@GarouGothic
Ok, here is a thread for you.
What happens when you have:
Netflix
Apple
Amazon
WarnerMedia +
Disney+
SonyCrackle (Reboot)
Verizon All Access (after they buy CBS/Viacom)
UniversalSkyMedia
By 2021
Answer? Internet Slows To A Craw and Dies.
Why?
Bandwidth.

Netflix's gets 35% of all internet traffic.
Now we all know Apple Coming to Netflix Corner.
We know that WarnerMedia Planning One
We Know about Disney+
Now how will the net handle 8 Streaming Platforms all at once?
Answer - IT CANT.

But Novid, the speed, the 4K the all everything?
NOOOOO BUDDY.
Even if you could do it and even if AWS ran six million clouds, The Net Will still slow to a crawl. 35%, goes to nearly 90% if any of the 8 or all of the 8 eat at netflix's numbers.

Oh, they wouldn't be running at once.
FOOL. You forget how bad things were when game of thrones season premieres came around. HBO SERVERS FALL DOWN GO BOOM!

Now see if a season like 2021 come around and they air shows on a same day. It gets crazy. AT&T and others gonna realize they cant build out forever. Something will give and it might be your entertainment consumption big time.
TECH
Advertisement
Jaya_Upadhyaya
Jaya_Upadhyaya
@Jayalko1
WEAPONS OF MAHADEV

Sarvaripati Shiva is one of the most fearsome manifestations of Mahadev. Assigned with destroying all of the universes at the end of time, Shiva is one of the most fearsome warriors. He is the Mrityunjaya.
Here are some weapons associated with him:


TRISHULA: the 3 pointed blades denote creation, maintenance, and destruction or the 3 Kalas – Past, Present and Future. They also represent 3 Gunas – Sattva, Rajas and Tamas).
Shiva’s trishul can only be stopped by Shiva himself.
@onlyonenetra @DetheEsha


Trishul is also said to represent Ida, Pingala, and Sushumna. These are the three basic nadis – the left, the right and the central – in the pranamaya kosha, or the energy body of the human system.
@iamkamyabuch @unever_followme


PARASHU: axe with 4 cutting edges which Shiva gave to Parashurama. In his anger, Parashurama used the parashu to get rid of the all the Earth’s tyrannical kshatriya caste twenty-one times over.
@harshasherni


CHANDRAHASA SWORD: The divine sword Chandrahasa literally means ‘the laughter of the moon’. Ravana gave this sword to Indrajit on different occasions especially to fight against Devas.
GIRISH: A special sword of Shiva with unique characteristics.
ALL
Andrew Chen
Andrew Chen
@andrewchen
👇Thread.

Published a new essay: The red flags and magic numbers that investors look for in your startup’s metrics – 80 slide deck included!


This was a deck that I created on my (longish) interview process with @a16z. It was a long path, starting with meeting folks at the firm 10 years ago. But the purpose of the deck was to explain how I would use my superpower in an investing context

Here's what I explain in the deck. As investors (whether angel or VC) we're often confronted with an up-and-to-the-right graph. Is it going to go up? Or down?


One solution to forecast these growth curves is the Growth Accounting Framework, where you add up New+Reactivated and subtract churned users. In each time period that gives you the difference in monthly actives.


The problem with this is that it's a lagging metric, not a leading one. We need to go one level deeper and look at the underlying loops that drive these numbers, to understand the quality.
STARTUPS
Noah Smith
Noah Smith
@Noahpinion
Met a Brazilian-American Lyft driver from San Diego who passionately attacked the racism of Republicans, then switched to passionately defending Bolsonaro.

If I were Thomas Friedman, I could tell you what this means.

Met a Haitian-American in a restaurant who said he'd always vote for Democrats because of the immigration issue, but that he has conservative beliefs too. "I don't want to pay for someone's abortion!", he declared.

Met a Latino Lyft driver from San Jose who said that while he was liberal, California was getting too liberal for him and he was considering moving to San Antonio.

Again, not being Tom Friedman, I am unable to offer any commentary on the political and policy implications of these conversations.

I guess my only thought is that political opinions are pretty complex and multidimensional, out there in the real world.

(end)
POLITICS