0:01 Someone is going to get really rich doing this. You might have noticed how
0:05 social media got filled with these cool Nad workflows that use AI to solve all
0:10 kinds of things. I've been sharing my workflows, too, both on LinkedIn and
0:14 here on YouTube. NAN is an incredible tool and these workflows are truly really helpful. But
0:22 a lot of people, especially people who don't have technical skills, find these
0:28 very difficult and complex to use. And I guess the UI of Naden can be a bit
0:33 intimidating. A lot of people want something more simple, a simple form,
0:37 click a button, and then you get the results. And this is a massive
0:43 opportunity cuz YouTube is filled with powerful N workflows that solve real
0:49 problems for real users, often free to download, free of charge. And if you can
0:53 slide in between the workflow and the average user and offer access in a more
0:58 userfriendly way, you'll be in business. And in this video, I'm going to show you
1:02 three different ways this could be achieved. Ranging from that simple to
1:06 more challenging, but with bigger potential. Let's go. If you're new to
1:12 this channel, welcome here. I'm Simon Hornberg and I run a SAS portfolio of AI
1:16 tools to help you grow your personal brand, handle incoming emails, and
1:20 support, track link engagement, and much more. We are a fully bootstrapped small
1:25 team of just four people, myself included. And the reason we can stay
1:30 this lean is because we know how to use AI and automation to handle most of our
1:34 operations. If you're not familiar with NADN, it's a popular AI and automation
1:40 tool similar to Sapier and Make, but much more powerful. And I use this tool
1:45 heavily to run my startup. The first and easiest approach is to build a super
1:50 simple and streamlined UI on top of a really good but complex NAN workflow.
1:56 Here's how it works. Scroll YouTube for NAN workflows. Try to find one that
2:00 looks really valuable, but also one that looks a bit complex and where you notice
2:04 many people in the comments struggle to make it work. Then simply download the
2:10 workflow and get it running on your own The best and most scalable option here
2:18 is if you have it self-hosted, so you can have unlimited workflow runs. Now,
2:23 NAND allows you to start any workflow using an incoming web hook, which
2:29 essentially is just an API endpoint. So, you now go and build a simple UI on top
2:34 of this where users can input only the most crucial things the workflow needs
2:38 to get started. Some workflows may need a user to log in with Google. Some may need that they
2:45 upload certain files. But that's it. You stripped away all the
2:50 complexity and now offer a very simple but very powerful little tool for one
2:55 specific job. And here's how you could monetize this. If your NAN workflow uses
3:00 something like Open AI, then you obviously need to pay for the tokens
3:04 through your own account. Asking users to bring their own API key is again
3:08 complex for some users, but it also gives you the opportunity to charge
3:12 users for the AI credits that's being used and of course add a small margin on
3:17 top. Of course, you could also offer monthly plans to accommodate a certain
3:21 number of workflow runs per month. Once you find a good workflow, understand it
3:25 and make it work for yourself. You can use tool like Lovable to describe the
3:30 use case and quickly create the perfect user-friendly UI to put on top.
3:35 Now, the second approach is a bit more ambitious, but here we start thinking
3:40 bigger. Instead of a single use case, you create a collection, go on a spree,
3:45 and collect super valuable innate workflows while creating really simple
3:50 user-friendly UIs on top of them. You can start with two or three, but keep
3:55 iterating. Use YouTube as your source of inspiration and keep adding new
3:59 workflows to your collection. Call it easyN or something like that. And then
4:04 ensure that users need to create just a single account to use any app in your
4:08 collection. And now you can sell subscription plans that covers all apps
4:13 under your ECN umbrella. And just like before, you could also here offer AI
4:17 credits and add a margin to make a profit. There's a tool called Run Comfy,
4:21 and they're doing something very similar. They took an existing
4:26 open-source tool, Comfy UI, and now they're collecting workflows and provide
4:30 one-click run in the cloud with a super simple UI on top. These complex comfy UI workflows still
4:37 run in the background, but the user will see a simplified interface to do a
4:42 single specific job. I think this is super clever. You could build a small
4:46 library of reusable UI components for all your workflow forms. Give Lovable
4:51 access to your repository and simply use Lovable to repeat the process of
4:55 creating simple userfriendly UIs on top of your workflows. Finally, the last
5:00 approach is the hardest, but also the one with the biggest potential. With
5:04 this approach, you zoom out a bit and ask yourself, what exactly is the
5:08 problem this workflow is solving? What does users achieve by using it? How is
5:13 their businesses or lives better by using this exact workflow? Find a
5:18 popular, super comprehensive, and complex workflow and turn the core of
5:24 that problem into a fullyfledged SAS. Now the scope of this SAS might span
5:28 much more than what the workflow is offering and you might keep growing the
5:32 product in the direction of your users's feedback but using the idea behind that
5:37 one NN workflow as a starting point. You could still use lovable to create a SAS
5:41 starter but for a tool like this I would move more into custom code maybe
5:46 assisted by tools like cursor or client and a custom backend and infrastructure
5:51 on AWS. Use the workflow only as an entry point to kick things off, but
5:55 replace the steps in the workflow with custom API endpoints you control
6:00 yourself. Now you have the UI on top. You replaced Naden with your own backend
6:04 and now you have a fullyfledged SAS product ready to serve. If you follow
6:09 any of these three steps, you will have a SAS by the end of the year, at least
6:15 in some form. And who knows, by building one SAS this way, you'll quickly get a
6:19 better understanding of how to build and run a SAS in general, and it might spark
6:24 some serious inspiration to do more. I think NAN workflows are a great source
6:29 of inspiration. They are easy to access, mostly free, and fundamentally they
6:34 solve a problem. Now, if you want more inspiration like this, take a look at
6:38 these five real AI agent business ideas you can build in 2025. I will see you
