STICKY BRAND LAB
  • Podcast
  • Ask Muse
  • About
    • Blog
  • Services
    • Be YOU-nique
    • Be Distinctive
    • Be Val-YOU-Able
    • Courses
  • Resources
    • Podcast Freebies
    • Recommended Biz Resources
    • Offers
  • Mindset Reset
    • Meditation & Inspiration with Cyndee Rae Lutz
  • Mini-Podcasts
    • How it Works
    • Sample Mini-Pods
  • Contact
Picture

The Sticky Brand Lab Podcast

Empowerment for professional women who are ready to call themselves an entrepreneur!
Small steps. Big wins.
​Bursting with humor, optimism, and real-world experience, each weekly, engaging episode provides you with small actionable steps for building a profitable side business. Come be a part of our safe, judgement-free, diverse community of like-minded entrepreneurial seekers.
Picture
Picture
Picture
Picture
Picture
Picture
"Love the Sticky Brand Lab!
[The podcast] provided me so much insight as I began to build my new business!"

~Jessica Kersey Rodriguez, Founder, Cloud 9 Nonprofit Advisors (​www.thrivewithcloud9.com​)

I have an Idea for an App. How to Turn Your Great App Idea into an Actual Product - #40

7/6/2021

0 Comments

 

Show Notes

You’re not a developer, but you have an innovative idea for a software or maybe a mobile app, now what? How can a non-techie turn a great idea into a viable product without blowing your budget? That’s exactly what Lori Vajda and Nola Boea wanted to know so they sat down with Igor Belagorudsky, Founder and CEO of Fast CTO. Igor and his team started the company to help people and companies with great software ideas get them built the right way, the first time around.
In this episode Igor shares his experience, insights and tips so listeners can learn what you need to know about hiring developers, why you don’t want an SOW (statement of work), and how to build a successful tech company.
Thanks for Listening!
​

Ready to start your business or grow your personal brand? Schedule a free 20 min. consultation call now. 

Sticky Brand Lab is the place for professionals who want to take their knowledge, experience or ideas on the road less traveled. 

If you enjoyed this show, make sure to subscribe to the podcast so you’ll never miss an episode. Want to get to know us more? Find out more about us and our services at Sticky Brand Lab

We love hearing from you! Leave or speak your message here

If you haven’t already, please connect with us on Facebook! 

Would you like to be a featured guest or have your question, comment or review mentioned? Ask Muse!

Business success strategies are in the works. Come have a listen!
In This Episode You’ll Learn
  • Why a poorly executed mobile app or software idea can quickly become a huge bank debt and how you can avoid it.
  • The make-or-break steps for finding and hiring the right developer partner to successfully build your app.
  • The risky mistake first time startup founders make when coming up with an idea for an app. 
  • The 3 reasons you need to treat your app like a business.

Hire a reputable app developer. It’s a statement that implies anyone can do so. As Nola and Lori found out, when you’re a non-techie with a great idea, but limited to no experience talking the language of a developer, miscommunication is the fastest way to lose money on app development. As Igor Belagorudsky pointed out, while it’s important to do your research, being knowledgeable about what to look for, what type of developer do you need and speaking the language throughout the process to ensure your idea is executed, is quite another.

(5:16.46) While the process of building an app seems pretty straightforward, this one costly mistake often leads non-tech founders to hire the wrong team of developers and programmers. 

(7:48.17) The three primary reasons non-tech entrepreneurs should be wary about signing an SOW and why it usually doesn’t help with getting your idea built.

(11:10.90) Why you don’t want to hire, and should run the other way, a dev shop that offers project management for free. 

(13:06:42) When it comes to technology businesses, men and women have uniquely different approaches. Unfortunately, that difference can also lead more women to get taken advantage of by these scammy dev shops than male on.

(14:20:20) Before hiring anyone, this is the first thing you should do, when considering if your app is worth developing.

(17:12:28) The three main pros and cons of hiring a freelance software developer and hiring a company such as a dev shop.

(19:27:22) The surprising answer to determine whether or not you can tell if a developer is trying to scam you.
Resources 

