Mai Bui, Building a Design Wiki

"Why do hardware teams still rely on brittle slides and spreadsheets?" asks Mai Bui, cofounder of Quarter20. "A CAD‑connected wiki can turn documentation into living, executable knowledge."

Quarter20 shows auto-updating work instructions, technician analytics, and a cloud workflow that links design to the shop floor.

• The boiling frog of legacy CAD tooling and manual documentation
• Quarter20’s origin story from real manufacturing pain
• A CAD-connected wiki as a single source of truth
• Replacing PowerPoint and Word with live documentation
• Linking hardware tools like software’s integrated stack
• Customer use cases in robotics, agtech, and medical
• Demo of auto-updating images, BOMs, and part tagging
• Cloud access without CAD laptops and large model performance
• Technician mode, analytics, and feedback loops
• Pricing by team with editors and technicians

"Mention 'Roopinder' and I’ll give you a discount because I’m excited to promote more conversations for innovation and design," says Mai. 

Transcript

Setting the stage: old vs new CAD

Roopinder 0:19

Today, Mai Bui co-founder and CEO of Quarter20, a cloud-based AI-powered platform that automates and modernizes hardware documentation workflows. In other words, a Wiki for mechanical design. Mai has a master's of science in mechanical engineering from Stanford, as well as a degree from UCLA Business School. She has held engineering roles at SpaceX, Tesla, and All Motors, experiencing firsthand the frustration of hardware and manufacturing operations. Purpose of the show, Mai, is to go more into depth in emerging technology. The podcast is called Future of Design and Engineering Software. Really, it's all about what CAD design and simulation ought to be, not what it is now. You guys seem to be perfect for that rule because I might represent the old school. I'm thinking people like you are the new school.

Mai 1:13

I'm excited to chat. I have SOLIDWORKS pulled up on my computer right now. SOLIDWORKS in the UX is not updated in the 10, 15 years that I've used SOLIDWORKS, yet it's still the tool that absolutely every engineer uses. So I'm excited to be part of the forefront of building new tools for hardware engineering teams. I'm excited to be a part of just how much innovation is going on in the CAD in the hardware space.

Roopinder 1:38

I'm looking at your background and it's very impressive. You went to Stanford Masters in Mechanical. Yep. State that you had a little bit of frustration using these design tools or just in the process that's used for design in industry. And that's what led to Quarter 20.

Mai 1:53

It's almost like the boiling frog problem, where if you put the frog in boiling water, you don't notice that the temperature is just rising and rising until you're dead.

Roopinder 2:01

Sorry. I used that in my first editorial. Boiled frog. That was 30 seven years ago. It still holds true, right?

The boiling frog of broken workflows

Mai 2:06

Exactly. It's not as if I go in every day saying, oh, I hate the tools that we use right now. It's just that every single day you go into work and you say, oh, SolidWorks crashed again. I guess I'm gonna go and take a coffee break, or oh, I guess I need to put together another design review deck. Let me just sit at my desk, put in my headphones, wait for two hours to take screenshots of CAD and put them to a PowerPoint deck only for me to get to the design review, have no one look at the spreadsheet or the PowerPoint deck. The state of where we're at right now isn't that the system doesn't work. It works. It just doesn't serve teams. And so when you're looking at hardware companies that are getting impacted by tariffs that are looking for ways to get to production more effectively, more cheaply, you need to find ways to innovate in terms of how they can just build better processes.

Roopinder 2:54

Computer-aided design is kind of a misnomer. The computer is not aiding me in my design at all. I'm waiting for that to happen. I think AI is gonna put computer aided into design. That's what I'm hoping for. I hope it happens in my lifetime. I'm sure it'll happen in yours. So tell me what you're doing. You're using AI somewhat, right? Or exclusively.

Mai 3:14

Yeah, so what we're building is a tool to automate the process of creating CAD-based documentation. We call ourselves the CAD connected wiki for hardware. And I think AI kind of just is this all-encompassing word that people kind of throw around. Really, what we want to do is we want to automate the manual processes that people do to document their work. If you look at the problems that plague manufacturing teams, engineering teams, rarely was it, hey, we didn't know how to design a part or we didn't think about the various forms of analyses we need to run on it. Really, what people are struggling with is I made a design change. How do I communicate this design change to the 20 different stakeholders that are involved? How do I communicate it to my manufacturers, my technicians, my coworkers, the supply chain team, etc.? So we're trying to streamline that communication and really building this central knowledge repository for engineering teams.

