We Ran 5 Audits on Our Own SaaS in a Week. Found 62 Problems.
Dogfooding is a cliche. Auditing yourself like a hostile stranger is rarer. Last month we ran five audits on our own product in one week - security, performance, content, SEO, infrastructure - and logged 62 issues. Most were embarrassing. All were fixable. Here is what the week taught us.
Security audit: the bot nobody authenticated
Worst find: our Telegram bot called backend endpoints with no credentials at all. Every command failed with 401, so the bot had been decorative for weeks and nobody noticed. Fix took an afternoon: scoped API keys plus a new auth path. Lesson: unauthenticated integrations fail silently. Monitor the failure, not just the uptime.
Schema audit: the database disagreed with the code
Eight tables and four columns existed in production but in no migration file. Fresh installs were missing them. Every "works on prod, breaks on staging" mystery traced back to this drift. Fix: four backfill migrations, plus a model-vs-database diff check. Lesson: the migration chain is the source of truth, or nothing is.
Content audit: our sitemap lied (a little)
Two URLs in our Search Console coverage redirected instead of serving. Turned out fine - http-to-https by design - but the hour proving it was worth it. Lesson: verify redirect chains with curl, not assumptions, especially before telling anyone "everything is fine".
The full write-up with all five audits: https://www.24go.site/blog/5-auditov-svoego-saas-chto-nashli?locale=en
What I would repeat
Time-box each audit to a day. Log issues with severity, not essays. Fix the critical path the same week or the report rots. And publish the ugly parts - our mistake post outperformed every feature announcement. Details on setting up your first campaign after the dust settles: https://www.24go.site/blog/how-to-set-up-first-lead-generation-campaign?locale=en
Honest limits
An audit finds what its checklist knows. Ours missed things customers found later. Audits decay from the day they finish - schedule the next one before closing the current.
Also: 62 sounds dramatic. Forty were trivial. The number got the clicks; the five critical ones did the work. Count issues, but weight them.
When did you last audit your own product like a stranger?
Top comments (0)