here. </p><p><a href=https://www.ycombinator.com/"https://www.snapdocs.com//">Snapdocs is the leading digital closing platform for the mortgage industry. Today, the company touches 25% of all US real estate transactions and is valued at $1.5B. Founder and CEO <a href=https://www.ycombinator.com/"https://twitter.com/a_w_king/">Aaron King</a> and his team have expertly navigated fundraising and market cycles. We sat down with Aaron to hear his insight into getting a business up and running with minimal outside funding and building through volatile market conditions. </p><p><strong>Why did you decide to raise minimal funding early in the company’s history?</strong></p><p>I never considered funding to be a requirement for building — but I also didn't know much about fundraising early on in the company’s history. Snapdocs was started as a side project a couple of years before ever thinking about applying to YC. By the time I applied, we had a live product, customers, and revenue. Even after YC, we didn’t raise much immediately. We stayed focused on building and then raised a seed round later in the year.</p><p>It wasn’t until three years later that we raised our Series A. By then, we had spent about $1MM of our seed round and were at a $5MM revenue run rate. Around that time we started working with much larger customers, and it was clear we would need more capital to be successful in this bigger market. So, we raised our Series A. After we closed the round, our lead investor revealed how capital efficient we had been compared to our peers. </p><p><strong>Do you feel you had to ruthlessly prioritize when building the product because you didn't have the capital?</strong></p><p>Yes, and I’ve learned that you should take the same approach even when you do have the capital to be less disciplined. Back then, ruthless prioritization was our only option. We couldn’t afford to build features that weren’t essential. There were always a hundred distractions that would result in a broader, less focused product. But our capital constraints kept us focused on going deep with our paying customers. That helped us avoid the common trap of building products no one wanted. </p><p>It also meant that when we decided to build a product, we had to think about the smallest version of that product in order to quickly ship. That helped ensure we had a short feedback loop from our users and ensure our resources were continuously being invested in building the right features. Looking back, I’m amazed at how much we were able to accomplish without spending much capital. </p><p>Being capital constrained forced good behaviors that served us well even after we raised more funding. We continue to be thoughtful about every dollar we spend. But, there is a cost to this approach, and we’re paying for it today. We built many things that weren't engineered for scale or flexibility. However, now we can afford to reengineer those unscalable solutions because we built something people want.</p><p><strong>What did your product cycles look like before you raised your Series A?</strong></p><p>We were always heavy on customer involvement when building product. We spent a lot of time in our customers’ offices watching them use what we were building and understanding their work. We also kept a lot of our prospects in the loop as we built new features. Some of the best feedback came from people who had chosen to not yet work with us. Responding to that feedback with a killer feature was a great way to ultimately get them on board. </p><p>We built a lot of trust and rapport with these early customers, and the in-person interactions helped immensely. As a result, they would call one of us the moment they thought there was a problem or if they thought a competitor was doing something compelling. Customer churn for Snapdocs has always been incredibly low as a result. </p><p>We created a disciplined product release process, even in those early days, but we were still able to move quickly. We shipped code every day, sometimes multiple times a day. Customers were impressed by how quickly we could respond to issues and feedback. </p><p>Interestingly, not having too much pressure from investors early on allowed us to experiment more in an underappreciated part of our market. The Serviceable Available Market (SAM) of our initial product was roughly only $20MM, but we believed it would allow us to expand into more critical parts of the mortgage ecosystem. It was the type of opportunity that would be hard to discover through market analysis or spreadsheet exercises. You had to get deep into the problem set to see the opportunity and develop the right strategy—and that ultimately worked to our advantage. </p><p><strong>Founders need capital to hire employees. As a bootstrapped company, what was your strategy around hiring? </strong></p><p>Hiring was hard, but we did a few things that worked well. Even before the company could afford full-time employees, I worked with talented contractors. I also leaned on friends to help me work through both technical and business challenges. Someone would come over and whiteboard with me or we’d get into the code and work through a problem. </p><p>When I could afford to hire full-time employees, I treated them like founding team members. I was generous with equity and shared everything about the potential and challenges of the business. We built a lot of trust as a small team. Getting a few really good people into the company early on was foundational to the company’s success. </p><p>The first person to join full-time was an engineer I had worked with in a previous role (and one of the friends that would help in those early days). The second and third hires were applicants from job postings on Hacker News. All three turned out to be excellent. None of us initially had large networks in the startup world, so most of our early hiring involved lots of interviews and hiring a few of the wrong people. We couldn’t attract well-known talent and took risks; invested in people we thought had a lot of potential. </p><p>One mistake I made in the early years was being too timid to approach more of the people I respected. I should have tried to convince them to quit their successful jobs and join our small (yet risky at the time) startup. I’m fearless on this approach now, but back then I was intimidated to try to convince a friend to join a company that might fail. In hindsight, I did them a disservice by not trying to recruit them. The truth is that these people are smart and you’re not harming anyone by sharing your vision and the potential of the company with them. As long as you’re honest and transparent about the inherent challenges, you should give them the opportunity to take a risk on you. </p><p>As Snapdocs grew, it became easier to pull from the team’s networks. We continued to build a lot of trust within the team, and they started referring their friends to apply. Eventually, we attracted well-known investors, and that, along with our culture and growth, made hiring easier. </p><p>Because we were capital constrained, we also didn’t hire anyone until there was a clear and painful need. It made running the company harder because we were all spread thin but ultimately made us incredibly productive, as it meant we were always working on the most important things. </p><p><strong>How have you navigated different market conditions? When do you decide to react?</strong></p><p>A big part of our success has come from selectively ignoring some market changes while reacting quickly to others. It has always been a question of how the change aligns with our resources, vision, and north star metric of market share growth. </p><p>For example, the biggest and most dynamic change we regularly experience are fluctuations in the number of mortgages that happen in a given month or year. This can change quickly based on a host of economic factors. When we are well-resourced and growing fast, we can ignore some of those market downturns and stay focused on market share growth — knowing we have the momentum and capital to power through it. Other times we’ve had to scale up or scale back based on the size of the fluctuation.</p><p>But other market dynamics can change quickly too, like the industry’s appetite for new technologies and the competitive landscape. There have been times when the market was demanding a technology but we believed there were underlying factors in the industry that would prevent that tech from scaling. If we built the technology, it would pull resources away from the priorities that drove us toward our long-term goals. And so, sometimes to the protests of our sales team, we ignored it or invested minimally in these trendy areas. By doing so, we were able to stay focused on the things that were truly going to transform the industry. </p><p>It’s also worth noting that navigating change was relatively easy in the first few years of building the company. It was a lot easier to adjust course on company direction or strategy when the team was smaller and could all fit in the same room. The product cycles were relatively short and malleable. The cost of making a change was low. </p><p>As the company has grown, we’ve had to be a lot more thoughtful and methodical about changing the speed or direction of the business as we react to market changes. The cost of making a change has increased a lot. Investments take longer to play out. Changes to headcount take longer to scale up or down. There are more people on the team and more layers in the organization to communicate the change through. </p><p><strong>In March 2020, Snapdocs made a huge shift because of changes you were seeing in the housing market. How did you communicate this shift to your team and ensure their goals were aligned with the new priorities? </strong></p><p>COVID accelerated demand for our product, but with that came a shift in what our customers wanted from a platform like ours. We had to expand quickly to serve their needs, and we had to pivot our roadmap on a dime. It’s a testament to the team that we were able to pull that off. </p><p>To make decisions quickly and then communicate them, we worked in concentric circles. We started by discussing the change in a smaller group of 3-4 people. This is where the hardest and messiest conversations took place. We moved quickly to define the problems and opportunities and set a direction for the company. We then looped in the senior leadership team for further discussion and to arm them with everything they needed to share the directional changes with their teams. Finally, we held a company-wide meeting to share the new direction and answer questions. All of this happened over the course of about 2 weeks.</p><p>Now, our business required more speed and flexibility as information was coming in and changing week on week. We dealt with this by creating temporary pods of 4-5 team members focused on solving specific challenges that would spin up for a few weeks and then dissolve once the challenge was addressed. We also increased the frequency of our company-wide all-hands meetings from monthly to weekly so we could keep the whole company up to speed. </p><p>Luckily we had a deep culture of transparency that goes back to the beginning of the company. We’ve always tried to share everything with our entire team — our cash balance, monthly growth rate, burn, our biggest challenges. This got harder as the team grew, but we’ve largely continued this transparency to today. It’s much easier to be transparent in times of great change if you've laid a foundation of trust and transparency in the past. </p><p>We also worked hard to be intellectually honest about the growth we were experiencing. It’s easy to take credit when the business accelerates, but our message to the team wasn't, “Look at how great we're doing.” The message was closer to, “This industry works in cycles. We're in an up cycle now and that's great. There's going to be a down cycle. We don't know when or how strong it's going to be. But we should not overly congratulate ourselves for the current situation, just as we shouldn’t be too hard on ourselves when we’re fighting through an inevitable downturn in the future.”</p><p><strong>In 2021, Snapdocs </strong><a href=https://www.ycombinator.com/"https://www.snapdocs.com/resource-center/blog/announcing-our-150m-series-d-funding-round/">announced a Series D round. How did this change your mentality around resources?</strong></p><p>It was clear that the pandemic would be an accelerator for our business, and we needed to move fast to stay ahead of the market. We went from being frugal to raising larger rounds of capital and hiring seasoned executives who could help us scale. It’s important for companies to evolve at the right points in time and ask themselves, “Is what I did yesterday the thing that's going to get me to where I need to be tomorrow?”. We asked that question and decided we needed to change parts of our culture and capital investment strategy if we wanted to win.</p><p>When we raised capital in 2021, transactions on Snapdocs had steadily increased to millions of closings a year and thousands of lenders and title companies were using our technology every month. Demand for mortgages throughout the pandemic was strong, and we deployed an intentional strategy of prioritizing effectiveness over efficiency. We needed to get aggressive and expand our market position, which required capital. </p><p>The market turned again later in the year, with demand for mortgages cooling. It was clear that it was time to go back to some of our old ways of doing things. We ditched the motto of being effective over being efficient. This meant a return to ruthless prioritization of our focus. We shifted away from investing so heavily in future scale as we wouldn’t need to tap into these systems for a few years.</p><p>I find it helpful to remember that market fluctuations are normal and unavoidable. Startups should scale up at times and scale back at others. It’s hard and painful. There’s nothing easy or enjoyable about being understaffed to meet customer demand on one side, or needing to let team members go on the other. But these ups and downs are natural and a necessary part of building an enduring company. In a startup, you’re always making hard decisions based on insufficient information. You’re never going to be able to perfectly predict the future. You need to keep making the best decisions you can — knowing all the while that you may be wrong and need to change course again once the future becomes clearer.</p>","comment_id":"63d45276ba7a5900012d1cb7","feature_image":"/blog/content/images/2023/02/BlogTwitter-Image-Template--24-.png","featured":true,"visibility":"public","email_recipient_filter":"none","created_at":"2023-01-27T14:38:46.000-08:00","updated_at":"2023-02-22T18:17:22.000-08:00","published_at":"2023-01-30T08:59:00.000-08:00","custom_excerpt":"Founder & CEO Aaron King expertly built Snapdocs through volatile market conditions and with minimal outside funding into the mortgage industry's leading digital closing platform, valued at $1.5B today. This is what he learned about navigating market cycles.","codeinjection_head":null,"codeinjection_foot":null,"custom_template":null,"canonical_url":null,"authors":[{"id":"61fe29e3c7139e0001a710a7","name":"Lindsay Amos","slug":"lindsay-amos","profile_image":"/blog/content/images/2022/02/Lindsay.jpg","cover_image":null,"bio":"Lindsay Amos is the Senior Director of Communications at Y Combinator. In 2010, she was one of the first 30 employees at Square and the company’s first comms hire.","website":null,"location":null,"facebook":null,"twitter":null,"meta_title":null,"meta_description":null,"url":"https://ghost.prod.ycinside.com/author/lindsay-amos/"}],"tags":[{"id":"61fe29efc7139e0001a71174","name":"Advice","slug":"advice","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/advice/"},{"id":"61fe29efc7139e0001a71181","name":"YC Continuity","slug":"yc-continuity","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/yc-continuity/"},{"id":"61fe29efc7139e0001a71152","name":"Founder Stories","slug":"founder-stories","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/founder-stories/"},{"id":"61fe29efc7139e0001a71158","name":"Leadership","slug":"leadership","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/leadership/"},{"id":"61fe29efc7139e0001a71170","name":"Startups","slug":"startups","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/startups/"},{"id":"61fe29efc7139e0001a71155","name":"Growth","slug":"growth","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/growth/"},{"id":"63d45389ba7a5900012d1ccf","name":"#622","slug":"hash-622","description":null,"feature_image":null,"visibility":"internal","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/404/"}],"primary_author":{"id":"61fe29e3c7139e0001a710a7","name":"Lindsay Amos","slug":"lindsay-amos","profile_image":"https://ghost.prod.ycinside.com/content/images/2022/02/Lindsay.jpg","cover_image":null,"bio":"Lindsay Amos is the Senior Director of Communications at Y Combinator. In 2010, she was one of the first 30 employees at Square and the company’s first comms hire.","website":null,"location":null,"facebook":null,"twitter":null,"meta_title":null,"meta_description":null,"url":"https://ghost.prod.ycinside.com/author/lindsay-amos/"},"primary_tag":{"id":"61fe29efc7139e0001a71174","name":"Advice","slug":"advice","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/advice/"},"url":"https://ghost.prod.ycinside.com/learnings-of-a-snapdocs-aaron-king-on-navigating-market-cycles/","excerpt":"Founder & CEO Aaron King expertly built Snapdocs through volatile market conditions and with minimal outside funding into the mortgage industry's leading digital closing platform, valued at $1.5B today. This is what he learned about navigating market cycles.","reading_time":9,"access":true,"og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"email_subject":null,"frontmatter":null,"feature_image_alt":null,"feature_image_caption":null},"mentions":[{"id":622,"slug":"snapdocs","name":"Snapdocs","batch_name":"W14","small_logo_url":"https://bookface-images.s3.amazonaws.com/small_logos/4391e46749d4be871f138c61fa409a9979d7739e.png","one_liner":"Snapdocs digitizes real estate closings","website":"http://snapdocs.com","long_description":"Snapdocs powers homeownership. Using technology, we’re building the connective tissue for an entire pillar of the U.S. economy: residential real estate. \r\n\r\nToday, we’re working to perfect mortgage closings, but that’s only the beginning. If we succeed, more than five million families per year will gain clarity and transparency as they make the biggest financial decision of their lives: buying a home. Before Snapdocs, no one felt responsible or empowered to solve the problems we face every day we come to the office. \r\n\r\nIt's complex and difficult work, and the result is not an app we brag about at tech industry parties. Instead, we're making a difference and carefully building a team that shares our priorities—pragmatism, respect and empathy for our clients, and building honest products that improve all our users’ lives.","tags":["SaaS","B2B","Housing"],"ycdc_status":"Active","logo_url":"https://bookface-images.s3.amazonaws.com/logos/52b98b22374f039b027b6d40c3545f8854ea8cc2.png","year_founded":2014,"team_size":285,"location":"San Francisco","linkedin_url":"https://www.linkedin.com/company/snapdocs","twitter_url":"https://twitter.com/snapdocs","fb_url":"https://www.facebook.com/snapdocs/","cb_url":"https://www.crunchbase.com/organization/snapdocs","is_hiring":true,"active_job_count":4}],"related_posts":[{"id":"61fe29f1c7139e0001a71ba2","uuid":"a2de7e9b-655c-4b88-af38-1d4df1e6630f","title":"Meet 8 YC startups that are hiring right now","slug":"meet-8-yc-startups-that-are-hiring-right-now","html":"<!--kg-card-begin: html--><p>Many YC startups are actively hiring on <a href=https://www.ycombinator.com/"https://www.workatastartup.com/">Work at a Startup</a> across engineering, product, design, marketing and more. We asked founders to shoot a 30-second video describing their businesses and open roles. Meet them below:</p>\n<p><iframe loading=\"lazy\" width=\"560\" height=\"315\" src=https://www.ycombinator.com/"https://www.youtube.com/embed/videoseries?list=PLQ-uHSnFig5P_7Vrgb-hrPRnA6tqyX233\%22 frameborder=\"0\" allow=\"accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture\" allowfullscreen></iframe></p>\n<p>About each company:</p>\n<ul>\n<li><a href=https://www.ycombinator.com/"https://www.workatastartup.com/directory/1884/">Curebase is a CRO and software platform for distributed clinical trials. <em>Hiring: Software Engineer, Trial Manager and Product Manager.</em> </li>\n<li><a href=https://www.ycombinator.com/"https://www.workatastartup.com/directory/1276/">Curtsy makes it easy for women to buy and sell clothes from their phone. <em>Hiring: Product Design and Software Engineer.</em> </li>\n<li><a href=https://www.ycombinator.com/"https://www.workatastartup.com/directory/76/">OneSignal creates developer APIs for push notifications, in-app messaging, and email. <em>Hiring: Front-end, Mobile, Back-end and Senior Engineers.</em></li>\n<li><a href=https://www.ycombinator.com/"https://www.workatastartup.com/directory/13332/">PostEra provides chemistry-as-a-service to design and synthesize molecules faster and at a lower cost. <em>Hiring: Software and ML Engineer.</em></li>\n<li><a href=https://www.ycombinator.com/"https://www.workatastartup.com/directory/12660/">Rosebud AI</strong></a> creates software generated photos for advertising and marketing. <em>Hiring: Deep-learning Engineer.</em></li>\n<li><a href=https://www.ycombinator.com/"https://www.workatastartup.com/directory/12609/">Soteris creates ML software to route and price insurance risk. <em>Hiring: ML and Back-end Engineer.</em> </li>\n<li><a href=https://www.ycombinator.com/"https://www.workatastartup.com/directory/989/">Tovala makes home-cooked meals effortless. <em>Hiring: Software Engineer, Marketing, and Social Media Manager.</em> </li>\n<li><a href=https://www.ycombinator.com/"https://www.workatastartup.com/directory/13146/">Eternal is a rewards program for gamers. <em>Hiring: Product Design and Front-end Engineer.</em> </li>\n</ul>\n<p>And if you&#8217;re looking for a new job, apply with a single profile to over 400 YC startups on <a href=https://www.ycombinator.com/"https://www.workatastartup.com/">Work at a Startup</a>.</p>\n<!--kg-card-end: html-->","comment_id":"1104267","feature_image":"https://images.unsplash.com/photo-1542744173-8e7e53415bb0?crop=entropy&cs=tinysrgb&fit=max&fm=jpg&ixid=MnwxMTc3M3wwfDF8c2VhcmNofDU3fHxoaXJpbmclMjBub3d8ZW58MHx8fHwxNjQzOTM0NzEz&ixlib=rb-1.2.1&q=80&w=2000","featured":false,"visibility":"public","email_recipient_filter":"none","created_at":"2020-04-09T04:59:26.000-07:00","updated_at":"2022-06-27T13:08:02.000-07:00","published_at":"2020-04-09T04:59:26.000-07:00","custom_excerpt":null,"codeinjection_head":null,"codeinjection_foot":null,"custom_template":null,"canonical_url":null,"authors":[{"id":"61fe29e3c7139e0001a710bf","name":"Ryan Choi","slug":"rchoi","profile_image":"//www.gravatar.com/avatar/36ba914c5f191f813e96db0296154469?s=250&d=mm&r=x","cover_image":null,"bio":"Ryan works with YC companies to find great engineers — from 2-person startups to larger ones like Airbnb, Stripe and Instacart.","website":null,"location":null,"facebook":null,"twitter":null,"meta_title":null,"meta_description":null,"url":"https://ghost.prod.ycinside.com/author/rchoi/"}],"tags":[{"id":"61fe29efc7139e0001a71170","name":"Startups","slug":"startups","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/startups/"},{"id":"61fe29efc7139e0001a71172","name":"Video","slug":"video","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/video/"},{"id":"61fe29efc7139e0001a71171","name":"Work at a Startup","slug":"work-at-a-startup","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/work-at-a-startup/"},{"id":"61fe29efc7139e0001a71178","name":"#jobs","slug":"hash-jobs","description":null,"feature_image":null,"visibility":"internal","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/404/"},{"id":"61fe29efc7139e0001a71177","name":"Jobs","slug":"jobs","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/jobs/"},{"id":"62b9d2f7063d2d0001f0fc2d","name":"#1884","slug":"hash-1884","description":null,"feature_image":null,"visibility":"internal","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/404/"},{"id":"62ba0d42063d2d0001f0fc79","name":"#1276","slug":"hash-1276","description":null,"feature_image":null,"visibility":"internal","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/404/"},{"id":"62ba0d42063d2d0001f0fc7a","name":"#76","slug":"hash-76","description":null,"feature_image":null,"visibility":"internal","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/404/"},{"id":"62ba0de1063d2d0001f0fc80","name":"#13332","slug":"hash-13332","description":null,"feature_image":null,"visibility":"internal","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/404/"},{"id":"62ba0de1063d2d0001f0fc81","name":"#12660","slug":"hash-12660","description":null,"feature_image":null,"visibility":"internal","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/404/"},{"id":"62ba0de1063d2d0001f0fc82","name":"#12609","slug":"hash-12609","description":null,"feature_image":null,"visibility":"internal","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/404/"},{"id":"62ba0de1063d2d0001f0fc83","name":"#989","slug":"hash-989","description":null,"feature_image":null,"visibility":"internal","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/404/"},{"id":"62ba0de1063d2d0001f0fc84","name":"#13146","slug":"hash-13146","description":null,"feature_image":null,"visibility":"internal","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/404/"}],"primary_author":{"id":"61fe29e3c7139e0001a710bf","name":"Ryan Choi","slug":"rchoi","profile_image":"//www.gravatar.com/avatar/36ba914c5f191f813e96db0296154469?s=250&d=mm&r=x","cover_image":null,"bio":"Ryan works with YC companies to find great engineers — from 2-person startups to larger ones like Airbnb, Stripe and Instacart.","website":null,"location":null,"facebook":null,"twitter":null,"meta_title":null,"meta_description":null,"url":"https://ghost.prod.ycinside.com/author/rchoi/"},"primary_tag":{"id":"61fe29efc7139e0001a71170","name":"Startups","slug":"startups","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/startups/"},"url":"https://ghost.prod.ycinside.com/meet-8-yc-startups-that-are-hiring-right-now/","excerpt":"Many YC startups are actively hiring on Work at a Startup across engineering, product, design, marketingand more. We asked founders to shoot a 30-second video describing theirbusinesses and open roles. Meet them below:About each company: * Curebase is a CRO and software platform for distributed clinical trials.Hiring: Software Engineer, Trial Manager and Product Manager. * Curtsy [https://www.","reading_time":1,"access":true,"og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"email_subject":null,"frontmatter":null,"feature_image_alt":null,"feature_image_caption":"Photo by <a href=https://www.ycombinator.com/"https://unsplash.com/@campaign_creators?utm_source=ghost&utm_medium=referral&utm_campaign=api-credit\%22>Campaign Creators</a> / <a href=https://www.ycombinator.com/"https://unsplash.com/?utm_source=ghost&utm_medium=referral&utm_campaign=api-credit\%22>Unsplash%22},{%22id%22:%226357f9044557ad0001018040%22,%22uuid%22:%22b73507ea-8de6-4799-8305-1554bd33437c%22,%22title%22:%22How to maintain engineering velocity as you scale","slug":"how-to-maintain-engineering-velocity-as-you-scale","html":"<p>Engineering is typically the function that grows fastest at a scaling startup. It requires a lot of attention to make sure the pace of execution does not slow and cultural issues do not emerge as you scale.</p><p>We’ve learned a lot about pace of execution in the past five years at Faire. When we launched in 2017, we were a team of five engineers. From the beginning, we built a simple but solid foundation that allowed us to maintain both velocity and quality. When we found product-market fit later that year and started bringing on lots of new customers, instead of spending engineering resources on re-architecturing our platform to scale, we were able to double down on product engineering to accelerate the growth. In this post, we discuss the guiding principles that allowed us to maintain our engineering velocity as we scaled.</p><h2 id=\"four-guiding-principles-to-maintaining-velocity\">Four guiding principles to maintaining velocity</h2><p>Faire’s engineering team grew from five to over 100 engineers in three years. Throughout this growth, we were able to sustain our pace of engineering execution by adhering to four important elements:</p><ol><li><a href=https://www.ycombinator.com/"https://www.ycombinator.com/blog/how-to-maintain-engineering-velocity-as-you-scale/#1-hire-the-best-engineers\">Hiring the best engineers</a></li><li><a href=https://www.ycombinator.com/"https://www.ycombinator.com/blog/how-to-maintain-engineering-velocity-as-you-scale/#2-build-a-solid-long-term-foundation-from-day-one\">Building solid long-term foundations from day one</a></li><li><a href=https://www.ycombinator.com/"https://www.ycombinator.com/blog/how-to-maintain-engineering-velocity-as-you-scale/#3-track-engineering-metrics-to-drive-decision-making\">Tracking metrics to guide decision-making</a></li><li><a href=https://www.ycombinator.com/"https://www.ycombinator.com/blog/how-to-maintain-engineering-velocity-as-you-scale/#4-keep-teams-small-and-independent\">Keeping teams small and independent</a></li></ol><h2 id=\"1-hire-the-best-engineers\">1. Hire the best engineers</h2><p>You want to hire the best early team that you can, as they’re going to be the people helping you scale and maintain velocity. And good people follow good people, helping you grow your team down the road.</p><p>This sounds obvious, but it’s tempting to get people in seats fast because you have a truckload of priorities and you’re often the only one doing engineering recruiting in those early years. What makes this even harder is you often have to play the long game to get the best engineers signed on. Your job is to build a case for why your company is <em>the</em> opportunity for them. </p><p>We had a few amazing engineers in mind we wanted to hire early on. I spent over a year doing coffee meetings with some of them. I used these meetings to get advice, but more importantly I was always giving them updates on our progress, vision, fundraising, and product releases. That created FOMO which eventually got them so excited about what was happening at Faire that they signed up for the ride.</p><p>While recruiting, I looked for key competencies that I thought were vital for our engineering team to be successful as we scaled. These were:</p><h3 id=\"a-experts-at-our-core-technology\">a. Experts at our core technology</h3><p>In early stages, you need to move extremely fast and you cannot afford to make mistakes. We wanted the best engineers who had previously built the components we needed so they knew where mistakes could happen, what to avoid, what to focus on, and more. For example, we built a complex payments infrastructure in a couple of weeks. That included integrating with multiple payment processors in order to charge debit/credit cards, process partial refunds, async retries, voiding canceled transactions, and linking bank accounts for ACH payouts. We had built similar infrastructure for the Cash App at Square and that experience allowed us to move extremely quickly while avoiding pitfalls.</p><h3 id=\"b-focused-on-delivering-value-to-customers\">b. Focused on delivering value to customers</h3><p>Faire’s mission is to empower entrepreneurs to chase their dreams. When hiring engineers, we looked for people who were amazing technically but also understood our business, were customer focused, were passionate about entrepreneurship—and understood how they needed to work. That is, they understood how to use technology to add value to customers and product, quickly and with quality. To test for this, I would ask questions like: “Give me examples of how you or your team impacted the<em> </em>business.” Their answers would show how well they understood their current company’s business and how engineering can impact customers and change a company’s top-line numbers.</p><p>I also learned a lot when I let them ask questions about Faire. I love when engineering candidates ask questions about how our business works, how we make money, what our market size is, etc. If they don't ask these kinds of questions, I ask them things like: “Do you understand how Faire works?” “Why is Faire good for retailers?” “How would you sell Faire to a brand?” After asking questions like these a few times, you’ll see patterns and be able to quickly identify engineers who are business-minded and customer-focused.</p><p>Another benefit of hiring customer-focused engineers is that it’s much easier to shut down projects, start new ones, and move people around, because everyone is focused on delivering value for the customer and not wedded to the products they helped build. During COVID, our customers saw enormous change, with in-person trade shows getting canceled and lockdowns impacting in-person foot traffic. We had to adapt quickly, which required us to stop certain initiatives and move our product and engineering teams to launch new ones, such as our own version of <a href=https://www.ycombinator.com/"https://blog.faire.com/thestorefront/introducing-faire-summer-market-our-first-online-trade-show-event//">online trade shows</a>.</p><h3 id=\"c-grit\">c. Grit</h3><p>When we first started, we couldn’t afford to build the most beautiful piece of engineering work. We had to be fast and agile. This is critical when you are pre-product-market fit. Our CEO Max and a few early employees would go to trade shows to present our product to customers, understand their needs, and learn what resonated with them. Max would call us with new ideas several times a day. It was paramount that our engineers were <a href=https://www.ycombinator.com/"https://angeladuckworth.com/grit-book//">gritty and able to quickly make changes to the product. Over the three or four days of a trade show, our team deployed changes nonstop to the platform. We experimented with offerings like:</p><ul><li>Free shipping on first orders</li><li>Buy now, pay later</li><li>Buy from a brand and get $100 off when you re-order from the same brand</li><li>Free returns</li></ul><p>By trying different value propositions in a short time, our engineering team helped us figure out what was most valuable to our customers. That was how we found strong product-market fit within six months of starting the company.</p><figure class=\"kg-card kg-image-card\"><img src=https://www.ycombinator.com/"https://lh3.googleusercontent.com/CrRDf25EV8if-oP6rfEnSYeA_ttfKsayeQoM61gMOYFODZvpYsId0z2Y5RQ8z5xH4zt8UQaPBOwe1xus8oaqKQW1zxqNxz_ss9LHTpWyCc6tWsyJUm6_g6lVUtb6PkHluwNcqIU9MN3silgCLqtNHO2S8RkPcQCHBYiVPhK9Fteoiq_w9dZJqaxTqA/" class=\"kg-image\" alt loading=\"lazy\"></figure><p><em>Our trade show storefront back when we were called Indigo Fair.</em></p><h2 id=\"2-build-a-solid-long-term-foundation-from-day-one\">2. Build a solid long-term foundation from day one</h2><p>The number one impediment to engineering velocity at scale is a lack of solid, consistent foundation. A simple but solid foundation will allow your team to keep building on top of it instead of having to throw away or re-architecture your base when hypergrowth starts.</p><p>To create a solid long-term foundation, you first need to get clear on what practices you believe are important for your engineering team to scale. For example, I remember speaking with senior engineers at other startups who were surprised we were writing tests and doing code reviews and that we had a code style guide from the very early days. But we couldn’t have operated well without these processes. When we started to grow fast and add lots of engineers, we were able to keep over 95% of the team focused on building features and adding value to our customers, increasing our growth. </p><p>Once you know what long-term foundations you want to build, you need to write it down. We were intentional about this from day one and documented it in our <a href=https://www.ycombinator.com/"https://craft.faire.com/handbook-89f166841ec9/">engineering handbook</a>. Today, every engineer is onboarded using this handbook.</p><p>The four foundational elements we decided on were:</p><h3 id=\"a-being-data-driven\">a. Being data-driven</h3><p>The most important thing is to build your data muscle early. We started doing this at 10 customers. At the time, the data wasn’t particularly useful; the more important thing was to start to collect it. At some point, you’ll need data to drive product decision-making. The longer you wait, the harder it is to embed into your team.</p><p>Here’s what I recommend you start doing as early as possible:</p><ul><li>Set up data pipelines that feed into a data warehouse.</li><li>Start collecting data on how people are using your product. As you add features and iterate, record how those changes are impacting user interactions. All of this should go into a data warehouse that is updated within minutes and made available to your team. As your product gets increasingly complex, it will become more and more important to use data to validate your intuition.</li><li>We use Redshift to store data. As user events are happening, our relational database (MySQL) replicates them in Redshift. Within minutes, the data is available for queries and reports.</li><li>Train your team to use experimentation frameworks.</li><li>Make it part of the product development process. The goal is to transform your intuition into a statistically testable statement. A good place to start is to establish principles and high-level steps for your team to follow when they run experiments. We’ve set principles around when to run experiments vs. when not to, that running rigorous experiments should be the default (and when it isn’t), and when to stop an experiment earlier than expected. We also have teams log experiments in a Notion dashboard.</li><li>The initial focus should be on what impact you think a feature will have and how to measure that change. As you’re scoping a feature, ask questions like: How are we going to validate that this feature is achieving intended goals? What events/data do we need to collect to support that? What reports are we going to build? Over time, these core principles will expand.</li><li>The entire team should be thinking about this, not just the engineers or data team. We reinforced the importance of data fluency by pushing employees to learn SQL, so that they could run their own queries and experience the data firsthand.</li><li>It’ll take you multiple reps to get this right. We still miss steps and fail to collect the right data. The sooner you get your team doing this, the easier it will be to teach it to new people and become better at it as an organization.</li></ul><h3 id=\"b-our-choice-of-programming-language-and-database\">b. Our choice of programming language and database</h3><p>When choosing a language and database, pick something you know best that is also scalable long-term.<strong> </strong>If you choose a language you don’t know well because it seems easier or faster to get started, you won’t foresee pitfalls and you’ll have to learn as you go. This is expensive and time-consuming. We started with Java as our backend programming language and MySQL as our relational database. In the early days, we were building two to three features per week and it took us a couple of weeks to build the framework we needed around MySQL. This was a big tradeoff that paid dividends later on.</p><h3 id=\"c-writing-tests-from-day-one\">c. Writing tests from day one</h3><p>Many startups think they can move faster by not writing tests; it’s the opposite. Tests help you avoid bugs and prevent legacy code at scale. They aren’t just validating the code you are writing now. They should be used to enforce, validate, and document requirements. Good tests protect your code from future changes as your codebase grows and features are added or changed. They also catch problems early and help avoid production bugs, saving you time and money. Code without tests becomes legacy very fast. Within months after untested code is written, no one will remember the exact requirements, edge cases, constraints, etc. If you don’t have tests to enforce these things, new engineers will be afraid of changing the code in case they break something or change an expected behavior.<br><br>There are two reasons why tests break when a developer is making code changes:</p><ul><li>Requirements change. In this case, we expect tests to break and they should be updated to validate and enforce the new requirements.</li><li>Behavior changes unexpectedly. For example, a bug was introduced and the test alerted us early in the development process.</li></ul><p>Every language has tools to measure and keep track of test coverage. I highly recommend introducing them early to track how much of your code is protected by tests. You don’t need to have 100% code coverage, but you should make sure that critical paths, important logic, edge cases, etc. are well tested. <a href=https://www.ycombinator.com/"https://leanylabs.com/blog/good-unit-tests//">Here are tips for writing good tests</a>.</p><h3 id=\"d-doing-code-reviews\">d. Doing code reviews</h3><p>We started doing code reviews when we hired our first engineer. Having another engineer review your code changes helps ensure quality, prevents mistakes, and shares good patterns. In other words, it’s a great learning tool for new and experienced engineers. Through code reviews, you are teaching your engineers patterns: what to avoid, why to do something, the features of languages you should and shouldn’t use. </p><p>Along with this, you should have a coding style guide. Coding guides help enforce consistency and quality on your engineering team. It doesn’t have to be complex. We use a tool that formats our code so our style guide is automatically enforced before a change can be merged. This leads to higher code quality, especially when teams are collaborating and other people are reviewing code.</p><p>We switched from Java to Kotlin in 2019 and we have a comprehensive style guide that includes recommendations and rules for programming in Kotlin. For anything not explicitly specified in our guide, we ask that engineers follow <a href=https://www.ycombinator.com/"https://kotlinlang.org/docs/coding-conventions.html/">JetBrains’ coding conventions</a>.</p><p>These are the code review best practices we share internally:</p><ul><li>#bekind when doing a code review. Use positive phrasing where possible (\"there might be a better way\" instead of \"this is terrible\"; \"how about we name this X?\" instead of \"naming this Y is bad\"). It's easy to unintentionally come across as critical, especially if you have a remote team.</li><li>Don't block changes from being merged if the issues are minor (e.g., a request for variable name change, indentation fixes). Instead, make the ask verbally. Only block merging if the request contains potentially dangerous changes that could cause issues or if there is an easier/safer way to accomplish the same.</li><li>When doing a code review, ensure that the code adheres to your style guide. When giving feedback, refer to the relevant sections in the style guide.</li><li>If the code review is large, consider checking out the branch locally and inspecting the changes in IntelliJ (Git tab on the bottom). It’s easier to have all of the navigation tools at hand.</li></ul><h2 id=\"3-track-engineering-metrics-to-drive-decision-making\">3. Track engineering metrics to drive decision-making</h2><p>Tracking metrics is imperative to maintaining engineering velocity. Without clear metrics, Faire would be in the dark about how our team is performing and where we should focus our efforts. We would have to rely on intuition and assumptions to guide what we should be prioritizing. </p><p>Examples of metrics we started tracking early (at around 20 engineers) included:</p><ul><li><strong>Uptime.</strong> One of the first metrics we tracked was <a href=https://www.ycombinator.com/"https://docs.datadoghq.com/integrations/uptime//">uptime. We started measuring this because we were receiving anecdotal reports of site stability issues. Once we started tracking it, we confirmed the anecdotal evidence and dedicated a few engineers to resolve the issue.</li><li><strong>CI wait time.</strong> Another metric that was really important was CI wait time (i.e., time for the build system to build/test pull requests). We were receiving anecdotal reports of long CI wait times for developers, confirmed it with data, and fixed the issue.</li></ul><figure class=\"kg-card kg-image-card\"><img src=https://www.ycombinator.com/"https://lh3.googleusercontent.com/KiE8tjsqkFvtJFmyY_6-IinXuT1A6C4x6JBUSX9qb9nDHB9lurJZAlHocGDEi3Sx_HSHNuBxozMBljGOsNokrQIJ9Hk6ZolI39yQtKPz0yuAbue0G2weaKWXqD65_Gbal_LYuEC5TpPoGIdCGd0jflhy1yRQzuG-pxV1IePbh8LuEtvqehC1gHs5lw/" class=\"kg-image\" alt loading=\"lazy\"></figure><p><em>This is a dashboard we created in the early days of Faire to track important engineering metrics. It was updated manually by collecting data from different sources. Today, we have more comprehensive dashboards that are fully automated.</em></p><p>Once our engineering team grew to 100+, our top-level metrics became more difficult to take action against. When metrics trended beyond concerning thresholds, we didn’t have a clear way to address them. Each team was busy with their own product roadmap, and it didn’t seem worthwhile to spin up new teams to address temporary needs. Additionally, many of the problems were large in scale and would have required a dedicated group of engineers. </p><p>We found that the best solution was to build <a href=https://www.ycombinator.com/"https://www.datadoghq.com/blog/the-power-of-tagged-metrics//">dimensions so that we could view metrics by team. Once we had metrics cut by team, we could set top-down expectations and priorities. We were happy to see that individual teams did a great job of taking ownership of and improving their metrics and, consequently, the company’s top-level metrics.</p><h4 id=\"an-example-transaction-run-duration\">An example: transaction run duration</h4><p>Coming out of our virtual trade show, <a href=https://www.ycombinator.com/"https://blog.faire.com/thestudio/faire-summer-market-2021-our-global-trade-show-event-is-coming-in-july//">Faire Summer Market</a>, we knew we needed significant investment in our database utilization. During the event, site usage pushed our database capacity to its limits and we realized we wouldn’t be able to handle similar events in the future.</p><p>In response, we created a metric of how long transactions were open every time our application interacted with the database. Each transaction was attributed to a specific team. We then had a visualization of the hottest areas of our application along with the teams responsible for those areas. We asked each team to set a goal during our planning process to reduce their database usage by 20% over a three-month period. The aggregate results were staggering. Six months later, before our next event—<a href=https://www.ycombinator.com/"https://blog.faire.com/thestorefront/announcing-faires-2022-winter-virtual-trade-show-events//">Faire Winter Market</a>—incoming traffic was 1.6x higher, but we were nowhere close to maxing out our database capacity. Now, each team is responsible for monitoring their database utilization and ensuring it doesn’t trend in the wrong direction.</p><h3 id=\"managing-metrics-with-kpi-scorecards\">Managing metrics with KPI scorecards</h3><p>We’re moving towards a model where each team maintains a set of key performance indicators (KPIs) that get published as a scorecard reflecting how successful the team is at maintaining its product areas and the parts of the tech stack it owns.</p><p>We’re starting with a top-level scorecard for the whole engineering team that tracks our highest-level KPIs (e.g., <a href=https://www.ycombinator.com/"https://docs.datadoghq.com/tracing/guide/configure_an_apdex_for_your_traces_with_datadog_apm//">Apdex, database utilization, CI wait time, severe bug escapes, flaky tests). Each team maintains a scorecard with its assigned top-level KPIs as well as domain-specific KPIs. As teams grow and split into sub-teams, the scorecards follow the same path recursively. Engineering leaders managing multiple teams use these scorecards to gauge the relative success of their teams and to better understand where they should be focusing their own time.</p><p>Scorecard generation should be as automated and as simple as possible so that it becomes a regular practice. If your process requires a lot of manual effort, you’re likely going to have trouble committing to it on a regular cadence. Many of our metrics start in DataDog; we use their API to extract relevant metrics and push them into Redshift and then visualize them in Mode reports.</p><p>As we’ve rolled this process out, we’ve identified criteria for what makes a great engineering KPI:</p><ul><li><strong>Can be measured and has a believable source of truth.</strong> If capturing and viewing KPIs is not an easy and repeatable task, it’s bound to stop happening. Invest in the infrastructure to reliably capture KPIs in a format that can be easily queried.</li><li><strong>Clearly ladders up to a top-level business metric.</strong> If there isn’t a clear connection to a top-level business metric, you’ll have a hard time convincing stakeholders to take action based on the data. For example, we’ve started tracking pager volume for our critical services: High pager volume contributes to tired and distracted engineers which leads to less code output, which leads to fewer features delivered, which ultimately means less customer value.</li><li><strong>Is independent of other KPIs.</strong> When viewing and sharing KPIs, give appropriate relative weight to each one depending on your priorities. If you’re showing two highly correlated KPIs (e.g., cycle time and PR throughput), then you’re not leaving room for something that’s less correlated (e.g., uptime). You might want to capture some correlated KPIs so that you can quickly diagnose a worrying trend, but you should present non-duplicative KPIs when crafting the overall scorecard that you share with stakeholders.</li><li><strong>Is normalized in a meaningful way.</strong> Looking at absolute numbers can be misleading in a high-growth environment, which makes it hard to compare performance across teams. For example, we initially tracked growth of overall infrastructure cost. The numbers more than doubled every year, which was concerning. When we later normalized this KPI by the amount of revenue a product was producing, we observed the KPI was flat over time. Now we have a clear KPI of “amount spent on infrastructure to generate $1 in revenue.” This resulted in us being comfortable with our rate of spend, whereas previously we were considering staffing a team to address growing infrastructure costs.</li></ul><p>We plan to keep investing in this area as we grow. KPIs allow us to work and build with confidence, knowing that we’re focusing on the right problems to continue serving our customers.</p><h2 id=\"4-keep-teams-small-and-independent\">4. Keep teams small and independent</h2><p>When we were a company of 25 employees, we had a single engineering team. Eventually, we split into two teams in order to prioritize multiple areas simultaneously and ship faster. When you split into multiple teams, things can break because people lose context. To navigate this, we developed a pod structure to ensure that every team was able to operate independently but with all the context and resources they needed. </p><p>When you first create a pod structure, here are some rules of thumb:</p><ul><li><strong>Pods should operate like small startups.</strong> Give them a mission, goals, and the resources they need. It’s up to them to figure out the strategy to achieve those goals. Pods at Faire typically do an in-person offsite to brainstorm ideas and come up with a prioritized roadmap and expected business results, which they then present for feedback and approval.</li><li><strong><strong><strong>Each pod should have no more than 8 to 10 employees. </strong></strong></strong>For us, pods generally include 5 to 7 engineers (including an engineering manager), a product manager, a designer, and a data scientist.</li><li><strong>Each pod should have a clear leader. </strong>We have an engineering manager and a product manager co-lead each pod. We designed it this way to give engineering a voice and more ownership in the planning process.</li><li><strong>Expect people to be members of multiple pods. </strong>While this isn’t ideal, there isn’t any other way to do it early on. Resources are constrained, and you need a combination of seasoned employees and new hires on each pod (otherwise they’ll lack context). Pick one or two people who have lots of context to seed the pod, then add new members. When we first did this, pods shared backend engineers, designers, and data analysts, and had their own product manager and frontend engineer.</li><li><strong>If you only have one product, assign a pod to each well-defined part of the product.</strong> If there’s not an obvious way to split up your product surface area, try to break it out into large features and assign a pod to each.</li><li><strong><strong><strong>Keep reporting lines and performance management within functional teams. </strong></strong></strong>This makes it easier to maintain:</li></ul><p>\t\t(1) Standardized tooling/processes across the engineering team and balanced \t\tleadership between functions</p><p>\t\t(2) Standardized career frameworks and performance calibration. We give our \t\tmanagers guidance and tools to make sure this is happening. For example, I \t\thave a spreadsheet for every manager that I expect them to update on a \t \t\tmonthly basis with a scorecard and brief summary of their direct reports’ \t\t \t\tperformance.</p><h3 id=\"how-we-stay-on-top-of-resource-allocation-census-and-horsepower\">How we stay on top of resource allocation: Census and Horsepower</h3><p>Our engineering priorities change often. We need to be able to move engineers around and create, merge, split, or sunset pods. In order to keep track of who is on which team—taking into account where that person is located, their skill set, tenure at the company, and more—we built a tool called Census.</p><p>Census is a real-time visualization of our team’s structure. It automatically updates with data from our ATS and HR system. The visual aspect is crucial and makes it easier for leadership to make decisions around resource allocation and pod changes as priorities shift. Alongside Census, we also built an algorithm to evaluate the “horsepower” of a pod. If horsepower is showing up as yellow or red, that pod either needs more senior engineers, has a disproportionate number of new employees, or both.</p><figure class=\"kg-card kg-image-card kg-card-hascaption\"><img src=https://www.ycombinator.com/"https://lh3.googleusercontent.com/pJk7SUqsmeQLU_dYU3BrN5wMnzyHwVySmydpuiNbHgDddt_FzwwQzCQ_pQH75FX-InduoRGg5hSVhcfXZxRC3FztBZ3aF_2JnwIFMBOhjSey2cgRQEqs38oORhgZgrtwrmgO7CM-WSU_34oeyp15hdzHOrH_FAXTlFlJOt-A87J4Brce_ri3MER8RA/" class=\"kg-image\" alt loading=\"lazy\"><figcaption>.</figcaption></figure><p><em>Census.</em></p><figure class=\"kg-card kg-image-card\"><img src=https://www.ycombinator.com/"https://lh3.googleusercontent.com/N7btbx4GDkomhZp8wj0CMlTiGywqDffV6qCakK6aZEILScjRiIqjhwjV1q2AlT6bmrzU9vqo_pa1ggXn8j_C0CWsO4BEQdHoq5EcPfOhZwhe8tg1oMmmmDeYQXNrjF99WOdM5AKVTT5GAisZM_idtecOsjdXH_qQ2ezvEVRLltbkMfmk1j3qouwt7g/" class=\"kg-image\" alt loading=\"lazy\"></figure><p><em>Pods are colored either green, yellow, or red depending on their horsepower.</em><br><br>One of the most common questions that founders have is how to balance speed with everything else: product quality, architecture debt, team culture. Too often, startups stall out and sacrifice their early momentum in order to correct technical debt. In building Faire, we set out to both establish a unified foundation <em>and</em> continue shipping fast. These four guiding principles are how we did it, and I hope they help others do the same.</p>","comment_id":"6357f9044557ad0001018040","feature_image":"/blog/content/images/2022/10/BlogTwitter-Image-Template-2.jpeg","featured":true,"visibility":"public","email_recipient_filter":"none","created_at":"2022-10-25T07:56:04.000-07:00","updated_at":"2022-10-26T12:38:29.000-07:00","published_at":"2022-10-25T09:00:00.000-07:00","custom_excerpt":"Faire’s engineering team grew from five to over 100 engineers in three years. Throughout this growth, we were able to sustain our pace of engineering execution by adhering to four guiding principles.","codeinjection_head":null,"codeinjection_foot":null,"custom_template":null,"canonical_url":null,"authors":[{"id":"61fe29e3c7139e0001a710d4","name":"Marcelo Cortes","slug":"marcelo-cortes","profile_image":"/blog/content/images/2022/10/Instagram-Image-Template--Square---7-.jpg","cover_image":null,"bio":"Marcelo Cortes is a co-founder and the CTO of Faire, an online wholesale marketplace connecting mostly small brands to independent, local retailers.","website":null,"location":null,"facebook":null,"twitter":null,"meta_title":null,"meta_description":null,"url":"https://ghost.prod.ycinside.com/author/marcelo-cortes/"}],"tags":[{"id":"61fe29efc7139e0001a7116d","name":"Essay","slug":"essay","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/essay/"},{"id":"61fe29efc7139e0001a71181","name":"YC Continuity","slug":"yc-continuity","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/yc-continuity/"},{"id":"61fe29efc7139e0001a71196","name":"Technical","slug":"technical","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/technical/"},{"id":"61fe29efc7139e0001a71170","name":"Startups","slug":"startups","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/startups/"},{"id":"61fe29efc7139e0001a71158","name":"Leadership","slug":"leadership","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/leadership/"},{"id":"61fe29efc7139e0001a7114c","name":"Company Building","slug":"company-building","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/company-building/"},{"id":"62d804e33644180001d72a1f","name":"#1543","slug":"hash-1543","description":null,"feature_image":null,"visibility":"internal","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/404/"},{"id":"61fe29efc7139e0001a71155","name":"Growth","slug":"growth","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/growth/"}],"primary_author":{"id":"61fe29e3c7139e0001a710d4","name":"Marcelo Cortes","slug":"marcelo-cortes","profile_image":"https://ghost.prod.ycinside.com/content/images/2022/10/Instagram-Image-Template--Square---7-.jpg","cover_image":null,"bio":"Marcelo Cortes is a co-founder and the CTO of Faire, an online wholesale marketplace connecting mostly small brands to independent, local retailers.","website":null,"location":null,"facebook":null,"twitter":null,"meta_title":null,"meta_description":null,"url":"https://ghost.prod.ycinside.com/author/marcelo-cortes/"},"primary_tag":{"id":"61fe29efc7139e0001a7116d","name":"Essay","slug":"essay","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/essay/"},"url":"https://ghost.prod.ycinside.com/how-to-maintain-engineering-velocity-as-you-scale/","excerpt":"Faire’s engineering team grew from five to over 100 engineers in three years. Throughout this growth, we were able to sustain our pace of engineering execution by adhering to four guiding principles.","reading_time":16,"access":true,"og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"email_subject":null,"frontmatter":null,"feature_image_alt":null,"feature_image_caption":null},{"id":"6356a9c957e9f90001984b62","uuid":"32e1602f-ec89-49b0-932c-61ef6bbacfcb","title":"YC Founder Firesides: Mutiny on AI and the next era of company growth","slug":"yc-founder-firesides-mutiny-on-ai-and-the-next-era-of-company-growth","html":"<p><a href=https://www.ycombinator.com/"https://www.mutinyhq.com//">Mutiny (<a href=https://www.ycombinator.com/"https://www.ycombinator.com/companies/mutiny/">YC S18</a>) uses AI and data to convert website visitors into customers. Today, the fastest growing B2B companies such as Notion and Snowflake use Mutiny to identify ideal customers, determine sections of websites that will increase conversion, and produce copy that converts visitors into customers. </p><p>YC’s <a href=https://www.ycombinator.com/"https://twitter.com/anuhariharan/status/1557784730543632384/">Anu Hariharan</a> sat down with Mutiny co-founder and CEO <a href=https://www.ycombinator.com/"https://twitter.com/jalehr/">Jaleh Rezaei</a> to talk about their <a href=https://www.ycombinator.com/"https://twitter.com/jalehr/status/1582352047659024385/">recent acquisition</a> of Intellipse, an AI marketing platform, as well as how AI will impact the next era of growth. Throughout, Jaleh shares advice about acquisitions as a growth strategy and evolving your product with AI. </p><p>You can listen here or on <a href=https://www.ycombinator.com/"https://open.spotify.com/episode/7dy1qB7XQfOryE4kj4spGS/">Spotify, <a href=https://www.ycombinator.com/"https://podcasts.apple.com/us/podcast/160-yc-founder-firesides-mutiny-on-ai-and-the-next/id1236907421?i=1000583708925\%22>Apple Podcasts</a>, and <a href=https://www.ycombinator.com/"https://twitter.com/i/spaces/1yNxaNzAPPnKj/">Twitter.

