DEV Community

Alessandro Rodi
Alessandro Rodi

Posted on

Mugshot Bot Acquisition: our side of the story

What an amazing story the one from Joe where he tells us how he built, scaled, and sold MugShotBot in 14 months!

Well, I thought it might be interesting as well how it happened that we decided to buy it :)

So here is our side of the story.

It all starts with Rails

I have worked on Ruby On Rails for 10 years now, and I also became the maintainer of one of the most historical gems, CanCanCan. Ruby On Rails was my bet ten years ago, when I quit my previous job, to switch from Java to Ruby, and to move from Italy to Switzerland at the same time.

Here in Switzerland 🇨🇭 I started working at Renuo, exactly because it was a Web Agency and it was working mainly with Ruby On Rails.

A few years later I bought shares of the company and became one of the three shareholders.

At Renuo we have worked with Rails for 10 years now, it's our main framework to bring our customers' ideas to life.

Meet Joe

And along this journey, I of course started following the Hotwired Dev Newsletter from Joe Masilotti and started following him on Twitter.

As a big fan of Hotwire, I also started creating the Turbo Showcase, where we train ourselves on Turbo and collect all possible components and ideas (by the way, it is open-source, so contributions are welcome!)

I already knew MugShotBot and when Joe decided to sell it, I immediately contacted him to ask a few questions.

Tweet from Joe, selling Mugshotbot

The quick decision

The nice thing about being a 20 people company with just three partners, is that you can make decisions very fast. I wrote to my partners right away and organised a meeting a few days later to discuss if we wanted to acquire MugShotBot. I sent them all the necessary information: estimated number of customers, monthly revenues, estimated price on Microacquire, technology stack. Each one of us had to answer the following questions (copy-pasted from our internal slack):

  • each one of us looks into it and makes a list of possible questions
  • each one of us also estimates “if I’d buy, I much would I pay for it”
  • we sit together 1h and compare what we have and get back to him with questions, offers, or a no

A few days later we had the meeting, which lasted way less than one hour. Main points that lead to the decision to make Joe an offer were:

  • It’s a lovely tool and a smart idea
  • We can perfectly sell this to our existing Web Agency customers. Many of them will benefit from it
  • It’s in Ruby On Rails, so we can easily maintain it and improve it. The company costs are at zero for the acquisition of a Ruby On Rails platform
  • We never acquired a SaaS before so this is going to be a very good chance to learn something

Let’s make him an offer!

The offer

I prepared a single-page offer for Joe, that was following the “no bullshit” principle that usually drives us at our daily work at Renuo. It consisted of the following parts:

  • What we offer: the price. Right up here. First information. The most important.
  • Why we want to buy: we know that selling a product is like saying goodbye to your child, so it’s important for Joe to know why we want to acquire the platform
  • What’s our plan: same as above, explain to him our plans
  • Who are we: if all the above look good, here is who we are, and what we do

We also highlighted some points that I felt could have been important, like:

  • 10% of our earnings goes to all employees
  • 10% of our earnings goes to charities and open source
  • We work and invest daily in Ruby On Rails and Open Source and sponsor different projects like cancancan or rubocop

The sale

Joe accepted our offer! It was an amazing day, on the same day I acquired MugShotBot my second child, Pietro, was born! What a day! 🤣

Me and Pietro

In a few days, we had a one-page contract ready, performed the payment to Joe, and started transferring ownership.

The process was very smooth, Joe was very professional and willing to help us in the process. The whole coordination happened through a single Google Drive document and a few Github issues.

The migration happened in just a few days, and MugShotBot had a new maintainer!

The future of MugShotBot

What will happen now? We started with very simple changes on the platform, where we updated references, email addresses, and logos to point to Renuo.

During these days we are also taking care of updating ruby, rails, and all dependencies, to their latest version. The project was already in very good shape, so this won’t take us long.

We plan to also replace turbolinks with turbo, and webpacker with esbuild. But this is all about the technical part.

We already started reaching out to our existing customers to show them the tool and make proposals about how they can use it. We plan to expand beyond blogs and aim to a wider variety of customers. Some examples?

E-commerce: we believe that an e-commerce platform will benefit a lot from being able to share rich previews of their products, including prices and discounts.

Online courses platforms: the customer likes the idea that when a course is shared, there is a full title, a small description, and the school logo.

Auction Houses: and what about sharing an item in an auction, with a nice picture and the start bidding price and the actual offer?

Escape Rooms, textures, second-hand shops, newspapers, and plugins for existing platforms! We have so many ideas! Let’s see where this will bring us.

If you are interested, have ideas or know anyone who would be interested in the upcoming changes and would like to test it out reach us at info@mugshotbot.com or over Twitter @TheMugShotBot.

Aaaand...to celebrate the acquisition, and since you read until here, we are offering the first month for free to new subscribers until the end of January! 🎉 Use the discount code JANUARY2022ONEOFF during the checkout.

Discussion (0)