Form filled in.
Lead researched.
Your website’s contact form posts each lead to Jimothy. Claude Code researches the company on the web and writes a cited brief with a fit rating against your ideal customer, then a first reply is drafted. After you approve both, they go to your CRM.
- Research the company Claude Code · sonnet
- Draft first reply Claude API · sonnet
- Review lead you
- Send to CRM webhook
What the pipeline does for you
A brief with sources
What the company does, its size, recent news and signals that matter to you, with the URLs it came from. Guesses are labelled as guesses.
Fit against your ideal customer
You describe your ideal customer once. Every lead is rated strong, possible or weak, with a one-line reason.
A reply that proves you read it
The first reply answers their question, mentions one specific thing about their company and offers a call.
You see it before sales does
The brief and the reply wait together at an approval gate. Nothing reaches the CRM until you approve.
Four steps, once
- Import the Inbound lead research pipeline and describe your product and ideal customer in its variables.
- Triggers → Add trigger → Webhook, and send form submissions to it (directly or through Zapier).
- Set leadWebhookUrl to a catch hook that creates the contact in your CRM.
- Submit a test lead from your own form.
The research step uses Claude Code, which needs to be installed and signed in on the machine running Jimothy.
Same engine, different jobs
For engineering
Issues → pull requests
Hand off a Linear, Jira or GitHub issue. Agents plan, build and review it, and you approve the PR.
See how it runs →Schedule → Pull requestNightly maintenance
A schedule updates dependencies overnight, fixes what breaks, and opens a PR only if something changed.
See how it runs →GitHub → CommentSpecs from vague issues
A fuzzy issue gets a spec with acceptance criteria and open questions, posted back after you approve it.
See how it runs →Beyond engineering
Support reply drafts
New tickets are triaged and answered in your voice, within your policies. You approve before anything is sent.
See how it runs →Schedule → SlackWeekly product updates
Every Friday the week’s changes become a customer-facing “What’s new” post, ready to approve and publish.
See how it runs →Build your own
Agent, shell and approval steps in a DAG, started by an issue, a schedule or a webhook. Or describe it and let Jimothy draft the pipeline.