Notion drives 60% more leads through paid marketing</a></li><li>Example 2: <a href=https://www.ycombinator.com/"https://www.mutinyhq.com/blog/the-second-lever-replays#conversion-secret-how-snowflake-runs-abm-at-scale\">Snowflake builds an ABM and enterprise marketing program</a></li></ul><p><strong>12:50</strong> - You recently shared that with data and AI, Mutiny transforms conversion from a niche A/B testing tool to a platform that every go-to-market team can use to drive efficient growth at scale. What does that mean, and how have you leveraged the advances in AI over the last four years? </p><ul><li>When you can give the entire go-to-market team x-ray vision into every visitor and how they are converting – and then pair that insight with the ability to change the website for different segments – every team will make the website a core part of their strategy to drive more revenue. Mutiny uses AI to give teams this insight and answer questions like: What segments should I prioritize? What parts of the website should I change? What copy will resonate? Where should I focus? </li></ul><p><strong>17:00</strong> - At Mutiny when looking at data, when do you know the right questions to ask and when do you say these are not questions we need to optimize now?</p><ul><li>In the early days, one of the most valuable things we did was follow our customers’ growth teams. We would attend team meetings, watch them use our product, and ask questions. It became clear what we should build for our customers. </li></ul><p><strong>20:30</strong> - Since you started Mutiny, what are some of the advances in AI that you’ve leveraged? </p><ul><li>We did things that didn't scale in the early days to solve customers’ problems. As our customers grew, our data set grew and we used AI models and inputs to improve our recommendation engines and service a broader customer base. Today, we can build models that tell a user where on the website they should make changes and write personalized copy leveraging GPT-3. </li></ul><p><strong>29:10</strong> - Did you have moments when you felt Mutiny could be doing more with the advances being made in AI? </p><ul><li>We saw an opportunity to marry our proprietary data set with GPT-3 to produce highly personalized copy. </li></ul><p><strong>32:15</strong> - GPT-3 was an inflection point for Munity. What is the next inflection point? </p><ul><li>There are a lot of opportunities with DALL-E, as visuals are important in marketing.</li></ul><p><strong>36:30</strong> - Do you have cautionary advice on how to think about using technologies like GPT-3 and DALL-E for founders dabbling in AI? </p><ul><li>Think through the ultimate long-term vision of the product and the long-term defensibility of the business. And launch fast, as technology develops quickly. </li></ul><p><strong>38:40</strong> - What advice do you have for founders in terms of leveraging OpenAI, GPT-3, etc. while focusing on the long-term vision? </p><ul><li>Your vision and long-term view is separate from your day-to-day execution. Your long-term vision (i.e. the opportunity and what you’re trying to create over the course of a decade) provides clarity around where you’re trying to go and brings other people along with you, like your investors and employees. Day-to-day, you’re focused and executing quickly – and not always thinking about the ten year vision when you’re building V1.</li></ul><p><strong>43:45</strong> - You decided to grow your team by acquiring Intellipse. And now, Mutiny has one of the larger engineering teams with production experience in modern marketing AI technologies. Why did you decide to pursue an acquisition? </p><ul><li>Founders have to look for inflection points where something happens in the market leading to the “old way” no longer being as good. And as a result, a much larger portion of the market is open to a new and better way. We’re in a recession, and this is an inflection point for Mutiny. Companies need to convert every dollar to a customer, and Mutiny has built a product that makes marketing dollars more efficient. We can accelerate our road map with the acquisition of Intellipse</li></ul><p><strong>46:40</strong> - How did you know you wanted to work with the Intellipse team so much that you had to go through an acquisition?</p><ul><li>We were interested in the Intellipse team and the skills the team had developed. Their CTO and senior engineers had a unique experience with marketing AI and newer technologies, like GPT-3.</li><li>The personality and values of the founder spreads in an organization and becomes the company culture. After getting to know the founder and the free am, it was evident the two companies had a similar culture and shared values – and we’d be able to bring this team in and enhance our culture.</li></ul><p><strong>50:15</strong> - How long did it take to assess the culture? </p><ul><li>We spent the same amount of time with each individual as if we were hiring them onto the team through our typical recruiting process.</li></ul><p><strong>51:30</strong> - Do you expect to acquire more companies in the future? And how should founders and CEOs determine whether this strategy is right for their company? </p><ul><li>Be clear about your goals and why an acquisition is the right way to achieve those goals. When a company is working toward a similar goal – building something we would have done ourselves – it is a successful acquisition. With Intellipse, the team shared similar goals and company culture, and could accelerate our timing.</li><li>We want to hire founders onto our product team who are user focused and move quickly. Founders can focus their entrepreneurial energy on building a product and growing that business area within Mutiny. </li></ul><p><strong>54:55</strong> - What are your thoughts about how AI will impact the next ten years? </p><ul><li>There has been enough productization of backend AI technologies that as a founder you can tap into AI to accelerate the product you want to build and the value you give to customers. From a user and growth perspective, AI enables us to automate many of the tasks no one wants to do. And for those who aren’t technical – but understand what they are trying to do – they can now be self sufficient.</li></ul>","comment_id":"6356a9c957e9f90001984b62","feature_image":"/blog/content/images/2022/10/BlogTwitter-Image-Template-1.jpeg","featured":true,"visibility":"public","email_recipient_filter":"none","created_at":"2022-10-24T08:05:45.000-07:00","updated_at":"2022-10-25T08:44:16.000-07:00","published_at":"2022-10-24T09:25:31.000-07:00","custom_excerpt":"YC’s Anu Hariharan sat down with Mutiny co-founder and CEO Jaleh Rezaei to talk about their recent acquisition of Intellipse, an AI marketing platform, as well as how AI will impact the next era of growth.","codeinjection_head":null,"codeinjection_foot":null,"custom_template":null,"canonical_url":null,"authors":[{"id":"61fe29e3c7139e0001a7106f","name":"Y Combinator","slug":"yc","profile_image":"/blog/content/images/2022/02/yc.png","cover_image":null,"bio":null,"website":null,"location":null,"facebook":null,"twitter":null,"meta_title":null,"meta_description":null,"url":"https://ghost.prod.ycinside.com/author/yc/"}],"tags":[{"id":"61fe29efc7139e0001a71170","name":"Startups","slug":"startups","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/startups/"},{"id":"61fe29efc7139e0001a71175","name":"Interview","slug":"interview","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/interview/"},{"id":"61fe29efc7139e0001a71181","name":"YC Continuity","slug":"yc-continuity","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/yc-continuity/"},{"id":"61fe29efc7139e0001a71152","name":"Founder Stories","slug":"founder-stories","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/founder-stories/"},{"id":"61fe29efc7139e0001a71176","name":"Podcast","slug":"podcast","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/podcast/"},{"id":"6312238da32f070001d502c0","name":"#2014","slug":"hash-2014","description":null,"feature_image":null,"visibility":"internal","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/404/"},{"id":"61fe29efc7139e0001a71155","name":"Growth","slug":"growth","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/growth/"},{"id":"61fe29efc7139e0001a71158","name":"Leadership","slug":"leadership","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/leadership/"}],"primary_author":{"id":"61fe29e3c7139e0001a7106f","name":"Y Combinator","slug":"yc","profile_image":"https://ghost.prod.ycinside.com/content/images/2022/02/yc.png","cover_image":null,"bio":null,"website":null,"location":null,"facebook":null,"twitter":null,"meta_title":null,"meta_description":null,"url":"https://ghost.prod.ycinside.com/author/yc/"},"primary_tag":{"id":"61fe29efc7139e0001a71170","name":"Startups","slug":"startups","description":null,"feature_image":null,"visibility":"public","og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"codeinjection_head":null,"codeinjection_foot":null,"canonical_url":null,"accent_color":null,"url":"https://ghost.prod.ycinside.com/tag/startups/"},"url":"https://ghost.prod.ycinside.com/yc-founder-firesides-mutiny-on-ai-and-the-next-era-of-company-growth/","excerpt":"YC’s Anu Hariharan sat down with Mutiny co-founder and CEO Jaleh Rezaei to talk about their recent acquisition of Intellipse, an AI marketing platform, as well as how AI will impact the next era of growth.","reading_time":5,"access":true,"og_image":null,"og_title":null,"og_description":null,"twitter_image":null,"twitter_title":null,"twitter_description":null,"meta_title":null,"meta_description":null,"email_subject":null,"frontmatter":null,"feature_image_alt":null,"feature_image_caption":null}]},"url":"/blog/learnings-of-a-snapdocs-aaron-king-on-navigating-market-cycles","version":null,"rails_context":{"railsEnv":"production","inMailer":false,"i18nLocale":"en","i18nDefaultLocale":"en","href":"https://www.ycombinator.com/blog/learnings-of-a-snapdocs-aaron-king-on-navigating-market-cycles","location":"/blog/learnings-of-a-snapdocs-aaron-king-on-navigating-market-cycles","scheme":"https","host":"www.ycombinator.com","port":null,"pathname":"/blog/learnings-of-a-snapdocs-aaron-king-on-navigating-market-cycles","search":null,"httpAcceptLanguage":"en, *","applyBatchLong":"Winter 2024","applyBatchShort":"W2024","applyDeadlineShort":"October 13","ycdcRetroMode":true,"currentUser":null,"serverSide":true},"id":"ycdc_new/pages/BlogPage-react-component-42511540-96ac-422f-a4d3-9001bff08e22","server_side":true}" data-reactroot="">

