For DePIN & AI-on-Chain Protocol Teams
Node operator recruitment, enterprise client outreach, developer onboarding, ecosystem BD. These are the supply and demand pipelines that determine whether a DePIN network survives or scales. GhostWork deploys an AI agent to run one of them.
Scoped Phase 1 build. One named surface. $5,000 flat. You get a mapped workflow, source materials, and a clear handoff path for what to run next.
The pipelines that DePIN teams build last
Protocol teams are built for technical execution and community. Not for the supply and demand pipelines that sit underneath both.
Node operator recruitment does not scale through manual outreach
Identifying, qualifying, and onboarding node operators requires research, personalized outreach, and consistent follow-up. At 100 operators it is manual but manageable. At 10,000 it is a pipeline problem, not a staffing problem. Most DePIN teams discover this bottleneck after they needed to solve it.
Enterprise clients do not default to decentralized infrastructure
Selling compute, storage, bandwidth, or AI inference capacity to enterprise buyers means finding the right teams, educating them on the model, and getting them through a procurement process that was not designed for decentralized providers. This is a BD motion. Most DePIN protocols run it informally or not at all.
Developer onboarding pipeline dies without follow-through
Developers express interest at hackathons, in Discord threads, in documentation feedback. Most of them never ship. The teams that convert interest to active builders have a system for tracking developers through the funnel and following up at the right moment. The ones that do not keep re-acquiring the same developers.
Ecosystem BD is perpetually backlogged
Integration outreach, protocol partnership applications, chain expansion conversations. The targets are known. The value proposition is clear. Nobody has time to work through the list systematically. By the time someone prioritizes it, a competitor has already shipped the integration.
What a pilot delivers
A scoped build on one ops surface with a runbook and source materials.
- A deployed AI agent running one named ops surface
- Scope workshop before any work starts (both sides sign off on what working means)
- Scoped build and handoff on your actual toolstack
- 2 months of iteration included in the same SOW
- All data stays in your systems, on your accounts
- One signed document, flat fee, no retainer commitment
$5,000 flat
With case study rights. No-CSR variant: $7,500.
How it works
Four phases. One scoped system.
Scope workshop
You walk us through which pipeline is costing you the most growth right now. We help you pick one surface with a clear success definition. Both sides sign a one-page SOW before any work starts.
Agent build
We build the agent against your actual toolstack. Your CRM, Notion, Airtable, Discord, Telegram, on-chain data sources, or custom APIs. No generic demos. Handoff happens in your environment.
Live iteration
Phase 2 iteration can sit in the same SOW. New operator segments, updated enterprise targets, API changes, workflow adjustments.
Handoff or retain
At handoff, you keep the runbook and source materials. If you want continued operations support, we offer a monthly retainer. If not, you have the package to run in-house.
Common questions
2 pilot slots open
Ready to run one pipeline on autopilot?
Book a 20-minute intake call. We will walk through your current pipeline gaps, identify the right surface for the pilot, and tell you whether it fits the format.
Book a 20-min intake callOr email us at hello@ghostwork.agency