Contact
Reach Jeremy Longshore at Intent Solutions — consulting, OSS, partnerships, and client engagements. Gulf Shores, Alabama; remote-first.
The fastest way to reach me is email. Everything else is a slower lane.
jeremy@intentsolutions.io — usually answered same day, almost always within 24 hours. If it’s been longer than that, it’s stuck in spam — DM on X or LinkedIn and I’ll dig it out.
What helps a first email
- What you’re trying to do, in plain language. Not “explore an AI strategy” — “we have 6,000 PDFs of inspection reports and want to ask them questions in Slack.”
- Where you are now. Codebase, vendor stack, who’s on the team, what’s already failed.
- What “done” looks like. Even a rough sketch — production for real users, internal demo, board update — is enough to scope the conversation.
- Timing. Soft deadline, hard deadline, or open-ended.
I don’t need a polished brief. A four-paragraph email beats a 30-page deck for getting to a useful first call.
Where I’m useful
| Lane | What that looks like |
|---|---|
| AI integration in production | Claude / MCP / RAG / Vertex AI Gemini systems with proper telemetry, evals, and recovery. The boring infrastructure included. |
| Operational AI | Workflow automation with n8n, Claude Code, and custom skills/agents. The “stop doing this manually” engagements. |
| Data foundations | BigQuery, Postgres, Firestore — schema design, ingestion pipelines, access posture. Built so the AI on top has clean inputs. |
| Rapid product builds | Hugo / Next.js / Astro front-ends with the deploy pipeline, monitoring, and runbooks done before launch. |
| Audits & second opinions | Code review, architecture review, AI-system reviews. Especially valuable when an internal champion needs an external voice. |
| OSS partnerships | Joint plugins/skills/integrations with the claude-code-plugins-plus-skills ecosystem and tonsofskills.com. |
Where I’m not the right fit
- Pure research / paper-writing engagements with no production endpoint.
- Frontend pixel-pushing without a backend or AI component.
- Anything that requires me to be on-site five days a week — happy to travel for kickoffs and milestones, but the work is remote.
Other channels
- X: @asphaltcowb0y — DMs open, expect public reply for non-sensitive questions.
- GitHub: @jeremylongshore — issues on any of my repos get answered.
- LinkedIn: jeremylongshore — fine for intros; not where I work.
- Discord:
asphaltcowboy— I’m in a few server communities, mostly read-only.
Where I am
Gulf Shores, Alabama (Central time, US). Remote-first; I’ll travel for project kickoffs and milestones when it makes sense. Most engagements are run async with weekly syncs.
On AI in the inbox
If you’re using an AI to draft your initial email — fine, I do too. But please proofread it before sending. AI-drafted cold emails that hallucinate things about my background or paste in the wrong company name are easy to spot and don’t get answered.