Roopinder 4:09

Quarter20 aims to increase the communication and collaboration for teams. Right now, we're doing it through PowerPoints, screen captures and Word documents. How's your process different? Are you prepared to demo this, by the way?

Mai 4:24

Yeah, I'm very happy to show a demo. Absolutely. Everything that you said is what the state of the norm is right now. But let's build up these documents that we will pretend to take very carefully. And then when that review has happened, we just ignore that these documents exist and ultimately knowledge goes to die as the information leaves people's heads because it's just really difficult to use. The product that we're starting with is a work instructions tool to automate the knowledge handoff from design teams to manufacturing teams. And what we do is we're CAD connected. So as you said, the state of the norm right now is to use these legacy tools. It's to use PowerPoint, it's to use snipping tools, to use Excel, it's to use Word. And the problem with that is it's really easy to create a document once, but every time that you need to make a change to it, you have to manually update the images, the parts, the quantity, etc. The ramifications of you not doing that is the technician doesn't assemble the product correctly. It goes into the field and then there's a recall, or there's a major issue with your plane that causes the wing flap to fall off. These are real consequences that happen due to poor design communication and poor collaboration between the design and the manufacturing teams. What we do is build a CAD-connected space for you to automatically push your CAD from, for example, SOLIDWORKS into quarter 20 and build up your documentation from that. And as the design change, your documentation will update as well. And because we also have a platform for folks to operate off of the documents, you can ensure that your technicians are able to operate off of the correct documentation. So really we're streamlining the information across multiple teams, across multiple stakeholders to really have a connected flow of information across the entire product development cycle.

CAD‑connected wiki: vision and scope

Roopinder 6:13

So a connected flow of information. I like the way you said that earlier. Where information doesn't go to die, right? You can use your existing tools like Word or PowerPoint or whatever I have. Does existing tools include SOLIDWORKS or whatever CAD program you're using? Quarter20 just sort of works in parallel.

Mai 6:30

It works in parallel with CAD. What we're trying to replace is the PowerPoints of the world and manually typing out your documents, taking screenshots for your documents. We want to make sure that we use CAD as that source of truth to drive documentation. And so we have a connection to CAD. As CAD updates, you can automatically maintain your documents.

Roopinder 6:49

So you are replacing Word and PowerPoint then. Like I can get rid of Office.

Mai 6:53

I don't think anyone has ever said Office really serves me. That's why you have so many companies building billion-dollar businesses to replace generic Office tools, whether it be Notion or Airtable, or the numerous other companies that are trying to confluence at Lassian the numerous tools built to replace just how antiquated it is to just build a doc for these workflows.

Roopinder 7:15

You might add to that even email and Slack. Like those tools are also used to spread engineering information and they're not really built for it either.

Mai 7:24

No, and if you think about the corollary of software engineering, the reason why software engineering is it's easier to build a software and launch a software product than a hardware product. One of the reasons why software engineering really sings is because of all the connectivity between different spaces, right? You have the ability to plan your sprints in Jira, but you're able to connect Jira to your code base and you're able to connect it to GitHub. You're able to connect it to Sentry for you to do error tracking if there are issues that come up in your staged environment or your production environment. You can link it to Slack. All of these different tools are linked and connected together. If you think about the hardware stack, it's you have SOLIDWORKS in this nice little silo that sits by itself for CAD. You have PLM that kind of talks to SolidWorks. And then you have your PowerPoint, you have your Word, and you have your Google Drive, and you have your Confluence. And they all sit in different places and they don't connect together. So what we're trying to build is a tool that can help link these different aspects together to build a more connected ecosystem.

Roopinder 8:24

You're talking about connections that a person would have with all these different tools, but does what you're saying in principle also apply to different individuals?

Mai 8:33

If you think about Slack, it's not like every person has their own individual Slack, it's that you have a connected workspace of Slack. You're thinking about JIRA, it's not everyone has their own JIRA, but rather it's a connected database of tickets that we're all working off of together. So when you're thinking of quarter 20, you're similarly thinking of this connected database of documents that everyone can reference and learn from.

Roopinder 8:53

Quarter 20 just makes me think of quarter 20 knots and bolts, screws, right? Is that what the name came from or am I missing something?

Replacing slides and docs with live data

Mai 9:00

