Reference

Glossary

The terms, frameworks, and technical concepts that shape how Gilgamesh thinks about Engineered Demand. 41 entries across 7 sections.

01 · Methodology

Methodology

Engineered Demand: The Gilgamesh thesis. Demand is not magic. It is the predictable output of designing strategy, systems, and story as one connected motion. Most B2B companies fragment them. We fuse them.
Strategy × Systems × Story: The brand equation. Strategy is positioning, ICP, and motion design. Systems are RevOps, attribution backend, and signal capture. Story is message architecture, category framing, and content output. Multiplied, not added.
Diagnose · Design · Deploy · Defend: The four-stage Gilgamesh process. Diagnose the demand motion in 1 to 2 weeks (free, no commitment). Design the system scope. Deploy operators who run it live (3 to 6 months). Defend through ongoing calibration.
Diagnosis Before Direction: The non-negotiable. We do not design a system before understanding the market. Diagnosis comes first, scope second. No exceptions.
The Demand Motion: How a market actually buys, distinct from how a category sells. Engineered Demand starts with diagnosing the buying behaviour that exists, then designing every layer to match.

02 · Framework

The Seven-Layer Framework

Layer 00 · Narrative & Category Design: The narrative bedrock. Category creation vs entry decision, unique POV articulation, messaging architecture (pain to promise to proof). Precedes message; message precedes channel.
Layer 01 · Demand Motion Diagnosis: The diagnostic engine. Signal ingestion architecture (first-party, third-party intent, enrichment), account state engine, motion classification across the three demand motions.
Layer 02 · Go-to-Market Architecture: The GTM pillar. ICP & Segmentation, Positioning & Messaging, Pricing & Packaging, Channel Architecture. What we target, what we say, how value is structured, where it goes. Read more →
Layer 02 · Paid Media Strategy: Parallel to GTM Architecture at the same layer. Demand Creation vs Demand Capture mix determined by the motion: 70/30 for Shift, 50/50 for Steepening, 30/70 for Segmentation.
Layer 03 · Revenue Operations: The systems layer. Sales Operations (pipeline integrity, forecasting, CRM governance). Marketing Operations (lead lifecycle, attribution, automation). CS Operations (retention signals, churn prediction, expansion).
Layer 04 · Sales Team-as-a-Service: The execution layer. Account Executives (commercial close), Sales Development (pipeline sourcing), Customer Success (retention and expansion). Operators embedded inside the client business, not advisors.
Layer 05 · Orchestration & Automation: The connective tissue. Workflow automation, signal-to-action routing, lifecycle orchestration across systems. Where the layers stop being silos and start being one engine.
Layer 06 · Stack Architecture: The tooling layer. Tool selection, integration design, vendor management. Picks tools that serve the motion; never lets tools dictate motion. See Stack Validation.
Stack Validation: The Layer 06 principle. Every tool category serves the motion, not the vendor. Stack decisions are motion-determined and vendor-agnostic. Tools that do not earn their place against the motion are removed regardless of incumbency.

03 · Diagnostics

Diagnostics & Motion Analysis

The Three Demand Motions: The diagnostic for matching GTM posture to market reality. Demand Shift (problem exists, awareness is low: create more buyers). Demand Steepening (problem is known, value perception is weak: increase willingness to pay). Demand Segmentation (market exists, willingness varies: capture more value from same demand).
Demand Creation vs Demand Capture: The channel architecture split. Demand Creation builds pipeline that does not yet exist (6 to 18 month horizon: founder thought leadership, SEO, community, long-form content). Demand Capture harvests existing intent (30 to 90 day horizon: paid search, review sites, competitor interception, ABM). The ratio is motion-determined.
Signal Ingestion Architecture: The three-source signal capture system. First-Party (product usage, site behaviour, form completions, email engagement). Third-Party Intent (Bombora, 6sense, funding triggers, technographic changes). Enrichment (firmographics, behavioural scoring, account hierarchy).
Account State Engine: The Layer 01 sub-block that classifies accounts across five lifecycle states, each linked to the matching demand motion. Latent (problem unrecognised, Demand Shift). Aware (problem known, no solution, Shift to Steepening). In-Market (actively evaluating, Demand Steepening). Customer (revenue active, Demand Segmentation). Expansion (growth surface available, Demand Segmentation).
Motion Diagnostic: The Layer 01 starting point. The structured diagnosis that decides which of the three demand motions a company should run, based on observed buyer behaviour. Precedes architecture decisions in Layer 02.

