HubSpot Sandbox Updates for 2025: Grab Your Shovel & Your Sandcastle Bucket!

Do you live in a world filled with corporate data? Are you plagued by siloed apartments? Are your lackluster growth strategies demolishing your chances for success? Are you held captive by the evil menace Lord Lack? Lack of time, lack of strategy, and lack of the most important and powerful tool in your superhero tool belt knowledge. Never fear, Hub heroes. Get ready to don your cape and mask into action and become the hub hero your organization needs. Tune in each week to join the League of Extraordinary Inbound Heroes as we help you educate, empower, and execute Hub heroes. It's time to unite and activate your powers.

I feel so activated right now, dude.

And educated.

Me too.

I'm educated.

Yeah.

Hibernated together.

Oh, hibernated. Activated. Wow.

Did you know? Oh, last week.

Is this. First of all, is this G rated? PG rated?

Adjudicated is a legal term.

Sure.

No, I mean, Max. Max said. Do you know what I got into?

Right?

Yeah.

Is that PG or G rated?

It's rated.

Oh, it's rated A level.

Sure.

That is an answer. Thank you, Max.

It is.

It's an answer.

What'd you get into?

I'm getting into a little bit of a game dev. Oh, nice. I'm learning a platform called.

Wait, what's it called?

Godot.

It's French. G O D O, T. Good.

Yeah, Godot.

I got some tissues for that.

Yeah. Oh, I haven't learned how to make tissues yet, but I did make a table in boxes.

Oh, no. Nice.

And I put the box on the table.

So is this like, kind of like. Is it like really high definition or is it more like the eight pixel type game?

It's 3D.

Oh, 3D.

It's 3D. I made some low poly textures, if that's what you're asking.

Wow.

I do be up in that block bench, you know what I mean?

Painting some pixels right there.

16 bits. Yeah.

I'm not sure how this relates to sandboxes in HubSpot at all, but, hey.

Because it's like I'm playing in his sandbox.

Sandbox?

You made boxes and he made a box. Looks like I got my own virtual sandbox and playing in is what I'm saying. Wow.

I did sandbox sandboxing. No sandboxing. This weekend I have been Bing watching Game of Thrones and I had a really good omelet, so I'm looking to get my fill of sandboxes this morning, so. So, George, I actually want to tee you up for today's conversation if we're ready to dig into it. So you got A ping from one of our favorite friends of the pod, Chris Carolan, who is asking for this episode. Talk to me about what he was asking for.

We were talking about customer platform updates and I do believe that we ran across a product update that is the new standard sandbox with improved production metadata and deploy to production supported assets. That is the longest name of an update ever to a HubSpot product. But we were going over that and Chris referenced like, hey, you know, it'd be great to have Chad. He literally named Chad wax nerdy because Chris really loves when Chad wax nerdy on things on the show. We should see if Chad can wax nerdy and Max can max nerdy on sandboxes. And I think that that would be a useful episode. I, I and I said, Chris, I think you're right because you know, one thing that I don't do a lot of in HubSpot over the last like, you know, eons, since I'm the grandpa of, of inbound and grandpa of HubSpot sandboxes, like most of my clients are small to medium sized businesses. They have like marketing or sales pro or less. And so which by the way, we'll get to why that's important to why I don't really do sandboxes a lot. And so here we are, we're having an episode, we're talking about sandboxes. If you, if you've ever been curious if you should have a sandbox environment, what a sandbox environment is, maybe some of the cool things that Chad or Max have done with sandboxes, well then buckle up because we're playing in the sand today. Now also my beginning joke might make a little more sense or us rambling about boxes might make a little more sense too. We got there.

We got there guys. We got there. Now I personally am excited about this episode because again, I play in very specific parts of HubSpot and I don't often get to learn or hear about these more technical areas. So let's, let's start with that kind of obvious question, right? Like I've heard of Sandbox environments in HubSpot. Sandbox environments are not necessarily a new HubSpot specific concept, but when we're talking about HubSpot Sandbox for today's conversation, what specifically are we talking about it? Take the nerd and make it user accessible. What are we talking about?

