# I Invested in a Company Then It Failed: Here Is What Happened **TL;DR:** I invested in a B2B SaaS company with strong early traction, a credible founding team, and a defensible wedge. Eighteen months later, it was dead. This post is an honest post-mortem — what I saw when I invested, what I ignored, what the founders got wrong, and the specific changes I made to my angel investing process as a result. If you are writing checks as an angel investor, this will hurt to read and probably save you money. --- ## Table of Contents - [The Setup: Why I Got Excited](#the-setup) - [The Investment Thesis](#the-investment-thesis) - [Early Signs I Ignored](#early-signs-i-ignored) - [What Actually Went Wrong](#what-actually-went-wrong) - [The Doubling Down Decision](#the-doubling-down-decision) - [The Final Months](#the-final-months) - [The Post-Mortem Conversation](#the-post-mortem-conversation) - [Financial Outcome](#financial-outcome) - [What I Changed About My Investing Process](#what-i-changed) - [Lessons for Other Angel Investors](#lessons-for-angel-investors) - [FAQ](#faq) --- ## The Setup: Why I Got Excited {#the-setup} Let me call this company Meridian. It was a workflow automation platform for mid-market professional services firms — law firms, accounting practices, and consultancies with 50 to 500 employees. The founders had noticed that these businesses were running critical client workflows on a combination of email threads, spreadsheets, and legacy software that had not been updated since 2009. Their pitch was clean: replace the chaos with a single, configurable workflow layer that integrates with the tools these firms already use. The pitch deck was one of the better ones I had seen that year. Not because it was beautifully designed — it was fine — but because the market section was grounded in specifics. They had interviewed 47 professional services firms over three months before writing a single line of code. They had documented the exact workflows that were broken, the cost of mistakes in those workflows (compliance failures, missed client deadlines, billing leakage), and the willingness-to-pay signals they had received during those conversations. The founding team was two people. The CEO had spent six years at a mid-size management consultancy, which meant he understood the buyer intimately. The CTO had been an engineering lead at a Series B SaaS company and had built integrations infrastructure before. These were not two people guessing at a problem. They had lived it from different angles. On paper, the [founder-market fit signals](/blog/angel-investing-checklist-before-investing) were nearly all green. By the time I met them, they had four paying customers, $14,000 in monthly recurring revenue, and a handful of design partners who were actively shaping the product roadmap. The check size I was writing was small enough that I did not need to do deep diligence. But I did it anyway — or I thought I did. --- ## The Investment Thesis {#the-investment-thesis} Here is what I wrote in my investment memo at the time, paraphrased: > Meridian is attacking a large, underserved market of professional services firms that have been ignored by enterprise software vendors because the segment is too fragmented to land large contracts and too operationally complex for self-serve tools. The founding team has an unusual combination of domain knowledge and technical depth. Early revenue signals are promising. The product is selling to a rational buyer who pays on value, not budget cycles. The specific things I liked: **The buyer was economically rational.** When a law firm makes a compliance mistake, the partner on that matter may face sanctions. When a consultancy misses a client deliverable because someone dropped a thread in a 200-email chain, they lose the client. The pain was real and measurable. That makes it easier to sell because you are not fighting for attention — you are solving a problem with a calculable cost. **The wedge was defensible.** They were not trying to replace every piece of software in the firm on day one. They were inserting themselves into the part of the workflow where the most errors occurred: client intake and matter setup. Once you own that step, you are the source of truth for everything downstream. That is a good place to start. **Early revenue was growing.** They had gone from $0 to $14K MRR in about five months. The growth rate was not explosive, but it was consistent and each new customer had come through referral. For a B2B product selling into a conservative buyer, referral-driven growth is the most trustworthy signal you can see at this stage. **The market structure favored a new entrant.** The incumbent software in this space was genuinely bad. I tried the demo of the leading competitor and could not believe anyone was paying for it. The UI looked like it had been designed in 2005 and the integration story was held together with CSV exports. Meridian had a real technical advantage. I wrote the check. --- ## Early Signs I Ignored {#early-signs-i-ignored} This is the part that is hard to write because everything I am about to describe was visible. I saw these signals. I rationalized each of them. ### The Sales Cycle Was Longer Than They Admitted During the pitch, the founders said their typical sales cycle was six to eight weeks. When I looked more carefully at the customer list, I noticed that three of their four paying customers had been design partners first — relationships that started four to six months before the contract was signed. The one customer who was not a prior design partner had taken twelve weeks to close. I asked about this and the CEO explained it away: "Design partners moved faster because we were building features they requested. Pure sales cycles will compress as the product matures." That sounded reasonable. In retrospect, what he was describing was not a sales cycle problem — it was a trust problem. Professional services buyers are fundamentally conservative and risk-averse. They were not going to put their client workflows on a platform built by a two-person startup without extensive hand-holding. The [design partner model had masked how hard actual sales were](/blog/how-to-achieve-product-market-fit) going to be. ### The Champion at Each Customer Was a Specific Person, Not a Role Every one of their customers had a specific internal champion — usually a director of operations or a firm administrator who was particularly frustrated with the status quo and particularly comfortable with new software. When I asked who would own the tool if that person left, the answer was vague. This is a structural fragility that looks fine until it is not. If your product's adoption depends on a specific person at a customer rather than being embedded in a process, you are one personnel change away from losing that customer. ### The CTO Was Already Stretched Thin This was subtle but in retrospect the clearest signal of all. In my early conversations with the team, the CTO would reference things on the roadmap and then qualify them: "We will get to that once I finish the billing infrastructure" or "That is on the list once I have some breathing room." He was a senior engineer managing the full technical load of the company alone. The CEO had no technical background, which meant the CTO was also the only person who could evaluate technical risks or make architectural decisions. This setup works when the technical scope is narrow. It stops working the moment you [hit a technical problem that requires more than one person's attention](/blog/managing-technical-debt-ai-startups). ### Revenue Growth Stalled After Month 6 When I invested, they were at $14K MRR. I did a check-in call three months later and they were at $17K MRR. Another three months after that: $19K MRR. The growth rate had gone from 40% month-over-month in the early days to under 5%. I asked about the pipeline and the CEO described several "almost closed" deals. One had been almost closed for six weeks. I wrote a note to myself that said "growth stalling — watch closely." Then I did nothing. --- ## What Actually Went Wrong {#what-actually-went-wrong} The failure had four distinct causes. Each one alone might have been survivable. Together, they were not. ### 1. The Market Was Larger but Harder Than the Research Suggested The 47 interviews before product development had done a good job of confirming the problem. They had done a poor job of stress-testing the solution. The founders had validated that firms were frustrated with their current tools. They had not validated that those firms were willing to go through the organizational change required to adopt a new workflow platform. Professional services firms, it turned out, had a deep cultural resistance to changing how they worked. Partners had years of ingrained habits. The associates who would actually use the tool every day had no input into the buying decision. And the partners who made the buying decision were the people who were least affected by the workflow chaos because they had assistants to manage the chaos for them. This is a classic B2B trap: the person who feels the pain most acutely is not the person with budget authority. And the person with budget authority does not feel enough pain to prioritize change management. ### 2. The Product Required More Change Management Than They Could Afford to Deliver Every successful customer implementation required 40 to 80 hours of onboarding work. The CEO was doing most of this himself because there was no customer success hire. As the company tried to scale from 4 customers to 10, he was spending so much time on implementation that he could not do outbound sales. Pipeline dried up. The company was caught in a loop: no time to sell because of implementation burden, no revenue to hire implementation help because not enough sales. They tried to solve this by [raising prices (which they needed to do anyway)](/blog/growth-plateau-diagnostic) but that made the sales cycle even longer. Higher price, more scrutiny, more internal sign-off required. ### 3. A Technical Debt Crisis Hit at Exactly the Wrong Moment Around month 10, the CTO informed the CEO that the integration layer they had built during the earliest days of the product — written quickly to get design partners live — was starting to break under load. Not catastrophically, but reliably. Certain workflow triggers were firing twice. Data was occasionally out of sync between Meridian and the connected tools. For any startup this is a painful moment. For a startup selling to professional services firms on the premise of reliability and compliance, it was nearly fatal. Two customers reached out within the same week with complaints about data integrity issues. The CTO spent six weeks in firefighting mode. No features shipped. No integrations improved. One of the two customers who complained did not renew. ### 4. The Founding Team Started to Fracture This is the most painful part to write because I watched it happen and could not stop it. The CEO and CTO had different theories about what to do. The CEO believed the answer was to pivot toward a narrower vertical — focus exclusively on law firms, build law-specific features, and charge more for a specialized product. The CTO believed the product needed to be rebuilt with a proper technical foundation before any new vertical focus would matter. Both of them were right. Neither of them could convince the other. The conversations became less frequent and more formal. The CEO started making product decisions without looping in the CTO. The CTO started job-hunting. Co-founder breakdown is one of the most common and least preventable failure modes — the [Founder Challenges Checklist](/blog/founder-challenges-checklist) documents several early warning patterns that, in retrospect, were present here from month 8 onward. I found out about the job-hunting from a mutual connection, not from the founders. By that point, the company had four months of runway. --- ## The Doubling Down Decision {#the-doubling-down-decision} When the technical debt crisis became visible in month 11, the CEO reached out to investors for a small bridge round. The ask was $150K to buy time to fix the technical foundation and close a few deals in the pipeline. This is one of the hardest decisions in angel investing: do you put more money into a struggling company to give it a chance, or does putting more money in just delay the inevitable and deepen your losses? Here is how I thought through it at the time: **Arguments for participating in the bridge:** - The market problem was real and the competition was still weak - Two pipeline deals seemed genuinely close to closing - The technical debt was fixable with focused effort — it was not an architectural catastrophe - A $150K bridge was small enough that if it failed, the additional loss was manageable relative to the potential upside if it worked **Arguments against:** - The founding team dynamic was deteriorating and no amount of money fixes a co-founder relationship breakdown - The company had not demonstrated it could close deals at the pace needed to become self-sustaining - The implementation burden problem had no clear solution - The CTO was clearly disengaged I participated in the bridge. Half the round closed. The other half of the investors declined. In retrospect, the decision was wrong. Not wrong because the logic was flawed — each individual argument was reasonable — but wrong because I was doing what investors often do when they have conviction in a deal: I was looking for reasons to believe it could still work rather than looking honestly at whether the structural problems had solutions. --- ## The Final Months {#the-final-months} The bridge bought four months. In those four months: - The CTO formally resigned in month 13. He gave two months of notice and left on reasonably good terms, but the transition was brutal. The CEO scrambled to find a contract engineer to keep the product stable. The contract engineer, who was good, could not work full-time. - One of the two pipeline deals that looked close fell through. The firm had been acquired and the new parent company froze all software procurement. - The second pipeline deal closed, but at a lower price than expected because the champion had gone to bat for a discount in exchange for a case study. - The new MRR from that deal brought total MRR to $22K. Still not enough to get to default alive. - The CEO had conversations with three potential acqui-hire targets. None of them moved past initial conversations because the technology was tightly coupled to the domain and the team had shrunk to essentially one full-time person. The broader [patterns behind angel investing wins and losses](/blog/exits-and-learnings-angel-investing) show how often this particular sequence — technical debt, co-founder breakdown, failed bridge — appears in the loss column. In month 17, the CEO sent an email to investors saying he was winding down the company. He had found a job as VP of Operations at a growth-stage startup. He thanked everyone for their support and apologized for the outcome. It was a gracious and honest email. I appreciated that he sent it. Many founders do not. --- ## The Post-Mortem Conversation {#the-post-mortem-conversation} A few weeks after the wind-down announcement, I asked the CEO if he would be willing to do a post-mortem call. He agreed. It was one of the most useful investor conversations I have had — and also one of the most uncomfortable. Some of the things he said that stayed with me: **On the sales cycle problem:** "I knew the sales cycles were longer than I was saying. I was embarrassed to admit it because I had already told investors what the number was. I kept thinking we were one product improvement away from it getting better. We were not." **On the implementation burden:** "I should have priced implementation as a separate line item from the start and charged enough to hire someone to do it. Instead, I included it in the software price to make the sale easier and then trapped myself doing it for free forever." **On the co-founder dynamic:** "We should have had the hard conversation about disagreements six months earlier than we did. By the time we were fighting about strategy, it was not really about strategy anymore. It was about trust that had eroded slowly." **On investors:** "The most helpful thing an investor did was tell me directly, in month 10, that he did not think the path to $1M ARR was visible and that I should be thinking about what a soft landing looked like. I did not listen to him. I wish I had." I was not that investor. I wish I had been. --- ## Financial Outcome {#financial-outcome} I will not share the exact dollar figures but I will be honest about the structure: - My initial check was in the pre-seed round at a valuation I thought was reasonable for the traction they had shown. - I participated in the bridge at a flat valuation, which meant my ownership percentage stayed the same but the company's implied value had not improved from the prior round despite a year of work. - Total loss on the investment: 100%. There was no acqui-hire. There were no assets worth recovering. The software was shut down. The customers migrated back to spreadsheets or to a competitor. - The financial loss was within a range I had pre-accepted as possible when I invested. Angel investing has a power law distribution of outcomes and losses on individual deals are not the exception — they are the norm for most of the portfolio. What stung was not the money. It was the feeling that I had seen the warning signs and not acted on them. --- ## What I Changed About My Investing Process {#what-i-changed} This is the most important section if you are an angel investor reading this post. Here are the concrete changes I made after Meridian. ### Change 1: I Now Ask About Sales Cycles Differently Before Meridian, I would ask "What is your typical sales cycle?" and accept whatever number I heard. Now I ask: "Walk me through every customer you have ever sold, from first conversation to signed contract, and tell me how long each one took." Then I do the math myself. The average number the founder volunteers is almost always lower than the actual median, because founders remember the fast ones more vividly. ### Change 2: I Audit Champion Risk in Every Deal For every B2B investment I consider, I now ask: "If the person who championed this purchase left the company tomorrow, what would happen to your contract?" The answer tells you whether you have a product sale or a relationship sale. Relationship sales can be fine at small scale. They do not scale. ### Change 3: I Require a Technical Architecture Conversation for Every Technical Investment I am not a deeply technical investor but I know enough to ask the right questions. I now insist on a 45-minute conversation specifically about the technical architecture of every company I invest in — what was built to move fast and what was built to last, where the debt is, and what the plan is for addressing it. I was not asking these questions at Meridian. I should have been. ### Change 4: I Watch Co-Founder Dynamics More Carefully Co-founder breakups are one of the leading causes of early-stage startup death. I now explicitly ask co-founders, separately if possible, how they make decisions together and what the last significant disagreement they had was and how they resolved it. The content of the answer matters less than the ease with which they give it. When founders struggle to name a real disagreement they have resolved, that is a red flag. ### Change 5: I Set a Clearer Go/No-Go Threshold Before Bridge Decisions Before Meridian, my bridge decision process was informal. Now I have a written framework: before I participate in a bridge or follow-on, I have to write a paragraph explaining why the core thesis is still intact and what specific evidence from the past 90 days supports the conclusion that the investment of additional capital will change the outcome. If I cannot write that paragraph, I do not write the check. ### Change 6: I Am More Direct About Wind-Down Conversations The investor who told the CEO of Meridian to think about a soft landing was doing the right thing. I should have had a version of that conversation. Now I do. It is uncomfortable and founders do not like hearing it. But a soft landing with some team members hired and some customers transitioned is better than a catastrophic shutdown with burned employees and abandoned customers. --- ## Lessons for Other Angel Investors {#lessons-for-angel-investors} If you are writing your first or fifth angel check, here is what this experience taught me that I believe applies beyond my specific situation. For the systematic pre-investment process I now run before every check — including the 5 non-negotiable checks across founder-market fit, timing, and unit economics — see [The 5 Angel Checks I Run Before Writing a Check](/blog/angel-investing-checklist-before-investing). ### Your Job Is to Be Right About the Risks, Not Just the Opportunity It is easy to fall in love with what could go right. Experienced investors spend equal time on what could go wrong. Before you invest, write down the three most likely reasons this company fails and then stress-test whether those risks are mitigated. If you cannot write down the failure modes clearly, you do not understand the investment well enough to make it. ### Momentum in a Pitch Meeting Is Not Evidence of Product-Market Fit A great founder can make a struggling company look like a rocket ship in a pitch. The energy, the confidence, the coherent narrative — all of it is persuasive. None of it is data. Separate your emotional reaction to the founder from your analytical assessment of the business. Write the investment memo before the final meeting, not after. ### The Companies That Fail Fastest Are the Ones Where Multiple Things Go Wrong at Once Meridian did not fail because of one catastrophic mistake. It failed because a sales challenge, an operational scaling problem, a technical debt crisis, and a co-founder breakdown all intersected within a six-month window. Each problem individually was solvable. Together, they were not. When you are evaluating a deal, ask yourself: if two things go wrong at the same time, does this company have the resources — human, financial, relational — to handle them simultaneously? ### The Investors Who Help Most Are Not the Ones Who Are Most Encouraging The most useful investor in Meridian's life was the one who told them the hard truth. Encouragement from investors is cheap. Honest, specific, uncomfortable feedback is rare and valuable. If you are investing in early-stage companies, be willing to be the person who says the thing no one else is saying. Your founder will not thank you at the time. They will thank you later, or they will not, but either way you will have done the right thing. ### Know What "Help" Means for Each Investment I invested in Meridian and offered to help with sales introductions and product feedback. I made a few introductions that did not go anywhere and gave product feedback that was sometimes acted on. What the company actually needed was someone who had scaled a B2B SaaS company through the implementation burden problem — someone who had been in that loop and found a way out. I did not have that specific experience. I should have been clearer about what kind of help I could actually provide and tried harder to connect them with someone who had the specific expertise they needed. This is where a strong [advisory board](/blog/building-advisory-board-startup) would have given the founders direct access to operators who had solved exactly this scaling problem before. ### Portfolio Construction Matters as Much as Individual Deal Quality Every angel investor is going to have losses. The [portfolio construction question](/blog/angel-portfolio-diversification-strategy) is whether your winners can cover your losers and then some. If you are writing 10 checks and all of them are to companies with very similar risk profiles — same stage, same sector, same type of founder — you are not diversified even if your portfolio has 10 companies. True diversification in angel investing means having exposure to different stages, different types of moats, and different market structures. --- ## FAQ {#faq} **Q: Would you invest in the same founder again?** Probably yes, depending on what they were building. The CEO of Meridian made real mistakes but he also showed genuine honesty in the post-mortem and ended up in a senior operational role where his domain expertise is genuinely useful. Founders who fail honestly and reflect on why are often better at their second attempt. I would want to see the idea and do deeper diligence on the team dynamics, but the failure itself would not automatically disqualify him. **Q: How much of this was market vs. execution?** About 40% market, 60% execution in my assessment. The market problem was real and the competitive environment was weak enough that a well-executed company could have built something significant. The execution problems — the implementation burden trap, the co-founder breakdown, the delayed response to technical debt — were the difference between survival and failure. A stronger operational CEO might have figured out the implementation problem earlier. A better co-founder relationship might have survived the strategic disagreement. **Q: What would have had to be true for this investment to work?** The company would have needed to: (1) price implementation separately from the start and hire dedicated customer success by month 6, (2) identify and invest in a top-of-funnel approach that did not depend entirely on the CEO's time, (3) rebuild the integration layer before it became a crisis rather than after, and (4) have a more explicit framework for resolving co-founder disagreements. Any one of those things alone might not have been sufficient. All four together would have given them a real chance. **Q: How do you think about disclosing this kind of failure publicly?** Carefully. I have anonymized the company and the founders here because the purpose of this post is to share what I learned, not to damage anyone's reputation. The founders have moved on to new things and have handled the failure with more dignity than many founders do. I do think transparency about failure in the investing community is undervalued. Most investor content is about the wins. The losses contain more useful information. **Q: Did you consider pulling your initial investment before the bridge?** No, and I should be honest about why: secondary markets for early-stage equity are thin and the practical answer is that there was no exit. Once you have written a check into an early-stage startup, you are in until there is an exit event — acquisition, IPO, or failure. This is why the initial decision matters so much. The bridge decision is where you have a meaningful choice, and that is the decision I analyzed most carefully. **Q: What is the most important thing you would tell a first-time angel investor before they write their first check?** Assume every check you write is going to zero. Not because most startups fail — although many do — but because that assumption puts you in the right psychological state for angel investing. You evaluate deals more rigorously when you are not emotionally attached to getting a return. You have more useful conversations with founders when you are not privately panicking about your position. And when a company does succeed, the return is not a relief — it is a genuine reward for the thesis you built before the outcome was known. --- *Udit Goenka is a founder, investor, and builder. He has invested in over two dozen early-stage startups across B2B SaaS, developer tools, and AI infrastructure. He writes about investing, building companies, and the intersection of technology and strategy.*