> ## Content Index
> Fetch the complete content index at: https://www.antoinebuteau.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Lessons from Justin Gage
- URL: https://www.antoinebuteau.com/lessons-from-justin-gage/
- Published: 2025-08-08T02:33:21.000Z
- Updated: 2026-11-04T21:32:06.000Z
- Description: Justin Gage approaches marketing to technical audiences through authentic, helpful engagement, treating developers as practical, solution-oriented people. His philosophy invites marketers to study usefulness and credibility before reaching for persuasion, performance, or promotional polish.
- Author: Antoine Buteau
- Tags: Profile, GTM, Sales & Marketing, Business Leaders & Executives Profiles

Justin Gage is VP of Marketing at Amplify Partners. In his own account, effective developer marketing means understanding the audience, helping it, and communicating with practical specificity. — [Justin Gage at Amplify Partners](https://www.amplifypartners.com/team/justin-gage?ref=antoinebuteau.com).

![Infographic for "Lessons from Justin Gage".](https://www.antoinebuteau.com/content/images/2026/07/c3620035-5996-4f35-9202-f584e538d998-11bd8565-dbfa-42e5-ad33-0e8b4b7ef290-optimized.webp)

## On Marketing to Technical Audiences

1. **Understand and help the audience:** Gage says developer marketing starts with understanding the audience and helping it, as with marketing to anyone else. — [Justin Gage at Amplify Partners](https://www.amplifypartners.com/team/justin-gage?ref=antoinebuteau.com).
2. **Be specific with developers:** Gage describes developers as practical and solution-oriented; he recommends specific, useful communication rather than vague promotion. — [Justin Gage at Amplify Partners](https://www.amplifypartners.com/team/justin-gage?ref=antoinebuteau.com).
3. **Know the work behind the product:** Gage roots his developer-marketing experience in having built software himself, while explicitly downplaying his own engineering skill. — [Justin Gage at Amplify Partners](https://www.amplifypartners.com/team/justin-gage?ref=antoinebuteau.com).
4. **Help technical founders reach users:** At Amplify, Gage describes his role as helping founders put products in front of developers and data teams through sites, blogs, community and documentation. — [Justin Gage at Amplify Partners](https://www.amplifypartners.com/team/justin-gage?ref=antoinebuteau.com).
5. **Meet developers in their context:** Gage’s account emphasizes understanding technical audiences and giving them useful, specific material in the form they need. — [Justin Gage at Amplify Partners](https://www.amplifypartners.com/team/justin-gage?ref=antoinebuteau.com).
6. **Go-to-market matters in crowded markets:** In a crowded developer-tool market, Gage argues that good engineering alone is insufficient to attract attention; go-to-market deserves deliberate work. — [There Are a Lot of Developer Tools Out There](https://www.amplifypartners.com/blog-posts/there-are-a-lot-of-developer-tools-out-there?ref=antoinebuteau.com).
7. **Bring creative energy to sales and marketing:** Gage urges technical founders to treat sales and marketing as creative work rather than a necessary evil when many capable products compete for attention. — [There Are a Lot of Developer Tools Out There](https://www.amplifypartners.com/blog-posts/there-are-a-lot-of-developer-tools-out-there?ref=antoinebuteau.com).
8. **Do not mistake PR wire distribution for discovery:** In his satirical launch guide, Gage warns that developers are unlikely to discover tools through PR Newswire or embargoed exclusives alone. — [How Not to Launch Your Developer Tool](https://www.readamplified.com/how-not-to-launch-your-developer-tool?ref=antoinebuteau.com).

## On Writing and Content Creation

1. **Learn from ignored writing:** Gage says much of his writing drew little attention, and he sees that experience as part of becoming a better writer. — [Justin Gage at Amplify Partners](https://www.amplifypartners.com/team/justin-gage?ref=antoinebuteau.com).
2. **Expect uneven reception:** Gage contrasts work that reached Hacker News with posts that barely drew a response; a single hit does not mean every piece will land. — [Justin Gage at Amplify Partners](https://www.amplifypartners.com/team/justin-gage?ref=antoinebuteau.com).
3. **Write for a reader you understand:** Gage says Technically became clearer when he wrote for the non-technical version of himself from five years earlier. — [Substack Grow Interview](https://on.substack.com/p/grow-series-17-justin-gage).
4. **Choose a topic you can sustain:** In his Substack interview, Gage warns that a newsletter built around what others expect, rather than the writer’s own interest, is hard to maintain. — [Substack Grow Interview](https://on.substack.com/p/grow-series-17-justin-gage).
5. **Early founders often need more marketing:** Gage argues that many early technical founders suffer less from bad marketing than from doing too little of it. — [Marketing Planning 101 for Technical Founders](https://www.amplifypartners.com/blog-posts/marketing-planning-101-for-technical-founders?ref=antoinebuteau.com).
6. **Consistency gives marketing a chance:** Gage says technical founders often fail to produce marketing work consistently enough for it to have an effect; a basic plan can make the activity repeatable. — [Marketing Planning 101 for Technical Founders](https://www.amplifypartners.com/blog-posts/marketing-planning-101-for-technical-founders?ref=antoinebuteau.com).
7. **Choose a sustainable writing cadence:** Gage describes publishing Technically about every two to two-and-a-half weeks while holding a full-time job; a writing practice has to fit the writer’s actual capacity. — [Substack Grow Interview](https://on.substack.com/p/grow-series-17-justin-gage).
8. **Stay technically current through small projects:** Gage says he keeps close to developer work through marketing pages, small frontend changes and side projects, even without being a full-time engineer. — [Justin Gage at Amplify Partners](https://www.amplifypartners.com/team/justin-gage?ref=antoinebuteau.com).
9. **Reject hollow generated copy:** Gage criticizes formulaic generated writing that conveys little information; this is his editorial judgment, not a measured claim about every business. — [Amplify Writing Fellowship](https://www.amplifypartners.com/blog-posts/announcing-the-amplify-writing-fellowship?ref=antoinebuteau.com).
10. **Technical work can foster deep writing:** Gage argues that engineers and researchers often bring a valuable habit of detail, standards and careful qualification to substantive writing. — [Amplify Writing Fellowship](https://www.amplifypartners.com/blog-posts/announcing-the-amplify-writing-fellowship?ref=antoinebuteau.com).
11. **Invest in deep research and writing:** Gage presents sustained research and thoughtful writing as an alternative to attention-seeking, low-information content. — [Amplify Writing Fellowship](https://www.amplifypartners.com/blog-posts/announcing-the-amplify-writing-fellowship?ref=antoinebuteau.com).

## Advice for Technical Founders

1. **Keep a simple marketing plan:** Gage argues that even an early technical founder can use a basic marketing plan to produce more consistent work and understand how it supports growth. — [Marketing Planning 101 for Technical Founders](https://www.amplifypartners.com/blog-posts/marketing-planning-101-for-technical-founders?ref=antoinebuteau.com).
2. **Connect activities to growth outputs:** Gage’s planning framework distinguishes output goals such as site visits or signups from input activities such as articles and events, so marketing effort can be examined concretely. — [Marketing Planning 101 for Technical Founders](https://www.amplifypartners.com/blog-posts/marketing-planning-101-for-technical-founders?ref=antoinebuteau.com).
3. **Define a launch objective:** Gage’s reverse-advice launch essay warns founders to decide what a launch is for before choosing channels or tactics. — [How Not to Launch Your Developer Tool](https://www.readamplified.com/how-not-to-launch-your-developer-tool?ref=antoinebuteau.com).
4. **Treat launch as a beginning:** Gage argues a developer-tool launch is better treated as the start of ongoing market engagement than as a single make-or-break event. — [How Not to Launch Your Developer Tool](https://www.readamplified.com/how-not-to-launch-your-developer-tool?ref=antoinebuteau.com).
5. **Ask the buyer’s hard questions:** Gage urges founders to step outside a launch-day mindset and consider the questions prospective buyers will actually ask. — [How Not to Launch Your Developer Tool](https://www.readamplified.com/how-not-to-launch-your-developer-tool?ref=antoinebuteau.com).
6. **Technical literacy improves collaboration:** Gage argues that understanding how software is built can help non-engineers work with engineers and improve their own workflows. — [How to Excel in Tech Without Learning to Code](https://future.com/excel-in-tech-without-learning-to-code/?ref=antoinebuteau.com).
7. **Literacy does not require becoming a coder:** Gage distinguishes learning how code and software work from becoming a professional programmer; the former can still help non-engineers in tech. — [How to Excel in Tech Without Learning to Code](https://future.com/excel-in-tech-without-learning-to-code/?ref=antoinebuteau.com).
8. **Reconsider deployment overhead for small agent-built tools:** In a coauthored investment thesis, Pruss and Gage argue that traditional build-and-deploy machinery can outweigh the effort of creating small tools with coding agents; they limit the example to modest internal applications. — [exe.dev and the Perfect Little Computer](https://www.amplifypartners.com/blog-posts/exe-dev-and-the-perfect-little-computer?ref=antoinebuteau.com).
9. **Protect agent credentials:** Pruss and Gage highlight keeping integration tokens off agent-accessible VMs as a way to reduce credential-exfiltration risk and the blast radius of compromise. — [exe.dev and the Perfect Little Computer](https://www.amplifypartners.com/blog-posts/exe-dev-and-the-perfect-little-computer?ref=antoinebuteau.com).
10. **Production needs more than an academic idea:** Gage notes that making text-diffusion models usable in production required solving practical inference and caching problems beyond the original research idea. — [Every Token, Everywhere, All at Once](https://www.amplifypartners.com/blog-posts/every-token-everywhere-all-at-once?ref=antoinebuteau.com).

## On Venture Capital and the Tech Industry

1. **Question the special criticism of VCs:** A 2019 Gage tweet asks why venture capitalists draw unusually broad criticism and parody. This is a question he posed, not a demonstrated conclusion about the profession. — [Gage Tweet in Dunking on VCs](https://99d.substack.com/p/dunking-on-vcs).
2. **Treat model access as infrastructure:** In their exe.dev thesis, Pruss and Gage describe LLM-token access as a proposed fifth compute primitive alongside CPU, memory, storage and networking. This is a design view, not a settled standard. — [exe.dev and the Perfect Little Computer](https://www.amplifypartners.com/blog-posts/exe-dev-and-the-perfect-little-computer?ref=antoinebuteau.com).
3. **Faster inference could change RL economics:** Gage argues that if diffusion models substantially speed up generation, reinforcement-learning pipelines could spend less time on inference relative to training. He presents this as a conditional scaling possibility, not a demonstrated universal law. — [Every Token, Everywhere, All at Once](https://www.amplifypartners.com/blog-posts/every-token-everywhere-all-at-once?ref=antoinebuteau.com).
4. **Understand Runway’s frame-by-frame model:** Gage describes Runway’s GWM-1 as autoregressive and causal, generating shorter video chunks from prior context rather than producing an entire clip bidirectionally. The claim is specific to Runway’s architecture. — [The Infrastructure Behind Runway Characters](https://www.amplifypartners.com/blog-posts/the-infrastructure-behind-runway-characters?ref=antoinebuteau.com).
5. **Causal training changes the context available:** Gage explains that an autoregressive video model must train using prior context rather than looking ahead to future frames, making frame-by-frame generation more demanding. — [The Infrastructure Behind Runway Characters](https://www.amplifypartners.com/blog-posts/the-infrastructure-behind-runway-characters?ref=antoinebuteau.com).

---

Learn more:

1. [Justin Gage — Amplify Partners Team](https://www.amplifypartners.com/team/justin-gage?ref=antoinebuteau.com)
2. [Welcome Justin Gage — Amplify Partners](https://www.amplifypartners.com/blog-posts/justin-gage?ref=antoinebuteau.com)
3. [There Are a Lot of Developer Tools Out There — Justin Gage](https://www.amplifypartners.com/blog-posts/there-are-a-lot-of-developer-tools-out-there?ref=antoinebuteau.com)
4. [How to Excel in Tech Without Learning to Code — Justin Gage](https://future.com/excel-in-tech-without-learning-to-code/?ref=antoinebuteau.com)
5. [Marketing Planning 101 for Technical Founders — Justin Gage](https://www.amplifypartners.com/blog-posts/marketing-planning-101-for-technical-founders?ref=antoinebuteau.com)
6. [Dunking on VCs — Embedded Justin Gage Tweet](https://99d.substack.com/p/dunking-on-vcs)