Video: 2026 Product Roadmap | Duration: 3524s | Summary: 2026 Product Roadmap | Chapters: Welcome and Introduction (8.32s), Introducing the Presenter (152.06s), Grid Reports Enhancements (291.39s), AI-Powered Data Analysis (555.505s), AI-Powered App Building (727.75s), Governance Features Overview (1060.405s), Database Structure Analysis (1883.675s), Data Analysis Capabilities (1964.915s), AI Analysis Accuracy (2110.46s), AI Data Security (2271.505s), AI Agent Implementation (2582.55s), Q&A Session Conclusion (2788.72s), AI Security Considerations (2927.775s), AI and Permissions (3085.745s), Concluding Q&A Session (3410.7s)
Transcript for "2026 Product Roadmap":
Hi, everyone. Welcome to today's webinar where we are going to be covering our 2026 product road map. We are gonna get started in just a minute here. I see a lot of you are dropping in the chat where you're joining us from, which is always super fun for us to see. As someone who's located in Minnesota, I'm super jealous of all of you who are joining us from the South and aren't dealing with any of the snow or the cold that we've all had over the last, week or so here. So, before we dive in and I turn it over to our product experts, just a few housekeeping items for today's webinar. First of all, we are recording this session right now, and this will be distributed to you, about twenty four hours after the sessions conclude. So if you have to leave early, need to revisit anything, send this on to any of your coworkers, absolutely, you are free to do so when that recording comes through. Be on the lookout for that to hit your email inboxes tomorrow. Now, of course, we are kind of walking through our product road map today. We're really you know, have a lot of content to present to all of you for what's to come throughout this year, but we do want to make sure that this is interactive as interactive as possible. So we do have some time for question and answer at the end. So please feel free at any time throughout the presentation today to submit your questions. You should see a q and a tab right within the webinar platform here. Feel free to submit those questions at any time, and we will get to as many as we can at the end of the session today. If we're not able to get to your questions specifically, we will have someone follow-up with you directly later this week to make sure that all those questions get answered. Final thing before we dive into our product road map webinar, we are giving away a free ticket to Empower today. So that is our annual event. That is this May in Houston, Texas. If you haven't heard from it heard about it, I'm seeing a lot of people in the chat from Texas, which is great. So I love to see a lot of people in that area. But we will be randomly selecting one live attendee of today's webinar, and we will be notifying that winner later today because early bird pricing for Empower does end this week. So we wanna make sure that if you are not the lucky winner on today's webinar, you still have time to sign up to join us in Houston at Empower in May at the lowest possible price, as early bird pricing again ends on January 31. I believe that is all of the housekeeping announcements that I have. So I am going to turn it over to our expert of the day. Please welcome Alice Rich. Awesome. Thank you so much, Charlie. And hey, folks. Thank you so much for joining me today for our 2026 product road map webinar. As Charlie mentioned, my name is Alice Rich, and I'm a senior manager of product here at Quickbase. I focus on user experience and platform usability. And recently, I've been spending a lot of my time working on grid reports. So I'm really excited to walk you through what's coming next for Quickbase and Fastfield in 2026. Here is our agenda for the session today. We will start with a quick look back at what we shipped in 2025, then I'll share our 2026 vision and the road map pillars that we're organizing our workaround. After that, I'll walk through the key features under each pillar, and then I'll do a couple of demos, and we'll close with some q and a. Alright. Before we dive in, I do just wanna quickly also flash this slide. This is just our usual safe harbor slide. Just means that everything we share today is subject to change, and what you eventually see implemented may not be exactly what you see in this presentation. So without further ado, let's dive in. To start, I want to ground us in the Quickbase platform vision. Quickbase aims to be the AI powered operations platform you can tailor to fit your unique processes, not the other way around. We wanna give you a tool that you can customize easily to reflect the way that your processes work, not try to fit your process into a tool. And there are four areas that we're focused on to make that happen. The first is connecting data. We wanna make it easy for you to bring in the data that matters from wherever it lives. The second is automating repetitive tasks. We have lots of tools available so you can let the platform do the heavy lifting there while your team's focus on higher value work. Third is analyzing for action. Quickbase has always given you real time visibility into your operational data. Now with tools like data analyzer and Quickbase, the Quickbase AI agent and our updated report capabilities that we'll talk about today, we're making it easier than ever to spot trends and predict problems before they happen. Last but not least is governing at scale. As ever, ensuring admins have the controls to safely govern your apps as you grow, including find grain permissions and audit logs is core to our experience. Everything we build is in service to helping you accomplish these four key goals faster. Now before we look at twenty twenty six, again, that quick flashback to last year. In 2025, we shipped a lot of great capabilities that set the foundation for the work you'll see this year. Grid reports went into open beta. We added 15 new chart types. We improved pipeline error notifications. We brought our new form experience to mobile, and we made major strides with our AI capabilities. There is a ton of other great stuff in here that I'm not gonna have a chance to get into right now. But if you want more details on everything we shipped, you can check out our year end review webinar from December. Believe that's linked in our resources for this session as well. Alright. Now looking to 2026, we grouped the features we're gonna talk about today into these three categories. First is boosting your team's productivity. This is gonna be where we'll talk about features that help end users get more done. Second is making building easier. These will be tools that help builders iterate and quickly adjust. Third is making it easier to govern. These are gonna be admin and security investments to help you scale safely. Now let's dive into each of these categories. First up is end user productivity. And first feature is the one that is nearest and dearest to my heart, which is grid reports. Grid reports, if you haven't heard, are the next evolution of quick based table reports. Our goal with this project was to make everyday interactions with your table reports feel familiar and fast for people coming from tools like Excel. You can double click to edit in line. You can fill down to repeat values. You can drag to reorder columns or pin columns or auto size your columns just like you would in a spreadsheet. And all those preferences are remembered so users don't have to keep reconfiguring their views in widgets and on forms and dashboards, you know, when you keep coming back to them. So notably, when you adjust a column width on an embedded report, it will be remembered the next time you come back. Grid reports are also editable in embedded reports on forms and widgets forms and dashboards, which unlocks an entirely new category of use cases that weren't possible before with our new form experience. Also, roles and permissions are respected exactly as they are today. If someone can't edit data in the table today, they won't be able to after you enable grid reports either. To access these, grid reports are available for everyone today. To try them out, you just go to app properties and select yes in the drop down to titled used grid reports in this app. If you haven't tried them out, I highly encourage you to do so. Later this year, they will become the default experience, so you'll wanna make sure you've tried them out before then. I'll do a little grid reports demo at the end here to show off some of these features and show you how to enable them as well. Next up, we have a handful of FastField features. If you're new to FastField, let me give you a little refresher. A few years ago, we acquired FastField because we believed that field connectivity was a really important piece of who Quickbase is. Quickbase has always been really strong on the back office side of operations, but we're also hearing a big need for a mobile first, like, on the front lines in the field solution as well. And at the same time, Fastfield needed an enterprise grade back end to help them scale. Since then, we've been investing to tightly integrate FastField and Quickbase so teams get that powerful capture dispatch and automation tooling that feeds directly into the analytics automations and governance you already run with Quickbase. Alright. Now to get to these enhancements. First up, we have label scanner. For teams capturing information in the field, reducing that manual typing is a massive benefit. Label scanner turns a photo of a barcode or a serial number or a printed label into actually usable data instantly. Instead of having to type those long strings of data, users are simply able to scan that and our OCR is actually gonna write those values into the field. That's gonna speed up inspections and remove transcription errors. And it's especially useful when your crews are under time pressure or they're working in noisy or otherwise chaotic environments. This is available today on the FastField Pro Plan. To access that, you can use the new OCR scan button in the bottom left, and the data is gonna auto populate into your relevant fields. Next up, another fast field feature, our asset and team tracker. Once you can capture that data, the next problem is visibility. Who is where and what is happening? The asset and team tracker gives you a real time map of crews and equipment. You can assign tasks from the map, set asset locations at a glance, and monitor on the ground operations so supervisors can reallocate resources as priorities change. That cuts back on wasted travel and keeps jobs on schedule. This one is still in development though, so watch our release notes for an availability announcement. Next up is another fast field feature, AI photo insights. This is actually a a massive time saver. Once you have a photo in your form, once you have that data populated, the AI will actually analyze the image and videos from your forms to detect and surface issues automatically. Example, if you have damaged equipment or missing PPE or other compliance problems, rather than leaving those static images as attachments that someone has to manually review, the AI will proactively flag problems and trigger follow ups in real time so your teams can actually act faster on those. So really skips a step there. This one is also still in development. So again, watch our release notes for an availability announcement. You can also talk to your account teams to make sure they know you're interested and can let you know as soon as those are available. One more fast field feature in this section, AI workflows. Once you detect those issues or the AI does, and you need to make sure the right follow ups are in place. AI workflow will automate the routing reviews and alerts and give a smart summary of all your form submissions. So it kind of knows where you need these things to go. So instead of those, like, simple rigidly defined rules only flows that you'd say, if this, then then then this, and it's kind of one directional, The AI will actually decide the next step for you. It'll summarize that content and trigger notifications to the right people on your team so those critical issues get attention faster. This one is available now on the pro plan and above. You can talk to your account teams about how to get access there. Next up is data analyzer. All that operational data that you've been inputting into your app is only as good as the insights you can get from it. Data analyzer is a super cool feature that lets anyone build a custom machine learning model from data already in Quickbase. You just set up in the UI, the table, and the outcome that you care about, like predicting which orders are likely to ship late or which projects are over budget, like in the example here. And data analyzer does the heavy lifting. It will train a model, highlight the handful of fields that matter to your chosen outcome, and whether they increase or decrease the risk of that happening. It will also give you a confidence score so you know how much to trust the result. Once that's generated as well, then you have a field that is available. It's live in your application. You can use it to trigger notifications or pipelines. What I love most about this feature is that it's really designed to be approachable. The UI makes it super simple to set up, which allows anyone to operationalize these predictions in your apps without being a data scientist or having that kind of background. This is available in beta as part of the Quickbase intelligence package. Talk to your account team about how they can help you get access to this one. That wraps wraps up our end user focused feature set. And here's a slide that you can reference after this presentation is over, which includes not only the features we just reviewed, but a ton of other features as well that were really helpful that we released in 2025 aimed at driving end user productivity as well. Next, we will move on to talking about features that speed app building. And first is another really cool AI feature. First is AI spreadsheet import. If you haven't tried this, I really encourage you to do so because it is really a game changer, especially if you have a new app that you need to stand up from a process process that is currently operating in a spreadsheet. You just upload that spreadsheet to AI spreadsheet import, and it's gonna take that static spreadsheet and automatically transform it into a connected Quickbase app in just a few minutes. The AI is gonna automatically propose a table structure and map your columns to fields as part of that import process. And it also creates different assets like forms and reports, which automatically gives you, like, a fully built out app that you can iterate on and saves a ton of time since you didn't have to manually build out each piece. It is it is quite good at mapping that structure that you had in your spreadsheet. So, again, I encourage everyone to try this out. It's available now. You can find the import tool in the little AI sparkle in the toolbar at the top in the nav bar. Even if you don't have a need, try it out so that next time you do have a need, you're ready and you know how to do this. Next up is AI actions. AI actions let you automatically extract data from documents and emails or create records or summarize records all as part of your pipelines. It has this, like, document understanding built in, so you don't need to write any complicated, like, extraction code or configure any API keys to or train a model to do all of this. This is just built in. You just configure a step in your pipeline, choose this AI step, and the platform extracts and routes that information for you. This is available in beta at the moment. So, again, talk to your account team about how they can help you get access there. The next AI feature is actually the feature that I'm most excited about on this entire list and this entire presentation. No shade to grid reports, but this one is so cool. The AI agent is a conversational interface that combines all of our platforms AI skills in one location. You can use it for data analysis or to help you build, actually. So this one crosses into our last section of end user productivity as well. But just by act asking natural language questions, just by chatting with the agent, you can look in one particular app or you can look across apps to pull together relevant data to build reports or visualizations, or even take actions like creating records or building new fields or setting up relationships in your application all based on that data. It also understands context across different apps and will plug into AI actions and data analyzer that we just mentioned as well. They can give you analysis and outcomes in that sense. It personally saves me so much time in my day to day. We'll include this one in the demo at the end as well because it's it's pretty slick. This one is also in beta, so definitely talk to your account teams about how to get access there. Next up, we have a few pipeline focus enhancements. And first on our list is another round improvements to troubleshooting tools. We shipped the first set of troubleshooting improvements last year in June. You are already seeing more descriptive error emails now sent to realm admins as well as pipeline owners. Those have time stamps and step level context for failures and an activity log exports you can search and share diagnostics. What we're working on next is deeper level, step level error handling, retry mechanisms, and an AI assisted debugging tool to make it even faster to find and fix issues. Again, some of these enhancements are already available, like I just mentioned, but the remaining items are rolling out over the first half of this year. So keep an eye on our release notes for more information there. Next up is the NetSuite channel for pipelines. This one is pretty straightforward. We're adding a new NetSuite native channel, so your financial customer and inventory records can flow easily between NetSuite and Quickbase in real time. That'll result in fewer manual syncs, fewer errors, and faster, more accurate decisions for you. This one's still in development, so watch our release notes for deploy timeline there. Next up, AI workflows and pipelines. AI workflows lets you describe what you wanna build in pipelines, and it will set it up for you. It'll generate a fully configured pipeline, no manual field mapping or step by step setup required. This is really great for people who aren't as proficient in pipelines like me, and it really unlocks these automation capabilities for this group of people that it wasn't really accessible for without a lot of setup or help or, you know, studying, to be required there. Even if you're already experienced in pipelines and you're really good at it, it can also be a great time saver to help you set those up as well. This is available now as part of the smart builder workflow in pipeline, so I encourage folks to go try that out as well. And the last feature in this section, builder focused features, I wanna mention the new suite of extensions that is now available to users natively under the Quickbase umbrella. Last year, Quickbase acquired our longtime partner, Juiced Technologies, who have long been known for their extensions like ExactForms Plus, which allows you to generate highly complex documents and gives you pixel by pixel control over how those how those look. Or Juiced Sign, which integrates an esignature capability easily into your Quickbase data, or QB Maps that provides robust map visualization in Google Maps from your Quickbase data. These are all available now. You can talk to your account teams about how to get access there. And to learn more and deep dive into each of these, we are actually hosting a webinar next week on this topic. And I think Emma and Charlie will share more info in the chat about that as well. That is our last builder focused feature here. And there, you can see on this slide is so much more that I won't have time to get to today. But this is included here so you can take a screenshot and refer to it later. And our last section, we're gonna talk about governance features before we move into the demo. Our first up governance feature is a native interface for ALM. Previously, to leverage our application life cycle management capabilities, you had to be quite technical, and you had to leverage our API or a complex solution life cycle manager setup. Now we're providing a native visual user experience that you can use to set up your dev test prod environments and move changes between them without any of that complex API tooling or setup. It provides clear, auditable deployment paths and visibility into exactly what's being deployed so you can test safely, reduce rollout risk, and make releases repeatable. I cannot stress how much this lowers the bar to entry and simplifies our ALM workflows, which is really exciting for a massive chunk of our base that this wasn't really accessible to before. This one is available in beta very newly. You can sign up in our beta registration app, which is included in the links, the resources for this session as well. And that is really exciting. So go check that out if ALM is something that you would be interested in. Sign up for that beta to get access to this. Next up, if I can move to the next slide. There we go. This has been available for a while, our redesigned account summary page, but it was such a big improvement I wanted to call it out. The redesigned account summary page basically provides you more of a one stop shop for all of the information that you care about, for your account. All your billing, renewal dates, license, and quota consumption, and all of the apps driving most of your usage. You can see all of that in this one easy to scan page. It also surfaces a lot of links that might be helpful, like, to support or your billing details or a lot of common admin questions so you don't have to hunt across all of your many admin screens to answer some of those basic questions. This is available now. Just go to your admin console and click on account summary to view that new page. Last but not least, before we get into the demo, I wanted to mention AI app intelligence. That one is, available in beta now. And this one basically gives you an overview of your application generated by AI. So take the burden off of you in terms of documentation and understanding your application. It can also be really great for new users if you have recently, like, taken ownership of an application or you are kind of one of those accidental app admins. You need to get up to speed with an application very quickly, this can be a really valuable tool for you. It is available through your app settings, and it will just generate that for you. It can also make app audits a lot easier and really take the guesswork out of that as well. This is available in beta. Again, you could talk to your account team for more information on how to set that up. And that is my last feature for our feature highlights. Again, I'll pause on this governance slide as well in case you wanna take a screenshot to understand all of the other features that we have made available over this last year as well. And that's actually it for future highlights before we move into the demo. And I'm sure folks would love a break from the slides. So I'm gonna shift gears, and we're gonna do a little demo. I know this is a roadmap presentation, but I couldn't help myself, and I think this will be fun. So first up on grid reports, I wanna just call out and show you guys a little bit of what we got going on here. So Grid reports, again, our goal was to bring a more intuitive spreadsheet like experience to the platform and make them work more like users expect, especially for users coming from things like Excel. That encompasses both viewing and editing data. So, you know, I wanna just go ahead and double click, make this easy. I'm just gonna go ahead and I'm gonna change the priority here to medium. That one's already completed. Maybe this one, let's change the status from accepted to in progress. And you could see that was so seamless for me to move from view into edit mode. I just double clicked, and then I can go ahead and save those changes. Before I do, I wanna call out that you'll notice that this there's this little blue notch in the upper left hand corner of cells that I've edited that haven't yet been saved. But let's just go ahead and save those. That was so easy. Straightforward. I didn't have to lose my context like sometimes you have to do today with grid edit. And because I know it's top of mind, I wanna reinforce that permissions message again. I know, everyone, this is so foundational. I make sure that this message really gets through. If your users can't edit certain records or don't have permission to use Grid Edit at all today, no worries. Those same rules are still gonna apply once you turn Grid reports on in your application. We're respecting everything in exactly the same way. We've built everything on top of that foundation to make the transition to grid reports easy, and smooth. Next, I wanna highlight a couple other cool pieces of functionality that we've added. Let's talk about filtering. So for column filters, you still have a filter available with each field, But now we're giving you two new options. So you can either use one of these operator filters. Like, if you wanna say where the priority is not blank and where it contains high, you can actually stack these. You can stack up to 10 levels of conditions here. And you have all of these different operators to choose from, which is super powerful and something that was never available before. Can easily reset those. And you also have a pick list that you can choose from for fields where it's relevant. You know, I can easily say, actually, just show me low, You know? And that is very straightforward and, again, really familiar. That interaction is pretty obvious as well. So I'll just reset that. And while I'm talking about filters, I wanna mention that the dynamic filters for your report have moved over here to the right. If they were on the top, these are the exact same fields that you saw before, but we just moved them into this panel on the right. If I apply a filter, say, I wanna see only in progress work orders, it's gonna stay in sync if you have a field that is listed both on the report and in your dynamic filters. It keeps those in sync so you can see wherever you are that that filter is in effect. And I'm just gonna go ahead. You can also, of course, save those back to your report settings just as you could before, or you can save it as a new report or revert back to your last saved report state, which is what I'm gonna do here. And then, I mentioned fill down in the kind of presentation, but I am it's really easy to do here as well. If I just grab this little corner, I can go ahead and fill all those down to repeat that value. You If had a numeric value that you wanted to increment. You can also do that by highlight, like, one, two, three and drag, and you'd be able to count, you know, four, five, six. I'm just gonna go ahead and save that. You'll also notice if I just make that change, wanted to highlight also that we have undo and redo natively. Keyboard shortcuts also work. Again, that's something that you just expect to work out of the box, but just wanna highlight that that's there. And I wanna call out performance as well. This is something that we really focused on with Grid reports. They have an incredibly high bar that we set internally in terms of performance. So they're built to handle the scale of your largest applications. This report just has, you know, 45 little records in it, but we can handle hundreds of thousands of records. So if you do ever try Grid reports and wanna and run into a performance problem, please let us know because we have built them with performance in mind. Other cool new functionality, you can also now pin columns. So if I go to the column menu, I'm gonna hover over this and say that I wanna pin that to the left. Then that's gonna be frozen as I scroll here. Maybe I wanna pin status to the right. You can also do that. And you can pin more columns. You can pin as much as you want to your heart's content, and those are fully customizable by the builder. So once you have this set up, you can go ahead and save that to your report settings so that your users, as they come into the report, they will have that view right away. And you rest assured that they will see what you want them to see. And we're also bringing back a fan favorite feature interaction. You can now drag directly on the report to reorder your columns, which is really useful. And in terms of other interactions, we are bringing a whole host of new ways that you can actually display the columns that you want in the order you want on your report without ever having to go back into report settings as well. So if I wanna hide a column, I can just say, actually, I don't want this notes field to display over here and it's removed from my report. Or maybe I do actually want to see the, you know, date created for each of these records, for example. And I can actually go ahead and move that into my report and place that wherever I want it to be. Let's just move it up here so we see the change visually. And then I can still obviously move it back and forth here, and it updates in the column as well, the columns menu over here. This menu, you can also make it wider if you have some really long field names as I know a lot of folks do. You can also remove or add grouping here, which is something that was also never possible before, which is pretty cool. I'm gonna just revert that back to my normal report state as well. And now we have a are introducing a couple new behaviors as well. I wanna talk about column widths and row heights. In grid reports, instead of trying to guess what you wanna see, we're giving you more control both as the builder and the end user. So builders first can start with they can set default field widths in field properties here. So you can specify a default column width here. You specify that in pixels so you know exactly what your users are getting no matter if they're on a smaller or larger screen than you. So you set that up and you, each of your users will see that the first time they enter a report, and then they have the ability to adjust either manually by dragging the column. They can adjust the column width that way, or they can choose to auto size this column or auto size all the columns on the report. And we will remember those adjustments the next time they come back into the report as well, and they'll be able to have those remembered. And notably, even if they set those on an embedded report in a form or a dashboard, we will also remember those there. For row heights, the story is similar. You can specify as a builder in your report settings what you want your default row height to be. Just in the report setting here, this is the menu. You can set this up at a table level to say, hey, this is my default row height for this table should be short or it should be, you know, maybe it should be five lines tall. And then in each report settings, you can either choose to inherit or override that. And you can say, actually, I want this one to be three lines tall. And your users will see that by default. Then they can adjust themselves on the front of the report if they say, actually, you know, I want a little bit more space. I need to make sure that I see all of the ZIP codes in line here, and I don't want to make that column wider, for example. So that is another option that's available. While I'm talking about report settings, one more thing I wanna mention here. We are also now that we've made it easier than ever for you to edit, we also wanna make it easier than ever for you to control where things are editable. So we have added this option to say if inline editing is available on this report or not. You can set this again following the same pattern, default report settings. You can say if inline editing is available on this table or and then you can inherit or override that on each individual report. So you have just a really easy, one stop shop where you can say, are records editable from this report or not? And I've saved kind of the best for last here in embedded reports. I mentioned that grid reports are also editable. So let's go to a table that is a parent that has some children records in it here. So the easy piece here, I can just go in and I can say, actually, I need to edit this email address. It should actually be my email. And I can edit that, embedded report here in line with this form and just go ahead and save. And it is that easy. To enable grid reports, you just go into app properties. If I just use the context menu here, I'm gonna go to app properties, and then I will choose yes in the drop down titled use new grid reports in this application, and then you click save. That makes them available for everyone in your application. And, again, I encourage everyone to give this a try since grid reports are gonna become the default experience later this year. And that's it for Grid reports. At this point, I'm gonna ask Ryan to come on stage with me as I switch gears to demo the AI agent. Hey, Ryan. How's it going? Hey, Alice. Well, thanks for letting me crash your party. Yeah. I'm excited to have another voice here talking. That's not just me. I'm really excited to show off the AI agent. It's not something that I get to demo a lot, and I think it's super cool. It's very easy to use. You're gonna do great. it's so easy to use as long as I can type this correctly, which is a debate. But a little bit of a look behind the curtain here into this demo app. This is an app that I don't really know too much about. It's super full featured. And from our solutions consultants team, they shared this with me. So I've not explored every little nook and cranny of this application. And I'm guessing, again, that mirrors the situation lots of you have found yourselves in when you have, like, inherited an app that was already built and running a mission critical process for you, but you didn't know kind of where to start. You can throw in the chat if you've ever found yourself in that situation. But luckily, we have some awesome new AI tools to help us get started here. So I'm gonna prompt the a the agent here to say, hey. I'm a new admin taking over this app. Management of this app. Can you give me an overview of the main processes and how it's constructed? That's gonna think for a minute. I'm gonna make this full screen so we can really focus on it. Ryan, you wanna tell me a little bit more about what it's doing. while it's thinking here? Yeah. So, the agent is gonna start by looking at the structure of the application. So it's gonna look at the tables, the relationships, and the fields within them, and then build a summary, of the of the structure of the app. Yeah, and came back with an answer pretty quickly. I had. more on that talk track. really quickly. That was really quickly. Alright. So we've got yep. Work orders table. Okay. Wait. Oh, it's asking me another question now. Okay. What do I like to start with? Let's start with work orders. That's where I wanna focus in on here. Well, typo, but it'll know what I mean. Yeah. It's the best part about demoing this. Like, it it figures out on the typos. It's very forgiving. Absolutely. Yeah. Let's let's talk about the table structure. Pretty cool. I wanna get into the data as well in a minute, so we'll get into that second bullet point too. Alright. Let's see what if it what it can tell me about kind of the broader picture of how this is set up. Work orders is my top table. Okay. I'll let it load so we don't get all. Alright. Okay. Relates to customers and tasks. Sure. Makes perfect sense. Then we've got employees that okay. Have sites and shifts and messages and incident reports. Makes total sense. I can totally understand how that's going. Nice. Okay. That's straightforward. Alright. Now I wanna I wanna get into the data analysis piece of this a little bit. So we know we're focused on work orders. Now let's see what areas we need to focus on. I cheated and copy pasted this one. So what's the average time to complete my work orders by type? Let's see what it can do to dig into the data for me here. Great. So, again, just like the agent can go off and analyze the structure of an application, we've also given it the ability to write queries. So based on what it learned from how the app was constructed, it's gonna, write some, queries on the back end, analyze the raw data that comes back, and then synthesize what it's learned. Nice. Thanks. Very cool. Yeah. Alright. Fourteen and a half days to complete. Got some orders with data. I think some of this are some of this is, like, data hygiene in this test app kind of situation. That's pretty forgiving here. That's very cool. Okay. Yeah. One thing I like, and we hear this a lot from our our builders is sometimes their users, like they they get into an app, they answer the question, but they don't necessarily know what to do next. So we've asked the agent to ask or prompt the user for some additional tasks that they could do based on the information they've received. So you can see that at the bottom. Hey. Do you wanna analyze. task level completion times, or do you wanna look at this by priority level or see what work orders are currently under, overdue? Nice. Yeah. Yeah. And think building on that one. I kinda I wanna see what contributes to, like, making something successful or not. mhmm. Yeah. Very cool. That is definitely helpful. Oh, I meant to say work order completion. Oops. Gonna tell me patterns broadly for the whole application. We can dig into that. And, again, one of the, challenges we've heard from our our builders specifically is that their users require lots of different, like, data visualization views in order to accomplish their tasks, and it can sometimes change really, really frequently, which puts a lot of pressure on our builders to make sure that we have all the data in one place in order to drive that reporting. Like, I've gotta look up the work order status from, work orders down to tasks and then into activities in order to see, hey. What activities are we doing against in progress work orders? The agent is able to much more flexibly look across those tables for the end user and get to the same answer, that it would've if, you know, all of those relational fields were were brought down to the to the right level. Very cool. Ryan, Yeah. is there a way for me to interrupt it to say, hey. I meant to type this other thing? no. One, because that's just rude, and we'd like our agents to. But, no, we are we are working on it now. Yeah. Nice. That would be. that would be really helpful. Yep. And there are there are two things that I I kinda wanna draw attention to because I've seen a couple of comments in the chat around, like, well, how can we ensure that the answers are accurate that the AI gives you? First thing, AI is gonna make mistakes just like human beings make mistakes. It it happens, especially in cases where there's a lot of different or similarly named fields. Like, we have status and status. override, order status, it could get confused. So we've done two things. One, we've exposed the thinking. So you can see, the steps that the agent is gonna take before it goes off and and makes the analysis. The other thing we're doing is trying to include links back to the source records, so that you can validate. So, you know, at the you can see, hey. Yeah. We have two sources here. We pulled it from our work orders table and our tasks table. We'll give you a quick insight into, you know, where the agent was sourcing the information and the fields that it used. Nice. So I asked a much broader question than I meant to ask it. Mhmm. But I'm really it's I'm interested to take into kind of some of this. Yeah. I mean, that's a really chunky query when you think about it. was. Like, Yeah. you essentially asked it, like, look at my data and figure out what's wrong with my processes, I did. would take a human a long time to figure out. Like, we could hire a consultant, you know, and they'll build. us a PowerPoint to figure that out. Our agent kind of helps streamline that a a little bit. So, what it thought were really good, barometers to use here were like, well, let's sort of stratify the work orders by operational work orders or customer facing work orders. Then let's. look at the priority disparity and see if there's any difference between completion rates. And we can see, like, hey. Our customer facing high priority work orders are not completing very frequently. doing good. Percent. of them. And 21% of them are delayed. So this is just, I I hope that our our builders and our users kind of see the potential here for being able to conduct lots of deep data analysis without needing to do that, like, quick based gymnastics to get all data summarized up to one level or to build the summary of the summary table in order to stratify some of this information. We're using pretty neat techniques behind the scenes to ensure that the data that you get back is accurate. And, yeah, always, looking forward to hearing how our folks, plan to use tools like this for sure. Very cool. Very cool. I think that's all I had for the demo portion, Ryan, unless there's anything else you want me to highlight here. Well, there's so much more in the box here. Mhmm. I don't think we have time to to go through all of it. But, our agent in in general, we've given tools to analyze data like what we're seeing right now, understand the structure of the application, which is really, really helpful when making some of these deeper queries. It also can modify applications by creating new tables, fields, relationships, even formulas, and you can add and modify records. So if Alice said, hey. For all those customer facing, you know, high priority. tasks, like, we need to go and alert all of the project managers or the the assigned users. Can you go create tasks for me? It can do that type of, like, on the fly data upload for you without you needing to either pull data out into Excel or go through quick based forms or group report one by one and start creating. Yeah. That's really powerful. Yeah. Absolutely. I've just scratched the surface of what this can do, and there's so much more here. But I do wanna leave some time for the q and a. So I think we should pop back over there, and we'll bring on a few more folks to the to the stage here. Welcome, Adam and Charlie back. Amazing. Yes. Thank you, Alice, for walking through all of that and Ryan for hopping in on the demo and now sticking around for q and a. So, yeah, we've got Alice, we've got Ryan, and we're now welcoming Adam to the stage as well, who is our product manager for FastSkills, to make sure that we can get answers to as many questions as we possibly can in the next nineteen minutes here, it looks like. So we have a ton of questions already flowing in. Feel free to continue to submit those questions in that q and a module. Again, we will respond to as many as we can. If we don't get to your question, we will make sure that someone follows up with you directly to make sure that you do get an answer to that question. And then real quick, Alice, I'm gonna have you go on to the next slide. One final reminder for me. Early bird pricing for Empower ends on January 31, which is only in four days, which is crazy. January absolutely flew by for me at least. So be sure to register. Again, we will pick one lucky winner of a free Empower pass who was a live attendee of today's webinar. We will let you guys know by the end of today who that winner is so that you can still take advantage of the early bird pricing, if you are not the winner from today's webinar. So with all of that said, let's dive into some questions. Again, there is a ton here, which is amazing. First question, I have clients who are apprehensive about using AI in their apps. Do you have documentation about how their data is used, stored, etcetera, to enable the AI tools? Yeah. Great question. Thank you, Sharon, for asking. I'm sure it's on the mind of of lots of folks. What, I have observed being in the AI space for a couple of years now is, like, the pendulum swings both ways. Like, there's lots of hype and excitement and, like, AI is gonna cure cancer, and we're gonna be able to do so much more with it. And then there's this reckoning of the pendulum swinging back the other way. Like, oh, no. What is it learning? Is my data safe and secure? And we're we're probably right about here now, and we'll swing back here in in another, you know, six or eight months. Mark my words. I think that we have taken a really responsible approach to introducing AI in Quickbase. At the end of the day, we are stewards of your data, and we wanna make sure that you trust us to do the right thing by you. So first and foremost, inputs, outputs, and any AI interactions are never used to train third party models in Quickbase, period. Full stop. We have really, really strict data processing agreements with our vendors who who help provide some of these services to ensure that nobody sees AI, like our customers use of AI. The second thing is our AI is isolated almost per tenant. So there's no risk in, prompts that you write being, leaked, for lack of a better word, to another customer who's asking about something tangential. The third thing is that Quickbase is a role based access control. So our permissions are always in play here, which means that when if a user asks a question about how many tasks that are currently in progress, but they can only see tasks that are assigned to them, that's the only data that the AI fetches. So we've put a lot of work into making sure that our agent and the user have the same level of information about the application to avoid scenarios that we hear, like, every three days in the news about AI leaking data, that that it shouldn't be. There is documentation in our trust center on how we approach responsible AI. I think we also have a white paper that we can we can share out. And, again, I think we're we're pretty overly transparent on what models we're using. That's gonna be available in our in our help center, and we'll have lots and lots more, materials as we get closer to GA with with Quickbase AI. So Excellent. Thanks, Ryan. I'm gonna follow this up with another AI question that we have here. Lots of pressure from leaders to enable AI agents that can answer questions. Their scenario is to allow a low propensity user to ask a question instead of going to one of the dashboards for super users. Yep. Speaking to the super users, they're sticking with dashboards. So where do we start? How do we train it? Yeah. Great question. Train is a is a very tricky word here. When we talk about training, we we don't mean, like, foundation model or frontier model training. We don't train any models here at Quickbase today. We use the latest and greatest from some of the leading research firms in this space. When you are interacting with the agent, you are, almost augmenting or enhancing the memory of the agent as you use it. So when we go back to what Alice had demoed earlier around, like, how does this application work? Well, the agent has tools to go understand the structure of the application. So it knows the tables, the fields, the relationships, and the key fields, in order to power a lot of the interactions that your end users will have. So it's learning almost on the fly. Now we do have plans, at some point in the near future to allow our super users or power users to augment the the knowledge layer of the AI with more, information that's specific to their business. Like, sure. We can learn the shape of a work order today through the schema, but we wanna teach the agent more about the process of how a work order should move through different stages of, completion. So that's on our road map, but you don't need to necessarily train the agent out of the box. It's actually really good at operating in an app it's never seen before like Alice, just showed today. Excellent. Thanks, Ryan. Looks like we've got a fast field question here for Adam. If you set up a recurring annual task that needs to be completed every October, are you able to edit the task for the current year with the scheduled date for the task? Yeah. So this is talking about our fast field scheduling feature, that we just released for the pro plan. Yeah. Great question. Once you set up a schedule and in this case, I believe it's asking about a recurring schedule. You can once the task is sent, you should be able to go in there and edit the specific specific due date. Now I think the there's a there's a start date, and then there's a due date. The start date is when it's actually sent out or dispatched. And then I think it's probably best to edit the due date after that, given it, like, a buffer of seven days or something like that if there's some variance in when you're wanting to, have the user actually, interact with that particular task and and submit it before before it's actually due. So whoever, sent that, please get in touch with me, and we can talk more about specifics of your particular use case, so that we make sure that we answer your your question. Perfect. Thank you, Adam. I just saw a new question pop in. I've seen this one a couple times. This one's for me. Can you share a recording for this session and the last last session? Yes. We will do that. We're recording this session right now. Be on the lookout for an email to your inbox from the Quickbase team tomorrow, and that will include both the recording for today's webinar and some follow-up resources to help with all of the stuff that we're talking about here today. Alright. Next one. Looks like it's about grid reports. Alice, I think this is when you were showing, the edit settings. Mhmm. Are those remembered at the user level or the report level? Good question. So for edit settings to con to say, is the data in this report, are you able to inline edit it or not? Do you set that at there's a hierarchy to the levels here. So you first set it at the table level in your default report settings. So you say I'm sorry. Actually, I'm gonna back up even more. You first set it in your role and permission settings. So you say, does the user in this role have permission to edit these fields in this table? So that is the first level. Then at the table level, you can say, for all of the reports on this table, the default setting is that inline editing is or isn't available. And then that is gonna be inherited to each of the reports in that table. And then on those reports, you can also make a choice. So you can say, is that are is this report able to be in line edited? And then that is kind of the last level there. So if any of the higher levels aren't available, if the user doesn't have permission, but the report says users can edit it, then they are not gonna be able to edit Or if the default says that you can't edit it, then you can actually choose to inherit or override that at the report level. But builders set that. They're the ones that have permission that have the ability to specify if inline editing is available or not. Hope that answered the question. Excellent. Thanks, Alice. We have a handful of questions here about grid report column headings. Can you or will you be able to wrap the column headings for longer titles? Yes. You will be able to. That is coming out really soon. We actually hope to deploy that in the next couple of days within this week. And if that doesn't quite happen, then we will get it with the February release. That's gonna be kind of our backstop there. So watch our release notes for that timing. That is coming very, very soon. We know that that was a really popular enhancement request. So that is coming really, really soon. Awesome. Love that. Alice, I'm gonna keep grilling you on grid reports here. for it. Let's see. This next one, is there a way to make the column widths save so on a refresh, they don't go back to the default? So they should save for you every time you, you know, adjust them and then they should be remembered on a refresh or if you leave and you come back, those should always stick for you. It should override the default actually. If they aren't sticking, then that's a problem you should submit a tech support case about so we can investigate it as a bug. If the only scenario that I know where it might not stick right now is if you adjust them and then navigate away, like, in under a second. You might wanna just, you know, breathe for one second, literally one second, and then it will be remembered for you the next time you come back. Perfect. And then a similar vein, when a user adjusts the column or row widths, is that just for their user, or does it impact everyone? Good question. So to adjust something for everyone, you have to be a builder and you have to be in field properties to say, hey. This default width is gonna be 500 pixels. That changes it for everyone. But if it's just me dragging my columns on my report, that is an an adjustment that is just for me as I'm seeing the report. Excellent. Alright. Let's see. We'll give Alice a break and hop into a couple more AI questions that we've got here. How is security considered with the click based AI versus using ChatGPT or other AI tools? Yeah. Mean, it's a it's a good question. So, again, just to, you know, not to sound like a broken record, but, our models or the the models that we use internally and the inputs and outputs and the interactions our users have with our AI aren't gonna be used for for training. Again, we've got pretty strict data processing agreements with with our vendors to make sure that that that doesn't happen. We're also running it, inside of Quickbase, for lack of a better word. So it's running on the same infrastructure that powers all of the other, features and capabilities that Alice just walked you through today. The I you know, using, the sort of more consumer facing, AI tools like ChatGPT or Plot or or Gemini, I mean, you've gotta be aware of what you've, allowed them to remember about you. And there are I'm sure there are toggles in in all three of those platforms where you can prevent training, but Quickbase out of the box will not use your data to train third party models. Excellent. Let's see. Fast field question, Adam. Gonna call on you again. Would the AI summary recognize multiple fields in an in an, excuse me, in an inspection report? That's a really hard, sentence to read. Would the AI summary recognize multiple fields in an inspection report that are selected as poor or failed and add that to the summary? Yeah. Great question. This is specifically talking about our AI workflow features that we released for the pro plan as well. And in this, you can, write a statement or a query that AI will analyze. It's a criteria that it's gonna use to analyze submission data every time, every time it comes in for a particular form and then trigger an action off of whatever AI finds to be true or false. So if you ask it to find if your tires, when the inspection came through, if the tires, you know, failed or or the oil levels failed or something like that, you can have it analyze as many field data items. You can even write to have it analyze and kinda summarize based off of the values of different of different fields. It can go it can go all out. So, yeah, you can do way more than just one or two fields. You can have it analyze all kinds of things. If it's in the data for your submission, then you can have it analyze that and place that in your summary report. Awesome. Thanks, Adam. We have a couple questions here, and I'm not positive if anyone knows live on this call. But we have a few questions specifically around plans to Quickbase getting FedRAMP compliance. And, Allison, Yeah. I you're our our answer has remained the same there. We are, awaiting sponsorship from organizations and and don't have any current plans until that's, until that's met. So if you wanna sponsor us, let us know. Reach out to your account team. Love it. Thank you, Ryan. Let's see what else we've got here. Couple more AI questions. Is the AI searching through data counting as read usage? Yeah. That's a good question. We are, introducing other, guardrails and, almost like utility mechanisms in there to ensure much fair use of AI in inside of Quickbase. So while they won't necessarily impact reads, they there will be a limit for what a customer can do in a in a given month. If you want more info than that on this webinar, I I'll just ask you to reach out to your account team. They can walk you through the plans there. Amazing. And, Ryan, as a sort of follow-up to that along. the same vein of AI, do we have updated documentation around our Quickbase AI and kind of that sensitive information being used. A 100%. Yes. All of that information is in our help center. I will link the article in the, in the chat. But, yes, we are taking an overly transparent approach when it comes to this because we wanna make sure our customers feel, safe when using our AI features. Again, we've built this from the ground up with that, you know, well measured hesitancy in mind of some of our customers in using AI on their, you know, really sensitive, sometimes even proprietary operational data. So you have there's more information there. And, again, we'll we'll come out with more white papers, one pagers, slide decks around how AI works. Just stay tuned as we get closer to GA. Perfect. Alright. Another grid reports question. What happens when two users edit the same row at the same time? Do the saves only update the changes or the whole row? Good question. So when two users edit the same data at the same time, we have conflict resolution logic in place. So the user that saves first, they're just gonna they're not gonna know anything happened. The user that saves second, they will see a little dialogue that says, hey. Ryan was editing this record at the same time you were editing it. And they will get to choose which values they want to save for each value that conflicts with what they were editing. And when you're editing data in Quickbase and in grid reports, we're operating on the row level. So the record level and the same way that everything else operates in Quickbase. So when you save information, it saves at the row level so you can trigger things like pipelines and notifications in the same way that you have them set up for the rest of your application as well. Awesome. Let's see. A couple questions around, will we be able to create reports that are only visible to an admin or a specific role? You can do that already today. So you can set up the permissions, in your reports to say, hey. Actually, this report is only for me, or this report should only be viewable to administrators. You set that up. It's kind of in the top section of your report settings, but that is possible today. Excellent. Alright. Let's see what else we've got. I know we are running close on time here. Probably time for one or two more. We have a handful of questions about integrations. Do we are we able to work with Microsoft Teams at this point? That's one I. don't know the answer to. Yeah. We? have I think we have a pipelines channel for the entire Microsoft product suite. Amazing. Alright. Let's see. AI agent, is that available at all plan levels? It will be. It'll be part of a new package that we'll be unveiling over the next few weeks here. If you want an early sneak peek, reach out to your account teams, and they can get you on the list for for beta. Amazing. Alright. I know we are wrapping up here, so I think we will call it there. There are still quite a few questions that we did not get into, so apologies that if we were not able to answer your question. But, again, please please feel free to reach out to your account executive, your CSM, or our support team to get answers to those questions. But regardless, we will make sure that if you asked a question and it did not get answered live, we will have someone follow-up with you directly as well to talk through your questions. So thank you all so much for joining us. Thank you, Alice, Ryan, and Adam for the content and answering all of our questions today. One final pro plug for me to register for Empower and join us in Houston. We would love to see you there. I am so ready to be in Texas, be somewhere warm. So, hope to see you all in May for that. And once again, thanks to our speakers, and thank you all for joining. Have a great rest of your day. Hey, folks.