Suggested projects
Requests from calls, tickets and Slack, ranked by how many customers asked. You approve what gets built.
Works with Jira and Linear, or on its own
Stop guessing what to build and chasing status updates. Devplan gives your whole company shared product context, turns it into agent-ready specs, and tracks work automatically.
$100 free credits, no card.
Knowledge
Here's what changed across your product, customers and delivery work.
Generated today · 08:00∿Daily reportPreferences →
Product updates
Finance teams can now pick their export columns. 14 customers asked for it.
2 sourcesReminders now send from one queue, so retries no longer double-send.
1 sourceWatch list
It waits on the auth team's API change. Two open deals depend on it.
3 sources▢My projectsAll →
▦Dashboard updates
Answers from your code, customers and decisions, with sources.
Why did we move bulk-edit for invoices behind SSO?
Weaver
It was moved in the October 12 planning review. Three things decided it:
Bulk-edit is next in line once SSO ships.
Decision · Oct 12 planning
#product thread
Sales call · Corvo
2 open deals
6 tickets
Ask anything about your product…↑
Evidence-backed proposals that need attention.
Corvo Logistics and Orbital Health need single sign-on before they can roll out.
Sales call · Corvo
Zendesk ticket
#sales
2 open deals
CLCorvo Logistics$48k ACVOHOrbital Health$31k ACV+7 customers
Clients want to pay large invoices in instalments.
8 Intercom chats
3 calls
TWTallis & Webb$22k ACVFSFernhill Studio$9k ACV+10 customers
Accounts with many clients want to move due dates in one step.
KDKestrel Dental$6k ACV+5 customers
WeaverDefine project · SSO for admins
Drafting the spec from 9 customer requests, 2 open deals and your code…
Should SSO cover all admins, or only workspace owners?
All adminsOwners only
Which identity providers should we support first?
Okta and GoogleAzure ADAny SAML
Thinking…
✓Project created
← Back to Proposals
Priority score82 · High
Estimate5–8 days
StatusSignalsDefinitionExecution 5Tech Spec
Jira Sync
Linear Sync
In scope · 5
✓SAML sign-in for admins
✓Map identity-provider roles
✓Session timeout settings
Audit log for sign-ins
Docs and release note
Estimate
Days5–8
Effort35–46 h
Sized from your code · confidence p10 to p90
Shareable, evidence-backed dashboards for recurring product questions.
Engineering
Product
PRs merged4↑ 2 vs yesterday
Tickets closed6↑ 1
Blockers1Same as yesterday
JJon
DoneSAML sign-in for admins
NextAudit log for sign-ins
BlockedWaiting on the auth team's API change
PPriya
DoneSession timeout settings
NextDocs and release note for SSO
No blockers
KKai
DoneOne queue for invoice reminders
NextBug: duplicate tax line on PDFs
No blockers
LLeo
DoneBug: reminder sent twice on retries
NextPartial payments: first spec review
No blockers
14 commits · 4 PRs
6 tickets moved
#eng thread
Average cycle time4.6 d↓ 0.4 d vs last month
PRs merged31↑ 5
Wait for first review1.8 d↑ 0.9 d
Cycle time, last 6 weeks
Review is the slowest step. PRs wait 1.8 days for a first review. It was 0.9 days a month ago.
Features52%Goal 60% · ↓ 6 vs Sep
Bugs23%Goal 15% · ↑ 8
Tech debt17%Goal 20% · ↓ 2
Other8%Goal 5% · Same
Last 3 months
Aug
Sep
Oct
Bugs went from 15% to 23% in one month. Most of the extra time went to invoice reminder retries.
Requests this week48↑ 12 vs last week
New requests3Spanish reminders, +2
Revenue at stake$116k↑ $31k
SSO for admins9 customers$79k at stake
Partial payments on invoices12 customers$31k at stake
Bulk-edit invoice due dates6 customers$6k at stake
Reminder emails in Spanish4 customersNew this week
11 calls
23 tickets
9 chats
5 deals
Signals this week7↑ 3
Threats1Quillbill free SSO
Opportunities2Pricing, search demand
ThreatQuillbill added SSO to its free planTwo of our open deals compared us with Quillbill this month. · Oct 21Changelog
OpportunityTallywren raised prices for teams over 10 seatsCould help our mid-market pipeline. · Oct 19Pricing page
Opportunity"Invoice automation" searches up this quarterMatches the rise in reminder requests. · Oct 16Search trends
Shipped2↑ 1 vs last week
At risk1SSO for admins
Decisions2Both with sources
ShippedCSV export with custom columnsRelease note sent to the 14 customers who asked.PR #412
ShippedInvoice reminders on one queueRetries no longer send a reminder twice.PR #418
At riskSSO for admins, 2 days behindWaits on the auth team's API change.3 sources
DecidedBulk-edit moves behind SSOOctober 12 planning review.Decision
DecidedSpanish reminders go in the Q1 plan4 customers asked, 2 in Mexico.#product
Connect your tools once. Devplan reads them and keeps everything linked.
9 connectedSlackChat
Synced 2 min agoMicrosoft TeamsChat
Connect nowLinearPlanning
Synced 1 min agoJiraPlanning
Connect nowZendeskSupport & CRM
Synced 4 min agoIntercomSupport & CRM
Synced 6 min agoHubSpotSupport & CRM
Synced 12 min agoSalesforceSupport & CRM
Connect nowGitHubCode
Synced just nowGitLabCode
Connect nowBitbucketCode
Connect nowZoomCalls
Synced 1 h agoGranolaCalls
Connect nowNotionDocs
Synced 18 min agoConfluenceDocs
Connect nowGoogle DriveDocs
Connect nowClaude CodeAI agents
Connected over MCPCursorAI agents
Connect nowCodexAI agents
Connect nowWhat was decided, when and why. Linked to the evidence.
1 open contradictionThe Q1 plan says "no new payment features", but partial payments has $31k in open deals behind it.Review
SSO starts with Okta and Google
Oct 6 · Maya · when the SSO project was defined
Why: the two identity providers customers asked for most.
Sales call · Corvo
3 tickets
Bulk-edit moves behind SSO
Oct 12 · Maya, Jon, Priya · planning review
Why: two open deals need SSO; no deal waits on bulk-edit.
Planning notes
#product thread
2 open deals
Spanish reminders go in the Q1 plan
Oct 20 · Maya · #product
Why: 4 customers asked, 2 in Mexico.
#product
4 chats
Invoice reminders move to one queue
Oct 8 · Jon · PR review
Why: retries were sending reminders twice.
PR #418
5 tickets
Every call, ticket and message, matched to the customer and the request it's about.
LiveSales call · Corvo Logistics · 2 h ago“We can't roll out until admins can log in with Okta.”
→ SSO for adminsTicket #4821 · Orbital Health · 3 h ago“Our admins got locked out again this morning.”
→ SSO for adminsChat · Tallis & Webb · 5 h ago“Can a client pay half now and half next month?”
→ Partial payments#sales · Priya · Yesterday“Fernhill asked about instalments again on today's call.”
→ Partial paymentsDeal note · Kestrel Dental · Yesterday“They want to move 40 due dates at once.”
→ Bulk-edit due datesRadar: your personalized daily report of what changed across code, calls and Slack.
Built by engineers from Meta, Snap and Amazon. Backed by a $2.5M seed round.
The problem
Code got fast. Planning, deciding and sharing context didn't. The work around the code now takes longer than the code.
01
You learn where projects stand in standups, not from the work.
“At some point the updates kind of became the work.”r/EngineeringManagers · July 2026
02
Requirements sit in Slack threads and memory, so the wrong thing ships.
“…how much of this job only ever exists in people's heads.”r/EngineeringManagers · June 2026
03
Estimates made at kickoff fall apart once the code starts moving.
“It's not planning if nothing survives.”r/ExperiencedDevs · February 2026
Product intelligence
Devplan does the busywork at every step. Your team makes the calls.
Requests from calls, tickets and Slack, ranked by how many customers asked. You approve what gets built.
Written from customer requests and your code. Every line links to its source.
A first estimate from your code. Your leads adjust it.
Tickets in Jira or Linear. Claude Code, Cursor and Codex get the spec.
Status updates itself from your code. A daily digest lands in Slack and email.
See what's slipping and why. Ask for any dashboard in plain words.
Spec-driven development, built in. New to specs?
Start with the free PRD template →Where your team already works
Devplan for Slack
Anyone on the team can ask what shipped, what's next and what customers asked for, and get an answer with sources in seconds.
See Devplan for Slack →Devplan for Claude Code
Claude Code gets your specs, customer requests and the decisions behind them, inside the workflow you already use. One command to connect.
See Devplan for Claude Code →Why it works
Your code, customers and decisions, linked to evidence and remembered over time. Ask it in Slack, or let your coding agents build from it over MCP.
Product tours
A two-minute product tour and quick updates on what's new.
Customer stories

