TWO LEAD SYSTEMSAmbulance 24 and Home Nursing
Two focused websites for distinct problems that reached more than 10 inbound calls per day in their first week.
Image from the project’s public version, captured to document this case study.
How does the project work?
The four stages below show the product’s primary flow without exposing sensitive data or details.
- 01 / 04
A specific need
Each domain focuses on one service type and one primary search intent.
- 02 / 04
A quick answer
The page immediately explains the service, use scenarios, and path to action.
- 03 / 04
Preparing the call
The user knows what patient information to have ready before calling.
- 04 / 04
Conversion to a lead
The inbound call becomes a real measure of website performance.
Problem, build, decision, outcome.
- 01 / PROBLEM
Two medical services with two distinct search intents
Patient transport and in-home nursing address different needs. One large portal would have made the message and action path unclear for both groups.
- 02 / BUILT
Two independent, call-focused sites
For each service, lightweight scenario-led pages were built so users could quickly find the service, the information needed before calling, and the coordination path.
- 03 / DECISION
Clarity and speed over a large scope
The domains, opening messages, and CTAs remained separate, while the conversion logic and content standards stayed aligned across both sites.
- 04 / EVIDENCE
More than 10 inbound calls per day in the first week
Based on recorded data from operating the two sites together, their combined daily inbound calls exceeded 10 in the first week. This figure does not guarantee performance for other projects.
Full project notesOPEN PROJECT NOTES
Two domains, two problems, one clear measure
Rather than build one large medical-services portal, two focused, clear experiences were designed: one for arranging patient transport and the other for in-home nursing services. Each site needed to address its user’s primary need without distraction.
The success metric was never visits or time on site; it was a relevant inbound call.
Reducing scope to increase clarity
Ambulance 24 explains transport scenarios from home, hospital, and intercity routes. Home Nursing focuses on elder care, post-discharge care, and regular in-home services.
This separation let each site’s opening message, pre-call information, and CTA align precisely with the user’s situation.
The page should prepare the user for the conversation
In phone-based services, good content does more than rank: it improves the quality of the next conversation. Both sites foreground information needed before coordination: the patient’s condition, origin, destination, or type of care required.
This design helps turn a completely vague call into a more prepared conversation.
Speed, focus, and publishability
The lightweight structure and limited page count enabled quick release and content updates. Decorative elements were kept to a minimum so phone numbers, service availability, and operational information stayed first.
Each domain has an independent identity, while the conversion logic and content standards remain aligned across both experiences.
More than 10 daily calls from the first week
According to data recorded from the project’s operation, the two websites together reached more than 10 daily inbound calls from locations across the country in their first week.
This is stated as the combined result of two sites and does not guarantee performance for other projects. Call quality and the business’s final conversion have not been made public on this page.
A small product can signal quickly when it is precise
This project showed that a limited but problem-led website can test its value sooner than a feature-heavy platform. A smaller scope also makes measurement clearer.
The next step is to separately record call quality, geographic coverage, and landing pages so future content decisions become more precise.
A second problem, with its own path.
What was built within the project scope.
This list is based on project outputs that can be stated publicly—not speculative features or unverified technology.
- 01Two-domain strategy
- 02Focused content architecture
- 03Design and development of two sites
- 04Service and scenario pages
- 05Call path
- 06Inbound-call measurement
- LEAD GENERATION
- LANDING SYSTEM
- CONTENT DESIGN
- SEO
- CONVERSION SIGNAL
Do you have a similar challenge?
If your project sits between web, operations, content, and automation, we can first clarify the problem and the shortest path to build it.
Start a conversation on Telegram