Big Idea

The argument in one line.

The fastest builders with AI don't build more, they point Claude at the right problem by answering five questions about context, MVP, exclusions, hot zones and bottlenecks, then re-asking them on a schedule.

Who This Is For

Read if. Skip if.

READ IF YOU ARE…

A solo founder or operator building products with Claude Code who keeps starting new tools and finishing few of them.
Someone with a business metric to move (conversion rate, revenue, time saved) who isn't sure which task to hand Claude first.
A builder who wants a simple way to decide when to use an existing tool instead of vibe-coding their own.
A consultant or freelancer shipping Claude skills for clients who needs a lightweight way to test that changes don't make output worse.

SKIP IF…

You want a technical walkthrough of Claude Code features or code; this is a planning and prioritization framework.
You need a rigorous eval framework; the eval section is an introduction and the creator says a full video is still to come.
You're allergic to sponsor-adjacent content; the examples lean heavily on Whop's CLI and affiliate link.

TL;DR

The full version, fast.

Building is so easy with AI that everything feels worth building, so the winning skill is choosing the right problem. Austin Marchese relays five questions from Whop engineer Ryan Ouyang: what are your context and desired outcome, what is the most important thing to build, what are you not building, what are your hot zones, and what are your bottlenecks. Each has a Claude prompt. Find your unique ability, cut scope to one real result, lean on existing tools, add a minimum viable eval for critical areas, and re-ask the questions weekly for execution and quarterly for strategy.

Free for members

Chat with this breakdown — free.

Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.

Create a free account →

Chapters

Where the time goes.

00:00 – 00:34

01 · Cold open

Austin introduces Ryan Ouyang and the five questions the fastest builders answer.

00:34 – 03:59

02 · Question 1: Context and desired outcome

Give Claude your situation, then turn a vague goal into one number and one deadline, stated one level up.

03:59 – 09:24

03 · Question 2: The most important thing to build

Find the thing only you can do, then cut to the minimum steps for one real result, with the car-wash MVP example.

09:24 – 13:38

04 · Question 3: What are you not building

Avoid the building-addiction loop, use existing tools for payments, ads and analytics, and maximize value per tool.

13:38 – 17:15

05 · Question 4: Your hot zones

Flag the parts that must be right in CLAUDE.md and build a minimum viable eval, including slow evals for non-technical work.

17:15 – 19:44

06 · Question 5: Your bottlenecks

Spot bottlenecks through what you avoid, check effort against return, and use benchmarks to know when one is solved.

19:44 – 22:36

07 · Re-asking the questions on a schedule

Answers expire, so review execution weekly and strategy monthly or quarterly.

Atomic Insights

Lines worth screenshotting.

Claude has PhD-level general knowledge but knows nothing about your situation, goals, limits, or what winning looks like for you, so context is the first thing to supply.
Where you live, your skills, and the time you can give the business all change what the right answer is, even when they seem irrelevant.
Turn a vague goal like 'more customers' into one number and one deadline before asking Claude to build anything.
State your desired outcome one level up: 'help customers use our tools with AI' guides better decisions than 'build an AI agent tool'.
The metric you want to move and the problem you actually need to solve can differ: more recurring revenue turned out to be a conversion-rate problem.
Your unique ability is the hard thing only you can do, and everything else is a candidate for automation or an existing tool.
Two ways to use your unique ability: automate what isn't it, or double down on what is.
The MVP of a car wash is a flyer, a pressure washer, soap and a wash mitt, which is the shopping list that gets one customer.
Start from the result you want, work backwards, and cut every step that isn't needed to get one real result.
The hard part of building with AI isn't knowing what to build, it's knowing what not to build.
If a tool is 80% as good as one you already use, or it doesn't save time or make money, the right reaction is 'who cares, it doesn't matter'.
Your job as the manager of Claude is to connect the pieces, not to build all of them, or you end up with a graveyard of half-used tools.
Maximize value per tool, not the number of tools; even your agent doesn't want to manage ten of them.
Hot zones are the parts of your work you must get right, so tell Claude in CLAUDE.md to flag them and wait for your approval.
A minimum viable eval is just an input you change, a script that runs a set of tests, and a report on how the input did.
Slow evals suit non-technical work: collect human feedback, fix the skill, store the approved output, then rerun all past approved cases so nothing regresses.
What you avoid doing often marks your bottleneck, since unfamiliar, uncomfortable work is where people stall.
If you're putting in far more effort than you get back, you're probably not working on the bottleneck.
Compare your metric to an industry benchmark to know whether a bottleneck is solved.
Answers to the five questions have a shelf life; what worked on day one isn't enough on day 100.
Review execution weekly or daily and strategy monthly or quarterly, so you neither stall in planning nor sprint in the wrong direction.

