.svg)
.svg)
.svg)
Some Recent Thoughts...
Juicy Tidbits Without the "Tech Speak"
A compilation of ramblings about everything from HubSpot CMS development to data architecture, integrations and all the tech stuff you never knew you needed to know.
memeify the blog!
Blogs Listing - UPDATE 2024 (Jordan)
HubSpot Layoffs: HubSpot Technical Partners' Critical Role in HubSpot’s Forward Trajectory
It's our time down here. HubSpot Technical Partners will play a critical role in how successfully HubSpot moves forward after their round of layoffs.
HubSpot Partner Tier Discussion
We're going to continue on our path to advocate for Technical Service Partners in the space. We'll continue to grow our platform to be a part of the solution
HubSpot CMS Developer Relationships Like Bert & Ernie
Your relationship with your HubSpot CMS developer should be kinda like Bert and Ernie's friendship...
7 HubSpot CMS Developer Interview Questions to Ask: Part 1
When it comes to HubSpot CMS developer interviews - here are the questions you should be asking:
Website Quality Assurance: You Need QA in HubSpot CMS Development
Website quality assurance matters! Here's why you can't afford NOT to have a QA process in HubSpot CMS Development projects.
HubSpot CMS Developer Utopia: What to Expect When Developing a Website
HubSpot CMS Developer utopia looks a little like less worrying, more clarity, timelines that are honored and really, really quality work...
Growing Pains: 4 Problems with HubSpot Development Agencies That Grow Quickly
We've all experienced growing pains, but when HubSpot development agencies grow too quickly - sometimes clients feel it a little too much...
![\"Milton](\"https://i.imgflip.com/33gh3q.jpg\")
There are many thoughts on everyone’s minds as HubSpot, the marketing and automation leaders behind the term Inbound Marketing, announced its first large layoff in company history. Whether or not you agree with how HubSpot handled the setbacks they have been experiencing - their discussion of revenue shortfalls by CEO Yamini Rangan in HubSpot’s Company News article definitely warrants some discussion on what this means for HubSpot Partners moving forward. It’s possible that having an additional 500 HubSpotters available for hire could lead to closing the talent gap a little more for agencies with the possibilities of HubSpot onboarding specialists and HubSpot technical experts entering the marketplace.
But that’s not what we came here to talk about - the role of HubSpot’s developer community has been a topic of hot conversation for us for the last year, and even more so in the last few weeks - and we’re here to make a lofty claim:
HubSpot technical agencies and freelancers will be the most critical role in HubSpot’s forward trajectory as they refocus their mission.
![\"The](\"https://i.pinimg.com/originals/05/0c/62/050c62da9687c5f4329a204556a03ae8.jpg\")
The reality is that every day HubSpot customers encounter obstacles in their HubSpot portal that they’re not easily able to overcome on their own or even with many of the most popular agencies that HubSpot often recommends.
The day to day issues that companies experience with HubSpot require technical solutions:
According to HubSpot’s CEO, Yamini Rangan:
We have to invest in our future. In order to do that, we need to reduce investments that are not aligned with our strategy. To help our customers grow better during this time, we need to double down on product innovation. For us to scale better, we need to double down on our own internal efficiencies. Both of these require investments that we cannot make if we don't make changes now.
\nWe think all of these things will help HubSpot refocus, but we also think that HubSpot needs to have a better beat on what is happening with the customers they do have that are being cared for by HubSpot agencies. While we’re by no means in the shoes of HubSpot’s CEO, we do have the unique perspective of being inside customer woes when they come to us with their problems with HubSpot. Things we hear?
“I don’t have internal adoption like I want.”
“My sales team doesn’t want to use this because its double entry with the application we use in house”
“My agency is too expensive.”
“We hired the wrong developer and now our website has handicapped us, but we don’t have the budget for a new one.”
“We’re struggling with in-house technical talent and need a partner that actually understands HubSpot.”
“My developer oversold his skills and doesn’t know how to build in HubSpot”
Day to day issues of HubSpot customers are largely technically related, but there is not enough support to fulfill them.
\nWe conducted a survey a few months ago to better understand the talent gap that existed inside HubSpot Partner agencies and more than 60% of respondents confirmed that they struggle to find experienced HubSpot developers to work with.
A great blog from loginradius.com about How Customer Retention Can Help Businesses Grow has the following to say about customer retention rates:
“A good retention rate signifies an increased revenue generation, higher levels of customer satisfaction, and customer loyalty. A study has highlighted that engaged customers are likely to produce 1.7 times more revenue than general customers. Engaged employees and consumers can produce as much as 3.4 times the average revenue. Loyal customers can increase the overall revenue more than one-time customers and acts as a protective factor against the rainy days and the ever-increasing market competition.”
\nWhen it comes to the game of customer retention and HubSpot products, these products have to make sense with business processes and actually make the lives of marketers, service and support EASIER. While we all know the power of HubSpot and the capabilities it brings, oftentimes customers are sold on the product capabilities, but less often paired with a technical partner and truly educated on the investment required to seamlessly integrate these solutions into their organization.
\nWe need to bridge the gap between internal software and HubSpot.
\nWhat’s the point in having a powerful piece of analytics or automation software if it costs you more in double-data entry and employee efficiency than it saves you in monitoring and automating your marketing and service processes? One of the most critical aspects of the true adoption of HubSpot into an organization that has purchased one or more hubs is the absolute seamless success of that first hub.
We executed integrations on behalf of many different clients in 2022, and they all sang the praises of being able to move data around seamlessly. It will be critical to HubSpot’s forward trajectory that they invest heavily into their internal development teams to establish even more business integrations with large, popular applications. However, it’s even more important that HubSpot promote and reward technical partners that are building integrations between lesser known software applications and business. There are incredible developers out there creating connectors in the app marketplace and HubSpot creating an app incubator should be talked about more. HubSpot can't create internal connectors to all of these services, but the stock integrations outside of Salesforce connector and Shopify are just scratching the surface of what can be done.
We can spit out boring statistics and terms like “data redundancy” all we want, but the bottom line is that unless HubSpot sales reps and HubSpot promote the importance and benefit of these integrations, and help support the developers behind the scene building these - they’ll not see the deep rooting of HubSpot into many of their customers organizations - and if a piece of software isn’t deeply rooted into business processes *AND* they’re having trouble with adoption or its causing inefficiency with data redundancy, guess who gets cut first from the team when customer budgets are constrained as they are in an uncertain economic environment?
We need to build websites that can scale and actually empower marketers.
\nLackluster specialized HubSpot developer pools, lack of developer accreditation opportunities, a lack of centralized solutions beyond chat groups, a forum that doesn’t have a centralized knowledge base of solutions for day to day issues, and a lack of true support for technical partners behind the scenes have meant that HubSpot partners, agencies, and end users are finding themselves running into the same issue: we didn’t budget properly.
We hired the wrong person for the job, they used most of the budget - and now we’re stuck with an end product that doesn’t improve our business processes.
This song plays on repeat and every time we hear it, we feel for the client. If there were a centralized, vetted skills ecosystem for specialized partners with incentives to perform, we anticipate a huge influx of skilled developers moving into HubSpot development and even taking it on as a specialty.
For us, it was a no-brainer and we saw quickly that being a skilled provider is not only needed, but pays big time. We have formed so many close agency relationships, and while it may not necessarily benefit from a growth and recurring revenue with HubSpot commissions, we have faith that eventually things may change a little bit and we’ll start to see more support for people behind the curtain in HubSpot.
Building websites that look good on HubSpot CMS is one thing, but building truly versatile and flexible modules that really give marketers the power to do whatever they want? That’s something that HubSpot promotes, but we aren’t always seeing as we work in the back end of the websites that other non-specialized developers have created.
We need to solve complex business process problems with the ability to “add on” features
\nHubSpot is an expensive product, and customers need to see the ROI from certain features that are only available in enterprise level subscriptions. We see a very real need for serverless functions, custom objects and behavioral events for customers that don’t need the full functionality of enterprise level Hub subscriptions.
For example: read more about the need for serverless functions that our development team dealt with:
“Moving from HubSpot CMS Professional to Enterprise is an extra 400 dollars per month. However this is causing us to have to create cloud servers on another product that is actually owned by a competitor to handle it. Serverless functions are a wrapper around AWS serverless. I could easily just use AWS and pay the usage. On top of that HubSpot limits the amount of additional node packages you can load into these, and puts a time limit on the processing. So instead of paying for USAGE like other vendors charge, they charge a flat fee for the service, which handicaps the capabilities, and clients see no benefit in upgrading for 400 dollars when their need is only for serverless functions.”
\nWhile moving ahead to bigger fish is important, we want HubSpot to not forget the roots that built them. The vast majority (99.9% to be exact) of businesses in the United States are small businesses, and there are 33.2 million of them in this country. While making moves for the big ones is a natural progression for HubSpot when multiple hubs help businesses solve for so many things, there may be revenue still to be gained from the smaller accounts by bundling small add-on packages that allow individual product features to be purchased. These things would not only benefit HubSpot, but save developers time in configuration, and make integrations and serverless functions much easier to implement, keeping all business processes in one place.
Overall, we’re doubling down on HubSpot - and we’ll always remain loyal to the brand that built our own foundation. We are very empathetic to the 500 employees and their families that were let go yesterday, and while we may not love that it was done or agree that it should have been done, we want to help HubSpot Partners and HubSpot look to the forward trajectory of how they continue to move the vision of helping businesses scale and measure marketing and close the loop between business processes and customer retention by letting them know how important the technical specialized service provider is to achieving that mission.
In the multiple Hubs that are offered to the customer, don’t forget that Marketing Agencies can’t be everything to everyone. The rise of the specialized technical partner, the specialized Hub consultant, HubSpot systems architect, and other types of partners that support the internal sales team is imminent - it’s just a matter of how HubSpot will support these partners moving forward.
We are a proud HubSpot Technical Partner that is finding the silver lining in a very difficult situation, and we hope that others might start to see what has been clear to us since we’ve signed on as a partner agency.
There are many thoughts on everyone’s minds as HubSpot, the marketing and automation leaders behind the term Inbound Marketing, announced its first large layoff in company history. Whether or not you agree with how HubSpot handled the setbacks they have been experiencing - their discussion of revenue shortfalls by CEO Yamini Rangan in HubSpot’s Company News article definitely warrants some discussion on what this means for HubSpot Partners moving forward. It’s possible that having an additional 500 HubSpotters available for hire could lead to closing the talent gap a little more for agencies with the possibilities of HubSpot onboarding specialists and HubSpot technical experts entering the marketplace.
But that’s not what we came here to talk about - the role of HubSpot’s developer community has been a topic of hot conversation for us for the last year, and even more so in the last few weeks - and we’re here to make a lofty claim:
HubSpot technical agencies and freelancers will be the most critical role in HubSpot’s forward trajectory as they refocus their mission.
The reality is that every day HubSpot customers encounter obstacles in their HubSpot portal that they’re not easily able to overcome on their own or even with many of the most popular agencies that HubSpot often recommends.
The day to day issues that companies experience with HubSpot require technical solutions:
According to HubSpot’s CEO, Yamini Rangan:
There are many thoughts on everyone’s minds as HubSpot, the marketing and automation leaders behind the term Inbound Marketing, announced its first large layoff in company history. Whether or not you agree with how HubSpot handled the setbacks they have been experiencing - their discussion of revenue shortfalls by CEO Yamini Rangan in HubSpot’s Company News article definitely warrants some discussion on what this means for HubSpot Partners moving forward. It’s possible that having an additional 500 HubSpotters available for hire could lead to closing the talent gap a little more for agencies with the possibilities of HubSpot onboarding specialists and HubSpot technical experts entering the marketplace.
But that’s not what we came here to talk about - the role of HubSpot’s developer community has been a topic of hot conversation for us for the last year, and even more so in the last few weeks - and we’re here to make a lofty claim:
HubSpot technical agencies and freelancers will be the most critical role in HubSpot’s forward trajectory as they refocus their mission.
The reality is that every day HubSpot customers encounter obstacles in their HubSpot portal that they’re not easily able to overcome on their own or even with many of the most popular agencies that HubSpot often recommends.
The day to day issues that companies experience with HubSpot require technical solutions:
According to HubSpot’s CEO, Yamini Rangan:
We have to invest in our future. In order to do that, we need to reduce investments that are not aligned with our strategy. To help our customers grow better during this time, we need to double down on product innovation. For us to scale better, we need to double down on our own internal efficiencies. Both of these require investments that we cannot make if we don't make changes now.
\nWe think all of these things will help HubSpot refocus, but we also think that HubSpot needs to have a better beat on what is happening with the customers they do have that are being cared for by HubSpot agencies. While we’re by no means in the shoes of HubSpot’s CEO, we do have the unique perspective of being inside customer woes when they come to us with their problems with HubSpot. Things we hear?
“I don’t have internal adoption like I want.”
“My sales team doesn’t want to use this because its double entry with the application we use in house”
“My agency is too expensive.”
“We hired the wrong developer and now our website has handicapped us, but we don’t have the budget for a new one.”
“We’re struggling with in-house technical talent and need a partner that actually understands HubSpot.”
“My developer oversold his skills and doesn’t know how to build in HubSpot”
Day to day issues of HubSpot customers are largely technically related, but there is not enough support to fulfill them.
\nWe conducted a survey a few months ago to better understand the talent gap that existed inside HubSpot Partner agencies and more than 60% of respondents confirmed that they struggle to find experienced HubSpot developers to work with.
A great blog from loginradius.com about How Customer Retention Can Help Businesses Grow has the following to say about customer retention rates:
“A good retention rate signifies an increased revenue generation, higher levels of customer satisfaction, and customer loyalty. A study has highlighted that engaged customers are likely to produce 1.7 times more revenue than general customers. Engaged employees and consumers can produce as much as 3.4 times the average revenue. Loyal customers can increase the overall revenue more than one-time customers and acts as a protective factor against the rainy days and the ever-increasing market competition.”
\nWhen it comes to the game of customer retention and HubSpot products, these products have to make sense with business processes and actually make the lives of marketers, service and support EASIER. While we all know the power of HubSpot and the capabilities it brings, oftentimes customers are sold on the product capabilities, but less often paired with a technical partner and truly educated on the investment required to seamlessly integrate these solutions into their organization.
\nWe need to bridge the gap between internal software and HubSpot.
\nWhat’s the point in having a powerful piece of analytics or automation software if it costs you more in double-data entry and employee efficiency than it saves you in monitoring and automating your marketing and service processes? One of the most critical aspects of the true adoption of HubSpot into an organization that has purchased one or more hubs is the absolute seamless success of that first hub.
We executed integrations on behalf of many different clients in 2022, and they all sang the praises of being able to move data around seamlessly. It will be critical to HubSpot’s forward trajectory that they invest heavily into their internal development teams to establish even more business integrations with large, popular applications. However, it’s even more important that HubSpot promote and reward technical partners that are building integrations between lesser known software applications and business. There are incredible developers out there creating connectors in the app marketplace and HubSpot creating an app incubator should be talked about more. HubSpot can't create internal connectors to all of these services, but the stock integrations outside of Salesforce connector and Shopify are just scratching the surface of what can be done.
We can spit out boring statistics and terms like “data redundancy” all we want, but the bottom line is that unless HubSpot sales reps and HubSpot promote the importance and benefit of these integrations, and help support the developers behind the scene building these - they’ll not see the deep rooting of HubSpot into many of their customers organizations - and if a piece of software isn’t deeply rooted into business processes *AND* they’re having trouble with adoption or its causing inefficiency with data redundancy, guess who gets cut first from the team when customer budgets are constrained as they are in an uncertain economic environment?
We need to build websites that can scale and actually empower marketers.
\nLackluster specialized HubSpot developer pools, lack of developer accreditation opportunities, a lack of centralized solutions beyond chat groups, a forum that doesn’t have a centralized knowledge base of solutions for day to day issues, and a lack of true support for technical partners behind the scenes have meant that HubSpot partners, agencies, and end users are finding themselves running into the same issue: we didn’t budget properly.
We hired the wrong person for the job, they used most of the budget - and now we’re stuck with an end product that doesn’t improve our business processes.
This song plays on repeat and every time we hear it, we feel for the client. If there were a centralized, vetted skills ecosystem for specialized partners with incentives to perform, we anticipate a huge influx of skilled developers moving into HubSpot development and even taking it on as a specialty.
For us, it was a no-brainer and we saw quickly that being a skilled provider is not only needed, but pays big time. We have formed so many close agency relationships, and while it may not necessarily benefit from a growth and recurring revenue with HubSpot commissions, we have faith that eventually things may change a little bit and we’ll start to see more support for people behind the curtain in HubSpot.
Building websites that look good on HubSpot CMS is one thing, but building truly versatile and flexible modules that really give marketers the power to do whatever they want? That’s something that HubSpot promotes, but we aren’t always seeing as we work in the back end of the websites that other non-specialized developers have created.
We need to solve complex business process problems with the ability to “add on” features
\nHubSpot is an expensive product, and customers need to see the ROI from certain features that are only available in enterprise level subscriptions. We see a very real need for serverless functions, custom objects and behavioral events for customers that don’t need the full functionality of enterprise level Hub subscriptions.
For example: read more about the need for serverless functions that our development team dealt with:
“Moving from HubSpot CMS Professional to Enterprise is an extra 400 dollars per month. However this is causing us to have to create cloud servers on another product that is actually owned by a competitor to handle it. Serverless functions are a wrapper around AWS serverless. I could easily just use AWS and pay the usage. On top of that HubSpot limits the amount of additional node packages you can load into these, and puts a time limit on the processing. So instead of paying for USAGE like other vendors charge, they charge a flat fee for the service, which handicaps the capabilities, and clients see no benefit in upgrading for 400 dollars when their need is only for serverless functions.”
\nWhile moving ahead to bigger fish is important, we want HubSpot to not forget the roots that built them. The vast majority (99.9% to be exact) of businesses in the United States are small businesses, and there are 33.2 million of them in this country. While making moves for the big ones is a natural progression for HubSpot when multiple hubs help businesses solve for so many things, there may be revenue still to be gained from the smaller accounts by bundling small add-on packages that allow individual product features to be purchased. These things would not only benefit HubSpot, but save developers time in configuration, and make integrations and serverless functions much easier to implement, keeping all business processes in one place.
Overall, we’re doubling down on HubSpot - and we’ll always remain loyal to the brand that built our own foundation. We are very empathetic to the 500 employees and their families that were let go yesterday, and while we may not love that it was done or agree that it should have been done, we want to help HubSpot Partners and HubSpot look to the forward trajectory of how they continue to move the vision of helping businesses scale and measure marketing and close the loop between business processes and customer retention by letting them know how important the technical specialized service provider is to achieving that mission.
In the multiple Hubs that are offered to the customer, don’t forget that Marketing Agencies can’t be everything to everyone. The rise of the specialized technical partner, the specialized Hub consultant, HubSpot systems architect, and other types of partners that support the internal sales team is imminent - it’s just a matter of how HubSpot will support these partners moving forward.
We are a proud HubSpot Technical Partner that is finding the silver lining in a very difficult situation, and we hope that others might start to see what has been clear to us since we’ve signed on as a partner agency.
There are many thoughts on everyone’s minds as HubSpot, the marketing and automation leaders behind the term Inbound Marketing, announced its first large layoff in company history. Whether or not you agree with how HubSpot handled the setbacks they have been experiencing - their discussion of revenue shortfalls by CEO Yamini Rangan in HubSpot’s Company News article definitely warrants some discussion on what this means for HubSpot Partners moving forward. It’s possible that having an additional 500 HubSpotters available for hire could lead to closing the talent gap a little more for agencies with the possibilities of HubSpot onboarding specialists and HubSpot technical experts entering the marketplace.
But that’s not what we came here to talk about - the role of HubSpot’s developer community has been a topic of hot conversation for us for the last year, and even more so in the last few weeks - and we’re here to make a lofty claim:
HubSpot technical agencies and freelancers will be the most critical role in HubSpot’s forward trajectory as they refocus their mission.
The reality is that every day HubSpot customers encounter obstacles in their HubSpot portal that they’re not easily able to overcome on their own or even with many of the most popular agencies that HubSpot often recommends.
The day to day issues that companies experience with HubSpot require technical solutions:
According to HubSpot’s CEO, Yamini Rangan:
There are many thoughts on everyone’s minds as HubSpot, the marketing and automation leaders behind the term Inbound Marketing, announced its first large layoff in company history. Whether or not you agree with how HubSpot handled the setbacks they have been experiencing - their discussion of revenue shortfalls by CEO Yamini Rangan in HubSpot’s Company News article definitely warrants some discussion on what this means for HubSpot Partners moving forward. It’s possible that having an additional 500 HubSpotters available for hire could lead to closing the talent gap a little more for agencies with the possibilities of HubSpot onboarding specialists and HubSpot technical experts entering the marketplace.
But that’s not what we came here to talk about - the role of HubSpot’s developer community has been a topic of hot conversation for us for the last year, and even more so in the last few weeks - and we’re here to make a lofty claim:
HubSpot technical agencies and freelancers will be the most critical role in HubSpot’s forward trajectory as they refocus their mission.
The reality is that every day HubSpot customers encounter obstacles in their HubSpot portal that they’re not easily able to overcome on their own or even with many of the most popular agencies that HubSpot often recommends.
The day to day issues that companies experience with HubSpot require technical solutions:
According to HubSpot’s CEO, Yamini Rangan:
We have to invest in our future. In order to do that, we need to reduce investments that are not aligned with our strategy. To help our customers grow better during this time, we need to double down on product innovation. For us to scale better, we need to double down on our own internal efficiencies. Both of these require investments that we cannot make if we don't make changes now.
\nWe think all of these things will help HubSpot refocus, but we also think that HubSpot needs to have a better beat on what is happening with the customers they do have that are being cared for by HubSpot agencies. While we’re by no means in the shoes of HubSpot’s CEO, we do have the unique perspective of being inside customer woes when they come to us with their problems with HubSpot. Things we hear?
“I don’t have internal adoption like I want.”
“My sales team doesn’t want to use this because its double entry with the application we use in house”
“My agency is too expensive.”
“We hired the wrong developer and now our website has handicapped us, but we don’t have the budget for a new one.”
“We’re struggling with in-house technical talent and need a partner that actually understands HubSpot.”
“My developer oversold his skills and doesn’t know how to build in HubSpot”
Day to day issues of HubSpot customers are largely technically related, but there is not enough support to fulfill them.
\nWe conducted a survey a few months ago to better understand the talent gap that existed inside HubSpot Partner agencies and more than 60% of respondents confirmed that they struggle to find experienced HubSpot developers to work with.
A great blog from loginradius.com about How Customer Retention Can Help Businesses Grow has the following to say about customer retention rates:
“A good retention rate signifies an increased revenue generation, higher levels of customer satisfaction, and customer loyalty. A study has highlighted that engaged customers are likely to produce 1.7 times more revenue than general customers. Engaged employees and consumers can produce as much as 3.4 times the average revenue. Loyal customers can increase the overall revenue more than one-time customers and acts as a protective factor against the rainy days and the ever-increasing market competition.”
\nWhen it comes to the game of customer retention and HubSpot products, these products have to make sense with business processes and actually make the lives of marketers, service and support EASIER. While we all know the power of HubSpot and the capabilities it brings, oftentimes customers are sold on the product capabilities, but less often paired with a technical partner and truly educated on the investment required to seamlessly integrate these solutions into their organization.
\nWe need to bridge the gap between internal software and HubSpot.
\nWhat’s the point in having a powerful piece of analytics or automation software if it costs you more in double-data entry and employee efficiency than it saves you in monitoring and automating your marketing and service processes? One of the most critical aspects of the true adoption of HubSpot into an organization that has purchased one or more hubs is the absolute seamless success of that first hub.
We executed integrations on behalf of many different clients in 2022, and they all sang the praises of being able to move data around seamlessly. It will be critical to HubSpot’s forward trajectory that they invest heavily into their internal development teams to establish even more business integrations with large, popular applications. However, it’s even more important that HubSpot promote and reward technical partners that are building integrations between lesser known software applications and business. There are incredible developers out there creating connectors in the app marketplace and HubSpot creating an app incubator should be talked about more. HubSpot can't create internal connectors to all of these services, but the stock integrations outside of Salesforce connector and Shopify are just scratching the surface of what can be done.
We can spit out boring statistics and terms like “data redundancy” all we want, but the bottom line is that unless HubSpot sales reps and HubSpot promote the importance and benefit of these integrations, and help support the developers behind the scene building these - they’ll not see the deep rooting of HubSpot into many of their customers organizations - and if a piece of software isn’t deeply rooted into business processes *AND* they’re having trouble with adoption or its causing inefficiency with data redundancy, guess who gets cut first from the team when customer budgets are constrained as they are in an uncertain economic environment?
We need to build websites that can scale and actually empower marketers.
\nLackluster specialized HubSpot developer pools, lack of developer accreditation opportunities, a lack of centralized solutions beyond chat groups, a forum that doesn’t have a centralized knowledge base of solutions for day to day issues, and a lack of true support for technical partners behind the scenes have meant that HubSpot partners, agencies, and end users are finding themselves running into the same issue: we didn’t budget properly.
We hired the wrong person for the job, they used most of the budget - and now we’re stuck with an end product that doesn’t improve our business processes.
This song plays on repeat and every time we hear it, we feel for the client. If there were a centralized, vetted skills ecosystem for specialized partners with incentives to perform, we anticipate a huge influx of skilled developers moving into HubSpot development and even taking it on as a specialty.
For us, it was a no-brainer and we saw quickly that being a skilled provider is not only needed, but pays big time. We have formed so many close agency relationships, and while it may not necessarily benefit from a growth and recurring revenue with HubSpot commissions, we have faith that eventually things may change a little bit and we’ll start to see more support for people behind the curtain in HubSpot.
Building websites that look good on HubSpot CMS is one thing, but building truly versatile and flexible modules that really give marketers the power to do whatever they want? That’s something that HubSpot promotes, but we aren’t always seeing as we work in the back end of the websites that other non-specialized developers have created.
We need to solve complex business process problems with the ability to “add on” features
\nHubSpot is an expensive product, and customers need to see the ROI from certain features that are only available in enterprise level subscriptions. We see a very real need for serverless functions, custom objects and behavioral events for customers that don’t need the full functionality of enterprise level Hub subscriptions.
For example: read more about the need for serverless functions that our development team dealt with:
“Moving from HubSpot CMS Professional to Enterprise is an extra 400 dollars per month. However this is causing us to have to create cloud servers on another product that is actually owned by a competitor to handle it. Serverless functions are a wrapper around AWS serverless. I could easily just use AWS and pay the usage. On top of that HubSpot limits the amount of additional node packages you can load into these, and puts a time limit on the processing. So instead of paying for USAGE like other vendors charge, they charge a flat fee for the service, which handicaps the capabilities, and clients see no benefit in upgrading for 400 dollars when their need is only for serverless functions.”
\nWhile moving ahead to bigger fish is important, we want HubSpot to not forget the roots that built them. The vast majority (99.9% to be exact) of businesses in the United States are small businesses, and there are 33.2 million of them in this country. While making moves for the big ones is a natural progression for HubSpot when multiple hubs help businesses solve for so many things, there may be revenue still to be gained from the smaller accounts by bundling small add-on packages that allow individual product features to be purchased. These things would not only benefit HubSpot, but save developers time in configuration, and make integrations and serverless functions much easier to implement, keeping all business processes in one place.
Overall, we’re doubling down on HubSpot - and we’ll always remain loyal to the brand that built our own foundation. We are very empathetic to the 500 employees and their families that were let go yesterday, and while we may not love that it was done or agree that it should have been done, we want to help HubSpot Partners and HubSpot look to the forward trajectory of how they continue to move the vision of helping businesses scale and measure marketing and close the loop between business processes and customer retention by letting them know how important the technical specialized service provider is to achieving that mission.
In the multiple Hubs that are offered to the customer, don’t forget that Marketing Agencies can’t be everything to everyone. The rise of the specialized technical partner, the specialized Hub consultant, HubSpot systems architect, and other types of partners that support the internal sales team is imminent - it’s just a matter of how HubSpot will support these partners moving forward.
We are a proud HubSpot Technical Partner that is finding the silver lining in a very difficult situation, and we hope that others might start to see what has been clear to us since we’ve signed on as a partner agency.
There are many thoughts on everyone’s minds as HubSpot, the marketing and automation leaders behind the term Inbound Marketing, announced its first large layoff in company history. Whether or not you agree with how HubSpot handled the setbacks they have been experiencing - their discussion of revenue shortfalls by CEO Yamini Rangan in HubSpot’s Company News article definitely warrants some discussion on what this means for HubSpot Partners moving forward. It’s possible that having an additional 500 HubSpotters available for hire could lead to closing the talent gap a little more for agencies with the possibilities of HubSpot onboarding specialists and HubSpot technical experts entering the marketplace.
But that’s not what we came here to talk about - the role of HubSpot’s developer community has been a topic of hot conversation for us for the last year, and even more so in the last few weeks - and we’re here to make a lofty claim:
HubSpot technical agencies and freelancers will be the most critical role in HubSpot’s forward trajectory as they refocus their mission.
The reality is that every day HubSpot customers encounter obstacles in their HubSpot portal that they’re not easily able to overcome on their own or even with many of the most popular agencies that HubSpot often recommends.
The day to day issues that companies experience with HubSpot require technical solutions:
According to HubSpot’s CEO, Yamini Rangan:
We have to invest in our future. In order to do that, we need to reduce investments that are not aligned with our strategy. To help our customers grow better during this time, we need to double down on product innovation. For us to scale better, we need to double down on our own internal efficiencies. Both of these require investments that we cannot make if we don't make changes now.
\nWe think all of these things will help HubSpot refocus, but we also think that HubSpot needs to have a better beat on what is happening with the customers they do have that are being cared for by HubSpot agencies. While we’re by no means in the shoes of HubSpot’s CEO, we do have the unique perspective of being inside customer woes when they come to us with their problems with HubSpot. Things we hear?
“I don’t have internal adoption like I want.”
“My sales team doesn’t want to use this because its double entry with the application we use in house”
“My agency is too expensive.”
“We hired the wrong developer and now our website has handicapped us, but we don’t have the budget for a new one.”
“We’re struggling with in-house technical talent and need a partner that actually understands HubSpot.”
“My developer oversold his skills and doesn’t know how to build in HubSpot”
Day to day issues of HubSpot customers are largely technically related, but there is not enough support to fulfill them.
\nWe conducted a survey a few months ago to better understand the talent gap that existed inside HubSpot Partner agencies and more than 60% of respondents confirmed that they struggle to find experienced HubSpot developers to work with.
A great blog from loginradius.com about How Customer Retention Can Help Businesses Grow has the following to say about customer retention rates:
“A good retention rate signifies an increased revenue generation, higher levels of customer satisfaction, and customer loyalty. A study has highlighted that engaged customers are likely to produce 1.7 times more revenue than general customers. Engaged employees and consumers can produce as much as 3.4 times the average revenue. Loyal customers can increase the overall revenue more than one-time customers and acts as a protective factor against the rainy days and the ever-increasing market competition.”
\nWhen it comes to the game of customer retention and HubSpot products, these products have to make sense with business processes and actually make the lives of marketers, service and support EASIER. While we all know the power of HubSpot and the capabilities it brings, oftentimes customers are sold on the product capabilities, but less often paired with a technical partner and truly educated on the investment required to seamlessly integrate these solutions into their organization.
\nWe need to bridge the gap between internal software and HubSpot.
\nWhat’s the point in having a powerful piece of analytics or automation software if it costs you more in double-data entry and employee efficiency than it saves you in monitoring and automating your marketing and service processes? One of the most critical aspects of the true adoption of HubSpot into an organization that has purchased one or more hubs is the absolute seamless success of that first hub.
We executed integrations on behalf of many different clients in 2022, and they all sang the praises of being able to move data around seamlessly. It will be critical to HubSpot’s forward trajectory that they invest heavily into their internal development teams to establish even more business integrations with large, popular applications. However, it’s even more important that HubSpot promote and reward technical partners that are building integrations between lesser known software applications and business. There are incredible developers out there creating connectors in the app marketplace and HubSpot creating an app incubator should be talked about more. HubSpot can't create internal connectors to all of these services, but the stock integrations outside of Salesforce connector and Shopify are just scratching the surface of what can be done.
We can spit out boring statistics and terms like “data redundancy” all we want, but the bottom line is that unless HubSpot sales reps and HubSpot promote the importance and benefit of these integrations, and help support the developers behind the scene building these - they’ll not see the deep rooting of HubSpot into many of their customers organizations - and if a piece of software isn’t deeply rooted into business processes *AND* they’re having trouble with adoption or its causing inefficiency with data redundancy, guess who gets cut first from the team when customer budgets are constrained as they are in an uncertain economic environment?
We need to build websites that can scale and actually empower marketers.
\nLackluster specialized HubSpot developer pools, lack of developer accreditation opportunities, a lack of centralized solutions beyond chat groups, a forum that doesn’t have a centralized knowledge base of solutions for day to day issues, and a lack of true support for technical partners behind the scenes have meant that HubSpot partners, agencies, and end users are finding themselves running into the same issue: we didn’t budget properly.
We hired the wrong person for the job, they used most of the budget - and now we’re stuck with an end product that doesn’t improve our business processes.
This song plays on repeat and every time we hear it, we feel for the client. If there were a centralized, vetted skills ecosystem for specialized partners with incentives to perform, we anticipate a huge influx of skilled developers moving into HubSpot development and even taking it on as a specialty.
For us, it was a no-brainer and we saw quickly that being a skilled provider is not only needed, but pays big time. We have formed so many close agency relationships, and while it may not necessarily benefit from a growth and recurring revenue with HubSpot commissions, we have faith that eventually things may change a little bit and we’ll start to see more support for people behind the curtain in HubSpot.
Building websites that look good on HubSpot CMS is one thing, but building truly versatile and flexible modules that really give marketers the power to do whatever they want? That’s something that HubSpot promotes, but we aren’t always seeing as we work in the back end of the websites that other non-specialized developers have created.
We need to solve complex business process problems with the ability to “add on” features
\nHubSpot is an expensive product, and customers need to see the ROI from certain features that are only available in enterprise level subscriptions. We see a very real need for serverless functions, custom objects and behavioral events for customers that don’t need the full functionality of enterprise level Hub subscriptions.
For example: read more about the need for serverless functions that our development team dealt with:
“Moving from HubSpot CMS Professional to Enterprise is an extra 400 dollars per month. However this is causing us to have to create cloud servers on another product that is actually owned by a competitor to handle it. Serverless functions are a wrapper around AWS serverless. I could easily just use AWS and pay the usage. On top of that HubSpot limits the amount of additional node packages you can load into these, and puts a time limit on the processing. So instead of paying for USAGE like other vendors charge, they charge a flat fee for the service, which handicaps the capabilities, and clients see no benefit in upgrading for 400 dollars when their need is only for serverless functions.”
\nWhile moving ahead to bigger fish is important, we want HubSpot to not forget the roots that built them. The vast majority (99.9% to be exact) of businesses in the United States are small businesses, and there are 33.2 million of them in this country. While making moves for the big ones is a natural progression for HubSpot when multiple hubs help businesses solve for so many things, there may be revenue still to be gained from the smaller accounts by bundling small add-on packages that allow individual product features to be purchased. These things would not only benefit HubSpot, but save developers time in configuration, and make integrations and serverless functions much easier to implement, keeping all business processes in one place.
Overall, we’re doubling down on HubSpot - and we’ll always remain loyal to the brand that built our own foundation. We are very empathetic to the 500 employees and their families that were let go yesterday, and while we may not love that it was done or agree that it should have been done, we want to help HubSpot Partners and HubSpot look to the forward trajectory of how they continue to move the vision of helping businesses scale and measure marketing and close the loop between business processes and customer retention by letting them know how important the technical specialized service provider is to achieving that mission.
In the multiple Hubs that are offered to the customer, don’t forget that Marketing Agencies can’t be everything to everyone. The rise of the specialized technical partner, the specialized Hub consultant, HubSpot systems architect, and other types of partners that support the internal sales team is imminent - it’s just a matter of how HubSpot will support these partners moving forward.
We are a proud HubSpot Technical Partner that is finding the silver lining in a very difficult situation, and we hope that others might start to see what has been clear to us since we’ve signed on as a partner agency.
There are many thoughts on everyone’s minds as HubSpot, the marketing and automation leaders behind the term Inbound Marketing, announced its first large layoff in company history. Whether or not you agree with how HubSpot handled the setbacks they have been experiencing - their discussion of revenue shortfalls by CEO Yamini Rangan in HubSpot’s Company News article definitely warrants some discussion on what this means for HubSpot Partners moving forward. It’s possible that having an additional 500 HubSpotters available for hire could lead to closing the talent gap a little more for agencies with the possibilities of HubSpot onboarding specialists and HubSpot technical experts entering the marketplace.
But that’s not what we came here to talk about - the role of HubSpot’s developer community has been a topic of hot conversation for us for the last year, and even more so in the last few weeks - and we’re here to make a lofty claim:
HubSpot technical agencies and freelancers will be the most critical role in HubSpot’s forward trajectory as they refocus their mission.
The reality is that every day HubSpot customers encounter obstacles in their HubSpot portal that they’re not easily able to overcome on their own or even with many of the most popular agencies that HubSpot often recommends.
The day to day issues that companies experience with HubSpot require technical solutions:
According to HubSpot’s CEO, Yamini Rangan:
There are many thoughts on everyone’s minds as HubSpot, the marketing and automation leaders behind the term Inbound Marketing, announced its first large layoff in company history. Whether or not you agree with how HubSpot handled the setbacks they have been experiencing - their discussion of revenue shortfalls by CEO Yamini Rangan in HubSpot’s Company News article definitely warrants some discussion on what this means for HubSpot Partners moving forward. It’s possible that having an additional 500 HubSpotters available for hire could lead to closing the talent gap a little more for agencies with the possibilities of HubSpot onboarding specialists and HubSpot technical experts entering the marketplace.
But that’s not what we came here to talk about - the role of HubSpot’s developer community has been a topic of hot conversation for us for the last year, and even more so in the last few weeks - and we’re here to make a lofty claim:
HubSpot technical agencies and freelancers will be the most critical role in HubSpot’s forward trajectory as they refocus their mission.
The reality is that every day HubSpot customers encounter obstacles in their HubSpot portal that they’re not easily able to overcome on their own or even with many of the most popular agencies that HubSpot often recommends.
The day to day issues that companies experience with HubSpot require technical solutions:
According to HubSpot’s CEO, Yamini Rangan:
There are many thoughts on everyone’s minds as HubSpot, the marketing and automation leaders behind the term Inbound Marketing, announced its first large layoff in company history. Whether or not you agree with how HubSpot handled the setbacks they have been experiencing - their discussion of revenue shortfalls by CEO Yamini Rangan in HubSpot’s Company News article definitely warrants some discussion on what this means for HubSpot Partners moving forward. It’s possible that having an additional 500 HubSpotters available for hire could lead to closing the talent gap a little more for agencies with the possibilities of HubSpot onboarding specialists and HubSpot technical experts entering the marketplace.
But that’s not what we came here to talk about - the role of HubSpot’s developer community has been a topic of hot conversation for us for the last year, and even more so in the last few weeks - and we’re here to make a lofty claim:
HubSpot technical agencies and freelancers will be the most critical role in HubSpot’s forward trajectory as they refocus their mission.
The reality is that every day HubSpot customers encounter obstacles in their HubSpot portal that they’re not easily able to overcome on their own or even with many of the most popular agencies that HubSpot often recommends.
The day to day issues that companies experience with HubSpot require technical solutions:
According to HubSpot’s CEO, Yamini Rangan:
There are many thoughts on everyone’s minds as HubSpot, the marketing and automation leaders behind the term Inbound Marketing, announced its first large layoff in company history. Whether or not you agree with how HubSpot handled the setbacks they have been experiencing - their discussion of revenue shortfalls by CEO Yamini Rangan in HubSpot’s Company News article definitely warrants some discussion on what this means for HubSpot Partners moving forward. It’s possible that having an additional 500 HubSpotters available for hire could lead to closing the talent gap a little more for agencies with the possibilities of HubSpot onboarding specialists and HubSpot technical experts entering the marketplace.
But that’s not what we came here to talk about - the role of HubSpot’s developer community has been a topic of hot conversation for us for the last year, and even more so in the last few weeks - and we’re here to make a lofty claim:
HubSpot technical agencies and freelancers will be the most critical role in HubSpot’s forward trajectory as they refocus their mission.
The reality is that every day HubSpot customers encounter obstacles in their HubSpot portal that they’re not easily able to overcome on their own or even with many of the most popular agencies that HubSpot often recommends.
The day to day issues that companies experience with HubSpot require technical solutions:
According to HubSpot’s CEO, Yamini Rangan:
There are many thoughts on everyone’s minds as HubSpot, the marketing and automation leaders behind the term Inbound Marketing, announced its first large layoff in company history. Whether or not you agree with how HubSpot handled the setbacks they have been experiencing - their discussion of revenue shortfalls by CEO Yamini Rangan in HubSpot’s Company News article definitely warrants some discussion on what this means for HubSpot Partners moving forward. It’s possible that having an additional 500 HubSpotters available for hire could lead to closing the talent gap a little more for agencies with the possibilities of HubSpot onboarding specialists and HubSpot technical experts entering the marketplace.
But that’s not what we came here to talk about - the role of HubSpot’s developer community has been a topic of hot conversation for us for the last year, and even more so in the last few weeks - and we’re here to make a lofty claim:
HubSpot technical agencies and freelancers will be the most critical role in HubSpot’s forward trajectory as they refocus their mission.
The reality is that every day HubSpot customers encounter obstacles in their HubSpot portal that they’re not easily able to overcome on their own or even with many of the most popular agencies that HubSpot often recommends.
The day to day issues that companies experience with HubSpot require technical solutions:
According to HubSpot’s CEO, Yamini Rangan:
There are many thoughts on everyone’s minds as HubSpot, the marketing and automation leaders behind the term Inbound Marketing, announced its first large layoff in company history. Whether or not you agree with how HubSpot handled the setbacks they have been experiencing - their discussion of revenue shortfalls by CEO Yamini Rangan in HubSpot’s Company News article definitely warrants some discussion on what this means for HubSpot Partners moving forward. It’s possible that having an additional 500 HubSpotters available for hire could lead to closing the talent gap a little more for agencies with the possibilities of HubSpot onboarding specialists and HubSpot technical experts entering the marketplace.
But that’s not what we came here to talk about - the role of HubSpot’s developer community has been a topic of hot conversation for us for the last year, and even more so in the last few weeks - and we’re here to make a lofty claim:
HubSpot technical agencies and freelancers will be the most critical role in HubSpot’s forward trajectory as they refocus their mission.
The reality is that every day HubSpot customers encounter obstacles in their HubSpot portal that they’re not easily able to overcome on their own or even with many of the most popular agencies that HubSpot often recommends.
The day to day issues that companies experience with HubSpot require technical solutions:
According to HubSpot’s CEO, Yamini Rangan:
We have to invest in our future. In order to do that, we need to reduce investments that are not aligned with our strategy. To help our customers grow better during this time, we need to double down on product innovation. For us to scale better, we need to double down on our own internal efficiencies. Both of these require investments that we cannot make if we don't make changes now.
\nWe think all of these things will help HubSpot refocus, but we also think that HubSpot needs to have a better beat on what is happening with the customers they do have that are being cared for by HubSpot agencies. While we’re by no means in the shoes of HubSpot’s CEO, we do have the unique perspective of being inside customer woes when they come to us with their problems with HubSpot. Things we hear?
“I don’t have internal adoption like I want.”
“My sales team doesn’t want to use this because its double entry with the application we use in house”
“My agency is too expensive.”
“We hired the wrong developer and now our website has handicapped us, but we don’t have the budget for a new one.”
“We’re struggling with in-house technical talent and need a partner that actually understands HubSpot.”
“My developer oversold his skills and doesn’t know how to build in HubSpot”
Day to day issues of HubSpot customers are largely technically related, but there is not enough support to fulfill them.
\nWe conducted a survey a few months ago to better understand the talent gap that existed inside HubSpot Partner agencies and more than 60% of respondents confirmed that they struggle to find experienced HubSpot developers to work with.
A great blog from loginradius.com about How Customer Retention Can Help Businesses Grow has the following to say about customer retention rates:
“A good retention rate signifies an increased revenue generation, higher levels of customer satisfaction, and customer loyalty. A study has highlighted that engaged customers are likely to produce 1.7 times more revenue than general customers. Engaged employees and consumers can produce as much as 3.4 times the average revenue. Loyal customers can increase the overall revenue more than one-time customers and acts as a protective factor against the rainy days and the ever-increasing market competition.”
\nWhen it comes to the game of customer retention and HubSpot products, these products have to make sense with business processes and actually make the lives of marketers, service and support EASIER. While we all know the power of HubSpot and the capabilities it brings, oftentimes customers are sold on the product capabilities, but less often paired with a technical partner and truly educated on the investment required to seamlessly integrate these solutions into their organization.
\nWe need to bridge the gap between internal software and HubSpot.
\nWhat’s the point in having a powerful piece of analytics or automation software if it costs you more in double-data entry and employee efficiency than it saves you in monitoring and automating your marketing and service processes? One of the most critical aspects of the true adoption of HubSpot into an organization that has purchased one or more hubs is the absolute seamless success of that first hub.
We executed integrations on behalf of many different clients in 2022, and they all sang the praises of being able to move data around seamlessly. It will be critical to HubSpot’s forward trajectory that they invest heavily into their internal development teams to establish even more business integrations with large, popular applications. However, it’s even more important that HubSpot promote and reward technical partners that are building integrations between lesser known software applications and business. There are incredible developers out there creating connectors in the app marketplace and HubSpot creating an app incubator should be talked about more. HubSpot can't create internal connectors to all of these services, but the stock integrations outside of Salesforce connector and Shopify are just scratching the surface of what can be done.
We can spit out boring statistics and terms like “data redundancy” all we want, but the bottom line is that unless HubSpot sales reps and HubSpot promote the importance and benefit of these integrations, and help support the developers behind the scene building these - they’ll not see the deep rooting of HubSpot into many of their customers organizations - and if a piece of software isn’t deeply rooted into business processes *AND* they’re having trouble with adoption or its causing inefficiency with data redundancy, guess who gets cut first from the team when customer budgets are constrained as they are in an uncertain economic environment?
We need to build websites that can scale and actually empower marketers.
\nLackluster specialized HubSpot developer pools, lack of developer accreditation opportunities, a lack of centralized solutions beyond chat groups, a forum that doesn’t have a centralized knowledge base of solutions for day to day issues, and a lack of true support for technical partners behind the scenes have meant that HubSpot partners, agencies, and end users are finding themselves running into the same issue: we didn’t budget properly.
We hired the wrong person for the job, they used most of the budget - and now we’re stuck with an end product that doesn’t improve our business processes.
This song plays on repeat and every time we hear it, we feel for the client. If there were a centralized, vetted skills ecosystem for specialized partners with incentives to perform, we anticipate a huge influx of skilled developers moving into HubSpot development and even taking it on as a specialty.
For us, it was a no-brainer and we saw quickly that being a skilled provider is not only needed, but pays big time. We have formed so many close agency relationships, and while it may not necessarily benefit from a growth and recurring revenue with HubSpot commissions, we have faith that eventually things may change a little bit and we’ll start to see more support for people behind the curtain in HubSpot.
Building websites that look good on HubSpot CMS is one thing, but building truly versatile and flexible modules that really give marketers the power to do whatever they want? That’s something that HubSpot promotes, but we aren’t always seeing as we work in the back end of the websites that other non-specialized developers have created.
We need to solve complex business process problems with the ability to “add on” features
\nHubSpot is an expensive product, and customers need to see the ROI from certain features that are only available in enterprise level subscriptions. We see a very real need for serverless functions, custom objects and behavioral events for customers that don’t need the full functionality of enterprise level Hub subscriptions.
For example: read more about the need for serverless functions that our development team dealt with:
“Moving from HubSpot CMS Professional to Enterprise is an extra 400 dollars per month. However this is causing us to have to create cloud servers on another product that is actually owned by a competitor to handle it. Serverless functions are a wrapper around AWS serverless. I could easily just use AWS and pay the usage. On top of that HubSpot limits the amount of additional node packages you can load into these, and puts a time limit on the processing. So instead of paying for USAGE like other vendors charge, they charge a flat fee for the service, which handicaps the capabilities, and clients see no benefit in upgrading for 400 dollars when their need is only for serverless functions.”
\nWhile moving ahead to bigger fish is important, we want HubSpot to not forget the roots that built them. The vast majority (99.9% to be exact) of businesses in the United States are small businesses, and there are 33.2 million of them in this country. While making moves for the big ones is a natural progression for HubSpot when multiple hubs help businesses solve for so many things, there may be revenue still to be gained from the smaller accounts by bundling small add-on packages that allow individual product features to be purchased. These things would not only benefit HubSpot, but save developers time in configuration, and make integrations and serverless functions much easier to implement, keeping all business processes in one place.
Overall, we’re doubling down on HubSpot - and we’ll always remain loyal to the brand that built our own foundation. We are very empathetic to the 500 employees and their families that were let go yesterday, and while we may not love that it was done or agree that it should have been done, we want to help HubSpot Partners and HubSpot look to the forward trajectory of how they continue to move the vision of helping businesses scale and measure marketing and close the loop between business processes and customer retention by letting them know how important the technical specialized service provider is to achieving that mission.
In the multiple Hubs that are offered to the customer, don’t forget that Marketing Agencies can’t be everything to everyone. The rise of the specialized technical partner, the specialized Hub consultant, HubSpot systems architect, and other types of partners that support the internal sales team is imminent - it’s just a matter of how HubSpot will support these partners moving forward.
We are a proud HubSpot Technical Partner that is finding the silver lining in a very difficult situation, and we hope that others might start to see what has been clear to us since we’ve signed on as a partner agency.
There are many thoughts on everyone’s minds as HubSpot, the marketing and automation leaders behind the term Inbound Marketing, announced its first large layoff in company history. Whether or not you agree with how HubSpot handled the setbacks they have been experiencing - their discussion of revenue shortfalls by CEO Yamini Rangan in HubSpot’s Company News article definitely warrants some discussion on what this means for HubSpot Partners moving forward. It’s possible that having an additional 500 HubSpotters available for hire could lead to closing the talent gap a little more for agencies with the possibilities of HubSpot onboarding specialists and HubSpot technical experts entering the marketplace.
But that’s not what we came here to talk about - the role of HubSpot’s developer community has been a topic of hot conversation for us for the last year, and even more so in the last few weeks - and we’re here to make a lofty claim:
HubSpot technical agencies and freelancers will be the most critical role in HubSpot’s forward trajectory as they refocus their mission.
The reality is that every day HubSpot customers encounter obstacles in their HubSpot portal that they’re not easily able to overcome on their own or even with many of the most popular agencies that HubSpot often recommends.
The day to day issues that companies experience with HubSpot require technical solutions:
According to HubSpot’s CEO, Yamini Rangan:
![\"13.0_curved\"](\"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/devHub/13.0_curved.svg\")
You might be arriving here because there was a discussion around HubSpot Tiers.
The original reception of this created a conversation, and we are happy to have had it. I don't want to remove this post and have it disappear into the ether, but I also don't want the post to impact our relationships with other successful tiered partners of HubSpot or how partners in the ecosystem view deckerdevs.
\nI appreciate you if you were involved in our conversation and provided feedback. It was great to see all perspectives.
\nAt this point we are going to continue to do great work as a technical partner and hope that we can continue to advocate for technical partners in the ecosystem.
\nI hope you check back in with us in the coming months to see for yourself that we are following through on this.
\n\n","rss_summary":"
You might be arriving here because there was a discussion around HubSpot Tiers.
The original reception of this created a conversation, and we are happy to have had it. I don't want to remove this post and have it disappear into the ether, but I also don't want the post to impact our relationships with other successful tiered partners of HubSpot or how partners in the ecosystem view deckerdevs.
\nI appreciate you if you were involved in our conversation and provided feedback. It was great to see all perspectives.
\nAt this point we are going to continue to do great work as a technical partner and hope that we can continue to advocate for technical partners in the ecosystem.
\nI hope you check back in with us in the coming months to see for yourself that we are following through on this.
\n","rss_body":"You might be arriving here because there was a discussion around HubSpot Tiers.
The original reception of this created a conversation, and we are happy to have had it. I don't want to remove this post and have it disappear into the ether, but I also don't want the post to impact our relationships with other successful tiered partners of HubSpot or how partners in the ecosystem view deckerdevs.
\nI appreciate you if you were involved in our conversation and provided feedback. It was great to see all perspectives.
\nAt this point we are going to continue to do great work as a technical partner and hope that we can continue to advocate for technical partners in the ecosystem.
\nI hope you check back in with us in the coming months to see for yourself that we are following through on this.
\n\n","tag_ids":[78562833827,80453663900,90840659382],"topic_ids":[78562833827,80453663900,90840659382],"post_summary":"
You might be arriving here because there was a discussion around HubSpot Tiers.
The original reception of this created a conversation, and we are happy to have had it. I don't want to remove this post and have it disappear into the ether, but I also don't want the post to impact our relationships with other successful tiered partners of HubSpot or how partners in the ecosystem view deckerdevs.
\nI appreciate you if you were involved in our conversation and provided feedback. It was great to see all perspectives.
\nAt this point we are going to continue to do great work as a technical partner and hope that we can continue to advocate for technical partners in the ecosystem.
\nI hope you check back in with us in the coming months to see for yourself that we are following through on this.
\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":"","footer_html":null,"attached_stylesheets":[],"enable_domain_stylesheets":null,"include_default_custom_css":null,"meta_description":"We're going to continue on our path to advocate for Technical Service Partners in the space. We'll continue to grow our platform to be a part of the solution","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":8506132,"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/devHub/13.0_curved.svg","featured_image_width":858,"featured_image_height":858,"publish_timezone_offset":null,"theme_settings_values":null,"password":null,"header":null,"published_at":1674819144037,"last_edit_session_id":null,"last_edit_update_id":null,"created_by_agent":null},"metaDescription":"We're going to continue on our path to advocate for Technical Service Partners in the space. We'll continue to grow our platform to be a part of the solution","metaKeywords":null,"name":"HubSpot Partner Tier Discussion","nextPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-bert%20and%20ernie.png","nextPostFeaturedImageAltText":"","nextPostName":"HubSpot CMS Developer Relationships Like Bert & Ernie","nextPostSlug":"blogs/hubspot-cms-developer-relationships-like-bert-ernie","pageExpiryDate":null,"pageExpiryEnabled":null,"pageExpiryRedirectId":null,"pageExpiryRedirectUrl":null,"pageRedirected":false,"pageTitle":"HubSpot Partner Tier Discussion","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":"You might be arriving here because there was a discussion around HubSpot Tiers.
The original reception of this created a conversation, and we are happy to have had it. I don't want to remove this post and have it disappear into the ether, but I also don't want the post to impact our relationships with other successful tiered partners of HubSpot or how partners in the ecosystem view deckerdevs.
\nI appreciate you if you were involved in our conversation and provided feedback. It was great to see all perspectives.
\nAt this point we are going to continue to do great work as a technical partner and hope that we can continue to advocate for technical partners in the ecosystem.
\nI hope you check back in with us in the coming months to see for yourself that we are following through on this.
\n\n","postBodyRss":"
You might be arriving here because there was a discussion around HubSpot Tiers.
The original reception of this created a conversation, and we are happy to have had it. I don't want to remove this post and have it disappear into the ether, but I also don't want the post to impact our relationships with other successful tiered partners of HubSpot or how partners in the ecosystem view deckerdevs.
\nI appreciate you if you were involved in our conversation and provided feedback. It was great to see all perspectives.
\nAt this point we are going to continue to do great work as a technical partner and hope that we can continue to advocate for technical partners in the ecosystem.
\nI hope you check back in with us in the coming months to see for yourself that we are following through on this.
\n\n","postEmailContent":"
You might be arriving here because there was a discussion around HubSpot Tiers.
\nThe original reception of this created a conversation, and we are happy to have had it. I don't want to remove this post and have it disappear into the ether, but I also don't want the post to impact our relationships with other successful tiered partners of HubSpot or how partners in the ecosystem view deckerdevs.
\nI appreciate you if you were involved in our conversation and provided feedback. It was great to see all perspectives.
\nAt this point we are going to continue to do great work as a technical partner and hope that we can continue to advocate for technical partners in the ecosystem.
\nI hope you check back in with us in the coming months to see for yourself that we are following through on this.
","postFeaturedImageIfEnabled":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/devHub/13.0_curved.svg","postListContent":"You might be arriving here because there was a discussion around HubSpot Tiers.
\nThe original reception of this created a conversation, and we are happy to have had it. I don't want to remove this post and have it disappear into the ether, but I also don't want the post to impact our relationships with other successful tiered partners of HubSpot or how partners in the ecosystem view deckerdevs.
\nI appreciate you if you were involved in our conversation and provided feedback. It was great to see all perspectives.
\nAt this point we are going to continue to do great work as a technical partner and hope that we can continue to advocate for technical partners in the ecosystem.
\nI hope you check back in with us in the coming months to see for yourself that we are following through on this.
","postListSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/devHub/13.0_curved.svg","postRssContent":"You might be arriving here because there was a discussion around HubSpot Tiers.
\nThe original reception of this created a conversation, and we are happy to have had it. I don't want to remove this post and have it disappear into the ether, but I also don't want the post to impact our relationships with other successful tiered partners of HubSpot or how partners in the ecosystem view deckerdevs.
\nI appreciate you if you were involved in our conversation and provided feedback. It was great to see all perspectives.
\nAt this point we are going to continue to do great work as a technical partner and hope that we can continue to advocate for technical partners in the ecosystem.
\nI hope you check back in with us in the coming months to see for yourself that we are following through on this.
","postRssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/devHub/13.0_curved.svg","postSummary":"You might be arriving here because there was a discussion around HubSpot Tiers.
The original reception of this created a conversation, and we are happy to have had it. I don't want to remove this post and have it disappear into the ether, but I also don't want the post to impact our relationships with other successful tiered partners of HubSpot or how partners in the ecosystem view deckerdevs.
\nI appreciate you if you were involved in our conversation and provided feedback. It was great to see all perspectives.
\nAt this point we are going to continue to do great work as a technical partner and hope that we can continue to advocate for technical partners in the ecosystem.
\nI hope you check back in with us in the coming months to see for yourself that we are following through on this.
\n","postSummaryRss":"You might be arriving here because there was a discussion around HubSpot Tiers.
\nThe original reception of this created a conversation, and we are happy to have had it. I don't want to remove this post and have it disappear into the ether, but I also don't want the post to impact our relationships with other successful tiered partners of HubSpot or how partners in the ecosystem view deckerdevs.
\nI appreciate you if you were involved in our conversation and provided feedback. It was great to see all perspectives.
\nAt this point we are going to continue to do great work as a technical partner and hope that we can continue to advocate for technical partners in the ecosystem.
\nI hope you check back in with us in the coming months to see for yourself that we are following through on this.
","postTemplate":"deckerdevs-theme/templates/blog-content.html","previewImageSrc":null,"previewKey":"UxreoPbV","previousPostFeaturedImage":"https://i.pinimg.com/originals/05/0c/62/050c62da9687c5f4329a204556a03ae8.jpg","previousPostFeaturedImageAltText":"","previousPostName":"HubSpot Layoffs: HubSpot Technical Partners' Critical Role in HubSpot’s Forward Trajectory ","previousPostSlug":"blogs/hubspot-layoffs-the-hubspot-technical-partners-critical-role-in-hubspots-forward-trajectory","processingStatus":"PUBLISHED","propertyForDynamicPageCanonicalUrl":null,"propertyForDynamicPageFeaturedImage":null,"propertyForDynamicPageMetaDescription":null,"propertyForDynamicPageSlug":null,"propertyForDynamicPageTitle":null,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publishDate":1674080774000,"publishDateLocalTime":1674080774000,"publishDateLocalized":{"date":1674080774000,"format":"medium","language":null},"publishImmediately":true,"publishTimezoneOffset":null,"publishedAt":1674819144037,"publishedByEmail":null,"publishedById":8506132,"publishedByName":null,"publishedUrl":"https://deckerdevs.com/blogs/why-hubspot-partner-tiers-dont-matter-as-much-as-you-think-they-do","resolvedDomain":"deckerdevs.com","resolvedLanguage":null,"rssBody":"You might be arriving here because there was a discussion around HubSpot Tiers.
The original reception of this created a conversation, and we are happy to have had it. I don't want to remove this post and have it disappear into the ether, but I also don't want the post to impact our relationships with other successful tiered partners of HubSpot or how partners in the ecosystem view deckerdevs.
\nI appreciate you if you were involved in our conversation and provided feedback. It was great to see all perspectives.
\nAt this point we are going to continue to do great work as a technical partner and hope that we can continue to advocate for technical partners in the ecosystem.
\nI hope you check back in with us in the coming months to see for yourself that we are following through on this.
\n\n","rssSummary":"
You might be arriving here because there was a discussion around HubSpot Tiers.
The original reception of this created a conversation, and we are happy to have had it. I don't want to remove this post and have it disappear into the ether, but I also don't want the post to impact our relationships with other successful tiered partners of HubSpot or how partners in the ecosystem view deckerdevs.
\nI appreciate you if you were involved in our conversation and provided feedback. It was great to see all perspectives.
\nAt this point we are going to continue to do great work as a technical partner and hope that we can continue to advocate for technical partners in the ecosystem.
\nI hope you check back in with us in the coming months to see for yourself that we are following through on this.
\n","rssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/devHub/13.0_curved.svg","scheduledUpdateDate":0,"screenshotPreviewTakenAt":1739359973274,"screenshotPreviewUrl":"https://cdn1.hubspot.net/hubshotv3/prod/e/0/5ade5236-879c-4e6d-a25a-d411a410c795.png","sections":{},"securityState":"NONE","siteId":null,"slug":"blogs/why-hubspot-partner-tiers-dont-matter-as-much-as-you-think-they-do","stagedFrom":null,"state":"PUBLISHED","stateWhenDeleted":null,"structuredContentPageType":null,"structuredContentType":null,"styleOverrideId":null,"subcategory":"normal_blog_post","syncedWithBlogRoot":true,"tagIds":[78562833827,80453663900,90840659382],"tagList":[{"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":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":1667848603406,"deletedAt":0,"description":"","id":90840659382,"label":"HubSpot","language":"en","name":"HubSpot","portalId":6534445,"slug":"hubspot","translatedFromId":null,"translations":{},"updated":1667848603406}],"tagNames":["HubSpot Partner","Agency Outsourcing","HubSpot"],"teamPerms":[],"templatePath":"","templatePathForRender":"deckerdevs-theme/templates/blog-content.html","textToAudioFileId":null,"textToAudioGenerationRequestId":null,"themePath":null,"themeSettingsValues":null,"title":"HubSpot Partner Tier Discussion","tmsId":null,"topicIds":[78562833827,80453663900,90840659382],"topicList":[{"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":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":1667848603406,"deletedAt":0,"description":"","id":90840659382,"label":"HubSpot","language":"en","name":"HubSpot","portalId":6534445,"slug":"hubspot","translatedFromId":null,"translations":{},"updated":1667848603406}],"topicNames":["HubSpot Partner","Agency Outsourcing","HubSpot"],"topics":[78562833827,80453663900,90840659382],"translatedContent":{},"translatedFromId":null,"translations":{},"tweet":null,"tweetAt":null,"tweetImmediately":false,"unpublishedAt":0,"updated":1674819144040,"updatedById":8506132,"upsizeFeaturedImage":false,"url":"https://deckerdevs.com/blogs/why-hubspot-partner-tiers-dont-matter-as-much-as-you-think-they-do","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":{},"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-developer-relationships-like-bert-ernie","afterPostBody":null,"aifeatures":null,"allowedSlugConflict":false,"analytics":null,"analyticsPageId":"83820159083","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":1662150369993,"createdByAgent":null,"createdById":27630257,"createdTime":1662150369993,"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-bert%20and%20ernie.png","featuredImageAltText":"","featuredImageHeight":1080,"featuredImageLength":0,"featuredImageWidth":1080,"flexAreas":{},"folderId":null,"footerHtml":null,"freezeDate":1662151185000,"generateJsonLdEnabledOverride":true,"hasContentAccessRules":false,"hasUserChanges":true,"headHtml":null,"header":null,"htmlTitle":"HubSpot CMS Developer Relationships Like Bert & Ernie","id":83820159083,"includeDefaultCustomCss":null,"isCaptchaRequired":true,"isCrawlableByBots":false,"isDraft":false,"isInstanceLayoutPage":false,"isInstantEmailEnabled":false,"isPublished":true,"isSocialPublishingEnabled":false,"keywords":[],"label":"HubSpot CMS Developer Relationships Like Bert & Ernie","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 Developer Relationships Like Bert & Ernie","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":"No relationship is perfect all the time, but the best ones stand the test of time. For nearly 30 years, Bert and Ernie have been depicted as best friends on Sesame Street, and while it hasn’t always been perfect, their longevity is definitely something admirable. In the same way, we think that your relationship with your HubSpot CMS developer should be no different. But all too often - that just isn’t the case.
\n\n![\"bert](\"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/bert%20and%20ernie.jpg\")
When it comes to relationships with web developers, we’ve heard and seen it all. We’ve seen so many agencies and clients that have been ghosted by their web developer, we’ve seen order takers that treat your website like they’re making a sandwich for you, we’ve seen what happens when HubSpot agencies grow *too* quickly, and we’ve told you many times what you deserve when you’re developing a website.
\n
We’ve decided we need to draw some parallels to make the comparison make more sense for you and it doesn’t get more wholesome or relatable than the friendship or Bert and Ernie. Here are a few reasons why when it comes to your relationship with your HubSpot CMS developer, Bert and Ernie are the goal:
They have different opinions, but they still care
\nYou’re not always going to see eye to eye with your developer and that’s important. Bert and Ernie are a great example of this. Ernie is more fun-loving and easygoing while Bert is more serious and pensive. You can see what I mean in the video embedded below. Can Ernie be a little much sometimes? Absolutely. But Ernie very clearly tells him, he’ll be his friend no matter what.
\n\n
\n
Your developer doesn’t have to be a carbon copy of everything you believe, want and aspire to, they just have to understand you, let you be you, and get things done. Knowing that they’re there no matter what happens is important. They should be responsive, prioritize your needs and have the care and talent to deliver on your behalf. This sounds like such a basic list of items, but good developers that treat you well and know what they’re doing in HubSpot are very hard to find.
They're consistent
\nBert and Ernie have been going on Sesame Street for almost 30 years and they’re still besties - that’s a relationship with staying power. While it’s not necessarily important when your relationship begins with your developer, you need to know that they have the necessary skills and expertise to be consistent in the delivery of your projects. Ask the right questions (we’ve got a great series of blogs with HubSpot CMS developer interview questions) in the interview process when you’re vetting your candidates to ensure that you’ll have someone with a history of consistently delivering awesome projects for their clients.
They go above and beyond
\nThere is nothing more adorable than this “Gift of the Magi” scene with Bert and Ernie.
\n
In the video (embedded above), Bert and Ernie give up their most prized possessions to barter for a gift that helps out with the other’s most prized possession. This is a great example of going above and beyond - and finding the kind of developer that honors your relationship enough to do that is rare. Many are lucky to even locate a qualified and responsive HubSpot developer, so to find a developer that will go above and beyond is pretty rare, but they’re out there!
While any skilled, experienced developer will have hard boundaries and not allow themselves to be taken advantage of, a developer that goes above and beyond will act as a consultant of sorts. They’ll look out for your best interests and let you know when there are aspects of your website that are problematic for you. They’ll spend time with you to lay out your strategy and really provide valuable insight on the best course of action.
Bert and Ernie are an iconic pair whose close friendship continually has them referenced as a dynamic duo. There’s no reason you shouldn’t have the same close relationship with your developer. While you don’t necessarily have to be *best* friends, it’s still the little things that make your relationship with your HubSpot CMS developer really great. Find a partner that is consistent, continually over delivers and really cares about you and your business enough to give it to you straight. While it might feel like developer partners are hard to come by, when you’re willing to pay for better service, experience and care, you’ll foster the right dynamic and longevity in your relationship with your HubSpot developer.
","rss_summary":"
No relationship is perfect all the time, but the best ones stand the test of time. For nearly 30 years, Bert and Ernie have been depicted as best friends on Sesame Street, and while it hasn’t always been perfect, their longevity is definitely something admirable. In the same way, we think that your relationship with your HubSpot CMS developer should be no different. But all too often - that just isn’t the case.
\n","rss_body":"No relationship is perfect all the time, but the best ones stand the test of time. For nearly 30 years, Bert and Ernie have been depicted as best friends on Sesame Street, and while it hasn’t always been perfect, their longevity is definitely something admirable. In the same way, we think that your relationship with your HubSpot CMS developer should be no different. But all too often - that just isn’t the case.
\n\n
When it comes to relationships with web developers, we’ve heard and seen it all. We’ve seen so many agencies and clients that have been ghosted by their web developer, we’ve seen order takers that treat your website like they’re making a sandwich for you, we’ve seen what happens when HubSpot agencies grow *too* quickly, and we’ve told you many times what you deserve when you’re developing a website.
\n
We’ve decided we need to draw some parallels to make the comparison make more sense for you and it doesn’t get more wholesome or relatable than the friendship or Bert and Ernie. Here are a few reasons why when it comes to your relationship with your HubSpot CMS developer, Bert and Ernie are the goal:
They have different opinions, but they still care
\nYou’re not always going to see eye to eye with your developer and that’s important. Bert and Ernie are a great example of this. Ernie is more fun-loving and easygoing while Bert is more serious and pensive. You can see what I mean in the video embedded below. Can Ernie be a little much sometimes? Absolutely. But Ernie very clearly tells him, he’ll be his friend no matter what.
\n\n
\n
Your developer doesn’t have to be a carbon copy of everything you believe, want and aspire to, they just have to understand you, let you be you, and get things done. Knowing that they’re there no matter what happens is important. They should be responsive, prioritize your needs and have the care and talent to deliver on your behalf. This sounds like such a basic list of items, but good developers that treat you well and know what they’re doing in HubSpot are very hard to find.
They're consistent
\nBert and Ernie have been going on Sesame Street for almost 30 years and they’re still besties - that’s a relationship with staying power. While it’s not necessarily important when your relationship begins with your developer, you need to know that they have the necessary skills and expertise to be consistent in the delivery of your projects. Ask the right questions (we’ve got a great series of blogs with HubSpot CMS developer interview questions) in the interview process when you’re vetting your candidates to ensure that you’ll have someone with a history of consistently delivering awesome projects for their clients.
They go above and beyond
\nThere is nothing more adorable than this “Gift of the Magi” scene with Bert and Ernie.
\n
In the video (embedded above), Bert and Ernie give up their most prized possessions to barter for a gift that helps out with the other’s most prized possession. This is a great example of going above and beyond - and finding the kind of developer that honors your relationship enough to do that is rare. Many are lucky to even locate a qualified and responsive HubSpot developer, so to find a developer that will go above and beyond is pretty rare, but they’re out there!
While any skilled, experienced developer will have hard boundaries and not allow themselves to be taken advantage of, a developer that goes above and beyond will act as a consultant of sorts. They’ll look out for your best interests and let you know when there are aspects of your website that are problematic for you. They’ll spend time with you to lay out your strategy and really provide valuable insight on the best course of action.
Bert and Ernie are an iconic pair whose close friendship continually has them referenced as a dynamic duo. There’s no reason you shouldn’t have the same close relationship with your developer. While you don’t necessarily have to be *best* friends, it’s still the little things that make your relationship with your HubSpot CMS developer really great. Find a partner that is consistent, continually over delivers and really cares about you and your business enough to give it to you straight. While it might feel like developer partners are hard to come by, when you’re willing to pay for better service, experience and care, you’ll foster the right dynamic and longevity in your relationship with your HubSpot developer.
","tag_ids":[62770442823,78562833827,80453663900],"topic_ids":[62770442823,78562833827,80453663900],"post_summary":"
No relationship is perfect all the time, but the best ones stand the test of time. For nearly 30 years, Bert and Ernie have been depicted as best friends on Sesame Street, and while it hasn’t always been perfect, their longevity is definitely something admirable. In the same way, we think that your relationship with your HubSpot CMS developer should be no different. But all too often - that just isn’t the case.
\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":"Your relationship with your HubSpot CMS developer should be kinda like Bert and Ernie's friendship...","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-bert%20and%20ernie.png","featured_image_width":1080,"featured_image_height":1080,"publish_timezone_offset":null,"theme_settings_values":null,"password":null,"header":null,"published_at":1722381453433,"last_edit_session_id":null,"last_edit_update_id":null,"created_by_agent":null},"metaDescription":"Your relationship with your HubSpot CMS developer should be kinda like Bert and Ernie's friendship...","metaKeywords":null,"name":"HubSpot CMS Developer Relationships Like Bert & Ernie","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":"HubSpot CMS Developer Relationships Like Bert & Ernie","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":"No relationship is perfect all the time, but the best ones stand the test of time. For nearly 30 years, Bert and Ernie have been depicted as best friends on Sesame Street, and while it hasn’t always been perfect, their longevity is definitely something admirable. In the same way, we think that your relationship with your HubSpot CMS developer should be no different. But all too often - that just isn’t the case.
\n\n
When it comes to relationships with web developers, we’ve heard and seen it all. We’ve seen so many agencies and clients that have been ghosted by their web developer, we’ve seen order takers that treat your website like they’re making a sandwich for you, we’ve seen what happens when HubSpot agencies grow *too* quickly, and we’ve told you many times what you deserve when you’re developing a website.
\n
We’ve decided we need to draw some parallels to make the comparison make more sense for you and it doesn’t get more wholesome or relatable than the friendship or Bert and Ernie. Here are a few reasons why when it comes to your relationship with your HubSpot CMS developer, Bert and Ernie are the goal:
They have different opinions, but they still care
\nYou’re not always going to see eye to eye with your developer and that’s important. Bert and Ernie are a great example of this. Ernie is more fun-loving and easygoing while Bert is more serious and pensive. You can see what I mean in the video embedded below. Can Ernie be a little much sometimes? Absolutely. But Ernie very clearly tells him, he’ll be his friend no matter what.
\n\n
\n
Your developer doesn’t have to be a carbon copy of everything you believe, want and aspire to, they just have to understand you, let you be you, and get things done. Knowing that they’re there no matter what happens is important. They should be responsive, prioritize your needs and have the care and talent to deliver on your behalf. This sounds like such a basic list of items, but good developers that treat you well and know what they’re doing in HubSpot are very hard to find.
They're consistent
\nBert and Ernie have been going on Sesame Street for almost 30 years and they’re still besties - that’s a relationship with staying power. While it’s not necessarily important when your relationship begins with your developer, you need to know that they have the necessary skills and expertise to be consistent in the delivery of your projects. Ask the right questions (we’ve got a great series of blogs with HubSpot CMS developer interview questions) in the interview process when you’re vetting your candidates to ensure that you’ll have someone with a history of consistently delivering awesome projects for their clients.
They go above and beyond
\nThere is nothing more adorable than this “Gift of the Magi” scene with Bert and Ernie.
\n
In the video (embedded above), Bert and Ernie give up their most prized possessions to barter for a gift that helps out with the other’s most prized possession. This is a great example of going above and beyond - and finding the kind of developer that honors your relationship enough to do that is rare. Many are lucky to even locate a qualified and responsive HubSpot developer, so to find a developer that will go above and beyond is pretty rare, but they’re out there!
While any skilled, experienced developer will have hard boundaries and not allow themselves to be taken advantage of, a developer that goes above and beyond will act as a consultant of sorts. They’ll look out for your best interests and let you know when there are aspects of your website that are problematic for you. They’ll spend time with you to lay out your strategy and really provide valuable insight on the best course of action.
Bert and Ernie are an iconic pair whose close friendship continually has them referenced as a dynamic duo. There’s no reason you shouldn’t have the same close relationship with your developer. While you don’t necessarily have to be *best* friends, it’s still the little things that make your relationship with your HubSpot CMS developer really great. Find a partner that is consistent, continually over delivers and really cares about you and your business enough to give it to you straight. While it might feel like developer partners are hard to come by, when you’re willing to pay for better service, experience and care, you’ll foster the right dynamic and longevity in your relationship with your HubSpot developer.
","postBodyRss":"
No relationship is perfect all the time, but the best ones stand the test of time. For nearly 30 years, Bert and Ernie have been depicted as best friends on Sesame Street, and while it hasn’t always been perfect, their longevity is definitely something admirable. In the same way, we think that your relationship with your HubSpot CMS developer should be no different. But all too often - that just isn’t the case.
\n\n
When it comes to relationships with web developers, we’ve heard and seen it all. We’ve seen so many agencies and clients that have been ghosted by their web developer, we’ve seen order takers that treat your website like they’re making a sandwich for you, we’ve seen what happens when HubSpot agencies grow *too* quickly, and we’ve told you many times what you deserve when you’re developing a website.
\n
We’ve decided we need to draw some parallels to make the comparison make more sense for you and it doesn’t get more wholesome or relatable than the friendship or Bert and Ernie. Here are a few reasons why when it comes to your relationship with your HubSpot CMS developer, Bert and Ernie are the goal:
They have different opinions, but they still care
\nYou’re not always going to see eye to eye with your developer and that’s important. Bert and Ernie are a great example of this. Ernie is more fun-loving and easygoing while Bert is more serious and pensive. You can see what I mean in the video embedded below. Can Ernie be a little much sometimes? Absolutely. But Ernie very clearly tells him, he’ll be his friend no matter what.
\n\n
\n
Your developer doesn’t have to be a carbon copy of everything you believe, want and aspire to, they just have to understand you, let you be you, and get things done. Knowing that they’re there no matter what happens is important. They should be responsive, prioritize your needs and have the care and talent to deliver on your behalf. This sounds like such a basic list of items, but good developers that treat you well and know what they’re doing in HubSpot are very hard to find.
They're consistent
\nBert and Ernie have been going on Sesame Street for almost 30 years and they’re still besties - that’s a relationship with staying power. While it’s not necessarily important when your relationship begins with your developer, you need to know that they have the necessary skills and expertise to be consistent in the delivery of your projects. Ask the right questions (we’ve got a great series of blogs with HubSpot CMS developer interview questions) in the interview process when you’re vetting your candidates to ensure that you’ll have someone with a history of consistently delivering awesome projects for their clients.
They go above and beyond
\nThere is nothing more adorable than this “Gift of the Magi” scene with Bert and Ernie.
\n
In the video (embedded above), Bert and Ernie give up their most prized possessions to barter for a gift that helps out with the other’s most prized possession. This is a great example of going above and beyond - and finding the kind of developer that honors your relationship enough to do that is rare. Many are lucky to even locate a qualified and responsive HubSpot developer, so to find a developer that will go above and beyond is pretty rare, but they’re out there!
While any skilled, experienced developer will have hard boundaries and not allow themselves to be taken advantage of, a developer that goes above and beyond will act as a consultant of sorts. They’ll look out for your best interests and let you know when there are aspects of your website that are problematic for you. They’ll spend time with you to lay out your strategy and really provide valuable insight on the best course of action.
Bert and Ernie are an iconic pair whose close friendship continually has them referenced as a dynamic duo. There’s no reason you shouldn’t have the same close relationship with your developer. While you don’t necessarily have to be *best* friends, it’s still the little things that make your relationship with your HubSpot CMS developer really great. Find a partner that is consistent, continually over delivers and really cares about you and your business enough to give it to you straight. While it might feel like developer partners are hard to come by, when you’re willing to pay for better service, experience and care, you’ll foster the right dynamic and longevity in your relationship with your HubSpot developer.
","postEmailContent":"
No relationship is perfect all the time, but the best ones stand the test of time. For nearly 30 years, Bert and Ernie have been depicted as best friends on Sesame Street, and while it hasn’t always been perfect, their longevity is definitely something admirable. In the same way, we think that your relationship with your HubSpot CMS developer should be no different. But all too often - that just isn’t the case.
","postFeaturedImageIfEnabled":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-bert%20and%20ernie.png","postListContent":"No relationship is perfect all the time, but the best ones stand the test of time. For nearly 30 years, Bert and Ernie have been depicted as best friends on Sesame Street, and while it hasn’t always been perfect, their longevity is definitely something admirable. In the same way, we think that your relationship with your HubSpot CMS developer should be no different. But all too often - that just isn’t the case.
","postListSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-bert%20and%20ernie.png","postRssContent":"No relationship is perfect all the time, but the best ones stand the test of time. For nearly 30 years, Bert and Ernie have been depicted as best friends on Sesame Street, and while it hasn’t always been perfect, their longevity is definitely something admirable. In the same way, we think that your relationship with your HubSpot CMS developer should be no different. But all too often - that just isn’t the case.
","postRssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-bert%20and%20ernie.png","postSummary":"No relationship is perfect all the time, but the best ones stand the test of time. For nearly 30 years, Bert and Ernie have been depicted as best friends on Sesame Street, and while it hasn’t always been perfect, their longevity is definitely something admirable. In the same way, we think that your relationship with your HubSpot CMS developer should be no different. But all too often - that just isn’t the case.
\n","postSummaryRss":"No relationship is perfect all the time, but the best ones stand the test of time. For nearly 30 years, Bert and Ernie have been depicted as best friends on Sesame Street, and while it hasn’t always been perfect, their longevity is definitely something admirable. In the same way, we think that your relationship with your HubSpot CMS developer should be no different. But all too often - that just isn’t the case.
","postTemplate":"deckerdevs-theme/templates/blog-content.html","previewImageSrc":null,"previewKey":"TiHnUQGs","previousPostFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/devHub/13.0_curved.svg","previousPostFeaturedImageAltText":"","previousPostName":"HubSpot Partner Tier Discussion","previousPostSlug":"blogs/why-hubspot-partner-tiers-dont-matter-as-much-as-you-think-they-do","processingStatus":"PUBLISHED","propertyForDynamicPageCanonicalUrl":null,"propertyForDynamicPageFeaturedImage":null,"propertyForDynamicPageMetaDescription":null,"propertyForDynamicPageSlug":null,"propertyForDynamicPageTitle":null,"publicAccessRules":[],"publicAccessRulesEnabled":false,"publishDate":1662151185000,"publishDateLocalTime":1662151185000,"publishDateLocalized":{"date":1662151185000,"format":"medium","language":null},"publishImmediately":true,"publishTimezoneOffset":null,"publishedAt":1722381453433,"publishedByEmail":null,"publishedById":61310730,"publishedByName":null,"publishedUrl":"https://deckerdevs.com/blogs/hubspot-cms-developer-relationships-like-bert-ernie","resolvedDomain":"deckerdevs.com","resolvedLanguage":null,"rssBody":"No relationship is perfect all the time, but the best ones stand the test of time. For nearly 30 years, Bert and Ernie have been depicted as best friends on Sesame Street, and while it hasn’t always been perfect, their longevity is definitely something admirable. In the same way, we think that your relationship with your HubSpot CMS developer should be no different. But all too often - that just isn’t the case.
\n\n
When it comes to relationships with web developers, we’ve heard and seen it all. We’ve seen so many agencies and clients that have been ghosted by their web developer, we’ve seen order takers that treat your website like they’re making a sandwich for you, we’ve seen what happens when HubSpot agencies grow *too* quickly, and we’ve told you many times what you deserve when you’re developing a website.
\n
We’ve decided we need to draw some parallels to make the comparison make more sense for you and it doesn’t get more wholesome or relatable than the friendship or Bert and Ernie. Here are a few reasons why when it comes to your relationship with your HubSpot CMS developer, Bert and Ernie are the goal:
They have different opinions, but they still care
\nYou’re not always going to see eye to eye with your developer and that’s important. Bert and Ernie are a great example of this. Ernie is more fun-loving and easygoing while Bert is more serious and pensive. You can see what I mean in the video embedded below. Can Ernie be a little much sometimes? Absolutely. But Ernie very clearly tells him, he’ll be his friend no matter what.
\n\n
\n
Your developer doesn’t have to be a carbon copy of everything you believe, want and aspire to, they just have to understand you, let you be you, and get things done. Knowing that they’re there no matter what happens is important. They should be responsive, prioritize your needs and have the care and talent to deliver on your behalf. This sounds like such a basic list of items, but good developers that treat you well and know what they’re doing in HubSpot are very hard to find.
They're consistent
\nBert and Ernie have been going on Sesame Street for almost 30 years and they’re still besties - that’s a relationship with staying power. While it’s not necessarily important when your relationship begins with your developer, you need to know that they have the necessary skills and expertise to be consistent in the delivery of your projects. Ask the right questions (we’ve got a great series of blogs with HubSpot CMS developer interview questions) in the interview process when you’re vetting your candidates to ensure that you’ll have someone with a history of consistently delivering awesome projects for their clients.
They go above and beyond
\nThere is nothing more adorable than this “Gift of the Magi” scene with Bert and Ernie.
\n
In the video (embedded above), Bert and Ernie give up their most prized possessions to barter for a gift that helps out with the other’s most prized possession. This is a great example of going above and beyond - and finding the kind of developer that honors your relationship enough to do that is rare. Many are lucky to even locate a qualified and responsive HubSpot developer, so to find a developer that will go above and beyond is pretty rare, but they’re out there!
While any skilled, experienced developer will have hard boundaries and not allow themselves to be taken advantage of, a developer that goes above and beyond will act as a consultant of sorts. They’ll look out for your best interests and let you know when there are aspects of your website that are problematic for you. They’ll spend time with you to lay out your strategy and really provide valuable insight on the best course of action.
Bert and Ernie are an iconic pair whose close friendship continually has them referenced as a dynamic duo. There’s no reason you shouldn’t have the same close relationship with your developer. While you don’t necessarily have to be *best* friends, it’s still the little things that make your relationship with your HubSpot CMS developer really great. Find a partner that is consistent, continually over delivers and really cares about you and your business enough to give it to you straight. While it might feel like developer partners are hard to come by, when you’re willing to pay for better service, experience and care, you’ll foster the right dynamic and longevity in your relationship with your HubSpot developer.
","rssSummary":"
No relationship is perfect all the time, but the best ones stand the test of time. For nearly 30 years, Bert and Ernie have been depicted as best friends on Sesame Street, and while it hasn’t always been perfect, their longevity is definitely something admirable. In the same way, we think that your relationship with your HubSpot CMS developer should be no different. But all too often - that just isn’t the case.
\n","rssSummaryFeaturedImage":"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/deckerdevs-bert%20and%20ernie.png","scheduledUpdateDate":0,"screenshotPreviewTakenAt":1736723853203,"screenshotPreviewUrl":"https://cdn1.hubspot.net/hubshotv3/prod/e/0/323d7395-ffeb-4499-8b01-c6789ffa5d45.png","sections":{},"securityState":"NONE","siteId":null,"slug":"blogs/hubspot-cms-developer-relationships-like-bert-ernie","stagedFrom":null,"state":"PUBLISHED","stateWhenDeleted":null,"structuredContentPageType":null,"structuredContentType":null,"styleOverrideId":null,"subcategory":"normal_blog_post","syncedWithBlogRoot":true,"tagIds":[62770442823,78562833827,80453663900],"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":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":["HubSpot CMS Development","HubSpot Partner","Agency Outsourcing"],"teamPerms":[],"templatePath":"","templatePathForRender":"deckerdevs-theme/templates/blog-content.html","textToAudioFileId":null,"textToAudioGenerationRequestId":null,"themePath":null,"themeSettingsValues":null,"title":"HubSpot CMS Developer Relationships Like Bert & Ernie","tmsId":null,"topicIds":[62770442823,78562833827,80453663900],"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":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":["HubSpot CMS Development","HubSpot Partner","Agency Outsourcing"],"topics":[62770442823,78562833827,80453663900],"translatedContent":{},"translatedFromId":null,"translations":{},"tweet":null,"tweetAt":null,"tweetImmediately":false,"unpublishedAt":0,"updated":1722381453436,"updatedById":61310730,"upsizeFeaturedImage":false,"url":"https://deckerdevs.com/blogs/hubspot-cms-developer-relationships-like-bert-ernie","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 Developer Relationships Like Bert & Ernie","heading_size":"h1","heading_tag":"h1","image_holder":{"image_field":{"alt":"deckerdevs-bert and ernie","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-bert%20and%20ernie.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}},"child_css":{},"css":{},"deleted_at":1722380934974,"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/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:
Who will the architect be in this project?
\nIn 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.
![\"8\"](\"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/8.png\")
\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.
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.
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.
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.
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.
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.
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.
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.
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.
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
![\"9\"](\"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/9.png\")
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.
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
","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:
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:
Who will the architect be in this project?
\nIn 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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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
","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:
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:
Who will the architect be in this project?
\nIn 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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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
","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:
Who will the architect be in this project?
\nIn 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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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
","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:
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:
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:
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:
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:
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:
Who will the architect be in this project?
\nIn 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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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
","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:
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
![\"hs](\"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/hs%20partners.svg\")
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:
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.
It'll shorten the development process
\n
Who doesn’t love scope creep?
Just kidding. Everyone hates scope creep.
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. ![\"deckerdevs-mobile](\"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/deckerdevs-mobile%20optimization-1.svg\")
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
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.
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.
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.
","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:
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:
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.
It'll shorten the development process
\n
Who doesn’t love scope creep?
Just kidding. Everyone hates scope creep.
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
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.
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.
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.
","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:
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:
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.
It'll shorten the development process
\n
Who doesn’t love scope creep?
Just kidding. Everyone hates scope creep.
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
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.
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.
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.
","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:
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.
It'll shorten the development process
\n
Who doesn’t love scope creep?
Just kidding. Everyone hates scope creep.
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
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.
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.
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.
","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:
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:
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:
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:
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:
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:
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.
It'll shorten the development process
\n
Who doesn’t love scope creep?
Just kidding. Everyone hates scope creep.
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
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.
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.
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.
","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:
Business owners, marketers, and executive teams groan when it comes time for a new website project, and for good reason. It’s rare that a website project (particularly a redesign) stays within a reasonable budget or timeline. As quality HubSpot CMS developers become harder to find, and the biggest agencies continue to run into issues with scaling, a new website project proposal process can seem daunting. If you have only had bad experiences with website builds, what do you need to know to ensure things go more smoothly next time?
We’ve shared the warning signs that it’s time to ditch your current HubSpot developer, but you should also know what to expect when you choose a HubSpot developer. Here are seven things you can expect from a qualified, experienced HubSpot CMS developer when you’re developing a new website project.
1. A projected timeline.
\n
It’s hard to predict exactly when a website will launch, and while the go-live day can change based on any number of factors, setting an approximate timeline or specifying a certain week of the month you expect to finalize the project is more than reasonable. If you have a target date, you can build a for deliverables, including the delivery of the design, sign-off and approval of that design, development of modules, and delivery of a quality-assured and -tested first draft.
Your development partner should break down the timeline and hold you accountable as well, by specifying the date when final first draft edits are needed, as well as having you name a single point of contact to manage all edits on your side. This minimizes the back and forth for last-minute changes to design or afterthought additions to the website. While there are always a few edits and bugs to work out, for the most part once your design is approved and finalized, development should be fairly straightforward.
Be wary of developers promising a very specific launch date or refusing to adjust a launch date based on how the project unfolds. Setting realistic expectations is important, and unless you’ve worked with your developer in the past, it’s unlikely that you’ll meet a set-in-stone launch date. There are a number of variables outside a developer’s control that can affect the ability to launch at an exact date, such as delayed delivery of edits, additional design changes, or out of scope work. While a single-day delay may not impact a launch date, prolonged delays or the accumulation of minor delays can start to put pressure on the developer.
Busy dev agencies typically have their development staff estimated out. If your approvals and content aren’t delivered on time, this could come back to bite you later. Be sure to do your own due diligence and understand that it’s possible you might have played a role in your delayed launch. The ideal developer will work with you and explain that timelines are a guideline or estimate, and the more closely you both do your parts, the closer to that estimate the actual launch will be.
2. A finalized proof.
\n
We recently had a prospect come in whose HubSpot agency was bogged down (link when available). Whether that agency was chronically short staffed or just growing at a super fast pace, the Marketing Manager that we met with was pretty upset about the final draft that was delivered to them. “It’s almost as though they want us to handle the quality control, there were so many bugs and formatting issues. The proof didn’t even look like the agreed-upon design.”
It’s the worst to get clients that are unhappy with the delivery of a project that has such a significant upfront investment —so unhappy that they had to move development agencies to get quality delivered. By delineating the deliverables and responsibilities of each party, a client can easily hold their developer accountable by pointing back to the project timeline and responsibilities outline in order to receive exactly what they expect when it’s time for the final draft to be reviewed.
3. Feedback on your design requests.
\n
We say it a lot, but your developer should be more than an order taker. If you approach your agency with a preconceived design concept and haven’t had a UX/UI expert review it, your web developer should have usability and design feature feedback and suggestions based on your goals. They should be experienced enough in the front and back end of HubSpot CMS to point out potential issues with design and ask detailed questions on your expectations for both the end-user and the marketing team that will be updating content.
A user-friendly interface will allow employees to operate more efficiently and users to find the information they need with ease, increasing conversion rates and selling more products and services. It’s possible you’ve got a great design, but you should very specifically ask your developer for their feedback and suggestions. Their answer will tell a lot about the depth of their expertise and understanding of the relations among marketing, conversion optimization, and development.
Related reading: Your Website Isn’t a Submarine Sandwich
\n4. Accountability and updates.
\n![\"HubSpot](\"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/BLOG%20Images/HubSpot%20CMS%20developer%20Utopia%207%20things%20to%20expect%20when%20developing%20a%20Hubspot%20website%20(1).webp\")
Sometimes projects run into delays. Whether we’re waiting on access to a third-party application that we’re integrating with the website, your edits are taking longer than expected, or we’ve just run into challenges implementing the design, sometimes projects don’t run on time. Communication is the difference between an experienced, accountable developer and an inexperienced developer who’s bogged down or doesn’t have your best interests in mind.
Your HubSpot developer should have your project mapped out from the start. Any missed milestone has the potential to delay the delivery timeline. An experienced developer will know this and reach out quickly to communicate rather than making excuses when the project is running behind schedule. They’ll quickly inform you of the timeline for out of scope work and how you can expect those design changes or edits to impact the timeline initially discussed.
\n5. Push for needed items.
\n
Every web developer knows how busy small- to medium-sized businesses can be. With employees taking on multiple job functions and a huge focus on performance, delays in needed items can sometimes occur. Rather than sitting around and waiting (unless they’ve been specifically instructed to do so due to project delays), a qualified and experienced developer will follow up on deadlines for content, images, style elements, and feedback to keep a project running on time. They understand that your goals are important and that sometimes the day to day can get in the way of timely delivery. They’ll push for what they need and try to help you organize it as simply as possible for efficient handoff.
6. Training and support.
\n
Often a website project will launch and additional work will be needed. An employee might find inaccurate data in the website, an important design change may be needed, or marketing and IT staff may need training on how to change and edit the website. An experienced developer will accommodate this by providing a certain number of hours for training, support, and bug fixes for up to a week or two after project launch. They’ll hand-hold the transition and make sure they’re readily available should anything happen or should quick edits need to be made. Your developer shouldn’t ghost you or fail to support their work after the fact.
7. Post-launch feedback timeline.
\n
While a skilled, experienced, reputable HubSpot developer will stand behind their work and assist in the transition and delivery of your website after launch, they’ll also be sure to hold your organization accountable when it comes to edits and bug fixes. They’ll often provide one or two weeks for your point of contact to reach out with any issues that need to be completed or fixed. Once this timeline has expired, there may be a small amount of wiggle room, but generally you should expect to pay for any edits or changes after the agreed-upon delivery deadline. More proactive developers will have already negotiated a growth-driven design retainer of some sort to help ensure that you can continuously improve your website as your marketing evolves.
It is worthwhile to talk about the difference between defects or bug fixes and revisions. This is something that your developer will help you define beforehand and help categorize as they come up. Bug fixes or defects are items that aren’t working properly or weren’t executed correctly by the developer. Revisions are small tweaks that a client may find after the fact for elements that don’t work as well as they expected. For instance, the structure or length of copy or placeholder photos versus actual photos may make the delivered site different from the original design. Revisions will usually cost extra, but this can vary depending on the developer and whether the project came in within scope.
Related reading: the continuous improvement model
\n
Strategy for what’s to come.
\n
Continuous improvement is the next step for any company with a focus on inbound marketing. You’ll probably need to add more landing page templates, additional modules, or new calculators or other widgets as you understand more about the buyer’s journey. The complexity of the information you present will change and you’ll want to be sure that your website is keeping up with the ever-changing needs of your marketing staff. Having a growth-driven design retainer for continual improvement and evolution of your website is important, and your development team should discuss this both before and after launch to help you prepare a budget. This will ensure that your marketing staff continues to be happy with your website on an ongoing basis and avoid those expensive overhauls every three to five years.
Not every company owner, marketing manager, or agency that is outsourcing HubSpot development work knows what to expect or what needs to be done when it comes to a new HubSpot CMS development project. A skilled, experienced developer will have structures in place and communicate the needs and expectations for both their agency and your organization when it comes to delivering the project according to your expectations.
It might take time and it might not always look perfect, but fostering a close relationship with your HubSpot development professional is extremely important to the success of your marketing, the happiness of your employees, and the evolution of your online presence. Do your diligence to qualify any developer you’re vetting. If you need help, we’re always willing to provide a second opinion.
\n\n
Business owners, marketers, and executive teams groan when it comes time for a new website project, and for good reason. It’s rare that a website project (particularly a redesign) stays within a reasonable budget or timeline. As quality HubSpot CMS developers become harder to find, and the biggest agencies continue to run into issues with scaling, a new website project proposal process can seem daunting. If you have only had bad experiences with website builds, what do you need to know to ensure things go more smoothly next time?
Business owners, marketers, and executive teams groan when it comes time for a new website project, and for good reason. It’s rare that a website project (particularly a redesign) stays within a reasonable budget or timeline. As quality HubSpot CMS developers become harder to find, and the biggest agencies continue to run into issues with scaling, a new website project proposal process can seem daunting. If you have only had bad experiences with website builds, what do you need to know to ensure things go more smoothly next time?
We’ve shared the warning signs that it’s time to ditch your current HubSpot developer, but you should also know what to expect when you choose a HubSpot developer. Here are seven things you can expect from a qualified, experienced HubSpot CMS developer when you’re developing a new website project.
1. A projected timeline.
\n
It’s hard to predict exactly when a website will launch, and while the go-live day can change based on any number of factors, setting an approximate timeline or specifying a certain week of the month you expect to finalize the project is more than reasonable. If you have a target date, you can build a for deliverables, including the delivery of the design, sign-off and approval of that design, development of modules, and delivery of a quality-assured and -tested first draft.
Your development partner should break down the timeline and hold you accountable as well, by specifying the date when final first draft edits are needed, as well as having you name a single point of contact to manage all edits on your side. This minimizes the back and forth for last-minute changes to design or afterthought additions to the website. While there are always a few edits and bugs to work out, for the most part once your design is approved and finalized, development should be fairly straightforward.
Be wary of developers promising a very specific launch date or refusing to adjust a launch date based on how the project unfolds. Setting realistic expectations is important, and unless you’ve worked with your developer in the past, it’s unlikely that you’ll meet a set-in-stone launch date. There are a number of variables outside a developer’s control that can affect the ability to launch at an exact date, such as delayed delivery of edits, additional design changes, or out of scope work. While a single-day delay may not impact a launch date, prolonged delays or the accumulation of minor delays can start to put pressure on the developer.
Busy dev agencies typically have their development staff estimated out. If your approvals and content aren’t delivered on time, this could come back to bite you later. Be sure to do your own due diligence and understand that it’s possible you might have played a role in your delayed launch. The ideal developer will work with you and explain that timelines are a guideline or estimate, and the more closely you both do your parts, the closer to that estimate the actual launch will be.
2. A finalized proof.
\n
We recently had a prospect come in whose HubSpot agency was bogged down (link when available). Whether that agency was chronically short staffed or just growing at a super fast pace, the Marketing Manager that we met with was pretty upset about the final draft that was delivered to them. “It’s almost as though they want us to handle the quality control, there were so many bugs and formatting issues. The proof didn’t even look like the agreed-upon design.”
It’s the worst to get clients that are unhappy with the delivery of a project that has such a significant upfront investment —so unhappy that they had to move development agencies to get quality delivered. By delineating the deliverables and responsibilities of each party, a client can easily hold their developer accountable by pointing back to the project timeline and responsibilities outline in order to receive exactly what they expect when it’s time for the final draft to be reviewed.
3. Feedback on your design requests.
\n
We say it a lot, but your developer should be more than an order taker. If you approach your agency with a preconceived design concept and haven’t had a UX/UI expert review it, your web developer should have usability and design feature feedback and suggestions based on your goals. They should be experienced enough in the front and back end of HubSpot CMS to point out potential issues with design and ask detailed questions on your expectations for both the end-user and the marketing team that will be updating content.
A user-friendly interface will allow employees to operate more efficiently and users to find the information they need with ease, increasing conversion rates and selling more products and services. It’s possible you’ve got a great design, but you should very specifically ask your developer for their feedback and suggestions. Their answer will tell a lot about the depth of their expertise and understanding of the relations among marketing, conversion optimization, and development.
Related reading: Your Website Isn’t a Submarine Sandwich
\n4. Accountability and updates.
\n
Sometimes projects run into delays. Whether we’re waiting on access to a third-party application that we’re integrating with the website, your edits are taking longer than expected, or we’ve just run into challenges implementing the design, sometimes projects don’t run on time. Communication is the difference between an experienced, accountable developer and an inexperienced developer who’s bogged down or doesn’t have your best interests in mind.
Your HubSpot developer should have your project mapped out from the start. Any missed milestone has the potential to delay the delivery timeline. An experienced developer will know this and reach out quickly to communicate rather than making excuses when the project is running behind schedule. They’ll quickly inform you of the timeline for out of scope work and how you can expect those design changes or edits to impact the timeline initially discussed.
\n5. Push for needed items.
\n
Every web developer knows how busy small- to medium-sized businesses can be. With employees taking on multiple job functions and a huge focus on performance, delays in needed items can sometimes occur. Rather than sitting around and waiting (unless they’ve been specifically instructed to do so due to project delays), a qualified and experienced developer will follow up on deadlines for content, images, style elements, and feedback to keep a project running on time. They understand that your goals are important and that sometimes the day to day can get in the way of timely delivery. They’ll push for what they need and try to help you organize it as simply as possible for efficient handoff.
6. Training and support.
\n
Often a website project will launch and additional work will be needed. An employee might find inaccurate data in the website, an important design change may be needed, or marketing and IT staff may need training on how to change and edit the website. An experienced developer will accommodate this by providing a certain number of hours for training, support, and bug fixes for up to a week or two after project launch. They’ll hand-hold the transition and make sure they’re readily available should anything happen or should quick edits need to be made. Your developer shouldn’t ghost you or fail to support their work after the fact.
7. Post-launch feedback timeline.
\n
While a skilled, experienced, reputable HubSpot developer will stand behind their work and assist in the transition and delivery of your website after launch, they’ll also be sure to hold your organization accountable when it comes to edits and bug fixes. They’ll often provide one or two weeks for your point of contact to reach out with any issues that need to be completed or fixed. Once this timeline has expired, there may be a small amount of wiggle room, but generally you should expect to pay for any edits or changes after the agreed-upon delivery deadline. More proactive developers will have already negotiated a growth-driven design retainer of some sort to help ensure that you can continuously improve your website as your marketing evolves.
It is worthwhile to talk about the difference between defects or bug fixes and revisions. This is something that your developer will help you define beforehand and help categorize as they come up. Bug fixes or defects are items that aren’t working properly or weren’t executed correctly by the developer. Revisions are small tweaks that a client may find after the fact for elements that don’t work as well as they expected. For instance, the structure or length of copy or placeholder photos versus actual photos may make the delivered site different from the original design. Revisions will usually cost extra, but this can vary depending on the developer and whether the project came in within scope.
Related reading: the continuous improvement model
\n
Strategy for what’s to come.
\n
Continuous improvement is the next step for any company with a focus on inbound marketing. You’ll probably need to add more landing page templates, additional modules, or new calculators or other widgets as you understand more about the buyer’s journey. The complexity of the information you present will change and you’ll want to be sure that your website is keeping up with the ever-changing needs of your marketing staff. Having a growth-driven design retainer for continual improvement and evolution of your website is important, and your development team should discuss this both before and after launch to help you prepare a budget. This will ensure that your marketing staff continues to be happy with your website on an ongoing basis and avoid those expensive overhauls every three to five years.
Not every company owner, marketing manager, or agency that is outsourcing HubSpot development work knows what to expect or what needs to be done when it comes to a new HubSpot CMS development project. A skilled, experienced developer will have structures in place and communicate the needs and expectations for both their agency and your organization when it comes to delivering the project according to your expectations.
It might take time and it might not always look perfect, but fostering a close relationship with your HubSpot development professional is extremely important to the success of your marketing, the happiness of your employees, and the evolution of your online presence. Do your diligence to qualify any developer you’re vetting. If you need help, we’re always willing to provide a second opinion.
\n\n
Business owners, marketers, and executive teams groan when it comes time for a new website project, and for good reason. It’s rare that a website project (particularly a redesign) stays within a reasonable budget or timeline. As quality HubSpot CMS developers become harder to find, and the biggest agencies continue to run into issues with scaling, a new website project proposal process can seem daunting. If you have only had bad experiences with website builds, what do you need to know to ensure things go more smoothly next time?
Business owners, marketers, and executive teams groan when it comes time for a new website project, and for good reason. It’s rare that a website project (particularly a redesign) stays within a reasonable budget or timeline. As quality HubSpot CMS developers become harder to find, and the biggest agencies continue to run into issues with scaling, a new website project proposal process can seem daunting. If you have only had bad experiences with website builds, what do you need to know to ensure things go more smoothly next time?
We’ve shared the warning signs that it’s time to ditch your current HubSpot developer, but you should also know what to expect when you choose a HubSpot developer. Here are seven things you can expect from a qualified, experienced HubSpot CMS developer when you’re developing a new website project.
1. A projected timeline.
\n
It’s hard to predict exactly when a website will launch, and while the go-live day can change based on any number of factors, setting an approximate timeline or specifying a certain week of the month you expect to finalize the project is more than reasonable. If you have a target date, you can build a for deliverables, including the delivery of the design, sign-off and approval of that design, development of modules, and delivery of a quality-assured and -tested first draft.
Your development partner should break down the timeline and hold you accountable as well, by specifying the date when final first draft edits are needed, as well as having you name a single point of contact to manage all edits on your side. This minimizes the back and forth for last-minute changes to design or afterthought additions to the website. While there are always a few edits and bugs to work out, for the most part once your design is approved and finalized, development should be fairly straightforward.
Be wary of developers promising a very specific launch date or refusing to adjust a launch date based on how the project unfolds. Setting realistic expectations is important, and unless you’ve worked with your developer in the past, it’s unlikely that you’ll meet a set-in-stone launch date. There are a number of variables outside a developer’s control that can affect the ability to launch at an exact date, such as delayed delivery of edits, additional design changes, or out of scope work. While a single-day delay may not impact a launch date, prolonged delays or the accumulation of minor delays can start to put pressure on the developer.
Busy dev agencies typically have their development staff estimated out. If your approvals and content aren’t delivered on time, this could come back to bite you later. Be sure to do your own due diligence and understand that it’s possible you might have played a role in your delayed launch. The ideal developer will work with you and explain that timelines are a guideline or estimate, and the more closely you both do your parts, the closer to that estimate the actual launch will be.
2. A finalized proof.
\n
We recently had a prospect come in whose HubSpot agency was bogged down (link when available). Whether that agency was chronically short staffed or just growing at a super fast pace, the Marketing Manager that we met with was pretty upset about the final draft that was delivered to them. “It’s almost as though they want us to handle the quality control, there were so many bugs and formatting issues. The proof didn’t even look like the agreed-upon design.”
It’s the worst to get clients that are unhappy with the delivery of a project that has such a significant upfront investment —so unhappy that they had to move development agencies to get quality delivered. By delineating the deliverables and responsibilities of each party, a client can easily hold their developer accountable by pointing back to the project timeline and responsibilities outline in order to receive exactly what they expect when it’s time for the final draft to be reviewed.
3. Feedback on your design requests.
\n
We say it a lot, but your developer should be more than an order taker. If you approach your agency with a preconceived design concept and haven’t had a UX/UI expert review it, your web developer should have usability and design feature feedback and suggestions based on your goals. They should be experienced enough in the front and back end of HubSpot CMS to point out potential issues with design and ask detailed questions on your expectations for both the end-user and the marketing team that will be updating content.
A user-friendly interface will allow employees to operate more efficiently and users to find the information they need with ease, increasing conversion rates and selling more products and services. It’s possible you’ve got a great design, but you should very specifically ask your developer for their feedback and suggestions. Their answer will tell a lot about the depth of their expertise and understanding of the relations among marketing, conversion optimization, and development.
Related reading: Your Website Isn’t a Submarine Sandwich
\n4. Accountability and updates.
\n
Sometimes projects run into delays. Whether we’re waiting on access to a third-party application that we’re integrating with the website, your edits are taking longer than expected, or we’ve just run into challenges implementing the design, sometimes projects don’t run on time. Communication is the difference between an experienced, accountable developer and an inexperienced developer who’s bogged down or doesn’t have your best interests in mind.
Your HubSpot developer should have your project mapped out from the start. Any missed milestone has the potential to delay the delivery timeline. An experienced developer will know this and reach out quickly to communicate rather than making excuses when the project is running behind schedule. They’ll quickly inform you of the timeline for out of scope work and how you can expect those design changes or edits to impact the timeline initially discussed.
\n5. Push for needed items.
\n
Every web developer knows how busy small- to medium-sized businesses can be. With employees taking on multiple job functions and a huge focus on performance, delays in needed items can sometimes occur. Rather than sitting around and waiting (unless they’ve been specifically instructed to do so due to project delays), a qualified and experienced developer will follow up on deadlines for content, images, style elements, and feedback to keep a project running on time. They understand that your goals are important and that sometimes the day to day can get in the way of timely delivery. They’ll push for what they need and try to help you organize it as simply as possible for efficient handoff.
6. Training and support.
\n
Often a website project will launch and additional work will be needed. An employee might find inaccurate data in the website, an important design change may be needed, or marketing and IT staff may need training on how to change and edit the website. An experienced developer will accommodate this by providing a certain number of hours for training, support, and bug fixes for up to a week or two after project launch. They’ll hand-hold the transition and make sure they’re readily available should anything happen or should quick edits need to be made. Your developer shouldn’t ghost you or fail to support their work after the fact.
7. Post-launch feedback timeline.
\n
While a skilled, experienced, reputable HubSpot developer will stand behind their work and assist in the transition and delivery of your website after launch, they’ll also be sure to hold your organization accountable when it comes to edits and bug fixes. They’ll often provide one or two weeks for your point of contact to reach out with any issues that need to be completed or fixed. Once this timeline has expired, there may be a small amount of wiggle room, but generally you should expect to pay for any edits or changes after the agreed-upon delivery deadline. More proactive developers will have already negotiated a growth-driven design retainer of some sort to help ensure that you can continuously improve your website as your marketing evolves.
It is worthwhile to talk about the difference between defects or bug fixes and revisions. This is something that your developer will help you define beforehand and help categorize as they come up. Bug fixes or defects are items that aren’t working properly or weren’t executed correctly by the developer. Revisions are small tweaks that a client may find after the fact for elements that don’t work as well as they expected. For instance, the structure or length of copy or placeholder photos versus actual photos may make the delivered site different from the original design. Revisions will usually cost extra, but this can vary depending on the developer and whether the project came in within scope.
Related reading: the continuous improvement model
\n
Strategy for what’s to come.
\n
Continuous improvement is the next step for any company with a focus on inbound marketing. You’ll probably need to add more landing page templates, additional modules, or new calculators or other widgets as you understand more about the buyer’s journey. The complexity of the information you present will change and you’ll want to be sure that your website is keeping up with the ever-changing needs of your marketing staff. Having a growth-driven design retainer for continual improvement and evolution of your website is important, and your development team should discuss this both before and after launch to help you prepare a budget. This will ensure that your marketing staff continues to be happy with your website on an ongoing basis and avoid those expensive overhauls every three to five years.
Not every company owner, marketing manager, or agency that is outsourcing HubSpot development work knows what to expect or what needs to be done when it comes to a new HubSpot CMS development project. A skilled, experienced developer will have structures in place and communicate the needs and expectations for both their agency and your organization when it comes to delivering the project according to your expectations.
It might take time and it might not always look perfect, but fostering a close relationship with your HubSpot development professional is extremely important to the success of your marketing, the happiness of your employees, and the evolution of your online presence. Do your diligence to qualify any developer you’re vetting. If you need help, we’re always willing to provide a second opinion.
\n\n
Business owners, marketers, and executive teams groan when it comes time for a new website project, and for good reason. It’s rare that a website project (particularly a redesign) stays within a reasonable budget or timeline. As quality HubSpot CMS developers become harder to find, and the biggest agencies continue to run into issues with scaling, a new website project proposal process can seem daunting. If you have only had bad experiences with website builds, what do you need to know to ensure things go more smoothly next time?
We’ve shared the warning signs that it’s time to ditch your current HubSpot developer, but you should also know what to expect when you choose a HubSpot developer. Here are seven things you can expect from a qualified, experienced HubSpot CMS developer when you’re developing a new website project.
1. A projected timeline.
\n
It’s hard to predict exactly when a website will launch, and while the go-live day can change based on any number of factors, setting an approximate timeline or specifying a certain week of the month you expect to finalize the project is more than reasonable. If you have a target date, you can build a for deliverables, including the delivery of the design, sign-off and approval of that design, development of modules, and delivery of a quality-assured and -tested first draft.
Your development partner should break down the timeline and hold you accountable as well, by specifying the date when final first draft edits are needed, as well as having you name a single point of contact to manage all edits on your side. This minimizes the back and forth for last-minute changes to design or afterthought additions to the website. While there are always a few edits and bugs to work out, for the most part once your design is approved and finalized, development should be fairly straightforward.
Be wary of developers promising a very specific launch date or refusing to adjust a launch date based on how the project unfolds. Setting realistic expectations is important, and unless you’ve worked with your developer in the past, it’s unlikely that you’ll meet a set-in-stone launch date. There are a number of variables outside a developer’s control that can affect the ability to launch at an exact date, such as delayed delivery of edits, additional design changes, or out of scope work. While a single-day delay may not impact a launch date, prolonged delays or the accumulation of minor delays can start to put pressure on the developer.
Busy dev agencies typically have their development staff estimated out. If your approvals and content aren’t delivered on time, this could come back to bite you later. Be sure to do your own due diligence and understand that it’s possible you might have played a role in your delayed launch. The ideal developer will work with you and explain that timelines are a guideline or estimate, and the more closely you both do your parts, the closer to that estimate the actual launch will be.
2. A finalized proof.
\n
We recently had a prospect come in whose HubSpot agency was bogged down (link when available). Whether that agency was chronically short staffed or just growing at a super fast pace, the Marketing Manager that we met with was pretty upset about the final draft that was delivered to them. “It’s almost as though they want us to handle the quality control, there were so many bugs and formatting issues. The proof didn’t even look like the agreed-upon design.”
It’s the worst to get clients that are unhappy with the delivery of a project that has such a significant upfront investment —so unhappy that they had to move development agencies to get quality delivered. By delineating the deliverables and responsibilities of each party, a client can easily hold their developer accountable by pointing back to the project timeline and responsibilities outline in order to receive exactly what they expect when it’s time for the final draft to be reviewed.
3. Feedback on your design requests.
\n
We say it a lot, but your developer should be more than an order taker. If you approach your agency with a preconceived design concept and haven’t had a UX/UI expert review it, your web developer should have usability and design feature feedback and suggestions based on your goals. They should be experienced enough in the front and back end of HubSpot CMS to point out potential issues with design and ask detailed questions on your expectations for both the end-user and the marketing team that will be updating content.
A user-friendly interface will allow employees to operate more efficiently and users to find the information they need with ease, increasing conversion rates and selling more products and services. It’s possible you’ve got a great design, but you should very specifically ask your developer for their feedback and suggestions. Their answer will tell a lot about the depth of their expertise and understanding of the relations among marketing, conversion optimization, and development.
Related reading: Your Website Isn’t a Submarine Sandwich
\n4. Accountability and updates.
\n
Sometimes projects run into delays. Whether we’re waiting on access to a third-party application that we’re integrating with the website, your edits are taking longer than expected, or we’ve just run into challenges implementing the design, sometimes projects don’t run on time. Communication is the difference between an experienced, accountable developer and an inexperienced developer who’s bogged down or doesn’t have your best interests in mind.
Your HubSpot developer should have your project mapped out from the start. Any missed milestone has the potential to delay the delivery timeline. An experienced developer will know this and reach out quickly to communicate rather than making excuses when the project is running behind schedule. They’ll quickly inform you of the timeline for out of scope work and how you can expect those design changes or edits to impact the timeline initially discussed.
\n5. Push for needed items.
\n
Every web developer knows how busy small- to medium-sized businesses can be. With employees taking on multiple job functions and a huge focus on performance, delays in needed items can sometimes occur. Rather than sitting around and waiting (unless they’ve been specifically instructed to do so due to project delays), a qualified and experienced developer will follow up on deadlines for content, images, style elements, and feedback to keep a project running on time. They understand that your goals are important and that sometimes the day to day can get in the way of timely delivery. They’ll push for what they need and try to help you organize it as simply as possible for efficient handoff.
6. Training and support.
\n
Often a website project will launch and additional work will be needed. An employee might find inaccurate data in the website, an important design change may be needed, or marketing and IT staff may need training on how to change and edit the website. An experienced developer will accommodate this by providing a certain number of hours for training, support, and bug fixes for up to a week or two after project launch. They’ll hand-hold the transition and make sure they’re readily available should anything happen or should quick edits need to be made. Your developer shouldn’t ghost you or fail to support their work after the fact.
7. Post-launch feedback timeline.
\n
While a skilled, experienced, reputable HubSpot developer will stand behind their work and assist in the transition and delivery of your website after launch, they’ll also be sure to hold your organization accountable when it comes to edits and bug fixes. They’ll often provide one or two weeks for your point of contact to reach out with any issues that need to be completed or fixed. Once this timeline has expired, there may be a small amount of wiggle room, but generally you should expect to pay for any edits or changes after the agreed-upon delivery deadline. More proactive developers will have already negotiated a growth-driven design retainer of some sort to help ensure that you can continuously improve your website as your marketing evolves.
It is worthwhile to talk about the difference between defects or bug fixes and revisions. This is something that your developer will help you define beforehand and help categorize as they come up. Bug fixes or defects are items that aren’t working properly or weren’t executed correctly by the developer. Revisions are small tweaks that a client may find after the fact for elements that don’t work as well as they expected. For instance, the structure or length of copy or placeholder photos versus actual photos may make the delivered site different from the original design. Revisions will usually cost extra, but this can vary depending on the developer and whether the project came in within scope.
Related reading: the continuous improvement model
\n
Strategy for what’s to come.
\n
Continuous improvement is the next step for any company with a focus on inbound marketing. You’ll probably need to add more landing page templates, additional modules, or new calculators or other widgets as you understand more about the buyer’s journey. The complexity of the information you present will change and you’ll want to be sure that your website is keeping up with the ever-changing needs of your marketing staff. Having a growth-driven design retainer for continual improvement and evolution of your website is important, and your development team should discuss this both before and after launch to help you prepare a budget. This will ensure that your marketing staff continues to be happy with your website on an ongoing basis and avoid those expensive overhauls every three to five years.
Not every company owner, marketing manager, or agency that is outsourcing HubSpot development work knows what to expect or what needs to be done when it comes to a new HubSpot CMS development project. A skilled, experienced developer will have structures in place and communicate the needs and expectations for both their agency and your organization when it comes to delivering the project according to your expectations.
It might take time and it might not always look perfect, but fostering a close relationship with your HubSpot development professional is extremely important to the success of your marketing, the happiness of your employees, and the evolution of your online presence. Do your diligence to qualify any developer you’re vetting. If you need help, we’re always willing to provide a second opinion.
\n\n
Business owners, marketers, and executive teams groan when it comes time for a new website project, and for good reason. It’s rare that a website project (particularly a redesign) stays within a reasonable budget or timeline. As quality HubSpot CMS developers become harder to find, and the biggest agencies continue to run into issues with scaling, a new website project proposal process can seem daunting. If you have only had bad experiences with website builds, what do you need to know to ensure things go more smoothly next time?
Business owners, marketers, and executive teams groan when it comes time for a new website project, and for good reason. It’s rare that a website project (particularly a redesign) stays within a reasonable budget or timeline. As quality HubSpot CMS developers become harder to find, and the biggest agencies continue to run into issues with scaling, a new website project proposal process can seem daunting. If you have only had bad experiences with website builds, what do you need to know to ensure things go more smoothly next time?
Business owners, marketers, and executive teams groan when it comes time for a new website project, and for good reason. It’s rare that a website project (particularly a redesign) stays within a reasonable budget or timeline. As quality HubSpot CMS developers become harder to find, and the biggest agencies continue to run into issues with scaling, a new website project proposal process can seem daunting. If you have only had bad experiences with website builds, what do you need to know to ensure things go more smoothly next time?
Business owners, marketers, and executive teams groan when it comes time for a new website project, and for good reason. It’s rare that a website project (particularly a redesign) stays within a reasonable budget or timeline. As quality HubSpot CMS developers become harder to find, and the biggest agencies continue to run into issues with scaling, a new website project proposal process can seem daunting. If you have only had bad experiences with website builds, what do you need to know to ensure things go more smoothly next time?
Business owners, marketers, and executive teams groan when it comes time for a new website project, and for good reason. It’s rare that a website project (particularly a redesign) stays within a reasonable budget or timeline. As quality HubSpot CMS developers become harder to find, and the biggest agencies continue to run into issues with scaling, a new website project proposal process can seem daunting. If you have only had bad experiences with website builds, what do you need to know to ensure things go more smoothly next time?
Business owners, marketers, and executive teams groan when it comes time for a new website project, and for good reason. It’s rare that a website project (particularly a redesign) stays within a reasonable budget or timeline. As quality HubSpot CMS developers become harder to find, and the biggest agencies continue to run into issues with scaling, a new website project proposal process can seem daunting. If you have only had bad experiences with website builds, what do you need to know to ensure things go more smoothly next time?
We’ve shared the warning signs that it’s time to ditch your current HubSpot developer, but you should also know what to expect when you choose a HubSpot developer. Here are seven things you can expect from a qualified, experienced HubSpot CMS developer when you’re developing a new website project.
1. A projected timeline.
\n
It’s hard to predict exactly when a website will launch, and while the go-live day can change based on any number of factors, setting an approximate timeline or specifying a certain week of the month you expect to finalize the project is more than reasonable. If you have a target date, you can build a for deliverables, including the delivery of the design, sign-off and approval of that design, development of modules, and delivery of a quality-assured and -tested first draft.
Your development partner should break down the timeline and hold you accountable as well, by specifying the date when final first draft edits are needed, as well as having you name a single point of contact to manage all edits on your side. This minimizes the back and forth for last-minute changes to design or afterthought additions to the website. While there are always a few edits and bugs to work out, for the most part once your design is approved and finalized, development should be fairly straightforward.
Be wary of developers promising a very specific launch date or refusing to adjust a launch date based on how the project unfolds. Setting realistic expectations is important, and unless you’ve worked with your developer in the past, it’s unlikely that you’ll meet a set-in-stone launch date. There are a number of variables outside a developer’s control that can affect the ability to launch at an exact date, such as delayed delivery of edits, additional design changes, or out of scope work. While a single-day delay may not impact a launch date, prolonged delays or the accumulation of minor delays can start to put pressure on the developer.
Busy dev agencies typically have their development staff estimated out. If your approvals and content aren’t delivered on time, this could come back to bite you later. Be sure to do your own due diligence and understand that it’s possible you might have played a role in your delayed launch. The ideal developer will work with you and explain that timelines are a guideline or estimate, and the more closely you both do your parts, the closer to that estimate the actual launch will be.
2. A finalized proof.
\n
We recently had a prospect come in whose HubSpot agency was bogged down (link when available). Whether that agency was chronically short staffed or just growing at a super fast pace, the Marketing Manager that we met with was pretty upset about the final draft that was delivered to them. “It’s almost as though they want us to handle the quality control, there were so many bugs and formatting issues. The proof didn’t even look like the agreed-upon design.”
It’s the worst to get clients that are unhappy with the delivery of a project that has such a significant upfront investment —so unhappy that they had to move development agencies to get quality delivered. By delineating the deliverables and responsibilities of each party, a client can easily hold their developer accountable by pointing back to the project timeline and responsibilities outline in order to receive exactly what they expect when it’s time for the final draft to be reviewed.
3. Feedback on your design requests.
\n
We say it a lot, but your developer should be more than an order taker. If you approach your agency with a preconceived design concept and haven’t had a UX/UI expert review it, your web developer should have usability and design feature feedback and suggestions based on your goals. They should be experienced enough in the front and back end of HubSpot CMS to point out potential issues with design and ask detailed questions on your expectations for both the end-user and the marketing team that will be updating content.
A user-friendly interface will allow employees to operate more efficiently and users to find the information they need with ease, increasing conversion rates and selling more products and services. It’s possible you’ve got a great design, but you should very specifically ask your developer for their feedback and suggestions. Their answer will tell a lot about the depth of their expertise and understanding of the relations among marketing, conversion optimization, and development.
Related reading: Your Website Isn’t a Submarine Sandwich
\n4. Accountability and updates.
\n
Sometimes projects run into delays. Whether we’re waiting on access to a third-party application that we’re integrating with the website, your edits are taking longer than expected, or we’ve just run into challenges implementing the design, sometimes projects don’t run on time. Communication is the difference between an experienced, accountable developer and an inexperienced developer who’s bogged down or doesn’t have your best interests in mind.
Your HubSpot developer should have your project mapped out from the start. Any missed milestone has the potential to delay the delivery timeline. An experienced developer will know this and reach out quickly to communicate rather than making excuses when the project is running behind schedule. They’ll quickly inform you of the timeline for out of scope work and how you can expect those design changes or edits to impact the timeline initially discussed.
\n5. Push for needed items.
\n
Every web developer knows how busy small- to medium-sized businesses can be. With employees taking on multiple job functions and a huge focus on performance, delays in needed items can sometimes occur. Rather than sitting around and waiting (unless they’ve been specifically instructed to do so due to project delays), a qualified and experienced developer will follow up on deadlines for content, images, style elements, and feedback to keep a project running on time. They understand that your goals are important and that sometimes the day to day can get in the way of timely delivery. They’ll push for what they need and try to help you organize it as simply as possible for efficient handoff.
6. Training and support.
\n
Often a website project will launch and additional work will be needed. An employee might find inaccurate data in the website, an important design change may be needed, or marketing and IT staff may need training on how to change and edit the website. An experienced developer will accommodate this by providing a certain number of hours for training, support, and bug fixes for up to a week or two after project launch. They’ll hand-hold the transition and make sure they’re readily available should anything happen or should quick edits need to be made. Your developer shouldn’t ghost you or fail to support their work after the fact.
7. Post-launch feedback timeline.
\n
While a skilled, experienced, reputable HubSpot developer will stand behind their work and assist in the transition and delivery of your website after launch, they’ll also be sure to hold your organization accountable when it comes to edits and bug fixes. They’ll often provide one or two weeks for your point of contact to reach out with any issues that need to be completed or fixed. Once this timeline has expired, there may be a small amount of wiggle room, but generally you should expect to pay for any edits or changes after the agreed-upon delivery deadline. More proactive developers will have already negotiated a growth-driven design retainer of some sort to help ensure that you can continuously improve your website as your marketing evolves.
It is worthwhile to talk about the difference between defects or bug fixes and revisions. This is something that your developer will help you define beforehand and help categorize as they come up. Bug fixes or defects are items that aren’t working properly or weren’t executed correctly by the developer. Revisions are small tweaks that a client may find after the fact for elements that don’t work as well as they expected. For instance, the structure or length of copy or placeholder photos versus actual photos may make the delivered site different from the original design. Revisions will usually cost extra, but this can vary depending on the developer and whether the project came in within scope.
Related reading: the continuous improvement model
\n
Strategy for what’s to come.
\n
Continuous improvement is the next step for any company with a focus on inbound marketing. You’ll probably need to add more landing page templates, additional modules, or new calculators or other widgets as you understand more about the buyer’s journey. The complexity of the information you present will change and you’ll want to be sure that your website is keeping up with the ever-changing needs of your marketing staff. Having a growth-driven design retainer for continual improvement and evolution of your website is important, and your development team should discuss this both before and after launch to help you prepare a budget. This will ensure that your marketing staff continues to be happy with your website on an ongoing basis and avoid those expensive overhauls every three to five years.
Not every company owner, marketing manager, or agency that is outsourcing HubSpot development work knows what to expect or what needs to be done when it comes to a new HubSpot CMS development project. A skilled, experienced developer will have structures in place and communicate the needs and expectations for both their agency and your organization when it comes to delivering the project according to your expectations.
It might take time and it might not always look perfect, but fostering a close relationship with your HubSpot development professional is extremely important to the success of your marketing, the happiness of your employees, and the evolution of your online presence. Do your diligence to qualify any developer you’re vetting. If you need help, we’re always willing to provide a second opinion.
\n\n
Business owners, marketers, and executive teams groan when it comes time for a new website project, and for good reason. It’s rare that a website project (particularly a redesign) stays within a reasonable budget or timeline. As quality HubSpot CMS developers become harder to find, and the biggest agencies continue to run into issues with scaling, a new website project proposal process can seem daunting. If you have only had bad experiences with website builds, what do you need to know to ensure things go more smoothly next time?
![\"THAT](\"https://6534445.fs1.hubspotusercontent-na1.net/hubfs/6534445/THAT%20ESCALATED%20QUICKLY-1.jpg\")
We love big HubSpot Partner agencies (and we cannot lie). They inspire us to grow and scale and become the best in our industry. We’ve worked inside their offices and built our expertise through delivering incredible HubSpot projects and making connections that we still value today. We learned how their processes work and how they didn’t work. We have taken that experience and applied it to much of how we run our own HubSpot development agency now.
We see HubSpot case studies from partner agencies and posts on how they’ve grown their revenue by a factor of ten and doubled their staff, and we think, Wow! That’s inspiring, but it sounds like it could be pretty painful! While HubSpot has growth resources for their agency partners, we can’t help but think of the literal growing pains when we were kids; we sometimes couldn’t sleep when our bones grew. There was discomfort, and sometimes a little pain, associated with that growth.
While we love watching the growth of other HubSpot agencies, we’ve also seen the other side of that growth. Several recent prospects have approached us after they’ve found other agencies have let their projects fall through the cracks. Those agencies are encountering problems associated with quick growth, such as overwhelmed staff and quality control issues, which are causing their clients (our new prospects) to suffer.
Here are just a few of the problems fast-growing large HubSpot development agencies encounter. Use them as signs that you, as a small business selecting a HubSpot development agency, can watch out for.
Their talent is sometimes oversold
\n
Top agencies typically garner the top talent — until they don’t. A specialized HubSpot partner soon discovers that not many employees have extensive experience in HubSpot development. While the pool of seasoned HubSpot developers is growing daily, the demand is growing at a far greater pace. An agency might have a few talented, seasoned developers working for it, but the developers cannot keep up with the workload the agency is bringing on, especially if they’re a Diamond or Elite HubSpot Partner that is constantly funneled leads from HubSpot onboarding reps. In addition, those top agencies lose talent as developers go out on their own to become freelancers or open their own HubSpot development agencies. The combination of the deficit in talent and the slowdowns from overworked talent can be felt across the organization.
What to watch for:
\n
A development agency is only as good as its development team, so if they struggle with high turnover or you’re being shifted around to new account reps on the regular, you may want to explore what changes are going on inside the agency. Of course, many agencies run deep in expertise on HubSpot development, typically those whose CEOs and owners are developers themselves: A developer-run agency is often better situated from a depth-of-talent perspective than other agencies.
Check in with the agency and find out where their talent comes from and how they vet their developers, how those developers hone their skills, and what recent projects they’ve completed. Sift through those projects and check load times, bugs, and usability issues to determine how their work is holding up.
Their team is underpaid
\n
Here’s the real truth when it comes to agency life: Developers are not always compensated properly. I said what I said. One of the reasons our owner left the majority of the agencies that he worked within was a heavy workload and compensation that wasn’t commensurate with expertise. It’s a difficult position to be in, as an agency, since clients can be sensitive when it comes to billable time and per-hour billable rates. But as in almost every aspect of life, you get what you pay for. If a client isn’t paying a significant monthly fee, you can almost guarantee that their talent is subpar or very underpaid (and likely to leave).
What to watch for:
\n
Agencies that are willing to discount their hourly rates significantly can only afford to do so because they either have lower overhead or they’re paying their teams much less than they’re charging for margins. If they also charge a low hourly rate to begin with, they’re probably outsourcing work to inexperienced developers who may not be qualified to cleanly code and develop with a lot of intention inside the HubSpot CMS.
Related: The Problem with Cheap Outsourced Web Development
\n\n
Their team is overwhelmed
\n
When becoming a HubSpot partner and the associated boost in lead generation result in a tenfold revenue growth or the doubling of staff, you can almost guarantee that teams are overwhelmed. When a lot of new employees are introduced, new team structures are established, or new clients are assigned to existing teams (which, let’s face it, is a major issue during this widespread period of \"employee shortages\"), developers will be overwhelmed with a massive amount of work. Overwhelmed and unhappy employees are 10% less productive. We probably don’t need to go over how unproductive employees affect the client experience, but there’s a lot of research out there: Dissatisfied employees are two and a half times more likely to say they do not provide excellent customer service and twice as likely to say they do not deliver quality outcomes.
What to watch for:
\n
Many prospects approach us with partially developed websites. Quality assurance is among the most important aspects of our delivery and launch process at deckerdevs. If you notice that you’re approaching the finish line with your project and running into an alarming number of unresolved issues that your development team didn’t seem to catch, this may be a red flag. If you’re not hearing back from your account executive or developer, or it's taking days or weeks to get changes completed, these are also signs that their teams are overwhelmed.
Their team has underwhelming skills
\n
From slowly loading pages to poorly coded sites to ill-conceived resource centers to hard-coded modules and lots of bugs and script errors: We’ve seen a lot of things that you should never see coming from big agencies. People paying the premiums that the biggest HubSpot agencies get deserve better. The executive teams at those agencies probably agree.
What to watch for:
\n
Red flags include buggy websites, rationalizing why a new feature can’t be added, slow-loading pages, minimal feedback from a usability perspective, and stopping work once the project is done. We have long-standing relationships with all our clients to execute projects on their behalf long after a project is completed, whether it’s a single module edit or a full website overhaul. We work closely with clients to determine the best balance between their budget and wishlist, then execute properly with infrastructure that is proven to make things easy for the client.
With such a huge talent gap when it comes to HubSpot CMS developers, it’s important that you do your homework when you’re interviewing development agencies.
\n\n
To avoid these issues, during the sales process, ask who is developing your project; you can even request that you have some face time with the developer. While not all developers are able to meet with clients, depending on the agency, you can at least gain some knowledge and ask the agency for developer references, past projects, and the amount of time they’ve been working in the HubSpot CMS.
\n\n
Hiring an agency with a CEO or owner who has a lot of experience in HubSpot development is critical as well. Ask them about their process, what you should expect, the anticipated timeline, what their expectations are from you, how they’ll be handling bugs, what the QA process is, and how long they’ll support their project post-launch. You’ll also want to understand what happens if you decide the relationship isn’t working out: A lot of bigger agencies have iron-clad agreements that can be difficult to exit.
\n\n
While the majority of the experiences from the biggest HubSpot development agencies are positive, we want you to be as prepared as you can be when you’re interviewing prospective agencies. The more you know and the more questions you ask, the easier it might be to avoid potential issues down the line. While we always love to be the ones to fix any problem we’re approached with, we’d much rather you have the right experience the first time around.
\n\n
\n
","rss_summary":"
We love big HubSpot Partner agencies (and we cannot lie). They inspire us to grow and scale and become the best in our industry. We’ve worked inside their offices and built our expertise through delivering incredible HubSpot projects and making connections that we still value today. We learned how their processes work and how they didn’t work. We have taken that experience and applied it to much of how we run our own HubSpot development agency now.
We see HubSpot case studies from partner agencies and posts on how they’ve grown their revenue by a factor of ten and doubled their staff, and we think, Wow! That’s inspiring, but it sounds like it could be pretty painful! While HubSpot has growth resources for their agency partners, we can’t help but think of the literal growing pains when we were kids; we sometimes couldn’t sleep when our bones grew. There was discomfort, and sometimes a little pain, associated with that growth.
While we love watching the growth of other HubSpot agencies, we’ve also seen the other side of that growth. Several recent prospects have approached us after they’ve found other agencies have let their projects fall through the cracks. Those agencies are encountering problems associated with quick growth, such as overwhelmed staff and quality control issues, which are causing their clients (our new prospects) to suffer.
Here are just a few of the problems fast-growing large HubSpot development agencies encounter. Use them as signs that you, as a small business selecting a HubSpot development agency, can watch out for.
We love big HubSpot Partner agencies (and we cannot lie). They inspire us to grow and scale and become the best in our industry. We’ve worked inside their offices and built our expertise through delivering incredible HubSpot projects and making connections that we still value today. We learned how their processes work and how they didn’t work. We have taken that experience and applied it to much of how we run our own HubSpot development agency now.
We see HubSpot case studies from partner agencies and posts on how they’ve grown their revenue by a factor of ten and doubled their staff, and we think, Wow! That’s inspiring, but it sounds like it could be pretty painful! While HubSpot has growth resources for their agency partners, we can’t help but think of the literal growing pains when we were kids; we sometimes couldn’t sleep when our bones grew. There was discomfort, and sometimes a little pain, associated with that growth.
While we love watching the growth of other HubSpot agencies, we’ve also seen the other side of that growth. Several recent prospects have approached us after they’ve found other agencies have let their projects fall through the cracks. Those agencies are encountering problems associated with quick growth, such as overwhelmed staff and quality control issues, which are causing their clients (our new prospects) to suffer.
Here are just a few of the problems fast-growing large HubSpot development agencies encounter. Use them as signs that you, as a small business selecting a HubSpot development agency, can watch out for.
Their talent is sometimes oversold
\n
Top agencies typically garner the top talent — until they don’t. A specialized HubSpot partner soon discovers that not many employees have extensive experience in HubSpot development. While the pool of seasoned HubSpot developers is growing daily, the demand is growing at a far greater pace. An agency might have a few talented, seasoned developers working for it, but the developers cannot keep up with the workload the agency is bringing on, especially if they’re a Diamond or Elite HubSpot Partner that is constantly funneled leads from HubSpot onboarding reps. In addition, those top agencies lose talent as developers go out on their own to become freelancers or open their own HubSpot development agencies. The combination of the deficit in talent and the slowdowns from overworked talent can be felt across the organization.
What to watch for:
\n
A development agency is only as good as its development team, so if they struggle with high turnover or you’re being shifted around to new account reps on the regular, you may want to explore what changes are going on inside the agency. Of course, many agencies run deep in expertise on HubSpot development, typically those whose CEOs and owners are developers themselves: A developer-run agency is often better situated from a depth-of-talent perspective than other agencies.
Check in with the agency and find out where their talent comes from and how they vet their developers, how those developers hone their skills, and what recent projects they’ve completed. Sift through those projects and check load times, bugs, and usability issues to determine how their work is holding up.
Their team is underpaid
\n
Here’s the real truth when it comes to agency life: Developers are not always compensated properly. I said what I said. One of the reasons our owner left the majority of the agencies that he worked within was a heavy workload and compensation that wasn’t commensurate with expertise. It’s a difficult position to be in, as an agency, since clients can be sensitive when it comes to billable time and per-hour billable rates. But as in almost every aspect of life, you get what you pay for. If a client isn’t paying a significant monthly fee, you can almost guarantee that their talent is subpar or very underpaid (and likely to leave).
What to watch for:
\n
Agencies that are willing to discount their hourly rates significantly can only afford to do so because they either have lower overhead or they’re paying their teams much less than they’re charging for margins. If they also charge a low hourly rate to begin with, they’re probably outsourcing work to inexperienced developers who may not be qualified to cleanly code and develop with a lot of intention inside the HubSpot CMS.
Related: The Problem with Cheap Outsourced Web Development
\n\n
Their team is overwhelmed
\n
When becoming a HubSpot partner and the associated boost in lead generation result in a tenfold revenue growth or the doubling of staff, you can almost guarantee that teams are overwhelmed. When a lot of new employees are introduced, new team structures are established, or new clients are assigned to existing teams (which, let’s face it, is a major issue during this widespread period of \"employee shortages\"), developers will be overwhelmed with a massive amount of work. Overwhelmed and unhappy employees are 10% less productive. We probably don’t need to go over how unproductive employees affect the client experience, but there’s a lot of research out there: Dissatisfied employees are two and a half times more likely to say they do not provide excellent customer service and twice as likely to say they do not deliver quality outcomes.
What to watch for:
\n
Many prospects approach us with partially developed websites. Quality assurance is among the most important aspects of our delivery and launch process at deckerdevs. If you notice that you’re approaching the finish line with your project and running into an alarming number of unresolved issues that your development team didn’t seem to catch, this may be a red flag. If you’re not hearing back from your account executive or developer, or it's taking days or weeks to get changes completed, these are also signs that their teams are overwhelmed.
Their team has underwhelming skills
\n
From slowly loading pages to poorly coded sites to ill-conceived resource centers to hard-coded modules and lots of bugs and script errors: We’ve seen a lot of things that you should never see coming from big agencies. People paying the premiums that the biggest HubSpot agencies get deserve better. The executive teams at those agencies probably agree.
What to watch for:
\n
Red flags include buggy websites, rationalizing why a new feature can’t be added, slow-loading pages, minimal feedback from a usability perspective, and stopping work once the project is done. We have long-standing relationships with all our clients to execute projects on their behalf long after a project is completed, whether it’s a single module edit or a full website overhaul. We work closely with clients to determine the best balance between their budget and wishlist, then execute properly with infrastructure that is proven to make things easy for the client.
With such a huge talent gap when it comes to HubSpot CMS developers, it’s important that you do your homework when you’re interviewing development agencies.
\n\n
To avoid these issues, during the sales process, ask who is developing your project; you can even request that you have some face time with the developer. While not all developers are able to meet with clients, depending on the agency, you can at least gain some knowledge and ask the agency for developer references, past projects, and the amount of time they’ve been working in the HubSpot CMS.
\n\n
Hiring an agency with a CEO or owner who has a lot of experience in HubSpot development is critical as well. Ask them about their process, what you should expect, the anticipated timeline, what their expectations are from you, how they’ll be handling bugs, what the QA process is, and how long they’ll support their project post-launch. You’ll also want to understand what happens if you decide the relationship isn’t working out: A lot of bigger agencies have iron-clad agreements that can be difficult to exit.
\n\n
While the majority of the experiences from the biggest HubSpot development agencies are positive, we want you to be as prepared as you can be when you’re interviewing prospective agencies. The more you know and the more questions you ask, the easier it might be to avoid potential issues down the line. While we always love to be the ones to fix any problem we’re approached with, we’d much rather you have the right experience the first time around.
\n\n
\n
","tag_ids":[62770442823,78562833827],"topic_ids":[62770442823,78562833827],"post_summary":"
We love big HubSpot Partner agencies (and we cannot lie). They inspire us to grow and scale and become the best in our industry. We’ve worked inside their offices and built our expertise through delivering incredible HubSpot projects and making connections that we still value today. We learned how their processes work and how they didn’t work. We have taken that experience and applied it to much of how we run our own HubSpot development agency now.
We see HubSpot case studies from partner agencies and posts on how they’ve grown their revenue by a factor of ten and doubled their staff, and we think, Wow! That’s inspiring, but it sounds like it could be pretty painful! While HubSpot has growth resources for their agency partners, we can’t help but think of the literal growing pains when we were kids; we sometimes couldn’t sleep when our bones grew. There was discomfort, and sometimes a little pain, associated with that growth.
While we love watching the growth of other HubSpot agencies, we’ve also seen the other side of that growth. Several recent prospects have approached us after they’ve found other agencies have let their projects fall through the cracks. Those agencies are encountering problems associated with quick growth, such as overwhelmed staff and quality control issues, which are causing their clients (our new prospects) to suffer.
Here are just a few of the problems fast-growing large HubSpot development agencies encounter. Use them as signs that you, as a small business selecting a HubSpot development agency, can watch out for.
We love big HubSpot Partner agencies (and we cannot lie). They inspire us to grow and scale and become the best in our industry. We’ve worked inside their offices and built our expertise through delivering incredible HubSpot projects and making connections that we still value today. We learned how their processes work and how they didn’t work. We have taken that experience and applied it to much of how we run our own HubSpot development agency now.
We see HubSpot case studies from partner agencies and posts on how they’ve grown their revenue by a factor of ten and doubled their staff, and we think, Wow! That’s inspiring, but it sounds like it could be pretty painful! While HubSpot has growth resources for their agency partners, we can’t help but think of the literal growing pains when we were kids; we sometimes couldn’t sleep when our bones grew. There was discomfort, and sometimes a little pain, associated with that growth.
While we love watching the growth of other HubSpot agencies, we’ve also seen the other side of that growth. Several recent prospects have approached us after they’ve found other agencies have let their projects fall through the cracks. Those agencies are encountering problems associated with quick growth, such as overwhelmed staff and quality control issues, which are causing their clients (our new prospects) to suffer.
Here are just a few of the problems fast-growing large HubSpot development agencies encounter. Use them as signs that you, as a small business selecting a HubSpot development agency, can watch out for.
Their talent is sometimes oversold
\n
Top agencies typically garner the top talent — until they don’t. A specialized HubSpot partner soon discovers that not many employees have extensive experience in HubSpot development. While the pool of seasoned HubSpot developers is growing daily, the demand is growing at a far greater pace. An agency might have a few talented, seasoned developers working for it, but the developers cannot keep up with the workload the agency is bringing on, especially if they’re a Diamond or Elite HubSpot Partner that is constantly funneled leads from HubSpot onboarding reps. In addition, those top agencies lose talent as developers go out on their own to become freelancers or open their own HubSpot development agencies. The combination of the deficit in talent and the slowdowns from overworked talent can be felt across the organization.
What to watch for:
\n
A development agency is only as good as its development team, so if they struggle with high turnover or you’re being shifted around to new account reps on the regular, you may want to explore what changes are going on inside the agency. Of course, many agencies run deep in expertise on HubSpot development, typically those whose CEOs and owners are developers themselves: A developer-run agency is often better situated from a depth-of-talent perspective than other agencies.
Check in with the agency and find out where their talent comes from and how they vet their developers, how those developers hone their skills, and what recent projects they’ve completed. Sift through those projects and check load times, bugs, and usability issues to determine how their work is holding up.
Their team is underpaid
\n
Here’s the real truth when it comes to agency life: Developers are not always compensated properly. I said what I said. One of the reasons our owner left the majority of the agencies that he worked within was a heavy workload and compensation that wasn’t commensurate with expertise. It’s a difficult position to be in, as an agency, since clients can be sensitive when it comes to billable time and per-hour billable rates. But as in almost every aspect of life, you get what you pay for. If a client isn’t paying a significant monthly fee, you can almost guarantee that their talent is subpar or very underpaid (and likely to leave).
What to watch for:
\n
Agencies that are willing to discount their hourly rates significantly can only afford to do so because they either have lower overhead or they’re paying their teams much less than they’re charging for margins. If they also charge a low hourly rate to begin with, they’re probably outsourcing work to inexperienced developers who may not be qualified to cleanly code and develop with a lot of intention inside the HubSpot CMS.
Related: The Problem with Cheap Outsourced Web Development
\n\n
Their team is overwhelmed
\n
When becoming a HubSpot partner and the associated boost in lead generation result in a tenfold revenue growth or the doubling of staff, you can almost guarantee that teams are overwhelmed. When a lot of new employees are introduced, new team structures are established, or new clients are assigned to existing teams (which, let’s face it, is a major issue during this widespread period of \"employee shortages\"), developers will be overwhelmed with a massive amount of work. Overwhelmed and unhappy employees are 10% less productive. We probably don’t need to go over how unproductive employees affect the client experience, but there’s a lot of research out there: Dissatisfied employees are two and a half times more likely to say they do not provide excellent customer service and twice as likely to say they do not deliver quality outcomes.
What to watch for:
\n
Many prospects approach us with partially developed websites. Quality assurance is among the most important aspects of our delivery and launch process at deckerdevs. If you notice that you’re approaching the finish line with your project and running into an alarming number of unresolved issues that your development team didn’t seem to catch, this may be a red flag. If you’re not hearing back from your account executive or developer, or it's taking days or weeks to get changes completed, these are also signs that their teams are overwhelmed.
Their team has underwhelming skills
\n
From slowly loading pages to poorly coded sites to ill-conceived resource centers to hard-coded modules and lots of bugs and script errors: We’ve seen a lot of things that you should never see coming from big agencies. People paying the premiums that the biggest HubSpot agencies get deserve better. The executive teams at those agencies probably agree.
What to watch for:
\n
Red flags include buggy websites, rationalizing why a new feature can’t be added, slow-loading pages, minimal feedback from a usability perspective, and stopping work once the project is done. We have long-standing relationships with all our clients to execute projects on their behalf long after a project is completed, whether it’s a single module edit or a full website overhaul. We work closely with clients to determine the best balance between their budget and wishlist, then execute properly with infrastructure that is proven to make things easy for the client.
With such a huge talent gap when it comes to HubSpot CMS developers, it’s important that you do your homework when you’re interviewing development agencies.
\n\n
To avoid these issues, during the sales process, ask who is developing your project; you can even request that you have some face time with the developer. While not all developers are able to meet with clients, depending on the agency, you can at least gain some knowledge and ask the agency for developer references, past projects, and the amount of time they’ve been working in the HubSpot CMS.
\n\n
Hiring an agency with a CEO or owner who has a lot of experience in HubSpot development is critical as well. Ask them about their process, what you should expect, the anticipated timeline, what their expectations are from you, how they’ll be handling bugs, what the QA process is, and how long they’ll support their project post-launch. You’ll also want to understand what happens if you decide the relationship isn’t working out: A lot of bigger agencies have iron-clad agreements that can be difficult to exit.
\n\n
While the majority of the experiences from the biggest HubSpot development agencies are positive, we want you to be as prepared as you can be when you’re interviewing prospective agencies. The more you know and the more questions you ask, the easier it might be to avoid potential issues down the line. While we always love to be the ones to fix any problem we’re approached with, we’d much rather you have the right experience the first time around.
\n\n
\n
","postBodyRss":"
We love big HubSpot Partner agencies (and we cannot lie). They inspire us to grow and scale and become the best in our industry. We’ve worked inside their offices and built our expertise through delivering incredible HubSpot projects and making connections that we still value today. We learned how their processes work and how they didn’t work. We have taken that experience and applied it to much of how we run our own HubSpot development agency now.
We see HubSpot case studies from partner agencies and posts on how they’ve grown their revenue by a factor of ten and doubled their staff, and we think, Wow! That’s inspiring, but it sounds like it could be pretty painful! While HubSpot has growth resources for their agency partners, we can’t help but think of the literal growing pains when we were kids; we sometimes couldn’t sleep when our bones grew. There was discomfort, and sometimes a little pain, associated with that growth.
While we love watching the growth of other HubSpot agencies, we’ve also seen the other side of that growth. Several recent prospects have approached us after they’ve found other agencies have let their projects fall through the cracks. Those agencies are encountering problems associated with quick growth, such as overwhelmed staff and quality control issues, which are causing their clients (our new prospects) to suffer.
Here are just a few of the problems fast-growing large HubSpot development agencies encounter. Use them as signs that you, as a small business selecting a HubSpot development agency, can watch out for.
Their talent is sometimes oversold
\n
Top agencies typically garner the top talent — until they don’t. A specialized HubSpot partner soon discovers that not many employees have extensive experience in HubSpot development. While the pool of seasoned HubSpot developers is growing daily, the demand is growing at a far greater pace. An agency might have a few talented, seasoned developers working for it, but the developers cannot keep up with the workload the agency is bringing on, especially if they’re a Diamond or Elite HubSpot Partner that is constantly funneled leads from HubSpot onboarding reps. In addition, those top agencies lose talent as developers go out on their own to become freelancers or open their own HubSpot development agencies. The combination of the deficit in talent and the slowdowns from overworked talent can be felt across the organization.
What to watch for:
\n
A development agency is only as good as its development team, so if they struggle with high turnover or you’re being shifted around to new account reps on the regular, you may want to explore what changes are going on inside the agency. Of course, many agencies run deep in expertise on HubSpot development, typically those whose CEOs and owners are developers themselves: A developer-run agency is often better situated from a depth-of-talent perspective than other agencies.
Check in with the agency and find out where their talent comes from and how they vet their developers, how those developers hone their skills, and what recent projects they’ve completed. Sift through those projects and check load times, bugs, and usability issues to determine how their work is holding up.
Their team is underpaid
\n
Here’s the real truth when it comes to agency life: Developers are not always compensated properly. I said what I said. One of the reasons our owner left the majority of the agencies that he worked within was a heavy workload and compensation that wasn’t commensurate with expertise. It’s a difficult position to be in, as an agency, since clients can be sensitive when it comes to billable time and per-hour billable rates. But as in almost every aspect of life, you get what you pay for. If a client isn’t paying a significant monthly fee, you can almost guarantee that their talent is subpar or very underpaid (and likely to leave).
What to watch for:
\n
Agencies that are willing to discount their hourly rates significantly can only afford to do so because they either have lower overhead or they’re paying their teams much less than they’re charging for margins. If they also charge a low hourly rate to begin with, they’re probably outsourcing work to inexperienced developers who may not be qualified to cleanly code and develop with a lot of intention inside the HubSpot CMS.
Related: The Problem with Cheap Outsourced Web Development
\n\n
Their team is overwhelmed
\n
When becoming a HubSpot partner and the associated boost in lead generation result in a tenfold revenue growth or the doubling of staff, you can almost guarantee that teams are overwhelmed. When a lot of new employees are introduced, new team structures are established, or new clients are assigned to existing teams (which, let’s face it, is a major issue during this widespread period of \"employee shortages\"), developers will be overwhelmed with a massive amount of work. Overwhelmed and unhappy employees are 10% less productive. We probably don’t need to go over how unproductive employees affect the client experience, but there’s a lot of research out there: Dissatisfied employees are two and a half times more likely to say they do not provide excellent customer service and twice as likely to say they do not deliver quality outcomes.
What to watch for:
\n
Many prospects approach us with partially developed websites. Quality assurance is among the most important aspects of our delivery and launch process at deckerdevs. If you notice that you’re approaching the finish line with your project and running into an alarming number of unresolved issues that your development team didn’t seem to catch, this may be a red flag. If you’re not hearing back from your account executive or developer, or it's taking days or weeks to get changes completed, these are also signs that their teams are overwhelmed.
Their team has underwhelming skills
\n
From slowly loading pages to poorly coded sites to ill-conceived resource centers to hard-coded modules and lots of bugs and script errors: We’ve seen a lot of things that you should never see coming from big agencies. People paying the premiums that the biggest HubSpot agencies get deserve better. The executive teams at those agencies probably agree.
What to watch for:
\n
Red flags include buggy websites, rationalizing why a new feature can’t be added, slow-loading pages, minimal feedback from a usability perspective, and stopping work once the project is done. We have long-standing relationships with all our clients to execute projects on their behalf long after a project is completed, whether it’s a single module edit or a full website overhaul. We work closely with clients to determine the best balance between their budget and wishlist, then execute properly with infrastructure that is proven to make things easy for the client.
With such a huge talent gap when it comes to HubSpot CMS developers, it’s important that you do your homework when you’re interviewing development agencies.
\n\n
To avoid these issues, during the sales process, ask who is developing your project; you can even request that you have some face time with the developer. While not all developers are able to meet with clients, depending on the agency, you can at least gain some knowledge and ask the agency for developer references, past projects, and the amount of time they’ve been working in the HubSpot CMS.
\n\n
Hiring an agency with a CEO or owner who has a lot of experience in HubSpot development is critical as well. Ask them about their process, what you should expect, the anticipated timeline, what their expectations are from you, how they’ll be handling bugs, what the QA process is, and how long they’ll support their project post-launch. You’ll also want to understand what happens if you decide the relationship isn’t working out: A lot of bigger agencies have iron-clad agreements that can be difficult to exit.
\n\n
While the majority of the experiences from the biggest HubSpot development agencies are positive, we want you to be as prepared as you can be when you’re interviewing prospective agencies. The more you know and the more questions you ask, the easier it might be to avoid potential issues down the line. While we always love to be the ones to fix any problem we’re approached with, we’d much rather you have the right experience the first time around.
\n\n
\n
","postEmailContent":"
We love big HubSpot Partner agencies (and we cannot lie). They inspire us to grow and scale and become the best in our industry. We’ve worked inside their offices and built our expertise through delivering incredible HubSpot projects and making connections that we still value today. We learned how their processes work and how they didn’t work. We have taken that experience and applied it to much of how we run our own HubSpot development agency now.
We see HubSpot case studies from partner agencies and posts on how they’ve grown their revenue by a factor of ten and doubled their staff, and we think, Wow! That’s inspiring, but it sounds like it could be pretty painful! While HubSpot has growth resources for their agency partners, we can’t help but think of the literal growing pains when we were kids; we sometimes couldn’t sleep when our bones grew. There was discomfort, and sometimes a little pain, associated with that growth.
While we love watching the growth of other HubSpot agencies, we’ve also seen the other side of that growth. Several recent prospects have approached us after they’ve found other agencies have let their projects fall through the cracks. Those agencies are encountering problems associated with quick growth, such as overwhelmed staff and quality control issues, which are causing their clients (our new prospects) to suffer.
Here are just a few of the problems fast-growing large HubSpot development agencies encounter. Use them as signs that you, as a small business selecting a HubSpot development agency, can watch out for.
We love big HubSpot Partner agencies (and we cannot lie). They inspire us to grow and scale and become the best in our industry. We’ve worked inside their offices and built our expertise through delivering incredible HubSpot projects and making connections that we still value today. We learned how their processes work and how they didn’t work. We have taken that experience and applied it to much of how we run our own HubSpot development agency now.
We see HubSpot case studies from partner agencies and posts on how they’ve grown their revenue by a factor of ten and doubled their staff, and we think, Wow! That’s inspiring, but it sounds like it could be pretty painful! While HubSpot has growth resources for their agency partners, we can’t help but think of the literal growing pains when we were kids; we sometimes couldn’t sleep when our bones grew. There was discomfort, and sometimes a little pain, associated with that growth.
While we love watching the growth of other HubSpot agencies, we’ve also seen the other side of that growth. Several recent prospects have approached us after they’ve found other agencies have let their projects fall through the cracks. Those agencies are encountering problems associated with quick growth, such as overwhelmed staff and quality control issues, which are causing their clients (our new prospects) to suffer.
Here are just a few of the problems fast-growing large HubSpot development agencies encounter. Use them as signs that you, as a small business selecting a HubSpot development agency, can watch out for.
We love big HubSpot Partner agencies (and we cannot lie). They inspire us to grow and scale and become the best in our industry. We’ve worked inside their offices and built our expertise through delivering incredible HubSpot projects and making connections that we still value today. We learned how their processes work and how they didn’t work. We have taken that experience and applied it to much of how we run our own HubSpot development agency now.
We see HubSpot case studies from partner agencies and posts on how they’ve grown their revenue by a factor of ten and doubled their staff, and we think, Wow! That’s inspiring, but it sounds like it could be pretty painful! While HubSpot has growth resources for their agency partners, we can’t help but think of the literal growing pains when we were kids; we sometimes couldn’t sleep when our bones grew. There was discomfort, and sometimes a little pain, associated with that growth.
While we love watching the growth of other HubSpot agencies, we’ve also seen the other side of that growth. Several recent prospects have approached us after they’ve found other agencies have let their projects fall through the cracks. Those agencies are encountering problems associated with quick growth, such as overwhelmed staff and quality control issues, which are causing their clients (our new prospects) to suffer.
Here are just a few of the problems fast-growing large HubSpot development agencies encounter. Use them as signs that you, as a small business selecting a HubSpot development agency, can watch out for.
We love big HubSpot Partner agencies (and we cannot lie). They inspire us to grow and scale and become the best in our industry. We’ve worked inside their offices and built our expertise through delivering incredible HubSpot projects and making connections that we still value today. We learned how their processes work and how they didn’t work. We have taken that experience and applied it to much of how we run our own HubSpot development agency now.
We see HubSpot case studies from partner agencies and posts on how they’ve grown their revenue by a factor of ten and doubled their staff, and we think, Wow! That’s inspiring, but it sounds like it could be pretty painful! While HubSpot has growth resources for their agency partners, we can’t help but think of the literal growing pains when we were kids; we sometimes couldn’t sleep when our bones grew. There was discomfort, and sometimes a little pain, associated with that growth.
While we love watching the growth of other HubSpot agencies, we’ve also seen the other side of that growth. Several recent prospects have approached us after they’ve found other agencies have let their projects fall through the cracks. Those agencies are encountering problems associated with quick growth, such as overwhelmed staff and quality control issues, which are causing their clients (our new prospects) to suffer.
Here are just a few of the problems fast-growing large HubSpot development agencies encounter. Use them as signs that you, as a small business selecting a HubSpot development agency, can watch out for.
We love big HubSpot Partner agencies (and we cannot lie). They inspire us to grow and scale and become the best in our industry. We’ve worked inside their offices and built our expertise through delivering incredible HubSpot projects and making connections that we still value today. We learned how their processes work and how they didn’t work. We have taken that experience and applied it to much of how we run our own HubSpot development agency now.
We see HubSpot case studies from partner agencies and posts on how they’ve grown their revenue by a factor of ten and doubled their staff, and we think, Wow! That’s inspiring, but it sounds like it could be pretty painful! While HubSpot has growth resources for their agency partners, we can’t help but think of the literal growing pains when we were kids; we sometimes couldn’t sleep when our bones grew. There was discomfort, and sometimes a little pain, associated with that growth.
While we love watching the growth of other HubSpot agencies, we’ve also seen the other side of that growth. Several recent prospects have approached us after they’ve found other agencies have let their projects fall through the cracks. Those agencies are encountering problems associated with quick growth, such as overwhelmed staff and quality control issues, which are causing their clients (our new prospects) to suffer.
Here are just a few of the problems fast-growing large HubSpot development agencies encounter. Use them as signs that you, as a small business selecting a HubSpot development agency, can watch out for.
We love big HubSpot Partner agencies (and we cannot lie). They inspire us to grow and scale and become the best in our industry. We’ve worked inside their offices and built our expertise through delivering incredible HubSpot projects and making connections that we still value today. We learned how their processes work and how they didn’t work. We have taken that experience and applied it to much of how we run our own HubSpot development agency now.
We see HubSpot case studies from partner agencies and posts on how they’ve grown their revenue by a factor of ten and doubled their staff, and we think, Wow! That’s inspiring, but it sounds like it could be pretty painful! While HubSpot has growth resources for their agency partners, we can’t help but think of the literal growing pains when we were kids; we sometimes couldn’t sleep when our bones grew. There was discomfort, and sometimes a little pain, associated with that growth.
While we love watching the growth of other HubSpot agencies, we’ve also seen the other side of that growth. Several recent prospects have approached us after they’ve found other agencies have let their projects fall through the cracks. Those agencies are encountering problems associated with quick growth, such as overwhelmed staff and quality control issues, which are causing their clients (our new prospects) to suffer.
Here are just a few of the problems fast-growing large HubSpot development agencies encounter. Use them as signs that you, as a small business selecting a HubSpot development agency, can watch out for.
Their talent is sometimes oversold
\n
Top agencies typically garner the top talent — until they don’t. A specialized HubSpot partner soon discovers that not many employees have extensive experience in HubSpot development. While the pool of seasoned HubSpot developers is growing daily, the demand is growing at a far greater pace. An agency might have a few talented, seasoned developers working for it, but the developers cannot keep up with the workload the agency is bringing on, especially if they’re a Diamond or Elite HubSpot Partner that is constantly funneled leads from HubSpot onboarding reps. In addition, those top agencies lose talent as developers go out on their own to become freelancers or open their own HubSpot development agencies. The combination of the deficit in talent and the slowdowns from overworked talent can be felt across the organization.
What to watch for:
\n
A development agency is only as good as its development team, so if they struggle with high turnover or you’re being shifted around to new account reps on the regular, you may want to explore what changes are going on inside the agency. Of course, many agencies run deep in expertise on HubSpot development, typically those whose CEOs and owners are developers themselves: A developer-run agency is often better situated from a depth-of-talent perspective than other agencies.
Check in with the agency and find out where their talent comes from and how they vet their developers, how those developers hone their skills, and what recent projects they’ve completed. Sift through those projects and check load times, bugs, and usability issues to determine how their work is holding up.
Their team is underpaid
\n
Here’s the real truth when it comes to agency life: Developers are not always compensated properly. I said what I said. One of the reasons our owner left the majority of the agencies that he worked within was a heavy workload and compensation that wasn’t commensurate with expertise. It’s a difficult position to be in, as an agency, since clients can be sensitive when it comes to billable time and per-hour billable rates. But as in almost every aspect of life, you get what you pay for. If a client isn’t paying a significant monthly fee, you can almost guarantee that their talent is subpar or very underpaid (and likely to leave).
What to watch for:
\n
Agencies that are willing to discount their hourly rates significantly can only afford to do so because they either have lower overhead or they’re paying their teams much less than they’re charging for margins. If they also charge a low hourly rate to begin with, they’re probably outsourcing work to inexperienced developers who may not be qualified to cleanly code and develop with a lot of intention inside the HubSpot CMS.
Related: The Problem with Cheap Outsourced Web Development
\n\n
Their team is overwhelmed
\n
When becoming a HubSpot partner and the associated boost in lead generation result in a tenfold revenue growth or the doubling of staff, you can almost guarantee that teams are overwhelmed. When a lot of new employees are introduced, new team structures are established, or new clients are assigned to existing teams (which, let’s face it, is a major issue during this widespread period of \"employee shortages\"), developers will be overwhelmed with a massive amount of work. Overwhelmed and unhappy employees are 10% less productive. We probably don’t need to go over how unproductive employees affect the client experience, but there’s a lot of research out there: Dissatisfied employees are two and a half times more likely to say they do not provide excellent customer service and twice as likely to say they do not deliver quality outcomes.
What to watch for:
\n
Many prospects approach us with partially developed websites. Quality assurance is among the most important aspects of our delivery and launch process at deckerdevs. If you notice that you’re approaching the finish line with your project and running into an alarming number of unresolved issues that your development team didn’t seem to catch, this may be a red flag. If you’re not hearing back from your account executive or developer, or it's taking days or weeks to get changes completed, these are also signs that their teams are overwhelmed.
Their team has underwhelming skills
\n
From slowly loading pages to poorly coded sites to ill-conceived resource centers to hard-coded modules and lots of bugs and script errors: We’ve seen a lot of things that you should never see coming from big agencies. People paying the premiums that the biggest HubSpot agencies get deserve better. The executive teams at those agencies probably agree.
What to watch for:
\n
Red flags include buggy websites, rationalizing why a new feature can’t be added, slow-loading pages, minimal feedback from a usability perspective, and stopping work once the project is done. We have long-standing relationships with all our clients to execute projects on their behalf long after a project is completed, whether it’s a single module edit or a full website overhaul. We work closely with clients to determine the best balance between their budget and wishlist, then execute properly with infrastructure that is proven to make things easy for the client.
With such a huge talent gap when it comes to HubSpot CMS developers, it’s important that you do your homework when you’re interviewing development agencies.
\n\n
To avoid these issues, during the sales process, ask who is developing your project; you can even request that you have some face time with the developer. While not all developers are able to meet with clients, depending on the agency, you can at least gain some knowledge and ask the agency for developer references, past projects, and the amount of time they’ve been working in the HubSpot CMS.
\n\n
Hiring an agency with a CEO or owner who has a lot of experience in HubSpot development is critical as well. Ask them about their process, what you should expect, the anticipated timeline, what their expectations are from you, how they’ll be handling bugs, what the QA process is, and how long they’ll support their project post-launch. You’ll also want to understand what happens if you decide the relationship isn’t working out: A lot of bigger agencies have iron-clad agreements that can be difficult to exit.
\n\n
While the majority of the experiences from the biggest HubSpot development agencies are positive, we want you to be as prepared as you can be when you’re interviewing prospective agencies. The more you know and the more questions you ask, the easier it might be to avoid potential issues down the line. While we always love to be the ones to fix any problem we’re approached with, we’d much rather you have the right experience the first time around.
\n\n
\n
","rssSummary":"
We love big HubSpot Partner agencies (and we cannot lie). They inspire us to grow and scale and become the best in our industry. We’ve worked inside their offices and built our expertise through delivering incredible HubSpot projects and making connections that we still value today. We learned how their processes work and how they didn’t work. We have taken that experience and applied it to much of how we run our own HubSpot development agency now.
We see HubSpot case studies from partner agencies and posts on how they’ve grown their revenue by a factor of ten and doubled their staff, and we think, Wow! That’s inspiring, but it sounds like it could be pretty painful! While HubSpot has growth resources for their agency partners, we can’t help but think of the literal growing pains when we were kids; we sometimes couldn’t sleep when our bones grew. There was discomfort, and sometimes a little pain, associated with that growth.
While we love watching the growth of other HubSpot agencies, we’ve also seen the other side of that growth. Several recent prospects have approached us after they’ve found other agencies have let their projects fall through the cracks. Those agencies are encountering problems associated with quick growth, such as overwhelmed staff and quality control issues, which are causing their clients (our new prospects) to suffer.
Here are just a few of the problems fast-growing large HubSpot development agencies encounter. Use them as signs that you, as a small business selecting a HubSpot development agency, can watch out for.