Learnings of a CEO: Snapdocs’ Aaron King on navigating market cycles

by Lindsay Amos1/30/2023

Welcome to the fourth edition of Learnings of a CEO. You can read previous editions here.

Snapdocs is the leading digital closing platform for the mortgage industry. Today, the company touches 25% of all US real estate transactions and is valued at $1.5B. Founder and CEO Aaron King and his team have expertly navigated fundraising and market cycles. We sat down with Aaron to hear his insight into getting a business up and running with minimal outside funding and building through volatile market conditions.

Why did you decide to raise minimal funding early in the company’s history?

I never considered funding to be a requirement for building — but I also didn't know much about fundraising early on in the company’s history. Snapdocs was started as a side project a couple of years before ever thinking about applying to YC. By the time I applied, we had a live product, customers, and revenue. Even after YC, we didn’t raise much immediately. We stayed focused on building and then raised a seed round later in the year.

It wasn’t until three years later that we raised our Series A. By then, we had spent about $1MM of our seed round and were at a $5MM revenue run rate. Around that time we started working with much larger customers, and it was clear we would need more capital to be successful in this bigger market. So, we raised our Series A. After we closed the round, our lead investor revealed how capital efficient we had been compared to our peers.

Do you feel you had to ruthlessly prioritize when building the product because you didn't have the capital?

