Choices and process
The decisions made before the first line of code: build or buy, CRM or ERP, how to pick a vendor and how to tell a project is drifting. A mistake here costs more than any technical one — it surfaces six months later.
Vibe-coded app broken after launch? What to check and what to fix first
In short: an app built with AI tools and no engineer rarely breaks in the interface. It breaks where nobody looks: a database anyone can read, secret keys shipped to the browser, payments that never become orders, no backups and no monitoring. Fix data first, then money, then backups and monitoring. A full rewrite is not always needed: most projects can be rescued in parts.
Supabase security checklist: check RLS, keys and storage in your own app
In short: in a Supabase app, the browser talks to the database directly, and Row Level Security (RLS) is the only thing deciding who sees which rows. Check four things in your own project: RLS is on for every exposed table, the policies limit users to their own data, no secret key ships to the browser, and storage buckets are not public by accident. The Security Advisor in the dashboard catches most of it. If a secret key leaked, fix the cause, then rotate.
Rescue or rewrite an AI-built app: how to decide, and what to fix in what order
In short: most AI-built apps are cheaper to rescue in parts than to rewrite. A rewrite is justified when the data model is incoherent, when you cannot get access to your own code and infrastructure, or when the platform cannot support where the business is going. Decide on audit findings, not frustration, and fix in order of damage: data, money, backups, monitoring, then code.
How to hire someone to fix your AI-built app without losing control of it
In short: before anyone touches your app, make sure the code, database, domain and payment accounts are in your name. Give each person the narrowest role that lets them work, never your own passwords. Start with a fixed-price diagnosis that delivers a written, ranked list of problems and a plan with prices. Be wary of proposals that promise a rewrite or a timeline before anyone has looked at the code.
CRM or ERP: which one your business needs
In short: CRM handles the money that has not arrived yet — customers and deals. ERP handles what is already inside the company: stock, purchasing, production, finance. Almost always, start with CRM.
How to choose a development vendor and not get burned
In short: look past the portfolio and the price at how they build an estimate and what the contract says about source code ownership. A portfolio can show someone else’s work and a price can be lowballed, but those two things are hard to fake.