ProdProfile: Alexander Michaud (ARM)

1. What’s your background that’s led you to your current position at ProdPerfect?

After college, I decided to work in web development. I went to a boot camp where I met ProdPerfect Co-founders Dan Widing and Erik Fogg. They were exchanging mentorship for some resources when ProdPerfect was still in its early stages. They said: We’ll keep you in mind for our company. Lo and behold, ProdPerfect was growing so fast that they called me basically 8 months later. The offer was way too good to pass up: small company, growing fast. I had a lot of autonomy and got to work with people I knew and respected. 

I’ve now been working here for as long as I was working at my old job. I feel so much less burnout and so much more enthusiasm about where I am than I did being a very small cog in an engineering department of 1,500. And that’s very fulfilling.


2. What sets ProdPerfect apart from other places you’ve worked?

It comes down to the people. There is definitely a coherent ProdPerfect team culture. Everyone at ProdPerfect is the sort of person I want to spend 8 hours a day with. They’re ambitious and excited about what we do, but also grounded and down-to-earth. There are no caricatures. You don’t get the stereotypes of introverted, overly opinionated engineers or hyper-aggressive salespeople. They’re just real people. And God, is that refreshing to work with.  

Everyone is super dynamic and responsive. I’ve seen situations where unwavering preferences about engineering design make people set in their ways. You just don’t see that here. I’ve seen departments complain to one another in a most productive way. In other situations, you can just sense the egos and the tension of “I need something from you.” I’d be shocked if anyone here were anything but super willing and eager to help in any way they can. Of course, there’s push-back and there is constructive debate and dialogue. But there’s never: “We’re going to do our thing our way.” People are intellectually modest enough to lean on others. Nobody is so entrenched in their biases that they can’t see the greater picture.


3. Can you paint for me a picture of what life is like in your role?

As delivery engineers, we produce the final, customer-specific deliverable. We take information that comes from data engineering and use it with tool sets produced by other teams to produce a test suite. This is a big chunk of code which tells the machine to simulate the experience of a user clicking through a site. And we set that code to run on a timely schedule. In theory, if the customer sets it up, it also runs every time their engineers want to make a change to their website before it goes live. We encourage customers to use our product as a final check mark that confirms they’re set with every change they make.

I divide my job into things that are predictable and things that aren’t. Predictable things are part of the regular cycle of spinning up a customer: collecting data, running the analysis, and generating test cases. Once test cases are generated, I oversee the people who write tests: I review their code and answer questions. I also communicate with the customer about the state of the test suite and things we need clarification on. Then we hand it off. All of this usually happens within six weeks. What’s not predictable is we’re constantly monitoring when our tests fail and figuring out why. If it’s a bug, we forward the information to the customer. If it’s a change in the website or something goes wrong with tests, we update the tests. New features, new tools, and one-off things also comes up all the time, so I budget some time in for the unpredictable every day.


4. What are some elements of a typical interaction with customers?

With customers, I get brought in as early as the product demo stage. We serve a technical support role alongside salespeople as they walk customers through our product. Being close to the production of the test suites and understanding the data engineering team’s analysis, our team is in a good position to clarify and respond to more specific technical questions. We’re also brought onboard to understand the peculiarities of customer applications to determine if ProdPerfect will be a useful tool for them. Once the contract is signed, we are part of the process all the way through: we get all the information we need in order to access their staging environments to test against them. We communicate with them about the progress of gathering data and the creation of their test suite over Slack channels.


“We are part of the process all the way through.”



5. What intrigues you about delivery engineering at ProdPerfect?

Some engineering departments can feel peripheral and maybe foundational, but not central. We feel central. The organization has a lot of moving parts, but ours is the one that most closely looks like what we describe when we talk about our products and services. We produce the deliverable. Being responsible for the final deliverable has its own privileges and challenges. We are relying on and therefore learning about every other department. This means we have to have a shallow amount of knowledge about everything that’s going on around us. Extracting what others are producing as it’s relevant to us is sometimes the most efficient way to get the heart of what they’re doing. That’s a lot of my day. It’s fun to be able to learn a little bit about all parts of the organization. There really isn’t anything we don’t touch or that doesn’t touch us.


6. How do you explain to people the value of ProdPerfect?