You 100% nail that. My co-founder Addy and I, what really instigated us to want to start Quarter 20, sort of the why now moment, is I had come from a background in hardware, had spent years in SOLIDWORKS cursing that it was crashing, years building up PowerPoint decks, et cetera. And my co-founder Addy had spent most of her career launching sort of on the product side for hardware products and AirBR products. And when we were in business school, we met at UCLA. When we were in business school, it was COVID. So we were just sitting around thinking about kind of like how is the world gonna change, and especially how is the world of hardware gonna change as a result of COVID and having more streamlined tools to connect teams. And something that we just saw again and again in the news was oh, there was this one recall because of a missing torque value. There was this one recall because there was an improperly spec uh loctite that caused screws to back out. It was ironic that a Boeing vehicle to fail or a Rivian vehicle to fail is one teeny tiny screw. So kind of in jest, we named our company after the lily screw. So we named it quarter 20.

Roopinder 10:04

I was wondering why you didn't go metric.

Mai 10:05

Yeah, M6 has much less of a fun ring to it.

Roopinder 10:08

Thank you for that. Now, you mentioned wiki at one point. This is very uh crucial to what you're creating, the whole idea of wiki like a Wikipedia. Could you tell me how specifically this wiki technology or concept relates to quarter 20? What how it's used?

Mai 10:23

Yeah. Think about what is the core of Wikipedia. The core of Wikipedia is the ability to create multiple pages of documents, essentially, but they're all sorted one place, which means that they're infinitely interchangeable and referenceable within each other. And I thought you brought up a really good point about what is the focus of AI in quarter 20. That's where AI can really come into place. There's no one place where you can just say, hey, tell me all of the specs that we used for the last vehicle that we released, what are all the test plans that we released? It's stored across 20 different documents and it's all internal to your system. So what we're building at quarter 20 is a way to make that information modular and referenceable to really build up this knowledge repository of all forms of documentation within quarter 20. What really makes us powerful is being connected to data sources. We're starting with CAD as our primary data source and using that to drive the connectivity of information is what's really important to us.

Roopinder 11:19

So much like a wiki, anybody can contribute to it. Could you also install administration to it so there is some level of control at the top?

Mai 11:27

Yeah, that's ultimately where we're going. It's like being that confluence replacement, that wiki replacement for Teams, but built for hardware, where we're starting is very small and just managing one fleet of documents, of work instructions, but already we're seeing a growing number of customers using us a field service guide, installation guides, or troubleshooting manuals, things of that sort.

Roopinder 11:48

You have customers.

Mai 11:49

Yeah.

Roopinder 11:50

Pretty good for startup.

Linking the hardware stack like software

Mai 11:52

It's really exciting right now to be in our position because we're seeing the forefront of innovation for hardware teams and hardware companies. We have a number of companies building some of the coolest technology you can imagine. We have a customer building an automated tomato picker. We have a customer building a robotic arm. We have a customer building an automated lawn mower. We're working with a medical device company. These folks are really, really pushing the boundary of what it takes to be building hardware. And they're all startups, which is really cool. The barrier to entry for startups to build products has dramatically decreased in the last 10 years. And there are more and more hardware companies that are getting off the ground. But what's really slowing them down is all the administrative work that doesn't go away just because they're a small company. And we can really lower the barrier for these teams to get into production and get their products out into the market. It's just been so exciting to be a part of the innovation going on in the hardware.

Roopinder 12:49

So this tomato picker and the other companies, they're paying customers. You actually have paying customers. So you're not just moving off investor money anymore.

Mai 12:57

No, and that's ultimately the goal, right? The goal is to drive change for hardware and hardware teams. And for us, it's very much the goal to make sure that we are solving the needs of our customers. We are really excited. We're primarily focused on industrial robotics right now as our primary customer base. A lot of the folks that I talked about are in that space.

Roopinder 13:16

And agricultural, I guess.

Mai 13:17

Agricultural robotics, yeah. It's like kind of a broad category, if you will. It's kind of like if you're building robots, it kind of flops into that category. We have a growing number of folks reaching out to us in aerospace, defense, medical device companies, automotive. We're excited about being able to serve this growing need. What separates a tomato picker company from an electric airplane company is not that much when it comes to how they design, how they communicate amongst teams. We can build this agnostic tool to best serve the hardware landscape.

Roopinder 13:46

How old is the startup?

Mai 13:47

We're just under two years old. We just launched our product at the beginning of this year in February. So we're a little under seven months in the market, and it's been really exciting seeing the company grow, our customers grow. And it's also been really exciting to see them all move from early design phases into production, into building their second product, etc.

