As a growth marketer, I don't just manage campaigns. I design experiences, interpret behavioral data, coordinate departments, and now I also build functional interfaces, sometimes all in the same day. Google Stitch is one of the tools making that leap possible.
This article includes a prompt template at the end. You can jump directly to that section by clicking here.
The Problem Was Never Creativity. It Was Dependency.
If you've spent any time in digital marketing, you already know the frustration.
You have the hypothesis and the data to back it up. You know exactly what needs to change in the landing page, the registration flow, or the experience for new users. But between the idea and the execution, there are endless meetings, dozens of review rounds with the design team, an open queue of developer tickets, and at least three weeks on the calendar.
The problem was never creativity. It was the dependency we have on other teams.
The biggest bottleneck for a growth marketer isn't a lack of ideas, it's the distance between the idea and its execution.
For years, this has been one of the hidden costs of digital marketing: the speed of learning is limited by the speed of iteration, and the speed of iteration depends on resources that are outside your control.
These days I've been testing Google Stitch, and between this and Claude Code, everything I just described has changed.
The Glass Ceiling of the Traditional Growth Marketer
THE BEFORE
Before going freelance, I spent a total of seven years working in agencies. The ceiling was obvious: I was limited by the services the client had contracted. If I spotted an opportunity in the user experience or the design of a page, my role was reduced to documenting, recommending, and trying hard enough to sell the service. Execution belonged to another team, with another calendar, working by their own criteria.
When I moved to freelance work, I gained more freedom. Even so, for certain complex tasks, like email marketing campaigns or web development, I still depended on other specialists to execute. My contribution was strategic, but someone else had to translate it into code.
The result: long review cycles, a game of telephone between my initial proposal and what actually went live, and clients who lost their early enthusiasm while waiting to see something tangible.
The Leap: From Operator to Builder
A few months ago I started experimenting with Claude Code, and now with Google Stitch, to prototype digital products. What started as an internal test has now become part of my regular workflow.
Now I can execute and deliver by myself, not as a replacement for a senior designer, but as someone who can materialize ideas with enough fidelity to validate them, present them, and even build and publish them.
The change isn't just operational, it's also conceptual. When you can go from behavioral data to a functional mockup in a matter of hours, the conversations you have with clients shift completely. I no longer just present ideas, I now also present solutions. And the difference between the two is enormous in terms of confidence and decision speed, especially in startups where the pace is already high.
What Is Google Stitch and Why Does It Matter Now
Google Stitch doesn't replace good taste or critical thinking. It amplifies them. The difference comes from whoever is using it.
Google Stitch is an AI-powered prototyping tool developed by Google Labs. It allows you to generate interface mockups, web pages, and user flows from prompts, visual references, and existing files.
It's a system that understands context, style, and structure, generating visual proposals you can iterate on quickly, essentially a Figma on steroids.
In practice, this means a growth marketer with strong analytical judgment, behavioral data, and clarity about what needs to change can produce concrete design proposals without needing to master professional design tools.
Three Real Cases, Three Types of Impact
USE CASES
Case 1: Carbon Emissions Management SaaS
We evaluated a redesign of a landing page that helped users calculate their company's carbon emissions. The brief existed, usage data from the tool was available in Clarity, but the design team's calendar was packed for weeks and the developers had UI projects in the SaaS that took priority.
With Google Stitch, I produced a complete landing page proposal in a single morning: content structure, sections, visual hierarchy, main CTA, and the flow toward the tool. I iterated through three versions before presenting it to the team. The feedback was positive from the very first call.
Time saved compared to the traditional process: approximately 70 percent of the usual cycle.
Case 2: AI-Powered Digital Risk Insurer
For this cyber insurer, the challenge was different: not starting from scratch, but creating a replicable landing page template for different resource types. Each landing had to maintain brand consistency while adapting to different audiences depending on the resource, whether industry landings, product landings, or downloadable resource pages.
I uploaded the existing site files to the tool, defined the necessary variations, and generated the template skeleton. The result was a modular system the internal team could adopt directly, without needing to start from scratch for every new asset. That said, it's worth pointing out that a mockup doesn't translate directly into development. Google Stitch typically won't generate a landing that's perfectly faithful to a company's brand, and several revision rounds are needed, along with accounting for adjustments.
Case 3: Buy and Sell Bare Ownership Real Estate Proptech
The client operates in the real estate sector with a specialized product: the purchase and sale of bare ownership. A complex financial product that needs to be explained clearly before the user makes any decision.
The challenge was designing a simulation flow that guided the user step by step, reduced cognitive friction, and built enough trust to prompt a call request. We already had a calculator built with Outgrow that was producing great results, but as we migrated all landings to the company's own site, we generated the new flow prototype using Clarity behavioral data and specific prompts in Google Stitch. The client could see the user journey logic clearly before a single line of code was written. Again, it's worth emphasizing that the landing designed in Stitch is not a 100 percent accurate representation of what ends up in development.
The Workflow: From Data to Mockup in No Time
STEP BY STEP PROCESS
This is the workflow I've standardized, and it consistently produces reliable results:
- Upload the current website files to Claude Web. This gives it structural, style, and content context. The model understands where the design starts, so it's not working in a vacuum.
- Load Microsoft Clarity data. Session recordings, heatmaps, drop-off zones, rage clicks. This turns intuition into hypotheses grounded in real user behavior.
- Analyze the behavior. With data from both sources, the AI can identify specific friction points: where attention drops, where there's visual confusion, where the CTA isn't converting.
- Generate the prompts for Google Stitch. A vague prompt produces vague results. A prompt with brand context, audience, conversion goal, and style reference produces useful proposals. The AI itself, given all that context, can generate a much more precise and valuable Stitch prompt than I could produce on my own.
- Create the mockups and iterate. Google Stitch generates visual options you can refine in real time. Three or four iterations in an hour or two is perfectly realistic.
- Validate with the client before development. This is the most underrated advantage: the client sees something tangible before a single line of code exists. Feedback at this stage is far more useful and precise.
- Move to development or Claude Code. Once the prototype is validated, the handoff to development is much cleaner. If you're working with Claude Code, translating the mockup directly into functional code is much simpler because you can download the prototype as HTML.
This Changes the Rules, Not Just the Tools
Speed
The traditional design cycle carries enormous hidden costs: briefing meeting, proposal, review, adjustments, second review, approval. With this workflow, that cycle compresses into hours. Three weeks can become three days once you factor in the meetings. And in growth, the speed of iteration is directly proportional to the speed of learning, always keeping in mind that the more data you have, the better you'll understand your audience.
Independence
Operational autonomy changes the nature of the work. I can present complete solutions, not just recommendations. That has a direct impact on how clients perceive the value I bring, and on how quickly decisions get made.
Alignment Between Data and UX
The deepest advantage isn't speed, it's the quality of the connection between the analytical insight and the design proposal. When the person analyzing user behavior and the person defining the experience are the same person, less gets lost in translation. The design doesn't interpret the data, it incorporates it directly.
For me, the biggest loss in growth isn't traffic, it's having to play telephone with the rest of the teams.
Strategic Implications: For Founders and for Marketers
For Founders and Product Teams
If your startup is in growth phase and your growth marketer needs a three-week cycle to test website changes, I think it's fair to say, after all this, that the process has a lot of room for improvement. The tools exist to shorten that cycle. The profile you're looking for isn't just someone who optimizes campaigns or coordinates across teams. I'd argue it's now someone who can close the loop between user data and the experience that user receives, using tools that keep them right at the front line.
For Growth Marketers
The question isn't whether to learn prototyping tools. The question is how much longer you'll be able to differentiate yourself by working with campaigns alone. The market is rewarding profiles that expand their execution range. Mastering the space between data and interface is a real competitive advantage, and it's becoming more accessible every month.
The growth marketer of the next cycle won't just be a better analyst. They'll also be a better builder.
Limitations: What Google Stitch Doesn't Do (and Where It Falls Short)
BEING HONEST
This section exists because honesty is part of having good judgment. Google Stitch is a powerful tool, but it has real limitations worth knowing before you overestimate its capabilities.
- It doesn't replace a mature design system. If your company has a consolidated style guide, defined components, and a design team with their own established criteria, Google Stitch won't replicate that level of consistency without significant additional work. In my experience, it's difficult for someone without the same judgment as a trained designer to replicate what a real designer produces.
- It requires structured inputs and judgment. A vague prompt produces a generic result. The quality of the output depends directly on the quality of the input: brand context, conversion objective, visual reference, design constraints. If you don't have a clear picture of what you're looking for, the tool won't find it for you. Good context is what generates good results.
- The AI signature is detectable. Websites generated with AI follow a recognizable pattern. Users notice when personalized content is missing: real images, proprietary data, specific cases, sections built on genuine experience. A Stitch-generated prototype that reaches production without deep personalization shows. That personalization is still human work. My own website, however polished it might look, has sections that are clearly attributable to AI.
- It's not the final step in the process. It's the starting point for the handoff to development. The resulting code needs review, the design needs adaptation to existing systems, and the final experience still requires real iteration using the data that users generate during navigation.
The Future: Product and Marketing Closer Together Than Ever
The separation between whoever designs growth and whoever builds the experience has always been artificial. The product is the marketing. The user experience is the most important campaign you have.
What's changing is that the tools are removing the execution barriers that maintained that separation for years. A growth marketer who knows where users drop off, why they're not converting, and what hypothesis they want to test now has the ability to materialize that hypothesis without waiting for anyone.
That doesn't mean designers or developers are dispensable. It means the learning loop can be shortened substantially, and that the profile who closes that loop has a growing competitive advantage.
Even though I think Google Stitch is still quite early-stage to be considered the "tool that will put web designers out of work," it definitely opens up conversations about what a single person can now execute across different areas of digital marketing.
The growth marketer who can go from data to prototype in the same day is no longer an outlier. That's starting to become the standard.
Ready-to-Use Prompt for Google Stitch
If you've read this far, you deserve something useful. Below you'll find the prompt structure I'm currently using to produce valuable mockups with Google Stitch.
Design a highly conversion-focused landing page mockup for a B2B SaaS platform.
Strictly follow the structure, style and requirements defined below.
---
[1. OBJECTIVE]
Create a landing page that maximises conversion (demo, sign-up or contact),
clearly communicating the product's value.
---
[2. PRODUCT DESCRIPTION]
Product name:
[INSERT NAME]
Brief description:
[DESCRIBE IN 1–2 SENTENCES WHAT IT DOES]
What it allows the user to do:
- [MAIN FUNCTIONALITY 1]
- [MAIN FUNCTIONALITY 2]
- [MAIN FUNCTIONALITY 3]
- [MAIN FUNCTIONALITY 4]
- [PROBLEM IT ELIMINATES]
---
[3. TARGET AUDIENCE]
Profiles:
- [PROFILE 1]
- [PROFILE 2]
- [PROFILE 3]
- [PROFILE 4]
Audience characteristics:
- Technical level: [LOW / MEDIUM / HIGH]
- Current tools: [TOOLS]
- Frustrations: [KEY PAINS]
- What they're looking for: [BENEFITS]
- Level of scepticism: [LOW / MEDIUM / HIGH]
---
[4. VALUE PROPOSITION]
Main proposition:
"[CLEAR, OUTCOME-ORIENTED PROPOSITION]"
Alternative angles:
- "[ANGLE 1]"
- "[ANGLE 2]"
- "[ANGLE 3]"
---
[5. LANDING PAGE STRUCTURE]
5.1 Hero Section
- Headline focused on outcome (speed, clarity, ROI, etc.)
- Subtitle explaining the product simply
- Main CTA: [E.G. "Request a demo"]
- Secondary CTA: [E.G. "See how it works"]
- Visual: [DESCRIBE VISUAL IDEA]
---
5.2 Problem Section
Show clearly:
- [PROBLEM 1]
- [PROBLEM 2]
- [PROBLEM 3]
- [PROBLEM 4]
Use visual contrast: chaos vs clarity
---
5.3 Solution Section
Explain how it works:
1. [STEP 1]
2. [STEP 2]
3. [STEP 3]
4. [STEP 4]
Represent as a simple visual flow
---
5.4 Features / Functionality
Present in cards:
- [FEATURE 1]
- [FEATURE 2]
- [FEATURE 3]
- [FEATURE 4]
- [FEATURE 5]
- [FEATURE 6]
---
5.5 Use Cases
Format:
Input (user question) → Output (answer/insight)
Examples:
- "[QUESTION 1]"
- "[QUESTION 2]"
- "[QUESTION 3]"
- "[QUESTION 4]"
---
5.6 Social Proof
- Logos: [COMPANIES]
- Testimonials: [TYPE OF PROFILE]
---
5.7 How It Works (technical, simplified)
- [MAIN LAYER]
- [APIs / INTEGRATIONS]
- [INTERFACE]
- [OUTPUTS]
Maintain credibility without excessive complexity
---
5.8 Final CTA
- Reinforce value proposition
- Main CTA: [CTA]
- Secondary CTA: [OPTIONAL]
---
[6. DESIGN STYLE]
- Modern, minimalist, clean
- Inspiration: Stripe, Linear, Vercel (or similar)
- Professional (avoid generic style)
- Explore light or dark mode
- Use:
- Subtle gradients
- Grids
- Data visualisations
- Include real product mockups
---
[7. TONE]
- Clear and direct
- Confident and technical but accessible
- No unnecessary buzzwords
- Focused on results
---
[8. OUTPUT REQUIREMENTS]
- Complete landing mockup
- Desktop-first (responsive optional)
- Include:
- Charts
- Tables
- Query-type interfaces
- Use placeholders only if necessary
---
[9. STRATEGIC DIRECTION]
- Avoid generic SaaS templates
- Position the product as:
[E.G. "Data infrastructure", "Intelligence layer", etc.]
The design must convey:
- Precision
- Power
- Trust
---
Generate the complete landing following this structure.If you work on a SaaS, insurtech, proptech, or any sector where user experience is part of the acquisition funnel, and you want to explore how to shorten the cycle between insight and execution, you can book a call with me through the form.