Yes, and I’ve learned that you should take the same approach even when you do have the capital to be less disciplined. Back then, ruthless prioritization was our only option. We couldn’t afford to build features that weren’t essential. There were always a hundred distractions that would result in a broader, less focused product. But our capital constraints kept us focused on going deep with our paying customers. That helped us avoid the common trap of building products no one wanted.

It also meant that when we decided to build a product, we had to think about the smallest version of that product in order to quickly ship. That helped ensure we had a short feedback loop from our users and ensure our resources were continuously being invested in building the right features. Looking back, I’m amazed at how much we were able to accomplish without spending much capital.

Being capital constrained forced good behaviors that served us well even after we raised more funding. We continue to be thoughtful about every dollar we spend. But, there is a cost to this approach, and we’re paying for it today. We built many things that weren't engineered for scale or flexibility. However, now we can afford to reengineer those unscalable solutions because we built something people want.

What did your product cycles look like before you raised your Series A?

We were always heavy on customer involvement when building product. We spent a lot of time in our customers’ offices watching them use what we were building and understanding their work. We also kept a lot of our prospects in the loop as we built new features. Some of the best feedback came from people who had chosen to not yet work with us. Responding to that feedback with a killer feature was a great way to ultimately get them on board.

We built a lot of trust and rapport with these early customers, and the in-person interactions helped immensely. As a result, they would call one of us the moment they thought there was a problem or if they thought a competitor was doing something compelling. Customer churn for Snapdocs has always been incredibly low as a result.

