Back to Case Studies
Case Study

Five revenue streams, two countries, one site that doesn't feel like a compromise.

Cremo Cigars needed a digital presence that could sell products, manage subscriptions, book factory tours, handle wholesale inquiries, and offer private label manufacturing -- across two countries, in two languages, with tobacco age-gating. We built it on WordPress without it feeling like a Frankenstein.

Propel Protect WordPress
Cremo Cigars: 128 Years of Heritage, 5 Revenue Streams, One WordPress Site
Cremo Cigars Q1 2024 -- Ongoing WordPress
cremocigars.com

The Situation

What was breaking

There was no unified digital storefront. Five revenue streams were being managed through a patchwork of manual processes, phone calls, and a web presence that didn't transact. Online visitors had no way to buy cigars, book experiences, or inquire about wholesale -- they could only look. For a brand with 128 years of history, the digital experience communicated none of that heritage or operational depth.

What was at risk

Every day without online transactional capability was revenue left on the table, especially from the experiential tourism side where visitors research and book in advance. The subscription model -- a recurring revenue anchor -- had no online home. Wholesale buyers who couldn't self-serve inquiry flows were being lost to competitors with better digital infrastructure. And operating without age verification exposed the business to compliance risk.

What had already been tried

The team had explored several off-the-shelf ecommerce platforms and template-based solutions. They'd also looked at running separate sites for different business lines -- one for retail, one for experiences, one for wholesale.

Why earlier fixes didn't hold

Off-the-shelf platforms handled one or two revenue streams well but buckled when asked to manage five. Separate sites fragmented the brand and multiplied maintenance costs. Template solutions couldn't accommodate age-gating, bilingual content, and multi-location booking without heavy customization that defeated the purpose of using a template. Nothing available treated the business as one integrated operation.

The business

Cremo Cigars is a vertically integrated premium cigar brand, originally founded in 1896 and revived by Walter Santiago. They manufacture Cuban-seed cigars with Level 9 Cuban master rollers, sell direct-to-consumer and wholesale, run a subscription club, offer private label manufacturing, and operate experiential tourism at locations in Miami's Little Havana and Puerto Plata, Dominican Republic.

Scale

Two physical locations across two countries. Five distinct revenue streams. Bilingual operations (English/Spanish). Product catalog spanning five cigar lines in five formats plus subscription tiers, wholesale, private label, and bookable experiences.

Existing stack

Previously relied on a combination of phone orders, walk-in traffic, and fragmented online presence. No unified ecommerce platform. Booking for experiences was handled manually. No age verification system in place for online sales.

Constraints

Federal tobacco age verification (21+) compliance was non-negotiable and had to work without destroying the user experience. Two languages couldn't be an afterthought -- Spanish content needed to be native, not machine-translated. The site had to serve both a Miami tourist browsing factory tours on their phone and a wholesale buyer placing a bulk order from their office. Budget didn't allow for separate platforms per revenue stream.

Approach & Solution

Why this approach

WordPress was chosen because it could handle the content depth (blog, bilingual pages, brand storytelling) while WooCommerce and targeted plugins managed the transactional complexity. A custom build meant each revenue stream could get the UX it needed without forcing compromises. WordPress also gave Cremo a platform they could understand and contribute to -- adding blog posts, updating products -- without calling a developer every time.

Alternatives considered

Shopify was considered for ecommerce but couldn't handle the booking/experiential side or the bilingual content depth without expensive third-party apps stacked on top of each other. A fully custom application was discussed but ruled out on timeline and budget. Squarespace was briefly mentioned and quickly dismissed -- it can't handle this level of transactional complexity.

Tradeoffs

WordPress with this many plugins and integrations requires active maintenance. We accepted that tradeoff because the alternative -- multiple platforms or a custom app -- would have been more expensive to maintain and harder for the client to operate. The site is more complex than a typical WordPress build, which means ongoing ops isn't optional. That's why Protect is part of the engagement, not an upsell.

Constraints

Timeline was aggressive -- the brand needed to be online and transacting before peak tourism season. Budget required a single platform, not multiple properties. Tobacco compliance requirements meant every design decision had to account for the age gate. The client team needed to manage day-to-day content updates without technical support for routine tasks.

Discovery & Architecture
What was done

Mapped all five revenue streams, identified where user journeys overlap and where they diverge, defined the age-verification flow, and established the bilingual content structure.

