00:19:22 · Evgenii Tilipman, Ezekiel Iferia
[00:19:22] S1: I would say number one, if I saw a lot of agencies that were saying yes to everything. And then it turned out to be a very bad experience. Even when we were starting when we had like three people, we were saying yes to a lot of things that thinking about it now I should have said no to. And the problem of saying yes to everything is that number one, you're being overworked, the whole team is being overworked. Sometimes you cannot even deliver the service, but you think that you're going to find someone to deliver it for you like white label. And the issue with that I see is you're going to be burnt out. You're going to have to hire a new person that you don't have enough margin for, so it's not going to be financially wise. And the clients are going to hate you for saying that you can't do it when in fact you couldn't have. So look out for that red flag if the company is saying yes to everything and if they aren't really setting any boundaries, that's a big problem. Obviously, there's a pricing thing. If the company seems to give you an offer that sounds too good to be true, it probably is. And let me give a third red flag being if there's a lack of transparency in the processes, you better run. [00:20:56] S0: All right. That was a very insightful one. So, you know, what's something, you know, what's one thing clients don't ask, you know, that they always wish they had?
00:20:56 · Ezekiel Iferia, Evgenii Tilipman
[00:20:56] S0: All right. That was a very insightful one. So, you know, what's something, you know, what's one thing clients don't ask, you know, that they always wish they had? [00:21:07] S1: Well, to be frank, I don't really think that there is something they don't ask. It depends on case by case basis. What I always try to do is I try to ask as many questions as possible just to make sure that we are not running into some issues of ignorance. And then when we ask certain questions, clients sometimes remember certain things that they have forgotten and it just helps out a lot. So the goal is always to over communicate, try to get as much info as possible. And oftentimes I just say, hey, we are going to ask a lot of questions. They may sound dumb to you, but trust me, we need to know these things so that we are not delivering subpar work. And oftentimes they're understanding because obviously we have not been in their business for a long time. They do not expect us to know their business as well as we do like our own. And it just makes sense that we're ask silly questions that are part of regular onboarding. [00:22:27] S0: Evgenii, you are a Webflow agency. So I'd like to know why Webflow for b to b SaaS instead of WordPress, Framer, or custom build?
00:22:27 · Ezekiel Iferia, Evgenii Tilipman
[00:22:27] S0: Evgenii, you are a Webflow agency. So I'd like to know why Webflow for b to b SaaS instead of WordPress, Framer, or custom build? [00:22:42] S1: And that's a great question. And you kind of got it right, but also got it wrong. So on our site, you'll see there's a service page called Webflow Development Agency. That's the core thing that we deliver, right? We do Webflow development. But also we are not really technology based. We don't care about, I mean, we do kind of care about the technology, but we have done Webflow websites, we have done Framer websites, we have done WordPress websites. And as of recently, we have started doing custom development. We have migrated our own websites to Next. Js and Sanity CMS. And we are now in the middle of a couple of migrations that are going to be in Astro, which is another custom tech stack. [00:23:37] S0: So Evgenii, when should a startup build custom and when should they definitely not?
00:23:37 · Ezekiel Iferia, Evgenii Tilipman
[00:23:37] S0: So Evgenii, when should a startup build custom and when should they definitely not? [00:23:45] S1: It always depends of internal capabilities. Like in example, if you do not have an in house person who is going to actively manage the website that you know and trust, so the person that's not gonna leave in a month or two, and the person who is technically capable enough to figure things out, in that case, you can go custom and power the website using some sort of agentic development such as Claude Code or Codex or anything else, right? But otherwise, you've got this is gonna sound silly, but if you've got a more like a Karen for marketing director who's not really great with computers, then some sort of visual builder may be a better fit. Once again, I'm now learning that that may not necessarily be the case, but that has been the case in the past. We really did like Webflow for that specific reason. The CMS was great. A lot of people knew how to use it. And it was just a pleasant experience to interact with, which is feedback we got from a lot of our clients. Now that we are doing more of custom builds, I do believe that this feedback will change. I mean, will tell. But yeah, hope that makes sense. [00:25:17] S0: Absolutely, absolutely. So, you know, you've launched sites for AI Webdillion enterprise SaaS. So what's different about marketing websites in those categories compared to traditional SaaS?
00:25:17 · Ezekiel Iferia, Evgenii Tilipman
[00:25:17] S0: Absolutely, absolutely. So, you know, you've launched sites for AI Webdillion enterprise SaaS. So what's different about marketing websites in those categories compared to traditional SaaS? [00:25:33] S1: I think that the biggest things are the scale of their web operations and the sales process. The larger the company is a lot like the more processes that those companies have. It also means decisions or novelties are being introduced on a lot slower basis. But other than that, I don't think that things are much different for us at least as service providers. [00:26:10] S0: So before we wrap things up, when it comes to building a website, what's something that works well for AI startups that really wouldn't work for Web3 and, you know, vice versa. I mean, you do what... The other way around, what's something that would work for Web3, but wouldn't work well for AI startups?
00:26:32 · Evgenii Tilipman
[00:26:32] S1: That's a great question. So for Web3, what we found is you need to build a lot of trust more than probably anywhere else because Web3 is still associated very heavily with scams, NFTs and things that are kind of shady when in fact, for us at least we have worked with finance based companies that are just working with blockchain technology. Those are very different. There are a lot of use cases with blockchain, but whatever you do, there's a lack of trust in the industry. So it's all about building trust as much as possible. And if you gave as many trust factors in AI website, people would just find that silly because target audience is very different, right? In terms of AI companies, the thing that really I'm noticing works well is people are focusing on a lot of novel features such as like AI summaries, such as this... Let me actually find the website. It's called parallel.ai and this website has a very cool feature which is for humans and for machines and you can toggle in between those two views. So for humans, it's kind of a very beautiful website. It has a lot of visual assets and for machines, it's just like a dark screen with a bunch of links, a bunch of source code and it is exactly what it sounds like. It's part of the website that is... It's kind of a feature made specifically for machines so that crawlers can easily crawl it. I would say it's very innovative. I do not see a lot of companies do something like that. And that's the point of AI. You try as many new things as possible, whereas for blockchain, you try to avoid that. You try to make things as trustworthy as possible. Unfortunately, those don't go hand in hand. Those are sometimes conflicting with each other, but that's that's how it is.