1/ Stage out the conversation

One conversation is just that: another conversation.

Land a second, and now you’re being “evaluated”.

Don’t try to jam through everything in the first convo.

Do just enough to pique their interest and land that second meeting.
2/ Do your homework

If you’re pitching a customer, use their product,

Read about the company and the person you’re talking to.

Ultimately, this proves that you will do the work to make their lives easier.

It’s so powerful yet so easily overlooked.
3/ Ask about the decision making process

Who is required to make a decision like this?

What would you need to see from me to be able to buy?

How long will it take to make a decision?

These questions give you the roadmap on how to close the deal.
4/ Don’t always demo

Sometimes it’s habit to jump straight into a demo.

If someone wants to talk first, do that.

This could consume a whole first conversation.

Which gives you a great excuse for that second meeting: going thru the demo.
5/ Don’t stick to the script

If you’re going X direction in a conversation and the customer wants to go Y direction, embrace it.

If you’re using a deck, don’t be afraid to jump around.

This is a good thing; it means the conversation is unfolding organically.

Keep it fluid.
6/ Get commitment to a decision-making timeline

“Hey customer,

There are a number of reasons why timing matters, including ability to lock in best possible prices and integration resources.

Is there a reasonable timeframe in which we can mutually agree to come to a decision?”
7/ Conscious pricing

Pricing can be scary.

The best strategy I’ve found: complete transparency.

If the customer pushes back on pricing,

Explain why your company needs to price the way it does.
8/ Always quid pro quo

If someone wants something outside of the normal bounds,

Ie better pricing, new feature commitments, etc.

Ask for something in return!

Ie Ask the customer to pre-commit to serve as a reference or case study should things go well.
9/ Don’t be dissuaded by no

Persistence pays.

Especially in the early days, I’d often email a customer 5-10 times before receiving replies.

No customer would ever be marked as Lost.

Only “Paused, Try Again Later”
10/ Try turnarounds

After a customer says no, come back creatively:

New product offerings

New pricing scheme

New ROI calculator

Anything “new” is a great excuse to re-engage.
And there we have it!

I’m going to be focusing more on practical business building tips going forward.

If you liked this, give me a follow.

LFG 🤟

More from Ryan Breslow 🕺

More from Marketing

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

https://t.co/qyl4Bt1i5x


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

https://t.co/w7oNG5KUkJ


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.