If You Build It, They Will Come: The Power of Custom Development Services for K-12

Today, we're gonna talk about custom development services and in structure. We are gonna show some examples of things we've done, talk about our process, give you some tools to help you understand what's possible in Canvas so you can go back to your own teams that might be doing custom development or just contextualize what we could do for you through our custom development services. So we'll start off, with just an intro about me. So I I have been in an instructor nine years now. I'm the director of the solution architecture team, which means my team is responsible for all of the requirements definition for any type custom project that we do. So anything that we see today in terms of examples or anything that we might build for you in the future or help you build my team's involved trying to help make sure that that's possible that that we have the right requirements.

We've done the right framework. The two, like, personal quirky things, which I'm not a real quirky guy. But I came up with two things. One, I play mean power chord on a guitar. So if you need somebody to play power cords.

I'm your guy. Anything more complex, probably not. And I am obsessed with late nineties wrestling. So I'm in the exhibit hall. Afterwards, if you wanna talk about, like, WCSW versus WWFF, come down there, and we can have hours and hours of conversation.

But of course that's not what we're here for, or I'd be able to talk for much longer about it. So I wanna show this video here to kinda set the stage for some of the things that that we've done and that we're going to talk about. I guess it's not going to load. Try this really quick. Okay.

If it doesn't load here pretty quick, which you are not seeing it load anyways. So we'll skip that. I can show you down in the hall. You're gonna see most of the things that, more examples anyways. But that wasn't canvas.

This is much more impressive if you can see that. And the the message behind a lot of the examples that we're gonna see today is we've got a really extensive API, which you're probably familiar with, l, LTI support, which is probably familiar with UI style guides. Everything you need to make, canvas, do things that you want to do. And make it look like it was meant to do that. So as we go through some of the examples that you'll see here in just a second, you're going to There we go.

As we go through the examples you're gonna see here in just a second, hopefully you get the the same look and feel of, oh, that that looks like it was canvas. A little bit about our team. So the custom development team's a part of instructure. So we're all in structure employees. We have solution architects.

And I already explained what we do, project managers, custom development software engineers, quality assurance engineers, and UI and UX designers. Every year, we do about three hundred engagements of different types of projects, whether that's building a new application, We're doing consulting. We currently host and operate a hundred and forty different applications for customers. So there's a hundred and forty things on servers running today. That that are customizations that help extend the functionality of Canvas, and we have a hundred and thirty data warehouses that we host, which we'll talk about, today as well here in a minute.

And we look at custom development services through kind of three different categories. There's custom applications, which is anything from a a student information system integration that maybe we don't support. So maybe you're using something like Workday for a student information system or something that's a little off of the mainstream. We can help build the application to integrate that. All the way up to fully functional, applications that look like they're part of Canvas, which will show some examples of.

We also have some data services and some consulting, and we'll talk about each of things, each of these things here. So this is a k twelve focused session. There are a couple of higher education things that we put in just so you can kind of see what those use cases are. Most of what we'll talk about today is k twelve oriented. So the first example is some work we did for ball state university.

Ball state, like most higher ed institutions needs to get grades at the end of the semester, which is not unique to higher ed. And last state of attendance information for faster reporting, which is kind of unique to higher ed. So we built an application that for them gives a student roster. And as you see here, it's in the context of a course. The instructor opens the grades application the same way they would click on modules or assignments or anything else.

They're able to finalize grades here. It pulls what's in the grade book. And if they wanna adjust up or down, they can do that, as well as provide a last state of attendance, confirm that publishing, and it goes into their student information system. It also gives administrators tools to be able to see when these things are published, and go back and and troubleshoot. New tech network is really cool.

This is one that I actually like quite a bit. They're an institution that does a lot of project based learning. So instead of a standard assignment that, which I I think we're all kind of getting away from and going more to competency and its standards based, assignments anyways, they wanted to have assignments that reflected a number of competencies in their courses. So we built this custom grade book that made it easier for them to do this. So there's a few different things happening here.

If you look at the examples, up in the top left, you have an example of seeing the categories or competencies that they use for grading in their courses. This is established at the institution level. So if you're really driving towards writing skills, critical reasoning, something like that. You can set that up. And then within the course, determine how those different competencies are weighted towards the the grade for the student to the right, you can see an application here where you can create the assignment and then say, which of these competencies it's teaching? And in Canvas, that creates an assignment and a rubric such that the teacher doesn't have to go in and associate outcomes and align those things.

