Client requests arrive as email
Stakeholders keep sending context through inboxes, forwarded threads, and one-off notes.
ErrandMoleFor developers behind client businesses
Turn client email into tracked implementation work.
ErrandMole gives every client project a controlled inbox, turns approved messages into coding-work requests, and routes them to the workflow you already trust.
Email intakeRepository contextAgent-ready dispatch
solo developersmaintenance studiosfractional CTOsweb ops partners
The gap
Your clients think in outcomes. Your team ships through systems.
ErrandMole sits between client-friendly email and developer-native delivery, so recurring maintenance work starts with enough context to move.
Delivery happens in repos
The real work lives in GitHub, Linear, Codex, and the review process your clients never see.
You bridge the gap manually
Every unmanaged request costs triage time before anyone writes a single useful line of code.
How it works
A repeatable intake line for every client site.
Keep the client interface simple while ErrandMole records sender, project, repository, and automation context behind the scenes.
Client-specific intake addresses
Sender allowlists for each project
GitHub repository targeting
Linear ticket and agent options
Daytona sandbox execution
Provider-neutral webhook dispatch
Workflow
From inbox to pull request without losing the thread.
Controlled inbox
Give each client project an address that only approved senders can use.
Routed work
ErrandMole turns the message into a tracked request with repository and sender context.
Agent dispatch
Send work to Linear-managed agents, Daytona sandboxes, or your own webhook runner.
Reviewable output
Track the request through tickets, agent progress, and opened pull requests.
Provider-neutral
Use the runner that fits the errand.
A project can stay manual, open Linear tickets, delegate to Linear agents, dispatch to webhooks, or run Codex CLI inside a Daytona sandbox.
Pricing
Plans for client-service developers and web studios.
Start with email intake, then add automated coding work as your client roster grows.
Developer
For independent developers keeping a few client sites moving.
$49 / month
3 connected client projects
50 actioned requests per month
Email intake and allowlists
Studio
For web studios with recurring maintenance retainers.
$100 / month
12 connected client projects
250 actioned requests per month
Daytona coding-work runs
Agency
For teams acting as the technical back office for many client businesses.
$249 / month
40 connected client projects
1,000 actioned requests per month
Priority onboarding
Questions
Designed for the way developers already support clients.
What does a client have to learn?
They email a project-specific address. ErrandMole checks the sender allowlist, records the request, and routes it into your selected coding-work runner.
Can I keep my existing workflow?
You can keep work manual, create Linear tickets, delegate to Linear agents, dispatch webhooks, or run a Daytona sandbox with Codex CLI as the default in-sandbox agent.
Are provider accounts locked to one deployment?
No. GitHub, Linear, webhook, and Codex credentials can be connected per workspace. Deployment-level credentials are optional fallbacks.
Ready for the next request?