How this agency is reimagining website creation through AI and automation

October 21, 2025
0 minute read

When Justin Sturges talks about web design, it sounds less like coding and more like orchestration. Every element, from client onboarding to SEO content, plays its part in a finely tuned system where automation and artificial intelligence do much of the heavy lifting. “Once we get everything in, that’s when we start automating and doing everything we can to make it efficient,” Sturges explains.


For the founder of a small but remarkably efficient digital agency, this evolution was a necessity. His clients, small and local businesses paying for high-touch retainers, expect polish and precision. Yet the industry’s traditional workflows, weighed down by manual edits and endless client revisions, made scale almost impossible. Instead of hiring a larger team, Sturges turned to AI and a network of tools to reinvent the way websites are built, maintained, and marketed.


A white-glove process for an automated world


Sturges’s approach begins with something seemingly counterintuitive: a deeply human onboarding call. “We go for higher-end retainers, so it just doesn’t make sense to hand clients a form and say ‘fill it out,’” he says. “We’re helping them as much as possible in that first meeting. It’s sort of a concierge, white-glove thing.”


That conversation sets the tone, and collects the raw materials necessary for automation. Clients describe their business, their market, and what makes them different. Sturges’s team then maps out services and service areas in priority order, a crucial step that drives every decision that follows. “Once we get that nailed down, onboarding is done and we can execute the website,” he says.


What follows looks almost magical from the outside. Data from the intake process flows into a network of systems; GoHighLevel for client information, Google Sheets as a dynamic prompt library, and Duda as the final publishing platform. The information moves between these tools through APIs and custom scripts, turning what once took days or weeks into hours.


Website in a Day™: A proven methodology for agencies

Justin Sturges walks through his Website in a Day™ methodology, a proven, standardized, production-ready workflow that lets agencies deliver professional sites in hours, not weeks.

Watch the webinar


Training AI for authentic brand voices


Automation, however, is only as good as the intelligence behind it. Sturges knew from experience that AI-generated text could sound flat, generic, and lifeless; the kind of content Google flags and audiences ignore. His solution is to train AI dynamically for each client by combining the nuances of human tone with structured data.


“For every prompt, we train the AI,” he says. “We pick an author that Google knows, one whose voice fits the company’s tone, and then mix that with emotional brand traits like ‘confident’ or ‘approachable.’”


He’s careful to clarify that this isn’t about impersonation or style mimicry. Instead, it’s a way of aligning the model’s natural rhythm with a recognizable human cadence. “If the author comes up in an author box in Google results, then the AI usually has enough information to model their voice,” he explains. The result is content that reads as distinctly human, tailored to the client’s brand and infused with personality.


This method also simplifies revisions. Instead of line-editing text or chasing commas, Sturges adjusts the underlying data. “If the client says something’s wrong, we tweak the bullet points about that service and regenerate it via API,” he says. “It’s faster and more accurate than editing by hand.”


Even small updates, like replacing photos or minor text changes, flow seamlessly through Duda’s comment boxes. “I love that feature,” he says. “WordPress still doesn’t have anything like it.”


Dynamic pages, smarter SEO


The heart of Sturges’s innovation lies in how he combines AI-driven content creation with structured SEO. Each client’s services and service areas are prioritized early in the onboarding phase, not just for site navigation but for search optimization. “We standardize on six core services,” he says. “Those become the backbone of the homepage and the rest of the site.”


During strategy sessions, Sturges and his clients analyze search behavior live, adjusting terminology to match how real users look for those services. “You might call it ‘roof restoration,’ but people in your area are searching for ‘roof repair,’” he explains. “We make sure they align with search intent and local demand.”


From there, AI prompts are automatically populated with the right keywords, tone, and metadata. The generated content is both readable and optimized. “Our prompts write the content and include all the SEO,” Sturges says. “We can pump it right into Duda’s backend fields, titles, meta descriptions, alt tags, everything connects.”


The structure also allows for strategic use of FAQs, a surprisingly effective SEO and UX element. “We use FAQs to add depth without overwhelming the page,” he says. “They’re expandable, so the layout stays clean, and we’ve seen them help our clients show up in AI search results too.”


Converting manual labor into AI symphonies