We take care of all of that for them just by knowing what competencies we're teaching. They give us a little bit of assignment information. And then as the students submit it, we start to build grade data based on those competencies. So down at the bottom, you can see two views. One is a student centric view where I can see how is this specific student doing across all of these competencies.

And to the right is more of a traditional grade book type view where I could look and see maybe some of my students that are struggling in writing, plan some intervention activities, and try and beef that up. So new tech network developed this kind of framework of project based grading, but didn't have the resourcing to make that happen in Canvas or make it come to life. And that's where we were able to come in and help do these, integrations for them, find the integration points, and again, make it a little bit easier. So that teachers can teach, right, instead of create assignments and rubrics and all of those types of things that aren't quite as fun. Hall County Public Schools in Georgia is a really great partner.

We've done a lot of work for them. We're gonna show two examples today of of different problem areas that we've and with them. The first is professional development. How many of you are using Canvas to deliver professional development in your institutions? Okay. Great.

We also built staff directory. Some of their professional development, I I'm sure we'll overlap with things that you're familiar with. They have, a process where a lot of professional development is grassroots ground up. Right? So people at the school building are teaching a professional development course, which may or may not give PLC credit because we know that, you know, may maybe you don't get CEUs for everything, like the book club, or book study that you're doing, and others you do. So we build tooling in the top left.

You can kinda see for them to submit a request that indicated all the different competencies and teaching plans that they had, and that then goes through an approval queue So if you're, familiar with any other industry tools that do professional development, that's very standard. First, it goes to the principal for approval. If it's giving CEUs or the individual that's teaching the courses flagged it as a professional development activity that's credit bearing, it goes to the director of professional learning for the district to approve that. And then finally, once that's approved, it goes to their canvas admins to determine when that gets pushed to catalog. So you can see on the right here, We've got a Canvas catalog tile that was created all from information that the teacher put in when they requested the course.

So they may have an online course or it may be face to face. Give a description. And once that's approved, we kick it over into catalog so the users can actually register for it. And then we built transcripting tools There's a whole lot that's going on in this application. So we just picked some of the things that, touch on each of the areas.

But when a professional development course is done, the teachers of that course need to be able to say this person attended. Right? And maybe they attended half the session so they get half the credit. Maybe they get all of the credit. And they're able to submit that through this application in a way that then adds automatically to the professional development transcript. Something that I I thought was really cool and unique about this.

And and some of you maybe you're even doing this in your district. But if you attend an event like iste, sometimes there's there's credit bearing things you need that didn't happen in Canvas. And there's workflows in here for making those requests to get something added as well. So if I had an out of district or an out of state activity that should give credit, I can provide my documentation, get that approved, and have it on my transcript. So for Hall County, all of the professional development now happens within Canvas and cattle teachers never have to leave to another professional development system.

And it's been been really good in terms of driving adoption and helping them standardize the their process. On the other side, they wanted to have a staff or faculty directory that probably all of us have. And they wanted to be able to have a browse by school and to give teachers tools to build out parent pages or student pages, provide a biography. The normal things you might do in a staff directory So we built this in a way that it integrates with Canvas. So they have their different subaccounts, which probably all of you do as well, and each of those subaccounts automatically gets a tile on the directory.

So as there's a new school, we know surface that school and any courses that a teacher is teaching there, bring it over, We also have search and filter functionality. So maybe I have a high school student, and I don't know who their math teacher is. Right? But I know their ninth through twelfth grade. The functionalities there for me to filter and be able to find them. And then you can see up here at the top right, staff profile page has been made.

This is a public application. So if you go to teacher sites dot hallco dot org, you can actually play with it and see it out in the wild. That's one of the few things It's just out, not access protected that we've worked on. But again, it's been really helpful in connecting the parents and students with their, their teachers. University of Arizona Global Campus has a release.

They have a model that is very deployment heavy. Their instructional design team builds our courses. They deploy them. They need assignments copied over, and they need attendance information, but not for things like core surveys. And so they needed us to build the integration and also a way to say when this happens, don't bring those in attendance records is don't bring these assignments over.

So this is something that's a little more straightforward, not quite as flashy. But still a good example of how we're able to help take some of the admin load off by building customizations. This is one of the tools I I really like. It's the academic eligibility tool. How many of you have to do academic eligibility reporting for your athletes or debate team? Okay.

