This is one skill of many.
Browse the full catalog to see everything your Righthand can take off your plate — and everything you can teach it later.
Gtm
Builds and maintains competitor intelligence for sales and marketing. Use when monitoring competitor pricing, features, or messaging changes; researching alternatives for a comparison page; building 'vs' or 'alternatives to' SEO landing pages (e.g. 'create alternatives to Lindy'); handling competitive objections in deals; or analyzing customer sentiment on review sites (G2, Capterra). Sources include review sites, LinkedIn, competitor websites, news alerts, and Reddit. For broader positioning strategy see `marketing`; for SEO optimization of the comparison pages see `seo`; for prospect (not competitor) research see `prospect-research-automation`.
Skills travel in packs — pick one and your Righthand arrives already equipped with everything the job needs.
The judgment layer on top of the daily rhythm — briefs and reviews that say where time should go, what's at risk, and what actually matters this week.
The whole growth engine as one hire — content in your voice every day, marketing across every channel that fits, outbound that runs itself, partnerships that share your customer, and one honest weekly number that says what is working.
Positioning, demand, and the full channel menu — website and search, paid, creators and community, events and press, lifecycle email, launches, proof, and the analytics that say which of them actually earned the pipeline, adopted as one.
The full outbound motion — ICP and trigger-based lists, sequences run as hypotheses, fast qualification, an honest CRM, prep for every sales call, and the monthly loop that turns every no into a sharper pitch, adopted as one.
Partner sourcing by the shared-customer test, outreach run as a pipeline, co-marketing written from the partner's side, a warm cadence with every active partner, and honest tracking of every referral and payout, adopted as one.
Positioning as a living artifact, rewritten when customers describe the product differently than the website does, and every customer-facing surface kept consistent with it.
Feedback synthesis, buildable specs, and a roadmap that admits what's slipping — the space between what users say and what the team builds.
The space between what users say and what the team builds. Feedback synthesized into themes, users talked to on a cadence and thanked when their issue ships, specs that surface disagreement before the code does, and a roadmap that admits what is slipping.
The research arm. Competitors, markets, and open questions get watched continuously and answered on demand, so decisions are made on current facts instead of stale impressions.
A full outbound motion, from an evidence-based ICP through prospect research, sequences run as hypotheses, follow-up, and a CRM that stays true to reality.
The engineering lead and product manager a founder wishes they could afford as one hire. Code shipped through coding agents against scenarios written first, delivery always visible, users listened to and measured, the system kept healthy, launches coordinated, and a rhythm that protects maker time.
The front door of partnerships. The ecosystem your customer already trusts gets mapped, and every month five candidates are tested against one question, can each side put the other in front of a shared customer, with the weak ones declined politely.
The decision-support layer — one-pagers and strawmen before every big call, the research the manager has no time for, and an at-a-glance status view with institutional memory, adopted as one.
Browse the full catalog to see everything your Righthand can take off your plate — and everything you can teach it later.