For Sturges, this efficiency drives measurable transformation. “Compared to WordPress with an overseas team? Oh my God,” he laughs. “We used to have 11 people. Now it’s just my wife, me, and a couple of part-timers handling support.”


The workflow that replaced those extra hands is a feat of engineering. When clients submit data through an intake form, it lands in GoHighLevel, where fields can be easily reviewed or updated. That data is then exported to a Google Sheet, the central hub of Sturges’s automation.


Each row represents a client, with fields for brand voice, target audience, services, colors, tone, and more. Those variables feed directly into complex prompts that guide AI writing tasks. “It’s like creating a custom GPT for every client, but instead of building a model, we’re building a highly detailed prompt,” he says.


Once generated, the content travels automatically into Duda, either through collections or business text fields, filling in entire websites in a fraction of the time. The system even handles press releases, blog posts, and social media updates. “Everything talks to either Duda or GoHighLevel,” Sturges explains. “That’s it. Two platforms. Simple, efficient, and fast.”


The dynamic master template


Perhaps Sturges’s most powerful invention is what he calls the “Dynamic Master Template.” In essence, it’s a single, modular Duda site that every client website connects to.


“Instead of using different templates all the time, we have one master template,” he says. “If we need to change the design, we do. But all the grunt work, the service pages, social links, calls to action, that’s automated.”


This master template houses an intricate system of connected data fields, standardized sections, and reusable modules. When new client data is uploaded, those fields populate automatically, generating a unique but structurally consistent website.


“We can literally build fifteen service pages in five minutes,” Sturges says. “They read differently, and they rank. It’s a massive time-saver.”


The template also makes updates trivial. “If I change a form in GoHighLevel, it updates across every page of the site,” he says. “No more clicking through hundreds of instances.”


For agencies using Duda, Sturges’s system offers a vision of what’s possible. “I call it agency efficiency,” he says. “You can get more done, faster, and stay focused on strategy instead of production.”


Human strategy with automated execution


Sturges’s method doesn’t eliminate creativity, rather, it amplifies it. By automating repetitive work, he frees himself to focus on brand positioning, conversion strategy, and messaging.


The process begins with what he calls a “conversion framework,” a page structure designed to highlight a client’s value proposition instantly. “We’ve tested it,” he says. “It converts, it ranks, and it generates quality leads.” Each new client site inherits that structure automatically, with the AI generating copy that fits into pre-set character limits and tone guidelines.


That alignment between design and content is the true innovation. “If you design your page ahead of time, you can structure the prompts to match,” he explains. “Then you never have to rewrite the layout for each client.”


Even the creative flourishes are handled efficiently. Sturges saves sections of sites, from hero images to testimonials, in a library that can be pulled into new designs instantly. “They’re connected,” he says. “When I reuse a section, it automatically populates the right images and text.”


Empowering clients and agencies alike


The ripple effects of this automation extend far beyond time savings. For clients, it means faster launches, consistent branding, and better long-term performance. For Sturges’s agency, it’s a complete repositioning.


“This isn’t just about standardizing a process,” he says. “It makes your clients stick around longer and positions you as a consultant instead of just a web designer.”


That shift has opened up new business opportunities. “When clients start seeing you as a consultant, they ask for your advice on everything,” he says. “It opens the door to retainers for SEO, press releases, content—all powered by the same onboarding data.”


Sturges’s philosophy blends high-touch client care with high-tech efficiency. The balance allows him to operate at a scale that once required a full team while maintaining a personal connection with every client. “It’s the best of both worlds,” he says. “Human relationships upfront, automation on the backend.”


A framework for the future of agencies


At its core, Sturges’s system is about rethinking what an agency can be. Many web designers, he says, still spend too much time clicking, copying, and formatting; all work that machines can handle. The real value lies in the strategic layer: understanding audiences, crafting messaging, and building trust.


“When you get out from under the crush of too much clicking and work,” he says, “you rise above it. Suddenly, you’re a consultant, not just a web designer.”


That shift also has personal meaning for him. Sturges’ deeper drive is a passion for systematizing creativity, finding ways to scale quality without sacrificing authenticity. “I like this work. I really do,” he says. “But, you know, after doing it for so many years, your hands start to wear out. So, what can I do to save the things that just take time and clicks.”


Sharing his knowledge