We collect information about how people are using your website. And we recommend tests to be created that specifically verify that the parts of the website most people see are working. If the log-in page is seen by 80% of users that visit your site, you want to make sure that your log-in page is working. I often get asked how ProdPerfect is able to support a bunch of different organizations in quality assurance testing. The answer is because we’re making test suites that aren’t trying to support everything. We’re identifying the most important stuff. 

We’re not trying to be the be-all and end-all; we’re trying to provide a very targeted kind of value. It’s not worth your time to put the same amount of effort into resolving a niche edge case versus things that are more visible or that iterate on your product. We explicitly don’t do that. Everything is a trade-off of time. Choosing this trade-off gives us the ability to maintain the test suite in a more robust and dynamic way, which is a really unique principle that ProdPerfect operates under. 


7. In your own words, how would you differentiate ProdPerfect from competitors?

The major thing that distinguishes us is data collection. Anyone can give a contractor access to their application and tell them: “Go through and make a bunch of automated tests based on whatever you think should be tested.” It’s another thing entirely to give people the power to say: “We’ve got the top 70% of our workflows covered.” People appreciate that knowledge and sense of security. They appreciate that we integrate with their development workflows in a way that can mean that they never push a bug to production. We have customers that testify to that.

We are also very focused on the kinds of customers we are working with right now. We’re not doing a lot of mobile or native desktop testing; we’re focused on web applications. So our customers are usually Software as a service (SaaS) companies—usually smaller, start-upy kinds of companies that are iterating quickly and are more liable to make mistakes, but will also suffer more because of mistakes. In this sense the customer we’ve started to target in the space we occupy is getting more specific as we mature as a company.

ProdProfile: Nicola Molinaro

1. What’s your background that’s led you to your current position at ProdPerfect?

I’ve been working in technology sales for the past 13 years and previously was at a company where I successfully sold to ProdPerfect cofounders Erik and Dan. Erik and Dan ended up in NYC last summer because they were accepted into the Entrepreneurs Roundtable Accelerator (ERA) program. We’d hang out, get drinks, eat, and really got to know each other. And because I had sold to them and they enjoyed working with me, they said: “We want you to come sell for us.” 

Working at ProdPerfect has been extremely exciting. I accepted not only because it was an awesome opportunity for career growth and learning where I knew my opinions and feedback would have a real impact, but also because ProdPerfect is doing something absolutely revolutionary in the industry that shines through in the work that I do every day.


2. Can you paint for me a picture of what life is like in your role?

I meet with CTOs, heads of engineering teams, directors, and heads of QA regularly and speak with them about how we can improve their regression testing efforts, increase efficiencies, save their team time, and better accurately test. I often hear healthy skepticism from them: “This sounds like magic/Does it actually work?” and then I get to show them it’s not magic and it does work. It keeps me on my toes and is exciting to demonstrate that our solution can provide them a bunch of benefits they never thought they could have. It’s also fun to hear people get elated and say things like: “How has no one thought of this before?!” 


3. What are some elements of a typical interaction with customers?

Organizations don’t want to feel like we’re adding in more work or hindering their processes, but that we’re taking this work off their plates and helping them. So we make it clear that we’re integrating right into their Continuous Integration (CI) tool so our tests run with every build automatically, as if they had built them in-house. And because we’re driven by data, we’re able to take on the maintenance of the code as well: we fix broken tests build-to-build and add new tests as the web app evolves over time. Our model alleviates concerns around how much work they’re going to have to do.

Typical reactions after the first call are: “Wow, this definitely seems valuable.”  “This seems like magic.” “Everyone should have this!” And of course: “I like the promise that you’re making, but I need to learn more.” Sometimes, clients are skeptical that there’s a particular area of their platform that we’ll be able to support. I’m a big advocate of being honest and upfront. Having a demo of the client’s platform as a step in our process to assess what we can and cannot handle and being transparent about that helps to 1) level expectations with the client, and 2) instill confidence in working with us.



“We’re integrating right into their Continuous Integration (CI) tool so our tests run with every build automatically, as if they had built them in-house.”



4. What intrigues you about your role in sales at ProdPerfect?

I get to challenge the way people think about testing. In regression testing, coverage has always been: “What percentage of the application is covered?” We’re asking people to philosophically change the way they think to consider: “What if we could guarantee that the majority of observed user behavior from production is being covered by our testing suite?” Challenging people way more technical than me, who’ve been doing engineering for 15, 20+ years.  