“The change summaries from you guys are honestly already customer-grade, so we just light-edit and don't have to rewrite. That's the whole reason it works.”
Sahil NaikwadiCo-founder, Tato
How Tato sends customer-grade release updates every week
Read the story →“For bigger projects and consistent execution, Devplan was the obvious answer.”
Andrew FoongHead of Eng, Eight Sleep
Eight Sleep: consistent execution on bigger projects
“The Devplan knowledge graph was the missing link between our code, conversations and AI agents. We now track every project in the platform. If it’s not in Devplan, it doesn’t exist!”
Sergey S.VP of Engineering, Axiad
Axiad: every project tracked in Devplan

“We are running our 15 person VC-backed company right now without a PM. Devplan helps fills that gap for us by generating high-quality user stories that sync in Linear in minutes. What used to take me days of back and forth and refinement I’m now doing in less then a hour”
Andrew N.Founder, First
First: a 15-person company running without a PM

“Holy hell this is slick. So much value-add, even in the first few minutes.”
Jasper C.CTO, Aarden AI
Aarden AI: value in the first few minutes
“Using Devplan felt like magic. I just typed out rough ideas, and it helped turn them into clear plans, tasks, and roadmaps in minutes. It actually understood what I was trying to build and made the whole process way faster and easier. Honestly, it felt like having an experienced PM working with me.”
Omar S.Founder, Devmarketing
Devmarketing: from rough ideas to plans in minutes
Integrations
Connect your tools in minutes. Devplan reads where the work already happens, and sends specs and tickets back there. Keep your tools, or run Devplan on its own.
Questions
Devplan is AI-native product management software for software teams. It reads customer feedback from calls, tickets and Slack, ranks what customers ask for by demand, impact and effort, and turns it into PRDs, tech specs and tickets your engineers and AI coding agents can build. It keeps one live product brain that your whole team and your AI agents work from.
Devplan turns customer feedback into ranked projects, PRDs and Jira or Linear tickets. It reads feedback from calls, tickets and Slack, groups related requests, scores them by customer demand, impact and effort, and writes a spec grounded in your code, with a source on every line. Specs become fully formed tickets, or go straight to AI coding agents like Claude Code.
Devplan works with Jira and Linear, but they aren't required. Devplan specs and features work standalone or they become tickets in the tool you already use, and status flows from real work.
Devplan starts free with $100 in credits and no credit card. Paid plans use one shared monthly credit pool with no per-seat charge, so every team can use it. Enterprise plans are custom. See pricing.
Devplan is for when a whole team needs it, though you can connect Claude to a few tools yourself. Devplan gives you context that stays current, is shared, respects permissions and is maintained as tools change, plus specs, tickets and tracking on top. Our build vs buy page lays out the cost of each option.
Devplan encrypts data in transit and at rest, respects the permissions from your source tools, and never uses your data to train Devplan or third-party models. Enterprise teams can self-host on GCP or AWS. See Devplan for enterprise.
Devplan writes PRDs and tech specs from customer interviews and other feedback. It reads call notes and transcripts from tools like Zoom and Granola, plus tickets and Slack, finds what customers keep asking for, and drafts the PRD grounded in your codebase. Every requirement links to the call or ticket it came from, so you edit instead of starting from a blank page.
Devplan does the product admin a small team doesn't have time for. It collects requests from calls, tickets and Slack, ranks them, drafts the spec, creates tickets or hands work to AI coding agents, and tracks progress from real work. Founders and engineers make the judgment calls; Devplan keeps the evidence, specs and status up to date.
Devplan fixes this by giving agents the why, not just the ticket. Through MCP, Claude Code, Cursor and Codex get the spec, the customer evidence behind it and past decisions, so they know what was intended and what's already settled. Specs written in Devplan also carry acceptance criteria and pointers to the right files.
Devplan can run your roadmap, backlog, specs, tickets, tracking and risk alerts, so you don't need a separate tracker. However, most teams use Devplan on top of their Jira and Linear setup to start.