04 · Services

Service Lines

GTM & Revenue Engine: The flagship engagement. All seven layers fused into one compounding revenue motion. Typically Series A through Series C B2B companies. Read more →
Gilgamesh Capital: Operator-investor hybrid. Twelve weeks of operator-led GTM execution first. Equity investment if momentum holds. Exit at Series A. Read more →
Entertainment Lab: The creative production arm. IP and worldbuilding, manga, animation, game production, licensing, OTT. Where storytelling meets demand. Read more →
Products & Talent: Four products built for the post-AI operator economy: Gandiva.ai (signal-led demand generation), Colosseum (ranked operator ecosystem), Jester's Academy (operator education), SHIELD (fractional team deployment). Read more →
Systems Hub: Five open-source operational frameworks for founders and operators. Free, no paywall. Read more →

05 · Frameworks

Operating Systems

Gandiva: Signal-led demand generation. Capture buyer intent signals across paid, organic, content, and community. Route highest-fit signals to human operators at the moment of intent. Built for high-ticket, relationship-driven B2B sales. Read more →
ARC: Operational automation for SMEs. Finance admin, resource tracking, reporting automated on open tools (N8N, Zapier, LangChain). Eliminates the administrative overhead consuming team bandwidth. Read more →
DAM: Competitor traffic interception. Capture audiences searching for competitors and redirect through precision paid media. Category diversion at the demand layer. Read more →
Pashupathi: Market share takeover. Heavy-capital category raid framework. Full-channel saturation on a backend network moat, sized against excess-share-of-voice math. For B2C raids and enterprise category incursions. Read more →
Excalibur: Executive infrastructure for founders. Build and manage the leadership layer (board, cap table, executive team, strategic relationships) as an active growth lever, not administrative overhead. Read more →
Excess Share of Voice (ESOV): The marketing-science concept underpinning Pashupathi. When a brand maintains share of voice greater than its share of market, it gains market share over time. Validated by Nielsen, refined by Binet and Field at IPA. The mathematical justification for heavy, sustained category investment.

06 · Operators

Operator Economy

Operator-led GTM: GTM execution by people who have actually run the motion before. Gilgamesh embeds operators inside client businesses as first-priority team members with cross-functional authority.
The Jester: Likith Reddy Ramidi's working alias. Reflects the operator-creative posture Gilgamesh runs on: irreverent toward orthodoxy, structured in execution.
Jester's Corner: The Gilgamesh blog. Field notes on GTM, demand engineering, and the operator economy. Read more →
Jester's Academy: Education program for operators who want to learn the frameworks Gilgamesh uses, applied to their own context. Self-directed practitioners, not students.
Colosseum: Ranked, AI-verified operator ecosystem. Five divisions from Rookie to Colosseum Champion. Operators earn ranking through real project delivery, not pedigree.
SHIELD: Fractional team deployment in three modes. System (you run it), Managed (we run it remotely), Embedded (a verified operator works inside your business). Built on Colosseum-verified talent.

07 · Standards

Industry Standards

GTM (Go-to-Market): The set of decisions and systems that determine how a company reaches and converts buyers. Strategy, channels, sales motion, pricing, message. Not the same as marketing; marketing is one layer inside GTM.
RevOps (Revenue Operations): The operational discipline that connects sales, marketing, and customer success into a single accountable revenue system. Owns the pipeline state machine, attribution, automation, and forecast hygiene. Reports to the revenue leader, not to any one function.
ICP (Ideal Customer Profile): The defined account archetype most likely to buy, succeed, and expand. Combines firmographic (size, industry, geography), technographic (current stack, integration fit), and behavioural (urgency signals, buying-committee shape) criteria. Drives every downstream decision in GTM architecture.
ABM (Account-Based Marketing): A demand-capture motion that treats individual accounts (not leads) as the unit of work. Coordinated outreach across paid, content, sales, and partner channels targeting a defined list of in-market or in-segment accounts.
Pipeline Velocity: The composite metric that measures how fast revenue moves through the funnel. Standard formula: (number of opportunities × win rate × average deal size) divided by sales cycle length. Increases when any of the four levers improves; decreases when any one breaks.