Live data from Hacker News

Ask HN: Main things to consider when building an app for business/enterprise?

news.ycombinator.com

1–10 of 132 posts

Ask HN: Main things to consider when building an app for business/enterprise?

#1
I have a couple of ideas I’d like to build that would target business/enterprise and take the form or a SASS product (problems I see people having regularly)

I’m a pretty generalist fullstack engineer.

The things that worry me about this space are security best practices, providing features like corporate single sign on and handling data that customer expect to be healed very securely.

Its probably clear I don’t know much about this space and am likely missing even more things. Any advice or heads up would be really appreciated. Advice on business models and go to market strategies would also be really nice.

Re: Ask HN: Main things to consider when building an app for business/enterprise?

#4
Much will depend on the type of businesses you’re going after. If you’re targeting government agencies and/or financial services organizations, you’ll find that their requirements will be a lot steeper than your average software company.

In large enterprises, the sales cycle time can also be quite long, but to make up for it, the deal sizes can be quite large. It’s worth working with them for several months if it means a million dollar deal.

The best advice I have as someone who has sold to enterprise customers for years now is this: understand your target customers. That is, not just the companies themselves, but the actual people you’ll be selling your software to. So before you start building, you’d do well to talk to your target customers to see what exactly it is that they need (and see if it meshes with what you had in mind) and also find out what hurdles they have in place to buy software. If you know the requirements in advance, you won’t be surprised in the sales process.

One book I’d recommend if you haven’t read it is the Mom Test. It’ll give you good guidance on asking the right questions to get feedback from your target customers.

Re: Ask HN: Main things to consider when building an app for business/enterprise?

#5

This feels a bit too vague for anyone to give you advice on. Do you want to build enterprise apps. Do you need advice on using React Native vs Flutter vs Swift ? Do you want advice on actually building a SASSS business?

No, OP said: " things that worry me about this space are security best practices, providing features like corporate single sign on and handling data that customer[s] expect to be healed [handled] very securely."

Re: Ask HN: Main things to consider when building an app for business/enterprise?

#6
If the smaller companies I’ve worked for are any indication… don’t get hung up on branding this app. Be able to swip swap a logo and call it a day.

My god the time wasted talking about branding and then a client can’t even provide a decent logo and turns out they didn’t care about the branding anyways.

Don’t waste your time on that stuff unless it’s hyper critical to the core product itself.

Re: Ask HN: Main things to consider when building an app for business/enterprise?

#7

If the smaller companies I’ve worked for are any indication… don’t get hung up on branding this app. Be able to swip swap a logo and call it a day. My god the time wasted talking about branding and then a client can’t even provide a decent logo and turns out they didn’t care about the branding anyways. Don’t waste your time on that stuff unless it’s hyper critical to the core product itself.

To add to this, I have an application in production with a client right now that literally doesn’t have a logo. The favicon is the initial of the service’s name on a random color background. Nobody has ever asked or commented.

Re: Ask HN: Main things to consider when building an app for business/enterprise?

#8
Enterprises often have deals with cloud providers. Offer to host your app on "their" Azure / AWS / whatever. That way, they're taking responsibility for their data.

In your offer, state that you're happy to support Penetration Tests that might have to be carried out.

Get an IT insurance and tell customers about it.

If you've got a lot of time and money, get ISO 27001 certified (5 figure sum for a small company).

Re: Ask HN: Main things to consider when building an app for business/enterprise?

#9
At minimum, implement your application to address the OWASP Top ten: https://owasp.org/www-project-top-ten/ Document how you addressed these. Check with every new feature or change if you create a new vulnerability. Don‘t store data without a clear purpose Don‘t invent your own encryption. Think how data is erased or archived Separate the data of different tenants Implement a proper audit trail Once you gain traction: ask an independent party to do a penetration test. Be transparent to customers about vulnerabilities discovered and patched. Limit third party dependencies to components that get regular security patches. You need to proof your security is better than what your customers have in-house.

Re: Ask HN: Main things to consider when building an app for business/enterprise?

#10
I started a side project turned bootstrapped B2B SaaS that was eventually acquired, so I can share a bit of what I learned. Some day I’ll write up a longer list of lessons.

Security - complexity will absolutely kill you. I know it’s fun to experiment with Kubernetes and multi-region infrastructure deployments, but that does nothing but increase your attack surface. When we were acquired, I had a single static website hosted on AWS S3, one RDS database, and a handful of Lambda functions behind an API Gateway. You still need to follow best practices: use TLS for all connections, encrypt customer data, properly segment application users, OWASP top 10, etc. but that’s much easier to do with a simple application. Minimize application dependencies, scan them for venerabilities using free tools like Snyk, and keep things up to date.

Compliance: Depending on your domain, you may need to get a SOC II report at some point. Don’t do it until you need it, but when you do, just pay a company like Secureframe (full disclosure: I’m an advisor for them, but there are other similar companies).

Single Sign On: we used Auth0, which was great until we reached 10(?) enterprise connectors and it went from free to $15k/yr. We then migrated to AWS Cognito. If I did it again, I’d just use Cognito to begin with, but wouldn’t build the integration until you actually have customers asking for it.

Marketing: my weaker spot. I was a developer, so had a skeptical view of marketing. We tried a lot of things (agencies, paywalled content, contract writers, etc). I’m still convinced that the highest impact marketing was deeply technical content (doesn’t even need to be about the product, just the same problem space) that was published on our blog for free with a link at the bottom to our product. Simple and effective. Reddit ads on niche subreddits were helpful, especially with getting early users. Marketing agencies are probably overkill until you’ve got actual PMF.

Sales: you need to do the selling. Don’t hire a salesperson until you’ve got a significant number of users. “But I won’t have time to develop if I’m selling.” Yes, exactly. And you won’t have anyone buying if you spend all your time developing and not talking to users. It’s critical that you personally talk to every user as much as possible.

Pricing: I made the mistake of underpricing the product for a long time. I thought developers would love the low cost model. In reality, their companies were paying, and, when you give someone a company credit card, they’re a bit more willing to pay more for a good product. You can still price lower than the competition to get users in the door, but don’t try to be the bargain app. Monthly subscriptions are good, annual are better, but bring tougher sales cycles (enterprises will want to negotiate the contract, add their own legal terms, etc).

It’s a bit tough to give much more advice without knowing what domain you’re operating in, but hopefully that was helpful!

Post reply on HN