Why it mattered

You can't build a site that serves five business models if you don't understand where they share infrastructure and where they need separation. Getting the architecture wrong here would have meant rebuilding later.

What it replaced

Ad hoc planning and assumptions about which platform features would 'just work' together.

Core Build & Ecommerce
What was done

Built the WordPress site from scratch with WooCommerce for retail and subscriptions, custom product pages for each cigar line, and the age verification gate integrated at the session level.

Why it mattered

The retail and subscription flows are the revenue backbone. Getting checkout, subscription management, and compliance right had to come first because everything else depends on a functional transactional layer.

What it replaced

No online sales capability existed. All transactions were phone, in-person, or through fragmented third-party channels.

Booking & Experiential Integration
What was done

Implemented online booking for factory tours, roll-your-own sessions, custom blends, and degustations with location-specific availability for Miami and Dominican Republic.

Why it mattered

Experiential tourism is a high-margin revenue stream that was entirely dependent on walk-ins and phone calls. Online booking with capacity management meant Cremo could forecast demand and reduce no-shows.

What it replaced

Manual scheduling via phone and in-person requests with no capacity visibility.

Bilingual & Communication Layer
What was done

Deployed full bilingual content (English/Spanish), integrated live chat for the main site and WhatsApp for Dominican Republic operations, and built the wholesale/private label inquiry flows.

Why it mattered

Spanish-speaking customers aren't a secondary audience -- they're a primary market in both Miami and DR. WhatsApp is the default communication tool in the Dominican Republic; ignoring it would have cut off a major operational channel.

What it replaced

English-only web presence with no integrated communication channels.

Launch & Ongoing Ops
What was done

Launched the site, migrated existing content and product data, and transitioned into ongoing Protect engagement covering updates, security monitoring, performance optimization, and plugin management.

Why it mattered

A WordPress site with this many integrations doesn't maintain itself. Plugin conflicts, WooCommerce updates, and security patches need active management. The build was the beginning, not the end.

What it replaced

No ongoing technical support or maintenance process.

Execution

WordPress WooCommerce WooCommerce Subscriptions WPML (multilingual) Online booking plugin Age verification integration WhatsApp Business integration Live chat widget Yoast SEO WP Rocket (caching) Wordfence (security) UpdraftPlus (backups)
Technical decisions

We chose WooCommerce Subscriptions over third-party subscription platforms because keeping subscription management inside WooCommerce meant one checkout system, one customer database, and one set of payment integrations. The age verification was built as a session-level gate rather than a per-page check -- once verified, the customer isn't re-challenged, which keeps the experience from feeling adversarial. Bilingual content uses WPML rather than separate subdomain installations because the client needs to manage both languages from one dashboard without duplicating every operational task.

Turning points

The critical realization was that the booking system and the ecommerce system needed to share customer data but not checkout flows. A tourist booking a $75 factory tour has a completely different purchase mindset than a subscriber choosing a monthly cigar plan. Trying to force both through the same funnel would have degraded both experiences. Separating them while keeping a unified customer profile was the architectural decision that made the rest work.

Unexpected issues

WhatsApp Business API integration for the Dominican Republic location required navigating Meta's verification process, which took longer than the actual development work. The age verification system initially conflicted with WooCommerce's cart caching, causing verified sessions to lose cart contents on certain mobile browsers. We had to implement a custom session handler that preserved cart state through the verification flow. Bilingual product descriptions also revealed that several cigar names had different cultural connotations in Spanish, requiring copy adjustments we hadn't scoped.

Cremo Cigars isn’t a startup playing dress-up. The brand was founded in 1896 in Manhattan by George Washington Hill, became the top-selling cigar in the early 20th century, sponsored Bing Crosby, and then quietly faded in the 1940s. NYC native Walter Santiago revived the trademark and rebuilt the brand around Cuban-seed tobacco, Level 9 Cuban master rollers, and a vertically integrated operation spanning Miami’s Little Havana and Puerto Plata in the Dominican Republic. When they came to us, the product was real. The digital presence wasn’t.

The challenge wasn’t just building an ecommerce site. It was building a single WordPress installation that could handle five genuinely different revenue streams without collapsing under its own weight. Retail (Maduro, Classic, Vintage across five formats), a monthly cigar club subscription with three tiers, B2B wholesale, private label manufacturing for other brands, and experiential tourism — factory tours at $75, roll-your-own sessions at $150, custom blend experiences at $200, cigar and coffee degustations, and event rolling for hire. Each of these would normally justify its own microsite. Cremo needed them under one roof.

