[00:00] Hi and welcome to Broker Tools where we unpack the tools, systems, and strategies that help brokers optimize the way they work. I'm Katie, your host, and today we are catching up with James from Content Snare. Content Snare is the platform for brokers wanting to automate their factf finding process. In this episode, we're going to explore how Content Snare helps you reduce the turnaround time with client on boarding. If you've ever been looking for an app to support your client documentation collection, Content Snare might be for you. James, welcome to the pod. Or should I say, [laughter] >> Katie, it's awesome to be here. [clears throat] >> Yes, I thank you for joining me. And I know it's a bit odd to say oi, but that's how you start all LinkedIn posts. >> Yeah, I don't know. That's so silly. I can't believe that's taken hold. I just for I guess people that don't [clears throat] people won't know who I am but um it became like everyone seems to have something they're known for on LinkedIn. All the advice is to be known for something and I hate writing about
[01:04] the same topic over and over and over. And so I like being sort of differentiated and writing new and cool things. And so I was like in lie of having an actual thing I can be known for, I'm just going to say oi a lot. Start every post with oi and then just stuck to it. [laughter] And now, who knows, it might be a shirt that people wear. >> Yeah, that's right. People have literally said they want a shirt with just on it. And if I forget and start forgot forget to write at the start of a post, uh, within a few minutes, someone will have corrected me on it. So, I guess it's here to stay. >> Why not? Ultimately, these are the stories we want to tell with people because content snare is, I guess, the ultimate discussion we're going to have. But you started your entrepreneurial journey way before content. What happened? >> How did you get into it? >> So to to spare like the boredom of all the details, I think we've been in software for a long time. We built our first product in 2010 incorporated then and um through many years we've gone through I think this is our I mean if
[02:08] you count actual ones that got to market, I think it's our third product. Um but we've probably built five or six that sort of we just abandoned in that period had like a digital agency doing websites and marketing for people and uh software development, custom software development. That was you know quite a while ago now. Content snare was started in 2017 out of a problem that we had in our web design agency. Uh and I knew every designer I knew I actually interviewed a bunch of people about like what their biggest problems were and like getting information from people came up constantly. So we were like yeah that we can try and solve that and so we built the content scenario initially for web designers but that was 2016 2017 and then 2021 well we knew we had lots of people coming from lots of different industries you know mortgage legal accounting whatever and it was kind of just maybe 2021 we refined that and have spent most of our time since in the accounting bookkeeping mortgage and kind of legal industries are probably our top ones now. Yeah. I
[03:11] don't know. It was just a weird journey. We just found people finding content there on their own and going, "God, we love this." And we're like, "Wait, you're not a web designer." But it turns out they get a lot more value out of it from web design than web designers. So, that's kind of where we're in is this like I don't know, do you call professional services, broking, whatever. I don't know what I call this whole area. >> Yeah. It's really interesting because it it's finance. um and obviously people in finance but then you know document collection is document collection and I guess the gift of this niche is that it's got very very specific requirements >> and I guess this is the value of what content snare does because not only is it a document collection tool it's not just a form it has some special features and I guess one of the things that adds value is the level of data security and processing What would you say that uh content snare does well in this area? >> I guess I mean like it's honestly one of the biggest things we talk and think
[04:15] about internally. um it informs every single development feature and in fact almost to my uh it almost makes me mad because it slows down everything a lot you know like when we're like a surely it's just quickly to build this thing and the developers like yeah but to do it the secure way we got to do this that and I'm like damn it like security [laughter] but it's what we have to do right like it is it's just I don't know especially in this world that we live in now where with cyber attacks like I don't know how much if you follow investing, but like one of my best performing ETFs is a cyber security one. Like it's just it's absolutely ripped over the last few years because everyone knows how important it is and like everyone feels like I don't know under threat like yeah so it's very important to us. What do we do? I mean the we have the the badge ISA 27,0001 that says we're doing all the things. We've been third party audited to say we're doing all the right things which I mean that covers so many things. >> [clears throat] >> uh from like policies like doing a
[05:17] background check when you bring on a new employee like that's literally part of it. Um whereas like what is your security documentation like you know what do you what are your policies when you bring on a new employee when you offboard an employee how do you know like sensitive data isn't sitting on people's laptops like there's all these like person um policies and procedures and like training and like an agent that sits on your computer to make sure like you're not doing things not sorry that you have certain settings and stuff enabled on your device for security reasons through to the actual code right like you obviously want to have everything encrypted like the standard stuff's encrypted at rest encrypted in transit which means like I mean these are a muchness everyone should have that these days but that doesn't mean just those two things don't mean you're secure right because you could have encryption set up but have like a back door in your application that uh allows once people get in there the app decrypts everything anyway right so I a lot of people ask about those things but they're actually not they're only like a small piece so we get our application
[06:20] penetration tested by um you know actual security people. They're like ethical hackers. they try to hack into our stuff and and find like potential flaws or whatever and so we can patch them before um which I mean the last one it found a couple of things but they were like super minor like super super minor but um I think we do go a little bit further than most people like like one example I mean you don't have to do it's called per tenant encryption which means every single company that uses our product is encrypted in a different way so um you know if someone somehow they get into your data, they work out the encryption key for your data, which is like infantestimally small chance already that they don't have access to anyone else's data even if they had the entire database and they get your encryption key. They don't know the encryption key of everyone else. I mean serious security hole if someone gets your entire database but like it's just um it's just layers on top of layers, right? But we do lots of different things um to try and keep people's data secure um and you know all the requirements of ISO but beyond that as
[07:25] well >> which is really helpful because um before now nobody's really actually fully explained their >> [clears throat] >> um data security levels which I actually appreciate that you did because I guess if you are a broker and you are watching this there is terminology that they say your data is secure and if you use this platform >> it you know there is security in in place. But what does that mean? What does that look like? So, you know, a lot of people do what they call encryption at rest, which is when >> if I got this correct, I'm not a cyber like I do um cyber stuff and I have awareness enough, but I am not a security person. So um what I understand the terminology is at rest is that when it's sitting in storage that is encrypted but then in transit it's the I call it the pipeline. So it's almost like a a pickup car has picked up your data over here. [clears throat] >> It's in transit is that vehicle is now being encrypted and as it transits over
[08:28] to being at rest. >> Yeah. But but I mean this is much of a mushness now like HTTPS everything is on HTTPS and for most people that's what encrypted in transit means like so every everyone's encrypted at transit now like it's but it's funny because you got to write that down and say yes you do it. I mean there are other pieces but for majority that's it. And you raised something important there like everyone says they're secure. Of course they do. We've had brand new um companies come out that say from day one they're super secure and like back doors everywhere. Like I've seen this myself um well not myself but um look, let's just say there are there are companies out there that we know they're not doing penetration tests because someone would have found vulnerabilities immediately. Um and of course their website say we're very very secure. So yeah, it's it's a bit of a funny thing because how do you communicate this to like a buyer of our software? Like because they come to us and they go, "How secure is content snare?" Like what am I going to say? I'm not going to go into this tirade I just went on for you about all the different
[09:31] bits and pieces. I mean I guess I could but they don't want to hear that. They just want to hear you say, "Yeah, it's secure." >> Yeah. >> Um what do you want me to say? Like it's it's eight. >> Like just throw out a random number of how secure it is. like I cuz a lot of people who ask the question aren't necessarily ready for the answer or don't really understand anyway. So it's it's a really weird thing talking about security. I feel like I'm glad you liked the uh the detail I went through there. [laughter] >> And at the end of the day, I guess the way I've always seen Broken Tools is it's an education. And sure, um if you are even remotely watching this to the extent that we are, it is a lot of information, but I'm going into the details for the simple fact that people do say things are secure and they're not. And now that we've got AI in the mix. Um, >> yeah. >> And then there are people who are saying, "Oh, we have AI and it's it's not AI, it's an automation." Do you know what I mean? And at the end of the day, sure, we're talking about a way to collect documents and how to streamline that process for you. what services are
[10:33] available out there, you know, and obviously you in content snare are one of probably the best out there. Um because people need to be able to collect documents and um do it as securely as possible and this is why your niche existed because sure you started off in web but they didn't really need the refined points of document security. >> Yeah, it's it's interesting too. I think a benefit we got from starting in web is that we started out as collecting in like text and numbers and and like anything not just documents which I think actually was beneficial when we came into this industry because a lot of quote unquote document collection tools literally just collect documents and files. Um whereas in from what I the people I talk to almost never need just files. They need people to answer questions, type things in like and answer just normal questions, not file questions. So, yeah, I think we got a we got that. Um, that was lucky for us. >> Yeah. And and I think um it's I know that um
[11:38] accountants and I know mortgage brokers, this hasn't touched them yet, but you know, you know, the AML and CTF process is coming in for uh is it >> truncation? >> Yeah. [laughter] say trash. I don't know. I don't don't proper pronounce it, [laughter] >> but there there's um touch points in document collection points that matter >> with the you know the AMLCTF process >> and as a broker you you need to be aware across it. you might not have the same requirements of as as an accountant, but I >> in my humble opinion from an outsider looking in um I think document collection is probably one of the flag points that notifies you whether or not a person is legitimate or not. >> Yeah, I I look I haven't looked into it from the mortgage broker side, I'll be honest, but um I imagine like I've looked into I spent a lot of time on this, right? because we do have a lot of accountants on the platform and I mean a bulk of like a lot of it outside of like
[12:43] the reporting to um authorities and stuff and and like keeping an eye on your clients because the difference of an accountant is they're working with a client all the time. So they need to be watching like a generally I imagine a broker you know like you do the transaction and then it's another transaction later on sort of thing rather than this continuous relationship. So there's a point in time when you need to work out who that person is, what they say they are. And I mean that we built in this this ability to do the identity verification and AML screening. And to sort of simplify what that is essentially doing is the ID verification is making who sure they are who they say they are. So the classic is they get their phone out and they take a selfie. The more advanced version is like they have to like turn their head and count to like say four numbers that are on the screen so you know it's the real person and not some like reused photo or something that they've got of the other person and there's like license information or a passport or whatever. So that's step one is like get the identity that's who and and verify they are who they say they are and verify that the document is real. That's kind of all wrapped up in there. But
[13:45] then the second part, the AML screening is really just checking they're not on like databases. Are they on any watch list? Politically exposed persons, sanctions, child exploitation, um terror, like there's a ton ton of these lists around the world and it's really just making sure the person's not on any of those. So, um we actually felt this was pretty natural. We already had identity verification in content in there. So, it wasn't really much of a step extra step to add AML because it's it's literally just the same thing. Click a button, start the process, they do the identity verification, then all the screening happens on the background. So I I'm I again I haven't seen the actual requirements for brokers but I imagine it's that would be a bulk of it. um then flagging whether they're dodgy like you have to do a risk assessment most likely this is what accountants have to do and go based on what I've seen should I work with this person or not here's why I said you know the reason >> yeah uh to my knowledge um there the tranche 2 is really not applicable to brokers >> but um
[14:48] you do have AML CTF >> that that is AML right like it generally when people say you have to do like AML screen. That's all it means is like checking the databases. >> Yeah. Nice. And I guess um having a software and a service that holds that data and or can you know contain that information is is probably um a really great place to be because I've not seen it in any other document uh collection software. >> Oh, good. Yeah. I mean, again, another one that we're just lucky to be that we have accountants that need it, so maybe you guys get it for free. Yeah. I mean it's it's interesting like some people don't want necessarily us to hold it like we we we do hold it but a lot of to me it's like [snorts] we don't focus on being the central data store for people long term people do use us like that but like the way I like to operate is I've got Google Drive whatever you know maybe you've got um 365 or some other document management platform SharePoint whatever um we want you to be able to get that
[15:50] info in there which becomes your permanent storage, right? Like that's kind of the way we we have integrations with those tools for that reason. Um ju just since you flagged like having it all in one, like having all the data stored there. I mean, we we do do that and we can do that. It's just the way I like to work is getting it into the systems you're already using. >> Yeah. And I guess having that export feature is probably paramount for management. And I guess um I do know that um holding driver's license is um in your files is no longer required. like you need to be able to process it, but you cannot >> you you have to also uh delete that particular file at some point. >> Um and I guess that's what your service is saying is you can export what you want to um store what you need to on our services if you need to, but then at some point you're happy to delete. >> Yeah, that's right. So, we actually have two different reports available. One is like kind of the proof that you just did it and all the results that came back from [clears throat] it. uh like you know did the selfie check check check out um did the ML screening like what
[16:53] were the results but then the more advanced report actually has the information like the like screenshot of the license that they took and whatever so some people need that but it's like a we have a behind a checkbox like are you sure you really need this you're responsible this is sensitive data blah blah blah blah blah like sorry you have to actually opt in to get those reports but yeah some people need them >> and I I think this is the key thing about having a really good document collection tool Because sometimes when you're just trying to collect documents, you don't want to think about these tiny little [clears throat] >> um one security uh then you're you know best interest duties or AML CTF type requirements. >> Uh James, did you want to actually do a little demo of uh content snare? >> Sure. >> Have a little walk through so people actually see and know what >> it is. So this is content snare hell zoomed in um just to make it a bit easier to see on video. But yeah, so this is all the current like requests we have out. We call these a request. You can view it in this table view as well if you got lots
[17:56] of clients on the go. A request is basically just saying like I need this person Aaron Thomas. They've got like 47 questions outstanding. They've completed three and I've approved one of them. So at a glance we can see how far through all our clients are on what we've requested from them. So, the process of sending a new request is simple as clicking new request and then you're going to choose a uh a template. Now, these are literally just like built-in templates that we have. Uh we never we generally don't expect people to use them out of the box. These are there as a starting point to kind of show you what's possible with content snare. um you've probably got some kind of checklist you're already sending to clients in which case I would recommend going um this new request with AI and you can upload that questionnaire and we'll build your first request out of it. That's the um back on security and AI and stuff like the only way any of your data goes to AI in our platform is if you use that feature like that's a and then we send it we use open open AI to generate the question list and
[18:58] document list that you would send to somebody. Um, but if you don't use that, we don't use AI. So, yeah. So, we we might get like a little preview here. I'm just going to skip through this. Um, >> so just to confirm, a new request is actually another way of saying a, you know, like a form. >> Yeah, a form or a checklist, you know, just like here's the stuff we need from you. We we try to avoid form because these days it's becoming more about like a we need you to do all of these things because instead of just like answer a question it could be like can you go and do this thing like give them instructions or go and do something like you know add me to some system or um invite me to your bank I don't know like whatever whatever it happens to be it's not just getting info it could be like assigning a task in a way >> okay >> yeah so >> yeah So, um, I'll come back to this like request instructions later, but the meat of this is the builder. So, this is like the questions we're asking, right? So, this is the quote unquote form. We're asking for a name, date of birth,
[20:02] address, um, and there's lots of different bits of information you can ask from someone. So, this is the the very form looking thing, like we we want a document or a file. We want them to put some text in. Uh, we want them to put in like their current address or the dress that they're buying. select something from a list. We've got tables in there. So if you ever needed like a a list of expenses, for example, you could get them to like a multicolumn like what's what expense do you have? What's your monthly expenditure on this? Whatever. So you could put like it's like a mini spreadsheet within the request. Uh ID verification AML, which we spoke about before. Yeah. So we've got basic signatures now, but the like signature integrations are coming soon. So um so you can actually get them like to sign a PDF at the end of the request. This is just a list of questions really. Um, one thing now this template doesn't have a lot of uh, let me see. Yeah, we haven't really got any instructions in here. So, one thing I would say that's really important to get information right the first time from the client is to heavily rely on instructions. So, for example, when we say full name, I always
[21:05] ask myself like what are the ways a client could screw this up? Answer preemptively answer that. So, a good one is like make sure you include any middle names because like it's funny cuz everyone's like a not going to screw up their name. Actually, they kind of might. So, so any >> Yeah, cuz I probably would have just put my first name in my last name, not my little name. >> Yeah, exactly. So, like anytime you really like, and you'll notice this like when you actually do the document collection process, you know what people screw up and once you send them a contents, you'll see what people screw up and you can just come back in here and change your template. So, the next time you send this out, it's got that updated um instructions. Uh, actually, I might even just turn this to a table so you can see what it looks like. We could say expense name uh I'm just going on fee whatever I'm just going to leave the two columns there for now. Yeah. So upload questions oh and sorry conditional logic as well. So we've got this question here. Do you have any assets such as real estate whatever. If they say yes, we're going to show another question. So we're only showing them relevant questions. This is another really important thing if you want clients to actually use a system.
[22:09] like if you dumped them with this massive checklist that you would send everyone and I've been on the receiving end of this from not just brokers but like you know conveyancer um it was a big one. I just got this huge checklist and I was like oh my god like I was like I don't have time for this now. So I just put it away. Um but it turns out only like half of it was relevant to me. So if I knew I knew that I probably would have started earlier and gone off I do have time for this right now. But it was too big I was like at this. So only showing people the relevant questions is way underrated. Like it's really important to not hit that like overwhelm trigger that people are going to get anyway. So once I've laid out all the questions, um then I'm going to go to the next step >> which is a preview. I'll skip over that as well and just send this to myself. Um now you can put a pin code on it if you want, but otherwise that we um they can just access via clicking a link in their email which is more secure than people think. And we can talk about this later if you want, but the next layer is put a pin code on it. Um, and then what emails we're going to send to this person. So,
[23:10] we'll do all the automated reminders uh for people to get [clears throat] like so you don't have to chase clients for this stuff. I'm just going to turn those off and send this to myself now. So, if I just open this link in a new window. So, this is what your client would see. They'd get an SMS or a email or both. Um, that brings them in here. And you can see this is like super stripped back to make it just everything we do runs through a filter like can the most technically illiterate person I know work this out. Um and that's the only way these are going to work. Um so this is like a welcome page fully pretty much everything you see is fully customizable. Like we've got a video there but like we always recommend putting your own video in there like here's like you know awesome to be working with you whatever we we need this information and here's why. Um and then you record that once and then you never need to do it again. Otherwise, we have a video there on like how to use content snare. And then it's just one thing on screen at a time. Smith, whatever. Can't type and talk at the same time. So, they can go through and and answer questions. So, and they can sort of scroll through to different
[24:13] bits. Actually, where to put that uh table? Yeah. So, that's like, you know, they could they could enter a table. You could have pre-filled this as well with like set certain categories of of expense so they don't have to try and type them all in. Can you prepopulate the answers? So, say you've been on a discovery call [clears throat] and they've given you the answers. Can we feed the answers? >> Yeah, I actually skipped over that. So, that was the preview step. On the preview step, you can engage pre-filling and then enter the stuff you've already got and then you would ask so the client can just confirm that information. Yeah, sorry, I should have should have gone through that. Another really popular feature is this one here, this like ask a question. So, if they get stuck on something, they're in the middle. they don't know how to answer this properly. They can just pop this out and go like uh I don't know. I'm just going to put random text there for now. But this is like it just gets rid of that them having to call you or them having to email you separately and go hey question five. You've asked this and now you're like trying to cross reference what they like what that question means versus them. This is all just in context.
[25:15] There's no like mental load of working that out. It's just like here's the question. Oh, okay. Like I'll answer it, right? So you obviously see the comment on your end as well, but then they can see really quickly what's outstanding. So they've actually completed nothing at this point except those two questions, but imagine like as they go through this all gets ticked off. They can see really clearly um where they're up to. And then when they get a reminder to say, "Hey, you're not finished." Um they can click it and they can very clearly see um what you're still waiting on from them. So and then the final bit once once they've actually started answering some questions. This is back on your side of things now. Um, we can see they've got a comment in here. So, I could go and go and answer that one. You can also leave internal comments. Uh, so this is like only your team would see it if you want to like insult clients behind their back or something. Um, no, I'm kidding. Um, don't do that. Um, you can also >> don't do that because safe and secure things happen. >> Yeah, that's why it's dark out of this document. >> That's why it's dark blue and really obvious. Um, funny enough, we actually have the ability to not export the internal
[26:17] comments or not. You can turn that off when you export, which is which is up here. Um, >> yeah. So, >> sorry, I was having flashbacks to my days of when I worked in a [snorts] call center um in a insurance claims department and someone accidentally mistyped the word um this. So, instead of spelling this, they spell shi. Yeah. >> And then the person asked for the call pack and they thought the consultant was swearing. >> Oh my god. Yeah. >> You know what a crazy story is um with these AI meeting notetakers that are so prevalent now. someone like finishing a client call and then staying on with their team and bitching about the client for 10 minutes and then having the automatic summary be get sent to all the attendees including the client. [clears throat] >> Yeah. Anyway, so try not to win clients behind their back. >> You do have saying be be clean and clear and concise when you're using >> and uh you can see this is one of those
[27:20] um you can see that extra question showing up when I click yes there. Um, you can actually have internal questions too, like if you had an internal checklist that you wanted to run. So, this whole question would be blue. Um, and it's like, um, you know, have you done all of these things? So, you get to the end of the request and it's just like an internal note for your team to make sure you're actually doing all the things you're supposed to do. Um, but there, yeah, what I wanted to show you is this feature here. So, if they um have done something incorrectly, uh like the date of birth, you can say, "I'm pretty sure you weren't born in 2026, uh whatever." You can reject that question and get them to come back in and fix it. So, that's marked in yellow. They get another email to say, "Hey, uh you haven't finished everything." So, yeah, sorry, there it is. There's the email that just says, "Hey, we need you to come back and fix something." So, yeah, that and that'll bring them straight into that question to and it's very clear that you need them to redo it. So, that gets rid of more back and forth. Um, and then when you're done, you hit that export button, right? And that'll push that'll generate a PDF. Well, in this case, a CSV, but change that to PDF, PDF of all their answers. Um, as well as push all the documents to
[28:24] whatever system um that you're using. So, whether that's SharePoint or Google Drive or whatever, but you can also download them all locally in one like sort of zip folder. Yeah. So, that's kind of the process start to finish. Um, really quick version of it. You could save different types of templates for different types of clients. So, you know, you don't have to go through that builder step every time. You would just say, I want to send I've got a new mortgage client. I want to send this template to them. Go. Right? You don't have to go to that builder step and prefill unless you want to. So, >> I think the value is that if you would only do that if if you are trying to segment the things. So, for example, often I found in mortgage broking, you might do a preassessment. You might ask for five things when you're doing that preassessment rather than doing a full fact vine. >> Yeah, I mean it just depends. Like maybe you want to ask different questions if it's an investment or like if you already know it's an investment, you might have a different set of questions you send. You could obviously have the master template that they self- select their way through like is this an
[29:26] investment property or is it the principal place of residence then show them show or hide different questions. Some people like to go a bit more hightouch and they might have actually bespoke questions. So when you can create a request from an existing template and then modify it only for this customer, this client. >> Um yeah, so like the template is just kind of the starting point, but sometimes people will just send the raw template um to the to the client. So yeah, you've got that flexibility, you know, to that's the thing is like content snare works when you're getting any kind of information from a client. It doesn't have to be the same template every time. It could be a handful, five specific follow-up questions. Like, let's say they've answered a bunch of stuff. Um, I could go back and and I need I've got five new questions based on what they said. I can add a new page to this request um and say from an AI prompt and just paste the five questions I've got in here and it'll generate that um that final page to go into the request. That just stops you having to go like you could create a blank page and then go I want to add a question that is like blah blah blah blah blah
[30:30] and add another question. Or you can just use that AI thing and it'll generate the five questions and detect that it's this one's a file, this one's a text, this one's an address, whatever. >> Okay. So, um, and I guess this is how you are differentiating what how you use AI. AI is really part of the creation process of the form, but it is not used on client data. >> Correct. No, absolutely not. I guess the the caveat there would be don't put client data into that box. >> Yeah. >> Yeah. You're putting client data in there. >> Yeah. Into the prompt itself. That said, we are using open AI uh API which uh is bound by terms that says they're not using it for training data and not storing it and blah blah blah blah blah. This is a funny conversation that comes up a bit around data security and privacy with AI. It's like they explicitly say they're not going to use it, but do you trust them? But then that's the same with every software you've ever used. You know, like what are they doing with the data? They could say anything. So yeah, you've just got to [laughter]
[31:31] risk >> it's it's one of those things where sure we can only use the the software and the toolings that are available to us. >> Yeah. >> Um but you know Google, Microsoft, they hold a lot of information. >> Yeah. So I guess at the end of the day privacy is important and so when you're using AI inside of content snare it's really about form creation. It is not about doing a risk assessment or judgment call on any of the client data at this moment in time. >> Correct. Yeah. [laughter] >> It makes all the difference. If people wanted to reach out and learn more about content snare, where should they go and what should they do? >> Oh contents.com. It's probably the best place. Um free trial. You can actually I'd recommend signing up sending a questionnaire to yourself like use a personal email or something as pretend you're a client go through the process that you just saw there so you can see what it's like for yourself. Usually that's where the sort of click happens with people is they're like, "Ah, yeah, like I see how easy this is. After all,
[32:34] that is like our entire USB is that we're just easier to use than basically every other system." Which I didn't think would be that hard to sorry like it's just weird to me how that's not become the norm. But like we have people come to us and they're just like, "Oh man, like people wouldn't even use the previous system and they've like filled out everything in content center in two hours." So we hear that kind of thing pretty often. And I guess this is the gift of coming from web because you know what user interest matters and like how to keep people engaged and so from your perspective you unknowingly actually built it from a um a UX point of view which >> normally when people are doing forms that's not the the the view. You've given it enough color to also make it easier for people to see things. Um, [clears throat] but it it makes all the difference to how fast someone will fill in a form because they can see what they need to do and when they need to do it next. And if they need to ask a question, they're not having to jump out of the system. >> They can actually stay in full context
[33:38] and write a comment and then continue to the next question because they're not >> lost in a a tangent. >> And I guess that's the gift of what content scenario is. [laughter] >> Indeed. Thank you so much for joining me on the pod, James. It was so great to chat. >> Yeah, awesome, Katie. Thank you for having me. >> You're welcome. Um, please remember, anybody watching this to like, share, and do comments. If you have any more questions for James, feel free to put them down below. >> Catch you guys later.
