No. Kayak provides the theme via License to the client and handles the technical implementation.

Co-delivery projects are quoted and billed direct to the client. Referral partners earn a 10 percent commission. See Legal.

No. You handle strategy and client communication. We handle implementation and delivery.

HubSpot CMS (PRO/ENT Subscriptions for CMS Content Hub and Marketing Hub) using a structured system designed for consistency and scalability.

We begin with a conversation about your client, scope, and preferred involvement.

No. This supports your services by adding website delivery without replacing your role.

Yes. Co-delivery is designed for active partner involvement. Referral is not.

Partners refer or support clients using DropZone Pro. Kayak handles installation, configuration, warranty, and maintenance. Partners may support clients in building pages and managing content.

Kayak is responsible for the product, including setup, performance, and ongoing operation. Partners do not modify or maintain the theme.

Yes. Partners may use AI-assisted tools. They are responsible for any content they produce, including AI-assisted materials.

No. Independently produced materials, including AI-assisted content, cannot be represented as official Kayak documentation, standards, or product capabilities.

DropZone Pro is a structured way to build and manage HubSpot websites that helps partners deliver more consistently without rebuilding their approach for every project.

Work is done within defined page patterns instead of designing each page from scratch. This reduces layout decisions and shortens revision cycles.

For partners, this typically shows up as:

• more consistent margins across projects
• less time managing design and build variability
• reduced reliance on developers
• a clearer, repeatable service offering

It shifts website work from one-off execution to something that can scale.

Most themes and custom builds rely on teams to decide structure during the project.

DropZone Pro defines that upfront. Page types and layouts are selected based on intent (frameworks), not created each time.

For partners, this tends to:

• reduce back-and-forth on layout decisions
• shorten build cycles
• create more predictable delivery across projects

The difference shows up in how the work runs, not just how the site looks.

Brand templates are tailored page layouts created with the partner to align the system with the client’s brand and the partner’s approach.

They extend the core system by defining how key page types should be structured for that specific client. These templates still follow the system but reflect how the partner approaches messaging, conversion, and content flow.

For partners, this typically shows up as:

• layouts that support their strategy directly
• less need to adapt content to generic structures
• more consistent execution across pages
• stronger alignment between planning and build

Brand templates are where the partner’s approach is built into the system, not applied around it.

Brand templates allow partners to shape how pages are structured so the system aligns with their strategy and the client’s needs.

Instead of using only standard layouts, Kayak works with the partner to define tailored page patterns. These patterns still follow the system, but reflect how the partner approaches messaging, conversion, and content flow.

For partners, this typically shows up as:

• greater control over how strategy is implemented in the build
• layouts that support their frameworks and positioning
• less need to work around predefined structures
• more consistent execution across client pages

This keeps the system intact while allowing the partner’s approach to carry through the site.

Without tailored templates, partners often adapt their strategy to fit available layouts.

With brand templates, layouts are shaped to support the partner’s strategy from the start.

This tends to:

• reduce friction between strategy and execution
• improve alignment between content and layout
• make it easier to deliver consistent results across pages

For partners, it strengthens their role as the strategic lead rather than working around the system.

Brand templates are defined early and then reused across the site.

This means:

• fewer layout changes during the build
• clearer direction for content creation
• more consistent execution across pages

For partners, this reduces back-and-forth and keeps the project aligned with their strategy.

Brand templates guide how flexibility is applied.

They allow variation within a defined structure, so pages can adapt without becoming inconsistent.

For partners, this:

• reduces one-off layout requests
• maintains clarity across pages
• supports long-term usability

Flexibility is still there, but it’s applied in a controlled way that supports outcomes.

DropZone Pro works best when the site will continue to grow and be managed by more than one person.

This usually includes:

• teams using HubSpot as a core platform
• ongoing content creation
• a need for consistency across many pages

For partners, these projects tend to benefit most from a structured approach.

Some projects prioritize full control over each page.

This is more common with:

• highly design-led work
• small, static sites
• limited internal ownership after launch

In those cases, an approach with fewer structural controls may fit better.

Low-cost migrations move content. They usually keep the same structure.

That often means the same issues continue after launch.

DropZone Pro rebuilds how pages are structured. Content is organized into consistent page types.

For partners, this helps:

• shift the conversation away from price
• reduce post-launch clean-up work
• position the project as a long-term solution

Low-cost builds often depend on who is doing the work. Results can vary.

DropZone Pro applies the same system across every page.

For partners, this tends to:

• reduce variability between projects
• limit revision cycles tied to structure
• support more predictable delivery

The benefit is less about cost and more about control.

DropZone Pro reduces time spent on layout and structural decisions.

That time shifts toward strategy, messaging, and optimization.

Partners typically see:

• fewer revisions
• clearer scopes
• more consistent margins

