


James joined from Lisbon, Portugal, having just arrived for the Hollow Movement conference — a gathering focused on consciousness, cultural evolution, integral theory, and quantum physics (02:58). The conversation pivoted quickly into a candid review of the Light Creators engagement, project delays, and a strategic direction shift toward AI-assisted hybrid web development.
David opened directly with his dissatisfaction about how the engagement has unfolded (07:30). The original timeline anticipated a mid-February launch that would support a marketing campaign leading into a May retreat. As of late May, key pieces remain incomplete, and David had to cancel his retreat plans as a result.
David framed the conversation around mutual learning: what's each side's understanding of the value exchange, and what would feel fair given the delay?
James acknowledged the project turned out significantly more complex than originally scoped (10:10). His reflections:
The core insight: what's actually being delivered isn't a number of pages but the journey taken with the client within a defined time container. Future engagements need to honor that time container regardless of whether it produces ten small pages or one large page with complex functions (15:12).
The original project budget was $9,500, with a $2,850 deposit already paid. The payment schedule assumed a clean design-then-development cascade that didn't materialize (22:32).
James's position: He wouldn't feel right charging the full amount given the incomplete state, even though his actual hours exceed the budget. He's open to a reduction and wants David to feel he received the value paid for.
David's proposal: A reduction of roughly one-third of the total volume — landing somewhere around €6,000–6,500 total — would feel good and preserve willingness for future collaboration (32:39). David was also open to creative/barter arrangements, particularly if James helps bring a new Claude-generated landing page online.
James will consult with Andy before confirming timelines and finalizing the reduction offer.
To close out the current engagement cleanly, the agreed outstanding items are:
David committed to no new landing page requests during this wrap-up phase.
James introduced his evolved team approach (24:30). Losing Yvonne earlier in the project meant too much fell on James directly. The new structure includes:
Andy will be the primary point of contact for completing the remaining work. James acknowledged a personal development edge around managing expectations and pushing back when client requests would impact timelines — something he was perhaps too accommodating about throughout this project (31:18).
[technology="Collaboration Management Tools"]
The conversation's most generative thread emerged when David shared an HTML prototype he built with Claude [tag="claude"] — a "Five Pillars of a Flourishing Life" landing page (Vision, Belonging, Accomplishment, Health, Becoming) in German, reflecting his somatic heart-call vision (37:18).
James explained his evolving approach (36:13):
James recommended:
davidlebnow.com/flourishing-life, with the option to mirror it on another URL if David's partner Angelina wants a separate identity.James can take David's HTML files (one version for Jung & Lijia / youth, another for Eldon / parents) and embed them on a Light Creators URL within minutes as a quick publish — or invest more time to make them fully responsive and properly integrated.
[technology="Communication Automations"]
James
David
James joined from Lisbon, Portugal, having just arrived for the Hollow Movement conference — a gathering focused on consciousness, cultural evolution, integral theory, and quantum physics (02:58). The conversation pivoted quickly into a candid review of the Light Creators engagement, project delays, and a strategic direction shift toward AI-assisted hybrid web development.
David opened directly with his dissatisfaction about how the engagement has unfolded (07:30). The original timeline anticipated a mid-February launch that would support a marketing campaign leading into a May retreat. As of late May, key pieces remain incomplete, and David had to cancel his retreat plans as a result.
David framed the conversation around mutual learning: what's each side's understanding of the value exchange, and what would feel fair given the delay?
James acknowledged the project turned out significantly more complex than originally scoped (10:10). His reflections:
The core insight: what's actually being delivered isn't a number of pages but the journey taken with the client within a defined time container. Future engagements need to honor that time container regardless of whether it produces ten small pages or one large page with complex functions (15:12).
The original project budget was $9,500, with a $2,850 deposit already paid. The payment schedule assumed a clean design-then-development cascade that didn't materialize (22:32).
James's position: He wouldn't feel right charging the full amount given the incomplete state, even though his actual hours exceed the budget. He's open to a reduction and wants David to feel he received the value paid for.
David's proposal: A reduction of roughly one-third of the total volume — landing somewhere around €6,000–6,500 total — would feel good and preserve willingness for future collaboration (32:39). David was also open to creative/barter arrangements, particularly if James helps bring a new Claude-generated landing page online.
James will consult with Andy before confirming timelines and finalizing the reduction offer.
To close out the current engagement cleanly, the agreed outstanding items are:
David committed to no new landing page requests during this wrap-up phase.
James introduced his evolved team approach (24:30). Losing Yvonne earlier in the project meant too much fell on James directly. The new structure includes:
Andy will be the primary point of contact for completing the remaining work. James acknowledged a personal development edge around managing expectations and pushing back when client requests would impact timelines — something he was perhaps too accommodating about throughout this project (31:18).
[technology="Collaboration Management Tools"]
The conversation's most generative thread emerged when David shared an HTML prototype he built with Claude [tag="claude"] — a "Five Pillars of a Flourishing Life" landing page (Vision, Belonging, Accomplishment, Health, Becoming) in German, reflecting his somatic heart-call vision (37:18).
James explained his evolving approach (36:13):
James recommended:
davidlebnow.com/flourishing-life, with the option to mirror it on another URL if David's partner Angelina wants a separate identity.James can take David's HTML files (one version for Jung & Lijia / youth, another for Eldon / parents) and embed them on a Light Creators URL within minutes as a quick publish — or invest more time to make them fully responsive and properly integrated.
[technology="Communication Automations"]
James
David
Homepage drafts blending copy with preliminary graphics established. Hero messaging focuses on 'leadership from presence, not pressure' targeting conscious founders at transformational thresholds. Visual system developing around vertical/horizontal lines with circles symbolizing presence and leadership. Integration of mountain imagery as grounding metaphor to balance cosmic spaciousness with earth connection. Black and white compositions with natural (non-AI) qualities preferred. Standout image discovered: natural landscape with circle, vertical horizon, and horizontal line in Dao/yin-yang configuration. 6-8 core page designs in development with integrated copywriting approach. German-primary content strategy during proof-of-concept phase. Landing Page architecture refined: LP1 serves as initial touchpoint from social/podcast discovery; LP2 delivers quiz results with data visualization and introduces email course (now identical for English and German with both getting email course access). LP3 copy due Friday. Seven customized LP2 variations based on quiz results (logical visionary, quiet powerhouse, etc.) with same structure but personalized content (53:30). lightcreators.com functions as focused conversion funnel (quiz-centric), davidliebnau.com as broader personal brand site (49:52). Mallorca photo suite available for incorporation (57:50). March 1st launch deadline established (47:31). Copy development substantially advanced: LP1 (one-on-one offer) English & German complete except testimonials; LP2 (email course) complete; LP3 (group offer 'The Threshold') English & German complete; Resonance offer complete; davidliebnau.com homepage ready; podcast page nearly complete by Thursday; webinar waitlist page complete and in production (26:42-35:27). Design drafts now shared as Webflow preview links via WhatsApp for asynchronous review (46:09). davidliebnau.com homepage structure finalized: sections include How I Work, About David (incorporating Vision Quest), Experience, Testimonials, and Take Action CTA. 'Who is this for?' section removed as redundant for personal brand context (40:15). Navigation to function as anchor-link quick-orientation tool; Podcast nav item routes to dedicated page rather than homepage anchor (41:00, 44:31). Photo integration work underway: hero image background rework to unify David with concentric ring design (10:06); specific photos mapped to Discovery Call page sections — 'I See You' as hero, 'Feedbacking' for feedback section, 'Q&A Call' for details section (13:06); retouching planned for eye area freshening and photographer reflection removal (14:20, 28:27). Product naming update: 'Solo' is now 'Shift'; 'Notion Operating System' is now 'Solo' — requires update across all design materials (46:23). davidliebnau.com personal site hero section receives positive feedback with 'the update that makes all other updates possible' tagline (01:39). Social proof placement discussed: HR Excellence Award logo requires SYNC Group attribution (02:05); Proven Expert logo (4.98 rating) available only in German and behind upgrade paywall (06:01). Classical antique-flavored iconography appreciated but concern raised about communicating cutting-edge positioning; agreement to bring modern/technical icons higher on page for earlier contrast (12:31-15:18). New section planned: Truth/Presence/Connection three principles between five pillars and 'Leadership begins within' using vertical/horizontal circle visuals from earlier Figma work (19:33-23:54). Testimonial portrait photos to be sourced from LinkedIn and uploaded to Google Drive (33:46). HR Excellence Award logo to be added near SYNC Group reference (28:11). Podcast page cover art and hero imagery under discussion; speaking-action shot questioned for similarity to main hero and mid-word capture; alternatives to be marked up (35:02-41:00). Entrepreneur/Manager/Expert iconography to be replicated on podcast page (42:30). Photography strategy: shuffle 'solo hero' image to Solo page hero, use 'reserved smile' portrait as closing image on davidliebnau.com (48:09). Publishing decision: suboptimal landing page online beats no landing page; domain connection and publish targeted for Monday after weekend (49:44-53:07). Project significantly delayed from mid-February timeline, now incomplete as of late May (07:30). Scope evolved from cohesive single website to discrete, refined landing pages with multiple iteration arcs (10:10).
Technical implementation of lightcreators.com and davidliebnau.com as separate entities. Decision made to build Light Creators site from scratch rather than developing on top of previous junior-built site; old site remains accessible for archival reference (31:51). lightcreators.com serves as focused conversion funnel with quiz-centric architecture; davidliebnau.com functions as broader personal brand site with trust-building content about David's background (49:52). Phased approach: (1) lightcreators.com funnel pages (LP1-3) by March 1st, (2) davidliebnau.com personal brand site and podcast page, (3) deeper offer-specific landing pages for paid products (47:31). Bilingual structure setup, CMS configuration, content migration. Gantt chart timeline and Kanban board to be created organizing each page's content, design, and development phases. First landing page represents hardest lift; subsequent pages accelerate once design system established (51:43). Mallorca photo suite to be incorporated. Design drafts shared as Webflow preview links via WhatsApp for asynchronous review (46:09). Webinar waitlist page in production with German/English versions; mobile optimization needed (logo sizing, scroll-to-form CTA at 49:16). MailerLite form integration for email capture with account access granted during session (55:53). Homepage structure refined: sections include How I Work, About David (incorporating Vision Quest), Experience, Testimonials, and Take Action CTA. 'Who is this for?' section removed as redundant (40:15). Navigation tabs to function as anchor links for quick orientation (37:32). English version routes directly to Podcast page rather than embedding podcast section on homepage (44:31). Hero image background rework in progress to better integrate David into scene and unify with concentric ring design (10:06). Photo retouching underway for Discovery Call page with specific image-to-section mapping. Product naming update: 'Solo' is now 'Shift'; 'Notion Operating System' is now 'Solo' — requires propagation across all materials (46:23). Social proof section to be bolded and repositioned higher on hero (05:18). Modern/technical icons to be brought up earlier in page flow (15:18). Truth/Presence/Connection principles section to be added between five pillars and 'Leadership begins within' (23:54). HR Excellence Award logo to be integrated near SYNC Group reference (28:11). Testimonial photos to be added once David uploads to Google Drive (33:46). Podcast hero image alternatives to be marked up (40:32). Entrepreneur/Manager/Expert iconography to be replicated on podcast page (42:30). Discovery call video to be added when received (45:41). Solo page hero image strategy: swap 'solo hero' and 'reserved smile' placements (47:50). Podcast blog blocks to be integrated (52:34). Domain connection (davidliebnau.com) and publish targeted for Monday after weekend wedding (53:07). Project significantly delayed from mid-February timeline, now incomplete as of late May (07:30). Team member Andy Bittner (Munich-based, German-speaking, on David's timezone) will be primary point of contact for completing remaining work (24:30). Strategic pivot: davidliebnau.com recommended to move to fully AI-managed custom code architecture using Claude + GitHub for maximum flexibility, while lightcreators.com stays on Webflow due to quiz infrastructure (36:13-58:55). Remaining deliverables: davidliebnau.com finalization, podcast page, solo page with Calendly integration, qualitative review pass, Webflow training (29:07).
00:02:58
David Liebnau: Hello. Hello, James.
00:03:01
James: Hi, David.
00:03:03
David Liebnau: How are you doing?
00:03:06
James: I'm doing pretty good. I'm tired. We flew all night last night, and I just got to our hotel. Beautiful place here on the ocean.
00:03:19
David Liebnau: What brought you to Paris? Portugal. What kind of conference are you participating, if I may ask? I'm curious.
00:03:34
James: Yeah, it's called the Hollow Movement. I'll send you. I'll send you a link to it.
00:03:39
David Liebnau: Hollow Movement. Okay. Yeah. And. And what is it about? In. In like, your own terms or understanding? What. What is it about?
00:03:56
James: It's kind of like consciousness meets cultural evolution and collective action and integral theory and quantum physics. It's lots of different things. Yeah. Lots of different things together. Very progressive, fun and creative and upbeat, and lots of different movements involved. It's like they want to be a. Or different networks, different partner organizations. All kinds of things. Yes. Not really. I'm just. Yeah, go for it. Yeah, sure. Okay. They think that I'm here at an official table, but I'm just trying to work here.
00:05:01
David Liebnau: Cool. Okay, well, so you. You made yourself already home. You found a home office. That's cool. And then the honeymoon goes from there, or you gotta go through, travel back to the U.S. no, you. You. Where did you go? You intend to go then? From. From. And is it Lisbon now, or. Or where.
00:05:21
James: Yeah, we're in Lisbon now, or outside of Lisbon. And then from here we'll go to the Azores. In the Atlantic.
00:05:33
David Liebnau: Yes. Okay.
00:05:35
James: Yes.
00:05:36
David Liebnau: And they are. They belong to Portugal or Spain?
00:05:40
James: Portugal.
00:05:41
David Liebnau: Ah. Yeah. Well, you know, Portugal is the one beautiful country in Europe I haven't seen yet. So I'm. I've been. I spend a lot on. A lot of time on the Balearic Islands, you know, Spain, but I haven't been on the Azores. Okay. So I'm. I'm sure you're gonna have a beautiful time, and I'm glad we have a chance to. To meet and. And, you know, talk about our partnership. Yeah, let's zoom out a little to clarify things and. And then dive into details if needed. That. Yeah, and. And I mean, but maybe with the details as like a quick, quick, quick win. You mentioned there's a new colleague in your team who's now taking care of some of the details you couldn't take care of so swiftly. And please share the. The contact details eventually with me.
00:06:44
James: Yeah, I. Yeah, I already did. I texted you his WhatsApp number, but I'll make a group with you both. And he did a.
00:06:53
David Liebnau: His WhatsApp number went. Okay. Good to know. Good to know. I. I'VE overlooked that then no worries.
00:06:59
James: Yeah.
00:07:00
David Liebnau: The other day it's there, then it's good. But maybe in his name and maybe a little more formal introduction maybe.
00:07:10
James: Of course, yeah. Andy, we've worked, I've worked with him in the past. He's, he's not so, he's, he's not so new. Just new to this project.
00:07:22
David Liebnau: Okay.
00:07:23
James: He's, he's wonderful, he's reliable and, and I should have brought him in sooner.
00:07:29
David Liebnau: Yeah. And I mean, you know, you know, I value you as a person. You're a good guy. I like collaborating with you. But I have to say, James. Yeah. I'm not satisfied with how the partnership turned out. I mean to specify the reasons of dissatisfaction initially. I mean in, I think in December we, we worked out and I overall idea and I said, you know, and you asked me about timing and I said I'm easy with timing, I want to launch in middle February or so. And then you said no problem. And then I didn't facilitate or accelerated things in January and then came back to you on in February I think. And then I said then okay, let's launch in March. Because I intended, and that was part of my long term strategy to launch a marketing strategy of course with this series of landing pages to ideally conduct a retreat in May. Right. And now we are in the beginning of end of May and yeah, still a lot of it isn't online. So that was different than expected. And my intention is now to understand what's, what's your understanding of our deal in terms of value exchange. At some point I expressed my, my concern already to you and you said that you would somehow compensate for, for that severe delay on the same side I'm. Yeah, I heard you in terms of the quiz was more demanding than you intended or you not intended anticipated. So I like to have a conversation about your and my understanding expectations agreements in terms of scope and money. So what's your understanding or what's also your maybe specified response to that delay? And it's. Yeah, I don't want to say damage, but certainly not so fortunate outcomes for my intended marketing campaign and all that.
00:10:10
James: Mm. Yeah. So when we originally scoped this project and proposed this project, the sense I had was that it was more or less a. A contained website with different, different pages and, and very much one thing. And then as it's evolved and gotten clearer and I'm not sure how much of this is what's, what's changed or how much of this is the sense that you already had from the beginning and I've just caught up. But it's turned out to be lots of discrete landing pages which is harder and more difficult than, than a lot of the kinds of sites that we're used to where we have a homepage.
00:11:13
David Liebnau: About page with, with a quiz results. You are, I mean this was the, the quiz results was. And this personalized result sites. This, this was 10.
00:11:27
James: I'm speaking about everything. So we have the, the quiz page, the discovery page, you know, DavidLeadNow.com and different from Light Creators and the podcast page and these kind of distinct entities that are interconnected and have a wholeness to them. But the difficulty and complexity is, is a lot and the copy doc that we have, you know, of all these different pages plus the complexity of English and German, a lot of sites that we do. We, you know, There might be 1212 page Google Doc where we have homepage programs about over here and maybe some, something advanced and complex in there. But it's like oh one thing and a steady arc where we can have, you know, vision and strategy in the beginning and then we move into design and then we move into development. But the approach that we've ended up taking here is like do one, one page at a time. And we've had kind of lots of arcs which, and then as things took more time, I've been trying to over compensate and you know, make sure each one of those is really special and done. But it's been very inefficient and unlike what I initially envisioned in the proposal, you know, where the site could have been completed with like three creative vision sessions and three compact content sessions. And you know, that kind of flow can work when we're talking about a cohesive whole. But we end up talking about these different landing pages and that doesn't really work. And so I adapt and we've had lots of meetings and lots of iteration and I've made the time that I've, that I could have for this and it, it hasn't been enough to meet your, your expectations and, And I get that. And, and so yeah, I was just looking over the, the, the original.
00:14:07
David Liebnau: Let's, let's go back. I mean, I think, you know, I'm a service provider myself and I've been in situations where whatever the client wanted something different and then I had to make up for it and came into trouble. So I'm always interested in, you know, mutual learning because, and I, I just came in today prior to our call, so I hadn't had the time yet to look at the actual proposal you did send to me once, but there was I think mentioned like six to eight landing pages. Wasn't it like I think you offered that. So what would you do differently next time? Maybe that is the question, you know, the learning question for you and maybe for us as a learning field. What would need to happen next time to avoid such a call. Attention for now.
00:15:12
James: Yeah. I have six to eight custom page designs and custom page designs to me is quite different from a landing page where a landing page has a specific purpose. We want it to be refined, it can be quite involved. But a custom page design on a standard website can be much easier to create, especially if we're creating them all together in, in one stage. So the, you know, one learning for me is to, is to force the rhythm where what I'm, what I'm really delivering similar, I'm sure to you is not the number of pages but the journey that I can take the client on. And so I've hired a new project manager, Ashley, who's helping a lot and I've been onboarding new team members that will be integral to this. But we need to contain our engagements to these time containers and then in that time container we can, you know, there's so much presence and space and, and time that we can give to the creative process and if that ends up being, you know, 10 small pages on a big website or one big beautiful page with lots of parts and complex functions, it doesn't, it doesn't matter. You know, we could spend the same amount of time on those, on those things. And, and it's, we're not using pre built templates or stuff like that. So it's, I never want to price per page, but then I, you know, I, I have gotten into this situation where I've defined the scope and I want to deliver that even though the complexity of the parts has increased.
00:17:23
David Liebnau: So would you. Yeah, I don't know. A. I mean maybe I think it. Do you have our proposal or your proposal handy? Could, could you share it? Yeah, let's have a look at it. In terms of where would, would it, you know, open the door to this type of misunderstandings where. Because what I'm hearing is that you are saying actually although you, you didn't deliver in the promised time, you from your perspective delivered more money, more time, I mean working hours into the project than you scoped is. Is that right?
00:18:11
James: Than I expected. Yeah.
00:18:13
David Liebnau: Yeah. And so then, then I think it must have been somehow too over deliver over promising, right? Or not. Limiting enough. Is that the. Yeah, that's the proposal. Right. And what's. Can you, I don't know, zoom out a little more. Or share it with me again?
00:18:43
James: Yeah, I'll share this. There you go.
00:19:05
David Liebnau: WhatsApp. Or. Okay, here, I got it here in this one. No. Yes. No. Real time views. No. Where did you share it with me on WhatsApp. WhatsApp. Okay. WhatsApp. Oh yeah.
00:19:38
James: Okay.
00:19:38
David Liebnau: That was a nice, A nice qualitative entry cradling together all that visual language, brand strategic simplification. I know. I mean. Yeah. Well, let's look at this scope thing. Creative vision session. Two sessions, contents structure, brand visual, five to eight core pages. So you know, in my world. Yeah, but okay, like one page was not one page, but then seven pages and I counted as one page. That's, that's like one reason for, for, for specific, like room for misunderstanding. Right. Different journey. Yeah. Core page designs five and figma. I mean the. Yeah. I think that what's. What wasn't anticipated. It's mainly if, if I, you know, put myself in your shoes, is, is the quiz, isn't it?
00:21:08
James: Yeah, that's been the biggest, the biggest lift and there was nothing. Yeah, yeah, yeah.
00:21:18
David Liebnau: So again, overall, I think you definitely know your game. And more than that, I mean, you have a great aesthetic. Not only expectation, but also quality. So. Yeah, I like that. Could imagine we have more business going on in terms of airtable, maybe design customizations, automizations. I want to find a mutual ground for us to feel good about the project. So what would be your offer or point of view in terms of money delivery? Where are we at or where should we go to to achieve a good feeling between the two of us and potentially the willingness to collaborate in the future. Again.
00:22:32
James: Yeah, good question. So our original budget was. Just bringing up our payment schedule here, 9500. And you paid the 2850 deposit now? A long time ago. And originally the payment schedule was designed assuming that we would have a clear kind of design phase and then development phase. And so I, I wanted 40% after design approval that we've had this kind of cascade thing. So what would feel good to me? I want you to feel good and I want you to feel like you're, You're getting the value that you pay for. And I'm curious about the additional needs that you mentioned. You mentioned some more pages. And so. If we were to say right now we're done with everything, I wouldn't feel good about charging this full amount even if I, If I were to charge for the hours that I've put into this, it would probably be more than this. But I don't feel like we're complete with what we set out on here. If we can com complete what we set out on here, dot every T, cross every. I train you on webflow, hand everything over, have you be happy, have the quiz working really well. I would, I mean I would love the full amount for that, but I would also understand you're requesting a reduction. And also. Moving forward, if you want more support, I'm happy to talk about what a clear agreement structure might look like and also how we're setting up the studio now to provide more reliable support and forecasting and also leveraging of more team members besides myself, because I think one big problem here is I've done too much of this myself in part because we lost Yvonne, my kind of right hand guy, and a lot just fell on me to do. We now have Sean, who's awesome, and we have Andy, who's coming back in the fold, who's really great and he's German. I think you'll like him a lot. He's on your time zone, he speaks your language, he gets this world. And I think, you know, court coordinating with him will be, will be easy. I know, you know, and he does design and development. I, I'm probably always going to be the guy on the team who can do the most advanced things and find the craziest solutions to stuff, but in terms of, you know, just getting, getting the page built or making something look good or making a change fast, it's not efficient to have me do that. Anyway, so that, that's my thinking out loud on these.
00:27:09
David Liebnau: Yeah. Yeah.
00:27:10
James: So.
00:27:17
David Liebnau: What, what would be like, you know, to, to make it like at this point in time, like, like where. I mean, I mean I do want it. I, I do want you to complete the work. Right. I want you to. Or Henry. Hendrik is his name. Right, Hendrik. Andy. Sorry, Andy. I, I still haven't met him yet. So I'll, I'll need a. Make a note. Andy. Right. And his family name.
00:27:47
James: Andy Bittner Bitner.
00:27:49
David Liebnau: All right, so.
00:27:53
James: And he's in Frankfurt.
00:27:55
David Liebnau: Okay, so.
00:27:58
James: Or Munich actually.
00:28:01
David Liebnau: So what, I mean, what is this reduction offer you are willing to give assuming you deliver everything soon or Andy is doing it, I don't know by when you can promise me to be done because I mean this is an ongoing pain in a way. Right. And now you're on holiday, so when, when can you like promise with Andy's help that the. The requests I've been sharing with you already. No more at this point but the one I laid out to you can be, you know, all completed and all the things you've. You've like explained to me in terms of also extended webflow training. Yeah. To enable me potential to do something else on my own. So when we covered that, what would be your offer in terms of a reduction due to the delay?
00:29:07
James: So to be clear, the main outstanding things are final delivery that davidleadnow.com and then. And the changes we talked about on that and the podcast page.
00:29:27
David Liebnau: Right. Assuming I mean I haven't reviewed now the like the video integration, the thank you page from the diagnostic call. Assuming it works out. Yeah. And. And what I would also like to still have on my delivery side is one thorough qualitative review of the Davidleepnot.com side. I haven't done that now so far. I've been just looking on the functionality. Gross stuff. Right. But no more. And, and I mean you. You also I think laid out the solo page. Right. So that. That is also almost done. I. I want to review that. I need a tie it to an calendly paid schedule calendar and then we could say that's also good. Yeah. I don't want to make that too complicated but that I mean has been produced so should also go online. I think so no more landing page requests at this point in time just to wrap those projects up, make them all function in a way that you feel with your quality like understanding. Feel good about it. Allow me to enable me to work with this. Speaking of webflow training. So all that has been achieved by. When do you think that can be achieved? Let's start that.
00:31:18
James: I wanted to check in with Andy before I give you a promise on that.
00:31:27
David Liebnau: Yeah. And my friend James, I think as a coach at times it is I think also an important development edge for you to manage expectations and not be too kind. Maybe you've been too kind with me along the road. Always easy to work with but at times you should have probably pushed back and say if you request that it delays the process etc. Your project manager role I know was missing but for yourself maybe that's. That's something you. So I honor that. Please take the time. I don't need a rusher today. Maybe you know, you speak with Andy, you talk with him about his possibilities in the next days, weeks and then you think about not. Yeah. And then you feed back to me by when you can promise that and what you want to charge me then for it, I think. And then think about the reduction because the more I have to wait, really, the greater the pain is.
00:32:39
James: Yeah. Do you have a number in mind for that reduction?
00:32:47
David Liebnau: Well, as I said, I want to have a, a basis where you also feel honored enough. Right. For, for, for your good quality work and, and interested in doing more business with me. Yeah, I, so I, I, therefore, I don't want to be too pushy if you ask me for a number. What, what would it be? What would it make easy for me to ask you for, for a next project would be if you let go of a, like a third of, of the, of the overall volume. Like I've paid roughly. Yeah, well, yeah, like, I mean, yeah, very roughly. Yeah. So if I, if I round up, I would have to pay almost 10,000 or 9.5 paid already. Roughly 3. If I would pay now 6, 6 and a half overall, I would definitely feel very good about it. But that's, that's my perspective. If you have a different one, now is a good time to mention it or we speak about it at a later date. But I mean, I had to cancel my retreat plans really. And that was painful. I planned very different rollout and of course I don't want to blame it all to you. Right. And I'm also interested in bringing on another landing page live, one for which I've been already with Claude creating a ready HATML site. So no more like complicated design or text work would need to be done, but it still need to be integrated into, you know, webflow, etc. And at this point in time I wouldn't know how to do it, so. But I'm sure for you it's easy. I don't know how easy it is, but if you help me to get that done. And so that's also. I'm open also for barter deals. Yeah, so whatever, again, feels also good to you. So I'm open for creative solutions here or really mutual ways of looking at that.
00:35:42
James: Yeah, let me look at the numbers. But also speaking of Claude and webflow, let me tell you about this. Lately I've been building some hybrid websites. Well, actually all the sites we build these days have some hybrid components, like the quiz on your site.
00:36:13
David Liebnau: Hybrid. What hybrid means in your world in this context.
00:36:18
James: Yeah, I'll explain. So the user interface and the design and the elements on the page are built into webflow. And then we use a lot of custom code to make it work and to make it great. But we're also Doing some sites these days where sometimes the home page is fully built out in webflow, and then other pages that might change often are done entirely in custom code that Claude can create. And we can create files that make it easy for Claude to use the style guide and the elements of the website. And so it means that we can't edit those pages in the same visual way that we edit a webflow site. But it does mean that we can take that code as a whole and put it into Claude and say, hey, can you change this? Can you translate this? Can you make a new version of this?
00:37:18
David Liebnau: You want to see what I've done? Let me. Yeah, I like to share that with you. Maybe that's already what I've been doing. Let me hang on, let me share that with you. Yeah, hang on. And that is for a. A new. Or my. I mean, you know, the, the founder resonance thing came out of a. Yeah, an ongoing. Oh, how do I. How do I hang on? One step at a time. So the founder Resonance strategy of mine came out of a strategy conversation with Claude. More out of my mind, not so much out of my heart. What I'm about to share with you now is my true heart call my somatic. Yes. Yeah, So I definitely want to bring this to life. And I've been creating this on an HTML file with Claude, but I don't know how to. So this is how it looks. It's obviously German.
00:38:45
James: Copy.
00:38:47
David Liebnau: I, I fed Claude with my, my, like, design thing and then here we have these cool five pillars of a flourishing life, Vision, belonging, accomplishment, health and becoming. And yeah, I'm. I'm now actually in conversations where I, I like to share, show this to people and I may need to customize it quickly, but I don't know yet how to, how to do that most effectively. So is that a hybrid landing page or what is that? How would you call that?
00:39:33
James: Yeah, so one. Traditionally, what we would do is take this and then build it. Just use this as design and then build it in webflow, which is a bit tedious. You know, we have to build it by hand, go piece by piece. We can copy existing elements, of course, but we have to go through the whole thing. And there's no AI webflow builder that works well yet. There probably will be at some point, but so far.
00:40:07
David Liebnau: May I ask you something, James? I mean, I was, you know, that was before we were in conversations. I was once based on Jan bro. You know, Jan. I mean, he recommended me to you in the first place. But anyway, he also recommended and that was before, I think he recommended you Lovable as. As a AI tool to build websites and all that. And. But then they offered me, or Lovable wanted to build the website not on webflow, but on wix or, I don't know, some other. Other program I wasn't aware of. I. I didn't want it to go that way, so I stopped doing that. But is. Is. Is maybe the problem, just webflow Where. And would. Wouldn't it be. Would it be easier with other platforms to make real landing pages with AI?
00:41:18
James: No, webflow's not a problem, I don't think. It's just. We need to decide how we use it, because I could take this page that you've created and embed it on a webflow page in five minutes and publish it, and you can share that on your URL as it is, no problem. Like, that's. That's easy. It's. And, And I could also take that and spend more time with it and make sure it's responsive and maybe add in some custom icons and. But keep it as custom code living on that page instead of fully building it out in webflow as these elements. And you would be able to work with it as well. You could copy that code back into Claude and say, here's the page. I want to add this section. I want to change this thing. Can we do that?
00:42:19
David Liebnau: And do you call that hybrid, then? Is that hybrid? I call that hybrid, yeah, that's hybrid development. I mean, I would be interested in a little swimming help for hybrid development. And we could use this website I've shared with you as the initial project. And so I think if you consider, you know, like the delay and my need for. For this one, and make me an offer which has the potential to. For mutual. Mutual respect, appreciation, or a good feeling, basically. And.
00:43:13
James: Yeah.
00:43:13
David Liebnau: And if you aren't unclear about it, let's have another conversation, you know, after your honeymoon. It's not pressing from my side, but in the meantime, make sure if Andy is available, he's available for getting it done. Right. Without the other need in the first place. So that's the main thing. Right. And then the second one we can clarify after you return. So if I just wanted today to get a chance to bring a little more clarity in our relational space.
00:43:56
James: Yes. Yeah, great. Sounds good. I think that there's a solution in there that will make us both happy, and I'm excited about your willingness to play with these AI tools because I'm. I'm rethinking my own relationship to webflow even though it's. I love webflow as a platform. I want to show you something real quick.
00:44:38
David Liebnau: No, but you have to, James, you have to. I mean of course I, I notice what's going on and all that and. Oh, so what, what is that? That is what you. Are you doing it for the Hulu movement? That's one of your customers. Oh, hang on.
00:45:02
James: Sure, take your time.
00:45:04
David Liebnau: Yeah, let me take that call real quick.
00:45:09
James: Yeah, go for it. I'm here.
00:45:34
David Liebnau: So sorry, that was a customer who wasn't as important as our conversation now.
00:45:43
James: No problem. So yeah, I was just going to show. Are you still seeing this page here?
00:45:49
David Liebnau: Yeah, yeah, it looks cool.
00:45:53
James: So this is actually built all on webflow and I like using webflow because it's a solid backbone on top of which we can do more custom things like this map interface and. But we've built a full fledged app where people can create profiles. There's automatic image generation built into it, there's a really detailed assessment this profile that gets generated and we can do algorithmic matching with other people in the network to see if their needs and offerings and values align.
00:46:41
David Liebnau: I mean, you know, you're doing great work and looked very cool and so they are your customers and thus it's another reason why you came to the conference.
00:46:55
James: Yes. Yeah, yeah. So we're launching this app at the conference, I'm going to give a talk about it on Saturday and hopefully get a bunch of users in there testing things out. And it's. That's a hybrid website in that we're. We're using webflow for the user interface, but new features will do entirely in custom code first using Claude and prototype them and even host them on different pages on the site so we can get it tested out, see if it's working and then we'll go in and build it by hand, piece by piece so that we can have that full control over it.
00:47:47
David Liebnau: And when you use custom code, the hybrid sites, do they have still a short URL address or do they become then a long. No, you could always shorten it. Even if it's a long.
00:48:01
James: Yeah, any URL, it doesn't affect the URL.
00:48:06
David Liebnau: Yeah, yeah, yeah, yeah. I mean also if it's, if it's not a great deal at all anyway or for Andy, I assume Andy is comparable capable in using Automations as well these days. Is that so? I mean it's not yet the case where you gotta call James, right? Or is it not? Not yet. Really? Yeah. Okay, so the real crazy things we haven't talked about then yet, but that's another conversation we're gonna have at one point when it's, when it's, when is James needed? I want to know that one though. But I would, I mean, if feasible, I would like to get my custom code cloud created landing page, which I've just shared with you online quickly, ideally before your honeymoon.
00:49:18
James: Yeah. If you send me the code, I can on like, on like creators. A light creators URL.
00:49:23
David Liebnau: Yeah, yeah. If we just. I, I, how do I, how do I share the, the, the code? Just, just the URL address. Let, let's try this.
00:49:34
James: No, the file, it's on your computer.
00:49:37
David Liebnau: The HTML file, right? Yeah, yeah, I, I, and then yeah, I have, I have like two files or two, two different ones. One is for parents and one is for kids. So if I would share with you these files, you could just bring them online quickly. That would be great. And can I, can I then if I need to change a little of the copy, could I do that on webflow then? Or would I do that on Claude or how would editing happen then?
00:50:11
James: Yeah, I would make you a little video showing you how. So to bring it online quickly, I would just copy the code and put it right on web. Where right now, the thank you page, for example, Is that custom code. So you're seeing this here?
00:50:47
David Liebnau: Yeah, I do, I do.
00:50:50
James: So I just pasted the code for this page with the video player that I put into it in here. But editing it looks like this. And so if I, you know, I know HTML so I can edit this quickly. It's different from editing the homepage like this where I can, you know, should I.
00:51:14
David Liebnau: Would it be easier to edit it on Claude and then ask Claude again to produce a, an updated HTML file to download and then share that with you?
00:51:35
James: You can do that, but I want to. Yeah, that's, that, that totally works. And I can drop that in here. But I also want to show you how I, how I work with Claude on my own websites. So I have James Today as my personal site and this is entirely made with Claude. And when I have an update to make to this, I use Claude code and the site content is in GitHub and so I'm in Claude code and I see that it's connected to my James Today repo and I can just say, hey Claude, can you add a new section to my homepage or update this content or create a new version of this page as a draft? And it will do that. And if I say push it live It'll push it live. And I don't have to go into GitHub. I don't have to go into Webflow. I'm just talking to Claude. I can do it from my phone. I can text Claude from my phone and say, hey, make a new page on my website about this.
00:52:52
David Liebnau: I want this too, my friend. I want this too.
00:52:55
James: Okay, cool.
00:52:58
David Liebnau: What needs to happen so that, that I can do that myself?
00:53:04
James: Yeah, it's a bit of a setup, but I can do it for you. And then it's. It's very fun to have at your fingertips. So it's just about getting a GitHub repo, connecting that to Claude. And honestly, I think that we should make davidlebnow.com not on webflow. We should keep light creators on webflow. But I think David Leap now should just be this kind of thing. And then we can also use that same repo to create pages on like creators. We'll just have to put an embed on those custom pages. So if the landing page that you're telling me about today, if you want that to live on Light creators, we could still do that in this way. We just put a little script on Light creators to have it show up on that URL.
00:54:07
David Liebnau: So one thing first. I did share with you now the HTML files. Please try to open them to double check whether that's the right type of file I should share with you.
00:54:25
James: And you shared that you what tested them to me.
00:54:29
David Liebnau: Yeah, the first one is for Jug and Lijia. That's like youngsters. And then Eldon is like parents. I hadn't thought about the like, where Luke address which would be best. But you are saying you, you would suggest to make the davidleapnow.com in this hybrid way because then I have all flexibility and can further evolve it and all that.
00:55:03
James: Actually not hybrid. I would make it fully AI custom code. So fully Claude interface where updates you want to make to that site you make through. Through Claude.
00:55:22
David Liebnau: And why would you say that for the David Liebnau and not the Light creators?
00:55:30
James: Because Light creators, we already have so much precise mechanism that we built into the quiz.
00:55:41
David Liebnau: Yeah, yeah, yeah. And.
00:55:43
James: And the application and up there. And. But David Leibnow, it's. Yeah, we don't have that kind of assessment.
00:55:53
David Liebnau: Right.
00:55:53
James: It's not needed.
00:55:54
David Liebnau: Right. Then you could call the new site, you could call David LeapNow Dash Flourishing Life or Dash Fl. Yeah, we could rename it. Right?
00:56:17
James: Yes. Cool.
00:56:18
David Liebnau: Okay. So yeah, and you can open that here. Right. So that could be the one with which we could start setting that up in the way you, you mentioned. I'm. I'm definitely interested. Sorry. Yeah, so, so that's, that's one thing. But here, for example, the, the about David copy I know would need an update soon and whatever, and it could be a sub site of davidleapnow.com or it could become a new URL address. Maybe I would need to clarify that with the partner, Angelina, with whom I'm creating that. Probably I should have a conversation with her about it, but if it would be part of the David Leibnow.com world, it would be probably easier to set it up on a hybrid basis or more efficient to do it all in one thing. Right?
00:57:31
James: Yeah.
00:57:31
David Liebnau: And even if we would set it up initially as a David Leap now slash, Flourishing Life side, it could be probably doubled with another address where when Angelina says no, it should be Angelina and David Dash Flourishing Life. Right. Then that we could just publish it on another as well. Like mirrored. Right.
00:57:58
James: Yeah, easy.
00:58:00
David Liebnau: So, so right then, then let's put it together for, for now with a David LeapNow.com site. Right. And, but help me to fully understand, So far, the Davidleepnow.com site, you didn't intend as a hybrid thing. Right. You entered into webflow manually, mainly as the light creators thing. Right.
00:58:46
James: We started that, but right now the,.
00:58:51
David Liebnau: The,.
00:58:55
James: The podcast and the, and the landing page are fully flushed out in custom code. So if we want to keep them in, in the custom code space, that would be more than fine. And they would still look, you know, as, as good as they would look in web.
00:59:18
David Liebnau: Yeah, yeah, yeah, yeah. No, I, I'm, I'm just also double checking with you in terms of, like, scope of work. I don't want to make it again. I don't want to sneak more, more work into it for you.
00:59:35
James: Yeah, no, it's, it's less work for us if we can deal less with webflow.
00:59:41
David Liebnau: Yeah, yeah, but it will create more flexibility, as you say. I can envision that.
00:59:48
James: And if you're comfortable with working with AI, some people are like, I don't want to do it.
00:59:54
David Liebnau: No, no, no. I'm very comfortable working with Claude. If I can tell Claude I need an update on that, on that side, please do this and that. I'm more than happy. And if you can set that up for me, that would be great for sure.
01:00:07
James: Yeah, totally. And then you can even share designs with Claude. You can share pictures, you can say, publish my next podcast episode. The sky's the limit as well.
01:00:24
David Liebnau: Sorry. What did you say about the podcast episode?
01:00:29
James: You can have it publish your podcast episodes as well.
01:00:34
David Liebnau: Publishing or on. On the block or. Ah, you mean like connecting it, Uploading it into the podcast section? Yeah, yeah, yeah, yeah, yeah, yeah. I mean, I'm. I'm currently hosting my podcast on Potty G and from there it's connecting, but I don't know yet how the podcast landing page is supposed to. To work in terms of updating the. The files or the. The. The links and the zo.
01:01:11
James: The.
01:01:12
David Liebnau: The blocks. But whatever. I. Let's. I mean, I agree. Like, let's do that, you know, as automata Bill intelligent or operational friendly as feasible and helped me to understand how to. How to update it. And that's. That's great. And then let's bring in this into its ecosystem and yeah, that, That's. That's good. And let's do that fast, please.
01:01:53
James: Yeah. Great. Okay, well, let me check in with Andy and come up with a plan for you and a proposal, but I think we're gonna make something great work for all.
01:02:13
David Liebnau: Yeah. Good, good, good. Now I have also good feelings and thanks for today's conversation. I wish you a wonderful time in Europe and enjoy each moment. You well deserve it. James, I know you've been working hard, so I. Yeah, I'm happy for you. All the best. And let's have a continued our conversation after your honeymoon then.
01:02:37
James: Thank you so much. I'll be in touch before I go offline and see you on the other side.
01:02:43
David Liebnau: Alrighty. All the best.
01:02:45
James: All right.
01:02:45
David Liebnau: And one regrets to you beloved.
01:02:49
James: Thank you. Thank you.
01:02:50
David Liebnau: Bye.