Earthly Lunar

Critical Assessment of Earthly.dev

Earthly has a massive technical advantage, but the landing page messaging leans too heavily into developer jargon instead of immediate, tangible benefits. The page assumes the visitor already understands the inherent problems with traditional CI/CD pipelines.

While DevOps engineers might understand "build automation for the post-container era," Engineering Managers and CTOs might miss the business value. You are selling a solution to a massive pain point: "It works on my machine but fails in CI."

The current above-the-fold experience relies too much on the visitor connecting the dots. We need to spoon-feed them the exact time and frustration they will save by using Earthly.

Your technical credibility is high, but your marketing hook needs to be sharper, more benefit-driven, and relentlessly focused on the user's primary pain points.

External Resources to Reference:

• CXL Guide to Value Propositions
• Donald Miller's StoryBrand Framework

Hero Text Effectiveness

The Headline

Problem: Standard messaging like "The build framework for the post-container era" is clever but vague. It describes what the product is, not what it does for the user.

Why it matters: Visitors decide to stay or leave within the first 3-5 seconds. If they have to parse complex terminology to understand your offering, they will bounce.

Recommended fix: Pivot the headline to address the universal developer pain point: inconsistent builds and slow CI.

• Focus on speed and reproducibility
• Speak directly to the end result
• Remove "era" buzzwords

The Subheadline

Problem: Technical descriptions often read like a GitHub repository README.md file rather than a marketing pitch.

Why it matters: The subheadline must bridge the gap between the bold claim in the headline and the technical reality of the product. It needs to explain how you deliver the benefit.

Recommended fix: Explicitly mention that Earthly combines the best of Makefiles and Dockerfiles to run anywhere.

• State the exact technologies it replaces or integrates with
• Mention the local-to-CI parity
• Keep it under two sentences

External Resources to Reference:

• Copyblogger: How to Write Magnetic Headlines

Value Proposition (The 5-Second Rule)

Clarity of Core Benefit

Problem: A visitor landing on the page has to scroll down or watch a terminal animation to fully grasp why Earthly is better than standard GitHub Actions or Jenkins.

Why it matters: The unique value proposition (UVP) must be immediately visible without scrolling. If they don't know why you are different immediately, you become just another tool in a crowded DevOps landscape.

Recommended fix: Ensure your three core pillars are visible above the fold.

• Reproducible: It works on my machine, so it works in CI.
• Fast: Caching makes builds lightning fast.
• Agnostic: Works with any CI provider.

External Resources to Reference:

• Nielsen Norman Group: How Long Do Users Stay on Web Pages?

Above the Fold Experience

Visuals and First Impressions

Problem: Terminal animations are great for developers, but they can move too quickly. This creates a cognitive load that distracts from the core messaging.

Why it matters: You want the visitor reading your value proposition, not trying to decipher scrolling bash scripts before the loop resets.

Recommended fix: Use a static, side-by-side code snippet comparison.

• Show a messy, standard CI script on the left (Red/Bad)
• Show a clean, simple Earthly Earthfile on the right (Green/Good)
• Add small tooltip annotations to highlight the caching benefits

External Resources to Reference:

• GoodUI: Evidence-based UI Patterns

Target Audience Alignment

Addressing the DevOps Pain Point

Problem: The messaging splits its focus between individual contributors and platform teams, occasionally muddying who the primary buyer is.

Why it matters: A software engineer wants to save time debugging. A DevOps manager wants to cut CI compute costs and standardize tooling across the company.

Recommended fix: Create clear self-selection pathways right below the fold.

• Add a section: "For Developers: Never debug a failed CI pipeline again."
• Add a section: "For DevOps Teams: Cut CI compute costs by 50% with advanced caching."
• Drive each persona to a tailored use-case page.

External Resources to Reference:

• HubSpot: How to Create Detailed Buyer Personas

Call to Action (CTA)

Prominence and Actionability

Problem: "Get Started" is a passive, generic CTA used by every SaaS company on the internet. It doesn't excite the developer or set expectations.

Why it matters: Developers are hesitant to click vague buttons because they fear being dropped into a high-friction enterprise sales funnel.

Recommended fix: Use a low-friction, action-oriented CTA that tells them exactly what happens next.