So this tool is built for that very purpose. What it does is it at once a week, which is the the frequency that they do eligibility checks in Oklahoma, checks a student's grades, and it runs it through the formula to determine whether or not those students are eligible or on probation or ineligible so that the sports coaches the, you know, FBLA team, all of those types of activities that have eligibility requirements can check-in and see who's eligible and who's not eligible. And then for the students, they can actually pull up a student, see that student's grades across all their courses. So if I'm the basketball coach and, you know, my student's not eligible in one of members. I can actually see what grades need to to come up so I can work with those teachers to get them on a plan or work with the athlete to to help them get there.

And then we also built in the ability for certain weeks to non impact eligibility. So, this is the tool that in the fall mostly for them, right, really important every week. They're running it. They live and die by it. But it eliminated a whole lot of paper process and people hours that were involved here.

And again, this all just launches from within Canvas. So for teachers, for counselors. Nobody knows it's not actually a part of Canvas. It just looks like it is. So there's just some application examples, and there's ton.

We could talk about tying outcomes to badge awards and canvas credentials. We could talk about, other grading activities. We could talk about individual people pages But there's so many. We don't have time. So we'll move on and talk about some data services.

So we do have, some robust data services options. The first is custom account reports. So how many of you are familiar with the screen on the left, or that looks familiar? How many of you have that many options when you open the screen on the lot? Probably not many because I've got, you know, twenty turned on and we're still in the a's, every report we've ever built. So we have the ability to go in and build a report that is you specific to your to your institution. So if you need a report that's pulling three or four different data elements that isn't in a report today, we can build those things in a way that you can use the account reporting features and the API to pull that, getting just the data you want.

We also have the ability to build custom dashboard something you're looking at on the right is something that we built to help look at standards achievement for, English language arts across all of the schools in the district. So I could, from a district level, look and see how are people doing with the LA? What grade levels are doing better? Which schools are doing better? Where do we maybe need to help some PD interventions or get more staffing or or TAs to help bring those standards, achievements up. We also have hosted data services. So Any of you, that might be using Canvas data are familiar with the process of pulling it from the API, getting it to a place where you can actually use that data. You can connect power BI to it or Tableau.

It's not just go in and start building. Our hosted data services allow you to do that very thing. Go in start building. So we'll automate the pipeline of moving that data over into a data warehouse for you. So I I showed you the slide earlier.

I have a hundred and thirty of these. And these options really enable you to just start reporting and not have to worry about hitting integrate with Canvas data. Layered on top of that. We also have consulting services. So when we're doing data consulting, often we're writing the queries for you.

You may not be super familiar or wanna become super familiar with how Canvas structures data. Right? You just wanna know how many assignments are missing in each course. We can go and pull that data for you. We also have consulting for people who are building their own integration. So for a lot of institutions or or districts that have their own staff, that staff may not be fully familiar with how Canvas works, or what does Canvas call a certain thing? Really competent developers, they just don't really know what's going on in our platform.

And we can connect them with members development team for hourly consulting calls to help answer those questions, help them with system design, and get them over the hump so that they can start building faster, and building more efficiently. We do a lot of this type of work. So those are the the three different service areas that that we work on. We wanted to give you a little bit of insight into what it's like to to work with us, and hopefully give you some information as well as you go back. If you're looking at customization projects or change management projects and kind of see what framework we apply and how we think about some of those things where new processes need to be developed or new software needs to be developed.

So we'll talk about each of these different steps, in more in more detail here in a second. But our our process starts with defining objectives and goals, which hopefully is the first step for everybody. Then we go to, building out user personas. We'll talk about those using user stories, and taking that into business requirements and actually executing on the project. For us, it's a very people centered approach.

We wanna start with the people and what do they need as opposed to what does the system need to do? Because a lot of times you start with what the system needs to do. You get to the end, and it might do those things, but not great for those people, or it might not actually solve the user's needs. When we define the objectives and goals, the things that we're looking for and thinking about are, why are we doing this? Right? Like, what is what is the reason to do any custom development project? How are we gonna know if we're successful? So if we come in and we make this data available, but nobody ever uses it. Was that a success? Or was that not a success? Did we want this used? Right? Was the definition of success something totally different? And we use the one thing test, which is if I could do one thing in this project, right? So I know you probably have like eight goals. If we did this and one thing happened that would make you happy, what is that? And then kind of use that as design paradigm thinking.

Right? Come back to that one thing because it helps us fill in gaps and also overcome ambiguity. We might not we might not know exactly how a third grade teacher on a Thursday morning is gonna do some task But if we know the one thing that you're aiming at, we can get a really good idea of what might be effective. Once we've got some objectives and goals to to put the framework around how we're gonna work. We start to look at user personas. If you're not familiar with user personas, they're pretty self explanatory, but you may not have used them before.

