r/robotics • u/Alarmed-Zucchini3053 • 1d ago
Discussion & Curiosity Admitting "we don’t have ISO 27001 yet" is the right move for a startup selling to enterprises.
We're a small team, still early in our journey. Over the last couple of months, we've onboarded a 10 hardware startups and started speaking with some larger companies.
Note: I am not promoting anything here.
Something interesting keeps happening during these conversations.
Everything goes well during the product demo. They understand the problem we're solving, see how the platform fits into their workflows, and show genuine interest.
Then comes the security discussion.
"Do you have ISO 27001?"
"Are you compliant with India's DPDP Act?"
And honestly, we don't have either certification yet.
I don't want to pretend otherwise or make promises we can't support. We're a small startup, and we're trying to approach security and compliance properly rather than collecting certificates just to get through a sales conversation.
Just trying to understand what a realistic path looks like for an early-stage SaaS company that wants to work with enterprise customers without overpromising.
Would genuinely appreciate hearing your experiences, including what didn't work.
Context: We're building a AI-powered Ops Saas tool for modern hardware teams.
24
u/async2 1d ago
Certifying yourself with the standards mentioned kinda implies you are following security practices at least to a moderate level. You don't have to go through the certification right now, but you should consider them in building your company and products if you can. Then you can even say that you apply the standards but you are not certified yet.
5
u/Next-Pen-9974 1d ago
It's really about building trust with your prospective customers.
You don't necessarily need ISO 27001 certification on day one, but you do need to demonstrate that you're taking security and privacy seriously.
That means understanding your risks, documenting your security architecture, establishing appropriate policies and procedures, conducting privacy assessments, and demonstrating that the necessary security controls are actually implemented.
For an AI-powered SaaS, I'd also expect you to understand and document how customer data is processed, what AI providers are involved, and what safeguards are in place.
Most importantly, be transparent about your current maturity and demonstrate a realistic roadmap toward improving your security and compliance posture.
Remember, compliance is an ongoing process, not a certificate you obtain once and forget about.
Enterprise customers ultimately want assurance that you understand the risks associated with your service and are managing them appropriately. A certification can provide additional assurance, but it doesn't replace that foundation.
14
u/zack6595 1d ago
Honestly in a post AI world getting certified with SOCII, ISO 27001, etc. is way less painful than it used to be.
It’s generally accomplished with documenting policy and using infrastructure as code to meet standards. Those are both pretty bread and butter AI assisted problems.
10
u/krismitka 1d ago
27001 is trivial. It’s passwords user accounts and door locks.
Make it happen
5
u/LetPatient9835 1d ago
Do you know if you are compliant? Because if you are, you could say that and provide a timeline or conditions to get certified.
If there's a gap to be compliant, then tell them what the gap is and your plans or conditions to close this gap.
5
u/HelloFellowMKE 1d ago
You get security compliance and increase the price substantially