We also challenge perspectives that existing test suites encompass the “right kinds of tests.” One company had built 1,000 of their own test cases, which took hours to run, and they couldn’t run a regression test with every build as a result, which meant they’d see bugs in production even though they had many tests. Our response to this dilemma was: “How do you know those 1,000 test cases you’ve created are the right tests?” And to help them see it as: we’re going to build a lean test suite based on user behavior that runs with every build and catches more bugs” because we’re testing accurately for how users are using the platform.


5. How do you explain to people the value of ProdPerfect?

For someone with no tech experience: when you build software, you need to test it. A lot of companies test their software manually or build automation. But automation needs to be maintained. That takes time and money. Figuring out what to test is one of the hardest jobs in the testing world. Humans are guessing what to test and then spending time building and maintaining tests as the application changes over time. Yet, they’re not always testing accurately. ProdPerfect’s solution automatically builds and maintains test suites based on real user behavior so companies don’t have to do it or maintain it themselves.

For someone technical, I’d ask them questions like: “Hey you have a web app, how are you testing it? What’s a pain in the butt about it? How much time are you spending manually testing or building/maintaining automation? Let’s talk about how we can automate the whole process so your team doesn’t have to spend effort or mindshare on it.” Just higher-level, taking it off team plates so they don’t have to bother with it. I’ve never heard one person say in the last year that they enjoy doing regression testing. Customers know we’ve got them covered.


6. What are the top few frequently asked questions people have about us? About our product?

One common question is about things that won’t get picked up from data, which is what’s used to build our testing suites: “We’re worried you’re not going to get enough traffic around what we need to be covered. You won’t pick up on this really important edge case or mission-critical feature.” We solve for this by allocating a certain amount of wildcard test cases for each client: custom test cases they can hand off to us. And we’ll build out those tests, incorporate them into the suite, and maintain them alongside other test scripts that were generated from the data.

Some people are wary about letting us control maintaining and updating the code. Recently, we’ve come out with new functionality in our test results summary web portal that allows clients to request to skip a task if they know a big User Interface (UI) change is coming. This new functionality removes that test out of the suite and adds it to a queue to be fixed by the delivery engineer (proactively rather than reactively) so that when the client deploys, that test failing doesn’t block the deploy.  

Privacy and security is a concern as well, as we’re asking companies to put a data tracking snippet onto production so we can collect clickstream metadata. Once we explain and/or prove that our snippet avoids collecting PII (by not collecting any keystrokes or info about the dom) and that we don’t have a performance impact on production, we can normally circumvent lengthy infosec processes, but we also have a ton of experience going through them as necessary.


7. In your own words, how would you differentiate ProdPerfect from competitors?

We’re the only tool/service in the industry that’s solving the most critical challenge of testing: knowing what is important to test. With other tools and services, you still have to define test cases or user stories and hand them off for crowdtesting, or build and maintain automation. Humans approximate what they think should be the test cases, then build a bunch of tests, some of which aren’t important. This increases deploy time and sometimes prevents us from running a regression on every build. Bugs still make it to production because we’re not accurately testing for how users are using the application.  

ProdPerfect uses live user traffic to both 1) build an automation suite and in the process catch more bugs before production. And 2) maintain the suite. Teams put dozens to hundreds of engineering hours into fixing broken tests and maintaining automation suites. Our model allows us to automatically evolve the suite and keep the code maintained for clients, all the while providing real-time feedback to QA/dev teams on every single build.

ProdProfile: Wilson Funkhouser

1. What’s your background that’s led you to your current position at ProdPerfect?

I’ve always loved math. In fact, ProdPerfect Cofounder Dan Widing and I became friends on the math team and chess team (state champions!) growing up. I majored in math and economics with a minor in psychology. I used that to design financial software before eventually getting into a consulting company which gave me a lot of exposure in the startup world. I worked on everything from water conservation startups to conversion optimization tools to the e-commerce site for a brewery called “Mobcraft Beer.” I went to get my master’s degree in data science. All the while, Dan and I kept barely missing each other with job opportunities. Finally, at the end of my master’s program, my other co-Founders Dan Widing and Erik Fogg called me up and said: “Hey, let’s make a company. Let’s actually try and automate QA.” What do you do when they say that? I said: “Yeah, let’s do it.” That’s how I got here: nerdiness and wanting to solve cool problems.