• Primary CTA: "Install Earthly (It's Free)" or "Copy Install Script"
• Secondary CTA: "Read the Docs" or "View Earthfile Examples"
• Place the exact terminal install command (brew install earthly/earthly/earthly) directly under the button.

External Resources to Reference:

• WordStream: 31 Call to Action Examples You Can't Help But Click

Before → After Concrete Suggestions

Example 1: The Main Headline

Before: "The build framework for the post-container era."

After: "Never debug a broken CI pipeline again."

Why this matters: The "after" focuses on the emotional and practical pain point. It immediately hooks any developer who has spent hours pushing empty commits just to trigger a CI run.

Example 2: The Subheadline

Before: "Earthly is a build automation tool that allows you to execute all your builds in containers."

After: "Write your build logic once in an Earthfile. Run it locally, in GitHub Actions, or anywhere else with 100% reproducibility and massive caching speedups."

Why this matters: The "after" explains exactly how it works (Earthfile), where it works (local + CI), and the ultimate benefits (reproducibility and speed).

Example 3: The Primary Call to Action

Before: [ Get Started ]

After: [ Install Earthly (Open Source) ]

Why this matters: Developers love open-source tools. Specifying that it is open source reduces friction and the fear of hitting a paywall.

Example 4: The Social Proof

Before: "Trusted by great companies."

After: "Over 10,000 developers use Earthly to cut build times in half."

Why this matters: Specific numbers build trust instantly. Transitioning from a vague statement to a hard metric proves your value proposition is real.

External Resources to Reference:

• VWO: How to Use Social Proof to Increase Conversions

Product Positioning Score: 8.5/10

Here is a strategic analysis and set of recommendations based on Earthly.dev’s current landing page positioning.

1. Amplify the "Why" in Problem-Solution Fit

Analysis: The core problem—the friction between local development and CI environments—is perfectly addressed by your main promise: "Builds that work the same locally and in CI." The classic "works on my machine" problem is universally understood by developers, and your solution is highly compelling. Recommendation: While the solution is obvious to Individual Contributors (ICs), you need to elevate the business problem for buyers (Engineering Managers/Directors). Translate "broken builds" into lost engineering hours. Consider adding a subheadline or hero text that quantifies the pain, such as: "Stop wasting 20% of your engineering hours debugging CI failures."

2. Elevate Feature Communication to Business Benefits

Analysis: Earthly highlights features beautifully for technical users (e.g., "Built-in caching," "Parallel execution," and "Multi-platform"). However, the copy leans slightly too heavily on the technical "how" rather than the outcome-driven "why." Recommendation: Connect these technical features directly to team velocity and cost benefits. Instead of just stating, "Earthly automatically executes targets in parallel," frame it as: "Ship features faster and cut CI compute costs with automatic parallel execution." Developers care about caching; Engineering Managers care about developer velocity.

3. Broaden Market Positioning for Team Adoption

Analysis: Your market positioning is laser-focused on software/DevOps engineers. It is instantly clear who uses the tool. However, standardizing a build tool across a company is a team-level or organizational decision, and the messaging currently lacks an enterprise-level hook. Recommendation: Create a distinct narrative for team leaders. Explain how Earthly helps a polyglot engineering team scale. Add a section highlighting how Earthly simplifies onboarding for new hires by standardizing the build pipeline across different languages and monorepos, reducing the "time to first commit."

4. Sharpen the Competitive Angle

Analysis: The copy "Like Dockerfile and Makefile had a baby" is an absolute masterclass in developer marketing. It instantly anchors Earthly against legacy tools, explains the syntax, and establishes your unique competitive angle (containerized isolation + familiar build targets). Recommendation: Lean even harder into how you integrate with existing CI tools (GitHub Actions, Jenkins, CircleCI) rather than competing directly with them. Explicitly state that Earthly doesn't force teams to rip out their current CI infrastructure—it makes it better. Make this a primary competitive differentiator with a bold statement like: "Don't replace your CI, fix it. Earthly makes your existing pipelines reproducible."

Bottom Line

Earthly has nailed grassroots, developer-first marketing. The copy is punchy, highly relatable, and technically accurate, successfully avoiding corporate jargon. To move from a beloved individual developer tool to an enterprise-wide standard, the positioning simply needs to layer in the macro-benefits for decision-makers: engineering velocity, compute cost reduction, and team standardization.