The spreadsheet we wanted to replace

Sam is a fictional handyman. His spreadsheet tracks inquiries, quotes, job stages and callbacks. We gave Lovable the same fictional customer records and a brief for a small CRM. This was a new build, not a spreadsheet import.

The three starting inquiries were Alex, overdue; Jordan, due that day; and Casey, upcoming. Those groups use the fixed scenario date of October 30, 2026, shown in the app. They do not use the date you read this article.

The job was deliberately small: New, Quoted, Booked and Completed stages, quote estimates in USD, notes and follow-up dates. No real customer data, payments, invoices, email, SMS or calendar connections were used. The callback list is a list to act on, not an automatic reminder service.

The original build prompt

This is the original build prompt, including the fictional seed records. It is not the later date-field change. Keep the scenario date when reproducing this demonstration, or change it deliberately for a different app.

Build an internal web CRM for Cedar Lane Handyman, a fictional solo handyman business. Track inquiries through New, Quoted, Booked and Completed. Each record has a unique reference, customer name, job summary, USD quote estimate, status, date-only next follow-up and plain-text notes. Let the owner create a record, open and edit it, search by customer, and filter by status. Save records persistently using the platform's native included backend and authentication, once any required setup is approved. Reject a blank or whitespace-only customer name or job summary, a negative USD estimate, and an invalid date. Show a useful message and do not save invalid input. Show a simple open-jobs list and a follow-up list. Open means New, Quoted or Booked. Completed jobs remain in history but disappear from open jobs and follow-ups. For this demonstration, use October 30, 2026 as the fixed scenario date and display "Scenario date: Oct 30, 2026" in the header. Calculate follow-up groups from that scenario date, not the current clock. Mark an open record overdue only when its follow-up is before that date. Show due-today separately. Use the three starting records in section 1 exactly. Provide a clear empty state. Require an owner login for business records; do not use a visible role-switch button as proof of access control. Make the layout usable at a 390px phone width. No payments, invoices, email, SMS, calendar sync, AI assistant, scraping or external integrations beyond the approved native backend/auth needed for these requirements. Do not add extra features.

Starting records (fictional, use exactly):
CL-101 | Alex Reed | Repair a sticking door | New | $120 | Next follow-up October 29, 2026 | Note: Asked for a quote. No reply recorded.
CL-102 | Jordan Lane | Fit two shelves | Quoted | $240 | Next follow-up October 30, 2026 | Note: Quote sent. Waiting for a decision.
CL-103 | Casey Park | Patch a wall | New | $180 | Next follow-up November 2, 2026 | Note: Asked for a quote. Send after photo review.

What worked in the customer workflow

We added Morgan's cabinet-handle job with a $75 estimate and a November 3 follow-up. After save, reload and reopen, the record was still there. Search found Morgan, and the filters separated the job stages.

We changed Alex's status to Quoted, estimate to $135, note and follow-up date. The preview then stopped responding with a proxy error. After recovering a new preview address, all four saved edits were still present. Alex was no longer overdue.

Marking Jordan's job Completed reduced open jobs from four to three. Jordan remained in history after a reload. At an emulated phone width, Casey's note edit also persisted. That was Chrome emulation, not a physical-phone test.

The date catch, and one change

Blank names and negative estimates were rejected on the tested paths. The date attempt needs more care. The browser's segmented date control discarded an invalid entry and left the field incomplete. The app then saved the job with no follow-up date and no warning. That does not prove it accepted February 31 as a real date. The original prompt did not require every job to have a date.

We asked for a typed date field. In the recorded retest, 2026-02-31 was rejected with an error. The calendar picker was gone. The earlier empty-date record remained; this change did not clean up old records.

The repaired field was not retested at phone width. Do not assume the earlier phone check covers the changed form.

What the access checks do and do not show

Signing out showed the owner login. A fresh session's records request returned an empty list. A second account saw a blocked screen and no records.

Those are useful checks, not a full security audit. The video does not show a second user's create, edit or delete attempts. We did not test the published app. Before using real customer information, check read and write permissions in the actual deployment, not just the login screen.

The recorded credit cost

The build used 3.2 daily credits and the date-field change used 1.1, for 4.3 in total. The supplied run notes say the bonus balance was untouched.

These are the figures for this recorded run, not a fixed price for a CRM or a promise about today's allowance. Check Lovable's current plan before starting your own build.

For the broader product test, read our Lovable review. This article is a separate contractor-CRM use case, not a new score or a comparison winner.