2. Can you paint for me a picture of what life is like in your role?

As head of Data Science, there’s always the need to explore both the data we already have and the new stuff we can do with it. But, I am far more of a mathematician than a data scientist and slightly more of a product/UX designer than a mathematician. Therefore, I’m working to hire people who are going to be substantially better than me at data science, and that’s great. One of my goals in life—much less ProdPerfect—is to build my team to the point where I’m no longer needed.

I’m excited to focus more on product work: there is so much beautiful user-experience (UX) exploration, data visualization, and design to work on. By improving our transparency and visibility of some of our analysis, we’re going to improve the value we provide to our customers. We have the opportunity to transform the QA ecosystem. In the nearer-term, we can provide information about our test suite, our analysis of customers, and the bugs we find in a way that provides serious value for Quality Assurance (QA). Longer-term, we can do this not only historically, but predictively. We can give tools to QA teams to figure out what parts of their applications are the most vulnerable in a way that is focused on customer behavior. It prevents QA teams and engineers from burning out. I love it. Best of all, we have a fantastic team of people whose experiences and skills we can draw upon that are just as excited as me about this.

3. What are some elements of a “typical” interaction with customers and/or product?

This has certainly changed over time. Initially, there was constant interaction with customers. That’s because when the company was first founded, we had to figure out what customer data we could even collect, much less how to use it. In contrast, a lot of the work I’ve been doing this past year has been focused on making the job of maintaining customers easier; providing better or different information, making it easier for us to access and interpret data that comes from running test suite. Now, data science is finally getting to a place where I can once again start focusing on how we’re actually establishing value to the customer. As well as cool stuff like: “What’s the new value that we can provide to the customer?” So I’ve gone the full gamut from very closely interacting with new customers, to diving deep with a single customer, to having months of my customers and stakeholders being internal. Now, it’s finally looping back.

“We can give tools to QA teams to figure out what parts of their applications are the most vulnerable in a way that is focused on customer behavior.”

4. What intrigues you about your role in data science at ProdPerfect?

We are in the true golden age of data ethics. We get to figure out what data ethics means to the world at large. Data scientists have a concept of data ethics. But when it comes to consumer protection, personal privacy, GDPR—you name it—there’s so much to be navigated. At the same time, we are in a golden age of exploration in data science. You can log into an online open course like Coursera and within hours feed in the entire works of Shakespeare or Anne Rice and make a Twitter bot that spews out content. It takes longer to understand how it works, but the tools are available. How amazing is that? Every day there are more tools laid at our feet.

At the same time, I am a data scientist who has something of an aversion to data science. If you ever bring up machine learning or AI or data science to most engineers, you’ll likely be greeted with eye rolls and apprehension. AI isn’t perfect, machine learning isn’t perfect. Unless you are careful, you can bake black boxes into your system that are hard to fix and difficult to get five 9’s out of. Today’s culture has pushed the allure of machine learning without necessarily being able to back it up with improvements in this consistency. At ProdPerfect, we’ve applied machine learning. And it’s fantastic. But we’re doing it in a reserved manner because recklessness with these tools can lead to poor results that are difficult to diagnose. I’m a data scientist who loves data science, but remains skeptical of it. That’s why I encourage us to use it sparingly.

5. How do you explain to people the value of ProdPerfect?

We do hands-off QA testing. For someone who doesn’t understand Quality Assurance, I’d say: “We teach robots to make sure websites don’t break by feeding them anonymized behavior of your users.” There are thousands of analytical tools out there right now. You can use those to gain thousands of discrete insights. But none of those are really telling you what should be tested on your website. None of those are telling you: “What—if it does break—is going to hurt the use or usability of other parts of your website?” If I just say that, people get it. We’re using what users are actually doing on peoples’ websites to figure out what needs to be tested. That’s the insight people are incredulous about.

Here’s an example: my mother sometimes orders mail-order steaks online. The website only allows you to apply one coupon. Guess what? The customer service line often allows you to apply more. She uses the website differently from those that designed it. I don’t understand how my mother can use a website in a manner that seems different from all other humans on the planet. But she has a penchant for breaking web apps in beautifully unexpected ways. And if she’s doing it, other people are doing it. Keep in mind I used to design web apps; I’ve done the work of a senior QA engineer to give direction on test suites. And by looking at what ProdPerfect showed me, I realized I was consistently wrong about what should be tested. I’ve been in those shoes, I know a person deciding what should and shouldn’t be tested is going to make mistakes. Your users can and will surprise you.

