<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kajetan von Armansperg on Medium]]></title>
        <description><![CDATA[Stories by Kajetan von Armansperg on Medium]]></description>
        <link>https://medium.com/@kajetan.armansperg?source=rss-461d4c7c0c2f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dhv0cDdBQA5e9oDkF_hLDQ.jpeg</url>
            <title>Stories by Kajetan von Armansperg on Medium</title>
            <link>https://medium.com/@kajetan.armansperg?source=rss-461d4c7c0c2f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:53:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kajetan.armansperg/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Lessons from our first fundraise (and our $60M Series A pitch deck)]]></title>
            <link>https://medium.com/@kajetan.armansperg/lessons-from-our-first-ever-fundraise-and-our-60m-series-a-pitch-deck-5c44f06efd91?source=rss-461d4c7c0c2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c44f06efd91</guid>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[fundraising]]></category>
            <category><![CDATA[bootstrapping]]></category>
            <category><![CDATA[founder-stories]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Kajetan von Armansperg]]></dc:creator>
            <pubDate>Wed, 07 Feb 2024 07:49:22 GMT</pubDate>
            <atom:updated>2024-02-07T14:52:42.924Z</atom:updated>
            <content:encoded><![CDATA[<p>Nine months ago, I set out to write about our bootstrapping story. Every two weeks, I was going to post one insight from our journey, leading to a comprehensive compendium of lessons learnt while bootstrapping a SaaS company from 0 to $10M ARR. Then “life happened”. It turned out that we, too, were affected by the “2023 SaaS recession”, growth suddenly slowed and other areas of the business required more urgent attention.</p><p>That SaaS recession is not necessarily over (even though we see green shoots across the metaphorical field) but I still want to take another shot at getting back into a writing rhythm. I’ve decided to be a bit less strict on the initial plan of creating a somewhat chronological account of our journey, and rather pick and choose from a long list of topics I wanted to write about whenever I feel the time is right. I also don’t want to limit the scope to bootstrapping, as the adjustment to being a company that’s backed by external investors is <em>just</em> as interesting.</p><p>So today, that topic is fundraising. As two founders that had bootstrapped for five years, we had very little practice in what can be a time-consuming and draining process. I’m arguably pretty badly qualified to give advice on this topic. However, we <em>did</em> consult a couple of highly qualified and experienced founders and investors, and the outcome was solid.</p><p>After debating the costs and merits of a fundraise in early January 2022, we spent 2 weeks crafting our deck and preparing the actual discussions, 2 weeks talking to investors, and 4 weeks in the due diligence process to raise our <a href="https://www.leapsome.com/blog/leapsome-60-million-series-a">first-ever round of $60M</a>.</p><p>Take all of this with a grain (or fistful) of salt. This was in March 2022, and <em>of course</em> the funding environment was still very different at the very end of the “fundraising bonanza” of 2020/2021. But there are probably still a few things that we learnt from our advisors that are still applicable today — and therefore worth sharing.</p><p>We got <em>a lot</em> of help during this process and certainly attribute most of the success to it. As a founding team, we always try to optimize for impact and maybe this is one way of giving back and helping others!</p><h3>Raise when you can (not when you must)</h3><p>I’ll start with the most obvious point, which is also the hardest to achieve. Everything that follows below is merely tactical advice. Your true strategic advantage will materialize if you raise your round from a position of strength.</p><p>In our case, we were growing quickly, were cashflow-positive and had crossed the mythical mark of $10M in recurring revenue. We <em>wanted</em> to explore external financing (the “why” behind this is material for another post) but we didn’t <em>have to.</em> In a negotiation with investors where your best alternative to negotiated agreement is “simply walking away”, this changes everything.</p><p>It’s hard to get into such a situation, so the advice — as unhelpful as it may sound — is simply this: If you ever find yourself in this situation, think twice if you really want to wait until you <em>have</em> to raise.</p><h3>Set a deadline</h3><p>What kept us from raising earlier was the fear that we would waste too much time with a long and tedious process, which would keep us from focusing on building a product, making customers happy and carefully growing our company — our primary job as CEOs. Fundraising is a means to an end, not a goal in itself, and we didn’t want to get distracted by the fundraising process. When we decided to explore fundraising, we therefore set ourselves a deadline of 8 weeks for the entire process and did everything we could to keep it as short as possible.</p><h3>Get help from the experts</h3><p>Where would we even start? Given that we had no clue, we spent a week interviewing other founders and friends in venture capital (shoutout to Polly, Rob, Peter, David and many more) to understand how this process works. We ended up with a long list of notes that helped us prioritize our work for the following week.</p><h3>Create a shortlist of investors</h3><p>In the best case scenario, your investors will accompany your company’s journey for many years to come, so the choice of investor is obviously very important. We wanted to partner with investors that</p><ul><li>are aligned with our company’s mission and values and are easy and fun to work with</li><li>had relevant experience with growth-stage SaaS companies and</li><li>have a strong brand in the US (given that our <a href="https://www.leapsome.com/de/blog/announcing-leapsome-nyc">US expansion was imminent</a>).</li></ul><p>Based on these criteria, we went through a long list of potential partners and identified a short list of 10 investors that we wanted to talk to.</p><p>I believe it’s worth going through this early prioritization exercise and knowing exactly who you want to talk to so you can target your pitch effectively and maximize the chance of success for an ideal outcome for both the process and the future. Investors do due diligence, and you should, too.</p><h3>Get introduced</h3><p>Once you have a short list, try to get a credible introduction to the right person.</p><ul><li>It depends entirely on your business and stage of growth who the “right person” might be. It might not be the famous partner but someone at the firm who knows your sector well or has invested in similar companies before.</li><li>“Credible” means that your “introducer” should have collaborated in one way or another with the person you want to meet — a random LinkedIn connection is not enough. It also means you will likely have to share some context <em>before</em> the intro — we equipped our introducers with three bullet points on business metrics to spark some initial interest.</li></ul><p>We luckily got introductions to all of the people we wanted to speak to, so I can’t speak to the success of cold outbound. It seems obvious that this would be much harder.</p><h3>Plan your meetings (carefully)</h3><p>If the email introduction is successful, schedule your meetings. Choose the timing of these carefully — you should be well-prepared for these <em>and</em> the next steps (see below). Once the fundraising process starts, a few things will happen:</p><ul><li>The investors that are really interested will want to move fast. As a founder, you will try to create a competitive situation with several offers, so it is important to keep the various processes in sync; they should, therefore, start simultaneously.</li><li>You will start getting follow-up data requests and follow-up meetings. Of course, you want to come across as well-organized, so plan ahead for this.</li><li>VCs will start talking. This is a curious one as it decreases the odds of a VC actually winning a deal. Rest assured, though, that any “confidential” sticker you put on your slides is probably a waste of time. If your story is interesting, the wider community <em>will</em> quickly know about it.</li></ul><p>In our case, we held all 10 initial meetings in a period of four days. Each of them lasted 45–60 minutes, and in two cases, we had a follow-up meeting scheduled for the same week. We suddenly also received a <em>ton</em> of inbound interest from other investors and anecdotally heard from customers that they were contacted by “research firms” in a matter of days. All follow-ups and term sheets were concluded within two weeks.</p><p>A few things we learned:</p><ul><li>We were lucky not to schedule more than four meetings in a day. Even if they only last an hour, these — and the ensuing email ping pong — can be quite exhausting.</li><li>We should have cleared our schedules entirely. Trying to run the business next to a dense fundraising process was a bit of a stretch.</li><li>We should have done better research on which firms tend to move fast and which tend not to. Toward the end of the process, we had to stall a couple of conversations, which was slightly awkward.</li></ul><h3>Prepare your deck</h3><p>We built a deck for a 12-minute pitch, tested it a few times with our advisors, and iterated based on their feedback. The ideal outcome really depends on the story you want to tell and the stage of the business. In our case, we ended up with the following structure</p><ul><li>Why people enablement is mission-critical for any business</li><li>How hybrid work, the war for talent, and a generational shift fuel this category</li><li>How the category compares to neighboring markets</li><li>Platform overview</li><li>Business metrics (total MRR, Growth, ARPA, NRR)</li><li>Business metrics and global growth</li><li>Competitive differentiation (supported by G2 numbers)</li><li>Integrations</li><li>Team</li><li>What we would do with the money</li></ul><p>We liked that story. However, we then used <a href="https://www.docsend.com/">Docsend</a> to share the pitch after the initial meetings and found out that most visitors literally skipped over almost all slides in seconds and only spent time on the slides for business metrics and team. So, if you feel very adventurous, maybe you can just go with business metrics and team!</p><p>Here’s our deck (Medium doesn’t allow Pitch embeds, so please bear with me for the format):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ANCsgoWNlmoGrMvcJkuSjg.png" /><figcaption>Nothing surprising here</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1gfKaK8Dox2dbuPjjxGEAA.png" /><figcaption>Why it matters</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9ipyekbY1cydlZVg8ANfbg.png" /><figcaption>Why it matters even more <strong><em>now</em></strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7M9FSuzt_rnh5kTNQfVNkg.png" /><figcaption>Category differentiation (don’t we all want to build a category?)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D_c465z58bJBwZUWDtWaZQ.png" /><figcaption>Platform overview and social validation (by the way, we do <a href="https://www.leapsome.com/">much more</a> today)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-HwhX2Ed8SLJ1bRnAw-iJA.png" /><figcaption>The slide that everybody spent most time on</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3JBM9lnbJ-XqPmkJpwJ8NA.png" /><figcaption>Global impact</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RG-H39XijeDREsc_FgB7sA.png" /><figcaption>Competitive differentation</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9DmEJ22YLdBsIsE-x1rP2w.png" /><figcaption>Integrations</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vDYo5K4xmDKtmUg7LjzujQ.png" /><figcaption>Team overview (redacted for obvious reasons)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1kD12rh_SZ8Q8krJDP6Gcg.png" /><figcaption>Fancy growth projections in early 2022 (spoiler alert: very ambitious!)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ldXJQb7SwGkJZi0ERqqBFQ.png" /><figcaption>Strategy outlook</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cqG4tbxqwok0hDxK46RyQw.png" /><figcaption>Thank you</figcaption></figure><h3>Prepare additional data</h3><p>We knew that our pitch deck would not be enough once we had sparked an investor’s interest. Next to our pitch deck, we prepared a few other materials to share on demand. These included:</p><ul><li>Sales efficiency metrics (win rates, sales cycle by market)</li><li>Anonymized sales quota achievement data (showcasing a scalable Sales motion)</li><li>MRR growth by cohort (SMB vs. mid-market customers, different geographies)</li><li>Customer concentration chart (showcasing little dependency on single customers)</li><li>Marketing efficiency metrics (ad spend vs. SQL growth)</li><li>Specific user testimonials from G2</li></ul><p>In addition, we prepared:</p><ul><li>A full data dump of our anonymized subscription data, which luckily was a one-click export in <a href="https://chartmogul.com/">Chartmogul</a>. Sharing this feels a bit like stripping naked, but it satisfies almost all requests.</li><li>A custom demo environment of our platform to be able to show investors around (interestingly, not all investors asked for this).</li><li>A list of customers that would be available for reference calls. Make no mistake, though, if an investor is interested, they will start doing their own research and ask your customers whether they have agreed to be contacted or not (so it’s a good idea to check which logos you use on your website before you start fundraising).</li><li>A very basic financial model for the next 3 years. Nobody actually asked for it — it seems that at a certain stage, all that matters are historical figures and a credible story on how you will spend the additional money.</li></ul><h3>Talk to a friendly lawyer</h3><p>If you’re lucky, you might get a term sheet sooner than you expect, and it’s best to be prepared for it. Term sheets come in many shapes and forms, and all of these might have <em>very</em> different implications for the future of your business.</p><p>Even if you already know how liquidation preference works and what drag-along rights are (<a href="https://www.amazon.com/Venture-Deals-Smarter-Lawyer-Capitalist/dp/1119594820">this book</a> is a good primer), it is worth spending time with a specialized law firm <em>before</em> you start talking to investors.</p><p>We even asked our partners to draft the “ideal term sheet” which helped us understand the various provisions’ implications and have a good benchmark for the following discussions.</p><h3>Pitch</h3><p>After all the prep work, this part actually was a lot of fun. This was back in 2022, so all but two meetings happened via Zoom — Jenny and I would sit in two phone booths, lead through the deck, answer questions, maybe show a quick demo, and hop onto the next call. Not much advice to share other than,</p><ul><li>prepping well for this stage really pays off;</li><li>limiting yourself to four meetings per day (see above);</li><li>enjoying the discussions — in some cases, you get to speak to <em>really</em> interesting industry icons which, in itself, warrants the call.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zvNz18h_5eKSVFEtqPaqrA.jpeg" /><figcaption>Pretty much what it looked like! (Photo Credit: Gabriel Benois)</figcaption></figure><h3>Get ready for due diligence</h3><p>Notably less fun than pitching! After receiving term sheets and a bit of negotiation, be prepared to now <em>actually</em> share everything. Depending on your investors, you will get to cooperate with a broad array of stakeholders — financial auditors, law firms, ESG auditors, etc., and maybe even more than one in each category. If you are based in Germany, all of this is crowned with a ten-hour session with your neighborhood notary.</p><p>We agreed on a deadline with our investors to ensure this would not be a long-term distraction. But it is quite a bit of (obviously important and necessary) work: Make sure you have support from your team to collect data, structure documents, and fill out questionnaires.</p><p>And yes, things <em>can</em> still go wrong; a term sheet alone isn’t binding. Midway through our process, Russia tragically invaded Ukraine, and we found ourselves nail-biting and tracking the rapidly deteriorating investor sentiment. We got lucky in our process — but not everyone did.</p><h3>Disclaimer</h3><p>Just to reiterate: Our experience is based on a fundraising process in a very different environment. Things look different today. And maybe there are still a few interesting insights that help other companies out there today. Good luck in any case, and if you have any questions, <a href="https://www.linkedin.com/in/kajetanarmansperg/">please hit me up via Linkedin</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c44f06efd91" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zero to $10M: Making learning scalable from day one]]></title>
            <link>https://medium.com/@kajetan.armansperg/zero-to-10m-making-learning-scalable-from-day-one-b69dd2af9d51?source=rss-461d4c7c0c2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b69dd2af9d51</guid>
            <category><![CDATA[founder-stories]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[bootstrapping]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Kajetan von Armansperg]]></dc:creator>
            <pubDate>Sun, 04 Feb 2024 11:18:03 GMT</pubDate>
            <atom:updated>2024-02-04T11:18:03.519Z</atom:updated>
            <content:encoded><![CDATA[<p>“Documentation” doesn’t typically trigger outbursts of excitement. The image that comes to mind are dimly lit cabinets populated by shelves that are stuffed with dusty folders containing grey-ish paper that nobody wants to look at — ever again.</p><p>But we are building a company that focuses on a continuous cycle of feedback and learning — and solid documentation happens to be the foundation of future learning. We also bootstrapped that company for a long time, so our learning approach needed to be scalable from day one.</p><p>That’s why — after outlining our story in the first post, and focusing on the strategic question of co-founder relationships — the third post in this bootstrapping series makes an argument for investing into scalable documentation, and not just doing this, but doing it really well, from day one.</p><h3>Moon module manuals</h3><p>The level of our detail of our internal documentation regularly comes up as a top contender when we ask new colleagues what surprised them most during their onboarding phase.</p><p>Our knowledge database is far from perfect — information ages surprisingly quickly and there are many parts that could be much more organized. But on the whole, our documentation probably resembles that of the extremely detailed manual of the Apollo Lunar Module (with details on propulsion, navigation, communication and what not), rather than the flimsy slide decks and creative chaos of some early stage companies.</p><p>While we didn’t rationalise this until later, solid documentation has been part of our DNA from day one. And it makes sense. Bootstrapping forced us to make learning scalable from day one.</p><h3>Divide &amp; conquer</h3><p>For two years, we were a team of two. If we wanted to maximise the exposure to users, customers and partners, it was not an option to hold large discovery meetings where both of us would be present. We had to split up and share the learnings asynchronously.</p><p>We agreed on rough common formats and started to meticulously document our meetings. As a result, we still have Google documents with hundreds of pages of learnings from early customer interviews and user testing sessions.</p><p>Each morning, with a cup of fresh coffee, we would read through each other’s notes of previous days, comment, ask follow-up questions and highlight core insights. We learned more quickly, could iterate faster and avoid a couple of mistakes that we simply couldn’t afford to make.</p><h3>Centralize knowledge management</h3><p>Of course, building an internal knowledge base in Google docs in a growing team is somewhat akin to trying to build a sand castle with a spoon during a beach volleyball tournament — it is hard to establish structure, the pace of learning is high, and new stakeholders get involved all the time.</p><p>As the company evolved and we reached a certain team size, we therefore introduced Notion to document core processes and insights, give everything a better structure and make things more easily accessible.</p><p>Yes, the initial setup is an investment of a few days, and it does require ongoing maintenance. But it’s one of those investments that you do once and that yields continuous payouts: Every new Leapsome employee gets a personalized onboarding checklist (and dedicated <a href="https://www.leapsome.com/product/learning">Leapsome learning paths</a>) with links to all relevant early insights for each team, helping them to become productive very quickly.</p><p>In addition, knowledge that you don’t require on a daily basis (and which you therefore don’t know by heart) is still easily accessible. So instead of having to reinvent the wheel every time when trying to find the right database field or adequate competitor talking point, you just look the knowledge that’s maintained by a core group of knowledge experts.</p><p>Things that worked well for us:</p><ul><li>Investing into a user-friendly database (we use Notion, and it’s great)</li><li>Having a tooling champion (shoutout to our internal “Notion wizard”) that helps to optimize the setup</li><li>Mandating that all knowledge has to live in that database (no more rogue Google docs)</li><li>Assigning clear ownership for documentation &amp; maintenance of different teamspaces</li><li>Using re-usable “content blocks” where possible (reduces the maintenance overhead)</li><li>Linking content in onboarding checklists and learning paths to enable discovery from day one</li></ul><h3>Document meetings to allow for asynchronous “participation”</h3><p>Solid documentation also trickles down to our daily meetings — and while meeting effectiveness will be the topic of another posts, here are some highlights. We use our own platform to <a href="https://www.leapsome.com/product/1-on-1-meetings">plan meetings and document outcomes</a> and action items which are easily accessible to all meeting participants — and the ones that (consciously) missed the meeting.</p><p>Things that worked well for us</p><ul><li>Establishing clear templates for all recurring meetings (clear sections / questions)</li><li>Making preparation mandatory — what’s not on the agenda won’t be discussed</li><li>Adding takeaways to the meeting notes</li><li>Allowing read-only participation (not everyone has to physically participate in the meeting)</li></ul><h3>Train your (future) digital assistants</h3><p>With the recent of proliferation of generative AI tools, solid documentation will very likely bring another benefit: The option to train (future) tools based on your internal knowledge base. The more structured and detailed your internal documentation, the more precise the answers from your future digital assistants will be and the more time you will have to focus on things that really matter.</p><p>Investing into a scalable learning infrastructure has a compounding effect from the first day onwards. The sooner you think about how you can scale the learning effect from one-to-one to one-to-many, the faster you will be able to spin the flywheel of feedback and learning, and the more efficiently you will be able to deploy the limited resources you have.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BzV6mbGDs55MzBHUcUPV6w.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b69dd2af9d51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zero to $10M: Building a strong co-founder relationship that fosters success]]></title>
            <link>https://medium.com/@kajetan.armansperg/zero-to-10m-building-a-strong-co-founder-relationship-that-fosters-success-d19eb0fc1483?source=rss-461d4c7c0c2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d19eb0fc1483</guid>
            <category><![CDATA[bootstrapping]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[founder-stories]]></category>
            <dc:creator><![CDATA[Kajetan von Armansperg]]></dc:creator>
            <pubDate>Sun, 04 Feb 2024 11:07:21 GMT</pubDate>
            <atom:updated>2024-02-04T11:07:21.885Z</atom:updated>
            <content:encoded><![CDATA[<p>The notepad I mentioned in my last post contains a rather wild collection of “things we learned while bootstrapping”, jotted down during a long flight a couple of weeks ago. Some are rather practical or even technical insights, some focus more on strategy and some on team dynamics.</p><p>There was no particular order to these (side effect of writing in a dimly lit cabin while the person sitting in front of me maxed out their full seat inclination freedom) but I decided to start with a post on team dynamics.</p><p>Why? Posts touting how “ChatGPT built my company in 7 days” proliferate on Linkedin these days, and yet building a business is still a quintessentially human endeavour. And building a business in a <em>capital</em>-efficient way means the foundation of your business — the relationship with your co-founder — has to work fairly efficiently, too.</p><p>“Efficient” is probably not the attribute that first comes to mind when you think of “great relationship”, but I will gladly feed the German stereotype (and obviously I would also describe our relationship as “fantastic” — but that’s not the point of this post).</p><p>In a resource-constraint setup you <em>have</em> to focus <em>all</em> your energy on being productive with the very small team you have (initially it will just be you, the founders). You simply don’t have <em>time</em> for friction and expansive interpersonal issues.</p><p>So here’s a non-exhaustive list of things that helped us build a solid foundation:</p><h3>Codifying founder values and responsibilities</h3><p>While the urge to simply jump right in, start coding and pitching felt great, we sat down with a cup of steaming tea on a dark and grey Berlin autumn afternoon in November, opened a Google Doc and wrote down a couple of things:</p><ul><li>Why we were starting this company: This was pretty obvious to us, we had always sought out impact-oriented jobs, both felt the pain of underinvestment into people enablement in our previous jobs and wanted to make work more meaningful;</li><li>How we wanted to work together and what was important to us: We wrote a short “manifesto” on things like always putting the company first, not giving in to our egos, being radically transparent with each other, etc.</li><li>What — based on the the strengths that we saw in each other- our areas of responsibility would be: Jenny would focus on Sales, People and Ops, I would focus on Product, Marketing and Customer Success.</li><li>How we would split ownership of the company (50:50) and how we would resolve potential decision impasses because of this ownership split (which are far more frequently mentioned in startup literature than they actually occur, so this was — in hindsight — a rather theoretical issue).</li></ul><p>The advice is this: Ask these questions early on and write down the answers. Some of these questions might be hard. They are. Don’t postpone them and let them linger. Especially if you don’t know each other well, they will distract you. You will be more focused and more at ease if you get them out of the way quickly. Some questions might also seem a bit fluffy. They are not. They help you create a foundation that you can refer back to as you start giving feedback.</p><h3>Giving each other regular feedback</h3><p>In the first year or so, Jenny and I had regular feedback meetings that were a dedicated “safe space” to speak very freely about everything that went well, but also vent about everything that didn’t. We still do this today, but somewhat less frequently.</p><p>Especially if you haven’t worked with each other before, the early days of co-founding a startup can be bumpy.</p><p>Despite everything that’s going on in the early days, make time for regular feedback — 30 minutes every two weeks. This will be hard at first, but it becomes easier over time. I had (and probably still have remnants of) a tendency of communicating <em>very</em> concisely (or less euphemistically: not providing enough context) and am very grateful that Jenny flagged this early.</p><p>By doing this, you ease potential tensions early on, you become better at working together, you learn something new about yourself frequently, and as a result of that, you personally grow faster. If you are just getting started, you probably don’t need it yet, but once the team is growing a bit, we’d obviously love to show you Leapsome.</p><h3>Running weekly founder check-ins and monthly strategy syncs</h3><p>Reserve an hour every week to discuss operational topics and meticulously prepare for this (we built this tool into our platform and it’s my <a href="https://www.leapsome.com/product/free-1-on-1-meeting-notes-software">favourite feature</a>).</p><p>Separate strategic check-ins from these operational discussions — you need more time to really dig deep and should proactively take that time about once a month. Decide up-front what you want to discuss, focus on one or two topics per 4-hour session and try to resolve them in one go.</p><h3>Celebrating together</h3><p>We’ve admittedly always struggled with this, but have at least become much better over time. Building a company is hard work and it’s just so much more fun if you celebrate the important milestones.</p><p>When you win a customer, ship a new feature, finally close that person you really wanted to hire, instead of carrying on right away, take time for that high five (or Leapsome <a href="https://www.leapsome.com/product/continuous-feedback">praise</a>!), and maybe even have a drink to celebrate.</p><h3>Being incredibly lucky</h3><p>I’m closing with the most difficult point, as other than fostering your network, there is not much actionable advice here. Meeting the right co-founder <em>at the right time</em> is probably one of the most serendipitous elements of a startup journey. If you are using the right lens, you realize you are fishing in a very small and shallow pond rather quickly. At the end of the day, you are looking for someone that ideally</p><ul><li>has a highly complementary skillset (unless you have tons of spare money to hire whichever people with skills you don’t have in the founder team)</li><li>shares the passion for the topic or idea you want to explore and can discuss strategy at eye level (you need a sparring partner for the difficult choices)</li><li>shares your risk affinity not just in general, but at the same point in time when you are ready to make that scary jump</li></ul><p>This requires luck. Jenny and I had randomly met ten years prior to starting Leapsome, had stayed in touch over the years (living in the same city helped) and were both inclined to take new risks at a similar time.</p><p>Just like any relationship, a successful co-founder relationship requires hard work and continuous investment. It pays off, through increased focus and efficiency from the early days onwards, and by providing a role model for other relationships in the organization later on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rh17_iY1ZX1TzC6zPafWzA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d19eb0fc1483" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zero to $10M: Making the cup of coffee last]]></title>
            <link>https://medium.com/@kajetan.armansperg/zero-to-10m-making-the-cup-of-coffee-last-1970fb794ed1?source=rss-461d4c7c0c2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1970fb794ed1</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[fundraising]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[bootstrapping]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Kajetan von Armansperg]]></dc:creator>
            <pubDate>Sun, 04 Feb 2024 11:03:32 GMT</pubDate>
            <atom:updated>2024-02-04T11:03:32.445Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DU1jMTFrPpo4dNTCwkRb_A.jpeg" /></figure><h3>Why</h3><p>Writing about our bootstrapping journey first occurred to me when we <em>stopped</em> bootstrapping about a year ago. We had bootstrapped our SaaS platform Leapsome to more than 10M in ARR, had just raised a sizeable “Series A” and it seemed like a good moment. It was more of a quickly passing thought, though. The reality is that when you are bootstrapping, you are likely so deeply operationally involved in what your business is doing that you rarely think of being a public “thought leader”. And to be transparent, I’m also just not the type of person who naturally enjoys the public thought leader part.</p><p>About a week ago, a discussion during our board meeting (still something we’re getting used to, but highly beneficial) sparked the same thought again. Right now, founders that are trying to get their fledgling companies off the ground have to be capital-efficient. As a result of suddenly higher interest rates and costs of capital, the tech industry is reeling from the worst hangover in a long time and there simply isn’t a lot of funding around. For many, bootstrapping is the new default.</p><p>Jenny and I started Leapsome to have an impact — to make work fulfilling for everyone. As we built Leapsome in a very capital-efficient way, we learnt (and oftentimes that means: accidentally discovered) a few lessons that could be helpful to other founders that have to do much more with much less today. If sharing these lessons (some might be helpful, some not) can help you and have a positive impact, that’s time well invested.‍</p><h3>Making the cup of coffee last</h3><p>The journey of our startup has been unconventional. Looking back, it would be easy to say we planned it like this from day one. The reality is we didn’t — we stumbled into bootstrapping. Sitting in various co-working spaces and (much to the dismay of their owners) squatting in cafes in Berlin for hours while sipping on a single cup of coffee, we simply started doing the things we thought would generate a bit of initial traction so we had something to show to potential investors.</p><p>We started building a prototype that was very rough around the edges and talking to potential customers. We collected initial feedback, iterated, received more refined feedback and iterated a bit more. Eventually a few companies were brave enough to use our early product and actually pay for it. We decided to keep going, for that one additional iteration, and yet one more.</p><p>The early days were certainly not a walk in the park. We worked as a “team of two” for almost two years before we made our (incredibly lucky) first full-time hire. Grinding long hours as your bank balance keeps dwindling can feel threatening. Fast-forward roughly 4.5 years though, and we had bootstrapped our way to a solid business generating more than USD10M in annual recurring revenue (ARR), serving tech household names like Spotify, Unity, and Bolt, with a team of roughly 50 employees.‍</p><h3>Role models</h3><p>There are a couple of very notable tech companies — and lots of more traditional companies — that have grown to such scale without outside investment and that we look up to as role models. But you rarely hear about them. In the tech industry, sizeable venture capital investments and astronomic company valuations are seen as signs of success. You will get press coverage if you close large funding rounds — the stories of the bootstrapped companies are much less frequently told.</p><p>This blog series is therefore not a manifest for the virtue of bootstrapping. While we believe that bootstrapping made us stronger — and there are quite a few benefits which we’ll talk about — there are also clear downsides. We also always bootstrapped pragmatically, not dogmatically and raised a significant first funding round from fantastic investors last year.</p><p>Instead, we’re trying to share some practical lessons on building small &amp; efficient teams, on (not) hiring, on capturing demand, on iterating quickly on the product front, on shaping your mini-brand, and a few more. Some of them might seem rather obvious, especially in hindsight. We’ll share them regardless, as we think they eventually became strands of our DNA.</p><p>Please don’t take them for granted. We know that luck plays a massive role in any startup story, and it certainly did in ours. We’re also at a very, <em>very</em> early stage of our journey: When standing next to the giants in tech, we are certainly tiny and not in a position to share nuggets of wisdom without sounding slightly preposterous.‍</p><h3>On a personal note</h3><p>The things we’ve learned are things we learned as a team, and I don’t take personal credit for them. I do think that the personal perspective can make things a little more interesting, and I also just enjoy writing. My friends and family will remember my travel diaries — I spent hours crafting fun and entertaining (I hope) posts about my adventures while the clock was ticking in hot and humid internet cafes (those were the days) and I would make extra sure to save regularly so that the next blackout wouldn’t erase that beautiful draft.</p><p>My writing habit has admittedly become quite rusty in the meantime — please bear with me. There’s also no detailed plan, just a notepad with a few quickly jotted down ideas. We’ll see how this blog evolves. If you have particular questions or suggestions for topics — please send us a message.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1970fb794ed1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>