A growth agent per startup
Each portfolio company gets phone agents that keep its social accounts active and its launches amplified.
Three pains every sales and BD team hits weekly. Each one is what your reps actually complain about, not what a feature page would call them.
Every startup in your portfolio needs social presence and community growth.
None of them can justify a growth hire on day one, and you cannot staff one per company.
Every pipeline below is a shape you wire on the canvas using the crew and tools further down. Not a feature we ship for you, a pattern you configure.
Each portfolio company gets phone agents that keep its social accounts active and its launches amplified.
Founders approve every public action from their phone. Nothing ships in a company's name without its founder.
Web3 programs help early projects stay present across X, Telegram, and Discord communities. One tool, cohort-wide.
Real personas from the research_team crew. Each ships with a tuned system prompt and a default tool allowlist. Swap models per persona on the canvas.
Reads each startup's market and shapes what its agents amplify.
Tracks account activity and growth across the cohort.
Keeps community answers accurate and sourced.
Times launch pushes around market context, not against it.
Every tool below is a real shared tool from the Melaya bundle. Allowlist per agent; HITL-gate the writes; revoke any of them in one click.
Runs each company's social apps on a real device, gated by that founder's approvals.
X coverage for launches and mentions.
Keeps Telegram and Discord communities active.
Research plus the founder approval gate.
Every pipeline ships with three layers of knowledge access. Mix and match per agent on the canvas. No shared vector space with another tenant, no surprise reads, no opaque retrieval.
includeContextPer-pipeline documents appended to specific agents' input on every run. The ICP brief, playbook, pricing sheet, or won-deal email corpus. Whatever needs to be there before the agent thinks. You pick which personas get which docs.
rag_retrieveA scoped tool granted per-agent. When the agent decides it needs more depth, it queries the workflow's vector store on demand. Same knowledge base as Static context, accessed only when the model asks for it.
pipeline_memoryPipeline-level state that carries from one run to the next. Yesterday's research is in scope for today's follow-up. The crew remembers what it already prospected, what got approved, what was sent. The audit log is the second-order knowledge base.
Sandbox tier is free with no card. Join the waitlist and we will email you the moment a slot opens.
← Back to every use case