About LawnStarter
LawnStarter is the nation's leading on-demand marketplace for lawn care and related services, with over $100M in annual bookings. We're expanding beyond lawn care to become the one-stop shop for all home services.
About Growth at LawnStarter
Our Growth team drives customer acquisition and conversion across four brands — LawnStarter, Lawn Love, Home Gnome, and ProBase. The marketing sites are central to that work: thousands of organic SEO pages, landing pages, and core site experiences that need to move as fast as the team iterating on them. Today, making changes to our marketing sites requires engineering support. That bottleneck slows down testing, kills momentum, and means conversion opportunities sit on the table. We're moving to Webflow as the source of truth for our marketing sites, and we need someone to own that transition and everything that follows.
The Role
You'll report to the Director of Design but be fully embedded on the Growth team, working daily with CRO specialists, data analysts, SEO, Paid, content teams, and less frequently engineers. Your job is to make our marketing sites fast to change, beautiful, on-brand, and optimized for conversion — without needing an engineer every time something needs to move.
You'll start with Home Gnome, building it right from the ground up in Webflow. From there, you'll bring LawnStarter, Lawn Love, and ProBase into a componentized Webflow architecture. This is a chance to define how all four brands show up on the web.
What makes this role different:
What You'll Own
Problems to Solve
Our marketing sites depend on engineering for every change Today, even simple updates require a developer. That means the Growth team can't iterate at the speed they need to. VWO tests take too long to implement. New pages wait in a queue. You're here to break that dependency by making Webflow the place where marketing site changes happen — fast, without engineering involvement.
We don't have a componentized, scalable site architecture The current sites aren't built for speed or scale. We don't have a Webflow component library, styles, or CMS collections. You need to build the foundation — a clean component library, organized CMS structure, and page templates that let anyone on the team spin up on-brand pages without starting from scratch.
Thousands of SEO pages need to look good and perform well We have over a thousand organic SEO pages across our brands. These pages drive significant traffic and revenue, but they need to load fast, look modern, pull in the correct data, and maintain brand consistency at scale. Templating and CMS architecture are the key — you can't hand-craft a thousand pages.
Four brands need to look distinct but share a foundation Home Gnome, LawnStarter, Lawn Love, and ProBase each have their own visual identity. But the underlying Webflow architecture — components, CMS structure, interaction patterns — should be similar where it makes sense.
What Success Looks Like (Year 1)
Requirements
Who You Are
A Webflow expert. You've built and maintained complex, multi-page Webflow sites with real architectural rigor — not just pretty one-pagers. You understand component architecture, CMS collections, dynamic content, interactions, and how to keep a large site clean and performant. This is unlikely to be a good fit if you've only used Webflow for small projects or treat it as a visual tool rather than a development platform.
A top-tier visual designer. You have a strong eye and high standards for both modern design and usability. Your pages are modern, polished, and hold up against the best marketing sites on the web. You care about typography, spacing, hierarchy, usability, accessibility, and the details that separate good from great. This is unlikely to be a good fit if visual design is secondary to your development skills or you rely heavily on templates without elevating them.
Growth-team fluent. You've worked alongside CMOs, SEO teams, paid teams, content teams, CRO specialists, data analysts, and engineers before. You understand conversion funnels, A/B testing, and how to support experiments and implement changes quickly. You make decisions based on data, not just aesthetics. This is unlikely to be a good fit if you've only worked in brand or product design teams and aren't familiar with the pace and priorities of growth.
Self-directed and fast. You take a brief, run with it, and ship. You don't need someone managing your queue or reviewing every decision. When the Growth team needs a new landing page or a test variation, you turn it around quickly without sacrificing quality. This is unlikely to be a good fit if you need detailed direction for each project or prefer a slower, more deliberate pace.
AI-native. You use AI tools and platforms like Relume to accelerate your workflow — generating component layouts, scaling page production, and speeding up repetitive tasks. You're always looking for ways to move faster without cutting corners. This is unlikely to be a good fit if you're skeptical of AI tools or insist on building everything from scratch.
Technically capable beyond Webflow. You have some ability to write custom code when Webflow's native tools aren't enough — whether that's custom CSS, JavaScript for tracking implementations, or integrations with tools like VWO. You can collaborate with engineers on technical requirements without needing everything translated. This is unlikely to be a good fit if you strictly avoid code or can't troubleshoot basic technical issues.
Brand-disciplined. You can execute within established brand guidelines while pushing the visual quality forward. You work with the brand and product design team to develop components that are on-brand, not just on-trend. This is unlikely to be a good fit if you prefer to define your own visual direction or struggle to design within constraints.
This Role Is NOT
Benefits