18
19 Comments

I bootstrapped projects for 8 years and recently raised $2.75M in VC funding. AMA!

Back in 2011 I was the 2nd product manager at Twilio. I left at the end of 2012 after two years, and instead of joining Stripe I decided to move back to Chicago and self-fund my own product ideas while doing product design consulting.

After 8 years of self-funding my own projects, my cofounder Benedict and I decided our newest business Arrows.to (started in 2019) needed VC funding.

We got a term sheet the first day we had formal meetings with investors, from Gradient Ventures (Google’s AI focused venture firm), and then I spent the following month getting 48 really awesome angel investors on board.

As of yesterday we are now 7 total team members after being just the 2 of us at the start of June.

My cofounder and I record a 10-15 minute podcast every week about what we’re doing, thinking about, and experiencing in relative real-time. We hope it’s an artifact as we build a great company: https://arrows.to/keep-going/

Otherwise, we have lots of thoughts about iterating on ideas, doing customer research, getting preorders, pricing, marketing strategy, and more. AMA! 💘🥳
—-

Our funding press: https://techcrunch.com/2021/06/29/arrows-raises-2-75m-to-build-out-its-customer-onboarding-software/

A full list of our angel investors (48!): https://arrows.to/resources/arrows-seed-funding/

on August 17, 2021
  1. 4

    Hi Daniel! Arrows.to looks great!

    As code becomes commoditized and SaaS companies will try to build moats around user experience, brand and personalized services, it seems that personalized onboarding will be quite lucrative. Could you elaborate on your thesis behind Arrows and how you view the future of SaaS?

    What were your reasons for taking funding after 8 years of self-funding? Did you figure out growth and need funds for scaling?

    Since you mentioned that you:

    have lots of thoughts about iterating on ideas, doing customer research, getting preorders, pricing, marketing strategy

    could you share the most surprising insights you learned along the way in all of those areas? :)

    1. 4

      Hey @psto! Thanks for the question. I replied to someone else about the funding question in why we decided the Arrows company specifically needed funding, but I'll add a little extra:

      One thing I found as an "indie hacker"/bootstrapper/self-funder myself for many years was that much of my identity as a builder was wrapped up in that. I didn't actually have a problem with VC funding, but I found myself really having a difficult time with it. And I feel ultimately that it was a self-limiting belief at that time in my life.

      However, I have zero regrets and am happy with how I've built things. They all helped set us up to be able to go after this opportunity now.

      ---

      The most surprising insight that we had really came around researching what problem to solve. Simply put: all work that people do at companies is like plumbing. It's a series of workflows, inputs and outputs, pipes that connect.

      So to understand what problems someone has, you need to step through everything they actually do so you can understand where the headaches and inefficiencies are. Then when you build your product that solves one part of that workflow, you also understand the nuanced details of the steps that come before and after that part of the workflow... When we talk to customers, we really try to dig into what happens around the work they're doing in Arrows so we can better understand how to help them do the work inside Arrows.

      I started to write about it here and hope to add to the series: http://arrows.to/resources/building-arrows/working-in-bets/

      1. 4

        One thing I found as an "indie hacker"/bootstrapper/self-funder myself for many years was that much of my identity as a builder was wrapped up in that. I didn't actually have a problem with VC funding, but I found myself really having a difficult time with it. And I feel ultimately that it was a self-limiting belief at that time in my life.

        There is also an unnecessary stigma when indie hackers take VC funding as if it was a betrayal. It's just a tool. Good for you!

        all work that people do at companies is like plumbing. It's a series of workflows, inputs and outputs, pipes that connect. So to understand what problems someone has, you need to step through everything they actually do so you can understand where the headaches and inefficiencies are.

        I love this! It's like "on the ground" systems thinking.

        I started to write about it here and hope to add to the series: http://arrows.to/resources/building-arrows/working-in-bets/

        That's a great application of Annie Duke's Thinking in Bets. "Resulting" based thinking rots companies from the inside. I subscribed for the rest of the series!

        Thank you for all the insightful answers, Daniel! You missed one of my questions that I was the most curious about 😉 I'd be grateful if you find the time to answer it!

        As code becomes commoditized and SaaS companies will try to build moats around user experience, brand and personalized services, it seems that personalized onboarding will be quite lucrative. Could you elaborate on your thesis behind Arrows and how you view the future of SaaS?

        1. 4

          Definitely! I totally missed that part @psto! There’s a few things to our thesis behind Arrows.

          1. Subscription business models require having customer stick around for a long time, so retention is critical. Similarly, expansion revenue is a major focus for the best SaaS companies these days. We believe that the seeds of a happy, fast growing customer who will stick around for the long-term are planted from day 1 during onboarding. If your customer never properly adopts or rolls out your software to their company, how can they ever be a happy user? So the faster and more successfully your customers are onboarded, the happier they are and more likely they are to use your product deeply.

          2. We believe: Onboarding Never Ends. Onboarding isn’t something you do just in the first month of someone being a customer, you do it throughout the entire customer lifecycle as their goals change, as new team members come on board, as your product evolves and becomes more powerful, etc. There are consistent new opportunities to “onboard” your customer, and Arrows is specifically built with that in mind.

          3. We believe onboarding isn’t about learning the UI of your software (tooltips and product guides like AppCues, etc can do that just fine). We believe onboarding is about helping customers go through the organizational change required to reach the outcomes they have in mind for the product they purchased.

          Arrows is solely focused on helping your customers go from Point A (I want this outcome) to Point B (We’ve achieved this outcome), and your software is just part of that process. But customer success teams are the critical backbone to enabling this, and we believe our software can augment them delivering a better experience to customers.

          1. 3

            Thank you for a comprehensive answer, Daniel!

            I love how your thesis is around creating outcomes for your customer's customers (creating a win-win-win).

            Great to see a holistic approach to a never-ending onboarding with new updates, goals, phases of customer lifecycle etc.

            I'll keep Arrows in mind for my next project!

  2. 2

    After 8 years of self-funding, my cofounder Benedict and I decided our business Arrows.to needed funding.

    Why?

    1. 1

      Hey @dqmonn ;-)

      We recorded an episode of the podcast about this (the one about raising funding): http://arrows.to/keep-going/

      But the simple answer is: we realized the product category we're in and the customers we're serving necessitated us having funding.

      Our customers and sales prospects have really high expectations of what the product can do, and it was not a great signal when the founder was the one doing sales calls (which is often the case as a boostrapped company). Many companies don't want to buy important customer-facing, revenue-driving tools from two dudes who might not be around in a year or two... they want to feel more confidence.

      On the other side of that, we thought hard about what products make for good bootstrapped businesses, and we found that typically they were going one of two routes:

      1. They were an opinionated or niche-focused product in a very large existing category (i.e. Convertkit with email marketing. There is a major market here with large incumbents). This means there are a lot of people looking for something like your product already or customers switching off existing providers (i.e. mailchimp/others) because they're unsatisfied.
      2. They're building products specifically for a niche and the market isn't big enough to support a lot of companies, but customers look for and buy that specific thing.

      Arrows was and is trying to serve a broad set of customers, but we're in a new category that still needs time to develop and build awareness. We got real with the facts and realized we needed to become the Salesforce (#1 in size) of this category so that eventually a Highrise (smaller niche product) could exist later.

  3. 2

    What were some of your biggest challenges being bootstrapped that you hope to solve with VC Funding faster ?

    1. 2

      @codegeek1001 Great question. That was one of the big reasons we avoided taking funding for a while... we didn't have a good answer for what we'd do with it or what it would unlock for us.

      Primarily it's people. We have two engineers that started yesterday, so we can build a lot more of what our customers want a lot faster. We also hired one of our earliest advisors, someone who we've now been giving to our own customers as a free consultant on customer success and onboarding best practices. That's been hugely beneficial. And we hired sales + design, so I as the CEO am not in charge of those anymore as well.

      I don't have less work to do now... it’s that Arrows as a company can now parallelize more processes and deliver faster for customers. If anything, I have more work.

      Otherwise, it's been great to run more experiments and make more bets on things like ads or content marketing or hiring a contractor to help us with our Salesforce integration without the risk of any of those failing and it feeling like a waste of money.

  4. 2

    Do you have any regrets on not sticking it out at twilio or not joining at stripe at that early stage ? Sounds like that path would have been very lucrative financially.

    1. 1

      This is a fantastic question @mirv, and one I talk about often with friends.

      Simple answer: no. I have zero regrets.

      I am happy with my life and my choices, and I don't have any reason to believe I'd actually be happier with more money but without the friends/partner/Arrows/etc that I have in my life right now.

      More complicated answer: yes, I wish I would have stayed at Twilio another couple of years and learned more about that next stage of growth. OR that I'd have gone to Stripe and learned a lot about scaling a different company (and I wish i had closer friendships with the early Stripe people I knew). Yes, having the money those people have would be great, but it's not the primary reason I wish I'd have done them.

  5. 2

    Excited to be a part of this team! 🤩

  6. 1

    Arrows is an awesome product! Go Daniel go!

    1. 1

      haha Thanks @dternyak!

  7. 1

    You’re a legend

  8. 0

    Hi Daniel,

    From your video Arrows.to looks several cuts above most of what I see announced both in idea and execution.

    Since your onboarding tool touches on a lot of the same points that Uclusion tries to solve for development teams and since this is AMA, I can't help but ask if I can interest you in agile project management without all the meetings?

    1. 1

      Thanks for the kind words, @disrael! We're all set right now but I'll send it to the team!

  9. 2

    This comment was deleted 4 years ago

    1. 2

      Hey @harriskenny!!! One of our favorite customers 💘👋🏼

      I've found the most popular episodes to be surprising. Often we found the 3rd episode being one of the most listened to, long after we recorded it, because it was about filling up our sales funnel. Makes me realize we should record a follow-up about it.

      Otherwise, the funding episode and our episode with our PR consultant were the most reacted to... but typically we don't get a major response. I've meant to ask for it more. haha

      Here's our top episodes sorted by total downloads:
      https://i.imgur.com/PiUsvdA.jpeg

      1. 1

        This comment was deleted 4 years ago