The idea is breaking users up into common patterns of what they need from the software or what they need from whatever process change you're looking at. So you ask your things, your self question, questions like what value does this person seek? Right? In the case of academic eligibility earlier, teachers and coaches and counselors are all looking at the same data, but they're looking at it for different reasons. Right? The coach wants to know, can this kid play or not? They're not necessarily concerned with this this kid. I'm gonna graduate. Hopefully they are, but, you know, like some of those coaches.

What is this person's job function? So is this person's job to deliver teaching and learning, or is this person's job to support or to help identify where an intervention needs to happen because there's a different level of data or different level of of functionality that might be there. And then how does this person behave? Is this a person that every day is looking at this? Are they looking at it once a week? Are they looking at it once a month? Are they never gonna look at it? If we don't send them an email, what are things that we need to do in order to fit and tailored the the problem statement and our solution to that, to the way that they behave so that we can have a common set of users to build user stories. User stories are basically a a description of what software is going to do based on the user persona and why those people wanna do it. So one of the most effective things in any software development process, and we use this with our products as well as we build them. Is building out a user story.

Who are the people that want to do these things? And not just what do they wanna do, but why do they wanna do it? A lot of times when we work with people that have different context, different backgrounds, different daily situations, they might think that the best way to solve a problem is by doing one thing or another when the reality is we can meet that need in a better way that's easier for them. But they just don't have the context of everything else going on to do that. So these user stories really help us as we go through design and technical requirements to understand why people are doing it. But also give us a baseline of all the things that need to happen. So for athletic eligibility, for example, people need to be able to see eligibility.

That's a pretty basic thing. Why? Well, now the y might change. Right? For a teacher, it might be so I can help my student bring their grades up. For a coach, it might be so I can make sure that they don't get on the bus to go for the away game. Then we move into business requirements, and this is where a lot of the technical thinking happens.

Right? We'll work with you, if we're working on projects together and figure out how are users gonna navigate this? Like, we're How do they even get to this? Did they know how to get to this? What are the functions that are there? What type of workflows do we have? How many workflows are there? Who has access to these workflows. And then probably most importantly, what limitations are there. There's a lot of times the the idea that we need to solve everything for everyone. Right? Well, if you're not using mastery paths, we maybe don't need to build out workflows that accommodate mastery paths in canvas. Right? We can start with something else and then grow into that later.

So what are the the limitations? What are the limitations on your end? Right? Are there there staffing restrictions or things that you're not going to be able to do or licensing restrictions for us to get, integrated with other systems. After we have all that information, this is where it gets super boring, and I don't have anything really flashy or fun to show, but we'd write a statement of work. And it's this very long document and there's a lot of sentences in it. But it is really important because this is what our developers read to figure out what they're building because our developers aren't gonna necessarily sit with us in every meeting, and they and they don't know. So we'll develop a statement of work to make sure that you understand what we're proposing that we build and for you to to help us understand if we've got it right.

Sometimes we'll realize we didn't get it there. Once in a while, we'll slip in something fun like a recording artist, you know, like in the green room, we need a green M and M. And it's like, I don't care if there's a green M and M's. I just wanna know if you read it. But If you wanna find those Easter eggs, you have to read it.

And then, finally, we have the execution phase. And this is where hopefully everything is very boring. Right? All we're doing is building stuff and showing you what we built. And you say that works exactly the way that I thought it would work. Thank you.

And we move on and everybody's happy and we've conquered, you know, all of our problems. We have world peace and all of those happy things. So that's an idea of our process. And and if you take this away, you know, the there's obviously, we want you to know about these custom development services. We wanna work on cool projects and show you some of the things we've done.

We also want you to understand and and have some tooling as you go away. As you're at new technology in your district, even if you're not looking at a custom build. If you can start with user stories and user personas, makes process a lot easier, all the way through. It makes it easier to onboard new people as well because you basically have a manifest of these are all the problems that we're solving for all of the people, and this is why we're solving it. So with all that said, we also wanna show you some of the integration points for Canvas.

And we we do integrations for more than just Canvas. We've done integrations with credentials We do some report card services with Master Connect. We've done some migration work with credentials. A few things with Studio. So it doesn't really matter which product in our portfolio you're working with.