6. In your own words, how would you differentiate ProdPerfect from competitors?

Any other service out there I will loosely group into two groups. One is the throw-everything-at-the-wall-and-see-what-sticks group. Those are the companies that make thousands of small regression tests which run continually. Even if you can run those all in parallel, your test suite is going to take a heck of a long time to pass. Then you have other customers where it’s not actually hands-off QA. You still need someone at your own company who understands QA and your website to say what should be tested. This second group is great at maintaining tests. And they are fantastic at automatically healing tests. But that’s not the same as hands-off QA testing.

We’re filling this niche of telling you what should be tested in a data-driven manner. That’s something no one has ever done before with this level of granularity. And make no mistake, bugs will get into production. You can have the best engineering team, the best QA tools, the best automated QA tools. Bugs will get into production. But can you prevent the critical bugs that will affect a critical mass of users? That’s something that we can say with increasing confidence as time goes on. Yes, we can prevent those bugs.

ProdProfile: Josh Pevner


1. What’s your background that’s led you to your current position at ProdPerfect?

I came from a completely weird gig doing natural language processing, machine learning, and healthcare-related work. And then Co-founders Erik and Dan told me: “Hey, we’re working on this project, it’s really interesting.”  And then they pitched it to me. And I was like: “Oh, that’s absolutely boring. That’s a brilliant business.” A lot of people go after these hyper-local, social, global kind of businesses. This is the exact opposite of that. It’s not particularly interesting, which is exactly why we want to automate it. I’ve built some of these regression tests before. It’s not a fun gig. It’s tedious, painstaking work, and that’s why we are making it go away.  


2. Can you paint for me a picture of what life is like in your role?

My day-to-day is an adventure. My role straddles a lot of lines between doing the grunt work of coding and the people management side of making sure my team is happy and knows what they’re doing. In QA, so much of your job is being this relaxing force for the customer that you in turn want to make yourself a source of calm. But the company is changing so fast that the delivery team is constantly on fire. That’s the heart of opportunity right now: making it so that we live by our philosophy of avoiding burnout and automating menial labor. So what we’re working on is building up internal tools to make it easier for the delivery team to address what happens when a client’s test fails. Getting as much as we can into a process that’s at least scalable, if not truly automated.

3. What are some elements of a “typical” interaction with customers and/or product?

Our team tends not to have direct interactions with customers.  As far as product: we’re the “secret sauce” of the company. We have this thing called the analysis engine.  It’s where all the automation happens. The analysis engine takes in all the client’s data, slurps it all up, and says: “Okay, here are all the tests you actually want to run.” And it does this by performing this analysis saying: “Let me map out your website, and then look at the most popular flows through it.” It’s like looking at where the most congestion is on a roadmap. And saying: “This is what we need to be watching.” That’s what gives us our coverage. Currently, we generate what’s called test cases that get turned into tests. The goal over the next couple quarters is to move directly to generating. Generation and automation is a big part of what we’re working on. Also, improving the quality of the results: making them robust and scalable and all those magical things.

That’s the heart of opportunity right now: making it so that we live by our philosophy of avoiding burnout…”

4. What intrigues you about engineering at ProdPerfect?

My role is very multi-faceted. The job has two different sorts of challenges. The technical challenges are pretty straightforward. The human relationships and management side is more butt-kicking—making sure everyone feels like the company is following its values, knows where they’re supposed to be, and turns into this harmonious hive. Whereas everything is already built out in a bigger company, here we’re growing together as a family. We’re learning that what you focus on is everything. This is definitely a values-first company. So making sure what we focus on aligns with our values. From building culture to building internal processes. And making sure our product reflects those values. 

5. How do you explain to people the value of ProdPerfect?

You don’t need to be technical to appreciate ProdPerfect’s value. The value of ProdPerfect is that it keeps peoples’ websites up. We find bugs. That’s what we do. Our job is to make sure that when people make changes to their websites, they don’t break them. We find problems with peoples’ websites before they do. That’s what our tooling is about: analyzing a website’s traffic, building up a set of test suites so we understand what works and what doesn’t. And then quickly informing the customer when it doesn’t. The fact that it’s such a straightforward value proposition is why I joined ProdPerfect.