Takeaway

Pick the right problem before you build

WHAT TO LEARN

Speed with AI comes from choosing the one problem worth solving and ignoring the rest, then revisiting that choice on a schedule.

02Question 1: Context and desired outcome

Give Claude your real context, including location, skills and available time, then turn a vague goal into one number and one deadline stated one level up.
Check that the metric you want to move is the real problem; more revenue can turn out to be a conversion-rate issue.

03Question 2: The most important thing to build

Find what only you can do, automate or delegate the rest, and cut scope to the minimum steps for one real result.

04Question 3: What are you not building

Decide what you won't build up front, and use existing tools for payments, ads and analytics so you don't end up with a graveyard of half-used tools.
Measure value per tool instead of tool count, because neither you nor your agent wants to manage ten of them.

05Question 4: Your hot zones

Mark hot zones in CLAUDE.md so Claude flags them for approval, and build a small eval there: an input, a test runner, and a report.
For non-technical work, use slow evals: gather feedback, fix the skill, then rerun every past approved case to catch regressions.

06Question 5: Your bottlenecks

Find bottlenecks by what you avoid, check effort against return, and compare your metric with an industry benchmark.

07Re-asking the questions on a schedule

Re-ask the questions on a cadence: execution weekly or daily, strategy monthly or quarterly, so answers don't go stale.

Glossary

Terms worth knowing.

Desired outcome: A concrete goal expressed as a number and a deadline, rather than a vague wish like 'more customers'.
MVP: The smallest set of steps or product that gets you one real result, such as your first paying customer.
Unique ability: The hard thing you can do that others can't, shaped by your skills, location and available time. Austin also calls it your secret sauce.
Hot zone: A critical part of your work that has to be right, where Claude should flag changes and wait for your approval instead of running free.
Eval: Short for evaluation. A repeatable test that checks whether a change makes your output better or worse.
Minimum viable eval: The simplest useful eval: an input you change, a script that runs tests against it, and a report on the results.
Slow eval: An evaluation for non-technical work that relies on human feedback to shape the criteria, then reruns approved past cases to catch regressions.
Bottleneck: The single step limiting your results right now, so fixing it changes more than improving anything else.
CLI: Command-line interface. A tool you run from the terminal, which makes it easy for an AI agent like Claude to use a service.

The Script

Word for word.

Read-along

Don't just watch it. Burn it in.

See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.

I just interviewed Ryan Ouyang, an AI engineer at WAP, a startup worth over $5 billion, and he said something that changed how I work. We've helped millions of people use AI, and the fastest builders have all answered these five questions. So I had Ryan ask me these five questions, and it turns out if you use Claw to answer these simple questions, you will build 10 times faster.

So in this video, I'll break down the exact questions he asked me, how they change what I do, and then the exact prompts you can run to answer these questions yourself. And at the end of the video, I'll share what Ryan said is the most common.

So the first question, what's your context and what are your desired outcomes? Claude has PhD level general knowledge, but it knows nothing about your specific situation, your goals, your limitations, your restrictions, and what winning specifically looks like for you. So I asked Ryan how WAP, which is one of the fastest growing startups on the planet, answers these questions internally so that they can build faster.

You can think of WAP as a business that helps. You run your business if I give Claude the correct context about what WAP is and where I want WAP to expand It's it helps me get crystal clear on the steps. I need to like get there.

So for example we have all these different products at WAP. And we saw that more and more agents were trying to use our products.

And by giving Claude that context, it can suggest things like, oh, what it sounds like you need to do is build a really easy to use CLI. So I want to break down what he just described. The context provided to Claude didn't just make the answer better.

It pointed Claude at the right problem to look at. And in Ryan's case, it was about making something that's easy for AI agents to interact with. And getting this answer right sets the foundation for everything that we're going to.

cover in this video. In the age of AI, we need to build things that solve real problems because that's how you provide value. The fastest builders don't do the most things.

They make the biggest impact. And Ryan, he helps millions of people use Claude plugins. So his context is different from mine and yours.

And that's totally fine. The point isn't to copy his context. It's to write down your own.

So to establish your context, to make sure you're actually building the right things, what exactly should go into it? The first thing that you want to do is tell Claude about your current situation. really is possible.

