01
Before
Different people arrived with different needs.
Growers needed crew details. Applicants needed jobs. General questions needed somewhere to go. A single broad contact path made the team sort out the difference later.
Pearls Farm / grower intake and operations
A farm site built around the calls the office actually gets.
The business did not need more pages. It needed growers, applicants, and the Pearls team to stop entering the same conversation.
6
Grower services
2
Separate paths
2
Languages
The business owner view
The site sorts the conversation before the office has to.
02
The build
Each audience got its own next step.
The public site explains six service lines. Crew requests collect crop, acreage, location, timing, and work type. Hiring has a separate English and Spanish route.
03
Owner view
The request arrives with context attached.
Customer demand, applicants, subscribers, and site activity live in distinct views. The team can open the right queue without untangling the audience first.
Three people, three useful outcomes
Every visitor knows what to do next.
A grower
Reviews the work and requests a crew
Crop, acreage, location, timing, and service needs arrive together.
See the crew request →An applicant
Uses a separate hiring route
English and Spanish paths keep job interest out of the customer pipeline.
See the job path →The Pearls team
Opens the right operating view
Customer requests, hiring interest, subscribers, and site activity stay separated.
How I saw the job
A grower should not have to write a perfect message, and the office should not have to decode a vague one.
This case study describes the system that is live. It does not present an inquiry, an analytics event, or a website visit as closed revenue.
Have a business with mixed up intake?