Roopinder 14:07

You started this with your partner, Addie First, correct?

Mai 14:10

Yes.

Roopinder 14:10

And you're by yourself now. You must be incredibly busy. Aren't you isn't she out of commission for a bit?

Mai 14:15

She's on leave right now, but she is still part of the team. We have a great team as well. We have Mark, our head of engineering, who's really spearheading the engineering effort. We have two great front-end engineers, Paul and Annie, who are super invaluable in order to help us really crack this really complicated landscape of not only data, but also CAD. We're dealing with customers and their products that are big. People are putting their entire machines into quarter 20, and we're able to render that, we're able to be performant, build documentation off of that, etc. So it's been really cool seeing our engineering team step up to the challenge and build this robust product for these industrial scenarios.

Roopinder 14:55

We're definitely solving a need, that's for sure. I'm glad to hear they've already got customers. It's unusual. How are you getting the word out besides talking to people like me here?

Mai 15:04

We really enjoy going to conferences, especially conferences that really focus on hardware and innovation that's happening in hardware. Some of the conferences that we've been to in the past year or so has been the Boston Robotics Summit. Highly recommend for folks to go to the Boston Robotics Summit. There are a number of fabulous companies that attend that conference and building really cool things. We also enjoy going to Automate in the Midwest. Conferences have been a really great way to meet customers and folks. Honestly, LinkedIn is another really great place to meet folks. There's a number of growing people on LinkedIn that hardware gurus, hardware experts that are building a presence on LinkedIn. It's really fun to be tapped into that community. So really, there's a lot of very cool information that's getting disseminated across LinkedIn when it comes to hardware and what it takes to build hardware. And highly recommend folks be tapped into that now.

Roopinder 15:54

Sounds like smart marketing. Most technical companies, especially in the early stages, are the mentality that you build a better mousetrap and the world will beat a path to the door. That's what they think. Especially true of companies that are not in the US. They think, oh, we've got a great product. We don't need marketing.

Why “Quarter 20” and the tiny screw

Mai 16:10

I look, I'm an engineer and I've worked at a number of startups in which engineers have the exact same mentality, which is all we need to do is build a great product and then everyone will use it. And that works approximately zero percent of the time. The best companies that I've ever worked at, the ones that are the most successful, always have a great sales engine, have a great marketing engine. And ultimately, it's really important because that is what helps people understand what their problems are. As I said, this system that we're fixing, it's functional. It's not great, but it works. You can still get products out there into the market. You're just much less efficient about it. And so if you're not aware that this is a major problem, as everyone is trying to cost down more effectively, more efficiently get into market with the capital that they do have, it's really important for them to take a good look at where are the inefficiencies in their process and how can you help improve that. And so, really, what we're providing is a tool that enables teams to be able to see where these inefficiencies lie because they don't realize I have an engineer that's building work instructions and he's spending about half of his time doing that. How much are you paying that engineer? How much more could they be doing with their time if they weren't doing that?

Roopinder 17:17

In a nice way, tell them they are being boiled. Then they realize, oh, we do have a problem. Now I'm always reminded of the most successful companies. After their initial success, marketing made them really successful. Autodesk, for example, it's a great company. In the beginning, nobody had PC-based CAD. I wouldn't say it's a technically a great product. It was adequate, but great timing. They had initial success. Didn't get to be a billion-dollar company though, until Carol Barts came in with sales and marketing. So and SOLIDWORKS, again, great initial success. I mean, they filled a great need. They were price differentiated with Pro E, right? So that gave them a lot of success. But it was again, it was marketing that put them. John McEleney, I'll credit him. He was their CMO before he became CEO. And he just used marketing. He would hammer people at trade shows. He had a name for it. Mainstream. Before SolidWorks, nobody knew what mainstream CAD was. And he hammered people, including me, on what mainstream was until, hey, I finally got it. We are boiling. The temperature is rising. This mainstream needs to happen, right? Anyway, I need to see your product. Can you do a little demo for us?

Governance and wiki model for teams

Mai 18:22

