Press enter to see results or esc to cancel.

Lantern Origins

Co Founders Alex Smith and David Weiser nourished LanternCRM during their time in Longhorn Startup at the University of Texas.

Previously, we spotlighted our friend Aceable and how they got from zero to where they are now. Then, we realized we haven’t done that ourselves, nor does our ‘About’ page list any background about the company, only its employees.

Where did the original idea for LanternCRM come from?

Lantern, like many startups, was born out of necessity. Alex, our founder, had decided to bypass a college career and began his entrepreneurial journey early. Being a talented developer, he did freelance work out of his father’s office. A common complaint from his father’s employees was their CRM, which was surprise…Salesforce! Their main issues were with the complex interface and having to manually log emails and phone calls (see where this is headed?). Alex decided to act as the IT manager and help them find a CRM that better suited their needs. After some searching, they found and implemented Zoho, which turned out to be a pain itself.

Finally, Alex decided to take a few weeks and crack the problem himself to build a proprietary in-house CRM which, laughably, is something we highly suggest not doing as it’s a painful and complex animal.

What were the first features of your CRM?

He released the initial version to them with much praise from the team, mainly because he listened to their needs and executed an elegant solution. It wasn’t a pretty app, as you can see below, but it was functional for the team. After that, Alex began visiting the users frequently, shadowing their daily activities to learn how they used the app and what they wanted from it; then iterating accordingly. At one point, he noticed the amount of time and number of steps it was taking for someone to search for a contact then dial their number into their landline for a simple call. He spent a few weeks hacking Google Voice and building an unapproved API to hook into the CRM. This allowed the reps to use a simple click to call a Contact vs the wasted effort to manually punch in numbers (a lot of time saved extrapolated over the course of a month).

teleforceCRM

Who supported the product once you knew it was a viable idea?

After his father’s clients and friends began inquiring about the software—at the time called TeleForce—Alex figured he might have something more than a one-off solution for his father’s company. He stumbled upon an article about the Longhorn Startup Lab taught by Josh Baer and Bob Metcalfe. As we know, Alex wasn’t a University of Texas at Austin (UT) student, but his childhood friend and former neighbor David Weiser, happened to be a current UT student. Through David, Alex, and TeleForce were accepted to the Longhorn Startup Lab and Alex relocated to Austin from Atlanta. Over the course of the semester, David and Alex learned a lot about entrepreneurship from minds who had experienced the frustration and successes first-hand.

At the end of the semester, David went back to school, and Alex continued into the Capital Factory incubator through an invitation by Josh Baer. Starting February 2013, Alex, now with market validation, entrepreneurial education, and a year CRM experience—decided to rewrite the app from scratch under a new name. Enter LanternCRM.

When did the product and team really start to grow?

For the better part of a year, Alex lived at Capital Factory. Learning via CFU classes, consuming experience and suggestions via daily 1-on-1 meetings with mentors, and spending the rest of his time coding. As Lantern slowly grew organically, picking up users here and there, Alex continued to focus one hundred percent of his time on the product. David checked in on him every now and again, eventually realizing there was a lacking in sales and customer support. David took it upon himself to act as the customer facing side of Lantern for sales inquiries and customer issues. Months later, thanks to consistent meetings with CF mentors, Alex raised the first part of his angel round at $250k which allowed Lantern to grow from 1 to 4. David and myself (Chad) came onboard in late January, and Andrew joined the team shortly afterward.

Since the forming of the four-horsemen of Lantern, app functionality, stability and awareness has grown by leaps and bounds. We’ve been heartily pushing the flywheel with all our might and it is now beginning to pay off with consistent trial signups and a fairly stable close rate.

Lessons to be learned from Lantern

  • Build from a real use case. Don’t build something you think someone will want, build something people need.
  • Once your initial version is released, be prepared to listen to feedback, iterating the product based on customer needs. Software is never finished.
  • Andrew Chan
  • Michael Clay

    A word on your second bullet point. I have gone through your blog and noticed something curious. In all but a few blogs, you have shut off your comments. That’s not listening to feedback, that is stifling feedback. I don’t know if you have received too many spam comments, have another mechanism for feedback or don’t take criticism (potential) well, but there are many things that I agreed with and could add valuable insight to the discussion, but there wasn’t one. There wasn’t a chance to have one. If you have another way to provide feedback (other than in-app. That makes it necessary to sign up just to comment, skewing your signup numbers (or they just won’t bother)) it should be stated. People are used to being able to comment right where the post is and shutting it off just sends the wrong message. Information is a flow and it goes both ways. I appreciate the content and experience you share in your blogs and I can’t even tell you! 🙂

    A fellow Austinite

  • http://www.chadsakonchick.com/ Chad

    @Michael – There is an open ticket with Disqus that they haven’t responded to yet about this very topic. I’ve reached out to them several times asking why some posts have comments enabled and some don’t. I would love to have all the comments! In this case, Disqus is #fail