How to Build a Software Business With AI | Blink.new

Jon Law
434 followers
390 Video Views·Aug 11, 2026
Comment "blink"
https://blink.new/?via=jonlaw
-------------------
Clips channel @jonlawclips
I do NOT sell any products of my own. Watch out for scams.
Queries: [email protected]
____________
AI Generated·May contain errors
So everything that you are seeing on the screen right now, that's a live booking website,
an actual iPhone app, a Chrome extension, and an AI agent that runs customer follow-ups around
the clock, was all built by one person with one AI tool in a few hours, and that's with no code,
no developers, and no stitching different tools together. And together, those four things make up
a complete software business. You have a product, a mobile version of it, a tool to find the
customers, and an AI employee. So in this video, we're going to build all of that by scratch,
step by step, so you can do the exact same thing for your own idea. It's going to be a fun one,
let's go. So the problem currently with building all four of those things is there is usually a
lot of different tool chains involved. So a lot of the popular vibe coding tools can get you a
awesome looking web app, but then if you want that as a mobile app that can get pushed automatically,
that may be a different tool. And then same thing with Chrome extensions and a full AI agent
functionality. So that is the gap that Blink.nu is going after and how we're going to build this
system in this video. They're one of my favorite platforms, they are the sponsor of today's video.
So I'll give you my honest take on it after we go through the demos. I love these guys personally,
but I want you to form your own opinion based on what you see in the video. And the whole point of
Blink.nu is that they're a full stack AI builder. So we're talking full stack from AI agents and
employees through web apps, Chrome extensions, mobile apps, the full stack that we just talked
about. And so you can support the channel and follow along. So build something yourself while
you're watching the process unfold in this video by going to Blink.nu, this link on the screen
or in the description. And if you want that link sent to you, just comment BLINK in the comment
section of this video. So that in mind, what's the actual business we're going to try to build
in this video? So here's the idea. We're going to make booking software for independent fitness
studios. So you're talking small gyms, yoga studios, Pilates studios. A lot of those guys
are either running manually through something like Instagram DMs or they're using legacy software like
MindBody. So we're going to make a clean booking and membership platform. We'll price it at $99
a month. And so we'll make the web platform, the mobile app that members can actually book from,
a Chrome extension to find the studios that need this. And then finally an AI agent to run it all
day to day. So that's the plan. We just got to build and let's jump into my computer to do that.
So here we are inside the Blink platform. We're under app right here, which lets us build. All
of those things we've talked about are app as in web app, mobile app, website, Chrome extension.
I don't want to spoil what's coming up. You can see the little agent pad right here. We'll look
at that in a few minutes, but for now let's just kick off this idea and project with the following
prompt. So build a SAS booking platform for fitness studios. We're describing the features we want
and then include a dashboard as well. So pretty ambitious build. We can go ahead and select the
model we want right here. Let's go to Blink 1.7 Pro and then let's let it go. Now, a few notes
while it's going ahead and building this. Number one, security is on by default. So your data is
protected. There's no kind of custom prompting for the agent. You have to keep in mind there.
Number two, something I appreciate personally about Blink is they are very infrastructure,
kind of backend focused. So you'll see once we go ahead and publish this, the auto-scaling,
the CDN, the deployment side of things is all set up. We can click on backend. For example,
all the backend, the hosting, that is really solid and intuitive as far as the build goes.
Looks like the agent is getting started over here as well. And so we can take a look more
on that backend side as it finishes the app and we want to deploy. And then the third thing to
keep in mind is OAuth is completely no code. It's done for you. You don't have to go grab a bunch of
API keys from Google and for Gmail login and so on. All of that is done behind the scenes by default,
meaning users can by default, again, sign into Gmail or sign into your app through Gmail,
through social media accounts and so on. Very nice touch there. The same ease of use there applies
to Stripe. You can see if we press connect Stripe, that is what allows us to very easily accept
payments for whatever it is that we are building. Same with Superbase for our databases and GitHub
for just storing that code. If you want to own your own project per se. We can see the agents
have started to create the various databases here. And now if we jump into the dashboard,
I just mentioned Auth, we can jump into Auth. Google is already on, meaning people can sign
in with Google and now they can sign in with GitHub. Now they can sign in with Apple. Now
they can sign in with Microsoft. It is that easy to turn all of that on. A cool feature these guys
have, I don't really see this too often, it's kind of an AI search audit. So once the web is up,
it'll score it across how AI will interpret the site to see how well it'll rank. So kind of
interesting there and what I always recommend, if you deploy anything that you want to commercialize
or even use internally, get that custom domain. It's a dollar, maybe 10 or 20 bucks. It makes it
look and rank much better. Little shout out here as well to the AI features. What you can do is
very easily with no code, no API keys, work AI features into the app. So the users of the app
itself can engage with chatbots or whatever models you want inside the platform and the API,
the cost payment, et cetera side of things. It's all managed by link. Okay, here we go. We can see
the visual preview for our web app. Really nice UI UX. I like it and let's go ahead and click
get started. This is what that dashboard looks like. OAuth will be in the deployed version.
So we get a summary of our revenue, our attendance, today's schedule. This all looks really
good. I really like the UI UX. Let's click add class and that added a class which we can edit.
Looks good. Let's hop into schedule. Same deal there. If we click and then members will show us
all of our members and then finally insights. So this looks good. What we would want to do
to actually deploy this or kind of get it ready is say, Hey, wipe all of the data, right? This
is placeholder data. So you just remove all of that and then make sure that there's a member
class and there's a owner class. Let's do that now. Make sure there's a member and owner class
that are different or users and wipe the placeholder data. So everything looks good.
We just want to make sure it's ready to actually deploy. Let's give it that. Now we're going to
use the mobile app actual development cycle to develop our mobile app. But if we press right
here, we can see what this website or web app looks like on mobile as well. So it is responsive.
That all looks good and it's fully finished. All of those updates owners can own members can
browse classes and book. Let's go ahead and publish this and we'll give it a final demo.
So I'll click publish. I have this production URL and then I'm going to click deploy now. So it's
going to take care of all the hosting deployment side of things for you. You just pick deploy and
then you are good to go. You can add that custom URL if you want as well, but this is going to
scale up to 50,000 users a month with that global CDN. And then if you use more credits, it'll work
with more users and let's go ahead and give this a final demo. So looking really nice, actually. I'm
quite the fan of the UI UX. If I was going in and doing a pass, I would change the logo,
but otherwise this is looking good. Let's go ahead and click get started. Now here we can see you can
like we turned on with the magic OAuth buttons, sign in with Gmail. I'll use an account here,
sign in works and then here we go. We're inside the platform. It's going to ask us if I own a
studio. Okay. And here we go. Let's create our studio. Dashboard looks good. I'll just call it
my studio in Austin, Texas, but create. And here we go. So we can see the same dashboard. We looked
at all of the analytics. We can add a class. Let's test that. I'll click add and create. I can say
my Pilates class. I'm instructing 17 people and I'll go August 4th and publish. And then now people
on the app who are searching can go and sign up. There we go. Everything there looks good and we
can accept payments and create membership plans in the app. And this is all one prompt, right?
This is all V1. This looks awesome. I think we are good to go. Now, if you're doing this for real,
spend more time on it, go really in depth, but for one prompt and a V1, this looks awesome for
build one of our four. Now, before we wrap up, I would like to do another UI pass of this. So just
ask it to make the UI look not like coded, like AI, make it look sleek and highly functional,
usable. Think hard about how to make this happen. So I'm going to give it that. We're just going to
do ancient things and improve the UI. Okay. I really like this UI. That was a good pass with
the color, but yeah, it looks professional. It looks good and we're good to go. Okay. Now we're
going to go ahead and build that mobile app. So same concept, but this is where a lot of the
functionality of a lot of web coding tools die because that's going to be swift for the Apple
app store, different language, harder to do for sure. So let's give it that same prompt and we'll
see what we can do here. We're going to keep it on pro mode and let's click start building. Okay.
Here we go. We can see our mobile app is done. Now what we would also want to do if we're doing
this properly for a real business is take our web app, download the style of it, and then feed that
as context to this agent. So it's the same visual style and, or we'd want to just actually sync the
databases, right? So you have a consistent backend there, but let's see what this looks like.
This is a responsive demo. I can click show me around and then view membership plans. This
actually looks really good, really solid UI. I can click on monthly, for example. We can also, you can
see, actually connect our device to test. We can also actually test this on our phones, which is cool.
But if we jump back here, let's click continue to sign in. That all looks good as well. Let's just
check the interior of the app. And now here we can see the interface. This actually looks really
good to me. We have our little streak up here, schedule with all the different classes that would
be created on the studio owner side of things. And we can see our progress. Also for, you know,
one prompt, one shot, this looks awesome. And it is actually deployable. And if we click book,
then it says books and we get notifications in the app store, but that all looks awesome. I'm happy
with that. Let's just say, remove the demo login, and then we're going to jump into the dashboard
right here. Let's go to authentication and let's turn on GitHub, Apple, and Microsoft. You can
create an account easily. I also want to change the name. Let's also change the name just to
Fit Studio. Okay. It removed the demo. So accounts are functional. We can go ahead and publish this.
I'll click publish. And then here we can see the app store and the Google play store as our
publication options. We can also access it on the web if we want to. Let's click publish. So we can
just access it. And then the process for the app stores is integrated into Blink as far as the
application goes. So all the code is there. You just need to connect your Apple and your Google
play accounts, fill out or answer a few questions about the metadata and the use of the app. And
then it'll go ahead and be published on the official app and Google play stores. After you
finished that review process, Apple is a little more for sure stringent than Google. So again,
this has been published on the web, the code, everything is perfect and ready to go for app
app store on Google play store. Just press on those buttons when you want to do that for yours.
And just like on the last one, let's do another UI pass. I'll take the same prompt I used for the
website and we'll give it to this one to just overall improve the UI and we'll see what it
comes up with. Okay. This looks good. It's clean. I like the interface. We will consider that. Okay.
So there we go. We've done our web app and our mobile app to complete that little trifecta.
We're going to head over to Chrome extension and give it this prompt. So build a Chrome extension
that works on Google maps. Whereas when I'm browsing fitness studios, it will read the
listings and flag anyone that doesn't have a booking link. So this is for us as a tool,
as a customer engine or customer discovery engine. So we can go find those leads, give them a call
and sell the mobile app and the web app that we just built. So let's click start. Okay. Our
Chrome extension is done as opposed to playing around with this. Let's just go ahead and download
it and test it for real. And Google, I'll click load unpacked. So I'm going to take this file. I'm
going to drop it in here, but then now we can see our Chrome extension. And if we look at the top of
the browser page here, let's turn this on. And there we go. We can see studio lead Hunter
successfully loaded in the browser. And now we'll do our little demo. Let's say yoga studio. Let's
open that extension and then click scan map. There we go. That is one shot. It works perfectly
on number one. We can see no booking link found under this link. It interacts with the webpage
successfully and we can see our results right here. So these would all be leads for us to call
the Chrome extensions are a little bit different in that there's less of an kind of active backend
to manage depending on the setup, at least for this build, we don't really need any kind of
database backend work that is, unless we want to store those lists of leads and then kind of export
them, store them in the cloud, et cetera. Okay. And as usual, let's do our UI UX pass. So same
prompt we've used for the past two and we'll let it improve the UI of the extension. Okay. UI is
improved. It looks good. That's our final UI UX pass done. Now we've jumped back to three minutes.
There you go. That is our build three of four. And now we get to my favorite part of this. That'll
be the AI. So here we go. We're three builds through the four for our business. Now we get
to jump into that fun agent, excuse me, agent tab right here. And this is called the blink claw.
Many of you are familiar with open claw was the first kind of agent that works 24 seven
completes work on your behalf. So let's do it. Let's set up an agent to help us. What we're
going to do is create an AI or an agent that monitors the studio booking inbox, and then we'll
send emails automatically to members that are customized to follow-ups basically manage or do
what a sales rep or someone internal to manage bookings would do at my business. And then it can
send me a message on telegram every morning with a summary. So let's go ahead and click deploy
studio booker pro. I like that. We can set our avatar. This looks good to me. We'll click deploy.
Okay. It's setting up the agent. And so this is going to take a lot of what you have to do
manually with the open plot style infrastructure and just let it be done for you in a very nice
UI UX in one click. So it's a lot of the features you may have heard about it be familiar with,
but just wrapped in a very nice exterior that lets you just get more use out of it,
especially with less of a technical background. And here we go. We can see under my agents,
the agent is being created. And so we can do all of the things we want it to do.
I'll go ahead and send it a task and we can see what that looks like to do is connect the apps
that are needed under connectors for it to do it. So things like connect to my Gmail to receive
those notifications. And then let's say maybe store the data in HubSpot. You just click connect
the one click connection, super easy. And then it will be able to message us on one of these
platforms that we set up. So your AI can run 24 seven via those connectors, and then just shoot
you a text on telegram on WhatsApp with updates that you request. So that's it for the agent
set up. It is that easy to do. We can go ahead and see it's starting to give us instructions here.
So breaking down a request into tasks and then into the connectors that we'll need and basically
talk you through how to do the setup that you will need to do. So the rest is on you. You have
the blueprint at this point. We've seen all four builds. We've successfully orchestrated them.
And your imagination is your limit to go in, use this infrastructure, use the fact that you can
deploy agents that run autonomously, use the fact that you can build mobile apps, web apps,
Chrome extensions, and go out there, get out in the world with your idea and make something happen.
So there you go. That's the build. And as far as limitations go with a system and approach like
this, I think number one, you still have to steer. It's not a hundred percent done by the AI. So you
do have to guide the conversation to get those details right. Now you are iterating really fast,
but you still have to iterate yourself fast as opposed to that being fully automated. Hopefully
that does change in the future. Number two, publishing is hyper guided in a system like
this, but with the review process still takes time, right? Apple still has to spend a few days
looking at the submission before it goes live. So that is some friction built into that whole
process. And then number three, I just say trust agents gradually. A lot of this is already known.
So I'd let, for example, a claw agent just work internally and let you review its work for a few
days or a few weeks before you let it, the actual customer facing with no controls over that
relationship. And then finally, this is not free. You will need to use real credits. Is it a lot
cheaper than developers or what it used to be? Absolutely. But it's not going to be a cost of
zero. That's for sure. So there we go. To recap, we built that full stack successfully. We got the
Chrome extension, the mobile app, the web platform, and then the AI agent. So if you have an
idea, this is a blueprint that you can follow to go get it out of your brain into the real world
across the dimensions where it matters. And I truly hope that you find it useful in that regard.
And you go and build yourself that in mind. Appreciate you being here and I will see you in
the next one. Cheers.