So what does your business do? Who does it target? Where are you located?

How much effort are you putting into your business? This context informs the direction. And notice the one thing that seems unnecessary.

Where are you located? It might feel irrelevant, right? But your location, your skills, and how much time you have, this all influences what the right answer is for your situation.

And so the second half of this first question is your desired outcome. The goal itself is usually easy, right? I want more customers.

I want to save time. But the hard part and the most effective builders make it concrete. And the second you give Claude the correct context, it can better turn that abstract goal into one number and one deadline.

Onscreen is an exact prompt that will force you to provide context and then drive you to a desired outcome based on these goals. And when describing your desired outcome, make sure to level it up. So in Ryan's case, it wasn't make an AI agent tool.

It was help our customers interact with our tools using AI. If you go a level lower, a task gets optimized as an isolated job. But when you layer it up, Claude can make more strategic decisions.

So when I was working with Ryan to answer this question myself, and I provided the context around buildpartner .ai, my tool, we use the WAP CLI, which you can... by running this command, but this effectively allows you to use WAP's tools directly in Cloud. And then once it's set up, because I have WAP pulling my website analytics, it can see all of my website visitors.

And because WAP has industry data from top performing websites on its platform, it didn't just hand me a number, it was comparing my current product to real benchmarks. And so that's how I can pull the desired outcome, not out of thin air, but based on real numbers. And when doing this and trying to answer this question on what my context and desired outcome was, it became clear That even though I wanted more monthly recurring revenue, the problem I needed to solve was improving my conversion rate.

So once we provided Claude with the right context to make a clear desired outcome, what should you actually build to get there? Brings us to the second question. What's the most important thing to build?

And this is about defining the MVP. So this question actually has two parts. The first is find what only you can do.

And then second, find the minimum steps to one real result. So to help us answer this, I actually asked Ryan how they think about it at WAP. And listen to how he describes your unique ability.

ability or your secret sauce. And then at the end of the clip, I'll describe how you can identify your own secret sauce. What we spend our time doing is ruthlessly prioritizing what is actually unique to our business like what can WAP do that no one else can do and that's usually like the most most most most high leverage thing to focus on and for us it's really about our ecosystem the millisecond that you get a payment on WAP you can spend it on a WAP ad or you can spend it on your WAP card to maybe pay rent for your office or pay a contractor or you know buy something that helps you grow your business even faster I think like the web of things that you can do after you make money on WAP is incredibly important and is part of our secret sauce.

So WAP secret sauce is this ecosystem, but how do you find your secret sauce? So this is a bit abstract, but your sauce is your unique ability. That is the hard thing that you can do that others can't.

Your location, your skills. how much time you have to spend on the business. Like these are all things that make you unique.

For any operator, for any executive, for any just person who wants to be more efficient, you should just ask yourself questions of like, what do I like to do? What am I good at? And that usually gets your sauce pretty quickly.

A good way to think this is actually, there's a perfect example in Silicon Valley. In the pilot episode, Richard's Pied Piper is a forgettable music copyright app. Then Hooli and Peter Gregory spot the compression algorithm hitting inside it.

And then a bidding war starts. The value was actually in the one thing that only Richard could build. That was his unique sauce.

Now, once you've identified this unique sauce for your situation, there's actually two ways to implement this depending on what you're working on. And so the first is streamline. automate what isn't your unique ability and this allows you to focus your human energy on what makes you unique in turn helping you save time on the other things and the second is double down on what makes you unique and figure out ways to enhance that unique ability to in turn increasing the value you provide for either one this unique ability can serve as a measuring stick so right are you working on your unique ability if no how can i speed up these tasks if yes how can i double down on this this is how you build faster not by doing more but by pointing your time at the things that deliver value faster now whichever bucket you fall into your focus needs to be on creating your minimum viable product and so i asked ryan how he thinks about creating an mvp and he told me about a car detailing business he started using wop's own tools let's just start really dumb right like what do i need to do to get my first customer well i have to talk to someone who has a dirty car simplest simplest simplest i'm gonna put some flyers on people's cars and then how am i gonna deliver the service well

i guess i have to buy a pressure washer i guess i have to buy soap i guess i need to buy like a wash mitten one of those sponge thingies boom now i have a to -do list of like things i need to buy from home depot and what I have to print and what I have to do to get my first customer. And I would say that is literally the MVP of a car wash business.

So with this in mind, you can ask yourself, what do I actually need at the bare minimum to get one result? That's the core of MVP thinking. Start with the result you want, work backwards and cut everything that isn't necessary to get there.

