Renata Cherniavska
← All work Lead flows · Aquinium (Petram Construction)

A lead system for a business that started from zero

A new pool construction business needed a clear way to collect requests. I built the flow for its website form and its email inbox, and both now create leads in Bitrix24.

Company
Petram Construction s.r.o — project delivered as part of my role at Aquinium
My role
The whole project, from the lead flow to team notifications
Stack
Lovable Cloud · Make · Make Data Store · Bitrix24 · OpenAI · Google Sheets · Google Drive · Microsoft 365

the problem

One request is more than a name and an email

A request has contact details, pool type, project size, location, free text and several photos of the site. Without the photos, the team can't prepare an accurate offer.

The company had no structured way to collect all this online. With a new website coming, requests could get lost in the inbox.

what I built

Two channels, one CRM

I started with how a request should move, from the form to the team. Later I added a second scenario, because some customers skip the form and write an email. Then I connected both to Bitrix24.

  1. 1Website form. The customer sends the details and the site photos.
  2. 2Save the request. The data goes to the Lovable Cloud database and the photos go to private storage.
  3. 3Pass it to Make. If the request has photos, Make puts them in a Google Drive folder.
  4. 4Pick up emails. A second Make scenario works with emails sent straight to the company inbox. A Data Store shows which emails were already processed.
  5. 5Sort with AI. AI decides if the email is a lead and pulls out the data. An email that isn't a lead is logged. An unclear one is marked for a manual check.
  6. 6Create the lead in Bitrix24. Make looks for the contact, adds it if it's new, and creates the lead.
  7. 7Update the sheet and the team. Each lead gets a row in Google Sheets. For form requests, the team also gets an email.

Website form

1Request sentDetails and site photos
2Saved in Lovable CloudDatabase and private photo storage
3MakeSaves the photos to Google Drive

Direct email

4Email to the inboxChecked against processed emails
5Is it a lead?AI sorts the email
NO →LoggedNot a request
UNCLEAR →Manual checkA person decides
✓Lead data readyAttachments saved to Google Drive
6 · Bitrix24Finds or adds the contact, creates the lead
7 · Google SheetsA row for each lead. The form also emails the team

two ways in, one CRM

The flow, simplified.

In Make · click to enlarge

The form scenario: photos go to Google Drive, the contact and the lead go to Bitrix24, then Google Sheets and an email to the team.
The email scenario: AI sorts the email, leads go to Bitrix24 and Google Sheets, and everything else is logged.

the website

The website behind the form

The form lives on stavimebazeny.cz, the company's new website. I built it in Lovable as part of the same project.

I planned the page structure, wrote texts for the audience, set up basic SEO and checked the mobile version before launch.

Lovable · Google Tag Manager · Search Console

Visit stavimebazeny.cz

  • Page structure

    Simple, clear pages

  • Texts

    Written for the audience

  • Basic SEO

    Titles and descriptions

  • Mobile check

    Tested on a phone

  • Analytics ready

    Google Tag Manager and Search Console connected

why it's built this way

The decisions behind the flow

A few choices keep the data in order when requests and photos move between systems.

One Lead ID

Every request gets one, from the form or from email. For form requests it follows the request through the database, the automation, the sheet and the Drive folder, so photos stay with the right request.

Private photo storage

Site photos go to private storage in Lovable Cloud, and the team finds them in the request's Drive folder.

A contact check first

Make looks for the contact in Bitrix24 before it adds a new one, so one customer doesn't get a second contact.

Errors in a log

If the AI step or its answer fails, the email scenario writes the error to a log sheet.

the result

What changed

This was a new business, so there is no “before” to compare with. The goal was a process that works from the first request.

69 form requests

Saved in the database so far (November 2026).

Leads in Bitrix24

Requests from the form and from email become leads in one CRM.

Ready to measure

Each form request has marketing attribution, so the funnel can be measured.

No manual transfer

Requests reach Bitrix24 and the team's sheet without copying by hand.

Let's talk Write to me