So like imagine if you could take your HubSpot account and duplicate it so you could go play with it and test stuff without breaking the real stuff.

Yeah, yeah. Before Chad Goes I actually, I'll be completely honest with everybody listening is I took this conversation in these questions to my clone and I asked my clone, what the heck is a HubSpot sandbox? And my clone said, the HubSpot sandbox is like your personal testing laboratory. Max, that's literally what you just said. Inside of HubSpot, it's a safe, isolated environment where you can experiment, test and refine changes without messing up your live customer facing data. Think of it as a. I love this part, by the way. Think of it as a practice field. One of the things we love to do is we can go down to South Carolina, we can watch the Panthers practice before they actually hit the big. So. So it says think of it as a practice field where you can try out new plays before taking them to the big game. I was like, that's a pretty cool overview. That's a cool overview. Chad, where does your brain go?

Yeah, well, just in general, like to break it down when it comes to development as a whole. Like if you're going to be developing anything, which, let's be real, like, why, you know, people may call, oh, hey, we're CRM super admins or whatever, but at the end of the day, what you're doing is you're building, you're developing some sort of process or some sort of new thing for somebody to use. A lot of times when you're adding any kind of functionality or feature to HubSpot, just in general software development, typically you want to have a few environments. Actually you want to have a production environment, you want to have a test environment, and you want to have a dev environment for the developers to go play around in. Now I used to work at a company, we used to call our dev environment the trash can. And then when we'd want to go in and do this, a little bit of testing on a new build, they'd.

Be like, yeah, get out of my trash can. That's funny.

Like, want to go in early to see new features before they were ready? Like, yeah, my trash can, it's not working. You know, and then they like push it up to test once it was ready for somebody to like make sure that it's not really going to mess up everybody's world, right?

Yeah.

Now we don't have that here in HubSpot Sandbox we have two separate isolated environments. But what we do have is the ability to duplicate that live environment into what I would probably call a test environment.

Right?

Yeah. And I think also it's important to kind of like Explain the difference between this and other ways that you can just kind of like play around with stuff. So like, if you just want to, if like you're someone who just wants to like futz around with HubSpot, you can go create a developer account and create what's called a test account, which is essentially a, a blank slate, everything enterprise HubSpot account. The only difference is you can't send emails to people.

Right.

So it renders it functionally useless for anyone who wants to like, do anything, use it. Yeah, yeah. So that's a developer sandbox, or, sorry, a test portal. We don't want to call those sandboxes sandbox specifically. The big difference is that it's going to duplicate the way that your portal's already set up. So like imagine your layouts, your records, your custom objects, your properties, and then you could even bring in, I think, what is it now, like 5,000, 5,000 of your most recent records or something.

And their associated objects or something like that.

Exactly. And you can bring those in so you can play with like real data. Right. Which is great, but you're not going to screw up the original stuff. So like, yeah, this is really, really good. If you want to test a new workflow that you build so you can see how it interacts with like, stuff or if you want to, like, if you're doing any sort of like big data restructuring exercise, right. This is a great place to do it because you can kind of see how it'll all work without messing up your data structure on your regular portal. Right. So there's a million reasons why you might want to use the sandbox.

And, and I think, George, I have a clarifying question.

Oh yeah?

Yep, yep. So let me jump in for one second because one of the things too is because, Max, you did say development sandbox and then also what you guys kind of like backed up and then alluded to was a standard sandbox. And like right now if you. And it may be because I have this beta on, or it may have been that way historically. Again, rem, I don't do a lot with sandboxes, but I just want everybody to know the experience. Now if you go in and you create a new sandbox, you actually have the ability to pick one or the other. You can pick a standard sandbox, which again is kind of that extensive copy of production idea for like the robust testing. It's the, you know, the 5,000 contacts, the production objects, the forms, the workflows, the emails, all of that. Or there is the development Sandbox, which is like a minimal copy of production for like rapid testing. So this is like when you're gonna just test proof concepts, test proof custom cards, things like that. Go ahead, Max.

