Lovable Website Builder Reviews: A Joiner's First Site, Step by Step

Sometimes. Lovable can produce a five-page joinery site in an afternoon, but with no developer you become its maintainer: a custom domain needs a paid plan (Pro starts at $25 a month), the enquiry form needs a form service or a backend, and every later change is another prompt. Wix or Squarespace suit owners who want a hands-off site.

The catch is upkeep, not the build. Take a made-up three-person workshop that makes staircases, fitted wardrobes and kitchens: about five hours and 16 to 30 credits should get five pages and a working enquiry form live, and after that the form, the pages and the credit balance need 20 minutes of checking every month. Those minutes and credits are a planning budget drawn from Lovable's published pricing and documentation (read in early November 2026), not a timed client job, so keep your own log and trust it over mine.

Follow me on Instagram@sagnikteaches

A word on reviews. Lovable describes itself as a platform for building web applications, so a review you find may be about apps with logins and databases. A joinery brochure site is the easy end of what it does: a review about broken app logic may not apply to you, while one about credits vanishing on fixes still does. The useful question is narrower. Can you get five pages, a gallery of real work and a working enquiry form live for a known number of hours and a known monthly cost, and can you keep it working afterwards?

Connect on LinkedInSagnik Bhattacharya

What a joinery site has to do, and what it can skip

A joiner's site has one job: turn someone who has admired a photo of a staircase into someone who phones or sends measurements. Everything else is decoration. That shortens the brief, and it is why Lovable is a fair test here. There is no shop, no booking engine and no member login to get wrong.

Subscribe on YouTube@sagnikteaches

Notice what is missing: a news section, a shop, customer logins, a chatbot. A brochure site does not need a database at all, apart from wherever the form's messages end up. Keeping the brief that small is also what keeps the credit bill small.

The test brief: five pages, one form, one afternoon

The brief is Home, What we make, Our work, About and Contact, one enquiry form, a custom domain, published. Pass means all five of these hold: the site is live on your own domain; a test enquiry from your phone reaches your inbox in under a minute; every page reads properly on a phone; you spent no more than five hours; and you used no more than 30 credits, which is the monthly ceiling on Lovable's Free plan (5 build credits a day, up to 30 a month). That last line is deliberately tight. If a five-page brochure site cannot be built inside the free allowance, you want to know before you pay.

Here is the planning budget, step by step. Fill in the last column with what really happened.

For scale, Lovable's credits page says Build mode is priced by the work done, with illustrative examples from about 0.5 credit for a colour change to about 2 for a landing page with generated images. Plan mode costs 1 credit a message plus any research it runs. So 16 to 30 credits assumes roughly 20 prompts at an average of one credit or a little over, which is realistic only if you give each prompt one clear job.

The money side is short. The build test on Free costs nothing. Pro starts at $25 a month (about $21 a month if you pay $250 for the year), and Lovable's plans page shows Pro as the plan where custom domains and removal of the "Edit with Lovable" badge begin. A domain is extra, priced by whichever registrar you use or at Lovable's own checkout. If you want the enquiry form to send email through Resend, its free plan covers 3,000 emails a month with a limit of 100 a day, far more than a workshop will see. So a realistic first month is the Pro fee plus a domain, and from month two it is the Pro fee alone. The full tiers and credit arithmetic are in our Lovable pricing and credits tutorial.

Prompts that give a joiner's site a sensible first pass

Lovable has a place for rules it follows on every request: Project settings, then Instructions (the feature was previously called Knowledge). Fill that in before the first page prompt, because it is the cheapest way to stop invented claims. Here is a starting version to adapt.

You are building the website for [Business name], a three-person joinery workshop that makes bespoke staircases, fitted wardrobes and kitchens, and repairs period joinery.

Rules for every request:
- Use only facts I give you in the chat or in these instructions. Never invent testimonials, awards, years in business, project counts, prices, accreditations or customer names. If a fact is missing, write "TODO: [what is needed]" in plain text so I can find it.
- British English. Short sentences. No slogans such as "crafting dreams".
- Every page has the phone number [number] as a tap-to-call button in the header, and the enquiry form or a link to it near the bottom.
- Use only the photos I attach. Never add stock or generated photos. Give every photo alt text and a caption in this form: what it is, the timber, the finish.
- Plain design: off-white background, dark text, one accent colour taken from the logo, large photos, no animation that slows the page.
- Five pages only: Home, What we make, Our work, About, Contact. No news section, shop or login.

