The homepage says "Loved by 70,000+ engineers" and shows 12 customer logos, but the customers page has exactly one story. That one story, Goblins, is the strongest page on the site: ~60 to 300+ merged PRs a week, 98% of merged PRs built or reviewed by Capy, 14,000+ reviews, and a video. Supermemory, RunPod, Firecrawl, Exa, Million, Autumn and the rest are on the homepage with no proof behind them, in a market the engineering post itself calls crowded.
First action
Ask the three most active logo customers for a 20-minute call and permission to use their PR numbers.
How to measure it
Published stories
- Now
- –
- Target
- 8
- By
- 90 days
Steps
Rank the logos
By usage and willingness; start with the three most active teams.
Member of Growth Staff 1 day
Pull the numbers
Merged PRs before and after, share built or reviewed by Capy, reviews run.
Member of Technical Staff 2 days
Interview
Pain, switch moment, what changed in the team's week.
Member of Growth Staff 1 week
Film
A short screen-and-face video like the Goblins one.
Member of Growth Staff 1 week
Publish weekly
Same layout as Goblins, with a team-size and use-case filter.
Member of Growth Staff weekly
Link the logos
Each homepage logo links to its story with the headline number.
Member of Technical Staff 1 day
Reuse
Clips for X, Discord and outbound sequences.
Member of Growth Staff ongoing
Measure
Signup and paid conversion for sessions that view a story.
Member of Growth Staff monthly
Why it works
Use the Goblins template for every logo: before and after merged PRs, share built or reviewed by Capy, review count, the pain that triggered the switch, and a short video. Pull the PR numbers from Capy's own data (with each customer's permission), so every story has hard figures instead of quotes. Ship one a week, add a filter by team size and use case, and put the headline number on each homepage logo.
Developer buyers trust measured results from teams like theirs, and the growth role already owns customer calls and video. Each story also answers the "does this hold on a real codebase" question that comparison pages cannot.
Ready to use
ChecklistCustomer story kit
[ ] Permission to use PR metrics [ ] Merged PRs per week, before and after [ ] Share of merged PRs built or reviewed by Capy [ ] Reviews run [ ] The pain that triggered the switch [ ] Three quotes from engineers [ ] 2-3 minute video [ ] Industry, team size, features used [ ] Link from the homepage logo
Risks and how to handle them
Customers decline to share numbers
Offer ranges or percentages, and credits as thanks.
Stories look the same
Lead each with a different use case: review, bug triage, migrations, E2E testing.
Evidence
- Your websiteHomepage: H1 "The best AI software engineer"; "Orchestrate a fleet of cloud coding agents in all of the apps your team already lives in."; "Loved by 70,000+ engineers at" followed by 12 logos (Y Combinator, Supermemory, RunPod, Revyl, Million, Loop, Goblins, Firecrawl, Finta, Exa, Autumn, Aside AI). It shows Terminal-Bench results, bring-your-own-subscription, automations, a review agent and a Slack integration.Source
- Your websiteCustomers page (checked October 23, 2026): the filter reads "All [1]"; the only story is Goblins. The Goblins story reports merged pull requests going from "~60" to "300+ a week" with the same small team, "1,363 (98%)" of 1,392 merged PRs built or reviewed by Capy between September 10 and October 10, 2026, and "more than 14,000 reviews", with a 2:42 video.Source
- HiringMember of Growth Staff (San Francisco, posted October 6, 2026; $200K-$250K plus 0.5%-1% equity): "Growth at Capy is about getting developers to find Capy, try it, and bring their team." The role builds "Outreach and lifecycle automation, enrichment and qualification pipelines, landing pages, onboarding flows, demos", talks to customers "a lot", makes "Articles, videos, and demos about Capy ... launch videos, side-by-side comparisons, and benchmarks included", and runs "Hackathons, meetups, dinners, and workshops, often with other startups and developer communities".Source
- HiringMember of Technical Staff (posted October 6, 2026): "AI coding is a crowded market now, and developers expect first-minute magic and a quality bar that holds across every surface." The role spans the React web app, Electron desktop app, agent loop, backend and Kubernetes infrastructure, and "Talk to users". Capy says "We build Capy with Capy: our own PRs, reviews, and automations run through it."Source