Case Study / Travel Brands

Connecting travel websites, campaign pages, contact data, and email follow-up.

Siciclando and Soul Italy needed a digital presence that matched their personal travel-planning model. Hatchery built and supported the websites, then connected campaign landing pages, Brevo, contact migration, API integration, and automated follow-up.

Warm Italian countryside landscape used for the Siciclando and Soul Italy travel website case study.
2 Connected travel brands Siciclando and Soul Italy.
1,500 Contacts migrated Moved into Brevo for ongoing campaigns.
API Landing page connection Campaign requests flow into the email platform.
Long-term Business and technical partner Website support, campaign work, and platform improvements.
At a glance

Siciclando / Soul Italy

Website design and development for custom Italian cycling and walking travel experiences.
Continued website and technical support as the brands evolved.
Brevo selection, contact migration, API-connected landing pages, and automated email follow-up.
A more connected path from visitor interest to an active travel-planning conversation.
Problem

Personal travel needs a digital path that feels clear and human.

Siciclando and Soul Italy do not sell generic travel packages. Their trips are shaped around the traveler, so the websites and campaign flows needed to explain options clearly, capture interest cleanly, and move people into the right conversation.

Risk

A missed follow-up can mean a missed trip.

Prospective travelers may explore destinations, compare guided and self-guided formats, request sample itineraries, and ask questions before they are ready to book. The website, landing pages, contact data, and email communication needed to work together instead of sitting in separate tools.

Hatchery role

Hatchery built the sites, then kept improving the systems around them.

The work began with website design and development for Siciclando, then expanded into long-term support, campaign landing pages, email-platform selection, contact migration, API integration, and automated email funnels.

Comparison

Separate marketing pieces vs. a connected customer journey

Need Before After Hatchery
Website presence Travel information and inquiry paths needed to keep evolving. A supported website foundation for destinations, tour formats, planning information, and customer entry points.
Campaign pages Specific offers needed focused pages and cleaner capture. Landing pages built around campaign goals and visitor intent.
Contact data Existing contacts needed to move into a better marketing platform. Approximately 1,500 contacts migrated into Brevo.
Follow-up Manual or disconnected steps could slow the customer conversation. API-connected requests, automatic itinerary delivery, and planned email follow-up.
Support model Needs changed as the business and campaigns changed. Long-term business and technical support from the same team.
What Hatchery built

Built as one product system.

Strategy, design, code, integrations, infrastructure, and operations move together so the product can launch and keep serving customers.

Travel websites and campaign pages

Public pages that help travelers explore destinations, understand options, and enter a planning conversation.

Brevo migration and contact structure

Platform selection support and migration of approximately 1,500 contacts into a system ready for campaigns.

API-connected email funnel

Landing page requests flow into Brevo, trigger sample-itinerary delivery, and continue with planned follow-up emails.

Decisions

Product choices that made the work hold together.

01

Design around the traveler

The sites needed to make custom travel feel approachable without flattening the experience into a generic package.

02

Connect the campaign path

A sample-itinerary request should not be an isolated form submission. It should start a useful follow-up sequence.

03

Stay involved after launch

The relationship continued because websites, campaigns, data, and marketing systems need adjustment as the business learns.

Siciclando and Soul Italy today

The brands have a supported digital presence and a clearer campaign path. Website visitors can explore the experience, request information, and enter a follow-up process that connects landing pages, Brevo, contact data, and email communication.

What this demonstrates

This work shows how Hatchery supports companies beyond a one-time website launch. The value is in keeping design, content, campaign pages, data migration, API integration, and follow-up systems connected over time.

Working on a complex marketing campaign, from designing landing pages to implementing email marketing automations, can be tough, but Hatchery made our campaign launch seamless from start to finish. Jean and Kelli were incredibly responsive and communicative, and they went above and beyond by helping us select a new email marketing platform (Brevo) and smoothly migrating our existing contacts. Their expertise and support made a complex process feel easy, and we couldn't be happier with the results!
Hannah Cartwright Marketing, Siciclando and Soul Italy
FAQ

Common questions.

Did Hatchery build the Siciclando website?

Yes. Hatchery designed and developed the Siciclando website and continues to provide website and technical support.

What did Hatchery do beyond the website?

Hatchery supported campaign landing pages, Brevo selection, contact migration, API integration, sample-itinerary delivery, and automated email follow-up.

Can Hatchery help move contacts into a new email or CRM platform?

Yes. In this case, Hatchery helped select Brevo and migrated approximately 1,500 contacts so the team could manage campaigns and follow-up from a better foundation.

Can Hatchery connect a website form to an email platform?

Yes. Hatchery connected landing-page requests to Brevo through an API so a sample itinerary could be delivered automatically and followed by a planned email sequence.

Build with Hatchery

Take the product idea, complex workflow, or AI opportunity and make it real.

Clarify what to build, what to simplify, what to protect, and what must work first.

Idea UX Code AI + data Launch Operate Evolve

Start with Hatchery when

Clarify the path

Talk through the build