We created a disciplined product release process, even in those early days, but we were still able to move quickly. We shipped code every day, sometimes multiple times a day. Customers were impressed by how quickly we could respond to issues and feedback.

Interestingly, not having too much pressure from investors early on allowed us to experiment more in an underappreciated part of our market. The Serviceable Available Market (SAM) of our initial product was roughly only $20MM, but we believed it would allow us to expand into more critical parts of the mortgage ecosystem. It was the type of opportunity that would be hard to discover through market analysis or spreadsheet exercises. You had to get deep into the problem set to see the opportunity and develop the right strategy—and that ultimately worked to our advantage.

Founders need capital to hire employees. As a bootstrapped company, what was your strategy around hiring?

Hiring was hard, but we did a few things that worked well. Even before the company could afford full-time employees, I worked with talented contractors. I also leaned on friends to help me work through both technical and business challenges. Someone would come over and whiteboard with me or we’d get into the code and work through a problem.

When I could afford to hire full-time employees, I treated them like founding team members. I was generous with equity and shared everything about the potential and challenges of the business. We built a lot of trust as a small team. Getting a few really good people into the company early on was foundational to the company’s success.

The first person to join full-time was an engineer I had worked with in a previous role (and one of the friends that would help in those early days). The second and third hires were applicants from job postings on Hacker News. All three turned out to be excellent. None of us initially had large networks in the startup world, so most of our early hiring involved lots of interviews and hiring a few of the wrong people. We couldn’t attract well-known talent and took risks; invested in people we thought had a lot of potential.