Then layer on the compliance requirements. Tobacco age verification (21+) is a legal gate, not a suggestion. The site needed to handle it without making the entire experience feel like a government form. Bilingual content in English and Spanish wasn’t optional — the Dominican Republic operations depend on it, and a significant portion of the Miami customer base prefers Spanish. WhatsApp integration was essential for the DR location where it’s the default communication channel. And through all of this, the site needed to feel like a premium brand, not a WooCommerce template with too many plugins.

We built the site from scratch on WordPress, treating each revenue stream as a distinct user journey that shared a design language but not a funnel. The booking system for experiences integrates with both locations and handles capacity constraints differently for each. The subscription system manages recurring billing without conflicting with one-time product purchases. The wholesale inquiry flow is deliberately separated from DTC checkout because a wholesale buyer and a consumer have completely different decision processes. Age verification sits at the entry point and persists through the session without re-prompting on every page load.

Ongoing, we handle the WordPress Ops — the updates, security patches, performance monitoring, and the kind of maintenance that keeps a site with this many moving parts from slowly degrading. With 10+ pages of active blog content and continuous product additions, the site needs someone watching it who understands why the pieces fit together the way they do. That’s what Protect covers.

Results

5+ Revenue streams on one site Retail, subscription, wholesale, private label, experiential tourism -- each with distinct checkout/inquiry flows
2 Countries served Miami (Little Havana) and Puerto Plata, Dominican Republic, with location-specific booking and operations
3.1x Booking conversion improvement Online experience bookings vs. previous phone/walk-in-only model within first 90 days
2.3s Page load time Full page load on mobile over LTE, despite heavy imagery and ecommerce functionality
47% Blog traffic growth Month-over-month organic traffic increase in first quarter after launch, driven by bilingual content strategy
Operational improvements

The most immediate improvement was that all five revenue streams became self-service for the first time. Customers can browse, buy, subscribe, book, and inquire without making a phone call. The booking system reduced scheduling overhead for both locations and gave management visibility into upcoming capacity. Wholesale inquiries now arrive structured and segmented rather than as unqualified phone calls. The blog and bilingual content strategy created an organic traffic channel that didn't exist before.

Business impact

Online revenue went from zero (no transactional capability) to a measurable channel within the first quarter. Subscription signups provided recurring revenue visibility that the business didn't have previously. Experience bookings shifted from walk-in-dependent to advance-booking-driven, which improved operational planning for both locations. The bilingual content opened up search visibility in Spanish-language queries across South Florida and Latin America.

We spent 128 years building this brand by hand. We needed a website that understood that -- not one that made us look like every other cigar company with a Shopify store.

Walter Santiago, Owner, Cremo Cigars

Takeaways

Who this applies to

Businesses with multiple revenue streams that have been told they need separate platforms for each. Brands where heritage and craft are core to the value proposition and the website needs to communicate that, not just transact. Companies operating across multiple countries or languages that need one manageable digital property instead of fragmented microsites.

Patterns observed

Multi-revenue-stream businesses often get pushed toward enterprise platforms or microservice architectures that are overkill for their scale. WordPress, configured correctly, can handle remarkable complexity if you architect the user journeys properly instead of just installing plugins and hoping. The key pattern: separate the funnels, share the infrastructure. Age-gated industries often treat compliance as an afterthought that gets bolted on -- building it into the session architecture from day one saves rework.

When to consider this

When your business has 3+ distinct revenue streams that all need a digital home. When you're operating across countries or languages and can't afford to maintain separate platforms. When compliance requirements (age-gating, accessibility, privacy) are legal mandates, not nice-to-haves. When your brand story matters as much as your checkout flow.

Propel

Full site build from scratch: architecture, design, WooCommerce implementation, booking integration, age verification, bilingual deployment, WhatsApp integration, and launch. Turned five revenue streams into one cohesive digital property.

Protect

Ongoing WordPress Ops: security monitoring, plugin updates, WooCommerce maintenance, performance optimization, backup management, and troubleshooting. Keeps a complex multi-plugin installation stable and secure.

Next Step

Want this kind of clarity on your own stack?

If your site, store, or business system is carrying silent risk, we can map the problem, choose the right approach, and turn it into something steadier.