But let me clarify something. I was referring to developer test accounts, which are a separate idea. Okay, so like, but that's a good distinction too, right? In, in when you make a sand. Like when you have an Enterprise HubSpot account, you can make a sandbox and either have it be a standard or a developer sandbox. And like a developer sandbox is great if you're trying to test an integration or some APIs or some whatever stuff that you're trying to.

Or you're trying to build a uie, right?

Yep, something like that. Yeah. Some sort of extension. Right. But you have to have an enterprise account in order to build those. A developer test account. Any random Joe Schmo.

Yeah.

Can go get a HubSpot developer account and spit up test portals.

Yeah.

Right. So like bucket that outside of this conversation for anybody listening. Right. Like, I know there's like a lot of people like, oh, I don't have enterprise, I can't do a. I can't do a sandbox. Nothing's stopping you from going and building like proof of concept stuff in a developer test account.

100.

Literally nothing. Right. You just won't. It just won't copy anything from your portal because it's a disconnected idea completely from like, you know, being related to your portal in any way, shape or form.

One thing I want to double click on before I then shut up and let Liz continue us down the path that we're supposed to go down, because I find this very interesting as somebody who has been helping train humans in HubSpot for years and know that there are portals that have like test dash training for like forms and this, that and the other thing that have to like go back and clean up. If you have the enterprise version and can do a sandbox, one of the things that they have as a bullet point is like train new users and explore features and tools. In other words, it could become the trash can of training. Like you could have a do a development sandbox, but it be your training sandbox where that's where you go and just train people in and all the stuff could be littered around it and it not impact like your actual HubSpot portal where you're day in, day out and people are like, why is this test dash training workflow on here anyway? I'll shut up.

So I only had one clarifying question before we moved on because George, you and I have done a lot of work together in HubSpot. Is the sandbox environment we're talking about different from content staging?

Oh yeah, yeah, yeah, yeah. Good question.

Yeah.

So completely different because content staging is part of like CMS or what is now Content Hub. And so if you want to deploy website pages, landing pages, but be able to work on pages that are already live, make adjustments without anybody seeing them, but be able to have internal teams preview them and then push those pages live to like the same URL. That's what content staging is for. Very, very much just like content driven, by the way, if not why we're here, but I wish you could actually do content stage blogs. But again, totally different conversation. HubSpot development team, hopefully you're listening to this or somebody that knows the development team, who knows, maybe your mom's listening to this and they'll pass it on to you. But completely different than like a sandbox environment.

Hi.

That's like the content sandbox, basically. Yeah, in a way.

But I love, I love.

It's like content test probably, but yeah. Or pre prod maybe. Maybe you call it perfect, but anyway.

All right, so let's throw this out there, guys. What has changed with HubSpot Sandbox that we're excited about? What's the 41 1? What's the scoop?

Well, yeah, so they had legacy sandbox before, right? And that's what they're called now. So if you have an older style sandbox, it's referred to now as a legacy sandbox. And then they have a new version of the standard sandbox which essentially does a one time import of your current HubSpot account. But there is a bit of a distinction between the old and the new, right? The old sandbox, it could continually get refreshed like the legacy one where you could update it with whatever the current structure of your current production portal is. Now that feature has not been added to the new standard sandbox, but they added a big one that people have been wanting for a long time. And this is killer for anybody who is a standard. Like is managing one portal. Like if you're a HubSpot super admin of one portal, this is like pretty, pretty epic because you don't have to pay for extra tools to solve some of these problems. And what it allows you to do is basically reverse sync or they call it a deploy to production from your sandbox. And it supports like five things right now. Right now it supports the ability to like basically clone your portal, add Forms, lists, marketing, emails, objects and property structures and then workflows that involve any of those things. I don't know for certain, though. I don't believe it'll pull up any workflow. Like, if you put custom code in the workflow, it might not pull it over or if you put, you know. So there's a couple things that it still won't do as far as reverse sync, and those are the main things that are supported. But when you're talking about like, okay, well, what I'm going to do is create an integration, like, or add a new feature.

