[{"data":1,"prerenderedAt":402},["ShallowReactive",2],{"navigation":3,"\u002Foverview":28,"\u002Foverview-surround":399},[4,8,12,16,20,24],{"title":5,"path":6,"stem":7},"Overview","\u002Foverview","1.overview",{"title":9,"path":10,"stem":11},"The ICP","\u002Ficp","2.icp",{"title":13,"path":14,"stem":15},"Pete","\u002Fpete-the-indie-hacker","3.pete-the-indie-hacker",{"title":17,"path":18,"stem":19},"Max","\u002Fmax-the-product-engineer","4.max-the-product-engineer",{"title":21,"path":22,"stem":23},"Laura","\u002Flaura-the-founding-cto","5.laura-the-founding-cto",{"title":25,"path":26,"stem":27},"Marcus","\u002Fmarcus-the-platform-engineer","6.marcus-the-platform-engineer",{"id":29,"title":5,"body":30,"cover":392,"description":393,"extension":394,"meta":395,"navigation":396,"path":6,"persona":392,"seo":397,"stem":7,"__hash__":398},"personas\u002F1.overview.md",{"type":31,"value":32,"toc":380},"minimark",[33,37,40,44,52,56,161,164,168,190,194,197,204,207,211,214,299,303,359,363],[34,35,36],"p",{},"Polylane is proactive agents for production: agents that read your code, watch your infrastructure, detect issues, investigate them, and fix them. The brand promise is \"Nobody should be on-call in 2026.\" The go-to-market is bottom-up and self-serve: developer tools are consumer tools, win developers one at a time, no enterprise motion at this stage.",[34,38,39],{},"These personas were derived from a deep analysis of the product itself: its positioning and messaging, pricing and plan structure, onboarding funnel, lifecycle emails, console features, and the depth of each integration. They are inferences, not interview data. Treat them as a strong starting hypothesis to validate against real signup answers, founder check-in replies, and churn feedback.",[41,42,9],"h2",{"id":43},"the-icp",[34,45,46,47,51],{},"One ICP sits above the personas: ",[48,49,50],"a",{"href":10},"AI-pilled software teams at any scale",". The qualifier is temperament, not stage or headcount: the team ships with AI-first tools and is comfortable letting an agent do real work. The personas below describe who inside those teams; the ICP page describes which teams qualify and why.",[41,53,55],{"id":54},"the-personas","The personas",[57,58,59,81],"table",{},[60,61,62],"thead",{},[63,64,65,69,72,75,78],"tr",{},[66,67,68],"th",{},"#",[66,70,71],{},"Persona",[66,73,74],{},"Archetype",[66,76,77],{},"Typical plan",[66,79,80],{},"One line",[82,83,84,104,123,142],"tbody",{},[63,85,86,90,95,98,101],{},[87,88,89],"td",{},"1",[87,91,92],{},[48,93,94],{"href":14},"Pete, the indie hacker",[87,96,97],{},"Indie hacker \u002F solo founder",[87,99,100],{},"Free → Starter ($80)",[87,102,103],{},"Solo builder on Cloudflare or Vercel who is their own on-call and finds out about outages from customers",[63,105,106,109,114,117,120],{},[87,107,108],{},"2",[87,110,111],{},[48,112,113],{"href":18},"Max, the product engineer",[87,115,116],{},"Software engineer",[87,118,119],{},"Max ($200) or a seat on Team",[87,121,122],{},"Full-stack engineer at a small startup, ships daily with a coding agent, dreads the pager",[63,124,125,128,133,136,139],{},[87,126,127],{},"3",[87,129,130],{},[48,131,132],{"href":22},"Laura, the founding CTO",[87,134,135],{},"Exec (CTO \u002F VP Engineering)",[87,137,138],{},"Team ($200)",[87,140,141],{},"Player-coach CTO of a 10-40 person startup buying leverage instead of an SRE hire",[63,143,144,147,152,155,158],{},[87,145,146],{},"4",[87,148,149],{},[48,150,151],{"href":26},"Marcus, the platform engineer",[87,153,154],{},"SRE \u002F DevOps \u002F platform",[87,156,157],{},"Team → Enterprise",[87,159,160],{},"Pragmatic platform engineer at an AWS\u002FKubernetes scale-up, evaluates cautiously, secondary persona today",[34,162,163],{},"Priority order matters. Pete and Max are the bullseye and match the beachhead strategy: developers on fast-growing cloud platforms (Cloudflare, Vercel, Supabase, Railway, Fly.io) who ship faster than anyone and have almost no native operations tooling. Laura converts individual adoption into a team account. Marcus is the expansion persona: several tools he considers table stakes (PagerDuty, Grafana, GitLab, Terraform-aware linking) are not live yet.",[41,165,167],{"id":166},"what-all-personas-share","What all personas share",[169,170,171,175,178,181,184,187],"ul",{},[172,173,174],"li",{},"They are developers or ex-developers. The product's docs and console assume fluency with cloud providers, metrics, logs, traces, Git and PR workflows, and MCP. Nothing is written for a non-technical buyer.",[172,176,177],{},"They already use an AI coding agent daily (Claude Code, Cursor, Codex, or similar). The fastest onboarding path is handing that agent one setup prompt.",[172,179,180],{},"They ship on modern platforms through GitHub. GitHub is the only live code host; the deepest cloud integrations are Cloudflare, AWS, Vercel, Render, Fly.io, Kubernetes, and PlanetScale, with Datadog, Honeycomb, Axiom, Sentry, and Slack alongside.",[172,182,183],{},"They are allergic to noise. Every persona has been burned by alert spam. The product's stance that silence is a feature, and that the default verdict is \"no anomaly\", is a prerequisite for trust with all four.",[172,185,186],{},"They carry on-call pain in some form, from \"my phone is the pager\" (Pete) to \"I own the rotation's quality\" (Marcus).",[172,188,189],{},"They respond to the same product taste: dense, fast, restrained, opinionated, closer to Linear than to a dashboard vendor.",[41,191,193],{"id":192},"the-shared-journey-skeleton","The shared journey skeleton",[34,195,196],{},"Every persona walks the same ladder; they differ only in how fast, how alone, and how skeptically.",[34,198,199],{},[200,201],"img",{"alt":202,"src":203},"The shared journey","\u002Fdiagrams\u002Fshared-journey.svg",[34,205,206],{},"The details that vary by persona: a work email produces a company-named workspace with optional domain auto-join, a personal email a solo one; disposable domains are rejected outright; reminder emails nudge each unconnected rung over the first two weeks, personalized by what the product finds in already-connected repos; and founder check-in emails arrive at signup and on churn signals.",[41,208,210],{"id":209},"how-plans-segment-the-personas","How plans segment the personas",[34,212,213],{},"Plans are grouped into Individual (Starter, Max) and Team (Team, Enterprise). The unit of value is credits: cost-weighted AI tokens, where heavier models burn more credits per response. Overage is metered in small increments with a default monthly spending cap. Upgrade pressure comes from the credit pool, the automatic-incident cap, and cloud-account limits.",[57,215,216,232],{},[60,217,218],{},[63,219,220,223,226,229],{},[66,221,222],{},"Plan",[66,224,225],{},"Price",[66,227,228],{},"Seats",[66,230,231],{},"Built for",[82,233,234,247,260,272,285],{},[63,235,236,239,242,244],{},[87,237,238],{},"Free",[87,240,241],{},"$0",[87,243,89],{},[87,245,246],{},"Pete trying it out: 2 clouds, 1 automatic incident per day",[63,248,249,252,255,257],{},[87,250,251],{},"Starter",[87,253,254],{},"$80\u002Fmo",[87,256,89],{},[87,258,259],{},"Pete in production: 10 clouds, unlimited incidents, pay-as-you-go overage",[63,261,262,264,267,269],{},[87,263,17],{},[87,265,266],{},"$200\u002Fmo",[87,268,89],{},[87,270,271],{},"Max as a power user: unlimited clouds, 4x Starter credits, priority routing on frontier models",[63,273,274,277,279,282],{},[87,275,276],{},"Team",[87,278,266],{},[87,280,281],{},"up to 50",[87,283,284],{},"Laura's team: shared credits, shared memories and skills",[63,286,287,290,293,296],{},[87,288,289],{},"Enterprise",[87,291,292],{},"custom",[87,294,295],{},"unlimited",[87,297,298],{},"Marcus's org later: volume credit pricing, bring-your-own LLM key and AI gateway, bring-your-own cloud, dedicated support",[41,300,302],{"id":301},"where-to-reach-whom-summary","Where to reach whom (summary)",[57,304,305,317],{},[60,306,307],{},[63,308,309,311,314],{},[66,310,71],{},[66,312,313],{},"Best channels",[66,315,316],{},"Worst channels",[82,318,319,329,339,349],{},[63,320,321,323,326],{},[87,322,13],{},[87,324,325],{},"Cloudflare\u002FVercel marketplaces, X build-in-public circles, Hacker News, Product Hunt, dev YouTube, the shareable topology map itself",[87,327,328],{},"Cold email, LinkedIn ads, gated content",[63,330,331,333,336],{},[87,332,17],{},[87,334,335],{},"The PR comment surface itself, coding-agent communities, framework Discords, GitHub, word of mouth in team Slack, dev newsletters",[87,337,338],{},"Webinars, anything requiring a sales call",[63,340,341,343,346],{},[87,342,21],{},[87,344,345],{},"Their own engineers (bottom-up), founder and CTO communities, The Pragmatic Engineer-style newsletters, warm intros, the forwarded weekly digest",[87,347,348],{},"Cold outbound, feature-checklist comparisons",[63,350,351,353,356],{},[87,352,25],{},[87,354,355],{},"Deep technical blog posts, SRE\u002FDevOps newsletters and podcasts, KubeCon\u002FSREcon\u002FMonitorama hallways, r\u002Fdevops and r\u002Fsre, transparent security documentation",[87,357,358],{},"AI-magic marketing, anything hiding the IAM policy",[41,360,362],{"id":361},"anti-personas","Anti-personas",[169,364,365,368,371,374,377],{},[172,366,367],{},"Procurement-led enterprise buyers. No sales team, no SSO\u002FRBAC depth, no compliance paperwork motion yet, by explicit choice.",[172,369,370],{},"Dashboard power users who want another observability dashboard to stare at and hand-write queries in. The agent does the querying; the product positions against observability without action.",[172,372,373],{},"Legacy VM and datacenter shops. The integration surface assumes serverless and PaaS with config-file-driven deploys.",[172,375,376],{},"Non-GitHub teams, for now.",[172,378,379],{},"Anyone who wants a fully hands-off replacement for engineering judgment. Every persona still reviews and merges the fix.",{"title":381,"searchDepth":382,"depth":383,"links":384},"",1,2,[385,386,387,388,389,390,391],{"id":43,"depth":383,"text":9},{"id":54,"depth":383,"text":55},{"id":166,"depth":383,"text":167},{"id":192,"depth":383,"text":193},{"id":209,"depth":383,"text":210},{"id":301,"depth":383,"text":302},{"id":361,"depth":383,"text":362},null,"How the persona set was derived, what every persona shares, the journey they follow, and how plans and channels segment them.","md",{},{"title":5},{"title":5,"description":393},"nO803E8s3_p4IZ7OTMYo626w1k2dC0TfugLwK12johM",[392,400],{"title":9,"path":10,"stem":11,"description":401,"children":-1},"The ideal customer is a software team that is happy using AI-first tools, at any scale. Not teams building AI products; teams that build with AI.",1790523225097]