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.
Follower counts, engagement, and post performance live across six-plus app dashboards, so a weekly report means six logins and a spreadsheet.
Matching on-brand copy and image or video assets to six platforms at once is a full-time job by itself.
Reddit, TikTok, and Substack change their feeds often enough that a growth playbook from three months ago is already stale.
Engagement work, replies, likes, DMs, needs a human voice, but doing it by hand across more than a handful of accounts does not scale.
Agencies running one account per client hit the same six-platform wall for every client, with no shared dashboard across them.
A platform with no public API, or a client who will not grant one, means that whole channel gets skipped every time.
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.
Melaya Marketing's Socials surface reads live follower counts, engagement, and recent posts across X, Instagram, LinkedIn, TikTok, YouTube, and Threads in one dense view, so a weekly client report stops needing six logins.
ContentStrategist drafts the hook and structure, Copywriter writes the caption variants, and BrandArchitect checks palette and voice before the image pipeline or MemeArtist produces the asset. SocialMediaEngineer then posts the finished set to every connected platform in one pass.
Comments, replies, and DMs across Instagram, X, Threads, and LinkedIn get read, drafted, and queued by SocialMediaEngineer, so a human reviews and approves the reply instead of writing every one from scratch.
Agencies scope each client's connected accounts separately, so GrowthEngineer's distribution plan and BrandArchitect's brand check run per client inside Melaya Agents, each with its own approval queue.
For Reddit threads, comment sections, or a platform with no public write API, Melaya Browser Control drives a real, watched browser session instead, pausing for your approval before anything consequential posts.
Real personas from the marketing_team crew. Each ships with a tuned system prompt and a default tool allowlist. Swap models per persona on the canvas.
Designs the video and post concept, writes the hook, structures the shot list, and times every transition so the script lands on platform.
Writes the headline, three A/B variants, body copy, and CTA in a direct-response voice trained on the Ogilvy and Halbert tradition.
Designs the funnel, the viral loop, the seed list of accounts and communities, and the paid amplification plan against a target K factor.
Checks every asset against the brand brief on palette, typography, voice, and visual hierarchy, and surfaces inferred assumptions when guidelines are missing.
Turns the campaign into per-platform copy, hashtag strategy, posting windows, and thread or carousel structure for X, LinkedIn, TikTok, and YouTube.
Picks the canonical meme template that fits the angle, writes original captions inside the slot count, and renders one image per turn.
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.
Read live follower counts, engagement, and recent posts, then publish carousels, images, and replies once approved. instagram_publish_carousel and instagram_reply_to_comment are HITL by default for this crew.
Pull follower stats, post images, and draft or queue comment replies. linkedin_post_image and linkedin_reply_to_comment wait for your approval before anything sends.
Read account insights and recent replies, and post drafted content once approved. Reply drafts route through the same approval queue as every other platform.
Pull channel analytics so SocialMediaEngineer's weekly report reflects real numbers, not a cached export.
Read account info and publish video or photo posts once BrandArchitect and SocialMediaEngineer sign off on the asset. tiktok_publish_video and tiktok_publish_photo are HITL gated.
Post to X and stage image posts from the brand handle. x_post and x_post_image are HITL by default so a human reviews the draft before it ships.
Search Reddit threads and prepare image submissions for platforms Melaya Browser Control reaches when there is no public write API. Posts pause for approval before they go out.
General research and Slack handoff for the approver. pause_for_human is the explicit approval node every publish or reply routes through.
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