Right.

Like, I was working with a company and we added a contract management system, rad AI. And so we're doing this contract management system and I was able to install the integration, add additional properties, est the whole thing in Sandbox, and push all of those property changes back up to production.

Right.

And all of the. There was no new objects, but if there was a new object, it would do it. Property groups the. It didn't manipulate the user interface, unfortunately. So that's also something that it still doesn't do. But. And you know, we can maybe double click on that later when we're going into some more of Liz's questions. But it's, it's amazing now that at least at minimum you have a baseline and this is the, the worst this feature is ever going to be, as we often say.

Right?

Yeah.

And they're only going to be adding more and they're looking for feedback on, you know, what, what's missing.

Right.

Well, what's missing is for me, you know, user interface.

Right.

Update the user interface along with it. Because often you want to build a good user experience, not just, all right, I'll put the bits and bobs in the back end and then they'll all figure it out in production. You're going to have to redo whatever you did over in Sandbox in production.

Right?

Yeah. And also like a little bit of historical context here too. Like, sandboxes have been around for a while, but they've never had the ability to push stuff back into the main production portal.

Right?

Yeah. And that's what a lot of big enterprise CRMs often have. Like, you know, if you get Dynamics 365, I mean, you have like, I think you have. Because it was made by Microsoft.

Right.

So they have like three layers. Like, you can do the whole dev test prod thing that I described basically in Dynamics. But also Dynamics is a giant beast of a system that's like, basically you have to be a Developer to use it.

Yeah. Now, something important to note as of the day we're recording, this is August 18th or. No, not 18th.

11Th. The 11th. Man, don't do that to us. Come on.

I don't know why I did that. It was August 11th, right. The way that deployed. So the deploy to production stuff is in beta, right?

Yeah.

And it's interesting because the limitations around it are that you can only deploy back net new stuff you've created. It doesn't let you edit existing assets, which is a little bit goofy. But again, worst it's ever going to be right now. Right. The logical first step to any of this is recreating. Net new stuff. Right. Editing stuff is worlds more complicated. Right? Yeah. So keep that in mind, depending on when you're listening to this episode, is that the deploy to production feature is very new and it's half baked at the moment.

I think this is where I jump in and say, listen, we're talking about a public beta. It is. It is a beta version. So when Chad and Max say it's half baked or it's the worst it'll ever be, it's because it's a beta that once it goes live, I'm sure a lot of the things that we're talking about, you know, maybe the product team will actually like, tune in and check out this episode. But a lot of things that we're talking about might actually just be in the actual new sandboxes once they deploy the live version. Because smart humans like Chad, Max and others out there, maybe even listening to this podcast, are like leveraging it, using it. Second thing I want to throw out there is it is right now for anybody who signs up for the beta, but then also it's enterprise, customer platform, content, enterprise marketing, enterprise ops, enterprise sales, enterprise or service enterprise, if you have any of those enterprises, you can turn on the sandbox feature that we're talking about. Here's a question that I'm going to ask. And again, kind of going off the rails for a second. But when you guys talk about this deploy wizard, if it got smarter, because it might not be now, but let me ask you a question, because my brain went there. Are we entering a world where if you have an enterprise set up in HubSpot and you've got a sandbox where marketing and people should actually maybe even be working? Like, for instance, if I was going to create an email, do I create the email in the sandbox and then deploy it to the real one and then send it from there? Or is that Overkill. Like you're talking more like nerdy stuff.

Yeah, complete overkill. I mean because like that's the thing, you shouldn't be afraid to build stuff in your main portal. It's more so I would say untested fundamental structural changes to the way your portal operates. You should test drive it in the, in the, in the sandbox first. Right? You don't want to be spinning up a sandbox to go build an email just to push it into the.

Gotcha.