You can subscribe to Lori and Nola's show, (we love you and want to make it easy) on Apple Podcasts, Spotify, Audible, Google Podcasts, Stitcher, or wherever you listen to podcasts.

Fast CTO

Email address: igor@fastcto.com

Connect with angel Investor and CEO, Igor Belagorudsky Social Links:

Linked In: https://www.linkedin.com/in/igorbelagorudsky/ 

Instagram: https://www.instagram.com/lookattheigor/?hl=en 

Facebook: https://www.facebook.com/fastcto  

To Get Igor’s two recipes and quote: Sticky Brand Lab Resource Page

This episode was supported by: Be-YOU-nique

Transcripts

Nola: [00:00:00] You have an idea for an app or possibly a business software solution? It sounds exciting, right? Not to mention the friends and family who agree. This is a great idea. There's only one tiny problem. You're not a developer. So, what do you do? How do you develop your amazing idea into an app or software? Well, stay tuned because we're addressing all this and more with a chief technology officer and subject matter expert. In today's episode,
 
Announcer: [00:00:28] You're listening to the Sticky Brand Lab podcast, where time strapped professionals, learn how to create a business you love in as little as three hours a week,
 
Lori: [00:00:39] Is it possible to create an app, start a SaaS company, or launch a startup without a tech background? And if it is possible, what does it take for a non-techie entrepreneur-minded individual to turn her great idea into a viable product or business? We wondered. So, we set out to find out. And one thing we learned along the way; it starts with finding the best people to help you see your vision through. Hello and welcome aspiring entrepreneurs, Lori and Nola here with a decidedly, non tech savvy approach to getting your app or software solution idea on the path to development. But before we get this, everything you need to know about turning your idea into an app or software solution, but we're too embarrassed to ask show started, be sure to subscribe to our podcast on Apple Podcasts, Google Podcasts, Audible, Spotify, or wherever you listen to podcasts. That way you'll never miss out on any of our weekly helpful, informative, and always opinionated podcasts. Now let's get this say-yes-to-built-by-a-non-techie-founder show started. Woo!
 
Nola: [00:01:51] Woo. You are likely familiar with the following tech companies: Airbnb, Tinder, Pandora, and Apple. But what you might not be familiar with is that these companies were built by non-tech founders. That's right. Airbnb founders had industrial designing background. Pinterest founders were educators and Michael Dell was doing trade and stocks before he started Dell. For non-techie people, ourselves included, technology lingo is a foreign language. And when you don't speak the language, it's understandable to feel embarrassed, intimidated, and anxious, the moment someone talks to you using terms you know, nothing about. So, we set out to find a technology expert who specializes in working with novices, just like most of us. We wanted someone who could help us understand exactly what our audience needs to know in order to turn their idea into a viable product. Angel investor, mentor, advisor, and consultant, Igor Belagorudsky is founder and CEO of Fast, CTO, a company dedicated to helping people and companies with great ideas get them built the right way the first time around. Or said another way, you are a technology evangelist, software architect and thingy explainer. Welcome Igor.
 
Igor: [00:03:10] Hello.
 
Lori: [00:03:10] Hi. So, before we get into the specifics of how non-tech new entrepreneurs can go about creating an app or a software solution, can you tell us what is the most entrepreneurial thing about you?
 
Igor: [00:03:26] Well, so the most entrepreneurial thing, depending on how you define entrepreneurial or thing, uh, I suppose. So good entrepreneur, I think, has to be able to stand up after failing. In that way, I failed quite a bunch. And so, I think the entrepreneurial thing is that you stand up and you try again.
 
Lori: [00:03:48] I like that.
 
Nola: [00:03:49] Well, they say there is no such thing as failure, only lessons learned.
 
Igor: [00:03:54] Or failing forward.
 
Nola: [00:03:57] Fast CTO is a pretty unique company. For one thing, your company does very little in the way of actually building websites and apps. In fact, you're more about helping people with ideas find the right people to bring those ideas to fruition. Tell us about what your company does and what led you to start it?
 
