Skip to main content

Flexing Your Muscles

Today I had a review with Ermine Amies. Naked Element have been training the Sandler way with Ermine for some time now and reviews are an incredibly useful part of the process. We discussed a lot of aspects of Naked Element’s business in detail and Ermine offered great help and advice. As is often the case we got to talking about calling prospects (or potential clients). I don’t like calling it cold calling, because that is something which Naked Element doesn’t usually do. In most cases a prospect will be ‘warmed up’ with a LinkedIn connection and message, a brochure in the post or through meeting at a networking event.

Nobody really likes calling to speak to a prospect for the first time. Ok, so someone is going to put their hand up and say “I do! I just love talking to people.” and that’s fine, of course. Today, speaking to Ermine made me think how calling a prospect is like riding my bike to work. I don’t like doing it. The anticipation of getting on my bike can be crippling. It’s so much easier to get in the car or on the bus, but when I do do it and even more so when I do it every day for a week, I feel very good about it. I feel a sense of achievement and I’m pleased with myself.

Calling a prospect is much the same. I put it off and put it off and find almost anything else to do, but when I pluck up the courage to do it, it’s usually fine. Gatekeepers for the most part are friendly, even if they don’t put you through to who you want to speak to. There are those few calls every so often where you find yourself chatting away to a prospect like you’ve known them for years and a bond develops which may lead to work in the future.

The point I’m making? Calling prospects for the first time is like riding a bike, the more you do it, the stronger your muscles become and the easier it gets.

Comments

Popular posts from this blog

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th...

RESTful Behaviour Guide

I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as  Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resour...