Skip to main content

Is Sales More Like Hunting or Fishing?

When you implement a customer relationship management system (CRM) for sales force automation, you must analyze your sales process in order to understand the steps that should be automated, and all the business processes that come into play during the sales cycle.



Salespeople use many analogies that are used to describe sales, but the most common are hunting and fishing.  Hunting is the most common way of thinking about sales.  Your sales prospects are targets, and you spend your time tracking them down and finding out how you can reach them.  Sales tactics are a bit like hunting weapons, and you track statistics on how many of your quarry you bag and how many get away.

You can find sales books that explain sales as hunting, and how to use 'trust as your weapon."  Large sales are called "elephants" or "whales" and small sales are "deer" or "rabbits."  In the sales as hunting world, salespeople wander the earth to find prey and stalk them as long as necessary.

Fishing (specifically angling, or fishing with a line and a hook rather than a net) is another useful analogy to understand sales processes.  In most fishing, you cannot see the fish, so you rely on your judgment of the likelihood of fish where you are casting your line, and the quality of bait.

Marketing is the bait for sales.  The quality of your offering (product or service) is crucial for sales. You must have faith in the bait or lures that you use and present them with confidence to be successful.

CRM does a great job of keeping score of sales wins and losses.  It also shows which offerings are most successful, and often helps you identify successful marketing techniques.

What analogies do you use to describe your sales process?  How can these inform your CRM implementation?  If you see your sales force as hunters, how can tracking sales activities improve performance?  Can CRM reports help you understand the tactics of individual salespeople?

Don't assume that your CRM reflects your sales philosophy out of the box.  You can tailor it so that it reinforces the processes that you want to promote.






Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ by James Townsend Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do