Blog

From Lovable to production: what to test before launching an AI-built website

Follow a registration from a Lovable prototype through to the CRM. Decide what to keep, what to fix and what to ask a developer before buying campaign traffic.

Choose one action that matters to the business and test it end to end on the version you intend to share. For a registration campaign, the finish line is a usable enquiry in sales’ hands and a clear next step for the person who registered. A thank-you screen covers only part of that journey.

Test a registration from both sides

Imagine a campaign for an eight-seat workshop. Send the URL to a colleague who has never opened the project. Ask them to pick a date on their phone, register with test details and find their confirmation. Have someone else open the CRM. Did the workshop, correct time, contact details and campaign source come through? Who owns the follow-up?

Try the last available seat and a double tap on “Reserve.” There should be one valid booking, and the team should be able to explain what the next visitor will see. Ask the developer to simulate a delayed CRM response in the test environment. Find where the registration waits, who gets notified and how to recover it once. That exception makes the remaining work easier to estimate.

What to inspect on the published version

Lovable deploys a copy of the project to a shareable URL. Later edits reach the live site when you publish again. Record the tested URL and date, then repeat the journey after the final change. Lovable publishing documentation

  • Domain and navigation. Open the campaign address, share an internal page and reload it directly. Check the title and preview image when sharing the link.
  • Content and measurement. Ask marketing to update the workshop date. Submit a test reservation and compare the tracked conversion with the CRM record. Two clicks can represent one booking.
  • Ownership and cost. Identify who controls the domain, project, database and confirmation email. Record the subscriptions and limits that affect registration and who can close the event once it fills up.

Should you keep Lovable, bring in a developer or change platforms?

Keep Lovable when the important journey works, the team can operate it and the outstanding fixes are small. For a one-off workshop, documenting how to close registration might address most of the operational risk.

Bring in a developer when the screens are already approved and the work left is in permissions, data, integrations or testing. Request a quote to handle a real exception before budgeting for a rebuild. Lovable can sync code with GitHub for collaboration and review. Include the accounts and external services the code depends on in the handover. Lovable’s GitHub integration

Evaluate a platform change when future operations differ from what the prototype proved. If the workshop becomes a bilingual course catalogue with ten monthly contributors, compare editorial workflows in Webflow or Astro with a CMS. If the growing workload is seat allocation and student accounts, evaluate the application and its data first. Ask for separate estimates for retaining, adapting and replacing the working pieces.

What to send for a production estimate

Share a test URL, the priority journey, expected outcome, observed problem and campaign date. List integrations and who manages each one. A useful acceptance test for the workshop reads: “A mobile registrant receives the correct time, sales sees one record and our team can recover a pending submission.”

With that material, MANUBRIO can review what you have already built and what it will take to launch before you spend on traffic. Discuss a prototype with the studio

← Back to the blog

Start a project

Let's build
what's next.

Tell us about your business and what you want to achieve. We'll recommend the right stack and a clear plan, no strings attached.