Into the main portal. Right. Like you can still draft like that doesn't to me. Yeah, yeah, yeah.

You have all the functions with that. If you were like, I mean, if you really needed to do something like, you know, one of the things they push back is lists, right. And so if you had like property structure changes that you need to make to make your data clean, it may be worth attempting to build all of the lists that would let you segment all of your customers after all of those net new properties were changed or something along those lines so that you could really understand your segmentation. And unfortunately reports don't push back. But that would be a nice thing too is like, you know, now you can make your reports and it all works and your lists validate everything. Then you can push that all back up to production. Now at least you could put push the lists and the, you know, stuff like that, the lists and the property changes. I'm thinking at some point there may be a world where they need like it's almost like a code merge editor. Like where when you're viewing changes in code and there's like the green and the red that shows you like, oh, these lines are added, these lines are removed in this place. You know, it's, it's not quite that nerdy but like they will probably need something like that when they allow edits for conflicts pushing back up like hey, these properties already exist. Do you want, you know, obviously you change this but between the last time we saw it and now, this was edited and this was edited. Do you want the copy that's in production or that's in sandbox?

Right.

They're going to need like some level of conflict changes where it scans and scans both sides, runs through a checklist of however many things that it wants to confirm. And you know, I'm sure they'll let you just say choose all or whatever if you wanted but that could be dangerous. But you know, again I think there's a world where that's going to need to happen to allow non net new and an Edit of existing assets.

So, so let me ask one more question because my brain is going all kinds of like sideways left down over here and then Liz, I promise I'll shut up and you can continue to herd cats the rest of the way through the show that we need to. I'm just, hey man, I'm just giving.

Space for nerds to be nerds. Nerd away.

I'm, I'm, I'm, I'm just getting started with HubSpot. I fire up a sandbox. Do I go in and actually go to data management and go to data model and do I build my data model in the sandbox and then once I'm happy with it in the sandbox, then deploy it to the. Again. I'm trying to figure out these scenarios. Whereas that old, like if you're just.

Yeah, if you're brand new HubSpot. Empty HubSpot.

Yeah.

It's building Prod.

Yeah, build in Prod. Because it's, you're not affecting anybody and you don't have your whole list of contacts or you know, you haven't uploaded all of your data in there. The only time I might suggest that is if you're planning on doing like a mega, mega upload or something like that. Maybe. What I might do is build what I think is the right data structure in Sandbox, push that data structure up to Prod, do a mega import inside of my sandbox and make sure everything checks out. Otherwise then I have the opportunity to nuke the sandbox and pull that copy back from Prod into Sandbox. But again, remember that you only have those five assets to work with right now.

Yeah.

Also, I don't think anyone should over think this. You can test stuff in Prod. Not an issue. You know what I mean? It's just like it depends on the size of its impact, you know what I mean? And how detrimental it could be if it goes bad. Right. Don't be afraid to experiment in production. There are plenty of ways to. When you're building a workflow, there's plenty of ways to isolate the workflow so it doesn't touch your other data. It's one of those things where unless it's a really big project, it probably doesn't need a sandbox.

Right.

So. Because again, it's like a process to spin it up, get all the stuff imported, like maybe delete it. You know what I mean? It's, it's, it's a thing. Right. It's not a. Yeah.

Another thing too is like when you do a Sandbox, all the workflows that you have are turned off as after the sandbox is created. So like whatever you built in Prod, you basically have to go. I think it also. I don't know if the new sandboxes import your user interface, but the old one definitely didn't.

Right?

Like the record. The record.

The record structure. Yeah.

Oh geez, that would make me not even use it. That's crazy.

Yeah, the old one definitely didn't. I haven't checked the new one actually I don't even remember because it's been like a little bit since I created my. I. I went in and did a whole bunch of stuff in there and pushed it up for an integration that I was building. So. But it was missing some stuff still unfortunately. So I used another tool to import my record structure and a couple other things and yeah so that I think that that's one of those things that's a little tricky right, Is making that decision. But what you asked earlier George, like do I build it in sandbox? Actually I'm going to change my answer to like brand new portal. Probably never in sandbox. And the reason is because of the limited assets now in the future if it is like a full, you know, forward reverse kind of a thing, you know, then you could do either way. It depends on what you really prefer.

