# TexAu — Full Content Index> TexAu searches people, enriches companies, scores leads, and hands every lead to your outbound rails — Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences — from a table you already know how to use, or from our API and MCP server.Generated for LLM ingestion. Each page is delimited by frontmatter with url, title, and section.--- url: https://www.texau.com/ title: TexAu Home section: core --- # TexAu — The operator's bench for GTM TexAu searches people, enriches companies, scores leads, and runs every outbound action your GTM motion needs — from a table you already know how to use, or from our REST API and MCP server. 200+ actions across 32 integrations. Pay-on-match credits. --- url: https://www.texau.com/about title: About TexAu section: core --- # About TexAu TexAu builds the operator's bench for GTM teams — a single platform where searching, enriching, scoring, and pushing leads to outbound rails happens in one workflow. Founded by operators who got tired of stitching together five tools to run one outbound motion. --- url: https://www.texau.com/pricing title: TexAu Pricing section: core --- # Pricing — Two products, one account ## Platform tiers - **Solo** — $99/mo · 2,500 credits · 1 seat. For solo founders and small operators. - **Starter** — $249/mo · 8,000 credits · 3 seats · API + webhooks. Growing teams and small agencies. - **Teams** — $649/mo · 25,000 credits · 5 seats · bidirectional CRM sync. Agencies with 5+ clients. - **Enterprise** — custom volume, SSO/SAML, EU data residency. ## API & MCP Prepaid credit bundles from $20 per 1,000 credits. 50 free credits on signup. Volume discounts to 25%. ## How credits work One credit = one successful action. Failed lookups cost zero (pay-on-match). Roll over up to 2× monthly balance on Platform. Same credit pool for Platform, API, and MCP. --- url: https://www.texau.com/api-platform title: TexAu API Platform section: api --- # TexAu API Platform 200+ ready-to-run actions across 32 integrations. LinkedIn enrichment, waterfall email and phone, web scraping, search, AI enrichment. One auth header (`x-api-key`), one credit balance, one error contract. Base URL: `https://v3-api.texau.com/api/v1` ## Capabilities - Enrichment (profile, company) - Waterfall enrichment — 5 endpoints, one call cascades through 10+ providers - Email finding & verification - People & post search - Web scraping - AI Enrich (prompt-driven) ## Production grade 100,000 calls per endpoint per month. 13 async endpoints. Webhooks for job completion. Sandbox keys against test data. Per-client API keys with scoped allowlists. --- url: https://www.texau.com/mcp title: TexAu MCP Server section: api --- # TexAu MCP Server Hosted MCP server at `https://mcp.texau.com/mcp`. Connect any MCP-compatible agent (Claude Desktop, Cursor, Windsurf, VS Code Copilot, Cline, LangGraph, OpenAI Agents SDK) and get 200+ GTM tools as first-class agent tools — same auth as the REST API. ## Install (Claude Desktop example) ```json { "mcpServers": { "texau": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.texau.com/mcp", "--header", "x-api-key:${TEXAU_KEY}"] } } } ``` ## Tool groups - AI Column (flagship) — prompt-driven row reasoning - Email & phone waterfall (40+ tools) - Verification (8 tools) - People & profile search (60+ tools) - CRM read/write (78 tools) - Outbound push (30+ tools) - Web & content (20+ tools) --- url: https://www.texau.com/use-cases/agencies title: Use case: Outbound agencies section: use-case --- # One workspace per client. One credit pool for all of them. One workflow you build once. TexAu is built for the agency that runs the same enrichment-and-outbound playbook across ten or fifty clients — different ICPs, different lists, different CRMs, but one engine. Workspaces stay isolated. Credits pool. Templates deploy. The hour you used to spend rebuilding the same waterfall in client #7 belongs back to your margin. ## The problem Every agency hits the same wall. The first three clients are fun — you're learning the platform, building your playbook, shipping outbound. By client seven, you're rebuilding the same enrichment pipeline from memory because the last one's settings live in a Google Doc. By client fifteen, your team is asking why you can't just clone-and-deploy. Most GTM tools assume one workspace, one team, one CRM. Agencies need ten of everything, kept separate, billed once. ## How TexAu helps **One workspace per client** — Each client gets their own workspace. Their lists, their CRM connections, their templates, their team members — all isolated. Cross-tenant access is impossible by design. **One credit pool across all of them** — Credits are billed at the org level, not per workspace. Run heavy enrichment for client #3 in a busy week without rebalancing budgets across clients. Pay once, use everywhere. **One template, ten deployments** — Build your enrichment + outbound pipeline once. Save it as a template. Deploy across every client workspace with a single action. Update the template; redeploy. ## The pipeline 1. **1. Onboard the client** — New client comes in. Spin up a workspace from your "agency-onboarding" template. Their CRM connects in two clicks. Their default ICP filters and enrichment chain pre-load. 2. **2. Build the prospect list** — Run lead searches on Apollo, LinkedIn, and Sales Navigator inside the workspace (credit-priced like every action). Filter to the client's ICP. Save as a list inside their workspace. 3. **3. Run the enrichment chain** — 32-integration waterfall finds emails, verifier confirms them, AI columns score on hiring velocity or funding stage, source attribution lands in a column. Failed lookups cost zero. 4. **4. Push to outbound + CRM** — Pre-mapped Smartlead campaign per client. Pre-mapped HubSpot/Salesforce field mappings per client. Bidirectional sync — replies and meeting bookings flow back into the table. 5. **5. Audit + report** — Per-workspace audit log shows every action, every credit spent, every CRM write. Export per-client reports straight from the table for monthly client reviews. --- url: https://www.texau.com/use-cases/founder-led-sales title: Use case: Founders doing outbound section: use-case --- # You don't have time to assemble five tools. Use one. You're the CEO, the SDR, the RevOps person, and the person who fixes the printer. The last thing your day needs is a Clay canvas, a Hunter API key, a separate verifier, a separate scoring tool, and a Zapier zap holding it all together. TexAu is the one tool that does enrichment, scoring, outbound push, and CRM sync — fast enough to use between meetings. ## The problem Pre-Series-A, you have a thesis, a product, and a list of fifty companies you think would buy it. What you don't have: a sales team, a RevOps person, or three weeks to wire Clay + Hunter + Smartlead + HubSpot together. You either send seventeen perfect personal emails a week (slow), or you give up on outbound entirely (worse). The fix is the tool that lets you run an SDR's pipeline in a half-hour block on Tuesday afternoon. ## How TexAu helps **Replaces your stack of five** — Hunter for emails. ZeroBounce for verification. A scoring spreadsheet. Zapier for CRM push. Smartlead for sending. TexAu collapses the first four into one table; the fifth (Smartlead) integrates natively. **Replaces your "I'll figure this out later"** — GTM Co-Pilot turns "find Series A SaaS founders in California, enrich their LinkedIn, score them, push the top 30 to my Smartlead" into an editable pipeline in 60 seconds. **Replaces your contractor** — The freelance enrichment-and-list-building shop you were going to hire for $1,500/mo? Pro tier is $99/mo and doesn't go on holiday. ## The pipeline 1. **1. Describe the pipeline (60 seconds)** — Open Co-Pilot. Type: "Find Series A SaaS founders in California with 10–50 employees who raised in the last 6 months, enrich LinkedIn, push the top 50 to my Smartlead campaign 'cold-vc-warmup'." 2. **2. Edit the result (90 seconds)** — Co-Pilot proposes the table — columns, action chain, schedule. Tweak the funding-window filter. Confirm the Smartlead campaign mapping. Hit Run. 3. **3. Watch the table fill (~3 minutes)** — 500 candidates from the search; ~430 enriched; ~360 verified; ~50 score 80+ on the founder-fit signal you defined. 4. **4. Push and log** — Top 50 push to Smartlead automatically. The whole batch logs into your CRM with the score column and reasons. Replies route back to your inbox. 5. **5. Get back to building** — Done. Pipeline is in flight. The half hour you spent on outbound today is the same half hour next Tuesday — because you can clone the run. --- url: https://www.texau.com/use-cases/abm-teams title: Use case: ABM and revenue marketing teams section: use-case --- # Account-based isn't a list. It's a signal-driven motion. TexAu ships the data primitives ABM actually needs: per-account enrichment depth, signal capture (hiring, funding, technographic, executive moves), account-level scoring that updates as the world changes, and a tight loop into your CRM and outbound rails. No more once-a-quarter target-list rebuilds. ## The problem Most ABM tooling assumes the target-account list is static: 100 accounts, refreshed quarterly, scored once, marketed to identically. The reality is the opposite. The 100 accounts on your list this morning include three that just had executive changes, two that closed a Series B yesterday, and one that started hiring six engineers in the last 30 days. Capturing those signals, scoring on them, routing them to the right rep at the right moment — that's what TexAu's data layer is built for. ## How TexAu helps **Per-account enrichment depth** — For each target account: company firmographics, full org chart at the seniority levels you care about, technographic signals, funding stage and history, hiring velocity by role, news mentions. Refreshed continuously, not once a quarter. **Signal capture and scoring** — Every target account gets a score that updates as signals land. Hiring velocity, funding, executive change, technographic match. Top-3 reasons surface alongside every score. **CRM-aware enrichment** — Bidirectional sync to HubSpot, Salesforce, Pipedrive. Accounts already owned by an AE are flagged so marketing doesn't re-enrich, re-target, or step on the rep's motion. ## The pipeline 1. **1. Build the target-account list** — Either start from your existing CRM segment, or build from scratch via TexAu's prospecting. Filter by industry, headcount, geography, funding stage. 2. **2. Enrich and score on day one** — Run the full enrichment chain across the list. Every account gets the firmographic data + signal columns + score. Failed lookups cost zero. 3. **3. Schedule continuous signal monitoring** — Set a scheduler to re-enrich the list weekly and re-score on the new signals. New funding rounds, new hires, new executive changes — all flagged in the table the moment they land. 4. **4. Route signals to sales** — Score crosses 80 + signal type is "VP Engineering hired" → fire a webhook to your CRM. Sales gets the lead in their daily queue with the signal annotation. 5. **5. Measure motion at the account level** — Per-account audit log shows every action, every signal, every campaign touch. Tie pipeline back to specific signals when accounts close. --- url: https://www.texau.com/use-cases/sdr-teams title: Use case: SDR teams section: use-case --- # Your reps are paid to talk. Stop making them hunt for the data first. A typical SDR spends 30–40% of their day building lists, deduping against the CRM, looking up phone numbers, and drafting context. None of that converts a meeting. TexAu does the prep work overnight; reps walk into a sorted, scored, deduped queue that's ready to call. ## The problem The 9 AM SDR ritual: open Apollo, build today's list. Cross-check against the CRM to find which leads are already worked. Open ZoomInfo or LinkedIn for the ones missing direct dials. Drop them into a Google Sheet. Score them by gut. Push the survivors to Smartlead. By 10:30 AM, the team has spent the freshest hour of the day on data work that won't appear in their pipeline. The fix is a queue that arrives sorted, scored, and dedup'd before the rep opens their laptop. ## How TexAu helps **Overnight prep, scheduled** — Set a scheduler for 4 AM. Every morning: re-enrich the target list, refresh phone numbers via waterfall, re-score on new signals, dedup against the CRM. Reps open the table at 9 AM to a queue that's ready. **Dedup-aware** — Every lead is checked against your HubSpot/Salesforce. Owned by another rep? Flagged. Already in an active sequence? Flagged. Recent activity from the prospect? Flagged. The queue surfaces only leads that are actionable today. **Score-sorted with reasons** — Every lead in the queue is scored 0–100 with the top three reasons surfaced. Reps don't ask "why is this lead at the top?" — the table tells them. ## The pipeline 1. **1. Manager builds the daily-prep template** — Co-Pilot drafts it from a one-line prompt. Manager edits the column mapping, confirms the schedule. 2. **2. Workspace per rep (or per pod)** — Each SDR or pod has their own workspace inside the org. Shared template; per-rep filtering; per-rep credit accounting if you want it. 3. **3. Overnight refresh** — Schedule runs at 4 AM. Enrichment, dedup, scoring, push to sender — all done before anyone wakes up. Failures alert the manager via Slack, not the rep. 4. **4. Rep opens the queue** — 9 AM. Table is sorted by score. Top 50 are already pushed to Smartlead. Phone numbers populated. Last-activity from the CRM visible. 5. **5. Calls happen, results land** — Replies and meetings sync back to the table. The rep marks dispositions; the next morning's queue learns from yesterday's outcomes. --- url: https://www.texau.com/use-cases/growth-marketers title: Use case: Growth marketers section: use-case --- # Growth runs on experiments. Experiments run on data. We're the data primitive. Growth marketers ship five experiments a week — new audiences, new lookalikes, new ICPs, new outbound angles. Each one needs enriched data, segmented lists, and personalization at row level. TexAu is the engine those experiments run on: API-first when you want to script it, AI-column-rich when you want to draft it, fast enough to keep up with your roadmap. ## The problem You wanted to test outbound to mid-market healthcare CFOs this week. You wanted to test a new lookalike audience for your paid ad spend. You wanted to test a personalized re-engagement sequence for cold leads. None of those experiments runs without enriched, segmented, scored data — and most growth marketers spend more time pulling data than running tests. The fix is making the data layer programmable, AI-column-driven, and fast enough that data work isn't the experiment's bottleneck. ## How TexAu helps **Audience and segment construction** — Build new ICPs in minutes: filter by industry, headcount, technographic, hiring velocity, recent funding, executive moves. Iterate the filter as the experiment evolves. **Personalization at row level** — AI columns transform any data into per-row personalization: a one-line opener referencing their last funding round, a custom subject line based on their tech stack. BYOK for cost control. **Experiments that ship as code** — Every TexAu action is a REST endpoint. Wire experiments into your growth-engineering stack: trigger an enrichment job from your A/B testing framework, push winning audiences to your ad-platform API. ## The pipeline 1. **1. Hypothesis** — "Mid-market healthcare CFOs who recently joined will respond to a peer-benchmarking message about budget cycles." 2. **2. List construction (5 minutes)** — Co-Pilot proposes the table: Apollo search filters, enrichment chain, AI column for "tenure in current role." Edit, run. 3. **3. Personalization (10 minutes)** — AI columns draft openers and subject lines per row. BYOK on Anthropic or OpenAI keeps costs predictable. 4. **4. Push to sender (1 minute)** — Push to Smartlead with the experiment-tagged campaign. Per-row openers and subject lines as merge fields. Send rate respects warmup curve. 5. **5. Measure and learn** — Replies sync back to the table with reply class (positive / interested / out-of-office / nothing). Tag the experiment, run the next one. --- url: https://www.texau.com/comparison/texau-vs-clay title: TexAu vs Clay section: comparison --- # The wedge isn't enrichment. It's everything you do with the enrichment. Clay is the most powerful data canvas in GTM. We respect it. But Clay enriches — TexAu enriches and runs the actions. Plus, every TexAu workflow has a REST endpoint and an MCP tool. Clay's API is gated. That's the wedge. ## Where Clay wins **The most powerful canvas in GTM** — If you're an ops engineer who wants to wire seven signals into a custom scoring formula across five providers with branching logic, Clay's canvas is the best tool for that work. **Massive ops-team mindshare** — Clay has built the strongest community of GTM engineers in the space. Templates, recipes, mutual-aid Slack channels — there's a cultural moat. **Deep enrichment options** — 12+ providers, signal sources, AI columns, conditional logic. The substrate Clay built is real and well-engineered. ## Where TexAu wins **1. Real execution depth** — Clay enriches data. TexAu enriches data and runs the actions: search people, find phone numbers, send LinkedIn DMs, push to Smartlead, log activities to HubSpot. 200+ column actions, including 50+ outbound and CRM-write actions Clay doesn't ship. **2. Pay-on-match pricing** — Clay charges per credit attempted — failed lookups still cost. TexAu charges per successful match; failed lookups cost zero. Lead search on Apollo, LinkedIn, and Sales Navigator is credit-priced like every other action, with the per-result rate published in the action catalog. **3. API + MCP-native** — Every TexAu action is a REST endpoint at api.texau.com/v1 and an MCP tool at mcp.texau.com/mcp. Clay's API is gated to enterprise. If you're shipping enrichment in your product, the moat moves to whoever your code can call directly. --- url: https://www.texau.com/comparison/texau-vs-apollo title: TexAu vs Apollo section: comparison --- # Apollo is one database with a UI on top. TexAu is 32 integrations, with the table that ships them. Apollo's strength is being the all-in-one for SDR teams: contact database, dialer, sequencer. Our strength is enrichment depth across 32 integrations, focus (we don't pretend to be your CRM), and a native API + MCP that Apollo gates behind enterprise tiers. ## Where Apollo wins **A genuinely large contact database** — Apollo's contact graph is one of the bigger ones in the space. If you want a single-source database tool with a UI built around searching it, Apollo is a solid pick. **Built-in dialer and sequencer** — Apollo ships a dialer, a sequencer, and meeting-booking inside the same UI. For a small outbound team that wants one tool to do everything, that consolidation is real. **Strong SDR-team mindshare** — Apollo's brand among SDR managers is strong. Reps who've used it before will be productive day one. ## Where TexAu wins **1. Waterfall, not single-source** — Apollo enriches from Apollo's database. When Apollo misses, you miss. TexAu cascades 32 integrations per request — Hunter, RocketReach, Snov, Datagma, ContactOut, and others. Effective fill rate is materially higher because the union of 32 databases beats any single one. **2. Focus, not everything-OS** — Apollo wants to be your database, dialer, sequencer, CRM, and AI agent. We don't. TexAu does enrichment, automation, and CRM sync. Outbound sending we hand to Smartlead, Instantly, Lemlist, Apollo Sequences, or HeyReach. **3. API + MCP-native** — Every TexAu action is a REST endpoint and an MCP tool, on every plan. Apollo's API exists but is rate-limited and feature-gated by tier. --- url: https://www.texau.com/comparison/texau-vs-zoominfo title: TexAu vs ZoomInfo section: comparison --- # The procurement gauntlet is not a feature. ZoomInfo is the deepest contact database in B2B. It's also a 6-figure annual contract, a 90-day procurement cycle, and a vendor relationship that doesn't end when you stop using it. TexAu gets you 80% of the daily-use value for ~40% of the cost, billed monthly, with API + MCP included on every plan. ## Where ZoomInfo wins **Database depth and intent** — ZoomInfo's contact and company graph is genuinely the deepest in the market. If you need 300 million contacts, ZoomInfo has them. Their intent data (Bombora-powered) is real and useful. **Salesforce-native enterprise integration** — ZoomInfo has decades-deep Salesforce integration. If you're a 1,000-person sales org running on SFDC with custom objects and Einstein, ZoomInfo plugs in better than any newcomer. **Compliance and contract muscle** — GDPR, CCPA, SOC 2, HIPAA where applicable, signed BAAs, customizable DPAs. If your procurement team needs a 200-page security questionnaire answered, ZoomInfo's legal team has answered it. ## Where TexAu wins **1. Monthly billing, no procurement gauntlet** — ZoomInfo's standard contract is annual, with a published price floor in the high-five-figures and most real deals in the six-figures. TexAu's Pro tier is $99/mo, billed monthly, cancellable monthly. **2. Waterfall + execution depth ZoomInfo doesn't ship** — ZoomInfo is a database with read APIs. TexAu is a waterfall (32 integrations) plus the action layer: 200+ column actions including LinkedIn DMs, Smartlead pushes, HubSpot writes, scheduled re-enrichment. **3. API + MCP at the entry tier** — ZoomInfo's API is real and powerful — at the enterprise tier. TexAu's API is on the free tier, full feature set, no additional contract. The MCP server is on every plan. --- url: https://www.texau.com/comparison/texau-vs-phantombuster title: TexAu vs Phantombuster section: comparison --- # Phantombuster is a script library. TexAu is the platform you graduate to. Phantombuster's catalog of one-shot "phantoms" is the right starter tool for a single LinkedIn scrape or a one-time Sales Navigator extract. When you need pipelines — search → enrich → verify → score → push to CRM — running on a schedule with state and audit logs, you've outgrown the script library. ## Where Phantombuster wins **Catalog breadth for one-shot tasks** — Phantombuster has built one of the largest catalogs of social-action scripts. If you want to scrape a single LinkedIn group, extract a Sales Nav search, or pull a Twitter list, Phantombuster's "phantom" runs in five minutes. **Low cognitive overhead for first-time users** — Pick a phantom, fill in a few fields, run it, get a CSV. There is no schema, no table model, no workflow concept. **Cookie-based browser automation** — Phantombuster's session-based browser scripts work for tasks where API access doesn't exist. Some LinkedIn actions only work that way. ## Where TexAu wins **1. Pipelines, not scripts** — Phantombuster runs one phantom at a time. Each output is a CSV you have to manually feed into the next step. TexAu chains the steps inside one workspace: search → enrich → verify → score → push to Smartlead → log to HubSpot — running as one pipeline, on a schedule. **2. Real CRM sync, not export-and-import** — Every phantom ends in a CSV. You import that CSV into your CRM, dedup by hand, hope nothing went wrong. TexAu has bidirectional CRM sync to HubSpot, Salesforce, Pipedrive, Zoho, GoHighLevel. **3. API + MCP for GTM engineers** — Phantombuster has an API for triggering phantoms. TexAu has an API for every action plus an MCP server at mcp.texau.com/mcp so AI agents call TexAu actions natively. --- url: https://www.texau.com/comparison/texau-vs-bitscale title: TexAu vs BitScale section: comparison --- # Same category. Different stage. Different surface area. BitScale is a credible newer entrant in waterfall enrichment with sharp pricing. TexAu has been shipping the action layer — outbound execution, CRM sync, schedulers, MCP, AI columns — long enough to have settled the rough edges. ## Where BitScale wins **Sharp pricing on entry tiers** — BitScale's entry pricing is competitive and they're aggressive about credit-cost transparency. If your only need is "enrich a list with a waterfall and pay as little as possible," they're a real option. **Modern UX, less legacy** — BitScale's product is newer and the UX shows it — clean, fast, fewer dead corners. **Active feature velocity** — The team is shipping. New integrations, new actions, new model support land regularly. ## Where TexAu wins **1. Action catalog depth** — TexAu's action catalog is 200+ ready-to-run actions across find, enrich, verify, score, send, sync. BitScale's catalog is in the dozens — strong on enrichment, lighter on the action and integration tail. **2. Real bidirectional CRM sync** — BitScale ships CRM connectors. TexAu ships bidirectional, field-level, audit-logged sync to HubSpot, Salesforce, Pipedrive, Zoho, GoHighLevel — with conflict resolution, dry-run mode, and revert. **3. Native MCP server** — TexAu was MCP-native from day one. Every action exposed as an MCP tool at mcp.texau.com/mcp, on every plan. BitScale does not currently ship a public MCP server. --- url: https://www.texau.com/comparison/texau-vs-lusha title: TexAu vs Lusha section: comparison --- # Lusha gets you one contact. TexAu gets you the pipeline. Lusha's Chrome extension is the cleanest way to grab a single contact off LinkedIn. We respect that. But the moment you need 1,000 contacts enriched, scored, and pushed to a sequencer — let alone an AI agent calling enrichment as a tool — Lusha runs out of room. TexAu starts there. ## Where Lusha wins **The Chrome extension** — For grabbing one contact off LinkedIn while you're already there, Lusha's extension is genuinely the smoothest UX in the category. **Simple pricing for individual users** — Lusha's free + Pro tiers are straightforward and accessible. For an individual SDR or a founder doing solo outreach, the friction is low. **Compliance posture** — Lusha has invested heavily in GDPR, CCPA, and ISO 27701 compliance. For European teams concerned about source-of-data legitimacy, Lusha's documentation is solid. ## Where TexAu wins **1. Pipelines, not point lookups** — Lusha is built around looking up one contact at a time. TexAu is built around running a list — find 500 prospects, enrich all of them, verify, score, push to Smartlead, log to HubSpot — as a single pipeline. **2. 32-integration waterfall, not single-source** — Lusha's data comes from Lusha. TexAu cascades 32 integrations per request and tells you which one delivered. Fill rate is materially higher because the union of 32 databases beats any single one. **3. API + MCP-native at every tier** — Lusha has a paid API tier. TexAu's REST API is on the free tier, every action available, no use-case approval. The MCP server lets agents in Claude Desktop or Cursor call enrichment as a first-class tool. --- url: https://www.texau.com/features/waterfall-enrichment title: Waterfall Enrichment section: feature --- # Stop overpaying for enrichment. Run a waterfall. TexAu cascades a single enrichment request across the providers you trust — Hunter, Snov, Apollo, RocketReach, ZoomInfo, Dropcontact, Clearbit, and more — stopping the moment a verified result comes back. You pay one provider, not five, and only when the cheaper sources fail. ## Capabilities **Stack any provider** — Drag providers into the order you want. TexAu handles auth, rate limits, and credit budgeting. **Stop on first match** — The waterfall halts the instant a provider returns a verified result, so credits stay in your pocket. **Per-field cascades** — Chase email, phone, and firmographics through different ladders. Each field finds its cheapest valid source. **Audit every dollar** — Every step logged with cost, latency, confidence. Prune providers that never win. **Deterministic re-runs** — Re-run a row and TexAu skips providers that already answered — no double charges. ## How it works Drop the Waterfall Enrichment step into any workflow, pick the providers, and TexAu does the rest. Each row enters the cascade, walks down the ladder, and exits with the cheapest verified value plus a per-field provenance record. ## FAQ **Q: What is waterfall enrichment?** A: Querying multiple data providers in a defined order and stopping the moment one returns a verified result. Minimizes credit spend without sacrificing coverage. **Q: Which providers does TexAu support?** A: Hunter, Snov, Apollo, RocketReach, ZoomInfo, Dropcontact, Clearbit, Lusha, NeverBounce, and any custom HTTP enrichment endpoint you add. **Q: Do I get charged by every provider in the cascade?** A: No. The waterfall stops at the first verified match. Providers below the match are never called. --- url: https://www.texau.com/features/email-verification title: Email Verification section: feature --- # Verify every email before it costs you a domain. TexAu plugs verification into any workflow as a hard gate. NeverBounce, ZeroBounce, Million Verifier, and Kickbox run inline; only valid addresses move forward. Bad data dies before it touches your sending infrastructure. ## Capabilities **Inline verification** — A verification step lives anywhere in your workflow. No batch uploads, no CSV juggling. **Provider waterfall** — Cascade across NeverBounce, ZeroBounce, Million Verifier, and Kickbox the same way you cascade enrichment. **Result caching** — Verified addresses are cached, so re-running a list never re-charges providers for known-good rows. **Granular routing** — Route catch-all, risky, or invalid addresses down separate branches. **Reputation guardrails** — Hard caps on bounce rate per sending domain. Verifications stop the workflow before you cross threshold. ## How it works Drop the Verify Email step before any send action. Each row is checked, scored, and routed by status. Workflows that touch your sending infrastructure cannot proceed without verification flipping the gate to green. ## FAQ **Q: Why do I need email verification?** A: Sending to invalid addresses raises bounce rate, destroys sender reputation, and lands future emails in spam. Verification stops bad sends before they happen. **Q: Which providers does TexAu support?** A: NeverBounce, ZeroBounce, Million Verifier, Kickbox, Hunter, and any custom HTTP verifier. **Q: Are verification results cached?** A: Yes. Once an address has been verified, the result is cached against your workspace and re-used on future runs. --- url: https://www.texau.com/features/ai-lead-scoring title: Custom Scoring with the AI Column section: feature --- # Lead scoring you wrote yourself, not a black box you hope is right. TexAu does not ship a packaged "AI scoring model." Instead, the AI Column lets you write a prompt + a system prompt, pass in any column data on the row, and return a 0–100 score, a classification, or a routing decision — per row, on demand. You define the rubric. The model evaluates each row against it. BYOK supported (GPT, Claude, Gemini). ## Capabilities **You write the rubric** — A prompt describes what a great lead looks like. A system prompt sets the tone, output format, and guardrails. No training pipeline, no monthly re-train cycle. **Personalized per row** — Pass any combination of enriched fields — industry, headcount, tech stack, post engagement, recent funding — into the prompt as variables. The output is grounded in the row, not in a vibe. **Any output shape** — Return a 0–100 score, a tier (A/B/C), a routing decision, or a one-line reason. Whatever your downstream system needs. **Same tool over API and MCP** — The exact prompt that runs in your TexAu table also runs as a REST endpoint and as an MCP tool. One source of truth. **BYOK** — Bring your OpenAI, Anthropic, or Gemini key. Your tokens, your billing, your privacy. Or pay 1 credit per row through TexAu. ## How it works Right-click a column. Pick AI Column. Write the prompt and system prompt. Pass the variables you want the model to see. Run it on the table, on a schedule, over the API, or from your MCP-connected agent. Edit the prompt, rerun — no training loop required. ## FAQ **Q: Does TexAu train a model on my closed-won deals?** A: No. We deliberately do not ship a packaged "trained on your closed-won" scorer — the data shape and label quality required to make that honest is rare. Instead, the AI Column gives you a prompt-driven scoring surface you control end-to-end. If you have a separate model you want to call, you can wire it via a custom HTTP action and surface the score the same way. **Q: Is the score explainable?** A: Yes — return the score and the reasoning in the same prompt. Most teams ask the model to return JSON like { score, top_reasons }. The reasons are whatever the prompt asks for. **Q: How is this different from AI Columns?** A: Same primitive, different framing. The AI Column is the underlying tool. "Custom scoring" is one of the most common things teams use it for. Same goes for summarization, classification, lead routing, draft generation, etc. --- url: https://www.texau.com/features/ai-columns title: AI Columns section: feature --- # Right-click any column. Transform it with AI. Summarize, extract, classify, score, draft, translate. Use a template, paste a prompt, or bring your own. Runs on GPT, Claude, Gemini, or your own API key — your tokens, your billing, your privacy. ## Capabilities **Summarize** — "Summarize this LinkedIn bio in 25 words." Bio in, summary out, no GPT preamble. **Extract** — "Extract seniority, function, and company." Returns clean structured JSON parsed into separate columns. **Classify** — SaaS, agency, marketplace, fintech, other. Multi-label or single-label, your choice. **Draft** — Generate a one-line outbound hook from any enriched lead row. **Translate** — Localize bios, descriptions, and outbound copy into the buyer's language. **Bring your own key** — GPT, Claude, Gemini — your API key, your tokens, your billing, your privacy. ## How it works Right-click any column. Pick from 40+ prompt templates or paste your own. Choose the model — TexAu credits or BYOK. The same transform runs over the API and MCP unchanged. ## FAQ **Q: Which AI models does TexAu support?** A: OpenAI (GPT-4o, GPT-4.1, o3), Anthropic (Claude 3.5/3.7/4 family), Google (Gemini 1.5/2.0). BYOK supported on every model. **Q: What is BYOK?** A: Bring Your Own Key. Add your OpenAI/Anthropic/Gemini API key and AI columns run on your account — your tokens, your billing, your privacy. **Q: Can AI columns return structured JSON?** A: Yes. Use the Extract template. The output is parsed into separate typed columns automatically. --- url: https://www.texau.com/features/crm-sync title: CRM Sync section: feature --- # CRM sync without the spreadsheet middleman. TexAu syncs enriched, verified records straight into your CRM — one-way for read-only mirrors, bidirectional for live ownership. Field mapping, dedupe, and lifecycle stage updates are first-class, not afterthoughts. ## Capabilities **One-way push** — Create or update records with full field mapping and idempotent upserts. **Bidirectional sync** — Subscribe to CRM events and feed them back into TexAu workflows. Both systems stay aligned. **Native dedupe** — Match on email, domain, LinkedIn URL, or any custom key. Stop creating duplicates. **Lifecycle automation** — Promote leads through lifecycle stages on signal — replies, meetings, qualifications. **Field-level control** — Map every TexAu field to a CRM field with overwrite, fill-if-empty, or never-touch semantics. **Audit trail** — Every CRM write logged with payload, response, and outcome — finance, RevOps, and CS can trace any record. ## How it works Connect your CRM once. Pick the object (Lead, Contact, Account, Deal). Map TexAu fields to CRM fields. Choose one-way push, or enable webhooks for bidirectional. Every workflow that produces a row writes cleanly into your system of record. ## FAQ **Q: Which CRMs does TexAu sync with?** A: HubSpot, Salesforce, Pipedrive, Zoho, GoHighLevel, Close, Attio, Copper. Any CRM with a REST API can be wired via the HTTP integration. **Q: What is the difference between one-way and bidirectional sync?** A: One-way pushes records from TexAu into the CRM. Bidirectional also subscribes to CRM events (record created, updated, stage changed) and feeds them back into TexAu workflows. **Q: Will TexAu create duplicate records?** A: No. Every CRM sync step uses idempotent upsert keyed on email, domain, LinkedIn URL, or any custom key. --- url: https://www.texau.com/features/column-actions title: Column Actions section: feature --- # The table is the execution layer. 200+ ready-to-run actions, one right-click. Search people, enrich profiles, find phone numbers, push to outbound, log to CRM, send a LinkedIn DM. Everything that needed five tools is now a column. ## Capabilities **Find** — Search people, search companies, find emails, find phone numbers, find LinkedIn URLs. ~40 actions. **Enrich** — Pull firmographics, technographics, hiring signals, funding rounds, news mentions. ~60 actions. **Verify** — Validate emails, phone numbers, LinkedIn URLs, domains. Cached results re-used across runs. **Score** — AI Column for custom prompt-driven scoring, plus rule-based and intent scoring — all column-native. **Send** — Outbound rails: Smartlead, Instantly, Lemlist, Reply, Apollo, Outreach. LinkedIn DM, Twitter DM. **Sync** — Push or pull from HubSpot, Salesforce, Pipedrive, Zoho, GoHighLevel. ## How it works Paste your list. Right-click. Pick the action. Done. No workflow canvas, no nodes. If you want to automate it later, save the column action as a template and run it on a schedule. Same actions on the API and MCP at the same credit cost. ## FAQ **Q: How many actions does TexAu support?** A: 200+ ready-to-run actions across six categories — Find, Enrich, Verify, Score, Send, Sync. Catalog at /apps. **Q: Do actions run over the API?** A: Yes. Every column action is a REST endpoint and an MCP tool with the same credit cost as the table. **Q: How big a list can I run?** A: 50K rows in one click on Pro and above. Larger lists run as scheduled batches. --- url: https://www.texau.com/features/schedulers title: Schedulers section: feature --- # Workflows that run themselves, on the cadence the work demands. TexAu workflows run on cron, on calendar, on inbound signal, or on demand. Schedule the daily LinkedIn pull, the weekly enrichment refresh, the hourly intent sweep — and let the bench tend itself. ## Capabilities **Cron + calendar** — Plain English ("every weekday at 9am UTC") or full cron syntax. Both first-class. **Time-zone aware** — Schedules run in the time zone you specify per workflow. DST handled correctly. **Signal-triggered runs** — Trigger on inbound webhook, CRM stage change, form submit, or Slack command. **Concurrency control** — Cap parallel runs per workflow so you never overload an upstream provider. **Run history** — Every run logged with duration, rows processed, credits, errors. Searchable. **Pause + resume** — Pause from the UI or API. Pick up exactly where you left off. ## How it works Open any workflow. Add a Schedule. Pick a frequency — cron, calendar, or signal. TexAu queues the runs, executes with the concurrency cap you set, and posts results to the destinations the workflow already knows about. ## FAQ **Q: Can I schedule workflows on cron?** A: Yes — cron expressions, plain-English calendar rules, or signal triggers. Time-zone aware. **Q: How are concurrent runs handled?** A: Each workflow has a concurrency cap. New runs queue, skip, or run in parallel — your choice per workflow. **Q: Can I pause a scheduled workflow?** A: Yes. Pause from the UI or API. Resuming continues from the next scheduled tick. --- url: https://www.texau.com/features/templates title: Templates section: feature --- # Build it once. Run it across every client, every list, every workspace. Save any column action — or any chain of them — as a template. Deploy across client workspaces, share across team members, version-control every edit. Build the workflow on Monday; ship it across ten clients before lunch. ## Capabilities **Single column action** — "Find email" with your input mapping and credit policy. Right-click → Save as template. **Chain of actions** — "Find → verify → enrich → score → push." The whole pipeline as one named template. **Scheduled run** — Chain plus cron expression and trigger. Templates carry their schedule when deployed. **Full table schema** — Every column type, every action, every filter — saved as a workspace blueprint. New client workspace in seconds. **Versioned** — Every edit creates a new version. Roll back any deployment to a prior version per workspace. **Workspace-aware** — Same template, different workspace, different credit budget. No leaking client data. ## How it works Right-click any saved workflow → Save as template. Pick the visibility (private, team, public). Deploy to any workspace with one click. The same template runs in the table, over the API, and as an MCP tool. ## FAQ **Q: What can I save as a template?** A: A single column action, a chain of actions, a scheduled run, or a full table schema. **Q: Are templates versioned?** A: Yes. Every edit creates a new version. Each workspace can pin to a specific version or auto-upgrade. **Q: Can I share templates with my team?** A: Yes — private, team, or public visibility. Public templates show up in the workflow library. --- url: https://www.texau.com/features/gtm-copilot title: GTM Copilot section: feature --- # Type the table you wish existed. The Copilot builds it. Tell GTM Copilot what you want — "Find Series B SaaS in Europe hiring data engineers, enrich the CTO, push to HubSpot" — and it composes the table, picks providers, wires the steps, and hands you a working workflow. ## Capabilities **Plain-English to production** — Describe the outcome. Copilot picks sources, enrichment, verification, sync — and explains every choice. **Composable, not magic** — Every step Copilot generates is a real TexAu step you can edit, swap, or delete. Nothing locked behind the prompt. **Cost-aware** — Copilot ranks provider options by cost and coverage so you ship the cheapest plan that hits your quality bar. **Iterate in chat** — "Add LinkedIn intent." "Switch to a Hunter-first waterfall." "Skip catch-alls." Copilot edits the table in place. **Explain mode** — Ask "why this step?" on any block — Copilot defends the decision in plain English. **Bring your own data** — Point Copilot at a CSV, CRM segment, or Sheet. The table builds around your existing rows. ## How it works Open a fresh table. Type what you want it to do. GTM Copilot proposes a complete table with steps, providers, and rationale. Approve, tweak, or rewrite. Run. ## FAQ **Q: What is GTM Copilot?** A: An AI assistant inside TexAu that turns a plain-English description of a GTM goal into a working TexAu table — schema, enrichment, verification, sync, outbound — in seconds. **Q: Can I edit what GTM Copilot generates?** A: Yes. Every step is a normal TexAu step. Edit fields, swap providers, delete steps, or rewrite the prompt and regenerate. **Q: How does Copilot pick providers?** A: It ranks providers by cost, coverage, and historical accuracy on similar requests, then composes a waterfall that hits your quality bar at the lowest credit spend. **Q: Does it work with my existing data?** A: Yes — CSV, CRM segment, Google Sheet, or existing TexAu table. It builds around those rows. --- url: https://www.texau.com/integrations/claude title: TexAu × Claude Desktop section: integration --- # Sales-data superpowers, inside Claude. Connect Claude Desktop to TexAu's hosted MCP server in 60 seconds. Generate an API key, paste it into your config, restart Claude. Your assistant gets 25+ tools for LinkedIn search, email finding, waterfall enrichment, and verification. No local server to run. ## Install ``` export TEXAU_KEY=tx_live_... { "mcpServers": { "texau": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.texau.com/mcp", "--header", "x-api-key:${TEXAU_KEY}" ] } } } ``` ## Pricing The MCP server is free. You pay for what your AI calls — 50 free credits on signup, no card. --- url: https://www.texau.com/integrations/cursor title: TexAu × Cursor section: integration --- # Your IDE just got a sales team. Connect Cursor to TexAu's hosted MCP server. Generate an API key, paste it into your MCP config, reload. Your editor's AI can search LinkedIn, find emails, and enrich profiles without leaving the codebase. ## Install ``` export TEXAU_KEY=tx_live_... { "mcpServers": { "texau": { "url": "https://mcp.texau.com/mcp", "headers": { "x-api-key": "${TEXAU_KEY}" } } } } ``` ## Pricing Same pricing as everywhere else — 50 free credits on signup, then prepaid credit bundles. The MCP server itself is free. --- url: https://www.texau.com/integrations/windsurf title: TexAu × Windsurf section: integration --- # Codeium agents that close deals. Connect Windsurf to TexAu's hosted MCP server. Generate an API key, paste it into the MCP server entry, reload. Cascade (Codeium's agent) gets 25+ tools for LinkedIn search, email finding, and waterfall enrichment. ## Install ``` export TEXAU_KEY=tx_live_... { "mcpServers": { "texau": { "transport": "http", "url": "https://mcp.texau.com/mcp", "headers": { "x-api-key": "${TEXAU_KEY}" } } } } ``` ## Pricing Free MCP server. Free 50 starter credits on signup. Prepaid bundles for everything beyond — no separate Windsurf billing. --- url: https://www.texau.com/integrations/chatgpt title: TexAu × ChatGPT section: integration --- # ChatGPT with sales superpowers. ChatGPT doesn't yet support customer-installed MCP servers. The moment OpenAI ships it, TexAu will connect to mcp.texau.com on day one with the same x-api-key flow as every other client. In the meantime, hit our REST API directly from a Custom GPT or use Claude. ## Install ``` # ChatGPT doesn't ship customer-installed MCP yet. Two real options today: # 1) Call the TexAu REST API directly from a Custom GPT action. export TEXAU_KEY=tx_live_... curl https://api.texau.com/v1/email/find \ -H "x-api-key: ${TEXAU_KEY}" \ -H "content-type: application/json" \ -d '{"name":"Patrick Collison","company":"Stripe"}' # 2) Use Claude Desktop, Cursor, Windsurf, or VS Code — full MCP today. ``` ## Pricing When ChatGPT MCP ships, pricing will mirror every other client — 50 free credits on signup, then prepaid bundles from $0.020/credit. --- url: https://www.texau.com/integrations/vs-code title: TexAu × VS Code section: integration --- # Copilot Chat, but with real GTM data. Connect VS Code to TexAu's hosted MCP server. Generate an API key, paste it into settings.json, reload. Copilot Chat (in agent mode) gets 25+ tools for LinkedIn search, email finder, waterfall enrichment, and verification — right alongside your code. ## Install ``` export TEXAU_KEY=tx_live_... { "mcp": { "servers": { "texau": { "type": "http", "url": "https://mcp.texau.com/mcp", "headers": { "x-api-key": "${TEXAU_KEY}" } } } } } ``` ## Pricing Same as the rest — 50 free credits on signup, then prepaid bundles. No VS Code-specific pricing. --- url: https://www.texau.com/glossary/xml-extensible-markup-language title: XML (Extensible Markup Language) section: glossary --- # XML (Extensible Markup Language) XML (Extensible Markup Language) is a structured markup format for representing hierarchical data — older than JSON, still common in enterprise integrations, SOAP, and document standards. --- url: https://www.texau.com/glossary/webhook title: Webhook section: glossary --- # Webhook A webhook is a user-defined HTTP callback — system A POSTs to a URL on system B the moment an event happens — the simplest way to make integrations real-time. --- url: https://www.texau.com/glossary/warm-outreach title: Warm Outreach section: glossary --- # Warm Outreach Warm outreach is contact with a prospect who has some prior connection — they've engaged with your content, met you at an event, been referred — making the conversation easier to start. --- url: https://www.texau.com/glossary/verification title: Verification section: glossary --- # Verification Verification confirms a piece of data is genuine — an email actually receives mail, a phone actually rings, a person actually exists at that company — beyond just looking syntactically correct. --- url: https://www.texau.com/glossary/user-engagement-metrics title: User Engagement Metrics section: glossary --- # User Engagement Metrics User engagement metrics measure how actively users interact with your product or content — sessions, feature usage, time-in-app — and they predict retention, expansion, and PQL conversion. --- url: https://www.texau.com/glossary/upsert title: Upsert section: glossary --- # Upsert An upsert is a database operation that inserts a record if it doesn't exist or updates it if it does — the safe way to write data idempotently across systems. --- url: https://www.texau.com/glossary/unstructured-data title: Unstructured Data section: glossary --- # Unstructured Data Unstructured data is information without a fixed schema — emails, transcripts, web pages, social posts — and it's where the most valuable buying signals hide in 2026. --- url: https://www.texau.com/glossary/trigger title: Trigger section: glossary --- # Trigger A trigger is the event that starts an automation — a form submit, a CRM update, a webhook, a scheduled time — the entry point every workflow defines first. --- url: https://www.texau.com/glossary/trigger-based-automation title: Trigger-Based Automation section: glossary --- # Trigger-Based Automation Trigger-based automation runs the moment a defined event occurs — a job change, a website visit, a CRM stage move — turning static workflows into responsive, signal-driven plays. --- url: https://www.texau.com/glossary/third-party-data title: Third-Party Data section: glossary --- # Third-Party Data Third-party data is information collected by someone else and sold or licensed to you — enrichment, intent, firmographics — increasingly subject to privacy rules in 2026. --- url: https://www.texau.com/glossary/task-automation title: Task Automation section: glossary --- # Task Automation Task automation hands a discrete, repeatable task — sending a notification, updating a field, scheduling a follow-up — to software so humans don't do it manually. --- url: https://www.texau.com/glossary/target-audience title: Target Audience section: glossary --- # Target Audience Target audience is the specific group your product, message, or campaign is built for — the explicit decision about who you're trying to reach and who you're not. --- url: https://www.texau.com/glossary/subscription-plan title: Subscription Plan section: glossary --- # Subscription Plan A subscription plan is the packaged tier — features, limits, support level — sold for a recurring fee, the foundation of every SaaS revenue model. --- url: https://www.texau.com/glossary/spam-score title: Spam Score section: glossary --- # Spam Score Spam score is a numeric estimate of how likely a message is to be classified as spam — based on content, sender reputation, list quality, and dozens of other deliverability signals. --- url: https://www.texau.com/glossary/sales-qualified-lead title: Sales Qualified Lead (SQL) section: glossary --- # Sales Qualified Lead (SQL) A Sales Qualified Lead (SQL) is a lead that sales has talked to and confirmed represents a real, near-term opportunity — past the marketing-defined MQL bar. --- url: https://www.texau.com/glossary/sales-funnel title: Sales Funnel section: glossary --- # Sales Funnel A sales funnel is the conceptual model of how prospects move from awareness to closed customer — visualized as a narrowing series of stages where most don't convert at each step. --- url: https://www.texau.com/glossary/sales-automation title: Sales Automation section: glossary --- # Sales Automation Sales automation handles the repetitive parts of the sales process — sequence sending, activity logging, follow-up reminders, lead routing — so reps can spend their time with buyers. --- url: https://www.texau.com/glossary/robotic-process-automation title: Robotic Process Automation (RPA) section: glossary --- # Robotic Process Automation (RPA) Robotic Process Automation (RPA) uses software bots to execute repetitive, rule-based tasks across UIs and APIs — a foundational layer of enterprise automation that AI is now extending. --- url: https://www.texau.com/glossary/real-time-automation title: Real-Time Automation section: glossary --- # Real-Time Automation Real-time automation reacts within seconds of an event — a form submit, a status change, a webhook — instead of waiting for the next scheduled batch run. --- url: https://www.texau.com/glossary/rate-limiting title: Rate Limiting section: glossary --- # Rate Limiting Rate limiting caps how many requests an API or system will accept per second/minute/day — the default protection against abuse and the constraint your integrations must respect. --- url: https://www.texau.com/glossary/prospect-list title: Prospect List section: glossary --- # Prospect List A prospect list is the curated set of accounts and contacts you're actively reaching out to — built from ICP criteria, enriched, scored, and ready for sequencing. --- url: https://www.texau.com/glossary/primary-key title: Primary Key section: glossary --- # Primary Key A primary key is the unique identifier that distinguishes one record from every other in the same table — the anchor that joins, dedupes, and updates depend on. --- url: https://www.texau.com/glossary/performance-metrics title: Performance Metrics section: glossary --- # Performance Metrics Performance metrics are the numbers a team uses to measure whether the work is working — picked deliberately to align with goals and keep everyone rowing in the same direction. --- url: https://www.texau.com/glossary/pay-as-you-go title: Pay As You Go section: glossary --- # Pay As You Go Pay-as-you-go is a usage-based pricing model where customers pay for what they consume — API calls, enriched records, sends — instead of a fixed monthly seat or tier. --- url: https://www.texau.com/glossary/outlier-detection title: Outlier Detection section: glossary --- # Outlier Detection Outlier detection finds the records that don't fit the rest of the dataset — abnormal revenue, weird email patterns, sudden spikes — flagging them for review or special handling. --- url: https://www.texau.com/glossary/outbound-sequencing title: Outbound Sequencing section: glossary --- # Outbound Sequencing Outbound sequencing is the orchestration layer that runs multi-step, multi-channel outreach plays — pacing, branching, channel switches, auto-pause on reply. --- url: https://www.texau.com/glossary/outbound-marketing title: Outbound Marketing section: glossary --- # Outbound Marketing Outbound marketing is every motion that proactively reaches prospects — cold email, LinkedIn, ads, calling — instead of waiting for them to come to you through inbound channels. --- url: https://www.texau.com/glossary/open-rate title: Open Rate section: glossary --- # Open Rate Open rate is the percentage of recipients who opened your email — once a top KPI, now degraded by privacy protections and AI summarizers and treated as a noisy signal in 2026. --- url: https://www.texau.com/glossary/multi-channel-outreach title: Multi-Channel Outreach section: glossary --- # Multi-Channel Outreach Multi-channel outreach combines email, LinkedIn, phone, and (sometimes) SMS or direct mail into a coordinated sequence — lifting reply rates over single-channel by significant margins. --- url: https://www.texau.com/glossary/marketing-qualified-lead title: Marketing Qualified Lead (MQL) section: glossary --- # Marketing Qualified Lead (MQL) A Marketing Qualified Lead (MQL) is a lead that has shown enough engagement and fit to merit sales follow-up — but hasn't yet been validated as a real opportunity. --- url: https://www.texau.com/glossary/marketing-automation title: Marketing Automation section: glossary --- # Marketing Automation Marketing automation runs lifecycle programs — drip emails, lead scoring, behavioral triggers, attribution — at scale without a human touching each contact. --- url: https://www.texau.com/glossary/lookup-table title: Lookup Table section: glossary --- # Lookup Table A lookup table maps one value to another — country code to name, plan tier to price — letting workflows translate codes into meaningful values without hardcoding. --- url: https://www.texau.com/glossary/lead-scoring title: Lead Scoring section: glossary --- # Lead Scoring Lead scoring assigns each lead a numeric value reflecting fit and intent, so sales can prioritize the leads most likely to convert and ignore (or nurture) the rest. --- url: https://www.texau.com/glossary/lead-scoring-model title: Lead Scoring Model section: glossary --- # Lead Scoring Model A lead scoring model is the explicit set of rules and weights that produces a lead score — the formula behind "this lead is an A, that one is a C." --- url: https://www.texau.com/glossary/lead-qualification title: Lead Qualification section: glossary --- # Lead Qualification Lead qualification is the gate that decides which leads are worth a sales conversation — fit, intent, authority, timing — and which should be nurtured or disqualified. --- url: https://www.texau.com/glossary/lead-nurturing title: Lead Nurturing section: glossary --- # Lead Nurturing Lead nurturing is the long-cycle relationship-building program — content, check-ins, re-engagement — that keeps not-yet-ready leads warm until they're ready to buy. --- url: https://www.texau.com/glossary/lead-generation title: Lead Generation section: glossary --- # Lead Generation Lead generation is every activity that produces a new prospect record for the sales pipeline — inbound forms, outbound prospecting, paid ads, partnerships, events. --- url: https://www.texau.com/glossary/lead-attribution title: Lead Attribution section: glossary --- # Lead Attribution Lead attribution assigns credit to the marketing or sales touch(es) that produced a lead — first touch, last touch, multi-touch — and decides where the next dollar of spend goes. --- url: https://www.texau.com/glossary/knowledge-graph title: Knowledge Graph section: glossary --- # Knowledge Graph A knowledge graph models entities and the relationships between them — people, companies, products, events — as a queryable network rather than rows in a table. --- url: https://www.texau.com/glossary/javascript-object-notation title: JavaScript Object Notation section: glossary --- # JavaScript Object Notation JavaScript Object Notation (JSON) is the lightweight key-value data format that nearly every modern API speaks — the lingua franca of the integration layer. --- url: https://www.texau.com/glossary/ip-warming title: IP Warming section: glossary --- # IP Warming IP warming is the process of gradually increasing send volume from a new sending IP so inbox providers learn to trust it — preventing the cold-IP spam-folder hit. --- url: https://www.texau.com/glossary/intent-data title: Intent Data section: glossary --- # Intent Data Intent data signals which accounts are actively researching your category — content consumption, search behavior, peer-review activity — and it's the most actionable layer in modern outbound. --- url: https://www.texau.com/glossary/inbound-marketing title: Inbound Marketing section: glossary --- # Inbound Marketing Inbound marketing earns attention with content and SEO so prospects come to you — the demand-capture half of the GTM motion that pairs with outbound. --- url: https://www.texau.com/glossary/identity-resolution title: Identity Resolution section: glossary --- # Identity Resolution Identity resolution stitches together fragmented signals — different emails, devices, accounts — into a single profile of one real person or account. --- url: https://www.texau.com/glossary/hyperautomation title: Hyperautomation section: glossary --- # Hyperautomation Hyperautomation is the orchestrated combination of RPA, AI, workflow automation, and process mining to automate as many business processes as can be automated — end to end. --- url: https://www.texau.com/glossary/funnel-optimization title: Funnel Optimization section: glossary --- # Funnel Optimization Funnel optimization is the systematic improvement of conversion at each stage of the buyer journey — visit → lead → MQL → SQL → opportunity → close. --- url: https://www.texau.com/glossary/follow-up-email title: Follow-Up Email section: glossary --- # Follow-Up Email A follow-up email is any message after the first touch — a sequence step, a nudge after a meeting, a re-engagement — and it's where most outbound responses actually come from. --- url: https://www.texau.com/glossary/first-party-data title: First-Party Data section: glossary --- # First-Party Data First-party data is information you collect directly from your audience — site visits, signups, purchases, support tickets — and it's the most valuable data class in the post-cookie 2026 GTM stack. --- url: https://www.texau.com/glossary/export-formats title: Export Formats section: glossary --- # Export Formats Export formats are the file types — CSV, Excel, JSON, Parquet — that systems use to deliver data outward, each with tradeoffs in size, schema strength, and tool support. --- url: https://www.texau.com/glossary/event-driven-automation title: Event-Driven Automation section: glossary --- # Event-Driven Automation Event-driven automation runs the moment something happens — a form submit, a webhook, a status change — instead of waiting for a scheduled batch. --- url: https://www.texau.com/glossary/enrichment title: Enrichment section: glossary --- # Enrichment Enrichment adds depth to a thin record — emails, phone numbers, firmographics, intent signals — turning sparse leads into actionable prospects ready for outbound. --- url: https://www.texau.com/glossary/email-warm-up title: Email Warm-Up section: glossary --- # Email Warm-Up Email warm-up gradually ramps a new mailbox's send volume and engagement so inbox providers learn to trust it before any cold outreach starts. --- url: https://www.texau.com/glossary/email-verification title: Email Verification section: glossary --- # Email Verification Email verification confirms an address exists and accepts mail — beyond format-checking — preventing bounces that wreck sender reputation and deliverability. --- url: https://www.texau.com/glossary/email-tracking title: Email Tracking section: glossary --- # Email Tracking Email tracking is the per-message instrumentation — opens via tracking pixel, clicks via wrapped links, replies via mailbox sync — that powers engagement metrics. --- url: https://www.texau.com/glossary/email-template title: Email Template section: glossary --- # Email Template An email template is a reusable message skeleton with merge fields for personalization — the base layer that AI personalization and sequencer logic build on top of. --- url: https://www.texau.com/glossary/email-sequence title: Email Sequence section: glossary --- # Email Sequence An email sequence is a multi-step series of messages sent over days or weeks to a single prospect, designed to escalate engagement and earn a reply. --- url: https://www.texau.com/glossary/email-list title: Email List section: glossary --- # Email List An email list is the audience for an email program — the contacts you're sending to — and its quality determines campaign performance more than any other single factor. --- url: https://www.texau.com/glossary/email-finder title: Email Finder section: glossary --- # Email Finder An email finder takes a name + company (or a profile URL) and returns the work email — the workhorse tool of outbound prospecting and a core enrichment primitive. --- url: https://www.texau.com/glossary/email-deliverability title: Email Deliverability section: glossary --- # Email Deliverability Email deliverability is the share of your sent email that actually reaches the inbox — not the spam folder, not the void — and it depends on sender reputation, list quality, and content. --- url: https://www.texau.com/glossary/email-campaign title: Email Campaign section: glossary --- # Email Campaign An email campaign is a coordinated set of email sends — one or many — designed to drive a specific outcome for a defined audience within a defined window. --- url: https://www.texau.com/glossary/email-automation title: Email Automation section: glossary --- # Email Automation Email automation is any system that sends, schedules, or routes email based on triggers and rules instead of a human pressing send — the engine behind drip, nurture, and outbound at scale. --- url: https://www.texau.com/glossary/email-analytics title: Email Analytics section: glossary --- # Email Analytics Email analytics measures how recipients behave with your sends — delivered, opened, clicked, replied, unsubscribed — and rolls up to the metrics that decide whether the campaign worked. --- url: https://www.texau.com/glossary/drip-campaigns title: Drip Campaigns section: glossary --- # Drip Campaigns Drip campaigns send a pre-scheduled series of messages over time — onboarding sequences, nurture flows, win-back tracks — to move a contact toward a defined outcome. --- url: https://www.texau.com/glossary/data-verification title: Data Verification section: glossary --- # Data Verification Data verification confirms that a value is real — the email actually receives mail, the phone actually rings, the company actually exists — beyond just looking correctly formatted. --- url: https://www.texau.com/glossary/data-validation title: Data Validation section: glossary --- # Data Validation Data validation checks whether each value meets defined rules — format, range, presence, referential integrity — and rejects or flags the ones that don't before they corrupt downstream systems. --- url: https://www.texau.com/glossary/data-standardization title: Data Standardization section: glossary --- # Data Standardization Data standardization rewrites field values to a common format — title case, country codes, normalized phone numbers — so the same logical value reads the same everywhere. --- url: https://www.texau.com/glossary/data-source title: Data Source section: glossary --- # Data Source A data source is any system that produces data you ingest — your CRM, your product analytics, an enrichment provider, an intent vendor, a webhook from a partner. --- url: https://www.texau.com/glossary/data-segmentation title: Data Segmentation section: glossary --- # Data Segmentation Data segmentation divides a population into groups that behave or look alike — by firmographic, behavior, lifecycle stage — so each group can be addressed with the right message. --- url: https://www.texau.com/glossary/data-quality title: Data Quality section: glossary --- # Data Quality Data quality is the composite measure of how trustworthy a dataset is — accuracy, completeness, consistency, freshness, validity, uniqueness — and it makes or breaks every downstream automation. --- url: https://www.texau.com/glossary/data-profiling title: Data Profiling section: glossary --- # Data Profiling Data profiling analyzes the structure and content of a dataset — distributions, completeness, anomalies — to understand what you actually have before you act on it. --- url: https://www.texau.com/glossary/data-pipeline title: Data Pipeline section: glossary --- # Data Pipeline A data pipeline is the chain of steps that moves data from a source through transformations into a destination — extract, load, transform, deliver. --- url: https://www.texau.com/glossary/data-normalization title: Data Normalization section: glossary --- # Data Normalization Data normalization rewrites raw values into a consistent canonical format — phone numbers, country names, job titles — so downstream systems can compare them reliably. --- url: https://www.texau.com/glossary/data-matching title: Data Matching section: glossary --- # Data Matching Data matching identifies records across or within datasets that refer to the same entity — the foundation of dedup, identity resolution, and cross-system stitching. --- url: https://www.texau.com/glossary/data-mapping title: Data Mapping section: glossary --- # Data Mapping Data mapping defines how fields in a source system correspond to fields in a destination system — the contract that makes integration work without losing meaning. --- url: https://www.texau.com/glossary/data-integration title: Data Integration section: glossary --- # Data Integration Data integration connects two or more systems so data flows between them automatically — the wiring that turns a stack of tools into a single operating surface. --- url: https://www.texau.com/glossary/data-hygiene title: Data Hygiene section: glossary --- # Data Hygiene Data hygiene is the ongoing maintenance — cleansing, deduping, verifying, refreshing — that keeps a database accurate enough to act on. --- url: https://www.texau.com/glossary/data-governance title: Data Governance section: glossary --- # Data Governance Data governance is the framework — policies, ownership, standards, controls — that makes data trustworthy, compliant, and actually useful across an organization. --- url: https://www.texau.com/glossary/data-enrichment title: Data Enrichment section: glossary --- # Data Enrichment Data enrichment adds missing or fresher attributes — emails, phone numbers, titles, firmographics, tech stack — to your existing records, turning thin leads into actionable ones. --- url: https://www.texau.com/glossary/data-driven-prospecting title: Data-Driven Prospecting section: glossary --- # Data-Driven Prospecting Data-driven prospecting builds outbound lists from explicit ICP signals — firmographics, technographics, intent, hiring, funding — instead of intuition or alphabetical lists. --- url: https://www.texau.com/glossary/data-deduplication title: Data Deduplication section: glossary --- # Data Deduplication Data deduplication finds and merges duplicate records so the same person or account exists exactly once in your system — the prerequisite to accurate reporting and routing. --- url: https://www.texau.com/glossary/data-consistency title: Data Consistency section: glossary --- # Data Consistency Data consistency means the same record reads the same across every system — no contradiction between what the CRM says, what the marketing automation says, and what the warehouse says. --- url: https://www.texau.com/glossary/data-completeness title: Data Completeness section: glossary --- # Data Completeness Data completeness is the share of a record's expected fields that are actually populated — a key dimension of data quality alongside accuracy and freshness. --- url: https://www.texau.com/glossary/data-cleansing title: Data Cleansing section: glossary --- # Data Cleansing Data cleansing finds and fixes broken or inconsistent records — typos, dupes, dead emails, mis-cased fields — turning a messy database into something safe to act on. --- url: https://www.texau.com/glossary/data-append title: Data Append section: glossary --- # Data Append Data append adds missing fields to an existing record by matching against an external dataset — filling in phone numbers, titles, or firmographics that your record didn't have. --- url: https://www.texau.com/glossary/data-aggregation title: Data Aggregation section: glossary --- # Data Aggregation Data aggregation combines records from multiple sources into a single dataset — the foundation of analytics, reporting, and any cross-system view of a customer or account. --- url: https://www.texau.com/glossary/data-accuracy title: Data Accuracy section: glossary --- # Data Accuracy Data accuracy is the degree to which a record matches reality — the right person, the right title, the right phone number — and is the foundation of every downstream automation. --- url: https://www.texau.com/glossary/customer-lifetime-value title: Customer Lifetime Value (CLV) section: glossary --- # Customer Lifetime Value (CLV) Customer Lifetime Value (CLV or LTV) is the total gross profit a customer generates across their entire relationship with your business — the ceiling on what you can spend to acquire them. --- url: https://www.texau.com/glossary/customer-acquisition-cost title: Customer Acquisition Cost (CAC) section: glossary --- # Customer Acquisition Cost (CAC) Customer Acquisition Cost (CAC) is the fully-loaded sales and marketing cost to acquire one new paying customer — the foundation of every SaaS unit-economics model. --- url: https://www.texau.com/glossary/csv-upload title: CSV Upload section: glossary --- # CSV Upload CSV upload is the simplest way to bulk-load data into a system — paste a spreadsheet, map columns, and import — still the workhorse of day-one onboarding for most SaaS tools. --- url: https://www.texau.com/glossary/crm-automation title: CRM Automation section: glossary --- # CRM Automation CRM automation uses workflows inside (or feeding into) the CRM to handle repeatable record-keeping, routing, and follow-up — so reps spend their time selling, not updating fields. --- url: https://www.texau.com/glossary/cost-per-lead title: Cost Per Lead (CPL) section: glossary --- # Cost Per Lead (CPL) Cost Per Lead (CPL) is the total spend on a campaign or channel divided by the number of leads it produced — the basic efficiency metric for top-of-funnel demand-gen. --- url: https://www.texau.com/glossary/conversion-rate title: Conversion Rate section: glossary --- # Conversion Rate Conversion rate is the percentage of people who complete a desired action — sign up, book a demo, buy — out of the total who had the opportunity. --- url: https://www.texau.com/glossary/cold-outreach title: Cold Outreach section: glossary --- # Cold Outreach Cold outreach is the practice of contacting prospects with no prior relationship — across email, LinkedIn, phone, or any channel — to open a sales conversation. --- url: https://www.texau.com/glossary/cold-email title: Cold Email section: glossary --- # Cold Email Cold email is an unsolicited but compliant outreach message sent to a prospect with no prior relationship, used to start a B2B sales conversation. --- url: https://www.texau.com/glossary/click-through-rate title: Click-Through Rate (CTR) section: glossary --- # Click-Through Rate (CTR) Click-Through Rate (CTR) is the percentage of recipients who clicked a tracked link in your message — the most reliable engagement signal in cold outreach now that opens are unreliable. --- url: https://www.texau.com/glossary/buyer-persona title: Buyer Persona section: glossary --- # Buyer Persona A buyer persona is a semi-fictional profile of your ideal customer — role, goals, pains, buying triggers, objections — built from real data and used to align messaging across the team. --- url: https://www.texau.com/glossary/bounce-rate title: Bounce Rate section: glossary --- # Bounce Rate Bounce rate in email is the percentage of sends that don't reach the inbox; on a website, it's the percentage of visitors who leave after viewing only one page. --- url: https://www.texau.com/glossary/batch-processing title: Batch Processing section: glossary --- # Batch Processing Batch processing runs the same operation across a large set of records in one job — overnight enrichments, weekly imports — instead of processing each record as it arrives. --- url: https://www.texau.com/glossary/automation-workflow title: Automation Workflow section: glossary --- # Automation Workflow An automation workflow is a defined sequence of steps — triggers, conditions, actions — that runs without human involvement once started, executing a repeatable process end to end. --- url: https://www.texau.com/glossary/automated-reporting title: Automated Reporting section: glossary --- # Automated Reporting Automated reporting generates and delivers metric reports on a schedule — daily pipeline, weekly cohort, monthly board deck — without anyone manually building the file. --- url: https://www.texau.com/glossary/automated-lead-generation title: Automated Lead Generation section: glossary --- # Automated Lead Generation Automated lead generation uses workflows, scrapers, and AI agents to discover, qualify, and load new prospects into a sales pipeline without manual list-building. --- url: https://www.texau.com/glossary/automated-data-sync title: Automated Data Sync section: glossary --- # Automated Data Sync Automated data sync keeps records in two or more systems matching in near real time, so a change in one (a closed deal, an email opt-out) propagates everywhere it matters. --- url: https://www.texau.com/glossary/api-key title: API Key section: glossary --- # API Key An API key is a unique string that identifies and authenticates a request to an API — the simplest way to gate access to a service without a full OAuth flow. --- url: https://www.texau.com/glossary/api-integration title: API Integration section: glossary --- # API Integration An API integration connects two software systems so they can exchange data and trigger actions on each other automatically — the foundation of every modern GTM stack. --- url: https://www.texau.com/glossary/analytics-dashboard title: Analytics Dashboard section: glossary --- # Analytics Dashboard An analytics dashboard is a single screen that aggregates the metrics a team needs to make decisions — funnel conversion, channel performance, pipeline health — usually in near real time. --- url: https://www.texau.com/glossary/ai-driven-automation title: AI-Driven Automation section: glossary --- # AI-Driven Automation AI-driven automation uses LLMs and ML models to make decisions inside workflows — classifying, scoring, drafting, and routing — instead of relying purely on if/then rules. --- url: https://www.texau.com/glossary/adaptive-outreach title: Adaptive Outreach section: glossary --- # Adaptive Outreach Adaptive outreach is a campaign style where the next message — channel, copy, timing — adjusts in real time to the prospect's prior behavior and enrichment signals. --- url: https://www.texau.com/glossary/active-engagement title: Active Engagement section: glossary --- # Active Engagement Active engagement is when a prospect or user takes an intentional action — reply, click, demo request, in-app feature use — that signals genuine interest beyond a passive open. --- url: https://www.texau.com/glossary/account-warmup title: Account Warm-up section: glossary --- # Account Warm-up Account warm-up is the process of gradually building a sender or social account's reputation so that platforms trust its activity and don't flag it as spam or automation. --- url: https://www.texau.com/glossary/account-based-marketing title: Account-Based Marketing (ABM) section: glossary --- # Account-Based Marketing (ABM) Account-Based Marketing (ABM) is a B2B strategy that treats each target account as its own market — coordinating sales, marketing, and data ops around a tight named-account list. --- url: https://www.texau.com/glossary/ab-testing title: A/B Testing section: glossary --- # A/B Testing A/B testing compares two variants of a message, page, or workflow against the same audience to learn which one drives more conversions.