I'll show you what we're building. What we have at quarter 20 is a way to create CAD-based documentation really easily. And not only is it really important to have a product that works, it's important to have a product that is just easy to understand, right? If we're thinking about communication, the best communication happens if it's obvious what you're trying to interpret. That's why IKEA instructions work. It's unambiguous what you are looking at. If you look at work instructions that go from design teams to manufacturing teams, most of the time they're ambiguous because it's engineers that are putting them together. And so really what we want to build at quarter 20 is the ability to build out documentation that is beautiful, documentation that can maintain itself and update itself, and really just build this easy platform for folks to be able to build up their documentation and execute off of their documentation. But what's really powerful about our system is just how connected it is. For example, if I wanted to go in, reorder some parts, all I have to do is go in, say that this part was assembled first and now this part is assembled. If I wanted to rearrange the order of parts and how they're assembled, all I have to do is click and drag and then these images will update to reflect that latest version of CAD. So you can see that these images are updating here, and similarly in the document, the images are updating here. And so really what we've created has been this really simple tool for folks to be able to update, maintain their documentation. It's all connected to CAD. You can see that you can update CAD here. We also have plugins available for Onshape and SolidWorks, and we have automations that we can build for Creo and NX as well. We can really minimize the barrier that it takes for you to push CAD into Quarter20, build documentation off of CAD, and have it be a seamless way for you to interact with it. This is just a really high-level demo. Kind of just the two functionalities that I wanted to call out is our ability to go in and tag in parts. So this is really where the Wikipedia functionality comes in. You can see that I have this part here. You can see that that maps to a part that's in there. You can see that as I click on this part, it's tagged. I can link to it and we're building up more functionality to search for documents that reference this part and really build up this knowledge repository for you and for teams. So what I'll do is show you how the product works. I've created a new operation step. If you go to the document page, you'll see that this page is empty for now. When I go back to my CAD view, all I have to do is add in the parts that I want to assemble into that step. Our product is we make it really easy to manage your manufacturing bomb in addition to your engineering bomb. So previously there had been two green dots associated with those parts. Now that I've added in those parts, you can see that all information has automatically been filled in for me. The image has been filled in of the parts that are needed for this. A parts table has been generated with the parts needed, the quantity, the description, the revision. This is all seamlessly following the same template that you would need for the rest of the assembly. We created a seamless process for teams to create and maintain their documentation.

Roopinder 21:22

Is everything that you're showing me cloud-based?

Mai 21:25

Yes, everything I'm showing you is cloud-based, which has been really fun for some people to discover. One of our customers, I was talking to her and she was like, Oh yeah, there was this one thing that I was seeing in terms of when I was typing because I was using the command key. I said, That's interesting because I mean you're using a Mac. She said, Yeah, I was using a Mac. It's like, how are you using a Mac for work? You use SOLIDWORKS because you're a mechanical engineer. She's like, No, what I love about quarter 20 is before I left for the day, I just pushed my CAD file into quarter 20. And then I went home and I was able to pull up my account on my personal computer and continue working from home without having to log my CAD laptop. What's been really great has been providing a cloud-based tool for folks to create their documentation. They don't have to bring their CAD laptops home to build work instructions. They can seamlessly build it alongside a technician on the shop floor or not home.

Roopinder 22:13

This is possible because you can seamlessly read SOLIDWORKS files.

Mai 22:17

We you push your SOLIDWORKS file onto it. We read through the entire structure and the assembly, and then you can build your documentation off of that.

Roopinder 22:24

I see. So for a while there you have parallel duplicates.

Early customers and robotics focus

Mai 22:27

So what we do is it's basically a push from SOLIDWORKS into Quarter20. So it's almost that save point in time. We do have automations that you can set up in order for you to say, hey, every evening when I sort of log off for the day, I can run an automation from SOLIDWORKS for you to export into Quarter20. And so there's lots of things that you can do on the on the side that if you would like what's exciting to tap into these workflows that people didn't know could exist and build up fun animations.

Roopinder 22:52

An unintended benefit. You did not design it that way, right? But people are using it that way.

Mai 22:57

What's been really interesting has been the number of different ways that people are using the product. Different teams are using the product than we anticipated. People are using us for different functionality. Some people are using us for design reviews, even though we didn't intend for us to be used for design reviews. We're working with field service teams, even though we never intended for this to be a field service document tool to start. So it's been really exciting just to see the amount of ingenuity that we've unlocked. And really the focus for what unlocks these different people has been wanting to build a CAD-connected document. It's just so painful for people to go around chasing the mechanical engineers to have access to CAD, to take screenshots of CAD. Now all they have to do is push CAD to Quarter20, and everyone can build their documents off of that CAD file. And it's been a really powerful tool to connect teams together.

Roopinder 23:44

Are there limits like file size that you could display?

Mai 23:47