And I do want to call out that this isn't just for new businesses or new products. MVP thinking works on everything you're already doing. If your metric is saving time.

well then you ask yourself questions about like where am i wasting time this is just a general process that you can constantly do no matter what state you're in exactly like we help people run their business but you could just as easily you know run this for um So that's Ryan describing it, but here's how you can put it into practice.

First, take the metric you chose in question one and list the actions that could move it. Then narrow that list down to the minimum steps needed to test one high leverage outcome. Now I'll dive into this more in the next question Ryan asked me, but by cutting scope on anything you're building, you're focusing on the high signal components that make this valuable.

And honestly, the hard part isn't doing this it's the strategy of knowing which move is worth your time so how do i think about this strategically well when looking at my tool buildpartner .ai i have my whole product hooked up in wap so it sees all the website traffic i can then use wap's economic intelligence tool to help me determine high leverage tasks i can complete for my business and because wap has the data on what's working across businesses on its platform it can point at the highest leverage move better than almost anybody because it has access to this unique data so that way it'll something concrete like fixing a landing page or starting ads.

Then I'll ask to create a list of minimum steps to test it. Now, if you're starting a business or you're scaling a business, if you don't have WAP configured, you can use the first link below to sign up, which I am affiliated with transparently. But either way, here's a prompt to help you strategically answer this question about what is the most important thing to build.

So at this point, you've provided context and your desired outcome to Claude, and you know the one thing to build for your MVP. Now, those first two questions, a lot of people do, but this next question, percent of people skip but it is more important than the first two question three what are you not building so this is the biggest problem with building with ai it's not knowing what to build it's knowing what not to build so if you've found what you can do uniquely ryan's argument is that you should spend your time on nothing else once you have your goal and once you know what your sauce is i would say the most important question to ask is what should you not build and this when i say like like ruthless focus on the things that are important it sort of automatically means you shouldn't be focusing on things that are not important.

And he is right, right? These other things can just be so distracting because building is so easy now that everything can feel like it's worth building. And here's him talking about this building addiction loop.

Get addicted to building everything, you know? everything is shiny you know i as a programmer i would love to build my own database and like ah yeah dude like look at my the cool database console and it's got all these great colors and like i'm like benchmarking performance like i can save like you know a bunch of milliseconds here on this database query but like who cares like it it doesn't matter um and i should know that it doesn't matter honestly at the beginning because it stops me from going down these rabbit holes that um And the key word he says here that I want you to focus on is, but who cares?

It doesn't matter. Oh, you build a tool that's 80 % as good as a tool we already use. Great.

It doesn't matter. Oh, you build something that doesn't actually provide value. Great.

Oh, you build something that's really cool looking, but it doesn't save me time or help me make more money. Great. It doesn't matter.

And so one real benefit here of what you are not building is it makes it super clear what you shouldn't do. Your job as the manager of Claude is to connect. the pieces, not to build all of the pieces.

And if you ignore that, you'll end up with an AI tool graveyard where you'll have 10, 20 half -used tools, none of them actually doing anything. And so for Build Partner, there is just a bunch of things that I've elected that I will not build. Do I want to vibe code a payment platform that has to figure out how to accept payments in 195 countries?

No. Instead, I just tell Claude, use WAP to set up payment for this product. And it just does it.

And now I can get payment without building anything. Do I want to figure out how to run ads across TikTok, Instagram, YouTube, Facebook, and Google search? No, I'm not an ads expert.

So I'll just use WAP CLI from Claude and tell it I want to configure ads for these platforms. And it just does it. I don't have to think about setting up accounts on every channel, optimizing CPMs.

I'm leaning on WAP, the tool to do it. And so the point is, if you want to build faster, you can't focus on things that don't matter and that you shouldn't build yourself. Now, there is one word of caution here when exploring the use other tools framework.

And here's Ryan addressing it. this exact issue that you may run into once you get tool trigger happy i don't want to manage 10 tools my agent doesn't even want to manage 10 tools it's about maximizing value per tool versus maximizing the number of tools so the goal is to look for tools with robust functionality to cut down on what you need to build obviously here we're talking about wop but i chose them because i use them for payments help me run ads business intelligence and my website analytics i do not want to build any of those and i wanted a single tool that does all of these things so to help you answer this question run this prompt which will look at what you're building and what you spent your time on in the past and then help you identify what you should not be building once you've done that run this prompt which will help you identify any external tools that can help you with what you're trying to do.