One mistake I made in the early years was being too timid to approach more of the people I respected. I should have tried to convince them to quit their successful jobs and join our small (yet risky at the time) startup. I’m fearless on this approach now, but back then I was intimidated to try to convince a friend to join a company that might fail. In hindsight, I did them a disservice by not trying to recruit them. The truth is that these people are smart and you’re not harming anyone by sharing your vision and the potential of the company with them. As long as you’re honest and transparent about the inherent challenges, you should give them the opportunity to take a risk on you.

As Snapdocs grew, it became easier to pull from the team’s networks. We continued to build a lot of trust within the team, and they started referring their friends to apply. Eventually, we attracted well-known investors, and that, along with our culture and growth, made hiring easier.

Because we were capital constrained, we also didn’t hire anyone until there was a clear and painful need. It made running the company harder because we were all spread thin but ultimately made us incredibly productive, as it meant we were always working on the most important things.

How have you navigated different market conditions? When do you decide to react?

A big part of our success has come from selectively ignoring some market changes while reacting quickly to others. It has always been a question of how the change aligns with our resources, vision, and north star metric of market share growth.

For example, the biggest and most dynamic change we regularly experience are fluctuations in the number of mortgages that happen in a given month or year. This can change quickly based on a host of economic factors. When we are well-resourced and growing fast, we can ignore some of those market downturns and stay focused on market share growth — knowing we have the momentum and capital to power through it. Other times we’ve had to scale up or scale back based on the size of the fluctuation.

