Team aligned on moving immediately into website development with go-live targeted within two to three weeks. Frank approved overall design direction with only minor symbol adjustments pending from Andreas. Andy outlined realistic timeline: homepage completion in one day after receiving assets, full five-page review by next week, followed by one week for revisions. Development to begin in James's Webflow account using Relume framework, then transfer to Andreas's account pre-launch for domain connection.
Frank confirmed overall design approval with only small symbol changes pending from Andreas. Emphasized prioritizing go-live date over minor design tweaks, noting adjustments can be made post-launch.
James noted Will's design polish, particularly on backgrounds, confirming design maturity sufficient for development start.
Team agreed homepage will establish styling system to streamline development of remaining pages with similar layouts.
Andy outlined realistic development timeline: homepage completion within one day after receiving assets, with full review of all five pages targeted for next week, followed by one week for revisions.
Pages include homepage, individual journey, enterprise offering, about page, with blog and landing pages to follow later.
Development will use Relume Starter framework with rems and fluid typography for responsive design. Every section and style element will use classes to maximize flexibility and maintainability.
James committed to creating reusable components for complex UI elements like border widgets to simplify building and future adjustments. Team agreed on selecting fixed grid width to maintain layout consistency across pages.
Development to begin in James's Webflow account for speed, then transfer to Andreas's account pre-launch for domain connection. This staged approach balances development speed with reliable launch preparation.
Frank asked about bilingual setup complexity. James explained Webflow's localization add-on enables automatic AI translation and creates parallel page versions for easy editing.
Localization service involves monthly fee estimated between $18-30 per language. Premium plan includes IP-based automatic redirection to serve correct language version based on user location.
Andy confirmed technical feasibility and cost structure. This approach avoids complexity of managing separate sites and keeps all content centralized for easier updates and SEO benefits.
James recommended hosting blog content directly on website despite possible cross-posting on platforms like Substack, to centralize content and maintain SEO ownership.
Offered to create blog templates using existing design elements, making CMS setup straightforward and consistent with main site.
Frank confirmed need for blog and advertising landing pages after launch, emphasizing ease of use as critical factor.
James highlighted Webflow's WYSIWYG editor as user-friendly tool allowing Andreas and team to make ongoing edits without heavy technical skills. Proposed building modular page-builder blocks for drag-and-drop editing in future to empower non-technical users further.
Frank expressed caution about domain redirection due to past mistakes but confirmed experience redirecting domains, currently pointing to Odoo for existing site.
James reassured that connecting new Webflow site to domain will be straightforward once development is complete and ready to launch. Team will collaborate closely during transfer to prevent errors.
Andy cloned Relume framework and started working in James's workspace under project name "Sales Kung Fu."
Team agreed to follow up with Will and Andreas if no design asset updates received by next day.
Regular communication and responsiveness highlighted as key to meeting aggressive timeline, with James ready to assist on technical and process issues as needed.
James Redenbaugh
Development begins immediately in James's Webflow account once assets received from Will. Team to reconvene next week for full five-page review, followed by one-week revision period before go-live. Priority on maintaining aggressive timeline while ensuring quality through tight team coordination and efficient use of Webflow's component and class systems.
Team aligned on moving immediately into website development with go-live targeted within two to three weeks. Frank approved overall design direction with only minor symbol adjustments pending from Andreas. Andy outlined realistic timeline: homepage completion in one day after receiving assets, full five-page review by next week, followed by one week for revisions. Development to begin in James's Webflow account using Relume framework, then transfer to Andreas's account pre-launch for domain connection.
Frank confirmed overall design approval with only small symbol changes pending from Andreas. Emphasized prioritizing go-live date over minor design tweaks, noting adjustments can be made post-launch.
James noted Will's design polish, particularly on backgrounds, confirming design maturity sufficient for development start.
Team agreed homepage will establish styling system to streamline development of remaining pages with similar layouts.
Andy outlined realistic development timeline: homepage completion within one day after receiving assets, with full review of all five pages targeted for next week, followed by one week for revisions.
Pages include homepage, individual journey, enterprise offering, about page, with blog and landing pages to follow later.
Development will use Relume Starter framework with rems and fluid typography for responsive design. Every section and style element will use classes to maximize flexibility and maintainability.
James committed to creating reusable components for complex UI elements like border widgets to simplify building and future adjustments. Team agreed on selecting fixed grid width to maintain layout consistency across pages.
Development to begin in James's Webflow account for speed, then transfer to Andreas's account pre-launch for domain connection. This staged approach balances development speed with reliable launch preparation.
Frank asked about bilingual setup complexity. James explained Webflow's localization add-on enables automatic AI translation and creates parallel page versions for easy editing.
Localization service involves monthly fee estimated between $18-30 per language. Premium plan includes IP-based automatic redirection to serve correct language version based on user location.
Andy confirmed technical feasibility and cost structure. This approach avoids complexity of managing separate sites and keeps all content centralized for easier updates and SEO benefits.
James recommended hosting blog content directly on website despite possible cross-posting on platforms like Substack, to centralize content and maintain SEO ownership.
Offered to create blog templates using existing design elements, making CMS setup straightforward and consistent with main site.
Frank confirmed need for blog and advertising landing pages after launch, emphasizing ease of use as critical factor.
James highlighted Webflow's WYSIWYG editor as user-friendly tool allowing Andreas and team to make ongoing edits without heavy technical skills. Proposed building modular page-builder blocks for drag-and-drop editing in future to empower non-technical users further.
Frank expressed caution about domain redirection due to past mistakes but confirmed experience redirecting domains, currently pointing to Odoo for existing site.
James reassured that connecting new Webflow site to domain will be straightforward once development is complete and ready to launch. Team will collaborate closely during transfer to prevent errors.
Andy cloned Relume framework and started working in James's workspace under project name "Sales Kung Fu."
Team agreed to follow up with Will and Andreas if no design asset updates received by next day.
Regular communication and responsiveness highlighted as key to meeting aggressive timeline, with James ready to assist on technical and process issues as needed.
James Redenbaugh
Development begins immediately in James's Webflow account once assets received from Will. Team to reconvene next week for full five-page review, followed by one-week revision period before go-live. Priority on maintaining aggressive timeline while ensuring quality through tight team coordination and efficient use of Webflow's component and class systems.
00:00:02
Frank Kuhnecke: Andreas in a meeting. Are you.
00:00:26
James Redenbaugh: Hey, Frank.
00:00:28
Frank Kuhnecke: Yeah.
00:00:29
James Redenbaugh: How are you? Good to see you.
00:00:33
Frank Kuhnecke: I'm freezing.
00:00:35
James Redenbaugh: It looks cold.
00:00:37
Frank Kuhnecke: Yeah. And I have a wooden stove, but this is work. And the electric stove, I don't want to start, so.
00:00:50
James Redenbaugh: But you got a nice parker.
00:00:53
Frank Kuhnecke: That's. That's my outdoor parker. I bought the old I call this K medicine van and change it to office. So I'm traveling around and when I'm sitting inside.
00:01:15
James Redenbaugh: Cool van.
00:01:18
Frank Kuhnecke: Life sounds fun when office nice because sitting in the same room for the whole day, it's. It's not for me. So I'm driving to any nice place and do my office work over there.
00:01:36
James Redenbaugh: Very cool. Hey, Andy.
00:01:40
Andy Bittner: Hey guys.
00:01:43
James Redenbaugh: How are you today?
00:01:47
Andy Bittner: Doing better, but still not 100%. Yeah, still sweating and cold and like changing around all the time, but it's getting better.
00:02:02
James Redenbaugh: Oh man. Do you have access to a sauna?
00:02:07
Andy Bittner: No, unfortunately not.
00:02:09
James Redenbaugh: Might be sweating enough without it.
00:02:12
Andy Bittner: Yeah, it feels like it. I also heard it's good to like even sweat a bit more because when you get out the bacteria and everything, virus, whatever.
00:02:25
James Redenbaugh: Yeah. My wife and I have a sauna blanket which is like a heated sleeping bag. You feel like a hot Pocket going inside it and it's kind of gross. I think it's kind of gross because it's just like plasticky. But it heats you up like a sauna and you can sweat it out. It's very efficient.
00:02:51
Andy Bittner: Yes, that's great. Way more efficient in regards of like energy and room you need than having a real one.
00:03:02
James Redenbaugh: Yeah, yeah, definitely. It's not fun to do together though, unfortunately.
00:03:16
Andy Bittner: Oh, the reason it comes in.
00:03:20
James Redenbaugh: Yeah, we're just waiting on Andreas.
00:03:34
Frank Kuhnecke: I'm not sure whether he will meet us. He told me something about his appointment and maybe later. Don't know really.
00:03:55
James Redenbaugh: Okay.
00:03:57
Andy Bittner: Did we get any update from Will in regards of website like design and assets?
00:04:17
James Redenbaugh: He didn't respond to the email and I don't see anything new in the figma, I don't think.
00:04:31
Andy Bittner: Oh yeah, I don't see anything else either. Looks the same like yesterday.
00:04:43
James Redenbaugh: So. Yeah. But I know we're all eager to get moving into development. I'm going to share my screen here, so we're all looking at the same thing. Frank, if you. If you tell us that you're happy with the overall design here, then you know, and we can get Andreas's confirmation later today and then maybe see any updates that Will has or he comes online. We really just Need a sign off right now to. To move into development. And then, Andy, I wanted to talk to you about development strategy and how we want to handle that and get your sense of how long things should take from here.
00:06:29
Andy Bittner: Okay. Yeah.
00:06:35
Frank Kuhnecke: Overall I'm fine. Andreas had an idea to change some of the symbols. I had one idea maybe to change it, but this is all small stuff, so overall I'm fine.
00:06:55
James Redenbaugh: Cool.
00:07:00
Frank Kuhnecke: And now I'm interested mostly in Go Live.
00:07:05
James Redenbaugh: Yeah.
00:07:07
Frank Kuhnecke: Because some small things we can change afterwards. For example, one gate or something like this.
00:07:17
James Redenbaugh: Yeah. Yeah. I think that. I think a lot of this is updated or. I don't know if I just haven't. Haven't seen the updates, but it looks like Will's put a lot of work into. Into polishing things here. I really love his background.
00:07:40
Andy Bittner: I think so.
00:07:41
Frank Kuhnecke: This is the same I saw last week.
00:07:44
James Redenbaugh: Okay.
00:07:47
Andy Bittner: Maybe I didn't see the bottom stuff yet. I think it's the first time I see it with the trees in the background or proven results. Or maybe I didn't see it last time. I know. Caught my eye right now.
00:08:06
Frank Kuhnecke: I've seen this picture so often, so I can't say what I have seen and whatnot.
00:08:13
James Redenbaugh: Yeah.
00:08:18
Frank Kuhnecke: But the overall look is fine. The principles of the page are fine for me too.
00:08:30
James Redenbaugh: Great. So, Andy, I think that we should start building. It'll be helpful to have the Illustrator file. Some will.
00:08:46
Andy Bittner: Let's just do images, backgrounds.
00:08:48
James Redenbaugh: Yeah.
00:08:49
Andy Bittner: Icons and stuff.
00:08:51
James Redenbaugh: Let's build in my webflow account, if it's okay with you. You sure you have access in there?
00:09:01
Andy Bittner: And.
00:09:06
James Redenbaugh: Or we can start a. Actually, I wonder. Let's see where Andreas's site is.
00:09:20
Andy Bittner: Sorry.
00:09:21
James Redenbaugh: Maybe we should just both be added to Andreas's site.
00:09:26
Andy Bittner: Google. Okay.
00:09:28
Frank Kuhnecke: He's been called.
00:09:31
James Redenbaugh: Okay.
00:09:34
Frank Kuhnecke: I have one question about Figma to do it B. Lingual. Is it complicated? Because we already need it. In German too.
00:09:47
Andy Bittner: Of course.
00:09:50
James Redenbaugh: Yeah. Good question. So in webflow there's. There's. They call it locals and it's very easy to add. And then it uses AI to translate everything into a new language. It automatically creates a second version of the page or third or fourth, depending on how many languages you add. And then you can go through and edit all the content. So it does a pretty good job of automatically translating. And then you andreas can go in and edit yourselves to tweak things in German.
00:10:29
Andy Bittner: Right?
00:10:29
James Redenbaugh: Fine.
00:10:30
Andy Bittner: Yeah. Yeah.
00:10:37
James Redenbaugh: Is that an accurate description, Andy?
00:10:42
Andy Bittner: Yep, that's it. It's just like. You just have to pay for it. Yeah, that's the only. Yeah.
00:10:48
James Redenbaugh: There's a monthly.
00:10:49
Andy Bittner: So webflow is charging a monthly extra add on price for it and then you can like decide between the, it is the redirection between the IP redirection. You know what I mean? You have to pay extra. If you, if you take the premium plan for local, then it will recognize your IP and your, where you're at. Like if you're in Germany or if you're in outside of Germany and if you're IP is German, it will automatically forward you to the German side. If you're outside of Germany, it will forward you to the English side. Oh, but you don't have to take it. It's like, I think there are two price plans. I just don't know the exact pricing right now, to be honest. I think it's like 18 bucks or something for the normal one and 2530 or something for the other one.
00:11:43
Frank Kuhnecke: Okay.
00:11:47
Andy Bittner: And it's per language, but you only have one language, so.
00:11:51
Frank Kuhnecke: Okay.
00:11:54
Andy Bittner: Cool.
00:11:55
James Redenbaugh: So Andy, let's start building on my webflow account and when we're ready to go live or at any point before that, we can transfer to Andreas's account where it'll, it will probably live and that's where we'll connect the domain. But let's stay in tight coordination as we start building here. And I'd love for you and your team to, to. To do first what's easiest for you and not get hung up on details and effects. And then I want to assist with making things go as smoothly as possible. And I can also, I'm good at finding creative solutions for difficult things. So like these, yeah, these border widgets and stuff like that, I can create a component for those kind of things that we can just drop in as we need them and stuff like that. And we should, when we build the home page, let's bring as much thinking as we can into the different components so that we can reuse all of these things on other pages. So yeah, you know, maybe we number the backgrounds here and we use those numbered classes like, you know, this can be background one. So then on other pages, if we want a section with this background, we have that ready to go. You know, three column thing here, three column thing there. And then also if there's like small discrepancies, I think that we should pick a, a grid width and stick with that. So like these kind of come out a little bit more. These are go in and I think that we should.
00:14:34
Andy Bittner: Do you want to keep it like that or should we Just have everything.
00:14:36
James Redenbaugh: Inside the inside of it, everything inside the grid.
00:14:42
Andy Bittner: Because normally we work with the, with the relume starter. It's like the client first framework and so everything has like it's framework, you know, every section, every padding, every whatever. It's like, it's like a class and if you change something, it changes everywhere. If you want a different one, you choose a different class. If you want a different padding, you choose a different class for the padding. Sometimes it's annoying, but sometimes you just use your own custom classes to make it easier or like. Yeah, so it works better. And if you want to use components, we could also try to. I think you can even change classes with like a drop down or something for the components. If you really use components like that. Or we just use classes where I.
00:15:33
James Redenbaugh: Think mostly classes components for repeated elements, you know, of course, like header footer, whatnot. And then we can use them for these elements.
00:15:45
Andy Bittner: Every section has its own class and every style element has its own class and everything.
00:15:54
James Redenbaugh: And then remind me what reloom. What units the. The reloom system uses? Is it rams?
00:16:04
Andy Bittner: Yep, it's ribs.
00:16:06
James Redenbaugh: Okay.
00:16:07
Andy Bittner: And there's also. I also use the fluid for typography so it's always calculating based on the screen width. Cool.
00:16:19
James Redenbaugh: Great.
00:16:23
Frank Kuhnecke: Great. You may speak Latin.
00:16:25
Andy Bittner: Frank is like whatever you just talked about.
00:16:35
Frank Kuhnecke: James, you would assist me for redirecting the page if you are ready.
00:16:41
James Redenbaugh: Yes, when it's ready we can connect.
00:16:43
Frank Kuhnecke: The domain super easy because I redirected already to Odoo for the version now and I've heard you can make so many mistakes and I won't try them all.
00:16:57
James Redenbaugh: Cool. Yeah, it's pretty straightforward. When we're ready to do that.
00:17:06
Andy Bittner: Okay, great.
00:17:09
James Redenbaugh: Cool. And yeah, I want to see if Will has what he has for the other pages that we're discussing. But I'm assuming the, I'm sure that the designs don't deviate dramatically from the homepage and so if we can nail the system and the styles on the homepage, those other pages should go pretty smoothly. Andy, what's a realistic time frame from here on out? How soon do you think that we can go live with this?
00:18:10
Andy Bittner: I think we can do the homepage as soon as we get the assets. It's maybe one day get the homepage done, everything goes smooth, we can have a look at like it's. All the pages we have is in the Google Doc, right? The home page, individual journey page, enterprise offering, about page. That's Right. It's not more than five pages. So I think we can do it until next week to have a review. Great. And then maybe another week for like small revision stuff.
00:18:41
James Redenbaugh: Yeah, tweaks. And these guys can the language depending.
00:18:51
Andy Bittner: On revision and communication.
00:18:56
James Redenbaugh: Cool. Andres mentioned in his email a question about blog and substack and things like that. I tend to recommend if people do something like substack or medium to also have the content on their website to just double publish can be helpful to. To put things out there in their own format. But it's so easy to create a content management system in webflow and have everything in one place. I think you should use that. And we can make a template page for that pretty easily with these elements that. That. That shouldn't be a problem. So if he checks out the recording, he can hear that suggestion here. Anything that you would add to that, Andy?
00:20:02
Andy Bittner: No, it's just what you said. Yeah, really easy.
00:20:10
James Redenbaugh: Cool. Okay, great. I can't wait to have this up and working for them. Frank, is there anything else we should talk about while we're here?
00:20:26
Frank Kuhnecke: No, no. If we're installing the blog, how to do this we will do afterwards if it's ready. We must be sure that we are able to use it.
00:20:45
James Redenbaugh: Yeah. So Andreas already has a webflow site that I built for him probably three years ago and he manages that himself and he should know what to do with that. So I imagine that this site will live next to his and he'll have the same access he has to that. And you know, of course if you guys want to do something more complicated in the future or add a new feature or things like that, we can always come back to it. But you know, edits, tweaks, duplicating a page, making changes. Andrea should know how to do that.
00:21:26
Frank Kuhnecke: We need blogs and maybe we need some landing pages for some advertising and that's fine. If it's as easy as the other programs. I know we will take it.
00:21:45
James Redenbaugh: Cool. There's. You know what I love about webflow is we can't. It's complex enough for us to do anything and there's definitely. If you're working in the designer, there's a bit of a learning curve. But the. The page editor is super easy, simple, wysiwyg, straightforward and. And if you guys are doing a lot of like iterating of templates and you know, or trying a bunch of different things out and you guys want to do that yourselves, we can actually build kind of building blocks for you. Page builder blocks so that you can play with those, drag them around like Squarespace or something like that. But we should talk about that down the. Down the road, if you have.
00:22:48
Frank Kuhnecke: If you can see it live. Yeah, I think it's better.
00:22:51
Andy Bittner: Yeah. Yeah.
00:22:53
Frank Kuhnecke: Caching seldom is useful.
00:22:56
James Redenbaugh: Yeah. Cool.
00:23:00
Andy Bittner: So I actually just cloned the framework and created a new site in your workspace. I called it Sales Kung Fu. Great. Yeah, I started working in there.
00:23:12
James Redenbaugh: Awesome. Okay, guys, well, I think that's all we need for today. And hopefully we'll hear from. From Will andres later on.
00:23:33
Andy Bittner: Yep, hopefully. Otherwise, we have to follow up tomorrow.
00:23:37
James Redenbaugh: Yeah. Alrighty, guys. Take care. Talk to you next week.
00:23:45
Frank Kuhnecke: Talk to you next week. Fine.
00:23:47
James Redenbaugh: Ciao.
00:23:47
Andy Bittner: So next week. Bye. Bye.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
Unordered list
Bold text
Emphasis
Superscript
Subscript
.svg%20(1).png){kind=icon}
.png)
