Sample post: the questions to ask your AI before you launch

This is a sample post, not a published one. It exists to prove the blog section works: the index, the page, the meta tags, and the rule that a `## LinkedIn` section at the bottom of a draft is never rendered. Adam and Herald write the real posts: one a week, each ending one step from the shakedown.

The real posts follow the same shape this one does: a question a founder should ask their AI before launch, what a good answer looks like, and what happens if nobody asks.

What a good answer looks like

Ask your AI: "Where in this app can a logged-in user reach data that belongs to someone else?" A good answer names the specific routes and the specific tables (the bookings endpoint that returns every booking, the profile page that loads any user by id) and says what it will change. A bad answer says "I've added proper access control" and changes nothing you can check.

The difference is not effort. It is whether the question was asked.

What happens if nobody asks

• The bookings list shows every customer's bookings to every customer. Anyone can read everyone's data.
• The admin route has no check at all. Anyone who finds the URL is in.
• The API key is in the client bundle. Anyone can read it, and the bill arrives with it.

None of these are exotic. They are what happens when the app was built to work, not to be safe, and nobody asked the question that would have found them.

The shakedown is me asking all of them

I go through the whole app and ask every one of these questions (the access ones, the key ones, the bill ones, and many more of the common pitfalls) and hand back a ranked report with a fix prompt per finding that your own AI can apply. Quoted up front for the size of your app, fixed once agreed.

See the offers or book a shakedown.