Pipeline Engine: The White-Label AI Revenue System
Unlock unprecedented revenue growth for your clients with Pipeline Engine, a comprehensive, AI-powered system designed for white-label deployment. This dual-format solution empowers AI builders to deliver cutting-edge revenue intelligence, combining five specialist agents into one compounding revenue engine.
What is this?
Pipeline Engine is a dual-engine AI system that automates the two highest-leverage activities in B2B revenue: turning content into measurable pipeline, and converting anonymous website traffic into identified, qualified leads. It is delivered in two distinct formats, tailored for diverse operational contexts:
1. Pipeline Engine Desktop: A no-code prompt workspace operating entirely within standard browser-based LLM interfaces such as Claude.ai.
2. Pipeline Engine CLI: A programmatic Python codebase executable via the command line, offering direct integration with external APIs and CRMs.
As a white-label package, you receive full source code ownership for both formats, allowing you to rebrand, restructure, and resell the entire system under your agency’s name without any royalties or revenue sharing.
What’s Included?
Pipeline Engine Desktop (No-Code Prompt Workspace)
A structured, copy-paste repository of advanced system prompts, checklists, templates, and playbooks. Divided into 5 no-code modules tied together by orchestrator files and a shared knowledge base.
Directory & File Structure:
•START_HERE.md: The main entry point and user guide. Directs users based on their immediate growth objectives and outlines the full folder structure.
•SKILL.md: Detailed documentation covering all 5 modules, input requirements, output schemas, scoring weights, and step-by-step setup guides.
•Pipeline_Engine.aipkg: A package configuration file to import the entire Pipeline Engine system context into LLM project managers, such as Claude Projects, with one click.
•Orchestrator_Prompts/:
•00_master_orchestrator.txt: The core system prompt is pasted at the start of a chat session to initialize all 5 specialized agent personas.
•weekly_growth_cycle.txt: A prompt setting up a structured, step-by-step weekly routine (Mon to Fri) to run the business growth engines.
•full_audit.txt: Runs a complete marketing and revenue audit, generating a 30-day action plan.
•Modules/:
- •Cold-Email/: Prompts to extract Ideal Customer Profiles from deal CSVs, generate 3 personalized outreach variants, check emails against a 24-point slop detector, and suggest value-based pricing tiers.
- •Content-to-CFO/: Prompts to score draft articles out of 100, generate attribution tables linking articles to closed deals, and format monthly CFO executive reports.
- •Invisible-Pipeline/: Prompts to evaluate inbound site visitor intent, score closed-lost deals for reactivation potential, look up web-buying triggers, and review Gong call objection transcripts.
- •Podcast-Engine/: A 5-prompt step-by-step system translating transcript files into quote lists, Twitter/X threads, LinkedIn posts, video scripts, newsletter formats, A/B variant headlines, and publish schedules.
- •Unfair-SEO/: Prompts for finding keywords your competitors rank for, generating 50 headline variants, and simulating a 4-expert panel to critique and evolve headlines.
•Shared_Knowledge_Base/:
- •icp_playbook.md: Living templates for Ideal Customer Profiles used across all modules.
- •winning_headlines.md: A library tracking high-performing headlines scoring 85+.
- •content_scoring_rubric.md: Criteria used to score article quality across Voice Match, Specificity, AI Slop, Length, and Engagement.
- •revenue_attribution_guide.md: Explains how to set up content-to-revenue mapping in CRM platforms like HubSpot.
•Connectors/:
- •Connector_Guide.md: A no-code guide mapping integrations for RB2B, HubSpot, Slack, Stripe, Gong, Instantly, and Brave Search.
- •examples/: Sample spreadsheets and workflows for each module.
Pipeline Engine CLI (Developer-Ready Codebase)
A programmatic Python implementation of the agent system. Contains a command-line orchestrator, five individual Python agent modules, automated dependency setup scripts, environment configuration templates, and a shared local JSON database.
Directory & File Structure:
•pipeline_engine.py: The main CLI entry point. Parses terminal flags, runs both Flywheels, manages state saving and loading from data/, and provides diagnostic testing and status commands.
•setup.sh: Provides the Python runtime environment and installs required libraries, including anthropic, dotenv, requests, feedparser, and tqdm.
•.env.example: Configuration template outlining all API tokens and intent score thresholds.
•AGENTS.md: Markdown reference detailing the system prompts, guidelines, and rules passed to the LLM backend for each programmatic sub-agent.
•SKILL.md: Technical manual detailing installation, terminal commands, input formatting, and shared state JSON data architecture.
•agents/:
- •cold_email_agent.py: Functions to run cold email variants, check drafts against 24 AI slop patterns, suggest tiered pricing, and discover win patterns from CRM deal CSVs.
- •content_to_cfo.py: Programmatic content scoring and CSV revenue attribution tracking.
- •invisible_pipeline.py: Ingests visitor tracking data, verifies leads against suppression logic, queries Brave Search for buyer trigger signals, and hosts a webhook endpoint to capture visitor events in real time.
- •podcast_engine.py: Uses Whisper API to transcribe audio episodes, break transcripts into core atoms, and automatically construct content tables.
- •unfair_seo.py: Queries competitor domains for keyword gap opportunities, builds headline variants, and runs an evolution loop based on simulated critic scores.
•data/ (autogenerated on first run): Houses all execution output files as timestamped JSON, ensuring consistent state storage across independent runs.
How It Works
The system operates on two parallel revenue flywheels, each designed for continuous, compounding growth.
Flywheel 1: Content-to-Revenue
Content enters the system as a podcast transcript, blog draft, or article. The Content-to-CFO agent scores its quality across five criteria: Voice Match, Specificity, AI Slop, Length, and Engagement. Once approved, the Podcast Engine repurposes it into 20+ platform-specific assets, including threads, LinkedIn posts, video scripts, and newsletters. The Unfair SEO agent then optimizes headlines through competitor keyword gap analysis and a simulated 4-expert panel to iteratively evolve top-performing variants. The Cold Email agent integrates top-performing content concepts directly into personalized cold outreach. The CFO Attribution module then tracks which content pieces contributed to closed deals in the CRM, establishing a direct link from content creation to revenue.
Flywheel 2: Invisible-to-Visible Pipeline
The Invisible Pipeline agent processes website visitor data, scoring each visitor’s purchase intent and filtering them through a five-layer suppression system that removes personal emails, current customers, active campaigns, duplicates, and competitors. Qualified visitors are routed for outreach. Concurrently, the Deal Resurrection module scores stalled or closed-lost deals to trigger timely re-engagement campaigns. The Trigger Prospecting module monitors public signals, including funding rounds, job postings, and executive moves, to identify companies in active buying cycles. The ICP Learning module continuously refines the ideal customer profile based on historical win and loss patterns.
How to Use It
Pipeline Engine Desktop (Web Chat and Prompt Workspace)
Claude.ai:
- Open claude.ai and start a new chat session.
2. Copy the entire content of 00_master_orchestrator.txt and paste it as your first message to load all 5 agent personas.
3. Navigate to the desired module folder and open the relevant workflow prompt.
4. Copy the prompt, paste it into the same chat, replace bracketed placeholders with your real data, and send.
Claude Cowork (Projects):
1. Create a new Project in your Claude Cowork workspace.
2. Upload the entire Shared_Knowledge_Base/ directory and SKILL.md to the project knowledge base.
3. Paste 00_master_orchestrator.txt into the Project’s Custom Instructions box.
4. Command the workspace directly: “Analyze this draft cold email and remove AI slop using the templates in our knowledge base.”
Manus AI (Autonomous Agent):
1. Launch a new agent task in your Manus AI dashboard.
2. Upload or paste the prompt sequence from weekly_growth_cycle.txt.
3. Instruct Manus to run a competitor gap analysis autonomously. It will browse the web, execute search queries, and compile the final audit.
Pipeline Engine CLI (Terminal, IDEs, and Programmatic Environments)
Claude Code:
1. Open your terminal and navigate to the pipeline-engine-cli folder.
2. Start Claude Code and instruct it to run setup.sh to install dependencies.
3.Execute commands directly: python pipeline_engine.py content-flywheel –input transcript.txt or python pipeline_engine.py test.
OpenAI Codex:
1. Open your code editor inside the pipeline-engine-cli folder with Codex enabled.
2. Open any agent script and write code comments to prompt Codex inline.
3. Accept and extend the auto-generated Python code.
Google Antigravity IDE:
1. Import the pipeline-engine-cli workspace folder into the Antigravity IDE.
2. Configure API keys by creating a .env file from .env.example.
3. Run scripts directly from the IDE terminal or interact via the agent interface.
Openclaw / Hermes:
1. Launch the Openclaw or Hermes agent terminal framework inside your project path.
2. Direct the agent to execute specific pipelines: python pipeline_engine.py pipeline –resurrect –top 5.
3. The framework will consume deal logs, execute background scripts, and print structured JSON results back to the terminal.
Who Is It For?
AI Builders and Agencies seeking to deliver a production-grade revenue system to clients without building infrastructure from scratch. The white-label license allows full rebranding and resale with no royalties or revenue sharing.
Non-Technical Founders, Marketers, and Sales Leaders who need the Desktop variant for immediate, copy-paste workflows inside browser chat interfaces, with no terminal, API keys, or Python environment required.
Developers and Technical Builders who need the CLI variant as a programmatic backend for extension, customization, webhook hosting, or integration into an existing client tech stack.
Agencies Serving Both Audiences who deploy the Full variant, offering the prompt workspace as a client-facing daily driver while using the CLI engine as an automated backend for data processing and system feeding.
Why It Works
For the Desktop variant: The master orchestrator prompt prevents context drift, ensuring consistent expert behavior across long sessions. The modular structure lets clients use individual workflows independently without loading the full system.
For the CLI variant: Programmatic speed eliminates human bottlenecks, completing lead scoring, content repurposing, and SEO analysis in seconds. JSON state persistence ensures pipeline resilience, resuming from interruptions without restarting. The built-in webhook server in invisible_pipeline.py enables real-time visitor event capture and scoring.
For the Full variant: The dual-format design solves the most common agency challenge: clients who cannot use technical tools but need their output. The prompt workspace provides an accessible daily interface, while the CLI engine handles complex data processing in the background, covering the full workflow from raw input to CRM-attributed revenue.
Built by Adam2Scale — adam.mchaigui@adam2scale.com
Pipeline Engine v1.1 — June 2026