Right.

Just extra work though, you know what I mean? Like yeah, I mean it just going on in production then.

Yeah, if there's nothing in production. But I think the thing about it is like when it comes to like an actual development life cycle and actually building things like from the perspective of like if you were doing it from like a development perspective, you would always start in dev. No matter what you always start in dev. If you're developing something you always start in dev.

Right, True.

I just think, Yeah, I just think you know like for, for us to get to that place like the. It's obviously this. The sandbox has a long way to go in terms of what it can push to production.

Exactly. Yeah.

You end up rebuilding shit manually, you know.

Yeah. If we at a place where you're not having to rebuild anything manually and you have the ability to do like reverts almost like you know you're, you work in your git repo.

Right.

Like oh, I'm going to go back to this check in and then sandbox is back to whatever I built 5 check ins ago and then I can push that all back up, you know, or whatever.

Right.

Like those sort of things I think are theoretically Possible, but it is going to increase the complexity as well to allow that level of functionality.

Right.

Right now it is very turnkey. It's like if these things work for you, you click a button and she works.

Right.

Chad, you think they'll ever bring it down to Pro?

I could see it. I mean a lot of things that you know, like for example, custom data sets were enterprise now you get a cut down version.

Right.

But they're pro now. You can make custom data sets with custom calculator properties. In Pro you have less properties you can make but like in a pinch it will allow you to make a report that you absolutely never could have made in HubSpot before.

Yeah.

So let me ask you guys this.

Totally possible.

We've talked a lot about really interesting updates here, but is there anything that's still missing for us? Anything we still want to see? Chad? I see that smile.

Yeah, always. I mean definitely like version control will be one thing for sure. So that's huge. We were just talking about that. And then additional assets like you're gonna ultimately like and Max, I mean you, you mentioned the edit, right? It's only net new properties. So if you need to edit the description of a property, for example, you're going in and doing a mega overhaul and you just are taking your time in sandbox and maybe deleting properties that don't need to exist anymore, adding descriptions to properties that somebody just junked up and didn't put name. But you can't push those changes right now up to production.

Right.

So I think that'd be really killer, you know. So both delete and edit would be amazing to have even just on the property schema level.

Yeah. And I think also just like record layout stuff is a really big one. I mean record layout stuff is one of the biggest reasons like I feel like sandboxes would be useful. Right. Just because you know, you have to do. It's a lot of work to go in and completely like restructure like your UI and your, your, your record layouts and all that kind of stuff. And like it's also something that can like stop people dead in their tracks from working because they like can't find where a piece of data went or they don't know how to navigate the tabs on a certain record or where to find the data they need. Stuff like that. Right. So I think like moving to support that as fast as possible is, is probably a really important thing, you know, so that, and also like I wonder if there's like anything creative they can do around how to handle like connected integrations. You know what I mean? Like when you do a developer portal, like you don't have any of your integrations still hooked up. Not a developer portal, a sandbox. Right. Yeah. So like you got to go like reinstall apps, reconnect stuff. Like sometimes that's not so easy with like, you know, like, you know, for when we have customers that want to do, you know, an event happily Sandbox, we effectively have to give them like another license for free to go do that. Right. Which is like kind of goofy, you know. And so I, and I'm not sure like what the answer is to that because like the developers and how their apps works is always going to be like a variable there. Right.

Maybe they have to give a framework on the app partner side for Sandbox, they have to actually have a supported, you know, dev test or sorry, prod test branch where all your URLs change and all of your database changes because you can't just connect up somebody's prod data. So that also means that whatever that partner is has to have a level of Sandbox functionality for their tool in the first place.

Interesting. It's almost like my brain goes to. My simple mind goes to like it's in the future if it was just almost a mirrored version and it automatically kept up to date, but then you could make changes and push it over and then. Interesting.