We can probably help extend that, but Canvas is the thing that probably most of you are using also. We figured it made sense to focus on that. And this slide is is a table at it doesn't view so well in this slide, but it's okay because we're gonna show you examples. But when we're building LTI applications, which I I'm sure all of you are using from some vendor or another in Canvas. We have a number of places that we can put that to make it look and feel like it's a part of the experience.

And the first is global navigation. So comments is an example we use. How many of you have used comments before? Okay. About half ish. Cool.

So Commons is actually not a part of Canvas, in the technical sense. It's on different servers in a different place. Most users don't know that or don't need to know that because they just click the button in Canvas and all of a sudden they're there. So we have the ability with different app a lot of times we're doing custom dashboards or, in the case of professional development tooling, sometimes we'll have an icon there that says professional development. And they click on that.

They've got no idea. It's not just a part of the product. The course navigation is another example. This goes just right in the course menu. You probably are familiar with this from other applications that you might use.

Teachers click the button for eligibility the same way they'd click for modules or assignments, and now they're looking at something else that looks and feels like it's a part of the platform. And we have the ability to pull the data from it and and extend that. User navigation is another place that we have it from. So if you're building things with your teams, you could do this as well. If you click on your account, the all of those links down there at the bottom that I have that you probably may not be able to read, but, project based learning student progress dashboard.

Those are all external tools. And when those get opened, they take over the entire window. So it it again looks and feels just like it's part of the native experience. Rich content editor, probably, again, you're familiar with this. This is where a lot of tools get used especially for content generation.

But yeah, the ability to put in an application there that launches, lets you interact with it. I used NBC Learn as an example. But, the educator can go in, configure what they want, and students can get that same experience or be treated differently. Know they're a student, we can show different items there as well. There's these other set of LTI launch points that work just slightly differently.

It's not really worth explaining how different they are because, for the the purposes of this, we're just showing you where cool stuff happens. But, the account navigation is another place. It's just like the course navigation, so there's not a whole lot to say about it. But for admin tools, this works really well. This is an example of application that we built before course pacing was released in Canvas that managed, what we called PACE Plans.

It was kinda like the early version of And this was how people could control where it was turned on, where when blackout dates happened, so the students didn't have assignments due on Christmas day, for example. We also have the ability to embed as module items. So if you go in to add a module or add an item your module. You can say that you wanna use an external tool. Select what that tool might be.

This is an example of what Con Academy's interface looks like when you launch. And then for, you know, the educator and student, it will show something that's appropriate to their role. So if I'm the educator, I might see a screen that tells me what's there or if I'm using a tool that's gonna collect an assignment to grade it. See that if I'm a student, then I'm just gonna see the content. The assignment LTI is very similar.

When you go in, you say I wanna use an external tool assignment. We actually, built an application on this that was for coding programs. So students would upload their code as an assignment. We would automatically take that code and run it through a bunch of automated tests and then grade it and figure out, did it do all of the stuff the assignment said to do? And, you know, if it did eight out of ten, you got an eight out of ten in the grade book, so that the teachers didn't have to go download the code and run it every time. They could just write one file that said they need to pass these tests, and it would post that way.

And this is what that looks like. As an example, as a student, they just see that they're turning in an assignment, and they select, what they need to. So just to kind of summarize, we'll have time for some questions here. When we think about how we can help you, there's a number of ways. So we've got data consulting that we talked about.

Application integration analysis. We didn't talk really heavy about the analysis that we do. It's common for people to come to us and have us do the requirements analysis, and then take that to someone else to build, because we're the experts in our software. We know how it's gonna work. Maybe they have an internal design team.

Our development team, and they just want us to say how it should work. Build custom LTI applications, like we've shown application consultation, software evaluation. So sometimes we get engaged. People are saying, what's the best tool? We're doing one of these right now? What's the best tool for building data visualizations, within Canvas that we can embed and and helping go through that process of determining what do you need, what are the functions, and trying to align that with something and then really anything else. So we we can pretty much build anything we want.

We don't have a whole lot of constraints. And so If you have ideas, you have things that you I wish Canvas did this, or I would really like to get to this point or it would be great if those are all things to to bring to your customer success managers, or your, sales partners, and and help us explore. Right? Come to us. Talk about the project. Let's see what's possible.

And help you plan. And just know sometimes, like, we know it's sometimes there's not budget for it, but where we've had a lot of success, if we know now that we want it is helping plan for next budget year. So one of the largest projects we're working on now, it's like nine or ten months. It was something we talked about two years ago when there was no budget, but we helped to get a proposal that was put into fiscal year twenty twenty three so that it could go. And now they're doing something very similar to Hall County with professional development tooling integration.