Igor: [00:04:16] That's a great question. I've had a lot of startups. And I don't think I've had a single startup that was the same industry as a startup before or early in my career, basically, you look for a fun project and you don't really think about building on the previous thing and going forward. So, I've had failure after failure after failure, couple of minor successes. And then I ended up back in Boston after being in San Francisco for a bit. And I found this company that was, it grew out of staffing company. Right. So, they basically did the whole thing that everybody does. It disrupted the industry, all that kind of stuff in the staffing space. I started there as a first employee with two co-founders. It took nine years or so we finally built it up 120 people or so sold it several rounds of institutional investment, the whole journey. And I exited, I learned a lot, but the number one thing I learned is that I don't like staffing. You know, the way I define staffing is, you pay someone one thing, you bill them out at three X, that that's how you make your money. That's staffing. Most of the world works that way. But what it really means for startups and entrepreneurs is that anytime they go to find people to build something for them, instead of working with the people that they should be working with, they work with people they can afford, which are people at dev shops that are really getting paid three times less than what you're paying for them. And so, what ends up happening is a lot of times, and it's kind of a hypothesis that Fast CTO is built on is that if you go and you Google, you know, why do startups fail? And you get back a million different results, when you put in the pie chart, 80% of that pie chart, you could summarize as I spent too much money to build the wrong thing, and now I'm out of money. And there is like a lot of different ways you could walk into that statement. By the end of it, you had some amount of money, you tossed it over the fence to some dev shop and, you know, two, three months later you got nothing to show for it. So basically, Fast CTO, the idea behind it is, instead of doing that, bring along for the ride, somebody that's built a company very similar to yours already. They know exactly what the milestones should be, and they can direct a team of developers on exactly what they need to do and how, and so if we take a CTO like that and we make them affordable, that's where the magic.
 
Lori: [00:06:53] I love that. That kind of piggybacks on a question that I want to tie in here, which is. Fast CTO is more than just connecting the customer to the developer. Could you kind of help explain in giving it a better understanding? Because it's not just about finding a developer. I mean, if you're talking 70 K or you've got something that's even less, it's not just developers that you are connecting people to.
 
Nola: [00:07:21] Are there language barriers in trying to explain a concept that doesn't exist?
 
Igor: [00:07:27] Yeah. So let me answer Nola's question in exactly the way that you need your question to answer as well. The language barrier is not you're speaking English and they're speaking Ukrainian. The language barrier is that you're speaking non-tech and they need to hear tech. The analogy I often use is building a house. So, you can find the best contractor out there, like really, really experienced well-priced worthy contractor. And you could say, okay, I have this room, I need a window in this room. Without any other guidance, they're going to use their best judgment to put a window, right. They're going to pick a wall. They're going to pick a size; they're going to pick everything. And at the end, you're going to get a window and it's probably going to be well installed, right, because it's a good contractor. That's S O W. Cause on your SOW you’re going to say, I need a window, you know, I need login and you're leaving it to a developer to decide what that means, right? Now imagine if you gave a little bit more context. I need a window because I'm trying to grow some plants. Now you've got a contractor that says, okay, well, north is this way, west is this way. East is that way. You've got a hill over there. Best light is going to be. If I put a window on this wall. And they're going to put a window on the right wall. Still their choice, still their size, right. Whatever they pick, but at least it's on the right wall. Now let's say, you say, well, I'm growing this specific type of plant. They're like, well, for that kind of plant, we need this kind of glass because that kind of glass filters, UV rays. And then you say, oh, and actually I've got kids. And they say, okay, well now the window has to be like this. And actually, I also want to put TV in here. Well, now the window has to have shades and then just open and close. Right? So, the more information you give someone who's doing it, the better they're going to do at their job. And the problem is that, and it doesn't, it's not limited to non-tech founders. Most tech founders can't do this either. You don't know what the developer needs to hear to do the right thing. It's just unknowable because it changes every time. Even I get it wrong. You have to explain things in such a specific way for each specific thing that you're trying to solve. That's the language barrier. And that's where a CTO comes in. Like a real CTO that's done it before that can marry the business side and the tech side. And that's what we do.
 
