// Business Entrepreneurship · Consulting

The New Old Way of Doing Business

6 min read · Business
Summary 6 min read

Tech keeps reinventing ideas other fields solved long ago. Faced with filling a young agency's project pipeline, this post asks whether the entertainment industry's talent-agent model, one agency representing many people with similar skills, could work for software consultants and freelancers.

In the past couple of years I keep getting the same thought pop up in my head: “We are reinventing the wheel in tech every few months”. This thought is triggered usually by a blog post, twitter rant, or medium think piece that is being shared widely on the inter webs, and although the content is great and agreeable, I’m usually thinking to myself “But we’ve know this for the past 10 years.” or “Didn’t we learn this in CS201?” (i.e. there’s already a book written about it and it should be common knowledge if you have the basic education in the field).

For the most part, I think that the posts are good for the community because the bring something to the surface that might have been forgotten by most people, or is new to those who didn’t go through a traditional path into tech. But, there are times where I get the feeling that we are not learning from our past, as if tech has a disdain for its history, and I never see that in any other field, at least none that I am aware of. To give concrete examples, design patterns and OO are constantly re-litigated in the software community. Microservices have been introduced as a new brilliant idea, forgetting all about SOA. This is not to say that I am against any improvement or the re-adaptation of older principles, but something about rediscovering the past is odd to me, especially in a field that promotes ideas like the DRY principle and innovation.

I hope I didn’t come off as judgmental, specifically because I am about to embark on a similar journey of rediscovering an old way of doing business and trying to figure out whether it can be applied in tech. So really, I wanted to use the examples above as an invitation to dig into tech’s history for lessons that could be learned, as well as other industries and field for inspiration on thing that could be brought to tech.

One problem I have been focused on lately, is the problem of finding new work and projects for B&G. B&G is new, we haven’t built a strong reputation to the level of other agencies such that clients will come to us. So it’s very typical to be in a position where building a pipeline of projects is our focus since the survival of B&G depends on it. That’s a typical situation that is not unique to us. I’ve some really good conversations about this topic with smart people, many of whom have been solving this problem for themselves for many years. The interesting thing that I’ve come away with after all of these conversations is that each one of us is solving the same problem, dealing with the same “bugs”, ad more or less going through the same process, but each on their own. As a software developer, when I put all of this into perspective, I think of a code base where many parts of the application are repeating the same logic, violating the DRY principle, and it’s a prime use case for all that logic to be encapsulated into one class that is called in the various places where it’s needed. So if we know how to deal with this situation in terms of code, why don’t we follow the same recipe for what is called “business development”?

It’s very easy to dismiss this kind of idea. Different agencies can be competitors, or if you’re a freelancer, then you’re competing against other freelancers for work. Rubbish. Different developers have different skills and might be looking for different types of projects. Also rubbish. And many more excuses of the sorts. I think that is a very narrow and boxed in way of thinking about it. Most importantly though, it’s a limited view of the world that believes that developers are a special breed and what applies to others does not apply to us. That’s completely and utter bullshit. So the question that begs itself is whether there’s a model out there for the process of getting hired for a job on a contract basis.

In order to answer that question, let’s first examine what the components of the process are, at least the common parts of it which might be useful to identify some similarity. Here’s my list:

  • Find entity that is willing to pay for a particular skill set (in this case on a temporary/contract basis)
  • Engage said entity
  • Determine whether there’s a match (pitch/audition)
  • Make case why you not someone else
  • Close the deal and negotiate contract (payment, frequency, etc)

You might have been thinking all along that the model that we should be following is the client acquisition model. It’s a typical process that many companies follow, and you’ve probably met many people whose sole job is to follow the steps I laid out above. In fact, many consultancy are filled with “Biz Dev” folks who do nothing but this kind of work. Except, that model does not solve the problem of how you make this process work for multiple companies or people at the same time. On the contrary, it requires each individual or company to solve this problem for themselves, and I bet there’s a model out there that tackles these issues in a DRY manner.

Can you think of it yet? What if we reworded the problem to be something like this:

  • Talent (individual or group) is looking for the next opportunity
  • Entity has a need for talent to fill a role
  • Match the talent with the need
  • Negotiate terms of the deal

Does that sound familiar? To me, both processes solve the same problem but with different approaches. The second approach is akin to the “Talent Agent” approach a la entertainment industry (which includes actors, athletes, etc). The primary distinction between the two approaches is how to leverage the same resources for different entities. An agent (or agency) typically represents many individuals with similar talents, which on the surface appear to be competing for the same jobs but in practice are not because there are plenty of jobs for everyone, and not everyone is a perfect fit for the same job. In my opinion, that is the same in software consultancy. Many of you might think that this is what recruiters do, I’d argue it’s the opposite. Recruiters are payed by the companies and thus represent the companies’ best interest, whereas an agent is payed and represents the talent and negotiates on behalf of the talent.

I don’t know exactly how this could be put to practice. It’s an idea that I’m toying with right now, and it’s still in its nascent beginnings. It could be a really bad idea, or could be something worth developing. What do you think? Do you agree that is “Talent Agent” model is applicable to software consultants? Do you see this idea having potential? I’m interested to see what others think of this problem domain…

Bear & Giraffe Advisory

We partner with founders and tech leads to build sustainable Rails architecture, untangle monoliths, and scale pragmatic systems.

Schedule a Strategy Call
ESC

Type to search 38 posts