Honestly, this is what I'm most proud about for the team. As I mentioned, we have a great engineer named ENI, and he's done a phenomenal job of being able to take in any CAD file and be able to render it. So we've we're really pushing AWS to its limits, but any and work have done a phenomenal job of being able to take in really large CAD files and render them seamlessly on quarter 20. So what we say is if it can work in Onshape, it can work in Quarter20. We're really proud of the team for being able to handle that because it's not an easy problem. But if you look at some of these files, they're 500 megabyte files, 700 megabyte files. People are building really complex products. It's been really cool how awesome the team has been in being able to tackle this really hard problem of being able to render in really complex CAD and have it still be performant.

Roopinder 24:33

Now you said CAD, not so it's more than just SOLIDWORKS. You could handle it. Files, Solid Edge, those things. What can't you handle?

Mai 24:41

So we strictly work with 3D files. So anything that is a 3D file, we don't work with drawings, we don't work with sort of other forms of files. But you know, if you use NX, Creo, SolidWorks, OnShape, CATIA, we work with those. Most of our customers use SolidWorks, which is why we built our first integration with SolidWorks. We're seeing a growing number of people using Onshape, which is why we're starting to build up more capabilities with our plugin. Those two are the biggest ones. Creo still has a chokehold on the East Coast, in my opinion. So a lot of our customers on the East Coast still use Creo. We're not seeing quite as much Creo on the West Coast here, but definitely on the East Coast.

Roopinder 25:18

Interesting that you say you're seeing more Onshape users. I was shape because it's cloud-based and has built-in collaborative properties, can do a lot of the thought of show and tell, right, from itself.

Go‑to‑market: conferences and LinkedIn

Mai 25:28

Yeah, so on-Shape is really great for being able to collaborate on the design itself, but ultimately designs don't just live with mechanical engineers. And that's really the power that we've unlocked with Quarter 20. It's a platform that is used to communicate. Documentation is a tool to communicate across teams, internal and external stakeholders and vendors. What we've seen to be really powerful is people using Quarter 20 to say, or using Onshape to build up their CAD, build up their 2D drawings, but they still need to use Quarter 20 in order to build up their work instructions, any design review decks they want to build up, any field service guides they want to build up, etc. The last thing I'll show is what people really care about being able to not just create documentation, but also being a place where you can execute off the documentation. And that's something that's really important to our users. And so we have this mode called technician mode where you can go in and you can operate off of any documents. All you need to do is put in your name and we provide analytics for you and for your team. So we track how long each user is spending on each of these operation steps. We track any metrics that they want to track if they needed to check anything, if they needed to put in any forms. We have all folks to do that. Also, they can leave comments, which is really powerful. What's really exciting has been we're giving more folks a voice when it comes to the manufacturing team, when it comes to the design team. I can go in, I can tag that Addy. We need to check the heart stock of this part. And again, the same tagging that I had talked about works in the comments as well. I can tag in the same parts, I can tag in the same tools as a result of being able to do that. Now we're building up even more of that repository of what are the comments that are associated with a certain part, in addition to what are the different pages that are associated with it. So it's been really exciting to see how people have taken off with quarter 20 as a tool, not just for creating documentation, but also being able to execute all the documentation. This has been valuable for folks to give a voice to their technicians and build more assemblable parts as a result of the code.

Roopinder 27:29

So is that all of it?

Mai 27:30

That's all I'm going to show.

Roopinder 27:31

Cool, very cool. I'm glad I saw it. I'm also amazed by how versatile it is and how user-friendly it is. How expensive is it? What's your business model?

Mai 27:41

Yeah, so right now we do team-based licenses and the pricing varies based on the size of the team. The standard package that we offer is centered around five editors and ten technicians. That varies between 10 to 15k per year, depending on the usage. We're happy to flex up or down for the number of users. And if there are any folks that reach out as a result of this podcast, let me know. You can mention a repinder and I'll give you a discount because I'm excited to promote more conversations for innovation and design. We're excited to chat.

Roopinder 28:14

I'd be happy to leave that in. That's great. I think this needs to get out. More people need to see it. You can only do so many demos yourself. You need to magnify this to a bigger audience. It'll certainly help in my own little way to do that. I appreciate that. Thanks so much for spending your time with me. I thank you for being a guest on our show. Keep up the good work. Very important thing you're doing. And I'm glad to see something happening. It'll actually put computer aided in into design.

Mai 28:41

Thanks so much for having me. It's been really fun.

Roopinder 28:43

All right. Thank you.