Live data from Hacker News

Ask HN: Important nonobvious startup/business lessons you've learned?

news.ycombinator.com

151–160 of 256 posts

Re: Ask HN: Important nonobvious startup/business lessons you've learned?

#151
post #130

Earlier quoted context omitted.

>> But having more sales when you sales org is badly structured will make you loose a lot of money Read the original point. The OP is not saying sales globally optimizes all things, like how your sales department is organized, rather it mitigates (i.e "fixes") the problem. All your other points are secondary, and definitely don't hurt as much if you've got lots of sales. Larry Ellison of Oracle definitely fails rule…

But this is not true, it is not more sales that fix the problem it is more sales that are -successfully selling- that fix it. I've seen companies where more sales has amplified the problem EDIT: I use Sales as a shorthand for "Salespeople" but OP use Sales for "revenue" maybe ?

> EDIT: I use Sales as a shorthand for "Salespeople" but OP use Sales for "revenue" maybe ?

Yes, definitely.

Re: Ask HN: Important nonobvious startup/business lessons you've learned?

#152

As a dev i've always known my hunch when it comes to compromises. Never let the business team ruin your experience building cool rock-solid code. I'd rather resign than to compromise anymore. I know there should be a sweet spot between "perfect" and "working". Even a junior can pull-off a "working" app. But when it starts to scale, all those hasty bad decisions will bite your ass. Never skip planning, plan as long as…

No offense but this is awful advice for a startup.

Please read my comment below. You are right, but we cannot generalise.

Re: Ask HN: Important nonobvious startup/business lessons you've learned?

#153
I've worked as a normal employee at 2 startups and both failed. Some people invested their own money for different classes of stock.

Before going to a startup I would tell everyone to read this post about liquidation preferences and cap tables.

Why didn't I get any money from my startup?

https://www.reddit.com/r/startups/comments/a8f6xz/why_didnt_...

Who invests money? What about the second round of investors? A lot of people think that the people who were their the longest should have priority but it is the exact opposite. The people who invest last get the best deal on a return on their investment.

Ask these questions to the founder / owners of the company. If they don't answer your questions directly take that as a sign that they won't be truthful and straightforward when you are an employee.

Re: Ask HN: Important nonobvious startup/business lessons you've learned?

#154
post #102

These are more enterprisy: If you sell through a channel, that channel is your customer, not the end user. They have needs and actually those needs (not desires, needs) are more important than the end users' -- if your channel doesn't sell the product it doesn't matter how much you've worked to add that end-user feature. Have the entire exec team go on a sales call once a quarter (not all together on the same call!).…

> That mild-mannered A/R clerk is the real difference between paycheck and no paycheck.

What's A/R?

Re: Ask HN: Important nonobvious startup/business lessons you've learned?

#155
post #116

Earlier quoted context omitted.

I meant “sales” as transactions, not “sales” as in the department or role.

The commenter with the advice clearly mean "sales" as the department or role. To a founder or CEO the word "revenue" is used where you're using "sales", it isn't wrong except in context but the intention was unambiguous to me.

I believe the word revenue was simply elided in this case. i.e., parse as “sales revenue.”

(I’m noticing elsewhere in this thread that others are interpreting “sales” as sales departments or salespeople. Perhaps it’s a cultural thing, where the meaning of the plain word varies depending on where you live.)

Re: Ask HN: Important nonobvious startup/business lessons you've learned?

#156
From a family business started by my great grandfather, been running for over 100 years.

Things I learned from my dad and grand parents.

1. Being decent to people will cover all kinds of other problems.

2. A great reputation for doing good work is probably the best sales tool to have.

3. You can pay your people well if you charge premium rates. (and do premium or higher quality work)

4. If you pay your people well you just have a generally happier work force.

5. If you trust your people you don't have to micro-manage them.

6. Giving trust to people can be hard sometimes when things don't go well. (but you need to keep doing it anyways, even when you get taken advantage of from time to time)

7. Hiring mature and decent people fixes a lot of problems in advance.

8. Having a happy work environment is more important than efficiency.

9. The higher up you are, the first you are to take a pay cut, provides respect, stability and confidence in the rest of the company.

10. Don't beat up your vendors on price, and when things get rough, they will take care of you.

There is a lot more.

Me personally:

1. Being technically minded I had to learn to just hang out and talk with people. This was hard because I felt it was inefficient, but the long term, knowing people personally helped when there was difficult technical issues to solve while working with them.

2. Don't make changes to other peoples lives without consulting them first or at least giving them notice (if they don't have a choice). Changes to software, their computer, their job role, etc... Too many horror stories about this kind of thing really frustrating people. Thankfully, I avoided many of these issues by learning from others before making these kinds of mistakes to often.

3. It can take time to really understand a customer or a business. It's just hard to be patient as a technically minded person to sit and understand why something is done when it seems to be done so poorly.

