{"limit":9,"message":null,"objects":[{"ab":false,"abStatus":null,"abTestId":null,"abVariation":false,"abVariationAutomated":false,"absoluteUrl":"https://deckerdevs.com/blogs/hubspot-api-integrations-faqs-sunsetting-api-keys-for-private-apps","afterPostBody":null,"aifeatures":null,"allowedSlugConflict":false,"analytics":null,"analyticsPageId":"83672227709","analyticsPageType":"blog-post","approvalStatus":null,"archived":false,"archivedAt":0,"archivedInDashboard":false,"areCommentsAllowed":true,"attachedStylesheets":[],"audienceAccess":"PUBLIC","author":null,"authorName":null,"authorUsername":null,"blogAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogAuthorId":62235724408,"blogPostAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogPostScheduleTaskUid":null,"blogPublishInstantEmailCampaignId":null,"blogPublishInstantEmailRetryCount":null,"blogPublishInstantEmailTaskUid":null,"blogPublishToSocialMediaTask":"DONE_NOT_SENT","blueprintTypeId":0,"businessUnitId":null,"campaign":null,"campaignName":null,"campaignUtm":null,"category":3,"categoryId":3,"cdnPurgeEmbargoTime":null,"checkPostLevelAudienceAccessFirst":true,"clonedFrom":null,"composeBody":null,"compositionId":0,"contentAccessRuleIds":[],"contentAccessRuleTypes":[],"contentGroup":62179259185,"contentGroupId":62179259185,"contentTypeCategory":3,"contentTypeCategoryId":3,"contentTypeId":null,"created":1662040036226,"createdByAgent":null,"createdById":27630257,"createdTime":1662040036226,"crmObjectId":null,"css":{},"cssText":"","ctaClicks":null,"ctaViews":null,"currentState":"PUBLISHED","currentlyPublished":true,"deletedAt":0,"deletedBy":null,"deletedByEmail":null,"deletedById":null,"domain":"","dynamicPageDataSourceId":null,"dynamicPageDataSourceType":null,"dynamicPageHubDbTableId":null,"enableDomainStylesheets":null,"enableGoogleAmpOutputOverride":false,"enableLayoutStylesheets":null,"errors":[],"featuredImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/complicated.jpeg","featuredImageAltText":"complicated api key hubspot","featuredImageHeight":433,"featuredImageLength":0,"featuredImageWidth":577,"flexAreas":{},"folderId":null,"footerHtml":null,"freezeDate":1662046743000,"generateJsonLdEnabledOverride":true,"hasContentAccessRules":false,"hasUserChanges":true,"headHtml":null,"header":null,"htmlTitle":"HubSpot API Integrations: FAQs Sunsetting API Keys for Private Apps","id":83672227709,"includeDefaultCustomCss":null,"isCaptchaRequired":true,"isCrawlableByBots":false,"isDraft":false,"isInstanceLayoutPage":false,"isInstantEmailEnabled":false,"isPublished":true,"isSocialPublishingEnabled":false,"keywords":[],"label":"HubSpot API Integrations: FAQs Sunsetting API Keys for Private Apps","language":"en","lastEditSessionId":null,"lastEditUpdateId":null,"layoutSections":{},"legacyBlogTabid":null,"legacyId":null,"legacyPostGuid":null,"linkRelCanonicalUrl":null,"listTemplate":"","liveDomain":"deckerdevs.com","mab":false,"mabExperimentId":null,"mabMaster":false,"mabVariant":false,"meta":{"html_title":"HubSpot API Integrations: FAQs Sunsetting API Keys for Private Apps","public_access_rules":[],"public_access_rules_enabled":false,"enable_google_amp_output_override":false,"generate_json_ld_enabled":true,"composition_id":0,"is_crawlable_by_bots":false,"use_featured_image":true,"post_body":"

API (Application Programming Interface) keys are codes that are used to identify and authenticate an application or user. HubSpot currently uses API keys as one of three authentication methods when it comes to application integrations. However, HubSpot published a blog in June stating they would be eliminating API keys in favor of Private Apps. API keys will no longer be recognized as of November 30, 2022. The last day to request an extension after this date will be October 1, 2022 - and this is all important for anyone dealing with custom integrations or web application that use API keys for authentication.

\n\n

\n

How will this affect me?

\n

API keys are the most common way that developers have authenticated private integrations with HubSpot in the past. If you have a private or custom built integration with HubSpot or outside systems that feed data into HubSpot, it was more than likely authenticated with API keys and you probably need to have it reconfigured. Sunsetting HubSpot API keys is going to impact a lot of HubSpot customers, so you’ll want to reach out to your development partner soon to get switched over to private app authentication.

\n

What happens if I don't make the transition in time?

\n

Simply put - your application will stop integrating. Once the API keys expire they’ll no longer authenticate and data will no longer pass through to HubSpot or your third party application. This could impact a number of different departments and employees depending on how your business uses this data and cause workflow issues through the organization.

\n

How long will this take?

\n

In the majority of API integration situations, moving over to Private Apps from API keys shouldn’t take more than a few hours. We did have one situation take as long as 9 hours with a client with legacy integrations handled by multiple different developers and outsourced offshore teams, but most of that was chasing down information.

\n

What if I no longer work with my developer?

\n

If you no longer work with your developer, you can still easily make the transition, it’s just a matter of finding a HubSpot CMS developer to work with and understanding that it may take extra time to find what is needed to make the changes.

\n

Here are a few scenarios we’ve experienced making our own changes and helping clients make the switch:

\n

 

\n

deckerdevs conversion: < 1 hour

\n

For deckerdevs, because we are very familiar with and completed our own integrations, conversion will only take us about 30 minutes, 45 if we get distracted. The more you know about your integrations including where they are located and whether or not you have access, the less time the conversion will take.

\n

Scenario A - A few custom coded workflows: 2 hours

\n

One of our clients has a few custom coded workflows. Each workflow connects different aspects of their hubspot integration with deals and contacts to an outside system. Because everything was inside HubSpot to run this integration, we were able to quickly wrap these up in 2 hours.

\n

Scenario B - PHP Web Application: 2.5 hours

\n

Another of our clients has a PHP web application that reaches out to HubSpot and pushes/pulls different products from their tool and integrates into the blog as well as sales process. They have another cloud server to help push data to their ERP. We were able to provide a simple email to their development team to get this migrated. We emailed back and forth a couple times with the development team and got both of their authentication points updated in a total of 2.5 hours.

\n

Scenario C - Legacy Integrations by Multiple Developers, Access Issues: 8.5 hours

\n

A more complicated situation we encountered with a client included a legacy integration that was led by people no longer employed at the organization and was completed by an offshore outsourced team. The majority of our time was spent doing research on items and guiding the client on what they should be searching for in their email and invoices. Once we finally drilled down and found out who we needed to talk to, it took a couple hours trying to locate the account so we could gain access to where the integration takes place. We chased after a few rabbits on this one and spent about 8.5 hours working through these issues.

\n

What's the bottom line?

\n

It’s hard to say how long your conversion to Private Apps will take, but if your company’s approach to technology is anything like Scenario C and has a complicated or mismanaged tech stack, we encourage you to reach out to a HubSpot API Integration specialist as soon as possible.

\n

Don't have anyone to help you with your conversion? We're happy to help.

\n

\n

 

","rss_summary":"

API (Application Programming Interface) keys are codes that are used to identify and authenticate an application or user. HubSpot currently uses API keys as one of three authentication methods when it comes to application integrations. However, HubSpot published a blog in June stating they would be eliminating API keys in favor of Private Apps. API keys will no longer be recognized as of November 30, 2022. The last day to request an extension after this date will be October 1, 2022 - and this is all important for anyone dealing with custom integrations or web application that use API keys for authentication.

\n","rss_body":"

API (Application Programming Interface) keys are codes that are used to identify and authenticate an application or user. HubSpot currently uses API keys as one of three authentication methods when it comes to application integrations. However, HubSpot published a blog in June stating they would be eliminating API keys in favor of Private Apps. API keys will no longer be recognized as of November 30, 2022. The last day to request an extension after this date will be October 1, 2022 - and this is all important for anyone dealing with custom integrations or web application that use API keys for authentication.

\n\n

\n

How will this affect me?

\n

API keys are the most common way that developers have authenticated private integrations with HubSpot in the past. If you have a private or custom built integration with HubSpot or outside systems that feed data into HubSpot, it was more than likely authenticated with API keys and you probably need to have it reconfigured. Sunsetting HubSpot API keys is going to impact a lot of HubSpot customers, so you’ll want to reach out to your development partner soon to get switched over to private app authentication.

\n

What happens if I don't make the transition in time?

\n

Simply put - your application will stop integrating. Once the API keys expire they’ll no longer authenticate and data will no longer pass through to HubSpot or your third party application. This could impact a number of different departments and employees depending on how your business uses this data and cause workflow issues through the organization.

\n

How long will this take?

\n

In the majority of API integration situations, moving over to Private Apps from API keys shouldn’t take more than a few hours. We did have one situation take as long as 9 hours with a client with legacy integrations handled by multiple different developers and outsourced offshore teams, but most of that was chasing down information.

\n

What if I no longer work with my developer?

\n

If you no longer work with your developer, you can still easily make the transition, it’s just a matter of finding a HubSpot CMS developer to work with and understanding that it may take extra time to find what is needed to make the changes.

\n

Here are a few scenarios we’ve experienced making our own changes and helping clients make the switch:

\n

 

\n

deckerdevs conversion: < 1 hour

\n

For deckerdevs, because we are very familiar with and completed our own integrations, conversion will only take us about 30 minutes, 45 if we get distracted. The more you know about your integrations including where they are located and whether or not you have access, the less time the conversion will take.

\n

Scenario A - A few custom coded workflows: 2 hours

\n

One of our clients has a few custom coded workflows. Each workflow connects different aspects of their hubspot integration with deals and contacts to an outside system. Because everything was inside HubSpot to run this integration, we were able to quickly wrap these up in 2 hours.

\n

Scenario B - PHP Web Application: 2.5 hours

\n

Another of our clients has a PHP web application that reaches out to HubSpot and pushes/pulls different products from their tool and integrates into the blog as well as sales process. They have another cloud server to help push data to their ERP. We were able to provide a simple email to their development team to get this migrated. We emailed back and forth a couple times with the development team and got both of their authentication points updated in a total of 2.5 hours.

\n

Scenario C - Legacy Integrations by Multiple Developers, Access Issues: 8.5 hours

\n

A more complicated situation we encountered with a client included a legacy integration that was led by people no longer employed at the organization and was completed by an offshore outsourced team. The majority of our time was spent doing research on items and guiding the client on what they should be searching for in their email and invoices. Once we finally drilled down and found out who we needed to talk to, it took a couple hours trying to locate the account so we could gain access to where the integration takes place. We chased after a few rabbits on this one and spent about 8.5 hours working through these issues.

\n

What's the bottom line?

\n

It’s hard to say how long your conversion to Private Apps will take, but if your company’s approach to technology is anything like Scenario C and has a complicated or mismanaged tech stack, we encourage you to reach out to a HubSpot API Integration specialist as soon as possible.

\n

Don't have anyone to help you with your conversion? We're happy to help.

\n

\n

 

","tag_ids":[62770442823,77142401624],"topic_ids":[62770442823,77142401624],"post_summary":"

API (Application Programming Interface) keys are codes that are used to identify and authenticate an application or user. HubSpot currently uses API keys as one of three authentication methods when it comes to application integrations. However, HubSpot published a blog in June stating they would be eliminating API keys in favor of Private Apps. API keys will no longer be recognized as of November 30, 2022. The last day to request an extension after this date will be October 1, 2022 - and this is all important for anyone dealing with custom integrations or web application that use API keys for authentication.

\n","blog_post_schedule_task_uid":null,"blog_publish_to_social_media_task":"DONE_NOT_SENT","blog_publish_instant_email_task_uid":null,"blog_publish_instant_email_campaign_id":null,"blog_publish_instant_email_retry_count":null,"keywords":[],"head_html":null,"footer_html":null,"attached_stylesheets":[],"enable_domain_stylesheets":null,"include_default_custom_css":null,"meta_description":"HubSpot is sunsetting API keys effective November 30, 2022 and switching to Private Apps, here's what you need to know. ","meta_keywords":null,"layout_sections":{},"past_mab_experiment_ids":[],"deleted_by":null,"featured_image_alt_text":"complicated api key hubspot","enable_layout_stylesheets":null,"tweet":null,"tweet_at":null,"campaign_name":null,"campaign_utm":null,"tweet_immediately":false,"publish_immediately":true,"security_state":"NONE","scheduled_update_date":0,"placement_guids":[],"property_for_dynamic_page_title":null,"property_for_dynamic_page_slug":null,"property_for_dynamic_page_meta_description":null,"property_for_dynamic_page_featured_image":null,"property_for_dynamic_page_canonical_url":null,"preview_image_src":null,"legacy_blog_tabid":null,"legacy_post_guid":null,"performable_variation_letter":null,"style_override_id":null,"has_user_changes":true,"css":{},"css_text":"","unpublished_at":0,"published_by_id":27630257,"allowed_slug_conflict":false,"ai_features":null,"link_rel_canonical_url":null,"page_redirected":false,"page_expiry_enabled":null,"page_expiry_date":null,"page_expiry_redirect_id":null,"page_expiry_redirect_url":null,"deleted_by_id":null,"state_when_deleted":null,"cloned_from":null,"staged_from":null,"personas":[],"compose_body":null,"featured_image":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/complicated.jpeg","featured_image_width":577,"featured_image_height":433,"publish_timezone_offset":null,"theme_settings_values":null,"password":null,"header":null,"published_at":1692280396828,"last_edit_session_id":null,"last_edit_update_id":null,"created_by_agent":null},"metaDescription":"HubSpot is sunsetting API keys effective November 30, 2022 and switching to Private Apps, here's what you need to know. ","metaKeywords":null,"name":"HubSpot API Integrations: FAQs Sunsetting API Keys for Private Apps","nextPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/job-interview-memes-1-5d14a7ea1163a__700.jpeg","nextPostFeaturedImageAltText":"hubspot interview","nextPostName":"6 Questions to Ask Your HubSpot CMS Developer: Part 3","nextPostSlug":"blogs/6-questions-to-ask-your-hubspot-cms-developer-part-3","pageExpiryDate":null,"pageExpiryEnabled":null,"pageExpiryRedirectId":null,"pageExpiryRedirectUrl":null,"pageRedirected":false,"pageTitle":"HubSpot API Integrations: FAQs Sunsetting API Keys for Private Apps","parentBlog":{"absoluteUrl":"https://deckerdevs.com/blogs","allowComments":true,"ampBodyColor":"#404040","ampBodyFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampBodyFontSize":"18","ampCustomCss":"","ampHeaderBackgroundColor":"#ffffff","ampHeaderColor":"#1e1e1e","ampHeaderFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampHeaderFontSize":"36","ampLinkColor":"#416bb3","ampLogoAlt":"","ampLogoHeight":0,"ampLogoSrc":"","ampLogoWidth":0,"analyticsPageId":62179259185,"attachedStylesheets":[],"audienceAccess":"PUBLIC","businessUnitId":null,"captchaAfterDays":7,"captchaAlways":false,"categoryId":3,"cdnPurgeEmbargoTime":null,"closeCommentsOlder":0,"commentDateFormat":"medium","commentFormGuid":"cb653aa1-3db4-4167-9b59-744c46d49682","commentMaxThreadDepth":3,"commentModeration":false,"commentNotificationEmails":["nicholas@deckerdevs.com","jessica@deckerdevs.com"],"commentShouldCreateContact":true,"commentVerificationText":"Thanks for participating in this conversation! We look forward to responding and to assisting where we can","cosObjectType":"BLOG","created":1639786189589,"createdDateTime":1639786189589,"dailyNotificationEmailId":null,"dateFormattingLanguage":null,"defaultGroupStyleId":"","defaultNotificationFromName":"","defaultNotificationReplyTo":"","deletedAt":0,"description":"rev up your hubspot system to the max! deckerdevs' turbo-charged blog is your ultimate guide to harnessing the full potential of hubspot development. unleash the marketing magic with ingenious tips, tricks, and hacks. get ready to level up your hubspot game!","domain":"","domainWhenPublished":"deckerdevs.com","emailApiSubscriptionId":null,"enableGoogleAmpOutput":false,"enableSocialAutoPublishing":false,"generateJsonLdEnabled":true,"header":null,"htmlFooter":"","htmlFooterIsShared":true,"htmlHead":"","htmlHeadIsShared":true,"htmlKeywords":[],"htmlTitle":"deckerdevs thought nuggets","id":62179259185,"ilsSubscriptionListsByType":{},"instantNotificationEmailId":null,"itemLayoutId":null,"itemTemplateIsShared":false,"itemTemplatePath":"deckerdevs-theme/templates/blog-content.html","label":"deckerdevs live blog","language":"en","legacyGuid":null,"legacyModuleId":null,"legacyTabId":null,"listingLayoutId":null,"listingPageId":62179259186,"listingTemplatePath":"","liveDomain":"deckerdevs.com","monthFilterFormat":"MMMM yyyy","monthlyNotificationEmailId":null,"name":"deckerdevs live blog","parentBlogUpdateTaskId":null,"portalId":6534445,"postHtmlFooter":"","postHtmlHead":"","postsPerListingPage":9,"postsPerRssFeed":10,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publicTitle":"thought nuggets","publishDateFormat":"medium","resolvedDomain":"deckerdevs.com","rootUrl":"https://deckerdevs.com/blogs","rssCustomFeed":null,"rssDescription":null,"rssItemFooter":null,"rssItemHeader":null,"settingsOverrides":{"itemLayoutId":false,"itemTemplatePath":false,"itemTemplateIsShared":false,"listingLayoutId":false,"listingTemplatePath":false,"postsPerListingPage":false,"showSummaryInListing":false,"useFeaturedImageInSummary":false,"htmlHead":false,"postHtmlHead":false,"htmlHeadIsShared":false,"htmlFooter":false,"listingPageHtmlFooter":false,"postHtmlFooter":false,"htmlFooterIsShared":false,"attachedStylesheets":false,"postsPerRssFeed":false,"showSummaryInRss":false,"showSummaryInEmails":false,"showSummariesInEmails":false,"allowComments":false,"commentShouldCreateContact":false,"commentModeration":false,"closeCommentsOlder":false,"commentNotificationEmails":false,"commentMaxThreadDepth":false,"commentVerificationText":false,"socialAccountTwitter":false,"showSocialLinkTwitter":false,"showSocialLinkLinkedin":false,"showSocialLinkFacebook":false,"enableGoogleAmpOutput":false,"ampLogoSrc":false,"ampLogoHeight":false,"ampLogoWidth":false,"ampLogoAlt":false,"ampHeaderFont":false,"ampHeaderFontSize":false,"ampHeaderColor":false,"ampHeaderBackgroundColor":false,"ampBodyFont":false,"ampBodyFontSize":false,"ampBodyColor":false,"ampLinkColor":false,"generateJsonLdEnabled":false},"showSocialLinkFacebook":true,"showSocialLinkLinkedin":true,"showSocialLinkTwitter":true,"showSummaryInEmails":true,"showSummaryInListing":true,"showSummaryInRss":true,"siteId":null,"slug":"blogs","socialAccountTwitter":"","state":null,"subscriptionContactsProperty":null,"subscriptionEmailType":null,"subscriptionFormGuid":null,"subscriptionListsByType":{},"title":null,"translatedFromId":null,"translations":{},"updated":1712344124471,"updatedDateTime":1712344124471,"urlBase":"deckerdevs.com/blogs","urlSegments":{"all":"all","archive":"archive","author":"author","page":"page","tag":"tag"},"useFeaturedImageInSummary":true,"usesDefaultTemplate":false,"weeklyNotificationEmailId":null},"password":null,"pastMabExperimentIds":[],"performableGuid":null,"performableVariationLetter":null,"personas":[],"placementGuids":[],"portableKey":null,"portalId":6534445,"position":null,"postBody":"

API (Application Programming Interface) keys are codes that are used to identify and authenticate an application or user. HubSpot currently uses API keys as one of three authentication methods when it comes to application integrations. However, HubSpot published a blog in June stating they would be eliminating API keys in favor of Private Apps. API keys will no longer be recognized as of November 30, 2022. The last day to request an extension after this date will be October 1, 2022 - and this is all important for anyone dealing with custom integrations or web application that use API keys for authentication.

\n\n

\n

How will this affect me?

\n

API keys are the most common way that developers have authenticated private integrations with HubSpot in the past. If you have a private or custom built integration with HubSpot or outside systems that feed data into HubSpot, it was more than likely authenticated with API keys and you probably need to have it reconfigured. Sunsetting HubSpot API keys is going to impact a lot of HubSpot customers, so you’ll want to reach out to your development partner soon to get switched over to private app authentication.

\n

What happens if I don't make the transition in time?

\n

Simply put - your application will stop integrating. Once the API keys expire they’ll no longer authenticate and data will no longer pass through to HubSpot or your third party application. This could impact a number of different departments and employees depending on how your business uses this data and cause workflow issues through the organization.

\n

How long will this take?

\n

In the majority of API integration situations, moving over to Private Apps from API keys shouldn’t take more than a few hours. We did have one situation take as long as 9 hours with a client with legacy integrations handled by multiple different developers and outsourced offshore teams, but most of that was chasing down information.

\n

What if I no longer work with my developer?

\n

If you no longer work with your developer, you can still easily make the transition, it’s just a matter of finding a HubSpot CMS developer to work with and understanding that it may take extra time to find what is needed to make the changes.

\n

Here are a few scenarios we’ve experienced making our own changes and helping clients make the switch:

\n

 

\n

deckerdevs conversion: < 1 hour

\n

For deckerdevs, because we are very familiar with and completed our own integrations, conversion will only take us about 30 minutes, 45 if we get distracted. The more you know about your integrations including where they are located and whether or not you have access, the less time the conversion will take.

\n

Scenario A - A few custom coded workflows: 2 hours

\n

One of our clients has a few custom coded workflows. Each workflow connects different aspects of their hubspot integration with deals and contacts to an outside system. Because everything was inside HubSpot to run this integration, we were able to quickly wrap these up in 2 hours.

\n

Scenario B - PHP Web Application: 2.5 hours

\n

Another of our clients has a PHP web application that reaches out to HubSpot and pushes/pulls different products from their tool and integrates into the blog as well as sales process. They have another cloud server to help push data to their ERP. We were able to provide a simple email to their development team to get this migrated. We emailed back and forth a couple times with the development team and got both of their authentication points updated in a total of 2.5 hours.

\n

Scenario C - Legacy Integrations by Multiple Developers, Access Issues: 8.5 hours

\n

A more complicated situation we encountered with a client included a legacy integration that was led by people no longer employed at the organization and was completed by an offshore outsourced team. The majority of our time was spent doing research on items and guiding the client on what they should be searching for in their email and invoices. Once we finally drilled down and found out who we needed to talk to, it took a couple hours trying to locate the account so we could gain access to where the integration takes place. We chased after a few rabbits on this one and spent about 8.5 hours working through these issues.

\n

What's the bottom line?

\n

It’s hard to say how long your conversion to Private Apps will take, but if your company’s approach to technology is anything like Scenario C and has a complicated or mismanaged tech stack, we encourage you to reach out to a HubSpot API Integration specialist as soon as possible.

\n

Don't have anyone to help you with your conversion? We're happy to help.

\n

\n

 

","postBodyRss":"

API (Application Programming Interface) keys are codes that are used to identify and authenticate an application or user. HubSpot currently uses API keys as one of three authentication methods when it comes to application integrations. However, HubSpot published a blog in June stating they would be eliminating API keys in favor of Private Apps. API keys will no longer be recognized as of November 30, 2022. The last day to request an extension after this date will be October 1, 2022 - and this is all important for anyone dealing with custom integrations or web application that use API keys for authentication.

\n\n

\n

How will this affect me?

\n

API keys are the most common way that developers have authenticated private integrations with HubSpot in the past. If you have a private or custom built integration with HubSpot or outside systems that feed data into HubSpot, it was more than likely authenticated with API keys and you probably need to have it reconfigured. Sunsetting HubSpot API keys is going to impact a lot of HubSpot customers, so you’ll want to reach out to your development partner soon to get switched over to private app authentication.

\n

What happens if I don't make the transition in time?

\n

Simply put - your application will stop integrating. Once the API keys expire they’ll no longer authenticate and data will no longer pass through to HubSpot or your third party application. This could impact a number of different departments and employees depending on how your business uses this data and cause workflow issues through the organization.

\n

How long will this take?

\n

In the majority of API integration situations, moving over to Private Apps from API keys shouldn’t take more than a few hours. We did have one situation take as long as 9 hours with a client with legacy integrations handled by multiple different developers and outsourced offshore teams, but most of that was chasing down information.

\n

What if I no longer work with my developer?

\n

If you no longer work with your developer, you can still easily make the transition, it’s just a matter of finding a HubSpot CMS developer to work with and understanding that it may take extra time to find what is needed to make the changes.

\n

Here are a few scenarios we’ve experienced making our own changes and helping clients make the switch:

\n

 

\n

deckerdevs conversion: < 1 hour

\n

For deckerdevs, because we are very familiar with and completed our own integrations, conversion will only take us about 30 minutes, 45 if we get distracted. The more you know about your integrations including where they are located and whether or not you have access, the less time the conversion will take.

\n

Scenario A - A few custom coded workflows: 2 hours

\n

One of our clients has a few custom coded workflows. Each workflow connects different aspects of their hubspot integration with deals and contacts to an outside system. Because everything was inside HubSpot to run this integration, we were able to quickly wrap these up in 2 hours.

\n

Scenario B - PHP Web Application: 2.5 hours

\n

Another of our clients has a PHP web application that reaches out to HubSpot and pushes/pulls different products from their tool and integrates into the blog as well as sales process. They have another cloud server to help push data to their ERP. We were able to provide a simple email to their development team to get this migrated. We emailed back and forth a couple times with the development team and got both of their authentication points updated in a total of 2.5 hours.

\n

Scenario C - Legacy Integrations by Multiple Developers, Access Issues: 8.5 hours

\n

A more complicated situation we encountered with a client included a legacy integration that was led by people no longer employed at the organization and was completed by an offshore outsourced team. The majority of our time was spent doing research on items and guiding the client on what they should be searching for in their email and invoices. Once we finally drilled down and found out who we needed to talk to, it took a couple hours trying to locate the account so we could gain access to where the integration takes place. We chased after a few rabbits on this one and spent about 8.5 hours working through these issues.

\n

What's the bottom line?

\n

It’s hard to say how long your conversion to Private Apps will take, but if your company’s approach to technology is anything like Scenario C and has a complicated or mismanaged tech stack, we encourage you to reach out to a HubSpot API Integration specialist as soon as possible.

\n

Don't have anyone to help you with your conversion? We're happy to help.

\n

\n

 

","postEmailContent":"

API (Application Programming Interface) keys are codes that are used to identify and authenticate an application or user. HubSpot currently uses API keys as one of three authentication methods when it comes to application integrations. However, HubSpot published a blog in June stating they would be eliminating API keys in favor of Private Apps. API keys will no longer be recognized as of November 30, 2022. The last day to request an extension after this date will be October 1, 2022 - and this is all important for anyone dealing with custom integrations or web application that use API keys for authentication.

","postFeaturedImageIfEnabled":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/complicated.jpeg","postListContent":"

API (Application Programming Interface) keys are codes that are used to identify and authenticate an application or user. HubSpot currently uses API keys as one of three authentication methods when it comes to application integrations. However, HubSpot published a blog in June stating they would be eliminating API keys in favor of Private Apps. API keys will no longer be recognized as of November 30, 2022. The last day to request an extension after this date will be October 1, 2022 - and this is all important for anyone dealing with custom integrations or web application that use API keys for authentication.

","postListSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/complicated.jpeg","postRssContent":"

API (Application Programming Interface) keys are codes that are used to identify and authenticate an application or user. HubSpot currently uses API keys as one of three authentication methods when it comes to application integrations. However, HubSpot published a blog in June stating they would be eliminating API keys in favor of Private Apps. API keys will no longer be recognized as of November 30, 2022. The last day to request an extension after this date will be October 1, 2022 - and this is all important for anyone dealing with custom integrations or web application that use API keys for authentication.

","postRssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/complicated.jpeg","postSummary":"

API (Application Programming Interface) keys are codes that are used to identify and authenticate an application or user. HubSpot currently uses API keys as one of three authentication methods when it comes to application integrations. However, HubSpot published a blog in June stating they would be eliminating API keys in favor of Private Apps. API keys will no longer be recognized as of November 30, 2022. The last day to request an extension after this date will be October 1, 2022 - and this is all important for anyone dealing with custom integrations or web application that use API keys for authentication.

\n","postSummaryRss":"

API (Application Programming Interface) keys are codes that are used to identify and authenticate an application or user. HubSpot currently uses API keys as one of three authentication methods when it comes to application integrations. However, HubSpot published a blog in June stating they would be eliminating API keys in favor of Private Apps. API keys will no longer be recognized as of November 30, 2022. The last day to request an extension after this date will be October 1, 2022 - and this is all important for anyone dealing with custom integrations or web application that use API keys for authentication.

","postTemplate":"deckerdevs-theme/templates/blog-content.html","previewImageSrc":null,"previewKey":"vILVKDdM","previousPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/job-interview-memes-1-5d14a7ea1163a__700.jpeg","previousPostFeaturedImageAltText":"hubspot interview","previousPostName":"6 Questions to Ask Your HubSpot CMS Developer: Part 3","previousPostSlug":"blogs/6-questions-to-ask-your-hubspot-cms-developer-part-3","processingStatus":"PUBLISHED","propertyForDynamicPageCanonicalUrl":null,"propertyForDynamicPageFeaturedImage":null,"propertyForDynamicPageMetaDescription":null,"propertyForDynamicPageSlug":null,"propertyForDynamicPageTitle":null,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publishDate":1662046743000,"publishDateLocalTime":1662046743000,"publishDateLocalized":{"date":1662046743000,"format":"medium","language":null},"publishImmediately":true,"publishTimezoneOffset":null,"publishedAt":1692280396828,"publishedByEmail":null,"publishedById":27630257,"publishedByName":null,"publishedUrl":"https://deckerdevs.com/blogs/hubspot-api-integrations-faqs-sunsetting-api-keys-for-private-apps","resolvedDomain":"deckerdevs.com","resolvedLanguage":null,"rssBody":"

API (Application Programming Interface) keys are codes that are used to identify and authenticate an application or user. HubSpot currently uses API keys as one of three authentication methods when it comes to application integrations. However, HubSpot published a blog in June stating they would be eliminating API keys in favor of Private Apps. API keys will no longer be recognized as of November 30, 2022. The last day to request an extension after this date will be October 1, 2022 - and this is all important for anyone dealing with custom integrations or web application that use API keys for authentication.

\n\n

\n

How will this affect me?

\n

API keys are the most common way that developers have authenticated private integrations with HubSpot in the past. If you have a private or custom built integration with HubSpot or outside systems that feed data into HubSpot, it was more than likely authenticated with API keys and you probably need to have it reconfigured. Sunsetting HubSpot API keys is going to impact a lot of HubSpot customers, so you’ll want to reach out to your development partner soon to get switched over to private app authentication.

\n

What happens if I don't make the transition in time?

\n

Simply put - your application will stop integrating. Once the API keys expire they’ll no longer authenticate and data will no longer pass through to HubSpot or your third party application. This could impact a number of different departments and employees depending on how your business uses this data and cause workflow issues through the organization.

\n

How long will this take?

\n

In the majority of API integration situations, moving over to Private Apps from API keys shouldn’t take more than a few hours. We did have one situation take as long as 9 hours with a client with legacy integrations handled by multiple different developers and outsourced offshore teams, but most of that was chasing down information.

\n

What if I no longer work with my developer?

\n

If you no longer work with your developer, you can still easily make the transition, it’s just a matter of finding a HubSpot CMS developer to work with and understanding that it may take extra time to find what is needed to make the changes.

\n

Here are a few scenarios we’ve experienced making our own changes and helping clients make the switch:

\n

 

\n

deckerdevs conversion: < 1 hour

\n

For deckerdevs, because we are very familiar with and completed our own integrations, conversion will only take us about 30 minutes, 45 if we get distracted. The more you know about your integrations including where they are located and whether or not you have access, the less time the conversion will take.

\n

Scenario A - A few custom coded workflows: 2 hours

\n

One of our clients has a few custom coded workflows. Each workflow connects different aspects of their hubspot integration with deals and contacts to an outside system. Because everything was inside HubSpot to run this integration, we were able to quickly wrap these up in 2 hours.

\n

Scenario B - PHP Web Application: 2.5 hours

\n

Another of our clients has a PHP web application that reaches out to HubSpot and pushes/pulls different products from their tool and integrates into the blog as well as sales process. They have another cloud server to help push data to their ERP. We were able to provide a simple email to their development team to get this migrated. We emailed back and forth a couple times with the development team and got both of their authentication points updated in a total of 2.5 hours.

\n

Scenario C - Legacy Integrations by Multiple Developers, Access Issues: 8.5 hours

\n

A more complicated situation we encountered with a client included a legacy integration that was led by people no longer employed at the organization and was completed by an offshore outsourced team. The majority of our time was spent doing research on items and guiding the client on what they should be searching for in their email and invoices. Once we finally drilled down and found out who we needed to talk to, it took a couple hours trying to locate the account so we could gain access to where the integration takes place. We chased after a few rabbits on this one and spent about 8.5 hours working through these issues.

\n

What's the bottom line?

\n

It’s hard to say how long your conversion to Private Apps will take, but if your company’s approach to technology is anything like Scenario C and has a complicated or mismanaged tech stack, we encourage you to reach out to a HubSpot API Integration specialist as soon as possible.

\n

Don't have anyone to help you with your conversion? We're happy to help.

\n

\n

 

","rssSummary":"

API (Application Programming Interface) keys are codes that are used to identify and authenticate an application or user. HubSpot currently uses API keys as one of three authentication methods when it comes to application integrations. However, HubSpot published a blog in June stating they would be eliminating API keys in favor of Private Apps. API keys will no longer be recognized as of November 30, 2022. The last day to request an extension after this date will be October 1, 2022 - and this is all important for anyone dealing with custom integrations or web application that use API keys for authentication.

\n","rssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/complicated.jpeg","scheduledUpdateDate":0,"screenshotPreviewTakenAt":1735307596019,"screenshotPreviewUrl":"https://cdn1.hubspot.net/hubshotv3/prod/e/0/f03f1cd6-e8df-46a2-bdeb-758fa3638357.png","sections":{},"securityState":"NONE","siteId":null,"slug":"blogs/hubspot-api-integrations-faqs-sunsetting-api-keys-for-private-apps","stagedFrom":null,"state":"PUBLISHED","stateWhenDeleted":null,"structuredContentPageType":null,"structuredContentType":null,"styleOverrideId":null,"subcategory":"normal_blog_post","syncedWithBlogRoot":true,"tagIds":[62770442823,77142401624],"tagList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1655914616188,"deletedAt":0,"description":"","id":77142401624,"label":"API Integrations","language":"en","name":"API Integrations","portalId":6534445,"slug":"api-integrations","translatedFromId":null,"translations":{},"updated":1655914616188}],"tagNames":["HubSpot CMS Development","API Integrations"],"teamPerms":[],"templatePath":"","templatePathForRender":"deckerdevs-theme/templates/blog-content.html","textToAudioFileId":null,"textToAudioGenerationRequestId":null,"themePath":null,"themeSettingsValues":null,"title":"HubSpot API Integrations: FAQs Sunsetting API Keys for Private Apps","tmsId":null,"topicIds":[62770442823,77142401624],"topicList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1655914616188,"deletedAt":0,"description":"","id":77142401624,"label":"API Integrations","language":"en","name":"API Integrations","portalId":6534445,"slug":"api-integrations","translatedFromId":null,"translations":{},"updated":1655914616188}],"topicNames":["HubSpot CMS Development","API Integrations"],"topics":[62770442823,77142401624],"translatedContent":{},"translatedFromId":null,"translations":{},"tweet":null,"tweetAt":null,"tweetImmediately":false,"unpublishedAt":0,"updated":1692280396833,"updatedById":27630257,"upsizeFeaturedImage":false,"url":"https://deckerdevs.com/blogs/hubspot-api-integrations-faqs-sunsetting-api-keys-for-private-apps","useFeaturedImage":true,"userPerms":[],"views":null,"visibleToAll":null,"widgetContainers":{},"widgetcontainers":{},"widgets":{"blog-image":{"body":{"image_field":{"alt":"pattern-2","height":563,"loading":"lazy","max_height":563,"max_width":1000,"size_type":"auto","src":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/pattern-2.jpg","width":1000}},"child_css":{},"css":{},"deleted_at":1692280362416,"id":"blog-image","label":null,"module_id":62246908725,"name":"blog-image","order":3,"smart_type":null,"styles":{},"type":"module"}}},{"ab":false,"abStatus":null,"abTestId":null,"abVariation":false,"abVariationAutomated":false,"absoluteUrl":"https://deckerdevs.com/blogs/6-questions-to-ask-your-hubspot-cms-developer-part-3","afterPostBody":null,"aifeatures":null,"allowedSlugConflict":false,"analytics":null,"analyticsPageId":"82901816962","analyticsPageType":"blog-post","approvalStatus":null,"archived":false,"archivedAt":0,"archivedInDashboard":false,"areCommentsAllowed":true,"attachedStylesheets":[],"audienceAccess":"PUBLIC","author":null,"authorName":null,"authorUsername":null,"blogAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogAuthorId":62235724408,"blogPostAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogPostScheduleTaskUid":null,"blogPublishInstantEmailCampaignId":null,"blogPublishInstantEmailRetryCount":null,"blogPublishInstantEmailTaskUid":null,"blogPublishToSocialMediaTask":"DONE_NOT_SENT","blueprintTypeId":0,"businessUnitId":null,"campaign":null,"campaignName":null,"campaignUtm":null,"category":3,"categoryId":3,"cdnPurgeEmbargoTime":null,"checkPostLevelAudienceAccessFirst":true,"clonedFrom":null,"composeBody":null,"compositionId":0,"contentAccessRuleIds":[],"contentAccessRuleTypes":[],"contentGroup":62179259185,"contentGroupId":62179259185,"contentTypeCategory":3,"contentTypeCategoryId":3,"contentTypeId":null,"created":1661356779556,"createdByAgent":null,"createdById":27630257,"createdTime":1661356779556,"crmObjectId":null,"css":{},"cssText":"","ctaClicks":null,"ctaViews":null,"currentState":"PUBLISHED","currentlyPublished":true,"deletedAt":0,"deletedBy":null,"deletedByEmail":null,"deletedById":null,"domain":"","dynamicPageDataSourceId":null,"dynamicPageDataSourceType":null,"dynamicPageHubDbTableId":null,"enableDomainStylesheets":null,"enableGoogleAmpOutputOverride":false,"enableLayoutStylesheets":null,"errors":[],"featuredImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/job-interview-memes-1-5d14a7ea1163a__700.jpeg","featuredImageAltText":"hubspot interview","featuredImageHeight":963,"featuredImageLength":0,"featuredImageWidth":700,"flexAreas":{},"folderId":null,"footerHtml":null,"freezeDate":1661358300000,"generateJsonLdEnabledOverride":true,"hasContentAccessRules":false,"hasUserChanges":true,"headHtml":null,"header":null,"htmlTitle":"6 Questions to Ask Your HubSpot CMS Developer: Part 3","id":82901816962,"includeDefaultCustomCss":null,"isCaptchaRequired":true,"isCrawlableByBots":false,"isDraft":false,"isInstanceLayoutPage":false,"isInstantEmailEnabled":false,"isPublished":true,"isSocialPublishingEnabled":false,"keywords":[],"label":"6 Questions to Ask Your HubSpot CMS Developer: Part 3","language":"en","lastEditSessionId":null,"lastEditUpdateId":null,"layoutSections":{},"legacyBlogTabid":null,"legacyId":null,"legacyPostGuid":null,"linkRelCanonicalUrl":null,"listTemplate":"","liveDomain":"deckerdevs.com","mab":false,"mabExperimentId":null,"mabMaster":false,"mabVariant":false,"meta":{"html_title":"6 Questions to Ask Your HubSpot CMS Developer: Part 3","public_access_rules":[],"public_access_rules_enabled":false,"enable_google_amp_output_override":false,"generate_json_ld_enabled":true,"composition_id":0,"is_crawlable_by_bots":false,"use_featured_image":true,"post_body":"

We’ve discussed this many times before - but it’s always worth mentioning again: the HubSpot CMS developer that you choose will make or break (literally) your website or the websites of your clients, if you’re an agency. We’ve had so many clients come to us in bad situations after being let down by their developer partners. We think it’s important that agencies and businesses alike be able to understand exactly what to look for in an ideal development partner. For this reason, we’ve been offering up a little insight on things to address in your developer interview process.

There are a LOT of questions that you should ask a prospective HubSpot CMS developer before you decide to work with them. We’ve already taken time to outline 12 different questions in part one and part two of this series. We’re hoping that after part three that you’ll be armed with enough questions to adequately interview and qualify your HubSpot developer.

\n\n

Can you provide me with references?

\n

\n

This should be an easy one. Any developer that has experience in HubSpot CMS will be able to provide references of businesses or agencies that they’ve worked with to sing their praises as a developer.

Be sure to actually contact the references that you request. You’ll want to ask the references when they worked together and how the process went, as well as what they struggled with in the process and what went well. Struggles aren’t necessarily red flags, but how that developer handled the struggles could be, so make sure to ask about them.

\n

If we are lower budget, can you work with us?

\n

Some developers won’t work with certain budgets - and that’s important to know in advance. This is a really good question to ask your developer so that you can plan appropriately. It’s important to make sure you are realistic about what a lower budget can fetch you.

Many developers can make a smaller budget work, but you’ll almost always have to compromise features in the immediate. Some HubSpot developers (like us) get creative when clients have a lower budget and break down a website project into phases to help with the expense over time. We refer to this as growth-driven design. Growth-driven design allows you to get all the features and functions that you want in a huge website project by breaking out those features into a predictable monthly budget over a longer time period to soften the financial blow of a robust website.

Growth-driven design is the best approach to maximizing your return on investment with HubSpot and really making your website into a lead-generation machine. Choosing a web developer based on price or paying less for cheap, outsourced development will usually come back to bite you somewhere else along the way, so be sure that you’re being realistic when it comes to your goals and what will be required in order to achieve them.

\n

Related: Agencies Should Pay More for Web Development Outsourcing

\n

Will you be able to provide open an honest feedback on our ideas and designs?

\n

Having hard conversations is a skill set that’s extremely critical for a development partner, but one that isn’t often found, particularly when there are many layers of communication to pass through. A developer may become complacent and prone to order taking (we’ll keep saying it - your website isn’t a sub sandwich), especially when they’re bogged down with a lot of projects or just want to take a job for the money.

Other developers are here to make amazing websites that really deliver on a client’s behalf and help them reach their goals. They’re the type to geek out on page speed optimization and UX and A/B testing. They’re probably going to install a tool like Hotjar or Lucky Orange onto your website to understand user behavior.

Just because a design looks pretty, doesn’t mean that you’ve conceived exactly what a user might do when they interact with that information or planned that design out according to the buyer journey of your website visitors. An experienced developer has done this a few different times and they’re willing to say what will work and won’t work. At times we’ve been hamstrung when our agency clients are firm on a design, but that doesn’t mean we don’t speak up. Hire a developer that’s willing to say something and be willing to consider their opinion and feedback seriously when it comes to design changes, potential for design elements to cause website bloat and potential UX issues.

\n

Can you give more details on the developers that will be part of the project?

\n

Our owner, technical director, lead developer and all around do-everything guy is the one on our sales calls - but in larger organizations, that’s not always the case. You’re usually dealing with a sales rep and there’s an entire hive of people dedicated to delivering on your behalf. This can be great in some ways, but in others it can be a bit like a game of telephone. Organizations, especially HubSpot Partners, are usually pretty good at hiring developers that align with their mission. However, this isn’t always the case and getting to know more about the person behind the development of your website can be helpful.

Dig into who they are, where they came from, who they’ve worked with in the past. An agency’s experience isn’t necessarily an individual developer’s experience. The more you learn about the projects your individual developer (or team of developers) has worked on and how that can contribute to the success of your site, the more you’ll understand about their mentality in the development of your website project.

\n

What is the anticipated timeline?

\n

We hate “deadlines” - we prefer timelines. There are so many factors that can go into a website not being delivered on an exact date, and we think that choosing a random date for the completion for a huge project can set you up for disappointment. Your website isn’t a rocketship that’s launching into space. It’s not a one-and-done - it’s the delivery of something amazing. Almost like a child, you don’t want it coming out before it’s ready and you definitely want to make sure it’s fully developed. Having a “due date” rather than an expected timeframe can sometimes be unrealistic. We never make launch date promises, because there are too many factors outside of our control.

If, for some reason, you find yourself in a time crunch where you need a new website done quickly, keep in mind that you’ll have to compromise. A stripped back version of your website can likely be launched under a time crunch, but if you’re paying a premium for this, the very last thing you want is to rush it along.

All the best things take time. You have to keep in mind that you’re not the only project your developers are working on and if you want something now-now-now, you might have to sacrifice on things we never like to sacrifice on, like diligent quality assurance testing or superior back end functionality. Take your time. Realign your expectations with reasonable time frames rather than singular dates. We promise it’ll be worth it, and a good developer is almost always trying to overdeliver, so you may be pleasantly surprised by the date you end up launching on.

\n

How will we communicate?

\n

Different agencies communicate in different ways. Some include the client in their project management software for the granular details of their projects, while others prefer to correspond via e-mail. We’re pretty flexible and fit into the processes that exist with the different agency partners we work with. For our direct business clients, we typically use a combination of Slack and e-mail. E-mail is our go-to, but Slack helps us communicate quickly if we need an answer to something time sensitive. Feedback gets run through Pastel (our favorite collaboration and QA software), which makes things really efficient and seamless for us. We’ll take to Zoom for reviewing designs or running through screen-share scenarios as well.

Overall, you can probably expect a few different communication methods and none of them are wrong - but your developer will be able to give you the correct platform for communication in different scenarios. This is also a good time to mention any preferred communication methods you have. Your developer partner should be flexible, but still have boundaries and processes for regular communication and the best ways to submit requested edits.

\n

Related: HubSpot CMS Developer Quality Assurance - Why we Love Pastel

\n

 

\n

There they are - 6 more of our 18 interview questions to ask your HubSpot CMS developer during your interviews. While this is by no means a comprehensive list, we think it’ll get a really great dialogue going and help you prioritize what matters most. Take these questions and consider your biggest priorities when it comes to a web developer. Don’t forget that you always get what you pay for. The answers to these questions will show you exactly why some development agencies charge what they charge for development. And no matter what the agency you’re talking to charges? You can rest assured that they’re worth exactly that.

What are our final thoughts on the web development interviewing process when it comes to HubSpot CMS?

\n

\n
• Determine your priorities
\n
• Work with a developer that you LIKE
\n
• Expect to get back out exactly what you put in
\n
• Stick to deadlines to help your project run on time
\n
• Communicate changes that impact the project ASAP!
\n

\n

For businesses on HubSpot, your website is everything to you. This means that selecting your web developer is one of the most critical decisions that you’re going to make for your business’ growth.

\n

We hope our list of questions helps you choose wisely and make the most educated decision based on your business and priorities.

\n

Be sure to check out Part 1 and Part 2.

\n
\n

","rss_summary":"

We’ve discussed this many times before - but it’s always worth mentioning again: the HubSpot CMS developer that you choose will make or break (literally) your website or the websites of your clients, if you’re an agency. We’ve had so many clients come to us in bad situations after being let down by their developer partners. We think it’s important that agencies and businesses alike be able to understand exactly what to look for in an ideal development partner. For this reason, we’ve been offering up a little insight on things to address in your developer interview process.

There are a LOT of questions that you should ask a prospective HubSpot CMS developer before you decide to work with them. We’ve already taken time to outline 12 different questions in part one and part two of this series. We’re hoping that after part three that you’ll be armed with enough questions to adequately interview and qualify your HubSpot developer.

\n","rss_body":"

We’ve discussed this many times before - but it’s always worth mentioning again: the HubSpot CMS developer that you choose will make or break (literally) your website or the websites of your clients, if you’re an agency. We’ve had so many clients come to us in bad situations after being let down by their developer partners. We think it’s important that agencies and businesses alike be able to understand exactly what to look for in an ideal development partner. For this reason, we’ve been offering up a little insight on things to address in your developer interview process.

There are a LOT of questions that you should ask a prospective HubSpot CMS developer before you decide to work with them. We’ve already taken time to outline 12 different questions in part one and part two of this series. We’re hoping that after part three that you’ll be armed with enough questions to adequately interview and qualify your HubSpot developer.

\n\n

Can you provide me with references?

\n

\n

This should be an easy one. Any developer that has experience in HubSpot CMS will be able to provide references of businesses or agencies that they’ve worked with to sing their praises as a developer.

Be sure to actually contact the references that you request. You’ll want to ask the references when they worked together and how the process went, as well as what they struggled with in the process and what went well. Struggles aren’t necessarily red flags, but how that developer handled the struggles could be, so make sure to ask about them.

\n

If we are lower budget, can you work with us?

\n

Some developers won’t work with certain budgets - and that’s important to know in advance. This is a really good question to ask your developer so that you can plan appropriately. It’s important to make sure you are realistic about what a lower budget can fetch you.

Many developers can make a smaller budget work, but you’ll almost always have to compromise features in the immediate. Some HubSpot developers (like us) get creative when clients have a lower budget and break down a website project into phases to help with the expense over time. We refer to this as growth-driven design. Growth-driven design allows you to get all the features and functions that you want in a huge website project by breaking out those features into a predictable monthly budget over a longer time period to soften the financial blow of a robust website.

Growth-driven design is the best approach to maximizing your return on investment with HubSpot and really making your website into a lead-generation machine. Choosing a web developer based on price or paying less for cheap, outsourced development will usually come back to bite you somewhere else along the way, so be sure that you’re being realistic when it comes to your goals and what will be required in order to achieve them.

\n

Related: Agencies Should Pay More for Web Development Outsourcing

\n

Will you be able to provide open an honest feedback on our ideas and designs?

\n

Having hard conversations is a skill set that’s extremely critical for a development partner, but one that isn’t often found, particularly when there are many layers of communication to pass through. A developer may become complacent and prone to order taking (we’ll keep saying it - your website isn’t a sub sandwich), especially when they’re bogged down with a lot of projects or just want to take a job for the money.

Other developers are here to make amazing websites that really deliver on a client’s behalf and help them reach their goals. They’re the type to geek out on page speed optimization and UX and A/B testing. They’re probably going to install a tool like Hotjar or Lucky Orange onto your website to understand user behavior.

Just because a design looks pretty, doesn’t mean that you’ve conceived exactly what a user might do when they interact with that information or planned that design out according to the buyer journey of your website visitors. An experienced developer has done this a few different times and they’re willing to say what will work and won’t work. At times we’ve been hamstrung when our agency clients are firm on a design, but that doesn’t mean we don’t speak up. Hire a developer that’s willing to say something and be willing to consider their opinion and feedback seriously when it comes to design changes, potential for design elements to cause website bloat and potential UX issues.

\n

Can you give more details on the developers that will be part of the project?

\n

Our owner, technical director, lead developer and all around do-everything guy is the one on our sales calls - but in larger organizations, that’s not always the case. You’re usually dealing with a sales rep and there’s an entire hive of people dedicated to delivering on your behalf. This can be great in some ways, but in others it can be a bit like a game of telephone. Organizations, especially HubSpot Partners, are usually pretty good at hiring developers that align with their mission. However, this isn’t always the case and getting to know more about the person behind the development of your website can be helpful.

Dig into who they are, where they came from, who they’ve worked with in the past. An agency’s experience isn’t necessarily an individual developer’s experience. The more you learn about the projects your individual developer (or team of developers) has worked on and how that can contribute to the success of your site, the more you’ll understand about their mentality in the development of your website project.

\n

What is the anticipated timeline?

\n

We hate “deadlines” - we prefer timelines. There are so many factors that can go into a website not being delivered on an exact date, and we think that choosing a random date for the completion for a huge project can set you up for disappointment. Your website isn’t a rocketship that’s launching into space. It’s not a one-and-done - it’s the delivery of something amazing. Almost like a child, you don’t want it coming out before it’s ready and you definitely want to make sure it’s fully developed. Having a “due date” rather than an expected timeframe can sometimes be unrealistic. We never make launch date promises, because there are too many factors outside of our control.

If, for some reason, you find yourself in a time crunch where you need a new website done quickly, keep in mind that you’ll have to compromise. A stripped back version of your website can likely be launched under a time crunch, but if you’re paying a premium for this, the very last thing you want is to rush it along.

All the best things take time. You have to keep in mind that you’re not the only project your developers are working on and if you want something now-now-now, you might have to sacrifice on things we never like to sacrifice on, like diligent quality assurance testing or superior back end functionality. Take your time. Realign your expectations with reasonable time frames rather than singular dates. We promise it’ll be worth it, and a good developer is almost always trying to overdeliver, so you may be pleasantly surprised by the date you end up launching on.

\n

How will we communicate?

\n

Different agencies communicate in different ways. Some include the client in their project management software for the granular details of their projects, while others prefer to correspond via e-mail. We’re pretty flexible and fit into the processes that exist with the different agency partners we work with. For our direct business clients, we typically use a combination of Slack and e-mail. E-mail is our go-to, but Slack helps us communicate quickly if we need an answer to something time sensitive. Feedback gets run through Pastel (our favorite collaboration and QA software), which makes things really efficient and seamless for us. We’ll take to Zoom for reviewing designs or running through screen-share scenarios as well.

Overall, you can probably expect a few different communication methods and none of them are wrong - but your developer will be able to give you the correct platform for communication in different scenarios. This is also a good time to mention any preferred communication methods you have. Your developer partner should be flexible, but still have boundaries and processes for regular communication and the best ways to submit requested edits.

\n

Related: HubSpot CMS Developer Quality Assurance - Why we Love Pastel

\n

 

\n

There they are - 6 more of our 18 interview questions to ask your HubSpot CMS developer during your interviews. While this is by no means a comprehensive list, we think it’ll get a really great dialogue going and help you prioritize what matters most. Take these questions and consider your biggest priorities when it comes to a web developer. Don’t forget that you always get what you pay for. The answers to these questions will show you exactly why some development agencies charge what they charge for development. And no matter what the agency you’re talking to charges? You can rest assured that they’re worth exactly that.

What are our final thoughts on the web development interviewing process when it comes to HubSpot CMS?

\n

\n
• Determine your priorities
\n
• Work with a developer that you LIKE
\n
• Expect to get back out exactly what you put in
\n
• Stick to deadlines to help your project run on time
\n
• Communicate changes that impact the project ASAP!
\n

\n

For businesses on HubSpot, your website is everything to you. This means that selecting your web developer is one of the most critical decisions that you’re going to make for your business’ growth.

\n

We hope our list of questions helps you choose wisely and make the most educated decision based on your business and priorities.

\n

Be sure to check out Part 1 and Part 2.

\n
\n

","tag_ids":[62770442823,80453663900,81427543405],"topic_ids":[62770442823,80453663900,81427543405],"post_summary":"

We’ve discussed this many times before - but it’s always worth mentioning again: the HubSpot CMS developer that you choose will make or break (literally) your website or the websites of your clients, if you’re an agency. We’ve had so many clients come to us in bad situations after being let down by their developer partners. We think it’s important that agencies and businesses alike be able to understand exactly what to look for in an ideal development partner. For this reason, we’ve been offering up a little insight on things to address in your developer interview process.

There are a LOT of questions that you should ask a prospective HubSpot CMS developer before you decide to work with them. We’ve already taken time to outline 12 different questions in part one and part two of this series. We’re hoping that after part three that you’ll be armed with enough questions to adequately interview and qualify your HubSpot developer.

\n","blog_post_schedule_task_uid":null,"blog_publish_to_social_media_task":"DONE_NOT_SENT","blog_publish_instant_email_task_uid":null,"blog_publish_instant_email_campaign_id":null,"blog_publish_instant_email_retry_count":null,"keywords":[],"head_html":null,"footer_html":null,"attached_stylesheets":[],"enable_domain_stylesheets":null,"include_default_custom_css":null,"meta_description":"Here's part 3 with more questions to ask your HubSpot CMS developer. ","meta_keywords":null,"layout_sections":{},"past_mab_experiment_ids":[],"deleted_by":null,"featured_image_alt_text":"hubspot interview","enable_layout_stylesheets":null,"tweet":null,"tweet_at":null,"campaign_name":null,"campaign_utm":null,"tweet_immediately":false,"publish_immediately":true,"security_state":"NONE","scheduled_update_date":0,"placement_guids":[],"property_for_dynamic_page_title":null,"property_for_dynamic_page_slug":null,"property_for_dynamic_page_meta_description":null,"property_for_dynamic_page_featured_image":null,"property_for_dynamic_page_canonical_url":null,"preview_image_src":null,"legacy_blog_tabid":null,"legacy_post_guid":null,"performable_variation_letter":null,"style_override_id":null,"has_user_changes":true,"css":{},"css_text":"","unpublished_at":0,"published_by_id":27630257,"allowed_slug_conflict":false,"ai_features":null,"link_rel_canonical_url":null,"page_redirected":false,"page_expiry_enabled":null,"page_expiry_date":null,"page_expiry_redirect_id":null,"page_expiry_redirect_url":null,"deleted_by_id":null,"state_when_deleted":null,"cloned_from":null,"staged_from":null,"personas":[],"compose_body":null,"featured_image":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/job-interview-memes-1-5d14a7ea1163a__700.jpeg","featured_image_width":700,"featured_image_height":963,"publish_timezone_offset":null,"theme_settings_values":null,"password":null,"header":null,"published_at":1692280453931,"last_edit_session_id":null,"last_edit_update_id":null,"created_by_agent":null},"metaDescription":"Here's part 3 with more questions to ask your HubSpot CMS developer. ","metaKeywords":null,"name":"6 Questions to Ask Your HubSpot CMS Developer: Part 3","nextPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-interview%20questions.png","nextPostFeaturedImageAltText":"","nextPostName":"6 More HubSpot CMS Developer Interview Questions Part 2: The Process","nextPostSlug":"blogs/6-more-hubspot-cms-developer-interview-questions-part-2-the-process","pageExpiryDate":null,"pageExpiryEnabled":null,"pageExpiryRedirectId":null,"pageExpiryRedirectUrl":null,"pageRedirected":false,"pageTitle":"6 Questions to Ask Your HubSpot CMS Developer: Part 3","parentBlog":{"absoluteUrl":"https://deckerdevs.com/blogs","allowComments":true,"ampBodyColor":"#404040","ampBodyFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampBodyFontSize":"18","ampCustomCss":"","ampHeaderBackgroundColor":"#ffffff","ampHeaderColor":"#1e1e1e","ampHeaderFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampHeaderFontSize":"36","ampLinkColor":"#416bb3","ampLogoAlt":"","ampLogoHeight":0,"ampLogoSrc":"","ampLogoWidth":0,"analyticsPageId":62179259185,"attachedStylesheets":[],"audienceAccess":"PUBLIC","businessUnitId":null,"captchaAfterDays":7,"captchaAlways":false,"categoryId":3,"cdnPurgeEmbargoTime":null,"closeCommentsOlder":0,"commentDateFormat":"medium","commentFormGuid":"cb653aa1-3db4-4167-9b59-744c46d49682","commentMaxThreadDepth":3,"commentModeration":false,"commentNotificationEmails":["nicholas@deckerdevs.com","jessica@deckerdevs.com"],"commentShouldCreateContact":true,"commentVerificationText":"Thanks for participating in this conversation! We look forward to responding and to assisting where we can","cosObjectType":"BLOG","created":1639786189589,"createdDateTime":1639786189589,"dailyNotificationEmailId":null,"dateFormattingLanguage":null,"defaultGroupStyleId":"","defaultNotificationFromName":"","defaultNotificationReplyTo":"","deletedAt":0,"description":"rev up your hubspot system to the max! deckerdevs' turbo-charged blog is your ultimate guide to harnessing the full potential of hubspot development. unleash the marketing magic with ingenious tips, tricks, and hacks. get ready to level up your hubspot game!","domain":"","domainWhenPublished":"deckerdevs.com","emailApiSubscriptionId":null,"enableGoogleAmpOutput":false,"enableSocialAutoPublishing":false,"generateJsonLdEnabled":true,"header":null,"htmlFooter":"","htmlFooterIsShared":true,"htmlHead":"","htmlHeadIsShared":true,"htmlKeywords":[],"htmlTitle":"deckerdevs thought nuggets","id":62179259185,"ilsSubscriptionListsByType":{},"instantNotificationEmailId":null,"itemLayoutId":null,"itemTemplateIsShared":false,"itemTemplatePath":"deckerdevs-theme/templates/blog-content.html","label":"deckerdevs live blog","language":"en","legacyGuid":null,"legacyModuleId":null,"legacyTabId":null,"listingLayoutId":null,"listingPageId":62179259186,"listingTemplatePath":"","liveDomain":"deckerdevs.com","monthFilterFormat":"MMMM yyyy","monthlyNotificationEmailId":null,"name":"deckerdevs live blog","parentBlogUpdateTaskId":null,"portalId":6534445,"postHtmlFooter":"","postHtmlHead":"","postsPerListingPage":9,"postsPerRssFeed":10,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publicTitle":"thought nuggets","publishDateFormat":"medium","resolvedDomain":"deckerdevs.com","rootUrl":"https://deckerdevs.com/blogs","rssCustomFeed":null,"rssDescription":null,"rssItemFooter":null,"rssItemHeader":null,"settingsOverrides":{"itemLayoutId":false,"itemTemplatePath":false,"itemTemplateIsShared":false,"listingLayoutId":false,"listingTemplatePath":false,"postsPerListingPage":false,"showSummaryInListing":false,"useFeaturedImageInSummary":false,"htmlHead":false,"postHtmlHead":false,"htmlHeadIsShared":false,"htmlFooter":false,"listingPageHtmlFooter":false,"postHtmlFooter":false,"htmlFooterIsShared":false,"attachedStylesheets":false,"postsPerRssFeed":false,"showSummaryInRss":false,"showSummaryInEmails":false,"showSummariesInEmails":false,"allowComments":false,"commentShouldCreateContact":false,"commentModeration":false,"closeCommentsOlder":false,"commentNotificationEmails":false,"commentMaxThreadDepth":false,"commentVerificationText":false,"socialAccountTwitter":false,"showSocialLinkTwitter":false,"showSocialLinkLinkedin":false,"showSocialLinkFacebook":false,"enableGoogleAmpOutput":false,"ampLogoSrc":false,"ampLogoHeight":false,"ampLogoWidth":false,"ampLogoAlt":false,"ampHeaderFont":false,"ampHeaderFontSize":false,"ampHeaderColor":false,"ampHeaderBackgroundColor":false,"ampBodyFont":false,"ampBodyFontSize":false,"ampBodyColor":false,"ampLinkColor":false,"generateJsonLdEnabled":false},"showSocialLinkFacebook":true,"showSocialLinkLinkedin":true,"showSocialLinkTwitter":true,"showSummaryInEmails":true,"showSummaryInListing":true,"showSummaryInRss":true,"siteId":null,"slug":"blogs","socialAccountTwitter":"","state":null,"subscriptionContactsProperty":null,"subscriptionEmailType":null,"subscriptionFormGuid":null,"subscriptionListsByType":{},"title":null,"translatedFromId":null,"translations":{},"updated":1712344124471,"updatedDateTime":1712344124471,"urlBase":"deckerdevs.com/blogs","urlSegments":{"all":"all","archive":"archive","author":"author","page":"page","tag":"tag"},"useFeaturedImageInSummary":true,"usesDefaultTemplate":false,"weeklyNotificationEmailId":null},"password":null,"pastMabExperimentIds":[],"performableGuid":null,"performableVariationLetter":null,"personas":[],"placementGuids":[],"portableKey":null,"portalId":6534445,"position":null,"postBody":"

We’ve discussed this many times before - but it’s always worth mentioning again: the HubSpot CMS developer that you choose will make or break (literally) your website or the websites of your clients, if you’re an agency. We’ve had so many clients come to us in bad situations after being let down by their developer partners. We think it’s important that agencies and businesses alike be able to understand exactly what to look for in an ideal development partner. For this reason, we’ve been offering up a little insight on things to address in your developer interview process.

There are a LOT of questions that you should ask a prospective HubSpot CMS developer before you decide to work with them. We’ve already taken time to outline 12 different questions in part one and part two of this series. We’re hoping that after part three that you’ll be armed with enough questions to adequately interview and qualify your HubSpot developer.

\n\n

Can you provide me with references?

\n

\n

This should be an easy one. Any developer that has experience in HubSpot CMS will be able to provide references of businesses or agencies that they’ve worked with to sing their praises as a developer.

Be sure to actually contact the references that you request. You’ll want to ask the references when they worked together and how the process went, as well as what they struggled with in the process and what went well. Struggles aren’t necessarily red flags, but how that developer handled the struggles could be, so make sure to ask about them.

\n

If we are lower budget, can you work with us?

\n

Some developers won’t work with certain budgets - and that’s important to know in advance. This is a really good question to ask your developer so that you can plan appropriately. It’s important to make sure you are realistic about what a lower budget can fetch you.

Many developers can make a smaller budget work, but you’ll almost always have to compromise features in the immediate. Some HubSpot developers (like us) get creative when clients have a lower budget and break down a website project into phases to help with the expense over time. We refer to this as growth-driven design. Growth-driven design allows you to get all the features and functions that you want in a huge website project by breaking out those features into a predictable monthly budget over a longer time period to soften the financial blow of a robust website.

Growth-driven design is the best approach to maximizing your return on investment with HubSpot and really making your website into a lead-generation machine. Choosing a web developer based on price or paying less for cheap, outsourced development will usually come back to bite you somewhere else along the way, so be sure that you’re being realistic when it comes to your goals and what will be required in order to achieve them.

\n

Related: Agencies Should Pay More for Web Development Outsourcing

\n

Will you be able to provide open an honest feedback on our ideas and designs?

\n

Having hard conversations is a skill set that’s extremely critical for a development partner, but one that isn’t often found, particularly when there are many layers of communication to pass through. A developer may become complacent and prone to order taking (we’ll keep saying it - your website isn’t a sub sandwich), especially when they’re bogged down with a lot of projects or just want to take a job for the money.

Other developers are here to make amazing websites that really deliver on a client’s behalf and help them reach their goals. They’re the type to geek out on page speed optimization and UX and A/B testing. They’re probably going to install a tool like Hotjar or Lucky Orange onto your website to understand user behavior.

Just because a design looks pretty, doesn’t mean that you’ve conceived exactly what a user might do when they interact with that information or planned that design out according to the buyer journey of your website visitors. An experienced developer has done this a few different times and they’re willing to say what will work and won’t work. At times we’ve been hamstrung when our agency clients are firm on a design, but that doesn’t mean we don’t speak up. Hire a developer that’s willing to say something and be willing to consider their opinion and feedback seriously when it comes to design changes, potential for design elements to cause website bloat and potential UX issues.

\n

Can you give more details on the developers that will be part of the project?

\n

Our owner, technical director, lead developer and all around do-everything guy is the one on our sales calls - but in larger organizations, that’s not always the case. You’re usually dealing with a sales rep and there’s an entire hive of people dedicated to delivering on your behalf. This can be great in some ways, but in others it can be a bit like a game of telephone. Organizations, especially HubSpot Partners, are usually pretty good at hiring developers that align with their mission. However, this isn’t always the case and getting to know more about the person behind the development of your website can be helpful.

Dig into who they are, where they came from, who they’ve worked with in the past. An agency’s experience isn’t necessarily an individual developer’s experience. The more you learn about the projects your individual developer (or team of developers) has worked on and how that can contribute to the success of your site, the more you’ll understand about their mentality in the development of your website project.

\n

What is the anticipated timeline?

\n

We hate “deadlines” - we prefer timelines. There are so many factors that can go into a website not being delivered on an exact date, and we think that choosing a random date for the completion for a huge project can set you up for disappointment. Your website isn’t a rocketship that’s launching into space. It’s not a one-and-done - it’s the delivery of something amazing. Almost like a child, you don’t want it coming out before it’s ready and you definitely want to make sure it’s fully developed. Having a “due date” rather than an expected timeframe can sometimes be unrealistic. We never make launch date promises, because there are too many factors outside of our control.

If, for some reason, you find yourself in a time crunch where you need a new website done quickly, keep in mind that you’ll have to compromise. A stripped back version of your website can likely be launched under a time crunch, but if you’re paying a premium for this, the very last thing you want is to rush it along.

All the best things take time. You have to keep in mind that you’re not the only project your developers are working on and if you want something now-now-now, you might have to sacrifice on things we never like to sacrifice on, like diligent quality assurance testing or superior back end functionality. Take your time. Realign your expectations with reasonable time frames rather than singular dates. We promise it’ll be worth it, and a good developer is almost always trying to overdeliver, so you may be pleasantly surprised by the date you end up launching on.

\n

How will we communicate?

\n

Different agencies communicate in different ways. Some include the client in their project management software for the granular details of their projects, while others prefer to correspond via e-mail. We’re pretty flexible and fit into the processes that exist with the different agency partners we work with. For our direct business clients, we typically use a combination of Slack and e-mail. E-mail is our go-to, but Slack helps us communicate quickly if we need an answer to something time sensitive. Feedback gets run through Pastel (our favorite collaboration and QA software), which makes things really efficient and seamless for us. We’ll take to Zoom for reviewing designs or running through screen-share scenarios as well.

Overall, you can probably expect a few different communication methods and none of them are wrong - but your developer will be able to give you the correct platform for communication in different scenarios. This is also a good time to mention any preferred communication methods you have. Your developer partner should be flexible, but still have boundaries and processes for regular communication and the best ways to submit requested edits.

\n

Related: HubSpot CMS Developer Quality Assurance - Why we Love Pastel

\n

 

\n

There they are - 6 more of our 18 interview questions to ask your HubSpot CMS developer during your interviews. While this is by no means a comprehensive list, we think it’ll get a really great dialogue going and help you prioritize what matters most. Take these questions and consider your biggest priorities when it comes to a web developer. Don’t forget that you always get what you pay for. The answers to these questions will show you exactly why some development agencies charge what they charge for development. And no matter what the agency you’re talking to charges? You can rest assured that they’re worth exactly that.

What are our final thoughts on the web development interviewing process when it comes to HubSpot CMS?

\n

\n
• Determine your priorities
\n
• Work with a developer that you LIKE
\n
• Expect to get back out exactly what you put in
\n
• Stick to deadlines to help your project run on time
\n
• Communicate changes that impact the project ASAP!
\n

\n

For businesses on HubSpot, your website is everything to you. This means that selecting your web developer is one of the most critical decisions that you’re going to make for your business’ growth.

\n

We hope our list of questions helps you choose wisely and make the most educated decision based on your business and priorities.

\n

Be sure to check out Part 1 and Part 2.

\n
\n

","postBodyRss":"

We’ve discussed this many times before - but it’s always worth mentioning again: the HubSpot CMS developer that you choose will make or break (literally) your website or the websites of your clients, if you’re an agency. We’ve had so many clients come to us in bad situations after being let down by their developer partners. We think it’s important that agencies and businesses alike be able to understand exactly what to look for in an ideal development partner. For this reason, we’ve been offering up a little insight on things to address in your developer interview process.

There are a LOT of questions that you should ask a prospective HubSpot CMS developer before you decide to work with them. We’ve already taken time to outline 12 different questions in part one and part two of this series. We’re hoping that after part three that you’ll be armed with enough questions to adequately interview and qualify your HubSpot developer.

\n\n

Can you provide me with references?

\n

\n

This should be an easy one. Any developer that has experience in HubSpot CMS will be able to provide references of businesses or agencies that they’ve worked with to sing their praises as a developer.

Be sure to actually contact the references that you request. You’ll want to ask the references when they worked together and how the process went, as well as what they struggled with in the process and what went well. Struggles aren’t necessarily red flags, but how that developer handled the struggles could be, so make sure to ask about them.

\n

If we are lower budget, can you work with us?

\n

Some developers won’t work with certain budgets - and that’s important to know in advance. This is a really good question to ask your developer so that you can plan appropriately. It’s important to make sure you are realistic about what a lower budget can fetch you.

Many developers can make a smaller budget work, but you’ll almost always have to compromise features in the immediate. Some HubSpot developers (like us) get creative when clients have a lower budget and break down a website project into phases to help with the expense over time. We refer to this as growth-driven design. Growth-driven design allows you to get all the features and functions that you want in a huge website project by breaking out those features into a predictable monthly budget over a longer time period to soften the financial blow of a robust website.

Growth-driven design is the best approach to maximizing your return on investment with HubSpot and really making your website into a lead-generation machine. Choosing a web developer based on price or paying less for cheap, outsourced development will usually come back to bite you somewhere else along the way, so be sure that you’re being realistic when it comes to your goals and what will be required in order to achieve them.

\n

Related: Agencies Should Pay More for Web Development Outsourcing

\n

Will you be able to provide open an honest feedback on our ideas and designs?

\n

Having hard conversations is a skill set that’s extremely critical for a development partner, but one that isn’t often found, particularly when there are many layers of communication to pass through. A developer may become complacent and prone to order taking (we’ll keep saying it - your website isn’t a sub sandwich), especially when they’re bogged down with a lot of projects or just want to take a job for the money.

Other developers are here to make amazing websites that really deliver on a client’s behalf and help them reach their goals. They’re the type to geek out on page speed optimization and UX and A/B testing. They’re probably going to install a tool like Hotjar or Lucky Orange onto your website to understand user behavior.

Just because a design looks pretty, doesn’t mean that you’ve conceived exactly what a user might do when they interact with that information or planned that design out according to the buyer journey of your website visitors. An experienced developer has done this a few different times and they’re willing to say what will work and won’t work. At times we’ve been hamstrung when our agency clients are firm on a design, but that doesn’t mean we don’t speak up. Hire a developer that’s willing to say something and be willing to consider their opinion and feedback seriously when it comes to design changes, potential for design elements to cause website bloat and potential UX issues.

\n

Can you give more details on the developers that will be part of the project?

\n

Our owner, technical director, lead developer and all around do-everything guy is the one on our sales calls - but in larger organizations, that’s not always the case. You’re usually dealing with a sales rep and there’s an entire hive of people dedicated to delivering on your behalf. This can be great in some ways, but in others it can be a bit like a game of telephone. Organizations, especially HubSpot Partners, are usually pretty good at hiring developers that align with their mission. However, this isn’t always the case and getting to know more about the person behind the development of your website can be helpful.

Dig into who they are, where they came from, who they’ve worked with in the past. An agency’s experience isn’t necessarily an individual developer’s experience. The more you learn about the projects your individual developer (or team of developers) has worked on and how that can contribute to the success of your site, the more you’ll understand about their mentality in the development of your website project.

\n

What is the anticipated timeline?

\n

We hate “deadlines” - we prefer timelines. There are so many factors that can go into a website not being delivered on an exact date, and we think that choosing a random date for the completion for a huge project can set you up for disappointment. Your website isn’t a rocketship that’s launching into space. It’s not a one-and-done - it’s the delivery of something amazing. Almost like a child, you don’t want it coming out before it’s ready and you definitely want to make sure it’s fully developed. Having a “due date” rather than an expected timeframe can sometimes be unrealistic. We never make launch date promises, because there are too many factors outside of our control.

If, for some reason, you find yourself in a time crunch where you need a new website done quickly, keep in mind that you’ll have to compromise. A stripped back version of your website can likely be launched under a time crunch, but if you’re paying a premium for this, the very last thing you want is to rush it along.

All the best things take time. You have to keep in mind that you’re not the only project your developers are working on and if you want something now-now-now, you might have to sacrifice on things we never like to sacrifice on, like diligent quality assurance testing or superior back end functionality. Take your time. Realign your expectations with reasonable time frames rather than singular dates. We promise it’ll be worth it, and a good developer is almost always trying to overdeliver, so you may be pleasantly surprised by the date you end up launching on.

\n

How will we communicate?

\n

Different agencies communicate in different ways. Some include the client in their project management software for the granular details of their projects, while others prefer to correspond via e-mail. We’re pretty flexible and fit into the processes that exist with the different agency partners we work with. For our direct business clients, we typically use a combination of Slack and e-mail. E-mail is our go-to, but Slack helps us communicate quickly if we need an answer to something time sensitive. Feedback gets run through Pastel (our favorite collaboration and QA software), which makes things really efficient and seamless for us. We’ll take to Zoom for reviewing designs or running through screen-share scenarios as well.

Overall, you can probably expect a few different communication methods and none of them are wrong - but your developer will be able to give you the correct platform for communication in different scenarios. This is also a good time to mention any preferred communication methods you have. Your developer partner should be flexible, but still have boundaries and processes for regular communication and the best ways to submit requested edits.

\n

Related: HubSpot CMS Developer Quality Assurance - Why we Love Pastel

\n

 

\n

There they are - 6 more of our 18 interview questions to ask your HubSpot CMS developer during your interviews. While this is by no means a comprehensive list, we think it’ll get a really great dialogue going and help you prioritize what matters most. Take these questions and consider your biggest priorities when it comes to a web developer. Don’t forget that you always get what you pay for. The answers to these questions will show you exactly why some development agencies charge what they charge for development. And no matter what the agency you’re talking to charges? You can rest assured that they’re worth exactly that.

What are our final thoughts on the web development interviewing process when it comes to HubSpot CMS?

\n

\n
• Determine your priorities
\n
• Work with a developer that you LIKE
\n
• Expect to get back out exactly what you put in
\n
• Stick to deadlines to help your project run on time
\n
• Communicate changes that impact the project ASAP!
\n

\n

For businesses on HubSpot, your website is everything to you. This means that selecting your web developer is one of the most critical decisions that you’re going to make for your business’ growth.

\n

We hope our list of questions helps you choose wisely and make the most educated decision based on your business and priorities.

\n

Be sure to check out Part 1 and Part 2.

\n
\n

","postEmailContent":"

We’ve discussed this many times before - but it’s always worth mentioning again: the HubSpot CMS developer that you choose will make or break (literally) your website or the websites of your clients, if you’re an agency. We’ve had so many clients come to us in bad situations after being let down by their developer partners. We think it’s important that agencies and businesses alike be able to understand exactly what to look for in an ideal development partner. For this reason, we’ve been offering up a little insight on things to address in your developer interview process.

There are a LOT of questions that you should ask a prospective HubSpot CMS developer before you decide to work with them. We’ve already taken time to outline 12 different questions in part one and part two of this series. We’re hoping that after part three that you’ll be armed with enough questions to adequately interview and qualify your HubSpot developer.

","postFeaturedImageIfEnabled":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/job-interview-memes-1-5d14a7ea1163a__700.jpeg","postListContent":"

We’ve discussed this many times before - but it’s always worth mentioning again: the HubSpot CMS developer that you choose will make or break (literally) your website or the websites of your clients, if you’re an agency. We’ve had so many clients come to us in bad situations after being let down by their developer partners. We think it’s important that agencies and businesses alike be able to understand exactly what to look for in an ideal development partner. For this reason, we’ve been offering up a little insight on things to address in your developer interview process.

There are a LOT of questions that you should ask a prospective HubSpot CMS developer before you decide to work with them. We’ve already taken time to outline 12 different questions in part one and part two of this series. We’re hoping that after part three that you’ll be armed with enough questions to adequately interview and qualify your HubSpot developer.

","postListSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/job-interview-memes-1-5d14a7ea1163a__700.jpeg","postRssContent":"

We’ve discussed this many times before - but it’s always worth mentioning again: the HubSpot CMS developer that you choose will make or break (literally) your website or the websites of your clients, if you’re an agency. We’ve had so many clients come to us in bad situations after being let down by their developer partners. We think it’s important that agencies and businesses alike be able to understand exactly what to look for in an ideal development partner. For this reason, we’ve been offering up a little insight on things to address in your developer interview process.

There are a LOT of questions that you should ask a prospective HubSpot CMS developer before you decide to work with them. We’ve already taken time to outline 12 different questions in part one and part two of this series. We’re hoping that after part three that you’ll be armed with enough questions to adequately interview and qualify your HubSpot developer.

","postRssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/job-interview-memes-1-5d14a7ea1163a__700.jpeg","postSummary":"

We’ve discussed this many times before - but it’s always worth mentioning again: the HubSpot CMS developer that you choose will make or break (literally) your website or the websites of your clients, if you’re an agency. We’ve had so many clients come to us in bad situations after being let down by their developer partners. We think it’s important that agencies and businesses alike be able to understand exactly what to look for in an ideal development partner. For this reason, we’ve been offering up a little insight on things to address in your developer interview process.

There are a LOT of questions that you should ask a prospective HubSpot CMS developer before you decide to work with them. We’ve already taken time to outline 12 different questions in part one and part two of this series. We’re hoping that after part three that you’ll be armed with enough questions to adequately interview and qualify your HubSpot developer.

\n","postSummaryRss":"

We’ve discussed this many times before - but it’s always worth mentioning again: the HubSpot CMS developer that you choose will make or break (literally) your website or the websites of your clients, if you’re an agency. We’ve had so many clients come to us in bad situations after being let down by their developer partners. We think it’s important that agencies and businesses alike be able to understand exactly what to look for in an ideal development partner. For this reason, we’ve been offering up a little insight on things to address in your developer interview process.

There are a LOT of questions that you should ask a prospective HubSpot CMS developer before you decide to work with them. We’ve already taken time to outline 12 different questions in part one and part two of this series. We’re hoping that after part three that you’ll be armed with enough questions to adequately interview and qualify your HubSpot developer.

","postTemplate":"deckerdevs-theme/templates/blog-content.html","previewImageSrc":null,"previewKey":"DLYyQsxX","previousPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/complicated.jpeg","previousPostFeaturedImageAltText":"complicated api key hubspot","previousPostName":"HubSpot API Integrations: FAQs Sunsetting API Keys for Private Apps","previousPostSlug":"blogs/hubspot-api-integrations-faqs-sunsetting-api-keys-for-private-apps","processingStatus":"PUBLISHED","propertyForDynamicPageCanonicalUrl":null,"propertyForDynamicPageFeaturedImage":null,"propertyForDynamicPageMetaDescription":null,"propertyForDynamicPageSlug":null,"propertyForDynamicPageTitle":null,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publishDate":1661358300000,"publishDateLocalTime":1661358300000,"publishDateLocalized":{"date":1661358300000,"format":"medium","language":null},"publishImmediately":true,"publishTimezoneOffset":null,"publishedAt":1692280453931,"publishedByEmail":null,"publishedById":27630257,"publishedByName":null,"publishedUrl":"https://deckerdevs.com/blogs/6-questions-to-ask-your-hubspot-cms-developer-part-3","resolvedDomain":"deckerdevs.com","resolvedLanguage":null,"rssBody":"

We’ve discussed this many times before - but it’s always worth mentioning again: the HubSpot CMS developer that you choose will make or break (literally) your website or the websites of your clients, if you’re an agency. We’ve had so many clients come to us in bad situations after being let down by their developer partners. We think it’s important that agencies and businesses alike be able to understand exactly what to look for in an ideal development partner. For this reason, we’ve been offering up a little insight on things to address in your developer interview process.

There are a LOT of questions that you should ask a prospective HubSpot CMS developer before you decide to work with them. We’ve already taken time to outline 12 different questions in part one and part two of this series. We’re hoping that after part three that you’ll be armed with enough questions to adequately interview and qualify your HubSpot developer.

\n\n

Can you provide me with references?

\n

\n

This should be an easy one. Any developer that has experience in HubSpot CMS will be able to provide references of businesses or agencies that they’ve worked with to sing their praises as a developer.

Be sure to actually contact the references that you request. You’ll want to ask the references when they worked together and how the process went, as well as what they struggled with in the process and what went well. Struggles aren’t necessarily red flags, but how that developer handled the struggles could be, so make sure to ask about them.

\n

If we are lower budget, can you work with us?

\n

Some developers won’t work with certain budgets - and that’s important to know in advance. This is a really good question to ask your developer so that you can plan appropriately. It’s important to make sure you are realistic about what a lower budget can fetch you.

Many developers can make a smaller budget work, but you’ll almost always have to compromise features in the immediate. Some HubSpot developers (like us) get creative when clients have a lower budget and break down a website project into phases to help with the expense over time. We refer to this as growth-driven design. Growth-driven design allows you to get all the features and functions that you want in a huge website project by breaking out those features into a predictable monthly budget over a longer time period to soften the financial blow of a robust website.

Growth-driven design is the best approach to maximizing your return on investment with HubSpot and really making your website into a lead-generation machine. Choosing a web developer based on price or paying less for cheap, outsourced development will usually come back to bite you somewhere else along the way, so be sure that you’re being realistic when it comes to your goals and what will be required in order to achieve them.

\n

Related: Agencies Should Pay More for Web Development Outsourcing

\n

Will you be able to provide open an honest feedback on our ideas and designs?

\n

Having hard conversations is a skill set that’s extremely critical for a development partner, but one that isn’t often found, particularly when there are many layers of communication to pass through. A developer may become complacent and prone to order taking (we’ll keep saying it - your website isn’t a sub sandwich), especially when they’re bogged down with a lot of projects or just want to take a job for the money.

Other developers are here to make amazing websites that really deliver on a client’s behalf and help them reach their goals. They’re the type to geek out on page speed optimization and UX and A/B testing. They’re probably going to install a tool like Hotjar or Lucky Orange onto your website to understand user behavior.

Just because a design looks pretty, doesn’t mean that you’ve conceived exactly what a user might do when they interact with that information or planned that design out according to the buyer journey of your website visitors. An experienced developer has done this a few different times and they’re willing to say what will work and won’t work. At times we’ve been hamstrung when our agency clients are firm on a design, but that doesn’t mean we don’t speak up. Hire a developer that’s willing to say something and be willing to consider their opinion and feedback seriously when it comes to design changes, potential for design elements to cause website bloat and potential UX issues.

\n

Can you give more details on the developers that will be part of the project?

\n

Our owner, technical director, lead developer and all around do-everything guy is the one on our sales calls - but in larger organizations, that’s not always the case. You’re usually dealing with a sales rep and there’s an entire hive of people dedicated to delivering on your behalf. This can be great in some ways, but in others it can be a bit like a game of telephone. Organizations, especially HubSpot Partners, are usually pretty good at hiring developers that align with their mission. However, this isn’t always the case and getting to know more about the person behind the development of your website can be helpful.

Dig into who they are, where they came from, who they’ve worked with in the past. An agency’s experience isn’t necessarily an individual developer’s experience. The more you learn about the projects your individual developer (or team of developers) has worked on and how that can contribute to the success of your site, the more you’ll understand about their mentality in the development of your website project.

\n

What is the anticipated timeline?

\n

We hate “deadlines” - we prefer timelines. There are so many factors that can go into a website not being delivered on an exact date, and we think that choosing a random date for the completion for a huge project can set you up for disappointment. Your website isn’t a rocketship that’s launching into space. It’s not a one-and-done - it’s the delivery of something amazing. Almost like a child, you don’t want it coming out before it’s ready and you definitely want to make sure it’s fully developed. Having a “due date” rather than an expected timeframe can sometimes be unrealistic. We never make launch date promises, because there are too many factors outside of our control.

If, for some reason, you find yourself in a time crunch where you need a new website done quickly, keep in mind that you’ll have to compromise. A stripped back version of your website can likely be launched under a time crunch, but if you’re paying a premium for this, the very last thing you want is to rush it along.

All the best things take time. You have to keep in mind that you’re not the only project your developers are working on and if you want something now-now-now, you might have to sacrifice on things we never like to sacrifice on, like diligent quality assurance testing or superior back end functionality. Take your time. Realign your expectations with reasonable time frames rather than singular dates. We promise it’ll be worth it, and a good developer is almost always trying to overdeliver, so you may be pleasantly surprised by the date you end up launching on.

\n

How will we communicate?

\n

Different agencies communicate in different ways. Some include the client in their project management software for the granular details of their projects, while others prefer to correspond via e-mail. We’re pretty flexible and fit into the processes that exist with the different agency partners we work with. For our direct business clients, we typically use a combination of Slack and e-mail. E-mail is our go-to, but Slack helps us communicate quickly if we need an answer to something time sensitive. Feedback gets run through Pastel (our favorite collaboration and QA software), which makes things really efficient and seamless for us. We’ll take to Zoom for reviewing designs or running through screen-share scenarios as well.

Overall, you can probably expect a few different communication methods and none of them are wrong - but your developer will be able to give you the correct platform for communication in different scenarios. This is also a good time to mention any preferred communication methods you have. Your developer partner should be flexible, but still have boundaries and processes for regular communication and the best ways to submit requested edits.

\n

Related: HubSpot CMS Developer Quality Assurance - Why we Love Pastel

\n

 

\n

There they are - 6 more of our 18 interview questions to ask your HubSpot CMS developer during your interviews. While this is by no means a comprehensive list, we think it’ll get a really great dialogue going and help you prioritize what matters most. Take these questions and consider your biggest priorities when it comes to a web developer. Don’t forget that you always get what you pay for. The answers to these questions will show you exactly why some development agencies charge what they charge for development. And no matter what the agency you’re talking to charges? You can rest assured that they’re worth exactly that.

What are our final thoughts on the web development interviewing process when it comes to HubSpot CMS?

\n

\n
• Determine your priorities
\n
• Work with a developer that you LIKE
\n
• Expect to get back out exactly what you put in
\n
• Stick to deadlines to help your project run on time
\n
• Communicate changes that impact the project ASAP!
\n

\n

For businesses on HubSpot, your website is everything to you. This means that selecting your web developer is one of the most critical decisions that you’re going to make for your business’ growth.

\n

We hope our list of questions helps you choose wisely and make the most educated decision based on your business and priorities.

\n

Be sure to check out Part 1 and Part 2.

\n
\n

","rssSummary":"

We’ve discussed this many times before - but it’s always worth mentioning again: the HubSpot CMS developer that you choose will make or break (literally) your website or the websites of your clients, if you’re an agency. We’ve had so many clients come to us in bad situations after being let down by their developer partners. We think it’s important that agencies and businesses alike be able to understand exactly what to look for in an ideal development partner. For this reason, we’ve been offering up a little insight on things to address in your developer interview process.

There are a LOT of questions that you should ask a prospective HubSpot CMS developer before you decide to work with them. We’ve already taken time to outline 12 different questions in part one and part two of this series. We’re hoping that after part three that you’ll be armed with enough questions to adequately interview and qualify your HubSpot developer.

\n","rssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/job-interview-memes-1-5d14a7ea1163a__700.jpeg","scheduledUpdateDate":0,"screenshotPreviewTakenAt":1735307653132,"screenshotPreviewUrl":"https://cdn1.hubspot.net/hubshotv3/prod/e/0/92cfd312-4e9b-4516-abc9-29f871387a31.png","sections":{},"securityState":"NONE","siteId":null,"slug":"blogs/6-questions-to-ask-your-hubspot-cms-developer-part-3","stagedFrom":null,"state":"PUBLISHED","stateWhenDeleted":null,"structuredContentPageType":null,"structuredContentType":null,"styleOverrideId":null,"subcategory":"normal_blog_post","syncedWithBlogRoot":true,"tagIds":[62770442823,80453663900,81427543405],"tagList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1659024478836,"deletedAt":0,"description":"","id":80453663900,"label":"Agency Outsourcing","language":"en","name":"Agency Outsourcing","portalId":6534445,"slug":"agency-outsourcing","translatedFromId":null,"translations":{},"updated":1659024478836},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1659974680861,"deletedAt":0,"description":"","id":81427543405,"label":"Growth-Driven Design","language":"en","name":"Growth-Driven Design","portalId":6534445,"slug":"growth-driven-design","translatedFromId":null,"translations":{},"updated":1659974680861}],"tagNames":["HubSpot CMS Development","Agency Outsourcing","Growth-Driven Design"],"teamPerms":[],"templatePath":"","templatePathForRender":"deckerdevs-theme/templates/blog-content.html","textToAudioFileId":null,"textToAudioGenerationRequestId":null,"themePath":null,"themeSettingsValues":null,"title":"6 Questions to Ask Your HubSpot CMS Developer: Part 3","tmsId":null,"topicIds":[62770442823,80453663900,81427543405],"topicList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1659024478836,"deletedAt":0,"description":"","id":80453663900,"label":"Agency Outsourcing","language":"en","name":"Agency Outsourcing","portalId":6534445,"slug":"agency-outsourcing","translatedFromId":null,"translations":{},"updated":1659024478836},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1659974680861,"deletedAt":0,"description":"","id":81427543405,"label":"Growth-Driven Design","language":"en","name":"Growth-Driven Design","portalId":6534445,"slug":"growth-driven-design","translatedFromId":null,"translations":{},"updated":1659974680861}],"topicNames":["HubSpot CMS Development","Agency Outsourcing","Growth-Driven Design"],"topics":[62770442823,80453663900,81427543405],"translatedContent":{},"translatedFromId":null,"translations":{},"tweet":null,"tweetAt":null,"tweetImmediately":false,"unpublishedAt":0,"updated":1692280453937,"updatedById":27630257,"upsizeFeaturedImage":false,"url":"https://deckerdevs.com/blogs/6-questions-to-ask-your-hubspot-cms-developer-part-3","useFeaturedImage":true,"userPerms":[],"views":null,"visibleToAll":null,"widgetContainers":{},"widgetcontainers":{},"widgets":{"blog-image":{"body":{"image_field":{"alt":"pattern-2","height":563,"loading":"lazy","max_height":563,"max_width":1000,"size_type":"auto","src":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/pattern-2.jpg","width":1000},"module_id":62246908725},"child_css":{},"css":{},"deleted_at":1692280429259,"id":"blog-image","label":null,"module_id":62246908725,"name":"blog-image","order":3,"smart_type":null,"styles":{},"type":"module"}}},{"ab":false,"abStatus":null,"abTestId":null,"abVariation":false,"abVariationAutomated":false,"absoluteUrl":"https://deckerdevs.com/blogs/6-more-hubspot-cms-developer-interview-questions-part-2-the-process","afterPostBody":null,"aifeatures":null,"allowedSlugConflict":false,"analytics":null,"analyticsPageId":"82662190437","analyticsPageType":"blog-post","approvalStatus":null,"archived":false,"archivedAt":0,"archivedInDashboard":false,"areCommentsAllowed":true,"attachedStylesheets":[],"audienceAccess":"PUBLIC","author":null,"authorName":null,"authorUsername":null,"blogAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogAuthorId":62235724408,"blogPostAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogPostScheduleTaskUid":null,"blogPublishInstantEmailCampaignId":null,"blogPublishInstantEmailRetryCount":null,"blogPublishInstantEmailTaskUid":null,"blogPublishToSocialMediaTask":"DONE_NOT_SENT","blueprintTypeId":0,"businessUnitId":null,"campaign":null,"campaignName":null,"campaignUtm":null,"category":3,"categoryId":3,"cdnPurgeEmbargoTime":null,"checkPostLevelAudienceAccessFirst":true,"clonedFrom":null,"composeBody":null,"compositionId":0,"contentAccessRuleIds":[],"contentAccessRuleTypes":[],"contentGroup":62179259185,"contentGroupId":62179259185,"contentTypeCategory":3,"contentTypeCategoryId":3,"contentTypeId":null,"created":1661181128808,"createdByAgent":null,"createdById":27630257,"createdTime":1661181128808,"crmObjectId":null,"css":{},"cssText":"","ctaClicks":null,"ctaViews":null,"currentState":"PUBLISHED","currentlyPublished":true,"deletedAt":0,"deletedBy":null,"deletedByEmail":null,"deletedById":null,"domain":"","dynamicPageDataSourceId":null,"dynamicPageDataSourceType":null,"dynamicPageHubDbTableId":null,"enableDomainStylesheets":null,"enableGoogleAmpOutputOverride":false,"enableLayoutStylesheets":null,"errors":[],"featuredImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-interview%20questions.png","featuredImageAltText":"","featuredImageHeight":1080,"featuredImageLength":0,"featuredImageWidth":1080,"flexAreas":{},"folderId":null,"footerHtml":null,"freezeDate":1661183901000,"generateJsonLdEnabledOverride":true,"hasContentAccessRules":false,"hasUserChanges":true,"headHtml":null,"header":null,"htmlTitle":"6 More HubSpot CMS Developer Interview Questions Part 2: The Process","id":82662190437,"includeDefaultCustomCss":null,"isCaptchaRequired":true,"isCrawlableByBots":false,"isDraft":false,"isInstanceLayoutPage":false,"isInstantEmailEnabled":false,"isPublished":true,"isSocialPublishingEnabled":false,"keywords":[],"label":"6 More HubSpot CMS Developer Interview Questions Part 2: The Process","language":"en","lastEditSessionId":null,"lastEditUpdateId":null,"layoutSections":{},"legacyBlogTabid":null,"legacyId":null,"legacyPostGuid":null,"linkRelCanonicalUrl":"","listTemplate":"","liveDomain":"deckerdevs.com","mab":false,"mabExperimentId":null,"mabMaster":false,"mabVariant":false,"meta":{"html_title":"6 More HubSpot CMS Developer Interview Questions Part 2: The Process","public_access_rules":[],"public_access_rules_enabled":false,"enable_google_amp_output_override":false,"generate_json_ld_enabled":true,"composition_id":0,"is_crawlable_by_bots":false,"use_featured_image":true,"post_body":"

The most critical aspect of your entire HubSpot CMS project isn’t the day that you launch it, but the day you choose your HubSpot CMS developer. We’ve witnessed agencies being ghosted by their HubSpot developer, businesses that had to perform their own quality assurance testing despite contracting large agencies and so many other misadventures when it comes to HubSpot development over the years. We’ve lost projects to budget-conscious companies only for them to come back and tell us how paying less ended up costing them more in the long run.

We wish that we could be there to help you vet your HubSpot developer ourselves, because what is most important to us isn’t getting the work ourselves. What is most important to us is that amazing, beautiful projects are created on HubSpot CMS by gifted developers that allow marketers and business owners to really leverage the platform and meet their goals. Maybe it’s idealistic - but that’s what we’re really about.

We’re still a small shop and while we cannot take on every project that comes our way, we want you to have the tools at your disposal to make sure you ask the right questions to qualify the HubSpot CMS development partner that you’re vetting. While we’ve already taken the time to break down Part 1 of 6 HubSpot CMS developer interview questions, the list is long and we need to tell you 6 more…

\n\n

Can you show me something you've completed recently that you're proud of?

\n

You’d be surprised how often, especially being an agency-focused development shop, we take on the development of designs that we don’t love. While we know better than to ever be order takers (everyone knows your website isn’t a sub sandwich), at the end of the day our recommendations may be hampered by budget or stubborn clients. There are some projects that we’ve completed that we’re proud of - but there are other projects that we championed from start to finish to deliver something truly amazing - and those are the ones that we want to show our prospects.

A qualified web development partner will not just be happy to show you his or her most prized projects, but they’ll be enthusiastic about it. An experienced development partner will have a lot of different projects in HubSpot CMS and be able to talk about the obstacles they overcame to create them. Showcasing work they’re proud of will tell you a lot about the agency or developer you’re selecting. You’ll want your developer to approach your project with the amount of passion they’ve shown to their favorite projects.

\n

What should we expect if we work together? Tell me about your process.

\n

Typically, once a website project is discussed with a prospect, it will be scoped out and broken into different modules, pages and feature functionality so that it can be approved by the development team. The dev team will provide a number of hours for scope and that will be drafted into a proposal or quote.

Once the quote is accepted by the client, the kickoff meeting will be scheduled and the preliminary project kickoff worksheets and information requests will be sent to the client. Once the information is received, it will be reviewed internally and a kickoff call will be scheduled.

They will probably provide a timeline for development and when to expect design as well as how things will work once development begins. This process will differ between each agency, but you’ll want to get a timeline, understand your responsibilities and manage your expectations accordingly. Record calls or take detailed notes to refer back to in case the project becomes delayed.

\n

What is the QA process once a page is built? Do you test across devices and browsers?

\n

Two for one! While this may be two questions, it gives you more insight into what to ask when it comes to the QA process. QA stands for quality assurance, which refers to the rigorous testing period that takes place after a page or module is developed. For us that means testing all elements, links, checking information, testing responsiveness, browser compatibility testing, testing across multiple different devices and offering feedback to our design team.

Our agency uses Pastel for design feedback internally and with our clients. It’s a great tool for collaboration, especially when our development team and clients are spread across many remote locations.

\n

Related: HubSpot CMS Development Quality Assurance: Why We Love Pastel

\n

Understanding how your agency or developer approaches the review process is really important. We recently took on a project that came from a large agency who wasn’t taking the time to perform QA testing prior to delivering draft pages to the client and it was making things very difficult for them. Understanding how QA is handled in advance will give you a better idea for what to expect and an understanding of who is responsible for what along the way. Check out this blog to understand more about why website QA is so important in HubSpot CMS.

\n

 Will anything be hard-coded?

\n

There will be some aspects of your website that a developer must update and change, but those items should be minimal, particularly if you’re working within HubSpot CMS. You’ll want to ask this question to understand when you’ll need to contact your developer partner. Inside HubSpot CMS the days of needing to send information to your developer to update should be gone for the most part.

Most of your website elements, including headers, footers, CTA buttons, your blog, and other website content should easily be able to be updated from your HubSpot login. Understanding which elements require hard coding will help you plan better for updates and costs associated with making those updates.

\n

How will the revision process work?

\n

When not handled properly, revisions can cause so many delays in project launches. An experienced development agency will have strict parameters associated with website reviews and revisions on behalf of the client. They’ll clearly outline what is included in scope, and address how new features will be handled.

Frequently in the development process clients request additions to functionality on the back end or additional design elements to be implemented on the front end. Your developer will discuss these with you, how they impact the overall budget and whether they’re pre-launch updates or post-launch updates. They’ll also discuss how they’ll impact launch timelines.

Revisions during the development process will often have deadlines attached and typically these will need to be submitted by a single point of contact.

\n

How long after the process is completed will you support your work?

\n

For all projects in HubSpot CMS, we typically support bug fixes and revisions for one week after the project is launched. When we have long standing relationships with our clients or growth-driven design retainers, there is some flexibility here. You should understand your developer’s policy towards bug fixes and revisions, as it can sometimes be difficult to get developers to make updates and fixes once a certain amount of time has passed.

For the most part, a reputable HubSpot developer will be supportive of their work to a point. Many excellent developers have been taken advantage of when they have not taken the time to clearly communicate how long they’ll support their website projects after launch. Understanding these expectations in advance will help you be more proactive after launch and ensure that your developer is able to support your expectations once your project reaches the finish line.

We hope that these 6 questions give you more to think about when you’re interviewing prospective development agencies for your next project. The more questions you ask, the more you’ll understand about how your developer handles things and the more likely you are to match up with the perfect developer.

While it may seem cumbersome to have such a long list of questions, it’s much better to ask more questions than less. A well-established, experienced development agency will understand this and easily be able to answer any questions you have and address other concerns associated with your website.

\n

Be sure to check out Part 1 and Part 3!

\n

What has helped you in vetting developers during the interview process? Share your tips in the comments.

\n

\n

 

\n

Also check out: 
7 HubSpot CMS Developer Interview Questions to Ask: Part 1

","rss_summary":"

The most critical aspect of your entire HubSpot CMS project isn’t the day that you launch it, but the day you choose your HubSpot CMS developer. We’ve witnessed agencies being ghosted by their HubSpot developer, businesses that had to perform their own quality assurance testing despite contracting large agencies and so many other misadventures when it comes to HubSpot development over the years. We’ve lost projects to budget-conscious companies only for them to come back and tell us how paying less ended up costing them more in the long run.

We wish that we could be there to help you vet your HubSpot developer ourselves, because what is most important to us isn’t getting the work ourselves. What is most important to us is that amazing, beautiful projects are created on HubSpot CMS by gifted developers that allow marketers and business owners to really leverage the platform and meet their goals. Maybe it’s idealistic - but that’s what we’re really about.

We’re still a small shop and while we cannot take on every project that comes our way, we want you to have the tools at your disposal to make sure you ask the right questions to qualify the HubSpot CMS development partner that you’re vetting. While we’ve already taken the time to break down Part 1 of 6 HubSpot CMS developer interview questions, the list is long and we need to tell you 6 more…

\n","rss_body":"

The most critical aspect of your entire HubSpot CMS project isn’t the day that you launch it, but the day you choose your HubSpot CMS developer. We’ve witnessed agencies being ghosted by their HubSpot developer, businesses that had to perform their own quality assurance testing despite contracting large agencies and so many other misadventures when it comes to HubSpot development over the years. We’ve lost projects to budget-conscious companies only for them to come back and tell us how paying less ended up costing them more in the long run.

We wish that we could be there to help you vet your HubSpot developer ourselves, because what is most important to us isn’t getting the work ourselves. What is most important to us is that amazing, beautiful projects are created on HubSpot CMS by gifted developers that allow marketers and business owners to really leverage the platform and meet their goals. Maybe it’s idealistic - but that’s what we’re really about.

We’re still a small shop and while we cannot take on every project that comes our way, we want you to have the tools at your disposal to make sure you ask the right questions to qualify the HubSpot CMS development partner that you’re vetting. While we’ve already taken the time to break down Part 1 of 6 HubSpot CMS developer interview questions, the list is long and we need to tell you 6 more…

\n\n

Can you show me something you've completed recently that you're proud of?

\n

You’d be surprised how often, especially being an agency-focused development shop, we take on the development of designs that we don’t love. While we know better than to ever be order takers (everyone knows your website isn’t a sub sandwich), at the end of the day our recommendations may be hampered by budget or stubborn clients. There are some projects that we’ve completed that we’re proud of - but there are other projects that we championed from start to finish to deliver something truly amazing - and those are the ones that we want to show our prospects.

A qualified web development partner will not just be happy to show you his or her most prized projects, but they’ll be enthusiastic about it. An experienced development partner will have a lot of different projects in HubSpot CMS and be able to talk about the obstacles they overcame to create them. Showcasing work they’re proud of will tell you a lot about the agency or developer you’re selecting. You’ll want your developer to approach your project with the amount of passion they’ve shown to their favorite projects.

\n

What should we expect if we work together? Tell me about your process.

\n

Typically, once a website project is discussed with a prospect, it will be scoped out and broken into different modules, pages and feature functionality so that it can be approved by the development team. The dev team will provide a number of hours for scope and that will be drafted into a proposal or quote.

Once the quote is accepted by the client, the kickoff meeting will be scheduled and the preliminary project kickoff worksheets and information requests will be sent to the client. Once the information is received, it will be reviewed internally and a kickoff call will be scheduled.

They will probably provide a timeline for development and when to expect design as well as how things will work once development begins. This process will differ between each agency, but you’ll want to get a timeline, understand your responsibilities and manage your expectations accordingly. Record calls or take detailed notes to refer back to in case the project becomes delayed.

\n

What is the QA process once a page is built? Do you test across devices and browsers?

\n

Two for one! While this may be two questions, it gives you more insight into what to ask when it comes to the QA process. QA stands for quality assurance, which refers to the rigorous testing period that takes place after a page or module is developed. For us that means testing all elements, links, checking information, testing responsiveness, browser compatibility testing, testing across multiple different devices and offering feedback to our design team.

Our agency uses Pastel for design feedback internally and with our clients. It’s a great tool for collaboration, especially when our development team and clients are spread across many remote locations.

\n

Related: HubSpot CMS Development Quality Assurance: Why We Love Pastel

\n

Understanding how your agency or developer approaches the review process is really important. We recently took on a project that came from a large agency who wasn’t taking the time to perform QA testing prior to delivering draft pages to the client and it was making things very difficult for them. Understanding how QA is handled in advance will give you a better idea for what to expect and an understanding of who is responsible for what along the way. Check out this blog to understand more about why website QA is so important in HubSpot CMS.

\n

 Will anything be hard-coded?

\n

There will be some aspects of your website that a developer must update and change, but those items should be minimal, particularly if you’re working within HubSpot CMS. You’ll want to ask this question to understand when you’ll need to contact your developer partner. Inside HubSpot CMS the days of needing to send information to your developer to update should be gone for the most part.

Most of your website elements, including headers, footers, CTA buttons, your blog, and other website content should easily be able to be updated from your HubSpot login. Understanding which elements require hard coding will help you plan better for updates and costs associated with making those updates.

\n

How will the revision process work?

\n

When not handled properly, revisions can cause so many delays in project launches. An experienced development agency will have strict parameters associated with website reviews and revisions on behalf of the client. They’ll clearly outline what is included in scope, and address how new features will be handled.

Frequently in the development process clients request additions to functionality on the back end or additional design elements to be implemented on the front end. Your developer will discuss these with you, how they impact the overall budget and whether they’re pre-launch updates or post-launch updates. They’ll also discuss how they’ll impact launch timelines.

Revisions during the development process will often have deadlines attached and typically these will need to be submitted by a single point of contact.

\n

How long after the process is completed will you support your work?

\n

For all projects in HubSpot CMS, we typically support bug fixes and revisions for one week after the project is launched. When we have long standing relationships with our clients or growth-driven design retainers, there is some flexibility here. You should understand your developer’s policy towards bug fixes and revisions, as it can sometimes be difficult to get developers to make updates and fixes once a certain amount of time has passed.

For the most part, a reputable HubSpot developer will be supportive of their work to a point. Many excellent developers have been taken advantage of when they have not taken the time to clearly communicate how long they’ll support their website projects after launch. Understanding these expectations in advance will help you be more proactive after launch and ensure that your developer is able to support your expectations once your project reaches the finish line.

We hope that these 6 questions give you more to think about when you’re interviewing prospective development agencies for your next project. The more questions you ask, the more you’ll understand about how your developer handles things and the more likely you are to match up with the perfect developer.

While it may seem cumbersome to have such a long list of questions, it’s much better to ask more questions than less. A well-established, experienced development agency will understand this and easily be able to answer any questions you have and address other concerns associated with your website.

\n

Be sure to check out Part 1 and Part 3!

\n

What has helped you in vetting developers during the interview process? Share your tips in the comments.

\n

\n

 

\n

Also check out: 
7 HubSpot CMS Developer Interview Questions to Ask: Part 1

","tag_ids":[62234989205,62770442823,80453663900],"topic_ids":[62234989205,62770442823,80453663900],"post_summary":"

The most critical aspect of your entire HubSpot CMS project isn’t the day that you launch it, but the day you choose your HubSpot CMS developer. We’ve witnessed agencies being ghosted by their HubSpot developer, businesses that had to perform their own quality assurance testing despite contracting large agencies and so many other misadventures when it comes to HubSpot development over the years. We’ve lost projects to budget-conscious companies only for them to come back and tell us how paying less ended up costing them more in the long run.

We wish that we could be there to help you vet your HubSpot developer ourselves, because what is most important to us isn’t getting the work ourselves. What is most important to us is that amazing, beautiful projects are created on HubSpot CMS by gifted developers that allow marketers and business owners to really leverage the platform and meet their goals. Maybe it’s idealistic - but that’s what we’re really about.

We’re still a small shop and while we cannot take on every project that comes our way, we want you to have the tools at your disposal to make sure you ask the right questions to qualify the HubSpot CMS development partner that you’re vetting. While we’ve already taken the time to break down Part 1 of 6 HubSpot CMS developer interview questions, the list is long and we need to tell you 6 more…

\n","blog_post_schedule_task_uid":null,"blog_publish_to_social_media_task":"DONE_NOT_SENT","blog_publish_instant_email_task_uid":null,"blog_publish_instant_email_campaign_id":null,"blog_publish_instant_email_retry_count":null,"keywords":[],"head_html":null,"footer_html":null,"attached_stylesheets":[],"enable_domain_stylesheets":null,"include_default_custom_css":null,"meta_description":"The process that your HubSpot CMS developer uses is extremely important. Check out Part 2 of Interview Questions for your web developers:","meta_keywords":null,"layout_sections":{},"past_mab_experiment_ids":[],"deleted_by":null,"featured_image_alt_text":"","enable_layout_stylesheets":null,"tweet":null,"tweet_at":null,"campaign_name":null,"campaign_utm":null,"tweet_immediately":false,"publish_immediately":true,"security_state":"NONE","scheduled_update_date":0,"placement_guids":[],"property_for_dynamic_page_title":null,"property_for_dynamic_page_slug":null,"property_for_dynamic_page_meta_description":null,"property_for_dynamic_page_featured_image":null,"property_for_dynamic_page_canonical_url":null,"preview_image_src":null,"legacy_blog_tabid":null,"legacy_post_guid":null,"performable_variation_letter":null,"style_override_id":null,"has_user_changes":true,"css":{},"css_text":"","unpublished_at":0,"published_by_id":61310730,"allowed_slug_conflict":false,"ai_features":null,"link_rel_canonical_url":"","page_redirected":false,"page_expiry_enabled":null,"page_expiry_date":null,"page_expiry_redirect_id":null,"page_expiry_redirect_url":null,"deleted_by_id":null,"state_when_deleted":null,"cloned_from":null,"staged_from":null,"personas":[],"compose_body":null,"featured_image":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-interview%20questions.png","featured_image_width":1080,"featured_image_height":1080,"publish_timezone_offset":null,"theme_settings_values":null,"password":null,"header":null,"published_at":1722384465749,"last_edit_session_id":null,"last_edit_update_id":null,"created_by_agent":null},"metaDescription":"The process that your HubSpot CMS developer uses is extremely important. Check out Part 2 of Interview Questions for your web developers:","metaKeywords":null,"name":"6 More HubSpot CMS Developer Interview Questions Part 2: The Process","nextPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/63.png","nextPostFeaturedImageAltText":"hubspot cms developer","nextPostName":"7 HubSpot CMS Developer Interview Questions to Ask: Part 1","nextPostSlug":"blogs/7-hubspot-cms-developer-interview-questions-to-ask-part-1","pageExpiryDate":null,"pageExpiryEnabled":null,"pageExpiryRedirectId":null,"pageExpiryRedirectUrl":null,"pageRedirected":false,"pageTitle":"6 More HubSpot CMS Developer Interview Questions Part 2: The Process","parentBlog":{"absoluteUrl":"https://deckerdevs.com/blogs","allowComments":true,"ampBodyColor":"#404040","ampBodyFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampBodyFontSize":"18","ampCustomCss":"","ampHeaderBackgroundColor":"#ffffff","ampHeaderColor":"#1e1e1e","ampHeaderFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampHeaderFontSize":"36","ampLinkColor":"#416bb3","ampLogoAlt":"","ampLogoHeight":0,"ampLogoSrc":"","ampLogoWidth":0,"analyticsPageId":62179259185,"attachedStylesheets":[],"audienceAccess":"PUBLIC","businessUnitId":null,"captchaAfterDays":7,"captchaAlways":false,"categoryId":3,"cdnPurgeEmbargoTime":null,"closeCommentsOlder":0,"commentDateFormat":"medium","commentFormGuid":"cb653aa1-3db4-4167-9b59-744c46d49682","commentMaxThreadDepth":3,"commentModeration":false,"commentNotificationEmails":["nicholas@deckerdevs.com","jessica@deckerdevs.com"],"commentShouldCreateContact":true,"commentVerificationText":"Thanks for participating in this conversation! We look forward to responding and to assisting where we can","cosObjectType":"BLOG","created":1639786189589,"createdDateTime":1639786189589,"dailyNotificationEmailId":null,"dateFormattingLanguage":null,"defaultGroupStyleId":"","defaultNotificationFromName":"","defaultNotificationReplyTo":"","deletedAt":0,"description":"rev up your hubspot system to the max! deckerdevs' turbo-charged blog is your ultimate guide to harnessing the full potential of hubspot development. unleash the marketing magic with ingenious tips, tricks, and hacks. get ready to level up your hubspot game!","domain":"","domainWhenPublished":"deckerdevs.com","emailApiSubscriptionId":null,"enableGoogleAmpOutput":false,"enableSocialAutoPublishing":false,"generateJsonLdEnabled":true,"header":null,"htmlFooter":"","htmlFooterIsShared":true,"htmlHead":"","htmlHeadIsShared":true,"htmlKeywords":[],"htmlTitle":"deckerdevs thought nuggets","id":62179259185,"ilsSubscriptionListsByType":{},"instantNotificationEmailId":null,"itemLayoutId":null,"itemTemplateIsShared":false,"itemTemplatePath":"deckerdevs-theme/templates/blog-content.html","label":"deckerdevs live blog","language":"en","legacyGuid":null,"legacyModuleId":null,"legacyTabId":null,"listingLayoutId":null,"listingPageId":62179259186,"listingTemplatePath":"","liveDomain":"deckerdevs.com","monthFilterFormat":"MMMM yyyy","monthlyNotificationEmailId":null,"name":"deckerdevs live blog","parentBlogUpdateTaskId":null,"portalId":6534445,"postHtmlFooter":"","postHtmlHead":"","postsPerListingPage":9,"postsPerRssFeed":10,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publicTitle":"thought nuggets","publishDateFormat":"medium","resolvedDomain":"deckerdevs.com","rootUrl":"https://deckerdevs.com/blogs","rssCustomFeed":null,"rssDescription":null,"rssItemFooter":null,"rssItemHeader":null,"settingsOverrides":{"itemLayoutId":false,"itemTemplatePath":false,"itemTemplateIsShared":false,"listingLayoutId":false,"listingTemplatePath":false,"postsPerListingPage":false,"showSummaryInListing":false,"useFeaturedImageInSummary":false,"htmlHead":false,"postHtmlHead":false,"htmlHeadIsShared":false,"htmlFooter":false,"listingPageHtmlFooter":false,"postHtmlFooter":false,"htmlFooterIsShared":false,"attachedStylesheets":false,"postsPerRssFeed":false,"showSummaryInRss":false,"showSummaryInEmails":false,"showSummariesInEmails":false,"allowComments":false,"commentShouldCreateContact":false,"commentModeration":false,"closeCommentsOlder":false,"commentNotificationEmails":false,"commentMaxThreadDepth":false,"commentVerificationText":false,"socialAccountTwitter":false,"showSocialLinkTwitter":false,"showSocialLinkLinkedin":false,"showSocialLinkFacebook":false,"enableGoogleAmpOutput":false,"ampLogoSrc":false,"ampLogoHeight":false,"ampLogoWidth":false,"ampLogoAlt":false,"ampHeaderFont":false,"ampHeaderFontSize":false,"ampHeaderColor":false,"ampHeaderBackgroundColor":false,"ampBodyFont":false,"ampBodyFontSize":false,"ampBodyColor":false,"ampLinkColor":false,"generateJsonLdEnabled":false},"showSocialLinkFacebook":true,"showSocialLinkLinkedin":true,"showSocialLinkTwitter":true,"showSummaryInEmails":true,"showSummaryInListing":true,"showSummaryInRss":true,"siteId":null,"slug":"blogs","socialAccountTwitter":"","state":null,"subscriptionContactsProperty":null,"subscriptionEmailType":null,"subscriptionFormGuid":null,"subscriptionListsByType":{},"title":null,"translatedFromId":null,"translations":{},"updated":1712344124471,"updatedDateTime":1712344124471,"urlBase":"deckerdevs.com/blogs","urlSegments":{"all":"all","archive":"archive","author":"author","page":"page","tag":"tag"},"useFeaturedImageInSummary":true,"usesDefaultTemplate":false,"weeklyNotificationEmailId":null},"password":null,"pastMabExperimentIds":[],"performableGuid":null,"performableVariationLetter":null,"personas":[],"placementGuids":[],"portableKey":null,"portalId":6534445,"position":null,"postBody":"

The most critical aspect of your entire HubSpot CMS project isn’t the day that you launch it, but the day you choose your HubSpot CMS developer. We’ve witnessed agencies being ghosted by their HubSpot developer, businesses that had to perform their own quality assurance testing despite contracting large agencies and so many other misadventures when it comes to HubSpot development over the years. We’ve lost projects to budget-conscious companies only for them to come back and tell us how paying less ended up costing them more in the long run.

We wish that we could be there to help you vet your HubSpot developer ourselves, because what is most important to us isn’t getting the work ourselves. What is most important to us is that amazing, beautiful projects are created on HubSpot CMS by gifted developers that allow marketers and business owners to really leverage the platform and meet their goals. Maybe it’s idealistic - but that’s what we’re really about.

We’re still a small shop and while we cannot take on every project that comes our way, we want you to have the tools at your disposal to make sure you ask the right questions to qualify the HubSpot CMS development partner that you’re vetting. While we’ve already taken the time to break down Part 1 of 6 HubSpot CMS developer interview questions, the list is long and we need to tell you 6 more…

\n\n

Can you show me something you've completed recently that you're proud of?

\n

You’d be surprised how often, especially being an agency-focused development shop, we take on the development of designs that we don’t love. While we know better than to ever be order takers (everyone knows your website isn’t a sub sandwich), at the end of the day our recommendations may be hampered by budget or stubborn clients. There are some projects that we’ve completed that we’re proud of - but there are other projects that we championed from start to finish to deliver something truly amazing - and those are the ones that we want to show our prospects.

A qualified web development partner will not just be happy to show you his or her most prized projects, but they’ll be enthusiastic about it. An experienced development partner will have a lot of different projects in HubSpot CMS and be able to talk about the obstacles they overcame to create them. Showcasing work they’re proud of will tell you a lot about the agency or developer you’re selecting. You’ll want your developer to approach your project with the amount of passion they’ve shown to their favorite projects.

\n

What should we expect if we work together? Tell me about your process.

\n

Typically, once a website project is discussed with a prospect, it will be scoped out and broken into different modules, pages and feature functionality so that it can be approved by the development team. The dev team will provide a number of hours for scope and that will be drafted into a proposal or quote.

Once the quote is accepted by the client, the kickoff meeting will be scheduled and the preliminary project kickoff worksheets and information requests will be sent to the client. Once the information is received, it will be reviewed internally and a kickoff call will be scheduled.

They will probably provide a timeline for development and when to expect design as well as how things will work once development begins. This process will differ between each agency, but you’ll want to get a timeline, understand your responsibilities and manage your expectations accordingly. Record calls or take detailed notes to refer back to in case the project becomes delayed.

\n

What is the QA process once a page is built? Do you test across devices and browsers?

\n

Two for one! While this may be two questions, it gives you more insight into what to ask when it comes to the QA process. QA stands for quality assurance, which refers to the rigorous testing period that takes place after a page or module is developed. For us that means testing all elements, links, checking information, testing responsiveness, browser compatibility testing, testing across multiple different devices and offering feedback to our design team.

Our agency uses Pastel for design feedback internally and with our clients. It’s a great tool for collaboration, especially when our development team and clients are spread across many remote locations.

\n

Related: HubSpot CMS Development Quality Assurance: Why We Love Pastel

\n

Understanding how your agency or developer approaches the review process is really important. We recently took on a project that came from a large agency who wasn’t taking the time to perform QA testing prior to delivering draft pages to the client and it was making things very difficult for them. Understanding how QA is handled in advance will give you a better idea for what to expect and an understanding of who is responsible for what along the way. Check out this blog to understand more about why website QA is so important in HubSpot CMS.

\n

 Will anything be hard-coded?

\n

There will be some aspects of your website that a developer must update and change, but those items should be minimal, particularly if you’re working within HubSpot CMS. You’ll want to ask this question to understand when you’ll need to contact your developer partner. Inside HubSpot CMS the days of needing to send information to your developer to update should be gone for the most part.

Most of your website elements, including headers, footers, CTA buttons, your blog, and other website content should easily be able to be updated from your HubSpot login. Understanding which elements require hard coding will help you plan better for updates and costs associated with making those updates.

\n

How will the revision process work?

\n

When not handled properly, revisions can cause so many delays in project launches. An experienced development agency will have strict parameters associated with website reviews and revisions on behalf of the client. They’ll clearly outline what is included in scope, and address how new features will be handled.

Frequently in the development process clients request additions to functionality on the back end or additional design elements to be implemented on the front end. Your developer will discuss these with you, how they impact the overall budget and whether they’re pre-launch updates or post-launch updates. They’ll also discuss how they’ll impact launch timelines.

Revisions during the development process will often have deadlines attached and typically these will need to be submitted by a single point of contact.

\n

How long after the process is completed will you support your work?

\n

For all projects in HubSpot CMS, we typically support bug fixes and revisions for one week after the project is launched. When we have long standing relationships with our clients or growth-driven design retainers, there is some flexibility here. You should understand your developer’s policy towards bug fixes and revisions, as it can sometimes be difficult to get developers to make updates and fixes once a certain amount of time has passed.

For the most part, a reputable HubSpot developer will be supportive of their work to a point. Many excellent developers have been taken advantage of when they have not taken the time to clearly communicate how long they’ll support their website projects after launch. Understanding these expectations in advance will help you be more proactive after launch and ensure that your developer is able to support your expectations once your project reaches the finish line.

We hope that these 6 questions give you more to think about when you’re interviewing prospective development agencies for your next project. The more questions you ask, the more you’ll understand about how your developer handles things and the more likely you are to match up with the perfect developer.

While it may seem cumbersome to have such a long list of questions, it’s much better to ask more questions than less. A well-established, experienced development agency will understand this and easily be able to answer any questions you have and address other concerns associated with your website.

\n

Be sure to check out Part 1 and Part 3!

\n

What has helped you in vetting developers during the interview process? Share your tips in the comments.

\n

\n

 

\n

Also check out: 
7 HubSpot CMS Developer Interview Questions to Ask: Part 1

","postBodyRss":"

The most critical aspect of your entire HubSpot CMS project isn’t the day that you launch it, but the day you choose your HubSpot CMS developer. We’ve witnessed agencies being ghosted by their HubSpot developer, businesses that had to perform their own quality assurance testing despite contracting large agencies and so many other misadventures when it comes to HubSpot development over the years. We’ve lost projects to budget-conscious companies only for them to come back and tell us how paying less ended up costing them more in the long run.

We wish that we could be there to help you vet your HubSpot developer ourselves, because what is most important to us isn’t getting the work ourselves. What is most important to us is that amazing, beautiful projects are created on HubSpot CMS by gifted developers that allow marketers and business owners to really leverage the platform and meet their goals. Maybe it’s idealistic - but that’s what we’re really about.

We’re still a small shop and while we cannot take on every project that comes our way, we want you to have the tools at your disposal to make sure you ask the right questions to qualify the HubSpot CMS development partner that you’re vetting. While we’ve already taken the time to break down Part 1 of 6 HubSpot CMS developer interview questions, the list is long and we need to tell you 6 more…

\n\n

Can you show me something you've completed recently that you're proud of?

\n

You’d be surprised how often, especially being an agency-focused development shop, we take on the development of designs that we don’t love. While we know better than to ever be order takers (everyone knows your website isn’t a sub sandwich), at the end of the day our recommendations may be hampered by budget or stubborn clients. There are some projects that we’ve completed that we’re proud of - but there are other projects that we championed from start to finish to deliver something truly amazing - and those are the ones that we want to show our prospects.

A qualified web development partner will not just be happy to show you his or her most prized projects, but they’ll be enthusiastic about it. An experienced development partner will have a lot of different projects in HubSpot CMS and be able to talk about the obstacles they overcame to create them. Showcasing work they’re proud of will tell you a lot about the agency or developer you’re selecting. You’ll want your developer to approach your project with the amount of passion they’ve shown to their favorite projects.

\n

What should we expect if we work together? Tell me about your process.

\n

Typically, once a website project is discussed with a prospect, it will be scoped out and broken into different modules, pages and feature functionality so that it can be approved by the development team. The dev team will provide a number of hours for scope and that will be drafted into a proposal or quote.

Once the quote is accepted by the client, the kickoff meeting will be scheduled and the preliminary project kickoff worksheets and information requests will be sent to the client. Once the information is received, it will be reviewed internally and a kickoff call will be scheduled.

They will probably provide a timeline for development and when to expect design as well as how things will work once development begins. This process will differ between each agency, but you’ll want to get a timeline, understand your responsibilities and manage your expectations accordingly. Record calls or take detailed notes to refer back to in case the project becomes delayed.

\n

What is the QA process once a page is built? Do you test across devices and browsers?

\n

Two for one! While this may be two questions, it gives you more insight into what to ask when it comes to the QA process. QA stands for quality assurance, which refers to the rigorous testing period that takes place after a page or module is developed. For us that means testing all elements, links, checking information, testing responsiveness, browser compatibility testing, testing across multiple different devices and offering feedback to our design team.

Our agency uses Pastel for design feedback internally and with our clients. It’s a great tool for collaboration, especially when our development team and clients are spread across many remote locations.

\n

Related: HubSpot CMS Development Quality Assurance: Why We Love Pastel

\n

Understanding how your agency or developer approaches the review process is really important. We recently took on a project that came from a large agency who wasn’t taking the time to perform QA testing prior to delivering draft pages to the client and it was making things very difficult for them. Understanding how QA is handled in advance will give you a better idea for what to expect and an understanding of who is responsible for what along the way. Check out this blog to understand more about why website QA is so important in HubSpot CMS.

\n

 Will anything be hard-coded?

\n

There will be some aspects of your website that a developer must update and change, but those items should be minimal, particularly if you’re working within HubSpot CMS. You’ll want to ask this question to understand when you’ll need to contact your developer partner. Inside HubSpot CMS the days of needing to send information to your developer to update should be gone for the most part.

Most of your website elements, including headers, footers, CTA buttons, your blog, and other website content should easily be able to be updated from your HubSpot login. Understanding which elements require hard coding will help you plan better for updates and costs associated with making those updates.

\n

How will the revision process work?

\n

When not handled properly, revisions can cause so many delays in project launches. An experienced development agency will have strict parameters associated with website reviews and revisions on behalf of the client. They’ll clearly outline what is included in scope, and address how new features will be handled.

Frequently in the development process clients request additions to functionality on the back end or additional design elements to be implemented on the front end. Your developer will discuss these with you, how they impact the overall budget and whether they’re pre-launch updates or post-launch updates. They’ll also discuss how they’ll impact launch timelines.

Revisions during the development process will often have deadlines attached and typically these will need to be submitted by a single point of contact.

\n

How long after the process is completed will you support your work?

\n

For all projects in HubSpot CMS, we typically support bug fixes and revisions for one week after the project is launched. When we have long standing relationships with our clients or growth-driven design retainers, there is some flexibility here. You should understand your developer’s policy towards bug fixes and revisions, as it can sometimes be difficult to get developers to make updates and fixes once a certain amount of time has passed.

For the most part, a reputable HubSpot developer will be supportive of their work to a point. Many excellent developers have been taken advantage of when they have not taken the time to clearly communicate how long they’ll support their website projects after launch. Understanding these expectations in advance will help you be more proactive after launch and ensure that your developer is able to support your expectations once your project reaches the finish line.

We hope that these 6 questions give you more to think about when you’re interviewing prospective development agencies for your next project. The more questions you ask, the more you’ll understand about how your developer handles things and the more likely you are to match up with the perfect developer.

While it may seem cumbersome to have such a long list of questions, it’s much better to ask more questions than less. A well-established, experienced development agency will understand this and easily be able to answer any questions you have and address other concerns associated with your website.

\n

Be sure to check out Part 1 and Part 3!

\n

What has helped you in vetting developers during the interview process? Share your tips in the comments.

\n

\n

 

\n

Also check out: 
7 HubSpot CMS Developer Interview Questions to Ask: Part 1

","postEmailContent":"

The most critical aspect of your entire HubSpot CMS project isn’t the day that you launch it, but the day you choose your HubSpot CMS developer. We’ve witnessed agencies being ghosted by their HubSpot developer, businesses that had to perform their own quality assurance testing despite contracting large agencies and so many other misadventures when it comes to HubSpot development over the years. We’ve lost projects to budget-conscious companies only for them to come back and tell us how paying less ended up costing them more in the long run.

We wish that we could be there to help you vet your HubSpot developer ourselves, because what is most important to us isn’t getting the work ourselves. What is most important to us is that amazing, beautiful projects are created on HubSpot CMS by gifted developers that allow marketers and business owners to really leverage the platform and meet their goals. Maybe it’s idealistic - but that’s what we’re really about.

We’re still a small shop and while we cannot take on every project that comes our way, we want you to have the tools at your disposal to make sure you ask the right questions to qualify the HubSpot CMS development partner that you’re vetting. While we’ve already taken the time to break down Part 1 of 6 HubSpot CMS developer interview questions, the list is long and we need to tell you 6 more…

","postFeaturedImageIfEnabled":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-interview%20questions.png","postListContent":"

The most critical aspect of your entire HubSpot CMS project isn’t the day that you launch it, but the day you choose your HubSpot CMS developer. We’ve witnessed agencies being ghosted by their HubSpot developer, businesses that had to perform their own quality assurance testing despite contracting large agencies and so many other misadventures when it comes to HubSpot development over the years. We’ve lost projects to budget-conscious companies only for them to come back and tell us how paying less ended up costing them more in the long run.

We wish that we could be there to help you vet your HubSpot developer ourselves, because what is most important to us isn’t getting the work ourselves. What is most important to us is that amazing, beautiful projects are created on HubSpot CMS by gifted developers that allow marketers and business owners to really leverage the platform and meet their goals. Maybe it’s idealistic - but that’s what we’re really about.

We’re still a small shop and while we cannot take on every project that comes our way, we want you to have the tools at your disposal to make sure you ask the right questions to qualify the HubSpot CMS development partner that you’re vetting. While we’ve already taken the time to break down Part 1 of 6 HubSpot CMS developer interview questions, the list is long and we need to tell you 6 more…

","postListSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-interview%20questions.png","postRssContent":"

The most critical aspect of your entire HubSpot CMS project isn’t the day that you launch it, but the day you choose your HubSpot CMS developer. We’ve witnessed agencies being ghosted by their HubSpot developer, businesses that had to perform their own quality assurance testing despite contracting large agencies and so many other misadventures when it comes to HubSpot development over the years. We’ve lost projects to budget-conscious companies only for them to come back and tell us how paying less ended up costing them more in the long run.

We wish that we could be there to help you vet your HubSpot developer ourselves, because what is most important to us isn’t getting the work ourselves. What is most important to us is that amazing, beautiful projects are created on HubSpot CMS by gifted developers that allow marketers and business owners to really leverage the platform and meet their goals. Maybe it’s idealistic - but that’s what we’re really about.

We’re still a small shop and while we cannot take on every project that comes our way, we want you to have the tools at your disposal to make sure you ask the right questions to qualify the HubSpot CMS development partner that you’re vetting. While we’ve already taken the time to break down Part 1 of 6 HubSpot CMS developer interview questions, the list is long and we need to tell you 6 more…

","postRssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-interview%20questions.png","postSummary":"

The most critical aspect of your entire HubSpot CMS project isn’t the day that you launch it, but the day you choose your HubSpot CMS developer. We’ve witnessed agencies being ghosted by their HubSpot developer, businesses that had to perform their own quality assurance testing despite contracting large agencies and so many other misadventures when it comes to HubSpot development over the years. We’ve lost projects to budget-conscious companies only for them to come back and tell us how paying less ended up costing them more in the long run.

We wish that we could be there to help you vet your HubSpot developer ourselves, because what is most important to us isn’t getting the work ourselves. What is most important to us is that amazing, beautiful projects are created on HubSpot CMS by gifted developers that allow marketers and business owners to really leverage the platform and meet their goals. Maybe it’s idealistic - but that’s what we’re really about.

We’re still a small shop and while we cannot take on every project that comes our way, we want you to have the tools at your disposal to make sure you ask the right questions to qualify the HubSpot CMS development partner that you’re vetting. While we’ve already taken the time to break down Part 1 of 6 HubSpot CMS developer interview questions, the list is long and we need to tell you 6 more…

\n","postSummaryRss":"

The most critical aspect of your entire HubSpot CMS project isn’t the day that you launch it, but the day you choose your HubSpot CMS developer. We’ve witnessed agencies being ghosted by their HubSpot developer, businesses that had to perform their own quality assurance testing despite contracting large agencies and so many other misadventures when it comes to HubSpot development over the years. We’ve lost projects to budget-conscious companies only for them to come back and tell us how paying less ended up costing them more in the long run.

We wish that we could be there to help you vet your HubSpot developer ourselves, because what is most important to us isn’t getting the work ourselves. What is most important to us is that amazing, beautiful projects are created on HubSpot CMS by gifted developers that allow marketers and business owners to really leverage the platform and meet their goals. Maybe it’s idealistic - but that’s what we’re really about.

We’re still a small shop and while we cannot take on every project that comes our way, we want you to have the tools at your disposal to make sure you ask the right questions to qualify the HubSpot CMS development partner that you’re vetting. While we’ve already taken the time to break down Part 1 of 6 HubSpot CMS developer interview questions, the list is long and we need to tell you 6 more…

","postTemplate":"deckerdevs-theme/templates/blog-content.html","previewImageSrc":null,"previewKey":"fkxNsxHw","previousPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/job-interview-memes-1-5d14a7ea1163a__700.jpeg","previousPostFeaturedImageAltText":"hubspot interview","previousPostName":"6 Questions to Ask Your HubSpot CMS Developer: Part 3","previousPostSlug":"blogs/6-questions-to-ask-your-hubspot-cms-developer-part-3","processingStatus":"PUBLISHED","propertyForDynamicPageCanonicalUrl":null,"propertyForDynamicPageFeaturedImage":null,"propertyForDynamicPageMetaDescription":null,"propertyForDynamicPageSlug":null,"propertyForDynamicPageTitle":null,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publishDate":1661183901000,"publishDateLocalTime":1661183901000,"publishDateLocalized":{"date":1661183901000,"format":"medium","language":null},"publishImmediately":true,"publishTimezoneOffset":null,"publishedAt":1722384465749,"publishedByEmail":null,"publishedById":61310730,"publishedByName":null,"publishedUrl":"https://deckerdevs.com/blogs/6-more-hubspot-cms-developer-interview-questions-part-2-the-process","resolvedDomain":"deckerdevs.com","resolvedLanguage":null,"rssBody":"

The most critical aspect of your entire HubSpot CMS project isn’t the day that you launch it, but the day you choose your HubSpot CMS developer. We’ve witnessed agencies being ghosted by their HubSpot developer, businesses that had to perform their own quality assurance testing despite contracting large agencies and so many other misadventures when it comes to HubSpot development over the years. We’ve lost projects to budget-conscious companies only for them to come back and tell us how paying less ended up costing them more in the long run.

We wish that we could be there to help you vet your HubSpot developer ourselves, because what is most important to us isn’t getting the work ourselves. What is most important to us is that amazing, beautiful projects are created on HubSpot CMS by gifted developers that allow marketers and business owners to really leverage the platform and meet their goals. Maybe it’s idealistic - but that’s what we’re really about.

We’re still a small shop and while we cannot take on every project that comes our way, we want you to have the tools at your disposal to make sure you ask the right questions to qualify the HubSpot CMS development partner that you’re vetting. While we’ve already taken the time to break down Part 1 of 6 HubSpot CMS developer interview questions, the list is long and we need to tell you 6 more…

\n\n

Can you show me something you've completed recently that you're proud of?

\n

You’d be surprised how often, especially being an agency-focused development shop, we take on the development of designs that we don’t love. While we know better than to ever be order takers (everyone knows your website isn’t a sub sandwich), at the end of the day our recommendations may be hampered by budget or stubborn clients. There are some projects that we’ve completed that we’re proud of - but there are other projects that we championed from start to finish to deliver something truly amazing - and those are the ones that we want to show our prospects.

A qualified web development partner will not just be happy to show you his or her most prized projects, but they’ll be enthusiastic about it. An experienced development partner will have a lot of different projects in HubSpot CMS and be able to talk about the obstacles they overcame to create them. Showcasing work they’re proud of will tell you a lot about the agency or developer you’re selecting. You’ll want your developer to approach your project with the amount of passion they’ve shown to their favorite projects.

\n

What should we expect if we work together? Tell me about your process.

\n

Typically, once a website project is discussed with a prospect, it will be scoped out and broken into different modules, pages and feature functionality so that it can be approved by the development team. The dev team will provide a number of hours for scope and that will be drafted into a proposal or quote.

Once the quote is accepted by the client, the kickoff meeting will be scheduled and the preliminary project kickoff worksheets and information requests will be sent to the client. Once the information is received, it will be reviewed internally and a kickoff call will be scheduled.

They will probably provide a timeline for development and when to expect design as well as how things will work once development begins. This process will differ between each agency, but you’ll want to get a timeline, understand your responsibilities and manage your expectations accordingly. Record calls or take detailed notes to refer back to in case the project becomes delayed.

\n

What is the QA process once a page is built? Do you test across devices and browsers?

\n

Two for one! While this may be two questions, it gives you more insight into what to ask when it comes to the QA process. QA stands for quality assurance, which refers to the rigorous testing period that takes place after a page or module is developed. For us that means testing all elements, links, checking information, testing responsiveness, browser compatibility testing, testing across multiple different devices and offering feedback to our design team.

Our agency uses Pastel for design feedback internally and with our clients. It’s a great tool for collaboration, especially when our development team and clients are spread across many remote locations.

\n

Related: HubSpot CMS Development Quality Assurance: Why We Love Pastel

\n

Understanding how your agency or developer approaches the review process is really important. We recently took on a project that came from a large agency who wasn’t taking the time to perform QA testing prior to delivering draft pages to the client and it was making things very difficult for them. Understanding how QA is handled in advance will give you a better idea for what to expect and an understanding of who is responsible for what along the way. Check out this blog to understand more about why website QA is so important in HubSpot CMS.

\n

 Will anything be hard-coded?

\n

There will be some aspects of your website that a developer must update and change, but those items should be minimal, particularly if you’re working within HubSpot CMS. You’ll want to ask this question to understand when you’ll need to contact your developer partner. Inside HubSpot CMS the days of needing to send information to your developer to update should be gone for the most part.

Most of your website elements, including headers, footers, CTA buttons, your blog, and other website content should easily be able to be updated from your HubSpot login. Understanding which elements require hard coding will help you plan better for updates and costs associated with making those updates.

\n

How will the revision process work?

\n

When not handled properly, revisions can cause so many delays in project launches. An experienced development agency will have strict parameters associated with website reviews and revisions on behalf of the client. They’ll clearly outline what is included in scope, and address how new features will be handled.

Frequently in the development process clients request additions to functionality on the back end or additional design elements to be implemented on the front end. Your developer will discuss these with you, how they impact the overall budget and whether they’re pre-launch updates or post-launch updates. They’ll also discuss how they’ll impact launch timelines.

Revisions during the development process will often have deadlines attached and typically these will need to be submitted by a single point of contact.

\n

How long after the process is completed will you support your work?

\n

For all projects in HubSpot CMS, we typically support bug fixes and revisions for one week after the project is launched. When we have long standing relationships with our clients or growth-driven design retainers, there is some flexibility here. You should understand your developer’s policy towards bug fixes and revisions, as it can sometimes be difficult to get developers to make updates and fixes once a certain amount of time has passed.

For the most part, a reputable HubSpot developer will be supportive of their work to a point. Many excellent developers have been taken advantage of when they have not taken the time to clearly communicate how long they’ll support their website projects after launch. Understanding these expectations in advance will help you be more proactive after launch and ensure that your developer is able to support your expectations once your project reaches the finish line.

We hope that these 6 questions give you more to think about when you’re interviewing prospective development agencies for your next project. The more questions you ask, the more you’ll understand about how your developer handles things and the more likely you are to match up with the perfect developer.

While it may seem cumbersome to have such a long list of questions, it’s much better to ask more questions than less. A well-established, experienced development agency will understand this and easily be able to answer any questions you have and address other concerns associated with your website.

\n

Be sure to check out Part 1 and Part 3!

\n

What has helped you in vetting developers during the interview process? Share your tips in the comments.

\n

\n

 

\n

Also check out: 
7 HubSpot CMS Developer Interview Questions to Ask: Part 1

","rssSummary":"

The most critical aspect of your entire HubSpot CMS project isn’t the day that you launch it, but the day you choose your HubSpot CMS developer. We’ve witnessed agencies being ghosted by their HubSpot developer, businesses that had to perform their own quality assurance testing despite contracting large agencies and so many other misadventures when it comes to HubSpot development over the years. We’ve lost projects to budget-conscious companies only for them to come back and tell us how paying less ended up costing them more in the long run.

We wish that we could be there to help you vet your HubSpot developer ourselves, because what is most important to us isn’t getting the work ourselves. What is most important to us is that amazing, beautiful projects are created on HubSpot CMS by gifted developers that allow marketers and business owners to really leverage the platform and meet their goals. Maybe it’s idealistic - but that’s what we’re really about.

We’re still a small shop and while we cannot take on every project that comes our way, we want you to have the tools at your disposal to make sure you ask the right questions to qualify the HubSpot CMS development partner that you’re vetting. While we’ve already taken the time to break down Part 1 of 6 HubSpot CMS developer interview questions, the list is long and we need to tell you 6 more…

\n","rssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-interview%20questions.png","scheduledUpdateDate":0,"screenshotPreviewTakenAt":1736726865574,"screenshotPreviewUrl":"https://cdn1.hubspot.net/hubshotv3/prod/e/0/de7189e3-7385-4c3e-8296-dca20b3be48a.png","sections":{},"securityState":"NONE","siteId":null,"slug":"blogs/6-more-hubspot-cms-developer-interview-questions-part-2-the-process","stagedFrom":null,"state":"PUBLISHED","stateWhenDeleted":null,"structuredContentPageType":null,"structuredContentType":null,"styleOverrideId":null,"subcategory":"normal_blog_post","syncedWithBlogRoot":true,"tagIds":[62234989205,62770442823,80453663900],"tagList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1639919937608,"deletedAt":0,"description":"","id":62234989205,"label":"Development","language":"en","name":"Development","portalId":6534445,"slug":"development","translatedFromId":null,"translations":{},"updated":1639919937608},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1659024478836,"deletedAt":0,"description":"","id":80453663900,"label":"Agency Outsourcing","language":"en","name":"Agency Outsourcing","portalId":6534445,"slug":"agency-outsourcing","translatedFromId":null,"translations":{},"updated":1659024478836}],"tagNames":["Development","HubSpot CMS Development","Agency Outsourcing"],"teamPerms":[],"templatePath":"","templatePathForRender":"deckerdevs-theme/templates/blog-content.html","textToAudioFileId":null,"textToAudioGenerationRequestId":null,"themePath":null,"themeSettingsValues":null,"title":"6 More HubSpot CMS Developer Interview Questions Part 2: The Process","tmsId":null,"topicIds":[62234989205,62770442823,80453663900],"topicList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1639919937608,"deletedAt":0,"description":"","id":62234989205,"label":"Development","language":"en","name":"Development","portalId":6534445,"slug":"development","translatedFromId":null,"translations":{},"updated":1639919937608},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1659024478836,"deletedAt":0,"description":"","id":80453663900,"label":"Agency Outsourcing","language":"en","name":"Agency Outsourcing","portalId":6534445,"slug":"agency-outsourcing","translatedFromId":null,"translations":{},"updated":1659024478836}],"topicNames":["Development","HubSpot CMS Development","Agency Outsourcing"],"topics":[62234989205,62770442823,80453663900],"translatedContent":{},"translatedFromId":null,"translations":{},"tweet":null,"tweetAt":null,"tweetImmediately":false,"unpublishedAt":0,"updated":1722384465753,"updatedById":61310730,"upsizeFeaturedImage":false,"url":"https://deckerdevs.com/blogs/6-more-hubspot-cms-developer-interview-questions-part-2-the-process","useFeaturedImage":true,"userPerms":[],"views":null,"visibleToAll":null,"widgetContainers":{},"widgetcontainers":{},"widgets":{"blog-hero":{"body":{"column_split":"split-40-60","flip_columns_on_desktop":true,"heading":"6 More HubSpot CMS Developer Interview Questions Part 2: The Process","heading_size":"h1","heading_tag":"h1","image_holder":{"image_field":{"alt":"deckerdevs-interview questions","height":1080,"loading":"lazy","max_height":1080,"max_width":1080,"size_type":"auto","src":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-interview%20questions.png","width":1080}},"module_id":82854350373},"child_css":{},"css":{},"id":"blog-hero","label":null,"module_id":82854350373,"name":"blog-hero","order":1,"smart_type":null,"styles":{},"type":"module"},"blog-image":{"body":{"image_field":{"alt":"pattern","height":563,"loading":"lazy","max_height":563,"max_width":1000,"size_type":"auto","src":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/deckerdevs%20brand%20assets/pattern.jpg","width":1000},"module_id":62246908725},"child_css":{},"css":{},"deleted_at":1692280493579,"id":"blog-image","label":null,"module_id":62246908725,"name":"blog-image","order":3,"smart_type":null,"styles":{},"type":"module"},"blog-posts":{"body":{"heading":"Some Other Recent Thoughts"},"child_css":{},"css":{},"id":"blog-posts","label":null,"module_id":82853805588,"name":"blog-posts","order":4,"smart_type":null,"styles":{},"type":"module"}}},{"ab":false,"abStatus":null,"abTestId":null,"abVariation":false,"abVariationAutomated":false,"absoluteUrl":"https://deckerdevs.com/blogs/7-hubspot-cms-developer-interview-questions-to-ask-part-1","afterPostBody":null,"aifeatures":null,"allowedSlugConflict":false,"analytics":null,"analyticsPageId":"82260419178","analyticsPageType":"blog-post","approvalStatus":null,"archived":false,"archivedAt":0,"archivedInDashboard":false,"areCommentsAllowed":true,"attachedStylesheets":[],"audienceAccess":"PUBLIC","author":null,"authorName":null,"authorUsername":null,"blogAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogAuthorId":62235724408,"blogPostAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogPostScheduleTaskUid":null,"blogPublishInstantEmailCampaignId":null,"blogPublishInstantEmailRetryCount":null,"blogPublishInstantEmailTaskUid":null,"blogPublishToSocialMediaTask":"DONE_NOT_SENT","blueprintTypeId":0,"businessUnitId":null,"campaign":null,"campaignName":null,"campaignUtm":null,"category":3,"categoryId":3,"cdnPurgeEmbargoTime":null,"checkPostLevelAudienceAccessFirst":true,"clonedFrom":null,"composeBody":null,"compositionId":0,"contentAccessRuleIds":[],"contentAccessRuleTypes":[],"contentGroup":62179259185,"contentGroupId":62179259185,"contentTypeCategory":3,"contentTypeCategoryId":3,"contentTypeId":null,"created":1660759667304,"createdByAgent":null,"createdById":27630257,"createdTime":1660759667304,"crmObjectId":null,"css":{},"cssText":"","ctaClicks":null,"ctaViews":null,"currentState":"PUBLISHED","currentlyPublished":true,"deletedAt":0,"deletedBy":null,"deletedByEmail":null,"deletedById":null,"domain":"","dynamicPageDataSourceId":null,"dynamicPageDataSourceType":null,"dynamicPageHubDbTableId":null,"enableDomainStylesheets":null,"enableGoogleAmpOutputOverride":false,"enableLayoutStylesheets":null,"errors":[],"featuredImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/63.png","featuredImageAltText":"hubspot cms developer","featuredImageHeight":2700,"featuredImageLength":0,"featuredImageWidth":2700,"flexAreas":{},"folderId":null,"footerHtml":null,"freezeDate":1660763003000,"generateJsonLdEnabledOverride":true,"hasContentAccessRules":false,"hasUserChanges":true,"headHtml":null,"header":null,"htmlTitle":"7 HubSpot CMS Developer Interview Questions to Ask: Part 1","id":82260419178,"includeDefaultCustomCss":null,"isCaptchaRequired":true,"isCrawlableByBots":false,"isDraft":false,"isInstanceLayoutPage":false,"isInstantEmailEnabled":false,"isPublished":true,"isSocialPublishingEnabled":false,"keywords":[],"label":"7 HubSpot CMS Developer Interview Questions to Ask: Part 1","language":"en","lastEditSessionId":null,"lastEditUpdateId":null,"layoutSections":{},"legacyBlogTabid":null,"legacyId":null,"legacyPostGuid":null,"linkRelCanonicalUrl":"","listTemplate":"","liveDomain":"deckerdevs.com","mab":false,"mabExperimentId":null,"mabMaster":false,"mabVariant":false,"meta":{"html_title":"7 HubSpot CMS Developer Interview Questions to Ask: Part 1","public_access_rules":[],"public_access_rules_enabled":false,"enable_google_amp_output_override":false,"generate_json_ld_enabled":true,"composition_id":0,"is_crawlable_by_bots":false,"use_featured_image":true,"post_body":"

When it comes to hiring a HubSpot CMS developer partner agency for a development project, it is important to hire an experienced professional that is going to create a beautiful, functional website, application or module they are willing to support.

You might be wondering - where the best HubSpot CMS developers are hiding?
You might be wondering - how can you make sure you’re working with the best developer?

As HubSpot CMS developers, we have been working within HubSpot CMS since shortly after launch and we have compiled a list of questions that you can ask during the vetting process to ensure that you end up with the best developer to suit your individual business needs.

Here are 6 preliminary questions you will want to ask your HubSpot developer during the interview process to qualify them for the job:

\n\n

Who will the architect be in this project?

\n

In many agencies, there can be a large disconnect between the sales rep and the development team. This can mean big issues when it comes to scoping and developing new projects on a client’s behalf. If you are not interfacing with the development team, you will want to take time to understand who is architecting your project and how the salesperson or account manager will be interacting with the rest of the team to ensure that your brand and project vision are communicated seamlessly to them.

\n

\n

 

\n

You do not want to be playing a game of telephone between a sales rep, account manager, project manager and developer unless they have a really comprehensive, seamless project flow.

\n

Will we get to meet the project architect during the kickoff meeting?

\n

This is one of the most critical aspects of project planning. You need to get to know the person who will be architecting your website and ideally that means meeting with them prior to the start of the project.

\n

If you are unable to meet with them, an extremely detailed plan must be in place to give the architect information about your brand mission, services, vision for the website or project, the buyer journey and goals of the project. Meeting with the lead designer or developer in charge of your project is a critical aspect to ensure that you are getting what you ask for.

\n

Can you provide some examples of work you've completed in HubSpot CMS?

\n

Any experienced developer will have a considerable amount of projects to share with you.

\n

They will be able to provide a list of the projects they have completed and run down the complexities of the design and how they implemented the projects.

\n

They will be able to explain how the back end works for the users that will be updating the website and give examples of how they made it easy for the marketer to implement the design elements on the back end.

\n

Tell us about the challenges you've encountered with these projects in HubSpot; how did you overcome them? 

\n

Good developers put out quality projects. Great developers complete projects that other developers say cannot be done. There are always challenges when it comes to implementing designs, bridging integrations and adding features in HubSpot CMS, but the key in vetting the developer for your next project is understanding how they overcame the challenges they were faced with in the development process.

Great developers love a challenge and they are usually willing to brag about how they used their brain and coding skills to overcome them. Ask the question to get to know how your developers think and approach complex problems. While not all developers will have case studies at their disposal if you are working with them directly, a qualified agency will have an arsenal of case studies and white papers to showcase their skills.

\n

Have you worked with businesses like ours before?

\n

Industry experience, while helpful, is not the most important thing when it comes to hiring a HubSpot CMS developer, but it does help. Knowing that a developer understands the intricacies of your industry or business can be beneficial, especially if there are regulations and legal requirements associated with your business.

It never hurts to ask if a developer has experience working with other businesses of your type. They may be able to give you more valuable feedback when it comes to what works and doesn’t work relating to the project that you are discussing.

\n

Are you modifying a theme you worked with before, is this a template or are you working from scratch? 

\n

A custom website is very expensive. Customizing templates or themes can be a great way for your developer to keep your costs down. You will want to know what is happening, though and they should not oversell what they are doing.

If they are modifying a template or theme, you will want to ask follow up questions about website bloat. Coding on top of an existing website theme design can bog down your website - an experienced developer will be aware of potential problems and let you know how they intend to handle them in advance.

\n

How will the design process work?

\n

Your design is critical to the success of your HubSpot CMS project. It should balance aesthetics and function. Analysis should be done to determine how it compliments the journey your buyers are on when they find your website.

\n

 

\n

\n

Your developer or agency should have a comprehensive process for how to handle design and it should include a lot of feedback from you. You will want to deliver your branded fonts, colors, style guidelines and information about your products and services. If you have notalready done so, your agency may engage in the development of your buyer personas to help you understand the buyer journey and how it fits into your offerings and goals.

While each agency’s design process is different, any process that does not involve getting all of this information prior to establishing a design - isn’t worth vetting, in our opinion.

These are just a few of the questions you should lead with when vetting a HubSpot CMS agency or development partner. You are likely investing thousands of dollars into this project in the hopes that it will yield leads, greater revenue, or better efficiency among your employees - asking the right questions during the interview process is critical to your success.

\n

Got any to add to the list? Drop them in the comments and be sure to check out Part 2 for more HubSpot CMS developer interview questions to ask. 

\n

\n

 

\n

 

","rss_summary":"

When it comes to hiring a HubSpot CMS developer partner agency for a development project, it is important to hire an experienced professional that is going to create a beautiful, functional website, application or module they are willing to support.

You might be wondering - where the best HubSpot CMS developers are hiding?
You might be wondering - how can you make sure you’re working with the best developer?

As HubSpot CMS developers, we have been working within HubSpot CMS since shortly after launch and we have compiled a list of questions that you can ask during the vetting process to ensure that you end up with the best developer to suit your individual business needs.

Here are 6 preliminary questions you will want to ask your HubSpot developer during the interview process to qualify them for the job:

\n","rss_body":"

When it comes to hiring a HubSpot CMS developer partner agency for a development project, it is important to hire an experienced professional that is going to create a beautiful, functional website, application or module they are willing to support.

You might be wondering - where the best HubSpot CMS developers are hiding?
You might be wondering - how can you make sure you’re working with the best developer?

As HubSpot CMS developers, we have been working within HubSpot CMS since shortly after launch and we have compiled a list of questions that you can ask during the vetting process to ensure that you end up with the best developer to suit your individual business needs.

Here are 6 preliminary questions you will want to ask your HubSpot developer during the interview process to qualify them for the job:

\n\n

Who will the architect be in this project?

\n

In many agencies, there can be a large disconnect between the sales rep and the development team. This can mean big issues when it comes to scoping and developing new projects on a client’s behalf. If you are not interfacing with the development team, you will want to take time to understand who is architecting your project and how the salesperson or account manager will be interacting with the rest of the team to ensure that your brand and project vision are communicated seamlessly to them.

\n

\n

 

\n

You do not want to be playing a game of telephone between a sales rep, account manager, project manager and developer unless they have a really comprehensive, seamless project flow.

\n

Will we get to meet the project architect during the kickoff meeting?

\n

This is one of the most critical aspects of project planning. You need to get to know the person who will be architecting your website and ideally that means meeting with them prior to the start of the project.

\n

If you are unable to meet with them, an extremely detailed plan must be in place to give the architect information about your brand mission, services, vision for the website or project, the buyer journey and goals of the project. Meeting with the lead designer or developer in charge of your project is a critical aspect to ensure that you are getting what you ask for.

\n

Can you provide some examples of work you've completed in HubSpot CMS?

\n

Any experienced developer will have a considerable amount of projects to share with you.

\n

They will be able to provide a list of the projects they have completed and run down the complexities of the design and how they implemented the projects.

\n

They will be able to explain how the back end works for the users that will be updating the website and give examples of how they made it easy for the marketer to implement the design elements on the back end.

\n

Tell us about the challenges you've encountered with these projects in HubSpot; how did you overcome them? 

\n

Good developers put out quality projects. Great developers complete projects that other developers say cannot be done. There are always challenges when it comes to implementing designs, bridging integrations and adding features in HubSpot CMS, but the key in vetting the developer for your next project is understanding how they overcame the challenges they were faced with in the development process.

Great developers love a challenge and they are usually willing to brag about how they used their brain and coding skills to overcome them. Ask the question to get to know how your developers think and approach complex problems. While not all developers will have case studies at their disposal if you are working with them directly, a qualified agency will have an arsenal of case studies and white papers to showcase their skills.

\n

Have you worked with businesses like ours before?

\n

Industry experience, while helpful, is not the most important thing when it comes to hiring a HubSpot CMS developer, but it does help. Knowing that a developer understands the intricacies of your industry or business can be beneficial, especially if there are regulations and legal requirements associated with your business.

It never hurts to ask if a developer has experience working with other businesses of your type. They may be able to give you more valuable feedback when it comes to what works and doesn’t work relating to the project that you are discussing.

\n

Are you modifying a theme you worked with before, is this a template or are you working from scratch? 

\n

A custom website is very expensive. Customizing templates or themes can be a great way for your developer to keep your costs down. You will want to know what is happening, though and they should not oversell what they are doing.

If they are modifying a template or theme, you will want to ask follow up questions about website bloat. Coding on top of an existing website theme design can bog down your website - an experienced developer will be aware of potential problems and let you know how they intend to handle them in advance.

\n

How will the design process work?

\n

Your design is critical to the success of your HubSpot CMS project. It should balance aesthetics and function. Analysis should be done to determine how it compliments the journey your buyers are on when they find your website.

\n

 

\n

\n

Your developer or agency should have a comprehensive process for how to handle design and it should include a lot of feedback from you. You will want to deliver your branded fonts, colors, style guidelines and information about your products and services. If you have notalready done so, your agency may engage in the development of your buyer personas to help you understand the buyer journey and how it fits into your offerings and goals.

While each agency’s design process is different, any process that does not involve getting all of this information prior to establishing a design - isn’t worth vetting, in our opinion.

These are just a few of the questions you should lead with when vetting a HubSpot CMS agency or development partner. You are likely investing thousands of dollars into this project in the hopes that it will yield leads, greater revenue, or better efficiency among your employees - asking the right questions during the interview process is critical to your success.

\n

Got any to add to the list? Drop them in the comments and be sure to check out Part 2 for more HubSpot CMS developer interview questions to ask. 

\n

\n

 

\n

 

","tag_ids":[62770442823,78562833827],"topic_ids":[62770442823,78562833827],"post_summary":"

When it comes to hiring a HubSpot CMS developer partner agency for a development project, it is important to hire an experienced professional that is going to create a beautiful, functional website, application or module they are willing to support.

You might be wondering - where the best HubSpot CMS developers are hiding?
You might be wondering - how can you make sure you’re working with the best developer?

As HubSpot CMS developers, we have been working within HubSpot CMS since shortly after launch and we have compiled a list of questions that you can ask during the vetting process to ensure that you end up with the best developer to suit your individual business needs.

Here are 6 preliminary questions you will want to ask your HubSpot developer during the interview process to qualify them for the job:

\n","blog_post_schedule_task_uid":null,"blog_publish_to_social_media_task":"DONE_NOT_SENT","blog_publish_instant_email_task_uid":null,"blog_publish_instant_email_campaign_id":null,"blog_publish_instant_email_retry_count":null,"keywords":[],"head_html":null,"footer_html":null,"attached_stylesheets":[],"enable_domain_stylesheets":null,"include_default_custom_css":null,"meta_description":"When it comes to HubSpot CMS developer interviews - here are the questions you should be asking:","meta_keywords":null,"layout_sections":{},"past_mab_experiment_ids":[],"deleted_by":null,"featured_image_alt_text":"hubspot cms developer","enable_layout_stylesheets":null,"tweet":null,"tweet_at":null,"campaign_name":null,"campaign_utm":null,"tweet_immediately":false,"publish_immediately":true,"security_state":"NONE","scheduled_update_date":0,"placement_guids":[],"property_for_dynamic_page_title":null,"property_for_dynamic_page_slug":null,"property_for_dynamic_page_meta_description":null,"property_for_dynamic_page_featured_image":null,"property_for_dynamic_page_canonical_url":null,"preview_image_src":null,"legacy_blog_tabid":null,"legacy_post_guid":null,"performable_variation_letter":null,"style_override_id":null,"has_user_changes":true,"css":{},"css_text":"","unpublished_at":0,"published_by_id":61310730,"allowed_slug_conflict":false,"ai_features":null,"link_rel_canonical_url":"","page_redirected":false,"page_expiry_enabled":null,"page_expiry_date":null,"page_expiry_redirect_id":null,"page_expiry_redirect_url":null,"deleted_by_id":null,"state_when_deleted":null,"cloned_from":null,"staged_from":null,"personas":[],"compose_body":null,"featured_image":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/63.png","featured_image_width":2700,"featured_image_height":2700,"publish_timezone_offset":null,"theme_settings_values":null,"password":null,"header":null,"published_at":1719976774551,"last_edit_session_id":null,"last_edit_update_id":null,"created_by_agent":null},"metaDescription":"When it comes to HubSpot CMS developer interviews - here are the questions you should be asking:","metaKeywords":null,"name":"7 HubSpot CMS Developer Interview Questions to Ask: Part 1","nextPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-mega%20menu%20mistakes2.png","nextPostFeaturedImageAltText":"","nextPostName":"HubSpot CMS Development Tips: Mega Mistakes with Mega Menus","nextPostSlug":"blogs/hubspot-cms-development-tips-mega-mistakes-with-mega-menus","pageExpiryDate":null,"pageExpiryEnabled":null,"pageExpiryRedirectId":null,"pageExpiryRedirectUrl":null,"pageRedirected":false,"pageTitle":"7 HubSpot CMS Developer Interview Questions to Ask: Part 1","parentBlog":{"absoluteUrl":"https://deckerdevs.com/blogs","allowComments":true,"ampBodyColor":"#404040","ampBodyFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampBodyFontSize":"18","ampCustomCss":"","ampHeaderBackgroundColor":"#ffffff","ampHeaderColor":"#1e1e1e","ampHeaderFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampHeaderFontSize":"36","ampLinkColor":"#416bb3","ampLogoAlt":"","ampLogoHeight":0,"ampLogoSrc":"","ampLogoWidth":0,"analyticsPageId":62179259185,"attachedStylesheets":[],"audienceAccess":"PUBLIC","businessUnitId":null,"captchaAfterDays":7,"captchaAlways":false,"categoryId":3,"cdnPurgeEmbargoTime":null,"closeCommentsOlder":0,"commentDateFormat":"medium","commentFormGuid":"cb653aa1-3db4-4167-9b59-744c46d49682","commentMaxThreadDepth":3,"commentModeration":false,"commentNotificationEmails":["nicholas@deckerdevs.com","jessica@deckerdevs.com"],"commentShouldCreateContact":true,"commentVerificationText":"Thanks for participating in this conversation! We look forward to responding and to assisting where we can","cosObjectType":"BLOG","created":1639786189589,"createdDateTime":1639786189589,"dailyNotificationEmailId":null,"dateFormattingLanguage":null,"defaultGroupStyleId":"","defaultNotificationFromName":"","defaultNotificationReplyTo":"","deletedAt":0,"description":"rev up your hubspot system to the max! deckerdevs' turbo-charged blog is your ultimate guide to harnessing the full potential of hubspot development. unleash the marketing magic with ingenious tips, tricks, and hacks. get ready to level up your hubspot game!","domain":"","domainWhenPublished":"deckerdevs.com","emailApiSubscriptionId":null,"enableGoogleAmpOutput":false,"enableSocialAutoPublishing":false,"generateJsonLdEnabled":true,"header":null,"htmlFooter":"","htmlFooterIsShared":true,"htmlHead":"","htmlHeadIsShared":true,"htmlKeywords":[],"htmlTitle":"deckerdevs thought nuggets","id":62179259185,"ilsSubscriptionListsByType":{},"instantNotificationEmailId":null,"itemLayoutId":null,"itemTemplateIsShared":false,"itemTemplatePath":"deckerdevs-theme/templates/blog-content.html","label":"deckerdevs live blog","language":"en","legacyGuid":null,"legacyModuleId":null,"legacyTabId":null,"listingLayoutId":null,"listingPageId":62179259186,"listingTemplatePath":"","liveDomain":"deckerdevs.com","monthFilterFormat":"MMMM yyyy","monthlyNotificationEmailId":null,"name":"deckerdevs live blog","parentBlogUpdateTaskId":null,"portalId":6534445,"postHtmlFooter":"","postHtmlHead":"","postsPerListingPage":9,"postsPerRssFeed":10,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publicTitle":"thought nuggets","publishDateFormat":"medium","resolvedDomain":"deckerdevs.com","rootUrl":"https://deckerdevs.com/blogs","rssCustomFeed":null,"rssDescription":null,"rssItemFooter":null,"rssItemHeader":null,"settingsOverrides":{"itemLayoutId":false,"itemTemplatePath":false,"itemTemplateIsShared":false,"listingLayoutId":false,"listingTemplatePath":false,"postsPerListingPage":false,"showSummaryInListing":false,"useFeaturedImageInSummary":false,"htmlHead":false,"postHtmlHead":false,"htmlHeadIsShared":false,"htmlFooter":false,"listingPageHtmlFooter":false,"postHtmlFooter":false,"htmlFooterIsShared":false,"attachedStylesheets":false,"postsPerRssFeed":false,"showSummaryInRss":false,"showSummaryInEmails":false,"showSummariesInEmails":false,"allowComments":false,"commentShouldCreateContact":false,"commentModeration":false,"closeCommentsOlder":false,"commentNotificationEmails":false,"commentMaxThreadDepth":false,"commentVerificationText":false,"socialAccountTwitter":false,"showSocialLinkTwitter":false,"showSocialLinkLinkedin":false,"showSocialLinkFacebook":false,"enableGoogleAmpOutput":false,"ampLogoSrc":false,"ampLogoHeight":false,"ampLogoWidth":false,"ampLogoAlt":false,"ampHeaderFont":false,"ampHeaderFontSize":false,"ampHeaderColor":false,"ampHeaderBackgroundColor":false,"ampBodyFont":false,"ampBodyFontSize":false,"ampBodyColor":false,"ampLinkColor":false,"generateJsonLdEnabled":false},"showSocialLinkFacebook":true,"showSocialLinkLinkedin":true,"showSocialLinkTwitter":true,"showSummaryInEmails":true,"showSummaryInListing":true,"showSummaryInRss":true,"siteId":null,"slug":"blogs","socialAccountTwitter":"","state":null,"subscriptionContactsProperty":null,"subscriptionEmailType":null,"subscriptionFormGuid":null,"subscriptionListsByType":{},"title":null,"translatedFromId":null,"translations":{},"updated":1712344124471,"updatedDateTime":1712344124471,"urlBase":"deckerdevs.com/blogs","urlSegments":{"all":"all","archive":"archive","author":"author","page":"page","tag":"tag"},"useFeaturedImageInSummary":true,"usesDefaultTemplate":false,"weeklyNotificationEmailId":null},"password":null,"pastMabExperimentIds":[],"performableGuid":null,"performableVariationLetter":null,"personas":[],"placementGuids":[],"portableKey":null,"portalId":6534445,"position":null,"postBody":"

When it comes to hiring a HubSpot CMS developer partner agency for a development project, it is important to hire an experienced professional that is going to create a beautiful, functional website, application or module they are willing to support.

You might be wondering - where the best HubSpot CMS developers are hiding?
You might be wondering - how can you make sure you’re working with the best developer?

As HubSpot CMS developers, we have been working within HubSpot CMS since shortly after launch and we have compiled a list of questions that you can ask during the vetting process to ensure that you end up with the best developer to suit your individual business needs.

Here are 6 preliminary questions you will want to ask your HubSpot developer during the interview process to qualify them for the job:

\n\n

Who will the architect be in this project?

\n

In many agencies, there can be a large disconnect between the sales rep and the development team. This can mean big issues when it comes to scoping and developing new projects on a client’s behalf. If you are not interfacing with the development team, you will want to take time to understand who is architecting your project and how the salesperson or account manager will be interacting with the rest of the team to ensure that your brand and project vision are communicated seamlessly to them.

\n

\n

 

\n

You do not want to be playing a game of telephone between a sales rep, account manager, project manager and developer unless they have a really comprehensive, seamless project flow.

\n

Will we get to meet the project architect during the kickoff meeting?

\n

This is one of the most critical aspects of project planning. You need to get to know the person who will be architecting your website and ideally that means meeting with them prior to the start of the project.

\n

If you are unable to meet with them, an extremely detailed plan must be in place to give the architect information about your brand mission, services, vision for the website or project, the buyer journey and goals of the project. Meeting with the lead designer or developer in charge of your project is a critical aspect to ensure that you are getting what you ask for.

\n

Can you provide some examples of work you've completed in HubSpot CMS?

\n

Any experienced developer will have a considerable amount of projects to share with you.

\n

They will be able to provide a list of the projects they have completed and run down the complexities of the design and how they implemented the projects.

\n

They will be able to explain how the back end works for the users that will be updating the website and give examples of how they made it easy for the marketer to implement the design elements on the back end.

\n

Tell us about the challenges you've encountered with these projects in HubSpot; how did you overcome them? 

\n

Good developers put out quality projects. Great developers complete projects that other developers say cannot be done. There are always challenges when it comes to implementing designs, bridging integrations and adding features in HubSpot CMS, but the key in vetting the developer for your next project is understanding how they overcame the challenges they were faced with in the development process.

Great developers love a challenge and they are usually willing to brag about how they used their brain and coding skills to overcome them. Ask the question to get to know how your developers think and approach complex problems. While not all developers will have case studies at their disposal if you are working with them directly, a qualified agency will have an arsenal of case studies and white papers to showcase their skills.

\n

Have you worked with businesses like ours before?

\n

Industry experience, while helpful, is not the most important thing when it comes to hiring a HubSpot CMS developer, but it does help. Knowing that a developer understands the intricacies of your industry or business can be beneficial, especially if there are regulations and legal requirements associated with your business.

It never hurts to ask if a developer has experience working with other businesses of your type. They may be able to give you more valuable feedback when it comes to what works and doesn’t work relating to the project that you are discussing.

\n

Are you modifying a theme you worked with before, is this a template or are you working from scratch? 

\n

A custom website is very expensive. Customizing templates or themes can be a great way for your developer to keep your costs down. You will want to know what is happening, though and they should not oversell what they are doing.

If they are modifying a template or theme, you will want to ask follow up questions about website bloat. Coding on top of an existing website theme design can bog down your website - an experienced developer will be aware of potential problems and let you know how they intend to handle them in advance.

\n

How will the design process work?

\n

Your design is critical to the success of your HubSpot CMS project. It should balance aesthetics and function. Analysis should be done to determine how it compliments the journey your buyers are on when they find your website.

\n

 

\n

\n

Your developer or agency should have a comprehensive process for how to handle design and it should include a lot of feedback from you. You will want to deliver your branded fonts, colors, style guidelines and information about your products and services. If you have notalready done so, your agency may engage in the development of your buyer personas to help you understand the buyer journey and how it fits into your offerings and goals.

While each agency’s design process is different, any process that does not involve getting all of this information prior to establishing a design - isn’t worth vetting, in our opinion.

These are just a few of the questions you should lead with when vetting a HubSpot CMS agency or development partner. You are likely investing thousands of dollars into this project in the hopes that it will yield leads, greater revenue, or better efficiency among your employees - asking the right questions during the interview process is critical to your success.

\n

Got any to add to the list? Drop them in the comments and be sure to check out Part 2 for more HubSpot CMS developer interview questions to ask. 

\n

\n

 

\n

 

","postBodyRss":"

When it comes to hiring a HubSpot CMS developer partner agency for a development project, it is important to hire an experienced professional that is going to create a beautiful, functional website, application or module they are willing to support.

You might be wondering - where the best HubSpot CMS developers are hiding?
You might be wondering - how can you make sure you’re working with the best developer?

As HubSpot CMS developers, we have been working within HubSpot CMS since shortly after launch and we have compiled a list of questions that you can ask during the vetting process to ensure that you end up with the best developer to suit your individual business needs.

Here are 6 preliminary questions you will want to ask your HubSpot developer during the interview process to qualify them for the job:

\n\n

Who will the architect be in this project?

\n

In many agencies, there can be a large disconnect between the sales rep and the development team. This can mean big issues when it comes to scoping and developing new projects on a client’s behalf. If you are not interfacing with the development team, you will want to take time to understand who is architecting your project and how the salesperson or account manager will be interacting with the rest of the team to ensure that your brand and project vision are communicated seamlessly to them.

\n

\n

 

\n

You do not want to be playing a game of telephone between a sales rep, account manager, project manager and developer unless they have a really comprehensive, seamless project flow.

\n

Will we get to meet the project architect during the kickoff meeting?

\n

This is one of the most critical aspects of project planning. You need to get to know the person who will be architecting your website and ideally that means meeting with them prior to the start of the project.

\n

If you are unable to meet with them, an extremely detailed plan must be in place to give the architect information about your brand mission, services, vision for the website or project, the buyer journey and goals of the project. Meeting with the lead designer or developer in charge of your project is a critical aspect to ensure that you are getting what you ask for.

\n

Can you provide some examples of work you've completed in HubSpot CMS?

\n

Any experienced developer will have a considerable amount of projects to share with you.

\n

They will be able to provide a list of the projects they have completed and run down the complexities of the design and how they implemented the projects.

\n

They will be able to explain how the back end works for the users that will be updating the website and give examples of how they made it easy for the marketer to implement the design elements on the back end.

\n

Tell us about the challenges you've encountered with these projects in HubSpot; how did you overcome them? 

\n

Good developers put out quality projects. Great developers complete projects that other developers say cannot be done. There are always challenges when it comes to implementing designs, bridging integrations and adding features in HubSpot CMS, but the key in vetting the developer for your next project is understanding how they overcame the challenges they were faced with in the development process.

Great developers love a challenge and they are usually willing to brag about how they used their brain and coding skills to overcome them. Ask the question to get to know how your developers think and approach complex problems. While not all developers will have case studies at their disposal if you are working with them directly, a qualified agency will have an arsenal of case studies and white papers to showcase their skills.

\n

Have you worked with businesses like ours before?

\n

Industry experience, while helpful, is not the most important thing when it comes to hiring a HubSpot CMS developer, but it does help. Knowing that a developer understands the intricacies of your industry or business can be beneficial, especially if there are regulations and legal requirements associated with your business.

It never hurts to ask if a developer has experience working with other businesses of your type. They may be able to give you more valuable feedback when it comes to what works and doesn’t work relating to the project that you are discussing.

\n

Are you modifying a theme you worked with before, is this a template or are you working from scratch? 

\n

A custom website is very expensive. Customizing templates or themes can be a great way for your developer to keep your costs down. You will want to know what is happening, though and they should not oversell what they are doing.

If they are modifying a template or theme, you will want to ask follow up questions about website bloat. Coding on top of an existing website theme design can bog down your website - an experienced developer will be aware of potential problems and let you know how they intend to handle them in advance.

\n

How will the design process work?

\n

Your design is critical to the success of your HubSpot CMS project. It should balance aesthetics and function. Analysis should be done to determine how it compliments the journey your buyers are on when they find your website.

\n

 

\n

\n

Your developer or agency should have a comprehensive process for how to handle design and it should include a lot of feedback from you. You will want to deliver your branded fonts, colors, style guidelines and information about your products and services. If you have notalready done so, your agency may engage in the development of your buyer personas to help you understand the buyer journey and how it fits into your offerings and goals.

While each agency’s design process is different, any process that does not involve getting all of this information prior to establishing a design - isn’t worth vetting, in our opinion.

These are just a few of the questions you should lead with when vetting a HubSpot CMS agency or development partner. You are likely investing thousands of dollars into this project in the hopes that it will yield leads, greater revenue, or better efficiency among your employees - asking the right questions during the interview process is critical to your success.

\n

Got any to add to the list? Drop them in the comments and be sure to check out Part 2 for more HubSpot CMS developer interview questions to ask. 

\n

\n

 

\n

 

","postEmailContent":"

When it comes to hiring a HubSpot CMS developer partner agency for a development project, it is important to hire an experienced professional that is going to create a beautiful, functional website, application or module they are willing to support.

You might be wondering - where the best HubSpot CMS developers are hiding?
You might be wondering - how can you make sure you’re working with the best developer?

As HubSpot CMS developers, we have been working within HubSpot CMS since shortly after launch and we have compiled a list of questions that you can ask during the vetting process to ensure that you end up with the best developer to suit your individual business needs.

Here are 6 preliminary questions you will want to ask your HubSpot developer during the interview process to qualify them for the job:

","postFeaturedImageIfEnabled":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/63.png","postListContent":"

When it comes to hiring a HubSpot CMS developer partner agency for a development project, it is important to hire an experienced professional that is going to create a beautiful, functional website, application or module they are willing to support.

You might be wondering - where the best HubSpot CMS developers are hiding?
You might be wondering - how can you make sure you’re working with the best developer?

As HubSpot CMS developers, we have been working within HubSpot CMS since shortly after launch and we have compiled a list of questions that you can ask during the vetting process to ensure that you end up with the best developer to suit your individual business needs.

Here are 6 preliminary questions you will want to ask your HubSpot developer during the interview process to qualify them for the job:

","postListSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/63.png","postRssContent":"

When it comes to hiring a HubSpot CMS developer partner agency for a development project, it is important to hire an experienced professional that is going to create a beautiful, functional website, application or module they are willing to support.

You might be wondering - where the best HubSpot CMS developers are hiding?
You might be wondering - how can you make sure you’re working with the best developer?

As HubSpot CMS developers, we have been working within HubSpot CMS since shortly after launch and we have compiled a list of questions that you can ask during the vetting process to ensure that you end up with the best developer to suit your individual business needs.

Here are 6 preliminary questions you will want to ask your HubSpot developer during the interview process to qualify them for the job:

","postRssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/63.png","postSummary":"

When it comes to hiring a HubSpot CMS developer partner agency for a development project, it is important to hire an experienced professional that is going to create a beautiful, functional website, application or module they are willing to support.

You might be wondering - where the best HubSpot CMS developers are hiding?
You might be wondering - how can you make sure you’re working with the best developer?

As HubSpot CMS developers, we have been working within HubSpot CMS since shortly after launch and we have compiled a list of questions that you can ask during the vetting process to ensure that you end up with the best developer to suit your individual business needs.

Here are 6 preliminary questions you will want to ask your HubSpot developer during the interview process to qualify them for the job:

\n","postSummaryRss":"

When it comes to hiring a HubSpot CMS developer partner agency for a development project, it is important to hire an experienced professional that is going to create a beautiful, functional website, application or module they are willing to support.

You might be wondering - where the best HubSpot CMS developers are hiding?
You might be wondering - how can you make sure you’re working with the best developer?

As HubSpot CMS developers, we have been working within HubSpot CMS since shortly after launch and we have compiled a list of questions that you can ask during the vetting process to ensure that you end up with the best developer to suit your individual business needs.

Here are 6 preliminary questions you will want to ask your HubSpot developer during the interview process to qualify them for the job:

","postTemplate":"deckerdevs-theme/templates/blog-content.html","previewImageSrc":null,"previewKey":"mwvcSOLp","previousPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-interview%20questions.png","previousPostFeaturedImageAltText":"","previousPostName":"6 More HubSpot CMS Developer Interview Questions Part 2: The Process","previousPostSlug":"blogs/6-more-hubspot-cms-developer-interview-questions-part-2-the-process","processingStatus":"PUBLISHED","propertyForDynamicPageCanonicalUrl":null,"propertyForDynamicPageFeaturedImage":null,"propertyForDynamicPageMetaDescription":null,"propertyForDynamicPageSlug":null,"propertyForDynamicPageTitle":null,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publishDate":1660763003000,"publishDateLocalTime":1660763003000,"publishDateLocalized":{"date":1660763003000,"format":"medium","language":null},"publishImmediately":true,"publishTimezoneOffset":null,"publishedAt":1719976774551,"publishedByEmail":null,"publishedById":61310730,"publishedByName":null,"publishedUrl":"https://deckerdevs.com/blogs/7-hubspot-cms-developer-interview-questions-to-ask-part-1","resolvedDomain":"deckerdevs.com","resolvedLanguage":null,"rssBody":"

When it comes to hiring a HubSpot CMS developer partner agency for a development project, it is important to hire an experienced professional that is going to create a beautiful, functional website, application or module they are willing to support.

You might be wondering - where the best HubSpot CMS developers are hiding?
You might be wondering - how can you make sure you’re working with the best developer?

As HubSpot CMS developers, we have been working within HubSpot CMS since shortly after launch and we have compiled a list of questions that you can ask during the vetting process to ensure that you end up with the best developer to suit your individual business needs.

Here are 6 preliminary questions you will want to ask your HubSpot developer during the interview process to qualify them for the job:

\n\n

Who will the architect be in this project?

\n

In many agencies, there can be a large disconnect between the sales rep and the development team. This can mean big issues when it comes to scoping and developing new projects on a client’s behalf. If you are not interfacing with the development team, you will want to take time to understand who is architecting your project and how the salesperson or account manager will be interacting with the rest of the team to ensure that your brand and project vision are communicated seamlessly to them.

\n

\n

 

\n

You do not want to be playing a game of telephone between a sales rep, account manager, project manager and developer unless they have a really comprehensive, seamless project flow.

\n

Will we get to meet the project architect during the kickoff meeting?

\n

This is one of the most critical aspects of project planning. You need to get to know the person who will be architecting your website and ideally that means meeting with them prior to the start of the project.

\n

If you are unable to meet with them, an extremely detailed plan must be in place to give the architect information about your brand mission, services, vision for the website or project, the buyer journey and goals of the project. Meeting with the lead designer or developer in charge of your project is a critical aspect to ensure that you are getting what you ask for.

\n

Can you provide some examples of work you've completed in HubSpot CMS?

\n

Any experienced developer will have a considerable amount of projects to share with you.

\n

They will be able to provide a list of the projects they have completed and run down the complexities of the design and how they implemented the projects.

\n

They will be able to explain how the back end works for the users that will be updating the website and give examples of how they made it easy for the marketer to implement the design elements on the back end.

\n

Tell us about the challenges you've encountered with these projects in HubSpot; how did you overcome them? 

\n

Good developers put out quality projects. Great developers complete projects that other developers say cannot be done. There are always challenges when it comes to implementing designs, bridging integrations and adding features in HubSpot CMS, but the key in vetting the developer for your next project is understanding how they overcame the challenges they were faced with in the development process.

Great developers love a challenge and they are usually willing to brag about how they used their brain and coding skills to overcome them. Ask the question to get to know how your developers think and approach complex problems. While not all developers will have case studies at their disposal if you are working with them directly, a qualified agency will have an arsenal of case studies and white papers to showcase their skills.

\n

Have you worked with businesses like ours before?

\n

Industry experience, while helpful, is not the most important thing when it comes to hiring a HubSpot CMS developer, but it does help. Knowing that a developer understands the intricacies of your industry or business can be beneficial, especially if there are regulations and legal requirements associated with your business.

It never hurts to ask if a developer has experience working with other businesses of your type. They may be able to give you more valuable feedback when it comes to what works and doesn’t work relating to the project that you are discussing.

\n

Are you modifying a theme you worked with before, is this a template or are you working from scratch? 

\n

A custom website is very expensive. Customizing templates or themes can be a great way for your developer to keep your costs down. You will want to know what is happening, though and they should not oversell what they are doing.

If they are modifying a template or theme, you will want to ask follow up questions about website bloat. Coding on top of an existing website theme design can bog down your website - an experienced developer will be aware of potential problems and let you know how they intend to handle them in advance.

\n

How will the design process work?

\n

Your design is critical to the success of your HubSpot CMS project. It should balance aesthetics and function. Analysis should be done to determine how it compliments the journey your buyers are on when they find your website.

\n

 

\n

\n

Your developer or agency should have a comprehensive process for how to handle design and it should include a lot of feedback from you. You will want to deliver your branded fonts, colors, style guidelines and information about your products and services. If you have notalready done so, your agency may engage in the development of your buyer personas to help you understand the buyer journey and how it fits into your offerings and goals.

While each agency’s design process is different, any process that does not involve getting all of this information prior to establishing a design - isn’t worth vetting, in our opinion.

These are just a few of the questions you should lead with when vetting a HubSpot CMS agency or development partner. You are likely investing thousands of dollars into this project in the hopes that it will yield leads, greater revenue, or better efficiency among your employees - asking the right questions during the interview process is critical to your success.

\n

Got any to add to the list? Drop them in the comments and be sure to check out Part 2 for more HubSpot CMS developer interview questions to ask. 

\n

\n

 

\n

 

","rssSummary":"

When it comes to hiring a HubSpot CMS developer partner agency for a development project, it is important to hire an experienced professional that is going to create a beautiful, functional website, application or module they are willing to support.

You might be wondering - where the best HubSpot CMS developers are hiding?
You might be wondering - how can you make sure you’re working with the best developer?

As HubSpot CMS developers, we have been working within HubSpot CMS since shortly after launch and we have compiled a list of questions that you can ask during the vetting process to ensure that you end up with the best developer to suit your individual business needs.

Here are 6 preliminary questions you will want to ask your HubSpot developer during the interview process to qualify them for the job:

\n","rssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/63.png","scheduledUpdateDate":0,"screenshotPreviewTakenAt":1734319174574,"screenshotPreviewUrl":"https://cdn1.hubspot.net/hubshotv3/prod/e/0/9c29f4e4-bded-483f-9ebc-991239ec0a20.png","sections":{},"securityState":"NONE","siteId":null,"slug":"blogs/7-hubspot-cms-developer-interview-questions-to-ask-part-1","stagedFrom":null,"state":"PUBLISHED","stateWhenDeleted":null,"structuredContentPageType":null,"structuredContentType":null,"styleOverrideId":null,"subcategory":"normal_blog_post","syncedWithBlogRoot":true,"tagIds":[62770442823,78562833827],"tagList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1657204695862,"deletedAt":0,"description":"","id":78562833827,"label":"HubSpot Partner","language":"en","name":"HubSpot Partner","portalId":6534445,"slug":"hubspot-partner","translatedFromId":null,"translations":{},"updated":1657204695862}],"tagNames":["HubSpot CMS Development","HubSpot Partner"],"teamPerms":[],"templatePath":"","templatePathForRender":"deckerdevs-theme/templates/blog-content.html","textToAudioFileId":null,"textToAudioGenerationRequestId":null,"themePath":null,"themeSettingsValues":null,"title":"7 HubSpot CMS Developer Interview Questions to Ask: Part 1","tmsId":null,"topicIds":[62770442823,78562833827],"topicList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1657204695862,"deletedAt":0,"description":"","id":78562833827,"label":"HubSpot Partner","language":"en","name":"HubSpot Partner","portalId":6534445,"slug":"hubspot-partner","translatedFromId":null,"translations":{},"updated":1657204695862}],"topicNames":["HubSpot CMS Development","HubSpot Partner"],"topics":[62770442823,78562833827],"translatedContent":{},"translatedFromId":null,"translations":{},"tweet":null,"tweetAt":null,"tweetImmediately":false,"unpublishedAt":0,"updated":1719976774554,"updatedById":61310730,"upsizeFeaturedImage":false,"url":"https://deckerdevs.com/blogs/7-hubspot-cms-developer-interview-questions-to-ask-part-1","useFeaturedImage":true,"userPerms":[],"views":null,"visibleToAll":null,"widgetContainers":{},"widgetcontainers":{},"widgets":{"blog-image":{"body":{"image_field":{"alt":"pattern-2","height":563,"loading":"lazy","max_height":563,"max_width":1000,"size_type":"auto","src":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/pattern-2.jpg","width":1000},"module_id":62246908725},"child_css":{},"css":{},"deleted_at":1692280568439,"id":"blog-image","label":null,"module_id":62246908725,"name":"blog-image","order":3,"smart_type":null,"styles":{},"type":"module"}}},{"ab":false,"abStatus":null,"abTestId":null,"abVariation":false,"abVariationAutomated":false,"absoluteUrl":"https://deckerdevs.com/blogs/hubspot-cms-development-tips-mega-mistakes-with-mega-menus","afterPostBody":null,"aifeatures":null,"allowedSlugConflict":false,"analytics":null,"analyticsPageId":"82133679662","analyticsPageType":"blog-post","approvalStatus":null,"archived":false,"archivedAt":0,"archivedInDashboard":false,"areCommentsAllowed":true,"attachedStylesheets":[],"audienceAccess":"PUBLIC","author":null,"authorName":null,"authorUsername":null,"blogAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogAuthorId":62235724408,"blogPostAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogPostScheduleTaskUid":null,"blogPublishInstantEmailCampaignId":null,"blogPublishInstantEmailRetryCount":null,"blogPublishInstantEmailTaskUid":null,"blogPublishToSocialMediaTask":"DONE_NOT_SENT","blueprintTypeId":0,"businessUnitId":null,"campaign":null,"campaignName":null,"campaignUtm":null,"category":3,"categoryId":3,"cdnPurgeEmbargoTime":null,"checkPostLevelAudienceAccessFirst":true,"clonedFrom":null,"composeBody":null,"compositionId":0,"contentAccessRuleIds":[],"contentAccessRuleTypes":[],"contentGroup":62179259185,"contentGroupId":62179259185,"contentTypeCategory":3,"contentTypeCategoryId":3,"contentTypeId":null,"created":1660664851474,"createdByAgent":null,"createdById":27630257,"createdTime":1660664851474,"crmObjectId":null,"css":{},"cssText":"","ctaClicks":null,"ctaViews":null,"currentState":"PUBLISHED","currentlyPublished":true,"deletedAt":0,"deletedBy":null,"deletedByEmail":null,"deletedById":null,"domain":"","dynamicPageDataSourceId":null,"dynamicPageDataSourceType":null,"dynamicPageHubDbTableId":null,"enableDomainStylesheets":null,"enableGoogleAmpOutputOverride":false,"enableLayoutStylesheets":null,"errors":[],"featuredImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-mega%20menu%20mistakes2.png","featuredImageAltText":"","featuredImageHeight":1080,"featuredImageLength":0,"featuredImageWidth":1080,"flexAreas":{},"folderId":null,"footerHtml":null,"freezeDate":1660665547000,"generateJsonLdEnabledOverride":true,"hasContentAccessRules":false,"hasUserChanges":true,"headHtml":null,"header":null,"htmlTitle":"HubSpot CMS Development Tips: Mega Mistakes with Mega Menus","id":82133679662,"includeDefaultCustomCss":null,"isCaptchaRequired":true,"isCrawlableByBots":false,"isDraft":false,"isInstanceLayoutPage":false,"isInstantEmailEnabled":false,"isPublished":true,"isSocialPublishingEnabled":false,"keywords":[],"label":"HubSpot CMS Development Tips: Mega Mistakes with Mega Menus","language":"en","lastEditSessionId":null,"lastEditUpdateId":null,"layoutSections":{},"legacyBlogTabid":null,"legacyId":null,"legacyPostGuid":null,"linkRelCanonicalUrl":"","listTemplate":"","liveDomain":"deckerdevs.com","mab":false,"mabExperimentId":null,"mabMaster":false,"mabVariant":false,"meta":{"html_title":"HubSpot CMS Development Tips: Mega Mistakes with Mega Menus","public_access_rules":[],"public_access_rules_enabled":false,"enable_google_amp_output_override":false,"generate_json_ld_enabled":true,"composition_id":0,"is_crawlable_by_bots":false,"use_featured_image":true,"post_body":"

We said it. When it comes to HubSpot CMS development, we think that mega menus are an excellent way to organize your navigation and pre-qualify your prospects on your website by putting the information in front of them that is most relevant to their interests.

\n

 

\n

But not all mega menus are created equal. It’s important that you create a mega menu that’s strategic to the needs of your buyers, functional, usable and logical. While this can seem like a “no shit” statement, you’d be surprised how many times we’ve had clients approach us with a pretty design from their design team, only to find little to no research or thought was put into how the mega menu they’re requesting is structured.

Your website should be intentional. Manufacturers don’t put extra parts inside your vehicle or television that don’t function to make that machine work better and your website is no different. Every element of your website should be like a cog in a machine, working together to generate leads, further qualify existing leads or sell additional products and services to your existing customers. You should have a strategy session with your marketing agency or internal marketing department to break down buyer personas, aspects of the buyer journey, content and conversion opportunities. If you haven’t taken the time to do this, odds are good that you may be making one of these mega mistakes with your mega menus.

\n\n

Not having a comprehensive strategy

\n

We know your web designer is amazing, but do they really understand your buyer persona? You should approach your graphic or web design team with a strategic plan that breaks down where prospects on your website may need to go and what their goals and needs are. In order to do that, you have to first create that plan.

What does that look like? It looks like taking a deeper dive into their needs by exploring how they might answer the following questions:

\n

\n
1. As this target buyer persona, what am I looking to get out of my experience with this company’s website?
   As you probably know by now, the buyer’s journey has multiple stages. Regardless of where a prospect is at in their journey you need to make sure that you have information within your mega menu that caters to these different stages. Breaking down your resource topics or finding new ways to address pain points inside your navigation will go a long way towards catering to that experience.
   
   
\n
2. Are there specifics to my industry that I need to know when considering these products and services?
   Are there special regulations related to your products and services that mean certain industries must be treated in a special way?
   Do you have a special certification relevant to the financial, health or government industries? (Bonus 3 for 1)
   You’ll want to highlight your experience, because those prospects that find themselves in niche industries are often looking for partners that are experienced in those industries and the regulations associated with them.
   
   
\n
3. What are the biggest symptoms of my pain and where can I find information relevant to resolving that pain?
   This one is a slam dunk. Working with a well-qualified wordsmith will usually yield really amazing categories that you can place into your mega menu that really speak to your audience - find those most common pain points and work from there.
   
   
\n
4. I fit into a specific role - is there content that I would want to see relevant to that role?
   Industries are one thing, but don’t forget that organizing content by a persona’s role in the organization can be really useful too. Executives versus managers have very different perspectives and their concerns are often related but with very different focuses.
   
   
\n
5. How can I find the information most relevant to me with minimal effort?
   We operate in an ADD nation that is instant gratification. Keep this in mind when building your navigation and make sure the buyer’s bigger priorities are front and center in your navigation. Deep buyer persona research will help you unlock these insights.
   
   
\n

\n

Watch your language

\n

Using the right words is always essential when communicating with your prospects. When it comes to doing business, organizations seem to throw around jargon-heavy words related to their industry, products and services so much internally they don’t realize that their prospects have no idea what they’re talking about. Choosing the right words associated with a buyer's needs in your navigation is critical to the success of your mega menu. To determine what these are. Again, a talented wordsmith can help, but you’ll also want to do some buyer persona interviews with your target audience profiles. Incentivize your best customers or lost prospects to sit with you and understand their concerns, the words they’re using relative to your products and services and how they think.

There will be certain trigger words that help your buyers make their decisions, diagnose their pain points and better understand your offerings. Wherever possible, try to determine what those trigger words are so that you can compel your prospects to take action on your mega menu.

Are your buyers looking for specific solutions to their problems? Consider adding those problems and their solutions to your mega menu. If your products have specifically branded names that a brand new prospect may not be able to recognize, place them underneath a broader category, add an icon representing it or even consider adding a small description underneath, space allowing.

\n

Your mega menu is hover dependent

\n

Hover-over menus in theory are believed by some to be faster and easier for users to navigate. However, when it comes to mega menus, it can be a little presumptuous to think you know how a user is going to move their mouse. The majority of users pause their mouse prior to making the decision to move to the content that they want. Pre-empting this with hover-over pop up navigation can be annoying to users. It gets worse when an organization assumes they can push their website prospects through hover tunnels that require a mouse to be moved slowly and carefully across other elements to reach the information that they are looking for. By not allowing a user to move their cursor the way they want without the menu closing, you’re creating frustration and extra work to get to the information they’re looking for, which is the opposite of your goal. We almost always advise our clients to go with menus that require click through, but many still opt for hover, since it’s what they’re accustomed to.

Hover-over items on the edge of a menu are more difficult to click, requiring more focus and potentially increasing frustration. While this can sometimes be remedied by adding extra space to the menu to avoid it closing if a prospect misses their mark, it usually doesn’t make the hover-over menu much more usable.

Hover-over menus also don’t take into account mobile devices, so the functionality cannot translate well for users moving between devices. Rather than using a hover-over mega menu, we recommend that clients stick to mega menus that activate upon being clicked - which is a clear user intention, saving time and keeping your website visitors happy.

\n

You haven't considered images, buttons or logos

\n

Adding compelling images, icons or call to action buttons on your mega menus are a great way to add engagement and draw your user in while giving them context. Visual elements can help users quickly analyze information and understand more about the products, services and information that you’re offering inside your menu.

\n

You didn't plan for mobile

\n

Have you taken the opportunity to look at your website traffic by device lately? Odds are very good that over the years the percentage of users viewing your website from mobile devices has increased significantly. We always develop our websites with a “mobile first” approach. That means that if a company or agency approaches us with a design in mind, one of our first questions will be - where’s the mobile design? In many instances mobile traffic is outpacing desktop traffic significantly.

If you haven’t taken the time to create a mobile design, be sure that your developer talks through how your mega menu will translate to mobile devices and that you settle on the functionality prior to beginning the project. An involved mobile mega menu may increase the cost of the project, so you need to be ready to pay a little more to convert your mega menu over to a user friendly design that works on mobile devices and achieves your original goals.

\n

You're blocking critical conversion opportunities

\n

This goes without saying, but you don’t want your mega menu to deploy on landing pages. When it comes to pages that have very specific goals, like your resource downloads, webinar sign ups or other conversion opportunities, you’ll want to eliminate the navigation entirely or shift to a new format for those pages so that expanded mega menus don’t occupy the important conversion real estate that should be a prospect’s focus when they reach your landing page.

What’s the point of an amazing landing page if it’s only going to be covered up by a massive (hopefully not hover-over) mega menu? Take the time to do a little role play scenario and test your pages accordingly, not just inside your organization, but outside as well. Make sure that your designs make sense, don’t get in the way of the main focus of your website and offer expanded opportunities for conversion rather than covering them up.

We still think that mega menus are here to stay and for savvy organizations that are deep in resources and information for their website visitors, they’re quickly becoming an essential. Ask yourself what critical information is missing from your main website navigation and how a mega menu design could give your users exactly what they need. The right mega menu can increase the time a prospect spends on your website, may reduce your bounce rate and can even increase your visitor to lead conversions.

\n

If you need help with your mega menu or you've been wanting to redesign it more intuitively to serve the needs of your website visitors, we can help. 

\n

\n

 

\n

Tell us:
Do you prefer hover-over menus or click through menus?

\n

Let us know in the comments!

","rss_summary":"

We said it. When it comes to HubSpot CMS development, we think that mega menus are an excellent way to organize your navigation and pre-qualify your prospects on your website by putting the information in front of them that is most relevant to their interests.

\n

 

\n

But not all mega menus are created equal. It’s important that you create a mega menu that’s strategic to the needs of your buyers, functional, usable and logical. While this can seem like a “no shit” statement, you’d be surprised how many times we’ve had clients approach us with a pretty design from their design team, only to find little to no research or thought was put into how the mega menu they’re requesting is structured.

Your website should be intentional. Manufacturers don’t put extra parts inside your vehicle or television that don’t function to make that machine work better and your website is no different. Every element of your website should be like a cog in a machine, working together to generate leads, further qualify existing leads or sell additional products and services to your existing customers. You should have a strategy session with your marketing agency or internal marketing department to break down buyer personas, aspects of the buyer journey, content and conversion opportunities. If you haven’t taken the time to do this, odds are good that you may be making one of these mega mistakes with your mega menus.

\n","rss_body":"

We said it. When it comes to HubSpot CMS development, we think that mega menus are an excellent way to organize your navigation and pre-qualify your prospects on your website by putting the information in front of them that is most relevant to their interests.

\n

 

\n

But not all mega menus are created equal. It’s important that you create a mega menu that’s strategic to the needs of your buyers, functional, usable and logical. While this can seem like a “no shit” statement, you’d be surprised how many times we’ve had clients approach us with a pretty design from their design team, only to find little to no research or thought was put into how the mega menu they’re requesting is structured.

Your website should be intentional. Manufacturers don’t put extra parts inside your vehicle or television that don’t function to make that machine work better and your website is no different. Every element of your website should be like a cog in a machine, working together to generate leads, further qualify existing leads or sell additional products and services to your existing customers. You should have a strategy session with your marketing agency or internal marketing department to break down buyer personas, aspects of the buyer journey, content and conversion opportunities. If you haven’t taken the time to do this, odds are good that you may be making one of these mega mistakes with your mega menus.

\n\n

Not having a comprehensive strategy

\n

We know your web designer is amazing, but do they really understand your buyer persona? You should approach your graphic or web design team with a strategic plan that breaks down where prospects on your website may need to go and what their goals and needs are. In order to do that, you have to first create that plan.

What does that look like? It looks like taking a deeper dive into their needs by exploring how they might answer the following questions:

\n

\n
1. As this target buyer persona, what am I looking to get out of my experience with this company’s website?
   As you probably know by now, the buyer’s journey has multiple stages. Regardless of where a prospect is at in their journey you need to make sure that you have information within your mega menu that caters to these different stages. Breaking down your resource topics or finding new ways to address pain points inside your navigation will go a long way towards catering to that experience.
   
   
\n
2. Are there specifics to my industry that I need to know when considering these products and services?
   Are there special regulations related to your products and services that mean certain industries must be treated in a special way?
   Do you have a special certification relevant to the financial, health or government industries? (Bonus 3 for 1)
   You’ll want to highlight your experience, because those prospects that find themselves in niche industries are often looking for partners that are experienced in those industries and the regulations associated with them.
   
   
\n
3. What are the biggest symptoms of my pain and where can I find information relevant to resolving that pain?
   This one is a slam dunk. Working with a well-qualified wordsmith will usually yield really amazing categories that you can place into your mega menu that really speak to your audience - find those most common pain points and work from there.
   
   
\n
4. I fit into a specific role - is there content that I would want to see relevant to that role?
   Industries are one thing, but don’t forget that organizing content by a persona’s role in the organization can be really useful too. Executives versus managers have very different perspectives and their concerns are often related but with very different focuses.
   
   
\n
5. How can I find the information most relevant to me with minimal effort?
   We operate in an ADD nation that is instant gratification. Keep this in mind when building your navigation and make sure the buyer’s bigger priorities are front and center in your navigation. Deep buyer persona research will help you unlock these insights.
   
   
\n

\n

Watch your language

\n

Using the right words is always essential when communicating with your prospects. When it comes to doing business, organizations seem to throw around jargon-heavy words related to their industry, products and services so much internally they don’t realize that their prospects have no idea what they’re talking about. Choosing the right words associated with a buyer's needs in your navigation is critical to the success of your mega menu. To determine what these are. Again, a talented wordsmith can help, but you’ll also want to do some buyer persona interviews with your target audience profiles. Incentivize your best customers or lost prospects to sit with you and understand their concerns, the words they’re using relative to your products and services and how they think.

There will be certain trigger words that help your buyers make their decisions, diagnose their pain points and better understand your offerings. Wherever possible, try to determine what those trigger words are so that you can compel your prospects to take action on your mega menu.

Are your buyers looking for specific solutions to their problems? Consider adding those problems and their solutions to your mega menu. If your products have specifically branded names that a brand new prospect may not be able to recognize, place them underneath a broader category, add an icon representing it or even consider adding a small description underneath, space allowing.

\n

Your mega menu is hover dependent

\n

Hover-over menus in theory are believed by some to be faster and easier for users to navigate. However, when it comes to mega menus, it can be a little presumptuous to think you know how a user is going to move their mouse. The majority of users pause their mouse prior to making the decision to move to the content that they want. Pre-empting this with hover-over pop up navigation can be annoying to users. It gets worse when an organization assumes they can push their website prospects through hover tunnels that require a mouse to be moved slowly and carefully across other elements to reach the information that they are looking for. By not allowing a user to move their cursor the way they want without the menu closing, you’re creating frustration and extra work to get to the information they’re looking for, which is the opposite of your goal. We almost always advise our clients to go with menus that require click through, but many still opt for hover, since it’s what they’re accustomed to.

Hover-over items on the edge of a menu are more difficult to click, requiring more focus and potentially increasing frustration. While this can sometimes be remedied by adding extra space to the menu to avoid it closing if a prospect misses their mark, it usually doesn’t make the hover-over menu much more usable.

Hover-over menus also don’t take into account mobile devices, so the functionality cannot translate well for users moving between devices. Rather than using a hover-over mega menu, we recommend that clients stick to mega menus that activate upon being clicked - which is a clear user intention, saving time and keeping your website visitors happy.

\n

You haven't considered images, buttons or logos

\n

Adding compelling images, icons or call to action buttons on your mega menus are a great way to add engagement and draw your user in while giving them context. Visual elements can help users quickly analyze information and understand more about the products, services and information that you’re offering inside your menu.

\n

You didn't plan for mobile

\n

Have you taken the opportunity to look at your website traffic by device lately? Odds are very good that over the years the percentage of users viewing your website from mobile devices has increased significantly. We always develop our websites with a “mobile first” approach. That means that if a company or agency approaches us with a design in mind, one of our first questions will be - where’s the mobile design? In many instances mobile traffic is outpacing desktop traffic significantly.

If you haven’t taken the time to create a mobile design, be sure that your developer talks through how your mega menu will translate to mobile devices and that you settle on the functionality prior to beginning the project. An involved mobile mega menu may increase the cost of the project, so you need to be ready to pay a little more to convert your mega menu over to a user friendly design that works on mobile devices and achieves your original goals.

\n

You're blocking critical conversion opportunities

\n

This goes without saying, but you don’t want your mega menu to deploy on landing pages. When it comes to pages that have very specific goals, like your resource downloads, webinar sign ups or other conversion opportunities, you’ll want to eliminate the navigation entirely or shift to a new format for those pages so that expanded mega menus don’t occupy the important conversion real estate that should be a prospect’s focus when they reach your landing page.

What’s the point of an amazing landing page if it’s only going to be covered up by a massive (hopefully not hover-over) mega menu? Take the time to do a little role play scenario and test your pages accordingly, not just inside your organization, but outside as well. Make sure that your designs make sense, don’t get in the way of the main focus of your website and offer expanded opportunities for conversion rather than covering them up.

We still think that mega menus are here to stay and for savvy organizations that are deep in resources and information for their website visitors, they’re quickly becoming an essential. Ask yourself what critical information is missing from your main website navigation and how a mega menu design could give your users exactly what they need. The right mega menu can increase the time a prospect spends on your website, may reduce your bounce rate and can even increase your visitor to lead conversions.

\n

If you need help with your mega menu or you've been wanting to redesign it more intuitively to serve the needs of your website visitors, we can help. 

\n

\n

 

\n

Tell us:
Do you prefer hover-over menus or click through menus?

\n

Let us know in the comments!

","tag_ids":[62770442823,81857606195,82133680259,94338241715],"topic_ids":[62770442823,81857606195,82133680259,94338241715],"post_summary":"

We said it. When it comes to HubSpot CMS development, we think that mega menus are an excellent way to organize your navigation and pre-qualify your prospects on your website by putting the information in front of them that is most relevant to their interests.

\n

 

\n

But not all mega menus are created equal. It’s important that you create a mega menu that’s strategic to the needs of your buyers, functional, usable and logical. While this can seem like a “no shit” statement, you’d be surprised how many times we’ve had clients approach us with a pretty design from their design team, only to find little to no research or thought was put into how the mega menu they’re requesting is structured.

Your website should be intentional. Manufacturers don’t put extra parts inside your vehicle or television that don’t function to make that machine work better and your website is no different. Every element of your website should be like a cog in a machine, working together to generate leads, further qualify existing leads or sell additional products and services to your existing customers. You should have a strategy session with your marketing agency or internal marketing department to break down buyer personas, aspects of the buyer journey, content and conversion opportunities. If you haven’t taken the time to do this, odds are good that you may be making one of these mega mistakes with your mega menus.

\n","blog_post_schedule_task_uid":null,"blog_publish_to_social_media_task":"DONE_NOT_SENT","blog_publish_instant_email_task_uid":null,"blog_publish_instant_email_campaign_id":null,"blog_publish_instant_email_retry_count":null,"keywords":[],"head_html":null,"footer_html":null,"attached_stylesheets":[],"enable_domain_stylesheets":null,"include_default_custom_css":null,"meta_description":"Mega menus are a great way to help your website visitors find what they need, but be sure you don't make these mistakes:","meta_keywords":null,"layout_sections":{},"past_mab_experiment_ids":[],"deleted_by":null,"featured_image_alt_text":"","enable_layout_stylesheets":null,"tweet":null,"tweet_at":null,"campaign_name":null,"campaign_utm":null,"tweet_immediately":false,"publish_immediately":true,"security_state":"NONE","scheduled_update_date":0,"placement_guids":[],"property_for_dynamic_page_title":null,"property_for_dynamic_page_slug":null,"property_for_dynamic_page_meta_description":null,"property_for_dynamic_page_featured_image":null,"property_for_dynamic_page_canonical_url":null,"preview_image_src":null,"legacy_blog_tabid":null,"legacy_post_guid":null,"performable_variation_letter":null,"style_override_id":null,"has_user_changes":true,"css":{},"css_text":"","unpublished_at":0,"published_by_id":61310730,"allowed_slug_conflict":false,"ai_features":null,"link_rel_canonical_url":"","page_redirected":false,"page_expiry_enabled":null,"page_expiry_date":null,"page_expiry_redirect_id":null,"page_expiry_redirect_url":null,"deleted_by_id":null,"state_when_deleted":null,"cloned_from":null,"staged_from":null,"personas":[],"compose_body":null,"featured_image":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-mega%20menu%20mistakes2.png","featured_image_width":1080,"featured_image_height":1080,"publish_timezone_offset":null,"theme_settings_values":null,"password":null,"header":null,"published_at":1722384440382,"last_edit_session_id":null,"last_edit_update_id":null,"created_by_agent":null},"metaDescription":"Mega menus are a great way to help your website visitors find what they need, but be sure you don't make these mistakes:","metaKeywords":null,"name":"HubSpot CMS Development Tips: Mega Mistakes with Mega Menus","nextPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/Screenshots/mega-menu-staffing.jpg","nextPostFeaturedImageAltText":"hubspot cms development mega menu","nextPostName":"HubSpot CMS Development Trends: Mega Menus are Here to Stay","nextPostSlug":"blogs/hubspot-cms-development-trends-mega-menus-are-here-to-stay","pageExpiryDate":null,"pageExpiryEnabled":null,"pageExpiryRedirectId":null,"pageExpiryRedirectUrl":null,"pageRedirected":false,"pageTitle":"HubSpot CMS Development Tips: Mega Mistakes with Mega Menus","parentBlog":{"absoluteUrl":"https://deckerdevs.com/blogs","allowComments":true,"ampBodyColor":"#404040","ampBodyFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampBodyFontSize":"18","ampCustomCss":"","ampHeaderBackgroundColor":"#ffffff","ampHeaderColor":"#1e1e1e","ampHeaderFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampHeaderFontSize":"36","ampLinkColor":"#416bb3","ampLogoAlt":"","ampLogoHeight":0,"ampLogoSrc":"","ampLogoWidth":0,"analyticsPageId":62179259185,"attachedStylesheets":[],"audienceAccess":"PUBLIC","businessUnitId":null,"captchaAfterDays":7,"captchaAlways":false,"categoryId":3,"cdnPurgeEmbargoTime":null,"closeCommentsOlder":0,"commentDateFormat":"medium","commentFormGuid":"cb653aa1-3db4-4167-9b59-744c46d49682","commentMaxThreadDepth":3,"commentModeration":false,"commentNotificationEmails":["nicholas@deckerdevs.com","jessica@deckerdevs.com"],"commentShouldCreateContact":true,"commentVerificationText":"Thanks for participating in this conversation! We look forward to responding and to assisting where we can","cosObjectType":"BLOG","created":1639786189589,"createdDateTime":1639786189589,"dailyNotificationEmailId":null,"dateFormattingLanguage":null,"defaultGroupStyleId":"","defaultNotificationFromName":"","defaultNotificationReplyTo":"","deletedAt":0,"description":"rev up your hubspot system to the max! deckerdevs' turbo-charged blog is your ultimate guide to harnessing the full potential of hubspot development. unleash the marketing magic with ingenious tips, tricks, and hacks. get ready to level up your hubspot game!","domain":"","domainWhenPublished":"deckerdevs.com","emailApiSubscriptionId":null,"enableGoogleAmpOutput":false,"enableSocialAutoPublishing":false,"generateJsonLdEnabled":true,"header":null,"htmlFooter":"","htmlFooterIsShared":true,"htmlHead":"","htmlHeadIsShared":true,"htmlKeywords":[],"htmlTitle":"deckerdevs thought nuggets","id":62179259185,"ilsSubscriptionListsByType":{},"instantNotificationEmailId":null,"itemLayoutId":null,"itemTemplateIsShared":false,"itemTemplatePath":"deckerdevs-theme/templates/blog-content.html","label":"deckerdevs live blog","language":"en","legacyGuid":null,"legacyModuleId":null,"legacyTabId":null,"listingLayoutId":null,"listingPageId":62179259186,"listingTemplatePath":"","liveDomain":"deckerdevs.com","monthFilterFormat":"MMMM yyyy","monthlyNotificationEmailId":null,"name":"deckerdevs live blog","parentBlogUpdateTaskId":null,"portalId":6534445,"postHtmlFooter":"","postHtmlHead":"","postsPerListingPage":9,"postsPerRssFeed":10,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publicTitle":"thought nuggets","publishDateFormat":"medium","resolvedDomain":"deckerdevs.com","rootUrl":"https://deckerdevs.com/blogs","rssCustomFeed":null,"rssDescription":null,"rssItemFooter":null,"rssItemHeader":null,"settingsOverrides":{"itemLayoutId":false,"itemTemplatePath":false,"itemTemplateIsShared":false,"listingLayoutId":false,"listingTemplatePath":false,"postsPerListingPage":false,"showSummaryInListing":false,"useFeaturedImageInSummary":false,"htmlHead":false,"postHtmlHead":false,"htmlHeadIsShared":false,"htmlFooter":false,"listingPageHtmlFooter":false,"postHtmlFooter":false,"htmlFooterIsShared":false,"attachedStylesheets":false,"postsPerRssFeed":false,"showSummaryInRss":false,"showSummaryInEmails":false,"showSummariesInEmails":false,"allowComments":false,"commentShouldCreateContact":false,"commentModeration":false,"closeCommentsOlder":false,"commentNotificationEmails":false,"commentMaxThreadDepth":false,"commentVerificationText":false,"socialAccountTwitter":false,"showSocialLinkTwitter":false,"showSocialLinkLinkedin":false,"showSocialLinkFacebook":false,"enableGoogleAmpOutput":false,"ampLogoSrc":false,"ampLogoHeight":false,"ampLogoWidth":false,"ampLogoAlt":false,"ampHeaderFont":false,"ampHeaderFontSize":false,"ampHeaderColor":false,"ampHeaderBackgroundColor":false,"ampBodyFont":false,"ampBodyFontSize":false,"ampBodyColor":false,"ampLinkColor":false,"generateJsonLdEnabled":false},"showSocialLinkFacebook":true,"showSocialLinkLinkedin":true,"showSocialLinkTwitter":true,"showSummaryInEmails":true,"showSummaryInListing":true,"showSummaryInRss":true,"siteId":null,"slug":"blogs","socialAccountTwitter":"","state":null,"subscriptionContactsProperty":null,"subscriptionEmailType":null,"subscriptionFormGuid":null,"subscriptionListsByType":{},"title":null,"translatedFromId":null,"translations":{},"updated":1712344124471,"updatedDateTime":1712344124471,"urlBase":"deckerdevs.com/blogs","urlSegments":{"all":"all","archive":"archive","author":"author","page":"page","tag":"tag"},"useFeaturedImageInSummary":true,"usesDefaultTemplate":false,"weeklyNotificationEmailId":null},"password":null,"pastMabExperimentIds":[],"performableGuid":null,"performableVariationLetter":null,"personas":[],"placementGuids":[],"portableKey":null,"portalId":6534445,"position":null,"postBody":"

We said it. When it comes to HubSpot CMS development, we think that mega menus are an excellent way to organize your navigation and pre-qualify your prospects on your website by putting the information in front of them that is most relevant to their interests.

\n

 

\n

But not all mega menus are created equal. It’s important that you create a mega menu that’s strategic to the needs of your buyers, functional, usable and logical. While this can seem like a “no shit” statement, you’d be surprised how many times we’ve had clients approach us with a pretty design from their design team, only to find little to no research or thought was put into how the mega menu they’re requesting is structured.

Your website should be intentional. Manufacturers don’t put extra parts inside your vehicle or television that don’t function to make that machine work better and your website is no different. Every element of your website should be like a cog in a machine, working together to generate leads, further qualify existing leads or sell additional products and services to your existing customers. You should have a strategy session with your marketing agency or internal marketing department to break down buyer personas, aspects of the buyer journey, content and conversion opportunities. If you haven’t taken the time to do this, odds are good that you may be making one of these mega mistakes with your mega menus.

\n\n

Not having a comprehensive strategy

\n

We know your web designer is amazing, but do they really understand your buyer persona? You should approach your graphic or web design team with a strategic plan that breaks down where prospects on your website may need to go and what their goals and needs are. In order to do that, you have to first create that plan.

What does that look like? It looks like taking a deeper dive into their needs by exploring how they might answer the following questions:

\n

\n
1. As this target buyer persona, what am I looking to get out of my experience with this company’s website?
   As you probably know by now, the buyer’s journey has multiple stages. Regardless of where a prospect is at in their journey you need to make sure that you have information within your mega menu that caters to these different stages. Breaking down your resource topics or finding new ways to address pain points inside your navigation will go a long way towards catering to that experience.
   
   
\n
2. Are there specifics to my industry that I need to know when considering these products and services?
   Are there special regulations related to your products and services that mean certain industries must be treated in a special way?
   Do you have a special certification relevant to the financial, health or government industries? (Bonus 3 for 1)
   You’ll want to highlight your experience, because those prospects that find themselves in niche industries are often looking for partners that are experienced in those industries and the regulations associated with them.
   
   
\n
3. What are the biggest symptoms of my pain and where can I find information relevant to resolving that pain?
   This one is a slam dunk. Working with a well-qualified wordsmith will usually yield really amazing categories that you can place into your mega menu that really speak to your audience - find those most common pain points and work from there.
   
   
\n
4. I fit into a specific role - is there content that I would want to see relevant to that role?
   Industries are one thing, but don’t forget that organizing content by a persona’s role in the organization can be really useful too. Executives versus managers have very different perspectives and their concerns are often related but with very different focuses.
   
   
\n
5. How can I find the information most relevant to me with minimal effort?
   We operate in an ADD nation that is instant gratification. Keep this in mind when building your navigation and make sure the buyer’s bigger priorities are front and center in your navigation. Deep buyer persona research will help you unlock these insights.
   
   
\n

\n

Watch your language

\n

Using the right words is always essential when communicating with your prospects. When it comes to doing business, organizations seem to throw around jargon-heavy words related to their industry, products and services so much internally they don’t realize that their prospects have no idea what they’re talking about. Choosing the right words associated with a buyer's needs in your navigation is critical to the success of your mega menu. To determine what these are. Again, a talented wordsmith can help, but you’ll also want to do some buyer persona interviews with your target audience profiles. Incentivize your best customers or lost prospects to sit with you and understand their concerns, the words they’re using relative to your products and services and how they think.

There will be certain trigger words that help your buyers make their decisions, diagnose their pain points and better understand your offerings. Wherever possible, try to determine what those trigger words are so that you can compel your prospects to take action on your mega menu.

Are your buyers looking for specific solutions to their problems? Consider adding those problems and their solutions to your mega menu. If your products have specifically branded names that a brand new prospect may not be able to recognize, place them underneath a broader category, add an icon representing it or even consider adding a small description underneath, space allowing.

\n

Your mega menu is hover dependent

\n

Hover-over menus in theory are believed by some to be faster and easier for users to navigate. However, when it comes to mega menus, it can be a little presumptuous to think you know how a user is going to move their mouse. The majority of users pause their mouse prior to making the decision to move to the content that they want. Pre-empting this with hover-over pop up navigation can be annoying to users. It gets worse when an organization assumes they can push their website prospects through hover tunnels that require a mouse to be moved slowly and carefully across other elements to reach the information that they are looking for. By not allowing a user to move their cursor the way they want without the menu closing, you’re creating frustration and extra work to get to the information they’re looking for, which is the opposite of your goal. We almost always advise our clients to go with menus that require click through, but many still opt for hover, since it’s what they’re accustomed to.

Hover-over items on the edge of a menu are more difficult to click, requiring more focus and potentially increasing frustration. While this can sometimes be remedied by adding extra space to the menu to avoid it closing if a prospect misses their mark, it usually doesn’t make the hover-over menu much more usable.

Hover-over menus also don’t take into account mobile devices, so the functionality cannot translate well for users moving between devices. Rather than using a hover-over mega menu, we recommend that clients stick to mega menus that activate upon being clicked - which is a clear user intention, saving time and keeping your website visitors happy.

\n

You haven't considered images, buttons or logos

\n

Adding compelling images, icons or call to action buttons on your mega menus are a great way to add engagement and draw your user in while giving them context. Visual elements can help users quickly analyze information and understand more about the products, services and information that you’re offering inside your menu.

\n

You didn't plan for mobile

\n

Have you taken the opportunity to look at your website traffic by device lately? Odds are very good that over the years the percentage of users viewing your website from mobile devices has increased significantly. We always develop our websites with a “mobile first” approach. That means that if a company or agency approaches us with a design in mind, one of our first questions will be - where’s the mobile design? In many instances mobile traffic is outpacing desktop traffic significantly.

If you haven’t taken the time to create a mobile design, be sure that your developer talks through how your mega menu will translate to mobile devices and that you settle on the functionality prior to beginning the project. An involved mobile mega menu may increase the cost of the project, so you need to be ready to pay a little more to convert your mega menu over to a user friendly design that works on mobile devices and achieves your original goals.

\n

You're blocking critical conversion opportunities

\n

This goes without saying, but you don’t want your mega menu to deploy on landing pages. When it comes to pages that have very specific goals, like your resource downloads, webinar sign ups or other conversion opportunities, you’ll want to eliminate the navigation entirely or shift to a new format for those pages so that expanded mega menus don’t occupy the important conversion real estate that should be a prospect’s focus when they reach your landing page.

What’s the point of an amazing landing page if it’s only going to be covered up by a massive (hopefully not hover-over) mega menu? Take the time to do a little role play scenario and test your pages accordingly, not just inside your organization, but outside as well. Make sure that your designs make sense, don’t get in the way of the main focus of your website and offer expanded opportunities for conversion rather than covering them up.

We still think that mega menus are here to stay and for savvy organizations that are deep in resources and information for their website visitors, they’re quickly becoming an essential. Ask yourself what critical information is missing from your main website navigation and how a mega menu design could give your users exactly what they need. The right mega menu can increase the time a prospect spends on your website, may reduce your bounce rate and can even increase your visitor to lead conversions.

\n

If you need help with your mega menu or you've been wanting to redesign it more intuitively to serve the needs of your website visitors, we can help. 

\n

\n

 

\n

Tell us:
Do you prefer hover-over menus or click through menus?

\n

Let us know in the comments!

","postBodyRss":"

We said it. When it comes to HubSpot CMS development, we think that mega menus are an excellent way to organize your navigation and pre-qualify your prospects on your website by putting the information in front of them that is most relevant to their interests.

\n

 

\n

But not all mega menus are created equal. It’s important that you create a mega menu that’s strategic to the needs of your buyers, functional, usable and logical. While this can seem like a “no shit” statement, you’d be surprised how many times we’ve had clients approach us with a pretty design from their design team, only to find little to no research or thought was put into how the mega menu they’re requesting is structured.

Your website should be intentional. Manufacturers don’t put extra parts inside your vehicle or television that don’t function to make that machine work better and your website is no different. Every element of your website should be like a cog in a machine, working together to generate leads, further qualify existing leads or sell additional products and services to your existing customers. You should have a strategy session with your marketing agency or internal marketing department to break down buyer personas, aspects of the buyer journey, content and conversion opportunities. If you haven’t taken the time to do this, odds are good that you may be making one of these mega mistakes with your mega menus.

\n\n

Not having a comprehensive strategy

\n

We know your web designer is amazing, but do they really understand your buyer persona? You should approach your graphic or web design team with a strategic plan that breaks down where prospects on your website may need to go and what their goals and needs are. In order to do that, you have to first create that plan.

What does that look like? It looks like taking a deeper dive into their needs by exploring how they might answer the following questions:

\n

\n
1. As this target buyer persona, what am I looking to get out of my experience with this company’s website?
   As you probably know by now, the buyer’s journey has multiple stages. Regardless of where a prospect is at in their journey you need to make sure that you have information within your mega menu that caters to these different stages. Breaking down your resource topics or finding new ways to address pain points inside your navigation will go a long way towards catering to that experience.
   
   
\n
2. Are there specifics to my industry that I need to know when considering these products and services?
   Are there special regulations related to your products and services that mean certain industries must be treated in a special way?
   Do you have a special certification relevant to the financial, health or government industries? (Bonus 3 for 1)
   You’ll want to highlight your experience, because those prospects that find themselves in niche industries are often looking for partners that are experienced in those industries and the regulations associated with them.
   
   
\n
3. What are the biggest symptoms of my pain and where can I find information relevant to resolving that pain?
   This one is a slam dunk. Working with a well-qualified wordsmith will usually yield really amazing categories that you can place into your mega menu that really speak to your audience - find those most common pain points and work from there.
   
   
\n
4. I fit into a specific role - is there content that I would want to see relevant to that role?
   Industries are one thing, but don’t forget that organizing content by a persona’s role in the organization can be really useful too. Executives versus managers have very different perspectives and their concerns are often related but with very different focuses.
   
   
\n
5. How can I find the information most relevant to me with minimal effort?
   We operate in an ADD nation that is instant gratification. Keep this in mind when building your navigation and make sure the buyer’s bigger priorities are front and center in your navigation. Deep buyer persona research will help you unlock these insights.
   
   
\n

\n

Watch your language

\n

Using the right words is always essential when communicating with your prospects. When it comes to doing business, organizations seem to throw around jargon-heavy words related to their industry, products and services so much internally they don’t realize that their prospects have no idea what they’re talking about. Choosing the right words associated with a buyer's needs in your navigation is critical to the success of your mega menu. To determine what these are. Again, a talented wordsmith can help, but you’ll also want to do some buyer persona interviews with your target audience profiles. Incentivize your best customers or lost prospects to sit with you and understand their concerns, the words they’re using relative to your products and services and how they think.

There will be certain trigger words that help your buyers make their decisions, diagnose their pain points and better understand your offerings. Wherever possible, try to determine what those trigger words are so that you can compel your prospects to take action on your mega menu.

Are your buyers looking for specific solutions to their problems? Consider adding those problems and their solutions to your mega menu. If your products have specifically branded names that a brand new prospect may not be able to recognize, place them underneath a broader category, add an icon representing it or even consider adding a small description underneath, space allowing.

\n

Your mega menu is hover dependent

\n

Hover-over menus in theory are believed by some to be faster and easier for users to navigate. However, when it comes to mega menus, it can be a little presumptuous to think you know how a user is going to move their mouse. The majority of users pause their mouse prior to making the decision to move to the content that they want. Pre-empting this with hover-over pop up navigation can be annoying to users. It gets worse when an organization assumes they can push their website prospects through hover tunnels that require a mouse to be moved slowly and carefully across other elements to reach the information that they are looking for. By not allowing a user to move their cursor the way they want without the menu closing, you’re creating frustration and extra work to get to the information they’re looking for, which is the opposite of your goal. We almost always advise our clients to go with menus that require click through, but many still opt for hover, since it’s what they’re accustomed to.

Hover-over items on the edge of a menu are more difficult to click, requiring more focus and potentially increasing frustration. While this can sometimes be remedied by adding extra space to the menu to avoid it closing if a prospect misses their mark, it usually doesn’t make the hover-over menu much more usable.

Hover-over menus also don’t take into account mobile devices, so the functionality cannot translate well for users moving between devices. Rather than using a hover-over mega menu, we recommend that clients stick to mega menus that activate upon being clicked - which is a clear user intention, saving time and keeping your website visitors happy.

\n

You haven't considered images, buttons or logos

\n

Adding compelling images, icons or call to action buttons on your mega menus are a great way to add engagement and draw your user in while giving them context. Visual elements can help users quickly analyze information and understand more about the products, services and information that you’re offering inside your menu.

\n

You didn't plan for mobile

\n

Have you taken the opportunity to look at your website traffic by device lately? Odds are very good that over the years the percentage of users viewing your website from mobile devices has increased significantly. We always develop our websites with a “mobile first” approach. That means that if a company or agency approaches us with a design in mind, one of our first questions will be - where’s the mobile design? In many instances mobile traffic is outpacing desktop traffic significantly.

If you haven’t taken the time to create a mobile design, be sure that your developer talks through how your mega menu will translate to mobile devices and that you settle on the functionality prior to beginning the project. An involved mobile mega menu may increase the cost of the project, so you need to be ready to pay a little more to convert your mega menu over to a user friendly design that works on mobile devices and achieves your original goals.

\n

You're blocking critical conversion opportunities

\n

This goes without saying, but you don’t want your mega menu to deploy on landing pages. When it comes to pages that have very specific goals, like your resource downloads, webinar sign ups or other conversion opportunities, you’ll want to eliminate the navigation entirely or shift to a new format for those pages so that expanded mega menus don’t occupy the important conversion real estate that should be a prospect’s focus when they reach your landing page.

What’s the point of an amazing landing page if it’s only going to be covered up by a massive (hopefully not hover-over) mega menu? Take the time to do a little role play scenario and test your pages accordingly, not just inside your organization, but outside as well. Make sure that your designs make sense, don’t get in the way of the main focus of your website and offer expanded opportunities for conversion rather than covering them up.

We still think that mega menus are here to stay and for savvy organizations that are deep in resources and information for their website visitors, they’re quickly becoming an essential. Ask yourself what critical information is missing from your main website navigation and how a mega menu design could give your users exactly what they need. The right mega menu can increase the time a prospect spends on your website, may reduce your bounce rate and can even increase your visitor to lead conversions.

\n

If you need help with your mega menu or you've been wanting to redesign it more intuitively to serve the needs of your website visitors, we can help. 

\n

\n

 

\n

Tell us:
Do you prefer hover-over menus or click through menus?

\n

Let us know in the comments!

","postEmailContent":"

We said it. When it comes to HubSpot CMS development, we think that mega menus are an excellent way to organize your navigation and pre-qualify your prospects on your website by putting the information in front of them that is most relevant to their interests.

\n

 

\n

But not all mega menus are created equal. It’s important that you create a mega menu that’s strategic to the needs of your buyers, functional, usable and logical. While this can seem like a “no shit” statement, you’d be surprised how many times we’ve had clients approach us with a pretty design from their design team, only to find little to no research or thought was put into how the mega menu they’re requesting is structured.

Your website should be intentional. Manufacturers don’t put extra parts inside your vehicle or television that don’t function to make that machine work better and your website is no different. Every element of your website should be like a cog in a machine, working together to generate leads, further qualify existing leads or sell additional products and services to your existing customers. You should have a strategy session with your marketing agency or internal marketing department to break down buyer personas, aspects of the buyer journey, content and conversion opportunities. If you haven’t taken the time to do this, odds are good that you may be making one of these mega mistakes with your mega menus.

","postFeaturedImageIfEnabled":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-mega%20menu%20mistakes2.png","postListContent":"

We said it. When it comes to HubSpot CMS development, we think that mega menus are an excellent way to organize your navigation and pre-qualify your prospects on your website by putting the information in front of them that is most relevant to their interests.

\n

 

\n

But not all mega menus are created equal. It’s important that you create a mega menu that’s strategic to the needs of your buyers, functional, usable and logical. While this can seem like a “no shit” statement, you’d be surprised how many times we’ve had clients approach us with a pretty design from their design team, only to find little to no research or thought was put into how the mega menu they’re requesting is structured.

Your website should be intentional. Manufacturers don’t put extra parts inside your vehicle or television that don’t function to make that machine work better and your website is no different. Every element of your website should be like a cog in a machine, working together to generate leads, further qualify existing leads or sell additional products and services to your existing customers. You should have a strategy session with your marketing agency or internal marketing department to break down buyer personas, aspects of the buyer journey, content and conversion opportunities. If you haven’t taken the time to do this, odds are good that you may be making one of these mega mistakes with your mega menus.

","postListSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-mega%20menu%20mistakes2.png","postRssContent":"

We said it. When it comes to HubSpot CMS development, we think that mega menus are an excellent way to organize your navigation and pre-qualify your prospects on your website by putting the information in front of them that is most relevant to their interests.

\n

 

\n

But not all mega menus are created equal. It’s important that you create a mega menu that’s strategic to the needs of your buyers, functional, usable and logical. While this can seem like a “no shit” statement, you’d be surprised how many times we’ve had clients approach us with a pretty design from their design team, only to find little to no research or thought was put into how the mega menu they’re requesting is structured.

Your website should be intentional. Manufacturers don’t put extra parts inside your vehicle or television that don’t function to make that machine work better and your website is no different. Every element of your website should be like a cog in a machine, working together to generate leads, further qualify existing leads or sell additional products and services to your existing customers. You should have a strategy session with your marketing agency or internal marketing department to break down buyer personas, aspects of the buyer journey, content and conversion opportunities. If you haven’t taken the time to do this, odds are good that you may be making one of these mega mistakes with your mega menus.

","postRssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-mega%20menu%20mistakes2.png","postSummary":"

We said it. When it comes to HubSpot CMS development, we think that mega menus are an excellent way to organize your navigation and pre-qualify your prospects on your website by putting the information in front of them that is most relevant to their interests.

\n

 

\n

But not all mega menus are created equal. It’s important that you create a mega menu that’s strategic to the needs of your buyers, functional, usable and logical. While this can seem like a “no shit” statement, you’d be surprised how many times we’ve had clients approach us with a pretty design from their design team, only to find little to no research or thought was put into how the mega menu they’re requesting is structured.

Your website should be intentional. Manufacturers don’t put extra parts inside your vehicle or television that don’t function to make that machine work better and your website is no different. Every element of your website should be like a cog in a machine, working together to generate leads, further qualify existing leads or sell additional products and services to your existing customers. You should have a strategy session with your marketing agency or internal marketing department to break down buyer personas, aspects of the buyer journey, content and conversion opportunities. If you haven’t taken the time to do this, odds are good that you may be making one of these mega mistakes with your mega menus.

\n","postSummaryRss":"

We said it. When it comes to HubSpot CMS development, we think that mega menus are an excellent way to organize your navigation and pre-qualify your prospects on your website by putting the information in front of them that is most relevant to their interests.

\n

 

\n

But not all mega menus are created equal. It’s important that you create a mega menu that’s strategic to the needs of your buyers, functional, usable and logical. While this can seem like a “no shit” statement, you’d be surprised how many times we’ve had clients approach us with a pretty design from their design team, only to find little to no research or thought was put into how the mega menu they’re requesting is structured.

Your website should be intentional. Manufacturers don’t put extra parts inside your vehicle or television that don’t function to make that machine work better and your website is no different. Every element of your website should be like a cog in a machine, working together to generate leads, further qualify existing leads or sell additional products and services to your existing customers. You should have a strategy session with your marketing agency or internal marketing department to break down buyer personas, aspects of the buyer journey, content and conversion opportunities. If you haven’t taken the time to do this, odds are good that you may be making one of these mega mistakes with your mega menus.

","postTemplate":"deckerdevs-theme/templates/blog-content.html","previewImageSrc":null,"previewKey":"SWZXDlNZ","previousPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/63.png","previousPostFeaturedImageAltText":"hubspot cms developer","previousPostName":"7 HubSpot CMS Developer Interview Questions to Ask: Part 1","previousPostSlug":"blogs/7-hubspot-cms-developer-interview-questions-to-ask-part-1","processingStatus":"PUBLISHED","propertyForDynamicPageCanonicalUrl":null,"propertyForDynamicPageFeaturedImage":null,"propertyForDynamicPageMetaDescription":null,"propertyForDynamicPageSlug":null,"propertyForDynamicPageTitle":null,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publishDate":1660665547000,"publishDateLocalTime":1660665547000,"publishDateLocalized":{"date":1660665547000,"format":"medium","language":null},"publishImmediately":true,"publishTimezoneOffset":null,"publishedAt":1722384440382,"publishedByEmail":null,"publishedById":61310730,"publishedByName":null,"publishedUrl":"https://deckerdevs.com/blogs/hubspot-cms-development-tips-mega-mistakes-with-mega-menus","resolvedDomain":"deckerdevs.com","resolvedLanguage":null,"rssBody":"

We said it. When it comes to HubSpot CMS development, we think that mega menus are an excellent way to organize your navigation and pre-qualify your prospects on your website by putting the information in front of them that is most relevant to their interests.

\n

 

\n

But not all mega menus are created equal. It’s important that you create a mega menu that’s strategic to the needs of your buyers, functional, usable and logical. While this can seem like a “no shit” statement, you’d be surprised how many times we’ve had clients approach us with a pretty design from their design team, only to find little to no research or thought was put into how the mega menu they’re requesting is structured.

Your website should be intentional. Manufacturers don’t put extra parts inside your vehicle or television that don’t function to make that machine work better and your website is no different. Every element of your website should be like a cog in a machine, working together to generate leads, further qualify existing leads or sell additional products and services to your existing customers. You should have a strategy session with your marketing agency or internal marketing department to break down buyer personas, aspects of the buyer journey, content and conversion opportunities. If you haven’t taken the time to do this, odds are good that you may be making one of these mega mistakes with your mega menus.

\n\n

Not having a comprehensive strategy

\n

We know your web designer is amazing, but do they really understand your buyer persona? You should approach your graphic or web design team with a strategic plan that breaks down where prospects on your website may need to go and what their goals and needs are. In order to do that, you have to first create that plan.

What does that look like? It looks like taking a deeper dive into their needs by exploring how they might answer the following questions:

\n

\n
1. As this target buyer persona, what am I looking to get out of my experience with this company’s website?
   As you probably know by now, the buyer’s journey has multiple stages. Regardless of where a prospect is at in their journey you need to make sure that you have information within your mega menu that caters to these different stages. Breaking down your resource topics or finding new ways to address pain points inside your navigation will go a long way towards catering to that experience.
   
   
\n
2. Are there specifics to my industry that I need to know when considering these products and services?
   Are there special regulations related to your products and services that mean certain industries must be treated in a special way?
   Do you have a special certification relevant to the financial, health or government industries? (Bonus 3 for 1)
   You’ll want to highlight your experience, because those prospects that find themselves in niche industries are often looking for partners that are experienced in those industries and the regulations associated with them.
   
   
\n
3. What are the biggest symptoms of my pain and where can I find information relevant to resolving that pain?
   This one is a slam dunk. Working with a well-qualified wordsmith will usually yield really amazing categories that you can place into your mega menu that really speak to your audience - find those most common pain points and work from there.
   
   
\n
4. I fit into a specific role - is there content that I would want to see relevant to that role?
   Industries are one thing, but don’t forget that organizing content by a persona’s role in the organization can be really useful too. Executives versus managers have very different perspectives and their concerns are often related but with very different focuses.
   
   
\n
5. How can I find the information most relevant to me with minimal effort?
   We operate in an ADD nation that is instant gratification. Keep this in mind when building your navigation and make sure the buyer’s bigger priorities are front and center in your navigation. Deep buyer persona research will help you unlock these insights.
   
   
\n

\n

Watch your language

\n

Using the right words is always essential when communicating with your prospects. When it comes to doing business, organizations seem to throw around jargon-heavy words related to their industry, products and services so much internally they don’t realize that their prospects have no idea what they’re talking about. Choosing the right words associated with a buyer's needs in your navigation is critical to the success of your mega menu. To determine what these are. Again, a talented wordsmith can help, but you’ll also want to do some buyer persona interviews with your target audience profiles. Incentivize your best customers or lost prospects to sit with you and understand their concerns, the words they’re using relative to your products and services and how they think.

There will be certain trigger words that help your buyers make their decisions, diagnose their pain points and better understand your offerings. Wherever possible, try to determine what those trigger words are so that you can compel your prospects to take action on your mega menu.

Are your buyers looking for specific solutions to their problems? Consider adding those problems and their solutions to your mega menu. If your products have specifically branded names that a brand new prospect may not be able to recognize, place them underneath a broader category, add an icon representing it or even consider adding a small description underneath, space allowing.

\n

Your mega menu is hover dependent

\n

Hover-over menus in theory are believed by some to be faster and easier for users to navigate. However, when it comes to mega menus, it can be a little presumptuous to think you know how a user is going to move their mouse. The majority of users pause their mouse prior to making the decision to move to the content that they want. Pre-empting this with hover-over pop up navigation can be annoying to users. It gets worse when an organization assumes they can push their website prospects through hover tunnels that require a mouse to be moved slowly and carefully across other elements to reach the information that they are looking for. By not allowing a user to move their cursor the way they want without the menu closing, you’re creating frustration and extra work to get to the information they’re looking for, which is the opposite of your goal. We almost always advise our clients to go with menus that require click through, but many still opt for hover, since it’s what they’re accustomed to.

Hover-over items on the edge of a menu are more difficult to click, requiring more focus and potentially increasing frustration. While this can sometimes be remedied by adding extra space to the menu to avoid it closing if a prospect misses their mark, it usually doesn’t make the hover-over menu much more usable.

Hover-over menus also don’t take into account mobile devices, so the functionality cannot translate well for users moving between devices. Rather than using a hover-over mega menu, we recommend that clients stick to mega menus that activate upon being clicked - which is a clear user intention, saving time and keeping your website visitors happy.

\n

You haven't considered images, buttons or logos

\n

Adding compelling images, icons or call to action buttons on your mega menus are a great way to add engagement and draw your user in while giving them context. Visual elements can help users quickly analyze information and understand more about the products, services and information that you’re offering inside your menu.

\n

You didn't plan for mobile

\n

Have you taken the opportunity to look at your website traffic by device lately? Odds are very good that over the years the percentage of users viewing your website from mobile devices has increased significantly. We always develop our websites with a “mobile first” approach. That means that if a company or agency approaches us with a design in mind, one of our first questions will be - where’s the mobile design? In many instances mobile traffic is outpacing desktop traffic significantly.

If you haven’t taken the time to create a mobile design, be sure that your developer talks through how your mega menu will translate to mobile devices and that you settle on the functionality prior to beginning the project. An involved mobile mega menu may increase the cost of the project, so you need to be ready to pay a little more to convert your mega menu over to a user friendly design that works on mobile devices and achieves your original goals.

\n

You're blocking critical conversion opportunities

\n

This goes without saying, but you don’t want your mega menu to deploy on landing pages. When it comes to pages that have very specific goals, like your resource downloads, webinar sign ups or other conversion opportunities, you’ll want to eliminate the navigation entirely or shift to a new format for those pages so that expanded mega menus don’t occupy the important conversion real estate that should be a prospect’s focus when they reach your landing page.

What’s the point of an amazing landing page if it’s only going to be covered up by a massive (hopefully not hover-over) mega menu? Take the time to do a little role play scenario and test your pages accordingly, not just inside your organization, but outside as well. Make sure that your designs make sense, don’t get in the way of the main focus of your website and offer expanded opportunities for conversion rather than covering them up.

We still think that mega menus are here to stay and for savvy organizations that are deep in resources and information for their website visitors, they’re quickly becoming an essential. Ask yourself what critical information is missing from your main website navigation and how a mega menu design could give your users exactly what they need. The right mega menu can increase the time a prospect spends on your website, may reduce your bounce rate and can even increase your visitor to lead conversions.

\n

If you need help with your mega menu or you've been wanting to redesign it more intuitively to serve the needs of your website visitors, we can help. 

\n

\n

 

\n

Tell us:
Do you prefer hover-over menus or click through menus?

\n

Let us know in the comments!

","rssSummary":"

We said it. When it comes to HubSpot CMS development, we think that mega menus are an excellent way to organize your navigation and pre-qualify your prospects on your website by putting the information in front of them that is most relevant to their interests.

\n

 

\n

But not all mega menus are created equal. It’s important that you create a mega menu that’s strategic to the needs of your buyers, functional, usable and logical. While this can seem like a “no shit” statement, you’d be surprised how many times we’ve had clients approach us with a pretty design from their design team, only to find little to no research or thought was put into how the mega menu they’re requesting is structured.

Your website should be intentional. Manufacturers don’t put extra parts inside your vehicle or television that don’t function to make that machine work better and your website is no different. Every element of your website should be like a cog in a machine, working together to generate leads, further qualify existing leads or sell additional products and services to your existing customers. You should have a strategy session with your marketing agency or internal marketing department to break down buyer personas, aspects of the buyer journey, content and conversion opportunities. If you haven’t taken the time to do this, odds are good that you may be making one of these mega mistakes with your mega menus.

\n","rssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-mega%20menu%20mistakes2.png","scheduledUpdateDate":0,"screenshotPreviewTakenAt":1736726839397,"screenshotPreviewUrl":"https://cdn1.hubspot.net/hubshotv3/prod/e/0/f2a4a766-f958-46e5-852a-b95fdc0a98d6.png","sections":{},"securityState":"NONE","siteId":null,"slug":"blogs/hubspot-cms-development-tips-mega-mistakes-with-mega-menus","stagedFrom":null,"state":"PUBLISHED","stateWhenDeleted":null,"structuredContentPageType":null,"structuredContentType":null,"styleOverrideId":null,"subcategory":"normal_blog_post","syncedWithBlogRoot":true,"tagIds":[62770442823,81857606195,82133680259,94338241715],"tagList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1660323635311,"deletedAt":0,"description":"","id":81857606195,"label":"Web Design Trends","language":"en","name":"Web Design Trends","portalId":6534445,"slug":"web-design-trends","translatedFromId":null,"translations":{},"updated":1660323635311},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1660665478382,"deletedAt":0,"description":"","id":82133680259,"label":"UX Design","language":"en","name":"UX Design","portalId":6534445,"slug":"ux-design","translatedFromId":null,"translations":{},"updated":1660665478382},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1670343408539,"deletedAt":0,"description":"","id":94338241715,"label":"mega menu","language":"en","name":"mega menu","portalId":6534445,"slug":"mega-menu","translatedFromId":null,"translations":{},"updated":1670343408539}],"tagNames":["HubSpot CMS Development","Web Design Trends","UX Design","mega menu"],"teamPerms":[],"templatePath":"","templatePathForRender":"deckerdevs-theme/templates/blog-content.html","textToAudioFileId":null,"textToAudioGenerationRequestId":null,"themePath":null,"themeSettingsValues":null,"title":"HubSpot CMS Development Tips: Mega Mistakes with Mega Menus","tmsId":null,"topicIds":[62770442823,81857606195,82133680259,94338241715],"topicList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1660323635311,"deletedAt":0,"description":"","id":81857606195,"label":"Web Design Trends","language":"en","name":"Web Design Trends","portalId":6534445,"slug":"web-design-trends","translatedFromId":null,"translations":{},"updated":1660323635311},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1660665478382,"deletedAt":0,"description":"","id":82133680259,"label":"UX Design","language":"en","name":"UX Design","portalId":6534445,"slug":"ux-design","translatedFromId":null,"translations":{},"updated":1660665478382},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1670343408539,"deletedAt":0,"description":"","id":94338241715,"label":"mega menu","language":"en","name":"mega menu","portalId":6534445,"slug":"mega-menu","translatedFromId":null,"translations":{},"updated":1670343408539}],"topicNames":["HubSpot CMS Development","Web Design Trends","UX Design","mega menu"],"topics":[62770442823,81857606195,82133680259,94338241715],"translatedContent":{},"translatedFromId":null,"translations":{},"tweet":null,"tweetAt":null,"tweetImmediately":false,"unpublishedAt":0,"updated":1722384440385,"updatedById":61310730,"upsizeFeaturedImage":false,"url":"https://deckerdevs.com/blogs/hubspot-cms-development-tips-mega-mistakes-with-mega-menus","useFeaturedImage":true,"userPerms":[],"views":null,"visibleToAll":null,"widgetContainers":{},"widgetcontainers":{},"widgets":{"blog-hero":{"body":{"column_split":"split-40-60","flip_columns_on_desktop":true,"heading":"HubSpot CMS Development Tips: Mega Mistakes with Mega Menus","heading_size":"h1","heading_tag":"h1","image_holder":{"image_field":{"alt":"deckerdevs-mega menu mistakes2","height":1080,"loading":"lazy","max_height":1080,"max_width":1080,"size_type":"auto","src":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-mega%20menu%20mistakes2.png","width":1080}}},"child_css":{},"css":{},"id":"blog-hero","label":null,"module_id":82854350373,"name":"blog-hero","order":1,"smart_type":null,"styles":{},"type":"module"},"blog-image":{"body":{"image_field":{"alt":"pattern","height":563,"loading":"lazy","max_height":563,"max_width":1000,"size_type":"auto","src":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/deckerdevs%20brand%20assets/pattern.jpg","width":1000},"module_id":62246908725},"child_css":{},"css":{},"deleted_at":1692280612908,"id":"blog-image","label":null,"module_id":62246908725,"name":"blog-image","order":3,"smart_type":null,"styles":{},"type":"module"},"blog-posts":{"body":{"heading":"Some Other Recent Thoughts"},"child_css":{},"css":{},"id":"blog-posts","label":null,"module_id":82853805588,"name":"blog-posts","order":4,"smart_type":null,"styles":{},"type":"module"}}},{"ab":false,"abStatus":null,"abTestId":null,"abVariation":false,"abVariationAutomated":false,"absoluteUrl":"https://deckerdevs.com/blogs/hubspot-cms-development-trends-mega-menus-are-here-to-stay","afterPostBody":null,"aifeatures":null,"allowedSlugConflict":false,"analytics":null,"analyticsPageId":"81849403256","analyticsPageType":"blog-post","approvalStatus":null,"archived":false,"archivedAt":0,"archivedInDashboard":false,"areCommentsAllowed":true,"attachedStylesheets":[],"audienceAccess":"PUBLIC","author":null,"authorName":null,"authorUsername":null,"blogAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogAuthorId":62235724408,"blogPostAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogPostScheduleTaskUid":null,"blogPublishInstantEmailCampaignId":null,"blogPublishInstantEmailRetryCount":null,"blogPublishInstantEmailTaskUid":null,"blogPublishToSocialMediaTask":"DONE_NOT_SENT","blueprintTypeId":0,"businessUnitId":null,"campaign":null,"campaignName":null,"campaignUtm":null,"category":3,"categoryId":3,"cdnPurgeEmbargoTime":null,"checkPostLevelAudienceAccessFirst":true,"clonedFrom":null,"composeBody":null,"compositionId":0,"contentAccessRuleIds":[],"contentAccessRuleTypes":[],"contentGroup":62179259185,"contentGroupId":62179259185,"contentTypeCategory":3,"contentTypeCategoryId":3,"contentTypeId":null,"created":1660320256428,"createdByAgent":null,"createdById":27630257,"createdTime":1660320256428,"crmObjectId":null,"css":{},"cssText":"","ctaClicks":null,"ctaViews":null,"currentState":"PUBLISHED","currentlyPublished":true,"deletedAt":0,"deletedBy":null,"deletedByEmail":null,"deletedById":null,"domain":"","dynamicPageDataSourceId":null,"dynamicPageDataSourceType":null,"dynamicPageHubDbTableId":null,"enableDomainStylesheets":null,"enableGoogleAmpOutputOverride":false,"enableLayoutStylesheets":null,"errors":[],"featuredImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/Screenshots/mega-menu-staffing.jpg","featuredImageAltText":"hubspot cms development mega menu","featuredImageHeight":760,"featuredImageLength":0,"featuredImageWidth":1384,"flexAreas":{},"folderId":null,"footerHtml":null,"freezeDate":1660322381000,"generateJsonLdEnabledOverride":true,"hasContentAccessRules":false,"hasUserChanges":true,"headHtml":null,"header":null,"htmlTitle":"HubSpot CMS Development Trends: Mega Menus are Here to Stay","id":81849403256,"includeDefaultCustomCss":null,"isCaptchaRequired":true,"isCrawlableByBots":false,"isDraft":false,"isInstanceLayoutPage":false,"isInstantEmailEnabled":false,"isPublished":true,"isSocialPublishingEnabled":false,"keywords":[],"label":"HubSpot CMS Development Trends: Mega Menus are Here to Stay","language":"en","lastEditSessionId":null,"lastEditUpdateId":null,"layoutSections":{},"legacyBlogTabid":null,"legacyId":null,"legacyPostGuid":null,"linkRelCanonicalUrl":null,"listTemplate":"","liveDomain":"deckerdevs.com","mab":false,"mabExperimentId":null,"mabMaster":false,"mabVariant":false,"meta":{"html_title":"HubSpot CMS Development Trends: Mega Menus are Here to Stay","public_access_rules":[],"public_access_rules_enabled":false,"enable_google_amp_output_override":false,"generate_json_ld_enabled":true,"composition_id":0,"is_crawlable_by_bots":false,"use_featured_image":true,"post_body":"

When it comes to HubSpot CMS development trends, we’ve seen a lot of different requests over the years. Parallax scrolling animations, retro fonts, 3D visuals, augmented reality and more - web design trends the last few years have brought a lot of interesting features to websites. One feature that isn’t that new, stands out to us and seems to be a more popular request in our recent projects is a website mega menu. While mega menus have been around for many years, we’re just now seeing more adoption in businesses. For a very long time, confusing and difficult-to-navigate hover-over drop down menus dominated business websites. While it helped meet the needs for growing businesses with complex resources on their websites, it often came at the expense of user experience. The majority of the most valuable information remained inside individual web pages and there wasn’t much ability for users to parse through the information most relevant to them or gain a better understanding of what information was both relevant and available to them.

\n\n

What are mega menus?

\n

Mega menus are a more robust navigation menu that displays many different categories and options inside a 2D dropdown layout. Mega menus are the perfect way to enhance the user experience and place more central information in the hands of your users. Rather than guessing at what they’d like to see, your prospects can easily review a list of categories that apply to your goods and services. Segment your goods and services by industry or market to assist website visitors in better determining how your products apply to their business. The result? More organized navigation and resource centers that break down offerings by type or category.

Mega menus are one of the web development trends for HubSpot CMS that are here to stay. Here’s why we think that they’re a really valuable design trend that you should consider adding to your website.

\n

They're more interactive

\n

When it comes to time on page, you want to give your users options while still helping them move down the funnel in the buyer’s journey by delivering them the most relevant content. By adding a mega menu to your website, you can help your users get to the information that they need by using the categories, industries or products that you feature in your mega menu. This can help to better qualify your online prospects prior to them delving deep into your website and potentially reduces the number of steps required before they make a conversion decision.

\n

\n

Mega menus are used among a wide variety of industries, including healthcare, business services, e-commerce and more. Here’s a really great example of a mega menu that we partnered up with BS+Co to develop for Advanced Data Systems Corporation, a healthcare automation company. This mega menu is a great option that allows users to select a main navigation component where they can look at the solutions that are most relevant to them. The right section segments the users by industry so that they can learn more about how those solutions may work for their business specifically.

This allows users to easily access the solution that is most relevant to them without having to deal with the noise associated with the other elements of the navigation, which is a common complaint for mega menus that are very broad.

\n

They're super easy to navigate

\n

Many make claims that mega menus are not easy for users to navigate because of the additional display of information that isn’t relevant to that particular user. When a mega menu is poorly designed, it can be very overwhelming. However, when mega menus are broken down into categories and extraneous information is hidden from the user, it’s much more helpful.

Mega Menus are needed when there are too many sub categories in traditional drop down navigation. Mega Menus are a simpler way to manage multiple offerings and product categories. We can see this is particularly useful for business to consumer retail shops like online fashion retailers, home improvement stores and more.

Implementing mega menus helps avoid endless scrolling in their attempt to find the information they need about the topics that are most important to them. The days of scrolling to the bottom of a webpage to get to the information you need are gone, so long as you plant your mega menu properly.

\n

Users get what they need

\n

Through the use of a mega menu, users can easily navigate between products that they want or explore services that are most relevant to them based on the content categories present in the navigation. The more quickly a user can find what they’re looking for, the greater the potential for converting faster into a lead, since the content they’re viewing out of the gate is more relevant to their interests.

Regular dropdown menus can often hide many user options, which requires users to recall information rather than it remaining in front of them. Mega menus show your users everything in one place for an at-a-glance review of the information they’re seeking.

It also shows relationships between products and services and allows you to target more specifically by topic, service, product type, industry or individual need.

\n

Align your content with the buyer journey

\n

Mega menus allow you to target your content within your navigation based on the needs of your ideal buyer personas. If you are targeting specific industries or roles, have important information that’s relevant to them, want to elaborate on more specific services, or feature specific high-converting pages, this is a great opportunity to do so.

Breaking your content down by industry or most common problems based on role helps your users quickly navigate to content that they identify with. Highlighting pain points or industries can deliver relevant content more quickly than it would for a user just browsing solutions or services on your website. Think of this as a different type of content personalization.

\n

\n

Above you’ll see how a staffing agency has targeted their solutions section and highlighted those looking for executive team members. They’ve also broken down their other service offerings very clearly by needs and segments of their market.

It’s important to organize your mega menu properly if you’re exploring adding one to your website. There are many instances where agencies or businesses failed to do the appropriate amount of research on their buyers and the lack of planning created more conversion issues than it resolved.

By doing in-depth research on your buyers, their journey from awareness to consideration and then decision, and your high converting pages and popular resources, you can easily segment your content in your navigation to better serve your customers and get them to where they want to go.

Need some help implementing a mega menu on your website?



What do you think of mega menus? Share your favorites below in the comments. 

","rss_summary":"

When it comes to HubSpot CMS development trends, we’ve seen a lot of different requests over the years. Parallax scrolling animations, retro fonts, 3D visuals, augmented reality and more - web design trends the last few years have brought a lot of interesting features to websites. One feature that isn’t that new, stands out to us and seems to be a more popular request in our recent projects is a website mega menu. While mega menus have been around for many years, we’re just now seeing more adoption in businesses. For a very long time, confusing and difficult-to-navigate hover-over drop down menus dominated business websites. While it helped meet the needs for growing businesses with complex resources on their websites, it often came at the expense of user experience. The majority of the most valuable information remained inside individual web pages and there wasn’t much ability for users to parse through the information most relevant to them or gain a better understanding of what information was both relevant and available to them.

\n","rss_body":"

When it comes to HubSpot CMS development trends, we’ve seen a lot of different requests over the years. Parallax scrolling animations, retro fonts, 3D visuals, augmented reality and more - web design trends the last few years have brought a lot of interesting features to websites. One feature that isn’t that new, stands out to us and seems to be a more popular request in our recent projects is a website mega menu. While mega menus have been around for many years, we’re just now seeing more adoption in businesses. For a very long time, confusing and difficult-to-navigate hover-over drop down menus dominated business websites. While it helped meet the needs for growing businesses with complex resources on their websites, it often came at the expense of user experience. The majority of the most valuable information remained inside individual web pages and there wasn’t much ability for users to parse through the information most relevant to them or gain a better understanding of what information was both relevant and available to them.

\n\n

What are mega menus?

\n

Mega menus are a more robust navigation menu that displays many different categories and options inside a 2D dropdown layout. Mega menus are the perfect way to enhance the user experience and place more central information in the hands of your users. Rather than guessing at what they’d like to see, your prospects can easily review a list of categories that apply to your goods and services. Segment your goods and services by industry or market to assist website visitors in better determining how your products apply to their business. The result? More organized navigation and resource centers that break down offerings by type or category.

Mega menus are one of the web development trends for HubSpot CMS that are here to stay. Here’s why we think that they’re a really valuable design trend that you should consider adding to your website.

\n

They're more interactive

\n

When it comes to time on page, you want to give your users options while still helping them move down the funnel in the buyer’s journey by delivering them the most relevant content. By adding a mega menu to your website, you can help your users get to the information that they need by using the categories, industries or products that you feature in your mega menu. This can help to better qualify your online prospects prior to them delving deep into your website and potentially reduces the number of steps required before they make a conversion decision.

\n

\n

Mega menus are used among a wide variety of industries, including healthcare, business services, e-commerce and more. Here’s a really great example of a mega menu that we partnered up with BS+Co to develop for Advanced Data Systems Corporation, a healthcare automation company. This mega menu is a great option that allows users to select a main navigation component where they can look at the solutions that are most relevant to them. The right section segments the users by industry so that they can learn more about how those solutions may work for their business specifically.

This allows users to easily access the solution that is most relevant to them without having to deal with the noise associated with the other elements of the navigation, which is a common complaint for mega menus that are very broad.

\n

They're super easy to navigate

\n

Many make claims that mega menus are not easy for users to navigate because of the additional display of information that isn’t relevant to that particular user. When a mega menu is poorly designed, it can be very overwhelming. However, when mega menus are broken down into categories and extraneous information is hidden from the user, it’s much more helpful.

Mega Menus are needed when there are too many sub categories in traditional drop down navigation. Mega Menus are a simpler way to manage multiple offerings and product categories. We can see this is particularly useful for business to consumer retail shops like online fashion retailers, home improvement stores and more.

Implementing mega menus helps avoid endless scrolling in their attempt to find the information they need about the topics that are most important to them. The days of scrolling to the bottom of a webpage to get to the information you need are gone, so long as you plant your mega menu properly.

\n

Users get what they need

\n

Through the use of a mega menu, users can easily navigate between products that they want or explore services that are most relevant to them based on the content categories present in the navigation. The more quickly a user can find what they’re looking for, the greater the potential for converting faster into a lead, since the content they’re viewing out of the gate is more relevant to their interests.

Regular dropdown menus can often hide many user options, which requires users to recall information rather than it remaining in front of them. Mega menus show your users everything in one place for an at-a-glance review of the information they’re seeking.

It also shows relationships between products and services and allows you to target more specifically by topic, service, product type, industry or individual need.

\n

Align your content with the buyer journey

\n

Mega menus allow you to target your content within your navigation based on the needs of your ideal buyer personas. If you are targeting specific industries or roles, have important information that’s relevant to them, want to elaborate on more specific services, or feature specific high-converting pages, this is a great opportunity to do so.

Breaking your content down by industry or most common problems based on role helps your users quickly navigate to content that they identify with. Highlighting pain points or industries can deliver relevant content more quickly than it would for a user just browsing solutions or services on your website. Think of this as a different type of content personalization.

\n

\n

Above you’ll see how a staffing agency has targeted their solutions section and highlighted those looking for executive team members. They’ve also broken down their other service offerings very clearly by needs and segments of their market.

It’s important to organize your mega menu properly if you’re exploring adding one to your website. There are many instances where agencies or businesses failed to do the appropriate amount of research on their buyers and the lack of planning created more conversion issues than it resolved.

By doing in-depth research on your buyers, their journey from awareness to consideration and then decision, and your high converting pages and popular resources, you can easily segment your content in your navigation to better serve your customers and get them to where they want to go.

Need some help implementing a mega menu on your website?



What do you think of mega menus? Share your favorites below in the comments. 

","tag_ids":[62770442823,81857606195,94338241715],"topic_ids":[62770442823,81857606195,94338241715],"post_summary":"

When it comes to HubSpot CMS development trends, we’ve seen a lot of different requests over the years. Parallax scrolling animations, retro fonts, 3D visuals, augmented reality and more - web design trends the last few years have brought a lot of interesting features to websites. One feature that isn’t that new, stands out to us and seems to be a more popular request in our recent projects is a website mega menu. While mega menus have been around for many years, we’re just now seeing more adoption in businesses. For a very long time, confusing and difficult-to-navigate hover-over drop down menus dominated business websites. While it helped meet the needs for growing businesses with complex resources on their websites, it often came at the expense of user experience. The majority of the most valuable information remained inside individual web pages and there wasn’t much ability for users to parse through the information most relevant to them or gain a better understanding of what information was both relevant and available to them.

\n","blog_post_schedule_task_uid":null,"blog_publish_to_social_media_task":"DONE_NOT_SENT","blog_publish_instant_email_task_uid":null,"blog_publish_instant_email_campaign_id":null,"blog_publish_instant_email_retry_count":null,"keywords":[],"head_html":null,"footer_html":null,"attached_stylesheets":[],"enable_domain_stylesheets":null,"include_default_custom_css":null,"meta_description":"When it comes to HubSpot CMS development trends, mega menus are here to stay. Here's why:","meta_keywords":null,"layout_sections":{},"past_mab_experiment_ids":[],"deleted_by":null,"featured_image_alt_text":"hubspot cms development mega menu","enable_layout_stylesheets":null,"tweet":null,"tweet_at":null,"campaign_name":null,"campaign_utm":null,"tweet_immediately":false,"publish_immediately":true,"security_state":"NONE","scheduled_update_date":0,"placement_guids":[],"property_for_dynamic_page_title":null,"property_for_dynamic_page_slug":null,"property_for_dynamic_page_meta_description":null,"property_for_dynamic_page_featured_image":null,"property_for_dynamic_page_canonical_url":null,"preview_image_src":null,"legacy_blog_tabid":null,"legacy_post_guid":null,"performable_variation_letter":null,"style_override_id":null,"has_user_changes":true,"css":{},"css_text":"","unpublished_at":0,"published_by_id":8982263,"allowed_slug_conflict":false,"ai_features":null,"link_rel_canonical_url":null,"page_redirected":false,"page_expiry_enabled":null,"page_expiry_date":null,"page_expiry_redirect_id":null,"page_expiry_redirect_url":null,"deleted_by_id":null,"state_when_deleted":null,"cloned_from":null,"staged_from":null,"personas":[],"compose_body":null,"featured_image":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/Screenshots/mega-menu-staffing.jpg","featured_image_width":1384,"featured_image_height":760,"publish_timezone_offset":null,"theme_settings_values":null,"password":null,"header":null,"published_at":1718126434431,"last_edit_session_id":null,"last_edit_update_id":null,"created_by_agent":null},"metaDescription":"When it comes to HubSpot CMS development trends, mega menus are here to stay. Here's why:","metaKeywords":null,"name":"HubSpot CMS Development Trends: Mega Menus are Here to Stay","nextPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-quality%20assurance.png","nextPostFeaturedImageAltText":"","nextPostName":"Website Quality Assurance: You Need QA in HubSpot CMS Development","nextPostSlug":"blogs/website-quality-assurance-you-need-qa-in-hubspot-cms-development","pageExpiryDate":null,"pageExpiryEnabled":null,"pageExpiryRedirectId":null,"pageExpiryRedirectUrl":null,"pageRedirected":false,"pageTitle":"HubSpot CMS Development Trends: Mega Menus are Here to Stay","parentBlog":{"absoluteUrl":"https://deckerdevs.com/blogs","allowComments":true,"ampBodyColor":"#404040","ampBodyFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampBodyFontSize":"18","ampCustomCss":"","ampHeaderBackgroundColor":"#ffffff","ampHeaderColor":"#1e1e1e","ampHeaderFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampHeaderFontSize":"36","ampLinkColor":"#416bb3","ampLogoAlt":"","ampLogoHeight":0,"ampLogoSrc":"","ampLogoWidth":0,"analyticsPageId":62179259185,"attachedStylesheets":[],"audienceAccess":"PUBLIC","businessUnitId":null,"captchaAfterDays":7,"captchaAlways":false,"categoryId":3,"cdnPurgeEmbargoTime":null,"closeCommentsOlder":0,"commentDateFormat":"medium","commentFormGuid":"cb653aa1-3db4-4167-9b59-744c46d49682","commentMaxThreadDepth":3,"commentModeration":false,"commentNotificationEmails":["nicholas@deckerdevs.com","jessica@deckerdevs.com"],"commentShouldCreateContact":true,"commentVerificationText":"Thanks for participating in this conversation! We look forward to responding and to assisting where we can","cosObjectType":"BLOG","created":1639786189589,"createdDateTime":1639786189589,"dailyNotificationEmailId":null,"dateFormattingLanguage":null,"defaultGroupStyleId":"","defaultNotificationFromName":"","defaultNotificationReplyTo":"","deletedAt":0,"description":"rev up your hubspot system to the max! deckerdevs' turbo-charged blog is your ultimate guide to harnessing the full potential of hubspot development. unleash the marketing magic with ingenious tips, tricks, and hacks. get ready to level up your hubspot game!","domain":"","domainWhenPublished":"deckerdevs.com","emailApiSubscriptionId":null,"enableGoogleAmpOutput":false,"enableSocialAutoPublishing":false,"generateJsonLdEnabled":true,"header":null,"htmlFooter":"","htmlFooterIsShared":true,"htmlHead":"","htmlHeadIsShared":true,"htmlKeywords":[],"htmlTitle":"deckerdevs thought nuggets","id":62179259185,"ilsSubscriptionListsByType":{},"instantNotificationEmailId":null,"itemLayoutId":null,"itemTemplateIsShared":false,"itemTemplatePath":"deckerdevs-theme/templates/blog-content.html","label":"deckerdevs live blog","language":"en","legacyGuid":null,"legacyModuleId":null,"legacyTabId":null,"listingLayoutId":null,"listingPageId":62179259186,"listingTemplatePath":"","liveDomain":"deckerdevs.com","monthFilterFormat":"MMMM yyyy","monthlyNotificationEmailId":null,"name":"deckerdevs live blog","parentBlogUpdateTaskId":null,"portalId":6534445,"postHtmlFooter":"","postHtmlHead":"","postsPerListingPage":9,"postsPerRssFeed":10,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publicTitle":"thought nuggets","publishDateFormat":"medium","resolvedDomain":"deckerdevs.com","rootUrl":"https://deckerdevs.com/blogs","rssCustomFeed":null,"rssDescription":null,"rssItemFooter":null,"rssItemHeader":null,"settingsOverrides":{"itemLayoutId":false,"itemTemplatePath":false,"itemTemplateIsShared":false,"listingLayoutId":false,"listingTemplatePath":false,"postsPerListingPage":false,"showSummaryInListing":false,"useFeaturedImageInSummary":false,"htmlHead":false,"postHtmlHead":false,"htmlHeadIsShared":false,"htmlFooter":false,"listingPageHtmlFooter":false,"postHtmlFooter":false,"htmlFooterIsShared":false,"attachedStylesheets":false,"postsPerRssFeed":false,"showSummaryInRss":false,"showSummaryInEmails":false,"showSummariesInEmails":false,"allowComments":false,"commentShouldCreateContact":false,"commentModeration":false,"closeCommentsOlder":false,"commentNotificationEmails":false,"commentMaxThreadDepth":false,"commentVerificationText":false,"socialAccountTwitter":false,"showSocialLinkTwitter":false,"showSocialLinkLinkedin":false,"showSocialLinkFacebook":false,"enableGoogleAmpOutput":false,"ampLogoSrc":false,"ampLogoHeight":false,"ampLogoWidth":false,"ampLogoAlt":false,"ampHeaderFont":false,"ampHeaderFontSize":false,"ampHeaderColor":false,"ampHeaderBackgroundColor":false,"ampBodyFont":false,"ampBodyFontSize":false,"ampBodyColor":false,"ampLinkColor":false,"generateJsonLdEnabled":false},"showSocialLinkFacebook":true,"showSocialLinkLinkedin":true,"showSocialLinkTwitter":true,"showSummaryInEmails":true,"showSummaryInListing":true,"showSummaryInRss":true,"siteId":null,"slug":"blogs","socialAccountTwitter":"","state":null,"subscriptionContactsProperty":null,"subscriptionEmailType":null,"subscriptionFormGuid":null,"subscriptionListsByType":{},"title":null,"translatedFromId":null,"translations":{},"updated":1712344124471,"updatedDateTime":1712344124471,"urlBase":"deckerdevs.com/blogs","urlSegments":{"all":"all","archive":"archive","author":"author","page":"page","tag":"tag"},"useFeaturedImageInSummary":true,"usesDefaultTemplate":false,"weeklyNotificationEmailId":null},"password":null,"pastMabExperimentIds":[],"performableGuid":null,"performableVariationLetter":null,"personas":[],"placementGuids":[],"portableKey":null,"portalId":6534445,"position":null,"postBody":"

When it comes to HubSpot CMS development trends, we’ve seen a lot of different requests over the years. Parallax scrolling animations, retro fonts, 3D visuals, augmented reality and more - web design trends the last few years have brought a lot of interesting features to websites. One feature that isn’t that new, stands out to us and seems to be a more popular request in our recent projects is a website mega menu. While mega menus have been around for many years, we’re just now seeing more adoption in businesses. For a very long time, confusing and difficult-to-navigate hover-over drop down menus dominated business websites. While it helped meet the needs for growing businesses with complex resources on their websites, it often came at the expense of user experience. The majority of the most valuable information remained inside individual web pages and there wasn’t much ability for users to parse through the information most relevant to them or gain a better understanding of what information was both relevant and available to them.

\n\n

What are mega menus?

\n

Mega menus are a more robust navigation menu that displays many different categories and options inside a 2D dropdown layout. Mega menus are the perfect way to enhance the user experience and place more central information in the hands of your users. Rather than guessing at what they’d like to see, your prospects can easily review a list of categories that apply to your goods and services. Segment your goods and services by industry or market to assist website visitors in better determining how your products apply to their business. The result? More organized navigation and resource centers that break down offerings by type or category.

Mega menus are one of the web development trends for HubSpot CMS that are here to stay. Here’s why we think that they’re a really valuable design trend that you should consider adding to your website.

\n

They're more interactive

\n

When it comes to time on page, you want to give your users options while still helping them move down the funnel in the buyer’s journey by delivering them the most relevant content. By adding a mega menu to your website, you can help your users get to the information that they need by using the categories, industries or products that you feature in your mega menu. This can help to better qualify your online prospects prior to them delving deep into your website and potentially reduces the number of steps required before they make a conversion decision.

\n

\n

Mega menus are used among a wide variety of industries, including healthcare, business services, e-commerce and more. Here’s a really great example of a mega menu that we partnered up with BS+Co to develop for Advanced Data Systems Corporation, a healthcare automation company. This mega menu is a great option that allows users to select a main navigation component where they can look at the solutions that are most relevant to them. The right section segments the users by industry so that they can learn more about how those solutions may work for their business specifically.

This allows users to easily access the solution that is most relevant to them without having to deal with the noise associated with the other elements of the navigation, which is a common complaint for mega menus that are very broad.

\n

They're super easy to navigate

\n

Many make claims that mega menus are not easy for users to navigate because of the additional display of information that isn’t relevant to that particular user. When a mega menu is poorly designed, it can be very overwhelming. However, when mega menus are broken down into categories and extraneous information is hidden from the user, it’s much more helpful.

Mega Menus are needed when there are too many sub categories in traditional drop down navigation. Mega Menus are a simpler way to manage multiple offerings and product categories. We can see this is particularly useful for business to consumer retail shops like online fashion retailers, home improvement stores and more.

Implementing mega menus helps avoid endless scrolling in their attempt to find the information they need about the topics that are most important to them. The days of scrolling to the bottom of a webpage to get to the information you need are gone, so long as you plant your mega menu properly.

\n

Users get what they need

\n

Through the use of a mega menu, users can easily navigate between products that they want or explore services that are most relevant to them based on the content categories present in the navigation. The more quickly a user can find what they’re looking for, the greater the potential for converting faster into a lead, since the content they’re viewing out of the gate is more relevant to their interests.

Regular dropdown menus can often hide many user options, which requires users to recall information rather than it remaining in front of them. Mega menus show your users everything in one place for an at-a-glance review of the information they’re seeking.

It also shows relationships between products and services and allows you to target more specifically by topic, service, product type, industry or individual need.

\n

Align your content with the buyer journey

\n

Mega menus allow you to target your content within your navigation based on the needs of your ideal buyer personas. If you are targeting specific industries or roles, have important information that’s relevant to them, want to elaborate on more specific services, or feature specific high-converting pages, this is a great opportunity to do so.

Breaking your content down by industry or most common problems based on role helps your users quickly navigate to content that they identify with. Highlighting pain points or industries can deliver relevant content more quickly than it would for a user just browsing solutions or services on your website. Think of this as a different type of content personalization.

\n

\n

Above you’ll see how a staffing agency has targeted their solutions section and highlighted those looking for executive team members. They’ve also broken down their other service offerings very clearly by needs and segments of their market.

It’s important to organize your mega menu properly if you’re exploring adding one to your website. There are many instances where agencies or businesses failed to do the appropriate amount of research on their buyers and the lack of planning created more conversion issues than it resolved.

By doing in-depth research on your buyers, their journey from awareness to consideration and then decision, and your high converting pages and popular resources, you can easily segment your content in your navigation to better serve your customers and get them to where they want to go.

Need some help implementing a mega menu on your website?



What do you think of mega menus? Share your favorites below in the comments. 

","postBodyRss":"

When it comes to HubSpot CMS development trends, we’ve seen a lot of different requests over the years. Parallax scrolling animations, retro fonts, 3D visuals, augmented reality and more - web design trends the last few years have brought a lot of interesting features to websites. One feature that isn’t that new, stands out to us and seems to be a more popular request in our recent projects is a website mega menu. While mega menus have been around for many years, we’re just now seeing more adoption in businesses. For a very long time, confusing and difficult-to-navigate hover-over drop down menus dominated business websites. While it helped meet the needs for growing businesses with complex resources on their websites, it often came at the expense of user experience. The majority of the most valuable information remained inside individual web pages and there wasn’t much ability for users to parse through the information most relevant to them or gain a better understanding of what information was both relevant and available to them.

\n\n

What are mega menus?

\n

Mega menus are a more robust navigation menu that displays many different categories and options inside a 2D dropdown layout. Mega menus are the perfect way to enhance the user experience and place more central information in the hands of your users. Rather than guessing at what they’d like to see, your prospects can easily review a list of categories that apply to your goods and services. Segment your goods and services by industry or market to assist website visitors in better determining how your products apply to their business. The result? More organized navigation and resource centers that break down offerings by type or category.

Mega menus are one of the web development trends for HubSpot CMS that are here to stay. Here’s why we think that they’re a really valuable design trend that you should consider adding to your website.

\n

They're more interactive

\n

When it comes to time on page, you want to give your users options while still helping them move down the funnel in the buyer’s journey by delivering them the most relevant content. By adding a mega menu to your website, you can help your users get to the information that they need by using the categories, industries or products that you feature in your mega menu. This can help to better qualify your online prospects prior to them delving deep into your website and potentially reduces the number of steps required before they make a conversion decision.

\n

\n

Mega menus are used among a wide variety of industries, including healthcare, business services, e-commerce and more. Here’s a really great example of a mega menu that we partnered up with BS+Co to develop for Advanced Data Systems Corporation, a healthcare automation company. This mega menu is a great option that allows users to select a main navigation component where they can look at the solutions that are most relevant to them. The right section segments the users by industry so that they can learn more about how those solutions may work for their business specifically.

This allows users to easily access the solution that is most relevant to them without having to deal with the noise associated with the other elements of the navigation, which is a common complaint for mega menus that are very broad.

\n

They're super easy to navigate

\n

Many make claims that mega menus are not easy for users to navigate because of the additional display of information that isn’t relevant to that particular user. When a mega menu is poorly designed, it can be very overwhelming. However, when mega menus are broken down into categories and extraneous information is hidden from the user, it’s much more helpful.

Mega Menus are needed when there are too many sub categories in traditional drop down navigation. Mega Menus are a simpler way to manage multiple offerings and product categories. We can see this is particularly useful for business to consumer retail shops like online fashion retailers, home improvement stores and more.

Implementing mega menus helps avoid endless scrolling in their attempt to find the information they need about the topics that are most important to them. The days of scrolling to the bottom of a webpage to get to the information you need are gone, so long as you plant your mega menu properly.

\n

Users get what they need

\n

Through the use of a mega menu, users can easily navigate between products that they want or explore services that are most relevant to them based on the content categories present in the navigation. The more quickly a user can find what they’re looking for, the greater the potential for converting faster into a lead, since the content they’re viewing out of the gate is more relevant to their interests.

Regular dropdown menus can often hide many user options, which requires users to recall information rather than it remaining in front of them. Mega menus show your users everything in one place for an at-a-glance review of the information they’re seeking.

It also shows relationships between products and services and allows you to target more specifically by topic, service, product type, industry or individual need.

\n

Align your content with the buyer journey

\n

Mega menus allow you to target your content within your navigation based on the needs of your ideal buyer personas. If you are targeting specific industries or roles, have important information that’s relevant to them, want to elaborate on more specific services, or feature specific high-converting pages, this is a great opportunity to do so.

Breaking your content down by industry or most common problems based on role helps your users quickly navigate to content that they identify with. Highlighting pain points or industries can deliver relevant content more quickly than it would for a user just browsing solutions or services on your website. Think of this as a different type of content personalization.

\n

\n

Above you’ll see how a staffing agency has targeted their solutions section and highlighted those looking for executive team members. They’ve also broken down their other service offerings very clearly by needs and segments of their market.

It’s important to organize your mega menu properly if you’re exploring adding one to your website. There are many instances where agencies or businesses failed to do the appropriate amount of research on their buyers and the lack of planning created more conversion issues than it resolved.

By doing in-depth research on your buyers, their journey from awareness to consideration and then decision, and your high converting pages and popular resources, you can easily segment your content in your navigation to better serve your customers and get them to where they want to go.

Need some help implementing a mega menu on your website?



What do you think of mega menus? Share your favorites below in the comments. 

","postEmailContent":"

When it comes to HubSpot CMS development trends, we’ve seen a lot of different requests over the years. Parallax scrolling animations, retro fonts, 3D visuals, augmented reality and more - web design trends the last few years have brought a lot of interesting features to websites. One feature that isn’t that new, stands out to us and seems to be a more popular request in our recent projects is a website mega menu. While mega menus have been around for many years, we’re just now seeing more adoption in businesses. For a very long time, confusing and difficult-to-navigate hover-over drop down menus dominated business websites. While it helped meet the needs for growing businesses with complex resources on their websites, it often came at the expense of user experience. The majority of the most valuable information remained inside individual web pages and there wasn’t much ability for users to parse through the information most relevant to them or gain a better understanding of what information was both relevant and available to them.

","postFeaturedImageIfEnabled":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/Screenshots/mega-menu-staffing.jpg","postListContent":"

When it comes to HubSpot CMS development trends, we’ve seen a lot of different requests over the years. Parallax scrolling animations, retro fonts, 3D visuals, augmented reality and more - web design trends the last few years have brought a lot of interesting features to websites. One feature that isn’t that new, stands out to us and seems to be a more popular request in our recent projects is a website mega menu. While mega menus have been around for many years, we’re just now seeing more adoption in businesses. For a very long time, confusing and difficult-to-navigate hover-over drop down menus dominated business websites. While it helped meet the needs for growing businesses with complex resources on their websites, it often came at the expense of user experience. The majority of the most valuable information remained inside individual web pages and there wasn’t much ability for users to parse through the information most relevant to them or gain a better understanding of what information was both relevant and available to them.

","postListSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/Screenshots/mega-menu-staffing.jpg","postRssContent":"

When it comes to HubSpot CMS development trends, we’ve seen a lot of different requests over the years. Parallax scrolling animations, retro fonts, 3D visuals, augmented reality and more - web design trends the last few years have brought a lot of interesting features to websites. One feature that isn’t that new, stands out to us and seems to be a more popular request in our recent projects is a website mega menu. While mega menus have been around for many years, we’re just now seeing more adoption in businesses. For a very long time, confusing and difficult-to-navigate hover-over drop down menus dominated business websites. While it helped meet the needs for growing businesses with complex resources on their websites, it often came at the expense of user experience. The majority of the most valuable information remained inside individual web pages and there wasn’t much ability for users to parse through the information most relevant to them or gain a better understanding of what information was both relevant and available to them.

","postRssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/Screenshots/mega-menu-staffing.jpg","postSummary":"

When it comes to HubSpot CMS development trends, we’ve seen a lot of different requests over the years. Parallax scrolling animations, retro fonts, 3D visuals, augmented reality and more - web design trends the last few years have brought a lot of interesting features to websites. One feature that isn’t that new, stands out to us and seems to be a more popular request in our recent projects is a website mega menu. While mega menus have been around for many years, we’re just now seeing more adoption in businesses. For a very long time, confusing and difficult-to-navigate hover-over drop down menus dominated business websites. While it helped meet the needs for growing businesses with complex resources on their websites, it often came at the expense of user experience. The majority of the most valuable information remained inside individual web pages and there wasn’t much ability for users to parse through the information most relevant to them or gain a better understanding of what information was both relevant and available to them.

\n","postSummaryRss":"

When it comes to HubSpot CMS development trends, we’ve seen a lot of different requests over the years. Parallax scrolling animations, retro fonts, 3D visuals, augmented reality and more - web design trends the last few years have brought a lot of interesting features to websites. One feature that isn’t that new, stands out to us and seems to be a more popular request in our recent projects is a website mega menu. While mega menus have been around for many years, we’re just now seeing more adoption in businesses. For a very long time, confusing and difficult-to-navigate hover-over drop down menus dominated business websites. While it helped meet the needs for growing businesses with complex resources on their websites, it often came at the expense of user experience. The majority of the most valuable information remained inside individual web pages and there wasn’t much ability for users to parse through the information most relevant to them or gain a better understanding of what information was both relevant and available to them.

","postTemplate":"deckerdevs-theme/templates/blog-content.html","previewImageSrc":null,"previewKey":"EgMwDoAd","previousPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-mega%20menu%20mistakes2.png","previousPostFeaturedImageAltText":"","previousPostName":"HubSpot CMS Development Tips: Mega Mistakes with Mega Menus","previousPostSlug":"blogs/hubspot-cms-development-tips-mega-mistakes-with-mega-menus","processingStatus":"PUBLISHED","propertyForDynamicPageCanonicalUrl":null,"propertyForDynamicPageFeaturedImage":null,"propertyForDynamicPageMetaDescription":null,"propertyForDynamicPageSlug":null,"propertyForDynamicPageTitle":null,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publishDate":1660322381000,"publishDateLocalTime":1660322381000,"publishDateLocalized":{"date":1660322381000,"format":"medium","language":null},"publishImmediately":true,"publishTimezoneOffset":null,"publishedAt":1718126434431,"publishedByEmail":null,"publishedById":8982263,"publishedByName":null,"publishedUrl":"https://deckerdevs.com/blogs/hubspot-cms-development-trends-mega-menus-are-here-to-stay","resolvedDomain":"deckerdevs.com","resolvedLanguage":null,"rssBody":"

When it comes to HubSpot CMS development trends, we’ve seen a lot of different requests over the years. Parallax scrolling animations, retro fonts, 3D visuals, augmented reality and more - web design trends the last few years have brought a lot of interesting features to websites. One feature that isn’t that new, stands out to us and seems to be a more popular request in our recent projects is a website mega menu. While mega menus have been around for many years, we’re just now seeing more adoption in businesses. For a very long time, confusing and difficult-to-navigate hover-over drop down menus dominated business websites. While it helped meet the needs for growing businesses with complex resources on their websites, it often came at the expense of user experience. The majority of the most valuable information remained inside individual web pages and there wasn’t much ability for users to parse through the information most relevant to them or gain a better understanding of what information was both relevant and available to them.

\n\n

What are mega menus?

\n

Mega menus are a more robust navigation menu that displays many different categories and options inside a 2D dropdown layout. Mega menus are the perfect way to enhance the user experience and place more central information in the hands of your users. Rather than guessing at what they’d like to see, your prospects can easily review a list of categories that apply to your goods and services. Segment your goods and services by industry or market to assist website visitors in better determining how your products apply to their business. The result? More organized navigation and resource centers that break down offerings by type or category.

Mega menus are one of the web development trends for HubSpot CMS that are here to stay. Here’s why we think that they’re a really valuable design trend that you should consider adding to your website.

\n

They're more interactive

\n

When it comes to time on page, you want to give your users options while still helping them move down the funnel in the buyer’s journey by delivering them the most relevant content. By adding a mega menu to your website, you can help your users get to the information that they need by using the categories, industries or products that you feature in your mega menu. This can help to better qualify your online prospects prior to them delving deep into your website and potentially reduces the number of steps required before they make a conversion decision.

\n

\n

Mega menus are used among a wide variety of industries, including healthcare, business services, e-commerce and more. Here’s a really great example of a mega menu that we partnered up with BS+Co to develop for Advanced Data Systems Corporation, a healthcare automation company. This mega menu is a great option that allows users to select a main navigation component where they can look at the solutions that are most relevant to them. The right section segments the users by industry so that they can learn more about how those solutions may work for their business specifically.

This allows users to easily access the solution that is most relevant to them without having to deal with the noise associated with the other elements of the navigation, which is a common complaint for mega menus that are very broad.

\n

They're super easy to navigate

\n

Many make claims that mega menus are not easy for users to navigate because of the additional display of information that isn’t relevant to that particular user. When a mega menu is poorly designed, it can be very overwhelming. However, when mega menus are broken down into categories and extraneous information is hidden from the user, it’s much more helpful.

Mega Menus are needed when there are too many sub categories in traditional drop down navigation. Mega Menus are a simpler way to manage multiple offerings and product categories. We can see this is particularly useful for business to consumer retail shops like online fashion retailers, home improvement stores and more.

Implementing mega menus helps avoid endless scrolling in their attempt to find the information they need about the topics that are most important to them. The days of scrolling to the bottom of a webpage to get to the information you need are gone, so long as you plant your mega menu properly.

\n

Users get what they need

\n

Through the use of a mega menu, users can easily navigate between products that they want or explore services that are most relevant to them based on the content categories present in the navigation. The more quickly a user can find what they’re looking for, the greater the potential for converting faster into a lead, since the content they’re viewing out of the gate is more relevant to their interests.

Regular dropdown menus can often hide many user options, which requires users to recall information rather than it remaining in front of them. Mega menus show your users everything in one place for an at-a-glance review of the information they’re seeking.

It also shows relationships between products and services and allows you to target more specifically by topic, service, product type, industry or individual need.

\n

Align your content with the buyer journey

\n

Mega menus allow you to target your content within your navigation based on the needs of your ideal buyer personas. If you are targeting specific industries or roles, have important information that’s relevant to them, want to elaborate on more specific services, or feature specific high-converting pages, this is a great opportunity to do so.

Breaking your content down by industry or most common problems based on role helps your users quickly navigate to content that they identify with. Highlighting pain points or industries can deliver relevant content more quickly than it would for a user just browsing solutions or services on your website. Think of this as a different type of content personalization.

\n

\n

Above you’ll see how a staffing agency has targeted their solutions section and highlighted those looking for executive team members. They’ve also broken down their other service offerings very clearly by needs and segments of their market.

It’s important to organize your mega menu properly if you’re exploring adding one to your website. There are many instances where agencies or businesses failed to do the appropriate amount of research on their buyers and the lack of planning created more conversion issues than it resolved.

By doing in-depth research on your buyers, their journey from awareness to consideration and then decision, and your high converting pages and popular resources, you can easily segment your content in your navigation to better serve your customers and get them to where they want to go.

Need some help implementing a mega menu on your website?



What do you think of mega menus? Share your favorites below in the comments. 

","rssSummary":"

When it comes to HubSpot CMS development trends, we’ve seen a lot of different requests over the years. Parallax scrolling animations, retro fonts, 3D visuals, augmented reality and more - web design trends the last few years have brought a lot of interesting features to websites. One feature that isn’t that new, stands out to us and seems to be a more popular request in our recent projects is a website mega menu. While mega menus have been around for many years, we’re just now seeing more adoption in businesses. For a very long time, confusing and difficult-to-navigate hover-over drop down menus dominated business websites. While it helped meet the needs for growing businesses with complex resources on their websites, it often came at the expense of user experience. The majority of the most valuable information remained inside individual web pages and there wasn’t much ability for users to parse through the information most relevant to them or gain a better understanding of what information was both relevant and available to them.

\n","rssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/Screenshots/mega-menu-staffing.jpg","scheduledUpdateDate":0,"screenshotPreviewTakenAt":1739640033535,"screenshotPreviewUrl":"https://cdn1.hubspot.net/hubshotv3/prod/e/0/afc080f2-050c-43f8-a2ce-64484e9c264f.png","sections":{},"securityState":"NONE","siteId":null,"slug":"blogs/hubspot-cms-development-trends-mega-menus-are-here-to-stay","stagedFrom":null,"state":"PUBLISHED","stateWhenDeleted":null,"structuredContentPageType":null,"structuredContentType":null,"styleOverrideId":null,"subcategory":"normal_blog_post","syncedWithBlogRoot":true,"tagIds":[62770442823,81857606195,94338241715],"tagList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1660323635311,"deletedAt":0,"description":"","id":81857606195,"label":"Web Design Trends","language":"en","name":"Web Design Trends","portalId":6534445,"slug":"web-design-trends","translatedFromId":null,"translations":{},"updated":1660323635311},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1670343408539,"deletedAt":0,"description":"","id":94338241715,"label":"mega menu","language":"en","name":"mega menu","portalId":6534445,"slug":"mega-menu","translatedFromId":null,"translations":{},"updated":1670343408539}],"tagNames":["HubSpot CMS Development","Web Design Trends","mega menu"],"teamPerms":[],"templatePath":"","templatePathForRender":"deckerdevs-theme/templates/blog-content.html","textToAudioFileId":null,"textToAudioGenerationRequestId":null,"themePath":null,"themeSettingsValues":null,"title":"HubSpot CMS Development Trends: Mega Menus are Here to Stay","tmsId":null,"topicIds":[62770442823,81857606195,94338241715],"topicList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1660323635311,"deletedAt":0,"description":"","id":81857606195,"label":"Web Design Trends","language":"en","name":"Web Design Trends","portalId":6534445,"slug":"web-design-trends","translatedFromId":null,"translations":{},"updated":1660323635311},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1670343408539,"deletedAt":0,"description":"","id":94338241715,"label":"mega menu","language":"en","name":"mega menu","portalId":6534445,"slug":"mega-menu","translatedFromId":null,"translations":{},"updated":1670343408539}],"topicNames":["HubSpot CMS Development","Web Design Trends","mega menu"],"topics":[62770442823,81857606195,94338241715],"translatedContent":{},"translatedFromId":null,"translations":{},"tweet":null,"tweetAt":null,"tweetImmediately":false,"unpublishedAt":0,"updated":1718126434435,"updatedById":8982263,"upsizeFeaturedImage":false,"url":"https://deckerdevs.com/blogs/hubspot-cms-development-trends-mega-menus-are-here-to-stay","useFeaturedImage":true,"userPerms":[],"views":null,"visibleToAll":null,"widgetContainers":{},"widgetcontainers":{},"widgets":{"blog-image":{"body":{"image_field":{"alt":"pattern","height":563,"loading":"lazy","max_height":563,"max_width":1000,"size_type":"auto","src":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/deckerdevs%20brand%20assets/pattern.jpg","width":1000},"module_id":62246908725},"child_css":{},"css":{},"deleted_at":1692282600554,"id":"blog-image","label":null,"module_id":62246908725,"name":"blog-image","order":3,"smart_type":null,"styles":{},"type":"module"}}},{"ab":false,"abStatus":null,"abTestId":null,"abVariation":false,"abVariationAutomated":false,"absoluteUrl":"https://deckerdevs.com/blogs/website-quality-assurance-you-need-qa-in-hubspot-cms-development","afterPostBody":null,"aifeatures":null,"allowedSlugConflict":false,"analytics":null,"analyticsPageId":"81427894392","analyticsPageType":"blog-post","approvalStatus":null,"archived":false,"archivedAt":0,"archivedInDashboard":false,"areCommentsAllowed":true,"attachedStylesheets":[],"audienceAccess":"PUBLIC","author":null,"authorName":null,"authorUsername":null,"blogAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogAuthorId":62235724408,"blogPostAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogPostScheduleTaskUid":null,"blogPublishInstantEmailCampaignId":null,"blogPublishInstantEmailRetryCount":null,"blogPublishInstantEmailTaskUid":null,"blogPublishToSocialMediaTask":"DONE_NOT_SENT","blueprintTypeId":0,"businessUnitId":null,"campaign":null,"campaignName":null,"campaignUtm":null,"category":3,"categoryId":3,"cdnPurgeEmbargoTime":null,"checkPostLevelAudienceAccessFirst":true,"clonedFrom":null,"composeBody":null,"compositionId":0,"contentAccessRuleIds":[],"contentAccessRuleTypes":[],"contentGroup":62179259185,"contentGroupId":62179259185,"contentTypeCategory":3,"contentTypeCategoryId":3,"contentTypeId":null,"created":1659976384089,"createdByAgent":null,"createdById":27630257,"createdTime":1659976384089,"crmObjectId":null,"css":{},"cssText":"","ctaClicks":null,"ctaViews":null,"currentState":"PUBLISHED","currentlyPublished":true,"deletedAt":0,"deletedBy":null,"deletedByEmail":null,"deletedById":null,"domain":"","dynamicPageDataSourceId":null,"dynamicPageDataSourceType":null,"dynamicPageHubDbTableId":null,"enableDomainStylesheets":null,"enableGoogleAmpOutputOverride":false,"enableLayoutStylesheets":null,"errors":[],"featuredImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-quality%20assurance.png","featuredImageAltText":"","featuredImageHeight":1080,"featuredImageLength":0,"featuredImageWidth":1080,"flexAreas":{},"folderId":null,"footerHtml":null,"freezeDate":1659976947000,"generateJsonLdEnabledOverride":true,"hasContentAccessRules":false,"hasUserChanges":true,"headHtml":null,"header":null,"htmlTitle":"Website Quality Assurance: You Need QA in HubSpot CMS Development","id":81427894392,"includeDefaultCustomCss":null,"isCaptchaRequired":true,"isCrawlableByBots":false,"isDraft":false,"isInstanceLayoutPage":false,"isInstantEmailEnabled":false,"isPublished":true,"isSocialPublishingEnabled":false,"keywords":[],"label":"Website Quality Assurance: You Need QA in HubSpot CMS Development","language":"en","lastEditSessionId":null,"lastEditUpdateId":null,"layoutSections":{},"legacyBlogTabid":null,"legacyId":null,"legacyPostGuid":null,"linkRelCanonicalUrl":"","listTemplate":"","liveDomain":"deckerdevs.com","mab":false,"mabExperimentId":null,"mabMaster":false,"mabVariant":false,"meta":{"html_title":"Website Quality Assurance: You Need QA in HubSpot CMS Development","public_access_rules":[],"public_access_rules_enabled":false,"enable_google_amp_output_override":false,"generate_json_ld_enabled":true,"composition_id":0,"is_crawlable_by_bots":false,"use_featured_image":true,"post_body":"

We hear it all the time from our agency clients, “We said we weren’t going to do website projects any more, and then we took this one on - and it’s been a nightmare!”

\n

 

\n

Most people don’t realize that we are a specialized HubSpot Partner that focuses almost exclusively on HubSpot CMS Development. The majority of our client list are HubSpot Partners. We are often referred work by some of the top development agencies and have a lot of experience in implementing website designs in HubSpot CMS and taking them live.

We were surprised to find in a recent prospect call that not all specialized HubSpot development agencies have a comprehensive internal quality assurance process. Website quality assurance is an internal review of an unpublished website for bugs, formatting issues, browser compatibility, and more. The internal review allows for a certain amount of quality control prior to reaching the client. Issues that we’ve discovered in quality assurance testing can be minor things like responsiveness bugs, incorrect fonts, forms not redirecting properly, or small design issues that are inconsistent with the provided design. Completing QA prior to client review is really important, as it not only solidifies your credibility, but builds client confidence as you move along in the development process.

Here are just a few reasons that you want to make sure to include comprehensive website quality assurance testing in your next HubSpot CMS development project:

\n\n

The client should focus on what’s important

\n

If the client has provided an expected, finalized and approved design, they’ll be looking to test and approve a draft that looks very similar if not identical to that design. They will not want to handle major bugs, formatting issues, questions of inconsistencies in browser compatibility and other aesthetic issues.

If you’re working with a one-man development team, it’s very difficult for them to objectively look at work and see it from any other angle. It’s likely that if this is the case, you’re gonna need external departments or others (hopefully not the client) to look it over objectively. Allowing a single developer to complete a project and turn it directly over to the client is basically asking your client to complete quality assurance for you. A very good developer may be able to catch an issue or two, but you’ll always want to have a separate, skilled person that understands how to properly test a website for bugs, browser compatibility issues and other problems.

Once your development team finishes a round of edits or the initial design template, you’ll want to have your internal team take a close look at what they’ve built. Working within the template build to find usability issues, bugs and any other glitches is important. Your project management staff or quality assurance staff (if you’re lucky enough to have them) can review all of these items before the design is handed off to the client.

You should have a comprehensive list of QA items for them to review and some sort of tool that allows for collaboration and feedback. Our team uses Pastel. Pastel is a great tool because it allows for internal and external collaboration, hidden comments, status updates and more. You can do QA on PDF, JPEG and live website pages. The team at Pastel is very passionate about making improvements and they particularly enjoy working with agencies. (No, we aren’t paid to say that, we just think they’re really awesome.) You can snag a free trial to test it out.

\n

It'll shorten the development process

\n

Who doesn’t love scope creep?
Just kidding. Everyone hates scope creep.

\n

It can be an inevitable and sometimes unavoidable evil in the industry of marketing services delivery and website development, but implementing a really good quality assurance process can go a long way to avoiding scope creep. When you deliver a draft website to a client or when you receive a draft website as a client, you’ll want to make sure it’s as close to the design as possible. We’ve heard the statement before, “The CEO just can’t get past the formatting issue to proof the copy” or “These images aren’t what we want” - it is sometimes difficult when a website is still in draft mode to envision that end product when all that the client wants to see is the perfect iteration of the original design document.

Delivering a draft that is as close to complete as possible will allow the client to to focus on the elements they need to focus on - like core functionality, adding or delivering the correct images and copy and providing the important feedback and envisioning how the design is working well for both internal marketers and the prospects and leads that will find themselves on the website. The more they can focus on these items, the more “wish list” items they may compile, which provides strong support for them leveraging growth driven design (more on that later).

\n

 

\n

 

\n

It puts more eyes on the work

\n

Developers have very different brains.

Believe us when we say that it requires a special kind of nerd to have a passion to create something by staring at tiny lines of code all day. We’re very good at what we do, but we don’t necessarily have marketer brains. Placing a project manager, quality assurance specialist or marketer in the middle of a project before it is sent over for review is critical. They’ll ask important questions, play with modules until they can break them, and identify issues that the development team may not see.

By having a centralized spreadsheet or piece of software that manages these edits, you can eliminate a large portion of feedback and make things easier for both the developer and the client. The more people that see the initial draft prior to it being delivered to the client, the more issues can be weeded out in advance.

\n

It keeps edits in a central location and makes teams more productive

\n

Using a software or spreadsheet to manage the quality assurance process keeps everything centralized and helps avoid the issue of project managers or developers wasting time threading through a 75 e-mail string to find the feedback they need. This also allows multiple people to submit feedback without it becoming overwhelming. We do request in most cases that there be a single “final answer, Regis” contact to provide the edits so we can make sure we have the right information to execute edits and complete changes.

\n

It reduces post-launch feedback

\n

Once a website is completed, we’re ready to jump into the next project. We often encounter “wish list” items that pop up during development that we categorize as pre-launch or post-launch. Post-launch work allows us to develop the bells and whistles for a client that they find are “nice to have” items after the initial website build has been completed.

If we’re stuck in an endless round of edits because of lacking quality assurance testing, it can not only take a lot longer to get to those wish list items, but frustration can build if client expectations are not managed properly and a developer might risk losing a relationship with the client.

We’d much rather move our clients into growth-driven design to accommodate all their projects after launch or a short term development retainer to get some of those wish list items completed.

Website projects can be cumbersome for a small business. Often they’re only looking at their website every 3-5 years for a redesign. While we as HubSpot development partners are working slowly to show businesses that a long term relationship with a development partner that makes small changes over time (check out why continuous improvement is the best model for your website) is ideal, it will take time for the world to catch up. In the meantime, a comprehensive quality assurance process will help avoid development headaches for everyone involved.

Work on implementing a comprehensive quality assurance process with your development team to ensure that projects launch on time and everyone is as happy with the process as they are with the final project.

\n

\n

 

","rss_summary":"

We hear it all the time from our agency clients, “We said we weren’t going to do website projects any more, and then we took this one on - and it’s been a nightmare!”

\n

 

\n

Most people don’t realize that we are a specialized HubSpot Partner that focuses almost exclusively on HubSpot CMS Development. The majority of our client list are HubSpot Partners. We are often referred work by some of the top development agencies and have a lot of experience in implementing website designs in HubSpot CMS and taking them live.

We were surprised to find in a recent prospect call that not all specialized HubSpot development agencies have a comprehensive internal quality assurance process. Website quality assurance is an internal review of an unpublished website for bugs, formatting issues, browser compatibility, and more. The internal review allows for a certain amount of quality control prior to reaching the client. Issues that we’ve discovered in quality assurance testing can be minor things like responsiveness bugs, incorrect fonts, forms not redirecting properly, or small design issues that are inconsistent with the provided design. Completing QA prior to client review is really important, as it not only solidifies your credibility, but builds client confidence as you move along in the development process.

Here are just a few reasons that you want to make sure to include comprehensive website quality assurance testing in your next HubSpot CMS development project:

\n","rss_body":"

We hear it all the time from our agency clients, “We said we weren’t going to do website projects any more, and then we took this one on - and it’s been a nightmare!”

\n

 

\n

Most people don’t realize that we are a specialized HubSpot Partner that focuses almost exclusively on HubSpot CMS Development. The majority of our client list are HubSpot Partners. We are often referred work by some of the top development agencies and have a lot of experience in implementing website designs in HubSpot CMS and taking them live.

We were surprised to find in a recent prospect call that not all specialized HubSpot development agencies have a comprehensive internal quality assurance process. Website quality assurance is an internal review of an unpublished website for bugs, formatting issues, browser compatibility, and more. The internal review allows for a certain amount of quality control prior to reaching the client. Issues that we’ve discovered in quality assurance testing can be minor things like responsiveness bugs, incorrect fonts, forms not redirecting properly, or small design issues that are inconsistent with the provided design. Completing QA prior to client review is really important, as it not only solidifies your credibility, but builds client confidence as you move along in the development process.

Here are just a few reasons that you want to make sure to include comprehensive website quality assurance testing in your next HubSpot CMS development project:

\n\n

The client should focus on what’s important

\n

If the client has provided an expected, finalized and approved design, they’ll be looking to test and approve a draft that looks very similar if not identical to that design. They will not want to handle major bugs, formatting issues, questions of inconsistencies in browser compatibility and other aesthetic issues.

If you’re working with a one-man development team, it’s very difficult for them to objectively look at work and see it from any other angle. It’s likely that if this is the case, you’re gonna need external departments or others (hopefully not the client) to look it over objectively. Allowing a single developer to complete a project and turn it directly over to the client is basically asking your client to complete quality assurance for you. A very good developer may be able to catch an issue or two, but you’ll always want to have a separate, skilled person that understands how to properly test a website for bugs, browser compatibility issues and other problems.

Once your development team finishes a round of edits or the initial design template, you’ll want to have your internal team take a close look at what they’ve built. Working within the template build to find usability issues, bugs and any other glitches is important. Your project management staff or quality assurance staff (if you’re lucky enough to have them) can review all of these items before the design is handed off to the client.

You should have a comprehensive list of QA items for them to review and some sort of tool that allows for collaboration and feedback. Our team uses Pastel. Pastel is a great tool because it allows for internal and external collaboration, hidden comments, status updates and more. You can do QA on PDF, JPEG and live website pages. The team at Pastel is very passionate about making improvements and they particularly enjoy working with agencies. (No, we aren’t paid to say that, we just think they’re really awesome.) You can snag a free trial to test it out.

\n

It'll shorten the development process

\n

Who doesn’t love scope creep?
Just kidding. Everyone hates scope creep.

\n

It can be an inevitable and sometimes unavoidable evil in the industry of marketing services delivery and website development, but implementing a really good quality assurance process can go a long way to avoiding scope creep. When you deliver a draft website to a client or when you receive a draft website as a client, you’ll want to make sure it’s as close to the design as possible. We’ve heard the statement before, “The CEO just can’t get past the formatting issue to proof the copy” or “These images aren’t what we want” - it is sometimes difficult when a website is still in draft mode to envision that end product when all that the client wants to see is the perfect iteration of the original design document.

Delivering a draft that is as close to complete as possible will allow the client to to focus on the elements they need to focus on - like core functionality, adding or delivering the correct images and copy and providing the important feedback and envisioning how the design is working well for both internal marketers and the prospects and leads that will find themselves on the website. The more they can focus on these items, the more “wish list” items they may compile, which provides strong support for them leveraging growth driven design (more on that later).

\n

 

\n

 

\n

It puts more eyes on the work

\n

Developers have very different brains.

Believe us when we say that it requires a special kind of nerd to have a passion to create something by staring at tiny lines of code all day. We’re very good at what we do, but we don’t necessarily have marketer brains. Placing a project manager, quality assurance specialist or marketer in the middle of a project before it is sent over for review is critical. They’ll ask important questions, play with modules until they can break them, and identify issues that the development team may not see.

By having a centralized spreadsheet or piece of software that manages these edits, you can eliminate a large portion of feedback and make things easier for both the developer and the client. The more people that see the initial draft prior to it being delivered to the client, the more issues can be weeded out in advance.

\n

It keeps edits in a central location and makes teams more productive

\n

Using a software or spreadsheet to manage the quality assurance process keeps everything centralized and helps avoid the issue of project managers or developers wasting time threading through a 75 e-mail string to find the feedback they need. This also allows multiple people to submit feedback without it becoming overwhelming. We do request in most cases that there be a single “final answer, Regis” contact to provide the edits so we can make sure we have the right information to execute edits and complete changes.

\n

It reduces post-launch feedback

\n

Once a website is completed, we’re ready to jump into the next project. We often encounter “wish list” items that pop up during development that we categorize as pre-launch or post-launch. Post-launch work allows us to develop the bells and whistles for a client that they find are “nice to have” items after the initial website build has been completed.

If we’re stuck in an endless round of edits because of lacking quality assurance testing, it can not only take a lot longer to get to those wish list items, but frustration can build if client expectations are not managed properly and a developer might risk losing a relationship with the client.

We’d much rather move our clients into growth-driven design to accommodate all their projects after launch or a short term development retainer to get some of those wish list items completed.

Website projects can be cumbersome for a small business. Often they’re only looking at their website every 3-5 years for a redesign. While we as HubSpot development partners are working slowly to show businesses that a long term relationship with a development partner that makes small changes over time (check out why continuous improvement is the best model for your website) is ideal, it will take time for the world to catch up. In the meantime, a comprehensive quality assurance process will help avoid development headaches for everyone involved.

Work on implementing a comprehensive quality assurance process with your development team to ensure that projects launch on time and everyone is as happy with the process as they are with the final project.

\n

\n

 

","tag_ids":[62770442823,78562833827,81427988387],"topic_ids":[62770442823,78562833827,81427988387],"post_summary":"

We hear it all the time from our agency clients, “We said we weren’t going to do website projects any more, and then we took this one on - and it’s been a nightmare!”

\n

 

\n

Most people don’t realize that we are a specialized HubSpot Partner that focuses almost exclusively on HubSpot CMS Development. The majority of our client list are HubSpot Partners. We are often referred work by some of the top development agencies and have a lot of experience in implementing website designs in HubSpot CMS and taking them live.

We were surprised to find in a recent prospect call that not all specialized HubSpot development agencies have a comprehensive internal quality assurance process. Website quality assurance is an internal review of an unpublished website for bugs, formatting issues, browser compatibility, and more. The internal review allows for a certain amount of quality control prior to reaching the client. Issues that we’ve discovered in quality assurance testing can be minor things like responsiveness bugs, incorrect fonts, forms not redirecting properly, or small design issues that are inconsistent with the provided design. Completing QA prior to client review is really important, as it not only solidifies your credibility, but builds client confidence as you move along in the development process.

Here are just a few reasons that you want to make sure to include comprehensive website quality assurance testing in your next HubSpot CMS development project:

\n","blog_post_schedule_task_uid":null,"blog_publish_to_social_media_task":"DONE_NOT_SENT","blog_publish_instant_email_task_uid":null,"blog_publish_instant_email_campaign_id":null,"blog_publish_instant_email_retry_count":null,"keywords":[],"head_html":null,"footer_html":null,"attached_stylesheets":[],"enable_domain_stylesheets":null,"include_default_custom_css":null,"meta_description":"Website quality assurance matters! Here's why you can't afford NOT to have a QA process in HubSpot CMS Development projects. ","meta_keywords":null,"layout_sections":{},"past_mab_experiment_ids":[],"deleted_by":null,"featured_image_alt_text":"","enable_layout_stylesheets":null,"tweet":null,"tweet_at":null,"campaign_name":null,"campaign_utm":null,"tweet_immediately":false,"publish_immediately":true,"security_state":"NONE","scheduled_update_date":0,"placement_guids":[],"property_for_dynamic_page_title":null,"property_for_dynamic_page_slug":null,"property_for_dynamic_page_meta_description":null,"property_for_dynamic_page_featured_image":null,"property_for_dynamic_page_canonical_url":null,"preview_image_src":null,"legacy_blog_tabid":null,"legacy_post_guid":null,"performable_variation_letter":null,"style_override_id":null,"has_user_changes":true,"css":{},"css_text":"","unpublished_at":0,"published_by_id":61310730,"allowed_slug_conflict":false,"ai_features":null,"link_rel_canonical_url":"","page_redirected":false,"page_expiry_enabled":null,"page_expiry_date":null,"page_expiry_redirect_id":null,"page_expiry_redirect_url":null,"deleted_by_id":null,"state_when_deleted":null,"cloned_from":null,"staged_from":null,"personas":[],"compose_body":null,"featured_image":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-quality%20assurance.png","featured_image_width":1080,"featured_image_height":1080,"publish_timezone_offset":null,"theme_settings_values":null,"password":null,"header":null,"published_at":1722393644639,"last_edit_session_id":null,"last_edit_update_id":null,"created_by_agent":null},"metaDescription":"Website quality assurance matters! Here's why you can't afford NOT to have a QA process in HubSpot CMS Development projects. ","metaKeywords":null,"name":"Website Quality Assurance: You Need QA in HubSpot CMS Development","nextPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-wordpress%20to%20hubspot.png","nextPostFeaturedImageAltText":"","nextPostName":"It's Time to Leave WordPress for HubSpot CMS","nextPostSlug":"blogs/its-time-to-leave-wordpress-for-hubspot-cms","pageExpiryDate":null,"pageExpiryEnabled":null,"pageExpiryRedirectId":null,"pageExpiryRedirectUrl":null,"pageRedirected":false,"pageTitle":"Website Quality Assurance: You Need QA in HubSpot CMS Development","parentBlog":{"absoluteUrl":"https://deckerdevs.com/blogs","allowComments":true,"ampBodyColor":"#404040","ampBodyFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampBodyFontSize":"18","ampCustomCss":"","ampHeaderBackgroundColor":"#ffffff","ampHeaderColor":"#1e1e1e","ampHeaderFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampHeaderFontSize":"36","ampLinkColor":"#416bb3","ampLogoAlt":"","ampLogoHeight":0,"ampLogoSrc":"","ampLogoWidth":0,"analyticsPageId":62179259185,"attachedStylesheets":[],"audienceAccess":"PUBLIC","businessUnitId":null,"captchaAfterDays":7,"captchaAlways":false,"categoryId":3,"cdnPurgeEmbargoTime":null,"closeCommentsOlder":0,"commentDateFormat":"medium","commentFormGuid":"cb653aa1-3db4-4167-9b59-744c46d49682","commentMaxThreadDepth":3,"commentModeration":false,"commentNotificationEmails":["nicholas@deckerdevs.com","jessica@deckerdevs.com"],"commentShouldCreateContact":true,"commentVerificationText":"Thanks for participating in this conversation! We look forward to responding and to assisting where we can","cosObjectType":"BLOG","created":1639786189589,"createdDateTime":1639786189589,"dailyNotificationEmailId":null,"dateFormattingLanguage":null,"defaultGroupStyleId":"","defaultNotificationFromName":"","defaultNotificationReplyTo":"","deletedAt":0,"description":"rev up your hubspot system to the max! deckerdevs' turbo-charged blog is your ultimate guide to harnessing the full potential of hubspot development. unleash the marketing magic with ingenious tips, tricks, and hacks. get ready to level up your hubspot game!","domain":"","domainWhenPublished":"deckerdevs.com","emailApiSubscriptionId":null,"enableGoogleAmpOutput":false,"enableSocialAutoPublishing":false,"generateJsonLdEnabled":true,"header":null,"htmlFooter":"","htmlFooterIsShared":true,"htmlHead":"","htmlHeadIsShared":true,"htmlKeywords":[],"htmlTitle":"deckerdevs thought nuggets","id":62179259185,"ilsSubscriptionListsByType":{},"instantNotificationEmailId":null,"itemLayoutId":null,"itemTemplateIsShared":false,"itemTemplatePath":"deckerdevs-theme/templates/blog-content.html","label":"deckerdevs live blog","language":"en","legacyGuid":null,"legacyModuleId":null,"legacyTabId":null,"listingLayoutId":null,"listingPageId":62179259186,"listingTemplatePath":"","liveDomain":"deckerdevs.com","monthFilterFormat":"MMMM yyyy","monthlyNotificationEmailId":null,"name":"deckerdevs live blog","parentBlogUpdateTaskId":null,"portalId":6534445,"postHtmlFooter":"","postHtmlHead":"","postsPerListingPage":9,"postsPerRssFeed":10,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publicTitle":"thought nuggets","publishDateFormat":"medium","resolvedDomain":"deckerdevs.com","rootUrl":"https://deckerdevs.com/blogs","rssCustomFeed":null,"rssDescription":null,"rssItemFooter":null,"rssItemHeader":null,"settingsOverrides":{"itemLayoutId":false,"itemTemplatePath":false,"itemTemplateIsShared":false,"listingLayoutId":false,"listingTemplatePath":false,"postsPerListingPage":false,"showSummaryInListing":false,"useFeaturedImageInSummary":false,"htmlHead":false,"postHtmlHead":false,"htmlHeadIsShared":false,"htmlFooter":false,"listingPageHtmlFooter":false,"postHtmlFooter":false,"htmlFooterIsShared":false,"attachedStylesheets":false,"postsPerRssFeed":false,"showSummaryInRss":false,"showSummaryInEmails":false,"showSummariesInEmails":false,"allowComments":false,"commentShouldCreateContact":false,"commentModeration":false,"closeCommentsOlder":false,"commentNotificationEmails":false,"commentMaxThreadDepth":false,"commentVerificationText":false,"socialAccountTwitter":false,"showSocialLinkTwitter":false,"showSocialLinkLinkedin":false,"showSocialLinkFacebook":false,"enableGoogleAmpOutput":false,"ampLogoSrc":false,"ampLogoHeight":false,"ampLogoWidth":false,"ampLogoAlt":false,"ampHeaderFont":false,"ampHeaderFontSize":false,"ampHeaderColor":false,"ampHeaderBackgroundColor":false,"ampBodyFont":false,"ampBodyFontSize":false,"ampBodyColor":false,"ampLinkColor":false,"generateJsonLdEnabled":false},"showSocialLinkFacebook":true,"showSocialLinkLinkedin":true,"showSocialLinkTwitter":true,"showSummaryInEmails":true,"showSummaryInListing":true,"showSummaryInRss":true,"siteId":null,"slug":"blogs","socialAccountTwitter":"","state":null,"subscriptionContactsProperty":null,"subscriptionEmailType":null,"subscriptionFormGuid":null,"subscriptionListsByType":{},"title":null,"translatedFromId":null,"translations":{},"updated":1712344124471,"updatedDateTime":1712344124471,"urlBase":"deckerdevs.com/blogs","urlSegments":{"all":"all","archive":"archive","author":"author","page":"page","tag":"tag"},"useFeaturedImageInSummary":true,"usesDefaultTemplate":false,"weeklyNotificationEmailId":null},"password":null,"pastMabExperimentIds":[],"performableGuid":null,"performableVariationLetter":null,"personas":[],"placementGuids":[],"portableKey":null,"portalId":6534445,"position":null,"postBody":"

We hear it all the time from our agency clients, “We said we weren’t going to do website projects any more, and then we took this one on - and it’s been a nightmare!”

\n

 

\n

Most people don’t realize that we are a specialized HubSpot Partner that focuses almost exclusively on HubSpot CMS Development. The majority of our client list are HubSpot Partners. We are often referred work by some of the top development agencies and have a lot of experience in implementing website designs in HubSpot CMS and taking them live.

We were surprised to find in a recent prospect call that not all specialized HubSpot development agencies have a comprehensive internal quality assurance process. Website quality assurance is an internal review of an unpublished website for bugs, formatting issues, browser compatibility, and more. The internal review allows for a certain amount of quality control prior to reaching the client. Issues that we’ve discovered in quality assurance testing can be minor things like responsiveness bugs, incorrect fonts, forms not redirecting properly, or small design issues that are inconsistent with the provided design. Completing QA prior to client review is really important, as it not only solidifies your credibility, but builds client confidence as you move along in the development process.

Here are just a few reasons that you want to make sure to include comprehensive website quality assurance testing in your next HubSpot CMS development project:

\n\n

The client should focus on what’s important

\n

If the client has provided an expected, finalized and approved design, they’ll be looking to test and approve a draft that looks very similar if not identical to that design. They will not want to handle major bugs, formatting issues, questions of inconsistencies in browser compatibility and other aesthetic issues.

If you’re working with a one-man development team, it’s very difficult for them to objectively look at work and see it from any other angle. It’s likely that if this is the case, you’re gonna need external departments or others (hopefully not the client) to look it over objectively. Allowing a single developer to complete a project and turn it directly over to the client is basically asking your client to complete quality assurance for you. A very good developer may be able to catch an issue or two, but you’ll always want to have a separate, skilled person that understands how to properly test a website for bugs, browser compatibility issues and other problems.

Once your development team finishes a round of edits or the initial design template, you’ll want to have your internal team take a close look at what they’ve built. Working within the template build to find usability issues, bugs and any other glitches is important. Your project management staff or quality assurance staff (if you’re lucky enough to have them) can review all of these items before the design is handed off to the client.

You should have a comprehensive list of QA items for them to review and some sort of tool that allows for collaboration and feedback. Our team uses Pastel. Pastel is a great tool because it allows for internal and external collaboration, hidden comments, status updates and more. You can do QA on PDF, JPEG and live website pages. The team at Pastel is very passionate about making improvements and they particularly enjoy working with agencies. (No, we aren’t paid to say that, we just think they’re really awesome.) You can snag a free trial to test it out.

\n

It'll shorten the development process

\n

Who doesn’t love scope creep?
Just kidding. Everyone hates scope creep.

\n

It can be an inevitable and sometimes unavoidable evil in the industry of marketing services delivery and website development, but implementing a really good quality assurance process can go a long way to avoiding scope creep. When you deliver a draft website to a client or when you receive a draft website as a client, you’ll want to make sure it’s as close to the design as possible. We’ve heard the statement before, “The CEO just can’t get past the formatting issue to proof the copy” or “These images aren’t what we want” - it is sometimes difficult when a website is still in draft mode to envision that end product when all that the client wants to see is the perfect iteration of the original design document.

Delivering a draft that is as close to complete as possible will allow the client to to focus on the elements they need to focus on - like core functionality, adding or delivering the correct images and copy and providing the important feedback and envisioning how the design is working well for both internal marketers and the prospects and leads that will find themselves on the website. The more they can focus on these items, the more “wish list” items they may compile, which provides strong support for them leveraging growth driven design (more on that later).

\n

 

\n

 

\n

It puts more eyes on the work

\n

Developers have very different brains.

Believe us when we say that it requires a special kind of nerd to have a passion to create something by staring at tiny lines of code all day. We’re very good at what we do, but we don’t necessarily have marketer brains. Placing a project manager, quality assurance specialist or marketer in the middle of a project before it is sent over for review is critical. They’ll ask important questions, play with modules until they can break them, and identify issues that the development team may not see.

By having a centralized spreadsheet or piece of software that manages these edits, you can eliminate a large portion of feedback and make things easier for both the developer and the client. The more people that see the initial draft prior to it being delivered to the client, the more issues can be weeded out in advance.

\n

It keeps edits in a central location and makes teams more productive

\n

Using a software or spreadsheet to manage the quality assurance process keeps everything centralized and helps avoid the issue of project managers or developers wasting time threading through a 75 e-mail string to find the feedback they need. This also allows multiple people to submit feedback without it becoming overwhelming. We do request in most cases that there be a single “final answer, Regis” contact to provide the edits so we can make sure we have the right information to execute edits and complete changes.

\n

It reduces post-launch feedback

\n

Once a website is completed, we’re ready to jump into the next project. We often encounter “wish list” items that pop up during development that we categorize as pre-launch or post-launch. Post-launch work allows us to develop the bells and whistles for a client that they find are “nice to have” items after the initial website build has been completed.

If we’re stuck in an endless round of edits because of lacking quality assurance testing, it can not only take a lot longer to get to those wish list items, but frustration can build if client expectations are not managed properly and a developer might risk losing a relationship with the client.

We’d much rather move our clients into growth-driven design to accommodate all their projects after launch or a short term development retainer to get some of those wish list items completed.

Website projects can be cumbersome for a small business. Often they’re only looking at their website every 3-5 years for a redesign. While we as HubSpot development partners are working slowly to show businesses that a long term relationship with a development partner that makes small changes over time (check out why continuous improvement is the best model for your website) is ideal, it will take time for the world to catch up. In the meantime, a comprehensive quality assurance process will help avoid development headaches for everyone involved.

Work on implementing a comprehensive quality assurance process with your development team to ensure that projects launch on time and everyone is as happy with the process as they are with the final project.

\n

\n

 

","postBodyRss":"

We hear it all the time from our agency clients, “We said we weren’t going to do website projects any more, and then we took this one on - and it’s been a nightmare!”

\n

 

\n

Most people don’t realize that we are a specialized HubSpot Partner that focuses almost exclusively on HubSpot CMS Development. The majority of our client list are HubSpot Partners. We are often referred work by some of the top development agencies and have a lot of experience in implementing website designs in HubSpot CMS and taking them live.

We were surprised to find in a recent prospect call that not all specialized HubSpot development agencies have a comprehensive internal quality assurance process. Website quality assurance is an internal review of an unpublished website for bugs, formatting issues, browser compatibility, and more. The internal review allows for a certain amount of quality control prior to reaching the client. Issues that we’ve discovered in quality assurance testing can be minor things like responsiveness bugs, incorrect fonts, forms not redirecting properly, or small design issues that are inconsistent with the provided design. Completing QA prior to client review is really important, as it not only solidifies your credibility, but builds client confidence as you move along in the development process.

Here are just a few reasons that you want to make sure to include comprehensive website quality assurance testing in your next HubSpot CMS development project:

\n\n

The client should focus on what’s important

\n

If the client has provided an expected, finalized and approved design, they’ll be looking to test and approve a draft that looks very similar if not identical to that design. They will not want to handle major bugs, formatting issues, questions of inconsistencies in browser compatibility and other aesthetic issues.

If you’re working with a one-man development team, it’s very difficult for them to objectively look at work and see it from any other angle. It’s likely that if this is the case, you’re gonna need external departments or others (hopefully not the client) to look it over objectively. Allowing a single developer to complete a project and turn it directly over to the client is basically asking your client to complete quality assurance for you. A very good developer may be able to catch an issue or two, but you’ll always want to have a separate, skilled person that understands how to properly test a website for bugs, browser compatibility issues and other problems.

Once your development team finishes a round of edits or the initial design template, you’ll want to have your internal team take a close look at what they’ve built. Working within the template build to find usability issues, bugs and any other glitches is important. Your project management staff or quality assurance staff (if you’re lucky enough to have them) can review all of these items before the design is handed off to the client.

You should have a comprehensive list of QA items for them to review and some sort of tool that allows for collaboration and feedback. Our team uses Pastel. Pastel is a great tool because it allows for internal and external collaboration, hidden comments, status updates and more. You can do QA on PDF, JPEG and live website pages. The team at Pastel is very passionate about making improvements and they particularly enjoy working with agencies. (No, we aren’t paid to say that, we just think they’re really awesome.) You can snag a free trial to test it out.

\n

It'll shorten the development process

\n

Who doesn’t love scope creep?
Just kidding. Everyone hates scope creep.

\n

It can be an inevitable and sometimes unavoidable evil in the industry of marketing services delivery and website development, but implementing a really good quality assurance process can go a long way to avoiding scope creep. When you deliver a draft website to a client or when you receive a draft website as a client, you’ll want to make sure it’s as close to the design as possible. We’ve heard the statement before, “The CEO just can’t get past the formatting issue to proof the copy” or “These images aren’t what we want” - it is sometimes difficult when a website is still in draft mode to envision that end product when all that the client wants to see is the perfect iteration of the original design document.

Delivering a draft that is as close to complete as possible will allow the client to to focus on the elements they need to focus on - like core functionality, adding or delivering the correct images and copy and providing the important feedback and envisioning how the design is working well for both internal marketers and the prospects and leads that will find themselves on the website. The more they can focus on these items, the more “wish list” items they may compile, which provides strong support for them leveraging growth driven design (more on that later).

\n

 

\n

 

\n

It puts more eyes on the work

\n

Developers have very different brains.

Believe us when we say that it requires a special kind of nerd to have a passion to create something by staring at tiny lines of code all day. We’re very good at what we do, but we don’t necessarily have marketer brains. Placing a project manager, quality assurance specialist or marketer in the middle of a project before it is sent over for review is critical. They’ll ask important questions, play with modules until they can break them, and identify issues that the development team may not see.

By having a centralized spreadsheet or piece of software that manages these edits, you can eliminate a large portion of feedback and make things easier for both the developer and the client. The more people that see the initial draft prior to it being delivered to the client, the more issues can be weeded out in advance.

\n

It keeps edits in a central location and makes teams more productive

\n

Using a software or spreadsheet to manage the quality assurance process keeps everything centralized and helps avoid the issue of project managers or developers wasting time threading through a 75 e-mail string to find the feedback they need. This also allows multiple people to submit feedback without it becoming overwhelming. We do request in most cases that there be a single “final answer, Regis” contact to provide the edits so we can make sure we have the right information to execute edits and complete changes.

\n

It reduces post-launch feedback

\n

Once a website is completed, we’re ready to jump into the next project. We often encounter “wish list” items that pop up during development that we categorize as pre-launch or post-launch. Post-launch work allows us to develop the bells and whistles for a client that they find are “nice to have” items after the initial website build has been completed.

If we’re stuck in an endless round of edits because of lacking quality assurance testing, it can not only take a lot longer to get to those wish list items, but frustration can build if client expectations are not managed properly and a developer might risk losing a relationship with the client.

We’d much rather move our clients into growth-driven design to accommodate all their projects after launch or a short term development retainer to get some of those wish list items completed.

Website projects can be cumbersome for a small business. Often they’re only looking at their website every 3-5 years for a redesign. While we as HubSpot development partners are working slowly to show businesses that a long term relationship with a development partner that makes small changes over time (check out why continuous improvement is the best model for your website) is ideal, it will take time for the world to catch up. In the meantime, a comprehensive quality assurance process will help avoid development headaches for everyone involved.

Work on implementing a comprehensive quality assurance process with your development team to ensure that projects launch on time and everyone is as happy with the process as they are with the final project.

\n

\n

 

","postEmailContent":"

We hear it all the time from our agency clients, “We said we weren’t going to do website projects any more, and then we took this one on - and it’s been a nightmare!”

\n

 

\n

Most people don’t realize that we are a specialized HubSpot Partner that focuses almost exclusively on HubSpot CMS Development. The majority of our client list are HubSpot Partners. We are often referred work by some of the top development agencies and have a lot of experience in implementing website designs in HubSpot CMS and taking them live.

We were surprised to find in a recent prospect call that not all specialized HubSpot development agencies have a comprehensive internal quality assurance process. Website quality assurance is an internal review of an unpublished website for bugs, formatting issues, browser compatibility, and more. The internal review allows for a certain amount of quality control prior to reaching the client. Issues that we’ve discovered in quality assurance testing can be minor things like responsiveness bugs, incorrect fonts, forms not redirecting properly, or small design issues that are inconsistent with the provided design. Completing QA prior to client review is really important, as it not only solidifies your credibility, but builds client confidence as you move along in the development process.

Here are just a few reasons that you want to make sure to include comprehensive website quality assurance testing in your next HubSpot CMS development project:

","postFeaturedImageIfEnabled":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-quality%20assurance.png","postListContent":"

We hear it all the time from our agency clients, “We said we weren’t going to do website projects any more, and then we took this one on - and it’s been a nightmare!”

\n

 

\n

Most people don’t realize that we are a specialized HubSpot Partner that focuses almost exclusively on HubSpot CMS Development. The majority of our client list are HubSpot Partners. We are often referred work by some of the top development agencies and have a lot of experience in implementing website designs in HubSpot CMS and taking them live.

We were surprised to find in a recent prospect call that not all specialized HubSpot development agencies have a comprehensive internal quality assurance process. Website quality assurance is an internal review of an unpublished website for bugs, formatting issues, browser compatibility, and more. The internal review allows for a certain amount of quality control prior to reaching the client. Issues that we’ve discovered in quality assurance testing can be minor things like responsiveness bugs, incorrect fonts, forms not redirecting properly, or small design issues that are inconsistent with the provided design. Completing QA prior to client review is really important, as it not only solidifies your credibility, but builds client confidence as you move along in the development process.

Here are just a few reasons that you want to make sure to include comprehensive website quality assurance testing in your next HubSpot CMS development project:

","postListSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-quality%20assurance.png","postRssContent":"

We hear it all the time from our agency clients, “We said we weren’t going to do website projects any more, and then we took this one on - and it’s been a nightmare!”

\n

 

\n

Most people don’t realize that we are a specialized HubSpot Partner that focuses almost exclusively on HubSpot CMS Development. The majority of our client list are HubSpot Partners. We are often referred work by some of the top development agencies and have a lot of experience in implementing website designs in HubSpot CMS and taking them live.

We were surprised to find in a recent prospect call that not all specialized HubSpot development agencies have a comprehensive internal quality assurance process. Website quality assurance is an internal review of an unpublished website for bugs, formatting issues, browser compatibility, and more. The internal review allows for a certain amount of quality control prior to reaching the client. Issues that we’ve discovered in quality assurance testing can be minor things like responsiveness bugs, incorrect fonts, forms not redirecting properly, or small design issues that are inconsistent with the provided design. Completing QA prior to client review is really important, as it not only solidifies your credibility, but builds client confidence as you move along in the development process.

Here are just a few reasons that you want to make sure to include comprehensive website quality assurance testing in your next HubSpot CMS development project:

","postRssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-quality%20assurance.png","postSummary":"

We hear it all the time from our agency clients, “We said we weren’t going to do website projects any more, and then we took this one on - and it’s been a nightmare!”

\n

 

\n

Most people don’t realize that we are a specialized HubSpot Partner that focuses almost exclusively on HubSpot CMS Development. The majority of our client list are HubSpot Partners. We are often referred work by some of the top development agencies and have a lot of experience in implementing website designs in HubSpot CMS and taking them live.

We were surprised to find in a recent prospect call that not all specialized HubSpot development agencies have a comprehensive internal quality assurance process. Website quality assurance is an internal review of an unpublished website for bugs, formatting issues, browser compatibility, and more. The internal review allows for a certain amount of quality control prior to reaching the client. Issues that we’ve discovered in quality assurance testing can be minor things like responsiveness bugs, incorrect fonts, forms not redirecting properly, or small design issues that are inconsistent with the provided design. Completing QA prior to client review is really important, as it not only solidifies your credibility, but builds client confidence as you move along in the development process.

Here are just a few reasons that you want to make sure to include comprehensive website quality assurance testing in your next HubSpot CMS development project:

\n","postSummaryRss":"

We hear it all the time from our agency clients, “We said we weren’t going to do website projects any more, and then we took this one on - and it’s been a nightmare!”

\n

 

\n

Most people don’t realize that we are a specialized HubSpot Partner that focuses almost exclusively on HubSpot CMS Development. The majority of our client list are HubSpot Partners. We are often referred work by some of the top development agencies and have a lot of experience in implementing website designs in HubSpot CMS and taking them live.

We were surprised to find in a recent prospect call that not all specialized HubSpot development agencies have a comprehensive internal quality assurance process. Website quality assurance is an internal review of an unpublished website for bugs, formatting issues, browser compatibility, and more. The internal review allows for a certain amount of quality control prior to reaching the client. Issues that we’ve discovered in quality assurance testing can be minor things like responsiveness bugs, incorrect fonts, forms not redirecting properly, or small design issues that are inconsistent with the provided design. Completing QA prior to client review is really important, as it not only solidifies your credibility, but builds client confidence as you move along in the development process.

Here are just a few reasons that you want to make sure to include comprehensive website quality assurance testing in your next HubSpot CMS development project:

","postTemplate":"deckerdevs-theme/templates/blog-content.html","previewImageSrc":null,"previewKey":"GCQZlWAY","previousPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/Screenshots/mega-menu-staffing.jpg","previousPostFeaturedImageAltText":"hubspot cms development mega menu","previousPostName":"HubSpot CMS Development Trends: Mega Menus are Here to Stay","previousPostSlug":"blogs/hubspot-cms-development-trends-mega-menus-are-here-to-stay","processingStatus":"PUBLISHED","propertyForDynamicPageCanonicalUrl":null,"propertyForDynamicPageFeaturedImage":null,"propertyForDynamicPageMetaDescription":null,"propertyForDynamicPageSlug":null,"propertyForDynamicPageTitle":null,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publishDate":1659976947000,"publishDateLocalTime":1659976947000,"publishDateLocalized":{"date":1659976947000,"format":"medium","language":null},"publishImmediately":true,"publishTimezoneOffset":null,"publishedAt":1722393644639,"publishedByEmail":null,"publishedById":61310730,"publishedByName":null,"publishedUrl":"https://deckerdevs.com/blogs/website-quality-assurance-you-need-qa-in-hubspot-cms-development","resolvedDomain":"deckerdevs.com","resolvedLanguage":null,"rssBody":"

We hear it all the time from our agency clients, “We said we weren’t going to do website projects any more, and then we took this one on - and it’s been a nightmare!”

\n

 

\n

Most people don’t realize that we are a specialized HubSpot Partner that focuses almost exclusively on HubSpot CMS Development. The majority of our client list are HubSpot Partners. We are often referred work by some of the top development agencies and have a lot of experience in implementing website designs in HubSpot CMS and taking them live.

We were surprised to find in a recent prospect call that not all specialized HubSpot development agencies have a comprehensive internal quality assurance process. Website quality assurance is an internal review of an unpublished website for bugs, formatting issues, browser compatibility, and more. The internal review allows for a certain amount of quality control prior to reaching the client. Issues that we’ve discovered in quality assurance testing can be minor things like responsiveness bugs, incorrect fonts, forms not redirecting properly, or small design issues that are inconsistent with the provided design. Completing QA prior to client review is really important, as it not only solidifies your credibility, but builds client confidence as you move along in the development process.

Here are just a few reasons that you want to make sure to include comprehensive website quality assurance testing in your next HubSpot CMS development project:

\n\n

The client should focus on what’s important

\n

If the client has provided an expected, finalized and approved design, they’ll be looking to test and approve a draft that looks very similar if not identical to that design. They will not want to handle major bugs, formatting issues, questions of inconsistencies in browser compatibility and other aesthetic issues.

If you’re working with a one-man development team, it’s very difficult for them to objectively look at work and see it from any other angle. It’s likely that if this is the case, you’re gonna need external departments or others (hopefully not the client) to look it over objectively. Allowing a single developer to complete a project and turn it directly over to the client is basically asking your client to complete quality assurance for you. A very good developer may be able to catch an issue or two, but you’ll always want to have a separate, skilled person that understands how to properly test a website for bugs, browser compatibility issues and other problems.

Once your development team finishes a round of edits or the initial design template, you’ll want to have your internal team take a close look at what they’ve built. Working within the template build to find usability issues, bugs and any other glitches is important. Your project management staff or quality assurance staff (if you’re lucky enough to have them) can review all of these items before the design is handed off to the client.

You should have a comprehensive list of QA items for them to review and some sort of tool that allows for collaboration and feedback. Our team uses Pastel. Pastel is a great tool because it allows for internal and external collaboration, hidden comments, status updates and more. You can do QA on PDF, JPEG and live website pages. The team at Pastel is very passionate about making improvements and they particularly enjoy working with agencies. (No, we aren’t paid to say that, we just think they’re really awesome.) You can snag a free trial to test it out.

\n

It'll shorten the development process

\n

Who doesn’t love scope creep?
Just kidding. Everyone hates scope creep.

\n

It can be an inevitable and sometimes unavoidable evil in the industry of marketing services delivery and website development, but implementing a really good quality assurance process can go a long way to avoiding scope creep. When you deliver a draft website to a client or when you receive a draft website as a client, you’ll want to make sure it’s as close to the design as possible. We’ve heard the statement before, “The CEO just can’t get past the formatting issue to proof the copy” or “These images aren’t what we want” - it is sometimes difficult when a website is still in draft mode to envision that end product when all that the client wants to see is the perfect iteration of the original design document.

Delivering a draft that is as close to complete as possible will allow the client to to focus on the elements they need to focus on - like core functionality, adding or delivering the correct images and copy and providing the important feedback and envisioning how the design is working well for both internal marketers and the prospects and leads that will find themselves on the website. The more they can focus on these items, the more “wish list” items they may compile, which provides strong support for them leveraging growth driven design (more on that later).

\n

 

\n

 

\n

It puts more eyes on the work

\n

Developers have very different brains.

Believe us when we say that it requires a special kind of nerd to have a passion to create something by staring at tiny lines of code all day. We’re very good at what we do, but we don’t necessarily have marketer brains. Placing a project manager, quality assurance specialist or marketer in the middle of a project before it is sent over for review is critical. They’ll ask important questions, play with modules until they can break them, and identify issues that the development team may not see.

By having a centralized spreadsheet or piece of software that manages these edits, you can eliminate a large portion of feedback and make things easier for both the developer and the client. The more people that see the initial draft prior to it being delivered to the client, the more issues can be weeded out in advance.

\n

It keeps edits in a central location and makes teams more productive

\n

Using a software or spreadsheet to manage the quality assurance process keeps everything centralized and helps avoid the issue of project managers or developers wasting time threading through a 75 e-mail string to find the feedback they need. This also allows multiple people to submit feedback without it becoming overwhelming. We do request in most cases that there be a single “final answer, Regis” contact to provide the edits so we can make sure we have the right information to execute edits and complete changes.

\n

It reduces post-launch feedback

\n

Once a website is completed, we’re ready to jump into the next project. We often encounter “wish list” items that pop up during development that we categorize as pre-launch or post-launch. Post-launch work allows us to develop the bells and whistles for a client that they find are “nice to have” items after the initial website build has been completed.

If we’re stuck in an endless round of edits because of lacking quality assurance testing, it can not only take a lot longer to get to those wish list items, but frustration can build if client expectations are not managed properly and a developer might risk losing a relationship with the client.

We’d much rather move our clients into growth-driven design to accommodate all their projects after launch or a short term development retainer to get some of those wish list items completed.

Website projects can be cumbersome for a small business. Often they’re only looking at their website every 3-5 years for a redesign. While we as HubSpot development partners are working slowly to show businesses that a long term relationship with a development partner that makes small changes over time (check out why continuous improvement is the best model for your website) is ideal, it will take time for the world to catch up. In the meantime, a comprehensive quality assurance process will help avoid development headaches for everyone involved.

Work on implementing a comprehensive quality assurance process with your development team to ensure that projects launch on time and everyone is as happy with the process as they are with the final project.

\n

\n

 

","rssSummary":"

We hear it all the time from our agency clients, “We said we weren’t going to do website projects any more, and then we took this one on - and it’s been a nightmare!”

\n

 

\n

Most people don’t realize that we are a specialized HubSpot Partner that focuses almost exclusively on HubSpot CMS Development. The majority of our client list are HubSpot Partners. We are often referred work by some of the top development agencies and have a lot of experience in implementing website designs in HubSpot CMS and taking them live.

We were surprised to find in a recent prospect call that not all specialized HubSpot development agencies have a comprehensive internal quality assurance process. Website quality assurance is an internal review of an unpublished website for bugs, formatting issues, browser compatibility, and more. The internal review allows for a certain amount of quality control prior to reaching the client. Issues that we’ve discovered in quality assurance testing can be minor things like responsiveness bugs, incorrect fonts, forms not redirecting properly, or small design issues that are inconsistent with the provided design. Completing QA prior to client review is really important, as it not only solidifies your credibility, but builds client confidence as you move along in the development process.

Here are just a few reasons that you want to make sure to include comprehensive website quality assurance testing in your next HubSpot CMS development project:

\n","rssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-quality%20assurance.png","scheduledUpdateDate":0,"screenshotPreviewTakenAt":1736736044331,"screenshotPreviewUrl":"https://cdn1.hubspot.net/hubshotv3/prod/e/0/60274a59-846f-4273-9200-8eaffea25cef.png","sections":{},"securityState":"NONE","siteId":null,"slug":"blogs/website-quality-assurance-you-need-qa-in-hubspot-cms-development","stagedFrom":null,"state":"PUBLISHED","stateWhenDeleted":null,"structuredContentPageType":null,"structuredContentType":null,"styleOverrideId":null,"subcategory":"normal_blog_post","syncedWithBlogRoot":true,"tagIds":[62770442823,78562833827,81427988387],"tagList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1657204695862,"deletedAt":0,"description":"","id":78562833827,"label":"HubSpot Partner","language":"en","name":"HubSpot Partner","portalId":6534445,"slug":"hubspot-partner","translatedFromId":null,"translations":{},"updated":1657204695862},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1659976870464,"deletedAt":0,"description":"","id":81427988387,"label":"Quality Assurance","language":"en","name":"Quality Assurance","portalId":6534445,"slug":"quality-assurance","translatedFromId":null,"translations":{},"updated":1659976870464}],"tagNames":["HubSpot CMS Development","HubSpot Partner","Quality Assurance"],"teamPerms":[],"templatePath":"","templatePathForRender":"deckerdevs-theme/templates/blog-content.html","textToAudioFileId":null,"textToAudioGenerationRequestId":null,"themePath":null,"themeSettingsValues":null,"title":"Website Quality Assurance: You Need QA in HubSpot CMS Development","tmsId":null,"topicIds":[62770442823,78562833827,81427988387],"topicList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1657204695862,"deletedAt":0,"description":"","id":78562833827,"label":"HubSpot Partner","language":"en","name":"HubSpot Partner","portalId":6534445,"slug":"hubspot-partner","translatedFromId":null,"translations":{},"updated":1657204695862},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1659976870464,"deletedAt":0,"description":"","id":81427988387,"label":"Quality Assurance","language":"en","name":"Quality Assurance","portalId":6534445,"slug":"quality-assurance","translatedFromId":null,"translations":{},"updated":1659976870464}],"topicNames":["HubSpot CMS Development","HubSpot Partner","Quality Assurance"],"topics":[62770442823,78562833827,81427988387],"translatedContent":{},"translatedFromId":null,"translations":{},"tweet":null,"tweetAt":null,"tweetImmediately":false,"unpublishedAt":0,"updated":1722393644644,"updatedById":61310730,"upsizeFeaturedImage":false,"url":"https://deckerdevs.com/blogs/website-quality-assurance-you-need-qa-in-hubspot-cms-development","useFeaturedImage":true,"userPerms":[],"views":null,"visibleToAll":null,"widgetContainers":{},"widgetcontainers":{},"widgets":{"blog-hero":{"body":{"column_split":"split-40-60","flip_columns_on_desktop":true,"heading":"Website Quality Assurance: You Need QA in HubSpot CMS Development","heading_size":"h1","heading_tag":"h1","image_holder":{"image_field":{"alt":"deckerdevs-quality assurance","height":1080,"loading":"lazy","max_height":1080,"max_width":1080,"size_type":"auto","src":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-quality%20assurance.png","width":1080}}},"child_css":{},"css":{},"id":"blog-hero","label":null,"module_id":82854350373,"name":"blog-hero","order":1,"smart_type":null,"styles":{},"type":"module"},"blog-image":{"body":{"image_field":{"alt":"pattern","height":563,"loading":"lazy","max_height":563,"max_width":1000,"size_type":"auto","src":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/deckerdevs%20brand%20assets/pattern.jpg","width":1000}},"child_css":{},"css":{},"deleted_at":1692621815110,"id":"blog-image","label":null,"module_id":62246908725,"name":"blog-image","order":3,"smart_type":null,"styles":{},"type":"module"},"blog-posts":{"body":{"heading":"Some Other Recent Thoughts"},"child_css":{},"css":{},"id":"blog-posts","label":null,"module_id":82853805588,"name":"blog-posts","order":4,"smart_type":null,"styles":{},"type":"module"}}},{"ab":false,"abStatus":null,"abTestId":null,"abVariation":false,"abVariationAutomated":false,"absoluteUrl":"https://deckerdevs.com/blogs/its-time-to-leave-wordpress-for-hubspot-cms","afterPostBody":null,"aifeatures":null,"allowedSlugConflict":false,"analytics":null,"analyticsPageId":"81427893582","analyticsPageType":"blog-post","approvalStatus":null,"archived":false,"archivedAt":0,"archivedInDashboard":false,"areCommentsAllowed":true,"attachedStylesheets":[],"audienceAccess":"PUBLIC","author":null,"authorName":null,"authorUsername":null,"blogAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogAuthorId":62235724408,"blogPostAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogPostScheduleTaskUid":null,"blogPublishInstantEmailCampaignId":null,"blogPublishInstantEmailRetryCount":null,"blogPublishInstantEmailTaskUid":null,"blogPublishToSocialMediaTask":"DONE_NOT_SENT","blueprintTypeId":0,"businessUnitId":null,"campaign":null,"campaignName":null,"campaignUtm":null,"category":3,"categoryId":3,"cdnPurgeEmbargoTime":null,"checkPostLevelAudienceAccessFirst":true,"clonedFrom":null,"composeBody":null,"compositionId":0,"contentAccessRuleIds":[],"contentAccessRuleTypes":[],"contentGroup":62179259185,"contentGroupId":62179259185,"contentTypeCategory":3,"contentTypeCategoryId":3,"contentTypeId":null,"created":1659975528316,"createdByAgent":null,"createdById":27630257,"createdTime":1659975528316,"crmObjectId":null,"css":{},"cssText":"","ctaClicks":null,"ctaViews":null,"currentState":"PUBLISHED","currentlyPublished":true,"deletedAt":0,"deletedBy":null,"deletedByEmail":null,"deletedById":null,"domain":"","dynamicPageDataSourceId":null,"dynamicPageDataSourceType":null,"dynamicPageHubDbTableId":null,"enableDomainStylesheets":null,"enableGoogleAmpOutputOverride":false,"enableLayoutStylesheets":null,"errors":[],"featuredImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-wordpress%20to%20hubspot.png","featuredImageAltText":"","featuredImageHeight":1080,"featuredImageLength":0,"featuredImageWidth":1080,"flexAreas":{},"folderId":null,"footerHtml":null,"freezeDate":1659890640000,"generateJsonLdEnabledOverride":true,"hasContentAccessRules":false,"hasUserChanges":true,"headHtml":null,"header":null,"htmlTitle":"It's Time to Leave WordPress for HubSpot CMS","id":81427893582,"includeDefaultCustomCss":null,"isCaptchaRequired":true,"isCrawlableByBots":false,"isDraft":false,"isInstanceLayoutPage":false,"isInstantEmailEnabled":false,"isPublished":true,"isSocialPublishingEnabled":false,"keywords":[],"label":"It's Time to Leave WordPress for HubSpot CMS","language":"en","lastEditSessionId":null,"lastEditUpdateId":null,"layoutSections":{},"legacyBlogTabid":null,"legacyId":null,"legacyPostGuid":null,"linkRelCanonicalUrl":"","listTemplate":"","liveDomain":"deckerdevs.com","mab":false,"mabExperimentId":null,"mabMaster":false,"mabVariant":false,"meta":{"html_title":"It's Time to Leave WordPress for HubSpot CMS","public_access_rules":[],"public_access_rules_enabled":false,"enable_google_amp_output_override":false,"generate_json_ld_enabled":true,"composition_id":0,"is_crawlable_by_bots":false,"use_featured_image":true,"post_body":"

Is it finally time to leave WordPress for HubSpot CMS? For a long time, WordPress was the most flexible game in town when it came to content management systems (CMS). With so much functionality in plugins and a huge number of developers working within it, it has been the industry standard for years for those looking to develop complex websites with flexible functionality. It’s open-source, so anyone can create plugins, fixes, themes, or modules. There are dozens of free themes that can have you up and running in no time..

But for a growing business that will be focusing heavily on marketing and building a website robust in resources that grows with them? We’re no longer selling WordPress as a solution for our clients.

Here’s why we think it’s finally time to leave WordPress for HubSpot CMS.

\n\n

You get what you pay for

\n

One of the best things about WordPress is that it’s free. You pay for your themes and plugins and the developers who created them usually provide support, or you can hire a web developer if you need either more support or ongoing development expertise. However, that can come at a cost. Security issues, plugins not functioning as you’d hoped, and your website loading more slowly because of so many plugins are just a few common issues with WordPress.

Keep in mind that if you want a robust solution, you’re going to have to fork out a little cash. Committing an investment to HubSpot CMS might mean paying a monthly or annual fee, but it’ll give you a lot more capabilities out of the box without the additional frustration.

HubSpot support is super helpful and not outsourced, so you’re speaking to humans who really understand the platform. Not to mention, there’s an entire fully vetted and trained developer ecosystem with vendors who are crazy experienced and not even a little bit sketchy.

\n

You’re using a ton of different tools to execute on your digital marketing

\n

Versatility used to be what WordPress was known for, but as the number of plugins and developers creating them increases, growing businesses need a less complicated solution. WordPress, as a free CMS with some paid plugins and themes, is a great foundation for a new small business, but once a business starts to move in the direction of lead generation, its needs become more complex.

Now that HubSpot has launched a free version of their CMS, B2B demand generation for startups has become simpler, which is definitely a consideration for those who might’ve gone straight to WordPress in the past. HubSpot CMS Hub Free is HubSpot’s introductory CMS package. It includes premium hosting on HubSpot, the option to build a from-scratch website (with forms, live chat, landing pages, and a blog), and its free CRM platform. This is a perfect option for small businesses that cannot afford HubSpot quite yet, but want to dig into its tools and build a website that creates awareness and builds their brand. It does have a few limitations, however:

\n

\n
• Limited to 25 website pages
\n
• Limited to one blog with 100 posts
\n
• No ability to modify system pages
\n
• HubSpot branding on website pages, blog posts and landing pages
\n

\n

While it might not be for everyone, it gives startups a powerful, free, and simple way to get their brand off the ground. A perfect example is this super basic website we stood up in only three hours using HubSpot CMS Free.

Many growing businesses operating with a WordPress website end up paying a premium for a form manager, SEO plugin, analytics tool, CRM, email marketing platform, and automation solution. All of these different tools not only don’t speak to one another (unless you pay for another integration tool to centralize them), but your marketing team has to login to every single platform to manage information and execute your marketing. It’s cumbersome and inefficient.

With HubSpot, you’re managing everything in one portal. From CMS tools to social media marketing, ad management, CRM for sales and email marketing, automation, blogging, SEO, and analytics — it doesn’t get more centralized than that. While all the tools in HubSpot can be costly when purchased together, HubSpot allows you to close the loop with your content marketing and sales processes, attributing revenue to your campaigns and gaining a full view on what efforts are working, so you can execute more of them. With WordPress, you have to be incredibly organized to use all the different tools. You’ll also probably need to create your own spreadsheets to allow you to really understand where your revenue is coming from.

Keeping your tech stack small helps fuel your marketing team to make educated decisions and work more efficiently.

\n

You've coded yourself into a corner

\n

Probably the biggest pitfall that comes with working in WordPress is a bloated website. While we’ve outlined a a few different factors that can contribute to website bloat and how you can optimize your page speed, you cannot unwind the drag that comes with adding poorly coded plugins to your website.

The more plugins you add to your site, the more code a browser has to load, which can bog down your load speed. While you can limit your plugins and have a developer recommend the best ones, eventually you may want to add advanced functionality such as calculators or a robust resource center to your content arsenal.

HubSpot allows you to add functionality to your website with modules that can be coded by a HubSpot developer who knows best practices. Using one development partner who is certified keeps your website code clean and can ensure that your website doesn’t just pile on code from multiple different developers with plugins that break or leave security holes.

\n

It's more secure

\n

WordPress sites are notorious for experiencing malware attacks. While keeping your plugins and WordPress up to date helps, malware attacks can still occur. Security is an extremely important aspect of your website, and HubSpot has the edge over WordPress here.

Because WordPress is open source, hackers can find security holes and exploit the platform easily. In addition, many of the available plugins aren’t supported and updated by the developers who created them. This makes WordPress sites easy targets.

WordPress theme and plugin developers typically bundle quite a few different plugins together to bring a full suite for you to take advantage of, but this can also create dependencies that aren’t updated correctly. Even if the theme is up to date, sometimes those smaller packages underneath aren’t updated and can create additional security vulnerabilities on your site.

HubSpot, however, has SSL encryption, which not only boosts your rankings with Google, but assures the users whose information you’re collecting that their information is safe. In HubSPot, you automatically receive a standard SAN SSL certification through DigiCert when you connect a domain to your account. If you purchase the custom SSL add-on, you can upload custom SSL certifications to HubSpot and configure security settings. Learn more about your SSL options in HubSpot here.

If you’re cost conscious and don’t plan to do much with your website, WordPress may have been a no-brainer for you. It’s free and has infinite customization options. Just be sure if you opt in to WordPress, you update plugins and WordPress regularly, manage comments, and have your site checked for security issues regularly.

If you’re cost conscious and looking for a starter platform that will grow with you as your marketing budget grows and lead generation is important to you, look to HubSpot. While we’re not currently offering development help on CMS Hub Free, we can definitely give you what you need once you’re ready to upgrade your HubSpot CMS Hub and build something that will suit you as you grow. HubSpot’s CRM is unmatched when it comes to sales, and we think that from a sustainability standpoint there’s no better platform for a growing business that is investing heavily into its sales and marketing strategies.

For a scaling business that uses its website as a lead generation tool, you’ll eventually need a better way to make website improvements, ensure the security of your site, and prevent website bloat. We’ve been huge supporters of HubSpot since they were just a tiny piece of analytics code. They continue to prove that they’re not only surpassing best practices, but setting new benchmarks for what to expect from a CMS and comprehensive marketing automation software.

If you’re considering a switch to HubSpot CMS Professional, we’d love to give you a rundown of the power of HubSpot.

\n

","rss_summary":"

Is it finally time to leave WordPress for HubSpot CMS? For a long time, WordPress was the most flexible game in town when it came to content management systems (CMS). With so much functionality in plugins and a huge number of developers working within it, it has been the industry standard for years for those looking to develop complex websites with flexible functionality. It’s open-source, so anyone can create plugins, fixes, themes, or modules. There are dozens of free themes that can have you up and running in no time..

But for a growing business that will be focusing heavily on marketing and building a website robust in resources that grows with them? We’re no longer selling WordPress as a solution for our clients.

Here’s why we think it’s finally time to leave WordPress for HubSpot CMS.

\n","rss_body":"

Is it finally time to leave WordPress for HubSpot CMS? For a long time, WordPress was the most flexible game in town when it came to content management systems (CMS). With so much functionality in plugins and a huge number of developers working within it, it has been the industry standard for years for those looking to develop complex websites with flexible functionality. It’s open-source, so anyone can create plugins, fixes, themes, or modules. There are dozens of free themes that can have you up and running in no time..

But for a growing business that will be focusing heavily on marketing and building a website robust in resources that grows with them? We’re no longer selling WordPress as a solution for our clients.

Here’s why we think it’s finally time to leave WordPress for HubSpot CMS.

\n\n

You get what you pay for

\n

One of the best things about WordPress is that it’s free. You pay for your themes and plugins and the developers who created them usually provide support, or you can hire a web developer if you need either more support or ongoing development expertise. However, that can come at a cost. Security issues, plugins not functioning as you’d hoped, and your website loading more slowly because of so many plugins are just a few common issues with WordPress.

Keep in mind that if you want a robust solution, you’re going to have to fork out a little cash. Committing an investment to HubSpot CMS might mean paying a monthly or annual fee, but it’ll give you a lot more capabilities out of the box without the additional frustration.

HubSpot support is super helpful and not outsourced, so you’re speaking to humans who really understand the platform. Not to mention, there’s an entire fully vetted and trained developer ecosystem with vendors who are crazy experienced and not even a little bit sketchy.

\n

You’re using a ton of different tools to execute on your digital marketing

\n

Versatility used to be what WordPress was known for, but as the number of plugins and developers creating them increases, growing businesses need a less complicated solution. WordPress, as a free CMS with some paid plugins and themes, is a great foundation for a new small business, but once a business starts to move in the direction of lead generation, its needs become more complex.

Now that HubSpot has launched a free version of their CMS, B2B demand generation for startups has become simpler, which is definitely a consideration for those who might’ve gone straight to WordPress in the past. HubSpot CMS Hub Free is HubSpot’s introductory CMS package. It includes premium hosting on HubSpot, the option to build a from-scratch website (with forms, live chat, landing pages, and a blog), and its free CRM platform. This is a perfect option for small businesses that cannot afford HubSpot quite yet, but want to dig into its tools and build a website that creates awareness and builds their brand. It does have a few limitations, however:

\n

\n
• Limited to 25 website pages
\n
• Limited to one blog with 100 posts
\n
• No ability to modify system pages
\n
• HubSpot branding on website pages, blog posts and landing pages
\n

\n

While it might not be for everyone, it gives startups a powerful, free, and simple way to get their brand off the ground. A perfect example is this super basic website we stood up in only three hours using HubSpot CMS Free.

Many growing businesses operating with a WordPress website end up paying a premium for a form manager, SEO plugin, analytics tool, CRM, email marketing platform, and automation solution. All of these different tools not only don’t speak to one another (unless you pay for another integration tool to centralize them), but your marketing team has to login to every single platform to manage information and execute your marketing. It’s cumbersome and inefficient.

With HubSpot, you’re managing everything in one portal. From CMS tools to social media marketing, ad management, CRM for sales and email marketing, automation, blogging, SEO, and analytics — it doesn’t get more centralized than that. While all the tools in HubSpot can be costly when purchased together, HubSpot allows you to close the loop with your content marketing and sales processes, attributing revenue to your campaigns and gaining a full view on what efforts are working, so you can execute more of them. With WordPress, you have to be incredibly organized to use all the different tools. You’ll also probably need to create your own spreadsheets to allow you to really understand where your revenue is coming from.

Keeping your tech stack small helps fuel your marketing team to make educated decisions and work more efficiently.

\n

You've coded yourself into a corner

\n

Probably the biggest pitfall that comes with working in WordPress is a bloated website. While we’ve outlined a a few different factors that can contribute to website bloat and how you can optimize your page speed, you cannot unwind the drag that comes with adding poorly coded plugins to your website.

The more plugins you add to your site, the more code a browser has to load, which can bog down your load speed. While you can limit your plugins and have a developer recommend the best ones, eventually you may want to add advanced functionality such as calculators or a robust resource center to your content arsenal.

HubSpot allows you to add functionality to your website with modules that can be coded by a HubSpot developer who knows best practices. Using one development partner who is certified keeps your website code clean and can ensure that your website doesn’t just pile on code from multiple different developers with plugins that break or leave security holes.

\n

It's more secure

\n

WordPress sites are notorious for experiencing malware attacks. While keeping your plugins and WordPress up to date helps, malware attacks can still occur. Security is an extremely important aspect of your website, and HubSpot has the edge over WordPress here.

Because WordPress is open source, hackers can find security holes and exploit the platform easily. In addition, many of the available plugins aren’t supported and updated by the developers who created them. This makes WordPress sites easy targets.

WordPress theme and plugin developers typically bundle quite a few different plugins together to bring a full suite for you to take advantage of, but this can also create dependencies that aren’t updated correctly. Even if the theme is up to date, sometimes those smaller packages underneath aren’t updated and can create additional security vulnerabilities on your site.

HubSpot, however, has SSL encryption, which not only boosts your rankings with Google, but assures the users whose information you’re collecting that their information is safe. In HubSPot, you automatically receive a standard SAN SSL certification through DigiCert when you connect a domain to your account. If you purchase the custom SSL add-on, you can upload custom SSL certifications to HubSpot and configure security settings. Learn more about your SSL options in HubSpot here.

If you’re cost conscious and don’t plan to do much with your website, WordPress may have been a no-brainer for you. It’s free and has infinite customization options. Just be sure if you opt in to WordPress, you update plugins and WordPress regularly, manage comments, and have your site checked for security issues regularly.

If you’re cost conscious and looking for a starter platform that will grow with you as your marketing budget grows and lead generation is important to you, look to HubSpot. While we’re not currently offering development help on CMS Hub Free, we can definitely give you what you need once you’re ready to upgrade your HubSpot CMS Hub and build something that will suit you as you grow. HubSpot’s CRM is unmatched when it comes to sales, and we think that from a sustainability standpoint there’s no better platform for a growing business that is investing heavily into its sales and marketing strategies.

For a scaling business that uses its website as a lead generation tool, you’ll eventually need a better way to make website improvements, ensure the security of your site, and prevent website bloat. We’ve been huge supporters of HubSpot since they were just a tiny piece of analytics code. They continue to prove that they’re not only surpassing best practices, but setting new benchmarks for what to expect from a CMS and comprehensive marketing automation software.

If you’re considering a switch to HubSpot CMS Professional, we’d love to give you a rundown of the power of HubSpot.

\n

","tag_ids":[62770442823,81427988227],"topic_ids":[62770442823,81427988227],"post_summary":"

Is it finally time to leave WordPress for HubSpot CMS? For a long time, WordPress was the most flexible game in town when it came to content management systems (CMS). With so much functionality in plugins and a huge number of developers working within it, it has been the industry standard for years for those looking to develop complex websites with flexible functionality. It’s open-source, so anyone can create plugins, fixes, themes, or modules. There are dozens of free themes that can have you up and running in no time..

But for a growing business that will be focusing heavily on marketing and building a website robust in resources that grows with them? We’re no longer selling WordPress as a solution for our clients.

Here’s why we think it’s finally time to leave WordPress for HubSpot CMS.

\n","blog_post_schedule_task_uid":null,"blog_publish_to_social_media_task":"DONE_NOT_SENT","blog_publish_instant_email_task_uid":null,"blog_publish_instant_email_campaign_id":null,"blog_publish_instant_email_retry_count":null,"keywords":[],"head_html":null,"footer_html":null,"attached_stylesheets":[],"enable_domain_stylesheets":null,"include_default_custom_css":null,"meta_description":"WordPress has served us well for a long time, but it's time to switch to HubSpot CMS - here's why:","meta_keywords":null,"layout_sections":{},"past_mab_experiment_ids":[],"deleted_by":null,"featured_image_alt_text":"","enable_layout_stylesheets":null,"tweet":null,"tweet_at":null,"campaign_name":null,"campaign_utm":null,"tweet_immediately":false,"publish_immediately":true,"security_state":"NONE","scheduled_update_date":0,"placement_guids":[],"property_for_dynamic_page_title":null,"property_for_dynamic_page_slug":null,"property_for_dynamic_page_meta_description":null,"property_for_dynamic_page_featured_image":null,"property_for_dynamic_page_canonical_url":null,"preview_image_src":null,"legacy_blog_tabid":null,"legacy_post_guid":null,"performable_variation_letter":null,"style_override_id":null,"has_user_changes":true,"css":{},"css_text":"","unpublished_at":0,"published_by_id":61310730,"allowed_slug_conflict":false,"ai_features":null,"link_rel_canonical_url":"","page_redirected":false,"page_expiry_enabled":null,"page_expiry_date":null,"page_expiry_redirect_id":null,"page_expiry_redirect_url":null,"deleted_by_id":null,"state_when_deleted":null,"cloned_from":null,"staged_from":null,"personas":[],"compose_body":null,"featured_image":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-wordpress%20to%20hubspot.png","featured_image_width":1080,"featured_image_height":1080,"publish_timezone_offset":null,"theme_settings_values":null,"password":null,"header":null,"published_at":1722397568400,"last_edit_session_id":null,"last_edit_update_id":null,"created_by_agent":null},"metaDescription":"WordPress has served us well for a long time, but it's time to switch to HubSpot CMS - here's why:","metaKeywords":null,"name":"It's Time to Leave WordPress for HubSpot CMS","nextPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/64.png","nextPostFeaturedImageAltText":"cms development pastel","nextPostName":"HubSpot CMS Development Quality Assurance: Why We Love Pastel","nextPostSlug":"blogs/hubspot-cms-development-quality-assurance-why-we-love-pastel","pageExpiryDate":null,"pageExpiryEnabled":null,"pageExpiryRedirectId":null,"pageExpiryRedirectUrl":null,"pageRedirected":false,"pageTitle":"It's Time to Leave WordPress for HubSpot CMS","parentBlog":{"absoluteUrl":"https://deckerdevs.com/blogs","allowComments":true,"ampBodyColor":"#404040","ampBodyFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampBodyFontSize":"18","ampCustomCss":"","ampHeaderBackgroundColor":"#ffffff","ampHeaderColor":"#1e1e1e","ampHeaderFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampHeaderFontSize":"36","ampLinkColor":"#416bb3","ampLogoAlt":"","ampLogoHeight":0,"ampLogoSrc":"","ampLogoWidth":0,"analyticsPageId":62179259185,"attachedStylesheets":[],"audienceAccess":"PUBLIC","businessUnitId":null,"captchaAfterDays":7,"captchaAlways":false,"categoryId":3,"cdnPurgeEmbargoTime":null,"closeCommentsOlder":0,"commentDateFormat":"medium","commentFormGuid":"cb653aa1-3db4-4167-9b59-744c46d49682","commentMaxThreadDepth":3,"commentModeration":false,"commentNotificationEmails":["nicholas@deckerdevs.com","jessica@deckerdevs.com"],"commentShouldCreateContact":true,"commentVerificationText":"Thanks for participating in this conversation! We look forward to responding and to assisting where we can","cosObjectType":"BLOG","created":1639786189589,"createdDateTime":1639786189589,"dailyNotificationEmailId":null,"dateFormattingLanguage":null,"defaultGroupStyleId":"","defaultNotificationFromName":"","defaultNotificationReplyTo":"","deletedAt":0,"description":"rev up your hubspot system to the max! deckerdevs' turbo-charged blog is your ultimate guide to harnessing the full potential of hubspot development. unleash the marketing magic with ingenious tips, tricks, and hacks. get ready to level up your hubspot game!","domain":"","domainWhenPublished":"deckerdevs.com","emailApiSubscriptionId":null,"enableGoogleAmpOutput":false,"enableSocialAutoPublishing":false,"generateJsonLdEnabled":true,"header":null,"htmlFooter":"","htmlFooterIsShared":true,"htmlHead":"","htmlHeadIsShared":true,"htmlKeywords":[],"htmlTitle":"deckerdevs thought nuggets","id":62179259185,"ilsSubscriptionListsByType":{},"instantNotificationEmailId":null,"itemLayoutId":null,"itemTemplateIsShared":false,"itemTemplatePath":"deckerdevs-theme/templates/blog-content.html","label":"deckerdevs live blog","language":"en","legacyGuid":null,"legacyModuleId":null,"legacyTabId":null,"listingLayoutId":null,"listingPageId":62179259186,"listingTemplatePath":"","liveDomain":"deckerdevs.com","monthFilterFormat":"MMMM yyyy","monthlyNotificationEmailId":null,"name":"deckerdevs live blog","parentBlogUpdateTaskId":null,"portalId":6534445,"postHtmlFooter":"","postHtmlHead":"","postsPerListingPage":9,"postsPerRssFeed":10,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publicTitle":"thought nuggets","publishDateFormat":"medium","resolvedDomain":"deckerdevs.com","rootUrl":"https://deckerdevs.com/blogs","rssCustomFeed":null,"rssDescription":null,"rssItemFooter":null,"rssItemHeader":null,"settingsOverrides":{"itemLayoutId":false,"itemTemplatePath":false,"itemTemplateIsShared":false,"listingLayoutId":false,"listingTemplatePath":false,"postsPerListingPage":false,"showSummaryInListing":false,"useFeaturedImageInSummary":false,"htmlHead":false,"postHtmlHead":false,"htmlHeadIsShared":false,"htmlFooter":false,"listingPageHtmlFooter":false,"postHtmlFooter":false,"htmlFooterIsShared":false,"attachedStylesheets":false,"postsPerRssFeed":false,"showSummaryInRss":false,"showSummaryInEmails":false,"showSummariesInEmails":false,"allowComments":false,"commentShouldCreateContact":false,"commentModeration":false,"closeCommentsOlder":false,"commentNotificationEmails":false,"commentMaxThreadDepth":false,"commentVerificationText":false,"socialAccountTwitter":false,"showSocialLinkTwitter":false,"showSocialLinkLinkedin":false,"showSocialLinkFacebook":false,"enableGoogleAmpOutput":false,"ampLogoSrc":false,"ampLogoHeight":false,"ampLogoWidth":false,"ampLogoAlt":false,"ampHeaderFont":false,"ampHeaderFontSize":false,"ampHeaderColor":false,"ampHeaderBackgroundColor":false,"ampBodyFont":false,"ampBodyFontSize":false,"ampBodyColor":false,"ampLinkColor":false,"generateJsonLdEnabled":false},"showSocialLinkFacebook":true,"showSocialLinkLinkedin":true,"showSocialLinkTwitter":true,"showSummaryInEmails":true,"showSummaryInListing":true,"showSummaryInRss":true,"siteId":null,"slug":"blogs","socialAccountTwitter":"","state":null,"subscriptionContactsProperty":null,"subscriptionEmailType":null,"subscriptionFormGuid":null,"subscriptionListsByType":{},"title":null,"translatedFromId":null,"translations":{},"updated":1712344124471,"updatedDateTime":1712344124471,"urlBase":"deckerdevs.com/blogs","urlSegments":{"all":"all","archive":"archive","author":"author","page":"page","tag":"tag"},"useFeaturedImageInSummary":true,"usesDefaultTemplate":false,"weeklyNotificationEmailId":null},"password":null,"pastMabExperimentIds":[],"performableGuid":null,"performableVariationLetter":null,"personas":[],"placementGuids":[],"portableKey":null,"portalId":6534445,"position":null,"postBody":"

Is it finally time to leave WordPress for HubSpot CMS? For a long time, WordPress was the most flexible game in town when it came to content management systems (CMS). With so much functionality in plugins and a huge number of developers working within it, it has been the industry standard for years for those looking to develop complex websites with flexible functionality. It’s open-source, so anyone can create plugins, fixes, themes, or modules. There are dozens of free themes that can have you up and running in no time..

But for a growing business that will be focusing heavily on marketing and building a website robust in resources that grows with them? We’re no longer selling WordPress as a solution for our clients.

Here’s why we think it’s finally time to leave WordPress for HubSpot CMS.

\n\n

You get what you pay for

\n

One of the best things about WordPress is that it’s free. You pay for your themes and plugins and the developers who created them usually provide support, or you can hire a web developer if you need either more support or ongoing development expertise. However, that can come at a cost. Security issues, plugins not functioning as you’d hoped, and your website loading more slowly because of so many plugins are just a few common issues with WordPress.

Keep in mind that if you want a robust solution, you’re going to have to fork out a little cash. Committing an investment to HubSpot CMS might mean paying a monthly or annual fee, but it’ll give you a lot more capabilities out of the box without the additional frustration.

HubSpot support is super helpful and not outsourced, so you’re speaking to humans who really understand the platform. Not to mention, there’s an entire fully vetted and trained developer ecosystem with vendors who are crazy experienced and not even a little bit sketchy.

\n

You’re using a ton of different tools to execute on your digital marketing

\n

Versatility used to be what WordPress was known for, but as the number of plugins and developers creating them increases, growing businesses need a less complicated solution. WordPress, as a free CMS with some paid plugins and themes, is a great foundation for a new small business, but once a business starts to move in the direction of lead generation, its needs become more complex.

Now that HubSpot has launched a free version of their CMS, B2B demand generation for startups has become simpler, which is definitely a consideration for those who might’ve gone straight to WordPress in the past. HubSpot CMS Hub Free is HubSpot’s introductory CMS package. It includes premium hosting on HubSpot, the option to build a from-scratch website (with forms, live chat, landing pages, and a blog), and its free CRM platform. This is a perfect option for small businesses that cannot afford HubSpot quite yet, but want to dig into its tools and build a website that creates awareness and builds their brand. It does have a few limitations, however:

\n

\n
• Limited to 25 website pages
\n
• Limited to one blog with 100 posts
\n
• No ability to modify system pages
\n
• HubSpot branding on website pages, blog posts and landing pages
\n

\n

While it might not be for everyone, it gives startups a powerful, free, and simple way to get their brand off the ground. A perfect example is this super basic website we stood up in only three hours using HubSpot CMS Free.

Many growing businesses operating with a WordPress website end up paying a premium for a form manager, SEO plugin, analytics tool, CRM, email marketing platform, and automation solution. All of these different tools not only don’t speak to one another (unless you pay for another integration tool to centralize them), but your marketing team has to login to every single platform to manage information and execute your marketing. It’s cumbersome and inefficient.

With HubSpot, you’re managing everything in one portal. From CMS tools to social media marketing, ad management, CRM for sales and email marketing, automation, blogging, SEO, and analytics — it doesn’t get more centralized than that. While all the tools in HubSpot can be costly when purchased together, HubSpot allows you to close the loop with your content marketing and sales processes, attributing revenue to your campaigns and gaining a full view on what efforts are working, so you can execute more of them. With WordPress, you have to be incredibly organized to use all the different tools. You’ll also probably need to create your own spreadsheets to allow you to really understand where your revenue is coming from.

Keeping your tech stack small helps fuel your marketing team to make educated decisions and work more efficiently.

\n

You've coded yourself into a corner

\n

Probably the biggest pitfall that comes with working in WordPress is a bloated website. While we’ve outlined a a few different factors that can contribute to website bloat and how you can optimize your page speed, you cannot unwind the drag that comes with adding poorly coded plugins to your website.

The more plugins you add to your site, the more code a browser has to load, which can bog down your load speed. While you can limit your plugins and have a developer recommend the best ones, eventually you may want to add advanced functionality such as calculators or a robust resource center to your content arsenal.

HubSpot allows you to add functionality to your website with modules that can be coded by a HubSpot developer who knows best practices. Using one development partner who is certified keeps your website code clean and can ensure that your website doesn’t just pile on code from multiple different developers with plugins that break or leave security holes.

\n

It's more secure

\n

WordPress sites are notorious for experiencing malware attacks. While keeping your plugins and WordPress up to date helps, malware attacks can still occur. Security is an extremely important aspect of your website, and HubSpot has the edge over WordPress here.

Because WordPress is open source, hackers can find security holes and exploit the platform easily. In addition, many of the available plugins aren’t supported and updated by the developers who created them. This makes WordPress sites easy targets.

WordPress theme and plugin developers typically bundle quite a few different plugins together to bring a full suite for you to take advantage of, but this can also create dependencies that aren’t updated correctly. Even if the theme is up to date, sometimes those smaller packages underneath aren’t updated and can create additional security vulnerabilities on your site.

HubSpot, however, has SSL encryption, which not only boosts your rankings with Google, but assures the users whose information you’re collecting that their information is safe. In HubSPot, you automatically receive a standard SAN SSL certification through DigiCert when you connect a domain to your account. If you purchase the custom SSL add-on, you can upload custom SSL certifications to HubSpot and configure security settings. Learn more about your SSL options in HubSpot here.

If you’re cost conscious and don’t plan to do much with your website, WordPress may have been a no-brainer for you. It’s free and has infinite customization options. Just be sure if you opt in to WordPress, you update plugins and WordPress regularly, manage comments, and have your site checked for security issues regularly.

If you’re cost conscious and looking for a starter platform that will grow with you as your marketing budget grows and lead generation is important to you, look to HubSpot. While we’re not currently offering development help on CMS Hub Free, we can definitely give you what you need once you’re ready to upgrade your HubSpot CMS Hub and build something that will suit you as you grow. HubSpot’s CRM is unmatched when it comes to sales, and we think that from a sustainability standpoint there’s no better platform for a growing business that is investing heavily into its sales and marketing strategies.

For a scaling business that uses its website as a lead generation tool, you’ll eventually need a better way to make website improvements, ensure the security of your site, and prevent website bloat. We’ve been huge supporters of HubSpot since they were just a tiny piece of analytics code. They continue to prove that they’re not only surpassing best practices, but setting new benchmarks for what to expect from a CMS and comprehensive marketing automation software.

If you’re considering a switch to HubSpot CMS Professional, we’d love to give you a rundown of the power of HubSpot.

\n

","postBodyRss":"

Is it finally time to leave WordPress for HubSpot CMS? For a long time, WordPress was the most flexible game in town when it came to content management systems (CMS). With so much functionality in plugins and a huge number of developers working within it, it has been the industry standard for years for those looking to develop complex websites with flexible functionality. It’s open-source, so anyone can create plugins, fixes, themes, or modules. There are dozens of free themes that can have you up and running in no time..

But for a growing business that will be focusing heavily on marketing and building a website robust in resources that grows with them? We’re no longer selling WordPress as a solution for our clients.

Here’s why we think it’s finally time to leave WordPress for HubSpot CMS.

\n\n

You get what you pay for

\n

One of the best things about WordPress is that it’s free. You pay for your themes and plugins and the developers who created them usually provide support, or you can hire a web developer if you need either more support or ongoing development expertise. However, that can come at a cost. Security issues, plugins not functioning as you’d hoped, and your website loading more slowly because of so many plugins are just a few common issues with WordPress.

Keep in mind that if you want a robust solution, you’re going to have to fork out a little cash. Committing an investment to HubSpot CMS might mean paying a monthly or annual fee, but it’ll give you a lot more capabilities out of the box without the additional frustration.

HubSpot support is super helpful and not outsourced, so you’re speaking to humans who really understand the platform. Not to mention, there’s an entire fully vetted and trained developer ecosystem with vendors who are crazy experienced and not even a little bit sketchy.

\n

You’re using a ton of different tools to execute on your digital marketing

\n

Versatility used to be what WordPress was known for, but as the number of plugins and developers creating them increases, growing businesses need a less complicated solution. WordPress, as a free CMS with some paid plugins and themes, is a great foundation for a new small business, but once a business starts to move in the direction of lead generation, its needs become more complex.

Now that HubSpot has launched a free version of their CMS, B2B demand generation for startups has become simpler, which is definitely a consideration for those who might’ve gone straight to WordPress in the past. HubSpot CMS Hub Free is HubSpot’s introductory CMS package. It includes premium hosting on HubSpot, the option to build a from-scratch website (with forms, live chat, landing pages, and a blog), and its free CRM platform. This is a perfect option for small businesses that cannot afford HubSpot quite yet, but want to dig into its tools and build a website that creates awareness and builds their brand. It does have a few limitations, however:

\n

\n
• Limited to 25 website pages
\n
• Limited to one blog with 100 posts
\n
• No ability to modify system pages
\n
• HubSpot branding on website pages, blog posts and landing pages
\n

\n

While it might not be for everyone, it gives startups a powerful, free, and simple way to get their brand off the ground. A perfect example is this super basic website we stood up in only three hours using HubSpot CMS Free.

Many growing businesses operating with a WordPress website end up paying a premium for a form manager, SEO plugin, analytics tool, CRM, email marketing platform, and automation solution. All of these different tools not only don’t speak to one another (unless you pay for another integration tool to centralize them), but your marketing team has to login to every single platform to manage information and execute your marketing. It’s cumbersome and inefficient.

With HubSpot, you’re managing everything in one portal. From CMS tools to social media marketing, ad management, CRM for sales and email marketing, automation, blogging, SEO, and analytics — it doesn’t get more centralized than that. While all the tools in HubSpot can be costly when purchased together, HubSpot allows you to close the loop with your content marketing and sales processes, attributing revenue to your campaigns and gaining a full view on what efforts are working, so you can execute more of them. With WordPress, you have to be incredibly organized to use all the different tools. You’ll also probably need to create your own spreadsheets to allow you to really understand where your revenue is coming from.

Keeping your tech stack small helps fuel your marketing team to make educated decisions and work more efficiently.

\n

You've coded yourself into a corner

\n

Probably the biggest pitfall that comes with working in WordPress is a bloated website. While we’ve outlined a a few different factors that can contribute to website bloat and how you can optimize your page speed, you cannot unwind the drag that comes with adding poorly coded plugins to your website.

The more plugins you add to your site, the more code a browser has to load, which can bog down your load speed. While you can limit your plugins and have a developer recommend the best ones, eventually you may want to add advanced functionality such as calculators or a robust resource center to your content arsenal.

HubSpot allows you to add functionality to your website with modules that can be coded by a HubSpot developer who knows best practices. Using one development partner who is certified keeps your website code clean and can ensure that your website doesn’t just pile on code from multiple different developers with plugins that break or leave security holes.

\n

It's more secure

\n

WordPress sites are notorious for experiencing malware attacks. While keeping your plugins and WordPress up to date helps, malware attacks can still occur. Security is an extremely important aspect of your website, and HubSpot has the edge over WordPress here.

Because WordPress is open source, hackers can find security holes and exploit the platform easily. In addition, many of the available plugins aren’t supported and updated by the developers who created them. This makes WordPress sites easy targets.

WordPress theme and plugin developers typically bundle quite a few different plugins together to bring a full suite for you to take advantage of, but this can also create dependencies that aren’t updated correctly. Even if the theme is up to date, sometimes those smaller packages underneath aren’t updated and can create additional security vulnerabilities on your site.

HubSpot, however, has SSL encryption, which not only boosts your rankings with Google, but assures the users whose information you’re collecting that their information is safe. In HubSPot, you automatically receive a standard SAN SSL certification through DigiCert when you connect a domain to your account. If you purchase the custom SSL add-on, you can upload custom SSL certifications to HubSpot and configure security settings. Learn more about your SSL options in HubSpot here.

If you’re cost conscious and don’t plan to do much with your website, WordPress may have been a no-brainer for you. It’s free and has infinite customization options. Just be sure if you opt in to WordPress, you update plugins and WordPress regularly, manage comments, and have your site checked for security issues regularly.

If you’re cost conscious and looking for a starter platform that will grow with you as your marketing budget grows and lead generation is important to you, look to HubSpot. While we’re not currently offering development help on CMS Hub Free, we can definitely give you what you need once you’re ready to upgrade your HubSpot CMS Hub and build something that will suit you as you grow. HubSpot’s CRM is unmatched when it comes to sales, and we think that from a sustainability standpoint there’s no better platform for a growing business that is investing heavily into its sales and marketing strategies.

For a scaling business that uses its website as a lead generation tool, you’ll eventually need a better way to make website improvements, ensure the security of your site, and prevent website bloat. We’ve been huge supporters of HubSpot since they were just a tiny piece of analytics code. They continue to prove that they’re not only surpassing best practices, but setting new benchmarks for what to expect from a CMS and comprehensive marketing automation software.

If you’re considering a switch to HubSpot CMS Professional, we’d love to give you a rundown of the power of HubSpot.

\n

","postEmailContent":"

Is it finally time to leave WordPress for HubSpot CMS? For a long time, WordPress was the most flexible game in town when it came to content management systems (CMS). With so much functionality in plugins and a huge number of developers working within it, it has been the industry standard for years for those looking to develop complex websites with flexible functionality. It’s open-source, so anyone can create plugins, fixes, themes, or modules. There are dozens of free themes that can have you up and running in no time..

But for a growing business that will be focusing heavily on marketing and building a website robust in resources that grows with them? We’re no longer selling WordPress as a solution for our clients.

Here’s why we think it’s finally time to leave WordPress for HubSpot CMS.

","postFeaturedImageIfEnabled":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-wordpress%20to%20hubspot.png","postListContent":"

Is it finally time to leave WordPress for HubSpot CMS? For a long time, WordPress was the most flexible game in town when it came to content management systems (CMS). With so much functionality in plugins and a huge number of developers working within it, it has been the industry standard for years for those looking to develop complex websites with flexible functionality. It’s open-source, so anyone can create plugins, fixes, themes, or modules. There are dozens of free themes that can have you up and running in no time..

But for a growing business that will be focusing heavily on marketing and building a website robust in resources that grows with them? We’re no longer selling WordPress as a solution for our clients.

Here’s why we think it’s finally time to leave WordPress for HubSpot CMS.

","postListSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-wordpress%20to%20hubspot.png","postRssContent":"

Is it finally time to leave WordPress for HubSpot CMS? For a long time, WordPress was the most flexible game in town when it came to content management systems (CMS). With so much functionality in plugins and a huge number of developers working within it, it has been the industry standard for years for those looking to develop complex websites with flexible functionality. It’s open-source, so anyone can create plugins, fixes, themes, or modules. There are dozens of free themes that can have you up and running in no time..

But for a growing business that will be focusing heavily on marketing and building a website robust in resources that grows with them? We’re no longer selling WordPress as a solution for our clients.

Here’s why we think it’s finally time to leave WordPress for HubSpot CMS.

","postRssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-wordpress%20to%20hubspot.png","postSummary":"

Is it finally time to leave WordPress for HubSpot CMS? For a long time, WordPress was the most flexible game in town when it came to content management systems (CMS). With so much functionality in plugins and a huge number of developers working within it, it has been the industry standard for years for those looking to develop complex websites with flexible functionality. It’s open-source, so anyone can create plugins, fixes, themes, or modules. There are dozens of free themes that can have you up and running in no time..

But for a growing business that will be focusing heavily on marketing and building a website robust in resources that grows with them? We’re no longer selling WordPress as a solution for our clients.

Here’s why we think it’s finally time to leave WordPress for HubSpot CMS.

\n","postSummaryRss":"

Is it finally time to leave WordPress for HubSpot CMS? For a long time, WordPress was the most flexible game in town when it came to content management systems (CMS). With so much functionality in plugins and a huge number of developers working within it, it has been the industry standard for years for those looking to develop complex websites with flexible functionality. It’s open-source, so anyone can create plugins, fixes, themes, or modules. There are dozens of free themes that can have you up and running in no time..

But for a growing business that will be focusing heavily on marketing and building a website robust in resources that grows with them? We’re no longer selling WordPress as a solution for our clients.

Here’s why we think it’s finally time to leave WordPress for HubSpot CMS.

","postTemplate":"deckerdevs-theme/templates/blog-content.html","previewImageSrc":null,"previewKey":"DCeNhgsa","previousPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-quality%20assurance.png","previousPostFeaturedImageAltText":"","previousPostName":"Website Quality Assurance: You Need QA in HubSpot CMS Development","previousPostSlug":"blogs/website-quality-assurance-you-need-qa-in-hubspot-cms-development","processingStatus":"PUBLISHED","propertyForDynamicPageCanonicalUrl":null,"propertyForDynamicPageFeaturedImage":null,"propertyForDynamicPageMetaDescription":null,"propertyForDynamicPageSlug":null,"propertyForDynamicPageTitle":null,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publishDate":1659890640000,"publishDateLocalTime":1659890640000,"publishDateLocalized":{"date":1659890640000,"format":"medium","language":null},"publishImmediately":true,"publishTimezoneOffset":null,"publishedAt":1722397568400,"publishedByEmail":null,"publishedById":61310730,"publishedByName":null,"publishedUrl":"https://deckerdevs.com/blogs/its-time-to-leave-wordpress-for-hubspot-cms","resolvedDomain":"deckerdevs.com","resolvedLanguage":null,"rssBody":"

Is it finally time to leave WordPress for HubSpot CMS? For a long time, WordPress was the most flexible game in town when it came to content management systems (CMS). With so much functionality in plugins and a huge number of developers working within it, it has been the industry standard for years for those looking to develop complex websites with flexible functionality. It’s open-source, so anyone can create plugins, fixes, themes, or modules. There are dozens of free themes that can have you up and running in no time..

But for a growing business that will be focusing heavily on marketing and building a website robust in resources that grows with them? We’re no longer selling WordPress as a solution for our clients.

Here’s why we think it’s finally time to leave WordPress for HubSpot CMS.

\n\n

You get what you pay for

\n

One of the best things about WordPress is that it’s free. You pay for your themes and plugins and the developers who created them usually provide support, or you can hire a web developer if you need either more support or ongoing development expertise. However, that can come at a cost. Security issues, plugins not functioning as you’d hoped, and your website loading more slowly because of so many plugins are just a few common issues with WordPress.

Keep in mind that if you want a robust solution, you’re going to have to fork out a little cash. Committing an investment to HubSpot CMS might mean paying a monthly or annual fee, but it’ll give you a lot more capabilities out of the box without the additional frustration.

HubSpot support is super helpful and not outsourced, so you’re speaking to humans who really understand the platform. Not to mention, there’s an entire fully vetted and trained developer ecosystem with vendors who are crazy experienced and not even a little bit sketchy.

\n

You’re using a ton of different tools to execute on your digital marketing

\n

Versatility used to be what WordPress was known for, but as the number of plugins and developers creating them increases, growing businesses need a less complicated solution. WordPress, as a free CMS with some paid plugins and themes, is a great foundation for a new small business, but once a business starts to move in the direction of lead generation, its needs become more complex.

Now that HubSpot has launched a free version of their CMS, B2B demand generation for startups has become simpler, which is definitely a consideration for those who might’ve gone straight to WordPress in the past. HubSpot CMS Hub Free is HubSpot’s introductory CMS package. It includes premium hosting on HubSpot, the option to build a from-scratch website (with forms, live chat, landing pages, and a blog), and its free CRM platform. This is a perfect option for small businesses that cannot afford HubSpot quite yet, but want to dig into its tools and build a website that creates awareness and builds their brand. It does have a few limitations, however:

\n

\n
• Limited to 25 website pages
\n
• Limited to one blog with 100 posts
\n
• No ability to modify system pages
\n
• HubSpot branding on website pages, blog posts and landing pages
\n

\n

While it might not be for everyone, it gives startups a powerful, free, and simple way to get their brand off the ground. A perfect example is this super basic website we stood up in only three hours using HubSpot CMS Free.

Many growing businesses operating with a WordPress website end up paying a premium for a form manager, SEO plugin, analytics tool, CRM, email marketing platform, and automation solution. All of these different tools not only don’t speak to one another (unless you pay for another integration tool to centralize them), but your marketing team has to login to every single platform to manage information and execute your marketing. It’s cumbersome and inefficient.

With HubSpot, you’re managing everything in one portal. From CMS tools to social media marketing, ad management, CRM for sales and email marketing, automation, blogging, SEO, and analytics — it doesn’t get more centralized than that. While all the tools in HubSpot can be costly when purchased together, HubSpot allows you to close the loop with your content marketing and sales processes, attributing revenue to your campaigns and gaining a full view on what efforts are working, so you can execute more of them. With WordPress, you have to be incredibly organized to use all the different tools. You’ll also probably need to create your own spreadsheets to allow you to really understand where your revenue is coming from.

Keeping your tech stack small helps fuel your marketing team to make educated decisions and work more efficiently.

\n

You've coded yourself into a corner

\n

Probably the biggest pitfall that comes with working in WordPress is a bloated website. While we’ve outlined a a few different factors that can contribute to website bloat and how you can optimize your page speed, you cannot unwind the drag that comes with adding poorly coded plugins to your website.

The more plugins you add to your site, the more code a browser has to load, which can bog down your load speed. While you can limit your plugins and have a developer recommend the best ones, eventually you may want to add advanced functionality such as calculators or a robust resource center to your content arsenal.

HubSpot allows you to add functionality to your website with modules that can be coded by a HubSpot developer who knows best practices. Using one development partner who is certified keeps your website code clean and can ensure that your website doesn’t just pile on code from multiple different developers with plugins that break or leave security holes.

\n

It's more secure

\n

WordPress sites are notorious for experiencing malware attacks. While keeping your plugins and WordPress up to date helps, malware attacks can still occur. Security is an extremely important aspect of your website, and HubSpot has the edge over WordPress here.

Because WordPress is open source, hackers can find security holes and exploit the platform easily. In addition, many of the available plugins aren’t supported and updated by the developers who created them. This makes WordPress sites easy targets.

WordPress theme and plugin developers typically bundle quite a few different plugins together to bring a full suite for you to take advantage of, but this can also create dependencies that aren’t updated correctly. Even if the theme is up to date, sometimes those smaller packages underneath aren’t updated and can create additional security vulnerabilities on your site.

HubSpot, however, has SSL encryption, which not only boosts your rankings with Google, but assures the users whose information you’re collecting that their information is safe. In HubSPot, you automatically receive a standard SAN SSL certification through DigiCert when you connect a domain to your account. If you purchase the custom SSL add-on, you can upload custom SSL certifications to HubSpot and configure security settings. Learn more about your SSL options in HubSpot here.

If you’re cost conscious and don’t plan to do much with your website, WordPress may have been a no-brainer for you. It’s free and has infinite customization options. Just be sure if you opt in to WordPress, you update plugins and WordPress regularly, manage comments, and have your site checked for security issues regularly.

If you’re cost conscious and looking for a starter platform that will grow with you as your marketing budget grows and lead generation is important to you, look to HubSpot. While we’re not currently offering development help on CMS Hub Free, we can definitely give you what you need once you’re ready to upgrade your HubSpot CMS Hub and build something that will suit you as you grow. HubSpot’s CRM is unmatched when it comes to sales, and we think that from a sustainability standpoint there’s no better platform for a growing business that is investing heavily into its sales and marketing strategies.

For a scaling business that uses its website as a lead generation tool, you’ll eventually need a better way to make website improvements, ensure the security of your site, and prevent website bloat. We’ve been huge supporters of HubSpot since they were just a tiny piece of analytics code. They continue to prove that they’re not only surpassing best practices, but setting new benchmarks for what to expect from a CMS and comprehensive marketing automation software.

If you’re considering a switch to HubSpot CMS Professional, we’d love to give you a rundown of the power of HubSpot.

\n

","rssSummary":"

Is it finally time to leave WordPress for HubSpot CMS? For a long time, WordPress was the most flexible game in town when it came to content management systems (CMS). With so much functionality in plugins and a huge number of developers working within it, it has been the industry standard for years for those looking to develop complex websites with flexible functionality. It’s open-source, so anyone can create plugins, fixes, themes, or modules. There are dozens of free themes that can have you up and running in no time..

But for a growing business that will be focusing heavily on marketing and building a website robust in resources that grows with them? We’re no longer selling WordPress as a solution for our clients.

Here’s why we think it’s finally time to leave WordPress for HubSpot CMS.

\n","rssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-wordpress%20to%20hubspot.png","scheduledUpdateDate":0,"screenshotPreviewTakenAt":1736739968180,"screenshotPreviewUrl":"https://cdn1.hubspot.net/hubshotv3/prod/e/0/e88a2e6e-c945-4d62-9e4e-e1d2a0cefc27.png","sections":{},"securityState":"NONE","siteId":null,"slug":"blogs/its-time-to-leave-wordpress-for-hubspot-cms","stagedFrom":null,"state":"PUBLISHED","stateWhenDeleted":null,"structuredContentPageType":null,"structuredContentType":null,"styleOverrideId":null,"subcategory":"normal_blog_post","syncedWithBlogRoot":true,"tagIds":[62770442823,81427988227],"tagList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1659976163308,"deletedAt":0,"description":"","id":81427988227,"label":"HubSpot CMS","language":"en","name":"HubSpot CMS","portalId":6534445,"slug":"hubspot-cms","translatedFromId":null,"translations":{},"updated":1659976163308}],"tagNames":["HubSpot CMS Development","HubSpot CMS"],"teamPerms":[],"templatePath":"","templatePathForRender":"deckerdevs-theme/templates/blog-content.html","textToAudioFileId":null,"textToAudioGenerationRequestId":null,"themePath":null,"themeSettingsValues":null,"title":"It's Time to Leave WordPress for HubSpot CMS","tmsId":null,"topicIds":[62770442823,81427988227],"topicList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1659976163308,"deletedAt":0,"description":"","id":81427988227,"label":"HubSpot CMS","language":"en","name":"HubSpot CMS","portalId":6534445,"slug":"hubspot-cms","translatedFromId":null,"translations":{},"updated":1659976163308}],"topicNames":["HubSpot CMS Development","HubSpot CMS"],"topics":[62770442823,81427988227],"translatedContent":{},"translatedFromId":null,"translations":{},"tweet":null,"tweetAt":null,"tweetImmediately":false,"unpublishedAt":0,"updated":1722397568405,"updatedById":61310730,"upsizeFeaturedImage":false,"url":"https://deckerdevs.com/blogs/its-time-to-leave-wordpress-for-hubspot-cms","useFeaturedImage":true,"userPerms":[],"views":null,"visibleToAll":null,"widgetContainers":{},"widgetcontainers":{},"widgets":{"blog-hero":{"body":{"column_split":"split-40-60","flip_columns_on_desktop":true,"heading":"It's Time to Leave WordPress for HubSpot CMS","heading_size":"h1","heading_tag":"h1","image_holder":{"image_field":{"alt":"deckerdevs-wordpress to hubspot","height":1080,"loading":"lazy","max_height":1080,"max_width":1080,"size_type":"auto","src":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-wordpress%20to%20hubspot.png","width":1080}}},"child_css":{},"css":{},"id":"blog-hero","label":null,"module_id":82854350373,"name":"blog-hero","order":1,"smart_type":null,"styles":{},"type":"module"},"blog-image":{"body":{"image_field":{"alt":"pattern-2","height":563,"loading":"lazy","max_height":563,"max_width":1000,"size_type":"auto","src":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/pattern-2.jpg","width":1000},"module_id":62246908725},"child_css":{},"css":{},"deleted_at":1692621870619,"id":"blog-image","label":null,"module_id":62246908725,"name":"blog-image","order":3,"smart_type":null,"styles":{},"type":"module"},"blog-posts":{"body":{"heading":"Some Other Recent Thoughts"},"child_css":{},"css":{},"id":"blog-posts","label":null,"module_id":82853805588,"name":"blog-posts","order":4,"smart_type":null,"styles":{},"type":"module"}}},{"ab":false,"abStatus":null,"abTestId":null,"abVariation":false,"abVariationAutomated":false,"absoluteUrl":"https://deckerdevs.com/blogs/hubspot-cms-development-quality-assurance-why-we-love-pastel","afterPostBody":null,"aifeatures":null,"allowedSlugConflict":false,"analytics":null,"analyticsPageId":"81217280881","analyticsPageType":"blog-post","approvalStatus":null,"archived":false,"archivedAt":0,"archivedInDashboard":false,"areCommentsAllowed":true,"attachedStylesheets":[],"audienceAccess":"PUBLIC","author":null,"authorName":null,"authorUsername":null,"blogAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogAuthorId":62235724408,"blogPostAuthor":{"avatar":"","bio":"","cdnPurgeEmbargoTime":null,"cosObjectType":"BLOG_AUTHOR","created":1639920511177,"deletedAt":0,"displayName":"deckerdevs","email":"","facebook":"","fullName":"deckerdevs","gravatarUrl":null,"hasSocialProfiles":false,"id":62235724408,"label":"deckerdevs","language":"en","linkedin":"","name":"deckerdevs","portalId":6534445,"slug":"deckerdevs","translatedFromId":null,"translations":{},"twitter":"","twitterUsername":"","updated":1639920511177,"userId":null,"username":null,"website":""},"blogPostScheduleTaskUid":null,"blogPublishInstantEmailCampaignId":null,"blogPublishInstantEmailRetryCount":null,"blogPublishInstantEmailTaskUid":null,"blogPublishToSocialMediaTask":"DONE_NOT_SENT","blueprintTypeId":0,"businessUnitId":null,"campaign":null,"campaignName":null,"campaignUtm":null,"category":3,"categoryId":3,"cdnPurgeEmbargoTime":null,"checkPostLevelAudienceAccessFirst":true,"clonedFrom":null,"composeBody":null,"compositionId":0,"contentAccessRuleIds":[],"contentAccessRuleTypes":[],"contentGroup":62179259185,"contentGroupId":62179259185,"contentTypeCategory":3,"contentTypeCategoryId":3,"contentTypeId":null,"created":1659715100819,"createdByAgent":null,"createdById":27630257,"createdTime":1659715100819,"crmObjectId":null,"css":{},"cssText":"","ctaClicks":null,"ctaViews":null,"currentState":"PUBLISHED","currentlyPublished":true,"deletedAt":0,"deletedBy":null,"deletedByEmail":null,"deletedById":null,"domain":"","dynamicPageDataSourceId":null,"dynamicPageDataSourceType":null,"dynamicPageHubDbTableId":null,"enableDomainStylesheets":null,"enableGoogleAmpOutputOverride":false,"enableLayoutStylesheets":null,"errors":[],"featuredImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/64.png","featuredImageAltText":"cms development pastel","featuredImageHeight":2700,"featuredImageLength":0,"featuredImageWidth":2700,"flexAreas":{},"folderId":null,"footerHtml":null,"freezeDate":1659716452000,"generateJsonLdEnabledOverride":true,"hasContentAccessRules":false,"hasUserChanges":true,"headHtml":null,"header":null,"htmlTitle":"HubSpot CMS Development Quality Assurance: Why We Love Pastel","id":81217280881,"includeDefaultCustomCss":null,"isCaptchaRequired":true,"isCrawlableByBots":false,"isDraft":false,"isInstanceLayoutPage":false,"isInstantEmailEnabled":false,"isPublished":true,"isSocialPublishingEnabled":false,"keywords":[],"label":"HubSpot CMS Development Quality Assurance: Why We Love Pastel","language":"en","lastEditSessionId":null,"lastEditUpdateId":null,"layoutSections":{},"legacyBlogTabid":null,"legacyId":null,"legacyPostGuid":null,"linkRelCanonicalUrl":"","listTemplate":"","liveDomain":"deckerdevs.com","mab":false,"mabExperimentId":null,"mabMaster":false,"mabVariant":false,"meta":{"html_title":"HubSpot CMS Development Quality Assurance: Why We Love Pastel","public_access_rules":[],"public_access_rules_enabled":false,"enable_google_amp_output_override":false,"generate_json_ld_enabled":true,"composition_id":0,"is_crawlable_by_bots":false,"use_featured_image":true,"post_body":"

Our team has been developing websites for many years and HubSpot CMS development quality assurance is one of the most important aspects of the development process. Our project management team and technical director love diving into newly developed modules and projects in an attempt to find bugs that need fixing or responsiveness and browser compatibility issues.

We use a comprehensive checklist for testing all active browsers on most major devices, manually testing responsiveness, reviewing design files in comparison to the “final” product, and testing module functionality for bugs. Through that process we use a few tools to ensure that nothing falls through the cracks. These tools include QA spreadsheets, BrowserStack to test browser compatibility, and perhaps our favorite collaboration and feedback tool, Pastel.

Pastel is a collaboration tool that allows internal teams, contractors, and clients to review marketing projects. We simply plug the project URL into usepastel.com and can quickly begin the review process with live browsing and the ability to easily click to add comments, update text, and collaborate for quick edits and updates. This is critical for us, since most of our team is remote.

For other teams looking for feedback collaboration software, or for agencies and companies that want to understand more about how a website should be reviewed for quality assurance, here’s a feature and benefit rundown of why we love Pastel for HubSpot CMS development feedback and communication for quality assurance testing.

\n\n

It avoids the 75-email edit strings

\n

According to a survey by Zippia.com, 80% of employees feel stressed because of ineffective company communication. Clearly no one likes inefficiency when it comes to communication, internally or externally.

One of the most difficult parts of managing communication surrounding website projects can be the multiple rounds of edits. If your developer or agency doesn’t have a simple way to communicate edits with a platform like Pastel, they can get caught in an endless string of back and forth messages.With no centralized feedback option, clients have to compile Google Docs, Powerpoint presentations, or those long strings of emails or Slack messages, which then need to be searched to find every single edit.

Not only does this increase the amount of time that a developer has to spend on updates, edits,and bug fixes, but sometimes a request can be overlooked, prolonging the process and sometimes even delaying the delivery of a completed site for review.

By having feedback centralized in Pastel, we avoid the extra communication, leaving our inboxes and Slack queue cleaner, our brains a little freer, and our development team that much more efficient. Keep in mind that not every client or employee likes to use new tools, so we still allow other feedback options, we just try to default to this to keep things organized.

\n

 

\n

It allows multiple people to leave feedback in one place.

\n

Of course, it’s easy to assign a single point of contact as a final word on a website, but how often does something get lost in translation? We’ve encountered scenarios when the people at the top are dictating their wants and needs to a marketing director or manager, only for the company’s CEO to step in with their internal team and provide the feedback our teams needed all along. In order to avoid issues with too many cooks in the kitchen while also allowing all eyes in for review, Pastel is a great alternative.

With Pastel, you can hover over sections of the website and pin comments to each section. The comment is sticky and remains in place as you navigate through the rest of the document. This allows you to easily click on comments while reviewing areas of concern to save time in describing issues and identifying the issue in question for the development team receiving the feedback.

You can also @mention any user to quickly ping them with a question, notify them of a new edit, or request an update. You can even hold clients and internal teams accountable by turning off commenting after a “comment deadline.” (This is a favorite feature for us when projects are running on tight timeframes and we need to hold everyone to their deadlines.)

\n

 

\n

You can stay organized and keep up to date on progress.

\n

Keeping comments organized can sometimes be a hassle, and if your development team has a huge list of edits and bug fixes, they may not know exactly how to prioritize them. You can mark items as high priority or categorize your edits using labels. Once a comment is labeled, the team can review it in real time and address high priority items or certain categories of issues, such as bug fixes, before wishlist items or additional feature functionality are addressed.

Pastel also allows for status updates so you can see how edits are progressing in real time. A status can be updated from Active to In Progress to In Review to Resolved by a team member. This keeps a project management team up to date and allows them to communicate timeframes with the client to manage expectations accordingly.

\n

 

\n

It offers “live” editing.

\n

Because Pastel pulls from the website URL, it allows you to use the same canvas for multiple rounds of edits if you want. If you use a live website URL for feedback, once the code is changed, the edits will reflect on the same document, allowing the team to verify those changes and make additional suggestions if needed.

\n

It integrates with other common marketing tools for seamless ticket or task creation.

\n

We’ve spoken to the team at Pastel; they have a lot of great ideas about how they’ll continue to evolve the software. They’ve communicated that their intent is to build on the number of integrations they offer to make it easier for development teams to use Pastel. . They’ve also assured us that big things are on the horizon for the platform.

We asked Valentin Stakov, founder at Pastel, what the company’s focus was and what agencies and developers could expect from Pastel in the coming months. He said, \"We're planning on improving our existing integrations to make them more robust, as well as building additional integrations. We're also focused on building out more tools to make it easier to communicate with your clients and to keep them updated on their projects.\"

For now, their website lists the following integrations here:

Asana
Monday
Trello
Adobe XD
Jira

Finding a tool with a forward-thinking team is important; we look forward to seeing what integrations these guys come up with in the future.

\n

It saves you time with additional functionality.

\n

Pastel has a few time-saving features as well.

Its interface allows you to easily add screenshots, upload files, and link URLs in the comments. If you want an image replaced on a web page, company file storage can sometimes take a bit to sort through.

\n

Basic responsiveness tests are also a perk of Pastel. While we use real browsers when available and BrowserStack for full browser compatibility testing, the simple toggle on Pastel gives the client and other reviewers a way t to visualize what the website will look like on both mobile and desktop, allowing for more eyes on the process.

Another common activity during launch preparation is tweaking copy and headlines. While all our clients operating in HubSpot CMS have the flexibility to make updates to all content and headlines themselves, sometimes you need those perfect words to make a website look launch-ready.

\n

 

\n

","rss_summary":"

Our team has been developing websites for many years and HubSpot CMS development quality assurance is one of the most important aspects of the development process. Our project management team and technical director love diving into newly developed modules and projects in an attempt to find bugs that need fixing or responsiveness and browser compatibility issues.

We use a comprehensive checklist for testing all active browsers on most major devices, manually testing responsiveness, reviewing design files in comparison to the “final” product, and testing module functionality for bugs. Through that process we use a few tools to ensure that nothing falls through the cracks. These tools include QA spreadsheets, BrowserStack to test browser compatibility, and perhaps our favorite collaboration and feedback tool, Pastel.

Pastel is a collaboration tool that allows internal teams, contractors, and clients to review marketing projects. We simply plug the project URL into usepastel.com and can quickly begin the review process with live browsing and the ability to easily click to add comments, update text, and collaborate for quick edits and updates. This is critical for us, since most of our team is remote.

For other teams looking for feedback collaboration software, or for agencies and companies that want to understand more about how a website should be reviewed for quality assurance, here’s a feature and benefit rundown of why we love Pastel for HubSpot CMS development feedback and communication for quality assurance testing.

\n","rss_body":"

Our team has been developing websites for many years and HubSpot CMS development quality assurance is one of the most important aspects of the development process. Our project management team and technical director love diving into newly developed modules and projects in an attempt to find bugs that need fixing or responsiveness and browser compatibility issues.

We use a comprehensive checklist for testing all active browsers on most major devices, manually testing responsiveness, reviewing design files in comparison to the “final” product, and testing module functionality for bugs. Through that process we use a few tools to ensure that nothing falls through the cracks. These tools include QA spreadsheets, BrowserStack to test browser compatibility, and perhaps our favorite collaboration and feedback tool, Pastel.

Pastel is a collaboration tool that allows internal teams, contractors, and clients to review marketing projects. We simply plug the project URL into usepastel.com and can quickly begin the review process with live browsing and the ability to easily click to add comments, update text, and collaborate for quick edits and updates. This is critical for us, since most of our team is remote.

For other teams looking for feedback collaboration software, or for agencies and companies that want to understand more about how a website should be reviewed for quality assurance, here’s a feature and benefit rundown of why we love Pastel for HubSpot CMS development feedback and communication for quality assurance testing.

\n\n

It avoids the 75-email edit strings

\n

According to a survey by Zippia.com, 80% of employees feel stressed because of ineffective company communication. Clearly no one likes inefficiency when it comes to communication, internally or externally.

One of the most difficult parts of managing communication surrounding website projects can be the multiple rounds of edits. If your developer or agency doesn’t have a simple way to communicate edits with a platform like Pastel, they can get caught in an endless string of back and forth messages.With no centralized feedback option, clients have to compile Google Docs, Powerpoint presentations, or those long strings of emails or Slack messages, which then need to be searched to find every single edit.

Not only does this increase the amount of time that a developer has to spend on updates, edits,and bug fixes, but sometimes a request can be overlooked, prolonging the process and sometimes even delaying the delivery of a completed site for review.

By having feedback centralized in Pastel, we avoid the extra communication, leaving our inboxes and Slack queue cleaner, our brains a little freer, and our development team that much more efficient. Keep in mind that not every client or employee likes to use new tools, so we still allow other feedback options, we just try to default to this to keep things organized.

\n

 

\n

It allows multiple people to leave feedback in one place.

\n

Of course, it’s easy to assign a single point of contact as a final word on a website, but how often does something get lost in translation? We’ve encountered scenarios when the people at the top are dictating their wants and needs to a marketing director or manager, only for the company’s CEO to step in with their internal team and provide the feedback our teams needed all along. In order to avoid issues with too many cooks in the kitchen while also allowing all eyes in for review, Pastel is a great alternative.

With Pastel, you can hover over sections of the website and pin comments to each section. The comment is sticky and remains in place as you navigate through the rest of the document. This allows you to easily click on comments while reviewing areas of concern to save time in describing issues and identifying the issue in question for the development team receiving the feedback.

You can also @mention any user to quickly ping them with a question, notify them of a new edit, or request an update. You can even hold clients and internal teams accountable by turning off commenting after a “comment deadline.” (This is a favorite feature for us when projects are running on tight timeframes and we need to hold everyone to their deadlines.)

\n

 

\n

You can stay organized and keep up to date on progress.

\n

Keeping comments organized can sometimes be a hassle, and if your development team has a huge list of edits and bug fixes, they may not know exactly how to prioritize them. You can mark items as high priority or categorize your edits using labels. Once a comment is labeled, the team can review it in real time and address high priority items or certain categories of issues, such as bug fixes, before wishlist items or additional feature functionality are addressed.

Pastel also allows for status updates so you can see how edits are progressing in real time. A status can be updated from Active to In Progress to In Review to Resolved by a team member. This keeps a project management team up to date and allows them to communicate timeframes with the client to manage expectations accordingly.

\n

 

\n

It offers “live” editing.

\n

Because Pastel pulls from the website URL, it allows you to use the same canvas for multiple rounds of edits if you want. If you use a live website URL for feedback, once the code is changed, the edits will reflect on the same document, allowing the team to verify those changes and make additional suggestions if needed.

\n

It integrates with other common marketing tools for seamless ticket or task creation.

\n

We’ve spoken to the team at Pastel; they have a lot of great ideas about how they’ll continue to evolve the software. They’ve communicated that their intent is to build on the number of integrations they offer to make it easier for development teams to use Pastel. . They’ve also assured us that big things are on the horizon for the platform.

We asked Valentin Stakov, founder at Pastel, what the company’s focus was and what agencies and developers could expect from Pastel in the coming months. He said, \"We're planning on improving our existing integrations to make them more robust, as well as building additional integrations. We're also focused on building out more tools to make it easier to communicate with your clients and to keep them updated on their projects.\"

For now, their website lists the following integrations here:

Asana
Monday
Trello
Adobe XD
Jira

Finding a tool with a forward-thinking team is important; we look forward to seeing what integrations these guys come up with in the future.

\n

It saves you time with additional functionality.

\n

Pastel has a few time-saving features as well.

Its interface allows you to easily add screenshots, upload files, and link URLs in the comments. If you want an image replaced on a web page, company file storage can sometimes take a bit to sort through.

\n

Basic responsiveness tests are also a perk of Pastel. While we use real browsers when available and BrowserStack for full browser compatibility testing, the simple toggle on Pastel gives the client and other reviewers a way t to visualize what the website will look like on both mobile and desktop, allowing for more eyes on the process.

Another common activity during launch preparation is tweaking copy and headlines. While all our clients operating in HubSpot CMS have the flexibility to make updates to all content and headlines themselves, sometimes you need those perfect words to make a website look launch-ready.

\n

 

\n

","tag_ids":[62234989205,62770442823],"topic_ids":[62234989205,62770442823],"post_summary":"

Our team has been developing websites for many years and HubSpot CMS development quality assurance is one of the most important aspects of the development process. Our project management team and technical director love diving into newly developed modules and projects in an attempt to find bugs that need fixing or responsiveness and browser compatibility issues.

We use a comprehensive checklist for testing all active browsers on most major devices, manually testing responsiveness, reviewing design files in comparison to the “final” product, and testing module functionality for bugs. Through that process we use a few tools to ensure that nothing falls through the cracks. These tools include QA spreadsheets, BrowserStack to test browser compatibility, and perhaps our favorite collaboration and feedback tool, Pastel.

Pastel is a collaboration tool that allows internal teams, contractors, and clients to review marketing projects. We simply plug the project URL into usepastel.com and can quickly begin the review process with live browsing and the ability to easily click to add comments, update text, and collaborate for quick edits and updates. This is critical for us, since most of our team is remote.

For other teams looking for feedback collaboration software, or for agencies and companies that want to understand more about how a website should be reviewed for quality assurance, here’s a feature and benefit rundown of why we love Pastel for HubSpot CMS development feedback and communication for quality assurance testing.

\n","blog_post_schedule_task_uid":null,"blog_publish_to_social_media_task":"DONE_NOT_SENT","blog_publish_instant_email_task_uid":null,"blog_publish_instant_email_campaign_id":null,"blog_publish_instant_email_retry_count":null,"keywords":[],"head_html":null,"footer_html":null,"attached_stylesheets":[],"enable_domain_stylesheets":null,"include_default_custom_css":null,"meta_description":"When it comes to HubSpot CMS Development quality assurance, Pastel is the an amazing tool to make your life easier...","meta_keywords":null,"layout_sections":{},"past_mab_experiment_ids":[],"deleted_by":null,"featured_image_alt_text":"cms development pastel","enable_layout_stylesheets":null,"tweet":null,"tweet_at":null,"campaign_name":null,"campaign_utm":null,"tweet_immediately":false,"publish_immediately":true,"security_state":"NONE","scheduled_update_date":0,"placement_guids":[],"property_for_dynamic_page_title":null,"property_for_dynamic_page_slug":null,"property_for_dynamic_page_meta_description":null,"property_for_dynamic_page_featured_image":null,"property_for_dynamic_page_canonical_url":null,"preview_image_src":null,"legacy_blog_tabid":null,"legacy_post_guid":null,"performable_variation_letter":null,"style_override_id":null,"has_user_changes":true,"css":{},"css_text":"","unpublished_at":0,"published_by_id":61310730,"allowed_slug_conflict":false,"ai_features":null,"link_rel_canonical_url":"","page_redirected":false,"page_expiry_enabled":null,"page_expiry_date":null,"page_expiry_redirect_id":null,"page_expiry_redirect_url":null,"deleted_by_id":null,"state_when_deleted":null,"cloned_from":null,"staged_from":null,"personas":[],"compose_body":null,"featured_image":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/64.png","featured_image_width":2700,"featured_image_height":2700,"publish_timezone_offset":null,"theme_settings_values":null,"password":null,"header":null,"published_at":1719976906253,"last_edit_session_id":null,"last_edit_update_id":null,"created_by_agent":null},"metaDescription":"When it comes to HubSpot CMS Development quality assurance, Pastel is the an amazing tool to make your life easier...","metaKeywords":null,"name":"HubSpot CMS Development Quality Assurance: Why We Love Pastel","nextPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-website%20like%20pokemon.png","nextPostFeaturedImageAltText":"","nextPostName":"Growth-Driven Design: Why Your Website is Kinda Like Pokemon","nextPostSlug":"blogs/growth-driven-design-why-your-website-is-kinda-like-pokemon","pageExpiryDate":null,"pageExpiryEnabled":null,"pageExpiryRedirectId":null,"pageExpiryRedirectUrl":null,"pageRedirected":false,"pageTitle":"HubSpot CMS Development Quality Assurance: Why We Love Pastel","parentBlog":{"absoluteUrl":"https://deckerdevs.com/blogs","allowComments":true,"ampBodyColor":"#404040","ampBodyFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampBodyFontSize":"18","ampCustomCss":"","ampHeaderBackgroundColor":"#ffffff","ampHeaderColor":"#1e1e1e","ampHeaderFont":"'Helvetica Neue', Helvetica, Arial, sans-serif","ampHeaderFontSize":"36","ampLinkColor":"#416bb3","ampLogoAlt":"","ampLogoHeight":0,"ampLogoSrc":"","ampLogoWidth":0,"analyticsPageId":62179259185,"attachedStylesheets":[],"audienceAccess":"PUBLIC","businessUnitId":null,"captchaAfterDays":7,"captchaAlways":false,"categoryId":3,"cdnPurgeEmbargoTime":null,"closeCommentsOlder":0,"commentDateFormat":"medium","commentFormGuid":"cb653aa1-3db4-4167-9b59-744c46d49682","commentMaxThreadDepth":3,"commentModeration":false,"commentNotificationEmails":["nicholas@deckerdevs.com","jessica@deckerdevs.com"],"commentShouldCreateContact":true,"commentVerificationText":"Thanks for participating in this conversation! We look forward to responding and to assisting where we can","cosObjectType":"BLOG","created":1639786189589,"createdDateTime":1639786189589,"dailyNotificationEmailId":null,"dateFormattingLanguage":null,"defaultGroupStyleId":"","defaultNotificationFromName":"","defaultNotificationReplyTo":"","deletedAt":0,"description":"rev up your hubspot system to the max! deckerdevs' turbo-charged blog is your ultimate guide to harnessing the full potential of hubspot development. unleash the marketing magic with ingenious tips, tricks, and hacks. get ready to level up your hubspot game!","domain":"","domainWhenPublished":"deckerdevs.com","emailApiSubscriptionId":null,"enableGoogleAmpOutput":false,"enableSocialAutoPublishing":false,"generateJsonLdEnabled":true,"header":null,"htmlFooter":"","htmlFooterIsShared":true,"htmlHead":"","htmlHeadIsShared":true,"htmlKeywords":[],"htmlTitle":"deckerdevs thought nuggets","id":62179259185,"ilsSubscriptionListsByType":{},"instantNotificationEmailId":null,"itemLayoutId":null,"itemTemplateIsShared":false,"itemTemplatePath":"deckerdevs-theme/templates/blog-content.html","label":"deckerdevs live blog","language":"en","legacyGuid":null,"legacyModuleId":null,"legacyTabId":null,"listingLayoutId":null,"listingPageId":62179259186,"listingTemplatePath":"","liveDomain":"deckerdevs.com","monthFilterFormat":"MMMM yyyy","monthlyNotificationEmailId":null,"name":"deckerdevs live blog","parentBlogUpdateTaskId":null,"portalId":6534445,"postHtmlFooter":"","postHtmlHead":"","postsPerListingPage":9,"postsPerRssFeed":10,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publicTitle":"thought nuggets","publishDateFormat":"medium","resolvedDomain":"deckerdevs.com","rootUrl":"https://deckerdevs.com/blogs","rssCustomFeed":null,"rssDescription":null,"rssItemFooter":null,"rssItemHeader":null,"settingsOverrides":{"itemLayoutId":false,"itemTemplatePath":false,"itemTemplateIsShared":false,"listingLayoutId":false,"listingTemplatePath":false,"postsPerListingPage":false,"showSummaryInListing":false,"useFeaturedImageInSummary":false,"htmlHead":false,"postHtmlHead":false,"htmlHeadIsShared":false,"htmlFooter":false,"listingPageHtmlFooter":false,"postHtmlFooter":false,"htmlFooterIsShared":false,"attachedStylesheets":false,"postsPerRssFeed":false,"showSummaryInRss":false,"showSummaryInEmails":false,"showSummariesInEmails":false,"allowComments":false,"commentShouldCreateContact":false,"commentModeration":false,"closeCommentsOlder":false,"commentNotificationEmails":false,"commentMaxThreadDepth":false,"commentVerificationText":false,"socialAccountTwitter":false,"showSocialLinkTwitter":false,"showSocialLinkLinkedin":false,"showSocialLinkFacebook":false,"enableGoogleAmpOutput":false,"ampLogoSrc":false,"ampLogoHeight":false,"ampLogoWidth":false,"ampLogoAlt":false,"ampHeaderFont":false,"ampHeaderFontSize":false,"ampHeaderColor":false,"ampHeaderBackgroundColor":false,"ampBodyFont":false,"ampBodyFontSize":false,"ampBodyColor":false,"ampLinkColor":false,"generateJsonLdEnabled":false},"showSocialLinkFacebook":true,"showSocialLinkLinkedin":true,"showSocialLinkTwitter":true,"showSummaryInEmails":true,"showSummaryInListing":true,"showSummaryInRss":true,"siteId":null,"slug":"blogs","socialAccountTwitter":"","state":null,"subscriptionContactsProperty":null,"subscriptionEmailType":null,"subscriptionFormGuid":null,"subscriptionListsByType":{},"title":null,"translatedFromId":null,"translations":{},"updated":1712344124471,"updatedDateTime":1712344124471,"urlBase":"deckerdevs.com/blogs","urlSegments":{"all":"all","archive":"archive","author":"author","page":"page","tag":"tag"},"useFeaturedImageInSummary":true,"usesDefaultTemplate":false,"weeklyNotificationEmailId":null},"password":null,"pastMabExperimentIds":[],"performableGuid":null,"performableVariationLetter":null,"personas":[],"placementGuids":[],"portableKey":null,"portalId":6534445,"position":null,"postBody":"

Our team has been developing websites for many years and HubSpot CMS development quality assurance is one of the most important aspects of the development process. Our project management team and technical director love diving into newly developed modules and projects in an attempt to find bugs that need fixing or responsiveness and browser compatibility issues.

We use a comprehensive checklist for testing all active browsers on most major devices, manually testing responsiveness, reviewing design files in comparison to the “final” product, and testing module functionality for bugs. Through that process we use a few tools to ensure that nothing falls through the cracks. These tools include QA spreadsheets, BrowserStack to test browser compatibility, and perhaps our favorite collaboration and feedback tool, Pastel.

Pastel is a collaboration tool that allows internal teams, contractors, and clients to review marketing projects. We simply plug the project URL into usepastel.com and can quickly begin the review process with live browsing and the ability to easily click to add comments, update text, and collaborate for quick edits and updates. This is critical for us, since most of our team is remote.

For other teams looking for feedback collaboration software, or for agencies and companies that want to understand more about how a website should be reviewed for quality assurance, here’s a feature and benefit rundown of why we love Pastel for HubSpot CMS development feedback and communication for quality assurance testing.

\n\n

It avoids the 75-email edit strings

\n

According to a survey by Zippia.com, 80% of employees feel stressed because of ineffective company communication. Clearly no one likes inefficiency when it comes to communication, internally or externally.

One of the most difficult parts of managing communication surrounding website projects can be the multiple rounds of edits. If your developer or agency doesn’t have a simple way to communicate edits with a platform like Pastel, they can get caught in an endless string of back and forth messages.With no centralized feedback option, clients have to compile Google Docs, Powerpoint presentations, or those long strings of emails or Slack messages, which then need to be searched to find every single edit.

Not only does this increase the amount of time that a developer has to spend on updates, edits,and bug fixes, but sometimes a request can be overlooked, prolonging the process and sometimes even delaying the delivery of a completed site for review.

By having feedback centralized in Pastel, we avoid the extra communication, leaving our inboxes and Slack queue cleaner, our brains a little freer, and our development team that much more efficient. Keep in mind that not every client or employee likes to use new tools, so we still allow other feedback options, we just try to default to this to keep things organized.

\n

 

\n

It allows multiple people to leave feedback in one place.

\n

Of course, it’s easy to assign a single point of contact as a final word on a website, but how often does something get lost in translation? We’ve encountered scenarios when the people at the top are dictating their wants and needs to a marketing director or manager, only for the company’s CEO to step in with their internal team and provide the feedback our teams needed all along. In order to avoid issues with too many cooks in the kitchen while also allowing all eyes in for review, Pastel is a great alternative.

With Pastel, you can hover over sections of the website and pin comments to each section. The comment is sticky and remains in place as you navigate through the rest of the document. This allows you to easily click on comments while reviewing areas of concern to save time in describing issues and identifying the issue in question for the development team receiving the feedback.

You can also @mention any user to quickly ping them with a question, notify them of a new edit, or request an update. You can even hold clients and internal teams accountable by turning off commenting after a “comment deadline.” (This is a favorite feature for us when projects are running on tight timeframes and we need to hold everyone to their deadlines.)

\n

 

\n

You can stay organized and keep up to date on progress.

\n

Keeping comments organized can sometimes be a hassle, and if your development team has a huge list of edits and bug fixes, they may not know exactly how to prioritize them. You can mark items as high priority or categorize your edits using labels. Once a comment is labeled, the team can review it in real time and address high priority items or certain categories of issues, such as bug fixes, before wishlist items or additional feature functionality are addressed.

Pastel also allows for status updates so you can see how edits are progressing in real time. A status can be updated from Active to In Progress to In Review to Resolved by a team member. This keeps a project management team up to date and allows them to communicate timeframes with the client to manage expectations accordingly.

\n

 

\n

It offers “live” editing.

\n

Because Pastel pulls from the website URL, it allows you to use the same canvas for multiple rounds of edits if you want. If you use a live website URL for feedback, once the code is changed, the edits will reflect on the same document, allowing the team to verify those changes and make additional suggestions if needed.

\n

It integrates with other common marketing tools for seamless ticket or task creation.

\n

We’ve spoken to the team at Pastel; they have a lot of great ideas about how they’ll continue to evolve the software. They’ve communicated that their intent is to build on the number of integrations they offer to make it easier for development teams to use Pastel. . They’ve also assured us that big things are on the horizon for the platform.

We asked Valentin Stakov, founder at Pastel, what the company’s focus was and what agencies and developers could expect from Pastel in the coming months. He said, \"We're planning on improving our existing integrations to make them more robust, as well as building additional integrations. We're also focused on building out more tools to make it easier to communicate with your clients and to keep them updated on their projects.\"

For now, their website lists the following integrations here:

Asana
Monday
Trello
Adobe XD
Jira

Finding a tool with a forward-thinking team is important; we look forward to seeing what integrations these guys come up with in the future.

\n

It saves you time with additional functionality.

\n

Pastel has a few time-saving features as well.

Its interface allows you to easily add screenshots, upload files, and link URLs in the comments. If you want an image replaced on a web page, company file storage can sometimes take a bit to sort through.

\n

Basic responsiveness tests are also a perk of Pastel. While we use real browsers when available and BrowserStack for full browser compatibility testing, the simple toggle on Pastel gives the client and other reviewers a way t to visualize what the website will look like on both mobile and desktop, allowing for more eyes on the process.

Another common activity during launch preparation is tweaking copy and headlines. While all our clients operating in HubSpot CMS have the flexibility to make updates to all content and headlines themselves, sometimes you need those perfect words to make a website look launch-ready.

\n

 

\n

","postBodyRss":"

Our team has been developing websites for many years and HubSpot CMS development quality assurance is one of the most important aspects of the development process. Our project management team and technical director love diving into newly developed modules and projects in an attempt to find bugs that need fixing or responsiveness and browser compatibility issues.

We use a comprehensive checklist for testing all active browsers on most major devices, manually testing responsiveness, reviewing design files in comparison to the “final” product, and testing module functionality for bugs. Through that process we use a few tools to ensure that nothing falls through the cracks. These tools include QA spreadsheets, BrowserStack to test browser compatibility, and perhaps our favorite collaboration and feedback tool, Pastel.

Pastel is a collaboration tool that allows internal teams, contractors, and clients to review marketing projects. We simply plug the project URL into usepastel.com and can quickly begin the review process with live browsing and the ability to easily click to add comments, update text, and collaborate for quick edits and updates. This is critical for us, since most of our team is remote.

For other teams looking for feedback collaboration software, or for agencies and companies that want to understand more about how a website should be reviewed for quality assurance, here’s a feature and benefit rundown of why we love Pastel for HubSpot CMS development feedback and communication for quality assurance testing.

\n\n

It avoids the 75-email edit strings

\n

According to a survey by Zippia.com, 80% of employees feel stressed because of ineffective company communication. Clearly no one likes inefficiency when it comes to communication, internally or externally.

One of the most difficult parts of managing communication surrounding website projects can be the multiple rounds of edits. If your developer or agency doesn’t have a simple way to communicate edits with a platform like Pastel, they can get caught in an endless string of back and forth messages.With no centralized feedback option, clients have to compile Google Docs, Powerpoint presentations, or those long strings of emails or Slack messages, which then need to be searched to find every single edit.

Not only does this increase the amount of time that a developer has to spend on updates, edits,and bug fixes, but sometimes a request can be overlooked, prolonging the process and sometimes even delaying the delivery of a completed site for review.

By having feedback centralized in Pastel, we avoid the extra communication, leaving our inboxes and Slack queue cleaner, our brains a little freer, and our development team that much more efficient. Keep in mind that not every client or employee likes to use new tools, so we still allow other feedback options, we just try to default to this to keep things organized.

\n

 

\n

It allows multiple people to leave feedback in one place.

\n

Of course, it’s easy to assign a single point of contact as a final word on a website, but how often does something get lost in translation? We’ve encountered scenarios when the people at the top are dictating their wants and needs to a marketing director or manager, only for the company’s CEO to step in with their internal team and provide the feedback our teams needed all along. In order to avoid issues with too many cooks in the kitchen while also allowing all eyes in for review, Pastel is a great alternative.

With Pastel, you can hover over sections of the website and pin comments to each section. The comment is sticky and remains in place as you navigate through the rest of the document. This allows you to easily click on comments while reviewing areas of concern to save time in describing issues and identifying the issue in question for the development team receiving the feedback.

You can also @mention any user to quickly ping them with a question, notify them of a new edit, or request an update. You can even hold clients and internal teams accountable by turning off commenting after a “comment deadline.” (This is a favorite feature for us when projects are running on tight timeframes and we need to hold everyone to their deadlines.)

\n

 

\n

You can stay organized and keep up to date on progress.

\n

Keeping comments organized can sometimes be a hassle, and if your development team has a huge list of edits and bug fixes, they may not know exactly how to prioritize them. You can mark items as high priority or categorize your edits using labels. Once a comment is labeled, the team can review it in real time and address high priority items or certain categories of issues, such as bug fixes, before wishlist items or additional feature functionality are addressed.

Pastel also allows for status updates so you can see how edits are progressing in real time. A status can be updated from Active to In Progress to In Review to Resolved by a team member. This keeps a project management team up to date and allows them to communicate timeframes with the client to manage expectations accordingly.

\n

 

\n

It offers “live” editing.

\n

Because Pastel pulls from the website URL, it allows you to use the same canvas for multiple rounds of edits if you want. If you use a live website URL for feedback, once the code is changed, the edits will reflect on the same document, allowing the team to verify those changes and make additional suggestions if needed.

\n

It integrates with other common marketing tools for seamless ticket or task creation.

\n

We’ve spoken to the team at Pastel; they have a lot of great ideas about how they’ll continue to evolve the software. They’ve communicated that their intent is to build on the number of integrations they offer to make it easier for development teams to use Pastel. . They’ve also assured us that big things are on the horizon for the platform.

We asked Valentin Stakov, founder at Pastel, what the company’s focus was and what agencies and developers could expect from Pastel in the coming months. He said, \"We're planning on improving our existing integrations to make them more robust, as well as building additional integrations. We're also focused on building out more tools to make it easier to communicate with your clients and to keep them updated on their projects.\"

For now, their website lists the following integrations here:

Asana
Monday
Trello
Adobe XD
Jira

Finding a tool with a forward-thinking team is important; we look forward to seeing what integrations these guys come up with in the future.

\n

It saves you time with additional functionality.

\n

Pastel has a few time-saving features as well.

Its interface allows you to easily add screenshots, upload files, and link URLs in the comments. If you want an image replaced on a web page, company file storage can sometimes take a bit to sort through.

\n

Basic responsiveness tests are also a perk of Pastel. While we use real browsers when available and BrowserStack for full browser compatibility testing, the simple toggle on Pastel gives the client and other reviewers a way t to visualize what the website will look like on both mobile and desktop, allowing for more eyes on the process.

Another common activity during launch preparation is tweaking copy and headlines. While all our clients operating in HubSpot CMS have the flexibility to make updates to all content and headlines themselves, sometimes you need those perfect words to make a website look launch-ready.

\n

 

\n

","postEmailContent":"

Our team has been developing websites for many years and HubSpot CMS development quality assurance is one of the most important aspects of the development process. Our project management team and technical director love diving into newly developed modules and projects in an attempt to find bugs that need fixing or responsiveness and browser compatibility issues.

We use a comprehensive checklist for testing all active browsers on most major devices, manually testing responsiveness, reviewing design files in comparison to the “final” product, and testing module functionality for bugs. Through that process we use a few tools to ensure that nothing falls through the cracks. These tools include QA spreadsheets, BrowserStack to test browser compatibility, and perhaps our favorite collaboration and feedback tool, Pastel.

Pastel is a collaboration tool that allows internal teams, contractors, and clients to review marketing projects. We simply plug the project URL into usepastel.com and can quickly begin the review process with live browsing and the ability to easily click to add comments, update text, and collaborate for quick edits and updates. This is critical for us, since most of our team is remote.

For other teams looking for feedback collaboration software, or for agencies and companies that want to understand more about how a website should be reviewed for quality assurance, here’s a feature and benefit rundown of why we love Pastel for HubSpot CMS development feedback and communication for quality assurance testing.

","postFeaturedImageIfEnabled":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/64.png","postListContent":"

Our team has been developing websites for many years and HubSpot CMS development quality assurance is one of the most important aspects of the development process. Our project management team and technical director love diving into newly developed modules and projects in an attempt to find bugs that need fixing or responsiveness and browser compatibility issues.

We use a comprehensive checklist for testing all active browsers on most major devices, manually testing responsiveness, reviewing design files in comparison to the “final” product, and testing module functionality for bugs. Through that process we use a few tools to ensure that nothing falls through the cracks. These tools include QA spreadsheets, BrowserStack to test browser compatibility, and perhaps our favorite collaboration and feedback tool, Pastel.

Pastel is a collaboration tool that allows internal teams, contractors, and clients to review marketing projects. We simply plug the project URL into usepastel.com and can quickly begin the review process with live browsing and the ability to easily click to add comments, update text, and collaborate for quick edits and updates. This is critical for us, since most of our team is remote.

For other teams looking for feedback collaboration software, or for agencies and companies that want to understand more about how a website should be reviewed for quality assurance, here’s a feature and benefit rundown of why we love Pastel for HubSpot CMS development feedback and communication for quality assurance testing.

","postListSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/64.png","postRssContent":"

Our team has been developing websites for many years and HubSpot CMS development quality assurance is one of the most important aspects of the development process. Our project management team and technical director love diving into newly developed modules and projects in an attempt to find bugs that need fixing or responsiveness and browser compatibility issues.

We use a comprehensive checklist for testing all active browsers on most major devices, manually testing responsiveness, reviewing design files in comparison to the “final” product, and testing module functionality for bugs. Through that process we use a few tools to ensure that nothing falls through the cracks. These tools include QA spreadsheets, BrowserStack to test browser compatibility, and perhaps our favorite collaboration and feedback tool, Pastel.

Pastel is a collaboration tool that allows internal teams, contractors, and clients to review marketing projects. We simply plug the project URL into usepastel.com and can quickly begin the review process with live browsing and the ability to easily click to add comments, update text, and collaborate for quick edits and updates. This is critical for us, since most of our team is remote.

For other teams looking for feedback collaboration software, or for agencies and companies that want to understand more about how a website should be reviewed for quality assurance, here’s a feature and benefit rundown of why we love Pastel for HubSpot CMS development feedback and communication for quality assurance testing.

","postRssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/64.png","postSummary":"

Our team has been developing websites for many years and HubSpot CMS development quality assurance is one of the most important aspects of the development process. Our project management team and technical director love diving into newly developed modules and projects in an attempt to find bugs that need fixing or responsiveness and browser compatibility issues.

We use a comprehensive checklist for testing all active browsers on most major devices, manually testing responsiveness, reviewing design files in comparison to the “final” product, and testing module functionality for bugs. Through that process we use a few tools to ensure that nothing falls through the cracks. These tools include QA spreadsheets, BrowserStack to test browser compatibility, and perhaps our favorite collaboration and feedback tool, Pastel.

Pastel is a collaboration tool that allows internal teams, contractors, and clients to review marketing projects. We simply plug the project URL into usepastel.com and can quickly begin the review process with live browsing and the ability to easily click to add comments, update text, and collaborate for quick edits and updates. This is critical for us, since most of our team is remote.

For other teams looking for feedback collaboration software, or for agencies and companies that want to understand more about how a website should be reviewed for quality assurance, here’s a feature and benefit rundown of why we love Pastel for HubSpot CMS development feedback and communication for quality assurance testing.

\n","postSummaryRss":"

Our team has been developing websites for many years and HubSpot CMS development quality assurance is one of the most important aspects of the development process. Our project management team and technical director love diving into newly developed modules and projects in an attempt to find bugs that need fixing or responsiveness and browser compatibility issues.

We use a comprehensive checklist for testing all active browsers on most major devices, manually testing responsiveness, reviewing design files in comparison to the “final” product, and testing module functionality for bugs. Through that process we use a few tools to ensure that nothing falls through the cracks. These tools include QA spreadsheets, BrowserStack to test browser compatibility, and perhaps our favorite collaboration and feedback tool, Pastel.

Pastel is a collaboration tool that allows internal teams, contractors, and clients to review marketing projects. We simply plug the project URL into usepastel.com and can quickly begin the review process with live browsing and the ability to easily click to add comments, update text, and collaborate for quick edits and updates. This is critical for us, since most of our team is remote.

For other teams looking for feedback collaboration software, or for agencies and companies that want to understand more about how a website should be reviewed for quality assurance, here’s a feature and benefit rundown of why we love Pastel for HubSpot CMS development feedback and communication for quality assurance testing.

","postTemplate":"deckerdevs-theme/templates/blog-content.html","previewImageSrc":null,"previewKey":"kIwlUlgr","previousPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-wordpress%20to%20hubspot.png","previousPostFeaturedImageAltText":"","previousPostName":"It's Time to Leave WordPress for HubSpot CMS","previousPostSlug":"blogs/its-time-to-leave-wordpress-for-hubspot-cms","processingStatus":"PUBLISHED","propertyForDynamicPageCanonicalUrl":null,"propertyForDynamicPageFeaturedImage":null,"propertyForDynamicPageMetaDescription":null,"propertyForDynamicPageSlug":null,"propertyForDynamicPageTitle":null,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publishDate":1659716452000,"publishDateLocalTime":1659716452000,"publishDateLocalized":{"date":1659716452000,"format":"medium","language":null},"publishImmediately":true,"publishTimezoneOffset":null,"publishedAt":1719976906253,"publishedByEmail":null,"publishedById":61310730,"publishedByName":null,"publishedUrl":"https://deckerdevs.com/blogs/hubspot-cms-development-quality-assurance-why-we-love-pastel","resolvedDomain":"deckerdevs.com","resolvedLanguage":null,"rssBody":"

Our team has been developing websites for many years and HubSpot CMS development quality assurance is one of the most important aspects of the development process. Our project management team and technical director love diving into newly developed modules and projects in an attempt to find bugs that need fixing or responsiveness and browser compatibility issues.

We use a comprehensive checklist for testing all active browsers on most major devices, manually testing responsiveness, reviewing design files in comparison to the “final” product, and testing module functionality for bugs. Through that process we use a few tools to ensure that nothing falls through the cracks. These tools include QA spreadsheets, BrowserStack to test browser compatibility, and perhaps our favorite collaboration and feedback tool, Pastel.

Pastel is a collaboration tool that allows internal teams, contractors, and clients to review marketing projects. We simply plug the project URL into usepastel.com and can quickly begin the review process with live browsing and the ability to easily click to add comments, update text, and collaborate for quick edits and updates. This is critical for us, since most of our team is remote.

For other teams looking for feedback collaboration software, or for agencies and companies that want to understand more about how a website should be reviewed for quality assurance, here’s a feature and benefit rundown of why we love Pastel for HubSpot CMS development feedback and communication for quality assurance testing.

\n\n

It avoids the 75-email edit strings

\n

According to a survey by Zippia.com, 80% of employees feel stressed because of ineffective company communication. Clearly no one likes inefficiency when it comes to communication, internally or externally.

One of the most difficult parts of managing communication surrounding website projects can be the multiple rounds of edits. If your developer or agency doesn’t have a simple way to communicate edits with a platform like Pastel, they can get caught in an endless string of back and forth messages.With no centralized feedback option, clients have to compile Google Docs, Powerpoint presentations, or those long strings of emails or Slack messages, which then need to be searched to find every single edit.

Not only does this increase the amount of time that a developer has to spend on updates, edits,and bug fixes, but sometimes a request can be overlooked, prolonging the process and sometimes even delaying the delivery of a completed site for review.

By having feedback centralized in Pastel, we avoid the extra communication, leaving our inboxes and Slack queue cleaner, our brains a little freer, and our development team that much more efficient. Keep in mind that not every client or employee likes to use new tools, so we still allow other feedback options, we just try to default to this to keep things organized.

\n

 

\n

It allows multiple people to leave feedback in one place.

\n

Of course, it’s easy to assign a single point of contact as a final word on a website, but how often does something get lost in translation? We’ve encountered scenarios when the people at the top are dictating their wants and needs to a marketing director or manager, only for the company’s CEO to step in with their internal team and provide the feedback our teams needed all along. In order to avoid issues with too many cooks in the kitchen while also allowing all eyes in for review, Pastel is a great alternative.

With Pastel, you can hover over sections of the website and pin comments to each section. The comment is sticky and remains in place as you navigate through the rest of the document. This allows you to easily click on comments while reviewing areas of concern to save time in describing issues and identifying the issue in question for the development team receiving the feedback.

You can also @mention any user to quickly ping them with a question, notify them of a new edit, or request an update. You can even hold clients and internal teams accountable by turning off commenting after a “comment deadline.” (This is a favorite feature for us when projects are running on tight timeframes and we need to hold everyone to their deadlines.)

\n

 

\n

You can stay organized and keep up to date on progress.

\n

Keeping comments organized can sometimes be a hassle, and if your development team has a huge list of edits and bug fixes, they may not know exactly how to prioritize them. You can mark items as high priority or categorize your edits using labels. Once a comment is labeled, the team can review it in real time and address high priority items or certain categories of issues, such as bug fixes, before wishlist items or additional feature functionality are addressed.

Pastel also allows for status updates so you can see how edits are progressing in real time. A status can be updated from Active to In Progress to In Review to Resolved by a team member. This keeps a project management team up to date and allows them to communicate timeframes with the client to manage expectations accordingly.

\n

 

\n

It offers “live” editing.

\n

Because Pastel pulls from the website URL, it allows you to use the same canvas for multiple rounds of edits if you want. If you use a live website URL for feedback, once the code is changed, the edits will reflect on the same document, allowing the team to verify those changes and make additional suggestions if needed.

\n

It integrates with other common marketing tools for seamless ticket or task creation.

\n

We’ve spoken to the team at Pastel; they have a lot of great ideas about how they’ll continue to evolve the software. They’ve communicated that their intent is to build on the number of integrations they offer to make it easier for development teams to use Pastel. . They’ve also assured us that big things are on the horizon for the platform.

We asked Valentin Stakov, founder at Pastel, what the company’s focus was and what agencies and developers could expect from Pastel in the coming months. He said, \"We're planning on improving our existing integrations to make them more robust, as well as building additional integrations. We're also focused on building out more tools to make it easier to communicate with your clients and to keep them updated on their projects.\"

For now, their website lists the following integrations here:

Asana
Monday
Trello
Adobe XD
Jira

Finding a tool with a forward-thinking team is important; we look forward to seeing what integrations these guys come up with in the future.

\n

It saves you time with additional functionality.

\n

Pastel has a few time-saving features as well.

Its interface allows you to easily add screenshots, upload files, and link URLs in the comments. If you want an image replaced on a web page, company file storage can sometimes take a bit to sort through.

\n

Basic responsiveness tests are also a perk of Pastel. While we use real browsers when available and BrowserStack for full browser compatibility testing, the simple toggle on Pastel gives the client and other reviewers a way t to visualize what the website will look like on both mobile and desktop, allowing for more eyes on the process.

Another common activity during launch preparation is tweaking copy and headlines. While all our clients operating in HubSpot CMS have the flexibility to make updates to all content and headlines themselves, sometimes you need those perfect words to make a website look launch-ready.

\n

 

\n

","rssSummary":"

Our team has been developing websites for many years and HubSpot CMS development quality assurance is one of the most important aspects of the development process. Our project management team and technical director love diving into newly developed modules and projects in an attempt to find bugs that need fixing or responsiveness and browser compatibility issues.

We use a comprehensive checklist for testing all active browsers on most major devices, manually testing responsiveness, reviewing design files in comparison to the “final” product, and testing module functionality for bugs. Through that process we use a few tools to ensure that nothing falls through the cracks. These tools include QA spreadsheets, BrowserStack to test browser compatibility, and perhaps our favorite collaboration and feedback tool, Pastel.

Pastel is a collaboration tool that allows internal teams, contractors, and clients to review marketing projects. We simply plug the project URL into usepastel.com and can quickly begin the review process with live browsing and the ability to easily click to add comments, update text, and collaborate for quick edits and updates. This is critical for us, since most of our team is remote.

For other teams looking for feedback collaboration software, or for agencies and companies that want to understand more about how a website should be reviewed for quality assurance, here’s a feature and benefit rundown of why we love Pastel for HubSpot CMS development feedback and communication for quality assurance testing.

\n","rssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/64.png","scheduledUpdateDate":0,"screenshotPreviewTakenAt":1734319306219,"screenshotPreviewUrl":"https://cdn1.hubspot.net/hubshotv3/prod/e/0/35a8ed89-cf6c-46c3-914d-2895f6e697b0.png","sections":{},"securityState":"NONE","siteId":null,"slug":"blogs/hubspot-cms-development-quality-assurance-why-we-love-pastel","stagedFrom":null,"state":"PUBLISHED","stateWhenDeleted":null,"structuredContentPageType":null,"structuredContentType":null,"styleOverrideId":null,"subcategory":"normal_blog_post","syncedWithBlogRoot":true,"tagIds":[62234989205,62770442823],"tagList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1639919937608,"deletedAt":0,"description":"","id":62234989205,"label":"Development","language":"en","name":"Development","portalId":6534445,"slug":"development","translatedFromId":null,"translations":{},"updated":1639919937608},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781}],"tagNames":["Development","HubSpot CMS Development"],"teamPerms":[],"templatePath":"","templatePathForRender":"deckerdevs-theme/templates/blog-content.html","textToAudioFileId":null,"textToAudioGenerationRequestId":null,"themePath":null,"themeSettingsValues":null,"title":"HubSpot CMS Development Quality Assurance: Why We Love Pastel","tmsId":null,"topicIds":[62234989205,62770442823],"topicList":[{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1639919937608,"deletedAt":0,"description":"","id":62234989205,"label":"Development","language":"en","name":"Development","portalId":6534445,"slug":"development","translatedFromId":null,"translations":{},"updated":1639919937608},{"categoryId":3,"cdnPurgeEmbargoTime":null,"contentIds":[],"cosObjectType":"TAG","created":1640714493781,"deletedAt":0,"description":"","id":62770442823,"label":"HubSpot CMS Development","language":"en","name":"HubSpot CMS Development","portalId":6534445,"slug":"hubspot-cms-development","translatedFromId":null,"translations":{},"updated":1640714493781}],"topicNames":["Development","HubSpot CMS Development"],"topics":[62234989205,62770442823],"translatedContent":{},"translatedFromId":null,"translations":{},"tweet":null,"tweetAt":null,"tweetImmediately":false,"unpublishedAt":0,"updated":1719976906257,"updatedById":61310730,"upsizeFeaturedImage":false,"url":"https://deckerdevs.com/blogs/hubspot-cms-development-quality-assurance-why-we-love-pastel","useFeaturedImage":true,"userPerms":[],"views":null,"visibleToAll":null,"widgetContainers":{},"widgetcontainers":{},"widgets":{"blog-image":{"body":{"image_field":{"alt":"pattern-2","height":563,"loading":"lazy","max_height":563,"max_width":1000,"size_type":"auto","src":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/pattern-2.jpg","width":1000}},"child_css":{},"css":{},"deleted_at":1692622562035,"id":"blog-image","label":null,"module_id":62246908725,"name":"blog-image","order":3,"smart_type":null,"styles":{},"type":"module"}}}],"offset":27,"total":44,"totalCount":44}