Harden a product before launch
Launch is close and nobody has looked at the security, the bot exposure or the data-handling obligations.
Security review, automated usability testing, vulnerability scanning in CI, and the edge and bot policy that keeps a product reachable but not scrapeable.
For technology companies the engagement is usually a specific hard problem rather than a whole build: a security review before a customer audit, deterministic vulnerability scanning that does not send source to a model provider, or a bot policy that stops scrapers without stopping Googlebot.
Launch is close and nobody has looked at the security, the bot exposure or the data-handling obligations.
It worked at a hundred users and it is failing at ten thousand. Pages time out, the database is pinned, and the hosting bill is climbing faster than revenue.
A general-purpose model does not know your domain, your terminology or your documents, and no amount of prompt engineering is fixing it.
Everyone wants an assistant in the product, and most of them are a chat box bolted to a landing page that answers questions wrong with total confidence.
Last reviewed · Site changelog