Growth Hacking Within the Setting of a Fortune 500 Company

In the startup community, growth hacking tactics are often a key to massive growth in a short amount of time. This is vital in a community where innovation consistently outpaces development, funding runs out fast and products are easily scalable. In this rush to get users, startup companies are finding ways to scale quickly and efficiently, leaving bigger companies unable to keep pace. This thesis examines how Fortune 500 companies can utilize growth hacking in order to mimic the successes found by startups using these techniques. When large companies implement growth hacking tactics, there are two primary models they can follow. The first is an acquisition model, where companies acquire a startup that has already implemented growth hacking tactics successfully. In this model, the startup, despite being acquired, remains autonomous from the core company and is largely allowed to continue in its efforts to grow without the strain and rules of corporate culture. The second model is an internal implementation model. In this model, the company attempts to create an "internal startup" that lives within the parameters of the company's culture and rules. The company then tries to discover and implement the best-suited growth hacking tactics themselves. At the moment, there are several instances of Fortune 500 companies implementing both models. It is important that companies experiment in implementing these tactics as one way to stay relevant and keep up with the ever changing and innovating market. In this thesis, I will attempt to implement growth hacking through MakerSource, an internal project started by Avnet, Inc. I will compare the results of the growth hacking tactics implemented within MakerSource with those implemented by Hackster.io, a startup recently acquired by Avnet, Inc. In each program a variety of push, pull and product tactics were to be implemented. While Hackster.io achieved success with their growth hacking following the acquisition model, MakerSource, following the internal implementation model saw less success.