Secure Data Collection and Workflow Automation: FormAssembly

WEBVTT
00:00:05.040 --> 00:00:07.839
Hello, everyone, and welcome back to the SourceForge podcast.
00:00:07.919 --> 00:00:17.600
I'm your host, Bo Hamilton, senior editor and multimedia producer here at SourceForge, the world's most visited software comparison site where B2B software buyers compare and find business software solutions.
00:00:17.760 --> 00:00:22.160
Now, for this episode, I'd like you to think about how data actually gets into your business.
00:00:22.399 --> 00:00:29.039
Every CRM record, every patient file, every loan application, at some point, it all entered through a door.
00:00:29.199 --> 00:00:37.439
And for most organizations, that door is a form built in oftentimes 20 minutes, embedded on a web page, and then forgotten about.
00:00:37.840 --> 00:00:42.799
And that was fine when forms were contact us pages, but it's not really fine now.
00:00:42.960 --> 00:00:50.000
Forms have quietly become the front door for how regulated industries collect their most sensitive data, and the cost of getting it wrong just keeps going up.
00:00:50.159 --> 00:00:55.439
The average breach now runs US companies over$10 million, which is an all-time high.
00:00:55.759 --> 00:01:00.320
Yet the form itself is usually the least scrutinized link in the whole chain.
00:01:00.560 --> 00:01:05.760
Now, my guest today has spent years arguing that the front door deserves the same security as the vault.
00:01:06.000 --> 00:01:22.400
Josh Stray is director of product marketing at FormAssembly, a secure data collection platform trusted across healthcare, higher ed, finance, and government, one of the uh rare form platforms with FedRAMP high authorization and a longtime favorite among Salesforce teams.
00:01:22.560 --> 00:01:37.760
So, in this conversation, we're going to get into what companies actually use forms for today, where basic form builders break down, how deep Salesforce integration turns forms into a data quality safeguard, and then what it takes to protect sensitive data at the point of collection and not after the fact.
00:01:37.920 --> 00:01:39.040
So a lot to get into.
00:01:39.200 --> 00:01:41.359
Josh, welcome to the show.
00:01:41.519 --> 00:01:42.480
It's great to have you here.
00:01:42.719 --> 00:01:43.920
Oh, thank you so much for having me.
00:01:44.000 --> 00:01:45.040
I'm really excited to be here.
00:01:45.200 --> 00:01:53.280
Excited to talk to your audience, uh discerning members of the software procurement community, uh, looking forward to explaining what we do and uh, you know, why it's important today.
00:01:53.599 --> 00:01:54.560
Yeah, very well said.
00:01:54.640 --> 00:01:56.159
Let's let's uh get right into that.
00:01:56.319 --> 00:02:00.400
For folks who haven't heard of FormAssembly, give us that elevator pitch.
00:02:00.480 --> 00:02:02.239
What did it, what is it that you guys all do?
00:02:02.480 --> 00:02:08.479
Yeah, you know, if you look for us uh on the internet, you'll see uh data collection platform process automation.
00:02:08.639 --> 00:02:17.280
What that really means for organizations, for our customers today is we make it incredibly simple to securely connect with the audiences that an organization serves.
00:02:17.439 --> 00:02:19.360
And those audiences can be customers.
00:02:19.520 --> 00:02:27.680
They can also be volunteers or in the public sector, they can be citizens of uh, you know, the United States or any government entity across the globe.
00:02:27.919 --> 00:02:40.639
Connecting with those audiences in a way that builds trust, that also uh gives those audiences, you know, the sense that, hey, whoever I'm giving my data to knows me, understands me, and we can talk about uh how we accomplish that later.
00:02:40.800 --> 00:02:47.919
And then we make it super simple for these organizations to connect that data to the processes that their organization uses to conduct their business.
00:02:48.080 --> 00:02:55.520
Um, and as you mentioned, we uh are especially well connected to the Salesforce ecosystem, though we work with other CRMs and other platforms as well.
00:02:55.680 --> 00:02:57.280
Uh, we are that data layer.
00:02:57.360 --> 00:03:04.479
Um, and as you mentioned, you know, really where we stand out is we serve regulated teams, teams that are working under uh compliance and security scrutiny.
00:03:04.639 --> 00:03:18.080
We provide uh encryption, you know, in transit and at rest and just best in practice uh environments and uh all of the security controls that modern organizations need to make sure that they're not subject to a breach from the very moment that data enters their system.
00:03:18.479 --> 00:03:19.199
Yeah, absolutely.
00:03:19.360 --> 00:03:23.919
I mean, you you so you underlined it there, you you're really concerned with data collection.
00:03:24.080 --> 00:03:30.960
You're not just a standard sort of form builder, um, uh I which I think is really important to dis uh distinguish there.
00:03:31.120 --> 00:03:40.000
Um and you listed uh like the healthcare industry, government finance, those industries where a form screwing up just isn't just an inconvenience.
00:03:40.080 --> 00:03:48.240
I mean, it could really lead to uh a lot of unwanted outcomes, a lot of like lawsuits, um, which would not be would not be good.
00:03:48.400 --> 00:03:52.639
So um before we get into that scary stuff though, let's sort of zoom out a little bit.
00:03:52.719 --> 00:03:57.680
Because I think most people underestimate what forms are even uh, I don't know, what they even are anymore.
00:03:57.840 --> 00:04:00.800
Um, like when I hear web form, I picture sort of the contact page.
00:04:00.879 --> 00:04:04.639
Um, but what are what are companies actually doing with forms these days?
00:04:04.960 --> 00:04:09.680
Yeah, and you know, the the simple forms that are out there are still probably the most ubiquitous.
00:04:09.759 --> 00:04:14.400
Any website is going to have, you know, three to four fields for you to get in touch with someone, right?
00:04:14.560 --> 00:04:16.240
And those simple forms are important too.
00:04:16.319 --> 00:04:20.240
Those are kind of those very easy processes, an easy door to walk through.
00:04:20.399 --> 00:04:28.720
But where a lot of our customers are using FormAssembly and where they take the definition of form and kind of expand on it is these other data collection experiences.
00:04:28.879 --> 00:04:32.000
Think um, you know, student applications, right?
00:04:32.079 --> 00:04:37.759
Uh maybe uh especially for many of your listeners, a long time since they went through that collegiate application process.
00:04:37.920 --> 00:04:40.240
But it's more than just your name and your email address.
00:04:40.319 --> 00:04:41.759
They're collecting a lot of information.
00:04:41.839 --> 00:04:52.800
We're talking GPAs, we're talking about uploading high school transcripts, we're talking about oftentimes personally identifiable information, sometimes health information, allergies, uh, you know, medical conditions.
00:04:52.959 --> 00:05:05.360
Um, and uh that's common across industries, not just in higher education, but uh when you go to the financial services, obviously uh your contacts are handing over uh critical financial data, right?
00:05:05.519 --> 00:05:10.639
And the average consumer today recognizes that data means something to the world.
00:05:10.800 --> 00:05:13.920
They understand that data, their personal data has value.
00:05:14.079 --> 00:05:17.279
And I think that's been the big change over the last 10 years.
00:05:17.439 --> 00:05:26.560
Uh, you know, the news drives a lot of this, where you keep hearing about data breaches, and then in your email, you get a uh a notification that, hey, your data may have been lost in a breach.
00:05:26.720 --> 00:05:30.319
So we start to, you know, understand as consumers, people want my data.
00:05:30.399 --> 00:05:31.279
They want to take it.
00:05:31.439 --> 00:05:34.480
So I look at every form with a bit more scrutiny.
00:05:34.639 --> 00:05:36.319
Why am I giving you this information?
00:05:36.480 --> 00:05:41.199
And are you going to handle it in a way that uh, you know, doesn't put me at risk?
00:05:41.439 --> 00:05:48.319
And so that trust uh level is what we start to see as the trend over the last, especially couple of years.
00:05:48.480 --> 00:05:54.399
Um, you know, the average person filling out a form takes a second and thinks about where that data is going.
00:05:54.560 --> 00:06:02.959
And if they don't think that data is going somewhere that's going to handle their data safely, someone who's going to be a good steward of their data, data stewardship is one of our missions.
00:06:03.199 --> 00:06:04.959
You might not fill out that form, right?
00:06:05.040 --> 00:06:14.079
Uh, if you're engaging with an organization and say you understand the brand, you know the brand, but their website and their form on their website doesn't look branded, that's going to throw up a warning flag.
00:06:14.160 --> 00:06:15.199
Is this a phishing attempt?
00:06:15.279 --> 00:06:17.519
You know, is this something that uh is set up as a trap?
00:06:17.759 --> 00:06:21.759
Did I get here from an email and maybe that link was compromised?
00:06:22.000 --> 00:06:27.120
All of that lowers the uh the rate at which data might be submitted.
00:06:27.279 --> 00:06:29.360
I might not uh submit the application.
00:06:29.519 --> 00:06:33.680
I might not engage with that bank if I think that the form looks untrustworthy.
00:06:33.839 --> 00:06:45.360
That causes organizations to lose business, and that's exactly where Form Assembly sees our kind of mission is making sure that your organization gets the data that they need, but then you handle it compliantly as well.
00:06:45.519 --> 00:06:51.199
Um, and so, you know, that's more than just those three fields email address, first name that you're often submitting.
00:06:51.279 --> 00:06:59.759
We're talking about multi-page forms, we're talking about critical information, we're talking about information that drives businesses forward, really across every industry.
00:07:00.240 --> 00:07:09.839
Well, yeah, I mean, I I mentioned in the intro, and you you've um obviously mentioned it is that the form is basically the front door to a business.
00:07:09.920 --> 00:07:18.319
And so when you're dealing with all this private information, it's it's kind of uh uh alarming of like to think of how many organizations sort of treat that door like an afterthought.
00:07:18.399 --> 00:07:23.439
Like they don't, I don't know, uh prioritize the security and privacy aspects as much as they should.
00:07:23.600 --> 00:07:36.560
Um it's almost like a tool somebody uh in in marketing spun up uh a handful of years ago that nobody really owns and takes um, you know, uh puts the right priority on again safety and security and whatnot.
00:07:36.720 --> 00:07:41.920
So it's good to um that thanks for explaining a little bit more about what it is you guys do.
00:07:42.160 --> 00:07:47.360
Um maybe you can help compare FormAssembly to some of the other providers out there.
00:07:47.600 --> 00:07:52.959
At what point do the free sort of like drag and drop for building tools just stop cutting it?
00:07:53.040 --> 00:07:58.160
Like where do bigger teams or regulated teams start running into those walls?
00:07:58.639 --> 00:08:02.319
Yeah, I and I want to, you know, piggyback on something you said there.
00:08:02.399 --> 00:08:09.680
You know, I I don't want to put the blame on an organization for, you know, having forum experiences that they kind of set and forget.
00:08:09.839 --> 00:08:16.000
Um, really, there's too many data collection, we'll use a buzzword, surfaces out there, right?
00:08:16.240 --> 00:08:19.439
Um, every department probably has a different tool, as you mentioned.
00:08:19.600 --> 00:08:21.920
Marketing probably has a marketing form tool.
00:08:22.000 --> 00:08:26.079
Maybe it's Marketo, you know, something that actually feeds into their marketing automation platform.
00:08:26.240 --> 00:08:30.240
The sales team might rely on a different form to fill out their information.
00:08:30.399 --> 00:08:35.600
Um, your security team might have a trust base that has its own form in there for applications.
00:08:35.759 --> 00:08:40.159
There's just so many entrances for data into the modern organization.
00:08:40.320 --> 00:08:41.759
It's difficult to keep track of.
00:08:41.840 --> 00:08:53.200
And one of the things that's driving that is this proliferation of free tools or very, you know, low-cost kind of uh what do we call freemium tools that anyone at an organization can spin up.
00:08:53.360 --> 00:09:04.799
Um there's a broader conversation to be had there about shadow IT and uh you know the need for most organizations to take more control over what is being used at their organization, especially when it comes to data collection.
00:09:05.039 --> 00:09:11.279
But uh, where we stand apart from those free tools is most of those free tools are limited in some form or fashion.
00:09:11.440 --> 00:09:22.639
Uh, if we talk about uh free tools like Google Forms or Microsoft Forms that are actually included in a workspace like uh Google Workspace or uh Microsoft 365, they're not really free, obviously.
00:09:22.799 --> 00:09:24.799
Your organization pays for that workspace.
00:09:24.960 --> 00:09:29.600
Where those are limited is if you fill out a Google form, you know it's a Google form.
00:09:29.840 --> 00:09:45.120
They don't offer the branding to be able to really customize it, to make it look like your website, to make it match every aspect of your business and really build trust that this is, hey, this is you know an organization, this form is a natural extension of the website I came through, right?
00:09:45.279 --> 00:09:48.480
Uh, those limitations start to eke away at trust.
00:09:48.720 --> 00:09:51.840
Other free tools out there are free meum tools you'll see.
00:09:51.919 --> 00:09:56.080
Uh, and I'm sure everyone has run into one of these at one form or at one time or another.
00:09:56.320 --> 00:10:02.399
You'll see limits on what you can actually do with the tool, how many forms you can build, how many responses you can collect.
00:10:02.639 --> 00:10:13.679
And uh for the organizations we serve, their processes that they're using with uh with FormAssembly, they can't have those processes just suddenly cut off when they reach 100 or 1000 responses.
00:10:13.840 --> 00:10:21.759
Uh, you know, like our goal is to provide unlimited use of our platform because the organizations that we serve, that data needs to continue flowing.
00:10:21.919 --> 00:10:26.159
And it needs to not just continue flowing through unchecked, it needs to be validated.
00:10:26.240 --> 00:10:31.919
Uh, you know, we need to make sure that the email address that is on that form is an email address, right?
00:10:32.080 --> 00:10:33.919
You need to make sure that that data is clean.
00:10:34.000 --> 00:10:35.360
And we take it a step further.
00:10:35.440 --> 00:10:47.919
And with a bi-directional integration with the CRMs that we support, Salesforce and HubSpot, we also allow you to, if a uh piece of data is coming in through a FormAssembly form, you can check and see if that exists in your CRM already.
00:10:48.080 --> 00:10:55.600
And if it does, rather than create a duplicate record, one of the banes of any CRM admin's existence, um, we make it so you can check.
00:10:55.679 --> 00:10:59.360
And rather than creating a duplicate, update that existing record.
00:10:59.519 --> 00:11:08.240
So we start to bring a little bit of intelligence to the integration level that you just don't see when you look at these kind of more basic form providers out there.
00:11:08.399 --> 00:11:16.720
They're really about fast, quick, and then, you know, if I can be so bold, they they want to monetize the scale at which your organization operates.
00:11:16.879 --> 00:11:18.159
FormAssembly doesn't do that.
00:11:18.240 --> 00:11:20.799
We give you the tools to build processes that scale.
00:11:20.960 --> 00:11:23.200
We don't stand in the way of the data that you're going to collect.
00:11:23.279 --> 00:11:26.320
And I think that's a shift that we're going to see more and more.
00:11:26.559 --> 00:11:29.919
Um, you know, data collection has scaled over the last 10 years.
00:11:30.080 --> 00:11:33.600
COVID was a big driver of bringing, you know, processes online.
00:11:33.919 --> 00:11:36.480
So organizations are collecting more information than ever before.
00:11:36.639 --> 00:11:40.080
They're slowly moving away from any paper-based process, you know.
00:11:40.240 --> 00:11:47.600
Um, and I think, I think uh our competitors in the space are going to start noticing and uh moving to unlimited, but that's what we've always offered.
00:11:47.919 --> 00:11:56.799
Yeah, the freemium, the freemium options, you know, uh could be great for something like simplistic sort of needs, uh uh big bike sale signups or something.
00:11:56.879 --> 00:11:57.360
I don't know.
00:11:57.519 --> 00:12:08.480
Um, but yeah, the the scale issue, I think um, not only are you being kind of monetized uh uh in ways that you maybe don't prefer to be, um, but also, yeah, you run into the a certain wall at a certain point.
00:12:08.559 --> 00:12:14.639
It's like, I don't know, my mind's going to like Y2K or something, you hit this like certain number and then things just stop working.
00:12:14.879 --> 00:12:15.200
Yeah.
00:12:15.440 --> 00:12:19.120
And and again, you know, in the the organizations we serve, that's not an option.
00:12:19.279 --> 00:12:23.840
You know, you can't have during application season, again, you know, just use higher ed as an example.
00:12:24.000 --> 00:12:28.559
You can't have suddenly your forms break and suddenly student applications aren't flowing anymore, right?
00:12:28.720 --> 00:12:32.159
Uh during the census, you can't have information stop coming in.
00:12:32.240 --> 00:12:34.639
Like they these tools need to continue working.
00:12:34.799 --> 00:12:43.039
So uh keeping it reliable and then, you know, beyond those limitations, a lot of those form builders um are a bit shallow in their depth of integration.
00:12:43.200 --> 00:12:45.360
And that's not really an option anymore either.
00:12:45.440 --> 00:12:54.320
Uh, being able to speak to your CRM surface data in forms to make sure that you're not asking someone to give them information you have already given them.
00:12:54.480 --> 00:12:56.720
That's something that users expect.
00:12:56.799 --> 00:13:04.799
You know, they expect to engage with uh your business and in your business to act like they know you at every turn, including the digital experiences they have.
00:13:05.039 --> 00:13:08.720
So um both of those are where we see ourselves standing apart.
00:13:09.039 --> 00:13:15.600
I I definitely want to get into the integrations, especially with Salesforce, as um you've mentioned and as I alluded to in the intro.
00:13:15.759 --> 00:13:20.639
Um, before we get there, uh I do want to uh talk about the security side a bit more.
00:13:20.720 --> 00:13:27.279
Like why has data collection just gotten so much more like high stakes in the last few years, broadly speaking?
00:13:27.679 --> 00:13:29.440
Well, and and you mentioned this already.
00:13:29.519 --> 00:13:34.320
Uh the stakes have gotten higher because bad actors out there are trying more and more.
00:13:34.480 --> 00:13:39.759
And obviously, uh, you know, with the advent of AI, I think a lot of bad actors are now superpowered.
00:13:40.000 --> 00:13:48.799
The ability to spin up very convincing uh websites, convincing forum experiences that look like a business and trap data has increased exponentially.
00:13:48.879 --> 00:13:53.200
And I think we're going to continue seeing that uh the FBI puts out a report every year.
00:13:53.279 --> 00:14:02.320
It's usually trailing a couple of years uh on the amount of you know revenue loss, data loss, et cetera, that happens from bad actors, uh, you know, phishing attempts, et cetera.
00:14:02.480 --> 00:14:06.639
But uh the the proliferation of AI tools, I think, is going to drive those numbers up.
00:14:06.799 --> 00:14:11.360
Uh luckily, as I said earlier, I think consumers are more aware of this than ever before.
00:14:11.440 --> 00:14:25.759
Um, but the stakes are so high that uh data might be lost or stolen that organizations absolutely need to look at every tool that is in their tech stack and make sure that it is uh secure and not leaking information.
00:14:25.919 --> 00:14:29.200
But they also need to look at the connections between those systems.
00:14:29.519 --> 00:14:44.320
A lot of uh tools have relied on third-party infrastructure, you know, connection as a service, uh, not to badmouth our friends at Zapier, or obviously they they uh they uh serve a very important purpose of carrying data from system to system.
00:14:44.639 --> 00:14:55.519
But when you are in a regulated industry like healthcare, every tool that touches patient data needs to be, needs to have a BAA signed with your organization in order to be HIPAA compliant.
00:14:55.679 --> 00:14:59.120
And so the fewer connections that you have, the more direct connections you have.
00:14:59.200 --> 00:15:06.879
And candidly, the fewer systems that you have touching data, the less chance that you have at exposing yourself to compliance risk.
00:15:07.039 --> 00:15:14.399
And then every handoff that you minimize, also there's less of a risk of someone injecting something in the middle of that and intercepting that data.
00:15:14.480 --> 00:15:16.879
Uh, and so there's there's where the stakes are coming from.
00:15:16.960 --> 00:15:22.480
And it's why uh FormAssembly spends so much time and focuses so much on our integrations.
00:15:22.879 --> 00:15:26.639
We have direct integrations with every platform that we support.
00:15:26.799 --> 00:15:30.960
We do not use third-party middleware in order to hand that data off to a system.
00:15:31.039 --> 00:15:32.159
We integrate directly.
00:15:32.399 --> 00:15:57.919
Does mean we have fewer integrations, but all of those integrations are able to be used compliantly to hand off that sensitive data, including, as you, as you mentioned at the very beginning, uh we just achieved with in partnership with FedHive, FedRamp High compliance and DOD IL4 compliance, which means we can handle what's called controlled unclassified information, which is almost every piece of data that is associated with federal uh funds and federal projects.
00:15:58.080 --> 00:16:02.879
Um, and so you know, there's a high level of rigor when you're handling that kind of sensitive information.
00:16:03.039 --> 00:16:23.759
And so we focused very heavily on making sure that our platform, you know, obviously supports the controls that are required for those uh security and compliance frameworks, but also we we try to educate our customers on why this is important, the best practices in spinning up information, minimizing the information you collect, and obviously routing that to secure and compliance systems as well.
00:16:23.919 --> 00:16:25.279
So, you know, the stakes are high.
00:16:25.440 --> 00:16:32.080
I also want to mention that because people are collecting more data, they're also kind of collecting more types of data than they were before.
00:16:32.240 --> 00:16:41.840
So, you know, it used to be that you'd probably only think of a hospital or a doctor's office as collecting PHI or uh protected health information.
00:16:42.080 --> 00:16:50.559
Now, uh, as I mentioned earlier, if you are having students uh tell you about uh their allergies or you know their food needs, you're collecting PHI.
00:16:50.720 --> 00:16:56.320
Those uh classes of information have expanded legally in several states over the last couple of years.
00:16:56.480 --> 00:17:03.200
And so organizations are just collecting sensitive information, and sometimes they don't know it, which is really scary because that puts them at risk more.
00:17:03.759 --> 00:17:05.200
Yeah, let's let's expand upon that.
00:17:05.279 --> 00:17:11.680
So, say I'm collecting genuinely sensitive information, health data, financial details, student records, that sort of thing.
00:17:11.759 --> 00:17:16.559
Like beyond just getting the forms live, like what should I actually really be thinking about?
00:17:17.039 --> 00:17:18.960
Yeah, so uh that's a great question.
00:17:19.119 --> 00:17:20.240
Here's the framework that I use.
00:17:20.319 --> 00:17:21.359
And you'll have to forgive me.
00:17:21.440 --> 00:17:22.960
Obviously, marketing's in my title.
00:17:23.039 --> 00:17:26.640
So I write emails with exclamation marks and I talk a little bit too much.
00:17:26.720 --> 00:17:31.119
But but my framework is, you know, you have this front-end experience, uh, which is the form, right?
00:17:31.200 --> 00:17:36.799
This surface that uh your form responded as a term we use, but your audience, you know, interacts with.
00:17:36.960 --> 00:17:41.680
Uh that form surface uh needs to look secure on the outside again to build trust.
00:17:41.759 --> 00:17:42.720
It should be branded.
00:17:42.799 --> 00:17:46.559
Uh, it should also have fields that are collecting sensitive information be masked.
00:17:46.720 --> 00:17:56.319
You're gonna be familiar with this, even if you're not familiar with that term, when you're inputting a password into any password field and dots show up rather than the numbers or characters that you're inputting.
00:17:56.480 --> 00:17:57.839
Those are masked fields.
00:17:58.000 --> 00:18:00.000
So there's that surface level.
00:18:00.240 --> 00:18:10.799
I do encourage all of our users and anyone that's collecting data to also think about where that data goes, whether that's the data collection platform itself or the system that you're sending that information to.
00:18:10.960 --> 00:18:20.480
And by that I mean when you have a form builder out there, um, it's going to, when someone uh clicks submit, it's usually going to store that response at the form level.
00:18:20.640 --> 00:18:32.960
Uh, that's a risk uh if that information is not encrypted, encrypted, and masked, uh, because anyone in your department that has access to that tools, anyone in your organization, so if this is a marketing platform, you might have a marketer.
00:18:33.039 --> 00:18:42.960
And if that form is collecting protected health information or sensitive information, and it's stored in that form builder, that data could be exposed to that marketing resource.
00:18:43.119 --> 00:18:45.279
Um, ideally, that's not the case.
00:18:45.440 --> 00:18:50.400
Only people who have a reason to uh view that data should have access to that information.
00:18:50.559 --> 00:18:59.200
So the form assembly platform supports masking that information inside of FormAssembly and auditing anyone who does access that information.
00:18:59.359 --> 00:19:02.880
So you may need someone on your team to go in and check a response.
00:19:03.039 --> 00:19:07.759
Perhaps, perhaps a patient record uh you know was submitted on a form and there was an error.
00:19:07.920 --> 00:19:09.440
Perhaps Salesforce timed out.
00:19:09.519 --> 00:19:13.279
You reach your rate, uh API rate limits and that information didn't go anywhere.
00:19:13.440 --> 00:19:15.440
You still do need to be able to access that data.
00:19:15.519 --> 00:19:18.640
You don't want that data just lost and have to ask them to submit it again.
00:19:18.799 --> 00:19:20.319
So someone does need to access it.
00:19:20.480 --> 00:19:25.359
But in order to be truly compliant, you need to know who accessed it, when they accessed it.
00:19:25.440 --> 00:19:30.400
And if it, you know, uh you have an audit that comes through, you need to know why they access it.
00:19:30.559 --> 00:19:44.480
So with FormAssembly, you can have an audit log that if somebody uh accesses a sensitive record for that sensitive information, it tells you when they logged in, when they accessed that data, date and time, and the user ID that was used for that.
00:19:44.640 --> 00:19:48.000
And then you would have to ask that person, hey, what reason did you log in?
00:19:48.079 --> 00:19:50.160
But that supports that audit trail.
00:19:50.240 --> 00:19:53.200
Um, so these organizations can prove compliance.
00:19:53.359 --> 00:20:12.480
Um, and from there, you know, like uh you should also be very aware of where this data ends up, uh, whether you're sending it to an EHR, which uh an electronic health record system, or a CRM, you need to make sure that that data, especially if you're sending sensitive information, is again not being exposed to people who shouldn't have access to that information.
00:20:12.720 --> 00:20:19.119
So uh that requires organizations to build their CRM differently, custom objects for storing sensitive information.
00:20:19.200 --> 00:20:20.559
There's a ton of best practices out there.
00:20:20.640 --> 00:20:22.960
It's a little beyond my purview, to be honest with you.
00:20:23.119 --> 00:20:32.400
But if you are building and collecting flows that require or collect sensitive information, it can't just be at the forum level that you're thinking about, you know, making it secure and compliant.
00:20:32.559 --> 00:20:39.440
You need to think about every step, every handoff, anywhere that that data may live and uh who might have access to it.
00:20:39.759 --> 00:20:45.039
Well, I hope organizations are taking notes, especially those in the highly sensitive uh industries.
00:20:45.200 --> 00:20:53.279
Um that and that's a really good sort of bridge to the compliance question I have for you because your compliance list is is just kind of uh absurd.
00:20:53.359 --> 00:21:03.279
You know, you got the HIPAA, uh GDPR, FERPA, I hopefully I'm saying all these right, PCI, SOC2, FedRAMP, high authorization um certifications.
00:21:03.440 --> 00:21:11.519
For listeners who, you know, uh don't live in this world, like maybe you can just reiterate like why does compliance matter at the form level?
00:21:11.680 --> 00:21:16.000
Because isn't that usually, I don't know, handled somewhere else, maybe in the tech stack?
00:21:16.480 --> 00:21:20.640
Well, unfortunately, too many organizations have thought that for too long.
00:21:20.799 --> 00:21:26.160
You know, again, you might think of where the data ends up as the place that you need to make secure.
00:21:26.400 --> 00:21:30.880
But really, what what we're finding, and more compliance standards are requiring this.
00:21:30.960 --> 00:21:33.039
Uh GDPR is a great example.
00:21:33.200 --> 00:21:43.440
Uh GDPR notes that uh when you collect information, you need to have motivated opt-in for those contacts, usually in the form of double opt-in.
00:21:43.599 --> 00:21:54.079
You know, uh you cannot check the boxes on the form when they give you any information, whether that be simple contact information or some of the more sensitive information that we are uh we've been talking about.
00:21:54.319 --> 00:21:59.759
Um so you know, I think I think with the proliferation of things like GDPR, like CCP.
00:22:00.160 --> 00:22:13.039
PA, which is California's kind of GDPR version, I think the eyes are opening at more organizations that really from the point that data enters your system, you need to be thinking about security compliance.
00:22:13.440 --> 00:22:27.519
I'll be honest with you, I think the limitations of form tools and just kind of this idea that they were inherently limited for so long is one of the reasons that people don't think about trying to enforce security and compliance at that layer.
00:22:27.839 --> 00:22:29.920
But now, as I mentioned, you know, the stakes are high.
00:22:30.079 --> 00:22:38.480
As soon as you take someone's information, that information becomes, I don't want to say a liability because obviously your organization needs it, but it becomes your responsibility to protect it.
00:22:38.640 --> 00:22:43.039
So you do need to be thinking about that collection moment, that that collection surface.
00:22:43.200 --> 00:22:49.119
And you need to be bringing your compliance footing all the way out to the very surface of your tech stack, we'll say.
00:22:49.599 --> 00:22:53.680
And there's just so much to keep in uh keep track of, you know, by oneself.
00:22:53.839 --> 00:23:03.839
Like uh there's like kind of a there's a new sort of uh regulation at least being discussed or maybe implemented every sort of like congressional legislative hearing, so like, uh or session.
00:23:04.000 --> 00:23:18.559
So, you know, trying to keep track of all this, um, the cali the state-by-state approaches and then the the national and then um international sort of uh regulations, you it's it's uh very uh appealing to be able to partner with somebody who handles all this, right?
00:23:19.039 --> 00:23:25.839
Yeah, you know, your larger organizations are going to have uh, you know, like a legal team that's going to keep up to date with this.
00:23:26.000 --> 00:23:28.400
Um, you know, again, because the stakes are so high, right?
00:23:28.480 --> 00:23:30.880
There's a financial incentive to protecting this data.
00:23:31.039 --> 00:23:44.319
But smaller teams, uh, you know, and we support a lot of nonprofit organizations that are small teams doing incredible work uh at scale, but they don't have time, to your point, to keep up with every change to legislation that uh they might fall under.
00:23:44.480 --> 00:23:47.759
It's something that we uh are trying to kind of bridge a gap with.
00:23:47.920 --> 00:23:49.200
Yes, we want to provide the tools.
00:23:49.359 --> 00:23:51.119
We also want to provide the guidance.
00:23:51.279 --> 00:23:56.079
Um, something that we're offering in a sneak peek at a roadmap and just where we see the industry going.
00:23:56.160 --> 00:24:14.319
Um, FormAssembly is going to offer what we call a policy library where you can build into your platform the ability to uh, you know, all of the requirements, whether you fall under GDPR, whether you fall under HIPAA, or whether you fall under something more rigorous and much more niche like uh FedRamp High, you can encode your policies into the platform.
00:24:14.400 --> 00:24:25.359
And then RAI assistant, we have an assistant on the platform that helps you use the platform, can analyze your forms and tell you which ones are falling under the compliance standards that you support or that are out of compliance.
00:24:25.519 --> 00:24:32.079
Because to your point, it's difficult even for teams to look at every form in their ecosystem, right?
00:24:32.160 --> 00:24:36.960
Every platform in their ecosystem and make sure that it is meeting their compliance requirements.
00:24:37.119 --> 00:24:47.279
So we're doing uh, we're we're kind of bringing that uh, you know, we're doing that journey for them, helping put guardrails in place and helping give them that visibility of, hey, when am I in compliance?
00:24:47.359 --> 00:24:48.319
When am I out of compliance?
00:24:48.400 --> 00:24:50.000
Where do I have work to do?
00:24:50.319 --> 00:24:51.599
Yeah, that education layer.
00:24:51.680 --> 00:24:54.559
Is that something that you said it's it's uh rolling out?
00:24:54.880 --> 00:25:00.799
Yeah, it'll be available in the next uh several months, um, end of 2026, early 2027.
00:25:00.880 --> 00:25:11.519
Uh it's we're calling it a policy library, but yes, um the whole goal is to allow you to customize your platform to basically have your users operate within guardrails that keep you compliant.
00:25:11.599 --> 00:25:13.680
So you have less to be concerned about.
00:25:14.000 --> 00:25:14.720
Very exciting.
00:25:14.799 --> 00:25:15.920
Okay, something to look forward to.
00:25:16.000 --> 00:25:18.319
That that could be very, very useful, I can imagine.
00:25:18.480 --> 00:25:25.680
Um, I okay, I want to get to the integration um story because um I know a huge chunk of your customers are our Salesforce shops.
00:25:25.759 --> 00:25:27.519
Um, so talk to me about that connection.
00:25:27.599 --> 00:25:31.759
Why is FormAssembly uh plus Salesforce just such a big deal?
00:25:32.240 --> 00:25:34.799
Yeah, so um there's a couple layers to this.
00:25:34.880 --> 00:25:46.000
The way that we've been uh working with Salesforce for the last couple of decades um has been uh we've offered an integration that offers more depth than what is normally out there.
00:25:46.160 --> 00:25:49.839
Um typically, when you see integrations with Salesforce, they would be shallow.
00:25:49.920 --> 00:26:02.720
They'd only work with standard objects, or they'd come with other restrictions, only being able to use certain fields inside of the CRM, uh, perhaps requiring double entry or running up to against rate limits.
00:26:02.960 --> 00:26:09.279
Form assemblies integration allows an amount of flexibility that uh our customers really appreciate.
00:26:09.519 --> 00:26:22.400
You can bring Salesforce information into your forms, an act that we call pre-filling, so that when you have somebody that you already have information on interact with your forms, they don't need to give you information twice.
00:26:22.559 --> 00:26:32.319
There is a uh, you know, obviously a user experience aspect of that where it's just better if I don't have to fill out 12 form fields, if I only need to give you one piece of information.
00:26:32.480 --> 00:26:34.720
There's also a data quality issue there.
00:26:34.960 --> 00:26:44.640
Anyone who has been an admin or spent any time with customer data knows that when you ask somebody for information, there's a high likelihood they're going to make a mistake typing that in.
00:26:44.799 --> 00:26:50.079
Uh, they're going to give you an old address because their uh browser submits an old address, right?
00:26:50.240 --> 00:26:53.759
Um, so being able to pre-fill that information has been incredibly valuable.
00:26:53.920 --> 00:27:01.920
And then what we allow you to do with that information once you have it in the form and send it over, we allow you to bring a little bit of logic to this integration layer.
00:27:02.079 --> 00:27:10.400
So obviously, if you're a Salesforce user, you're familiar with Salesforce flows, there is tons of automation you can build on your CRM platform.
00:27:10.559 --> 00:27:15.680
The problem is you have to have that information in the CRM before you can actually start automating it.
00:27:15.839 --> 00:27:22.640
And so if you get bad information into the CRM and then kick off processes from it, tell a salesperson to reach out to this person, right?
00:27:22.799 --> 00:27:31.039
Or uh, you know, tell an advisor again in higher ed to reach out to the student, but the information is bad, you're wasting time with your employees, right?
00:27:31.119 --> 00:27:35.440
Uh and that's that's breaking down and that's causing kind of what we call manual rework.
00:27:35.519 --> 00:27:44.240
So, you know, correcting that data, going through, checking for typos, all things that waste your organization's time and make those data collection uh processes less scalable.
00:27:44.400 --> 00:27:56.240
So FormAssembly allows you to take a little bit of a logic step there before you pass that information into the CRM, you can have FormAssembly's forms look into the CRM and say, hey, does this record exist already?
00:27:56.400 --> 00:27:58.720
Does any component of this record exist?
00:27:59.039 --> 00:28:04.160
If it does, rather than creating a new record, we're going to go in and we're going to update that.
00:28:04.319 --> 00:28:07.599
And if there's no information in there, we'll obviously create a new record.
00:28:07.680 --> 00:28:17.680
And maybe if something looks a little wonky, maybe if it's like, well, there's a slight match here, but it doesn't match both the name and the email address, you can then put that name perhaps on a list.
00:28:17.839 --> 00:28:19.839
You can make a little update on a Google Sheet.
00:28:20.000 --> 00:28:24.079
You can send that information somewhere else before it pollutes your CRM.
00:28:24.240 --> 00:28:31.279
You know, a lot of questions that I get asked around a Salesforce integration is why wouldn't you just use Salesforce's data collection tools?
00:28:31.440 --> 00:28:37.039
And the reason being is you are already inside of the CRM when you have that data.
00:28:37.200 --> 00:28:43.039
And again, that that's allowing oftentimes bad data into the CRM before you can start working on it.
00:28:43.279 --> 00:28:50.319
If you can have this layer outside of the CRM that does everything that you need it to do, it's like it's like you have a native tool.
00:28:50.480 --> 00:28:56.559
You're losing no capabilities inside of the CRM for decision making, but you can do it before it enters your system.
00:28:56.720 --> 00:29:06.640
That's the kind of flexibility that customers are coming to FormAssembly for so that they can keep that CRM data much more clean, much more usable, and trust it a bit more too.
00:29:06.960 --> 00:29:07.599
Very well said.
00:29:07.680 --> 00:29:09.279
Yeah, a lot of tons of benefits there.
00:29:09.359 --> 00:29:13.519
The the no middle middleware part really um stands out there.
00:29:13.599 --> 00:29:21.599
And then, yeah, just I'm just thinking of all the manual entry and the sort of copy and paste uh people are stuck doing, which the integrations really help sort of alleviate.
00:29:21.680 --> 00:29:25.119
And there's just a lot of practicality with integrations.
00:29:25.359 --> 00:29:28.960
That's that's kind of the main sort of the most broad way to put it.
00:29:29.519 --> 00:29:39.200
In the Salesforce ecosystem, this is really coming to a head because obviously uh, you know, Salesforce is a trailblazer when it comes to uh usage of AI, promotion of AI, agent force is everywhere.
00:29:39.359 --> 00:29:42.079
They just this week announced a new integration with Claude.
00:29:42.160 --> 00:29:48.880
They're calling Claude Force to allow for uh interacting with the CRM on any surface, essentially.
00:29:49.039 --> 00:30:04.880
Um, at the same time, most of their customers and most of our customers are living in a present that unfortunately is still dealing with a lot of manual processes, a lot of just data quality issues that are making it really hard to reach this kind of like AI agentic organization future.
00:30:05.119 --> 00:30:07.920
We're offering tools to help address that today.
00:30:08.079 --> 00:30:18.240
Um, so hopefully, you know, like our customers and clients are able to eventually access this promised future of, you know, an agentic operation where everything's automated.
00:30:18.880 --> 00:30:19.200
Yeah.
00:30:19.440 --> 00:30:32.400
So that's actually where I want to get to next is this sort of idea of the form as a sort of quality gate, so to speak, that that catches bad data before it ever gets in, you know, duplicates, incomplete entries, the risky submissions.
00:30:32.559 --> 00:30:35.839
Um can you talk about how that all works?
00:30:36.160 --> 00:30:37.039
Yeah, absolutely.
00:30:37.200 --> 00:30:48.160
So there's a uh there's a very basic component, very similar to regex, if your uh users are familiar um with just kind of like form building in general, because obviously you can create your own forms with HTML and CSS.
00:30:48.559 --> 00:30:52.160
Um, but there's a validation of the fields that come in.
00:30:52.319 --> 00:30:55.680
So if somebody gives you an email address, it should look like an email address.
00:30:55.759 --> 00:31:00.079
It needs to have an at, it needs to have a domain, it needs to have something before the at, right?
00:31:00.240 --> 00:31:09.519
Um, same with uh phone numbers, especially for my international customers, making sure to collect country code in addition to any area codes and then the full uh number.
00:31:09.680 --> 00:31:14.559
Um and having those um field validations be smart as well.
00:31:14.799 --> 00:31:21.599
So if you're collecting a phone number from the UK, it looks different than it would in North America, for instance.
00:31:21.759 --> 00:31:23.680
Um those are the kind of things that we support.
00:31:23.759 --> 00:31:28.640
And that's really like bread and butter validation, just making sure that data is in the right format.
00:31:28.799 --> 00:31:35.359
Um, beyond that, though, there's that smart logic that uh, you know, if a record already exists, update it.
00:31:35.519 --> 00:31:37.279
If it doesn't exist, create it.
00:31:37.359 --> 00:31:40.160
And if it looks a little strange, do something else with it.
00:31:40.319 --> 00:31:51.440
That's where FormAssembly's kind of data quality component really shines, is giving people this opportunity to go outside of the systems of record and start to defend against bad data entering that system.
00:31:51.519 --> 00:31:59.279
I kind of gave that example already of, you know, like, hey, if this doesn't look right, let me put this on a spreadsheet for investigation later.
00:31:59.440 --> 00:32:14.160
Just being able to do that saves teams from this kind of hunting and pecking through the CRM, or worse, you know, having bad data show up much later in a process when a salesperson gets on a phone call, or when you try to reach a customer and realize this email address is a dead email address.
00:32:14.319 --> 00:32:16.079
We don't know how to get in touch with this person.
00:32:16.319 --> 00:32:28.000
So, you know, that's that's where we really see kind of like our value there is you can make sure that bad data does not enter your system because there is data deduplication tools.
00:32:28.160 --> 00:32:31.359
There are duplicate rules inside of Salesforce.
00:32:31.519 --> 00:32:36.240
Again, that requires you to send them into the platform and pollute your data before you start using it.
00:32:36.319 --> 00:32:45.680
So really we we see a lot of value in taking that fight basically outside, if you will, you know, and uh uh having it outside before it enters the CRM.
00:32:45.759 --> 00:32:47.039
Um and it saves people time.
00:32:47.119 --> 00:32:51.839
That's that's what we continue to hear when customers uh start raving about FormAssembly after they get on the platform.
00:32:52.000 --> 00:32:55.920
They start saying, hey, you know, I'm saving 35 hours across my team every week.
00:32:56.079 --> 00:33:01.839
We're really able to do more with our time now because we're not spending time on manual data cleanup.
00:33:02.240 --> 00:33:17.200
It's so much, it's you save time and you know, I imagine you save a bunch of money too to reject sort of the bad data at the door, again, keeping with that door analogy, um, than it is to sort of scrub it out of your CRM, you know, X months later, six months later.
00:33:17.440 --> 00:33:28.960
So, so every okay, at the up to this point, every everything we've described, you described sounds um great, but I want to play uh a skeptic a little bit here for a second because there's yeah, there's a there's a sort of a switch involved.
00:33:29.039 --> 00:33:30.960
Um let's I want to talk about migration.
00:33:31.039 --> 00:33:39.200
Like what are people maybe worried about when moving to a centralized platform and and and how do you help alleviate that sort of worry?
00:33:39.759 --> 00:33:45.759
Yeah, well, I mean, you know, as I pointed out earlier, there are so many data collection tools.
00:33:45.839 --> 00:33:54.960
Uh, we did a survey about two years ago, um, and just trying to ask people if they were aware of how many data collection tools were at their organization.
00:33:55.119 --> 00:33:57.359
We came back with an average of 3.5.
00:33:57.680 --> 00:34:01.519
Um, and that was just what the CIO or the CISO was aware of.
00:34:01.680 --> 00:34:08.159
And almost every one of them flagged that they were really concerned that they didn't have full visibility over every platform that's on their system.
00:34:08.320 --> 00:34:15.280
So when you're dealing with that many tools to try to consolidate from, you're like, this is a project that's going to take months, right?
00:34:15.440 --> 00:34:19.599
Uh, you know, this is something that I'm going to need a big team dedicated to.
00:34:19.679 --> 00:34:24.639
I'm going to have to interview all the stakeholders at this organization, and it's going to take me a long time to migrate.
00:34:24.800 --> 00:34:26.639
Um, and we've we recognize that.
00:34:26.719 --> 00:34:36.320
Um, you know, like the worst part is most of these organizations that are trying to find a consolidated platform uh cannot take time off of these systems being up and running.
00:34:36.480 --> 00:34:39.360
They need these forms, every form collecting information.
00:34:39.519 --> 00:34:42.639
So any kind of downtime is a problem.
00:34:43.039 --> 00:34:50.639
Um, we have made done everything we can to make it incredibly easy to bring your data collection processes onto the Form Assembly platform.
00:34:50.800 --> 00:34:59.920
You can do something like take a screenshot of a form that you already have existing or a PDF version of a paper form that you have at your organization.
00:35:00.079 --> 00:35:01.679
You can upload that into our system.
00:35:01.760 --> 00:35:03.440
We call it file to web form.
00:35:03.760 --> 00:35:12.159
It will create a form for you that matches all of those data collection fields that you have either on that screenshot or in that PDF form.
00:35:12.400 --> 00:35:19.280
So do you still have this, we'll call it a responsibility to go find all of the forms in your organization that you want to replace?
00:35:19.440 --> 00:35:22.000
Yes, that is going to be a part of the project.
00:35:22.159 --> 00:35:27.920
But the actual conversion or migration is going to be a matter of moments, right, for each of those forms.
00:35:28.079 --> 00:35:34.320
So you can be up and running in days and replace those forms immediately with no downtime.
00:35:34.480 --> 00:35:46.159
And we've seen a lot of success, even with longtime users of FormAssembly, you know, like uh finding out how easy it is to bring new forms and new processes onto the platform, they're starting to automate things that they didn't really think about.
00:35:46.320 --> 00:35:54.000
You know, sometimes you can look at a paper format's at your business and be like, this should really be digitized, but it's like a multi-page packet.
00:35:54.159 --> 00:35:55.360
I'm not doing this, you know.
00:35:55.519 --> 00:35:57.039
I need, I need a week to do it.
00:35:57.199 --> 00:36:02.719
When you don't, when you need 60 seconds, uh, those kind of projects start to fall much faster.
00:36:02.800 --> 00:36:07.840
And uh again, your organization suddenly is, oh, all of my processes are on one platform in one place.
00:36:08.000 --> 00:36:09.840
I've got better control, better visibility.
00:36:10.000 --> 00:36:14.480
That's when they start to unlock kind of this idea like, oh man, my organization can be automated.
00:36:14.559 --> 00:36:15.760
This is looking much better.
00:36:15.920 --> 00:36:20.960
So uh yeah, the the migration problem is much less of a problem than it used to be.
00:36:21.280 --> 00:36:35.760
Now, I I don't want to put you too much on the spot here, and you don't have to name names or anything, but I'm just curious if you have a maybe a favorite customer story that comes to mind, like maybe a time where fixing data collection just really moved the needle for an organization.
00:36:36.079 --> 00:36:37.679
Anything that comes to mind?
00:36:38.239 --> 00:36:38.559
Yeah.
00:36:38.800 --> 00:36:52.400
So the the name of the customer that I love uh will probably not ring any bells, but what they do uh will, um the Boston Athletics Association is the organization responsible for putting on the Boston Marathon every year.
00:36:52.639 --> 00:36:56.239
And so every year for all of their races, they spin up a form assembly form.
00:36:56.320 --> 00:37:02.960
And if you're I'm well, I'm not as much of a runner as I used to be, but I have run many half marathons and tried at least one marathon.
00:37:03.119 --> 00:37:09.519
If you're familiar with that process, that sign up process can be, well, it used to be a lot of paperwork.
00:37:09.599 --> 00:37:11.039
Now it's a couple of forms.
00:37:11.199 --> 00:37:14.960
The Boston Marathon is one of the largest races in the world.
00:37:15.039 --> 00:37:19.519
So the scale at which they need to collect information is astonishing.
00:37:19.760 --> 00:37:29.199
But every year, uh, they they slightly modify a form assembly form that they've used in years past, and they use that to sign up thousands upon thousands of uh racers every year.
00:37:29.280 --> 00:37:31.440
And they collect a variety of data with that.
00:37:31.599 --> 00:37:37.679
Uh, you know, as I mentioned, you might not think about collecting uh personally identifiable information for a race, right?
00:37:37.920 --> 00:37:43.199
But you need medical contacts, you need age, you need uh phone numbers, you need addresses.
00:37:43.440 --> 00:37:48.960
Starts to look like sensitive information, things that you don't want to trust to just any old free, medium form builder.
00:37:49.280 --> 00:37:53.280
I want to pick your brain about the industry and then also sort of your leadership style.
00:37:53.440 --> 00:38:03.119
Um, first of all, what's a common misconception about your industry, you know, forms, data collection, whatever you want to call to call this space that you really wish people, more people understood?
00:38:03.599 --> 00:38:09.039
Yeah, I think um for too long, you know, these uh this idea that uh forms are just forms.
00:38:09.199 --> 00:38:19.840
And uh again, you know, you kind of mentioned they're set it and forget it, and um they're really limited, and all they are are a door for someone to walk through, and really it's where that data goes is the most important part.
00:38:20.079 --> 00:38:22.639
I uh I think that people are starting to realize this.
00:38:22.800 --> 00:38:30.400
But again, um, you know, if you have security and compliance concerns, they need to be handled at every level of your software.
00:38:30.559 --> 00:38:35.360
But also there's a lot more capability out of what you can do with that front door.
00:38:35.440 --> 00:38:43.440
Um, you know, you might think of the front door of your home as just, hey, the way to get in, but that's also where people start their journey into your home, right?
00:38:43.599 --> 00:38:49.599
Uh would your foyer look uh better if you uh knew you were going to have a thousand runners come through it?
00:38:49.760 --> 00:38:52.000
Maybe, or maybe you lay out a carpet at least.
00:38:52.159 --> 00:39:01.280
So um I think I think, you know, just changing that concept that forms are just forms and that uh you don't need to worry about where the data goes, I think that's the biggest change.
00:39:01.440 --> 00:39:04.239
I think the the whole industry is heading that way already.
00:39:04.400 --> 00:39:14.400
But uh in case organizations are still treating this as uh, you know, just a uh a module on a WordPress site or something like that, I think uh a little bit more attention is definitely deserved.
00:39:14.719 --> 00:39:20.880
Um now here's uh here's a sort of uh another follow-up, and you can be as as as spicy and edgy as you want with this one.
00:39:20.960 --> 00:39:30.800
But if you could change one thing about how your industry operates today, uh like a you know, snap of the fingers type of thing, uh, what would it be and why?
00:39:31.599 --> 00:39:41.760
I I do think that um we are, and when I say we, I'll just, you know, kind of thinking at that form level.
00:39:41.920 --> 00:39:45.519
Um I think that we are not helping our customers enough.
00:39:45.679 --> 00:39:48.079
I think, I think that we're not giving enough guidance.
00:39:48.239 --> 00:39:53.679
I think that data collection has so many facets now and so many regulations.
00:39:53.840 --> 00:40:02.559
To your point, there literally is legislation rolling out in several different states, disparate legislation that deals with data collection sensitive information.
00:40:02.719 --> 00:40:07.920
And so that means if you're doing business in a certain state, you are going to have different requirements in another state.
00:40:08.079 --> 00:40:10.800
That's incredibly difficult for any business to keep up with, right?
00:40:10.960 --> 00:40:15.599
And your local bakery still needs to be able to collect customer information, you know, every day.
00:40:15.760 --> 00:40:17.519
And they don't have a legal department.
00:40:17.679 --> 00:40:25.679
I think there's a responsibility for software providers that do operate globally and nationally to pay attention and educate their customers.
00:40:25.840 --> 00:40:27.760
Uh, we try to do that through the platform.
00:40:27.840 --> 00:40:31.760
Uh, there's other ways to do it, hosting webinars, writing blogs, sending emails.
00:40:31.920 --> 00:40:33.760
Um, I think there is more of a responsibility.
00:40:33.920 --> 00:40:34.719
I think we should do that.
00:40:34.880 --> 00:40:37.840
I think we should focus less on just being that commodified layer.
00:40:37.920 --> 00:40:41.599
And I think we need to do more education for our uh for our consumers.
00:40:42.000 --> 00:40:54.960
Which which you are are doing, like you're saying, with the policy library that's rolling out and that education layer to help uh people get a better understanding of of some of these regulations and how they're going to affect the specific, your, you know, your specific organization.
00:40:55.119 --> 00:40:59.039
That, you know, you're you're helping to tackle that that issue.
00:40:59.440 --> 00:41:05.599
Yeah, but you know, I mean, we're we're one player, and I would uh I would never imagine that we'll ever you know take over most of the industry.
00:41:05.760 --> 00:41:17.360
The industry is just so large, but I think every player in the industry should be educating more people uh because you know, a lot of our users are are non-technical people, uh, and they're just reaching for the tool that they need for the day.
00:41:17.599 --> 00:41:24.800
That tool should not come with a warning label, but that tool should say, hey, you know, here's how you could use me better, safer, you know, et cetera.
00:41:24.880 --> 00:41:26.239
I I think we can do more.
00:41:26.559 --> 00:41:26.800
All right.
00:41:26.880 --> 00:41:28.400
Well, last uh last question for you.
00:41:28.480 --> 00:41:34.159
Um, and I have a version of this to uh I ask to a lot of guests because the the answers are always pretty interesting.
00:41:34.239 --> 00:41:44.239
But setting aside forms and and software entirely here for this one, what qualities do you think are really essential for someone who wants to be a leader in today's business world?
00:41:44.639 --> 00:41:47.360
So um I'm blessed to work at a remote organization.
00:41:47.519 --> 00:41:53.679
FormAssembly has been remote first since 20, uh 2006, actually, for more than uh 20 years now.
00:41:53.840 --> 00:41:59.119
Um, and you know, leadership when you're when you're not in the office is a different beast.
00:41:59.280 --> 00:42:04.880
Um, but I think that when it, you know, when it comes down to it, I think uh, well, this will sound generic, but communication.
00:42:05.039 --> 00:42:08.800
But communication needs to look different in 2026 than it used to.
00:42:08.960 --> 00:42:10.480
It needs to include context.
00:42:10.639 --> 00:42:16.320
I don't think any employee at any organization is willing to just take marching orders anymore.
00:42:16.480 --> 00:42:26.960
They need to know reasons behind decisions and they need to know that they're playing a part in a broader whole, and they need to get a sense of what that broader picture looks like.
00:42:27.119 --> 00:42:40.239
And so I think it's a leader's job nowadays to um, you know, beyond direct, beyond, you know, give uh, you know, require tasks or hand out deadlines, uh, you need to communicate the vision of what you're trying to accomplish.
00:42:40.400 --> 00:42:44.400
And I don't mean, you know, as a company with a mission statement or a vision statement.
00:42:44.559 --> 00:42:53.840
I mean with every campaign, uh, you know, and obviously I'm looking at this from a marketing lens, but uh, you know, every time you reach out to your customers, um, that needs to feed into a broader story.
00:42:54.000 --> 00:42:55.599
It needs to have some coherence.
00:42:55.679 --> 00:42:57.679
Uh, and I think you owe that to your employees.
00:42:57.760 --> 00:43:02.559
And it can be difficult because it is a lot of work and you end up saying the same thing over and over, right?
00:43:02.639 --> 00:43:04.480
When you're communicating this to multiple people.
00:43:04.639 --> 00:43:05.840
But I think that's our job.
00:43:05.920 --> 00:43:11.039
I think as leaders, I think you need to uh I think you need to understand the story and the why yourself.
00:43:11.119 --> 00:43:16.800
And I think you need to bring that to anyone that you talk to at your organization, especially those that report to you.
00:43:17.119 --> 00:43:17.519
Beautiful.
00:43:17.599 --> 00:43:19.039
I love that's such a great answer.
00:43:19.119 --> 00:43:19.519
I love it.
00:43:19.599 --> 00:43:20.480
Uh, and it's so true.
00:43:20.559 --> 00:43:21.039
It's so true.
00:43:21.119 --> 00:43:28.000
I mean, there's so much communication is the the it's fundamental for any sort of relationship, uh, you know, personal and professional.
00:43:28.079 --> 00:43:45.760
And yeah, I mean, a lot of us are kind of siloed away um working remotely, and we have to, you know, also we have that the the style of communication is a lot largely over Teams and Slack and email, and you miss a lot of important context, and uh let alone the communication of the the brand and company you're you're working for.
00:43:45.920 --> 00:43:48.400
So, um, and the product of that, you know.
00:43:48.639 --> 00:43:49.280
Very well said.
00:43:49.440 --> 00:43:49.760
I love it.
00:43:49.840 --> 00:43:50.880
I love that takeaway.
00:43:51.039 --> 00:43:57.599
Um, I and now I want to give you a chance uh to direct listeners and viewers to FormAssembly.
00:43:57.840 --> 00:44:01.679
Where's the best place to go to learn more and also get in contact with you and your team?
00:44:02.000 --> 00:44:05.360
Yes, uh I would have you go to uh formassembly.com.
00:44:05.440 --> 00:44:08.480
Um from there, you can choose the path that makes the most sense to you.
00:44:08.559 --> 00:44:13.360
Uh, if you're sick of listening to a marketing guy, give you uh marketing language with exclamation marks.
00:44:13.519 --> 00:44:22.719
Um, I would encourage you to reach out to our team, schedule a demo, get a sense of what uh you know FormAssembly can do, and they can answer some of the more technical uh questions as well.
00:44:22.800 --> 00:44:29.280
Uh, if you're bringing you know custom software, you need if you need to integrate to custom builds or uh have some of those more technical questions.
00:44:29.440 --> 00:44:32.960
We have team members that can answer you, real uh, you know, data collection experts.
00:44:33.119 --> 00:44:34.960
So uh I'd have you start on our website.
00:44:35.039 --> 00:44:36.800
Uh we've got a couple of different paths there.
00:44:36.880 --> 00:44:42.239
You can watch videos, uh, you can read some case studies on uh Boston Athletics Association and other customers.
00:44:42.320 --> 00:44:44.159
Uh, that's the best place to start.
00:44:44.400 --> 00:44:44.800
Perfect.
00:44:44.880 --> 00:44:46.320
All right, formassembly.com.
00:44:46.400 --> 00:44:48.400
We'll place a link down below in the show notes.
00:44:48.559 --> 00:44:49.599
Josh, thank you so much.
00:44:49.679 --> 00:44:50.719
This has really been fantastic.
00:44:50.800 --> 00:44:52.159
I appreciate everything you shared with us.
00:44:52.400 --> 00:44:53.039
Thank you, Bo.
00:44:53.199 --> 00:44:54.159
Appreciate the conversation.
00:44:54.320 --> 00:44:55.679
Appreciate the research that you all do.
00:44:55.760 --> 00:44:57.119
Um, thank you, SourceForge.
00:44:57.199 --> 00:44:57.760
Glad to be here.
00:44:58.239 --> 00:44:58.480
All right.
00:44:58.559 --> 00:45:00.559
Well, thank you all for listening to the SourceForge podcast.
00:45:00.639 --> 00:45:01.920
I'm your host, Bo Hamilton.
00:45:02.000 --> 00:45:06.800
Make sure to subscribe to stay up to date with all of our upcoming B2B software related podcasts.
00:45:06.960 --> 00:45:09.119
I will talk to you in the next one.