It helps maintain profitability without increasing project volume.

DropZone Pro allows partners to position website work as a system rather than a one-time build.

This supports conversations around:

• long-term usability
• consistency across the site
• ongoing growth

It helps move away from design comparisons and price pressure.

Partners retain control of strategy, messaging, and the client relationship.

Kayak manages layout structure and system implementation.

For partners, this:

• keeps them in the lead role
• reduces involvement in technical execution
• maintains consistency across builds

Control shifts toward direction rather than build detail.

Referral partners identify fit and introduce the opportunity.

They can stay involved or step back depending on preference.

This allows partners to:

• participate without taking on delivery risk
• generate revenue without adding workload

Co-delivery partners lead positioning, guide content, and manage the client.

They are not responsible for layout configuration or build execution.

This allows partners to:

• stay focused on strategy
• reduce time spent on production work
• maintain client ownership

Page types and layouts are defined before the build starts.

This removes many layout decisions during the project.

For partners, this tends to:

• reduce revision cycles
• shorten delivery timelines
• create more consistent outcomes

Pricing reflects building a structured foundation, not just launching a site.

Partners are encouraged to position this as:

• avoiding repeated redesign costs
• reducing future rework
• supporting long-term use

This helps move the conversation away from lowest price.

Clients often come in with:

• inconsistent pages
• difficulty managing content
• repeated redesign cycles
• underused HubSpot portals

DropZone Pro addresses how the site is built and managed, not just how it looks.

Content is reviewed and mapped to defined page types.

It is not copied directly. Some restructuring is required.

For partners, this:

• improves clarity
• reduces legacy issues
• sets a cleaner foundation going forward

Clients work within consistent page patterns.

This reduces decision-making when creating new pages.

For partners, this tends to:

• reduce support requests
• make training more effective
• keep the site consistent over time

Client enablement depends on the project scope and should be defined during delivery.

In most cases, partners and clients need clarity on:

• who can create new pages
• how page patterns should be used
• what should stay within the system
• when to involve Kayak or the partner

For partners, this reduces confusion after launch and helps protect the system from drifting over time.

Customization is applied within defined patterns.

This keeps pages aligned across the site while still allowing variation where it matters.

For partners, this:

• reduces one-off requests
• maintains consistency
• protects long-term usability

DropZone Pro applies structure to how pages are built.

This means:

• less reliance on one-off layout changes
• more upfront alignment
• more consistency over time

For partners, the tradeoff is less variation in exchange for more predictable delivery.

The site is designed to evolve rather than be replaced.

Clients can continue building within the system.

For partners, this often leads to:

• longer engagements
• ongoing strategy work
• fewer full rebuild cycles

Content is structured consistently across pages.

Answers are placed in predictable locations.

For partners, this supports:

• clearer content
• better reuse by search and AI systems
• stronger long-term visibility

Common risks include:

• inconsistent page structures
• extended revision cycles
• unclear delivery boundaries

The system reduces these by defining how pages are built upfront.

Custom builds allow full control over structure.

DropZone Pro uses defined patterns to maintain consistency.

For partners, this tends to:

• reduce delivery variability
• simplify future updates
• support repeatable execution

DropZone Pro creates a more repeatable delivery model.

Partners often see:

• more consistent project outcomes
• clearer service positioning
• more opportunities for ongoing work

It supports scaling without increasing complexity.

Recommend DropZone Pro when:

• the site will grow
• multiple contributors are involved
• consistency matters
• HubSpot is central

Consider alternatives when:

• the project is static
• design variation is the priority
• long-term management is not a concern

The decision is based on how the partner wants to deliver work and how the client will use the site over time.

Pro-level marketplace themes and DropZone Pro both support modern page building in HubSpot.

Teams can:

• use modules to build pages
• arrange sections visually
• create a wide range of page layouts
• manage content without code

The difference is not what can be built.

It is how the site is governed and how it performs as it grows.

Marketplace themes rely on the team to decide how pages are structured and maintained over time. That responsibility sits with whoever is building and updating the site.

DropZone Pro defines how pages are structured and how they evolve.

For partners, this typically shows up as:

• clearer rules around how pages are built and extended
• more consistent outputs across teams and contributors
• less need to correct or realign pages later
• a delivery model that holds together as the site grows

There is also a difference in how the site supports search and AI systems.

DropZone Pro is built so content follows consistent patterns across pages and includes structured data as part of the system. This makes it easier for content to be understood, reused, and surfaced over time.

Finally, there is a difference in how work is delivered.

Marketplace themes are typically implemented and managed by the partner or client (DIY).

DropZone Pro supports a co-delivery model. Brand templates are defined collaboratively, so the partner’s approach may be built into the site from the start.

The distinction is not capability.

It is how the site is controlled, how it scales, and how much of that responsibility the partner chooses to manage directly.