- Business context
- A home service estimate request that becomes more complete over time.
- My contribution
- The bilingual website intake and n8n orchestration connecting it to the business records.
- Connected systems
- The website, n8n, Google Sheets and GoHighLevel.
Useful information arrives in stages.
A customer may ask for a planning estimate before having every detail available. As the enquiry progresses, the office needs the additional information to remain connected to the same person and the same item of work.
I built the website intake and automation around that progression. An initial estimate starts the record. A separate refinement path carries later answers into the connected sales process.
The design connects the customer experience with the team’s operating records, so the second step has a defined place to send its information.
Follow the estimate journey.
Start with a useful first enquiry.
The bilingual website gathers the information needed for an initial planning estimate. The workflow receives the answers together with language and source context.
- Request
- Initial estimate
- Language
- Carried with the enquiry
- Source
- Website and page context
Give the answers a consistent shape.
n8n normalizes the contact details, service context and estimate inputs. The prepared information can then be used by the connected records.
- Contact details
- Normalized fields
- Estimate inputs
- Structured values
- Business context
- Service area and source
Identify the person and the work.
The initial branch creates or updates the CRM contact, creates the opportunity and retains its identifier. Those records have different responsibilities.
- Contact
- Who made the enquiry
- Opportunity
- The item of work
- Saved reference
- Used by the later step
Let later answers continue the process.
A separate refinement branch consolidates the additional answers, updates the contact information and moves the related opportunity to its next stage.
- New information
- Additional estimate answers
- Connection
- Existing opportunity reference
- Result
- Updated context for the team
Illustrative walkthrough. The descriptions and example records are recreated for this case study.
Give the records different jobs.
- The contact
- Contact details identify the person making the enquiry. The initial branch creates or updates that GoHighLevel record.
- The opportunity
- The opportunity represents the particular item of work. Its identifier is retained so the later branch has a specific record to update.
- The refinement
- Additional answers are consolidated separately from the initial request, then used to update contact information and the corresponding opportunity stage.
- The context
- Language, service area, page and estimate inputs are normalized alongside the contact information. The workflow also carries source attribution into the records.
Connect the experience to the operation.
My work covered the bilingual website intake and the orchestration between the form, spreadsheet records and CRM. The important decisions were what each field meant, which record it belonged to and what should happen when more information arrived.
The first request and the refinement have different responsibilities. Keeping them explicit makes the progression understandable without presenting each new answer as a completely new enquiry.
This is a practical use of workflow engineering: preserving relationships between information as it moves through tools and through the people using them.
What the implementation shows.
The case is supported by review of the maintained website and its active workflow configuration in August 2026. The review identified the separate initial estimate and refinement branches and the record operations described here.
It establishes the implemented connection and the configuration observed at that time. Conversion lift, revenue and hours saved were not measured by that review. The walkthrough above is a recreated explanation of the data journey.
For a similar project, I would also agree the checks for repeat submissions, delayed updates, unavailable systems and human ownership. Those checks must fit the actual tools and the consequences of each action.
Written by Younes Nadif