Sturges isn’t protective of his methods. In fact, he’s eager to share them. He mentors other designers informally, showing them how to combine AI tools, APIs, and Duda’s ecosystem into cohesive workflows. The response, he says, has been overwhelmingly positive. “Everyone I’ve shown the dynamic master template to says, ‘Oh my God, we’re doing that,’” he says. “It’s just such a lightbulb moment.”


As automation continues to transform creative industries, Sturges’s model points to a future where small agencies can operate with the sophistication of much larger ones, not by hiring more people, but by designing smarter systems.


“The tools are there,” he says. “You just have to connect them.”


Did you find this article interesting?


Thanks for the feedback!
By Shawn Davis April 1, 2026
Core Web Vitals aren't new, Google introduced them in 2020 and made them a ranking factor in 2021. But the questions keep coming, because the metrics keep changing and the stakes keep rising. Reddit's SEO communities were still debating their impact as recently as January 2026, and for good reason: most agencies still don't have a clear, repeatable way to measure, diagnose, and fix them for clients. This guide cuts through the noise. Here's what Core Web Vitals actually measure, what good scores look like today, and how to improve them—without needing a dedicated performance engineer on every project. What Core Web Vitals measure Google evaluates three user experience signals to determine whether a page feels fast, stable, and responsive: Largest Contentful Paint (LCP) measures how long it takes for the biggest visible element on a page — usually a hero image or headline — to load. Google considers anything under 2.5 seconds good. Above 4 seconds is poor. Interaction to Next Paint (INP) replaced First Input Delay (FID) in March 2024. Where FID measures the delay before a user's first click is registered, INP tracks the full responsiveness of every interaction across the page session. A good INP score is under 200 milliseconds. Cumulative Layout Shift (CLS) measures visual stability — how much page elements unexpectedly move while content loads. A score below 0.1 is good. Higher scores signal that images, ads, or embeds are pushing content around after load, which frustrates users and tanks conversions. These three metrics are a subset of Google's broader Page Experience signals, which also include HTTPS, safe browsing, and mobile usability. Core Web Vitals are the ones you can most directly control and improve. Why your clients' scores may still be poor Core Web Vitals scores vary dramatically by platform, hosting, and how a site was built. Some of the most common culprits agencies encounter: Heavy above-the-fold content . A homepage with an autoplay video, a full-width image slider, and a chat widget loading simultaneously will fail LCP every time. The browser has to resolve all of those resources before it can paint the largest element. Unstable image dimensions . When an image loads without defined width and height attributes, the browser doesn't reserve space for it. It renders the surrounding text, then jumps it down when the image appears. That jump is CLS. Third-party scripts blocking the main thread . Analytics pixels, ad tags, and live chat tools run on the browser's main thread. When they stack up, every click and tap has to wait in line — driving INP scores up. A single slow third-party script can push an otherwise clean site into "needs improvement" territory. Too many web fonts . Each font family and weight is a separate network request. A page loading four font files before rendering any text will fail LCP, especially on mobile connections. Unoptimized images . JPEGs and PNGs served at full resolution, without compression or modern formats like WebP or AVIF, add unnecessary weight to every page load. How to measure them accurately There are two types of Core Web Vitals data you should be looking at for every client: Lab data comes from tools like Google PageSpeed Insights, Lighthouse, and WebPageTest. It simulates page loads in controlled conditions. Lab data is useful for diagnosing specific issues and testing fixes before you deploy them. Field data (also called Real User Monitoring, or RUM) comes from actual users visiting the site. Google collects this through the Chrome User Experience Report (CrUX) and surfaces it in Search Console and PageSpeed Insights. Field data is what Google actually uses as a ranking signal — and it often looks worse than lab data because it reflects real-world device and connection variability. If your client's site has enough traffic, you'll see field data in Search Console under Core Web Vitals. This is your baseline. Lab data helps you understand why the scores are what they are. For clients with low traffic who don't have enough field data to appear in CrUX, you'll be working primarily with lab scores. Set that expectation early so clients understand that improvements may not immediately show up in Search Console. Practical fixes that move the needle Fix LCP: get the hero image loading first The single most effective LCP improvement is adding fetchpriority="high" to the hero image tag. This tells the browser to prioritize that resource over everything else. If you're using a background CSS image for the hero, switch it to anelement — background images aren't discoverable by the browser's preload scanner. Also check whether your hosting serves images through a CDN with caching. Edge delivery dramatically reduces the time-to-first-byte, which feeds directly into LCP. Fix CLS: define dimensions for every media element Every image, video, and ad slot on the page needs explicit width and height attributes in the HTML. If you're using responsive CSS, you can still define the aspect ratio with aspect-ratio in CSS while leaving the actual size fluid. The key is giving the browser enough information to reserve space before the asset loads. Avoid inserting content above existing content after page load. This is common with cookie banners, sticky headers that change height, and dynamically loaded ad units. If you need to show these, anchor them to fixed positions so they don't push content around. Fix INP: reduce what's competing for the main thread Audit third-party scripts and defer or remove anything that isn't essential. Tools like WebPageTest's waterfall view or Chrome DevTools Performance panel show you exactly which scripts are blocking the main thread and for how long. Load chat widgets, analytics, and ad tags asynchronously and after the page's critical path has resolved. For most clients, moving non-essential scripts to load after the DOMContentLoaded event is a meaningful INP improvement with no visible impact on the user experience. For websites with heavy JavaScript — particularly those built on frameworks with large client-side bundles — consider breaking up long tasks into smaller chunks using the browser's Scheduler API or simply splitting components so the main thread isn't locked for more than 50 milliseconds at a stretch. What platforms handle automatically One of the practical advantages of building on a platform optimized for performance is that many of these fixes are applied by default. Duda, for example, automatically serves WebP images, lazy loads below-the-fold content, minifies CSS, and uses efficient cache policies for static assets. As of May 2025, 82% of sites built on Duda pass all three Core Web Vitals metrics — the highest recorded pass rate among major website platforms. That baseline matters when you're managing dozens or hundreds of client sites. It means you're starting each project close to or at a passing score, rather than diagnosing and patching a broken foundation. How much do Core Web Vitals actually affect rankings? Honestly, they're a tiebreaker — not a primary signal. Google has been clear that content quality and relevance still dominate ranking decisions. A well-optimized site with thin, irrelevant content won't outrank a content-rich competitor just because its CLS is 0.05. What Core Web Vitals do affect is the user experience that supports those rankings. Pages with poor LCP scores have measurably higher bounce rates. Sites with high CLS lose users mid-session. Those behavioral signals — time on page, return visits, conversions — are things search engines can observe and incorporate. The practical argument for fixing Core Web Vitals isn't just "because Google said so." It's that faster, more stable pages convert better. Every second of LCP improvement can reduce bounce rates by 15–20% depending on the industry and device mix. For client sites that monetize through leads or eCommerce, that's a revenue argument, not just an SEO argument. A repeatable process for agencies Audit every new site before launch. Run PageSpeed Insights and record LCP, INP, and CLS scores for both mobile and desktop. Flag anything in the "needs improvement" or "poor" range before the client sees the live site. Check Search Console monthly for existing clients. The Core Web Vitals report surfaces issues as they appear in field data. Catching a regression early — before it compounds — is significantly easier than explaining a traffic drop after the fact. Document what you've improved. Clients rarely see Core Web Vitals scores on their own. A monthly one-page performance summary showing before/after scores builds credibility and makes your technical work visible. Prioritize mobile. Google uses mobile-first indexing, and field data shows that mobile CWV scores are almost always worse than desktop. If you only have time to optimize one version, do mobile first. Core Web Vitals aren't a one-time fix. Platforms change, new scripts get added, campaigns bring in new widgets. Build the audit into your workflow and treat it like any other ongoing deliverable, and you'll stay ahead of the issues before they affect your clients' rankings. Duda's platform is built with Core Web Vitals performance in mind. Explore how it handles image optimization, script management, and site speed automatically — so your team spends less time debugging and more time building.
By Ilana Brudo March 31, 2026
Vertical SaaS must transition from tools to an AI-powered Vertical Operating System (vOS). Learn to leverage context, end tech sprawl, and maximize retention.
By Shawn Davis March 27, 2026
Automate client management, instant site generation, and data synchronization with an API-driven website builder to create a scalable growth engine for your SaaS platform.
Show More

Latest posts