Lori: [00:09:51] Cool. It almost sounds like you're a matchmaker. Except that you don't leave.
 
Igor: [00:09:56] Yeah. Yeah.
 
Nola: [00:10:00] Okay. Stay and hold hands.
 
Igor: [00:10:03] Lori, to answer your questions. Fast CTO is decidedly, not a dev shop. We don't sell developers, we don't sell development, but our mission in general is we don't profit off of startups.  Like Google us, check us out. But I don't stand to make any money off of it. I only stand to save you money.
 
Nola: [00:10:21] Very cool.
 
Lori: [00:10:22] Is there anything that you wish non-tech people knew or considered before they invested their time and money in getting an app or a software developed?
 
Igor: [00:10:35] A lot.
 
Lori: [00:10:36] Could you, could you narrow it down to a couple of the top ones? Yeah.
 
Igor: [00:10:43] I actually teach a class on this. It's called Product Development for an accelerator called Founder Institute. And I'm happy to add a link to the deck I use, but basically, look, SOWs are bad, developers speak a different language, both figuratively, and actually, sometimes. Any time, you try to engage someone that does this sort of thing, where they put a barrier between you and the developers, run the other way. So, like a lot of dev shops are this blended model where they say like, well, our developers are in India, but you have a local project manager, product owner. You talk to them; they'll talk to the developers. Run the other way. So, think about how real companies do it. That's what I always tell early-stage founders. A real, like CEO of an early-stage company. Like, let's say you have like 10, 15, 20 developers, you know who they are. . So, if you don't know who your developers are, if you can't talk to them, you're starting off on the wrong foot. Right? You don't want that. There's so much, nothing is free. Any dev shop that says like, oh, here's a blended rate. Like our project managers free, what you really need is two developers, QA, dev ops, and this and this and this, and let's try to build you a team, but you get free project management. It's not free. Right. They're just packing it all up by building your team you probably don't need. Give me a second. I'll come back with more.
 
Lori: [00:12:07] I think that's always that kind of, by the time people get to you, you could have saved them a lot of headaches, but then they didn't know that you existed, or some company like yours. Do you often consult with founders or people with ideas prior so that they really understand and educate themselves first? Or do people usually find you because of some other means?
 
Igor: [00:12:33] Most of the time, and this is a phrase I hear several times a day, is, where were you a year ago? So, a lot of times it's that. However, more and more people are coming to us first. We work with a lot of universities and accelerators and just various programs and know more and more way in an entrepreneur office as someone that knows the ecosystem and they say, hey, I want to build something. They say, hey, before you do anything, go talk to Fast CTO. And what's even more interesting, you know, both interesting and frankly, disappointing or sad in a way is women get taken advantage of a lot more by these scammy dev shops than male on. I don't have the numbers to know whether they waste more money or less, but there are certainly a bigger percentage of women that get scammed and men like per capita. And so, what's happening is if you're a female entrepreneur and you go to someone that knows what's up, they say, go talk to Fast CTO. And what that turned into completely unexpectedly is about 80% of our clients are actually female founded because basically a lot of folks that, uh, that are wherever they are in the startup community, in Boston and elsewhere, you know, they basically get sent to us.
 
Lori: [00:13:53] Well, that's why we brought you here because you make this approachable. And it's so intimidating. And then you add to that the while there are women making head roads in technology, it's still decidedly, favoring, male energy, more than female entrepreneurs. And we wanted to make. More accessible, more approachable. So, thank you for simplifying it.
 
Nola: [00:14:20] So you had talked about things that, you know, in hindsight, you wish people knew before they started an app. So, if somebody hasn't started yet, what would you say their first step should be? What is the thing they should do before they even think about hiring anyone?
 
Igor: [00:14:37] Do some market research, A find out what's out. If you find something similar, find the CEO on LinkedIn, everybody's happy to share. And so, if you have an idea, find out who's doing what in the industry. Most people are happy to share. There's enough room for everybody. Other people doing the same thing isn't scary. It means that there is actually a demand for it. So, it's fine. We'll figure it out. Then. call Fast CTO. We'll tell you whether you should spend money on this or not and how much. It's probably about $70,000. Unless it's something super simple,
 
