Overskill Series Part 2: Refining Your App | Coaching Corner #043

In this live Coaching Corner episode, Tyson and Devin continue their Overskill series by refining a prototype roofing app built on the Overskill platform. They review the initial app, discuss the need for iterative refinement after the first generation, and demonstrate a back‑and‑forth workflow with the AI using spoken prompts (WhisperFlow) and prompt stacking. Key design concerns surface, including client‑side vs. admin‑side UI separation, lack of clear client navigation, missing calendar and timeline views, revenue/estimate fields, and the desire for weekly project updates. They ask the AI clarifying questions, adjust the prompt to add a calendar, revenue projection, and project‑stage cost fields, and observe the AI’s queue‑based processing. Throughout, they emphasize treating the AI interaction as a conversational dance, using WhisperFlow for hands‑free dictation, and iterating until the app reaches a usable state. The session ends with a call for viewer feedback, a reminder of weekly office hours, and plans to continue the series toward a marketable product.
Chapters
What's up everybody? Happy Tuesday.
What is up?
What's happening? Happy to be here with, uh, our main man Devin and, uh, I don't know, hang out with you guys. What a fun time. All right, today we're following up what we talked about last week. What'd we talk about last week, Devin? What was, what was so fun that we have to stretch it into 2 episodes? What, what's going on today? Overskill. I wish I—
sorry, I'm not, I'm not Greg. I don't have this soundboard.
I was thinking the same thing. Uh, one day we'll be as cool as him, but for right now, just, I'll take the, the ad-libs. It's okay. Um, for now, yeah, we're talking about overskill and just kind of expanding upon what we left off on last week. Last week we were more or less just talking about like the basics of getting up and running, how do you— how does it get started with the platform and, you know, prompt your first, uh, app experience, right? That, that's kind of what we were after, after, uh, but there's some other things in that that I guess we didn't really take time or have time to cover, which is what do you do once you have the first refinement? What do you do after you make the first, um, I don't know, app creation? Like, it's, it's been created. You're not the, the product of what it created after that, I don't know, 10-minute time period it took for it to build whatever you asked. Um, what next? What now? Like, we're just gonna be staring at the screen. So like, what do you do with that information?
Yeah, absolutely. I mean, yeah, I— there's, there's also just like a lot of things that kind of go into like building out this stuff where it's not always instant. I think we're kind of used to that instant gratification of stuff like this. And sometimes when you're building out something to this stature as well, you kind of have to work with the prompting, see what it comes back with. Maybe you need to be a little bit more specific on certain things. Maybe it needs some clarification. And so it takes a little time. We're still brewing it up in the background too, of everything that we were working through last week. Um, yeah, it's, um, it's a little bit of a process for sure.
Yeah, it— and, um, with product process comes refinements and just evolution of the actual initial idea. So, um, yeah, nothing wrong with that at all. That's part of the game. I'd say that most of the time here, like, it's, it's gonna get close, it's gonna get like close to what you're describing, but then you're gonna see it in, in in actuality, and you'll be like, huh, I actually don't like the way I worded how to set this up. I think we need to change this portion up. Like, maybe like the header is like completely off, or like the colors are just— we didn't specify on colors. We definitely didn't do that last time we talked about Overskill. I didn't say anything about design or, uh, the layout and flow of a page. You know, that's gonna become a common problem or I don't know, commonality between every platform you use, but in this case Overskill, right?
Yeah, I wouldn't even call it a problem. I would say like the, the thing about it is, is that every platform you're using from an AI perspective, I think on its like basis of its foundation has like a foundational design principle kind of built in. So if we're not being like super specific with what we're talking about here, um, at a certain point, let's say we had a room of 20 people building something on Overskill, even if we're building something completely different, there might be a lot of similarities in the design if there was no specification of like branding and, you know, things that would kind of set you apart of like, oh, that's something Tyson was building for his business, or oh, that's something Devin was building for his business, and seeing those differences.
Yeah, yeah, 100%. So I guess it's a good way to segue into our first and only slide of the day. Uh, don't worry, not a slideshow presentation. It's really just, uh, one initial kickstarting that point. Um, we've already said it enough at this point for you to understand what we're talking about, but your first version is just a starting point. It's never usually the end point. If it is, then you're— I don't know, you have things really refined. You took like a year to go through every small minute detail when it comes to app functionality and how— what it looks like, how it functions, what it's going to do on the other side for whoever's using it, right, um, into one prompt. And, um, kudos, well done. I don't think I've ever achieved a one-and-done situation with app building, but I like it.
I would, I would go as far as saying if you're spending a year to try to build the world's perfect prompt to put into an app to build your app, you're probably wasting too much time overthinking and not enough time just putting the idea into action. I'm just gonna say it. We're gonna talk about the elephant in the room or something like that.
That's fair. A year is way too long. You know what, I put it out there. I was being— I was exaggerating. But you're right. Don't take a year. Yeah, treat it like a conversation. Like you go back and forth. And, you know, there's a continuation that has to happen. You have to acknowledge what happened in the conversation with what someone else said. Then that person, you basically go back and forth, right? There's a dance that comes with the conversation. Same thing happens with a conversation with AI, right? Kind of alluded to it last time, but Whisper Flow is probably my favorite way to do this personally, just because you can literally just prompt it to be on and you can talk out loud and describe what you're seeing and what you think would look better and just describe the other side of that, whatever it is that you're trying to have shifted. We'll show that in a second. But, uh, personally, my favorite way to do that— you can use regular dictation, I'm sure that exists elsewhere, but it's not, it's not as smart, honestly. And that's the problem. Yeah, exactly.
WhisperFlow is, uh, definitely a little bit more intuitive as far as picking up on— you can even— it'll pick up on your corrections too. You can start talking to it and kind completely like change your thought and be like, actually, no, scratch that. I want to mention this. And it'll just completely leave out the piece that you're like, scratch that or whatever. Whereas like the dictation would literally say, scratch that. But random side note too, I also find it funny that it's called Whisper Flow. Imagine if you had to like whisper when you talk to it.
I've done it. I've done it. All right. No, I have. Because my wife was sleeping in another room and I was like, this is embarrassing. I can't be caught talking like this.
This is crazy.
So I'd literally be whispering to—
Who are you having a conversation with last night?
Yeah, like, who are you talking to right now? I didn't tell her I was using this. And yeah, I didn't want to have to describe what I was saying while I was talking to AI. Anyways, yeah, I have tried that out and it works. It does work pretty well in low volume. And didn't lose anything. Um, yeah, okay. Either way, tangent. I think we covered enough of what we're talking about today. We're just gonna go through what we should— what you should do if you're going back and forth, um, or when you're trying to make refinements, right? The— this is the app that we were kind of working on last time. This is for a roofer. This— that's just the niche we picked out of, I don't know, I don't even know why I picked Roofer, but it was on my brain last time we were working. And so Roofer is what we went with, baby. And here we are. Uh, it's an app where you can essentially— you can manage projects from the customer side and the owner side. On the owner side, we're really just going and maybe documenting the, the actual project that we are about to do. So we can say what the actual project estimate is going to be, how long it's going to take. Uh, job scope. Um, yeah, and just give a nice little overview, right? And then on the customer side, which is what we're looking at right now as an example, it'll give kind of an overview of what's happening. And don't, don't read too much into this. I was having fun with it and, uh, that's it. The job scope is a fun time. Is that what you're laughing at? I see you.
Yeah, Jason's making me laugh, uh, in the comments. What's up, Jason? Uh, he, uh, he said, I can't believe you guys chose that niche.
Hey, come on, you want to be part of this?
It pays for itself. Look, it pays for itself. Look, that's a $2 million quote for a roof. I, I, you know, we have to readdress, uh, some of these people here. I don't know why they were quoting so high for a roof, but you know, maybe it opens up, who knows.
Okay, but the concept was we wanted an area where everybody can manage everything at once. The client side, like the, the business owner could send a proposal, have them view it and see the timeline and see the progression as that, uh, as that project's underway, right? Just because most of the time you have no idea what's actually happening when it's happening, um, and you're just sitting there waiting until you get a call or they show up the next day or whatever. And like, this could help you kind of create that transparency perhaps, right? That was the thought process behind it. But we can switch different views. We got client portal right now, that's what we're looking at. We've got a dashboard that should be the business owner side. Cool. We have project list over here on the left, project details. Uh, we haven't really tested it out. Like, this is— we're doing it together. So, uh, if we go and add a new client as an example—
If it breaks, if it breaks, Tyson built it. If it does well, I built it.
Shoot. Uh, @gmail.com.
Imagine being the first Devin to create a Gmail account. There's some power there.
It wasn't you. One. Okay, and then we'll go ahead and save clients. Okay, so yeah, we went and created a client inside of the Accounts. I see 2 clients listed. I don't see anything here. Oh, it's for project lists. Okay, cool. So we go down to the bottom, we see all of our clients in one area. This is kind of messy. I don't know, what would you say that you would change around this? Because this right now, it just seems all like— I don't know.
First things first, view-wise, I mean, if I'm looking— because scroll up a little bit. Because we have client details. This is just for one client right here, Test Client 1, and then you scroll down and you see all the clients there at the bottom. Seems like there's not really— there's not really client separation at that point.
Yeah, it's only one.
And this is— this is from our view or from their view?
This is our view as the business owner right now.
So, okay, I was gonna say, because if this was from their view, that's also problematic because then they could see other people's, uh, information. But I would say too, like, from the specification, from an admin perspective, I would like to see just a separation of like the global contacts, if you will.
Um, so just so we don't lose this, let me write this down and I'll keep my mic on so you can hear how I'm prompting it, right? I don't know if that's useful or not, but I used to—
Oh, I think it's very useful.
Cool.
So makes you whisper.
In our example, Devin's asking— No, in our example, Devin's asking for, uh, a separation with clients. As of right now, all clients seem to be blurred together onto one central page for the business owner's perspective, which is kind of inconvenient. It doesn't really allow for separation of data, and it kind of blurs everything together, which isn't— yeah, just not helpful. Um, Aside from that, I am not sure I'm following the client record feature at the bottom here. And that's— is that just for one client? I don't know. So far, I don't think that belongs at the very bottom here without any context. It doesn't— I can't switch between the 2 different clients. So at this point, it doesn't make sense what it's actually attached to for that log at the bottom. Nice to have, but I'm not sure I follow. Um, looking at the top of the page here on the, the business owner side of things, it would also be nice to have maybe a project— projection of revenue. Um, if we have an ability to maybe have set costs that we can, I don't know, include here, we can— some form of, form of accounting or analytics up top. Would be nice. I feel like that'd be useful, uh, if we're talking about the home page, like the home page for the owner itself. Um, yeah, I'm trying to think of what else to add there. Like what, what other things?
Pacific was saying maybe add like a calendar. Do you mean like a calendar where they can see, um, like scheduling for things, or—
Let's see if That's a good idea. See if that's what you mean. Clarifies. Add calendar.
That would be interesting.
If that's what you mean, then yeah, I'm, I'm on board. We definitely add that.
Yeah, maybe just add that towards the end of the prompt there. Yeah, like a calendar to see like your overall— like, I guess if we're thinking from the admin perspective Maybe a calendar to see your overall, like, schedule of what you're doing.
Another thing worth mentioning for the admin side of things, it'd be great to have a calendar to see what is happening per project. And that way you get a better idea of sort of timeline that takes place per client, or just in general, all clients in general. Yeah. Okay, cool. It's a good idea.
Uh, yeah, he confirmed as well, so we're, we're on the same page.
Beauty. Okay, anything else? I think that's good for right now.
I think that's good for right now because the other thing too, we don't want to like overload it with too much at once. No, I'd give it all. I, I just say at this point of the refinement, at this point of the refinement stage, you know, we could get really granular if we're like just kind of piece by piece finding things here. Um, and then as it continues to, you know, modify stuff too, we might have more feedback for it to tweak certain things here and there. Yeah, but this is kind of the flow. It's like, uh, you know, like Tyson was saying, you're kind of dancing with the AI a little bit, maybe a little salsa, who knows.
Um, but, uh, let's take it back. I guess while it's working on one side, we can hopefully look at the other. I don't know if it'll Oh, did it already do it? It already did.
Enough said. Said I can do that.
Sign direction. I see why the contact log feels disconnected. Oh no, it hasn't. Before I change the app, could you confirm a few details? Question 1, by separation, do you mean clear client-by-client navigation and filtering? For question 1, yes.
And so we dance. For question 2, what is it saying for the Financial overview should show estimated revenue by the project stage and projected profit after the cost. Would you prefer one estimate cost field per project or separate material and labor costs? Maybe one estimate per project because they might have multiple that they're working on.
Project.
And then for question 3, it's pretty much just clarifying exactly what we wanted there, which is the Project start and expected completion dates. So I think that's pretty on par with the third one. See, when you're typing, it sounds so much more aggressive than whispering.
It takes way longer too. Okay, for question three.
Uh, it's basically just asking if it wants the calendar to have a project start and completion, which I would say yeah.
All right, it cut you off when I do Blister Flow, but you said yeah, you agree?
Yeah, yeah, you're good, I agree.
Cool. And submit. Let's do this thing.
Okay, agreed.
While it's doing a thing, its thing, we'll go and check out the client side. So on the client side, what would be nice to have here, right? Um, we have the estimate As far as— oh, estimate sent. Okay, one link project, and it just has like the one project they're working on. Okay, um, there's not really a date as far as like timeline goes. I feel like that'd be one thing. I, you know, I don't know if you can—
Isn't that what the— it's not what the—
isn't that what the calendar is going to This is the client side, so we did that for the— okay, the other side, so they can, they can map things out.
Uh, yeah, so maybe mirroring some of that on the, on the client side.
We'll just write down while it's working on another thing.
Client side prompt stacking.
Prompt stacking, absolutely.
Um, feel free to whisper and flow.
I will. Yeah.
Cool.
It would be great if there was some sort of description or overview of timeline when it comes to projects. Right now, it's just kind of a floating, lingering thing. It doesn't really have any— I mean, we have job scope, but I think that's more or less just what is actually going to happen in that project, which in this case makes sense. But I think a date area, maybe, I don't know, a calendar carrying over here. That might be nice somewhere on the page. Like with it highlighting the time period that it's going to be taking place. Yeah. Okay, what else?
I'm kind of looking through it here. So we have the calendar when it's taking place. Um, I don't have like major feedback for the client side at the moment. Is this— this is the— is this the full— this is the full scroll? Yeah, we don't have anything above this.
It's a one-pager. My thought would be like, okay, for something like this, for a project, roofing project, is there other components that come into play? Like, do you have any other contractors that you're would end up needing to come into play here. Is there like— is there—
So maybe, maybe different tabs?
Yeah, I don't know what tabs. So like, how can we incorporate that all in one thing?
Okay, so you have— let's say you have, for starters, let's say even before you have the project done, um, maybe you had some sort of a roof inspector or just a roofing expert that came and they were like, hey, this is what we feel like needs to be done to your roof. This is the actual cost. Maybe they're the person that fixes it, maybe they're not. But then from there, you actually have the repairs done. I can't— maybe roofs are just throwing me off a little bit. Roofs are okay. I can't think of like too much sequence that would go in to, to that. It's like, oh, your, your roof needs repair? Okay, cool, send somebody out. Cool, this is the estimate. You want to pay me? You don't want to pay me? You don't got $2 million to pay me for your roof? Then be gone.
I think, I think that, okay, it'd be nice to have like project, like weekly updates or something around the project. I don't know, a roof usually takes, I don't know, I'm not a roofer. I'm guessing like a week or two, right? I'm gonna get— I'm gonna guess that a week, a week or two.
But it'd be nice to know average.
Yeah, maybe let's do that. Let's get some actual, actual data on that one.
And, um, let's see, let's see. It says the average, the average physical Installation is 1 to 3 days, but there's pre-installation of securing permits, ordering materials, and all that stuff that would be anywhere from 1 to 2 weeks. So let's just call it 3 weeks to be gracious there.
Okay, cool. After looking it up, it seems that it takes anywhere from 1 to 3 weeks for a roof to actually be replaced, from inspections to permits to any pre-work that needs to be done to the actual fulfillment and installation of the roof itself. Uh, it'd be nice if we had that included in the actual process here so that way people knew from start to finish where they were in the actual process. Um, it'd be nice if we could maybe have that updated from the admin side of things and have it portrayed and shown on the client side of things. Aside from that, it'd be cool if we could have some sort of update section where the contractor or the person that is fulfilling the actual service, the business owner, whoever is actually on site and managing that, could leave an update maybe once a week or per day. They can set the routine as, as they see fit, but leave updates for the clients so that way it's almost like an open dialogue. As the whole project progresses and they get closer to the end date, or just in general throughout the entire experience. Would you agree?
I would agree.
Cool. All right, looks like we're 2 out of 4 over here. I don't— I wonder if I hit enter, what do you think will happen?
What do I think would happen if you hit enter?
Yeah. Oh, we're 3 to 4. All right, I think it's almost done. I can just— I'll just wait.
Yeah, I'm gonna say we might, we might wait. We got it, we got a few minutes. I was answering a comment in the— I was answering a comment in the chat. Somebody asked how— how— oh, he said how often are these calls, not how long are we here for. I don't know why I read that the way I did. Um, Mark, if you're still listening, uh, these are once a week. Um, uh, my, my comment basically means nothing.
Yeah, no, eight minutes does not come to play here except for today. We we're here.
We're here every minute training.
Third minute training every Tuesday. We might move it to one thirty Pacific Standard Time next week, but we shall see. Either either way, there's announcements or it's it's added to the live stream either on YouTube or Facebook, the Facebook page directly. For ClickFunnels. And that's it.
Yeah, there we go.
I corrected it. Oh, look at that. There we go. This is what happens if you end up submitting more than one. It just actually ends up creating a queue, so it will— ah, nice. Okay, I sent it. Well, we're stacking up here. I think our—
might as well, just so we can, just so we can kind of be building on that, because obviously we only got about 5 more minutes left here on stream. So we want to get as much as we can kind of moving here so we can continue this series. And I think the hope, you know, by the end of this is that we have something like actually usable that we can say, hey, this could be something that maybe we could actually sell, per se. Um, that's the, that's the hope. So I don't think, um, I don't think stacking on the prompts are a bad thing here. And this also gives you a visual of like, if you were building an overskill, how does that look? If you did have multiple thoughts, do you have to sit here and wait until they're done, or could you just stack? And the answer is you could stack. It's got a queue, you're good.
You can also play games if you want to join the leaderboard.
But, uh, yeah, yeah, that's right.
Not today, not today. It's all good.
The—
I mean, honestly It does take time in between, and that's just— that's part of this process. But the— I don't know, we're, we're thinking about taking us all the way, like Devin said, to a point where we might even end up walking through how to sell it, you know, after the fact, once it's refined enough and it's, it's at a point where, I don't know, people— it's usable, right? Uh, if you want to see that, obviously leave a comment letting us know that that's interesting. Otherwise, maybe we'll deviate to some other topic. Somewhere in the middle there, I don't know. Um, but this is going to be an ongoing series probably for a little bit until we make it work, until we, until we see it through, baby. For, um, for today, as far as like, I don't know, when it comes to other aspects of this, what's— are there any other things we haven't thought about so far?
So far I feel like this is a good This is a good point to see what it actually comes up with. Obviously, we're still in some really big preliminary stages of allowing it to build and seeing how it looks, seeing how it functions. I think as we see it kind of building across the way, we're going to get more answers to be like, okay, maybe we like this calendar here that it built. Maybe it's too much, whatever the case may be. But ultimately, um, yeah, I don't know how I feel about calendar. I was gonna say, I, I don't think it— now, now the calendar on that calendar note is taking up so much space.
Yeah, um, we have client history. You're viewing all clients. Select a project. Okay. Oh well. Uh-oh. Okay, still, still pushing us. We got the revenue shown here, $2 million. Nice, we're killing it.
$2 million on the roof, they should be good for the year.
On a roof, yeah. Okay, so this one actually has a project history. We have the project lists, we have the current estimates. We can do— now we can set time and estimation of day for completion.
Increase the estimate if $2 million is not enough for you.
Um, estimated costs, we'll say $20. It's a pretty good return. Project updates. Okay, cool. Uh, oh, so it must have— that was fast for that one. Good to know it's already working on the next page.
It's still showing the— it's still showing the client stuff at the bottom, so I'm curious once it fully goes through it if we're still going to see that at the bottom there.
This right here, is that what you're talking about?
No, where it's showing all the clients at the bottom there.
Yeah, and I can't click through them. Oh, I can open. If you open at the bottom, it'll take you to that specific contact instead.
I still am just not a big fan of like how that's displayed. I guess I'm thinking more of like an actual like CRM layout, even if we're thinking of like ClickFunnels. If you think of like global contacts, how you have like a page that's just kind of specified and you have all those contacts there. Um, I, I find it a little weird that you'd be in like one contact profile and you click underneath it because you might even accidentally— I, I could see you accidentally clicking on someone else's contact profile and maybe you put wrong information in it because you didn't even realize it went through.
Yeah, no, that's a good point. Okay, I'll, I'll try to prompt it. We can get that set up before the next call. Um, yeah, I can't believe it's already been 30 minutes, but this is, this is the process. You're literally going back and forth. Having a conversation with it, defining exactly what you want to be adjusted. If you don't like something on it, that means you can go in and prompt it to something you do like. If you don't know what you actually like, then go do research around, or even have it do research for you around other softwares that might be similar. Um, could do that, or just like best practices, right? But go play with other, other platforms. That's usually a nice, uh, I don't know, testing ground or exposure therapy, I guess, for this type of thing. is actually seeing what is out there right now. We're not trying to copy, but yeah, model or understand.
The other thing too is if you have those examples, like, it, it just gives you fuel to prompt the AI too.
Yeah, because then you can be a lot more specific around, I don't want this to be this big, I probably want to be a quarter of the size. I want— like, you can define exactly how the layout and structure might actually come through. Um, yeah, very, very good point. But okay, um, that was fun. Literally, this is, this is prompt engineering at this point. You're literally going back and— not prompt engineering, but you are, uh, AI engineering now. I don't know how else to describe this. We're building something, we're inventing something with our words, and it is becoming the reality, which is bizarre and cool to watch.
We're whispering and flowing.
We are whispering and flowing. And, uh, we're not affiliated with them at all necessarily, but I, I recommend personally That's just, that's where I'm at. Uh, Rob would say the same. I know he uses that all the time.
Devin? I think Todd, I think Todd, uh, he used it in a couple videos I've seen recently, so. Oh yeah, during one of our challenges. So just saying, I mean, you know, enough about WhisperFlow anyway.
Yeah, if there's any other specific parts of this that you want to see us walk through, obviously, you know, stay along for the journey or just put in the comments what you're looking to see and we can engineer this towards what you're looking to see. I guess it's kind of a journey we're creating together. So that's it. That's all I have to say today. Anything else, Devin? Close us out.
I, I think that's pretty much it. It's been a very whimsical time here, um, on the Coaching Corner. I'm glad that you're in my corner. Thank you everybody that's come to this corner of the coaching, and, um, we're gonna be happy to see you next Tuesday.
Maybe final comments If you have questions and you wanna walk through anything live with one of us to help hold your hand, we do have open office hours Monday, Wednesday, and Friday from 11:00 AM to 1:00 PM Eastern Standard Time. And this is a link to be able to join, clickfunnels.com/office-hours. And we'll be there live hanging out, answer your questions, and looking forward to seeing your beautiful faces. That's it.
Be a fun time.
Always.
See you guys later.
All right, guys, happy Tuesday. See you next week.
More from Todd

How to Set Up and Send Your First Newsletter In Daily Draft | Coaching Corner #044