But we're here to help. So we've got a few minutes for any questions you have. There are any questions any of you have about anything we talked today or anything that you came in hoping I would say or address that I didn't. I have a question. The custom solutions that you build for schools and districts, how does that influence the future of the campus products? Yeah.

I have to repeat your question for the recording. So, so the question was for the custom solutions we built, how does that influence the product roadmap and future for the product? The the reality is it it helps us in cases like PACE plans where we built something and it was out there and we could see that there were common patterns It helps us understand what those common patterns are so that at some point, we could add it to the base product. Course pacing is really the only feature we've done that for. Because most of the work that we do is very, very specific. So going back to the eligibility dashboard, that's a great example.

Their cutoff is just like sixty percent grades, but it runs once a week. If it's a short week, then you can better your status but not be worse. If it's a skip week, then it gets worse. And there are other certain Oklahoma specific conditions around, like, you're in a special ed course, how that influences it. And so when we go and we talk to, we which done before we talk to somebody in Louisiana about it, That's not how it works there.

And so it's very difficult for us to say, great. Well, let's let's shepherd this in and and build it. So it's always a possibility and it's always, open, but more of what it is is solving your needs. Right? Like helping make sure that you've got something that you need And generally, our cost of ownership is a lot lower. So I mentioned the customer that we worked with in twenty twenty two that got their their fiscal year budget twenty three in their annual subscription fees to the the solution they were using for professional development.

I think we're about ten times more what we're gonna charge them on an annual basis once it's done. Our recurring fees are a lot lower. Now, obviously, we're building software. So there's a big a big upfront. Right? But when you look at that over two years or three years versus a a SaaS application.

It's a really quick time to to pay off. And then also it works exactly how they want. Right? You've probably all had hopefully not with us. But you've probably all had things where I can't wait for this feature. I need feature, and it's not there.

It's not there. It's not there. And I'm constrained by the road map because the rest of the market doesn't need it. And this is kind of like a shortcut to to bypass that. Did that answer the question? Okay.

Yeah. You're welcome. Sure. Are all the custom developments? That you refer to, are those all customer communication as you build, or is there any Yeah. So the question was, is everything that comes to us something that we end up building or other options for first to build those things, as well.

It it's really both so that the we we have models where we're consulting one of our largest, projects this year. Is a consultation retainer where we meet with a customer weekly. And we've used this year about eight hundred hours, I think, of consulting with their development team across different projects. Some of that is building, because there are components they have us build into the whole they don't wanna build this piece, and so we're gonna build that piece and they're building the rest. So we can do either.

It's more common that people come and then we build it and host it and maintain, but it's also not uncommon for the other where we're consulting and helping design the requirements, informing the development, and then somebody else does the development. The only kind of exception to that is for core product features, because a core product feature has to align with the the spirit of the platform and where we're going. So for example, if you were to say, you know, we want to make it so that assignments can only have points grading and nothing else ever. No complete and complete. Something that just doesn't really fit with where we're going, that's not something either of us would build.

Right? It would be something that that couldn't make it into the the core product. But there's a process around even that, where if you have ideas, bring them to us. Let's talk about it. And if you have development resourcing, whether it's third parties you're already contracting with or, internal people that that work for your district. Like, we can help with the design aspects and then have them deliver.

One thing I didn't mention, the the one customer I mentioned that we've done about eight hundred hours They've got a really good development team, but they don't have a UX team. So they, user experience team. So they wanted us to do the design and say, what should this look like, to to make it look like it's a part of Canvas, and we built all of the mock ups and then their team went and implemented it. So all of those different functions that we talked about, with development, user experience designer, user interface design, solution architects, which is like the design and the requirements analysis. We can do pieces of that without doing the whole of it.

Yep. You're welcome. K. So There's no other questions. Don't forget to rate the session in the Instructure Con app.

And also, don't forget to scan this code. I'll leave it up for a minute. We're in the partner hall. So, if you're which hopefully will be there this afternoon. If you had any questions or something you wanted to address, obviously, be around the room for a little while.

But if you wanted to talk to the rest of our staffing team, staffing and services team, we're gonna be in the partner hall you can come down there and get a sticker. I also have those stickers here because that haul is a long walk away. So if you want a panda sticker that says professional services, come see me afterwards, and we'll we'll get you connected. Thanks, everyone.