Lori: [00:15:07] Then it's like $10,000.
 
Igor: [00:15:09] Honestly, rarely.
 
Lori: [00:15:11] Yeah.
 
Igor: [00:15:11] Very honestly, unless you're doing something super, super trivial or like you're very aggressive with what the M in MVP stands for, minimum viable product. It's usually not $10,000.
 
Nola: [00:15:23] And you were so right about there definitely being a market demand for apps. We've got a statistic here that according to Statista by the third quarter of 2020 Android had 2.8, 7 million apps to choose from an Apple users had 1.9, 6 million apps available. What does that? That's more than
 
Igor: [00:15:50] That's a smaller number than I expected honestly.
 
Nola: [00:15:52] Really.
 
Igor: [00:15:53] Single digit millions? I don't know if that's accurate. I
 
Nola: [00:15:58] Really?
 
Igor: [00:15:58] Honestly,
 
Nola: [00:15:59] there's way
 
Igor: [00:16:00] more apps than you think there's a lot more than that. Most of them are garbage, but there's a lot more than,
 
Nola: [00:16:06] Wow.
 
Lori: [00:16:07] Is hiring somebody to build an app and hiring somebody, a developer to build software or a software for service. Are you using the same type of developer, like thinking a developer one size fits all kind of background or are there specifics in that sense?
 
Igor: [00:16:28] It's more or less the same, but there are specific say again, back to my house analogy, right? Some contractors have more experiences with brick houses or wooden houses, houses on the hill, houses in your water. So, there's definitely differences between a website or a web app and an iPhone app and an Android app. You're looking for the same type of developers, but some developers prefer mobile, some developers prefer web. So, you need to put together the right team for the thing that you're building. And that's the attraction by the way of dev shops, right? Like for all the poop that I talked about dev shops, there's benefits there. They've got all these people under one roof; they could put together a team. Whereas if you're going solo, you have to like scrape together your own team.
 
Nola: [00:17:12] Speaking of which, if you were going to go and get something developed, which would be better, hiring a company such as a dev shop that has that specialty, or hiring a freelancer? And what are the pros and cons for each?
 
Igor: [00:17:27] Have you been reading my deck? So, I break it up into couple of different categories there, a technical co-founder. Right. Which is someone that you basically don't pay, they have equity. And the pro of that is they're bought in the con of it is if they walk out the door, it's messy. Sometimes legally, sometimes, you know, emotionally, whatever. And they are likely to walk out the door. If there's no revenue for a while, or if you don't raise, it's risky. The next kind of, and this is not hierarchical, they're literally like different threads of the same thing. Right? You've got something like a dev shop. A dev shop, they've got a business reputation, unless they're out the scam you, which 5% of dev shops are. Maybe it's a little higher So like, not most, but enough that it's an issue. So, dev shops, they have a reputation to uphold, but the way they make money is by charging like the same $40 developers I mentioned earlier, if you're paying $40 for a developer from a dev shop, that developer's making $17 to $21. Usually, the margins are about 60%. Sometimes a little higher, sometimes a little lower, but usually right around there. That's the con.
And then you've got freelance developers. Upwork I'm using as an example, the pro there is like, they want to please you and you're paying them by the hour usually. Well, they're happy to work. The problem is you're paying them by the hour, just like the dev shop. So, if you don't tell them exactly how to do something, they're going to invent the most complicated way to do it because it's in their best interest to do that. Usually. Not always. But usually. There have been successes with any one of those approaches. And there have been some horror stories with all three of those. And I'm not talking like out there in the ether. With me, I've had horror stories with the co-founders, with dev shops, with solo developers. And I've had successes with all three of them.
 
Nola: [00:19:27] If I were approaching a developer, a dev shop, how can I tell if somebody were trying to scam me? How can I tell if they're trying to take advantage of me?
 