Then one page per prompt. The home page prompt names the order of blocks and supplies the facts, so Lovable has nothing to improvise.

Build the Home page. Order: header with logo and call button; a headline that says what we make in plain words ("Bespoke staircases, wardrobes and kitchens, made in our own workshop"); three short blocks (Staircases, Fitted wardrobes, Kitchens), each linking to the What we make page; a strip of three photos from the gallery; a four-step "how a job runs" (visit and measure, drawings and quote, make, fit); a call-to-action block with the phone number and the words "Send us your measurements"; a footer with business name and contact details.
Use these facts and nothing else:
[paste services, how a job runs, workshop details]

The gallery is where first-timers lose credits, because large photos and loose instructions invite rework. Lovable accepts up to 10 attached files per message, with images totalling up to 15 MB a message (it compresses large ones), so send eight at a time and number the captions in the order you attach them.

Build the Our work page as a grid of the 8 photos attached to this message. Captions, in the order attached:
1 Open-string oak staircase, oiled finish
2 Fitted wardrobe, painted MDF doors, oak interior
3 [continue to 8]
Tapping a photo opens it larger. Keep the files small so the page loads fast on a phone. Use each caption as the alt text. Do not add any photo I have not attached.

Before you go further, make Lovable audit itself. This prompt suits Chat mode, which discusses the project without changing code. Lovable's credits page priced chat messages at typically a fraction of a credit under a temporary offer that ran to 31 October 2026, so check what a chat message costs now before you lean on it.

Read every page. List each sentence that states a fact I did not give you: years, numbers, awards, qualifications, materials, guarantees. Change nothing. Wait for me to say which to keep.

A reply to that prompt tends to look like this (illustrative, not a recorded run):

1. About, paragraph 1: "With over 20 years in the trade": not in your instructions.
2. Home, headline block: "Every staircase comes with a 10-year guarantee": not supplied.
3. What we make, Kitchens: "Solid oak as standard": you said oak or ash, chosen per job.
4. Footer: "Members of a national joinery federation": not supplied.
5. Our work, photo 3: "hand-cut dovetails throughout" was added to the caption you gave.

Fix it in one prompt, not five: "Delete items 1, 2, 4 and 5. Change item 3 to: Oak or ash, chosen with you for each job." Then read the pages yourself, because the audit only lists sentences it recognises as claims, and a phrase such as "fully insured" can slip past it. That ten-minute read is the cheapest protection against a customer quoting your own website back at you.

What the first pass usually gets wrong

These are the faults to hunt for on a first read (illustrative, not a recorded run). Each one has a one-line fix prompt.

• Confident claims you never supplied. "Over 20 years of experience" or "trusted by hundreds of customers" appears in the About copy. Fix: "Remove every claim that is not in my instructions."
• A form with no confirmation. It submits, then the page does nothing. Fix: "After submitting, replace the form with: Thanks, we reply within two working days. If it is urgent, call [number]." Only promise a reply time you will keep.
• Photos that all look the same size. A tall staircase photo gets cropped to a thin strip. Fix: "Show each photo uncropped at its natural shape."
• Headings that sound like a brochure. "Where vision meets craftsmanship". Fix: "Rewrite headings as plain labels: Staircases, Fitted wardrobes, Kitchens."
• Placeholder contact details left in the footer. Search the live page for TODO and for example addresses before publishing.

Hosting, the domain and the badge: what the free plan cannot do

Publishing is one dialog. Lovable puts the site at an address ending in lovable.app, and nothing you change afterwards reaches visitors until you click Publish and then Publish changes. That catches people out on their first edit. The free address is fine for showing your family and no good on a van door.

A custom domain needs a paid plan. You can buy one inside Lovable or connect one you own. The manual route is an A record plus a TXT verification record at your DNS provider, with Lovable showing the exact values, or an automatic route that asks your provider for permission. Its docs say changes can take up to 72 hours, though most finish within a few hours, and Lovable issues the security certificate itself. If the domain still points at an old host, clear the old address records first: the guide says it must have no AAAA record when you connect.

