Martin Maciel @zedrushq

Security review Sunday, round 4. Reply with your SaaS and I'll tell you the first thing an enterprise security reviewer would flag. Free, no pitch. (Round 3 finally happened on an account people could actually see. Let's keep it going.)

Founders think "no SOC 2 = no enterprise deals." Mostly false. Plenty of mid-market buyers just need clear written answers, a real security page, and a vendor who doesn't overclaim. SOC 2 comes when a deal actually demands it — not before.

Zedrus builds your trust page in ~10 minutes: AI drafts the sections, you fix what's wrong, publish to a public URL. Free tier = a complete page. Pro ($19/mo) = your own domain. The point isn't the page. It's having the answers before the questionnaire arrives.

This week a founder building in public asked, out loud: "how do you post your progress? like making a security page for it?" That's the whole thesis in one tweet. Nobody googles "trust page." They hit the wall mid-build and ask. So I answered. That's the job.

"But it's just self-declared — anyone can write anything." So is every security questionnaire you've ever filled out. Nobody audits the $50/mo vendor. Buyers get written, dated answers with your name on them. Self-declared IS the standard at your size. Own it.

@elvissun @FeHa Yes — and date every claim. List what's live now (encryption, backups, access control), flag in-progress items honestly, add a "last updated." Buyers care less about the cert than seeing you keep it current. "Updated weekly" beats "SOC 2 coming."

@socialwithaayan @arsh_goyal Every founder's rite of passage 😅 The applause is for the product; the questionnaire is for the buyer's legal team — a totally different audience. The ones who saw it coming had the answers written down before the demo, not scrambling after.

@thisiskp_ @Netlify Building a way for indie founders to answer enterprise security questionnaires without a $20k SOC 2 — just a public page with honest, dated answers. Turns out "we wrote it down" beats "trust us" more often than you'd think.

@khemmapich @lightsilver323 Congrats on the first enterprise customer 🎉 One heads-up from experience: the security questionnaire usually lands right after the handshake — 40 pages on encryption, backups, access control. Writing those answers down before they ask is what saved my second deal.

@icenquon The convergence point: both sides increasingly expect the answers published up front. A public security page pre-answers most of the SOC 2-style AND the data-residency questions before any form arrives

@dogan3646 Underrated item here is #5 — it's the only one on the list buyers actually read before paying. The rest they assume works; the trust page is where they check.

@LaunchAIJam @misterlyserious @conecteer "Trust page, trust product" is exactly right. Curious how much weight you give it in your teardowns — I've seen buyers bounce at the security page before they ever read the pricing.

Security review Sunday, round 2. Reply with your SaaS and I'll tell you the first thing an enterprise security reviewer would flag. Free, no pitch. (Weekly ritual. Round 1 taught me indie founders underrate what they already do well.)

The "trust center" products enterprises use cost $8–20k/yr. Great tools — built for companies with security teams. If you're a 1–5 person SaaS that just got its first security questionnaire, that math doesn't work. That's exactly why Zedrus is $19/mo.

My own custom domain sat stuck on "pending" for 2.5 hours recently. The only retry path was me, poking the backend by hand. So Zedrus now has a Retry button on every stuck state. The best feature requests come from your own pain.

I broke my own product this week. Published a trust page before the AI finished drafting — shipped a beautiful page with zero sections. Just a header and a badge. Fix is on the roadmap: block empty publishes. Dogfooding finds what unit tests don't.

@themanavpaul Congrats! 🎉 Heads-up from experience: the enterprise customer that signs before launch usually sends the security questionnaire right after the contract draft. Having answers written down before it lands saves a very stressful week.

@preflightdocs This resonates. Buyers don't compare feature lists — they scan for reasons to distrust you. An honest "here's what we don't do" removes exactly that. Transparency is a badly underrated conversion lever.

@BhargabLinx Solid stack. One thing that surprised me selling to enterprise: their IT's first question isn't about features, it's "how do you handle our data?" — worth writing those answers down early, saves a mid-deal scramble later.

@_eyb_s Clean UI. Curious — with "enterprise-grade" positioning, are prospects asking you for security docs yet (questionnaires, trust page)? In my experience that ask shows up right after the first demo.