Igor: [00:19:35] You can't. Not until it's too late. I mean, I've gotten scammed as recently as several months ago. So, it's, yeah, it's hard. It's hard. Like I have a better ear for it or eye or some body part, but it's still hard. And the problem is, the more junior someone is the more likely there are tell you that they can do anything you want. Right. Like, they've got a huge ego, they haven't failed too badly yet in their career, and they're like, anything you tell me, I can build it. And their heart might be in the right place. But if you hear that about every single thing you're saying, probably they can't. On the other end with a super senior developer, they'll start telling you, ah, you don't want to go down this path. Maybe I can build it, but maybe do this instead. Like really good senior experienced developers, they'll be a lot, I guess you could say negative. But in a good way in the way that you need them to be negative.
 
Lori: [00:20:29] This has been enlightening and helpful. Switching gears, just a little, well, actually a lot. We're going to table that part for the moment we love eating. And as a matter of fact, Nola and. Came up with the idea for our podcast over dinner, we thought it would be interesting to see what your personal favorite recipes are and how they reflect your experience and journey to successful entrepreneurship. Can you tell us about your two recipes?
 
Igor: [00:21:02] Sure. My first recipe is a mojito. Because a mojito is actually hard to make and no matter what anybody says, there's only one right way to make it. And if you want to make it, you'll fail the first time around. And the second and the third, and eventually is going to start tasting like a mojito. You have to make simple syrup, which is a whole process, but eventually you end up if you work hard at it, a mojito. I'll come back with how that links in the second.
 
Lori: [00:21:31] Okay.
 
Igor: [00:21:32] On the other side of the spectrum, I love making miso soup. And miso soup, you can make a million different ways. Experimentation is encouraged. You want meat? Great. You don't want meat fine. The only thing it must have as miso. Right. And water. Like I've made miso soup dozens of times, no two times the same exact way, and it is delicious every time. Uh, almost every time. Almost every time, right. And so, with the things you're doing, in whatever type of startup you're doing, like, there are some things like you've got to get right. There is no other choice. And you might get it wrong the first time around. On the other hand, there's things out there that you got to experiment with. You know, marketing. All that kind of stuff. There's no right way to do it. Every company is different and you're going to waste some money. Some of your miso soups are going to be not that great, but there's a lot of times you're going to end up with something that works. That's different from what you thought was going to work, and that's fine.
 
Lori: [00:22:37] That's great. That's very cool.
 
Igor: [00:22:39] I thought of that right before the show. I wasn't prepared.
 
Nola: [00:22:47] That is very creative thinking. Very creative thinking.
Moving on there, we asked you for one of your favorite quotes and you gave us a quote that is actually authentically your quote. And it's something you said you always say, and that is, "shortcuts are okay to take, as long as you know, you're taking them." So, can you tell us more about that and how it reflects your experience and journey to successful entrepreneurship?
 
Igor: [00:23:20] Yeah. The way of boils down on the technical side is, any entrepreneur, technical or non-technical, telling the developer go do something. When that developer is left to their own devices, to pick how they're doing it, they're going to take shortcuts that you're not aware of. They're going to make decisions that you're not aware of.
And sometimes those decisions will be right. But often they're going to be not right, but definitely not ones that you had any say in. And so, what ends up happening later is in the back of your head, you have some thoughts about here's what my company is going to be doing six months from now. Twelve months from now, 18 months from now that the developer doesn't know. And so, they're going to take some shortcut that puts you in a dead end. Right? So then in six months we'd be like, oh, I actually want to do this. And that developer, some other developers are going to say, oh, actually I have to rebuild this whole section in order to do that. But if you, if they had known, they wasn't built a differently. And back when they were building it, maybe it's a one-hour difference. A really good example that happens pretty often is like low code, no code type sites, right? Like there's a bunch out there like Bubble and et cetera. And they're great. I'm actually a big supporter of them for MVPs. If your MVP is the type of MVP that fits within their framework. But what often happens is you go down this path with, and I'm going to use Bubble just cause they're the most popular one. You go down this path, like I'm going to build this MVP. I'm going to use Bubble, for example. And you don't know where the boundaries are. You just looked up Bubble and you said, okay, it looks like they can do the thing that I want, but you don't know where you're going to be six months from now, 12 months from now. And so, I've seen plenty of success, stories of people using Bubble or something similar to build their MVPs and they're happy, and it's great, but I've seen way more examples of somebody that uses one of these local networks or frameworks built something and puts it out there. And the first client they have says, oh, this is awesome. I would totally pay for it if it had X. And you realize that you can't do that in Bubble. Or you can't do it in some other, your shared drive or whatever else. And now basically you just spent three months, even something like Bubble will cost you $20,000, $30,000 and you're in a dead end. You throw it out, start from scratch because you weren't aware of the limitations and you weren't aware of the shortcuts. And so, you don't want to be ever in that position. Meanwhile, it's perfectly okay to take shortcuts as long as you know, you're taking them and you basically say, okay, I know the right way to do it is this. I don't have time, I don't have the budget, the bandwidth, whatever, I'm going to do it like this, but I, I know the gap and I know how I'm going to bridge that gap when the time comes to it. You make sure that there's that bridge there. Or if it's not, you just made a conscious decision to go in this direction and never go in that direction. But you don't want to be surprised by that. That's expensive.
 