But other market dynamics can change quickly too, like the industry’s appetite for new technologies and the competitive landscape. There have been times when the market was demanding a technology but we believed there were underlying factors in the industry that would prevent that tech from scaling. If we built the technology, it would pull resources away from the priorities that drove us toward our long-term goals. And so, sometimes to the protests of our sales team, we ignored it or invested minimally in these trendy areas. By doing so, we were able to stay focused on the things that were truly going to transform the industry.

It’s also worth noting that navigating change was relatively easy in the first few years of building the company. It was a lot easier to adjust course on company direction or strategy when the team was smaller and could all fit in the same room. The product cycles were relatively short and malleable. The cost of making a change was low.

As the company has grown, we’ve had to be a lot more thoughtful and methodical about changing the speed or direction of the business as we react to market changes. The cost of making a change has increased a lot. Investments take longer to play out. Changes to headcount take longer to scale up or down. There are more people on the team and more layers in the organization to communicate the change through.

In March 2020, Snapdocs made a huge shift because of changes you were seeing in the housing market. How did you communicate this shift to your team and ensure their goals were aligned with the new priorities?

COVID accelerated demand for our product, but with that came a shift in what our customers wanted from a platform like ours. We had to expand quickly to serve their needs, and we had to pivot our roadmap on a dime. It’s a testament to the team that we were able to pull that off.