Two details matter to a business. Each project has one primary domain, and any other domain you connect redirects to it with a temporary (302) redirect, so settle on www or the bare domain on day one. And hosting is included but not free of credits: Lovable's publishing page says hosting and the built-in backend use credits as the app is used. For a brochure site that is small, and it is why the monthly check later includes a glance at the balance.

Three ways to wire the enquiry form, and the one I would pick

Lovable's documentation has no dedicated forms page. The nearest thing is a Tally connector, which lets an app create forms and fetch their submissions through Tally's API; its examples are dashboards and lead lists built from responses, not a contact form on a brochure site. That tells you something: a contact form is something you assemble, not something the builder hands over finished.

For a first site I would use the embedded form tool, with a tap-to-call button and a plain email link beside it. The reason is a verified one: when a Lovable workspace runs out of credits, the published pages keep serving but anything needing the built-in backend pauses, and Lovable's out-of-credits page names the database, storage and sign-in as examples. An embedded form lives on the form tool's servers, so a bad month on credits cannot silence it. Move to Resend later if you want enquiries to arrive in a Lovable-styled flow. The domain-email side of that is covered in our Lovable email setup tutorial.

Whichever route you choose, test it like a customer. Send an enquiry from your phone on mobile data, not your workshop wifi; check the inbox and the spam folder; reply to it from the address you advertise; and repeat monthly. If you do store enquiries in a Lovable database, run the security scan before publishing. Lovable says the quick scan runs automatically on every publish and checks tables for missing per-record access rules, and also that its scans cannot guarantee complete security. Our security checklist for vibe-coded apps lists what to look at before customers' names and phone numbers sit in a table.

Will customers find it? What Lovable gives you for search

Search is the area where template builders have a head start, so read this part twice. Lovable's SEO page says new apps created from 13 May 2026 use TanStack Start with server-side rendering, so every request returns fully rendered HTML. Older React and Vite projects behave as single-page apps for people and are pre-rendered only for verified crawlers, and an existing project can be upgraded to the newer setup at normal credit cost. Ask which kind your project is before you rely on it.

The same page is candid about the rest. Every new project gets a robots file, but a sitemap is not always created and the starting metadata is generic, which means every page can carry the same title. Lovable has an in-chat SEO and AI search review that checks the sitemap, metadata, headings, alt text and structured data and can fix most findings in one click, and it connects to Google Search Console. It also says the review does not guarantee rankings and does not score page speed.

A joiner's checklist for the afternoon after publishing:

1. Give each page its own title and description, with what you make and your town in the title of the Home and What we make pages.
2. Check that every photo has alt text that describes it, which the instructions above already ask for.
3. Run the SEO review, apply the fixes you understand, and connect Search Console so Google hears about the sitemap.
4. Make sure your business name, phone number and website are written identically here and on your Google Business Profile, which is worth setting up before the site goes live.
5. Open the live site on a phone over mobile data and time how long the gallery takes to appear. If it feels slow, ask Lovable to shrink the images.

What breaks, and who fixes it on a Sunday evening

The honest answer to "who maintains it" is you, with a freelancer as backup. These are the failures to plan for.

• A prompt changes something you did not ask about. Lovable saves every change as a version. Revert restores the code and your chat history stays, but it does not roll back database data, so a form's saved messages are untouched. For one bad change, "Undo latest edit" is quicker.
• Credits run out mid-month. Building stops, the published pages keep serving, and backend features pause. Set a low-balance alert under Usage limits and alerts and keep a few credits spare.
• The form's email stops arriving. Usually an unverified domain, an expired key or a spam-folder rule. This is the failure that costs real jobs, which is why the monthly test exists.
• Small text changes eating credits. A new phone number or opening hours does not need a prompt. Typing over text directly in the preview is free within limits Lovable states on its preview-toolbar page, after which inline edits cost credits too.
• You stop paying. On Free, existing domains keep working but you cannot connect new ones, and a free project with no custom domain can be unpublished once it has gone 12 months with no visits and no owner login. Keep the GitHub copy current.
• Nobody knows how it works. Git sync gives a freelancer the code, but Lovable says it does not deploy changed backend functions when commits sync, so a form built on its backend still needs the Lovable account. If a build stalls, our guide to hiring a Lovable expert (listed under further reading) covers the brief and the budget.

A 20-minute monthly check that keeps the site honest