Lori: [00:26:27] Yeah, Igor all the information you've shared. I feel like should be in a checklist that somebody who has a, a non-tech person, or even at this point, a tech person who has an idea for a business model, because it's not just an app or a software solution. It is a business model should get in touch with you. So, can you tell our listeners how they can learn more about you, your company, the services that you provide?
 
Igor: [00:26:55] Uh, you should listen to the Sticky Brand Lab podcast.
So, I am a uniquely, the only person in the world with my name. You can Google me and you will absolutely find me. You could, find me on LinkedIn. You could go to fastcto.com, CTO for chief technology officer. You could email me igor@fastcto.com. My phone number is OK ring Igor. There's also seriously. There's all sorts of different ways to get in touch with me.
 
Nola: [00:27:30] Listeners. You can also get the links, details and information about Igor, his company, Fast CTO, the services they offer, and capture his motto by visiting our website at stickybrandlab.com/resources.
 
Lori: [00:27:45] Be sure to come back next Tuesday and every Tuesday for another informative, inspiring and motivating episode. And remember. Actions create results. So tap into your desire to create a business and brand you love by taking 1% action every day. Small steps, big effects.
 
Nola: [00:28:04] Do you have questions about creating a personal brand, side hustle or small business? Sign up for one of our clarity sessions. For more information, contact us at stickybrandlab.com/contact.
 
[OUT-TAKE]
 
Nola: [00:28:18] ….you love in as little as three hours a week.
 
Igor: [00:28:20] Three hours a week?
 
Lori: [00:28:21] Well, you're working on it.
 
Igor: [00:28:22] It's a big commitment.
 
Nola: [00:28:24] It takes about 30 years, but hey.
0 Comments



Leave a Reply.

    Ask Muse

    Get your questions answered and possibly featured on our podcast. Record or write your question and submit it below.

      Or, write question here

    Submit

    Archives

    January 2023
    December 2022
    November 2022
    October 2022
    September 2022
    August 2022
    July 2022
    June 2022
    May 2022
    April 2022
    March 2022
    February 2022
    January 2022
    December 2021
    November 2021
    October 2021
    September 2021
    August 2021
    July 2021
    June 2021
    May 2021
    April 2021
    March 2021
    February 2021
    January 2021
    December 2020
    November 2020
    September 2020

    Categories

    All
    Ask Muse
    DIY
    General
    Is It Worth It
    Mindset Reset
    Mom Boss
    Money Wise
    Subject Matter Expert

    RSS Feed

Copyright 2020-2023 Kelix Partners dba StickyBrand Lab
Terms of Use
Privacy Policy
Contact Us
  • Podcast
  • Ask Muse
  • About
    • Blog
  • Services
    • Be YOU-nique
    • Be Distinctive
    • Be Val-YOU-Able
    • Courses
  • Resources
    • Podcast Freebies
    • Recommended Biz Resources
    • Offers
  • Mindset Reset
    • Meditation & Inspiration with Cyndee Rae Lutz
  • Mini-Podcasts
    • How it Works
    • Sample Mini-Pods
  • Contact