Yeah, I think ultimately that's where they're moving. Right. But I'm sure there's drawbacks with doing a complete mirror. Also, I think sometimes there's. There is a benefit to having it be a snapshot just in that it's not going to start changing while other people are making changes in production, you know what I mean? And screwing up what you're doing in Sandbox. Right. Yeah, but. Yeah, yeah.

So I did double check the new version of the sandbox. It does not pull in the UI structure. So it still has the default HubSpot. About the steel card, I can think the reason is because the. If you have integrated apps and they're not there or something, I mean, maybe they just omit those. But if those possibly could cause some sort of issue or if you've installed like a UI extension so you've made a custom HubSpot UI extension and it's in prod, but it's not connected to your sandbox, obviously, because that doesn't have like splitting. I could expect that the hard library that we now use for the record editors.

Right.

You know you have like the side panel that comes up when you're editing the structure. Those hard editors would have properties in them that wouldn't be able to exist in the sandbox theoretically, or stuff that could theoretically not exist. So right now they're just completely omitting it, rather than like parsing out the stuff that's missing or putting placeholders in, you know, or something that will allow them to still exist, you know, or some way that it says this is in production, but it's can't be in sandbox. So you can still have everything. Because here's the thing is like when you build something in sandbox and you add a record editor like that, or a property card or some sort of structure for the user interface of Sandbox, then you have to manually recreate it in production. You also have the possible missing out of making it exactly the same or some sort of conditional logic that you forgot to add. So I think a big piece would be adding that data in. And then the last thing, while we were talking about the developer sandbox in the enterprise accounts, one thing I wanted to point out that's really, really, really for your developers outside of just them spooling up a free dev account, is the fact that it has your HubSpot structure. So if they're building a HubSpot user interface extension, then they already are going to see all of like your HubSpot portal properties and associations and association type IDs if you have custom objects and often like you want to interact with a custom object when you end up dealing with the user interface extension. So that's like one reason that it's extremely helpful for your developer to work out of your enterprise developer sandbox rather than just the freebie developer sandbox. Also, they'll be constrained to the limits of whatever your subscription is. So if they want to use some sort of fancy technique. But it's a hub you don't pay for for some reason they'll have to live within that world as well. So a few, couple extra things as we round the corner here.

Yeah, well, let's round the corner and land this plane, shall we? George, what is the between 1 and 23 things you want our listeners to take away from today's episode? Just one.

Not just one thing. One thing. There was a word, I think, I think it was Max used this word, I'm almost positive. And maybe it was used by multiple.

Just one.

No, just one thing. One thing. My one takeaway is like when you're thinking of. I think it was Max used this word, I'm almost positive and maybe it was used by multiple people, but the word is impact. And so my one takeaway is like when you're thinking about sandbox and if you should use a sandbox or not use a sandbox or do something in sandbox, if you're using sandbox is impact. And I would suggest that maybe you come up with like, you know, small, medium or large gauge around impact to the team. Impact. Well, actually, let's just say impact to the people, impact to the platform, or impact to the process. Right? So think about those three layers, the word impact and small, medium or large to know where you should be building or doing the thing that you're doing moving forward. That's it. One thing okay Hub Heroes, we've reached the end of another episode. Will Lord Lack continue to loom over the community or or will we be able to defeat him in the next episode of the Hub Heroes podcast? Make sure you tune in and find out in the next episode. Make sure you head over to thehubheroes.com to get the latest episodes and become part of the League of Heroes. FYI, if you're part of the League of Heroes, you'll get the show notes right in your inbox and they come with some hidden power up potential as well. Make sure you share this podcast with a friend, leave a review if you like what you're listening to, and use the hashtag hubieroes Podcast on any of the socials and let us know what strategy conversation you'd like to listen into next. Until next time, when we meet and combine our forces, remember to be a happy, helpful, humble human. And of course, always be looking for a way to be someone's hero.