1. Send a test enquiry from your phone and confirm it arrives within a minute.
2. Open every page on a phone and tap every button, including the call button.
3. Look at the credit balance and the date it refills.
4. Check opening hours, phone number and any prices or lead times against reality.
5. Add one new job photo to the gallery, with caption and alt text. Fresh work is the best reason for a visitor to believe you are still busy.

Lovable, Wix or Squarespace for the same joinery site

Here is the same five-page site through three tools. Plan prices are USD list prices on annual billing as of October 2026. Wix and Squarespace show different prices and plan names in some countries, so confirm on your own pricing page.

Put the first year side by side and the money gap is smaller than the monthly prices suggest. Lovable Pro on annual billing is $250, plus a domain, which a budget registrar sells from about $11 a year for a .com: roughly $261. Wix's entry plan is 12 × $17, or $204, and Squarespace's is 12 × $19, or $228, each with the first year's domain included. So the three sit within about $60 of each other in year one. The real difference is who carries the upkeep: on Lovable it is you, with the credit balance and the form wiring added to the monthly check.

We have separate walk-throughs of the other two for tradespeople: a plumber's site built and checked in Wix and Squarespace's AI builder judged on an electrician's site. For the wider question of a brochure site versus an app, see Lovable against Wix for a small business site.

The verdict for a joiner with no developer

Pick Lovable if three things are true. You enjoy fiddling and will happily spend an evening a quarter on the site. You want a custom look rather than a template. And you accept a monthly 20-minute check as part of owning it. In that case run the Free test first, then pay for one month of Pro to connect the domain, and decide at day 30 by looking at your log: if you stayed near 30 credits and needed no outside help, keep going.

Pick Wix or Squarespace if your main goal is to be live this week and never think about hosting, backends or credits again. The visual editor, the built-in form and the vendor's own security patches are worth the lack of a custom look for most workshops, and a hosted builder gives you one fewer thing that can silently stop working. Pick a freelancer if you want the site off your plate entirely and can afford a one-off fee plus a small monthly retainer.

My own lean for a three-person workshop with no appetite for maintenance is the template builder. The point of the test above is that you do not have to take my word, or anyone's review, for it: five hours and a log of credits will tell you.

Questions joiners ask before paying for Lovable

Can I move my Lovable site to another host later?

The code, yes. Git sync keeps a repository you own on GitHub, GitLab or Bitbucket, and Lovable's docs say you can self-host or deploy elsewhere from it. The repository carries the code, not the running services: the database, stored secrets and the backend its functions run on stay with Lovable, so a plain gallery-and-form site moves easily while one built on the built-in backend needs a proper migration.

What happens if I stop paying for Lovable?

If you downgrade to Free, domains you already connected keep working, but you cannot connect new ones. Free workspaces may also have a project unpublished after 12 months with no visits, no owner logins and no custom domain. Keeping a synced GitHub copy means a lapsed payment never costs you the site itself.

Do I need to know any code to build a trades website in Lovable?

Not for a five-page brochure site, but you do need to judge the result. You must read every sentence it writes, test the enquiry form from a phone, and find your domain's DNS settings. Those three jobs are where first-timers get stuck, so budget an evening for them instead of assuming the prompts handle everything.

Will a Lovable site rank on Google as well as a Wix site?

Neither promises rankings. Lovable's docs say apps created from 13 May 2026 are server-side rendered, older ones are pre-rendered for verified crawlers, and its own review tool does not guarantee results. Local results also lean on your Google Business Profile, reviews and useful service pages, whichever builder you pick.

Further reads

• Joinery Quotation Template: Bespoke Items, Finishes, Lead Times With AI — Once the site brings enquiries, quote them consistently.
• Website Builder With AI Chatbot: Which Suits a Trades Business? — If you want an AI chat box on the site as well.
• Joinery AI App Checklist: What to Check Before You Pay for One — Questions to ask before paying for any joinery software.
• Wix AI Builder Pricing: Which Plan a Small Trades Firm Needs — Light, Core, Business or Elite? Wix plan prices read on the day, what each gives a trades firm for forms, bookings and deposits, and what to skip.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Lovable documentation (plans, credits, publishing, custom domains, built-in backend, SEO, Git sync, version history, preview editing), Wix and Squarespace pricing and help pages, Resend and Tally pricing pages, read in early November 2026.