I'm delighted that this article struck such a chord. I'll try to answer the most common questions here. I wish I could answer everyone directly.
1) I called it off before anyone sent money or quit their jobs. The only one who lost money or a job because of ContractBeast was me. If the money was in the bank and the team on board we would have gone ahead. That's why I had to make that decision when I did.
2) I'm not saying there was no solution. There might have been, but the team and I could not find one. Think of it this way. You and a team decide to summit a mountain. It's a high-risk endeavor. After weeks of going over your maps and equipment you just can't see a plausible way up. Do you call it off or set out hoping you'll be able to figure it out. It doesn't mean no one can do it. I means I could not do it with that team and that equipment.
3) Why didn't we leverage the contract approval features that customers loved? We tried. The problem was that those kinds of approvals were not core workflow for SMBs. It was useful when importing contract templates, but was not used much after that. Nice feature but not important enough to get companies to sigh up for multiple seats, which is what we needed.
4) Whats going to happen to the code and to Tim? No decisions yet. I'm open to suggestions on both counts.
1) You can describe the market in a few sentences, even to people without a background.
2) You can track user reaction without the need to ask them.
3) You know that most people don't understand their problem and therefore can't give good feedback via feature requests.
4) You understand human nature. People want to see a payout fast, before investing real energy into something.
5) You can pull the plug when the setup is not right.
Hope to work together with more people like you in the future. Are you currently looking for a CEO position in a start-up btw? ;-)
To be honest, it is much better now, but as a QE on the project, now I get to deal with so many half-abandonned/half-finished features.
Users don't come to you with problems, they come to you with shitty solutions.
You need to take their solution, reverse engineer their real problem from that, then work out a good solution for that problem that fits well with your product.
A couple recent related articles:
1) How to Pick Winning Product Features https://medium.com/pm-insights/how-to-pick-winning-product-f...
2) Building Products https://medium.com/the-year-of-the-looking-glass/building-pr...
I came to realize that the challenge is in the changing costs. They already had a product that could do more than what they could do with the systems they had at the time (mostly excel). It did a bunch of reporting and shift swapping etc. etc. but there was no way it wasn't getting momentum.
Thing is, I just wasn't passionate enough about it to make it a product I would love working on for the next 10 years.
A few people here say you're burned out, maybe you are, but maybe there are other projects you're more passionate about.
The project I'm currently on I'm not madly passionate about as a product, but other people love it, and it is fun to move the levers and see the affect on traffic and the (potential) business.
You're definitely not alone in your thoughts on this one, I can appreciate where you're coming from. Hopefully you look back at this as a great decision.
Better things ahead!
(great writing style btw)
Well, I thought I was crazy some times in my life (when I pulled the plug of my own company) for putting my life and my sanity on par with money. I was getting broken, I had a constant flow of ... 70+ /hrs job paid 35 hrs a week and even though I had customers but I was chaining more and more burn-in on burn-out. I was seeing my benefits diminish and my life sucked out.
But I did the right choice retrospectively. When clouds of stress disappears emotional reactions loosen up, then most of the time it shows you that rational thoughts such as the one you are exposing are right.
Risks have to be rationalized else you can get sucked in a gambler attitude. I guess some entrepreneurs are not guarded well enough against the "gambling/irrational risk" addiction that can be fired up.
It is hard because we are driven to entrepreneurship by emotions, and business decisions are best done in a cold sociopathic kind of state of mind.
You have all my regards and I wished I could have written such a concise and clear essay on the difficulty to live with decisions that are right and seem wrong because we human have doubts, emotions, dreams...
I'm better now, and this discussion on HN -- even those who disagree with me -- really helps.
From what I've read (and I could be wrong), it just sounds like you burned out. From personal experience, it's super difficult to keep up the energy and morale when you're either solo or semi-solo (when your cofounders aren't full time like you are). Part time cofounders are better than no one, but they're nothing compared to a full time cofounder who's with you in the trenches.
Good job on lasting as long as you did on that death march.
I have no problem working 70+ hour weeks for something I believe in. I've done it before, and there's a good chance I'll do it again. Just not on this project.
It's that you didn't want to stake your future on an uncertain outcome.
Nobody can argue with you that such a decision was a bad idea. If you, the founder don't want to do it - it will fail. So I think this just wasn't your passion play and you can't go down this road without being passionate and come out the other side in one piece.
That said, if every founder thought this way we wouldn't have most of the companies that we rely on today (not just startups by the way) - maybe that's good maybe that's bad.
It totally was! He had no way to solve the fundamental problem of the software - making people use it ALL the time, for multiple (paying) users. If the software was doomed to be one licence for an office of 20, where it is used sporadically for one or two infrequent use cases, it was doomed, and the only hope was a pivot. No one should start a business hoping to pivot.
> It's that you didn't want to stake your future on an uncertain outcome.
Again, no it wasn't. It was that he didn't want to chase hoping there might be a solution, because there may not have been a solution at all. If your whole business plan is "raise cash and hope we pivot to a good idea", is that really a solid plan? Why not just pivot before getting the cash? I have never heard of anyone proposing to raise cash based on an as yet undecided pivot.
> That said, if every founder thought this way we wouldn't have most of the companies that we rely on today
Prove it. No company I can think of knew pre-funding of a huge flaw at the core of their product they couldn't solve, and raised cash so they COULD pivot. Most pivots happen because a company finds a small element people love, so they move towards that. Startups don't go in hoping to pivot to an as yet undecided new plan. I mean, that just seems non sensical to me.
I've worked on enterprise collaboration software before, and came to the conclusions that the users will favour using the simplest thing for the task in hand (email or excel) no matter what SAAS products they have.
The trick then becomes 1. sell to management and get them to gamble on enforcing it's usage, (maybe by taking away the other tools, extensive training), or 2. have something that works at a grass roots level (e.g. dropbox being used to work around IT constraints) .
I think I may have just restated your post, oops!
I keep wondering if the future for workflow tools might be to unobtrusively monitor user interactions by hooking into the email client, and have an intelligent Clippy-like service which prompts and decorates their tools i.e. prompting to use ContractBeast if a contract is attached to an email (or in fact just doing so), and to display relevant information as and when needed. There was some CRM system extension for gmail years ago which I remember being radically successful.
Could something like that have worked out for you?
*and server in order to provide analysis, archiving etc.
As another example, if I had to enter tracking IDs into some app to have a nice view of when my packages were coming I wouldn't do it.
But gmail picks them from my email for free, so I use the app every day.
On the bright side, you still have Contract Beast on the back of your mind and if you ever do think of an interesting solution then you'll be in a good position to test it out.
I think you made the right choice, I would have done the same and don't think you should be judge worse for it. The whole thing was an experiment, your reason seems like a good reason to cut your losses personally. Before investment, that's Ok.
Sorry man. Good call not to waste a year of your life.
That's a great point. There are a lot of intractable problems that everybody wishes could be "solved" but the reason they're intractable is that solving them simply requires working harder. They can't be solved with cleverness they just require doing all of the work, rather than doing as much of the work as you absolutely have to. A ton of "solutions" just shuffle the work around. So it's like you have a clean sink, but if you want to use the oven you have to find another place for the dirty dishes. One pseudo-solution that doesn't actually reduce the work is just as good as another, so there's no NEED to switch.
As far as tools go, ethnography can be very powerful in the right hands.
I wonder if they considered involving both sides of the contract from the get go. When I've negotiated small-mid size deals with other tech savvy folks, I've often thought a two sided chat style interface that I could use sitting next to someone or if they were across town would be ideal.
The way I conceptualized it would be a 3rd party tool for making deals where the main feature is standardized clauses for minimal lawyer involvement. Eg. Need a standard confidentiality clause? (Drag Drop). Boom. Let's do business.
Commercial lawyers would hate it, but that's sort of the point.
"Oh check out this contract at FooBarContracts"
(counterparty opens link, copies text into word doc, edits)
"Here's the latest DOCX with my revisions."
This bit resonates the most with me. I worked on a project worth little traction where we'd keep getting feature requests from the client facing team members for things that were of minor value but sometimes major effort. It grinds you down over time as you realise there's no real demand. Eldorado isn't over the next hill.
Sometimes it feels like the people giving feedback are just too eager to please you with positive feedback.
This is an important observation. As someone once said, "no one wants to crush your dreams". If you present people an idea for a business plan, most people will say that is sounds very interesting, nice opportunity, they'd definitely consider buying that, etc. If you show them something you made, they will say it's great and politely have a little conversation about it.
It is very easy for perennially optimistic (/self-deluded) entrepreneurial types to take this kind of feedback as validation, when in fact it is nothing of the sort. The only validation is this: Are they giving you money for it? That is when you know you've made something of value, not a second before.
It feels like progress, but it's not.
That's the key quote in the article. It's a fair decision from his standpoint but I wonder if saying that will lead investors to question his determination in the future (if he tries a new venture). I suppose the investors could also appreciate that he didn't want to waste more of their money if he didn't believe in the product.
I respect the author for admitting he didn't want to run the business, and I realise it was his choice to stop in the face of any other options, but I really don't agree with the idea that running a startup requires 70+ hours a week and if you're not willing to put that time in you have to shut down.
It's easy to see when you realize your goals and your outsourcing entity have different objectives which are at odds with one another.
Whether that's 70 per week or 5 hours per month, the total amount of hours needed is going to be x,00 or x,000 - and that's time he simply thinks is not a priority or valuable to him.
but that's a false dichotomy
For reference, Paul Graham defines a startup as:
A startup is a company designed to grow fast. Being newly founded does not
in itself make a company a startup. Nor is it necessary for a startup to
work on technology, or take venture funding, or have some sort of "exit."
The only essential thing is growth. Everything else we associate with
startups follows from growth.Yes, very much so. Startup investments fail all the time, part of the business. Better a clean shutdown than trying to eak out an exit with money that could be better spent elsewhere.
You could also argue that it proves his determination, if he does in fact decide to engage in a new venture.
I didn't get the impression that it was more of their money, but rather the first injection, like a seed round.
"But most of the time, customers don’t really want the the features they are asking for. At least not very badly."
Customer feedback drives an absurd amount of our roadmap at Cronitor. We have a good idea of the many shortcomings of our product and are constrained primarily by resources in developing it faster. When a customer -- especially somebody on a trial -- puts their thumb on the scale of a specific flaw or deficiency, we look at it as an opportunity to seriously delight that user and at the same time level-up the product for all users after. We don't build everything asked for, but I would say "most of the time, customers know exactly what they need, and we try to give it to them within our ability."
A specific example for us would be Etsy, who uses Cronitor on a part of their business and during evaluation asked for a couple API endpoints to expose more advanced functionality.
I think this is true for both big ideas and little ones. I guess there may be some nuggets of truth deep down in the cw that "users don't know what they want until you give it to them" but I think it's mostly an over-used canard.
It is easy to agree or disagree with that because it is rather ambiguous and everyone has seen it go either way.
At least, I've seen it go both ways. It really depends on the context and most of all who the customer is. Are they paying for the product, will they be more likely to upgrade or pay if the feature is there, do they know that feature contradicts with other feature they already requested and so on?
Even silly things like customer is trying to be nice to you can interfere with the process. Because they don't want upset you and they want to be polite, they might ask for something trivial and hide something more annoying or bothersome.
I have seen this happen with me and design. I know a crappy design when I see it. It is annoying and bothers me. But, at the same time I wouldn't know how to tell the designer to fix it. If they press me I might make up something like "yeah, change color to beige" or something silly like that. I can imagine that happens with any domain where customer might not have as much expert knowledge.
> if i'dve asked people what they wanted, they'd have said faster horses.
is applicable here, much more so than in the battlecries of every company making something no one wants for some hypothetical market that doesn't exist.
While I don't understand the author's biz/space enough to comment situationally, this is a key insight. People almost always miss this. Users want to get to places much faster, and much more confortably in the Ford example. They speak in solutions and it is an entrepreneurs job to translate this into problems, rank them, and provide actionable responses.
The flaw I believe in your example, could be a few things. possibly if you are paid by a customer directly & are more a consultant/contractor than a SaaS provider, well, that's how you get paid. However, generalizing about a feature, especially without behavioural feedback is dangerous. if it is very easy to do, of course do it. However, the risk of a feature is some subset of:
* value to customer
* conviction/data in that value prop. & feedback
* difficulty to achieve
* is it replicable. how valuable is this to all my customers? is it very valuable to a few, or semi-valuable to many/all.
This is again, highest level, even in the last point above you can see the thread fan out.
So, again, i am bot super familiar with the authors company but I agree wholeheartedly with his process of decision making. Consider it is possible that either etsy was a big client, thus worth retaining for markwt goodwill & rev, or that it was quite easy to open an endpoint to data you already had, and thus doesn't discount this methodology
> When someone is shopping for a drill bit, they don't want you to sell them a drill bit. They want you to sell them a hole in their wall.
If you're wondering, most people will put a nail or hook in the hole in their wall, and hang a picture or something. 3M would go on to sell them tape or other wall adhesives instead of a hole in their wall.
Rephrased to correlate to this thread:
> When someone is shopping for document signing software, they don't want you to sell them software. They want you to sell them a set of agreements already negotiated with their business partners.
Don't confuse the tool with the goal.
I worked with some guys a few years ago that do vertical market software like this. They have like $12M in sales and 6 employees. Most sales is via referral, trade shows and partnerships with other vendors.
Not sexy stuff, but lucrative.
Future investor reaction to it will tell us what they think of actually bucking convention to do the right thing.
And now, the armchair brainstorming: focus on the "contract review and approval" immediate gratification and marginal user wins - if not sufficient benefit for them to buy, make it multi-month free trial, make it a year. After some "months of use", users get the delayed gratification. They become your sales force from within, and CIO's notice the long-term benefits, validated within their own company, and mandate its use top-down.
It's a long slow burn and mightn't work.
1. Your vision is crucial to your determination. Your vision is disrupting SMB CLM with "huge gains in accuracy and efficiency". You can only start the fire with those also inflamed with your vision - those who care. It seems only CIO's (anyone else?). The CtC idea is to target those few adventurous CIO's ("visionaries") who want to leapfrog the competition with this new, unproven approach. Reach them through those very, very few CIO's who are excited by the idea itself ("enthusiasts") - just because it's a clever, efficient, elegant approach to a broken process. They exist, just not many.
So: if you try to appeal to users, it must be those users who are excited by what causes the "huge gains in accuracy and efficiency". Otherwise they'll carry the wrong torch to the CIO.
2. The other CtC idea is "niches": pick out the types of customer who would really benefit from your solution. e.g. inaccuracy causes chronic problems for them/losing customers/bad publicity; CLM is a dangerously high cost center; they can't keep up with sudden demand and are losing sales; they can't adjust to changing contracts, and lose opportunities; (new) regulations/legislation makes inaccuracy very expensive. Plus, it would open up a new market; overtake a competitor; resist a competitor. These also excite upper management.
Applying it gratifying users: are some businesses constantly approving contracts, and importing templates (or should be)? Maybe during M&A; law/consultancy firms?
Choose your customers to suit you.
Sometimes what you build becomes bigger than you. If you want to quit, and everyone else wants to keep going why not let someone else run the show?
If you started a chess club, or even a chatroom, and had no time (as the guy says, he only has one life) to be an admin, would you just close down the whole thing and kick everyone out? Maybe. If they really were so passionate they'd pick up the pieces and start their own thing. Your old group might have a way to transfer the accumulated wealth to the new group. Instead of just losing it.
I remember writing an article about this a couple years ago called the Politics of Groups:
http://magarshak.com/blog/?p=135
Here is an excerpt:
If the individual - the risk is that the individual may have too much power over others who come to rely on the stream. They may suddenly stop publishing it, or cut off access to everyone, which would hurt many people. (I define hurt in terms of needs or strong expectations of people that form over time.)
There are prolly more ...
And it sounds like the product automated a good, sound process. One that was different from the customer's actual, current process.
I don't know how one could hope to sell a new process (incidentally along with an automation framework) without massive training, and, well, consulting.
I'm a little surprised they didn't take the opportunity to pivot. Maybe none of their beta users were interested in the 100x(?) investment buying such a package would cost? It sounds like they found a different market, smaller in number of customers, larger in revenue - and chose to walk away because: software is fun, human process is hard and boring?
It's a valid choice to be sure, but it strikes me as a little odd. I thought the idealised, naive idea of a computer system being more important than the human systems it enables was more of a delusion limited to Silicon Valley, than a general problem.
I'm reminded of how model-view-controller was internally known as model-view-controller-user, and how shortening it to mvc[1] was probably a terrible mistake that obscured most of the valuable idea behind the concept (that of mapping the users mental model of domain knowledge to widgets on the screen and on to the data models used by the software).
[1] according to a talk Trygve gave, but it kind of shines through in his brief history of mvc too: https://heim.ifi.uio.no/~trygver/themes/mvc/mvc-index.html
Interesting comment in there about 'Approvals' being one of the most used feature. Why couldn't you build around that? A more generic approvals solution for any kind of contract.
Maybe the next generation of UX will have change management built into the system, not just tours and tooltips. For now, the burden of software adoption is best served with donuts and somebody how cares enough to make it work for the business that is investing in it.
My understanding is that people seem to resist change in corporate environments because it is a high stakes environment where, for example, the ability to hold onto work "flow" achieved over a long period can make the difference between thriving and failing. Thus software becomes more of a political tool, not necessarily in the sense of office politics, but in the sense of being part of a strategic toolbox by which people grapple with the networks of power they participate in at work.
So corporate users are not necessarily resistant to change; they are just strategic about whether and what changes are to their advantage; if the introduction of new software can strengthen their work-related strategies, they can become its champions. I have seen this myself when I used to work for big multinational corporations.
To model software adoption in the corporate space, therefore, one might need to employ a theory of power such as Actor-Network theory (in which terms one might think of software as an actor that can be "enrolled" for various ends)
A theory of work and instrumentality, such as Activity Theory, is what most people (sometime without knowing it as such) apply to analyze work environments; but paradoxically it is usually the wrong approach to analysis. I see this failure of analysis all the time.
In a nutshell, the more instrumental and work-oriented software is, the more necessary it is to analyze it through a power-relations lens.
I'm trying to figure out how ContractBeast's problem of continuous usage is any different than almost all the business tools out there that require human intervention (with the exception of email, and MS office suite).
It seems every investor and entrepreneur has this desire to make "crack" and not just tools. Good tools don't need to be used all the time. They don't need to provide some sort of gamification, feedback loop, or enjoyment.
As for money making good business tools don't need even need to be used by the user... in fact they really should be automated. I know this because we had some of the some problems ContractBeast did and the key was not getting the endusers involved at all. Automate and integrate so they are almost out of the loop completely (again I don't know much about CLM... maybe this isn't possible).
As far as top down selling it is almost impossible in the B2B market to do something different. Managers force users to use tools and those users use MS Office most of the time but those tools still get bought and eventually those tools do provide value (aka sales force).
Every idea to fix it takes time to develop, and with whatever time remains you have to make progress with sales and the existing customer base. With any given product and the right team you can get there, but the only way to get the right team to commit is with a passionate belief that you will get there before you run out of money.
If you spend the time trying to build a roadmap out of whatever options you can come up with, and none of those options give confidence given time and budget constraints... well, then you've done all you can do. It's not hard to come up with a list of reasonable options to move forward with, but it is hard to come up with one that's worth committing to.
If you've grown to the point where you can man up and make the decision to walk away early, you have a good future.
As someone completely unfamiliar with the world of startups, this sentence baffles me. If this describes your track record, how do you even get funding? Obviously I'm not an investor, but this sentence alone is a massive red flag.
For example, if you expect something to fail 80% of the time but to gain >400% the other 20% of the time, then the bet has positive expected value.
Think of the success rate of startups as a whole. It's like 10%. So if you are at 50%, that's a reasonable bet.
For example: use a chunk of the $500k as rewards to push people through the initial adoption. Then presumably the real gains would take over and they'd be happy customers.
Contract Beast's customers were likely exclusively these "purchasing" people, and thus, that's where the feature requests and feedback were coming from.
But, in the end, the success of the product within a customer company is often more driven by the "non purchasing" users...the actual departments that are trying to buy (or sell) something. It's not unusual for the wants/needs of these people to be completely different than the purchasing department.
I watched several attempts for contract management software fail because of this. In the end, what won out was narrowing the solution down to the biggest pain point...implementing just e-signatures. That got rid of all the manual print / sign / scan-or-fax cycle, which everyone could agree on.
Moving everything to the cloud would be far more efficient. But the corpus of legal text captured in Word and Legal's preference for redlining email attachments is the status quo.
There should have been some guideposts here: who were the power users? what did they love? who were the huge detractors? what was their big issue? how did ContractBeast fit into the ideal world? how were people splitting their work between the old system and ContractBeast? were there network effects for the old system?
Yeah we can look at some sort of short term win and long term gain framework, but it's pretty reductionist to a) only depend on that framework and b) not be able to come up with any solutions to fulfill short term wins.
If you had discovered this when you were 6 months in, spent 50% of the cash and had employees would you have made the same decision? To pull the plug and return remaining capital vs trying to make it work.
Sometimes it's not necessary to assess this because you are compelled to act and you can't stop.
In this case I think had he asked this hard question sooner he would have found his heart wasn't in it. Either way dropping it was the right thing to do.
In comparison my 'why' for the thing I'm working on makes my soul burn and is a limitless well of determination.
Call it 'Conviction/Opportunity' pull.
I don't really understand "having nothing" -- you're either creating value or you're not. You guys spotted a real problem, but your v1 solution was meh. There were certainly multiple ways out (and not just tack on gamification), and even if some were long-shots, the uniqueness of a startup is to place those bets.
Neither does insurance but its pretty much a no brainer for most companies. Contact management isnt suppose to give instant gratification. Its supposed to provide peace of mind knowing you will not miss important dates in the FUTURE.
Hate to say it but Mr Romero seems to have given up way too early. All the smart people on HN someone will pickup the baton and run with this idea.
If the team and investors believed in the product, perhaps you could have asked if some of the current team were willing to take it on, and make it work. You could have retained a bit of equity for the year and the hard work you put in so far without having to commit any longer yourself.
OT, but curious, how is it possible to get this kind of engagement data?
Querying DB to get number of logins per week? But that doesn't mean that they're "using" the system.
Google Analytics? I'm not aware of any such GA feature
Third party analytics?
Surveys?
Using just your database, you can store records when users complete certain actions.
Eg. When a contract is uploaded, modified, when new people are invited to collaborate over it ...
That way you simply query for user actions over a period.
I use Google Analytics to do the same thing via events. Fire events when actions take place, review the data in your dashboard.
I have seen a small companies use student licenses instead of paying for the more expensive commercial license in order to save every possible penny.
Essentially they need to add an extra step to their routine & pay for the lack of convenience. This was likened to ecercise by the author. However, if you expect anyone without a top down authority (also mentioned) to do something that is harder & more expensive, they won't. It's why gym memberships bought on Jan 1 are rarely renewed in Feb or March
edit: so you are correct, paying for what you use is logical especially vs the value. Here it sounded like the customer has high value, but we discount it steeply for lack of immeadiacy.
Reading between the lines here, I'm picking up some resentment. I think an underlying cause of the decision to walk away from ContractBeast might have been a specific subtype of founder burnout -- the kind that happens when you feel like you're pulling more than your share of the weight, and/or you feel like you're more committed to the company/project than the rest of your team is.
There's a downvoted comment at the bottom of this thread stating that the commenter would never give this guy money. That's a bit harsh, but at another point in the comment he makes a very (IMO) valid observation that burnout is at play here and the author should have taken some time off. That rings true to me.
Also,
> Weeks of brainstorming and dozens of hypotheses later, we had nothing. Not a single, plausible way of providing our users with the instant gratification their cerebella so desperately crave.
> With no clear path forward, investors ready to wire funds, and the team ready to quit their day jobs, I decided to pull the plug.
Is it just me or does this seem like there's a big hole in the plot here? The whole team spent several weeks trying to figure out how the product was going to get traction, came up with zero good ideas, and everyone's still ready to quit their jobs and work on this full-time?
Assuming this is accurate and absent further details, I can think of two non-mutually-exclusive hypotheses for how this might have actually happened:
1) "We had nothing" was really "I had nothing". Either because of a failure on the part of the author to communicate with the team, or their indifference upon hearing the author's description of the problem in question, the only person really working on solving the problem was the author. To the extent that this was the case, it would certainly have exacerbated the "I'm working way harder on this than my cofounders are" burnout described above.
2) It's also possible that the other prospective cofounders and/or early team members were aware of the headwinds facing ContractBeast and just really, really hated their day jobs and were thinking, "I honestly don't even give a shit if this company works out, I just want to go somewhere I can get paid while not having to deal with my current boss, and if it fails it's not a big deal, it's a startup, they fail all the time and I'll be able at a minimum to use the newfound flexibility in my schedule and relative seniority in the organization to make myself much more available for interviews at other companies."
startup = a newly established business
Patrick McKenzie has demonstrated that you can do high-touch corporate sales as a small organization or even as a single person. He just needed to figure out how.
I think this guy needed to take a day off or seven and get his head back on straight. I'm nearly positive every entrepreneur goes through the "doubt" process many times in a given start-up.
It's the person that figures out how to renew themselves that ends up succeeding.
> The team was excited. Our potential investors were excited.
He didn't really have a team and he didn't really have investors. He took a personal risk and found it wasn't working. He shut it down before it got expensive for people other than himself. I applaud this.
People, especially around here, need to understand failure is the norm. This person failed fast, well. Nice work. On to the next thing.
I have nothing against accepting failure in an idea. My first start-up failed and I had to let it go. It was really fucking hard to do that. But I tried to pivot twice before finally letting it go and I worked at it for a number of years.
The people that want us to fail fast don't have entrepreneurs best interests at heart. They're looking for quick wins and the more starts and fails they get, the better _their_ odds of something "popping".
But there's something to be said for perseverance.
I won't argue that there shouldn't be a balance, and maybe I was too hard on the OP, but it sounded to me like he needed to step away and think about it, not just let it go.
But I guess we have to defer to his judgment since it was his idea.
I just really don't like fail fast mentality.
When your heart isn't in something, there's no way to "get your head back on straight".
He did the right thing.
I don't think you should sling this kind of thing around so lightly. It's trivial to post charges like this on the internet and have many people just believe them. But this is a serious thing to say right after you've invoked the idea of suicide, and doesn't remotely resemble anything I've observed at YC. In my observation, YC partners don't "force founders" to do anything; they couldn't anyhow, and they don't think that way in the first place.