4. Everything doesn't have to be fixed. I thoroughly enjoy fixing and improving things, but sometimes it's just fine to let something be clunky. Why? Because sometimes that clunky thing will stay working under every possible difficult circumstance, and an efficient issue requires calling me when it breaks...

5. Stand down. I've had to give up on very important issues because it would have had too much impact on other people. I wanted to fix product ids because they were based on a 1980s limitation, but the fight to win this change would cause too much turmoil, so I let it go, and I am glad I did, because I never really had to use these product ids myself anyways, and my concerns were theoretical.

6. Patience on change. I've found that when I see something I want to improve (from sales processes to manufacturing to IT related items) that if I bring up the issue to those involved, offer some ideas, and then leave it alone. When everyone now knows there is a solution waiting in the background, they start to notice the issues more keenly (instead of the frog in the pot) and then when they've had enough, they will be motivated for change instead of me pushing people towards it.

Re: Ask HN: Important nonobvious startup/business lessons you've learned?

#157
1. Make sure your business model doesn't mean growth will kill you.

@armc's first point "Few business problems can't be solved by more sales." is important, but here is a case where it doesn't work (on the contrary).

I once (indirectly) worked for a startup whose business model was basically to rent expensive hardware to its customers. It was considered a rising star, but here's the problem: it had exponential growth. That meant exponential capital needed to buy hardware.

It was considered a rising start, most of its metrics were incredible. Given unlimited access to liquidity it would have easily IPOd by now. But there is no such thing, so it crashed and burned.

(The product still exists but they took measures to address that problem, and the growth is hardly what it once was.)

2. Money doesn't exist until it's on your bank account.

Another startup I worked for (you might guess which one) raised a round with a new fund as the lead. For various reasons that fund couldn't give us the money for a whole year and that locked the other funds as well.

That startup was selling hardware. With no money in the bank we couldn't pay the factory or shipping. We had endless pre-order lists. When the money finally arrived, we had had a whole year with basically no sales, and that ended up being fatal.

3. Some customers aren't rational and that's fine.

At a startup I worked for some time ago, a customer bought an expensive yearly license for our product and never even used it once. At the end of the year, they came back... and renewed the license. I think we actually asked them if they were sure, and they said yes. They didn't use the product for yet another year.

4. Only found a company if you understand the field.

That one is from my experience as a founder. I was the technical co-founder of the company but I had no previous experience or knowledge of that specific market. I thought that was fine because I had a great co-founder who did and very serious partners, so I could learn as I went.

As it turns out we realized quickly that all our initial market study had important flaws an our assumptions didn't hold. We then went into a mode where we tried to figure out if we could turn the company around or maybe pivot, and that was a very frustrating time for me because I felt powerless, not having the necessary knowledge to help like I would have wanted to do.

Thankfully I had enough experience with other businesses to look at the metrics and figure out a few key things. Eventually we shut the company down and it was the right decision, but I will never again start a company in a field I don't know well.

5. Everyone on support.

I have done support one way or another at every single company I worked for. At the company I currently work for everyone works L1 support in rotation and I strongly believe it is a good thing. It will ensure everyone talks to customers and is aware of their pain points.

Re: Ask HN: Important nonobvious startup/business lessons you've learned?

#158
post #102

These are more enterprisy: If you sell through a channel, that channel is your customer, not the end user. They have needs and actually those needs (not desires, needs) are more important than the end users' -- if your channel doesn't sell the product it doesn't matter how much you've worked to add that end-user feature. Have the entire exec team go on a sales call once a quarter (not all together on the same call!).…

You strike me as a genius, Gumby. I literally said "oh my god" out loud while reading the free pilots paragraph

Re: Ask HN: Important nonobvious startup/business lessons you've learned?

#159

Earlier quoted context omitted.

This is amazing advise. People working in tech, especially in high tech orgs live in bubbles and often imagine that the whole world is like this. I know a multimillion £ business that probably gained hundreds of thousands in productivity by simply introducing shared mailbox. Some of those low hanging fruits are litterly on the ground ready to be picked up.

> I know a multimillion £ business that probably gained hundreds of thousands in productivity by simply introducing shared mailbox. Good if someone can pull it off. But, I believe that company might have sold that feature as an add-on to their existing customers. Otherwise, you know “Sales” are the hard part

I think the advice here is not so much to sell a solution to these businesses, but to start a business in that sector and run it more efficiently---thanks to tech magic---than the competition.

Re: Ask HN: Important nonobvious startup/business lessons you've learned?

#160
post #154
post #102

These are more enterprisy: If you sell through a channel, that channel is your customer, not the end user. They have needs and actually those needs (not desires, needs) are more important than the end users' -- if your channel doesn't sell the product it doesn't matter how much you've worked to add that end-user feature. Have the entire exec team go on a sales call once a quarter (not all together on the same call!).…

> That mild-mannered A/R clerk is the real difference between paycheck and no paycheck. What's A/R?

Accounts receivable. The people who handle payments, and who hound delinquent accounts to pay up.
Post reply on HN