Lenny's Newsletter

AUGUST 8, 2023

He realized that essentially all of the knowledge about what was working and not working was hidden inside people’s heads: ‘The CRM was showing me stuff, but it wasn’t anything meaningful. And through that, we realized that we should double down on docs and wiki. focused around just docs and wikis.

Startups 52

Startups Work Management CPO Enterprise Management 52

Lead Liaison

MAY 1, 2018

CRM: OneFocus™. CRM : OneFocus™ ™. Don’t waste your time on expensive and bloated CRMs such as Salesforce.com and Microsoft Dynamics. These platforms are great for large enterprises, but if you’re reading this article and care about growth marketing software – then you won’t be interested in those CRMs anyhow.

Enterprise Management 50

Enterprise Management Work Management Marketing Management Marketing Automation Services 50

Lead Liaison

MAY 1, 2018

CRM: OneFocus™. CRM : OneFocus™ ™. Don’t waste your time on expensive and bloated CRMs such as Salesforce.com and Microsoft Dynamics. These platforms are great for large enterprises, but if you’re reading this article and care about growth marketing software – then you won’t be interested in those CRMs anyhow.

Enterprise Management 48

Enterprise Management Work Management Marketing Management Marketing Automation Services 48

Customer Experience Matrix

JULY 28, 2009

Summary: Entiera is a sophisticated consumer marketing automation system, offered as a service and at a lower price than conventional competitors. Entiera also supports portals (with message boards, document repositories, Wikis, etc.) Entiera Insight is a marketing automation system primarily for companies that sell to consumers.

Marketing Automation Services 120

Marketing Automation Services Enterprise Management Work Management Marketing Management 120

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

GreenRope

DECEMBER 4, 2017

In the evolution of CRM, the ability to store information in a flexible, easy-to-use way is the key to a successful implementation. GreenRope already has many custom objects built into the design of our Complete CRM. Some examples of information that you would want to store about the transaction would be: Purchase price (decimal).

Wiki 40

Wiki Class CRM Purchase 40

Hubspot

OCTOBER 17, 2018

If you’re not sure where your leads are most likely to convert -- on a product page, versus a pricing page, for example -- you can use a non-intrusive exit intent popup to test different conversion points. Get started with the free HubSpot CRM to manage your sales pipeline, schedule meetings, and track emails. Leads -- they’re great!

Resources 96

Resources Lead Ranking Marketing Automation Services Lead Scoring 96

Lead Liaison

MARCH 14, 2018

You got to have a CRM. Within Lead Liaison we use a solution from atlasin, it’s called Complements, its kind of a Wiki. You know what you really want is you don’t want to have to use an email address and put that in your BCC field so that it gets stored in your CRM. We want to make sure that email goes into the CRM.

Top of Funnel 48

Top of Funnel Webinar Metrics Lead Liaison Marketing Automation Services 48

Hubspot

SEPTEMBER 13, 2012

social CRM: The word “social” here is lowercase. The single exception is specifying currency in prices; in this case, do not include the periods. wiki: Lowercase. Plural: wikis. Also applies to “due to” and “owing to” and “due to the fact that” and other, needlessly wordy ways of saying because. site map: Two words.

RSS 28

RSS Wiki Clickthrough Social Networks 28

Webbiquity

AUGUST 16, 2010

Here he outlines five ways that sales can use these tools as well, from social CRM to teaching prospects how to solve business issues. To help out, Sean Horrigan has compiled this glossary of social media terms from aggregator, blogs and crowdsourcing to thumbstream, widget and wikis. 10 Principles for B2B Sales by Better Closer.

Social Media 100

Social Media Budget Programs Social Marketing Tools 100

chiefmartech

SEPTEMBER 29, 2019

a system of record), such as your CRM, your CMS, your DAM, your CDP. As I joked in my MarTech keynote , martech decentralization is not an Oprah-esque giveaway where everybody gets their own CRM. You’ve heard of the 4 P’s of marketing, naturally: product, price, place, promotion. Call it Acronym’s Law ?).

Marketing Automation Services 92

Marketing Automation Services Work Management CMS Development Marketing Management 92