Name: The Next Big Thing from Pigment AI Is Coming
Uploaded: 2026-09-22T17:30:45.552Z
Duration: 46 min
Description: The Next Big Thing from Pigment AI Is Coming

Transcript for "The Next Big Thing from Pigment AI Is Coming": Good morning, good afternoon, and good evening to everyone joining us, on our Pigment webinar. I am Steven Riddecker. Thank you for joining us today. I am the head of customer experience here at Pigment for the last, bit over a year. Very excited today to bring a lot of new capabilities to you that you'll be able to use in your Pigment implementations and your your solutions quite soon. But it really starts with, if you can describe something, can you get that interface for your users on top of your existing data? I think a lot of us for a long time, operating in pigment and even in other tools have known that we often have to think about how things work around, how our UX is designed. Now what if we could just, deliver that the way exactly the way that we want to see that? So with that, let's take a look and let's look at the introduction of frames. Pigment frames are going to allow you to create the experience that your users need to see, Whether that be a CFO who has a specific, view of the world or whether that be your users that need a very simple, step by step guide for doing their input, you can do that with pigment frames. So as we move into, into some of the details here, with frames, what is it? Frames are where you can decide how do you want to create this interface. You can express your intent and you can get a presentation back. You can get a form back. You can get all of the chart types that that you've always had in your head or you've seen in in other other tools or other places. The crucial thing though is that it's all connected live in your pigment data. It's on that governed information built for your enterprise scale. The the interface you exactly need against the data that is governed by your organization. And there's three different primary use cases that you might see for this. Those three different use cases, often fall into these buckets, but sometimes can cross multiple buckets. First, probably the easiest one to think about is I just want to explore and I wanna simulate a different experience than my users have seen. A certain chart type that I wanna see or I wanna do a what if interface, and and I wanna create that experience for my user. Or it might be, and I think this has been a dream for so many of us for so long, is I have all of my information in Pigment, and I wanna present that to my stakeholders, my my the folks that I work with in my business. Now I can present that information directly from pigment. So that plan, that presentation is the plan. And I can also build in narrative reporting and story modes and and board ready slides, in this modality. And then finally, I think we all know that some of our users really need the the the hand holding guidance of what exact information do we wanna capture from them. Being able to create a data entry form that is exactly focused on what your users need to do so they can give it to you easily. They get in. They provide their information and and participate in that planning process. You heard a lot about it. Let's see it in action. So I'm gonna go ahead and, let let's, show what we can do. One second while we get that, pulled up and running. We wanna show you, exactly a customer doing that. So we're gonna first show you that, and then we will move into a live demonstration. So just a second and we'll pull that up. While we're waiting, if you do have questions, please feel free to, put them in the q and a chat here in the in the webinar interface. We will have time towards the end to, to answer many of those questions. Any that we don't, we'll follow-up on. And here we go. Nice. Looks great. It's exactly what we, drafted up. I oversee, obviously, all things finance, strategic finance, business operations. I want my team to spend a lot more of their time analyzing the business and making decisions versus, like, reconciling numbers and and doing that sort of stuff. So we are here today to talk about frames. Yeah. So frames are AI generated components, like, UI components, okay, that let you actually, build, you know, some very customized, UI for your processes. So it could be either for reporting, but also to collect data, you know, input forms, if you want to create slides. And it would be, you know, sitting inside the application so connected to your live data. So what I suggest now, is that we spend some time on the whiteboard. I think the use case that would be really helpful to work on is really, like, helping us get a better handle on just our sales capacity model. You know, at Glean, it's this very manual process. Every time we wanna do an analysis and, you know, show it to either our board or the executive team, my team kinda has to scramble and kinda, like, stitch things together. So it'd be really cool to have a frame that sort of, like, just shows that, gets updated in real time. So to start with, I think what we would need is an AE roster by segment, by manager, what their quota is, what the ramp time is, hire date. And then what we also need is a live view of quota capacity, adding future AEs. It's basically being able to just, like, play with future hiring assumptions. Maybe just like simulation scenario analysis. I just wanna know, like, what hiring pace Yep. Do I need to be at to hit my number next year? Makes sense. Okay. Cool. So let's build this sales capacity frame. Let's do it. Okay. So I'm gonna attach, three files. We have the picture we took from the whiteboard, the design requirement from the discussion we just had, and also the design skill of cleanse that is respects your your brand. Okay? And let's prompt. Let's create the, set frame. So it's gonna start reasoning about, you know, what should be including in the frame based on the drawing we did and the requirements. Alright. The frame is ready. Alright. Okay. Let's see. Let's see. Wow. Nice. Looks great. It's exactly what we, drafted up. So some KPIs at the top. K. Okay. We have the a roster here. Actually, it's, as you mentioned, editable. Oh, wow. So maybe it's not that you won't change, but the CUDA Mhmm. Cool. Can change. You see live updates here. Then below, we have the simulation part. Exactly. Like, we we create a lot of this by hand manually. So just being able to toggle it, super valuable. I mean, I think the most surprising thing was we started out of whiteboard. Whiteboarded, I drew up what I wanted to see, and we uploaded it to pigment, and it one shot it that was incredibly useful, without any edits. It just saves us a ton of time from having to do all of this stuff manually in spreadsheets. So I think just expands the aperture of what clients can do, makes us move faster. It's really, really exciting. How about that? Very cool introduction to frames, but we wanna take you a little bit deeper. So we're gonna move into our demo now, and I'm gonna turn over the stage to Anna. Great. Thanks, Steven. Go ahead and get my screen shared. Alright. So hello, everyone. I'm Anna, and I'm actually no longer a solution consultant at Pigment. For the next fifteen minutes, I am a finance leader at Lumina. Pigment is the single shared source of truth for Lumina across budgeting, forecasting, revenue to expenses, and across all of our global regions. That means that we all look at one live connected plan, except for one final thing, our long range plan. This still exists as an Excel file with a tab for each entity, formulas tracing across different initiatives. It's a big pain and because it's in Excel it's extremely manual to update. It lacks the flexibility and insight that we really need. And some number in there is always slightly off because it's not connected to pigment or our source of truth. Now this morning, my CFO sent me an email asking me if we could turn our long range plan or LRP into something that could be updated at a moment's notice, allowing them to easily flex assumptions, more quickly gather information from our different local leaders, as well as create a polished board ready presentation for next week. Normally, this process takes about five weeks end to end, but I need to get this rebuilt in pigment today so we can have everything ready for next week. Instead of spending the afternoon unwinding what's happening in that Excel file, let's go directly to the Modeler Agent. Now as we know, the Modeler Agent is already an expert on how I plan at Lumina because it's embedded within Pigment. It has all of the context of how we plan and all of that business context unique to Lumina. With the modeler I can not only start with my intent, I need to build a collaborative initiative based long range plan. I can also upload the actual Excel file directly into the context of the modeler. Now I can upload other files like PDFs, images, PowerPoints into my conversation. Now as the modeler reads and analyzes that Excel file or other files that I've added, it's also scanning everything that already exists in Pigment. Again, that context that is unique to Lumina. And within just a few minutes, the modeler created an end to end build plan to get this long range plan into Pigment. Now even just getting to this point of understanding what really needs to be done to translate this into Pigment would have probably taken me a whole day. From there, the modeler created all of the components that we need. It took those Excel formulas and created metrics. It's able to understand how that logic shifts when we're moving between these two different types of planning. And again, it shows me everything that it's thinking, every thought that it has, all the way through to creating a collaborative and intuitive initiative based long range plan board in Pigment. Now before pigment, it would have taken me at least a day to unwind that Excel file and probably a week to get this manually built out before the modeler. But today, I was able to go from intent and Excel file to a model and pigment in about an hour. But the spreadsheet only has the math of of what we're doing for our long range plan. It doesn't have all of the decisions and all the nuances that really come with it, that kind of qualitative information. While the modeler was building out this model, I was having a conversation with my CFO. We were talking about the long range plan, talking about new initiatives we want, really just having this back and forth conversation here. This is the transcript of that conversation in Notion. I don't wanna go back through this, reread it, or have to ask for a summary here, copy the information to different places. That's quite manual. So instead, let's go back to Pigment. And from the Modeler agent, I can connect directly to Notion, and I can ask, please look through Notion for any recent conversations I've had with my CFO about our long range plan. Now with Pigment Agent connectors, the modeler can bring in key information from external sources, reading lengthy and potentially messy notes or back and forth conversations to find information and, needs for your pigment model buried within. Now I don't have to waste time going to to different places, having different tabs open. Whenever I want to come and iterate on my model, bring in different information, I can come directly to the pigment agents and bring that information in. So here, I can see a quick summary of the four new initiatives that we want to add to our long range plan and that we want to have a new strategic theme dimension to organize these. The modeler then built that for me. The modeler took that context, created a new strategic theme dimension, which is organizing our initiative dimension here. It even went as far as adding in those new initiatives that we spoke about with the CFO, including all the context, who the owner is, what the key insights are that will drive how we model this in Pigment. And as things continue to change I can come back to the Modeler to iterate, improve, and strategize my model. That is why pigment agents are the first place that I go when something unexpected lands in my inbox. So think about this for a second of what this process would have looked like. Everything that Anna just talked about, what that would have looked like a year ago in Figma, what that would have looked like in years past in other tools that many of us have experienced with. It would have taken, as Anna said, at least a day, probably even longer. And then when that CFO comes and gives you that much more context, uh-oh, are we doing that again? Now you can start to see, like, this is a game changing moment. We can do things now, that we just never really even dreamt about in the past. It is incredibly helpful to bring in the Excel spreadsheet and get the math from that and then have the modeler, create that and be real for you. It is next level that we're also then capturing the intent, of those conversations. When you combine the math and your business processes with the intent, this is when you get really fast time to value for your business processes. When the model agent came back came out in March, it it was very, very useful right from the beginning. It's been getting better and better and better and better. And as Anna highlighted today, not only can we bring in Excel files, but also PowerPoints and PDF and screenshots, even the photo of the whiteboard like we saw in the, in the frames video with the with Glean. It can also see the audit trail of of who made what changes in the plan so that you can you can keep up to date with what other people are doing. Whatever those whatever is new, whatever business problems come your way, the model or agent is ready for you to share that information with it and then take you into the next phase. And with that, we'll go back to the demo. This board that the modeler created is perfect for my everyday use on the finance team, but my CFO has quite a particular way that they prefer to view things. Does that sound familiar to anybody? In the email that my CFO sent me earlier today, they included a screenshot of a dashboard that they created using our LRP Excel file and AI outside of Pigment. Now that's great for a quick iteration but it's still disconnected from our source of truth. We can't and shouldn't make decisions off of stale data. But what if I could build the same intuitive interface that my CFO wanted but connected to our live Pigment model. Frames make that dream a reality. Frames are fully customizable interfaces within Pigment. And I know what you're thinking. Pigment is already the most customizable platform on the market. But frames go far beyond the interactions, the charts, the experience that you expect from a board in Pigment. And to get here, I simply had a conversation with the modeler. I shared what stakeholder I was building this for, that I wanted this to be for my CFO, the specific interactions I wanted, like using sliders, drag and drop, a same key chart. I even included the screenshot that my CFO had sent me of something they created on their own as inspiration for the modeler because I know that they like that interface. And within minutes the modeler created the frame that you say see here. And this is connected to all of the metrics, all of the views that we were just looking at on the board before this. It's all one model, just a different lens. Here, my CFO can easily use sliders to adjust high level assumptions that impact from our revenue all the way through our EBITDA. In the bottom right, they can click in to further adjust assumptions for specific initiatives. In our same key chart, we can visualize EBITDA or revenue, understanding how things move from our strategic theme to the initiative to each country involved. And when changes are needed, my CFO can easily come in here and drag and drop to include or exclude countries from these initiatives. Now you've probably built something similar to this using AI outside of Pigment but then turning that into something scalable and production ready is where it breaks down. Pigment solves that gap. It gives you the power and creativity of something like Claude along with the unlimited scale and security of Pigment's graphite engine. That means that one, my CFO does not have to compromise on their user experience, two, no one is manually updating an Excel ever again, and three, we can move more confidently because we know we are looking at the same numbers. If frames enable me to build any interface that I can imagine for my stakeholders why would we ever need to leave Pigment? And this is one of the big seminal moments. It seminal I can't say the word. Let's just pick a different one. This is one of the big moments, that I think all of us are starting to think about, oh, what can I do now, with my user population that maybe I haven't done before? Many of you that have used, EPM tools, for for many years have always known that the UX can be a friction point for getting your users in the system. And having to do things in grids or having to do things in in specific ways could be a limiting factor. Even if even if you as a model builder thought, oh, this is easy to do. This now removes that constraint. You now can make the experience exactly what you need your users to see, whether that is a a board presentation or a an input form, either of those are gen are are generated by the modeler. The modeler will do the entire build for you. It'll build the model as we saw in the first, part of of Anna's demonstration. It'll also then build the UX for you. There's a crucial part about this though, which is it's not just about the UX itself. It's that the UX is connected through to your governed data inside of Pigment. This means that you can create that user experience and it's going to update live. It's going to accept input. It's going to be there next month and tomorrow when new data is coming in. All of this is live connected through to your your underlying pigment data. And this is really, as Anna said, one of the things that sets it apart from, creating interfaces like this just through, LLM models is it stays connected to your data. So if I create a board presentation for q three that we're in net right now, I'll know that I can use that and dynamically use that in q four. I'm not having to rerun prompts. I'm not having to rerun, the these types of of build. It's the same plan. It's the same numbers, just live connected through to pigment. This is what it looks like when you start to build across an enterprise foundation that you wanna bring everyone into. Let's see what's next. My top down plan that my CFO is planning for is really only as good as the supporting information that we can get from our different local leaders. And as I mentioned, that this normally takes weeks of back and forth, tracing down spreadsheets, emails. Last week, it took us five weeks or more to gather everything that we needed, and that just doesn't cut it anymore. That is why I use the modeler to create this guided intuitive interface for my local leaders in Pigknit. Again, I had a conversation with the modeler agent, and I shared my intent. I shared that it was for my local leaders, that I wanted it to feel like they were filling out information on their favorite website. Maybe they don't even notice that they're in pigment. And Lumina is a global company, so we wanna meet our local leaders where they're at in their preferred language. So when my local leader in Germany logs in, everything defaults to German, meeting them where they are at. Now, as I move through this form here, we see those same initiatives and those top down assumptions that we were just looking at from our CFO perspective. That's because this is all wired up to the same model and pigment that we have been talking about this whole time. As my CFO has new asks, it's immediately available here in this different UI. There's no waiting, no copying across different apps, or copy and pasting things in a Google Sheet or an Excel file. It's already there. As inputs are made, say, if my local leader wants to bump up revenue in a certain year, everything updates in real time. As those changes happen, my CFO is able to see those impacts again in their frame, and I'll be able to see that in my own board that I prefer to work in. When we use frames to gather information from stakeholders, they get to experience the guidance and the story. They don't have to worry about knowing how to use pigment. Again, we don't have that that blocker there that can sometimes that was a problem for us at Lumina before with these local leaders. And as they confirm and submit their work, on my end, I can see exactly when and where that has happened. I spend no time having to chase down spreadsheets for those models that we just can't get into pigment yet because we have those specific UI blockers. And now I get to spend more time being a strategic partner and actually helping these come to life. These initiatives come to life. Now while I've been chatting with the modeler agent to create these frames, I almost forgot about the a of my FP and A role. And since Pigment is our single source of truth at Lumina, it also acts as the semantic layer for all the AI that we use. It allows the analyst and the modeler agent to act as extensions of every person with that governed understanding of this is how we're looking at our plans and our dimensions and our data. Earlier today, I was having a conversation with the analyst agent. I was sharing that I wanted to help my CFO better prepare for upcoming meetings with looking at how we want to prioritize our initiatives, helping us understand where there are anomalies for different inputs. So I got a quick understanding of where things sit today. But to get this analysis, I don't always have to come and prompt the analyst agent. Now every morning when I log into Pigment, the analyst agent has already ran and created this report that we see here in this frame. This is a mission output in a frame. While submissions were coming in, the analyst agent was already analyzing the impact of the initiatives, helping us understand where there was specific concentration of higher value, whether we're looking at EBITDA or revenue, helping us look at different anomalies, as well as helping us rank priority because at some point, we're going to have to help strategize with the board on what do we what initiatives do we prioritize over the other. I used to spend my mornings stressed and crafting the spending time crafting the right information, the right story to share with my leaders. But now with pigment agents, so much of that work is already done here. So So instead of spending my precious time sifting through data, I now can spend more time deciding and strategizing what to do next. And this is a really important shift in how all of us are doing our jobs. It means that where previously it required action for someone to go in and run an analysis or or or or answer a question, we can start to do things in an autonomous way. This is the first step towards autonomous planning. And as you saw there from Anna, the analyst agent has two different modes. I can ask it questions and I can get answers, and it's very, very good at that across, all the information available to it, which also includes things like the Notion connector and whatnot. But it also can just save these things as missions and be running automatically so that the next time that there is a a business change and we see what that change is, the report is done for us. The root cause analysis is there. And then we, as the as the humans in in our organization, can take that from there and apply our judgment, without having to do that work upfront. The planner agent is going to take that even further with scenario agents and comparing options and looking at different scenarios, and we're moving towards that with Figma across all of that. You've seen that with the modeler agent and and laying the foundations of what we can do there with the UX and frames, the analyst agent doing the analysis for all of that. All of this built on the platform that scales with you with your data connected across all of your, planning processes so that we can start to move into this age of doing autonomous planning where agents are doing a lot of the work for us. So we spend our time, as Anna said, being that judgment layer and that decision layer in our organizations. Alright. So now I have the structure of my model. I have a frame for my CFO, and I have a simple intake form in a frame for my local leaders. Now I need to make this presentation ready. But first, I want you all to think about a situation you might have found yourself in. How many of you have spent at least a week putting slides together for executives or the board just to find that at the end of the week something doesn't tie exactly to your source of truth or some change happened outside of the system, then you spend a week trying to, excuse me, spend the weekend trying to figure out where that number came from, that is a painful rite of passage, that a lot of us find ourselves in. But now with frames, that process of getting something from model to presentation ready can be done for you. Frames can take our model, all of the work that we've done, all of the inputs, all of the insights, and turn it into a vehicle for decision making. So what we're looking at here is a frame in pigment again, and it allows my CFO to both prepare and present. So this first part of the frame, my CFO can look at main figures, filter down to particular metrics that we're looking at, use that same analyst agent output just formatted differently so I can derive more insights from that, all the way through to helping me think about potential questions that the board may have. Now to get this into a presentation, I don't need to get the data out of Pigment. I don't need to download it, you know, disconnect it from Pigment. Directly within this frame, I have Lumina branded slides. And from here, my CFO can even present. My team used to spend at least a week, a quarter, trying to tick and tie numbers, but now as plans change, as we add new countries, new initiatives, new versions as the years go on, this will update automatically because it's connected directly to pigment in this frame. And because I need to stay agile for any ask, I can also export this as a PDF to send to my board ahead of time if they prefer. Pigment really lets me do it all without leaving the platform. And what's key is that it's all traceable. That's the difference between something that's just impressive that you've created with AI and something that you can truly make decisions off of. Today, an email changed what my day was going to look like. I then used an Excel file, my intent, my conversation from Notion, along with the modeler to build a new production grade model in Pigment. We then use frames to create three unique interfaces and experiences for different stakeholders. And these frames are connected to that model we built. They write back to the model. It's just like inputting to a metric, just visualized in whatever customized way you need. I then use the analyst agent to provide autonomous insights to my CFO before they even asked for them. What used to take me maybe, you know, two normal weeks or one very busy stressful week became an afternoon of work with the pigment agents. And now that we are nearing the end of our time together, I have something that I need to confess to you all. This agenda that we've been looking at this whole time, even this is a frame within Pigment. Any model, any interface, any workflow can live within Pigment. Pigment has not only changed the way that my team plans, but also the way that I approach solving any new workflow need, any new problem in a world without limits. Awesome. Thank you, Anna. You've just seen a demonstration, taking you through the model or agent, what we can do with the MCP connector through the Notion, the analyst agent and frames, being very much the front runner and the highlight of this. We're gonna spend a little bit of time on questions, that you've been asking throughout and any additional questions that you have. Welcome to the stage our head of education, Terry Artsmith, who will help facilitate this. While she's coming to stage, I do wanna jump in on a couple of the questions that I saw. There was one question about the what does frames cost and who is it available to? First off, frames will be available in open beta to all customers on September 28, so six days from today. Some folks have it available already in closed beta, as we've been doing testing and rolling this out and get and soliciting feedback. But next week, it'll be turned on for everyone. Although, it does require that you do have AI turned on in your pigment system. And so if that is not the case, I'm very happy to help you, change that. And we can change that via a support ticket, and then we can turn it on for your for your organization. Also, as it relates to cost, the creation of a frame is going to use model or agent AI credits. When you're when you're putting the prompt in and running that, that will consume those credits. The usage of a frame will not cost anything. And any of your users who have the right data access and the right frame or board access to see it can use that with their existing licenses. It's not going to to have a recurring, AI, credit cost for just the usage of it. Couple other questions around how efficiently can you create a frame. If you write a perfect prompt, will you get the boards that, Anna showed you and the frames that Anna showed you? Yeah. If if your if your if your prompt is really well, articulated. And if you want examples of that, go check out the hollow frames. We'll put up the QR code here in a second, and we'll we'll we'll share the the URL in chat. But there are examples of frames available on the pigment website that you can interact with, and each of those has a really well done prompt that will generate that frame. I'll tell you though in practice because I build frames every day, I almost always favor the iterative approach. And I start off with, I want a chart that looks like this, and then I see it, and then I react to it, and I iterate through. it over the course of a number of prompts. I think that is a pretty common, method that you'll see. So I kick us off on questions. Terry, where should we go now? Yeah. I mean, just to to reiterate too with with the iteration, I mean, that's how I approach building frames, and I build a lot of frames as well. But sharing context, sharing visuals, some of those best practices are already documented in some of the content that we shared on community for for frames. So check that out. Check out the hall of frames link. But I think one of the, different themes in a couple of questions that is is coming together and something that we've talked a lot about at Pigments is the perspective on when to use frames versus boards. How how do they interact? Are they specialized? Let's let's talk about that for a second. Sure. So You know yeah. Sorry. I'll I'll I'll start and then please, jump in if I if I miss it. There are certain users that are going to want the the pivot interface, the certain charging interface, some of the drill down capabilities that you have in a pigment board. Is it every user? I think we all know the answer that not all users, even if the pigment user interface is easy to use, some users, you know, just aren't gonna get there. So some some personas are gonna prefer those capabilities that exist in a pigment board today and have existed for for years, inside of pigment. Where I where I would use frames is when I need to hit one of those use cases that Anna showed in her demonstration today. I wanna create a presentation that I want to be live against my my pigment information. I wanna create that in that intake form of information that is super prescriptive to my users about what they wanna do, or I wanna be very creative and I wanna create a new visualization that shows something about my business in a way that I haven't been able to do before. Final thing I'll say about this is you don't necessarily have to make the decision yourself. If you express your intent to the modeler agent, hey. This is what I wanna do, it will recommend to you, oh, that should be a board or that should be a frame. And then you can just say, great. Go. And it'll go build it for you. Yeah. And that's exactly what what I was gonna say. When in doubt, ask the model or agent. It honestly has a really good perspective on what should be a board versus a frame. So just ask it if you're in doubt. It's a really good question too that just came through in chat, about driving user access. We have permission metrics on existing permit on existing pigment dashboards. How do we control access on frames as well? Sure. It works essentially the same as how it works on boards. So first, your data access is always respected. So if I'm only allowed only allowed to see The US in my data, it doesn't matter if I'm in a frame, if I'm in a board, or if I'm drilling down into the metric, I'm only gonna be able to see The US. And Ramon might be able to see friends, you know, in in when he looks at that exact same, board or that frame. There's also board level and frame level access to whether or not I can even see the existence of this board or frame. So that works the same way as it does in boards today. And that's that's pretty important to have because you don't just want to you don't wanna show your users a whole bunch of frames or a whole bunch of boards for that matter that they don't have any data access to. So it's nice to be able to have that that two layered approach so that you can curate the experience for your users. We've had a couple of questions about how that iterative process and the editing works with with frames, whether it always has to go through the model or agent or can, can frames be edited a little bit more directly like you can do in pigment boards. So I can start out. You absolutely. If, if you've got some knowledge of JavaScript, you do have the ability once you've created the the first frame prompted the model or agent for the first time to go in, reveal the JavaScript, and make edits directly, directly there. It does require that you know a little bit about JavaScript in order to to do that, though. Yep. Echo that. I've done it one time out of the 50 to a 100 frames that I've created. It's it's just so much faster just to tell the model agent, oh, I need to change this or that. Now maybe, I I I do think we will be looking at how do we make that process better, going forward. But for now, I would as as a user myself that is using Figma every hour of every day, I would use the model agent for those types of changes. I'm just scanning through the q and a. I think a lot of them, especially, like, Ramon from our product team has done a fantastic job of answering a lot of the, the questions live. So I'm not really seeing anything that hasn't been answered at this point. I have one, that I wanted to it touches on a couple different chats, in a diff in a different way. And there was a nice question here about implementation time frames, and do we think frames will will will change that? And I think in short, the answer is yes. And but let me explain why that is the case. There was also a question earlier about does frames build off off of existing metrics and boards and lists and things like that. And the and these two things tie together. When you use the modeler agent, you can create new metrics as part of what you're asking it to do, and then frames can then show that. It's the probably the most common way that I actually use it is I will go into the model or agent in a pigment, in my in our pigment, workspace, and I'll ask a question and I'll say, give me that answer visually in frames. And it'll go and it'll pull information from lots of different applications, and sometimes it needs to create metrics to calculate things along the way. Now the reason that that is tied to implementation time frames is because it allows you to put together a what might be in your head, of the intent of how you want your implementation to work. And frames gives you a really nice canvas to be working on to say, this is what I want my users to see, and then I can build back from that. And and I do think that will speed up implementations. Because one of the hardest parts of implementations for the last twenty plus years that I've been involved in these is figuring out exactly what you and your business need and translating that to what the what the system can do. And now with the modeler agent, bringing in all the contextual information, bringing in the Notion information, visual visualizing that in frames, you can accelerate that that aspect. Dating yourself a little bit. One kind of tactical, but I think really important, question, where is frames gonna live within the application? You're you're spot on with your question, Carson. It is going to be added as a section in your left hand navigation right along with, with boards and blocks. So you'll see that show up if you have the model or agent already enabled. You'll see it show up in your applications starting, Monday for open beta. Okay. So as we're getting towards the end of questions, we will follow-up on any questions that we didn't get to, just to to make sure that that answers are there. Wanted to remind everyone that you can check these things out for yourself. Whether or not frames is enabled on your workspace right now or not, it will be next week as I said. You can go check it out right now. You can go to the Hall Of Frames on this QR code or if you just wanna find it on the website and you can interact with a bunch of frames there. As I said, they all do come with a prompt as well that will generate something in the style of that frame that you can then use in your workspaces when it is available. I encourage everyone to check this out. And then next week when it's turned on for you, to apply apply this in your own creativity and your own needs within your workspace. Okay. Terry, have we covered everything? Yeah. I think just one more thing. There's a few questions coming through about best practices and how to use it. So we will be launching, user documentation on our knowledge base at the same time that frames goes open beta on Monday. So check out that documentation. Give us feedback on that. I think a lot of the questions, that are being asked right now will be answered in that documentation as well. But, but with that, like the slide says, can't wait to see what you all build. Alright. Well, thank you everyone for joining us today. It was really nice to see over 200 people, yeah, here for this webinar. Really excited to see what you build, and, and and and we'll follow-up with recordings hereafter. Thanks, everyone.