To make decisions quickly and then communicate them, we worked in concentric circles. We started by discussing the change in a smaller group of 3-4 people. This is where the hardest and messiest conversations took place. We moved quickly to define the problems and opportunities and set a direction for the company. We then looped in the senior leadership team for further discussion and to arm them with everything they needed to share the directional changes with their teams. Finally, we held a company-wide meeting to share the new direction and answer questions. All of this happened over the course of about 2 weeks.

Now, our business required more speed and flexibility as information was coming in and changing week on week. We dealt with this by creating temporary pods of 4-5 team members focused on solving specific challenges that would spin up for a few weeks and then dissolve once the challenge was addressed. We also increased the frequency of our company-wide all-hands meetings from monthly to weekly so we could keep the whole company up to speed.

Luckily we had a deep culture of transparency that goes back to the beginning of the company. We’ve always tried to share everything with our entire team — our cash balance, monthly growth rate, burn, our biggest challenges. This got harder as the team grew, but we’ve largely continued this transparency to today. It’s much easier to be transparent in times of great change if you've laid a foundation of trust and transparency in the past.

We also worked hard to be intellectually honest about the growth we were experiencing. It’s easy to take credit when the business accelerates, but our message to the team wasn't, “Look at how great we're doing.” The message was closer to, “This industry works in cycles. We're in an up cycle now and that's great. There's going to be a down cycle. We don't know when or how strong it's going to be. But we should not overly congratulate ourselves for the current situation, just as we shouldn’t be too hard on ourselves when we’re fighting through an inevitable downturn in the future.”

In 2021, Snapdocs announced a Series D round. How did this change your mentality around resources?

It was clear that the pandemic would be an accelerator for our business, and we needed to move fast to stay ahead of the market. We went from being frugal to raising larger rounds of capital and hiring seasoned executives who could help us scale. It’s important for companies to evolve at the right points in time and ask themselves, “Is what I did yesterday the thing that's going to get me to where I need to be tomorrow?”. We asked that question and decided we needed to change parts of our culture and capital investment strategy if we wanted to win.

When we raised capital in 2021, transactions on Snapdocs had steadily increased to millions of closings a year and thousands of lenders and title companies were using our technology every month. Demand for mortgages throughout the pandemic was strong, and we deployed an intentional strategy of prioritizing effectiveness over efficiency. We needed to get aggressive and expand our market position, which required capital.

The market turned again later in the year, with demand for mortgages cooling. It was clear that it was time to go back to some of our old ways of doing things. We ditched the motto of being effective over being efficient. This meant a return to ruthless prioritization of our focus. We shifted away from investing so heavily in future scale as we wouldn’t need to tap into these systems for a few years.

I find it helpful to remember that market fluctuations are normal and unavoidable. Startups should scale up at times and scale back at others. It’s hard and painful. There’s nothing easy or enjoyable about being understaffed to meet customer demand on one side, or needing to let team members go on the other. But these ups and downs are natural and a necessary part of building an enduring company. In a startup, you’re always making hard decisions based on insufficient information. You’re never going to be able to perfectly predict the future. You need to keep making the best decisions you can — knowing all the while that you may be wrong and need to change course again once the future becomes clearer.

Author

  • Lindsay Amos

    Lindsay Amos is the Senior Director of Communications at Y Combinator. In 2010, she was one of the first 30 employees at Square and the company’s first comms hire.