6. In your own words, how would you differentiate ProdPerfect from competitors?

A lot of folks who generate tests tend to put a lot of the labor on the customer – they are product companies. Whereas we are a service company. As much as we are converting into a product company over time, because we’ve had a background as a service company, that’s going to shape the DNA of the product to be much friendlier. We will continue to provide support. Because being there for the customer matters. There’s also a difference culturally. We’re in a different phase than our competitors. They’re a little bit more mature, and that’s why they’re going to need to figure out where they’re going next. We’re going to wake up to that same problem one day. But I believe that because we’re self-aware, when we enter that world we’ll be prepared.   

ProdProfile: Kyle McCullough

1. What’s your background that’s led you to your current position at ProdPerfect?

My background is mostly in back-end software engineering, site reliability and operations. I’m familiar with standard QA practices, but it’s never been my job.

I knew ProdPerfect was a good fit because, in my prior job, I built a smaller-scale version of what ProdPerfect does. I built an environment that allowed our internal teams to test any branch of their software in a scalable, dynamic QA environment. That project gave me an idea of what it would look like to do this kind of work at scale, which is one of ProdPerfect’s primary goals—to make testing easy and scalable.

2. Can you paint for me a picture of what life is like in your role?

At this stage, we’re figuring out how to scale, which is one of my favorite problems to solve. I like taking a technical solution and figuring out how to expand it and roll it out.

One project my team is working on now is what we call our remote harness environment. Until recently, customers ran tests in their own Continuous Integration (CI) systems. They would maintain their own servers to do that. The remote harness allows customers to run tests on demand, on infrastructure that ProdPerfect controls. They don’t have to worry about running servers or doing anything that would make integrating with ProdPerfect difficult. My job is building that and then scaling it. I.e.: How do we support 10 times as many customers as we have now?

3. What are some elements of a “typical” interaction with customers considering our product?

The role of my team is to maintain infrastructure, build APIs, and provide a nice, uniform experience for running workloads in our environment. So my interaction with customers is through tooling—publishing and releasing tooling customers can use to run tests. Our goal is to provide consistent, reliable tooling that behaves predictably and is a joy to use.

Internally, it’s a support-based interaction. If customers have questions like “How does this work?” or “Why is this not working?”, we’ll investigate, support, and troubleshoot. We’ll figure out why the environment is failing to behave the way we want it to. For other teams, we develop best practices and make sure that, across the organization, we’re doing things consistently in a way that’s scalable and maintainable.

“I saw how powerful my work was in enabling other teams.”

4. What intrigues you about engineering at ProdPerfect?

The thing that got me hooked was when I saw how powerful my work was in enabling other teams. I realized the work I’d done—even though it was difficult—was worth the investment because it saved so many other teams so many hours. The idea of doing that at scale was really interesting. It’s a really hard and finicky problem to solve even for a single company. So it’s super ambitious to solve that broadly for lots of companies.

I also find it interesting because we’re a start-up. You don’t know how we’ll grow. So it’s the excitement of building something out that doesn’t exist yet and learning how to scale it as the business grows.

5. How do you explain to people the value of ProdPerfect?

The value we provide is in making the process of developing software better and in making better quality software. We cut out friction by making it easier to test, maintain and develop software, and deploy things with confidence. Of course, there’s also value in money saved in not shipping bugs.

Another thing I think about for anyone involved in the development lifecycle is: How frustrating is it for them to test software and get a release out? If we make testing easy and quick, everyone will use it. But if it’s tedious and frustrating, people are going to skip steps. And they’re not going to use systems that are there.

One of the other things that got me hooked was our CEO and Cofounder Dan’s vision and enthusiasm. The company has a set of values and everything revolves around that.

6. In your own words, how would you differentiate ProdPerfect from competitors?

We are multiple products in one. There’s the analytics side: capturing analytics from customer sites. Then there’s machine-learning automation: a lot of companies do testing, but our efforts are to remove humans from that process and still make testing useful. Then, there’s what my team does: serve as an infrastructure provider. We’re not just handing off tests and saying: “Here, go run these.” We’ll even run the tests for our customers.

We collect the data, develop the tests in an automated fashion, and we even provide the infrastructure to run those tests. It’s as low-friction as we can make it. The unique combination of how we’re solving this problem is definitely what sets us apart.