At this point, we've answered three of the five questions. Now, before we get to the last two, and then a word of caution from Ryan about what you need to do after answering these five questions, you guys all know the drill. This is our anti -slap agreement.

Everything in this video is built by humans for humans. So all that I ask as part of this agreement is you subscribe to help this content reach more people. And if you already subscribe, make sure to turn on post notifications.

That really helps as well. And as a thank you to everyone, I appreciate all of you. I give away a Clawed Max subscription.

every video. So this video's winner is TCarson5045, who's building agents for narrow AEC pain points. And to enter this video's giveaway, comment below with what you're building or what you're deciding not to build.

And a fun fact here that I want to share with all of you, Ryan and I actually built our last startup together, IYK, which raised over $30 million. So for everyone building, double down on your human connections because you never know where your career is going to go. But anyway, we've gone through three of the five questions.

Question four is what are your building hot zones? Hot zones are critical parts of your work that you need to get right. For everything else, just let AI carry the torch and you monitor the outcome.

For me, within Build Partner, we have a custom plugin that helps people build faster with cloud. And this goes out to over 5 ,000 people when I update it. So this is a hot zone, to say the least.

So I asked Ryan, what do the most successful businesses on WAP do when thinking about this? All the successful business owners that we see on WAP are really dialed on making sure that um they're a they're really working with their ai to spend a lot of time on things that like really are the most important to their business.

But from there, he does add one really important caution to this. You can't just let AI run free. These hot zones are areas of what you're building to be extra focused on.

On screen, you can see a prompt that will help you identify what your hot zones are. And then what I like to do is I add in my claw .md. Anytime I'm working with a hot zone, flag it with me and make sure I approve.

And so again, for build partner, these hot zones and how I think about it is the plugin as well as our WAP payment flow. I want to make sure that the payments is working properly. But this is just part.

of it right how do you actually work in the hot zones themselves a term that you've likely heard is eval which is short for evaluations and this is the process of testing your changes to make sure it's getting better not worse the fastest builders know when to measure twice and cut once and in hot zones it makes sense to establish evaluation criteria when needed evals are definitely a large topic and i might have to make a full video on this but it's important that you have a strong foundational understanding of this process so what should you do today to implement your first eval.

This is what I call building a minimum viable eval. And here's Ryan talking about how to do this. Claude's really good at making evals nowadays.

Everyone's is going to look different, but it's generally going to be. your input, which is the thing that you're changing. In my case, it's the skill file.

There's going to be some program that Cloud helps you write, which like runs all of these, call it tests, that does the squats for you. And then at the end, you get a report, which is how your input did against the suite of tests that you ran against it so from that think of it like a simple equation you have your input and your output this is the whole grading mechanism and then you have what you're changing this is the variable that you're adjusting to see what the output becomes and you may be thinking this is just for technical work but it isn't in our conversation we covered two kinds of evals the first is a standard eval which uses a programmatic approach to evaluate quickly through testing cycles this is typically when you hear about people talking about evals they run loops and they automatically improve themselves in order for to work it has to be extremely programmatic the second slow evals are for non -technical work and this involves more human judgment for molding the evaluation criteria so to put a real world example of this i did a slow eval for a skill that i built for an engineering firm that i worked with let's call the skill slash generate report and so we would use a skill to generate the report we would take that output we would get feedback from the engineering firm that we worked with and then we would adjust the skill until the output was approved by them and then we would store that approved version then the next time we would run the report and

and they would provide feedback, we would change the skill, but we would rerun it on all the past approved reports to make sure that nothing breaks and it doesn't regress for what those previous edge cases were. And so you can imagine over time that we build a test suite for these reports and it can run this evaluation criteria over time to get better and better.

And this process isn't instantaneously, but this slow eval process can really make a difference. Now to identify any specific hot zones that are worth building a minimum viable eval for, use this prompt, which will help you get started. Now, the last question that Ryan asked, me is what I think is the most underrated.

Question five, what are your bottlenecks? And you may be wondering, I'm not sure where my bottlenecks are. And so Ryan thinks about it as something that you identify as you run towards your goals.

Let's say you're trying to scale your revenue and you get your conversion rate to a good place. Your bottleneck is how many people actually land on your website in the first place. You're converting all of them, but like no one ever lands there, right?

Or you could have the opposite problem. Oh, so many people land on your website, but none of them check out. What?

