First, I am amazed at Lovable’s capabilities and ease of use. It’s almost too good, which caused me some extra work. Here are some tips: I started my projects working with Claude to create a scope of work, and a project description. It help me build n8n workflows, design the UI, scope the database and tables, and ultimately a big Lovable prompt. My biggest mistake was creating my database and associated tables in Supabase. Don’t do that! Link Lovable to Supabase and it will create those databases for you. u my own caused a lot of confusion as Lovable was not using them. Just give Lovable the full script and let it work. You will have many revisions. Everything from small tweaks to big changes in the layout, adding pages (terms of service, Privacy, ADA, contact, etc). Test everything. If you integrate a payment platform like Stripe, test it. If you have a free trial, make sure that Lovable actually sets an expiration date for the trial. Follow the suggestions to fix security holes. Make your site ADA-compliant. Test it on multiple devices. Make sure it renders well on mobile. Lovable makes suggestions after it executes most prompts. Use them. You can build a great app with fewer than 200 tokens, even 150. That’s making something that looks professional and COMPLETE.

I’ve been focused on building automations for my company. Everything from a company credit card and bank account auditor to processing terrible pdf reports into a nice proposal with a great pricing table in PadaDoc. Also created transient voice agents that are incredibly useful. My latest project was to make something to track our small fleet of about 15 vehicles and drivers. Most platforms out there were expensive, and didn’t really do what I want, which was to alert my fleet supervisor (part time) when something was expiring - like registration, insurance, service contract, aged vinyl wraps, even the driver’s licenses. I used Lovable as my UI for this. Workflows in n8n and Supabase for the backend. It’s pretty cool. I don’t have GPS yet, as that requires buying a dongle that plugs into the car’s ODB port, but that is next. I was more concerned with the administrative side vs. physical tracking. This app called Fleet Nanny does that. You enter users and give them a role; admin, supervisor or driver. Then send an invite. They are then responsible to add their info and upload their DL. AI extracts the info from the DL and populates the fields (Date of birth, address, expiration date, etc). Likewise, the cars are added with basic info and assigned to a driver. The driver takes pictures of each side of the car, interior, etc and tracks the mileage, reports when service was performed, updates the mileage and so on. They get a reminder email monthly to do these things. The supervisor gets monthly reports on everything, including alerts when something is coming up for expiration. I decided that this can be monetized with a monthly subscription. Please check it out if you have some time. https://www.fleetnanny.com Future upgrade will include the GPS layer with geofencing and reports from whatever useful I can get from the Dongle provider.

When open AI discontinues 4.0, will 4.1 mini disappear also? I can’t find information on that. I have a lot of workflows that rely on it and it will be a big job to upgrade it. I tried five mini and it does not do what I want.

https://youtu.be/oi6zp2ex3tI

So many people are just weird about speaking to a voice agent. We have tried several different greetings to build confidence, but people still simply want to leave a voicemail. For those of you building successful voice agents to answer the phones. What have you found to be the best greeting to lead people to a conversation?