You'll own the platform surface of Saleshandy: the API and CLI that developers build on, the integrations that connect Saleshandy into a customer's existing stack (CRMs first, then the rest), the webhook layer that fires when things happen, and the Unified Inbox that brings replies back together. Your job is to make Saleshandy the easiest tool in a sales team's stack to connect, automate, and trust.
You'll partner with the platform engineering pod (API, CLI, webhooks) and the CRM integration engineers day-to-day. You're a product PM, not an engineer, but you'll be the person who reads the API docs end-to-end, runs the CLI yourself, fires a webhook and traces it through to delivery, and notices when something feels off long before a customer files a ticket.
The hardest part of this role is the breadth. Four connected surfaces (API, CRM integrations, webhooks, Unified Inbox) all need attention, and each one has its own customer, its own metric, and its own engineering partner. Holding the bar across all four without dropping any is what makes this role hard, and what makes the person who can do it valuable.
Typical candidates have 2-4 years of product management experience on a technical product, but we hire on demonstrated outcomes, not tenure or degree. If your track record fits the must-haves below, the year count is secondary.
-
Own the API and CLI roadmap. Decide which new capabilities ship next, write the developer-facing docs alongside engineering, and use the API yourself often enough to feel where it's clunky.
-
Own integration and CRM adoption. Make it easy for a customer to connect Saleshandy to HubSpot, Salesforce, Pipedrive, and the rest. Ship the automations and workflows that turn a connected CRM into actual revenue activity (sequences triggered from CRM events, prospects synced both ways, activity logged back).
-
Own webhook reliability as a product surface. Track success vs failure rates, build the diagnostic tools customers and support need when a webhook silently stops firing, and ship the remediations (retries, dead-letter queues, customer-facing delivery logs).
-
Own the Unified Inbox: the surface that brings replies from connected mailboxes back into Saleshandy. Ship the experiments that increase how much of a customer's reply workflow happens inside the product.
-
Run a weekly user-research loop with developers building on Saleshandy and operators wiring integrations into their stack. Turn what you hear into shipped product changes.
-
Define and track the platform metrics that matter: time-to-first-API-call for a new developer, % of accounts with at least one CRM connected and actively used, webhook success rate, integration-related support ticket volume, and Unified Inbox engagement.
-
Use AI tools (Claude Code, Cursor, and similar) as a daily part of how you research, draft specs, debug API behavior, analyze logs, and move work forward.
-
Demonstrated history shipping platform, API, or integration product work on a SaaS product. You can walk through specific capabilities you shipped, who used them, and what changed because of them.
-
Hands-on technical fluency. You read API documentation comfortably, you've made API calls yourself (Postman, curl, scripts), you understand REST conventions, webhook patterns, and authentication flows (OAuth, API keys, JWTs). You don't need a hand-hold to test a new endpoint.
-
Demonstrable computer-science or technical-systems fundamentals. By degree (IT or CS), structured coursework, certifications, or a portfolio of technical work. Degree path matters less than whether you can think in systems and protocols.
-
Direct user-research muscle. You've personally talked to developers and integration users, synthesized what you heard into shipped changes, and can show the line from a conversation to a release.
-
Comfort defining and reading product metrics end-to-end across both developer experience (time-to-first-call, API error rate) and customer outcomes (integration adoption, support load). You set the success criteria, instrument the change, and read results yourself.
-
AI-fluent in your daily work. You already use Claude Code, Cursor, or comparable tools to research, draft, analyze, debug, and ship faster, and can describe specific workflows where AI compressed your cycle time.
-
Prior PM experience on a sales-tech, marketing-tech, or CRM-adjacent product.
-
Hands-on experience with CRM platforms as a user (HubSpot, Salesforce, Pipedrive, Zoho, Close).
-
Comfort writing SQL or pulling data from product-analytics tools without an analyst.
-
Has shipped a public API or developer-facing product before.
The Saleshandy platform layer: the public API, the CLI, the webhook delivery system, the CRM integration suite (HubSpot, Salesforce, Pipedrive, and adjacent connectors), the Unified Inbox, and the automation and workflow layer that ties them together. Day-to-day you'll touch API logs, webhook delivery dashboards, CRM sync diagnostics, customer support transcripts on integrations, and the experimentation tooling.
You'll join Saleshandy's product org and partner day-to-day with two engineering pods: the platform pod (API, CLI, webhooks, Unified Inbox infrastructure) and the CRM integration pod (the connectors and the sync layer). You'll also work closely with the customer-success engineers who help customers wire Saleshandy into their stack, and with the Outreach Growth and Deliverability PMs on the seams between products. The next two quarters are focused on three things: cutting time-to-first-API-call for new developers, lifting the % of accounts with an actively-used CRM connection, and getting webhook success rates and customer-visible diagnostics to a place where reliability stops being a support topic.
Purpose: The platform layer is where Saleshandy stops being a tool and becomes part of a customer's revenue stack. Every integration you ship is one more reason a customer can't leave, and every API capability you open is one more team that can build on Saleshandy. This is the work that turns customers into long-term partners.
Growth: Few PM roles give you this much surface area this early. You'll own four connected products (API, integrations, webhooks, Unified Inbox), work directly with developers as users, ship customer-facing capabilities and reliability work in the same week, and build a track record across both technical depth and adoption work. That combination is what senior platform and developer-experience roles screen for.
Motivators: This role is built for someone who's genuinely excited by APIs as a product. If you've ever read a public API doc for a tool you love and thought "I want to make one of these," or if you find it satisfying to watch a webhook fire and arrive cleanly at its destination, this is your seat.