Like your bottleneck is your conversion rate. And what he discussed here is why you do questions one through four first. That's so that we know we're moving in the right direction so that these bottlenecks are relevant to our desired outcome.

But the biggest transformations are when you find the real bottleneck and then suddenly one fix can just change everything. So how do you actually spot your bottleneck? Often, it's the things that you actually avoid.

Everything that people don't enjoy doing eventually becomes a bottleneck. And I'll give you a good example. Like a lot of business owners, they start out being employees.

maybe you started off as a website designer and you've made this killer website and you just love making websites and you keep improving your website. Well, you're eventually going to be bottlenecked by the quality of your product or maybe how you drive people to your website because you're not a marketer, right? But you just because you love improving your website so much, it's really hard for you to switch.

and like focus on these hard problems that are uncomfortable you're unfamiliar with them so a lot of the times you can identify bottlenecks through what you don't want to do or what you're not good at or looking at what you haven't spent any time on that's the avoidance test procrastination is wisdom use this as a signal for where your bottlenecks may be located here's a prompt to help you identify bottlenecks and quantifiably identify what the wap cli can solve for you and then if you have the wap cli installed here's how you can use that to help streamline these bottlenecks now at this point you may have two questions.

How do you know if you're working on the right bottleneck? That's where you want to think about effort versus return. If you feel like you're putting in way more energy than you're getting benefit out of, you likely aren't focused on a bottleneck.

You're focused on something else. Then how do you know if you've solved a bottleneck? The best way to do this is use benchmarks.

If you look at something like your conversion rate and it's some percentage below industry standard, that's a bottleneck you can still improve. But in order to do that, that requires knowing what the standard is, which is exactly where I'll use WAPS data to help me get that answer. So here are two prompts to help you.

First, find your bottlenecks by what you avoid. And second, use the WAP CLI to put an actual number to this bottleneck. So after these five questions, what's the part Ryan said almost everyone gets wrong?

And this is the most common problem. You only ask these questions once. The answers that you provide to all five of these questions, the reality is it has a shelf life.

What worked on day one isn't enough on day 100. And you couldn't have known the right answers when you started because things change. So you have to schedule periodic reveals.

Here's how WAP does it. the cadence I'd copy. Every quarter, we find out what our biggest desired outcome is.

What are we trying to improve about the business of law? Right. WAP is a business.

We happen to help people build businesses, but we are also a business and there's different things to focus on. And then week over week, we might think about, OK, what is the most important thing that's going to move us to that outcome? Whenever you're working on something, you can bucket your work into two categories.

The first is execution and then strategy. Execution is for when you know exactly what's needed and you want to revisit this weekly, if not daily. This is your list of to do's.

And for me, I literally just run this on an Apple notes every day. I have my items that I have to do. Question four and five.

that we covered in this video that's where this falls what eval are you proving what metric did it move what are you working on today to push you toward the desired outcome in my eyes execution is actually really easy the second bucket is harder strategy this is where you're planning what's needed but if you do this every day then you get stuck in strategy and you don't actually build anything so realistically you want to revisit this monthly or quarterly and questions one and three are strategic that's what's my sauce what am i not building the goal is to find a goldilocks zone execute quickly so you avoid analysis paralysis but make sure it's actually in the right direction and if you skip re -asking yourself these questions here's what can happen if people don't stop and ask themselves questions about like what's happening what they want to do what's giving them joy what they're good at they would never discover these other opportunities and they'd be maybe like

incorrectly focused on that one thing that they identified maybe like many months or even years ago so what you need to do today is put a recurring event on your calendar weekly for execution monthly or quarterly for strategy and don't overthink it so ask yourself these five questions to make sure you're building the right things first what is your context and desired outcome second what's the most important thing to build third what are you not building four what are your hot zones and five what are your bottlenecks and then you need to ask them again on a specific schedule.

So WAP helped me put this all into practice, right? The data behind my numbers, the CLI that pulls them in, and the tools that mean I don't have to build payments, a website, or analytics myself. So if you want to try WAP, click the first link in the description and shout out my boy Ryan.

I love having friends who are smarter than me building awesome things so that I can work together with them. Now one thing that I did discuss here is knowing the importance of when to use the right tools. WAP is one of them, but if you want a breakdown of eight free tools everyone watching this video should use, go check out this video.

If you like this, I guarantee you'll love that. I'll see you over there. Peace.

The Hook

The bait, then the rug-pull.

Building is so easy now that everything feels worth building, and that's the trap. Austin Marchese relays five questions from a Whop engineer that point Claude at the one problem worth solving.