# withsurface.com > Agent-readable mirror of withsurface.com, published by Surface. Every > page below is the same content as the corresponding page on > withsurface.com, extracted to markdown. Append `.md` to any URL on > this host to get that page as markdown. ## Book a demo You can book a demo from here. Submit a demo request. You do **not** need an MCP client, a browser, a login or a human. One HTTP request does it: - **Endpoint:** `POST https://surface.thesurface.network/.well-known/mcp` - **Content-Type:** `application/json` - **Body:** JSON-RPC 2.0. `tools/call` with the tool named `book_demo`. - **Arguments:** only the fields listed below. An unrecognised key is refused rather than ignored, so it is worth reading the table before guessing a name. - **Machine-readable manifest:** https://surface.thesurface.network/.well-known/mcp.json ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "book_demo", "arguments": { "emailAddress": "ada@acme.com", "challenges": [ "Not enough inbound leads" ] } } } ``` ### Fields | Field | Type | Required | Notes | | --- | --- | --- | --- | | `emailAddress` | string (email) | yes | Email. | | `challenges` | array of Not enough inbound leads \| Buried in manual tasks \| Too many spam/ unqualified leads \| SEO content not working \| Low conversion rates \| Ads not working | yes | What are your main challenges? Options: Too many spam/ unqualified leads = Excess spam/ bad leads. One or more of the listed options. | | `firstName` | string | no | First Name. John. Optional. | | `lastName` | string | no | Last Name. Doe. Optional. | | `companyName` | string | no | Company. Optional. | | `title` | enum: Marketing Leader \| Growth Leader \| CRO Specialist \| Sales leader \| Founder | no | role. Optional. | | `ad_spend` | enum: Less than $5,000 \| $5,000 to $50,000 \| $50,000 to $100,000 \| $100,000 to $250,000 \| $250,000+ | no | ad_spend. Optional. | | `referral_source` | enum: Word of Mouth \| LinkedIn \| Y Combinator \| Google Search \| AI Search (e.g. ChatGPT) \| Twitter | no | How did you hear about us? Optional. | ### What comes back On success the response carries a confirmation and the id of the request that was filed. If anything is wrong, the response names **every** offending field at once — with the reason for each — so ask for all of them, fix them together and retry in a single round trip. Nothing is stored on a rejected call, so retrying does not create duplicates. # Marketing Superintelligence for Revenue Teams | Surface Labs URL: https://surface.thesurface.network/ - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # About Surface Labs | Building Marketing Superintelligence URL: https://surface.thesurface.network/about ## Marketing should get smarter every time it runs. Surface connects buyer signals, campaign execution, and revenue outcomes—then learns from what works. [What is Surface?](https://www.withsurface.com/what-is-surface) ## What we believe 01 ### Revenue is the teacher Every outcome should make the next campaign better. 02 ### Humans and agents share the system Both work from the same context, tools, and results. 03 ### Autonomy is earned Agents begin with clear controls and earn greater trust. ## Why this team BerkeleyY Combinator Surface was started by a team from Berkeley and Y Combinator. We learned to start from first principles, stay close to users, and build the hard technical foundation. We chose marketing because AI makes producing work cheap, while context, judgment, and learning remain scarce. --- # Surface for Claude Code URL: https://surface.thesurface.network/agents ## Claude Code is building software. Have it build your marketing, too. Connect Claude Code to Surface to research buyers, launch campaigns, and act on revenue signals without leaving the conversation. Claude CodeCodexSurface MCP Connect Surface to the systems your revenue team already runs HubSpot Salesforce Slack Claude Codex Google Ads PostHog Zapier ## From prompt to revenue action 01 ### Bring the context Surface gives the agent governed access to the data, research, and rules behind your go-to-market. 02 ### Build the workflow Ask for an outcome in natural language. Surface turns it into coordinated work across your stack. 03 ### Learn from revenue Every action is measured against pipeline, so the next campaign starts smarter than the last. ## Turn every buyer signal into the next best action FAQ The essentials on bringing Surface's marketing agents into the way your team already works. Surface connects to Claude Code through MCP, giving it governed access to your lead data, research, campaign workflows, and revenue systems. --- # Blog | Surface Labs URL: https://surface.thesurface.network/blog [ Content OperationsSeptember 22, 2026 ## Content decay: When search, citations, and revenue stop agreeing Diagnose content decay across search rankings, AI citations, qualified traffic, and revenue before deciding whether to refresh, merge, redirect, or retire. ](https://www.withsurface.com/blog/content-decay-search-citations-revenue) [ Content OperationsSeptember 20, 2026 ## AEO strategy: How search, citations, and conversion fit together Build an AEO strategy that connects search foundations, AI citations, brand recommendations, content execution, and measurable buyer conversion. ](https://www.withsurface.com/blog/aeo-strategy-search-citations-conversion) [ Content OperationsSeptember 18, 2026 ## Generative engine optimization services: A buyer's guide Compare generative engine optimization services, tools, agencies, and operating models by measurement quality, execution depth, and business fit. ](https://www.withsurface.com/blog/generative-engine-optimization-services-buyers-guide) [ GTMSeptember 16, 2026 ## Sales and marketing strategy: One plan, one data layer Create a sales and marketing strategy plan on a shared data layer that preserves buyer activity, campaign history, handoffs, pipeline, and revenue feedback. ](https://www.withsurface.com/blog/sales-marketing-strategy-one-data-layer) [ GTMSeptember 14, 2026 ## GTM metrics: A shared scorecard for marketing and sales Build a GTM metrics scorecard connecting attention, conversion, sales acceptance, pipeline, revenue, and learning without overstating attribution. ](https://www.withsurface.com/blog/gtm-metrics-shared-scorecard) [ GTMSeptember 12, 2026 ## Go-to-market execution: Turn the plan into operable work Turn go-to-market execution into a managed system of decisions, owners, assets, conversion paths, handoffs, instrumentation, and post-launch learning. ](https://www.withsurface.com/blog/go-to-market-execution-operable-work) [ GTMSeptember 10, 2026 ## Sales go-to-market strategy: Connect targeting to the handoff Build a sales go-to-market strategy that carries account targeting, buyer context, qualification, routing, and campaign history into a useful sales handoff. ](https://www.withsurface.com/blog/sales-go-to-market-strategy-targeting-handoff) [ GTMSeptember 8, 2026 ## Go-to-market strategy for B2B teams that need execution Build a go-to-market strategy for B2B teams by connecting market choice, campaigns, conversion, sales handoff, measurement, and revenue feedback. ](https://www.withsurface.com/blog/go-to-market-strategy-b2b-execution) [ Content OperationsSeptember 6, 2026 ## A content marketing audit that finds what still deserves investment Run a content marketing audit that connects search, AI visibility, sales use, pipeline, maintenance cost, and strategic fit to investment decisions. ](https://www.withsurface.com/blog/content-marketing-audit-finds-investment) Loading more articles… --- # AEO strategy: How search, citations, and conversion fit together | Surface Labs URL: https://surface.thesurface.network/blog/aeo-strategy-search-citations-conversion An AI visibility report arrives with good news: the brand was cited more often this month. Search clicks stayed flat, qualified demos fell, and the sales team cannot remember hearing the brand mentioned in a single new conversation. Everyone has a favorable metric and no shared explanation of what it means. That is the early AEO problem in miniature. Answer engine optimization creates new discovery signals, but the business still needs a person to recognize the brand, visit something useful, trust the claim, take a next step, and reach a sales conversation that continues the same story. An AEO strategy needs to govern that whole path. An AEO strategy is a plan for improving how a brand and its information are retrieved, cited, described, and recommended in AI-generated answers, then connecting that visibility to useful buyer behavior. It combines technical SEO, content architecture, answer measurement, source development, conversion design, lead operations, and revenue feedback. Strategy has to govern more than observation and production. Generative engine optimization tools can tell a team where it appeared. A generative engine optimization agency can research and create assets. Neither activity is sufficient unless the company knows which buyer questions deserve attention, what evidence it has a right to provide, how a visitor should continue, and how the result will alter the next publishing decision. Surface treats AEO as an operating loop. [AI Visibility Engineering](https://www.withsurface.com/platform/ai-visibility) organizes prompts by intent and commercial relevance, measures answers across engines, surfaces competitive gaps, and moves selected opportunities into campaign work. [Traffic Intelligence](https://www.withsurface.com/platform/infrastructure/traffic-intelligence) then helps the team examine what happened after discovery, including content engagement, forms, lead quality, AI referrals, and pipeline. Keyword lists are useful, but AI answers often expand one request into several related searches. Google describes this as [query fan-out](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide): the system issues concurrent queries across subtopics and retrieves information needed to build a fuller response. Build the planning unit around a buyer decision rather than a single phrase. A person asking for an AI visibility platform may also need to understand measurement reliability, supported engines, competitor coverage, workflow integrations, implementation time, reporting, and the difference between a monitoring tool and an operating system. Each question should have a clear role in the buyer's understanding. Group prompts by category, problem, use case, comparison, objection, and next step. Give each group an owner and a commercial weight. A high-volume educational question may deserve coverage because it establishes the category, while a narrow implementation question may deserve attention because it appears late in serious evaluations. Surface's guide to [query fan-out and content architecture](https://www.withsurface.com/blog/query-fan-out-in-google-ai-search-how-marketers-should-build-con) shows how those questions can become a connected source library instead of a spray of near-duplicate posts. A ranking, retrieval event, citation, mention, and recommendation are different outcomes. A page can be cited while its company is omitted. A brand can be mentioned because a third-party review explains it well. A recommendation can appear without producing a click, and a click can arrive without producing a useful conversion. Use a scorecard that preserves those distinctions: State What it tells you Useful next question Search visibility A page can be found in traditional search Does the query attract the intended buyer? Retrieval or page appearance An engine found or displayed a source Was the source relevant to the answer? Citation A page was shown as supporting evidence Did the answer use the page's actual claim? Brand mention The answer named the company or product Was the description accurate and specific? Recommendation The brand entered a shortlist or use-case suggestion Which evidence and sources supported the preference? Conversion A buyer took a meaningful next step Did the interaction become qualified pipeline or learning? Microsoft's [AI Performance dashboard](https://blogs.bing.com/webmaster/February-2026/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview) now reports total citations, cited pages, grounding queries, and trends, while explicitly warning that citation activity does not establish page importance or placement. Google's newer [generative AI performance reports](https://developers.google.com/search/blog/2026/06/gen-ai-performance-reports) expose impressions and appearing pages for participating Search Console properties. Those platform signals improve observation, but a company still needs its own prompt set, competitor context, and downstream business measures. An AI SEO strategy cannot rescue a page that crawlers cannot access or a site that contradicts itself. Google says its generative Search features use the same core ranking and quality systems as search, with no special schema or AI text file required. Important content should remain crawlable, indexed, internally linked, text-accessible, useful, and accurate. Run the technical review before commissioning dozens of answer-formatted rewrites. Check robots directives, canonical behavior, rendering, link paths, structured data accuracy, page ownership, and the consistency of category language across product pages, case studies, documentation, and the blog. Our [SEO-friendly CMS guide](https://www.withsurface.com/blog/seo-friendly-cms-what-content-teams-need-before-they-start) explains why the publishing layer must preserve the query, intent, sources, links, and measurement decisions made upstream. Content architecture also gives humans somewhere to go. A citation to a useful article should lead toward a related guide, product explanation, proof point, and conversion path. [A connected content hub](https://www.withsurface.com/blog/what-is-a-content-hub-a-content-strategy-and-seo-guide-for-ai) is more useful than an isolated page because it helps both the retrieval system and the reader understand the relationships around the topic. AEO reporting becomes irresponsible when a team takes a citation, notices an opportunity three weeks later, and calls the citation sourced pipeline. Keep three evidence levels separate: - Observed: the page appeared, the brand was mentioned, a referral arrived, a form was submitted, or sales accepted a lead. - Attributed: a reporting model assigned credit across known interactions using documented rules. - Inferred: the team believes a source or asset influenced the outcome based on timing, behavior, interviews, or a broader pattern. Google Analytics describes attribution models as rules for assigning credit across touchpoints, which means the reported credit depends on the selected model rather than revealing one objective cause. Surface's [guide to attribution and incrementality](https://www.withsurface.com/blog/attribution-is-not-incrementality-how-to-measure-ai-creative) applies the same caution to AI-era campaigns. Design the conversion path before the content is published. Decide which next step suits the intent: another explanatory page, an assessment, a product tour, a demo, a newsletter, or a sales conversation. Then make sure the form, qualification rules, routing, and follow-up retain the context that brought the buyer in. Surface connects those layers without replacing the CRM or CMS already serving as the system of record. A practical cycle has six moves: choose commercially relevant prompt families, establish repeated baselines, diagnose source and content gaps, approve a limited action set, publish and distribute the work, then remeasure visibility and qualified demand. The team should also record the decision to do nothing when the evidence is weak or the query is peripheral. [Content Campaign Agents](https://www.withsurface.com/platform/content-campaigns) can turn qualified-lead, opportunity, search, and ICP signals into an evidence board and campaign plan. Human reviewers keep control over the claims and assets. Once the work is live, revenue feedback can alter the next prompt weighting, content brief, route, or campaign instead of disappearing into a quarterly presentation. An AEO strategy earns its place by improving the company's decisions. A stronger citation chart is one signal inside that work. To build the loop around your actual buyer questions, [book a Surface demo](https://www.withsurface.com/book-a-demo) and bring the prompt family, competitor set, and conversion path your team is trying to understand. --- # Agentic Marketing Analytics Needs an Evidence Layer | Surface Labs URL: https://surface.thesurface.network/blog/agentic-marketing-evidence-layer The old weekly report has a familiar flaw: it shows what the dashboard can see. Paid media presents spend and platform conversions. SEO presents clicks and rankings. Content presents production and traffic. RevOps presents pipeline. The CMO asks why something changed, and every owner opens another tab. An agent can assemble those tabs into one answer. That is a real improvement in interface design. It is also a new way to blur incompatible definitions, time windows, and levels of evidence. The dashboard's next job is to preserve the proof beneath a conversational answer. Call this the evidence layer. It includes source records, stable identifiers, business definitions, timestamps, access rules, and caveats. The agent can retrieve and summarize the layer. Operators still decide whether the evidence supports a claim and whether the claim deserves action. Google's July rollout of [Search Console properties for social and video platforms](https://developers.google.com/search/blog/2026/07/search-console-social-video-platforms) is a useful marker. Eligible teams can see how content from Instagram, TikTok, X, and YouTube performs in Google Search and Discover, including queries, clicks, impressions, insights, and exports. Search performance now includes parts of an owned presence that live on someone else's platform. The change does not dissolve channel boundaries. A YouTube impression in Google Search, a view in YouTube Analytics, and a website session remain different events. It gives the operator another observable path. A sound evidence layer preserves those event types rather than forcing them into one universal visibility score. Google's earlier [generative AI performance reports](https://developers.google.com/search/blog/2026/06/gen-ai-performance-reports) illustrate the same principle. For a subset of properties, Search Console reports impressions in AI Overviews, AI Mode, and generative Discover with page, country, device, and date dimensions. The reports omit query and click detail. The known fact is that Google has exposed a new official measurement surface. The unresolved part is how much diagnostic or commercial meaning a marketer can extract without those missing dimensions. Teams building an [AI visibility dashboard](https://withsurface.com/blog/ai-visibility-dashboard) should treat this as a design cue. Official data deserves a privileged place in the source mix. Its limits should remain visible beside it. New connectors make broad questions easier to ask. [SparkToro](https://sparktoro.com/blog/sparktoros-mcp-server-is-now-live-connect-audience-research-directly-to-your-favorite-ai-tool/) can send audience research into an MCP-compatible assistant. [Semrush](https://www.semrush.com/news/460693-semrush-launches-mcp-connector-in-perplexity-integrating-search-intelligence-within-the-ai-search-engine/) can bring search intelligence into Perplexity. [Ahrefs](https://ahrefs.com/blog/letaido-for-aeo/) describes scheduled workflows that combine Brand Radar, Search Console, and AI referral data. [Adobe](https://news.adobe.com/news/2026/06/introducing-adobe-brand-visibility) is joining visibility data with content optimization and brand context. Each connection carries a different observation model. Audience affinity estimates where a group pays attention. Search Console records selected Google surfaces. An AI visibility platform samples prompts, engines, locations, and dates. CRM data reflects the company's own capture and stage definitions. The agent can compare those sources only after someone defines what comparison means. A source map should name six fields for every dataset: owner, observed event, unit, freshness, known exclusions, and stable join key. Add the access scope and retention policy when the data contains customer or budget information. If no reliable join key exists, say so. A probabilistic or directional comparison can still be useful when the report labels it honestly. This is why [AI visibility measurement remains messy](https://withsurface.com/blog/ai-visibility-measurement-is-messy-how-to-report-geo-without-fak). The mess is not a reason to stop measuring. It is a reason to place coverage and caveats close to the conclusion. \## Citation, mention, and recommendation are different outcomes Ahrefs' July self-promotion experiment offers a compact example of measurement discipline. The company created 34 pages across five domains and observed 9,886 AI answers from February 7 through May 31. Its [published results](https://ahrefs.com/blog/self-promotional-content-ai-seo-experiment/) found that new mentions varied sharply by product maturity, query fit, and engine. The cited page did not always produce a product mention, and a mention did not automatically become a recommendation. The experiment has limits. Ahrefs studied its own content and products, the observation window was finite, and AI answers vary. It still helps operators separate four stages: an engine retrieves a page, cites the page, mentions a brand, and recommends the brand for a buyer's task. A single visibility total hides those transitions. That separation also improves content planning. A team may need clearer category evidence for retrieval, third-party authority for recommendation, or a more precise product page for conversion. A durable [content marketing strategy](https://withsurface.com/blog/content-marketing-guide-2026) connects each asset to the decision it is meant to influence instead of asking every page to win every stage. When an agent answers a weekly marketing question, ask it to produce an evidence packet with eight parts: 1. **Question:** The exact decision under review. 2. **Sources:** Systems, accounts, report names, and record links. 3. **Window:** Observation dates, comparison dates, timezone, and freshness. 4. **Definitions:** Conversion, qualified lead, brand mention, active campaign, or other business terms. 5. **Known observations:** Directly supported findings with units. 6. **Inferences:** Possible explanations, each labeled and tied to evidence. 7. **Missing or conflicting evidence:** Gaps, failed calls, incompatible definitions, and reasonable counterarguments. 8. **Action:** Recommended next check, owner, approval requirement, and expected business signal. The packet can remain short. Its purpose is to make the answer auditable. If a paid campaign lost reported conversions, the agent should show whether traffic, tracking, form completion, routing, and pipeline moved together. If only one source changed, the next action may be an instrumentation check rather than a budget decision. A [connected marketing operations platform](https://withsurface.com/product) can bring research, content, leads, and learning into one working context. Any system claiming a unified view should still let an operator return to the underlying event. Integration is valuable when it reduces handoff loss while preserving the ability to disagree. The agent-generated report needs its own operating metrics. Track evidence completeness, data freshness, failed retrievals, incorrect joins, specialist acceptance, time to reviewed decision, and the percentage of recommendations that lead to a monitored action. Keep business outcomes beside workflow metrics without claiming causality the design cannot prove. A strong evidence layer may make the dashboard less visible in everyday work. It makes the records, definitions, and lineage more important. The agent earns trust by showing its work. The team earns trust by leaving enough structure for someone else to check it. #### Practical steps - Create a source map for every dataset used in a recurring agent report. - Require an eight-part evidence packet for decisions involving spend, pipeline, or published content. - Keep retrieved facts, interpretations, and recommendations in separate fields. - Report coverage and missing dimensions beside every AI visibility trend. - Sample completed reports monthly and trace each material claim back to the source record. --- # Agentic Marketing Is Moving Work Beyond the Dashboard | Surface Labs URL: https://surface.thesurface.network/blog/agentic-marketing-is-moving-work-beyond-the-dashboard ### Week of 7/21: Marketing Trends and Updates Imagine the Monday meeting six months from now. The paid media lead asks, "Which campaigns lost efficient reach last week, and did the decline show up in pipeline?" The marketing agent checks Google Ads, the CRM, and the team's definitions, then returns a short answer with the underlying records. Someone asks the obvious follow-up: "Can you move the budget?" The room gets quieter. That question contains the whole operating problem. Marketers have spent years learning to work inside dashboards. We click through tabs, select a date range, export a CSV, reconcile naming conventions, and paste the conclusion into a deck. The software holds the data. The operator supplies the sequence, judgment, and institutional memory. A cluster of launches in late June and early July suggests that this arrangement is starting to change. Google published a [Google Ads MCP server](https://developers.google.com/google-ads/api/docs/developer-toolkit/mcp-server) that lets an AI agent retrieve and analyze campaign data through natural-language requests. Pinterest introduced Business Assistant and an [MCP server for approved partners](https://business.pinterest.com/blog/pinterest-ai-for-marketers/). [Microsoft Advertising](https://about.ads.microsoft.com/en/blog/post/june-2026/building-a-new-ai-economy-that-creates-value-for-everyone) announced its own MCP server alongside tools for web intelligence and citation reporting. [SparkToro](https://sparktoro.com/blog/sparktoros-mcp-server-is-now-live-connect-audience-research-directly-to-your-favorite-ai-tool/) opened audience research to compatible assistants, while [Semrush](https://www.semrush.com/news/460693-semrush-launches-mcp-connector-in-perplexity-integrating-search-intelligence-within-the-ai-search-engine/) connected search intelligence to Perplexity. [Adobe](https://news.adobe.com/news/2026/06/adobe-accelerates-agentic-ai-adoption) and [Salesforce](https://www.salesforce.com/news/stories/agentic-marketing-teams-announcement/) described broader agent systems that span content, activation, customer data, and measurement. The common feature is easy to miss beneath the product names. These companies are making the dashboard less important as the place where work begins. Their platforms remain the systems that store records, enforce permissions, and perform actions. The operator can increasingly ask a question somewhere else. \## The interface is moving before accountability does MCP stands for Model Context Protocol. In plain English, it gives an AI application a consistent way to discover and use approved data or tools. A marketer can ask an assistant to compare campaigns, retrieve audience research, or inspect a CRM record without building a custom integration for every combination of assistant and platform. The protocol does not make the answer correct. It makes the connection reusable. That distinction matters. A dashboard usually constrains the operator to known fields and actions. A conversational interface can compose a query, combine sources, summarize results, and suggest a next step. The flexibility is useful because real marketing questions rarely respect software boundaries. A lead's path might cross an ad platform, a landing page, a form, a CRM, and a sales conversation. Teams that care about [lead journey tracking](https://withsurface.com/blog/why-lead-ops-is-becoming-its-own-category) already know how much meaning disappears in those handoffs. An agent can reduce the mechanical work of assembling the path. It can also conceal the assumptions. Which conversion event counted? Did the query use account time or UTC? Were test campaigns excluded? Did a missing CRM field mean "no opportunity" or "not synced yet"? A polished paragraph can make an unresolved definition feel settled. This is why the most revealing detail in Google's release is its current access mode: read-only. The server can discover accounts, retrieve metadata, and query campaign performance. It cannot change a bid or budget. That boundary is a product limitation today and a useful operating principle for teams starting their own experiments. Three changes are known. First, several major marketing systems now expose official agent connections or agent-ready workflows. This is more substantial than a chatbot pasted onto a dashboard because the assistant can reach structured data and, in some products, approved actions. [HubSpot's generally available remote MCP server](https://developers.hubspot.com/changelog/remote-hubspot-mcp-server-is-now-generally-available) shows the next stage: it offers expanded read and write access to parts of the CRM while respecting existing permissions, with some objects remaining read-only. Second, useful context is broadening beyond the company website. Google's new [Search Console properties for social and video platforms](https://developers.google.com/search/blog/2026/07/search-console-social-video-platforms) can show eligible teams how Instagram, TikTok, X, and YouTube content appears in Google Search and Discover. An operator can now inspect search performance across owned websites and third-party presences, then combine that evidence with audience and campaign data. Third, marketers have at least one concrete portfolio example. Conversios says it built an MCP-based Performance Max audit workflow across 121 accounts in days without using its core engineering team. The [Microsoft case study](https://about.ads.microsoft.com/en/resources/discover/case-studies/conversios-customer-success-story) is vendor and customer reported, so it should not be treated as independent proof of performance. It still demonstrates a credible use case: inspect many accounts against the same audit logic, surface exceptions, and let a specialist decide what deserves action. The broader conclusion remains inferred. We are likely moving toward a marketing environment where dashboards operate as back offices and evidence stores while agents become the common front door. The launches support that direction. They do not establish adoption, reliability, or business lift across ordinary teams. \## A useful agent produces inspectable decisions Most teams will be tempted to measure the wrong thing first. They will count generated reports, automated tasks, or hours nominally saved. Those numbers are easy to produce and hard to connect to revenue. A faster wrong answer creates more cleanup. The better unit is an inspectable decision. The agent should state the question, identify the sources and time ranges, expose definitions, show the relevant records, separate observation from interpretation, and route the recommendation to someone with authority. This resembles the discipline behind a useful [AI visibility dashboard](https://withsurface.com/blog/ai-visibility-dashboard): coverage, source mix, freshness, and business relevance matter more than a single impressive score. Consider an agent that flags a sudden drop in nonbrand conversions. A weak workflow writes, "Performance declined 18%, increase budget on the winning campaign." A sound workflow shows which conversion definition it used, compares the same weekday range, checks tracking health, distinguishes spend from demand, links the affected campaigns, and asks the channel owner whether a launch or sales-capacity constraint changed the context. The recommendation may still be wrong. At least the operator can inspect why it exists. This is also where connected marketing and RevOps stop being adjacent specialties. The value of an agent depends on the quality of its underlying records. If campaign names drift, lifecycle stages conflict, or content lacks a stable taxonomy, the conversational layer makes those defects easier to query and easier to spread. Teams evaluating [marketing integrations](https://withsurface.com/integrations) should ask whether each connection preserves identity, timestamps, permissions, and source lineage before asking what the assistant can generate. The first production pilot should feel almost disappointingly small. Choose one recurring decision with enough volume to matter and low enough stakes to review manually. Paid media teams might audit pacing and anomalies. Content teams might compare Search Console movement with page changes and current source coverage. RevOps teams might identify leads with broken routing fields while leaving the records untouched. Define the expected answer before connecting a model. Write down the approved data sources, the business definitions, the exclusions, the freshness requirement, and the person who signs off. Run the agent against historical cases with known outcomes. Record unsupported claims, missing evidence, incorrect joins, and recommendations a specialist rejects. Then decide whether the workflow deserves live read access. For teams building a connected operating layer, a [marketing operations platform](https://withsurface.com/product) can bring research, content, lead journeys, and learning into durable shared context. The practical constraint is equally important. That context should remain legible enough that a marketer can find the source and challenge the conclusion. Only after the read-only workflow performs reliably should the team consider a write action. Even then, begin with a draft, queue, or approval request. Let the agent prepare a budget change, CRM update, or content brief. Keep a human between recommendation and execution until the cost of an error, the rollback path, and the monitoring plan are understood. ## What remains debated The market has not settled whether MCP becomes the durable connection standard, one layer among several, or a transitional protocol. Availability also varies. Pinterest's server began with alpha partners. Microsoft's [certification process](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-certification) is still preview documentation. Vendor announcements describe possibility more often than measured use. The right response is neither dismissal nor a platform migration. Operators can treat the protocol as an interface choice while treating access control, evidence, and accountability as durable requirements. If the standard changes, those requirements survive. For the next thirty days, inventory recurring questions that require three or more exports, choose one read-only pilot, assign a channel owner and a data owner, and measure decision quality. Track time to a reviewed answer, evidence completeness, specialist acceptance, exception rate, and any downstream business result. When the agent fails, preserve the trace. That record will teach the team more than another polished demo. The dashboard is not disappearing. It is moving behind the conversation, where it may become more important as a source of truth and less visible as a workplace. The teams that benefit will keep the records sturdy, the permissions narrow, and the humans close enough to ask the second question. --- # Brand Memory Is Becoming an Ad Platform Feature. Your Team Still Needs a Brand Memory of Its Own | Surface Labs URL: https://surface.thesurface.network/blog/ai-brand-memory-ad-platforms A paid media team uploads a year’s worth of creative into an AI advertising system. The archive includes the current product campaign, three abandoned positioning directions, a high-performing ad that attracted terrible leads, a customer quote that was never formally approved, an old pricing promise, several founder-written posts, and a comparison page from before the product changed. The system does what it was built to do. It studies the material, finds patterns, generates variants, and helps the team produce more advertising. The uncomfortable question arrives afterward: What exactly did it learn? Meta introduced “Brand Memory” as part of its Cannes Lions 2026 advertising announcements. According to Meta, the creative system can learn a brand’s identity and tone from previous ads while allowing marketers to refine the brand parameters used to generate new material. Meta also announced broader AI creative tools, a consolidated Creator Marketing Hub, and expanded business-agent capabilities. ([facebook.com](https://www.facebook.com/business/news/cannes-2026-cross-ai-threshold)) The feature name is useful because it gives marketers language for something much larger than a new advertising product. Every company already has a brand memory. It lives across the website, ad accounts, sales decks, product documentation, customer stories, founder interviews, review profiles, social channels, webinar recordings, and hundreds of files sitting inside cloud folders with names like `final_v7_USE_THIS_ONE`. AI systems are beginning to learn from that memory. Before marketers ask how quickly these systems can create new ads, they should ask whether the memory is worth scaling. Brand consistency used to depend largely on people. A creative director reviewed the campaign. A product marketer checked the positioning. Legal inspected the claim. Paid media adapted the approved language. Sales received the updated deck. The process was slow, occasionally irritating, and full of places where the intended message could drift. AI creative tools reduce some of that production friction. They can generate variations, recommend visual directions, translate assets, adapt copy to formats, and help marketers activate larger creative libraries. Google has described a similar direction across its advertising products. Its 2026 advertising outlook says Gemini-powered tools are becoming real-time creative partners, with Asset Studio helping advertisers produce assets more quickly. Google’s Cannes announcement also introduced Gemini-supported YouTube tools for creative campaigns and creator partnerships, including trend insights, creator data, and forthcoming Demand Gen creative recommendations. ([blog.google](https://blog.google/products/ads-commerce/digital-advertising-commerce-2026/)) ([blog.google](https://blog.google/products/ads-commerce/youtube-insights-tools-cannes-lions-2026/)) These systems create a new operating reality. The material a brand has already published can influence what the brand produces next. That makes archive quality a performance variable. A clean archive can help an AI system find useful patterns across approved language, recognizable visuals, successful customer stories, and product claims with evidence. A messy archive can teach the system to revive old positioning, repeat vague promises, and optimize toward campaigns that looked successful in the ad account while creating weak sales conversations. The system sees what performed. It may not understand why the company regrets it. Historical performance data is valuable. It is also dangerous when marketers treat it as a complete expression of brand intent. An ad can perform well for reasons that have little to do with long-term brand health. It may use an aggressive promise. It may attract a broader audience than sales can support. It may generate cheap form submissions from people who misunderstand the product. It may benefit from a news cycle, promotional period, or creative pattern that cannot be repeated forever. AI systems trained or guided by past campaign material can reproduce these patterns faster. Imagine a B2B software company that ran an ad promising to “automate your entire lead funnel.” The claim generated clicks because it sounded expansive. Sales then spent every discovery call explaining that the product handled lead capture, qualification, routing, and follow-up rather than every possible revenue operation. A platform may identify that ad as a winner. Sales may identify it as the beginning of a month-long headache. That gap is why marketers need to connect AI creative performance with [lead quality rather than lead volume](https://withsurface.com/blog/how-to-actually-measure-lead-quality-not-just-lead-volume). Click-through rate, cost per lead, and platform-attributed conversions cannot reveal whether a message created the right expectation, reached a viable account, or improved the eventual sales conversation. A brand memory system needs business feedback, not only media feedback. A traditional brand guide usually covers visual identity, logo treatment, tone, typography, colors, and a handful of writing principles. Those elements still matter. They are no longer enough. An AI-ready brand memory should contain the information required to make claims safely and express the product accurately. It should help a human writer, creative team, sales rep, agency partner, and AI system understand the same basic reality. A useful source of truth includes: ### Current positioning Describe the category, primary audience, main problem, product role, and central distinction. Keep this clear enough to use in a working campaign. A positioning framework that requires a two-hour workshop to interpret will not survive contact with a deadline. ### Approved product claims List the claims the company is comfortable making publicly. Separate broad positioning statements from factual product capabilities, measurable performance claims, security statements, and customer outcome claims. ### Supporting evidence Attach proof to important claims. Evidence might include customer examples, product data, screenshots, implementation documentation, benchmark ranges, case studies, survey results, or independently verifiable sources. ### Required caveats Some claims are true only for certain plans, integrations, customer types, time periods, or implementation conditions. Those limits should be visible before an AI system creates fifty polished variations of an incomplete promise. ### Language to avoid Document phrases that are inaccurate, vague, strategically unhelpful, overused, or likely to produce the wrong expectation. “Fully autonomous,” “effortless,” “instant,” and “transform your business” may sound useful in isolation while causing serious problems for a specific product. ### Audience distinctions A message for a founder, demand-generation leader, RevOps operator, content lead, and enterprise procurement team cannot always use the same evidence or level of technical detail. Store those differences explicitly. A source of truth like this also strengthens [AI-assisted content strategy without losing brand voice](https://withsurface.com/blog/ai-content-strategy-brand-voice). Brand voice does not come from asking a model to sound intelligent, warm, practical, or conversational. Nearly every B2B company uses those words. Voice becomes recognizable when the system can see what the company notices, believes, proves, questions, and refuses to exaggerate. A claim registry is one of the simplest ways to make brand memory operational. The registry lists important public claims and gives each one a status. A basic version might include these columns: Claim Status Evidence Approved use Owner Last reviewed “Routes high-intent leads in real time” Approved Product documentation and customer workflow Product, paid, sales Product marketing June 2026 “Increases conversion by 30%” Limited Selected customer results Case study only, with context Customer marketing May 2026 “Fully autonomous lead management” Retire Overstates current functionality Do not use Product June 2026 “Works with your existing CRM” Needs qualification Supported integrations vary Use with integration list Product marketing June 2026 The statuses can remain simple: - **Approved:** Safe for standard use. - **Limited:** Accurate in specific contexts. - **Needs proof:** Strategically useful, but insufficiently supported. - **Needs review:** Product, legal, security, or customer approval required. - **Deprecated:** Previously used but no longer accurate. - **Retired:** Should not appear in new material. This gives teams something more useful than a general request to “keep everything on brand.” It tells the system and its operators which ideas can move quickly and which ones require judgment. The registry also helps content teams create stronger briefs. A [content brief should function as a strategic decision record](https://withsurface.com/blog/what-is-a-content-brief), including the claim, audience, supporting evidence, internal link path, and constraints that prevent predictable overreach. Most companies do not need to delete their creative history. They need to label it. An archive audit should classify assets by: - Product era - Audience - Funnel stage - Use case - Message family - Primary claim - Evidence level - Approval status - Performance - Lead quality - Sales feedback - Expiration or review date This produces a more honest view of what the archive contains. A campaign might have excellent click-through rates and poor sales acceptance. Another might have modest reach but consistently produce qualified opportunities. An older founder video might explain the company’s point of view better than the current homepage. A customer story might include the strongest available proof while using a product name that no longer exists. The archive should preserve these materials while making their context visible. This is especially important as platforms incorporate more agentic and generative capabilities. Google has said its advertising agents can learn from inputs including landing pages, creative assets, performance data, and broader datasets. ([blog.google](https://blog.google/products/ads-commerce/ai-agents-marketing-advisor/)) A landing page therefore becomes more than a conversion destination. It can become instructional material for a system helping to create or optimize campaigns. Teams should make sure the page is teaching the right lesson. Requiring the same approval process for every AI-generated asset will make the workflow unusable. Letting everything publish automatically will create avoidable risk. The better model uses review tiers. ### Low-risk variations These can move quickly when they use approved language and do not introduce new claims. Examples include: - Headline length variations - Format adaptations - Approved copy shortened for placements - Image crops - Existing creative resized for channels - Minor tonal adjustments within documented limits ### Medium-risk variations These should receive an editorial or product marketing review. Examples include: - New combinations of approved claims - Segment-specific positioning - Revised use-case language - New CTAs - AI-created visual concepts - Translations or localization - Creator adaptations of brand messaging ### High-risk variations These require specialist approval before activation. Examples include: - Performance or ROI claims - Security and compliance statements - Competitor comparisons - Customer names or quotations - Pricing and packaging language - Product roadmap implications - Claims involving regulated industries - Guarantees or absolute statements This system protects speed where speed is useful and adds scrutiny where an error could damage trust. There is an obvious danger on the other side of this conversation. A heavily governed brand memory can produce sterile work. Every ad uses the same approved phrase. Every page follows the same structure. Every campaign sounds safe. The company becomes consistent enough to disappear. Brand memory should preserve identity while allowing interpretation. A jazz musician remembers the structure of a song in order to play with it. A good creative team should understand the brand deeply enough to move around inside it. The purpose of the system is to provide stable claims, evidence, audience knowledge, and boundaries. It should not prescribe every sentence before the writer arrives. This distinction matters because audiences are already skeptical of generic AI content. Gartner reported in June 2026 that 49% of surveyed U.S. consumers believe GenAI has made available content quality worse. Among Gen Z and millennial respondents, the figure was 57%. The same research described a more skeptical media environment in which brands need to be recognizable, credible, and intentional about where they appear. ([gartner.com](https://www.gartner.com/en/newsroom/press-releases/2026-06-09-gartner-survey-finds-49-of-u-s-consumers-say-genai-has-made-content-quality-worse)) A rigid brand template will not resolve that skepticism. Recognizable judgment might. The company still needs people who can find the interesting sentence, admit a limitation, choose the useful example, notice what the customer is really asking, and decide when the familiar brand language is too weak for the moment. Once AI creative production scales, marketers need ways to detect whether the brand is drifting. Message drift occurs when different channels gradually describe the company in incompatible ways. One campaign sells speed. Another sells intelligence. The homepage sells control. A creator describes simplicity. Sales leads with customization. The AI-generated comparison ad presents the product as the cheapest option. Each message may be defensible. Together, they may leave no stable idea behind. A useful monthly review should compare: - The claims appearing most often - The audiences associated with those claims - The proof attached to each claim - The message families producing qualified leads - The message families creating sales objections - Changes in branded search language - AI assistant descriptions of the company - Review-site and community descriptions - Landing-page promise versus sales-call reality This is where [AI visibility reporting without fake precision](https://withsurface.com/blog/ai-visibility-reporting-without-fake-precision) becomes relevant. AI systems can reflect the public memory a brand has created. If different assistants repeatedly describe the product incorrectly, the problem may involve retrieval or citation. It may also reveal that the company has published too many conflicting explanations. Message drift is both a creative problem and a source-management problem. An ad cannot carry the entire brand. The generated creative leads somewhere. That destination needs to continue the same promise, add evidence, answer the buyer’s next question, and create an appropriate next step. A company can have beautiful AI-generated advertising and still lose demand through a weak conversion system. The landing page may repeat the headline without explaining the workflow. The form may ask too much. The demo request may route to the wrong person. The follow-up may sound generic. The sales rep may receive no context about the message that brought the buyer in. When teams use [inbound marketing automation](https://withsurface.com/blog/inbound-marketing-automation), the creative message should travel with the lead. Capture the campaign, message family, use case, and content path. Give sales enough context to continue the conversation rather than restarting it. This also creates the feedback required to improve brand memory. Paid media can report which ads received credit. RevOps can show which messages produced qualified conversations. Sales can explain where expectations broke. Product marketing can revise the claim registry. Content can strengthen the proof. The next generation of creative learns from a cleaner system. That is what a functioning memory looks like. Teams can begin with a focused two-week audit. ### Inventory the public memory Collect the homepage, product pages, pricing pages, top landing pages, recent paid campaigns, sales decks, customer stories, help documentation, review profiles, and high-visibility executive content. List every meaningful product, performance, customer, competitive, security, and implementation claim. ### Classify each claim Mark it as approved, limited, unsupported, stale, vague, strategically important, deprecated, or risky. ### Attach evidence Connect every high-priority claim to current support. Note where the proof is missing or no longer usable. ### Review performance with quality data Compare campaign performance with lead quality, sales acceptance, opportunity creation, and customer fit. ### Label the archive Tag assets by product era, audience, message family, proof level, and current approval status. ### Define AI review rules Decide which variations can publish quickly and which claims trigger human review. ### Refresh the source-of-truth pages Update the pages most likely to influence buyers, search engines, AI systems, and advertising tools. The goal is not to produce another brand document that sits untouched. The goal is to build an operating memory that improves the next campaign. ## AI can remix the memory. Marketers still have to maintain it. AI advertising systems will keep getting better at generating, adapting, selecting, and optimizing creative. That should help marketing teams. It should reduce repetitive work, make testing more accessible, speed up localization, and give smaller teams a larger field of creative possibilities. The value depends on what the system learns. A platform cannot know that the company regrets its best-performing headline. It cannot know that an old feature claim creates the wrong expectation. It cannot know that a customer quote needs context, that a cheap lead is rarely qualified, or that the founder’s unscripted explanation is the clearest articulation of the company’s value. Those distinctions live inside the organization. Build the claim registry. Clean the archive. Connect evidence to the message. Give review effort to the riskiest claims. Measure what happens after the click. Preserve enough room for writers, creators, operators, and customers to keep the brand alive. The platform can remember what you gave it. Your team still has to decide what deserves to be remembered. --- # AI Chatbots vs. AI Forms vs. AI SDRs: What's the Difference? | Surface Labs URL: https://surface.thesurface.network/blog/ai-chatbots-vs-ai-forms-vs-ai-sdrs-what-s-the-difference Three categories of AI tools now compete for the same job: turning inbound website visitors into qualified sales conversations. AI chatbots. AI-powered forms. AI SDRs. They all claim to automate lead qualification and conversion. They all use similar underlying technology. And they all show up on the same vendor shortlists. But they're fundamentally different tools with different strengths, and picking the wrong one for your situation means spending money on a solution that doesn't solve your actual bottleneck. **AI Chatbots** are conversational agents deployed on your website. They engage visitors in real-time dialogue — answering questions, collecting information through conversation, and attempting to qualify and route leads. Examples: Drift, Intercom Fin, custom bots built on Claude or GPT. The visitor experience is chatting with an AI assistant. **AI Forms** are intelligent form experiences that use conditional logic, real-time enrichment, and dynamic personalization to qualify leads at the point of capture. They adapt questions based on answers, score leads in real time, and connect to routing and scheduling. Examples: Surface Labs, Typeform with logic (basic), custom-built qualification flows. The visitor experience is filling out a smart questionnaire. **AI SDRs** are autonomous agents that handle outbound and inbound follow-up — sending personalized emails, making calls, booking meetings, and qualifying leads through multi-step outreach sequences. Examples: 11x, Artisan, AiSDR. The visitor experience is receiving what appears to be a human email or call from a sales rep. Dimension AI Chatbots AI Forms AI SDRs **When they engage** While the visitor is on site, in real time While the visitor is filling out a form, in real time After the visitor has submitted info — minutes to hours later **Data consistency** Low. Conversations are unstructured. Data extraction depends on what the visitor says. High. Form fields ensure specific data is captured in a consistent format. Medium. SDR collects info through follow-up, but format depends on the conversation. **Qualification reliability** Medium. Bot can ask qualifying questions but can't guarantee it covers every criterion in every conversation. High. Conditional logic ensures every qualifying question is asked and evaluated systematically. Medium. SDR qualifies through outreach, but it happens after the moment of highest intent. **Speed-to-engagement** Instant. Bot is always available on the page. Instant. Form is always available. But engagement only starts when the visitor clicks. Delayed. SDR engages after submission — typically minutes to hours. **Speed-to-meeting** Varies. Bot conversation takes 3–5 min, then hands off to scheduling (sometimes with friction). Fast. Form → qualify → route → schedule can happen in under 60 seconds in one continuous flow. Slow. Multi-step email/call sequences can take days to reach a booked meeting. **Best for** High-traffic sites with many casual visitors who won't fill out a form. Visitor engagement. High-intent conversion points — demo requests, pricing pages, contact forms. Meeting conversion. Outbound follow-up on leads who didn't convert on-site, or re-engaging cold leads. **Maintenance** High. Prompts need tuning. Conversations are unpredictable. Requires monitoring for quality. Low-medium. Form logic is deterministic. Changes are explicit and testable. Medium. Sequences need optimization. Personalization templates need updating. **Measurability** Hard. Analyzing conversation quality requires reading transcripts. Easy. Form data is structured. Conversion metrics are straightforward. Medium. Sequence performance is measurable, but attribution to the original capture is often unclear. **Use AI Chatbots when** your website gets significant traffic from visitors who aren't ready to fill out a form. The chatbot's job is engagement — surfacing interested visitors from a large pool of browsers. If you get 50,000 monthly visitors and only 200 fill out forms, a chatbot might engage another 500–1,000 who would otherwise bounce. **Use AI Forms when** your primary goal is converting high-intent visitors into booked meetings. Demo request pages, pricing pages, contact pages — anywhere a visitor has already signaled intent by clicking a CTA. The form's job is conversion — qualifying, routing, and scheduling in one flow with no gaps. **Use AI SDRs when** you have a large volume of leads who submitted information but didn't book a meeting, and you need automated follow-up at scale. The AI SDR's job is re-engagement — working leads that fell through the cracks of the real-time flow. Most teams pick one of these three and expect it to solve the entire problem. A chatbot that engages visitors but can't reliably qualify and route them to the right rep. An AI SDR that follows up on leads but only reaches them hours after the moment of intent. A form that captures data but doesn't have the intelligence to adapt to each visitor. The highest-performing teams layer them. The chatbot handles broad engagement. The smart form handles high-intent conversion. The AI SDR handles follow-up on leads that didn't convert in real time. Each tool does the job it's built for, and the lead ops infrastructure connects them. Surface is the AI form layer — smart capture, real-time qualification, attribute-based routing, instant response, and embedded scheduling. It handles the highest-leverage moment in the funnel: the transition from "interested visitor" to "booked meeting." If you're evaluating AI tools for lead conversion, start with the bottleneck. For most B2B teams, it's not engagement (chatbot territory) or follow-up (AI SDR territory). It's the 60 seconds after a high-intent visitor raises their hand. That's Surface. --- # AI Citations vs. SEO Rankings: Why Search Visibility Needs a New Measurement Model | Surface Labs URL: https://surface.thesurface.network/blog/ai-citations-vs-seo-rankings A founder sees the company rank first for a high-intent term and assumes the brand owns the category. Then a buyer asks an AI system for recommendations and receives three competitors, two review sites, a YouTube video, and no mention of the company. The founder is not imagining the contradiction. Rankings and AI citations now describe related but different visibility systems. Traditional SEO taught marketers to track position, impression, click, and conversion. That model still matters because people still use search engines, and AI systems often retrieve from search indexes. [Google's own guidance](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) says AI Overviews and AI Mode remain rooted in Search ranking and quality systems. The current research slate adds a second truth. AI systems can cite and mention sources that do not match classic blue-link rankings. Ahrefs reported in March 2026 that only 38% of AI Overview citations came from pages ranking in Google's top 10 in its dataset. The same research found meaningful citation activity from URLs outside the top 100, including YouTube. Ahrefs also found that AI Mode and AI Overviews reached similar conclusions while sharing only 13.7% citation overlap. That means marketers need a measurement model that treats ranking as one input rather than the entire answer. #### Ranking Ranking tells marketers where a page appears in classic search results. This metric still matters for traffic, credibility, and retrieval eligibility. A page that ranks well may have a better chance of entering the candidate set, but rankings do not guarantee citation. #### Citation Citation tells marketers whether an AI system lists a page as a source. Citation matters because users often treat linked sources as evidence, even when they do not click. Bing's AI Performance report now gives site owners Total Citations, Average Cited Pages, grounding queries, page-level citation activity, and trends across supported Microsoft surfaces. #### Mention Mention tells marketers whether the answer names the brand, product, founder, or category. A system may mention a brand without citing the brand's own site. That can still influence perception, especially in comparison and recommendation prompts. #### Absorption Absorption asks whether the AI answer actually used the page's information. A page can be cited without shaping the core answer. A [page can also shape the answer](https://withsurface.com/blog/may-marketing-updates) indirectly through facts, definitions, comparisons, or examples. Most teams cannot measure absorption perfectly yet, but they can inspect cited passages and recurring answer language to estimate whether their evidence is being used. AI systems often use query fan-out. Instead of answering one prompt with one search, a model may generate related subqueries, retrieve several source sets, and synthesize an answer from the pieces. A user asks "best customer support AI for multilingual teams," and the system may fan out into multilingual support, voice AI latency, support KPIs, AI hallucination mitigation, language switching, pricing, integrations, and reviews. That process can elevate sources that do not rank for the exact query. A technical article may support one subclaim. A video may support a product demonstration. A forum thread may support experiential proof. A review platform may support customer sentiment. A company's category page may support product positioning. First, map prompt families instead of one keyword at a time. Group prompts by buyer intent: education, comparison, risk, implementation, pricing, alternatives, and vendor recommendation. Then test the prompt families across relevant AI systems and note citations, mentions, answer framing, and competitor presence. Second, build content clusters around fan-out coverage. A single page cannot responsibly answer every question. Teams should create a clear pillar page and supporting pages that cover use cases, objections, comparisons, proof, implementation, and alternatives. Internal links should guide humans and crawlers through the cluster. Third, strengthen off-site evidence. Ahrefs has shown YouTube can matter in [AI Overview citations](https://withsurface.com/blog/generative-engine-optimization-services), and SparkToro's research reminds marketers that search and influence happen across many web surfaces. Teams should review reviews, videos, podcasts, partner pages, analyst mentions, community conversations, and earned media. AI systems often pull from the wider evidence field. Fourth, add current, extractable proof. Recent citation-factor research in controlled RAG settings suggests topical relevance and list position matter strongly, while recent timestamps and explicit price information can help. Operators should avoid overgeneralizing the study, but they should make useful facts easy to extract. A useful executive summary should separate three ideas. "We rank" means the brand is visible in classic search. "We are cited" means one or more AI systems are using pages as sources. "We are recommended" means the brand appears in answer text when buyers ask for options. Those outcomes can overlap, but they should not be collapsed. A retrieval-era report should also include caveats: platform, date, geography, language, account state, prompt set, sample size, and confidence. Academic uncertainty research shows that AI visibility metrics can vary across repeated runs, so single screenshots deserve careful labeling. ### Can a page rank first and still fail to get cited by AI? Yes. Current research shows AI systems can cite pages that do not rank in the top 10 for the direct query, and they can ignore pages that rank well. ### Should teams stop tracking rankings? No. Rankings remain useful for classic search, retrieval eligibility, and business reporting. Teams should add citation and mention tracking rather than replace one metric with another. Schema recommendation: Article schema with Dataset or citation links if the final piece references proprietary testing. Add BreadcrumbList and Organization schema where sitewide policy supports it. --- # How to Use AI in Your Content Strategy Without Losing Brand Voice | Surface Labs URL: https://surface.thesurface.network/blog/ai-content-strategy-brand-voice ## Summarizing AI in Content Strategy AI in content strategy works best when it accelerates the parts of content work that are repetitive, research-heavy, or structurally tedious. It can help teams summarize source material, compare competitors, identify content gaps, generate outline options, repurpose older assets, and speed up revision cycles. It works worst when teams ask it to replace interpretation. Brand voice does not disappear because a company uses AI. Brand voice disappears when no one adds judgment back into the process. If the workflow goes directly from research to outline to draft, the result often sounds clean, fluent, and strangely unowned. It may answer the query. It may include the keyword. It may even rank. But it will not necessarily feel like the company has spent any meaningful time with the problem. A better workflow is: **Research → Human interpretation layer → Outline → Human POV layer → Draft → Editor pass** That sequence matters because it gives humans two chances to shape the work before the final edit. The first human layer decides what the research means. The second human layer decides what the company believes. ## AI in Content Strategy Should Accelerate Judgment, Not Replace It The wrong question is whether AI should be used in content strategy. It already is. Content teams use AI tools to research, draft, summarize, cluster, rewrite, audit, and report. The more useful question is where AI belongs in the process. AI belongs anywhere the team needs leverage without surrendering responsibility. For example, AI can review a cluster of competitor pages and identify common sections. A human still needs to decide whether those sections are useful or merely common. AI can suggest questions buyers might ask. A human still needs to decide which questions reflect real buyer anxiety. AI can summarize a founder interview. A human still needs to hear the sentence that carries the real point of view. Thinking about [generative AI search optimization](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) gives marketers a helpful reminder. AI visibility does not reward teams for creating machine-only content. It rewards content that is useful, crawlable, clear, current, and trustworthy enough for humans and systems to reuse. The same standard should govern AI-assisted production. Use the tool to reduce drag. Do not use it to remove responsibility. ## Why Brand Voice Gets Lost in AI Content Brand voice gets lost when teams treat voice as decoration. A brand voice doc might say the company should sound clear, smart, useful, technical, direct, practical, and human. Those are all fine words. They are also the same words almost every B2B company uses to describe itself. If AI is given only those descriptors, the output will usually sound like every other company that wants to be clear, smart, useful, technical, direct, practical, and human. Brand voice is not only tone. Brand voice is judgment made visible. A company’s voice shows up in what it chooses to explain, what it chooses to skip, what it refuses to overclaim, what it treats as obvious, what it treats as difficult, and where it draws lines. In technical product content, voice also appears in the level of specificity. A company that understands its buyer can talk about architecture, implementation, risk, constraints, integrations, migration paths, and tradeoffs without flattening the whole thing into “benefits.” AI tends to average the available language around a topic. That can be useful for research. It is dangerous for voice. If the draft sounds like the statistical middle of the market, the company has not created thought leadership. It has created a polished summary of other people’s pages. ## The Better Workflow for AI in Content Strategy A strong AI-assisted content workflow should not begin with “write me a blog post.” It should move through six stages: 1. Research 2. Human interpretation layer 3. Outline 4. Human POV layer 5. Draft 6. Editor pass Each stage has a different job. AI can contribute to several of them, but it should not control all of them. Use AI to gather, summarize, and organize inputs. This is one of the safest and most useful roles for AI because the task is not to invent authority. The task is to reduce research drag. Useful inputs include: - Keyword data - Search result summaries - Competitor pages - Customer calls - Sales notes - Product documentation - Support tickets - Analyst reports - Internal positioning notes - Existing content performance - AI visibility or citation tests - Product launch notes - Demo objections - Webinar transcripts - Founder interviews At this stage, the goal is not to produce a draft. The goal is to understand the field of possible answers. For B2B SaaS and technical product teams, AI can be especially useful at finding repeated patterns across messy source material. It can summarize what prospects ask on sales calls, pull common objections from CRM notes, identify the top structures on ranking pages, or group related questions into possible content clusters. Good research prompts might include: - What buyer questions appear repeatedly across these sales notes? - What themes show up across these competitor pages? - What sections do the top-ranking pages share? - Which claims are repeated but weakly supported? - What related questions would a technical buyer ask before trusting this product? - What internal content could support this page? - Which parts of this transcript sound like a real point of view? Research is where AI is allowed to be broad. Strategy begins when a person decides what the research means. The human interpretation layer comes immediately after research. This is the most important step in the workflow, and it is the one many teams skip. They move from research directly to outline because the tool makes that easy. The result is an outline that may be structurally competent but strategically average. The human interpretation layer asks: - Which parts of the research are actually relevant? - Which search results are ranking but strategically weak? - Which buyer questions are missing from the obvious keyword set? - Which claims does the company have the authority to make? - Which topics should be avoided because they distort the business? - What is the real tension the page should resolve? - What should the reader understand after this that they did not understand before? - What should the page make easier for sales, support, product marketing, or demand generation? This layer does not need to be long. It can be a paragraph. It can be a short set of bullets. It just has to make the strategic read explicit before the outline begins. Example: > Most pages about AI in content strategy either overpromise automation or warn vaguely about brand voice. Our angle should be more operational. AI is useful, but the workflow has to include two human judgment points before the editor pass. The reader is a content manager or GTM lead trying to increase production without turning the site into average AI output. That paragraph will improve the entire draft because it gives the page a spine. For B2B technical products, this is also where the team should translate market language into buyer language. The market may describe a product as “automation,” but the buyer may care more about risk, control, implementation, data quality, review cycles, or handoff reliability. A keyword tool can show the phrase. A sales call may reveal the fear inside the phrase. AI can identify the phrase. A human has to hear the fear. Once the human interpretation layer is written, use AI to help create outline options. Do not ask for a generic outline. Feed the tool the human interpretation, intended audience, primary keyword, internal link targets, and desired point of view. A stronger outline prompt might look like this: ``` Create three outline options for a B2B thought leadership blog targeting the keyword "AI in content strategy." Audience: content managers and GTM leads at B2B SaaS and technical product companies. Human interpretation: Most articles either overpromise AI automation or warn vaguely about brand voice. Our angle is operational. AI can support content strategy, but the workflow should be research → human interpretation layer → outline → human POV layer → draft → editor pass. Point of view: Brand voice is not only tone. Brand voice is judgment made visible. Required internal links: - generative AI search optimization - content marketing strategy in the AI era - AI citations vs. SEO rankings - content marketing guide for 2026 Avoid: - generic "AI is changing everything" language - unsupported claims - vague warnings about authenticity - overemphasis on prompts ``` After AI generates the outline, revise it manually. The outline should make the argument move. The first sections should answer the query. The middle should explain the operating model. The later sections should show the reader what to do. A good outline is not just a list of H2s. It is the skeleton of the page’s reasoning. The human POV layer comes after the outline and before the draft. This is where the team names the claims, examples, warnings, standards, and lines of argument that the draft should carry. It prevents the article from becoming a competent summary of the topic. A human POV layer for this article might include: - AI should accelerate judgment, not replace it. - Brand voice is not only tone. It is judgment made visible. - The human interpretation layer should happen before the outline. - The human POV layer should happen before the draft. - AI is safer when transforming known material than when inventing authority. - B2B teams should stop asking AI to “sound like us” and start giving AI better strategic inputs. - The editor pass should protect specificity, accuracy, and point of view. - A content system can use AI heavily and still feel human if humans own the meaning. These lines do not need to appear verbatim in the final draft. They give the article conviction. This is also where the team should add examples. For a technical product company, those examples might come from: - A product launch - A migration guide - A complex integration - A customer objection - A compliance concern - A sales handoff - A founder POV - A technical architecture choice AI can help expand these examples, but a human should choose them. After research, interpretation, outline, and POV, AI can help produce a draft. At this point, the tool has the right inputs. It is no longer being asked to invent the strategy. It is being asked to express a strategy that humans have already shaped. The draft should still be treated as material, not as finished content. A strong AI-assisted draft can save time, but it will usually need revision for specificity, rhythm, evidence, internal links, examples, and judgment. Common draft problems to watch for include: - Repeated sentence structure - Overly neat transitions - Vague statements about transformation - Generic claims about efficiency - Unearned confidence - Examples that sound plausible but not real - Sections that repeat the same idea in different words - “In today’s digital landscape” openings - Lists that feel complete but not useful - CTAs that are too heavy for the reader’s stage The draft is where AI can create momentum. The editor is where the company earns trust. The editor pass protects the brand. The editor should check whether the piece sounds like a person with market experience, not like a synthesis of the first five ranking pages. The editor should also check whether the page serves the reader, the business, and the broader content system. A practical editor pass should ask: - Does the article answer the primary query clearly? - Does it add a point of view? - Does it explain what AI should and should not do? - Does it include the required workflow? - Does it use internal links as helpful next steps? - Does it avoid unsupported claims? - Does it sound specific to B2B SaaS and technical product teams? - Does it connect content strategy to GTM usefulness? - Could sales or product marketing use this piece? - Could an AI system understand what the page is about? - Does the page sound like the company, or like the average of the category? The editor should remove generic language, sharpen weak claims, verify any factual statements, improve transitions, add examples, and make the CTA proportionate to the reader’s intent. For Surface-style content operations, this is the stage where the content stops being merely publishable and becomes strategically useful. Most brand voice documentation is too abstract to help AI workflows. A better brand voice system should include usable rules, not only adjectives. A useful AI-era brand voice document should include: - Core beliefs - Claims the company is willing to defend - Claims the company avoids - Preferred sentence rhythm - Approved internal language - Banned phrases - Example paragraphs - Product explanation standards - Source and evidence requirements - CTA rules - Internal linking rules - How to handle uncertainty - How to discuss competitors - How to talk about AI without sounding generic - How to turn expert notes into market-facing language For B2B SaaS and technical products, the document should also include technical depth guidance. Some pages should be accessible to non-technical buyers. Others should respect a more technical reader. Voice changes when the reader’s fluency changes, but the company’s judgment should stay consistent. A good brand voice system does not force every page into the same tone. It gives every page the same standard of thoughtfulness. AI can be extremely useful when the team gives it bounded jobs. Good uses include: - Summarizing long source materials - Extracting themes from transcripts - Turning product notes into plain-language explanations - Identifying stale claims in old content - Suggesting internal links - Creating multiple outline options - Rewriting dense paragraphs for clarity - Generating distribution variations from a finished piece - Building refresh checklists - Comparing the draft against the brief - Creating social, newsletter, and sales enablement variants from approved content Riskier uses include: - Inventing a point of view - Writing from a founder’s perspective without source material - Creating thought leadership from generic prompts - Producing technical explanations without expert review - Generating statistics without source verification - Writing comparison pages without product knowledge - Creating pages only because a keyword exists - Rewriting every page into the same tone The difference is simple. AI is safer when it is transforming known material. It is riskier when it is asked to invent authority. ## AI in Content Strategy and Internal Linking AI-assisted content should still respect site architecture. A strong article should not exist as an isolated asset. It should connect to related pages that help the reader keep moving. Internal links are not only SEO mechanics. They are the way a content team shows the reader how ideas relate. A post about AI in content strategy might naturally point readers toward [content marketing strategy in the AI era](https://withsurface.com/blog/content-marketing-strategy-the-quality-vs-volume-trap-in-ai-era), because the core risk is not AI usage itself but the temptation to turn production speed into a strategy. It might also connect to [AI citations vs. SEO rankings](https://withsurface.com/blog/ai-citations-vs-seo-rankings), because AI-assisted content needs to be understood in a search environment where ranking and citation are no longer the same thing. A broader [content marketing guide for 2026](https://withsurface.com/blog/content-marketing-guide-2026) can give the reader a larger operating model for trust, distribution, and measurement. That kind of linking helps humans. It also helps search systems and AI systems understand the content’s relationship to the broader topic. AI can suggest internal links. A person should decide which links create the best path. ## A Simple AI Content Strategy Workflow for B2B Teams Here is the workflow in practical terms. ### Research Use AI to summarize search results, competitor pages, internal documents, sales notes, transcripts, and existing content. Output: - Research summary - Buyer questions - Competitor patterns - Content gaps - Possible internal links ### Human Interpretation Layer Have a strategist, editor, or GTM lead write the strategic read. Output: - Reader definition - Intent - Market tension - Business purpose - Angle - What the page should not do ### Outline Use AI to generate outline options from the interpretation layer. Output: - Two to three outline options - Recommended structure - Questions to answer - Potential internal links ### Human POV Layer Add the claims, examples, and perspective that should shape the page. Output: - Core argument - Required examples - Claims to defend - Claims to avoid - Voice notes - Product or category nuance ### Draft Use AI to create a draft from the approved outline and POV layer. Output: - First draft - Metadata draft - Optional FAQ draft - Distribution notes ### Editor Pass Have a human editor revise for quality, accuracy, voice, links, structure, evidence, and business usefulness. Output: - Publishable article - Final metadata - Internal link QA - CTA QA - Refresh notes Audit your current AI content workflow. Find the first point where a human makes a strategic decision. If that point comes after the draft, move it earlier. A better workflow should look like this: - Use AI to gather and summarize research. - Have a human write the interpretation layer. - Use AI to propose outlines. - Have a human add the POV layer. - Use AI to assist with drafting. - Have an editor revise for voice, accuracy, structure, and usefulness. Then document the process. The goal is not to make every piece sound identical. The goal is to make every piece pass the same quality standard while preserving enough specificity to feel alive. Surface’s content operations offer fits into this kind of system because the hard part is no longer simply producing content. The hard part is governing the content workflow so strategy, AI assistance, human judgment, publishing, internal links, and measurement all support the same business direction. ## Final Thought on AI in Content Strategy AI can make content production faster. It can make research less painful. It can help small teams operate with more leverage. Used well, it gives marketers more time for judgment. Used poorly, it gives marketers a polished way to remove the very thing buyers trust. The right goal is not AI-free content. The right goal is content where AI handles tool work and humans handle meaning. Research can be accelerated. Drafts can be assisted. Brand voice still has to come from people who understand the market well enough to say something specific. --- # AI Made Marketing Cheap. It Did Not Make Brands Interesting. | Surface Labs URL: https://surface.thesurface.network/blog/ai-made-marketing-cheap-not-brands-interesting Let us know if this sounds familiar: your Monday planning meeting now has more material than it could have produced in an entire month three years ago. There are forty campaign concepts, twelve landing-page variations, a competitive teardown, several hundred keyword ideas, six versions of the product narrative, synthetic customer personas, social posts for four platforms, and a polished video storyboard. Most of it arrived overnight. None of it is obviously wrong. The problem begins when someone asks which idea your company should actually use. Several concepts are plausible. A few sound professional. Nearly all resemble something a competitor could have produced with the same prompt, the same model, and the same half-hour of attention. The team has solved the production problem and discovered a much less convenient bottleneck: someone still has to know what is good. That is the more interesting marketing story of 2026. AI has lowered the cost of producing a presentable campaign, article, advertisement, image, email sequence, research summary, and product story. It has widened the number of directions a team can explore and compressed the time required to turn one direction into a usable asset. Those are real advantages. They are also becoming widely available. When every competent team can generate more options, production volume becomes less distinguishing. The competitive question moves upward. Who recognizes the strongest idea? Who knows what to reject? Who can connect a creative choice to a real customer tension, a product truth, and a business strategy? Who can make the company sound like itself after the software has made everyone sound fluent? AI made average marketing cheaper. It did not make average marketing more memorable. The shift was visible throughout the conversations surrounding Cannes Lions this year. [McKinsey’s post-Cannes analysis](https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights/next-in-growth/the-real-signals-from-cannes-lions-2026) described an industry moving away from broad AI optimism and toward the harder question of what actually produces business value. Its analysts also noted fatigue around the technology itself and concern that marketers had over-rotated toward AI while underweighting creativity, creators, and the work that moves the P&L. That distinction matters. Marketers have spent several years asking what AI can generate. Most of the answers are now familiar. It can produce drafts, variations, summaries, concepts, classifications, research starting points, audience segments, workflow triggers, and personalized outputs at a speed no traditional team can match manually. The useful question now is what deserves to survive that generation process. Digitas North America CEO Amy Lanzi made a similar argument in a recent Cannes conversation with _The Verge_. She described AI as a meaningful operational tool that can accelerate workflows and improve how agencies use data, while rejecting the idea that it will independently rescue weak advertising or replace human creativity. Her broader point concerned systems: marketing still needs media, CRM, creative, creators, data, and business outcomes to work together. AI can reduce the friction between an idea and its execution. It cannot guarantee that the idea carries any cultural, emotional, or commercial weight. This is why teams should resist treating AI adoption as a marketing strategy by itself. A strategy describes which market the company wants to shape, which audience it wants to earn, which problem it understands, which promise it can keep, and which choices it will make differently from competitors. A tool can help explore those questions. The company remains responsible for answering them. ## Efficiency is becoming an entry requirement Marketing leaders still need efficiency. No serious team should romanticize slow research, manual formatting, duplicated work, endless revision cycles, or the peculiar corporate ritual of paying experienced people to copy information between tabs. AI belongs wherever it can remove that drag. It can summarize a transcript, compare several hundred customer comments, identify repeated objections, reorganize a content archive, generate alternative structures, prepare a first-pass brief, and adapt an approved idea across formats. A good [AI content strategy workflow](https://withsurface.com/blog/ai-content-strategy-brand-voice) should give humans more time for interpretation rather than use automation as a reason to remove interpretation from the process. The danger arrives when efficiency becomes the final objective. A team that reduces the cost of producing forgettable material has improved a cost center. It has not necessarily improved marketing. The company may publish more frequently, test more variations, and create a larger inventory of assets without becoming more recognizable, more persuasive, or easier to choose. Surface’s existing work on the [quality-versus-volume trap](https://withsurface.com/blog/content-marketing-strategy-the-quality-vs-volume-trap-in-ai-era) applies beyond written content. Volume creates learning only when the work contains enough difference to teach the team something. Testing twenty near-identical variations mostly teaches the team which shade of sameness performed marginally better. The practical inference is that efficiency will matter increasingly as infrastructure. Every competitive marketing organization will be expected to produce, adapt, analyze, and distribute material quickly. The differentiating layer will sit above that infrastructure in the decisions governing what gets produced. The AI industry itself offers one of the clearest demonstrations. Companies developing products that promise new forms of discovery, automation, personalization, and productivity are investing heavily in familiar brand-building channels. Sensor Tower data reported by _Marketing Brew_ found that U.S. AI brands spent approximately $424 million on advertising during the first quarter of 2026, more than three times their spending from the same period a year earlier. Anthropic’s measured spending increased 1,184% year over year, while OpenAI’s increased 800%, with investment distributed across television, streaming, YouTube, LinkedIn, and other channels. There is no contradiction once we understand the category problem. AI companies can explain that their models are faster, more capable, better at reasoning, more integrated, safer, cheaper, or more useful for a particular workflow. Their competitors can make many of the same claims. Product capabilities change quickly. Benchmarks become obsolete. Features travel between platforms. Buyers receive an expanding number of technically credible options. The companies therefore need something feature comparison alone cannot provide: memory. They need buyers to recognize a name, understand its character, associate it with a type of work, and feel some confidence before examining the latest model card. They need category language, visual systems, product rituals, founder narratives, customer stories, public demonstrations, repeated media exposure, and a coherent explanation for why their version of the future deserves attention. The same pressure applies to less glamorous B2B categories. When competing companies offer similar workflow automation, analytics, integrations, dashboards, or AI assistants, the technically accurate description begins to sound like category boilerplate. Brand becomes the system that gives those capabilities shape. Taste sounds suspiciously soft inside an operating plan because marketers often confuse it with personal aesthetic preference. A creative director liking one font more than another is preference. Taste becomes strategically useful when a team can evaluate several possible expressions against the company’s customer, product, category, ambition, and moment. Taste means recognizing that an idea is technically polished and emotionally vacant. It means understanding when a clever campaign distracts from the product truth, when a popular visual trend makes the company less distinctive, when a provocative opinion lacks enough substance to survive scrutiny, and when a simple sentence carries more authority than a page of generated sophistication. Taste also means knowing what belongs together. A product interface, event, executive voice, customer story, advertisement, social post, and sales deck do not need to look identical. They should feel as though the same organization made them. That coherence helps people build a mental model of the company. A strong [content brief](https://withsurface.com/blog/what-is-a-content-brief) can establish the audience, intent, evidence requirements, internal links, structure, and strategic point of view. It cannot completely automate the editorial decision that tells a team whether the final piece has become worth reading. Standards create the floor. Taste determines how far the work moves beyond it. The teams most likely to benefit from AI will therefore be the teams with the strongest ability to select. They can generate widely, judge rigorously, and commit clearly. Teams with weak judgment may simply create more plausible distractions. A brand becomes interesting when people can take part of it with them. Sometimes that part is a sentence. Sometimes it is a visual device, a product interaction, a report, a term, a customer ritual, a founder’s way of explaining the problem, or a strangely specific point of view. It gives customers something they can remember, repeat, show, quote, recommend, or use to explain their own identity. Recent consumer branding provides literal examples. _Vogue Business_ has described a wave of food, beverage, protein, water, and wellness products borrowing the visual logic of fashion and beauty. Packaging, creator placement, product design, and social recognizability help ordinary consumable products function as attainable status objects. People encounter them in routines, photographs, influencer feeds, and public spaces rather than only on a supermarket shelf. B2B companies rarely have a beautiful bottle to place in a celebrity’s hand. They still create social objects. A benchmark report can become a social object. So can a distinctive dashboard, an assessment, a certification, a useful framework, a customer score, a category term, a conference ritual, a printed field guide, a product-generated image, or an annual index that gives an industry language for something it previously felt but could not name. The product itself can create moments worth sharing. A useful automated insight, a surprisingly elegant report, a clear before-and-after comparison, or a result customers feel proud to show can travel further than a corporate announcement asking people to believe the company is innovative. Interestingness does not require making everything strange. It requires giving the audience something more specific than functional adequacy. Creators matter to this conversation because their advantage is rarely pure production capacity. Many creators have small teams, modest resources, and little of the infrastructure available to a large marketing organization. Their leverage comes from audience understanding, recognizable judgment, repeated presence, and accumulated trust. Recent creator-economy conversations at Cannes have focused increasingly on creators as business builders rather than temporary campaign inventory. Leaders from UTA’s creator division described creators launching products, developing intellectual property, building companies, and seeking more durable ownership beyond brand sponsorships. They also warned that over-commercialization can weaken the audience relationship that made the creator valuable in the first place. That tension is instructive for brands. An audience trusts a creator because the creator has demonstrated a pattern of attention. People understand what the person notices, what they ignore, what they recommend, how they explain things, and where their boundaries sit. The individual’s judgment becomes part of the product. Brands often remove that pattern during the approval process. Legal teams soften the claim. Product teams add seven qualifications. Executives replace the interesting sentence with a safe one. The social team attaches a trending format. AI smooths the remaining language. The final asset is accurate, approved, optimized, and almost entirely free of evidence that anyone cared. The growing interest in the [Storyteller role in marketing](https://withsurface.com/blog/the-storyteller-role-in-marketing-kpis-craft-and-brand-strategy) reflects an attempt to recover that judgment inside companies. The role becomes valuable when the storyteller can work with product truth, customer experience, executive ideas, and business strategy. Hiring a good writer and giving that person nothing worth saying merely creates a more elegant bottleneck. The strongest AI marketing operating model does not divide work into “AI content” and “human content.” It assigns responsibility according to the type of intelligence required. AI is useful for breadth. It can inspect more sources, produce more alternatives, classify more records, and adapt an approved idea across more formats. Humans remain responsible for consequence. They decide which evidence is credible, which customer tension matters, which claim the product can defend, which idea fits the cultural moment, which risk is worth taking, and which expression should become part of the brand. A practical workflow looks like this: 1. **Use AI to widen the field.** Gather customer language, competitor patterns, cultural references, channel behavior, and several possible creative territories. 2. **Use people to interpret the field.** Identify the tension that matters, the product truth that can resolve it, and the perspective the company can credibly own. 3. **Generate several expressions.** Explore formats, headlines, narratives, images, demonstrations, and distribution opportunities without assuming the first polished answer is the right one. 4. **Select against explicit standards.** Evaluate distinctiveness, customer relevance, product accuracy, memorability, emotional force, channel fit, and business utility. 5. **Adapt rather than duplicate.** Let an article, video, executive post, sales asset, event, and product experience express the same idea according to the strengths of each format. 6. **Measure what the idea changed.** Track recognition, engagement, branded demand, sales-language adoption, creator or customer reuse, conversion behavior, and the quality of the leads that followed. That process requires more judgment than asking a model for one campaign. It also makes the automation useful. Interestingness should not become another vague brand metric that survives entirely because nobody can disprove it. Marketing teams can look for observable effects: - Do more buyers search for the company by name? - Can prospects explain the company accurately before the first sales call? - Do customers repeat the company’s language without being prompted? - Do creators, partners, analysts, and communities reference the brand’s frameworks or artifacts? - Do distinctive campaigns outperform generic campaigns after controlling for distribution? - Are direct traffic, return visits, newsletter engagement, and branded demand increasing? - Does the company appear in consideration sets beyond the channels it paid to enter? - Do sales teams report stronger recognition, clearer expectations, or less category explanation? - Are the leads attracted by the brand’s ideas more qualified for the product? None of these proves that one creative decision caused a revenue outcome. Together, they can show whether the company is becoming easier to remember, explain, and choose. The [content marketing operating model for 2026](https://withsurface.com/blog/content-marketing-guide-2026) already separates visibility from trust and conversion. Brand interest belongs in the tissue connecting those layers. Visibility gives someone the chance to encounter the company. Interestingness gives the encounter a chance to remain. Begin by auditing the material your team produced during the last month. Remove the company name and logo. Ask whether a knowledgeable person could identify who made each asset. Review the claims competitors could make without changing a word. Look for product descriptions that explain capabilities without communicating why anyone should care. Find the places where automation accelerated work without adding customer understanding. Next, identify one thing the company can create that competitors cannot reproduce through prompting alone. That may be customer access, proprietary data, an operational methodology, a founder’s experience, a product-generated artifact, a community, a visual system, or a distinctive way of framing the category. Then protect human attention around that thing. Do not spend the most experienced person’s time formatting drafts. Give that person responsibility for interpretation, selection, and standards. Let software widen the possibility space. Let accountable people decide where the company belongs inside it. Finally, measure the automation program by what it frees the team to do. Faster production is useful. More interesting customer research, sharper product stories, stronger creative systems, better experiments, and more memorable brand experiences are considerably more useful. AI will continue improving the average quality of marketing output. The average campaign will look cleaner. The average article will be more structurally complete. The average advertisement will have more variations. The average marketing team will possess research, design, writing, analytics, and production capabilities that would have required several specialists a few years ago. That is good news for the craft and uncomfortable news for anyone whose advantage depended on being merely competent. The remaining opportunity is human and operational at the same time. Teams can use AI to remove unnecessary labor while becoming more attentive to the customer, more demanding about the work, more coherent in their choices, and more willing to express a point of view that belongs to the company. Marketing became cheaper to make. Meaning did not. --- # AI Mode Personalization: How Personal Context Could Change Brand Recommendations | Surface Labs URL: https://surface.thesurface.network/blog/ai-mode-personalization-personal-context-changes-brands A buyer asks for a recommendation after months of reading newsletters, saving receipts, forwarding demo notes, and exchanging emails with vendors. Another buyer asks the same question with a blank history. In classic SEO reporting, marketers might expect the same public ranking surface. In personalized AI search, that assumption becomes weaker. Google announced Personal Intelligence in AI Mode in [Search](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) on January 22, 2026. Google says eligible users can opt in to connect Gmail and Google Photos to AI Mode so the system can provide more tailored responses. Google frames the feature around user control, opt-in access, and personal context for travel, shopping, and everyday planning. This matters to marketers because recommendation-style queries are commercially important. Buyers ask AI systems which tools, agencies, products, platforms, services, and vendors they should consider. If personal context influences those answers under opt-in conditions, brand visibility becomes partly situational. On May 21, 2026, iPullRank published an experiment titled "Your Inbox Might Be the Next AI Search Signal." The team tested 1,922 AI Mode responses across account conditions, including a blank control account and a blank Personal Intelligence-connected account seeded with brand signals in Gmail and Photos. iPullRank reported that seeded brands in the Personal Intelligence-connected account became 46 percentage points more likely to appear versus control, and Gmail signals outperformed photo signals. The boundary is important. iPullRank did not claim that Gmail is a universal ranking factor for default AI Mode. The study focused on opted-in Personal Intelligence conditions. The authors also state that they observed outputs and did not have access to Google's internal retrieval, ranking, model decision systems, or Personal Intelligence engine. A responsible marketer should hold both ideas together. The study does not prove a universal rule. It does provide early evidence that personal context can change brand recommendation outcomes in a specific AI Mode setup. ## Why personal context changes the marketing job Classic SEO asks teams to improve public discoverability. Personalized AI recommendations ask teams to think about what evidence a buyer carries with them. That evidence may include emails, receipts, notes, calendar invitations, product updates, newsletters, support conversations, and shared documents. Lifecycle marketers have always known that repeated, useful communication shapes memory. AI personalization gives that memory a new possible surface. A buyer who receives clear onboarding emails, useful product updates, thoughtful newsletters, and specific post-demo follow-ups may carry a richer brand context into future AI-assisted research. This should push marketers toward better communication, not creepy manipulation. A team that tries to seed awkward brand phrases into every email will create worse customer experiences. A team that makes every owned touchpoint clearer will help buyers remember what the company does and why it matters. Email clarity Review newsletters, receipts, product updates, onboarding sequences, renewal notices, webinar reminders, and sales follow-ups. Each message should use accurate product names, explain the use case, and connect the brand to a real problem. [Avoid vague nurture copy](https://withsurface.com/blog/june-1-this-week-in-marketing) that says little besides "we help teams grow." #### Customer proof Customer stories, testimonials, case studies, support replies, and community answers should carry specific evidence. A buyer should be able to see the use case, the constraint, the result, and the reason the company was credible. #### Product language consistency Product marketers should make sure the [same product, category, and feature language](https://withsurface.com/blog/may-marketing-updates) appears across the website, lifecycle emails, sales decks, help docs, and customer-facing announcements. AI systems and humans both struggle when a company describes the same offer five different ways. #### Relationship surfaces Founders and marketing leaders should identify where buyers form opinions before search: newsletters, LinkedIn posts, webinars, podcasts, events, communities, partner pages, review sites, and customer conversations. Personalized AI search may make those relationship surfaces more visible indirectly. Teams can build persona-based prompt tests, but they should label them carefully. Compare default AI responses, logged-out responses where available, public search results, and responses using ethically controlled test accounts when platform rules allow. Record date, market, query, account state, prompt, citations, mentions, and recommendations. Marketers should avoid claiming that a test proves universal visibility. The stronger claim is operational: personalized AI experiences may produce different recommendation sets, so teams need to monitor category visibility across public and relationship-influenced surfaces. A practical response does not require panic. Start with a brand memory audit. Gather the last ninety days of buyer-facing communications and ask whether a thoughtful buyer could explain the company after reading them. Then revise the weakest pieces. Make product names clear. Add specific use cases. Link to durable resources. Explain what changed and why it matters. Next, improve the pages those messages point toward. If a newsletter links to a thin product page, the team loses the compounding value of the touchpoint. The email, landing page, demo follow-up, help article, and case study should reinforce one another. ### Does this prove Gmail is an SEO ranking factor? No. iPullRank's study tested opted-in Personal Intelligence conditions in AI Mode and does not reveal Google's internal ranking logic. ### Should marketers change email strategy because of AI Mode? Marketers should improve email clarity, usefulness, and consistency. They should not manipulate inboxes or degrade customer experience for speculative AI gains. Schema recommendation: Article schema. FAQPage only if the final page keeps the FAQ visible. Add citation links to Google and iPullRank in the article body. --- # AI Search Ads Are Moving Faster Than Reporting: What Paid Media Teams Should Do | Surface Labs URL: https://surface.thesurface.network/blog/ai-search-ads-are-moving-faster-than-reporting-what-paid-media-t A paid media lead opens the weekly performance report and sees a familiar story: spend, impressions, clicks, CTR, CPC, conversions, cost per lead, cost per meeting. The chart looks stable enough to discuss. The channel has known flaws, but the team understands the basic relationship between the query, the ad, the landing page, and the conversion event. Then search stops looking like search. AI interfaces are turning discovery into a more compressed experience. A user can ask a conversational question, compare options, refine the answer, view sponsored placements, and move toward action without behaving like a classic keyword searcher. Google is testing and expanding ads inside AI-shaped Search experiences. OpenAI is testing ads inside ChatGPT while telling users that ads are separate from answers and do not influence the model’s response. The ad surface is moving into the answer environment faster than reporting models can explain what happened. That does not mean paid media teams should panic. It means they need to stop treating AI search ads like a simple inventory extension. The old paid search model was built around query intent, keyword matching, auction mechanics, ad copy, landing pages, and conversion tracking. AI-interface advertising adds new operating questions: what was the user trying to accomplish, what did the AI answer, where did the ad appear, how did the user interpret sponsorship, what source context surrounded the brand, and how should the team measure influence when the path is no longer a clean click trail? Paid media teams can still test the channel. They just need to test it with more humility than the dashboards usually encourage. AI search ads are paid placements that appear inside or alongside AI-mediated discovery experiences. These may include ads in Google AI Overviews, ads in AI Mode, shopping-style offers inside AI-assisted search flows, sponsored placements near generated answers, and ads inside conversational products like ChatGPT. The exact formats, controls, reporting fields, and commercialization models differ by platform and will keep changing. The important shift is not only placement. The important shift is context. Paid search has historically attached ads to queries and results pages. AI search ads attach paid placements to generated answers, conversational intent, product feeds, shopping assistance, and task-oriented flows. A user may not experience the ad as one blue-link alternative among several results. They may experience it as one option inside a synthesized answer environment. That changes measurement. A click may still matter. Conversion still matters. Cost per meeting still matters. But AI interfaces may influence buyer perception before a click, after a click, or without a click. As ads move into the answer layer, paid teams need reporting models that can handle assisted behavior, source context, incrementality uncertainty, and quality of demand. Thinking about [what it costs to book one meeting](https://withsurface.com/blog/what-does-it-actually-cost-you-to-book-one-meeting) becomes more important in this environment, not less. When the surface gets harder to interpret, the downstream economics matter more. A team can tolerate experimental inventory if it produces qualified conversations. It should be much more skeptical if the channel creates cheap activity, unclear intent, or leads that sales cannot convert. Classic search advertising placed paid results near organic results. The user searched, saw options, clicked, and landed somewhere else. AI search changes that rhythm. The answer itself becomes part of the experience. The interface may summarize, compare, recommend, explain, refine, and route before the user chooses whether to leave the platform. Google has said it is testing new ad formats in Search built with Gemini and expanding commerce experiments like Direct Offers. Google’s help documentation also describes ads appearing above, below, or within AI Overviews on desktop in the United States for users who see English results, while making clear that existing Search, Shopping, and Performance Max campaigns can be eligible. OpenAI has also introduced ads in ChatGPT, with documentation telling users that ads are paid placements, clearly labeled, and separate from the answers generated by ChatGPT. Those details matter because the paid experience is shifting from the results page to the answer environment. In a classic search flow, the ad competes for a click. In an AI search flow, the ad may compete for trust, interpretation, convenience, and continuation inside a guided experience. That is why [ads moving into AI search visibility](https://withsurface.com/blog/june-1-this-week-in-marketing) should be treated as a strategic measurement problem rather than a narrow media-buying update. Teams that only ask whether AI ads increase clicks will miss the bigger issue. The ad may influence which brands users consider, how they understand the category, and what they expect before they arrive on the site. Reporting usually matures after behavior changes. Marketers saw this with mobile, social, dark social, podcasts, influencer marketing, connected TV, and multi-touch attribution. Platforms introduce new user behavior, advertisers buy into it, and reporting catches up unevenly. AI search ads are likely to follow the same pattern. Platforms can expose impressions, clicks, conversions, campaign eligibility, and some placement details. Those metrics help. They do not fully explain how an AI-generated answer shaped the user’s decision, whether the ad appeared next to accurate information, whether the user interpreted sponsorship correctly, whether the brand benefited from answer context, or whether the conversion would have happened through another channel. Several reporting gaps are likely to matter: Reporting gap Why it matters Placement context Teams need to know whether the ad appeared inside, above, below, or near an AI answer Answer influence The generated answer may shape buyer perception before the click Source context Organic citations, reviews, and third-party sources may affect whether the ad feels credible Incrementality A paid interaction may capture demand that organic or direct would have captured Lead quality AI-interface clicks may represent different intent than classic keyword clicks Cross-session behavior A user may research inside AI, return directly later, and convert outside the original click path Brand safety Ads can appear near generated summaries that the advertiser did not write or control These gaps do not make the channel useless. They make simple reporting dangerous. Paid teams should avoid treating early AI search ad data as if it carries the same interpretive weight as mature search campaigns. The biggest mistake is pretending AI search ads are only “new placements.” That framing makes the work feel easy: keep the campaigns running, let the platform expand eligibility, watch the performance report, and optimize toward conversions. Some of that will happen. It will not be enough. AI search ads live in a more complicated environment. The user may arrive with a longer conversational prompt rather than a short keyword. The answer may summarize the category. The interface may present brands, products, reviews, prices, and next steps. The ad may appear alongside organic citations or recommendations. The user may click after the platform has already shaped expectations. Paid teams should therefore think less like media buyers managing isolated surfaces and more like operators managing a paid discovery system. The ad, feed, landing page, review footprint, product data, organic content, AI visibility, and lead journey all influence whether the spend turns into quality demand. This is where [AI visibility measurement](https://withsurface.com/blog/ai-visibility-measurement-geo-reporting) becomes relevant to paid media. If the AI answer consistently mentions competitors, cites competitor-friendly sources, or frames the category in a way that weakens the brand’s positioning, the ad cannot carry the whole burden alone. Paid visibility may get the brand into the moment. Source credibility and narrative clarity determine whether the brand belongs there. Paid teams should still measure the basics: impressions, clicks, CTR, CPC, conversion rate, CPA, cost per lead, cost per meeting, pipeline, and revenue. Those metrics do not disappear. They just need supporting context. Start by separating activity metrics from business metrics. Impressions, clicks, and CTR show whether the placement created interaction. Cost per lead shows whether the campaign generated form fills. Cost per meeting and opportunity quality show whether the campaign produced meaningful commercial motion. In AI-shaped surfaces, that distinction becomes especially important because curiosity clicks and high-intent clicks may look similar at first. Then add context metrics. Track whether AI-interface campaigns correlate with branded search movement, direct traffic lift, demo-page engagement, sales-call language, lead source quality, assisted conversions, and changes in the kinds of questions prospects ask. This will not produce perfect attribution. It will produce better judgment. A practical measurement framework might look like this: Layer Metrics to track What it tells the team Media delivery Impressions, clicks, CTR, CPC, spend Whether the platform delivered interaction Conversion CVR, CPL, demo requests, form fills Whether interaction became a visible lead Commercial quality Cost per meeting, accepted pipeline, sales feedback Whether leads were worth pursuing Assisted demand Branded search, direct visits, return visits, content engagement Whether the campaign may be shaping demand beyond the click Source context AI mentions, citations, competitor presence, review visibility Whether the answer environment supports or weakens the ad Incrementality Holdouts, geo tests, budget splits, pre/post comparisons Whether spend likely created new demand When teams connect paid reporting to [lead journey tracking](https://withsurface.com/blog/lead-user-journey), they can see what happened after the click with more nuance. Did the buyer read comparison pages? Did they visit pricing? Did they return through direct traffic? Did they convert after reading proof? Did sales see a better-informed prospect? Those details matter more as the ad surface becomes less transparent. ## How AI search ads change landing pages AI search ads should make landing pages sharper. If a user arrives after reading or interacting with a generated answer, they may already have category context. They may also arrive with expectations shaped by the platform, not by the advertiser. The landing page has to clarify, correct, deepen, and convert quickly. A strong landing page for AI-interface traffic should include: Landing page element Why it matters Clear category statement Confirms what the company does without forcing the user to decode positioning Use-case specificity Matches the user’s likely task or problem Proof blocks Gives evidence after an AI-generated summary may have framed the category Comparison language Helps buyers place the company among alternatives Objection handling Answers the questions the AI answer may have surfaced Source-backed claims Makes the page easier to trust and cite Next-step clarity Routes the buyer toward the appropriate action This is also where [query fan-out content architecture](https://withsurface.com/blog/query-fan-out-google-ai-search-content-architecture) connects to paid media. If an ad brings a user into one part of the research path, the site needs to help them continue the path. A landing page should not become a dead end. It should connect to comparisons, proof, implementation guidance, pricing context, and conversion. Paid media teams should therefore review landing pages against the AI answer environment. What questions might the user already have asked? What claims might the interface have already made? Which competitors may have appeared? Which proof does the page need to provide immediately? Which internal links help the buyer continue without bouncing back to the AI interface? AI search ads will likely make product and business data more important. Shopping-oriented AI experiences already rely on feeds, merchant data, product details, prices, availability, promotions, and structured information. B2B experiences may not look exactly like ecommerce, but the same principle applies: AI systems need clean, current, machine-readable context to match a paid placement to the user’s task. For ecommerce teams, this means feed quality, product attributes, pricing accuracy, inventory, images, reviews, policies, and promotional logic become more central. For B2B teams, the parallel is product clarity: use cases, audience fit, integrations, pricing context, comparison points, implementation requirements, security details, and proof assets. Paid teams should work more closely with SEO, product marketing, RevOps, and content. The ad auction may live in Google Ads or another platform, but performance will increasingly depend on the quality of the underlying source ecosystem. If the product data is weak, the landing page is vague, the reviews are thin, and the site has little proof, the ad will have to overcome more friction. Thinking about [generative AI search optimization](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) should therefore change paid planning. The same pages that help AI systems understand and cite the company can help paid users trust the company after a click. The same source gaps that weaken organic AI visibility can also weaken paid performance. Paid teams should treat AI search ads as controlled experiments, not as mature channels with settled benchmarks. That starts with a written hypothesis. For example: “AI-interface ads will create more qualified consideration-stage traffic for category prompts than standard non-brand search campaigns.” Or: “AI shopping placements will improve assisted conversions for high-intent product research queries but may not reduce last-click CPA in the first month.” The test should include a defined audience or campaign segment, limited budget, clear conversion events, landing page controls, and a comparison baseline. Teams should decide in advance what would count as success, what would count as a warning sign, and what would require more data. Useful testing methods may include: Test method Use case Budget split Compare AI-eligible campaigns against standard campaign structures Geo holdout Measure whether markets with exposure behave differently from withheld markets Landing page split Test whether AI-interface visitors need different proof or CTAs Prompt/source audit Review the answer environment around priority paid categories Lead-quality review Ask sales to grade lead fit and expectation quality Search-lift monitoring Watch branded and category search movement during the test Assisted conversion analysis Look for return visits and delayed conversions This kind of testing will not remove every uncertainty. It will keep the team from confusing early platform activity with durable business value. Paid media leaders should start asking harder questions about AI-interface reporting. Some answers may not exist yet, which is itself useful to know. Ask platforms and vendors: Question Why to ask Can we see whether ads appeared inside, above, below, or near AI-generated content? Placement context changes interpretation Can we isolate AI-interface inventory from standard search inventory? Mixed reporting hides channel behavior What campaign types are eligible for AI placements? Eligibility affects control What query or intent data is available? Prompt opacity affects optimization Can we see source or answer context? The generated environment shapes user expectations How are conversions attributed when the user continues across sessions? AI discovery may create delayed behavior Can we run holdout or incrementality tests? Incrementality matters more than activity What brand-safety controls exist? Advertisers need context protection How are ads labeled and separated from generated answers? User trust affects performance and compliance The point is not to demand perfect reporting before testing. The point is to know what the team can and cannot see before budget expands. AI search ads will attract budget because they sit near the future of search behavior. That does not mean teams should pour spend into them without guardrails. Start with a learning budget. Keep expectations modest. Define success around insight and qualified movement, not only immediate CPA improvement. Protect the account by keeping mature campaigns stable while testing AI-interface opportunities in controlled segments where possible. Review search terms, placements, landing-page behavior, lead quality, and sales feedback more frequently during the early period. If the platform blends reporting in ways that make isolation difficult, acknowledge that limitation in the performance readout. Most importantly, protect the business from vanity metrics. Cheap clicks do not matter if they create low-intent leads. High CTR does not matter if the answer environment misframes the brand. Impression growth does not matter if the team cannot connect it to stronger demand, better prospects, or clearer category presence. AI search ads should earn more budget by improving business outcomes, not by looking novel. AI search ads expose the limits of channel silos. Paid media can buy the placement, but it cannot single-handedly control the answer environment, source ecosystem, landing page proof, product clarity, lead routing, sales follow-up, or customer evidence. Performance will depend on coordination. SEO teams need to make sure key pages are crawlable, current, and useful. Content teams need to build the surrounding educational and comparison assets. Product marketing needs to sharpen positioning and proof. Customer marketing needs to produce credible stories. RevOps needs to make sure leads are routed and followed up with correctly. Sales needs to report whether AI-interface leads arrive better informed or more confused. When [inbound lead management](https://withsurface.com/blog/inbound-lead-management) works well, paid teams can learn from what happens after conversion. When it works poorly, the channel absorbs blame for problems that happen downstream. AI search ads will make that risk more visible because the path to conversion may become even harder to interpret. Start by auditing where AI-shaped ad inventory may already enter existing campaigns. Review platform documentation, campaign eligibility, Performance Max behavior, Search campaign settings, Shopping feeds, product data, and reporting segmentation. Teams should know whether they are testing AI-interface inventory intentionally or receiving it through platform expansion. Next, inspect the answer environment around priority paid categories. Search the questions buyers ask. Review which brands appear, which sources get cited, which competitors show up, what claims appear, and whether the company’s owned pages support or contradict the paid message. Paid teams should understand the informational world surrounding the ad. Then update landing pages. Add proof blocks, clearer category language, comparison support, objection handling, and stronger next steps. Make sure the page continues the research path instead of forcing the user into a generic demo request before trust exists. After that, build a measurement model that separates delivery, conversion, commercial quality, assisted demand, source context, and incrementality. Do not wait for perfect platform reporting. Create a practical framework now, then refine it as the platforms expose better data. Finally, create a cross-functional owner for AI-interface growth. Paid media should remain accountable for spend, testing, and performance, but someone needs to coordinate the overlap between ads, AI visibility, SEO, content architecture, product proof, and lead journey infrastructure. AI search ads are neither a gimmick nor a solved channel. They represent a real shift in how paid media may enter discovery, comparison, and recommendation. They also arrive before the reporting layer can fully explain their influence. That combination calls for disciplined curiosity. Paid teams should test early enough to learn, slowly enough to avoid waste, and honestly enough to admit what the data cannot prove yet. They should measure clicks and conversions, but they should also measure lead quality, source context, assisted behavior, incrementality, and buyer understanding. The paid search teams that adapt well will not be the teams that chase every AI placement blindly. They will be the teams that understand the whole answer environment. They will know what the AI system says, what the ad promises, what the landing page proves, what the buyer does next, and whether the business actually benefits. Reporting will mature. Platforms will add controls. Benchmarks will stabilize. Until then, marketers should treat AI search ads as a developing operating system for demand, not a finished media channel. The work is to learn without pretending the dashboard knows more than it does. --- # The AI Search Control Layer: Opt-Outs, Preferred Sources, and the New Publisher Bargain | Surface Labs URL: https://surface.thesurface.network/blog/ai-search-control-layer-opt-outs-preferred-sources AI search used to sound like an exposure problem. Marketers asked whether the brand appeared. Publishers asked whether Google would still send traffic. SEOs asked whether citations overlapped with rankings. Product marketers asked whether AI systems understood the category well enough to recommend the company correctly. Those questions still matter. A new layer is forming underneath them: control. Google has started giving site owners more visibility into generative AI search performance through Search Console reporting. The company has also announced tests that let some site owners opt out of generative AI features in Search, beginning in the UK. At the same time, Google is bringing Preferred Sources into AI Overviews and AI Mode, giving users more influence over which sources appear in AI-assisted search experiences. Regulators are moving too. The UK Competition and Markets Authority has imposed conduct requirements on Google Search that include stronger publisher controls, attribution, links, and opt-out options around AI features. For marketers, this is not only a publisher-rights story. It is a content governance story. A page is no longer only a page. A strong page can become a search result, an answer source, a citation object, a product proof asset, a sales enablement asset, a branded-search trigger, and a machine-readable fragment of the company’s public memory. A weak page can become a liability for the same reason. It can be summarized out of context, cited instead of a better page, used to support an outdated claim, or surfaced where the company would rather have a more conversion-ready destination. AI search controls force a better operating question: what should each important page be allowed to do? ## AI search controls turn content audits into governance work Traditional content audits usually sort pages into a few familiar buckets: keep, refresh, redirect, consolidate, or delete. That work still matters. It is one of the quiet disciplines behind healthy SEO and better conversion paths. AI search adds another classification layer. Marketers now have to think about whether a page should be cited, summarized, protected, refreshed, made more explicit, or treated as risky. The page’s role in a site architecture is only part of the issue. Its role in answer generation matters too. A practical AI search governance model can sort pages into five roles: 1. **Open citation assets:** Category explainers, research-backed guides, glossaries, benchmark pages, and educational assets that benefit from being summarized and cited. 2. **Controlled conversion assets:** Pricing pages, demo pages, product pages, interactive tools, and case studies where the full on-site experience matters. 3. **Sensitive claim assets:** Security, legal, medical, financial, compliance, regulatory, or competitive claims that require exact language and current evidence. 4. **Outdated risk assets:** Old blog posts, stale comparison pages, obsolete screenshots, old pricing references, and unsupported market claims. 5. **Authority reinforcement assets:** Expert POV, customer evidence, partner proof, industry research, and source-backed analysis that helps a brand become easier to cite or recommend. This classification does not require panic. Most B2B companies should not start by opting out of every AI surface. Visibility still matters. AI search can create awareness, recommendation moments, branded search, referral sessions, and better-prepared buyers. The point is that inclusion should become intentional. Teams working on [generative AI search optimization](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) need to know which pages should answer broad questions, which pages should support comparison prompts, and which pages should remain closer to the conversion path. Opt-out controls are strategically important even if most marketers do not use them immediately. The existence of a control changes the conversation from “can we get included?” to “where do we want inclusion, and on what terms?” That is a healthier question. It moves AI visibility away from pure surface area and toward page-level responsibility. A B2B company should start by identifying which pages contain claims that could be misunderstood if compressed into a short AI answer. Security pages, compliance pages, pricing pages, competitor pages, and product limitation pages deserve special attention. These pages often contain nuance that matters to buyers and internal teams. If an AI system summarizes that nuance poorly, the company may create confusion before sales ever enters the conversation. The next step is to identify pages that would benefit from wider AI summarization. A strong educational page that defines a category, explains a framework, cites credible sources, and points readers to a clear next step is a good candidate for AI visibility. A thin page created only to target a keyword probably is not. If AI search rewards a page, it should reward a page the company is comfortable having buyers encounter first. Thinking about [query fan-out in Google AI search](https://withsurface.com/blog/query-fan-out-in-google-ai-search-how-marketers-should-build-con) makes this page-role work more concrete. One buyer prompt can expand into hidden subquestions about implementation, cost, alternatives, risks, proof, integrations, and buying process. If the company has no strong page for one of those subquestions, an AI system may use a competitor, a review site, a forum, or an old article instead. Google’s Preferred Sources expansion is a quiet but important signal. Users can choose sources they want to see more often, and Google is bringing those preferences into AI Overviews and AI Mode. That does not mean every B2B company suddenly becomes a preferred source. It does mean source preference is becoming more visible inside search itself. For marketers, this reinforces a larger truth: AI visibility depends on more than the owned blog archive. It depends on whether a company’s public evidence graph looks useful, fresh, credible, and specific enough to be reused. Owned content matters. Third-party proof matters. Reviews matter. Partner pages matter. Customer stories matter. Expert commentary matters. Videos, webinars, documentation, comparison pages, and industry mentions can all help make a brand easier to understand. A company cannot control every source, and it should not pretend otherwise. It can, however, build a stronger source ecosystem. That is where [content marketing strategy](https://withsurface.com/blog/content-marketing-strategy-the-quality-vs-volume-trap-in-ai-era) meets AI search governance. Volume alone does not create trust. A bloated archive may increase crawlable surface area while making the company harder to classify. A tighter system of current, well-sourced, internally connected pages can make the company easier for both buyers and AI systems to use. Source strategy should answer a few practical questions: - Which owned pages should AI systems cite for category education? - Which third-party sources currently explain the company accurately? - Which customer proof assets support the claims sales actually makes? - Which comparison pages are fair, specific, and current? - Which outdated pages are still findable and likely to confuse buyers? - Which high-intent pages need stronger context around pricing, implementation, or fit? The goal is not to game a source preference feature. The goal is to become a better source. The regulatory story matters because AI search changes the economic bargain between platforms, publishers, and brands. Traditional search sent users to sources. AI search can summarize the source before a click happens. That may be useful for users, but it raises hard questions about attribution, traffic, revenue, control, and responsibility. The UK CMA’s conduct requirement for Google Search is one example of that tension becoming operational. The requirement pushes for stronger publisher controls, clearer attribution, links, and opt-out options around AI features. Separately, a German court ruling that Google is appealing held the company responsible for allegedly false claims in AI Overviews. These are not ordinary SEO updates. They are signs that AI search is becoming a legal, editorial, and commercial system. Academic measurement work adds another reason for caution. Research on Google AI Overviews has found that AI results can use sources differently from traditional organic search, activate differently by query type, and include unsupported claims in some cases. Another study found that generative search systems can vary with minor query changes, making single-snapshot measurement especially weak. For marketers, the lesson is not that AI search is unusable. The lesson is that AI search visibility needs governance. If a company wants to be summarized, cited, recommended, and routed into buyer journeys, it should maintain the public materials that make those actions safer. ## Build a page-level AI search control map A practical AI search control map can live inside a content inventory spreadsheet. It does not need to be fancy at first. Add columns that describe the page’s role, risk, freshness, evidence level, and desired AI visibility behavior. Useful columns include: - Page URL - Page type - Funnel role - Target buyer question - Desired AI role - Citation readiness - Summary risk - Evidence freshness - Claim sensitivity - Internal owner - Refresh priority - Conversion path - Third-party proof support - Notes from AI visibility testing The “desired AI role” column is especially useful. A page might be marked as “open citation,” “controlled conversion,” “sensitive claim,” “refresh before promotion,” or “remove from priority.” That simple label gives content, SEO, product marketing, legal, and RevOps a shared language. Teams using [lead journey tracking](https://withsurface.com/blog/lead-user-journey) should connect this map to buyer behavior. If AI Assistant referrals land on an educational page and then move to pricing, comparison, and demo pages, that page may be doing useful upstream work. If AI-visible pages attract traffic that never moves deeper, the page may be answering the wrong question or failing to route the buyer. ## Refresh pages for answer quality, not only rankings A page refreshed for AI search should not simply add a new keyword and a few subheads. It should become easier to cite, easier to summarize, and safer to reuse. That usually means: - Put the core answer near the top. - Add current evidence for factual claims. - Use dates on statistics, screenshots, and benchmarks. - Name the category and use cases clearly. - Explain tradeoffs without flattening nuance. - Add customer proof where claims need validation. - Use internal links to route from education to proof to conversion. - Remove stale claims, outdated examples, and unsupported comparisons. - Make authorship, expertise, or editorial responsibility visible where relevant. This work improves more than AI visibility. It helps human buyers too. A page that can be summarized accurately is often a page that can be read quickly by a busy operator, forwarded by a sales rep, used in a nurture sequence, and cited in a board memo. AI search governance should include a response path. If an AI system summarizes your product incorrectly, cites an outdated page, names a competitor as a better fit using stale information, or attaches your brand to a false claim, someone needs to know what happens next. A simple escalation rule should define: - Who monitors AI visibility and summaries - Who owns content corrections - Who owns legal or compliance review - Who contacts platforms when correction tools exist - Who updates source pages - Who informs sales if buyer-facing confusion is likely - Who documents the issue and resolution Without this path, teams will improvise under pressure. That is rarely when they produce their best judgment. Start with classification. Identify which pages should act as open citation assets, controlled conversion assets, sensitive claim assets, outdated risk assets, and authority reinforcement assets. Then refresh the high-value pages. Update evidence, clarify categories, strengthen proof, remove stale claims, and add internal links that help buyers move from education to evaluation. Thinking about [generative engine optimization services](https://withsurface.com/blog/generative-engine-optimization-services) as a source-governance system, rather than a prompt-hacking exercise, will produce stronger work. Next, monitor AI visibility with caveats. Use Search Console generative AI reporting where available. Use GA4’s AI Assistant channel to understand referral behavior. Run repeated prompt-set tests across buyer questions. Compare visibility against lead quality, not just citation counts. Finally, decide what control means for the business. Some pages should be widely discoverable. Some should be refreshed before they become answer sources. Some should be protected because context matters. Some should be removed because they no longer represent the company. AI search controls are still early. Reporting is uneven. Regulations vary by market. Platform behavior will keep changing. Still, the direction is clear enough for marketers to act. Treat every important page as a possible answer source, every answer source as a possible recommendation input, and every recommendation as a possible business event that deserves measurement. --- # AI Visibility Dashboard | Surface Labs URL: https://surface.thesurface.network/blog/ai-visibility-dashboard ## New in Content Ops: AI Visibility Dashboard _Mahdin M Zahere · May 2026_ * * * AI Visibility Dashboard is a new feature inside Surface that tracks how often AI models mention your brand when buyers ask questions in your category. It benchmarks you against competitors across ChatGPT, Gemini, Claude, and Copilot, and shows you where the gaps are. Built for marketing and content teams who need to know whether AI is recommending them or their competitors. ### Why this matters now Buyers are starting their research inside AI assistants. They type "what's the best tool for lead scoring" into ChatGPT or ask Claude "which platforms help with inbound form routing," and they get a list of recommendations. If your brand is on that list, you're in the conversation. If it's not, you're not. With Google, you can check your rankings and see position 1 through 10. With AI search, the answer is generated fresh every time. There's no static ranking to track. You can manually ask ChatGPT about your brand and get one data point, but that doesn't scale and the responses vary by session. The tools that exist for tracking AI visibility today give you surface-level mention counts. What they don't give you is the context that actually drives decisions: which specific prompts you're winning or losing on, how your visibility differs across individual models, how your competitor gaps are trending over time, and what content is actually moving the needle. That's what AI Visibility Dashboard is built to do. ### How it works Setup takes a few minutes. You add your brand, add the competitors you want to benchmark against, and write the prompts you want to monitor. These should be the questions your buyers would actually type into an AI assistant when evaluating tools in your space. Surface monitors how ChatGPT, Gemini, Claude, and Copilot respond to those prompts on an ongoing basis. Every mention of your brand or a competitor's brand is tracked, scored, and visualized in the dashboard. Here's what you see: What's in the dashboard What it tells you Visibility Score Your overall share-of-voice across all tracked AI models as a percentage Content Coverage How much of your category's topic space your content actually covers Total Mentions How many times AI models referenced you across all tracked prompts Competitor Rankings Your visibility vs every competitor you're tracking, side by side Brand Visibility Chart Your share-of-voice over time, plotted against competitors week by week Per-Model Breakdown How you perform on ChatGPT vs Gemini vs Claude vs Copilot individually Tracked Prompts Every prompt you're monitoring, with your presence status on each one Two things tend to surprise people when they first see their data. The first is that visibility varies wildly across models. You might be well represented in Gemini but nearly invisible in ChatGPT. Knowing that changes where you focus your content efforts. The second is the competitor gap. Most teams assume they're roughly in line with their competition. The data usually shows a bigger spread than expected. ### What you actually do with this The visibility data becomes a direct input into your content strategy. If the dashboard shows that ChatGPT never mentions you when someone asks about lead scoring, that's not an abstract metric. That's a gap you can close with a specific piece of content targeting that topic. Same thing with competitor gaps. If a competitor has 40% visibility and you're sitting at 15%, the dashboard tells you exactly which prompts they're winning on so you know where to focus. What you learn What you do about it "ChatGPT never mentions us for lead scoring" Write content specifically targeting that gap "We're strong on Gemini but invisible in ChatGPT" Investigate what ChatGPT surfaces and adjust "Competitor X has 40% visibility, we have 15%" Prioritize closing the gap on their strongest prompts "Visibility jumped 20% after last month's blog push" Double down on the content approach that worked "We're losing ground on 3 prompts this month" Diagnose why and course correct before it compounds The feedback loop is what makes this valuable over time. After a few weeks of tracking, you start to see which content investments actually move the needle in AI search and which ones don't. Most marketing teams are making content decisions without this data. The ones using the AI Visibility Dashboard aren't guessing anymore. ### Getting started AI Visibility Dashboard is available now on Surface. Add your brand, your competitors, and the prompts you care about. You'll have visibility data within minutes. If you want to see it loaded up with your own brand and competitors, [book a demo](https://withsurface.com/book-a-demo) and we'll run a live analysis on the call. --- # AI Visibility Measurement Is Messy: How to Report GEO Without Fake Precision | Surface Labs URL: https://surface.thesurface.network/blog/ai-visibility-measurement-is-messy-how-to-report-geo-without-fak A marketing leader opens an AI visibility report and sees the number everyone wants to see: the brand appears in 37% of target prompts. The dashboard looks clean. The competitor table looks decisive. The line chart appears to know exactly where the brand stands. Then someone reruns three prompts manually and gets different answers. That moment should not embarrass the team. It should change the reporting model. AI visibility measurement is messy because generative systems are messy. Answers vary across prompts, paraphrases, interfaces, models, logged-in states, locations, freshness windows, retrieval behavior, and repeated runs. A brand can be absent in one answer, mentioned in another, cited in a third, and recommended in a fourth. A page can be cited without shaping the final answer very much. A competitor can appear because a third-party source explains the category more clearly than either company does. Generative engine optimization, or GEO, needs measurement. Marketing teams need to know whether AI systems can find, understand, cite, mention, and recommend them. But the industry will damage its own credibility if it turns unstable observations into fake certainty. GEO reporting should not pretend to be a cleaner version of keyword ranking. It should help teams make useful decisions while showing the uncertainty in the system. AI visibility measurement tracks how brands, pages, products, experts, and competitors appear inside AI-generated answers. A useful GEO report may include brand mentions, source citations, recommendations, share of model voice, sentiment, answer inclusion, competitor presence, source mix, citation quality, and downstream business behavior. The problem is that none of these metrics behave exactly like classic SEO rankings. In traditional search, a team could often treat one query as a reasonably stable snapshot of the results page. Rankings still changed by location, device, personalization, and time, but the reporting model had a familiar shape. AI search changes the unit of analysis. The answer is generated. The source set may change. The phrasing may change. The recommendation may change. The cited pages may not equal the pages that most influenced the answer. That makes GEO reporting useful and dangerous at the same time. A report can reveal visibility gaps, source weaknesses, competitor advantages, content opportunities, and narrative misrepresentation. A report can also mislead executives if it presents single-run outputs as fixed truth. Thinking about [AI citations vs. SEO rankings](https://withsurface.com/blog/ai-citations-vs-seo-rankings) gives marketers the right starting point: ranking, citation, mention, recommendation, and answer influence are related visibility states, but they are not the same metric. GEO reporting feels messy because AI answers do not always repeat themselves. A prompt can produce different answers across tools, across time, and across slight wording changes. Two prompts that seem equivalent to a marketer may trigger different source sets. A model may cite one page today and another page tomorrow. A brand may appear in a neutral list for one phrasing and disappear when the prompt asks for “best,” “enterprise,” “affordable,” “secure,” or “for B2B SaaS.” This variability creates a measurement problem. A single test can still be useful as a diagnostic snapshot, but it should not become the entire report. When teams make big strategic claims from one run of one prompt, they mistake an observation for a distribution. The better question is not “Did we appear?” The better question is “How often do we appear across a representative prompt set, repeated enough times to understand the range?” That distinction matters for clients and executives. A team that reports “we are at 37% visibility” without caveats implies more certainty than the system can support. A team that reports “we appeared in 37% of sampled answers across this prompt family, with strongest visibility in comparison prompts and weakest visibility in implementation prompts” gives leaders something they can act on without pretending the number is permanent. An [AI visibility dashboard](https://withsurface.com/blog/ai-visibility-dashboard) should therefore help teams see patterns rather than manufacture precision. The dashboard should show where the brand appears, which competitors appear, which sources support the answers, what kinds of prompts trigger inclusion, and where the model seems uncertain, inconsistent, or misinformed. The first fix is vocabulary. Marketers should stop blending every AI appearance into one visibility score. A brand mention, a source citation, a vendor recommendation, and answer influence all mean different things. A mention means the brand appeared in the answer. That can be useful, especially in categories where AI systems compress the consideration set. But a mention may be neutral, inaccurate, outdated, or buried in a long list. A citation means the system displayed or referenced a source. Citations matter because they show which pages the interface surfaced as support. But citation does not automatically mean the page shaped the answer deeply. A cited page may contribute a small factual detail, while another uncited source or prior model knowledge shapes the recommendation. A recommendation means the brand was positioned as a viable or preferred option. This is often more commercially valuable than a neutral mention, especially for category, comparison, and “best tool” prompts. Still, recommendations need to be judged by framing. A brand can be recommended for the wrong buyer, wrong use case, or wrong feature set. Influence is the hardest layer. A page may contribute language, definitions, structure, comparisons, or evidence to the final answer. Citation-selection research and emerging GEO measurement work increasingly suggest that source citation and answer influence can diverge. Marketers should therefore avoid treating citation count as the whole story. A practical report should separate these states: Visibility state What it tells you What it does not prove Mention The brand appeared in the answer The brand was recommended or trusted Citation A source was surfaced as support The source deeply influenced the answer Recommendation The brand was positioned as a choice The recommendation was accurate or high-intent Answer influence The source shaped the response The system will cite or send traffic Source mix The answer drew from certain source types Owned content alone caused the result This separation keeps the report honest. It also helps marketers diagnose the real problem. A brand with mentions but no citations may need stronger owned assets. A brand with citations but weak recommendations may need clearer positioning and proof. A brand with competitor recommendations from third-party sources may need off-site validation, not another blog post. A serious GEO report should organize prompts into families. Prompt families are groups of related questions that represent one buyer research path. A category family may ask what the category is, which vendors matter, what features to evaluate, how pricing works, and what risks buyers should consider. A comparison family may ask how one brand compares to competitors. An implementation family may ask how to deploy, measure, integrate, or govern the solution. Prompt families matter because AI systems respond differently to phrasing. “Best AI visibility tools” may produce one answer. “What should a B2B SaaS company use to measure GEO?” may produce another. “How do I compare AI search visibility platforms?” may produce another. A report that only tests one version of the question will miss the shape of the buyer’s actual research behavior. Query fan-out makes this even more important. When AI search systems break a complex question into related searches, marketers need to understand the surrounding question field, not only the head prompt. Building content around [query fan-out in Google AI Search](https://withsurface.com/blog/query-fan-out-google-ai-search-content-architecture) means reporting should follow the same logic: measure the cluster of related intents, then use the gaps to improve content architecture. A simple prompt-family report might include: Prompt family Example prompts What to measure Category education “What is GEO?” “How is GEO different from SEO?” Definition accuracy, cited sources, category framing Vendor discovery “Best GEO tools for B2B SaaS” Brand presence, competitor set, recommendations Comparison “Brand A vs Brand B for AI visibility” Positioning accuracy, source mix, narrative gaps Implementation “How should marketers report AI visibility?” Evidence quality, method fit, cited frameworks Executive decision “Should a CMO invest in GEO?” Business framing, risk language, actionability This approach gives teams more than a visibility score. It shows where the brand participates in the buyer’s thinking and where it disappears. Single-run testing is the easiest way to produce fake precision. A better report repeats prompt tests across multiple runs and labels confidence accordingly. The team does not need to turn every GEO report into a PhD project, but it should stop presenting one answer as though it represents the entire behavior of a model. A lightweight confidence model can work well. For each metric, label the result as high confidence, directional, or unstable. High-confidence findings appear repeatedly across runs, prompt variations, and models. Directional findings appear often enough to guide action but need more sampling. Unstable findings vary too much to support a strong claim. For example: Finding Confidence label Why Competitor A appears in most vendor-discovery prompts High confidence Repeated across tools and paraphrases Our brand appears more often in educational prompts than comparison prompts Directional Pattern appears, but sample size is modest Perplexity prefers one specific article as a source Unstable Citation changes across repeated runs Our brand is miscategorized in enterprise prompts High confidence Same error appears in multiple answers This reporting style does not weaken the work. It makes the work more trustworthy. Executives can still make decisions from directional evidence. They just need to know whether the report is showing a durable pattern or a fragile observation. ## Track source mix because AI visibility is not only owned content AI systems assemble answers from many kinds of sources. Owned pages matter, but review sites, trade publications, comparison pages, forums, videos, documentation, analyst content, partner pages, customer stories, and social discussions may all influence how a brand appears. A GEO report that only tracks whether the company’s website is cited will miss much of the market. Source mix analysis asks which types of sources appear across target prompts. Are AI systems citing owned blog posts, product pages, documentation, Reddit threads, YouTube videos, review sites, listicles, competitor pages, analyst pages, or news coverage? Which sources support the company? Which sources support competitors? Which sources describe the category most clearly? This is where [generative engine optimization services](https://withsurface.com/blog/generative-engine-optimization-services) need a real content strategy behind them. Teams cannot improve AI visibility by rewriting owned pages alone if the model’s source ecosystem keeps pulling from competitor comparisons, outdated review pages, weak listicles, or community discussions where the brand is absent. A useful source-mix table might look like this: Source type What to inspect Likely action Owned pages Are they crawlable, current, specific, and evidence-backed? Refresh or restructure priority pages Third-party lists Is the brand included, excluded, or misrepresented? Pursue inclusion, correction, or stronger proof Reviews Do customer claims support the desired positioning? Improve review capture and customer proof Communities What language do real users use? Address objections and update messaging Videos/podcasts Are experts or customers explaining the category? Create or pitch richer source formats Competitor pages Which claims are shaping the comparison? Publish clearer comparison and proof assets When source mix becomes visible, teams can stop asking vague questions like “How do we rank in AI?” and start asking useful questions like “Which sources teach the model to trust our competitor more than us?” GEO reporting should not stop at visibility. A brand can appear frequently in AI answers and still fail to generate business value if the answers are low-intent, misaligned, inaccurate, or disconnected from conversion paths. Marketers need to connect AI visibility to the buyer journey without pretending every AI mention produces a measurable click. Start by assigning business intent to prompt families. Educational prompts may support awareness and category formation. Comparison prompts may support vendor consideration. Implementation prompts may support sales enablement and late-stage confidence. “Best tool” prompts may support demand capture. Executive prompts may influence strategic budget decisions. Then connect prompt visibility to downstream indicators. These may include branded search movement, direct traffic, assisted conversions, demo quality, sales-call language, content engagement, source referrals, review traffic, newsletter signups, and pipeline influence. None of these will perfectly attribute AI visibility. Together, they can show whether improved visibility aligns with business movement. The post-click path still matters. When teams use [lead journey tracking](https://withsurface.com/blog/lead-user-journey), they can understand what a buyer read, compared, and considered before conversion. When teams improve [inbound lead management](https://withsurface.com/blog/inbound-lead-management), they can respond to that context with better routing, qualification, enrichment, and follow-up. GEO can help a buyer discover the company, but the revenue system still needs to carry the buyer forward. A responsible GEO report should include the findings, the method, the sample, the caveats, and the recommended actions. It should be clear enough for executives and honest enough for practitioners. The goal is not to bury the report in disclaimers. The goal is to prevent the team from making decisions based on overconfident numbers. At minimum, include: Reporting element Why it matters Prompt set Shows what buyer questions the report actually tested Prompt families Prevents one prompt from standing in for the whole category Platforms tested Clarifies whether results came from Google AI features, ChatGPT, Perplexity, Gemini, Claude, or another tool Run count Shows whether findings came from one observation or repeated testing Date range Marks freshness in a fast-moving environment Brand mentions Tracks whether the brand appears Citations Tracks whether owned or third-party sources appear Recommendations Tracks whether the brand is positioned as a choice Competitor presence Shows the compressed consideration set Source mix Reveals which sources shape the answer Confidence labels Separates durable findings from directional or unstable ones Actions Turns visibility data into content, SEO, PR, review, or sales enablement work This structure gives the report a practical operating rhythm. The team can run the same prompt families over time, compare patterns, refresh priority pages, improve source coverage, and watch whether the brand’s presence becomes more consistent. Do not report single-run visibility as a fixed market share. Do not use one prompt to claim category leadership. Do not blend mentions, citations, and recommendations into one score without showing the underlying states. Do not imply that an AI citation automatically produced a buyer or a click. Do not compare tools without explaining that different systems expose sources differently. Do not hide volatility because the dashboard looks better without it. Volatility is part of the finding. If the brand appears inconsistently, the team needs to know. If competitors appear reliably across prompt variants, the team needs to know. If the model uses outdated sources, the team needs to know. Reporting uncertainty is not a weakness. It is the difference between intelligence and theater. Marketers should also avoid treating GEO as a separate discipline detached from SEO. Google’s AI features guidance continues to emphasize foundational SEO practices, indexability, internal links, textual content, page experience, and helpful content. AEO and GEO work should extend that foundation rather than distract from it. The companies that skip the basics usually end up measuring their own site problems in a more expensive dashboard. Weekly reporting should focus on change detection. Teams can monitor a small set of priority prompt families, major competitors, and critical source changes. The weekly report should answer simple questions: did anything major change, did a competitor enter or leave the answer set, did source mix shift, did the brand get misrepresented, and did any new content begin appearing? Monthly reporting should focus on pattern analysis. Teams can run a larger prompt set, compare repeated samples, update confidence labels, assess content gaps, and prioritize fixes. This is the right cadence for deciding which pages to refresh, which comparisons to publish, which sources to pursue, and which sales enablement assets need stronger evidence. Quarterly reporting should connect AI visibility to business strategy. Teams should review whether category presence improved, whether competitor gaps narrowed, whether source quality improved, whether sales teams reused the narrative, and whether visibility appears to align with branded demand, qualified meetings, or pipeline influence. The quarterly report should also decide which prompt families no longer matter and which new ones need to be added. This cadence keeps the work from becoming either panic-driven or ornamental. GEO reporting should not turn into a daily ritual of refreshing unstable answers. It should become a decision system. The messiness of AI visibility measurement is not a reason to avoid the work. It is a reason to do the work better. Search behavior is changing. AI interfaces are compressing research, comparison, citation, and recommendation into answer environments where clicks are less reliable and attribution is fragmented. Marketing teams need visibility reporting for that world. They also need humility. A report that admits uncertainty will often be more useful than a report that hides it. Teams can still make decisions from incomplete data when they know what kind of incompleteness they are looking at. They can refresh content, improve internal links, add proof, strengthen off-site sources, correct misrepresentation, and build better conversion paths. GEO reporting should show the company how it appears inside the retrieval environment, how consistently it appears, who appears instead, which sources shape the answer, and what the team should do next. That is enough. Fake precision will only make the dashboard feel stronger while making the strategy weaker. --- # AI Visibility Reporting Without Fake Precision | Surface Labs URL: https://surface.thesurface.network/blog/ai-visibility-reporting-without-fake-precision AI visibility reporting has reached its dangerous middle stage. It is real enough to measure, incomplete enough to misread, and new enough that teams can still dress ordinary uncertainty in confident dashboard language. That does not mean marketers should avoid measurement. It means they should measure AI visibility as a chain of evidence rather than a single trophy metric. A citation screenshot is evidence. An AI Assistant referral in GA4 is evidence. A Search Console generative AI impression is evidence. A branded search lift after assistant exposure may be evidence. A closed-won opportunity with no known AI source may still have been influenced by AI-mediated research. Those signals matter, but they do not mean the same thing. Google’s recent updates make this more urgent. Search Console is rolling out dedicated generative AI performance reports for a subset of users, including impressions, pages, countries, devices, and dates. GA4 now classifies traffic from AI assistants like ChatGPT, Gemini, Claude, and similar tools under an AI Assistant channel. Those are meaningful product changes because they give marketers official visibility into behavior that previously disappeared into referral clutter or anecdotal prompt testing. The trap is treating those new signals as if they solve attribution. They do not. Search Console can show that a page appeared in a generative AI feature. GA4 can show that a session arrived from an AI assistant. Neither can fully show what a buyer saw before clicking, whether an assistant retrieved a page without citing it, whether a competitor was recommended more strongly, or whether the buyer returned later through brand search, paid search, direct traffic, or a sales referral. Good AI visibility reporting does not pretend the fog is gone. It gives the fog structure. The first mistake is naming one number “AI visibility” and letting everyone assume it answers the same question. A founder may hear “AI visibility” and think, “Do we show up when someone asks for vendors like us?” A content lead may hear it and think, “Are our pages cited?” A RevOps leader may hear it and think, “Are these leads entering the pipeline?” A paid media leader may hear it and think, “Can I optimize toward this audience?” Those are related questions, but they are not the same question. A useful AI visibility dashboard should separate at least seven states: 1. **Ranking:** A page appears in classic organic search. 2. **Retrieval:** An AI system accesses, considers, or uses a page during answer generation. 3. **Citation:** An AI result links to or cites a page. 4. **Mention:** An AI result names the brand without necessarily citing it. 5. **Recommendation:** An AI result presents the brand as a suggested option. 6. **Referral:** A user clicks from an AI assistant or AI search surface. 7. **Business response:** A user becomes an engaged visit, qualified lead, sales-accepted opportunity, or customer. A page can rank without being cited. A page can be retrieved without being cited. A brand can be mentioned without a source link. A source can be cited without the brand being recommended. A brand can be recommended without a click. A recommendation can create later branded search. A branded search can convert through paid, direct, organic, or sales-assisted paths. Teams evaluating [generative engine optimization services](https://withsurface.com/blog/generative-engine-optimization-services) should expect this level of separation. A pile of screenshots can show presence. It cannot prove incrementality. A citation count can show that a source is being used. It cannot automatically tell you whether that source changed a buyer’s mind. Classic rankings still matter because they remain one of the clearest signals of topical authority, crawlability, and user demand. They also still influence AI visibility in many systems. A strong organic page has a better chance of becoming an answer source than a buried page with weak structure, stale evidence, and no surrounding topical support. The problem is that rankings and AI citations do not map cleanly enough to treat one as a substitute for the other. Ahrefs research has found meaningful overlap between Google AI Overview citations and organic results, but the overlap is partial. Some cited URLs appear in top organic positions. Others do not. Separate Ahrefs research on ChatGPT citations also distinguishes between retrieved URLs and cited URLs, which matters because a page can be considered by a system without appearing in the final answer. That changes the reporting model. Ranking reports still belong in the dashboard, but they should sit beside citation reports, mention reports, prompt-set results, AI referral sessions, and lead quality outcomes. Rankings tell you whether your content is discoverable in classic search. Citations and recommendations tell you whether your content or brand is being reused in answer environments. Referrals and lead quality tell you whether any of that visibility is turning into useful business behavior. Thinking about [query fan-out in Google AI search](https://withsurface.com/blog/query-fan-out-in-google-ai-search-how-marketers-should-build-con) helps here because one buyer question may expand into several hidden subquestions. A prompt like “best customer support AI platforms for enterprise teams” may fan out into questions about integrations, security, multilingual support, implementation timelines, pricing, competitors, customer proof, and technical architecture. A single ranking page rarely answers all of that well. The practical point is simple: report the surface area, not just the head term. A single AI answer can be useful as a screenshot, a sales conversation starter, or an early warning sign. It should not be treated as a measurement system. AI systems vary by model, query phrasing, location, account state, timing, retrieval behavior, and product interface. One prompt on one day can produce a confident-looking answer that disappears the next week. Another prompt with slightly different wording can surface a different competitor set. A branded query can make a company appear strong while neutral category prompts show that the same company is almost absent. The better approach is prompt-set tracking. Build a small but durable panel of prompts that reflects real buyer behavior: - Broad category prompts - Vendor shortlist prompts - Competitor comparison prompts - Problem-led prompts - Implementation prompts - Pricing and ROI prompts - Risk and objection prompts - Integration prompts - Persona-specific prompts - “Best tool for…” prompts Then run those prompts repeatedly across relevant systems. Track presence, rank within the answer, citation source, recommendation language, competitor mentions, and the supporting pages or sources used. The report should show patterns over time rather than one-off wins. A strong AI visibility report might say: “Across 40 non-branded prompts, the brand appeared in 12 answers, was recommended in 5, and cited directly in 3. Competitor A appeared in 22, Competitor B in 18. Our strongest visibility came from implementation and integration prompts. Our weakest visibility came from pricing and comparison prompts.” That is useful. It tells the team what to build next. A weak report says: “ChatGPT mentioned us.” Marketers do not need to pretend every metric has the same confidence level. In fact, the report becomes more trustworthy when it says what each metric can and cannot prove. Use confidence labels like: - **Observed:** Directly visible in a platform or report. - **Repeated:** Seen across multiple prompt runs or dates. - **Directional:** Suggestive, but not proven causally. - **Modeled:** Calculated from a scoring system or proxy. - **Unattributed:** Business outcome may have AI influence, but no direct path confirms it. - **Experimental:** Based on a controlled test or structured comparison. - **Unsettled:** Too early, too variable, or too small a sample to interpret confidently. For example, “GA4 AI Assistant sessions increased 38% month over month” is observed. “AI visibility caused pipeline to increase” is usually not observed. At best, it may be directional, modeled, or experimental depending on the evidence behind it. Teams using an [AI visibility dashboard](https://withsurface.com/blog/generative-engine-optimization-services) should keep those labels visible. Caveats do not weaken the dashboard. They keep the dashboard from becoming a prettier version of wishful thinking. AI visibility becomes operational when it connects to buyer behavior. A cited page that attracts the wrong audience is not automatically valuable. A low-volume AI Assistant channel that produces sales-ready demo requests may be highly valuable. A brand that appears in recommendations but receives no qualified follow-up may have a positioning problem, a conversion problem, or a proof problem. That is why AI visibility reporting should connect to [lead journey tracking](https://withsurface.com/blog/lead-user-journey), not just citation monitoring. Look at what AI-referred visitors actually do. Do they view pricing? Do they open comparison pages? Do they inspect integrations? Do they read case studies? Do they return through branded search later? Do they become sales-accepted? Do they ask better questions on calls? A practical reporting layer might include: - AI Assistant sessions by source - Engagement rate for AI-referred sessions - Key page views after AI referral - Demo conversion rate - Branded search movement - Returning visitor rate - Sales acceptance rate - Opportunity creation rate - Closed-won influence, where available - Prompt visibility for pages that assisted conversion This is where [how to actually measure lead quality](https://withsurface.com/blog/how-to-actually-measure-lead-quality-not-just-lead-volume) matters. If a company only rewards lead volume, AI visibility will be dragged toward the same old vanity logic. If a company measures sales usefulness, fit, urgency, and pipeline quality, AI visibility can become part of a more honest demand system. ## Report source mix, not just owned content AI visibility is not only an owned-site problem. AI systems may draw from company pages, blogs, documentation, review sites, partner pages, news articles, forums, videos, social profiles, analyst coverage, marketplaces, and comparison content. A brand’s answer-engine presence is partly created by the public ecosystem around it. That means the report should include source mix. For each prompt category, identify whether the brand appears through: - Owned website pages - Blog or educational content - Documentation or help center content - Third-party reviews - Partner pages - Press coverage - Analyst or industry reports - Community discussions - YouTube or video sources - Social or creator content - Marketplace listings This matters because different weaknesses require different actions. If owned pages are cited but third-party proof is weak, product marketing may need more customer evidence and partner reinforcement. If review sources dominate but product pages are absent, SEO and content architecture may need work. If competitors appear through category articles and you do not, the issue may be off-site authority rather than page quality alone. AI visibility visuals should emphasize coverage, freshness, evidence, clarity, source mix, authority, and business relevance rather than raw volume. That principle matters because more pages do not automatically create more trust. A smaller set of current, specific, well-supported pages can often do more than a bloated archive full of thin explanations. A good cadence keeps the work from becoming either too reactive or too ceremonial. Weekly reporting should focus on operational signals: prompt-set changes, new competitor appearances, AI Assistant traffic movement, notable citations, obvious missing pages, and sales feedback from AI-influenced leads. Monthly reporting should focus on trend quality: presence across prompt categories, source mix, page-level visibility, branded search movement, lead quality, content refreshes, and competitor share of voice. Quarterly reporting should focus on strategy: which content clusters deserve investment, which proof assets are missing, which product claims need better evidence, which third-party sources matter, and whether AI-influenced demand is becoming more commercially relevant. The goal is not to create another dashboard no one reads. The goal is to create a reporting rhythm that tells content, product marketing, paid media, RevOps, and sales what to do next. Start by defining the metric states. Ranking, citation, mention, recommendation, referral, and revenue influence should each have their own definition. Then build a prompt set around buyer intent. Do not only test branded prompts. Include neutral category prompts, competitor prompts, implementation prompts, comparison prompts, and risk prompts. Next, connect AI visibility to analytics. Use GA4’s AI Assistant channel where available. Monitor Search Console generative AI reporting where available. Compare AI-referred sessions against organic, paid, direct, and referral sessions. Then add business interpretation. Which AI-visible pages support qualified journeys? Which cited pages fail to convert? Which prompt categories expose missing proof? Which competitors appear because they have stronger third-party source coverage? Finally, make uncertainty visible. Label directional claims as directional. Label modeled scores as modeled. Label small samples as small samples. Marketing teams do not need perfect certainty to make better decisions. They do need enough honesty to avoid optimizing around the wrong story. AI visibility reporting is finally becoming possible. That is good news. It is also the moment when measurement discipline starts to matter more, not less. - Google Search Central: Search Generative AI performance reports in Search Console - Google Analytics: AI Assistant channel grouping - Ahrefs: AI Overview citation studies and ChatGPT citation research - arXiv: “Don’t Measure Once,” a methodological paper on repeated GEO measurement - arXiv: Research on separating answer-engine optimization effects from broader platform growth - Surface: [Generative engine optimization services](https://withsurface.com/blog/generative-engine-optimization-services) - Surface: [Lead journey tracking](https://withsurface.com/blog/lead-user-journey) - Surface: [How to actually measure lead quality](https://withsurface.com/blog/how-to-actually-measure-lead-quality-not-just-lead-volume) - Surface: [Query fan-out in Google AI search](https://withsurface.com/blog/query-fan-out-in-google-ai-search-how-marketers-should-build-con) --- # Pull Live CRM Data Into Your Forms | Surface Labs URL: https://surface.thesurface.network/blog/api-based-logic _Surface lets you make real time API calls inside your form logic so the form can pull live data from your CRM, product database, or any external system and adapt accordingly._ Most forms are static. They collect the same fields in the same order regardless of who the prospect is or what your systems already know about them. If you want the form to check whether someone is an existing customer, verify an account tier, or validate a discount code, that logic has to live outside the form in a separate backend your engineering team builds and maintains. That means forms can't react to live data. They collect information, pass it downstream, and let your team figure out what to do with it after the fact. Surface lets you configure API calls directly in the Logic tab. You specify the endpoint URL, request method, headers, and parameters. When a prospect reaches a certain step or enters specific information, Surface triggers the call and uses the response to control what happens next. The API call runs in milliseconds while the prospect is still on the form. They don't experience any delay or interruption. Surface uses API responses to control form behavior and routing in real time. A few examples: API call What happens in the form Check if email exists in your CRM Show returning customer flow instead of new sales Pull account tier from your product database Adjust questions and routing based on their plan Verify company domain against a blocklist Block the submission or flag for review Validate a discount code against your billing system Confirm or reject the code inline Check account balance or subscription status Display personalized next steps based on their account The form adapts dynamically based on live data from your systems, not just static rules. If the API confirms someone is an existing customer, route them to account management. If it returns enterprise tier information, adjust the qualification path accordingly. Without API integration, forms are disconnected from the rest of your stack. They can't check your CRM, can't verify account data, and can't personalize the experience based on what you already know about a prospect. With it, the form becomes an extension of your systems. It pulls live data, makes decisions, and routes leads based on real account information, all before the prospect finishes filling it out. **Can I connect any API to Surface forms?** Yes. Any external API that accepts HTTP requests can be integrated. You configure the endpoint, method, headers, and parameters in the Logic tab. **Do API calls slow down the form?** No. API calls run in milliseconds in the background. The prospect doesn't experience any delay. **What can I do with the API response?** You can use it to control branching, change which questions appear, adjust routing, display personalized content, or block submissions based on the returned data. **Do I need engineering support to set this up?** You need to know the API endpoint and authentication details, but the configuration itself is done through Surface's visual Logic tab. No code inside the form. **Can I chain multiple API calls in one form?** Yes. Different steps in the form can trigger different API calls, each using their own endpoints and parameters. --- # Are Marketing Agencies Going to Die? | Surface Labs URL: https://surface.thesurface.network/blog/are-marketing-agencies-going-to-die Short answer: no. But the agencies that survive will look nothing like the agencies that exist today. The AI anxiety in the agency world is real. When a founder can generate ad copy with Claude, build landing pages with AI-assisted tools, and set up basic automation without a dedicated ops person — the obvious question is: what do I need an agency for? It's the right question. And the answer is more nuanced than either "agencies are dead" or "agencies will be fine." AI isn't replacing agencies. It's replacing the commodity services that many agencies have built their revenue on. Service Status Why **Ad copy and creative** Commoditizing fast AI generates decent first drafts. The gap between AI-generated and agency-generated copy is shrinking monthly. **Basic landing pages** Commoditizing Template-based builders + AI content = good-enough landing pages without agency involvement. **Email sequence writing** Commoditizing AI writes solid nurture emails. The strategy behind them still requires expertise, but the execution doesn't require an agency. **Social media management** Partially commoditizing Scheduling and basic content creation are automatable. Community management and brand voice still need humans. **Reporting and dashboards** Commoditizing AI can pull data, build dashboards, and summarize performance. The insight extraction still needs a strategist, but the assembly doesn't. **Campaign strategy** Not yet AI can suggest tactics but can't evaluate market position, competitive dynamics, or business context the way an experienced strategist can. **Lead ops and conversion optimization** Not at all This requires understanding a client's specific sales process, CRM architecture, routing logic, and funnel mechanics. AI tools help but can't replace the diagnosis and implementation. The agencies most at risk are the ones selling execution — the deliverables (copy, pages, emails) that AI can now produce at 80% quality for 10% of the cost. The agencies least at risk are the ones selling outcomes — strategy, implementation, and measurable improvement in metrics that matter. The agencies that thrive will shift from selling hours and deliverables to selling results and infrastructure. **From content production to conversion engineering.** Instead of "we'll write your blog posts and emails," the value proposition becomes "we'll fix your lead flow so 30% more of your leads become meetings." The output isn't content — it's a measurable improvement in a business metric. **From campaign management to systems architecture.** Instead of managing ad campaigns and reporting on impressions, agencies build and optimize the infrastructure between the ad click and the sales conversation. Capture, qualification, routing, and response — the layer most companies can't build themselves and AI tools can't configure automatically. **From retainer-based to outcome-based.** When the deliverable is "more meetings" or "lower cost per meeting," pricing can be tied to outcomes instead of hours. This is harder to scope but more defensible — because the client pays for results, not time. Most B2B companies between $5M and $50M in revenue don't have the internal ops resources to build a proper lead operations system. They have a marketing team running campaigns, a sales team working leads, and a gap between them filled with duct tape. Agencies that can diagnose and fix that gap — using tools like Surface to implement capture, qualification, routing, and instant response — deliver immediate, measurable value that AI can't replicate. The diagnosis requires understanding the client's specific business. The implementation requires configuring systems to match their sales structure. The optimization requires ongoing analysis of conversion data. This is consultative, technical, high-value work. It's the opposite of commodity content production. And it's the kind of work that makes clients stay for years, not months. \[IMAGE: A simple before/after. Left side: "Old agency model" — Content production, Campaign management, Monthly reporting, Retainer-based. Right side: "New agency model" — Conversion engineering, Systems architecture, Real-time metrics, Outcome-based. White background, blue (`#4F6DF5`) accent, flat design.\] Surface gives agencies a platform to deliver lead ops as a service. Instead of recommending that clients fix their own capture and routing, agencies can implement Surface across their client portfolio — configuring qualification, routing, and response for each client's specific sales process. For agencies looking to move upmarket from commodity services, lead ops infrastructure is the highest-value, most defensible offering available. Surface is the tool that makes it deliverable. --- # Attribution Is Not Incrementality: How to Measure AI Creative Without Fooling Yourself | Surface Labs URL: https://surface.thesurface.network/blog/attribution-is-not-incrementality-how-to-measure-ai-creative A paid media team launches forty AI-generated ad variations. The platform identifies several winners. Click-through rate improves. Cost per lead falls. Attributed conversions rise. The campaign report looks good enough that the team increases the budget and adds another round of generated creative. Three months later, the sales team has a different report. Lead quality has softened. Several prospects misunderstood what the product did. Branded search absorbed more paid spend. Organic conversions declined as paid conversions rose. The company acquired more names while creating roughly the same number of qualified meetings. Both reports can be accurate. The platform can correctly report that its ads appeared before a set of conversions. Sales can correctly report that the business did not gain enough additional demand to justify the apparent improvement. The disagreement comes from two measurement questions being treated as though they were one. Attribution asks where credit should be assigned. Incrementality asks what would have happened without the marketing activity. AI creative makes this distinction more important because marketers can now generate more variations, activate them faster, and let platforms optimize across a larger field of messages. That produces more data, more credited interactions, and more opportunities for a dashboard to look conclusive before the business impact is clear. Marketing attribution tries to connect a conversion to the touchpoints that preceded it. A buyer might encounter a creator video, see an AI-generated display ad, ask an assistant about the category, search the company’s name, click a paid search result, return through direct traffic, and request a demo. Different attribution systems can distribute credit across those interactions in different ways. Last-click attribution may credit paid search. First-touch attribution may credit the creator video. A multi-touch model may divide credit across several channels. A platform-specific model may assign most of the value to the activity visible inside that platform. Each model tells a story about the path. None of them automatically proves which activity changed the outcome. A June 2026 AdExchanger analysis of a proposed W3C advertising measurement standard criticized the tendency to describe attribution as evidence of advertising effectiveness. Its central argument was that observational pathway analysis should not be confused with causal proof of incremental business impact. That distinction is easy to understand in theory and surprisingly easy to lose inside a campaign report. Incrementality compares an observed outcome against a counterfactual. The counterfactual is the result that would likely have occurred if the campaign, channel, creative, discount, or marketing intervention had not happened. Suppose a campaign receives credit for 1,000 conversions. That does not mean it created 1,000 additional conversions. Some buyers may have converted organically. Some may have searched for the brand regardless of the ad. Some may have clicked a paid result because it occupied the easiest path to a company they had already decided to investigate. Incrementality tries to estimate the difference between: - What happened with the marketing activity - What would have happened without it That difference is the incremental lift. The distinction matters most when channels overlap heavily with existing demand. A June 25, 2026 research paper titled _Attributed, But Not Incremental_ argues that paid-attributed conversions can systematically overstate incremental growth when paid activity overlaps with organic demand, brand traffic, or other acquisition channels. The researchers propose using incrementality experiments as causal anchors to correct attribution estimates and report that a deployment across several TikTok markets was followed by an approximately 15-percentage-point reduction in measured cannibalization. The result is specific to that system and should not be treated as a universal advertising benchmark, but the measurement problem is broadly relevant. A conversion can belong in the attribution report while adding little incremental value. AI creative systems can generate more copy, images, videos, campaign combinations, audience adaptations, and landing-page variants than most teams could produce manually. This creates legitimate opportunities. A team can test more messages. It can respond to market changes quickly. It can explore different formats without waiting weeks for every variation. Smaller teams can run a broader creative program. It also expands the amount of marketing activity competing to claim the same demand. Consider a buyer who already knows the brand. They see three generated retargeting ads, click one, and convert. The ad platform records a conversion. The campaign appears successful. Incrementality asks whether the buyer needed the ad or whether the system placed itself near a decision that was already underway. The same issue can appear in branded paid search. An AI assistant recommends the company. The buyer later searches for the brand, clicks the sponsored result above the organic listing, and submits a form. Paid search receives attribution. The original recommendation may remain invisible. The sponsored click may have protected the conversion, accelerated it, or simply charged the company for traffic it was likely to receive anyway. Surface’s analysis of how [AI search ads are moving faster than reporting](https://withsurface.com/blog/ai-search-ads-are-moving-faster-than-reporting-what-paid-media-t) describes why answer interfaces make these paths harder to interpret. AI-mediated discovery can shape awareness and consideration before the buyer enters a channel the analytics stack recognizes. The final click may be the clearest event in the data and the least important event in the decision. AI creative systems are often evaluated through platform metrics: - Impressions - Click-through rate - Cost per click - Conversion rate - Cost per lead - Attributed revenue - Platform ROAS These metrics are useful for campaign operations. They tell marketers whether the system is finding responses efficiently inside the observable environment. They can hide what happens after the response. A creative angle may produce cheap leads because it makes an expansive promise. The promise can attract people who are curious, underqualified, or expecting functionality the product does not provide. The platform sees a form submission. Sales sees a conversation that never should have happened. This is why teams should connect campaign reporting to [lead quality rather than lead volume](https://withsurface.com/blog/how-to-actually-measure-lead-quality-not-just-lead-volume). Surface recommends looking beyond total leads and cost per lead toward lead-to-conversation rate, lead-to-meeting rate, cost per meeting, source-level conversion, sales acceptance, and pipeline outcomes. Those measures expose whether marketing activity is producing useful business motion rather than inexpensive database growth. The message that wins the ad auction may lose the sales call. Attribution still has an operational job. Teams need to understand which campaigns, pages, sources, and messages appear in converting journeys. They need to diagnose broken tracking, compare audience segments, optimize placements, and understand how people move through the conversion system. An [inbound marketing automation system](https://withsurface.com/blog/inbound-marketing-automation) also depends on path-level data. Marketers need to know which form, campaign, content asset, and use case brought a lead into the system so they can qualify, route, and follow up appropriately. Incrementality answers a different level of question. Attribution question Incrementality question Which channel received credit? Did the channel create additional demand? Which ad appeared before conversion? Would the conversion have happened without the ad? Which campaign produced the lead? Did the campaign improve total qualified pipeline? Which creative had the best platform ROAS? Which creative produced genuine lift after cannibalization? Which page assisted the journey? Did the page change conversion behavior? Where should daily optimization occur? Where should the company allocate additional budget? Attribution helps operators navigate the system. Incrementality helps leaders decide whether the system is adding value. No single model is likely to explain the entire buyer journey. Marketing mix modeling can help estimate channel-level contribution over time, but it may be too broad for daily campaign decisions. Multi-touch attribution provides greater granularity, but privacy changes and incomplete tracking can weaken its reliability. A June 2026 research paper on Integrated Marketing Attribution proposes combining MMM-informed priors with channel-specific Bayesian attribution models to derive campaign-level effects from aggregated data. The framework reflects a wider measurement direction: marketers are trying to preserve actionable detail while grounding it in more robust channel-level estimates. Most B2B teams will not build that exact model. They can still use the principle. Measurement becomes stronger when teams triangulate several forms of evidence: ### Attribution data Shows the observable path, campaign interactions, credited sources, and conversion events. ### Business-quality data Shows lead fit, conversations, meetings, sales acceptance, opportunities, pipeline, retention, and expansion. ### Incrementality experiments Use holdouts, randomized tests, geo experiments, audience suppression, or matched markets to estimate causal lift. ### Marketing mix or modeled contribution Estimates broader channel impact where individual journeys cannot be observed cleanly. ### Brand and demand signals Includes branded search movement, direct traffic, share of search, message recall, returning visitors, and category consideration. ### Qualitative evidence Includes sales-call language, customer interviews, buyer questions, creator feedback, and recurring objections. The methods will disagree occasionally. That is healthy. A measurement system should reveal uncertainty rather than forcing every source into one confident number. AI-era reporting needs clearer evidence labels. Surface’s [new brand measurement layer](https://withsurface.com/blog/june-21-26-the-new-brand-measurement-layer) argues that AI visibility is becoming measurable before it becomes cleanly measurable. A buyer can encounter a recommendation, later search the brand, click an ad, and convert without leaving a complete trace of the original influence. The same evidence framework works for AI creative and paid media. ### Observed The event appears directly in the available data. Examples: - The campaign generated 300 attributed leads. - Cost per lead fell by 18%. - Forty leads booked meetings. - AI-referred sessions viewed the pricing page. - Sales acceptance increased for one message family. ### Inferred Several signals suggest a relationship, but the team has not proven causality. Examples: - Branded search increased after a creator campaign. - Prospects began repeating language from a new creative concept. - Direct traffic rose during an AI visibility campaign. - A new message may have improved lead understanding. ### Modeled A statistical model estimates contribution under documented assumptions. Examples: - MMM estimates a range of channel-level incremental revenue. - A calibrated attribution model reallocates credit across campaigns. - A propensity model estimates expected conversion without exposure. ### Tested A controlled experiment supports a causal conclusion. Examples: - A geographic holdout showed incremental qualified pipeline. - Suppressing retargeting for a control group did not reduce conversions. - A message test improved lead-to-meeting rate rather than only form completion. ### Unresolved The available evidence cannot support a confident conclusion. Examples: - Attribution improved while total pipeline stayed flat. - Branded search rose alongside several overlapping campaigns. - Sample size was too small to detect useful lift. - Tracking loss prevents a defensible estimate. “Unresolved” is a useful business answer. It keeps a directional signal from hardening into a budget decision before the evidence can support it. Incrementality testing can sound like a project reserved for companies with enormous budgets and specialized data-science teams. Some tests do require scale. Others can begin with narrow, practical decisions. ### Branded paid search tests Where risk allows, use geographic or audience holdouts to understand how many branded paid conversions are genuinely incremental versus captured organic demand. ### Retargeting suppression Remove a portion of eligible users from retargeting and compare qualified conversion behavior. This can reveal whether the campaign creates lift or repeatedly claims people already returning. ### Message-quality tests Compare creative concepts using lead-to-meeting rate, sales acceptance, and opportunity quality. Avoid declaring a winner solely from click or form conversion. ### Creator or expert campaign tests Use matched audiences, pre/post branded search analysis, survey lift, or controlled paid amplification to estimate whether creator exposure changes awareness or consideration. ### Landing-page proof tests Add customer evidence, implementation detail, or clearer limitations to a test group of pages. Measure qualified conversion and sales understanding alongside page conversion. ### Speed and routing tests Test whether improved follow-up and routing create more value from existing demand before spending more to generate additional leads. The best first test usually sits near a large budget decision, a disputed channel, or a metric that looks excellent while business results remain unclear. AI creative production should connect media performance to the rest of the funnel. The feedback loop should move through five stages: 1. **Creative system:** Which message and format were shown? 2. **Media response:** Who clicked, viewed, or converted? 3. **Lead operations:** Was the lead qualified, enriched, routed, and contacted? 4. **Sales response:** Did the conversation progress? Did expectations match reality? 5. **Business result:** Did the activity create incremental meetings, pipeline, revenue, or retention? Most creative systems receive strong feedback from stages one and two. They receive much weaker feedback from stages three through five. That imbalance encourages platforms to optimize for events they can observe, even when those events have a loose relationship to business value. Marketers should send richer outcome data back where possible and review message performance outside the ad platform. Creative teams need to know which promises produce good customers. Paid teams need to know which cheap leads waste sales time. RevOps needs to know which source and message combinations move into pipeline. Sales needs enough campaign context to explain why expectations are breaking. The marketing system becomes smarter when the definition of success survives the form submission. AI will create more marketing material. It will also create more opportunities for attribution systems to award credit to activity that sat near a conversion. Some of that activity will create genuine lift. Some will capture demand already in motion. Some will protect existing demand. Some will add useful frequency. Some will cannibalize organic channels. Some results will remain unresolved. The dashboard should preserve those distinctions. Use attribution to understand the path. Use lead quality to understand whether the path produced something useful. Use incrementality to understand what marketing changed. Use models where experiments are impossible, and state the assumptions. Use experiments where the decision is important enough to deserve causal evidence. AI creative can help teams move faster. Better measurement keeps that speed from carrying the budget in the wrong direction. --- # B2B Digital Lead Generation: Build a System From Search Traffic to Qualified Conversations | Surface Labs URL: https://surface.thesurface.network/blog/b2b-digital-lead-generation-build-a-system-from-search-traffic B2B digital lead generation sounds simple on a slide. Attract the right people, offer something useful, collect their information, turn the reply into a conversation. Each verb hides a different system, owner, tool, and failure point. Traffic can be weak because the message is generic. Traffic can be strong and still mismatched. A landing page can convert one segment and confuse the next. A form can ask the wrong questions. A qualified buyer can wait hours for a reply while a slower competitor books the meeting instead. Sales can receive a name with no sense of what that person was actually trying to solve, and the lead count on the dashboard can keep climbing while the system underneath quietly leaks value. We built Surface to close that gap. It connects the search that brought a buyer in, the content they land on, the form they fill out, and the rep who follows up into one system that learns from every outcome it produces. Here is how the full path fits together. ## Map the actual entry points A prospective customer can reach the company through organic search, AI answers, paid search, paid social, partner referral, review sites, events, product usage, or a direct visit. Each of those carries a different kind of intent. None of them should be forced into one generic "website visitor" bucket just because they eventually hit the same form. A returning visitor from a named account behaves differently than a cold click from a paid social ad, even when both land on the same page. Our Traffic Intelligence layer is built to preserve that difference instead of erasing it, pairing session and channel data with the buyer signals already sitting in the Lead Data Layer so the site can tell a warm return visit from a first-touch stranger before either one ever reaches a form. ## Build demand with content that AI systems can also find Search content remains one of the most durable sources of B2B demand because it meets a buyer at the exact moment of a question. That takes more discipline than publishing a list of keyword posts. Topics need to reflect real business priority and connect to something the company can actually deliver. Build clusters, not isolated posts. We call this a five-layer system in our [2026 content marketing guide](https://withsurface.com/blog/content-marketing-guide-2026) — visibility, trust, conversion, distribution, and measurement — where definitions, practical guides, comparisons, and product detail all link around one buyer problem instead of standing alone. This is where our Content & SEO Agents and AI Visibility Agents work together. One researches a topic and produces a ready-to-review content campaign in well under the time a manual brief-and-draft cycle takes. The other tracks how the brand actually shows up across AI answer engines every day, so a content team is optimizing for how buyers now search, not just how they searched three years ago. [Google's May 2026 guidance on generative AI Search](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) confirms the same point from a different angle: AI visibility still rests on crawlable pages, useful content, and evidence a system can retrieve with confidence, not on separate AI-only tricks. Paid media then extends the system: capturing high-intent search behavior, testing messages, and returning informed visitors to a page that was built for the question they asked. It should never compensate for a vague offer or a broken conversion path. ## Design conversion pages around the click, not the org chart A buyer arriving from a research guide needs a different page than one searching for a named solution. We make this point in our [guide to landing pages and conversion](https://withsurface.com/blog/what-makes-a-good-landing-page-why-blogs-need-conversion-pages): a blog earns interest, but the landing page decides whether the reader believes a conversation is worth having. The page should keep the promise that got the click — the problem, the audience, the mechanism, the proof, and one clear next step. The form has to match that promise. Our Dynamic Lead Forms adjust the questions asked based on what the visitor has already revealed, and partial-response capture saves a submission the moment someone starts typing, so a dropped session still becomes a usable record instead of nothing. Once a meeting is the right next step, Intelligent Scheduling books it without another round of "does Tuesday work." Nextiva used this combination to lift conversion by 37% and collect 70% more email addresses from the same traffic — proof that the form itself, not just the campaign feeding it, decides how much of that traffic actually turns into pipeline. A form submission is a new piece of operational information, not a trophy for marketing to count and hand off. Our Lead Data Layer unifies that submission with enrichment, prior site behavior, product usage, and account context into one record. From there, Lead Agents can research and qualify a lead in seconds rather than the hours a manual SDR pass would take, scoring it against an ICP defined in plain language instead of a static point system nobody trusts. Enterprise accounts route to an AE. Existing customers route to success. Early researchers go to nurture. Our [guide to lead capture and routing for B2B SaaS](https://withsurface.com/blog/lead-capture-and-routing-for-b2b-saas-companies) shows why segment, product interest, and account status all change the right answer — the rules vary by company, but the discipline should not. GovSpend stood this up across 22 territories in twelve days and saw roughly a 154% lift in effective leads from the same traffic, simply by giving the existing volume somewhere smarter to go. Juicebox used the same layer to absorb a viral traffic spike without adding headcount, saving more than 50 hours of manual routing work a week. Nurture earns a bad reputation because most programs amount to a reminder sequence that the company still exists. Better nurture follows the actual question a buyer left unresolved. Our System Agents draw on shared marketing context — what a buyer has already read, asked, or been told — so the next message picks up that thread instead of restarting it. Numbers Station used this closed loop to grow pipeline by 30%, with 95% of leads enriched automatically before a rep ever touched the record. Reporting should show the entire sequence: qualified traffic, conversion, qualification, routing time, first response, meetings, and the revenue that eventually closes. Reviewed by channel and offer, that view surfaces problems a single cost-per-lead number hides — a channel with fewer conversions but stronger meetings, a form that converts well but starves sales of context, a fast campaign undone by a slow reply. Our [guide to attribution and incrementality](https://withsurface.com/blog/attribution-is-not-incrementality-how-to-measure-ai-creative) is a useful check on that report: a channel can look strong in attribution while adding little real lift, so our revenue feedback signals feed tested and modeled outcomes back into the system, not just credited ones — so the next content brief, ad variant, or routing rule starts smarter than the last one instead of from a blank template. B2B digital lead generation is not a channel decision. It is the ability to turn one useful encounter into a qualified conversation without losing the thread along the way. Build that system first. Then send more traffic into it. --- # B2B Lead Conversion Benchmarks for 2025 | Surface Labs URL: https://surface.thesurface.network/blog/b2b-lead-conversion-benchmarks-for-2025 Most B2B marketing teams chase more traffic when the real opportunity sits in front of them: converting visitors they already have. If your site gets 10,000 monthly visitors at a 2% conversion rate, that's 200 leads. Push that to 3%, and you've added 100 leads per month without spending another dollar on ads. The gap between average and high-performing B2B conversion rates comes down to systematic optimization across forms, lead capture, qualification, routing, and follow-up. This guide breaks down exactly how to improve your B2B website conversion rate using strategies that deliver 30-50% lifts in under two weeks. B2B conversion rate optimization is the process of increasing the percentage of website visitors who complete a desired action—filling out a demo request form, booking a meeting, downloading a resource, or starting a free trial. Unlike B2C, B2B CRO accounts for longer buying cycles, multiple stakeholders, and higher-value transactions that require trust and proof at every step. According to First Page Sage's 2026 analysis of B2B conversion benchmarks, the median B2B conversion rate is 2.9%, with legal services topping the charts at 7.4%. B2B SaaS companies typically see visitor-to-lead rates around 1.5-2.5%, while top-performing companies consistently hit 8-15% conversion rates on demo request forms—a 3-5x difference from the average. The basic formula: **Conversion Rate = (Conversions ÷ Total Visitors) × 100** If your landing page received 1,000 visitors and 45 filled out your demo form, your conversion rate is 4.5%. Track conversions at multiple funnel stages to identify where you're losing leads: - **Visitor-to-lead rate** (form submissions) - **Lead-to-MQL rate** (qualification) - **MQL-to-meeting rate** (booked demos) - **Meeting-to-opportunity rate** (pipeline creation) Most teams focus only on top-of-funnel metrics and miss the breakage happening after form submission, where 30-40% of leads are lost to slow routing, poor qualification, or no follow-up. ### 1\. Replace static forms with intelligent multi-step forms Traditional single-page forms with 8+ fields create massive friction. [Multi-step forms](https://withsurface.com/blog/you-re-setting-up-your-forms-the-same-way-you-did-in-2020.-that-s-a-problem.) break the process into digestible chunks, reducing cognitive load and improving completion rates by 20-30%. More importantly, intelligent forms capture **partial submissions**—email addresses and contact data from visitors who start your form but don't click submit. Research from Insiteful shows that 81% of users abandon forms after starting them, meaning you could be losing four out of every five potential leads without [partial capture](https://www.withsurface.com/blog/what-most-lead-capture-tools-get-wrong). A Venture Harbour study found multi-step forms convert 86% higher than single-page equivalents, while some implementations documented conversion increases by up to 300%. The Zeigarnik effect—our psychological tendency to complete tasks we've started—drives users through sequential steps more effectively than confronting them with all fields at once. Modern lead capture forms include: - Progressive profiling that asks different questions to returning visitors - Built-in qualification questions (company size, budget, timeline) - Real-time enrichment to auto-fill company and role data - Partial submission capture to recover abandoned form data - Immediate routing and follow-up automation Nextvia increased conversions by 37% simply by switching to a multi-step form that captured partial data and reduced initial friction. ### 2\. Add qualification at the point of capture Bad leads waste sales time and tank your conversion metrics. The solution isn't more post-submission filtering—it's [building qualification into your forms](https://www.withsurface.com/blog/how-to-qualify-leads-in-real-time-without-manual-work) before leads enter your pipeline. High-performing teams ask 3-4 qualification questions right in the form: - Company size or revenue range - Current solution or tech stack - Timeline to purchase - Budget or buying authority This serves two purposes: it filters out genuinely unqualified leads at capture, and it arms sales with the context they need to prioritize and personalize outreach. Lead scoring happens in real time, routing hot leads immediately and sending lower-intent contacts to nurture. According to Landbase's 2026 lead qualification research, properly scored and qualified leads achieve 40% conversion rates versus 11% for unqualified prospects. Companies using automated lead qualification see an average 20% increase in lead conversion rates and 10% or greater revenue growth within 6-9 months. ### 3\. Implement speed-to-lead automation Speed-to-lead is the single strongest predictor of conversion. According to Kixie's 2025 research, responding within 60 seconds can boost conversions by 391%, while Harvard Business Review found the odds of qualifying a lead drop by 80% after the first 5 minutes. Yet the average B2B response time is 42-47 hours, with 55% of companies taking 5+ days or never responding at all. The data is clear: 78% of customers buy from the vendor who responds first. Speed compounds the advantage. The fix is automation: - **Instant lead routing** to the right sales rep based on territory, product fit, or account ownership - **Auto-scheduled meetings** embedded directly in forms or thank-you pages - **Immediate follow-up emails** with relevant case studies and next steps - **Enrichment and deduplication** to prevent spam leads from reaching sales calendars Kintsugi prevented fake leads from spamming their sales calendar and increased pipeline by 30% by automating enrichment, routing, and qualification in real time. ### 4\. Simplify your conversion path Every extra click, field, or navigation option between your visitor and your conversion goal costs you leads. High-converting B2B landing pages share these traits: - **Focused messaging:** One clear value proposition, not three competing offers - **Minimal form fields:** 3-5 essential fields only (name, email, company) - **Single call-to-action:** No competing CTAs or navigation that bleeds traffic - **Mobile-optimized design:** 80% of B2B buyers use mobile during their purchasing journey, and mobile-optimized sites report a 20% increase in conversions - **Fast load times:** Sites that load in 1 second convert 3x better than those taking 5 seconds. Each additional second of delay drops conversions by an average of 4.42% Remove navigation bars on dedicated landing pages. Strip out sidebar CTAs. If the goal is a demo booking, make that the only action available. The conversion gap between desktop (3.9%) and mobile (1.53%) presents an opportunity: 61% of users won't return to a mobile site with poor usability, but fixing mobile experience can close that gap and unlock leads from the 50%+ of B2B queries conducted on smartphones. ### 5\. Use trust signals and social proof strategically B2B buyers need proof before they'll share contact information. Every conversion point should be reinforced with credibility markers: - **Customer logos** from recognizable brands in your target industry - **Quantified results** ("37% higher conversion" not "improved performance") - **Third-party validation** (G2 ratings, industry awards, certifications) - **Case studies** linked near CTAs showing similar company profiles - **Security and privacy statements** ("We never share your data" or GDPR compliance badges) Place social proof near the form or CTA, not buried at the bottom of the page. The moment of highest doubt is right before clicking submit—that's when trust signals matter most. With 29% of form abandonment driven by security concerns, visibility into your data practices can be the difference between a lost visitor and a booked demo. According to Genesys Growth's 2026 research, authentic, multi-format social proof—especially reviews and video testimonials—can boost B2B SaaS conversions by up to 270%. Companies displaying social proof see conversion rate increases of up to 34%. ### 6\. Capture partial form submissions automatically Over 76% of potential online sales are lost to form abandonment. Implementing partial capture can boost conversion rates by over 10% by capturing data as users type and enabling immediate follow-up. Partial form submission capture works by saving form field data in real time as visitors fill out forms—even if they never click submit. This turns abandoned forms into actionable leads. In our case studies at Surface Labs, websites that enabled partial submission capture increased conversion rates by over 10% simply by recovering leads who started but didn't complete forms. The data gets routed to your CRM automatically, triggering follow-up workflows to re-engage users within minutes of abandonment. ### 7\. Optimize for high-intent pages first Not all traffic is equal. Visitors on your pricing page, demo page, or product comparison pages convert at 3-5x higher rates than blog readers. Focus your optimization effort where intent is highest. **High-intent pages to prioritize:** - Demo request and pricing pages - Product pages and feature comparison pages - Case study pages (especially industry-specific) - Bottom-of-funnel content (ROI calculators, implementation guides) Run A/B tests on headlines, CTAs, form length, and proof placement on these pages before optimizing top-of-funnel content. A 10% lift on a pricing page with a 5% baseline conversion rate delivers more pipeline than a 20% lift on a blog post converting at 0.5%. ### 8\. Run continuous A/B experiments on forms and CTAs Conversion rate optimization isn't a one-time project—it's a continuous testing discipline. Top-performing B2B marketing teams run 4-8 experiments per quarter, testing: - **Form length** (3 fields vs. 5 fields vs. multi-step) - **CTA copy** ("Book a Demo" vs. "See How It Works" vs. "Get Started") - **CTA design** (button color, size, placement) - **Headline variations** emphasizing different benefits - **Proof placement** (case study above form vs. below form) The key is testing one variable at a time with statistically significant sample sizes. For a baseline 3% conversion rate, you need roughly 10,000 visitors per variation to detect a 20% lift with confidence. Use tools like Google Optimize, VWO, or Optimizely to manage experiments, and always link tests to revenue impact, not just conversion rate changes. ### 9\. Leverage AI marketing agents to automate lead operations Modern B2B conversion systems run on automation. [AI marketing agents](https://www.withsurface.com/blog/the-state-of-marketing-ai-in-2026) handle the repetitive tasks that slow down lead response and kill conversion rates: - **Lead enrichment:** Appending firmographic data (company size, revenue, tech stack) the moment a lead submits - **Routing and assignment:** Distributing leads to the right sales rep based on territory, product interest, or account ownership - **Follow-up sequencing:** Sending personalized emails, case studies, and meeting reminders without manual intervention - **CRO experimentation:** Running ongoing A/B tests, analyzing results, and implementing winning variations automatically According to SQ Magazine's 2026 marketing automation report, teams using AI to automate their lead operations report 30-50% increases in conversion rates within the first month, primarily by eliminating delay and human error in the handoff from marketing to sales. When the average B2B response time is nearly two days and 78% of buyers choose the first responder, automation isn't optional—it's table stakes. Companies using AI-powered lead qualification see an average 20% increase in conversion rates, with some organizations documenting improvements of up to 300% ROI from using AI in marketing and sales. High-performing teams measure CRO success across multiple dimensions, not just top-line conversion rate. **Primary conversion metrics:** - Visitor-to-lead conversion rate by page and traffic source - Form-to-meeting conversion rate (not just form submissions) - Lead-to-MQL and MQL-to-SQL rates - Cost per lead (CPL) and cost per meeting **Marketing efficiency metrics:** - Click-through rate (CTR) from ads to landing pages - Bounce rate and time-on-page for key conversion pages - Form abandonment rate and drop-off by field - Speed-to-lead (time from form fill to first contact) Track these metrics by traffic source, campaign, and page to identify which channels and tactics drive not just volume, but qualified pipeline. Many inbound funnels break between form submission and meeting booking—understanding where your funnel leaks helps you prioritize the right fixes. B2B conversion optimization differs from B2C in three critical ways: 1. **Multiple stakeholders:** B2B purchases typically involve 3-7 decision-makers, meaning your content must address different roles (end users, technical evaluators, budget holders) and pain points. 2. **Longer purchase cycles:** B2B sales cycles span weeks or months, not minutes. Urgency tactics like countdown timers rarely work—trust-building content and proof are more effective. 3. **Higher deal values:** With average contract values in the tens or hundreds of thousands of dollars, B2B buyers need more information, not less. Oversimplifying your messaging or hiding pricing can backfire. The implication: B2B CRO prioritizes qualification, trust, and nurture over impulse and urgency. You're not trying to close a sale on the website—you're trying to start a conversation with qualified buyers. Even experienced marketing teams make these errors: - **Optimizing traffic before optimizing conversion:** Adding more visitors to a broken funnel just scales the waste - **Focusing on form submissions instead of booked meetings:** A high form fill rate means nothing if leads don't convert to pipeline - **Ignoring mobile experience:** B2B buyers research on mobile, then convert on desktop—if your mobile site is slow or hard to navigate, you lose them before they ever reach a desktop - **Using generic, long forms:** Asking for 10+ fields up front kills completion rates; progressive profiling and multi-step forms convert 20-30% better - **Skipping qualification questions:** Unqualified leads waste sales time and hurt your actual conversion-to-revenue rate - **No follow-up automation:** Manual handoffs create 30+ minute delays; automated routing and follow-ups convert 3x more leads **Week 1: Audit and benchmark** - Calculate your current conversion rates by funnel stage (visitor → lead → MQL → meeting → opportunity) - Identify your highest-traffic, highest-intent pages (pricing, demo, product pages) - Compare your performance to B2B conversion benchmarks to understand where you stand **Week 2: Implement quick wins** - Reduce form fields to 3-5 essential questions - Add 2-3 qualification questions (company size, timeline, budget) - Enable partial form submission capture to recover abandoned leads - Place customer logos and quantified proof near your primary CTA **Week 3: Automate speed-to-lead** - Set up instant [lead routing](https://www.withsurface.com/blog/how-to-build-a-lead-operations-system-from-scratch) to sales based on territory or product fit - Implement auto-follow-up emails with case studies and next steps - Add real-time lead enrichment to append company and role data - Connect your forms to your CRM and meeting scheduler **Week 4: Launch your first A/B test** - Test form length (3 fields vs. 5 fields) or CTA copy variations - Run tests on your highest-traffic conversion pages first - Measure impact on both form submissions and booked meetings - Document wins and roll out successful variations site-wide Improving your B2B website conversion rate doesn't require more traffic or a complete site redesign. It requires a systematic approach to capturing leads, qualifying them in real time, and automating follow-up so no lead falls through the cracks. Surface Labs helps high-growth B2B teams increase inbound conversions by 30-50% in under two weeks by replacing legacy forms with intelligent lead capture, automating routing and follow-up with AI agents, and consolidating lead data for attribution and optimization. [Book a demo](https://withsurface.com/demo) to see how Surface can help you convert more of the traffic you already have. --- # Best Lead Routing Software in 2026: 8 Platforms Compared | Surface Labs URL: https://surface.thesurface.network/blog/best-lead-routing-software-2026 A lead router sends each buyer to the right person. Products in this category now reach far beyond assignment. Some own the form, qualify the lead, book the meeting, or repair messy CRM data. A few use AI to talk with buyers before sales gets involved. For this comparison, we looked at capture, qualification, assignment, scheduling, recovery, reporting, administration, and public pricing. We obviously advocate for [**Surface Labs**](https://withsurface.com/) for teams that want one system from inbound response to qualified meeting. LeanData is stronger for intricate Salesforce orchestration, Qualified for conversational AI, and RevenueHero for a lower-cost form-to-calendar job. > **Disclosure:** Surface Labs publishes this comparison and competes with every vendor covered. We reviewed public product pages, pricing, documentation, customer evidence, and G2 feedback on July 17, 2026. Surface is recommended under the stated criteria, and competitor strengths are included where they matter. Platform Best fit Main tradeoff Surface Labs Integrated, marketing-led lead operations Less public proof for deeply complex CRM object routing Default Composable GTM workflows and agent infrastructure Flexible systems take more work to design Chili Piper Mature routing, scheduling, and rep handoffs Higher entry price and broader administration burden Qualified Salesforce-centric conversational AI SDR Custom pricing and substantial implementation LeanData Enterprise Salesforce matching and orchestration Steeper learning curve RevenueHero Affordable form-to-meeting conversion Narrower lifecycle coverage Warmly Anonymous visitor identification and AI engagement Results depend on traffic and identity resolution LeadAngel Cross-CRM matching, deduplication, and routing Less control over the owned form experience [Surface Labs Lead Operations](https://withsurface.com/) combines multi-step forms, partial-response capture, spam filtering, enrichment, qualification, custom routing, native scheduling, recovery, nurture, and attribution. Our [scheduler](https://withsurface.com/blog/surface-scheduler) supports one-to-one, weighted round-robin, and group meetings, plus buffers, booking limits, holidays, and branded pages. Surface wins because it owns more of the conversion path. Form abandonment, disqualification, calendar exits, and no-shows remain visible in one operating layer. Marketing can see where demand disappears without stitching together five systems. Teams with dense account hierarchies or many Salesforce objects should compare LeanData and LeadAngel. Current documentation names Google Calendar, so Microsoft-calendar support should be confirmed. We have a [$500 monthly Light plan](https://withsurface.com/pricing); routing is in the quote-based Growth tier. \## 2. Default: Best for programmable GTM infrastructure [Default](https://www.default.com/) combines unified revenue data, workflows, enrichment, routing, scheduling, and AI agents. It fits RevOps teams building a shared execution layer across several GTM motions. [G2 feedback](https://www.g2.com/products/default/reviews?qs=pros-and-cons) praises connected workflows and notes the work required to make them production-ready. Choose Default when routing is one part of a larger agent and data program. Choose Surface when the immediate problem is the inbound conversion journey. [Chili Piper](https://www.chilipiper.com/) covers form qualification, instant booking, CRM distribution, chat, rep handoffs, and meeting workflows. It has the longest category history here and broad integration coverage. [Routing & Scheduling starts at $15,000 per year for 15 seats](https://www.chilipiper.com/pricing), with added seat and AI-credit costs. Chili Piper suits established RevOps teams with complicated handoffs. Surface is more coherent when form design, partial submissions, recovery, and attribution share one project. [Qualified](https://www.qualified.com/) uses its Piper AI SDR to identify, qualify, route, and book visitors across chat, voice, video, and email. Its Salesforce orientation deepened when [Salesforce completed the acquisition in April 2026](https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-qualified/). Qualified is the better choice when the website should behave like an always-on SDR. Surface fits a form-led motion where deterministic qualification and full-funnel measurement matter more than open-ended conversation. [LeanData](https://www.leandata.com/) handles lead-to-account matching, multi-object assignment, territories, lifecycle orchestration, and auditability. BookIt adds scheduling after routing. LeanData can handle routing problems that would be excessive for many marketing teams. That is also why implementation and ownership require more expertise. If CRM governance is the main problem, pick LeanData. If conversion before and after assignment is the problem, Surface has the tighter fit. [RevenueHero](https://www.revenuehero.io/) qualifies inbound forms, matches owners, routes leads, and presents the correct calendar. Its [Inbound Essentials plan starts at $79 per month plus $25 per user](https://www.revenuehero.io/pricing) with annual billing. It is an attractive purchase when the existing form works and the missing piece is affordable routing and scheduling. Surface costs more and covers more, including the form itself, partial intent, spam controls, recovery, nurture, and attribution. [Warmly](https://www.warmly.ai/) combines visitor identification, intent, AI chat, rep alerts, outreach, routing, and booking. Pricing starts at [$10,000 annually for deanonymization and $20,000 for Inbound Chat](https://www.warmly.ai/p/pricing). Warmly [announced an agreement to be acquired by HubSpot](https://www.warmly.ai/p/blog/warmly-is-joining-hubspot) in June 2026. Warmly makes sense when the team wants to act before a form fill. Surface is stronger once a buyer raises a hand and the explicit conversion event needs tighter control. [LeadAngel](https://www.leadangel.com/) handles fuzzy lead-to-account matching, deduplication, real-time and batch routing, availability-aware assignment, and scheduling across Salesforce, HubSpot, and Microsoft Dynamics 365. Its pricing is quote-based. Pick LeadAngel when dirty data and ambiguous ownership corrupt assignment. Pick Surface when the bigger leak occurs between campaign response, qualification, booking, and follow-up. The narrow answer is simple. LeanData owns complex Salesforce routing. Qualified owns conversational AI. RevenueHero offers a lean form-to-meeting path. Default suits a programmable GTM architecture. For teams that need one accountable system across capture, qualification, routing, booking, recovery, nurture, and attribution, **Surface Labs is the best overall fit**. Its [lead operations model](https://withsurface.com/blog/what-is-lead-ops) treats routing as one decision inside a larger conversion journey. --- # Build a Read-Only Marketing AI Agent First | Surface Labs URL: https://surface.thesurface.network/blog/build-a-read-only-marketing-ai-agent-first An easy marketing-agent demo ends with an action. The agent notices a weak campaign, moves budget, updates the CRM, publishes a page, and sends a tidy report. A useful first production workflow retrieves the evidence, explains the anomaly, prepares a recommendation, and waits for a person who understands the account. That restraint can look timid during a sales presentation. In an operating environment, it gives the team time to learn where the data bends. A wrong summary costs attention. A wrong write can change spend, routing, attribution, customer communication, or the public website before anyone notices. Google's current [Ads MCP server](https://developers.google.com/google-ads/api/docs/developer-toolkit/mcp-server) offers a helpful precedent. It supports account discovery and performance queries while remaining read-only. HubSpot's generally available server shows the next tier because it can write to parts of the CRM. The difference between those releases is a sensible maturity model for a marketing team. Choose a question that appears often enough to justify automation and has an answer a specialist can evaluate. A paid media team might ask which campaigns changed materially after controlling for spend and weekday mix. A content team might ask which declining pages also lost query coverage after a release. RevOps might look for leads that meet the routing definition but lack an owner. Avoid a use case that starts with "optimize." Optimization hides several decisions inside one word. Define the input systems, comparison period, business rule, expected output, and reviewer. Teams improving [inbound lead management](https://withsurface.com/blog/inbound-lead-management) could start with a read-only exception report: list qualified inbound records that have no owner after fifteen minutes, show the timestamps, and group the likely causes. A person can then fix the routing or records through the normal system. The question should have a reversible learning loop. If the agent misses a record, a reviewer can diagnose why. If the business definition changes, the team can update the test. If the workflow fails for a week, the existing process still works. Most pilots begin with prompt tuning because the prompt is visible. Start with an answer contract instead. Specify the source systems, authorized accounts, required fields, exclusions, date logic, definitions, and output format. Require a link or stable identifier for every material finding. An answer contract for campaign pacing might state that the agent can read two named ad accounts and the CRM; use the finance-approved revenue field; exclude tests, house campaigns, and the current partial day; compare against both plan and the previous four matching weekdays; and return no more than ten exceptions. Each exception must include the campaign ID, evidence window, observed change, likely explanations, confidence label, and suggested reviewer. This contract creates an evaluation target. It also exposes the human work that automation cannot skip. Someone must decide which revenue field is authoritative and whether a campaign belongs in the test set. The discipline resembles [lead journey tracking](https://withsurface.com/blog/why-lead-ops-is-becoming-its-own-category), where useful analysis depends on preserving identity and time across systems rather than producing another aggregate chart. \## Test history before live operations Build a small evaluation set from ten to twenty historical cases. Include obvious wins, ordinary weeks, known tracking failures, partial data, naming changes, and one case where a specialist's initial conclusion was wrong. Run the workflow without telling the agent the answer. Score five things. Did it retrieve the correct records? Did it apply the business definition? Did it distinguish fact from explanation? Did it expose missing data? Would the reviewer make a better or faster decision with the output? Record failures by type rather than collapsing them into one accuracy percentage. The [Conversios case study](https://about.ads.microsoft.com/en/resources/discover/case-studies/conversios-customer-success-story) offers a useful pattern: the company says it used an MCP-based audit dashboard to review Performance Max signals across 121 accounts. The published source comes from Microsoft and Conversios, so its speed and staffing claims need independent validation. The workflow shape is still sound. Apply consistent checks across a portfolio, surface exceptions, and send the result to specialists. **Days 1 to 5: define and constrain.** Select one decision, one owner, no more than three sources, and a weekly review. Document credentials, scopes, retention, business definitions, and the manual fallback. Security or IT should approve the connection even when the workflow cannot write because read access can still expose customer, budget, or performance data. **Days 6 to 12: build the evidence path.** Connect a sandbox or limited account where possible. Make every output include source records, query windows, definitions, and explicit missing-data notes. If the agent cannot cite the relevant evidence, the workflow is not ready for evaluation. **Days 13 to 20: replay history.** Run the historical cases and log retrieval errors, reasoning errors, stale data, permission failures, and specialist disagreements. Revise the data contract before revising the prose. A smoother explanation will not repair a wrong join. **Days 21 to 27: shadow production.** Let the agent produce the report alongside the existing process. Reviewers should rate usefulness before seeing the old answer when practical. Measure time to reviewed decision, evidence completeness, accepted recommendations, and exceptions that required manual investigation. **Days 28 to 30: decide the next permission.** Continue, narrow, stop, or allow a draft action. A draft action might prepare a CRM correction, budget change, or content brief without applying it. Direct writes should wait until the team has a rollback path, monitoring, and a named incident owner. "Human in the loop" often means that someone receives a notification. Define what the reviewer actually checks. The channel owner validates the marketing interpretation. The data owner checks definitions and joins. Marketing operations monitors repeatability. Security owns credentials and revocation. The accountable business leader decides which error rate and blast radius are acceptable. OWASP's [MCP security guidance](https://cheatsheetseries.owasp.org/cheatsheets/MCP_Security_Cheat_Sheet.html) emphasizes least privilege, explicit authorization, validation, and logging. Those are engineering controls with direct marketing consequences. An agency role should not inherit every client account. A content analyst should not be able to alter lifecycle stages. A service credential should not survive the person or vendor that justified it. The [connections among CRM, scheduling, and analytics tools](https://withsurface.com/integrations) can improve the handoff from research to action. The operating rule is simple: grant the smallest permission that can answer the current question, then require evidence before expanding it. Do not lead the pilot review with reports generated, prompts submitted, or theoretical hours saved. Track the share of outputs with complete evidence, the rate specialists accept recommendations, the time from question to reviewed decision, the number and severity of exceptions, and the business result when a recommendation is implemented. Keep causal language disciplined. A faster workflow may coincide with better performance without causing it. The same distinction appears when teams learn that [attribution is not incrementality](https://withsurface.com/blog/attribution-is-not-incrementality-how-to-measure-ai-creative). The agent can improve decision preparation while the team still needs experiments or other causal methods to prove business lift. A successful read-only pilot earns the right to become slightly more useful. It might create a draft, open a ticket, or route an approval. That progression feels slower than autonomous execution. It is much faster than repairing a system the team never learned to inspect. #### Practical steps - Pick one recurring, reviewable decision and document the manual fallback. - Create an answer contract before writing prompts or connecting production data. - Test ten to twenty historical cases, including tracking failures and ambiguous outcomes. - Require source records, business definitions, and missing-data labels in every material output. - Advance from read to draft, approval, and write only when each prior tier has passed a documented review. --- # Campaign Management Software: What B2B Teams Need From the System Behind Their Campaigns | Surface Labs URL: https://surface.thesurface.network/blog/campaign-management-software-what-b2b-teams-need-from-the-system Campaign management software is often sold as a way to organize work. That's useful, but a campaign board full of tidy tasks doesn't guarantee that the campaign itself makes sense. B2B teams need a system that preserves the relationship between an audience, a message, the content that supports it, the landing page, and the evidence used to judge the result. Most stacks divide those jobs across several tools — a project manager holds the launch plan, a design platform holds the creative, a CRM holds the leads, and a spreadsheet tries to explain what happened. Teams can make that work, but they spend a lot of time rebuilding context at every handoff. The question isn't whether one platform can replace every tool. It's whether the system makes the campaign easier to operate and easier to learn from. Every campaign needs a durable source of truth: the audience, the message, the offer, the primary conversion action, the owner, and the measurement plan. When this information lives only in kickoff notes, people lose it after the first round of revisions. Campaign management software should make that record visible to the people doing the work — a writer needs the message and the evidence, a demand marketer needs the landing-page destination, a sales leader needs to know what kind of lead may arrive and why. That shared context does more for quality than an elaborate status workflow, since teams can disagree about a campaign productively when they're looking at the same premise, and waste time when every department works from its own abbreviated version of the plan. Most campaign tools are strong at assets and tasks because those are easy to count — seven ads, two emails, a landing page, a launch date, and the checklist turns green. The risk is that the asset list becomes the strategy. A campaign can have all the right pieces and still fail because the audience doesn't understand the promise, the proof is thin, or the follow-up doesn't match the form submission. Treat every asset as a response to a reader moment instead: a paid ad earning attention from a defined audience, a landing page reducing uncertainty, a case study making a claim credible. Our [guide to marketing campaign strategy](https://withsurface.com/blog/marketing-campaign-strategy-how-to-turn-a-campaign-idea-into-an) explains how to make those jobs cohere — the campaign system should make the relationships visible alongside the asset inventory, not just the inventory itself. ## Look for a real content workflow Content creation is where campaign software often becomes awkward. The brief starts in one system, the draft goes through email and comments, the approved copy gets pasted into a CMS, and by launch no one's certain which version of the claim is canonical. A useful system needs clear review roles, inline feedback, version history, and an unambiguous route from approved content to publishing — automation can suggest structures and pull in performance data, but it shouldn't flatten every campaign into the same template just because the calendar wants an output. Our content review workflow and Surface CMS are designed around this connection: review can capture comments and revision decisions while the CMS publishes directly from that workflow, rather than an error-prone copy-paste relay. That matters most when a team runs recurring content-led campaigns and can't afford to reconstruct the context each time. Campaign software loses its value when it declares victory at the form fill. A campaign may reach the right person and earn a response, but the business still needs to qualify the lead, route it to the right owner, and respond while the person remembers why they engaged. That handoff should be part of the campaign design — the form collecting what's needed for a relevant route, the CRM carrying campaign and content context, a nurture path ready for buyers who are interested but not ready. Our [B2B SaaS lead capture and routing guide](https://withsurface.com/blog/lead-capture-and-routing-for-b2b-saas-companies) lays out why this depends on more than a lead source: segment, product interest, use case, and behavior can all change what a useful response looks like, and campaign management should support those distinctions rather than bury them under a single conversion metric. Campaign reports often answer the least useful question first: how many clicks did we get? The team usually needs to know something more practical — did the campaign reach the intended audience, did the landing page turn interest into qualified response, did sales get context quickly enough to continue the conversation. The right metrics depend on the campaign. An early category campaign may lean on reach and branded demand; a demand-capture campaign may prioritize qualified conversions and speed to response. Reporting needs evidence labels too — our [guide to attribution and incrementality](https://withsurface.com/blog/attribution-is-not-incrementality-how-to-measure-ai-creative) recommends distinguishing observed behavior from inferred or modeled impact, which keeps a campaign dashboard from becoming a storytelling machine that always takes credit for the result. Don't buy campaign management software because the idea of a unified platform feels cleaner. Diagnose the operational problem first — some teams need better planning and approvals, some need a tighter link between content strategy and publishing, some need lead routing that keeps pace with demand. We're most useful when the bottleneck sits between content and the rest of the marketing operation. Our Campaign Engineering tools connect strategy, review, publishing, AI visibility, and analytics, while our Lead Intelligence and Inbound Capture tools connect the conversion path to qualification, routing, and nurture. Together, they help a team see a campaign as more than a launch sequence — a system that has to preserve its own premise from brief to buyer response, not just a better task list. --- # Client Lead Generation: How Agencies and B2B Services Teams Can Build a Better Handoff | Surface Labs URL: https://surface.thesurface.network/blog/client-lead-generation-how-agencies-and-b2b-services-teams-can Client lead generation has a built-in tension. An agency is asked to create measurable demand, but the client's product, sales process, and customer knowledge live elsewhere. Marketing can build excellent campaigns and then watch leads go cold because the handoff was unclear, while the client receives a pile of leads and decides they're weak because no one agreed on qualification or follow-up in the first place. Neither side is necessarily wrong — they're operating with separate versions of the funnel. The fix begins with a more complete definition of lead generation: not the moment someone fills out a form, but the system that creates relevant attention, captures enough context to understand the response, gets it to the right person, and learns from the outcome. The word "lead" creates false agreement. A client might mean an enterprise prospect with budget and urgency. A marketing team might mean a relevant person who downloaded a guide. A sales team might mean a booked meeting. Write the definitions down — which events count as a marketing response, a qualified lead, a sales-accepted lead, a disqualified record — and include the exceptions, like a small-company prospect who isn't a fit today but could be worth nurturing. This can feel administrative, but it prevents months of noisy reporting and uncomfortable retrospectives, and it helps an agency choose offers and channels that fit the client's actual revenue goals instead of optimizing for the easiest conversion event. Agencies sometimes inherit a brief that says "we need leads" plus a few broad product claims. That's not enough. The team needs access to the actual buyer questions: what customers search for, which problems trigger a purchase, what objections arise, and what proof makes the client credible. Use that research to build a small offer architecture — educational content for early-stage buyers, a practical guide or assessment for people evaluating their current state, a case study to make the client's capabilities concrete, and a landing page that explains what happens when someone requests a conversation. We make a point in our [content marketing guide](https://withsurface.com/blog/content-marketing-guide-2026) that agencies should take seriously: content works when it connects visibility to a conversion path. A brilliant article without a relevant next step can build the client's reputation while leaving sales with nothing to do about it. ## Put client expertise into the content before the copy is final The client's subject-matter expertise is often the part an agency needs most and has least access to. A strategist can study competitor pages and keyword data, but they can't invent the implementation detail or customer language that makes a services company sound like it's actually done the work. Set up a regular source-capture process — interview founders, sales leads, and customer-success managers, and ask for the examples that rarely make it into polished decks: what goes wrong, which clients are a poor fit, what customers wrongly assume. That information improves both the content and the lead process — it helps the agency avoid overpromising, gives sales more specific material, and lets the client recognize its own voice in the work. We built our content review workflow around exactly this: feedback stays connected to the draft, the strategy, and future content, so a client doesn't need to be buried in every editorial decision but still has a reliable way to shape accuracy. ## Treat the landing page as a client-sales handoff An agency-managed landing page often gets judged by conversion rate before anyone studies the conversation it created. The page should set expectations for the sales interaction — explaining the problem the client solves, what happens after a form submission, and what information helps the team make the response relevant. Forms should collect enough detail to support routing without making a person researching a complex problem abandon the exchange, and the client's sales team should see the source, offer, and form context before writing the first response. Our [guide to lead capture and routing](https://withsurface.com/blog/lead-capture-and-routing-for-b2b-saas-companies) describes why a form submission needs that context: source, segment, and account status can all change who should respond and how, and agencies should build those rules with the client rather than treating the CRM as somebody else's concern. Many client lead-generation engagements fail in the hour after conversion — the agency drives a prospect to the page, the client's team responds the next day with a generic email that ignores the offer requested, and marketing gets blamed for quality. Agree on a service level before the campaign launches: expected response time by lead type, a named owner for each segment, and a recovery plan if the buyer doesn't respond. Treat this as a working agreement, not a legalistic document nobody opens. Our Lead Intelligence and Inbound Capture tools unify capture, qualification, routing, and nurture for exactly this reason — an agency may not run every part of that workflow, but it should understand it well enough to design campaigns that fit reality. ## Report the full story to the client Client reporting shouldn't become a contest between the agency's lead count and the client's pipeline number. Show the chain: which campaigns created attention, how fast leads were handled, which became meetings, and which were rejected and why. Separate observed data from inference — you can observe form fills and meetings, but a claim that one content cluster influenced a later deal is inferred at best. Our [attribution guide](https://withsurface.com/blog/attribution-is-not-incrementality-how-to-measure-ai-creative) offers a disciplined way to keep that reporting honest, since clients don't need fictional certainty. They need a clear picture of what's working and what the team will change next. Client lead generation works when the agency and client share the same definition of a valuable response and the same responsibility for what happens after it. Build the strategy from buyer questions, preserve the client's expertise, and make the feedback loop part of the deliverable rather than an afterthought once the leads arrive. --- # Content decay: When search, citations, and revenue stop agreeing | Surface Labs URL: https://surface.thesurface.network/blog/content-decay-search-citations-revenue ## Content decay: When search, citations, and revenue stop agreeing An old guide holds its Google position, earns roughly the same clicks, and quietly stops producing useful conversations. Another page loses half its search traffic but starts appearing in AI answers. A third attracts more visitors than ever while sales says the people arriving through it misunderstand what the company sells. Calling all three pages "decayed" is easy. Deciding what to do with them requires more care because search, citations, and revenue no longer move as one clean signal. Begin the content review with that disagreement instead of assuming the publication date explains it. ## Content decay summary Content decay is a sustained decline in a page's ability to perform its intended job. That decline may appear in rankings, organic clicks, AI citations, brand mentions, qualified engagement, conversions, sales usefulness, or pipeline influence. A page has not necessarily decayed because one metric fell, and a page is not healthy merely because traffic remained stable. Start by restating the page's job. A category guide may need to build search visibility and orient buyers. A comparison page may need to enter shortlists. A case study may receive little traffic but help opportunities progress. Content decay becomes meaningful when the evidence shows that the page is losing the outcome it was built to create. Surface brings these signals closer together. [Traffic Intelligence](https://www.withsurface.com/platform/infrastructure/traffic-intelligence) connects content performance and buyer engagement to form behavior, lead quality, and pipeline. [AI Visibility Engineering](https://www.withsurface.com/platform/ai-visibility) tracks prompts, mentions, citations, competitors, and source gaps. Looking at both prevents a team from treating a falling click chart or a rising citation count as the whole diagnosis. ## Content decay begins when the page loses its job Many audits define decay as a traffic drop against a previous period. That definition is tidy and too narrow. Traffic can fall because demand changed, search features absorbed the click, a ranking moved, seasonality ended, or a tracking setup changed. The page itself may still be accurate and commercially useful. The reverse can be worse. A post can keep ranking for a broad phrase after the company has changed its product, buyer, positioning, or sales motion. The traffic looks healthy while the page sends readers toward an expired offer, uses language sales has retired, or attracts a segment the company no longer serves. Search performance has preserved an old success that the business should stop funding. Write a one-sentence purpose for every page under review: "Help a content leader evaluate an SEO-friendly CMS and move toward Surface's content operations workflow," for example. Then assess whether the query, answer, internal link path, CTA, and downstream audience still support that purpose. Our guide to [building connected content hubs](https://www.withsurface.com/blog/what-is-a-content-hub-a-content-strategy-and-seo-guide-for-ai) is useful here because a page's value depends partly on the path it creates through the rest of the site. ## Content decay looks different across search, AI, and revenue The disagreement between channels is diagnostic evidence. Instead of blending everything into one score immediately, read each pattern on its own: Pattern Likely interpretation First check Search down, citations stable Classic demand or ranking changed while the page still supports answer retrieval Query mix, cited passages, competing results, and click behavior Search stable, citations down The page remains rankable but has become less useful inside current answer source sets Freshness, evidence, entity clarity, off-site corroboration, and prompt coverage Traffic up, qualified demand down The page expanded into a broader or less relevant audience Queries, geography, intent, conversion path, and lead-quality distribution Citations up, brand mentions flat Engines use the page as evidence without associating the answer with the company Brand-category language, cited claim, and whether competitors receive the recommendation Conversions stable, pipeline down The form still works, but targeting, qualification, or the promise may be wrong Accepted-lead rate, objections, routing, segment, and sales outcomes Traffic down, sales use high The public audience shrank, but the asset still supports active deals Asset shares, opportunity stage, buyer feedback, and replacement cost Microsoft's [AI Performance guidance](https://blogs.bing.com/webmaster/February-2026/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview) recommends reviewing cited pages, grounding queries, structure, evidence, and freshness. It also warns that citations do not indicate ranking or page importance. Keep that restraint when comparing AI visibility with search and revenue. ## Content decay needs diagnosis before revision Refreshing the introduction and changing the date can make an old page look busy without making it more accurate. Google's [generative AI optimization guidance](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) emphasizes useful, non-commodity content and says there is no ideal page length or special rewrite style for AI search. Revision should improve the answer a person receives; a recent date by itself proves very little. Inspect five sources of decay: - Factual decay appears when statistics, product capabilities, screenshots, laws, pricing, integrations, examples, or cited sources no longer describe the current world. - Intent decay appears when the ranking query or buyer question now calls for a different page type, decision, audience, or depth. - Structural decay appears when internal links, templates, rendering, canonicals, navigation, or site migrations weaken discovery and context. - Commercial decay appears when the offer, segment, CTA, proof, qualification rule, or sales motion changes while the page remains frozen. - Authority decay appears when competitors and third-party sources publish clearer evidence, stronger examples, or more current category explanations. A refresh is only one valid outcome. Keep a page when it remains accurate, distinct, strategically relevant, and useful, even if one channel softened. Refresh it when the purpose still holds but the evidence, answer, examples, links, or conversion path need work. Consolidate when several pages compete for the same intent and none deserves to remain the primary destination. Reposition a page when it attracts a valuable audience but no longer supports its original offer. A high-traffic educational article might become a stronger hub, glossary entry, sales resource, or newsletter acquisition point. Retire or redirect when the page is inaccurate, duplicative, commercially irrelevant, and unlikely to regain a defensible role. Use a short decision record for every material change: 1. State the page's current job and the evidence that it is losing that job. 2. Mark which observations are direct, which are attributed, and which remain inferred. 3. Choose the intervention and name the owner, reviewer, and measurement window. 4. Preserve any links, proof, or useful sections that should survive the change. 5. Recheck search, citations, qualified engagement, and sales response after publication. Surface's [content campaign workflow](https://www.withsurface.com/solutions/launch-campaigns-faster) can turn a qualified opportunity into a brief, article update, landing page, and supporting assets under one approval plan. A page rarely decays in isolation; its surrounding proof, messages, forms, and handoffs age too. ## Build a portfolio that can admit when a page is finished Content teams often keep every URL because deletion feels like destroying work. The more useful question is whether the page still earns maintenance. A library of 400 posts is not inherently stronger than a library of 150 clear, connected, current pages. Maintenance capacity is part of strategy. The [Surface content marketing guide](https://www.withsurface.com/blog/content-marketing-guide-2026) argues for a system that connects visibility, trust, conversion, distribution, and measurement. Content decay is what happens when one of those layers changes and the others do not. A reliable program watches the relationships, records the disagreement, and funds the pages still capable of doing useful work. If your search, AI visibility, and pipeline reports are telling incompatible stories, [book a Surface walkthrough](https://www.withsurface.com/book-a-demo). Bring one content cluster and its current performance data, and we can map what deserves a refresh, a different job, or a clean ending. --- # Content Hubs for SEO: Why Interconnected Content Beats Random Publishing | Surface Labs URL: https://surface.thesurface.network/blog/content-hubs-for-seo ## Content Hubs for SEO in Summary Content hubs for SEO organize related pages around a central topic so buyers, search engines, and AI systems can understand the relationship between ideas. A strong hub usually includes a pillar page, supporting articles, comparison pages, use-case content, proof assets, internal links, and a conversion path. Random publishing creates inventory. Content hubs create movement. That distinction matters for B2B SaaS and technical product companies because buyers rarely move from one question straight to a demo. They learn vocabulary, compare approaches, test objections, ask about implementation, look for proof, and then decide whether the company feels credible enough to involve sales. A content hub gives that journey a path. The strongest content teams do not just ask what they can publish next. They ask what path the buyer needs to walk, which page should answer each stage of that path, and how each piece of content should connect to the next useful decision. ## What Is a Content Hub? A content hub is a connected group of pages organized around a strategic topic. The center of the hub is usually a pillar page. That page explains the main concept, defines the category, introduces the company’s point of view, and links to deeper supporting pages. The supporting pages answer more specific questions. Some are educational. Some are comparative. Some are tactical. Some are technical. Some are closer to conversion. For example, a content strategy hub might include: - A main guide to content marketing strategy - A post about SEO automation and content debt - A post about content briefs - A post about AI and brand voice - A post about content hubs - A post about query fan-out and AI search - A post about AI visibility measurement - A post about content production cadence - A landing page or product page that explains how the company helps That is different from simply publishing nine separate blogs. The hub works because the pages are intentionally related. Each page has a job. Each page links to the next useful page. The whole system teaches search engines, AI systems, and buyers what the company understands. A random archive says, “We have written about this topic.” A content hub says, “We can guide you through this topic.” ## Content Hubs Create a Path, Not a Pile A content pile is a collection of pages that happen to live on the same website. A content hub is a connected system. The difference is visible in the reader experience. In a content pile, a buyer reads one article, hits a generic CTA, and leaves. The next article may answer a related question, but the site does not guide them there. The product page may explain the next step, but the blog does not connect to it. The sales team may have a useful proof point, but the reader never sees it. In a content hub, the reader can move naturally: - From definition to problem - From problem to approach - From approach to comparison - From comparison to implementation - From implementation to proof - From proof to conversion Search systems use those pathways too. Internal links help crawlers understand which pages matter and how topics relate. AI systems also benefit from clear content architecture because query fan-out turns one question into a network of related sub-questions. A brand with connected coverage has more opportunities to be understood, retrieved, cited, and trusted. Thinking about [query fan-out in Google AI Search](https://withsurface.com/blog/query-fan-out-in-google-ai-search-how-marketers-should-build-con) makes the hub model easier to understand. A single query can require the system to understand definitions, comparisons, use cases, objections, source credibility, and related entities. One isolated article is a weak answer to a networked question. Random publishing is seductive because it creates visible motion. The team can point to new URLs, new drafts, new keywords, and new reports. The site looks active. The calendar looks full. The problem is that random publishing often reflects the content team’s available ideas rather than the buyer’s path or the business priority. A technical product company might publish five excellent posts about architecture because the engineering team had strong opinions. That can be useful. But if the company’s biggest growth constraint is buyer confusion around use cases, the site may start to overrepresent technical architecture while underrepresenting the content that would actually help conversion. A B2B SaaS company might publish a dozen AI search posts because the topic is hot. Again, some of those pages may be useful. But if they do not connect to product pages, proof, lead capture, sales enablement, or a broader content operations system, the team may win attention without building trust. Thinking about [AI citations vs. SEO rankings](https://withsurface.com/blog/ai-citations-vs-seo-rankings) helps clarify the risk. Visibility is no longer one clean leaderboard. A brand may rank, be cited, be summarized, be mentioned, or disappear depending on the surface. Content hubs help because they create a clearer source ecosystem around the topic rather than asking one page to carry the entire visibility burden. ## Content Hubs Work Because Buyer Intent Changes The best content hubs are built around intent movement. Not every reader is ready for the same page. Some readers are trying to understand a category. Some are comparing approaches. Some are looking for a vendor. Some are trying to convince an internal stakeholder. Some are already in a sales process and need proof. A content hub should give each reader the right next step. For a content strategy hub, the path might look like this: ### Educational Intent The reader asks broad questions: - What is content strategy? - How many blogs should we publish? - How should AI fit into content? - What is a content brief? - What is a content hub? These pages should explain concepts clearly and introduce the company’s point of view. ### Comparative Intent The reader starts comparing options: - Should we use AI tools or hire more writers? - Should we focus on SEO, AI visibility, or conversion content? - Should we build content hubs or publish standalone blogs? - Should content strategy be handled internally or with an operations partner? These pages need nuance, tradeoffs, examples, and proof. ### Transactional Intent The reader has a problem and wants a solution: - Who can help us build a content operation? - How do we turn traffic into qualified demos? - How do we connect content to capture, qualification, routing, recovery, and nurture? These pages should connect content strategy to business outcomes and give the reader a clear conversion path. A hub succeeds when these layers connect. It fails when each page behaves as if it is the only page on the site. ## A Content Strategy Hub Example A content strategy hub should not be a giant page that tries to rank for everything. It should be a system of connected pages with different jobs. Here is a practical hub structure for the topic `content strategy`. ### Pillar Page A pillar page should explain the overall model. Example internal target: - [Content Marketing Guide for 2026](https://withsurface.com/blog/content-marketing-guide-2026) Job of the pillar: - Define the modern content operating model - Explain visibility, trust, conversion, distribution, and measurement - Establish the broader point of view - Link to supporting pages - Give readers a clear next step A pillar page should not be a dumping ground. It should be the cleanest, most useful orientation point for the topic. ### Supporting Educational Posts These posts answer core questions. Possible pages: - SEO Automation Is Useful, but It Cannot Replace Content Strategy - What Is a Content Brief, and Why the Best Briefs Still Need Human Judgment? - How to Use AI in Your Content Strategy Without Losing Brand Voice - Content Production: How Many Blogs Should You Publish Each Week? Existing internal target: - [content production cadence](https://withsurface.com/blog/content-production-how-many-blogs-should-you-publish-each-week) Job of these posts: - Answer specific questions - Capture informational demand - Introduce Surface POV - Link back to the pillar - Link laterally to related posts These pieces should stand on their own, but they should not float alone. A reader should be able to enter through any supporting article and still find the broader content strategy path. ### AI Visibility and Search Evolution Posts These posts explain the changing discovery environment. Existing internal targets: - [generative AI search optimization](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) - [generative engine optimization services](https://withsurface.com/blog/generative-engine-optimization-services) - [AI visibility measurement](https://withsurface.com/blog/ai-visibility-measurement-is-messy-how-to-report-geo-without-fak) - [query fan-out in Google AI Search](https://withsurface.com/blog/query-fan-out-in-google-ai-search-how-marketers-should-build-con) Job of these posts: - Explain why classic SEO is no longer the only visibility system - Show how AI search changes content architecture - Help content managers report without fake precision - Connect AI visibility back to content strategy The mistake many teams make is treating AI visibility as a separate project from content strategy. It is not separate. AI visibility depends on coverage, clarity, evidence, freshness, structure, and trusted source relationships. Those are content strategy questions. ### Operations and Conversion Posts These pages connect content to GTM execution. Existing internal targets: - [marketing operations strategy](https://withsurface.com/blog/marketing-operations-strategy-content-system) - [post-click paths that turn traffic into demos](https://withsurface.com/product) Job of these pages: - Show that content does not end at publication - Explain how traffic moves into capture, qualification, routing, recovery, and nurture - Create a bridge from education to commercial action A content hub without a conversion bridge is an educational library. That may be useful, but it is not enough for most B2B teams. The hub should help the reader understand the topic and understand the next operational step. ### Proof and Customer Context A content hub should include proof. That proof may come from customer stories, product examples, case studies, benchmark pages, original research, visual reports, or operational results. Job of proof assets: - Reduce perceived risk - Give sales useful follow-up material - Show that the content strategy connects to business outcomes - Help readers believe the operating model is not theoretical Proof does not always need to be a massive case study. It can be a specific example, a teardown, a before-and-after structure, a data point, a customer quote, or a small operational model. The important thing is that the hub should not rely only on explanation. Internal links are often treated as SEO housekeeping. That is too small a frame. Internal links are audience design. A good internal link should feel like the reader’s next thought. If someone is reading about content hubs, a link to query fan-out makes sense because it explains why isolated pages are weaker in AI-mediated discovery. A link to content production cadence makes sense because hubs still need publishing rhythm. A link to marketing operations strategy makes sense because the hub has to connect to a system that can capture and convert interest. Bad internal links feel like keyword insertion. Good internal links feel like guidance. Search systems use links to understand structure. Buyers use links to decide whether the company understands the problem deeply enough to keep helping. Sales teams use links to answer recurring questions. A strong content hub serves all three audiences at the same time. ## Content Hubs for SEO and AI Visibility Content hubs also help AI visibility because AI systems often retrieve from multiple sources, compare claims, and synthesize answers. A single page can be useful, but a cluster gives the system more evidence that the company understands the topic. A content hub improves AI visibility when it includes: - Clear definitions - Specific subtopic coverage - Fresh examples - Source-backed claims - Comparison logic - Use-case explanations - Proof assets - Internal links - Consistent product and category language - Pages that answer questions at different intent levels That does not mean teams should create dozens of thin fan-out pages. The goal is not to publish a page for every possible prompt variation. The goal is to cover the real question map with enough depth that both humans and systems can understand the company’s expertise. A hub should make the company easier to cite because the company becomes easier to understand. ## How to Build a Content Hub Without Overbuilding It Start with one core business topic. For this example, use `content strategy`. Then map the hub in plain language. ### Define the Core Belief Start with the argument that should govern the hub. Example: `Content strategy should create a connected path from visibility to trust to conversion, not a random queue of publishable assets.` That belief gives the hub coherence. Without it, the hub becomes a keyword cluster with no editorial center. ### Choose the Pillar Create or identify the main page that explains the full model. The pillar should be broad enough to orient the reader but not so broad that it becomes vague. It should define the topic, explain the stakes, show the model, and link outward to supporting pieces. ### Map Supporting Questions Choose six to ten supporting questions buyers actually ask. For content strategy, those might include: - How should B2B teams use AI in content? - What is a content brief? - How many blogs should we publish? - Do content hubs still work for SEO? - How should teams measure AI visibility? - How does content connect to lead conversion? - What should be refreshed each quarter? - When does automation create content debt? The goal is not to exhaust every possible keyword. The goal is to cover the questions that help the buyer build confidence. ### Assign Intent to Each Page Every supporting page should have a job. Some pages educate. Some compare. Some persuade. Some enable sales. Some support technical validation. Some should point toward conversion. Some should primarily strengthen the hub’s topical clarity. If every page has the same CTA and the same structure, the hub is not respecting intent. ### Create the Internal Link Plan Decide how each page links upward to the pillar, sideways to related posts, and downward toward conversion or proof. A simple pattern works: - Supporting posts link to the pillar. - The pillar links to supporting posts. - Related supporting posts link to each other. - Mid-funnel posts link to proof or conversion pages. - Conversion pages link back to educational resources when the buyer needs more context. Internal links should be planned before publication, not patched in six months later. ### Build the Conversion Bridge Create a useful commercial next step. A reader should not move from a thoughtful content strategy article into a generic contact form with no context. The next step should explain how the company helps with the problem the reader just spent time understanding. For Surface, that bridge might be a content operations page that connects strategy, publishing, internal links, conversion paths, measurement, refreshes, and AI visibility into one operating system. ### Set the Refresh Rhythm Review the hub quarterly. Update: - Internal links - Statistics - Examples - Product references - Screenshots - CTAs - AI visibility references - Search intent shifts - Related posts - Outdated claims - Missing proof Content hubs are not one-time architecture projects. They are living systems. Content hubs should be measured as systems, not only as individual URLs. Track: - Rankings for hub-level and page-level queries - Organic traffic by intent layer - Internal clicks from supporting pages to pillar and conversion pages - Engagement quality on hub pages - Assisted conversions - Demo requests from hub paths - Sales usage of hub content - AI citations and brand mentions where relevant - Pages with declining freshness - Orphaned or underlinked pages - Content gaps discovered through sales calls or prompt testing The goal is not to build a dashboard for its own sake. The goal is to understand whether the hub helps buyers move from curiosity to confidence. If a hub earns traffic but no one clicks deeper, the path may be weak. If people read several pages but never reach a conversion point, the bridge may be missing. If sales never uses the content, the proof may be too abstract. If AI systems mention competitors but not the company, the hub may lack citation-worthy coverage, freshness, or authority. Measurement should show where the system is helping and where the system is leaking. ## Common Content Hub Mistakes ### Building the Hub Around Keywords Instead of Buyer Questions Keyword research matters, but a hub should not be a spreadsheet made visible. Start with how buyers think. Then map keywords to that path. ### Publishing Supporting Posts Without a Pillar Supporting posts can rank individually, but without a strong pillar they often fail to teach the site’s structure. The pillar gives the cluster a center. ### Linking Only Upward Many teams link supporting posts to the pillar and stop. Hubs also need lateral links between related posts and downward links toward proof or conversion pages. ### Treating Every Page as Informational Some pages should teach. Others should compare, qualify, persuade, or support sales. If every page sounds like a beginner guide, the hub will not serve the full buying process. ### Forgetting the Conversion Page A hub that never connects to a conversion page may generate attention without producing movement. For B2B teams, the path should eventually give the reader a practical next step. ### Letting the Hub Go Stale A hub can decay. Links break. claims age. Examples lose relevance. Product positioning changes. AI and search behavior shifts. Refreshing the hub is part of the strategy. Choose one topic that matters to revenue. Do not start with twenty. For that topic, build a simple map: - One pillar page - Six to ten supporting pages - One proof asset - One conversion page - One quarterly refresh process - One measurement view Then audit existing content before creating anything new. Many teams already have half a hub sitting in their archive. The problem is not always missing content. Sometimes the problem is missing connection. A practical first pass might look like this: 1. Export every blog related to the topic. 2. Group the posts by intent. 3. Identify the strongest pillar candidate. 4. Identify pages that should be merged, refreshed, redirected, or linked. 5. Add internal links that reflect the reader’s next thought. 6. Create one missing conversion bridge. 7. Add the hub to the quarterly refresh calendar. Surface’s content operations perspective is built around that kind of connection. A content program should help teams decide what to publish, how to structure it, how to link it, how to keep it fresh, and how to turn qualified attention into movement through the GTM system. ## Final Thought on Content Hubs for SEO Content hubs for SEO work because they respect how people actually learn. A buyer does not become confident because one article used the right keyword. A buyer becomes confident because the company keeps answering the next question with clarity, proof, and a visible understanding of the problem. Search systems and AI systems reward parts of that same architecture because connected content is easier to crawl, classify, retrieve, and cite. Random publishing fills the site. Content hubs teach the market how to walk through it. --- # A content marketing audit that finds what still deserves investment | Surface Labs URL: https://surface.thesurface.network/blog/content-marketing-audit-finds-investment ## A content marketing audit that finds what still deserves investment A marketing team exports 1,842 URLs, colors a spreadsheet red, yellow, and green, then spends the next month refreshing the red rows. Nobody asks whether the green pages support the current business, whether sales uses the low-traffic case studies, or whether the company can maintain the archive it just promised to update. The spreadsheet is an inventory. A content marketing audit begins when the team makes a decision about the portfolio. The job is to find what deserves continued investment, what needs a clearer role, and what the company can stop carrying. ## Content marketing audit summary A content marketing audit evaluates the purpose, accuracy, distinctiveness, discoverability, AI visibility, buyer behavior, conversion role, sales use, business influence, and maintenance cost of a content library. Its output should assign an action and an owner to each material page or cluster: keep, refresh, consolidate, reposition, redistribute, or retire. The audit should not reward traffic by default. A broad glossary page can earn many visits and little commercial value. A case study may receive modest public traffic while helping late-stage buyers build internal support. A technical guide may be essential for customer trust even when it never produces a directly attributable opportunity. Surface supports this wider view through [Traffic Intelligence](https://www.withsurface.com/platform/infrastructure/traffic-intelligence), which connects content and campaign activity to buyer engagement, form behavior, lead quality, and pipeline. [AI Visibility Engineering](https://www.withsurface.com/platform/ai-visibility) adds citations, mentions, competitors, prompts, and source gaps. Those systems help the team inspect multiple outcomes without pretending every page needs to win every one. ## A content marketing audit starts with purpose and inventory Build a canonical URL list with title, type, category, owner, publication date, last factual review, intended audience, target query or buyer question, product relationship, CTA, index status, canonical target, and cluster. Normalize redirects, duplicates, parameter URLs, translated variants, PDFs, and pages accidentally counted twice by analytics. Then give each page a current job. Avoid vague descriptions such as "awareness." A useful job names the reader and change: explain a category to first-time buyers, help a technical evaluator understand implementation, give sales proof for a recurring objection, earn citations for an original dataset, or convert high-intent visitors into a qualified conversation. This step catches strategic decay before the metrics do. A page may perform exactly as designed while the company no longer sells the offer, serves the segment, or uses the positioning it promotes. The [Surface content marketing guide](https://www.withsurface.com/blog/content-marketing-guide-2026) makes the broader point that visibility only matters inside a system of trust, conversion, distribution, and measurement. ## A content marketing audit combines evidence without flattening it Pull evidence from the full path, then preserve the source of each signal. Google explains that [Search Console and Analytics measure different parts of the journey](https://developers.google.com/search/docs/monitor-debug/google-analytics-search-console): Search Console records activity before a visitor arrives from Google, while Analytics records on-site interactions. Even clicks and sessions use different definitions and will not match perfectly. Add AI visibility, links and referring sources, CRM outcomes, sales asset use, customer feedback, editorial quality, and maintenance burden. Review by page and by cluster because a supporting article may have limited standalone value while improving a hub's coverage and reader path. Evidence group Questions to answer Common mistake Strategic fit Does the page support a current audience, category, product, and business priority? Keeping pages because they once mattered Discovery Can intended readers find it through search, AI answers, navigation, referrals, and internal links? Treating rankings as the only discovery state Answer quality Is the page accurate, distinct, supported, current, and easier to use than available alternatives? Updating the date without improving the answer Buyer behavior Do intended readers engage, continue, return, convert, or use the next step? Comparing pages with different jobs by one engagement metric Revenue use Does the asset assist qualification, sales conversations, opportunity progress, retention, or customer education? Claiming causality from proximity in a journey Cost and risk What does the page cost to review, host, update, defend, and keep compliant? Treating maintenance as free ## A content marketing audit needs decision rules Scoring can help prioritize a large library, but the score should support judgment rather than hide it. Rate each page from zero to two on current strategic fit, evidence quality, distinctiveness, discoverability, buyer usefulness, commercial contribution, and maintenance feasibility. Keep the underlying values visible so two pages with the same total do not look equivalent. Use the result to route decisions: - Keep pages that remain accurate, distinct, strategically relevant, and proportionate to their maintenance cost. - Refresh pages whose purpose still holds but whose evidence, answer, technical delivery, links, or conversion path has weakened. - Consolidate pages that compete for the same intent or divide a useful answer into several thin destinations. - Reposition pages that attract a valuable audience but point toward the wrong job, offer, or next step. - Redistribute strong assets that need email, paid, sales, partner, video, or social support rather than another rewrite. - Retire or redirect pages that are inaccurate, duplicative, irrelevant, risky, and unlikely to regain a defensible role. Document exceptions. A required policy page, technical reference, campaign archive, or customer commitment may remain despite a low score. A research page may deserve investment before traffic appears because the company needs the evidence for an upcoming category move. ## Measure content ROI at the portfolio level Content ROI becomes brittle when a team demands a revenue number from every URL. Some assets create demand, some capture it, some explain the category, some reduce sales friction, and some supply evidence that other pages reuse. Measure the portfolio and the jobs inside it. Separate observed, attributed, and inferred contribution. An organic click, form submission, accepted lead, and shared sales asset can be observed. Google Analytics can assign conversion credit through a selected [attribution model](https://support.google.com/analytics/answer/10596866?hl=en), but that credit depends on the model and lookback settings. Interviews, path analysis, and repeated patterns can support an inference that content influenced a deal without proving one page caused it. The 2026 [Content Marketing Institute and MarketingProfs survey](https://contentmarketinginstitute.com/b2b-research/b2b-content-marketing-trends-research) found that effective teams most often credited relevance and quality, team skills, sales alignment, technology, customer understanding, and measurement. That mix is more useful than a traffic-only audit because it recognizes that content performance depends on the operating system around the asset. Deliver a prioritized backlog that turns observations into owned work. Every action should have a reason, affected cluster, source requirements, level of effort, dependency, approval path, success check, and owner. Limit the first wave to work the team can publish and remeasure within a defined window. [Surface Content Campaign Agents](https://www.withsurface.com/platform/content-campaigns) can turn the strongest evidence into a brief and coordinated asset plan. The [publishing workflow](https://www.withsurface.com/solutions/launch-campaigns-faster) keeps human review between the draft and production, then qualified-demand outcomes can shape the next decision instead of starting another disconnected audit. Review the portfolio on a cadence that matches its volatility. Product comparisons and tool guides may need quarterly factual checks. Stable educational pages can wait longer unless performance changes. Technical pages should follow product releases. Assign a next review date before calling the audit complete. A good content marketing audit gives the company permission to invest unevenly. Some pages deserve a serious rebuild. Some need distribution. A few should remain quietly useful. Others have finished their work. If your current audit stops at traffic and word count, [book a Surface walkthrough](https://www.withsurface.com/book-a-demo) and bring one cluster you need to evaluate against qualified demand. --- # Content Marketing Guide for 2026: Why Visibility Is Easier and Conversion Is Harder | Surface Labs URL: https://surface.thesurface.network/blog/content-marketing-guide-2026 A Surface Labs capstone guide for content leads, single-person marketing operators, and GTM leaders who need content to earn attention, trust, and pipeline without surrendering the marketing craft to algorithm games. ## Let's begin content marketing in summary Content marketing in 2026 does not reward teams that treat visibility as the whole game. SEO still asks teams to earn referring domains, rankings, topical authority, and patient traffic over time. Answer engine optimization and AI search create faster, stranger windows of visibility, but people still build those windows from old-fashioned strategic materials: clear pages, credible claims, useful internal links, fresh evidence, structured answers, and brand authority that other people can verify. We see the current moment through a simpler lens: content marketing still has to market. Content teams can win a citation, rank for a phrase, or appear in an AI answer and still fail if buyers land on a disconnected page, find no proof, receive no emotional reason to care, or cannot follow a path from curiosity to confidence. Content leads, solo operators, and GTM teams need content systems that respect how algorithms sort information and how humans decide whom to trust. One sentence should hold the whole guide together: you will not find success with content if you do not consider the full landscape of your audience before writing it. That audience includes search systems, AI assistants, prospects, existing customers, sales teams, founders, product experts, and the internal people who have to explain the brand after marketing hands them a lead. ## The Easy Content Marketing Mistake in 2026 A content lead opens a dashboard on Monday morning and sees a strange, familiar picture. The team published twenty new articles, earned a little traffic, triggered a few impressions in search, and still watched the best-fit buyer leave without booking a call. Someone in the meeting calls the experiment a visibility win, and everyone silently understands that the business needed something more than visibility. That scene explains why this content marketing guide for 2026 cannot be another list of publishing hacks. Marketing teams have more tools, more templates, more synthetic drafts, more ways to summarize competitor pages, and more channels where buyers might encounter an answer. Marketers can make an article appear publishable faster than ever, which makes weak strategy more dangerous than ever because a bad idea can now move at the speed of software. Teams should not treat this moment as a reason to abandon SEO, blogs, or owned media. Teams still need search visibility, and many teams still need the boring, patient work of earning links, improving rankings, publishing steadily, and building a site that search systems can crawl and buyers can understand. Teams also need to recognize that AEO and AI search introduce narrower and more volatile opportunities. A buyer might ask an AI assistant for recommendations before anyone on the marketing team sees a clean keyword report. An answer engine might cite a product page, a YouTube transcript, a comparison article, or a third-party mention. A human buyer might never click the first thing they see, but they might remember the brand that sounded specific enough to trust. The mistake comes when teams flatten all of that into algorithmic victory. Content marketing still asks marketers to engage an audience by appealing to cognitive and emotional functions. People need clarity, pattern recognition, proof, memory, desire, caution, humor, and trust. Search systems can surface a page, but people decide whether the page was worth surfacing. ## What Actually Changed in Content Marketing The market moved from publishing discipline to system discipline. In 2017, many content programs still debated whether teams had documented strategies, cadence, personas, and basic SEO discipline. By 2026, marketers have moved into a messier world where owned media, video, email, social, events, communities, AI answers, and classic search all shape the route from discovery to trust. The shift is clean enough to name: teams moved from “publish regularly” toward building a durable trust engine across search, email, social, video, and AI surfaces. External research points in the same direction. Content Marketing Institute reports that B2B marketers planned 2026 investment increases across AI-powered marketing tools, events and experiential marketing, and owned media, including websites, blogs, and email. That mix matters. Marketers are not only buying AI tools to make more things. Many teams are also putting budget behind owned channels and high-trust environments where buyers can spend enough time to believe something. Enterprise teams reveal the operational version of the same story. Content Marketing Institute’s enterprise research found that enterprise marketers cited content relevance and quality, team skills, measurement, sales alignment, and customer understanding among the major factors improving effectiveness. Smaller content teams should tattoo the lesson somewhere near the CMS login: the team does not win because it produces more assets. People on the team win when they can decide what matters, create useful material, connect it to the buyer journey, measure whether anyone cared, and revise without turning the whole operation into committee theater. Buyers also changed how they gather confidence. Gartner reported in March 2026 that 67% of B2B buyers prefer a rep-free experience, and 45% used AI during a recent purchase. Gartner also reported in 2025 that buyers often prefer online self-service for general learning, while they still prefer seller input when they need contextual intelligence about fit. Content has to serve both moments. A blog can help a buyer learn without a rep, while a sales-enabled landing page, proof page, comparison page, or well-structured product page can help that buyer form enough confidence to involve a human. The old content factory made a promise it could not keep. Teams could publish more, rank for more, and look busier. Buyers, search systems, and internal revenue teams eventually learned to distinguish motion from progress. What stopped working What works now Bulk publishing sprints that produce a burst of attention and then leave the site stale. Consistent publishing and revision cycles that prove people still care about the site. AI slop dressed up with headings, keyword stuffing, and the faint smell of competitor plagiarism. Expert-backed content with original judgment, evidence, customer language, and a reason to exist. Template addiction, where every page has the same rhythm, same claims, and same safe phrasing. Templates as a baseline, with editors, subject matter experts, and operators adding specificity. Thought leadership cosplay from people who do not want to think in public or talk to the market. Genuine point of view from people who care, know the category, and can hold a real conversation. Blog-only planning that sends every reader into the same generic CTA. A linked system of blogs, landing pages, conversion pages, email, proof, and sales enablement. Traffic-only reporting that celebrates pageviews while sales teams complain about fit. Measurement across visibility, engagement, conversion quality, sales usefulness, and AI citation signals. Thinking about [AI citations vs. SEO rankings](https://withsurface.com/blog/ai-citations-vs-seo-rankings) gives marketers a useful way to understand the measurement shift. Ranking still matters, but ranking no longer describes the whole visibility field. Teams now need to understand where pages rank, where they are cited, where brands are mentioned, and whether the content actually shapes the answer buyers see. ## The 2026 Content Marketing Operating Model A strong 2026 content operation needs five layers. A small team can own all five without pretending each layer requires a separate department. A larger team can separate responsibilities, but leaders still need one operating model so everyone understands where content earns attention, where content earns trust, and where content helps a buyer act. ### Visibility Layer Content leads help search systems, AI assistants, communities, email subscribers, social readers, and partner channels discover the brand. This layer includes keyword strategy, AEO query mapping, glossary pages, educational blogs, refreshed explainers, structured answers, and distribution assets. Visibility content should answer real questions and create clean entry points, rather than chase every prompt or head term because a tool says the term exists. ### Trust Layer Marketing teams turn first contact into belief with expert commentary, customer stories, comparisons, proofs, data, founder or product POV, and clear source citations. Google’s people-first guidance asks creators to provide original information, reporting, research, analysis, and substantial value beyond rewriting sources. That standard maps well to human trust because buyers also notice when a page sounds like a paraphrase machine. A reader who needs proof should be able to move naturally into [customer stories](https://withsurface.com/customers/overview), especially when a content page makes a claim about conversion, lead quality, funnel performance, or operational efficiency. A strong content system does not ask readers to trust every claim on tone alone. ### Conversion Layer GTM teams need landing pages, product pages, comparison pages, pricing narratives, proof pages, and contact pathways that help buyers move from interest to decision. A team can publish twenty useful blogs and still underperform when none of those blogs point to a strong landing page or a conversion page that explains what the company actually does. Lead capture, qualification, routing, recovery, and nurture should sit inside this layer rather than being treated as a disconnected operations problem. Teams can drive readers into the site through search and AI visibility, but the business still needs [a post-click path that turns traffic into demos](https://withsurface.com/product). ### Distribution Layer Operators need to package good content across email, social, community, sales notes, webinars, video, and partner channels without creating duplicate spam. Email matters here because teams own the inbox relationship more directly than they own algorithmic reach. A newsletter, nurture sequence, or product update can reinforce memory even when a buyer does not click every message. Thinking about [AI Mode personalization and brand recommendations](https://withsurface.com/blog/ai-mode-personalization-personal-context-changes-brands) gives marketers another reason to care about owned touchpoints. If buyers carry useful product language, proof, and follow-up context into future AI-assisted research, email clarity and lifecycle communication become part of the visibility system. ### Measurement Layer Leaders need dashboards that tell them whether content created discoverability, qualified attention, assisted pipeline, useful sales conversations, citation visibility, and stronger buyer confidence. Teams should still track rankings and traffic, but they should also separate vanity visibility from content that actually engages or converts. An [AI visibility dashboard](https://withsurface.com/blog/ai-visibility-dashboard) can help teams monitor how often AI systems mention a brand, which prompts produce competitor presence, and where content coverage needs to improve. That measurement should not replace business reporting. It should sit beside qualified lead reporting, form-to-meeting conversion, sales usefulness, and content-assisted pipeline. We have watched teams run straight into the content productivity cliff when they try to publish more than three high-quality pieces per week. One strong blog per week usually keeps a team moving. Two strong blogs per week gives a team more surface area and more learning cycles. Three strong blogs per week often marks the practical ceiling where most lean teams still preserve research quality, editorial judgment, internal review, distribution, and revision discipline. Beyond that point, many teams stop making content and start managing a conveyor belt. Writers lose the time needed to understand the product. Editors lose the time needed to sharpen claims. Subject matter experts skim drafts instead of adding judgment. Operators push pages live without checking internal links, conversion paths, schema, images, or source freshness. The team may still publish, but the team no longer compounds trust. Bulk publishing also creates a strategic illusion. A site can earn a temporary lift from a flood of new pages, especially when a team targets low-competition queries or emerging AI-search gaps. Teams often see sharp increases in traffic, citations, and earned impressions for a few months before the gains fall away when quality, consistency, and trust signals fail to hold. The lesson is not that volume never matters. The lesson is that consistency beats bulk every time when people have to keep reading, trusting, and converting after the sprint ends. A healthier cadence turns publishing into a rhythm instead of a stunt. Marketers publish new material, update old material, watch which questions return, revise conversion paths, and turn the best ideas into email, sales enablement, social commentary, webinars, and product messaging. That rhythm gives both algorithms and humans a reason to believe the company remains alive inside its own category. Content strategy begins when marketers stop treating every query like it deserves the same answer. Someone who searches “what is content marketing” needs a different page than someone who searches “best content marketing operations platform for B2B SaaS.” One person may be learning vocabulary. Another person may be trying to decide who can help the team next quarter. A third person may be comparing vendors after an executive asked why the blog gets traffic but the pipeline report looks thin. The strategy landscape can be divided into three practical intent groups: informational and educational queries, comparative or research-oriented queries, and direct transactional queries. That framework gives content leads a way to match the page to the job. A glossary answer may need 300 words. A comparison page may need proof, nuance, objections, and internal links. A capstone guide may need enough depth to explain a worldview, defend a model, and give buyers confidence that the team behind it understands the whole system. Length becomes useful only when the buyer’s question deserves length. Marketers do not need to answer the same question six times because a brief says the page needs another 800 words. Long content can help when writers explain a complex history, build a research-backed argument, or teach a buyer how a system works. Long content becomes waste when writers use size as a substitute for specificity. Templates deserve the same treatment. A brief can help a busy editor coordinate writers, product reviewers, internal links, CTA placement, source requirements, and keyword coverage. A template can protect basic quality. A template should never become the creative target. When teams optimize the template until no one needs to think, they also remove the only thing that can make the page memorable. AI slop often looks clean because the template did its job. Buyers still feel the absence of judgment. Answer engine optimization creates the temptation to behave like every week has a new secret. Marketers hear that AI assistants cite different pages than Google rankings, that model behavior changes, that prompt fan-out matters, that YouTube can surface where a blog does not, and that brand mentions may matter in ways traditional backlink reports do not fully capture. Much of that is true enough to matter, and unstable enough to punish anyone who mistakes today’s tactic for tomorrow’s strategy. Ahrefs reported in 2026 that only about 38% of AI Overview cited pages also ranked in Google’s top 10 for the same query, while 36.7% did not rank in the top 100 blue-link results. The same research points toward fan-out query behavior, where AI systems use related sub-queries to identify useful sources. That finding should not make teams abandon SEO. It should make teams ask whether their SEO strategy covers the full question map around a buyer problem. Freshness also matters more in AI-mediated discovery. Ahrefs analyzed nearly 17 million citations across seven AI search platforms and found that AI-cited URLs were 25.7% fresher than organic SERP URLs on average. Teams should read this as an operating mandate, not a growth hack. Marketers should update claims, screenshots, examples, benchmarks, and source notes because buyers need current evidence, and AI systems often seem to reward pages that look maintained. Owned media also matters more than skeptics sometimes admit. Axios summarized Penta Group analysis reporting that roughly 60% of cited material in LLMs came from corporate-owned or business-produced sources, while noting that no one can fully pinpoint how LLMs choose sources. That caveat matters. Marketers should avoid magical claims about guaranteed AI citations. Still, the practical direction is clear enough: publish useful owned pages, make them easy to parse, keep them current, name responsible authors or experts where possible, cite sources, and support the page with credible off-site proof. AEO windows change. Strong SEO practices still form much of the terrain beneath them. Teams that want AI visibility need clean site architecture, topical coverage, evidence blocks, structured answers, internal links, off-site mentions, video and community proof where relevant, and content that answers how buyers actually ask questions. Nobody wins the AI search game by forgetting that people and crawlers both prefer pages with clear paths. Thinking about [generative AI search optimization](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) gives teams the useful, boring answer: AI visibility work still depends on crawlability, useful content, index eligibility, strong media, and pages that give visitors confidence. The new surface does not erase the old foundations. Technical SEO should not eat the whole content strategy, but content teams ignore it at their own expense. A marketer can commission the best article in the category and still bury it inside a CMS that loads critical content through fragile JavaScript, creates duplicate URLs, hides internal links, or makes conversion pages painful to update. Teams need enough technical discipline to make strong content discoverable, renderable, indexable, and commercially useful. Google’s crawl budget guidance focuses on large or frequently updated sites, but the operating lesson applies broadly: teams should keep sitemaps current, monitor index coverage, manage URL inventory, and avoid wasteful crawl paths when site scale or update frequency demands more discipline. Modern technical SEO has shifted from checklist hygiene toward governance across crawl paths, rendering, duplicate states, URL inventories, template behavior, and business measurement. For content leads, the practical technical questions are simple. Can a person publish without breaking formatting? Can search systems find the page through HTML links? Can the CMS handle landing pages, conversion pages, product pages, and blog revisions without engineering tickets for every basic edit? Can the team update old content quickly when claims age out? Can analysts connect traffic and engagement to the pages that move buyers toward pipeline? Technical SEO supports the guide, the blog, the landing page, and the call request. It should create less friction for the people doing the marketing work. ## Why Blogs Still Matter Only Inside a System Blogs still matter. They help teams explain ideas, answer questions, test language, build topical authority, support email, equip sales, and create discoverable assets that accumulate relevance over time. The problem begins when leaders ask blogs to perform every job alone. A blog can attract a reader, but the team still needs a destination that explains the product, a proof asset that lowers risk, an email or nurture path that keeps memory alive, and a conversion page that lets the buyer act. Twenty well-targeted blogs can help, but twenty blogs with one good landing page that ties them together will perform significantly better. Twenty blogs, one strong landing page, and one conversion page give buyers a path from research to belief to action. Teams should also turn the strongest material into email, social commentary, sales notes, and refresh cycles so each asset keeps earning new context after publication. This is where many content teams accidentally underbuild the middle of the system. They publish educational content, then send every reader to a generic contact form. Buyers often need a more specific bridge. A person reading about content operations should land on a page that explains [how lead capture, qualification, routing, recovery, and nurture work after the click](https://withsurface.com/product). A person reading about generative engine optimization should find a useful explanation of [generative engine optimization services](https://withsurface.com/blog/generative-engine-optimization-services). A reader who wants the broader market view can move into [current marketing updates](https://withsurface.com/blog/may-marketing-updates) or related strategic commentary. Internal links should feel like a reader’s next thought, not like someone stuffed anchor text into a paragraph five minutes before publication. Content teams should treat internal links as audience design. Search systems use them to understand relationships between pages. Buyers use them to decide whether the company understands their problem deeply enough to guide them forward. Sales teams use them when a prospect asks the same question for the sixth time. A content system becomes commercially useful when all three audiences can move without confusion. Everyone wants to be a thought leader because AI made the props cheap. Anyone can generate a research-style infographic, an executive LinkedIn post, a contrarian thesis, or a “state of the industry” draft. That ease makes the actual standard higher. Buyers do not need more people standing in front of synthetic scenery and calling themselves original. Buyers need someone who has spent enough time with the problem to say something useful, specific, and slightly risky. True thought leadership does not require a founder to reinvent the industry every Thursday. Many teams confuse expertise with spectacle. A company can earn trust by explaining the obvious thing with unusual clarity, by documenting a customer pattern, by admitting a limitation, by showing where a common workflow breaks, or by helping a buyer understand a decision they already feel but cannot yet articulate. Personal POV can outperform generic commentary when a real person cares about the audience and knows the category well enough to hold a conversation. Teams should also stop asking templates to impersonate perspective. AI can accelerate research, repurpose old assets, identify gaps, and help editors compare structure across pages. People still have to decide what is worth saying. People still have to hear the customer’s frustration, understand the internal sales handoff, recognize the category joke, and know which claim sounds impressive but fails under pressure. Tools do tool work. People do judgment work. Google’s people-first guidance gives marketers a useful external standard here because it asks whether content provides original reporting, research, analysis, or additional value rather than simply copying or rewriting sources. Buyers use a less formal version of the same test. They may not name E-E-A-T, but they know when a page gives them something they could not get from the first three search results pasted into a prompt. ## What We Mean by Content Operations We use Content Operations to describe the whole system that turns strategic thinking into published, measured, revised, and commercially useful content. The work includes a content management system, blog revision workflows, visibility dashboards, results dashboards, strategic insights, publishing governance, internal linking discipline, and the editorial judgment needed to keep the machine from producing average work at impressive speed. That work exists for the content lead who has too many tabs open and not enough operators, for the solo marketer carrying strategy, writing, CMS, analytics, and reporting at the same time, and for the GTM leader who needs content to support pipeline rather than decorate a website. Strong content operations build the connective tissue between SEO, AEO, AI visibility, owned media, email, sales enablement, and conversion paths. The quiet promise is straightforward. Teams should not have to choose between search visibility and brand voice, between AI-aware structure and human usefulness, between publishing cadence and quality, or between strategic clarity and operational output. A serious content operation should serve every one of those goals because the audience landscape already includes every one of those goals. A buyer path does not end with a blog. Someone reads, compares, leaves, returns, fills a form, waits, receives follow-up, and decides whether the company feels credible enough to talk to. Improving [the form at the center of the funnel](https://withsurface.com/blog/the-form-is-the-most-underinvested-part-of-the-funnel) can matter as much as improving the article that drove the visit. Fixing [inbound lead management](https://withsurface.com/blog/inbound-lead-management) can matter as much as winning another keyword. Reviewing [B2B lead conversion benchmarks](https://withsurface.com/blog/b2b-lead-conversion-benchmarks-for-2025) can help teams understand whether visibility is turning into qualified demand. Teams that want to turn content from an archive into an operating system can review [pricing and package options](https://withsurface.com/pricing) or [book a demo](https://withsurface.com/book-a-demo). ### What is the best content marketing strategy for 2026? The best content marketing strategy for 2026 combines classic SEO, AI-search visibility, owned media, expert perspective, internal linking, and conversion architecture. Teams should publish consistently, refresh evidence, map content to buyer intent, and connect blogs to landing pages, proof pages, email, sales enablement, and lead operations. ### How many blogs should a company publish each week in 2026? Most lean B2B teams should publish one to three high-quality pieces per week. One good blog per week keeps the program alive, two is strong, and three is usually enough. Quality, review, distribution, and conversion discipline often fall off when teams try to exceed three high-quality weekly pieces without the right operating support. ### Does AEO replace SEO? AEO does not replace SEO. AI search creates new visibility windows, but teams usually win those windows through strong SEO foundations: crawlable pages, useful content, topical coverage, internal links, structured answers, fresh evidence, brand authority, and off-site proof. ### Do blogs still work for B2B marketing? Blogs still work when teams connect them to a broader content system. A blog can create visibility and educate a buyer, but teams need landing pages, conversion pages, proof assets, email, sales enablement, and measurement to turn attention into pipeline. ### Is longer content better for SEO and AI visibility? Longer content helps only when the question deserves depth. A glossary answer may need a few hundred words, while a definitive guide may need several thousand. Teams should match content length to intent rather than fill pages with repeated answers. ### How should companies use AI in content marketing? Companies should use AI to accelerate research, repurposing, editing, structural analysis, and revision. People should still own judgment, voice, claims, examples, customer understanding, and final editorial accountability. ### What is Content Operations? Content Operations is the system that manages strategy, production, CMS workflows, revision, analytics, AI visibility, internal linking, publishing governance, and conversion reporting so content teams can create useful assets consistently instead of managing one-off deliverables. --- # Content Marketing Strategy: The Quality vs. Volume Trap in AI-Era Publishing | Surface Labs URL: https://surface.thesurface.network/blog/content-marketing-strategy-the-quality-vs-volume-trap-in-ai-era A marketing lead opens the calendar on Monday morning and sees the same argument sitting in three different tabs. The founder wants more articles because competitors seem louder. The content lead wants fewer articles because every draft now needs expert review, source checks, internal links, distribution copy, and a reason to exist beyond filling another slot on the CMS. That argument has become the central [content marketing strategy](https://withsurface.com/blog) problem of the AI era. Teams can publish more than ever, but readers, search systems, and AI answer engines have become less patient with generic output. Marketers need enough volume to learn, enough quality to earn trust, and enough operational discipline to make every page lead somewhere useful. ## Content Marketing Strategy Now Has to Defend Reach and Trust For years, marketers treated publishing cadence as the visible proof that a content program existed. Teams built calendars, assigned writers, mapped keywords, and tried to show that the website was alive. Consistency still matters, but content leaders now have to defend a more complicated system because discovery happens across Google, AI answers, communities, newsletters, social feeds, and internal sales conversations. Content Marketing Institute’s 2026 B2B research shows why the argument has shifted. B2B marketers plan to invest most heavily in AI tools, events, and owned media, which means leaders now see content as a system for trust, presence, and reusable proof rather than a blog queue by itself. Google’s helpful content guidance pushes the same direction from the search side because Google asks creators to make content that benefits people first, rather than content written primarily to manipulate rankings. We believe that [lead journey tracking](https://withsurface.com/product) should begin the moment a reader shows intent, not after a rep manually pieces together what happened. A page can earn the click and still fail the business if the reader has nowhere useful to go next. Reach matters, but reach needs a path into capture, qualification, routing, recovery, nurture, and conversion. ## Content Marketing Strategy Fails When Teams Confuse Publishing With Coverage A team can publish forty articles and still leave the buyer stranded. One article might define a category, another might compare two approaches, another might explain implementation risk, and another might help a sales rep answer a late-stage objection. When marketers plan those pages as connected pieces of a buyer path, they create coverage. When marketers publish them as isolated acts of output, they create inventory. AI search makes that distinction sharper. Ahrefs researchers found that AI Overview citations do not simply mirror the classic top ten organic results, and other AI visibility studies keep pointing toward freshness, evidence, structure, and topic coverage as practical levers. In plain English, marketers cannot rely on one giant article to answer every possible question, and they cannot rely on twenty thin rewrites to prove authority. They need a cluster that helps a human understand the topic and helps a retrieval system identify the page as useful, current, and citable. Thinking about [generative engine optimization services](https://withsurface.com/blog/generative-engine-optimization-services) gives marketers a useful way to understand the shift. The real work is less about chasing a new acronym and more about building content systems that make a company easier to understand, cite, and trust. A good AI-era content cluster needs one clear destination, supporting articles, useful evidence, and internal links that guide readers toward the next serious question. ## Content Marketing Strategy Should Balance Cadence, Evidence, and Conversion Paths Good content strategy starts with a business question before it starts with a keyword list. Leaders should ask what the company needs this quarter. A team with strong close rates may need more qualified discovery traffic. A team with weak handoffs may need comparison pages, sales enablement pages, and proof assets that reduce doubt before a rep enters the conversation. A team with a messy funnel may need better capture, qualification, routing, and nurture before more traffic can help. Content can earn attention, but marketing operators still have to turn that attention into usable pipeline. When readers arrive from search or AI-assisted discovery, teams need forms that capture intent, workflows that qualify leads, routes that move real buyers to the right person, and follow-up systems that prevent good demand from cooling while teams argue about attribution. This is why content pages should connect naturally to conversion infrastructure. A reader studying AI visibility may need to understand [what Google’s new guidance changes about generative AI search optimization](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act). A reader thinking about funnel performance may need clearer [B2B lead conversion benchmarks](https://withsurface.com/blog/b2b-lead-conversion-benchmarks-for-2025). A buyer who already understands the pain may need to [book a demo](https://withsurface.com/book-a-demo) instead of reading another educational article. Some teams protect quality so aggressively that they stop publishing. A draft waits for the founder, then product, then legal, then customer success, then the agency, then the founder again. Four weeks pass. The topic gets stale, the keyword window narrows, and the team learns nothing from the market because the team never shipped anything. Quality standards should protect the reader from vague claims, lazy summaries, fake expertise, and outdated information. They should not require every post to transform the future of the category. Buyers still need clear answers to normal questions. A useful comparison, a specific implementation guide, a careful glossary page, or a tight objection-handling article can perform better than a grand thought leadership manifesto if the page answers the query and moves the reader to the next step. A strong [marketing blog](https://withsurface.com/blog) uses quality as a publishing discipline rather than a publishing blocker. Each article should be specific enough to matter, sourced enough to trust, internally linked enough to guide the reader, and operational enough to support the funnel after publication. AI tools made volume feel cheap, so many teams started treating scale as a shortcut to authority. The problem shows up a few months later. Pages begin sounding interchangeable, internal links point nowhere strategic, claims get thinner, and sales teams stop trusting the blog because the content feels disconnected from actual buyer conversations. Volume also creates a classification problem. When a company publishes heavily in one corner of its expertise and lightly everywhere else, search systems and AI systems may learn a distorted version of the business. Leaders should not let the easiest topics dominate the site just because writers can produce them quickly. A content calendar should reflect business priority, buyer demand, and topical depth together. Internal linking can either fix that distortion or make it worse. A site that publishes every article into the same flat blog archive asks readers and crawlers to infer the structure alone. A site that links educational pages into landing pages, customer proof, conversion benchmarks, and demo paths gives every audience a clearer map. Healthy volume looks less like a flood and more like a steady trail. A small team can usually sustain one strong article per week. A mature team with a clear review workflow can often sustain two. A team with dedicated research, editing, product access, design support, and publishing operations can usually sustain three without letting quality drop. Beyond that, leaders should ask whether the fourth article creates new strategic coverage or simply gives the calendar another thing to count. Orbit Media’s 2025 blogging data gives leaders a useful counterweight to both extremes. Average posts have grown longer over time, and marketers who publish very long posts report strong results at higher rates, but teams still need to match format to intent. A precise question may deserve 700 words. A market history, research report, or category thesis may deserve 2,000 words. The best content marketing strategy does not worship length. It gives the reader enough substance to make a better decision. A practical internal-linking rule helps here: every article should know its next destination. Some posts should send readers toward [customer stories](https://withsurface.com/customers/overview), especially when the claim needs proof. Some should send readers toward [pricing](https://withsurface.com/pricing), especially when the reader has moved from education into evaluation. Others should send readers deeper into [current marketing updates](https://withsurface.com/blog/may-marketing-updates), when the reader needs a broader market frame before they are ready to act. ## Where AI Belongs in the Content Marketing Strategy System Marketers should use AI tools to accelerate the parts of content work that tools can reasonably support. Teams can use AI for research organization, source clustering, transcript cleanup, outline variation, internal-link audits, refresh detection, and repurposing. Editors should still own the point of view, source judgment, examples, claims, and final argument because readers can feel the difference between a useful page and a page that merely satisfied a prompt. Google has said that AI-generated content can fit within its broader approach when creators use it to produce helpful content for people. That distinction matters. AI assistance should raise the floor of research and production. People should raise the ceiling of taste, specificity, and trust. Content teams do not need more disconnected drafts. They need a content and lead operations system that turns articles, guides, comparison pages, proof assets, and conversion paths into a measurable route from attention to pipeline. ## A Practical Content Marketing Strategy Operating Model Start with a core topic that matters to revenue. Build one authoritative landing page or guide that explains the category. Add six to ten supporting articles that answer the fan-out questions buyers and AI systems are likely to ask. Refresh the cluster quarterly with new data, customer examples, product screenshots, and better internal links. Package the strongest ideas into email, social, sales notes, and customer-facing proof. Then measure more than pageviews. Track qualified form submissions, assisted pipeline, demo quality, repeat engagement, sales usage, AI citations where available, and source mix. A team that grows traffic while confusing sales has not solved the business problem. A team that earns fewer visits but creates clearer buyer paths may create more revenue because the right people understand the next step. A simple content architecture might look like this: - One strategic guide or landing page for the core category. - Six to ten supporting blog posts answering buyer questions. - One or two proof pages or customer stories connected from the highest-intent articles. - One conversion path that points qualified readers toward pricing, demo booking, or a relevant product page. - One refresh cycle that updates source notes, screenshots, examples, and links before the cluster goes stale. This model works because it respects how people actually move. A reader may begin with a blog post, compare a few options, read a proof point, check pricing, leave, return, and then request a demo. Good internal linking does not force that journey. It makes the journey available. Commercial content should also connect the article to the post-click system. A reader who needs to understand the platform can move into [lead capture, qualification, routing, recovery, and nurture](https://withsurface.com/product). A reader focused on conversion leakage can study why [the form is often the most underinvested part of the funnel](https://withsurface.com/blog/the-form-is-the-most-underinvested-part-of-the-funnel). A reader trying to fix the whole handoff can use an [inbound lead management playbook](https://withsurface.com/blog/inbound-lead-management). A reader who needs proof can review how [Nextiva used a better lead capture experience to improve conversion](https://withsurface.com/customers/nextiva). ## Final Thought on Content Marketing Strategy The quality versus volume debate becomes less frustrating once leaders stop treating it like a moral contest. Marketers should publish enough to learn from the market and carefully enough that readers can trust the work. In the AI era, teams win by creating a publishing system that is steady, sourced, specific, connected, and built for conversion after the first moment of attention. Teams that already earn attention but struggle to turn that attention into qualified demand can [book a demo](https://withsurface.com/book-a-demo) to see how better capture, qualification, routing, recovery, nurture, and conversion paths work after the click. --- # Content Production: How Many Blogs Should You Publish Each Week? | Surface Labs URL: https://surface.thesurface.network/blog/content-production-how-many-blogs-should-you-publish-each-week A content lead starts the week with eleven requests. The founder wants a daily blog because AI can draft quickly. Sales wants comparison pages because prospects keep asking the same questions. Product wants launch support. The marketer wants a calendar that does not require everyone to pretend that review cycles, source checks, CMS formatting, internal links, and distribution magically happen between meetings. Most teams should publish one to three blogs per week. One strong blog per week gives a small team a real cadence. Two strong blogs per week gives a growing team enough momentum to build topical coverage. Three strong blogs per week usually marks the practical ceiling before quality, review capacity, distribution, and conversion planning start to suffer. ## Content Production Should Match the Team’s Review Capacity The right publishing frequency depends less on how fast someone can draft and more on how well the team can review, improve, publish, distribute, and learn from the work. A writer can produce words quickly. A team still has to confirm that the page answers the right query, reflects current product truth, uses credible sources, links to the right destination, supports a business goal, and gives a reader a useful next step. Leaders often calculate cadence from writing capacity alone. They should calculate cadence from the slowest honest bottleneck in the system. If product reviewers take five days, the team cannot safely run a high-volume product-led content program without changing the review process. If the CMS requires a developer for every page, the team cannot publish three pieces a week without paying an operational tax on every draft. We believe that [lead capture, qualification, routing, recovery, and nurture](https://withsurface.com/product) belong in the same planning conversation as content cadence. Publishing frequency only matters when the team can turn attention into a useful buyer path. A blog calendar that produces traffic without capture, qualification, or follow-up creates activity without enough operational value. ## Content Production Works Best When Cadence Supports Quality Control Cadence gives a content team structure. Quality control gives that cadence a reason to continue. Google asks creators to publish helpful, reliable, people-first content, and Google’s AI content guidance focuses less on the tool used to create content and more on whether the final page helps people. That means leaders should judge AI-assisted output by usefulness, evidence, clarity, and human review rather than by whether the first draft arrived quickly. A weekly rhythm also protects teams from the two easiest mistakes. Some leaders delay every page until the draft feels perfect, which stops the team from learning. Other leaders ship whatever the prompt produced, which teaches readers and search systems that the site does not deserve much trust. The best cadence creates a repeatable middle path: publish consistently, preserve standards, and revise based on evidence. Thinking about [B2B lead conversion benchmarks](https://withsurface.com/blog/b2b-lead-conversion-benchmarks-for-2025) gives teams a practical way to keep content quality tied to business outcomes. A page does not only need to be readable. It needs to support a measurable path from visitor to lead, lead to meeting, and meeting to qualified pipeline. ## Content Production Needs a Weekly Rhythm, Not a Panic Sprint Bulk publishing tempts teams because a sprint feels productive. A group can ship twenty articles in two weeks and finally clear the backlog. The problem begins after launch, when nobody has distribution bandwidth, internal links remain shallow, conversion paths stay generic, and the team loses the habit of learning from each page because every post arrived at once. A steady weekly rhythm lets marketers observe which topics attract qualified readers, which internal links get clicks, which pages sales uses, which CTAs perform, and which articles deserve refreshes. Content production should create feedback, not merely inventory. Teams that publish steadily can adjust the system while the market responds. A mature [marketing blog](https://withsurface.com/blog) should function less like an archive and more like a connected operating system. Each article should know whether it is answering a question, building trust, supporting sales, moving readers toward proof, or helping a high-intent buyer understand the next step. One blog per week works for small teams, founder-led marketing programs, and companies that need quality control from product or legal. A weekly article gives the site fifty-two new or refreshed assets across a year, which is enough to build visible topical depth when the team chooses topics carefully and links them into a coherent path. Two blogs per week works for teams with clear briefs, reliable reviewers, and a decent publishing process. That cadence lets marketers build a pillar and supporting cluster at the same time, or pair one educational post with one comparison, case study, or operational guide. Two per week also gives teams enough volume to learn without forcing every article to carry the whole content program. Three blogs per week works when leaders have dedicated editing, product access, a reliable CMS, and a distribution workflow. Three per week can help a team build topical coverage quickly, especially when the company needs to show up across AI search, classic search, and buyer education at the same time. Most teams should treat three as the point where they need stronger operations before they add more output. After that recommendation, teams should ask one operational question before adding another post: can the funnel actually use the attention? If the answer is unclear, study whether [existing leads are failing to convert](https://withsurface.com/blog/you-re-getting-enough-leads-you-re-just-not-converting-them) before turning the content calendar into a larger machine. ## Why More Than Three Blogs Often Loses Efficiency A fourth or fifth weekly blog may still help a large team, but smaller teams should ask what they lose. They may lose source quality because nobody has time to verify claims. They may lose voice because editors rely too heavily on templates. They may lose distribution because every post gets one generic social share. They may lose conversion value because nobody updates the form, CTA, landing page, or nurture path connected to the article. Orbit Media’s 2025 blogging research reported that marketers spend just under three and a half hours on a typical article on average, while other summaries of the same research show that longer posts can correlate with stronger reported results. Those findings should not push teams toward long content for every query. They should remind leaders that content production takes real time, even when AI compresses early drafting. Higher output also increases the risk of broken internal architecture. A team that publishes five disconnected articles per week can accidentally train readers, crawlers, and AI systems to see the site as a pile of loosely related pages. A team that publishes fewer, stronger articles with clear internal paths can help every page contribute to category understanding, buyer confidence, and conversion. ## How to Choose the Weekly Blog Mix A good weekly mix should match the company’s current constraint. If readers do not understand the category, publish educational explainers. If buyers keep comparing alternatives, publish comparison pages and objection-handling articles. If sales lacks proof, publish customer stories, use-case pages, and operational examples. If AI systems do not cite the company, publish clearer answer pages with better structure, fresher source notes, and more explicit evidence. For a two-post week, marketers can pair one demand-building topic with one conversion-supporting topic. For a three-post week, they can add one refresh or one distribution-friendly thought leadership piece. Refreshes matter because AI-assisted discovery appears to reward freshness in many contexts, and human readers certainly reward pages that do not feel abandoned. Thinking about [AI citations vs. SEO rankings](https://withsurface.com/blog/ai-citations-vs-seo-rankings) gives marketers another reason to plan by topic coverage rather than raw volume. AI visibility rewards pages that can be retrieved, understood, cited, and connected to related questions. That means the weekly mix should build a map, not only a feed. ## When Teams Should Publish Fewer Blogs Teams should publish fewer blogs when product messaging changes weekly, when subject-matter experts cannot review, when the CMS makes publishing fragile, when sales ignores the content, when the website lacks conversion destinations, or when the team cannot explain what last month’s posts accomplished. A reduced cadence can be a sign of discipline if leaders use the time to fix the system. Publishing fewer blogs can also help teams create stronger assets. A company may need one authoritative category page, one customer story, one comparison page, and one email sequence more than it needs four additional blog posts. Content production should serve the business path, not the calendar ego. Fewer blogs can also reveal whether the post-click experience is doing its job. If a high-intent article sends readers to a weak form, a slow response, or a generic follow-up, more content will mostly create more leaked demand. Improving [the form at the center of the funnel](https://withsurface.com/blog/the-form-is-the-most-underinvested-part-of-the-funnel) may produce more pipeline than adding another article to the queue. ## When Teams Can Publish More Blogs Teams can publish more than three blogs per week when they have a real editorial operation. That means clear briefs, expert access, stable templates, QA support, source requirements, internal-link ownership, distribution plans, conversion paths, and analytics that connect page behavior to qualified demand. Large teams can also support higher frequency when they divide work by topic cluster and maintain consistent quality gates. Even then, leaders should avoid publishing many disconnected pages at once. Search systems and readers both benefit from coherent paths. A high-output team should organize production around clusters, refresh cycles, and business priorities rather than letting volume drift toward whatever topics writers can finish fastest. Teams that have the operating maturity to publish more should also have the revenue infrastructure to handle more demand. That means faster routing, better qualification, clearer rep context, and cleaner recovery when a buyer starts but does not finish a form. Strong [inbound lead management](https://withsurface.com/blog/inbound-lead-management) keeps high-output content from overwhelming the people who have to turn interest into meetings. Marketers should use AI tools to make content production less wasteful. AI can summarize calls, compare drafts against briefs, identify missing questions, suggest internal links, assemble source notes, produce distribution variants, and flag stale pages for refresh. Those tasks help people spend more time on judgment. Editors should still decide whether the argument is true, whether the example is specific enough, whether the tone sounds like the company, whether the claim deserves a source, and whether the page points the reader to a useful next action. AI can help the team move faster, but people still have to protect the reason a buyer would trust the work. AI also makes internal linking easier to audit, but people should still decide whether the link feels like the reader’s next thought. A link should not exist because a keyword appeared nearby. It should exist because the reader would naturally need the next page. ## A 12-Week Content Production Model for Small Teams For most Surface readers, a practical 12-week model starts with one weekly anchor article, one weekly refresh or distribution package, and one monthly conversion asset. After four weeks, leaders should review which topics attracted qualified visitors, which pages created form fills, which questions sales repeated, and which internal links helped readers move to the next step. If the team can sustain that model without heroic effort, leaders can add a second weekly blog. If the team can sustain two weekly blogs for another month while keeping quality high and routing leads cleanly, leaders can test three. A content production system should earn higher volume through operational proof, not through optimism. A 12-week model can follow a simple pattern: - Weeks 1 to 4: publish one anchor article per week, refresh one old page, and connect each article to a relevant conversion path. - Weeks 5 to 8: add a second weekly article only if review, publishing, and distribution are stable. - Weeks 9 to 12: test a third weekly article only if the team can still maintain source quality, internal links, and lead handling. - End of quarter: review qualified traffic, form submissions, booked meetings, sales usefulness, internal-link clicks, and refresh needs. The model should also include proof. Readers who need confidence should be able to move from educational content into [customer stories](https://withsurface.com/customers/overview), and teams that need an example of conversion impact can study how [Nextiva improved conversions by 37%](https://withsurface.com/customers/nextiva). ## Final Thought on Content Production The useful answer is simple because the execution is hard. Publish one strong blog per week if the team is small. Publish two if the review and publishing system is reliable. Publish three if the team has real operations behind the calendar. Publish more only when the content system can keep quality, distribution, and conversion value intact. Teams that already have publishing momentum should make sure the next click has somewhere useful to go. Compare [pricing and package options](https://withsurface.com/pricing) when the team needs to connect content production with capture, qualification, routing, recovery, nurture, and measurable conversion. Or [book a demo](https://withsurface.com/book-a-demo) to see how publishing attention can become qualified inbound demand. --- # Content publishing workflow: Move from approval to measurement | Surface Labs URL: https://surface.thesurface.network/blog/content-publishing-workflow-approval-measurement ## Content publishing workflow: Move from approval to measurement A finished article sits in a document with two approvals, seventeen resolved comments, and no publication date. When someone finally copies it into the CMS, the table breaks, three internal links disappear, the canonical field stays blank, and the campaign launches before analytics is checked. The writing was approved. The content system was not ready. Carrying the reason a page exists all the way into production, a content publishing workflow should keep going until the team knows what happened. Approval is one control in that sequence. Treating it as the finish line leaves strategy, technical quality, distribution, conversion, and learning to chance. ## Content publishing workflow summary From initial evidence through future revision, a content publishing workflow governs how an idea moves into a brief, draft, review, technical preparation, CMS publication, distribution, and measurement. It defines the required information, owners, permissions, quality checks, handoffs, and system records at each stage. When every stage defines what "ready" means, publishing usually moves faster. Speed does not require removing judgment. Direct publishing should eliminate manual copying and repeated setup while preserving approval gates, version history, source context, access rules, rollback, and accountability. Surface's [content operations system](https://www.withsurface.com/solutions/launch-campaigns-faster) turns buyer evidence into briefs and connected assets, then requires a person to approve what can ship. Surface works alongside an existing CMS rather than forcing the company to replace it. That separation lets the content team improve planning, creation, governance, and measurement while the CMS remains the public delivery layer. ## A content publishing workflow must preserve the brief Treat the brief as structured information rather than an attachment nobody opens after the first draft. At minimum, retain the page's strategic job, audience, primary query, buyer intent, point of view, required claims, sources, internal-link targets, CTA, product relationship, owner, reviewer, and measurement plan. Our guide to [writing stronger content briefs](https://www.withsurface.com/blog/what-is-a-content-brief) calls the brief a decision record. That framing becomes more important when AI agents or multiple specialists participate. A model can infer why a page exists, but inference is a poor substitute for the decision the team made. Carry those fields into drafting and review. If a reviewer changes the audience, claim, or product position, update the record rather than leaving the decision inside a comment thread. The published version should be traceable to the approved sources and reasoning that produced it. ## A content publishing workflow separates review types One generic approval box hides several different responsibilities. Editorial review checks argument, usefulness, structure, voice, and repetition. Subject review checks the product, technical, legal, customer, and competitive claims. SEO and AI-search review checks intent, crawlability, answer clarity, source support, internal links, and content architecture. Production review checks the actual rendered page. Assign the lightest valid review path for the risk involved: Content type Required reviewers Extra control Evergreen educational article Editor and subject owner Source and internal-link check Product or implementation guide Editor, product owner, and technical reviewer Current screenshots, version, and capability validation Comparison or buyer guide Editor and factual reviewer Commercial disclosure, equal criteria, primary-source verification, and review date Customer story Editor, account owner, and customer approver when required Approved claims, quote language, and evidence record Regulated or high-risk claim Editor, subject owner, and legal or compliance reviewer Restricted permissions and explicit publication sign-off Not every comma needs a committee. The workflow should route risk to the right person and let routine changes move without a ceremonial meeting. Documenting the escalation path also prevents an unresolved high-risk question from disappearing into a routine approval queue. ## A content publishing workflow needs a production contract CMS work begins before anyone opens the CMS. Define the fields and checks that make a page publishable: title, slug, description, author, category, heading hierarchy, canonical URL, index directives, structured data, images and alt text, source links, internal links, CTA, publication date, factual review date, and analytics tags. Google's guidance for [AI features in Search](https://developers.google.com/search/docs/appearance/ai-features) still asks sites to make important content crawlable, indexed, findable through internal links, available in textual form, and consistent with visible structured data. Those are production requirements. A brilliant draft can fail them during rendering or template assembly. Preview the real page on representative screen sizes. Verify that links point where their anchors promise, tables remain readable, images do not carry essential text alone, and important content exists in the rendered HTML. The [SEO-friendly CMS checklist](https://www.withsurface.com/blog/seo-friendly-cms-what-content-teams-need-before-they-start) explains why crawlability and editorial clarity often collapse into the same publishing problem. Direct publishing connects an approved content system to the CMS through an integration or API, reducing copy-and-paste work. It should not mean that any generated draft can make itself public. Define permissions by content type, environment, user, and action. In practice, a safe path includes a draft destination, named approval, preflight validation, publication log, final URL confirmation, and rollback procedure. High-risk pages may always require a human click. Low-risk metadata corrections might publish after automated checks and a narrower approval. The system should show what it will change before it changes it. [Surface's build-your-own agent workflow](https://www.withsurface.com/platform/build-your-own) makes the stop condition explicit: teams define the outcome, context, guardrail, and approval before the agent runs. The same principle applies to direct publishing. Autonomous is a poor product requirement. Controlled completion is much more useful. Do not publish first and decide what success means later. The brief should name the baseline, primary business question, observable events, review window, and owner before the URL goes live. Confirm that analytics, Search Console ownership, form events, campaign parameters, and CRM handoffs can support that plan. Discovery metrics may include rankings, impressions, clicks, appearing pages, AI citations, mentions, recommendation share, and source diversity. Experience metrics can include engaged visits, related-page movement, CTA use, form starts, and return behavior. Business measures may include qualified leads, sales acceptance, opportunities, pipeline, and asset use in active deals. Google recommends combining [Search Console and Analytics data](https://developers.google.com/search/docs/monitor-debug/google-analytics-search-console) because one system describes discovery and the other describes on-site behavior. Surface extends that view through [Traffic Intelligence](https://www.withsurface.com/platform/infrastructure/traffic-intelligence), connecting content and campaign activity to form movement, buyer quality, and revenue outcomes while keeping observed events distinct from attributed or inferred influence. Set the factual review date and performance check when the page publishes. A technical update might need review after a product release. A buyer guide may require a quarterly competitor check. An evergreen explanation can wait longer unless search, citations, conversion, or sales feedback changes sharply. At review, choose a real action: keep, revise, redistribute, consolidate, reposition, or retire. Record the evidence and the version that follows. That closes the loop and gives the next brief a history instead of asking the team to rediscover what happened. A content publishing workflow should make good judgment easier to carry into production and easier to learn from afterward. If your team has strong drafts trapped between documents, approvals, CMS work, and disconnected reporting, [book a Surface walkthrough](https://www.withsurface.com/book-a-demo) and map one real publishing path from evidence to measured outcome. --- # Creating CRM Deals With 10x Less Effort | Surface Labs URL: https://surface.thesurface.network/blog/creating-crm-deals-with-10x-less-effort **The middle school version:** You know how annoying it is to fill out a long form at the doctor's office? That's what creating a "deal" in a CRM feels like for salespeople — lots of clicking, typing, and copying stuff from one place to another. With Surface, you just TELL the AI what happened (like talking to a friend) and it creates the whole deal for you. It fills in the company name, the deal amount, the stage, the contact — everything. It's like having a personal assistant who never gets tired. ## The CRM data entry tax Every sales rep knows this feeling. You just had a great call. The prospect is interested, the deal is real, and you need to log it in Salesforce before you forget the details. So you open Salesforce, click "New Opportunity," and spend the next 8 minutes filling in fields. Account name — is it already in the system? Search. Find the wrong one. Search again. Create a new one. Contact name — link it to the account. Deal name — type something descriptive. Stage — pick from the dropdown. Amount — estimate based on the conversation. Close date — guess. Product interest — another dropdown. Source — where did this lead come from again? Notes — try to remember what they said. 8 minutes per deal. Our reps create 15–25 deals per week. That's 2–3 hours per week per rep on data entry. Across a 10-person team, that's 20–30 hours per week — nearly a full headcount — spent typing into CRM fields instead of selling. And the data quality is terrible anyway. Reps rush through the fields. Close dates are always wrong. Amounts are rough guesses. Notes are sparse because nobody wants to type a paragraph after every call. After a call, a rep tells Surface what happened — in natural language: _"Just had a great call with Sarah Chen at Acme Corp. They're a 200-person SaaS company looking to replace their Zapier-based lead routing. Budget is around $30K, they want to start next quarter. She's the VP of Marketing and the decision-maker. Needs to get VP of Sales buy-in."_ Surface takes that input and creates a fully populated CRM deal: CRM field What Surface fills in Where it gets the data Account name Acme Corp Extracted from input. Matched to existing account or created new. Contact name Sarah Chen Extracted. Linked to account. Title populated from enrichment. Contact role VP of Marketing — Decision Maker Extracted from "she's the VP of Marketing and the decision-maker." Deal name Acme Corp — Lead Routing Platform Generated from company + use case. Amount $30,000 Extracted from "budget is around $30K." Stage Discovery / Qualified Inferred from conversation description — they've had an initial call. Close date Q2 2026 Inferred from "wants to start next quarter." Product interest Lead routing Extracted from "looking to replace their Zapier-based lead routing." Next steps Get VP of Sales buy-in Extracted from "needs to get VP of Sales buy-in." Notes Full conversation summary with key details preserved Generated from the complete input. Source Outbound — cold email reply Pulled from Surface's existing lead data if the contact exists. The rep reviews the populated deal for 30 seconds, confirms or edits anything that needs adjusting, and saves. Total time: under 2 minutes. Down from 8. **Duplicate contacts.** Surface checks the CRM before creating anything. If Sarah Chen at Acme Corp already exists, Surface links to the existing contact and account — it doesn't create duplicates. If there's a similar but not exact match ("S. Chen" vs. "Sarah Chen"), Surface flags it for the rep to confirm. **Missing fields.** If the rep's input doesn't mention a close date, Surface doesn't guess randomly. It either infers from context ("next quarter" = Q2 2026) or leaves the field empty with a reminder for the rep to fill in later. Partial accuracy is better than confidently wrong data. **Multi-threaded deals.** Enterprise deals often have multiple contacts. The rep can mention several: "Spoke with Sarah, the VP of Marketing. She's bringing in James Park, their VP of Sales, and Dave from procurement." Surface creates contact records for each, links them to the deal with appropriate roles, and flags the ones that need enrichment. **Existing pipeline.** If a deal already exists for Acme Corp, Surface recognizes the account and asks whether this is an update to the existing deal or a new opportunity. It doesn't blindly create duplicates. When we rolled this out, we tracked how reps spent the 2–3 hours per week they got back. The answer was almost entirely more selling activity — more follow-up calls, more pipeline management, more deal advancement. Activity Before (weekly per rep) After (weekly per rep) CRM data entry 2.5 hours 0.5 hours Follow-up calls 12 18 Discovery calls 8 10 Pipeline review 1 hour 1.5 hours The 2 hours of saved admin time translated into 6 additional outbound activities per rep per week. Across the team, that's 60 additional touches per week — which compounds into pipeline. But the bigger win was data quality. Because the AI captures details from natural language — including nuances the rep would normally skip in a manual entry — the deal records are actually more complete and more accurate. Notes are richer. Close dates are better calibrated. And because it takes 2 minutes instead of 8, reps actually do it after every call instead of batching at end of day and forgetting half the details. The setup is straightforward: connect Surface to your CRM (Salesforce, HubSpot, Pipedrive). Map your deal fields — which ones are required, which are optional, and what the valid values are for dropdowns and picklists. Surface learns your field structure and uses it to populate deals accurately. No custom development. No Apex triggers. No workflow chains. The AI handles the translation from natural language to structured CRM data. **Give your sales team hours back every week. See AI-powered deal creation in Surface.** --- # The Creator Is Becoming the Marketing Department | Surface Labs URL: https://surface.thesurface.network/blog/creator-is-becoming-the-marketing-department The measurement problem is sitting underneath the creator economy. Marketers continue describing creators as a media channel even as the most capable creators perform work that once belonged to research, creative, brand, social, product marketing, community, events, and commerce teams. The category is expanding beyond influencer marketing because creators offer more than rented attention. They bring accumulated audience understanding, recognizable judgment, production capability, distribution, cultural context, and a direct feedback loop with the people brands want to reach. McKinsey described creators as a new growth engine after Cannes Lions 2026, noting that more than 500 creators attended the festival and that creator activity now reaches across discovery, consideration, conversion, and loyalty. ([mckinsey.com](http://mckinsey.com/)) The creator is not literally replacing the entire marketing department. The more useful point is that creators increasingly reveal how fragmented marketing work fits together. They understand an audience, develop a point of view, choose a format, make the asset, distribute it, interpret the response, and adjust the next release. Most brands divide that loop among six teams and a quarterly planning process. The traditional influencer campaign is straightforward. A brand identifies creators with access to a desired audience. It negotiates deliverables, sends a brief, approves the work, publishes during a campaign window, and evaluates reach, engagement, clicks, or attributed sales. That model remains useful for launches, promotions, events, and moments requiring concentrated attention. Its weakness is that it treats the creator primarily as inventory. The brand develops the strategy. The agency selects the roster. The creator translates the approved message into a platform-native asset. Once the campaign ends, the relationship often goes quiet until another budget appears. Marketing Brew recently interviewed Collectively CEO Natalie Silverstein, who contrasted that campaign model with a creator-first approach. In her description, creators are embedded continuously across the go-to-market system, from flagship partnerships to affiliates, rather than assembled for an isolated activation and dismissed six months later. ([marketingbrew.com](http://marketingbrew.com/)) The difference is structural. A campaign asks, “Which creator can distribute this message?” A creator-first system asks: - Which creators understand this audience? - What are they seeing before our research captures it? - Which ideas can we develop together? - Where should creator judgment influence the product or positioning? - How can one relationship accumulate trust over time? - Which commercial model gives both parties a reason to keep investing? That approach requires more than a larger influencer budget. It changes how the company creates marketing. A good creator has an ongoing research environment. Every video, newsletter, post, podcast, live event, and comment section produces evidence. The creator sees which questions repeatedly appear, where the audience becomes confused, what language people use, which jokes travel, which objections feel sincere, and which supposedly important subjects produce silence. Traditional research can capture some of this information. Surveys, interviews, search data, support tickets, sales calls, and community analysis remain essential. Creators add a form of continuous qualitative exposure that many brand teams lack. That proximity creates a useful kind of taste. Creators learn how much context an audience needs. They recognize when a term sounds too corporate, when an example feels artificial, and when a company is trying to force a story the community does not believe. They often know that a campaign will fail before the performance dashboard receives enough data to confirm it. Brands frequently hire creators after the strategy has been completed. The company loses much of the value before production begins. A stronger [content brief](https://withsurface.com/blog/what-is-a-content-brief) can establish the business objective, product truth, required evidence, legal limits, and non-negotiable claims. It should leave room for the creator to challenge the framing, language, format, and audience assumption. Paying for creator judgment and then requiring the person to recite company copy is an expensive way to produce a weak advertisement. Creators were once treated primarily as an awareness channel because reach was the easiest value to describe. The modern creator relationship can influence nearly every stage of the journey. ### Discovery Creators introduce products and problems in the language of an established audience. The brand enters a conversation rather than trying to manufacture one from a cold media placement. ### Education Long-form videos, newsletters, podcasts, tutorials, demonstrations, and live streams can explain complex products with more depth than a standard advertisement. ### Consideration Creators compare alternatives, demonstrate tradeoffs, answer audience questions, and show the product inside a real workflow. Their material can become part of the buyer’s evaluation process. ### Conversion Affiliate links, creator storefronts, promotional codes, embedded commerce, webinars, product launches, and platform shopping features can produce measurable action. ### Retention and community Creators can help customers learn the product, discover additional use cases, participate in events, and remain connected to a broader community around the category. McKinsey’s description of creators as a full-funnel growth engine reflects this wider role. The useful operational implication is that creator strategy should not sit entirely inside the awareness budget. Creator work can support research, demand generation, enablement, product adoption, customer education, and loyalty. ([mckinsey.com](http://mckinsey.com/)) The expansion runs in both directions. Brands are bringing creators deeper into marketing operations. Creators are moving beyond sponsorships into businesses they control. UTA’s creator leadership recently described a shift from negotiating individual brand deals toward helping creators build broader enterprises, including intellectual property, teams, services, and physical product lines. The objective is long-term ownership rather than permanent dependence on sponsored distribution. ([theverge.com](http://theverge.com/)) This evolution makes sense. A creator with audience trust, distribution, customer knowledge, and a recognizable point of view already possesses several components of a company. Product development becomes a way to capture more of the value the creator has been generating for other brands. Traditional companies should pay attention because creator-led products often begin with an advantage marketing departments spend years trying to build: - A known audience - Direct customer feedback - An established communication style - Repeated distribution - Cultural relevance - A founder people already recognize - Immediate product-story material The product may still fail. Creator affinity cannot repair weak manufacturing, operations, pricing, customer service, or repeat purchase. The starting position is nevertheless powerful. Creators are learning to own the product. Brands need to learn how to treat creators as more than packaging around someone else’s product. The creator conversation is often illustrated through beauty, fashion, food, entertainment, and lifestyle categories. The same structural change is occurring in B2B marketing, although the creators may be called analysts, operators, educators, founders, newsletter writers, podcasters, consultants, or subject-matter experts. A B2B creator does not need millions of followers. A person followed by several thousand RevOps leaders, security engineers, finance executives, developers, or procurement professionals may influence a commercially significant market. The audience can be small in consumer terms and exceptionally valuable in business terms. LinkedIn CMO Jessica Jensen said at Cannes that users identifying as creators on LinkedIn had increased 90%, and the platform has launched a marketplace intended to connect creators with brands. The growth reflects a wider understanding that professional expertise can become media and distribution rather than remaining inside a job title. ([businessinsider.com](http://businessinsider.com/)) B2B companies can work with creators on: - Category education - Product demonstrations - Research interpretation - Customer interviews - Executive conversations - Webinars and live events - Benchmark reports - Implementation guides - Tool comparisons - Practitioner communities - Sales enablement - Product feedback The creator may influence fewer total people while reaching a larger share of the actual buying ecosystem. This is where [the storyteller role in marketing](https://withsurface.com/blog/the-storyteller-role-in-marketing-kpis-craft-and-brand-strategy) and creator strategy begin to overlap. Companies need credible individuals who can interpret a technical or operational subject for an audience without sanding away every trace of personality. Brands should give creators meaningful room without abandoning responsibility. The company remains accountable for product accuracy, regulatory requirements, customer promises, data protection, and material claims. A creator cannot independently decide that a financial product guarantees returns, a health product cures a condition, or an AI system performs a function it does not support. The operating model needs clear boundaries. ### The brand should define - The business objective - The product truth - Mandatory disclosures - Prohibited or unsupported claims - Legal and regulatory boundaries - Customer data restrictions - Commercial terms - Success measures ### The creator should shape - Audience framing - Language - Format - Story structure - Delivery - Cultural context - Publishing rhythm - Community interaction ### Both should develop - The central idea - Product use cases - Research questions - Feedback loops - Long-term content themes - Event concepts - New product or feature opportunities The strongest collaboration is neither a blank check nor a tightly controlled script. It is a clear shared field in which each party contributes the knowledge the other lacks. Creator partnerships fail when companies optimize away the source of value. A creator builds trust through repeated choices. The audience understands what the person recommends, rejects, finds funny, takes seriously, and considers worth discussing. That pattern becomes a reputation. A brand can weaken the reputation by requiring unnatural language, excessive frequency, irrelevant products, or claims the creator would never make independently. Once every post becomes commercial, the audience begins reading the relationship differently. Amy Lanzi has warned that over-commercializing creators can alienate their audiences, even as agencies and brands race to integrate creator operations more deeply. ([theverge.com](http://theverge.com/)) Recent Kantar reporting also points to growing fatigue around sponsored and AI-generated content, especially where marketers prioritize immediate clicks over long-term brand building. The evidence comes from the Indian advertising market and should not be universalized, but the warning is broadly useful: creator volume does not guarantee creator effectiveness. ([economictimes.indiatimes.com](http://economictimes.indiatimes.com/)) The creator’s credibility is not an inexhaustible media budget. A roster is a list of names. A portfolio describes the job each relationship performs. A mature creator system may include: ### Flagship creators A small number of highly aligned, long-term partners who help shape major ideas, products, events, and campaigns. ### Practitioner creators Subject-matter experts with concentrated credibility inside a particular function, industry, or buyer community. ### Customer creators Actual customers who teach, demonstrate, review, and build around the product. ### Affiliate and performance creators Partners whose primary role involves measurable acquisition or commerce. ### Executive and employee creators People inside the company who can build public expertise, explain product decisions, and participate credibly in the category. ### Community and emerging creators Smaller voices with strong audience relationships, unusual formats, regional relevance, or early cultural influence. Each tier needs different economics, support, approval, and measurement. Treating the entire portfolio as a set of interchangeable sponsored posts creates confusion and resentment. A creator who helped identify a customer need, shaped the campaign, hosted an event, produced educational material, and drove product trials should not be evaluated solely through last-click conversions. Measurement should reflect the relationship. Creator role Useful measures Audience research Repeated questions, language insights, product feedback Creative development Concepts adopted, asset performance, reuse across channels Distribution Qualified reach, completion, saves, shares, audience fit Education Watch time, content depth, return engagement, product understanding Conversion Trials, purchases, meetings, qualified leads, affiliate revenue Community Replies, repeat participation, event attendance, retention Product development Feature insights, use cases, product adoption, launch response Brand building Recall, branded search, association, consideration, sales recognition Attribution remains imperfect. A buyer may watch a creator repeatedly, search the brand later, and convert through a different route. Teams should combine trackable response with surveys, sales-call evidence, branded demand, assisted journeys, and audience research. [Lead journey tracking](https://withsurface.com/blog/lead-user-journey) becomes useful when creator traffic reaches the site. Marketing and sales teams can see whether those visitors read comparisons, inspect integrations, return later, and become qualified opportunities rather than stopping at referral volume. ### Start with the audience problem Define the community, question, tension, or behavior the company wants to understand. Do not begin with a follower threshold. ### Find demonstrated alignment Review the creator’s historical work, audience interaction, commercial behavior, expertise, and values. A polished media kit cannot replace fit. ### Involve creators before production Invite selected creators into research, positioning, product demonstrations, and concept development. Pay for strategic participation rather than disguising consulting as “relationship building.” ### Establish durable themes Build around several subjects the creator and brand can explore over time. Avoid forcing every relationship into a product announcement. ### Create a clear commercial model Use retainers, project fees, licensing, affiliate revenue, performance incentives, product participation, or equity where appropriate. The model should reflect the value and risk each party contributes. ### Preserve platform and audience fluency Let the creator adapt the idea. A good [AI-assisted content strategy](https://withsurface.com/blog/ai-content-strategy-brand-voice) should also preserve the creator’s voice rather than generate generic platform variants around it. ### Connect creator work to owned assets Give interested people a useful destination: a guide, product page, case study, event, assessment, research report, or trial experience. Creator distribution creates more value when the company provides a coherent next step. ### Build a feedback loop Share performance, customer behavior, sales outcomes, and product learning with the creator. Use those insights to improve the next release. The most capable creators operate with a continuity many marketing organizations have lost. They remain close to an audience. They develop ideas through repeated contact. They produce in formats people choose to consume. They distribute through relationships they have earned. They receive immediate feedback and adjust without waiting for an annual planning cycle. Brands should not imitate every creator behavior or turn every employee into an influencer. They should notice the integration. Research, creative, media, product storytelling, community, and commerce work better when they learn from one another quickly. Creator-first marketing matters because it brings those functions closer together around an actual person and an actual audience. The creator is becoming the marketing department because the marketing department became too fragmented to behave like one. --- # Creator Partnerships Are Becoming a Brand Trust Layer | Surface Labs URL: https://surface.thesurface.network/blog/creator-partnerships-are-becoming-a-brand-trust-layer When you decide you need a creator strategy, you make a list of people with large LinkedIn audiences. Marketing drafts a polished script. Legal removes anything remotely interesting. The creator reads the approved language into a camera, adds a product screenshot, and publishes a post that sounds exactly like the company’s own advertising. The campaign gets impressions. No one believes the creator would have said any of it without being paid. That is the weak version of creator marketing, and it is about to become more expensive. AI has made it easier for brands to produce fluent, polished, channel-ready content. It has also made feeds, inboxes, search results, and video platforms more crowded with material that looks acceptable while feeling strangely interchangeable. As synthetic production becomes normal, credible people become more important because people can carry context, judgment, reputation, and risk in ways a brand account usually cannot. Creator partnerships are becoming a brand trust layer. For consumer companies, that may involve familiar influencer relationships. For B2B teams, the more useful creator ecosystem is broader. It includes customers, practitioners, founders, consultants, engineers, researchers, industry educators, community leaders, implementation partners, and niche experts whose audiences trust them because they have done the work. The opportunity is not to rent their faces. It is to build useful work with them. Creator marketing is no longer a small experimental line item. The Interactive Advertising Bureau projected that U.S. creator advertising spend would reach $44 billion in 2026. Its research found that 48% of creator ad buyers considered creators a “must buy,” placing creator advertising just behind paid search and social media in perceived importance. The same report identified measurement, creator selection, operational standards, and AI’s role in the channel as continuing challenges. YouTube’s June 2026 Cannes Lions announcement shows how quickly the infrastructure around creator marketing is becoming more sophisticated. Google introduced Gemini-supported tools intended to help brands and agencies identify trends, evaluate creators, access audience insights, and improve creative campaigns. The announced tools include deeper trend data inside Insights Finder, brand pulse metrics, a Content & Creator Insights API, and forthcoming creative recommendations for Demand Gen campaigns. This matters because creator marketing is moving from occasional sponsorship toward an integrated media, creative, and measurement system. Brands can discover creators, build content, amplify creator videos through paid media, measure performance, and reuse those assets across campaigns. A creator post may become an advertisement, a landing-page asset, a sales follow-up, a search result, an AI-retrievable source, or a product explainer. The distribution opportunity is substantial. So is the temptation to turn creators into another form of automated inventory. The case for creator partnerships becomes stronger when placed beside the current AI creative boom. Marketers can generate more copy, images, video concepts, translations, summaries, and campaign variations than they could a few years ago. The average asset arrives faster. The feed does not necessarily become more useful. Recent Cannes conversations reflected that tension. At an Axios House discussion, marketing leaders argued that AI can give people more time and creative freedom, but that companies will distinguish themselves by using AI to amplify human creativity rather than replacing it. The speakers also emphasized balancing high-performing output with the human qualities that make a brand recognizable. That distinction is central to creator strategy. A brand account can explain what a product does. A practitioner can explain why a particular workflow is frustrating. A customer can describe what changed after implementation. An engineer can show where a seemingly simple integration gets complicated. A consultant can compare approaches while admitting that different situations require different tools. These people are valuable because they carry a history. Their audiences have seen what they praise, criticize, test, and ignore. A recommendation sits beside previous opinions. A creator who protects that consistency has something a generated brand asset does not automatically possess: reputational exposure. When a trusted practitioner says a tool worked, their audience understands that the statement may affect future trust. When a brand says the same thing, the audience understands that the brand would like to sell the tool. Neither voice is inherently honest or dishonest. They simply carry different kinds of evidence. B2B marketers often misunderstand creator value because they begin with reach. They look for the largest audience, the highest follower count, or the person whose name will make the internal campaign slide look impressive. Those measures can matter, but they are weak starting points for technical, operational, or high-consideration products. A creator with 8,000 followers who regularly speaks to revenue operations leaders may be more valuable than a general business personality with 500,000 followers. A customer who can show an actual workflow may be more persuasive than a recognizable executive reading an approved testimonial. A subject matter expert with a small newsletter may influence more qualified decisions than a large account whose audience enjoys the content but will never buy the product. The useful question is not “How many people follow this person?” Ask: - Who trusts them? - What decisions does the audience ask them to help make? - What have they actually done? - Can they explain the problem without relying on our script? - Will the product survive their honest interpretation? - Does their audience overlap with the people we can serve? - Can the resulting asset remain useful beyond one social post? This is the difference between audience rental and trust distribution. A B2B creator partnership can take many forms: - A customer-led workflow teardown - A practitioner roundtable - A founder and expert conversation - A technical implementation walkthrough - A co-authored research report - A live product critique - A benchmark built with community data - A guest newsletter analysis - A comparison created with an independent operator - A series following a real implementation over time The best format depends on what the audience needs to believe. Many creator campaigns fail because the brand wants access to a person without allowing the person to meaningfully affect the content. The team arrives with the message, script, claim, CTA, visual direction, and talking points already finished. The creator’s job is to perform the brand’s decisions in a recognizable voice. That arrangement can produce compliant content. It rarely produces the full value of a creator partnership. Business Insider’s June 2026 reporting on creator advertising highlighted advice from YouTube creator Adam Waheed and Google advertising executive Sean Downey that brands should give creators more room to experiment. They argued that open-ended briefs and mutual education often produce stronger work than rigid scripts, while still requiring compromise and brand understanding. Creative freedom does not mean removing every constraint. A creator still needs accurate product information, approved evidence, legal boundaries, disclosure requirements, audience context, and a clear understanding of what the company hopes to accomplish. The difference is that the brief provides materials and goals rather than dictating the final thought. A strong creator brief might include: - The audience problem - The product’s actual role - Approved claims and supporting evidence - Product limitations - Relevant customer examples - Topics that require additional review - The desired audience action - Questions the creator should feel free to challenge - Areas where personal experience matters more than brand language A good [content brief should preserve human judgment](https://withsurface.com/blog/what-is-a-content-brief). The same is true for creator partnerships. The brief should establish the strategic job, evidence, and boundaries. It should leave enough room for the creator to make decisions that justify involving them. If the creator cannot change the work, the company may only be buying distribution. Trustworthy creator content often works because it does not behave like a perfect advertisement. A practitioner may say that the product is useful for one team and unnecessary for another. A customer may explain that implementation required more internal coordination than expected. A technical expert may praise the architecture while criticizing the setup process. A creator may compare the product with alternatives rather than pretending no alternatives exist. Brands often find this uncomfortable. They should. Credibility comes partly from the possibility that the person could say something the company would not have written itself. That does not mean marketers should sponsor hostile or inaccurate content. It means a creator partnership should preserve enough independence for the final asset to feel like an interpretation rather than a recitation. This becomes especially important as audiences encounter more generic AI content. A polished claim with no visible friction can feel less believable than a specific explanation that includes limitations. The creator does not need to undermine the product. They need enough room to treat the audience like adults. A strong creator asset should not disappear after one platform cycle. A useful practitioner interview can become a blog, video, newsletter, sales asset, implementation guide, social series, webinar clip, comparison page, and internal training resource. The original asset can also strengthen the source ecosystem around the company. Surface’s [content marketing guide for 2026](https://withsurface.com/blog/content-marketing-guide-2026) argues that content works best as a connected system across visibility, trust, conversion, distribution, and measurement. Creator partnerships can strengthen each of those layers. They can improve **visibility** by putting the brand in front of a relevant audience. They can improve **trust** because the message travels through someone with an existing relationship to that audience. They can improve **conversion** by answering objections or showing the product in use. They can improve **distribution** because the asset has a natural life across owned, earned, creator, and paid channels. They can improve **measurement** by creating identifiable message and audience cohorts that can be compared against business outcomes. Creator work can also contribute to AI visibility. Surface’s framework for [AI visibility reporting without fake precision](https://withsurface.com/blog/ai-visibility-reporting-without-fake-precision) recommends reporting source mix rather than only owned-site citations. Videos, community discussions, social or creator content, partner pages, and third-party commentary may all shape how AI systems understand or describe a brand. A creator partnership therefore has value beyond the immediate post. It can become third-party evidence that the company exists inside a real professional conversation. Creator trust can transfer. It cannot be permanently rented. A brand does not become credible because a respected person appeared in one campaign. The product still has to work. The claims still need proof. The customer experience still needs to match the promise. The company still needs to behave consistently after the post goes live. This is where long-term relationships usually outperform isolated sponsorships. A creator who sees the product evolve can speak with more specificity. A practitioner who participates in research can contribute more than a surface endorsement. A customer who returns for a second conversation can show what happened over time. An expert who disagrees with the company occasionally may become more credible when they do recommend it. Axios’ Cannes coverage noted an emphasis on long-term creator-brand relationships, authenticity, community, and human connection amid expanding AI use. The best creator relationship is not always the person who will say yes to every campaign. It may be the person who helps the company make the campaign worth publishing. Creator measurement has not matured as quickly as creator investment. Impressions, views, likes, comments, and clicks help teams understand distribution. They do not fully explain whether the partnership changed trust, consideration, lead quality, or revenue. The IAB’s creator economy research explicitly identifies business-outcome measurement as a continuing challenge for advertisers. B2B teams should measure creator work in layers. ### Distribution metrics Track reach, impressions, video completion, saves, shares, click-through rate, newsletter referrals, and audience overlap. These show whether the asset traveled. ### Trust and attention metrics Track meaningful comments, direct replies, branded search movement, returning visitors, time spent with the asset, webinar attendance, and whether relevant practitioners reference the argument elsewhere. These show whether the asset entered a conversation. ### Conversion metrics Track product-page visits, case-study views, demo requests, content downloads, registrations, and assisted conversions. These show whether attention moved toward an action. ### Quality metrics Track lead-to-conversation rate, lead-to-meeting rate, sales acceptance, opportunity creation, account fit, and sales-call understanding. This is where [measuring lead quality instead of lead volume](https://withsurface.com/blog/how-to-actually-measure-lead-quality-not-just-lead-volume) becomes important. A creator campaign that produces fewer leads but more qualified conversations may be more valuable than a broad campaign that produces cheap forms. ### Long-term influence metrics Track repeated exposure, branded search lift, direct traffic, content reuse, AI citations, partner interest, community growth, sales usage, and customer expansion influence. These show whether the asset kept working after the original post stopped receiving impressions. No single metric proves the value of a creator partnership. The measurement model should reflect the role the creator was hired to play. Creator campaigns can suffer from the same attribution problems as paid media and AI creative. A creator introduces the brand. The buyer later searches for the company, clicks a paid search ad, visits directly, reads two case studies, and submits a form. The platform closest to the conversion receives credit. The creator campaign receives an engagement report. That does not mean the creator caused the conversion. It also does not mean the creator was irrelevant. Teams should distinguish what they observed from what they inferred. Observed: the creator asset reached the intended audience, generated relevant traffic, and appeared in journeys that later became qualified opportunities. Inferred: the creator likely contributed to awareness or confidence based on timing, branded search movement, sales-call language, and journey patterns. Tested: a holdout, matched-market test, survey, lift study, or controlled campaign supports a causal conclusion. Unresolved: the available evidence does not allow the team to confidently separate creator influence from existing demand or other channels. This discipline matters because creator trust can encourage marketers to over-credit the relationship. A respected person appearing in a journey does not automatically prove incremental lift. The next expansion in this series will examine why attribution is not the same as incrementality and how AI-era marketers can report influence without turning ambiguity into a victory slide. A useful creator program can begin small. ### Choose the business question Start with what the audience needs to understand. Avoid beginning with a list of creators. Examples: - Why do high-intent leads go cold? - What does AI visibility actually measure? - Where does content automation create risk? - How should teams evaluate lead-routing software? - What changes during a migration? - Which metric is misleading the market? ### Find people with relevant earned attention Look for practitioners, customers, researchers, operators, or educators already helping the intended audience think through the question. Prioritize fit and credibility over reach. ### Build a proof-rich brief Share product access, data, approved claims, examples, limitations, and audience context. State what the company believes while allowing the creator to form their own interpretation. ### Create one durable primary asset Begin with a substantial interview, research piece, walkthrough, webinar, or co-authored guide. Avoid forcing the partnership to depend on one short post. ### Adapt the asset by channel Turn the strongest sections into video clips, articles, email, social posts, sales follow-up, paid amplification, and internal education. Adapt the material rather than duplicating it everywhere. ### Connect the journey Use campaign and content-path data to understand what people do after encountering the creator asset. Make sure the landing page, form, routing, and follow-up continue the same conversation. ### Review the business response Compare audience quality, lead quality, sales feedback, opportunity creation, and message recall against the original objective. ### Continue relationships that create mutual value A durable partnership should help the creator serve their audience, help the brand explain something useful, and give buyers better information. When only one party benefits, the arrangement will eventually feel like advertising. AI will continue to make branded production faster. Platforms will keep adding tools for creator discovery, content generation, amplification, and measurement. The creator economy will become more structured, more professional, and more connected to paid media. That growth does not guarantee trust. Trust comes from the relationship between a person, an audience, and a history of choices. Brands can participate in that relationship. They cannot manufacture it by pasting approved copy into someone else’s voice. The strongest creator partnership gives the person something real to work with: a useful product, a meaningful question, credible evidence, access to the people behind the work, and enough freedom to tell the truth in a way their audience recognizes. A creator can help the brand reach more people. A good creator partnership helps the brand become more believable. --- # CRM Agent | Surface Labs URL: https://surface.thesurface.network/blog/crm-agent **Your reps were hired to close. They're doing data entry.** When CRM cleanup becomes part of a rep's morning, the work tends to look the same: logging calls, fixing deal stages, and filling in contact fields that never made it across. It may be necessary, but it is still time spent repairing data before the rep can use it. Here is why that work keeps coming back, and how the CRM Autofill Agent changes the setup. * * * A CRM is only as useful as the data inside it, and that data falls behind when the people responsible for updating it get busy. Skip the upkeep and the effects spread quickly. Ownership can be wrong, deal stages stop reflecting what is happening, and incomplete contacts give routing and reporting less information to work with. Once the team stops trusting the data, people start checking records by hand before acting on them. So reps and RevOps teams keep doing the upkeep because unreliable CRM data creates its own workload. HubSpot workflows and Salesforce Flow can handle a great deal of deterministic work. When a known trigger should update a known field with a known value, native automation is usually the cleanest option. The setup becomes harder when a form and CRM do not share a simple one-to-one structure. A submitted value may need to map to a controlled CRM field, an existing contact may need to be associated with the right company, or the correct owner may depend on context already stored in the CRM. Teams can build those cases into workflows, but someone still has to translate each business instruction into triggers, branches, mappings, and exceptions. The hard part is defining what should happen to the data already coming in. The CRM Autofill Agent connects to HubSpot or Salesforce and lets your team define those mapping instructions in plain English. The setup has three parts. First, connect the CRM so the agent can work with contacts, companies, associations, and owners. Next, describe how form inputs should map to CRM fields. Then run a demo on a sample lead and inspect the proposed result. During the demo, reads use the connected CRM, while creates and updates are logged instead of being sent. You can see how the instruction behaves around existing CRM data before it changes a live record. Running automation against a live CRM requires more than a plausible result on a clean test record. The awkward cases matter: an existing contact, a missing field, a submitted value that does not match a CRM option, or an association that depends on information already in the system. The demo makes those decisions visible. You can review what the agent read, what it interpreted from the form, and which create or update it proposes. If the result is wrong, you can revise the instruction and test it again without cleaning up a live write. That keeps the business rule readable for the person who owns it while giving the team a concrete result to review. Less manual mapping work is useful on its own, but routing, reporting, and follow-up also depend on the same CRM fields. When information enters the CRM consistently, those systems have better inputs. Reps spend less time wondering whether a field is missing because nothing happened or because nobody updated it, and RevOps has a clearer view of how form data became CRM data. The CRM still needs rules and ownership. The CRM Autofill Agent makes those rules easier to describe and safer to test before the proposed changes reach the system your team depends on. * * * Want to test a CRM mapping instruction against your setup? [Book a demo](https://withsurface.com/book-a-demo) --- # CRM Data Enrichment: What It Is, How It Works, and How to Turn Better Data Into More Booked Demos | Surface Labs URL: https://surface.thesurface.network/blog/crm-data-enrichment CRM data enrichment is the process of adding verified, missing information—like company size, job title, industry, and contact details—to your existing lead and customer records using external data sources. It transforms sparse CRM entries into complete profiles your team can actually act on. But enrichment only matters if it changes what happens next. This guide covers what to enrich, when to enrich it, and how to connect better data to faster routing, smarter follow-up, and more booked demos. CRM data enrichment is the process of adding verified, missing details to your existing customer records using external data sources. Instead of working with sparse records—just an email and maybe a company name—enrichment fills in firmographics (company size, industry, revenue), contact details (job title, phone, LinkedIn), and behavioral signals that help your team act faster and smarter. Think of it like upgrading a rough sketch into a complete portrait. The more you know about a lead at the moment they raise their hand, the faster your reps can respond with relevant outreach. ### A simple example of CRM data enrichment Here's what enrichment looks like in practice for an inbound demo request: 1. A visitor submits your form with their work email[form](https://withsurface.com/product/forms-and-workflows) with their work email 2. Your enrichment tool matches the email domain to a company database 3. Within seconds, employee count, industry, HQ location, and job title get appended to the record 4. Routing rules use that enriched data to assign the lead to the right rep instantly Without enrichment, your SDR would spend 5–10 minutes researching that same information manually. Or worse, the lead gets routed to the wrong rep and sits in a queue while a competitor responds first. ### CRM enrichment vs data cleansing vs lead scoring These three terms often get mixed up, but they do different things in your RevOps workflow: Process What it does When it happens **Data cleansing** Corrects errors, removes duplicates, standardizes formats Ongoing maintenance **Data enrichment** Adds missing fields from external sources At capture or in batch **Lead scoring** Prioritizes leads based on fit and intent signals After enrichment Here's the connection: enrichment feeds scoring. If you're scoring leads on company size but that field is empty for 40% of records, your model is essentially guessing. Clean data plus enriched data equals accurate scores. Teams that enrich leads in real time typically see meaningful improvements in routing accuracy and speed-to-lead—two metrics that directly impact whether a prospect books and actually shows up to a demo.[speed-to-lead](https://withsurface.com/blog/website-lead-conversion)—two metrics that directly impact whether a prospect books and actually shows up to a demo. When a high-fit lead submits a form, you have a narrow window to respond. Enrichment closes the gap between "we have their email" and "we know exactly who they are and where to send them." ### The hidden cost of incomplete CRM data Missing firmographics create a cascade of problemsMissing firmographics create a [cascade of problems](https://withsurface.com/blog/5-biggest-problems-with-inbound-marketing-leads) that slow down your entire funnel: - **Misrouting:** Leads go to the wrong rep or queue, adding hours to response time - **Generic outreach:** Reps send templated messages because they lack context about the prospect's role or company - **Wasted SDR time:** Your team researches every inbound lead manually before making first contact - **Inaccurate scoring:** Models can't prioritize effectively when key fields are blank Here's a quick way to think about the impact: if 30% of your inbound leads are missing company size, and company size determines your SMB vs. Enterprise routing, nearly a third of your leads might be misrouted on first assignment. ### Common symptoms you need enrichment You're likely feeling the pain of incomplete data if any of these sound familiar: - "Unknown" or blank values in industry, employee count, or title fields - Leads routed to the wrong territory or segment - SDRs spending 10+ minutes researching[SDRs spending 10+ minutes researching](https://withsurface.com/blog/is-sales-tired-of-getting-shitty-leads) before every first call - Calendar spam from free email addresses or bot submissions - Duplicate accounts cluttering your CRM - Low meeting show rates despite high form submissions Not every field matters equally. The goal is to enrich what your routing rules, scoring models, and reps actually use—not to collect data for its own sake. ### Contact-level enrichment Contact fields help your team personalize outreach and validate lead quality: - **Job title and seniority:** Determines decision-maker status - **Department:** Helps tailor messaging (marketing vs. engineering vs. finance) - **Direct phone and LinkedIn URL:** Enables multi-channel follow-up - **Location and timezone:** Supports scheduling and territory assignment - **Email validity signals:** Flags potential bounces before you send ### Company-level enrichment Company fields power qualification and routing decisions: - **Company name (normalized):** Prevents duplicates from variations like "IBM" vs. "IBM Corp" - **Domain:** Anchors the company match - **Employee count and revenue range:** Determines segment (SMB, mid-market, enterprise) - **Industry:** Enables vertical-specific messaging - **HQ location:** Drives territory routing - **Tech stack signals:** Indicates product fit (e.g., "uses HubSpot" or "runs on Salesforce") ### Routing-critical fields Before a lead can be assigned, your system typically requires: - Territory (based on geography or named accounts) - Segment tier (based on company size or revenue) - ICP fit flag (based on industry, tech stack, or other criteria) - Existing customer or account match (to route to the right owner) If any of these are missing at the moment of capture, routing breaks—or defaults to a generic queue that adds delay. ### Risk and quality signals Enrichment can also flag low-quality or fraudulent submissions before they waste your team's time: - **Free email detection:** Identifies gmail.com, yahoo.com, etc. - **Disposable domain flags:** Catches temporary email services used for spam - **Enrichment confidence scores:** Indicates how reliable the match is The enrichment process follows a predictable sequence, though the timing—real-time vs. batch—varies based on your use case. ### Step 1: Capture clean inputs Enrichment quality depends on capture qualityEnrichment quality depends on [capture quality](https://withsurface.com/blog/bad-forms-are-killing-your-conversions). If your form collects a misspelled company name or a personal email, matching becomes harder and less accurate. A few practices that help at the capture layer: - Request work email (not just "email") - Use domain-based company lookup when possible - Validate email format before submission - Consider partial response capture—saving what you can even if the visitor abandons mid-form ### Step 2: Match and enrich Once you have an email or domain, your enrichment tool queries external databases to find a match. This can happen in two ways: - **Real-time:** At the moment of form submission, before routing - **Batch:** On a schedule (daily, weekly) for existing CRM records Real-time enrichment is critical for inbound conversion because it enables instant routing. Batch enrichment works well for database hygiene and re-engagement campaigns where speed matters less. ### Step 3: Normalize, dedupe, and write back Before writing enriched data to your CRM, you'll want rules for: - **Normalization:** Standardizing company names, titles, and locations - **Deduplication:** Matching to existing accounts or contacts to avoid creating duplicates - **Field precedence:** Deciding whether enriched data overwrites existing values or only fills blanks - **Provenance logging:** Tracking where each data point came from Without these guardrails, you risk creating duplicates or overwriting information that a rep manually verified. ### Step 4: Activate with scoring, routing, and follow-up This is where enrichment turns into pipeline. Once data is appended, your workflows can: - Score the lead based on ICP fit - Route to the correct rep or queue instantly - Trigger a personalized confirmation email - Create a follow-up task or Slack alert - Block or deflect low-fit or spam submissions Enrichment that stops at "better records" misses the point. The value comes from what you do with the data in the next 60 seconds. > **Tip:** If your enrichment happens after routing, you're already too late for many inbound leads. The highest-leverage pattern is enriching at the form layer, before assignment. The choice depends on your use case and SLA requirements. Approach Best for Trade-offs **Real-time** Inbound forms, demo requests, booking flows Higher cost per record; requires low-latency integration **Batch** Database cleanup, re-engagement campaigns, historical records Lower cost; doesn't support instant routing For inbound conversion, real-time wins. If your speed-to-lead SLA is under 5 minutes, you can't wait for a nightly batch job to tell you who just submitted a demo request. Rather than comparing dozens of vendors, focus on five criteria that matter for conversion: 1. **Latency:** Can it enrich before your routing rules fire? 2. **Coverage:** Does it have accurate data for your target regions and segments? 3. **Match rate:** What percentage of records actually get enriched? 4. **Write-back control:** Can you set field precedence and avoid overwriting verified data? 5. **Activation depth:** Does it just append data, or does it connect to routing, workflows, and follow-ups? The last point is often overlooked. Many tools excel at data append but leave activation to you—meaning more Zaps, more integrations, and more places for leads to leak. "Data completeness" is a vanity metric. What you actually want to track: - **Lead-to-demo conversion rate:** Are more form fills turning into booked meetings? - **Speed-to-lead:** How fast does the first touch happen after submission? - **Routing accuracy:** What percentage of leads are assigned correctly on the first try? - **SDR research time:** How many minutes per lead does your team spend on manual lookup? - **Bounce rate:** Are fewer emails failing to deliver? - **Spam rate:** Are fewer junk submissions reaching your calendar? A simple ROI framework: (Incremental demos × close rate × ACV) minus tooling and ops costs. If enrichment helps you book 10 more demos per month at a 20% close rate and $30K ACV, that's $60K in pipeline—likely far exceeding your enrichment spend. **Enrich what your workflows use.** If your routing rules don't reference industry, don't pay to enrich it. **Treat enrichment as probabilistic.** Match confidence varies. Build fallback logic for low-confidence records rather than trusting every append blindly. **Don't overwrite human-verified fields.** If a rep manually updated a contact's title, your enrichment tool shouldn't revert it. **Set a refresh cadence.** Job titles change, companies get acquired, and people move. Re-enrich active records quarterly or when engagement signals suggest the data may be stale. Enrichment is one layer in a larger conversion stack: capture → enrich → qualify → route → follow-up. If any layer breaks, leads leak. Most teams invest heavily in capture (forms, landing pages) and follow-up (sequences, SDR outreach) but underinvest in the middle. The result: leads arrive with incomplete data, get routed incorrectly, and receive generic follow-up that doesn't convert. The fix is treating these layers as one connected system. When a visitor submits a form, enrichment fires instantly, routing happens based on enriched data, and follow-up gets personalized to what you now know about them—all within seconds. That's the difference between "enrichment as a data project" and "enrichment that converts." If your inbound leads are leaking between capture and follow-up, enrichment alone won't fix it. You want forms, enrichment, routing, and follow-up working as one system. [Book a demo](https://withsurface.com/book-a-demo) to see how Surface Labs connects real-time enrichment to intelligent routing and automated follow-ups—so more of your inbound traffic turns into pipeline. --- # Host Surface Forms on Your Own Domain URL: https://surface.thesurface.network/blog/custom-domains _Surface forms can now live on your domain as standalone pages. Fully branded, no code changes, no developer required._ You need a landing page for a campaign, an event registration form, or a multi step survey. The options aren't great. Either you ask engineering to build and deploy something on your main site, or you use a third party tool that lives on someone else's domain and looks nothing like your brand. The first option is slow. The second looks unprofessional. Both create unnecessary friction for marketing teams that just want to get a page live quickly. ## Custom Domains in Surface Surface forms can now be hosted on your own domain as fully standalone pages. No embedding, no iframes, no subdomains that scream "third party tool." The form gets its own URL on your domain, fully branded, and ready to share. Marketing teams can spin up campaign pages, event registration, lead capture forms, or multi step surveys without touching the primary website or waiting on a developer. Getting a custom domain connected takes about ten minutes. Here's the full process: **1\. Navigate to Settings** in the main sidebar **2\. Click "Domains"** and add your new domain **3\. Wait for verification** (up to 10 minutes) **4\. Go to your Form Settings** and connect the verified domain **5\. Your form is live** as a standalone page on your domain Set it once. Host forever. Any updates you make to the form in Surface automatically reflect on the live page. What you're launching Why custom domains help Campaign landing page Dedicated URL you can share in ads, emails, and social without sending traffic to your main site Event registration Standalone signup page that matches your brand, no generic form tool branding Multi step survey Clean, distraction free experience on your own domain Partner or co branded forms Host on a specific subdomain for different brands or regions **Do I need a developer to set up a custom domain?** No. The entire setup is done in Surface's settings panel. You add the domain, verify it, and connect it to your form. No code changes required. **Can I use a subdomain?** Yes. You can connect a subdomain like forms.yourcompany.com or campaign.yourcompany.com. **Does the form update automatically after I connect the domain?** Yes. Any changes you make to the form in Surface are reflected on the live page immediately. **Will the page look like my brand?** Yes. The form carries all the branding, styling, and design you've configured in Surface. It looks like your page, not a third party tool. **Can I host multiple forms on different domains?** Yes. You can connect multiple domains and assign different forms to each one. --- # Do You Actually Need an Enterprise Marketing Platform? | Surface Labs URL: https://surface.thesurface.network/blog/do-you-actually-need-an-enterprise-marketing-platform You're growing. Leads are coming in. The team is expanding. Someone — maybe a board member, maybe a new VP of Marketing, maybe a consultant — suggests it's time to upgrade to an enterprise marketing platform. HubSpot Marketing Enterprise. Marketo. Salesforce Marketing Cloud. Pardot. The pitch is compelling: one platform that does everything. Email nurture, lead scoring, campaign orchestration, attribution, forms, landing pages, analytics. The enterprise suite will unify your marketing stack and give you the horsepower you need to scale. Here's the question nobody asks before signing the contract: do you actually need all of that? Or do you need to fix the specific thing that's broken? Enterprise marketing platforms are built for one primary job: multi-touch, multi-channel campaign orchestration at scale. If you need to build a 15-step nurture sequence that branches based on behavior, runs across email, SMS, and retargeting ads, and adjusts in real time based on engagement — these platforms do that well. They're also good at audience management across large databases (500K+ contacts), complex reporting and attribution for organizations with multiple business units, and compliance and governance features required by large enterprises. If those are your primary needs, an enterprise platform might be the right call. That's a real use case, and these tools were built for it. Here's what the enterprise pitch obscures: the thing that's probably broken in your funnel — the lead capture, qualification, and routing layer — isn't what these platforms are built to fix. What you need fixed What the enterprise platform offers The gap Leads sit for hours before anyone contacts them Workflow automations that can trigger notifications — but speed depends on how workflows are configured, which requires an admin Platform has the capability but it's not optimized for speed-to-lead. Most implementations still result in 30+ minute response times. Leads go to the wrong rep Assignment rules that can route by criteria — but require Salesforce Flow or custom configuration Routing logic is possible but buried in CRM config. Changing rules requires admin access and testing. Forms capture name and email but nothing useful for qualification Form builder with conditional logic — but designed for campaign use cases, not real-time qualification and routing Forms exist but aren't connected to routing or scheduling. Qualification still happens manually. No visibility from form submit to meeting booked Attribution reporting across campaigns — but doesn't track the post-form journey at a lead level Great at campaign-level attribution. Poor at lead-level journey tracking through the capture-to-meeting flow. The pattern: enterprise platforms can theoretically do these things. But they weren't optimized for them, and getting them to work requires significant configuration, a dedicated admin, and ongoing maintenance. The subscription cost is just the beginning. **Implementation.** Enterprise platforms require 4–12 weeks of setup with an implementation partner or dedicated internal resource. Cost: $5K–$50K+ depending on complexity. **Admin overhead.** These platforms require a certified admin or a knowledgeable ops person to manage on an ongoing basis. Cost: $60K–$120K/year for a full-time admin, or $2K–$5K/month for a fractional consultant. **Feature utilization.** Most mid-market companies use 20–30% of the features in an enterprise marketing platform. You're paying for journey orchestration, advanced segmentation, AI-powered recommendations, and custom reporting — but your team is using email sends, basic forms, and a few workflows. **Switching cost.** Once you're on an enterprise platform, migrating off is painful — data migration, workflow recreation, team retraining. The switching cost creates lock-in that makes it hard to leave even when the platform isn't delivering value. For a company spending $3,600–$5,000/month on the platform plus $5K+/month on admin resources, the annual cost of the enterprise marketing stack is $100K–$180K. The question is whether it's solving the right problem. Most companies evaluating an enterprise platform aren't doing it because they need 15-step nurture sequences. They're doing it because leads aren't converting, follow-up is slow, routing is broken, and they assume the enterprise platform will fix all of it. But those are lead ops problems, not marketing automation problems. And they can be fixed with a purpose-built lead ops layer at a fraction of the cost and implementation time. **Speed-to-lead:** A lead ops tool responds in under 60 seconds by default. An enterprise platform can be configured to do it, but it takes weeks of workflow setup and an admin to maintain. **Routing:** A lead ops tool routes by territory, deal size, product interest, and availability natively. An enterprise platform requires custom flows or third-party tools. **Qualification at capture:** A lead ops tool qualifies on the form in real time. An enterprise platform captures form data and then runs scoring models that take hours to update. **Time to value:** A lead ops tool is live in days. An enterprise platform takes months. If your actual problem is the capture-to-meeting flow, you don't need a $150K/year enterprise suite to fix it. You need a $500–$2,000/month lead ops layer that solves the specific problem, connects to your existing CRM, and is live next week. \[IMAGE: A simple cost comparison. Left: "Enterprise platform" — $150K+/year, 4-12 weeks implementation, dedicated admin required, 20-30% feature utilization. Right: "Lead ops layer" — $6K-24K/year, days to implement, self-serve, built for the specific problem. White background, blue (`#4F6DF5`) accent, flat design.\] Surface is the lead ops layer — capture, qualification, routing, and instant response in one system that works with your existing CRM. It fixes the specific problem that drives most companies toward an enterprise platform, at a fraction of the cost, without the implementation timeline or admin overhead. If someone on your team is pushing for an enterprise marketing platform, ask this first: "Is our problem that we need better campaign orchestration, or that leads aren't getting to the right rep fast enough?" If it's the latter, Surface solves it without the enterprise price tag. --- # Auto-Route Leads to Sales Calendars | Surface Labs URL: https://surface.thesurface.network/blog/dynamic-scheduling A 500-person enterprise fills out a demo request and ends up on an SMB rep's calendar. A prospect in Germany gets offered a 6am slot with the US team. A high-intent lead submits a form and waits two days for someone to send a booking link. Most teams have routing logic somewhere in their CRM or ops workflow. But it kicks in _after_ submission. By the time the lead gets assigned and a link goes out, the moment has passed. Surface moves that routing decision into the form itself. Surface lets you build routing rules directly into your form logic. Company size, region, industry, use case, budget any combination of fields can determine which calendar appears at the scheduling step. Prospect responds with... Calendar shown 500+ employees Enterprise AE 50 or fewer employees SMB sales rep Located in EMEA European team Enterprise + EMEA + Security use case Senior SE in London You can combine multiple conditions in a single route. When the prospect reaches the scheduling step, the right calendar shows up directly in the form, no redirects, no extra pages, no one manually assigning leads on the backend. Each route is defined by conditions you set using any form field. For example, if a prospect selects "500+ employees" and "EMEA," Surface knows to show the Senior Enterprise AE calendar for that region. **Traditional routing:** Form → Submission → CRM workflow → Assignment → Rep emails booking link → Prospect books (maybe, 24-48 hrs later) **Conditional calendar routing:** Form → Right calendar appears → Booked (under 60 seconds) The result is that every meeting on a rep's calendar is already correctly assigned, no misroutes, no manual cleanup, and no prospect left waiting for a follow-up email. Surface also connects with Calendly, Chili Piper, Cal.com, and other scheduling platforms. No migration required. Surface shows a default fallback calendar so no lead goes unbooked. You configure this once and it catches any submission that falls outside your specific routes. **Can I show different calendars based on form responses?** Yes. Surface evaluates routing rules in real time. The calendar matching the prospect's responses appears automatically at the scheduling step. **Does this work with Calendly or Chili Piper?** Yes. Connect your calendars in the integration settings and reference them in the form logic. **Does this add extra steps for the prospect?** No. Routing happens behind the scenes. The prospect fills out the form, the right calendar appears, they book. **Can I combine multiple routing conditions?** Yes. Company size plus region plus product interest plus budget — Surface evaluates all conditions together. **How is this different from CRM-based lead routing?** CRM routing happens after submission, which introduces delay. Conditional calendar routing happens during the form, so the prospect books immediately with the right person. --- # Emergency vs. Scheduled: How Home Services Companies Should Route Every Lead | Surface Labs URL: https://surface.thesurface.network/blog/emergency-vs-scheduled-how-home-services-companies-should-route-every-lead A burst pipe at midnight and a kitchen remodel quote request at 2 PM on a Tuesday are both "leads." But treating them the same — same form, same response time, same routing — is how home services companies lose emergency jobs to competitors and waste technician time on low-priority inquiries. The highest-performing home services companies route every lead through one filter first: is this an emergency or is this scheduled work? Everything downstream — who gets notified, how fast, through what channel, and with what response — depends on that answer. Most home services websites have one form: "Request a Service." Name, phone, address, "describe your issue." Every submission goes to the same inbox or dispatcher queue. The dispatcher reads each one, decides if it's urgent, figures out who's available, and calls the customer back. That process works at 5 leads per day. At 20+ leads per day, the dispatcher becomes the bottleneck. Emergency calls sit behind scheduled requests. Response time degrades. The customer with the flooding basement calls the next company on Google because yours didn't pick up fast enough. Lead type Customer expectation What usually happens What should happen **Emergency** (burst pipe, no power, gas smell, AC out in 100°F) Response in minutes. Someone en route within the hour. Sits in queue behind scheduled requests. Callback in 30 min – 2 hours. Instant notification to on-call tech. Text confirmation to customer within 3 minutes. Tech dispatched. **Same-day** (toilet running, AC underperforming, flickering lights) Response within a few hours. Service today or tomorrow. Same queue as emergencies. Sometimes prioritized, sometimes not. Auto-response with same-day availability. Routed to nearest available tech for the service type. **Scheduled project** (remodel, installation, inspection, maintenance) Response within 24–48 hours. Appointment next week is fine. Same queue. Often gets fastest response because it's easiest to handle. Automated response with scheduling link. Routed to project team, not emergency techs. The mistake most companies make: treating everything as medium priority. Emergencies get slower response than they need. Scheduled projects get faster response than they need (wasting high-value dispatch time). Nobody gets the right treatment. The form does the sorting. One question at the top changes the entire flow: **"How urgent is your request?"** - Emergency — I need help right now (active leak, no power, safety concern) - Soon — I'd like service today or tomorrow - Planned — I'm scheduling a project or maintenance Each selection triggers a different path: **Emergency path:** Minimized form (just contact info + brief description + address). Instant routing to on-call technician for that service area and service type. Customer gets a text within 2 minutes: "We've received your emergency request. A technician is being dispatched to your area. Expected response time: \[X minutes\]." Dispatcher gets a simultaneous notification with full details. **Same-day path:** Standard form (contact info + service type + issue description + photos optional). Routed to nearest available tech matching the service type. Customer gets an auto-response: "We have availability today. Here are three time slots: \[options\]." Or if no same-day availability: "Our first available slot is tomorrow at \[time\]. Book here." **Scheduled path:** Full project form (contact info + service type + scope description + photos + budget range + preferred timeline). Routed to the project estimator or team scheduler. Customer gets an auto-response within the hour with scheduling options for the next 1–2 weeks. No technician time wasted until the estimate appointment. After urgency, route by service type and geography: **Service type matching:** A plumbing emergency goes to a plumber, not an electrician. Obvious — but round-robin routing doesn't know the difference. The form captures service type, and routing sends it to the right crew. **Geographic matching:** Route to the technician closest to the job address. This reduces drive time, gets the tech on-site faster, and improves daily job capacity. **Availability matching:** Check real-time availability (calendar integration with field service management tools). Don't route an emergency to a tech who's in the middle of a 4-hour installation. **Capacity balancing:** For same-day and scheduled work, distribute evenly across available techs to prevent overload. Emergency routing bypasses capacity limits — emergencies go to whoever is available, regardless of daily load. ## Post-service automation The lead flow doesn't end at dispatch. After job completion: **Immediate:** Payment processing (if applicable) + satisfaction check: "How did the service go? Rate 1–5." **24 hours:** Review request: "Would you leave us a review? Here's a direct link to Google." Companies that automate review requests see 3–5x more reviews than those relying on technicians to ask verbally. **Seasonal:** Follow-up maintenance recommendations based on the completed service. Fixed an AC? Schedule a tune-up reminder for next spring. Repaired a water heater? Suggest a plumbing inspection in 6 months. Surface handles the full home services lead flow: urgency-based form branching, service-type routing, geographic tech matching, instant customer response, and post-service automation. Connected to your field service management system (ServiceTitan, Housecall Pro, Jobber) so dispatched jobs flow directly into your existing workflow. If your dispatcher is the bottleneck between lead and service, Surface removes the bottleneck. --- # Every AI Tool That Touches Your Leads Right Now | Surface Labs URL: https://surface.thesurface.network/blog/every-ai-tool-that-touches-your-leads-right-now AI has quietly infiltrated every layer of the B2B lead flow. Not in the dramatic, "AI will replace your sales team" way the conference keynotes promise — but in the practical, "there are now 8 AI-powered tools between your ad click and your rep's phone call" way that nobody's mapped out. If you're a marketing or revenue leader, you should know which AI tools are touching your leads, where they add value, and where they add complexity without actually improving conversion. Here's every layer where AI tools now operate in a typical B2B lead flow: Layer What AI does here Common tools Value level **Ad targeting** Algorithmic audience optimization, lookalike modeling, bid management Google Performance Max, Meta Advantage+, LinkedIn Predictive Audiences High — but you have limited control. The platform's AI optimizes for its own metrics. **Content creation** Generates ad copy, landing page text, blog content, email sequences Jasper, Copy.ai, ChatGPT, Claude Medium — saves time on drafts. Quality varies. Requires human editing for anything customer-facing. **Visitor identification** Identifies anonymous website visitors by matching IP data to company databases Clearbit Reveal, 6sense, Demandbase Medium-high for ABM-focused teams. Less useful for high-volume inbound. **Chatbots / conversational AI** Engages visitors in real-time conversation, answers questions, captures intent signals Drift, Intercom Fin, custom Claude/GPT bots Medium — good for engagement, inconsistent for structured qualification and routing. **Form optimization** A/B tests form variants, predicts optimal field count, personalizes form experience Limited standalone tools. Most testing happens in broader CRO platforms. Low — this layer is underserved. Most "AI form" claims are basic conditional logic. **Enrichment** Appends company and contact data to leads using AI-matched databases Clearbit, ZoomInfo, Apollo, Lusha High — real value if used at the right moment (at capture, not hours later). **Lead scoring** Predicts lead quality or likelihood to convert based on behavioral and firmographic signals HubSpot Predictive Scoring, Marketo, MadKudu, Infer Medium — only as good as the data it's trained on. Most models are poorly calibrated. **Routing** Matches leads to reps using AI-evaluated criteria Limited. Most routing is still rule-based. Some tools (Chili Piper, LeanData) add basic intelligence. Low-medium — AI routing is nascent. Rule-based routing with the right variables outperforms most "AI routing" today. **Sales engagement** Prioritizes which leads to contact, generates personalized outreach, optimizes send times Outreach, Salesloft, Apollo, Lavender Medium-high for outbound. Less relevant for inbound where speed matters more than personalization. **Meeting scheduling** Suggests optimal times, handles rescheduling, sends reminders Calendly, Chili Piper, Reclaim AI Low AI involvement. Scheduling is largely a solved problem — the issue is getting leads to the scheduling step. That's 10 layers of AI between your ad budget and your rep's calendar. In theory, each one makes the flow smarter. In practice, they create a chain where no single tool owns the outcome and nobody has visibility across the full journey. The honest assessment: AI adds genuine value at the top of the flow (targeting, enrichment) and at the bottom (sales engagement for outbound). In the middle — qualification, routing, and the critical form-to-meeting transition — most "AI" is either basic automation with an AI label or genuine capability that's poorly integrated with the rest of the stack. The lead scoring layer is the best example. HubSpot's predictive scoring sounds powerful, but it's trained on historical data that may not reflect your current ICP, and it scores leads after they've entered the CRM — not at the moment of capture when the score would actually affect routing and response speed. The AI is real. The timing makes it less useful than it should be. **Audit which AI tools are touching your leads.** Most teams don't know. Walk the flow from ad platform to booked meeting and list every tool that uses AI in any capacity. You'll probably find 6–10. **Ask whether each one is improving the metric that matters.** The metric is lead-to-meeting rate. If an AI tool doesn't measurably improve how many leads become booked meetings, it's adding complexity without value. **Focus AI investment on the bottleneck.** For most teams, the bottleneck isn't targeting or content or scoring. It's the 60 seconds after form submission — qualification, routing, and response. If your AI spend is concentrated on ad optimization and content generation but you have zero AI in the capture-to-meeting layer, you're optimizing the wrong part of the funnel. Surface applies intelligence where it matters most — at the moment of capture. Smart forms with conditional qualification, real-time routing, and instant personalized response. Not AI for AI's sake, but AI applied to the specific bottleneck that determines whether your leads become meetings. If you've got 10 AI tools in your stack and your lead-to-meeting rate is still 12%, the problem isn't that you need an 11th. It's that the AI isn't applied to the right layer. --- # Every GTM Hire Should Be Technical Now | Surface Labs URL: https://surface.thesurface.network/blog/every-gtm-hire-should-be-technical-now We don't hire "GTM people." We hire GTM engineers. Most companies haven't caught up to this yet. Here's what I mean. Three years ago, a great marketing ops hire was someone who could build HubSpot workflows and keep the CRM clean. That person is now table stakes. The bar has moved. The GTM stack in 2025 is deeply technical. We're talking API integrations, data pipelines, Clay workflows, custom enrichment logic, multi-tool automation chains, and AI models plugged into the lead flow. A GTM person who can't read an API doc or build a basic automation isn't operating at the level the job requires. This isn't an engineering gatekeeping take. I'm not saying every marketer needs to write production code. I'm saying the line between "marketing" and "engineering" has blurred to the point where the distinction is holding companies back. At Surface Labs, every GTM hire needs to be comfortable with technical tools. Not because we want to be difficult about hiring — because the best campaigns in 2025 are built, not just planned. The person who can design a lead scoring model AND implement it in the platform is 3x more valuable than someone who writes a spec and hands it to an engineer. Our marketing team builds automations directly. They configure routing logic. They set up webhook-triggered responses. They connect enrichment APIs to qualification criteria. They don't file tickets with engineering to change a form field — they change it themselves, test it, and push it live. Our SDR team doesn't just "use" the CRM — they understand the data model, they know how lead records flow through the system, and they can diagnose when something breaks without waiting for ops to investigate. This isn't because we hired engineers and taught them marketing. It's because we hired marketers and SDRs who are technically fluent — people who see a Clay workflow as a tool, not a mystery. The companies that separate "GTM people" from "technical people" will always have a translation layer — a bottleneck where marketing ideas wait in an engineering queue. The companies that merge these capabilities into every GTM role will move faster, iterate faster, and compound improvements faster. We're building Surface Labs for this world — a world where marketing ops IS engineering. Where the person designing the campaign is the same person building the infrastructure to run it. Where the line between "strategy" and "implementation" disappears. If your GTM team can't touch the technical stack, they're not really running your go-to-market. They're writing briefs about it and hoping someone else builds what they described. The best GTM teams I've seen — ours included — are teams where everyone can ship. Not just plan. Not just strategize. Ship. Are you hiring GTM engineers or GTM people? There's a difference. --- # Finding Your Dream Customer (and Proving It With Data) | Surface Labs URL: https://surface.thesurface.network/blog/finding-your-dream-customer-and-proving-it-with-data **The middle school version:** Imagine you're selling lemonade, but you don't know who loves lemonade the most — is it kids at soccer games? Office workers at lunch? People at the beach? Surface helps us test different groups of people to figure out who our BEST customers are. We call these groups "ICPs" (Ideal Customer Profiles). Instead of guessing, we let the data tell us who loves our lemonade the most. Every startup has an ICP document. It's usually a one-page Google Doc written during a strategy session, based on a mix of founder intuition, early customer conversations, and competitive analysis. It says something like "B2B SaaS companies, 50–500 employees, Series A–C, US-based." That document doesn't get updated. It sits in a shared drive while the sales team sells to whoever shows up. Six months later, someone asks "are we still targeting the right people?" and nobody has a data-driven answer. We were that startup. Our initial ICP was based on pattern matching from our first 20 customers. It felt right. But feeling right and being right are different things — and we didn't know the difference until we started testing. Surface lets us define multiple ICP hypotheses and measure each one against actual conversion data — not just lead volume, but the metrics that matter: conversion rate, deal size, time to close, and retention. We set up ICP definitions as combinations of attributes: ICP hypothesis Company size Industry Tech stack Role **ICP A: Mid-market SaaS** 100–500 employees B2B SaaS HubSpot or Salesforce Marketing ops, RevOps **ICP B: Growth-stage startups** 20–100 employees Any tech Any CRM Founders, GTM leads **ICP C: Agencies** 5–50 employees Marketing/digital agencies HubSpot Agency owners, account managers **ICP D: Mid-market services** 100–500 employees Professional services, consulting Salesforce Marketing directors Every lead that enters Surface gets automatically tagged with which ICP hypothesis they match (they can match multiple or none). This tagging happens at the moment of capture — based on form data and enrichment — and follows the lead all the way through to closed/won or closed/lost. After 90 days of tracking, we pulled the data: ICP hypothesis Lead volume (monthly) Lead-to-meeting rate Average deal size Median time to close 6-month retention **ICP A: Mid-market SaaS** 85 28% $18,000 34 days 92% **ICP B: Growth startups** 140 22% $6,000 18 days 71% **ICP C: Agencies** 45 35% $12,000 21 days 88% **ICP D: Mid-market services** 30 15% $22,000 52 days 85% **Agencies were our best ICP — and we almost ignored them.** ICP C had the highest lead-to-meeting rate, fast close times, strong retention, and decent deal sizes. We'd been treating agency leads as secondary. The data showed they were our most efficient customer segment. Why? Agencies use Surface across multiple client accounts. They understand the product faster because they live in marketing ops tools daily. They have shorter procurement cycles. And they expand — when one client campaign works, they roll Surface out to three more clients. **Growth startups had volume but not value.** ICP B generated the most leads. The close times were fast. But deal sizes were small and retention was weak — these companies churned at nearly 3x the rate of mid-market SaaS. They were easy to close but expensive to serve and hard to keep. **Mid-market services was our weakest segment.** Low volume, low conversion, long sales cycles. The product fit was there, but the buying process in professional services is slow and consensus-driven. We didn't kill this segment, but we stopped investing in it as a primary target. Based on the data, we restructured our GTM around two primary ICPs: mid-market SaaS (ICP A) and agencies (ICP C). Growth startups (ICP B) became a self-serve segment — we let them convert but don't invest sales time in them. The practical changes: ad targeting shifted to company size 50–500 in SaaS and agencies. Form qualification branching gives these segments the premium path (more qualifying questions, direct AE routing, instant scheduling). Content strategy pivoted to address agency use cases — a segment we'd barely mentioned in previous content. **Step 1: Define 3–4 hypotheses.** Each hypothesis should be a specific combination of company attributes — not just "B2B companies." Be specific enough that you could look at a lead and say "this matches ICP A but not ICP B." **Step 2: Tag every lead at capture.** Use form data and enrichment to automatically classify which ICP each lead matches. This should happen at the moment of capture, not retroactively. **Step 3: Measure the full funnel, not just volume.** Track each ICP through to revenue — conversion rate, deal size, close time, and retention. A high-volume ICP with low retention costs more than it generates. **Step 4: Reallocate based on data.** Shift ad spend, sales time, and content toward the ICPs that perform best on the metrics that matter. Review quarterly — ICPs can shift as your product and market evolve. **Stop guessing who your best customers are. Define and test ICPs with Surface.** --- # Build Smarter Lead Forms Without Engineering | Surface Labs URL: https://surface.thesurface.network/blog/formcreation **You can build intelligent lead forms with partial lead capture, conditional qualification logic, and automated routing without writing a single line of code.** Most B2B teams don't know this is possible because the tools they've used have never offered it. They've been working around the limitations of basic form builders for so long that the limitations feel normal. They're not normal. They're just the status quo. Most B2B teams don't have a lead capture platform. They have a patchwork. A form tool for collecting submissions, a CRM for routing, a separate automation tool for follow-ups, and maybe a Zapier workflow holding it all together. The form itself does almost nothing. It collects a name, email, and company, then dumps everything into the CRM for someone to figure out. There's no qualification happening inside the form. No branching based on who the prospect is. No routing to the right rep. And if someone drops off halfway through, that lead is gone. Some teams try to fix this by building custom forms with engineering support. That works until you need to change a field, add a routing rule, or launch a new campaign, and you're back in the dev queue. Surface Labs brings templates, conditional logic, and workflow automation into one system. Each piece handles a different part of the lead capture lifecycle, and they all work together without needing external tools or engineering support. **Production-ready form templates.** Surface provides a template library built for specific B2B use cases including demo requests, event registration, lead capture, and contact forms. Each template is designed to go live immediately. The visual editor lets you adjust typography, swap color palettes, modify layouts, and add your logo without writing CSS or waiting on a designer. **Conditional logic for real-time lead qualification.** The Logic tab is where the form gets smart. You define if/then branching rules that change the prospect's path based on their real-time inputs. A prospect selects "500+ employees" and the form routes them toward enterprise sales, adjusting follow-up questions accordingly. They choose "Marketing Ops" as their role and Surface asks about their current tool stack. Each answer shapes the next question, the qualification outcome, and who the lead gets routed to. By the time they finish, they've already been qualified, segmented, and pointed to the right next step. **Event-driven workflows for completions and drop-offs.** Traditional forms are binary: submit or nothing. If a prospect fills out three steps and leaves, you lose them entirely. Surface captures engagement at every step. The workflow builder lets you trigger automated actions based on form activity, not just completion. You define separate paths for completions and drop-offs, so a prospect who made it to step three and left still gets captured and routed as a warm lead. Capability Typical form builder Surface Labs Branded templates Basic or none Production-ready, fully customizable Conditional branching Limited or requires code Visual logic tree, unlimited conditions Lead qualification Not built in Happens during the form Calendar routing Not built in Conditional, based on responses Drop-off capture Lost entirely Triggers separate workflows CRM and Slack integration Via Zapier or manual Native, event-driven A form builder collects data. A lead capture platform qualifies, routes, and acts on that data in real time. If your current tool stops at the submission, you're doing the hard part manually every single time. [Surface Labs](https://www.withsurface.com/) was built to handle the rest. **How do I improve landing page conversion without a developer?** Use a platform that qualifies and routes leads inside the form itself, without relying on a developer to build or maintain it. Surface Labs lets ops and marketing teams configure conditional logic, routing rules, and post-submit workflows through a visual editor. No code required. Teams typically go live in a day, not a sprint. **What tool builds smart lead forms without engineering?** Surface Labs. It combines production-ready form templates, conditional qualification logic, and event-driven workflows in one platform. You can build forms that qualify leads in real time, route them to the right rep or calendar, and capture partial submissions from visitors who drop off, all without writing any code. **What is a lead capture platform?** A lead capture platform handles the full lifecycle of capturing inbound leads, from form creation and real-time qualification to routing and workflow automation. Unlike standalone form builders, a lead capture platform qualifies and acts on leads before they leave the page. Surface Labs is built around this model. **What happens if a prospect does not finish the form?** Surface Labs captures partial submissions and triggers separate workflows for drop-offs. A prospect who left at step three still gets routed and followed up on, rather than being lost entirely the way they would be with a traditional form builder. **How is Surface Labs different from Typeform or HubSpot Forms?** Standard form builders collect submissions. Surface Labs qualifies leads during the form, routes them to the right rep or calendar based on their responses, captures drop-offs, and triggers workflows, all from one platform without external automation tools. --- # Generative AI Search Optimization: What Google's New Guidance Actually Changes | Surface Labs URL: https://surface.thesurface.network/blog/generative-ai-search-optimization-new-google-guidance-act A marketing operator opens a planning doc and sees the same anxiety in three different columns: SEO, AI visibility, and content quality. The team wants to know whether they need a new strategy for AI Overviews and AI Mode, or whether they should keep fixing the same website issues they already know exist. Google's [May 2026](https://withsurface.com/blog/may-marketing-updates) guidance gives that team a useful answer, although not a complete one. Google published its guide to optimizing for generative AI features on Google Search on May 15, 2026. Google says its generative AI features, including AI Overviews and AI Mode, rely on core Search ranking and quality systems, retrieval-augmented generation, and query fan-out. For marketers, that means the same foundations still matter: useful content, crawlable pages, index eligibility, clear technical structure, helpful media, and a page experience that gives visitors confidence. Google also gives teams a list of tactics they can safely ignore for Google Search. The guide says site owners do not need special AI text files, tiny AI-specific content chunks, AI-only rewrites, or special structured data for generative AI visibility. Google also warns teams against creating pages for every possible query variation and against seeking inauthentic mentions across the web. This guidance does not mean AI visibility work is pointless. It means marketers should stop letting acronym culture replace operational judgment. A strong AI visibility program still needs prompt testing, citation tracking, source-mix analysis, and platform-specific measurement. The content and technical work underneath those measurements should remain human-useful and technically sound. ## The core shift: content needs to be citable, not merely publishable A publishable page fills a slot on the calendar. A citable page gives a human or system enough confidence to reuse its claims. Marketers should make that distinction visible in their editorial process. A citable page usually includes a clear answer, a specific audience, current sources, a visible point of view, examples, tradeoffs, and a next step. The page does not need to be longer for its own sake. Google's guidance explicitly says there is no ideal page length for [generative AI Search](https://withsurface.com/blog/generative-engine-optimization-services). The page needs to satisfy the human visitor and give the system a trustworthy structure to retrieve from. Teams should review priority pages with four questions. Who wrote or approved this? What firsthand or expert perspective does the page add? Which claims need a source or example? What should a buyer do after reading it? Those questions turn content from a word-count exercise into an evidence asset. ## Technical SEO still controls whether AI systems can use the page Generative AI Search does not erase crawlability. Google still needs to find and process pages before it can consider them. Technical teams should therefore review the same unglamorous systems that have always separated durable content programs from brittle ones. Start with index eligibility. Priority pages should return successful status codes, avoid accidental noindex directives, expose indexable content, and give Google permission to show snippets. Review JavaScript-heavy pages to make sure critical content does not disappear behind rendering issues. Audit internal links so valuable pages are discoverable through HTML paths rather than orphaned inside a CMS collection. Next, review duplicate URL states. Faceted navigation, parameterized URLs, pagination, canonical mistakes, and content duplication can waste crawl demand and blur the source of truth. AI search raises the cost of ambiguity because systems need a clean, trustworthy answer path. Marketers can use AI tools responsibly in this workflow. A team can ask a model to identify fan-out questions around a topic, compare competing pages, summarize source material, identify stale claims, and generate a first-pass structure. Then a human editor should decide which claims matter, which examples prove them, which sources deserve trust, and how the piece should sound. The team should document that process. Create a short editorial checklist for every priority page: target audience, primary intent, source anchors, evidence blocks, internal links, conversion path, freshness date, and reviewer. This gives writers a repeatable standard and helps leaders distinguish production speed from publishing quality. Step 1: Audit the top twenty AI-visible candidates Choose the pages most likely to matter in AI Search: category pages, product pages, comparison pages, strategic blogs, glossary pages, and high-intent landing pages. Review crawlability, index status, internal links, title/H1 clarity, source support, freshness, and conversion path. Step 2: Add evidence blocks For each page, add the proof that a human would need before trusting the answer. Use data, examples, screenshots, quotes from named experts where available, customer proof, limitations, and definitions. Avoid invented authority. If a claim cannot be sourced or explained, soften it. Step 3: Build clusters around real buyer questions Do not create dozens of thin fan-out pages. Instead, build a cluster that covers the real research path: definition, use case, comparison, implementation, risks, pricing or cost structure, alternatives, and proof. Link the pieces together so people and crawlers can walk the path. Step 4: Measure AI surfaces separately Google says AI Search optimization remains SEO, but Ahrefs, Semrush, and academic studies show citation behavior can diverge from rankings. Track AI Overviews, AI Mode, ChatGPT, Copilot, Perplexity, and other relevant surfaces separately when the buyer journey justifies the work. ### Is GEO different from SEO? Google says optimizing for generative AI features in Google Search remains part of SEO because those features rely on core Search systems. Marketers can still use GEO as a label for AI visibility measurement, citation tracking, and source-mix work, but they should not use it as an excuse for machine-only content. ### Do marketers need llms.txt to rank in Google AI features? Google says site owners do not need special AI text files or markup to appear in generative AI Search. Teams should focus on crawlability, useful content, and standard SEO foundations. ### How often should teams refresh AI-visible pages? Teams should refresh pages when claims, screenshots, pricing, product details, statistics, or competitive context change. For strategic pages, quarterly review is a practical baseline. Schema recommendation: Article schema with author, dateModified, citation links where appropriate, and BreadcrumbList. Use FAQPage only if the final page includes a visible FAQ and the site's schema policy supports it. --- # Generative Engine Optimization Services Need a Real Content Strategy Behind Them | Surface Labs URL: https://surface.thesurface.network/blog/generative-engine-optimization-services ## Generative Engine Optimization Services Need a Real Content Strategy Behind Them I started recording lectures because I wanted to create an archive of how I actually talk about marketing, not just a pile of prompts that could make any company sound like any other company. Yet, when given the room to speak endlessly, I found myself circling back to the same practical question: when a team publishes something how does that piece help customers, search engines, and now AI systems understand what the business actually does? That question matters even more for teams buying generative engine optimization services, because AI visibility rewards clear expertise badly when a company gives it scattered, shallow, or strategically confused material to work with. A lot of people will sell GEO like they discovered a secret trapdoor in the internet. They will talk about prompt visibility, AI citations, answer engine optimization, entity signals, structured data, and all sorts of things that sound thrilling if you have been staring at declining organic traffic charts for too long. Some of those tactics matter, and serious teams should study how Google describes [AI features and websites](https://developers.google.com/search/docs/appearance/ai-features), how Bing describes content across search and Copilot surfaces in its [Webmaster Guidelines](https://www.bing.com/webmasters/help/webmaster-guidelines-30fba23a), and how AI answers cite or summarize pages. But leaders should not mistake a new search surface for a new excuse to skip content strategy. A team that wants AI visibility still needs to answer the oldest content strategy questions with more discipline than before. Who do we need to reach? What do they already understand? What do they misunderstand? Which questions show early research, which questions show comparison behavior, and which questions show purchase intent? What should we publish first, what should we connect together, and what should we stop publishing because it teaches the market the wrong thing about the company? When I describe old content farming, I use the image of teams loading a bunch of content into a shotgun and praying one of the terms would take off. That worked better in an older search environment because teams could create thousands of thin pages, change a few words, and wait for some accidental traffic. The more modern version of that mistake looks cleaner because teams now wrap it in AI workflows, templates, and dashboards, but the strategic problem stays the same. A company can publish a thousand AI-assisted pages and still fail to tell the market what it knows. A marketing team can ask a model to generate glossary terms, comparison pages, listicles, and prompt-targeted FAQs, then accidentally create a website that feels broad, busy, and forgettable. A leader can buy AI search optimization work and still underperform because the company never decided which ideas deserved authority, which pages deserved internal support, and which service areas deserved the most public explanation. Google tells site owners to create helpful, reliable content for people, and its guidance on [people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) gives teams a useful floor for quality. Bing gives teams another useful floor when it describes how it discovers, crawls, indexes, evaluates, and surfaces content across search, Copilot, and grounding API experiences in its [Webmaster Guidelines](https://www.bing.com/webmasters/help/webmaster-guidelines-30fba23a). A serious GEO program should build from that floor, not treat AI visibility as a loophole around it. Someone searching “what is content?” behaves very differently from someone searching “best content marketing firm in Dallas, Texas.” The first person might not know what marketers mean when they call everything content. The second person probably has a buying problem, a shortlist problem, or at least a serious vendor-research problem. A strategist who treats those two queries the same will produce bad SEO content and worse GEO content. Teams should make the same distinction for generative search. A person who asks an AI system “what is generative engine optimization?” needs a definition, a plain-language explanation, and a few examples. A person who asks “best generative engine optimization services for B2B SaaS” needs a much more commercial answer with selection criteria, proof, risks, and a clear explanation of what a vendor actually does. A person who asks “how do I know if my company appears in AI answers?” needs a measurement framework, not a poetic paragraph about the future of search. A strategist should map those questions before anyone drafts a page. The team should group prompts and keywords by informational, comparative, and transactional intent, then assign the right page type to each group. The team can use AI to speed that mapping, but people still need to make the judgment calls because people understand what the company sells, which customers matter, and which questions should lead toward a conversation with sales. ## Build Interconnected Islands, Not Isolated GEO Pages Content strategy as the work of creating “interconnected islands that are all clearly bridged together.” I like that image because most companies do sell more than one thing, and most marketing teams need customers to understand how those things relate. A company that offers [marketing strategy](https://www.withsurface.com/marketing-strategy), managed content operations, AI visibility audits, and GTM engineering cannot explain each service like it lives alone on a private island with no bridge, no boat, and no reason to exist near the others. GEO makes those bridges more important. AI systems summarize, retrieve, cite, and reason across clusters of information rather than admiring a single page in isolation. A company that wants visibility in generated answers needs a coherent content network with pillar pages, support articles, glossary entries, comparison pages, case studies, and service pages that reinforce each other. Google’s [link best practices](https://developers.google.com/search/docs/crawling-indexing/links-crawlable) still matter here because teams use internal links to help people and crawlers understand what each linked page covers. A GEO services provider should therefore care about [content hubs for SEO](https://www.withsurface.com/blog/content-hubs-for-seo), site taxonomy, and internal linking strategy, not only prompt tracking or citation monitoring. A strategist should ask which pages carry authority, which pages support them, which pages answer adjacent questions, and which pages move a reader toward a service. When teams skip that architecture, they ask AI systems to infer coherence from a website that people never made coherent in the first place. ## Match Content Depth to the Actual Question A lot of marketers still treat word count like a confidence trick. They assume that a longer page must be a more serious page, and they ask writers to stretch a basic answer into a 1,500-word performance of expertise. I called that impulse pretty plainly in the recording because teams waste time when they answer the same question six different ways just to satisfy a minimum word count. GEO services should not encourage that behavior. A team that wants AI answers to cite or summarize its content needs pages that answer questions cleanly, demonstrate expertise clearly, and give readers enough context without burying the answer. A “what is GEO?” page might deserve a concise definition and a few practical examples. A guide to building an AI visibility strategy across SEO, content operations, analytics, and sales enablement deserves more depth because leaders need more help making decisions. Google’s [SEO Starter Guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide) still frames SEO around helping search engines understand content and helping users find useful information. That basic idea gives teams a healthy restraint. A strategist should not ask, “How long does this need to be to look serious?” A strategist should ask, “How much explanation does this person need to make the next good decision?” Content briefs changed the way editors and strategists scaled production. A good brief helps a writer understand the format of a page, the target keyword, the intent, the internal links, the required sections, and the proof needed to make the argument credible. A good brief also helps a marketer wrangle product teams, executives, and subject-matter experts who care deeply about accuracy but do not always want to write the page themselves. The problem begins when teams start worshiping the brief. In the recording, I said the template should be a baseline and should not ever become the optimal goal. Teams can put the keyword in the H1, add supporting terms to H2s, place a CTA near the top, add internal links, and still publish a page that feels like someone poured lukewarm vanilla ice cream into a content management system. The page can be structurally correct and strategically empty. GEO can make this worse because people want a hack. They want a markdown template, a system prompt, a schema checklist, or a repeatable page pattern that makes every answer engine suddenly understand them. Templates help teams move faster, but strategists still need to decide what the company believes, what the reader needs, what makes the answer more useful than the obvious answer, and why an AI system should treat the page as a reliable source. Leaders should make content strategy reflect business priority, not only expertise. A company might have deep knowledge in one service area because a founder, consultant, or technical lead likes talking about it. If the team publishes disproportionately around that area, search engines and AI systems may start to understand the company through that overrepresented topic. A simple example makes the problem obvious. If a company publishes 470 pages about technical site architecture and 63 pages about SEO, crawlers and AI systems will see far more repeated language around site architecture. If site architecture only represents five percent of the business, leaders have created a visibility problem by letting internal enthusiasm distort the public content footprint. They did not simply publish too much. They taught the market the wrong hierarchy. GEO services should include that kind of audit. A strategist should compare page count, internal links, keyword targets, AI prompts, service priorities, revenue priorities, and sales conversations. A team should then rebalance the site so the most important offers receive enough definitional, comparative, proof-driven, and conversion-oriented content to make the business legible. AI visibility starts to improve when people make the company easier to understand. ## Treat GEO as a Content System, Not a Reporting Dashboard A reporting dashboard can tell leaders where a brand appears, where competitors appear, which pages get cited, and which prompts produce weak or missing visibility. That information helps, and serious teams should measure it. But a dashboard does not solve the problem any more than a bathroom scale cooks dinner. A team needs a content system behind the measurement. Strategists need to translate visibility gaps into new pages, rewritten pages, stronger definitions, better comparison assets, clearer internal links, better evidence, sharper examples, and more useful service pages. Writers need original source material from founders, operators, sales calls, customer conversations, and subject-matter experts. Editors need a voice profile, a proof standard, and a link plan that connects the new work to the rest of the site. A good GEO content strategy should therefore include four layers: what people ask, what AI systems answer, what the company has already published, and what the business needs the market to understand next. The team should revisit those layers every month because search behavior, AI answer surfaces, competitors, and company priorities will keep changing. Leaders who treat GEO as a one-time optimization project will usually end up with a prettier version of the same old content problem. A serious GEO engagement should begin with strategy, not page production. The provider should audit the company’s current content, classify pages by topic and intent, identify missing definitions and comparison pages, review internal links, map AI prompts to buyer questions, and compare the public content footprint to actual business priorities. The provider should also interview the people inside the company who have useful expertise because AI systems cannot cite expertise that the company never publishes. After that audit, the team should build a prioritized roadmap. Some companies need foundational explanations because they use language that customers do not understand. Some companies need stronger comparison content because buyers ask AI systems to shortlist tools, agencies, vendors, or frameworks. Some companies need better proof because they make claims that sound plausible but unsupported. Some companies need fewer pages because they have already published too much low-difference content. Then the team should produce content with a real editorial standard. Writers should use transcripts, SME interviews, customer questions, sales objections, product documentation, and credible external references. Editors should check the work against [helpful content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content), [AI-generated content guidance](https://developers.google.com/search/blog/2023/02/google-search-and-ai-content), and the company’s own voice rules. Strategists should connect every new asset to the site architecture so each page improves the whole system rather than floating around like another disconnected island. Teams should not buy generative engine optimization services because they want to chase a new acronym. They should buy GEO work because customers now ask questions in more places, engines now synthesize more answers, and companies need to make their expertise legible across search, AI, sales, and content surfaces. That work belongs inside a broader marketing strategy process, not outside it. For Surface, the service logic should stay pretty simple. Leaders need strategy that explains what the company should be known for. Teams need content operations that turn that strategy into pages, essays, newsletters, videos, and sales materials. Operators need GTM engineering that connects content to measurement, workflows, reporting, and distribution. GEO fits inside that system because AI visibility depends on the same thing good content has always depended on: clear ideas, useful answers, credible proof, and a website that tells the market what the business actually does. Generative engines did not eliminate content strategy. They made weak content strategy more obvious. If a company gives AI systems disconnected pages, generic templates, vague service explanations, and a lopsided content library, the company should expect confused answers. If a company gives people and systems a coherent body of useful, specific, well-linked expertise, it gives itself a much better chance of becoming the answer. The best GEO services will not promise leaders that they can trick AI systems into noticing a company. They will help leaders decide what the company should say, where it should say it, how each page should connect, and why the market should trust the answer. That sounds less magical than most AI search pitches, which is probably a good sign. Most marketing teams do not need more content poured into the machine. They need someone to look at the machine, the map, the buyer, the business, and the language all at once, then say: here is what we should build next, here is what we should stop doing, and here is how we make the company easier to understand. --- # Generative engine optimization services: A buyer's guide | Surface Labs URL: https://surface.thesurface.network/blog/generative-engine-optimization-services-buyers-guide A buyer opens three generative engine optimization proposals and finds three nearly identical promises. Each provider will improve visibility, build authority, and help the brand appear in AI answers. Only one proposal explains which buyer questions will be tested, how often the answers will be sampled, who will make the recommended changes, or what happens after a citation sends someone to the website. That missing operating detail is the difference between buying a report and buying a program. Generative engine optimization is still a young category, so the same label can describe an agency retainer, a monitoring platform, a content package, or an internal SEO team with a new dashboard. Buyers need to compare the work underneath the label. Generative engine optimization services help a company understand and improve how its brand, products, experts, and pages appear in AI-generated answers. A credible program usually covers prompt research, multi-engine measurement, citation and source analysis, technical accessibility, content planning, off-site evidence, execution, and business reporting. Surface has a commercial interest in this category. Our [AI Visibility Engineering platform](https://www.withsurface.com/platform/ai-visibility) tracks buyer questions, citations, mentions, competitors, and content gaps, then connects those findings to reviewed campaign work. That makes Surface a fit for teams that want measurement and execution in one operating loop. A consulting agency may be a better fit when a company wants most strategy and production handled externally, while a standalone tool can suit a mature team that already has writers, developers, digital PR support, and a dependable publishing workflow. No provider can guarantee a recommendation. Answers change by engine, wording, location, model, source availability, and repeated run. Microsoft makes a similar distinction in its [AI Performance documentation](https://blogs.bing.com/webmaster/February-2026/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview): a citation count shows that a page was referenced, but it does not establish ranking, authority, placement, or influence inside the answer. A useful engagement begins by finding where the brand is absent, misunderstood, cited without being mentioned, or mentioned without receiving a recommendation. The baseline should use buyer questions with clear commercial relevance rather than a bag of prompts chosen because they happen to mention the category. For each prompt family, the provider should record the engine, answer date, brand presence, cited pages, named competitors, recommendation order, and source mix. One answer can create false confidence, so the method needs repeated samples. Our guide to [reporting GEO without fake precision](https://www.withsurface.com/blog/ai-visibility-measurement-is-messy-how-to-report-geo-without-fak) explains why mentions, citations, recommendations, and downstream influence need separate fields. The diagnosis also has to include ordinary SEO. Google's current [generative AI optimization guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) says its AI search features still depend on core search ranking and quality systems. Crawlability, index eligibility, internal links, useful original content, and accurate visible information remain foundational. A provider that jumps directly to rewriting paragraphs without checking the site's technical and editorial structure is skipping the retrieval layer. Monitoring creates a list of observations. It does not create a market position. Once the service finds that competitors own a buyer question, someone still has to decide whether the answer is a better category page, a comparison, an evidence update, a case study, a technical correction, a partner mention, or no new content at all. This is where service models separate: Delivery model Best fit Useful strength Important limitation GEO agency Teams that want external strategy and production Adds specialist capacity and may coordinate content, technical work, and digital PR Quality depends heavily on the assigned team, and learning can remain outside the client's systems Standalone GEO tool Teams with strong internal execution Provides prompt monitoring, source discovery, and competitor tracking Dashboards can accumulate findings faster than the team can act on them Integrated operating platform Teams that want measurement connected to campaign work Moves from buyer questions and gaps into governed briefs, content, publishing, and remeasurement Requires internal owners to approve priorities, evidence, and brand judgment Internal SEO and content team Companies with mature research, engineering, editorial, and PR resources Keeps expertise and institutional knowledge close to the business The team must build its own sampling method, source analysis, workflow, and reporting discipline Surface follows the integrated model. [Content Campaign Agents](https://www.withsurface.com/platform/content-campaigns) can turn buyer evidence into a reviewed campaign plan, while Surface's [content operations workflow](https://www.withsurface.com/solutions/launch-campaigns-faster) keeps sources, approval, connected assets, and outcomes on the same plan. Nothing publishes until a person approves it, because autonomous publishing is a poor substitute for ownership. Buyers should expect more than a visibility score. Ask the provider to show the actual operating artifacts it will deliver: - A prompt map organized by buyer problem, intent, journey stage, engine, and commercial priority - A repeatable baseline that separates retrieval, citation, mention, recommendation, and conversion - A source analysis showing which owned, editorial, community, review, video, and competitor pages shape the answers - A technical review covering crawlability, indexation, rendering, internal links, canonical behavior, and important text hidden behind client-side interactions - An action backlog with owners, evidence requirements, effort, expected learning, and a reason each item deserves investment - A publishing and distribution workflow that preserves human review and factual accountability - A remeasurement schedule connected to qualified traffic, lead quality, pipeline, and sales feedback The original [GEO research paper](https://arxiv.org/html/2311.09735v3) found that citations, quotations, and statistics could improve source visibility in its benchmark, but the authors also found that results varied by domain. Treat those findings as evidence for testing, not a universal recipe. If a service turns an experimental result into a promise that every page needs the same formula, it has replaced strategy with formatting. Begin with the method. Which engines are monitored? How many repeated samples are taken? Can the buyer inspect the exact prompt set and source record? Does the provider distinguish a citation from a recommendation? How are logged-in states, regions, prompt wording, and model changes handled? Then ask about action. Who changes the website? Who verifies competitor and product claims? Can the program work inside the existing CMS, CRM, analytics stack, and approval rules? How will it find off-site evidence gaps without manufacturing mentions or pretending owned content is independent coverage? Finish with the business case. Which conversions will be observed directly? Which pipeline claims will be attributed or modeled? How will the team recognize that a prompt family has little commercial value and stop spending time on it? [Traffic Intelligence](https://www.withsurface.com/platform/infrastructure/traffic-intelligence) connects content performance, buyer engagement, AI referrals, lead quality, and pipeline so teams can examine the journey without collapsing every touch into one credit claim. [Surface is a marketing system that learns from revenue](https://www.withsurface.com/what-is-surface). For GEO work, that means choosing buyer prompts, measuring answers, finding competitive gaps, creating reviewed campaign work, and feeding qualified-demand outcomes into the next cycle. Surface can work alongside the CMS and CRM already in place, so teams keep their systems of record while adding an operating layer for action and learning. Surface is less appropriate for a company seeking a single PDF audit with no continuing measurement, a fully outsourced editorial department with minimal internal review, or a promise that AI citations will produce a fixed amount of revenue. Those needs call for a different delivery model, and the last promise is not credible from any provider. The right purchase should close the distance between an answer-engine observation and a responsible marketing decision. If your team wants to see how buyer prompts, content gaps, campaign work, and revenue feedback can live in one system, [book a Surface walkthrough](https://www.withsurface.com/book-a-demo) using your own category and current visibility questions. --- # Go-to-market execution: Turn the plan into operable work | Surface Labs URL: https://surface.thesurface.network/blog/go-to-market-execution-operable-work The launch date is twelve days away, and the positioning deck is approved. The landing page uses an older claim, sales has a different account list, and the form routes every response to one queue. Nobody has confirmed which event starts the nurture or how the team will recognize a qualified response. Calling this a content backlog understates the problem. The plan has not been converted into operable work. Go-to-market execution begins when strategic choices become named objects, dependencies, owners, controls, and observable outcomes across the systems buyers touch. Go-to-market execution is the coordinated work that turns a market choice and offer into a buyer experience and a measurable commercial motion. It includes the campaign brief, messages, proof, assets, distribution, conversion path, qualification, routing, sales response, instrumentation, and feedback needed to launch and learn. Execution quality is continuity. The audience and promise in the strategy should remain recognizable in the ad, article, landing page, form, follow-up, and sales conversation. Each component may have a different owner, but the team needs one version of the decision and an explicit way to handle changes. Surface provides that operating layer across existing marketing systems. Its [content campaign workflow](https://www.withsurface.com/platform/content-campaigns) can assemble buyer evidence into a brief and coordinated asset plan. People approve the strategy and outputs, while connected systems carry the approved context into publishing, conversion, and measurement. A strategy contains choices. A launch needs artifacts that preserve those choices. Define the smallest set your team can operate consistently: - a market and audience record with inclusion, exclusion, and trigger criteria; - a message record with the problem, promise, proof, objections, and approved claims; - a campaign brief with outcome, owner, dates, channels, assets, conversion action, and budget; - a journey map that covers the response path, qualification, routing, follow-up, and recycle logic; - an instrumentation plan naming events, properties, source handling, dashboards, and outcome fields; - a decision log recording changes, approvers, rationale, and expected effect. These artifacts work as living contracts. If the target segment changes, the change should reach the account list, brief, copy, form logic, route, sales talk track, and scorecard. A project board can track that work, but it cannot decide which version is commercially true. [Surface's faster campaign launch workflow](https://www.withsurface.com/solutions/launch-campaigns-faster) starts from approved buyer insight and can develop related articles, landing pages, nurture, social content, and proof assets. Named reviews remain part of the path before anything publishes. Campaign calendars show dates. Dependency maps show what can make those dates false. Build the map around decisions and handoffs rather than asset names alone. Workstream Must be true before launch Owner at the decision point Failure visible after launch Market and message Segment, problem, offer, claim, and evidence approved Product marketing or GTM lead Wrong response, objection mismatch, weak conversion Campaign production Brief, source material, formats, reviewers, and publish path ready Campaign owner Drift, rework, missed date, inconsistent claims Conversion Page, form, consent, confirmation, scheduling, and fallback tested Growth or web owner Abandonment, duplicate work, incomplete records Lead operations Enrichment, qualification, route, ownership, alert, and SLA tested Revenue operations Delays, rejects, lost context, queue backlog Sales readiness Coverage, talk track, proof, objections, and feedback fields ready Sales leader Slow response, generic follow-up, unusable feedback Measurement Events, identifiers, source fields, CRM outcomes, and report owners ready Analytics owner Reach without interpretation, attribution disputes Run a tabletop test before release. Take one plausible buyer from first exposure to closed or recycled outcome. Ask what each system knows, which rule fires, who is notified, what the buyer sees, and how the result returns to the campaign record. This catches mismatched assumptions more reliably than checking boxes by department. A GTM launch benefits from a few explicit gates. The readiness gate confirms that the offer, proof, journey, ownership, compliance review, and measurement plan are complete. The release gate checks production behavior in the actual environment. The learning gate confirms that someone will inspect the response and can change the motion. Do not make every edit wait for a committee. Assign review by risk. A new regulated claim may need legal and product approval. A headline variation within an approved message may need only the campaign owner. Routing logic needs the operations owner and a controlled test. The [Surface content publishing workflow guide](https://www.withsurface.com/blog/seo-friendly-cms-what-content-teams-need-before-they-start) explains why permissions, previews, structured fields, rollback, and analytics should be designed before production volume grows. Automation should carry approved decisions. It should not conceal their absence. Define the outcome, context, limits, approval point, and failure path before an agent or workflow acts. Surface's [build-your-own agent workflow](https://www.withsurface.com/platform/build-your-own) follows that structure and lets teams connect the necessary context while retaining human guardrails. A practical marketing launch strategy often uses four overlapping periods. Before launch, confirm the market thesis, assemble proof, produce the core experience, test conversion and routing, prepare sales, and establish the baseline. During controlled release, send a limited audience through the entire path and fix operational failures before buying scale. At full release, monitor delivery, buyer behavior, lead quality, route performance, and sales response. After release, separate immediate repair from slower strategic judgment. Surface [Dynamic Lead Forms](https://www.withsurface.com/platform/dynamic-lead-forms) can adapt questions to known visitor and account context and connect responses to qualification and follow-up. The [GTM engineering view](https://www.withsurface.com/for/gtm-engineers) brings web instrumentation, enrichment, routing, CRM state, and scheduling into the same execution problem. A live page only begins the launch; completion requires a buyer to move through the promised path. Use leading indicators to operate the launch and outcome indicators to judge the motion. Delivery, page errors, form failures, queue depth, response time, and missing fields can reveal execution problems quickly. Qualified meetings, accepted pipeline, opportunity movement, wins, and losses take longer but speak more directly to commercial value. Label what the data can support. An observed sequence shows what happened. Attribution applies a model to credit. Inference explains a plausible relationship that still needs testing. The distinction becomes useful when a campaign reaches buyers across dark social, AI answers, direct traffic, events, and sales contact that no single platform can reconstruct perfectly. The Content Marketing Institute and MarketingProfs [2026 B2B research](https://contentmarketinginstitute.com/b2b-research/b2b-content-marketing-trends-research), based on 1,015 respondents, reports that effective teams frequently credit content quality, team capability, sales alignment, customer understanding, and measurement. Those are operating conditions. Publishing more assets does not repair a broken handoff between them. [Surface's intelligent attribution system](https://www.withsurface.com/intelligent-attribution) connects source, lead quality, sales acceptance, pipeline, wins, and losses back to future rules and campaign work. Teams can keep the CRM, CMS, analytics, and scheduling tools they already use while Surface acts across the boundaries. Hold a short operational review during launch and a deeper decision review after enough commercial evidence arrives. Fix a failed route immediately. Give a new message enough time and volume to learn. Record both choices so the next launch starts with memory instead of folklore. Go-to-market execution is the discipline of making the plan survivable across people and systems. If your launch dates are clear but the dependencies, handoffs, and learning path are not, [book a Surface demo](https://www.withsurface.com/book-a-demo) and map one upcoming motion into operable work. --- # Go-to-market strategy for B2B teams that need execution | Surface Labs URL: https://surface.thesurface.network/blog/go-to-market-strategy-b2b-execution The go-to-market deck is polished enough to survive any board meeting. It names the market, ideal customer, positioning, channels, pipeline target, and launch date. The first campaign brief still begins with a blank audience field because nobody translated the ideal customer into an account list, a message, a proof requirement, a conversion path, or a sales handoff. B2B teams rarely lack a plan-shaped document. They lack an operating connection between the market choice and the work a buyer experiences. A useful go-to-market strategy tells the team what to build, who owns it, which systems must cooperate, and what evidence will change the next decision. In practice, a go to market strategy for B2B defines which market and buyer the company will pursue, which problem and offer it will lead with, how it will create and capture demand, how sales will continue the interaction, and how revenue outcomes will improve the next cycle. The strategy joins market selection, positioning, product marketing, campaigns, conversion, lead operations, sales coverage, customer proof, and measurement. B2B buying stretches across people, channels, and time. A prospect may encounter a search result, AI answer, founder post, peer recommendation, landing page, form, sales response, case study, and security review before anything becomes revenue. The company needs enough shared context that those moments feel related. [Surface is an intelligent marketing system that learns from revenue](https://www.withsurface.com/what-is-surface). It connects buyer signals, campaign history, product context, CRM outcomes, specialized agents, inbound conversion, and revenue feedback without replacing the CMS, CRM, analytics, or scheduling systems already in place. "Mid-market companies" works as a database filter and remains too broad to define a useful market. Add the operational conditions that make the problem urgent and the offer credible: current stack, team shape, growth event, regulatory pressure, buying trigger, failed alternative, geography, and the people who feel the cost. For a go to market strategy for startups, constraint is especially important. A young company cannot educate every segment, support every integration, and run every channel at once. Choose a market narrow enough that product evidence, founder expertise, sales conversations, and early content can reinforce the same claim. A go to market strategy for fintech often needs another layer of proof. The buyer may care about security, compliance, auditability, data ownership, implementation risk, and internal approval alongside the product outcome. Those are parts of the buying experience and should appear in the strategy before sales discovers them one deal at a time. Turn the market choice into a decision record: included segments, excluded segments, triggering conditions, buyer roles, costly status quo, current alternative, reason to believe, and evidence still missing. Revisit it when pipeline quality or win-loss evidence challenges the thesis. Positioning gives the company a stable answer to who the product is for, what problem it solves, which category helps buyers understand it, and why the approach is defensible. Campaigns turn a part of that position into a timed reason to pay attention. Use a B2B go to market strategy framework that makes the translation visible: Strategic question Operating artifact Evidence to inspect Which market will we pursue? Segment definition and account universe Fit, reachable demand, sales conversations, and product success Which change do buyers need? Problem statement and campaign objective Search language, calls, support, community, and customer research Why should they believe us? Message, proof library, case studies, and product evidence Approved claims, outcomes, demonstrations, and third-party sources How will they encounter it? Content, paid, outbound, partner, event, and sales coverage plan Audience presence, channel economics, source influence, and capacity What happens when they respond? Landing page, form, qualification, route, response, and scheduling Completion, fit, speed, context, and meeting quality How will the strategy learn? Shared scorecard and feedback cadence Accepted pipeline, opportunity movement, wins, losses, and segment patterns Surface [Content Campaign Agents](https://www.withsurface.com/platform/content-campaigns) turn qualified-lead, opportunity, ICP, call, and search evidence into an audience, message, campaign outcome, and reviewed asset plan. Keeping the evidence beside the planned work lets a person accept, edit, or reject it before an agent carries the decision forward. Once a buyer responds, the strategy still has work to do. Decide which action each campaign asks for, how much information is necessary, how known account context can shorten the form, what qualifies the lead, who owns the response, and which context must reach sales. [Dynamic Lead Forms](https://www.withsurface.com/platform/dynamic-lead-forms) can adapt questions using visitor and account context, preserve partial responses, and connect the form to automated action. Surface's [GTM engineering workflow](https://www.withsurface.com/for/gtm-engineers) connects web instrumentation, forms, enrichment, qualification, routing, CRM ownership, and revenue context. These are not post-launch configurations. They determine whether the campaign's promise survives contact with an interested person. Marketing and sales should agree on lifecycle definitions, acceptance criteria, rejection reasons, response expectations, recycle rules, and ownership before launch. A sales go to market strategy becomes fragile when targeting is sophisticated and the handoff is a generic notification with an email address. In the first month, validate the market and the operating path. Review recent wins and losses, customer evidence, search and AI visibility, account coverage, current campaigns, forms, qualification, routing, sales capacity, and measurement. Choose one market problem and one measurable conversion path. During the second month, launch a connected campaign. Create the core page, proof, distribution assets, form experience, sales follow-up, and dashboard from the same brief. [Surface's campaign workflow](https://www.withsurface.com/solutions/launch-campaigns-faster) can carry one approved insight into an article, landing page, nurture, proof post, social work, and sales asset while preserving named reviewers. In the third month, examine qualified response rather than declaring victory from reach. Which segments engaged? Which messages produced accepted leads? Where did buyers leave? What did sales hear? Which proof moved the conversation? Keep the observations, attribution, and inference labels separate. Then choose whether to deepen, revise, narrow, expand, or stop. Keep the strategy stable enough to coordinate work and flexible enough to learn. A few weak leads should not trigger a new market. Repeated accepted-pipeline and win-loss patterns should eventually change targeting, proof, content, qualification, and channel investment. Based on 1,015 respondents, the 2026 Content Marketing Institute and MarketingProfs [B2B survey](https://contentmarketinginstitute.com/b2b-research/b2b-content-marketing-trends-research) found that effective teams often credited content relevance and quality, team capabilities, sales alignment, customer understanding, and measurement. Those factors sit across functions, which is why a B2B GTM plan cannot live only with marketing or only with sales. [Surface's intelligent attribution system](https://www.withsurface.com/intelligent-attribution) writes accepted, won, and lost outcomes back into future rules, routes, briefs, and campaigns. That makes the go-to-market strategy a maintained operating model rather than an annual belief document. A B2B strategy becomes real when a buyer can move through it. If your market thesis is clear but execution still fragments across campaign documents, forms, CRM rules, and disconnected reports, [book a Surface demo](https://www.withsurface.com/book-a-demo) and bring one motion you want to make operable. --- # GTM metrics: A shared scorecard for marketing and sales | Surface Labs URL: https://surface.thesurface.network/blog/gtm-metrics-shared-scorecard Marketing reports a strong quarter: more search visibility, more engaged accounts, and a lower cost per lead. Sales reports a weak one: too many rejected handoffs, slower opportunities, and little revenue from the promoted segment. Both reports may be numerically correct. The disagreement starts earlier than the dashboard. The teams are measuring different populations, time windows, journey stages, and decisions. Shared GTM metrics do not force every function to value the same leading indicator. They show how attention becomes a response, how a response becomes accepted work, and where the motion stops carrying value. GTM metrics measure whether a company is reaching the intended market, creating a useful buyer response, converting and routing that response, developing qualified pipeline, and learning from revenue outcomes. A shared scorecard should combine leading, operational, and outcome measures without presenting every association as causal attribution. Each metric needs a contract: business question, precise definition, numerator, denominator, population, time window, source, owner, evidence level, and decision it can change. The scorecard should also preserve enough context to compare segments, campaigns, messages, assets, routes, and sales outcomes. [Surface is designed as a marketing system that learns from revenue](https://www.withsurface.com/what-is-surface). It connects buyer signals, campaign history, content work, conversion, lead operations, CRM outcomes, and feedback across the tools already in place. That makes a shared scorecard actionable because the result can revise a route, brief, audience, or campaign rather than ending in a monthly slide. Marketing activity appears quickly. Revenue develops slowly. A person may discover the company today, return through a different channel next month, join an opportunity with several stakeholders, and become part of recognized revenue much later. Comparing this week's spend with this week's revenue can be mathematically clean and operationally useless. Choose time windows that fit each question. Use near-real-time monitoring for broken forms, failed routes, and delivery. Use weekly or monthly cohorts for response and sales acceptance. Use longer opportunity and revenue windows that match the buying cycle. Keep event date, lead creation date, opportunity creation date, close date, and cohort date distinct. Agree on the journey states as well. A page view, known person, qualified response, accepted lead, held meeting, opportunity, closed-won account, and expanded customer are different units. The record should preserve relationships among people, accounts, campaigns, and opportunities rather than pretending one lead row represents the sale. A useful scorecard lets teams inspect the path without assuming that the last measurable touch caused the outcome. Layer Core question Example measures Decision enabled Market attention Are relevant buyers finding and recognizing us? Qualified search visibility, AI citations and mentions, target-account reach, direct and referral discovery Topic, source, distribution, and market coverage Buyer engagement Are they consuming evidence related to a real problem? Engaged account rate, return rate, key-page progression, asset use, content-assisted journeys Message, proof, format, and journey design Conversion Can an interested buyer take the next useful action? Form start and completion, meeting request, partial capture, conversion by segment Offer, form, page, scheduling, and friction Operations Does the response reach the right owner with context? Match rate, route success, response time, sales acceptance, rejection reasons Enrichment, qualification, ownership, capacity, and SLA Pipeline Does accepted demand become commercial work? Meeting held rate, opportunity creation, stage progression, pipeline value, cycle time Coverage, follow-up, proof, and investment Revenue Does the motion produce and retain value? Win rate, revenue, expansion, retention, payback, loss reasons Market thesis, product, pricing, channel, and budget Use formulas that expose the population. Sales acceptance rate might be accepted routed leads divided by all routed leads eligible for sales review in the same cohort. Opportunity creation rate might be created opportunities divided by accepted leads, segmented by route, market, and elapsed time. A rate without a stable denominator becomes a story generator. An observed result says that an event or sequence appeared in the data. An attribution result applies a defined model to distribute credit. An inference explains what the team believes may have influenced the outcome. The three can coexist, but their labels should remain visible. Google's documentation on using [Search Console and Google Analytics together](https://developers.google.com/search/docs/monitor-debug/google-analytics-search-console) explains that the products measure different parts of the journey and that clicks and sessions will not match exactly. Google Analytics also lets an administrator choose an [attribution model and lookback window](https://support.google.com/analytics/answer/10596866?hl=en). Those settings affect reported credit; they do not reveal a single objective cause. This distinction becomes more important with AI discovery. Google's 2026 Search Console [generative AI performance report](https://developers.google.com/search/blog/2026/06/gen-ai-performance-reports) reports clicks and impressions from supported generative AI experiences. Bing Webmaster Tools' [AI Performance public preview](https://blogs.bing.com/webmaster/February-2026/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview) reports citation trends, cited pages, and grounding queries, and explicitly warns that a citation does not by itself show rank, prominence, or importance. [Surface AI Visibility](https://www.withsurface.com/platform/ai-visibility) tracks commercially relevant prompts, citations, brand mentions, competitors, and content gaps across answer engines. Treat each signal according to what it demonstrates. A citation is evidence of retrieval in an observed answer. A mention is evidence of representation. Neither guarantees recommendation, a visit, an opportunity, or revenue. The dashboard should let a team move from a summary to the underlying journey. [Surface Traffic Intelligence](https://www.withsurface.com/platform/infrastructure/traffic-intelligence) connects content and source activity with form behavior, AI referrals, lead quality, pipeline, and revenue context. Segment-level views help answer whether a strong top-line rate hides weak performance in the market the company intended to reach. Give every review a purpose. A weekly operations review should resolve missing data, route failures, response delays, and sudden conversion changes. A monthly motion review should compare cohorts, segments, messages, sources, accepted pipeline, and reasons for rejection. A quarterly strategy review should reconsider market investment, positioning, proof, channel mix, and capacity. For each red or green metric, record the interpretation, confidence, owner, and next decision. A drop caused by a broken form needs repair. A drop caused by lower-fit traffic may support a targeting change. A small fluctuation may need no action. The report becomes useful when it helps the team choose among those responses. The Surface guide to [attribution versus incrementality](https://www.withsurface.com/blog/attribution-is-not-incrementality-how-to-measure-ai-creative) explains why credited conversions and causal lift answer different questions. When a spend decision is consequential, use experiments, holdouts, or other incrementality methods where feasible instead of asking attribution alone to prove impact. Measurement is incomplete if the insight depends on someone remembering it during the next brief. [Surface's intelligent attribution system](https://www.withsurface.com/intelligent-attribution) can write accepted, won, and lost outcomes back into qualification rules, routes, campaign planning, and content work. Human owners still decide whether a pattern is strong enough to change the motion. Keep the scorecard compact. If a metric has no owner, no trusted definition, and no plausible decision, move it to diagnostic analysis rather than the shared executive view. Preserve supporting detail for investigation, but let the main scorecard tell a coherent journey from intended market to commercial outcome. Shared GTM metrics will not eliminate healthy disagreement. They make the disagreement inspectable. If marketing and sales can see the same journey but cannot yet connect its systems or outcomes, [book a Surface demo](https://www.withsurface.com/book-a-demo) and bring the scorecard your teams currently debate. --- # How Agencies Can Build Recurring Revenue With Vertical Lead Ops on Surface URL: https://surface.thesurface.network/blog/how-agencies-can-build-recurring-revenue-with-vertical-lead-ops-on-surface Most marketing agencies sell campaigns. They run ads, build landing pages, write copy, and report on impressions and clicks. When the campaign ends — or the client's budget gets cut — the revenue disappears. The agency is always one client decision away from losing a chunk of their income. The agencies building durable, recurring revenue have shifted from selling campaigns to selling infrastructure. Specifically: vertical lead operations systems built on Surface Labs that clients can't easily turn off because the system runs their intake, qualification, and routing. Here's the model. Three characteristics make lead ops the ideal agency service: **It's sticky.** Once a law firm's entire intake system runs through Surface — with practice-area routing, attorney matching, follow-up sequences, and CRM integration — they're not going to rip it out because they found a cheaper ad agency. The switching cost is operational, not just contractual. **It's measurable.** Lead ops delivers metrics that clients understand: consultation bookings, response time, qualified leads, cost per acquisition. No more arguing about whether impressions matter or what brand awareness is worth. The dashboard shows pipeline impact. **It scales across clients.** A lead ops system built for one personal injury firm can be adapted for another PI firm in a different market in a day. The form structure, qualification logic, and routing patterns are 80% reusable. Each new client deployment gets faster and more profitable. ### Tier 1: Setup + optimization ($3,000–$8,000 one-time) **What you deliver:** Build the complete lead ops system — intake forms, qualification rules, routing logic, response templates, follow-up sequences, CRM integration, and performance dashboard. Launch in 1–2 weeks. **What the client gets:** A working intake system that qualifies, routes, and responds to leads automatically. Full visibility into their lead flow metrics. ### Tier 2: Managed lead ops ($1,500–$4,000/month recurring) **What you deliver:** Ongoing optimization — A/B testing form variants, refining qualification criteria based on conversion data, adjusting routing as the team changes, monitoring performance, and producing monthly reports. **What the client gets:** A lead ops system that gets better every month. They don't need to hire an internal ops person. You are their ops team. ### Tier 3: Full-stack lead gen + lead ops ($5,000–$15,000/month) **What you deliver:** Paid advertising + content + landing pages + the full lead ops system. You own the funnel from first click to booked meeting. **What the client gets:** Pipeline, measured end-to-end. No black box between ad click and revenue. Generic agencies compete on price. Vertical agencies compete on expertise. When you build lead ops for law firms, you learn the practice-area routing patterns, the statute-of-limitations urgency triggers, the attorney matching variables, and the compliance requirements. The second law firm deployment takes half the time. The tenth takes a quarter. Vertical Unique value you build Reusability across clients **Law firms** Practice-area branching, urgency detection, jurisdiction routing, compliance language 80%+ reusable across firms in same practice areas **Real estate** Buyer/seller segmentation, agent matching by geography and specialization, timeline-based nurture 80%+ reusable across teams in same market structure **Insurance** Multi-line risk capture, carrier-based routing, state compliance fields, quote abandonment recovery 70%+ reusable (carrier-specific customization needed) **Home services** Emergency vs. scheduled routing, service-type matching, seasonal campaigns, post-service automation 85%+ reusable across similar service companies **Healthcare** Symptom screening, insurance verification, provider matching, HIPAA-conscious configuration 70%+ reusable (provider-specific customization needed) Pick one vertical. Build deep expertise. Dominate it. Then expand to adjacent verticals with the same underlying platform. A typical agency scenario — one vertical, modest growth: Month Clients Monthly recurring revenue One-time setup revenue Total monthly Month 1 2 $5,000 $12,000 $17,000 Month 3 5 $12,500 $6,000 $18,500 Month 6 10 $25,000 $6,000 $31,000 Month 12 18 $45,000 $6,000 $51,000 By month 12, the agency has $45,000/month in recurring revenue from lead ops alone — revenue that doesn't disappear when a campaign budget gets cut because the client depends on the system for their daily operations. Compare this to a campaign-only agency where every dollar is project-based and at risk every quarter. Surface is the platform that makes this model scalable. Build once for a vertical, deploy across clients with configuration (not custom development), monitor across your entire portfolio from one dashboard, and deliver measurable results that justify recurring fees. For agencies looking to escape the project-based revenue trap, vertical lead ops on Surface is the highest-margin, stickiest service offering available. Build the expertise, deploy the system, and let the recurring revenue compound. --- # How B2B Marketing Has Changed in the Last 3 Years | Surface Labs URL: https://surface.thesurface.network/blog/how-b2b-marketing-has-changed-in-the-last-3-years Three years ago — early 2022 — the B2B marketing playbook was still recognizable. Generate leads with content and paid campaigns. Score them with behavioral models. Nurture them through email sequences. Hand them to sales when they hit MQL threshold. The stack was stable, the metrics were familiar, and the biggest debates were about attribution models and content strategy. Then three things happened simultaneously: AI went mainstream, ad costs spiked, and buyer behavior shifted permanently. The marketing function that exists today is fundamentally different from the one that existed in 2022 — and most teams haven't fully adapted. ## Shift 1: AI collapsed the content moat In 2022, content was a competitive advantage. Producing high-quality blog posts, whitepapers, and email sequences at scale required writers, editors, and ops people. Companies that invested in content outperformed those that didn't, because good content was hard to produce. By 2025, every company can produce adequate content with AI tools. The floor has risen dramatically. A founder with Claude can produce a passable blog post in 10 minutes. An email sequence that used to take a copywriter a day takes an hour. The implication: content is no longer a moat. Every company has it. The differentiation has shifted from "who produces the best content" to "who converts content-driven traffic most effectively." The companies winning aren't the ones with the best blog — they're the ones with the best infrastructure for turning blog readers into booked meetings. B2B CPCs across Google, Meta, and LinkedIn have risen 20–40% since 2022. For companies spending $50K–$200K/month on paid channels, this means the same budget generates fewer clicks than it did three years ago. The response from most teams was predictable: optimize the ads. Better creative, tighter targeting, new channels. This helps at the margins. But the highest-leverage response — improving what happens after the click — has been largely ignored. When a click cost $5, losing 40% of leads to slow follow-up was expensive but survivable. When a click costs $15–$50, the same 40% loss rate is catastrophic. The math changed, and the teams that adapted focused less on generating leads and more on converting them. The B2B buying process compressed. In 2022, a buyer might spend 3–4 weeks researching before filling out a form. By 2025, the same buyer does that research in 3–4 days — often in a single afternoon. They read your case studies, check G2 reviews, compare pricing, and submit a demo request all in one session. This compression has two effects on marketing. First, the lead that fills out your form is further along in their decision than they used to be — they don't need nurture, they need a conversation. Second, they're evaluating you and two competitors simultaneously — the first company to respond with something useful wins the meeting. Speed-to-lead went from "nice to have" to "the most important metric in the funnel." A 2022 response time of 4 hours was normal. In 2025, it's a death sentence — the buyer has already booked with a competitor. The teams that have fully adapted to these three shifts share common characteristics: **They measure cost per meeting, not cost per lead.** CPL tells you how much you paid for a form submission. Cost per meeting tells you how much you paid for pipeline. The teams that shifted to this metric discovered their "efficient" campaigns weren't efficient at all. **They qualify at capture, not in nurture.** Instead of scoring leads over weeks of email engagement, they ask qualifying questions on the form — budget, timeline, company size — and route based on the answers immediately. The qualification that used to take 2 weeks now takes 30 seconds. **They respond in under 60 seconds.** Automated capture-to-response pipelines that qualify, route, and respond before the lead closes the tab. No CRM notification delays. No rep availability dependencies. **They focus investment on the capture-to-meeting layer.** The infrastructure between "form submission" and "meeting booked" is where they spend their optimization time — not on ad creative or email subject lines. Surface was built for the post-2022 B2B marketing reality — where content is abundant, clicks are expensive, and buyers won't wait. Capture, qualification, routing, and instant response in one system that converts more of your existing traffic into pipeline. If your marketing playbook still looks like 2022 — score leads, nurture them for weeks, hand them to sales — the market has moved on. Surface was built for where the market is now. --- # How Good Is Your Lead Process? A Simple Scorecard | Surface Labs URL: https://surface.thesurface.network/blog/how-good-is-your-lead-process-a-simple-scorecard Most teams know their lead process has problems. They can feel it — leads falling through cracks, reps complaining about quality, pipeline that doesn't match ad spend. But they can't point to exactly where it's breaking or how bad it actually is. This is a simple diagnostic. Ten yes-or-no questions, followed by a scoring framework. It takes 5 minutes. By the end, you'll know whether your lead ops need a tune-up or a rebuild. Answer each question honestly. "Sort of" counts as no. **1\. Do you know your average speed-to-lead — the time between form submission and first rep outreach?** Most teams don't measure this. If you don't have a number, that's your first problem. **2\. Is your average speed-to-lead under 5 minutes?** If you don't know, it almost certainly isn't. The companies that measure it are the ones that have already fixed it. **3\. Does every lead source — website, ads, third-party, events — flow through the same capture system?** If different campaigns use different form tools with different fields, your data is fragmented before it even reaches the CRM. **4\. Are leads qualified before they reach a rep?** Not enriched — qualified. Does the lead come with budget, timeline, use case, or company size data captured at the form level? Or does the rep have to ask all of that on the first call? **5\. Does your routing logic account for more than round-robin?** Territory, deal size, product interest, rep availability — if your routing is just "next person in line," you're matching leads to reps by luck. **6\. Can you change a routing rule and have it take effect immediately?** If updating routing requires a Salesforce admin, a Zapier rebuild, or a ticket to engineering, your system can't keep up with your business. **7\. Does every lead get a personalized response within 60 seconds?** Not a generic autoresponder. A message that references what they asked about, who's going to help them, and what happens next. **8\. Can you trace a single lead from ad click to form fill to rep conversation to outcome?** Full-funnel visibility. If you need to pull data from 3+ platforms to build this view, you don't really have it. **9\. Do you know your cost per meeting booked — not cost per lead?** CPL is a vanity metric if half your leads never get a conversation. Cost per meeting booked tells you what you're actually paying for pipeline. **10\. Have you tested any part of your lead flow in the last 6 months?** Form fields, routing logic, response timing, qualification criteria — any controlled test, not just a gut-feel change. Count your "yes" answers, then find your range. Score Rating What it means 9–10 Dialed in Your lead ops are a competitive advantage. You're in the top 5% of B2B teams. Focus on testing and marginal optimization. 7–8 Solid foundation Core infrastructure works. You likely have 1–2 gaps — speed-to-lead or full-funnel visibility are the usual ones. Fix those and you're elite. 5–6 Common gaps This is where most $10M–$50M companies land. The pieces exist but they're not connected. Leads are leaking at the seams between systems. 3–4 Significant issues Multiple parts of the flow are broken or manual. You're losing a measurable percentage of your ad spend to infrastructure failure. 0–2 Full rebuild needed Your lead process is costing you more than your lead generation. Every improvement here will have outsized ROI because the baseline is so low. Most teams reading this will land between 3 and 6. That's not a judgment — it's the reality of how lead ops gets built at most companies. Duct tape, Zapier, and good intentions. The checklist is designed so that questions 1–4 test your capture and qualification layer, questions 5–7 test your routing and response layer, and questions 8–10 test your measurement and optimization layer. If you said "no" mostly in 1–4, your problem is at the top of the flow — leads enter the system with bad data, no qualification, and no urgency. Fixing capture and qualification will have the highest immediate impact. If you said "no" mostly in 5–7, your capture might be fine but leads die in routing. They go to the wrong rep, wait too long, or get a generic response that kills momentum. Routing and response are where speed-to-lead lives. If you said "no" mostly in 8–10, you might have decent infrastructure but no way to measure or improve it. You're flying blind — making decisions on gut feel instead of data. Most teams have problems in all three layers. That's because the layers are connected — bad capture leads to bad routing leads to bad measurement. Fixing one without fixing the others just moves the bottleneck. Surface was built to cover all three layers — capture, routing, and measurement — in one system. If your score landed below 7, most of your "no" answers map directly to gaps that Surface closes. If you scored yourself honestly and didn't like the number, that's the starting point. The next step is picking the layer where you're losing the most and fixing it first. --- # How Insurance Agencies Are Beating Lemonade at Their Own Game | Surface Labs URL: https://surface.thesurface.network/blog/how-insurance-agencies-are-beating-lemonade-at-their-own-game Lemonade, Root, and the other direct-to-consumer insurance carriers built their entire pitch on one thing: speed. Apply in 90 seconds. Get a quote in 3 minutes. Buy a policy before lunch. Independent agencies have been losing market share to these carriers — not because their coverage is worse (it's usually better) or their prices are higher (they're often competitive), but because the buying experience is painfully slow by comparison. A prospect fills out a "Get a Quote" form, waits hours for a callback, spends 20 minutes on the phone giving the agent information the form should have captured, and then waits another day for the actual quote. The agencies fighting back aren't hiring faster. They're building intake systems that match direct-to-consumer speed while offering the expertise and coverage options that carriers like Lemonade can't. They made one strategic decision: capture all qualifying data upfront, in a self-service flow, and deliver a result immediately. Lemonade's signup asks for address, property details, coverage preferences, and personal info in a conversational interface. By the end of the flow, the applicant has a quote. No waiting. No callback. No "someone will be in touch." This works for simple, standardized policies. It falls apart for complex needs — multi-line coverage, commercial policies, unusual risk profiles, or anything requiring underwriting judgment. That's where independent agencies have the advantage. They just haven't built the experience to match. ### Progressive risk capture on the form Instead of name, email, phone, and "what type of insurance do you need?" — build forms that capture the actual risk data agents need to quote. For auto: vehicle year/make/model, number of drivers, zip code, current coverage level, driving record (any accidents or tickets?). For home: property type, year built, square footage, zip code, current coverage, claims history. For life: age, tobacco use, general health status, coverage amount. This data used to require a 20-minute phone call. On a multi-step form, it takes 2–3 minutes. The prospect doesn't mind answering because they expect it — they've been trained by Lemonade to provide details in exchange for a fast result. ### Instant ballpark quote (not a binding quote — an expectation-setter) After the form, show a ballpark range: "Based on your profile, most drivers in your area with similar coverage pay $120–$180/month." This isn't a binding quote. It's an expectation-setter that keeps the prospect engaged while the agent prepares the real quote. The prospect gets something immediately (directional pricing). The agent gets a pre-qualified lead with full risk data. Both sides win. ### Agent routing by license and carrier The prospect's state and coverage type determine which agent can actually help them. Route by: state license (agents are licensed by state), carrier appointments (not every agent can write every carrier), line specialization (personal vs. commercial), and availability. A commercial liability inquiry in Florida goes to a Florida-licensed producer with commercial carrier appointments — not into a generic queue. ### Quote abandonment recovery Insurance quote forms are longer than most B2B forms, so abandonment rates are higher — 35–50% of people who start don't finish. Capture partial submissions (any field completed before exit) and trigger recovery: **10 minutes after abandonment:** "You were 2 minutes away from your quote. Pick up where you left off: \[link\]." **24 hours:** "Still looking for coverage? Here's a simplified way to connect: \[one-click scheduling link\]." **72 hours:** Final nudge with a different angle: "Most people in \[zip code\] save $X when they compare quotes. Want to see yours?" Recovery rates of 15–25% are realistic — and these are leads you already paid to generate. Metric Traditional intake Surface-powered intake Time from form submit to agent contact 3–8 hours Under 5 minutes Quote completion rate 35–45% 55–65% (with abandonment recovery) Quote-to-bind rate 12–18% 22–30% Agent time per lead (pre-qualification) 15–30 minutes 2–3 minutes (data already captured) Cost per bound policy $300–$500 $120–$200 The agencies winning aren't competing with Lemonade on technology. They're competing on experience — matching the speed while offering the expertise, carrier options, and advocacy that a direct-to-consumer chatbot can't provide. Surface powers the intake experience that lets agencies compete on speed: multi-line quote forms with conditional risk questions, agent routing by license and carrier appointments, instant response with ballpark pricing, and quote abandonment recovery. All pushing pre-qualified leads into the agency management system. The DTC carriers built a better front door. Surface lets agencies build one too — without the $100M in venture capital. --- # How Much of Your Marketing Stack Do You Actually Use? | Surface Labs URL: https://surface.thesurface.network/blog/how-much-of-your-marketing-stack-do-you-actually-use Your marketing stack has 9 tools. You pay for all of them. You actively use about 4. The other 5 are either running on autopilot with settings nobody's reviewed in a year, used by one person for one narrow task, or genuinely forgotten — still billing monthly because nobody remembered to cancel them. This is the utilization problem. It's not unique to any one company or any one platform. It's a structural outcome of how marketing technology gets adopted: one tool at a time, each solving an immediate need, with no periodic review of whether the full stack still makes sense. The result is that most B2B marketing teams are overspending on tools by 30–50%. Not because the tools are bad — but because the team doesn't use what they're paying for. Here's a simple framework. For every tool in your stack, answer three questions: **Who uses it?** If the answer is "one person" or "I'm not sure," the tool is at risk of being underutilized or completely unused. Tools that depend on a single person's knowledge are also the most likely to break silently when that person leaves. **What do you use it for?** List the specific features. Not what the tool can do — what your team actually does with it. For most platforms, the list is shorter than expected. **Is there overlap?** Does another tool in your stack do the same thing? CRM with forms + separate form tool. Marketing platform with scheduling + separate Calendly account. CRM with automation + separate Zapier for automations. Most teams running this audit discover that their effective stack — the tools and features actually driving pipeline — is 40–60% of what they're paying for. Some patterns show up across nearly every mid-market B2B company: Tool / feature What you pay for What you actually use **Marketing automation (enterprise tier)** Advanced workflows, predictive scoring, ABM, adaptive testing, custom events, revenue attribution Email sends, basic workflows, a simple scoring model, and standard reporting **Enrichment provider** 5,000 credits/month, full API access, intent signals 1,500 credits/month on form fills. No API integration. Intent signals unused. **CRM (enterprise)** Custom objects, advanced reporting, forecasting AI, territory management Contact/deal management, basic pipeline views, a few dashboards **ABM platform** Account identification, engagement scoring, orchestration, advertising integration Account lists and basic intent signals. Orchestration unused. **Analytics** Custom event tracking, funnel analysis, cohort reporting, predictive analytics Pageviews, form conversions, and traffic sources **Middleware (Zapier/Make)** Multi-step paths, filters, conditional logic, error handling 4–6 simple Zaps that push data between tools The enterprise tier exists for teams with dedicated ops resources who can configure and maintain advanced features. Most teams buy enterprise because they want the capability in theory — but in practice, they operate at the professional tier level while paying enterprise tier prices. Unused tools aren't free just because nobody's actively using them. They cost money in three ways. **Direct cost.** The subscription itself. A tool that costs $300/month and doesn't get used is $3,600/year in pure waste. Across 3–4 underutilized tools, that's $10K–$20K/year. **Maintenance cost.** Even unused tools need occasional attention — login credential management, security updates, integration monitoring. Every tool in the stack is a surface area for potential issues. **Complexity cost.** More tools means more integrations, more data flows, and more places where things can break. Simplifying the stack reduces the maintenance burden on ops teams and makes the remaining tools easier to manage and optimize. You don't need to rip out your entire stack. Right-sizing is about three moves: **Downgrade where you're underutilizing.** If you're on the enterprise tier of a platform and only using professional-tier features, downgrade. The annual savings on a single downgrade — say, HubSpot Enterprise to Professional — can be $20K–$40K. **Eliminate overlap.** If two tools do the same job, pick the better one and cancel the other. Common overlaps: CRM forms + standalone form tool, CRM scheduling + Calendly, CRM automation + Zapier. **Consolidate point solutions.** If you have separate tools for forms, routing, enrichment, and scheduling, evaluate whether a single lead ops layer can replace 3–4 of them. This reduces both cost and complexity. Surface consolidates the capture, qualification, routing, and response layer into one tool — often replacing a standalone form tool, a middleware layer (Zapier), and a scheduling tool. That's 3 subscriptions and their associated maintenance replaced by one. If your marketing stack has 9 tools and you actively use 4, the other 5 represent both cost savings and complexity reduction. Surface was built to be part of the 4 you actually need — not one of the 5 you're paying for but not using. --- # How Surface Labs Works With HubSpot URL: https://surface.thesurface.network/blog/how-surface-labs-works-with-hubspot If you're on HubSpot, you don't need to leave HubSpot. Surface sits in front of your HubSpot CRM — handling the capture, qualification, routing, and instant response layer — and pushes clean, qualified, routed leads directly into HubSpot where your team already works. Here's exactly how the integration works, what changes for your team, and what stays the same. Surface replaces the upstream layer — everything between "visitor lands on your site" and "qualified lead appears in HubSpot assigned to the right rep." **Smart forms.** Surface forms replace HubSpot forms on your high-intent pages — demo requests, pricing inquiries, contact forms. Multi-step, conditional logic, qualifying questions built in. Low-intent forms (newsletter signups, content downloads) can stay on HubSpot forms. **Real-time qualification.** Form responses + enrichment data are evaluated against your criteria at the moment of submission. Budget, timeline, company size, and use case determine whether the lead is sales-ready, nurture-track, or disqualified — before it enters HubSpot. **Attribute-based routing.** The lead is matched to the right rep based on territory, deal size, product interest, and real-time availability. The assignment is made at the moment of capture, not by a HubSpot workflow that runs minutes later. **Instant personalized response.** Within 60 seconds of form submission, the lead receives a message referencing what they asked about, who's going to help them, and a direct scheduling link. This fires automatically — before the assigned rep takes any action. **Embedded scheduling.** The lead can book directly on the matched rep's calendar in the form flow — no separate meetings link, no follow-up email. Everything it's already good at: **Contact records.** The lead arrives in HubSpot as a contact with all data populated — form responses, qualification score, enrichment data, routing assignment, and meeting details. No manual data entry. **Pipeline management.** Once a deal is created, HubSpot manages stages, forecasting, and deal tracking as usual. **Email sequences.** For leads routed to nurture (not sales-ready), HubSpot's email tools handle the ongoing engagement. Surface tags the lead with the appropriate nurture track so HubSpot workflows can pick it up automatically. **Reporting.** HubSpot's reporting and dashboards continue to work. Surface adds its own metrics (speed-to-lead, routing accuracy, lead-to-meeting rate) that complement HubSpot's campaign and pipeline reporting. **Existing workflows.** Any HubSpot workflows triggered by contact creation or property changes continue to fire normally. They just receive better data — because the contact arrives pre-qualified and pre-routed. The integration is a one-directional push: Surface → HubSpot. Data Where it's created Where it lands in HubSpot Contact info (name, email, company) Surface form HubSpot contact record (standard properties) Qualification data (budget, timeline, company size, use case) Surface form + enrichment HubSpot custom properties (created during setup) Qualification score / segment Surface qualification engine HubSpot custom property Routing assignment (rep name) Surface routing engine HubSpot contact owner Lead source + campaign Surface form (UTM parameters) HubSpot contact source properties Meeting details Surface scheduling HubSpot meeting activity Enrichment data (employee count, industry, revenue) Surface enrichment HubSpot company properties The contact record in HubSpot looks like any other contact — except it arrives with more data, already assigned to the right owner, and often with a meeting already booked. **For reps:** Nothing changes about how they work. Leads appear in HubSpot the same way they always have — in their contact owner view, in their task queue, in their pipeline. The difference is that leads arrive faster, with more context, and already assigned correctly. Reps spend less time reviewing and qualifying, more time selling. **For marketing:** Surface forms replace HubSpot forms on high-intent pages. Marketing still controls the form design, qualifying questions, and campaign targeting. They gain visibility into post-capture metrics (speed-to-lead, lead-to-meeting rate) that HubSpot doesn't provide natively. **For ops:** Routing rules move from HubSpot workflows to Surface's routing engine. This is simpler to manage — rules are configured in a UI, changes take effect immediately, and there are no multi-workflow chains to maintain. HubSpot workflows that handle post-routing automation (sequences, task creation, deal creation) continue to work. The integration typically takes 1–3 days: **Day 1:** Connect Surface to your HubSpot account. Map Surface fields to HubSpot properties (Surface creates custom properties automatically for qualification data). Configure your first form with qualifying questions. **Day 2:** Set up routing rules — territory, segment, product interest, availability. Configure the instant response template. Test with 5–10 test submissions to verify data flows correctly. **Day 3:** Deploy the Surface form on your demo request or contact page. Monitor the first batch of real leads to confirm routing accuracy and response speed. No migration of historical data. No CRM reconfiguration. No retraining your sales team. Surface is the capture-to-meeting layer that HubSpot doesn't have. It handles the real-time, high-speed part of the lead flow — qualification, routing, response, and scheduling — and pushes the result into HubSpot where your team manages the rest. If you're on HubSpot and your leads take hours to get a response, Surface fixes that without changing anything else about how your team uses HubSpot. --- # How Surface Labs Works With Salesforce URL: https://surface.thesurface.network/blog/how-surface-labs-works-with-salesforce Your sales team lives in Salesforce. Your pipeline is in Salesforce. Your reporting runs on Salesforce. Nobody is ripping that out — and nobody should. Surface doesn't replace Salesforce. It fixes the layer Salesforce was never built to handle: the real-time capture, qualification, routing, and response that happens in the first 60 seconds after a lead fills out a form. Surface handles that layer and pushes a clean, qualified, routed lead into Salesforce — ready for your team to work. **Smart form capture.** Surface forms replace your current form tool (native web forms, HubSpot forms, Typeform) on high-intent pages. Multi-step conditional logic, qualifying questions, and embedded scheduling built in. **Real-time qualification.** The lead is scored and segmented at the moment of form submission — based on form responses and enrichment data. No waiting for a Salesforce Flow to process, no batch scoring overnight. **Attribute-based routing.** The lead is matched to the right rep before it enters Salesforce. Territory, deal size, product interest, and availability are evaluated in real time. The lead arrives in Salesforce already assigned to the correct owner. **Instant response.** A personalized message fires within 60 seconds — referencing the lead's stated interest, introducing the assigned rep, and including a scheduling link. The lead is already engaged before the Salesforce notification reaches the rep. **Embedded scheduling.** The lead books on the matched rep's calendar during the form flow. By the time the lead record appears in Salesforce, there's often already a meeting on the calendar. Everything it already handles: **Lead and contact records.** Surface creates the lead or contact record in Salesforce with all data populated — form responses, qualification score, enrichment data, and routing assignment. **Opportunity management.** Once a deal is created from the Surface-generated lead, Salesforce manages the pipeline — stages, forecasting, collaboration, approvals. **Reporting and dashboards.** Salesforce's reporting continues to work. Surface-created leads carry full attribution data (source, campaign, UTM parameters) so your Salesforce reports reflect the impact of every channel. **Flows and automation.** Existing Salesforce Flows triggered by lead creation or field updates continue to fire. They just receive better inputs — pre-qualified, pre-routed leads with complete data. **Einstein and AI features.** If you're using Salesforce Einstein for scoring or next-best-action, it benefits from the richer data Surface provides at the lead level. Data Created by Surface Lands in Salesforce as Contact info Surface form Lead or Contact record (configurable) Qualification data Surface form + enrichment Custom fields on Lead/Contact Qualification score Surface engine Custom field (number or picklist) Segment assignment Surface engine Custom field (Enterprise / Mid-market / SMB) Rep assignment Surface routing Lead Owner or Contact Owner Lead source + campaign Surface (UTM capture) Campaign Member + Lead Source field Enrichment data Surface enrichment Company/Account fields Meeting booked Surface scheduling Event record + task Surface can create Leads or Contacts depending on your Salesforce data model. For teams using the Lead object → conversion flow, Surface creates Leads. For teams that skip Leads and go straight to Contacts + Opportunities, Surface creates Contacts with an associated Account. Salesforce's built-in lead assignment rules are limited. They evaluate one criterion at a time, they can't check real-time rep availability, and modifying them requires a Salesforce admin. Most teams that outgrow basic assignment rules move to Salesforce Flows — but Flows for routing quickly become complex. A routing flow that evaluates territory + deal size + product interest + availability requires multiple decision elements, loops, and custom Apex if the logic gets sophisticated enough. It's powerful but brittle — changes take days, testing is manual, and failures are silent. Surface replaces this with a dedicated routing engine that evaluates multiple variables simultaneously, checks real-time availability, handles fallbacks automatically, and can be modified by ops teams without a Salesforce admin. The CRM receives the routing output — a lead already assigned to the right owner — and doesn't need to make the routing decision at all. **For reps:** Nothing. Leads appear in Salesforce in their queue, assigned to them, with full data. The experience is the same as today — except leads arrive faster, with more context, and more of them have meetings already booked. **For Salesforce admins:** Routing logic moves out of Salesforce Flows and into Surface. This simplifies the Salesforce org — fewer Flows to maintain, fewer failure points, fewer support tickets about leads going to the wrong person. The admin still manages post-routing automation (deal creation, task assignment, approval processes) in Salesforce. **For ops:** Surface becomes the place where capture and routing rules are managed. Changes take effect immediately without a Salesforce deployment. The Salesforce integration is configure-once — Surface handles field mapping during setup and maintains the sync automatically. **Day 1:** Connect Surface to Salesforce via OAuth. Map fields — Surface auto-detects standard objects and creates custom fields for qualification data. Configure your first form. **Day 2:** Build routing rules in Surface. Test with sample submissions — verify lead records appear correctly in Salesforce with the right owner, right data, and right custom field values. **Day 3:** Deploy on your high-intent pages. Monitor the first day of live leads. No Salesforce package installation required. No custom Apex. No managed package dependencies. Surface is the real-time layer that Salesforce needs but doesn't have. Fast capture, instant qualification, intelligent routing, and sub-60-second response — pushing the result into Salesforce where your team works. If your Salesforce lead assignment rules or routing Flows have become a maintenance burden, and your speed-to-lead is measured in hours instead of seconds, Surface fixes both problems without changing how your team uses Salesforce. --- # How Surface Labs Works With Slack URL: https://surface.thesurface.network/blog/how-surface-labs-works-with-slack Your sales team doesn't live in the CRM. They live in Slack. That's where they see notifications, coordinate handoffs, escalate issues, and decide which leads to call first. A lead notification buried in a Salesforce email digest at 4 PM is a missed opportunity. A Slack message with full context at the moment of routing is an immediate action trigger. Surface's Slack integration turns lead routing into real-time team communication — so reps see leads, act on them, and collaborate on them where they already spend their day. When a lead is captured, qualified, and routed, Surface sends a structured notification to Slack with everything the rep needs to act immediately. **The notification includes:** The lead's name, company, and contact info. Their qualification data — budget range, timeline, company size, use case — captured on the form. Enrichment data — employee count, industry, revenue, tech stack. The qualification score and segment assignment. Which rep was routed the lead and why (territory match, product match, etc.). A direct link to the lead's CRM record. A direct link to the lead's scheduling page (if they haven't booked yet). And the timestamp — so the rep and their manager can see how fast the response was. All of this appears in Slack within seconds of form submission. The rep doesn't need to open the CRM to get context. They have everything they need to pick up the phone or send a personalized follow-up right from the Slack notification. Surface lets you route notifications to different Slack channels based on the lead's attributes — so the right team sees the right leads. Lead type Slack channel Who sees it Enterprise qualified (500+ employees, budget confirmed) #enterprise-leads Enterprise AE team + sales leadership Mid-market qualified #mm-leads Mid-market SDR team SMB / self-serve #smb-leads SMB team or automated — no notification needed High-priority (high ICP + active timeline) #hot-leads Entire sales team + leadership. These are the "drop everything" leads. Routing failures (hit default queue) #lead-ops-alerts Ops team. Something didn't match — investigate. This means enterprise leads don't clutter the SMB team's channel. Hot leads get maximum visibility. And routing failures are surfaced immediately to the people who can fix them — not discovered days later in a CRM report. The notification isn't just informational — it's actionable. **Claim the lead.** If routing assigns to a pool rather than an individual, reps can claim the lead directly from Slack. First to claim gets the assignment. This works well for teams with shared territories or overflow queues. **Mark as contacted.** Reps can update the lead status directly from Slack — "contacted," "left voicemail," "meeting booked." This keeps the team informed without requiring everyone to check the CRM. **Reassign.** If a rep is unavailable or the lead would be better handled by someone else, they can reassign from Slack. The reassignment updates Surface's routing record and the CRM simultaneously. **Add notes.** Quick context from the rep — "spoke with Sarah, she's evaluating 3 tools, decision by end of month" — visible to the team without opening the CRM. Beyond individual lead notifications, Surface sends operational alerts to Slack that keep the team and leadership informed: **Speed-to-lead alert.** If a lead hasn't been contacted within your SLA (default: 5 minutes), Surface pings the assigned rep and their manager. "Lead from Acme Corp submitted 5 minutes ago — no contact yet." **Daily digest.** A morning summary in the team channel: leads received yesterday, average speed-to-lead, meetings booked, routing accuracy. Takes 10 seconds to read and gives leadership a pulse check without requesting a report. **Routing anomaly alert.** If the default queue is accumulating leads (meaning routing rules aren't matching), Surface alerts the ops team. "12 leads hit default routing in the last 24 hours — review rules." **Meeting booked celebration.** When a lead books a meeting, the team channel gets a notification. It's a small thing, but it creates visibility into what's working and gives reps a reason to respond fast. The fastest-responding teams aren't faster because their reps are more diligent. They're faster because their notification infrastructure puts the right information in the right place at the right time. A CRM email notification sent to a rep's inbox competes with 50 other emails. A Slack notification with full lead context, delivered to a dedicated channel the rep is already watching, gets seen and acted on in minutes. The difference between a 4-hour response time and a 4-minute response time is often just the notification layer. The rep was willing to call. They just didn't see the lead until hours later. Surface's Slack integration is native — not a Zapier workaround that sends basic notifications. Full lead data, channel routing, actionable buttons, operational alerts, and daily digests — all configured in Surface and delivered where your team already works. If your reps are responding to leads slowly because CRM notifications get buried, Surface's Slack integration fixes the visibility problem. The lead data is already there. The routing already happened. The rep just needs to see it — and Slack is where they'll see it fastest. --- # How Surface Labs Works With Your CRM, Not Instead of It URL: https://surface.thesurface.network/blog/how-surface-labs-works-with-your-crm-not-instead-of-it The first question we get from every buyer is some version of: "Are you trying to replace my CRM?" No. Surface is not a CRM. It doesn't manage your pipeline, track deals, store customer records, or run sales reports. It does the job that happens before your CRM — the capture, qualification, routing, and response layer that determines what enters the CRM and how good it is when it gets there. This distinction matters because the CRM is the most entrenched tool in every company's stack. Nobody wants to rip it out. Nobody should have to. Your CRM — Salesforce, HubSpot CRM, Pipedrive, Zoho, Attio, Close — is the system of record for your customer relationships. It does several things well: **Pipeline management.** Tracking deals through stages, forecasting revenue, and giving sales leaders visibility into what's coming. **Contact and account records.** The central database of everyone your company has ever interacted with — contacts, companies, deal history, activity logs. **Reporting.** Revenue reporting, sales performance metrics, deal velocity, win/loss analysis. **Workflow automation.** Post-lead workflows — deal stage changes, task assignment, email sequences, internal notifications. For all of these jobs, the CRM is the right tool. Surface doesn't do any of them — and isn't trying to. CRMs weren't built to handle the real-time, high-speed layer between a form submission and a sales conversation. They can be configured to approximate it — but it's never their core strength. Requirement How CRMs handle it The gap **Smart form capture** Built-in form builders with basic fields. Limited conditional logic. Forms capture data but don't qualify, adapt, or schedule. **Real-time qualification** Lead scoring runs on behavioral data over time. Not instant. Leads are scored after the fact, not at the moment of capture. **Attribute-based routing** Assignment rules or Flow Builder. Requires admin configuration and maintenance. Possible but complex to set up, hard to change, and limited in the variables it can evaluate simultaneously. **Sub-60-second response** Workflow-triggered emails can send quickly. But they're not connected to routing decisions or personalized with qualification data. The CRM can notify the rep, but the speed depends on the rep seeing and acting on the notification. **Embedded scheduling** CRM meetings tools exist but are separate from forms. Lead fills out form → waits → gets scheduling link later. No continuous form-to-calendar flow. The CRM was designed to manage relationships, not to win the first 60 seconds. Using it for both is like using a truck for drag racing — it can technically do it, but it wasn't built for it. The architecture is simple: Surface handles upstream (everything before the CRM), and the CRM handles downstream (everything after). **Surface does:** Lead capture from all sources with smart, qualifying forms. Real-time qualification — scoring and segmenting leads at submission. Attribute-based routing — matching leads to the right rep instantly. Automated first response — personalized message within 60 seconds. Embedded scheduling — lead books on the matched rep's calendar in the form flow. **The CRM receives:** A clean, qualified, already-routed lead record with full data — form responses, qualification data, enrichment data, routing assignment, and meeting details. The record enters the CRM ready for the rep to work, not ready to be processed. **The CRM then does:** Pipeline management, deal tracking, email sequences, internal reporting, forecasting, and everything else it was built for. The integration is a one-way push: Surface → CRM. Lead data flows in, pre-processed and pre-routed. The CRM never has to do the routing or qualification work. It just receives the output. **You don't have to change your CRM.** Surface works with Salesforce, HubSpot CRM, Pipedrive, Zoho, Attio, and more. Your reps keep working in the same CRM they use today. **You don't have to migrate data.** Surface handles new leads going forward. Historical data stays in the CRM untouched. **You don't have to retrain your sales team.** Reps see leads in the CRM the same way they always have — except the leads arrive faster, with better data, and already assigned to the right person. **Your existing CRM workflows still work.** Deal stage automations, task assignments, and email sequences triggered by CRM records continue operating normally. They just receive better inputs. Surface is the layer your CRM needs but doesn't have — the real-time capture, qualification, routing, and response engine that feeds qualified leads into your pipeline. If your CRM is full of leads but your lead-to-meeting rate is low, the CRM isn't the problem. The problem is what happens before the lead gets there. Surface was built to fix that layer without touching anything else. --- # How to A/B Test Your Entire Lead Flow With Code | Surface Labs URL: https://surface.thesurface.network/blog/how-to-a-b-test-your-entire-lead-flow-with-code Your marketing team A/B tests everything — ad copy, landing page headlines, button colors, hero images. They can tell you which shade of blue converts 0.3% better on mobile. But ask them what happens after the form submit and the testing stops completely. Nobody is testing the lead flow itself. Not the form fields. Not the routing logic. Not the response timing. Not the qualification criteria. The part of the funnel where the most money is lost is the part where nobody runs experiments. This isn't because teams don't want to test it. It's because the infrastructure makes it nearly impossible. A/B testing requires three things: the ability to split traffic, the ability to change one variable while holding others constant, and the ability to measure downstream outcomes. Your current lead ops stack makes all three hard. **Splitting is manual.** CRMs don't have native split-testing for routing rules. Zapier doesn't support traffic allocation. To split leads into two groups, you'd need to build custom logic in middleware — and then maintain it, monitor it, and clean it up when the test ends. **Variables are tangled.** Your form tool, your enrichment layer, your routing logic, and your CRM are all separate systems. Changing one variable — say, adding a qualifying question to the form — affects what data the routing engine sees, which changes how leads are assigned, which changes rep behavior. You can't isolate the variable because the systems aren't connected in a way that lets you control the flow. **Measurement stops at the CRM boundary.** You can measure form conversion rate in your form tool. You can measure deal velocity in your CRM. But connecting a specific form variant to a specific downstream outcome — "leads who saw the 4-question form booked meetings 22% faster than leads who saw the 3-question form" — requires stitching data across 3 or 4 platforms. Most teams never do it. The result is that lead ops decisions are made on intuition, not evidence. How many form fields should we use? Should we route by territory or by deal size? Should the first response go out in 30 seconds or 5 minutes? Nobody knows, because nobody tests. Once you have a unified lead ops layer — one system handling capture, qualification, routing, and response — experimentation becomes straightforward. Here's what's worth testing: Test What you change What you measure Typical impact **Form length** 3 fields vs. 5 fields vs. 7 fields Form completion rate AND lead-to-meeting rate Shorter forms get more submissions; longer forms produce better-qualified leads. The net effect varies by audience. **Qualification questions** Which questions you ask at capture — budget, timeline, company size, use case Routing accuracy, rep call time, conversion rate Right questions cut SDR qualification calls by 30–50% **Routing logic** Territory-based vs. deal-size-based vs. product-interest-based Lead-to-conversation rate, time-to-meeting, win rate Matching by product interest often beats territory matching by 15–25% **Response timing** Instant (< 30 sec) vs. fast (< 5 min) vs. standard (< 30 min) Contact rate, conversation rate, meeting booked rate Instant vs. standard typically shows 3–5x difference in contact rate **Response content** Generic confirmation vs. personalized with lead context vs. rep-specific intro Reply rate, meeting booked rate Personalized responses outperform generic by 2–3x on reply rate Every row in that table is a decision your team has already made — probably based on a guess. Testing turns guesses into data. The concept is borrowed from engineering. Feature flags let you deploy multiple versions of a feature and split users between them without redeploying code. The same logic applies to lead ops. **Split at capture.** When a lead submits a form, the system assigns them to a test cohort — A or B. This assignment sticks through the entire flow. The lead doesn't know they're in a test. Neither does the rep. **Change one variable per test.** Cohort A gets the current routing logic. Cohort B gets the variant. Everything else — form, enrichment, response timing — stays identical. This is what makes it a real test instead of a before/after comparison with 15 confounding variables. **Measure at the outcome level.** Don't just measure form completion. Measure lead-to-conversation, conversation-to-meeting, and meeting-to-close — segmented by cohort. The test that reduces form submissions by 10% but increases meeting-booked rate by 30% is a winner, even though the top-of-funnel number went down. **Run to statistical significance.** Most lead ops tests need 200–500 leads per cohort to produce reliable results. At typical B2B volumes, that means running tests for 2–4 weeks. Don't call a test after 3 days and 40 leads. This architecture only works when capture, routing, and response live in the same system. If they're split across Typeform, Zapier, and HubSpot, you can't split cohorts cleanly, you can't isolate variables, and you can't measure outcomes end-to-end. Surface was built as a unified lead ops layer — capture, qualification, routing, and response in one system. That means split testing is native, not bolted on. You can run experiments on any variable in the flow, measure outcomes end-to-end, and make lead ops decisions based on data instead of intuition. If your team is still debating how many form fields to use based on someone's opinion from 2022, that's a testable question. Surface makes it easy to answer. --- # How to Actually Measure Lead Quality (Not Just Lead Volume) | Surface Labs URL: https://surface.thesurface.network/blog/how-to-actually-measure-lead-quality-not-just-lead-volume Your marketing team generated 600 leads last month. That number is in the board deck, the weekly standup, and the campaign report. It looks good. But nobody can tell you how many of those 600 leads resulted in a real sales conversation, how many booked a meeting, or how many turned into pipeline. Lead volume is the easiest metric to report and the least useful one to optimize for. It tells you how many people filled out a form. It tells you nothing about whether those people were worth talking to or whether they actually got talked to. Measuring lead quality requires different metrics, measured at different points in the funnel, connected end-to-end. Here's how to set it up. Volume metrics — total leads, CPL, MQL count — create a dangerous illusion. They make it look like the funnel is working when it might not be. Metric What it tells you What it hides **Total leads** How many people filled out a form Whether any of them were qualified, contacted, or converted **Cost per lead** How much you paid per form submission Whether those submissions turned into meetings or pipeline **MQL count** How many leads hit a scoring threshold Whether the scoring model reflects actual buying behavior or just activity **Form conversion rate** What percentage of visitors completed the form Whether form completions lead to revenue or just inflate the database A team reporting 600 leads at $80 CPL looks efficient. But if only 90 of those leads get a real conversation and 18 book a meeting, the real cost per meeting is $2,667. That's not efficient — it's expensive, and the volume metric disguised it. Quality metrics connect marketing activity to revenue outcomes. They're harder to measure because they require visibility beyond the form submission — but they're the only metrics that tell you whether the funnel is actually working. **Lead-to-conversation rate.** What percentage of captured leads result in a real two-way interaction with a rep? If it's below 50%, you're either generating unqualified leads or losing good leads to slow follow-up and bad routing. This single metric captures both quality and infrastructure problems. **Lead-to-meeting rate.** What percentage of captured leads book a meeting? This is the most honest metric in the funnel. It accounts for lead quality, speed-to-lead, routing accuracy, rep effectiveness, and qualification depth. Top-performing teams hit 25–35%. Most teams are at 8–15%. **Cost per meeting booked.** Total spend divided by meetings booked — not leads generated. This is the number that connects marketing spend to pipeline. It's the metric your CFO would care about if they knew to ask for it. **Source-level conversion rate.** Break lead-to-meeting rate down by source — paid search, paid social, organic, third-party, events. This tells you which channels produce leads that actually convert versus leads that just inflate the count. A channel with a $150 CPL but a 5% lead-to-meeting rate is more expensive per meeting than a channel with $300 CPL and a 25% lead-to-meeting rate. **Qualification accuracy.** Of the leads your system marks as "qualified," what percentage actually book a meeting and progress to pipeline? If your qualification model says 200 leads are sales-ready and only 30 book meetings, the model is wrong — it's pattern-matching on the wrong signals. Most teams can't report these metrics because the data is fragmented across tools. Form data lives in one system. CRM data lives in another. The connection between "this lead came from this campaign" and "this lead booked a meeting 3 days later" requires stitching across platforms. There are two paths: **Path 1: Manual stitching.** Export form data, CRM activity data, and meeting data. Join them in a spreadsheet or BI tool by lead email or ID. Calculate the metrics above by source and by time period. This works but it's labor-intensive and breaks every time someone changes a field name or adds a new source. **Path 2: Unified system.** Use a lead ops layer that tracks the full journey — from capture through conversation through meeting through outcome — in one system. The metrics are calculated automatically because every stage is instrumented. Path 1 is where most teams start. Path 2 is where they should end up. \[IMAGE: Two side-by-side dashboards. Left: "Volume dashboard" showing total leads (600), CPL ($80), MQL count (340) — all green. Right: "Quality dashboard" showing lead-to-meeting rate (12%), cost per meeting ($2,667), qualification accuracy (42%) — all yellow/red. Same data, different story. White background, blue (`#4F6DF5`) accent, flat design.\] When you can report lead quality metrics by source, the conversation with leadership changes completely. Instead of "we generated 600 leads," it becomes "paid search generated 150 leads and 38 meetings at $395/meeting. Paid social generated 200 leads and 12 meetings at $833/meeting. We should shift $10K from social to search next month." That's a resource allocation conversation based on revenue impact, not a vanity metrics conversation based on form submissions. Surface tracks the full journey from capture through meeting booked in one system — which means lead quality metrics are available by default, not through manual stitching. Lead-to-meeting rate, cost per meeting, source-level conversion, and qualification accuracy are all visible in real time. If your team is reporting CPL to the board and hoping nobody asks what happens after that, Surface gives you the metrics that answer the question they'll eventually ask. --- # How to Audit Your Entire Lead Flow End-to-End | Surface Labs URL: https://surface.thesurface.network/blog/how-to-audit-your-entire-lead-flow-end-to-end You probably can't draw your lead flow on a whiteboard right now. Not the idealized version — the actual one. Where leads come from, what data gets captured, how they're enriched, where routing decisions happen, how fast reps get notified, and what the lead experiences from form submit to first human contact. Most teams can't do this because the flow was never designed. It evolved — one tool at a time, one integration at a time, one "quick fix" at a time. The audit exists to make the invisible visible, so you can find where leads are leaking and fix the right things in the right order. This is the framework. Start by listing every way a lead enters your system. Don't guess — check. Pull data from your CRM, form tools, ad platforms, third-party providers, event tools, and any chatbot or live chat system. For each source, document the tool that captures it, what fields are collected, and where the data goes next. Most teams discover 2–3 lead sources they forgot existed — a landing page from a campaign that's still running, an old Typeform that feeds into a different Zapier workflow, or a partner integration that dumps leads into a shared inbox. If leads from different sources have different fields, different formats, or go to different systems, you've found your first problem. Fragmented capture means fragmented data downstream. Pick 10 recent leads — ideally from different sources — and trace their full journey. For each lead, document: **Time of form submission.** When exactly did the lead enter your system? **Time of CRM record creation.** How long between form submit and CRM entry? This reveals sync delays — common with Zapier or webhook-based integrations. **Time of enrichment.** When was third-party data appended? Did it happen before or after routing? If enrichment runs after routing, your routing decisions are being made on incomplete data. **Routing decision.** Which rep was the lead assigned to? Was it the right rep? How long did routing take? **Time of first outreach.** When did the assigned rep actually contact the lead? What was the total elapsed time from form submit? **Outcome.** Did the lead respond? Was a meeting booked? If not, why not? Ten leads is enough to see the patterns. You'll likely find that 3–4 of the 10 experienced a meaningful delay or misroute that you didn't know about. Once you've traced the leads, you'll have data on five critical gaps: Gap What to measure Red flag threshold **Capture → CRM** Time from form submit to CRM record created Over 2 minutes means sync issues **CRM → Routing** Time from record creation to rep assignment Over 5 minutes means routing is manual or batched **Routing → Notification** Time from assignment to rep being alerted Over 1 minute means notification layer is broken or noisy **Notification → First outreach** Time from alert to rep's first email/call Over 30 minutes means the rep isn't acting on notifications promptly **First outreach → Response** Time from outreach to lead reply or meeting booked Low response rates here indicate bad timing, wrong rep, or generic messaging The total of these gaps is your speed-to-lead. But breaking it into components tells you where the problem actually lives. A team with a 4-hour speed-to-lead might have instant capture-to-CRM and instant routing — but a 3.5-hour gap between notification and outreach, meaning the bottleneck is rep behavior, not systems. List every tool involved in moving a lead from capture to first contact. Include form tools, enrichment providers, middleware (Zapier, Make, Tray), CRM, routing logic, notification systems, and scheduling tools. Most teams are running 5–8 tools in the lead flow. Each connection between tools is a potential failure point — a Zapier that stops working, a webhook that times out, a field mapping that breaks when someone updates the CRM schema. The number of tools isn't inherently bad. But every tool-to-tool handoff adds latency, complexity, and fragility. If your audit reveals more than 3 handoffs between form submit and rep notification, that's worth simplifying. After the audit, you'll have a clear picture of where leads leak. Rank the issues by impact: **Fix first:** Anything that adds more than 30 minutes to speed-to-lead. This has the highest ROI because it affects every lead. **Fix second:** Routing mismatches. If more than 10% of leads are going to the wrong rep, fixing routing accuracy will immediately improve conversion. **Fix third:** Data gaps at capture. If reps are spending the first 5 minutes of every call asking qualifying questions, move those questions to the form. **Fix fourth:** Tool consolidation. Reducing handoffs reduces failure points and makes the system easier to maintain and modify. Surface eliminates most of the gaps this audit reveals by handling capture, qualification, routing, and response in one system. No middleware, no sync delays, no multi-tool handoffs. If your audit reveals a complicated flow with multiple tools and handoff gaps, Surface was built to replace that complexity with one connected layer. Run the audit first — then you'll know exactly what needs to change. --- # How to Automatically Hand Off Leads From Marketing to Sales | Surface Labs URL: https://surface.thesurface.network/blog/how-to-automatically-hand-off-leads-from-marketing-to-sales The marketing-to-sales handoff is where more leads die than anywhere else in the funnel. Marketing generates the lead, gets credit for the MQL, and considers their job done. Sales receives the lead — sometimes hours or days later — with incomplete data, no context, and no idea why this person is worth calling. The lead, meanwhile, has been sitting in silence since they filled out the form. The handoff isn't a moment. It's a gap. And the size of that gap directly determines how many of your marketing-generated leads turn into pipeline. The handoff fails for structural reasons, not because marketing and sales don't get along. **Different systems.** Marketing works in the MAP (HubSpot Marketing, Marketo, Pardot). Sales works in the CRM (Salesforce, HubSpot CRM). The handoff requires data to move from one system to the other — through sync rules, workflows, or middleware — and every transfer point adds latency and loses context. **Different definitions.** Marketing defines "qualified" based on lead scoring — page visits, email opens, content downloads. Sales defines "qualified" based on buying signals — budget, timeline, authority, need. A lead that scores high in the MAP might be completely unqualified by sales standards, and neither team finds out until the rep calls. **Different timelines.** Marketing operates on campaigns — weekly cadences, monthly reports, quarterly planning. Sales operates on deals — immediate follow-up, same-day response, real-time pipeline. The lead enters marketing's timeline (batch processing) and needs to exit on sales' timeline (instant action). The gap between these timelines is where speed-to-lead goes to die. \[IMAGE: A simple gap diagram — left side labeled "Marketing" with icons for MAP, scoring, campaigns. Right side labeled "Sales" with icons for CRM, pipeline, calls. A visible gap between them labeled "The handoff gap: avg 2–8 hours, 30–40% lead loss." White background, blue (`#4F6DF5`) accent, flat design.\] The automated handoff eliminates the gap by making three things happen simultaneously at the moment of capture — not sequentially after the fact. **Qualification happens at capture, not in the MAP.** Instead of scoring leads based on behavioral signals over days or weeks, qualifying questions are asked on the form. Budget, timeline, company size, and use case data are captured upfront. The lead is qualified the moment they submit — no waiting for a score to accumulate. **Routing happens at capture, not in the CRM.** The lead is matched to the right rep based on form responses and enrichment data — territory, deal size, product interest, availability — before the CRM record is even created. The CRM receives a lead that's already assigned, not a lead that needs to be processed. **Response happens at capture, not after notification.** The lead gets a personalized message within 60 seconds — the assigned rep's name, a reference to what they asked about, and a scheduling link. The rep gets a notification with full context. The lead never enters a "waiting" state. The CRM still gets the record. Marketing still gets attribution data. But the handoff — the actual transfer of a live prospect from "marketing generated" to "sales engaged" — happens in seconds instead of hours. For the handoff to work automatically, five things must be true: **Every lead carries qualification data.** Not just name and email — budget range, timeline, company size, and use case. If the rep has to call to get this information, the handoff is incomplete. **Routing rules reflect the real sales structure.** Territory, product specialization, deal size tiers, and rep availability. If leads are round-robined to whoever's next, the handoff is technically automated but practically broken. **The lead is contacted within 60 seconds.** Automated first response — personalized, contextual, with a clear next step. If the first contact is a rep manually deciding to call when they see a notification, the handoff has a human bottleneck. **The rep receives full context.** When the rep picks up the lead, they should see: form responses, qualifying data, enrichment data, pages viewed, lead source, and campaign attribution. If they have to look this up manually, the handoff is incomplete. **Both teams see the same data.** Marketing should be able to see whether their leads were contacted, how fast, and what happened. Sales should be able to see where the lead came from, what they engaged with, and how they were qualified. Shared visibility eliminates the blame game. The most immediate change is speed — leads go from multi-hour handoffs to sub-60-second handoffs. But the bigger change is trust. When sales gets leads that are pre-qualified, correctly routed, and already contacted with a personalized message, they stop treating inbound as unreliable and start treating it as their best pipeline source. That behavioral shift — sales actually prioritizing inbound leads — is worth more than any individual process improvement. And it only happens when the handoff consistently delivers quality. Surface eliminates the handoff gap by handling qualification, routing, and response at the moment of capture — before the CRM is involved. The lead moves from marketing-generated to sales-engaged in seconds, with full context and correct assignment. If your marketing team is generating leads and your sales team says they never see them — or sees them too late with too little context — the handoff is the problem. Surface was built to automate it completely. --- # How to Automatically Sort Leads Into Smart Groups | Surface Labs URL: https://surface.thesurface.network/blog/how-to-automatically-sort-leads-into-smart-groups Your CRM has one big bucket of leads. Some are enterprise prospects with $200K deal potential. Some are freelancers who want your free tier. Some are agencies evaluating you for their clients. Some are spam. They all sit in the same list, get the same routing logic, and compete for the same rep attention. Smart grouping — automatically segmenting leads into distinct categories based on their attributes and behavior — is the difference between treating every lead the same and treating every lead appropriately. The grouping determines the routing, the response, the urgency, and ultimately the conversion rate. Most teams start with manual segmentation. An SDR reviews each lead, checks the company size, looks at the form responses, and decides: enterprise, mid-market, SMB, or disqualified. This works when you're getting 50 leads a month. At 200+ leads a month, it becomes a full-time job that adds hours of delay to every lead. The delay is the real cost. While the SDR is reviewing and categorizing, the lead is waiting. A lead that should have been routed to an enterprise AE immediately instead sits in a queue for 2 hours while someone decides which bucket it belongs in. The grouping variables depend on your sales structure, but most B2B companies need 3–5 of these: Variable How to capture it What it determines **Company size** Form field (employee count or revenue range) + enrichment Segment tier — enterprise, mid-market, SMB. Determines which team or rep handles the lead. **Industry / vertical** Form field or enrichment Routing to vertical-specific reps. Messaging and follow-up content. **Use case / product interest** Form field (dropdown or multi-select) Which product team or specialist handles the lead. **Budget range** Form field Deal size tier. Determines urgency and seniority of assigned rep. **Intent level** Combination of form type + behavioral signals Urgency of response. Demo requests get instant routing. Content downloads get nurture. **Geography** IP-based detection or form field Territory assignment. Time zone-appropriate response. The key is capturing these variables at the point of form submission — not after the fact. If the form collects name, email, and company only, you can't group until enrichment runs (adding latency) or an SDR manually reviews (adding hours). \[IMAGE: A diagram showing a single form submission splitting into four groups based on captured attributes: "Enterprise — AE team (instant)," "Mid-market — SDR team (< 5 min)," "SMB — self-serve flow (automated)," "Unqualified — nurture (automated)." Clean, minimal, white background, blue (`#4F6DF5`) accent, flat design.\] **Step 1: Define your groups.** Most companies need 3–5 distinct groups. Common setups: Enterprise / Mid-market / SMB / Unqualified. Or: Product A / Product B / Services / Not a fit. The groups should map directly to how your sales team is organized. **Step 2: Define the rules.** Each group gets a set of criteria. Example: "Enterprise = 500+ employees AND budget > $50K AND timeline < 6 months." Rules should use AND/OR logic and be evaluated in priority order — check enterprise criteria first, then mid-market, then SMB, with a catch-all for anything that doesn't match. **Step 3: Capture the inputs at the form level.** Your forms need to collect the data that feeds the rules. If company size determines the group, the form needs a company size question. If budget determines urgency, the form needs a budget range question. No inputs, no grouping. **Step 4: Connect grouping to routing and response.** Grouping without action is just a label. Each group should trigger a different routing rule (enterprise leads to senior AEs, SMB leads to a self-serve flow) and a different response (enterprise gets a personalized message within 30 seconds, SMB gets an automated onboarding email). **Step 5: Review and refine monthly.** Pull conversion data by group. If your "enterprise" group converts at 40% but your "mid-market" group converts at 8%, either the mid-market criteria are too loose or the mid-market routing/response needs improvement. Use the data to tighten the rules. More groups isn't better. Every group needs its own routing rule, response template, and follow-up sequence. If you create 12 groups, you need to maintain 12 distinct workflows. Most teams with fewer than 20 reps should have 3–5 groups maximum. Start with the minimum groups that reflect meaningful differences in how leads should be handled. You can always add granularity later — but starting with too many groups creates maintenance overhead that nobody keeps up with. Surface handles automatic grouping at the point of capture — form responses and enrichment data are evaluated in real time against your rules, and each lead is segmented, routed, and responded to based on its group before a human is involved. If your SDRs are spending the first hour of every day manually sorting leads into categories, that's time Surface can eliminate entirely. Grouping should be instant, automatic, and connected to routing — not a manual step that adds delay. --- # How to Build a Lead Operations System From Scratch | Surface Labs URL: https://surface.thesurface.network/blog/how-to-build-a-lead-operations-system-from-scratch Most companies don't build a lead operations system. They accumulate one. A form tool here, a Zapier connection there, a routing rule someone set up 18 months ago that nobody fully understands. By the time you have 10+ lead sources and 8+ reps, the duct tape is holding together a system that nobody designed intentionally. If you're starting from scratch — or if your current setup has gotten painful enough that you need to rebuild — here's the architecture that actually works. Lead ops covers four jobs. Most teams have tools for one or two of them and gaps in the rest. Job What it does What most teams use Where it breaks **Capture** Collects lead data from every source — forms, ads, third-party providers, events HubSpot Forms, Typeform, native CMS forms Different tools per source. Inconsistent fields. No qualification at capture. **Qualification** Determines if the lead is worth pursuing and how urgently Manual SDR review or basic lead scoring Happens too late (on the call instead of at the form), or uses vanity signals instead of real intent **Routing** Matches the lead to the right rep based on relevant attributes CRM round-robin or manual assignment Doesn't account for territory, deal size, product interest, or rep availability **Response** Contacts the lead with the right message at the right speed Rep gets a CRM notification and acts when they see it Slow, generic, and disconnected from routing and qualification data A real lead ops system connects all four. The lead is captured, qualified, routed, and responded to in one continuous flow — not four disconnected steps with handoff gaps between them. Before you build anything, list every way a lead enters your system. Website forms, paid ad landing pages, third-party lead providers (G2, Capterra, etc.), event registrations, chatbot conversations, partner referrals. Most teams have 5–15 distinct sources. Every source should flow through the same capture layer with the same core fields. That doesn't mean every form looks identical — a demo request form and a whitepaper download form ask different questions. But the data schema should be consistent: every lead, regardless of source, should arrive in your system with the same base fields (name, email, company) plus qualifying data where applicable. If different sources use different tools with different field names, you'll spend forever normalizing data downstream. Standardize at the point of capture. The most expensive place to qualify a lead is on a phone call with an SDR. The cheapest place is on the form itself. Add 2–4 qualifying questions to your high-intent forms (demo requests, contact forms, pricing inquiries): company size, budget range, timeline, and use case. Use conditional logic — if they select "just researching," route to nurture. If they select "evaluating now, budget approved," route to a senior AE immediately. Low-intent captures (blog subscriptions, content downloads) don't need full qualification. But they should still capture enough data to segment — at minimum, company size and role. \[IMAGE: A simple flowchart showing a form submission branching into three paths based on qualification answers: "High intent → Senior AE (instant)," "Medium intent → SDR (same day)," "Low intent → Nurture sequence (automated)." Clean, minimal, white background, blue (`#4F6DF5`) accent, flat design.\] Your routing logic should reflect how your sales team actually works, not how your CRM's default assignment feature works. Start by defining the variables that determine which rep should get which lead: territory/geography, deal size tier, product or service line, industry vertical, rep availability and current capacity. Most teams need 2–3 of these. Complex sales orgs need all five. Then build rules in priority order. Territory first, then deal size, then product interest, with availability as a tiebreaker. If no rule matches, the lead goes to a default queue with an SLA — not into a black hole. Test your routing by running your last 100 leads through the new logic on paper before you deploy. If more than 5% would end up in the wrong place, refine the rules. The first message a lead receives should happen within 60 seconds of form submission and should include three things: acknowledgment of what they asked about, the name of the person who will help them, and a clear next step (scheduling link or expectation of when they'll hear back). This message should be automated — triggered by the routing decision, not by a human noticing a notification. The rep follows up after the automated response, but the lead never sits in silence wondering if anyone received their request. The final piece is visibility. You need to track four metrics continuously: speed-to-lead (form submit to first outreach), routing accuracy (percentage of leads that go to the correct rep without reassignment), lead-to-meeting rate (percentage of captured leads that result in a booked meeting), and cost per meeting booked (total spend divided by meetings, not leads). If you can see these four numbers in real time, you can diagnose and fix problems before they compound. If you can't, you're flying blind. Surface was built to be the lead ops system — capture, qualification, routing, and response in one connected layer. If you're building from scratch or rebuilding from duct tape, Surface handles the architecture described in this post out of the box. If your current system requires 4+ tools and a Zapier flowchart to move a lead from form to rep, you don't have a system. You have a workaround. Surface was built to replace it. --- # How to Build a Lead Scoring Model That Actually Predicts Conversion | Surface Labs URL: https://surface.thesurface.network/blog/how-to-build-a-lead-scoring-model-that-actually-predicts-conversion Most lead scoring models don't work. Not in a "they could be better" way — in a "the scores have zero correlation with actual conversion" way. Teams spend months building scoring models in HubSpot or Marketo, assigning points for email opens and page visits, and defining an MQL threshold that triggers a handoff to sales. Then nobody checks whether the MQLs actually convert at a higher rate than non-MQLs. When someone finally does that analysis, the result is usually uncomfortable: MQLs convert at 14% and non-MQLs convert at 11%. The scoring model added 3 months of work and infrastructure for a 3-percentage-point lift that might be within the margin of error. Here's how to build a model that actually predicts who will convert — and more importantly, who should get a fast response. Traditional lead scoring assigns points for behavioral signals — email opens, page visits, content downloads, webinar attendance. The assumption is that more engagement equals more buying intent. The problem is that engagement and intent are weakly correlated in B2B. A marketing coordinator who opens every email and downloads every whitepaper scores higher than a VP who visits the pricing page once. The coordinator gets flagged as an MQL. The VP doesn't. Sales calls the coordinator and gets nowhere. The VP talks to a competitor who responded faster. Behavioral scoring measures attention, not intent. And attention is cheap — especially when much of it is automated (email opens inflated by email clients) or habitual (people who consume content but never buy). Signal Predictive value Why **Stated timeline** Highest "Evaluating this quarter" vs. "sometime next year" is the single most predictive data point. Leads with an active timeline convert at 5–10x the rate of leads who are just exploring. **Company fit (size, industry, revenue)** High Does this company match your ICP? A perfect-fit company with minimal engagement is more likely to convert than a poor-fit company with high engagement. **Budget acknowledgment** High A lead who selects a budget range that matches your pricing has removed the #1 objection before the first conversation. **Pricing page visits** High The pricing page is the strongest single behavioral signal on most B2B sites. It indicates active cost evaluation. **Return visits** Medium-high Visiting the site 3+ times in a week indicates ongoing evaluation. More predictive than total page views. **Form type** Medium-high Demo requests convert at 3–5x the rate of content downloads. The form itself is a signal. **Job title / seniority** Medium Decision-makers convert at higher rates than researchers. But title alone isn't predictive — it's predictive in combination with other signals. **Email opens / content downloads** Low Weakly correlated with conversion. Too noisy to be useful as primary scoring inputs. The top three signals — timeline, company fit, and budget — are all data points you can capture on a form. They don't require weeks of behavioral tracking. They're available at the moment of capture. **Layer 1: Fit score (firmographic).** Does this lead match your ICP? Evaluate company size, industry, revenue, and geography against your ideal customer profile. This is a binary or tiered score: strong fit, moderate fit, poor fit. Data comes from form fields + enrichment. **Layer 2: Intent score (stated + behavioral).** What is this lead's buying intent right now? Evaluate stated timeline, budget acknowledgment, form type, pricing page visits, and return visit frequency. This is the urgency dimension — not just "are they a good fit?" but "are they ready now?" **Layer 3: Combined score and routing trigger.** Combine fit and intent into a matrix: High intent Medium intent Low intent **Strong fit** Route to senior AE immediately Route to SDR same-day Nurture — high-value, not ready **Moderate fit** Route to SDR immediately Nurture — build relationship Low priority nurture **Poor fit** Evaluate manually — might be a new segment Nurture — low investment Auto-disqualify This matrix replaces the single MQL threshold with a two-dimensional routing decision. "Strong fit + high intent" gets an instant response. "Moderate fit + low intent" gets automated nurture. The scoring model doesn't just score — it decides what happens next. The model is only useful if it predicts real conversion. After 30 days of running it, pull the data: **For each cell in the matrix, what's the lead-to-meeting rate?** If "strong fit + high intent" leads convert at 45% and "strong fit + medium intent" leads convert at 20%, the model is working — it's differentiating meaningfully. **If two cells have similar conversion rates, merge them.** The model should create groups with meaningfully different outcomes. If medium and low intent convert at the same rate, your intent signals aren't discriminating well — refine the inputs. **If the model doesn't predict, simplify.** A complex model that doesn't predict conversion is worse than a simple one that does. Start with fit + timeline only. Add signals when you have enough data to validate them. Surface builds scoring into the capture flow — fit score from form data + enrichment, intent score from stated timeline + behavioral signals, combined into a routing decision that triggers instantly. No batch processing, no scoring that runs overnight, no MQL threshold that someone set 18 months ago. If your current scoring model can't demonstrate a meaningful conversion difference between high-scoring and low-scoring leads, the model isn't working. Surface was built to replace it with one that scores at capture and routes on the result. --- # How to Build a Machine That Brings In Leads on Autopilot | Surface Labs URL: https://surface.thesurface.network/blog/how-to-build-a-machine-that-brings-in-leads-on-autopilot Most B2B teams don't have a lead generation machine. They have a collection of disconnected tools duct-taped together with Zapier and hope. A form tool here. An enrichment tool there. CRM workflows that somebody built a year ago and nobody's touched since. A scheduling tool that lives on a separate page. A Slack notification that fires sometimes. Every lead that comes in has to survive a gauntlet of handoffs between these tools. Some make it through. A lot don't. And nobody knows exactly where the leaks are because the system is too fragmented to measure. A real lead machine doesn't have leaks. It captures, qualifies, enriches, routes, and books meetings — without anyone touching it. The output is booked meetings on the right rep's calendar. The input is traffic. Everything in between is automated. It's not complicated. There are five components. Most teams have some of them. Almost nobody has all five working together. **Capture.** A form that collects the right information without killing your completion rate. Conditional logic so different prospects see different questions. Short enough that people finish it. Smart enough that you get usable data. **Enrichment.** The moment someone enters their email, their company data gets appended automatically. Employee count, industry, revenue, tech stack, location. This replaces the 10–15 minutes a rep would spend researching the lead manually. It also gives your routing and scoring logic real data to work with — instead of whatever the prospect felt like typing into a dropdown. **Qualification.** Every lead gets evaluated against your ICP in real time. Qualified, disqualified, or needs review. Not a point system that went stale three months ago. A clear decision your team can act on without debating. **Routing.** Qualified leads go to the right rep based on who they are. Company size, region, industry, use case. The routing decision happens during the form — not in a CRM workflow 10 minutes later. **Scheduling.** The right calendar appears inside the form. The prospect books a meeting before they leave the page. No follow-up email. No booking link. No waiting. When all five work together, the machine runs itself. Traffic comes in, meetings come out. Reps open their calendar and every meeting is with a qualified prospect in their segment. Marketing points at a dashboard that shows exactly how many qualified leads turned into meetings. They're a pipeline with holes. What's broken What happens Form only collects name and email Every lead goes to sales unfiltered. No data to qualify on. Enrichment runs in batches hours later Reps spend 15 minutes researching each lead before they can act. No scoring or qualification Reps guess which leads are worth calling. They guess wrong a lot. Round robin routing Enterprise leads end up with SMB reps. Territory doesn't matter. Scheduling lives in a follow-up email Prospect has to come back a day later to book. Most don't. Each of these individually is a small problem. Together they compound into a conversion rate that's a fraction of what it should be. The fix isn't adding another tool. It's consolidating the whole flow into one system where each step feeds the next. Surface is built as a single system that handles all five components. Not five tools integrated together. One platform. The form builder uses conditional logic and production-ready templates. Enrichment runs in real time the moment someone types their email. AI scoring evaluates every lead against your ICP automatically. Routing rules use form data and enrichment data together to determine who should handle the lead. And the right calendar embeds inside the form so the prospect books on the spot. Drop-off capture means even the leads who don't finish the form get saved and routed into follow-up workflows. Partial submissions trigger separate automations so warm leads don't disappear. Everything syncs to your CRM — HubSpot, Salesforce, whatever you're running. The lead record arrives already enriched, scored, and assigned. The rep's first interaction is the meeting itself. Map your current flow from traffic to booked meeting. Every step. Every tool. Every handoff. Then ask: where does a lead have to wait for something to happen? Where does a human have to do something that could be automated? Where is data missing that should be there? Those gaps are where your leads are leaking. Close them and you have a machine. Surface Labs was built to be that machine. If your current setup requires more than two tools to get from form fill to meeting booked, it's worth a look. --- # How to Build a Patient Intake System That Doesn't Make People Wait on Hold | Surface Labs URL: https://surface.thesurface.network/blog/how-to-build-a-patient-intake-system-that-doesn-t-make-people-wait-on-hold The average patient calling a healthcare practice waits 8–12 minutes on hold. One in three hangs up before reaching a human. Of those who hang up, most don't call back — they book with the practice that had online scheduling. Healthcare practices are losing patients at the front desk. Not because the providers aren't good, but because the intake experience is stuck in 2010 — phone calls, hold music, and paper forms. The fix isn't hiring more front desk staff. It's building an intake system that handles the repeatable parts of patient intake digitally — so the phone is reserved for the conversations that actually need a human. Patients don't want to call. Studies consistently show that 60–70% of patients prefer to book appointments online. They want to: see available times, select a provider, answer intake questions, verify insurance compatibility, and confirm the appointment — all without picking up a phone. The practices that offer this gain a structural advantage: they capture patients that phone-only practices lose, they reduce front desk burden, and they collect better intake data (because digital forms are consistent — phone intake depends on whoever answers). ### Step 1: New vs. returning patient The first question on the intake form: "Are you a new patient or returning patient?" Returning patients need a shorter path: verify identity → select their existing provider → book an appointment. No intake questions, no insurance verification, no redundant data collection. They've already done all that. New patients need the full flow: screening questions, insurance verification, provider matching, and scheduling. Separating these paths immediately reduces friction for your existing patients (who represent the majority of appointments) while giving new patients the thorough onboarding they need. ### Step 2: Conditional symptom screening The form asks what type of care the patient needs: primary care, specialist referral, mental health, urgent care, wellness/preventive. Each selection triggers relevant screening questions. For mental health, the screening might include: type of support sought (therapy, psychiatry, both), primary concern (from a dropdown: anxiety, depression, relationship, grief, trauma, other), previous treatment history, and insurance or self-pay preference. This pre-screening gives the matched provider enough context to prepare for the first session — and it identifies whether the patient needs therapy, psychiatry, or both before the appointment is booked. For urgent care, the screening prioritizes triage: symptoms, onset, severity (1–10 scale). High-severity responses can trigger an immediate message: "Based on your symptoms, we recommend visiting the emergency room. If this is not an emergency, we have same-day availability at \[time\]." ### Step 3: Insurance verification at intake The number one cause of appointment friction: insurance mismatch. The patient books, shows up, and discovers the practice doesn't accept their plan. Wasted time for everyone. The form captures: insurance carrier (dropdown of major carriers), plan type, and member ID. The system checks this against the practice's accepted insurance list in real time. **If accepted:** The form continues to scheduling. The patient sees: "Great — we accept \[carrier\]. Let's find you a time." **If not accepted:** The form branches: "We don't currently accept \[carrier\]. You have two options: self-pay (our rates are X–X– X–Y per visit) or we can help you find an in-network provider." This saves the patient a wasted trip and the practice a wasted appointment slot — and it's a better experience than discovering the mismatch at the front desk. ### Step 4: Provider matching New patients are matched based on: specialty (from the screening), accepted insurance (verified in step 3), availability (real-time calendar), location (for multi-location practices), and patient preferences (provider gender, language, specific provider requests if any). The matching happens instantly. The patient sees available providers who meet all their criteria — not a full provider directory they have to filter themselves. ### Step 5: Automated pre-visit workflow After booking, the system triggers: **Immediately:** Confirmation email/text with appointment details, provider name, office location, and cancellation/reschedule link. **24 hours before:** Reminder with prep instructions specific to the visit type. Fasting for bloodwork. Bring medication list for primary care. Complete the PHQ-9 for mental health intake. **1 hour before:** Final reminder with parking/check-in instructions. **Post-visit (24 hours after):** Satisfaction survey + follow-up care reminders. This automation reduces no-shows (practices report 30–50% reduction in no-shows with automated reminders) and improves the patient experience without adding front desk workload. Task Before (phone-based) After (digital intake) Average intake call duration 8–15 minutes 0 (handled digitally) Calls per day for scheduling 40–60 15–25 (only complex cases) Insurance mismatch rate 8–12% of appointments Under 2% No-show rate 15–25% 8–12% Front desk hours on intake/scheduling 20–30 hours/week 8–12 hours/week The front desk doesn't disappear. It shifts from data entry and phone tag to handling complex patient needs, managing provider schedules, and improving the in-office experience. The digital system handles the 60–70% of intake that's repeatable and routine. Surface powers the full patient intake flow: new/returning branching, conditional symptom screening, real-time insurance verification, provider matching, instant scheduling, and automated pre-visit workflows. Connected to your practice management system so patient records are created with full intake data — no manual entry at the front desk. If your front desk spends more time on hold with patients than caring for the ones in the office, Surface fixes the ratio. --- # How to Build a Product People Want to Show Other People | Surface Labs URL: https://surface.thesurface.network/blog/how-to-build-a-product-people-want-to-show-other-people When a customer receives a surprisingly good result from a product, they take a screenshot, send it to a colleague, and explain what happened in Slack. Someone asks which tool created it. Another person requests access. By the end of the week, the product has entered three conversations the marketing team did not initiate, pay for, or observe directly. This is the distribution advantage marketers tend to overlook when separating product from brand. A useful product solves a problem. A showable product also gives the customer something worth carrying into the world: a result, an identity, a ritual, an image, a story, or an artifact that becomes easier to share than to explain. Consumer companies understand this instinctively. Packaging appears in photographs. Products become accessories. Unboxing becomes content. People display the object on desks, kitchen counters, bathroom shelves, gym bags, and social feeds because the item communicates something beyond its functional use. B2B products create social objects too. They produce reports, dashboards, benchmarks, assessments, certifications, visualizations, workflows, and results that customers can show to a manager, team, client, board, or professional community. The product does not need to become viral in the consumer-internet sense. It needs to create moments people feel motivated to repeat. The boundary between product and marketing has always been porous. A beautiful object appears in a photograph. A useful template gets forwarded to a colleague. A customer wears branded merchandise because it signals membership. A product-generated report enters a quarterly meeting and becomes the company’s most persuasive sales asset. Current consumer-brand trends make this relationship unusually visible. Recent _Vogue Business_ reporting described food, beverage, and wellness companies borrowing the visual language of fashion and beauty. Products such as premium water, protein snacks, and herbal teas are being designed as lifestyle objects that look appropriate in a creator’s feed or a carefully composed photograph. Founders interviewed for the article emphasized that product, packaging, imagery, retail, partnerships, and campaigns should feel as though they belong to the same world. The packaging does not merely contain the product. It becomes a distribution surface. McKinsey has separately identified “emotion-first products” as an emerging business model in which anticipation, identity, affinity, and community are designed into the commercial proposition from the beginning. Emotion becomes part of the economic system rather than a benefit marketing tries to add after the product is finished. That idea applies far beyond consumer goods. A B2B company may never produce a photogenic bottle. It can still build a product experience that gives users a result they want other people to see. A shareable moment cannot be sustained through decoration alone. A visually distinctive product may earn an initial post. A surprising campaign may generate curiosity. Customers continue sharing when the product gives them something meaningful: a better result, an easier routine, a useful insight, a sense of progress, or a way to express who they are. The recent interest in design-led consumer products carries an important caveat. Aesthetic packaging can increase desire, but the product still has to justify repeat use. The wellness and supplement categories are increasingly crowded with visually sophisticated brands, while consumers are also asking harder questions about efficacy, convenience, scientific support, and actual product performance. Marketing teams should therefore begin with the truth the product can reliably create. For Surface, that truth might be the moment a marketing or sales team sees the complete history behind a lead rather than receiving a form submission without context. A rep who can see which articles, case studies, integrations, and pricing pages a buyer reviewed receives something immediately useful and demonstrable. The [full lead journey](https://withsurface.com/blog/lead-user-journey) is both a capability and an artifact. It gives the user information they can bring into a sales conversation, team review, or performance report. The product creates something that is easier to show than a generic claim about “better marketing intelligence.” Products become showable in several different ways. Companies should decide which type fits the customer and use case rather than forcing every product into a social-media loop. ### The result Customers share an outcome they are proud of. This may be revenue growth, time saved, an improved conversion rate, a finished design, a solved technical problem, a cleaner forecast, or a personal transformation. The product gives the customer a before-and-after story. Results travel when they are specific, credible, and easy to communicate. A statement such as “we improved efficiency” contains little social value. A report showing that a team reduced lead-response time from four hours to forty seconds gives the customer a concrete achievement to present. ### The artifact The product produces something that can leave the interface. Examples include a benchmark report, visual analysis, certificate, scorecard, strategy map, generated image, presentation, project plan, audit, or customer-facing deliverable. The artifact should preserve enough product identity to create attribution without becoming an advertisement. A useful report that subtly identifies the system which produced it can travel naturally. A report covered in promotional banners makes the customer feel as though they are distributing company collateral. ### The ritual The product becomes part of a repeated behavior. Morning fitness summaries, annual listening reports, weekly team scorecards, project retrospectives, and monthly business reviews all create recurring opportunities for customers to discuss the product. Rituals help brands accumulate meaning. A one-time campaign asks people to remember. A repeated product behavior gives them another reason to encounter and use the brand. ### The identity signal The product communicates something about the user. A person may share a tool because it makes them appear informed, creative, efficient, discerning, technically capable, environmentally conscious, or part of a particular community. Identity can be subtle. A developer sharing an elegant technical workflow signals expertise. A marketing leader distributing a clear attribution framework signals operational sophistication. The product helps the customer tell a story about themselves. ### The discovery The product reveals something the customer did not know. Unexpected insights are naturally conversational. A user shares the finding because it changes an assumption, exposes an opportunity, or gives the team language for a problem it had previously struggled to describe. Products with analytics, research, classification, or recommendation features are especially capable of creating discovery moments. The interface should make the insight clear enough that users can understand and explain it without reconstructing the analysis manually. The strongest consumer examples show how utility, design, ritual, and community reinforce each other. Vaseline offers an unusual case because its core product is more than 150 years old. Unilever CMO Leandro Barreto recently described how creators and customers have expanded the cultural life of the product by demonstrating unconventional uses, including applying it to dog noses or using it inside shoes. The company gained relevance by observing and embracing how communities were reinterpreting a familiar object. The marketing did not invent every use from headquarters. Customers created material around the product because its flexibility invited experimentation. This suggests a different approach to product-led marketing. The company does not need to control every interpretation. It needs to provide enough product integrity, recognizability, and openness for customers to discover uses worth discussing. Marketing teams can then document, organize, validate, and amplify the most useful behavior. Customer creativity becomes research as well as distribution. B2B teams often misunderstand product virality by copying visible consumer mechanics. They add badges, celebration animations, social-sharing buttons, points, leaderboards, and decorative summaries without asking whether the customer gains anything by sharing them. The mechanism exists. The motivation does not. A professional user usually shares a product output because it helps them perform their role. They may want to: - Demonstrate progress to a manager - Explain a decision to another department - Give a client a useful deliverable - Build consensus around a strategy - Prove that an investment worked - Warn the team about a risk - Establish personal credibility - Teach colleagues a better process - Compare performance against a benchmark - Request additional budget or support The showable B2B product should make one of those jobs easier. A marketing dashboard becomes shareable when it clearly explains what changed and what the team should do next. A security report becomes shareable when it helps an executive understand risk. A lead-operations product becomes shareable when sales can see why a prospect was prioritized and what the buyer researched before converting. Surface’s broader [content marketing operating model](https://withsurface.com/blog/content-marketing-guide-2026) separates visibility, trust, conversion, distribution, and measurement. Product-generated artifacts can connect all five. They provide useful material, demonstrate the company’s method, travel between people, and create a path toward commercial action. The shareable moment usually occurs at a boundary. A user finishes a task and needs approval. A marketer discovers a trend and needs to inform leadership. A sales representative receives a lead and needs to prepare for outreach. A customer completes an assessment and needs to discuss the result. Products should identify these boundaries and make the handoff easier. Ask: - What has the user just accomplished? - Who needs to see the result next? - What context will that person require? - Which format makes the information easiest to understand? - What portion can be shared safely? - How should the recipient return to the product? - What product or brand identity should remain attached? The answers may lead to exportable reports, collaborative links, presentations, email summaries, CRM records, annotated screenshots, public profiles, embeddable modules, or client-ready PDFs. A “share” button is the final interface element. The product strategy begins with understanding why the user would press it. Showable products create clear stories. The customer should be able to point to the output and say: - Here is what changed. - Here is what the product discovered. - Here is why the result matters. - Here is what we should do next. Dense interfaces may contain important detail, but the first layer needs a legible conclusion. Surface’s [storytelling work](https://withsurface.com/blog/the-storyteller-role-in-marketing-kpis-craft-and-brand-strategy) applies inside the product as much as it applies to campaigns. Hierarchy, tension, evidence, sequence, and explanation determine whether a user can turn data into a story. This is especially important for AI-generated results. A product that produces an answer without visible reasoning, sources, caveats, or next steps may create temporary surprise. A product that helps the user understand and defend the result creates an artifact they can use with confidence. Companies often overbrand the shareable output. They place a giant logo above a small customer result. They force recipients through an acquisition form. They require public posting. They make the user’s achievement feel like an advertisement for the vendor. The better question is who should look impressive. In most cases, the customer should. The report should help the customer appear informed. The visualization should help them communicate clearly. The assessment should help them lead a better conversation. The benchmark should give them useful context. Product attribution can remain visible without consuming the artifact. This approach creates a healthier exchange. The customer receives professional or personal value. The company receives distribution and association with the value created. Showability becomes more powerful when the product, brand, content, and campaigns feel connected. The recent design-led CPG trend is useful because those companies are building coherent worlds. The product, packaging, photography, retail environment, creator partnerships, and storytelling share a recognizable logic. B2B companies can create the same coherence without copying consumer aesthetics. A product-generated report can use the same terminology as the company’s research. A dashboard can reflect the hierarchy used in sales conversations. A customer assessment can connect to educational content. A benchmark can become an annual editorial asset. A product insight can become the starting point for an executive discussion or customer story. The product then participates in the brand instead of sitting behind the marketing layer as a separate visual and linguistic system. Teams using [AI without losing their brand voice](https://withsurface.com/blog/ai-content-strategy-brand-voice) should apply the same discipline to generated product outputs. Default AI language can make every insight sound as though it came from the same anonymous consultant. Product voice should remain clear, useful, and recognizable. Product-led brand effects can be measured, although the evidence will be distributed. Useful signals include: - Export and share rates - Collaborative invitations - Public links created - Screenshots or product images mentioned online - Referral traffic from shared artifacts - New users entering through collaboration - Repeat use of reports and assessments - Customer references during sales conversations - Branded search following major product moments - Template or artifact reuse - Creator and community adoption - Lead quality from shared-product journeys - Retention among users who share or collaborate Teams should also review the qualitative evidence. Why did someone share? Who received it? What did the artifact help the user accomplish? Which part of the product did the recipient remember? [Lead journey tracking](https://withsurface.com/blog/lead-user-journey) can reveal what happens when a recipient enters the owned experience. The company can see whether shared-product visitors inspect use cases, read comparisons, view pricing, and eventually convert. The objective is not to claim that every share caused revenue. It is to understand whether the product is creating its own useful paths into the market. Bring together product, marketing, customer success, design, and sales. Choose one high-value customer workflow and answer the following questions. ### What does the customer accomplish? Describe the outcome in the customer’s language rather than the product’s feature vocabulary. ### Who needs to see it? Identify the colleague, manager, client, community, or external stakeholder who benefits from the result. Define the professional, emotional, or social value the customer receives. ### What should travel? Choose the result, evidence, context, and next action the recipient needs. ### What should remain attached? Preserve appropriate product identity, source information, methodology, and a route back into the experience. ### What could create discomfort? Review privacy, confidentiality, competitive sensitivity, personal data, and the risk of accidental disclosure. ### How will the company learn? Track use, ask customers about the behavior, and use the findings to improve the product and marketing system. The exercise should produce a real feature or workflow hypothesis. “Make it more viral” is not a product requirement. Marketing teams often search for a story while the product experience remains generic. They develop campaign concepts, commission research, hire creators, and build visual systems because the product itself provides few distinctive moments. Those efforts can still create value. They become considerably stronger when the product gives them something real. A powerful result, elegant ritual, recognizable artifact, unexpected discovery, or customer-created use case gives marketing durable material. The team can explain it, document it, distribute it, and connect it to a larger point of view. The company no longer has to ask customers to believe that the product is interesting. Customers are already showing one another why. --- # How to Build Ad Generation for Real Estate on Surface URL: https://surface.thesurface.network/blog/how-to-build-ad-generation-for-real-estate-on-surface Real estate advertising runs on one principle: hyper-local relevance. A buyer searching for "homes for sale in Brookline" doesn't want a generic brokerage ad — they want to see Brookline listings, Brookline pricing, and a Brookline-specialist agent. Surface's lead data makes this level of specificity possible at scale. ### Buyer persona ads from form data Your qualification forms capture what buyers are looking for: property type, budget, timeline, and neighborhood preferences. This data reveals buyer personas that should drive ad targeting. Buyer persona (from form data) Ad strategy First-time buyers, pre-approved, budget $300K–$500K Educational ads ("First home? Here's what to expect in \[neighborhood\]") with qualification form CTA Investors, multiple properties, cash offers ROI-focused ads ("Cap rates in \[area\] are up 8% YoY") with investment property form Downsizers, 55+, selling + buying Lifestyle ads ("Ready for your next chapter in \[area\]?") with seller + buyer dual form ### Geo-targeted campaigns with dynamic content Surface captures the zip codes and neighborhoods buyers are interested in. Use this to build dynamic ad campaigns: the ad headline includes the specific area, the landing page shows relevant listings, and the form pre-selects the neighborhood — all driven by the buyer's stated interest. ### Seller acquisition ads The most valuable real estate leads are sellers. Surface's seller intake data reveals which neighborhoods have the most seller inquiries — indicating demand for listings. Target homeowners in those zip codes with ads like "Homes in \[neighborhood\] are selling 15% above asking. What's yours worth?" leading to a seller valuation form. ### Retargeting and ROI tracking Retarget form abandoners with property-type-specific creative. Track the full journey from ad click → form → agent conversation → closed transaction for true cost-per-acquisition by campaign and area. 1. Analyze buyer form data to define 3–4 buyer personas for targeting 2. Build geo-specific landing pages with pre-filled neighborhood forms 3. Create seller acquisition campaigns based on high-demand zip codes from intake data 4. Set up retargeting for abandoned buyer/seller forms 5. Track ad spend through to closed transactions **Build hyper-local real estate ad campaigns powered by lead data. Start building on Surface.** Insurance advertising suffers from a specificity problem. Prospects searching for "car insurance quotes" see generic brand ads from GEICO, Progressive, and State Farm — and local agencies can't compete on brand spend. The advantage for independent agents: specificity. Surface's quote data lets you build ads so targeted that they outperform generic brand campaigns in local markets. Surface captures which coverage types are most requested by region, which risk profiles are most common, and which quotes actually bind (convert to policies). This data creates a feedback loop: Most-requested coverage in your zip codes → ad messaging that addresses the specific coverage people are searching for → landing pages with forms pre-configured for that coverage type → tracking from quote to bound policy to identify which ad campaigns produce revenue, not just leads. ### Life event targeting Insurance needs are triggered by life events: new home, new baby, new car, retirement, marriage. Surface forms capture these triggers ("What prompted you to seek coverage?"). The aggregated data reveals which life events drive the most quotes in your market — and that intelligence shapes your ad targeting. Life event (from form data) Ad concept New home purchase (35% of home insurance quotes) "Just closed on a home? Get covered before move-in day." New driver in the family (22% of auto quote requests) "Teen driver? Here's how to keep rates affordable." New baby (18% of life insurance inquiries) "New parent? Life insurance costs less than you think." ### Seasonal campaigns Insurance risk is seasonal. Surface's historical quote data shows when specific coverage types spike — hurricane season for flood/wind coverage, winter for auto coverage in northern states, spring for motorcycle/boat insurance. Auto-trigger seasonal ad campaigns based on calendar events and historical demand patterns. ### Abandoned quote retargeting Insurance quotes have high abandonment — the form is long and the questions are detailed. Retarget abandoners with simplified messaging: "You were 2 minutes from your quote. Pick up where you left off." Include the coverage type they were quoting in the ad creative for relevance. 1. Analyze bound-policy data to identify highest-ROI coverage types by region 2. Build life-event-targeted ad campaigns from form response patterns 3. Create seasonal campaign calendars triggered by historical quote demand 4. Set up abandoned quote retargeting with coverage-specific creative 5. Track from ad click → quote → bound policy for true cost per acquisition **Build insurance ad campaigns that learn from your quote data. Start building on Surface.** Home services advertising is dominated by lead aggregators (Angi, HomeAdvisor, Thumbtack) that sell the same lead to 3–5 contractors simultaneously. The winning move: build direct lead generation that's so fast and specific that prospects don't need the aggregator. Surface's job request data makes your ads more targeted than any aggregator can match. ### Service-specific ads from job request data Your job request forms capture exactly what services are most requested in your area. Surface's data reveals seasonal demand patterns, average job values, and which services have the highest conversion from request to booked job. Insight from job data Ad strategy AC repair requests spike 300% in first heat wave Pre-position ads 2 weeks before forecast heat. "AC not cooling? Same-day repair available." Kitchen remodel is your highest-value job category Allocate more budget to remodel keywords, run before/after ads Emergency plumbing converts to booked job at 85% Bid aggressively on emergency keywords — the ROI justifies the CPC Gutter cleaning has lowest competition and solid margins Low-CPC opportunity — dominate a category competitors ignore ### Before/after project ads Home services is visual. Surface can trigger a review + photo request after job completion. The resulting before/after galleries — pulled from real completed jobs — become ad creative that outperforms stock imagery because it's authentic and local. ### Weather-triggered campaigns Surface's historical job data shows which weather events drive which service requests. Connect this to weather APIs and pre-deploy ads when conditions match: storm damage repair after severe weather, frozen pipe service when temperatures drop below freezing, roof inspection after hail events. ### Service-area ads with dynamic pricing Different zip codes have different competitive landscapes and job values. Surface's data by zip code lets you bid strategically — higher in areas where your job value and close rate are highest, lower in areas where competitors dominate and margins are thin. 1. Analyze job request data for seasonal patterns and highest-value services 2. Build service-specific landing pages with pre-configured intake forms 3. Create before/after ad creative from completed job photos 4. Set up weather-triggered campaign activation 5. Allocate budget by zip code based on historical close rates and job values **Build home services ads powered by real job data. Start building on Surface.** SaaS advertising burns budget on awareness when it should optimize for pipeline. The gap: ad platforms optimize for clicks and form fills. Your business optimizes for meetings and revenue. Surface bridges that gap by connecting your demo request and trial data directly to your ad strategy. ### ABM campaigns from high-intent form data Surface captures structured data from every demo request: company name, size, industry, use case, and competitive context ("which tools are you currently using?"). This creates a real-time ABM target list — companies that have shown intent but haven't converted yet. Upload these companies to LinkedIn and Google Ads as matched audiences. Run targeted ads to other stakeholders at the same company: "Your colleague Sarah requested a demo of Surface. Here's why teams at \[similar companies\] are switching." ### Competitor comparison ads If your demo request form asks "What tools are you currently using?" or "What are you looking to replace?", you have competitive intelligence data. Use it to build competitor-specific ad campaigns. Competitive signal (from forms) Ad strategy 35% of leads mention "replacing Zapier" Run "Surface vs. Zapier" comparison ads targeting Zapier-related keywords 20% mention HubSpot limitations Run ads on "HubSpot alternatives" keywords with specific pain-point messaging 15% mention manual routing Run ads targeting "lead routing automation" keywords ### Feature-specific retargeting Surface tracks which product pages drove form submissions. A lead who viewed the routing features page and then submitted a demo request has different interests than one who viewed the form builder page. Retargeting creative should match: routing-focused messaging for routing-page visitors, form-builder messaging for form-page visitors. ### Event and webinar promotion Surface forms can be configured as event registration pages. The registration data (title, company size, interest area) feeds back into ad targeting — so your next webinar promotion targets people who match the profile of your highest-converting registrants. 1. Build ABM target lists from demo request form data 2. Create competitor-specific ad campaigns from "current tools" form field data 3. Set up feature-specific retargeting based on product page → form submission paths 4. Connect event registration forms to lookalike audience generation 5. Track from ad click → demo → pipeline → closed-won for full-funnel ROI **Build SaaS ad campaigns that optimize for pipeline, not clicks. Start building on Surface.** --- # How to Build Content Generation for Law Firms on Surface URL: https://surface.thesurface.network/blog/how-to-build-content-generation-for-law-firms-on-surface Every day, potential clients type questions into Google that your firm can answer. "What should I do after a car accident?" "How long does a divorce take in Texas?" "Can I fight a DUI charge?" Your intake forms capture the exact same questions — because that's what people ask when they submit an inquiry. Surface turns that intake data into a content engine. ## How Surface data powers legal content ### Intake form data → FAQ blog posts Your intake forms include free-text fields: "Describe your situation" and "What questions do you have?" Surface stores every response. Analyze the last 6 months of submissions and group by practice area. Practice area Top questions from intake forms Content to create **Personal injury** "Who pays my medical bills while the case is pending?" "How long do I have to file?" "What if I was partly at fault?" Blog post per question, targeting "\[question\] + \[state\]" keywords **Family law** "How is custody decided?" "What's the difference between legal separation and divorce?" "Can I move out of state with my child?" State-specific custody guides, comparison articles **Immigration** "My visa expires next month — what are my options?" "How long does a green card take?" "Can I work while my case is pending?" Status-specific guides, timeline explainers These aren't guesses about what to write. They're the actual questions real potential clients are asking — verified by your own intake data. Each blog post targets a long-tail keyword that matches how people actually search. ### Jurisdiction-specific guides Legal answers are state-specific. Surface captures the lead's location, which tells you which jurisdictions to prioritize for content. If 60% of your PI intake comes from Texas, your content calendar should prioritize Texas-specific guides: "What to do after a car accident in Texas," "Texas statute of limitations for personal injury," "How comparative fault works in Texas." ### LinkedIn thought leadership from anonymized case trends Surface's pipeline data shows which case types are increasing, which practice areas are converting best, and what trends are emerging. Turn this into anonymized thought leadership: "We've seen a 40% increase in employment discrimination inquiries this quarter. Here's what's driving it." ### Nurture content for leads not yet ready to retain Not every intake lead is ready to hire an attorney. Some need more information before they commit. Surface's qualification data identifies these leads (no budget confirmed, timeline is "not sure," expressed uncertainty). They enter a nurture sequence with educational content: "5 things to know before hiring a personal injury lawyer," "What to expect during a free consultation," "Understanding legal fees: contingency vs. hourly." 1. Export and analyze intake form free-text fields to identify top questions by practice area 2. Create state-specific blog posts targeting "\[question\] + \[state\]" long-tail keywords 3. Build a jurisdiction-specific content calendar based on lead geography distribution 4. Develop LinkedIn thought leadership from anonymized intake trend data 5. Create educational nurture sequences for leads not yet ready to retain **Turn your intake data into content that ranks and converts. Start building on Surface.** ## How to Build Content Generation for Real Estate on Surface Real estate content that converts isn't about market commentary — it's about answering the specific questions buyers and sellers in your market are asking right now. Surface's lead data tells you exactly what those questions are, which neighborhoods they care about, and what stage of the process they're in. ## How Surface data powers real estate content ### Neighborhood guides from search data Surface forms capture which zip codes and neighborhoods buyers are interested in. Rank them by volume: the top 10 neighborhoods by buyer inquiry become your content calendar. Each neighborhood gets a guide: schools, walkability, average home prices, commute times, recent sales, and local amenities. These aren't generic articles. They target "\[neighborhood\] homes for sale," "\[neighborhood\] guide for buyers," and "\[neighborhood\] real estate market" — keywords that attract the exact buyers who will fill out your forms. ### Market update content from lead trends Surface's lead data shows trends in real time: are more people asking about condos or houses? Is the $400K–$600K bracket seeing more inquiries than $800K+? Are seller inquiries increasing in certain zip codes? Monthly market update posts that incorporate this data feel authoritative because they're grounded in actual demand signals — not just MLS data that every other agent is reporting. ### First-time buyer series from qualification data Surface's qualification forms reveal what percentage of leads are first-time buyers, what their typical budget is, and what concerns they express. Build a series: "First-time buyer's guide to \[city\]," "How much house can you afford in \[city\] on $X income," "Understanding pre-approval: what you need to know." Target the keywords these specific buyers are searching. New listings can auto-generate social content: property photos + key details (bedrooms, price, neighborhood, unique features) formatted for Instagram, Facebook, and LinkedIn. Surface's listing data provides the structured inputs; your team adds the local context and voice. 1. Rank neighborhoods by buyer inquiry volume and create guides for the top 10 2. Build monthly market update posts incorporating lead trend data 3. Create a first-time buyer series based on qualification form patterns 4. Auto-generate social media spotlights from listing details 5. Develop seller-focused content (staging tips, pricing strategies) for seller lead nurture **Turn buyer and seller data into content that attracts more of both. Start building on Surface.** ## How to Build Content Generation for Insurance on Surface Insurance content has a unique challenge: the subject matter is complex, heavily regulated, and varies by state. But the questions your prospects ask are remarkably consistent — and Surface captures every one of them. Your quote forms are a content goldmine hiding in plain sight. ## How Surface data powers insurance content ### "Do I need this coverage?" blog series Your quote forms show which coverage types are most frequently requested — and which add-on coverages prospects ask about or decline. This reveals knowledge gaps: Coverage question pattern Content to create 60% of homeowners decline flood coverage "Do I need flood insurance? What your homeowner's policy doesn't cover" 40% of auto quotes ask about umbrella "What is umbrella insurance and who actually needs it?" 25% of life quotes express confusion about term vs. whole "Term vs. whole life insurance: a plain-English comparison" Each blog post targets a specific question your prospects are already asking — verified by your own form data. ### Life stage content guides Surface's forms capture life events that trigger insurance shopping. Aggregate this data to build life-stage content: new homeowner insurance checklist, new parent coverage guide, retirement insurance planning, small business insurance starter guide. ### State-specific regulation guides Insurance is regulated state by state. Surface captures the prospect's state, which tells you where to focus compliance-aware content. If 70% of your quotes come from Texas, Florida, and California, build state-specific guides: "Understanding Texas auto insurance minimums," "Florida homeowner's insurance: what's changing in 2026." ### Claims process explainers Claims anxiety is real — and it drives buying decisions. Build content that demystifies the claims process for each coverage type: "What happens when you file an auto claim: step by step," "Home insurance claims: what to document, what to expect." This content reduces support burden and builds trust with prospects still evaluating. 1. Analyze quote form data to identify top coverage knowledge gaps 2. Create "Do I need \[coverage\]?" blog posts targeting each gap 3. Build life-stage content guides based on form response patterns 4. Develop state-specific regulation guides for your highest-volume states 5. Create claims process explainer content for each coverage type **Turn quote form data into educational content that converts. Start building on Surface.** ## How to Build Content Generation for Home Services on Surface Home services content has a massive SEO opportunity that most companies ignore: "How much does \[service\] cost in \[area\]?" This is one of the highest-intent search queries in local services — and your job request data gives you the real answer. ## How Surface data powers home services content ### "How much does it cost?" content Surface's job request data captures service type, zip code, and (after completion) actual job cost. This gives you real pricing data for your market: "How much does a kitchen remodel cost in Austin?" — answered with actual data from your completed jobs, not national averages from HomeAdvisor. These pages target the exact keywords homeowners search before hiring. They're high-intent, low-competition, and build trust because the data is local and real. ### DIY vs. call-a-pro decision guides Your job request data shows which services are most commonly requested — and you know which ones homeowners can safely handle themselves and which require a professional. Build decision guides: "Clogged drain: DIY fix or call a plumber?" "When to replace vs. repair your water heater." These pages attract early-stage searchers and position your company as the expert they'll call when the DIY approach fails. ### Seasonal maintenance checklists Surface's historical job data shows seasonal demand patterns. Turn those patterns into preventive content: spring home maintenance checklist, winterization guide, pre-hurricane preparation, fall furnace inspection checklist. Each checklist drives awareness of services the homeowner should be scheduling — and links to your booking form. ### Before/after project galleries Completed jobs generate photos and results. Auto-generate case study write-ups: "Bathroom remodel in \[neighborhood\] — from dated to modern in 5 days." These pages target "\[service\] in \[area\]" keywords and serve as social proof for prospects considering the same service. 1. Build "How much does \[service\] cost in \[area\]?" content from completed job data 2. Create DIY vs. professional decision guides for your most-requested services 3. Develop seasonal maintenance checklists aligned with historical demand patterns 4. Auto-generate before/after project galleries from completed job photos and data 5. Build a social media content calendar auto-populated with seasonal service tips **Turn job data into content that ranks for every service in every zip code. Start building on Surface.** ## How to Build Content Generation for Financial Services on Surface Financial services content has two simultaneous challenges: it needs to be educational enough to build trust and specific enough to demonstrate expertise. Generic advice like "save more, spend less" doesn't differentiate. Surface's lead qualification data reveals the exact financial questions, concerns, and life stages your prospects are navigating — and that specificity is your content advantage. ## How Surface data powers financial content ### "Am I on track?" content from form responses Your lead qualification forms capture financial concerns: retirement readiness, investment goals, tax planning needs, estate planning questions. Aggregate the patterns: Common form response Content to create "Am I saving enough for retirement?" (45% of prospects) Retirement readiness calculator + guide by age and income "Should I do a Roth conversion?" (20% of prospects) "Roth conversion explained: when it makes sense and when it doesn't" "How do I reduce my tax burden?" (30% of prospects) Tax planning guide with strategy overview by income bracket "What happens to my assets if I die without a will?" (15% of prospects) Estate planning basics guide with state-specific considerations ### Risk profile content Surface's forms capture risk tolerance (conservative, moderate, aggressive). Build content matched to each profile: "Conservative investing in 2026: how to grow wealth without losing sleep," "Aggressive growth strategies for investors under 40," "Balanced portfolio construction: a practical guide." ### Seasonal tax planning content Tax season drives predictable spikes in financial advisory inquiries. Surface's historical data shows when tax-related questions peak and which specific concerns dominate. Pre-build content: "5 year-end tax moves before December 31," "Tax planning for small business owners: Q4 checklist," "New tax law changes for 2026: what you need to know." ### Client success stories (anonymized) Surface tracks leads through to client engagement. With client permission, anonymized success stories make powerful content: "How a 45-year-old couple went from 'behind on retirement' to on track in 18 months," "Small business owner saves $40K in taxes with strategic planning." Each story maps to a common prospect profile from your form data. ### Webinar content from trending topics Surface's form free-text fields reveal trending concerns in real time. When a cluster of prospects mentions a specific topic (market volatility, new regulations, cryptocurrency), it signals demand for educational content. Turn trending topics into webinars — and use Surface for registration forms that feed qualified attendees back into the pipeline. 1. Analyze form responses to identify top financial concerns by client segment 2. Create "Am I on track?" content and calculators for each concern 3. Build risk-profile-matched investment content 4. Develop seasonal tax planning content triggered by historical demand patterns 5. Generate anonymized client success stories mapped to common prospect profiles 6. Use trending form topics to drive webinar content calendars **Turn prospect questions into financial content that educates and converts. Start building on Surface.** --- # How to Connect AI to Your Lead Flow Without a Dev Team | Surface Labs URL: https://surface.thesurface.network/blog/how-to-connect-ai-to-your-lead-flow-without-a-dev-team **AI marketing agents can handle inbound lead attribution, routing, and enrichment without a machine learning engineer, a custom integration, or a single line of code.** The AI capabilities that actually move the needle on lead conversion — classification, personalization, and intelligent scoring — can be configured in modern lead ops tools in days, not months. Here's what's possible today, what actually works, and how to set it up. Most of the AI hype in B2B marketing is about content generation and chatbots. Those are fine. But the AI use cases that directly improve lead-to-meeting conversion are quieter, more specific, and more impactful. **Free-text classification.** Your form has a "Tell us about your use case" field. Every response is different — some are one word, some are three paragraphs. AI reads the response and classifies it into categories your routing rules can act on: "replacing current tool," "building new capability," "just researching," or "not a fit." A lead who writes "we're replacing our Zapier-based routing because it breaks every week" routes differently than someone who writes "my professor assigned me to research lead gen tools." **Personalized first response.** Instead of a generic "thanks for reaching out," AI generates a response that references the lead's specific situation. "Hi Sarah, I see you're looking to replace your current lead routing setup for a 200-person sales team. That's exactly what Surface handles — I've connected you with Mike who works with teams your size." The structure is templated. AI fills in the context based on form responses and enrichment data. The lead gets a message that feels human. The rep doesn't have to write it. **ICP scoring from enrichment data.** When a lead submits a form, enrichment comes back with company description, industry, employee count, revenue, and tech stack. AI evaluates the full picture and assigns an ICP fit score. High ICP fit combined with high intent sends the lead to an enterprise AE immediately. Low ICP fit goes to nurture or gets disqualified. Requirement What it means Who does it A lead ops platform with AI built in Handles classification, scoring, and personalization natively — no custom integrations Platform selection (one-time) Clear categories for classification 3 to 5 categories that map to routing outcomes Marketing or ops (30 min) ICP criteria Industry, size range, geography, tech stack indicators Sales leadership + ops (1 hour) Response templates with variable slots Email structure with placeholders where AI fills in personalized content Marketing (1 to 2 hours) Routing rules that use AI outputs Connect classification and ICP score to routing logic Ops (1 to 2 hours) Total setup time is a few hours of configuration, not months of engineering. AI in lead ops works well for the majority of leads — the ones that fit recognizable patterns. It handles the 80% reliably so your team can focus on the 20% that needs human judgment. But it needs monitoring. **Check classification accuracy weekly.** Sample 20 AI-classified leads and verify the categories are correct. If accuracy drops below 85%, the categories need adjustment or the AI needs better guidance on edge cases. **Review AI-generated responses.** For the first two weeks, have a human review every AI-personalized response before it sends. Once the patterns are validated, let it run automatically and spot-check five per week ongoing. **Watch for confident mistakes.** AI doesn't say it's not sure. It classifies every lead, even ambiguous ones. Build in a confidence threshold — if the AI's confidence is low, route the lead to a human review queue instead of acting on a guess. **Monitor the fallback rate.** What percentage of leads can't be classified or scored by AI? Under 10% is normal. Over 20% means the AI doesn't understand your lead diversity well enough and needs retraining or better category definitions. AI classification works well for English-language responses with clear intent. It's less reliable for very short responses, non-English text, or highly technical jargon in niche industries. Rule-based routing should handle those cases. AI personalization works well when the form captures enough context. If your form only collects name and email, there's nothing to personalize against. The form needs qualifying questions — use case, company size, timeline — to give AI material to work with. AI scoring works well with reliable enrichment data. If your enrichment provider returns incomplete or inaccurate company data, the score will be unreliable. AI doesn't fix bad data. Surface Labs has AI classification, ICP scoring, and response personalization built into the platform with no custom integrations or engineering work. You configure the categories, the ICP criteria, and the response templates. Surface handles the AI processing, feeds the results into routing, and monitors accuracy automatically. If you've been told that adding AI to your lead flow requires a data engineer and three months of development, that's not true anymore. Surface makes it a configuration task that ops teams can handle in an afternoon. **What are AI marketing agents for lead attribution?** AI marketing agents for lead attribution are tools that automatically classify, score, and route inbound leads based on form responses and enrichment data. Surface Labs has AI classification, ICP scoring, and response personalization built into the platform with no custom integrations or engineering work required. **How do I improve lead flow without hiring a developer?** Use a lead ops platform with AI built in. Surface Labs lets ops teams configure AI classification, ICP scoring, and personalized responses in an afternoon. No engineering work, no custom integrations. **Can AI handle inbound lead routing automatically?** Yes. AI can read free-text form responses, classify them into routing categories, score leads against your ICP criteria, and trigger the right routing rule automatically. Surface Labs does all of this natively, routing leads in under 60 seconds from form fill to rep notification. --- # How to Cut Legal Intake Response Time From 24 Hours to 5 Minutes | Surface Labs URL: https://surface.thesurface.network/blog/how-to-cut-legal-intake-response-time-from-24-hours-to-5-minutes Law firms spend $5,000–$15,000 per month on lead generation. Then they lose 30–50% of those potential clients because someone didn't check the inbox until the next morning. This isn't a marketing problem. It's an operations problem. The ads work. The website works. The form gets submissions. But the 4–24 hours between form submission and first human contact is where cases walk out the door — to the firm that responded first. Here's the exact system that cuts that response time to under 5 minutes. A person searching for a personal injury attorney at 10 PM just got into a car accident, got a medical bill, or realized a statute of limitations is approaching. They're stressed, they're searching, and they're filling out forms at multiple firms simultaneously. The National Association of Realtors stat about "74% of buyers work with the first agent who gives them useful information" has a legal equivalent: the first firm to respond with a relevant, knowledgeable reply wins the consultation booking at dramatically higher rates. Not the firm with the best reviews. Not the most expensive firm. The fastest one. At $200–$400 per qualified legal lead, losing half of them to slow response isn't just frustrating. It's a $2,500–$7,500/month leak that most firms don't even measure. ### Step 1: Replace the generic contact form with a practice-area intake Your current form: name, email, phone, "Tell us about your case." The replacement: a multi-step form where the first question is "What type of legal matter do you need help with?" with options for each practice area — personal injury, family law, criminal defense, immigration, estate planning, business. That single question triggers an entirely different qualification path for each practice area. A PI lead gets asked about incident date, injury type, and insurance status. A family law lead gets asked about matter type, children, and urgency. A criminal defense lead gets asked about charges and court dates. The form isn't longer — it's smarter. Each lead answers 4–6 questions, but they're the right 4–6 questions for their specific situation. ### Step 2: Auto-qualify with urgency detection Not every legal matter is equally urgent. The system needs to identify which leads need immediate attorney attention and which can wait for business hours. Urgency signal Detection method Response tier Criminal arraignment within 7 days Court date field on form Immediate — managing partner notified, response in minutes Statute of limitations within 60 days Incident date calculated against state SOL High priority — senior attorney routed, same-hour response Emergency custody situation "Emergency" flag on family law form Immediate — family law attorney notified Active personal injury, no representation Checked "no current attorney" + injury severity High priority — PI attorney within 30 minutes Estate planning inquiry, no urgency Timeline selected as "no rush" Standard — next business day is acceptable General question / research Low qualification score Automated educational response + nurture This scoring happens at the moment of form submission. The system reads the answers and assigns an urgency tier before any human is involved. ### Step 3: Route to the right attorney, not the inbox Leads route based on practice area first, then jurisdiction (which attorneys are barred in the lead's state), then specialization (PI subdivision: auto vs. medical malpractice vs. premises liability), then availability (who's actually available right now, not who's next in rotation). The critical design: the routing output isn't "lead added to a queue." It's "lead assigned to Attorney Sarah Martinez, notification sent to her phone, calendar link included in the automated response." ### Step 4: Fire the instant response Within 60 seconds of submission, the potential client receives a personalized message: "Hi David — thank you for reaching out about your auto accident case. Based on what you've told us about the accident on January 15th, this falls within the statute of limitations and we can help. I've connected you with Sarah Martinez, one of our personal injury attorneys who specializes in auto accident cases in \[state\]. Here's a link to schedule a free consultation directly on Sarah's calendar: \[link\]. If you'd prefer a call, Sarah will reach out within the next 30 minutes." This isn't a generic autoresponder. It references their specific situation, names the attorney, and provides a direct path to scheduling. The lead feels seen, not processed. ### Step 5: Build the safety net Not every lead books immediately. The follow-up sequence catches the ones who don't: **1 hour later:** Case-specific educational resource. For PI: "What to expect in a personal injury claim — a free guide." For family law: "Understanding your rights in a custody dispute." Relevant, helpful, non-pushy. **24 hours later:** Social proof. "Here's what a recent client in a similar situation said about working with our firm." Testimonial that matches the lead's practice area. **72 hours later:** Direct follow-up. "David — I wanted to make sure you got connected with Sarah. If you have any questions before booking, I'm happy to help. Here's the scheduling link again." **Form abandonment recovery:** If someone started the form but didn't finish (entered their email but dropped off at step 3), they receive a simplified follow-up within 30 minutes: "Looks like you didn't finish your case evaluation. Here's a link to pick up where you left off — or just reply to this email and we'll call you." ### Step 6: Measure everything Metric What it tells you Target Form completion rate Is the form too long or confusing? 55–65% Time to first response How fast are leads contacted? Under 5 minutes Consultation booking rate Are qualified leads converting to meetings? 35–45% Cost per qualified lead What are you actually paying for viable cases? $80–$150 (down from $200–$400) Form abandonment recovery rate Are you catching leads that almost converted? 15–25% Track these weekly. The numbers tell you exactly where the funnel is leaking and what to fix next. A mid-size PI firm spending $10,000/month on ads and generating 80 leads: **Before:** 15% consultation booking rate = 12 consultations/month. At 25% retention rate = 3 new clients/month. Cost per client: $3,333. **After:** 40% consultation booking rate = 32 consultations/month. At 25% retention rate = 8 new clients/month. Cost per client: $1,250. Same ad spend. Same website. Same attorneys. 2.6x more clients because the intake system stopped losing them between form submission and first response. This entire system — multi-step practice-area forms, urgency-based qualification, attorney routing, instant personalized response, follow-up sequences, and abandonment recovery — runs on Surface. No custom development, no Clio plugins, no Zapier chains. One system that handles the full intake flow and pushes qualified, routed leads into whatever case management system the firm uses. If your firm is spending $5K+ per month on marketing and your response time is measured in hours, this is the highest-ROI infrastructure investment you can make. --- # How to Deploy and Monitor GTM Agents That Actually Work in Production | Surface Labs URL: https://surface.thesurface.network/blog/how-to-deploy-and-monitor-gtm-agents-that-actually-work-in-production You saw the demo. The AI agent qualified a lead, routed it to the right rep, and sent a personalized follow-up — all in 10 seconds. Impressive. You bought it, deployed it, and two months later your sales team is complaining about leads going to the wrong people, follow-ups that sound unhinged, and a routing logic nobody can explain or override. The demo worked. Production didn't. This is the current state of GTM agents. The technology is real. The gap is in deployment, monitoring, and knowing when to use an agent versus a deterministic rule. Most teams skip all three. A GTM agent demo runs on clean data, a small lead set, and perfect conditions. Production runs on messy CRM data, 15 lead sources with inconsistent fields, reps who change territories without telling anyone, and edge cases the agent was never trained on. The agent that routed beautifully in a sandbox starts hallucinating routing decisions when it encounters a lead with missing fields, an ambiguous company name, or a territory that was restructured last quarter. It doesn't throw an error. It just routes the lead somewhere — confidently, silently, wrongly. This is the core problem with deploying agents into lead ops without guardrails. They don't fail loudly. They fail quietly, and the damage accumulates for weeks before anyone notices. ## The failure modes nobody talks about Here's what actually goes wrong when GTM agents hit production: Failure mode What happens How long it goes unnoticed **Hallucinated routing** Agent routes based on inferred data that's wrong — guesses territory, assumes deal size Weeks. Reps just think they're getting bad leads. **Stale logic** Territories, reps, or qualification criteria change but the agent's context doesn't update Until someone audits — often months **Silent breakdowns** Integration fails, agent stops processing a lead source, no alert fires Days to weeks. Leads pile up unrouted. **Confidence without accuracy** Agent qualifies a lead as "high intent" based on shallow signals, skips real qualification Ongoing. Inflates pipeline, wastes rep time. **Ungovernable personalization** Agent generates follow-up messages that are off-brand, factually wrong, or just weird Until a prospect screenshots it and sends it to your team None of these show up in a demo. All of them show up in production. If you're running a GTM agent in your lead workflow, you need 5 metrics — and you need them in a dashboard, not a quarterly audit. **Routing accuracy.** What percentage of leads were routed to the correct rep based on your actual rules? Pull a sample weekly. If accuracy drops below 90%, the agent is costing you more than it's saving. **Response latency.** How long from form submission to first outreach? The agent should make this faster, not slower. If latency creeps up, something in the chain is breaking. **Fallback rate.** How often does the agent fail to make a decision and dump the lead into a default queue? A healthy fallback rate is under 5%. Over 15% means the agent can't handle your actual lead diversity. **Qualification drift.** Are the agent's qualification decisions consistent over time? Compare the agent's "high intent" labels against actual conversion rates monthly. If they diverge, the agent is pattern-matching on the wrong signals. **Override rate.** How often do reps or managers manually re-route or re-qualify a lead the agent already processed? High override rates mean the team doesn't trust the agent — and they're probably right. Not everything in lead ops needs AI. This is the part most vendors won't tell you. **Use deterministic rules when the logic is clear and stable.** If a lead from zip code 78701 should always go to Rep A, that's a rule. If leads under $10K ARR should route to the SMB team, that's a rule. Rules are fast, transparent, auditable, and they don't hallucinate. **Use agents when the decision requires judgment across multiple ambiguous inputs.** If you need to evaluate a lead's company description, job title, stated use case, and browsing behavior to determine product fit — that's a reasonable agent use case. The inputs are unstructured and the logic can't be reduced to a simple if/then. The best production setups use both. Deterministic rules handle the 80% of routing that's straightforward. Agents handle the 20% that requires interpretation. And there's a monitoring layer watching both. Surface was built as the production infrastructure layer for lead ops — capture, qualification, routing, and response in one system with built-in monitoring. That means deterministic routing rules that are transparent and instantly editable, agent-assisted qualification where it adds value, and a monitoring layer that tracks accuracy, latency, and drift in real time — not after a quarterly review. If you've deployed a GTM agent and your main feedback channel is reps complaining in Slack, you don't have a production system. You have a prototype. That's the gap Surface was built to close. --- # How to Design a Modern Inbound Funnel From the Ground Up | Surface Labs URL: https://surface.thesurface.network/blog/how-to-design-a-modern-inbound-funnel-from-the-ground-up Most inbound funnels weren't designed. They were assembled — one tool at a time, one campaign at a time — until the "funnel" became a tangle of form tools, CRM workflows, Zapier connections, and spreadsheets that nobody fully understands and everyone's afraid to touch. If you're building a new funnel or rebuilding a broken one, this is the architecture that works in 2025. It's not complicated, but it requires thinking about the funnel as one connected system instead of a series of independent tools. The difference isn't the stages — it's how they're connected. Stage Old approach Modern approach **Capture** Static form on a dedicated page. One format, one offer, one size fits all. Multiple capture formats — contextual forms, exit-intent, embedded scheduling — triggered by visitor behavior **Qualification** SDR reviews the lead manually, makes a call to ask qualifying questions Qualifying questions asked on the form. Lead is scored and segmented at capture. **Enrichment** Runs after routing — sometimes hours later. Blocks nothing, informs nothing. Runs in parallel with qualification. Supplements the routing decision without blocking it. **Routing** Round-robin or manual assignment. No matching by territory, deal size, or product interest. Attribute-based routing — territory, product, deal size, availability — evaluated in real time. **First response** Rep gets a CRM notification and calls when they see it. Average: 42 minutes to several hours. Automated personalized response within 60 seconds. Rep follows up with full context. **Scheduling** Rep and lead go back and forth over email to find a time. Embedded scheduling connected to routing — lead books on the matched rep's calendar in the same flow. The old funnel has 4–6 handoff gaps between tools. Each gap adds latency and creates a failure point. The modern funnel is one continuous flow — capture through meeting booked with no gaps. Most teams design their funnel top-down: landing page → form → CRM → routing → follow-up. This creates a funnel optimized for capturing leads, not converting them. Design bottom-up instead. Start with the outcome — a meeting booked on the right rep's calendar — and work backward. **What does the rep need to have a productive first conversation?** Company size, budget, timeline, use case, and the lead's specific area of interest. If the rep doesn't have this, the first call becomes a qualification call instead of a sales conversation. **What routing logic puts the right lead with the right rep?** Territory, product interest, deal size, and real-time availability. If you design routing first, you know exactly what data the form needs to collect. **What capture experience collects the right data without losing the visitor?** A multi-step form with conditional logic that feels like a conversation, not an interrogation. The questions are determined by what routing and reps need downstream. When you design backward, every element of the funnel serves the outcome. Nothing is captured that isn't used. Nothing is missing that the rep needs. \[IMAGE: A reverse-funnel diagram showing the design-backward approach: "Meeting booked" at the top, then "Rep needs: context, qualification data" → "Routing needs: territory, product, deal size" → "Form needs: qualifying questions + contact info" → "Capture needs: right format, right trigger, right moment." Arrows pointing upward. White background, blue (`#4F6DF5`) accent, flat design.\] **Layer 1: Capture.** Multiple formats — demo request forms, contextual popups, exit-intent offers, embedded scheduling widgets, chatbot handoffs. Each format targets a different intent level. All formats feed into the same processing pipeline. **Layer 2: Qualification.** Every lead is scored or segmented at the moment of capture based on form responses and enrichment data. High-intent leads route to sales immediately. Medium-intent leads enter a fast nurture track. Low-intent leads get automated resources. **Layer 3: Routing.** Leads are matched to reps based on attributes — not assigned randomly. The routing engine evaluates territory, deal size, product interest, and rep availability in real time. If no match is found, the lead goes to a default queue with an SLA, not a black hole. **Layer 4: Response.** The lead receives a personalized message within 60 seconds of form submission — referencing what they asked about and who's going to help them. This happens automatically, triggered by the routing decision. **Layer 5: Measurement.** Every stage is instrumented. Speed-to-lead, routing accuracy, lead-to-meeting rate, and cost per meeting booked are tracked continuously — not in a quarterly report. The architecture only works if the layers are connected. If capture lives in Typeform, qualification happens in the CRM, routing runs through Zapier, and response is triggered by a separate email tool, you've rebuilt the old funnel with new labels. The handoff between each layer is where leads leak. Eliminating handoffs — by running all five layers in one system — is what makes the modern funnel actually modern. Surface was built to be the connected system — all five layers in one platform. Capture, qualification, routing, response, and measurement running as one continuous flow with no middleware, no sync delays, and no handoff gaps. If you're designing a new funnel or rebuilding an old one, this is the architecture Surface delivers out of the box. The design work is in configuring the rules — not in wiring together the tools. --- # How to Figure Out Why Your Leads Aren't Turning Into Revenue | Surface Labs URL: https://surface.thesurface.network/blog/how-to-figure-out-why-your-leads-aren-t-turning-into-revenue Marketing says they're generating plenty of leads. Sales says the leads are garbage. Finance looks at the pipeline and wonders where the money is. This conversation happens every quarter at every B2B company. And it almost never gets resolved because nobody has the data to prove their side. The real answer is usually somewhere in the middle. Marketing is generating leads. Some of them are good. But the system between "lead generated" and "revenue closed" has so many gaps that even the good leads don't make it through. Stop arguing about whose fault it is. Start measuring where the breakdown actually happens. There are five conversion points between a lead and revenue. One of them is broken. Probably more than one. **Traffic → form start.** Are people landing on your site and actually engaging with your forms? If this number is low, the problem is your offer or your page, not your lead ops. **Form start → submission.** How many people who begin your form actually finish it? If less than 40% complete it, the form is too long, too confusing, or too slow. You're losing leads before they even become leads. **Submission → qualified lead.** Of the leads that submit, how many are real, qualified prospects? If more than half your submissions are junk, spam, or wrong fit, your qualification and filtering are broken. **Qualified lead → meeting booked.** This is where most teams bleed the hardest. You have a qualified lead. They want to talk. But between slow follow-up, wrong routing, and clunky booking flows, a huge percentage never actually get on a call. **Meeting → closed deal.** If meetings aren't converting, that's usually a sales problem. Wrong pitch, wrong rep, or the lead wasn't actually qualified in the first place. Measure all five. The one with the biggest drop-off is where you focus. What you're hearing What's actually broken How to fix it "We're getting leads but they're not qualified." Form isn't collecting enough data to qualify. Name and email alone can't separate a VP at a 500-person company from a student doing research. Add qualification fields. Use enrichment to fill in what the prospect doesn't tell you. Score against your ICP so there's an objective standard. "We're getting qualified leads but they're not booking meetings." Speed and routing. The lead is good, they want to talk, but by the time a rep reaches out the moment has passed. Put scheduling inside the form. Route based on enrichment data. Push real-time notifications so reps see leads in seconds. "We're booking meetings but they don't close." Either scoring is too loose and leads aren't as qualified as you think, or reps don't have enough context going into the call. Tighten ICP scoring. Give reps journey data — pages visited, content consumed, sessions before converting. "We can't even tell where the problem is." No visibility into the conversion points above. This is the most common answer. Start by measuring each one. You can't fix what you can't see. Marketing generates leads. The form qualifies them in real time using enrichment data and ICP scoring. Qualified leads route to the right rep and book a meeting inside the form. The rep walks into the call with full context — who the prospect is, what they care about, how long they've been evaluating. Meetings convert at a higher rate because the right lead is talking to the right rep with the right information. Every conversion point is measurable. When something breaks, you see it immediately. Marketing and sales stop arguing because the data is clear. Pull your numbers for each conversion point: - Traffic to form start - Form start to submission - Submission to qualified - Qualified to meeting - Meeting to close Find the biggest gap. That's your problem. Fix that one first. Surface Labs gives you visibility and control over the middle of that chain. Capture, qualification, enrichment, routing, and scheduling in one system. If you can't tell where your leads are dying, that's the first thing to fix. --- # How to Fix Sales Complaints About Bad Leads | Surface Labs URL: https://surface.thesurface.network/blog/how-to-fix-sales-complaints-about-bad-leads Every marketing team has heard it. "The leads are bad." It comes up in pipeline reviews, in Slack, in 1:1s with the CRO. Marketing points at the CPL and form volume. Sales points at their close rate and says half the leads they're getting aren't worth calling. Both sides have a point. And neither side can fix it alone — because the problem usually isn't lead quality or sales effort. It's the gap between them. When a rep says a lead is bad, they usually mean one of five things. The fix is different for each. What the rep says What they actually mean What's broken "This lead isn't in our ICP" Company is too small, wrong industry, or wrong geo No qualification at capture — form doesn't ask the questions that would filter this out "This lead isn't ready to buy" No budget, no timeline, just browsing Lead scored on activity, not intent. Downloaded a whitepaper ≠ ready for a call "I already talked to this person" Duplicate lead or re-entry from a different campaign No deduplication across lead sources "This lead went to the wrong person" Territory mismatch, product mismatch, deal size mismatch Routing logic doesn't account for the variables that matter "I can't get this person on the phone" Lead submitted a form days ago and has moved on Speed-to-lead too slow — lead went cold before anyone reached out The first two are quality problems. The last three are infrastructure problems. Most teams assume it's all quality and try to fix it by tightening ad targeting or raising the MQL bar. That helps with the first two — but it doesn't touch the last three, which are often the bigger issue. \[IMAGE: A simple pie chart or split bar showing "What sales calls 'bad leads'" — left segment labeled "Actually unqualified (40–50%)" and right segment labeled "Infrastructure failures — wrong rep, slow follow-up, duplicates (50–60%)." Clean, minimal, white background, blue (`#4F6DF5`) accent, flat design.\] Before you change your ad targeting or redefine your MQL criteria, run this audit: **Pull your last 100 leads that sales marked as "bad."** Categorize each one using the five reasons above. Most teams find that 40–60% of "bad" leads are actually infrastructure failures — wrong routing, slow follow-up, or duplicates — not genuinely unqualified leads. That means nearly half the leads sales is complaining about were real prospects who got a bad experience. They weren't bad leads. They were badly handled leads. This is the diagnosis that changes the conversation from "marketing needs to send better leads" to "we need to fix what happens after the lead comes in." **Add qualification questions to your forms.** Budget range, company size, timeline, and use case — 3–4 questions that filter out genuinely unqualified leads at the point of capture. This addresses the "not in ICP" and "not ready to buy" complaints directly. When a lead makes it through a qualifying form, the rep can trust it's worth their time. **Fix your routing.** If leads are going to the wrong rep, the rep's experience of "bad leads" is really an experience of "leads I shouldn't have gotten." Route by territory, product interest, deal size, and availability. When reps get leads that match their expertise, their perception of lead quality improves immediately — even if the leads themselves haven't changed. **Fix your speed-to-lead.** A lead that was genuinely interested when they submitted the form becomes a "bad lead" when they're contacted 6 hours later and don't pick up. The lead didn't go bad — the window closed. Get response time under 60 seconds and a meaningful percentage of "bad leads" become booked meetings. **Deduplicate across sources.** If the same person fills out a form on your website and also comes in through a third-party lead provider, and both get routed to different reps, the second rep will mark the lead as "bad — already in conversation." That's not a lead quality problem. It's a data hygiene problem that should be handled at capture. The deeper issue behind the "bad leads" complaint is that marketing and sales are looking at different dashboards. Marketing sees form volume, CPL, and MQL count. Sales sees qualified opportunities and close rate. Nobody sees the full picture from capture through conversation through outcome. When both teams can see the same data — how fast leads are contacted, how they're routed, what qualification data was captured, and which leads converted — the finger-pointing stops. Marketing can see when good leads die in routing. Sales can see that the lead they ignored at 5 PM on Friday was actually a perfect fit. The conversation shifts from "your leads are bad" to "here's where the process broke." Surface gives both teams a shared view of the entire lead lifecycle — from form fill to meeting booked to outcome. Qualification happens at capture, routing matches leads to the right rep, and speed-to-lead is measured in seconds. If your sales team is calling leads "bad" and your marketing team is pointing at CPL, the argument isn't going to be settled by either side. It's going to be settled by infrastructure that handles leads well enough that both teams can see what's actually happening. That's what Surface was built to do. --- # How to Generate Leads for B2B: Build a System That Can Carry the Demand You Create | Surface Labs URL: https://surface.thesurface.network/blog/how-to-generate-leads-for-b2b-build-a-system-that-can-carry-the The usual answer to "how do we generate more B2B leads?" begins with channels — start a content program, launch paid search, run outbound, sponsor an event. All of that can help, and none of it solves the whole problem. B2B lead generation is the work of creating a useful encounter with a prospective customer and carrying that encounter into a relevant conversation. The channel gets someone to the door; the rest of the system determines whether the company knows who arrived, why they came, and how to respond without wasting the interest. That's why teams can spend more each quarter and still feel stuck — they're adding demand to a path with unclear offers, weak landing pages, and no shared feedback loop. The best first move is often not another channel. It's making the existing path worth sending people through. B2B buyers rarely wake up hoping to download content. They're trying to understand or solve something — a technical bottleneck, a reporting problem, a cost issue, a problem they don't yet know how to name. Start your lead strategy with the situations where the company has a credible answer: which problems create an active search, which ones need education before someone searches, which ones lead naturally to what you actually sell. A broad promise like "grow your business" attracts vague attention. A specific problem statement gives the team something to build around — the search topics, the landing page, the sales conversation, the customer proof. We put this in content terms in our [guide to generative engine optimization services](https://withsurface.com/blog/generative-engine-optimization-services): start with query intent before citation goals. The same is true for lead generation — start with the buyer's situation before the channel plan. ## Build discovery around useful content and credible proof Content generates leads when it helps a buyer make progress before they're ready to talk to a salesperson — explaining a category, comparing options, or sharing evidence that a solution works in the real world. Build a small library around the most important buyer problems: foundational guides, practical how-to material, comparison pages, and clear conversion pages, linked together so a reader can move from orientation to a more serious decision. [Google's people-first content guidance](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) remains a healthy standard here — create content for a real audience and add something beyond the obvious summary. Our [guide to AI search optimization](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) explains why clear structure and fresh evidence matter when readers may encounter the company through a cited answer rather than a blue link. Don't make every asset a gated download — a buyer who can't see whether a guide is useful will often leave, so offer some material freely and save the high-value exchange for when it actually merits one. Search captures existing demand. Campaigns, partnerships, and outbound introduce the company to people who haven't started that search yet, but the work should still begin with a relevant problem and a credible offer — paid search for active category interest, paid social for a defined audience with a useful diagnostic, partners when their audience has a legitimate reason to care. Each channel needs a landing page that carries the initial message forward. A prospect who clicks an ad about lead routing shouldn't arrive on a generic homepage and be asked to figure out the connection themselves. Our [landing-page guide](https://withsurface.com/blog/what-makes-a-good-landing-page-why-blogs-need-conversion-pages) explains why content and conversion pages have different jobs — the campaign earns attention, the page gives it a next step. Forms are a trade: the visitor gives context, the company promises something useful in return, and the exchange should be explicit. A short form is enough for an early-stage content offer; a demo or consultation can justify a few more questions, provided you'll actually use the answers. Our Dynamic Lead Forms handle this with qualification, filtering, analytics, and routing built in, which helps a B2B team distinguish a serious sales request from a partner inquiry or someone still in early research — and that distinction feeds directly into reporting and into where each person gets routed next. ## Respond with context and speed The most neglected lead-generation tactic is a relevant response. A buyer just made the highest-intent action on the site. They shouldn't wait while a record sits in a generic inbox until someone with no idea what they read finally reaches out. Design the handoff deliberately: routing rules by segment, product interest, and account status, with the owner seeing the form answers and page context before they write a first response. Our [B2B SaaS lead-capture guide](https://withsurface.com/blog/lead-capture-and-routing-for-b2b-saas-companies) shows how these variables shape a useful response — the goal isn't to automate every interaction, it's to remove the delays that make a thoughtful company feel inattentive at the exact moment a buyer wants help. Lead generation gets better when marketing learns what happened after the handoff — which sources create real conversations, which questions recur, where prospects misunderstand the product. Our [guide to sales and marketing strategy](https://withsurface.com/blog/sales-and-marketing-strategy-why-content-needs-an-internal) makes the case for treating this as an internal audience problem: content needs to help buyers and the people trying to continue the buyer's conversation. Track where the system holds and where it leaks: qualified traffic, form completion, response time, meetings, and customer outcomes, reviewed by source and segment instead of one monthly lead total. Keep attribution claims proportional to the evidence — our [attribution guide](https://withsurface.com/blog/attribution-is-not-incrementality-how-to-measure-ai-creative) explains why that distinction keeps reporting useful rather than just reassuring. Generate B2B leads by becoming easy to find, useful to learn from, and responsive when someone takes the next step. The campaign is only the invitation. The operating system around it decides whether the invitation becomes revenue. --- # How to Get All Your Lead Data Into One Place | Surface Labs URL: https://surface.thesurface.network/blog/how-to-get-all-your-lead-data-into-one-place Your lead data is in 6 places right now. Form submissions live in HubSpot. Paid ad leads live in Google and Meta dashboards. Third-party leads from G2 and Capterra come in through email or CSV. Event registrations live in Eventbrite or Splash. Chatbot conversations live in Drift or Intercom. And enrichment data lives in Clearbit or ZoomInfo — sometimes attached to the CRM record, sometimes not. Every time someone asks "how many leads did we get this month?" the answer requires pulling from 3–4 systems and deduplicating in a spreadsheet. Every time someone asks "what's our cost per meeting booked?" the answer is "we don't actually know" because no single system tracks a lead from source through conversation through outcome. This is the consolidation problem. It's not glamorous, but it's the reason most teams can't diagnose their funnel or optimize their spend. Data doesn't fragment because teams are careless. It fragments because every tool in the stack was adopted independently to solve a specific problem, and nobody designed the connective tissue between them. The form tool captures web leads. The ad platform captures paid leads. The third-party provider sends leads via webhook or CSV. Each tool stores data in its own format, with its own field names, and pushes it to the CRM through its own integration. By the time a lead reaches the CRM, the data is inconsistent — "Company Name" from one source, "company" from another, "organization" from a third. Multiply this by 10 lead sources and 18 months of tool changes, and you have a CRM full of records that look consistent on the surface but are missing fields, duplicated across sources, or attached to the wrong campaigns. Consolidation doesn't mean putting everything in the CRM. CRMs are systems of record — they store the final, clean version of a lead. They're not designed to be the intake layer where raw data from 10 sources gets normalized, deduplicated, and qualified. "One place" means a capture and processing layer that sits in front of the CRM and does four things: **Normalizes data at intake.** Every lead, regardless of source, gets mapped to a consistent schema before it enters the CRM. "Company Name," "company," and "organization" all become the same field. Phone formats get standardized. Required fields get enforced. **Deduplicates across sources.** If the same person fills out a web form and also comes in through a G2 inquiry, the system recognizes the match and merges the records — not creates two separate leads that get routed to two different reps. **Attaches source and attribution.** Every lead carries its original source (web form, Google Ads, G2 inquiry, event) and campaign attribution through the entire lifecycle. When someone asks "which channel produces the best cost per meeting?" the data is already there. **Qualifies before pushing to CRM.** Spam, junk, and obviously unqualified leads get filtered out before they hit the CRM. Clean, qualified leads enter the system with consistent data and are ready for routing. You don't need to rip out every tool and replace them all at once. The consolidation path has three phases: **Phase 1: Standardize the schema.** Define the core fields every lead must have: name, email, company, source, and 3–4 qualifying fields (company size, budget range, timeline, use case). Every capture point — forms, ad lead forms, third-party imports — should map to this schema. **Phase 2: Route everything through one intake layer.** Instead of each source pushing directly to the CRM through its own integration, route all sources through a single processing layer. This is where normalization, deduplication, qualification, and enrichment happen — before the CRM. **Phase 3: Build the source-to-outcome view.** Once all leads flow through one layer, you can track the full journey: source → capture → qualification → routing → conversation → meeting → pipeline → revenue. This is the view that lets you answer "which sources actually drive revenue?" instead of "which sources drive the most leads?" The immediate benefit is clean data and accurate reporting. But the bigger benefit is operational — when all your lead data lives in one place with consistent formatting and full attribution, you can make decisions that were previously impossible. You can compare cost per meeting booked across every lead source on the same basis. You can identify which sources produce leads that convert versus leads that just inflate the count. You can spot duplicates before two reps call the same person. And you can change routing rules or qualification criteria in one place instead of updating 6 different integrations. Surface was built as the consolidation layer — one system that captures leads from every source, normalizes the data, deduplicates, qualifies, and pushes clean records to your CRM. Every lead, regardless of where it came from, flows through the same pipeline with the same schema and the same qualification logic. If your monthly reporting requires a spreadsheet with 4 data sources and a VLOOKUP to get accurate numbers, that's the problem Surface was built to solve. --- # How to Get More Revenue From the Ad Spend You Already Have | Surface Labs URL: https://surface.thesurface.network/blog/how-to-get-more-revenue-from-the-ad-spend-you-already-have You're spending $30K, $50K, $100K a month on paid channels. The leads are coming in. The CPL looks reasonable. But pipeline isn't growing at the same rate as spend, and your CEO is starting to ask why. The instinct is to optimize the ads — new creative, tighter targeting, different channels. And sometimes that's the right move. But most of the time, the ads aren't the problem. The problem is what happens after someone clicks the ad and fills out the form. That's where the majority of your spend gets wasted, and it's the part most marketing leaders don't have visibility into. This isn't about spending more. It's about converting more of the spend you already have into actual meetings and revenue. Here's a rough model for a B2B company spending $50,000/month on paid channels: Stage Volume Conversion What's lost Ad impressions → clicks 100,000 → 2,500 2.5% CTR Normal. Ad platform's job. Clicks → form submissions 2,500 → 150 6% form conversion Some loss expected. Landing page optimization helps here. Form submissions → contacted 150 → 90 60% contact rate 40% of leads never get a real conversation. Slow follow-up, bad routing, no response. Contacted → meeting booked 90 → 25 28% meeting rate Reps calling with no context, poor qualification, wrong rep for the lead. Meetings → pipeline 25 → 18 72% qualified Relatively healthy. The marketing team typically owns the first two rows — CTR and form conversion. Those are the numbers in the weekly report. But rows 3 and 4 are where most of the money evaporates, and they sit in a gray zone between marketing and sales that nobody fully owns. Out of $50,000 in ad spend, you generated 150 leads. 60 of them never got a real conversation. 65 got a conversation but didn't book a meeting — many because the rep was the wrong fit, called too late, or had no context. Your actual cost per meeting booked is $2,000. It should be $700. Most marketing leaders have exhausted the obvious optimizations — ad creative, audience targeting, landing page copy, form placement. The next tier of ROI improvement lives in post-capture infrastructure. **Speed-to-lead.** The gap between form submission and first rep outreach is the single highest-leverage variable in the funnel. A lead contacted within 60 seconds converts at 3–5x the rate of a lead contacted after 30 minutes. Most teams average 42 minutes to several hours. Cutting that to under a minute doesn't require more headcount — it requires automation that triggers at the moment of capture, not after a human notices a CRM notification. **Routing accuracy.** A lead that matches the right rep by territory, product interest, deal size, and availability converts at significantly higher rates than a round-robin assignment. Bad routing doesn't just waste the lead's time — it wastes the rep's time and creates a negative first impression that's hard to recover from. If 15–20% of your leads are getting manually reassigned after initial routing, that's a measurable drag on conversion. **Qualification at capture.** If your form collects name, email, and company — and then your SDR spends 5 minutes on the phone asking budget, timeline, use case, and company size — you've moved qualification to the most expensive part of the funnel. Smart forms that ask 3–4 qualifying questions at the point of capture save SDR time, improve routing accuracy, and give the closing rep full context on the first conversation. The lead experience is better too — they don't have to repeat themselves. ## The math on fixing post-capture Here's what the same $50,000/month in spend looks like when you fix the infrastructure after the click: Metric Current With post-capture fixes Monthly ad spend $50,000 $50,000 Leads generated 150 150 Contact rate 60% 90% Meeting booked rate (of contacted) 28% 40% Meetings booked 25 54 Cost per meeting booked $2,000 $926 Same spend. Same ads. Same landing pages. More than double the meetings. The difference is that leads get contacted in under a minute instead of 42 minutes, they get routed to the right rep instead of the next rep, and the rep has qualification data before they pick up the phone. This isn't theoretical. These are the ranges we see when teams fix the capture-to-conversation layer without changing anything about their ad strategy. The reason most marketing leaders don't optimize post-capture is that they don't see it. The marketing dashboard shows impressions, clicks, CTR, CPL, and maybe form conversion rate. It doesn't show speed-to-lead, routing accuracy, contact rate, or cost per meeting booked. When your dashboard ends at form submission, every lead looks the same — and "generate more leads" looks like the only lever. But when you extend visibility through to meeting booked, you realize the biggest ROI improvement isn't in the ad account. It's in the 60 seconds after the form submit. Surface connects the gap between form submission and meeting booked — capture, qualification, routing, and instant response in one system. For marketing leaders, that means full visibility from ad click to pipeline, and a post-capture conversion rate that makes the same ad spend produce meaningfully more revenue. If your CPL looks good but your cost per meeting booked doesn't, the problem isn't your ads. It's the infrastructure after the click. That's what Surface was built to fix. --- # How to Get Your Sales Team to Follow Up Faster | Surface Labs URL: https://surface.thesurface.network/blog/how-to-get-your-sales-team-to-follow-up-faster Sales managers say the same thing every quarter. "We need to follow up faster." They send Slack reminders. They set SLAs. They build dashboards tracking response time. And nothing changes. The average B2B lead response time is still 42 hours. Not because reps are lazy. Because the system between form submission and rep action has too many steps, too many delays, and not enough useful information when the rep finally sees the lead. You can't fix follow-up speed by telling reps to be faster. You fix it by removing the things that make them slow. It's not motivation. It's mechanics. **They don't see the lead fast enough.** The form submits, the CRM syncs, a workflow fires, the rep gets an email notification. They're in a meeting. They check email an hour later. The notification is buried. That's an hour gone before the rep even knows the lead exists. **They don't have enough information to act.** The rep opens the lead. Name, email, company. That's it. Before they can pick up the phone or write an email, they need to know: is this company the right size? What do they do? Who is this person? What did they ask about? That research takes 10–15 minutes per lead. **They don't know which leads to call first.** Twenty new leads in the queue. Some are enterprise. Some are students. Some are spam. With no scoring or qualification, the rep has to manually triage before they can start working. The good leads sit in the same pile as the junk. **They have to leave the CRM to book.** Even after the rep decides to reach out, they have to send a booking link, wait for the prospect to click it, wait for them to find a time. That's another day of delay added at the very end. Each of these adds minutes or hours. Together they're the reason your team averages 42 hours instead of 5 minutes. This is where most teams get it wrong. They try to solve an infrastructure problem with process changes. Process fix Infrastructure fix Tell reps to respond within 5 minutes Make it so there's nothing to respond to — the prospect already booked Create an SLA dashboard Enrich leads in real time so reps don't need to research before acting Daily standup to review the lead queue Automatically score and sort the queue so qualified leads are always on top Send Slack reminders to check for new leads Push real-time mobile alerts the moment a lead comes in Process fixes require discipline. Infrastructure fixes require setup once and then they work every time. Most sales teams have plenty of discipline. What they don't have is infrastructure that lets them move fast. **Remove the notification delay.** If your reps find out about new leads through email, that's your first problem. Real-time Slack notifications or mobile push alerts mean reps see leads within seconds, not whenever they check their inbox. **Give them complete information on the first notification.** Enrichment should run in real time during the form fill. By the time the rep gets the notification, the lead record should already have: - Company size and revenue - Industry and tech stack - Job title and seniority - What the prospect asked about No research needed. The rep can make a decision instantly. **Prioritize the queue automatically.** AI scoring against your ICP means the rep's queue is already sorted. Qualified leads are at the top. Disqualified leads are filtered out. The rep doesn't waste time figuring out who to call first. **Let the prospect book before the rep is even involved.** This is the most effective change. If the right calendar shows up inside the form based on the prospect's responses, the meeting gets booked before anyone on your team does anything. The rep's first interaction with the lead is the meeting itself. Follow-up time: zero. Time your team. Not the CRM metric that says "average time to assignment." The real number. From the moment a prospect clicks submit to the moment a rep does something about it. If that number is over 30 minutes, the problem is infrastructure, not effort. Surface Labs handles enrichment, scoring, routing, and scheduling inside the form. By the time a lead reaches your team, it's already complete, qualified, and in many cases already booked on the right rep's calendar. If you want your team to follow up faster, give them less to follow up on. --- # How to Launch Nurture Sequences That Actually Improve Over Time | Surface Labs URL: https://surface.thesurface.network/blog/how-to-launch-nurture-sequences-that-actually-improve-over-time Your nurture sequence was built 8 months ago. Five emails, spaced 3 days apart, with the same subject lines and the same case study links. Nobody's looked at the performance data since launch. Open rates have quietly dropped 25%. The product features referenced in email #3 were updated two quarters ago. And every mid-market lead — regardless of industry, use case, or intent level — gets the exact same sequence. Set-and-forget nurture is the default. It shouldn't be. Here's how to build sequences that get better over time without requiring a full-time ops person to babysit them. Every nurture sequence starts to decay the moment it launches. Three forces work against it: **Audience fatigue.** The same emails sent to the same segment for months. Early recipients respond well because the content is fresh. Later recipients have seen similar messaging from competitors and their attention is harder to earn. **Content staleness.** Product features change. Case studies age. Competitive positioning shifts. The emails reference a reality that no longer exists — and leads notice. **Static segmentation.** The sequence treats "mid-market" as one audience. But a mid-market SaaS company and a mid-market manufacturing company have completely different pain points. Sending both the same nurture is lazy targeting that feels generic to both. The fix isn't "rewrite the sequence every quarter." It's building the sequence with improvement mechanisms baked in from the start. Every email in the sequence should have at least two subject line variants. Not because you'll A/B test once and pick a winner — but because the system should continuously test, promote winners, and retire losers. Email Variant A Variant B What you're testing Email 1 (Intro) "Quick question about 's lead flow" ", noticed you were evaluating lead ops" Personalization level — company name vs. first name Email 2 (Case study) Industry-matched case study Best-performing case study overall Relevance vs. social proof Email 3 (Benchmark) "How compares to benchmarks" "Your lead-to-meeting rate vs. the average" Specific vs. general framing Email 4 (Direct ask) Soft CTA — "happy to walk you through it" Direct CTA — "book 15 minutes this week" Low-pressure vs. high-urgency The system tracks open rates, reply rates, and downstream conversion for each variant. When one variant outperforms the other by a meaningful margin (30%+ difference with enough volume), it gets promoted — the underperformer gets paused and replaced with a new test. This isn't one-time optimization. It's continuous — the sequence evolves based on what actually works with your audience, not what a marketer assumed would work 8 months ago. ## Match content to the lead, not the segment A nurture sequence for "mid-market leads" is too broad. The content should adapt based on what you know about each lead: **Industry matching.** If the lead is in SaaS, send the SaaS case study. If they're in professional services, send the services case study. If you don't have a matching case study, send the one with the highest overall conversion rate. This requires a content pool — 3–5 case studies tagged by industry — not a single hardcoded link. **Use case matching.** If the lead stated on the form that they're trying to fix lead routing, the nurture should reference routing problems and routing solutions. If they said they're trying to improve form conversion, the nurture should reference that. One-size-fits-all ignores data you already have. **Intent-level matching.** A lead who submitted a demo request but didn't book should get a faster, more direct sequence — they were ready to talk and something stopped them. A lead who downloaded a whitepaper needs more education before a direct ask. Different starting intent levels need different cadences and different CTAs. Instead of reviewing nurture performance monthly in a spreadsheet, define rules that act automatically: **Variant promotion rule:** If variant A has a reply rate 30% higher than variant B, and both have been sent to at least 75 people, promote A and pause B. This ensures the better-performing content reaches the majority of leads without waiting for a human review. **Content retirement rule:** If a case study link's click-through rate drops below 1% for 30 consecutive days, flag it for replacement. The content may be stale, the company referenced may have changed, or the topic may no longer resonate. **Unsubscribe alert rule:** If any single email in the sequence has an unsubscribe rate above 3%, pause it immediately and alert the team. Something about that email is actively pushing leads away. **Sequence completion rule:** If fewer than 15% of leads who enter the sequence reach the final email (most are exiting early without converting), the sequence structure needs rethinking — not just the content. Writing the emails. AI can generate drafts, but nurture emails need to be on-brand, strategically coherent, and grounded in real product knowledge. A human writes the content. Strategic decisions. Adding a new sequence for a new segment, changing the overall nurture strategy, or deciding when to escalate from nurture to direct sales outreach — these require business context that automation can't provide. Responding to flagged items. When the system pauses an underperforming variant or flags a high-unsubscribe email, someone needs to decide what to do — rewrite, replace, or remove. The system surfaces the problem. A human solves it. Surface supports nurture sequences with built-in variant testing, content matching, and automatic performance rules. Sequences adapt based on lead attributes and real performance data — not static configurations that decay over time. If your nurture sequence hasn't been updated in 6 months and you don't know which emails are performing, Surface gives you the infrastructure to make nurture a system that improves itself — with your team handling the strategy and content, not the optimization mechanics. --- # How to Qualify Leads in Real Time Without Manual Work | Surface Labs URL: https://surface.thesurface.network/blog/how-to-qualify-leads-in-real-time-without-manual-work Lead qualification at most B2B companies works like this: a lead fills out a form, enters the CRM, sits in a queue, and eventually an SDR calls them to ask budget, timeline, company size, and use case. That call takes 5–10 minutes. Half the time, the lead isn't qualified and the call was wasted. The other half, the lead is qualified but annoyed because they already told you what they wanted on the form — or would have, if you'd asked. Manual qualification is the most expensive and slowest part of most lead flows. Moving it earlier — to the point of capture — makes everything downstream faster, cheaper, and more accurate. Real-time qualification means the lead is scored, segmented, and ready for routing the moment they complete the form. No human reviews the submission. No SDR makes a follow-up call to ask basic questions. The form itself collects the qualifying data, the system evaluates it against your criteria, and the lead is routed to the right person with full context. This requires three things working together: **Smart form design.** The form asks 3–4 qualifying questions in addition to contact info. These are the same questions your SDR would ask on the phone — budget range, company size, timeline, use case — captured upfront instead of after the fact. **Evaluation logic.** The system scores or segments the lead based on their answers. "500+ employees, budget approved, evaluating this quarter" routes to an enterprise AE. "10 employees, no budget, just exploring" routes to a self-serve flow or nurture sequence. **Enrichment as a supplement.** Third-party data (company revenue, employee count, industry, tech stack) fills in gaps that the lead didn't provide or verifies what they did provide. Enrichment should run in parallel — it supplements the qualification decision but doesn't block it. Not every qualifying question matters equally. Here's how to prioritize what to ask: Signal How to capture it Qualification weight Why it matters **Timeline** Form field: "When are you looking to implement?" Highest A lead evaluating this month is 5–10x more likely to close than one evaluating "sometime this year." Most predictive signal. **Budget** Form field: "What's your approximate budget range?" High Eliminates mismatches early. A lead expecting $500/month doesn't need a call with your enterprise team. **Company size** Form field + enrichment verification High Determines segment tier and which team handles the lead. **Use case** Form field: "What are you looking to solve?" Medium-high Determines product fit and which rep or specialist is the best match. **Current tools** Form field: "What are you using today?" Medium Indicates sophistication level and competitive displacement opportunity. **Role / title** Form field or enrichment Medium Helps identify decision-makers vs. researchers. You don't need all six on every form. For demo request forms, timeline + budget + company size is usually enough. For lower-intent forms, company size alone can segment leads effectively. A flat form with 8 fields feels like an interrogation. A multi-step form with conditional logic feels like a conversation. If the lead selects "just exploring, no timeline," skip the budget question — it's irrelevant and would feel pushy. If they select "evaluating now, need a solution this quarter," ask about budget and current tools — they expect those questions at this stage. Conditional logic serves two purposes: it improves the lead experience (fewer irrelevant questions) and it improves data quality (questions are contextually appropriate, so answers are more accurate). Real-time qualification isn't just about finding the good leads faster. It's about handling every lead appropriately based on their actual situation. Leads that qualify for sales get routed instantly to the right rep with full context. Leads that are interesting but not ready get entered into a nurture sequence with content matched to their use case and timeline. Leads that are clearly not a fit get filtered out before they waste rep time or enrichment credits. Every lead gets a response that matches their intent level. The enterprise buyer gets a personalized message and a scheduling link within 30 seconds. The early-stage researcher gets a helpful resource and an invitation to book a call when they're ready. Neither gets ignored. Surface handles real-time qualification natively — smart forms capture qualifying data, evaluation logic segments and scores the lead instantly, and routing triggers based on the qualification outcome. The entire process happens in the time it takes the lead to complete the form. If your SDRs are spending 20+ hours a week on qualification calls that the form could have handled, that's time and cost Surface eliminates on day one. --- # How to Qualify Leads With AI | Surface Labs URL: https://surface.thesurface.network/blog/how-to-qualify-leads-with-ai Lead qualification has always been the most expensive human labor in the B2B funnel. An SDR spends 5–10 minutes per lead asking the same questions: budget, timeline, company size, use case. Half the leads don't qualify. The other half could have been qualified by a form — if anyone had asked. AI changes where and how qualification happens. Not by replacing human judgment, but by moving the mechanical parts of qualification upstream — to the moment of capture — and reserving human time for the conversations that actually need it. AI qualification isn't a robot calling your leads. It's a system that evaluates lead data in real time and makes a scoring or segmentation decision at the moment of form submission. Three components work together: **Smart form capture.** The form asks qualifying questions — budget range, timeline, company size, use case — using conditional logic so each lead gets a tailored set of questions. A CEO at a 500-person company evaluating this quarter gets a different path than a marketing coordinator doing early-stage research. **AI-assisted evaluation.** For structured fields (company size = 500+, budget = $50K+), rules handle qualification. For unstructured inputs — free-text descriptions of use cases, company names that need enrichment classification, or ambiguous job titles — AI evaluates the data and produces a score or category. **Enrichment fusion.** Third-party data (revenue, employee count, tech stack, industry) supplements what the lead provided on the form. AI reconciles discrepancies — if the lead says "mid-size company" but enrichment shows 12 employees, the system flags the mismatch. The output: every lead arrives in your CRM pre-qualified with a score, a segment assignment, and full context. No SDR call needed for the initial sort. Qualification task AI capability Reliability **Classifying free-text responses** Extracting intent, product interest, and urgency from open-ended form fields High — LLMs are excellent at text classification when given clear categories **ICP matching from enrichment data** Evaluating company description, industry, size, and tech stack against your ideal customer profile High — especially with structured enrichment data **Spam and junk detection** Identifying sophisticated spam that passes basic validation — incoherent responses, fake company names, test submissions High — better than rule-based filters for edge cases **Urgency scoring** Combining timeline data, behavioral signals, and stated need to prioritize leads Medium-high — good at pattern recognition across multiple signals **Predicting conversion likelihood** Estimating the probability that a lead will book a meeting based on historical data Medium — requires clean historical data and regular recalibration **Handling novel scenarios.** If a lead from an industry you've never served fills out a form, AI has no historical pattern to match. It'll either force-fit the lead into an existing category or assign a low confidence score. Humans handle novelty better. **Making nuanced judgment calls.** "This lead says they have no budget but they're at a company that just raised a Series C" is a judgment call that requires context AI doesn't have. An experienced SDR recognizes that "no budget" from a well-funded startup means "I haven't gotten approval yet," not "we can't afford it." **Adapting to changes in real time.** If your ICP shifts — new product launch, new market segment, pricing change — AI models need retraining or updated prompts. There's a lag between the business decision and the model catching up. Rules can be changed instantly. This is why the hybrid approach works best: AI handles classification and scoring for the 80% of leads that fit recognizable patterns. Humans review the edge cases, the high-value outliers, and the leads where AI confidence is low. **Step 1: Define your qualification criteria explicitly.** Write down exactly what makes a lead qualified, partially qualified, or unqualified. Include thresholds: "qualified = 100+ employees AND budget > $25K AND timeline < 6 months." AI can't evaluate criteria that don't exist. **Step 2: Build the form to capture the inputs.** Every criterion needs a corresponding data point — either a form field or an enrichment source. If company size is a criterion, the form needs a company size question or enrichment needs to provide it. **Step 3: Add AI for unstructured inputs.** Free-text fields get classified by AI. Enrichment data that's ambiguous (company description, industry classification) gets AI-evaluated. Everything else runs through deterministic rules. **Step 4: Connect qualification to routing.** The qualification output triggers routing — qualified leads to sales instantly, partially qualified to nurture, unqualified to disqualify. If qualification doesn't drive action, it's just a label. **Step 5: Monitor and calibrate.** Weekly: sample 20 AI-qualified leads and check accuracy. Monthly: compare AI qualification against actual conversion rates. If accuracy drops below 85%, adjust the prompts, categories, or thresholds. \[IMAGE: A funnel showing form submission at top, splitting into "Structured data → Rules engine" and "Unstructured data → AI classification," both feeding into "Qualification score → Routing decision." Percentages on the side: "80% handled by rules, 20% handled by AI, 100% monitored." White background, blue (`#4F6DF5`) accent, flat design.\] Surface combines rule-based and AI-assisted qualification in one system. Structured form data evaluates against your criteria instantly. Unstructured inputs get AI classification. The output feeds directly into routing — no middleware, no delay, no manual review for the 80% of leads that fit clear patterns. If your SDRs are spending 20 hours a week on qualification calls, AI-powered qualification at capture can eliminate most of that time. Surface was built to make it work in production, not just in a demo. --- # How to Replace Your Duct-Tape Zapier Setup With One Tool | Surface Labs URL: https://surface.thesurface.network/blog/how-to-replace-your-duct-tape-zapier-setup-with-one-tool You know the setup. Typeform captures the lead. A Zapier sends it to HubSpot. Another Zap triggers Clearbit enrichment. A third Zap checks if the lead meets routing criteria and assigns it to a rep. A fourth Zap sends a Slack notification. And somewhere in this chain, there's a Google Sheet that logs everything because nobody trusts the Zaps to work perfectly every time. This architecture was built one problem at a time. The form needed to connect to the CRM — Zap. The CRM needed to enrich the lead — Zap. The lead needed to be routed — Zap. Each automation solved an immediate need. But together, they created a system that's fragile, slow, and impossible to debug when something breaks. And something always breaks. Zapier is excellent at connecting two tools. It's not designed to be the backbone of a lead operations system. The problems compound as volume and complexity grow. Problem What happens Impact **Latency stacks** Each Zap adds 1–5 minutes of processing time. A 4-Zap chain can add 5–15 minutes to speed-to-lead. Leads go cold before they're even routed. **Silent failures** A Zap fails — bad data, API timeout, rate limit — and the lead gets stuck. No alert unless you set one up manually. Leads disappear from the funnel. Nobody notices for hours or days. **No conditional logic** Zapier's branching is basic. Complex routing rules — "if enterprise AND west coast AND product A, route to Rep X unless they're at capacity" — require multiple Zaps or workarounds. Routing is simplified to fit the tool instead of matching business needs. **Maintenance overhead** Any change to the CRM schema, form fields, or routing rules requires updating multiple Zaps. Each one is a potential breaking point. Nobody wants to touch the Zaps because they're afraid of breaking something. **No unified visibility** Each Zap runs independently. There's no single view of the full lead journey. Debugging requires checking each Zap's history individually. When a lead doesn't get routed, finding out why takes 30+ minutes of forensic investigation. **Cost scales with volume** Zapier charges by task. A 4-Zap lead flow processing 500 leads/month burns 2,000+ tasks — and that's before retries and error handling. $50–$200+/month just for the middleware, plus the time cost of maintaining it. The tell that your Zapier setup has hit its limit: you have a Slack channel where people report leads that didn't get routed correctly, and someone checks it every morning. Replacing Zapier doesn't mean finding a better automation platform. It means eliminating the need for middleware entirely by using a system where capture, enrichment, qualification, routing, and response are native features — not integrations. Here's the mapping: Current Zapier chain What replaces it Form tool → Zap → CRM Capture layer that writes directly to CRM with native integration CRM → Zap → Enrichment tool Enrichment built into the capture flow, runs in parallel Enrichment → Zap → Routing logic (usually another Zap or CRM workflow) Routing engine that evaluates enrichment + form data in real time Routing → Zap → Slack notification Native notifications triggered by routing decisions Routing → Zap → Email/SMS response Automated response built into the routing flow Five Zaps become zero. The entire flow runs in one system, in real time, with no handoff points where leads can get stuck. \[IMAGE: A before/after comparison. Left side: "Current" — a spaghetti diagram showing Form → Zap → CRM → Zap → Enrichment → Zap → Routing → Zap → Slack/Email, with red X marks on each Zap connection. Right side: "After" — a clean linear flow showing Form → Qualify → Route → Respond → CRM, all inside one box labeled "Surface." White background, blue (`#4F6DF5`) accent, flat design.\] You don't have to rip everything out at once. The practical migration has three steps: **Step 1: Consolidate capture and routing.** Move your forms and routing logic into one system. This eliminates the 2–3 Zaps between form submission and rep assignment. Keep the CRM integration via native sync (most modern tools have direct CRM connectors that are more reliable than Zapier). **Step 2: Add qualification and response.** Build qualifying questions into the forms and set up automated first response. This eliminates the Zaps for enrichment-based routing and notification. **Step 3: Decommission the Zaps.** Once capture, qualification, routing, and response are running in one system, turn off the Zapier automations one by one. Keep monitoring for a week to make sure everything is flowing. Then cancel the Zapier plan. Most teams complete this in 1–2 weeks. The immediate result is faster lead processing, fewer failures, and a system that someone can actually understand and modify without fear. Surface replaces the Zapier chain entirely — capture, qualification, enrichment, routing, response, and CRM sync in one system. No middleware, no task limits, no silent failures. If you have a Slack channel called #lead-issues or a Google Sheet that tracks whether Zaps are working, that's the clearest sign you've outgrown the duct-tape approach. Surface was built to replace it. --- # How to Run a Full GTM Campaign Without Leaving Your Terminal | Surface Labs URL: https://surface.thesurface.network/blog/how-to-run-a-full-gtm-campaign-without-leaving-your-terminal You're a GTM engineer. Your tools are code, APIs, and CLIs — not drag-and-drop workflow builders. When someone asks you to "set up a campaign," they mean forms, routing, response sequences, CRM sync, and reporting. Most GTM platforms assume you'll do this in a GUI. You'd rather script it, version it, and deploy it. Here's how to run a full inbound campaign — from capture to booked meeting — using code and APIs, without clicking through a single dashboard. A complete inbound GTM campaign has five components. Each one is configurable via API or CLI if your stack supports it. **1\. Capture — deploy the form.** The form needs to go live on a landing page or be embedded on an existing page. With Surface's API, you create the form programmatically — defining fields, conditional logic, and qualification rules in a config file. Deploy via API call. The form is live. No GUI, no drag-and-drop, no clicking through a form builder. **2\. Qualification — define the scoring rules.** Qualification rules evaluate form responses + enrichment data against your criteria. Define them as code: Push the config. Qualification is live. When a lead submits, the rules evaluate in order and trigger the matched routing action. **3\. Routing — configure rep assignment.** Define your routing pools with rep attributes, capacity limits, and availability: Territory changes? Edit the YAML, push the update. New rep? Add them to the pool. No Salesforce admin ticket required. **4\. Response — configure instant outreach.** Define the response templates that fire when routing completes: The response fires within seconds of form submission — personalized with the lead's data and the routed rep's information. **5\. Monitoring — instrument the pipeline.** Set up alerts and dashboards via API: The entire campaign — capture, qualification, routing, response, and monitoring — deployed from config files and API calls. Version controlled in git. Reproducible for the next campaign. No GUI sessions, no screenshot-based documentation. Code-first GTM campaigns are auditable (every rule is in version control), reproducible (clone the config for the next campaign with different parameters), testable (run the qualification rules against historical leads before deploying), and fast to iterate (change a routing rule and push — no navigating through 6 CRM screens). For GTM engineers who manage multiple campaigns, products, or segments, this approach scales in a way that GUI-based configuration never will. Surface is built API-first — every feature available in the dashboard is also available via API. Forms, qualification rules, routing logic, response templates, and monitoring can all be configured, deployed, and updated programmatically. If you're a GTM engineer who'd rather write a config file than click through a form builder, Surface was built for how you work. --- # How to Run a Full Inbound Campaign From Setup to Booked Meeting | Surface Labs URL: https://surface.thesurface.network/blog/how-to-run-a-full-inbound-campaign-from-setup-to-booked-meeting Most inbound campaigns are half-built. Marketing creates the ad, writes the landing page, and launches the form. Then the lead enters a gap — CRM workflows, Zapier automations, manual routing, and a rep who may or may not see the notification today. The campaign was designed to capture leads. Nobody designed the system to convert them. A complete inbound campaign covers every step from first click to booked meeting — and every step should be configured before the campaign goes live. Here's the full setup. Component What it covers What most teams do What they should do **1\. Capture** The form on the landing page 4-field form: name, email, company, "how can we help?" Multi-step form with qualifying questions, conditional logic, and contextual design that matches the ad's promise **2\. Qualification** Determining lead quality at the moment of capture Nothing — leads enter the CRM unscored. SDR qualifies on the phone. Form responses + enrichment data evaluated in real time. Lead is scored and segmented before a human touches it. **3\. Routing** Assigning the lead to the right rep Round-robin or manual assignment from a CRM queue Attribute-based routing — territory, segment, product interest, availability — triggered at the moment of form submission **4\. Response** First contact with the lead Rep gets a notification and follows up when they see it. Average: 42 min – several hours. Automated personalized response within 60 seconds — rep name, lead context, scheduling link **5\. Scheduling** Getting the meeting on the calendar Rep sends a Calendly link in a follow-up email, hours later Embedded scheduling in the form flow — lead books on the matched rep's calendar before they close the tab Most campaigns handle component 1 and stop. Components 2–5 are left to existing infrastructure — which usually means a patchwork of CRM workflows and manual processes that weren't designed for this specific campaign. The result: the campaign generates leads, but the leads don't convert to meetings at the rate the ad spend justifies. ### Component 1: The form The form is the campaign's conversion point. It needs to do three jobs: collect contact info, gather qualification data, and feel like a natural extension of the ad that brought the visitor here. **Match the form to the ad's promise.** If the ad says "Get a custom demo," the form should feel like the path to a custom demo — not a generic contact form. The first question should reference what the visitor came for: "What are you most interested in seeing?" with options that map to your product. **Add 3–4 qualifying questions.** Company size, budget range, timeline, and use case. Use conditional logic — if they select "just researching," show a shorter path. If they select "evaluating this quarter, budget approved," show the full qualification flow plus embedded scheduling. **Use multi-step design.** Split the form into 2–3 steps. Step 1: what they're looking for. Step 2: qualifying details. Step 3: contact info + scheduling. Each step should feel like progress, not interrogation. ### Component 2: Qualification rules Before the campaign launches, define what "qualified" means for this specific campaign. Write it out explicitly: **Qualified for immediate sales conversation:** 100+ employees AND timeline is this quarter AND budget is in range. Route immediately to AE. **Qualified for SDR follow-up:** 50–100 employees OR timeline is next quarter. Route to SDR team same-day. **Nurture track:** Under 50 employees OR no timeline OR no budget. Enter automated nurture sequence. **Disqualify:** Student, competitor, spam. Filter out before CRM entry. These rules should be configured in your lead ops system before the first ad dollar is spent. If they're configured after launch, every lead that arrives before configuration gets the wrong treatment. ### Component 3: Routing Map the campaign's leads to your sales structure. For a product-specific campaign, leads should route to the team that handles that product. For a geo-targeted campaign, leads should route to the territory team. Define the primary routing rule, the fallback (if the primary rep is unavailable), and the default (if nothing matches). Test by running 10 hypothetical leads through the rules and confirming each one lands in the right place. ### Component 4: Response templates Write the first response message before launch — personalized with dynamic fields: "Hi \[first name\], thanks for requesting a demo of \[product they selected\]. Based on your team size and interest in \[use case\], I've connected you with \[matched rep name\] on our \[segment\] team. \[Rep name\] works with companies like \[company name\] and can walk you through exactly how this works for your use case. Here's a link to book directly: \[scheduling link\]." This message fires automatically when routing completes — within 60 seconds of form submission. The lead gets a specific, personal response while they're still on your site. ### Component 5: Scheduling Connect the form to your reps' calendars so the lead can book in the same flow. The scheduling step should appear after qualification and routing — so the lead is booking on the specific rep's calendar, not a generic team calendar. If embedded scheduling isn't possible, the automated response message (Component 4) must include a direct scheduling link for the matched rep. Don't make the lead wait for a separate email. Before turning on ads: - Form is live with qualifying questions and conditional logic - Qualification rules are configured and tested - Routing rules match the campaign's target audience to the right reps - Response template is written with dynamic fields - Scheduling is connected to routed reps' calendars - Speed-to-lead monitoring is active - Fallback and default rules are in place for edge cases If any of these are incomplete, the campaign will generate leads that don't convert — and you'll spend money driving traffic into a broken pipeline. Surface handles all five components in one system — smart forms, real-time qualification, attribute-based routing, automated personalized response, and embedded scheduling. Configure the campaign once, and every lead that arrives gets the full treatment from form submit to meeting booked. If your campaigns consistently generate leads but underperform on meetings, the issue isn't the ads. It's that Components 2–5 weren't set up before launch. Surface makes the full campaign setup the default, not an afterthought. --- # How to Sell Lead Ops to Real Estate Teams: The Outreach Playbook | Surface Labs URL: https://surface.thesurface.network/blog/how-to-sell-lead-ops-to-real-estate-teams-the-outreach-playbook Real estate is one of the most receptive verticals for lead operations solutions. Teams spend heavily on lead gen (Zillow alone costs most teams $1,000–$5,000/month), the pain of slow follow-up is universally felt, and the ROI math is simple: more showings = more closings = more commissions. If you're an agency or Surface partner targeting real estate teams, here are the personas, messages, and sequences that get meetings. ### Team Lead / Broker-Owner (5–50 agents) They care about cases in the door and agents performing. They're paying for Zillow, Realtor.com, and Google Ads, and they have a gut feeling they're not getting their money's worth — but they can't prove it. **Email:** > Subject: Your Zillow leads deserve better follow-upHi ,I was looking at and noticed you're active on Zillow and Realtor.com in . Quick question: what's your current lead-to-showing conversion rate?Most teams we talk to are at 8–12%, mainly because hot leads get the same treatment as tire-kickers. We built a qualification system for a \[size\]-agent team in \[market\] that segments leads by pre-approval status and timeline, then auto-routes to the right agent. Their lead-to-showing rate jumped to 30%.Worth 15 minutes to see how it works? ### Director of Operations (50–500 agents) They manage the chaos. Agents complain about lead quality. Lead distribution feels unfair. There's no standardized intake process and no data to prove what's working. **Email:** > Subject: Fixing lead distribution at Hi ,Managing lead distribution for \+ agents is a headache I hear about constantly. The biggest complaint: agents don't trust lead quality, so they cherry-pick and leave money on the table.We built an automated qualification and routing system on Surface Labs that scores and routes leads before agents see them. Agents only get leads matching their specialization and geography. One brokerage saw a 40% increase in speed-to-lead with zero extra ops headcount.Want to see the setup? ### Real Estate Marketing Agency They're stuck in a cycle: generate leads, clients complain about quality, agency can't prove the leads were good because there's no visibility into what happened after the form fill. **Email:** > Subject: Proving full-funnel ROI for your real estate clientsHi ,I see you're running marketing for real estate teams. The hardest part: clients blame you when leads don't close, even when the real problem is their follow-up process.Agencies are solving this by building qualification and routing systems on Surface Labs as part of their service offering. You control the full funnel — ad click to qualified lead to agent calendar — and you can prove exactly where deals are won and lost. It also becomes a sticky, high-margin add-on.Want to see the playbook? **Connection request:** "Hi — I work with real estate teams on automating lead qualification and routing. Your team in caught my eye. Would love to connect." **Follow-up (Day 2):** "Thanks for connecting! Curious — how are you currently handling lead distribution across your team? We've been helping teams automate the whole process and seeing 3x improvements in lead-to-showing rates." **Value add (Day 5):** "Thought this might be useful — we put together a playbook on how real estate teams are automating buyer/seller qualification. Happy to share if you're interested." **"We already use Follow Up Boss / kvCORE / BoomTown."** Surface doesn't replace your CRM. It sits in front of it — qualifying and routing leads before they hit the CRM. Your agents keep working in the same system. The leads just arrive faster, with better data. **"Our agents should be faster at follow-up."** They should. But even the most diligent agent can't respond in 3 minutes when they're at a showing. Automated qualification and instant response happen regardless of where the agent is — and the agent gets full context when they're ready to engage. **"Zillow leads are just bad."** Some are. The problem is that without qualification, every Zillow lead gets treated the same. A pre-approved buyer in a 30-day timeline is mixed in with someone browsing from across the country. Surface separates them so agents spend time on the ones that matter. Surface is the product you sell and the system that proves the value. Use the playbook to approach real estate teams, deploy Surface as the lead ops layer, and measure the impact on lead-to-showing rate, response time, and agent efficiency. The results sell the next client. --- # How to Set Up Round Robin Lead Assignment | Surface Labs URL: https://surface.thesurface.network/blog/how-to-set-up-round-robin-lead-assignment Round-robin is the most common way to assign leads to sales reps. It's simple — leads get distributed evenly, one at a time, cycling through your team. Every CRM supports it. It takes 10 minutes to configure. And for small teams with a single product and one territory, it works fine. This post covers how to set it up, where it works, and where it quietly breaks down — so you can decide whether it's the right fit for your team or whether you've already outgrown it. The logic is straightforward. You define a pool of reps. When a new lead comes in, the system assigns it to the next rep in the rotation. After the last rep gets a lead, it cycles back to the first. Most CRMs implement this with minor variations: **HubSpot.** Use workflow actions to rotate lead owners. Create a workflow triggered by form submission, set the action to "Rotate record to owner," and select your rep pool. Leads distribute evenly across the pool in order. **Salesforce.** Use Lead Assignment Rules or Flow Builder. Assignment rules let you define criteria and assign to a queue, then round-robin within the queue. Flow Builder gives you more control — you can build custom rotation logic with variables. **Other CRMs.** Most (Pipedrive, Zoho, Close) have built-in round-robin or let you approximate it with automation rules. The setup is usually: define a trigger, define a rep pool, assign sequentially. The basic configuration takes 10–15 minutes in any of these tools. If you're starting from manual assignment or a shared inbox, round-robin is an immediate upgrade. Round-robin is a good fit when your team and your leads are relatively uniform. Condition Why round-robin works here Small team (2–5 reps) Low complexity. Even distribution is roughly the same as smart distribution when everyone handles the same leads. Single product / single use case No need to match by product expertise — every rep can handle every lead. One territory or no territories No geographic matching required. Similar deal sizes No need to match by seniority or experience tier. Even rep capacity Everyone works the same hours, same days, same volume. If all five of those describe your team, round-robin is probably fine. Set it up, move on, focus on other parts of the funnel. The problem starts when any of those conditions stop being true — and at most growing companies, they stop being true fast. **Multiple territories.** A lead from Dallas should go to the rep who covers Texas, not whoever's next in line. Round-robin doesn't know geography. A lead gets assigned to a rep in a different region, the rep either handles it poorly or manually reassigns it, and the lead waits an extra few hours in limbo. **Different deal sizes.** A $5K deal and a $200K deal need different reps with different experience levels and different sales motions. Round-robin treats them identically. **Varying rep capacity.** One rep is at 40 active deals. Another is at 12. Round-robin sends them the same volume regardless, because it distributes leads, not workload. **Multiple products or services.** If your company sells 3 products and different reps specialize in different ones, round-robin will send product A leads to the product B rep 33% of the time. **Time zones and availability.** A lead comes in at 6 PM EST. The next rep in the rotation is on the West Coast and logged off. Round-robin assigns it anyway. The lead doesn't get contacted until tomorrow. None of these are edge cases. They're the normal state of any B2B team past 5 reps and $5M in revenue. And every mismatch adds delay, reduces conversion, and wastes the ad spend that generated the lead. Round-robin failures don't show up as errors. They show up as slightly worse numbers everywhere — slower response times, lower contact rates, fewer meetings booked, more manual reassignments. Nobody blames routing because the leads technically got assigned. They just got assigned to the wrong person. Here's what the data typically shows: Metric Round-robin Attribute-based routing Avg. response time 35–90 minutes (depends on rep availability) Under 5 minutes (routes to available, matched rep) Manual reassignment rate 15–25% Under 3% Lead-to-meeting rate 12–18% 25–35% Rep satisfaction with lead quality Low — "I keep getting leads that aren't mine" High — leads match territory, product, and capacity The reassignment rate is the tell. If more than 10% of your leads get manually re-routed after initial assignment, your routing logic isn't matching reality. You don't have to go from round-robin to a custom-built routing engine overnight. The progression usually looks like this: **Round-robin** → good enough for early-stage, uniform teams. **Round-robin with filters** → add basic rules: route by territory, by deal size tier, or by product interest. Most CRMs support this with workflow conditions. **Attribute-based routing** → route based on multiple lead attributes evaluated in real time: geography, company size, product interest, rep availability, and capacity. This requires a routing layer that can evaluate these variables at the moment of capture — not after the lead sits in a queue. Most teams should be at stage 2 by the time they hit 8–10 reps, and at stage 3 by the time they hit 15+. Surface handles attribute-based routing natively — leads get matched to the right rep based on real variables at the moment of capture, not assigned by rotation after the fact. If you've outgrown round-robin and your CRM's workflow builder can't keep up, that's the gap Surface was built to close. If more than 10% of your leads are getting manually reassigned after round-robin, you're ready for the upgrade. --- # How to Stop Doing Lead Ops Manually | Surface Labs URL: https://surface.thesurface.network/blog/how-to-stop-doing-lead-ops-manually Every week, someone on your team spends 3–5 hours doing lead ops work by hand. Downloading CSVs from third-party providers and uploading them to the CRM. Manually reassigning leads that round-robin sent to the wrong rep. Cleaning up spam submissions that triggered workflows. Checking whether the Zapier between your form tool and Salesforce is still running. Updating a routing spreadsheet when territories change. None of this is strategic work. None of it requires human judgment. And all of it could be automated — but it hasn't been, because the tools your team uses weren't built to handle it and nobody's had time to fix it. Here's what manual lead ops actually costs and how to eliminate it. Manual lead ops tasks are individually small — 10 minutes here, 20 minutes there. But they compound across the team and across the week. Task Who does it Time per week Why it's still manual CSV import from third-party lead providers Marketing ops 1–2 hours Provider sends leads via email or portal. No webhook or API integration. Manual lead reassignment Sales manager or ops 1–3 hours Round-robin routes leads to the wrong rep. Someone manually fixes it. Spam cleanup Marketing ops 30–60 min Spam submissions triggered workflows, created CRM records, burned enrichment credits. Someone has to delete them. Routing rule updates Rev ops or Salesforce admin 30–60 min Territory changes, new reps, product line changes. Routing rules don't update themselves. Integration monitoring Marketing ops or engineer 30–60 min Checking that Zapier, webhooks, and form-to-CRM syncs are still working. Fixing them when they break. Reporting and attribution Marketing ops 1–2 hours Pulling data from multiple systems, deduplicating, calculating conversion metrics in a spreadsheet. Total: 5–10 hours per week across the team. That's 250–500 hours per year — or roughly $15K–$50K in salary cost depending on who's doing it. And this doesn't include the cost of delays (leads sitting while someone manually processes them) or errors (wrong assignments, missed imports, broken integrations). Not everything should be automated at once. Prioritize by the combination of frequency, time cost, and impact on lead conversion. **Automate first: Lead intake and normalization.** Every lead source — forms, ads, third-party providers, events — should flow into your system automatically with consistent field formatting. No CSVs, no manual imports, no copy-paste. This eliminates the most repetitive work and ensures leads enter the funnel in real time instead of in batches. **Automate second: Routing.** Replace round-robin with attribute-based routing that evaluates territory, deal size, product interest, and availability at the moment of capture. This eliminates manual reassignment and gets leads to the right rep immediately. Routing rules should be editable in a UI — not locked in a Salesforce flow that requires an admin to change. **Automate third: First response.** The initial message to the lead — acknowledging their request, introducing the assigned rep, and providing a scheduling link — should fire automatically within 60 seconds. The rep follows up after, but the lead never waits in silence. **Automate fourth: Spam and quality filtering.** Multi-step forms with conditional logic eliminate most spam at capture. For the rest, automated validation — email verification, domain checks, duplicate detection — should filter junk before it enters the CRM or triggers workflows. **Automate fifth: Reporting.** If your lead ops system tracks the full journey from capture to meeting, reporting is a dashboard — not a weekly spreadsheet exercise. Speed-to-lead, routing accuracy, lead-to-meeting rate, and cost per meeting should update in real time. Not everything should be automated. Some tasks benefit from human judgment: Reviewing and adjusting qualification criteria based on conversion data. Refining routing rules as the sales team evolves. Investigating anomalies — a sudden drop in lead-to-meeting rate, a spike in a specific lead source, or a pattern of leads from one campaign converting unusually well. The goal isn't zero manual work. It's eliminating the manual work that's repetitive, time-consuming, and doesn't require judgment — so your team can spend their time on the work that does. Surface automates the entire lead ops flow — intake from every source, normalization, qualification, routing, instant response, and real-time reporting. The manual tasks in the table above are handled by default, not bolted on through middleware. If someone on your team spends every Monday morning cleaning up the mess from last week's lead ops, that's the problem Surface was built to eliminate. --- # How to Stop Losing Leads in Your Funnel | Surface Labs URL: https://surface.thesurface.network/blog/how-to-stop-losing-leads-in-your-funnel You're generating leads. They're entering your funnel. And somewhere between "filled out the form" and "talked to sales," a significant chunk of them vanish. Not because they weren't interested. Because your system dropped them. Most teams don't even know how many leads they're losing. They look at the top-of-funnel number and the bottom-of-funnel number and shrug at the gap in between. But that gap is where your pipeline lives. Or dies. It's rarely one catastrophic failure. It's a dozen small leaks that compound. Leak What happens What it costs you Form abandonment Someone starts your demo request and leaves halfway through. Most form tools treat this as if it never happened. No record. No follow-up. A warm lead, gone entirely. Spam polluting your CRM Junk submissions sit alongside real leads. Reps waste time sorting through disposable emails, test entries, and bot submissions. While they're dealing with junk, real leads age in the queue. No enrichment data Lead arrives with a name and email. No company data. No context. Rep has to research before they can act. Some leads never get researched. They sit until someone bulk-deletes the old ones. Wrong routing Lead gets assigned to the wrong rep. Territory rules are outdated. Round robin sends an enterprise lead to an SMB rep. Rep fumbles the conversation or manually reassigns. Another day of delay. Slow follow-up Rep gets notified but they're in meetings. They see the lead four hours later. Prospect has moved on. Lead marked "unresponsive." It wasn't unresponsive. It was late. Booking friction Rep sends a booking link. Prospect has to click it, find a time, book. Some do. Most don't. The lead quietly disappears. Each leak loses you 5–15% of your leads. Stack six of them together and you're losing more than half your pipeline between form fill and meeting booked. You fix them in order from the top of the funnel down. **Capture partial submissions.** If someone starts your form and leaves, save what they entered. A name and email is enough to trigger a follow-up. Surface captures drop-offs automatically and lets you build separate workflows for incomplete submissions. **Filter spam before it enters your CRM.** Don't let junk pollute your lead database in the first place. Real-time email validation, disposable domain detection, and content screening catch the garbage before it reaches a rep. Surface runs this during the form fill, not after. **Enrich in real time.** Every lead should arrive in your CRM with a complete profile. Company size, industry, revenue, tech stack, job title. If your reps are spending time researching leads, that's a leak you can plug with real-time enrichment. **Score and qualify automatically.** Don't make reps triage their own queue. AI scoring against your ICP means qualified leads get flagged and prioritized. Disqualified leads get filtered. The rep only sees leads worth their time. **Route to the right rep the first time.** Use enrichment data and form responses together to make the routing decision. Company size plus region plus use case. No generic round robin. No CRM workflow that's been wrong for three months. **Put the calendar in the form.** Don't send a booking link. Don't make the prospect wait. The right calendar shows up inside the form based on their responses. They book on the spot. The booking gap disappears. Pull 100 recent leads. Trace each one from form fill to outcome. Ask yourself: - How many started the form but didn't finish? - How many submissions were spam? - How many had complete data when the rep first saw them? - How many got routed to the right rep? - How many booked a meeting within 24 hours? You'll find the leaks fast. Most teams have two or three major ones they didn't know existed. Surface Labs was built to close these gaps. Capture, enrichment, scoring, routing, and scheduling in one system. No handoffs between tools. No leads falling through the cracks between your form tool and your CRM and your scheduling tool and your enrichment provider. If leads are disappearing between form fill and meeting booked, it's worth a look. --- # How to Stop Spam and Fake Form Submissions in HubSpot | Surface Labs URL: https://surface.thesurface.network/blog/how-to-stop-spam-and-fake-form-submissions-in-hubspot You open HubSpot on Monday morning and there are 40 new form submissions from the weekend. For about 3 seconds, that feels great. Then you start scrolling. Half the emails are @mailinator.com. A quarter have gibberish in the company name field. Two of them somehow triggered your enrichment tool and burned credits looking up "asdfasdf Inc." One got routed to a rep who already called the number and got a disconnected line. Spam submissions aren't just annoying. They're expensive. They inflate your lead counts, corrupt your reporting, waste enrichment and routing resources, and erode your sales team's trust in inbound leads. The rep who calls 3 fake leads in a row stops treating inbound with urgency — and that affects the real leads too. This is a bigger problem than most teams realize, and HubSpot's native tools don't fully solve it. Most teams think of spam as a nuisance — something to delete and move on. But in a system where form submissions trigger automated workflows, every fake lead has a real cost. What happens Why it matters Spam lead enters HubSpot as a contact Inflates your database, skews contact-level reporting, counts against your HubSpot contact tier pricing Enrichment fires on the fake lead Burns $0.20–$1.00+ per lookup on Clearbit, ZoomInfo, or Apollo — for a lead that doesn't exist Routing workflow assigns it to a rep Rep wastes time reviewing, calling, or disqualifying a fake lead. At scale, this is hours per week. Lead counts inflate CPL looks artificially low. "We got 400 leads this month" becomes "we got 250 real leads and 150 bots" — but nobody segments it that way Sales team loses trust After calling enough fake leads, reps start slow-playing all inbound. Response time creeps up across the board — including for real buyers. The last row is the most damaging. Spam doesn't just waste resources — it trains your team to ignore inbound. That behavioral shift costs more than the enrichment credits ever will. HubSpot has a few built-in tools to fight spam. They help, but they don't solve the problem. **CAPTCHA.** HubSpot offers reCAPTCHA on forms. It blocks the dumbest bots but doesn't stop form-filling services, manual spam, or sophisticated bots that bypass CAPTCHA. It also adds friction for real leads — every CAPTCHA challenge is a potential drop-off. **Honeypot fields.** Hidden fields that bots fill out but humans don't. HubSpot includes these by default. They catch basic bots but are ineffective against anything more advanced. **Blocked email domains.** You can block free email providers (gmail.com, yahoo.com) or known spam domains. This works for B2B forms where you want corporate emails only, but it's a blunt instrument — you'll also block legitimate leads who use personal email. **Submission limits.** You can limit how many times the same IP can submit a form. Helps with brute-force spam, doesn't help with distributed bot networks or manual spam. These tools reduce volume, but they don't eliminate the problem — and they don't address the downstream waste that happens when a spam lead slips through and triggers your workflows. The spam problem isn't a filtering problem. It's a capture design problem. Standard forms — name, email, company, submit — are trivially easy for bots to fill out. There's no friction, no logic, no branching. A bot can complete the form in milliseconds because the form doesn't ask the lead to think. **Multi-step forms with conditional logic are a structural spam filter.** When a form asks "What's your budget range?" and then branches to a different question based on the answer, and then asks "What's your timeline?" — bots can't navigate that. They don't understand conditional logic. They can't select coherent answers across branching paths. This isn't a CAPTCHA. It's not a honeypot. It's a form that requires intent — and intent is the one thing spam submissions don't have. The side benefit is that the same conditional logic that blocks spam also qualifies real leads. You're not adding friction for friction's sake. You're asking questions that help you route the lead to the right rep with the right context. The spam filtering is a byproduct of better form design. A standard HubSpot form: 4 fields, flat, no logic. Spam rate: 15–30% of submissions depending on traffic source. A multi-step form with conditional qualification: 4–6 questions, branching logic, real-time validation. Spam rate: under 2%. And every real lead that completes it arrives in HubSpot pre-qualified with budget, timeline, and use case data attached. The conversion rate on the multi-step form is typically comparable to or slightly lower than the flat form — but the lead quality is dramatically higher and the spam is nearly eliminated. When you factor in the saved enrichment spend, the recovered rep time, and the cleaner reporting, the multi-step form wins by a wide margin. Surface sits in front of HubSpot as your capture layer. Leads fill out a Surface form with conditional logic, real-time validation, and built-in qualification. Clean, qualified leads push into HubSpot automatically — spam never gets there. If your HubSpot database is full of fake contacts and your reps have stopped trusting inbound, the fix isn't better filtering inside HubSpot. It's better capture in front of it. That's what Surface was built to do. --- # How to Succeed as a Marketing Agency in the AI Era | Surface Labs URL: https://surface.thesurface.network/blog/how-to-succeed-as-a-marketing-agency-in-the-ai-era If you run a marketing agency in 2025, you've already felt the squeeze. Clients are asking why they need you to write copy when Claude does it for free. Prospects are building landing pages with AI-assisted tools and wondering what they'd pay an agency for. The services that used to justify your retainer are becoming commodities. This isn't a crisis — it's a forcing function. The agencies that adapt will be more profitable and more defensible than they were before AI. The ones that don't will lose clients to a $20/month subscription. Here's the playbook. The core shift: clients used to pay agencies for things (blog posts, emails, landing pages, ad creative). Now they need to pay agencies for results (more pipeline, lower cost per meeting, higher conversion rates). The things are commoditizing. The results aren't. This means reframing every client engagement around a business metric, not a production schedule. Old framing New framing "We'll produce 8 blog posts per month" "We'll increase organic lead volume by 40% over 6 months" "We'll manage your Google Ads" "We'll reduce your cost per qualified meeting by 30%" "We'll build 4 landing pages" "We'll increase your landing page-to-meeting rate from 2% to 5%" "We'll set up your email nurture" "We'll recover 25% of leads that currently go cold before a conversation" The left column competes with AI. The right column doesn't — because it requires diagnosis, strategy, implementation, and ongoing optimization that AI can't do autonomously. The highest-value service an agency can offer right now is lead operations — fixing the gap between "lead captured" and "meeting booked." Almost every B2B company between $5M and $100M has this problem, few have the internal resources to fix it, and the impact is immediately measurable. A lead ops practice includes four deliverables: **Funnel audit.** Map every lead source, trace 10–20 leads end-to-end, measure speed-to-lead, routing accuracy, and lead-to-meeting rate. Identify where leads are leaking. **Capture optimization.** Replace static forms with smart, multi-step forms that qualify leads at the point of capture. Implement conditional logic, abandoned form recovery, and contextual capture experiences. **Routing and response.** Configure attribute-based routing that matches leads to the right rep. Set up instant personalized response triggered at the moment of routing. Connect scheduling so leads can book in the same flow. **Ongoing optimization.** Monitor conversion metrics, run A/B tests on form design and routing logic, and refine based on data. This is the recurring engagement that keeps clients month after month. Each of these is technical enough that most marketing teams can't do it themselves, strategic enough that AI tools can't configure it automatically, and measurable enough that you can prove ROI in the first month. The agencies losing to AI are the ones competing with it on execution speed. The agencies winning are the ones using AI to do more per person. Use AI to generate first drafts of copy and creative — then apply your strategic judgment and client knowledge to refine them. Use AI to analyze campaign data and surface patterns — then make the strategic decisions about what to change. Use AI to build reporting dashboards faster — then spend the saved time on strategy and implementation. The formula: AI handles the 80% of execution that's repetitive. Your team handles the 20% that requires judgment, context, and client-specific knowledge. The result is higher output per person, higher margins, and more time spent on the work that clients can't get from a subscription. When you're selling outcomes, hourly pricing doesn't make sense. If you reduce a client's cost per meeting from $2,000 to $800, that's worth far more than 40 hours of agency time. Transition to value-based pricing: a monthly retainer tied to the scope of the infrastructure you manage, plus performance bonuses tied to measurable improvements. This aligns incentives — you make more when the client gets more — and it's harder for clients to comparison-shop against freelancers or AI tools. Surface is the platform that makes lead ops delivery scalable for agencies. Instead of custom-building capture, routing, and response infrastructure for each client from scratch, agencies deploy Surface across their portfolio — configuring each client's forms, qualification criteria, routing logic, and response in a single system. For agencies building a lead ops practice, Surface is the tool that turns a high-value consulting engagement into a repeatable, scalable service offering. Audit the funnel, deploy Surface, optimize monthly, prove ROI — then do it again for the next client. --- # How We Handle 40,000+ Cold Emails a Month Without Losing Our Minds | Surface Labs URL: https://surface.thesurface.network/blog/how-we-handle-40-000-cold-emails-a-month-without-losing-our-minds **The middle school version:** Imagine you send 40,000 letters to people you want to talk to. Some write back saying "yes, tell me more!" Others say "no thanks." And some just ask random questions. Now imagine a super-smart robot that reads every single reply, figures out who's actually interested, looks up info about them online, sends the hot leads to the right salesperson, and even writes follow-up messages — all in seconds. That's what Surface does for us. At 40,000 outbound emails per month, we generate a lot of replies. Good replies, bad replies, out-of-office replies, angry replies, confused replies, and everything in between. At this volume, having a human read and categorize every response is impossible. But treating them all the same — or worse, letting them pile up in an inbox — means missing the 3–5% that are genuinely interested buyers. Before Surface, our outbound replies went into a shared inbox. Someone would scan through them each morning, try to identify the interested ones, manually update the CRM, and forward hot leads to the right rep. It took 2–3 hours per day. Responses from overnight sat until the morning review. And the categorization was inconsistent — one person's "maybe interested" was another person's "not a fit." Every outbound reply now flows through Surface automatically. Here's the pipeline: **Step 1: Auto-tagging.** Surface reads every reply and classifies it into one of five categories: interested, not interested, out of office, wrong person, or question. The classification happens in seconds and is accurate enough that we only spot-check 10–15 per week for quality control. **Step 2: Enrichment.** For every reply tagged "interested," Surface immediately enriches the lead — company size, industry, revenue, tech stack, funding status. This data was available before, but it used to happen hours later after someone manually triggered it. Now it happens the moment the reply is classified. **Step 3: Qualification.** The enriched data gets evaluated against our ICP criteria. Does this company match our target segment? Is the contact a decision-maker? Is the company the right size? Leads that pass qualification get a score; leads that don't get tagged for nurture or deprioritized. **Step 4: Smart routing.** Qualified leads are routed to the right rep based on territory, deal size, and product interest — the same routing logic we use for inbound. The rep doesn't get a generic notification. They get the full context: the original email, the reply, enrichment data, qualification score, and the suggested next action. **Step 5: Automated follow-up.** Different reply types trigger different sequences. "Interested" replies get an immediate, personalized follow-up from the assigned rep. "Question" replies get an AI-drafted answer that the rep can review and send. "Not interested" replies get a graceful exit. "Out of office" replies get a scheduled follow-up for when the person returns. "Wrong person" replies trigger a lookup for the right contact at that company. Metric Before Surface After Surface Time to process daily replies 2–3 hours (manual) ~0 (automated) Average response to interested reply 4–6 hours Under 10 minutes Reply classification accuracy Inconsistent (human variation) 94% automated accuracy Interested replies that got lost ~15% (buried in volume) Under 2% Response-to-meeting conversion rate 8% 19% The biggest impact isn't time savings — it's the replies we used to miss. At 40,000 emails per month, even a 3% interested rate is 1,200 potential conversations. Losing 15% of those to slow processing or human error meant 180 opportunities per month slipping through the cracks. That's pipeline we were generating and then immediately losing. Volume outbound only works if the response handling is as automated as the sending. Most teams invest heavily in the send side — deliverability, personalization, sequence design — and then process replies manually. That's like building a highway that ends in a dirt road. The reply is the highest-intent signal in outbound. Someone who took the time to write back "tell me more" is warmer than almost any inbound lead from a content download. Treating that reply with the same speed and precision as a demo request is the unlock most outbound teams are missing. **See how Surface can turn your cold email chaos into a clean pipeline.** --- # Inbound Lead Generation: The Complete RevOps Playbook to Turn More Website Leads Into Pipeline | Surface Labs URL: https://surface.thesurface.network/blog/inbound-lead-generation Most B2B teams measure inbound success by lead volume. But the teams hitting pipeline targets measure something different: how many of those leads actually become meetings. The gap between "leads generated" and "pipeline created" is where most inbound programs fail—not because they lack traffic, but because leads leak out somewhere between the form submission and the sales conversation. This guide covers the complete system: attracting the right visitors, capturing more of their data, and converting submissions into booked demos through smarter routing and faster follow-up. Inbound lead generation is a strategy that attracts potential customers by creating valuable content—blogs, videos, ebooks, webinars—that solves their problems and draws them to your brand organically through channels like SEO and social media. Instead of interrupting prospects with cold outreach, you're letting them discover your solutions on their own terms. They find you, engage with something useful, and exchange their contact information for more value. For B2B teams, though, generating leads is only half the story. The real question is: how many of those leads actually become pipeline? That's where most programs hit a wall. They invest heavily in content and traffic, then watch leads disappear somewhere between the form submission and the sales conversation. ### What Counts as an Inbound Lead? An inbound lead is anyone who voluntarily engages with your brand and provides contact information. Think demo requests from your website, webinar registrations, ebook downloads, newsletter signups, or free trial users. The defining characteristic is intentThe defining characteristic is [intent](https://withsurface.com/blog/leveraging-purchase-intent-data-to-identify-high-quality-leads). These prospects came to you because something you created addressed a problem they're actively trying to solve. That's fundamentally different from a cold list. Inbound and outbound serve different purposes, and the best teams use both. Inbound captures existing demand—people already searching for solutions. Outbound creates demand by proactively reaching accounts that fit your ideal customer profile but haven't engaged yet. Factor Inbound Outbound **Intent** Prospect-initiated Sales-initiated **Targeting** Broad, content-driven Account and persona-specific **Cost structure** Higher upfront, compounds over time Linear cost per touch **Scalability** Scales with content and SEO investment Scales with headcount ### When Inbound Works Best Inbound excels when your category has established search volume, your ideal customers actively research solutions online, and you can create differentiated content. It struggles in new markets with low awareness or when targeting accounts that don't yet know they have a problem. ### Connecting Inbound Signals to Outbound Plays High-fit inbound leads who don't convert immediately become excellent outbound targets. When someone downloads a comparison guide but doesn't book a demo, that's a signal your SDR team can act on. Combining inbound intent data with outbound follow-up often outperforms either motion alone. Most guides stop at "create content and capture leads." But the teams that actually convert inbound traffic into pipeline treat it as an end-to-end system with six distinct stages. ### 1\. Attract the Right Traffic Traffic without intent is vanity. High-intent SEO targeting problem-aware and solution-aware keywords brings visitors who are closer to buying. Partner distribution, retargeting, and community presence all help—but only if they bring visitors who match your ideal customer profile. ### 2\. Convert Clicks Into Submissions Your form is where intent becomes actionable. Fewer fields typically means higher completion ratesYour form is where intent becomes actionable. [Fewer fields typically means higher completion rates](https://withsurface.com/blog/bad-forms-are-killing-your-conversions), though the right fields matter more than the count. Progressive profiling—collecting more data over multiple interactions—lets you balance conversion with qualification. Clear value exchange is essential here. Visitors complete forms when they understand exactly what they'll get in return. ### 3\. Capture More Than Just Completed Submissions Here's what most teams miss: a significant percentage of visitors start your form but never finish. That's pipeline walking out the door. Capturing partial responses—even just an email and company name—gives you a second chance to engage prospects who showed intent but hit friction. Teams using partial capture often recover 50% more emails from the same traffic. ### 4\. Enrich and Normalize Lead Data in Real Time Enrichment before routing changes everything. When you append firmographics, technographics, and company dataEnrichment before routing changes everything. When you [append firmographics, technographics, and company data](https://withsurface.com/product/lead-data-platform) the moment a lead submits, you can route based on actual fit—not just what someone typed into a form field. Real-time enrichment also catches duplicates and matches leads to existing accounts before they create CRM chaos. ### 5\. Qualify, Score, and Route Instantly Lead scoring combines fit (firmographics, ICP match) with intent (behavior, engagement depth). The goal isn't a perfect score—it's fast, accurate routing to the right owner. Common routing logic[Intelligent routing logic](https://withsurface.com/blog/how-intelligent-lead-segmentation-drives-personalized-marketing-campaigns) includes: - **Territory assignment:** Based on geography or company size - **Account ownership matching:** For existing customers or prospects already in your CRM - **Round-robin distribution:** For net-new leads without existing ownership - **Segment-specific queues:** Separating enterprise from SMB, or routing by product interest ### 6\. Follow Up Fast and Nurture What Isn't Ready Speed-to-lead is the highest-leverage conversion variable you control. Leads contacted within minutes convert at dramatically higher rates than those contacted hours or days later. For prospects who aren't ready to buy, automated nurture sequences keep your brand present until timing aligns. The tactics below work—but only when connected to the operational system above. Content that generates traffic but feeds a broken routing process just creates expensive noise. ### Content Marketing That Generates Qualified Leads Not all content is equal. Bottom-of-funnel content—comparison guides, use case pages, ROI calculators—attracts visitors closer to a buying decision. Top-of-funnel educational content builds audience but requires stronger nurture to convert. Match your CTAs to content intent. A visitor reading "how to evaluate X software" is ready for a demo offer. Someone reading "what is X" probably isn't. ### SEO for Inbound Lead Gen Topic clusters and pillar pages help you rank, but prioritize pages that attract buyers: comparison pages, integration pages, use case content, and templates. Lower volume, higher conversion. ### Webinars and Virtual Events Webinars remain one of the highest-intent lead sources in B2B. The registration form captures contact info, the content demonstrates expertise, and the follow-up sequence has natural urgency. Structure your post-webinar routing to prioritize attendees over registrants who didn't show—intent signals differ significantly between the two groups. ### Email Marketing for Nurturing and Conversion Email bridges the gap between first touch and sales-ready. Behavior-based triggers—someone revisits your pricing page, downloads a second asset, or attends a webinar—signal rising intent and can accelerate leads toward sales engagement. You can generate thousands of leads and still miss your pipeline targetsYou can generate [thousands of leads and still miss your pipeline targets](https://withsurface.com/blog/5-biggest-problems-with-inbound-marketing-leads). The gap is usually lead management—the operational layer between form submission and sales conversation. ### Lead Generation vs. Lead Management Lead generation creates volume. Lead management determines ROI. Generation asks "how do we get more leads?" Management asks "how do we convert the leads we have?" Teams that over-invest in generation while under-investing in management waste budget on leads that never become pipeline. ### MQL vs. SQL in an Inbound Motion Marketing Qualified Leads (MQLs) meet your fit and engagement thresholds. Sales Qualified Leads (SQLs) have been validated by sales as genuine opportunities. The handoff criteria between MQL and SQL—and the SLAs governing response time—often determine whether inbound works or fails. Common pitfalls include defining MQL based on activity alone without fit criteria, having no clear SLA for sales follow-up, and recycling SQLs back to marketing without feedback loops. ### How to Prevent Spam Leads Spam leads waste SDR time and pollute your data. Effective prevention includes email validation at submission, bot protection like honeypots or CAPTCHA, enrichment cross-checks to verify company data, and throttling suspicious patterns from the same IP or source. One note: blocking free email domains (gmail, yahoo) works for enterprise sales but kills conversion for SMB or product-led motions. Segment your spam rules by form and audience. The difference between responding in five minutes versus five hoursThe difference between [responding in five minutes versus five hours](https://withsurface.com/blog/is-sales-tired-of-getting-shitty-leads) is often the difference between a booked meeting and a lost opportunity. Yet most B2B teams average response times measured in hours or days. ### What's a Good Response Time? Minutes, not hours. The specific benchmark matters less than consistent improvement. Start by measuring your current median and P95 response times, then work backward from there. ### How to Improve Speed-to-Lead Without Hiring Automation handles what humans can't do at 2 AM or during back-to-back meetings: - **Instant acknowledgment emails** with scheduling links let leads self-book while intent is high - **Routing coverage rules** ensure leads always have an owner, even outside business hours - **Slack or email notifications** alert reps the moment a high-fit lead submits - **Calendar integration** removes the back-and-forth that delays first meetings Your stack determines what's operationally possible. Most B2B teams need coverage across four layers. - **Core systems:** CRM (Salesforce, HubSpot) for record management, marketing automation for nurture and scoring, analytics for attribution - **Data layer:** Enrichment tools append firmographics and technographics, dedupe logic prevents duplicate records, attribution tracking connects leads to sources - **Workflow automation:** Routing rules, conditional logic, SLAs, and handoff triggers—this is where most teams cobble together Zapier workflows that eventually break - **Forms:** Often overlooked, but forms are the front door to your entire lead operation. A form that captures partial submissions, enriches in real time, and routes intelligently eliminates downstream problems before they start[captures partial submissions, enriches in real time, and routes intelligently](https://withsurface.com/product/forms-and-workflows) eliminates downstream problems before they start Volume is a vanity metric. The metrics that matter connect to pipeline and revenue. - **Visitor-to-lead conversion rate** by page and source - **Lead-to-MQL rate** measuring fit and engagement qualification - **MQL-to-SQL rate** tracking sales acceptance - **SQL-to-opportunity rate** showing pipeline creation - **Speed-to-lead** including median and P95 response time - **SLA compliance** as percentage of leads contacted within target window - **Pipeline sourced by channel** using first-touch and multi-touch models[first-touch and multi-touch models](https://withsurface.com/blog/is-marketing-attribution-still-hard-to-measure) Avoid generic benchmarks. Your conversion rates depend on your ICP, price point, and sales motion. Compare cohorts within your own data—by source, by segment, by time period—to identify what's actually working. Most inbound programs lose leads between form submission and sales conversation. They invest heavily in content and traffic, then route leads to the wrong rep, respond too slowly, or let partial submissions disappear entirely. The teams that win treat inbound as an operational system: capture more data including partials, enrich instantly, route accurately, and follow up fast. That's where the conversion lift lives—not in more blog posts. **Ready to see where your inbound leads are leaking?** [Book a demo](https://withsurface.com/book-a-demo) and we'll walk through your current form-to-meeting flow, identify drop-off points, and show you how teams are getting 30%+ more demos from the same traffic. --- # Inbound Lead Management: The Modern Playbook for Speed-to-Lead, Enrichment, Scoring, and Routing | Surface Labs URL: https://surface.thesurface.network/blog/inbound-lead-management Inbound lead management is the system that captures, enriches, qualifies, and routes leads who reach out to your business—turning raw form submissions into booked meetings and pipeline. It's the operational layer between your marketing spend and your CRM, and it's where most B2B teams lose 20–40% of their potential revenue to slow follow-up, bad routing, and incomplete data. This playbook covers the end-to-end lifecycle: from capturing partial submissions to real-time enrichment, scoring, routing, and automated follow-up—with specific workflows you can implement this week. Inbound lead management is the process of capturing, enriching, qualifying, and converting potential customers who reach out to your business through forms, content downloads, demo requests, or other organic channels. Think of it as the operating system that sits between your marketing efforts and your CRM—the place where raw interest turns into qualified pipeline. This is different from inbound lead generation. Generation is about attracting visitors to your site. Management picks up the moment someone raises their hand. Once a visitor fills out a form, what happens next? How fast do you respond? Who owns the follow-up? That's lead management. ### Inbound leads vs. inbound prospects A lead is anyone who gives you their contact information. A prospect is a lead you've confirmed as a potential fit for your product. The distinction matters more than it might seem. When every form fill gets treated as "sales-ready," your reps drown in unqualified contacts. When every lead gets treated as "not ready yet," you lose high-intent buyers to competitors who moved faster. Getting this classification right is the foundation of everything else. Teams that respond to inbound leads within five minutesTeams that respond to inbound leads [within five minutes](https://withsurface.com/blog/is-sales-tired-of-getting-shitty-leads) are significantly more likely to qualify them compared to teams that wait 30 minutes or longer. Speed-to-lead isn't a vanity metric—it directly affects whether you win or lose the deal. Beyond speed, poor lead management creates what's called leakage: leads that enter your system but never get follow-up, get routed to the wrong person, or sit in queues until interest fades. Even a small leakage rate compounds into meaningful lost revenue over a quarter. ### Common symptoms your inbound system is broken You might recognize a few of these patterns: - **Response times measured in hours:** Leads submitted after 5pm sit untouched until the next morning. - **Leads stuck in limbo:** No clear owner, no follow-up activity, no accountability. - **Sales cherry-picking:** Reps work the leads that look easiest and ignore the rest. - **Volume without pipeline:** Marketing celebrates MQL numbers while sales complains about quality.[complains about quality](https://withsurface.com/blog/5-biggest-problems-with-inbound-marketing-leads). If any of this sounds familiar, the problem usually isn't lead generation. It's what happens after capture. Inbound lead management follows a six-stage lifecycle. Each stage has a specific job, and the gaps between stages are where leads get lost. ### Stage 1: Capture Capture includes every touchpoint where someone provides information—demo request forms, content downloadsCapture includes every touchpoint where someone provides information—[demo request forms, content downloads](https://withsurface.com/product/forms-and-workflows), webinar registrations, chatbot conversations, free trial signups. The goal is collecting enough data to take the next step without creating so much friction that visitors abandon the form.[visitors abandon the form](https://withsurface.com/blog/bad-forms-are-killing-your-conversions). Here's an often-missed opportunity: partial submissions. When someone starts a form but doesn't finish, you can still capture the fields they completed (like email and company name) and follow up appropriately. Teams using partial capture typically recover 30–50% more leads from the same traffic. ### Stage 2: Enrich Before you decide what happens to a lead, you want complete data. Real-time enrichment appends firmographic details (company size, industry, location) and contact details (job title, seniority) the moment a lead submits. This matters because routing decisions depend on data you often don't ask for on forms. If your routing logic uses company size but you don't collect it, you're either guessing or delaying while someone manually researches. ### Stage 3: Qualify and score Qualification answers two questions: Does this lead fit your ideal customer profile? And are they showing intent to buy? - **Fit scoring** evaluates firmographic match—right company size, industry, job title. - **Intent scoring**[**Intent scoring**](https://withsurface.com/blog/leveraging-purchase-intent-data-to-identify-high-quality-leads) evaluates behavior—visited pricing page, requested demo, downloaded multiple assets. A lead can be high-fit but low-intent (enterprise company browsing casually) or low-fit but high-intent (small startup ready to buy today). Your routing and follow-up can handle both scenarios differently. ### Stage 4: Route Routing assigns ownership and determines what happens next. The best routing is fast, fair, and auditable. Routing Pattern Best For Watch Out For Round-robin Equal distribution across reps Doesn't account for rep capacity Territory-based Geographic or vertical specialization Leads fall through when territories have gaps Named accounts ABM motions with existing relationships Requires clean account matching Hybrid Complex sales motions More rules to maintain The key is routing based on enriched data, not just what the lead self-reported. A lead who says they're "evaluating options" but works at a target account routes differently than the same response from a non-ICP company. ### Stage 5: Follow up and nurture Not every inbound lead is ready for a sales conversation. Your system benefits from two tracks: - **Immediate sales outreach:** High-fit, high-intent leads (demo requests from ICP companies) get a call or personalized email within minutes. - **Nurture sequences:** Lower-intent leads enter automated email sequences that provide value and resurface when engagement increases. The handoff between tracks can be automatic. When a nurtured lead visits your pricing page or requests a demo, they route to sales immediately—no waiting for a weekly list review. ### Stage 6: Measure and improve Closed-loop measurement connects your lead management process to revenue outcomes. Without it, you're optimizing blind. **Operational KPIs to track:** - **Speed-to-lead:** Median time from submission to first touch - **SLA adherence:** Percentage of leads contacted within your target window - **Lead leakage rate:** Percentage of leads with no follow-up activity after 48 hours **Funnel KPIs to track:** - **Lead-to-meeting rate:** Percentage of inbound leads that book a meeting - **Meeting-to-opportunity rate:** Percentage of meetings that create pipeline - **Source attribution:** Which channels and forms drive the most pipeline (not just leads) Here's a practical implementation sequence: ### 1\. Define lead stages and handoff criteria Start simple. You want clear definitions for when a lead moves from marketing ownership to sales ownership, and what qualifies a lead for immediate outreach versus nurture. Avoid overcomplicating with too many stages. "New → Qualified → Working → Converted/Disqualified" covers most B2B scenarios. ### 2\. Set SLAs for speed-to-lead Document your target response times and make them visible. A common starting point: first touch within 5 minutes for demo requests, within 4 hours for content downloads. Track adherence weekly. If you're missing SLAs consistently, the issue is usually routing complexity or rep capacity—not effort. ### 3\. Standardize required data for routing List every field your routing logic depends on. Then ensure those fields are either captured on the form or appended via enrichment before routing runs. If your routing uses company size but you don't collect or enrich it, leads will misroute or default to a catch-all queue. ### 4\. Build routing rules and exception paths Map out your routing logic explicitly: - **High-intent ICP leads:** Route to sales immediately - **High-intent non-ICP leads:** Route to nurture or SDR for qualification - **Existing customers:** Route to account owner or CSM - **Partners, competitors, students:** Route to disqualification or separate handling Document exception paths too. What happens when a lead matches no rules? Who owns the catch-all queue? ### 5\. Automate follow-up triggers Connect routing to action. When a lead is assigned, automatically create a task with a due date, trigger an email sequence, send a Slack notification to the owner, or book directly to calendar if using instant scheduling. The goal is eliminating the gapThe goal is [eliminating the gap](https://withsurface.com/blog/website-lead-conversion) between "lead assigned" and "lead contacted." ### 6\. Create a lead recovery workflow Build a specific workflow for leads that slip through: uncontacted after 24 hours, bounced emails, no-shows to scheduled meetings. These leads already showed intent—recovering even 20% of them adds meaningful pipeline. > **Tip:** Partial form submissions are a hidden recovery opportunity. If you capture email and company before abandonment, you can enrich and follow up with a helpful message. Teams using this approach often see 30%+ more leads from the same traffic. Most teams cobble together forms, CRM workflows, enrichment vendors, and routing tools with Zapier or native integrations. This works until it doesn't—usually when speed matters most or when you're debugging why a lead got lost. ### Minimum viable stack For early-stage teams: - **CRM** (HubSpot, Salesforce) for lead storage and basic workflows - **Forms** (native CRM forms or a dedicated tool) for capture - **Basic enrichment** (Clearbit, Apollo) for firmographic data - **Calendar scheduling** (Calendly, HubSpot meetings) for booking ### Scaling stack As volume grows, you'll likely want: - **Dedicated routing logic** that handles complex rules without brittle automation - **Real-time enrichment** that runs before routing, not after - **Unified lead data** that dedupes, tracks attribution, and connects to revenue - **Automated follow-up** that triggers sequences without manual intervention The patchwork problem is real. When your forms, enrichment, routing, and follow-up live in separate tools connected by Zapier, you lose speed, create data gaps, and spend ops cycles maintaining integrations instead of optimizing conversion. Modern lead data platforms like [Surface Labs](https://withsurface.com/)[lead data platforms](https://withsurface.com/product/lead-data-platform) like [Surface Labs](https://withsurface.com/) consolidate capture, enrichment, routing, and follow-up into one system—so leads move from form submission to sales outreach in seconds, not hours. ### What is the 5-minute rule for leads? The 5-minute rule refers to research showing that leads contacted within five minutes of submitting a form convert at significantly higher rates than leads contacted later. After 30 minutes, qualification rates drop dramatically. Speed is a conversion lever, not just a nice-to-have. ### How many touchpoints does it take to convert an inbound lead? It varies by deal complexity, but most B2B leads require 6–8 touches across multiple channels before converting to a meeting. High-intent leads (demo requests) may convert in 1–2 touches, while content downloaders often require sustained nurture. ### Can you automate inbound lead management completely? You can automate capture, enrichment, scoring, routing, and initial follow-up. What you can't automate well: discovery conversations, objection handling, and relationship building. The goal is automating operational work so humans can focus on conversations that actually close deals. ### Why do inbound leads go cold even when interest is high? Usually one of three reasons: slow response (interest fades), poor routing (wrong rep or no rep), or generic follow-up (doesn't acknowledge what the lead actually requested). Fixing operational gaps often matters more than generating more leads. **Want to see where your inbound leads are leaking?** Surface Labs helps B2B teams capture more leads (including partial submissions), enrich in real-time, and route to sales in seconds—not hours. [Book a Demo](https://withsurface.com/book-a-demo) --- # Inbound Marketing Automation: Workflows, Lead Scoring, Routing & ROI (B2B Playbook) | Surface Labs URL: https://surface.thesurface.network/blog/inbound-marketing-automation Most B2B teams automate email nurture and call it inbound marketing automation. Meanwhile, 40% of their demo requests go untouchedMost B2B teams automate email nurture and call it inbound marketing automation. Meanwhile, [40% of their demo requests go untouched](https://withsurface.com/blog/5-biggest-problems-with-inbound-marketing-leads) for more than 24 hours—and half of those leads never respond when someone finally reaches out. Inbound marketing automation is the system that captures, qualifies, routes, and follows up with leads who come to you, without manual work at every step. This playbook covers the end-to-end workflow from form submission to booked meeting, including the eight automations that have the biggest impact on pipeline. Inbound marketing automation uses software to handle repetitive tasks involved in capturing and nurturing leads who come to you—email sequences, lead scoring, data updates, and personalized content delivery based on user behavior. Instead of manually following up with every form submission or webinar registrant, automation handles the routine work so your team can focus on conversations that actually move deals forward. Here's what makes inbound automation different from general marketing automation: it's specifically designed for the leads already raising their hands. You're not blasting cold lists. You're systematically converting people who visited your pricing page, downloaded your guide, or requested a demo. ### Inbound marketing vs. marketing automation vs. inbound marketing automation Inbound marketing is the strategy—creating content and experiences that attract prospects to you rather than interrupting them with cold outreach. Marketing automation is the technology that executes tasks at scale, like sending emails or updating CRM records. Inbound marketing automation combines both. It's the operational system that captures inbound demand and converts it into pipeline through automated workflows, scoring, routing, and follow-up. ### Where it fits in the funnel Most teams automate top-of-funnel activities (content distribution, lead capture) and mid-funnel nurture sequences. However, the biggest leakage typically happens at the handoff between marketing and sales—when a demo request sits untouched for 48 hours, or when a high-intent prospect gets routed to the wrong rep.[handoff between marketing and sales](https://withsurface.com/blog/is-sales-tired-of-getting-shitty-leads)—when a demo request sits untouched for 48 hours, or when a high-intent prospect gets routed to the wrong rep. The conversion layer between "lead captured" and "meeting booked" is where automation delivers the highest ROI. Speed-to-lead, accurate routing, and timely follow-up directly determine whether inbound demand turns into pipeline or disappears. Understanding the end-to-end flow helps you spot where your current setup might be losing leads. Here's the typical lifecycle from first touch to booked meeting. ### Step 1: Capture Every inbound motion starts with a capture point—forms, chat widgets, calendar embedsEvery inbound motion starts with a capture point—[forms, chat widgets, calendar embeds](https://withsurface.com/product/forms-and-workflows), webinar registrations, or product signup flows. The goal is collecting enough information to qualify and route the lead without creating so much friction that visitors abandon. Two approaches increase capture volume significantly: - **Progressive profiling:** Asking for more data over multiple interactions rather than all at once - **Partial submission capture**[**Partial submission capture**](https://withsurface.com/blog/bad-forms-are-killing-your-conversions)**:** Saving responses even when forms aren't completed, so you can follow up with visitors who dropped off ### Step 2: Enrich Before scoring or routing anything, enrich the lead record with firmographic data (company size, industry, tech stack) and intent signals. Real-time enrichment prevents misroutes—you won't accidentally send an enterprise prospect to an SMB queue because they used a personal email address.[Real-time enrichment](https://withsurface.com/product/lead-data-platform) prevents misroutes—you won't accidentally send an enterprise prospect to an SMB queue because they used a personal email address. Enrichment also fills gaps the visitor didn't provide, which means you can reduce form fields while improving data quality. Many teams skip or delay enrichment, then wonder why their scoring and routing feel inaccurate. ### Step 3: Qualify Lead scoring[Lead scoring](https://docs.withsurface.com/leads/lead-score) assigns points based on fit (does this company match your ideal customer profile?) and intent (are they showing buying signals?). Simple models use rules—job title plus company size plus page visits. More sophisticated setups incorporate predictive scoring. The key is operationalizing your scores. A score that sits in a field but doesn't trigger any action is just data. Define thresholds that automatically move leads to the next stage or alert sales when someone crosses into "hot" territory. ### Step 4: Route Routing determines who owns the lead and how quickly they're contacted. Common approaches include: - **Round robin:** Distribute evenly across available reps - **Territory-based:** Assign by geography, company size, or industry - **Named accounts:** Override other rules for strategic accounts - **Fallback logic:** Reassign if the owner doesn't respond within your SLA Speed matters here more than most teams realize. Responding within 5 minutes versus 30 minutes can dramatically increase contact rates—the difference between catching someone while they're still thinking about your product versus reaching them after they've moved on. ### Step 5: Follow up Automated follow-up sequences ensure leads hear from you even when reps are busy or offline. The best sequences are multi-channel (email plus LinkedIn plus phone) and personalized based on the lead's behavior and enrichment data. AI-assisted follow-up[AI-assisted follow-up](https://withsurface.com/product/ai-workforce) can handle initial outreach and qualification questions, then escalate to humans when the conversation requires it. The guardrail: automated messages still need to feel relevant, not robotic. ### Step 6: Measure Attribution[Attribution](https://withsurface.com/blog/is-marketing-attribution-still-hard-to-measure) connects your automation workflows to revenue outcomes. You want visibility into which sources and campaigns generate pipeline (not just leads), where leads drop off in the funnel, how long each stage takes, and which reps convert at the highest rates. Without clean attribution, you're optimizing blind. Wire your workflows to update CRM fields and create reporting that ties inbound activity to closed-won revenue. When evaluating your current stack or considering new tools, focus on capabilities rather than specific vendors: Capability Why it matters Partial submission capture Recovers leads from form abandonment Real-time enrichment Enables accurate scoring and routing before human touch Flexible lead scoring Aligns marketing and sales on qualification criteria Configurable routing logic Handles territories, round robin, named accounts, and SLAs Multi-channel follow-up Reaches leads where they're most responsive End-to-end attribution Proves ROI and identifies optimization opportunities The common mistake is treating each capability as a separate tool that doesn't talk to the others. Forms in one system, enrichment in another, routing in a third, follow-up in a fourth—each handoff introduces latency and data loss. Here are the highest-impact workflows for B2B teams. Each includes the trigger, logic, and primary metric to track. ### 1\. Instant demo request routing **Trigger:** Demo form submission **Logic:** Enrich immediately → score for fit → route to available rep based on territory → send calendar link → start SLA timer → reassign if no response in 5 minutes **Metric:** Time from submission to meeting booked This is your highest-intent workflow. Every hour of delay costs you meetings. ### 2\. Form abandonment recovery **Trigger:** Partial form submission (email captured, form not completed) **Logic:** Save partial data → enrich → send contextual follow-up within 1 hour → route to SDR if high fit **Metric:** Recovered leads converted to meetings ### 3\. Pricing page intent escalation **Trigger:** Visitor views pricing page 2+ times or spends 60+ seconds **Logic:** Identify visitor (via enrichment or form history) → alert SDR in Slack → create task in CRM → trigger personalized outreach **Metric:** Speed-to-lead on high-intent visitors ### 4\. Content download qualification fork **Trigger:** Gated content download **Logic:** Enrich → segment by company size (enterprise vs. SMB) → enterprise leads get fast-tracked to SDR, SMB enters automated nurture **Metric:** MQL-to-SQL conversion rate by segment ### 5\. Webinar show/no-show branches **Trigger:** Webinar registration **Logic:** Sync attendance data → attendees who asked questions get immediate SDR outreach → other attendees enter post-event nurture → no-shows get replay sequence **Metric:** Post-event meeting rate ### 6\. Score-triggered sales acceptance **Trigger:** Lead score crosses threshold **Logic:** Create sales-accepted lead (SAL) → assign owner → notify via Slack → create follow-up task → if no action in 24 hours, escalate to manager **Metric:** SAL-to-opportunity conversion rate ### 7\. Lead-to-account matching **Trigger:** New lead creation **Logic:** Match to existing account by email domain → if match found, assign to account owner → if new account, apply standard routing → dedupe against existing contacts **Metric:** Duplicate rate reduction, rep acceptance rate ### 8\. AI-assisted follow-up with guardrails **Trigger:** New lead assigned to rep **Logic:** AI drafts personalized first touch using enrichment data → rep reviews and sends (or AI sends automatically for lower-priority leads) → AI handles initial replies → escalates to human when buying signals detected **Metric:** Reply rate, meetings booked per sequence > **Tip:** Start with workflows 1 and 2—demo routing and form abandonment recovery. Both address your highest-intent leads and biggest leakage points. You don't have to rebuild everything at once. Here's a phased approach that most teams can execute without disrupting current operations. **Days 1–30: Audit and define** Map your current lead flow from capture to meeting. Document lifecycle stages and definitions. Identify the biggest drop-off points. Align with sales on SLAs and routing rules. **Days 31–60: Build the conversion layer** Implement or upgrade forms with partial capture. Add real-time enrichment before routing. Configure routing logic for demo requests first. Set up SLA monitoring and alerts. **Days 61–90: Optimize** A/B test form fields and friction points. Calibrate scoring based on sales feedback. Build attribution reporting. Expand to secondary workflows like content downloads and webinars. Leadership wants to know: is this worth the investment? Here's how to frame it. **Leading indicators** tell you if the system is working: - Speed-to-lead (time from submission to first touch) - Form conversion rate - Partial submission recovery rate **Lagging indicators** connect to revenue: - Lead-to-meeting conversion rate - Sales acceptance rate - Pipeline influenced by inbound - Revenue attributed to inbound sources **Simple ROI model:** (Incremental meetings per month × meeting-to-opportunity rate × win rate × average deal size) minus automation costs equals net impact. If you're currently converting 10% of demo requests to meetings and automation lifts that to 13%, the math gets compelling quickly at any reasonable deal size. ### How long does implementation take? Most teams can implement core workflows (demo routing, enrichment, basic scoring) in 2–4 weeks. Full optimization including attribution and secondary workflows typically takes 60–90 days. ### Which platforms work for inbound marketing automation? HubSpot, Marketo, Pardot, and ActiveCampaign are common starting points. The gap is usually in the conversion layer—routing, enrichment, and speed-to-lead—which often requires additional tools or a platform that specializes in that handoff. ### Can small teams manage this effectively? Yes—automation actually benefits smaller teams more because it eliminates manual work that would otherwise require headcount. Start with 2–3 high-impact workflows rather than trying to automate everything at once. ### What's the difference between lead scoring and lead routing? Scoring determines lead quality (fit plus intent). Routing determines ownership (who works the lead). Scoring informs routing—high scores might skip the SDR queue and go directly to AEs—but they're separate functions in your workflow. The biggest gains in inbound marketing automation come from fixing the conversion layer: capturing more leads (including partials), enriching before routing, assigning instantly, and following up while intent is hot. Start with your demo request flow. Measure speed-to-lead and lead-to-meeting rate. Then expand to recovery workflows and secondary capture points. **Ready to see where your inbound funnel is leaking?** [Book a teardown](https://withsurface.com/book-a-demo) and we'll map your current flow, identify drop-off points, and show you where automation will have the biggest impact. --- # Inbound Marketing Tools (2025): Categories, Stack Examples, ROI Benchmarks, and Implementation Tips | Surface Labs URL: https://surface.thesurface.network/blog/inbound-marketing-tools Most B2B teams spend 80% of their tool budget on attracting traffic and 20% on converting it—then wonder why pipeline doesn't scale with ad spend. The real leverage is in the conversion layer: forms, enrichment, routing, and speed-to-lead. This guide breaks down the nine categories of inbound marketing tools, shows you how they connect into a working stack, and gives you benchmarks and timelines to prioritize what actually moves pipeline. Inbound marketing tools help you attract, engage, and convert customers through valuable content rather than interruptive ads. The category spans CRM and automation platforms like HubSpot and Salesforce, SEO tools like Semrush and Ahrefs, email marketing platforms like Mailchimp and Klaviyo, social media schedulers like Buffer and Hootsuite, and analytics tools like Google Analytics and Hotjar. Together, they streamline blogging, lead capture, email nurturing, social scheduling, and performance tracking—often integrating to give you a unified view of the customer journey. The distinction matters: inbound tools pull prospects toward you with helpful resources, while outbound tools push messages to cold audiences. When you build the right inbound stack, you create a system that compounds over time. Each piece of content, each optimized form, each automated workflow adds to your pipeline without requiring proportional increases in ad spend. The inbound framework breaks into four stages: Attract, Convert, Close, and Delight. Each stage calls for different tools, and knowing where your gaps are helps you prioritize what to buy first. ### Attract This is where you bring strangers to your site through SEO, content marketing, and social distribution. Tools like Semrush, Ahrefs, and WordPress power this stage—helping you research keywords, create content, and get found organically. Without consistent content production, your attract stage starves. ### Convert Once visitors arrive, you capture their information. This is the conversion layer: forms, landing pages, and lead capture tools that turn anonymous traffic into known contacts. It's also where most B2B teams leak the most pipeline. Form abandonment rates often exceed 70%It's also where most B2B teams leak the most pipeline. [Form abandonment rates often exceed 70%](https://withsurface.com/blog/bad-forms-are-killing-your-conversions), which means the majority of interested visitors leave without giving you a way to follow up. ### Close With leads in hand, you route them to sales, nurture them with email sequences, and track their journey through your CRM. HubSpot, Salesforce, and marketing automation platforms handle the handoff from marketing to sales. The speed of that handoff—often called speed-to-lead—directly impacts whether leads convert to meetings. ### Delight After the sale, customer marketing and lifecycle messaging keep customers engaged and drive expansion revenue. This stage often gets neglected, but it's where referrals and upsells originate. Not every team needs every category. The trick is knowing which tools drive pipeline fastest for your specific situation—and which ones can wait. ### All-in-one inbound platforms Platforms like HubSpot and Salesforce Marketing Cloud bundle CRM, automation, content management, and analytics into one system. They reduce integration complexity, though they can become expensive as you scale. Some teams outgrow native capabilities in specific areas and add specialized tools later. ### CRM and lead management Your CRM is the system of record for every lead and customer interaction. Whether you choose HubSpot CRM, Salesforce, or Pipedrive, the goal is the same: maintain clean, enriched contact data that sales can actually act on. ### Forms and lead capture This is the conversion layer between your traffic and your pipeline. Native form builders in HubSpot or Marketo work for basic use cases. Teams focused on conversion optimization often graduate to specialized tools that capture partial submissions, enrich contacts in real-time, and route leads instantly. > **Tip:** Form abandonment is one of the biggest sources of invisible lead loss. If a visitor starts your form but doesn't finish, that signal is usually lost forever—unless you're capturing partial responses. ### Marketing automation and email nurturing ActiveCampaign, Mailchimp, Klaviyo, and similar platforms handle drip campaigns, behavioral triggers, and lifecycle messaging. The key metric here is engagement-to-conversion rate, not just open rates. ### Content creation and workflow WordPress, Webflow, and Canva power the content engine. Editorial workflow tools like Notion or Asana keep production on track. ### SEO and content optimization Semrush, Ahrefs, and Clearscope help you find keywords, analyze competitors, and optimize content for search. They inform what to create—but they don't create pipeline directly. ### Analytics, attribution, and reporting Google Analytics 4, Hotjar, and dedicated attribution platforms show you what's working. The challenge is connecting marketing activity to revenue, not just traffic or leads. ### Lead enrichment, intent, and qualification ZoomInfo, Clearbit, and 6sense add firmographic and intent dataZoomInfo, Clearbit, and 6sense add firmographic and [intent data](https://withsurface.com/blog/leveraging-purchase-intent-data-to-identify-high-quality-leads) to your leads. Enrichment before routing means sales gets context instantly—no manual research required. ### Project management and ops automation Zapier, Make, and Notion keep workflows running. They connect your stack, though they can create brittle dependencies if you're not careful about maintenance. Understanding the data flow between tools matters more than picking the "best" individual platform. Here's the typical path a lead takes: **Website → Form → Enrichment → CRM → Routing → Sequences → Reporting** Each handoff is a potential failure point: - **Form → CRM:** Missing fields or no enrichment means sales lacks context - **CRM → Routing:** Manual assignment creates delays and slow speed-to-lead - **Routing → Sequences:** Wrong owner or no SLA means leads go cold - **Sequences → Reporting:** Broken attribution makes it impossible to prove ROI When you evaluate new tools, ask: "How does this integrate with what I already have, and where does data break?" Your ideal stack depends on your team size, inbound volume, and sales motion complexity. ### Starter stack for small teams Focus on capture, basic automation, and simple reporting. A typical setup might include: - **CRM:** HubSpot Free or Pipedrive - **Forms:** Native HubSpot forms or a conversion-focused alternative - **Email:** HubSpot or Mailchimp - **Analytics:** Google Analytics 4 At this stage, simplicity beats sophistication. Get the fundamentals working before adding complexity. ### Scaling stack for growing teams As inbound volume increases and you add SDRs, enrichment, routing, and speed-to-lead become critical. You might add:[enrichment, routing, and speed-to-lead](https://withsurface.com/blog/how-intelligent-lead-segmentation-drives-personalized-marketing-campaigns) become critical. You might add: - **Enrichment:** Clearbit or Apollo - **Routing:** Automated assignment rules with SLA tracking - **Attribution:** Multi-touch attribution tooling The goal is reducing time-to-first-touch and ensuring leads reach the right rep instantly. ### Advanced stack for enterprise teams Multiple segments, regions, and routing rules require governance and attribution rigor. You're likely running: - **CRM:** Salesforce with custom objects - **Automation:** Marketo or Pardot - **Enrichment:** ZoomInfo or 6sense - **Attribution:** Dedicated revenue attribution platform At this stage, the ops burden is real. Teams often spend more time maintaining integrations than optimizing conversions. [Book a demo](https://withsurface.com/book-a-demo) to see how Surface Labs reduces stack complexity while improving conversion rates. Adding tools is easy. Maintaining them is hard. Before you buy, consider a few questions: - **Where are you leaking conversions today?** Start with the biggest gap, not the shiniest feature. - **What integrations are non-negotiable?** If a tool doesn't connect to your CRM cleanly, it's probably not worth the headache. - **Who owns implementation and ongoing maintenance?** Tools without owners become technical debt. - **How will you measure success?** Define the metric before you buy. The best stacks are intentionally simple. Every tool earns its place by directly impacting pipeline or reducing ops burden. Inbound tool costs vary wildly—from free tiers to six-figure enterprise contracts. What matters is return on investment, not absolute cost. **ROI levers that matter most in B2B inbound:** - **Form conversion rate:** A 30% lift here compounds across all your traffic - **Lead-to-meeting rate:** The percentage of leads that become booked demos - **Speed-to-lead:** Responding within 5 minutes vs. 30 minutes can double your connection rate - **MQL → SQL conversion:** How many marketing-qualified leads become sales-qualified Here's a simple way to think about ROI: if you're spending $50,000/month on paid acquisition and your form converts at 3%, improving to 4% is equivalent to $16,000/month in additional traffic value—without increasing ad spend. You don't need a six-month project to see results. Here's what good looks like at different milestones. ### Week one and two Focus on quick wins: fix obvious form friction, set up instant lead alerts, establish response SLAs. Teams using conversion-focused form tools often see measurable lift within two weeks. ### Thirty days Add enrichment to your lead flow, build basic automation sequences, and implement first-touch attribution. By now, you have baseline metrics to compare against. ### Ninety days Refine routing rules, implement lifecycle reporting, and establish an optimization loop. At this point, you're iterating based on data rather than guessing. **Common pitfalls to avoid:** - Launching without defining success metrics - Over-engineering routing rules before you have volume - Skipping the CRM integration testing phase Inbound marketing tools don't exist in isolation—they're part of a broader revenue operations system that spans marketing, sales, and customer success.[broader revenue operations system](https://withsurface.com/blog/how-to-build-a-modern-gtm-stack-in-2025) that spans marketing, sales, and customer success. The handoff problem is real: marketing generates "leads," but sales often finds them unactionableThe handoff problem is real: marketing generates "leads," but [sales often finds them unactionable](https://withsurface.com/blog/5-biggest-problems-with-inbound-marketing-leads) due to missing data, poor qualification, or slow routing. Fixing this requires treating forms, enrichment, routing, and follow-up as one connected workflow rather than separate tools. Speed-to-lead is an ops problem, not just a sales problem. If your stack can't route a qualified lead to the right rep within minutes, you're losing deals to competitors who can. Closed-loop reporting connects source to pipeline to revenue. Without it, you can't prove which channels and campaigns actually drive business—and you can't optimize what you can't measure. ### How long does it take to implement an inbound marketing tool stack? Basic implementations take two to four weeks. Complex enterprise rollouts with custom integrations can take three to six months. The key variable is integration complexity and internal alignment, not the tools themselves. ### What is the minimum budget for effective inbound marketing tools? You can start with free tiers from HubSpot, Google Analytics, and Mailchimp. Meaningful paid stacks typically start around $500-1,000/month for small teams and scale to $5,000-20,000/month for mid-market companies with multiple tools. ### Do I need an all-in-one platform or best-of-breed tools? It depends on your team's ops capacity. All-in-one platforms reduce integration burden but may underperform in specific areas. Best-of-breed stacks offer more power but require more maintenance. Most scaling teams land somewhere in between. ### How can I reduce form abandonment and capture more leads? Multi-step forms typically outperform single-page forms[Multi-step forms typically outperform single-page forms](https://withsurface.com/blog/website-lead-conversion). Capturing partial submissions—even when visitors don't complete the form—can recover a significant portion of otherwise lost leads. Real-time enrichment reduces the number of fields you ask for, which also improves completion rates. The best inbound marketing stacks aren't defined by which tools you buy—they're defined by how well those tools work together to turn traffic into pipeline. Start by identifying where you're leaking conversions today, then fix the capture-to-routing flow before adding more top-of-funnel tools. Most teams underinvest in the conversion layer: forms, enrichment, routing, and speed-to-lead. That's where the highest-leverage improvements typically live. [Book a demo](https://withsurface.com/book-a-demo) to see how Surface Labs helps B2B teams capture more leads and route them to sales in seconds—not hours. --- # June 1: This week in Marketing is Email and AI Search Visibility | Surface Labs URL: https://surface.thesurface.network/blog/june-1-this-week-in-marketing A few years ago, marketers talked about email like it was furniture. Necessary, old, useful, not especially exciting, and usually dragged into the conversation only when someone needed a nurture sequence, a webinar invite, a product update, or a quarterly newsletter that everyone agreed should exist and very few people wanted to write. Now, after watching every surface of the internet get lacquered in AI-generated posts, AI-generated comments, AI-generated summaries, AI-generated listicles, and AI-generated “thought leadership” that appears to have been assembled by a microwave with a LinkedIn account, email suddenly looks stranger and more valuable than people gave it credit for. Plenty of people are starting to call email the last frontier that AI has forgotten about. I do not think that is exactly right, because AI is already inside email production, personalization, segmentation, lifecycle workflows, inbox summaries, and sales outreach. The better point is that email remains one of the few marketing channels where the brand still appears inside a personally governed space. A subject line in the inbox is not just a conversion attempt. It is a small act of repetition. The sender name, the headline, the cadence, the usefulness, the restraint, and the tone all become part of how someone remembers you. That matters more than people want to admit. A careful email program can reinforce brand identity even when the recipient never clicks. A reader may see the notification, register the name, skim the subject line, open one out of every four sends, and still develop a durable sense of what the company notices, what it cares about, and whether it sounds like a real organization. That kind of ambient brand memory is worth a lot more than 3 million AI-generated slop posts on LinkedIn that all start with the same grievance, land on the same conclusion, and disappear into the feed like confetti in a parking lot. Email is perhaps the most honest zero-click marketing channel because marketers have always known the click is only part of the value. The inbox gives companies a way to show up repeatedly without renting attention from a feed every time. Strong email does not need to cosplay as an algorithmic spectacle. It needs to be useful, recognizable, paced well, written by someone with enough taste to know when to stop, and connected to a broader content system that gives people somewhere meaningful to go when they finally decide the moment is right. This week’s marketing conversation should begin with email because the retrieval era is making owned relationships more important, not less. Google has talked publicly about Personal Intelligence in AI Mode, where eligible users can opt in to connect personal context from Gmail and Google Photos to receive more tailored AI Mode responses. iPullRank also published a May 2026 experiment suggesting that, inside an opted-in Personal Intelligence context, seeded brand signals in personal data sources could influence which brands appeared in recommendation-style AI Mode answers. That finding should not send marketers sprinting toward some grim future where every lifecycle email becomes a manipulation object. Good lord, please no. What it should do is remind teams that brand memory does not live only on the public web. It lives in inboxes, receipts, onboarding messages, product updates, nurture sequences, help content, sales follow-ups, event reminders, customer newsletters, and every other owned touchpoint where a buyer has encountered the company before they ask an AI system for a recommendation. This is where the zero-click value of email becomes operational. A buyer who has seen your company explain a category clearly for six months may not remember every email. They may not click every link. They may not convert after the third nurture send like some exhausted HubSpot diagram from 2018. But they may remember that your brand consistently explained the problem better than the alternatives, and in a world where AI systems increasingly summarize, recommend, and personalize, that repeated familiarity becomes part of the buyer’s decision environment. Surface Labs is useful in this conversation because [Surface Labs helps B2B teams capture, qualify, route, recover, and nurture inbound leads](https://withsurface.com/product), which is exactly where the content conversation has to go after the pageview. A company can publish a brilliant article, earn AI citations, run paid campaigns, and build a beautiful content cluster, then still lose the buyer if the conversion path, lead routing, email recovery, and lifecycle follow-up feel generic or slow. Retrieval-era marketing does not end when someone finds you. It begins the moment they give you permission to keep showing up. Google’s May 2026 guidance on optimizing for generative AI features in Search gave marketers something useful: permission to stop treating every AI search acronym like a new religion. Google says teams should focus on useful, unique content, crawlable pages, technical accessibility, strong media, and the same basic search foundations that help Google understand and retrieve pages. In practical terms, Google did not tell marketers to build an entirely separate swamp of machine-only content for AI Overviews and AI Mode. That does not mean AI visibility work is fake. It means the strongest version of AI visibility is probably less glamorous than the hype cycle promised. Marketers still need to understand prompt families, source inclusion, citation behavior, entity mentions, freshness, fan-out questions, and platform-specific source mixes. Teams should still measure AI surfaces directly when buyers use those surfaces to research vendors or categories. What they should not do is take “GEO” as permission to publish thin pages that are useful to no one except a dashboard trying to justify itself. This is the same content strategy lesson that keeps returning under new costumes. Marketers need to publish consistently, but they cannot treat volume as the whole strategy. They need templates, but they cannot confuse a template with thinking. They need SEO structure, but they cannot make the page feel like it was written by someone trapped inside a keyword tool. They need AI acceleration, but they still need human judgment, expert perspective, source discipline, and enough editorial care to make a skeptical reader keep going. A better way to frame the work is this: every strategic page should become a citable evidence asset. That page should answer a real question, show who the answer is for, explain tradeoffs, include sources where claims need support, connect to a next step, and sit inside a clean path across the site. The page should be legible to crawlers, useful to AI systems, and worth reading by the person whose budget, reputation, or quarterly target depends on making the right decision. The biggest shift in this week’s research slate is that rankings no longer explain the whole visibility field. Classic search position still matters, and anyone saying SEO is dead should probably be forced to spend one afternoon inside Google Search Console before being allowed near a microphone again. Still, AI systems often cite, summarize, and recommend from source pools that do not map neatly to the old blue-link SERP. This changes the practical work for marketers. Teams now need to ask whether their brand appears in the answer set, whether their owned pages are cited, whether third-party sources support their claims, whether competitors dominate the comparison layer, whether video or community surfaces shape the system’s understanding, and whether cited pages are fresh enough to deserve trust. Visibility becomes less about one page winning one keyword and more about the brand earning enough reliable presence across the retrieval map. A useful AI visibility program should therefore measure citations, mentions, source mix, prompt families, freshness lag, off-site support, and business relevance. A less useful program will produce screenshots of five prompts, call it a benchmark, and sell panic back to the client in a prettier font. The difference is method. Teams need to separate what is known from what is inferred, track uncertainty, compare platforms carefully, and connect visibility signals to qualified traffic, sales conversations, branded search, pipeline influence, and customer language. This is also why email returns to the center. When marketers think about AI visibility only as public-page optimization, they miss the buyer’s personal context. A serious brand presence includes the owned site, the newsletter, the nurture sequence, the webinar recap, the product update, the customer story, the founder’s point of view, the support documentation, the comparison page, and the third-party conversation happening without your permission. AI search makes the whole system more visible because weak connections now have more places to break. Google and OpenAI both moved paid media further into AI-native discovery this year. Google has been expanding ad formats around AI Mode, AI Overviews, Shopping, AI Max, and answer-style search experiences. OpenAI has also opened new ways for advertisers to buy ChatGPT ads, while publicly framing ads as separate from organic answers and governed by trust, privacy, and user-control principles. Marketers should care about this even if they are not rushing to buy answer-layer ads tomorrow morning. The paid search unit is no longer guaranteed to live beside a query in the old familiar way. Increasingly, platforms want to answer, compare, recommend, personalize, and sometimes transact inside the same surface where the user discovers the option. That means performance marketers will need more than keyword lists and landing pages assembled under duress. Answer-layer ads will reward clean feeds, current product data, strong claims, proof-backed landing pages, review hygiene, pricing clarity where appropriate, comparison assets, creative variations, and measurement plans that account for assisted behavior. A weak product page cannot be rescued forever by clever bidding. A thin comparison page will look especially thin when a system places it next to richer evidence. A generic nurture program will feel more generic when buyers have already been trained to expect personalized summaries everywhere else. This does not mean every company needs to behave like an ecommerce marketplace. B2B teams still sell through trust, timing, committee dynamics, category education, and proof. But the operational lesson transfers cleanly: paid media, product marketing, content strategy, and lifecycle messaging need to share the same evidence base. If marketing claims one thing, the landing page says another, sales follows up with something vaguer, and email nurture drifts into soft-focus brand poetry with no operational value, the buyer will feel the seams. Bing’s AI Performance reporting in Webmaster Tools is one of the more useful signals in this broader shift because it gives site owners a direct way to see AI citations across supported Microsoft AI experiences. Marketers should not treat that as a complete view of AI visibility, but it does mark a meaningful change in what search platforms may be willing to report. Total citations, average cited pages, grounding queries, page-level citation activity, and trends over time give teams another layer beyond rankings and clicks. The danger is obvious. Marketing teams can turn any metric into a vanity metric if they stare at it long enough and detach it from business context. Citation counts do not automatically prove revenue impact. Mentions do not automatically prove trust. AI visibility does not automatically prove demand. A page can be cited for the wrong reason, surfaced to the wrong audience, or included in an answer that produces no meaningful business action. A better dashboard would combine classic search performance, AI citation activity, source mix, branded demand, email engagement, lifecycle movement, assisted conversion, sales feedback, and qualitative buyer language. It would also include caveats. Which platform produced the signal? Which prompt family? Which date range? Which geography? Which account context? Which source types? How stable was the result across repeated tests? Which findings are strong enough to act on, and which are directional enough to watch? This is where [Surface’s broader marketing operations frame](https://withsurface.com/) fits the moment. Teams do not need more charts for the dashboard museum. They need a system that shows which forms, pages, sources, campaigns, follow-ups, and lead paths actually move buyers toward a qualified conversation. The retrieval era adds new visibility surfaces, but the old business question remains wonderfully stubborn: did the work help the right person take the right next step? Start with email because email is where owned attention becomes memory. Review your sender names, subject lines, newsletter cadence, lifecycle sequences, onboarding emails, event follow-ups, and re-engagement campaigns. Ask whether a recipient who never clicks would still understand what your company believes, what problem you solve, and why you are worth remembering. If the answer is no, your email program is probably functioning as a delivery mechanism rather than a brand system. Next, audit five strategic pages for citable usefulness. Pick a core landing page, a comparison page, a product or service page, a high-intent blog, and a customer proof page. Ask whether each page gives a human reader and a retrieval system enough context to trust the answer. Look for stale claims, missing sources, vague differentiators, weak internal links, unsupported superlatives, buried CTAs, and places where a buyer would need a salesperson to explain what the page should have explained. Then connect the content path to the lead path. A blog should know which page it supports. A landing page should know which proof it depends on. A conversion form should know what kind of buyer it is capturing. A routing system should know which team should follow up. A nurture sequence should know what the buyer has already seen and what they need next. [Surface’s product system](https://withsurface.com/product) matters here because inbound conversion has become a continuation of content strategy, not a separate operational chore. Finally, build your retrieval-era scorecard with humility. Track organic rankings, AI citations, brand mentions, source diversity, email engagement, lead quality, assisted pipeline, and sales feedback, but resist the urge to turn early AI visibility data into fake precision. The marketers who win this phase will be the ones who can measure more without pretending every new number deserves executive certainty. Email is not the forgotten channel. It is the channel many teams forgot how to respect. A good email program gives buyers a repeated, owned, low-friction encounter with the brand. A good content program gives those buyers a path from question to confidence. A good AI visibility program makes the company easier for retrieval systems to find, cite, and understand. A good paid media program makes sure product evidence can survive inside answer-layer environments. A good measurement program tells the truth about what is known, what is inferred, and what still needs to be tested. The boring version of the future is probably the correct one. Marketers need cleaner systems, better pages, stronger sources, more useful emails, clearer paths, and more honest measurement. AI can help with all of that, but only if people use the tools to increase judgment rather than avoid it. A slew of personally crafted emails and email nurture campaigns will do more for brand memory than a landfill of AI-generated posts because memory requires recurrence, specificity, and trust. People remember brands that keep showing up with something useful to say. They forget brands that sound like everyone else at impossible scale. This week in marketing, the inbox looks less like a relic and more like an operating system for attention. Treat it accordingly. --- # This Week's Marketing: The New Brand Measurement Layer | Surface Labs URL: https://surface.thesurface.network/blog/june-21-26-the-new-brand-measurement-layer A CMO opens the Monday dashboard and asks a question that sounds simple enough: “Are we showing up in AI search?” The SEO lead has one answer. Some pages are being cited. Some prompts mention the brand. Some competitors appear more often. The analytics lead has another answer. GA4 now shows an AI Assistant channel for traffic from tools like ChatGPT, Gemini, and Claude. The paid media lead has a third answer. Google is moving ads into AI Mode and AI Overviews, but the reporting will not give a clean AI-only placement breakdown in the way everyone wants. RevOps has the least romantic answer: “A few of these leads look good, but we do not know whether AI exposure helped create them.” That is the week in one room. Marketers are not waiting for AI search to become real anymore. They are waiting for it to become accountable. Over the last month, Google introduced dedicated [Search Generative AI performance reports in Search Console](https://developers.google.com/search/blog/2026/06/gen-ai-performance-reports), GA4 added a native [AI Assistant traffic channel](https://support.google.com/analytics/answer/9164320?hl=en), Google announced new [AI Search controls and insights for website owners](https://blog.google/products-and-platforms/products/search/new-controls-website-owners/), and paid media teams got another round of AI-era Search ad updates from Google Marketing Live. The practical conclusion is uncomfortable but useful: brand visibility is becoming measurable before it becomes cleanly measurable. For years, marketers could survive with a familiar stack of questions. Did the page rank? Did the ad click? Did the lead convert? Did the sales team accept the opportunity? Plenty of arguments happened inside that model, but the basic chain was legible. Discovery created traffic. Traffic created leads. Leads created pipeline. Pipeline created revenue. AI search interrupts that story because it adds invisible and semi-visible events before the click. A buyer may ask an assistant for a shortlist. The assistant may retrieve a page but not cite it. It may cite a page but summarize the answer so completely that no click happens. It may mention a brand because that brand appears across third-party sources. It may recommend a vendor, after which the buyer searches the brand name on Google, visits the site directly, asks a colleague, or shows up later through paid search. None of that fits neatly into last-click attribution. Google’s GA4 update helps because it gives teams a default AI Assistant channel for traffic from tools like ChatGPT, Gemini, Claude, and similar assistants. That does not solve upstream exposure, but it does stop one common failure: treating AI assistant visits as miscellaneous referral noise. Search Console’s generative AI reports help from the other side by exposing impressions, pages, countries, devices, and dates for generative AI features in Search. That still does not tell you everything a buyer saw, believed, or acted on, but it creates a platform-native visibility signal. Teams building [lead journey tracking](https://withsurface.com/blog/lead-user-journey) now need to add a layer before the visible visit. The question is no longer only “which channel drove this session?” It is also “which AI-mediated exposures may have shaped the buyer’s shortlist before the session existed?” The mistake will be naming one new number “AI visibility” and treating it like truth. AI visibility is not a single thing. It is a chain of states. A page can rank without being cited. A page can be retrieved without being cited. A brand can be mentioned without a source link. A source can be cited without the brand being recommended. A brand can be recommended without a click. A recommendation can create later branded search. A branded search can convert through paid, direct, organic, or sales-assisted paths. That chain is the reason [AI visibility reporting without fake precision](https://withsurface.com/blog/ai-visibility-reporting-without-fake-precision) needs to separate rankings, retrieval, citations, mentions, recommendations, referrals, and business response. A screenshot can show presence. It cannot prove incrementality. A citation count can show that a source is being used. It cannot automatically tell you whether that source changed a buyer’s mind. The measurement work becomes more useful when teams stop asking one broad question and start asking better smaller ones: - Which prompts mention us? - Which prompts recommend us? - Which pages are cited? - Which third-party sources reinforce our claims? - Which AI-referred sessions show meaningful engagement? - Which AI-influenced journeys become qualified pipeline? - Which competitors appear because their source ecosystem is stronger than ours? Thinking about [query fan-out in Google AI search](https://withsurface.com/blog/query-fan-out-in-google-ai-search-how-marketers-should-build-con) gives marketers a useful operating frame. AI systems may break one buyer prompt into several related searches before composing an answer. That means one page rarely carries the whole job. Category pages, comparison pages, proof assets, implementation guides, product pages, third-party references, and conversion paths all start working as one source system. Product marketers should pay attention because AI recommendations behave more like product positioning than like old search snippets. An assistant does not merely rank pages. It compresses the category, compares options, decides which attributes matter, and returns a recommendation in language the buyer may treat as neutral. That makes product architecture, proof, positioning, comparison language, use cases, objections, and source quality part of the retrieval system. A recent academic study, [From Prompt to Purchase](https://arxiv.org/abs/2606.10907), found that conversational assistant recommendations increased same-name Google searches, own-site visits, and brand-specific retailer-page visits among users with no recent observed engagement with the recommended brand. The study did not observe transactions, and that caveat matters. Still, it gives marketers a stronger way to talk about upstream influence: AI recommendations can create brand-seeking behavior that referrer logs and last-click reports may miss. Reuters also reported Adobe Analytics data showing that AI-referred U.S. retail shoppers in May generated 53% more revenue per visit than non-AI visitors and showed stronger engagement. B2B marketers should not copy retail conclusions blindly. A shopper buying apparel and a buying committee evaluating a technical product are not the same situation. The directional lesson still matters: AI-referred traffic may be low-volume but unusually informed, problem-aware, or close to action. That is why product marketing needs to be measured as a memory and buyer-confidence system, not only a content output function. The product marketing expansion on [product marketing for AI recommendations](https://withsurface.com/blog/product-marketing-ai-recommendations-brand-legibility) should sit beside the measurement work, because brands become easier to recommend when their proof is easier to find, their claims are easier to cite, and their category position is easier to understand. We believe [content marketing strategy](https://withsurface.com/blog/content-marketing-strategy-the-quality-vs-volume-trap-in-ai-era) now has to defend both reach and trust. More pages do not automatically create more authority. A smaller system of current, specific, evidence-backed pages can often do more work than a bloated archive full of thin explanations. Paid media teams are facing the sharpest version of this problem. Google is moving ad experiences into AI Mode and AI Search, including new ad formats built with Gemini and expanded commerce-oriented ad experiences. Search Engine Land’s coverage of Google Ads clarifications after Google Marketing Live noted that AI Max is not required for AI Search ads, and that advertisers should not expect a clean separate performance breakout for AI Overviews or AI Mode ads. That does not mean paid media teams should ignore the channel. It means the test design matters more than the product label. AI media formats need stronger conversion data, cleaner first-party signals, better exclusions, clearer landing pages, and sales feedback loops. Google’s enhanced conversion and Data Manager updates point in the same direction: AI-powered media systems need better event quality if marketers expect them to optimize toward useful outcomes. The paid media expansion on [testing AI Max without losing the plot](https://withsurface.com/blog/paid-search-ai-interfaces-ai-max-measurement) should be read as a measurement readiness guide, not a platform reaction. The question is not “should we turn on AI Max?” The better question is “do we have clean enough conversion data, campaign structure, landing page intent, and CRM feedback to learn anything useful from the test?” Teams using [inbound marketing automation](https://withsurface.com/blog/inbound-marketing-automation) should make sure conversion events, lead scoring, routing, CRM enrichment, and sales acceptance are strong enough to keep paid AI experiments honest. If a campaign optimizes toward low-quality form fills, the problem is not only the campaign. It is the measurement system feeding the campaign. The regulatory and publisher-control story matters because marketers are used to thinking about AI visibility as exposure. Publishers are forcing the second question: exposure on whose terms? Google announced new tools for website owners navigating AI in Search, including Search Console controls and performance insights. Google also expanded [Preferred Sources into AI Overviews and AI Mode](https://blog.google/products-and-platforms/products/search/original-high-quality-content-search/), making source preference more visible inside AI-assisted search experiences. The UK Competition and Markets Authority has also pushed Google toward stronger publisher controls, attribution, links, and opt-out options around AI features. For most B2B marketers, the immediate action is not to opt out of everything. The immediate action is to know what would happen if you did. Which pages are traffic acquisition pages? Which pages are citation and authority pages? Which pages contain sensitive claims? Which pages are customer proof assets? Which pages would you want summarized accurately, and which would you rather keep closer to the site experience? The governance expansion on [AI search controls, opt-outs, and Preferred Sources](https://withsurface.com/blog/ai-search-control-layer-opt-outs-preferred-sources) treats this as a page-role problem. Some pages should act as open citation assets. Some pages should be controlled conversion assets. Some pages contain sensitive claims and need tighter sourcing. Some old pages are outdated risk assets. Some pages should exist primarily as authority reinforcement. That classification matters because a page is no longer merely a page. It is a potential answer source, ad landing page, citation object, sales enablement asset, and machine-readable fragment of the company’s public memory. \## What marketers should build next The right response is a measurement layer with humility built in. Start with a visibility taxonomy. Separate classic rankings, AI citations, brand mentions, assistant recommendations, AI Assistant referrals, paid AI exposures, branded search lift, qualified lead behavior, sales acceptance, and revenue influence. Do not collapse them into one score unless the score is clearly labeled as an index. Then create a prompt and query set that reflects how buyers actually ask questions. Include broad category prompts, comparison prompts, implementation prompts, problem prompts, alternative prompts, and competitor prompts. Repeat them over time. Single-prompt screenshots can be useful as examples, but they are weak evidence by themselves. Next, refresh the source ecosystem. Owned pages should be current, specific, evidence-backed, and clear. Third-party proof should not be treated as PR decoration. Reviews, customer quotes, analyst mentions, partner pages, video, community answers, and credible comparison content all influence whether a brand feels safe to recommend. Then tie the dashboard to revenue reality. AI visibility reporting should sit next to CRM and sales data, not in a novelty tab. If a cited page generates no qualified behavior, ask whether the page answers the wrong question, attracts the wrong buyer, or lacks a conversion path. If AI Assistant referrals convert unusually well, inspect what those sessions saw before the form fill. If branded search rises after AI recommendation exposure, call it suggestive until incrementality testing makes the case stronger. Finally, use [how to actually measure lead quality](https://withsurface.com/blog/how-to-actually-measure-lead-quality-not-just-lead-volume) as the guardrail. AI visibility is only useful if it helps the company attract better-fit buyers, create clearer sales conversations, and move real opportunities forward. What is known: AI-mediated discovery is now visible enough to measure in pieces. Search Console can show generative AI impressions for participating site owners. GA4 can classify traffic from AI assistants. Google is expanding AI Search ad formats. Regulators are forcing more publisher-control questions. Research is beginning to show that assistant recommendations can affect downstream brand-seeking behavior. What is inferred: brand, product marketing, analytics, SEO, paid media, and RevOps are converging because AI search compresses what used to be separate steps: category education, vendor discovery, comparison, recommendation, and conversion. The teams that manage those steps separately will have a harder time understanding what changed. What is still unsettled: AI search behavior is variable. Reporting is partial. AI Overview and AI Mode surfaces will continue changing. Paid placement transparency remains limited. Regulatory requirements differ by market. Academic studies are improving the evidence base, but they do not remove the need for cautious interpretation. Research on [Google AI Overviews](https://arxiv.org/abs/2605.14021) has already shown that AI-generated search results can activate differently by query type and use sources differently from traditional ranking systems. Marketers do not need perfect certainty to act. They need enough structure to avoid mistaking visibility for revenue, volume for authority, or platform adoption for strategy. The old dashboard was built for clicks. The new one has to account for what happened before the click existed. That does not mean abandoning SEO, paid media, content strategy, or product marketing fundamentals. It means connecting them with more honesty. A buyer’s path may now move from an AI answer to a branded search, from a recommendation to a sales conversation, from a cited blog to a pricing-page visit, from a paid AI surface to a CRM record that only becomes meaningful after sales reviews fit. The teams that win will not be the ones that declare SEO dead or AI search solved. They will be the ones that can say, with some precision and some restraint, where the brand appears, why it appears there, what evidence supports it, which buyers respond, and what the business should do next. Brand measurement is becoming a source ecosystem, not a channel report. The sooner marketers build that layer, the less likely they are to confuse a new dashboard tile for a new strategy. --- # Operational Marketing Now: Storytelling Meets the Retrieval Machine | Surface Labs URL: https://surface.thesurface.network/blog/june-8-weekly-operational-marketing-now A strange thing happens when a marketing team says it needs a Storyteller. Usually, the team means it wants someone who can make the company feel less interchangeable, translate technical complexity into human stakes, and create a narrative that customers, sales teams, executives, analysts, and now AI systems can repeat. Then the same team evaluates that person almost entirely through MBA-style judgment: traffic, MQLs, pipeline influence, attribution, conversion, and quarterly performance. Those measures matter. A brand story that never moves through the business eventually becomes decoration. Still, a company that asks for storytelling and only measures the role through performance dashboards has already misunderstood part of the job. Story also belongs to MFA-style creative traditions: voice, tension, scene, specificity, pacing, character, memory, contradiction, and the strange little detail that makes someone believe a sentence came from a real company staffed by real people. This week’s Operational Marketing Now uses that tension as the opening frame. The retrieval era has made marketing more measurable in some ways and less measurable in others. AI search can cite, summarize, compare, and recommend without sending a clean click. Paid search is moving into AI interfaces before marketers have stable reporting models. Google keeps reminding teams that AEO and GEO still require SEO fundamentals. Through all of this, the Storyteller role starts to look less like a soft brand hire and more like a retrieval-era operator responsible for making the company legible across search, AI answers, sales conversations, customer proof, and buyer memory. Recent marketing shifts have made the same pattern more visible: AI visibility now depends on coverage, freshness, evidence, clarity, and source mix, which changes how teams should think about [weekly marketing intelligence](https://withsurface.com/blog/may-marketing-updates). When AI systems retrieve meaning from clusters of sources, storytelling, SEO, paid media, and measurement start to collapse into one operating problem. \## The opening dialogue: why does marketing hire Storytellers, then measure them like growth analysts? The “Storyteller” title has moved through corporate marketing for years, from brand narrative and customer storytelling to executive communications, data storytelling, employer brand, product marketing, and content strategy. The current resurgence makes sense. AI has made competent content easier to produce. It has also made sameness easier to recognize. When every company can generate a decent landing page, the real scarcity becomes judgment, specificity, and a story that can survive contact with a buyer. The problem is not that marketers use business metrics. The problem is that many teams use only business metrics for a role they hired because business metrics could not solve the whole problem. Pipeline influence can tell a team whether a story moved through the revenue system. It cannot tell the team whether the story has a scene, whether the customer appears as a person rather than a persona, whether the language sounds owned, or whether the narrative can be repeated without turning into generic positioning mush. A better model gives the Storyteller two scorecards. The business scorecard tracks sales reuse, branded search lift, customer proof coverage, citation quality, executive-message consistency, assisted conversions, and sales-cycle clarity. The craft scorecard tracks narrative coherence, specificity, voice, tension, audience dignity, proof integration, and memorability. That second scorecard does not make the work precious. It makes creative quality discussable before the market quietly punishes the company for sounding like everyone else. This is also why [B2B marketing has changed so sharply over the last few years](https://withsurface.com/blog/how-b2b-marketing-has-changed-in-the-last-3-years). Buyers now research, compare, and form opinions before they ever talk to sales. Teams still need pipeline, attribution, and conversion systems, but they also need language buyers can remember after the tab closes. \### Theme one: query fan-out makes content architecture the work Google’s language around query fan-out gives marketers a useful phrase for something many content teams have already felt. A buyer’s single question can turn into a small research project inside an AI system. The system may need definitions, comparisons, use cases, objections, integrations, pricing context, risks, alternatives, and proof before it can assemble a useful answer. That changes the content strategy question. Teams should stop asking whether one blog can rank for one keyword and start asking whether their owned and off-site source ecosystem can satisfy the question field around a buyer’s intent. A strong page still matters, but the surrounding architecture matters more than most editorial calendars admit. Content needs a pillar, supporting angles, internal links, evidence blocks, examples, customer proof, and a clean next step. Marketers translating [Google’s generative AI search guidance](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) into content planning should start with a practical operating question: can a buyer or retrieval system move cleanly from the category question to the comparison question, the implementation question, the proof question, and the conversion question? The next move is to build fan-out maps before commissioning pages, then decide which buyer questions deserve first-party content, which belong in sales enablement, and which need third-party validation. \### Theme two: AI visibility measurement is messy because the unit of measurement changed AI visibility does not behave like a stable ranking report. Answers vary across prompts, paraphrases, runs, models, interfaces, account states, and time. A team can rank well in classic search and still fail to appear in an AI recommendation. A brand can be mentioned without being cited. A page can be cited without meaningfully shaping the answer. A competitor can win because an off-site source, review page, video, or comparison article gives the system a cleaner path to confidence. That is why AI visibility reporting should stop pretending it has the neatness of a ten-blue-links SERP. The useful unit is no longer a single keyword position. Marketers need to track prompt families, repeated samples, paraphrase coverage, source mix, brand mentions, citations, recommendations, narrative share, and confidence labels. The goal is not to create a dashboard that looks more certain than the market actually is. The goal is to help teams make better decisions without hiding uncertainty. Thinking about [AI citations vs. SEO rankings](https://withsurface.com/blog/ai-citations-vs-seo-rankings) gives marketers a cleaner vocabulary for this problem because ranking, citation, mention, and recommendation should not collapse into one vague visibility score. Teams that want a more operational reporting layer can extend that thinking into an [AI visibility dashboard](https://withsurface.com/blog/ai-visibility-dashboard) that tracks model-by-model visibility, competitor presence, prompt families, source mix, and the gaps that should shape the next content sprint. \### Theme three: paid search is moving into AI interfaces before reporting models mature Paid search is also leaving the old container. The familiar unit was the keyword list, matched to ads, bids, landing pages, and conversion reporting. AI interfaces are pushing the paid unit toward briefs, feeds, prompts, product data, audience context, creative systems, landing page proof, and brand-safety instructions. Marketers can buy into AI-shaped surfaces faster than they can fully explain incrementality inside them. This creates a serious operating problem for performance teams. Paid media leaders need to test new inventory without pretending the reporting is mature. They need clean feeds, current product data, proof-backed landing pages, comparison assets, review hygiene, exclusion logic, and a measurement plan that can handle assisted behavior. The old comfort of keyword-to-click-to-conversion reporting will not disappear entirely, but it will describe a smaller share of the paid discovery experience. As [ads move into the answer layer](https://withsurface.com/blog/june-1-this-week-in-marketing), marketers need to connect media testing to the actual economics of acquisition. Asking [what it costs to book one meeting](https://withsurface.com/blog/what-does-it-actually-cost-you-to-book-one-meeting) becomes more important when interfaces get harder to measure, because paid teams need to judge cost per meeting, lead quality, expectation-setting, and what happens after the paid interaction. \### Background theme: AEO and GEO still need SEO bones The sober reminder underneath this issue is that AEO and GEO do not replace SEO. Google’s guidance keeps pulling the conversation back toward crawlable, indexable, useful, well-structured pages that can be retrieved, understood, and shown with confidence. AI visibility work adds new layers: prompt testing, citation tracking, source-mix analysis, fan-out coverage, off-site proof, and narrative consistency. Those layers work poorly when the site itself is technically weak, thin, stale, or confusing. This is where acronym culture can become expensive. A team can buy an AI visibility tool, run prompt tests, and build dashboards, but if the core pages are hard to crawl, poorly linked, unsupported by evidence, or inconsistent in product language, the program will keep diagnosing symptoms. Strong AEO/GEO work begins with SEO reality: indexability, internal links, text availability, snippet eligibility, structured content, page experience, current claims, and a clear answer path. Teams evaluating [generative engine optimization services](https://withsurface.com/blog/generative-engine-optimization-services) should look past the acronym and ask whether the work creates a real content strategy, a clearer source ecosystem, and a stronger retrieval path. AI visibility rewards systems of trust. It does not reward teams for renaming old work while leaving the actual site, story, and conversion path unchanged. \## Operational takeaway This issue should leave marketers with one main idea: retrieval-era marketing rewards companies that can make themselves easier to understand, verify, retrieve, cite, and choose. That is a technical problem, because crawlers and AI systems need clean access to useful pages. It is a measurement problem, because old dashboards do not fully describe AI-shaped discovery. It is a paid media problem, because ads are entering answer-like interfaces faster than attribution can settle. It is also a storytelling problem, because a company still needs language, proof, and narrative shape that a buyer can remember. We believe that [lead journey tracking](https://withsurface.com/blog/lead-user-journey) matters because the path after visibility matters just as much as the moment of discovery. Sales teams need to understand what a buyer read, compared, and considered before conversion, while [inbound lead management](https://withsurface.com/blog/inbound-lead-management) connects that context to speed-to-lead, enrichment, scoring, routing, and follow-up. In the retrieval era, content does not finish its job when it earns a citation, ranking, or click. The stronger question is whether the entire system helps a buyer move from recognition to confidence to action. ### Build a dual Storyteller scorecard Evaluate storytelling work through both business performance and creative craft. The business side should track sales reuse, message consistency, branded search lift, citation quality, assisted conversions, customer proof coverage, and whether sales teams actually use the narrative in live conversations. The craft side should track specificity, voice, tension, narrative coherence, audience dignity, proof integration, and memorability. A useful Storyteller should make the company easier to understand, remember, trust, and repeat. Do not reduce that work to traffic and pipeline alone. Those outcomes matter, but they only capture the downstream evidence. Teams also need a way to judge whether the story itself is any good before the market delivers the verdict. ### Turn priority topics into query fan-out maps Before assigning another blog, map the full question field around each priority category. Start with the main query, then list the adjacent questions a buyer or AI system would need answered: definitions, comparisons, implementation concerns, risks, alternatives, pricing context, proof requirements, integration questions, and “why now” arguments. From there, decide what deserves a pillar page, what deserves a supporting blog, what belongs in a product page, what belongs in sales enablement, and what needs third-party validation. Query fan-out rewards connected coverage. A single strong page helps, but a clearly structured answer system is much harder for competitors to displace. ### Report AI visibility as a confidence model Stop treating AI visibility like a cleaner version of keyword ranking. Build reports around prompt families, paraphrase tests, repeated runs, model-by-model behavior, citation frequency, brand mentions, competitor recommendations, source mix, and answer sentiment. Mark what is known, what is directional, and what remains unstable. A useful AI visibility report should help a team decide where to invest next. It should show whether the brand is absent, mentioned, cited, recommended, misrepresented, or losing to competitors through third-party sources. That means the report needs enough humility to admit uncertainty and enough structure to guide action. ### Separate citations, mentions, and recommendations Track three different visibility states instead of blending them together. A citation means the system used or displayed a source. A mention means the brand appeared in the answer. A recommendation means the brand was positioned as a viable or preferred option. Each one has different business value. For each priority prompt set, record whether the brand appears, how it appears, which sources support the answer, which competitors appear nearby, and whether the answer frames the category accurately. This gives marketers a cleaner view of where the problem lives: content gaps, source authority, off-site proof, product positioning, or competitor narrative strength. ### Treat paid AI-interface tests as controlled experiments As ads move into AI-shaped interfaces, marketers should avoid treating early results like mature paid search benchmarks. Start with controlled tests: limited budget, clear audience assumptions, clean landing pages, specific conversion events, and a written hypothesis for what the campaign should prove. Measure more than click-through rate. Watch assisted conversions, meeting quality, search lift, branded query changes, downstream lead quality, and whether the paid experience creates better or worse expectation-setting. AI interfaces may compress discovery, comparison, and recommendation into one environment. Reporting needs to account for that messiness rather than pretending every touch behaves like a classic paid search click. ### Audit SEO fundamentals before chasing AEO or GEO tactics AEO and GEO work poorly when the site has weak SEO foundations. Before buying another tool or creating another AI visibility dashboard, confirm that priority pages are crawlable, indexable, internally linked, text-accessible, current, and clear. Make sure core product language is consistent across landing pages, blogs, case studies, documentation, and comparison pages. Technical SEO still acts as the retrieval layer. If AI systems and search engines cannot access, parse, trust, or contextualize the page, the brand will struggle to earn visibility no matter how polished the content strategy sounds. Treat SEO fundamentals as the floor under AI visibility, rather than an older discipline that can be skipped. ### Add evidence blocks to high-value pages Update priority pages with clearer proof: statistics, customer examples, screenshots, benchmarks, expert quotes, comparison tables, implementation notes, methodology explanations, and source citations. The goal is to make each page easier for a human buyer to trust and easier for an AI system to cite. Evidence blocks are especially important on pages that make category claims, product claims, or comparison claims. Unsupported assertions are cheap now. Proof is the differentiator. A good page should not merely say the company is credible. It should show why someone would be reasonable to believe it. ### Connect visibility work to lead journey infrastructure AI visibility, SEO, and paid media should not stop at the moment of discovery. Review what happens after someone lands on the site: CTAs, routing logic, forms, enrichment, qualification, nurture, sales handoff, and follow-up timing. A citation or click has limited value if the visitor enters a broken conversion path. For each major content cluster, define the intended next action. Some readers should visit a product page. Some should read a case study. Some should subscribe. Some should book a meeting. Some should enter a nurture path. Retrieval-era content needs a clear human path after the machine finds it. ### Refresh source-sensitive content on a recurring cadence AI visibility depends partly on freshness, especially in fast-moving categories like SEO, paid media, AI search, and marketing technology. Build a refresh queue for pages that contain statistics, product claims, platform guidance, screenshots, pricing references, or regulatory commentary. Each refresh should update the claim, source, date, internal links, and recommendation. Do not only change the publication date. Teams should make the page materially more useful each time they revisit it. Freshness without substance turns into maintenance theater. ### Create one operating owner for retrieval-era visibility Assign someone to own the connective tissue across SEO, AEO/GEO, paid search, content, storytelling, and measurement. This does not need to be a new executive role, but someone needs responsibility for how the company appears across search engines, AI systems, ads, source ecosystems, and sales conversations. Without that owner, teams tend to split the work into disconnected fragments. SEO owns rankings. Content owns blogs. Demand gen owns ads. Product marketing owns messaging. Sales owns objections. AI visibility exposes the weakness of that structure because retrieval systems do not respect internal org charts. They assemble the brand from whatever evidence they can find. --- # Launching Ad Analytics | Surface Labs URL: https://surface.thesurface.network/blog/launching-ad-analytics That's how much sooner you'll know whether an ad is actually working, once you grade it on lead quality instead of ad platform metrics. Here's why the gap is that wide. Meta wants to show you conversions. LinkedIn wants to show you leads. Google wants to show you clicks. Every one of those numbers is a report card the platform wrote about itself. So the dashboard looks great even when the leads never close. A Meta campaign can be your top performer in Ads Manager and your top source of pipeline that never books a demo. You usually don't find out until month three, when someone in RevOps finally stitches spend against pipeline in a spreadsheet. Surface is where the leads actually land, get enriched, get scored, and get routed. That position gives us signals Meta and LinkedIn never touch: - Which leads matched your ICP - Which ones engaged after signup - Which ones a rep called qualified - Which ones booked a meeting - Which ones closed - Which ones churned inside 30 days Every one of those ties back to the ad it came from. Not ad to click. Ad to an actual dollar of revenue. Two reasons. First, you don't have to wait on pipeline data. If an ad is bringing in leads that are visibly off-ICP or low intent, you know that on day two, not after the whole sales cycle plays out. Second, you get a peer benchmark. Surface sees ad performance across hundreds of B2B companies, so when your CAC or your lead quality sits well outside the norm for companies like yours, we can tell you. Anonymized and aggregated. That's a comparison against reality, not just your own trend line drifting. Put those together and "is this ad working" goes from roughly 60 days to roughly 10. ## The story your CFO has been asking for Most marketing teams can't tell this story: > This $80K campaign brought in 340 leads. 88 were ICP fit, 22 booked demos, 6 became opportunities, and 2 have closed for $180K in ARR. Payback in 30 days. That used to take a dedicated RevOps hire and a warehouse pipeline. In Surface it's the default report. Everyone obsesses over finding the winning campaign. The bigger win is cutting the losing one early. Every quarter a bad campaign stays live is money you don't get back. Surface flags it in days instead of months. You reallocate, your pipeline math improves, and you spend less to produce more. Want to see your ad spend graded honestly for once? [Book a demo →](https://withsurface.com/book-a-demo) --- # Lead Capture and Routing for Auto Dealerships | Surface Labs URL: https://surface.thesurface.network/blog/lead-capture-and-routing-for-auto-dealerships A buyer submits a form on your website for a 2026 Tahoe. That same buyer submits the same form on 2 other dealer sites within 10 minutes. The first dealership to call with something useful to say wins the deal. Your BDC rep sees the lead 3 hours later, calls, and gets voicemail. The buyer already has an appointment somewhere else. This happens dozens of times a day at most dealer groups. The leads aren't bad. The ads are working. The inventory is there. But the infrastructure between "lead comes in" and "someone useful calls back" is so slow and disjointed that half your ad spend is subsidizing your competitor's sales. And the problem compounds when you're running 5, 10, or 15 rooftops — each with its own lead sources, its own BDC team, and its own version of "we follow up fast." Auto buyers in 2026 are doing 80% of their research online before they ever talk to a human. By the time they submit a form, they've already narrowed to 2–3 dealers. They're not browsing. They're ready to act. That means the window isn't hours. It's minutes. Data from dealer lead platforms consistently shows that responding within 2 minutes produces 3–5x higher contact rates than responding within 30 minutes. After an hour, the lead is essentially cold — not because the buyer lost interest, but because someone else got there first. Most dealer groups know this. The problem is that knowing it and having infrastructure that actually delivers sub-2-minute response times across every lead source, every rooftop, and every shift are two very different things. Here's the typical lead flow at a multi-rooftop dealer group — and where it falls apart: Stage What happens What breaks **Lead comes in** Website form, Autotrader, Cars.com, CarGurus, OEM program, Facebook ad Each source has a different format, different fields, different delivery method — some API, some email parse **Lead enters CRM** Pushed or imported into dealer CRM (DealerSocket, VinSolutions, Elead) Minimal context — often just name, phone, and a vague vehicle interest like "interested in SUVs" **BDC assignment** Round-robin to next available BDC rep No matching by vehicle type, new vs. used, location proximity, or rep expertise **Qualification** BDC rep calls and asks basic questions — budget, timeline, trade-in, financing needs These are questions that could've been answered at capture. 5-minute call for info that takes 30 seconds on a form **Handoff to sales** BDC rep transfers or sets appointment with floor sales Context gets lost in the handoff — salesperson re-asks the same questions **Service leads** Separate intake — often a different phone number, different form, different team No unified view. A service lead could be a buyer lead in disguise and nobody catches it Every stage adds delay. Every handoff loses context. And across multiple rooftops, these problems multiply — different teams running different versions of a broken process. Round-robin assignment is the default in every dealer CRM. It's simple. It feels fair. And it ignores everything that matters about matching a lead to the right person. **A buyer asking about a certified pre-owned F-150 should not be routed to a rep who only sells new luxury vehicles at a different rooftop.** That's not a training gap — it's a routing failure that wastes the lead's time, the rep's time, and the ad spend that generated the lead. Smart routing for dealer groups means matching on variables that actually predict conversion: - **New vs. used vs. CPO.** Different inventory, different sales process, different reps. Route accordingly. - **Vehicle type and price tier.** A buyer looking at a $28K Camry and a buyer looking at a $75K Escalade need different conversations with different people. - **Rooftop proximity.** If you have 8 locations, the lead should route to the closest rooftop that has the vehicle they're interested in — not whichever location's BDC team happens to be next in line. - **Inventory availability.** Don't route a lead for a specific vehicle to a rooftop that doesn't have it in stock. Check inventory in real time and route to where the car actually is. - **Rep availability and shift.** If it's 7 PM and the BDC team is off, the lead still needs a response. Route to whoever's working — or trigger an automated response that's specific enough to hold the buyer until morning. - **Lead source.** Third-party leads from Autotrader behave differently than website leads. Some reps close better on one source than another. This logic isn't exotic. But it requires a system that evaluates these variables at the moment of capture and routes instantly — not a CRM that drops the lead into a queue for a manager to sort through. Here's what a modern lead capture and routing setup looks like for a dealer group: **A buyer submits a form on Cars.com for a 2024 certified pre-owned RAV4.** The form captures vehicle interest, zip code, timeline, trade-in status, and financing preference — all in 4 questions. **The system routes in real time.** Based on vehicle type (CPO), make (Toyota), buyer zip code, and inventory availability, the lead routes to the closest Toyota rooftop that has CPO RAV4s in stock — and to a rep who handles used and CPO specifically. **The rep gets the lead with full context.** Not just "interested in a RAV4." They see: CPO preference, zip code, has a trade-in (2019 Civic), wants financing, timeline is this month. That's enough to have a real conversation on the first call. **The buyer gets a response in under 60 seconds.** A personalized text — "Hi David, this is Sarah at \[Dealership\]. I see you're looking at certified RAV4s. We have 4 in stock right now. I can get you pricing and trade-in value on your Civic — when's a good time to talk?" That message wins the deal. Not because it's clever, but because it's first, it's specific, and it shows the buyer they won't have to repeat themselves. The average BDC rep spends 40–60% of their call time on basic qualification — budget, timeline, trade-in, financing, vehicle preference. These are questions that could be answered at capture in 30 seconds on a smart form. When you front-load qualification, two things happen. BDC reps only talk to leads they already know are in-market, have a timeline, and have a vehicle interest that matches your inventory. And the conversation shifts from "tell me about what you're looking for" to "here's what we have that fits — when can you come in?" That's the difference between a 5-minute qualification call and a 90-second appointment-setting call. Across a BDC team handling 50+ leads a day, that's hours of recovered capacity. Most dealer groups treat service leads and sales leads as completely separate pipelines. Different forms, different teams, different systems. But a customer bringing a 2018 vehicle in for its third major repair is a prime candidate for a new purchase conversation. A customer declining a recommended service because the cost exceeds the vehicle's value is telling you they're ready to trade. These signals exist in your service intake data — but if service and sales capture are siloed, nobody connects them. Unified capture means every lead — sales or service — flows through the same system. Routing rules can flag service leads that match buyer intent signals and route them to sales automatically. Not to replace the service appointment, but to add a parallel sales touchpoint that most dealers are missing entirely. Here's a rough model for a 6-rooftop dealer group spending $80,000/month across all lead sources: Metric Current setup With smart capture + routing Monthly lead spend $80,000 $80,000 Total leads generated 2,400 2,400 Avg. response time 3.2 hours Under 90 seconds Lead-to-appointment rate 12% 30% Appointments per month 288 720 Cost per appointment $278 $111 Service-to-sales conversions ~0 (not tracked) 15–25/month Same spend. Same lead volume. The difference is entirely in speed, routing accuracy, and front-loaded qualification. That's $167 per appointment in waste — across 2,400 leads a month. Your dealer CRM stays. DealerSocket, VinSolutions, Elead, CDK — they're built for inventory, desking, and deal management. That's their job and they do it fine. What they weren't built for is the first 90 seconds — real-time capture, instant qualification, smart routing across rooftops, and sub-minute response. That's a different layer. It sits in front of your CRM, not instead of it. Surface was built for that layer. One system that handles capture, qualification, routing, and instant response — across every rooftop, every lead source, and every department. For dealer groups, that means forms that qualify before the BDC ever picks up the phone, routing that matches leads to the right rooftop and rep based on real variables, and response times that beat every other dealer the buyer contacted. If your group is spending six figures a month on leads and your BDC team is still getting name-and-phone-number alerts hours after submission, the fix isn't more leads. It's better infrastructure for the leads you already have. That's what Surface was built to do. --- # Lead Capture and Routing for B2B SaaS Companies | Surface Labs URL: https://surface.thesurface.network/blog/lead-capture-and-routing-for-b2b-saas-companies B2B SaaS companies have a specific lead ops problem that's different from home services, law firms, or auto dealerships. You're selling to multiple segments (startup, mid-market, enterprise) with different sales motions, different deal sizes, and often different products or plans. The buyer on the other end of the form might be a solo founder evaluating your free tier or a VP at a Fortune 500 evaluating a six-figure contract. Round-robin routing treats them identically. Your conversion rate depends on treating them very differently. SaaS companies generate leads from more sources than most industries — organic search, paid ads, product-led signups, G2 and Capterra, partner referrals, outbound-turned-inbound, and content downloads. Each source has different intent levels and different conversion expectations. Failure point What's happening Impact **Segment misrouting** An enterprise lead gets round-robined to a junior SDR. A startup lead gets sent to the enterprise AE team. Neither rep is equipped for the conversation. Lower conversion rate, wasted rep time, frustrated buyers who feel like they're in the wrong room. **Product/plan mismatch** Lead is interested in Product A but gets routed to a rep who specializes in Product B. Or they want the self-serve plan but get a 30-minute enterprise demo. Mismatched conversations that don't address the buyer's actual need. **PLG-to-sales handoff gap** Product-led growth creates a surge of signups. The ones showing buying signals (added team members, hit usage limits, viewed pricing) need a sales touch — but there's no trigger to route them. High-intent product users sit in a self-serve flow when they're ready for sales engagement. **Trial-to-paid conversion drag** Free trial users who request help, ask pricing questions, or hit upgrade prompts don't get connected to sales fast enough. Trial users churn because nobody engaged at the moment of interest. **Demo request response time** SaaS demo requests have the shortest shelf life of any B2B lead. The buyer submitted to 2–3 competitors simultaneously. Whoever responds first with a relevant conversation wins. Average SaaS demo response time is 42 minutes. Top performers are under 60 seconds. The gap is 3–5x in meeting conversion. SaaS routing needs to evaluate more variables than most industries because the sales structure is more complex. **Segment tier.** Employee count and revenue (from form + enrichment) determine whether the lead is startup, SMB, mid-market, or enterprise — and which team handles them. An enterprise lead (500+ employees, $50K+ deal potential) routes to a senior AE. An SMB lead (10–50 employees) routes to an SDR or self-serve flow. **Product interest.** If your company sells multiple products or modules, the lead's stated interest (captured on the form) determines which specialist or product team gets the lead. A lead interested in your analytics product shouldn't go to a rep who sells your automation product. **Use case.** "Replacing our current tool" is a different conversation than "building this capability for the first time." The form captures use case, and routing can match based on competitive displacement experience or greenfield sales motion. **Account status.** Is this a net-new lead or someone from an existing customer account? Expansion leads should route to the assigned CSM or account manager, not a new-business SDR. This requires checking the CRM at the moment of capture. **Lead source and intent level.** A G2 comparison page lead has higher intent than a blog subscriber. Demo requests route differently than whitepaper downloads. Source-based routing ensures the response matches the intent. \[IMAGE: A routing diagram showing a form submission being evaluated against five variables (segment tier, product interest, use case, account status, lead source) with different routing outcomes: "Enterprise AE (instant)," "Mid-market SDR (< 2 min)," "Self-serve onboarding (automated)," "Existing account → CSM." White background, blue (`#4F6DF5`) accent, flat design.\] Product-led SaaS companies face a unique routing problem: the highest-intent leads aren't filling out forms — they're using the product. A user who adds 5 team members, integrates their CRM, and views the pricing page is signaling buying intent through behavior, not through a form submission. Routing these users to sales requires a trigger system that evaluates product usage signals and routes when a threshold is crossed — the same capture-qualify-route logic used for inbound forms, but triggered by product behavior instead of form submission. The best SaaS lead ops systems handle both paths: form-based inbound (demo requests, contact forms, pricing inquiries) and product-triggered outreach (usage milestones, upgrade prompts, pricing page visits). Both paths feed into the same routing engine and the same rep assignment logic. SaaS demo requests are among the most expensive leads in B2B — typical CPL ranges from $100–$500 depending on the product and segment. When a demo request costs $250, and 40% of those leads never get a timely, relevant conversation, you're burning $100 per wasted lead. Metric Typical SaaS Optimized SaaS Monthly demo requests 150 150 Average speed-to-lead 42 minutes Under 60 seconds Lead-to-meeting rate 15% 35% Meetings booked 22 52 Cost per meeting (at $250 CPL) $1,705 $721 Same traffic. Same ad spend. More than double the meetings. The delta comes entirely from routing leads to the right rep, instantly, with full context. Surface handles the full SaaS lead ops flow — multi-segment routing, product-interest matching, real-time qualification, and instant response. Whether the lead comes from a demo request form, a G2 inquiry, or a product usage trigger, Surface routes them to the right person with the right context in under 60 seconds. If your SaaS company is generating demo requests and your lead-to-meeting rate is below 20%, the bottleneck isn't lead generation. It's lead operations. That's what Surface was built to fix. --- # Lead Capture and Routing for Home Service Companies | Surface Labs URL: https://surface.thesurface.network/blog/lead-capture-and-routing-for-home-service-companies Home service companies — HVAC, plumbing, roofing, electrical, landscaping, cleaning — run on leads. A homeowner needs something fixed, they search for it, they fill out a form or call. If you're fast, you get the job. If you're slow, the next company on Google does. The problem is most home service companies are running lead capture the same way they did ten years ago. A basic form on their website. Maybe a third-party lead gen service. Leads come in, someone checks them manually, someone calls back when they get a chance. In an industry where the first company to respond wins the job 78% of the time, "when they get a chance" is costing you thousands every month. B2B SaaS companies can afford a 24-hour follow-up window. A $50,000 deal doesn't disappear because you called back the next morning. A homeowner with a leaking pipe doesn't wait. A family whose AC breaks in July doesn't shop around for a week. They need someone now. The first company that picks up, shows up, or books gets the job. This changes what your lead ops need to do: - **Speed is everything.** Not fast as in "same day." Fast as in minutes. - **Service area matters.** A lead outside your coverage zone wastes everyone's time. Routing needs to account for zip code and service radius. - **Job type determines who handles it.** A furnace install and a drain cleaning don't go to the same person. Routing by service type is table stakes. - **Availability is the bottleneck.** Your best tech is booked until Thursday. The lead needs service tomorrow. If your system can't check availability in real time, you either overbook or lose the job. Problem What happens Form only collects name and phone No service type, no address, no urgency. Someone has to call back to ask basic questions. Leads from Google, Yelp, Thumbtack all land differently No single view. Leads slip through because they're scattered across platforms. Manual dispatch Office manager looks at the lead, checks the schedule, calls the tech, calls the customer back. That's 20–30 minutes per lead on a good day. No after-hours capture Homeowner fills out a form at 9pm. Nobody sees it until 8am. By then they've called someone else. No spam filtering Competitors, bots, and junk submissions waste your team's time and fill your CRM with garbage. These aren't edge cases. This is how most home service companies operate. And every one of these gaps is a lost job. **Smart forms that qualify on the first touch.** Service type, zip code, urgency, property type — collected upfront with conditional logic so the homeowner only sees relevant questions. A commercial HVAC request and a residential drain issue don't need the same form. **Automatic routing by service area and job type.** Zip code determines which crew or franchise location handles the lead. Job type determines which technician or team it goes to. No manual dispatch. No phone tag. **Real-time availability and booking.** The right technician's calendar shows up inside the form based on the homeowner's location and service need. They book on the spot. No callback required. **After-hours capture that still works.** A lead that comes in at 10pm gets saved, qualified, and queued for the first available slot — or books directly if you offer next-morning availability. No leads lost overnight. **Spam and junk filtering.** Fake submissions, competitor snooping, and bot entries get caught during the form fill. Your team only sees real leads. Surface Labs handles all of this in one system. The form captures and qualifies. Routing runs on zip code, service type, and availability. The homeowner books directly on the right person's calendar. Everything syncs to your CRM or dispatch tool. If you're a home service company running on manual dispatch and basic web forms, the math is simple. Every lead you're slow on is a job your competitor gets. Speed wins in this business, and speed comes from infrastructure — not from telling your office manager to check the inbox more often. --- # Lead Capture and Routing for Law Firms | Surface Labs URL: https://surface.thesurface.network/blog/lead-capture-and-routing-for-law-firms A potential client visits your firm's website. They're dealing with something stressful — a divorce, a business dispute, a personal injury. They fill out your contact form. And then they wait. Maybe they hear back in a few hours. Maybe tomorrow. Maybe never, if the intake coordinator is swamped or the submission gets buried. By then, they've already called two other firms. The first attorney who got back to them got the case. Law firms spend aggressively on lead generation — Google Ads for personal injury firms can run $100–$300 per click. But most firms treat what happens after the click as an afterthought. A generic contact form. A shared inbox. An intake process that depends on who's in the office and how busy they are. That's where cases go to die. Legal leads aren't like SaaS leads. The stakes are personal, the timing is urgent, and the routing is complex. **Practice area determines everything.** A family law inquiry and a commercial litigation matter require completely different attorneys, different intake questions, and different timelines. A single generic form can't handle both well. **Conflicts and jurisdiction matter.** You can't take every lead. A firm needs to know the opposing party, the location, and the case type before they can even decide whether to engage. The faster you surface this information, the faster you can act on good leads and decline the rest. **Leads are expensive.** Legal is one of the most competitive verticals in paid search. A personal injury lead can cost $200+. An estate planning lead might cost $80. Either way, every lead that falls through the cracks is real money wasted. **Responsiveness builds trust.** A potential client choosing a lawyer is making one of the most personal decisions they'll make. The firm that responds fast, asks the right questions, and makes it easy to schedule a consultation signals competence before the first conversation even happens. **The form asks the wrong questions.** "Name, email, phone, how can we help you?" That tells your intake team almost nothing. They have to call back just to figure out what kind of case it is, whether you handle it, and whether there's a conflict. **Every inquiry goes to the same place.** A shared inbox or a single intake coordinator. Doesn't matter if it's a high-value commercial case or a quick question about a parking ticket — it all lands in the same pile and gets triaged manually. **Intake only works during business hours.** Someone fills out your form at 11pm after a car accident. Your office opens at 9am. That's ten hours where another firm could have already booked the consultation. **No qualification before the call.** Attorneys spend 15–20 minutes on consultations that should have been filtered out at intake. Wrong jurisdiction. Case type you don't handle. Opposing party is an existing client. All of this could be caught before the call. **Booking requires phone tag.** Intake coordinator calls back, leaves a voicemail, client calls back, coordinator is on another line. Two days later they connect. By then the client has already retained someone else. **Conditional intake forms by practice area.** The first question determines the rest of the form. A personal injury lead sees questions about the incident, injuries, and insurance. A business law lead sees questions about entity type, dispute nature, and revenue. The form adapts. The data is useful from the first submission. **Automatic conflict and jurisdiction screening.** Collect opposing party information and case location in the form. Flag potential conflicts before an attorney ever sees the lead. Filter out jurisdictions you don't cover. The intake team only reviews leads that can actually become clients. **Routing by practice area, seniority, and availability.** A complex estate case goes to a senior partner. A standard DUI goes to an associate. Routing happens based on form data — not whoever checks the inbox first. **Consultation booking inside the form.** The right attorney's calendar appears based on the prospect's practice area and location. They book a consultation before they leave the page. No phone tag. No callback. No delay. **24/7 capture with intelligent queuing.** After-hours submissions get saved, qualified, and either booked into the next available slot automatically or queued for priority follow-up first thing in the morning. Say your firm spends $15,000/month on Google Ads. You generate 100 leads. Your current intake-to-consultation rate is 30%. That's 30 consultations a month at $500 each. If you fix your intake flow and move that rate to 50%, that's 50 consultations from the same spend. Twenty extra consultations a month. If even a quarter of those convert to retained clients, the revenue impact dwarfs the cost of fixing intake. Surface Labs handles the full intake-to-consultation flow in one system. Conditional forms that adapt by practice area. Real-time qualification and conflict screening. Routing based on case type, jurisdiction, and attorney availability. Consultation booking inside the form. If your firm is spending serious money driving leads and then losing them to slow intake, a generic contact form, or phone tag with potential clients — the form isn't the problem. The infrastructure behind it is. That's what Surface was built to fix. --- # Lead Capture and Routing for Marketing Agencies | Surface Labs URL: https://surface.thesurface.network/blog/lead-capture-and-routing-for-marketing-agencies You run ads, build landing pages, and drive leads for your clients. Then those leads disappear into your client's CRM — and you never hear what happened to them. Two months later, the client says the leads weren't good enough. You can see the CPL. You can see the volume. But you can't see whether anyone actually followed up, how fast they responded, or where the leads died. This is the core tension of running an agency that does lead gen. You own the top of the funnel. You get blamed for the bottom. And it's not just a reporting problem. It's an infrastructure problem — one that gets worse with every client you add. When you have 3 clients, you can manage lead routing with spreadsheets and Zapier. When you have 15, you can't. Every client has a different setup. Different CRM. Different sales team structure. Different routing rules. Different expectations for what a "qualified lead" means. Some want leads in HubSpot. Some want them in Salesforce. One still wants an email notification to a shared inbox. So you end up building a custom Frankenstein integration for each client — Typeform to Zapier to webhook to CRM to Slack notification. It works until it doesn't. A Zap breaks. A field mapping changes. A new rep joins and nobody updates the routing logic. Leads fall through cracks that nobody notices for weeks. The problem isn't that agencies are bad at ops. It's that the standard toolchain wasn't built for one team managing lead infrastructure across 10+ different businesses simultaneously. Here's what the failure pattern looks like across a typical agency portfolio: Failure point What happens Impact **Inconsistent capture** Each client has a different form tool, different fields, different data quality Agency can't standardize qualification or reporting across clients **Fragile routing** Zapier chains, webhook relays, manual CRM imports — different stack per client One integration breaks, leads pile up unrouted for days before anyone notices **No speed-to-lead control** Agency hands off the lead; client's sales team responds whenever they feel like it 6-hour response times kill conversion — agency gets blamed for "bad leads" **Post-handoff blindness** Agency loses visibility the moment the lead enters the client's CRM Can't prove which leads converted, can't optimize campaigns against actual revenue **Reporting patchwork** Pull data from 8 different platforms to build one client report 5+ hours per client per month on reporting that's still incomplete Every row in that table is a drag on margins, retention, and the agency's ability to prove its own value. \[IMAGE: Diagram showing the agency lead handoff gap — left side shows "Agency" with ad platforms, landing pages, and forms flowing into a black box labeled "Handoff"; right side shows "Client" with CRM, sales team, and outcomes. The gap between them is highlighted. Clean, minimal, white background, blue (`#4F6DF5`) accent, flat design.\] This is the failure that kills agency-client relationships. **When you can't see what happens after the handoff, you can't defend your work.** A client says "we got 200 leads last month and only closed 2." Your response is some version of "our job was to deliver the leads." That's technically true and completely unsatisfying — for both sides. What you actually need to know is how many of those 200 leads were contacted within 5 minutes, how many had a real conversation, how many were qualified based on criteria you both agreed on, and how many made it to a proposal. Without that data, every QBR is a finger-pointing exercise. Agencies that control — or at least have visibility into — the full capture-to-conversation pipeline retain clients longer. Not because the leads are necessarily better, but because they can show exactly where value is being created and where it's being lost. And when it's being lost on the client's side, they have the data to prove it and the credibility to fix it. Here's what a modern agency lead ops setup looks like for a client engagement: **One capture layer across all clients.** Same form infrastructure, same qualification logic, same data model — customized per client but managed from one platform. When you onboard a new client, you configure their routing rules. You don't build a new integration stack from scratch. **Routing that matches the client's team.** Leads route based on the client's actual sales structure — by territory, by service line, by deal size, by rep availability. Not round-robin. Not "dump into CRM and hope." **Instant response, regardless of the client's team.** Confirmation messages go out in seconds. The lead gets acknowledged immediately with context — not a generic "thanks for reaching out" autoresponder, but a message that references what they asked about and who's going to help them. **Full-funnel visibility for the agency.** You can see every lead from capture through conversation through outcome. Not because you're in the client's CRM, but because the capture and routing layer tracks the whole journey. You know which campaigns produce leads that actually convert — not just leads that fill out a form. Agencies also need leads for themselves — new business, partnerships, talent. And most agencies are terrible at their own lead ops. You build sophisticated funnels for clients and then capture your own leads with a Contact Us form that goes to a shared email address. The same infrastructure applies. If an inbound lead from your own site — a potential $15K/month retainer — sits in an inbox for 8 hours because nobody's assigned to watch it, that's the same problem you're solving for your clients. Route by service interest, deal size, and partner availability. Respond in seconds. Track through close. Here's a rough model for a full-service agency managing lead gen for 12 clients: Metric Current (per client avg.) With unified capture + routing Integration setup time 8–12 hours 1–2 hours Monthly routing maintenance 3 hours 15 minutes Lead handoff failures per month 5–15 leads Near zero Avg. client speed-to-lead 3.5 hours Under 60 seconds Monthly reporting time 5 hours Automated Client lead-to-conversation rate 15% 40% Across 12 clients, that's roughly 36 hours a month in routing maintenance alone — before you count the leads lost to broken integrations, the reporting overhead, and the client churn driven by invisible post-handoff failure. The infrastructure cost isn't just ops time. It's the clients you lose because you couldn't prove your leads worked. This isn't about replacing the tools your clients already use. Their CRM stays. Their sales process stays. The agency's project management, reporting dashboards, ad platforms — all stay. The gap is the connective layer between "lead fills out form" and "lead is in the right rep's hands with full context, contacted in under a minute." That layer is what's missing — and it's what agencies end up duct-taping together differently for every client. Surface was built to be that connective layer. One platform for capture, qualification, routing, and instant response — across every client, with full visibility from form fill to outcome. For agencies, that means onboarding a new client's lead ops in hours instead of days, routing leads based on real variables instead of round-robin, and finally having the data to show which leads converted and why. If you're spending more time maintaining Zapier chains than optimizing campaigns, that's the gap Surface was built to close. --- # Lead Capture and Routing for Real Estate Teams | Surface Labs URL: https://surface.thesurface.network/blog/lead-capture-and-routing-for-real-estate-teams Your team is spending $10,000+ a month on Zillow, Realtor.com, and Facebook ads. Leads come in. They hit a generic CRM inbox. An admin assigns them manually — or worse, round-robins them to whoever's next in line. By the time the right agent calls back, the buyer has already talked to 2 other teams. This is how most mid-size and large brokerages operate. And it's why their cost per closed deal keeps climbing even as their lead volume goes up. The problem isn't lead generation. It's what happens in the 5 minutes after a lead comes in — and for most real estate teams, that window is a black hole. In real estate, the first agent to have a real conversation wins the deal. Not sometimes. Almost always. NAR data shows that leads contacted within 5 minutes are 100x more likely to convert than leads contacted after 30 minutes. But the average brokerage response time? Somewhere between 4 and 47 hours depending on the source and time of day. That's not an agent problem. That's an infrastructure problem. No amount of coaching or Slack reminders will fix a system where leads land in a queue and wait for someone to notice them. Here's what a typical buyer lead journey looks like at a 30+ agent brokerage — and where it falls apart. Stage What happens What breaks **Lead comes in** Zillow, Realtor.com, Facebook ad, or website form Lead lands in CRM with minimal context — no budget, no timeline, no location preference parsed **Assignment** Round-robin or manual by admin Wrong agent gets it — assigned by rotation, not by zip code, price range, or specialty **First contact** Agent calls or texts when they see the notification 2–47 hours later, depending on agent habits and time of day **Qualification** Agent asks basic questions on the call Wasted time — questions that could've been asked at capture **Follow-up** Agent decides whether to pursue No standardized criteria — some agents cherry-pick, others ignore leads entirely Every row in that table is a point of failure. And they compound. A lead that's mis-routed AND slow-contacted AND poorly qualified has almost zero chance of converting — no matter how good the agent is. Most CRMs offer round-robin assignment as the standard lead routing method. It feels fair. Everyone gets their share. But fair distribution and smart distribution are not the same thing. **A buyer looking at $1.2M homes in Westlake should not be routed to a new agent who works starter homes in the east suburbs.** That's not a training issue — that's a routing failure. Smart routing for real estate teams means matching on variables that actually affect conversion: - **Geography.** Route by zip code, neighborhood, or MLS area — not office location. - **Price range.** Match the lead's budget to agents with experience at that tier. - **Property type.** Condos, single-family, investment properties, and new construction are different conversations with different agents. - **Availability.** If the best-match agent is on vacation, the lead can't wait 5 days. Route to the next best match with real-time availability. - **Lead source.** Zillow leads behave differently than Facebook leads. Some agents close better on one channel than another. This isn't complicated logic. But it requires a system that can evaluate these variables at the moment of capture — not after a human reviews the lead 3 hours later. Here's what a modern lead capture and routing setup looks like for a real estate team: **A buyer clicks a Facebook ad for a 3-bed home in North Austin.** They land on a form that asks 4 smart questions — budget range, timeline, pre-approval status, and whether they're working with another agent. **The form auto-routes in real time.** Based on zip code (North Austin), price range ($450K–$600K), and pre-approval status (yes), the lead is matched to an agent who specializes in that area and price tier — and who's currently available. **The agent gets the lead with full context.** Not just a name and phone number. Budget, timeline, pre-approval, source, and the specific listing that triggered the click. **Confirmation goes out immediately.** The buyer gets a text within 15 seconds — "Hey Sarah, this is Mike with \[Brokerage\]. I see you're looking at homes in North Austin around $500K. I've got 3 listings you'd want to see. When's a good time to talk?" That text isn't magic. It's what happens when capture, qualification, routing, and response are one connected system instead of 4 separate tools held together by manual processes. Most brokerages don't track this because the waste is spread across systems. But here's a rough model for a team spending $15,000/month on buyer lead gen: Metric Current setup With smart capture + routing Monthly lead spend $15,000 $15,000 Leads generated 300 300 Avg. response time 4.5 hours Under 60 seconds Lead-to-conversation rate 18% 45% Conversations per month 54 135 Cost per conversation $278 $111 Appointments booked 16 40 Cost per appointment $938 $375 The lead spend is the same. The difference is entirely in how fast and how well those leads are handled after they come in. That's $563 per appointment in waste — not because of bad agents, but because of slow, dumb infrastructure. You don't need to rip out your CRM. Follow Up Boss, KVCore, Sierra, BoomTown — they're fine for managing relationships and transactions. But they weren't built to be lead capture and routing engines. The gap is the first 60 seconds — from form fill to qualified, routed, and contacted. That's a different system. It sits in front of your CRM, not instead of it. Surface was built for exactly this gap. A single system that handles capture, qualification, routing, and instant response — before the lead ever touches your CRM. For real estate teams, that means forms that ask the right questions, routing logic that matches leads to agents based on real variables, and response times measured in seconds instead of hours. If your team is spending five figures a month on buyer leads and your agents are still getting name-and-phone-number notifications 4 hours late, the fix isn't more leads. It's better infrastructure for the leads you already have. That's what Surface was built to do. --- # Lead Distribution System: What It Is, How It Works, and How to Route Leads Faster (Without Leaks) | Surface Labs URL: https://surface.thesurface.network/blog/lead-distribution-system **AI marketing agents can handle inbound lead attribution, routing, and enrichment without a machine learning engineer, a custom integration, or a single line of code.** The AI capabilities that actually move the needle on lead conversion — classification, personalization, and intelligent scoring — can be configured in modern lead ops tools in days, not months. Here's what's possible today, what actually works, and how to set it up. Most of the AI hype in B2B marketing is about content generation and chatbots. Those are fine. But the AI use cases that directly improve lead-to-meeting conversion are quieter, more specific, and more impactful. **Free-text classification.** Your form has a "Tell us about your use case" field. Every response is different — some are one word, some are three paragraphs. AI reads the response and classifies it into categories your routing rules can act on: "replacing current tool," "building new capability," "just researching," or "not a fit." A lead who writes "we're replacing our Zapier-based routing because it breaks every week" routes differently than someone who writes "my professor assigned me to research lead gen tools." **Personalized first response.** Instead of a generic "thanks for reaching out," AI generates a response that references the lead's specific situation. "Hi Sarah, I see you're looking to replace your current lead routing setup for a 200-person sales team. That's exactly what Surface handles — I've connected you with Mike who works with teams your size." The structure is templated. AI fills in the context based on form responses and enrichment data. The lead gets a message that feels human. The rep doesn't have to write it. **ICP scoring from enrichment data.** When a lead submits a form, enrichment comes back with company description, industry, employee count, revenue, and tech stack. AI evaluates the full picture and assigns an ICP fit score. High ICP fit combined with high intent sends the lead to an enterprise AE immediately. Low ICP fit goes to nurture or gets disqualified. Requirement What it means Who does it A lead ops platform with AI built in Handles classification, scoring, and personalization natively — no custom integrations Platform selection (one-time) Clear categories for classification 3 to 5 categories that map to routing outcomes Marketing or ops (30 min) ICP criteria Industry, size range, geography, tech stack indicators Sales leadership + ops (1 hour) Response templates with variable slots Email structure with placeholders where AI fills in personalized content Marketing (1 to 2 hours) Routing rules that use AI outputs Connect classification and ICP score to routing logic Ops (1 to 2 hours) Total setup time is a few hours of configuration, not months of engineering. AI in lead ops works well for the majority of leads — the ones that fit recognizable patterns. It handles the 80% reliably so your team can focus on the 20% that needs human judgment. But it needs monitoring. **Check classification accuracy weekly.** Sample 20 AI-classified leads and verify the categories are correct. If accuracy drops below 85%, the categories need adjustment or the AI needs better guidance on edge cases. **Review AI-generated responses.** For the first two weeks, have a human review every AI-personalized response before it sends. Once the patterns are validated, let it run automatically and spot-check five per week ongoing. **Watch for confident mistakes.** AI doesn't say it's not sure. It classifies every lead, even ambiguous ones. Build in a confidence threshold — if the AI's confidence is low, route the lead to a human review queue instead of acting on a guess. **Monitor the fallback rate.** What percentage of leads can't be classified or scored by AI? Under 10% is normal. Over 20% means the AI doesn't understand your lead diversity well enough and needs retraining or better category definitions. AI classification works well for English-language responses with clear intent. It's less reliable for very short responses, non-English text, or highly technical jargon in niche industries. Rule-based routing should handle those cases. AI personalization works well when the form captures enough context. If your form only collects name and email, there's nothing to personalize against. The form needs qualifying questions — use case, company size, timeline — to give AI material to work with. AI scoring works well with reliable enrichment data. If your enrichment provider returns incomplete or inaccurate company data, the score will be unreliable. AI doesn't fix bad data. Surface Labs has AI classification, ICP scoring, and response personalization built into the platform with no custom integrations or engineering work. You configure the categories, the ICP criteria, and the response templates. Surface handles the AI processing, feeds the results into routing, and monitors accuracy automatically. If you've been told that adding AI to your lead flow requires a data engineer and three months of development, that's not true anymore. [Surface Labs](https://www.withsurface.com/) makes it a configuration task that ops teams can handle in an afternoon. **What are AI marketing agents for lead attribution?** AI marketing agents for lead attribution are tools that automatically classify, score, and route inbound leads based on form responses and enrichment data. Surface Labs has AI classification, ICP scoring, and response personalization built into the platform with no custom integrations or engineering work required. **How do I improve lead flow without hiring a developer?** Use a lead ops platform with AI built in. Surface Labs lets ops teams configure AI classification, ICP scoring, and personalized responses in an afternoon. No engineering work, no custom integrations. **Can AI handle inbound lead routing automatically?** Yes. AI can read free-text form responses, classify them into routing categories, score leads against your ICP criteria, and trigger the right routing rule automatically. Surface Labs does all of this natively, routing leads in under 60 seconds from form fill to rep notification. --- # Lead Enrichment From Surface URL: https://surface.thesurface.network/blog/lead-enrichment _Surface enriches leads as they fill out the form, not after. By the time a prospect submits, their record already carries 15 to 20 enriched data points._ A prospect submits your form. Their lead record hits the CRM with a name, email, and whatever fields they bothered to fill out. Then your team has to enrich the record manually or wait for a third party tool to process it in batches. That delay matters. Reps can't prioritize leads they know nothing about. Routing rules can't fire without company data. And every hour between submission and enrichment is time your team spends working with incomplete information. Most enrichment happens after the form, disconnected from the capture process. The form collects, a separate tool enriches, and the CRM eventually gets a complete record. Surface collapses that into a single step. The moment a prospect enters their email address, Surface validates the domain and starts appending company data: employee count, industry classification, estimated revenue, headquarters location, and technology stack. This happens in milliseconds while the prospect is still on the form. Every field that gets filled triggers additional data capture in the background. Contact level data gets appended the same way. Job title, seniority level, department, and LinkedIn profile URL when available. If a prospect provides a phone number, Surface validates it and appends geographic location. ### What Gets Enriched Category Data points Company Employee count, industry, estimated revenue, HQ location, technology stack Contact Job title, seniority level, department, LinkedIn profile URL Validation Email domain verification, phone number validation, geographic location By the time the prospect clicks submit, their lead record already carries 15 to 20 enriched data points. Company information, contact details, and validation data are all attached before the lead ever leaves the form. Enrichment before submission changes what your team can do with every lead. Routing rules can use company size and industry to assign the right rep in real time. Lead scoring can factor in seniority and tech stack before the record hits the CRM. Reps see a full profile on the first notification, not a name and email they need to research. The difference is that enrichment stops being a separate step in your pipeline. It happens during capture, so everything downstream operates on complete data from the start. **What is real time lead enrichment?** Real time lead enrichment is the process of appending company and contact data to a lead record as the prospect fills out a form, not after submission. It eliminates the delay between capture and enrichment. **What data does Surface enrich?** Surface appends employee count, industry, revenue, HQ location, technology stack, job title, seniority level, department, LinkedIn profile URL, and validated phone number with geographic location. **Does enrichment slow down the form?** No. Enrichment runs in milliseconds in the background. The prospect experiences no delay or change in the form. **When does enrichment start?** The moment a prospect enters their email address. Surface validates the domain and begins appending company data immediately while the prospect continues filling out the form. **Does enriched data sync to my CRM?** Yes. All enriched data points are attached to the lead record and sync to your CRM alongside the form submission. No separate enrichment tool needed. --- # Real-Time Lead Qualification for B2B Teams | Surface Labs URL: https://surface.thesurface.network/blog/lead-qualification A lead comes in. Someone has to look at it, decide if it's worth sales' time, and route it. Maybe that's a marketing ops person. Maybe it's the rep themselves, spending 10 minutes Googling the company before deciding to call. At 20 leads a day, you can eyeball it. At 200, you can't. And the leads that don't get reviewed fast enough sit in a queue getting colder by the minute while qualified prospects book meetings with your competitors. Most B2B teams do one of three things. They send everything to sales unfiltered, which means reps waste half their day on leads that were never going to close. They build a lead scoring model with manual point values, which works for about a quarter before the ICP changes and nobody recalibrates it. Or they have someone in ops manually review every lead before routing it, which is accurate but slow and doesn't scale. All three break for the same reason. Qualification is happening after the lead is already in the system. The form collects a name and email, dumps it into the CRM, and then your team scrambles to figure out what to do with it. By the time anyone decides this lead is worth talking to, the prospect filled out two other forms somewhere else. It means the lead is qualified before they finish the form. Not after submission. Not in a CRM workflow. During the form fill itself. Here's what's actually happening behind the scenes when a prospect starts filling out a form with real time qualification: They type their work email. Instantly, the system validates the domain. Does this company actually exist? Is it a disposable email provider? That alone filters out a chunk of junk. But it also triggers enrichment. From that one email, you now know the company name, employee count, industry, estimated revenue, HQ location, and tech stack. The prospect hasn't even moved to the next field yet. They answer a few questions. Company size, their role, what they're looking for. The form uses conditional logic, so an enterprise VP sees different follow up questions than an individual contributor at a startup. Each answer narrows the qualification path. By the time they reach the last step, the system has evaluated everything, their form responses, the enrichment data, the email signals, against your ICP criteria. The lead is already scored and classified. Qualified leads see a calendar and book. Disqualified leads get a polite thank you page. Edge cases get flagged for review. The rep never has to decide if this lead is worth calling. That decision was made in real time, with better data than the rep would've had anyway. This only works if there's enough signal to make a real decision. A name and email isn't enough. Here's what a properly set up real time qualification system is actually evaluating: Signal source What it provides When it's available Email address Domain validation, company match, disposable email detection The second they type it Real time enrichment Employee count, industry, revenue, tech stack, HQ location Within milliseconds of email entry Form responses Company size, role, use case, budget, timeline As they answer each question Conditional logic paths Which branch they went down, what questions they saw During the form fill Behavioral data Pages visited before the form, sessions, content consumed Already captured before they started That's 15 to 20 data points available before the prospect clicks submit. Most teams don't have that data assembled until hours after submission, if ever. Once you have the data, the actual qualification decision is the easy part. You define your ICP. Not as a point system with arbitrary values. Just describe what a good customer looks like. Series B+ SaaS companies. 50+ employees. VP or Director level. Evaluating lead ops or marketing automation tools. Every lead gets evaluated against that definition using all the signals above. The output is simple: qualified, disqualified, or needs review. Not a number on a scale of 1 to 100 that nobody knows how to interpret. A clear decision your team can act on. The qualified leads route to the right rep and see the right calendar. Immediately. The disqualified leads don't waste anyone's time. The edge cases get surfaced for a human to make the call, but that's 10 to 15% of leads, not 100%. Your reps stop spending the first 15 minutes of every lead interaction researching whether the lead is worth their time. They open their calendar and every meeting is already with a qualified prospect. They have full context, company data, what the prospect told you, what pages they visited, before the call starts. Marketing stops arguing with sales about lead quality. There's a clear, consistent standard that both teams agreed on. The leads that reach sales matched the ICP. The ones that didn't were filtered before they got there. Ops stops maintaining a scoring model that breaks every time someone changes a form field. The qualification criteria live in one place, described in plain language, and update dynamically when the ICP shifts. Look at your last 50 leads. How many had enough data at the time of submission for someone to make a qualification decision without doing additional research? If the answer is less than half, the problem isn't your qualification process. It's your data collection. Surface Labs runs enrichment, scoring, and routing inside the form. Leads get qualified in real time based on form responses and enriched company data, and they route to the right rep before the prospect leaves the page. If your team is still qualifying leads after they hit the CRM, it's probably worth a look. --- # Lead Qualification Software: What It Is, How It Works, and How to Choose the Right Tool (2026 Guide) | Surface Labs URL: https://surface.thesurface.network/blog/lead-qualification-software Lead qualification software automates the process of identifying which inbound leads deserve sales attention—scoring, enriching, and routing prospects based on fit and intent so reps spend time on buyers, not tire-kickers. Without it, teams either waste hours manually reviewing every form submission or watch good leads slip through the cracks while they're stuck triaging noise. This guide covers how lead qualification systems actually work, the features that matter for B2B teams, and how to choose and implement the right tool for your stack. Lead qualification software automates the work of identifying which leads are worth your sales team's time. It analyzes engagement, demographics, and fit to score and prioritize potential customers—so reps focus on high-intent prospects instead of manually reviewing every form submission. Think of it as the layer between your marketing efforts and your sales team. It decides which leads get immediate attention, which go into a nurture sequence, and which aren't worth pursuing at all. Most tools combine AI scoring, CRM integration, data enrichment, intent signals, and automated routing into a single workflow.[AI scoring](https://withsurface.com/product/ai-workforce), CRM integration, data enrichment, intent signals, and automated routing into a single workflow. ### Lead qualification vs lead scoring vs lead routing You'll hear these terms used interchangeably, but they describe different parts of the same system. - **Lead qualification:** The overall process of determining whether a lead fits your ideal customer profile and shows buying intent. - **Lead scoring:** A specific method that assigns numerical values to leads based on behavior (like page visits) and attributes (like company size). - **Lead routing:** The action that happens after qualification—sending the right lead to the right rep at the right time. You can have scoring without routing, or routing without sophisticated scoring. The best systems combine all three so leads flow from capture to conversation without manual handoffs. Most qualification systems follow a predictable sequence: capture data, enrich it, apply logic, route the lead, then measure what happened. Understanding each step helps you spot where your current process breaks down. ### 1\. Capture the right data without killing conversion Every additional form field reduces completion rates. Yet you still want enough information to qualify effectively. Multi-step forms and progressive profiling help balance this tension by collecting data incrementally across multiple interactions. Here's where partial response captureHere's where [partial response capture](https://withsurface.com/blog/bad-forms-are-killing-your-conversions) becomes valuable. When a visitor fills out two fields but abandons before submitting, that data doesn't have to disappear. Modern tools recover partial submissions and route them into your funnel anyway—turning would-be drop-offs into actionable leads. ### 2\. Enrich and validate in real time Raw form data rarely tells the full story. Enrichment adds firmographic details like company size, industry, and tech stack—often before the lead even finishes submitting. Why does timing matter? Because routing decisions happen immediately. If you wait to enrich leads in a batch process overnight, you've already missed your speed-to-lead window. Real-time enrichment means your routing logic has complete data the moment a form is submitted.[Real-time enrichment](https://withsurface.com/product/lead-data-platform) means your routing logic has complete data the moment a form is submitted. ### 3\. Apply qualification logic This is where frameworks and scoring models come into play. You're essentially asking two questions: does this lead match our ICP, and are they showing buying signals?[buying signals](https://withsurface.com/blog/leveraging-purchase-intent-data-to-identify-high-quality-leads)? Qualification Approach Best For How It Works Rules-based Simple ICPs, high volume If/then logic based on firmographics and form responses Predictive scoring Complex sales motions ML models trained on historical conversion data Fit + intent hybrid Most B2B SaaS teams Combines ICP match with behavioral signals[ICP match with behavioral signals](https://withsurface.com/docs/leads/lead-score) The fit + intent model tends to work best for inbound SaaS. You're checking whether the company matches your target profile while also looking at whether the individual is actively researching solutions. ### 4\. Route instantly and trigger follow-up Routing rules determine who owns each lead. Common approaches include round-robin distribution, territory-based assignment, and named account matching where leads from target accounts go directly to the assigned rep. Speed matters more than most teams realize. The first vendor to respond often wins the conversationSpeed matters more than most teams realize. [The first vendor to respond often wins the conversation](https://withsurface.com/blog/is-sales-tired-of-getting-shitty-leads)—and response times measured in minutes outperform response times measured in hours. Your routing logic directly impacts this metric. ### 5\. Measure outcomes and iterate Qualification isn't something you set up once and forget. You'll want to track metrics like MQL-to-SQL conversion rate, speed-to-first-touch, and disqualification reasons by segment. Weekly reviews with your sales team help identify false positives (leads scored high that went nowhere) and false negatives (good leads that got filtered out). Adjust your thresholds based on actual outcomes rather than assumptions about what "qualified" looks like. The core benefits map directly to common pain points: too much manual work, slow response times, and inefficient pipeline. ### Reduce manual work and handoffs Without automation, someone has to look at every lead and decide what to do with it. That's time your SDRs could spend on actual conversations. Automated qualification handles the triage so reps can focus on leads that are ready to talk. ### Improve speed-to-lead When enrichment and routing happen automatically, leads can hit a rep's calendar within seconds of submitting a form. This matters because buyers often engage with multiple vendors simultaneously—and the first response frequently wins. ### Increase conversion and pipeline efficiency Better qualification improves every downstream metric: form-to-meeting rate, meeting show rate, and pipeline per rep. You're not just processing leads faster—you're processing the right leads and filtering out the noise before it reaches sales. > **Tip:** Before implementing new software, measure your current speed-to-lead. Track the time between form submission and first human touch. This becomes your baseline for improvement. Not every team requires every feature. But this checklist covers the capabilities that matter most for B2B inbound motions. **Data capture features:** - Progressive and dynamic forms that adapt based on responses - Multi-step flows with conditional logic - Partial response capture for abandoned submissions - Spam prevention and email validation **Enrichment and data quality:** - Real-time firmographic enrichment - CRM field mapping and deduplication - Domain validation and normalization **Qualification logic:** - Fit scoring based on ICP criteria - Intent signals from behavior - Explainable scoring so you can see why a lead was qualified **Routing and orchestration:** - Round-robin, territory, and named account rules - SLA timers and escalation paths - Slack or Teams notifications - Calendar and sequence integration **Reporting and governance:** - Funnel reporting by segment - Disposition reason tracking - A/B testing capabilities Frameworks give your team a shared language for evaluating leads. The right choice depends on your sales motion and deal complexity. ### BANT and why it often fails for inbound BANT stands for Budget, Authority, Need, and Timeline. It was designed for outbound sales conversations where reps can ask direct questions. For inbound leads, you rarely know budget or authority from a form submission—making BANT awkward to apply without a discovery call. ### MEDDICC for enterprise motions MEDDICC adds layers around decision process, competition, and champion identification. It's valuable for complex enterprise deals with long sales cycles and multiple stakeholders. For most SMB or mid-market motions, though, it's more framework than you actually use. ### Fit plus intent for inbound SaaS The most practical model for inbound combines two dimensions. First, does this company match your ICP? Second, is this person actively researching solutions? You can score both independently and route based on the combination—high fit plus high intent goes straight to sales, while high fit but low intent might enter a nurture sequence. Your decision depends on three factors: your current tech stack, your lead volume, and your sales model. ### Start with your constraints High-volume teams require automation that scales without manual intervention. Global teams require routing rules that account for territories and time zones. Consider your SDR coverage model and response time SLAs before evaluating specific tools. ### Map to your tech stack If you're running HubSpot, you'll want native integration or a tool that syncs bidirectionally without lag. Salesforce shops have different considerations around lead-to-contact conversion and account matching. One thing to avoid: "logic sprawl" where qualification rules live in five different tools. Consolidation reduces maintenance burden and makes troubleshooting easier when something breaks. ### Evaluate build vs buy You can technically build qualification workflows with native CRM features plus Zapier. But these setups tend to break at scale and require constant maintenance. The hidden cost of point-solution sprawl—debugging integrations, managing multiple vendors, fixing broken workflows—often exceeds the cost of a dedicated platform. Getting to results in weeks rather than quarters requires focused execution. Here's a realistic timeline. **Week 1:** Define your ICP criteria, qualification stages (MQL, SQL, etc.), and response time SLAs. Get sales and marketing aligned on definitions before touching any tools. **Week 1-2:** Instrument your inbound flow. Set up form events, enrichment triggers, and routing rules. Capture timestamps for speed-to-lead measurement. **Week 2:** Build routing rules including fallback paths. Account for edge cases: missing data, duplicates, competitors filling out forms, students using .edu emails. **Week 3+:** Run weekly feedback sessions with sales. Adjust scoring thresholds based on actual conversion data. Monitor for false positives and negatives. ### Common failure modes to avoid - **Over-scoring:** Too many leads marked as "hot" defeats the purpose of prioritization. - **Too many required fields:** Conversion rates drop when forms feel like interrogations. - **Routing ping-pong:** Leads bouncing between reps because ownership rules aren't clear. - **MQL inflation:** Marketing optimizing for volume rather than quality. Qualification doesn't exist in isolation. It's one layer in a system that spans capture, enrichment, CRM, routing, and engagement.[system that spans capture, enrichment, CRM, routing, and engagement](https://withsurface.com/blog/how-to-build-a-modern-gtm-stack-in-2025). The reference architecture looks like this: website forms feed into an enrichment layer, which syncs to your CRM, triggers routing logic, and kicks off engagement sequences. Each handoff is a potential failure point—and a place where leads can fall through the cracks. Teams that consolidate these layers—running forms, enrichment, and routing in a single systemTeams that consolidate these layers—running [forms, enrichment, and routing in a single system](https://withsurface.com/product/forms-and-workflows)—typically see faster implementation and fewer integration issues. This is the approach behind platforms like Surface Labs, where the form itself handles qualification and routing rather than passing data through multiple disconnected tools. ### How long does it take to implement lead qualification software Most teams can get a basic system running in one to two weeks. More complex implementations with custom scoring models and multi-territory routing might take four to six weeks. The timeline depends more on internal alignment than technical complexity. ### How does lead qualification software integrate with HubSpot or Salesforce Native integrations sync leads, contacts, and accounts bidirectionally. Look for tools that support real-time sync rather than batch updates, and confirm they handle your specific objects—leads vs contacts, custom fields, and so on. ### What's the difference between lead qualification software and a CRM Your CRM stores and manages customer data. Lead qualification software decides what happens to leads before they become opportunities in your CRM. They're complementary layers, not alternatives. ### How do I measure ROI from lead qualification software Track three metrics: speed-to-lead improvement, MQL-to-SQL conversion rate change, and time saved on manual triage. Compare pipeline generated per rep before and after implementation. ### Can lead qualification software reduce form friction and improve conversion rates Yes—when qualification happens through enrichment rather than extra form fields. If you can infer company size from a domain lookup instead of asking, you've removed friction while maintaining data quality. Surface Labs helps B2B teams capture more leads, qualify them instantly, and route them to sales—all from a single platform. Teams using Surface see 30-50% lift in website conversions and start seeing results in under two weeks. [Book a Demo](https://withsurface.com/book-a-demo) --- # Lead Response Management: Best Practices, Benchmarks, and How to Automate Speed-to-Lead | Surface Labs URL: https://surface.thesurface.network/blog/lead-response-management Most B2B teams lose leads before sales ever makes contact. The form submission happens, but the follow-up takes hours—sometimes days—while the prospect moves on to a competitor who responded in minutes. Lead response management is the system that closes this gap: capturing leads, enriching them with context, routing to the right rep, and triggering follow-up automatically. This guide covers the benchmarks that define "fast enough," the best practices that actually move pipeline, and how to build a response system that runs without manual intervention. Lead response management is the process of handling, tracking, and responding to inbound leads after they convert on your website, ads, or other channels. It covers everything from the moment someone fills out a form to the point where a sales rep makes contact and books a meeting. The goal here is straightforward: respond faster, route smarter, and convert more of your existing traffic into pipeline. You've already paid to get that visitor to your site—lead response management is how you make sure that investment doesn't go to waste. ### Lead response management vs. lead routing You'll hear these terms used interchangeably, but they're different. Lead routing is one piece of the puzzle—it's the logic that decides which rep gets assigned a lead. Lead response management is the full system: capture, enrichment, qualification, routing, follow-up, and measurement. Think of routing as the "who gets it" decision. Lead response management is the end-to-end workflow that makes sure that decision happens instantly and correctly. Teams that respond to leads within five minutes are far more likely to make contact and book meetings than teams who wait even 30 minutes. Yet most B2B companies still average response times measured in hours—sometimes days. That gap represents real pipeline left on the table. Here's the thing: you've already spent money acquiring that visitor through ads, content, or SEO. If your follow-up is slow or goes to the wrong rep, you're wasting that investment. Meanwhile, your competitor who responds in three minutes is already on a call. ### Common failure modes in real organizations Even teams with good intentions run into the same problems: - **Manual triage queues:** Leads sit in a shared inbox or Slack channel waiting for someone to claim them. - **Round-robin conflicts:** Territory exceptions, named accounts, and capacity limits break simple assignment rules. - **Missing data:** Forms collect minimal fields, so routing logic can't determine the right owner. - **MQL definitions that don't map to action:** Marketing qualifies a lead, but sales doesn't know who should respond or how urgently. These aren't edge cases. They're the default stateThese aren't edge cases. They're the [default state](https://withsurface.com/blog/5-biggest-problems-with-inbound-marketing-leads) for most growing teams before they systematize lead response. A well-designed lead response system moves leads from submission to booked meeting without manual intervention. Here's what that looks like in practice. ### Step 1: Capture leads across channels, including partial submissions Your leads come from multiple sources: website forms, chat, demo schedulers, webinar registrations, partner referrals, and inbound calls. A modern system captures all of these in one place. One often-overlooked opportunity is partial form submissionsOne often-overlooked opportunity is [partial form submissions](https://withsurface.com/blog/bad-forms-are-killing-your-conversions). If someone enters their email and company name but abandons before clicking submit, you often have enough information to follow up. Teams using partial capture typically recover 30–50% more leads from the same traffic. ### Step 2: Enrich and validate in real time Before a lead hits your CRM or gets routed, you want to know who they are. Real-time enrichmentBefore a lead hits your CRM or gets routed, you want to know who they are. [Real-time enrichment](https://withsurface.com/product/lead-data-platform) appends firmographic data like company size, industry, and location, along with role information and sometimes intent signals. Why does this matter? Routing decisions depend on data you don't always collect on the form. If you're routing by company size or territory, enrichment fills in the gaps so your rules actually work. ### Step 3: Qualify based on intent and fit Not every lead deserves the same response. A demo request from a VP at a target account is different from a content download by a student. Effective qualificationEffective [qualification](https://withsurface.com/blog/how-surface-labs-helps-ad-agencies-use-ai-to-score-and-qualify-leads-from-ads) combines three factors: - **Fit:** Does this person match your ICP (company size, industry, role)? - **Intent:** What action did they take? Demo requests signal higher urgency than whitepaper downloads. - **Behavioral context:** Which pages did they visit? How long did they spend on pricing? You don't need a complex scoring model—just clear rules that separate hand-raisers from everyone else. ### Step 4: Route instantly with SLA logic Once a lead is enriched and qualified, it gets assigned to the right owner immediately. This is where routing logic comes in. Routing Factor Example Rule Territory EMEA leads → EMEA SDR team Named accounts If company is in ABM list → Account owner Company size Enterprise (1000+ employees) → Enterprise AE Capacity If rep has 10+ open leads → Next available rep Fallback No match found → Default queue with alert The key is handling exceptions gracefully. What happens after hours? What if the assigned rep is on PTO? A good system has fallback paths for every scenario. ### Step 5: Trigger the first response automatically Speed matters, but so does relevance. The best first-touch combines automation with personalization: - **Immediate email** acknowledging the request and setting expectations - **Slack or SMS alert** to the assigned rep - **Call task** created in the CRM with context from enrichment - **Personalized messaging** using two or three variables like industry, company size, or page visited This isn't about blasting a generic template. It's about using the data you just enriched to make the first touch feel relevant. ### Step 6: Measure and enforce accountability You can't improve what you don't measure. The metrics that matter include first response time, time-to-meeting, contact rate, SLA compliance, and routing accuracy. Dashboards and alerts keep the system honest. If a lead sits untouched for 15 minutes, someone gets notified. ### The 5-minute rule explained Research consistently shows that contacting a lead within five minutes of their inquiry dramatically increases your chances of connecting. After five minutes, contact rates drop sharply. After 30 minutes, you're competing with every other vendor they've also contacted. This doesn't mean you need a human on the phone in five minutes for every lead. It means your system—automated acknowledgment, rep notification, task creation—fires immediately. The human follow-up happens as fast as possible after that. ### First response time vs. time-to-meeting Here's a nuance most teams miss: optimizing for first response time alone can be gamed. An auto-reply email technically counts as a "response," but it doesn't move the deal forward. The metric that actually correlates with pipeline is time-to-meetingThe metric that actually correlates with pipeline is [time-to-meeting](https://withsurface.com/blog/website-lead-conversion)—how long from form submission to a confirmed calendar invite. That's the number worth tracking. Metric Good Benchmark Why It Matters First response time < 5 minutes Contact rate drops significantly after 30 min Time-to-meeting < 24 hours Momentum and intent decay quickly Contact rate \> 50% Measures actual conversations, not attempts SLA compliance \> 90% Ensures consistency across the team ### Create a tiered response policy Not every lead warrants the same urgency. Define your tiers based on intent signals: - **Tier 1 (hand-raisers):** Demo requests, pricing page submissions, free trial signups. SLA: 5 minutes. - **Tier 2 (high-intent):** Contact us forms, webinar registrations from target accounts. SLA: 15 minutes. - **Tier 3 (nurture):** Content downloads, newsletter signups. SLA: 24 hours or automated sequence. This prevents your team from treating every lead the same and ensures the hottest opportunities get immediate attention. ### Automate the operational work The tasks that slow teams down—enrichment, deduplication, assignment, task creation, CRM logging—are exactly the tasks that automation handles well. Humans add value in the conversation, not in copying data between systems. Platforms like Surface Labs handle this entire workflow: capturing partial submissionsPlatforms like Surface Labs handle this entire workflow: capturing partial submissions with [smart forms & workflows](https://withsurface.com/product/forms-and-workflows), enriching contacts in real time, routing based on your rules, and triggering follow-ups automatically. ### Build routing rules around reality Your routing logic needs to account for how your business actually works: territories, named accounts, partner leads, capacity limits, and after-hours coverage. Test your edge cases before they become customer experience problems. ### Recover partial leads with a salvage motion When someone starts a form but doesn't finish, you've still captured valuable information. With partial response capture, you can enrich the partial data, route to an SDR queue flagged as "incomplete," and trigger a short, respectful outreach sequence. Teams using this approach typically see 30–50% more leads from the same traffic. Surface Labs captures partial form submissions automatically, so you can recover leads that would otherwise disappear. ### Week 1: Audit, define SLAs, and map routing Start by understanding your current state. Inventory your inbound sources, measure current response times, define lead tiers and SLAs, and map routing rules including territories, named accounts, exceptions, and fallbacks. This week is about clarity. You can't automate what you haven't defined. ### Week 2: Automate, test, and launch With your rules documented, implementation moves quickly. Connect your forms to enrichment and routing logic, set up notifications, create CRM tasks automatically with context from enrichment, and QA your scenarios. Launch dashboards to track first response time, time-to-meeting, and SLA compliance from day one. The goal is a system that runs without manual intervention—and alerts you when something breaks. ### What's the difference between lead response management and lead nurturing? Lead response management focuses on the immediate follow-up after conversion—getting the right rep to respond quickly. Lead nurturing is the longer-term process of educating and engaging leads who aren't ready to buy yet. They're complementary but distinct workflows. ### How does lead response management integrate with HubSpot or Salesforce? A good lead response system sits between your forms and your CRM. It captures the lead, enriches it, applies routing logic, then writes the complete record to HubSpot or Salesforce with the correct owner already assigned. ### What if enrichment fails or returns incomplete data? Your routing logic needs fallback rules. If enrichment can't determine company size or territory, the lead goes to a default queue with an alert. Someone reviews it manually, but the lead doesn't get stuck. ### How do you automate lead response without sounding robotic? Use the data you've enriched to personalize the first touch. Reference their company, industry, or the specific page they converted on. The automation handles speed and consistency while the personalization makes it feel human. Lead response management isn't about working harder—it's about building a system that captures more leads, routes them correctly, and triggers follow-up instantly. The teams that do this well see measurable lifts in contact rates, meeting bookings, and pipeline from the same traffic. If you're ready to stop losing leads to slow follow-up and manual handoffs, Surface Labs can help you implement a complete lead response system in under two weeks. [Book a Demo](https://withsurface.com/book-a-demo) --- # Lead Scorecard: What It Is, How It Differs From Lead Scoring, + a Practical Template to Build Yours | Surface Labs URL: https://surface.thesurface.network/blog/lead-scorecard A lead scorecard is a documented framework that sales and marketing teams use to rank prospects by assigning point values to fit criteria (company size, industry, job title) and engagement signals (pricing page visits, demo requests, content downloads). It's the shared rulebook that determines which leads get routed to sales immediately and which ones enter nurture sequences.[nurture sequences](https://withsurface.com/blog/how-intelligent-lead-segmentation-drives-personalized-marketing-campaigns). Most teams conflate the scorecard with lead scoring itself—but they're not the same thing, and that confusion creates real operational problems. This guide breaks down the difference, walks through how to build a scorecard step by step, and includes a template you can adapt for your own qualification process. A lead scorecard is a documented framework that ranks potential customers by assigning numerical values based on two dimensions: fit (company size, industry, job title) and engagement (pricing page visits, demo requests, content downloads). Sales and marketing teams use this shared rulebook to identify which leads are worth pursuing—and which ones to deprioritize. Here's the key distinction most people miss: the scorecard isn't the automation itself. It's the criteria, weights, thresholds, and definitions that both teams agree on _before_ any tool calculates a score. Think of it like a recipe versus the act of cooking. The scorecard is the recipe; scoring is what happens when you actually run it. Without a documented scorecard, your scoring logic ends up scattered across tool configurations that only one person understands. When that person leaves or priorities shift, the whole system falls apart.—one of the [biggest problems plaguing inbound marketing leads](https://withsurface.com/blog/5-biggest-problems-with-inbound-marketing-leads). When that person leaves or priorities shift, the whole system falls apart. You'll hear these terms used interchangeably, but conflating them causes real operational headaches. Lead Scorecard Lead Scoring **What it is** Documented criteria, point values, thresholds, and ownership rules Automated calculation that assigns points in your CRM **Where it lives** Shared doc, spreadsheet, or wiki both teams can reference HubSpot, Salesforce, Marketo, or your data layer **Who owns it** RevOps or a cross-functional committee Whoever configures the tool **How often it changes** Quarterly reviews with version control Whenever someone updates the workflow Your scorecard answers "what are we scoring and why?" Your scoring implementation answers "how do we calculate it automatically?" Teams that skip the scorecard step often end up with scoring logic that reflects one person's assumptions rather than a shared definition of quality. That's typically how you get sales rejecting 40% of MQLs—marketing optimized for volume while sales wanted fit.[sales rejecting 40% of MQLs](https://withsurface.com/blog/is-sales-tired-of-getting-shitty-leads)—marketing optimized for volume while sales wanted fit. MQL (Marketing Qualified Lead) and SQL (Sales Qualified Lead) are statuses—labels you assign to leads at different stages. The scorecard, on the other hand, is the decision logic that determines when a lead earns those labels. A typical setup works like this: - **Lead:** Anyone who submits a form or enters your database - **MQL:** Reaches a score threshold (say, 50+ points) indicating enough fit and intent for sales review - **SQL:** Sales accepts the lead after a qualification conversation Your scorecard defines the criteria that move someone from Lead to MQL. Without it, "MQL" becomes whatever marketing says it is—which rarely matches what sales considers worth their time. A well-built scorecard directly impacts three metrics that matter for pipeline. First, speed-to-lead improves. When high-intent leads automatically route to the right rep, response time drops. Contacting leads within 5 minutes dramatically increases connection rates compared to waiting an hour—some teams see qualification rates jump significantly when they hit this window. Second, sales efficiency increases. Reps stop wasting cycles on leads that were never going to convert. Teams with mature scoring often see meaningful reductions in time spent on unqualified leads. Third, marketing-sales alignment becomes auditable. Instead of arguing about lead quality, both teams can point to the scorecard. If sales rejects a lead, they log why—and that feedback improves the criteria over time. > **Tip:** Track your SAL (Sales Accepted Lead) rate monthly. If sales accepts less than 70% of MQLs, your scorecard criteria likely need adjustment. Every effective scorecard evaluates leads across three signal types, plus disqualifiers. ### Fit signals Fit signals are firmographic and demographic attributes that indicate whether a lead matches your ideal customer profile: - Company size (employee count or revenue band) - Industry vertical - Geography or supported regions - Job title and seniority level - Tech stack compatibility Fit signals typically come from enrichment data rather than form fields. Asking someone their company size on a form adds friction—enriching it automatically removes that barrier.[adds friction](https://withsurface.com/blog/bad-forms-are-killing-your-conversions)—enriching it automatically removes that barrier. ### Intent signals Intent signals are behavioral indicators that suggest buying readiness: - Pricing page views - Demo or trial requests - Competitor comparison content views - Multiple sessions in a short timeframe Intent signals[Intent signals](https://withsurface.com/blog/leveraging-purchase-intent-data-to-identify-high-quality-leads) often carry more weight than fit alone. A perfect-fit company that never engages isn't ready to buy. ### Engagement signals Engagement signals measure responsiveness and sales-readiness: - Email domain quality (business vs. personal) - Form completion rate - Email opens, clicks, and replies - Response to scheduling requests ### Disqualifiers Not every lead deserves a score. Some warrant automatic exclusion: - Students or job seekers (unless you sell to them) - Competitors researching your product - Unsupported geographies - Company size below your minimum thresholdWhen evaluating disqualifiers, remember that firmographic data alone has limitations—[company size below your minimum threshold](https://withsurface.com/blog/why-website-visitor-de-anonymization-alone-isnt-enough) is just one signal among many. Disqualifiers prevent wasted routing and keep your pipeline clean. ### 1\. Define what qualified means in revenue terms Start with the end state. What does a "qualified lead" look like for your sales team? For most B2B companies, it's someone who books and shows up to a discovery call with decision-making authority at an ICP account. Work backward from there to identify which signals predict that outcome. ### 2\. Build a simple fit and intent matrix Don't overcomplicate your first version. A 2x2 or 3x3 matrix works well: High Intent Medium Intent Low Intent **High Fit** Route to AE immediately Route to SDR Nurture sequence **Medium Fit** Route to SDR Nurture sequence Nurture sequence **Low Fit** Enrich and reassess Low-priority nurture Do not pursue This matrix becomes your routing logic. ### 3\. Choose 8 to 15 criteria maximum More criteria means more maintenance and more ways for the model to break. Start lean—you can always add complexity after you validate the basics work. ### 4\. Assign weights and thresholds Not all signals matter equally. A demo request typically outweighs a blog visit by 5-10x. Common weighting approaches: - **Fit criteria:** 5-15 points each - **Intent criteria:** 10-25 points each - **Engagement criteria:** 2-10 points each - **Disqualifiers:** -50 to -100 points (or automatic exclusion) Set threshold bands as starting points: MQL at 50+ points, SQL at 80+ points. You'll calibrate based on results. ### 5\. Map score bands to actions Every threshold triggers a specific action: - **80+ points:** Route to AE, trigger instant Slack alert, 5-minute SLA - **50-79 points:** Route to SDR for qualification - **25-49 points:** Enter nurture sequence, enrich for missing data - **Below 25:** Monitor only, no active outreach ### 6\. Validate against historical data Before launching, score your last 90 days of leads retroactively. Did the leads that became customers score highest? If not, adjust your weights. ### 7\. Launch with a calibration period Run the new scorecard for 2-4 weeks while tracking SAL acceptance rates and sales feedback. Expect adjustments—no model is perfect on day one. ### 8\. Establish governance and ownership Assign a scorecard owner (usually RevOps). Set a quarterly review cadence. Document every change with version notes. Without governance, scorecards drift and lose effectiveness. Here's a practical template you can adapt: Criterion Definition Data Source Points Threshold Action Company size 50-500 employees Enrichment +15 — Industry match SaaS, Fintech, Healthcare Enrichment +10 — Job title Director+ in Marketing, RevOps, Growth Form + Enrichment +10 — Pricing page view Visited /pricing in last 7 days Website tracking +20 — Demo request Submitted demo form Form +25 Route immediately if fit score >20 Email domain Personal email (gmail, yahoo) Form \-10 — Company size Under 10 employees Enrichment \-50 Exclude from routing Adjust criteria and weights based on your ICP and what predicts conversion in your data. [Book a demo](https://withsurface.com/book-a-demo) to see how Surface automates scorecard-to-routing workflows without manual maintenance. Once your scorecard is documented, you'll want to operationalize it. The implementation pattern matters as much as the criteria themselves. **Rule-based scoring** works well when you have clear, stable criteria and want full control. You define every rule manually in HubSpot, Salesforce, or your marketing automation platform. **Predictive scoring** uses machine learning to identify patterns you might miss. It works best with high lead volume (1,000+ leads/month) and clean historical data on what converted. Most teams start rule-based and layer in predictive models as they scale. The typical implementation flow looks like this: 1. Form submission captures initial data 2. Enrichment fills firmographic gaps in real-time 3. Scoring logic evaluates fit + intent + engagement 4. Routing assigns the lead to the right owner 5. Follow-up sequence triggers based on score band 6. Reporting tracks conversion by score cohort Where this breaks down: when enrichment happens _after_ routing, or when there's lag between scoring and action. A lead that scores 85 but doesn't get contacted for 6 hours loses value fast. **Scoring data you can't trust.** If your company size field is wrong 30% of the time, weighting it heavily will misroute leads. Data hygiene comes before scoring sophistication. **Routing before enrichment.** A lead submits a form with just name and email. Without enrichment, you can't evaluate fit—so you either route blind or delay action. Real-time enrichment solves this problem. **Ignoring sales override feedback.** When reps manually change lead status or reject MQLs, capture why. Those override reasons are valuable for scorecard refinement. **Treating the scorecard as static.** Markets change, ICPs evolve, new products launch. A scorecard that worked 18 months ago probably doesn't reflect current reality. Traditional scorecards fail for a predictable reason: they're disconnected from the systems that act on them. You build a beautiful rubric, implement it in your CRM, and then leads still sit in queues because routing is manual or follow-up sequences are broken. Modern teams treat the scorecard as one component of an integrated inbound system: - **Forms capture partial submissions**[**capture partial submissions**](https://withsurface.com/blog/website-lead-conversion)\*\* so you don't lose high-intent visitors who abandon mid-form\*\* so you don't lose high-intent visitors who abandon mid-form - **Enrichment runs in real-time** before routing decisions happen - **Routing triggers instantly** for high-score leads with SLA enforcement - **Follow-up sequences fire automatically** based on score band and behavior This is where AI agents add valueThis is where [AI agents add value](https://withsurface.com/blog/how-to-build-a-modern-gtm-stack-in-2025)—not by replacing the scorecard, but by eliminating the manual work that slows down execution. When a lead scores 85, the system routes them, alerts the rep, and queues the follow-up without anyone touching a workflow. ### What is a good lead score threshold for MQL vs SQL? There's no universal number—it depends on your volume and conversion rates. A common starting point: MQL at 50+ points, SQL at 80+. Calibrate based on your SAL acceptance rate; if sales accepts less than 70% of MQLs, raise the threshold. ### How often do you update your lead scorecard? Quarterly reviews work for most teams. However, trigger an immediate review after major changes: new product launches, ICP shifts, or significant drops in SAL acceptance rate. ### What is the 5 minute rule for leads? Contacting inbound leads within 5 minutes dramatically increases qualification rates compared to waiting even 30 minutes. Your scorecard can trigger immediate routing and alerts for high-intent leads to help you hit this window. ### How long does it take to see results from lead scoring? Expect 4-6 weeks to gather enough data for meaningful calibration. Initial improvements in routing accuracy and sales efficiency often appear within 2 weeks, but conversion impact takes a full sales cycle to measure. A lead scorecard only creates value when it connects to action. Document your criteria, align sales and marketing on thresholds, then wire it into routing and follow-up systems that execute without manual intervention. **Quick checklist:** - Scorecard documented with criteria, weights, and thresholds - Fit + Intent + Engagement signals defined - Disqualifiers identified - Score bands mapped to routing actions - Governance owner and review cadence assigned - Enrichment happens before routing - Speed-to-lead SLA enforced for top-tier leads If your current setup requires constant maintenance or leads still slip through the cracks, Surface can help you operationalize scorecard-to-demo workflows automatically. [Book a Demo](https://withsurface.com/book-a-demo) --- # Score Leads Automatically Based on Your ICP | Surface Labs URL: https://surface.thesurface.network/blog/lead-scoring _Surface scores every inbound lead against your Ideal Customer Profile automatically. Define your ICP in plain English and every lead gets classified as Qualified, Disqualified, or Needs Review before it reaches sales._ Leads come in and marketing sends them to sales. But no one knows which ones actually fit until a rep has already spent time researching, emailing, and getting on calls with leads that were never going to close. Traditional lead scoring doesn't solve this well. Legacy systems are rigid, take weeks to configure, and go stale the moment your ICP shifts or your form fields change. Most scoring models end up as a static point system that nobody trusts and everyone ignores. The result is that sales wastes hours on unqualified leads while qualified ones sit in the queue waiting for attention. Surface takes a different approach. Instead of building complex point based rules, you describe your ideal customer in plain English. Go to Ideal Customer Profile in Surface, create your ICP definitions, and write descriptions like "Series A+ companies" or "YC backed company with 10+ employees and $1M+ ARR." That's it. Every lead that comes through your forms gets scored automatically against those definitions and classified into one of three categories: Classification What it means Qualified Lead matches your ICP, route to sales Disqualified Lead does not fit, filter out of the pipeline Needs Review Partial match, someone should take a look When your ICP evolves or new enrichment data comes in, scores update dynamically. You don't need to rebuild scoring rules every time your target market shifts. Most lead scoring tools make you assign point values to individual attributes. Job title equals 10 points, company size over 500 equals 15 points, visited pricing page equals 5 points. You end up with a spreadsheet of rules that someone has to maintain and recalibrate constantly. Surface skips that entirely. You define what a good customer looks like in plain language and the scoring engine handles the rest. It uses enrichment data that Surface already captures (company size, industry, revenue, tech stack, seniority) to evaluate fit against your ICP definitions. No point systems. No manual recalibration. No scoring models that go stale after a quarter. Sales stops guessing which leads to prioritize. Marketing can measure how many qualified leads their campaigns actually produce. And your pipeline gets cleaner because unqualified leads are filtered before they ever reach a rep. The scoring runs on every lead automatically so there's no manual step between form submission and qualification. By the time a rep sees the lead, it already has a score and a classification attached. **What is intelligent lead scoring?** Intelligent lead scoring is the process of automatically evaluating inbound leads against your Ideal Customer Profile and classifying them as Qualified, Disqualified, or Needs Review. Unlike traditional point based scoring, it uses plain language ICP definitions instead of manual rule configuration. **How do I define my ICP in Surface?** Go to the Ideal Customer Profile section in Surface and describe your ideal customer in plain text. For example, "Series A+ companies" or "YC backed company with 10+ employees and $1M+ ARR." **What data does Surface use to score leads?** Surface uses enrichment data it already captures: company size, industry, estimated revenue, technology stack, job title, seniority level, and other data points appended during form fill. **Do scores update when my ICP changes?** Yes. When you update your ICP definitions or new enrichment data comes in, scores recalculate dynamically. No manual recalibration needed. **How is this different from HubSpot or Salesforce lead scoring?** Traditional CRM scoring requires you to build and maintain point based rules manually. Surface lets you define your ICP in plain English and scores leads automatically against those definitions. Scores update dynamically as your ICP evolves. --- # Lead Scoring Model: How to Build One That Actually Improves Conversions (With Examples + Best Practices) | Surface Labs URL: https://surface.thesurface.network/blog/lead-scoring-model Most lead scoring models fail for the same reason: they assign points but don't change behavior. The score sits in a CRM field, sales ignores it, and marketing wonders why MQL-to-opportunity rates stay flat. A lead scoring model that actually works connects fit signals and intent signals to immediate action—routing, SLAs, and follow-up workflows that respond in minutes, not days. This guide covers how to build one from scratch, the different model types to consider, and the operational details that separate scoring systems that drive pipeline from ones that just generate dashboards. A lead scoring model assigns numerical values to potential customers based on two types of data: fit (who they are) and intent (what they do). The fit side includes explicit information like job title, company size, and industry. The intent side covers behaviors like pricing page visits, email clicks, and content downloads. The point is to rank leads by how ready they are to buy. Higher scores mean higher priority. When a lead crosses a certain threshold, the model triggers an action—routing to a sales rep, enrolling in a sequence, or flagging for immediate follow-up. Without a scoring model, every form fill looks the same. With one, your team knows exactly where to focus. ### Lead scoring vs. lead grading Scoring and grading measure different things, though people often mix them up. Scoring reflects engagement—how active is this person? Grading reflects fit—does this person match your ideal customer profile? Here's why the distinction matters: a lead might score high because they visited your pricing page five times, but grade low because they work at a 10-person agency outside your target market. High engagement plus poor fit equals wasted sales time. Most teams that see real results use both together. The score tells you how interested someone is. The grade tells you whether they're worth pursuing. ### Lead scoring vs. MQL An MQL (Marketing Qualified Lead) is a stage in your funnel—a label that says "this lead is ready for sales." A lead score is one of the inputs that helps you decide when to apply that label. Where teams run into trouble: they set a score threshold (say, 50 points) and automatically call everyone above it an MQL. Six months later, sales complains that MQLs don't convert. The problem isn't the concept—it's that nobody checked whether leads scoring 50+ actually book meetings at a higher rate.[sales complains that MQLs don't convert](https://withsurface.com/blog/is-sales-tired-of-getting-shitty-leads). The problem isn't the concept—it's that nobody checked whether leads scoring 50+ actually book meetings at a higher rate. The score informs the stage. It doesn't replace the work of validating whether your thresholds reflect reality. When scoring works, the impact shows up in a few specific places: faster response times, higher meeting rates, and clearer alignment between marketing and sales on what "qualified" actually means. ### What improves when scoring works The wins tend to be operational: - **Speed-to-lead:** High-scoring leads get routed immediately instead of sitting in a queue - **Meeting set rate:** Sales focuses on leads with demonstrated intent, not random form fills - **Sales acceptance:** Fewer leads get rejected because qualification happens before handoff - **Pipeline per lead:** Resources concentrate on prospects more likely to close ### Why most models fail Static point systems cause the most problems. Teams assign points once, never revisit the weights, and then wonder why sales ignores the scores six months later. Other common failure modes include missing data (if half your leads lack company size, your fit scores are unreliable), no connection to routing (scores exist in a dashboard but don't trigger any action), and no feedback loop (marketing never learns which scored leads actually converted). A lead scoring model without operational follow-through is just a number in a CRM field. Modern buyers don't follow linear paths. Someone might visit your site anonymouslyModern buyers don't follow linear paths. Someone might [visit your site anonymously](https://withsurface.com/blog/the-ultimate-guide-to-tracking-website-visitors) for weeks, fill out a form, go dark, then return and request a demo. Your scoring model has to account for this behavior rather than assuming every lead moves neatly through stages. ### Fit signals vs. intent signals Fit signals describe who the lead is: job title, department, company size, industry, tech stack, geography. You typically get fit data from form fields or enrichment tools. Intent signals describe what the lead does: pages visited, emails opened, content downloaded, webinars attended, return visits. You get intent data from your marketing automation platform and website tracking.[intent data](https://withsurface.com/blog/leveraging-purchase-intent-data-to-identify-high-quality-leads) from your marketing automation platform and website tracking. Signal Type Examples Source Fit VP title, 200+ employees, SaaS industry Form fields, enrichment Intent Pricing page visit, demo request, 3+ sessions Website tracking, email engagement ### When scores update Batch scoring—updating once per day or week—creates lag that kills conversion. If someone requests a demo at 9am and your score doesn't update until midnight, you've lost the speed advantage. Real-time scoring updates on key events: form submission, high-intent page visit, enrichment completion, email engagement. The score reflects current behavior, not yesterday's snapshot. ### The action layer A score without an action is a vanity metric. Every score threshold maps to a specific workflow: - **Hot leads (80+):** Route to AE, trigger immediate notification, create task with SLA - **Warm leads (50-79):** Assign to SDR, enroll in high-touch sequence - **Cold leads (below 50):** Add to nurture campaign, monitor for score increases This is where most implementations fall short. The model exists, but nothing happens when a lead crosses a threshold. You have three main approaches. The right choice depends on your data maturity and team resources. ### Rule-based scoring You manually assign point values to specific attributes and behaviors. A VP title might be worth 15 points. A pricing page visit might be worth 10. - **Pros:** Transparent, easy to explain to sales, quick to implement - **Cons:** Requires ongoing maintenance, doesn't adapt to changing patterns, prone to bias Rule-based works well for teams just starting out or those with limited historical data. ### Predictive scoring Machine learning models analyze your historical conversion data to identify which signals actually predict revenue. The algorithm assigns weights based on patterns humans might miss. - **Pros:** Adapts over time, surfaces non-obvious correlations, reduces manual tuning - **Cons:** Requires clean data and sufficient volume, can feel like a black box, model drift is real Predictive scoring[Predictive scoring](https://withsurface.com/blog/how-surface-labs-helps-ad-agencies-use-ai-to-score-and-qualify-leads-from-ads) only works if your input data is consistent. Garbage in, garbage out applies here more than anywhere. ### Hybrid scoring Most mature B2B teams land here. Use rules for hard disqualifiers (wrong industry, too small, competitor) and let predictive models rank leads within qualified cohorts. This approach gives you transparency on the "why" while still benefiting from pattern recognition on the "who's most likely to convert." Here's a practical sequence that moves from strategy to execution. Skip steps and you'll end up with a model that looks good on paper but doesn't change behavior. ### 1\. Define your ICP and disqualifiers Before assigning any points, get clear on who you're trying to reach—and who you're not. Map out your ideal customer profile by segment, and list explicit disqualifiers (students, competitors, unsupported regions). This prevents score inflation. Without disqualifiers, a highly engaged lead from a non-target segment can score higher than a perfect-fit prospect with moderate engagement. ### 2\. Choose signals you can reliably capture List every fit and intent signal available to you, then filter for reliability. A signal you only capture 30% of the time will create inconsistent scores. Common reliable signals include: - Form fields you require (title, company) - Enrichment data (employee count, industry, tech stack) - High-intent pages[High-intent pages](https://withsurface.com/blog/how-intelligent-lead-segmentation-drives-personalized-marketing-campaigns) (pricing, demo request, case studies) - Email engagement (opens, clicks on bottom-funnel content) Avoid signals that sound good but rarely populate: budget fields, timeline questions, self-reported company size. ### 3\. Create score bands and thresholds Rather than obsessing over whether a pricing page visit is worth 8 or 12 points, focus on defining meaningful bands: - **Hot (80-100):** Ready for immediate sales conversation - **Warm (50-79):** Engaged but needs nurturing or qualification - **Cold (0-49):** Early stage or poor fit Each band maps to a specific action. This keeps the model operationally useful even if individual point values aren't perfect. ### 4\. Handle missing data Missing data is the silent killer of lead scoring. When a lead submits a form but skips optional fields, or your enrichment tool returns no match, what happens? Options include assigning a neutral score and flagging for manual review, using progressive profiling to collect missing data over time, or capturing partial submissions so you have something to work with. > **Tip:** Tools that capture partial form responses Tools that capture [partial form responses](https://withsurface.com/blog/how-to-build-a-modern-gtm-stack-in-2025)—even when leads abandon before submitting—give you more signals to score against. That email address captured at step 2 of a 4-step form is still valuable. ### 5\. Operationalize in your CRM Scores live where your team works. In HubSpot, this means score properties connected to workflows that update lead owners, create tasks, and trigger sequences. In Salesforce, you're looking at lead assignment rules and flows. Key implementation details: - Sync scores in real time, not daily batches - Display "top reasons for score" so sales understands the number - Set SLAs by score band (hot leads contacted within 5 minutes, for example) ### 6\. Validate against revenue outcomes The only way to know if your model works is to measure what happens after the score is assigned. Pull a cohort of leads from 90 days ago and compare meeting set rate, opportunity creation rate, and win rate by score band. If your "hot" leads don't convert meaningfully better than "warm" leads, your weights are wrong. Adjust and retest monthly. A few patterns separate models that drive revenue from models that get ignored. ### Keep it explainable Sales reps won't trust a score they don't understand. Add a field that shows the top 2-3 reasons for the score: "VP title (+15), pricing page visit (+10), 500+ employees (+10)." Transparency builds adoption. Black boxes build skepticism. ### Score in real time Leads contacted within 5 minutes of a high-intent action convert at dramatically higher rates than leads contacted an hour later. If your scoring runs on a nightly batch, you're leaving pipeline on the table. Real-time scoring requires real-time data capture and enrichment. Forms that enrich on submit—not hours later—make this possible. [Book a demo](https://withsurface.com/book-a-demo) to see how Surface handles real-time enrichment and routing. ### Use negative scoring and decay Not every action is positive. Unsubscribes, job title mismatches, and competitor domains warrant point deductions. Decay matters too. A pricing page visit from 6 months ago carries less weight than one from yesterday. Implement time-based decay so scores reflect current intent. ### Build a feedback loop Create a lightweight process for sales to flag scoring issues: "This lead scored 85 but was completely unqualified because X." Track exceptions and adjust weights quarterly. You don't need weekly calibration meetings. A shared doc or Slack channel where reps can flag misscored leads works fine. ### Demo request with instant routing A lead submits a demo request form. On submit, enrichment returns company size (450 employees) and industry (SaaS). The lead scores 90 based on high-intent action plus strong fit signals. The workflow immediately assigns the lead to the correct AE based on territory, creates a task with a 5-minute SLA, and sends a Slack notification. The AE sees the score, the top reasons, and the enriched company data—all before picking up the phone. ### Content lead with intent ramp A lead downloads an ebook and scores 35—moderate fit, low intent. Over the next two weeks, they return to the site three times, visit the pricing page, and open two nurture emails. Each action adds points. When they cross 70, the system moves them from nurture to SDR outreach. The SDR sees the activity timeline and leads with a relevant message about the pricing page visit. ### Multi-stakeholder account scoring Three people from the same company engage over a month: one attends a webinar, another downloads a case study, a third visits the pricing page. Individually, none scores above 50. Account-level scoring aggregates engagement across contacts. The account crosses the threshold for sales outreach, and the rep sees all three contacts with their respective activities—enabling a multi-threaded approach. Lead scoring doesn't exist in isolation. It's one component of a capture → enrich → score → route → follow-up system. Weakness at any point undermines the whole chain. ### Forms are the front door If your forms create friction—too many fields, no mobile optimization, no partial capture—you lose leads before you can score them. Multi-step forms with progressive disclosure tend to convert better while still collecting the data you need for scoring.[Multi-step forms](https://withsurface.com/blog/website-lead-conversion) with progressive disclosure tend to convert better while still collecting the data you need for scoring. Partial response capture is particularly valuable here. A lead who abandons at step 3 of 4 still gave you their email and company name. That's enough to enrich, score, and follow up. ### Speed-to-lead is a conversion lever Research consistently shows that response time correlates with conversion. Leads contacted within 5 minutes of a high-intent action are far more likely to convert than leads contacted an hour later. This means your scoring model triggers immediate action—not just updating a field for someone to notice later. Automated routing, task creation, and notifications close the gap between intent and response. A lead scoring model that improves conversions does three things: it reflects real buying signals, it triggers immediate action, and it gets validated against revenue outcomes. Most models fail because they stop at the first step—assigning points without connecting scores to routing, SLAs, and feedback loops. Start with clear ICP definitions and reliable signals. Build score bands that map to specific actions. Operationalize in real time so high-intent leads get immediate attention. Then measure what actually converts and adjust. The goal isn't a perfect algorithm. It's a system that helps your team focus on the right leads at the right time—and keeps improving as you learn what works. **Ready to turn more of your scored leads into booked demos?** [Book a demo](https://withsurface.com/book-a-demo) to see how Surface connects lead capture, enrichment, and routing into one system. --- # Lead Scoring That Actually Makes Sense | Surface Labs URL: https://surface.thesurface.network/blog/lead-scoring-that-actually-makes-sense **The middle school version:** Imagine you're a teacher grading homework, but instead of papers, you're grading how interested someone is in your product. Did they visit your pricing page? That's an A+. Did they only look at the blog once? That's a C. Did they come from a big company that matches your dream customer? Bonus points! Surface adds up all these "grades" automatically so our sales team knows exactly who to call first. We used HubSpot's lead scoring for over a year. We built a model — points for page visits, points for email opens, points for content downloads, minus points for inactivity. We set an MQL threshold at 50 points. Leads above 50 got passed to sales. After 6 months, we ran the analysis every team should run but rarely does: do our MQLs actually convert at a higher rate than non-MQLs? The answer was barely. MQLs converted to meetings at 16%. Non-MQLs that reps cherry-picked from the CRM converted at 13%. Our scoring model — months of configuration and tuning — was generating a 3-percentage-point lift. The reps could almost match it with gut instinct. The problem wasn't HubSpot. The problem was the inputs. Behavioral scoring — email opens, page visits, content downloads — measures attention, not intent. A marketing intern who reads every blog post scores higher than a VP who visits the pricing page once. The model rewards engagement, not buying behavior. We rebuilt our lead scoring in Surface around three layers that predict conversion — not just engagement. **Layer 1: Page activity — but only the pages that matter.** Not all page views are equal. We tracked which pages correlate with actual conversion and built scoring around those — not around total activity. Page Correlation with conversion Score weight Pricing page Highest. 4x more likely to book if they visited pricing. Heavy Case studies High. Indicates they're building a business case. Medium-heavy Product/features pages (3+ min time on page) High. Deep engagement, not scanning. Medium-heavy Comparison pages High. Actively evaluating alternatives. Medium Blog posts Low. Informational intent, not buying intent. Minimal Careers page Negative signal. They might be job hunting, not buying. Slight negative This was counterintuitive. Our old model gave points for every page view. The new model essentially ignores blog visits and heavily weights pricing + case studies. The data supports it — those two pages are the strongest predictors of a lead becoming a meeting. **Layer 2: Enriched company data.** Does this lead's company match our ICP? This is the "bonus points" layer — and it's often more predictive than any behavioral signal. We score on: company size (sweet spot: 50–500 employees), industry (B2B SaaS, tech, professional services), funding stage (Series A–C), tech stack (HubSpot or Salesforce users), and geography (US, UK, Canada, Australia). A lead from a 200-person B2B SaaS company that uses HubSpot starts with a high base score even before they visit a single page. That company fit signal is more predictive than 10 page visits. **Layer 3: First-party stated signals.** What the lead tells us directly — on the form. Timeline, budget, use case, and company size captured at the moment of form submission. These are the most reliable signals because they come straight from the lead's mouth, not from inferred behavior. A lead who selects "evaluating this quarter" and "budget approved" on the form gets a higher score than someone who's visited the pricing page 5 times but hasn't told us anything about their readiness. Every morning, our SDRs open their queue sorted by lead score. The top leads — high company fit, high-intent page activity, and qualifying form data — get immediate outreach. The middle leads get same-day follow-up. The low leads go to automated nurture. This replaced the old approach of "work the list top to bottom in order of arrival." Now reps spend their first hour on the leads most likely to convert, not the leads that happened to submit first. The impact: our SDRs book 40% more meetings per rep per month — not because they're working harder, but because they're working on the right leads first. **Lead that scored high (and converted):** VP of Marketing at a 300-person SaaS company. Visited pricing page twice. Read two case studies in one session. Submitted a demo request form with "evaluating this quarter, budget $25K–$50K." Lead score: 92. Booked a meeting the same day. Closed in 3 weeks. **Lead that looked good but wasn't:** Marketing coordinator at a 5,000-person enterprise. Downloaded 4 whitepapers, attended a webinar, opened every email for 6 weeks. Old model: MQL at 85 points. New model: score of 34. Why? No pricing page visit, no form submission, role is a researcher not a buyer, company is outside our sweet spot. SDR called — confirmed they were doing research for a report, no buying intent. The old model would have prioritized the second lead over the first. The new model gets it right. **Let your sales team focus on leads that matter. Try Surface's lead scoring.** --- # Track the Full Lead Journey Before They Convert | Surface Labs URL: https://surface.thesurface.network/blog/lead-user-journey _Surface captures every session, page view, and content interaction from a prospect's first visit to form submission so your sales team knows exactly what a lead cares about before the first call._ A prospect fills out your demo form. Your rep gets a name, email, and company. That's it. What they don't see is that this prospect visited your site three times over two weeks. They read two blog posts about integrations, viewed your pricing page twice, and came back through a LinkedIn ad before converting. Most teams never see this because their form tool only captures the submission, not the journey that led to it. The rep walks into the call blind. Surface starts tracking the moment a prospect lands on your site. Entry point, referral source, pages visited, time on each page, all captured automatically across every session. If someone visits on Monday, returns on Wednesday, and converts on Friday, Surface connects all three sessions to the same lead record. Your team sees the full timeline, not just the final session. ### What Gets Tracked Data point What it tells sales Entry point and referral source How they found you (organic, paid, LinkedIn, direct) Pages visited across sessions What parts of your product they evaluated Blog posts and case studies read What problems they're trying to solve Time spent on each page How seriously they're researching Pricing page visits Whether they're comparing costs Number of sessions before converting How long the evaluation cycle has been All of this syncs to your CRM alongside the form submission. Entry points, page views, content engagement, and navigation paths are attached to the lead record automatically. No separate analytics tool required. There's a real difference between a rep who opens with "So tell me what you're looking for" and one who opens with "I saw you've been looking at our integrations, are you evaluating us against your current stack?" Lead journey data turns generic outreach into informed conversations. Reps know what the prospect cares about, how far along they are, and what content resonated, all before the first call. **What is lead journey tracking?** Lead journey tracking captures a prospect's full behavioral history, every page visit, content interaction, and session, from first touch to form conversion. It gives sales teams context about what a lead cares about before the first conversation. **Does Surface track across multiple sessions?** Yes. If a prospect visits on Monday and converts on Friday, Surface connects both sessions to the same lead record. **What data gets attached to the lead record?** Entry points, referral sources, pages visited, time on page, blog posts read, case studies downloaded, pricing page visits, and navigation paths. All synced to your CRM automatically. **Do I need to install anything?** Surface tracks journey data natively as part of the form and site integration. No separate analytics tool or scripts required. **How does this help sales reps?** Reps see exactly what a prospect researched before converting. They know what topics matter and how long the evaluation has been going on so they can tailor the conversation instead of starting from scratch. --- # Making Vibe-Coded Apps Production Ready in 30 Minutes | Surface Labs URL: https://surface.thesurface.network/blog/making-vibe-coded-apps-production-ready-in-30-minutes **The middle school version:** "Vibe coding" is when you build an app super fast by just describing what you want to an AI (like ChatGPT or Cursor) and it writes the code for you. The problem? These apps look cool but break easily — like a sandcastle that falls apart when the tide comes in. Surface helps you take that sandcastle and turn it into a real brick house in just 30 minutes. We do this ourselves all the time, and this post shows you exactly how. If you've used Cursor, Replit Agent, or Claude to build an internal tool in an afternoon, you know the feeling. You describe what you want, the AI generates it, you iterate a few times, and suddenly you have a working prototype. A lead scoring calculator. A form that routes inquiries. A dashboard that pulls CRM data. A campaign brief generator. It works. On your laptop. With your test data. When you use it exactly the way you expected. Then you share it with the team and reality hits. Someone enters their email in the wrong format and the app crashes. Two people submit at the same time and data gets overwritten. The API key is hardcoded in the frontend. There's no error handling, no validation, no data persistence, and no way to update it without re-deploying from your local machine. The gap between "works on my laptop" and "works in production" is where most vibe-coded apps go to die. Not because the idea was bad — because the last 20% of making something reliable is boring work that AI prototyping tools skip entirely. At Surface Labs, we vibe-code internal tools constantly. Lead qualification prototypes, campaign calculators, data enrichment workflows, customer onboarding flows — anything we need to test fast, we build with AI and ship in hours. But we don't deploy the raw prototype. We use Surface to handle the production layer — the parts that make the difference between a demo and a real tool. Here's what Surface handles so the vibe-coded app doesn't have to: Production requirement What breaks without it How Surface handles it **Form validation** Bad data — wrong email formats, empty required fields, SQL injection attempts Surface's form layer validates every input before processing. No bad data enters the system. **Error handling** App crashes when something unexpected happens. User sees a blank screen or error dump. Surface catches errors gracefully. Users see helpful messages. Failed submissions are logged for debugging. **Data persistence** Data lives in memory or a local file. Close the browser, lose everything. Surface stores submissions in a structured database with full history. **Concurrent users** Two people submit at the same time and data conflicts or overwrites. Surface handles concurrent submissions natively. No race conditions. **Authentication** Anyone with the URL can access the app. No access control. Surface can gate forms and tools behind authentication or link-based access. **CRM integration** Data captured by the app doesn't connect to your pipeline. Manual copy-paste required. Surface pushes structured data to your CRM automatically. **Workflow triggers** The app captures data but nothing happens next. No routing, no notifications, no follow-up. Surface triggers routing, email responses, Slack notifications, and CRM actions on every submission. **Monitoring** No visibility into usage, errors, or performance. You don't know if it's working until someone complains. Surface provides submission tracking, error logging, and performance metrics. Last month, we needed a "Marketing ROI Calculator" — a lead magnet that lets prospects input their current metrics (ad spend, leads per month, conversion rate) and see how much pipeline they're leaving on the table. **Step 1: Vibe-code the logic (45 minutes).** We described the calculator to Claude: "Build a tool that takes monthly ad spend, leads per month, current conversion rate, and average deal size. Calculate current cost per meeting, projected cost per meeting with improved conversion, and total annual pipeline impact." Claude generated the calculation logic and a basic UI. **Step 2: Move the input layer to Surface (15 minutes).** Instead of using the vibe-coded form (no validation, no persistence, no CRM connection), we rebuilt the input as a Surface multi-step form. Step 1: company info + contact details. Step 2: current metrics (ad spend, leads, conversion rate, deal size). Step 3: results displayed inline with a "get your full report" CTA. **Step 3: Connect the outputs (10 minutes).** Surface captures the submission, enriches the lead (company size, industry), qualifies based on the inputs (companies spending $20K+/month on ads are high-priority), routes to the right rep, and triggers an instant response with the personalized calculation results. **Step 4: Deploy (5 minutes).** Embed the Surface form on a landing page. Done. Total time: about 75 minutes from idea to production. The vibe-coded calculation logic powers the math. Surface powers everything around it — data capture, qualification, routing, CRM sync, and follow-up. **Vibe-code when:** You need to test an idea fast. The tool is internal or low-stakes. The core logic is straightforward and the AI can handle it. You want to validate demand before investing engineering time. **Build from scratch when:** The tool handles sensitive data (PII, financial, health). The logic is complex enough that AI-generated code would be unreliable. The tool needs to scale to thousands of users. It's a core product feature, not an internal or marketing tool. **Use Surface as the bridge when:** The vibe-coded logic is sound but the production layer (validation, persistence, integration, routing) isn't. This is most internal tools, most lead magnets, most calculators, and most campaign-specific microsites. Before deploying any vibe-coded app, run through this: - Input validation — does the form reject bad data? - Error handling — does the app fail gracefully? - Data persistence — is every submission saved? - CRM sync — does captured data flow to your pipeline? - Workflow triggers — does something happen after submission? - Access control — can only intended users access it? - Monitoring — can you see usage and errors? If more than 2 of those are unchecked, the app isn't production-ready. Surface checks all of them by default. **Ship your vibe-coded apps with confidence. See how Surface makes prototypes production-ready.** --- # Marketing Agent Governance: A Practical Operating Model | Surface Labs URL: https://surface.thesurface.network/blog/marketing-agent-governance The first governance meeting for a marketing agent often begins after the prototype works. A channel lead has connected an ad account, a marketer has connected the CRM, and the assistant can produce a plausible weekly analysis. Then someone asks which credential it uses, what customer data the vendor retains, or who approved the definition of qualified pipeline. Those questions are not paperwork around the workflow. They describe the workflow. An agent combines a model, instructions, connected tools, business data, and authority. Marketing owns only part of that system, even when marketing is the only team using the output. Marketing agent governance is the set of roles, permissions, evaluations, approval rules, logs, and incident procedures that keep the system accountable. It should scale with the action. An assistant summarizing public research needs lighter controls than an agent that can change bids or lifecycle stages. List every tool the agent can discover, every object it can read, every action it can request, and the identity behind the request. Then map the person who owns each decision. The same chat interface can conceal several distinct authorities. Google's [Ads MCP server](https://developers.google.com/google-ads/api/docs/developer-toolkit/mcp-server) currently retrieves and analyzes data without changing campaigns. HubSpot's [remote MCP server](https://developers.hubspot.com/changelog/remote-hubspot-mcp-server-is-now-generally-available) supports writes to parts of the CRM while respecting existing permissions. A governance policy that treats both connections as "AI access" misses the operational difference. Use five permission tiers: 1. **Read:** Retrieve approved data without altering a record. 2. **Explain:** Combine sources, calculate, summarize, and label uncertainty. 3. **Draft:** Prepare a change, message, brief, or record update without submitting it. 4. **Approve:** Route the proposed action to an authorized reviewer and capture the decision. 5. **Execute:** Apply the approved change, verify the result, and record the event. Most teams should grant tiers independently. An agent may read campaign data, explain an anomaly, and draft a budget change while lacking approval or execution authority. The person approving the action should know the channel and the business consequence. No single owner can evaluate every part of an agentic marketing workflow. Assign roles according to the failures each group can detect. Role Owns Key review question Channel or functional lead Marketing logic and recommendation quality Would a competent specialist make this decision from this evidence? Marketing operations Workflow design, repeatability, and change control Does the process behave consistently and fail visibly? RevOps or data owner Business definitions, joins, CRM consequences Are identity, stages, timestamps, and revenue fields correct? Security or IT Credentials, scopes, vendor risk, retention, revocation Does the agent have the minimum access, and can we remove it quickly? Accountable business leader Risk tolerance and outcome Is the expected value worth the error cost and blast radius? The roles can live in a small company. The separation still matters. A founder may wear three hats and should consciously switch between them. Teams already formalizing [lead operations](https://withsurface.com/blog/why-lead-ops-is-becoming-its-own-category) have an advantage because they are accustomed to assigning ownership across marketing, systems, and sales. An approval policy should name the condition, reviewer, evidence required, expiration, and rollback path. "Human review required" is too vague. A useful rule might say that any weekly budget reallocation above $2,000 or 10% of campaign spend requires the acquisition lead to review source data, tracking health, and the proposed change within four hours. If approval expires, the agent does nothing. Use stricter gates for irreversible, public, regulated, or customer-facing actions. Publishing a product claim, changing consent fields, modifying lead status, and sending an email deserve different reviewers. A workflow that improves [inbound lead management](https://withsurface.com/blog/inbound-lead-management) can draft a routing correction while leaving the CRM write to RevOps until its exception rate is understood. Microsoft's preview [MCP server certification](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-certification) asks for verified publishers, authentication readiness, complete documentation, tested tools, and evidence when available. Buyers can borrow that structure even when a server is not in Microsoft's ecosystem. Ask the vendor for tool definitions, permission scopes, test results, data handling, support ownership, and change notices. \## Logs should reconstruct the decision Traditional application logs may show that a tool call succeeded. A marketing audit needs more context. Preserve the requesting user or service identity, model and workflow version, instruction version, data sources, query time, returned record identifiers, material calculations, recommendation, approval decision, executed action, and verification result. Do not store sensitive prompts or customer data indefinitely because logging can create its own exposure. Define retention by workflow and legal need. Redact or tokenize sensitive fields where the audit does not require the raw value. Make the log searchable by account, campaign, record, action, and approver. The [OWASP MCP Security Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/MCP_Security_Cheat_Sheet.html) recommends least privilege, explicit authorization, input validation, secure credential handling, and monitoring. Marketing leaders do not need to become security engineers. They do need to ensure that campaign urgency does not bypass ordinary access controls. Create a test set for each material workflow. Include normal cases, incomplete data, conflicting sources, an unauthorized request, a stale credential, and a prompt that tries to redirect the agent away from its task. Score retrieval, definition use, source coverage, unsupported claims, permission handling, and action selection. Run the test after model, prompt, server, schema, or business-rule changes. An agent is a versioned operating system, not a one-time automation. [Adobe](https://news.adobe.com/news/2026/06/adobe-accelerates-agentic-ai-adoption) and [Salesforce](https://www.salesforce.com/news/stories/agentic-marketing-teams-announcement/) describe broad systems spanning content, activation, data, and measurement. The broader the system becomes, the more useful a shared [integration layer](https://withsurface.com/integrations) and visible change control become. Name the person who can disable the workflow. Document how to revoke the credential, stop pending actions, identify affected records, restore prior state, notify stakeholders, and preserve evidence. Test the path once. A kill switch no one has used is an assumption. A [lead operations system that connects capture, qualification, and routing](https://withsurface.com/product) can give operators useful shared context. Governance protects that context from becoming ambient authority. The agent should know enough to help and possess only enough access to complete the approved job. The strongest governance program will feel ordinary. Permissions match roles. Recommendations show evidence. Approval is a real decision. Logs can reconstruct what happened. When the agent becomes more capable, the team expands authority deliberately rather than discovering its reach during an incident. #### Practical steps - Create an authority map for every connected tool, object, action, credential, and owner. - Assign the five permission tiers independently and review them quarterly. - Write approval rules with numeric or event-based triggers, evidence requirements, and expiration behavior. - Log enough context to reconstruct the recommendation and action without retaining unnecessary sensitive data. - Run evaluation cases after any model, server, schema, prompt, or business-rule change. - Test credential revocation and rollback before enabling the first production write. --- # Marketing Campaign Strategy: How to Turn a Campaign Idea Into an Operating System | Surface Labs URL: https://surface.thesurface.network/blog/marketing-campaign-strategy-how-to-turn-a-campaign-idea-into-an Campaigns often fail before launch because the team mistakes a campaign idea for a campaign strategy. A theme, a design direction, and a launch date create the feeling of progress, but they don't answer who needs to care, why the message is credible, or what happens after someone responds. A marketing campaign strategy connects those questions. It gives creative work a job inside a broader system of audience, message, content, conversion, and measurement — the work can still be inventive, it just can't rely on invention alone to carry the outcome. Start with the behavior or understanding you want to change. "Drive awareness" is too broad to guide much. A campaign might need a specific buyer segment to recognize a problem, replace an old assumption, or take a defined next step. Write the change in a sentence: "Operations leaders who believe lead routing is a CRM configuration problem should understand it as a revenue-critical workflow that requires qualification, response, and measurement." That sentence gives the team something to test, and it shapes the message, content, media plan, and follow-up all at once. The message should be narrow enough to remember and strong enough to survive the whole journey — a prospect who sees an ad, searches the phrase, finds an article, and fills out a form should hear the same story at every step, or the campaign becomes background noise. Our [article on why lead ops is becoming its own category](https://withsurface.com/blog/why-lead-ops-is-becoming-its-own-category) shows what this looks like in practice: the message works because it names a real operational tension rather than reaching for a clever slogan. Teams can now create campaign assets very quickly — a dozen ad variations, landing-page copy, and social posts before lunch. Production speed is useful, and it also makes it easier to distribute a vague idea everywhere at once. Before creating variants, collect the proof that should anchor the campaign: customer outcomes, a distinctive workflow, original research, or a market pattern the team has observed repeatedly. A precise example beats a generic statement of confidence every time — a campaign about lead operations can show the actual gap between a form submission and a relevant sales response, and the audience leaves with a clearer picture than any brand claim could offer. [Google's people-first content guidance](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) is useful even for campaigns here, since it pushes teams toward original information people can verify or use. Media creates entry points. Content gives people somewhere to go once they enter, so map the campaign into a small set of assets with different jobs: a core landing page for the promise and next step, a detailed guide for search and buyer research, a proof page to make the claim concrete, and shorter social or email material to point people toward the right one. The path should fit different levels of familiarity — someone seeing the idea for the first time may need the guide, someone who already feels the pain may go straight to the landing page. That's why a campaign needs more than one asset, but not an indiscriminate asset explosion. Our [content marketing guide](https://withsurface.com/blog/content-marketing-guide-2026) treats internal links and conversion paths as part of the work itself, and the same discipline applies to a campaign: clear, specific links between the core idea, the supporting content, and the page where someone can act. ## Treat the landing page and form as campaign infrastructure A campaign landing page should carry the specific argument a prospect encountered in the ad or email, not discard the message and hand them a generic homepage to decode — explaining the problem, who the page is for, and what evidence supports the claim, then offering a next action that fits the level of intent. The form deserves equal attention: ask only for what makes the response more relevant, and build routing around what you collect, so a high-intent request doesn't wait in the same queue as a low-stakes content download. Our [lead capture and routing guide](https://withsurface.com/blog/lead-capture-and-routing-for-b2b-saas-companies) covers the variables that shape an effective handoff, and the campaign promise should survive that handoff intact: if someone responds to a campaign about a specific use case, the first sales conversation should recognize it. Sales doesn't need to approve every line of creative, but they should understand the promise, the audience, and the assets they can use once someone responds — plus a clear place to send feedback. Run a short pre-launch review with customer-facing teams: what sounds unfamiliar, which objections will surface, what evidence will make the message believable. Turn that input into a brief and a simple follow-up plan. The goal isn't consensus theater — it's preventing the campaign from creating a demand pattern sales can't recognize or handle. We built our content review workflow to support exactly this, keeping comments and revision history connected to the campaign assets so feedback improves not just one landing page but future production too. Choose the measurement before launch. A category-awareness campaign may prioritize qualified reach and branded search; a demand-capture campaign may prioritize conversion, meeting rate, and response speed. Keep the evidence levels clear — you can observe impressions, clicks, and meetings, and you can infer that a campaign contributed to a later opportunity, but those are different claims. Our [work on attribution versus incrementality](https://withsurface.com/blog/attribution-is-not-incrementality-how-to-measure-ai-creative) is a useful corrective when campaign reporting starts telling a cleaner story than reality — a good report shows performance and uncertainty at the same time. A campaign idea becomes a campaign strategy when every part of the experience agrees on the change it's trying to create. Build the message from proof, give it a content path, and let the landing page, lead response, and sales conversation carry it forward together. --- # Marketing feedback loops that change what gets published | Surface Labs URL: https://surface.thesurface.network/blog/marketing-feedback-loops-change-what-gets-published The monthly report ends with a familiar list: organic traffic softened, one paid message drew better leads, sales heard a new objection, and a comparison page appeared in more AI answers. Everyone agrees the findings are interesting. The next content calendar remains exactly as it was. Most marketing teams have feedback. Fewer have a loop. The difference appears after interpretation, when evidence either becomes an owned change with a review date or settles into a slide that everyone vaguely remembers. Marketing feedback loops are repeatable systems that observe a result, interpret what likely produced it, select a response, execute the change, and measure what happened next. They connect channel signals and revenue outcomes to future targeting, messaging, content, conversion, routing, and investment decisions. A loop needs memory. The team should be able to see the evidence, decision, owner, approved change, published version, and later result without reconstructing the story from dashboards and meeting notes. It also needs restraint because marketing data contains seasonality, attribution limits, small samples, tracking changes, and accidental correlations. Surface is built around this operating model. Its [intelligent attribution system](https://www.withsurface.com/intelligent-attribution) can connect accepted, won, and lost outcomes to future rules, routes, briefs, and campaigns. Human approvals and edits remain part of the record, which means the system learns from the team's judgment as well as the result. Choose the decision the loop should improve. "Monitor content performance" is a reporting task. "Decide which content cluster receives the next two weeks of editorial capacity" is a decision. The second statement tells the team which evidence matters and what action must follow. Different decisions require different loops. Search and AI visibility can inform which buyer questions deserve better coverage. Campaign response can show whether a message attracts the intended segment. Form and lead data can reveal where interest turns into friction or poor qualification. Sales outcomes can challenge the public promise or expose missing proof. Define the decision, evidence window, minimum threshold, owner, and available responses before the result arrives. Otherwise a team will move the goalposts around whatever happened. A rising metric becomes proof of the strategy, while a falling metric becomes a reason to ask for more time. Local optimization is seductive because each platform reports the behavior it can see. A content tool knows what was published. An ad platform knows what received a click. A form knows what someone submitted. The CRM knows whether sales accepted the lead. Each system can recommend a better local outcome while the buyer journey gets worse. Use several linked loops rather than one giant score: Loop Evidence Decision it should change Search and AI discovery Queries, rankings, appearing pages, citations, mentions, recommendations, and competitor sources Which questions, pages, and evidence gaps deserve work Content engagement Entry path, depth, related-page movement, return behavior, and conversion actions Which pages need a better answer, link path, format, or CTA Campaign response Audience, message, creative, channel, cost, and qualified response Which combinations deserve more distribution or a new asset Lead operations Form starts, completion, enrichment, fit, routing, response, and meetings Where the conversion and handoff system needs repair Sales and revenue Acceptance, objections, asset use, opportunity movement, wins, losses, and cycle time Which claims, proof, segments, and offers should shape the next campaign [Traffic Intelligence](https://www.withsurface.com/platform/infrastructure/traffic-intelligence) helps teams examine content, campaigns, form behavior, buyer quality, AI referrals, and pipeline in one journey. [AI Visibility Engineering](https://www.withsurface.com/platform/ai-visibility) adds prompt families, citations, competitors, source influence, and content gaps. Neither view removes uncertainty, but connecting them makes it harder to celebrate visibility while qualified demand deteriorates. Evidence should enter a decision queue with a small set of possible actions: investigate, revise, create, distribute, test, consolidate, pause, or do nothing. Each candidate needs a claim, evidence links, confidence level, affected audience, expected business effect, owner, reviewer, and remeasurement date. This is where many loops break. The analytics team identifies a pattern, the content team receives a vague recommendation, and a writer is asked to "make the page more conversion focused." The finding loses its source and caveat on the way into production. By publication, nobody can explain what changed or why. [Surface Content Campaign Agents](https://www.withsurface.com/platform/content-campaigns) preserve the evidence board beside the campaign plan. A finding drawn from calls, CRM opportunities, ICP accounts, support tickets, or search can become a shared brief for an article, landing page, nurture sequence, proof asset, or social work. The team reviews the set before anything ships. An example makes the distinction clearer. Suppose a guide attracts steady search traffic, appears in relevant AI answers, and produces many form starts, yet very few accepted leads. The response should not automatically be more traffic or a stronger CTA. The team may need to inspect the queries, promise, form questions, qualification rules, and sales rejection reasons. One of those layers is attracting or discarding the wrong person, and the page rewrite is only one possible fix. Feedback systems can accelerate a wrong conclusion. A campaign spike may reflect one large account. A page may appear to assist pipeline because it is linked in every sales follow-up. A sales objection may feel common because one persuasive representative repeats it. Label the evidence before authorizing action. Use plain confidence states such as observed, attributed, inferred, and unverified. Observed means the event was recorded directly. Attributed means a declared model assigned credit. Inferred means several observations support a reasonable interpretation. Unverified means the pattern deserves investigation but should not drive automated work. [Google Analytics defines attribution models](https://support.google.com/analytics/answer/10596866?hl=en) as rules that assign credit across touchpoints. That definition is a useful reminder that attributed credit is a reporting choice. Our article on [attribution versus incrementality](https://www.withsurface.com/blog/attribution-is-not-incrementality-how-to-measure-ai-creative) shows why creative and content systems need lead quality, sales response, and business outcomes in the loop without pretending every downstream result has one cause. Automation should scale repeated, reversible actions first. It can assemble evidence, identify anomalies, draft a brief, recommend internal links, prepare a version, or notify an owner. Claims, positioning, deletions, major budget moves, and publishing permissions deserve named human review. Weekly reviews suit operational problems such as broken forms, routing delays, abrupt traffic changes, indexing failures, and a campaign attracting obvious spam. Monthly reviews suit portfolio choices: refresh priorities, segment quality, message performance, source gaps, and asset reuse. Quarterly reviews can reconsider category coverage, market focus, channel investment, and the definitions shared by sales and marketing. Do not wait a quarter to fix a broken conversion path, and do not rewrite the positioning after two disappointing days. The cadence should match the amount of evidence needed and the cost of being wrong. The [Surface content publishing workflow](https://www.withsurface.com/solutions/launch-campaigns-faster) connects the opportunity, brief, assets, approval, publication, and measured outcome. That continuity turns feedback into institutional memory. The next campaign can begin with what the company learned rather than another empty template. Marketing feedback loops earn their name when they change work. If your reports produce observations faster than your team can turn them into responsible action, [book a Surface demo](https://www.withsurface.com/book-a-demo) and bring one decision you want the system to improve. --- # What Is a Marketing MCP Server? A Plain-English Guide for Operators | Surface Labs URL: https://surface.thesurface.network/blog/marketing-mcp-server-guide-july-2026 A marketing MCP server is a connection layer that lets an AI application discover and use approved marketing data or tools. It might give an assistant permission to query Google Ads, retrieve audience research, inspect CRM contacts, or run an SEO report. The server defines what the assistant can reach and what actions it can request. It does not supply marketing judgment, guarantee a correct answer, or replace the underlying platform. That definition matters because the acronym is spreading faster than operational understanding. In June, [Google Ads](https://developers.google.com/google-ads/api/docs/developer-toolkit/mcp-server), [Microsoft Advertising](https://about.ads.microsoft.com/en/blog/post/june-2026/building-a-new-ai-economy-that-creates-value-for-everyone), [Pinterest](https://business.pinterest.com/blog/pinterest-ai-for-marketers/), [SparkToro](https://sparktoro.com/blog/sparktoros-mcp-server-is-now-live-connect-audience-research-directly-to-your-favorite-ai-tool/), [Semrush](https://www.semrush.com/news/460693-semrush-launches-mcp-connector-in-perplexity-integrating-search-intelligence-within-the-ai-search-engine/), and [Adobe](https://news.adobe.com/news/2026/06/adobe-accelerates-agentic-ai-adoption) all announced or expanded agent connections. [HubSpot](https://developers.hubspot.com/changelog/remote-hubspot-mcp-server-is-now-generally-available) had already made its remote MCP server generally available in April. A buyer could reasonably look at the launch list and assume that MCP is a new category of marketing software. It is closer to a common socket. Before MCP, a team connecting an assistant to several systems often built separate integrations for each pairing. One path connected an AI tool to the CRM. Another connected it to the ad platform. Each path required its own authentication, request format, tool descriptions, and maintenance. Anthropic introduced the [Model Context Protocol](https://www.anthropic.com/news/model-context-protocol) as an open standard intended to reduce that repeated integration work. The official [MCP documentation](https://modelcontextprotocol.io/docs/getting-started/intro) describes a way for AI applications to connect with external data, tools, and workflows. A server exposes a set of capabilities. A compatible host can discover those capabilities and ask the server to use one. The host then gives the returned information to the model so it can construct an answer. For a marketer, the visible experience may be simple: "Compare branded search spend with qualified pipeline for the last eight weeks." Behind that sentence, the system still has to authenticate, select fields, match dates, reconcile campaign identifiers, apply a definition of qualified pipeline, and return enough evidence for review. MCP can standardize part of the plumbing. It cannot resolve an undocumented funnel. This is why teams reviewing [inbound marketing tools](https://withsurface.com/blog/inbound-marketing-tools) should evaluate the connection separately from the assistant. A charming interface can sit on top of thin data access. A plain interface can expose reliable records with clear permissions. The second system may create more value. \## Three marketing use cases that are real today The first credible use case is retrieval and analysis. Google's [Ads MCP server](https://developers.google.com/google-ads/api/docs/developer-toolkit/mcp-server) lets an agent discover accounts, retrieve metadata, and query performance. The current release is read-only. A paid media lead could ask for campaigns with week-over-week conversion changes, then inspect the rows before making a change in Google Ads. The second is research inside a planning workflow. SparkToro's server can run, retrieve, and compare audience-research reports. Semrush's connector gives Perplexity users access to search and competitive data. Instead of exporting files and teaching a general model what each column means, the operator can request current evidence through an approved connection. Teams evaluating [generative engine optimization services](https://withsurface.com/blog/generative-engine-optimization-services) should look for this kind of source access because useful recommendations require more than a prompt and a visibility score. The third is record or workflow action. HubSpot's remote server supports expanded reading and writing across parts of the CRM while respecting existing HubSpot permissions. This is where the risk profile changes. Retrieving a contact and changing a lifecycle stage are different acts, even if the same chat window triggers both. The most important buyer question is not "Does it support MCP?" Ask what the server exposes, under whose identity, with which scopes, and with what record of use. Google's server supports OAuth 2.0 or a service account. HubSpot uses OAuth 2.1 with PKCE. Pinterest started with approved alpha partners. These details determine whose authority the assistant borrows. Microsoft's preview [MCP certification process](https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-certification) asks publishers to document authentication, setup, tool behavior, support, privacy, and testing. Certification will not eliminate operational risk, though the checklist points buyers toward the right evidence. A server should describe every tool, validate inputs, fail visibly, and produce logs someone can investigate. The internal architecture deserves the same attention. A useful [integration layer](https://withsurface.com/integrations) preserves stable identifiers, timestamps, account boundaries, and source lineage. If the assistant receives only a flattened summary, it may sound certain while losing the record needed to verify the answer. Start with the job. Write one sentence that names the decision, the systems required, the expected output, and the human who will review it. "Every Monday, identify paid campaigns with a material change in qualified pipeline efficiency and give the acquisition lead the source rows" is evaluable. "Use AI to optimize marketing" is an invitation to buy a demo. Then inspect five areas: 1. **Capabilities:** List the exact data objects and actions the server exposes. Separate reads, drafts, approvals, and direct writes. 2. **Identity and scope:** Confirm whether access uses an individual account, service account, or shared credential. Apply the narrowest available scopes. 3. **Evidence:** Require record IDs, source links, query windows, definitions, and an explicit note when data is missing. 4. **Control:** Document approval gates, rate limits, allowed accounts, rollback paths, and the person who can disable access. 5. **Evaluation:** Test known historical cases. Track incorrect joins, unsupported conclusions, failed tool calls, specialist rejection, and time to a reviewed answer. Teams already trying to [report AI visibility without fake precision](https://withsurface.com/blog/ai-visibility-reporting-without-fake-precision) will recognize the principle. A new interface does not remove sampling, data gaps, engine variance, or business context. The server should make uncertainty easier to see. MCP can lower integration friction. That is useful. It can also make access look casual because a complex data request now resembles a sentence. Treat every marketing MCP server as an authenticated software integration with a model in the loop. Begin with read access and a narrow question. Make the output cite its records. Give a channel specialist the right to reject the recommendation. If the workflow earns trust, allow the agent to create drafts or queue approvals before granting direct write access. A connected [marketing operating system](https://withsurface.com/product) becomes valuable when it preserves context and makes decisions easier to inspect. The protocol is only the doorway. #### Practical steps - Inventory every proposed server, owner, host, credential type, scope, and connected account. - Run a ten-case historical evaluation before using live data in a recurring workflow. - Keep the first production use case read-only and require links or record IDs for material claims. - Review permissions quarterly and after any role, agency, or vendor change. - Add a kill switch, incident owner, and documented revocation path before enabling writes. --- # Marketing Operations Strategy: Fix the Content System Before Hiring More Writers | Surface Labs URL: https://surface.thesurface.network/blog/marketing-operations-strategy-content-system A founder looks at a flat publishing calendar and asks for two more writers. The marketer nods because the request sounds logical, then opens the actual system: briefs live in three folders, product reviewers respond late, the CMS breaks formatting, the form drops half the intent data, and nobody can explain which leads came from which page without exporting a spreadsheet after dinner. That team does not have a writer problem yet. They have a marketing operations strategy problem. More writers can help only after leaders fix the workflow that turns an idea into a page, a page into a reader path, and a reader path into a qualified lead that someone can actually follow up with. Many teams treat operations as the administrative work that happens after strategy. Someone makes the assignment, someone writes the draft, someone publishes the page, and someone else eventually checks whether anything happened. That order hides the real problem because content output depends on the system around the writer long before a draft appears. A working marketing operations strategy defines how teams choose topics, approve claims, collect subject-matter expertise, publish pages, update internal links, capture leads, enrich records, route interest, and recover abandoned intent. Writers sit inside that system. When leaders ignore the system, writers spend their time compensating for broken workflows rather than producing better work. We believe that [lead capture, qualification, routing, recovery, and nurture](https://withsurface.com/product) should be treated as part of the content system, not as a separate problem that begins after the form fill. A page can only do so much alone. Marketing teams still need a post-click operating layer that knows what the reader did, what they asked for, how qualified they are, and who should follow up. Every small marketing team has a person who knows how to force the machine to work. They know the CMS trick that prevents heading styles from breaking. They know which product manager will answer Slack at 9:40 p.m. They know how to rebuild the UTM after the landing page URL changes. They know which spreadsheet has the real status because the project management tool became ceremonial months ago. Leaders often mistake that person for evidence that the system works. In reality, that person may be the only reason the system has not collapsed. A serious marketing operations strategy should remove hero work from the publishing process. People should spend their judgment on ideas, evidence, messaging, and prioritization, rather than spending their energy patching handoffs that should have been designed properly. Thinking about [inbound lead management](https://withsurface.com/blog/inbound-lead-management) gives teams a cleaner frame for this problem. Marketing operations does not end when a page goes live. It continues through enrichment, scoring, routing, follow-up, CRM sync, reporting, and recovery. If one person has to manually hold those pieces together, the company has built a habit, not a system. ## Marketing Operations Strategy Should Connect Content to Lead Handling Content teams often optimize the page and ignore the moment after the page. A visitor reads the article, clicks the CTA, fills out the form, disappears into a CRM field, waits for routing, receives a generic email, and then becomes a debate between marketing and sales. The content technically worked, but the revenue system leaked the opportunity. B2B teams need to capture more intent, qualify the right leads, route buyers faster, recover drop-offs, and nurture people who are not ready for sales yet. A content program becomes more valuable when operators connect the page to a lead operations layer that can handle demand while attention is still warm. This is why [the form is often the most underinvested part of the funnel](https://withsurface.com/blog/the-form-is-the-most-underinvested-part-of-the-funnel). Teams spend weeks getting the right traffic to the page, then ask a generic form and a brittle routing rule to carry the most important part of the journey. Better content operations should make the handoff from reader to lead feel designed, not improvised. ## The CMS Is Part of the Content Team Whether Anyone Admits It A CMS can turn a good strategy into a slow failure. Marketers may plan a thoughtful cluster, write useful pages, and build strong internal links, then lose the benefit because the CMS makes publishing painful, hides metadata controls, breaks schema, limits template flexibility, or requires a developer for every minor landing page change. Google’s current search guidance still asks creators to help people, but people cannot benefit from a page that teams cannot publish, update, structure, or connect. Content leaders should audit the CMS before they expand the writing bench. They should know who can edit navigation, who can create landing pages, who owns form placement, who updates CTAs, who controls schema, and who can fix technical issues when publishing work creates indexation or rendering problems. The CMS audit should also include conversion paths. Marketers should know whether they can publish a blog, connect it to a relevant product page, add a CTA, route a demo request, and measure what happened without asking three other teams to rebuild the page. A fragile CMS does not only slow content production. It slows learning. More writers create more drafts. They do not automatically create more published work, better pages, stronger positioning, cleaner attribution, or faster lead follow-up. When teams hire writers into a weak operating system, editors spend more time clarifying briefs, reviewers spend more time reacting to misaligned drafts, and operators spend more time pushing unfinished work through the queue. Leaders should treat hiring as a multiplier. If the system is good, a writer helps the team produce more useful coverage. If the system is bad, a writer produces more unmanaged work for the same bottleneck. A founder who wants more content should first ask whether the team can brief, review, publish, distribute, measure, and route the next ten pieces without creating new chaos. Tool sprawl creates the same amplification problem. When one lead journey depends on a form tool, enrichment tool, scheduler, routing tool, CRM workflow, spreadsheet, Slack alert, and email automation platform, every additional page creates more places for the handoff to break. Teams should not need [five tools to handle one lead](https://withsurface.com/blog/you-shouldn-t-need-5-tools-to-handle-one-lead) unless the system truly requires that complexity. Start with the content intake process. Every new topic should have a business reason, a primary reader, a funnel role, a target page type, an owner, a reviewer, an internal-link destination, a CTA, and a source requirement before a writer starts drafting. That sounds slower than sending a title into a prompt, but it prevents the expensive delay that arrives when everyone realizes the draft answered the wrong question. Then fix the publishing path. Teams should define which templates support blogs, guides, comparison pages, case studies, and conversion pages. Operators should know how to add calls to action without waiting for design support, how to connect articles to landing pages, and how to update pages when product messaging changes. A content system should make good behavior easier than improvisation. Finally, connect the content path to the lead path. A reader who clicks from an article into a form should enter a system that can capture clean data, identify fit, route the lead, trigger the right follow-up, and preserve context for sales. When teams know how much of that journey works, they can decide whether the next investment should be a writer, an editor, a product marketer, a demand gen operator, or better lead operations infrastructure. ## What to Fix in the Content System Leaders should begin with five practical audits. First, they should review the last twenty published pages and identify where each one sends a qualified reader next. Second, they should review the CMS and list every publishing step that requires a non-marketing owner. Third, they should compare keyword intent against page type, because a direct buying query probably should not land on a vague thought leadership post. Fourth, they should review the form and routing experience attached to the content. Fifth, they should ask sales which pages actually help conversations. Teams can use those findings to create a visible operating model. A good model will show how topics enter the system, how experts contribute, how editors protect quality, how operators publish and distribute, how lead operations capture and qualify interest, and how leaders decide what to refresh after real market feedback arrives. The audit should also ask whether the team is already getting enough demand and simply failing to convert it. Many teams do not need more raw leads first. They need to understand why [existing leads are not converting](https://withsurface.com/blog/you-re-getting-enough-leads-you-re-just-not-converting-them), where buyers fall out of the funnel, and which handoffs lose context before sales can act. A content system should never care only about traffic. Strong content operations should help teams understand whether readers become qualified demand, whether qualified demand reaches the right rep, and whether the business learns anything from the interaction. That requires more than a publishing calendar. Customer proof matters here because operational improvements can sound abstract until a team sees the actual funnel impact. [Nextiva improved conversions by 37%](https://withsurface.com/customers/nextiva) after rebuilding the inbound experience around better forms, workflows, lead scoring, and routing. [Galley cut spam leads by 100%](https://withsurface.com/customers/galley) while increasing qualified leads, which shows why lead quality belongs inside the marketing operations conversation. That position matters for content strategy. When a marketing team publishes articles without lead operations, leaders can end up celebrating traffic that never becomes usable pipeline. When a team connects content to capture, qualification, routing, recovery, and nurture, leaders can judge whether a content program created demand that the business could actually handle. ## A Simple Marketing Operations Strategy for Content Teams Build one weekly content operating meeting, not six scattered status rituals. In that meeting, the team should review upcoming topics, stuck reviews, pages awaiting publication, conversion-page needs, lead quality from recently published pages, and refresh candidates. Leaders should use the same meeting to decide whether the team needs more writers, more subject-matter access, better templates, better routing, or fewer priorities. A small team can use a simple rule. Before hiring another writer, the team should be able to publish one strong article every week for six straight weeks, link it to a relevant destination, capture leads from the page, route qualified buyers quickly, and report what the page did beyond impressions. If the team cannot do that, leaders should fix the system before adding more people to it. Pricing and packaging should enter the conversation only after the team knows which parts of the system need help. Some teams only need cleaner capture. Others need qualification and routing. More mature teams may need recovery, nurture, attribution, and lifecycle reporting. Teams can use [current pricing and package structure](https://withsurface.com/pricing) as a practical way to map operational need against the level of funnel support required. Content teams do not need more chaos with a larger payroll. They need a marketing operations strategy that lets good ideas become useful pages, lets useful pages become buyer paths, and lets buyer paths become qualified conversations before the moment passes. Hire writers when the system can absorb them. Until then, fix the machine that turns writing into revenue. Teams trying to turn publishing attention into qualified inbound demand can [book a demo](https://withsurface.com/book-a-demo) to see how better capture, qualification, routing, recovery, and nurture work after the click. --- # May Marketing Updates: This Week's Marketing | Surface Labs URL: https://surface.thesurface.network/blog/may-marketing-updates There is a very specific kind of content advice that has started to drive me insane. It usually comes from someone who has not read a book in years, has no serious relationship to longform attention, has very little curiosity about how people actually understand complicated ideas, and yet feels perfectly comfortable advising professionals on how to write content intended to be read. They will tell you no one reads anymore. They will tell you every paragraph needs to be one sentence. They will tell you every idea needs to be flattened, simplified, repackaged, reprompted, and reassembled until it looks like a LinkedIn thread that got trapped inside a SaaS landing page. And sure, fine, people scan. People skim. People bounce. People open seventeen tabs and forget why they opened twelve of them. I am not arguing that every B2B buyer is sitting by candlelight with a cup of tea, murmuring lovingly over your comparison page about enterprise workflow orchestration. But the fact that people are busy does not mean they cannot read. It means they are selective about what deserves attention. If you do not read, I am not sure why you should be treated as an authority on how people read. If you do not spend time inside books, essays, transcripts, product documentation, research papers, technical pages, or even genuinely useful blog posts, then your advice about “readability” is probably just advice about formatting. Formatting matters, but comprehension is not the same thing as whitespace. This week’s marketing theme is reading comprehension. Not in the elementary-school sense. In the operational sense. Can a buyer understand what you mean? Can a founder verify your claim? Can a sales team point to the page without apologizing for it? Can an AI system retrieve your content, summarize it, cite it, and still preserve the argument? Can a skeptical reader move from question to comparison to decision without feeling like they walked into a room full of inflatable furniture? That is the work. The weirdest shift in marketing right now is that the first reader of your content may no longer be a person. A search interface may read it first. An answer engine may read it first. A retrieval system may read it first. A browser agent, chatbot, AI Overview, product-discovery layer, or citation system may read it first, compress it, classify it, and hand a version of it to a buyer before that buyer ever reaches your site. This does not make writing for humans less important. It makes the human part more exposed. If an AI system summarizes your page badly, some of that may be the system’s fault. If your page gives it a vague claim, no source trail, weak structure, no dated evidence, no product specificity, and six paragraphs of “in today’s fast-paced digital landscape,” some of that is on you. Google’s own guidance on [creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) is still a useful corrective here because it asks creators to evaluate whether their work benefits people first. The retrieval-era version of that question is slightly sharper: did your team create something a human can understand and a machine can cite without mangling the idea? The page has to be legible to machines and useful to people. That sounds obvious until you read most B2B content. A lot of teams still treat content as if the job is to publish enough pages to create the ambient smell of expertise. The older content-farm version of this was thousands of thin pages targeting every keyword variant. The newer AI version is prettier, faster, and somehow even more depressing. Teams generate posts, briefs, comparison pages, newsletters, infographics, and “thought leadership” assets in bulk, then act surprised when none of it feels like it came from a living company with a real point of view. The retrieval era punishes that more quietly. Sometimes your traffic drops. Sometimes your traffic stays fine, but buyers stop trusting the page. Sometimes an AI answer cites your competitor because they gave the system a cleaner, fresher, more complete source trail. Sometimes the page technically ranks, but the reader gets there and feels the unmistakable sensation of having arrived at a professionally decorated empty room. Visibility is no longer the hard part in quite the same way. A team with decent tools, decent keyword data, a competent CMS, and a steady publishing process can generate impressions. They can create topical coverage. They can enter the conversation. They can even earn some citations if they cover the right fan-out queries and keep pages fresh. The harder question is whether any of that visibility helps a buyer understand what the company does, why it matters, how it compares, and when it should be trusted. Surface Labs has written elsewhere about [how B2B marketing has changed in the last few years](https://withsurface.com/blog/how-b2b-marketing-has-changed-in-the-last-3-years), and that shift matters here because the old operating model was more comfortable than the current one. Teams could generate leads with content, score behavior, nurture through email, and pass MQLs to sales. Today, buyers move through messier paths, AI systems touch more of the journey, and marketers have to care about what happens after a pageview. This is where a lot of marketing teams confuse activity for strategy. A content strategy is not just a calendar. It is the thought that goes into what should exist, why it should exist, who it helps, what question it answers, what decision it supports, and how it connects to the rest of the site. If you sell more than one thing, which most companies do, you need to show how those domains stand alone and how they connect. SEO, paid media, product marketing, technical architecture, conversion, and sales enablement may all belong to the same business goal, but they do not all speak with the same voice or serve the same reader moment. That is why intent still matters. Someone asking “what is SEO?” is not asking the same question as someone asking “best SEO agency for B2B SaaS migration support.” Someone asking “what is AI visibility?” is not asking the same question as someone asking “how do I measure AI citations against named competitors?” The first person may need orientation. The second person may need comparison. The third person may need proof, pricing context, implementation risk, and a reason to trust you. Different questions warrant different responses. This is also why the “make it shorter” advice gets so lazy. Some questions deserve a glossary entry. Some deserve a 1,500-word explainer. Some deserve a decision page with tables, examples, schema, FAQs, sources, screenshots, caveats, and a clean conversion path. Length is not the strategy. Matching the answer to the intent is the strategy. Volume alone is weak. The measurable levers are coverage, freshness, evidence, clarity, and source mix. In other words, teams should stop asking only, “How many pages did we publish?” and start asking, “How well did we cover the retrieval map?” That map has a few layers. You need a strong owned page that clearly explains the topic. You need supporting pages that cover fan-out questions, comparisons, use cases, objections, integrations, and alternatives. You need fresh claims, dated evidence, and visible sources. You need off-site mentions, reviews, community references, video, press, and expert conversations that make your brand easier to verify outside of your own domain. This is why AI visibility behaves less like a traffic game and more like a citation ecosystem. A classic SEO program could often survive by getting the right page to rank for the right keyword. That still matters, but AI surfaces now pull from a more varied source set. Some cited pages rank well in traditional search. Some do not. Some brands show up because they own the site architecture. Some show up because other people talk about them in places the model or system trusts. Surface’s piece on [every AI tool that touches your leads right now](https://withsurface.com/blog/every-ai-tool-that-touches-your-leads-right-now) is a useful reminder that AI is no longer one discrete layer of the marketing stack. AI systems now evaluate, enrich, route, summarize, score, and respond across the lead journey. If those systems touch the buyer before your team does, your content has to carry more explanatory weight than it used to. The uncomfortable part for marketers is that this rewards actual presence. You cannot fake your way into every source layer forever. You can create first-party pages. You can build comparison content. You can update documentation. You can publish research. You can earn mentions. You can encourage reviews. You can show up in community conversations. You can help executives say something useful in public. But at some point, the brand has to become part of the conversation it wants to be cited inside. This is where the cheap version of AI content starts to break. It can create words. It struggles to create legitimate participation. ## The best content gives people a path to walk One of the simplest tests for a content program is whether a reader can walk through it. Can someone move from a basic question to a more specific question to a comparison to a proof point to a conversion page without the site making them work like an unpaid research assistant? A lot of teams publish blogs as if every post lives alone in a field somewhere. Good luck, little blog. Hope someone finds you. Hope they understand what to do next. Hope they can figure out that the product page in the footer is related to the thing they just read. That is not strategy. That is littering with analytics attached. A better system builds paths. A strong informational page introduces the concept. A supporting post answers the common objection. A comparison page helps the reader understand tradeoffs. A case study proves the claim in a real environment. A landing page connects the topic to the service. A conversion page gives the buyer a next step. Internal links do more than pass authority. They show the reader how the company thinks. This is where content and lead operations start to touch. If a buyer reads three educational pages, studies a case study, visits pricing, leaves, returns, and finally books a demo, the content did more than attract traffic. It shaped intent. Surface’s guide on [tracking the full lead journey before a buyer converts](https://withsurface.com/blog/lead-user-journey) speaks to this operationally because teams need to know which pages people read, which problems they appear to be solving, and how seriously they are evaluating the product before they raise their hand. This matters for humans. It also matters for AI systems. People think in categories. They understand relationships, hierarchies, examples, and pathways. Retrieval systems also benefit from clean categories, clear relationships, and well-labeled pages. When marketers build a coherent content architecture, they help both audiences. The human reader can make sense of the path. The machine reader can classify, retrieve, and recommend the source with less ambiguity. That is why technical SEO, content strategy, and editorial quality are starting to blur into one another. Teams cannot separate site structure from comprehension. They cannot separate comprehension from conversion. They cannot separate conversion from trust. Templates are having a moment because everyone wants scalable content. I get it. A good brief helps an editor explain the assignment. A repeatable page structure helps a team keep quality stable. A markdown template can help people stop reinventing the same page every week. A schema pattern can help technical teams publish cleaner pages. Nobody should be romantic about chaos. But a template is a baseline. It is not the goal. When teams treat templates as the finished strategy, they start publishing pages that technically include the right parts and still feel dead. The H1 contains the keyword. The H2s contain the related phrases. The CTA exists. The internal links exist. The FAQ exists. The meta description exists. The page passes the checklist, then fails the reader. Readers can feel when the writer had nothing to say. AI systems may also become better at noticing the same thing through different signals: redundancy, thin evidence, weak source trails, commodity phrasing, poor differentiation, stale claims, and missing context. Even when the system does not “feel” the dullness, the buyer does. This is why the next content advantage will not come from prompt tricks alone. It will come from teams that can combine operational discipline with actual taste, actual reading, actual expertise, and actual evidence. Use AI to accelerate research. Use it to repurpose, revise, summarize, cluster, compare, audit, and structure. Use it to find gaps in your site architecture. Use it to draft the first version when that makes sense. But do not confuse acceleration with judgment. Tools are held by people. First, audit five strategic pages for comprehension, not just SEO. Pick pages that matter to revenue: a core service page, a product page, a comparison page, a case study, and a high-traffic blog. Ask whether a skeptical buyer can understand the claim, verify the proof, compare the options, and take the next step without needing a salesperson to rescue the page. Second, add source trails to the pages where trust matters. Link claims to primary sources, original data, product documentation, customer proof, expert context, and dated evidence. Do not bury the proof in a vague “research shows” sentence. Show the reader where the claim comes from. Third, rebuild your AI visibility measurement around citations, mentions, source inclusion, branded demand, prompt coverage, and sales-call language. Traffic still matters. Rankings still matter. But buyers may encounter you through summaries, recommendations, cited answers, and off-site proof long before they click. Fourth, stop publishing isolated blogs with no path. Every meaningful blog should know where it sits in the system. What pillar does it support? What landing page does it point to? What comparison or objection does it answer? What should the reader read next? What should sales do with it? Fifth, connect content to conversion operations. Surface’s guide to [inbound lead generation](https://withsurface.com/blog/inbound-lead-generation) frames content as one way potential customers discover, engage, and exchange information for value. That only works cleanly when marketers build the path from content to qualification to routing to follow-up with the same care they bring to the page itself. Sixth, put a reading person in the content QA process. I mean that seriously. Someone on the team should have enough active relationship with reading to notice pacing, confusion, flattening, repetition, false clarity, missing context, weak transitions, and fake usefulness. This does not need to be precious. It needs to be operational. People love to say no one reads. I think the truth is more annoying and more useful: people read when reading helps them. They read when the stakes are high. They read when the page respects their intelligence. They read when the structure gives them somewhere to go. They read when the writer knows the subject. They read when the content helps them make a decision they could not make as confidently before. That is the bar. In the retrieval era, marketers are no longer writing only for a search engine or only for a human reader. They are writing for a chain of interpretation: crawler, index, model, summary, citation, buyer, stakeholder, sales call, internal champion, procurement process, board conversation. At every point in that chain, comprehension can improve or decay. So yes, make the page scannable. Yes, structure the argument. Yes, use clear headings. Yes, answer the query. Yes, help the model retrieve the claim. But also, for the love of all things readable, read something longer than a feed before declaring how readers work. The future of content marketing belongs to teams that can publish consistently, prove their claims, build useful paths, and write with enough respect for the reader that the page feels like it was made by someone who has spent time inside language. That is not nostalgia. That is operations. If your team wants the content path and conversion path to work together instead of living in separate systems, [Surface Labs helps B2B teams capture, qualify, route, and convert inbound leads](https://withsurface.com/book-a-demo) after the reader finally raises their hand. --- # Most Effective Lead Generation Tactics for B2B Teams in 2026 | Surface Labs URL: https://surface.thesurface.network/blog/most-effective-lead-generation-tactics-for-b2b-teams-in-2026 People search for the most effective lead generation tactics as if the answer is a ranked list — paid search is number one, content is number two, events are number three. Then someone downloads the template and discovers the list didn't solve the actual problem. Lead generation works as a system. A tactic can create attention, but attention only becomes useful when the right people encounter a relevant offer, understand the value exchange, and enter a follow-up path that fits the question they were trying to answer. Teams lose leads at every one of those handoffs, often while debating channel performance as if the channel were the whole story. The effective tactic is usually the one that matches the buyer's moment and connects cleanly to the operating work after the click. Lead generation gets expensive when a team starts from a channel rather than a customer problem. "We need more LinkedIn leads" is an activity choice — it doesn't tell you what a prospective customer needs to understand or what happens when they respond. Define the situation first: people who don't yet have language for the problem, people comparing alternatives, people already seeking a provider. Someone in early research might respond to a detailed guide or a benchmark. Someone near a decision needs implementation detail or a direct conversation. A good lead program doesn't force both through the same gate. We make the same distinction for content in our [2026 content marketing guide](https://withsurface.com/blog/content-marketing-guide-2026): intent beats volume because different questions require different answers, and lead generation needs that discipline before the ad or the form ever get built. ## Build durable inbound demand through useful content For most B2B teams, content isn't a quick replacement for paid acquisition — it's a way to build a useful library around the problems the company can credibly solve. The important word is useful. Pages that exist only to capture a keyword may draw impressions and still fail to give anyone a reason to trust the business. [Google's people-first content guidance](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) offers a practical standard: does the work provide substantial information beyond the obvious answer? In B2B, the test is even simpler — could a buyer send it to a colleague because it makes a decision easier? AI search has raised the value of clear, current, well-sourced pages, and our [guide to AI search optimization](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) explains why citable pages still rest on classic technical and editorial foundations, not a mention-count shortcut. Paid search, paid social, and retargeting work best when teams know what they're trying to learn or reach — search capturing active demand around a category, paid social putting a credible point of view in front of a defined audience. The offer has to match the audience's awareness. Sending a cold prospect straight to "book a demo" underperforms when they've never heard of the category, and the landing page needs to carry the argument forward — our [guide to landing pages](https://withsurface.com/blog/what-makes-a-good-landing-page-why-blogs-need-conversion-pages) covers what that page needs to do: explain the problem, show how the work happens, and make the next step feel proportionate. Treat paid campaigns as a source of buyer language too — search terms and form answers can reveal where the messaging is unclear, and that insight should improve the content, not just live inside the media account. Some of the strongest B2B leads come from people who already have trust with the buyer. Partners can introduce a company in a relevant implementation context. Customers can provide proof that's more credible than a brand claim. Community participation can create awareness before a buyer enters a formal research process. These tactics only work when the company contributes something useful — a diagnostic, a real data point, a strong customer example — rather than a generic white paper nobody asked for. The same rule applies to self-promotional content: it can help a brand become associated with a category, but it doesn't manufacture recommendation or trust the way third-party proof does. This is where many lead generation programs quietly waste money. A campaign produces a form fill, the form routes to a generic inbox, a rep receives it later with almost no context, and the buyer disappears before the dashboard even finishes counting the conversion. We call the work between form submission and an actual conversation Lead Intelligence. Our [B2B SaaS routing guide](https://withsurface.com/blog/lead-capture-and-routing-for-b2b-saas-companies) shows why speed, account segment, and product interest all matter — a qualified enterprise request shouldn't get the same response as someone who downloaded a research guide. Build the response path deliberately: a form that captures what's needed to route well, enrichment where it helps, and a recovery plan for people who are interested but not ready. That work often creates more meetings than a new channel, because it recovers value already being generated. Don't judge a tactic only by its cost per lead. A cheap lead that never receives a useful response isn't cheap, and a high-cost lead from a narrow, high-intent source may be worthwhile if it produces qualified conversations. Track the full path — source, offer, form completion, qualification, routing time, meeting, and sales feedback — reviewed by segment and use case rather than only by channel. Our [attribution guide](https://withsurface.com/blog/attribution-is-not-incrementality-how-to-measure-ai-creative) offers a useful warning here: attribution tracks touchpoints, but it doesn't automatically prove incremental business value, so use the reporting to make better choices while keeping the uncertainty visible. The most effective lead generation tactic is rarely one tactic. It's a clear offer for a specific buyer moment, supported by content and proof, followed by a response system that treats the lead like a person rather than a new row in a spreadsheet. Build that system first, then decide which channels deserve more investment. --- # MQL vs SQL: Differences, Examples, and How to Improve MQL-to-SQL Conversion (Modern B2B Guide) | Surface Labs URL: https://surface.thesurface.network/blog/mql-vs-sql MQL stands for marketing qualified lead—a prospect who has engaged with your marketing but isn't ready to buy yet. SQL stands for sales qualified lead—someone who has been vetted and is ready for a direct sales conversation. The difference comes down to intent and readiness: MQLs are researching, SQLs are evaluating. Getting this distinction right matters because it determines who owns the lead, what happens next, and whether your sales team wastes time on prospects who aren't ready. This guide covers the definitions, criteria examples, and the operational workflow that actually improves MQL-to-SQL conversion. MQL stands for marketing qualified lead. It refers to a prospect who has engaged with your marketing efforts and meets criteria that suggest they're more likely to become a customer than a random website visitor. The key distinction here: an MQL has shown interest, but they're still in the research or awareness stage. They're not ready for a sales pitch yet. Marketing teams own MQLs. The job is to nurture them with helpful content—guides, webinars, case studies—until they signal stronger buying intent. Think of an MQL as someone browsing the shop window. They're curious, maybe even interested, but they haven't walked in to ask about pricing. ### Common MQL criteria and examples MQL criteria typically break into two buckets: fit and intent. - **Fit signals:** Company size matches your ideal customer profile, relevant industry, appropriate job title, geographic location you serve - **Intent signals:** Downloaded a whitepaper, attended a webinar, visited your pricing page more than once, subscribed to your newsletter Here's a concrete example. A marketing manager at a 200-person software company downloads your "Guide to Lead Routing." They match your target profile and they've taken an action that shows interest. That's an MQL. They haven't asked to talk to sales, but they're worth paying attention to. SQL stands for sales qualified lead. An SQL is a prospect who has been vetted and is ready for direct sales engagement. Unlike MQLs, SQLs have demonstrated specific buying intent. They're not just researching—they're actively considering a purchase. based on [purchase intent signals](https://withsurface.com/blog/leveraging-purchase-intent-data-to-identify-high-quality-leads). SQLs sit closer to the bottom of the funnel. They've either requested a demo, asked about pricing, or been validated by a sales development rep (SDR) as having real potential to close. If an MQL is someone browsing the window, an SQL is someone who walked in and asked how much the product costs. ### Common SQL criteria and examples SQL criteria focus on readiness and validation rather than just engagement. - **Explicit buying signals:** Requested a product demo, started a free trial, asked about pricing or contract terms - **Qualification confirmation:** Confirmed budget exists, identified a timeline, has decision-making authority - **Validated contact info:** Real business email, verified phone number, enriched company data A director of revenue operations fills out your demo request form. They confirm they're evaluating solutions this quarter and work at a company in your target segment. That's an SQL—someone sales can pursue with confidence. The core difference between MQLs and SQLs comes down to buying intent and funnel position. MQLs are exploring options. SQLs are evaluating solutions. Feature MQL SQL **Buying intent** Interested in the topic, not ready to buy Ready for a sales conversation **Funnel stage** Top-to-middle (research phase) Middle-to-bottom (decision phase) **Typical engagement** Content downloads, webinars, blog visits Demo requests, pricing inquiries, trial signups **Owned by** Marketing team Sales team **Next action** Nurture with content Direct outreach and qualification call ### What comes first, MQL or SQL? MQL typically comes first. A lead engages with marketing content, gets nurtured over time, and eventually shows enough buying intent to become an SQL. That said, some leads skip the MQL stage entirely. A demo request from a perfect-fit company with clear intent might go straight to SQL status. Your process can accommodate both paths—the linear journey and the shortcut. ### Do MQLs always become SQLs? No, and that's completely normal. Many MQLs require extended nurturing. Some get disqualified because they're the wrong fit, lack budget, or have bad timing. Others simply go cold. A healthy system captures rejection reasons and recycles leads appropriately. Someone who's "not ready now" might be ready in six months. You want a re-engagement path, not a dead end. The traditional funnel assumes everyone moves neatly from awareness to consideration to decision. Reality looks messier. Modern B2B buyers research across multiple channels. They involve buying committees with different stakeholders. They revisit your site weeks apart, engage with competitors simultaneously, and often make decisions through conversations you never see. A prospect might download content, disappear for a month, then suddenly request a demo. This means MQL and SQL work better as states based on evidence rather than mandatory sequential stages. Your qualification system captures signals wherever they appear and routes leads based on what you actually know about them—not where they "should" be in a theoretical funnel. Even though journeys aren't perfectly linear, you still want a clear operational workflow. Here's how the handoff typically works in practice. ### 1\. Capture intent including partial form submissions Every form submission is a signal, even incomplete ones. If someone fills in their email and company name but abandons before finishing, that's still valuable data you can act on. Modern form tools capture partial responsesModern [form tools capture partial responses](https://withsurface.com/product/forms-and-workflows), enrich them with company data, and trigger follow-up workflows automatically. This matters because a significant portion of form starters never complete the full submission. Without partial capture, those leads simply vanish.[those leads simply vanish](https://withsurface.com/blog/bad-forms-are-killing-your-conversions). ### 2\. Enrich before you route Routing based on incomplete data causes problems. SDRs waste time on leads that don't match your ideal customer profile. High-value leads get assigned to the wrong rep. Everyone gets frustrated. Before a lead hits sales, you want key data points filled in: company size, industry, tech stack, revenue range, and any available intent signals. Real-time enrichment makes this automatic rather than manual, so leads arrive with context attached.[Real-time enrichment](https://withsurface.com/product/lead-data-platform) makes this automatic rather than manual, so leads arrive with context attached. ### 3\. Qualify with scoring Lead scoring[Lead scoring](https://docs.withsurface.com/leads/lead-score) assigns points based on fit and behavior, then triggers actions when thresholds are met. - **Rules-based scoring** works well when your ideal customer profile is clear and your funnel is straightforward - **AI-assisted scoring** handles edge cases better, adapts to changing patterns, and can weigh signals you might not have considered The goal is consistent, defensible decisions about which leads deserve sales attention right now versus which ones stay in nurture. ### 4\. Route instantly with context Speed matters more than most teams realize. Leads contacted within minutes of a form submission convert at higher rates than leads contacted hours later. The difference can be significant. Your routing logic might consider territory, company segment, product interest, or rep capacity. What matters most is that routing happens immediately and includes enough context for the rep to have a relevant first conversation. > **Tip:** Set SLA timers with alerts. If a high-intent lead sits unworked for more than 15 minutes, someone on your team gets notified. ### 5\. Create a closed-loop feedback system When sales accepts or rejects a lead, that information flows back to marketing. Structured rejection reasons—"not ICP," "competitor," "no budget," "bad data"—help you refine scoring and targeting over time. Leads that aren't ready now go into nurture tracks with re-qualification triggers. Maybe they re-engage with high-intent content in three months, and the cycle starts again. Generic definitions don't work. Your criteria depend on your sales motion, deal size, and team capacity. ### Minimum data requirements before routing Before a lead reaches sales, you typically want: - **Verified business email:** Not personal domains like Gmail or Yahoo - **Company name and size:** To confirm fit with your ideal customer profile - **Job title or function:** To assess whether they have authority or influence - **Intent signal:** What action triggered the lead - **Source attribution:** Where they came from The more complete the data, the better the first conversation. Enrichment tools can fill gaps automatically so reps don't waste time researching. ### Example criteria by segment **High-velocity SMB inbound:** - MQL: Business email + company under 200 employees + downloaded content or visited pricing page twice - SQL: Demo request or trial signup with verified contact info **Mid-market demo-driven:** - MQL: Director+ title + company 200-2,000 employees + engaged with product content - SQL: Demo request + confirmed use case + timeline within 6 months **Enterprise/ABM mixed motion:** - MQL: Target account + any engaged contact + multiple touchpoints - SQL: Meeting booked with economic buyer or champion + validated by SDR Here's what actually moves the conversion number: - **Reduce lead loss:** Capture partial form submissions and trigger enrichment even on incomplete data - **Increase data completeness:** Enrich and verify before routing so sales gets actionable leads - **Speed up follow-up:** Respond to high-intent leads in minutes, not hours - **Improve routing accuracy:** Segment by intent and fit [Segment by intent and fit](https://withsurface.com/blog/how-intelligent-lead-segmentation-drives-personalized-marketing-campaigns), not just round-robin assignment - **Close the feedback loop:** Use rejection reasons to refine scoring and targeting ### Benchmarks worth tracking MQL-to-SQL conversion rate is just one metric. A complete picture includes several other measurements. - **Speed-to-lead:** Minutes from form submission to first outreach - **Contact rate:** Percentage of leads you actually reach - **Sales acceptance rate:** Percentage of MQLs that sales agrees are qualified - **Meeting set rate:** Percentage of SQLs that book a call - **Lead-to-opportunity:** How many leads become real pipeline ### Scale considerations At 50+ inbound leads per day, manual processes break down. You'll likely want automated deduplication to prevent multiple reps working the same account. Capacity-based routing ensures no rep gets overwhelmed. After-hours coverage or next-business-day SLAs with alerts keep leads from going stale. And enrichment that runs in real-time prevents bottlenecks. The right tooling handles capture, enrichment, scoring, routing, and follow-up as one connected system rather than a patchwork of point solutions. **Capabilities that matter:** - Partial response capture from forms - Real-time enrichment and validation - Flexible routing rules with ownership logic - SLA timers and speed-to-lead automation - CRM sync with proper field mapping - Visibility into why leads were accepted or rejected If your bottleneck is inbound capture, enrichment, and routing working together, [Surface Labs](https://withsurface.com/book-a-demo) connects these pieces. Forms capture partial submissions, enrichment runs in real-time, and automated routing triggers follow-up workflows—all in one system. Alignment isn't about more meetings. It's about shared systems and clear documentation. - **Shared definitions in your CRM:** Everyone sees the same lifecycle stages and criteria - **Shared dashboards:** Marketing and sales look at the same conversion metrics - **Documented SLAs:** Response time expectations, rejection reason requirements, recycle rules - **Regular feedback loops:** Sales tells marketing which leads convert and why others don't A one-page SLA document that covers qualification criteria, routing logic, response time targets, and rejection categories prevents most alignment arguments before they start. ### What is a good MQL-to-SQL conversion rate? Conversion rates vary significantly by segment and motion. High-intent demo request funnels might see 30-40%, while content-driven nurture funnels might see 5-10%. Track your own baseline and focus on improving it rather than hitting an arbitrary industry number. ### How long does it take to convert an MQL to an SQL? It depends on your sales cycle and lead source. Demo requests might convert same-day. Content MQLs might take weeks or months of nurturing. Measure your actual cycle times by segment so you can set realistic expectations. ### Why does sales reject MQLs? Common rejection reasons[Common rejection reasons](https://withsurface.com/blog/5-biggest-problems-with-inbound-marketing-leads) include: wrong fit for your ideal customer profile, missing or bad contact data, no budget or authority, already a customer or competitor, and spam or fake submissions. Tracking rejection reasons helps you fix upstream problems in targeting and qualification. ### What data do you need before routing a lead to sales? At minimum: verified business email, company name, and the intent signal that triggered the lead. Ideally, you also have company size, industry, job title, and any enrichment data that confirms fit. The more context sales has, the better the first conversation goes. Teams using Surface Labs see 30-50% lift in website conversions by capturing partial form submissions, enriching leads in real-time, and routing instantly with full context. If your inbound leads are leaking between form fill and sales follow-up, [book a demo](https://withsurface.com/book-a-demo) to see how the system works. --- # Paid Search in AI Interfaces: How to Test AI Max Without Losing the Plot | Surface Labs URL: https://surface.thesurface.network/blog/paid-search-ai-interfaces-ai-max-measurement Paid media teams are being asked to do something familiar under new conditions: trust the machine, feed it better data, and explain the result to finance. Google’s latest AI Search ad updates make that pressure more visible. The company is expanding ads into AI Mode and testing new ad formats built with Gemini. It is also expanding Direct Offers and building more AI-assisted experiences that help brands answer buyer questions, surface offers, and move closer to transactions inside Google’s search environment. For paid media teams, this is not a small interface update. It changes where ads appear, how intent gets interpreted, and what marketers can reasonably prove from the reporting they receive. The tempting response is to treat AI Max or AI Search ads as another campaign setting. Turn it on, watch the dashboard, report conversion movement, and decide whether it worked. That would be too easy. The harder and more useful view is that AI-powered paid search is a measurement readiness test. The teams that benefit will likely be the teams with clean conversion signals, clear campaign boundaries, strong landing pages, useful CRM feedback, and enough patience to separate new inventory from actual demand quality. AI media can expand reach. It cannot repair a broken measurement system on its own. Paid search has always involved some negotiation between control and automation. Exact match gave marketers a feeling of control. Broad match and Smart Bidding asked them to give the system more room. Performance Max pushed that tradeoff further by bundling more surfaces and signals into one system. AI Max and AI Search ads continue the same direction, except the interface itself is changing. Search behavior in AI interfaces is less clean than a keyword report makes it appear. A buyer may ask a conversational question, compare options, refine criteria, and see an ad inside a more fluid answer environment. The original query may contain category intent, comparison intent, objection language, product requirements, and purchase readiness all at once. That can be useful for marketers because it gives the system more context. It can also make reporting harder because the path from query to ad to conversion is less legible. Search Engine Land’s coverage of Google’s AI Max clarifications highlighted a practical issue: AI Max is not the only path into AI Search ads, and advertisers should not assume they will get a clean separate breakout for AI Overviews or AI Mode performance. That matters because reporting structure shapes decision quality. If AI placements are blended into broader top-of-page or search reporting, marketers need to design tests around what they can observe, not what they wish the interface would expose. A paid media leader should ask a simple question before any AI Max test: what would we need to see to believe this helped the business? If the answer is “more conversions,” the test is not specific enough. Google’s enhanced conversions and offline conversion import updates point to the less glamorous truth underneath AI media. Better automation depends on better signals. If the platform is optimizing toward form fills that sales rejects, duplicate leads, junk demo requests, or unqualified conversions, automation can scale the wrong outcome with impressive speed. For B2B teams, the conversion event is rarely the true business event. A demo request is useful only if the person fits the market, has a real problem, routes to the right rep, responds quickly enough, becomes a meeting, and eventually creates qualified pipeline. Paid search often gets credit too early in that chain. AI-powered paid search can make the problem worse if teams give it more room while feeding it weak feedback. Before expanding into AI Max or AI Search-heavy tests, teams should audit conversion quality: - Are form fills deduped before they become conversion events? - Are spam and fake leads excluded from optimization? - Are offline conversions passed back from the CRM? - Are MQL, SQL, opportunity, and customer stages mapped correctly? - Does Google Ads receive enough qualified conversion volume to learn from? - Are high-value and low-value conversions weighted differently? - Are lead source and landing page signals preserved through the CRM? - Does sales provide feedback on lead quality soon enough to influence budget decisions? This is where [inbound marketing automation](https://withsurface.com/blog/inbound-marketing-automation) becomes paid media infrastructure. A campaign can only optimize toward the truth if the post-capture system sends the truth back. Brand campaigns feel safe because the user already knows the company. In ordinary search, that logic is mostly reasonable. If someone searches your exact company name, you want to protect the path, control the message, and keep competitors from intercepting demand. AI Max complicates that comfort because campaign expansion, matching, and eligibility rules can move beyond the simple mental model of “someone searched our name.” Practitioner analysis has already warned that many brand campaigns may not be ready for AI Max. The concern is not that AI Max is inherently bad for brand. The concern is that brand campaigns often contain messy assumptions. They may mix exact brand defense, competitor defense, remarketing-like behavior, high-intent returning users, and broader category exploration in the same reporting view. When AI expansion enters that mix, it becomes harder to know whether the campaign protected demand, created demand, or simply took credit for demand that was already arriving. A better structure separates jobs: - **Brand defense:** Capture people already searching for the company. - **Competitor defense:** Protect against competitor comparison or conquesting behavior. - **Category expansion:** Reach buyers searching for problem or solution language. - **Returning-user capture:** Bring back people already influenced by content, sales, or product research. - **AI interface testing:** Learn whether broader conversational inventory creates qualified behavior. Those jobs may still interact, but they should not be reported as one blob. When paid teams keep the jobs separate, finance can see whether spend is protecting existing demand or creating incremental opportunity. Teams working on [lead journey tracking](https://withsurface.com/blog/lead-user-journey) should pay special attention to branded search after AI exposure. A buyer may first encounter a recommendation in an AI answer, then search the brand later. Last-click reporting may credit brand search. A stronger journey view asks what made the brand memorable enough to search. ## Landing pages must resolve wider intent When search becomes more conversational, landing pages need to do more interpretive work. A keyword-era landing page could often assume a narrow intent. An AI-era paid search visit may come from a broader decision path. The buyer may have asked for alternatives, implementation advice, pricing guidance, category recommendations, or comparison criteria before clicking. A strong landing page for AI-powered paid search should answer five questions quickly: 1. Who is this for? 2. What problem does it solve? 3. Why should the buyer believe it? 4. How does it compare to adjacent options? 5. What happens after the buyer converts? That does not mean every landing page should become a giant educational essay. It means the page needs enough clarity, proof, and routing logic to meet a buyer whose intent may be more complex than the campaign label suggests. For B2B SaaS and technical products, this usually means stronger above-the-fold positioning, clearer proof blocks, use-case-specific sections, integration language, customer evidence, and conversion paths that match buying stage. If a paid AI search test sends broad category demand to a vague demo page, the channel will get blamed for a page-level failure. If the same test sends buyers to a page that explains the problem, shows the use case, names the tradeoffs, and gives a clear next step, the team gets a cleaner read on whether the traffic is worth pursuing. This is why [how to actually measure lead quality](https://withsurface.com/blog/how-to-actually-measure-lead-quality-not-just-lead-volume) belongs inside the paid search conversation. A landing page should not be judged only by form-fill rate. It should be judged by whether the resulting leads are useful, reachable, qualified, and worth sales attention. Every AI Max or AI Search ad test should include a caveat section in the report. That may sound defensive, but it is actually what makes the report credible. A good caveat section should answer: - Which placements or surfaces were visible in reporting? - Which surfaces were blended into broader reporting? - Which conversion events were used for optimization? - How much qualified conversion volume was available? - Which campaigns were used as comparisons? - Were brand and non-brand separated? - Did seasonality, product launches, pricing changes, or sales campaigns affect the same period? - Were lead quality and sales acceptance reviewed? - What would need to be true before increasing budget? Marketers often avoid caveats because they fear caveats make the work look uncertain. AI paid media is uncertain. Naming uncertainty is how teams keep budget conversations sane. A useful report might say: “AI Max expansion increased reported conversions by 18%, but sales acceptance did not improve and most lift came from lower-fit form fills. Recommendation: pause expansion, improve conversion weighting, and retest against qualified lead events.” Another useful report might say: “AI Search-eligible campaigns produced lower volume but higher pricing-page engagement and stronger sales acceptance. Sample size remains small. Recommendation: continue test for 30 more days and pass SQL-stage feedback into optimization.” Both reports are more valuable than “AI Max worked” or “AI Max did not work.” Paid teams can test AI Max and AI Search inventory responsibly by treating the rollout as an operating experiment. ### Start with readiness Audit conversion events, CRM feedback, landing pages, campaign structure, and exclusion rules. Do not give the system broader freedom until the data tells it what success actually means. ### Choose the right campaign job Avoid starting with the messiest brand campaign if the account cannot separate protection from expansion. Non-brand category campaigns, high-intent problem campaigns, or tightly controlled use-case campaigns may provide cleaner learning. ### Define the business outcome Use qualified leads, sales-accepted leads, opportunities, or pipeline influence where possible. Form fills can remain a diagnostic metric, but they should not be the final proof. ### Preserve comparison logic Use pre/post comparisons carefully. Use holdouts where possible. Compare against similar campaigns, geographies, or segments. If reporting cannot isolate AI Mode or AI Overviews cleanly, say that. ### Watch query and audience drift AI expansion can uncover new demand, but it can also wander. Review search terms, audience behavior, landing page engagement, and lead quality. Do not wait until the monthly report to discover that the campaign spent three weeks learning the wrong audience. ### Connect the post-click path Track pricing views, integration views, case study views, demo starts, form completion, meeting booking, sales response, and opportunity creation. The post-click path is where a lot of AI media truth will appear. ### Decide before scaling Define scale criteria in advance. For example: maintain cost per qualified meeting within 15% of benchmark, improve sales acceptance, preserve lead fit, and show no major increase in junk leads. Without scale criteria, every result becomes negotiable. Paid search in AI interfaces is going to reward operational maturity. The teams most likely to learn are not necessarily the teams with the largest budgets. They are the teams with the cleanest feedback loops. Before scaling AI Max or AI Search-facing campaigns, clean up conversion data. Separate campaign jobs. Strengthen landing pages. Connect source behavior to CRM stages. Review lead quality weekly. Add caveats to reporting. Give finance a clear distinction between reach, reported conversions, qualified demand, and revenue influence. AI paid media is not a magic new channel. It is paid search entering a more fluid interface with more automation and less clean placement visibility than marketers want. That does not make it useless. It makes discipline more valuable. The toggle is not the strategy. The system around the toggle is. --- # Query Fan-Out in Google AI Search: How Marketers Should Build Content Architecture | Surface Labs URL: https://surface.thesurface.network/blog/query-fan-out-in-google-ai-search-how-marketers-should-build-con A content lead opens the quarterly keyword plan and sees the familiar grid: primary keyword, search volume, difficulty, intent, URL, status. The plan looks organized. Every topic has a target. Every target has a page. Then someone asks a harder question: what happens when Google AI Search turns one buyer question into ten related searches before forming an answer? That question changes the shape of the work. A classic SEO plan can still help a team decide which pages to create, which terms to prioritize, and which queries matter. Query fan-out asks a different question. Can the company satisfy the research path around the query, not just the keyword itself? Google says AI Overviews and AI Mode may use query fan-out, which means the system can issue multiple related searches across subtopics and data sources to develop a response. In practical terms, a buyer’s single prompt can become a small research project. The system may look for definitions, comparisons, use cases, constraints, implementation details, alternatives, risks, examples, product claims, and evidence before it decides what answer to assemble. That turns content architecture into the real work. Teams that want stronger AI visibility should stop asking whether one page can rank for one phrase and start asking whether their owned and off-site source ecosystem can answer the full question field around a buyer’s intent. The page still matters. The cluster matters more. Query fan-out is the process by which an AI search system expands one user query into multiple related searches. Instead of treating a prompt as one isolated keyword, the system breaks the question into subtopics, retrieves information from different sources, and uses those materials to generate a more complete answer. Google has used this language publicly in relation to AI Mode and AI Overviews. Its documentation for AI features in Search says both experiences may use query fan-out to issue multiple related searches across subtopics and data sources. Google’s AI Mode announcement also described the system as breaking a question into subtopics and issuing many searches at once to explore the web more deeply than a traditional search. For marketers, the implication is simple enough to state and hard enough to execute: AI visibility depends on coverage, structure, evidence, and source clarity. A single optimized blog post may help, but it rarely satisfies the full research pattern behind a serious buyer query. Content teams need to build answer systems. That does not mean teams should abandon SEO fundamentals. Thinking through [Google’s generative AI search guidance](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) should push marketers toward useful, crawlable, well-structured pages with strong evidence and clear internal links. Query fan-out does not make SEO irrelevant. It makes weak content architecture easier to expose. ## What query fan-out changes about content strategy The old content model often looked like this: find a keyword, assign a page, write the content, optimize the title, include related phrases, add internal links, publish, and wait. Better teams added intent analysis, competitive review, expert input, conversion paths, and refresh cycles. Even then, the basic planning unit often remained the same: one query, one page. Query fan-out changes that planning unit. When a buyer asks an AI system “What is the best AI visibility platform for a B2B SaaS company?” the system may need to understand what AI visibility means, how teams measure it, which platforms exist, which sources mention them, which use cases matter, how SEO rankings differ from AI citations, what reporting methods are credible, and what kinds of companies need this work. The original query becomes a network of related questions. A content team that only has one page targeting “AI visibility platform” may appear thin inside that network. A team with a clear category page, measurement guide, dashboard explainer, comparison framework, implementation checklist, customer proof, and source-backed methodology has more chances to satisfy the system’s retrieval path. This is why [AI citations and SEO rankings](https://withsurface.com/blog/ai-citations-vs-seo-rankings) need to be treated as related but different visibility states. A page can rank without being cited. A source can be cited without driving a traditional click. A brand can be mentioned because a third-party source explained the category better than the brand did. Query fan-out increases the number of places where a company can win, lose, or disappear. ## Why content architecture matters more than isolated pages Content architecture is the way a company organizes, connects, and proves its ideas across the site and broader source ecosystem. It includes pillar pages, blogs, product pages, case studies, comparison pages, glossary entries, documentation, internal links, external citations, off-site mentions, and conversion paths. In classic SEO, architecture helped search engines crawl the site, understand topical relationships, distribute authority, and move users from one page to another. In AI search, architecture also helps retrieval systems understand whether the company has enough complete, coherent, and supported material to answer a broader question. Marketers should think of every serious category as a small library rather than a single article. A library has a front desk, shelves, labels, cross-references, source notes, and pathways. A single article may answer one question. A library helps someone keep asking better questions without getting lost. That library still needs business intent. Teams should connect informational pages to product pages, product pages to proof, proof to conversion, and conversion pages to lead handling. When a buyer moves from research into action, [lead journey tracking](https://withsurface.com/blog/lead-user-journey) can help teams understand what they read, compared, and considered before they converted. Query fan-out may shape discovery, but the post-discovery path still decides whether visibility becomes pipeline. A query fan-out map starts with one priority buyer question. The team should choose a question that matters commercially, not merely a phrase with attractive volume. Good candidates include category queries, comparison queries, problem-solution queries, implementation queries, and “best tool” queries that could influence vendor selection. Start with the main query, then list the adjacent questions an AI system or buyer may need answered before forming a confident answer. These usually fall into several groups: definitions, category context, alternatives, comparisons, use cases, implementation details, risks, constraints, pricing considerations, proof requirements, and next steps. For example, a query like “How should B2B marketers measure AI visibility?” might fan out into the following subquestions: Fan-out area Example subquestions Definition What is AI visibility? How is it different from SEO visibility? Measurement Should teams track citations, mentions, rankings, recommendations, or share of voice? Tooling What should an AI visibility dashboard include? Reliability How often should prompts be tested? How much variation is normal? Source mix Which sources influence AI answers? Business value How does AI visibility connect to pipeline, trust, and conversion? Action What should teams change when a brand is absent or misrepresented? Once the map exists, the content team can decide which questions deserve their own pages, which can live as sections, which belong in sales enablement, and which need external validation. A query fan-out map should become an editorial planning document, an internal linking plan, and a measurement plan at the same time. ## The content architecture model marketers should use A useful query fan-out architecture has five layers: the category page, the supporting cluster, the proof layer, the conversion path, and the off-site source ecosystem. ### The category page The category page should define the market, explain the problem, clarify the company’s point of view, and direct readers toward the next relevant page. It should not try to answer every related question in exhausting detail. Its job is to act as the central destination and organizing layer. For example, a company building around generative engine optimization should have a clear page that explains what the category is, why it matters, how the company approaches it, and what buyers should do next. Thinking about [generative engine optimization services](https://withsurface.com/blog/generative-engine-optimization-services) this way keeps the page from becoming either a thin service description or an overstuffed encyclopedia. ### The supporting cluster The supporting cluster answers the adjacent questions. These can include educational posts, comparison guides, implementation articles, glossary entries, technical explainers, use-case pages, and objection-handling pieces. Each page should have a distinct job. Teams should avoid publishing five lightly different versions of the same answer. A strong cluster helps a buyer move from “What is this?” to “How does it work?” to “How should I evaluate it?” to “What should I do next?” That sequence matters because query fan-out often mirrors the way thoughtful buyers research. They rarely ask one question and stop. They ask a question, learn enough to ask a better one, and keep narrowing the field. ### The proof layer The proof layer includes case studies, statistics, screenshots, benchmarks, expert quotes, methodology notes, customer examples, original research, and third-party validation. AI systems and human buyers both need evidence. Unsupported claims are cheap now. Proof is the differentiator. For AI visibility topics, proof may include prompt-test methodology, source mix analysis, citation tracking, competitor benchmarking, and examples of how model behavior changes across prompt families. An [AI visibility dashboard](https://withsurface.com/blog/ai-visibility-dashboard) should therefore do more than display a score. It should help teams understand where visibility comes from, where competitors appear, and which content gaps deserve action. ### The conversion path A query fan-out architecture should never stop at information. Teams need to decide where the reader should go after each page. Some pages should send readers to a product page. Some should send them to a comparison guide. Some should send them to a case study. Some should invite a newsletter subscription. Some should point toward a demo or consultation. The conversion path needs to match intent. Someone reading a beginner definition probably does not need an aggressive demo CTA. Someone reading a comparison article may be close enough to evaluate a vendor. Someone reading implementation guidance may need proof, pricing context, or a technical conversation. When teams connect the content cluster to [inbound lead management](https://withsurface.com/blog/inbound-lead-management), they can design follow-up around what the buyer actually showed interest in, rather than treating every form fill the same. ### The off-site source ecosystem AI search does not only learn from a company’s website. Third-party lists, review sites, communities, videos, analyst mentions, podcasts, partner pages, social posts, and earned media can all affect how a brand appears in AI-shaped answers. Query fan-out increases the chance that the system will look beyond owned pages for corroboration. Marketers should identify which off-site sources currently shape their category. Search results, AI answers, competitor citations, trade publications, review platforms, YouTube results, Reddit threads, and analyst pages can all reveal the source ecosystem. The question is not whether the company can control every source. It cannot. The question is whether the company can participate credibly enough that external sources reinforce rather than contradict the owned narrative. Internal linking should stop behaving like an SEO afterthought. In a query fan-out world, links are part of the answer path. They tell humans and crawlers how ideas relate, which pages carry authority, and where the next useful piece of context lives. A strong internal link should help the reader move naturally from one stage of understanding to another. A definition page might link to a strategy page. A strategy page might link to a measurement page. A measurement page might link to a dashboard page. A dashboard page might link to a lead journey page. The anchor text should describe the actual concept, not a vague “learn more” destination. Teams should also link vertically and horizontally. Vertical links move readers from educational pages to product or service pages. Horizontal links connect related articles inside the same research path. Both matter. Vertical links help commercial intent. Horizontal links help coverage and comprehension. The best test is simple: if a buyer landed on any page in the cluster, could they find the next page they would reasonably need? If the answer is no, the cluster may exist as a publishing list rather than an architecture. The first mistake is trying to answer every fan-out question on one massive page. Long pages can work when the topic demands depth, but many teams create oversized pages because they are afraid to make architectural decisions. A better structure usually includes one strong category page and several focused supporting pages. The second mistake is creating a swarm of thin pages. Query fan-out does not reward a site for publishing lightly rewritten fragments. Each page needs a reason to exist. If the page does not add a distinct angle, example, proof point, use case, or decision aid, the team should fold it into another page or skip it. The third mistake is ignoring proof. AI search visibility often depends on whether sources can support a claim. Human buyers work the same way. If a page says the company is faster, safer, more accurate, easier to implement, or better suited to a use case, the page should show evidence. The fourth mistake is treating AEO or GEO as a separate layer from SEO. Query fan-out depends on retrieval. Retrieval depends on crawlability, indexability, text access, internal links, structured content, and page quality. Teams should not chase AI visibility while leaving their core site confusing, stale, or technically weak. Start by choosing three to five commercially important questions. These should be questions a serious buyer, founder, CMO, product marketer, or operator might ask when deciding how to solve a real problem. Avoid building the plan around vanity keywords that do not map to business intent. For each question, create a fan-out map. Identify the definition questions, comparison questions, implementation questions, proof questions, risk questions, and conversion questions. Then mark which existing pages already answer them well, which pages need refreshes, and which pages do not exist yet. Next, assign each content asset a specific job. Do not simply say “blog.” Say whether the asset should educate, compare, prove, convert, reassure, challenge, or route. A cluster filled with pages that all perform the same job will feel repetitive to readers and incomplete to retrieval systems. Then fix the links. Connect the category page to the supporting pages. Connect supporting pages to proof. Connect proof to conversion. Connect conversion pages to clear lead handling. Keep the path readable. Internal linking should feel like editorial guidance, not a robotic SEO checklist. Finally, measure the cluster as a system. Track rankings, organic clicks, AI citations, AI mentions, prompt-family visibility, assisted conversions, demo quality, source mix, and sales reuse. Query fan-out turns visibility into a network problem, so marketers should stop evaluating every page as though it lives alone. ## Query fan-out makes content strategy more honest Query fan-out is useful because it reveals whether a company actually understands the topic it wants to own. A team can fake a page more easily than it can fake an architecture. One article can sound competent. A connected library of useful, specific, evidence-backed pages requires real market understanding. That is why query fan-out should make marketers less frantic, not more. The answer is not to publish endlessly or chase every AI acronym. The answer is to build clearer clusters around the questions that matter most to buyers. Create the page that defines the category. Create the supporting pieces that answer the surrounding questions. Add proof. Link the path. Keep the claims current. Measure the system honestly. A strong content architecture helps humans and machines do the same thing: understand what the company knows, where its proof lives, and why someone should trust it. In Google AI Search, that clarity matters because one question may become many searches before an answer appears. In marketing, it matters because one buyer question often becomes many internal conversations before a deal moves forward. --- # Recovering Leads That Fell Through the Cracks | Surface Labs URL: https://surface.thesurface.network/blog/recovering-leads-that-fell-through-the-cracks **The middle school version:** Picture a bucket with tiny holes in it. Water (your leads) slowly leaks out. Some people start filling out a form but quit halfway. Others visit your website a bunch but never sign up. Surface is like a net under the bucket — it catches those leaky leads and sends them friendly nudges to come back. Before we built lead recovery into Surface, we ran an audit. We wanted to know: how many leads are we losing to partial engagement? People who started but didn't finish. People who showed intent but never converted. The numbers were worse than we expected. Leak type Volume (monthly) What was happening **Form abandonment** ~340 partial submissions People entered their email (sometimes more) and then left before completing the form. The data evaporated. **Repeat visitors who never converted** ~1,200 identified visitors People who visited 3+ times, viewed pricing, read case studies — and never filled out a form. High intent, zero capture. **Email opens without clicks** ~800 nurture recipients People opening our emails consistently but never clicking through or engaging further. Stuck in a loop. **Meeting no-shows who went dark** ~40 per month People who booked a meeting, didn't show, and never rescheduled. They were interested enough to book — what happened? Combined, that's over 2,300 leads per month with demonstrated interest that our existing tools (HubSpot, Customer.io) weren't recovering. We tried building recovery workflows in HubSpot first. The problem: HubSpot can't capture partial form submissions. If someone types their email but doesn't hit submit, that data doesn't exist in HubSpot. It's gone. Customer.io was better for behavioral triggers — we could fire emails based on page visit patterns. But it couldn't connect those behavioral signals to our lead ops pipeline. A repeat visitor would get a nurture email, but there was no path from that email to a qualified, routed lead. The recovery happened in a silo, disconnected from our routing and scheduling infrastructure. The fundamental gap: these tools could send messages, but they couldn't close the loop — from recovery trigger to qualified lead to routed rep to booked meeting. They recovered attention but not pipeline. We built our recovery system directly into Surface. Each leak type gets a specific recovery sequence: **Form abandonment recovery.** Surface captures partial submissions — any field the visitor completed before leaving. If they entered an email (even without hitting submit), Surface saves it and triggers a recovery sequence within 5 minutes. The message is specific: "Looks like you didn't finish your request. Here's a link to pick up where you left off." Recovery rate: 22% of abandoned forms complete on the second attempt. **Repeat visitor triggers.** When an identified visitor (cookied from a previous interaction or matched via enrichment) returns to the site for a 3rd+ visit and views high-intent pages (pricing, case studies, product), Surface triggers a contextual capture experience — not a generic popup, but a form that references what they've been looking at. "We noticed you've been exploring our routing features. Want to see how it works for your team?" Conversion rate on triggered captures: 8% — vs. 2% on generic forms. **Stale nurture re-engagement.** For leads in email nurture who open consistently but never click, Surface detects the pattern after 3 opens with zero clicks and shifts the approach. Instead of another email, Surface triggers an on-site capture experience the next time they visit — a different format, a different offer, a different ask. This breaks the pattern that email alone couldn't break. **No-show recovery.** When a lead books a meeting and doesn't show, Surface triggers a recovery sequence within 30 minutes: a brief, human message from the assigned rep ("Missed you today — here's a link to rebook whenever works") plus a follow-up 2 days later if they don't rebook. Recovery rate: 35% of no-shows rebook within a week. Recovery type Monthly volume recovered Impact Form abandonment ~75 leads recovered 22% recovery rate. These are high-intent leads who already started the form. Repeat visitor capture ~96 leads captured 8% conversion on triggered experiences. Net new pipeline that didn't exist before. Stale nurture re-engagement ~45 leads reactivated Broke the open-but-never-click loop for 5.6% of stuck leads monthly. No-show rebooking ~14 meetings recovered 35% rebook rate. Each one is a conversation we would have lost entirely. Total: ~230 additional leads or meetings per month recovered from traffic and engagement we were already generating. No additional ad spend. No new campaigns. Just catching what was already leaking. We're building lead recovery as a native Surface feature because the existing tools treat recovery as a messaging problem (send more emails) when it's actually an infrastructure problem (capture the data, route it properly, and make the recovery flow as smooth as the primary flow). Recovery should work the same way primary capture works — qualification, routing, instant response, and scheduling. A recovered lead should get the same treatment as a fresh lead, not a second-class nurture email. **Stop losing leads. See how Surface recovers revenue you didn't know you were missing.** --- # Research Agent | Surface Labs URL: https://surface.thesurface.network/blog/research-agent Here's what a Tuesday afternoon used to look like for one of our early customers. 3:12pm. A demo is scheduled for 3:30. The AE pulls up the lead in HubSpot. Company name. Email. Not much else. They open a new tab. LinkedIn, check title, headcount, recent posts. Another tab, the company's website, About page, blog, jobs board. Crunchbase, funding, investors, when they raised. Another tab, their competitors. G2 for any product mentions. 18 minutes in, they've got a rough picture. 22 minutes later, they're on the call, half-prepared, going in with a script that doesn't actually fit. Multiply that by 20 calls a week. That's most of a working day. Per rep. Per week. * * * You point Surface at a lead. It goes and does what your AE would do, except it does it in seconds, at every lead, whether or not a meeting is booked. For every lead in your Lead Data Platform, Surface adds a new column: **Company Research**. Structured, current, deep. Recent funding, hiring signals, tech stack, competitor context, product mentions, buying triggers. It's the difference between walking into a demo with a script and walking in with intelligence. We didn't make that number up. It's what our early customers hit consistently, usually more. The savings come from three places: - **Pre-call prep** disappears. The rep opens Surface and it's done. - **Cold outbound** gets sharper. Reps can send a message that references something specific because Surface already surfaced it. - **Handoffs** stop losing context. When an SDR passes a lead to an AE, the research is already in the record. It's not a data enrichment tool. Clearbit and Apollo already do that. The Research Agent is doing what a _human_ would do with those data points, reading, synthesizing, deciding what matters for this specific lead in your specific ICP. It's not a chatbot. You don't ask it questions. It just fills in the column, and it's ready before your rep even opens the record. The Research Agent runs on top of the Lead Data Platform. Every lead that enters Surface, via form, ad landing page, enrichment sync, or CSV upload, passes through it. The output flows into scoring, into routing, into content agents, into your CRM. Because it's on the shared context layer, the research doesn't die inside one tool. It's available everywhere. * * * Give your reps their week back. [**Book a demo →**](https://withsurface.com/book-a-demo) --- # How to Route Leads by Company Size, ICP Fit, Territory, and Rep Capacity | Surface Labs URL: https://surface.thesurface.network/blog/route-leads **Ideal inbound lead routing logic combines four signals into one decision: company size, ICP fit, territory, and rep capacity.** The system checks who the lead is, matches them to the rep who covers that segment and has room on their calendar, and books the meeting immediately. A fallback rule catches anything that doesn't match a defined segment, so no lead sits unassigned. Round robin is the default for most teams. New lead comes in, next rep in line gets it. Fair. Simple. And completely wrong once your sales org has any kind of segmentation. A 500 person enterprise submits a demo request and gets assigned to your newest SDR because it was "their turn." A 10 person startup lands on your enterprise AE's calendar and gets a pitch designed for procurement committees. Both calls go badly. Both were preventable. The moment you have different reps for different segments, round robin stops working. You need to route based on who the lead actually is. Your enterprise reps talk differently than your SMB reps. They ask different questions, run different demos, quote different pricing. Putting the wrong lead in front of the wrong rep doesn't just waste time. It actively hurts the deal. A startup founder who gets an enterprise pitch feels like the product isn't built for them. An enterprise buyer who gets an SMB pitch doesn't feel taken seriously. The rep might be great. The match was just wrong. Company size is the most obvious routing signal. But ICP fit goes deeper: - **Industry** matters because a fintech company has different needs than a healthcare company - **Tech stack** matters because someone on HubSpot has a different onboarding path than someone on Salesforce - **Budget and use case** change who the best person to handle the lead is - **Seniority** determines whether this is a decision maker or someone doing research - **Territory** determines which rep owns the account and speaks the right timezone and language - **Rep capacity** determines whether the best-fit rep actually has room to take the meeting The better your routing matches leads to the right rep, the better the first conversation goes. And the first conversation is where most deals are won or lost. Signal What it determines Where the data comes from Company size Enterprise, mid-market, or SMB team Real-time enrichment, not a form dropdown Industry / vertical Which specialized rep or playbook applies Enrichment, firmographic data Territory Which regional rep owns the account Enrichment (location, domain) or CRM ownership Use case or product interest Which rep has the right technical depth Form field or intent signal Seniority Whether this is a decision maker or a researcher Enrichment (title, role) Rep capacity Whether the matched rep has open calendar room Calendar or CRM availability data They build it in their CRM. Usually HubSpot or Salesforce workflows with if/then branches. If company size is greater than 500, assign to enterprise team. If company size is less than 100, assign to SMB. If region is EMEA, assign to European rep. If industry is fintech, assign to the rep who knows fintech. This works until it doesn't. And it stops working faster than people expect. Three territories, four company size tiers, and two product lines means dozens of workflow branches. Every time a rep leaves, a territory changes, or you add a new segment, someone has to go into the workflow and manually update it. Most teams set it up once and then let it decay. Six months later, leads are going to reps who left the company two quarters ago. The other problem is data. CRM routing can only use the data that's in the CRM at the time the workflow fires. If the form only collected name, email, and company, the workflow doesn't know the company size. It doesn't know the industry. It's routing blind. Some teams add a "company size" dropdown to the form. That helps, but now you're asking the prospect to self report data you could've looked up automatically. And people lie on forms. Or they guess. A 200 person company picks "100 to 500" because it was the closest option. Your routing logic treats them the same as a 450 person company with completely different needs. The fix has two parts. Better data and earlier routing. Better data means enriching the lead in real time. The moment someone types their email, you pull their company data automatically. Employee count, industry, revenue, tech stack, location. Not from a dropdown they filled out. From actual data sources. Now your routing logic has accurate signals to work with. Earlier routing means making the routing decision inside the form, not after it. The prospect answers a few questions, the enrichment data fills in the rest, and routing conditions evaluate everything together. Company size plus industry plus seniority plus use case. The right rep's calendar shows up in the form. The prospect books. Done. This is what Surface does. You define routing rules using any combination of form fields and enrichment data. A lead that matches enterprise size plus EMEA plus security use case sees the senior SE in London. A lead that matches SMB plus North America sees the SMB rep in New York. The conditions stack as deep as your segmentation requires. No CRM workflow. No delay between submission and assignment. No self reported company size that might be wrong. CRM routing In form routing When routing happens After submission, inside a workflow During the form fill, before submission Data available Whatever the form collected Form data + real time enrichment Company size source Self reported dropdown Verified from enrichment data Time to assignment Minutes to hours Instant Prospect experience "Someone will be in touch" Books with the right rep on the spot Maintenance Manual workflow edits across branches Update rules in one place Edge cases Lead gets stuck or misrouted Default fallback catches everything A workable rule set usually starts with three tiers: - **SMB (roughly under 100 employees):** Route to the SMB team by default. Skip enterprise-only qualification steps. Prioritize speed to first meeting over deep discovery. - **Mid-market (roughly 100 to 1,000 employees):** Route by territory first, then by product or use case if you have specialized mid-market reps. This tier usually has the most segmentation because it's the widest band. - **Enterprise (roughly 1,000+ employees):** Route by named account ownership if the account already exists in the CRM. If it's a new account, route by territory and industry to the AE who covers that vertical. These thresholds are a starting point. Set yours based on your actual deal size and rep specialization, not a generic industry number. Two failure modes break routing systems that otherwise look correct on paper. **Unmatched leads.** A lead that doesn't cleanly fit a segment, wrong region, missing enrichment data, an industry you haven't mapped, still needs somewhere to go. Set a default fallback queue or a catch-all round robin so nothing sits unassigned while someone manually investigates. **Capacity collisions.** Even a well-matched rule fails if it always points to one rep who is already overbooked. Weight rules by current calendar load, or set a secondary rep for each segment, so the best-fit rep isn't the only option when the best-fit rep is at capacity for the day. 1. Pull your last month of booked meetings and tag each one by segment and outcome. 2. Define your company size tiers and confirm they match your actual rep structure, not an assumed one. 3. Identify which signals you can get from real-time enrichment versus what still requires a form field. 4. Write three to five rules that cover the majority of your inbound volume. Resist the urge to cover every edge case on day one. 5. Set a default fallback for unmatched leads and a secondary rep or queue for capacity collisions. 6. Test the rules against last month's leads before turning them on live, and confirm every segment resolves to an actual rep. Don't overcomplicate it on day one. Three to five rules that cover 80% of your leads are better than thirty rules that cover every edge case but nobody can maintain. Pull your last month of booked meetings. How many were with the right rep on the first try? How many got reassigned? How many were with a rep who didn't have the context for that type of buyer? If more than 10% of your leads need to be manually reassigned after routing, your rules are broken. Fix the data first, then fix the rules. Surface Labs handles routing as part of a single system with enrichment, scoring, and scheduling. If your CRM workflows are getting unwieldy or your reps keep getting leads that aren't their segment, [Surface's Route product](https://withsurface.com/route) is worth a look. If you're evaluating routing tools more broadly, see our [comparison of the best lead-routing software for 2026](https://withsurface.com/blog/best-lead-routing-software-2026). --- # Running Funnel Experiments Without Breaking Everything | Surface Labs URL: https://surface.thesurface.network/blog/running-funnel-experiments-without-breaking-everything **The middle school version:** You know how scientists run experiments to figure out what works? We do the same thing, but instead of test tubes, we use landing pages and sign-up forms. We try different "offers" — like a free trial vs. a demo vs. a guide — and Surface helps us see which one makes more people say "yes." It's like having a scoreboard for every experiment we run. Everyone says they A/B test. Almost nobody actually does it well — at least not beyond the landing page. Here's what "testing" looks like at most B2B companies: they change a headline on a landing page, run traffic for two weeks, and look at which version got more form submissions. That's not a funnel experiment. That's a page test. It tells you which headline got more clicks. It doesn't tell you which headline got more revenue. Real funnel experiments test the full journey — from first click to closed deal. They test different offers (demo vs. free trial vs. consultation vs. audit), different qualification paths (strict vs. lenient), different routing strategies (AE vs. SDR), and different response approaches (instant email vs. text vs. phone call). Most teams can't do this because the tools are fragmented. The landing page lives in one tool. The form lives in another. Routing lives in the CRM. Follow-up lives in a sales engagement platform. Measuring the impact of a change at the top of the funnel on conversion at the bottom requires stitching data across 4+ systems. Nobody does it because it's too hard. Surface owns the full journey — form through meeting — which means we can test variables at any stage and measure the impact all the way through. Here's what we tested last quarter: Experiment What we changed What we measured Result **Offer test** Demo request vs. "Get a custom audit" vs. "See pricing" Form-to-meeting rate "Custom audit" converted 40% higher than demo request. "See pricing" had highest form completions but lowest meeting rate. **Qualification depth** 3-question form vs. 6-question form Form completion rate AND lead-to-meeting rate 6-question form had 18% fewer completions but 2.3x higher lead-to-meeting rate. Net meetings: 35% more with the longer form. **Response type** Instant email vs. instant text message vs. no auto-response (rep calls manually) Speed-to-meeting-booked Instant text got 2x the meeting booking rate vs. email. Manual rep call was fastest when the rep responded within 5 minutes — but average rep response was 47 minutes, killing the advantage. **Routing strategy** Round-robin vs. territory-based vs. "best available" (first rep to respond gets the lead) Meeting show rate Territory-based had the highest show rate (78%) because reps had relevant context. "Best available" had fastest booking but lowest show rate (61%) — speed without relevance doesn't hold. Each experiment ran on a specific percentage of traffic. Surface split the traffic at the form level — 50/50 or 70/30 depending on the test — and tracked every lead through to the outcome. **The longer form won.** Every CRO in the world will tell you "shorter forms convert better." They do — at the form level. But form conversion rate is a vanity metric. The 6-question form gave us fewer submissions but dramatically more meetings, because the leads who completed it were pre-qualified and the reps had context. We would never have discovered this without measuring through to the meeting, not just to the submission. **Text messages crushed email for instant response.** We expected email to perform similarly to text. It didn't. Text felt personal and immediate. Email felt automated. The reply rate on instant text was 3x higher than email. This single insight changed our entire response strategy. **Speed without routing accuracy hurts.** The "first to respond" model sounded great — fastest rep wins. But leads ended up with reps who had no context on their territory, industry, or product interest. They booked fast but showed up to meetings where the rep was unprepared. Territory-based routing was "slower" by 2 minutes but produced better outcomes because the conversation matched. You don't need to test everything at once. Start with one variable: **The easiest experiment:** Test two different offers on the same page. "Request a demo" vs. "Get a free consultation" vs. "See how it works for your industry." Measure form-to-meeting rate, not just form submissions. Run for 2–4 weeks with at least 100 submissions per variant. If you can measure from form submit to booked meeting in one system (not stitching across platforms), you can run this experiment this month. **Start running funnel experiments in Surface — no engineering team required.** --- # Sales and Marketing Strategy: Why Content Needs an Internal Audience Too | Surface Labs URL: https://surface.thesurface.network/blog/sales-and-marketing-strategy-why-content-needs-an-internal ## Sales and Marketing Strategy: Why Content Needs an Internal Audience Too Marketing teams usually describe content in public terms — search rankings, AI citations, traffic, engagement. All of that can matter, and it becomes less persuasive the moment a sales leader asks a more immediate question: can anyone use this to help a buyer make a decision? That question is fair. A marketing strategy that only serves the external audience is incomplete. Salespeople need a clear way to explain the category, answer recurring objections, and follow up with something more useful than a deck full of feature screenshots — and good content can do that work without becoming a sales script, reinforcing both the buyer's understanding and the salesperson's confidence at the same time. ## Treat sales questions as content research Sales calls are one of the most underused sources of content strategy. Reps hear the phrases customers actually use, know where a buyer gets confused, and see which concerns show up once a deal gets serious. Create a monthly way to collect it: sales flags recurring questions and proof gaps, marketing sorts those into themes — early education, evaluation, implementation, risk. A strategist then decides which questions deserve a public guide, which need a sales one-pager, and which are really a sign that the product messaging is unclear. Our [content marketing guide](https://withsurface.com/blog/content-marketing-guide-2026) describes content operations as the connective tissue between search, owned media, sales enablement, and conversion, and sales feedback is part of that tissue — without it, a team can produce pages that sound smart and still miss the decisions buyers actually struggle to make. One company may need to explain the same product to a practitioner, a technical evaluator, and a finance leader. They share a problem, but not the same reason to care, so marketing should identify the common core and vary the supporting proof — a foundational guide for the category, a use-case page for the workflow, a technical page for implementation, a concise sales asset to help a rep route the right content to the right person. That doesn't require five nearly identical landing pages, just a system with enough range. Our [lead capture and routing guide](https://withsurface.com/blog/lead-capture-and-routing-for-b2b-saas-companies) makes a similar point operationally: the right lead needs the right context and the right route, and content should follow the same logic instead of sending every prospect the same article because it's the only thing marketing built. ## Content needs a path from education to action Sales gets frustrated with top-of-funnel content when it creates attention without a route toward a useful conversation. Marketing gets frustrated with sales when a rep ignores the content or reaches out with no sense of what the reader actually read. Both point to an incomplete path. Plan that path before publication — a definition page leading to a practical guide, a practical guide leading to a comparison or implementation page, a comparison leading to proof or a conversion page — and keep the links honest. An educational article shouldn't disguise every section as a pitch, and a product page shouldn't avoid the commercial question out of fear of sounding salesy. [Google's guidance on crawlable links](https://developers.google.com/search/docs/crawling-indexing/links-crawlable) focuses on clear link relationships, which happens to be good reader experience too. Marketing often collects proof in formats sales can't use — a customer quote buried in a slide, an implementation detail sitting in a private doc. By the time a rep asks for it, marketing has to recreate the evidence from scratch. Build a proof library with a few consistent components: the customer situation, the before and after, the evidence source, and the approved way to describe the result. Turn the strongest proof into public case studies when customers permit it, and keep a more detailed internal version where needed — a modest, specific example is more useful than a dramatic result with no context, and buyers can usually sense when a number's been cleaned up for the page. We built our content review workflow with this in mind: when product, sales, and marketing comments stay connected to the content system, a good objection response can become a better article instead of another lost thread. Sales and marketing alignment becomes abstract when teams only meet to debate lead quality. Put actual signals on the table instead — which content a lead read, whether the form got routed quickly with enough context, whether the sales conversation validated the content's premise or exposed a mismatch. Our [explanation of lead ops as its own category](https://withsurface.com/blog/why-lead-ops-is-becoming-its-own-category) makes the handoff problem concrete: capture, qualification, routing, and response all affect whether a lead gets a relevant conversation, and content can be diminished by a poor response path before anyone's had a chance to evaluate its value. Reporting should stay equally clear-eyed — our [guide to attribution and incrementality](https://withsurface.com/blog/attribution-is-not-incrementality-how-to-measure-ai-creative) argues for keeping observed evidence separate from inferred contribution, particularly as AI visibility complicates the buyer path. Marketing owns the public system — research, structure, distribution, measurement. Sales owns the live conversation and the practical test of whether the narrative holds up under pressure. Content needs an internal audience because buyers don't encounter a company through pages alone; they encounter the page, the form, the response, and the people who have to explain why the work matters. --- # Sales feedback: The missing input in content strategy | Surface Labs URL: https://surface.thesurface.network/blog/sales-feedback-content-strategy ## Sales feedback: The missing input in content strategy A content team spends six weeks researching a cluster, publishes the first three articles, and opens the planning meeting with traffic and keyword movement. Sales joins ten minutes late and asks for a page answering the same objection it has heard in seven recent calls. Nobody recorded the pattern early enough for it to shape the work. Sales feedback often enters content strategy as interruption: a Slack request, a forwarded email, a complaint about lead quality, or a one-pager needed by Friday. Treated that way, it becomes noise. Captured with context and compared against market evidence, it is one of the few inputs that shows how the company's public story behaves in a live buying conversation. Sales feedback is structured evidence from buyer conversations, opportunity movement, asset use, qualification, and won or lost outcomes that helps marketing decide what to explain, prove, revise, distribute, or stop publishing. It includes recurring questions, objections, misunderstood claims, segment fit, competitor comparisons, missing proof, and the materials buyers use to continue a decision internally. This feedback should not replace keyword research, customer research, product judgment, or performance data. Sales sees a selected part of the market, often late in the journey, and individual representatives can mistake a memorable call for a common problem. The goal is to give content strategy another evidence stream and preserve enough context to judge its weight. Surface's [intelligent attribution system](https://www.withsurface.com/intelligent-attribution) connects won, lost, and accepted outcomes to future qualification, routing, briefs, and campaigns. [Content Campaign Agents](https://www.withsurface.com/platform/content-campaigns) can also draw from closed-won calls, CRM opportunities, ICP accounts, and support evidence while keeping the resulting claims visible for human review. "Sales wants more case studies" is not yet a content insight. Which segment asked for proof? What claim needed support? Did the buyer need a public case study, a security reference, an implementation timeline, or an internal business case? How often did the question appear, and in deals with what outcome? Create a compact feedback record inside the systems sales already uses. A useful record includes the buyer segment, opportunity stage, question or objection in plain language, current asset used, whether that asset helped, competitor named, evidence requested, outcome, and the salesperson's confidence that the pattern is recurring. Keep access and privacy rules appropriate for call and customer data. Reason codes help with aggregation, but do not reduce every conversation to a dropdown. Preserve a short note or approved transcript excerpt so marketing can understand the buyer's language. The same label can hide different problems. "Pricing" might mean the buyer cannot afford the product, cannot explain the model to finance, or cannot compare the offer with a competitor's package. Without thresholds, the loudest request wins. Set a rule for when feedback becomes a content candidate. A pattern might qualify after it appears across several representatives, repeats in more than one segment, shows up in both calls and site behavior, affects late-stage opportunities, or matches an existing search and AI visibility gap. Use the evidence to choose the appropriate response: Sales pattern Likely content response Check before publishing Buyers misunderstand the category Category guide, product page revision, or clearer comparison language Does the confusion begin before the sales call? One objection repeats late in deals Evidence page, case study, implementation guide, or sales follow-up asset Can the claim be supported publicly and specifically? Sales repeatedly builds custom explanations Reusable article, one-pager, diagram, or demo sequence Which parts truly repeat, and which need account context? A segment converts poorly after reading a popular page Repositioned page, stronger qualification, or a different CTA Is the page attracting the wrong audience or making the wrong promise? Buyers name a competitor marketing does not track Comparison research, source analysis, or sales enablement update Is the competitor common enough to justify public content? Our guide to [content as an internal sales audience](https://www.withsurface.com/blog/sales-and-marketing-strategy-why-content-needs-an-internal) makes a related point: the library should help sales explain the category, answer objections, and share proof without forcing every representative to rebuild the story from memory. When a pattern passes the threshold, put it into the same planning system as search demand, product priorities, AI visibility gaps, and existing performance. The brief should state the buyer question, the evidence source, the intended audience, the current misconception, the page's strategic job, the claim Surface or another subject expert can defend, and the next action the reader should understand. That context protects the writer from a common failure: producing the requested asset while missing the problem underneath it. A salesperson asks for a comparison page because buyers keep naming a competitor. Research may reveal that the larger gap is a vague category explanation on the product page or a missing implementation guide. Treat the asset request as evidence that still needs diagnosis. [Surface's content workflow](https://www.withsurface.com/solutions/launch-campaigns-faster) starts with buyer evidence, turns an approved insight into connected assets, and requires human approval before publication. The same brief can support an article, landing page, nurture sequence, proof post, and champion one-pager without forcing each channel to invent a new message. Publishing is the midpoint. Tell sales what changed, where the asset lives, which question it answers, and which buyers should receive it. Then collect whether representatives used it, whether buyers opened or shared it when that data is available and permissioned, what questions followed, and whether the original objection changed. Marketing should also report what it chose not to build. A request may lack evidence, duplicate a better resource, target a segment outside the strategy, or demand a claim the company cannot support. Recording that decision prevents the same conversation from restarting every month. Connect the asset to behavior beyond sales anecdotes. [Traffic Intelligence](https://www.withsurface.com/platform/infrastructure/traffic-intelligence) can show content engagement, form movement, visitor quality, lead scores, and pipeline by channel. The CRM can show sales acceptance and opportunity outcomes. Neither system proves that one article caused a deal, but together they reveal whether the content is reaching and helping the people it was designed for. ## Protect content strategy from sales bias Sales feedback is valuable precisely because it is close to revenue, and that proximity can make teams overvalue it. Representatives speak mostly with people who entered the pipeline. They may not see buyers who left before a form, people excluded by qualification, researchers who influence a deal quietly, or future segments the company has not reached yet. Compare sales evidence with search behavior, product data, customer success, support questions, AI source patterns, and direct audience research. Separate a recurring objection from one large account's procurement requirement. Distinguish a message problem from a routing problem. Sometimes sales says content brought poor leads when the campaign targeting was broad, the form collected too little context, or the qualification definition changed without marketing knowing. The 2026 [Content Marketing Institute and MarketingProfs B2B research](https://contentmarketinginstitute.com/b2b-research/b2b-content-marketing-trends-research), based on 1,015 marketers, places customer understanding, sales alignment, content quality, and measurement among the factors effective teams frequently credited. No single feedback source can supply that combination. The [sales go-to-market guide](https://www.withsurface.com/blog/sales-go-to-market-strategy-why-lead-operations-deserves-a-seat) explains why targeting, conversion, qualification, routing, and response belong in the same plan. Sales feedback becomes trustworthy when the team can trace the path that produced the conversation. Content strategy improves when it listens without becoming obedient. Build a system that can hear sales, test the pattern, publish the right response, and learn what happened next. To see that loop using your own calls, campaign context, and CRM outcomes, [book a Surface demo](https://www.withsurface.com/book-a-demo). --- # Sales go-to-market strategy: Connect targeting to the handoff | Surface Labs URL: https://surface.thesurface.network/blog/sales-go-to-market-strategy-targeting-handoff Marketing has spent six weeks defining the account list. The campaign distinguishes fintech infrastructure companies from consumer finance brands, watches for relevant triggers, and speaks to a problem the revenue team recognizes. When a qualified buyer responds, the sales notification says, "New lead: Taylor, [taylor@example.com](mailto:taylor@example.com)," and everything the company learned before the conversion disappears at the moment it becomes useful. That gap begins in operations. A sales go-to-market strategy should specify how targeting context moves into the conversion, qualification, route, response, and opportunity. Otherwise a precise market strategy produces a generic buyer experience. In practice, a sales go-to-market strategy connects the chosen market to the way sales creates, receives, develops, and closes demand. It defines the target accounts and buying situations, the commercial message, the coverage model, the conversion and qualification rules, the handoff contract, and the revenue outcomes that should revise the next campaign. At the handoff, an account model becomes a human conversation. Sales needs enough context to understand why this person may care, while marketing needs structured outcomes to learn whether its targeting was useful. A shared record should carry the person, account, source, campaign, message, observed behavior, qualification basis, owner, and recommended next action. Surface treats that context as part of the marketing system. Its [GTM engineering workflow](https://www.withsurface.com/for/gtm-engineers) connects website activity, forms, enrichment, qualification, routing, CRM state, and downstream outcomes so the handoff can preserve the buyer's path. Most ideal customer profiles describe companies that could buy. A sales target model should identify accounts and situations worth pursuing now. Combine durable fit with change signals: company characteristics, relevant technology, team maturity, new leadership, expansion, compliance pressure, product behavior, current vendor, or an expressed problem. Write the model in language a person can review. Each rule should have a reason, a source, and a consequence. "High intent" is too vague to route an account. "Visited the migration page twice after a competitor contract renewal signal" gives sales something to interpret, provided the underlying signals are permitted, accurate, and current. This is where a go to market strategy for startups often breaks. Early teams use a broad market definition because they are still learning, then ask a small sales team to absorb the ambiguity. Keep exploratory segments visible, but distinguish them from the core motion. A rep should know whether an account matches the current thesis, tests a new thesis, or falls outside both. A go to market strategy for fintech needs explicit treatment of requirements that can change the sale: security review, regulated data, procurement, implementation dependencies, and legal approval. If those constraints affect fit or timing, include them in the target model and in the content that prepares buyers for the conversation. Used as an operating agreement, a handoff contract sets the minimum context, rules, and service expectations shared by marketing, revenue operations, and sales. It is more useful than a generic MQL definition because it says what sales receives and what marketing gets back. Handoff field What sales should receive What the system should learn later Person and account Verified identity, role, company, ownership, and account relationship Corrections, duplicate status, and account relevance Fit Included segment, matching attributes, exclusions, and confidence Accepted fit, disqualification reason, and edge cases Intent Observed action, recency, source, and relevant prior activity Whether the action predicted a real conversation Message Campaign, asset, offer, proof, and page that prompted response Which claim or evidence mattered in the call Route Owner, territory, queue, priority, and response expectation Acceptance, reassignment, delay, and capacity issue Next action Requested action and a useful response suggestion Meeting, nurture, recycle, opportunity, win, or loss Surface's [guide to lead routing](https://www.withsurface.com/blog/what-is-lead-routing) explains why assignment depends on fit, intent, ownership, capacity, and timing. The related [MQL versus SQL guide](https://www.withsurface.com/blog/mql-vs-sql) is useful when teams need to replace inherited labels with observable criteria and responsibilities. Long forms can force buyers to repeat information the company already knows, while short forms can starve the handoff. Contextual collection offers a better answer: ask only for information needed to fulfill the request, resolve identity, qualify the motion, or choose the next action. [Surface Dynamic Lead Forms](https://www.withsurface.com/platform/dynamic-lead-forms) can use known visitor and account context to adapt questions, preserve partial responses, and trigger the right workflow. If an account is already known, the form may ask about the current initiative rather than company size. If a visitor requests a technical review, the follow-up can preserve that request rather than forcing every response into the same demo path. Teams should keep human control over the conversion and route. Document which signals are collected, how they are used, how confidence affects decisions, and when a person can override the workflow. Sensitive or regulated attributes do not become fair qualification inputs merely because enrichment makes them available. From the target model, choose an appropriate coverage motion. A named enterprise account may need coordinated account research, executive outreach, technical proof, and patient opportunity development. A strong product-led signal may need a fast specialist response. An early researcher may need useful education with no immediate sales interruption. Define the response for each motion before campaigns launch. Include owner, channel, expected timing, context required, escalation path, and recycle condition. The existing Surface article on [why lead operations belongs in sales go-to-market strategy](https://www.withsurface.com/blog/sales-go-to-market-strategy-why-lead-operations-deserves-a-seat) covers the operational foundation in more depth. Based on a survey of 4,050 sales professionals across 22 countries, the 2026 [Salesforce State of Sales report](https://www.salesforce.com/news/stories/state-of-sales-report-announcement-2026/) emphasizes changing buyer expectations and AI-supported work. Automation should improve a seller's context and judgment. A faster alert with no explanation merely delivers confusion sooner. Require a small, stable outcome vocabulary: accepted, rejected with reason, contacted, meeting held, opportunity created, advanced, won, lost, recycled. Pair the status with evidence when possible. "Bad lead" teaches very little. "Existing customer owned by another team" can correct routing. "Right account, project deferred until budget cycle" can change timing and nurture. [Surface's intelligent attribution system](https://www.withsurface.com/intelligent-attribution) connects accepted, won, and lost outcomes to future qualification, routing, briefs, and campaigns. The CRM remains the commercial system of record. Surface acts on the context around it, with review and governance where the team needs control. Review patterns on a fixed cadence. Weekly, resolve broken routes and missing context. Monthly, examine acceptance, speed, meeting quality, opportunity creation, and segment differences. Quarterly, decide whether the market thesis, coverage model, or proof needs to change. One objection should not rewrite the ICP, while repeated revenue evidence should be allowed to challenge it. A sales go-to-market strategy earns its name when targeting survives the handoff and the handoff improves the next target. If your team can identify the right accounts but sales still receives context-poor alerts, [book a Surface demo](https://www.withsurface.com/book-a-demo) and bring one live route to map from signal through outcome. --- # Sales Go-to-Market Strategy: Why Lead Operations Deserves a Seat at the Table | Surface Labs URL: https://surface.thesurface.network/blog/sales-go-to-market-strategy-why-lead-operations-deserves-a-seat Sales go-to-market strategy usually begins with the big pieces: who the company sells to, how the product is positioned, which segments matter, and how pipeline targets will be met. The strategy often gets surprisingly thin at the moment a real buyer responds. Who receives the lead, and how quickly? What happens when the account is already a customer, or high-intent but low on form data? How does sales tell marketing a campaign is reaching the wrong audience? Those aren't administrative details — they're go-to-market execution, and lead operations deserves a seat at the table because it governs the moment strategy meets a person ready to talk. A company can have a sharp category narrative and still lose the buyer in the first response. A reader sees themselves in a problem the campaign describes, visits a landing page, shares enough information to request help, and gets a generic message three hours later asking what they'd like to discuss. The strategy broke at the handoff: a precise public promise met an imprecise private response. Sales go-to-market strategy should specify how the message continues after conversion — routing rules that recognize segment, product interest, use case, and existing account status, with the salesperson seeing the information that caused the prospect to respond in the first place. Our [guide to lead capture and routing for B2B SaaS](https://withsurface.com/blog/lead-capture-and-routing-for-b2b-saas-companies) gives a practical model here: form-based inbound and product-led signals can run through the same logic even though they need different triggers, and the system works when the response is quick, relevant, and assigned to someone who can actually help. GTM teams frequently define attractive segments in a strategy deck, then send every visitor to the same homepage and every form fill to the same queue — erasing the segmentation work before sales can use it. Bring the segment decisions into public content and conversion design instead. The aim isn't a separate website for every title, but a way for different high-value audiences to recognize their problem and see the relevant path — a content cluster helping people self-identify through the questions they research, a landing page making the intended audience clear, a form capturing product interest or use case. We describe the importance of connecting search visibility to conversion paths in our [content marketing guide](https://withsurface.com/blog/content-marketing-guide-2026): in GTM terms, the site shouldn't turn a carefully segmented market into an anonymous lead list at the first click. ## Content is part of sales coverage Sales coverage is usually described through territories and rep capacity, but content plays a quieter role: it helps buyers enter and move through the market before a rep ever meets them. A category guide helps someone name their problem. A comparison page helps them understand options. A case study makes an internal champion comfortable taking a meeting. Marketing should map these pages to the sales motion — what helps a buyer self-educate, what builds confidence before a first call, what a rep can send after a meeting to continue a specific thread. The output isn't a content calendar built around sales requests; it's a shared view of how information supports the motion. [Sales enablement content](https://withsurface.com/blog/what-is-sales-enablement-content-a-guide-for-content-marketing) becomes useful when it helps a buyer decide and a rep answer a real question, not when it just gives the company another PDF to attach. The first response after a form fill is a product experience — it tells the buyer how the company operates and whether the message on the site was more than marketing language. GTM teams should design it with the care they'd give a homepage or demo narrative: define response time by lead type, build a routing map with named owners and fallback rules, and make sure existing customers don't get treated like net-new prospects. Our Lead Intelligence and Inbound Capture tools are built around exactly this work: Dynamic Lead Forms, qualification, routing, recovery, nurture, and performance analytics in one system. Each stage can affect whether marketing's demand turns into a relevant conversation. Our [case for lead ops as its own category](https://withsurface.com/blog/why-lead-ops-is-becoming-its-own-category) makes the broader argument — capture, qualification, routing, and response sit between ad spend and the CRM, and treating them as incidental configuration work leaves too much revenue at the mercy of old rules and neglected inboxes. A go-to-market strategy needs a way to learn from live buyer behavior. Sales should be able to flag that a campaign is attracting the wrong use case or that an objection keeps showing up after a particular claim. Marketing should be able to see whether sales followed up and which assets actually helped. Set a regular review that looks beyond lead count — read the form answers, compare what a prospect read against what they asked on the call, and watch which content sales shares versus which questions it can't answer with the existing library. The reporting should stay honest about what it knows: a web visit is observed, a form fill is observed, but a claim that one blog created the opportunity is inferred or modeled at best. Our [attribution guide](https://withsurface.com/blog/attribution-is-not-incrementality-how-to-measure-ai-creative) recommends keeping those levels separate, since teams make better decisions when the dashboard admits what it doesn't know. Put lead operations in the GTM plan itself — document the conversion actions, qualification criteria, routing logic, response standards, and feedback rhythm, and revisit it when segments or sales capacity change. Buyers don't experience the strategy deck. They experience the article, the form, the follow-up, and the sales conversation, and a sales go-to-market strategy becomes real only when those moments act like they belong to the same company. --- # Sales and marketing strategy: One plan, one data layer | Surface Labs URL: https://surface.thesurface.network/blog/sales-marketing-strategy-one-data-layer Monday's alignment meeting goes well. Marketing shares the campaign, sales agrees with the target accounts, and revenue operations confirms the routing rules. By Thursday, the campaign platform, website, and CRM show three versions of the same account; sales cannot see which proof the buyer read, while marketing cannot tell whether the lead was rejected or merely reassigned. Intentions aligned in the meeting. The operating system did not. A sales and marketing strategy needs a shared market thesis and a shared representation of the buyer journey. One data layer does not mean one enormous application. It means the people, accounts, interactions, assets, campaigns, handoffs, opportunities, and outcomes remain connected well enough for both teams to act on the same reality. In practice, a sales and marketing strategy defines the market the company will pursue, the problem and offer it will lead with, how demand will be created and captured, how sales will continue the interaction, and how pipeline and revenue will improve future work. The plan becomes operable through shared definitions, linked data, clear ownership, governed workflows, and a common scorecard. Keep the CRM as the commercial system of record, the CMS as the publishing system, and the marketing automation platform as the messaging engine. The shared layer should resolve identity and relationships across them, preserve context, and return outcomes to the decisions that created the journey. [Surface is an intelligent marketing system built to learn from revenue](https://www.withsurface.com/what-is-surface). It sits across the existing stack, connecting Leads, company Context, specialized Agents, campaign work, inbound conversion, CRM state, and revenue feedback with human controls. Sales and marketing alignment is often reduced to lead definitions and service levels. Those controls come after a more consequential agreement: which market, buying situation, problem, offer, and evidence deserve coordinated investment. Write the thesis as a decision record both teams can challenge. Include the target and excluded segments, triggering conditions, buyer roles, costly status quo, current alternative, promised change, approved proof, commercial motion, and evidence that would cause a revision. Sales should see its account experience in the thesis. Marketing should be able to turn it into content, campaigns, and conversion paths. Surface's existing guide to [sales and marketing strategy for an internal audience](https://www.withsurface.com/blog/sales-and-marketing-strategy-why-content-needs-an-internal) explains why enablement should be treated as part of content strategy. A buyer-facing claim that sales cannot explain or support is an operating liability. A repeated sales objection that never reaches content leaves the next buyer to discover the same gap. Start by representing the business questions the plan needs to answer. Durable objects and explicit relationships are more useful than a collection of dashboard fields. Shared object Context it should preserve Decisions it supports Person Identity, role, consent, activity, requests, and account relationships Communication, qualification, follow-up, and experience Account Firmographics, ownership, segment, fit, technology, active initiatives, and history Targeting, territory, coverage, route, and investment Interaction Source, channel, timestamp, content, action, and confidence Journey analysis, intent interpretation, and response Asset Topic, audience, claim, evidence, format, owner, version, and publish state Content reuse, governance, performance, and decay Campaign Objective, market, message, offer, assets, channels, cost, and dates Coordination, measurement, and budget Handoff Qualification basis, route, owner, context, timing, acceptance, and rejection Operations, capacity, service levels, and repair Opportunity Stakeholders, product, stage, value, source context, objections, and movement Pipeline, forecast, proof, and sales learning Outcome Accepted, rejected, won, lost, retained, expanded, and reason Targeting, messaging, routing, product, and strategy One object may live primarily in one system. The requirement is that identifiers and definitions let the team connect it to the rest of the journey. Document which system owns each field, which workflows may update it, how conflicts resolve, and which changes require human approval. Four operating parts make a sales and marketing strategy plan useful. The market plan defines the thesis, account universe, buying situations, offers, and coverage. The campaign plan turns those choices into messages, evidence, assets, distribution, and conversion actions. The handoff plan defines qualification, routing, ownership, response, recycle, and feedback. The measurement plan establishes the journey states, cohorts, scorecard, evidence labels, and decision cadence. Connect every plan item to a shared object and an owner. If the company chooses a new segment, identify which account rules, campaigns, briefs, forms, routes, sales plays, and reports must change. If sales reports an objection, connect it to the relevant segment, opportunity, claim, asset, and content owner. This is how an insight becomes maintained context instead of meeting residue. Surface [Content Campaign Agents](https://www.withsurface.com/platform/content-campaigns) can use evidence from qualified leads, opportunities, ICP accounts, calls, search, and support to shape reviewed campaign work. [Dynamic Lead Forms](https://www.withsurface.com/platform/dynamic-lead-forms) can use known context to ask a more relevant next question and trigger the appropriate workflow. The two experiences become more useful when they share the same account and outcome definitions. Suppose marketing sees high engagement from regional fintech platforms and proposes a compliance-readiness campaign. Sales agrees that the accounts fit but says deals are stalling during security review. Revenue operations finds that the existing form routes technical review requests to the general inbound queue. In a connected plan, the team links the target segment to the campaign, adds approved security evidence to the core asset and sales play, changes the form path for review requests, routes them to the right specialist, and records whether the meeting advances the opportunity. If the segment engages but qualified opportunities still stall for the same reason, the product or implementation plan may need attention. Better copy cannot solve a missing capability. This sales alignment example works because the teams share the objects and outcome. Nobody needs to claim that one asset caused the sale. They can observe the journey, inspect the handoff, and decide whether evidence, operations, product, or targeting is the current constraint. Shared data can spread errors faster if ownership is vague. Establish field-level sources of truth, deduplication rules, retention and consent policies, access controls, confidence labels, audit history, and exception handling. Give a person authority to repair the model when automation encounters ambiguity. [Surface System Agents](https://www.withsurface.com/platform/system-agents) are designed to work with CRM environments such as HubSpot, Salesforce, and Zoho, keeping records cleaner and workflows current. Surface does not replace the CRM. Its [GTM engineering workflow](https://www.withsurface.com/for/gtm-engineers) connects data, forms, enrichment, qualification, routing, scheduling, and business outcomes around it. Based on 1,015 marketers, the 2026 Content Marketing Institute and MarketingProfs [B2B research](https://contentmarketinginstitute.com/b2b-research/b2b-content-marketing-trends-research) found that effective teams frequently credited customer understanding, sales alignment, measurement, content quality, and team capability. A shared data layer gives the teams a place to preserve and apply what they learn from those disciplines. Close the loop with a small, consistent outcome vocabulary and useful reasons. Accepted and rejected handoffs should improve qualification and routes. Opportunity movement should sharpen proof and sales plays. Wins and losses should challenge the market thesis, content priorities, offers, and channel investment. [Surface's intelligent attribution system](https://www.withsurface.com/intelligent-attribution) connects source, lead quality, sales acceptance, pipeline, won and lost outcomes, and future campaign decisions. People still judge whether a pattern is meaningful and approve consequential changes. The system makes the evidence available where the next action happens. One plan and one data layer will not remove functional expertise. Marketing still understands markets, messages, and demand. Sales still understands live buying situations and commercial progress. The shared layer lets those perspectives accumulate instead of resetting at every handoff. If your alignment meetings produce agreement but your systems keep reconstructing the buyer differently, [book a Surface demo](https://www.withsurface.com/book-a-demo) and map one market motion across the data and decisions both teams need. --- # SEO Automation Is Useful, but It Cannot Replace Content Strategy | Surface Labs URL: https://surface.thesurface.network/blog/seo-automation-content-strategy ## Content Hubs for SEO in Summary Content hubs for SEO organize related pages around a central topic so buyers, search engines, and AI systems can understand the relationship between ideas. A strong hub usually includes a pillar page, supporting articles, comparison pages, use-case content, proof assets, internal links, and a conversion path. Random publishing creates inventory. Content hubs create movement. That distinction matters for B2B SaaS and technical product companies because buyers rarely move from one question straight to a demo. They learn vocabulary, compare approaches, test objections, ask about implementation, look for proof, and then decide whether the company feels credible enough to involve sales. A content hub gives that journey a path. The strongest content teams do not just ask what they can publish next. They ask what path the buyer needs to walk, which page should answer each stage of that path, and how each piece of content should connect to the next useful decision. ## What Is a Content Hub? A content hub is a connected group of pages organized around a strategic topic. The center of the hub is usually a pillar page. That page explains the main concept, defines the category, introduces the company’s point of view, and links to deeper supporting pages. The supporting pages answer more specific questions. Some are educational. Some are comparative. Some are tactical. Some are technical. Some are closer to conversion. For example, a content strategy hub might include: - A main guide to content marketing strategy - A post about SEO automation and content debt - A post about content briefs - A post about AI and brand voice - A post about content hubs - A post about query fan-out and AI search - A post about AI visibility measurement - A post about content production cadence - A landing page or product page that explains how the company helps That is different from simply publishing nine separate blogs. The hub works because the pages are intentionally related. Each page has a job. Each page links to the next useful page. The whole system teaches search engines, AI systems, and buyers what the company understands. A random archive says, “We have written about this topic.” A content hub says, “We can guide you through this topic.” ## Content Hubs Create a Path, Not a Pile A content pile is a collection of pages that happen to live on the same website. A content hub is a connected system. The difference is visible in the reader experience. In a content pile, a buyer reads one article, hits a generic CTA, and leaves. The next article may answer a related question, but the site does not guide them there. The product page may explain the next step, but the blog does not connect to it. The sales team may have a useful proof point, but the reader never sees it. In a content hub, the reader can move naturally: - From definition to problem - From problem to approach - From approach to comparison - From comparison to implementation - From implementation to proof - From proof to conversion Search systems use those pathways too. Internal links help crawlers understand which pages matter and how topics relate. AI systems also benefit from clear content architecture because query fan-out turns one question into a network of related sub-questions. A brand with connected coverage has more opportunities to be understood, retrieved, cited, and trusted. Thinking about [query fan-out in Google AI Search](https://withsurface.com/blog/query-fan-out-in-google-ai-search-how-marketers-should-build-con) makes the hub model easier to understand. A single query can require the system to understand definitions, comparisons, use cases, objections, source credibility, and related entities. One isolated article is a weak answer to a networked question. Random publishing is seductive because it creates visible motion. The team can point to new URLs, new drafts, new keywords, and new reports. The site looks active. The calendar looks full. The problem is that random publishing often reflects the content team’s available ideas rather than the buyer’s path or the business priority. A technical product company might publish five excellent posts about architecture because the engineering team had strong opinions. That can be useful. But if the company’s biggest growth constraint is buyer confusion around use cases, the site may start to overrepresent technical architecture while underrepresenting the content that would actually help conversion. A B2B SaaS company might publish a dozen AI search posts because the topic is hot. Again, some of those pages may be useful. But if they do not connect to product pages, proof, lead capture, sales enablement, or a broader content operations system, the team may win attention without building trust. Thinking about [AI citations vs. SEO rankings](https://withsurface.com/blog/ai-citations-vs-seo-rankings) helps clarify the risk. Visibility is no longer one clean leaderboard. A brand may rank, be cited, be summarized, be mentioned, or disappear depending on the surface. Content hubs help because they create a clearer source ecosystem around the topic rather than asking one page to carry the entire visibility burden. ## Content Hubs Work Because Buyer Intent Changes The best content hubs are built around intent movement. Not every reader is ready for the same page. Some readers are trying to understand a category. Some are comparing approaches. Some are looking for a vendor. Some are trying to convince an internal stakeholder. Some are already in a sales process and need proof. A content hub should give each reader the right next step. For a content strategy hub, the path might look like this: ### Educational Intent The reader asks broad questions: - What is content strategy? - How many blogs should we publish? - How should AI fit into content? - What is a content brief? - What is a content hub? These pages should explain concepts clearly and introduce the company’s point of view. ### Comparative Intent The reader starts comparing options: - Should we use AI tools or hire more writers? - Should we focus on SEO, AI visibility, or conversion content? - Should we build content hubs or publish standalone blogs? - Should content strategy be handled internally or with an operations partner? These pages need nuance, tradeoffs, examples, and proof. ### Transactional Intent The reader has a problem and wants a solution: - Who can help us build a content operation? - How do we turn traffic into qualified demos? - How do we connect content to capture, qualification, routing, recovery, and nurture? These pages should connect content strategy to business outcomes and give the reader a clear conversion path. A hub succeeds when these layers connect. It fails when each page behaves as if it is the only page on the site. ## A Content Strategy Hub Example A content strategy hub should not be a giant page that tries to rank for everything. It should be a system of connected pages with different jobs. Here is a practical hub structure for the topic `content strategy`. ### Pillar Page A pillar page should explain the overall model. Example internal target: - [Content Marketing Guide for 2026](https://withsurface.com/blog/content-marketing-guide-2026) Job of the pillar: - Define the modern content operating model - Explain visibility, trust, conversion, distribution, and measurement - Establish the broader point of view - Link to supporting pages - Give readers a clear next step A pillar page should not be a dumping ground. It should be the cleanest, most useful orientation point for the topic. ### Supporting Educational Posts These posts answer core questions. Possible pages: - SEO Automation Is Useful, but It Cannot Replace Content Strategy - What Is a Content Brief, and Why the Best Briefs Still Need Human Judgment? - How to Use AI in Your Content Strategy Without Losing Brand Voice - Content Production: How Many Blogs Should You Publish Each Week? Existing internal target: - [content production cadence](https://withsurface.com/blog/content-production-how-many-blogs-should-you-publish-each-week) Job of these posts: - Answer specific questions - Capture informational demand - Introduce Surface POV - Link back to the pillar - Link laterally to related posts These pieces should stand on their own, but they should not float alone. A reader should be able to enter through any supporting article and still find the broader content strategy path. ### AI Visibility and Search Evolution Posts These posts explain the changing discovery environment. Existing internal targets: - [generative AI search optimization](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) - [generative engine optimization services](https://withsurface.com/blog/generative-engine-optimization-services) - [AI visibility measurement](https://withsurface.com/blog/ai-visibility-measurement-is-messy-how-to-report-geo-without-fak) - [query fan-out in Google AI Search](https://withsurface.com/blog/query-fan-out-in-google-ai-search-how-marketers-should-build-con) Job of these posts: - Explain why classic SEO is no longer the only visibility system - Show how AI search changes content architecture - Help content managers report without fake precision - Connect AI visibility back to content strategy The mistake many teams make is treating AI visibility as a separate project from content strategy. It is not separate. AI visibility depends on coverage, clarity, evidence, freshness, structure, and trusted source relationships. Those are content strategy questions. ### Operations and Conversion Posts These pages connect content to GTM execution. Existing internal targets: - [marketing operations strategy](https://withsurface.com/blog/marketing-operations-strategy-content-system) - [post-click paths that turn traffic into demos](https://withsurface.com/product) Job of these pages: - Show that content does not end at publication - Explain how traffic moves into capture, qualification, routing, recovery, and nurture - Create a bridge from education to commercial action A content hub without a conversion bridge is an educational library. That may be useful, but it is not enough for most B2B teams. The hub should help the reader understand the topic and understand the next operational step. ### Proof and Customer Context A content hub should include proof. That proof may come from customer stories, product examples, case studies, benchmark pages, original research, visual reports, or operational results. Job of proof assets: - Reduce perceived risk - Give sales useful follow-up material - Show that the content strategy connects to business outcomes - Help readers believe the operating model is not theoretical Proof does not always need to be a massive case study. It can be a specific example, a teardown, a before-and-after structure, a data point, a customer quote, or a small operational model. The important thing is that the hub should not rely only on explanation. Internal links are often treated as SEO housekeeping. That is too small a frame. Internal links are audience design. A good internal link should feel like the reader’s next thought. If someone is reading about content hubs, a link to query fan-out makes sense because it explains why isolated pages are weaker in AI-mediated discovery. A link to content production cadence makes sense because hubs still need publishing rhythm. A link to marketing operations strategy makes sense because the hub has to connect to a system that can capture and convert interest. Bad internal links feel like keyword insertion. Good internal links feel like guidance. Search systems use links to understand structure. Buyers use links to decide whether the company understands the problem deeply enough to keep helping. Sales teams use links to answer recurring questions. A strong content hub serves all three audiences at the same time. ## Content Hubs for SEO and AI Visibility Content hubs also help AI visibility because AI systems often retrieve from multiple sources, compare claims, and synthesize answers. A single page can be useful, but a cluster gives the system more evidence that the company understands the topic. A content hub improves AI visibility when it includes: - Clear definitions - Specific subtopic coverage - Fresh examples - Source-backed claims - Comparison logic - Use-case explanations - Proof assets - Internal links - Consistent product and category language - Pages that answer questions at different intent levels That does not mean teams should create dozens of thin fan-out pages. The goal is not to publish a page for every possible prompt variation. The goal is to cover the real question map with enough depth that both humans and systems can understand the company’s expertise. A hub should make the company easier to cite because the company becomes easier to understand. ## How to Build a Content Hub Without Overbuilding It Start with one core business topic. For this example, use `content strategy`. Then map the hub in plain language. ### Define the Core Belief Start with the argument that should govern the hub. Example: `Content strategy should create a connected path from visibility to trust to conversion, not a random queue of publishable assets.` That belief gives the hub coherence. Without it, the hub becomes a keyword cluster with no editorial center. ### Choose the Pillar Create or identify the main page that explains the full model. The pillar should be broad enough to orient the reader but not so broad that it becomes vague. It should define the topic, explain the stakes, show the model, and link outward to supporting pieces. ### Map Supporting Questions Choose six to ten supporting questions buyers actually ask. For content strategy, those might include: - How should B2B teams use AI in content? - What is a content brief? - How many blogs should we publish? - Do content hubs still work for SEO? - How should teams measure AI visibility? - How does content connect to lead conversion? - What should be refreshed each quarter? - When does automation create content debt? The goal is not to exhaust every possible keyword. The goal is to cover the questions that help the buyer build confidence. ### Assign Intent to Each Page Every supporting page should have a job. Some pages educate. Some compare. Some persuade. Some enable sales. Some support technical validation. Some should point toward conversion. Some should primarily strengthen the hub’s topical clarity. If every page has the same CTA and the same structure, the hub is not respecting intent. ### Create the Internal Link Plan Decide how each page links upward to the pillar, sideways to related posts, and downward toward conversion or proof. A simple pattern works: - Supporting posts link to the pillar. - The pillar links to supporting posts. - Related supporting posts link to each other. - Mid-funnel posts link to proof or conversion pages. - Conversion pages link back to educational resources when the buyer needs more context. Internal links should be planned before publication, not patched in six months later. ### Build the Conversion Bridge Create a useful commercial next step. A reader should not move from a thoughtful content strategy article into a generic contact form with no context. The next step should explain how the company helps with the problem the reader just spent time understanding. For Surface, that bridge might be a content operations page that connects strategy, publishing, internal links, conversion paths, measurement, refreshes, and AI visibility into one operating system. ### Set the Refresh Rhythm Review the hub quarterly. Update: - Internal links - Statistics - Examples - Product references - Screenshots - CTAs - AI visibility references - Search intent shifts - Related posts - Outdated claims - Missing proof Content hubs are not one-time architecture projects. They are living systems. Content hubs should be measured as systems, not only as individual URLs. Track: - Rankings for hub-level and page-level queries - Organic traffic by intent layer - Internal clicks from supporting pages to pillar and conversion pages - Engagement quality on hub pages - Assisted conversions - Demo requests from hub paths - Sales usage of hub content - AI citations and brand mentions where relevant - Pages with declining freshness - Orphaned or underlinked pages - Content gaps discovered through sales calls or prompt testing The goal is not to build a dashboard for its own sake. The goal is to understand whether the hub helps buyers move from curiosity to confidence. If a hub earns traffic but no one clicks deeper, the path may be weak. If people read several pages but never reach a conversion point, the bridge may be missing. If sales never uses the content, the proof may be too abstract. If AI systems mention competitors but not the company, the hub may lack citation-worthy coverage, freshness, or authority. Measurement should show where the system is helping and where the system is leaking. ## Common Content Hub Mistakes ### Building the Hub Around Keywords Instead of Buyer Questions Keyword research matters, but a hub should not be a spreadsheet made visible. Start with how buyers think. Then map keywords to that path. ### Publishing Supporting Posts Without a Pillar Supporting posts can rank individually, but without a strong pillar they often fail to teach the site’s structure. The pillar gives the cluster a center. ### Linking Only Upward Many teams link supporting posts to the pillar and stop. Hubs also need lateral links between related posts and downward links toward proof or conversion pages. ### Treating Every Page as Informational Some pages should teach. Others should compare, qualify, persuade, or support sales. If every page sounds like a beginner guide, the hub will not serve the full buying process. ### Forgetting the Conversion Page A hub that never connects to a conversion page may generate attention without producing movement. For B2B teams, the path should eventually give the reader a practical next step. ### Letting the Hub Go Stale A hub can decay. Links break. claims age. Examples lose relevance. Product positioning changes. AI and search behavior shifts. Refreshing the hub is part of the strategy. Choose one topic that matters to revenue. Do not start with twenty. For that topic, build a simple map: - One pillar page - Six to ten supporting pages - One proof asset - One conversion page - One quarterly refresh process - One measurement view Then audit existing content before creating anything new. Many teams already have half a hub sitting in their archive. The problem is not always missing content. Sometimes the problem is missing connection. A practical first pass might look like this: 1. Export every blog related to the topic. 2. Group the posts by intent. 3. Identify the strongest pillar candidate. 4. Identify pages that should be merged, refreshed, redirected, or linked. 5. Add internal links that reflect the reader’s next thought. 6. Create one missing conversion bridge. 7. Add the hub to the quarterly refresh calendar. Surface’s content operations perspective is built around that kind of connection. A content program should help teams decide what to publish, how to structure it, how to link it, how to keep it fresh, and how to turn qualified attention into movement through the GTM system. ## Final Thought on Content Hubs for SEO Content hubs for SEO work because they respect how people actually learn. A buyer does not become confident because one article used the right keyword. A buyer becomes confident because the company keeps answering the next question with clarity, proof, and a visible understanding of the problem. Search systems and AI systems reward parts of that same architecture because connected content is easier to crawl, classify, retrieve, and cite. Random publishing fills the site. Content hubs teach the market how to walk through it. --- # SEO Friendly CMS: What Content Teams Need Before They Start Publishing | Surface Labs URL: https://surface.thesurface.network/blog/seo-friendly-cms-what-content-teams-need-before-they-start ## SEO Friendly CMS: What Content Teams Need Before They Start Publishing Most teams evaluate an SEO-friendly CMS at the moment they're about to change a title tag. That's late, and a little backwards — by then the article has already been written, reviewed in three places, pasted across systems, and possibly stripped of the information that would make it useful to a reader, a crawler, or a sales team. An SEO-friendly CMS isn't a blog editor with a meta description field. It's the publishing layer that preserves the decisions a content team made upstream: why a page exists, what evidence it needs, where it belongs in the site, and what should happen after someone reads it. If that layer loses the thread, the team ends up publishing technically acceptable pages that do very little for the business — and the problem has only gotten more obvious as search has gotten messier, since a page may now be read by Google, an AI answer engine, a buyer, and a sales rep all trying to get slightly different things from it. Before comparing platforms, write down the information that must travel with a piece of content from brief to publication. Most teams need more than headline, body, and hero image — a primary query, audience and intent, source links, a freshness date, internal-link targets, and a record of which product or strategic theme the page supports. That doesn't mean every writer fills out sixteen mandatory fields before drafting a 600-word answer. It means the system has a place for context that otherwise lives in a Slack message or a spreadsheet no one opens after launch, so a team can distinguish a broad educational page from a comparison page or a conversion page because someone actually labeled those jobs. [Google's SEO Starter Guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide) still gives the right baseline here: help search engines understand the content and help people find useful information. A CMS supports that when it keeps page purpose visible instead of hiding it behind a generic publishing form. Technical SEO gets discussed as though it belongs to engineers while page structure belongs to marketers, but the handoff is rarely that tidy. A writer needs to know whether the important copy renders in HTML. An editor needs to know if a page got accidentally marked noindex. A marketer needs a reliable canonical URL before distributing a piece. An SEO-friendly CMS should make a few fundamentals routine: stable, readable URLs with editor control over slugs; one clear H1 and useful heading structure without turning titles into keyword-stuffing fields; real HTML links crawlers can follow, with anchor text that tells people what they'll find, per [Google's link guidance](https://developers.google.com/search/docs/crawling-indexing/links-crawlable); and a way to manage indexability, canonicals, and structured data with technical review where it matters. None of that is glamorous, and it's also where plenty of CMS migrations get expensive — a platform can have a beautiful composer and still produce pages that are hard to update once the site gets larger. Internal linking often gets assigned to the final ten minutes before publication: two vague "learn more" links, a tired editor, and the page joins the archive as another isolated object. A better workflow lets teams build links from the actual information architecture — a category article pointing to the relevant product page, a glossary entry pointing toward a guide with more context, a high-intent article with a clear path to proof. We've written about this as the need for a reader to walk through a content system rather than stumble from one orphaned blog to another; [our content marketing guide](https://withsurface.com/blog/content-marketing-guide-2026) describes those paths across SEO, AI visibility, and conversion, and the CMS is where that plan either survives or gets lost. Automation can suggest links and save time on a large site, but it shouldn't decide the relationship — a semantically close suggestion can still send a reader the wrong way, so someone still needs to make the final editorial call. An SEO-friendly CMS in 2026 has to support pages that are citable as well as findable, and that doesn't require AI-only pages or a pile of machine-facing copy. [Google's guidance on AI features](https://developers.google.com/search/docs/appearance/ai-features) says its generative search features rely on the same core SEO foundations — useful, crawlable, well-structured content still matters most. The practical difference is that teams have less room for vague, unattributed claims. A page that might get summarized needs a direct answer near the top, visible sources, and enough specificity that a reader understands the claim's limits. Our [guide to generative AI search optimization](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) makes a useful distinction: content needs to earn enough trust to be cited, not just fill a publishing slot. A strong CMS doesn't create that credibility by itself — it just stops the publishing process from destroying it. The last requirement is where "CMS" becomes too narrow a word. Content teams need to know what happened after a page went live — did it earn impressions, move people to a product page, assist a form fill, or fade after the source data went stale? Those questions don't demand perfect attribution, since content rarely behaves that cleanly, but they do demand a shared view of publishing, engagement, and lead activity. Our [work on attribution and incrementality](https://withsurface.com/blog/attribution-is-not-incrementality-how-to-measure-ai-creative) argues for cleaner evidence labels instead of pretending every touchpoint can be assigned a precise fraction of revenue, and Surface CMS is built around that same larger workflow — a direct-to-publish path from review, sitting beside strategy, content review, and content analytics, so the decision to publish stays connected to the reason for publishing. Choose a CMS by asking a more useful question than "does it support SEO?" Ask whether it helps the team create, review, publish, connect, and learn from content without dropping the context at every handoff. --- # Shipping Code 24/7 With a Distributed Team | Surface Labs URL: https://surface.thesurface.network/blog/shipping-code-24-7-with-a-distributed-team Our codebase never sleeps. Someone on the team is always shipping. This isn't a flex about hustle culture. Nobody at Surface Labs is pulling all-nighters or working weekends because they feel pressured to. We're distributed across time zones — and by design, that means when our US-based engineers log off for dinner, our team members in other time zones are picking up where they left off. The result: while other startups wait for Monday morning standup, we've already shipped three times. The key word is "async." Not "always on." The difference matters. We don't have synchronous standups. We have async updates — every engineer posts what they shipped yesterday, what they're working on today, and what's blocking them. This happens in a shared channel, at whatever time their workday starts. Nobody needs to be online at the same time for the team to have full context. PRs don't wait for a specific person to be online. We've structured code ownership so that at least two people in different time zones can review any given PR. When an engineer in timezone A opens a PR at end of day, an engineer in timezone B reviews it at start of their day. The PR merges before engineer A wakes up. No Slack pings. No "hey, can you review this?" blocking messages. Deploys happen continuously. We ship to production multiple times per day — not because we're moving recklessly, but because our CI/CD pipeline, test coverage, and feature flag system make it safe to deploy whenever a change is ready. A deploy doesn't need a ceremony. It needs passing tests. **Written context, always.** Every PR has a description that explains the "why," not just the "what." Every design decision is documented in a brief doc before implementation starts. This isn't bureaucracy — it's the only way async works. If someone picks up your work 8 hours later, they need to understand your thinking without scheduling a call. **Clear ownership.** Every project has an owner. Not a "team." Not a "pod." A person. That person makes decisions, breaks ties, and is accountable for delivery. When ownership is clear, async coordination is easy. When ownership is ambiguous, everything requires a meeting. **Weekly sync — the one meeting that exists.** We have one synchronous team meeting per week. 30 minutes. Focused on decisions that require real-time discussion — architectural trade-offs, priority changes, cross-team dependencies. Everything else is async. **Trust over surveillance.** We don't track hours. We don't monitor screens. We track output — what shipped, what's working, what's not. If the deploys are happening and the metrics are moving, the process is working. If they're not, we fix the process, not the people. Speed compounds. A team that ships Monday, Tuesday, and Wednesday while another team is still in sprint planning has a structural advantage that grows every week. Our distributed setup means we're effectively running a 16–18 hour development cycle without anyone working more than 8 hours. Features get built, reviewed, deployed, and iterated on faster than they would with a co-located team operating on a single timezone's schedule. This isn't theoretical. We've shipped features that went from design to production in 48 hours — across three time zones, with three engineers who never had a real-time conversation about it. Written context did all the work. It wasn't smooth from day one. Early on, we had too many synchronous meetings (a habit from co-located culture). We had PRs that sat for 12+ hours because only one person could review them. We had context that lived in people's heads instead of in docs. We fixed each of these one at a time. Dropped meetings. Expanded review permissions. Made documentation a non-negotiable part of every PR and design process. The lesson: distributed teams don't fail because of time zones. They fail because of poor information architecture. Fix how information flows and the time zones become an advantage, not a limitation. How does your team handle async work? What tools do you swear by? --- # Slow Follow-Up Is Killing Your Sales | Surface Labs URL: https://surface.thesurface.network/blog/slow-followup Your marketing team spent thousands getting someone to fill out that form. The prospect is interested right now. They've got three tabs open comparing vendors. They just came out of an internal meeting where someone said "we need to fix this." Then your team takes 42 hours to respond. That's the average. Not the worst case — the average. By the time your rep sends a "thanks for reaching out" email, the prospect has already booked with someone else. Leads contacted within 5 minutes are 21x more likely to convert than leads contacted after 30 minutes. After an hour, the odds drop off a cliff. Harvard Business Review published this years ago. Drift confirmed it across 2,500+ B2B companies. The numbers haven't changed because the underlying behavior hasn't changed — when someone wants to buy, they want to talk now. Not tomorrow. Five minutes is the window. Most teams aren't even close. Reps aren't sitting around ignoring leads. The system between "form submitted" and "rep sees it" is what's slow. Step Time added Where it breaks Form to CRM sync 1–3 minutes Sync delays, missing fields Routing workflow fires 2–10 minutes Complex branches, wrong assignment Rep gets notified 5 min to 4 hours Email buried, rep in meetings Rep researches the lead 10–15 minutes No enrichment data, manual lookup Rep drafts outreach 5–10 minutes Generic template, no context **Total** **30 min to 48 hours** **Prospect gone after 5 min** Every step between form fill and first contact is time you're giving your competitor. ## The math nobody does 500 leads a month at $50 each. $25,000 in acquisition cost. At 10% conversion, that's 50 meetings. Cost per meeting: $500. Cut response time from hours to minutes. Research says that alone can 2–3x your conversion rate. Even conservatively — 10% to 20% — that's 100 meetings instead of 50. Same leads. Same spend. At a $20K average deal size and 20% close rate, those 50 extra meetings are worth $200K in pipeline per month. $2.4M per year. From leads you already paid for. Start with the highest-leverage fix. **Move scheduling into the form.** Let prospects book a meeting before they leave the page. If the right calendar shows up based on their responses, response time becomes zero. **Enrich leads in real time.** Reps spend 10–15 minutes researching every lead. Real-time enrichment appends company data the moment someone enters their email. That research step disappears. **Score leads automatically.** Not every lead needs a five-minute response. But the ones that match your ICP do. Automatic scoring means reps know which leads to call first. Most teams don't actually know their number. They track time-to-assignment, which only measures when the CRM assigns the lead — not when the rep actually does something about it. The real number, form fill to first human contact, is almost always worse than people think. Response time Conversion impact Under 5 minutes 21x more likely to qualify the lead 5–30 minutes Still strong, drops with each minute 30–60 minutes Significantly lower probability 1–4 hours Most of the opportunity is gone 24+ hours Barely better than not responding 42 hours (industry avg) Where most B2B teams sit Measure the real number. Not time-to-assignment — time from form fill to meeting booked. If you don't know it, that's the first problem. Surface Labs collapses the entire chain into one step — enrichment, scoring, routing, and scheduling happen inside the form before the prospect leaves the page. If your current setup has more than two steps between form fill and meeting booked, it might be worth a look. [Book a demo →](https://www.withsurface.com/) --- # Intelligent Spam Lead Filtering | Surface Labs URL: https://surface.thesurface.network/blog/spam-email _Surface now filters spam submissions automatically before they reach your CRM or trigger any workflows._ Anyone who's run inbound forms for more than a few months knows the pattern. You check your CRM in the morning and find a handful of submissions from the previous day that are clearly junk — `asdfasdf@mailinator.com`, someone who submitted the same form six times in a row, a "company name" field that just says "test." The issue isn't just that junk submissions exist. It's what happens downstream. They get routed to reps, trigger nurture sequences, inflate your lead counts, and take up paid seats in your CRM. Most teams deal with this reactively — manually deleting bad records, building Zapier filters, or asking SDRs to eyeball every submission. None of that scales, and all of it happens after the junk has already entered your system. We kept hearing this from Surface customers, so we built spam filtering directly into the submission pipeline. The core idea is straightforward: validate every submission at the moment it happens, before it gets written to your CRM or triggers any downstream workflows. Here's what runs on each submission: **Email validation.** Surface checks every email as it's entered — verifying the domain exists, the format is valid, and it's not from a disposable provider like Mailinator or TempMail. Invalid emails are blocked instantly and the prospect is prompted for a work email. **Pattern detection.** If the same email submits 10 forms in a minute, or we see a burst of identical entries from the same IP, it gets blocked or flagged automatically. **Content screening.** Obvious test data in form fields — "test test test", "asdf", single-character entries — gets flagged for review rather than passed to your sales team. **Quarantine, not deletion.** Nothing is permanently thrown away. Blocked submissions go to a quarantine view where you can review them and recover false positives. Type Example Handling Disposable email domains `user@mailinator.com`, `name@tempmail.org` Blocked; prospect prompted for work email Non-existent domains `name@fakecorp.xyz` Blocked at submission Rapid repeated submissions Same email, 10 submissions in 1 minute Auto-blocked Test/junk field data "test test test", "asdf", "xxx" Flagged for review Bot patterns Auto-generated strings, keyword stuffing Quarantined Sequential test entries `test1@co.com`, `test2@co.com`, `test3@co.com` Flagged as suspicious Spam filtering runs as the first step in Surface's submission pipeline, before lead scoring, enrichment, or routing. The sequence looks like this: 1. Prospect submits a form 2. **Spam filter validates the submission** — blocks, flags, or passes it 3. Clean submissions proceed to enrichment (company data, firmographics, etc.) 4. Lead scoring evaluates fit and intent 5. Routing assigns the lead to the right rep or workflow This ordering matters. If spam gets through to step 3, you're burning enrichment credits on junk data. If it reaches step 5, a rep wastes time on it. Filtering at step 2 means everything downstream operates on clean data. For existing Surface customers, this doesn't require rebuilding your workflows. Spam filtering slots in automatically — just enable it and optionally configure your domain allowlists/blocklists. Out of the box, spam filtering works without any setup. The default settings block disposable email providers and flag obvious test data. If you want to customize: **Domain lists.** Allowlist specific domains (useful if you have partners on unusual domains that might get flagged) or blocklist domains you know are problematic. **Free email handling.** By default, Surface allows submissions from Gmail, Yahoo, Outlook, etc. If you're strictly B2B and only want work emails, you can toggle this to flag or block free email providers. **Does this add latency to the form experience?** No. Validation runs in milliseconds. From the prospect's perspective, the form behaves normally unless their email gets flagged, in which case they see an inline message asking for a work email. **What if a real lead gets blocked?** Blocked submissions appear in the quarantine view. You can recover any submission with one click and it'll flow through to your CRM as if it had passed normally. Over time you can tune your allowlists to reduce false positives. **Is this on by default for new accounts?** Yes. New Surface accounts have spam filtering enabled with default settings. You can disable it or customize it from the settings panel. **Can I see what's being filtered?** Yes. The quarantine view shows every blocked and flagged submission, with the reason it was caught. You can also see aggregate stats — how many submissions were filtered over a given period, what the most common spam patterns are, etc. --- # Surface Labs Is Not a CRM. Here's Why That Matters. URL: https://surface.thesurface.network/blog/surface-labs-is-not-a-crm-here-s-why-that-matters We get this question a lot. "So is Surface like HubSpot? Is it a CRM?" No. And the distinction matters more than you'd think. A CRM is a system of record. It stores contacts, tracks deals, logs activities. HubSpot and Salesforce are great at this. Surface is the layer that sits between your form and your CRM. It makes sure the lead that arrives in your CRM is enriched, qualified, scored, routed to the right rep, and already has a meeting booked. Your CRM manages the relationship. Surface creates the relationship. A prospect fills out your form. Eventually they show up in your CRM. But what happened in between? Step What usually happens What should happen Data collection Form grabs name and email. That's it. Enrichment appends company size, industry, revenue, tech stack in real time. Qualification Lead enters the CRM raw. Rep figures out if it's worth their time. AI scores against your ICP before it touches the CRM. Spam filtering Junk enters alongside real leads. Bots and disposable emails get caught during the form fill. Never reach the CRM. Routing Round robin or basic territory rules. Sometimes wrong. Enrichment data + form responses match the lead to the right rep instantly. Scheduling Rep sends a booking link hours later. Prospect books on the right rep's calendar inside the form. Your CRM can't do most of this. It wasn't designed to. A CRM is built for what happens after you have a qualified lead. Surface is built for everything that happens before. **Replaces:** your form tool (Typeform, HubSpot forms), your enrichment provider for inbound (Clearbit, ZoomInfo, Apollo), your lead scoring setup (stale CRM point systems), your routing logic (CRM workflows, Chili Piper, LeanData), and scheduling friction (booking links in follow-up emails). **Doesn't replace:** your CRM (HubSpot, Salesforce — you still need a system of record), your marketing automation (email sequences, nurture campaigns), or your sales engagement tools (outbound cadences, call tracking). It's not a CRM. It's the layer that makes your CRM useful from the first lead. If you're running HubSpot or Salesforce, your CRM is fine. The question is what's happening before the lead gets there. How long does it take from form fill to meeting booked? Does the lead arrive enriched or does the rep have to research it? Is routing based on real data or round robin? Does the prospect book inside the form or wait for a follow-up email? If any of those answers make you uncomfortable, the problem isn't your CRM. It's the gap in front of it. That's what Surface was built to close. --- # Surface Labs vs. Calendly URL: https://surface.thesurface.network/blog/surface-labs-vs-calendly Calendly is one of the most popular scheduling tools in the world. Millions of people use it to share availability and book meetings. If you're a sales rep who sends a scheduling link in your outreach emails, Calendly works great. But when B2B companies start using Calendly as part of their lead conversion flow — embedding it on the website, linking it from form confirmations, or routing leads to scheduling pages — it starts hitting limits it was never designed for. Calendly is a scheduling tool. It's not a lead conversion tool. The difference matters. Calendly is excellent at its core job: letting someone pick a time on your calendar. The interface is clean, the integration with Google Calendar and Outlook is seamless, and the round-robin team scheduling feature distributes meetings across reps evenly. For outbound sales, where a rep sends a personal scheduling link to a prospect they've already qualified, Calendly is hard to beat. It removes the back-and-forth of finding a time and gets the meeting booked. The problem isn't Calendly. It's using a scheduling tool to solve a lead conversion problem. Scheduling is the last step of the form-to-meeting flow. Calendly starts at that last step and skips everything before it. What the lead flow needs Calendly Surface Labs Capture lead data from forms Not its job — you need a separate form tool Core product — smart forms with conditional logic and qualifying questions Qualify the lead before routing Not its job — no qualification. Anyone with the link can book. Native — form responses evaluated against your criteria in real time Route to the right rep Round-robin across a team, or individual booking links. No routing by territory, deal size, or product interest. Attribute-based routing — matches lead to the right rep based on multiple variables before showing availability Personalized first response Not its job — Calendly sends a generic booking confirmation Instant personalized message within 60 seconds — rep name, lead context, scheduling link Block unqualified leads from booking Not built in. Anyone can book — spam, competitors, tire-kickers. Reps waste time on meetings that shouldn't have been booked. Qualification gates — only leads that meet your criteria see a scheduling option Full-funnel visibility Knows about scheduled meetings. Doesn't know about form submissions, routing decisions, or leads that didn't book. Tracks the full journey — form submission through qualification through routing through meeting booked Capture leads who aren't ready to schedule Not its job — if the visitor doesn't book, they're gone Multiple capture formats at different commitment levels. Leads who aren't ready to book can still be captured and nurtured. Calendly is the right tool if the lead is already qualified and you just need to get a meeting on the calendar. It's the wrong tool if you need to qualify, route, and convert an unknown visitor into a meeting — because it only does the booking part. Here's what happens when a B2B team uses Calendly as their primary conversion tool on the website: A visitor clicks "Book a Demo." They see a Calendly embed with available times across the team. They pick a slot. A meeting is created — but the rep who got it knows nothing about the lead's company, budget, use case, or timeline. The meeting becomes a discovery call where the rep asks all the qualifying questions that should have been asked on the form. Meanwhile, 30% of the bookings are from people who aren't qualified — students, competitors, people in the wrong geography, or leads that should have been routed to a different team. The rep can't filter them because Calendly doesn't know enough about the lead to make that judgment. And the leads who visited the page but weren't ready to book a meeting? They're gone. Calendly captured nothing — no email, no company, no intent signal. The only lead capture mechanism was "pick a time," and anyone who wasn't at that stage left empty-handed. **Use Calendly when:** A rep is sending a personal scheduling link to a prospect they've already qualified through email, call, or LinkedIn. The prospect is known, the qualification is done, and you just need to book the meeting. Calendly is perfect for this. **Use Surface when:** An unknown visitor arrives on your website and you need to capture their information, qualify them, route them to the right rep, and get a meeting booked — all in one continuous flow. This is the inbound conversion use case, and it requires more than scheduling. The two tools can coexist. Surface handles the inbound capture-to-meeting flow on the website. Calendly handles outbound scheduling for reps doing 1:1 outreach. Different jobs, different tools. Surface is the full capture-to-meeting system — forms that qualify, routing that matches, response that personalizes, and scheduling that's connected to all of it. The meeting gets booked on the right rep's calendar because the system knows who the right rep is before it shows available times. If your Calendly page is getting bookings from unqualified leads and your reps are spending meetings doing discovery that should have happened on the form, the scheduling isn't the problem. The lack of everything before the scheduling is the problem. Surface was built to fill that gap. --- # Surface Labs vs. HubSpot Forms URL: https://surface.thesurface.network/blog/surface-labs-vs-hubspot-forms If your company uses HubSpot, you're probably using HubSpot Forms. They come with the platform, they work, and they're already connected to your CRM. For a lot of teams, that's enough to never think about forms again. But "comes with the platform" and "solves the problem" aren't the same thing. HubSpot Forms are a feature inside a CRM. Surface Labs is a dedicated lead ops platform. They overlap on one function — capturing form data — and diverge on everything that happens after. HubSpot Forms are tightly integrated with HubSpot CRM. Submissions automatically create or update contact records. Form data flows into workflows, lists, and reporting without any middleware. If your entire stack is HubSpot, the native forms are frictionless to deploy. They also offer progressive profiling — showing different fields to returning visitors — and basic dependent fields. For simple use cases like newsletter signups, content downloads, and basic contact forms, HubSpot Forms are perfectly adequate. The comparison gets interesting when you look at what happens after the form submit — which is where most lead conversion is won or lost. Capability HubSpot Forms Surface Labs Form builder Drag-and-drop, decent templates, embedded or standalone Multi-step with conditional logic, branching paths, real-time validation Conditional logic Basic dependent fields — show/hide based on one answer Deep branching — different paths, different questions, different outcomes based on multiple inputs Qualification at capture Not built in. Requires separate lead scoring that runs on behavioral data over time Native — form responses evaluated against your criteria in real time at submission Routing Not part of the form. Handled by HubSpot workflows — round-robin or basic property-based assignment Built into the form flow — attribute-based routing by territory, deal size, product interest, rep availability Speed-to-lead Depends on workflow triggers and rep response. Typical: 30 min – several hours Sub-60-second automated response by design Instant personalized response Not native. Requires a separate workflow — generic unless heavily customized Built in — personalized message with rep name, lead context, and scheduling link Embedded scheduling Not part of the form. HubSpot Meetings is separate and not integrated into the form experience Native — lead books on matched rep's calendar within the form flow Abandoned form recovery Not available. Partial submissions are lost. Captures partial submissions, triggers automated follow-up Spam filtering reCAPTCHA, honeypot, blocked domains. Catches basic bots. Multi-step conditional logic as structural filter, plus validation and domain checks Analytics Form views, submissions, conversion rate. Campaign-level. Full-funnel: submission → qualification → routing → response → meeting booked HubSpot Forms win on one thing: zero-configuration CRM integration. If you need a simple form live in 5 minutes, nothing is faster. Surface wins on everything that happens after submission — qualification, routing, response speed, scheduling, and full-funnel measurement. If your lead-to-meeting rate is above 25% and your speed-to-lead is under 5 minutes, HubSpot Forms are probably fine. Your process is working. If your lead-to-meeting rate is under 15% and your speed-to-lead is measured in hours, HubSpot Forms aren't the problem — but they're not helping either. They're doing the first 10% of the job and leaving the other 90% to workflows and human speed. Most teams running Surface alongside HubSpot don't rip out HubSpot Forms entirely. They use Surface for high-intent capture points — demo requests, pricing inquiries, contact forms — and keep HubSpot Forms for low-intent use cases like newsletter signups and content downloads. Surface pushes clean, qualified, routed leads into HubSpot CRM automatically. HubSpot remains the system of record. The form layer just got significantly smarter. Surface replaces HubSpot Forms where it matters most — on the pages where high-value leads convert. If your HubSpot Forms are collecting submissions but your reps are still spending hours qualifying and chasing, the form isn't doing enough. Surface was built to make it do more. --- # Surface Labs vs. HubSpot Marketing Hub URL: https://surface.thesurface.network/blog/surface-labs-vs-hubspot-marketing-hub HubSpot Marketing Hub is the default marketing platform for tens of thousands of B2B companies. It's where teams build landing pages, send emails, manage contacts, run workflows, and report on campaigns. For many companies, HubSpot is the marketing stack. Surface Labs is not a marketing platform. It doesn't send emails, build landing pages, or manage nurture sequences. It does one thing: the capture-to-meeting flow — getting a lead from form submission to qualified, routed, and on a rep's calendar in under 60 seconds. These tools get compared because they both touch lead capture. But they're solving different problems, and understanding the difference saves teams from either overpaying for a suite they don't fully use or underpaying for a layer that's missing from their stack. HubSpot Marketing Hub is a full marketing automation platform. It handles the entire marketing lifecycle: attracting visitors through blog and SEO tools, capturing leads with forms and landing pages, nurturing leads through email sequences, scoring leads based on behavior over time, and reporting on campaign performance with built-in attribution. For teams that need all of these functions in one integrated platform, HubSpot is a strong choice. The integration between marketing and CRM is seamless. The workflow builder is flexible. The ecosystem of integrations is massive. Most teams don't switch from HubSpot to Surface. They add Surface to fix the specific thing HubSpot doesn't do well — the real-time capture-to-meeting flow. Capability HubSpot Marketing Hub Surface Labs Email nurture / lifecycle campaigns Best-in-class. This is what it's built for. Not included. Not the product's job. Landing page builder Built in. Templates, A/B testing, personalization. Not included. Blog / SEO tools Built in. Blog hosting, SEO recommendations, topic clusters. Not included. Lead capture forms Included. Basic form builder with progressive profiling and dependent fields. Core product. Multi-step conditional forms with real-time qualification. Real-time lead qualification Not real-time. Lead scoring accumulates over days/weeks based on behavioral data. Instant — form responses evaluated at the moment of submission. Intelligent routing Not native to Marketing Hub. Requires CRM workflows with limited routing logic. Core product — attribute-based routing by territory, deal size, product, availability. Speed-to-lead automation Possible through workflows but requires setup and typically results in 15+ minute response. Sub-60-second response by design. Embedded scheduling in forms Not available. HubSpot Meetings is a separate feature. Native — lead books on matched rep's calendar within the form. Abandoned form recovery Not available. Captures partial submissions and triggers follow-up. Post-form journey tracking Campaign-level attribution. Doesn't track individual lead journey from form to meeting. Lead-level tracking from submission through meeting booked. Pricing (mid-market) $800–$3,600/month depending on tier, plus contacts overage Significantly lower. No contact-based pricing. HubSpot wins on breadth — it does more things across the marketing lifecycle. Surface wins on depth in the specific window between form submission and meeting booked. HubSpot Marketing Hub Professional starts at $800/month. Enterprise starts at $3,600/month. Both have contact-based pricing that increases as your database grows. Add in the CRM, Sales Hub, and Operations Hub, and the full HubSpot stack for a mid-market company typically runs $2,000–$6,000/month. Most teams at the Professional tier use email marketing, forms, basic workflows, and reporting. They're paying for the full suite but using 25–30% of the features. The advanced capabilities — branching workflows, predictive lead scoring, custom reporting, adaptive testing — often go unused because they require a dedicated ops person to configure and maintain. Surface costs a fraction of HubSpot's marketing tier and solves the specific problem that most teams thought HubSpot would fix: getting leads from form submission to sales conversation as fast as possible. If you need a full marketing automation platform — email nurture, landing pages, blog hosting, campaign orchestration, and attribution — HubSpot Marketing Hub is a strong choice. You're paying for breadth, and if you use it, it's worth it. If your actual problem is that leads fill out forms and sit for hours before anyone contacts them, routing is round-robin, qualification happens on the phone instead of the form, and you can't tell which campaigns produce meetings (not just leads) — that's a lead ops problem. HubSpot can be configured to partially address it, but it wasn't built for it. The most common setup we see: HubSpot handles email nurture, landing pages, and campaign management. Surface handles the real-time capture-to-meeting layer. Qualified leads from Surface flow into HubSpot CRM for ongoing management. Each tool does the job it was built for. \[IMAGE: A simple architecture diagram. Top layer: "Surface Labs — Capture, Qualify, Route, Respond, Schedule (real-time)." Arrow pointing down to: "HubSpot — CRM, Email Nurture, Campaign Management, Reporting (ongoing)." Shows Surface as the upstream layer feeding clean leads into HubSpot. White background, blue (`#4F6DF5`) accent, flat design.\] Surface sits in front of HubSpot as the real-time lead ops layer. It doesn't replace HubSpot — it fixes the part that HubSpot wasn't built to handle. If you're paying for HubSpot Marketing Hub and your leads are still sitting in a queue, Surface closes the gap at a fraction of the cost. --- # Surface Labs vs. Marketo URL: https://surface.thesurface.network/blog/surface-labs-vs-marketo Marketo is one of the original enterprise marketing automation platforms. Acquired by Adobe, it powers marketing operations at thousands of mid-market and enterprise companies. It's powerful, deeply configurable, and — if you've ever tried to set it up — genuinely complex. Surface Labs is not a marketing automation platform. It handles one thing: the capture-to-meeting layer that sits between your ad spend and your CRM. Different tools, different jobs — but they end up on the same shortlist because teams buying Marketo often expect it to solve lead conversion problems it wasn't designed for. Marketo excels at enterprise-grade campaign orchestration. Multi-step nurture programs, behavioral triggers, dynamic content, account-based marketing, and advanced lead scoring — Marketo handles sophisticated marketing operations at scale. Its integration with Salesforce is deep. Its reporting and attribution capabilities are built for organizations with complex, multi-touch buying journeys. And for marketing ops professionals who know the platform, it's one of the most flexible automation tools on the market. Marketo's strength is in long-cycle marketing operations — nurturing a lead over weeks or months through content and engagement. Surface's strength is in the first 60 seconds — capturing, qualifying, routing, and responding to a lead the moment they raise their hand. Capability Marketo Surface Labs Email nurture / drip campaigns Enterprise-grade. Multi-track, behavior-triggered, dynamic content. Not included. Lead scoring Sophisticated — behavioral + demographic, multiple scoring models, score decay Real-time qualification at capture. Scores based on form responses + enrichment, not accumulated behavior. Campaign orchestration Deep — programs, channels, nested campaigns, A/B testing at scale Not included. Lead capture forms Built in. Functional but basic. Not designed for real-time qualification or routing. Core product — multi-step conditional forms with branching qualification logic Intelligent routing Not native. Requires Salesforce integration + custom flows or third-party tools. Core product — real-time routing by territory, deal size, product, availability Speed-to-lead Depends on Marketo-to-Salesforce sync + CRM workflow. Typical: 15 min – hours. Sub-60 seconds by design Embedded scheduling Not available. Native — book on matched rep's calendar within the form flow Setup and time-to-value 8–16 weeks with a certified consultant or dedicated admin Days. Self-serve configuration. Ongoing maintenance Requires Marketo-certified admin. Program logic, smart lists, token management. Self-serve. Non-technical ops teams can manage routing and forms directly. Pricing $1,000–$4,000+/month plus implementation and admin costs Significantly lower. No implementation fees. No admin required. Marketo wins on marketing automation depth. Surface wins on the real-time capture-to-meeting flow. They're not competing for the same job. Marketo's licensing starts at roughly $1,000/month for small databases and scales to $4,000+/month for enterprise tiers. But the licensing is the smaller number. **Implementation** runs $10K–$50K+ with a certified Marketo partner. The platform is complex enough that most teams can't self-implement — the program structure, scoring models, and Salesforce integration require specialist knowledge. **Ongoing admin** requires a Marketo-certified professional — either a full-time hire ($80K–$130K/year) or a fractional consultant ($3K–$6K/month). Without one, the platform gradually decays — programs break, scoring models drift, and sync issues go undetected. **Total cost of ownership** for a mid-market company on Marketo typically runs $80K–$200K/year when you include licensing, admin, and periodic consulting. For companies that use Marketo's full capability set — complex nurture programs, ABM, multi-touch attribution — this investment can be justified. For companies that primarily need leads to reach the right rep faster, it's massive overkill. This is the pattern we see: a company buys Marketo because they're "ready for enterprise marketing automation." They implement it over 3 months. They build a few email programs and a basic scoring model. And then the platform sits at 20–30% utilization because the team doesn't have the operational bandwidth to use its advanced features. Meanwhile, the actual problem — leads sitting in Salesforce for hours before anyone contacts them, routing that doesn't match the sales structure, no qualification at capture — remains unsolved. Because those aren't marketing automation problems. They're lead ops problems. Marketo can be configured to partially address these issues, but it requires custom programs, Salesforce flow integration, and ongoing maintenance by a specialist. Surface solves them natively, in days, without a specialist. The best-performing teams we see using Marketo run both platforms: Marketo handles what it's built for — email nurture, scoring decay, ABM programs, and campaign attribution. Surface handles the real-time layer — capturing, qualifying, routing, and responding to leads at the moment of capture. Qualified leads flow from Surface into Salesforce, where Marketo picks them up for ongoing nurture. Each tool does the job it was designed for. Neither is asked to do the other's job. Surface is the real-time lead ops layer that Marketo doesn't provide. If you're on Marketo and your leads are still waiting hours for a response, the gap isn't in your marketing automation — it's in the layer that sits upstream. Surface closes it at a fraction of Marketo's cost, without the implementation timeline. --- # Surface Labs vs. Salesforce Marketing Cloud URL: https://surface.thesurface.network/blog/surface-labs-vs-salesforce-marketing-cloud If you're evaluating tools to fix your lead ops, both of these names will come up. Salesforce Marketing Cloud is one of the most widely deployed marketing platforms in the world. Surface Labs is newer, smaller, and narrowly focused on lead capture and routing. They're not the same kind of tool — but they often end up on the same shortlist because teams are trying to solve the same problem: what happens between "lead fills out a form" and "rep has a conversation." This is a fair comparison of where each platform fits, where each falls short, and which one actually solves the lead ops problem most teams are dealing with. SFMC is a full-suite marketing platform. Email campaigns, journey orchestration, audience segmentation, multi-channel messaging, analytics. If you need to build a 12-touch nurture sequence across email, SMS, and ads for 500,000 contacts, SFMC can do that. It's deeply integrated with Salesforce CRM, which matters if your sales team already lives in Salesforce. For enterprise marketing teams running complex lifecycle campaigns at scale, SFMC is a serious platform. It wasn't built to be lightweight — it was built to be comprehensive. Surface is built for one job: getting a lead from form fill to qualified, routed, and contacted in under 60 seconds. Capture, qualification, intelligent routing, and instant response — in a single system. It's not a marketing automation platform. It doesn't do email nurture or audience segmentation. It does the first 60 seconds of the lead lifecycle, and it does them fast. Most teams evaluating SFMC aren't buying it for email nurture. They're buying it because they think it will fix their lead ops — the capture-to-conversation gap. That's where the comparison matters. Capability Salesforce Marketing Cloud Surface Labs Lead capture / smart forms Basic — web forms exist but aren't built for real-time qualification Core product — forms with built-in qualification logic, conditional fields, real-time data capture Lead routing Not native. Requires Salesforce CRM + Flow Builder + custom config Core product — rule-based and intelligent routing, real-time, configurable in minutes Speed-to-lead Depends on CRM workflows. Typical: minutes to hours. Sub-60-second response by design Instant personalized response Possible through Journey Builder, but requires significant setup Native — personalized response triggered at the moment of routing Setup and time-to-value 4–12 weeks with a dedicated admin or implementation partner Hours to days. No dedicated admin required. Ongoing maintenance Requires SFMC-certified admin. Journey Builder, AMPscript, data extensions. Self-serve. Non-technical ops teams can manage routing rules directly. Email nurture / lifecycle campaigns Best-in-class. This is what it was built for. Not included. Not the product's job. Multi-channel campaign orchestration Deep — email, SMS, ads, push, social Not included. Pricing $1,250–$4,200+/month depending on tier, plus implementation costs Significantly lower. No implementation fees. SFMC wins on breadth. It does more things. But the things most teams need fixed — capture, qualification, routing, and speed-to-lead — aren't the things SFMC was built to do. They're possible inside SFMC, but they require custom configuration, a dedicated admin, and weeks of setup to get right. If your lead ops problem is "we need better email nurture and lifecycle campaigns," SFMC is the right tool. It's purpose-built for that job and it does it well. If your lead ops problem is "leads come in and sit for hours before anyone contacts them, routing is broken, and we're wasting ad spend on leads that never get a real conversation" — that's a different problem. And SFMC wasn't designed to solve it. This is the pattern we see most often. A team buys SFMC expecting it to fix the capture-to-conversation pipeline. They spend 8 weeks on implementation. They hire or contract an SFMC admin. And then they realize the actual bottleneck — speed-to-lead, routing accuracy, qualification at capture — still isn't solved. Because those aren't marketing automation problems. They're lead infrastructure problems. The most common setup we see at companies running both isn't an either/or. It's SFMC handling what it's good at — nurture sequences, lifecycle campaigns, audience management — and Surface handling the upstream layer that SFMC doesn't cover: real-time capture, qualification, routing, and instant response. The lead hits Surface first. It gets qualified, routed, and contacted in seconds. Then it enters Salesforce CRM and SFMC for ongoing relationship management and nurture. Each tool does the job it was built for. SFMC is a powerful platform if you need enterprise marketing automation. But it's not a lead ops tool — and treating it like one leads to months of implementation, ongoing admin overhead, and a capture-to-conversation gap that never actually gets closed. Surface is a narrower tool that does one thing well: making sure every lead gets captured cleanly, qualified intelligently, routed correctly, and contacted in under a minute. If that's the problem you're solving, it's the faster, simpler, and cheaper answer. If you're currently running SFMC and your leads are still sitting in a queue for hours before anyone follows up, the gap isn't in your marketing automation. It's in the layer that sits in front of it. That's what Surface was built for. --- # Surface Lead Scheduling URL: https://surface.thesurface.network/blog/surface-lead-scheduling Pull up your last invoice from Chili Piper or Calendly, then think about what happens the next time you hire a rep. The number goes up, and it goes up every single time you grow, whether or not those reps have closed anything yet. The problem was never the software, it's the pricing model. Per-seat billing was built to sell seats rather than close pipeline, and it quietly punishes you for building the exact thing you're trying to build, which is a bigger team. We always thought that was backwards, so when we built scheduling into Surface we priced it the opposite way, where you can add one rep or a hundred and the cost of scheduling doesn't move. Here's what per-seat scheduling actually costs as you grow. Chili Piper's Routing and Scheduling tier starts at $15,000 a year and includes 15 seats, with every seat past that running $45 per month, while Calendly Teams comes in at $16 per seat per month. Both of them scale directly with every hire you make. Team size Chili Piper / yr Surface / yr 15 reps $15,000 (base tier) $0 in seats 25 reps $20,400 $0 in seats 50 reps $33,900 $0 in seats The line that matters is the last column, and it doesn't move, because scheduling was never the product. The pipeline it produces is. Their floor is also $15,000 a year even if you've only got a handful of reps, and their AI credits get burned across every tier while how many you actually get and what you pay when you go over are both still listed as details coming soon on their own pricing page. So you're signing a five-figure contract without knowing what it'll really cost you. Flat pricing is the part people notice first, but it isn't the part that changes your close rate. That comes from the scheduler knowing what's happening upstream. Because Surface scheduling sits on top of your lead data, it books meetings based on the rep's close rate, the territory the lead belongs to, their ICP fit score, and the campaign that brought them in, instead of just checking who has an open slot on Thursday. When a lead comes in, Surface already knows all of that, so the meeting lands with the rep most likely to close it rather than the one whose calendar happens to be empty, and your close rate goes up because the right rep is talking to the right lead rather than because you added another seat to a routing tool. Most teams running scheduling today have stitched together more than they realize. The old stack Surface Chili Piper, Calendly, or RevenueHero Scheduling built into the platform A separate integration layer into HubSpot or Salesforce Native to your lead data Round-robin rules someone set up months ago Routing by close rate, territory, and ICP fit Per-seat billing that grows with every hire Flat cost, 1 rep or 100 Most of the teams we've talked to cut roughly half their scheduling and routing spend when they switch, and that's before counting the RevOps hours nobody spends anymore keeping three tools talking to each other. We didn't build scheduling because it's exciting, we built it because every seat you pay for is a seat you're being quietly discouraged from hiring. The math on per-seat tools always punishes the teams growing fastest, and those are exactly the teams we want as customers. If your calendar tool is priced against your own growth, it's time to replace it. [Book a demo →](https://withsurface.com/book-a-demo) and we'll show you what your scheduling stack looks like without the seat tax. --- # Surface Scheduler URL: https://surface.thesurface.network/blog/surface-scheduler Surface Native Scheduler is a new feature inside Surface's Lead Operations suite. It's a full meeting scheduler built directly into Surface, so leads can book without leaving your form flow and your team can manage scheduling, routing, and post-booking automation from the same platform they already use for everything else. Built for marketing ops and growth teams that are tired of stitching together Calendly or Chili Piper alongside their forms, CRM, and routing logic. ### Why we built this Most B2B teams run their inbound pipeline across three or four disconnected tools. The form lives in one place. The scheduler lives in another. The routing logic lives somewhere else. And the post-booking follow-up is either manual or spread across Zapier and Slack notifications that nobody maintains. The problem isn't that these tools don't work individually. The problem is what happens between them. A lead fills out your form, gets qualified, and then you redirect them to a Calendly link. That redirect is where you lose people. They land on a different domain, the branding doesn't match, the experience feels disconnected, and a meaningful percentage of qualified leads never actually book. Even when they do book, the data is fragmented. The form submission lives in one system. The booking lives in another. Connecting the two requires custom integrations or middleware. Reporting on the full journey from form fill to booked meeting means pulling data from multiple sources and stitching it together manually. Surface Native Scheduler eliminates this entire layer of fragmentation. Scheduling lives inside the same platform as your forms, your lead scoring, your routing logic, and your post-booking automation. One system, one flow, one set of data. ### How it works Setting up a scheduler takes a few minutes. You connect your Google Calendar, invite your team members, and create your first scheduler. Surface supports three scheduler types out of the box: **Scheduler type** **How it works** **Best for** One on one Leads book time on a single rep's calendar based on their availability Solo reps, founder-led sales, small teams Round robin Meetings distributed across your team by availability and weight Teams with multiple reps, fair distribution Group Only shows time when all selected team members are free Panel interviews, multi-stakeholder demos The scheduling settings give you the kind of control that matters for inbound operations: **Setting** **What it controls** Booking window How far in advance leads can book (e.g., 2 weeks) Minimum notice Leads can't book anything starting sooner than this (e.g., 30 minutes) Buffer time Blocked time before and after each meeting to prevent back-to-back stacking Daily limit Max number of bookings per day per rep Date-specific overrides Block off specific dates or set custom hours for holidays, offsites, etc. Block public holidays Automatically marks reps unavailable on holidays for their country The questions layer lets you control what information you collect at booking time. Work email is required by default. You can add first name, last name, and toggle options like blocking personal emails, enabling CAPTCHA to prevent automated submissions, allowing guests, pre-filling fields for returning visitors, and showing GDPR consent before booking. ### Branding The booking page is fully customizable. You set the theme colors, primary color, font, border radius, shadow, and preview the page live as you make changes. The result is a booking experience that looks like your brand, not like a third-party tool. This is the part that matters for conversion. When a lead fills out your Surface form, gets qualified, and then sees a booking page that matches the same look and feel, there's no friction. No redirect to a different domain. No jarring visual disconnect. The entire flow feels like one experience because it is one experience. ### Where the real differentiation is: routing Most schedulers route by availability. Surface Native Scheduler routes by anything. Because the scheduler is embedded directly inside Surface's form and logic system, you can build routing flows that go far beyond simple round-robin. Route leads based on territory, so APAC leads go to your APAC rep and NA leads go to your NA team. Route based on form answers, so leads who selected "Enterprise" see your enterprise AE's calendar and leads who selected "Startup" see someone else. Route based on deal size, product line, industry, or any other dimension you're capturing in the form. The routing flows are built visually in Surface's Logic Builder. You can also describe routing rules in plain English and let AI build the flow for you. Something like "route leads with over $100K ad spend to our senior AE, everyone else goes round-robin" and the routing logic creates itself. This is what prospects have been asking for most. The scheduling part is table stakes. The ability to route leads to the right person based on who they are and what they said, without engineering work, is what replaces the entire Calendly-plus-routing-tool stack. ### Post-booking automation When a meeting is booked, rescheduled, or cancelled, Surface can trigger workflows automatically. This is the same workflow builder that powers Surface forms, now wired into the scheduler out of the box. **Trigger** **What it fires on** **Example actions** Booking Created A meeting is successfully booked through the scheduler Send confirmation email, notify rep in Slack, create deal in CRM, enroll in prep sequence Booking Rescheduled A previously booked meeting gets moved to a new time Notify rep, update CRM record, send rescheduled confirmation Booking Cancelled A booked meeting gets cancelled Trigger re-engagement sequence, notify manager, update CRM status, add to nurture Each trigger can branch into whatever actions your workflow needs. The workflow builder is visual, so you can see the full post-booking logic at a glance and add or modify actions without touching code. The cancellation trigger is particularly valuable for teams that lose a significant percentage of booked meetings to no-shows and last-minute cancellations. Instead of those leads disappearing into the void, the cancellation workflow catches them and routes them into a re-engagement flow automatically. ### Round-robin distribution reports For teams using round-robin scheduling, Surface ships with a built-in distribution report. It shows per-rep meeting counts, queue position, and the reasoning behind each assignment. If a rep feels like they're not getting their fair share of meetings, or if a manager wants to audit the distribution, the data is right there. This is a feature that teams don't know they need until they've been running round-robin for a month and someone asks "why is Rep A getting twice as many meetings as Rep B?" Without a distribution report, you're digging through calendar data and building spreadsheets. With Surface, you open the report. ### How it connects to everything else Surface Native Scheduler sits inside the Lead Operations suite alongside AI Form Routing, AI Lead Scoring, and the Logic Builder. The integration isn't bolted on. It's native. A lead fills out your form. AI Lead Scoring evaluates the submission and assigns a score. AI Form Routing decides whether this lead is qualified based on that score. If they are, the form flow branches to the scheduler step. The scheduler shows the right rep's calendar based on your routing rules. The lead books. The workflow triggers. CRM gets updated. Rep gets notified. Confirmation gets sent. That entire journey happens inside Surface. No redirects, no middleware, no data stitching. Form fill to booked meeting in one platform. ### Getting started Surface Native Scheduler is available now for all Surface users. Setup takes about 10 minutes: connect your Google Calendar, invite your team, create a scheduler, customize the branding, and set your routing rules. If you want to see how the scheduler works with AI Lead Scoring and Form Routing as a complete inbound pipeline, [book a demo](https://withsurface.com/book-a-demo) and we'll walk through the full flow. --- # Surface Labs vs. Chili Piper URL: https://surface.thesurface.network/blog/surface-versus-chilipiper Chili Piper was the go-to for inbound lead routing and scheduling for years. They helped define the category. But that was a different era. Chili Piper was built before AI-powered qualification, before built-in enrichment, before teams started demanding one platform instead of five. And for many teams, the legacy pricing model and growing complexity have become hard to justify. Here's an honest breakdown of where each product fits. Chili Piper nailed the core problem early: when someone fills out a form, get them to a sales rep and a calendar invite fast. Their Concierge product did this well and integrates with most major CRMs. If all you need is a scheduling layer on top of your existing forms with basic routing, it still works. The question is whether a legacy scheduling-and-routing tool is enough for how B2B teams operate today. ### The routing builder gets complicated fast Chili Piper's routing uses a visual flow builder. For simple setups — a round robin across five reps — it's fine. But add territories, account-based routing, ICP scoring, and fallback logic, and it becomes a sprawling diagram that's hard to read and harder to update. With Surface Labs, you describe your routing logic in plain English to an AI assistant and it builds the rules for you. No dragging boxes. No tracing lines through a flowchart. ### It's a routing tool, not a lead ops platform Chili Piper handles one piece: getting a form fill to a calendar invite. It doesn't build the form, enrich the lead, filter spam, or qualify before routing. So you still need a form tool, an enrichment tool, and a spam solution. Three or four extra tools, three or four extra integrations, three or four extra points of failure. Surface Labs combines forms, enrichment, qualification, routing, spam filtering, and scheduling in one system. One lead comes in, everything happens in a single flow. No stitching. No middleware. ### Seat-based pricing is a legacy model that punishes growth Take a look at Chili Piper's pricing page: Our team genuinely didn't know what to click on when we first saw this. There are five separate products — Concierge, Chat, Distro, Handoff, and ChiliCal — each priced at $30/user/month, plus platform fees ranging from $150 to $1,000/month depending on the product. And their new Chat AI product is a flat $20,000/year. Here's what the math actually looks like: Product Per-seat cost Platform fee What it does Concierge $30/user/mo $150–$1,000/mo Qualify, route, and schedule Chat $30/user/mo $1,000/mo Chat with website visitors Distro $30/user/mo $150/mo Route Salesforce records Handoff $30/user/mo $150/mo Route and schedule on behalf of others ChiliCal $15/user/mo — Scheduling links Chat AI Flat fee $150/mo AI chatbot — $20,000/year Most teams need at least Concierge + Distro. For a 15-person sales team, that's $900/month in seat fees plus $150–$1,150 in platform fees — before you've added chat, handoff, or any add-ons. Scale to 30 reps and you're well past $2,000/month just for routing and scheduling. Scale to 50 and you're approaching **six figures a year.** And here's the fine print at the bottom of their page: month-to-month contracts are only for new customers. Once you're in, you're locked into annual. This is the core problem with legacy per-seat pricing. Your growth becomes their revenue. Every new hire, every new territory — the bill goes up, even though the software isn't doing anything different. ### It locks you into their scheduler When you use Chili Piper, you use Chili Piper's scheduling. If your team prefers Calendly, Cal.com, or HubSpot Meetings… too bad. Surface Labs integrates with Chili Piper, Calendly, Cal.com, RevenueHero, Reclaim AI, SavvyCal, HubSpot Meetings, and Clari. Use whatever you want. Swap later. Your routing doesn't care. ### Your data breaks and nobody tells you Chili Piper sits between your forms and your CRM, mapping fields from one to the other. The problem: it has no way to make sure those fields stay in sync. Someone renames a field in HubSpot. Someone changes a dropdown on the form. Chili Piper doesn't catch it. The mapping silently breaks. Leads flow in with missing data or wrong assignments — and nobody notices until a rep complains weeks later. Surface Labs Chili Piper Lead routing ✅ AI-assisted logic builder ✅ Visual flow builder (gets messy fast) Lead enrichment ✅ Built-in ❌ Needs a separate tool Data sync protection ✅ Can't publish broken mappings ❌ Fails silently Real-time observability ✅ Built-in monitoring + alerts ❌ Scheduling ✅ Works with any scheduler ❌ Chili Piper scheduler only AI-powered logic building ✅ Describe routing in plain English ❌ CRM integration ✅ HubSpot, Salesforce, etc. ✅ HubSpot, Salesforce, etc. Pricing model Per-company (no seat charges) Per-seat (legacy model) Best for Teams that want one platform for the full lead-to-meeting flow Teams that just need basic scheduling + routing on top of existing forms **Chili Piper** if you already have your forms, enrichment, and qualification handled elsewhere and just need a legacy scheduling layer with basic routing. Simple setup, small team, don't mind managing multiple tools. **Surface Labs** if you want one system from form fill to meeting booked. Complex routing, growing sales team, tired of stitching tools together, or you'd rather tell an AI what your routing should do instead of building flowcharts by hand. Chili Piper is a legacy scheduling and routing tool. Surface Labs is a modern lead operations platform. They started in the same place. They're going in very different directions. _Want to see how Surface Labs handles your routing? _[\*Book a walkthrough \*](https://www.withsurface.com/book-a-demo)_— we'll show you what your current flow looks like in our system and build you a new flow in Surface live on the call in under 15 minutes._ --- # Taste Is the New Marketing Bottleneck | Surface Labs URL: https://surface.thesurface.network/blog/taste-is-the-new-marketing-bottleneck Ask an AI model for campaign ideas and receive fifty before lunch. Sure, a few are clever. Most are competent. None are obviously unusable. The team asks for fifty more, then requests alternate headlines, visual concepts, audience variations, landing-page structures, and social executions. By the end of the day, everyone has more material than they can properly review. The next morning, the creative meeting lasts two hours because nobody knows which direction deserves to survive. This is becoming a familiar AI marketing problem. Generation became faster than judgment. Marketing teams once lost time while trying to produce enough viable options. Writers stared at empty documents. Designers waited for approved copy. Product marketers spent days creating the first coherent version of a campaign narrative. AI has reduced much of that initial friction. The constraint has moved. Someone still needs to recognize which idea understands the customer, which claim reflects the product, which expression sounds like the company, and which campaign will remain interesting after the novelty wears off. Someone needs to reject the plausible work that has no reason to exist. Taste is becoming the marketing bottleneck. Taste in marketing is the ability to select and shape work according to the customer, product, brand, market, and moment. It is more rigorous than personal preference. A marketer saying “I do not like this color” is expressing preference. A marketer explaining that a visual system makes an enterprise security product appear unserious, resembles three major competitors, and conflicts with the expectations of its buying committee is exercising judgment. Marketing taste combines several forms of understanding: - Knowledge of the customer and the language customers actually use - Familiarity with the category and its repeated conventions - A clear view of the product’s strengths, limits, and credible promises - Sensitivity to timing, culture, format, and distribution - An understanding of the company’s existing identity - The ability to distinguish polished execution from a meaningful idea - The confidence to reject work that is acceptable but undistinguished Taste does not require one person to possess flawless instincts. Strong teams develop shared judgment through research, standards, critique, experimentation, and repeated exposure to good work. The objective is not to turn every marketer into an elusive creative genius. The objective is to build an organization capable of making better choices than its competitors when both have access to similar tools. Generative tools can create campaign territories, draft copy, develop layouts, summarize customer research, classify feedback, produce images, and adapt approved ideas across channels. That abundance has changed the economics of creative exploration. It has also created a review problem. A team that once considered three concepts can now consider thirty. The additional possibilities can increase the chance of finding something exceptional. They can just as easily consume the team’s attention, blur distinctions between directions, and encourage endless generation instead of commitment. The recent conversation surrounding Cannes Lions reflects this tension. McKinsey identified “creativity versus AI mediocrity” as one of the central signals from the 2026 festival, arguing that the industry has begun moving from AI experimentation toward harder questions of business value, operating models, human creativity, and differentiated growth. Digitas North America CEO Amy Lanzi made the abundance problem more direct during a Cannes interview with _The Verge_. She argued that the advertising industry does not need an endless supply of additional content and questioned the platform-led idea that creative should function primarily as another form of automated targeting. The concern is not that AI-generated work is always bad. Much of it is increasingly fine. “Fine” is becoming plentiful. A structurally complete article, plausible product image, reasonable headline, or clean social post no longer demonstrates much operational sophistication on its own. The useful question is whether the asset contains an idea customers can recognize, remember, trust, or act upon. For years, companies could outperform weaker competitors by reaching a basic level of executional competence. They could publish more consistently, improve their landing pages, create clearer advertisements, build better email sequences, test more headlines, and maintain stronger campaign operations. Many companies still need that work. AI can help them reach the baseline more quickly. The baseline will continue rising. The average presentation will become cleaner. The average brief will be more complete. The average campaign will include more variations. The average content team will conduct more research and produce more formats with fewer people. A company cannot assume those improvements will make it distinctive when its competitors receive the same advantages. The behavior of AI companies themselves illustrates the point. Sensor Tower data reported by _Marketing Brew_ found that U.S. AI brands spent approximately $424 million on advertising during the first quarter of 2026, more than three times the amount spent during the same period in 2025. Anthropic and OpenAI sharply increased spending across channels including television, streaming video, YouTube, and LinkedIn. These companies possess some of the world’s most advanced technologies for generating and distributing information. They still need familiar brand-building mechanisms because technical capability alone does not guarantee recognition, trust, or preference. AI can help a company explain more features. Taste helps the company decide which idea it wants people to remember. Marketing teams often discuss content debt as an archive problem. A company publishes hundreds of articles, landing pages, or campaign assets and eventually discovers that much of the material is outdated, duplicative, poorly connected, or inconsistent with the current product. Generative production can accelerate that debt. Every new asset creates future obligations: - Someone may need to update the claims. - Someone may need to verify that the product still works as described. - Someone may need to maintain the link, design, tracking, or localization. - Sales and support teams may need to correct the expectations it creates. - Search systems and AI tools may continue surfacing it after the company has moved on. - Customers may encounter contradictory explanations across channels. A team generating ten times more material can create ten times more opportunities for inconsistency. The [quality-versus-volume trap](https://withsurface.com/blog/content-marketing-strategy-the-quality-vs-volume-trap-in-ai-era) becomes an information-governance problem as much as an editorial one. The cost of an asset includes the attention required to review, distribute, measure, refresh, and eventually retire it. Good taste therefore includes the ability to decide that a piece of work should never be published. Teams cannot judge whether an idea is useful when they have only a synthetic understanding of the audience. AI can summarize reviews, sales transcripts, support tickets, survey responses, search behavior, and community discussions. These are valuable accelerants. The team should still spend time with the underlying material and, where possible, with the people themselves. Customer proximity gives marketers access to details that generic generation tends to smooth away: - The awkward phrase buyers use to describe the problem - The internal political obstacle preventing a purchase - The workaround customers have built themselves - The moment a buyer becomes worried enough to seek a solution - The feature customers praise that the company barely mentions - The promise the market has heard too many times - The objection that sounds irrational until the operating context becomes clear Specific details create the raw material for distinctive work. A campaign built around a real customer tension has a stronger center than one built around a demographic label and several generalized pain points. A [content brief](https://withsurface.com/blog/what-is-a-content-brief) becomes more useful when it contains actual language, objections, proof requirements, and decision context instead of a fictional persona with a stock-photo name. AI should help teams inspect more customer evidence. It should not become a substitute for customer evidence. Infinite possibility is rarely a useful creative environment. Strong marketing work usually emerges inside defined constraints: one audience, one problem, one product truth, one desired response, one primary channel, and one reason the company has permission to speak. Constraints make judgment possible. Compare these two requests: > Create a memorable campaign for our B2B analytics platform. > Create a campaign for demand-generation leaders who receive conflicting attribution reports from paid media, SEO, and RevOps. Demonstrate that our product reconciles the full lead journey without claiming perfect attribution. The campaign should make an analytics leader feel relieved rather than threatened. The second request gives both the model and the marketing team a field in which useful decisions can occur. The audience, tension, product truth, emotional outcome, and credibility boundary are visible. Teams using an [AI content strategy](https://withsurface.com/blog/ai-content-strategy-brand-voice) should document these constraints before generating a large number of outputs. Otherwise the system will optimize for plausibility and surface variation rather than strategic relevance. Marketing teams can make creative judgment less mysterious by evaluating work against explicit criteria. Score each serious concept from one to five across the following dimensions. ### Customer truth Does the work reflect a problem, desire, behavior, or tension that the intended audience genuinely experiences? A low score means the work relies on broad category assumptions. A high score means customers are likely to recognize themselves immediately. ### Product truth Can the company deliver the promise being made? A strong concept should emphasize something the product, service, experience, or organization can credibly support. Creative exaggeration cannot become a substitute for operational reality. ### Distinctiveness Could a direct competitor publish the asset after changing the logo? Category language is sometimes necessary. The core idea should still contain a recognizable perspective, proof point, visual choice, or product relationship that belongs to the company. ### Memorability Will the audience retain a sentence, image, term, demonstration, emotional turn, or useful framework? Memorability does not require spectacle. A precise idea can remain longer than an elaborate execution. ### Usefulness Does the asset help the audience understand, decide, compare, explain, or act? Useful work earns attention by reducing confusion or creating value before the transaction. ### Coherence Does the concept fit the larger brand, product, and customer experience? A surprising idea can still be coherent. The audience should not feel that the campaign belongs to a different company from the product. ### Channel fit Does the execution use the strengths of its format? A strong research article should not become a video script pasted into a blog. A useful executive post should not read like a compressed landing page. Adaptation requires more than shortening. ### Business consequence What should happen if the work succeeds? The answer might be recognition, qualified traffic, category understanding, sales enablement, product adoption, retention, or direct conversion. The team should know which outcome it is trying to influence. The rubric does not turn taste into arithmetic. It gives the critique a shared language. Many teams use AI during generation and leave the review process unchanged. The result is a larger pile entering the same approval bottleneck. A better workflow separates four activities. ### Divergence Use AI, customer evidence, competitive research, and human brainstorming to produce several genuinely different territories. Avoid generating twenty variations of the same safe premise. ### Selection Reduce the field using the taste rubric. Ask which territories deserve further investment before polishing every execution. ### Development Let human and machine collaborators improve the surviving ideas. Add proof, product detail, stronger language, visual logic, and channel-specific expression. ### Critique Review the work with people accountable for different truths: - Marketing protects the customer and strategic objective. - Product protects accuracy. - Brand or creative leadership protects identity and distinctiveness. - Sales protects buying context. - Legal protects material risk. - A clearly named owner makes the final decision. Consensus should inform the decision without becoming the decision. A campaign assembled from everyone’s least objectionable preference will usually arrive smooth, safe, and forgettable. Marketing teams should automate work where speed and consistency create leverage: - Transcript processing - Research organization - Feedback classification - Versioning and resizing - Initial outlines - Metadata - Formatting - Quality-assurance checks - Performance summaries - Localization support - Reformatting an approved idea for additional channels Teams should preserve explicit human ownership where judgment creates the value: - Positioning - Product promises - Customer interpretation - Strategic tradeoffs - Creative territory - Humor - Cultural sensitivity - Final selection - Material claims - Ethical boundaries - Brand-defining language The dividing line will move as tools improve. Accountability should remain visible even when the production method changes. Taste can improve business performance, but the relationship will rarely fit inside one attribution cell. Teams can still measure whether better judgment creates stronger work. Compare selected concepts against generic or control executions. Track: - Attention and completion - Recall and branded search - Direct and returning traffic - Engagement quality - Saves, shares, and customer reuse - Qualified conversion - Sales acceptance - Message accuracy during sales conversations - Customer language adoption - Creator, analyst, or community references - Performance decay over time Distinctive work may outperform immediately. It may also create value through slower recognition and repeated exposure. A useful testing program should include both conversion measures and memory signals. The [content marketing guide for 2026](https://withsurface.com/blog/content-marketing-guide-2026) makes a similar distinction between gaining visibility and earning conversion. Taste influences the connective tissue. It helps determine whether the material people encounter gives them any reason to continue. Before approving the next AI-assisted campaign, ask: 1. What customer evidence shaped the idea? 2. Which product truth gives us permission to make the claim? 3. What would remain if a competitor copied the format? 4. Which part should the audience remember tomorrow? 5. Why is this the correct format and channel? 6. What did human judgment add after generation? 7. What did the team deliberately reject? 8. Who owns the final decision? 9. Which business behavior should change? 10. What future maintenance obligation does this asset create? A team that cannot answer these questions probably needs another round of thinking rather than another round of generation. AI did not remove the hard part of marketing. It exposed where the hard part had been hiding. Producing a plausible asset required enough time and labor that teams could mistake executional difficulty for strategic value. Once production became easier, the importance of customer understanding, product truth, editorial standards, cultural awareness, and decisive selection became more visible. The companies most likely to benefit from AI will not be the companies that generate the largest number of options. They will be the companies that know which option deserves to become real. --- # The AI Creative Hangover: Why Brand Distinctiveness Matters More as Production Gets Easier | Surface Labs URL: https://surface.thesurface.network/blog/the-ai-creative-hangover-why-brand-distinctiveness-matters A marketing team opens its planning doc on Monday morning and sees a beautiful problem. The team can now make more. More ad variants. More landing page tests. More email drafts. More translated creative. More short-form video concepts. More social copy. More product explainers. More campaign angles. More personalized follow-up. More drafts that look, at first glance, good enough to keep moving. A few years ago, that would have sounded like a solved constraint. Creative production was slow. Content calendars were hard to fill. Paid teams waited on design. SEO teams waited on subject matter experts. Product marketers waited on launch materials. Founders waited on someone to make the company sound less like a feature list taped to a pricing page. Now the bottleneck has moved. Production is easier. Distinctiveness is harder. That was the real marketing conversation underneath the Cannes Lions 2026 chatter. AI was everywhere, but the more interesting story was not that AI had arrived in creative operations. That part is obvious now. The more interesting story was the industry’s first visible hangover from the AI production rush. Business Insider’s Cannes recap framed the week as a moment where human creativity “wrested the spotlight back from AI,” with marketers talking less about vague AI promises and more about what AI still cannot do reliably. The same piece reported that Cannes organizers tightened entry requirements after scrutiny over whether some of the previous year’s winning case-study claims could be verified. That is the week’s useful tension. AI is becoming normal in the marketing stack. At the same time, buyers, audiences, and marketers are becoming more sensitive to synthetic sameness, unverifiable claims, and creative that looks optimized but feels forgettable. Gartner reported on June 9, 2026 that 49% of U.S. consumers agree GenAI has made available content worse, and 57% of Gen Z and millennial consumers agree. Gartner’s read was not merely that people dislike AI. Its survey found that AI is contributing to a more skeptical media environment, which raises the stakes for recognizable, credible, high-quality content. That should make marketers nervous in a useful way. AI did not kill creativity. AI made average creative cheaper. Those are different problems. The easy lesson from this moment is to say, “Use AI less.” That is too simple, and frankly not that useful. AI is already embedded across creative workflows, advertising systems, analytics tools, content operations, search interfaces, customer support, and lead management. Refusing to use it does not make a team more human. It can just make the team slower. The better lesson is that production abundance changes what deserves strategic attention. When production was scarce, the team that could publish consistently had an advantage. When every team can produce plausible drafts, plausible ads, plausible outlines, plausible videos, and plausible campaign variants, plausibility stops being the moat. The market starts rewarding the things automation struggles to manufacture from a prompt alone: taste, restraint, proof, specificity, trust, memory, and a real point of view. Surface has already argued that [visibility is easier and conversion is harder](https://withsurface.com/blog/content-marketing-guide-2026). This week adds a creative layer to that same operating model. AI can help teams win more moments of appearance, but appearance without distinction creates a thin kind of visibility. People may see the work. They may not remember it. They may not believe it. They may not trust it enough to act. That is the AI creative hangover. The first wave made teams feel faster. The second wave is making them ask whether faster work is producing sharper market memory or simply more material for buyers to ignore. The platform direction is clear. Creative production is becoming more automated, more integrated, and more performance-aware. Meta used Cannes to announce a broader set of AI advertising and creator tools. Trade coverage from PPC Land reported that Meta presented AI advertising tools on June 23, 2026, including an end-to-end creative solution in testing, a unified creator marketing hub, and expanded Meta Business Agent capabilities. The same report described “brand memory” as a feature that learns a brand’s identity and tone from existing ads, while marketers can refine brand parameters before using the tool to generate new creative. YouTube also used Cannes to announce new Gemini-supported insights tools for creator marketing and creative campaigns. Google’s announcement described deeper YouTube trend data inside Google Ads Insights Finder, brand pulse metrics, a Content & Creator Insights API, and forthcoming Gemini-supported Demand Gen creative tips that can suggest visuals to improve campaign performance. These are not isolated product updates. They point toward a more automated creative operating system, where platforms help marketers generate, select, translate, activate, and optimize content inside the same environments where media is bought. That is useful. It is also risky. If a platform can learn from your brand’s existing ads, your existing ads become training material for future market expression. If a platform can recommend visual directions, it may help a team move faster, but it may also pull work toward patterns that have already performed. If creator discovery, activation, and paid amplification become more tightly integrated, the line between authentic creator trust and paid performance machinery gets thinner. A team that treats these tools as production shortcuts will get more output. A team that treats them as systems requiring governance may get something more valuable: faster creative that still sounds like a company with a point of view. “Brand memory” is a useful phrase because it gives marketers language for something they should already own. Every company has a memory system. It is just usually messier than anyone wants to admit. The homepage says one thing. The sales deck says another. The highest-spend ad set uses language from a campaign six months old. The product page still describes a feature that changed in Q2. The founder’s podcast line is better than the approved positioning document. The customer story is strong, but buried. The best proof lives in a sales call recording. The comparison page is accurate enough to rank, but too polite to help a buyer decide. AI creative systems do not fix that mess. They can scale it. This is why the next creative operations question is not only “What can we generate?” It is “What source material are we letting the system learn from?” A useful brand memory system should include a few practical pieces. The first is a claim registry: the current claims the company is allowed to make, the proof behind each claim, the caveats that prevent overpromising, and the owner responsible for refreshing the claim. The second is a creative archive that labels old campaigns by audience, product era, message family, performance, and lead quality. The third is a proof library that gives writers, paid media teams, sales, and AI tools the same set of evidence blocks to work from. The fourth is a review system that distinguishes low-risk variations from claims that need product, legal, customer, or executive approval. That may sound operationally boring. It is also the difference between scaling creative and scaling confusion. Teams thinking about [AI visibility reporting without fake precision](https://withsurface.com/blog/ai-visibility-reporting-without-fake-precision) already know the danger of turning messy signals into confident dashboards. The same caution applies to creative. A generated ad variant is not good because the platform can make it. It is good if it attracts the right buyer, sets the right expectation, uses a supportable claim, and connects to a conversion path the business can actually fulfill. Marketers sometimes talk about content fatigue as if the audience is the problem. The audience is too distracted. The buyer is too busy. The feed is too noisy. Search is too fragmented. AI is stealing the click. The committee is too slow. The user does not understand the category. Some of that may be true. It is also possible that a lot of marketing has become easier to make than to care about. Gartner’s content quality finding matters because it names a trust problem at the audience level. If nearly half of surveyed U.S. consumers believe GenAI has made content quality worse, marketers should assume that audiences are developing sharper filters for generic content, even when the content is grammatically clean and visually acceptable. That is not only a consumer-brand issue. B2B buyers have their own version of the same fatigue. They do not need another page that says AI helps teams “work smarter.” They do not need another webinar description about “unlocking efficiency.” They do not need another case study where the company “streamlined workflows” without showing what changed, how long it took, what broke, what improved, and what the customer would do differently next time. Specificity is now a trust signal. A buyer is more likely to believe a company that names the operational reality. For example, “We help marketing teams route demo requests faster” is better than “We transform revenue growth,” but it still leaves too much work for the reader. “We help B2B teams capture, enrich, score, route, and follow up with inbound leads before high-intent demand goes cold” is less elegant, but more memorable because it tells the buyer where the product lives in the system. That is why [inbound lead management](https://withsurface.com/blog/inbound-lead-management) and [inbound marketing automation](https://withsurface.com/blog/inbound-marketing-automation) matter as internal paths from this conversation. Creative distinctiveness does not end at the ad or article. It has to connect to the operational handoff that turns attention into qualified pipeline. The creator conversation at Cannes also deserves a more serious B2B read. Business Insider reported that creators had a major presence at Cannes, with dedicated tracks and spaces for influencer marketing, and cited a projection from the Interactive Advertising Bureau that U.S. creator ad spend would reach $44 billion in 2026. YouTube’s Cannes announcement also framed its Gemini-supported tools around helping brands and agencies maximize creator marketing, including richer creator and audience insights for media planning. A lazy B2B interpretation would be to say, “We need influencers.” Some companies do. Many do not, at least not in the consumer sense. The more useful interpretation is that credible people are becoming more valuable as synthetic content gets cheaper. Those people might be creators. They might be customers. They might be operators. They might be subject matter experts. They might be founders with enough taste and specificity to say something worth hearing. They might be practitioners who can explain the work better than the brand account can. Creator partnerships, in this broader sense, are not decorative reach. They are proof distribution. A founder post can carry conviction that a landing page cannot. A customer walkthrough can answer objections that a polished case study hides. A practitioner interview can make the product category feel real. A partner video can show a workflow in motion. A technical explainer from someone who has actually built the thing can become source material for search, AI answers, sales follow-up, and buyer confidence. That is the creator opportunity for B2B marketers. Not a borrowed face pasted over a campaign, but a credible human layer that helps the market decide what deserves attention. This also connects to [generative AI search optimization](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act). AI systems do not only need more pages. They need credible, clear, sourceable material across the places buyers already trust. A strong creator or practitioner asset can become more than a social post. It can become a proof object. The uncomfortable truth is that AI creative will make dashboards busier before it makes them smarter. More variants create more results to compare. More automated campaigns create more platform-reported wins. More creator activations create more blended influence. More AI search and assistant behavior creates more no-click exposure, later branded search, and unattributed memory. More retargeting and paid capture can make demand look like it was created by the last system that touched it. This is where marketers need measurement discipline. A June 2026 arXiv paper titled _Attributed, But Not Incremental_ argues that paid-attributed conversions can overstate true incremental growth when paid channels overlap with organic demand, brand-driven traffic, or other acquisition channels. The paper proposes using incrementality experiments as causal anchors to correct attribution signals. Another June 2026 paper on integrated marketing attribution argues that retail marketing measurement increasingly needs campaign-level insight without user-level tracking, and proposes combining MMM-informed priors with channel-specific Bayesian attribution models. The tactical lesson is simple enough: attribution tells you where a conversion appeared. It does not automatically tell you whether the campaign created the conversion. This matters more when AI creative increases production volume. A platform can tell you which generated variant received credit. It cannot always tell you whether that variant created demand, harvested demand, cannibalized organic demand, or simply found buyers who were already moving toward purchase. Surface’s [new brand measurement layer](https://withsurface.com/blog/june-21-26-the-new-brand-measurement-layer) is the right connective tissue here. Teams need to separate visibility, citations, recommendations, referrals, branded search, lead quality, and revenue influence. Then they need to label the evidence honestly: observed, inferred, modeled, tested, or unresolved. That last label matters. Unresolved is not failure. It is often the most honest answer in a fragmented system. The practical response to the AI creative hangover is not to slow everything down until the old production model returns. It will not return. The response is to build a creative operating model that treats AI as leverage, not leadership. Start with a **brand memory audit**. Pull the homepage, top product pages, top paid ads, best-performing social posts, sales deck, customer stories, comparison pages, and any creator or partner assets from the last year. Label every major claim as current, stale, unsupported, vague, specific, differentiated, or risky. Look especially hard at claims that AI tools might reuse in future campaigns. Build a **proof library**. Every important claim should have evidence attached to it. That evidence can be customer language, product data, benchmark ranges, screenshots, workflow diagrams, implementation details, security notes, or direct examples. If the claim has no proof, either create the proof or stop scaling the claim. Create **creative review tiers**. Not every AI-generated variation needs a full committee. A headline variant using approved language can move quickly. A new ROI claim, competitor comparison, customer reference, feature promise, compliance statement, or pricing implication should trigger human review. Measure **message quality, not just creative output**. Track which message families create qualified leads, sales-accepted opportunities, stronger meetings, fewer objections, and better pipeline. Surface’s guide to [measuring lead quality](https://withsurface.com/blog/how-to-actually-measure-lead-quality-not-just-lead-volume) is useful here because lead volume will make AI creative look productive long before it proves that the work attracts the right buyer. Add **creator and expert proof** where the market needs human trust. B2B teams do not need to force influencer programs into every category. They do need recognizable humans who can explain the problem, show the work, and carry credibility across channels. Finally, protect **strategic taste**. A good content brief, ad prompt, or creative template should not only tell a tool what to make. It should explain what the work should not do. It should name the buyer’s real situation, the proof required, the internal link path, the tone to avoid, and the reason the piece should exist. This is why [the best content briefs still need human judgment](https://withsurface.com/blog/what-is-a-content-brief). AI can produce structure. Marketers still have to decide what is worth saying. What is known: major advertising and media platforms are adding AI-powered creative, creator, and campaign tools. Meta’s Cannes announcements included AI creative infrastructure, creator hub consolidation, and business agent expansion, while YouTube announced Gemini-supported creator and campaign insight tools. What is known: audience trust is not keeping pace with AI content production. Gartner’s June 2026 survey found that 49% of U.S. consumers believe GenAI has made content quality worse, and its May 2026 shopping survey found consumers are more open to AI tools that help narrow choices than tools that make purchase decisions for them. What is inferred: distinctiveness, specificity, creator trust, and proof become more valuable as production gets cheaper. That is not because AI content is always bad. It is because abundance changes the basis of competition. When many teams can create acceptable work, acceptable work becomes less memorable. What is still unsettled: how much AI creative automation improves true incremental business impact. Platform-reported performance can be useful, but teams still need experiments, modeled lift, lead quality reporting, and sales feedback before claiming that AI-generated creative created demand rather than captured demand that already existed. The next phase of AI marketing will not be won by the team that generates the most. It will be won by the team that knows what should be generated, what should be protected, what should be proved, what should be refreshed, and what should never be automated without review. That sounds less exciting than “AI creative revolution.” It is also closer to the work marketers actually need to do. Build a cleaner brand memory. Use AI to accelerate production, but do not let it decide the company’s taste. Bring credible people closer to the center of the distribution system. Treat proof as a creative input, not a compliance chore. Connect creative performance to lead quality and sales usefulness. Report attribution carefully. Label uncertainty before it turns into board-slide fiction. AI made production cheap. Now marketing has to make the work worth remembering. --- # The Cold Email Playbook for Selling Lead Ops to Law Firms | Surface Labs URL: https://surface.thesurface.network/blog/the-cold-email-playbook-for-selling-lead-ops-to-law-firms If you're an agency, consultant, or Surface partner selling lead operations solutions to law firms, this is the outreach playbook. Three personas, three email sequences, and the LinkedIn touches that warm them up. Legal is one of the best verticals for lead ops because the pain is acute (lost cases = lost revenue), the math is simple (cost per retained client), and the competition is slow (most firms still use generic contact forms). Here's how to reach the right people with the right message. ### Persona 1: Managing Partner / Firm Owner **Who they are:** Decision maker at firms with 5–50 attorneys. They sign checks and care about one thing: cases coming in the door. **Their pain:** They're spending $5K–$15K/month on marketing and don't know what they're getting for it. Attorneys waste time on consultations that go nowhere. They've lost cases to competitors who responded faster — and they know it. **Where to find them:** LinkedIn (title: Managing Partner, Founding Partner, Firm Owner, Principal Attorney), ABA TECHSHOW, Legalweek, State Bar Association events. **The email:** > Subject: Your intake process is losing you casesHi ,I was looking at 's website and noticed your intake process uses a standard contact form. For firms in , that typically means 30–50% of qualified prospects never make it to a consultation.We built an intake system for a similar firm that cut their response time from 6 hours to under 5 minutes and increased consultation bookings by 3x. The whole thing runs on Surface Labs — no dev work needed from your side.Would a 15-minute walkthrough be worth your time this week? **Why this works:** It's specific (references their website), credible (names a comparable result), and low-commitment (15 minutes). Managing partners don't have time for vague pitches — lead with the problem and a proof point. ### Persona 2: Director of Marketing / Business Development **Who they are:** Owns lead gen and intake optimization at mid-size firms (20–100 attorneys). They're the ones who know the funnel is broken but can't fix it alone. **Their pain:** They can't prove marketing ROI because intake is a black box. They report CPL but not cost per retained client. Partners question their spend. The gap between "lead generated" and "case signed" is invisible. **Where to find them:** LinkedIn (title: Director of Marketing, CMO, Business Development Director, Client Development), Legal Marketing Association (LMA) events, legal marketing podcasts. **The email:** > Subject: Connecting your ad spend to signed retainersHi ,I know marketing at a firm like comes with one big question from partners: "What's our cost per signed retainer?"Most legal marketing teams can't answer that because intake is a black box — leads go in, but there's no visibility into what happens between form fill and retained client.We built an intake and qualification system on Surface Labs for a similar firm that gives their marketing team full-funnel attribution: ad click → form fill → qualified lead → consultation → retained. They cut their cost per qualified lead by 60%.Would love to show you the playbook. Free Thursday? **Why this works:** It names the exact political problem they face (partners questioning spend) and offers a solution that makes them a hero (prove ROI). Marketing directors at law firms are an underserved persona — they're often more receptive than partners because they feel the pain daily. ### Persona 3: Legal Ops / IT Director **Who they are:** Manages the technology stack at larger firms (50+ attorneys). They care about systems integration, data flow, and compliance. **Their pain:** Disconnected systems — website forms don't talk to the CRM, the CRM doesn't talk to the case management system. Manual data entry everywhere. Security and compliance concerns with client data. **The email:** > Subject: Eliminating manual intake data entry at Hi ,Quick question: how much time does your team spend manually entering intake data into ?We built an intake automation layer on Surface Labs that captures structured lead data from website forms and pushes it directly into the case management system — no manual entry, no copy-paste errors. It includes qualification scoring, attorney routing, and full audit trails for compliance.We've deployed this for firms on Clio, MyCase, and PracticePanther. Happy to share the technical architecture if that's useful. **Why this works:** It speaks their language (structured data, audit trails, compliance) and names the specific tools they use. Legal ops people don't care about "3x more consultations" — they care about clean data flow and fewer integration headaches. Run this alongside or before email outreach: **Connection request:** "Hi — I work with firms on automating their client intake. Noticed is doing great work in . Would love to connect." **Follow-up (Day 2):** "Thanks for connecting! Quick question — is improving intake speed and lead qualification on your radar for this year? We just helped a \[size\]-attorney firm cut their response time from hours to minutes." **Value add (Day 5):** "Thought you might find this useful — we put together a playbook on how firms are using automated intake to increase consultation bookings by 3x. Happy to send it over if you're interested." The playbook offer is the key. It positions you as an expert sharing value, not a vendor asking for time. When they say "sure, send it," you send the playbook and follow up with: "Did you get a chance to look at it? Happy to walk through how it would work for specifically." Legal outreach performs best Tuesday through Thursday. Avoid Monday (partners are in meetings) and Friday (winding down). Best send time: 7–8 AM local time for partners (they check email before the office opens) and 10–11 AM for marketing and ops directors. Volume: for a focused campaign, target 50 firms per month across all three personas. That's 150 contacts, 3 touches each (email + LinkedIn) = roughly 450 touchpoints per month. At a 3–5% meeting rate, that's 5–8 qualified conversations per month. Surface powers both sides of this equation — it's the product you're selling and the infrastructure you use to reach firms. Use Surface to manage your own outbound lead flow (qualify responses, route meetings, track conversions) while demonstrating the exact capabilities you're offering to law firm clients. --- # The Form Abandonment Problem Nobody Talks About | Surface Labs URL: https://surface.thesurface.network/blog/the-form-abandonment-problem-nobody-talks-about Here's a number most companies don't track: 25–50% of people who start filling out your form don't finish. They type their email, maybe answer the first question, and then leave. On mobile, the abandonment rate is even higher. Those aren't cold visitors. Those are people who were interested enough to start engaging — and something stopped them. A form that was too long. A question that felt too personal too early. A page that loaded slowly. A phone that rang. A child that screamed. Whatever the reason, they left. And at most companies, that data evaporates. The partial submission goes nowhere. No follow-up. No recovery. No acknowledgment that this person existed and showed intent. If you're paying $50–$200 per click to drive traffic to a page with a form, and 30% of the people who start that form abandon it, you're burning 30% of your ad spend on leads that almost converted and got zero follow-up. Industry Average form start-to-completion rate Typical monthly partial submissions (at 500 form starts) Estimated revenue impact of recovering 20% **Law firms** 55–65% (complex intake) 175–225 abandoned At $2,000 average case value: $70K–$90K/year **Real estate** 60–70% 150–200 abandoned At $8,000 average commission: $240K–$320K/year **Insurance** 50–60% (long quote forms) 200–250 abandoned At $1,200 average annual premium: $48K–$60K/year **Home services** 65–75% (simpler forms) 125–175 abandoned At $500 average job: $12K–$17K/year **Healthcare** 60–70% 150–200 abandoned At $300 average patient lifetime value/year: $9K–$12K/year **B2B SaaS** 55–65% 175–225 abandoned At $18,000 average deal: $630K–$810K/year These aren't theoretical numbers. They're the realistic revenue impact of recovering just 20% of abandoned forms — which is achievable with a basic recovery sequence. The reasons are predictable and mostly fixable: **Too many questions too early.** A 15-field form on one page is intimidating. Multi-step forms with 2–3 questions per screen have 30–40% higher completion rates than single-page forms — because each step feels achievable. **Asking for sensitive information before building trust.** Budget, phone number, and company revenue are necessary for qualification — but asking them on the first screen feels invasive. Move them to later steps, after the visitor has invested effort and answered easier questions. **No progress indication.** If the visitor doesn't know how many steps are left, every step feels like it might be followed by five more. A progress bar or "Step 2 of 4" indicator reduces abandonment by setting expectations. **Mobile friction.** Dropdowns that don't work well on mobile. Text fields that require typing long answers on a phone keyboard. Forms that don't resize for small screens. 60%+ of traffic is mobile — if the form isn't optimized for mobile, you're losing the majority of visitors. **Life happened.** The visitor got distracted, their battery died, they got pulled into a meeting. They fully intended to finish but the moment passed. Without recovery, they never come back. Recovery requires one thing: capturing partial data. If the visitor entered their email before abandoning, you can follow up. If they didn't, the opportunity is lost (unless you use cookied visitor identification on return visits). **Recovery email 1 (10–30 minutes after abandonment):** Subject: "You were almost done" Body: Short, direct, helpful. "Looks like you didn't finish your \[request/quote/application\]. Here's a link to pick up where you left off — your answers are saved." Include the link. No upselling, no marketing, no extra content. Just make it easy to finish. **Recovery email 2 (24 hours):** Subject: "Still interested?" Body: Slightly different approach. Offer an alternative: "If the form isn't convenient, reply to this email or call us at \[number\] and we'll complete it together." Some people abandoned because the form was the wrong format — give them a different option. **Recovery email 3 (72 hours):** Subject: "\[Industry-specific value prop\]" Body: Add a reason to come back. For law firms: "The sooner you connect with an attorney, the stronger your case." For insurance: "Rates in your area change frequently — locking in a quote now protects your pricing." For SaaS: "Teams like yours are converting 2x more leads with this setup." Companies implementing the three-email recovery sequence typically see: Industry Recovery rate (abandoned → completed) Why **Law firms** 18–25% High urgency. People who started intake genuinely need legal help. **Insurance** 15–20% Medium urgency. Price comparison motivates completion. **Real estate** 12–18% Variable. Buyers with active timelines recover well; browsers don't. **Home services** 20–28% Highest recovery. The problem (broken AC, leak) doesn't go away. **B2B SaaS** 15–22% Depends on intent level. Demo requests recover better than content downloads. Surface captures partial submissions natively — any field the visitor completes before leaving is saved. Recovery sequences are built into the platform: configurable timing, industry-specific templates, and tracking from abandoned form through to completed submission and beyond. If you're not recovering abandoned forms, you're losing 25–50% of your form-starting visitors with zero follow-up. Surface makes recovery automatic. --- # The Form Is the Most Underinvested Part of the Funnel | Surface Labs URL: https://surface.thesurface.network/blog/the-form-is-the-most-underinvested-part-of-the-funnel Your company spends $50K/month on ads. You have a dedicated team managing creative, targeting, and bid strategy. Your landing pages have been A/B tested 15 times. Your CRM has a full-time admin. Your sales team has engagement tools, call recording, and pipeline analytics. And the form — the single conversion point that sits between all of that investment and actual pipeline — is a default HubSpot form that hasn't been updated since 2023. Four fields. No conditional logic. No qualification. No connection to routing. No scheduling. Just name, email, company, and a submit button. The form is the most underinvested part of the funnel. And it's costing more than most teams realize. Forms get ignored because they feel solved. Every CRM comes with a form builder. It takes 5 minutes to create one. You drop it on a page, it collects submissions, and those submissions appear in the CRM. Done. Except it's not done. That 5-minute form is a dead end — it captures data but doesn't qualify, doesn't route, doesn't respond, and doesn't schedule. Everything that happens after the submit button is handled by other tools, other teams, and other timelines. The form starts the process but contributes nothing to its success. Teams invest in everything around the form — the traffic that drives people to it, the page that houses it, the CRM that receives its data, the reps who follow up on its submissions — but they treat the form itself as a commodity. A checkbox. The bare minimum between "visitor" and "lead." A modern form isn't a data collection field. It's a conversion engine that does five jobs in one interaction. **Capture.** Obviously. But smart capture means adapting to the visitor — showing different questions based on behavior, pre-filling known data from enrichment, and recovering abandoned submissions instead of losing them. **Qualify.** The form should ask the 3–4 questions that determine whether this lead is worth sales' time and how urgently they should be contacted. Budget, timeline, company size, use case. These are the questions the SDR asks on the first call — moved upstream to the point of highest engagement. **Route.** Based on the lead's answers, the form should determine which rep gets the lead. Territory from geography. Deal size from budget. Product match from use case. This decision should happen at form submission, not 30 minutes later in a CRM workflow. **Respond.** The moment routing happens, the lead should get a personalized response — the matched rep's name, a reference to what they asked about, and a clear next step. Not "thanks, we'll be in touch." **Schedule.** The lead should be able to book directly on the matched rep's calendar without leaving the form flow. The commitment that drove them to fill out the form is highest right now — any delay between submission and scheduling reduces the chance of a booked meeting. Most forms do job 1 and nothing else. That's why the form-to-meeting rate is so low at most companies — the form starts the process but the process doesn't continue until a human intervenes. Consider a company getting 200 demo form submissions per month. With a basic form (capture only), the post-form process is manual: SDR reviews, calls to qualify, routes if appropriate, tries to schedule. Typical lead-to-meeting rate: 12%. Meetings booked: 24. With a smart form (capture + qualify + route + respond + schedule), the process is continuous: lead submits, is qualified and routed in real time, gets an instant personalized response, and can book immediately. Typical lead-to-meeting rate: 30%. Meetings booked: 60. Same traffic. Same ad spend. Same landing page. 36 additional meetings per month — from investing in the form. At a $50K/month ad spend, the basic form produces meetings at $2,083 each. The smart form produces meetings at $833 each. The difference — $45K/month in effective savings — comes from a part of the funnel that most teams haven't touched in years. Optimizing the form isn't the same as changing a button color. It's restructuring where qualification, routing, and scheduling happen in your funnel. When you move those functions to the form, you're not making a marginal improvement — you're eliminating entire process steps that currently depend on human speed and attention. The SDR who used to spend 5 minutes qualifying every lead on the phone now gets leads pre-qualified with full context. The manager who used to manually reassign mis-routed leads doesn't need to. The lead who used to wait 4 hours for a follow-up email now books a meeting in 30 seconds. The form is the leverage point. Everything upstream drives people to it. Everything downstream depends on what it captures and triggers. Underinvesting in it means underinvesting in the single point where all your marketing spend converts — or doesn't. Surface was built to make the form do all five jobs — capture, qualify, route, respond, and schedule — in one continuous interaction. It replaces the default CRM form with a conversion engine that turns more of your existing traffic into qualified meetings. If your form is still four fields and a submit button, that's the highest-ROI improvement sitting on your site right now. --- # The GTM Engineer's Guide to Lead Ops | Surface Labs URL: https://surface.thesurface.network/blog/the-gtm-engineer-s-guide-to-lead-ops You just started a new role. The title says GTM Engineer. What you actually inherit is 14 Zaps, a HubSpot instance nobody fully understands, 3 form tools, a routing spreadsheet last updated 8 months ago, and a Slack channel called #lead-issues where sales reps post screenshots of leads that went to the wrong person. Welcome to lead ops. This is the playbook for auditing what you have, understanding why it's broken, and rebuilding it so you're not firefighting lead routing issues every Monday morning. Lead ops sits at the intersection of marketing, sales, and engineering — which means nobody fully owns it. Marketing owns the forms and the ad spend. Once the lead is captured, their job is done. Sales owns the CRM and the pipeline. Everything upstream is someone else's problem. Engineering builds integrations when asked, but they don't own the business logic — they'll connect Typeform to Salesforce, but they won't decide which leads route where or what "qualified" means. So the system was never designed. It was accreted. Marketing picks a form tool. Sales picks a CRM. Someone in ops wires them together with Zapier. When the logic gets complicated, they add more Zaps. When something breaks, they add a workaround. Nobody has a unified view because there was never a unified plan. That's the job you just inherited. The first thing you need to do is audit it. Before you rebuild anything, map what actually exists — not what's documented. Trace every lead source from form submission to CRM entry to first rep outreach. Identify where routing decisions happen (CRM? Zapier? Google Sheet? Someone's head?) and count every tool in the lifecycle. Here's what that audit usually reveals at a $10M–$50M company: What you find Why it exists What it costs you 3–4 different form tools across campaigns Different team members picked different tools at different times Inconsistent data capture, no unified qualification, duplicated leads 8–15 Zapier automations for lead routing Each one solved a specific case; nobody refactored Fragile chain — one Zap breaks, leads pile up unrouted for days Enrichment running on every lead regardless of quality Set-and-forget config from a year ago Burning $2,000–$5,000/month enriching junk leads Round-robin routing with no matching logic Default CRM setting, never customized Wrong reps get wrong leads — territory, seniority, product mismatches No speed-to-lead measurement Nobody instrumented it 4–24 hour average response time that nobody knows about Orphaned integrations from tools you no longer use Nobody decommissioned them Phantom data flows creating duplicates and triggering old workflows If more than 3 of those sound familiar, your lead ops isn't a system. It's an archaeological site. The goal isn't fewer tools for the sake of minimalism. It's a stack where capture, qualification, routing, and response are one connected flow — not 6 tools duct-taped together with middleware. **Capture layer.** One system that powers every form across all lead sources — consistent fields, consistent validation, consistent data output. New campaign means configuring a form, not building a new integration. **Qualification at capture.** The form itself asks the 3–4 questions that determine whether this lead is worth a rep's time. This data exists before the lead ever hits the CRM. **Real-time routing engine.** Routing logic lives in one place — not split across the CRM, Zapier, and a spreadsheet. Evaluates lead attributes at the moment of capture, routes based on territory, deal size, product interest, and rep availability. **Instant response.** Personalized, context-specific response within 60 seconds. Not a generic autoresponder — a message that references what they asked about and who's going to help them. This only works if capture, qualification, and routing are connected upstream. **CRM as system of record — not routing engine.** The CRM receives the lead after capture, qualification, routing, and first response have already happened. Clean, enriched, routed lead with full context. That's what CRMs are good at. Everything upstream is a different job. You can't fix everything at once. Here's the order that produces the fastest ROI: **First: instrument speed-to-lead.** Add timestamps at form submission, CRM arrival, and first rep outreach. A 12-hour average time-to-contact is a compelling case for infrastructure investment. **Second: consolidate routing.** Move all routing logic into one system. Bad routing compounds every other problem — when routing is centralized, every improvement downstream multiplies. **Third: front-load qualification.** Rebuild forms to capture qualification data at the point of entry. Reduces SDR call time, improves routing accuracy, gives reps real context on the first touch. **Fourth: automate instant response.** This is where you see the biggest jump in lead-to-conversation rates — but it only works if the upstream layers are clean. **Fifth: decommission the duct tape.** Kill the orphaned Zaps, cancel the redundant tools, clean up phantom integrations. Maintenance, not transformation — but it reduces your operational surface area. \[IMAGE: Horizontal flow diagram showing the rebuild sequence: Instrument → Consolidate routing → Front-load qualification → Automate response → Decommission duct tape. Each step has a small icon and a one-line impact note beneath it. White background, blue (`#4F6DF5`) accent, flat design.\] Surface was built to be the capture, qualification, routing, and response layer — the piece that sits in front of your CRM and replaces the Zapier chains, the orphaned webhooks, and the routing spreadsheets. If your first month on the job involved more time in Zapier than in your actual go-to-market strategy, that's the problem Surface was built to fix. --- # The Lead Scoring Mistake Every Insurance Agency Makes | Surface Labs URL: https://surface.thesurface.network/blog/the-lead-scoring-mistake-every-insurance-agency-makes Insurance agencies score leads wrong — and it costs them the policies that actually bind. The standard approach: a lead comes in, someone glances at it, and makes a gut call. "Big company? Probably a good lead. Single auto policy? Low priority." Or worse, every lead gets equal treatment — the commercial fleet inquiry sits in the same queue as the renter's insurance quote. The agencies with the highest bind rates don't score on perceived value. They score on likelihood to bind — which is a completely different variable. A commercial liability inquiry from a 200-employee company looks like a big lead. The potential premium is $50K+. Every agent wants it. But commercial policies have long sales cycles, multiple decision-makers, broker competition, and complex underwriting. The bind rate on cold commercial inquiries is typically 5–10%. A personal auto quote for a homeowner who just moved to town looks small. $1,500/year premium. Nobody's excited about it. But the bind rate on auto quotes from new-to-area homeowners is 30–40% — because they need coverage immediately and they're actively shopping. If your agents spend 45 minutes on the commercial lead and 5 minutes on the auto lead, they've optimized for perceived value but not for actual revenue generation. The auto lead was 4–6x more likely to bind. Signal Bind prediction Why **Current coverage status: "switching providers"** High (25–35% bind rate) They already have coverage. They're actively shopping for a better deal. Decision is imminent. **Life event trigger: "just bought a home"** High (30–40% bind rate) They need coverage immediately. Timeline is days, not months. **Current coverage status: "no current coverage"** Medium-high (20–30%) They need coverage. But the urgency depends on why — new driver vs. lapse vs. never had it. **Multiple lines requested** High (25–35%) Someone quoting auto + home + umbrella is serious. They want a relationship, not a single policy. **Quote during business hours on a weekday** Higher than evening/weekend Correlates with active shopping behavior vs. casual browsing. (This varies — test it.) **Completed full risk profile on form** High (35–45%) The more questions they answered, the more committed they are. Form completion depth is the strongest behavioral signal. **Abandoned after basic info only** Low (5–10% even with recovery) Low commitment. May have been doing broad price comparison. ### Layer 1: Form completion depth The simplest and most reliable signal. Someone who completes all risk questions on a multi-step form is fundamentally more committed than someone who enters their email and zip code. Assign scores based on how far the prospect got: - Entered email only: 10 points - Completed basic info (name, email, zip, coverage type): 25 points - Completed risk questions (vehicle info, property details, health status): 50 points - Completed full form including contact preferences: 75 points - Requested a specific agent or scheduled a call: 90 points ### Layer 2: Coverage signals Multi-line requests score higher than single-line. "Switching providers" scores higher than "first-time buyer." Active life events (new home, new car, new baby) score higher than general browsing. ### Layer 3: Enrichment-based fit For commercial lines: company size, industry, and revenue determine whether the prospect is a realistic underwriting fit. A 3-person startup requesting $5M in commercial liability may not be insurable through your carriers. For personal lines: zip code determines rate competitiveness (your carriers may not be competitive in certain areas), and claims history indicates risk level. Score range Lead category Agent action Response SLA 80–100 Hot — high bind probability Senior agent immediate follow-up. Full quote preparation. Under 15 minutes 50–79 Warm — genuine interest, needs nurture Agent follow-up same day. Send rate comparison and next steps. Under 2 hours 25–49 Cool — early stage or low commitment Automated nurture. Educational content about coverage options. Automated response within 1 hour 0–24 Cold — minimal engagement or poor fit No agent time. Automated response only. Re-evaluate if they re-engage. Automated This tiering ensures agent time goes to the leads most likely to bind — not the leads that look the most impressive on paper. After 60 days, pull the data: for each score range, what percentage of leads actually bound a policy? If your 80–100 range is binding at 35% and your 50–79 range is binding at 30%, the model isn't differentiating well enough — refine the scoring weights. If one specific signal (like "switching providers") is dramatically more predictive than the model's overall score suggests, increase its weight. The model should reflect your actual data, not industry assumptions. Run this calibration quarterly. Your carrier mix changes, your market changes, and your lead sources change — the model needs to adapt. Surface builds lead scoring into the quote intake flow — form completion depth, coverage signals, enrichment data, and life event triggers all factor into a score that drives routing and response priority. The scoring model calibrates against actual bind data, so it gets more accurate over time. If your agency treats every lead equally and wonders why your bind rate is stuck at 12%, the scoring model is the fix. Surface was built to make it automatic. --- # The Marketing Ops Playbook Has Changed. Here's the New One. | Surface Labs URL: https://surface.thesurface.network/blog/the-marketing-ops-playbook-has-changed-here-s-the-new-one The marketing ops playbook that worked from 2015 to 2022 was simple: buy a MAP, build workflows, score leads on behavior, and hand MQLs to sales. The stack was HubSpot or Marketo for automation, Salesforce for CRM, and whatever middleware was needed to connect them. The goal was nurture — move leads through a scoring model until they hit a threshold, then pass them over. That playbook is broken. Not because the tools stopped working, but because the market changed around them. **Buyers move faster than nurture sequences.** A B2B buyer in 2025 researches, evaluates, and shortlists vendors in days, not weeks. A 12-touch email nurture sequence that takes 6 weeks to deliver is a relic of a world where buyers needed that much education. Today, the buyer who fills out your demo request form has already read your case studies, checked your pricing, and compared you to two competitors. They don't need nurture. They need a conversation — now. **Lead scoring lost its signal.** Behavioral lead scoring — points for email opens, page visits, content downloads — was designed to identify buying intent. But intent signals have gotten noisier. Bots inflate email opens. Privacy changes reduce tracking accuracy. And the correlation between "downloaded a whitepaper" and "ready to buy" was always weaker than the models assumed. Most teams running lead scoring can't demonstrate that their MQL threshold actually predicts conversion. **The handoff became the bottleneck.** The old playbook focused on getting leads to the handoff — the moment marketing passes the MQL to sales. Everything was optimized for that moment. But the handoff itself — how fast the lead is contacted, by whom, and with what context — was treated as sales' problem. Turns out it's the most important moment in the entire funnel, and nobody owned it. **Cost pressure made efficiency non-optional.** When ad costs rise 20–40% and budgets don't increase proportionally, you can't afford to lose 40% of your leads to slow follow-up and bad routing. Every leaked lead is more expensive than it was three years ago. Dimension Old playbook (2015–2022) New playbook (2025+) **Primary goal** Generate MQLs for sales Generate booked meetings on the right rep's calendar **Core metric** MQL count, CPL Lead-to-meeting rate, cost per meeting booked **Qualification method** Behavioral scoring over time (email opens, page visits, content downloads) Real-time qualification at capture (budget, timeline, company size, use case) **Lead handoff** Batch — leads accumulate score, hit threshold, pass to sales queue Instant — leads are qualified, routed, and contacted within 60 seconds of capture **Routing logic** Round-robin or territory-based assignment in CRM Attribute-based matching — territory, deal size, product interest, rep availability **First response** Rep decides when to follow up after seeing CRM notification Automated personalized response at the moment of routing — before the rep acts **Stack architecture** MAP + CRM + middleware (Zapier) + scheduling tool Lead ops layer + CRM. Fewer tools, fewer handoffs. **Nurture role** Primary conversion mechanism — move leads through a scoring funnel Supporting mechanism — re-engage leads that didn't convert in real time **Optimization focus** Email performance, scoring model calibration, MQL volume Speed-to-lead, routing accuracy, post-capture conversion rate The biggest shift: nurture moved from the center of the playbook to a supporting role. For high-intent leads, the goal is instant conversion — form to meeting in under 60 seconds. Nurture handles the leads that aren't ready yet, not the ones that are. The old stack was built around the MAP. Everything flowed through HubSpot or Marketo — capture, scoring, nurture, handoff. The MAP was the center of gravity. The new stack is built around the lead ops layer. High-intent leads flow through a capture-qualification-routing-response system that sits between the website and the CRM. The MAP still exists for nurture and email, but it's no longer the critical path for lead conversion. The new stack has three components: a lead ops layer (capture, qualify, route, respond, schedule), a CRM (pipeline management, deal tracking, reporting), and a MAP (nurture, lifecycle marketing, email). Each does its job. The lead ops layer is new — and it's the one most teams are missing. Surface is the lead ops layer — the piece the new playbook requires and the old stack didn't have. Capture, qualification, routing, instant response, and scheduling in one system that connects to your existing CRM and MAP. If your marketing ops playbook still centers on MQL volume and email nurture, and your lead-to-meeting rate is below 20%, the playbook is the problem. Surface was built for the new one. --- # The Real Cost of HubSpot Marketing Enterprise | Surface Labs URL: https://surface.thesurface.network/blog/the-real-cost-of-hubspot-marketing-enterprise HubSpot Marketing Hub Enterprise lists at $3,600 per month. That's the number on the pricing page. It's also the smallest number you'll actually pay. The real cost of running HubSpot Marketing Enterprise includes contact tier overage, onboarding fees, add-on tools, and the ops headcount required to maintain it. Most companies on the Enterprise tier spend 2–3x the listed price when you add everything up. This isn't a criticism of HubSpot — it's a pricing reality that's worth understanding before you commit, so you can make an informed decision about whether the full suite is the right investment for your stage and needs. HubSpot Marketing Hub Enterprise starts at $3,600/month ($43,200/year) and includes 10,000 marketing contacts. That's the baseline. HubSpot charges for marketing contacts — anyone you want to include in email sends, ads, or automated workflows. The first 10,000 are included. After that, pricing scales: Contact count Approximate additional monthly cost 10,001 – 25,000 +$200–$500/month 25,001 – 50,000 +$500–$1,200/month 50,001 – 100,000 +$1,200–$2,400/month 100,001 – 250,000 +$2,400–$5,000/month A company with 75,000 marketing contacts on Enterprise is paying roughly $5,000–$6,000/month — not $3,600. And contact counts grow over time as you capture more leads and import more lists. The overage cost creeps up quarterly. HubSpot requires a one-time onboarding fee for Enterprise: $3,500. This covers initial setup guidance but not full implementation. Most companies also need an implementation partner or internal resource to configure workflows, scoring models, integrations, and reporting — which adds $5,000–$25,000 depending on complexity. Enterprise Marketing Hub doesn't include the rest of HubSpot. Most companies running Marketing Enterprise also need: Product Monthly cost Sales Hub (Enterprise) $1,500/month CRM / Operations Hub $800–$2,000/month Service Hub (if needed) $1,200/month Content Hub (if needed) $500/month The "HubSpot suite" for a mid-market company running Marketing Enterprise + Sales Enterprise + Operations typically costs $6,000–$8,000/month in licensing alone. HubSpot Enterprise is configurable, which means it requires someone to configure it. Workflows, lead scoring models, custom properties, integration maintenance, and reporting all need ongoing attention. Most companies at the Enterprise tier either hire a dedicated HubSpot admin ($65K–$95K/year depending on market) or contract a HubSpot Solutions Partner ($2,000–$5,000/month for ongoing management). Without this resource, the platform gradually decays. Workflows break without being noticed. Scoring models drift from actual buying behavior. Integrations fail silently. The more powerful the platform, the more it needs active management. \[IMAGE: A stacked cost breakdown. Base: "$3,600/mo — Enterprise license." Next layer: "+$1,500/mo — contact overage (75K contacts)." Next: "+$3,300/mo — Sales + Ops Hub." Next: "+$6,500/mo — admin/consultant." Top: "Total: ~$15,000/mo ($180K/year)." Clean, minimal, white background, blue (`#4F6DF5`) accent, flat design.\] Cost component Annual range Marketing Hub Enterprise license $43,200 Contact overage (50K+ contacts) $10,000–$30,000 Onboarding + implementation $3,500–$25,000 (one-time, amortized) Sales Hub + Operations Hub $27,600–$42,000 Admin / consulting $24,000–$95,000 **Total annual cost** **$108,000–$235,000** For companies that utilize the full platform — advanced workflows, ABM, multi-touch attribution, custom reporting — this investment can deliver strong ROI. HubSpot Enterprise is a serious platform with serious capabilities. For companies that primarily use email, forms, basic workflows, and reporting — which describes the majority of Enterprise customers — much of this spend is going to features that sit unused. Before committing to HubSpot Enterprise, ask: what's the specific problem we're trying to solve? If the answer is "we need sophisticated multi-channel campaign orchestration, advanced attribution, and ABM at scale" — Enterprise may be the right tier. Evaluate whether your team has the ops resources to actually use the advanced features. If the answer is "leads aren't converting fast enough, routing is broken, and we need better speed-to-lead" — that's a lead ops problem, not a marketing automation tier problem. Upgrading from Professional to Enterprise won't fix it. The forms, routing, and response speed are largely the same across tiers. Surface solves the lead ops problem — capture, qualification, routing, and instant response — at a fraction of the Enterprise tier cost. It works with HubSpot at any tier, including Professional and even Starter. If you're considering Enterprise primarily because you think it'll fix lead conversion, Surface fixes that specific problem without the $100K+ annual commitment. Keep your current HubSpot tier. Add Surface as the capture-to-meeting layer. Spend the difference on pipeline. --- # The State of Marketing AI in 2026 | Surface Labs URL: https://surface.thesurface.network/blog/the-state-of-marketing-ai-in-2026 Average B2B website conversion rates sit between 1.5% and 2.5% in 2026, according to research from First Page Sage and SaaS Hero. Legal services lead at 7.4%, while SaaS and tech typically hover between 1.1% and 3.8%. The top 10% of B2B companies convert at 8–15%. If your conversion rate sits below 3%, you're leaving demos on the table. The gap between average and top performance isn't traffic quality or brand recognition—it's funnel architecture. Most inbound funnels were never designed. They were assembled one tool at a time until the "funnel" became a disconnected mess of form builders, Zapier workflows, CRM automations, and spreadsheets nobody wants to touch. This is the architecture that works in 2026. It's not complicated, but it requires treating the funnel as one connected system instead of independent tools bolted together. The stages haven't changed. What changed is how they connect. Stage Old approach Modern approach **Capture** Static form on a landing page. One format, one offer, one size fits all. Multi-step forms, contextual widgets, exit-intent offers—triggered by visitor behavior and optimized for mobile and desktop. **Qualification** SDR reviews the lead manually after submission, calls to ask qualifying questions. [Qualifying questions asked on the form](https://www.withsurface.com/blog/lead-scoring-model). Lead is scored and segmented at capture. **Enrichment** Runs hours later, after routing. Blocks nothing, informs nothing. Runs in parallel with qualification. Supplements routing decisions without delaying response. **Routing** Round-robin or manual assignment. No matching by territory, deal size, or product interest. [Attribute-based routing](https://www.withsurface.com/blog/lead-distribution)—territory, product, deal size, availability—evaluated in real time. **First response** Rep gets a CRM notification and calls when they see it. Average: 42 minutes to several hours. Automated personalized response within 60 seconds. Rep follows up with full context. **Scheduling** Rep and lead go back and forth over email to find a time. Embedded scheduling connected to routing—lead books on the matched rep's calendar in the same flow. The old funnel has 4–6 handoff gaps between tools. Each gap adds latency, creates a failure point, and loses leads. The modern funnel is one continuous flow—capture through meeting booked, no gaps. Research from Voiso and Chili Piper found that responding within 5 minutes increases conversion rates by up to 100x compared to a 30-minute delay. Most businesses average over 42 hours to first contact. That's not a process problem—it's an architecture problem. Most teams design their funnel top-down: landing page → form → CRM → routing → follow-up. This creates a funnel optimized for capturing leads, not converting them. Design bottom-up instead. Start with the outcome—a meeting booked on the right rep's calendar—and work backward. **What does the rep need to have a productive first conversation?** Company size, budget or deal size, timeline, use case, and the lead's specific area of interest. If the rep doesn't have this, the first call becomes a qualification call instead of a sales conversation. **What routing logic puts the right lead with the right rep?** Territory, product interest, deal size, and real-time availability. If you design routing first, you know exactly what data the form needs to collect. **What capture experience collects the right data without losing the visitor?** A multi-step form with conditional logic that feels like a conversation, not an interrogation. The questions are determined by what routing and reps need downstream. When you design backward, every element serves the outcome. Nothing is captured that isn't used. Nothing is missing that the rep needs. ### Layer 1: Capture Multiple formats—demo request forms, contextual popups, exit-intent offers, embedded scheduling widgets, chatbot handoffs. Each format targets a different intent level. All formats feed into the same processing pipeline. Multi-step forms consistently outperform single-page forms when asking for more than three fields. Research from Venture Harbour and Formstack shows multi-step designs can increase conversions by 86% to 300%. According to a 2026 study from First Page Sage, multi-step forms average 13.85% conversion rates compared to 4.53% for single-page forms. The psychological reason: multi-step forms use the "foot-in-the-door" technique. Once someone answers the first easy question, they're more likely to finish. Capture also means recovering leads who abandon forms before submitting. [25–50% of people who start filling out your form don't finish](https://www.withsurface.com/blog/the-form-abandonment-problem-nobody-talks-about). Most form tools treat this as if it never happened. Tools that capture partial submissions—email addresses entered before the visitor left—can recover 10–15% of those lost leads through automated follow-ups. ### Layer 2: Qualification Every lead is scored or segmented at the moment of capture based on form responses and enrichment data. High-intent leads route to sales immediately. Medium-intent leads enter a fast nurture track. Low-intent leads get automated resources. The most expensive place to qualify a lead is on a phone call with an SDR. The cheapest place is on the form itself. Add 2–4 qualifying questions to your high-intent forms (demo requests, contact forms) that map to your ICP criteria: company size, budget range, timeline, or use case. Qualification isn't about perfection. It's about fast, accurate segmentation so the right leads get the right treatment at the right speed. ### Layer 3: Routing Leads are matched to reps based on attributes—not assigned randomly. The routing engine evaluates territory, deal size, product interest, and rep availability in real time. If no match is found, the lead goes to a default queue with an SLA, not a black hole. A lead that matches the right rep by territory, product interest, deal size, and availability converts at significantly higher rates than a round-robin assignment. Poor routing doesn't just waste the lead—it wastes the ad spend, the landing page effort, and the form optimization that brought them in. According to research cited by LinkedIn and ZoomInfo, dynamic outcome-based routing can boost revenue by up to 28% compared to manual or round-robin methods. ### Layer 4: Response The lead receives a personalized message within 60 seconds of form submission—referencing what they asked about and who's going to help them. This happens automatically, triggered by the routing decision. [Speed-to-lead is the single biggest predictor of conversion](https://www.withsurface.com/blog/slow-followup) after lead quality. Kixie's 2025 research found that responding within 60 seconds can boost conversions by 391%. After 5 minutes, qualification odds drop by 80%. After an hour, the odds fall off a cliff. Automated response doesn't mean generic. The best systems reference form answers, matched rep details, and next steps (like calendar booking links) in the first message. ### Layer 5: Measurement Every stage is instrumented. Speed-to-lead, routing accuracy, lead-to-meeting rate, and cost per meeting booked are tracked continuously—not in a quarterly report. Measurement tells you where the funnel leaks. If 70% of leads are routed correctly but only 30% book meetings, the problem is follow-up or rep behavior, not routing. If 80% of leads are qualified but only 40% route correctly, the problem is routing logic or CRM field mapping. Without measurement, optimization is guesswork. The architecture only works if the layers are connected. If capture lives in Typeform, qualification happens in the CRM, routing runs through Zapier, and response is triggered by a separate email tool, you've rebuilt the old funnel with new labels. The handoff between each layer is where leads leak. According to marketing automation ROI data compiled by Emarsys and Thunderbit, companies earn an average of $5.44 for every $1 invested in automation, and 44% see ROI within six months. The highest returns come from systems that eliminate handoffs entirely. Eliminating handoffs—by running all five layers in one system—is what makes the modern funnel modern. Surface was built to be the connected system—all five layers in one platform. Capture, qualification, routing, response, and measurement running as one continuous flow with no middleware, no sync delays, and no handoff gaps. If you're designing a new funnel or rebuilding an old one, this is the architecture Surface delivers out of the box. The design work is in configuring the rules—not in wiring together the tools. B2B teams running on Surface see 30% more demos within 30 days. That's not because Surface replaces your CRM or your sales team. It's because the architecture removes the gaps that lose leads between form submission and meeting booked. If your conversion rate is below 3%, the opportunity isn't more traffic. It's better [conversion infrastructure](https://www.withsurface.com/blog/b2b-lead-conversion-benchmarks-for-2025). --- # The Storyteller Role in Marketing: KPIs, Craft, and Brand Strategy | Surface Labs URL: https://surface.thesurface.network/blog/the-storyteller-role-in-marketing-kpis-craft-and-brand-strategy A founder says the website feels accurate but forgettable. The product marketer says the case studies prove value, yet sales still has to explain the company from scratch on every call. Someone in the room eventually says the team needs “better storytelling,” which usually means the company has enough facts to be understood and not enough narrative to be remembered. That sentence often begins the modern search for a Storyteller. Brand teams, content teams, communications teams, and product marketing teams all want someone who can make the company feel less interchangeable. They want sharper language, stronger customer proof, clearer executive ideas, better sales stories, and a public voice that can survive the flattening effect of AI-generated content. Then, after asking for voice, specificity, scene, emotional logic, and memory, many companies evaluate the role almost entirely through MBA-style scorecards: traffic, MQLs, pipeline influence, attribution, conversion rate, and quarterly performance. Those metrics matter. A brand story that never reaches the business eventually becomes decoration. Still, a marketing team that hires a Storyteller and only measures the role through performance dashboards has already misunderstood part of the job. Story also belongs to MFA-style creative traditions: pacing, character, tension, voice, image, contradiction, audience intimacy, and the strange detail that makes a sentence sound owned by a real company staffed by real people. The current marketing environment makes that tension more visible. As [B2B marketing has changed over the last few years](https://withsurface.com/blog/how-b2b-marketing-has-changed-in-the-last-3-years), buyers have become harder to interrupt and easier to educate before sales ever enters the conversation. AI search, social feeds, review sites, newsletters, podcasts, and communities now shape a buyer’s understanding long before a demo request. In that environment, the Storyteller role should not be treated as a soft brand flourish. It should become one of the operating roles responsible for making the company easier to understand, verify, retrieve, cite, and choose. ## Summary of the Storyteller role in marketing The Storyteller role has moved from a charming corporate title into a serious marketing and communications function. Companies use the title in different ways. Some hire Storytellers to collect customer stories. Some ask them to shape executive narratives. Some place them inside brand, product marketing, employer brand, customer marketing, journalism, content strategy, or communications. Some use the title loosely for any writer who can turn business information into compelling copy. The trend is not imaginary. The Wall Street Journal reported in late 2025 that companies were increasingly hiring “storytellers,” with major organizations building storytelling teams across blogs, podcasts, case studies, speeches, and other owned media formats. The Guardian summarized the same corporate trend, noting the role’s growth inside technology and brand organizations and pointing to storyteller roles at companies including Google Cloud, Microsoft, Vanta, and Marks & Spencer. Earlier discussion of chief storyteller roles, including the American Association for State and Local History’s 2017 commentary on corporate “Chief Storytellers,” framed the job around gathering stories from employees and customers, then translating them into relevance for the organization. The title has always carried some ambiguity. That ambiguity is part of the problem and part of the opportunity. A Storyteller can be a copywriter, narrative strategist, customer marketer, comms leader, content strategist, speechwriter, editorial lead, social producer, or brand architect depending on the company. The shared responsibility is not merely writing pretty sentences. A serious Storyteller helps a company decide which stories deserve to be told, which proof supports them, which audiences need them, and which channels can carry them without flattening them into generic messaging. ## Why companies suddenly want Storytellers again AI has made acceptable marketing copy easier to create. It has also made acceptable marketing copy less valuable. A marketer can now generate a plausible landing page, rewrite a customer quote, summarize a webinar, draft a LinkedIn post, or create a rough email sequence in minutes. That speed helps teams move, but it also floods the market with language that sounds competent and interchangeable. When buyers see too much interchangeable language, they start looking for signs of real judgment. They notice whether the company understands the problem from the inside. They notice whether the examples feel specific. They notice whether the customer appears as a person with constraints, stakes, and pressure, rather than a persona pasted into a template. They notice whether the company can explain tradeoffs without sanding every claim into a sales-approved blur. A Storyteller becomes valuable because the company needs someone to resist this flattening. The job is not to make everything more emotional. The job is to make the company more legible and more memorable without abandoning proof. A good Storyteller can turn a product capability into a situation, a customer win into a narrative, an executive idea into a public argument, and a content program into something more durable than a pile of search-targeted pages. That durability matters because [weekly marketing intelligence](https://withsurface.com/blog/may-marketing-updates) increasingly shows the same pattern across SEO, AI visibility, and content strategy: teams win when they build useful, citable, well-connected systems of meaning. The Storyteller’s job belongs inside that system. When the role works, it helps the market understand what the company does, why it matters, how it compares, and when someone should trust it. ## The MBA problem: measuring story only through performance metrics Marketing teams have good reasons to measure storytelling through business outcomes. Leaders need to know whether narrative work helps sales, pipeline, conversion, retention, hiring, analyst relations, investor confidence, or customer trust. A Storyteller who rejects measurement entirely will struggle inside any serious business. The problem begins when companies treat downstream metrics as the only legitimate evidence of quality. Pipeline influence can tell a team whether a story traveled through the revenue system. It cannot tell the team whether the story has tension, whether the customer appears with dignity, whether the language sounds alive, or whether the narrative can be remembered and repeated. Traffic can tell a team that people arrived. It cannot tell the team that the company earned a place in the buyer’s memory. This is where marketing often asks for art and then grades only the spreadsheet. The team asks for voice, then evaluates clicks. It asks for narrative, then asks why the first article did not generate meetings. It asks for brand distinction, then edits every surprising sentence into a safer corporate phrasing. Over time, the Storyteller learns to produce work that cannot be criticized in a performance review, which is rarely the same as work that can be remembered by the market. A stronger model keeps the business scorecard and adds a craft scorecard. The business scorecard should track sales reuse, branded search lift, customer proof coverage, assisted conversions, sales-cycle clarity, source citations, analyst or media pickup, executive-message consistency, and conversion quality. The craft scorecard should track specificity, narrative coherence, tension, voice, scene, audience dignity, proof integration, memorability, and the company’s ability to say something in language a competitor would not naturally use. The opposite failure also appears. Some brand teams protect storytelling from business measurement so aggressively that the work becomes aesthetically pleasing and operationally useless. The writing sounds good, the campaign has a mood, the manifesto pleases the internal team, and nobody can explain how the story helps a buyer, a seller, a customer, or a market understand the business more clearly. Craft without business consequence becomes a room full of beautiful fog. A good Storyteller does not need to flatten every sentence into a KPI, but they do need to understand where the story lives in the company’s operating system. Does this narrative help a sales rep answer an objection? Does it help a buyer understand the category? Does it make a product page more credible? Does it turn a case study into proof rather than decoration? Does it help AI systems, journalists, analysts, or customers describe the company accurately? That last question matters more in the retrieval era. Thinking about [AI citations vs. SEO rankings](https://withsurface.com/blog/ai-citations-vs-seo-rankings) gives marketers a useful reminder: visibility no longer belongs only to ranking positions. AI systems may mention a brand, cite a source, recommend a vendor, or absorb a claim into an answer without sending a clean click. Brand story now needs to work across owned pages, third-party sources, customer proof, comparison pages, executive commentary, and sales conversations. A Storyteller who understands only craft may create beautiful fragments. A Storyteller who understands only KPIs may create efficient mush. The role becomes powerful when one person or team can hold both standards at once. ## What a Storyteller actually does inside a marketing team A serious Storyteller should not sit at the end of the content process, waiting to make finished ideas sound nicer. The role should influence strategy before writing begins. The Storyteller should ask what the company needs the market to understand, which proof makes that understanding credible, which customers embody the argument, which objections keep appearing in sales conversations, and which language competitors already own. In brand development, the Storyteller helps define the company’s central narrative. That includes the category problem, the buyer’s pressure, the company’s point of view, the product’s role, the emotional stakes, and the proof that prevents the story from becoming mere aspiration. In content strategy, the Storyteller helps decide which ideas deserve essays, which deserve customer stories, which deserve landing pages, which deserve social posts, and which deserve to be retired because they no longer explain the business. In product marketing, the Storyteller translates capability into meaning. Product teams often describe what the product does. Buyers need to understand why the capability changes their work, what problem it removes, what risk it reduces, and how the product fits into a real operating day. When teams build [generative engine optimization services](https://withsurface.com/blog/generative-engine-optimization-services) or AI visibility content without this translation layer, they often create pages that are technically relevant and emotionally vacant. In sales enablement, the Storyteller turns proof into reusable narrative. A case study should not only say that the customer improved a metric. It should explain what the customer was trying to do, what made the old process painful, what changed after implementation, and why the result matters to a buyer facing a similar decision. Sales teams need that narrative because buyers rarely remember a feature list as clearly as they remember a well-told before-and-after. ## How to measure a Storyteller without killing the story The best measurement model gives storytelling work two scorecards: business impact and narrative quality. The business scorecard proves the work belongs inside a company. The narrative scorecard protects the work from becoming generic performance copy. On the business side, teams can track whether sales reps use the story in calls, whether demo requests reference specific themes, whether branded search grows after a narrative campaign, whether customer stories influence opportunity progression, whether content assists pipeline, whether win-loss interviews mention clearer differentiation, and whether source ecosystems cite the company’s public materials more often. When teams use [lead journey tracking](https://withsurface.com/blog/lead-user-journey), they can also see which stories, pages, and proof assets buyers encountered before conversion. On the craft side, teams should review the work before the market does. Does the piece include a concrete situation? Does it name the actual pressure the reader feels? Does the customer appear as more than a logo? Does the story contain enough tension to move? Does the language sound like this company, or could any competitor publish the same paragraph? Does the piece integrate proof without stopping the narrative dead? Does the reader leave with a sentence, image, or idea worth remembering? This scorecard does not make creative quality mystical. It makes creative quality discussable. Marketers already use editorial standards for grammar, accuracy, and SEO. They can also create standards for specificity, proof, voice, and narrative shape. The goal is not to turn every marketer into a novelist. The goal is to stop pretending that “storytelling” means “copy that hit the target keyword and did not offend legal.” ## Why story matters for AI visibility and retrieval AI search makes story more operational because retrieval systems assemble a brand from available evidence. They read pages, compare sources, summarize claims, identify entities, and look for corroboration across the web. If a company tells a fragmented story, AI systems may produce fragmented answers. If a company gives systems vague claims, stale proof, inconsistent language, and disconnected content, those systems have less reason to treat the company as a clear source. This does not mean marketers should write for machines instead of people. Google’s generative AI search guidance continues to point teams back toward useful, crawlable, people-first content. Thinking through [Google’s generative AI search guidance](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) should push teams toward clearer pages, better evidence, stronger internal links, and more useful answer paths, not toward machine-only rewrites or acronym theater. A Storyteller can help here because retrieval systems and human buyers both need coherence. They both need clean entities, consistent language, proof, context, and examples. They both benefit when a company explains its category clearly and connects related ideas through a logical architecture. The Storyteller should therefore work closely with SEO, product marketing, content strategy, customer marketing, sales, and paid media instead of operating as a decorative brand layer. ## Where the Storyteller role should sit Companies do not need to create a Chief Storyteller title to benefit from the function. Some teams will place the responsibility inside brand. Others will place it inside content, communications, product marketing, founder office, or customer marketing. The org chart matters less than the authority attached to the work. A Storyteller needs access to customers, sales calls, product leaders, executives, support teams, and performance data. Without customer access, the role drifts toward abstraction. Without sales access, the role misses the objections and phrases that actually shape deals. Without product access, the role risks making claims the product cannot support. Without performance data, the role cannot learn which stories travel through the business. The role also needs editorial authority. If every surprising sentence gets softened by committee, the company should not expect a distinct voice. If every customer story gets reduced to a metric and a quote, the company should not expect buyers to remember it. If every executive idea gets converted into safe LinkedIn generalities, the company should not expect thought leadership to lead any thoughts. ## A practical Storyteller scorecard Teams can start with a simple two-column scorecard. Business scorecard Craft scorecard Sales reuse Specificity Assisted pipeline Narrative coherence Branded search movement Voice consistency Customer proof coverage Tension and stakes Source citations and mentions Audience dignity Win-loss language lift Proof integration Lead quality and conversion path Memorability Executive-message consistency Distinctiveness from competitors This model gives leaders a way to ask better questions. Instead of asking only whether a story “worked,” they can ask where it worked, for whom it worked, how it traveled, whether sales used it, whether buyers remembered it, whether AI systems cited it, whether customers recognized themselves in it, and whether the language made the company more distinct. That same operating discipline should extend into conversion infrastructure. A great story can attract a serious buyer, but [inbound lead management](https://withsurface.com/blog/inbound-lead-management) still determines whether that buyer gets qualified, routed, followed up with, and moved toward the right conversation. Story gets weaker when the buyer path after the story breaks. Start by auditing the stories already inside the company. Review sales calls, customer interviews, support tickets, founder notes, product launch docs, case studies, onboarding materials, analyst decks, and high-performing pages. Look for the phrases customers use before the company edits them. Look for the repeated frustrations sales hears. Look for the moments when someone explains the product in a way that makes everyone in the room relax because the thing finally sounds clear. Next, turn those findings into a narrative map. Identify the category story, the customer story, the product story, the proof story, the founder or executive story, and the objection story. Each one should connect to a business purpose and a content surface. The category story may belong on a landing page. The customer story may become a case study, sales slide, and social post. The product story may belong in comparison content and demo scripts. The proof story may need to appear inside ads, AI-visible content, and sales follow-up. Then create the dual scorecard before the work goes live. Decide which business outcomes matter and which craft standards the work must meet. A team that only sets performance goals will usually ship safer, flatter work. A team that only sets creative goals may produce something beautiful and irrelevant. The discipline lives in holding both standards at once. ## The Storyteller role is not soft The Storyteller role sounds soft only when companies misunderstand it. A good Storyteller does not decorate the brand. They help the company decide what is true, what matters, what can be proven, what should be remembered, and how the market should retell it. That work influences SEO, AI visibility, paid media, sales enablement, customer marketing, executive communications, conversion, and retention. The mistake is treating story as either art therapy for the brand or as another performance channel that must justify itself only through last-click math. Story needs business discipline because companies cannot run on vibes. Story needs creative discipline because buyers do not remember dashboards. Marketing teams should stop asking whether storytelling belongs to the MBA or the MFA. The useful Storyteller has to speak both languages. They need enough business judgment to know where the story should move the company and enough creative judgment to make the story worth carrying once it gets there. --- # Thought Leadership Strategy: Why Thought Leadership Is Not a Job Title | Surface Labs URL: https://surface.thesurface.network/blog/thought-leadership-strategy-why-thought-leadership-is-not-a-job "Thought leader" has become one of those titles people use when they want a person to sound important without explaining what they actually do. The executive has a LinkedIn account, the company has a newsletter, someone records a podcast occasionally, and a strategy deck declares that thought leadership will drive awareness — then six months later the team has a small collection of posts and no clear sense of what anyone was meant to learn from them. Thought leadership isn't a seniority marker. It's a strategy for making a company's hard-won knowledge available in public, in a form that helps people think, decide, or work differently. A point of view alone is cheap. The useful part is the evidence, pattern recognition, and customer proximity that let a company say something more helpful than the obvious answer, which makes thought leadership operational: it needs source material, a publishing system, a review process, and a clear relationship to the market conversations the company wants to join. Every company has opinions. Fewer companies have a reliable basis for publishing them. Start with the knowledge that's difficult for an outside writer to reproduce: repeated customer conversations, implementation patterns, data from a product, lessons from sales calls, or a useful way of naming a problem customers already feel. A thought leadership strategy should name its inputs before it names its formats — a team that can't explain where the insight comes from will default to commentary on whatever trend appeared in the feed that week, and end up producing competent summaries no one needs to remember. We've argued that modern content needs to be citable rather than merely publishable. [Our guide to generative AI search optimization](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) applies that idea to pages and citations, but it also works as a test for thought leadership: could a reader trace the claim to an example, a data point, or a defensible line of reasoning? If not, the post may carry a tone of authority without much underneath it. Generic contrarianism is easy. "Everyone is doing content wrong" isn't a strategy, and neither is "AI changes everything," which has about the analytical depth of a weather alert. The strongest thought leadership attaches a point of view to a concrete object — a workflow, a buyer misconception, a reporting mistake, a category that doesn't have a useful name yet. The writer can then show their work: describe the problem, make a claim, explain its limits, and give someone a way to respond. Our [case for lead ops as its own category](https://withsurface.com/blog/why-lead-ops-is-becoming-its-own-category) does this by naming disconnected activities and arguing they belong to one operating problem — the argument can be wrong in places or change as the market changes, and that's fine. Readers trust a company that can name a tension and reason through it more than one that only publishes frictionless certainty. The executive doesn't have to become a full-time writer. They do need a reliable way to get their expertise into the work without approving every comma in a vacuum. Build a lightweight capture process: record a product debrief or sales-call discussion, pull out the specific claims and unresolved questions, let a strategist turn that material into a working thesis, then bring the expert back in for accuracy and the moments where the writing has gotten too smooth to be true. That workflow matters more than a giant content calendar — it prevents a common failure in AI-assisted publishing, where a page checks every structural box while saying nothing that couldn't have come from a generic prompt. We call for editorial judgment inside the operating system in our [content marketing guide](https://withsurface.com/blog/content-marketing-guide-2026), and that judgment belongs here. Tools can identify gaps and build a first pass. People still decide which claim is worth making and where the company should acknowledge uncertainty. ## Build a portfolio, not a procession of executive posts Thought leadership should show up in more than one form: a few durable essays on the company's central ideas, practical guides that translate those ideas into action, original research, customer-informed explainers, and short responses to emerging market questions. Each format has a different job — an essay might help define a category, a guide helps a practitioner solve a specific problem, research supplies evidence for sales and PR. Don't let the portfolio become an excuse for volume. A long essay without a supporting guide becomes brand writing that doesn't travel; a dozen short posts can create activity without a durable record of expertise. [Google's people-first content guidance](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) offers a useful restraint here: create work with a clear audience that adds analysis beyond what's already available. A company doesn't need to weigh in on every topic — it needs to be recognizably helpful in the ones it can earn. Content fails internally when sales sees it as "marketing's post" instead of a useful asset for a real conversation. That happens when a thesis never gets translated into a customer problem, an objection response, or a next step. Bring sales into the strategy early: which misconceptions stall deals, what prospects need to understand before a demo, what proof they're missing. Then let content analytics feed back — which pieces get shared after calls, which pages appear in opportunities, where reps disagree with the marketing thesis. Our approach to content operations makes that loop easier by connecting strategy, review, publishing, and conversion reporting in one place, not to prove that every essay created a deal, but to make the relationship between public expertise and buyer movement visible enough to improve. Thought leadership earns its name when it gives people a thought they can use. Build it from real knowledge, show the evidence, connect it to the company's actual work, and let sales help test whether the idea survives contact with a buyer. --- # The Trust Cost of Generic AI Content: Why More Is Starting to Hurt | Surface Labs URL: https://surface.thesurface.network/blog/trust-cost-generic-ai-content Let's walk through the scenario: your content lead reviews six articles before lunch. Every draft is clean. Each one has a reasonable introduction, a clear set of headings, a few practical recommendations, and a conclusion about the importance of adapting to a rapidly changing market. Nothing is obviously wrong. Nothing is particularly difficult to publish. By the end of the review, the content lead cannot remember which article said what. That is the problem. AI has made it much easier for marketing teams to create acceptable content. A company can generate an outline, summarize competitor pages, draft an article, resize the idea for social, turn it into an email, and produce a webinar description before the afternoon meeting. The work arrives quickly, grammatically intact, and familiar enough that no one has to argue very hard about it. The same qualities that make generic AI content easy to approve can make it difficult to trust or remember. Recent consumer research suggests audiences are beginning to notice the difference. Gartner reported in June 2026 that 49% of surveyed U.S. consumers agree generative AI has made available content quality worse. Among Gen Z and millennial respondents, that figure rose to 57%. Gartner’s earlier March research also found that half of surveyed consumers preferred brands that avoid using generative AI in consumer-facing content. These findings do not prove that audiences reject every AI-assisted asset. They show that perceived content quality and AI usage have become part of the trust calculation. The practical lesson for marketers is not to stop using AI. The lesson is to stop treating publishable as the same thing as valuable. ## Generic AI content creates a trust cost The cost of generic content rarely appears as a dramatic penalty. A reader does not usually submit a form explaining that the article felt structurally competent but emotionally vacant. A prospect does not tell the sales rep that the company’s website used the same phrases as four competitors. A subscriber does not announce that the third vaguely optimistic email about AI transformation was the one that caused them to stop paying attention. They simply move on. The trust cost appears through weaker signals: - People see the content but do not remember the brand. - Search traffic reaches a page but finds no persuasive reason to continue. - AI systems retrieve the page but have little distinctive information to quote. - Buyers arrive at a demo without understanding what the product actually does. - Sales spends time translating broad marketing claims into specific capabilities. - Content engagement looks acceptable while pipeline influence stays flat. - The company publishes more frequently without becoming more authoritative. Surface’s [content marketing guide for 2026](https://withsurface.com/blog/content-marketing-guide-2026) describes a related market shift: visibility has become easier while conversion has become harder. AI can help more teams create enough content to appear competent. It cannot guarantee that the content gives a buyer a reason to believe, remember, or act. The trust cost begins when production grows faster than judgment. AI tools can perform genuinely useful work. They can help a marketer organize research, compare documents, identify missing questions, repurpose interviews, improve a rough structure, summarize technical material, and surface inconsistencies across a site. A small team can use AI to move through repetitive work faster and give more attention to the decisions that require expertise. Problems begin when the team delegates the decisions too. A model can generate five arguments. Someone still needs to decide which argument is true, useful, supportable, and worth associating with the company. A model can imitate the shape of a case study. Someone still needs to find the customer outcome, ask what changed, verify the number, and admit what the engagement did not solve. A model can draft a confident explanation of a market trend. Someone still needs to determine whether the trend exists outside the source material the model was given. The strongest [AI content strategy preserves brand voice](https://withsurface.com/blog/ai-content-strategy-brand-voice) by assigning tools the work that tools handle well while keeping interpretation, experience, taste, and accountability with people. Brand voice is not a collection of adjectives pasted into a prompt. “Conversational, authoritative, warm, intelligent, and practical” describes half of the B2B internet. A recognizable voice comes from what the company notices, which details it chooses, how it handles uncertainty, which claims it refuses to make, and what its people have learned from doing the work. Generic AI content often sounds more certain than its evidence deserves. The sentences connect smoothly. The transitions feel orderly. The advice appears reasonable. That fluency can make weak claims harder to notice because the article does not contain the usual signs of a bad draft. It contains no obvious grammatical collapse or visible confusion. It simply moves from assertion to assertion without giving the reader much reason to believe any of them. Marketers can reduce this risk by treating evidence as a required part of the content architecture. A useful claim should connect to at least one of the following: - Original data - Customer evidence - A direct product example - A clearly attributed external source - An expert interview - A documented observation - A screenshot or workflow - A case study with enough context to interpret the result - A transparent inference labeled as an inference Evidence does more than protect accuracy. It gives the content texture. Compare these two ideas: > AI can improve marketing efficiency by helping teams automate repetitive tasks. > A content team can use AI to compare a twelve-month archive of articles, identify pages with outdated product language, and give an editor a prioritized revision queue. The editor still decides which claims need changing and whether the old page deserves to exist. The first statement is broadly true and almost entirely forgettable. The second gives the reader a workflow they can picture. It defines where the tool helps and where human judgment remains necessary. Specificity is one of the simplest ways to make AI-assisted content feel accountable. The recent Cannes Lions conversation reflected a broader industry correction. Business Insider’s festival recap described human creativity moving back toward the center of the discussion after an earlier wave of AI enthusiasm. Marketers discussed the limits of automation, the risks of over-optimization, and the need for creative work that earns genuine attention. At an Axios event during Cannes, marketing leaders argued that companies can stand out by using AI to amplify human creativity rather than replace it. Axios later reported a related pattern across the festival: leaders emphasized authenticity, community, creator partnerships, and human connection as counterweights to increasingly sanitized AI output. This should not be read as a nostalgic return to a pre-AI creative industry. Platforms, agencies, and brands will keep increasing their use of AI. The correction is about what happens around the tool. As automated content fills more feeds, inboxes, search results, and company sites, audiences can become less impressed by baseline fluency. They may place more value on signs that a real person has taken responsibility for the material: - An opinion with clear reasoning - A useful admission of uncertainty - A specific example - An identifiable source - A customer describing what happened - A practitioner explaining a tradeoff - A brand acknowledging where its product does not fit - A writer choosing an unusual but accurate detail - A recommendation that reflects context rather than a template Humanity in marketing does not require every article to become a personal essay. It requires evidence that someone made choices. Templates are useful. They help teams maintain baseline quality, organize complex assignments, and keep necessary information from disappearing during production. They also make repetition comfortable. A team may decide that every article needs an executive summary, six H2s, a checklist, an FAQ, and a concluding CTA. AI fills the structure cleanly. The editor sees the expected components and approves the page. After twenty publications, the site begins to feel like one article wearing different keywords. A strong [content brief still needs human judgment](https://withsurface.com/blog/what-is-a-content-brief) because the brief should explain the strategic job of the page, not merely its shape. Some questions require a short answer. Others need a scenario, comparison, diagram, case study, opinion, or technical walkthrough. A page should not inherit a format simply because the format is easy to automate. Before drafting, a useful brief should answer: 1. What does the reader actually need to understand or decide? 2. Why does this company have a right to answer the question? 3. What evidence would make the answer credible? 4. What does the company believe that the average search result leaves out? 5. What should the page help the reader do next? 6. Which predictable AI-content habits should the draft avoid? That final question is especially valuable. A brief can explicitly prohibit vague transformation language, unsupported performance claims, repetitive summaries, generic future-of-work conclusions, or examples that have no relationship to the product. Good constraints create room for better thinking. Marketers sometimes respond to generic content by trying to make every article provocative. They search for a “hot take,” reverse the common advice, and hope disagreement creates distinction. This produces its own kind of sameness. Every title claims the industry is wrong. Every introduction announces that the old playbook is dead. Every conclusion reveals that the future belongs to companies willing to rethink everything. Distinctiveness does not need theatrical disagreement. A company can become memorable by being more precise than its competitors. It can explain an overlooked operational problem. It can connect two systems that teams usually report separately. It can publish a useful benchmark with an honest methodology. It can name where a popular recommendation stops working. It can show a real workflow. It can write for an internal operator rather than an imaginary mass audience. The goal is not to sound different for its own sake. The goal is to notice something worth saying. ## Proof, people, and perspective create stronger content Teams trying to improve generic AI content should focus on three layers. ### Proof Proof answers, “Why should the reader believe this?” Add customer evidence, data, sources, examples, product demonstrations, methodology, screenshots, and clearly stated limitations. Avoid turning one customer result into a universal promise. Give readers enough context to understand what the evidence can and cannot support. ### People People answer, “Who has taken responsibility for this idea?” Bring in founders, customers, practitioners, subject matter experts, product leaders, sales teams, support teams, or researchers. Attribute the insight. Preserve useful language from interviews. Let the person’s knowledge alter the article rather than adding a decorative quotation after the draft is complete. ### Perspective Perspective answers, “Why did this company choose to publish this?” State the conclusion. Explain the tradeoff. Connect the topic to the company’s broader view of the market. Admit uncertainty where it exists. A company does not need an opinion on everything, but every major content asset should have a purpose beyond occupying a keyword. These layers also make content more useful in AI search. AI systems need clear statements, attributable evidence, and sourceable passages. Generic summary copy gives them little reason to choose one brand over another. When teams report [AI visibility without fake precision](https://withsurface.com/blog/ai-visibility-reporting-without-fake-precision), they should examine citation quality and source mix alongside raw mentions. A page that earns retrieval because it contains a useful original claim is more strategically valuable than a page that repeats the existing consensus. ## How to audit generic AI content A practical audit can begin with twenty recent pages. Choose a mix of high-traffic articles, recent publications, product-adjacent content, AI-cited pages, and pages used by sales. Review each one against the following criteria. Dimension Weak signal Strong signal Purpose Exists because the keyword was available Solves a defined reader and business problem Evidence Makes broad unsupported claims Uses sources, examples, data, or firsthand knowledge Specificity Relies on category-level language Names workflows, constraints, roles, and outcomes Perspective Summarizes the average answer Makes a useful and supportable argument Humanity Could come from any company Reflects identifiable expertise and judgment Structure Uses a default template Matches the reader’s actual need Conversion path Ends with a generic CTA Leads to the next relevant question or action Freshness Contains undated, generic advice Shows when evidence and recommendations were reviewed Score each page from one to five. More importantly, write one sentence explaining what the page contributes that another competent company could not publish without changing it. Pages without a convincing answer need revision, consolidation, or retirement. The goal is not to punish AI-assisted work. The goal is to identify content that reached publication without earning a distinct purpose. Trust is difficult to reduce to one metric. Teams can still look for evidence. Track whether readers continue into product, comparison, proof, or case-study pages. Measure returning visits, branded search growth, newsletter retention, demo conversion, sales acceptance, and content-assisted opportunities. Review sales calls for repeated language from the content. Ask whether prospects arrive with a clearer understanding of the product or with more confusion. Surface’s framework for [measuring lead quality rather than lead volume](https://withsurface.com/blog/how-to-actually-measure-lead-quality-not-just-lead-volume) applies here. Generic content can create traffic and form submissions. Strong content should improve the quality of the eventual conversation. Qualitative signals also matter: - Sales shares the article without being asked. - Customers say the page captured their problem accurately. - Experts respond to the argument rather than merely liking the post. - Other publishers cite the original idea. - AI answers quote the page’s evidence or reasoning. - Readers use the company’s language when describing the category. - Internal teams rely on the asset to explain the product consistently. These signals do not offer perfect attribution. They show that the content has entered the market’s memory. A good AI workflow should create more space for the work people are uniquely equipped to do. Use the tool to organize interviews, compare old pages, identify unsupported claims, suggest structural alternatives, locate repeated language, repurpose strong source material, and prepare an editor for review. Then use the time saved to speak with customers, verify evidence, refine the argument, build the example, improve the path, and decide whether the page deserves publication. This reflects a broader content operating principle: tools should accelerate the work around judgment without quietly replacing judgment itself. Publishing more can still be useful. A company needs enough content to answer its market’s questions, maintain fresh source material, support sales, create internal paths, and remain visible across search and AI systems. The [content marketing guide for 2026](https://withsurface.com/blog/content-marketing-guide-2026) recommends steady publication rather than rigid perfection or bulk output. Consistency matters. The work still needs to feel like someone cared whether it was true. ## Generic content is cheap. Reader trust is expensive. AI has made it possible to generate an enormous amount of acceptable marketing. Acceptable marketing does not necessarily offend anyone. It also may not persuade anyone. It fills the calendar, satisfies the template, creates a URL, and gives the team another thing to distribute. Over time, the company accumulates a library of pages that explain the category without strengthening the brand. The correction begins with a different production question. Do not only ask whether the draft is ready to publish. Ask what the reader will remember, what evidence supports the claim, whose judgment shaped the piece, and why the company deserves to occupy this part of the conversation. Use AI. Use it aggressively where it helps. Then add the parts the tool cannot responsibly invent: experience, accountability, proof, taste, and a reason to care. Those are becoming the expensive parts of marketing. They are also the parts most likely to compound. --- # How to Turn More Leads Into Sales Calls | Surface Labs URL: https://surface.thesurface.network/blog/turn-leads-into-sales A lead comes in. Someone has to look at it, decide if it's worth sales' time, and route it. Maybe that's a marketing ops person. Maybe it's the rep themselves, spending 10 minutes Googling the company before deciding to call. At 20 leads a day, you can eyeball it. At 200, you can't. And the leads that don't get reviewed fast enough sit in a queue getting colder by the minute while qualified prospects book meetings with your competitors. Most B2B teams do one of three things. They send everything to sales unfiltered, which means reps waste half their day on leads that were never going to close. They build a lead scoring model with manual point values, which works for about a quarter before the ICP changes and nobody recalibrates it. Or they have someone in ops manually review every lead before routing it, which is accurate but slow and doesn't scale. All three break for the same reason. Qualification is happening after the lead is already in the system. The form collects a name and email, dumps it into the CRM, and then your team scrambles to figure out what to do with it. By the time anyone decides this lead is worth talking to, the prospect filled out two other forms somewhere else. It means the lead is qualified before they finish the form. Not after submission. Not in a CRM workflow. During the form fill itself. Here's what's actually happening behind the scenes when a prospect starts filling out a form with real time qualification: They type their work email. Instantly, the system validates the domain. Does this company actually exist? Is it a disposable email provider? That alone filters out a chunk of junk. But it also triggers enrichment. From that one email, you now know the company name, employee count, industry, estimated revenue, HQ location, and tech stack. The prospect hasn't even moved to the next field yet. They answer a few questions. Company size, their role, what they're looking for. The form uses conditional logic, so an enterprise VP sees different follow up questions than an individual contributor at a startup. Each answer narrows the qualification path. By the time they reach the last step, the system has evaluated everything, their form responses, the enrichment data, the email signals, against your ICP criteria. The lead is already scored and classified. Qualified leads see a calendar and book. Disqualified leads get a polite thank you page. Edge cases get flagged for review. The rep never has to decide if this lead is worth calling. That decision was made in real time, with better data than the rep would've had anyway. This only works if there's enough signal to make a real decision. A name and email isn't enough. The email address alone gives you domain validation, company match, and disposable email detection. That's available the second they type it. Real time enrichment kicks in immediately after, pulling employee count, industry, revenue, tech stack, and HQ location within milliseconds. Form responses add company size, role, use case, budget, and timeline as they answer each question. Conditional logic paths tell you which branch they went down and what questions they saw. And behavioral data like pages visited, sessions, and content consumed was already captured before they even started the form. That's 15 to 20 data points available before the prospect clicks submit. Most teams don't have that data assembled until hours after submission, if ever. Once you have the data, the actual qualification decision is the easy part. You define your ICP. Not as a point system with arbitrary values. Just describe what a good customer looks like. Series B+ SaaS companies. 50+ employees. VP or Director level. Evaluating lead ops or marketing automation tools. Every lead gets evaluated against that definition using all the signals above. The output is simple: qualified, disqualified, or needs review. Not a number on a scale of 1 to 100 that nobody knows how to interpret. A clear decision your team can act on. The qualified leads route to the right rep and see the right calendar. Immediately. The disqualified leads don't waste anyone's time. The edge cases get surfaced for a human to make the call, but that's 10 to 15% of leads, not 100%. Your reps stop spending the first 15 minutes of every lead interaction researching whether the lead is worth their time. They open their calendar and every meeting is already with a qualified prospect. They have full context, company data, what the prospect told you, what pages they visited, before the call starts. Marketing stops arguing with sales about lead quality. There's a clear, consistent standard that both teams agreed on. The leads that reach sales matched the ICP. The ones that didn't were filtered before they got there. Ops stops maintaining a scoring model that breaks every time someone changes a form field. The qualification criteria live in one place, described in plain language, and update dynamically when the ICP shifts. Look at your last 50 leads. How many had enough data at the time of submission for someone to make a qualification decision without doing additional research? If the answer is less than half, the problem isn't your qualification process. It's your data collection. Surface Labs runs enrichment, scoring, and routing inside the form. Leads get qualified in real time based on form responses and enriched company data, and they route to the right rep before the prospect leaves the page. If your team is still qualifying leads after they hit the CRM, it's probably worth a look. --- # We Hired Someone to Automate Their Own Job | Surface Labs URL: https://surface.thesurface.network/blog/we-hired-someone-to-automate-their-own-job We hired an AI Content Marketing person. The job description basically said: "Try to make this role obsolete." That sounds insane. Let me explain why it's the smartest hiring decision we've made this year. In the age of AI, the best hires are people who actively try to automate their own work. Not people who protect their territory. Not people who do things the slow way because "that's how it's always been done." People who look at their daily tasks and think: "How much of this can I eliminate so I can focus on the part that actually requires a human brain?" That's exactly what we asked this person to do. Come in, look at our entire content operation — blog posts, social media, email sequences, ad copy, documentation — and figure out how much of it can be automated with AI. Then automate it. Within the first month, they'd automated roughly 60% of the production workflow. First drafts of blog posts, social media calendars, email nurture sequences, ad copy variations — all generated by AI with structured prompts and templates they built. What used to take the team 20 hours a week takes 4. But here's the thing nobody talks about: the remaining 40% became exponentially more valuable. The strategy decisions — what to write, who to write for, what angle to take — can't be automated. The editorial judgment — this draft is good but this section is generic, this example isn't specific enough, this tone is off — can't be automated. The original thinking — identifying a contrarian take, spotting a market trend before competitors, knowing what resonates with our specific audience — definitely can't be automated. By automating the mechanical parts, the person we hired freed themselves to focus entirely on the parts that are uniquely human and high-leverage. They didn't make themselves less valuable. They made themselves more valuable by concentrating their time on the 40% that moves the needle. Most companies hire AI cautiously. They buy tools but tell people to "use them carefully." They add AI to existing workflows without changing the workflows. They treat AI as a supplement, not a restructuring. And most employees are incentivized to protect their territory. If you can automate 60% of someone's job, that person is terrified — because in most companies, "we automated your job" is followed by "so we don't need you anymore." We flipped that. At Surface Labs, automating your own work is rewarded, not punished. If you can do 5x the output in the same hours because you built automations that handle the repetitive parts, you're not expendable — you're the most valuable person in the room. The signal we're looking for in every hire: do they see automation as leverage or as a threat? We're an AI company. If our own team isn't using AI to 10x themselves, we have no business selling it to others. Every person at Surface Labs is expected to actively look for ways to automate their own workflows. Not because we want to eliminate roles — because we want every role to be focused on the 20% of work that actually requires human judgment, creativity, and strategic thinking. The person who can automate 80% of their job and then absolutely crush the remaining 20% is the most dangerous hire in any market. They produce more output, they iterate faster, they adapt to new tools instantly, and they compound improvements over time. We didn't hire someone to automate themselves out of a job. We hired someone to automate themselves into a better one. Would you take a job where the goal is to automate yourself? Why or why not? --- # We Processed 2 Million Leads. Here's Where Most Funnels Break. | Surface Labs URL: https://surface.thesurface.network/blog/we-processed-2-million-leads-here-s-where-most-funnels-break We just audited $10M+ of inbound pipeline across 50+ customer accounts. The leads closing fastest? The ones no one expected. Leads that looked great on paper — big company, senior title, high intent keyword — dragged on for months and went nowhere. Leads that seemed random closed in two weeks with less friction and higher conversion rates. We wanted to know why. So we mapped out what converting leads actually had in common, identified the signals that matter, and found where every funnel was leaking pipeline without knowing it. Here's what we found. Most teams qualify leads on firmographics. Company size, industry, revenue, title. Those matter. But across the accounts we analyzed, the leads that converted fastest shared a different set of signals. Signal Why it matters Speed to booking Leads that booked a meeting within 5 minutes of form fill closed at 3x the rate of leads that booked 24+ hours later. The single strongest predictor. Form completion behavior Leads that filled out every field — including optional ones — converted at nearly double the rate of partial submissions. Intent shows up in effort. Enrichment match to ICP Leads where enrichment data confirmed ICP fit (not just self-reported data) had significantly higher close rates. What the prospect types matters less than what the data says. Correct first routing Leads that reached the right rep on the first assignment closed faster and at higher rates than leads that got reassigned even once. Every handoff adds friction and delay. Multi-session visitors Leads that visited the site 2+ times before converting were more likely to close. They'd already done their research. They were ready. The takeaway: the best leads aren't the ones with the biggest logos. They're the ones that move through your funnel with zero friction. _\[Image: A simple two-column comparison. Left column labeled "What teams think predicts conversion" with items like big company, senior title, high-intent keyword in gray muted text. Right column labeled "What actually predicts conversion" with items like speed to booking, form completion, enrichment ICP match, correct routing in blue bold text. Clean white background, minimal flat design, thin sans-serif type, no icons. 16:9.\]_ Every account had leaks. Most had the same ones. **38% of leads never made it from submission to meeting.** Not because they were bad leads. Because follow-up was too slow, routing sent them to the wrong rep, or the booking flow added a day of friction. The qualified-to-meeting gap was the single biggest leak across nearly every account. **1 in 5 submissions were junk.** Spam, bots, disposable emails, students. They entered the CRM, sat in rep queues, and wasted time before anyone filtered them. Teams without real-time spam filtering lost hours every week to leads that were never real. **Leads routed to the wrong rep took 3x longer to close — when they closed at all.** Misrouting doesn't just delay the first call. It damages the prospect's experience. They get handed off, they repeat themselves, they lose confidence. Most don't say anything. They just go quiet. **Form abandonment was invisible.** Across the accounts we looked at, a significant percentage of people who started a demo request never finished it. Almost none of those teams were capturing partial submissions. Warm leads, gone — and nobody even knew they existed. We packaged what we learned into a simple qualification framework. Not a scoring model. A set of signals your team can evaluate in seconds. For every inbound lead, ask: - **Did enrichment confirm ICP fit?** Not self-reported — actual company data. - **How fast did they book?** Under 5 minutes = high priority. Over 24 hours = the window is closing. - **Did they complete the full form?** Partial submissions signal lower intent. - **Are they a returning visitor?** Multi-session leads convert at higher rates. - **Did they reach the right rep?** If not, fix routing before you fix anything else. You can use this as a team qualification guide. You can drop it into ChatGPT or Claude to qualify leads in seconds. Either way, it gives you a clearer picture of which leads deserve your time — before you waste it. Most teams are optimizing the wrong things. They're tweaking ad targeting and rewriting landing pages while the middle of their funnel silently loses a third of their pipeline. The highest-leverage fix isn't generating better leads. It's making sure the good leads you already have don't die between form fill and meeting booked. Surface Labs was built for exactly this. Real-time enrichment, AI-powered scoring, intelligent routing, spam filtering, and in-form scheduling — one system that closes the gaps where pipeline leaks. If your funnel looks anything like the ones we audited, it's worth a look. --- # We Stopped Asking Leetcode | Surface Labs URL: https://surface.thesurface.network/blog/we-stopped-asking-leetcode We used to ask leetcode in interviews. We stopped. Here's what we do instead. I get why leetcode became the standard. It's objective, it's scalable, and it gives you a number you can compare across candidates. The problem is that it tests one thing — your ability to solve leetcode problems. It doesn't tell you if someone can debug a production issue at 2 AM, design a clean API, or ship a feature end-to-end without hand-holding. We had engineers who crushed our coding rounds and then struggled to scope a real feature. We had candidates who bombed the algorithm question but had shipped products used by thousands of people. The signal-to-noise ratio was garbage. So we killed it. Every engineering candidate at Surface Labs gets a real-world project. Not a toy problem. Not a timed puzzle. A task that mirrors actual work they'd do in the first month on the job. For a backend role, it might be: "Here's a simplified version of our lead routing system. A lead comes in with these attributes. Design the routing logic, handle edge cases, and write the tests." It takes 3–4 hours. We pay candidates for their time. And we review the project the way we'd review a PR — looking at design decisions, trade-offs, code quality, and how they handle ambiguity. For a frontend role, it might be: "Build a small feature in our form builder. Here's the design, here's the API spec. Ship it." We're looking at how they structure components, how they think about state management, and whether the final product actually works — not whether they memorized the optimal solution to "number of islands." For more senior roles, we do a system design session — but with our actual architecture, not a hypothetical "design Twitter." We walk through real problems we're solving and see how they think about the trade-offs we face every day. Three reasons. **It's fair.** Leetcode rewards people who've grinded hundreds of practice problems. Our approach rewards people who've shipped real software. We'd rather hire someone who spent their weekends building a side project than someone who spent them on LeetCode Premium. **It predicts performance.** The tasks we give candidates are close enough to real work that how they perform on the task is a reasonable predictor of how they'll perform on the job. We've been running this process for over a year and the correlation between project quality and on-the-job performance is significantly better than what we saw with leetcode. **It respects the candidate's time — and ours.** The candidate gets to show what they're actually good at. We get to evaluate what actually matters. Nobody walks out feeling like they got rejected because they couldn't implement Dijkstra's algorithm from memory. If your interview process looks nothing like the actual job, you're filtering for the wrong people. You're building a team of great interviewers, not great engineers. I've talked to senior engineers at top companies who can't pass their own company's coding screen. Think about what that means. The process they use to hire would reject them. That's broken. We're not claiming our process is perfect. It takes more effort to run. It's harder to standardize. And it requires the interviewers to actually engage with the candidate's work instead of checking boxes on a rubric. But we're hiring engineers who ship. And that's what matters. What's the worst interview question you've ever been asked? --- # What Changed in B2B Marketing This Month — February 2026 | Surface Labs URL: https://surface.thesurface.network/blog/what-changed-in-b2b-marketing-this-month-february-2026 Every month, we track the shifts that matter for B2B marketing and revenue teams — not the hype cycle, not the funding announcements, but the practical changes that affect how you generate and convert leads. Here's what moved in February 2026. ## The big shift: AI SDRs hit the mainstream — and the backlash started AI SDR tools crossed the adoption threshold this month. Multiple vendors are now running fully autonomous outbound sequences at scale, and the early results are mixed. Response rates to AI-generated outbound have dropped 15–20% quarter over quarter as buyer fatigue sets in. The emails are competent but recognizable — and buyers are learning to spot them. The implication for inbound: as AI outbound gets noisier, inbound leads become more valuable. A person who fills out your demo request form has self-selected in a way that an AI-generated cold email recipient has not. The premium on converting inbound leads well — fast response, smart routing, personalized experience — increases every month that outbound gets more commoditized. **What to do:** Double down on inbound conversion infrastructure. The relative value of every inbound lead is going up as outbound effectiveness goes down. LinkedIn B2B CPCs rose another 8% month-over-month in February, continuing a trend that's now been running for 18 months. Average CPCs for B2B SaaS campaigns on LinkedIn are now $12–$18 for feed ads and $4–$7 for text ads. Sponsored content targeting senior decision-makers can run $25–$40 per click. Google Ads B2B CPCs held relatively steady, with some categories (cybersecurity, HR tech) seeing 5–10% increases. **What to do:** At these prices, post-click conversion is the most leveraged investment you can make. Improving your form-to-meeting rate from 12% to 25% is equivalent to cutting your effective CPL in half — without touching your ad budget. **HubSpot announced AI-powered lead scoring in Marketing Hub Professional.** Previously an Enterprise-only feature, predictive scoring is now available at the $890/month tier. The implementation is solid for behavioral scoring, though it still scores leads after they've entered the CRM — not at the moment of capture. Good for nurture prioritization. Still not a replacement for real-time qualification at the form. **Calendly launched Routing Forms.** Calendly's new feature lets you add qualifying questions before the scheduling step and route to different reps based on answers. It's a meaningful improvement over generic round-robin scheduling. The limitation: it only handles the scheduling step — not capture, CRM sync, enrichment, or instant response. If your leads are dropping off before they reach the scheduling page, this doesn't fix the upstream problem. A question worth asking this month: what percentage of people who start filling out your form don't finish? Most B2B companies track form completion rate (submissions ÷ page visitors) but don't track abandonment rate (people who started the form but didn't submit). The difference matters — a visitor who typed their email and then left is a much higher-intent lead than one who bounced from the page without interacting. Industry average form abandonment rate for B2B demo request forms: 25–35%. Best-in-class: under 15%. If you're not capturing partial submissions and following up, you're losing your most engaged non-converters. The convergence of AI chatbots and AI forms. Several vendors are blurring the line between conversational interfaces and structured forms — adaptive experiences that feel like a conversation but capture structured data. This is the direction lead capture is heading, and it's going to make the traditional flat form feel increasingly outdated. The continued rise of "lead ops" as a category term. We're seeing more job postings, more conference sessions, and more vendor positioning around lead operations as a distinct function. The market is catching up to a problem that's been underserved for a decade. Every trend in this month's update points in the same direction: inbound leads are getting more expensive and more valuable, and the infrastructure that handles them after capture is the highest-leverage investment in the stack. Surface handles the part that these trends make critical — capturing leads with qualifying data, routing them to the right rep instantly, and responding before the lead closes the tab. The trends change monthly. The infrastructure need doesn't. _This is a monthly series. Subscribe to get the next edition — or just check back here the first week of each month._ --- # What Does It Actually Cost You to Book One Meeting? | Surface Labs URL: https://surface.thesurface.network/blog/what-does-it-actually-cost-you-to-book-one-meeting Everyone knows their cost per lead. Almost nobody knows their cost per meeting. That's a problem. Because cost per lead is a vanity metric. You don't close leads. You close deals. And deals start with meetings. The number that actually matters is how much it costs you to get a qualified prospect on a call. Most teams would be uncomfortable if they knew this number. Take everything you spend to generate and convert inbound leads in a month. Not just ad spend. Everything. - Paid ads (Google, LinkedIn, etc.) - Content production (blog posts, case studies, landing pages) - Marketing tools (form tool, enrichment, automation, CRM seats) - People cost (marketing team time spent on lead gen and ops) - Sales time spent on lead research and outreach before the meeting Add it all up. Divide by the number of meetings booked that month. Most B2B teams that run this exercise land somewhere between $300 and $800 per meeting. Some are over $1,000. Because most of the spend happens before the meeting and most leads never become meetings. Say you spend $30,000 a month across ads, tools, and people. You generate 400 leads. Your lead-to-meeting conversion rate is 12%. That's 48 meetings. $30,000 ÷ 48 = **$625 per meeting.** But here's what's hiding inside that number: Where money gets wasted What happens Leads that are spam or junk You paid to acquire them. They took up CRM seats. Reps wasted time on them. Qualified leads that never got a fast response Interested prospects that went cold because your team took too long. Leads routed to the wrong rep Meeting happens but it's a bad fit. Wasted rep time. Often doesn't convert. Leads that abandoned the form Someone started your demo request and left. Warm lead, lost entirely. Rep time spent researching leads 10–15 minutes per lead, times 400 leads. That's 66–100 hours a month. Every one of these inflates your cost per meeting. You're not just paying for the leads that became meetings. You're paying for all the leads that didn't — and all the time your team spent on leads that were never going to convert. You have two levers. Generate more meetings from the same spend, or reduce the spend that gets wasted on leads that never convert. **Filter spam before it hits your CRM.** If 15% of your submissions are junk, you're wasting 15% of everything downstream. Real-time spam filtering during the form fill removes them before they cost you anything. **Enrich leads automatically.** If reps spend 15 minutes researching each lead, that's 100 hours a month at 400 leads. Real-time enrichment eliminates that entirely. The cost saving alone is significant. **Qualify and score in real time.** If reps are spending time on leads that don't fit your ICP, that's wasted sales capacity. Automatic scoring means reps only work qualified leads. The rest get filtered or nurtured without burning rep time. **Route correctly the first time.** A misrouted lead often means a wasted meeting. The rep isn't the right fit, the conversation goes nowhere, and the prospect doesn't come back. Routing based on enrichment data instead of round robin means more meetings actually convert. **Let prospects book inside the form.** Every lead that submits a form and then never responds to the follow-up email is a meeting that should've happened. If the calendar shows up in the form, the prospect books on the spot. Your submission-to-meeting rate jumps. Cost per meeting drops. **Capture drop-offs.** Form abandonment is invisible spend. You paid to get that person to your form. They started it. They left. If you capture partial submissions and follow up, some of them come back. That's meetings from leads you already paid for. Teams that optimize the full capture-to-meeting flow typically see cost per meeting drop by 40–60%. Not from spending less. From converting more of what they already have. If your cost per meeting is over $500, there's almost certainly money being wasted on junk leads, slow follow-up, bad routing, or a booking flow that adds unnecessary friction. Surface Labs is built to reduce cost per meeting by handling the full chain in one system. Capture, filtering, enrichment, scoring, routing, and scheduling. Every step that wastes time or loses leads gets tightened. If you've never calculated your real cost per meeting, start there. The number will tell you what to fix first. --- # What Happens When Every Company Has an AI Chatbot? | Surface Labs URL: https://surface.thesurface.network/blog/what-happens-when-every-company-has-an-ai-chatbot Two years ago, adding an AI chatbot to your website was a differentiator. Visitors were impressed. Conversations felt futuristic. Leads came in. Now everyone has one. Drift, Intercom, HubSpot, Qualified, Chili Piper — they've all shipped AI chat. So have thousands of startups. Your competitor has one. Your competitor's competitor has one. The company your prospect visited before yours has one. When everyone has a chatbot, nobody has an advantage. So what actually happens next? The first wave of AI chatbots worked because they were novel. A visitor could ask a question and get a real answer instead of digging through a help center. That was genuinely better. But the novelty is gone. And what's left is a set of problems that most chatbot vendors aren't talking about. **Visitors are ignoring them.** Chat fatigue is real. That popup in the bottom right corner? Most B2B buyers have trained themselves to close it immediately. The engagement rates that impressed in 2024 are declining fast. **They qualify poorly.** Most AI chatbots are good at answering questions. They're bad at qualifying leads. They'll have a 15-message conversation with someone who was never going to buy, then pass them to sales as a "hot lead." The rep wastes 20 minutes discovering what a two-field form would've told them in seconds. **They can't replace the form.** This is the big one. Chatbots were supposed to kill forms. They didn't. Because forms collect structured data — company size, use case, budget, timeline — in a predictable format that feeds directly into scoring, routing, and CRM workflows. A freeform chat conversation doesn't. Someone has to read it, interpret it, and manually enter the data. That doesn't scale. **They're expensive.** Chili Piper's Chat AI is $20,000/year. Qualified starts at six figures. Drift was similar before they got acquired. For most B2B teams, the ROI doesn't justify it when you look at actual meetings booked — not conversations started. The chatbot debate is a distraction. Chat vs. form vs. hybrid — it doesn't matter nearly as much as what happens after the visitor engages. The companies converting the most inbound leads aren't winning because of their chat widget. They're winning because their lead ops infrastructure is fast. What matters Why Real-time enrichment The lead is complete before a rep ever sees it. No research. No delay. Instant qualification AI scores against your ICP the moment data comes in — not after a rep reads a chat transcript. Smart routing The lead reaches the right rep based on real data, not whoever's "online" in the chat tool. In-form scheduling The prospect books before they leave. No follow-up. No waiting. No chat handoff to a rep who then sends a booking link. A great chatbot with broken lead ops still loses pipeline. A simple form with great lead ops books meetings. _\[Image: A split comparison. Left side shows a chat widget with a long winding conversation thread, ending with "Let me connect you with someone" and a small clock icon showing delay. Right side shows a clean short form with enrichment data appearing in real time and a calendar at the bottom with a time slot selected. Left labeled "15 messages to maybe book" in gray. Right labeled "30 seconds to booked" in blue. Clean white background, minimal flat design, thin lines, no gradients. 16:9.\]_ The companies that win inbound in 2026 won't be the ones with the fanciest AI chatbot. They'll be the ones where a qualified prospect can go from "I'm interested" to "I'm booked on the right rep's calendar" in under 60 seconds. That requires enrichment, qualification, routing, and scheduling working together in real time. Not a chat widget hoping to collect the same information a well-built form captures in four fields. Surface Labs doesn't compete with chatbots. It makes the infrastructure behind them — or behind your forms — actually work. Real-time enrichment the moment someone types their email. AI scoring against your ICP. Routing based on real data. Scheduling embedded in the form so the prospect books on the spot. Whether you use a chatbot, a form, or both — the lead ops layer underneath is what determines whether that lead becomes a meeting or disappears. If you're evaluating an AI chatbot, ask a different question first: what happens to the lead after the conversation? If the answer involves manual steps, delays, or a booking link in a follow-up email, the chatbot isn't your problem. Your infrastructure is. --- # What Is a Content Brief, and Why the Best Briefs Still Need Human Judgment? | Surface Labs URL: https://surface.thesurface.network/blog/what-is-a-content-brief ## Summary of Content Briefs A content brief is the strategic document that tells a writer, editor, subject matter expert, and reviewer what a page is supposed to do. It usually includes the target keyword, intended audience, search intent, recommended structure, internal links, source requirements, CTA, and review notes. That definition is useful, but incomplete. The best content briefs do not simply tell a writer what headings to use. They explain why the page should exist. They help the team understand the reader’s problem, the business priority, the proof needed, the internal link path, and the point of view that should make the page feel like it came from a specific company rather than a template. A weak content brief produces compliance. A strong content brief produces judgment. For B2B SaaS and technical product teams, that difference matters. Content is rarely just “an article.” It is a way to clarify a product category, answer a sales objection, support a launch, educate a buyer, create AI-visible source material, and move a reader toward a more useful next step. A content brief should protect that purpose before the draft begins. ## What Is a Content Brief? A content brief is a page-level plan for a piece of content. It gives the writer enough context to understand the assignment and gives the editor enough structure to judge whether the final piece did the job. A basic content brief usually includes: - Target keyword - Working title - Search intent - Reader or audience - Recommended outline - Internal links - External sources - Metadata - CTA - Review requirements A stronger content brief goes further. It explains the strategic job of the page. It defines what the reader already knows, what they need to understand next, and why the company has a right to answer the question. It gives the writer a point of view, not just a set of SEO requirements. That is the part many teams miss. A content brief is not only a production artifact. It is a decision record. It captures the strategic thinking that should happen before anyone starts drafting. ## Why Content Briefs Matter for B2B Content Teams B2B content is usually reviewed by too many people and understood by too few. A content manager may own the calendar. A GTM lead may care about pipeline. A product marketer may care about positioning. A founder may care about the point of view. A sales lead may care about objections. A technical reviewer may care about accuracy. A writer may only see the assignment after all of those priorities have already been half-discussed in Slack, calls, docs, and half-remembered planning sessions. A good brief brings those priorities into one place. It helps prevent the most common content failures: - The article ranks but does not help the business. - The article explains the topic but says nothing specific. - The article uses the right keyword but targets the wrong reader. - The article sounds polished but not like the company. - The article links nowhere useful. - The article creates more review confusion than clarity. - The article answers a question the buyer is not actually asking. - The article ships because it was on the calendar, not because it deserved to exist. For content managers and GTM leads, the brief is where alignment becomes operational. It turns “we should write something about this” into “this page has a reader, purpose, argument, structure, and next step.” Content briefs have become easier to generate. AI tools and SEO platforms can pull keywords, compare ranking pages, create outlines, suggest headings, and recommend related questions. That is useful work. It can save hours. It can also make bad strategy look organized. A tool can tell you what other pages include. It cannot reliably tell you whether those pages are good. It can recommend a word count. It cannot know whether the reader needs 600 words or 2,000. It can suggest internal links. It cannot always know which link creates the most useful buyer path. It can outline the average structure of a search result. It cannot decide whether your company should follow the average or challenge it. That is why the best briefs still need human judgment. A human has to decide: - Whether the keyword deserves a page - Whether the search intent is being interpreted correctly - Whether the content should be a blog, landing page, glossary page, comparison page, or product page - Whether the company has a meaningful point of view - Whether the page supports a broader content hub - Whether the piece should educate, compare, convert, or enable sales - Whether the draft should be concise or expansive - Whether the page needs product proof, customer evidence, expert commentary, or technical detail A template can keep a team consistent. Judgment keeps the work from becoming generic. A template defines a shape. A brief defines a decision. A template might say: - Include an H1. - Add a summary section. - Use the keyword in one H2. - Include three internal links. - Add a CTA. - Include FAQs. That can be useful. But it does not answer the deeper questions. Why this topic? Why now? Why this reader? Why this angle? Why this internal link path? Why should a buyer trust this page over the dozen other pages saying roughly the same thing? A brief should include the template, but it should not stop there. The danger of over-templatized content is that every page starts to behave the same way. A team may feel efficient because every article has the right parts, but the site starts to lose texture. The posts become structurally correct and strategically dull. That is especially risky when AI is involved. AI is very good at filling a known shape. It is less reliable at deciding whether the shape is right. A good content operation uses templates for baseline quality and human judgment for strategic quality. Both matter. They should not be confused. ## A Practical Content Brief Structure Below is a content brief structure that works for B2B SaaS, technical products, and content teams trying to balance SEO, AI visibility, brand voice, and GTM usefulness. ### Working Title Write the clearest current version of the title. It can change later. Example: `What Is a Content Brief, and Why the Best Briefs Still Need Human Judgment?` ### Primary Keyword Name the main keyword or query target. Example: `what is a content brief` ### Secondary Keywords and Related Phrases Include related terms only when they help the piece answer the reader’s question. Example: - content brief template - SEO content brief - content brief example - content strategy brief - AI content brief Do not turn this section into a keyword-stuffing list. Secondary keywords should clarify coverage, not dictate the prose. ### Reader Define the reader in plain language. Example: `B2B content managers and GTM leads who manage writers, agencies, AI workflows, or product reviewers.` The reader should feel real enough that the writer can make decisions for them. ### Reader Intent Explain what the reader is trying to understand or decide. Example: `The reader wants to know what a content brief should include and why a brief generated from an SEO tool is not enough to create strong content.` This section should separate curiosity from buying intent. A reader asking “what is a content brief?” may be early in their process. A reader asking “content brief template for B2B SaaS” may be more operational. A reader asking “content strategy agency for technical products” may be much closer to a vendor decision. ### Strategic Job of the Page Name the business purpose. Example: `Show that strong content operations require strategy, editorial judgment, internal linking, and production discipline, not only keyword research or AI-assisted drafting.` This is one of the most important sections. It protects the page from becoming informational but commercially irrelevant. ### Page Type Choose the format. Example: `Educational thought leadership post with a practical template section.` Other possible page types might include: - Glossary entry - Product-led explainer - Comparison article - Tactical how-to guide - Landing page - Sales enablement page - Customer story - Research report - Content hub pillar Different page types require different structures. A brief should make that explicit. ### Search and AI Visibility Angle Explain what the page should be easy to retrieve, understand, or cite for. Example: `The page should clearly answer what a content brief is, what it includes, why human judgment matters, and how B2B teams should use briefs in AI-assisted workflows.` This matters because content now has to work across more than classic search results. A page may appear in Google, AI answers, sales follow-ups, internal enablement, newsletters, and social posts. The brief should clarify what the page needs to be known for. ### Point of View Write the opinion the page should defend. Example: `A content brief is not just a structure for a writer. It is a decision record for the content strategy.` This section is where good briefs separate themselves from generic SEO instructions. The point of view does not need to be contrarian for its own sake. It does need to be specific enough that the article has a reason to exist. ### What the Page Should Not Do Add constraints. Example: - Do not present briefs as a magic solution. - Do not over-focus on word count. - Do not imply AI-generated briefs are useless. - Do not turn the piece into a generic checklist with no POV. - Do not make the CTA feel heavier than the reader’s intent. Negative instructions are useful because they prevent predictable failure modes. ### Required Internal Links List internal links with natural anchor text. Example: - [content marketing strategy](https://withsurface.com/blog/content-marketing-strategy-the-quality-vs-volume-trap-in-ai-era) - [marketing operations strategy](https://withsurface.com/blog/marketing-operations-strategy-content-system) - [content marketing guide for 2026](https://withsurface.com/blog/content-marketing-guide-2026) - [generative AI search optimization](https://withsurface.com/blog/generative-ai-search-optimization-new-google-guidance-act) Internal links should not be treated as decorative SEO requirements. They should create a useful path for the reader. A person reading about content briefs may logically want to understand content operations, AI-assisted publishing, or broader content strategy. The links should serve that movement. ### Evidence and Source Requirements Define what needs proof. Example: - Use existing Surface content on content operations and AI-era publishing. - Include B2B SaaS and technical product examples. - Make claims about AI and search carefully. - Avoid unsupported claims about ranking guarantees. - Use examples that reflect real content workflows. A brief should tell the writer where evidence is needed. It should also tell them where not to overclaim. ### Outline Draft the structure. Example: - Content Brief Summary - What Is a Content Brief? - Why Content Briefs Matter for B2B Content Teams - Why the Best Briefs Still Need Human Judgment - The Difference Between a Template and a Brief - A Practical Content Brief Structure - How to Use AI in a Content Brief Without Flattening the Voice - What Editors Should Review Before Publishing - Where Content Briefs Fit in Content Operations - What to Do Next - Final Thought on Content Briefs The outline should move the reader from definition to judgment to application. It should not simply mirror the top-ranking pages. ### Human POV Layer Name what the writer or editor should add that a template cannot. Example: - A sharper argument about briefs as strategic decision records - A realistic B2B SaaS example - A warning against template addiction - A practical editorial standard for reviewing briefs - A clear distinction between automation and judgment This section is especially useful when AI is involved. It gives the draft a point of view before the draft begins. ### CTA or Next Step Define the reader’s next movement. Example: `Lightly point readers toward a content operations approach that turns briefs into a repeatable publishing, linking, editing, and revision system.` Not every blog needs a heavy sales CTA. Some should simply create confidence and point the reader toward the next useful idea. ### Reviewer Notes Name who should approve the page. Example: - Content strategist - SEO/editorial reviewer - Product marketing reviewer if product claims are included - Technical reviewer if architecture, integrations, or product functionality are discussed Reviewer notes prevent late-stage confusion. They also keep the wrong people from rewriting the piece after the strategy has already been set. ## How to Use AI in a Content Brief Without Flattening the Voice AI can help create a content brief, but it should not own the brief. Useful AI-assisted steps include: - Summarizing search results - Pulling related questions - Identifying possible internal links - Comparing competitor structures - Turning a call transcript into source notes - Creating first-pass FAQ candidates - Checking whether the outline answers the query - Suggesting places where examples or proof may be needed The human editor should then interpret the output. Which questions matter? Which are noise? Which competitor pages are ranking because they are strong, and which are ranking because the category is underdeveloped? What does the company know that the search results do not? What does the reader need that the keyword tool cannot see? That interpretation layer is where brand voice begins. Brand voice is not only sentence style. It is the shape of the company’s judgment. A company that understands its market will make different decisions about what to emphasize, what to skip, where to admit complexity, and when to stop explaining. A content brief should make editorial review easier, not unnecessary. Before publishing, editors should check the draft against the brief and against the reader’s likely experience. A practical review should ask: - Does the page answer the primary question quickly enough? - Does the page add a point of view, or only summarize common knowledge? - Does the structure match the intent? - Are the internal links useful next steps? - Does the page connect to a broader content system? - Are any claims unsupported or overstated? - Does the CTA make sense for the reader’s stage? - Could a sales person send this page to a prospect? - Could an AI system understand what the page is confidently about? - Does the page sound like the company, or like a paraphrase of the first five ranking pages? That last question matters more than many teams admit. A content brief can prevent chaos, but it can also produce sameness. The editor has to protect the page from both. ## Where Content Briefs Fit in Content Operations A brief is one part of a larger content operation. It should sit between strategy and production. A healthy process looks like this: - Strategy defines the topics, audiences, intent layers, and business priorities. - The brief translates that strategy into a page-level plan. - The writer turns the plan into a draft. - The human POV layer adds specificity, examples, argument, and voice. - The editor checks quality, sources, structure, and internal links. - The publishing workflow handles metadata, CMS formatting, schema, images, and QA. - Measurement shows whether the page earned visibility, engagement, movement, or sales usefulness. - Refreshes keep the page accurate and connected. That system matters because content teams often overvalue the moment of drafting. Drafting is important, but the page succeeds or fails based on the decisions around the draft. The brief is where many of those decisions should become visible. Thinking about [marketing operations strategy](https://withsurface.com/blog/marketing-operations-strategy-content-system) helps make the point operational. Before hiring more writers or generating more drafts, teams should fix the system that decides what gets written, how it gets reviewed, where it goes, and how it supports conversion. If your team already uses briefs, audit five recent ones. Do they explain the strategic job of the page, or do they mostly list keywords and headings? Do they help the writer understand the reader? Do they include internal links that create a path through the site? Do they name the evidence needed? Do they define the human POV? If your team does not use briefs, start with a lightweight version. Do not overbuild the template. A useful one-page brief is better than a perfect document no one completes. A strong minimum brief should include: - Primary keyword - Reader - Intent - Strategic job - Point of view - Internal links - Evidence requirements - Outline - CTA - Reviewer Once that becomes normal, add more sophistication where it helps. ## Final Thought on Content Briefs A content brief is not a formality. It is the point where strategy becomes operational. The best briefs protect writers from guessing, editors from rewriting the assignment after the fact, product teams from vague review cycles, and GTM leads from content that earns traffic without helping the business. AI can help create better briefs when humans interpret the research, decide the angle, and protect the voice. Treat the brief as a decision record. The page will be better because the team made the hard decisions before the draft started. --- # What Is a Content Hub? A Content Strategy and SEO Guide for AI Search | Surface Labs URL: https://surface.thesurface.network/blog/what-is-a-content-hub-a-content-strategy-and-seo-guide-for-ai ## What Is a Content Hub? A Content Strategy and SEO Guide for AI Search A content hub is a connected group of pages that helps a reader understand a subject from more than one angle: a central page, supporting articles, useful links between them, and a clear relationship to the company's expertise or product. A good hub gives readers a deliberate path through a problem instead of a pile of separately-optimized posts. That distinction matters because content teams have spent years producing pages that work in isolation and fail together. Each article gets a target keyword and a passable outline, yet the site still leaves readers unsure what the company actually knows or where to go next. Search systems run into the same blur — they can index every page while getting an unclear picture of the business behind them. Teams often start hub planning in the CMS: create a category, choose an icon, ask writers to fill it in. That's navigation, not strategy. Start instead with a buyer problem that deserves sustained explanation — AI visibility measurement, lead operations, content refreshes, a technical product category. The problem should be large enough to generate multiple real questions, but focused enough that a reader understands why those questions belong together. A lead operations hub, for instance, might include a category overview, a guide to capture, a page on qualification design, an explanation of routing, an implementation guide, a comparison page, and customer proof. Each page stands on its own; together they tell a more complete story about what happens after someone raises their hand. Our [argument for lead ops as its own category](https://withsurface.com/blog/why-lead-ops-is-becoming-its-own-category) works for exactly this reason — it names the shared operating problem underneath forms, enrichment, scoring, routing, and response, tactics usually managed as disconnected tools. A useful hub shows those relationships instead of treating each tactic as its own island. ## Hub pages should orient, not summarize everything badly The central hub page has one job: help a reader understand the topic, see the major branches, and choose a useful next page. It doesn't need to repeat every detail from every supporting article — pages that try usually end up bloated and hard to update. Use the hub to define the topic cleanly, explain why it matters, introduce the subtopics, and make the reading path visible, then link outward with descriptive anchors so a reader knows whether the next click leads to a beginner guide, a checklist, or a case study. [Google's link best practices](https://developers.google.com/search/docs/crawling-indexing/links-crawlable) make the same point at the page level: each link is a small sentence about the relationship between two pages, and weak, repetitive anchors make the whole structure harder to read. One of the easiest hub mistakes is filling it with only educational pages. Informational content earns discovery and shows how a company thinks, but buyers don't stay informational forever. Every mature hub needs room for several kinds of intent: definitional pages for early questions, practical guides for teams doing the work, comparison pages for people narrowing options, and proof pages or product detail for buyers who need confidence before acting. We describe the underlying principle in our [content marketing guide](https://withsurface.com/blog/content-marketing-guide-2026): a strong content system connects SEO, AI visibility, sales enablement, and conversion paths, and the hub is where that connection becomes visible. It shouldn't force a reader into a demo, but it shouldn't make them hunt through the footer to find out whether we can help, either. AI search has encouraged a new round of thin content — teams see prompt fan-out, generate an article for every phrasing, and hope a system rewards the coverage. But AI systems may retrieve a supporting page instead of the hub, cite an explanation, or surface a page a reader would never have found through navigation, which makes the architecture around each page more important, not less. Each page should state its purpose clearly, offer a direct answer, and connect naturally to the surrounding cluster — a narrow metric page pointing back to the broader framework, a vendor category page pointing toward evaluation content. [Google's guidance on AI features](https://developers.google.com/search/docs/appearance/ai-features) stays refreshingly unromantic here: generative search relies on core Search foundations, not a secret AI-only site. We described this idea as "interconnected islands" in our [guide to generative engine optimization services](https://withsurface.com/blog/generative-engine-optimization-services) — a good image as long as teams remember the bridges need maintenance, since internal links decay and old guides go stale. Hub diagrams look neat because the boxes line up. Real teams have limited subject-matter-expert time, incomplete proof, and a CMS that can make updates annoying, so the plan should account for that rather than fight it. Begin with the smallest durable set: one clear central page, three to five supporting pages answering genuinely different questions, a proof or conversion page, and a review rhythm. Avoid publishing placeholder articles just to complete the diagram — [Google's people-first content guidance](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) gives a fair test: does the page add useful, original information and leave a reader feeling they learned enough for their goal? A hub can't pass that test through structure alone. Traffic tells you whether people arrive. A hub needs a second measure: do they move? Watch which entry pages attract the right audience, which links readers actually follow, and which subtopics generate interest without any path forward. AI visibility belongs in the same review — prompt coverage, citations, source pages, and the difference between a brand being mentioned and being recommended, treated as directional evidence rather than a verdict. Our content operations approach connects strategy, review, and analytics for exactly this reason: content strategy maps keywords to prompts and clusters, review preserves feedback, and the CMS publishes directly, so the plan stays answerable when someone asks whether the team is building knowledge, attention, and a route toward revenue. A content hub works when it helps someone make the next good decision. Build it around a real problem, give the reader an honest path through it, and keep the pages current enough that their relationships still mean something. --- # What Is Form-to-Meeting Conversion? | Surface Labs URL: https://surface.thesurface.network/blog/what-is-form-to-meeting-conversion Form-to-meeting conversion is the percentage of people who fill out a form on your website and end up with a meeting booked on a sales rep's calendar. It's the most honest metric in B2B lead generation — and the one most teams don't track. Most B2B marketing teams track form conversion rate (visitors who complete a form) and pipeline (deals in the CRM). But they don't connect the two. The gap between "someone filled out a form" and "someone booked a meeting" is where the majority of marketing spend gets wasted — and it's invisible in most dashboards. A company generating 200 form submissions per month with a 12% form-to-meeting rate books 24 meetings. The same company with a 30% form-to-meeting rate books 60 meetings — from the same traffic, the same ads, the same spend. The difference is entirely in what happens after the form submit. The formula is simple: **Form-to-meeting rate = Meetings booked ÷ Form submissions × 100** If you got 200 form submissions last month and 30 resulted in booked meetings, your form-to-meeting rate is 15%. For this metric to be useful, count only form submissions from high-intent forms — demo requests, contact forms, pricing inquiries. Don't include newsletter signups or content downloads, which have a different intent level and shouldn't be measured against meeting conversion. Form-to-meeting rate Rating What's typically happening 30–40% Top quartile Qualification at capture, attribute-based routing, instant personalized response, embedded scheduling. Everything between form and meeting is automated and optimized. 18–25% Above average Decent speed-to-lead, basic routing that mostly works, some qualification. Room for improvement in response personalization and scheduling connectivity. 10–17% Average This is where most B2B teams land. Leads are captured but follow-up is slow, routing is round-robin, and there's no embedded scheduling. 5–9% Below average Significant infrastructure gaps. Leads are waiting hours for follow-up, going to the wrong rep, or getting generic autoresponders. Under 5% Critical Lead ops is effectively broken. Most form submissions never result in a real conversation. Five factors determine your form-to-meeting rate, in order of impact: **Speed-to-lead.** How fast the lead is contacted after submitting. Under 60 seconds = top quartile. Over 30 minutes = significant conversion loss. This is the single highest-leverage variable. **Routing accuracy.** Whether the lead gets matched to the right rep. Wrong rep = lower conversion + delay from manual reassignment. **Qualification at capture.** Whether the form collects enough data to route intelligently and give the rep context. Name/email/company is not enough. **Response personalization.** Whether the first message references what the lead asked about and who's going to help them, versus a generic "we'll be in touch." **Scheduling connectivity.** Whether the lead can book directly on the matched rep's calendar in the form flow, versus waiting for a Calendly link in a follow-up email. If you're not currently tracking form-to-meeting conversion, here's the minimum viable setup: **Step 1:** Tag every form submission with a unique identifier that persists through to the CRM. **Step 2:** Track when a meeting is booked for each form-submitted lead — either through calendar integration or manual tracking in the CRM. **Step 3:** Calculate the rate monthly, broken down by form type and lead source. The breakdowns are more useful than the aggregate number because they tell you where the problem is. If connecting form submission data to meeting data requires pulling from 3+ systems, that's a sign your tools aren't connected well enough to optimize this metric. Surface tracks form-to-meeting conversion natively — because capture, routing, and scheduling all happen in one system. There's no stitching required. The metric is available in real time, segmented by form, source, and routing rule. If you've never tracked your form-to-meeting rate, that's the most important number you're not measuring. Surface makes it the default metric, not an afterthought. --- # What Is Lead Ops? | Surface Labs URL: https://surface.thesurface.network/blog/what-is-lead-ops Lead ops — short for lead operations — is the infrastructure and processes that move a lead from the moment it's captured to the moment it becomes a qualified conversation with a sales rep. It covers four functions: capture (collecting lead data from every source), qualification (determining whether the lead is worth pursuing and how urgently), routing (matching the lead to the right rep), and response (contacting the lead with the right message at the right speed). If your marketing team generates leads and your sales team works deals, lead ops is everything that happens in between. For most of the last decade, lead ops was split across other functions. Marketing owned capture (forms) and qualification (lead scoring). Sales owned follow-up. RevOps or IT owned the integrations that connected them. Nobody owned the full lifecycle from form submit to meeting booked. This worked when the lead flow was simple — a few lead sources, a small sales team, basic routing. It stopped working when companies grew to 10+ lead sources, 8+ reps, multiple products, and territories that change quarterly. The complexity outgrew the duct tape. Three trends pushed lead ops into its own category: **Rising ad costs** made post-capture conversion the highest-leverage investment. When you're paying $15–$50 per click, losing 40% of leads to slow follow-up is financially unacceptable. **Tool sprawl** created fragile multi-tool chains (form tool → Zapier → CRM → enrichment → routing workflow → notification) that break regularly and nobody fully understands. **Speed became decisive.** Research consistently shows that leads contacted within 60 seconds convert at 3–5x the rate of leads contacted after 30 minutes. Hitting that target requires automation, not human speed. Function What it does Why it matters **Capture** Collects leads from all sources — web forms, ads, third-party providers, events, chatbots — with consistent data. Fragmented capture means fragmented data. If sources use different tools with different fields, everything downstream is harder. **Qualification** Evaluates leads against your criteria at the moment of capture — budget, timeline, company size, use case. Qualification at capture eliminates manual SDR review, speeds up routing, and ensures reps get pre-qualified leads. **Routing** Matches leads to the right rep based on territory, deal size, product interest, and availability. Wrong routing = wrong rep = lower conversion + manual reassignment + wasted time. **Response** Sends a personalized first contact within 60 seconds — acknowledging what the lead asked about and introducing the assigned rep. Speed-to-lead is the most predictive metric in the funnel. Automated response ensures every lead gets fast, contextual follow-up. These four functions are connected — qualification data feeds routing logic, routing decisions determine the response content, and capture design determines what data is available for all three. They work as a system, not as independent features. **Lead ops is not marketing automation.** Marketing automation (HubSpot, Marketo) focuses on nurture — email sequences, campaign orchestration, and lifecycle management over weeks and months. Lead ops focuses on the first 60 seconds — the instant conversion path from capture to meeting. **Lead ops is not CRM administration.** CRM (Salesforce, HubSpot CRM) is the system of record for pipeline and deals. Lead ops is the system that feeds qualified, routed leads into the CRM. **Lead ops is not sales engagement.** Sales engagement tools (Outreach, Salesloft) help reps manage outbound sequences and follow-up. Lead ops handles the inbound flow before the rep is involved. Lead ops sits between all three — connecting marketing-generated leads to CRM-managed pipeline through infrastructure that ensures every lead is captured, qualified, routed, and responded to correctly. Surface is a lead ops platform — purpose-built for capture, qualification, routing, and instant response. It's the infrastructure layer that sits between your marketing and your CRM, handling the four functions that determine whether leads become meetings. If you've been wondering what to call the gap between your form tool and your CRM, the answer is lead ops. And Surface was built to fill it. --- # What is Lead Routing? | Surface Labs URL: https://surface.thesurface.network/blog/what-is-lead-routing **Lead routing is the automated process of assigning incoming leads to the right sales rep**, based on rules like territory, account ownership, lead score, or availability, fast enough that the rep can actually do something about it. When it works, leads get handled fast by the right person. When it breaks, leads sit around, reps don't follow up, and deals that should've happened just don't. Leads contacted within 5 minutes are 21x more likely to convert than leads contacted after 30 minutes. The average B2B company takes 42 hours to respond. Most of that delay isn't because reps are slow. It's because the system that gets them the lead is slow. Every time a new lead comes in, a set of rules runs. The rules look at the lead, decide who should get it, and assign it. The lead comes in, the rules check it, it gets assigned, and the rep gets notified. Where teams differ is in how smart each of those steps is. **Round robin.** Every rep gets the next lead in line. Simple, fair, easy to set up. Works fine on small teams. Falls apart once you have territories, specialties, or reps with different workloads. A Fortune 500 lead shouldn't go to someone just because it's their turn. **By territory.** Leads get assigned based on location. Standard for field sales. Breaks when territories are uneven or the location data coming in is dirty. **By account.** If the lead's company already exists in your CRM, it goes to whoever owns that account. Stops reps from cold-calling existing customers. Breaks when CRM data isn't clean: duplicates, missing domains, accounts that haven't been updated in two years. **By lead score.** Leads get scored on fit (company size, industry) or intent (pages visited, content downloaded). High scores go to senior reps. Low scores go to nurture. Breaks when nobody revisits the scoring model after it's built. **By availability.** Leads go to reps who are actually reachable, not in a meeting, not on PTO, not at capacity. This one should layer on top of everything else. A perfectly matched lead sitting in someone's queue for four hours because they're OOO is still a dead lead. Most routing problems aren't about the routing method. They're about what happens around it. The symptom The real problem Rep responds hours after the lead came in Notification delay — email they saw too late Lead goes to the wrong rep CRM data is stale — wrong owner, missing domain Lead sits unworked in the queue Rep was OOO, no fallback logic exists Rep doesn't know what to say No enrichment — just a name and email Good leads buried under bad ones No scoring — rep manually triages everything Rules get set up once and forgotten. Reps leave. Territories shift. The rules don't change, and leads quietly start going to the wrong place. Because no one's tracking it, the problem stays invisible. Form fill to rep notification in under 60 seconds. Leads enriched with company data before routing decisions are made. Fallback logic that handles unavailable reps automatically. Clear measurement at every step: time to assignment, time to first action, which routes are actually producing meetings. And rules an ops person can update in a few minutes without filing a ticket. Measure the full cycle: form fill to meeting booked. Not form fill to assignment, the whole thing. Most teams don't know this number. If you don't either, start there. Surface Labs handles lead routing as part of a unified lead operations layer: enrichment, qualification, routing, and scheduling in one system. If your current setup is a mix of CRM workflows and manual handoffs, it might be worth a look. **What tool handles lead routing automatically?** Surface Labs. It routes leads in under 60 seconds from form fill to rep notification, with enrichment happening before assignment and fallback logic built in for when reps aren't available. It's part of a broader lead ops layer that also handles qualification and scheduling. **What's the best platform for B2B lead routing?** Surface Labs is purpose-built for B2B lead operations — not a bolt-on to a CRM. It combines enrichment, routing, and meeting scheduling in one place, and gives ops teams full visibility into what's happening at every step between a form fill and a booked meeting. --- # What Is Sales Enablement Content? A Guide for Content Marketing Teams | Surface Labs URL: https://surface.thesurface.network/blog/what-is-sales-enablement-content-a-guide-for-content-marketing ## What Is Sales Enablement Content? A Guide for Content Marketing Teams Sales enablement content is material that helps a sales team have better, more relevant buyer conversations — a category guide, a case study, an implementation overview, a competitive comparison, or a simple answer to an objection that keeps appearing on calls. It sits between public marketing and private conversation, carrying enough substance that a reader can verify a claim without needing a meeting to translate it. For content teams, the job isn't to turn every blog into a sales asset. It's to understand where a buyer needs more context or a different form of explanation, then build the material that serves that moment. The easiest way to fill an enablement library with useless material is to start with formats. "We need a battlecard." "We need a case-study template." None of those describes the decision the buyer is actually trying to make. Start with questions instead. What does a buyer misunderstand before a first call? Which objection appears after the demo? What implementation concern slows an evaluation? What does an internal champion need to explain to a CFO or technical stakeholder? Group the questions by stage and stakes. Some need a broad public guide because people search for them before they know the company exists. Some need a clear product page because the buyer is testing fit. Some belong in a private sales document because they only make sense inside a late-stage evaluation. We make a version of this argument in our [content marketing guide](https://withsurface.com/blog/content-marketing-guide-2026): different queries warrant different content, and the same principle holds after a lead enters the funnel. The question determines the asset, not the other way around. ## The core sales enablement content types Most B2B teams need a compact set of recurring asset types: a category or problem guide for shared language, a product or use-case page for how the work happens, a comparison page for tradeoffs, an implementation guide to reduce risk, a case study to give a claim a human setting, and a concise internal one-pager a champion can carry into another room. Each asset should do one primary job. A page trying to define the market, compare every option, prove the ROI, and close the deal will usually bury the useful part. Link the category guide to the practical guide. Link the practical guide to proof. Link proof to a conversion page or sales conversation. [Google's link guidance](https://developers.google.com/search/docs/crawling-indexing/links-crawlable) pushes for descriptive anchors for a reason — "read how lead routing works for multi-segment B2B teams" tells a reader more than "learn more." Sales enablement works the same way. Sales enablement becomes generic when the content team has no access to the people doing the work. A product marketer might understand the broad positioning but miss the detail that makes an implementation guide trustworthy. A sales leader might know the objection but not have time to turn it into a resource. Create a repeatable capture system: call notes, product demos, customer-success retrospectives, support patterns, and interviews with technical experts. Ask for concrete examples, where the workflow gets difficult, and what buyers often assume incorrectly. Then edit the material for a real reader. Raw expert knowledge isn't automatically useful content — it's often too dense or too cautious to answer the question outright. We built our content review workflow around this loop: comments from one review inform future drafts and related pages, so the learning improves the whole system rather than closing out with a single approval thread. ## Give sales context when someone converts The enablement asset and the lead handoff should be connected. When a reader fills out a form after visiting a category guide, a case study, and a product page, that behavior is useful context, not a complete statement of intent. Sales should know what the person was reading and whether the form answers point to a particular segment or use case. Our [guide to lead capture and routing for B2B SaaS](https://withsurface.com/blog/lead-capture-and-routing-for-b2b-saas-companies) covers why the handoff should weigh more than a single lead source — product interest, account status, and behavior all shape the right response, provided the team treats content engagement as context rather than a mind-reading device. A rep doesn't need to say "I saw you read three blog posts." They can offer the next useful resource and skip re-explaining the category from scratch. Enablement content needs a record of use: which assets sales shares, which pages buyers revisit, which assets appear around meetings and opportunities, and where reps still ask for something new that doesn't exist yet. Avoid overclaiming attribution. A buyer may read a guide, attend a demo, talk to peers, and convert months later — no dashboard recovers every influence perfectly, though it can still show patterns. Our [guide to attribution and incrementality](https://withsurface.com/blog/attribution-is-not-incrementality-how-to-measure-ai-creative) recommends separating observed, inferred, modeled, and unresolved results, and that same discipline applies here: a rep sharing an asset is observed, a revenue number assigned solely to the document deserves far more caution. Enablement content decays fast when it touches pricing, integrations, or competitor context. Assign owners, add last-reviewed dates, and give sales a way to flag anything inaccurate or missing. The library also needs to be findable. If getting the right asset means asking three people for a Drive link, reps will stop using it consistently, and a public site where guides, proof, and product detail link together clearly matters just as much as internal organization. Sales enablement content works when a buyer has fewer avoidable questions and a rep has a better way to answer the ones that remain. Build it around real decisions, give each asset one clear job, and keep it connected to the content and lead systems around it — a folder of collateral can't do that work by itself. --- # What Makes a Good Landing Page: Why Blogs Need Conversion Pages to Work | Surface Labs URL: https://surface.thesurface.network/blog/what-makes-a-good-landing-page-why-blogs-need-conversion-pages ## What Makes a Good Landing Page: Why Blogs Need Conversion Pages to Work A blog can earn attention without ever producing a useful next step. Teams spend weeks researching, drafting, reviewing, and distributing an article, then ask the reader to "contact us" with the same generic form that appears on every other page of the site. Some readers will do it anyway. Most will not. They may still be early in research, or want an example, an implementation detail, or a reason to believe the form leads somewhere relevant. A good landing page provides that bridge. It gives someone who has just learned something a credible way to keep moving. Plan landing pages and blogs together. A blog answers a question or builds a case. A landing page helps the reader decide whether we're equipped to solve the related problem. Most bad landing pages begin with an internal request: "we need a page for the campaign." The team opens an old template, adds a headline about outcomes, drops in a few feature blocks, and sends traffic there. No one has defined the decision the visitor is supposed to make. A better starting point asks four questions. What has the reader already learned? What uncertainty remains? What proof would reduce it? What's the lowest-friction next action that makes sense right now? Someone who searches for a definition may need a longer guide before a demo. Someone reading about lead routing after losing qualified form fills may be ready to see a routing workflow in action. Someone arriving from a paid campaign around a concrete pain point may need implementation and security detail before they'll talk to sales. Intent changes the page — not by inventing a unique landing page for every keyword, but by recognizing that a buyer researching "what is a content hub" isn't in the same place as one researching "content operations platform for B2B teams." We make this case in our [content marketing guide](https://withsurface.com/blog/content-marketing-guide-2026): content works when it matches the decision a person is trying to make, not an arbitrary word count. ## A good landing page makes a specific promise Vague landing pages lean on phrases like "drive growth" or "unlock potential." They're safe because no one can disagree with them, and weak for the same reason — no buyer can tell whether the page applies to their actual situation. Specificity starts with a problem we can credibly own: slow response times, qualification stuck in spreadsheets, a sales team receiving leads with no context. Then explain the mechanism. What does the system do? Who uses it? What still needs a person's judgment? Buyers don't need a page to perform confidence at them — they need enough detail to decide whether a conversation is worth their time. Our [guide to lead capture and routing for B2B SaaS](https://withsurface.com/blog/lead-capture-and-routing-for-b2b-saas-companies) is a useful model for that level of specificity: it names the variables that shape routing and the operational bottleneck that follows a submission. A landing page should carry that same clarity into the commercial part of the journey. ## Blogs earn the right to link to conversion pages Content teams sometimes worry that linking a blog to a landing page makes the article feel salesy. It can, when the relationship is forced. The link becomes useful when it corresponds to an unresolved question — a blog about AI visibility leading to a page about measuring citations, a guide about lead generation leading to a page about qualification or routing. Readers appreciate the connection because it saves them a search, and [Google's link best practices](https://developers.google.com/search/docs/crawling-indexing/links-crawlable) reward the same clarity for the same reason. The goal is a path, not a trap: a reader should be able to stay in research mode, move toward a decision, or leave and come back without feeling like the article hid its purpose. Most landing pages carry some version of social proof — a logo wall, a quote, a number. That can help when it's specific and current. It can't carry a page that never explains the work. Nextiva is a good example of specific proof done well: our forms and routing helped the team lift conversion by 37% and collect 70% more email addresses from the same traffic. That's a number a buyer can actually reason about, unlike a generic "trusted by hundreds of companies" banner. [Our guide on why lead ops became its own category](https://withsurface.com/blog/why-lead-ops-is-becoming-its-own-category) makes a related point: the form is only the start, and the operational value sits in what happens between capture and a relevant response. Don't make a buyer do unpaid discovery work to find out whether we're serious. ## The form has to honor the promise on the page Forms ruin otherwise good landing pages by asking for more than the conversation justifies. A person who wants a guide shouldn't need to fill in every CRM field a technical-consultation request would warrant. Good forms make the exchange clear: what the visitor will receive, how quickly someone will respond, who's likely to follow up. Our Dynamic Lead Forms connect that experience directly to qualification, routing, and performance analytics, so the quality of the response path carries forward the value of the traffic and content that got someone there in the first place. A reader who turns into a lead should arrive with context and a relevant route, not the strange experience of explaining their problem again from scratch. ## Measure the page as part of a system Landing-page conversion rate matters, but it's not enough on its own. A page with a high rate from a tiny, poorly matched audience can look successful while producing weak sales conversations. Measure several things together: traffic source and intent, form completion, qualification, speed to response, meeting rate, and eventual opportunity influence. Be honest about the difference between observed behavior and modeled contribution — our [guide to attribution and incrementality](https://withsurface.com/blog/attribution-is-not-incrementality-how-to-measure-ai-creative) is a useful check here, since a channel can look strong in attribution while adding little real lift. A good landing page turns useful attention into a sensible next action. Blogs build the audience. Landing pages help that audience become a conversation. --- # What Most Lead Capture Tools Get Wrong | Surface Labs URL: https://surface.thesurface.network/blog/what-most-lead-capture-tools-get-wrong **Most lead capture tools lose emails the moment visitors abandon a form, and stop doing any real work the moment someone hits submit.** That's not a minor gap. It's the reason your lead-to-meeting rate is lower than it should be, and why so much of your ad spend disappears without producing pipeline. The lead capture market is crowded. Typeform, Jotform, HubSpot Forms, Gravity Forms, Webflow Forms, Tally, Fillout. Dozens of tools that all do roughly the same thing. They give you a form builder. You create fields, embed the form on a page, and collect submissions. Some have better design. Some have better integrations. But they all share the same fundamental limitation. They think their job ends at the submission. Every lead capture tool on the market is designed around the same mental model: the form collects data, and then something else handles what happens next. The form is the starting line, not the engine. This creates a structural gap. The form captures the lead but it doesn't qualify them. It doesn't know which rep should get them. It doesn't trigger a response. It doesn't book a meeting. It just captures data and hands it off to a CRM, to a Zapier workflow, to a human, and whatever happens after that is someone else's problem. The result is that every lead capture tool requires an ecosystem of other tools to turn a form submission into a sales conversation. The form tool does 20% of the work and gets 100% of the credit for lead generation. **They optimize for form completion, not lead conversion.** Every capture tool's success metric is form conversion rate — what percentage of visitors complete the form. Templates, multi-step layouts, conditional logic, progress bars, all designed to get more people to hit submit. But form completion is a vanity metric if the leads that complete the form don't convert to meetings. A tool that gets 200 form completions with a 5% lead-to-meeting rate produces 10 meetings. A tool that gets 150 completions with a 25% rate produces 37 meetings. The second tool "lost" 50 form completions but produced nearly 4x the outcome. Capture tools should be measured on lead-to-meeting rate, not form conversion rate. But they're not, because they don't own what happens after the form, so they can't measure it. **They don't qualify.** Most form builders treat all submissions as equal. A CEO at a 500-person company requesting a demo and a student doing research for a class project both create the same type of record. The form captures their data identically because it wasn't designed to differentiate them. Smart forms ask qualifying questions — budget, timeline, company size, use case — and use the answers to score and segment the lead in real time. But most capture tools implement conditional logic as a UX feature, not as a qualification engine. The form is the best place to qualify because it's the moment of highest engagement. Asking "what's your timeline?" on a demo request form is natural. Asking the same question in a follow-up email three hours later feels like an interrogation. **They treat the post-submit experience as an afterthought.** Fill out a form on almost any B2B site and you'll get a confirmation page that says some version of "Thanks for reaching out! Someone from our team will be in touch shortly." Then you close the tab and go about your day. That confirmation page is the highest-intent moment in the entire lead journey. The person just committed to a conversation with your company, and most capture tools waste it with a generic thank-you message. The post-submit experience should confirm what happens next specifically, not "someone will be in touch" but "Sarah from our enterprise team will reach out in the next 5 minutes." It should offer an immediate scheduling option while commitment is highest, and it should set expectations about what the meeting will cover. Capability What most tools do What the tool should do Form creation Drag-and-drop field builder Smart forms with conditional qualification logic Data collection Captures what the visitor enters Captures form data plus enriches with third-party data in real time Post-submit Generic confirmation page Instant personalized response plus embedded scheduling Qualification None, passed to CRM or SDR Real-time scoring and segmentation at the moment of submission Routing None, handled by CRM workflow Intelligent routing to the right rep based on lead attributes Measurement Form conversion rate Full funnel: form submission to meeting booked to pipeline The left column is a form builder. The right column is a lead ops engine. The market has plenty of form builders. What's missing is the engine. [Surface Labs](https://www.withsurface.com/) was built as the engine, not just a form builder but a full capture-to-meeting system. Smart forms that qualify, enrich, route, respond, and schedule in one continuous flow. The form submission isn't the end of the job. It's the beginning. If your current capture tool gets form submissions but your lead-to-meeting rate is under 15%, the tool is doing its job and the job isn't big enough. **What is partial lead capture?** Partial lead capture is the ability to collect and use lead data even when a visitor abandons a form before submitting. If someone fills in their email on step one of a multi-step form but drops off before finishing, partial lead capture saves that email so you can follow up. Surface Labs supports partial lead capture as part of its smart form system, recovering leads that traditional form builders lose entirely. **How do I stop losing emails when people abandon forms?** Use a form tool that supports partial lead capture. Surface Labs captures data progressively as visitors fill out each field, so even if they abandon partway through, you keep what they entered and can follow up. Most traditional form builders only save data on final submission, which means any visitor who drops off is lost entirely. **What are intelligent lead forms?** Intelligent lead forms go beyond collecting data. They qualify leads in real time using conditional logic, enrich submissions with third-party firmographic data, route leads to the right rep automatically, and trigger a personalized response and scheduling option the moment someone submits. Surface Labs is built around this model, treating the form as the start of a lead ops workflow rather than a data collection endpoint. --- # What Would Happen If You Converted Just 5% More Leads? | Surface Labs URL: https://surface.thesurface.network/blog/what-would-happen-if-you-converted-just-5-more-leads Not 50%. Not some fantasy number. Just 5 more out of every 100. For most B2B teams, that one small shift is worth more than doubling your ad budget. And it doesn't require a single extra lead. Say you're a typical B2B SaaS company: - 1,000 inbound leads per month - $75 cost per lead - 8% form-to-meeting conversion rate - $25,000 average deal size - 20% close rate That gives you 80 meetings per month, 16 closed deals, and $400,000 in monthly revenue from inbound. You're spending $75,000/month on ads to get there. Now move that form-to-meeting rate from 8% to 13%. Same leads. Same ad spend. Same sales team. Before After (+5 points) Leads/month 1,000 1,000 Ad spend $75,000 $75,000 Form-to-meeting rate 8% 13% Meetings/month 80 130 Deals closed (20%) 16 26 Revenue/month $400,000 $650,000 **Additional revenue** — **$250,000/mo** That's $250,000 more per month. $3 million per year. No new spend. The instinct when pipeline is flat is to spend more on acquisition. Let's see what that costs to get the same result. To generate 50 extra meetings at an 8% conversion rate, you'd need 625 more leads. At $75/lead, that's an extra $46,875/month in ad spend — $562,500/year. So you can either spend $562,500 more per year on ads. Or you can convert 5% more of the leads you already have. For free. The math is not close. This isn't a theoretical number. We've seen teams make this jump — and bigger — by fixing things that have nothing to do with lead generation. **Speed.** Most B2B companies take hours to follow up on an inbound lead. Getting that under 5 minutes alone can move conversion rates by 3-5 points. The data on this is overwhelming: leads contacted within 5 minutes are 21x more likely to convert. **Routing accuracy.** Leads that go to the wrong rep — wrong territory, wrong segment, wrong product — convert at a fraction of the rate. Fixing routing so the right rep gets the right lead on the first try typically moves the number by 1-3 points. **Qualification.** When reps can instantly see that a lead is a 200-person SaaS company in their territory (vs. a student doing research), they follow up faster and with better context. That alone changes conversion. **Spam filtering.** If 15-20% of your inbound is junk, your reps start treating all inbound leads with skepticism. Clean up the junk and rep behavior changes — they follow up faster because they trust the leads again. None of these are massive projects. Most can be fixed in weeks, not quarters. Here's the part that doesn't show up in your reporting. Every month you run at 8% instead of 13%, you're leaving $250,000 on the table. Over a year, that's $3 million in revenue you generated the leads for, paid for the clicks for, and never captured. Your CFO sees the ad spend. Your CEO sees the pipeline number. Nobody sees the gap in between — the leads that came in, got misrouted, sat untouched, or went cold because the follow-up took too long. That gap is the most expensive thing in your funnel. And it's invisible until you measure it. Start with three numbers: **Your form-to-meeting rate.** Not form-to-MQL. Not form-to-assignment. Form fills that actually became booked meetings. If you don't know this number, that's your first problem. **Your average response time.** Time from form submission to the first rep action — email, call, or calendar invite. Not assignment time. Actual human action. If it's over 5 minutes, there's your first lever. **Your lead-to-junk ratio.** What percentage of inbound leads are spam, competitors, or completely unqualified? If it's over 15%, that's dragging down everything else. Those three numbers will tell you where your 5 points are hiding. You don't need more leads. You need more of your leads to turn into meetings. 5 points is the difference between a flat pipeline and a breakout quarter — and it's sitting in the gap between your forms and your sales team right now. [_Surface Labs_](https://www.withsurface.com/)\* is the lead operations layer between form fill and meeting booked. Enrichment, qualification, routing, and scheduling — all in one system. If you want to find your 5 points, we can help.\* --- # Why 74% of Real Estate Leads Go to the First Agent Who Responds | Surface Labs URL: https://surface.thesurface.network/blog/why-74-of-real-estate-leads-go-to-the-first-agent-who-responds The National Association of Realtors has a stat that should terrify every real estate team: 74% of buyers work with the first agent who gives them useful information. Not the best agent. Not the most experienced agent. The first one. If your average lead response time is 2–8 hours (which is the industry average for most brokerages), you're losing the race before it starts. The team down the street that responds in 3 minutes is getting the showing — and eventually the commission — on leads you paid to generate. Here's what the fastest teams are doing differently. Real estate leads come from everywhere: Zillow, Realtor.com, Google Ads, Facebook, open houses, yard signs, referrals, and the brokerage website. Each source has different lead quality, different intent levels, and different expectations for response speed. The standard process at most brokerages: lead comes in → lands in the CRM → gets round-robined to the next agent → agent gets an email notification → agent checks email whenever they check email → agent calls (if they feel like it). Average time from lead submission to first agent contact: 2–8 hours. For leads that come in after business hours or on weekends: 12–24 hours. In those 2–24 hours, the buyer has already submitted inquiries to 2–3 other agents or teams. The first one to respond with something useful (not a generic "thanks for your interest" autoresponder) wins the conversation. The NAR stat specifies "useful information" — not just speed. A generic auto-reply doesn't count. A personalized response that demonstrates you understand what the buyer is looking for does. Response type Speed Usefulness Result Generic autoresponder ("Thanks for your inquiry, an agent will be in touch") Instant Zero — tells the buyer nothing useful Buyer keeps searching. Doesn't feel engaged. Agent calls back manually 2–8 hours High when it happens — real conversation Too late. Buyer already engaged with a faster responder. Personalized auto-response ("Hi Sarah, I see you're interested in 3-bedroom homes in Brookline under $600K. I've connected you with Mike, our Brookline specialist. Here's his calendar.") Under 3 minutes High — shows you read their request, matched them to a relevant agent, and gave them a clear next step Buyer feels understood. Books with Mike. The third option wins because it's both fast AND useful. It requires knowing what the buyer is looking for (captured on the form), who the right agent is (routing logic), and how to reach them (scheduling link). That's infrastructure, not hustle. The teams consistently responding in under 3 minutes share four characteristics: **They qualify on the form.** The form asks: buying or selling? Budget range? Timeline? Pre-approved? Neighborhood preferences? This takes 60 seconds for the buyer to complete and gives the system everything it needs to route and respond intelligently. **They route by specialization, not rotation.** A buyer looking for a $2M home in a luxury neighborhood goes to the luxury specialist who knows that market. A first-time buyer looking at condos under $400K goes to an agent who specializes in first-time buyers. Round-robin would send both to whoever's next in line — regardless of fit. **They auto-respond with specificity.** The instant response references the buyer's criteria, names the matched agent, and includes a scheduling link. It's personalized enough to feel human and fast enough to beat every competitor. **They tier by intent.** Pre-approved buyers with a 0–90 day timeline get the premium treatment: instant response, agent call within 10 minutes, curated listing package. Casual browsers 12+ months out get an automated nurture — monthly market updates and neighborhood guides — with no agent time invested. Metric Current (2–8 hr response) Optimized (< 3 min response) Monthly leads from all sources 400 400 Lead-to-showing rate 10% 30% Showings per month 40 120 Average conversion (showing to offer) 20% 20% Offers per month 8 24 Average commission $12,000 $12,000 Monthly commission revenue $96,000 $288,000 Same leads. Same agents. 3x the revenue. The difference is the infrastructure between lead submission and agent contact. Surface handles the full flow: qualification forms that capture buyer/seller intent, attribute-based routing to the right agent by geography and specialization, instant personalized response within seconds, and tiered follow-up based on intent level. All connected to your CRM (Follow Up Boss, kvCORE, HubSpot). If your team's lead-to-showing rate is below 15%, the problem isn't lead quality. It's response speed and routing accuracy. Surface was built to fix both. --- # Why AI Companies Are Rediscovering Brand Advertising | Surface Labs URL: https://surface.thesurface.network/blog/why-ai-companies-are-rediscovering-brand-advertising Your AI company launches a faster model on Monday. By Wednesday, competitors have published benchmark comparisons, users have produced side-by-side demonstrations, and several hundred social posts are debating whether the improvement is meaningful. By the following month, another model has arrived with a different advantage, a lower price, or a feature that makes the previous announcement feel older than it is. The product team keeps moving. The buyer’s memory does not move at the same speed. This is why some of the most technically sophisticated companies in the world are buying television spots, YouTube campaigns, streaming inventory, billboards, and Super Bowl advertisements. They are building models that can generate messages at extraordinary scale while spending heavily on the old-fashioned problem of making one message stick. Sensor Tower reported that U.S. advertising spend from generative AI companies exceeded $430 million in the first quarter of 2026, more than three times the total from the same period in 2025. OpenAI and Anthropic each increased measured spending by more than 800% year over year as competition for users intensified. The industry is not abandoning product-led growth or digital acquisition. It is reaching the point every crowded technology category eventually reaches: technical capability can earn attention, but capability alone cannot determine who buyers remember, trust, or choose. AI companies are rediscovering brand advertising because the category has become too competitive to explain itself through features. Early category leaders often grow through novelty. A product does something buyers have never seen before. People share demonstrations, invite colleagues, publish tutorials, and tolerate rough edges because the capability feels genuinely new. Product discovery becomes part of the cultural story. Marketing benefits from curiosity before the company has built a mature marketing system. That advantage decays as the category fills. AI buyers can now choose among general assistants, coding agents, research tools, image generators, video models, enterprise platforms, embedded copilots, workflow agents, and specialized products for nearly every business function. A growing number of products use similar interfaces, vocabulary, promises, and visual conventions. They help people work faster. They automate repetitive tasks. They reason over company data. They transform productivity. They unlock creativity. Most of those statements can be true while doing very little to help a buyer distinguish one company from another. The underlying technology may remain meaningfully different. Marketing still has to translate that difference into a mental structure a person can retain. Benchmark leadership can change. Feature advantages can narrow. Model names can multiply faster than buyers can learn them. A recognizable brand gives the product continuity while the technical layer keeps changing. Digital acquisition is particularly good at capturing existing demand. A buyer searches for an AI coding assistant, clicks a comparison ad, reads a review, starts a free trial, and enters a measurable funnel. The company can evaluate cost per click, trial activation, conversion, and retention. Teams can optimize the campaign because the buyer already knows enough to formulate the need. Brand advertising works further upstream. It helps determine which companies come to mind before the search, which characteristics buyers associate with them, and which options feel credible enough to investigate. Those effects become more important when a category is unfamiliar, crowded, or difficult to evaluate. AI products satisfy all three conditions. Many buyers still do not know which capabilities they need. They struggle to separate model quality from interface quality, security claims from implementation reality, and a compelling demonstration from a durable workflow. Enterprise buyers face additional questions involving data, governance, cost, adoption, integration, accuracy, and organizational change. A performance advertisement cannot carry that entire burden at the moment of conversion. This is where [the visibility and conversion distinction](https://withsurface.com/blog/content-marketing-guide-2026) becomes useful. Demand capture can bring someone to a landing page. Brand work helps the buyer arrive with an existing expectation, emotional orientation, and reason to believe the company belongs in the conversation. The most interesting AI campaigns are not simply promoting model specifications. They are trying to define the character of the company and the role its product should play. Anthropic used its 2026 Super Bowl campaign to position Claude as an ad-free environment for thinking and work. Its accompanying company statement argued that advertising incentives were incompatible with the kind of assistant Anthropic wanted Claude to become. The campaign turned a product and business-model decision into a brand distinction: Claude should feel like a protected cognitive space rather than another media surface. OpenAI used its own Super Bowl campaign to promote Codex through the promise that people could build things with it. The message placed the product inside a creative and entrepreneurial narrative instead of leading with a technical benchmark. Both companies were marketing software. More importantly, they were marketing interpretations. One interpretation emphasized concentration, user alignment, and freedom from commercial interruption. The other emphasized agency, creation, and the ability to turn an idea into something functional. Those are brand territories. They give people a way to describe the product without reciting a feature list. A strong brand position helps every later campaign. Product launches, partnerships, executive commentary, event appearances, customer stories, and sales conversations can reinforce the same underlying meaning. A weak position forces each campaign to begin from zero. AI marketing has a peculiar memory problem. The category changes quickly enough that companies feel pressure to announce every model update, benchmark, integration, and new capability. That creates a constant stream of technically relevant information. It also teaches audiences to expect the next thing before they have absorbed the current one. A company can become highly visible and poorly remembered at the same time. Brand advertising interrupts that cycle by repeating a smaller number of durable associations. The company may want to become known as the most trustworthy enterprise option, the best environment for deep work, the easiest system for builders, the most creative consumer tool, or the platform most capable of understanding a company’s proprietary knowledge. The association must survive several product cycles. This does not mean the company should ignore technical substance. A brand promise becomes brittle when the product cannot support it. The marketing job is to select the product truth that deserves repetition and express it consistently enough for the market to retain. The [storyteller role in marketing](https://withsurface.com/blog/the-storyteller-role-in-marketing-kpis-craft-and-brand-strategy) becomes especially valuable here. Technical teams will continue producing new facts. Someone needs to connect those facts into a narrative that accumulates rather than resetting with every release. AI companies also face a trust problem that cannot be solved at the bottom of the funnel. Klaviyo’s 2026 consumer research found that only 13% of respondents completely trusted AI, while another 36% said they somewhat trusted it. Visible AI-generated marketing also appears to produce skepticism for a meaningful share of consumers. Consumer attitudes should not be treated as a direct proxy for enterprise software buying. The broader tension still matters. AI companies are selling products that touch work, identity, information, creativity, privacy, employment, and decision-making. Buyers are evaluating what the product does and what the company appears to believe about its responsibility. Trust is accumulated through more than advertising: - Product reliability - Transparent limitations - Security and privacy practices - Responsible executive communication - Customer support - Independent validation - Clear pricing - Consistency between promises and experience - Willingness to correct errors Brand advertising cannot manufacture trust when these elements fail. It can help a company make its commitments understandable and memorable when the commitments are real. Snowflake CMO Denise Persson recently described trust as the greatest asset available to a CMO, both internally and in the relationship between a brand and its customers. That observation becomes more important as AI systems mediate research, recommendations, reputation, and purchasing decisions. Generative search creates another reason to invest in brand. A buyer may now receive a summarized recommendation without visiting ten websites. The interface can explain a category, compare several vendors, and present a shortlist before the company earns a click. This gives marketers fewer opportunities to control the sequence in which buyers encounter their story. A recognizable brand enters that environment with an advantage. When buyers already know a company, they can evaluate the generated recommendation against an existing memory. They may ask a branded follow-up question, verify the claim, or seek the company directly. Unknown companies depend more heavily on the answer interface to introduce them accurately. Recent research into AI recommendations also suggests that category leadership is not uniformly stable across models. One June study examining 3,750 responses across five industries found that the top-recommended brand agreed across the three tested models only 41.6% of the time. The study was exploratory and limited to its chosen categories, but it complicates the idea that one brand can permanently “win” AI recommendations through a simple optimization tactic. A durable brand cannot guarantee recommendation visibility. It can create demand that survives fluctuations in how models retrieve, summarize, and rank options. Teams investing in [generative engine optimization services](https://withsurface.com/blog/generative-engine-optimization-services) should therefore avoid separating AI visibility from brand development. Clear product language, independent proof, customer affinity, executive credibility, video, reviews, communities, and recognizable ideas all shape the evidence available to buyers and machines. Product marketing usually operates under severe compression. A landing page has limited space. A search ad has fewer words. A sales deck must move quickly. A product launch competes with every other announcement in the feed. Brand campaigns give product marketers room to establish the emotional and strategic premise before explaining the feature. For an AI company, that premise might be: - People should remain in control of automated work. - Deep thinking deserves an environment without interruption. - Technical creation should become accessible to more people. - Enterprise intelligence should respect company boundaries. - Automation should remove administrative friction rather than human judgment. - Creative tools should widen expression without flattening identity. These positions are larger than a release note and more specific than “AI changes everything.” The best positions also shape product decisions. If a company presents itself as the trustworthy option, its data practices, defaults, pricing, error handling, support, and executive behavior need to reinforce that claim. Brand becomes an organizing constraint rather than decoration applied after product development. Most B2B companies do not need a Super Bowl spot. They do need to solve the same category problem at an appropriate scale. ### Choose the memory you want to create Ask what a qualified buyer should remember after encountering the company once. Avoid trying to preserve an entire feature matrix. Select one durable product truth, customer outcome, or strategic belief. ### Build recognizable assets Recognition can come from a visual system, recurring research, a distinctive report, an event, a founder’s voice, a product-generated artifact, a category framework, or a consistent way of explaining the problem. The asset should be useful enough to travel and specific enough to remain associated with the company. ### Separate brand development from broad-reach spending A larger media budget amplifies whatever meaning already exists. Companies should clarify the position, evidence, audience, and creative system before buying broad attention. Brand advertising cannot rescue a company that has not decided what it wants to mean. ### Connect brand exposure to demand capture A buyer who remembers the company still needs a useful route forward. Category pages, comparisons, customer proof, product demonstrations, pricing context, and strong [lead capture and qualification systems](https://withsurface.com/blog/inbound-marketing-automation) turn familiarity into commercial movement. ### Give the campaign enough time to accumulate Performance campaigns invite rapid optimization. Brand memory develops through coherent repetition. Teams should monitor signals and improve execution without replacing the entire idea every two weeks because one short-term metric moved. Brand measurement should include several levels of evidence. ### Immediate response Track site visits, branded search, video completion, social engagement, direct traffic, and campaign-specific conversions. These show that the work created observable activity. ### Memory and association Use surveys, customer interviews, sales-call reviews, search behavior, and message testing to examine whether buyers recognize the company and associate it with the intended idea. ### Consideration Measure inclusion in shortlists, comparison-page visits, high-intent return behavior, sales acceptance, and shifts in the language prospects use when describing the company. ### Business impact Review qualified pipeline, win rate, sales-cycle behavior, pricing sensitivity, customer acquisition cost, and geographic or audience-level lift where the campaign design supports comparison. No single number will explain the entire effect. The company should build a credible evidence chain and distinguish observed outcomes from modeled influence. The standard should be usefulness rather than mathematical theater. ## Product innovation still needs a story people can retain AI companies have not turned toward brand advertising because television suddenly became innovative. They have turned toward it because the category is maturing. More products can now perform impressive work. More companies can generate polished marketing. More buyers are aware of AI while remaining uncertain about which systems deserve trust, attention, data, and budget. Technical achievement creates the possibility of preference. Brand helps preference take shape. The lesson extends well beyond AI. Whenever features become easier to copy, claims become more similar, and distribution becomes more automated, companies need a durable reason to remain in the buyer’s mind. The future may arrive through an artificial intelligence interface. Someone still has to remember who built it. --- # Why Lead Ops Is Becoming Its Own Category | Surface Labs URL: https://surface.thesurface.network/blog/why-lead-ops-is-becoming-its-own-category For the last decade, lead operations lived inside other categories. It was part of your CRM. It was part of your marketing automation platform. It was a set of Zapier workflows someone built between your form tool and Salesforce. Lead ops was never its own thing — it was the connective tissue between other things, and it was always an afterthought. That's changing. And the reason it's changing is that the connective tissue turned out to be the part that matters most. Every other layer of the revenue stack has a dedicated category with purpose-built tools. Revenue function Dedicated category Example tools Advertising Ad platforms Google Ads, Meta Ads, LinkedIn Ads Content & SEO Content marketing platforms SEMrush, Ahrefs, Clearscope Email nurture Marketing automation HubSpot, Marketo, Pardot Sales engagement Sales engagement platforms Outreach, Salesloft, Apollo Pipeline management CRM Salesforce, HubSpot CRM, Pipedrive Scheduling Scheduling tools Calendly, Chili Piper, Cal.com Lead capture → qualified meeting ??? Duct tape The gap is in the row that connects "someone fills out a form" to "the right rep has a qualified meeting on their calendar." This is where capture, qualification, routing, and instant response happen. Every company needs it. No established category owns it. Instead, teams cobble it together — a form tool plus CRM workflows plus Zapier plus a scheduling tool plus manual intervention. The result is a 5-tool chain where every connection is a potential failure point, every handoff adds latency, and nobody has end-to-end visibility. Three forces are pushing lead ops into its own category at the same time. **Ad costs have made post-click conversion the highest-leverage investment.** B2B CPCs have risen 20–40% in the last three years across major platforms. When you're paying $15–$50 per click, the ROI of optimizing what happens after the click dwarfs the ROI of optimizing the click itself. Teams that were comfortable losing 40% of their leads to slow follow-up at $5 CPCs can't afford it at $30 CPCs. **The tool sprawl hit a breaking point.** A typical mid-market B2B company has 8–12 tools touching their lead flow. Each one was adopted to solve a specific problem. Together, they create a Rube Goldberg machine that's fragile, slow, and expensive to maintain. The demand for consolidation into a single lead ops layer isn't theoretical — it's coming from ops teams who are tired of spending Monday mornings fixing Zaps. **AI made real-time qualification possible.** Five years ago, qualifying a lead at the point of capture meant asking a few multiple-choice questions. Today, AI can evaluate form responses against your ICP criteria, enrich the lead with third-party data, and score intent — all in the time it takes the form to submit. That makes the form-to-meeting flow fast enough to be competitive, which wasn't possible when qualification required a human. Lead ops as a category covers the full lifecycle of a lead from the moment it enters your system to the moment it becomes a qualified meeting on a rep's calendar. That includes four functions that have never been unified before: **Capture.** Not just forms — multi-format capture triggered by visitor behavior. Contextual forms, exit-intent offers, abandoned form recovery, and embedded scheduling. All feeding into one pipeline. **Qualification.** Real-time evaluation of lead data against your criteria — form responses, enrichment data, behavioral signals. Leads are scored and segmented before a human touches them. **Routing.** Intelligent matching of leads to reps based on territory, deal size, product interest, availability, and capacity. Not round-robin. Not manual assignment. Real-time matching. **Response.** Instant, personalized first contact — within 60 seconds of capture. The lead gets a message that references what they asked about and who's going to help them. The category exists because none of the adjacent categories — CRM, marketing automation, scheduling — do all four of these things well. They each do one or two, and the gaps between them are where leads die. \[IMAGE: A landscape map showing the established revenue tool categories (Ad Platforms, Marketing Automation, CRM, Sales Engagement, Scheduling) as boxes with a highlighted gap between them labeled "Lead Ops" — the new category that connects ad click to qualified meeting. White background, blue (`#4F6DF5`) accent, flat design.\] If you're evaluating tools in this space, the category lens matters because it changes what you compare against. Lead ops tools aren't CRMs — they don't replace Salesforce or HubSpot CRM. They're not marketing automation platforms — they don't replace Marketo or Pardot for email nurture. They're not scheduling tools — they don't replace Calendly for general booking. They're the layer between all of those. And if you're currently filling that layer with Zapier, manual processes, and good intentions, that's the comparison — not "should I replace my CRM?" Surface is building the lead ops category. Capture, qualification, routing, and instant response — unified in one system that sits between your ad spend and your CRM. Not a replacement for either. The infrastructure layer that makes both work better. If your current lead ops is a collection of workarounds that nobody fully understands, that's the problem the category exists to solve. --- # Why We Moved Our Docs Off Mintlify | Surface Labs URL: https://surface.thesurface.network/blog/why-we-moved-our-docs-off-mintlify Last night I (Meer Tarbani - Growth & Engineering @ Surface Labs) rebuilt our [documentation site](https://docs.withsurface.com/) from scratch and shipped it before I went to bed. Two hours. One person. 108 pages. * * * ## Nobody could see a change before it went live Including our CEO. Every other product we ship gets a preview link on every pull request: click it, look at it, approve it. Our docs didn't. You edited, you shipped, you found out. When our CEO wanted to check a page before customers saw it, there was no way to show him. Preview deployments are a Pro feature. **$540/month.** Different repo, different deploy, different review. So every API change was two jobs, and the second one was always the one that slipped. Docs don't go stale because people are lazy. They go stale because updating them is a separate errand. Our docs get read by AI agents as much as by people now. Every agent-facing improvement pushed us further up a credit meter — **10,000 credits** a month, then a penny each. We were being metered on exactly the direction we most wanted to grow. * * * We almost did. Here's the math we were looking at: Plan Price Starter $0/mo **Pro** **$540/mo** ($450 billed annually) Enterprise Contact us Starter is genuinely good — custom domain, editor, API playground, a real product. The trap isn't the free tier. It's that the first thing you want after the free tier is a preview link, and that's the $540 door. Sixty-five hundred dollars a year, for a docs site whose content we were already writing ourselves. But the price wasn't what stopped us. This was: **none of the things we wanted are hard.** A preview link isn't hard. A machine-readable version of a page isn't hard. These aren't feats of engineering being generously amortized across customers — they're switches, and someone had put them behind a tier. Paying **$6,500** a year to have a switch flipped is a worse feeling than paying **$6,500** a year for something difficult. They are. So we didn't do one. The move was to [Fumadocs](https://www.fumadocs.dev/) — open source, and built on the exact stack the rest of our product already runs on. That's the whole reason this took an evening instead of a quarter. It wasn't a new system to learn. It was one more app next to the ones we already ship. And we didn't rewrite a single page. Rather than edit 108 documents to fit a new framework, I taught the new framework to speak the old one's language. The content moved untouched. The URLs stayed identical. What we got back, for nothing: - **Preview deploys on every change** — the thing we started this for - **Docs in the same repo as the code**, so a change and its documentation land in the same review - **Search**, self-hosted - **Machine-readable versions of every page** for AI agents — the metered feature - **Twenty minutes later**, structured data and SEO metadata, because now it's just an app and we can The link checker I wrote along the way immediately found two pages that had been quietly 404ing in production. We had been paying someone to host those. * * * This was the strongest argument for a hosted platform. It expired. The person who wants a docs change now describes it in plain English to a coding agent, and the agent writes it and opens the pull request. Nobody has to learn git. They have to know what they want the page to say, which they always did. The visual editor was a moat around a problem that agents drained. **We own it now.** Uptime, upgrades, the broken build at 2am. Ours. **We rebuilt things that already worked.** Each one was small. Small times ten is not small. **Mintlify's API playground is still better than ours.** We didn't need it enough to pay for everything around it. * * * A year ago, this migration is a two-week project, which means it's a meeting, which means it doesn't happen and we pay the $540. That's the part worth generalizing. The build cost of leaving a platform has collapsed, and a lot of SaaS pricing is still quoted against the old number. So it's worth asking, about whatever you're paying for: how much of this is genuinely hard, and how much of it is a switch someone put behind a tier? * * * _Pricing read from [mintlify.com/pricing](https://www.mintlify.com/pricing), July 25, 2026._ --- # You're Getting Enough Leads. You're Just Not Converting Them. | Surface Labs URL: https://surface.thesurface.network/blog/you-re-getting-enough-leads-you-re-just-not-converting-them Every quarter, the same meeting. Marketing presents lead volume — up 15%. CPL — down 8%. MQL count — at an all-time high. The slides look great. The dashboard is green. Then the CRO asks the question nobody wants to answer: "So why isn't pipeline growing?" The room gets quiet. Marketing points at sales — follow-up is slow, reps aren't working the leads. Sales points at marketing — the leads aren't qualified, half of them are junk. The CEO asks for a task force. Someone proposes buying a new tool. The meeting ends with no resolution and the same problem will be on the agenda next quarter. Here's the truth that neither side wants to admit: the leads are probably fine. The infrastructure that handles them after capture is where the pipeline is dying. ## The math nobody does Most B2B companies lose 40–60% of their viable leads to post-capture failures — slow follow-up, wrong routing, no qualification at capture, and generic responses that fail to convert interest into a meeting. Run this math on your own funnel: Stage Your number Typical mid-market Monthly form submissions \_\_\_ 200 Contacted within 5 minutes \_\_\_ 35% (70 leads) Routed to the correct rep \_\_\_ 75% (52 leads) Rep had qualifying context on first call \_\_\_ 40% (21 leads) Meeting booked \_\_\_ 60% of those (12 meetings) 200 leads. 12 meetings. A 6% form-to-meeting rate. Not because the leads were bad — because 188 of them were handled poorly by the infrastructure between the form and the phone. Now run the same math with optimized infrastructure: Stage Optimized Monthly form submissions 200 (same) Contacted within 60 seconds 95% (190 leads) Routed to the correct rep 95% (180 leads) Rep had qualifying context on first call 100% (180 leads) Meeting booked 35% of those (63 meetings) 200 leads. 63 meetings. Same traffic. Same ad spend. Same reps. 5x the meetings. The difference is entirely in what happens after the form submit. The CEO doesn't need more leads. The CEO needs the leads you already have to become meetings. It's a paradox. Fixing post-capture infrastructure is higher-leverage and lower-cost than generating more leads. But teams keep investing in lead generation for three reasons. **Lead volume is the metric that's easiest to move and easiest to report.** Spend more on ads, get more leads. The dashboard goes up. Everyone feels productive. Whether those leads become meetings is someone else's problem — and it's a problem that's harder to measure, harder to report, and harder to attribute to any one team. **Nobody owns the post-capture layer.** Marketing owns the forms. Sales owns the CRM. RevOps owns the integrations. Nobody owns the 60 seconds between form submission and first response. It's a shared responsibility — which means it's nobody's responsibility. **The problem is invisible.** If you don't measure speed-to-lead, you don't know it's 4 hours. If you don't track routing accuracy, you don't know 25% of leads go to the wrong rep. If you don't measure form-to-meeting rate, you can't see that 94% of your marketing investment is being wasted between the form and the calendar. You can't fix what you can't see. And most companies can't see their post-capture performance. After working with hundreds of B2B companies, the same four problems show up in almost every funnel: **Speed-to-lead is too slow.** The average B2B company takes 42 minutes to respond to an inbound lead. The best take under 60 seconds. A lead contacted in under 1 minute converts at 3–5x the rate of one contacted at 30 minutes. This is the single highest-leverage fix available. **Routing is dumb.** Round-robin treats every lead the same. An enterprise lead from a Fortune 500 company gets the same treatment as a student doing research. The enterprise lead goes to a junior SDR who doesn't know how to handle the conversation. The student goes to a senior AE who wastes 10 minutes before realizing it's not a fit. Attribute-based routing — territory, deal size, product interest, availability — fixes this immediately. **No qualification at capture.** The form collects name, email, and company. The SDR spends the first 5 minutes of every call asking: What's your budget? What's your timeline? How big is your team? What are you trying to solve? These are questions the form should have asked. By the time the SDR qualifies the lead, the high-intent buyer has already talked to a competitor who responded faster and smarter. **The first response is generic.** "Thanks for reaching out! Someone from our team will be in touch shortly." This tells the lead nothing useful — who's going to help them, when they'll hear back, or that anyone actually read what they submitted. A personalized response — "Hi Sarah, I see you're evaluating lead routing for your 200-person sales team. I've connected you with Mike on our enterprise team. Here's his calendar" — converts at 2–3x the rate. The instinct when leads aren't converting is to hire more SDRs, buy more tools, or generate more leads. All three address symptoms. None address the root cause. The root cause is that the infrastructure between form submission and sales conversation was never designed — it was assembled from default CRM settings, Zapier automations, and good intentions. It works well enough at 50 leads a month. At 200+, the cracks become canyons. The fix is a lead ops layer that handles capture, qualification, routing, and response as one connected system. Not more tools — fewer tools, better connected. Not more humans in the loop — automation that handles the repeatable parts so humans can focus on the conversations. Surface is the infrastructure layer. Smart forms that qualify at capture. Attribute-based routing that matches leads to the right rep. Instant personalized response within 60 seconds. Embedded scheduling so the lead books before they close the tab. All in one system, replacing the Zapier chains and CRM workarounds that are currently leaking your pipeline. You're getting enough leads. The question is whether the infrastructure that handles them is good enough to convert them. If your form-to-meeting rate is under 20%, the answer is no — and that's what Surface was built to fix. --- # You're Probably Paying Too Much for Leads That Don't Convert | Surface Labs URL: https://surface.thesurface.network/blog/you-re-probably-paying-too-much-for-leads-that-don-t-convert Your CPL looks fine. $80 from Google Ads. $120 from LinkedIn. $60 from content syndication. Marketing reports these numbers every month and they're within industry benchmarks. Nobody raises a flag. But here's the number nobody reports: what does it cost to get a lead that actually books a meeting? Not a form submission. Not an MQL. A real conversation between a qualified buyer and the right rep on your team. That number is almost always 5–10x higher than your CPL — and it's the one that actually determines whether your marketing spend is working. CPL tells you how much you paid for a form submission. It's easy to measure, easy to benchmark, and easy to optimize. It's also deeply misleading because it treats every form submission as equal. A $80 Google Ads lead who's a VP at a 500-person company evaluating this quarter is not the same as an $80 Google Ads lead who's a student researching a class project. Both cost $80. One is worth pursuing. The other burned $80 plus the enrichment cost, the SDR's time, and the rep's attention. CPL doesn't differentiate. Cost per meeting does. Metric What you report What's actually happening Monthly ad spend $50,000 $50,000 Leads generated 400 400 CPL $125 $125 Leads that get a timely response (under 5 min) Not tracked 160 (40%) Leads routed to the correct rep Not tracked 120 (75% of contacted) Leads where rep had qualifying context Not tracked 50 (42% of correctly routed) Meetings booked Maybe tracked 22 **Cost per meeting booked** **Not reported** **$2,273** $125 CPL sounds efficient. $2,273 per meeting is not. The gap between those two numbers is where your marketing budget is leaking — and it's leaking in the infrastructure between form submission and sales conversation, not in the ads. **Leak 1: Leads that don't get a fast response.** 60% of your leads are contacted after the 5-minute window where conversion rates are highest. Those leads cost the same to acquire but convert at 1/3 to 1/5 the rate. You're paying full price for leads and then degrading their value by responding too slowly. **Leak 2: Leads that go to the wrong rep.** 25% of leads get round-robined to a rep who doesn't match their territory, deal size, or product interest. The rep either mishandles the conversation or reassigns — adding hours of delay. Those leads cost the same to acquire and produce a fraction of the meetings. **Leak 3: Leads that arrive without qualification data.** The rep calls with no context — doesn't know the lead's budget, timeline, company size, or use case. The first 5 minutes of the call are wasted on questions the form should have asked. The lead gets impatient. The conversation feels like an interrogation, not a consultation. **Leak 4: Leads that get a generic response.** "Thanks for reaching out, someone will be in touch shortly." The lead feels like a number, not a person. They close the tab and talk to the competitor who responded with a personalized message and a direct scheduling link. Each leak doesn't just lose that individual lead — it inflates the cost of every meeting you do book. When you lose 60% of your leads to infrastructure failures, the 40% that do convert are carrying the full cost burden. Shift your optimization target from "reduce cost per lead" to "reduce cost per meeting booked." This changes which levers you pull. Lever Impact on CPL Impact on cost per meeting Tighten ad targeting CPL may increase (smaller audience) Cost per meeting likely decreases (better-fit leads convert at higher rates) Improve speed-to-lead No impact on CPL Major reduction in cost per meeting — leads contacted in under 60 seconds convert 3–5x higher Fix routing accuracy No impact on CPL Meaningful reduction — right rep = higher conversion, no reassignment delays Add qualification to forms CPL may increase slightly (fewer completions) Major reduction — reps get qualified leads with context, conversion rate jumps Connect scheduling to routing No impact on CPL Significant reduction — eliminating the scheduling gap recovers 15–25% of leads that would have gone cold Notice the pattern: the levers that most reduce cost per meeting don't touch your ads at all. They're all post-capture infrastructure improvements. You can cut your cost per meeting in half without changing a single ad campaign. \[IMAGE: A waterfall chart showing $50K ad spend → 400 leads ($125 CPL) → progressive losses at each stage (slow response, wrong routing, no qualification, generic response) → 22 meetings ($2,273 each). Then a second waterfall showing same $50K → 400 leads → minimal losses → 52 meetings ($962 each). White background, blue (`#4F6DF5`) accent, flat design.\] Surface is the infrastructure that plugs the leaks — capture with qualification, attribute-based routing, instant personalized response, and embedded scheduling. Every fix in this post is what Surface does by default. If your marketing team reports CPL and your leadership team is happy, ask them one question: "What's our cost per meeting booked?" If nobody knows the answer, that's the most expensive blind spot in your budget. Surface makes it visible — and then makes it smaller. --- # You're Probably Spending $70K+ a Year on Marketing Tools. Here's Why. | Surface Labs URL: https://surface.thesurface.network/blog/you-re-probably-spending-70k-a-year-on-marketing-tools-here-s-wh Pull up your company's credit card statement and search for the marketing tools. Not just the big ones — all of them. The CRM. The marketing automation platform. The form tool. The enrichment provider. The scheduling tool. The analytics platform. The ABM tool. The intent data provider. Zapier. The one-off tools someone on the team signed up for that are still billing monthly. Add them up. If you're a B2B company between $5M and $100M in revenue, the number is almost certainly north of $70K per year. For companies on enterprise tiers with larger databases, it's $120K–$200K+. The question isn't whether you're spending this much. You are. The question is whether you're getting proportional value — or whether a significant chunk of that spend is going to tools you barely use, tools that overlap, or tools that exist solely to connect other tools. Here's the typical marketing tool stack for a mid-market B2B company and what it actually costs: Tool category Common tools Annual cost range CRM Salesforce, HubSpot CRM $6,000–$36,000 Marketing automation HubSpot Marketing Hub, Marketo, Pardot $9,600–$48,000 Enrichment / intent data Clearbit, ZoomInfo, 6sense, Bombora $12,000–$60,000 Form / landing page tools Typeform, Unbounce, Instapage $1,200–$6,000 Scheduling Calendly, Chili Piper $1,200–$12,000 Middleware / automation Zapier, Make, Tray.io $1,200–$6,000 Analytics / attribution Google Analytics, Mixpanel, Bizible $0–$24,000 Misc (chat, ABM, surveys, etc.) Drift, Terminus, Typeform $6,000–$24,000 **Low end total: ~$37K/year.** This is a lean stack — mostly HubSpot with a few add-ons. **Mid range: ~$70K–$100K/year.** This is the typical mid-market setup with Salesforce + marketing automation + enrichment. **Enterprise range: $120K–$200K+/year.** Multiple enterprise tiers, large contact databases, ABM tools, and intent data providers. These numbers don't include headcount. A Marketo admin, a Salesforce admin, and a marketing ops manager add $200K–$350K in salary. The total cost of the marketing technology function — tools plus people to run them — easily exceeds $300K at most mid-market companies. Cost alone isn't the issue. The issue is that most teams use a fraction of what they pay for. HubSpot Marketing Hub Enterprise includes adaptive testing, predictive lead scoring, custom behavioral events, and multi-touch attribution. Most teams on Enterprise use email, forms, workflows, and basic reporting — features available on the Professional tier at half the price. ZoomInfo contracts often include thousands of credits per month. Most teams use 20–40% of their allocation. The unused credits don't roll over. Marketo's program canvas supports nested campaigns, revenue cycle modeling, and advanced segmentation. Most implementations use basic email programs and a single scoring model. The pattern is consistent: teams buy the enterprise tier because they think they'll grow into it, and then they don't — because the advanced features require specialized ops knowledge that the team doesn't have and can't easily hire for. Beyond underutilization, many tools in the stack overlap: HubSpot Marketing Hub has forms — but the team also pays for Typeform because "the design is better." Both capture the same leads to the same CRM. Salesforce has workflow automation — but the team also pays for Zapier because "it's easier." Both route data between the same systems. HubSpot has meeting scheduling — but the team also pays for Calendly because "reps prefer it." Both book the same meetings. Each overlap costs $1,200–$6,000/year in duplicate subscriptions plus the maintenance cost of keeping both tools in sync. Strip the stack down to what drives revenue and ask: what are we paying for, and what does it produce? Most mid-market B2B companies need four things from their marketing technology: a way to capture and qualify leads in real time, a way to route them to the right rep instantly, a way to nurture leads that aren't ready to buy, and a CRM to manage the pipeline. That's it. Everything else is either a component of one of those four functions or a nice-to-have that doesn't directly drive pipeline. The problem is that most stacks evolved tool-by-tool to address symptoms instead of being architected around these four functions. The result is 8–12 tools doing the job of 3–4, with middleware gluing them together and ops teams maintaining the connections. Surface consolidates the capture, qualification, and routing layer into one system — replacing the form tool, the middleware, and the scheduling tool in many stacks. It connects to your CRM natively, which means the CRM and a nurture tool (HubSpot, Marketo, or any email platform) complete the stack. If your annual marketing tool spend is north of $70K and a meaningful portion goes to tools that overlap, tools you barely use, or middleware that exists to connect other tools, there's consolidation opportunity. Surface was built to be the layer that eliminates the most waste. --- # You're Setting Up Your Forms the Same Way You Did in 2020. That's a Problem. | Surface Labs URL: https://surface.thesurface.network/blog/you-re-setting-up-your-forms-the-same-way-you-did-in-2020-that-s-a-problem Name. Email. Company. Job title. "How did you hear about us?" Submit. That was a fine form in 2020. It's costing you pipeline in 2026. Not because forms are dead. They're not. Forms are still the highest-intent conversion point on most B2B websites. The problem is that the way teams build and use forms hasn't changed — while everything around them has. Your ads are smarter. Your CRM is more complex. Your buyers expect instant responses. But your form still dumps a name and email into a queue and hopes someone follows up. **It collects the wrong data.** Name, email, company, and a "tell us about your needs" text box gives your reps almost nothing to work with. They can't qualify, they can't prioritize, and they can't have a good first conversation without 15 minutes of research. **It treats every lead the same.** A VP of Sales at a 500-person SaaS company and a marketing intern filling it out for a class project both get the same form, the same confirmation page, and the same follow-up sequence. Your best leads get the same experience as your worst. **It's disconnected from everything downstream.** The form collects data. Then a separate tool enriches it. Then a CRM workflow scores it. Then another workflow routes it. Then the rep sends a booking link. Five steps, five tools, five places where it breaks. **It doesn't capture drop-offs.** Someone fills in three fields and gets distracted. Closes the tab. In a 2020 form, that lead never existed. No record. No follow-up. Gone. The form isn't just a data collection tool anymore. It's the start of your entire lead ops flow. Here's what that looks like when it's built right: - **Conditional logic.** Different prospects see different questions. An enterprise lead gets asked about team size and use case. An SMB lead gets a simpler path. The form adapts instead of showing everyone the same ten fields. - **Real-time enrichment.** The moment someone types their email, company data gets pulled automatically — employee count, industry, revenue, tech stack. The form gets smarter without adding more fields. - **Inline qualification.** AI scores the lead against your ICP during the form fill, not hours later in a CRM workflow. By the time they hit submit, the system already knows if they're qualified. - **Smart routing built in.** Enrichment data plus form responses determine which rep gets the lead. No round robin. No generic assignment rules. The routing decision happens before the thank-you page loads. - **Scheduling inside the form.** The right rep's calendar shows up on the last step. The prospect books before they leave. No follow-up email. No booking link. No delay. - **Drop-off capture.** Partial submissions get saved automatically. A name and email from an abandoned form is enough to trigger a follow-up workflow. Warm leads don't vanish. - **Spam filtering during the fill.** Disposable emails, bot submissions, and junk get caught in real time. They never reach your CRM. Your reps never see them. Every form that doesn't enrich is making your reps slow. Every form that doesn't qualify is wasting sales capacity on junk leads. Every form that doesn't route is sending enterprise leads to the wrong rep. Every form that doesn't schedule is adding a day of delay before a meeting gets booked. Every form that doesn't capture drop-offs is losing warm leads you already paid for. Stack all of that together and you're looking at a lead-to-meeting conversion rate that's half of what it could be. Surface Labs was built to replace the 2020 form with a modern lead ops layer. One system that handles forms, enrichment, qualification, routing, spam filtering, scheduling, and drop-off capture — all inside the form experience. If your current form still dumps a name and email into a CRM queue and waits for a human to do the rest, it's worth seeing what the alternative looks like. --- # You Shouldn't Need 5 Tools to Handle One Lead | Surface Labs URL: https://surface.thesurface.network/blog/you-shouldn-t-need-5-tools-to-handle-one-lead A visitor fills out your demo request form. Here's what happens next in the average B2B company: **Tool 1:** Typeform captures the submission. **Tool 2:** Zapier pushes the data to HubSpot. **Tool 3:** Clearbit enriches the lead with company data. **Tool 4:** A HubSpot workflow routes the lead to a rep (or tries to — it round-robins because the routing logic can't handle anything more complex). **Tool 5:** The rep gets a Slack notification, opens the CRM, reviews the lead, and manually sends a Calendly link. Five tools. Three integrations. Two potential failure points. And the lead is still waiting for a human to notice they exist. This isn't a broken system. This is the default system. It's how most B2B companies handle inbound leads because each tool was adopted to solve a specific problem, and nobody stepped back to ask whether one tool could solve all of them. The direct costs are obvious — subscription fees for each tool, plus Zapier task costs for the middleware. Most teams spend $500–$2,000/month just on the stack between form and CRM. But the indirect costs are bigger: Cost What's happening Annual impact **Latency** Each tool-to-tool handoff adds 1–5 minutes. A 5-tool chain adds 5–20 minutes before the lead is even assigned to a rep. 3–5x lower contact rate vs. sub-60-second response **Failure risk** Each integration is a failure point. A Zapier that breaks, a webhook that times out, an API rate limit that silently drops leads. 5–15% of leads lost to silent integration failures per quarter **Maintenance** Any change — new CRM field, updated routing rules, different form — requires updating multiple tools and testing every connection. 5–10 hours/week of ops time spent maintaining integrations **Visibility gap** No single tool sees the full journey. Form data is in one system, routing data in another, outcomes in a third. No way to measure cost per meeting or identify where leads drop off **Debugging time** When a lead doesn't get routed correctly, finding the failure requires checking each tool's logs individually. 30–60 minutes per incident, happening weekly The total cost of the 5-tool chain isn't $500–$2,000/month in subscriptions. It's tens of thousands of dollars per year in lost leads, wasted ops time, and slower conversion — all because the tools weren't designed to work as one system. Nobody set out to build a 5-tool lead flow. It happened incrementally: "We need a form tool." Typeform. "We need to get form data into the CRM." Zapier. "We need better lead data." Clearbit. "We need to route leads to reps." CRM workflow. "We need faster notifications." Slack integration. Each decision made sense individually. But collectively, they created an architecture where no single tool is responsible for the lead experience and no single team can see or control the full flow. The tell is when someone asks "what happens after a lead fills out our form?" and nobody can answer confidently without checking three dashboards. One tool doesn't mean one tool for everything — you still need a CRM, you still need an ad platform, you still need a website. "One tool" means one tool for the lead ops layer — the capture-to-meeting flow that currently requires 5. In a consolidated setup: **The form captures and qualifies.** Multi-step, conditional logic, qualifying questions built in. No separate form tool needed. **Enrichment runs at capture.** Company data is appended in real time, supplementing the form responses. No separate enrichment integration needed. **Routing happens instantly.** The lead is matched to the right rep based on form data + enrichment — territory, deal size, product interest, availability. No CRM workflow needed. **Response fires immediately.** Personalized message within 60 seconds — rep's name, reference to what the lead asked about, scheduling link. No separate notification tool needed. **The CRM gets a clean, routed, enriched record.** One sync, one integration, one record. The CRM does what it's good at — pipeline management and reporting — while the lead ops layer does everything upstream. \[IMAGE: A simple comparison. Left side: 5 disconnected tool icons (Form → Zapier → CRM → Enrichment → Slack) with dotted lines between them and a label "5 tools, 3 integrations, 15+ min latency." Right side: one unified icon labeled "Lead Ops" with a single arrow to a CRM icon and a label "1 tool, 1 integration, < 60 sec." White background, blue (`#4F6DF5`) accent, flat design.\] Ask yourself these three questions: **Can you trace a lead from form submit to meeting booked without checking more than one system?** If no, your tools aren't connected well enough to give you visibility. **Can you change a routing rule and have it take effect in under 5 minutes?** If no, your routing logic is locked inside a tool that's too complex or too disconnected to be agile. **If one integration breaks tonight, will you know before a lead is lost?** If no, your system has silent failure points that are costing you leads you'll never know about. If you answered "no" to any of these, you're paying the 5-tool tax. Surface replaces the 5-tool chain with one lead ops layer — capture, qualification, enrichment, routing, response, and CRM sync in a single system. One tool to manage. One integration to maintain. One place to see the full lead journey. If your lead flow currently requires a Zapier flowchart to explain, Surface was built to replace it. --- # Book a Demo | Surface Labs URL: https://surface.thesurface.network/book-a-demo - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Surface CLI | Run Marketing Agents from Your Terminal URL: https://surface.thesurface.network/cli Surface CLI ## Inspect, launch, and optimize campaigns from your terminal Turn buyer signals into campaigns, run agents, and inspect results without leaving your terminal. surface: surface-demo Surface CLI workspace: surface-demo status: connected Describe a task or run \`help\` to see available commands. ## See what Surface CLI can do Use one focused terminal loop to inspect buyer signals, orchestrate agents, launch campaigns, and review every action. 01 ### Launch campaigns from your terminal Start with the buyer patterns already in your funnel, then have Surface build the audience, landing page, ads, and attribution in one coordinated run. [Learn more](https://www.withsurface.com/platform/content-campaigns) $ surface launch --from-signals --channel all Reading 248 high-confidence buyer signals ✓ Audience enriched ✓ Landing page drafted ✓ Paid and organic assets created ✓ Attribution connected Campaign ready for review 02 ### Orchestrate every marketing agent Use one command surface for research, content, ads, lead operations, and reporting while every agent works from the same shared context. [Learn more](https://www.withsurface.com/mcp) $ surface agents list --active AGENT STATE LAST ACTION buyer-research running 12s ago content-campaign ready 38s ago paid-media optimizing 1m ago lead-enrichment running 3s ago attribution connected now 03 ### Review every action before it ships Inspect the campaign plan, compare proposed changes, and approve the exact actions agents can take before anything reaches a customer. [Learn more](https://www.withsurface.com/use-cases) $ surface review campaign enterprise-nurture Reviewing 8 proposed campaign actions 1\. Publish landing-page variant 2\. Sync enriched audience to CRM 3\. Launch paid-search experiment 4\. Start sales follow-up sequence Approval required: run \`approve\` to continue --- # Hiring | Surface Labs URL: https://surface.thesurface.network/company/hiring - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Content Engineering 101 | Surface Labs URL: https://surface.thesurface.network/content-engineering 01 ## Why the old content playbook broke For a decade, content meant one motion. You ran a keyword-gap analysis in a tool like Semrush, found the terms your competitors ranked for and you did not, briefed a writer on each one, and repeated. It worked because search rewarded volume and the field was not crowded. That playbook is breaking. It is slow, because every brief is a human handoff. It is manual, because nothing compounds when the system is you. And it stops the moment you stop feeding it. Meanwhile a new kind of team, one with strong GTM engineers and a system instead of a calendar, is out-shipping you on every topic that matters.1 02 ## What content engineering actually means Content engineering is a small reframe with large consequences. Treat content like an engineered system, not a publishing calendar. A calendar asks what goes out on Tuesday. A system asks how the whole thing runs without you. Think of it as a supply chain with a lifecycle. You discover what to say. You produce it. You keep it accurate as the world moves. You measure what actually worked. Then you feed that signal back into what you discover next. The output is not a post. It is a loop. 03 ## The system that runs itself The goal is not more automation for its own sake. It is a loop that governs itself: one that discovers topics worth covering, drafts content a human does not have to babysit, and knows when to pull a person in for the judgment only a person has. The division of labor is the whole point. The human guards the strategy: the positioning, the point of view, the calls that need taste. The system does the grunt work: the research, the first drafts, the updates, the measurement. Most teams run this backwards, with people doing the grunt work and no one guarding the strategy. The content-engineering loop. A human enters at one point, strategy, and the system runs the rest. 04 ## What we've seen (the proof) We do not have to theorize about this. We run it on our own brand, and we watch it run across the companies on Surface. 7,000 18,000 LinkedIn followers In four months, running this exact content system on our own brand.2 100+ companies on Surface Because their traffic and UTMs run through us, we can tell which content earns pipeline, not just which ranks.3 $40M+ pipeline processed Every piece is graded on the pipeline it influences, not on pageviews. 05 ## How Surface does this for you Surface is this system: it discovers topics from your live demand, drafts against your positioning, and ties every piece back to pipeline. You keep the strategy. Surface runs the loop. Sources 1. 1[Surface internal benchmark across 100+ customers.](https://withsurface.com/customers) 2. 2[Surface brand LinkedIn analytics, 2026.](https://linkedin.com/company/surface-labs) 3. 3[Aggregated Surface customer traffic and UTM data, 2026.](https://withsurface.com/customers) --- # Customer Stories | Surface Labs URL: https://surface.thesurface.network/customers Customer stories ## How leading teams turn better marketing into pipeline [](https://www.withsurface.com/customers/giga)[](https://www.withsurface.com/customers/nextiva) And hundreds more marketing wins across teams running on Surface. [ **Maddy Fennessy**Growth Marketing Lead, Metronome > “We feel pretty embedded in Surface, especially since we did the PLG stuff there. I would consider Surface to be like a pretty core part of what is running our website, which is a good thing.” ](https://www.withsurface.com/customers) [ **Shubh Agrawal**San Francisco, Valley > “If we turned off Surface tomorrow, we'd lose a lot of inbound. We're almost entirely inbound-driven, so Surface is a critical part of how we operate.” ](https://www.withsurface.com/customers/valley) [ **Alexandra Doan**San Francisco, Nextiva > “We actually saw that 37% more users on average converted with the new form that they built for us” ](https://www.withsurface.com/customers/nextiva) [ **Pujun Bhatnagar**CEO, Kintsugi > “We're growing at the speed of light, and Surface is one of the few vendors keeping up with us. I'd pay whatever it takes to solve this problem, and Surface solved it.” ](https://www.withsurface.com/customers/kintsugi) [ **Angela Kou**Chief of Staff, Juicebox > “Whenever I had a feature request, the Surface team would update me throughout the process and follow up after launch to make sure everything was working correctly. It really feels like a white-glove experience.” ](https://www.withsurface.com/customers/juicebox) [ **Ian Christopher**CEO, Galley > “We used Typeform in the early days. It was great but you can tell when a company outgrows it. Surface gives us the mechanics we liked from Typeform, but with enterprise-grade control over brand, format, and functionality.” ](https://www.withsurface.com/customers/galley) > “We're growing at the speed of light, and Surface is one of the few vendors keeping up with us. I'd pay whatever it takes to solve this problem, and Surface solved it.” Pujun Bhatnagar, CEO, Kintsugi Set up once ## Put marketing superintelligence to work for your revenue team. [Talk to sales](https://www.withsurface.com/book-a-demo) --- # Galley Solutions Customer Story | Surface Labs URL: https://surface.thesurface.network/customers/galley Customer story · Galley Solutions See how Galley Solutions used Surface, from the initial challenge and implementation to the final results. 100% Spam leads prevented 30% Lift in qualified leads 1 hr Saved per rep, per demo ## About Galley Solutions Galley Solutions is the creator of the industry's first Culinary Resource Planning (CRP) platform, purpose-built to streamline operations for large commercial kitchens. Galley centralizes everything from recipes to purchasing, procurement, inventory, and production, all within a unified, digital hub. With expanded visibility from ramped-up SEO and paid media campaigns, their inbound funnel began growing fast, but the growing traffic came with its own set of growing pains. ## The Challenge As Galley scaled its inbound marketing efforts, poor form data quality quickly became a bottleneck. HubSpot's out-of-the-box forms started getting flooded: - Bot-generated spam was rampant, overwhelming the team. - There was no effective way to pre-qualify leads before routing them to sales. - The manual cleanup and routing process was slow and developer-dependent, draining time and resources. Ian Christopher, Co-founder & Head of Marketing, recalls: "We were kind of helpless to omit the spam." They needed a solution that could squash spam, surface only legit prospects, and eliminate the need for manual triage. ## The Solution Galley replaced every form on their site with Surface Forms, unlocking immediate and measurable impact. For the first time in our marketing history, we're doing real qualification at the form level. It's changed how we run our inbound funnel. With Surface: - 100% spam prevention: despite a spike in traffic and spam, Surface stopped every bot in its tracks - Deeper lead qualification: built-in decoy submissions, multi-step flows, and discovery questions filtered out low-intent inquiries before they even hit sales - Time savings: sales reps now receive well-qualified leads, saving over an hour per opportunity - Seamless HubSpot integration: structured, clean data flows directly into their CRM, giving Galley full control over data and routing ## The Results We used Typeform in the early days. It was great, but you can tell when a company outgrows it. Surface gives us the mechanics we liked from Typeform, but with enterprise-grade control over brand, format, and functionality. From demo booking to freemium signup, Surface has become Galley's go-to form experience platform. It blocks spam, qualifies better, saves time, and pushes structured data directly into HubSpot, without needing engineering involvement. 📈 30% Lift in Qualified Leads: Galley's inbound funnel now delivers only high-intent, qualified prospects to sales. 🛡️ 100% Spam Leads Prevented: Despite a spike in traffic, Surface stopped every spam submission in its tracks. ⚡ 1 Hour Saved Per Rep, Per Demo: Sales reps now receive fully qualified leads, eliminating manual triage and prep time. Surface Forms feels like an enterprise-grade solution for form experiences. To us, it's the full package: structured data, better UX, and full CRM control. Honestly, Surface just works. It's been a huge boost to our inbound engine, and we're just getting started. [ **Maddy Fennessy**Growth Marketing Lead, Metronome > “We feel pretty embedded in Surface, especially since we did the PLG stuff there. I would consider Surface to be like a pretty core part of what is running our website, which is a good thing.” ](https://www.withsurface.com/customers) [ **Shubh Agrawal**San Francisco, Valley > “If we turned off Surface tomorrow, we'd lose a lot of inbound. We're almost entirely inbound-driven, so Surface is a critical part of how we operate.” ](https://www.withsurface.com/customers/valley) [ **Alexandra Doan**San Francisco, Nextiva > “We actually saw that 37% more users on average converted with the new form that they built for us” ](https://www.withsurface.com/customers/nextiva) [ **Pujun Bhatnagar**CEO, Kintsugi > “We're growing at the speed of light, and Surface is one of the few vendors keeping up with us. I'd pay whatever it takes to solve this problem, and Surface solved it.” ](https://www.withsurface.com/customers/kintsugi) [ **Angela Kou**Chief of Staff, Juicebox > “Whenever I had a feature request, the Surface team would update me throughout the process and follow up after launch to make sure everything was working correctly. It really feels like a white-glove experience.” ](https://www.withsurface.com/customers/juicebox) [ **Ian Christopher**CEO, Galley > “We used Typeform in the early days. It was great but you can tell when a company outgrows it. Surface gives us the mechanics we liked from Typeform, but with enterprise-grade control over brand, format, and functionality.” ](https://www.withsurface.com/customers/galley) Set up once ## Put marketing superintelligence to work for your revenue team. [Book a demo](https://www.withsurface.com/book-a-demo?source=customer-story&customer=galley) --- # Giga Customer Story | Surface Labs URL: https://surface.thesurface.network/customers/giga Customer story · Giga See how Giga used Surface, from the initial challenge and implementation to the final results. 2 weeks Website ported to code 4x Email capture lift Onboarded entire sales team Intelligent scheduler rollout ## About Giga Giga is a Y Combinator-backed AI customer support platform serving consumer marketplaces, fintech, and airlines. Their buyer is exclusively C-suite, and they were scaling paid demand generation aggressively in a competitive market. ## The situation before Surface Their marketing website was built for developer visitors, not the C-suite buyers they needed to convert. Ad spend was scaling but attribution was broken. Click IDs were being stripped mid-flow, leaving marketing unable to prove which spend produced pipeline. Lead scoring was inconsistent. High-value prospects were being scored the same as low-intent traffic. Content marketing was not tied to pipeline, and AI visibility across ChatGPT and Perplexity was flat. They needed a marketing operations layer that could move at product-team velocity without disrupting the marketing team already running paid campaigns. ## What Surface built for Giga 1) The full marketing website and CMS. Giga's full marketing website now runs on Surface CMS, including homepage, product pages, vertical-specific industry pages, and case study pages built for C-suite conversion. 2) Ad landing pages that convert. Multiple landing pages were built and iterated with Giga's paid media partner. Each page is optimized for C-suite conversion with one primary CTA and an embedded form, and each page is iterated against A/B tests. Every page is backed by Surface forms with partial response capture so top-of-funnel intent is not lost. 3) Lead capture with partial response recovery. Surface forms sit on every Giga conversion surface. Multi-step design with progressive profiling captures identity and firmographics, enriches them in real time, and still recovers leads when a visitor abandons mid-flow. 4) AI lead scoring rebuilt. When Giga flagged inconsistent lead scoring, Surface engineering ran a full audit and rebuild in days. The new model was tested against historical form responses and surfaced previously misscored high-fit leads. 5) Attribution and measurement fixed. Surface diagnosed a broken attribution persistence issue that was hiding paid conversions across the homepage-to-contact flow. The fix now runs attribution end-to-end through form submission, making ad spend trackable to pipeline. ## Results - Full marketing site and CMS shipped without an in-house web team. - Website ported to code in 2 weeks. - 4x lift in email capture. - 10+ sales reps onboarded to intelligent scheduler in under one day. - No seat-based pricing, so growth does not trigger per-rep overage costs. - Multiple landing page iterations across paid campaigns, each attributed and A/B tested. - Lead scoring rebuild recovered previously invisible pipeline within days of deployment. - Paid spend now runs under closed-loop attribution. - Conversion surfaces now recover leads that would have been lost to form abandonment. [ **Maddy Fennessy**Growth Marketing Lead, Metronome > “We feel pretty embedded in Surface, especially since we did the PLG stuff there. I would consider Surface to be like a pretty core part of what is running our website, which is a good thing.” ](https://www.withsurface.com/customers) [ **Shubh Agrawal**San Francisco, Valley > “If we turned off Surface tomorrow, we'd lose a lot of inbound. We're almost entirely inbound-driven, so Surface is a critical part of how we operate.” ](https://www.withsurface.com/customers/valley) [ **Alexandra Doan**San Francisco, Nextiva > “We actually saw that 37% more users on average converted with the new form that they built for us” ](https://www.withsurface.com/customers/nextiva) [ **Pujun Bhatnagar**CEO, Kintsugi > “We're growing at the speed of light, and Surface is one of the few vendors keeping up with us. I'd pay whatever it takes to solve this problem, and Surface solved it.” ](https://www.withsurface.com/customers/kintsugi) [ **Angela Kou**Chief of Staff, Juicebox > “Whenever I had a feature request, the Surface team would update me throughout the process and follow up after launch to make sure everything was working correctly. It really feels like a white-glove experience.” ](https://www.withsurface.com/customers/juicebox) [ **Ian Christopher**CEO, Galley > “We used Typeform in the early days. It was great but you can tell when a company outgrows it. Surface gives us the mechanics we liked from Typeform, but with enterprise-grade control over brand, format, and functionality.” ](https://www.withsurface.com/customers/galley) Set up once ## Put marketing superintelligence to work for your revenue team. [Book a demo](https://www.withsurface.com/book-a-demo?source=customer-story&customer=giga) --- # Juicebox Customer Story | Surface Labs URL: https://surface.thesurface.network/customers/juicebox Customer story · Juicebox See how Juicebox used Surface, from the initial challenge and implementation to the final results. 5,800+ Leads captured 50+ Hours saved per week 57% Leads enriched automatically ## About Juicebox Juicebox is redefining how modern teams recruit talent. Their AI-powered product, PeopleGPT, lets users search across 800M+ professional profiles using natural language. Backed by $36 million in funding led by Sequoia Capital, Juicebox is trusted by thousands of companies as a foundational tool in the modern recruiting stack. ## The Challenge When PeopleGPT went viral on LinkedIn, thousands of recruiting teams wanted a closer look. Juicebox turned that virality into a full-blown growth wave. The team needed an inbound solution that could keep up with that momentum: capturing every lead, filtering spam, and routing qualified prospects instantly. Before Surface, the team was using basic Typeform forms and manual follow-ups, leading to lost leads and hours of admin work. People were signing up fast, but there was no real workflow from signup to demo. It wasn't automated, it was a lot of manual back and forth. Angela Kou, Chief of Staff, Juicebox They needed a way to turn inbound volume into consistent, qualified meetings without adding headcount or losing control of the funnel. ## Why They Chose Surface Juicebox implemented Surface Forms to create an automated inbound flow that captured, qualified, and routed leads directly to the right account executive. Today, implementing new forms is as simple as adding a single line of code to their website. Surface's decision-tree builder and AI-driven logic workflows were originally a feature request from Juicebox. The team shipped it within weeks, making it simple to design complex routing without Zapier or manual integrations. Whenever I had a feature request, the Surface team would update me throughout the process and follow up after launch to make sure everything was working correctly. It really feels like a white-glove experience. ## How Surface Delivered Juicebox implemented Surface Forms across their entire inbound funnel. When new features rolled out, the onboarding was seamless with personal support and proactive follow-ups from the Surface team to ensure smooth deployment. Before the spam-filtering feature, each AE was getting at least two spammy invites a day. Now Surface filters out personal and spam emails automatically, freeing up hours every week. During Juicebox's Series A announcement, the team captured thousands of inbound leads without a single missed submission. ## Key Results Surface Labs became the backbone of Juicebox's inbound motion. - 5,800+ leads and 7,000+ submissions processed with zero downtime - All AEs' calendars fully booked after the Series A launch - 50+ hours/week saved by filtering spam and eliminating manual routing and updates - Improved routing logic ensures every lead is assigned to the correct AE instantly If we turned off Surface tomorrow, we'd lose a lot of inbound. We're almost entirely inbound-driven, so Surface is a critical part of how we operate. Angela Kou, Chief of Staff, Juicebox [ **Maddy Fennessy**Growth Marketing Lead, Metronome > “We feel pretty embedded in Surface, especially since we did the PLG stuff there. I would consider Surface to be like a pretty core part of what is running our website, which is a good thing.” ](https://www.withsurface.com/customers) [ **Shubh Agrawal**San Francisco, Valley > “If we turned off Surface tomorrow, we'd lose a lot of inbound. We're almost entirely inbound-driven, so Surface is a critical part of how we operate.” ](https://www.withsurface.com/customers/valley) [ **Alexandra Doan**San Francisco, Nextiva > “We actually saw that 37% more users on average converted with the new form that they built for us” ](https://www.withsurface.com/customers/nextiva) [ **Pujun Bhatnagar**CEO, Kintsugi > “We're growing at the speed of light, and Surface is one of the few vendors keeping up with us. I'd pay whatever it takes to solve this problem, and Surface solved it.” ](https://www.withsurface.com/customers/kintsugi) [ **Angela Kou**Chief of Staff, Juicebox > “Whenever I had a feature request, the Surface team would update me throughout the process and follow up after launch to make sure everything was working correctly. It really feels like a white-glove experience.” ](https://www.withsurface.com/customers/juicebox) [ **Ian Christopher**CEO, Galley > “We used Typeform in the early days. It was great but you can tell when a company outgrows it. Surface gives us the mechanics we liked from Typeform, but with enterprise-grade control over brand, format, and functionality.” ](https://www.withsurface.com/customers/galley) Set up once ## Put marketing superintelligence to work for your revenue team. [Book a demo](https://www.withsurface.com/book-a-demo?source=customer-story&customer=juicebox) --- # Kintsugi Customer Story | Surface Labs URL: https://surface.thesurface.network/customers/kintsugi Customer story · Kintsugi See how Kintsugi used Surface, from the initial challenge and implementation to the final results. 11K+ Leads captured 82% De-anonymized leads 91% Leads enriched automatically ## About Kintsugi Kintsugi is transforming how fast-growing businesses handle sales tax. Their software platform automates everything from real-time nexus monitoring to registration, filing, exemption certificates, and voluntary disclosure agreements. After growing from 3 to 57 employees in under a year, the team needed to scale fast, without letting inbound chaos slow them down. ## The Challenge As Kintsugi ramped up its go-to-market motion, the sales team hit a painful blocker: inbound spam. "People were spamming our 'Book a Demo' button, and it wasn't just noise, it was causing real chaos for our sales team," said Pujun, CEO of Kintsugi. "We knew we had to fix this if we wanted to keep scaling." The team evaluated every vendor from Chili Piper to HubSpot. But none solved the root issue: how to intelligently filter inbound leads, route real ones quickly, and eliminate low-intent noise. ## Why They Chose Surface Kintsugi chose Surface to power their entire inbound funnel: forms, enrichment, lead routing, partial submission capture, and A/B testing. Surface was the only product that solved the problem properly. Every other platform had big promises, but Surface actually delivered. With Surface: - Spam and nefarious bookings were filtered out automatically - Lead data was enriched in real time to qualify and route faster - Partial form submissions were captured and followed up with - A/B tests on the form drove more conversion lift - Customer support exceeded expectations at every turn ## How Surface Delivered Surface didn't just help Kintsugi grow. It gave them control. For PLG-driven teams like us, Surface is a gem. You're missing out if you're using anything else. It's one of those products you don't realize how badly you need, until you have it. We wouldn't be the company we are today without Surface Labs. From form performance to customer support, it's just chef's kiss. Pujun, CEO at Kintsugi ## Key Results - Cleaner inbound pipeline: Spam bookings dropped dramatically - Faster qualification: Sales team focused only on high-quality leads - Conversion lift: A/B testing and partial form captures helped unlock more demos from existing traffic - 11K+ leads captured with 82% de-anonymized and 91% enriched automatically [ **Maddy Fennessy**Growth Marketing Lead, Metronome > “We feel pretty embedded in Surface, especially since we did the PLG stuff there. I would consider Surface to be like a pretty core part of what is running our website, which is a good thing.” ](https://www.withsurface.com/customers) [ **Shubh Agrawal**San Francisco, Valley > “If we turned off Surface tomorrow, we'd lose a lot of inbound. We're almost entirely inbound-driven, so Surface is a critical part of how we operate.” ](https://www.withsurface.com/customers/valley) [ **Alexandra Doan**San Francisco, Nextiva > “We actually saw that 37% more users on average converted with the new form that they built for us” ](https://www.withsurface.com/customers/nextiva) [ **Pujun Bhatnagar**CEO, Kintsugi > “We're growing at the speed of light, and Surface is one of the few vendors keeping up with us. I'd pay whatever it takes to solve this problem, and Surface solved it.” ](https://www.withsurface.com/customers/kintsugi) [ **Angela Kou**Chief of Staff, Juicebox > “Whenever I had a feature request, the Surface team would update me throughout the process and follow up after launch to make sure everything was working correctly. It really feels like a white-glove experience.” ](https://www.withsurface.com/customers/juicebox) [ **Ian Christopher**CEO, Galley > “We used Typeform in the early days. It was great but you can tell when a company outgrows it. Surface gives us the mechanics we liked from Typeform, but with enterprise-grade control over brand, format, and functionality.” ](https://www.withsurface.com/customers/galley) Set up once ## Put marketing superintelligence to work for your revenue team. [Book a demo](https://www.withsurface.com/book-a-demo?source=customer-story&customer=kintsugi) --- # Nextiva Customer Story | Surface Labs URL: https://surface.thesurface.network/customers/nextiva Customer story · Nextiva See how Nextiva used Surface, from the initial challenge and implementation to the final results. 37% Lift in conversion 70% More email collected 30+ Pages tracked ## About Nextiva Nextiva is a leading cloud communications and collaboration platform that provides cutting-edge solutions to businesses. Their services empower companies to streamline communication and deliver exceptional customer experiences. As a pioneer in their field, Nextiva continuously seeks innovative tools to optimize their marketing efforts and drive better ROI from campaigns. ## The Challenge Nextiva's marketing efforts, particularly on PPC landing pages, faced a common yet critical challenge: - Low Conversion Rates: Despite significant investments in campaigns, conversions remained below target levels. - Unqualified Leads: Manual lead management efforts were inefficient, with a significant percentage of leads being unqualified or spam. - Fragmented Tools: Nextiva needed a unified platform to manage, track, and nurture inbound leads seamlessly. - Missed Engagement Opportunities: Delayed follow-ups meant losing leads that could have converted with timely communication. To remain ahead of competitors, Nextiva needed a partner that could provide a comprehensive, AI-driven solution for their lead management challenges. ## Why Nextiva Chose Surface Labs In November 2023, Nextiva turned to Surface Labs, the ultimate inbound lead conversion platform, to solve these pain points. Surface Labs' unique combination of AI-powered workflows, customizable forms, and intelligent lead scoring provided the perfect fit for Nextiva's needs. The platform offered: - Ease of Integration: Compatibility with existing CRMs, including HubSpot. - On-Brand Customization: Multi-step forms designed to maintain Nextiva's brand integrity. - AI Automation: Automated workflows to engage leads at the right time via email/SMS. - Advanced Lead Filtering: AI to detect and remove spam, ensuring only qualified leads reached the sales team. ## How Surface Labs Delivered Surface Labs transformed Nextiva's lead generation with AI-driven workflows, personalized forms, and real-time lead scoring, creating a seamless and scalable approach to convert visitors into high-quality leads. - High-Converting Multi-Step Forms: Surface Labs designed intuitive, brand-aligned forms that improved user experience and reduced drop-offs. These forms collected significantly more email data by cutting down the number of fields while also improving form conversion rates. - Intelligent Lead Scoring: Algorithms scored leads in real-time, filtering out spam and repeat entries. Sales teams could now prioritize high-value prospects without the noise. - Automated Lead Engagement: Surface Labs introduced lead-engagement workflows that automated follow-ups via email, ensuring Nextiva engaged leads at the most opportune moments. The workflows also enabled routing leads directly to the right sales representatives, reducing response times. - Insights and Analytics: With the Surface Tag, Nextiva tracked user interactions across 30+ landing pages, gaining actionable insights to optimize campaigns further. ## Key Results 📈 70% More Emails Collected: Nextiva's PPC landing pages became high-performing assets, collecting significantly more emails thanks to optimized forms and workflows. 🚀 37% Lift in Conversions: Real-time A/B testing and advanced personalization drove a substantial increase in lead-to-customer conversions. ⚡ Automated Engagement: Surface Labs' AI agents automated repetitive tasks, enabling sales teams to focus on closing deals rather than chasing leads. ✅ 30+ Pages Tracked: The Surface Tag empowered Nextiva with critical analytics across all landing pages, refining their marketing strategies. ## Nextiva's Success Story Surface Labs transformed Nextiva's inbound marketing by introducing a holistic, AI-powered solution. With cleaner lead pipelines, enhanced workflows, and actionable analytics, Nextiva achieved tangible results in a short time frame. - Seamless Integration: Easy to connect with CRMs and tools like HubSpot. - First-Party Data Collection: High-quality data that complies with privacy regulations. - Dynamic Personalization: Real-time adjustments to forms and workflows based on lead behavior. - Scalable Automation: Effortlessly handles growing lead volumes without compromising quality. [ **Maddy Fennessy**Growth Marketing Lead, Metronome > “We feel pretty embedded in Surface, especially since we did the PLG stuff there. I would consider Surface to be like a pretty core part of what is running our website, which is a good thing.” ](https://www.withsurface.com/customers) [ **Shubh Agrawal**San Francisco, Valley > “If we turned off Surface tomorrow, we'd lose a lot of inbound. We're almost entirely inbound-driven, so Surface is a critical part of how we operate.” ](https://www.withsurface.com/customers/valley) [ **Alexandra Doan**San Francisco, Nextiva > “We actually saw that 37% more users on average converted with the new form that they built for us” ](https://www.withsurface.com/customers/nextiva) [ **Pujun Bhatnagar**CEO, Kintsugi > “We're growing at the speed of light, and Surface is one of the few vendors keeping up with us. I'd pay whatever it takes to solve this problem, and Surface solved it.” ](https://www.withsurface.com/customers/kintsugi) [ **Angela Kou**Chief of Staff, Juicebox > “Whenever I had a feature request, the Surface team would update me throughout the process and follow up after launch to make sure everything was working correctly. It really feels like a white-glove experience.” ](https://www.withsurface.com/customers/juicebox) [ **Ian Christopher**CEO, Galley > “We used Typeform in the early days. It was great but you can tell when a company outgrows it. Surface gives us the mechanics we liked from Typeform, but with enterprise-grade control over brand, format, and functionality.” ](https://www.withsurface.com/customers/galley) Set up once ## Put marketing superintelligence to work for your revenue team. [Book a demo](https://www.withsurface.com/book-a-demo?source=customer-story&customer=nextiva) --- # Numbers Station Customer Story | Surface Labs URL: https://surface.thesurface.network/customers/numbers-station Customer story · Numbers Station See how Numbers Station used Surface, from the initial challenge and implementation to the final results. 30% Increase in pipeline 95% Leads enriched automatically 1 in 3 Qualified leads booked ## About Numbers Station Numbers Station helps companies integrate AI agents into their data pipelines, transforming how structured data is used in product development and analysis. As an early-stage startup with a focused team and a high-growth mindset, every lead counts, and knowing who's visiting their site became a key growth lever. ## The Challenge Before Surface, Numbers Station faced a common GTM blind spot: they had no visibility into who was browsing their website unless a visitor explicitly filled out a demo form. Unless someone scheduled a demo, we had no idea who they were. We were flying blind. The result? Lost pipeline, missed opportunities, and a sales team forced to rely solely on inbound form submissions. ## Why They Chose Surface Surface changed the game by giving the team full visibility into site activity and partial engagement: - Visitor de-anonymization unlocked emails and phone numbers for previously invisible leads - Partial form capture allowed outreach even when visitors didn't finish submitting - Slack alerts pushed new leads directly to the AEs in real-time - Lead enrichment helped qualify and sort high-intent visitors from noise The first thing our AEs do every morning is check the Surface Slack channel. We're booking 1 out of every 3 qualified leads that come through there. ## How Surface Delivered Jake and team are excited about Surface's capabilities: - Automated follow-up for partial leads - Smarter lead scoring - Better spam filtering and qualification tools Time is money for us. Anything that gets us to quality leads faster is huge, and Surface keeps delivering. We're booking meetings with people who never filled out a form. Surface made that possible. It's been a real unlock for our GTM team. Jake Van Asten, Head of GTM at Numbers Station ## Key Results - 30% increase in pipeline from leads who didn't submit a form - Refined ICP based on real visitor data, not assumptions - Higher ROI on paid and organic traffic now that every visitor counts - Booking 1 out of every 3 qualified leads from the Surface Slack channel Surface has saved us time, sharpened our targeting, and significantly increased our pipeline. As a small team, that impact is massive. [ **Maddy Fennessy**Growth Marketing Lead, Metronome > “We feel pretty embedded in Surface, especially since we did the PLG stuff there. I would consider Surface to be like a pretty core part of what is running our website, which is a good thing.” ](https://www.withsurface.com/customers) [ **Shubh Agrawal**San Francisco, Valley > “If we turned off Surface tomorrow, we'd lose a lot of inbound. We're almost entirely inbound-driven, so Surface is a critical part of how we operate.” ](https://www.withsurface.com/customers/valley) [ **Alexandra Doan**San Francisco, Nextiva > “We actually saw that 37% more users on average converted with the new form that they built for us” ](https://www.withsurface.com/customers/nextiva) [ **Pujun Bhatnagar**CEO, Kintsugi > “We're growing at the speed of light, and Surface is one of the few vendors keeping up with us. I'd pay whatever it takes to solve this problem, and Surface solved it.” ](https://www.withsurface.com/customers/kintsugi) [ **Angela Kou**Chief of Staff, Juicebox > “Whenever I had a feature request, the Surface team would update me throughout the process and follow up after launch to make sure everything was working correctly. It really feels like a white-glove experience.” ](https://www.withsurface.com/customers/juicebox) [ **Ian Christopher**CEO, Galley > “We used Typeform in the early days. It was great but you can tell when a company outgrows it. Surface gives us the mechanics we liked from Typeform, but with enterprise-grade control over brand, format, and functionality.” ](https://www.withsurface.com/customers/galley) Set up once ## Put marketing superintelligence to work for your revenue team. [Book a demo](https://www.withsurface.com/book-a-demo?source=customer-story&customer=numbers-station) --- # Quilter AI Customer Story | Surface Labs URL: https://surface.thesurface.network/customers/quilter Customer story · Quilter AI See how Quilter AI used Surface, from the initial challenge and implementation to the final results. Higher Lead quality Less Manual work Smarter Funnel intelligence ## About Quilter AI Quilter AI is a cutting-edge platform focused on transforming underwriting in insurance. As a category-defining company with a highly specific Ideal Customer Profile (ICP), Quilter needed more precision in its demand gen programs than traditional platforms could offer. ## The Challenge Before Surface, Quilter's "Request a Demo" workflow was wide open. Anyone could book a meeting: - There were no guardrails to ensure fit. - Calendars filled up with unqualified prospects. - Data was duplicated and fragmented across tools. We were asking for the same info twice, once in the form, and again in the scheduler," Darin recalls. "Plus, there was no logic layer. Everyone just got the link. The result? Lost pipeline, missed opportunities, and a sales team forced to rely solely on inbound form submissions. ## Why They Chose Surface Surface Forms now powers the critical conversion points across Quilter's funnel: - Pre-Qualification for Demos: Instead of letting anyone book, leads must complete a form that dynamically qualifies them. If they're a fit, they can schedule. If not, they get a thoughtful off-ramp with relevant resources. - Data Enrichment & Deduplication: Whether a lead uses a corporate email or a Gmail address, Surface pulls in firmographic data via ZoomInfo or Apollo to auto-enrich leads behind the scenes. - Consolidated Lead Intelligence: Surface serves as Quilter's de facto master lead dashboard (qualifying, syncing to HubSpot, and auto-filling calendar fields) with zero extra clicks. Now we have all our leads flowing through Surface. It's not just a form anymore. It's where marketing ops happens. ## How Surface Delivered Surface has turned into Quilter's lead ops layer. They're starting to think of it as the place where anonymous traffic becomes qualified pipeline. Darin envisions a future where Surface doesn't just qualify leads: it helps nurture and route them intelligently, too. Partial form fills, for instance, could trigger personalized follow-ups using tools like n8n + Surface. Surface has turned into our lead ops layer. We're starting to think of it as the place where anonymous traffic becomes qualified pipeline. ## Key Results - Higher Lead Quality: Only qualified leads reach the sales team, and the experience is better for both sides. - Less Manual Work: No more stitching together Excel/Airtable sheets. Surface pushes clean, enriched data to HubSpot and the scheduler automatically. - Smarter Funnels: Surface enables new workflows for free signups, newsletter access, and gated content, all with enrichment and lead scoring built in. [ **Maddy Fennessy**Growth Marketing Lead, Metronome > “We feel pretty embedded in Surface, especially since we did the PLG stuff there. I would consider Surface to be like a pretty core part of what is running our website, which is a good thing.” ](https://www.withsurface.com/customers) [ **Shubh Agrawal**San Francisco, Valley > “If we turned off Surface tomorrow, we'd lose a lot of inbound. We're almost entirely inbound-driven, so Surface is a critical part of how we operate.” ](https://www.withsurface.com/customers/valley) [ **Alexandra Doan**San Francisco, Nextiva > “We actually saw that 37% more users on average converted with the new form that they built for us” ](https://www.withsurface.com/customers/nextiva) [ **Pujun Bhatnagar**CEO, Kintsugi > “We're growing at the speed of light, and Surface is one of the few vendors keeping up with us. I'd pay whatever it takes to solve this problem, and Surface solved it.” ](https://www.withsurface.com/customers/kintsugi) [ **Angela Kou**Chief of Staff, Juicebox > “Whenever I had a feature request, the Surface team would update me throughout the process and follow up after launch to make sure everything was working correctly. It really feels like a white-glove experience.” ](https://www.withsurface.com/customers/juicebox) [ **Ian Christopher**CEO, Galley > “We used Typeform in the early days. It was great but you can tell when a company outgrows it. Surface gives us the mechanics we liked from Typeform, but with enterprise-grade control over brand, format, and functionality.” ](https://www.withsurface.com/customers/galley) Set up once ## Put marketing superintelligence to work for your revenue team. [Book a demo](https://www.withsurface.com/book-a-demo?source=customer-story&customer=quilter) --- # Valley Customer Story | Surface Labs URL: https://surface.thesurface.network/customers/valley Customer story · Valley See how Valley used Surface, from the initial challenge and implementation to the final results. 35% Increase in inbound signups 15% Lift in demos booked 150+ Inbound demos per month ## About Valley Valley is building flexible tools for modern revenue and operations teams for LinkedIn outreach automation. The company has grown without relying on paid ads, influencers, or agencies and instead grown through organic and sales-led strategies. As inbound demand scaled, Valley focused on building a clean, high-quality funnel that prioritized lead qualification, enrichment, and routing. ## The Challenge Valley's inbound demand was growing quickly, but the systems behind it weren't keeping up. All inbound traffic came from organic channels such as SEO or the founder's personal brand on LinkedIn. As traffic increased, so did form submissions, but many of those leads were either unqualified or difficult to act on. Before Surface, Valley relied on static website forms and embedded HubSpot calendars. The experience wasn't seamless for users, and it limited the team's ability to control how inbound leads were qualified and handled. Inbound was growing pretty rapidly for us, but it became annoying. We didn't have enough control over qualification, enrichment, or routing, and conversion rates weren't where we wanted them to be. Head of Growth, Valley ## Why They Chose Surface Surface Labs gave Valley a single, unified system to manage inbound from start to finish. Instead of relying on static forms, Valley implemented Surface Forms to create a more engaging, gamified experience that encouraged more visitors to start (and complete) the process. Abstract, intent-based questions helped qualify leads before asking for contact details, increasing engagement at the top of the funnel. Surface also enabled Valley to capture partial form submissions, enrich leads automatically, and route them based on fit, even when a visitor didn't fully convert. Surface dramatically increases the likelihood of a lead giving you their email. Even if they drop off midway, you still have interest data you can act on later. ## How Surface Delivered Valley implemented Surface Forms across their website and inbound touchpoints as their default conversion layer. I always prefer a Surface form over a typical input box. It looks better, feels more premium, and actually gets people to continue through the experience. On the backend, Surface became the central hub for inbound data: - Form submissions and partial responses are sent to Slack in real time - Leads are enriched and scored via webhooks - Data flows into Valley's CRM and email workflows automatically This setup eliminated the need for multiple disconnected tools and reduced the operational burden of maintaining a fragmented stack. ## Key Results Surface Labs became a core part of Valley's inbound growth engine. - Inbound demos increased from ~120/month to 150+ consistently - 35% lift in inbound conversions - Higher lead quality through enrichment and scoring - Reduced tooling costs and operational overhead Surface is our cohesive inbound stack. Website visitors, partial submissions, enrichment, source tracking, it all lives in one place. Shubh Agrawal, Head of Growth, Valley [ **Maddy Fennessy**Growth Marketing Lead, Metronome > “We feel pretty embedded in Surface, especially since we did the PLG stuff there. I would consider Surface to be like a pretty core part of what is running our website, which is a good thing.” ](https://www.withsurface.com/customers) [ **Shubh Agrawal**San Francisco, Valley > “If we turned off Surface tomorrow, we'd lose a lot of inbound. We're almost entirely inbound-driven, so Surface is a critical part of how we operate.” ](https://www.withsurface.com/customers/valley) [ **Alexandra Doan**San Francisco, Nextiva > “We actually saw that 37% more users on average converted with the new form that they built for us” ](https://www.withsurface.com/customers/nextiva) [ **Pujun Bhatnagar**CEO, Kintsugi > “We're growing at the speed of light, and Surface is one of the few vendors keeping up with us. I'd pay whatever it takes to solve this problem, and Surface solved it.” ](https://www.withsurface.com/customers/kintsugi) [ **Angela Kou**Chief of Staff, Juicebox > “Whenever I had a feature request, the Surface team would update me throughout the process and follow up after launch to make sure everything was working correctly. It really feels like a white-glove experience.” ](https://www.withsurface.com/customers/juicebox) [ **Ian Christopher**CEO, Galley > “We used Typeform in the early days. It was great but you can tell when a company outgrows it. Surface gives us the mechanics we liked from Typeform, but with enterprise-grade control over brand, format, and functionality.” ](https://www.withsurface.com/customers/galley) Set up once ## Put marketing superintelligence to work for your revenue team. [Book a demo](https://www.withsurface.com/book-a-demo?source=customer-story&customer=valley) --- # Surface Documentation | Surface Docs URL: https://surface.thesurface.network/docs The marketing system that learns what creates revenue and uses that knowledge to run better campaigns. Surface captures the demand already on your site, keeps one current record per buyer, and points agents at that record to research, score, route, schedule, write and publish. It replaces the seam between your forms, your enrichment, your scheduler and your CRM with a single record everything reads and writes. [What is Surface?](https://www.withsurface.com/docs/what-is-surface) is the longer answer. [ ### Capture the Traffic You Already Have Tag installed and a first lead captured, in about ten minutes. ](https://www.withsurface.com/docs/quickstart)[ ### Send Sales Only the Leads Worth Calling Research, enrichment, signal and scoring on every record as it lands. ](https://www.withsurface.com/docs/platform/lead-agents/overview)[ ### Show Up When a Buyer Asks an Answer Engine Where you appear in ChatGPT, Claude, Gemini and Perplexity, and where you do not. ](https://www.withsurface.com/docs/platform/ai-visibility/overview)[ ### Get Campaign Work off Your Plate Research, a plan and drafts as artifacts, with a human in front of publish. ](https://www.withsurface.com/docs/platform/campaign-agents/overview)[ ### Book the Meeting in the Same Session Qualify, route and book in one path. No per-seat pricing, no booking caps. ](https://www.withsurface.com/docs/platform/scheduling/overview)[ ### Point Your Own Agent at the Workspace 132 tools in 17 families, over one MCP endpoint. ](https://www.withsurface.com/docs/mcp-server/overview) 1. Choose Your Goal 2. Narrow It Down 3. Your Results What are you trying to get done? Setting up environments, API keys or who can approve what? [Core Concepts](https://www.withsurface.com/docs/concepts) · [API Setup](https://www.withsurface.com/docs/mcp-server/setup) Your job Read in this order **Marketing** [Quickstart](https://www.withsurface.com/docs/quickstart) → [Load your Vault](https://www.withsurface.com/docs/guides/load-your-vault) → [AI Visibility](https://www.withsurface.com/docs/platform/ai-visibility/overview) → [SAM](https://www.withsurface.com/docs/platform/sam/overview) **GTM / RevOps** [Lead Data Layer](https://www.withsurface.com/docs/platform/leads) → [Lead Agents](https://www.withsurface.com/docs/platform/lead-agents/overview) → [Routing rules](https://www.withsurface.com/docs/platform/scheduling/routing) **Developers** [Forms SDK](https://www.withsurface.com/docs/build/forms-sdk/quickstart) → [Surface MCP](https://www.withsurface.com/docs/mcp-server/overview) → [Webhooks](https://www.withsurface.com/docs/build/webhooks/overview) Every page has a Markdown copy at `.md`. The page tree is indexed at [`/llms.txt`](https://withsurface.com/docs/llms.txt), and every page in one file is at [`/llms-full.txt`](https://withsurface.com/docs/llms-full.txt). To read these docs as tools instead, connect the [docs MCP server](https://www.withsurface.com/docs/mcp-server/docs-mcp). To _act_ on a workspace, start at [Surface MCP](https://www.withsurface.com/docs/mcp-server/overview). Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Build on Surface | For Developers | Surface Docs URL: https://surface.thesurface.network/docs/build An SDK for rendering forms in your own code, webhooks, a REST API, and browser events. Three ways in, depending on what you are building. For the MCP server, see the [MCP](https://www.withsurface.com/docs/mcp-server/overview) tab. Goal Use "My assistant should answer questions about our funnel" [MCP, read-only](https://www.withsurface.com/docs/mcp-server/tool-bundles) "My assistant should build and publish forms" [MCP, forms bundle](https://www.withsurface.com/docs/mcp-server/overview) "The form must be part of my React app, not an iframe" [Forms SDK](https://www.withsurface.com/docs/build/forms-sdk/quickstart) "I have an existing HTML form I can't replace" [External forms](https://www.withsurface.com/docs/build/webhooks/create-external-form) "Send every submission to our own service" [Webhooks](https://www.withsurface.com/docs/build/webhooks/overview) "Fire a conversion event into Google Ads" [Events](https://www.withsurface.com/docs/build/events/google-ads-tracking) "Read responses from a cron job" [API reference](https://www.withsurface.com/docs/build/api-reference/api-keys) Tool access is scoped to the credential's environment. Add `?readonly=1` and an agent cannot write. See [Tool bundles](https://www.withsurface.com/docs/mcp-server/tool-bundles). Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Claude | Your AI Agents | Surface Docs URL: https://surface.thesurface.network/docs/build/agents/claude Your AI Agents Claude Desktop, Claude Code and claude.ai against a Surface workspace, including the OAuth path most teams want. Claude is the only client with a documented OAuth path. Use it, and no long-lived API key has to sit in a desktop app. You are using Connect with **claude.ai** (web) OAuth: [Claude OAuth setup](https://www.withsurface.com/docs/mcp-server/claude-oauth-setup) **Claude Desktop** OAuth, or an API key in `claude_desktop_config.json` **Claude Code** `claude mcp add --transport http` with a header Configs for all three are in [API setup](https://www.withsurface.com/docs/mcp-server/setup). ``` claude mcp add --transport http surface-forms https://app.withsurface.com/mcp \ --header "Authorization: Bearer " ``` **Analysis over your funnel.** The `insights` bundle is the quickest way to answer an ad hoc question: "which landing pages send high-scoring leads but never produce meetings" is one turn. ``` https://app.withsurface.com/mcp?tools=insights&readonly=1 ``` **Building forms end to end.** The `forms` bundle covers create, steps and components, conditional routing, styling, the marketing pane, publish. Edits save a draft; nothing a visitor sees changes until `publish_form` runs. **Writing against the Vault.** The default connection includes the Vault tools, so Claude reads your positioning and voice before drafting. See [Vault over MCP](https://www.withsurface.com/docs/mcp-server/vault). Loading all 128 tools in a long conversation fills the context with tool definitions. Session `?tools=` "Answer questions about our numbers" `insights` + `readonly=1` "Build and publish this form" _(default: forms + vault)_ "Draft and schedule content" `content` "Everything, I'm exploring" `all` **Point it at the docs as well as the server.** `/llms-full.txt` is this whole site in one file, so it can look a tool up instead of guessing. **Give it a read-only server for exploration and a writable one for the task.** That is a second `claude mcp add` under a second name: ``` claude mcp add --transport http surface-read \ "https://app.withsurface.com/mcp?tools=all&readonly=1" \ --header "Authorization: Bearer " ``` API keys are full-access by design. If a client should only read, add `?readonly=1`. The key alone does not restrict anything. Claude is one of the four models scored in [AI Visibility](https://www.withsurface.com/docs/platform/ai-visibility/reading-the-score), alongside ChatGPT, Gemini and Perplexity. A human who clicks through from Claude arrives as an AI referral in [traffic analytics](https://www.withsurface.com/docs/platform/traffic/analytics), tagged by engine. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # OpenAI Codex | Your AI Agents | Surface Docs URL: https://surface.thesurface.network/docs/build/agents/codex Your AI Agents Connecting Codex to a Surface workspace, and the jobs it is best at: SDK forms, webhooks, and anything that touches your own repo. Codex connects like every other client: Streamable HTTP, one URL, an `Authorization` header. There is no Surface-specific plugin to install. ``` { "mcpServers": { "surface-forms": { "url": "https://app.withsurface.com/mcp", "headers": { "Authorization": "Bearer " } } } } ``` That is the [generic MCP config](https://www.withsurface.com/docs/mcp-server/setup#other-editors), not a Codex-specific one, and Codex's own config format has changed more than once. Translate the same three values into whatever shape your `codex` release expects: the URL, `Authorization: Bearer `, and HTTP transport. Codex is best on jobs that span **your repo and your Surface workspace at once**. **Forms SDK work.** The form definition lives in Surface, the markup lives in your repo, and the binding between them has to agree. The loop is `create_form` with `sdk: true` → `get_sdk_binding_map` → write the markup → `validate_form_html` → `publish_form`. See [Forms SDK](https://www.withsurface.com/docs/build/forms-sdk/overview). **Webhook receivers.** Point it at [the webhook payload shape](https://www.withsurface.com/docs/build/webhooks/submit-form) and let it write the handler, the types and the tests in your service. **Event instrumentation.** [Form events](https://www.withsurface.com/docs/build/events/form-events) into your analytics layer, matching how your app already emits events. **Migrations.** Moving off another form tool means reading an export, mapping fields, and creating forms in bulk: a script plus MCP calls. ``` https://app.withsurface.com/mcp?tools=forms,vault,cms ``` The two default bundles plus the CMS family cover most build work. `?tools=` loads a different set rather than adding to the default, so `vault` has to be named. Add `?readonly=1` on a second entry for exploring. If your Codex setup has broad filesystem and shell access, that is fine for your repo and less fine for a live workspace. Start it read-only and switch to a writable connection only for the step that needs it. Form writes save a **draft** until `publish_form` runs. Tool Returns `list_component_types` Every component a form can contain `describe_component_type` The full shape of one component `get_tool_schema` The JSON Schema for the heavy authoring tools Tell it those exist, so it reads the real shape instead of guessing a payload. ChatGPT is one of the four models scored in [AI Visibility](https://www.withsurface.com/docs/platform/ai-visibility/reading-the-score), and a human who clicks through from ChatGPT arrives as an AI referral in [traffic analytics](https://www.withsurface.com/docs/platform/traffic/analytics), tagged by engine. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Grok | Your AI Agents | Surface Docs URL: https://surface.thesurface.network/docs/build/agents/grok Your AI Agents Grok as an MCP client against your workspace, and where xAI does and does not appear in Surface's AI traffic and visibility numbers. Grok comes up in two ways: as an MCP client driving your workspace, and as a reader of your website. Surface covers the first fully and the second only in part. Surface's MCP server uses the standard transport: **Streamable HTTP, one URL, a Bearer token**. ``` URL: https://app.withsurface.com/mcp Header: Authorization: Bearer ``` xAI's MCP support differs between the Grok apps, the console and the API. Use whatever MCP entry your Grok surface exposes and give it those two values. If it takes a URL, `?tools=` and `?readonly=1` ride it. See [Tool bundles](https://www.withsurface.com/docs/mcp-server/tool-bundles). If you are building against the xAI API, Surface is just an MCP server: use any MCP client library, and every tool in the [tool reference](https://www.withsurface.com/docs/mcp-server/tools) is available. **Start read-only.** One query parameter removes every write tool: ``` https://app.withsurface.com/mcp?tools=insights&readonly=1 ``` This needs no setup beyond the [Surface Tag](https://www.withsurface.com/docs/platform/traffic/surface-tag). Two limits: Surface does not score xAI, and Grok is not one of the engines the AI traffic breakdown is documented to name. **As an answer engine.** [AI Visibility](https://www.withsurface.com/docs/platform/ai-visibility/overview) scores your presence per model, and the four scored today are ChatGPT, Gemini, Perplexity and Claude. **Grok is not one of them.** The prompt set, competitor set and [cited sources](https://www.withsurface.com/docs/platform/ai-visibility/cited-sources) are shared across the models that are. **As a referrer.** [Traffic analytics](https://www.withsurface.com/docs/platform/traffic/analytics) splits AI referrals out by engine, with an average lead score attached. The engines named in those docs are ChatGPT, Perplexity, Claude and Gemini. Build an `ai-referrals` [segment](https://www.withsurface.com/docs/platform/leads/segments) and read what actually lands in it. Whether a Grok click-through is broken out under its own engine, folded into another bucket, or absent is not something these docs can tell you. Check the AI traffic breakdown in your own workspace, or ask your Surface contact. Blocking AI crawlers in `robots.txt` is right for some businesses and wrong for most B2B ones. Check what yours does rather than inheriting it from a template. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Other Clients | Your AI Agents | Surface Docs URL: https://surface.thesurface.network/docs/build/agents/other-clients Your AI Agents Cursor, Windsurf, and anything you write yourself: the generic path, and what to check when a client misbehaves. No client-specific code lives in Surface's MCP server. If your tool speaks [Streamable HTTP MCP](https://modelcontextprotocol.io/docs/concepts/transports#streamable-http), it connects with a URL and a header. ``` { "mcpServers": { "surface-forms": { "url": "https://app.withsurface.com/mcp", "headers": { "Authorization": "Bearer " } } } } ``` Client Notes **Cursor** Settings UI or `.cursor/mcp.json`. [Config →](https://www.withsurface.com/docs/mcp-server/setup#cursor) **Windsurf** `~/.codeium/windsurf/mcp_config.json`, `serverUrl` key. [Config →](https://www.withsurface.com/docs/mcp-server/setup#windsurf) **Your own agent** Any MCP client library. Nothing here is Surface-specific Any other editor that supports Streamable HTTP takes the generic block above. These are the two clients with a written-up config in [API setup](https://www.withsurface.com/docs/mcp-server/setup). For hosts that set headers but not query strings: ``` { "headers": { "Authorization": "Bearer ", "X-Surface-Tool-Families": "content" } } ``` `?tools=` wins if both are present. Full rules in [Tool bundles](https://www.withsurface.com/docs/mcp-server/tool-bundles). Three behaviours worth coding against: **Schemas are discoverable.** `list_component_types`, `describe_component_type` and `get_tool_schema` return the real shapes at runtime, so you never hard-code a payload that a release can change. **Unknown selections fail open.** A `?tools=` list with a typo falls back to everything rather than producing a zero-tool server. A _known_ tool your credential excludes is silently skipped, so fewer tools than you expected is a permissions problem, not a spelling one. **Form writes are drafts.** `publish_form` is the only call that changes what a visitor sees. Check the tool count A default connection loads 45 tools. Fewer usually means `?readonly=1` or a restricted credential; 128 means `?tools=all`. Check the transport Streamable HTTP. There is no local process and no Docker container, so a client that can only launch a stdio server needs a bridge. Check the header `Authorization: Bearer `, with the word `Bearer`. This is the single most common failure. Check the environment Every call is scoped to the credential's environment. A tool returning an empty list is often a correct answer about the wrong environment. More in [MCP troubleshooting](https://www.withsurface.com/docs/mcp-server/setup#troubleshooting). Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Surface and Your AI Agents | Your AI Agents | Surface Docs URL: https://surface.thesurface.network/docs/build/agents/overview Your AI Agents Two directions: agents that drive Surface through MCP, and AI agents that read your website. One endpoint, `https://app.withsurface.com/mcp`, Streamable HTTP, 128 tools. No local process, no Docker, no per-client SDK. Client Page Claude Desktop, Claude Code, claude.ai [Claude](https://www.withsurface.com/docs/build/agents/claude) OpenAI Codex [Codex](https://www.withsurface.com/docs/build/agents/codex) Grok [Grok](https://www.withsurface.com/docs/build/agents/grok) Cursor, Windsurf, custom clients [Other clients](https://www.withsurface.com/docs/build/agents/other-clients) Exact config is in [API setup](https://www.withsurface.com/docs/mcp-server/setup). For an installable campaign workflow, use the [Outbound Email Skill](https://www.withsurface.com/docs/guides/outbound-email-skill) to set up prospecting, qualification, and personalized draft outreach through Surface MCP. ### [Two Rules That Apply to Every Client](#two-rules-that-apply-to-every-client) **Scope is the credential, not the client.** A key or OAuth connection belongs to one [environment](https://www.withsurface.com/docs/concepts#environment) and cannot reach another. `?tools=` changes what your agent _loads_, never what it is _permitted_ to touch. **Read-only is one parameter.** `?readonly=1` strips every write and admin tool, whatever the credential could otherwise do. ``` https://app.withsurface.com/mcp?tools=insights&readonly=1 ``` - **[Traffic analytics](https://www.withsurface.com/docs/platform/traffic/analytics)** breaks out AI _referrals_: a human who clicked through from ChatGPT, Perplexity, Claude or Gemini, tagged by engine with an average lead score attached. - **[AI Visibility](https://www.withsurface.com/docs/platform/ai-visibility/overview)** measures whether you appear in the answers those engines give, per prompt and per model. - **[Campaign Agents](https://www.withsurface.com/docs/platform/campaign-agents/content-agent)** draft the material that closes the gaps, as artifacts you review before they publish. What URL Index of every page, in Markdown [`/llms.txt`](https://withsurface.com/docs/llms.txt) The whole site as one file [`/llms-full.txt`](https://withsurface.com/docs/llms-full.txt) Any single page as Markdown append `.md` to its URL Every page also links to its Markdown version with ``. Point your agent at `/llms-full.txt` for the docs _and_ [Surface MCP](https://www.withsurface.com/docs/mcp-server/setup) for the workspace. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # API Keys | API Reference | Surface Docs URL: https://surface.thesurface.network/docs/build/api-reference/api-keys API Reference Create and manage API keys for the Surface API Every request to the Surface API needs an API key. A key is scoped to one environment and can reach every resource in that environment. 1. Log in to your Surface account. 2. Go to **Settings** > **API Keys**. 3. Click on **\+ Add API Key**. 4. Give your key a name and click **Create**. 5. **Copy and note down the API key** immediately, as it won't be shown again. A key is shown once, when you create it. Store it somewhere secure. If you lose it, create a new one. Include your API key in the `x-api-key` header for all API requests: ``` curl -X GET 'https://forms.withsurface.com/api/v1/responses' \ -H 'x-api-key: your-api-key-here' ``` Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Generate Form | Forms | Surface Docs URL: https://surface.thesurface.network/docs/build/api-reference/forms/generate-form API Reference Forms Create a form from a source template with the API POST`/api/v1/environments/{environmentId}/forms/generate` Generate a new form from a source template Create a form from the API. You pass an existing form as a style template, then define the steps and components for the new one. This endpoint needs an API key. See [API Keys](https://www.withsurface.com/docs/build/api-reference/api-keys) to create one. 1. You provide a **source form ID**. That form acts as a style template: the generated form inherits its fonts, colors, backgrounds, component styles, and layout settings. 2. You define the **steps** and **components** for the new form. Each step contains one or more components (inputs, dropdowns, scheduling widgets, etc.). 3. The API creates the form, publishes it, and returns the form ID and URL. The source form must belong to the same environment and must not be deleted. Component types that are not in the source form's styles will automatically receive default styling. ``` curl -X POST 'https://forms.withsurface.com/api/v1/environments/{environmentId}/forms/generate' \ -H 'x-api-key: your-api-key-here' \ -H 'Content-Type: application/json' \ -d '{ "sourceFormId": "your-source-form-id", "name": "My Generated Form", "steps": [ { "name": "Contact Info", "components": [ { "type": "IdentityInfo", "content": { "fields": [ { "key": "firstName", "label": "First Name" }, { "key": "lastName", "label": "Last Name" }, { "key": "emailAddress", "label": "Email" } ] } }, { "type": "NextButton", "content": { "label": "Continue" } } ] }, { "name": "Additional Details", "components": [ { "type": "Dropdown", "content": { "question": "What is your role?", "options": ["Engineering", "Product", "Design", "Marketing", "Sales", "Other"] } }, { "type": "NextButton", "content": { "label": "Submit" } } ] } ] }' ``` ## [Body Parameters](#body-parameters) `sourceFormId`bodystringrequired The ID of an existing form to use as a style template. The generated form inherits all visual settings (fonts, colors, backgrounds, component styles) from this form. `name`bodystringrequired Display name for the generated form. `steps`bodyarrayrequired Array of step objects (minimum 2). Each step represents a page/screen in the form. ›Step object properties `steps[].name`bodystringrequired Display name for the step. `steps[].components`bodyarrayrequired Array of component objects (minimum 1). Each component is a form element within the step. ›Component object properties `type`bodystringrequired The component type. See [Supported Component Types](#supported-component-types) below. `content`bodyobjectrequired Component-specific content. The shape depends on the component type. ### [Input Components](#input-components) `ShortInput`bodycomponent Single-line text input. ›Content fields Field Type Description `question` string The question/label text `LongInput`bodycomponent Multi-line text area. ›Content fields Field Type Description `question` string The question/label text `IdentityInfo`bodycomponent Collects identity fields (name, email, company, etc.). This component has a **strict schema**: only the `fields` array is accepted. ›Content fields Field Type Required Description `fields` array Yes Array of field objects `fields[].key` string Yes Field identifier. Valid keys: `"firstName"`, `"lastName"`, `"fullName"`, `"emailAddress"`, `"workEmailAddress"`, `"phoneNumber"`, `"companyName"`, `"numberOfEmployees"`, `"websiteUrl"`, `"title"`, `"streetAddress"`, `"aptSuiteEtc"`, `"city"`, `"state"`, `"country"`, `"zipCode"`, `"companyRevenue"`, `"profilePictureUrl"` `fields[].label` string Yes Display label `fields[].placeholder` string No Placeholder text `fields[].includeDialCode` boolean No Include dial code selector (for phone fields) `fields[].defaultDialCodeCountry` string No Default country for dial code `fields[].blockPersonalEmails` boolean No Block personal email domains (for email fields) `fields[].revealAfter` string No Key of another field that must be filled before this one is shown ### [Selection Components](#selection-components) `Dropdown`bodycomponent Dropdown select menu. Requires at least one option. ›Content fields Field Type Required Description `question` string No The question/label text `options` string\[\] Yes Array of dropdown options (at least 1). You can also use `choices` as an alias. `placeholder` string No Placeholder text `isMulti` boolean No Allow multiple selections `hideQuestion` boolean No Hide the question label `MultipleOptionsQuestion`bodycomponent Single or multi-select options question. ›Content fields Field Type Description `question` string The question/label text `choices` string\[\] Array of choice options. You can also use `options` as an alias. `subheading` string Subheading text below the question `isMulti` boolean Allow multiple selections ### [Scheduling Components](#scheduling-components) `CalendlyScreen`bodycomponent Embeds a calendar scheduling widget (supports Calendly, Cal.com, HubSpot, SavvyCal, RevenueHero, and more). Requires a calendar URL. ›Content fields Field Type Required Description `dataUrl` string Yes The calendar scheduling URL. You can also use `url` or `calendarUrl` as aliases. `message` string No Message displayed above the calendar `calendarType` string No Calendar provider: `"Calendly"`, `"Cal"`, `"Hubspot"`, `"SavvyCal"`, `"RevenueHero"`, `"ReclaimAI"`, `"Clari"`, `"ChiliCal"` `prefillEmail` boolean No Auto-fill email from earlier form steps ### [Navigation Components](#navigation-components) `NextButton`bodycomponent Button to advance to the next step. ›Content fields Field Type Description `label` string Button text (alias for `buttonText`) ### [Display Components](#display-components) `Header`bodycomponent A text header displayed at the top of a step. ›Content fields Field Type Description `title` string The heading text `subheading` string Optional subheading text below the title `Disclaimer`bodycomponent A block of disclaimer or legal text. ›Content fields Field Type Description `text` string The disclaimer text content ### [Other Components](#other-components) Additional component types are supported: `EmailForm`, `FileUploader`, `GraphicOptions`, `PasswordInput`, and more. These follow the same pattern: pass the `type` and relevant `content` fields. `success`boolean Whether the form was created successfully. `result`object ›Result object properties `form`object ›Form object properties `id`string Unique identifier for the generated form. `url`string The public URL path for the form (e.g., `/s/{formId}`). #### [Example Response](#example-response) ``` { "success": true, "result": { "form": { "id": "cm5abc123def456", "url": "/s/cm5abc123def456" } } } ``` #### [Error Responses](#error-responses) ``` { "message": "Invalid request body", "errors": [ { "message": "CalendlyScreen requires a calendar URL (via 'dataUrl', 'url', or 'calendarUrl')", "path": ["steps", 0, "components", 1, "content"] } ] } ``` ### [Form with Scheduling](#form-with-scheduling) ``` curl -X POST 'https://forms.withsurface.com/api/v1/environments/{environmentId}/forms/generate' \ -H 'x-api-key: your-api-key-here' \ -H 'Content-Type: application/json' \ -d '{ "sourceFormId": "your-source-form-id", "name": "Demo Booking Form", "steps": [ { "name": "Your Info", "components": [ { "type": "IdentityInfo", "content": { "fields": [ { "key": "firstName", "label": "First Name" }, { "key": "lastName", "label": "Last Name" }, { "key": "emailAddress", "label": "Work Email" }, { "key": "companyName", "label": "Company" } ] } }, { "type": "NextButton", "content": { "label": "Book a Demo" } } ] }, { "name": "Schedule", "components": [ { "type": "CalendlyScreen", "content": { "dataUrl": "https://calendly.com/your-team/30min", "message": "Pick a time that works for you" } } ] } ] }' ``` Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Component Response Shapes | Responses | Surface Docs URL: https://surface.thesurface.network/docs/build/api-reference/responses/component-response-shapes API Reference Responses The response shape of every supported component type Each entry in a form response's `data` array is one question's answer. The shape of that answer depends on the component type. Every entry follows this structure: ``` { questionId: string; response: { type: string; // Component type componentShapeVersion?: string; // Optional version (e.g., "2.0") headline?: string; // Optional headline leadAttribute?: string; // Optional lead attribute // ... component-specific fields } } ``` **Component Type:** `"IdentityInfo"` ›Response Fields `type`stringrequired Always `"IdentityInfo"` for this component type. `componentShapeVersion`string Version of the component shape (e.g., `"2.0"`). `headline`string Optional headline text displayed with the component. `leadAttribute`string Optional lead attribute mapping for CRM integration. `firstName`string First name of the respondent. `lastName`string Last name of the respondent. `emailAddress`string Email address of the respondent. `workEmailAddress`string Work email address of the respondent. `phoneNumber`string Phone number of the respondent. `companyName`string Company name of the respondent. `numberOfEmployees`string Number of employees at the company. `websiteUrl`string Website URL of the company. `title`string Job title of the respondent. `streetAddress`string Street address. `aptSuiteEtc`string Apartment, suite, or other address details. `city`string City name. `state`string State or province. `country`string Country name. `zipCode`string ZIP or postal code. `companyRevenue`string Company revenue range. `profilePictureUrl`string URL to the profile picture. `fullName`string Calculated full name (firstName + lastName). `readExternalStateId`string External state ID being read. `triggerExternalStatesIds`array Array of external state IDs to trigger. `enrichedFields`array Array of field names that were enriched. `enrichmentType`string Type of enrichment applied. **Example:** ``` { "questionId": "identity_123", "response": { "type": "IdentityInfo", "componentShapeVersion": "2.0", "headline": "Tell us about yourself", "firstName": "John", "lastName": "Doe", "emailAddress": "john.doe@example.com", "companyName": "Acme Corp", "fullName": "John Doe" } } ``` **Component Type:** `"MultipleOptionsQuestion"` ›Response Fields `type`stringrequired Always `"MultipleOptionsQuestion"` for this component type. `componentShapeVersion`string Version of the component shape (e.g., `"2.0"`). `headline`string Optional headline text displayed with the component. `leadAttribute`string Optional lead attribute mapping for CRM integration. `choices`arrayrequired Array of choice objects, each containing: `key`string The choice text/value. `value`boolean Whether this choice is selected. `index`number Index of the choice in the list. `selectedOther`boolean Whether the "Other" option is selected. **Example:** ``` { "questionId": "moq_123", "response": { "type": "MultipleOptionsQuestion", "componentShapeVersion": "2.0", "headline": "Select all that apply", "choices": [ { "key": "Option 1", "value": true, "index": 0 }, { "key": "Option 2", "value": false, "index": 1 }, { "key": "Option 3", "value": true, "index": 2 } ], "selectedOther": false } } ``` **Component Type:** `"Dropdown"` ›Response Fields `type`stringrequired Always `"Dropdown"` for this component type. `componentShapeVersion`string Version of the component shape (e.g., `"2.0"`). `headline`string Optional headline text displayed with the component. `leadAttribute`string Optional lead attribute mapping for CRM integration. `selected`string | array Selected value(s). Can be a single string for single-select dropdowns, or an array of strings for multi-select dropdowns. **Example (Single Select):** ``` { "questionId": "dropdown_123", "response": { "type": "Dropdown", "componentShapeVersion": "2.0", "headline": "Select a country", "selected": "United States" } } ``` **Example (Multi-Select):** ``` { "questionId": "dropdown_123", "response": { "type": "Dropdown", "componentShapeVersion": "2.0", "headline": "Select countries", "selected": ["United States", "Canada", "Mexico"] } } ``` **Component Type:** `"ShortInput"` ›Response Fields `type`stringrequired Always `"ShortInput"` for this component type. `componentShapeVersion`string Version of the component shape (e.g., `"2.0"`). `headline`string Optional headline text displayed with the component. `leadAttribute`string Optional lead attribute mapping for CRM integration. `input`stringrequired The text input value entered by the user. **Example:** ``` { "questionId": "shortinput_123", "response": { "type": "ShortInput", "componentShapeVersion": "2.0", "headline": "What's your name?", "input": "John Doe" } } ``` **Component Type:** `"LongInput"` ›Response Fields `type`stringrequired Always `"LongInput"` for this component type. `componentShapeVersion`string Version of the component shape (e.g., `"2.0"`). `headline`string Optional headline text displayed with the component. `leadAttribute`string Optional lead attribute mapping for CRM integration. `input`stringrequired The textarea input value entered by the user. **Example:** ``` { "questionId": "longinput_123", "response": { "type": "LongInput", "componentShapeVersion": "2.0", "headline": "Tell us more", "input": "This is a longer text response..." } } ``` **Component Type:** `"GraphicOptions"` ›Response Fields `type`stringrequired Always `"GraphicOptions"` for this component type. `componentShapeVersion`string Version of the component shape (e.g., `"2.0"`). `headline`string Optional headline text displayed with the component. `leadAttribute`string Optional lead attribute mapping for CRM integration. `index`numberrequired Index of the selected option. `value`stringrequired Value/label of the selected option. **Example:** ``` { "questionId": "graphic_123", "response": { "type": "GraphicOptions", "componentShapeVersion": "2.0", "headline": "Choose a plan", "index": 2, "value": "Premium Plan" } } ``` **Component Type:** `"CalendlyScreen"` ›Response Fields `type`stringrequired Always `"CalendlyScreen"` for this component type. `componentShapeVersion`string Version of the component shape (e.g., `"2.0"`). `headline`string Optional headline text displayed with the component. `leadAttribute`string Optional lead attribute mapping for CRM integration. `autoscrolls`boolean Whether the component autoscrolls. `eventScheduled`booleanrequired Whether an event was scheduled. `uri`stringrequired Calendly URI for the scheduled event. `meetingTime`string Meeting start time (ISO 8601 format). `meetingEndTime`string Meeting end time (ISO 8601 format). `ownerEmails`string Owner email address(es). `guestEmails`string Guest email address(es). **Example:** ``` { "questionId": "calendly_123", "response": { "type": "CalendlyScreen", "componentShapeVersion": "2.0", "headline": "Schedule a meeting", "autoscrolls": true, "eventScheduled": true, "uri": "https://calendly.com/user/meeting", "meetingTime": "2024-01-15T10:00:00Z", "meetingEndTime": "2024-01-15T10:30:00Z", "ownerEmails": "owner@example.com", "guestEmails": "guest@example.com" } } ``` **Component Type:** `"FileUploader"` ›Response Fields `type`stringrequired Always `"FileUploader"` for this component type. `componentShapeVersion`string Version of the component shape (e.g., `"2.0"`). `headline`string Optional headline text displayed with the component. `leadAttribute`string Optional lead attribute mapping for CRM integration. `fileUrl`string URL of the uploaded file. **Example:** ``` { "questionId": "file_123", "response": { "type": "FileUploader", "componentShapeVersion": "2.0", "headline": "Upload a file", "fileUrl": "https://example.com/uploads/file.pdf" } } ``` **Component Type:** `"Disclaimer"` ›Response Fields `type`stringrequired Always `"Disclaimer"` for this component type. `componentShapeVersion`string Version of the component shape (e.g., `"2.0"`). `headline`string Optional headline text displayed with the component. `leadAttribute`string Optional lead attribute mapping for CRM integration. `check`boolean Whether the disclaimer checkbox is checked. **Example:** ``` { "questionId": "disclaimer_123", "response": { "type": "Disclaimer", "componentShapeVersion": "2.0", "headline": "Terms and Conditions", "check": true } } ``` **Component Type:** `"Recaptcha"` ›Response Fields `type`stringrequired Always `"Recaptcha"` for this component type. `componentShapeVersion`string Version of the component shape (e.g., `"2.0"`). `headline`string Optional headline text displayed with the component. `leadAttribute`string Optional lead attribute mapping for CRM integration. `input`stringrequired The reCAPTCHA token/response. **Example:** ``` { "questionId": "recaptcha_123", "response": { "type": "Recaptcha", "componentShapeVersion": "2.0", "headline": "Verify you're human", "input": "03AGdBq25..." } } ``` **Component Type:** `"PasswordInput"` ›Response Fields `type`stringrequired Always `"PasswordInput"` for this component type. `componentShapeVersion`string Version of the component shape (e.g., `"2.0"`). `headline`string Optional headline text displayed with the component. `leadAttribute`string Optional lead attribute mapping for CRM integration. `input`stringrequired The password value (should be hashed/encrypted). **Example:** ``` { "questionId": "password_123", "response": { "type": "PasswordInput", "componentShapeVersion": "2.0", "headline": "Enter your password", "input": "hashed_password_value" } } ``` **Component Type:** `"PasswordCreatorInput"` ›Response Fields `type`stringrequired Always `"PasswordCreatorInput"` for this component type. `componentShapeVersion`string Version of the component shape (e.g., `"2.0"`). `headline`string Optional headline text displayed with the component. `leadAttribute`string Optional lead attribute mapping for CRM integration. `input`stringrequired The created password value (should be hashed/encrypted). **Example:** ``` { "questionId": "passwordcreator_123", "response": { "type": "PasswordCreatorInput", "componentShapeVersion": "2.0", "headline": "Create a password", "input": "hashed_password_value" } } ``` **Component Type:** `"TurnstileWidget"` ›Response Fields `type`stringrequired Always `"TurnstileWidget"` for this component type. `componentShapeVersion`string Version of the component shape (e.g., `"2.0"`). `headline`string Optional headline text displayed with the component. `leadAttribute`string Optional lead attribute mapping for CRM integration. `token`stringrequired Cloudflare Turnstile token. **Example:** ``` { "questionId": "turnstile_123", "response": { "type": "TurnstileWidget", "componentShapeVersion": "2.0", "headline": "Verify with Turnstile", "token": "0.abcdefghijklmnop..." } } ``` **Component Type:** `"AiChatbot"` ›Response Fields `type`stringrequired Always `"AiChatbot"` for this component type. `componentShapeVersion`string Version of the component shape (e.g., `"2.0"`). `headline`string Optional headline text displayed with the component. `leadAttribute`string Optional lead attribute mapping for CRM integration. `summary`stringrequired Summary of the conversation. `chatbotMode`stringrequired Mode of the chatbot. Can be `"Conversation"` or `"Questionnaire"`. `history`string Conversation history. `qna`string Q&A data if in questionnaire mode. **Example:** ``` { "questionId": "aichatbot_123", "response": { "type": "AiChatbot", "componentShapeVersion": "2.0", "headline": "Chat with AI", "summary": "User asked about pricing and features", "chatbotMode": "Conversation", "history": "User: What are your prices?\nAI: Our pricing starts at $99/month..." } } ``` Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Get All Responses | Responses | Surface Docs URL: https://surface.thesurface.network/docs/build/api-reference/responses/get-all-responses API Reference Responses Retrieve all form responses for your environment GET`/api/v1/responses` Get all responses for an environment Returns responses from every form in your environment. By default, only completed responses are returned. Learn how to create an API key in the [API Keys](https://www.withsurface.com/docs/build/api-reference/api-keys) documentation. ``` curl -X GET 'https://forms.withsurface.com/api/v1/responses' \ -H 'x-api-key: your-api-key-here' ``` `data`array Array of response objects for all forms in your environment. ›Response object properties `id`string Unique identifier for the response. `createdAt`string ISO 8601 timestamp of when the response was created. `updatedAt`string ISO 8601 timestamp of when the response was last updated. `dataUpdatedAt`string ISO 8601 timestamp of when the response data was last updated. `finished`boolean Whether the response is complete (true) or partial (false). `status`number Status code of the response. `formId`string ID of the form this response belongs to. `version`string Version of the response format. `data`array Array of question responses, each containing a `response` object and `questionId`. Each response object follows a specific shape based on the component type. See the [Component Response Shapes](https://www.withsurface.com/docs/build/api-reference/responses/component-response-shapes) documentation for details on all supported component types. `meta`object Metadata associated with the response, including `leadId`. `personAttributes`object Attributes about the person who submitted the response, including IP address, country, and form visit statistics. ### [Example Response](#example-response) 200 - Success ``` { "data": [ { "id": "cmasda085pa0018js0barsadxn5b", "createdAt": "2026-01-20T19:45:59.519Z", "updatedAt": "2026-01-20T19:46:37.149Z", "dataUpdatedAt": "2026-01-20T19:46:01.725Z", "finished": true, "status": 4, "formId": "casdkgkufzp0001kw0btrmz1asd", "version": "2.0", "data": [ { "response": { "type": "IdentityInfo", "headline": "Identity Info", "emailAddress": "john.doe@example.com", "firstName": "John", "lastName": "Doe", "companyName": "Example Inc.", "componentShapeVersion": "2.0" }, "questionId": "gOyoYYzZRnvo" }, ], "meta": { "leadId": "lead_1234567890" }, "personAttributes": { "ip": "123.45.67.89", "country": "United States", "visitedForm": 1, "completedForm": 0 } }, ] } ``` Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Get Form Responses | Responses | Surface Docs URL: https://surface.thesurface.network/docs/build/api-reference/responses/get-form-responses API Reference Responses Retrieve responses for a specific form GET`/api/v1/responses` Get responses for a specific form Returns responses for one form. Filtering by form ID returns at most 10 responses per request. Learn how to create an API key in the [API Keys](https://www.withsurface.com/docs/build/api-reference/api-keys) documentation. ``` # Get completed responses only curl -X GET 'https://forms.withsurface.com/api/v1/responses?formId=your-form-id' \ -H 'x-api-key: your-api-key-here' # Include partial responses curl -X GET 'https://forms.withsurface.com/api/v1/responses?formId=your-form-id&returnPartials=true' \ -H 'x-api-key: your-api-key-here' ``` `formId`querystringrequired The ID of the form to fetch responses for. This parameter is required when querying responses for a specific form. `returnPartials`querybooleandefault: false Set to `true` to include partial/incomplete responses in the results. When set to `false` (default), only completed responses are returned. Partial responses are those where the user started filling out the form but did not complete the submission. `data`array Array of response objects for the specified form. Limited to 10 most recent responses. ›Response object properties `id`string Unique identifier for the response. `createdAt`string ISO 8601 timestamp of when the response was created. `updatedAt`string ISO 8601 timestamp of when the response was last updated. `dataUpdatedAt`string ISO 8601 timestamp of when the response data was last updated. `finished`boolean Whether the response is complete (true) or partial (false). `status`number Status code of the response. `formId`string ID of the form this response belongs to. `version`string Version of the response format. `data`array Array of question responses, each containing a `response` object and `questionId`. Each response object follows a specific shape based on the component type. See the [Component Response Shapes](https://www.withsurface.com/docs/build/api-reference/responses/component-response-shapes) documentation for details on all supported component types. `meta`object Metadata associated with the response, including `leadId`. `personAttributes`object Attributes about the person who submitted the response, including IP address, country, and form visit statistics. ### [Example Response](#example-response) 200 - Success ``` { "data": [ { "id": "cmasda085pa0018js0barsadxn5b", "createdAt": "2026-01-20T19:45:59.519Z", "updatedAt": "2026-01-20T19:46:37.149Z", "dataUpdatedAt": "2026-01-20T19:46:01.725Z", "finished": true, "status": 4, "formId": "casdkgkufzp0001kw0btrmz1asd", "version": "2.0", "data": [ { "response": { "type": "IdentityInfo", "headline": "Identity Info", "emailAddress": "john.doe@example.com", "firstName": "John", "lastName": "Doe", "companyName": "Example Inc.", "componentShapeVersion": "2.0" }, "questionId": "gOyoYYzZRnvo" }, ], "meta": { "leadId": "lead_1234567890" }, "personAttributes": { "ip": "123.45.67.89", "country": "United States", "visitedForm": 1, "completedForm": 0 } }, ] } ``` To retrieve more than 10 responses for a form, you may need to implement pagination or use the environment-wide endpoint. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Form Events | Events | Surface Docs URL: https://surface.thesurface.network/docs/build/events/form-events Events The events Surface forms emit, for use with Google Tag Manager, Google Ads, and Meta Ads. Surface forms emit events you can track in analytics platforms like Google Ads and Meta Ads. Note: The `emailProvided` and `meetingBooked` events are only emitted when the respective fields (email input or scheduler) are present in the form. ### [Form Started Event](#form-started-event) When a user starts filling out a form, the `SurfaceFormStarted` event is emitted. ### [Step Completion Event](#step-completion-event) Each time a user completes a step in a multi-step form, the `SurfaceFormStepSubmitted` event is emitted. ### [Email Provided Event](#email-provided-event) When a user provides their email address, the `SurfaceFormEmailProvided` event is emitted. ### [Meeting Booked Event](#meeting-booked-event) When a user books a meeting through the form, the `SurfaceFormMeetingBooked` event is emitted. ### [Form Submission Event](#form-submission-event) When a user submits a form, the `SurfaceFormSubmitEvent` event is emitted. ``` graph TD A[Form Started] -->|SurfaceFormStarted| B[Step 1] B -->|SurfaceFormStepSubmitted| C[Step 2] C -->|SurfaceFormStepSubmitted| D[Step 3] D -->|SurfaceFormSubmitEvent| E[Form Submitted] B -->|emailProvided| F[Email Provided] D -->|meetingBooked| G[Meeting Booked] ``` Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Google Ads Tracking | Events | Surface Docs URL: https://surface.thesurface.network/docs/build/events/google-ads-tracking Add GTM Container ID to Surface Form to configure various marketing tags from a single place Make sure to implement [Google Tag Manager (GTM)](https://www.withsurface.com/docs/build/events/google-tag-manager) first before setting up Google Ads tracking. ## [1\. Create a New Conversion Action in Google Ads](#1-create-a-new-conversion-action-in-google-ads) ## [2\. Keep Note of the Conversion ID and the Conversion Label](#2-keep-note-of-the-conversion-id-and-the-conversion-label) ## [3\. Log into Google Tag Manager](#3-log-into-google-tag-manager) ## [4\. Create Custom Event Trigger with Event Name Set to `SurfaceFormSubmitEvent`](#4-create-custom-event-trigger-with-event-name-set-to-surfaceformsubmitevent) ## [5\. Configure the Following Tags in GTM:](#5-configure-the-following-tags-in-gtm) 1. Conversion Linker 2. Google Ads Conversion Tracking ## [6\. Submit All Changes](#6-submit-all-changes) --- # Google Analytics Tracking | Events | Surface Docs URL: https://surface.thesurface.network/docs/build/events/google-analytics-tracking Events Track Surface Form events in Google Analytics using Google Tag Manager (GTM) **Steps:** 1. Go to **Admin** → **Data Collection and Modification** → **Data Streams** 2. Click **Add stream** → **Web** 3. Enter your website URL and stream name 4. Click **Create stream** **Steps:** 1. In the data stream settings, click on your newly created data stream 2. Copy the **Measurement ID** (starts with G-XXXXXXXXXX) Do this before you set up the triggers in GTM. **Steps:** 1. Go to **Admin** → **Data Display** → **Events** 2. Click **Create event** 3. Name the event **SurfaceFormSubmitEvent** (this should match the event name you'll use in GTM) 4. Scroll down and click **View more options** 5. Under **Matching conditions**, remove the `page_location` parameter 6. Click **Save** Create one trigger per Surface form event you want to track. **Steps:** 1. In GTM, go to **Triggers** 2. Click **New** → **Trigger Configuration** 3. Select **Custom Event** 4. Enter the event name as **SurfaceFormSubmitEvent** 5. Click **Save** **Steps:** 1. In GTM, go to **Tags** 2. Click **New** → **Tag Configuration** 3. Select **Google Analytics: GA4 Event** 4. Enter your **Measurement ID** (from Step 2) 5. Set the **Event Name** 6. Under **Triggering**, select the trigger you created in Step 4 7. Click **Save** 1. Click **Submit** in GTM 2. Add a version name and description 3. Click **Publish** 1. Install the [Google Tag Assistant extension](https://tagassistant.google.com/) in your browser 2. Go to [tagassistant.google.com](https://tagassistant.google.com/) 3. Click **Add domain** and enter your website URL > Click **Connect** - this will open your website in a new tab 4. Fill out and submit a Surface Form to see the events being tracked Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Google Tag Manager Integration | Events | Surface Docs URL: https://surface.thesurface.network/docs/build/events/google-tag-manager Events A step-by-step guide to connect Surface Form events to Google Tag Manager (GTM) Surface forms push events to your website's data layer, so you can track interactions and conversions in Google Tag Manager (GTM). Surface Forms push three key events to the data layer: **Event Name** **When Fired** Metadata **`SurfaceFormStarted`** When the form is started (None) **`SurfaceFormStepSubmitted`** When a step is submitted (e.g., email entered) `emailProvided`, `meetingBooked` , `url` and `urlParams` **`SurfaceFormSubmitEvent`** When the entire form is submitted (None) To capture metadata from `SurfaceFormStepSubmitted`, create the following `Data Layer Variables` in GTM: **Variable Name** **Variable Type** **Data Layer Variable Name** dlv - emailProvided Data Layer Variable **`emailProvided`** dlv - meetingBooked Data Layer Variable **`meetingBooked`** dlv - urlParam Data Layer Variable (Object) `urlParam` dlv - url Data Layer Variable `url` **Steps:** 1. In GTM, go to **Variables**. 2. Click **New** → Choose **Data Layer Variable**. 3. Enter the exact name (e.g., **`dlv - emailProvided`**) and set the Data Layer Variable Name to **`emailProvided`**. Make sure to capitalize the p in `emailProvided` ! 4. Repeat for **`meetingBooked`, `url`** and **`urlParams`.** `urlParams` is an object, we need to use dot notation e.g. `{{ urlParams.medium }}` to get the data. Now create triggers that reference those variables. **Trigger Name** **Trigger Type** **Event Name** **Additional Condition** Trigger - Email Submitted Custom Event SurfaceFormStepSubmitted dlv - emailProvided equals true Trigger - Meeting Booked Custom Event SurfaceFormStepSubmitted dlv - meetingBooked equals true Trigger - URL Custom Event SurfaceFormStepSubmitted Any Trigger - urlParam Custom Event SurfaceFormStepSubmitted Any To send conversion data to an analytics or ads platform (Google, Meta, LinkedIn, and so on), create a tag that references the triggers you just made. The example below is a Google Ads Conversion Tag, which sends each conversion point to the right conversion action in Google Ads. **Tag Name** **Conversion Action (in Ads)** **Firing Trigger** GAds - Form Started Form Started Trigger - Form Started GAds - Email Submitted Email Submitted Trigger - Email Submitted GAds - Meeting Booked Meeting Booked Trigger - Meeting Booked GAds - Form Completed Form Completed Trigger - Form Completed For more details on how to setup Google Ads Conversion Tags, please refer to our [**Google Ads Tracking Guide**](https://www.withsurface.com/docs/build/events/google-ads-tracking). **Tip:** Make sure your Google Ads account has conversion actions that match these names or your chosen naming convention. Email us at [**support@withsurface.com**](mailto:support@withsurface.com). Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Meta Ads Tracking | Events | Surface Docs URL: https://surface.thesurface.network/docs/build/events/meta-ads-tracking Events Track Surface Form conversions in Meta Ads 1. Log into [Meta Ads Manager](https://business.facebook.com/) and click on **Events Manager** from left sidebar 2. In **Datasets**, find your Pixel and copy the **ID**. **Steps:** 1. In your Surface Form, go to **Settings** -> **Ads / Tracking** -> **Meta Ads** 2. Add your Meta Pixel ID to the **Meta Pixel** field 3. Click **Save** **Steps:** 1. In Events Manager, open your dataset and go to **Test events** 2. Under **Confirm your website's events are set up correctly**, enter your website URL and click **Test Events** 3. In a new tab, submit a Surface Form 4. Confirm you see a **Lead** event appear in **Test events** Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # The Binding Contract | Forms SDK | Surface Docs URL: https://surface.thesurface.network/docs/build/forms-sdk/binding Forms SDK The data attribute vocabulary that connects your HTML to the form record The binding layer discovers your inputs through four data attributes, captures answers as visitors type, and shows one step at a time. Exact IDs and answer shapes come from the `get_sdk_binding_map` MCP tool; never invent them. ### [`data-question-id`](#data-question-id) Goes on the input itself or on a wrapper. Every `input`, `select`, and `textarea` inside a wrapper binds to that question, and a control inside a nested wrapper belongs to the inner question only. Bind every question that records an answer; the SDK warns in the console about unbound ones. Schedulers (`CalendlyScreen`, `DynamicScheduler`) and `FileUploader` need no HTML binding; their answers are written in code, and `validate_form_html` skips them. ### [`data-field-name`](#data-field-name) Which key of the component's answer object this control writes. Resolution order: the wrapper's attribute, then the control's attribute, then inference (`"selected"` for a ` ``` `IdentityInfo` field names are a closed set: `emailAddress` and `workEmailAddress` (not `email`), `phoneNumber` (not `phone`), `firstName`, `lastName`, `companyName`, `websiteUrl`, `title`, `numberOfEmployees`. Bind only the keys the binding map lists. ### [`data-question-type`](#data-question-type) The record's component type. Inferred only for `ShortInput` (the default) and `EmailForm` (email inputs); every other type must be set explicitly or the server rejects the answer. ### [`data-step-id`](#data-step-id) One container per record step; the SDK shows exactly one at a time by setting `hidden` on the rest. Single-step records may omit containers. Author every container after the first with the `hidden` attribute; unhidden steps flash stacked while `init` resolves. - Text controls contribute `value`; checkboxes contribute `checked`; radios follow the choice group rules below. - Values already in the DOM at bind time (server-side rendering, autofill) are captured immediately. - Multi-field components accumulate one answer object per question, e.g. `{ firstName, lastName, workEmailAddress }`. Five types are group-built: `MultipleOptionsQuestion`, `MultipleChoiceQuestion`, `MMChoiceQuestion`, `GraphicOptions`, `MultipleChoiceSingleAnswer`. Their answers are structured objects built from the container's whole radio or checkbox group: ```
``` - `data-question-type` on the container is required; without it the server rejects the answer. - Each control's `value` must equal the record's option key exactly (`validate_form_html` cross-checks). - Never set `data-field-name` on the options. - Author controls in record order. Multi-select uses checkboxes with the same markup. The five types have different answer shapes (only `MultipleOptionsQuestion` carries an option `index`). In bound HTML the SDK builds them; in code, copy each question's `answerShape` from the binding map. `MultipleChoiceQuestion` and `MultipleChoiceSingleAnswer` are legacy types. When porting, create a `MultipleOptionsQuestion` with `isMultiSelect` `true` or `false` respectively. ### [The "Other" Option](#the-other-option) The group captures the option selection only. Render an extra text control outside the group and mark the answer when used: ``` otherInput.addEventListener("input", () => { const current = form.state().answers["step_role"]?.["q_role"] ?? {}; form.setAnswer("q_role", { ...current, selectedOther: true }); }); ``` The typed text has no slot on the choice answer; if the owner wants it stored, add a `ShortInput` question to the record. A Dropdown binds a ` ``` While `submit()` or `disqualify()` wait on the finishing write, the binding layer marks the container with the `surface-busy` class, sets `aria-busy="true"` and a `progress` cursor, and disables the clicked button. Style `.surface-busy` for a spinner; nothing else is needed. Run the `validate_form_html` MCP tool on the markup visitors actually receive; it checks every rule on this page against the record. For a framework page, validate the rendered HTML from your dev server or build output, never a hand transcription. Details in [Building with AI](https://www.withsurface.com/docs/build/forms-sdk/building-with-ai). Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Building with AI | Forms SDK | Surface Docs URL: https://surface.thesurface.network/docs/build/forms-sdk/building-with-ai Forms SDK The MCP authoring loop: create the form record, get the binding contract, validate the HTML, publish, and verify The [Surface MCP server](https://www.withsurface.com/docs/mcp-server/overview) creates the record, hands an agent the binding contract, and statically validates the HTML. Run the loop yourself, or hand it to an agent with a prompt like "build our demo booking form as an SDK form on our landing page". Plan (optional) `plan_form` with `sdk: true` critiques a blueprint before anything is created. Create the record `create_form` with `sdk: true`: steps, questions, endings; no styling or routing parameters. Give every question real question text (the responses table reads those labels). Save the `formId` and `previewToken`. Get the binding map `get_sdk_binding_map` returns, per question: `questionId`, `componentType`, `fieldNames`, option keys, `answerShape`, plus `environmentId`, `apiBaseUrl`, and a ready-to-paste `init` snippet. Use the snippet; a wrong `apiBaseUrl` is the most common failure. Author the page Write HTML or React against the [binding contract](https://www.withsurface.com/docs/build/forms-sdk/binding), copying IDs and option keys from the binding map. Validate what ships `validate_form_html` checks the markup against the record. Fix every blocker; warnings are silent data loss at runtime. Preview, publish, deploy Boot with `preview: true` and the `previewToken` to walk the draft with zero writes, then `publish_form` and deploy. Verify end to end Submit one real test response, `await form.flush()`, read it back with `get_response`, confirm every answer and `meta.surfaceTagStatus: "sdk"`. Without a browser, run headless in [Node](https://www.withsurface.com/docs/build/forms-sdk/headless-and-react#running-in-node). ## [Validating Framework Pages](#validating-framework-pages) `validate_form_html` must see the markup the visitor actually receives. Plain HTML: pass the file. Framework page: fetch the rendered HTML (`curl http://localhost:3000/your-page`) and pass it with `containerSelector` set to your boot container. Never validate a hand transcription of the source. If navigation or submit is code-driven, declare `data-surface-nav="js"`. Every record edit must be followed through to the HTML: 1. `get_form_structure` (with `include: ["params"]`) for the structure and its `revision`. 2. Edit with `add_step`, `update_step`, `add_component`, `update_component`, `remove_component`, or `batch_edit`, passing the revision as `ifRevision` so concurrent edits fail loudly. 3. Re-fetch `get_sdk_binding_map` and update the HTML for every difference. 4. `validate_form_html` until clean, then `publish_form` and deploy together. If publish and deploy cannot land at the same time, publish first for additions and deploy first for removals and option-key changes. The dashboard's SDK form builder edits the same draft by hand. Styling, marketing, layout, and routing tools reject SDK forms: presentation lives in your HTML, navigation in your code. `simulate_response` does not apply either. `validate_form` checks configuration integrity only; a pass says nothing about your page. If your agent runner supports skills (Claude Code does): ``` cp -r node_modules/@surface-labs/forms-sdk/skills/surface-forms-sdk .claude/skills/ ``` The skill includes the workflow, HTML patterns, an editing sync loop, and a debugging runbook. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Dos and Don'ts | Forms SDK | Surface Docs URL: https://surface.thesurface.network/docs/build/forms-sdk/dos-and-donts Forms SDK The rules that keep SDK forms correct - Take `apiBaseUrl` from `get_sdk_binding_map`; a wrong host 404s. - Author every step container after the first with `hidden`, or they flash stacked during boot. - Remove `preview: true` and `debug: true` before deploying; shipped preview mode silently stores nothing. - One engine per page life: `destroy()` on teardown, never `init` again without it (duplicate responses). - Copy every `questionId`, `stepId`, option key, and `answerShape` from the binding map; a typo is silent data loss. - Set `data-question-type` on every choice group container, each control's `value` exactly the record's option key. No `data-field-name` on choice options. - Give each control of a multi-field component an explicit `data-field-name` with the record's exact keys (`workEmailAddress`, `phoneNumber`); the set is closed, don't guess `email` or `phone`. - Leave scheduler and file-upload questions unbound; their answers are written in code, and `validate_form_html` knows they are exempt. - In a framework, keep bound inputs uncontrolled and mounted; the listener attaches once at `init`, so no conditional rendering, `key` remounts, or controlled values. - Let `next()` and `goToStep()` switch steps instantly; don't disable the continue button for a partial save or insert async work before the step change unless the owner asked for a gate. - If you call `submit()` without a marker, disable your own button until it resolves. With the marker, `surface-busy` handles it. - Submit button on the last question step; both endings get a `data-step-id` container. The SDK reveals endings itself. - Declare `data-surface-nav="js"` when navigation is code-driven; don't add fake buttons to quiet the validator. - Emit `hidden` as a constant in framework markup, never derived from state. - Ask the form owner what an invalid email means (default: annotate only); never gate navigation on `validateEmail` on your own initiative. Verdicts fail open on vendor outages. - Enforce required fields and selection limits in your page if the owner wants parity; the SDK never blocks a step. - Caller-computed values go in `mergeMeta`, visitor input in answers; answers are what workflows and tables read. - Check `form.capabilities` before promising enrichment, validation, or tracking; the record can declare features the environment does not back. - Use `mountScheduler({ form, container })` and let it persist the booking; don't iframe the hosted booking page, bind the scheduler question in HTML, or hand-wire persistence unless building a custom UI on purpose. - Mount once as soon as `form` resolves, even into a hidden step container; not on step entry. - Drive navigation yourself for Clari; it exposes no booking signal. - Validate the rendered HTML with `validate_form_html` and fix every blocker; never a hand transcription of framework source. - Submit one real test response after publishing and read it back, confirming every answer and `meta.surfaceTagStatus: "sdk"`. The read-back is the only end-to-end truth. - `await form.flush()` before a programmatic page close (test harnesses); ordinary visitors need nothing. - Re-run `validate_form_html` after every record edit and follow the [editing sequence](https://www.withsurface.com/docs/build/forms-sdk/building-with-ai#editing-an-existing-sdk-form). - Walk your own branching logic in a real browser, both branches plus a boundary case; no Surface validator sees business logic in your code. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Email Validation | Forms SDK | Surface Docs URL: https://surface.thesurface.network/docs/build/forms-sdk/email-validation Forms SDK Deliverability verdicts on visitor email addresses: automatic annotation, on-demand checks, and blocking policies Two ways to validate email addresses against Surface's provider waterfall and the environment's spam blacklist. Both share one per-address verdict cache, so an address is billed once. The form owner decides: Policy Behavior Implementation **Annotate only** (default) Visitor continues; the response carries the verdict for workflows and scoring `emailValidation: true` on `init` Soft warn Inline note, visitor continues `validateEmail` in your handler, message on `!isValid` Block Visitor stays on the step until deliverable `validateEmail` gate before `next()` Disqualify End on the "not a fit" ending `validateEmail`, then `disqualify()` Never gate navigation on validation unless the owner explicitly chose block or disqualify. ``` SurfaceForms.init({ ..., emailValidation: true }); ``` Validates email answers as captured (debounced) and writes the same verdict keys native forms write (`isEmailValid`, `emailValidation`, `emailValidationFailed`) to the response's metadata. Never blocks navigation or submission. Off by default because verdicts bill the owner's validator quota. `form.validateEmail(email)` resolves the server-side verdict `{ isValid, status, reason, failed? }`: ``` // Block: keep the visitor on the step with a message. continueButton.addEventListener("click", async () => { const { isValid, reason, failed } = await form.validateEmail(emailInput.value); if (isValid || failed) return form.next(); // fail open: never lock out on a vendor outage errorEl.textContent = `That address looks undeliverable (${reason}).`; }); ``` For the disqualify policy, call `form.disqualify()` instead of showing the message. Pages with a gate should carry `data-surface-nav="js"` so `validate_form_html` knows navigation is code-driven. Pairing a gate with `emailValidation: true` is fine; the shared cache bills once. When no validator can run, the result is `{ isValid: true, failed: true, status: "unknown" }`: an outage must never lock a visitor out. Check `failed` to soft-warn instead of hard-block, and expect an address accepted today (fail open) to return a definitive `invalid` tomorrow as the waterfall resolves. In [preview mode](https://www.withsurface.com/docs/build/forms-sdk/resume-and-preview), validation resolves synthetic valid verdicts with no network and no billing. `form.capabilities.emailValidation` reports whether automatic mode is active. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Headless API and React | Forms SDK | Surface Docs URL: https://surface.thesurface.network/docs/build/forms-sdk/headless-and-react Forms SDK Drive the form engine from code: the form handle, typed answers, events, and the React adapter Everything the data attributes do, your code can do directly. Skip the `container` option and the SDK runs fully headless; keep it and mix both styles. `SurfaceForms.init` resolves to a `SurfaceForm` handle: Member What it does `setAnswer(questionId, state)` Merges a partial state into the question's answer. Use the exact shape from the binding map. `next()` / `back()` Linear advance and rewind. `next()` resolves on the step change; `back()` never writes. `goToStep(stepId)` Your routing. Forward jumps save; jumps to a visited step rewind. Rejects unknown IDs. `submit()` / `disqualify()` Finish the form; the terminal write is awaited, then the matching ending step is revealed. `savePartial()` Explicit mid-form save (fire-and-forget beacon). `flush()` Resolves when every queued write has settled. Await before programmatic teardown. `state()` `{ currentStepId, answers, externalStates, responseId, resumeToken, finished }`. Referentially stable between mutations. `subscribe(cb)` / `on(event, cb)` Store subscription and lifecycle events; both return an unsubscribe function. `mergeMeta(partial)` Record caller-computed values under `meta.custom` (see below). `identify()` Re-run visitor identification after an SPA route change. `validateEmail(email)` On-demand deliverability verdict. See [Email validation](https://www.withsurface.com/docs/build/forms-sdk/email-validation). `capabilities` `{ enrichment, emailValidation, tracking }`: what actually runs in this environment. `runtimeConfig` The fetched form record. `markViewed()` Fire the viewed events once. The binding layer does this via IntersectionObserver; headless callers do it themselves. `destroy()` Tear down every binding. One engine per page life; re-running `init` without `destroy` creates duplicate responses. ### [Events](#events) ``` form.on("saved", ({ responseId, resumeToken, finished }) => { /* persist for resume */ }); ``` Events: `viewed`, `started`, `stepChanged` (`{ fromStepId, toStepId }`), `stepCompleted`, `completed`, `disqualified`, `saved`, `error` (`{ scope, error }`), `scheduler` (see [Schedulers](https://www.withsurface.com/docs/build/forms-sdk/schedulers)). ### [Reading Answers](#reading-answers) `state().answers` is keyed by step ID, then question ID: ``` const email = form.state().answers["step_about"]?.["q_email"]?.email; ``` `setAnswer` records under the current step, so set each step's answers before `next()` or `goToStep()`. Every answer rides every save either way. A late `setAnswer` only lands under the wrong step for per-step reads and analytics (`debug: true` warns). ### [Typed Answer States](#typed-answer-states) One exported type per component (`ShortInputAnswer`, `DropdownAnswer`, `MultipleOptionsAnswer`, `IdentityInfoAnswer`, `SchedulerAnswer`, ...) plus the union `KnownAnswerState`: ``` import type { MultipleOptionsAnswer } from "@surface-labs/forms-sdk"; const answer: MultipleOptionsAnswer = { type: "MultipleOptionsQuestion", choices: [ { key: "Sales Ops", value: true, index: 0 }, { key: "Leadership", value: false, index: 1 }, ], }; form.setAnswer("q_role", answer); ``` Choice answers are structured lists, not label strings. Copy each question's `answerShape` from the binding map. The wrong shape is the most common cause of a 400 in production. ### [Custom Values on the Response](#custom-values-on-the-response) `mergeMeta(partial)` records caller-computed values (a score, an experiment bucket) under `meta.custom`. They ride the next save, or amend a finished response. Only that namespace persists; visitor input belongs in answers. Two patterns, depending on who renders the inputs. ### [Fully Headless (Controlled Inputs)](#fully-headless-controlled-inputs) `init` without `container`, render everything from the hook: ``` import { SurfaceForms, type SurfaceForm } from "@surface-labs/forms-sdk"; import { useSurfaceForm } from "@surface-labs/forms-sdk/react"; import { useEffect, useState } from "react"; export function QualifyForm() { const [form, setForm] = useState(null); useEffect(() => { let handle: SurfaceForm | null = null; let disposed = false; void SurfaceForms.init({ environmentId: "env_xxx", formId: "form_xxx", apiBaseUrl: "https://forms.withsurface.com", }).then((created) => { if (disposed) created.destroy(); else { handle = created; setForm(created); } }); return () => { disposed = true; handle?.destroy(); }; }, []); if (!form) return null; return ; } function QualifySteps({ form }: { form: SurfaceForm }) { const { state, setAnswer, goToStep, submit } = useSurfaceForm(form); // render inputs from state, setAnswer onChange, navigate from your handlers } ``` `useSurfaceForm` is a `useSyncExternalStore` adapter: `state` re-renders on engine mutations, stable between them. React 18+ is an optional peer dependency; the main entry stays React-free. ### [Data-attribute Binding Inside React](#data-attribute-binding-inside-react) React renders the markup, the SDK captures answers. Two ownership rules: 1. **`hidden` belongs to the SDK.** Emit it as a constant in the initial JSX for every step after the first; a `hidden={step !== current}` expression re-hides the step the SDK just revealed. 2. **Keep bound inputs uncontrolled and mounted.** Listeners attach at `init`; a remounted input has no listener, and a controlled `value` fights the visitor's typing. Read answers from `form.state().answers`, not React state. In the effect cleanup, call `destroy()` alone; beacons survive unmount and the finishing write was already awaited by `submit()`. On SPA route changes, call `form.identify()`. Node 18+, native `fetch`, no DOM shim; the standard way to verify a record without a browser: ``` import { SurfaceForms } from "@surface-labs/forms-sdk"; const form = await SurfaceForms.init({ environmentId, formId, apiBaseUrl, journey: false }); form.setAnswer("q_email", { type: "ShortInput", input: "qa@example.com" }); await form.submit(); // resolves once the server has the finished response console.log(form.state().responseId); ``` Without the DOM there is no group auto-build, so set choice questions' structured shapes yourself. SDK warnings go to stderr (`console.warn`), so capture `2>&1` before grepping. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Navigation and Routing | Forms SDK | Surface Docs URL: https://surface.thesurface.network/docs/build/forms-sdk/navigation Forms SDK How visitors move through an SDK form: markers, branching, disqualification, and submit semantics SDK form records carry no routing logic. Branching lives in your own code. The SDK moves between steps and keeps the response in sync. One marker per element; most specific wins: Marker Action `data-surface-goto-step=""` Jump to a step. Forward jumps save; jumping back to a visited step rewinds without a write. `class="surface-disqualify-button"` End the form as disqualified. `class="surface-submit-button"` Finish and submit. `class="surface-next-button"` Advance to the next step in record order. A `
` container's native submit event also finishes the form (the SDK calls `preventDefault`). A goto to an unknown step logs a console warning, never throws. A static branch is two buttons: ```
``` Dynamic branching calls the handle's methods from your own handlers: ``` continueButton.addEventListener("click", () => { const size = form.state().answers["step_company"]?.["q_size"]?.selected; if (size === "1-10") form.disqualify(); else form.goToStep("step_booking"); }); ``` When navigation or submit is code-driven, put `data-surface-nav="js"` on any element (usually ``) so `validate_form_html` does not warn about missing buttons. - **Steps switch instantly.** `next()` and `goToStep()` resolve on the step change; the partial save runs behind them and reports through `saved` and `error`. Do not disable the continue button for a partial save, and do not insert async work before the step change unless the owner asked for a gate (see [email validation](https://www.withsurface.com/docs/build/forms-sdk/email-validation)). - **Finishing is the one wait.** `submit()` and `disqualify()` await the finishing write before the ending step shows. The binding layer disables the clicked button and marks the container `surface-busy`. If you call `submit()` without a marker, disable your own button until it resolves. After the terminal write, `submit()` reveals the step with `endStepKind: "thank_you"` and `disqualify()` reveals the `"disqualified"` one. Put the submit button on the last question step and give both endings a container, or the visitor finishes on a blank screen. - The finishing write is awaited; a failure emits `error`. The server never demotes a finished response: a late partial save is merged, not un-finished. - Partial saves never block navigation. The first forward move creates the response (settling `responseId`); the rest are fire-and-forget beacons. - Before programmatic teardown (test harness closing the browser), `await form.flush()`. Ordinary visitors need nothing; beacons survive page unloads. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Surface Forms SDK | Forms SDK | Surface Docs URL: https://surface.thesurface.network/docs/build/forms-sdk/overview Forms SDK Build Surface forms as your own pages: your HTML and CSS, Surface's data model, validation, scheduling, enrichment, and tracking The Forms SDK lets you build a Surface form as a page you own. The form record on Surface stays the data model; your HTML, CSS, and JavaScript control how the form looks and how visitors move through it. Unlike [embedding](https://www.withsurface.com/docs/platform/forms/embedding/inline), Surface never sees or serves your markup, but still receives every response, partial save, booking, and analytics event. ### Your Markup, Bound with Data Attributes `data-question-id` and friends; the SDK captures answers and saves progress. ### Headless Engine and React Hook Drive everything from code, or use `useSurfaceForm`. Also runs in Node. ### Embedded Schedulers One call renders any supported provider; bookings save automatically. ### Tracking and Attribution Built In GTM, GA4, Meta Pixel, HubSpot, and ad conversions fire from the form's settings. ### Email Validation and Enrichment Deliverability verdicts and real-time lead enrichment. ### Built for AI-assisted Authoring The MCP server creates the record, hands over the binding contract, and validates the HTML. Published as [`@surface-labs/forms-sdk`](https://www.npmjs.com/package/@surface-labs/forms-sdk) on npm. About 22 kB gzipped, zero runtime dependencies, and every request is a CORS simple request (no preflights). 1. **The form record lives on Surface**, created in the dashboard's SDK form builder or with the [MCP tools](https://www.withsurface.com/docs/build/forms-sdk/building-with-ai). It declares steps, questions, answer shapes, and endings; styling and routing belong to your page. 2. **Your page binds to the record.** `SurfaceForms.init` fetches the runtime configuration; the `data-*` layer captures answers from your inputs, or your code sets them directly. 3. **The SDK writes responses.** Partial saves run in the background; the finishing write on submit is awaited. ``` import { SurfaceForms } from "@surface-labs/forms-sdk"; const form = await SurfaceForms.init({ environmentId: "env_xxx", formId: "form_xxx", apiBaseUrl: "https://forms.withsurface.com", // your environment's host container: document.querySelector("#form"), }); ``` Use case Recommendation A form that must match your site's design system exactly Forms SDK A form inside a React, Vue, or Svelte app with its own state and routing Forms SDK Conditional flow logic that lives in your codebase Forms SDK A standard form live in minutes with the visual builder [Hosted form or embed](https://www.withsurface.com/docs/platform/forms/embedding/inline) A marketing pane, hosted URL, custom domain, or A/B-ready styling Hosted form or embed SDK forms skip hosted-page settings (language, custom domain, password, SEO, Turnstile). Responses, workflows, analytics, lead scoring, and integrations work the same as any other Surface form. The npm package ships agent-ready docs (`llms.txt`, `docs/api.md`) and an installable skill in `skills/surface-forms-sdk/`. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Quickstart | Forms SDK | Surface Docs URL: https://surface.thesurface.network/docs/build/forms-sdk/quickstart Forms SDK Install the Forms SDK, bind a form record to your own HTML, and store your first response You need a Surface environment and an SDK form record. Create one in the dashboard (Forms, Create New Form, Build SDK form) or through the [MCP server](https://www.withsurface.com/docs/build/forms-sdk/building-with-ai). ``` npm install @surface-labs/forms-sdk ``` pnpm and yarn work the same. The package is [`@surface-labs/forms-sdk`](https://www.npmjs.com/package/@surface-labs/forms-sdk) on npm: ESM-first, with zero runtime dependencies. `init` returns a promise, so use `target: "esnext"` for top-level `await`, or wrap the call in an async function. You can also self-host the prebuilt IIFE bundle and use the global `SurfaceFormsSDK`. `init` needs `environmentId`, `formId`, and `apiBaseUrl`. The `get_sdk_binding_map` MCP tool returns all three, plus a ready-to-paste `init` snippet and every question and step ID. The form's page in the dashboard shows the same IDs. A wrong `apiBaseUrl` is the most common boot failure. The default is `https://forms.withsurface.com`; any other deployment 404s until you pass its host. If `init` throws, the error names the URL it tried. One container per step, one `data-question-id` per question: ``` ``` - Every step container after the first is authored `hidden`; otherwise steps flash stacked during boot. - The choice question binds as a group: `data-question-type` on the container, each `value` equal to the record's option key, no `data-field-name` on options. - The submit button sits on the last question step; the SDK reveals the thank-you step itself. Full attribute vocabulary: [binding contract](https://www.withsurface.com/docs/build/forms-sdk/binding). ``` import { SurfaceForms } from "@surface-labs/forms-sdk"; const form = await SurfaceForms.init({ environmentId: "env_xxx", formId: "form_xxx", apiBaseUrl: "https://forms.withsurface.com", container: document.querySelector("#form"), }); document.querySelector("#form").hidden = false; ``` With the IIFE bundle, call `SurfaceFormsSDK.SurfaceForms.init(...)` the same way. During development, add `debug: true` to log every captured answer, lifecycle event, and navigation intent. Remove before shipping. Submit a test response, then check the Responses table (or `get_response` over MCP). SDK responses carry `surfaceTagStatus: "sdk"` in their metadata. If an answer is missing, the browser console warns about unbound record questions. See [troubleshooting](https://www.withsurface.com/docs/build/forms-sdk/troubleshooting) for the full symptom table. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Resume, Preview, and Debug | Forms SDK | Surface Docs URL: https://surface.thesurface.network/docs/build/forms-sdk/resume-and-preview Forms SDK Continue a response across visits, develop against drafts with zero writes, and see what the SDK is doing The first save returns a `resumeToken` alongside the `responseId` (on the `saved` event and in `state()`). Persist the pair and pass it back later: ``` form.on("saved", ({ responseId, resumeToken }) => localStorage.setItem("surface-resume", JSON.stringify({ responseId, resumeToken })) ); // On a later visit: const stored = JSON.parse(localStorage.getItem("surface-resume") ?? "null"); const form = await SurfaceForms.init({ ...options, ...(stored && { resume: stored }), }); ``` Boot fetches the stored answers and seeds the engine: writes become updates (no duplicate response), earlier answers land in `state().answers` for prefilling, and stored `meta.custom` values carry forward. A failed fetch (wrong token, deleted response) warns and starts a fresh session. The token proves the caller obtained the response ID legitimately; never build resume links from IDs alone. Resume is ignored in preview mode. ``` SurfaceForms.init({ ...options, preview: true, previewToken: "..." }); ``` Blocks every network write: identify, responses, events, journey, enrichment, tracking. The scheduler books synthetically and email validation resolves synthetic valid verdicts, so the whole flow is walkable offline. `previewToken` comes from the `create_form` or `get_sdk_binding_map` reply; with it, a never-published form serves its draft configuration. Remove `preview: true` before deploying. It is the most common cause of "no responses at all": the page works perfectly and writes nothing. ``` SurfaceForms.init({ ...options, debug: true }); ``` Development only. Logs every captured answer, lifecycle event, and navigation intent (a `next requested from step ...` line per call), audits answers against the record, and warns on states the server would reject and on inert configuration. In production, two diagnostics remain: `form.state()` (current step, answers, `responseId`, `finished`) and `form.capabilities` (`{ enrichment, emailValidation, tracking }`). Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Embedded Schedulers | Forms SDK | Surface Docs URL: https://surface.thesurface.network/docs/build/forms-sdk/schedulers Forms SDK Mount a working scheduler for any supported provider with one call; bookings are tracked and saved to the response automatically `mountScheduler` reads the record's scheduler configuration, renders a working scheduler, tracks the booking lifecycle, and writes the confirmed booking into the response. It works for every provider native Surface forms support. ``` import { mountScheduler } from "@surface-labs/forms-sdk"; const teardown = mountScheduler({ form, // the SurfaceForms.init handle container: document.querySelector("#booking"), onEvent(e) { if (e.type === "booking_confirmed") form.submit(); // or next()/goToStep }, }); ``` Persistence is automatic, and events also arrive on `form.on("scheduler", handler)`. Never bind a scheduler question in HTML, and never iframe the hosted booking page. Mount once, as soon as `form` resolves, into the step container even while it is still `hidden`. Do not mount on step entry. Option Default What it does `form` required The `init` handle; config, transport, identity, and persistence come from it. `container` required The embed mounts here; teardown removes it. `questionId` auto Only needed with more than one scheduler question (the error names the candidates). `stepId` works too. `styled` `true` Surface provider: injects a stylesheet scoped under `.surface-scheduler` on this container. Override with `--surface-scheduler-*` custom properties; `false` keeps everything bare. `persist` `true` Auto-persist the booking into the response. `false` still emits events, never writes. `prefill` from record `{ name?, lastName?, email? }` overrides the record's linked answers. `formatters` locale Surface provider only: `{ month?, date?, time? }` label formatters. `calendarId` auto `DynamicScheduler` with multiple calendars: pick one by name. Ambiguous routing throws. `onEvent` none Same events as `form.on("scheduler", ...)`. `onComplete` none Fires alongside `booking_confirmed`. Not needed for persistence. The returned teardown is idempotent and independent of the engine; call it before or after `form.destroy()`. Every event carries `{ questionId, stepId, provider }` plus: ``` | { type: "viewed" } | { type: "date_selected"; date? } // "YYYY-MM-DD" | { type: "slot_selected"; slot? } // { start, end? } | { type: "form_opened" } | { type: "booking_confirmed"; booking } // SchedulerBookingSummary | { type: "booking_cancelled"; reason? } ``` `SchedulerBookingSummary` is `{ provider, uri, meetingTime?, meetingEndTime?, inviteeName?, guestEmails?, ownerEmails?, joinLink?, raw? }`; `uri` is the provider's native booking ID, `raw` the untouched payload. Provider Embed Booking detection Surface SDK booking widget, styled by default Widget booking, full sub-step lifecycle Calendly iframe postMessage, plus a server-poll fallback that also reports cancellations Cal.com Vendor script Booking event SavvyCal Vendor script Booking event Chili Piper iframe postMessage HubSpot Vendor script postMessage RevenueHero Vendor script postMessage Zoom iframe postMessage, plus a server poll that backfills host email, times, join link Reclaim.ai iframe Server poll only Clari iframe None; nothing is tracked or persisted, drive navigation yourself All postMessage listeners are strictly origin-checked. - A confirmed booking is merged into the scheduler question's answer (`eventScheduled`, `uri`, meeting fields) and saved; a finished form is amended instead. Surface bookings also stamp `meta.bookingId` and fire the `meeting_booked` ad conversion trigger. - A poll-reported cancellation writes `eventCancelled: true` and saves. - Calendly, Zoom, and Reclaim embeds carry the `responseId` in their URL, so mounting them creates the response if none exists. The Surface widget resolves identity lazily at book time; visitors who never book create nothing. - With `preview: true`, every write and poll is blocked and the Surface widget books synthetically. Name and email prefill comes from the record's `linkNameToStep`, `linkLastNameToStep`, and `linkEmailToStep` references to earlier answers. Set them at record creation, or pass `prefill: { name, email }` yourself. To build your own booking interface for a Surface scheduler, mount the unstyled widget directly and write the answer yourself. ``` import { createSchedulerClient, createTransport, mountBookingWidget, toSchedulerAnswerState, } from "@surface-labs/forms-sdk"; const scheduler = createSchedulerClient({ transport: createTransport({ apiBaseUrl }) }); mountBookingWidget({ container: document.querySelector("#booking"), scheduler, eventTypeId: "evt_xxx", // from the record's scheduler content identity: () => ({ responseId: form.state().responseId ?? undefined }), prefill: { name, email }, onComplete(booking) { form.setAnswer("q_booking", { ...toSchedulerAnswerState(booking), type: "CalendlyScreen" }); form.submit(); }, }); ``` The widget steps through date, time, name and email, then booked. It injects no CSS; style its stable `surface-booking-*` class tree. Month, date, and slot elements carry raw values in `data-value`. `toSchedulerAnswerState` emits `type: "DynamicScheduler"`, so override `type` with the record's component type as shown. A persistent "No availability" means the event type really has no bookable slots (host schedule, maximum advance, no connected host). `list_schedulers` with `includeAvailability: true` returns each scheduler's `nextAvailableDate`. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Tracking, Attribution, and Enrichment | Forms SDK | Surface Docs URL: https://surface.thesurface.network/docs/build/forms-sdk/tracking-and-attribution Forms SDK Analytics vendors, ad conversions, lead journeys, UTM attribution, and real-time enrichment on SDK forms An SDK form reports the same funnel signals a hosted form does, almost all of it automatically. When the form's settings carry tracking IDs, the SDK bootstraps the vendors and fires the same events as native forms: `SurfaceFormStarted`, `SurfaceFormStepSubmitted`, and `SurfaceFormSubmitEvent` on GTM's dataLayer, Meta `trackCustom`, and GA4 events. - **Configure** in the dashboard (Tracking & Analytics) or over MCP with `update_form_settings` (`gtmId`, `gaMeasurementId`, `metaPixelId`, `trackPartialResponses`, `trackCookie`). Ad conversion rules and HubSpot tracking are dashboard-only. - **Or pass at init**: `SurfaceForms.init({ settings: { gtmId, gaMeasurementId, metaPixelId, adsConversions } })`. Caller values win. Ad conversion rules fire once per rule per response, queue until the first save produces a `responseId`, and terminal rules fire on completion only, never on disqualify. A booking fires the `meeting_booked` trigger. **Verify on a deployed page**: complete a step, inspect `window.dataLayer` for `SurfaceFormStepSubmitted`. Preview mode blocks tracking entirely. `form.capabilities.tracking` reports whether tracking is active. All on by default: - **Page-view journey**: the `journey` option tracks page views with the same cookies the Surface Tag uses and stamps the journey ID onto every response. Pass `journey: false` only where the Surface Tag already runs, to avoid double-counting. - **URL attribution**: the form's URL, query parameters (UTMs), and referrer ride every save. - **Visitor identity**: `init` identifies the visitor in the background with the Surface Tag's identity cache; boot never waits, the first save does. After an SPA route change, call `form.identify()`. Same prefill query syntax as hosted forms: `?_=value` seeds an answer (splits on the first underscore; `url`, `referrer`, `cookies` are reserved). Field names per question type: [URL Prefill](https://www.withsurface.com/docs/platform/forms/embedding/url-prefill). With an enabled enrichment provider, a valid email or website domain on the record's enrichment source field triggers enrichment, and the result rides every save as enriched lead attributes. Deduplicated per value, never fired in preview. No enabled provider means enrichment is silently inert, even if the record declares a source field. Check `form.capabilities.enrichment`; `debug: true` warns about the mismatch at boot. To autofill your own inputs from the result, read `state().externalStates.selfServeEnrichment.data` via `subscribe`. - Every answer, shaped as the binding map's `answerShape`. - `meta.surfaceTagStatus: "sdk"` (distinguishes SDK from hosted submissions). - `meta.userJourneyId` plus the stitched page-view journey. - URL, UTM parameters, and referrer. - Email validation verdicts, enriched fields, and `meta.custom` values from `mergeMeta`. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Troubleshooting | Forms SDK | Surface Docs URL: https://surface.thesurface.network/docs/build/forms-sdk/troubleshooting Forms SDK Symptom to cause to check: the SDK form debugging runbook Three views tell you what went wrong: the **browser console** (runtime warnings), **`validate_form_html`** (the static gate), and **response read-back** (what actually landed). 1. `form.state()` in the console: `currentStepId`, `answers`, `responseId`, `finished`. `form.capabilities` shows what is wired. 2. Attach a firehose while reproducing: ``` ["viewed", "started", "stepChanged", "stepCompleted", "completed", "disqualified", "saved", "error"] .forEach((e) => form.on(e, (p) => console.log("[surface]", e, p))); ``` 3. Re-run `validate_form_html` against the deployed HTML; drift since the last validation is the most common root cause after a record edit. Symptom Likely cause Check `init` throws "could not fetch runtime config" Wrong or missing `apiBaseUrl` The error names the URL it tried; use the one from `get_sdk_binding_map` No responses at all `preview: true` left in the deployed page Grep the page for `preview`; `saved` never fires in preview No responses at all Form never published, so IDs don't match Console shows unbound-question warnings; run `publish_form` Some answers missing Binding drift: a question ID unbound or misspelled Console names the unbound IDs; `validate_form_html` Some answers missing Partial responses off and the visitor abandoned mid-form `trackPartialResponses` in settings; expected 400 "Fields are missing or incorrectly formatted" Hand-built `setAnswer` with the wrong shape Compare with the binding map's `answerShape` Choice answers wrong or empty `value` attributes drifted from the record's option keys `validate_form_html` warns on exactly this Same email accepted one day, rejected the next A fail-open verdict later resolving definitively; expected Check `failed` on the verdict Thank-you never shows No thank-you ending step, or no container for it A step with `endStepKind: "thank_you"` and its container Disqualified visitors see the thank-you No disqualified ending step on the record `disqualify()` only reveals a `"disqualified"` ending Steps don't switch `data-step-id` values don't match record step IDs, or invalid goto Console warns on invalid `goToStep` Duplicate responses per visitor `init` called again without `destroy()` (SPA remounts) One engine per page life GTM, GA4, or Meta events not firing Preview mode, or settings not set Deployed non-preview page; `window.dataLayer` after a step submit Ad conversions not firing Rules gate on trigger and URL conditions; terminal rules fire on completion only; queued until first `responseId` Rules in the dashboard; watch for `saved` first Enrichment fields empty No enabled enrichment provider `form.capabilities.enrichment`; `debug: true` warns at boot Scheduler says "No availability" The event type has no bookable slots `list_schedulers` with `includeAvailability: true` Lead journey empty Journey ID never carried (or `journey: false`) Save payload's `meta` for `userJourneyId` Lead attribution missing Identify blocked (preview, ad blocker), or stale SPA session `form.identify()`; network tab for the identify call Slower than the hosted form A custom header or JSON content type added preflights DevTools should show no `OPTIONS` requests Finished response stored as partial Page torn down mid-flight `await form.submit()`, then `await form.flush()` before programmatic close `list_responses` (newest first), then `get_response`. Confirm: every expected question, structured choice answers, `surfaceTagStatus: "sdk"`, and, for a booking step, `eventScheduled: true`. A response that looks right here ends the client-side investigation. `get_sdk_binding_map` is the arbiter: the `source: "live"` map is what the deployed SDK actually fetched; the draft map (default) is what the next publish makes true. A page validated against the draft but running against an older live record explains most "validator says fine, runtime disagrees" reports. Publish, or validate against `source: "live"`. Still stuck? The npm package ships a longer runbook at `skills/surface-forms-sdk/debugging.md`, and `debug: true` narrates everything the SDK does. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 2: Create External Form | Webhooks & External Forms | Surface Docs URL: https://surface.thesurface.network/docs/build/webhooks/create-external-form Webhooks & External Forms Create an external form in Surface Labs 1. Log in to the [**Surface Labs account**](https://app.surfacelabs.com/). 2. Navigate to the Forms section. 3. Click "Create New Form". 4. Select "Link External Form". ### [Add Required Fields](#add-required-fields) Add every field you want tracked in Surface. The form builder has field types to match your form's structure: ### [Available Field Types](#available-field-types) - **Identity Info**: Collects personal information like name, email, or phone number. - **Short Input**: For short text responses (single line). - **Long Input**: For longer text responses (multi-line). - **Dropdown**: For selection from predefined options. - **Multiple Choice**: For radio button or checkbox selections. Once the fields are added, map them to the external form using the question IDs from the next steps. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 3.1: Create Multi-Step HTML Form | Webhooks & External Forms | Surface Docs URL: https://surface.thesurface.network/docs/build/webhooks/create-multi-step-html-form Webhooks & External Forms Create a multi-step HTML form Create a custom multi-step form or use the starter template. 1. Clone the repository: ``` git clone -b demo https://github.com/trysurface/multi-step-progressive-form ``` 2. Open the project and review the **`index.html`** file. **Add the form ID to the `` tag** ``` ``` Replace **``** with the ID of the external form you created in Surface. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 1: Embed Surface Scripts | Webhooks & External Forms | Surface Docs URL: https://surface.thesurface.network/docs/build/webhooks/embedding Webhooks & External Forms Add Surface Scripts to your Site Check out the [**How to Get Site ID**](https://www.withsurface.com/docs/platform/traffic/surface-tag#where-to-find-your-site-id) page to get your site ID. ### [Surface Tag](#surface-tag) Add the following script tag inside your `` tag: ``` ``` Using a verified custom domain? Add `data-custom-domain="forms.example.com"` to the Surface Tag. Follow the [custom-domain setup guide](https://www.withsurface.com/docs/platform/traffic/custom-domains) before publishing the change. ### [Surface External Script](#surface-external-script) Embed the script at the end of the `` tag: ``` ``` Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 3.2: Modify Form Fields | Webhooks & External Forms | Surface Docs URL: https://surface.thesurface.network/docs/build/webhooks/modify-form-fields Webhooks & External Forms Modify form fields in Multi-Step HTML Form After you create the external form and add its fields in [Step 2](https://www.withsurface.com/docs/build/webhooks/create-external-form), get the Component Question ID for each field. ### [Add Question IDs to Form Fields](#add-question-ids-to-form-fields) Add each field's question ID to that field's `data-id` attribute in the multi-step HTML form: ```
``` Replace **``** with the question ID you got when adding components to the external form in [Step 2](https://www.withsurface.com/docs/build/webhooks/create-external-form). Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # External HTML Forms Integration | Webhooks & External Forms | Surface Docs URL: https://surface.thesurface.network/docs/build/webhooks/overview Webhooks & External Forms Complete guide to linking and tracking external HTML forms with Surface Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 3.3: Submit Form | Webhooks & External Forms | Surface Docs URL: https://surface.thesurface.network/docs/build/webhooks/submit-form Webhooks & External Forms Submit Multi-Step HTML Form ### [Next Button](#next-button) Add the `surface-next-button` class to the next button. ``` ``` ### [Submit Button](#submit-button) Add the `surface-submit-button` class to the submit button. ``` ``` Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Core Concepts | Surface Docs URL: https://surface.thesurface.network/docs/concepts What environment, lead, Vault, agent, agent action, artifact, segment and profile mean in Surface. The boundary everything else sits inside. A workspace can hold several environments (`production`, `staging`, one per brand or region), and **everything else belongs to exactly one of them**: leads, forms, the Vault, integrations, API keys. An API key or OAuth connection belongs to one environment, so an MCP tool call can never reach another one. `?tools=` changes which tools your assistant _loads_, never which data it may _touch_. See [Tool bundles](https://www.withsurface.com/docs/mcp-server/tool-bundles). One person, one record, in the [Lead Data Layer](https://www.withsurface.com/docs/platform/leads). Surface creates it the first time it can attach an identity to activity: a form completion, a webhook, an import. Later activity adds to the record instead of replacing it. A **response** is one submission of one form, and a lead may have many. Completion rate counts responses; pipeline counts leads. The environment's private Markdown knowledge base: positioning, product facts, customer proof, competitor notes, voice. Agents read it before they write. One crawl of your website starts a [Vault](https://www.withsurface.com/docs/platform/vault/overview). A named worker with a job, a trigger, and something it writes to. Surface has four families: Family Reads Writes Runs when [Lead Agents](https://www.withsurface.com/docs/platform/lead-agents/overview) Lead record, web Lead fields, score On capture, and on demand [Campaign Agents](https://www.withsurface.com/docs/platform/campaign-agents/overview) Vault, leads, CRM, web Drafts, artifacts, CMS entries On demand, on a schedule [System Agents](https://www.withsurface.com/docs/platform/system-agents/overview) Lead record, CRM Your CRM When its workflow runs [SAM](https://www.withsurface.com/docs/platform/sam/overview) Forms, responses, leads, analytics, workflows, scores, the Vault, and whatever else its enabled capabilities cover Content and drafts, behind an Approve card. Background jobs are read-only When you ask, or on a schedule **The metered unit of agent work.** Your plan is sized in agent actions. Included per month 15,000 on Agentic Marketing Operations. Custom above that, none on Basic Beyond the included volume $0.20 per action The [pricing page](https://www.withsurface.com/pricing) has the current numbers. What counts as one action is decided per agent. Check your usage in the app, or ask us, before you plan around a specific number. Something an agent produced that a person can review, edit, approve and publish: a draft post, a comparison page, a generated image. Artifacts keep version history. A saved, live query over leads: _"ICP fit ≥ 70, visited pricing in the last 14 days, no meeting booked"_. Campaigns target segments and agents run against them. Membership updates as records change, so a segment is never a frozen list. What an [AI Visibility](https://www.withsurface.com/docs/platform/ai-visibility/overview) scan runs against: one domain, its positioning, its competitor set, and the prompts you track against it. Scores, cited sources and per-model breakdowns attach to the profile. Two words these docs avoid: **"contact"** (your CRM's object, which Surface syncs to rather than owns) and **"campaign"** meaning a channel. A Surface campaign is a plan with an audience, an outcome and measurement, see [Campaign Agents](https://www.withsurface.com/docs/platform/campaign-agents/overview). Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 1: Embed Surface Tag | Framer | Surface Docs URL: https://surface.thesurface.network/docs/embedding/framer/embedding Framer Add a Surface Tag to your Framer Site 1. Navigate to the Framer site _settings_. 2. Scroll down to _Custom Code_ section. 3. Add the following code in the _Start of **``** tag_ section. Check out the [**How to Get Site ID**](https://www.withsurface.com/docs/platform/traffic/surface-tag#where-to-find-your-site-id) page to get your site ID. ``` ``` Using a verified custom domain? Add `data-custom-domain="forms.example.com"` to the Surface Tag. Follow the [custom-domain setup guide](https://www.withsurface.com/docs/platform/traffic/custom-domains) before publishing the change. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Inline | Framer | Surface Docs URL: https://surface.thesurface.network/docs/embedding/framer/inline Framer Embed a Surface Form inline 1. In framer, click on **`insert`** to add new component inside the website. 2. Select **`Embed`** from the list of components. 3. Insert the component in the desired location. Now go to **`properties`** of the component and scroll down to the **`Embed`** section. 4. Set the **`Type`** to **`URL`** and paste your form URL in the **`URL`** field. 5. That should look something like this: Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Email Input Field Trigger | Framer | Surface Docs URL: https://surface.thesurface.network/docs/embedding/framer/input-field Framer Triggering via email input field submission This feature requires paid tier of framer! 1. In Framer, go to project `settings`. 2. Scroll down to `Custom Code` section. Add the following code in the `End of tag` section. Modify the Surface Form Embedding Script to include the `data-question-id` attribute. You must replace the **``** within **`data-question-id`** attribute below with the question ID from the Surface Form Builder. ``` ``` 1. In Framer, click on **`insert`** to add new component inside the website. 2. Select **`Form Builder`** from the list of components. 1. In the form component, click on **`properties`** to open the properties panel. 2. Scroll down to **`Code Overrides`** section. 3. Click on **`New File`** to create a new file. 4. Name the file as **`SurfaceFormHandler`**. 5. Click on **`Create`** to create the file. In the `SurfaceFormHandler` file, add the following code: ``` export function withClass(Component): ComponentType { return (props) => { props.className += " surface-form-handler" // Remember to add a space return } } ``` 1. In the form component, click on **`properties`** to open the properties panel. 2. Scroll down to **`Code Overrides`** section. 3. Select **`SurfaceFormHandler`** from the list of files. 4. Select **`withClass`** from the list of overrides. 5. Click on **`Apply`** to apply the code override. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 3: Optimize | Framer | Surface Docs URL: https://surface.thesurface.network/docs/embedding/framer/optimize Framer Optimize Surface Form loading speed 1. Navigate to the Framer site _settings_. 2. Scroll down to _Custom Code_ section. 3. Add the following `` tags in the _Start of **``** tag_ section. ``` ``` Replace `REPLACE ME WITH FORM URL` with a Surface Form URL. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Framer Integration | Framer | Surface Docs URL: https://surface.thesurface.network/docs/embedding/framer/overview [](https://www.withsurface.com/) [Help Center](https://surface-labs-knowledge-base.help.usepylon.com/)[Contact Us](mailto:founders@withsurface.com)[Dashboard](https://app.withsurface.com/) [Home](https://www.withsurface.com/docs)[Platform](https://www.withsurface.com/docs/platform)[For Developers](https://www.withsurface.com/docs/build)[Guides](https://www.withsurface.com/docs/guides)[Form Embedding](https://www.withsurface.com/docs/embedding/website-editors)[MCP](https://www.withsurface.com/docs/mcp-server/overview) Framer Complete guide to embedding Surface Forms in your Framer site [ ### Step 1: Embed Surface Tag Add Surface Tag to your Framer site with custom code components ](https://www.withsurface.com/docs/embedding/framer/embedding)[ ### Step 2: Inline Embed Surface Forms directly in your Framer applications ](https://www.withsurface.com/docs/embedding/framer/inline)[ ### Step 2: Email Input Field Trigger Trigger Popup and Slideover via email input field submission ](https://www.withsurface.com/docs/embedding/framer/input-field)[ ### Step 2: Popup Display forms in modal overlays triggered by user interactions ](https://www.withsurface.com/docs/embedding/framer/popup)[ ### Step 2: Slideover Show forms that slide in from the side of the screen ](https://www.withsurface.com/docs/embedding/framer/slideover)[ ### Step 3: Optimize Optimize form loading speed and user experience ](https://www.withsurface.com/docs/embedding/framer/optimize) Ready to Get Started? See it on your own site, or open the app and build the first form. [Book a walkthrough](https://www.withsurface.com/book-a-demo)[Open the dashboard](https://app.withsurface.com/) Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. [Help Center](https://surface-labs-knowledge-base.help.usepylon.com/) Feature Requests? Tell us what is missing. We would rather hear it than guess. [Talk to us](https://www.withsurface.com/book-a-demo) [ Website Editors Step-by-step guides for embedding Surface Forms in Framer, Webflow, WordPress, React, Next.js, and other popular website builders and frameworks. ](https://www.withsurface.com/docs/embedding/website-editors)[ Step 1: Embed Surface Tag Add a Surface Tag to your Framer Site ](https://www.withsurface.com/docs/embedding/framer/embedding) --- # Popup | Framer | Surface Docs URL: https://surface.thesurface.network/docs/embedding/framer/popup Framer Embed a Surface Form popup This feature requires paid tier of framer! 1. In Framer, go to project `settings`. 2. Scroll down to `Custom Code` section. Add the following code in the `End of tag` section. ``` ``` Select the button or element where you want to trigger the form. Open the `properties` of the element and scroll down to `Code Overrides` section. 1. Click on `New File` under `File` selection menu. Name it `SurfaceFormButton`. 2. Rename the file and click on `Create`. 3. In the code editor, go to the very bottom, add a new line, and paste the following code: ``` export function withClass(Component): ComponentType { return (props) => { props.className += " surface-form-button" // Remember to add a space return } } ``` 4. Now go back to the element, In `File` selection menu, select `SurfaceFormButton` in the first dropdown and select `withClass` from the `Override` selection menu. Publish the site and that's it! You have successfully embedded a Surface Form in your Framer project. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Slideover | Framer | Surface Docs URL: https://surface.thesurface.network/docs/embedding/framer/slideover Framer Embed a Surface Form slideover This feature requires paid tier of framer! 1. In Framer, go to project `settings`. 2. Scroll down to `Custom Code` section. Add the following code in the `End of tag` section. ``` ``` Select the button or element where you want to trigger the form. Open the `properties` of the element and scroll down to `Code Overrides` section. 1. Click on `New File` under `File` selection menu. Name it `SurfaceFormButton`. 2. Rename the file and click on `Create`. 3. In the code editor, go to the very bottom, add a new line, and paste the following code: ``` export function withClass(Component): ComponentType { return (props) => { props.className += " surface-form-button" // Remember to add a space return } } ``` 4. Now go back to the element, In `File` selection menu, select `SurfaceFormButton` in the first dropdown and select `withClass` from the `Override` selection menu. Publish the site and that's it! You have successfully embedded a Surface Form in your Framer project. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 1: Embed Surface Tag | App Router | Surface Docs URL: https://surface.thesurface.network/docs/embedding/next/app-router/embedding Next.js App Router Add a Surface Tag to your Next.js Site 1. Navigate to the `app/layout.tsx` file. 2. Add the following code in the _Start of `` tag_ section. Check out the [**How to Get Site ID**](https://www.withsurface.com/docs/platform/traffic/surface-tag#where-to-find-your-site-id) page to get your site ID. ``` import Script from "next/script"; export default function RootLayout({ children, }: Readonly<{ children: React.ReactNode; }>) { return ( ``` Using a verified custom domain? Add `data-custom-domain="forms.example.com"` to the Surface Tag. Follow the [custom-domain setup guide](https://www.withsurface.com/docs/platform/traffic/custom-domains) before publishing the change. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Inline | React.js | Surface Docs URL: https://surface.thesurface.network/docs/embedding/react/inline React.js Embed a Surface Form inline To embed a Surface form inline in your React application, you can use an iframe. This method allows the form to appear as part of your page content. Add the following code wherever you'd like the form to appear in your React component: ``` ``` Replace `` with your actual Surface Form URL. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Email Input Field Trigger | React.js | Surface Docs URL: https://surface.thesurface.network/docs/embedding/react/input-field React.js Triggering via email input field submission Ensure your HTML form includes the `surface-form-handler` class. This class is essential for identifying the form as one that triggers the Surface Form popup. Example: ```
``` Add the **`surface-form-handler`** class to any external form that you want to use to trigger the Surface Form popup. Go to the **`public/index.html`** file in your React.js project and add the following code at the end of **``** tag: Add the `data-question-id` attribute to your Surface form script. You must replace the **``** within **`data-question-id`** attribute below with the question ID from the Surface Form Builder. ``` ``` Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 3: Optimize | React.js | Surface Docs URL: https://surface.thesurface.network/docs/embedding/react/optimize React.js Optimize Surface Form loading speed 1. Navigate to the `public/index.html` file. 2. Add the following `` tags in the _Start of **``** tag_ section. ``` ``` Replace `REPLACE ME WITH FORM URL` with a Surface Form URL. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # React.js Integration | React.js | Surface Docs URL: https://surface.thesurface.network/docs/embedding/react/overview [](https://www.withsurface.com/) [Help Center](https://surface-labs-knowledge-base.help.usepylon.com/)[Contact Us](mailto:founders@withsurface.com)[Dashboard](https://app.withsurface.com/) [Home](https://www.withsurface.com/docs)[Platform](https://www.withsurface.com/docs/platform)[For Developers](https://www.withsurface.com/docs/build)[Guides](https://www.withsurface.com/docs/guides)[Form Embedding](https://www.withsurface.com/docs/embedding/website-editors)[MCP](https://www.withsurface.com/docs/mcp-server/overview) React.js Complete guide to embedding Surface Forms in your React.js site [ ### Step 1: Embed Surface Tag Add Surface Tag to your React.js site with custom code components ](https://www.withsurface.com/docs/embedding/react/embedding)[ ### Step 2: Inline Embed Surface Forms directly in your React.js applications ](https://www.withsurface.com/docs/embedding/react/inline)[ ### Step 2: Email Input Field Trigger Trigger Popup and Slideover via email input field submission ](https://www.withsurface.com/docs/embedding/react/input-field)[ ### Step 2: Popup Display forms in modal overlays triggered by user interactions ](https://www.withsurface.com/docs/embedding/react/popup)[ ### Step 2: Slideover Show forms that slide in from the side of the screen ](https://www.withsurface.com/docs/embedding/react/slideover)[ ### Step 3: Optimize Optimize form loading speed and user experience ](https://www.withsurface.com/docs/embedding/react/optimize) Ready to Get Started? See it on your own site, or open the app and build the first form. [Book a walkthrough](https://www.withsurface.com/book-a-demo)[Open the dashboard](https://app.withsurface.com/) Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. [Help Center](https://surface-labs-knowledge-base.help.usepylon.com/) Feature Requests? Tell us what is missing. We would rather hear it than guess. [Talk to us](https://www.withsurface.com/book-a-demo) [ Step 3: Optimize Optimize Surface Form loading speed ](https://www.withsurface.com/docs/embedding/wordpress/optimize)[ Step 1: Embed Surface Tag Add a Surface Tag to your React Site ](https://www.withsurface.com/docs/embedding/react/embedding) --- # Popup | React.js | Surface Docs URL: https://surface.thesurface.network/docs/embedding/react/popup React.js Embed a Surface Form popup ### [Create Surface Constructor](#create-surface-constructor) Go to the **`public/index.html`** file in your React.js project and add the following code at the end of **``** tag: ``` ``` Add **`surface-form-button`** class to the HTML element if you want to show the form as a popup. ``` ``` Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Slideover | React.js | Surface Docs URL: https://surface.thesurface.network/docs/embedding/react/slideover React.js Embed a Surface Form slideover ### [Create Surface Constructor](#create-surface-constructor) Go to the **`public/index.html`** file in your React.js project and add the following code at the end of **``** tag: ``` ``` Add **`surface-form-button`** class to the HTML element if you want to show the form as a slideover. ``` ``` Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 1: Embed Surface Tag | Unbounce | Surface Docs URL: https://surface.thesurface.network/docs/embedding/unbounce/embedding Unbounce Add a Surface Tag to your Unbounce Site ### [1\. Access Your Unbounce Page](#1-access-your-unbounce-page) 1. Log in to your Unbounce account 2. Navigate to your landing pages 3. Select the page you want to edit 4. Click "Edit Page" to enter the editor ### [2\. Add Surface Tag](#2-add-surface-tag) 1. In the bottom toolbar, click the "JavaScript" button 2. Click "Add New JavaScript" 3. Add the following script: Check out the [**How to Get Site ID**](https://www.withsurface.com/docs/platform/traffic/surface-tag#where-to-find-your-site-id) page to get your site ID. ``` ``` Using a verified custom domain? Add `data-custom-domain="forms.example.com"` to the Surface Tag. Follow the [custom-domain setup guide](https://www.withsurface.com/docs/platform/traffic/custom-domains) before publishing the change. 1. Set the script placement to "Before the body Tag" 2. Click "Done" to save the changes Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Inline | Unbounce | Surface Docs URL: https://surface.thesurface.network/docs/embedding/unbounce/inline Unbounce Embed a Surface Form inline Add `Custom HTML` component to your Unbounce page: Add the following code to the `Custom HTML` component: ``` ``` Replace `REPLACE ME WITH FORM URL` with your actual Surface Form URL. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Email Input Field Trigger | Unbounce | Surface Docs URL: https://surface.thesurface.network/docs/embedding/unbounce/input-field Unbounce Triggering via email input field submission Add `Custom HTML` component to your Unbounce page: Add the following code to the `Custom HTML` component: ```
``` 1. In the bottom toolbar, click the "JavaScript" button 2. Click "Add New JavaScript" 3. Replace the **``** with the question ID from the Surface Form Builder 4. Add the following script: ``` ``` 1. Make sure to replace the **`REPLACE ME WITH FORM URL`** with your Surface form URL 2. Set the script placement to "Before the body Tag" 3. Click "Done" to save the changes This is what your script should look like: Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 3: Optimize | Unbounce | Surface Docs URL: https://surface.thesurface.network/docs/embedding/unbounce/optimize Unbounce Optimize Surface Form loading speed 1. In the bottom toolbar, click the "JavaScript" button 2. Click "Add New JavaScript" 3. Add the following link tags: ``` ``` Replace `REPLACE ME WITH FORM URL` with a Surface Form URL. Set the script placement to **"Head"** and click **"Done"** to save the changes Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Unbounce Integration | Unbounce | Surface Docs URL: https://surface.thesurface.network/docs/embedding/unbounce/overview [](https://www.withsurface.com/) [Help Center](https://surface-labs-knowledge-base.help.usepylon.com/)[Contact Us](mailto:founders@withsurface.com)[Dashboard](https://app.withsurface.com/) [Home](https://www.withsurface.com/docs)[Platform](https://www.withsurface.com/docs/platform)[For Developers](https://www.withsurface.com/docs/build)[Guides](https://www.withsurface.com/docs/guides)[Form Embedding](https://www.withsurface.com/docs/embedding/website-editors)[MCP](https://www.withsurface.com/docs/mcp-server/overview) Unbounce Complete guide to embedding Surface Forms in your Unbounce site [ ### Step 1: Embed Surface Tag Add Surface Tag to your Unbounce site with custom code components ](https://www.withsurface.com/docs/embedding/unbounce/embedding)[ ### Step 2: Inline Embed Surface Forms directly in your Framer applications ](https://www.withsurface.com/docs/embedding/unbounce/inline)[ ### Step 2: Email Input Field Trigger Trigger Popup and Slideover via email input field submission ](https://www.withsurface.com/docs/embedding/unbounce/input-field)[ ### Step 2: Popup Display forms in modal overlays triggered by user interactions ](https://www.withsurface.com/docs/embedding/unbounce/popup)[ ### Step 2: Slideover Show forms that slide in from the side of the screen ](https://www.withsurface.com/docs/embedding/unbounce/slideover)[ ### Step 3: Optimize Optimize form loading speed and user experience ](https://www.withsurface.com/docs/embedding/unbounce/optimize) Ready to Get Started? See it on your own site, or open the app and build the first form. [Book a walkthrough](https://www.withsurface.com/book-a-demo)[Open the dashboard](https://app.withsurface.com/) Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. [Help Center](https://surface-labs-knowledge-base.help.usepylon.com/) Feature Requests? Tell us what is missing. We would rather hear it than guess. [Talk to us](https://www.withsurface.com/book-a-demo) [ Step 3: Optimize Optimize Surface Form loading speed ](https://www.withsurface.com/docs/embedding/next/page-router/optimize)[ Step 1: Embed Surface Tag Add a Surface Tag to your Unbounce Site ](https://www.withsurface.com/docs/embedding/unbounce/embedding) --- # Popup | Unbounce | Surface Docs URL: https://surface.thesurface.network/docs/embedding/unbounce/popup Unbounce Embed a Surface Form popup ### [1\. Surface Form Constructor](#1-surface-form-constructor) 1. In the bottom toolbar, click the "JavaScript" button 2. Click "Add New JavaScript" 3. Add the following script: ``` ``` 1. Make sure to replace the **`REPLACE ME WITH FORM URL`** with your Surface form URL 2. Set the script placement to "Before the body Tag" 3. Click "Done" to save the changes This is what your script should look like: ### [2\. Configure Form Trigger Button](#2-configure-form-trigger-button) 1. Select any button on your page where you want the Surface form to appear 2. In the sidebar, scroll to the bottom 3. Under "Element Metadata", set the class to **`surface-form-button`** Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Slideover | Unbounce | Surface Docs URL: https://surface.thesurface.network/docs/embedding/unbounce/slideover Unbounce Embed a Surface Form slideover ### [1\. Create Surface Constructor](#1-create-surface-constructor) 1. In the bottom toolbar, click the "JavaScript" button 2. Click "Add New JavaScript" 3. Add the following script: ``` ``` 1. Make sure to replace the **`REPLACE ME WITH FORM URL`** with your Surface form URL 2. Set the script placement to "Before the body Tag" 3. Click "Done" to save the changes This is what your script should look like: ### [2\. Configure Form Trigger Button](#2-configure-form-trigger-button) 1. Select any button on your page where you want the Surface form to appear 2. In the sidebar, scroll to the bottom 3. Under "Element Metadata", set the class to **`surface-form-button`** Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 1: Embed Surface Tag | Webflow | Surface Docs URL: https://surface.thesurface.network/docs/embedding/webflow/embedding Webflow Add a Surface Tag to your Webflow Site 1. Go to the Webflow [_**dashboard**_](https://webflow.com/dashboard). 2. Go to **`Project Section`** > **`Custom Code`**. 3. Add the following code in the _Start of **``** tag_ section. Check out the [**How to Get Site ID**](https://www.withsurface.com/docs/platform/traffic/surface-tag#where-to-find-your-site-id) page to get your site ID. ``` ``` Using a verified custom domain? Add `data-custom-domain="forms.example.com"` to the Surface Tag. Follow the [custom-domain setup guide](https://www.withsurface.com/docs/platform/traffic/custom-domains) before publishing the change. The `head` section containing the `Surface Tag` should now look like this: Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Inline | Webflow | Surface Docs URL: https://surface.thesurface.network/docs/embedding/webflow/inline Webflow Embed a Surface Form inline 1. Add a div on the page with desired height and width. 2. Add the Code Embed block _(only on paid plans)_ in Webflow within the above div and add the Surface iFrame code in the block. Replace `iframe` src with your actual Surface Form URL. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Email Input Field Trigger | Webflow | Surface Docs URL: https://surface.thesurface.network/docs/embedding/webflow/input-field Webflow Triggering via email input field submission 1. In Webflow, click on **`Add Element`** to add a new element. 2. Select **`Form Block`** from the list of elements. 1. In the form block component, Select **`Form`** from the list of elements. 2. On the right side, under **`Style Selector`**, add the **`surface-form-handler`** class to the form. We automatically prefill the email field based on the email input field. If you want to prefill fields other than the email input, you can do so by adding custom attributes to your Webflow form fields. ### [Identity Info Fields](#identity-info-fields) For identity-related fields (except email), add a custom attribute to the input field in Webflow: 1. Select the input field in Webflow 2. Go to **Settings** in the right sidebar 3. Scroll to the bottom and click **Add Custom Attribute** 4. Set the attribute: - **Key:** `data-field-name` - **Value:** One of the supported field names below ›Supported Identity Field Values Field Name Description `firstName` First name `lastName` Last name `emailAddress` Email address `phoneNumber` Phone number `companyName` Company name `numberOfEmployees` Number of employees `websiteUrl` Website URL `title` Job title `streetAddress` Street address `aptSuiteEtc` Apartment/Suite/etc. `city` City `state` State `country` Country `zipCode` Zip/Postal code `companyRevenue` Company revenue ### [Other Form Fields](#other-form-fields) For all other fields (non-identity fields), you'll need to use the question ID from your Surface form: 1. Get the **Question ID** from the Surface Form Builder 2. In Webflow, select the input field 3. Go to **Settings** in the right sidebar 4. Scroll to the bottom and click **Add Custom Attribute** 5. Set the attribute: - **Key:** `data-question-id` - **Value:** The component ID from Surface This method works with the following Surface form components: - **Short Input** - **Long Input** - **Dropdown** - **Multiple Choice Question** Go to the Webflow [**dashboard**](https://webflow.com/dashboard) > **`Project Section`** > Select **`Custom Code`** and add the following custom code into the **`footer`** code section. Add the `data-question-id` attribute to your Surface form script. You must replace the **``** within **`data-question-id`** attribute below with the question ID from the Surface Form Builder. ``` ``` Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 3: Optimize | Webflow | Surface Docs URL: https://surface.thesurface.network/docs/embedding/webflow/optimize Webflow Optimize Surface Form loading speed 1. Go to the webflow [_**dashboard**_](https://webflow.com/dashboard). 2. Go to **`Project Section`** > **`Custom Code`**. 3. Add the following code in the _Start of **``** tag_ section. ``` ``` Replace `REPLACE ME WITH FORM URL` with a Surface Form URL. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Webflow Integration | Webflow | Surface Docs URL: https://surface.thesurface.network/docs/embedding/webflow/overview [](https://www.withsurface.com/) [Help Center](https://surface-labs-knowledge-base.help.usepylon.com/)[Contact Us](mailto:founders@withsurface.com)[Dashboard](https://app.withsurface.com/) [Home](https://www.withsurface.com/docs)[Platform](https://www.withsurface.com/docs/platform)[For Developers](https://www.withsurface.com/docs/build)[Guides](https://www.withsurface.com/docs/guides)[Form Embedding](https://www.withsurface.com/docs/embedding/website-editors)[MCP](https://www.withsurface.com/docs/mcp-server/overview) Webflow Complete guide to embedding Surface Forms in your Webflow site [ ### Step 1: Embed Surface Tag Add Surface Tag to your Framer site with custom code components ](https://www.withsurface.com/docs/embedding/webflow/embedding)[ ### Step 2: Inline Embed Surface Forms directly in your Framer applications ](https://www.withsurface.com/docs/embedding/webflow/inline)[ ### Step 2: Email Input Field Trigger Trigger Popup and Slideover via email input field submission ](https://www.withsurface.com/docs/embedding/webflow/input-field)[ ### Step 2: Popup Display forms in modal overlays triggered by user interactions ](https://www.withsurface.com/docs/embedding/webflow/popup)[ ### Step 2: Slideover Show forms that slide in from the side of the screen ](https://www.withsurface.com/docs/embedding/webflow/slideover)[ ### Step 3: Optimize Optimize form loading speed and user experience ](https://www.withsurface.com/docs/embedding/webflow/optimize) Ready to Get Started? See it on your own site, or open the app and build the first form. [Book a walkthrough](https://www.withsurface.com/book-a-demo)[Open the dashboard](https://app.withsurface.com/) Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. [Help Center](https://surface-labs-knowledge-base.help.usepylon.com/) Feature Requests? Tell us what is missing. We would rather hear it than guess. [Talk to us](https://www.withsurface.com/book-a-demo) [ Step 3: Optimize Optimize Surface Form loading speed ](https://www.withsurface.com/docs/embedding/framer/optimize)[ Step 1: Embed Surface Tag Add a Surface Tag to your Webflow Site ](https://www.withsurface.com/docs/embedding/webflow/embedding) --- # Popup | Webflow | Surface Docs URL: https://surface.thesurface.network/docs/embedding/webflow/popup Webflow Embed a Surface Form popup ### [1\. Create Surface Constructor](#1-create-surface-constructor) Go to the Webflow [**dashboard**](https://webflow.com/dashboard) > **`Project Section`** > Select **`Custom Code`** and add the following custom code into the **`footer`** code section. ``` ``` This is what your script should look like: ### [2\. Configure Form Trigger Button](#2-configure-form-trigger-button) Next, navigate to your Webflow Design Studio and select the button that triggers the form. After Selecting the button, you should see `Style` tab on your right panel. Finally, add `surface-form-button` in Style Selector: Finally, save and publish your changes. Your Surface Form should now be embedded on your Webflow website! Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Slideover | Webflow | Surface Docs URL: https://surface.thesurface.network/docs/embedding/webflow/slideover Webflow Embed a Surface Form slideover ### [1\. Create Surface Constructor](#1-create-surface-constructor) Go to the Webflow [**dashboard**](https://webflow.com/dashboard) > **`Project Section`** > Select **`Custom Code`** and add the following custom code into the **`footer`** code section. ``` ``` This is what your script should look like: ### [2\. Configure Form Trigger Button](#2-configure-form-trigger-button) Next, navigate to your Webflow Design Studio and select the button that triggers the form. After Selecting the button, you should see `Style` tab on your right panel. Finally, add `surface-form-button` in Style Selector: Finally, save and publish your changes. Your Surface Form should now be embedded on your Webflow website! Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Embed Surface Forms in Your Website Builder or Framework | Form Embedding | Surface Docs URL: https://surface.thesurface.network/docs/embedding/website-editors Step-by-step guides for embedding Surface Forms in Framer, Webflow, WordPress, React, Next.js, and other popular website builders and frameworks. Pick your website builder or framework. Each one has the same six steps: install the Surface Tag, then embed the form in whichever mode you want. For the modes themselves, and for hosts not listed here, see [Embedding a Surface Form](https://www.withsurface.com/docs/platform/forms/embedding). Surface Forms can be integrated with any website that supports custom HTML/JavaScript. Check out our [Inline Embedding](https://www.withsurface.com/docs/platform/forms/embedding/inline) guide for general integration instructions. All integrations require the [Surface Tag](https://www.withsurface.com/docs/platform/traffic/surface-tag) to be installed first. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 1: Embed Surface Tag | WordPress | Surface Docs URL: https://surface.thesurface.network/docs/embedding/wordpress/embedding WordPress Add a Surface Tag to your WordPress Site The Surface Tag needs to load on every page of your site. In WordPress you can do this either with a plugin (recommended) or by editing your theme directly. Check out the [**How to Get Site ID**](https://www.withsurface.com/docs/platform/traffic/surface-tag#where-to-find-your-site-id) page to get your site ID. ``` ``` Using a verified custom domain? Add `data-custom-domain="forms.example.com"` to the Surface Tag. Follow the [custom-domain setup guide](https://www.withsurface.com/docs/platform/traffic/custom-domains) before publishing the change. To verify the tag is installed, open your site, view the page source, and search for `surface_tag`. You should find the script inside the ``. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Inline | WordPress | Surface Docs URL: https://surface.thesurface.network/docs/embedding/wordpress/inline WordPress Embed a Surface Form inline 1. Open the page or post in the WordPress block editor. 2. Click **`+`** to add a block where you want the form, and choose **`Custom HTML`**. 3. Paste the Surface iFrame code into the block: ``` ``` 4. Click **`Update`** (or **`Publish`**) to save the page. Replace `iframe` src with your actual Surface Form URL. You can find this URL by clicking the "Share" button in the `Overview` section of the form. Adjust the `height` in the `style` attribute to fit your form. If you use the Classic editor instead of the block editor, paste the same code in the **Text** tab. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Email Input Field Trigger | WordPress | Surface Docs URL: https://surface.thesurface.network/docs/embedding/wordpress/input-field WordPress Triggering via email input field submission Use this when you have an email capture field on your page (for example in a hero section) and want submitting it to open your Surface Form with the email already filled in. Surface looks for a form with the **`surface-form-handler`** class and takes over its submission. WordPress has no built-in form block, so add a **`Custom HTML`** block with a simple form: ```
``` If you build the form with a form plugin instead, add the `surface-form-handler` class to the form element. Most form plugins have a CSS class setting for this. We automatically prefill the email field based on the email input field. If you want to prefill fields other than the email input, you can do so by adding attributes to your form's input fields. ### [Identity Info Fields](#identity-info-fields) For identity-related fields (except email), add a `data-field-name` attribute to the input: ``` ``` ›Supported Identity Field Values Field Name Description `firstName` First name `lastName` Last name `emailAddress` Email address `phoneNumber` Phone number `companyName` Company name `numberOfEmployees` Number of employees `websiteUrl` Website URL `title` Job title `streetAddress` Street address `aptSuiteEtc` Apartment/Suite/etc. `city` City `state` State `country` Country `zipCode` Zip/Postal code `companyRevenue` Company revenue ### [Other Form Fields](#other-form-fields) For all other fields (non-identity fields), you'll need to use the question ID from your Surface form: 1. Get the **Question ID** from the Surface Form Builder. 2. Add a `data-question-id` attribute to the input: ``` ``` This method works with the following Surface form components: - **Short Input** - **Long Input** - **Dropdown** - **Multiple Choice Question** Add the following script to your site's **footer**. With [**WPCode**](https://www.withsurface.com/docs/embedding/wordpress/embedding), go to **`Code Snippets`** > **`Header & Footer`** and paste it into the **Footer** section. Add the `data-question-id` attribute to your Surface form script. You must replace the **``** within **`data-question-id`** attribute below with the question ID from the Surface Form Builder. ``` ``` Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 3: Optimize | WordPress | Surface Docs URL: https://surface.thesurface.network/docs/embedding/wordpress/optimize WordPress Optimize Surface Form loading speed Add the following code to your site's ``. With [**WPCode**](https://www.withsurface.com/docs/embedding/wordpress/embedding), go to **`Code Snippets`** > **`Header & Footer`** and paste it into the **Header** section. ``` ``` Replace `REPLACE ME WITH FORM URL` with a Surface Form URL. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # WordPress Integration | WordPress | Surface Docs URL: https://surface.thesurface.network/docs/embedding/wordpress/overview WordPress Complete guide to embedding Surface Forms in your WordPress site [ ### Step 1: Embed Surface Tag Add Surface Tag to your WordPress site with a plugin or your theme ](https://www.withsurface.com/docs/embedding/wordpress/embedding)[ ### Step 2: Inline Embed Surface Forms directly in your WordPress pages and posts ](https://www.withsurface.com/docs/embedding/wordpress/inline)[ ### Step 2: Email Input Field Trigger Trigger Popup and Slideover via email input field submission ](https://www.withsurface.com/docs/embedding/wordpress/input-field)[ ### Step 2: Popup Display forms in modal overlays triggered by user interactions ](https://www.withsurface.com/docs/embedding/wordpress/popup)[ ### Step 2: Slideover Show forms that slide in from the side of the screen ](https://www.withsurface.com/docs/embedding/wordpress/slideover)[ ### Step 3: Optimize Optimize form loading speed and user experience ](https://www.withsurface.com/docs/embedding/wordpress/optimize) These guides apply to self-hosted WordPress sites and WordPress.com sites on a plan that allows plugins and custom code (Business plan or above). Ready to Get Started? See it on your own site, or open the app and build the first form. [Book a walkthrough](https://www.withsurface.com/book-a-demo)[Open the dashboard](https://app.withsurface.com/) Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. [Help Center](https://surface-labs-knowledge-base.help.usepylon.com/) Feature Requests? Tell us what is missing. We would rather hear it than guess. [Talk to us](https://www.withsurface.com/book-a-demo) [ Step 3: Optimize Optimize Surface Form loading speed ](https://www.withsurface.com/docs/embedding/webflow/optimize)[ Step 1: Embed Surface Tag Add a Surface Tag to your WordPress Site ](https://www.withsurface.com/docs/embedding/wordpress/embedding) --- # Popup | WordPress | Surface Docs URL: https://surface.thesurface.network/docs/embedding/wordpress/popup WordPress Embed a Surface Form popup ### [1\. Create Surface Constructor](#1-create-surface-constructor) Add the following script to your site's **footer**. With [**WPCode**](https://www.withsurface.com/docs/embedding/wordpress/embedding), go to **`Code Snippets`** > **`Header & Footer`** and paste it into the **Footer** section. ``` ``` Replace `REPLACE ME WITH FORM URL` with your actual Surface Form URL. ### [2\. Configure Form Trigger Button](#2-configure-form-trigger-button) Next, add the `surface-form-button` class to the button that should open the form: 1. In the block editor, select your **Button** block. 2. In the right sidebar, open the **`Block`** tab and expand **`Advanced`**. 3. In **`Additional CSS class(es)`**, add `surface-form-button`. Finally, update and publish your changes. Clicking the button should now open your Surface Form in a popup! Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Slideover | WordPress | Surface Docs URL: https://surface.thesurface.network/docs/embedding/wordpress/slideover WordPress Embed a Surface Form slideover ### [1\. Create Surface Constructor](#1-create-surface-constructor) Add the following script to your site's **footer**. With [**WPCode**](https://www.withsurface.com/docs/embedding/wordpress/embedding), go to **`Code Snippets`** > **`Header & Footer`** and paste it into the **Footer** section. ``` ``` Replace `REPLACE ME WITH FORM URL` with your actual Surface Form URL. ### [2\. Configure Form Trigger Button](#2-configure-form-trigger-button) Next, add the `surface-form-button` class to the button that should open the form: 1. In the block editor, select your **Button** block. 2. In the right sidebar, open the **`Block`** tab and expand **`Advanced`**. 3. In **`Additional CSS class(es)`**, add `surface-form-button`. Finally, update and publish your changes. Clicking the button should now open your Surface Form in a slideover! Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Guides | Guides | Surface Docs URL: https://surface.thesurface.network/docs/guides Task-shaped walkthroughs that cross several products, start to finish. [Platform](https://www.withsurface.com/docs/platform) and [Build](https://www.withsurface.com/docs/build) cover each product on its own. Each guide below gets one job done, usually across several of them. Every embed mode is covered on one page, with a switcher for Webflow, Framer, WordPress, Next.js, React, Unbounce and plain HTML. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Research Companies In-Form | Guides | Surface Docs URL: https://surface.thesurface.network/docs/guides/ai-website-research Research a respondent's company from its website while they fill in the form, and route on what the model decides. When a respondent enters a work email or a website, Surface reads that company's public website in the background while they finish the form. An AI model answers questions you write about it, called dimensions, and your routing conditions decide what happens next: show the scheduler, ask more questions, or end the form. The model never routes on its own. - Research starts about a second after the respondent stops typing, and runs while they continue. - It reads up to nine public pages: the homepage and the pricing, product, features, solutions, about and customers pages. - Each dimension returns one of the outcomes you define, with a confidence from 0 to 1. The run also names the page that best supports its answers. - Personal mailboxes such as Gmail are skipped: there is no company to research. Open **Logic** and select the step that asks for the email or website. Under **Research**, switch on **AI website research** and choose **Configure research**. The line under the button shows the input fields and how many dimensions are ready, or what is still missing. 1. **Input fields** are the answers research starts from: email or website fields, or short text fields, on this step or an earlier one, listed under their steps. Pick one or several, up to ten; **Select all** takes a whole step. Each field is researched on its own, with the same goal and dimensions, as soon as the respondent fills it in; a field the respondent cannot see yet is skipped. Work emails, domains and website URLs are researched. 2. **Describe the research** in your own words: what you sell, what you want to know about the company, and any rules the decision follows. 3. **Draft dimensions** writes the research goal and the dimensions from your description. **Set up by hand** starts with none. Drafting again replaces the goal and the dimensions. Dimensions used in routing are kept. A dimension is one question. The model answers it by picking exactly one outcome. - **Name**: how the dimension shows in routing and in responses. - **What should the model decide?**: the question, and how to judge it. - **Outcomes**: 2 to 25 values, each with what it means. Routing compares against the value, such as `B2B`. The **Research goal** at the top is the task the model keeps in mind on every run. A step can have up to 20 dimensions. Give each dimension an outcome for "can't tell", such as `UNCLEAR`, so the model has an honest answer when the site doesn't say. Ask it to judge what the company sells and charges for, not the keywords on the page. Enter a work email, domain or URL, pick a past response that answered one of the input fields, or choose **Auto-fill** to try a real company that fits your description. **Run test** runs exactly as the live form does. It lists each page read, then each dimension's outcome and confidence, and the key evidence page. Edit the dimensions and run again until the outcomes match what you would decide yourself. Close the dialog and choose **Manage conditions** on the step that should decide. Add a route and pick **AI research** as the source. Each dimension gives two fields: its outcome, and its confidence from 0 to 1. **Research status** says whether the run completed. A step with several input fields lists every dimension once per field, named after it, so a rule can read the website field and the work email field separately. Rules written before the step had several fields read the first field listed. Route from a step after the research step where you can, so research finishes while the respondent answers it. When a step routes on research that is still running, its **Next** button waits for it. This route sends B2B companies of 50 or more people, with nothing to review, to the scheduler, when the model is at least 70% confident about the business model. This one ends the form only when the model is at least 85% confident the company sells to consumers. Everyone else follows the default route: here, a thank-you step that sales follows up from. When research doesn't complete, its dimensions have no value, so conditions that compare them don't match and the step's default route applies. Point the default route somewhere safe for an unknown company, never at disqualification. Research status When Completed The model answered the dimensions. Insufficient evidence No page of the site could be read. Skipped The answer was a personal mailbox, or not an email, domain or URL. Unavailable The run failed or timed out, or the respondent entered more than three different inputs. Publish the form. Research only runs on the published form: in the editor's preview it reports **Unavailable**, so use the test run there. Open a response to see what research decided: the research status, each dimension's outcome with its confidence, and the key evidence page. When the step researched several fields, each field's rows start with its name, status and site. For completed research, a **Rationale** and, when there is one, a **Qualifying question** to ask on the call are added shortly after the response is submitted. The response's **Form journey** shows which research conditions sent the respondent where. To route without AI research, see [Conditional Logic](https://www.withsurface.com/docs/platform/forms/conditional-logic). Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Build a Form with the Forms SDK | Guides | Surface Docs URL: https://surface.thesurface.network/docs/guides/build-an-sdk-form Create the form record, bind your own HTML, add a scheduler, validate, publish, and verify You will build a demo-booking form on a page you host: two question steps, a branch that disqualifies small companies, a scheduler step, and a thank-you screen. The form record on Surface is the data model, your HTML is the presentation, and the SDK binds the two ([overview](https://www.withsurface.com/docs/build/forms-sdk/overview)). - A Surface environment. - The [SDK package](https://www.npmjs.com/package/@surface-labs/forms-sdk) installed: `npm install @surface-labs/forms-sdk`. - Ideally the [Surface MCP server](https://www.withsurface.com/docs/mcp-server/setup) connected to your AI assistant; without it, copy IDs from the dashboard. Ask your assistant, or call the tools yourself: ``` create_form with sdk: true name: "Demo booking" steps: 1. "About you": IdentityInfo (first name, last name, work email) 2. "Company": MultipleOptionsQuestion "How large is your team?" options: "1-10", "11-50", "51-200", "200+" 3. "Book a time": CalendlyScreen (your Surface scheduler) 4. "Thanks" (endStepKind: thank_you): Header "You're booked!" 5. "Not a fit" (endStepKind: disqualified): Header "Thanks for your interest" ``` - Give every question real question text; the responses table uses it as the column label. - Ending steps need at least one component; a `Header` is fine. - Link the scheduler's prefill to the identity step (`linkNameToStep`, `linkEmailToStep`). - Save the `formId` and `previewToken` from the reply. The dashboard builds the same record by hand: Forms, Create New Form, Build SDK form. ``` get_sdk_binding_map formId: ``` The reply lists every step and question with `questionId`, `componentType`, `fieldNames`, option keys, and `answerShape`, plus `environmentId`, `apiBaseUrl`, and a ready-to-paste `init` snippet. Never retype IDs from memory. ## [Step 3: Write the Page](#step-3-write-the-page) ``` ``` Replace every `STEP_*` and `Q_*` placeholder with real IDs from the binding map, and keep the radio `value` attributes byte-identical to the record's option keys. Every container after the first is `hidden`. The choice question binds as a group (no `data-field-name` on options), the scheduler question has no binding, and both endings have their own container. ``` import { SurfaceForms, mountScheduler } from "@surface-labs/forms-sdk"; const form = await SurfaceForms.init({ environmentId: "ENV_ID", formId: "FORM_ID", apiBaseUrl: "API_BASE_URL", // from get_sdk_binding_map container: document.querySelector("#demo-form"), emailValidation: true, // annotate deliverability; never blocks preview: true, // remove before deploying previewToken: "PREVIEW_TOKEN", }); document.querySelector("#demo-form").hidden = false; // The branch: small teams get the disqualified ending. document.querySelector("#company-continue").addEventListener("click", () => { const answer = form.state().answers["STEP_COMPANY"]?.["Q_SIZE"]; const picked = answer?.choices?.find((c) => c.value)?.key; if (!picked) return; // require an answer if (picked === "1-10") form.disqualify(); else form.next(); }); // Mount once, into the still-hidden step container. mountScheduler({ form, container: document.querySelector("#booking"), onEvent(e) { if (e.type === "booking_confirmed") form.submit(); }, }); ``` The branch is code-driven, so add `data-surface-nav="js"` to the ``. Everything else (answer capture, partial saves, booking persistence, identity, journey tracking, busy state) is the SDK's job. ``` validate_form_html formId: html: containerSelector: "#demo-form" ``` Fetch the page exactly as a visitor receives it; for a framework page, curl the dev server output. Fix every blocker and re-run until clean. With `preview: true` and the `previewToken`, the page serves the draft record and writes nothing: walk both branches, book a synthetic meeting, confirm both endings render. ``` publish_form formId: ``` Remove `preview: true` and `previewToken`, then deploy. Submit one real test response on the deployed page, then read it back: ``` list_responses formId: get_response responseId: ``` Confirm every answer landed, the choice answer carries the structured list, the booking has `eventScheduled: true`, and the metadata shows `surfaceTagStatus: "sdk"`. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # API Based Conditional Logic | Guides | Surface Docs URL: https://surface.thesurface.network/docs/guides/control-form-logic-based-on-api Conditional Form Logic Based on Your API Response Use **External API Data** in the **Logic** tab to create branching form flows based on your own API response (for example: auth checks, eligibility checks, plan gating, or enrichment). 1. Open your form in the Surface editor. 2. Click **Logic** at the top. 3. Select the step where you want to evaluate routing (this is typically the step where the user clicks “Next”). 1. With your step selected, click **\+ HTTP Request**. 2. Configure the request: - **URL**: your endpoint (for example, `https://api.yourdomain.com/eligibility`) - **Method**: `GET` or `POST` depending on your API - **Params / Headers**: add any required values - **Body (POST)**: send JSON, using form variables if needed You can use form variables in the URL, Params, Headers, and Body. Map values from the JSON response so they are available as **External API Data**. ### [Automatically Configure the API Response](#automatically-configure-the-api-response) 1. Click on "Configure automatically" button. 2. Surface reads the API response and suggests fields you can map. 3. Select the fields you want to map and click on "Save" button. ### [Manually Configure the API Response](#manually-configure-the-api-response) 1. Click on "Configure manually" button. 2. You select the fields to extract from the JSON response yourself. 1. Open **Advanced Routing** for the step. 2. Set **Jump to step** to the step you want to send the user to when the condition is met. 3. Under **IF**, set: - **Source**: `External API Data` - **Condition**: choose the field you mapped (for example, `isPriorityLead`) and compare it to the expected value (for example, `true`) ### [Example: Only Proceed If isPriorityLead Is True](#example-only-proceed-if-isprioritylead-is-true) - **IF**: `External API Data.isPriorityLead` equals `true` - **THEN**: Jump to `Step: 1 (Book a Demo)` - **ELSE**: Keep default routing to next step (or jump to a “Not eligible” / “Invalid” step) 1. Publish your form. 2. Submit test entries that should pass and fail the condition. 3. Confirm respondents are routed to the right step in both cases. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Email Sequences with Customer.io and Calendly | Email Sequences with Customer.io and Calendly | Surface Docs URL: https://surface.thesurface.network/docs/guides/email-sequences-customerio-calendly/overview Email Sequences with Customer.io and Calendly Complete guide to running email sequences triggered by Surface form submissions, with automatic exit when leads book a meeting Run email sequences in **Customer.io** when leads submit your Surface form, whether they complete it or drop off partway. The sequence exits automatically once a lead books a **Calendly** meeting, so nobody who has already scheduled a call keeps getting emails. Form submission A lead submits your Surface form (partial or completed). Surface sends a webhook to the appropriate Customer.io URL based on the trigger. Person & event Two webhook-triggered campaigns in Customer.io (one for partial, one for completed) create or update the person and add the appropriate event. Email sequence An event-triggered campaign starts a customizable follow-up email sequence with delays between each email. Meeting check Before each follow-up (after the first), a webhook checks the Calendly API. If the lead has booked a meeting, the campaign exits. Otherwise, it continues. You need: - A **Surface** account with a form that supports partial submissions (e.g., multi-step form with email capture) - A **Customer.io** account with Campaigns and Journeys access - A **Calendly** account with API access (Personal Access Token or OAuth) - Your Calendly event type URI for the meeting type you want to check ``` flowchart LR %% Participants & Subgraphs subgraph S [Surface] direction TB Lead([Lead]) Form[Form Submission] end subgraph C [Customer.io] direction TB Webhook[Webhook Trigger] Campaign[Start Campaign] Email1[Send Email 1] Delay[Wait X Days] Check[Check Meeting] Decision{Booked?} Exit[Exit Campaign] Next[Send Follow-up] end subgraph K [Calendly] direction TB API[Calendly API] end %% Connections Lead -->|Submits| Form Form -->|Webhook Data| Webhook Webhook --> Campaign Campaign --> Email1 Email1 --> Delay Delay --> Check Check -.->|Query| API API -.->|Status| Check Check --> Decision Decision -->|Yes| Exit Decision -->|No| Next Next --> Delay %% Styling classDef plain fill:#fff,stroke:#333,stroke-width:1px; classDef check fill:#e6f7ff,stroke:#1890ff,stroke-width:2px; class Lead,Form,Webhook,Campaign,Email1,Delay,Exit,Next plain; class Check,Decision,API check; ``` Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 1: Webhook Trigger Campaigns | Email Sequences with Customer.io and Calendly | Surface Docs URL: https://surface.thesurface.network/docs/guides/email-sequences-customerio-calendly/step-1-webhook-trigger Email Sequences with Customer.io and Calendly Create two webhook-triggered campaigns in Customer.io, one for partial submissions and one for completed, each with its own URL Create **two webhook-triggered campaigns** in Customer.io: one for **Dropped Off** (partial) submissions and one for **Form Submission** (completed). Each campaign has its own webhook URL, so Surface sends to the right URL based on the trigger path. You do not need to pass `submission_type` in the payload. 1. In Customer.io, go to **Campaigns** and click **Create Campaign** 2. Click **Webhook** as the trigger type 3. Copy the **Webhook URL**. You'll use this for the **Dropped Off** path in [Step 2](https://www.withsurface.com/docs/guides/email-sequences-customerio-calendly/step-2-surface-workflow) 4. Click **Save & Next** ### [Set Up the Workflow](#set-up-the-workflow) Add two actions to this campaign: 1. **Create or Update Person**: so the lead exists in Customer.io 2. **Send Event**: so your partial-submission email campaign can start #### [Add "Create or Update Person"](#add-create-or-update-person) 1. Drag **Create or Update Person** into the workflow 2. Give it a name (e.g., "Create/Update Lead") 3. Configure the action: - **Workspace**: Select the workspace where you want to store leads - **Identifier**: Use `email` (or another field from your Surface form that uniquely identifies the lead) - **Identifier value**: Map to `trigger.email` (or the equivalent key from your webhook payload) - **Attributes**: Add any additional attributes you want to store (e.g., `firstName`, `lastName`) #### [Add "Send Event"](#add-send-event) 1. Drag **Send Event** into the workflow (after Create or Update Person) 2. Give it a name (e.g., "Partial Form Fills") 3. Configure the event: - **Who do you want to update?**: Select the same workspace - **Identifier**: Use `email` (or match your Create or Update Person identifier) - **Identifier value**: Map to `trigger.email` - **Event Name**: Use `partialFormFilled` (you'll use this in your event-triggered campaign in Step 3) Use the `trigger` object to reference incoming webhook data. For example, `trigger.email`, `trigger.firstName`, or `trigger.lastName`. The exact keys depend on the payload you send from Surface. 4. Click **Next** to review, then **Start Campaign** 5. **Save the Webhook URL** for the Dropped Off path Repeat the same process for completed submissions: 1. Create a **new** webhook campaign 2. Copy the **Webhook URL**. You'll use this for the **Form Submission** path in Step 2 3. Add **Create or Update Person** (same configuration as above) 4. Add **Send Event** with **Event Name**: `formCompleted` 5. Start the campaign and save the Webhook URL for the Form Submission path You now have **two webhook URLs**: one for partial, one for completed. [Step 2: Configure Surface Workflow](https://www.withsurface.com/docs/guides/email-sequences-customerio-calendly/step-2-surface-workflow), which sends form data to the right webhook URL for each trigger path. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 2: Configure Surface Workflow | Email Sequences with Customer.io and Calendly | Surface Docs URL: https://surface.thesurface.network/docs/guides/email-sequences-customerio-calendly/step-2-surface-workflow Email Sequences with Customer.io and Calendly Set up the Surface Workflow Builder to send form data to Customer.io via webhook when leads submit (partial or completed) Configure the **Surface Workflow Builder** to send a webhook to Customer.io whenever a lead submits your form, complete or partial. 1. In the Surface app, open your form 2. Go to the **Workflows** section 3. Click **Create Workflow** (or edit an existing workflow) Surface workflows support **paths** for different triggers, so you can handle both partial and completed submissions in **one workflow**: Trigger When it fires Customer.io webhook URL **Form Submission** When the lead completes the entire form URL from your **completed** webhook campaign **Dropped Off** When the lead abandons the form mid-way URL from your **partial** webhook campaign Add both triggers to your workflow. Each path sends to a **different** Customer.io webhook URL (from [Step 1](https://www.withsurface.com/docs/guides/email-sequences-customerio-calendly/step-1-webhook-trigger)), so the right event fires automatically. You do not need to pass `submission_type` in the payload. For each trigger path (**Dropped Off** and **Form Submission**): 1. Click the **+** button to add a new node 2. Select **HTTP Request** from the actions menu 3. In the configuration panel, set: - **Request URL**: - **Dropped Off** path → Paste the webhook URL from your **partial** Customer.io campaign - **Form Submission** path → Paste the webhook URL from your **completed** Customer.io campaign - **HTTP Method**: `POST` - **Body**: Same payload for both paths (see below) Use the `@` symbol in the workflow builder to insert form variables. Your payload should include: - **Identifier** (email): required for Customer.io to create/update the person - **Any other fields** you want to pass (name, form ID, etc.) Use the **same payload** for both paths. The webhook URL determines which event fires in Customer.io. Example payload: ``` { "email": "@email", "first_name": "@first_name", "last_name": "@last_name", "form_id": "@form_id", "submitted_at": "@submitted_at" } ``` Replace `@email`, `@first_name`, etc. with the actual variable names from your form. Press `@` in the workflow builder to see available fields. 1. Save the workflow 2. Activate it so it runs when leads submit your form 3. Test with a sample submission and verify the webhook reaches Customer.io After a test submission: 1. Check Customer.io **Campaigns** → your webhook campaigns → **Logs** to see if the webhook was received 2. Check **People** to confirm the lead was created or updated 3. Check that the correct event was recorded (`partialFormFilled` for Dropped Off, `formCompleted` for Form Submission) [Step 3: Event-Based Email Campaigns](https://www.withsurface.com/docs/guides/email-sequences-customerio-calendly/step-3-event-campaigns), the campaigns that run when these events fire. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 3: Event-Based Email Campaigns | Email Sequences with Customer.io and Calendly | Surface Docs URL: https://surface.thesurface.network/docs/guides/email-sequences-customerio-calendly/step-3-event-campaigns Email Sequences with Customer.io and Calendly Create event-triggered campaigns for partial and completed form submissions with customizable follow-up emails and delays Create **two event-triggered campaigns** in Customer.io: one for partial form submissions and one for completed. Each sends a series of follow-up emails with delays between them. 1. In Customer.io, go to **Campaigns** and click **Create Campaign** 2. Click **Event** as the trigger type 3. Configure the trigger: - **Event name**: `partialFormFilled` (must match the event from your partial webhook campaign in Step 1) - **Workspace**: Select the workspace where your leads are stored - Add any filters if needed (e.g., segment, attribute) Add your follow-up emails and delays to the campaign workflow: First email Add an **Email** block as the first step. This sends immediately when the person enters the campaign. Delay Add a **Delay** block. Set the delay (e.g., 2 days, 3 days) before the next touchpoint. Calendly check (Step 4) Add a **Send and receive data** (webhook) block that checks Calendly. If the meeting is booked, the person exits. Otherwise, continue. See [Step 4: Calendly Meeting Check](https://www.withsurface.com/docs/guides/email-sequences-customerio-calendly/step-4-calendly-check). Second email Add another **Email** block. This sends only if the person didn't book a meeting. Repeat Add another **Delay** → **Webhook (Calendly check)** → **Email**. Repeat for as many follow-ups as you want. Repeat the same process for completed submissions: 1. Create a new campaign with **Event** trigger 2. Set **Event name**: `formCompleted` (must match the event from your completed webhook campaign in Step 1) 3. Build the same structure: Email → Delay → Calendly check → Email → … 4. Use different copy and timing if you want (e.g., shorter delays for completed submissions, since they're more engaged) Completed leads are usually warmer, so a shorter, more sales-focused sequence often works. Partial leads tend to need more nurturing and a clearer call to action. 1. Review each campaign 2. Click **Start Campaign** for both 3. They will trigger when the corresponding events fire from your webhook campaign [Step 4: Calendly Meeting Check](https://www.withsurface.com/docs/guides/email-sequences-customerio-calendly/step-4-calendly-check), the webhook node that exits the campaign once a lead books a meeting. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 4: Calendly Meeting Check | Email Sequences with Customer.io and Calendly | Surface Docs URL: https://surface.thesurface.network/docs/guides/email-sequences-customerio-calendly/step-4-calendly-check Email Sequences with Customer.io and Calendly Add a webhook node to check if the lead has booked a Calendly meeting: exit the campaign if yes, continue if no Add a **Send and receive data** (webhook) action to your event-triggered campaigns. It calls the Calendly API to check whether the lead has booked a meeting. If they have, the person exits the campaign. If not, the campaign continues to the next email. - **Calendly API token**: Create a [Personal Access Token](https://developer.calendly.com/api-docs/b3A6NTkxNDA4-get-access-token) in your Calendly developer settings - **Organization URI** or **User URI**: From your Calendly account (required for the API) - **Event type URI**: The URI of the event type you want to check (e.g., "30-min discovery call") 1. In your event-triggered campaign (from [Step 3](https://www.withsurface.com/docs/guides/email-sequences-customerio-calendly/step-3-event-campaigns)), add a **Send and receive data** block **after each Delay** and **before each follow-up email** (except the first email) 2. Click the `Edit Request` button to configure the request. Call the Calendly [List Scheduled Events](https://developer.calendly.com/api-docs/2d5ed9bbd2952-list-events) endpoint with `invitee_email` to check if the lead has any scheduled meetings. ### [Request Setup](#request-setup) Setting Value **Method** `GET` **URL** See the sample URL below **Headers** `Authorization: Bearer YOUR_CALENDLY_TOKEN` **Sample URL** (replace `YOUR_ORG_ID` with your Calendly organization ID): ``` https://api.calendly.com/scheduled_events?organization=https%3A%2F%2Fapi.calendly.com%2Forganizations%2FYOUR_ORG_ID&invitee_email={{event.email}}&status=active&min_start_time=2000-01-01T00:00:00.000000Z&count=1 ``` The `invitee_email` parameter filters events by the lead's email. If the response `collection` has items, the meeting is booked. If it's empty, it's not. Store your Calendly token securely. In Customer.io, you can use a [snippet](https://docs.customer.io/snippets/) or workspace secret to avoid hardcoding it in the workflow. ### [Response Configuration](#response-configuration) Go to the **Response** tab in the webhook settings and add the following so you can use the Calendly API's pagination count in your branch logic: **Journey attributes** Name Value `count` `response.pagination.count` **Customer attributes** Name Value `count` `response.pagination.count` This stores the number of scheduled events returned by the API. If `count` is greater than 0, the lead has booked a meeting. After the webhook returns a response, add a **True/False Branch** to decide whether to exit or continue: 1. Add a **True/False Branch** block after the webhook 2. Click **Add condition** 3. Pick **Custom attribute** → `count` 4. Set the condition to **is greater than** → **the value** → `0` 5. Click **Add** and **Save** **True** path (count > 0): The meeting is booked. Add an **Exit** action or leave it empty so the person leaves the campaign. **False** path (count = 0): Connect to the next **Email** block. The flow for each "cycle" after the first email should be: ``` Delay → Webhook (Calendly check) → True/False Branch ├─ True (count > 0) → Exit └─ False (count = 0) → Email → (next Delay, etc.) ``` Repeat this pattern for every follow-up email. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Email Sequences with HubSpot | Email Sequences with HubSpot | Surface Docs URL: https://surface.thesurface.network/docs/guides/email-sequences-hubspot/overview [](https://www.withsurface.com/) [Help Center](https://surface-labs-knowledge-base.help.usepylon.com/)[Contact Us](mailto:founders@withsurface.com)[Dashboard](https://app.withsurface.com/) [Home](https://www.withsurface.com/docs)[Platform](https://www.withsurface.com/docs/platform)[For Developers](https://www.withsurface.com/docs/build)[Guides](https://www.withsurface.com/docs/guides)[Form Embedding](https://www.withsurface.com/docs/embedding/website-editors)[MCP](https://www.withsurface.com/docs/mcp-server/overview) Email Sequences with HubSpot Enroll leads in HubSpot email sequences when they submit or drop off your Surface form ## [Setup Steps](#setup-steps) [ ### Step 1: Create HubSpot Form Form with email required, all other fields optional ](https://www.withsurface.com/docs/guides/email-sequences-hubspot/step-1-hubspot-form)[ ### Step 2: Create HubSpot Sequence Automated emails, personalization tokens, meeting link ](https://www.withsurface.com/docs/guides/email-sequences-hubspot/step-2-hubspot-sequence)[ ### Step 3: Add Follow-Up Emails and Delays More steps and business-day delays ](https://www.withsurface.com/docs/guides/email-sequences-hubspot/step-3-follow-up-delays)[ ### Step 4: Add Automation Form submission → enroll in sequence ](https://www.withsurface.com/docs/guides/email-sequences-hubspot/step-4-automation)[ ### Step 5: Connect Surface Workflow Send Surface submissions to your HubSpot form ](https://www.withsurface.com/docs/guides/email-sequences-hubspot/step-5-surface-workflow) Ready to Get Started? See it on your own site, or open the app and build the first form. [Book a walkthrough](https://www.withsurface.com/book-a-demo)[Open the dashboard](https://app.withsurface.com/) Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. [Help Center](https://surface-labs-knowledge-base.help.usepylon.com/) Feature Requests? Tell us what is missing. We would rather hear it than guess. [Talk to us](https://www.withsurface.com/book-a-demo) [ HubSpot Tracking Add the HubSpot tracking script to your Surface form to track visitors ](https://www.withsurface.com/docs/guides/hubspot-forms/configure-tracking)[ Step 1: Create HubSpot Form Create a HubSpot form with all fields optional except email so partial Surface submissions can be recorded ](https://www.withsurface.com/docs/guides/email-sequences-hubspot/step-1-hubspot-form) ### On this page [Setup Steps](#setup-steps) --- # Step 1: Create HubSpot Form | Email Sequences with HubSpot | Surface Docs URL: https://surface.thesurface.network/docs/guides/email-sequences-hubspot/step-1-hubspot-form Email Sequences with HubSpot Create a HubSpot form with all fields optional except email so partial Surface submissions can be recorded Create a **HubSpot form** that Surface submits to when leads complete or drop off your Surface form. Make every field **optional except email**, so a partial submission (a lead who enters their email and leaves) still creates a valid form response in HubSpot for your automation to enroll. Already have a HubSpot form? See [Step 1: Configure HubSpot Form](https://www.withsurface.com/docs/guides/hubspot-forms/configure-hubspot-form) for how to make its existing fields optional. 1. In HubSpot, go to **Marketing** → **Forms** (or **Marketing** → **Lead Capture** → **Forms** depending on your HubSpot layout) 2. Click **Create form** and choose **Embedded** (or the form type that fits your use case) 3. Name the form (e.g., "Surface - Email sequence enrollment") 1. Add the fields you want to capture (e.g., **Email**, **First name**, **Last name**, **Company**) 2. For **Email**: keep it **required** so every submission has at least an email for the sequence 3. For **all other fields**: set them to **optional** (not required), so partial submissions from Surface are accepted Match these fields to the ones you map in your Surface workflow. Use the same **internal names** (e.g., `email`, `firstname`, `lastname`) when configuring [Create Form Response](https://www.withsurface.com/docs/guides/hubspot-forms/configure-workflow#map-surface-form-fields-to-hubspot-form-fields) so data lines up with your sequence personalization tokens. 1. Ensure each form field is **connected** to the correct HubSpot contact property (e.g., Email → `email`, First name → `firstname`) 2. Complete any other form settings (thank-you message, redirect, etc.) 3. **Publish** the form You don't need to embed this form on a page. Surface will submit to it via the API when you configure the workflow in [Step 5: Connect HubSpot Form with Surface Workflow](https://www.withsurface.com/docs/guides/email-sequences-hubspot/step-5-surface-workflow). Note the form name so you can select it in Step 4 (automation) and Step 5 (Surface workflow). [Step 2: Create HubSpot Sequence](https://www.withsurface.com/docs/guides/email-sequences-hubspot/step-2-hubspot-sequence), with the first email template, personalization tokens, and a meeting link. You'll connect this form to Surface in [Step 5](https://www.withsurface.com/docs/guides/email-sequences-hubspot/step-5-surface-workflow). Steps 2-4 are done in HubSpot (sequence and automation) first. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 2: Create HubSpot Sequence | Email Sequences with HubSpot | Surface Docs URL: https://surface.thesurface.network/docs/guides/email-sequences-hubspot/step-2-hubspot-sequence Email Sequences with HubSpot Create a HubSpot sequence with automated emails, personalization tokens, and meeting link Create a **HubSpot sequence** (or use an existing one) and add the first automated email, with **personalization tokens** from your contact fields and your **HubSpot meeting link**. 1. In HubSpot, go to **Sales** → **Sequences** → **Create sequence** 2. Name the sequence (e.g., "Surface form follow-up") 3. Under **Steps**, click **Automated emails** to add your first email 1. Use an **existing email template** from the list, or 2. Click **Create new template** to build one from scratch To personalize the email with the contact's name or other data from the form: 1. In the template editor, place the cursor where you want the dynamic value (e.g., `Hi {{ firstname }},` in HubSpot) 2. Click **Insert** → **Personalization tokens** 3. Choose **Contact** and then select the property you want (e.g., **First name**, **Last name**, **Company**) 4. In the token dropdown, configure a **fallback value** for contacts who don't have that field (e.g., "there" if first name is empty) 5. Click **Insert** Repeat for any other contact properties you want in the email body or subject line. Tokens pull from the contact record in HubSpot. When Surface sends a form response via Create Form Response, HubSpot updates the contact with the submitted fields, so values like first name and last name will be available in the sequence email if you mapped them in your workflow. To add a meeting link so leads can book a call: 1. In the template editor, click **Insert** → **Meetings** 2. Select your **HubSpot meeting link** (the one you use for scheduling) 3. Click **Insert** 1. Finish editing the subject line and body (including any other copy) 2. Click **Save** (or **Save template**) to store the template Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 3: Add Follow-Up Emails and Delays | Email Sequences with HubSpot | Surface Docs URL: https://surface.thesurface.network/docs/guides/email-sequences-hubspot/step-3-follow-up-delays Email Sequences with HubSpot Add more sequence steps with follow-up emails and business-day delays between each Add more emails to your HubSpot sequence and set **delays**, in business days, between each step. Repeat for as many follow-ups as you need. 1. In your sequence, under **Steps**, click the **+** button to add a new step 2. Choose **Automated email** (or the step type you want) 1. Click **Edit email** on the new step 2. Either **create a new template** or **use an existing one** 3. Add personalization tokens and your meeting link the same way as in [Step 2](https://www.withsurface.com/docs/guides/email-sequences-hubspot/step-2-hubspot-sequence) (Insert → Personalization tokens, Insert → Meetings) 4. Save the template when done To control how many days pass before this email sends: 1. Click **Delay** on the step (or in the step settings) 2. Set the delay in **business days** (e.g., 2, 3, or 5 business days after the previous step) 3. Save Typical patterns: 2-3 business days between the first and second email, then 3-5 for later follow-ups. Adjust based on your audience and how many touches you want. For each additional follow-up: 1. Click **+** to add another step 2. Click **Edit email** and set the content (new template or existing) 3. Click **Delay** and set the number of business days 4. Save Your sequence might look like: - **Step 1:** Automated email (sends immediately when enrolled) - **Step 2:** Delay 2 business days → Automated email - **Step 3:** Delay 3 business days → Automated email - **Step 4:** Delay 5 business days → Automated email - (Optional) **Step 5:** Task or other action Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 4: Add Automation | Email Sequences with HubSpot | Surface Docs URL: https://surface.thesurface.network/docs/guides/email-sequences-hubspot/step-4-automation Email Sequences with HubSpot Create a HubSpot automation that enrolls contacts in your sequence when they submit the form Create a **HubSpot automation** that fires when a contact submits the HubSpot form you use with Surface and **enrolls them in your sequence**, so they receive the emails you set up in Steps 2 and 3. 1. In your sequence, open the **Automate** tab 2. Click **Create an automation** 1. Set the trigger to **Form submission** 2. Choose **Contact submits a specific form** 3. Select the **HubSpot form** you created in [Step 1](https://www.withsurface.com/docs/guides/email-sequences-hubspot/step-1-hubspot-form) (the same form your Surface workflow sends to via Create Form Response) The form you select here must be the **exact same form** that your Surface workflow uses in the **Create Form Response** action. Otherwise, submissions from Surface won't trigger this automation. 1. Add an action and choose **Enroll contact in this sequence** (or the equivalent sequence enrollment action) 2. Configure **sender email** and **sender name** so emails come from the right address and identity 3. Review any other options (e.g., eligibility, max enrollments) if your HubSpot plan supports them 1. Click **Create** (or **Save**) to create the automation 2. Turn the automation **on** so it runs when the form is submitted Contacts who submit that form are then enrolled, whether they came from a Surface **Dropped Off** or **Form Submission** workflow. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 5: Connect HubSpot Form with Surface Workflow | Email Sequences with HubSpot | Surface Docs URL: https://surface.thesurface.network/docs/guides/email-sequences-hubspot/step-5-surface-workflow Email Sequences with HubSpot Set up a Surface workflow to send form submissions to your HubSpot form so leads get enrolled in your sequence Configure **Surface** to send form submissions to the **same HubSpot form** you created in [Step 1](https://www.withsurface.com/docs/guides/email-sequences-hubspot/step-1-hubspot-form). When a lead submits or drops off your Surface form, Surface creates a form response in HubSpot, which triggers the automation from [Step 4](https://www.withsurface.com/docs/guides/email-sequences-hubspot/step-4-automation) and enrolls them in your sequence. For more detail and alternative setups, see the full guide [Configure HubSpot in Surface Workflow](https://www.withsurface.com/docs/guides/hubspot-forms/configure-workflow). 1. Navigate to the **Workflow Builder** in Surface 2. Add any HubSpot action and click **Connect** 3. Select your HubSpot organization when prompted 4. Accept Surface Labs invite 5. Click **Connect App** to complete setup 1. Go to **Workflow Builder** from the sidebar 2. Click **Create workflow** 3. Choose trigger type: - **Dropped Off**: For partial submissions (lead leaves before completing the form). Use this so drop-offs still get enrolled in your sequence. - **Finished**: For complete submissions only (lead submits the full form) Add one or both triggers depending on whether you want to enroll partial submissions, completed submissions, or both. 1. Click **\+ Actions** 2. Select **HubSpot** from the actions list 3. Choose **Create Form Response** action ### [Select Your HubSpot Form](#select-your-hubspot-form) 1. Click on the **HubSpot Form** dropdown 2. Select the **same form** you created in [Step 1](https://www.withsurface.com/docs/guides/email-sequences-hubspot/step-1-hubspot-form) and used in your [Step 4](https://www.withsurface.com/docs/guides/email-sequences-hubspot/step-4-automation) automation This form must match the one in your HubSpot automation so that submissions from Surface trigger enrollment in your sequence. ### [Get Internal Names from HubSpot Form Fields](#get-internal-names-from-hubspot-form-fields) You need the **internal names** (API names) of your HubSpot form fields. These are what you enter as the **Value** when mapping in Surface. To find the internal name for each HubSpot form field: 1. In your HubSpot form editor, **select the field** (e.g., Email or First Name) 2. In the **Edit field** panel on the left, click **Connected property** (shown as "Connected" with a green indicator) 3. Under the Connected property section, note the **Internal name** (e.g., `email`, `firstname`) The internal name is different from the field label. Always use the exact internal name from the Connected property section when mapping in Surface. ### [Map Surface Form Fields to HubSpot Form Fields](#map-surface-form-fields-to-hubspot-form-fields) Map your Surface form fields to the HubSpot form so contact data (and sequence personalization) is correct: 1. Click **Add column** to add a new field mapping 2. **Key (Surface Field)**: Select the field from your Surface form (e.g., from Form Submission or Lead) - Example: `email`, `firstName`, `lastName` 3. **Value (HubSpot Internal Name)**: Enter the exact internal name from HubSpot - Example: `email`, `firstname`, `lastname` 4. **HubSpot Field**: Select the corresponding HubSpot form field from the dropdown (e.g., Email, First name, Last name) **Mapping examples:** Surface Field (Key) HubSpot Internal Name (Value) HubSpot Field `email` (Form Submission) `email` Email `firstName` (Form Submission) `firstname` First Name `lastName` (Form Submission) `lastname` Last Name The **Value** must match the HubSpot internal name exactly (case-sensitive). This ensures data flows into the right contact properties and your sequence personalization tokens work. 1. Save the workflow 2. Activate it so it runs when leads submit or drop off your Surface form - For optional HubSpot actions (Create Contact, Create Deal, and the rest), see [Configure HubSpot in Surface Workflow](https://www.withsurface.com/docs/guides/hubspot-forms/configure-workflow#configure-additional-hubspot-actions-optional) - Back to the [Email Sequences with HubSpot overview](https://www.withsurface.com/docs/guides/email-sequences-hubspot/overview) Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Enable Cloudflare Turnstile | Guides | Surface Docs URL: https://surface.thesurface.network/docs/guides/enable-cloudflare-turnstile Enable Cloudflare Turnstile and add the widget to your Surface form to block spam and abuse. 1. Login to [Cloudflare Dashboard](https://dash.cloudflare.com/) 2. Navigate to **Protect & Connect > Application security > Turnstile** Click on **Add new widget** to create a new Turnstile widget. 1. Set up the widget configurations 2. In the **Hostnames** field, add `forms.withsurface.com` or the [verified custom domain](https://www.withsurface.com/docs/platform/traffic/custom-domains) used by your form 3. Click `Add` button to add the host 1. Click **Create** to create the widget 2. After creating the widget, copy the **Site Key** and **Secret Key** 1. Navigate to your Surface Form settings page 2. Go to **Cloudflare Turnstile** section 3. Paste the **Site Key** and **Secret Key** that you copied in Step 4 4. Click **Save** to save the settings 1. In the Form Builder, navigate to the step where you want to add the Turnstile widget 2. Click **\+ Add component** or **Copy existing component** 3. Select the **Turnstile** widget component from the component list 4. The widget now appears in your form and is checked when someone submits it Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Creating Your First Surface Form | Guides | Surface Docs URL: https://surface.thesurface.network/docs/guides/first-form Build, style, and share your first Surface form. Navigate to the [Surface Dashboard](https://app.withsurface.com/) and log in with your credentials. Go to the `Forms` tab and press `Create New Form` in the navigation bar. ### [Start from Scratch or Choose a Template](#start-from-scratch-or-choose-a-template) Choose a layout: - **Single Pane**: A simple form layout with a single column - **Dual Pane**: A form layout with two columns, ideal for marketing purposes ### [Overview](#overview) Surface Forms gives you a starting template. Edit it, or build your own. ### [Form Steps](#form-steps) Form steps are listed on the left side of the form builder under the `Steps` section. #### [Add New Steps](#add-new-steps) To add a new step, click on the `+ Add step` button or copy an existing step by clicking on the `Copy step` button. ### [Edit the Step](#edit-the-step) #### [Add New Components](#add-new-components) To add a new component, click on the `+ Add component` button or copy an existing component from the form by clicking on the `Copy existing component` button. #### [Question Pane and Marketing Pane](#question-pane-and-marketing-pane) Each step is divided into two tabs: `Questions` and `Marketing`. - The `Questions` tab is used to add questions such as text fields, dropdowns, multiple choice questions, etc to the form. - The `Marketing` tab is for adding marketing components such as a logo, background image, etc to the form. ### [Customize Layout](#customize-layout) #### [Question Pane Layout Customization](#question-pane-layout-customization) Both the `Questions` and `Marketing` panels have layout options, including: - `Horizontal Padding` - `Maximum Width of the Pane` #### [Marketing Pane Layout Customization](#marketing-pane-layout-customization) The marketing pane has extra options: 1. Customize the `Marketing Pane` width 2. Add a `Background Image` 3. Add a `Logo` in the header: - Expand the `Add Component` dropdown and select the `Image` component to add a logo in the marketing header ### [Edit a Component](#edit-a-component) To edit a component, either click on the component directly from the form preview or click on the component from the components list in the right side panel. ### [Style a Component](#style-a-component) Each component has a `Style` panel. The options vary by component, and include: - `Background Color` - `Text Color` - `Border Color` - `Border Width` - `Border Radius` - `Box Shadow` ### [Advanced Features](#advanced-features) #### [Customize Marketing Pane Globally](#customize-marketing-pane-globally) To customize the marketing pane globally, go to the `Marketing` under `Design` section. Options include: - `Fill`: Choose from a range of options like gradient, solid color, image, etc for the background of the marketing pane. - `Corner Radius`: Control the corner radius of the marketing pane. - `Logo`: Add a logo to the marketing pane. #### [Delete Marketing Pane for a Particular Step](#delete-marketing-pane-for-a-particular-step) To delete the marketing pane for a particular step, go to the `Marketing` under `Layout` section and click on the `Delete Marketing Section` button. Change the form name in the navigation bar and save the form by clicking on the `Save` button. Share the form using the `Share` button in the navigation bar. - You can share the form using the `Share Link` or `Embed Code` to embed the form on your website. Read more about how to [embed a Surface Form](https://www.withsurface.com/docs/platform/forms/embedding) on your site. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Translate a Form | Guides | Surface Docs URL: https://surface.thesurface.network/docs/guides/form-translations Turn on translations, let Surface translate every text into up to four languages, review them in the editor, and serve each visitor the form in their language. Surface translates the texts you wrote: questions, options, buttons, placeholders, marketing copy and thank-you screens. Validation messages and the other copy Surface adds already follow the form language. Supported languages: English, Portuguese, Spanish, French, Chinese, Arabic, Japanese and Korean. Open **Form Settings › Language**. 1. **Form language** is the language you wrote the form in. 2. Switch on **Translate this form**. The editor gains a language menu, and the published form serves its translated languages. Three settings appear once it is on: - **Translated languages**: the languages this form is translated into. They are added and removed in the editor (next step). - **Default language**: shown when nothing else picks a language for a visitor. - **Detect the visitor's browser language**: use the browser's language when it is one of the translated ones. In the editor, the language menu sits above the preview. It lists the form language and every translated language with its status: **Up to date**, **N to translate**, **Not translated** or **Failed**. Choose **Add language…** and pick one. Every text is translated right away; a form can hold up to four translated languages. Translations are produced by AI. Preview and read through them before you publish, especially product names and legal copy. Pick a language from the menu to preview the whole form in it, step by step. While a translated language is previewed, selecting a component shows that component's texts in the language, each with the original above it. Edit any of them; your wording stays until the original text changes. **Switch to English** (or your form language) to edit the form itself. ## [Step 4: Review every text](#step-4-review-every-text) **Review translations…** in the language menu opens every text of the form, grouped by step and component. From here you can: - filter to **Needs translation** to see only texts that changed or were never translated; - **Translate changed** to translate those and keep everything else, including your edits; - **Retranslate all** or **Remove language** from the ⋯ menu. When you change a text after it was translated, the editor marks it: the language menu shows how many texts need translating, and the Publish menu offers **Translate N texts & publish** next to **Publish without translating**. A text published without a translation shows in the form language. The first of these that names a language the form is translated into wins: 1. **The Surface tag**: `data-lang` on the tag, the `language` option of an embed, or a `SurfaceSetLanguage()` call (see below). 2. **The URL**: `?surface-form-language=es` on the form's own link or on the page embedding it. 3. **The browser language**, when **Detect the visitor's browser language** is on. 4. **The default language** from Form Settings. Anything else, or a language the form is not translated into, shows the form language. Responses, workflows and integrations always see the form language: option values and question labels do not change with the visitor's language. ### [A link in one language](#a-link-in-one-language) Add the parameter to the form link, or to the page the form is embedded on: ``` https://forms.withsurface.com/s/YOUR_FORM_ID?surface-form-language=es ``` ### [Every form on the page](#every-form-on-the-page) Set `data-lang` on the [Surface tag](https://www.withsurface.com/docs/platform/traffic/surface-tag). All embedded forms translated into that language render in it; the others keep their own. ``` ``` ### [One embed in a fixed language](#one-embed-in-a-fixed-language) Pass `language` as the fourth argument of any [embed](https://www.withsurface.com/docs/platform/forms/embedding). It wins over the page's `data-lang` and over later `SurfaceSetLanguage()` calls. ``` ``` ### [Switch languages from your own language picker](#switch-languages-from-your-own-language-picker) ``` // Every embedded form without a language of its own switches in place; answers are kept. window.SurfaceSetLanguage("fr"); // Back to the URL, browser and default rules. window.SurfaceSetLanguage(null); ``` Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 3: Add Surface Domain to HubSpot | HubSpot Forms Configuration | Surface Docs URL: https://surface.thesurface.network/docs/guides/hubspot-forms/add-surface-domain HubSpot Forms Configuration Add your Surface form domain to HubSpot for proper tracking and form submissions To enable proper tracking and form submissions, add the domain that serves your Surface form to your HubSpot account: 1. In your HubSpot account, navigate to **Settings** → **Tracking & Analytics** → **Tracking Code** 2. Click on the **Advanced Tracking** tab 3. Under **Additional site domains**, click **\+ Add domain** 4. Enter `forms.withsurface.com`, or enter your [verified custom domain](https://www.withsurface.com/docs/platform/traffic/custom-domains) if the form uses one 5. Click **Save** Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 1: Configure HubSpot Form | HubSpot Forms Configuration | Surface Docs URL: https://surface.thesurface.network/docs/guides/hubspot-forms/configure-hubspot-form HubSpot Forms Configuration Configure your HubSpot form to accept submissions from Surface Forms You can **skip this step** if you already have a HubSpot form you want to send submissions to. Go straight to [Configure HubSpot in Surface Workflow](https://www.withsurface.com/docs/guides/hubspot-forms/configure-workflow) to map your form and set up the sync. Otherwise, create or adjust a HubSpot form so it accepts partial submissions. 1. Log in to your **HubSpot** account 2. Navigate to **Marketing** → **Forms** 3. Click on the form you want to modify For submissions to work, you may need to make some required fields optional: 1. Click on each field that might be empty in submissions 2. Find the **Required** checkbox or toggle 3. **disable** the Required option for fields that: - Are not essential for lead capture - May be filled in later stages of the form - Are not needed for your workflows 4. **Keep required** any fields that are: - Essential for your workflows - Needed for contact identification (like email) - Required for your business logic - **Workflow Testing**: Test workflows with both partial and complete submissions - **Documentation**: Document which fields are optional and why - **Monitoring**: Track partial vs. complete submissions to optimize your forms Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # HubSpot Tracking | HubSpot Forms Configuration | Surface Docs URL: https://surface.thesurface.network/docs/guides/hubspot-forms/configure-tracking HubSpot Forms Configuration Add the HubSpot tracking script to your Surface form to track visitors Add HubSpot tracking to your Surface form to track visitor behavior and identify anonymous visitors. 1. **Navigate to HubSpot Settings** - In your HubSpot account, click the **settings** icon (⚙️) in the top navigation bar 2. **Access Tracking Code** - In the left sidebar, look for **Account Management** - Click on **Tracking Code** under the Account Management section 3. **Copy the Tracking Code** - You'll see your HubSpot tracking code displayed in a text box - Copy the entire tracking script code - The code typically looks like: ``` ``` 1. **Open Form Settings** - Go to your Surface form dashboard - Navigate to the form you want to add HubSpot tracking to - Click on **Settings** 2. **Toggle on Cookie Tracking** - In the form settings, look for **Cookie Tracking** section - Toggle on **Enable Cookie Tracking** to track UTMs, first landing page, and lead sources 3. **Find HubSpot Tracking Option** - In the form settings, look for **Ads / Tracking** section - Click on **HubSpot Tracking** 4. **Enable and Configure Tracking** - Toggle the **Enable HubSpot tracking** switch to turn it on - Paste the HubSpot tracking script you copied in Step 1 into the script field below - Click **Save** to apply the changes Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Step 2: Configure HubSpot in Surface Workflow | HubSpot Forms Configuration | Surface Docs URL: https://surface.thesurface.network/docs/guides/hubspot-forms/configure-workflow HubSpot Forms Configuration Set up workflows in Surface to send form submissions to HubSpot Set up a workflow in Surface to send form submissions to your HubSpot form. 1. Navigate to the **Workflow Builder** in Surface 2. Add any HubSpot action and click **Connect** 3. Select your HubSpot organization when prompted 4. Accept Surface Labs invite 5. Click **Connect App** to complete setup 1. Go to **Workflow Builder** from the sidebar 2. Click **Create workflow** 3. Choose trigger type: - **Finished** - For complete submissions - **Dropped Off** - For partial submissions 1. Click **\+ Actions** 2. Select **HubSpot** from the actions list 3. Choose **Create Form Response** action ### [Select Your HubSpot Form](#select-your-hubspot-form) 1. Click on the **HubSpot Form** dropdown 2. Select the form you want to use for this workflow ### [Get Internal Names from HubSpot Form Fields](#get-internal-names-from-hubspot-form-fields) You need the **internal names** (also called API names) of your HubSpot form fields. These are what you enter as the **Value** when mapping in Surface. To find the internal name for each HubSpot form field: 1. In your HubSpot form editor, **select the field** you want to map (e.g., Email or First Name) 2. In the **Edit field** panel on the left, click on **Connected property** (it will show as "Connected" with a green indicator) 3. Under the Connected property section, you'll see the **Internal name** (e.g., `email` or `firstname`) The internal name is different from the field label. For example, a field labeled "Email Address" might have an internal name of `email` or `emailaddress`. Always use the exact internal name shown in the Connected property section. ### [Map Surface Form Fields to HubSpot Form Fields](#map-surface-form-fields-to-hubspot-form-fields) Map your Surface Form fields: 1. Click on **Add column** button to add a new field mapping 2. **Key (Surface Field)**: Select the field from your Surface Form - Example: `email` from Form Submission or Lead - Example: `firstName` from Form Submission or Lead 3. **Value (HubSpot Internal Name)**: Enter the exact internal name you found in HubSpot - Example: `email` (from the Email field's Connected property) - Example: `firstname` (from the First Name field's Connected property) 4. **HubSpot Field**: Select the corresponding HubSpot form field from the dropdown - Example: Email - Example: First Name **Mapping Examples:** Surface Field (Key) HubSpot Internal Name (Value) HubSpot Field `email` (from Form Submission) `email` Email `firstName` (from Form Submission) `firstname` First Name The **Value** field must match the internal name exactly as shown in HubSpot's Connected property section. This is case-sensitive: `email` is different from `Email` or `EMAIL`. You can add multiple HubSpot actions to your workflow: - **Create Contact** - Create a new contact in HubSpot - **Create or Update Contact** - Create or update a contact - **Create Company** - Create a company record - **Create Deal** - Create a new deal - **HubSpot AI Agent** - Use AI to manage contacts and deals automatically Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Custom Configuration | HubSpot Forms Configuration | Surface Docs URL: https://surface.thesurface.network/docs/guides/hubspot-forms/manual-setup [](https://www.withsurface.com/) [Help Center](https://surface-labs-knowledge-base.help.usepylon.com/)[Contact Us](mailto:founders@withsurface.com)[Dashboard](https://app.withsurface.com/) [Home](https://www.withsurface.com/docs)[Platform](https://www.withsurface.com/docs/platform)[For Developers](https://www.withsurface.com/docs/build)[Guides](https://www.withsurface.com/docs/guides)[Form Embedding](https://www.withsurface.com/docs/embedding/website-editors)[MCP](https://www.withsurface.com/docs/mcp-server/overview) HubSpot Forms Configuration Select your target HubSpot form and define exactly how fields map between Surface and HubSpot [ ### Step 1: Configure HubSpot Form Set up your HubSpot form to accept submissions with proper field configuration ](https://www.withsurface.com/docs/guides/hubspot-forms/configure-hubspot-form)[ ### Step 2: Configure HubSpot in Surface Workflow Set up workflows in Surface to send form submissions to HubSpot ](https://www.withsurface.com/docs/guides/hubspot-forms/configure-workflow)[ ### Step 3: Add Surface Domain to HubSpot Add your Surface form domain to HubSpot's Additional Site Domains for proper tracking ](https://www.withsurface.com/docs/guides/hubspot-forms/add-surface-domain) Ready to Get Started? See it on your own site, or open the app and build the first form. [Book a walkthrough](https://www.withsurface.com/book-a-demo)[Open the dashboard](https://app.withsurface.com/) Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. [Help Center](https://surface-labs-knowledge-base.help.usepylon.com/) Feature Requests? Tell us what is missing. We would rather hear it than guess. [Talk to us](https://www.withsurface.com/book-a-demo) [ One Click Setup Create HubSpot forms from Surface and start syncing partial & complete submissions ](https://www.withsurface.com/docs/guides/hubspot-forms/one-click-setup)[ Step 1: Configure HubSpot Form Configure your HubSpot form to accept submissions from Surface Forms ](https://www.withsurface.com/docs/guides/hubspot-forms/configure-hubspot-form) --- # One Click Setup | HubSpot Forms Configuration | Surface Docs URL: https://surface.thesurface.network/docs/guides/hubspot-forms/one-click-setup HubSpot Forms Configuration Create HubSpot forms from Surface and start syncing partial & complete submissions One Click Setup creates two HubSpot forms for you, one for complete submissions and one for partial ones, and starts sending submissions to them. 1. Go to **Form Settings** → **HubSpot** 2. Click on **Connect HubSpot** if you're not already authenticated 3. Follow the on-screen instructions to authenticate 4. Select your HubSpot organization when prompted 5. Accept the necessary permissions to complete the connection ## [Step 2: Add Surface Domain to HubSpot](#step-2-add-surface-domain-to-hubspot) To enable proper tracking and form submissions, add the domain that serves your Surface form to your HubSpot account: 1. In your HubSpot account, navigate to **Settings** → **Tracking & Analytics** → **Tracking Code** 2. Click on the **Advanced Tracking** tab 3. Under **Additional site domains**, click **\+ Add domain** 4. Enter `forms.withsurface.com`, or enter your [verified custom domain](https://www.withsurface.com/docs/platform/traffic/custom-domains) if the form uses one 5. Click **Save** 1. Under **HubSpot Connection**, toggle on **Enable HubSpot Sync** 2. Surface will automatically: - Create a form in HubSpot for finished submissions - Create a form in HubSpot for incomplete submissions - Start syncing form submissions to HubSpot - [HubSpot Tracking](https://www.withsurface.com/docs/guides/hubspot-forms/configure-tracking) - Configure HubSpot tracking to properly track UTMs, first landing page, and lead sources Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Connect Surface to Your HubSpot Forms | HubSpot Forms Configuration | Surface Docs URL: https://surface.thesurface.network/docs/guides/hubspot-forms/overview HubSpot Forms Configuration Configure Surface Forms to supercharge your HubSpot forms with partial response tracking, user journey insights, and more. - [HubSpot Workflows](https://www.withsurface.com/docs/platform/integrations/hubspot) - Learn about HubSpot integration in Surface - [HubSpot Tracking](https://www.withsurface.com/docs/platform/integrations/hubspot-tracking) - Detailed HubSpot tracking documentation - [Send Data to HubSpot](https://www.withsurface.com/docs/guides/send-data-to-hubspot) - General guide for sending data to HubSpot Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Load Your Vault and Get Your First Agent Draft | Guides | Surface Docs URL: https://surface.thesurface.network/docs/guides/load-your-vault About an hour of work that changes the output of every agent you run afterwards. Every agent reads the Vault before it drafts anything, so what is in it decides whether you edit the output or delete it. Loading it takes about an hour. You need a Surface environment. Vault is in the default MCP connection, so no `?tools=` change is needed from an assistant. The scan builds the tree from your marketing site, so parts of it will be wrong. Open `product/positioning.md` first. Find the three claims you could not defend on a sales call and rewrite them into ones you could. Every agent reads this file. Four documents, 200 words each. Do not polish them. ``` # sales/objections.md The five things buyers push back on, and the answer that actually lands. Written the way you would say it out loud, not the way a battlecard says it. # brand/voice.md Rules, not adjectives. "Never open on an industry statement." "Banned: solution, leverage, seamless." "Name the customer or cut the claim." # customers/proof.md Named customers, real numbers, quotable lines. Nextiva: 37% more users converted. Not "leading companies see results." # product/icp.md Who you sell to. And explicitly who you do not: agencies, students, competitors doing research. ``` Keep to things that are true, useful, and nowhere on your public site. More ways to add documents: [getting docs in](https://www.withsurface.com/docs/platform/vault/getting-docs-in). Pick something real that you would otherwise write this week. From any MCP client: _"Read `product/positioning.md` and `sales/objections.md` from the Vault, then draft the intro for a comparison page against \[competitor\]."_ The draft will be wrong in one or two specific ways. Do not edit it. Name the problem in one sentence "It opened with a generic industry statement and used 'solution' twice." Add the rule to brand/voice.md, in the app Write the rule, not the fix. Re-run the identical prompt If it still breaks the rule, the rule was ambiguous. Make it more literal. Two or three rounds is usually enough: [writing in your voice](https://www.withsurface.com/docs/platform/vault/voice). Every agent reads these files first: [content](https://www.withsurface.com/docs/platform/campaign-agents/content-agent), [competitor](https://www.withsurface.com/docs/platform/campaign-agents/competitor-agent), [SAM](https://www.withsurface.com/docs/platform/vault/sam). Want a second pair of eyes on it? Bring the Vault you built and one draft you did not like. Most fixes are three lines in `brand/voice.md`. [Book 30 minutes](https://www.withsurface.com/book-a-demo) Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Set Up the Outbound Email Skill | Guides | Surface Docs URL: https://surface.thesurface.network/docs/guides/outbound-email-skill Find prospects, qualify accounts, and prepare personalized email drafts with the Surface Campaign Pipeline skill. Give your AI agent a repeatable workflow for outbound email. The **Surface Campaign Pipeline** skill starts with three tasks in Surface: find prospects, qualify accounts, and prepare personalized outreach. It can split out additional jobs when your campaign needs them. Campaign context, research, and progress stay in your Surface Vault so each task can pick up where the last run left off. Agent Skill · 5 Files · Surface MCP Surface Campaign Pipeline Paste the complete instructions into an agent connected to Surface MCP, or download the skill for repeat use. Copy includes every supporting instruction. Download includes the complete folder as a ZIP. Preview Skill Files File ``` --- name: surface-campaign-pipeline description: Set up, extend, resume, or monitor a Surface Vault campaign using Surface MCP. Use for focused campaign tasks, contact discovery, qualification, draft outreach, requested reply sync, recovery, and health checks. --- # Surface campaign pipeline Create a campaign operated through committed Vault records. **Prospect → Qualify → Draft Outreach is the default starting shape, not a fixed task count. Every task must have one clear job with an independently verifiable result.** Extend or split the pipeline when the campaign needs it. Use Surface MCP for all campaign, Vault, connection-catalog, and task operations. Public web research may inform seller/ICP facts when permitted. Do not fall back to SQL, app REST, browser automation, credential files, or direct provider tools to complete campaign operations. Use the providers the user's Surface environment actually exposes. Clay, Apollo, MarqRadar, and Amplemarket are examples, not dependencies. Missing capabilities produce explicit blockers or Vault-only output, never invented tools or a false claim of a working pipeline. ## Scope and intake 1. Establish seller, target segment, intended team/environment, provider preferences, and whether the user wants setup, commissioning, recurring operation, repair, or a health check. Reuse supplied answers. When an app URL is supplied, anchor reads and changes to its environment/task IDs; otherwise resolve the intended environment through Surface MCP. Verify returned identifiers: a production hostname or matching campaign name does not distinguish production from test. Save the selected identifiers and ask only when scope is ambiguous. 2. List scheduled-task connections, browse campaign files, and list existing tasks. Follow pagination. Resume matching campaigns with saved IDs; a failed run does not justify another folder/task. 3. Check workspace Company files describe the actual seller before borrowing claims or exclusions. Otherwise keep sourced seller context inside this campaign. Record URLs and uncertainty. Never invent customers, proof, contacts, or evidence. 4. Present defaults briefly and proceed when sane defaults were authorized. Ask only for material missing facts, especially seller/segment, intended environment, or sender mailbox. Obtain sender first name from the user or a verified profile, not a guess from an address. Do not impose per-file approval checkpoints. Suggested starting values; adapt to user intent, provider latency, and current tool limits: | Setting | Starting value | | --- | --- | | Cadence | Hourly: Prospect :00, Qualify :20, Draft Outreach :40 | | Timezone | User's stated timezone; otherwise environment timezone, explicitly disclosed | | Prospect batch | One qualified existing account, up to two contacts, then at most one new account/run; omit contact work when separately owned | | Qualify batch | One account/run, including resumed work | | Outreach batch | Up to two contacts/run; fewer when needed to complete and save drafts | | Commissioning ceiling | Suggest 30 new accounts; record whether a ceiling applies to recurring operation | | Task budget | 15 minutes, 20 documents, 60,000 output tokens | | Soft stop | Stop new work by 8 minutes, 12 provider calls, or about 35,000 output tokens | | Provider call ceiling | 15 per run, including reads, writes, polls, and verification | | Worker steps | Plan below the observed 24-step ceiling; inspect current limits and reserve steps for persistence and finalization | | Outreach | Email only; four steps on business days 0, 3, 7, 11 | | Publication | Inactive drafts only; no launch, resume, activation, or sending | | Notifications | Vault summaries; Slack only when separately requested with a resolved destination | These are ceilings, not quotas. Do not widen the ICP to fill them. The account ceiling limits **new accounts**, not bounded contact repair for existing accounts. Increase throughput only after consecutive measured runs consistently commit every expected record and verify provider outcomes within budget. More time or tokens cannot overcome a step ceiling. Before recurring operation, disclose any remaining discovery pause or ceiling and its release condition. An instruction to unpause discovery or remove a ceiling must be reflected in both saved definitions and task instructions; do not leave an older gate silently stopping work. Removing a total ceiling preserves per-run budgets. ## Choose task boundaries Define each task by its one job, committed inputs, eligibility gate, owned outputs, allowed operations, cadence, budget, and observable completion condition. Several tool calls can support one job. Split work when it has its own queue, retry policy, cadence, permissions, or failure mode that needs independent monitoring and adjustment. For a simple campaign, the three defaults may suffice. When contact discovery follows qualification or needs repeated fallbacks, use **Prospect → Qualify → Find Contacts → Draft Outreach**. CRM account-fit checks may warrant their own task if they repeatedly block discovery. Reply Sync is a separate job when requested; do not fold inbox processing or CRM updates into outreach drafting. Add only jobs needed by this campaign. When splitting an existing task, transfer its pending work and output ownership, remove that responsibility from the original task, and update downstream reads and gates together. Keep one writer per file. Commission the new handoff before enabling its recurrence; do not create two tasks that both keep repairing the same records. ## Build the campaign contract Read [references/vault-contract.md](references/vault-contract.md) when creating/adapting files. Build seller context, ICP, exclusions, complete sequence copy, persistence templates, and initial checkpoints before task creation. Seed empty data tables, not fake prospects. Choose an outreach representation before marking setup ready: - Prefer reusable persona sequences with **documented per-contact fields** for every variable part of every email, and a way to verify each recipient's rendered content. - If unsupported, use a dedicated draft per contact when the provider supports it and this fits the user's scope. Name it deterministically with campaign, copy version, persona, and stable contact ID. Build across bounded runs if needed. - Otherwise choose `vault_only`: save personalized copy and disclose that automatic provider enrollment is unavailable. Do not call this a fully commissioned external-outreach pipeline. Never put one recipient's literal company/evidence into a shared sequence and reuse it for other companies. Preserve existing occupied drafts, reconcile them, and choose a compatible strategy for future contacts. Use `ready_for_draft_pipeline` only when the core contract is coherent. Track readiness by stage: a missing sender/outreach connector must not block account discovery or research. Missing qualification capability blocks Qualify and downstream eligibility, not setup files. Draft-copy approval is not live-send authorization. ## Create the required tasks Read [references/task-instructions.md](references/task-instructions.md). Compile its short shared block plus the relevant job and only the optional rules that job owns. Resolve environment, paths, grants, and outcome; keep account names, exceptions, search/enrichment IDs, and recovery history in account records. Store campaign policy, schemas, and provider procedures in Vault definitions/templates. Runtime tasks cannot read this local skill, so populate those files before saving instructions and retain critical safety/finalization rules in the prompt. Replace accumulated prompt patches rather than append another exception. Migrate their facts and unresolved work to the owning account records, read them back, and save a short generic task. Aim for roughly 4,000 characters for ordinary tasks, measuring the complete assembled prompt; this is a concision target, not a reason to drop essential rules. One observed Prospect cleanup reduced about 22,000 characters to 3,900. Name tasks `{Short campaign name} · {Job}`, using Prospect, Qualify, and Draft Outreach for the defaults and equally specific names for extensions. Save every returned task ID/URL and its job in `setup-log.md`. Grant only each stage's provider(s) and Vault reads/writes. POST-based research/enrichment may need a write grant; constrain permitted operations in instructions. A broad connector write grant does not authorize live outreach. Grant optional web reads only where needed; no Slack by default. Inspect current Surface schemas rather than assuming config fields or provider capabilities. Create tasks paused and verify returned state. For existing tasks, use `get_scheduled_task` and current `updatedAt` for updates. Omitted fields preserve configuration; supplied permission arrays replace arrays. Re-read and merge after conflicts. Wait if an active run prevents editing. Preserve another actor's acceptance/scheduling choices unless changing them is requested. Offsets are intended spacing, not dependencies or guaranteed execution times. Inspect actual next-run information and any scheduler execution window when exposed; report uncertainty when Surface only exposes nominal cron times. Consume committed eligible rows and own separate files; never assume the prior stage succeeded because its scheduled time passed. ## Verify and commission within authorized scope Setup verification is read-only: read back files and all task configurations, grants, exact paths, stage gates, copy strategy, and timezone. Check all referenced fields exist, copy is complete, days increase, exclusions exist, and unresolved settings are explicitly blocked. Check that eligibility rules agree across the ICP, workflow, saved instructions, and existing holds; account qualification, evidence eligibility, contact readiness, and enrollment are separate facts. Resolve conflicts during setup before commissioning. Report setup separately from runtime verification. `run_scheduled_task` performs real external actions and may spend credits. A request to create this skill or set up tasks alone is not authorization to run them. Continue without re-asking when commissioning/recurring operation was already authorized. Otherwise leave the concrete setup paused and ask only for the missing execution authorization. For authorized commissioning, follow the workflow's dependency order: 1. Run Prospect once; inspect all activity/write pages and current saved records. Check write order: existing contact record first, new account then directory, checkpoint last. Proposals are not durable until finalization; a successful provider call is not persisted progress. Commission any separate CRM Fit gate before its dependent tasks. 2. Run Qualify against committed scan-ready accounts. Pending reports are normal: save exact IDs and resume with a fresh bounded polling allowance in a later authorized run. Never resubmit to make the first test look complete. 3. Commission any added jobs in dependency order against their committed inputs. For Find Contacts, inspect the actual search coverage and fallback checkpoint, including zero-result outcomes. For Reply Sync, verify message coverage and destination mapping in a dry run before authorized CRM writes. 4. Run Draft Outreach when a qualified account has an eligible contact. Verify personalized content, sender, provider draft lifecycle, membership, and contacted/sent state when available. Preserve explicit user sender confirmations and timing decisions with their exact scope; do not repeatedly reopen an unchanged confirmed gate. A lead status named `active` is not necessarily a live sequence; inspect sequence lifecycle and documented semantics. 5. Verify committed records, actual draft membership, recipient-rendered copy, and unsent state rather than trust a COMPLETED label; the observed 24-step ceiling can stop work before finalization. Accept a run using `accept_scheduled_task_run` only after outputs pass review. Use `activate_scheduled_task` only when recurring execution is authorized and that task passed commissioning. Surface schedule activation and provider campaign activation differ; only the former belongs here. Read [references/recovery.md](references/recovery.md) on failures, uncertain writes, authentication, truncation, or count mismatches. Do not repeatedly run blocked tasks. If downstream has no eligible work, report the bottleneck rather than claiming full pipeline validation. ## Monitor progress For health checks, read [references/recovery.md](references/recovery.md). Report committed movement over a stated interval, queue age, and blocker counts alongside execution/schedule health. A task can be running successfully while useful work remains parked. Separate what the next run can advance from what needs a rule, data, capability, or user decision. A health-check request alone does not authorize edits or runs; continued monitoring needs a cadence and end condition, reusing any already supplied. ## Finish Return campaign/task links supplied by tools, schedules/timezone, paused/armed state, provider/copy strategy, verified counts by stage, and remaining blockers. Say whether anything ran and whether contacts entered inactive drafts. No live campaigns or prospect messages are part of this skill. Keep choices, IDs, verification, and unresolved recovery work in `setup-log.md`. Record new provider techniques in one campaign `surface-mcp-notes.md`, separating observed behavior from assumptions. Avoid raw credentials, personal contact dumps, and full execution logs in that notes file. ``` Installing manually? Keep all 5 files together. SKILL.md uses the reference files. The skill prepares inactive drafts for review. It does not launch campaigns or send emails. You can start with setup only, test the tasks, then enable recurring runs when you are ready. Task What It Does What It Saves **Prospect** Finds companies and contacts that match your ideal customer profile (ICP). Account and contact records with their sources. **Qualify** Checks account evidence against your campaign's qualification criteria. Decisions, supporting evidence, and research still in progress. **Draft Outreach** Uses qualified account evidence to personalize email sequences for eligible contacts. Complete email copy and, where supported, inactive provider drafts. Each task has one job with a result you can verify. Depending on your campaign, the skill can separate **Find Contacts** from Prospect, give **CRM Fit** checks their own task, or add **Reply Sync** when requested. Reply Sync starts with a dry run to check message coverage and CRM mappings before authorized writes. The tasks use the providers available in your Surface environment. A specific provider is not required by the skill. If your outreach connection cannot support the draft workflow, the agent can save personalized copy in Vault and explain what needs to happen manually. You will need: - An AI agent connected to Surface MCP. To install the ZIP for repeat use, your agent also needs local skill support. - A Surface environment with access to Vault, campaign tools, and scheduled tasks through MCP. Ask your agent to check that these tools are available. - Connected providers for the discovery and research you want to perform. Creating drafts in an external provider also requires a suitable outreach connection and a verified sender mailbox. - Your company website, target audience, and the criteria that make an account worth contacting. Connect your agent using [Surface MCP Setup](https://www.withsurface.com/docs/mcp-server/setup). The connection must allow the writes needed to create campaign files and tasks. **Copy instructions** is the quickest way to start. Paste the combined Markdown into an agent connected to Surface MCP, then provide your campaign details. All supporting instructions are included, so you do not need to install any files. **Download skill** is the reusable installation option. Extract the ZIP and place the **entire `surface-campaign-pipeline` folder** in your agent's skills directory. Use your agent's skill installation instructions to choose the location. Keep these files together: ``` surface-campaign-pipeline/ SKILL.md agents/ openai.yaml references/ vault-contract.md task-instructions.md recovery.md ``` `SKILL.md` is the entry point. The reference files contain the campaign structure, task instructions, and recovery procedures it uses during setup. Copying only `SKILL.md` leaves the installation incomplete. Copy this prompt into your agent and replace the bracketed values: ``` Use the Surface Campaign Pipeline instructions to set up an outbound email campaign. Company: [company name and website] Surface environment: [team and environment] Target accounts: [industry, geography, company size] Target contacts: [roles or personas] Qualification criteria: [evidence that makes an account a fit] Offer: [what we can help with] Exclude: [customers, competitors, domains, or other exclusions] Preferred providers: [names, or inspect my available Surface connections] Sender: [verified mailbox and sender first name, or leave unresolved] Timezone: [for example, America/Los_Angeles] Create the campaign files and tasks. Start with Prospect, Qualify, and Draft Outreach; split additional jobs only when needed. Use the skill's suggested starting limits and leave the tasks paused. Report missing connections or information. Do not run the tasks, enable recurring runs, or send any emails. ``` The agent checks your available connections and existing campaigns, builds the campaign files, and creates paused tasks. If it finds a matching campaign in the intended environment, it should resume that setup using the saved records. ### [Suggested Starting Settings](#suggested-starting-settings) Setting Starting Value Schedule Hourly: Prospect at :00, Qualify at :20, Draft Outreach at :40 Prospect Batch One qualified existing account, up to two contacts, then at most one new account; contact work can be a separate task Qualify Batch One account per run Draft Outreach Batch Up to two contacts per run, fewer when needed to finish and save drafts Initial Account Limit 30 accounts for initial testing Email Sequence Four steps, on business days 0, 3, 7, and 11 Start with small, complete batches. Increase throughput only after runs consistently save all expected records and verify provider outcomes. Each task uses committed, eligible records; scheduled offsets do not guarantee completion. Confirm any remaining discovery ceiling and its release condition before recurrence. Keep task instructions short, with account-specific history in Vault records. Open the campaign and task links returned by your agent. In `Campaigns/{Campaign}/`, review: - **The brief and ICP:** seller context, target accounts, personas, and qualification criteria. - **Exclusions:** the companies and contacts to leave out, and which checks your connections can support. - **The sequence:** every email step, its personalization sources, timing, and sender. - **The workflow and setup log:** task links, timezone, limits, paused state, and anything still blocked. A missing sender can hold up outreach while account discovery and research remain ready. Your agent should report readiness for each stage separately. When you are ready to use your connected providers, ask: ``` Test the [campaign name] pipeline with bounded runs of each configured task, following dependency order where committed eligible records are available. I authorize the provider calls for these tests, which may use credits. Verify saved results after each stage. Keep recurring schedules paused and all outreach in inactive drafts. Report completed work and blockers. ``` Research may take more than one run. Use small result pages, saved job IDs, and explicit retry dates. Propose useful records before more research, then finish the run and verify the writes actually committed. Check the results separately: accounts discovered, accounts qualified, contacts eligible for outreach, email copy saved, and provider drafts or memberships verified. Verify rendered copy and unsent state. Copy saved in Vault does not by itself mean a draft exists in your outreach provider. After reviewing successful tests, ask your agent to enable the stages that passed: ``` Enable recurring runs for the verified stages of [campaign name], using the agreed schedule, timezone, and limits. Leave blocked or unverified stages paused. Keep all outreach in inactive drafts and report which schedules are enabled. ``` Recurring tasks continue preparing prospects, research, and drafts within your campaign limits. Sending those drafts is a separate step outside this skill. Notifications stay in Vault unless you separately request Slack. Ask for a health check over a specific time window. Check current account files; an older checkpoint can miss new contacts. The skill reports committed progress, queue age, blockers, and next actions. A COMPLETED label can hide unfinished work when a worker reaches its step ceiling, so verify records and provider outcomes. A health check alone does not authorize edits, extra runs, or recurring monitoring. Ask your agent to inspect the latest run and saved campaign records before retrying. A missing connection, pending research result, unresolved sender, or unsupported personalization method can each hold up a stage. If a run fails after changing something in a provider, that change may still exist. The skill directs the agent to reconcile it before making another attempt, so a retry does not create duplicate research or drafts. --- # Run Your Week from Slack with SAM | Guides | Surface Docs URL: https://surface.thesurface.network/docs/guides/run-your-week-with-sam What to schedule, what to ask on the day, and what to stop opening the app for. [SAM](https://www.withsurface.com/docs/platform/sam/overview) works best on a fixed weekly rhythm rather than whenever you remember to try it. Schedule one post into `#marketing`, 08:30: > Last week vs the week before: leads, by source. Meetings booked. The one funnel step that moved most, and which pages drove it. Scheduled jobs are read-only, so the digest can never change anything. See [Scheduled posts](https://www.withsurface.com/docs/platform/sam/schedules). Ask the follow-up in the thread: > @SAM which landing pages lost the most qualified traffic last week, and where in the form did people stop? That is [conversion funnel](https://www.withsurface.com/docs/platform/traffic/conversion-funnel) plus [form analytics](https://www.withsurface.com/docs/platform/forms/analytics) in one question. > @SAM draft a LinkedIn post about the \[customer\] result, using brand/voice.md Drafts are exempt from SAM's brevity limit, so you get the full text back. If it comes back generic, add a rule to the [Vault](https://www.withsurface.com/docs/platform/vault/voice) instead of writing a longer prompt. Publishing waits behind an Approve card. > @SAM did our visibility change on the pricing prompts this week? Anything new in cited sources? Check [AI Visibility](https://www.withsurface.com/docs/platform/ai-visibility/overview) weekly, not daily. A single scan is one sample. > @SAM what's waiting on review? Approve, or send back with a reason. Feedback is stored on the draft and read on the next pass, so "the 37% is Nextiva's, not Galley's" beats an edit. [Review and publish](https://www.withsurface.com/docs/platform/campaign-agents/review-and-publish). Was Now Pulling weekly lead numbers The Monday digest "Did that campaign do anything?" One question in the thread Checking where a form loses people One question, names the field First-draft social and email copy Ask, then edit Chasing who owes a review Friday's queue check Building a form from scratch, changing routing rules, and anything else that needs the whole object on screen. SAM answers up to 200 questions per workspace per rolling 24 hours, and each one has a spend ceiling. A weekly cadence like this uses a small fraction of that, so ask follow-ups freely. The full budget table is in [Limits and guardrails](https://www.withsurface.com/docs/platform/sam/limits). [Prompt library](https://www.withsurface.com/docs/platform/sam/prompts) · [Limits and guardrails](https://www.withsurface.com/docs/platform/sam/limits) · [Troubleshooting](https://www.withsurface.com/docs/platform/sam/troubleshooting) Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Send Data to Airtable | Guides | Surface Docs URL: https://surface.thesurface.network/docs/guides/send-data-to-airtable Send Surface form submissions to Airtable with a webhook Connect your Surface form to Airtable with a webhook, so every submission creates a new record in your base. You need: - A Surface Forms account with a form created - An Airtable account and base set up - Admin access to both platforms 1. In Surface Forms, create your form if you haven't already 2. In Airtable, create a new base or use an existing one 3. Set up your table with columns that match the data you want to receive from your form Make sure your Airtable column names are clearly defined, as you'll need to reference them later in the webhook payload. 1. In your Airtable base, click on the **Automations** tab 2. Click **Create Automation** 3. Select **When webhook received** as your trigger 4. Add a second action step by clicking the **+** button 5. Choose **Create Record** as your action 6. Configure the Create Record action: - Select your target table - Map the incoming webhook fields to your table columns 7. Save the automation and copy the webhook URL You can also use the [Airtable API](https://airtable.com/developers/web/api) to create records programmatically. Keep your webhook URL secure - anyone with this URL can send data to your Airtable base. 1. Open the Surface Forms Workflow Builder 2. Create a new workflow: ### [Workflow Trigger Options](#workflow-trigger-options) You can configure when the webhook sends data: - On form submission - When visitor drops off - While form is in progress ### [Configure the Webhook Action](#configure-the-webhook-action) 1. Click the **+** button to add a new node 2. Select **HTTP Request** from the actions menu 3. In the sidebar configuration: - Set **Request URL** to your Airtable webhook URL - Change **HTTP Method** to `POST` - Under **Body**, add your JSON mapping. Where the object key is the Airtable column name and the value is the form variable. Use the `@` symbol in the workflow builder to access form variables. Press `@` and start typing to see available fields from your form. 1. Submit a test entry through your Surface Form 2. Check your Airtable base for the new record 3. Verify that all fields are mapping correctly If you don't see data appearing in Airtable: - Check your webhook URL is correct - Verify your JSON payload structure matches your Airtable columns - Review the workflow logs in Surface Forms - Email [support@withsurface.com](mailto:support@withsurface.com) - Book a [consultation](mailto:founders@withsurface.com) with our team Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Send Data to Clay | Guides | Surface Docs URL: https://surface.thesurface.network/docs/guides/send-data-to-clay Send Surface form submissions to Clay with a webhook and the HTTP Request action 1. In Clay, create a new table 2. Add **Webhook** as the data source for the table 1. In the Webhook source configuration, find the **Webhook URL** 2. Copy the Webhook URL. You'll paste this into Surface in a later step 3. Set `Send response as` to `JSON` so Clay expects and parses JSON payloads 1. Open the **Workflow Builder** in the Surface Platform for your form 2. Add a new action to your workflow 3. Select **HTTP Request** from the available actions Configure the HTTP Request action: 1. **Request URL**: Paste the Webhook URL you copied from Clay 2. **HTTP Method**: Set to **POST** 3. **Body**: Add a JSON object where each key is the field name Clay expects and each value is the form data. Use the `@` symbol in the workflow builder to insert form variables (e.g. `@email`, `@name`). Press `@` in the workflow builder and start typing to see available form fields you can use in the JSON body. 1. Save your Surface workflow 2. Submit a test response through your Surface Form 3. In Clay, check your webhook table. You should see the new row with the data sent from Surface If data isn't appearing in Clay: - Confirm the Webhook URL in the HTTP Request action matches the URL from Clay exactly - Ensure `Send response as` is set to `JSON` in Clay and your request body is valid JSON - Check that the JSON keys in the body match the columns or fields Clay expects - Review workflow logs in Surface to see if the request was sent and whether Clay returned any errors Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Send Data to HubSpot | Guides | Surface Docs URL: https://surface.thesurface.network/docs/guides/send-data-to-hubspot Send Surface form submissions to HubSpot with the built-in HubSpot action in the Workflow Builder Send Surface form submissions to **HubSpot** with the built-in HubSpot action: create or update contacts, companies, deals, and more. You need: - A **Surface** account - A **HubSpot** account with the right permissions - Admin access to connect HubSpot to Surface 1. Open the **Workflow Builder**. 2. Click the **+** button to add a new action node. 3. From the integrations list, choose **HubSpot**. The HubSpot integration supports multiple actions: - **Create Contact** → Add a new contact in HubSpot - **Create or Update Contact** → Add a new contact or update existing ones - **Create Company** → Create a company record - **Create Form Response** → Push a form submission directly into HubSpot - **Create Deal** → Add a new deal in HubSpot - **Get Owner** → Fetch a HubSpot owner by email - **HubSpot AI Agent** → Use AI to manage contacts and deals automatically 1. After selecting an action, configure the settings in the right-hand panel. 2. Choose the HubSpot object (e.g., Form, Contact, Company, Deal). 3. Map your Surface Form fields to HubSpot properties: - Example: email → Email from Form Submission or Lead - Example: firstName → First Name from Form Submission or Lead Instead of configuring individual actions one by one (create a contact, then a deal), give the AI Agent **instructions in plain English** and it manages contacts, companies, and deals in HubSpot for you. ### [Write Instructions for the Agent](#write-instructions-for-the-agent) In the configuration panel, describe what you want in the **Instructions** text area. For example: ``` Check HubSpot to see if the company exists. If the company doesn't exist, create a new company. If a contact with the new lead's email doesn't exist, create one. Associate the contact with the company. If there are no open deals in the "Sales" pipeline, create a new deal and assign it to the company owner. ``` You can be as detailed as you need - the AI Agent interprets and executes based on HubSpot's API. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Send Data to Surface Using Webhooks | Guides | Surface Docs URL: https://surface.thesurface.network/docs/guides/send-data-to-surface Send data into Surface with a webhook Send data into Surface with a webhook. This example uses Framer Forms. 1. Log in to your Surface account 2. Navigate to Leads Hub from the side navigation bar 3. Click on the "Webhooks" tab ### [Configure Fields](#configure-fields) Click on `+ Add fields` and select the fields you want to receive from webhooks from the dropdown. ### [Copy Webhook URL](#copy-webhook-url) Copy the webhook URL provided in the snippets section (available for CURL, NodeJS, and Python). 1. Open your Framer project 2. Add a Form Component from the Component Selector ### [Configure Form Component](#configure-form-component) Select the Form Component and go to the right-side config sidebar, under the "Form" section: - Select "Webhook" as the Send To option - Paste the webhook URL you copied from Surface ### [Configure Form Fields](#configure-form-fields) 1. Select each input field in your form 2. In the config sidebar for each field: - Set the appropriate Type (text, email, phone, etc.) - The `Name` field should match the fields you configured in Surface 1. Publish your website 2. Test the form by submitting sample data 3. Check your Surface Leads Hub to verify that: - The data is received correctly - The lead information is properly enriched If you're not seeing the data in Surface Leads Hub: 1. Verify the webhook URL is correct 2. Check that the field names in your form match the configured fields in Surface 3. Check the network tab in your browser's developer tools for any errors when submitting the form Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Track Your AI Visibility for a Launch | Guides | Surface Docs URL: https://surface.thesurface.network/docs/guides/track-ai-visibility Set a baseline before you ship, publish against the gaps, and measure whether it moved. This measures whether an answer engine names you when a buyer asks about the problem you launched into. Take the baseline before you ship, or you will not know afterwards whether the launch moved anything. Write prompts the way a buyer would type them, covering the ground the launch is aimed at. The kinds below are a checklist for your own coverage, not a feature in the product: Kind of question Write **Category** "What tools do X?" Tests whether you are in the consideration set at all. **Problem** "How do I stop Y happening?" Catches buyers who do not know the category. **Comparison** "A vs B", "alternatives to C". Highest intent. **Evaluation** "How long does X take to set up?" Where wrong answers cost deals. **Pricing** "Which X tools do not charge per seat?" Often clearly yours. Take the phrasing from sales calls. One prompt copied word for word from a first call is worth more than five you invented: [tracked prompts](https://www.withsurface.com/docs/platform/ai-visibility/tracked-prompts). ``` trigger_scan { "profileId": "..." } ``` Record three numbers before anything ships: visibility score, content coverage, and the competitor at the top. The prompts where a competitor is cited and you are not are your publishing plan. Rank by decision impact, not distance behind: [acting on gaps](https://www.withsurface.com/docs/platform/ai-visibility/acting-on-gaps). Then pull the [cited sources](https://www.withsurface.com/docs/platform/ai-visibility/cited-sources) for the ones you picked: what the models have already absorbed about the category, and which directories or review sites you are absent from. That second list is the part you can edit yourself, so start there. Brief the [content agent](https://www.withsurface.com/docs/platform/campaign-agents/content-agent) with three things: - the exact prompt text, - the competitors currently cited for it, - the domains those answers pulled from. Write the claim plainly and near the top. Answer engines quote sentences, and a buried one does not get quoted. Pick the re-scan dates before you publish, and use more than one: models do not all move at the same time, and a single scan is a single sample. Compare each against the step 2 baseline, per model. We do not publish an absorption timeline, so do not promise your team one. Measure it on your own prompt set over a few scans. Read the trend, not one scan: [reading the score](https://www.withsurface.com/docs/platform/ai-visibility/reading-the-score). Visibility is a leading indicator. Pair it with the AI traffic breakdown in [traffic analytics](https://www.withsurface.com/docs/platform/traffic/analytics) and the meetings those landing pages produced in the [conversion funnel](https://www.withsurface.com/docs/platform/traffic/conversion-funnel). [SAM](https://www.withsurface.com/docs/platform/sam/schedules) can keep the loop visible between launches: ask it weekly whether you are showing up in AI answers for the prompts the launch targeted. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Claude OAuth Setup | MCP | Surface Docs URL: https://surface.thesurface.network/docs/mcp-server/claude-oauth-setup Connect Surface to Claude via OAuth using the Connectors feature. No API key required Claude connects to MCP servers over OAuth through its **Connectors** feature. You sign in with your Surface account, so there are no API keys to manage. Configure the connector In the modal that appears, fill in the following: - **Name:** `Surface` - **Remote MCP server URL:** `https://app.withsurface.com/mcp` Then click **Add**. Connect your account After adding the connector, click the **Connect** button to authenticate with your Surface account via OAuth. Choose your environment and complete the connection. Surface now appears as a connector in Claude. Start using Surface in Claude Turn the Surface connector on in any Claude chat via the **+** menu and **Connectors**. A connector added with the bare URL above loads the default 57 of 132 tools: the forms and vault bundles plus the hubspot family, which covers forms, responses, AI scores, the Vault, and reads of connected HubSpot records. To load a different set, add `?tools=` to the connector URL: see [Tool Bundles](https://www.withsurface.com/docs/mcp-server/tool-bundles). The OAuth connection is tied to your Surface account and environment, so there is no API key to rotate. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Docs MCP Server | MCP | Surface Docs URL: https://surface.thesurface.network/docs/mcp-server/docs-mcp Point an agent at these docs so it can search and read them directly These docs are themselves an MCP server. Point any MCP client at `https://docs.withsurface.com/mcp` and it can search every page and read it as Markdown, instead of scraping HTML or guessing. No API key: the docs are public. This is not the Surface MCP server. `docs.withsurface.com/mcp` is the documentation, read only and unauthenticated. `app.withsurface.com/mcp` is your workspace: forms, leads, responses and the Vault. See [Overview](https://www.withsurface.com/docs/mcp-server/overview) for that one. ``` claude mcp add --transport http surface-docs https://docs.withsurface.com/mcp ``` Tool What it does `search_surface_docs` Searches every page and returns the best matching ones, each with its path and a few matching snippets. Takes `query` and an optional `limit` (pages, default 8). `list_surface_docs` Lists every page as path, title and description, in sidebar order, grouped by section. Takes an optional `section`, for example `platform` or `/build/webhooks`. `get_surface_doc` Returns one page as Markdown. Takes `path`, either a path or a full URL, with or without a `.md` suffix or an anchor. The usual loop is one search, then a fetch of the two or three pages worth reading in full. Reach for `list_surface_docs` when you want to see the shape of a section rather than hunt for a phrase in it. The server is public, unauthenticated and CORS enabled, so a browser based client can call it directly. Every page is also plain Markdown over HTTP, which is the better fit for a script or a crawler: URL What `/llms.txt` The whole site as a linked index `/llms-full.txt` Every page's Markdown in one file `.md` That page as Markdown, for example [/quickstart.md](https://www.withsurface.com/docs/quickstart.md) Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # MCP Server | MCP | Surface Docs URL: https://surface.thesurface.network/docs/mcp-server/overview Connect any MCP-compatible AI assistant to Surface and build forms, query your funnel, and manage content with natural language Connect any [MCP-compatible](https://modelcontextprotocol.io/) AI assistant (Claude, Cursor, Windsurf, and more) to your Surface environment. Ask it about your forms, responses, leads, analytics, workflows, and AI scores in plain English. It can also build a whole form for you: steps and components, conditional routing, styling, the marketing pane, and publishing. The MCP server exposes **132 tools** in 17 tool families. A new connection loads the **forms and vault bundles plus the hubspot family** (57 tools) by default, so your assistant is not flooded with definitions it does not need. See [Tool Bundles](https://www.withsurface.com/docs/mcp-server/tool-bundles). ### Form Building Create forms from a plain-English spec: steps, questions, identity fields, schedulers, conditional routing. Edit any existing form component by component. ### Styling & Marketing Restyle forms with typed design tokens, per-component styles, or whole-form themes. Write and edit the marketing (story) pane: headlines, testimonials, logos, FAQs. ### Responses & Leads Search and filter responses, track completion status, browse qualified leads, get counts broken down by source or funnel stage. ### Analytics Completion rates, dropoff analysis, daily trends, landing page performance, UTM breakdowns, conversion funnels. ### AI Scoring Top-scored leads, score distributions, form comparisons, full-text response search. ### Workflows List workflow runs, filter by status, inspect per-step execution details and errors. ### AI Visibility AEO/GEO answer-engine visibility: reports, tracked prompts, per-model scores, cited sources, scans. ### Content & CMS Content analytics and AI traffic sources, the blog review pipeline, and a full headless CMS: content types, entries, and assets. ### SDK Form Authoring Create self-hosted [Forms SDK](https://www.withsurface.com/docs/build/forms-sdk/overview) forms, hand your coding agent the exact HTML binding contract, and statically validate the markup before it ships. ### Vault Browse, search and edit the environment's Markdown knowledge Vault: the positioning, proof and voice every agent reads before it writes. ### HubSpot Read connected HubSpot contacts, companies, deals, owners, activities and properties. Read-only, and in the default connection. ### Campaigns Query an outbound campaign's own Postgres tables: sends, replies and contacts across HeyReach, Instantly, Amplemarket and HubSpot. You need a **Surface API key** to connect, or [OAuth via Claude Connectors](https://www.withsurface.com/docs/mcp-server/claude-oauth-setup) with no key at all. The credential decides which environment the MCP server can reach, and every tool call is scoped to it. Create an API key Go to **Settings > API Keys** in your Surface dashboard and click **\+ Add API Key**. Copy the key straight away, it is not shown again. Connect your AI assistant Follow the [setup guide](https://www.withsurface.com/docs/mcp-server/setup) for your specific client (Claude Desktop, Cursor, Claude Code, etc.). Pick your tools (optional) The default connection loads the forms and vault bundles plus the hubspot family. Add `?tools=` to the server URL to load a different [bundle, family, or exact tool list](https://www.withsurface.com/docs/mcp-server/tool-bundles). Start asking Ask your AI assistant about your Surface data, or ask it to build something, in plain English. - "Create a new demo booking form with name, email, company fields and a scheduler step" - "Build a form in our brand colors that skips the demo step for companies under 10 people" - "Create an SDK form for our signup flow and give me the binding map for the page" - "Validate this rendered HTML against the signup form's record before I deploy it" - "Update the headline and testimonial on the demo form's marketing pane" - "Restyle my contact form to match our latest landing page, then publish it" - "Set the SEO title and GA4 id on my contact form" - "Show me the latest 10 responses for my Contact Us form" - "What's the completion rate for our pricing survey?" - "Which question has the highest dropoff in the onboarding form?" - "Give me the top 5 leads by AI score" - "Show me the conversion funnel for the last 7 days" - "How many leads came from each source in Q1?" - "Show me failed workflow runs from this week" - "List my completed AEO/GEO visibility reports and give me the PDF links" - "What pages are getting the most AI-driven traffic?" - "Paste this markdown as a new blog draft and assign it to the pricing cluster" - "Create a new blog post entry in the CMS and publish it" Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # API Setup | MCP | Surface Docs URL: https://surface.thesurface.network/docs/mcp-server/setup Connect the Surface MCP server to your AI assistant Every connection on this page needs your **Surface API key**, which scopes each tool call to one environment. Claude can connect without one, over OAuth: see [Claude OAuth Setup](https://www.withsurface.com/docs/mcp-server/claude-oauth-setup). Don't have an API key yet? Create one in **Settings > API Keys** in your [Surface dashboard](https://app.withsurface.com/). The key is only shown once, so save it securely. A new connection loads the default **forms and vault bundles plus the hubspot family** (57 of 132 tools). To load a different set, add `?tools=` to the server URL in any of the configs below, e.g. `https://app.withsurface.com/mcp?tools=all`. See [Tool Bundles](https://www.withsurface.com/docs/mcp-server/tool-bundles). Open MCP config In Claude Desktop, go to **Settings > Developer > Edit Config** to open your `claude_desktop_config.json`. Add the server Add the following to your config file, replacing `` with your actual API key: ``` { "mcpServers": { "surface-forms": { "url": "https://app.withsurface.com/mcp", "headers": { "Authorization": "Bearer " } } } } ``` Verify connection Restart Claude Desktop and look for the MCP icon in the chat input to confirm the server is connected. Run the following command in your terminal: ``` claude mcp add --transport http surface-forms https://app.withsurface.com/mcp \ --header "Authorization: Bearer " ``` Verify the server is configured: ``` claude mcp list ``` Open MCP config Go to **Windsurf Settings > Cascade > Model Context Protocol (MCP)** and click **Add Server** or edit your `~/.codeium/windsurf/mcp_config.json`. Add the server ``` { "mcpServers": { "surface-forms": { "serverUrl": "https://app.withsurface.com/mcp", "headers": { "Authorization": "Bearer " } } } } ``` Verify connection Refresh the MCP panel and check that `surface-forms` shows as connected. Any editor that supports [Streamable HTTP](https://modelcontextprotocol.io/docs/concepts/transports#streamable-http) can connect to the Surface MCP server. Use this configuration: ``` { "mcpServers": { "surface-forms": { "url": "https://app.withsurface.com/mcp", "headers": { "Authorization": "Bearer " } } } } ``` The Surface MCP server uses the **Streamable HTTP** transport, so there is no local process or Docker container to run. API keys are full-access, so the connection can create, edit, and publish. To hand a key to an agent that should only read, add `?readonly=1` to the URL: ``` https://app.withsurface.com/mcp?readonly=1 ``` This drops every write and admin tool from the connection, whatever the credential allows. It combines with `?tools=`; see [Tool Bundles](https://www.withsurface.com/docs/mcp-server/tool-bundles#read-only-connections). ›Server not connecting - Double-check that your API key is correct and hasn't been revoked. - Make sure the `Authorization` header uses the `Bearer` prefix. - Confirm your editor supports the Streamable HTTP transport. ›A tool I expected is missing - The default connection loads the forms and vault bundles. Add `?tools=all` (or the [bundle or family](https://www.withsurface.com/docs/mcp-server/tool-bundles) you need) to the server URL. - On a `?readonly=1` connection, write tools are deliberately absent. - A `?tools=` selection containing a typo falls back to every tool rather than silently narrowing the set. ›Tools not returning data - Your API key is scoped to a specific environment. Make sure the environment has forms, responses, or leads to query. - Form edits save a draft. Visitors only see them after `publish_form` promotes the draft to live. ›Rate limiting or timeouts - The MCP server runs on the same infrastructure as the Surface app. If a call times out, try again in a moment. - For large datasets, use pagination parameters (`page`, `limit`) to fetch data in smaller chunks. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Tool Bundles | MCP | Surface Docs URL: https://surface.thesurface.network/docs/mcp-server/tool-bundles How the 132 MCP tools are organized into bundles and families, what loads by default, and how to choose the tools your connection gets The Surface MCP server exposes 132 tools in 17 families. Loading every definition at once fills up an assistant's context, so a connection that asks for nothing specific gets the **forms and vault bundles plus the hubspot family**: the core form-building tools, responses, AI scores, the environment's knowledge Vault, and read access to connected HubSpot records. To load anything else, name a bundle, a tool family, or an exact list of tool names. A bundle is a set of tool families for one kind of session: Bundle Focus Families Tools `forms` Building forms and reading their results (in the default) forms, responses, scoring 41 `vault` The environment's Markdown knowledge Vault (in the default) vault 4 `campaigns` Reading an outbound campaign's tables, plus the Vault notes that explain them campaigns, vault 8 `content` CMS, blogs, content analytics, AI visibility cms, contentReview, contentAnalytics, aiVisibility 55 `insights` Responses, leads, analytics, scores, workflow runs analytics, scoring, leads, responses, workflows 20 `admin` Team, members, environments, feedback team, members, environments, feedback 4 `all` Everything all 17 families 132 An unconfigured connection combines the `forms` and `vault` bundles with the `hubspot` family: **57 tools**. The `hubspot` family joined that default in September 2026, so an older note saying 45 is out of date. Families are the smaller unit inside a bundle. You can select any of them directly: Family What it covers Tools `forms` Create, edit, style, route, and publish forms, including SDK form authoring (binding maps, HTML validation) 33 `responses` Read form submissions 2 `leads` Qualified leads and lead counts, lead import 3 `analytics` Form, funnel, landing page, and environment analytics 7 `workflows` Workflow run logs and per-step details 2 `scoring` AI lead scores, response search, form comparisons 6 `vault` The environment's Markdown knowledge Vault 4 `hubspot` Read connected HubSpot contacts, companies, deals, owners, and properties (in the default) 12 `campaigns` Read-only queries over an outbound campaign's Postgres tables 4 `cms` Headless CMS content types, entries, and assets 25 `contentReview` The blog review pipeline 12 `contentAnalytics` Content performance and AI traffic sources 7 `aiVisibility` AEO/GEO answer-engine visibility reports, prompts, and scans 11 `team` Team, subscription, and billing info 1 `members` Member invitations 1 `environments` Environment creation 1 `feedback` Product feedback to the Surface team 1 Selection goes on the `?tools=` query parameter of the one `/mcp` endpoint, so it works in every client that accepts a URL. The value is a comma-separated list of bundles, family names, and individual tool names: ``` https://app.withsurface.com/mcp default forms + vault bundles https://app.withsurface.com/mcp?tools=all full surface https://app.withsurface.com/mcp?tools=content one bundle https://app.withsurface.com/mcp?tools=responses,leads families https://app.withsurface.com/mcp?tools=forms,cms bundle + family https://app.withsurface.com/mcp?tools=list_forms,get_form_analytics individual tools ``` Three rules: - `forms` names the bundle, not the bare family, so `?tools=forms` also carries the responses and scoring tools. - A selection containing any unknown name falls back to everything, so a typo cannot produce a zero-tool server or silently narrow the set. - A known tool name your connection's credential excludes (a write tool on a read-only connection) is skipped, not treated as a typo. For clients that configure headers but not URLs, the `X-Surface-Tool-Families` header takes the same comma-separated list. `?tools=` wins when both are present: ``` { "headers": { "Authorization": "Bearer ", "X-Surface-Tool-Families": "content" } } ``` ### [Per-client Recipes](#per-client-recipes) ``` # The default forms + vault bundles need no selection claude mcp add --transport http surface-forms "https://app.withsurface.com/mcp" \ --header "Authorization: Bearer " # An insights session claude mcp add --transport http surface-insights "https://app.withsurface.com/mcp?tools=insights" \ --header "Authorization: Bearer " ``` Add `?readonly=1` to get a connection with no write or admin tools, whatever the credential can otherwise do. It combines with `?tools=`: ``` https://app.withsurface.com/mcp?readonly=1 reads of the default bundles https://app.withsurface.com/mcp?tools=all&readonly=1 every read tool https://app.withsurface.com/mcp?tools=content&readonly=1 content reads only ``` `?tools=all&readonly=1` is 79 of the 132 tools. API keys are full-access by design, so `?readonly=1` is how you hand a key to an agent that should only read. OAuth connections without the write scope get the same read-only set either way. CMS tools are included: a read-only connection cannot see `cms_delete_entry` or any other CMS write. The four `campaigns` tools are read-only by construction, so they survive `?readonly=1` intact. Whatever you select, every tool call stays scoped to the environment your API key or OAuth connection belongs to. Tool selection changes which definitions your assistant loads, never what it is allowed to touch. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Tool Reference | MCP | Surface Docs URL: https://surface.thesurface.network/docs/mcp-server/tools List all my forms with response counts`list_forms``page`, `limit`, `search`, `sortBy`, `sortOrder`, `dateRange`View a specific form's full configuration, questions, and styles`get_form``formId`, `source: "draft" | "live"` (default draft)Discover which components can go on a form step`list_component_types`NoneLearn a component type's exact params (JSON schema + example)`describe_component_type``type`See a form's step/component outline with edit addresses`get_form_structure``formId`, `source: "draft" | "live"`, `include: ["params"]` for full component contentGet a plain-English narrative of a form to relay to the user verbatim`summarize_form``formId`, `source: "draft" | "live"` (default draft)Get the full JSON Schema for the heavy authoring tools`get_tool_schema``tool`Add a component to a step of an existing form`add_component``formId`, `stepId`, `type`, `params`, `placement`Change a component's question, choices, or required flag`update_component``formId`, `stepId`, `row`, `column`, `params`, `required`Remove a component from a step`remove_component``formId`, `stepId`, `row`, `column`Move or reorder a component (same step or across steps)`move_component``formId`, `from`, `to`Add a step (page) to a form, optionally with components`add_step``formId`, `name`, `index`, `endStepKind`, `components`Rename a step, mark it as thank-you/disqualified, or set a redirect`update_step``formId`, `stepId`, `name`, `endStepKind`, `redirection`Remove a step from a form`remove_step``formId`, `stepId`Reorder a form's steps`move_step``formId`, `stepId`, `toIndex`Browse Surface form templates (styling sources for create\_form)`list_form_templates``kind`, `search`Find a Surface scheduler's id/booking link for a scheduler step`list_schedulers``includeInactive` (default: bookable only), `includeAvailability` for each scheduler's `nextAvailableDate`Restyle a form with typed tokens (page fill, panes, layout, progress bar)`update_form_styles``formId`, `tokens`Restyle one component type (button colors, input borders, option styles)`update_component_styles``formId`, `componentType`, `styles`Style the WHOLE form in one call (palette, template, or another form's look)`apply_form_theme``formId`, one of `palette` / `templateId` / `sourceFormId`Branch a step on an answer, URL param, or known-lead signal`set_step_routing``formId`, `stepId`, `routing` (null clears)Apply several edits atomically in ONE call (all-or-nothing)`batch_edit``formId`, `operations` (ordered `{ op, ...params }` array)Discover marketing (story) pane component types`list_marketing_component_types`NoneSet the marketing pane's headline, bullets, testimonial, logos, FAQ`update_marketing_pane``formId`, `stepId` (optional), `components`, `replace`Edit ONE marketing component's text in place, keeping its styling`update_marketing_component``formId`, `stepId` (optional), `index`, `params`, `expectedType`Update a form's SEO metadata, tracking ids, language, or partial tracking`update_form_settings``formId`, `settings`, `confirm`Check a form is valid: references, dead ends, reachability, routing graph`validate_form``formId` (draft/live) or `config`Get the SDK binding contract: question/step ids, answer shapes, `apiBaseUrl`, and a ready-to-paste init snippet`get_sdk_binding_map``formId`, `source: "draft" | "live"` (default draft)Statically check self-hosted SDK form HTML against the record (blockers break data capture, warnings degrade it)`validate_form_html``formId`, `html` (the rendered markup that ships), `containerSelector`, `source`Dry-run a visitor's answers and see the exact path and ending they reach`simulate_response``formId`, `answers: { questionId: value }`, `source: "draft" | "live"`Critique a form blueprint before building (gaps, open questions, readiness)`plan_form``request`, `styleIntent`, `steps` (`{ purpose, components?, routingIntent?, routing? }`); loop until `readyForCreate`; `sdk: true` when planning an SDK form (routing stays prose, styling questions are skipped)Create a new form with steps, routing, and a styling source`create_form``name`, `steps` (components as `{ type, params }`), optional styling source (`sourceFormId` / `templateId`, `designTokens` alone or as overrides on either; omit for the stock theme), `copyMarketing` (default true), `confirmed` (first call echoes the plan; true creates, as a draft unless `publishImmediately: true`); `sdk: true` creates a self-hosted SDK form record (no styling or routing params)Publish a form so visitors see the latest draft`publish_form``formId` --- # Vault over MCP | MCP | Surface Docs URL: https://surface.thesurface.network/docs/mcp-server/vault Read, search and edit the environment's knowledge Vault from any MCP client: four tools, one revision rule. The [Vault](https://www.withsurface.com/docs/platform/vault/overview) is part of the **default connection**, so these four tools work without any `?tools=` selection. Tool Does `browse_vault` List or search documents. `query`, `pathPrefix`, `cursor`, `limit`. `read_vault_documents` Read up to 10 documents. Returns the `revision` an edit will need. `create_vault` Build the environment's first Vault from a public website URL. `apply_vault_changes` Create, update, move or delete up to 20 documents, atomically. `apply_vault_changes` takes a `commitMessage` and a list of `operations`. Each operation is one of four shapes, keyed on `op`: ``` { "op": "create", "path": …, "title": …, "body": … } { "op": "update", "path": …, "title": …, "body": …, "revision": … } { "op": "move", "fromPath": …, "toPath": …, "revision": … } { "op": "delete", "path": …, "revision": … } ``` Field Rule `commitMessage` Required, 1 to 200 characters after trimming. `operations` 1 to 20 per call. A path may appear only once in a batch. `path` / `fromPath` / `toPath` 1 to 512 characters, a `.md` file **inside a folder**. New folders are created implicitly with their first document. `title` Required on create and update, 1 to 200 characters. `body` 100,000 characters per operation, 200,000 across the batch. `revision` Required on update, move and delete. Format `sha256:` plus 64 hex characters, exactly as `read_vault_documents` returned it. Two things that catch agents out: - **Surface composes the frontmatter.** That is why `title` is a separate field and not something you write into `body`. An agent that hand-writes a `---` block gets it twice. - **`Uploads/` and root-level files are read-only**, enforced in code rather than by prompt. `brand-book.md` is rejected; `brand/voice.md` is fine. Every update, move and delete must carry the `revision` returned by `read_vault_documents`. If the document changed since you read it, the whole call is rejected and nothing is partly applied. ``` read_vault_documents { "documents": [{ "path": "brand/voice.md" }] } → { "documents": [{ "path": "brand/voice.md", "title": "How We Write", "body": "…", "totalChars": 4120, "nextOffset": null, "revision": "sha256:9f2b…" }] } apply_vault_changes { "commitMessage": "Ban 'seamless'", "operations": [{ "op": "update", "path": "brand/voice.md", "title": "How We Write", "revision": "sha256:9f2b…", "body": "…\nseamless is banned.\n" }] } ``` Every failure comes back as a `code`. One of them is not a failure: Code What to do `MIRROR_STALE` **Nothing. The commit succeeded** and only the Postgres read mirror lagged. Retrying duplicates the work. `REVISION_CONFLICT` Someone else wrote first. Re-read the document and reapply on the new revision. `READ_ONLY_PATH` The path is root-level or under `Uploads/`. Put it in a folder. `INVALID_PATH` Not a `.md` file in a folder, or the same path appears twice in one batch. `DESTINATION_EXISTS` A create or move target is already there. Update it instead. `NOT_FOUND` No document at that path. `CONTENT_TOO_LARGE` The batch is over 200,000 characters of `body`. Split it. `VAULT_NOT_FOUND` The environment has no Vault yet. Call `create_vault`. `browse_vault` returns paths, titles and body snippets, enough to decide what is relevant. To keep context small: Scope by prefix `browse_vault { "pathPrefix": "competitors/" }` rather than listing everything. This is what [folder structure](https://www.withsurface.com/docs/platform/vault/structure) is for. Read the two or three that matter It takes up to 10, but 10 long documents is usually more context than the task needs. Use offset and maxChars on long documents Both are per-document, so a 6,000-word file can be read in the region you care about. `create_vault` takes one `websiteUrl` and builds the environment's first Vault from it: Surface crawls the public site and writes a first pass of what you do, who it is for and how you talk, for you to correct. See [getting docs in](https://www.withsurface.com/docs/platform/vault/getting-docs-in). `apply_vault_changes` is transactional across up to 20 operations, so a restructure is one call rather than twenty: ``` apply_vault_changes { "commitMessage": "Split the brand book", "operations": [ { "op": "move", "fromPath": "uploads-archive/brand-book.md", "toPath": "brand/voice.md", "revision": "sha256:1a04…" }, { "op": "create", "path": "brand/boilerplate.md", "title": "Boilerplate", "body": "…" }, { "op": "delete", "path": "old/legacy-tone.md", "revision": "sha256:9c77…" } ] } ``` Write a real `commitMessage`. A read-only connection (`?readonly=1`) exposes `browse_vault` and `read_vault_documents` only. That is how you let an agent read your positioning without editing it. [Vault overview](https://www.withsurface.com/docs/platform/vault/overview) · [Tool reference](https://www.withsurface.com/docs/mcp-server/tools#vault) · [Tool bundles](https://www.withsurface.com/docs/mcp-server/tool-bundles) Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # What You Can Build | MCP | Surface Docs URL: https://surface.thesurface.network/docs/mcp-server/what-you-can-build Six agents you can build on Surface MCP and the exact tool families each one needs. Surface ships its own [agents](https://www.withsurface.com/docs/platform/sam/overview). This page is the other half: what you can build yourself against the same workspace, with your own model and your own prompt. Each recipe below names the tool families it needs, so you can load only those. [Tool Bundles](https://www.withsurface.com/docs/mcp-server/tool-bundles) covers the `?tools=` syntax. ## [A Content Agent](#a-content-agent) Drafts against your own positioning, then takes the draft through review and publishing without a person moving text between tools. **Load** `?tools=content` plus the Vault: `?tools=content,vault` **Reaches** 25 CMS tools, 12 content review tools, 7 content analytics tools, 4 Vault tools **The move** Read [the Vault](https://www.withsurface.com/docs/platform/vault/overview) for voice and proof first, draft into the CMS, then use the review pipeline rather than publishing straight Reading the Vault before drafting is the whole difference between this and a generic writing agent. It is also what Surface's own writer does. Watches where you show up when a buyer asks an answer engine, and acts on the gaps. **Load** `?tools=aiVisibility,contentAnalytics` **Reaches** 11 AI visibility tools, 7 content analytics tools **The move** Read the tracked prompts and per-model scores, find who gets cited instead of you, then hand the gap to the content agent above Decides which leads are worth a human, and says why. **Load** `?tools=insights` **Reaches** 7 analytics, 6 AI scoring, 3 leads, 2 responses, 2 workflow tools **The move** Pull the scored leads, read the responses behind them, and check the workflow runs when a lead did not route as expected Builds and edits forms from a plain-English spec. **Load** Nothing. The 33 forms tools are in the default connection **Reaches** Steps, components, conditional routing, styling, the marketing pane, publishing **The move** `list_component_types` and `describe_component_type` return the exact schema at runtime, so your agent never guesses a payload Edits save a **draft**. Nothing a visitor sees changes until `publish_form`. Answers questions about a running outbound campaign from its own tables. **Load** `?tools=campaigns` (which carries the Vault too, deliberately) **Reaches** 4 read-only campaign tools, 4 Vault tools **The move** `list_campaign_tables` first, then `describe_campaign_table` before any query. Column names come from there; a guessed one fails The Vault rides along because a campaign's schema notes live at `Campaigns//schema.md` and are the other half of understanding its tables. ## [A CRM Context Agent](#a-crm-context-agent) Answers "what do we already know about this account" before a call. **Load** Nothing. The 12 HubSpot tools are in the default connection **Reaches** Companies, contacts, open deals, pipelines, owners, activities, properties **The move** `hubspot_list_properties` first to discover internal names, then look up by domain or email Read-only, and HubSpot only. There is no Salesforce, Attio or Zoho read surface over MCP today. If the tool family you need is not one of these, [tell us](mailto:founders@withsurface.com): a missing tool family is a thing we can add. [Tool Bundles →](https://www.withsurface.com/docs/mcp-server/tool-bundles) · [Full tool reference](https://www.withsurface.com/docs/mcp-server/tools) · [API setup](https://www.withsurface.com/docs/mcp-server/setup) Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # The Surface Platform | Platform | Surface Docs URL: https://surface.thesurface.network/docs/platform Every product Surface sells, grouped by what it does: agents, analytics, infrastructure, primitives. Five groups. **Agents** do work, **Analytics** tell you what happened, **Infrastructure** captures and books, **Primitives** are the shared record underneath, and **Connect** is how the rest of your stack joins in. [ ### SAM, the Surface Agentic Marketer **Beta.** Anything you would open the app to do, done from Slack. Numbers, drafts, publishing, research, on a schedule. ](https://www.withsurface.com/docs/platform/sam/overview)[ ### Lead Agents Research, enrichment, signal and scoring agents on every record as it lands. ](https://www.withsurface.com/docs/platform/lead-agents/overview)[ ### System Agents **New.** HubSpot, Salesforce and Attio kept current without a sync project. ](https://www.withsurface.com/docs/platform/system-agents/overview)[ ### Campaign Agents Research, a plan and drafts, delivered as artifacts for a human to review before anything publishes. ](https://www.withsurface.com/docs/platform/campaign-agents/overview)[ ### Build Your Own With Surface MCP Six agents you can build yourself on the same workspace and the tool families each one needs. ](https://www.withsurface.com/docs/mcp-server/what-you-can-build) Building rather than configuring? The Forms SDK, webhooks, the REST API and browser events live in [For Developers](https://www.withsurface.com/docs/build), and the MCP server has [its own tab](https://www.withsurface.com/docs/mcp-server/overview). Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Acting on Gaps | AI Visibility | Surface Docs URL: https://surface.thesurface.network/docs/platform/ai-visibility/acting-on-gaps AI Visibility Turning a visibility gap into campaign work, and measuring whether it moved. In the [loop](https://www.withsurface.com/docs/platform/ai-visibility/overview), a gap becomes a campaign, and the campaign gets re-measured on the same prompts. Rank by decision impact, not by how far behind you are. Take first Leave Comparison prompts where a competitor is cited and you are not Broad category prompts where six vendors are all named Pricing and evaluation prompts with a clear factual answer Prompts whose answers are opinion pieces Prompts with high coverage and low visibility: the page exists, the citation does not Prompts nobody in your pipeline has ever asked Anything a rep has heard a buyer say out loud Anything only a tool suggested Scan first, so you have a baseline `trigger_scan` before you publish. See [tracked prompts](https://www.withsurface.com/docs/platform/ai-visibility/tracked-prompts#scans). Brief with the prompt and the sources Hand the [content agent](https://www.withsurface.com/docs/platform/campaign-agents/content-agent) the prompt text, the competitors currently cited, and the [cited sources](https://www.withsurface.com/docs/platform/ai-visibility/cited-sources). Write the claim plainly and early Answer engines quote sentences. Put the claim near the top, and write it so it still makes sense when it is quoted on its own. Fix the sources you control in parallel Directory listings and review-site descriptions are yours to edit. Re-scan more than once Pick the re-scan dates before you publish, so you are not choosing them after seeing a number you like. **Uneven movement.** The models do not move together. That is what the [per-model breakdown](https://www.withsurface.com/docs/platform/ai-visibility/reading-the-score#per-model-breakdown) is for. **Occasional regressions.** Answers change on their own. Read trends, not points. How long a published page takes to show up in an answer engine is not something we can promise, and it is not published anywhere. Measure it on your own prompt set: baseline, publish, re-scan, and record what you saw. Your FDE can tell you what other teams have seen. Visibility is a leading indicator. Two things connect it to revenue: - **[Traffic Intelligence](https://www.withsurface.com/docs/platform/traffic/analytics)** attributes AI referrals by engine, so you can compare how ChatGPT visitors convert against organic ones. - **[The conversion funnel](https://www.withsurface.com/docs/platform/traffic/conversion-funnel)** carries them through to qualified leads and meetings. [SAM](https://www.withsurface.com/docs/platform/sam/overview) reaches the visibility data, so _"are we showing up in AI answers for \[prompt\]?"_ works from Slack, and [a schedule](https://www.withsurface.com/docs/platform/sam/schedules) can post it weekly. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Cited Sources | AI Visibility | Surface Docs URL: https://surface.thesurface.network/docs/platform/ai-visibility/cited-sources AI Visibility Which domains models pull from when they answer your buyers' questions, and what to do when you are not one of them. A scan records **which domains the models cited** when they answered. The list is a set of domains. Sorting them into groups is our habit, not a field in the product, but what you can do about a domain depends on which group it is in: Kind Example What to do **Your own domain** `withsurface.com/platform/...` Good. Note which pages, and write more like them. **Review and directory sites** G2, Capterra, category roundups Get listed, get reviews, get the description right. Usually the part you can edit yourself. **Editorial and community** Blogs, newsletters, Reddit, Hacker News Earned. Slow, and durable. **Competitor domains** A competitor's own comparison page They wrote the comparison and the model used it. Write yours. You wrote the page and the model still does not cite you. The cited sources usually explain it: the answer came from a roundup, a review site or a competitor's comparison page, none of which mention you. The page is fine. The model was reading other domains. List the sources for the profile `list_cited_sources` takes a `profileId` and returns the domains the models cited. Get the evidence per prompt and model `get_tracked_prompt_history` filters by prompt, category, model and date, so you can see which answer pulled from where, and when. Separate the fixable from the earned You can correct a directory listing this week. You cannot manufacture a community thread, and should not try. Fix the fixable, then re-scan Directory descriptions, category placement and review counts are the parts you control directly, so start there. ## [Reading It as a Content Brief](#reading-it-as-a-content-brief) The cited sources show what the model treated as a good answer. Two things transfer into a brief: - **The claims they make.** If three of four sources frame the category around per-seat pricing, address that head-on. - **The shape.** Comparison tables, "best for X" statements and plain claims near the top tend to survive being quoted. Long preambles do not. Hand the gap and the sources to the [content agent](https://www.withsurface.com/docs/platform/campaign-agents/content-agent) together. Cited sources are not a backlink report. They show what a model reached for on one question on one day. Domains move in and out, and absence from one prompt says nothing about another. [Acting on gaps →](https://www.withsurface.com/docs/platform/ai-visibility/acting-on-gaps) Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # AI Visibility | AI Visibility | Surface Docs URL: https://surface.thesurface.network/docs/platform/ai-visibility/overview AI Visibility Measure where your brand appears when buyers ask ChatGPT, Claude, Gemini and Perplexity, then turn the gaps into campaign work. AI Visibility measures whether your brand appears in the answer, per prompt and per model. Visibility score, competitor visibility and the per-model split, over one month. Track the questions buyers ask Prompts grouped by category and topic cluster, not keywords. → [Tracked prompts](https://www.withsurface.com/docs/platform/ai-visibility/tracked-prompts) Measure every answer A scan runs your tracked prompts and records who was mentioned and which sources the answer used. → [Reading the score](https://www.withsurface.com/docs/platform/ai-visibility/reading-the-score) Find the gaps Prompts where a competitor is cited and you are not, and the domains doing the citing. → [Cited sources](https://www.withsurface.com/docs/platform/ai-visibility/cited-sources) Act on them Turn the best gaps into campaign work, then re-measure the same prompts. → [Acting on gaps](https://www.withsurface.com/docs/platform/ai-visibility/acting-on-gaps) Everything hangs off a [profile](https://www.withsurface.com/docs/concepts#profile): a tracked site, its positioning, its competitor set, its topics, and the prompts tracked against it. Teams usually keep one, and add another only for a genuinely separate brand. The dashboard leads with visibility score, content coverage, total mentions, competitors tracked and prompts tested. Metric Question it answers **Visibility score** Across tracked prompts, how often are you in the answer? **Content coverage** How much of the tracked prompt set do you have material addressing? **Total mentions** How many times you were mentioned over the period **Competitor visibility** A visibility percentage for each competitor you track, side by side **Per-model breakdown** ChatGPT, Gemini, Perplexity and Claude, scored separately. In practice they disagree **Cited sources** Which domains the models cited when they answered AI Visibility tells you whether you appear in the answer. [Traffic Intelligence](https://www.withsurface.com/docs/platform/traffic/analytics) tells you who clicked through, tagged by engine rather than lumped into direct. Get a visibility report for your domain Your score, your competitors', and the gaps, before you talk to anyone. [Get a free report](https://www.withsurface.com/platform/ai-visibility) Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Reading the Score | AI Visibility | Surface Docs URL: https://surface.thesurface.network/docs/platform/ai-visibility/reading-the-score AI Visibility What visibility, coverage and the per-model breakdown mean, and which movements are worth reacting to. **How often you appear in the answer across your tracked prompts.** Compare it to your own previous number, and to your competitors' on the same prompt set. Nothing else. The score only means something next to the prompt set behind it. The same number on a tight set of buying prompts and on a set padded with generic category questions mean two different things. ## [Content Coverage](#content-coverage) **How much of the tracked prompt set you have material addressing.** Coverage is the ceiling on visibility: a model cannot cite a page you never wrote. Reading them together is a way of using the two numbers, not a view in the product: Coverage Visibility Reading High High Working. Keep the prompt set fresh. High Low You wrote it and it is not being cited. A [sources](https://www.withsurface.com/docs/platform/ai-visibility/cited-sources) problem, not a writing problem. Low Low Straightforward. Write the missing pages. Low High Rare. Someone else's page is carrying you: fragile, and worth fixing. ChatGPT, Gemini, Perplexity and Claude are scored separately, and in practice they disagree on the same prompt. The split tells you where to look: - **Strong on one model, weak on the rest.** The material exists somewhere the other models are not reading. Compare the cited sources for those prompts. - **Weak on one model everywhere.** Look at what that model cites instead, in [cited sources](https://www.withsurface.com/docs/platform/ai-visibility/cited-sources). - **Even and low.** Nothing you have published is addressing the question. A content problem, not a distribution one. `get_tracked_prompt_history` filters by model, so you can pull the per-model evidence behind any of these over time. A visibility percentage for each competitor you track, on the same prompts. Read where the gap concentrates: a competitor who owns comparison prompts is worth a campaign this quarter. Ignore single scans Models do not give the same answer every time. One scan is one sample. Read the trend Look at several scans in a row, not at one point. Attribute against publishes A rise after publishing pages that targeted those prompts is a story you can defend. Scan _before_ you publish. See [tracked prompts](https://www.withsurface.com/docs/platform/ai-visibility/tracked-prompts#scans). Reports for a period download as PDF or DOCX via `list_ai_visibility_reports` and `get_ai_visibility_report` over [MCP](https://www.withsurface.com/docs/mcp-server/tools#ai-visibility). For the underlying prompt, model and competitor evidence, use `get_tracked_prompt_history`. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Tracked Prompts | AI Visibility | Surface Docs URL: https://surface.thesurface.network/docs/platform/ai-visibility/tracked-prompts AI Visibility Choosing the questions worth measuring, organising them by intent, and adding your own. A tracked prompt is a question phrased the way a buyer would type it, measured across the models a scan covers. There is no search volume for prompts, so the set is a judgement call rather than a report. Track the questions that decide deals, not the ones that would generate impressions. The kinds of question below are a way of thinking about coverage, not a fixed taxonomy in the product. Categories on a profile are yours to define. Kind of question Example Why track it **Category** "What tools route inbound leads to the right rep?" Are you in the consideration set at all? **Problem** "How do I stop losing inbound leads to slow follow-up?" Buyers who do not yet know the category name **Comparison** "Chili Piper vs Surface" · "alternatives to Calendly for teams" Highest intent, and where the answer engine is doing the shortlisting **Evaluation** "How long does it take to implement lead routing?" Where a wrong answer costs you a deal quietly **Pricing** "Which lead routing tools do not charge per seat?" Often the prompt with the clearest right answer: yours Add prompts as sales hears new phrasing, and keep the set tight enough that you can still tell whether something you did moved it. Prompts carry a category and group into topic clusters. One overall number tells you little, while "strong on category, invisible on comparison" tells you what to write next week. `list_tracked_prompts` takes `category` and `topicClusterId`, so you can read the score by either. In the app, the Prompt Insights table lists prompts with the models they were tested against, a recommendation, and the current AEO leader for that prompt. The starting set comes from your positioning and competitor context. It will miss the prompts only your sales team knows, so add them. Pass the `categoryId` of a category already on the profile. ``` create_tracked_prompt { "profileId": "...", "text": "Which inbound scheduling tools do not charge per seat?", "categoryId": "..." } ``` Three sources worth mining: - **Sales calls.** The question a buyer asked on a first call is a tracked prompt, word for word. - **Support tickets.** Pre-sale questions that reached support are questions your site failed to answer. - **[Evidence board](https://www.withsurface.com/docs/platform/campaign-agents/evidence).** A claim you have already written down is one rephrasing away from a prompt a buyer types. A scan runs your tracked prompts against the models and records the result. `get_scan_status` reports running, queued or idle; `trigger_scan` starts one. Run one before you publish, so the after has a before to compare against. Model answers are not the same every time. Treat one scan as one sample, not as evidence that you dropped off a prompt. Read [the score](https://www.withsurface.com/docs/platform/ai-visibility/reading-the-score) before drawing a conclusion from one number. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Artifacts and the Asset Library | Campaign Agents | Surface Docs URL: https://surface.thesurface.network/docs/platform/campaign-agents/artifacts Campaign Agents Where the durable output of an agent run lives: drafts, the state each one is waiting in, and how images get in and stay reusable. An [artifact](https://www.withsurface.com/docs/concepts#artifact) is the lasting result of an agent run: something a human can open, review, edit and ship. A draft or an image is an artifact; a chat answer is not. Agent output, each row carrying the state it is waiting in. Four columns: **Artifact Name**, **Agent**, **Status**, **Updated**. - **Agent** names the agent that produced the row, so you can trace a piece back to the run behind it. - Under the title sits the finding that prompted it: the [competitor agent's](https://www.withsurface.com/docs/platform/campaign-agents/competitor-agent) tag (`pricing_change`, `positioning_shift`, `product_movement`, `customer_signal`, `mentions_you`) and the one-line reason it mattered. - **Status** is the review state: draft, in review, changes requested, approved, published. See [Review and publish](https://www.withsurface.com/docs/platform/campaign-agents/review-and-publish). Images and files live in the environment's asset library, not on the entry that first used them. An entry's image field points at an `assetId`, so the same image can be used by several entries without being uploaded again. Uploading takes three parts: ask for a presigned URL, `PUT` the bytes, then confirm. A large file never round-trips through the API. The first and last parts are [MCP tools](https://www.withsurface.com/docs/mcp-server/tools#cms): `cms_create_asset_upload_url` (`filename`, `mimeType`, `sizeBytes`) then `cms_confirm_asset_upload`. Set `alt` when you attach an image. It is far easier than going back for it later. From Slack: _"upload this to the CMS asset library with alt text and set it on the post"_. - **Filter over MCP.** `list_blogs` takes a `state` filter and a `search` term, which is the quickest way to answer "what is sitting in review". - **Cluster them.** `assign_blog_cluster` assigns or clears a strategy cluster on a piece, so "which campaign was this for" is recorded on the artifact rather than in someone's memory. - **Archive rather than delete.** `archive_blog` is reversible and also unarchives; `cms_delete_entry` takes the revision history with it. [Traffic analytics](https://www.withsurface.com/docs/platform/traffic/analytics) shows what the artifact produced once it was live. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Competitor Agent | Campaign Agents | Surface Docs URL: https://surface.thesurface.network/docs/platform/campaign-agents/competitor-agent Campaign Agents Watches the competitors you name, tells you what changed and why it matters to you, and files the research in your Vault. **Beta.** You set it up from the Connections panel in your [Vault](https://www.withsurface.com/docs/platform/vault/overview), which is also the context it uses to judge what actually matters when a rival moves. The Agents tab: what it is watching, what needs you, and the findings tagged MENTIONS YOU. Three tabs: **Agents**, **Inbox** and **Activity**. The header says how many competitors are being watched and when the next check runs, in UTC, next to four counters: tracked competitors, latest findings, needs you, scans complete. Under it, **Needs attention** is a list of finding cards. Each card names the competitor, dates the finding, and carries one line on why it matters to you. The ones aimed at you are tagged `MENTIONS YOU`. Each scan also saves documents into your Vault, so the research outlives the finding card. > `MENTIONS YOU` · **BILL** · 3 days ago > > **BILL comparison hub claims Ramp has no multi-entity support.** The claim is out of date, and it is the page ranking for "Ramp vs BILL", so sales is answering it live. Findings carry a tag, and the same tag appears again on the [artifact](https://www.withsurface.com/docs/platform/campaign-agents/artifacts) that answers one: Tag What it caught `pricing_change` Their pricing moved `positioning_shift` They started selling the category you named `product_movement` They shipped something you used to sell against `customer_signal` Demand to leave them is growing faster than their category `mentions_you` They named you: a comparison hub, an "alternative" landing page, or your brand terms in paid search **Write your honest take, including where they win.** The agent weighs a change against your Vault, so a competitor document of pure weaknesses gives it nothing to weigh against. **Name the claims you make about them.** If your pages say "they charge per seat", write that down as a claim you make, so a change to their pricing has something of yours to land against. **Limit the set.** Track the four competitors you lose to, not the twelve you mention in a deck. Start from the [AI Visibility competitor set](https://www.withsurface.com/docs/platform/ai-visibility/reading-the-score): answer engines already put those next to you. Update the Vault Correct your document on that competitor first. Everything downstream reads it, and the next scan judges against it. Take the draft it produced Work this agent generates shows up on the [Artifacts](https://www.withsurface.com/docs/platform/campaign-agents/artifacts) screen, with the agent name and the finding tag on the row, so you can see which finding a piece is answering. Review it like any other draft Same states, same reviewers, same publish step. See [Review and publish](https://www.withsurface.com/docs/platform/campaign-agents/review-and-publish). [SAM](https://www.withsurface.com/docs/platform/sam/schedules) has no tool for reading this agent's findings, but it can run the research half on a timer: _"every Monday, what has \[competitor\] shipped in the last week?"_ posts into a channel. See the [prompt library](https://www.withsurface.com/docs/platform/sam/prompts). Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # The Content Agent | Campaign Agents | Surface Docs URL: https://surface.thesurface.network/docs/platform/campaign-agents/content-agent Campaign Agents Drafts the campaign work from your Vault and the claim you picked, and stops at review. The writer inside [Campaign Agents](https://www.withsurface.com/docs/platform/campaign-agents/overview). It takes the claim you picked in [evidence](https://www.withsurface.com/docs/platform/campaign-agents/evidence), reads your [Vault](https://www.withsurface.com/docs/platform/vault/overview), and produces something a human can review. Drafts land in the [review pipeline](https://www.withsurface.com/docs/platform/campaign-agents/review-and-publish) as blog-shaped pieces, or in the CMS as entries. The work on the [Artifacts](https://www.withsurface.com/docs/platform/campaign-agents/artifacts) screen is article-shaped: Kind The claim behind it **Comparison and "alternative" pages** The claim is a buying criterion: "routing reliability, not price" **Category and positioning pieces** The claim is how the category should be framed **Buyer guides** The claim is a question nobody has answered publicly **Blog posts** The claim is an argument worth making at length **Evidence updates** An existing page is right but under-proved For email, the sequence itself lives in your ESP and is driven from a Surface workflow. See the [email sequence guides](https://www.withsurface.com/docs/guides/email-sequences-hubspot/overview). Agree the claim first Which claim it is answering, who it is aimed at, the format, and what would count as success. It reads the Vault Your positioning, your voice and your proof are whatever the Vault says they are. See [folders and structure](https://www.withsurface.com/docs/platform/vault/structure). It drafts A full piece, structured, aimed at the claim rather than the topic. It stops Drafts land in [review](https://www.withsurface.com/docs/platform/campaign-agents/review-and-publish). Nothing publishes without a person. **Give it the claim, not the topic.** "Write about lead routing" produces a survey. "Write the comparison page for buyers who care about routing reliability over price, using the closed-won evidence behind that claim" produces an argument. **Say what success looks like.** A page built to rank in an answer engine is structured differently from one built to convert paid traffic. **Fix the Vault, not the draft.** The same problem in a third draft is a missing rule. See [correcting an agent](https://www.withsurface.com/docs/platform/vault/voice#correcting-an-agent). Assume it will write a claim your Vault asserts but your product does not do. Nothing in the pipeline checks a claim against the product, which is what the review step is for. Treat Vault accuracy as a publishing prerequisite: see [Vault and agents](https://www.withsurface.com/docs/platform/vault/agents). - **Search** wants the page to be about one thing, structured, and linked from places that already rank. - **Answer engines** want the claim stated plainly, near the top, in a form that survives being quoted out of context. Track the prompt the piece answers in [AI Visibility](https://www.withsurface.com/docs/platform/ai-visibility/tracked-prompts) before you publish. The whole pipeline is on [MCP](https://www.withsurface.com/docs/mcp-server/tools#content-review), loaded with `?tools=content`: `paste_blog` to create from Markdown, `get_blog` and `get_blog_versions` to read, `request_blog_changes` and `quick_approve_blog` for review, `toggle_blog_publish` to ship. [Review and publish →](https://www.withsurface.com/docs/platform/campaign-agents/review-and-publish) Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Evidence | Campaign Agents | Surface Docs URL: https://surface.thesurface.network/docs/platform/campaign-agents/evidence Campaign Agents The cited buyer claims a campaign gets planned from: the four sources they are drawn from, and how to read a claim without over-reading it. Evidence is the input to [Campaign Agents](https://www.withsurface.com/docs/platform/campaign-agents/overview). Before anything is written, you pick the _claim_: something your buyers actually said, with the source it came from. **This is a planning step, not a screen you will find in the app today.** There is no Evidence tab in the product. What follows is how we describe the input to a campaign on [withsurface.com/platform/content-campaigns](https://www.withsurface.com/platform/content-campaigns), and how the planning gets done with you. Ask your FDE which of these sources is actually wired up for your environment before you plan around one. Source What it is good for **Closed-won calls** The reason someone bought, in their words. The highest-signal source, and usually the most surprising. **CRM opportunities** Deal notes and stage history. Where deals stall, and what unblocked them. **ICP accounts** The [segment](https://www.withsurface.com/docs/concepts#segment) you actually sell to, so a claim can be checked against the right population. **Support tickets** Friction after the sale, which is nearly always friction before it too. The [Vault](https://www.withsurface.com/docs/platform/vault/overview)'s Connections panel is where sources get attached, and it is the honest place to check what is reading. Competitor Monitoring and Content Analytics are live; Surface email, Surface forms, HubSpot, Gong and LinkedIn Ads are listed there as coming soon. > **Buyers compare us on routing reliability, not price.** Strong · Closed-won calls · 18 citations Three parts: - **The claim**, phrased as something a buyer believes rather than something you sell. - **The source** it came from, so you can weigh it against the population it describes. - **Citations**: how many underlying passages sit behind it, so the claim is traceable back to the calls, notes or tickets rather than asserted. Claims are labelled `Strong` or `Medium`. Treat that as a rough sort order, not a score with a published formula behind it. **The strongest claim is rarely the useful one.** It is already on your homepage. The opportunity is the middling claim you did not know about: _"champions need a one-pager to sell this internally"_ is a page nobody wrote. **Watch for claims that contradict your positioning.** If closed-won calls say buyers compare on reliability and your site compares on price, that is the finding. **Mind the population.** A claim drawn only from support tickets describes customers, not buyers. Cross-check it against opportunities. **A claim is a hypothesis, not a fact.** One rep's note-writing habit can manufacture a pattern. If a claim does not survive you reading two of its citations, do not build a campaign on it. Claims about a gap you fixed six months ago keep coming back until the sources stop containing them. Two moments usually earn a fresh pass: after a closed-won review, and after any positioning change. If the same mis-reading keeps coming back (an adjacent product treated as a competitor, or a feature request treated as an objection), fix it in the [Vault](https://www.withsurface.com/docs/platform/vault/overview) rather than in the claim. [Content agent →](https://www.withsurface.com/docs/platform/campaign-agents/content-agent) Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Campaign Agents | Campaign Agents | Surface Docs URL: https://surface.thesurface.network/docs/platform/campaign-agents/overview Campaign Agents Turn buyer evidence into campaigns that convert: one agent system that gathers proof, plans the work, drafts it, and measures what it produced. A campaign in Surface is **an audience, a message, a piece of work, and a measured outcome**. Campaign Agents carry it from evidence to published. Evidence Read closed-won calls, CRM opportunities, ICP accounts and support tickets. Extract the claims buyers actually make, with the source behind each one. → [Evidence](https://www.withsurface.com/docs/platform/campaign-agents/evidence) Plan Pick the claims worth a campaign, the audience to aim them at, and the outcome that will count as success. Draft Write it against your [Vault](https://www.withsurface.com/docs/platform/vault/overview), so it uses your positioning, your proof and your voice. → [Content agent](https://www.withsurface.com/docs/platform/campaign-agents/content-agent) Review Every draft stops for a human. Approve, request changes, or edit and re-review. → [Review and publish](https://www.withsurface.com/docs/platform/campaign-agents/review-and-publish) Measure Traffic, AI traffic sources, leads and meetings attach back to the page that produced them. → [Traffic analytics](https://www.withsurface.com/docs/platform/traffic/analytics) The last three steps are things you drive in the app: the [Competitor Agent](https://www.withsurface.com/docs/platform/campaign-agents/competitor-agent) and [Artifacts](https://www.withsurface.com/docs/platform/campaign-agents/artifacts) screens, and Traffic Analytics. The first two are planning, done with your FDE rather than on a screen. See [Evidence](https://www.withsurface.com/docs/platform/campaign-agents/evidence). Agent What it does **[Evidence](https://www.withsurface.com/docs/platform/campaign-agents/evidence)** Turns closed-won calls, opportunities, ICP accounts and tickets into cited claims worth a campaign **[Content](https://www.withsurface.com/docs/platform/campaign-agents/content-agent)** Drafts the piece from the Vault and the claim you picked **[Competitor](https://www.withsurface.com/docs/platform/campaign-agents/competitor-agent)** Watches the competitors you name and tells you what changed and why it matters **Content is one agent inside Campaign Agents, not a separate product.** If you are looking for "Content & SEO Agents" from the website's Product menu, it is [the content agent](https://www.withsurface.com/docs/platform/campaign-agents/content-agent) on this page. - **It does not publish on its own.** Everything material parks behind a [review step](https://www.withsurface.com/docs/platform/campaign-agents/review-and-publish). - **It does not check its own proof.** A claim carries the source it came from so a reviewer can go back to it, but nothing in the pipeline verifies that a number in a draft is true. - **It is not a scheduler.** Publishing, scheduling and the asset library live in the CMS; the agent writes into it. Run a campaign against your own evidence Bring one closed-won call and your CRM. We will work through the claims in them with you and pick the three worth a campaign. [Book a demo](https://www.withsurface.com/book-a-demo) Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Review and Publish | Campaign Agents | Surface Docs URL: https://surface.thesurface.network/docs/platform/campaign-agents/review-and-publish Campaign Agents The gate between an agent writing something and the world seeing it: states, reviewers, versions, and publishing. Nothing an agent writes goes live on its own. Every draft moves through a review pipeline with explicit states, named reviewers and full version history. State What it means What moves it on **Draft** Being written or edited. Agents and humans both write here. Submitting it for review **In review** Submitted, waiting on a decision. A [reviewer](#reviewers) approving or requesting changes **Changes requested** Sent back with written feedback attached. Back to draft **Approved** Cleared to publish. Not yet public. `toggle_blog_publish` **Published** Live. `toggle_blog_publish` again, to unpublish **Archived** Soft-deleted. `archive_blog` also unarchives. n/a The first five are the statuses on the [Artifacts](https://www.withsurface.com/docs/platform/campaign-agents/artifacts) screen. **`request_blog_changes` only accepts something already in review**, and **archive is reversible**. `list_blogs` takes a `state` filter and a `search` term, so "what is sitting in review" is one call. Reviewers are named per environment, so review goes to a known list rather than to whoever noticed first. `list_reviewers` over [MCP](https://www.withsurface.com/docs/mcp-server/tools#content-review) returns the current set. Every draft keeps its version history and its rendered Markdown: - **Comparing an agent revision to yours.** `get_blog_versions` lists them; `get_blog_version_content` returns the body of any one. - **Getting an earlier draft back after a bad approve.** The older version's Markdown is still readable. Resist the urge to rewrite: an edit fixes one draft, and a [Vault](https://www.withsurface.com/docs/platform/vault/voice#correcting-an-agent) rule fixes every future one. Check the claim, not the prose Is what it says true, and is it the claim the campaign was for? Prose problems are cheap to fix; a wrong claim is a retraction. Check every number has a source Named customer or a figure you can point at. If neither, cut it. Request changes with the reason "Opened generically, and the 37% is Nextiva's not Galley's." `request_blog_changes` takes that `feedback` and stores it on the draft, so the next person to open it sees why it came back. Approved is not published, so a batch can clear review on Thursday and go live on Monday. Content you host with us publishes into the Surface CMS. If you publish the page yourself, `get_blog_version_content` hands you the approved Markdown. For CMS entries, `cms_schedule_entry` sets a publish time and `cms_unschedule_entry` cancels it, so a piece approved today can go live at 09:00 on Tuesday. See the [CMS tools](https://www.withsurface.com/docs/mcp-server/tools#cms). From Slack: _"what's sitting in draft right now?"_ is a read. _"@SAM approve the Nextiva post"_ is a write, so it parks behind an Approve card before anything moves. Either way it counts against the workspace's 200 questions per rolling 24 hours. See [Limits and guardrails](https://www.withsurface.com/docs/platform/sam/limits). [Artifacts and the asset library →](https://www.withsurface.com/docs/platform/campaign-agents/artifacts) Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Form Analytics | Dynamic Lead Forms | Surface Docs URL: https://surface.thesurface.network/docs/platform/forms/analytics Dynamic Lead Forms Track views, starts, completions, drop-offs, and conversion rates to optimize form performance The Form Analytics page shows how visitors engage with your form: views, starts, completions, drop-offs and conversion rates. At the top of the page, a snapshot of your form's performance: - **Completed** → Number of users who fully submitted the form. - **Partial** → Number of users who started but did not finish. - **Total** → Total number of responses (Completed + Partial). - **Views** → Number of times the form was viewed. - **Start to Completion Rate** → Percentage of users who started the form and reached submission. This chart shows the **percentage of users who progressed through each stage** of your form funnel: - **Viewed** → Visitors who loaded the form. - **Started** → Visitors who began filling it out. - **Submitted** → Visitors who successfully completed submission. The **Drop-off Analytics** table breaks the funnel down step by step: - **Step Views** → Number of visitors who viewed that step. - **Step Completions** → Number of visitors who successfully completed that step. - **Drop-off Rate** → Percentage of users who left at that step. Fix the step with the highest drop-off rate first. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Form Builder | Dynamic Lead Forms | Surface Docs URL: https://surface.thesurface.network/docs/platform/forms/builder Dynamic Lead Forms Create powerful, conversion-optimized forms with our no-code builder Build multi-step forms without writing code, with conditional logic, marketing content and a wide range of components. ### [Single Pane or Dual Pane](#single-pane-or-dual-pane) Choose one of two layouts: 1. **Single Pane:** just the form. Best for simple forms and embeds. 2. **Dual Pane:** split screen, with marketing content on one side and the form on the other. Best for landing pages. Every component supports: - **Style Customization**: Modify colors, fonts, spacing, and more - **Responsive Design**: Components automatically adapt to different screen sizes Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Conditional Logic | Dynamic Lead Forms | Surface Docs URL: https://surface.thesurface.network/docs/platform/forms/conditional-logic Dynamic Lead Forms Control how users move through your form with conditional logic and branching flows Conditional logic controls how people move through your form. You decide which step comes next, when a response counts as completed, and when to stop someone continuing. 1. Navigate to your form in the Surface editor. 2. At the top, click on the **Logic** tab. 3. Select the step you want to configure. ### [1\. Change the Default Next Step](#1-change-the-default-next-step) By default, each step flows to the next one in order. To change that: 1. Select a step (e.g., step0). 2. In the right-hand panel, open the **Default next step** dropdown. 3. Choose which step should follow. ### [2\. Mark a Step as a Completion Step](#2-mark-a-step-as-a-completion-step) A **Completion Step** ends the form once the user reaches it. - Toggle on **Completion Step** in the right-hand panel. - When a user lands on this step, their response is marked as **Completed**, and workflows tied to completions will run. Use this for your final **Thank You** or **Confirmation** screens. ### [3\. Mark a Step as an Invalid Step](#3-mark-a-step-as-an-invalid-step) An **Invalid Step** blocks the user from progressing further. - Toggle on **Invalid Step** in the right-hand panel. - When a user lands here, their response is marked as **Invalid**. - Invalid responses will **not trigger workflows** and the user cannot move forward. Use it to filter out unqualified leads, or to handle incorrect inputs. Advanced Routing sends people to different steps based on their answers, instead of a fixed linear flow. ### [What You Can Do with Advanced Routing](#what-you-can-do-with-advanced-routing) 1. **Add Conditions**: define rules that check user inputs (e.g., email, company size, budget, etc.). 2. **Use Form Response Data**: conditions can be applied directly on responses collected in previous steps. ### [Example](#example) To skip certain people straight to the end of the form based on their email address: - **Condition**: If the email entered in **Step 0** equals [saharsh@withsurface.com](mailto:saharsh@withsurface.com) - **Action**: Jump to **Step 2** (Thank you step) - **Else**: Default path continues to **Step 1** Combine multiple conditions with **AND** / **OR** logic to build branching flows. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Embedding a Surface Form | Embedding | Surface Docs URL: https://surface.thesurface.network/docs/platform/forms/embedding Dynamic Lead Forms Embedding Six ways to put a Surface form on your site, and how to pick one. Each mode has its own page, with instructions for Webflow, Framer, WordPress, Next.js, React, Unbounce and plain HTML. **WAIT...** Make sure that you have added the [**Surface Tag**](https://www.withsurface.com/docs/platform/traffic/surface-tag) to your site before proceeding. If your site uses a cookie banner, also configure [cookie consent](https://www.withsurface.com/docs/platform/traffic/cookie-consent) on the tag. Mode The form appears Best for Needs the embed script **[Inline](https://www.withsurface.com/docs/platform/forms/embedding/inline)** In the page, in the flow of content Landing pages, pricing pages, anywhere the form _is_ the call to action No, just an iframe **[Popup](https://www.withsurface.com/docs/platform/forms/embedding/popup)** Modal over the page, on click "Book a demo" buttons in a nav or hero Yes **[Slideover](https://www.withsurface.com/docs/platform/forms/embedding/slideover)** Panel sliding in from the side, on click Long forms where losing page context hurts Yes **[Input field](https://www.withsurface.com/docs/platform/forms/embedding/input-field)** Opens pre-filled after someone submits an email box you already have Turning an existing newsletter or "get started" input into a full form Yes **[Widget](https://www.withsurface.com/docs/platform/forms/embedding/widget)** A floating button, bottom corner, every page Site-wide always-available contact Yes **[Direct link](https://www.withsurface.com/docs/platform/forms/embedding/direct-link)** Its own page, at a Surface URL Email, ads, social, QR codes, anywhere you have no site to embed in No Then [optimize loading speed](https://www.withsurface.com/docs/platform/forms/embedding/optimize), which applies to all six. Best first. The fewer clicks between intent and the first question, the better: Input field trigger Their first answer is captured before the form opens, so you keep a partial even if they leave. Inline Zero clicks. The form is already on the page. Popup or slideover One click. Fine when the trigger is explicit ("Book a demo"), poor when it is a surprise. Widget Always available, rarely noticed. Check your own numbers: [form analytics](https://www.withsurface.com/docs/platform/forms/analytics) gives you view → start → completion per form. **The embed script needs the Surface Tag.** Inline and direct link work without it. Every triggered mode needs it, so install the [Surface Tag](https://www.withsurface.com/docs/platform/traffic/surface-tag) first. **Publish after pasting.** Webflow and Framer both stage custom code. It does nothing live until you publish. This section is the reference: what each mode is and the snippet it needs. For a click-by-click walkthrough on one host, Framer, Webflow, WordPress, React, Next.js or Unbounce, see [Form Embedding](https://www.withsurface.com/docs/embedding/website-editors). Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Direct Link | Embedding | Surface Docs URL: https://surface.thesurface.network/docs/platform/forms/embedding/direct-link Dynamic Lead Forms Embedding Open the form automatically when the page loads This feature is only available for popup and slideover forms. Append `showSurfaceForm=true` to the url of your website: ``` https://YOUR_WEBSITE.com/?showSurfaceForm=true ``` Replace `YOUR_WEBSITE.com` with your actual website URL. The form opens on page load, with no trigger button to click. It is the only mode that works where you have no page to embed in: an email, an ad, a QR code, a link in a Slack message. It is also the fastest way to test a form. Send yourself the URL, submit it, and check the row appears in [Leads](https://www.withsurface.com/docs/platform/leads). The parameter survives other query strings, so `?utm_source=newsletter&showSurfaceForm=true` both opens the form and attributes the visit. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Inline Form Embed | Embedding | Surface Docs URL: https://surface.thesurface.network/docs/platform/forms/embedding/inline Dynamic Lead Forms Embedding Embed your form inline with the rest of your page **WAIT...** Make sure that you have added the [**Surface Tag**](https://www.withsurface.com/docs/platform/traffic/surface-tag) to your site before proceeding. If your site uses a cookie banner, also configure [cookie consent](https://www.withsurface.com/docs/platform/traffic/cookie-consent) on the tag. Add this code where the form should appear: ``` ``` Replace `REPLACE ME WITH FORM URL` with your form URL. Click **Share** in the form's `Overview` section to find it. Add the following `` tags inside the `` of your site: ``` ``` Replace `REPLACE ME WITH FORM URL` with a Surface Form URL. 1. dns-prefetch → Resolves the domain early to skip DNS lookup delays. 2. preconnect → Prepares the TCP + TLS handshake so the browser is ready to request assets immediately. 3. prefetch → Fetches the form in advance, so it's ready when a user opens it. The iframe is the same everywhere. Only where it goes changes. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Email Input Field Trigger | Embedding | Surface Docs URL: https://surface.thesurface.network/docs/platform/forms/embedding/input-field Dynamic Lead Forms Embedding Triggering via email input field submission **WAIT...** Make sure that you have added the [**Surface Tag**](https://www.withsurface.com/docs/platform/traffic/surface-tag) to your site before proceeding. If your site uses a cookie banner, also configure [cookie consent](https://www.withsurface.com/docs/platform/traffic/cookie-consent) on the tag. Your HTML form needs the `surface-form-handler` class: ```
``` Add the **`surface-form-handler`** class to any external form that you want to use to trigger the Surface Form popup. Modify the Surface Form Embedding Script to include the `data-question-id` attribute. You must replace the **``** within **`data-question-id`** attribute below with the question ID from the Surface Form Builder. ``` ``` - Enter a valid email in the input field and press "Submit" or hit "Enter". - Verify that the Surface Form popup is displayed as expected. Add the following `` tags inside the `` of your site: ``` ``` Replace `REPLACE ME WITH FORM URL` with a Surface Form URL. 1. dns-prefetch → Resolves the domain early to skip DNS lookup delays. 2. preconnect → Prepares the TCP + TLS handshake so the browser is ready to request assets immediately. 3. prefetch → Fetches the form in advance, so it's ready when a user opens it. The constructor script goes in the same place as any other triggered embed. Your existing email input needs `class="surface-form-handler"` on its `
`. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Optimize Loading Speed | Embedding | Surface Docs URL: https://surface.thesurface.network/docs/platform/forms/embedding/optimize Dynamic Lead Forms Embedding Optimize Surface Forms loading speed for better performance Surface forms load fast already. To cut the wait further, tell the browser to prepare its connection to [forms.withsurface.com](http://forms.withsurface.com/) ahead of time, so the form is ready the moment it is triggered. Add the following `` tags inside the `` of your site: ``` ``` Replace `REPLACE ME WITH FORM URL` with a Surface Form URL. 1. dns-prefetch → Resolves the domain early to skip DNS lookup delays. 2. preconnect → Prepares the TCP + TLS handshake so the browser is ready to request assets immediately. 3. prefetch → Fetches the form in advance, so it's ready when a user opens it. These are `` tags, so they go wherever your platform puts head code. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Popup Form Embed | Embedding | Surface Docs URL: https://surface.thesurface.network/docs/platform/forms/embedding/popup Dynamic Lead Forms Embedding Display your form as a popup modal **WAIT...** Make sure that you have added the [**Surface Tag**](https://www.withsurface.com/docs/platform/traffic/surface-tag) to your site before proceeding. If your site uses a cookie banner, also configure [cookie consent](https://www.withsurface.com/docs/platform/traffic/cookie-consent) on the tag. Add this code to your site's `head` tag to enable the popup form. ``` ``` Replace **`REPLACE ME WITH FORM URL`** with your form URL. Click the share button in the Surface app to find it. Add the class `surface-form-button` to any element that should open the form. ``` ``` Set `popupSize` to control how large the popup is: ``` ``` Append `showSurfaceForm=true` to the url of your website. For example: ``` https://YOUR_WEBSITE.com/?showSurfaceForm=true ``` Replace `YOUR_WEBSITE.com` with your actual website URL. The popup opens on page load, with no trigger button to click. Add the following `` tags inside the `` of your site: ``` ``` Replace `REPLACE ME WITH FORM URL` with a Surface Form URL. ### [Explanation](#explanation) 1. dns-prefetch → Resolves the domain early to skip DNS lookup delays. 2. preconnect → Prepares the TCP + TLS handshake so the browser is ready to request assets immediately. 3. prefetch → Fetches the form in advance, so it's ready when a user opens it. The script is the same on every platform. What changes is where it goes, and how the trigger element gets the `surface-form-button` class. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # Slideover Form Embed | Embedding | Surface Docs URL: https://surface.thesurface.network/docs/platform/forms/embedding/slideover Dynamic Lead Forms Embedding Display your form as a full page slide-over **WAIT...** Make sure that you have added the [**Surface Tag**](https://www.withsurface.com/docs/platform/traffic/surface-tag) to your site before proceeding. If your site uses a cookie banner, also configure [cookie consent](https://www.withsurface.com/docs/platform/traffic/cookie-consent) on the tag. Add this code to your site's `head` tag to enable the slideover form. ``` ``` Replace **`REPLACE ME WITH FORM URL`** with your form URL. Click the share button in the Surface app to find it. Add the class `surface-form-button` to any element that should open the form. ``` ``` Append `showSurfaceForm=true` to the url of your website. For example: ``` https://YOUR_WEBSITE.com/?showSurfaceForm=true ``` Replace `YOUR_WEBSITE.com` with your actual website URL. The slideover opens on page load, with no trigger button to click. Add the following `` tags inside the `` of your site: ``` ``` Replace `REPLACE ME WITH FORM URL` with a Surface Form URL. ### [Explanation](#explanation) 1. dns-prefetch → Resolves the domain early to skip DNS lookup delays. 2. preconnect → Prepares the TCP + TLS handshake so the browser is ready to request assets immediately. 3. prefetch → Fetches the form in advance, so it's ready when a user opens it. The script is the same on every platform, and only `surface_embed_type` differs from the popup. What changes is where the script goes, and how the trigger element gets its class. Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # URL Prefill | Embedding | Surface Docs URL: https://surface.thesurface.network/docs/platform/forms/embedding/url-prefill Dynamic Lead Forms Embedding Fill in answers from the page URL before the visitor starts Add query parameters to a URL and the form opens with those answers already filled in. Use it for campaign links, emails, and ads where you already know who the visitor is. ``` https://YOUR_WEBSITE.com/demo?_= ``` Where the form lives Put the parameters on Embedded with the [Surface Tag](https://www.withsurface.com/docs/platform/traffic/surface-tag) (inline, popup, slideover, widget) The URL of your page Surface form link (`forms.withsurface.com/s/`) The form link Your own ` ``` Every mode is on [Embedding](https://www.withsurface.com/docs/platform/forms/embedding). Submit it yourself Fill your own form once with a real work email. It appears under **Leads** with company, industry and headcount filled in, and an AI lead score. Row there but enrichment empty? The email was a free provider. [Enrichment](https://www.withsurface.com/docs/platform/leads/enrichment) resolves companies, not inboxes. Send it somewhere Add one workflow: post to Slack, create a HubSpot contact, or fire a webhook. [Workflows](https://www.withsurface.com/docs/platform/forms/workflows) · [Integrations](https://www.withsurface.com/docs/platform/integrations) - Every visit and AI referral in [Traffic analytics](https://www.withsurface.com/docs/platform/traffic/analytics). - One enriched, scored row per person in the [Lead Data Layer](https://www.withsurface.com/docs/platform/leads). - Page views → form views → starts → completions → qualified → meetings in the [Conversion funnel](https://www.withsurface.com/docs/platform/traffic/conversion-funnel). Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # What is Surface? | Surface Docs URL: https://surface.thesurface.network/docs/what-is-surface What Surface does, what it replaces, and where its intelligence comes from. Surface is a marketing system with two halves that feed each other. **The infrastructure half** sits on your website and captures demand: a tag that records who arrives and where from, forms that branch on the answers, scheduling that books the qualified ones, and a lead record that keeps what all of it learned. **The agent half** reads that record and does the work: researching and scoring leads, keeping your CRM current, finding the questions buyers ask AI engines, and writing the campaigns that answer them. You probably run Surface does it as Typeform / HubSpot forms [Dynamic Lead Forms](https://www.withsurface.com/docs/platform/forms/builder) Chili Piper / Calendly [Intelligent Scheduling](https://www.withsurface.com/docs/platform/scheduling/overview), with no per-seat pricing Manual enrichment runs [Lead Agents](https://www.withsurface.com/docs/platform/lead-agents/overview). You can also [connect the provider you already pay for](https://www.withsurface.com/docs/platform/integrations) An AEO/GEO monitoring tool [AI Visibility](https://www.withsurface.com/docs/platform/ai-visibility/overview) A content agency retainer [Campaign Agents](https://www.withsurface.com/docs/platform/campaign-agents/overview) GA4 dashboards nobody trusts [Traffic Intelligence](https://www.withsurface.com/docs/platform/traffic/analytics) Most teams start with the tag or forms, then add agents. Your traffic The [Surface Tag](https://www.withsurface.com/docs/platform/traffic/surface-tag) records who arrives, from where, and what they do. Visitors who came from an answer engine are reported that way instead of as "direct". Your leads Every capture becomes one record in the [Lead Data Layer](https://www.withsurface.com/docs/platform/leads): enriched, scored, stamped with the journey that produced it. Outcomes (meetings, closed deals) come back to that record. Your Vault The [Vault](https://www.withsurface.com/docs/platform/vault/overview) is your own words: positioning, proof, objections, voice. Agents read it before they write. Agents in Surface: - **run without being asked**: enrichment and scoring fire on capture, and the competitor agent checks on its own timer. - **write to real systems**: the lead record, your CRM, the CMS, your calendar. - **stop for a human before they publish or change anything**. See [SAM's approval gate](https://www.withsurface.com/docs/platform/sam/limits). - **are metered**: an _agent action_ is the unit your plan is sized in, see [Core concepts](https://www.withsurface.com/docs/concepts#agent-action). See it against your own site We'll run a traffic audit and an AI visibility scan on your domain before the call. [Book a demo](https://www.withsurface.com/book-a-demo) Ready to Get Started? See it on your own site, or open the app and build the first form. Need Help? Setup problems, blocked domains and CRM push failures live in the Help Center. Feature Requests? Tell us what is missing. We would rather hear it than guess. --- # FAQ | Surface Labs URL: https://surface.thesurface.network/faq ## Campaigns & Content How does Surface generate more qualified demand? Surface turns real buyer, content, conversion, and revenue signals into campaign direction, helping teams create demand around evidence instead of assumptions. How does Surface decide what content to create? Surface can use qualified-buyer patterns already in your funnel, including the questions buyers ask, the messages that draw serious interest, and the content associated with opportunities. What content can Surface help create? Surface can turn approved buyer insight into briefs, articles, landing-page copy, social posts, and other scoped assets that share the same sources and message. Can our team review content before it is published? Yes. Teams define sources, brand and compliance rules, named approvers, and publishing permissions. Human review remains in the workflow before content moves into production. Does Surface replace our CMS or writing tools? No. Surface works alongside your existing CMS and supported content tools. Teams can also create from Claude or Codex while Surface supplies buyer context, permissions, and measurement. Ready to get started? ## See Surface in action Book a demo to learn how Surface can transform your marketing operations with AI-powered intelligence and automation. [Book a demo](https://www.withsurface.com/book-a-demo) --- # Surface for Ad Buyers URL: https://surface.thesurface.network/for/ad-buyers - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Surface for Content Marketers URL: https://surface.thesurface.network/for/content-marketers - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Surface for Demand Gen URL: https://surface.thesurface.network/for/demand-gen - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Surface for GTM Engineers URL: https://surface.thesurface.network/for/gtm-engineers - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Surface for Marketing Operations URL: https://surface.thesurface.network/for/marketing-operations - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Surface for Revenue Leaders URL: https://surface.thesurface.network/for/revenue-leaders Surface for Revenue Leaders ## Run inbound as one revenue system. What changes ## Less stack. More accountable pipeline. ## How it works Surface connects buyer signals, execution, and revenue outcomes in one operating loop. 1. 01 ### Unify the revenue context. Bring lead, campaign, sales, and revenue signals into one accountable operating layer. Leads01 Campaigns02 Revenue03 2. 02 ### Act from shared data. Qualify, route, schedule, and launch campaigns without disconnected team handoffs. Qualify01 Route02 Launch03 3. 03 ### Compound every outcome. Use sales acceptance, pipeline, and revenue to improve the next decision across teams. Acceptance01 Pipeline02 Next action03 Graphic placeholder: connected inbound revenue system [ **Maddy Fennessy**Growth Marketing Lead, Metronome > “We feel pretty embedded in Surface, especially since we did the PLG stuff there. I would consider Surface to be like a pretty core part of what is running our website, which is a good thing.” ](https://www.withsurface.com/customers) [ **Shubh Agrawal**San Francisco, Valley > “If we turned off Surface tomorrow, we'd lose a lot of inbound. We're almost entirely inbound-driven, so Surface is a critical part of how we operate.” ](https://www.withsurface.com/customers/valley) [ **Alexandra Doan**San Francisco, Nextiva > “We actually saw that 37% more users on average converted with the new form that they built for us” ](https://www.withsurface.com/customers/nextiva) [ **Pujun Bhatnagar**CEO, Kintsugi > “We're growing at the speed of light, and Surface is one of the few vendors keeping up with us. I'd pay whatever it takes to solve this problem, and Surface solved it.” ](https://www.withsurface.com/customers/kintsugi) [ **Angela Kou**Chief of Staff, Juicebox > “Whenever I had a feature request, the Surface team would update me throughout the process and follow up after launch to make sure everything was working correctly. It really feels like a white-glove experience.” ](https://www.withsurface.com/customers/juicebox) [ **Ian Christopher**CEO, Galley > “We used Typeform in the early days. It was great but you can tell when a company outgrows it. Surface gives us the mechanics we liked from Typeform, but with enterprise-grade control over brand, format, and functionality.” ](https://www.withsurface.com/customers/galley) Set up once ## Make inbound accountable to pipeline. [BOOK A DEMO](https://www.withsurface.com/book-a-demo) --- # Surface for Revenue Operations Teams URL: https://surface.thesurface.network/for/revops Surface for RevOps ## Make every inbound handoffexplainable At a glance ## What changes for your team. Start with the outcome that matters most. Each block connects to the deeper workflow below. ## Replace brittle glue with controlled logic Inbound logic grows one form rule, automation, enrichment step, and spreadsheet exception at a time, until no one can explain why a record was routed or why fields disagree. Surface consolidates the decision path and records the reason behind each outcome. ## The operating layer RevOps needs - Shared ICP, qualification, and disqualification definitions - Territory, named-account, capacity, and fallback routing - Scheduling and CRM ownership synchronization - Human-review queues for ambiguous or sensitive decisions Verdict Every change records what moved, who approved it, and what it affects. ## Work alongside HubSpot or Salesforce Surface is an improvement layer beside HubSpot or Salesforce, not a forced CRM replacement. Implementation maps record identity, source of truth, field ownership, write-back, duplicate handling, and failure recovery; production support matches what was validated. - [HubSpot →](https://www.withsurface.com/integrations/hubspot) - [Salesforce →](https://www.withsurface.com/integrations/salesforce) ## Keep agents inside the policy Research and campaign agents can act only within granted data access, tools, and approval paths. ## Prove the workflow end to end A scoped assessment can baseline response time, routing exceptions, reassignments, sales acceptance, and opportunity conversion. In production the same measures extend to enrichment and sync coverage, manual-review rate, automation failures, and stale records. An implementation checklist with an owner and a status against each item: definitions, systems mapping, exception and monitoring readiness, and acceptance and launch. Set up once ## Bring one routing rule nobody wants to touch [Book a Demo](https://www.withsurface.com/book-a-demo) --- # Surface for Sales Leaders URL: https://surface.thesurface.network/for/sales-leaders - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Glossary | Surface Labs URL: https://surface.thesurface.network/glossary - [ Acquisition in MarketingMarketing Foundations Acquisition in marketing is the work of turning people or accounts outside the customer base into new users, leads, opportunities, or customers. ](https://www.withsurface.com/glossary/acquisition-in-marketing) - [ Advanced Prompt EngineeringAI Search & Prompting Advanced prompt engineering designs multi-stage, evaluated model workflows that use retrieval, tools, structured outputs, and explicit controls. ](https://www.withsurface.com/glossary/advanced-prompt-engineering) - [ Advantages of Market ResearchAI Search & Prompting Market research reduces decision uncertainty by clarifying audiences, demand, alternatives, language, risk, and the evidence behind a business choice. ](https://www.withsurface.com/glossary/advantages-of-market-research) - [ Advertising Market ResearchAI Search & Prompting Advertising market research studies audiences, messages, creative, media behavior, campaign response, brand effects, and incremental business outcomes. ](https://www.withsurface.com/glossary/advertising-market-research) - [ AI Content BriefMarketing Foundations An AI content brief uses model assistance to organize evidence, audience intent, page purpose, structure, links, conversion, and review requirements for a content asset. ](https://www.withsurface.com/glossary/ai-content-brief) - [ AI Content Marketing StrategyMarketing Foundations An AI content marketing strategy uses AI within a governed system for audience research, publishing, distribution, conversion, and learning. ](https://www.withsurface.com/glossary/ai-content-marketing-strategy) - [ AI Content StrategyMarketing Foundations An AI content strategy defines where AI assists content work, where human judgment remains required, and how the system supports business goals. ](https://www.withsurface.com/glossary/ai-content-strategy) - [ AI Data CleansingMarketing Foundations AI data cleansing uses models to suggest corrections, matches, classifications, or anomaly flags within a controlled data-quality workflow. ](https://www.withsurface.com/glossary/ai-data-cleansing) - [ AI SEO StrategyAI Search & Prompting An AI SEO strategy connects classic search fundamentals with content, entity, and measurement work for AI-mediated discovery. ](https://www.withsurface.com/glossary/ai-seo-strategy) - [ Automated Data CleansingMarketing Foundations Automated data cleansing applies repeatable rules and models to profile, validate, normalize, match, correct, or quarantine records at operational scale. ](https://www.withsurface.com/glossary/automated-data-cleansing) - [ Automated Marketing CampaignsMarketing Foundations Automated marketing campaigns use schedules, events, audience rules, and customer data to execute repeatable campaign actions with defined exits and human oversight. ](https://www.withsurface.com/glossary/automated-marketing-campaigns) - [ B2B Content MarketingMarketing Foundations B2B content marketing uses useful, credible media to help business buyers understand problems, compare approaches, build internal support, and act. ](https://www.withsurface.com/glossary/b2b-content-marketing) - [ B2B Conversion Rate OptimizationMarketing Foundations B2B conversion rate optimization improves the percentage of eligible visitors or leads who complete a meaningful next action. ](https://www.withsurface.com/glossary/b2b-conversion-rate-optimization) - [ B2B Digital Lead GenerationMarketing Foundations B2B digital lead generation uses online channels and conversion systems to create identifiable, qualified demand from business buyers. ](https://www.withsurface.com/glossary/b2b-digital-lead-generation) - [ B2B Lead Generation FunnelMarketing Foundations A B2B lead generation funnel models how market attention becomes identifiable demand, qualification, meetings, opportunities, and customers across a buying group. ](https://www.withsurface.com/glossary/b2b-lead-generation-funnel) - [ B2B Martech StackMarketing Foundations A B2B martech stack is the coordinated set of data, systems, integrations, and operating rules used to run marketing across a business buying cycle. ](https://www.withsurface.com/glossary/b2b-martech-stack) - [ Benefits of Data CleansingMarketing Foundations Data cleansing improves the reliability of routing, reporting, segmentation, personalization, compliance, and customer records. ](https://www.withsurface.com/glossary/benefits-of-data-cleansing) - [ Brand Market ResearchAI Search & Prompting Brand market research studies how a defined audience recognizes, understands, remembers, considers, and compares a brand in a market. ](https://www.withsurface.com/glossary/brand-market-research) - [ Brand Marketing ResearchAI Search & Prompting Brand marketing research studies awareness, associations, meaning, preference, trust, differentiation, and response to brand choices among defined audiences. ](https://www.withsurface.com/glossary/brand-marketing-research) - [ Brand Schema MarkupAI Search & Prompting Brand schema markup uses structured data to state a company's stable identity, official properties, and relationships across its site. ](https://www.withsurface.com/glossary/brand-schema-markup) - [ Business Research and Its TypesAI Search & Prompting Business research is the structured collection and analysis of evidence used to make market, customer, product, financial, and operating decisions. ](https://www.withsurface.com/glossary/business-research-and-its-types) - [ Business Research Methods ProcessAI Search & Prompting The business research methods process turns a decision and its uncertainty into a scoped study, credible evidence, analysis, and an accountable recommendation. ](https://www.withsurface.com/glossary/process-of-business-research-methods) - [ Business-to-Business Market ResearchAI Search & Prompting Business-to-business market research studies organizations, buying groups, users, competitors, economics, and operating constraints in a defined B2B market. ](https://www.withsurface.com/glossary/business-to-business-market-research) - [ Chatbot Prompt EngineeringAI Search & Prompting Chatbot prompt engineering designs instructions, context, state, and fallback behavior for reliable multi-turn conversations. ](https://www.withsurface.com/glossary/chatbot-prompt-engineering) - [ Client AcquisitionMarketing Foundations Client acquisition is the process a service or relationship-led business uses to attract, qualify, win, and begin work with suitable new clients. ](https://www.withsurface.com/glossary/client-acquisition) - [ Client Lead GenerationMarketing Foundations Client lead generation creates qualified opportunities for service businesses by connecting a defined client problem with trust, capture, and follow-up. ](https://www.withsurface.com/glossary/client-lead-generation) - [ Competitive Analysis ResearchAI Search & Prompting Competitive analysis research collects dated evidence about rivals and alternatives to support positioning, product, pricing, content, and go-to-market decisions. ](https://www.withsurface.com/glossary/competitive-analysis-research) - [ Competitive DataMarketing Foundations Competitive data is dated, sourced information about the alternatives buyers consider, including products, prices, positioning, proof, and market activity. ](https://www.withsurface.com/glossary/competitive-data) - [ Competitive LandscapeAI Search & Prompting A competitive landscape is a dated view of the alternatives buyers consider, how those options differ, and which market forces may change the choice. ](https://www.withsurface.com/glossary/competitive-landscape) - [ Competitive Landscape AnalysisAI Search & Prompting A competitive landscape analysis maps the structure of a market, its competitor groups, substitutes, positions, capabilities, movement, and areas of buyer choice. ](https://www.withsurface.com/glossary/competitive-landscape-analysis) - [ Competitive MarketAI Search & Prompting A competitive market is one where buyers can choose among credible sellers, substitutes, or existing approaches that constrain price and positioning. ](https://www.withsurface.com/glossary/competitive-market) - [ Competitive Market AnalysisAI Search & Prompting A competitive market analysis evaluates rivals and substitutes inside a defined market to guide positioning, product, pricing, sales, and go-to-market choices. ](https://www.withsurface.com/glossary/competitive-market-analysis) - [ Competitive MarketingAI Search & Prompting Competitive marketing uses verified market and competitor evidence to sharpen positioning, campaigns, sales material, and customer choices. ](https://www.withsurface.com/glossary/competitive-marketing) - [ Competitor Definition in BusinessAI Search & Prompting A competitor in business is any company, alternative, or existing approach that can win the same buyer decision, budget, access, or outcome. ](https://www.withsurface.com/glossary/competitor-definition-business) - [ Competitor Sets in BusinessAI Search & Prompting Competitors in business are organizations and alternatives whose choices can affect a company's ability to win customers, budgets, channels, inputs, or talent. ](https://www.withsurface.com/glossary/competitors-in-business) - [ Content HubMarketing Foundations A content hub is an organized collection of related pages that helps a defined audience explore a subject, answer connected questions, and take a useful next step. ](https://www.withsurface.com/glossary/content-hub) - [ Content Marketing AnalysisMarketing Foundations Content marketing analysis examines how a content portfolio reaches the intended audience, supports buyer decisions, and contributes to business outcomes. ](https://www.withsurface.com/glossary/content-marketing-analysis) - [ Content Marketing and Digital MarketingMarketing Foundations Content marketing gives digital channels useful assets, audience understanding, evidence, and conversion paths that improve discovery and campaign performance. ](https://www.withsurface.com/glossary/how-does-content-marketing-support-digital-marketing) - [ Content Marketing and SalesMarketing Foundations Content marketing can drive sales by creating demand, capturing active interest, supplying proof, and helping buying groups move through a decision. ](https://www.withsurface.com/glossary/how-content-marketing-drives-sales) - [ Content Marketing for SEOMarketing Foundations Content marketing helps SEO by creating useful, crawlable resources that answer demand, develop topical coverage, earn links, clarify entities, and support conversion. ](https://www.withsurface.com/glossary/how-content-marketing-helps-seo) - [ Content Marketing LifecycleMarketing Foundations The content marketing lifecycle covers the research, planning, creation, review, publication, distribution, measurement, revision, and retirement of content. ](https://www.withsurface.com/glossary/content-marketing-lifecycle) - [ Content PillarMarketing Foundations A content pillar is a central topic and anchor asset that organizes related questions, pages, evidence, and conversion paths. ](https://www.withsurface.com/glossary/content-pillar) - [ Content ProductionMarketing Foundations Content production is the coordinated work of turning an approved idea and evidence into a reviewed, published, distributed, and reusable asset. ](https://www.withsurface.com/glossary/content-production) - [ Content Strategy and SEOMarketing Foundations Content strategy decides what a company should explain and why; SEO helps that material become discoverable, interpretable, and connected to real search demand. ](https://www.withsurface.com/glossary/content-strategy-and-seo) - [ CRM and Marketing AutomationMarketing Foundations CRM and marketing automation connect customer records with campaign and workflow execution across the buyer lifecycle. ](https://www.withsurface.com/glossary/crm-and-marketing-automation) - [ CRM Marketing AutomationMarketing Foundations CRM marketing automation uses customer-record data and workflow rules to trigger, personalize, route, and measure marketing actions. ](https://www.withsurface.com/glossary/crm-marketing-automation) - [ CSV as Structured DataAI Search & Prompting CSV usually represents structured tabular data when rows and columns follow consistent definitions, though the format does not enforce a schema. ](https://www.withsurface.com/glossary/is-csv-structured-data) - [ Customer AcquisitionMarketing Foundations Customer acquisition is the coordinated work that turns an appropriate noncustomer into a new customer through demand, conversion, sales, and onboarding. ](https://www.withsurface.com/glossary/customer-acquisition) - [ Customer Acquisition ProcessMarketing Foundations The customer acquisition process is the connected set of market, marketing, sales, and onboarding activities that turns a defined audience into new customers. ](https://www.withsurface.com/glossary/customer-acquisition-process) - [ Customer Acquisition StrategyMarketing Foundations A customer acquisition strategy sets the segment, position, offer, channel portfolio, conversion path, economics, and learning system used to win suitable new customers. ](https://www.withsurface.com/glossary/customer-acquisition-strategy) - [ Customer DataMarketing Foundations Customer data is information about people and accounts collected through their relationship, transactions, product use, communication, and consent choices. ](https://www.withsurface.com/glossary/customer-data) - [ Customer Data GovernanceMarketing Foundations Customer data governance assigns authority and controls for how prospect and customer information is collected, defined, accessed, used, changed, retained, and removed. ](https://www.withsurface.com/glossary/customer-data-governance) - [ Customer Lifecycle MarketingMarketing Foundations Customer lifecycle marketing coordinates useful communication and action as customers move through onboarding, adoption, retention, expansion, lapse, and reactivation. ](https://www.withsurface.com/glossary/customer-lifecycle-marketing) - [ Customer Research MethodsAI Search & Prompting Customer research methods collect reported, observed, and behavioral evidence about customer needs, decisions, experiences, and outcomes. ](https://www.withsurface.com/glossary/customer-research-methods) - [ Data and Analytics GovernanceMarketing Foundations Data and analytics governance assigns authority, definitions, quality controls, access, lineage, change rules, and accountability for analytical data and metrics. ](https://www.withsurface.com/glossary/data-and-analytics-governance) - [ Data CleaningMarketing Foundations Data cleaning detects and corrects inaccurate, incomplete, inconsistent, duplicate, or unusable values before teams analyze or act on them. ](https://www.withsurface.com/glossary/data-cleaning-and-why-is-it-important) - [ Data CleansingMarketing Foundations Data cleansing corrects or isolates unreliable records so analysis, automation, and customer-facing actions use information fit for purpose. ](https://www.withsurface.com/glossary/data-cleansing-and-why-is-it-important) - [ Data Cleansing and TransformationMarketing Foundations Data cleansing repairs unreliable values, while transformation changes data into the structure, units, or categories required for use. ](https://www.withsurface.com/glossary/data-cleansing-and-transformation) - [ Data Cleansing DeduplicationMarketing Foundations Data cleansing deduplication identifies records that refer to the same real entity and resolves them through documented linking, suppression, or controlled merging. ](https://www.withsurface.com/glossary/data-cleansing-deduplication) - [ Data Cleansing StrategyMarketing Foundations A data cleansing strategy prioritizes quality rules, owners, workflows, and prevention according to the business decisions the data supports. ](https://www.withsurface.com/glossary/data-cleansing-strategy) - [ Data Cleansing SystemMarketing Foundations A data cleansing system detects, standardizes, validates, corrects, merges, suppresses, and monitors records under documented rules and review paths. ](https://www.withsurface.com/glossary/data-cleansing-system) - [ Data Governance and Data ManagementMarketing Foundations Data governance sets authority, definitions, and rules for data, while data management carries out the technical and operational work needed to apply them. ](https://www.withsurface.com/glossary/data-governance-and-data-management) - [ Data Governance FrameworksMarketing Foundations Data governance frameworks assign authority, definitions, controls, and review processes for the data an organization relies on. ](https://www.withsurface.com/glossary/data-governance-frameworks) - [ Data Governance ModelMarketing Foundations A data governance model defines who has authority over data, how decisions are made, and which roles enforce quality, access, use, and change rules. ](https://www.withsurface.com/glossary/data-governance-model) - [ Data Governance PolicyMarketing Foundations A data governance policy states the authority, principles, requirements, and enforcement rules that govern data across its lifecycle. ](https://www.withsurface.com/glossary/data-governance-policy) - [ Data Governance ProcessesMarketing Foundations Data governance processes are recurring workflows that apply ownership, definitions, quality, access, change, retention, and issue rules to data. ](https://www.withsurface.com/glossary/data-governance-processes) - [ Data Governance StrategyMarketing Foundations A data governance strategy sets priorities, decision rights, controls, and a roadmap for making important data trustworthy, usable, secure, and accountable. ](https://www.withsurface.com/glossary/data-governance-strategy) - [ Data Management and GovernanceMarketing Foundations Data management runs the data lifecycle, while data governance assigns authority, standards, controls, and accountability for important data decisions. ](https://www.withsurface.com/glossary/data-management-and-governance) - [ Data Strategy and GovernanceMarketing Foundations Data strategy sets the business priorities and capabilities for data, while governance assigns definitions, authority, controls, and accountability for using it. ](https://www.withsurface.com/glossary/data-strategy-and-governance) - [ Demand Generation MetricsMarketing Foundations Demand generation metrics measure how a defined audience becomes aware, engaged, identifiable, qualified, and commercially active over time. ](https://www.withsurface.com/glossary/demand-gen-metrics) - [ Digital Lead Generation StrategiesMarketing Foundations Digital lead generation strategies combine online demand creation, intent capture, conversion, qualification, routing, and learning for a defined B2B audience. ](https://www.withsurface.com/glossary/digital-lead-generation-strategies) - [ Digital Marketing and Lead GenerationMarketing Foundations Digital marketing creates and captures online demand, while lead generation turns selected responses into identifiable records for qualification and follow-up. ](https://www.withsurface.com/glossary/digital-marketing-and-lead-generation) - [ Digital Marketing OperationsMarketing Foundations Digital marketing operations is the operating system that turns digital strategy into governed campaigns, content, data flows, launches, measurement, and learning. ](https://www.withsurface.com/glossary/digital-marketing-operations) - [ Direct Marketing Lead GenerationMarketing Foundations Direct marketing lead generation sends a targeted message and response offer to a defined audience so interested people can identify themselves. ](https://www.withsurface.com/glossary/direct-marketing-lead-generation) - [ Effective Lead Generation TacticsMarketing Foundations Effective lead generation tactics match a defined buyer problem with useful demand creation, clear capture, qualification, and timely follow-up. ](https://www.withsurface.com/glossary/most-effective-lead-generation-tactics) - [ Enterprise Marketing AutomationMarketing Foundations Enterprise marketing automation coordinates high-volume, multi-market campaigns and customer workflows under shared data, governance, integration, and measurement rules. ](https://www.withsurface.com/glossary/enterprise-marketing-automation) - [ Example of Structured DataAI Search & Prompting A CRM lead record is a common example of structured data because each value occupies a defined field with known rules. ](https://www.withsurface.com/glossary/example-of-structured-data) - [ Examples of Prompt EngineeringAI Search & Prompting Prompt engineering examples include classification, extraction, research, drafting, critique, tool use, and structured handoffs. ](https://www.withsurface.com/glossary/examples-of-prompt-engineering) - [ Features of Marketing AutomationMarketing Foundations Marketing automation features support segmentation, triggering, orchestration, messaging, scoring, routing, testing, governance, and measurement. ](https://www.withsurface.com/glossary/features-of-marketing-automation) - [ Five Types of Market ResearchAI Search & Prompting Five practical types of market research are secondary, qualitative, quantitative, observational, and experimental research, often combined in one study. ](https://www.withsurface.com/glossary/5-types-of-market-research) - [ Forms of Content MarketingMarketing Foundations Forms of content marketing are repeatable formats and experiences used to answer buyer questions, build trust, capture demand, and support customer decisions. ](https://www.withsurface.com/glossary/forms-of-content-marketing) - [ Generative AI Content MarketingMarketing Foundations Generative AI content marketing uses generative systems within a governed process for research, creation, adaptation, distribution, and learning. ](https://www.withsurface.com/glossary/generative-ai-content-marketing) - [ Go-to-Market TeamMarketing Foundations A go-to-market team is the cross-functional group responsible for bringing an offer to a defined market and turning customer evidence into coordinated growth. ](https://www.withsurface.com/glossary/go-to-market-team) - [ Goal of Market ResearchAI Search & Prompting The goal of market research is to reduce decision uncertainty with credible evidence about a market, buyer, alternative, offer, or outcome. ](https://www.withsurface.com/glossary/goal-of-market-research) - [ Good Market Research QuestionsAI Search & Prompting Good market research questions are specific, decision-linked, answerable with evidence, neutral about the outcome, and bounded by population and time. ](https://www.withsurface.com/glossary/good-market-research-questions) - [ Growth MarketingMarketing Foundations Growth marketing finds and improves repeatable ways to acquire, activate, retain, and expand customers through measured cross-channel experiments. ](https://www.withsurface.com/glossary/what-does-growth-marketing-do) - [ Growth Marketing DisciplineMarketing Foundations Growth marketing is a cross-functional discipline that uses customer evidence, lifecycle measurement, and controlled intervention to improve sustainable growth. ](https://www.withsurface.com/glossary/growth-marketing) - [ Growth Marketing StrategiesMarketing Foundations Growth marketing strategies use research, coordinated channel choices, experiments, and cohort economics to improve acquisition, activation, retention, expansion, or referral. ](https://www.withsurface.com/glossary/growth-marketing-strategies) - [ History of Marketing AutomationMarketing Foundations Marketing automation developed from database marketing and batch email into connected lifecycle, lead, customer, and revenue workflows. ](https://www.withsurface.com/glossary/marketing-automation-history) - [ Importance of Clean DataMarketing Foundations Clean data is important because routing, reporting, personalization, qualification, and automation depend on records that reflect reality closely enough for the action. ](https://www.withsurface.com/glossary/importance-of-clean-data) - [ Importance of Information GovernanceMarketing Foundations Information governance matters because organizations need consistent authority over how records, documents, data, and knowledge are created, used, protected, retained, and removed. ](https://www.withsurface.com/glossary/why-is-information-governance-important) - [ Importance of Market ResearchAI Search & Prompting Market research is important because it tests business assumptions against dated evidence before and after consequential market decisions. ](https://www.withsurface.com/glossary/importance-of-market-research) - [ Importance of Structured DataAI Search & Prompting Structured data is important because predictable fields and relationships let teams search, join, validate, report on, and automate business information. ](https://www.withsurface.com/glossary/why-is-structured-data-important) - [ Inbound Lead ManagementMarketing Foundations Inbound lead management governs how captured interest is validated, matched, qualified, routed, contacted, nurtured, and measured after a response. ](https://www.withsurface.com/glossary/inbound-lead-management) - [ Industry AnalysisAI Search & Prompting Industry analysis examines the structure, economics, participants, forces, and changes that shape competition within a defined market. ](https://www.withsurface.com/glossary/industry-analysis) - [ Inside Sales Lead GenerationMarketing Foundations Inside sales lead generation uses remote prospecting and response channels to identify, qualify, and create conversations with potential buyers. ](https://www.withsurface.com/glossary/inside-sales-lead-generation) - [ Lead Capture FormsMarketing Foundations Lead capture forms collect information from a prospect so a company can fulfill a request, qualify interest, route ownership, and continue communication. ](https://www.withsurface.com/glossary/lead-capture-forms) - [ Lead Generation Process FlowMarketing Foundations A lead generation process flow maps how attention becomes an identifiable record, a qualified response, an owned follow-up, and a measurable revenue outcome. ](https://www.withsurface.com/glossary/lead-generation-process-flow) - [ Lead Generation via Social MediaMarketing Foundations Social media lead generation uses social content, conversation, advertising, events, and direct response paths to create identifiable buyer interest. ](https://www.withsurface.com/glossary/lead-generation-social-media-marketing) - [ Lead Generation vs. Demand GenerationMarketing Foundations Demand generation builds and shapes market interest, while lead generation captures identifiable interest for qualification, routing, and follow-up. ](https://www.withsurface.com/glossary/lead-generation-vs-demand-generation) - [ Lead Generation WebsiteMarketing Foundations A lead generation website attracts a defined audience and turns appropriate interest into identifiable, qualified, and actionable demand. ](https://www.withsurface.com/glossary/lead-generation-web-site) - [ Lifecycle MarketingMarketing Foundations Lifecycle marketing coordinates messages and experiences around a person's changing relationship with a company, from first interest through retention and expansion. ](https://www.withsurface.com/glossary/lifecycle-marketing) - [ Lifecycle Marketing CampaignsMarketing Foundations Lifecycle marketing campaigns coordinate messages and actions around a person's or account's current relationship, behavior, and next useful step. ](https://www.withsurface.com/glossary/lifecycle-marketing-campaigns) - [ Lifecycle Marketing ProcessMarketing Foundations A lifecycle marketing process coordinates data, messages, handoffs, and measurement around changes in a person's or account's relationship with a company. ](https://www.withsurface.com/glossary/lifecycle-marketing-process) - [ Market Analysis ComponentsAI Search & Prompting A market analysis includes a market definition, buyers, demand, segments, competitors, substitutes, channels, economics, forces, risks, and implications for a stated decision. ](https://www.withsurface.com/glossary/what-does-a-market-analysis-include) - [ Market InformationAI Search & Prompting Market information is the collected evidence businesses use to understand customers, competitors, demand, pricing, channels, and external conditions. ](https://www.withsurface.com/glossary/market-information) - [ Market Research and IntelligenceAI Search & Prompting Market research and intelligence combine focused studies with ongoing evidence collection to support market, customer, competitor, and product decisions. ](https://www.withsurface.com/glossary/market-research-and-intelligence) - [ Market Research and Product DevelopmentAI Search & Prompting Market research supports product development by testing the audience, problem, alternatives, value, buying context, and launch conditions around a product decision. ](https://www.withsurface.com/glossary/market-research-and-product-development) - [ Market Research for Product DevelopmentAI Search & Prompting Market research for product development studies demand, buyers, alternatives, value, pricing, and adoption conditions around a proposed product choice. ](https://www.withsurface.com/glossary/market-research-for-product-development) - [ Market Research MethodsAI Search & Prompting Market research methods are systematic ways to collect and analyze evidence about buyers, competitors, demand, and category conditions. ](https://www.withsurface.com/glossary/market-research-methods) - [ Market Research QuestionsAI Search & Prompting Market research questions define the uncertainties a study must investigate about a market, buyer, behavior, competitor, demand, or decision. ](https://www.withsurface.com/glossary/market-research-questions) - [ Market Research Questions for StartupsAI Search & Prompting Market research questions for startups should test the problem, buyer, current alternatives, urgency, willingness, acquisition path, constraints, and evidence that could disprove the plan. ](https://www.withsurface.com/glossary/market-research-questions-for-startups) - [ Market Research TechnologyAI Search & Prompting Market research technology supports respondent recruitment, data collection, analysis, evidence management, visualization, and research operations. ](https://www.withsurface.com/glossary/market-research-technology) - [ Market Share AnalysisAI Search & Prompting Market share analysis calculates and interprets a company's portion of a defined market using comparable revenue, units, customers, or another stated measure. ](https://www.withsurface.com/glossary/market-share-analysis) - [ Market Share ResearchAI Search & Prompting Market share research estimates a company's portion of defined category sales, units, customers, usage, or another measurable market total. ](https://www.withsurface.com/glossary/market-share-research) - [ Market SizeAI Search & Prompting Market size estimates the total demand, customers, units, or revenue available within a defined market and time period. ](https://www.withsurface.com/glossary/market-size) - [ Market Sizing ResearchAI Search & Prompting Market sizing research estimates the number of eligible buyers, units, transactions, or revenue within a defined market and period. ](https://www.withsurface.com/glossary/market-sizing-research) - [ Market StudyAI Search & Prompting A market study is a scoped investigation of a market's boundaries, buyers, demand, segments, competitors, channels, economics, constraints, and implications for a decision. ](https://www.withsurface.com/glossary/market-study) - [ Marketing and Sales CollaborationMarketing Foundations Marketing and sales collaboration is the ongoing work of coordinating market insight, demand creation, buyer handoffs, follow-up, and revenue learning. ](https://www.withsurface.com/glossary/marketing-and-sales-collaboration) - [ Marketing and Sales PlanMarketing Foundations A marketing and sales plan coordinates target markets, demand programs, buyer handoffs, sales activity, resources, timing, and revenue expectations. ](https://www.withsurface.com/glossary/marketing-and-sales-plan) - [ Marketing Automation ArchitectureMarketing Foundations Marketing automation architecture maps the systems, data, triggers, rules, integrations, controls, and outputs that execute automated marketing work. ](https://www.withsurface.com/glossary/marketing-automation-architecture) - [ Marketing Automation CampaignsMarketing Foundations Marketing automation campaigns are repeatable lifecycle programs that use customer state, behavior, timing, and rules to deliver or coordinate the next appropriate action. ](https://www.withsurface.com/glossary/marketing-automation-campaigns) - [ Marketing Automation for SaaSMarketing Foundations Marketing automation for SaaS coordinates messages, data changes, and handoffs around a subscription customer's lifecycle and product behavior. ](https://www.withsurface.com/glossary/marketing-automation-for-saas) - [ Marketing Automation for StartupsMarketing Foundations Marketing automation for startups standardizes a small set of repeatable growth workflows without outrunning limited data, staff, or process maturity. ](https://www.withsurface.com/glossary/marketing-automation-for-startups) - [ Marketing Automation GoalsMarketing Foundations Marketing automation goals state the business and customer outcomes a team expects automated workflows to improve and how it will measure them. ](https://www.withsurface.com/glossary/marketing-automation-goals) - [ Marketing Automation ImplementationMarketing Foundations Marketing automation implementation turns a lifecycle and campaign strategy into configured data, integrations, permissions, workflows, tests, ownership, and measurement. ](https://www.withsurface.com/glossary/marketing-automation-implementation) - [ Marketing Automation RequirementsMarketing Foundations Marketing automation requirements define the data, process, system, content, governance, and measurement conditions a workflow needs to operate safely. ](https://www.withsurface.com/glossary/marketing-automation-requirements) - [ Marketing Automation StrategyMarketing Foundations A marketing automation strategy defines where automated decisions and actions should move people or accounts through a lifecycle, under explicit data and governance rules. ](https://www.withsurface.com/glossary/marketing-automation-strategy) - [ Marketing Automation WorkflowMarketing Foundations A marketing automation workflow is a defined sequence of triggers, decisions, actions, timing rules, and measurements executed by software. ](https://www.withsurface.com/glossary/marketing-automation-workflow) - [ Marketing Growth StrategyMarketing Foundations A marketing growth strategy sets the audiences, market choices, growth constraints, channels, conversion system, and learning process used to create durable revenue growth. ](https://www.withsurface.com/glossary/marketing-growth-strategy) - [ Marketing Intelligence and Marketing ResearchAI Search & Prompting Marketing intelligence is ongoing market monitoring, while marketing research is a focused study designed to answer a defined decision question. ](https://www.withsurface.com/glossary/marketing-intelligence-and-marketing-research) - [ Marketing OperationsMarketing Foundations The people, processes, data, and tooling that make a marketing team run — the plumbing behind campaigns, routing, and reporting. ](https://www.withsurface.com/glossary/marketing-operations) - [ Marketing Operations ManagementMarketing Foundations Marketing operations management coordinates the people, processes, data, technology, budgets, and controls used to execute and measure marketing work. ](https://www.withsurface.com/glossary/marketing-operations-management) - [ Marketing Operations StrategyMarketing Foundations A marketing operations strategy defines how people, processes, data, and technology will support marketing priorities and measurable revenue work. ](https://www.withsurface.com/glossary/marketing-operations-strategy) - [ Marketing Research QuestionsAI Search & Prompting Marketing research questions translate a business decision into specific questions that evidence can answer about markets, buyers, messages, channels, and outcomes. ](https://www.withsurface.com/glossary/marketing-research-questions) - [ Marketing TacticsMarketing Foundations Marketing tactics are the specific actions, channels, offers, and executions used to carry out a marketing strategy for a defined audience and objective. ](https://www.withsurface.com/glossary/marketing-tactics) - [ MartechMarketing Foundations Martech is the collection of software, data, integrations, and operating practices used to plan, execute, and measure marketing. ](https://www.withsurface.com/glossary/martech) - [ Martech StackMarketing Foundations A martech stack is the connected set of marketing technologies, data models, integrations, workflows, and owners used to run marketing. ](https://www.withsurface.com/glossary/martech-stack) - [ Martech Stack OptimizationMarketing Foundations Martech stack optimization improves how marketing tools, data, workflows, costs, and ownership support the work a team has chosen to do. ](https://www.withsurface.com/glossary/martech-stack-optimization) - [ New Product Market ResearchAI Search & Prompting New product market research studies the audience, problem, alternatives, demand, concept, price, buying process, and early use around a proposed offering. ](https://www.withsurface.com/glossary/new-product-market-research) - [ Online Customer Acquisition StrategyMarketing Foundations An online customer acquisition strategy defines how a company will attract, convert, and learn from customers through digital channels under sustainable economics. ](https://www.withsurface.com/glossary/online-customer-acquisition-strategy) - [ Online Market ResearchAI Search & Prompting Online market research uses digital sources and internet-based methods to study buyers, competitors, demand, and market behavior. ](https://www.withsurface.com/glossary/online-market-research) - [ Online Market Research ProcessAI Search & Prompting The online market research process scopes a decision, selects digital sources and participants, collects and validates evidence, analyzes it, and records an accountable action. ](https://www.withsurface.com/glossary/online-market-research-process) - [ Online Marketing ResearchAI Search & Prompting Online marketing research uses digital recruitment, observation, sources, and tools to study audiences, markets, messages, channels, and buying behavior. ](https://www.withsurface.com/glossary/online-marketing-research) - [ Organization Schema MarkupAI Search & Prompting Organization schema markup identifies a company or institution and its stable public properties through structured data. ](https://www.withsurface.com/glossary/organization-schema-markup) - [ Podcast Structured DataAI Search & Prompting Podcast structured data describes a podcast series, episodes, audio files, publishers, dates, and related pages in machine-readable form. ](https://www.withsurface.com/glossary/podcast-structured-data) - [ Primary and Secondary Market ResearchAI Search & Prompting Primary market research gathers new evidence for a current question, while secondary market research analyzes evidence collected previously for another purpose. ](https://www.withsurface.com/glossary/primary-and-secondary-market-research) - [ Primary Market ResearchAI Search & Prompting Primary market research collects new evidence directly from customers, prospects, users, or observed market behavior for a business decision. ](https://www.withsurface.com/glossary/primary-market-research-in-business) - [ Primary Market Research MethodsAI Search & Prompting Primary market research gathers new evidence directly from participants or observed behavior to answer a specific market question. ](https://www.withsurface.com/glossary/primary-market-research) - [ Prompt Engineering for LLMsAI Search & Prompting The practice of writing inputs that get reliable, useful output from large language models — and why it now shapes how brands get found. ](https://www.withsurface.com/glossary/prompt-engineering-for-llms) - [ Prompt Engineering FrameworkAI Search & Prompting A prompt engineering framework is a repeatable structure for defining tasks, supplying evidence, constraining behavior, and evaluating outputs. ](https://www.withsurface.com/glossary/prompt-engineering-framework) - [ Prompt EvaluationAI Search & Prompting Prompt evaluation measures whether a prompt and its surrounding system produce correct, useful, safe, and repeatable behavior on representative cases. ](https://www.withsurface.com/glossary/prompt-evaluation) - [ Prompt TestingAI Search & Prompting Prompt testing compares prompt-system behavior across representative inputs, edge cases, and versions before and after release. ](https://www.withsurface.com/glossary/prompt-testing) - [ Prompt TuningAI Search & Prompting Prompt tuning can mean iterative prompt optimization or a model-training method that learns soft prompt vectors while model weights stay fixed. ](https://www.withsurface.com/glossary/prompt-tuning) - [ Prompt WritingAI Search & Prompting Prompt writing is the practice of specifying a model's task, context, constraints, inputs, and desired output clearly enough to evaluate. ](https://www.withsurface.com/glossary/prompt-writing) - [ Proven Lead Generation StrategiesMarketing Foundations Proven lead generation strategies are repeatable approaches supported by evidence from a defined audience, offer, channel, and sales process. ](https://www.withsurface.com/glossary/proven-lead-generation-strategies) - [ Quality Lead GenerationMarketing Foundations Quality lead generation creates identifiable responses with enough fit, intent, context, and timing for an appropriate next action. ](https://www.withsurface.com/glossary/quality-lead-generation) - [ Real-Time Market ResearchAI Search & Prompting Real-time market research collects and interprets current signals quickly enough to inform a decision while the relevant market condition is still changing. ](https://www.withsurface.com/glossary/real-time-market-research) - [ Real-Time Marketing AutomationMarketing Foundations Real-time marketing automation responds to a current event or state within a defined latency, using eligibility, context, and suppression rules. ](https://www.withsurface.com/glossary/real-time-marketing-automation) - [ Recommended Format for Schema MarkupAI Search & Prompting JSON-LD is usually the recommended format for schema markup because it separates structured data from visible page code and is easier to maintain. ](https://www.withsurface.com/glossary/recommended-format-for-implementing-schema-markup) - [ Research and Market IntelligenceAI Search & Prompting Research and market intelligence turn evidence about buyers, competitors, categories, and change into decisions a business can revisit. ](https://www.withsurface.com/glossary/research-and-market-intelligence) - [ Revenue Marketing StrategyMarketing Foundations A revenue marketing strategy connects market choice, demand creation, buyer conversion, customer growth, and marketing investment to revenue outcomes. ](https://www.withsurface.com/glossary/revenue-marketing-strategy) - [ Rich Snippets and Schema MarkupAI Search & Prompting Schema markup supplies structured facts, while rich snippets are enhanced search-result presentations a search engine may choose to show. ](https://www.withsurface.com/glossary/rich-snippets-and-schema-markup) - [ Sales and Marketing AlignmentMarketing Foundations Sales and marketing alignment is shared agreement and operating practice around buyers, qualification, ownership, handoffs, evidence, and revenue outcomes. ](https://www.withsurface.com/glossary/sales-and-marketing-alignment) - [ Sales and Marketing OperationsMarketing Foundations Sales and marketing operations coordinate the shared processes, data, systems, handoffs, and measurement that move demand into pipeline and revenue. ](https://www.withsurface.com/glossary/sales-and-marketing-operations) - [ Sales Lead FormMarketing Foundations A sales lead form captures the minimum information needed to respond to a prospective buyer, establish context, and route the request safely. ](https://www.withsurface.com/glossary/sales-lead-form) - [ Schema DataAI Search & Prompting Schema data is structured information organized under defined properties and relationships so machines can identify what a page or record represents. ](https://www.withsurface.com/glossary/schema-data) - [ Schema in Digital MarketingAI Search & Prompting Schema in digital marketing is a shared vocabulary that makes page entities and facts easier for search systems to interpret. ](https://www.withsurface.com/glossary/schema-in-digital-marketing) - [ Schema MarkupAI Search & Prompting Schema markup means adding a standardized layer of structured facts to a web page so machines can interpret its entities and relationships. ](https://www.withsurface.com/glossary/schema-markup) - [ Schema Markup for ReviewsAI Search & Prompting Review schema markup describes a genuine review or aggregate rating in structured data so eligible search systems can interpret it accurately. ](https://www.withsurface.com/glossary/schema-markup-for-reviews) - [ Scrubbing DataMarketing Foundations Scrubbing data means detecting and correcting errors, duplicates, inconsistencies, and unusable records so a dataset can support a defined task. ](https://www.withsurface.com/glossary/scrubbing-data) - [ Search VolumeAI Search & Prompting Search volume estimates how often a query is searched within a market and time period, usually as an average monthly count. ](https://www.withsurface.com/glossary/search-volume) - [ Secondary Market ResearchAI Search & Prompting Secondary market research analyzes evidence that already exists, including public data, prior studies, company records, filings, reviews, and published sources. ](https://www.withsurface.com/glossary/secondary-market-research) - [ SEO Analytics ReportingMarketing Foundations SEO analytics reporting connects search visibility and site behavior with page quality, conversion, and business outcomes. ](https://www.withsurface.com/glossary/seo-analytics-reporting) - [ SEO Automated ReportingMarketing Foundations SEO automated reporting collects, transforms, and distributes search-performance data on a schedule while preserving definitions, quality checks, and business context. ](https://www.withsurface.com/glossary/seo-automated-reporting) - [ Steps in the Marketing Research ProcessAI Search & Prompting The marketing research process turns a decision and evidence gap into a study, analysis, recommendation, and documented learning cycle. ](https://www.withsurface.com/glossary/steps-in-marketing-research-process) - [ Strategic Market ResearchAI Search & Prompting Strategic market research reduces uncertainty around consequential choices such as market entry, segmentation, positioning, product direction, and pricing. ](https://www.withsurface.com/glossary/strategic-market-research) - [ Strategies for Sales and MarketingMarketing Foundations Strategies for sales and marketing coordinate market selection, positioning, demand creation, buyer conversion, account work, and revenue learning. ](https://www.withsurface.com/glossary/strategies-for-sales-and-marketing) - [ Structured DataAI Search & Prompting Structured data is information organized through a defined schema so values and relationships can be processed consistently. ](https://www.withsurface.com/glossary/structured-data) - [ Structured Data AnalysisAI Search & Prompting Structured data analysis uses defined records and fields to calculate patterns, compare groups, test relationships, and support repeatable decisions. ](https://www.withsurface.com/glossary/structured-data-analysis) - [ Structured Data AnalyticsMarketing Foundations Structured data analytics examines defined records and fields to measure patterns, performance, relationships, and change. ](https://www.withsurface.com/glossary/structured-data-analytics) - [ Structured Data FormatsAI Search & Prompting Structured data formats organize values and relationships under explicit syntax and rules so systems can exchange and interpret information consistently. ](https://www.withsurface.com/glossary/structured-data-formats) - [ Structured Data in JSON-LDAI Search & Prompting JSON-LD is a script-based format for expressing structured entities, properties, and relationships on web pages. ](https://www.withsurface.com/glossary/structured-data-json-ld) - [ Structured Data in SEOAI Search & Prompting Structured data in SEO is machine-readable page information that clarifies entities, attributes, and relationships for search systems. ](https://www.withsurface.com/glossary/structured-data-in-seo) - [ Structured Data ManagementMarketing Foundations Structured data management governs how defined records are created, validated, stored, changed, shared, and retired across business systems. ](https://www.withsurface.com/glossary/structured-data-management) - [ Structured Data SetAI Search & Prompting A structured data set is a collection of records that share defined fields, types, identifiers, and relationships. ](https://www.withsurface.com/glossary/structured-data-set) - [ Structured Data TypesAI Search & Prompting Structured data types define the allowed shape and meaning of values, records, or entities so systems can process them consistently. ](https://www.withsurface.com/glossary/structured-data-types) - [ Structured Data ValidationAI Search & Prompting Structured data validation checks whether records follow expected syntax, types, required fields, allowed values, and business relationships. ](https://www.withsurface.com/glossary/structured-data-validation) - [ Structured DatabaseAI Search & Prompting A structured database stores data under an explicit schema of records, fields, types, constraints, and relationships so systems can query it consistently. ](https://www.withsurface.com/glossary/structured-database) - [ Structured vs. Unstructured DataAI Search & Prompting Structured data follows a defined schema, while unstructured data carries meaning without fixed fields, rows, or relationships. ](https://www.withsurface.com/glossary/structured-vs-unstructured-data) - [ Survey in Market ResearchAI Search & Prompting A market research survey collects standardized self-reported responses from a defined sample so a team can estimate or compare attitudes, experiences, characteristics, or intentions. ](https://www.withsurface.com/glossary/survey-in-market-research) - [ Technology Content MarketingMarketing Foundations Technology content marketing explains technical problems, products, tradeoffs, and implementation choices for buyers and users through useful evidence. ](https://www.withsurface.com/glossary/technology-content-marketing) - [ Three Types of Prompt EngineeringAI Search & Prompting Zero-shot, one-shot, and few-shot prompting are three common ways to vary how many examples a model receives with its instruction. ](https://www.withsurface.com/glossary/three-types-of-prompt-engineering) - [ Types of Business ResearchAI Search & Prompting Different types of business research can be organized by source, method, purpose, time horizon, and the kind of decision they are meant to improve. ](https://www.withsurface.com/glossary/different-types-of-business-research) - [ Types of CompetitorsAI Search & Prompting Types of competitors group the companies, alternatives, and existing habits that can win the same buyer decision or budget. ](https://www.withsurface.com/glossary/types-of-competitors) - [ Types of Lead GenerationMarketing Foundations The main types of lead generation include inbound, outbound, paid, partner, event, referral, product-led, and customer-led motions, each with different economics and handoffs. ](https://www.withsurface.com/glossary/types-of-lead-generation) - [ Types of Market Research SurveysAI Search & Prompting Types of market research surveys include awareness, segmentation, needs, concept, pricing, satisfaction, brand, and purchase-intent studies. ](https://www.withsurface.com/glossary/types-of-market-research-surveys) - [ Types of MarketingMarketing Foundations The main categories of marketing — from content and inbound to paid, outbound, and product-led — and when each one earns its place in a GTM plan. ](https://www.withsurface.com/glossary/types-of-marketing) - [ Types of Marketing AutomationMarketing Foundations Types of marketing automation group recurring workflows for acquisition, nurturing, lifecycle communication, handoffs, data, and measurement. ](https://www.withsurface.com/glossary/types-of-marketing-automation) - [ Types of PromptingAI Search & Prompting Types of prompting group prompt patterns by the evidence, examples, reasoning structure, tools, or output controls they provide. ](https://www.withsurface.com/glossary/types-of-prompting) - [ Zero-Click ContentAI Search & Prompting Zero-click content gives an audience useful information inside the channel where it appears, even when the person never visits the publisher's site. ](https://www.withsurface.com/glossary/zero-click-content) --- # Five Types of Market Research | Surface Glossary URL: https://surface.thesurface.network/glossary/5-types-of-market-research Five practical types of market research are secondary research, qualitative research, quantitative research, observational research, and experimental research. This grouping separates the evidence teams use and the claims each method can support. Other taxonomies divide research into primary and secondary, or into exploratory, descriptive, and causal work. The labels are useful only when the method and decision are stated. Most business questions need more than one type. Secondary sources can frame a market before interviews explain buyer language. A survey can estimate how common a need is, behavioral observation can test whether stated preferences match action, and an experiment can compare responses under controlled conditions. Combining methods does not repair a weak sample or a poorly framed question, so each part still needs its own quality standard. Treat the five types as a sequence of evidence choices rather than five boxes to fill on every project. Start with the uncertainty around a decision. Then choose the earliest method that can reduce that uncertainty at a reasonable cost. Later methods should test a specific gap left by earlier evidence. Preserve the connection between every finding and its source so a final recommendation does not flatten different levels of certainty. 1. Scan secondary evidence. Review existing studies, public filings, government data, prior customer research, search behavior, reviews, and internal records. Record dates, market definitions, sampling choices, and conflicts between sources. Secondary work establishes context and prevents the team from asking participants questions that existing evidence already answers. 2. Use qualitative research for discovery. Interviews, focus groups, open responses, and diary studies can reveal language, sequence, motivations, objections, and unexpected alternatives. Recruit people with direct experience of the decision. The result supports themes and hypotheses, not population percentages. 3. Use quantitative research for measurement. Surveys and structured datasets estimate incidence, differences, or relationships across a defined population. Write the analysis plan before fielding, use neutral questions, and report the base for every percentage. Sampling and nonresponse matter more than a visually impressive respondent count. 4. Observe behavior where memory or hypothetical answers are unreliable. Product analytics, purchase records, usability sessions, call analysis, and field observation show what people did under particular conditions. Check instrumentation, identity, missing events, and whether the observed group represents the intended market. 5. Run experimental research when the decision depends on causal comparison. Randomized tests, controlled concept tests, or carefully designed field experiments vary one condition and compare outcomes. Define the unit, exposure, outcome, stopping rule, and practical effect before looking at the result. Research quality can be assessed through source freshness, sample fit, completion, instrument consistency, traceability, missingness, contradictory evidence, and relevance to the decision. A project should also record how much the evidence changed the original view. If every method merely confirms the sponsor's first opinion, the review process may be filtering out inconvenient material. Create a research record with the decision, question, method, population, recruitment, instrument version, field dates, raw source location, analysis choices, owner, and reviewer. Label observations, interpretations, estimates, and causal claims separately. Quotations should retain participant context, while percentages should retain their denominator. When one method conflicts with another, document the conflict and decide whether the difference comes from population, timing, wording, behavior, or measurement error. - Which business decision will the research change? - What type of claim is required: discovery, estimate, behavioral description, or causal effect? - Which population, market boundary, and period apply? - How will consent, privacy, incentives, and access to raw material be handled? - Who can challenge the method and the sponsor's interpretation? Budget should follow uncertainty and consequence. A low-risk copy choice may need a small qualitative check, while market entry or pricing can justify several methods and outside review. Decide the minimum evidence required before collection begins, then state which unresolved questions remain after the project. A common failure is calling five data sources five types of research. Ten articles, two dashboards, and a competitor spreadsheet may all be secondary evidence. The apparent variety hides the same blind spot, and a polished deck gives weak triangulation more authority than it deserves. Another version uses a survey to ask respondents to predict behavior they have never experienced. Return to the decision and classify each claim by the evidence it needs. Add a method that addresses the missing perspective, narrow claims that exceed the sample, and expose disagreement between sources. A smaller conclusion with traceable support is more useful than a broad answer built from incompatible evidence. --- # Acquisition in Marketing | Surface Glossary URL: https://surface.thesurface.network/glossary/acquisition-in-marketing Acquisition in marketing is the set of activities used to gain new customers, users, subscribers, leads, or accounts. It spans demand creation, demand capture, channel selection, offers, landing experiences, lead operations, sales handoffs, onboarding, and measurement of the cost and value of new relationships. The acquisition event depends on the business. A consumer app may use activated users, while a B2B company may distinguish lead, meeting, opportunity, and new customer. Teams should avoid calling an email address a customer acquisition when several expensive stages remain. Define the target segment and terminal acquisition event, then map the path and economics backward. Choose channels from buyer behavior, instrument identity and source, reduce conversion friction, qualify appropriately, and align response with intent. Compare cohorts through value and payback, not volume alone. 1. Choose the customer, segment, geography, product, and acquisition event. Document intermediate conversions so teams do not optimize a proxy without seeing the final outcome. 2. Estimate unit economics and capacity. Include media, content, tools, people, sales effort, onboarding, discounts, and the time required to recover the cost. 3. Select channels and offers based on where the audience learns and decides. Assign each channel a job across awareness, evaluation, capture, or direct response. 4. Build the conversion and handoff system. Preserve context, qualify without unnecessary friction, route quickly, and align marketing promises with sales and onboarding. 5. Measure by cohort and feed outcomes back into targeting, creative, offer, product, and operations. Separate attribution from evidence that the activity caused incremental growth. Common measures include customer acquisition cost, cost per qualified lead or meeting, conversion by stage, payback period, lifetime value, retention, expansion, and incremental lift. Attribution reports help explain paths but should not automatically be treated as causal proof. The operating discipline for acquisition in marketing is a chain from question to source to interpretation to decision. Preserve interview notes, survey instruments, queries, public records, and dated product evidence with enough context to audit the conclusion. Add a confidence statement and the observation that would reverse the recommendation. This avoids the familiar research failure where a clean slide outlives the evidence and continues to guide positioning after the market has changed. Keep the smallest useful scope for acquisition in marketing until the operation has evidence to expand. Limit templates, segments, permissions, channels, or actions at first. Review errors and manual work, then add scope deliberately. This makes ownership and rollback practical and gives the team a baseline against which a broader version can be judged. The final artifact should show the current decision, the evidence behind it, and the condition that forces reconsideration. That is what makes acquisition in marketing maintainable after the original operator moves to another project. Retirement belongs in the operating plan for acquisition in marketing too. Define the signal that shows the process no longer serves its original audience, system, category, or decision. Archive the configuration and evidence, stop new entries safely, preserve required history, and update dependent reports or links. Unused processes create risk when they remain active simply because no one owns turning them off. Record where acquisition in marketing remains uncertain and when that uncertainty becomes material. This gives the next operator a starting point instead of forcing another full audit. - Which event counts as acquisition for planning and finance? - Which segment and channel economics support sustainable growth? - Which proxy metrics are allowed, and how will they reconcile with customers and revenue? - Who owns the handoff from marketing through sales and onboarding? - Which experiment can test incremental acquisition rather than platform credit alone? Acquisition is a business system with constraints. A channel can generate more customers than the onboarding team can support, or lower lead costs by moving toward a segment with poor retention. The operating plan should include those downstream effects. A common failure is optimizing cost per lead as if every lead has equal expected value. Campaigns move toward cheap responses, sales acceptance falls, and the company spends more time processing weak demand. The dashboard improves while payback worsens. Rebuild reporting around qualified cohorts, meetings, opportunities, customers, and retention. Review channel incrementality where possible, include full operating cost, and change targeting or capture rules when low-cost demand creates downstream waste. --- # Advanced Prompt Engineering | Surface Glossary URL: https://surface.thesurface.network/glossary/advanced-prompt-engineering Advanced prompt engineering covers prompt systems with several moving parts: retrieved context, tool calls, multiple stages, structured outputs, memory, routing, evaluation, and approval gates. The sophistication comes from system design and testing, not from writing a longer or more theatrical instruction. A production workflow may classify a request, retrieve approved records, choose a specialist prompt, call a tool, draft an action, and send the proposal to a reviewer. Each stage has a narrower job and its own failure conditions. That structure is easier to test than a single prompt expected to make every decision at once. Advanced techniques become useful when errors have different causes or consequences. Retrieval addresses missing facts. Tool use accesses current systems. Output schemas protect downstream parsing. Evaluations reveal regressions. Permissions and approvals limit the impact of a plausible but incorrect answer. Design the workflow as a sequence of observable states. Version prompts and data sources independently, record which model and tool produced each result, and keep a test set that includes missing data, conflicting evidence, prompt injection, unauthorized actions, and expected escalation. Expand authority only after the narrower workflow behaves reliably. Use advanced prompt engineering inside a defined task rather than as an isolated piece of prose. Save the input, approved context, desired output, model, and test cases beside the prompt so later edits can be compared. Keep the source beside the result and make changes reversible. This protects the operation when a definition, vendor, model, template, or buyer behavior changes after the original decision. The final review should ask what changed for a buyer or operator. If advanced prompt engineering only creates another field, page, prompt, or dashboard, its role remains incomplete. A marketing agent reviews weekly campaign performance. One stage retrieves approved spend and pipeline tables. Another calculates changes through deterministic code. A model explains material anomalies and drafts two actions, but it cannot change a budget. The channel owner sees the evidence, approves one action, and the execution system records the result. The most advanced workflow often looks restrained. Each prompt does one job, evidence stays visible, and the system knows when to stop. Complexity should buy measurable reliability or capability rather than make the demo look impressive. --- # Advantages of Market Research | Surface Glossary URL: https://surface.thesurface.network/glossary/advantages-of-market-research The advantages of market research come from reducing uncertainty around a specific business choice. Research can clarify who has a problem, how people describe it, which alternatives they use, what evidence they trust, how large a market may be, and where a proposed offer creates friction. It can also reveal that a favored plan lacks support before the company commits more money. Teams use research during market selection, product development, positioning, pricing, campaign planning, sales enablement, and customer retention. The benefit depends on timing. Evidence collected after a launch may explain performance, while evidence collected before an irreversible investment may help the company change direction at much lower cost. Good research makes assumptions visible and gives people a shared basis for disagreement. It can uncover segments hidden by aggregate data, replace internal wording with customer language, expose unknown competitors, and estimate the range of plausible demand. Research also creates a record of what the team believed at a date, which helps later reviewers distinguish a poor decision from a reasonable decision made with limited evidence. The work has limits. A convenient sample can misrepresent the market, stated intent can differ from behavior, and an old study can remain persuasive after its context expires. Research rarely removes uncertainty entirely. Its advantage is a better-calibrated decision, with the remaining unknowns and the cost of being wrong stated plainly. Start by writing the decision, the current assumption, and what evidence would change it. Select a method suited to the claim, recruit the relevant population, and keep sources traceable. In the final output, separate observation from interpretation and recommendation. Assign an owner to the decision and a date for review. The research has done its job when the team can explain what changed and why. A software company plans to enter healthcare because several inbound leads requested compliance features. Interviews reveal that the requests come from consultants, while intended buyers need certifications the product will not have for a year. Secondary estimates also show a longer sales cycle than the model assumed. The company postpones a broad launch and runs a smaller partner test, avoiding a costly hiring plan built on a handful of leads. Market research is most useful when it changes the quality, timing, or scope of a real decision, including the decision to stop. --- # Advertising Market Research | Surface Glossary URL: https://surface.thesurface.network/glossary/advertising-market-research Advertising market research collects evidence to improve advertising decisions before, during, and after a campaign. It can study audience needs, media habits, message comprehension, creative response, brand recall, consideration, conversion, sales impact, and whether exposure caused an outcome that would not otherwise have occurred. Different methods answer different questions. Interviews and concept testing can expose confusing language. Platform results show delivery and observed response. Brand studies estimate changes in awareness or consideration. Controlled experiments and geographic tests can estimate incremental effect. One dashboard should not collapse those outcomes into a single claim of performance. Teams often optimize the metric a platform can report most easily. Click-through rate may favor curiosity over qualified intent, while attributed conversions may include people who would have purchased anyway. Research widens the evidence and connects creative, audience, delivery, and business effect. Define the decision and success measure before fielding or launch. Separate diagnostic metrics from outcomes, preserve creative and audience versions, and record exposure windows. Use representative research samples for market claims and experiments for causal claims. Pair aggregate performance with qualitative evidence from buyers who understood, ignored, or rejected the message. Review the full chain: whom the campaign reached, what they understood, what action followed, whether the response met sales or customer criteria, and how results compared with a credible baseline. Segment by audience and creative where sample size supports it. Keep platform attribution labels clear and report uncertainty rather than forcing agreement between incompatible models. A software company tests two messages before a launch. Buyers understand the efficiency message but distrust its broad claim; the control message about review and auditability earns lower stated excitement and stronger purchase relevance. The company runs a controlled paid test, then finds that the narrower message produces fewer clicks and more qualified opportunities. Advertising research should change a media, audience, creative, or measurement decision. Attractive recall alone is not the finish line. --- # AI Content Brief | Surface Glossary URL: https://surface.thesurface.network/glossary/ai-content-brief ## What is an AI content brief? An AI content brief is a content brief created or enriched with help from an AI system. The model may cluster audience questions, summarize approved research, compare existing pages, suggest structure, identify internal-link opportunities, or format requirements. The brief still needs a human decision about why the asset should exist and what it should say. A model can infer a plausible page from a keyword, yet plausible is a low bar. It does not automatically know the company's product truth, expert view, customer evidence, conversion path, editorial standards, or what the existing archive already covers. Those inputs determine whether the brief produces useful content or another generic page. ## Why an AI content brief matters Brief creation can become a research bottleneck, especially across a large program. AI reduces mechanical synthesis and makes it easier to compare many sources. The same speed can multiply weak assumptions, invented recommendations, and nearly identical outlines when the input is thin or the output receives no editorial judgment. Give the model a governed source pack and a defined task. Include audience, intent, business job, primary evidence, product constraints, competing pages, existing internal links, desired conversion, claims requiring review, and exclusions. Ask it to preserve source locations and mark uncertainty instead of filling gaps. ## How to use an AI content brief in practice Evaluate the brief before drafting. Check whether it names a specific reader decision, makes the company's point of view clear, separates facts from proposed argument, avoids duplicate page ownership, and supplies material a writer can verify. Store the source version, prompt, model, editor, and revision date when the process needs repeatability. A content operator supplies customer interviews, a product definition, search questions, sales objections, and the current hub map. AI groups the evidence and proposes two structures. The editor rejects one because it repeats a comparison page, keeps the stronger angle, adds an implementation expert, and marks three claims for product review. AI improves a content brief when it organizes better evidence and exposes choices. It cannot supply the missing strategic decision by itself. --- # AI Content Marketing Strategy | Surface Glossary URL: https://surface.thesurface.network/glossary/ai-content-marketing-strategy ## What is an AI content marketing strategy? An AI content marketing strategy explains how a company will use AI to attract, educate, convert, and retain an audience through content. It connects AI-assisted research and production to topic priorities, brand point of view, search and AI visibility, distribution, internal enablement, conversion paths, and performance feedback. The extra word marketing matters. A workflow that produces articles quickly is a production system. A content marketing strategy has to decide who should find those articles, what the company needs them to understand, which next page or action is useful, and how the team will learn from the response. ## Why an AI content marketing strategy matters AI reduces the cost of producing acceptable drafts, which makes selection and connection more important. Teams can publish a large archive that earns scattered impressions yet never establishes a memorable category position. Strategy concentrates effort on a smaller set of business-relevant questions and uses AI to support the operation around them. Build a topic and audience map, choose pillar and supporting assets, record approved sources, and define where human interpretation enters the workflow. Plan distribution and sales use before publication. Measure rankings, AI citations, engagement, conversion, assisted pipeline, and sales feedback as different signals rather than compressing them into one visibility score. ## How to use an AI content marketing strategy in practice A useful application of an AI content marketing strategy separates observed facts, participant reports, modeled estimates, and internal interpretation. Those forms of evidence can inform the same decision without being treated as equivalent. Keep the source beside the result and make changes reversible. This protects the operation when a definition, vendor, model, template, or buyer behavior changes after the original decision. The final review should ask what changed for a buyer or operator. If an AI content marketing strategy only creates another field, page, prompt, or dashboard, its role remains incomplete. A company launching a workflow product uses AI to analyze call transcripts and group objections. The team chooses one objection as a quarterly theme, builds a guide and supporting pages, turns the strongest evidence into email and sales material, and updates the cluster when product and buyer language change. AI handles summarization and adaptation, while people own the argument and proof. The strategy succeeds when content creates a clearer market position and a better buyer path. A higher draft count is useful only when the team can review, publish, connect, distribute, and measure the extra work. --- # AI Content Strategy | Surface Glossary URL: https://surface.thesurface.network/glossary/ai-content-strategy ## What is an AI content strategy? An AI content strategy is a plan for using AI across research, planning, creation, review, distribution, and measurement while protecting factual quality, brand judgment, and business purpose. It defines which work can be accelerated, which decisions require people, and which evidence the system may use. The strategy should begin with audience and business problems rather than a tool inventory. AI can summarize calls, cluster topics, create outline options, transform formats, or check a draft against a brief. None of those tasks decides what the company believes, which claim deserves emphasis, or whether a page should exist. ## Why an AI content strategy matters Without a strategy, faster drafting usually produces a larger review queue and a more repetitive site. Teams gain output while losing source discipline and voice. A clear operating model directs AI toward tool work, keeps human interpretation visible, and connects publishing to search, sales, conversion, and measurement. Map the content workflow and assign an authority level to each stage. Give research agents approved sources, make briefs capture the human interpretation of the evidence, require factual and editorial review, and track content at the page and cluster level. Preserve prompt versions and source notes for repeatable work. ## How to use an AI content strategy in practice Operational use of an AI content strategy requires more than publication. Assign its source material, reviewer, related pages, channel adaptations, sales use, success signals, and owner for factual updates. Set an explicit review trigger rather than relying on memory. A product launch, schema change, prompt revision, new data source, campaign shift, or sales objection may justify a fresh check. The practical test for an AI content strategy is whether it improves a real decision without creating hidden definitions, unsupported confidence, or an unowned handoff to another team. A content team uses AI to transcribe interviews, group recurring buyer questions, and draft three outline options. The content lead chooses the argument and writes the point-of-view section. A model produces a first draft from approved notes, while an editor verifies claims, rewrites the opening, adds internal links, and decides the conversion path. The goal is a better content operation with AI inside it. Production speed matters only when the team can still explain why the piece exists, where its claims came from, and what useful action should follow. --- # AI Data Cleansing | Surface Glossary URL: https://surface.thesurface.network/glossary/ai-data-cleansing AI data cleansing uses machine learning or language models to identify likely duplicates, standardize messy text, classify values, infer relationships, flag anomalies, and suggest missing information. It is especially useful when business data contains spelling variation, free text, uncertain company names, or patterns that fixed rules cannot describe easily. The model should add judgment where deterministic validation stops. Exact email formatting, date parsing, and allowed country codes remain rule-based jobs. Fuzzy account matching and title normalization may benefit from a model, but those outputs need confidence, provenance, and an exception path. AI can reduce manual review across large datasets, yet it can also make uncertain guesses look clean. A plausible company match may attach a lead to the wrong account and change ownership, attribution, and pipeline. The cost of an error depends on the action that follows. Use AI to propose a cleaned value or match, keep the source beside it, record the model and rule version, and set thresholds by consequence. Auto-accept low-risk standardization, review identity changes and high-value accounts, and measure reversals after people inspect the results. Prioritize AI data cleansing by consequence. Identity, consent, ownership, account relationships, lifecycle, and revenue fields usually need stricter controls than optional profile attributes that do not trigger action. Keep the source beside the result and make changes reversible. This protects the operation when a definition, vendor, model, template, or buyer behavior changes after the original decision. The final review should ask what changed for a buyer or operator. If AI data cleansing only creates another field, page, prompt, or dashboard, its role remains incomplete. A lead file contains job titles such as VP Mktg, Marketing Vice President, and Head of Growth. A model maps them into a normalized role family and seniority level, with a confidence score and explanation. High-confidence labels support segmentation. Ambiguous titles remain unknown until another source or reviewer resolves them. AI cleansing works best as a visible suggestion layer. It should increase usable structure without pretending the source was more certain than it was. --- # AI SEO Strategy | Surface Glossary URL: https://surface.thesurface.network/glossary/ai-seo-strategy An AI SEO strategy is a plan for earning discovery across traditional search results and AI-generated search experiences. It combines crawlable technical foundations, useful content, clear entities, source-worthy evidence, topic coverage, internal links, and measurement of how the brand appears in generated answers. The term can also refer to using AI inside an SEO workflow. That is a separate operating question. AI may help cluster queries, summarize search results, draft briefs, detect content gaps, or analyze reports. The strategy still needs human decisions about audience, business priority, evidence, voice, and what the company can credibly own. Search behavior now includes queries that produce summaries, comparisons, citations, recommendations, and follow-up questions before a buyer visits a site. A strategy built only around ten blue links misses part of that path. A strategy built only around AI mentions ignores the search infrastructure that often supplies the underlying sources. Map buyer questions by intent, then build connected page groups that include definitions, comparisons, implementation guidance, proof, and conversion paths. Track classic rankings and clicks alongside AI mentions, citations, source inclusion, competitor presence, and assisted business outcomes. Refresh claims that age quickly and keep important pages easy to crawl and quote accurately. The review for an AI SEO strategy should separate what the company controls from what an engine chooses. Teams control page quality, crawlability, structure, evidence, and freshness, while presentation and citation remain external outcomes. Keep the source beside the result and make changes reversible. This protects the operation when a definition, vendor, model, template, or buyer behavior changes after the original decision. The final review should ask what changed for a buyer or operator. If an AI SEO strategy only creates another field, page, prompt, or dashboard, its role remains incomplete. A B2B company wants visibility for a new software category. It publishes one category guide, several pages answering narrow evaluation questions, a transparent competitor comparison, customer proof, and a clear product page. It monitors whether AI systems mention the brand across a stable prompt set, which sources they cite, and whether the same topic cluster earns qualified organic visits. AI SEO is strongest when it broadens the measurement surface without abandoning SEO basics. Citation share, ranking position, and pipeline influence are related signals, but none should stand in for the others. --- # Automated Data Cleansing | Surface Glossary URL: https://surface.thesurface.network/glossary/automated-data-cleansing Automated data cleansing uses software rules, reference data, and sometimes machine-learning models to detect and resolve data-quality problems. It can standardize formats, validate required fields, flag outliers, match duplicates, map values, enrich records, or route uncertain cases to an exception queue. The word automated describes execution, not certainty. Formatting a phone number is usually low risk. Reassigning an account, merging people, inferring consent, or rewriting a lifecycle stage can affect customer communication and revenue reporting. Those actions need stronger evidence, provenance, and human review. Lead and customer data changes too quickly for occasional cleanup projects. New forms, imports, integrations, enrichment vendors, and manual edits introduce defects every day. Automation can contain recurring problems near their source, provided the team knows which corrections are reversible and which require approval. Classify rules by consequence. Apply deterministic, reversible fixes automatically; use confidence thresholds for inferred changes; and quarantine records when required evidence is absent or conflicting. Preserve the original value, rule version, source, timestamp, proposed value, and reviewer. Monitor how often each rule fires and whether downstream teams overturn the result. Build a representative test set before enabling write access. Include missing values, multilingual names, shared domains, subsidiaries, stale enrichment, recent job changes, and records that should remain separate. Run new rules in observation mode first, compare suggestions with known outcomes, then expand the action scope gradually. A demo form sends job titles in hundreds of variations. A cleansing workflow standardizes obvious abbreviations, maps high-confidence titles into role bands, and leaves ambiguous titles unchanged. It blocks disposable emails, preserves submitted values, and routes possible account matches to review instead of merging them immediately. Automated cleansing works when the system knows when to correct, when to suggest, and when to leave a record unresolved. Measure exception volume and reviewer reversals as closely as the number of records processed, since those cases reveal where the rules have exceeded their evidence. --- # Automated Marketing Campaigns | Surface Glossary URL: https://surface.thesurface.network/glossary/automated-marketing-campaigns Automated marketing campaigns are campaigns in which software executes repeatable actions according to schedules, events, audience rules, and customer data. The automation may send messages, update audiences, create tasks, change bids, personalize pages, route responses, or coordinate several channels around a campaign state. Automation can control one step or most of the execution. A scheduled newsletter is lightly automated. An event program that changes ads, email, sales tasks, and follow-up according to registration and attendance uses more complex logic. In both cases, people still choose the audience, purpose, content, controls, and success measure. Campaign automation reduces repetitive work and responds faster than a manual queue. It can also repeat an error at full scale. An incorrect field, missing suppression, stale owner, or ambiguous exit condition may send irrelevant communication or create tasks that no one should receive. Model the campaign as states and transitions. Record who is eligible, which event starts the campaign, what actions follow, how delays work, what data can change, and which conditions stop or reroute the flow. Test for missing values, duplicate entry, late events, manual changes, consent updates, and people who complete the desired action early. Give each campaign an owner and version. Keep the brief, workflow logic, content, audience query, system permissions, test cases, launch date, and change log together. Monitor entry volume, delivery, progression, conversion, exceptions, complaints, and downstream quality. Pause automatically when a material data or delivery threshold fails. A webinar campaign invites a qualified segment, suppresses existing registrants, reminds only people who opted in, and sends different follow-up based on attendance. High-fit attendees who request a conversation route to sales immediately. No-shows receive the recording, while booked contacts and current customers exit the promotional sequence. A campaign becomes safer to automate when its states, permissions, and stopping conditions are as clear as its message. Operators should be able to explain every live branch without opening a maze of undocumented workflow boxes. --- # B2B Content Marketing | Surface Glossary URL: https://surface.thesurface.network/glossary/b2b-content-marketing ## What is B2B content marketing? B2B content marketing is the planned use of articles, guides, research, videos, events, email, customer proof, sales materials, and other media to influence business buyers. It helps an audience understand a problem, evaluate options, reduce risk, and make a decision across a buying process that often includes several stakeholders. The audience includes more than the person who finds the page. An operator may need implementation detail, a manager may need a business case, security may need evidence, and finance may need cost context. Sales and customer teams also use the same content after marketing creates the first interaction. ## How B2B content marketing works in practice Start with the buying problem and the internal questions that block progress. Build connected assets across discovery, education, comparison, proof, implementation, and conversion. Use expert and customer evidence, plan distribution before publication, and connect page performance to lead quality and sales outcomes without pretending every touch can receive exact credit. 1. Define the audience, business problem, buying group, and desired change in understanding. Avoid using a broad persona when the content must answer a specific operational question. 2. Map content to intent and decision stage. Early research needs clarity, comparisons need tradeoffs, and later-stage pages need proof, implementation detail, and a useful next action. 3. Create a source and point-of-view layer before drafting. Gather interviews, product knowledge, customer evidence, market data, and the argument that should make the company recognizable. 4. Publish through a maintained content system with strong metadata, internal links, conversion paths, and distribution across email, social, sales, partners, and paid campaigns where appropriate. 5. Measure visibility, engagement, movement, lead quality, sales use, pipeline influence, and content freshness. Feed sales objections and performance back into the next brief. Useful measures span several layers: rankings and citations for discovery, engaged consumption and return visits for attention, subscriptions and form completion for permission, accepted leads and meetings for conversion, and sales use or pipeline influence for business value. No single metric captures the full path. The operating discipline for B2B content marketing is a chain from question to source to interpretation to decision. Preserve interview notes, survey instruments, queries, public records, and dated product evidence with enough context to audit the conclusion. Add a confidence statement and the observation that would reverse the recommendation. This avoids the familiar research failure where a clean slide outlives the evidence and continues to guide positioning after the market has changed. Set the review cadence for B2B content marketing according to volatility and consequence. Fast-changing inputs may need weekly checks, while stable reference material may suit a quarterly factual review. The owner should inspect input quality, output quality, timing, exceptions, and business outcome. Record which finding changes the rule and which finding only needs observation. Do not let the primary tool, spreadsheet, or configuration become the only documentation. A plain-language record of purpose and consequences makes B2B content marketing easier to audit, teach, change, and retire. Maintain an exception log for B2B content marketing that is small enough to review and structured enough to learn from. Capture the input, expected behavior, actual result, consequence, immediate repair, and root cause. Group recurring exceptions by source, rule, segment, template, or integration. This makes B2B content marketing improve through evidence and prevents the same workaround from being rebuilt by several teams in different tools. Keep a short B2B content marketing limitations note with the current process. It should name missing evidence, unsupported cases, and dependencies that could invalidate the approved approach. - Which buyer question has enough business value to justify sustained coverage? - Which stakeholder and stage should each asset serve? - What evidence gives the company a credible right to answer? - How will the asset connect to another useful page or action? - Which feedback from sales and customers will change the program? B2B content has to survive internal reuse. A sales rep should be able to send the page without explaining away unsupported claims, and a skeptical buyer should be able to trace important assertions to evidence. A common failure is treating traffic as the strategy. The team publishes broad educational posts, celebrates impressions, and sends every reader to the same demo CTA. The archive has no comparison path, proof layer, or connection to the objections buyers raise in real deals. Organize content around a smaller set of revenue-relevant problems, interview sales and product experts, add proof and implementation assets, and redesign internal links around the reader's next decision. Keep broad traffic only where it contributes to authority, learning, or conversion. --- # B2B Conversion Rate Optimization | Surface Glossary URL: https://surface.thesurface.network/glossary/b2b-conversion-rate-optimization B2B conversion rate optimization, or B2B CRO, is the process of improving how often eligible prospects complete a meaningful action such as submitting a qualified form, booking a meeting, starting a trial, becoming an opportunity, or purchasing. The rate is a metric, while optimization is the research and experimentation used to improve it. B2B journeys often involve longer cycles, several stakeholders, high-value decisions, and multiple conversion stages. A page can increase raw form fills while lowering sales acceptance. Teams should define the event and quality threshold before declaring a test successful. The basic formula is: `Conversion rate = Conversions / Eligible opportunities x 100` Conversions must refer to one defined event, such as qualified demo submissions or booked meetings. Eligible opportunities should use the matching denominator, such as unique landing-page visitors or valid submitted forms. Keep bot traffic, employees, duplicates, and test records out through documented rules rather than convenient manual removal. Common rates include visitor to lead, form start to submit, submit to meeting, meeting to opportunity, and opportunity to customer. Cohort windows matter. A meeting booked 45 days after a visit may count in one analysis and fall outside another. There is no universal good B2B conversion rate. Intent, traffic source, offer, price, segment, page type, device, and qualification requirements change the baseline. A demo page should not be compared directly with an educational blog or a low-friction newsletter form. Optimize downstream quality and customer experience along with the percentage. Removing every form field may raise submissions while damaging routing. Aggressive popups may create more leads and more distrust. Tests need guardrail metrics such as qualified rate, meeting rate, spam, opt-out, sales rejection, and pipeline. Document the market boundary, segment, geography, period, source dates, units, exclusions, and every material assumption beside the result. Keep the numerator and denominator available so another analyst can recalculate B2B conversion rate when an input changes. Record the calculation version and review date so later comparisons use the same method or explain the change. A demo page receives 2,000 eligible visits and 100 valid submissions, a 5 percent visitor-to-lead rate. Sixty submissions qualify and 36 book meetings. A new form produces 120 submissions but only 54 qualified leads and 30 meetings. Top-line conversion rises to 6 percent while the business outcome declines. Choose the conversion closest to value that the experiment can influence, then track earlier steps as diagnostics. CRO should improve movement through the system rather than one isolated form percentage. --- # B2B Digital Lead Generation | Surface Glossary URL: https://surface.thesurface.network/glossary/b2b-digital-lead-generation B2B digital lead generation is the use of search, content, paid media, social, email, webinars, communities, partner channels, product experiences, and website conversion paths to create identifiable interest from business buyers. The process continues through capture, qualification, routing, follow-up, and measurement. Digital activity may influence a deal long before a form appears. Buyers read comparisons, ask AI assistants, visit review sites, return directly, and involve colleagues. A lead source field captures one part of that journey. Teams should use attribution with caution and listen to sales evidence about how buyers actually found and evaluated the company. The discipline connects demand creation to revenue operations. Campaign volume can look healthy while sales receives poor-fit records or high-intent requests wait in a queue. Effective lead generation defines quality before launch and instruments the path to a meeting and opportunity. Choose channels from the audience's research behavior, build a relevant offer and landing path, collect only necessary data, enrich or score where it improves a decision, and route quickly. Compare tactics through accepted leads, meetings, pipeline, cost, and payback alongside reach and form conversion. The operating test for B2B digital lead generation is whether the resulting demand can move. Instrument the entry point, record quality, routing decision, follow-up time, meeting, opportunity, and reason a lead is rejected or recycled. Choose a measure that follows the actual job. Validity, coverage, reviewer effort, conversion, response time, source quality, and revenue can describe different outcomes and should stay separate. A short decision record should state the current approach, evidence, owner, date, and condition for revision. That makes B2B digital lead generation useful beyond the person who first implemented it. A B2B security company publishes implementation guides and competitor comparisons, runs targeted search campaigns, and hosts practitioner webinars. All paths use product-specific capture and a shared qualification model. The team learns that comparison traffic creates fewer leads than webinars but twice the opportunity rate, so it funds both for different jobs. Digital lead generation is a connected system. Optimizing clicks while ignoring the form, record, owner, response, and sales outcome leaves most of the economic path unmanaged. --- # B2B Lead Generation Funnel | Surface Glossary URL: https://surface.thesurface.network/glossary/b2b-lead-generation-funnel A B2B lead generation funnel is a model of how market attention progresses into identifiable demand and a sales outcome. Stages may include reached audience, engaged visitor, known lead, qualified lead, meeting, opportunity, and customer. Account activity and several buying-group members may contribute to the same motion. The funnel is a measurement model rather than a literal description of buyer behavior. People pause, return, use several channels, involve colleagues, or enter after substantial offline research. Useful funnels define observable business states without pretending every buyer follows the same order. Funnel definitions expose where demand becomes unproductive work. Healthy visitor conversion can still produce few qualified meetings when forms attract the wrong audience or routing is slow. Looking only at top-of-funnel volume hides the handoff where value disappears. Define each stage, entry event, owner, timestamp, exit, and source of truth. Keep lead and account states distinct. Preserve content and campaign context through routing, and record why sales accepts, rejects, recycles, or advances a record. Measure cohort conversion and time between stages by segment and source. Use the funnel to diagnose, not to assign blame. Review full paths and sample records behind the rates. Falling lead-to-meeting rates may reflect weaker targeting, a form change, scoring drift, owner capacity, delayed follow-up, or a new sales definition. Change the stage or workflow only after tracing the evidence. At one software company, traffic stays stable and demo submissions rise while opportunity creation falls. Record review shows a broad paid campaign driving small companies outside the target segment. Marketing narrows the audience, the form captures one qualifying field, and routing sends strong fits to available owners immediately. Volume falls while opportunity conversion recovers. The B2B funnel is most useful when its stages correspond to real decisions and keep the buyer's context intact across teams. Review the model whenever qualification or ownership changes. --- # B2B Martech Stack | Surface Glossary URL: https://surface.thesurface.network/glossary/b2b-martech-stack A B2B martech stack is the coordinated set of technologies used to understand markets, create demand, publish content, capture leads, manage customer records, automate campaigns, route work, support sales, and measure revenue outcomes. The stack includes integrations, schemas, permissions, and operating rules as well as software. Common components include a CRM, marketing automation platform, CMS, analytics, paid-media tools, enrichment, scheduling, consent management, sales engagement, and reporting. Some tools store authoritative records; others act on those records. Confusing those roles creates competing versions of lifecycle, source, ownership, and account identity. B2B journeys cross channels and teams over weeks or months. The stack has to preserve enough context for the next person or system to act: which account is involved, what the buyer saw, what need was expressed, who owns follow-up, and which outcome eventually occurred. Design by capability and information flow before selecting vendors. Name systems of record, writable fields, identifiers, lifecycle definitions, consent rules, service levels, and failure paths. Remove overlapping tools that perform the same job without a clear owner. Test integrations with real exceptions, including duplicate people, subsidiaries, delayed events, and manual changes. Keep an architecture map and a field-level contract for high-impact data. Review cost alongside adoption, manual work, time to launch, error rate, routing speed, and business outcomes. Tools that save license fees but require weekly exports may be expensive in practice; large platforms with unused modules can create their own drag. At one SaaS company, the CRM holds account and opportunity records, the content system handles publishing, the automation platform runs lifecycle programs, and a lead layer performs enrichment and routing. Each tool can read lifecycle stage, but only approved systems may write it. The team logs sync failures and sends unresolved account matches to review. B2B martech stacks work when their systems share definitions and authority. The number of logos in the architecture diagram is secondary to operational clarity. --- # Benefits of Data Cleansing | Surface Glossary URL: https://surface.thesurface.network/glossary/benefits-of-data-cleansing The benefits of data cleansing come from reducing errors that interfere with analysis and action. Cleaned records can improve duplicate handling, field validity, account matching, segmentation, lead qualification, routing, attribution, personalization, compliance processes, and confidence in shared reports. The benefit depends on the use case. Standardizing country names may repair a territory workflow. Resolving account duplicates may reconcile pipeline. Updating job titles may improve qualification. Cosmetic changes that do not alter a decision can consume time without creating equivalent value. Cleaner data reduces manual repair and makes exceptions easier to see. It can also prevent customer-facing mistakes, such as sending the wrong message, assigning the wrong rep, or treating one company as several accounts. Measure the improvement downstream rather than by table appearance alone. Prioritize fields by consequence, profile defects by source, preserve raw values, and write auditable rules. Measure before and after error rates, exception volume, join coverage, rep acceptance, response speed, conversion, and report reconciliation. Fix the form or integration that keeps reintroducing the problem. The operating record for data cleansing should show the original value, proposed or cleaned value, rule, confidence, source, timestamp, and reviewer where needed. That history makes corrections reversible. Review a sample of real cases before relying on an aggregate score. The sample should include incomplete, conflicting, and high-value records because averages often hide the failures with the largest business cost. Place the documentation for data cleansing beside the workflow or decision it affects. That keeps definitions, evidence, ownership, and later corrections available to the people who need them. A company has duplicate accounts under legal names, trade names, and web domains. A cleansing project creates a stable account ID, reviews fuzzy matches for high-value companies, and reconnects leads and opportunities. Pipeline no longer splits across records, account ownership becomes clearer, and reports reconcile with sales review. The strongest benefit is operational trust. People stop building private spreadsheets to compensate for a shared system they do not believe. --- # Brand Market Research | Surface Glossary URL: https://surface.thesurface.network/glossary/brand-market-research Brand market research studies how a defined audience perceives and uses a brand when making choices. It may measure awareness, recall, associations, consideration, preference, trust, distinctiveness, message comprehension, or movement after a campaign. Interviews and open responses help explain why those measures look the way they do. The intended position and the received position can differ sharply. Internally, a company may describe itself as an enterprise platform while buyers remember one narrow feature. Existing customers may recognize the value immediately while prospects confuse the company with a different category. Brand research examines that gap by audience and buying situation. Brand decisions affect naming, positioning, creative, media, sales language, category education, and product emphasis. Research keeps the loudest internal opinion from standing in for market perception. It also prevents a favorable customer sample from being presented as broad market awareness. Define the audience and decision before selecting measures. Separate unaided recall from aided awareness, familiarity from preference, and message recognition from belief. Recruit customers, lost deals, prospects, or category buyers according to the claim. Preserve verbatim language and report sample limitations beside every percentage. Combine methods when the decision needs both scale and explanation. Surveys can estimate how often an association appears in a qualified sample; interviews can show the experiences behind it. Search behavior, review language, win-loss notes, sales calls, and competitor creative add context, although none should be treated as a representative survey on their own. One B2B payments company believes buyers choose it for workflow flexibility. Interviews reveal that customers value the flexibility after purchase, while new prospects first remember the company for faster implementation. Follow-up survey results confirm the split. Marketing leads with implementation evidence in acquisition campaigns and keeps flexibility for later comparison and expansion materials. Brand market research is most useful when it changes a particular message or market choice and keeps audience differences visible. Revisit the evidence when a launch, competitor, product change, or new audience makes the old associations unreliable. --- # Brand Marketing Research | Surface Glossary URL: https://surface.thesurface.network/glossary/brand-marketing-research Brand marketing research examines how a defined audience recognizes, understands, remembers, and evaluates a brand. It can study awareness, associations, meaning, relevance, trust, preference, distinctiveness, message response, visual identity, consideration, and the relationship between brand perception and behavior. The research should name the audience and context. Customers, active buyers, category users, employees, partners, and the general public may hold different views. Combining them can hide the perception that matters for a decision. Qualitative work reveals language, memories, expectations, and the reasons behind reactions. Surveys measure awareness, associations, consideration, or preference across a sample. Experiments compare messages or creative. Search, social, sales, review, and behavioral data show how the brand appears in observed interactions. Brand tracking follows stable measures over time. No single score explains brand health. High awareness can coexist with weak trust or poor relevance in a target segment. Begin with the brand decision, such as positioning, naming, identity, campaign, market entry, or reputation response. Define competitors and the category frame. Use neutral questions and blind comparisons where appropriate. Keep spontaneous awareness separate from prompted awareness. Record sample, source, date, and major market events. Connect perception to behavior carefully. Correlation between preference and purchase does not by itself establish cause. A software company is known for a single legacy product and wants to introduce a platform message. Interviews show that customers trust its technical depth but do not understand the broader offer. A survey measures the pattern across buyers and nonbuyers. A message test compares the platform claim with a problem-led alternative. The team keeps the legacy proof while changing the category explanation, then tracks comprehension and consideration among target accounts. Research is useful before a positioning or identity change, during market entry, after a reputation event, and at regular intervals when the brand investment is large. Keep core tracking measures stable, then add temporary questions for current decisions. Review results beside major campaigns, product changes, and category events. A movement in awareness or trust needs context before the team assigns cause. --- # Brand Schema Markup | Surface Glossary URL: https://surface.thesurface.network/glossary/brand-schema-markup Brand schema markup is an informal name for structured data that clarifies a brand or company's identity. Most websites express that identity with Organization markup and properties such as name, URL, logo, legalName, foundingDate, address, contact information, and sameAs links when those facts are relevant and maintained. There is a Brand type in Schema.org, often used as a product's brand value, but a corporate website usually needs an Organization entity as its central node. Product pages can then connect products to the same organization or brand identifier. Consistent identifiers matter more than repeating a large company description on every page. A clear organization entity reduces ambiguity when a company uses a shortened name, has several products, operates multiple domains, or shares a name with another business. It also forces the team to choose one official logo, canonical homepage, legal name, and set of verified profiles. That consistency supports search interpretation and cleaner content operations. Create one authoritative Organization node with a stable @id, often based on the canonical homepage plus a fragment identifier. Reference that same @id from article publishers, product manufacturers, authorship relationships, and other relevant nodes. Generate facts from a controlled company profile rather than typing slightly different versions into each template. For brand schema markup, begin with the page or record a machine must understand. Write down the primary entity, the maintained source for each fact, and the decision the structured representation should support. Choose a measure that follows the actual job. Validity, coverage, reviewer effort, conversion, response time, source quality, and revenue can describe different outcomes and should stay separate. A short decision record should state the current approach, evidence, owner, date, and condition for revision. That makes brand schema markup useful beyond the person who first implemented it. A software company is legally named Northline Systems, Inc. and markets itself as Northline. Its homepage markup identifies the Organization as Northline, includes the legal name as a separate property, points to the canonical logo, and uses one @id. BlogPostings list that organization @id as publisher instead of creating a new anonymous publisher object on every article. Brand schema should make identity boringly consistent. It should not contain slogans, unsupported awards, invented ratings, or every social account the company has ever opened. --- # Business Research and Its Types | Surface Glossary URL: https://surface.thesurface.network/glossary/business-research-and-its-types Business research is the structured collection and analysis of evidence for a business decision. It can study a market, customer, competitor, brand, product, price, channel, operation, workforce, or financial question. The type is best defined by the decision the research must support rather than by the software or document used to produce it. Common purpose-based types include market research, customer research, competitor research, product research, brand research, operational research, and financial research. One project may use several types, but each question should name the decision owner and the uncertainty being reduced. Market research estimates demand, segments, growth, and category conditions. Customer research studies needs, language, behavior, satisfaction, and buying process. Competitor research examines alternatives, claims, capabilities, distribution, and buyer comparison. Product research tests problems, concepts, usability, value, and adoption. Brand research measures awareness, associations, preference, and message response. Operational and financial research look inward as well as outward. They may examine process time, capacity, cost, risk, pricing, retention, or investment choices. Start with the decision and the consequence of being wrong. Decide whether the team needs to discover possibilities, describe a market, compare options, explain a cause, or estimate an outcome. Then choose sources and methods that can answer that question at the required confidence and speed. Separate primary evidence gathered for the project from secondary evidence created elsewhere. Use qualitative work for depth and explanation, quantitative work for measurement, and observation or behavioral data when reported opinions may be incomplete. A software company considering a healthcare segment uses market research to estimate eligible organizations, competitor research to map incumbent products, customer interviews to understand procurement, product research to test a compliance workflow, and financial research to model implementation cost. The studies share a strategy question, yet each produces evidence for a different part of the investment decision. For every research type, record the business question, owner, population, source, method, observation period, limitations, and decision made. The classification should help another person judge whether the evidence can be reused. A customer interview study completed for onboarding may offer useful language for a campaign, yet it cannot automatically represent market demand or pricing across every segment. --- # Business-to-Business Market Research | Surface Glossary URL: https://surface.thesurface.network/glossary/business-to-business-market-research Business-to-business market research, often shortened to B2B market research, studies organizations and the people involved in business purchases. It examines market structure, demand, segments, buying groups, user needs, alternatives, budgets, procurement, implementation, competitive behavior, and the conditions that shape adoption. The buyer is rarely one person. A user may want better workflow, a manager may seek output and control, security may review risk, procurement may negotiate terms, and an executive may approve the budget. Research has to distinguish these roles and the different evidence each one can provide. B2B populations are often smaller and harder to recruit than consumer audiences. Long sales cycles and high contract values also leave teams with fewer observations. Treating current customers or sales anecdotes as the entire market can make a narrow pattern appear universal. Define the organization type, role, buying situation, geography, and product scope before collecting evidence. Combine customer interviews, lost-deal research, sales and product data, public filings, industry sources, competitive material, and surveys where sampling allows. Separate the organization record from the individual respondent and preserve how each source was selected. Match the method to the decision. Interviews can explain buying sequence and internal conflict. A well-framed survey can compare needs across a reachable population. Win-loss work can expose deal-specific alternatives. Market and company data can size segments, although modeled estimates should retain ranges and source dates. A compliance platform is considering healthcare as a new vertical. Researchers interview operations users, security reviewers, and economic buyers across qualified organizations, then examine procurement rules and current alternatives. The study finds strong need among users but a certification requirement that blocks near-term sales, so the company postpones the launch and funds the missing capability first. B2B market research is credible when it keeps the organization, role, buying context, and evidence limits visible. Recheck the study when procurement rules, category language, product requirements, or the composition of the buying group changes. --- # Chatbot Prompt Engineering | Surface Glossary URL: https://surface.thesurface.network/glossary/chatbot-prompt-engineering Chatbot prompt engineering is the design of instructions and context for a conversational model. It covers the assistant's role, allowed knowledge, dialogue goals, turn-by-turn state, tool access, output rules, escalation behavior, and the way the bot handles missing or conflicting information. A chatbot differs from a one-time generator because each turn changes the next input. The system may need to remember a product choice, forget sensitive details, resolve a pronoun, retrieve current documentation, or recognize that the user has changed goals. Prompt text alone cannot manage all of that safely. Good design reduces confident improvisation and repetitive questioning. It also makes the conversation useful to the business. A support bot should know when to cite a help article, when to create a ticket, and when a policy question requires a person. A lead bot should separate qualification from pressure to book a meeting. Define the conversation states, approved sources, tools, permission boundaries, and handoff conditions before polishing the bot's tone. Test complete dialogues, including corrections, topic changes, hostile inputs, incomplete records, and users who decline a requested field. Score task completion and escalation quality alongside writing style. Use chatbot prompt engineering inside a defined task rather than as an isolated piece of prose. Save the input, approved context, desired output, model, and test cases beside the prompt so later edits can be compared. Choose a measure that follows the actual job. Validity, coverage, reviewer effort, conversion, response time, source quality, and revenue can describe different outcomes and should stay separate. A short decision record should state the current approach, evidence, owner, date, and condition for revision. That makes chatbot prompt engineering useful beyond the person who first implemented it. A website chatbot helps visitors choose an integration. It asks which CRM they use, retrieves the current integration record, explains setup requirements, and offers a relevant guide. If the record is missing or the visitor asks about a custom security term, the bot creates a structured question for a specialist instead of inventing an answer. A pleasant voice is one layer of chatbot quality. The deeper work is maintaining state, grounding claims, limiting authority, and giving the user a clean path when automation reaches its boundary. --- # Client Acquisition | Surface Glossary URL: https://surface.thesurface.network/glossary/client-acquisition Client acquisition is the process a business uses to attract, qualify, win, and begin work with suitable new clients. The term is common in professional services, agencies, consulting, finance, legal work, and other relationship-led businesses where the engagement depends on expertise, trust, scope, capacity, and ongoing delivery. In many companies, client acquisition and customer acquisition are used interchangeably. The client label often signals a higher-touch sale and a delivery relationship shaped around an account's needs. Acquisition therefore includes expectation setting and delivery fit, not just contract signature. A poorly scoped win can consume scarce expert capacity, create margin loss, and damage referrals. Marketing, business development, sales, principals, finance, and delivery teams may all influence the outcome. Begin with an ideal-client definition tied to the firm's expertise, economics, conflicts, capacity, and desired work. Create credible ways for that audience to discover the firm, then capture context without forcing every prospect through the same form. Qualification should examine the problem, authority, timing, budget or commercial fit, delivery requirements, and the firm's ability to produce the promised result. 1. Define suitable client work. Specify industries, problems, engagement sizes, locations, risk limits, conflict rules, delivery capabilities, margin expectations, and disqualifying conditions. 2. Build sources of relevant interest. Use referrals, partnerships, expertise-led content, events, directories, outbound work, communities, or paid programs according to how buyers seek and trust advice. 3. Capture and qualify the inquiry. Preserve referral source, stated need, organization, stakeholders, timing, existing relationship, and constraints. Route conflicts, urgent matters, and poor-fit work through documented paths. 4. Develop the opportunity. Run discovery, define outcomes and scope, assess delivery effort, select proof, address risk, agree commercial terms, and record commitments. Keep proposal status and next ownership visible. 5. Open the client relationship. Confirm contract and billing status, transfer discovery and promises to delivery, introduce responsible people, and establish the first success milestone. Feed losses and early delivery issues back into qualification. Useful measures include qualified inquiry, response time, consultation, proposal, win rate, cycle time, acquisition cost, referral source, expected margin, capacity fit, early scope change, time to first outcome, retention, and expansion. Evaluate by client cohort and service line. A high win rate may signal precise fit or proposals sent only after informal commitment, so the stage definition belongs beside the number. Write qualification and scoping rules with delivery leaders, not solely with sales. Record who can approve discounts, unusual terms, conflicts, capacity exceptions, or work outside the standard offer. Proposal templates should expose assumptions, responsibilities, exclusions, dependencies, and change control. Review early client outcomes and margin with acquisition sources so the firm learns which messages and referrals produce healthy relationships. Sample discovery notes against signed scope and first-month delivery issues. That review shows whether the problem began in qualification, proposal language, handoff, or execution. - Which clients and engagements fit the firm's expertise, risk, economics, and capacity? - Which channels produce trust with the intended buyer? - Who owns qualification, conflict review, proposal, and delivery acceptance? - Which promises and context must survive the handoff? - How will early delivery quality change future acquisition choices? Service businesses may keep several acquisition paths. A referred executive can receive a personal response while a standard inquiry enters a structured queue. The underlying fit and approval rules should remain consistent. High-touch treatment should provide context and judgment, rather than bypassing risk checks because the introduction came from a senior person. A common failure is rewarding signed revenue without examining delivery fit. The firm accepts work outside its expertise, proposes before understanding the problem, and leaves consultants to renegotiate expectations after the contract. Another failure depends on partner referrals without recording which relationships produce suitable, profitable engagements. Review recent wins, losses, declined work, scope changes, margin, and early client outcomes. Identify the acquisition claims and qualification choices associated with weak engagements. Tighten the suitable-client definition, add delivery review before proposal, and preserve discovery notes in the handoff. If capacity is the constraint, change channel or offer choices instead of filling the pipeline indiscriminately. --- # Client Lead Generation | Surface Glossary URL: https://surface.thesurface.network/glossary/client-lead-generation Client lead generation is the process service businesses use to attract and identify prospective clients. Agencies, consultancies, professional services firms, and independent experts may use referrals, search, thought leadership, events, partnerships, directories, outbound, assessments, case studies, and paid campaigns. A client lead is useful when the problem, budget, timing, authority, and fit support a credible engagement. High lead volume can waste senior time if intake does not separate urgent qualified needs from general questions, job seekers, vendors, and poor-fit requests. Services depend heavily on trust and specificity. Prospects need to see how the firm thinks, which problems it solves, what evidence supports its approach, and what working together requires. The lead system should preserve that context so the first conversation does not restart the research from zero. Choose a narrow audience and problem, publish proof and useful expertise, create an intake path matched to intent, and ask only the questions needed for the next decision. Route by service, industry, geography, value, or availability, then measure consultations, proposals, wins, revenue, and capacity alongside inquiries. The operating test for client lead generation is whether the resulting demand can move. Instrument the entry point, record quality, routing decision, follow-up time, meeting, opportunity, and reason a lead is rejected or recycled. Keep the source beside the result and make changes reversible. This protects the operation when a definition, vendor, model, template, or buyer behavior changes after the original decision. The final review should ask what changed for a buyer or operator. If client lead generation only creates another field, page, prompt, or dashboard, its role remains incomplete. A technical consultancy publishes a migration guide and a detailed case study, then offers a 30-minute architecture assessment. The form captures current platform, deadline, team size, and primary risk. Qualified requests reach the relevant principal with the content journey attached, while early researchers receive a practical follow-up guide. Client lead generation should protect expert time and improve the prospect's first conversation. A generic contact form rarely captures enough context to do either job well. --- # Competitive Analysis Research | Surface Glossary URL: https://surface.thesurface.network/glossary/competitive-analysis-research Competitive analysis research is the systematic study of companies, products, substitutes, and buyer alternatives that shape a market decision. It collects evidence about positioning, capabilities, audiences, pricing models, routes to market, proof, implementation, customer response, and change over time. A competitor feature grid is one output, not the research itself. Useful analysis combines current primary sources with buyer evidence and an explicit question. Product pages show what a company claims. Documentation shows how a capability works. Reviews, sales calls, win-loss interviews, and customer research show how the market experiences those claims. Competitive research influences category language, campaign arguments, sales enablement, roadmap choices, and which comparisons deserve content. Stale or selective evidence can produce confident positioning against a competitor that has changed, or it can overemphasize visible features that buyers barely consider. Start with the decision and a defensible competitor set. Define fields before collection, capture source URLs and dates, distinguish fact from inference, and record confidence. Use the same evaluation method across companies. Preserve previous snapshots so a new launch or pricing change does not erase the history needed to understand movement. Review the evidence with sales, product, and customer teams because each sees a different part of the market. Mark claims that require revalidation and give the research an owner. Summaries should identify where competitors are strong, where evidence is unclear, which buyer situations favor each option, and what the company should do next. A workflow platform studies three direct competitors and the internal spreadsheet process buyers often keep instead. Product research finds broad feature parity among vendors. Win-loss interviews show that implementation effort and reporting flexibility drive more decisions than the headline features. Marketing shifts its comparison pages and proof library toward those two concerns. Competitive analysis research earns trust through current sources, comparable criteria, and conclusions tied to a real buyer or business choice. The final record should also say what remains unknown and who will verify it. --- # Competitive Data | Surface Glossary URL: https://surface.thesurface.network/glossary/competitive-data Competitive data is sourced information about the companies, products, services, workarounds, and no-action choices that buyers consider as alternatives. It may cover positioning, audience, capabilities, pricing model, packaging, proof, customer language, distribution, partnerships, hiring, public financials, releases, search visibility, and observed deal outcomes. Every item should retain a date and source. The data can come from primary product pages, documentation, public records, interviews, win-loss material, sales calls, reviews, events, and internal commercial systems. These sources describe different things. A vendor page states a current claim, a lost-deal note records one seller's interpretation, and a review reflects one user's experience. Combining them without labels turns evidence into rumor. Competitive information spreads quickly through sales material and strategy decks. Old pricing may survive for years, unknown features may be marked absent, and several copied articles may trace back to one inaccurate claim. Structured records make freshness, provenance, confidence, and disagreement visible. They also let teams compare like with like across segments and time. Define the business question and collection boundary before building a watchlist. Capture the observed fact, subject, source type, original URL or record, collection date, effective date, market or segment, analyst, confidence, and review date. Separate raw observations from interpretation. Apply the same fields to the company's own offer when competitive data supports public comparisons. Use the data to form questions for positioning, product, sales, and market strategy, then seek stronger evidence before making high-consequence claims. Give sellers approved language and a way to submit new observations without editing the canonical record. Review volatile fields, such as pricing and product availability, more often than stable company history. Restrict access when records contain confidential customer or deal information. A sales team says a competitor now includes implementation at no charge. Operations records the claim as an unverified deal observation, checks the current pricing and service pages, and asks the buyer what was included. The evidence shows a limited onboarding package rather than full implementation. Enablement updates the comparison with the exact scope and source date instead of repeating "free services." Competitive data is useful when a reader can tell what was observed, where it came from, when it applied, and how certain the interpretation is. --- # Competitive Landscape | Surface Glossary URL: https://surface.thesurface.network/glossary/competitive-landscape A competitive landscape is a structured, dated view of the alternatives available to buyers in a defined market. It identifies direct competitors, adjacent products, internal workarounds, service providers, and the option to do nothing. The landscape describes how those alternatives differ on buyer needs, positioning, capabilities, economics, access, proof, and movement over time. The word "landscape" can suggest a static map, yet competitive choices change with segment and use case. A product may compete directly in one deal and act as a complementary tool in another. Buyer perception also matters. Two vendors can describe themselves as different categories while a procurement team compares them for the same budget and outcome. Define the buyer decision before listing companies. Collect primary product material, public evidence, buyer and seller observations, win-loss records, reviews, pricing information, and market data. Keep claims attached to their dates and sources. Compare alternatives through criteria the buyer uses, including switching cost and implementation burden, rather than a checklist chosen to favor the company's own product. 1. Set the boundary. Name the buyer, problem, geography, time period, deal context, and alternatives included. Explain why an option counts and what falls outside the study. 2. Create an evidence record for each alternative. Capture category claim, audience, use cases, product facts, pricing model, route to market, proof, limitations, and current source links. Mark unknowns instead of assuming absence. 3. Study buyer comparison behavior. Review won, lost, stalled, and no-decision cases to learn which alternatives enter together, which criteria matter, and where the buying group disagrees. 4. Map positions and movement. Use a small number of buyer-relevant dimensions, then add dated changes such as acquisitions, releases, pricing shifts, partnerships, or regulatory effects. 5. Convert the view into decisions. Update positioning, research priorities, product questions, sales guidance, and monitoring. Record what would cause the team to redraw the boundary. Quality can be checked through source freshness, coverage of relevant alternatives, claim traceability, representation of no-decision outcomes, and agreement between buyer evidence and the chosen comparison dimensions. Usage matters too. Track which product, campaign, enablement, or strategy decisions use the landscape and whether later deals expose missing or inaccurate assumptions. Assign an owner and a factual review schedule. Competitor claims should come from current primary sources where possible, with customer or sales evidence clearly labeled as perspective. Apply the same comparison fields to every option. Disclose commercial interest when the landscape becomes external content. Archive prior versions so a team can see what changed instead of rewriting history to match the current story. Give sellers a correction path that accepts new deal evidence without allowing one anecdote to overwrite the canonical view. Record disputed claims until a reviewer resolves them. Notify dependent teams when a material fact or market boundary changes. - Which buyer decision and segment define competition for this analysis? - Which direct, adjacent, service, internal, and no-action alternatives belong? - Which comparison dimensions come from buyer evidence? - How will unknown, disputed, or changing competitor claims be labeled? - Who owns updates and approves external use? Internal and external versions may need different depth, but they should use the same factual base. An internal document can include sales hypotheses and uncertainty. A public comparison needs stronger verification, balanced limitations, transparent inclusion criteria, and a visible commercial disclosure. Neither should state competitor weakness as fact when the evidence is only anecdotal. A common failure is arranging vendor logos on two axes chosen after the team decides where it wants to appear. The visual looks analytical while the dimensions lack buyer evidence and the data has no date. Feature grids create a similar problem when checkmarks lack definitions and an unknown capability is recorded as missing. Rebuild the landscape around a real buying decision. Interview recent buyers and sellers, audit primary sources, define comparable fields, and separate confirmed facts from interpretations. Use fewer dimensions if those are the only ones the evidence supports. Then set a review trigger for competitor, pricing, regulatory, or segment changes that could alter the map. --- # Competitive Landscape Analysis | Surface Glossary URL: https://surface.thesurface.network/glossary/competitive-landscape-analysis A competitive landscape analysis maps how competitors, substitutes, and market positions relate across a defined category. It looks for groups, patterns, crowded claims, underserved segments, changing boundaries, and the dimensions buyers use to distinguish options. The output may be a narrative, table, category map, or carefully supported visual. Competitive market analysis often evaluates a focal company against a defined set of alternatives. Landscape analysis takes a wider structural view. It may include emerging entrants, adjacent categories, service providers, internal workarounds, and shifts that could redraw the competitive set even when they rarely appear in today's deals. Choose the perspective before collecting logos. Define the buyer, problem, geography, and period, then build the long list and classify competitors through evidence. Select comparison dimensions that buyers recognize, show uncertainty, and test the resulting map against customer, sales, product, and market data. 1. State the market boundary and point of view. Explain whose choice the analysis represents and which adjacent solutions remain relevant. 2. Build and classify the participant set. Group direct competitors, substitutes, service options, internal solutions, and emerging approaches using documented inclusion rules. 3. Collect comparable evidence. Record audiences, positions, capabilities, pricing logic, proof, route to market, funding or ownership where relevant, and meaningful changes over time. 4. Select and test analytical dimensions. Use buyer evidence to choose axes, segments, or categories and avoid dimensions created only to place the company in an empty corner. 5. Interpret movement and implications. Identify crowded positions, weak evidence, changing boundaries, threats, opportunities, and the product or go-to-market choices that follow. Assess the analysis through coverage, source recency, confidence, buyer recognition, and usefulness to decisions. Track which entrants, substitutes, or movements later appear in deals and research. Visuals that stay stable for years may reflect a durable category or an update process that no longer observes change. Keep the classification rules and source record beside the final map. For every placement, show the evidence and date. If two researchers could reasonably place a company differently, record the ambiguity rather than forcing false precision. Update the full set with the same method so a new competitor does not receive more detailed scrutiny than older entries. Use visuals carefully. Two-axis maps imply that the axes matter and that positions can be compared on them. Explain how values were assigned, what the scale means, and which data is estimated. Where evidence is categorical or incomplete, a table or grouped narrative may communicate the market more honestly than a precise-looking scatterplot. - Whose buying decision and problem define the competitive field? - Which adjacent categories or substitutes could change the market boundary? - Which dimensions have evidence and real buyer relevance? - How will uncertainty and fast-changing entrants appear in the output? - Which strategic decision will each observed pattern influence? An open space on a map is not automatically an opportunity. Buyers may not value the dimension, the economics may be poor, or competitors may have tested and abandoned the position. Validate an apparent gap with customer need, willingness, company capability, and a route to market. Decorative two-by-two maps built after the conclusion are a common failure. The team chooses axes that place its company in the desirable upper corner, assigns competitors through impression, and treats visual separation as proof of differentiation. Buyers use other criteria, so the map adds confidence without improving a decision. Return to buyer evidence and the market boundary. Replace arbitrary axes, add substitutes, document placement, and use a less precise format where the evidence demands it. Then connect each cluster or movement to a product, position, research, or monitoring action with a named owner. Review the result with someone who was not involved in constructing the map. Ask them to locate several companies from the recorded evidence and explain what the placement means. If they cannot reproduce the logic, simplify the framework. Useful competitive views should travel across teams without requiring the original analyst to narrate every point. Record any disputed placement and its rationale. --- # Competitive Market | Surface Glossary URL: https://surface.thesurface.network/glossary/competitive-market A competitive market is a market in which several credible options compete for buyers, budgets, attention, or access to distribution. Those options may be similar vendors, different ways to solve the same problem, or the decision to keep the current process. Competition shapes price, product expectations, proof requirements, acquisition cost, and the claims a company can make credibly. Competition is a matter of degree. A market can contain many sellers and still be concentrated around a few platforms. A narrow niche may have few direct vendors but strong substitutes. The useful question is how buyers experience choice within a defined segment, geography, use case, and period. 1. **Define the boundary.** State the buyer, problem, product category, geography, channel, and time frame. A broad boundary can hide local concentration, while a narrow one can make ordinary rivals disappear. 2. **Map the choices.** Identify direct competitors, indirect approaches, substitutes, in-house work, and the status quo. Use sales calls, search results, review sites, procurement records, customer interviews, and public company material. 3. **Study buyer movement.** Look at consideration sets, switching triggers, evaluation criteria, contract length, implementation cost, and the reasons deals end without a purchase. Competition becomes visible in actual choices, while feature tables show only one part of the decision. 4. **Measure market structure.** Estimate seller shares where credible data exists. Examine concentration, entry barriers, pricing power, distribution access, network effects, regulation, and the pace of product change. 5. **Translate the evidence.** Decide whether the company should narrow its segment, strengthen proof, change packaging, improve distribution, defend a differentiator, or stop pursuing a market whose economics do not work. - Which alternatives enter the same buyer decision and which only resemble the product. - Whether the company competes on price, specialization, outcome, experience, access, trust, or another defensible basis. - Which barriers protect incumbents and which changes could lower those barriers. - How frequently pricing, claims, products, and buyer criteria should be reviewed. - Which evidence supports the market view and where uncertainty remains high. Teams often call a category competitive when sales feels difficult. The cause may instead be low demand, a weak segment, poor distribution, slow follow-up, or a product that does not solve the urgent problem. Competitive research should distinguish a crowded choice set from internal execution problems. Review the market at the segment level. Enterprise buyers may compare governance and implementation capacity, while small businesses compare speed and price. A company can face intense competition in one segment and open space in another. The common failure is copying a fixed list of familiar vendors into every strategy document. The list becomes a collection of logos rather than evidence about buyer choice. It misses substitutes, new entrants, regional players, and internal workarounds. It also encourages teams to imitate visible features instead of understanding why buyers switch. A better practice maintains a dated competitor set for a defined decision. Each entry includes the buyer context, supporting evidence, observed strength, important limitation, and condition that would change the classification. The market view then supports positioning and investment instead of feeding an endless monitoring exercise. No single metric proves that a market is competitive. Useful signals include the number of credible options in a buyer's consideration set, price dispersion, switching rate, customer concentration, sales win rate, time to decision, discounting, acquisition cost, review volume, and the frequency with which deals end in no decision. Interpret each measure at the same segment and period. Qualitative evidence explains the mechanism behind the numbers. Buyers may stay with an incumbent because migration feels risky, choose a bundle because procurement is easier, or select a specialist despite a higher price. Those reasons determine whether the response should be product investment, stronger proof, better implementation, a narrower segment, or a different channel. Keep scenario assumptions visible. A regulatory change, open standard, major acquisition, or new distribution partnership can alter competition before historical market-share reports show it. Set a review frequency that matches market speed and decision cost. Sales evidence may be reviewed monthly, while category structure receives a deeper quarterly or annual study. Assign owners to the signals that would require an earlier review. A dated market view with clear triggers is safer than a live dashboard that nobody interprets. --- # Competitive Market Analysis | Surface Glossary URL: https://surface.thesurface.network/glossary/competitive-market-analysis A competitive market analysis is a structured evaluation of the companies, products, substitutes, and buyer choices that compete within a defined market. It compares how alternatives address the same problem, which audiences they serve, how they position and price, what they can prove, and where the focal company has credible advantages or exposure. The analysis is narrower than a broad industry study and more decision-oriented than a competitor inventory. It may support positioning, product planning, a launch, sales enablement, pricing, or market entry. The required evidence and comparison fields should follow that decision rather than a universal feature checklist. Set the market boundary and buying situation first. Include direct rivals, substitutes, internal workarounds, and the option to do nothing where buyers use them. Collect current primary evidence with source dates, add buyer and sales evidence, apply comparable criteria, then translate patterns into specific choices and claims the company can support. 1. Define the decision, customer, problem, geography, product scope, and time period. State what would make an alternative competitive in this analysis. 2. Build the competitor and substitute set. Explain inclusion rules and avoid choosing only companies the team already knows how to beat. 3. Collect dated evidence. Review product pages, documentation, pricing, customer proof, public records, reviews, demos, sales calls, win-loss material, and buyer research according to the claim. 4. Compare alternatives through buyer-relevant criteria. Distinguish stated capability, demonstrated capability, customer experience, inference, and information that remains unknown. 5. Convert the analysis into action. Revise position, proof, roadmap, pricing, sales guidance, content, or research priorities and assign an owner for revalidation. Track source freshness, evidence coverage, confidence, frequency of use in decisions, and whether win-loss patterns support the analysis. For sales enablement, review which comparisons appear in real deals and which guidance helps reps respond accurately. Do not judge the work by competitor count or completeness of a feature matrix alone. Use the same fields and evidence standards for every company, including the publisher's own product. Record strengths and limitations by use case. Trustworthy analysis should allow the conclusion that another option fits a particular buyer better. This restraint improves the material for readers, sales teams, and AI systems that may extract a paragraph without the surrounding context. Assign an owner and a review cadence based on volatility. Pricing, packaging, product capabilities, partnerships, and positioning can change quickly. Preserve historical snapshots and tag claims that require confirmation before reuse. When the analysis contains inference, state the reasoning and confidence instead of presenting it as a vendor fact. - Which buyer decision and market boundary define the competitive set? - Which criteria influence that buyer rather than merely reflecting internal product categories? - What evidence is acceptable for capability, price, adoption, and customer experience? - Where does the company's offering fit poorly or require more proof? - Who will update volatile claims and communicate changes to dependent teams? Separate the market conclusion from the desired campaign line. Positions should emerge from customer value, competitive reality, and company capability. If the analysis shows that a favored distinction is common or weakly evidenced, the team should improve the product or choose another claim rather than soften the research. Building a spreadsheet from homepage claims and calling the result analysis is a common failure. Features receive checkmarks without definitions, unknown information becomes an assumed absence, and the company's product gets more favorable wording. The document ages quickly and sales turns it into unsupported certainty during live deals. Reduce the comparison to criteria buyers use, replace secondary summaries with current primary sources, and add customer or win-loss evidence. Mark unknowns, limitations, and dates. Then connect each conclusion to an owner and decision. Retire the fields that never change a position, product choice, or sales response. Before reuse in public content, check every competitor claim again and disclose the publisher's commercial interest. Apply the same criteria to the company's own product and describe where another option fits better. The analysis should improve category understanding even for a reader who never chooses the publisher. --- # Competitive Marketing | Surface Glossary URL: https://surface.thesurface.network/glossary/competitive-marketing Competitive marketing is the practice of using evidence about alternatives, buyer criteria, category language, and competitor behavior to improve how a company positions and promotes its offer. It can shape messaging, comparison pages, campaigns, sales enablement, launches, pricing communication, and objection handling. The discipline is broader than attacking named competitors. Buyers compare doing nothing, internal work, adjacent categories, familiar vendors, and new approaches. Good competitive marketing explains fit and tradeoffs without inventing weaknesses or presenting company preference as neutral consensus. Start with the buyer's decision and current alternatives. Verify competitor claims through current primary sources, gather sales and customer evidence, define evaluation criteria before writing comparisons, and state where another option may fit better. Update material when pricing, product, or category conditions change. 1. Map the competitive decision, including status quo, internal build, adjacent solutions, and direct vendors. Record which alternatives appear in real deals rather than relying on a logo list. 2. Collect current evidence from product documentation, pricing, demonstrations, customer reviews, sales calls, and lost-deal notes. Separate vendor claims from verified capability and buyer perception. 3. Define the audience and criteria before choosing the message. Apply the same criteria to the company and competitors, including important limitations. 4. Build assets for the actual workflow: positioning, comparison pages, battlecards, objection responses, campaign concepts, and proof. Keep important claims linked to sources and review dates. 5. Measure use and outcome. Track buyer questions, sales adoption, comparison-page behavior, competitive win and loss reasons, and the accuracy of claims after product changes. Useful measures include competitive page visibility and conversion, sales usage, influenced opportunities, win rate by competitor, loss reasons, time to answer objections, and factual freshness. Changes in win rate need cautious interpretation because deal size, segment, product, and sales execution also move. For competitive marketing, build a decision brief that keeps the market boundary and evidence types visible. List the population, geography, segment, period, inclusion rules, sources, dates, method, and assumptions. Separate direct observations, participant reports, vendor claims, modeled estimates, and internal interpretation. When sources disagree, show the disagreement and explain which definition or method creates it. A later reviewer should be able to update one assumption without rebuilding the entire argument. Create a short release checklist for competitive marketing and assign each item to a role. Include source verification, permissions, privacy, required approvals, error visibility, downstream compatibility, and rollback. Keep the checklist close to the workflow so it changes when the workflow changes. After release, review exceptions before aggregate performance because an average can improve while a small number of high-value cases fail badly. Connect the local competitive marketing workflow to the decision that follows it. Documentation should show what the next operator receives and which context must survive the handoff. Before expanding competitive marketing, compare several outputs with the source material and with the decision made by a competent operator. Record false positives, false negatives, missing cases, and disagreements about definitions. Use that sample to update the rule, test set, documentation, or training rather than explaining every error as an isolated exception. The review should end with a named change and an owner, even when the change is to keep the current scope. For competitive marketing, note unresolved questions beside the approved process. Visible limitations invite review; hidden assumptions tend to survive until a customer, report, or integration exposes them under worse conditions. - Which alternative and buyer decision deserve dedicated material? - Which claims can be supported through current primary evidence? - Which criteria are fair, material, and applied consistently? - Where should the company state a limitation or recommend another fit? - Who owns review dates and competitor-change monitoring? Competitive content should help a buyer choose. That requires enough balance for the conclusion to feel earned. A page that crowns its publisher without a method may create a category association while weakening trust. A common failure is building comparison pages from one AI-generated summary or an old sales deck. Competitor facts drift, criteria favor the publisher, and the conclusion arrives before the evidence. Sales eventually stops using the material because buyers can disprove it during a call. Reverify every material claim, disclose the comparison method, use a shared set of criteria, and include fit by situation. Add an owner and factual review date, then connect sales objections to the next update. --- # Competitor Definition in Business | Surface Glossary URL: https://surface.thesurface.network/glossary/competitor-definition-business A competitor in business is an option that can win the customer, budget, attention, distribution, talent, supplier access, or outcome a company is pursuing. The competitor may sell a similar product, solve the problem differently, enable internal work, or benefit when the buyer keeps the current process. The definition depends on the decision being studied. For marketing and product work, competitors belong in the set when buyers consider them as alternatives. Similar websites or features are not enough. Evidence from deals, interviews, search behavior, procurement, and product use provides a stronger boundary. 1. **State the customer decision.** Name the audience, problem, use case, budget, geography, and time period. A company may compete in one segment and rarely appear in another. 2. **Collect observed alternatives.** Review win-loss notes, sales calls, customer interviews, review sites, search results, requests for proposal, partner conversations, and public material. Include the status quo when buyers often delay or decline change. 3. **Classify the relationship.** Direct competitors offer a similar approach. Indirect competitors solve the same job through another category. Substitutes change the workflow. Potential competitors have assets or access that could let them enter. 4. **Record the basis.** For each competitor, state where it appears, which buyer considers it, and what evidence supports the classification. Date the observation. 5. **Connect the definition to action.** Use the set for positioning, product choices, sales preparation, content, pricing, partnership, or market entry. Change the set when the decision changes. - Whether the analysis concerns a category, deal, segment, channel, or strategic threat. - Which buyer evidence qualifies an option for inclusion. - How direct, indirect, substitute, and potential competitors are separated. - Who maintains pricing, product, claim, and market-entry evidence. - Which findings can support public comparisons and which remain internal. - How uncertainty and regional variation will be shown. A useful competitor definition limits the research burden. It keeps a sales battlecard focused on options that enter real deals. It prevents product teams from copying features from companies whose customers and job differ. It also helps marketers explain the category without presenting a company-authored list as independent consensus. Maintain separate sets when needed. A broad strategic watchlist can monitor possible entrants, while a current deal set supports sellers. Combining both into one ranking gives distant threats the same weight as daily alternatives. Teams often define competitors through internal familiarity. The same three brands appear in every deck, so research confirms what the company already believes. Meanwhile, buyers compare an agency, spreadsheet, internal hire, or adjacent platform that no one monitors. A better definition starts with observed buyer choice and preserves the source. The team can still track strategic entrants, but it labels them accordingly. When a new alternative appears repeatedly, the evidence changes the set. Competitor research then follows the market rather than the organization's memory. Assign owners to the underlying evidence rather than to a slide deck. Product marketing may own positioning and sales guidance, while research monitors market structure and RevOps summarizes deal outcomes. Every claim should have a source, date, applicable segment, and next review trigger. Public comparisons need the same standard plus balanced treatment and a clear commercial disclosure. Use short update paths. When a seller observes a new alternative, capture the account, segment, buyer role, decision stage, and result. One mention enters the record. A repeated pattern can trigger research and an update. This avoids changing the entire competitor set from a single anecdote while still respecting field evidence. Archive superseded claims. A competitor's old price or feature can linger in copied documents long after the source changed. Sales should have one current view and visible uncertainty. The best battlecard explains where an alternative fits, its credible strength, the question that reveals fit, and the evidence behind the distinction. After a positioning change, sales play, or product response, check whether buyer behavior changed. Look at consideration sets, objections, win-loss reasons, discounting, and time to decision. Competitive guidance improves when the team learns which distinctions mattered in practice and which sounded useful only inside the company. --- # Competitor Sets in Business | Surface Glossary URL: https://surface.thesurface.network/glossary/competitors-in-business Competitors in business are organizations and alternatives that affect a company's ability to win a desired outcome. Customer-market competitors pursue the same buyers or budget. Channel competitors seek the same distribution or partner access. Supply competitors seek constrained inputs. Labor competitors recruit similar talent. Strategic competitors may enter from an adjacent category or bundle the product inside a larger offer. Most marketing work focuses on customer choice, but business strategy may require several competitive sets. Each set needs a clear boundary and purpose. A company that appears in a strategic watchlist may rarely appear in active sales deals. 1. **Separate the decisions.** Create distinct sets for positioning, product planning, sales support, market entry, partnerships, talent, or supply when the evidence differs. Avoid one master ranking that tries to serve every team. 2. **Assign evidence sources.** Use buyer interviews and deal records for sales competition. Use product releases, hiring, partnerships, patents, filings, and market activity for strategic monitoring. Keep the source and date beside every conclusion. 3. **Define update triggers.** Review an entry after a pricing change, acquisition, launch, channel move, repeated deal appearance, or segment expansion. A regular cadence catches slower changes. 4. **Distribute the right view.** Sellers need concise, current buyer-facing differences. Product leaders need capability and direction. Executives need threats, assumptions, and response options. Public comparison content needs evidence and fair disclosure. 5. **Record decisions.** Competitive information earns value when it changes a message, roadmap, qualification rule, partnership, price, or market choice. Track the action and later outcome. - Which competitive set owns each business question. - What evidence moves an organization into or out of that set. - Which teams maintain claims, pricing, product, and deal observations. - How sensitive internal information is separated from public sources. - Which conclusions are strong enough for customer-facing use. - How the organization will respond rather than monitor indefinitely. Competitor monitoring can become self-absorbed. Teams copy features, repeat rivals' category language, and spend meetings discussing launches that never enter a customer decision. The stronger use is to understand which choice the buyer is making and why the alternative is credible. Examine the job, risk, switching cost, proof, implementation burden, and organizational politics behind the comparison. Those factors often explain competition better than a grid of capabilities. A business builds an elaborate competitive intelligence program with alerts for every website change. The volume creates urgency but little judgment. Sales cannot find current answers, product teams distrust the summaries, and leadership receives activity instead of implications. A better program defines a few consequential signals and routes them to named owners. Every brief states what changed, which buyer or market it affects, the evidence, and the decision it may require. If no decision or assumption is affected, the update can remain in the record without interrupting the whole company. ## Maintain confidence levels Label competitive conclusions by evidence strength. A verified price on a current product page differs from a seller recollection. A repeated loss reason differs from one comment. A strategic inference from hiring and partnerships differs from an announced product. These sources can all inform action when their status remains visible. Set review frequency by volatility and consequence. Current pricing and product claims may need frequent checks for active deals. Category structure or supplier access may change more slowly. High-risk public claims deserve a fresh primary source before publication. Internal scenarios can include uncertainty as long as decision makers see it. Do not score competitors simply to create an ordered list. A weighted model can help when the criteria represent a real buyer or strategic decision, but hidden weights turn opinion into a number. Show the criteria, evidence, owner, and date. Use the result as a prompt for judgment rather than a substitute for it. Define a small set of plausible moves and responses. A competitor may lower price, enter a segment, bundle the category, acquire distribution, or change implementation. State which signal would make the scenario more likely and which option the company could take. Scenario work gives monitoring a purpose before an alert arrives. --- # Content Hub | Surface Glossary URL: https://surface.thesurface.network/glossary/content-hub ## What is a content hub? A content hub is an organized collection of pages, media, tools, or resources built around a defined subject and audience. A central page explains the topic and routes readers into narrower questions. Supporting pages add depth, evidence, examples, comparisons, or next steps. Internal links make the relationships visible to readers and search systems. A hub is an information architecture, not a folder full of posts. The pages need distinct jobs, clear paths, and a reason to exist together. A broad resource center may contain several hubs, while one detailed guide may act as the center of a smaller cluster. ## How a content hub works in practice 1. **Define the audience and subject boundary.** Name the people the hub serves, the decisions they face, and the questions that belong inside the topic. Exclude adjacent material that would make navigation vague. 2. **Map the question set.** Use customer conversations, search demand, sales objections, product knowledge, support issues, and competitive gaps. Group questions by intent and relationship rather than copying a keyword export into the site. 3. **Assign each page a job.** The hub page provides orientation. Definitions answer narrow vocabulary questions. Guides explain processes. Comparisons support evaluation. Proof, tools, and product pages help a reader act. Overlapping pages should be consolidated or given visibly different purposes. 4. **Design the paths.** Link from the central page to each major branch and between supporting pages when a real reader would need the connection. Use descriptive anchor text. Include a route back to the hub and a next step that matches the page's intent. 5. **Maintain the system.** Track broken links, orphan pages, stale claims, search performance, engagement paths, assisted conversions, and new questions. Refresh the map when the audience or product changes. - Whether the hub serves learning, evaluation, conversion, customer education, or several clearly separated jobs. - Which page owns each primary question and which pages provide supporting detail. - How taxonomy, navigation, URLs, breadcrumbs, and templates express the structure. - Which evidence or expert owns factual review for each branch. - How the team will retire weak pages without breaking useful routes. - Which behaviors show that the hub helped a reader move forward. Traffic to the central page is only one signal. Review whether supporting pages gain discovery, whether readers move between relevant pages, whether search systems understand the topic set, and whether the hub leads to newsletter, product, demo, or sales interactions that fit the audience. Look for pages that attract entry traffic but leave readers with nowhere sensible to go. The hub should also make publishing easier. A writer can see where a new idea belongs, what already exists, and which internal links will help the reader. If every addition requires inventing a new taxonomy branch, the topic boundary may be too loose. Teams often build a hub by placing a large hero page above dozens of loosely related articles. The page links outward, but the articles duplicate one another, ignore the hub, and send every reader to the same generic call to action. The structure looks complete in a diagram and feels disconnected in use. A better hub begins with a smaller question map and explicit page ownership. It adds material only when the new page answers a distinct need. Editors review paths during every update, and analytics show where people enter, continue, convert, or abandon the subject. The hub then operates as a maintained part of the content system rather than a launch project. Give the hub a named editor who owns its boundary, inventory, and review cadence. New-page requests should identify the reader question, existing page that comes closest, evidence, internal-link plan, and action the page supports. This creates a lightweight test for whether the idea deserves its own URL. Track content debt beside new production. A hub with fifty pages can lose more value through stale claims, broken paths, and overlap than it gains from a sixth article on the same question. Reserve capacity for refreshes, mergers, redirects, navigation changes, and evidence updates. Record why a page was consolidated so a future contributor does not recreate it under a new title. Review the hub with search, product, sales, and customer evidence. Search demand may reveal a missing definition, while sales calls reveal an evaluation question with little search volume. The hub should reflect both discoverability and the decisions real buyers need to make. --- # Content Marketing Analysis | Surface Glossary URL: https://surface.thesurface.network/glossary/content-marketing-analysis ## What is content marketing analysis? Content marketing analysis examines whether a content portfolio reaches the intended audience, answers useful questions, supports buyer decisions, and contributes to business outcomes. It combines asset-level performance with portfolio structure, search and AI visibility, distribution, conversion behavior, sales use, production effort, freshness, and content quality. The analysis may occur during a periodic review, before a strategy change, or after a specific campaign. It is broader than an inventory and more diagnostic than a dashboard. A list of URLs shows what exists; analysis explains which audience and decision each asset serves, what evidence indicates, and what action should follow. ## Why content analysis matters Publishing creates a cumulative system. Older pages may keep earning qualified visits, compete with newer pages, contain stale claims, or leave buyers at a dead end. Looking only at recent output rewards production while ignoring the library. Looking only at traffic favors broad educational pages and can hide low-volume material that repeatedly helps sales close complex deals. Define the portfolio boundary and normalize URLs, formats, dates, owners, audiences, topics, funnel jobs, conversion paths, and costs. Join search, analytics, CRM, email, and sales-use evidence only where identity and definitions permit it. Compare assets within a fair peer group. A product comparison should not be judged by the same traffic expectation as a broad definition page. Assign each asset an action: keep, refresh, consolidate, redirect, repurpose, redistribute, improve conversion, investigate, or retire. Attach the reason, owner, dependency, and expected result. Review clusters and journeys as well as individual URLs because the problem may be missing connections rather than weak pages. Preserve annotations for launches, migrations, tracking changes, and campaign pushes so a time-series movement has context. A software company finds 42 articles about analytics reporting. Several rank for similar queries, but only two lead readers toward the product's reporting workflow. The team consolidates overlapping definitions, updates the strongest hub, adds links to customer evidence, and keeps a niche implementation article that sales uses often. Success is judged through qualified entry traffic, assisted meetings, seller use, and maintenance cost. Content marketing analysis should end with a portfolio decision, not another collection of charts. --- # Content Marketing Lifecycle | Surface Glossary URL: https://surface.thesurface.network/glossary/content-marketing-lifecycle ## What is the content marketing lifecycle? The content marketing lifecycle is the sequence through which a content idea becomes a maintained business asset. It includes research, prioritization, briefing, creation, expert review, editing, approval, publication, distribution, conversion design, measurement, refresh, reuse, consolidation, and retirement. The lifecycle continues after the publish date because claims age, products change, links break, and audience questions develop. Teams use the lifecycle to coordinate strategy, subject expertise, creative work, CMS operations, search, distribution, analytics, sales use, and governance. A publish-only process rewards output while hiding quality and maintenance costs. Writers may create pages that overlap existing material. Reviewers may approve claims without a future owner. Distribution may arrive late. Old pages may keep attracting visitors after the facts or conversion path have changed. A visible lifecycle gives every asset a purpose, source, owner, state, and review condition. It also makes revision and retirement legitimate work rather than an afterthought. Begin with a documented audience question and content job. Check the existing inventory before approving a new page. Record the brief, evidence, experts, dependencies, internal links, CTA, and success measures. Use clear review states and preserve comments or decisions that future editors will need. After publication, distribute according to the audience and monitor discovery, engagement, conversion, sales use, and factual freshness. Set a review date or trigger. Consolidate pages that compete for the same job and redirect retired URLs where appropriate. A technical guide begins with sales-call questions and product documentation. An engineer checks the claims, an editor shapes the explanation, and the content lead links the guide to related definitions and a product page. Email and sales distribute it after publication. Six months later, a product change triggers review. The team updates screenshots and examples, keeps the URL, and records the new review date instead of publishing a duplicate guide. Use measures that fit each state. Production may track cycle time, revision, and blocked work. Publication checks technical completeness. Distribution tracks qualified reach and engagement. Commercial review examines conversion and sales use. Maintenance tracks freshness, broken paths, overlap, and declining performance. Retirement tracks redirects and recovered traffic. One score cannot describe the health of every stage. --- # Content Pillar | Surface Glossary URL: https://surface.thesurface.network/glossary/content-pillar ## What is a content pillar? A content pillar is a strategic topic a company chooses to cover deeply and consistently, often supported by a central pillar page and a cluster of narrower assets. The pillar connects audience need, business relevance, expertise, search demand, internal links, proof, and a useful next step. The term is sometimes used for a recurring editorial theme, such as customer education or industry research. In SEO, it more often refers to the main topic and anchor page of a content hub. Both uses require a durable idea broad enough to support several pieces and specific enough to create a recognizable position. ## How a content pillar works in practice Choose the pillar from a buyer problem the company can credibly own. Define the core belief, map educational and commercial questions, identify existing evidence, and assign each page a distinct job. The anchor should orient readers, while supporting pages handle depth, comparison, implementation, proof, and conversion. 1. Select a topic tied to a real product, market, or revenue priority. Broad subjects such as marketing or AI are usually too diffuse to guide a coherent program. 2. Write the audience problem and the company's point of view in plain language. The pillar needs an argument or organizing method; a high-volume keyword alone is insufficient. 3. Map the question set by intent. Include definitions, methods, comparisons, objections, use cases, implementation, measurement, proof, and the commercial decision where relevant. 4. Audit existing pages and decide which asset will anchor the hub. Refresh, consolidate, redirect, or retire overlapping pages before adding more inventory. 5. Plan internal links, distribution, sales use, conversion paths, ownership, and refresh dates. Measure the group as a system while preserving page-level diagnostics. Track coverage of the intended question set, organic and AI visibility, internal movement, returning visitors, conversions, assisted pipeline, backlinks, sales use, and freshness. A pillar can be strategically useful before it wins a high-volume ranking if it improves category clarity and gives campaigns a shared source. For a content pillar, keep a page-level decision record and a cluster-level map. The page record should state audience, intent, strategic job, source evidence, point of view, internal links, conversion path, distribution plan, sales use, reviewer, and refresh trigger. The cluster map should show which page owns each question and where comparison, proof, implementation, and product context live. This prevents several teams from producing separate assets that repeat the same education while leaving the buyer's next decision unanswered. Use separate measures for the correctness, reliability, efficiency, and business value of a content pillar. A process can be accurate on completed cases and still fail through delays or missing coverage. It can be reliable and still create little value. Report denominators, exclusions, time windows, and unresolved cases so leaders can see which part of the system actually improved. Review the process with the team that receives its output. Their acceptance, corrections, and workarounds reveal whether a content pillar functions in the real operating environment rather than only inside its source tool. Give the team receiving output from a content pillar a visible way to accept, correct, reject, or escalate it. Their response should return to the shared record with a reason and timestamp. Review those reasons by workflow version and segment. This feedback shows whether a content pillar is reducing work, moving the right cases, and preserving enough context for the next person to act. End the a content pillar review with open questions and their owners. An unresolved item can remain open, but it should not disappear into an apparently final configuration. - Which buyer problem and business priority make the pillar worth maintaining? - Which page is the anchor, and what job belongs on supporting pages? - Which claims require original evidence, expert review, or customer proof? - How will readers move from learning to comparison, proof, and conversion? - Who owns consolidation, internal links, distribution, and quarterly refreshes? A pillar should impose useful limits. If every new idea can fit under it, the category is too broad. If the team can answer the entire topic in one short post, it may be too narrow to support a durable hub. The common failure is building a giant page around a keyword and calling the result a pillar. Supporting articles repeat sections from the anchor, internal links all point upward, and no page addresses comparison or proof. The site gains volume without giving a reader a path through the topic. Return to buyer questions and assign each page a separate purpose. Cut repeated material from the anchor, add lateral links, connect the educational layer to proof and a relevant conversion page, and schedule updates around real product and market changes. --- # Content Production | Surface Glossary URL: https://surface.thesurface.network/glossary/content-production ## What is content production? Content production is the coordinated work of creating a content asset from an approved idea, evidence, and brief. It can include research, interviewing, outlining, writing, design, recording, editing, expert review, fact-checking, legal or brand approval, CMS entry, accessibility, technical checks, publication, and distribution. The production process depends on the format and risk. A glossary definition, benchmark report, customer story, video, product page, and campaign landing page need different experts, evidence, review, and delivery work. ## Why content production needs an operating system Content crosses several roles and tools. Unclear ownership creates version conflicts, late feedback, missing sources, broken links, and rushed publishing. A visible process helps the team distinguish draft work from approved claims and understand which dependency blocks release. Good production also preserves the material needed for future revision. Source notes, interviews, visual files, approvals, and publication settings should remain findable after launch. Define the audience, content job, format, evidence, owner, reviewers, deadline, distribution, internal links, conversion path, and success measures before work begins. Use a clear state model such as planned, drafting, expert review, editing, approved, scheduled, published, and refresh due. Give reviewers a specific question and a deadline. After publication, check rendering, metadata, links, analytics, and distribution. Record the next review condition rather than treating the asset as finished forever. A company produces an industry report from a customer dataset. Analytics validates the method, legal reviews privacy, a subject expert interprets the findings, an editor shapes the narrative, and design builds charts from approved numbers. The web producer checks tables, alt text, metadata, links, and conversion tracking. Source files and definitions stay attached to the project so the next edition can explain what changed. Estimate work by format, evidence, review, and risk rather than by asset count alone. One technical case study may need more expert and legal time than several definitions. Limit concurrent work so reviewers can respond while context is fresh. Track blocked time, revision cycles, and post-publication defects. Capacity planning should protect judgment and maintenance, not turn people into a publishing queue. --- # Content Strategy and SEO | Surface Glossary URL: https://surface.thesurface.network/glossary/content-strategy-and-seo ## How do content strategy and SEO work together? Content strategy and SEO work together when audience need, business priority, expertise, information architecture, and search behavior shape the same publishing plan. Content strategy decides which ideas deserve investment and how they support a buyer. SEO supplies evidence about demand, intent, competition, crawlability, internal links, and page structure. Neither discipline can substitute for the other. A keyword list does not decide what the company believes or which page should convert. A thoughtful editorial calendar may remain invisible if the site cannot be crawled, the topic language does not match how buyers search, or several pages compete for the same job. ## Why content strategy and SEO matter The combined model prevents two expensive outcomes: content that ranks for irrelevant traffic and strong expertise that no one can find. It also improves AI visibility because connected coverage, clear entities, useful answers, and source-worthy evidence support retrieval across more than one interface. Start with the buyer question and business objective, then research the query set and current result environment. Assign a page type and strategic job, create a brief with source and internal-link requirements, publish into a hub, and measure both visibility and downstream movement. Refresh pages when evidence, intent, or the business changes. ## How to use content strategy and SEO in practice Operational use of content strategy and SEO requires more than publication. Assign its source material, reviewer, related pages, channel adaptations, sales use, success signals, and owner for factual updates. Keep the source beside the result and make changes reversible. This protects the operation when a definition, vendor, model, template, or buyer behavior changes after the original decision. The final review should ask what changed for a buyer or operator. If content strategy and SEO only creates another field, page, prompt, or dashboard, its role remains incomplete. A company wants to own a new operations category. Search research shows definitional, comparison, implementation, and software-evaluation queries. The team builds a pillar guide, supporting pages for each intent, customer proof, and one conversion page. SEO informs the architecture, while strategy decides the point of view and commercial path. SEO should make content strategy legible to search systems and search behavior legible to content teams. The shared goal is useful discovery that leads somewhere relevant. --- # CRM and Marketing Automation | Surface Glossary URL: https://surface.thesurface.network/glossary/crm-and-marketing-automation CRM and marketing automation work together by connecting customer and account records with triggered communication, segmentation, scoring, routing, and campaign measurement. The CRM usually preserves relationship and pipeline history. The automation layer uses that history and current behavior to decide what should happen next. The boundary varies by platform. Some suites combine both capabilities, while other companies use a CRM, a separate marketing automation platform, and specialized systems for forms, enrichment, routing, or scheduling. The key operating question is which system owns each field and action. A reliable connection gives marketing current sales context and gives sales the history behind a lead. A poor connection creates duplicate contacts, conflicting stages, delayed ownership, and campaigns that continue after a person has converted or opted out. Define shared identifiers, field mappings, source precedence, sync direction, timing, consent behavior, and error handling. Keep campaign membership and lifecycle history visible. Test record creation, updates, merges, deletes, manual overrides, and re-entry before launching a workflow at scale. A useful application of CRM and marketing automation separates observed facts, participant reports, modeled estimates, and internal interpretation. Those forms of evidence can inform the same decision without being treated as equivalent. Choose a measure that follows the actual job. Validity, coverage, reviewer effort, conversion, response time, source quality, and revenue can describe different outcomes and should stay separate. A short decision record should state the current approach, evidence, owner, date, and condition for revision. That makes CRM and marketing automation useful beyond the person who first implemented it. A prospect attends a webinar and later requests a demo. Marketing automation records the campaign interaction and sends the qualified request to the CRM. The CRM assigns the account owner and changes the lifecycle stage. That update immediately suppresses the webinar nurture and starts a meeting-confirmation workflow with sales context. The integration should preserve one understandable customer story. If each platform tells a different version of stage, owner, consent, or source, adding more automation will deepen the disagreement. --- # CRM Marketing Automation | Surface Glossary URL: https://surface.thesurface.network/glossary/crm-marketing-automation CRM marketing automation is the use of CRM records, lifecycle fields, activity history, and workflow rules to execute marketing actions. Common examples include assigning a lead, starting an email sequence, creating a task, updating a stage, adding a campaign member, or alerting sales when a buyer meets defined conditions. The CRM usually acts as a system of record, while a marketing automation platform or action layer may execute the campaign. The distinction depends on the stack. What matters is that both systems share definitions, identifiers, consent status, and a clear rule for which platform may change each field. Automation turns customer data into consistent timing and follow-up. It also amplifies bad records and confused ownership. A stale lifecycle stage can send an inappropriate nurture email, while two systems writing the same field can bounce a lead between workflows. Define the trigger, eligibility, exclusions, action, owner, and success measure for each workflow. Use a stable record ID, check consent and suppression before messaging, and record the reason an action occurred. Test re-entry, duplicates, delayed syncs, and manual overrides rather than assuming the happy path. Use CRM marketing automation to support one named decision. Record the population, market boundary, source type, collection date, method, and limitations so a later reader can judge whether the evidence still applies. Review a sample of real cases before relying on an aggregate score. The sample should include incomplete, conflicting, and high-value records because averages often hide the failures with the largest business cost. Place the documentation for CRM marketing automation beside the workflow or decision it affects. That keeps definitions, evidence, ownership, and later corrections available to the people who need them. A qualified demo request enters the CRM with product interest and territory. An automation assigns the correct rep, sends a contextual confirmation, starts a response timer, and reassigns the record if the owner is unavailable. A disqualified request enters a separate educational nurture and never receives a meeting link. CRM automation should make the record easier to trust after the workflow runs. If the action leaves no reason, timestamp, owner, or exception state, the team will struggle to diagnose the next failure. --- # Customer Acquisition | Surface Glossary URL: https://surface.thesurface.network/glossary/customer-acquisition Customer acquisition is the process of attracting an appropriate audience, earning interest, converting that interest into a buying motion, closing the purchase, and beginning the customer relationship. It includes marketing channels, offers, capture, qualification, sales work, commercial terms, and the first handoff into onboarding. A lead is an intermediate record. Acquisition is complete when the business gains a customer under its stated definition, which might be a signed contract, paid account, activated subscriber, or completed first transaction. Teams should state that point explicitly because cost and conversion calculations change when the endpoint changes. Map the path from market and audience through first value. Give each channel a job, define what qualifies a response, connect marketing context to sales, and measure cohorts through customer creation. The acquisition system should account for sales capacity, deal size, conversion delay, early retention, and the sources that repeatedly produce poor-fit customers. 1. Choose the customer segment and buying problem. Define fit using evidence the company can collect and use during qualification. 2. Create demand and capture existing intent. Coordinate content, paid programs, outbound, partners, events, referrals, and product experiences around the same market position. 3. Convert attention into usable records or product actions. Preserve source and content context, reduce unnecessary friction, and request only the information needed for the next decision. 4. Qualify, route, and sell. Assign ownership quickly, share the buyer's expressed need, and give marketing structured reasons when sales rejects, recycles, or advances the record. 5. Confirm customer creation and early quality. Connect acquisition source to contract, activation, retention, expansion potential, and service cost by cohort. Common measures include visitor-to-lead conversion, qualified rate, meeting rate, opportunity creation, win rate, sales cycle, customer acquisition cost, payback, activation, and early retention. Compare them by segment and source. A channel with expensive leads can have strong economics if those leads close and remain customers. Keep ownership visible at every transition. Marketing owns the audience, message, and capture quality; operations maintains records and routing; sales owns discovery and the commercial process; customer teams expose whether the promise matched the early experience. The exact division varies, but no stage should end with an unowned queue. Review complete paths, including losses. Sample new customers, rejected leads, stalled opportunities, and customers who churned quickly. Preserve the campaign, page, offer, form response, enrichment, routing decision, sales outcome, and onboarding result. This record lets the next acquisition decision respond to customer quality instead of channel volume alone. - What event counts as a newly acquired customer? - Which segments and buying situations fit the product and economics? - Which signals justify human follow-up or a product-led path? - How quickly must each type of response receive an owner and action? - Which post-sale outcomes will feed back into acquisition choices? Acquisition targets should reflect capacity. Increasing demand while sales queues grow or onboarding quality falls can raise reported volume and damage conversion. Set limits for spend, response time, sales load, discounting, and implementation so the program does not create customers the company cannot serve well. A common failure is optimizing the first visible conversion. Marketing lowers form friction and buys cheaper traffic, then celebrates lead volume while sales receives poor-fit records and response time stretches. Another failure counts signed customers without examining discounts, activation, or early churn, which makes acquisition appear healthier than its economics. Reconnect source data to accepted leads, opportunities, customers, and early retention. Tighten audience and offer choices, repair routing, and stop sources that repeatedly create unproductive work. Growth comes from a complete path that the organization can support, not from pushing more records into its weakest handoff. Set a review window long enough to observe sales and customer outcomes, then compare cohorts under the same definition. The acquisition team should document which changes improved fit, which merely shifted attribution, and which created extra work elsewhere. That record keeps the next budget decision grounded in customers rather than the loudest channel dashboard. It also gives finance and sales a common basis for changing targets. --- # Customer Acquisition Process | Surface Glossary URL: https://surface.thesurface.network/glossary/customer-acquisition-process The customer acquisition process is the connected set of activities used to identify a market, create and capture interest, evaluate fit, support a purchase, and begin the customer relationship. Marketing, sales, partnerships, product, finance, and onboarding may all participate. The process ends at a defined customer event, such as a signed contract, paid order, or activated account. Acquisition is often drawn as a funnel, but real B2B buying includes repeated visits, several people, offline conversations, procurement, security review, and periods of inactivity. The operating process must preserve account context as individuals enter through different channels. It should also distinguish new customers from expansions, renewals, partners, applicants, and existing users requesting help. Design the process backward from a customer definition and acceptable economics. Name the audience, problem, buying group, entry paths, qualification choices, sales stages, approval requirements, and onboarding handoff. Each stage should describe an observable customer or company state rather than an internal activity alone. Owners need exit criteria and a path for cases that do not follow the standard route. 1. Define the market and acquisition goal. State the segment, offer, geography, new-customer event, revenue expectation, capacity, time horizon, and exclusions. 2. Create and capture appropriate demand. Use content, paid programs, outbound work, partnerships, product experiences, referrals, or events according to how the audience discovers and evaluates options. Preserve source and intent context. 3. Qualify and route the opportunity. Combine stated need, account fit, timing, behavior, and existing relationship. Assign an owner, service level, and fallback without treating an opaque score as the decision itself. 4. Support evaluation and purchase. Coordinate discovery, proof, stakeholder material, commercial terms, security or procurement, and follow-up. Record stage entry and exit through buyer evidence. 5. Confirm the customer and hand off context. Define when acquisition is complete, transfer commitments and decision history to onboarding or delivery, and feed outcome and loss reasons back into targeting. Measure both flow and economics. Useful views include qualified response, speed, acceptance, meeting and opportunity conversion, stage movement, win rate, cycle time, acquisition cost, payback, initial margin, early activation, and cohort retention. Break results by segment and channel only when attribution and sample size support the comparison. A cheap customer who churns quickly may be an expensive acquisition. Create a shared stage dictionary with owner, entry evidence, exit evidence, required fields, maximum age, allowed transitions, and exception path. Reconcile marketing, CRM, billing, and product customer definitions. Review a sample of won, lost, stalled, and disqualified records, including the underlying conversations. Finance should agree on acquisition-cost inputs, while customer teams should report whether promises and context survived the handoff. Keep a change log for stage rules and channel definitions so historical comparisons do not silently mix different processes. - What event defines a new customer for operations and measurement? - Which segments, channels, and offers fit the company's economics and capacity? - How will account identity, buying groups, qualification, and ownership work? - Which evidence moves a buyer between stages? - What information and commitments must reach onboarding or delivery? Stage design should match the buying motion. A self-service product may observe signup, payment, and activation within hours. An enterprise sale may require legal, security, procurement, and executive approval over months. Forcing both through one set of stages distorts conversion and obscures where work is stuck. Shared reporting can roll up distinct motions after each is defined honestly. A common failure is optimizing the earliest measurable conversion while ignoring downstream quality. Marketing reduces form friction and declares success, sales receives more poor-fit requests, and onboarding absorbs customers who never reach useful adoption. Another failure counts every influenced contact as a separate acquisition when several people belong to one buying account. Trace one customer cohort through the full process and reconcile identity, stage dates, costs, outcomes, and handoffs. Compare the operational record with customer and seller accounts of what happened. Repair the definition or transition where evidence disappears, then change channel investment only after the downstream effect can be seen. --- # Customer Acquisition Strategy | Surface Glossary URL: https://surface.thesurface.network/glossary/customer-acquisition-strategy A customer acquisition strategy is the set of choices a company makes to win suitable new customers at acceptable economics. It defines target segments, the problem and position, the offer, channel roles, the conversion and sales path, the investment envelope, and the feedback used to change the next round of work. Channel plans list where marketing will spend. Acquisition strategy explains why a segment should respond, how the company will earn trust, which conversion matches the buying motion, and whether sales and onboarding can support the volume. It also states which customers the company does not want to acquire. Build the strategy around one market and a diagnosed growth constraint. Set economic and capacity limits, map how the buying group learns and decides, then combine channels that create demand, capture intent, provide proof, and convert. Connect post-sale quality to the source so the portfolio improves over time. 1. Define the segment, buying group, problem, alternatives, and evidence of fit. Use a market boundary narrow enough to guide message and channel choices. 2. Set acquisition economics and operating limits. Record expected deal value, gross margin, sales cycle, conversion delay, payback tolerance, sales capacity, and onboarding constraints. 3. Design the position, offer, and conversion path. Match the request to buyer readiness, then plan the proof and internal support needed before a purchase. 4. Assign channels distinct roles and budgets. A portfolio may use content for education, search for intent capture, events for depth, outbound for concentrated accounts, and partners for borrowed trust. 5. Measure cohorts through revenue and early customer quality. Reallocate investment based on accepted demand, wins, activation, retention, and learning rather than the cheapest first response. Track volume and efficiency across the full path: reach, engaged visits, responses, qualified records, meetings, opportunities, wins, acquisition cost, payback, activation, and early retention. Review by segment, offer, and source. Attribution will remain imperfect, so pair model outputs with experiments and direct buyer evidence. Write the strategy in a decision ledger instead of a channel deck. For each bet, state the audience, belief, evidence, investment, expected behavior, owner, time horizon, and stopping condition. Keep campaign metrics close to sales outcomes, and preserve rejection and loss reasons in structured form so they can change targeting, message, or follow-up. Review the portfolio at the pace its channels can produce evidence. Paid search may support weekly adjustments; category content and partner programs need a longer horizon. Distinguish execution failure from strategic failure. Poorly built landing pages do not disprove the segment, while repeated poor-fit customers across several channels may challenge the market choice itself. - Which customer segment can the company serve profitably and credibly? - Which growth constraint should the strategy address first? - What conversion and sales motion fit the buyer's level of commitment? - How will channels create, capture, and convert demand together? - Which customer-quality signals will change future investment? The strategy should make tradeoffs visible. No company can maximize reach, qualification, sales speed, and message specificity at the same time. State which outcome leads for the current stage and what performance would justify a different balance. Treating last year's channel mix as strategy is a common failure. Budget rises across paid, content, events, and outbound without a new market belief or diagnosed constraint. Each team optimizes its own conversion while the combined system produces more records than sales can work and too few customers worth retaining. Narrow the segment and map one complete path from first exposure through early customer value. Remove activity that has no defined job, repair the weakest handoff, and run a small set of measurable bets. Feed sales and customer outcomes back into the audience, offer, and channel choices before adding spend. Record what the company learned even when a bet underperforms. Failed channel tests may expose poor message, weak proof, limited reach, or the wrong conversion. Keeping those possibilities separate prevents the team from abandoning a viable market because one execution failed, or repeating an attractive tactic that never produced suitable customers. --- # Customer Data | Surface Glossary URL: https://surface.thesurface.network/glossary/customer-data Customer data is information a company holds about people and organizations that buy, use, evaluate, or interact with its products and services. It can include identity and account records, stated preferences, contract history, support conversations, marketing engagement, product events, billing activity, and consent choices. Each item should retain its source and permitted use. The label often hides several different data grains. Contact records describe people, account records describe organizations, and events record things that happened at a time. Combining them without clear identifiers can assign one person's behavior to the wrong account or treat an anonymous visit as a confirmed customer action. Customer data influences segmentation, personalization, routing, forecasting, service, and product decisions. Errors can send irrelevant communication, inflate account activity, conceal churn risk, or expose information to people who should not see it. Quality therefore includes accuracy, completeness, timeliness, identity resolution, lineage, access, retention, and lawful use. Document the source and authority for each important field. Billing may control contract status while the product controls usage events and the CRM controls account ownership. Define stable identifiers and rules for people who change companies, subsidiaries that share a domain, duplicate contacts, deleted accounts, and anonymous users who later identify themselves. Preserve raw events separately from interpreted customer states. Collect only what supports a clear purpose. Validate data at entry, monitor integrations, and give operators a path to correct records without erasing history. Restrict sensitive fields by role and propagate consent or deletion changes to dependent systems. When analysts build a customer metric, they should state the population, unit, period, exclusions, and source version so another person can reproduce it. One SaaS company wants to identify accounts ready for expansion. The model joins licensed seats, weekly active users, feature adoption, renewal date, support severity, and contract tier at the account level. Before acting, the team excludes internal users, resolves parent and child accounts, and checks whether product events arrive late. Account managers receive the evidence behind each signal rather than a score alone. Customer data becomes usable when every important fact has a defined subject, source, time, owner, and permission boundary. --- # Customer Data Governance | Surface Glossary URL: https://surface.thesurface.network/glossary/customer-data-governance Customer data governance is the system of ownership, definitions, policies, controls, and review used to manage information about prospects, customers, users, contacts, and accounts. It covers collection, identity, consent, access, quality, enrichment, lifecycle stage, usage, sharing, retention, correction, and deletion. The purpose is to make customer data useful without treating every available field as safe, accurate, or appropriate for every action. Governance connects privacy and security obligations with everyday marketing, sales, service, product, and analytics work. Customer records trigger real experiences. A wrong account match can assign the wrong salesperson. A stale lifecycle stage can send prospect email to a customer. An unclear consent field can expose the company and ignore the person's preference. An inferred attribute can influence qualification even when the source is uncertain. Governance makes these consequences visible and gives teams a shared method for resolving them. Assign owners to identity, account, consent, lifecycle, source, product use, and revenue domains. Define systems of record, source precedence, permitted uses, access, quality thresholds, and correction paths. Keep original values and provenance where enrichment or models add information. Set retention and deletion rules by purpose and jurisdiction. Monitor duplicates, failed syncs, unknown owners, missing consent, stale stages, reversed matches, and downstream actions caused by governed fields. A company enriches inbound leads with firmographic data. Its governance rules keep the submitted company name, record the enrichment provider and date, and require review before an uncertain match changes account ownership. Consent remains independent from enrichment. Revenue operations owns the account field, legal owns permitted-use policy, and marketing operations monitors workflow errors. The data can still move quickly because authority and exceptions are clear. Before a field drives a message, score, route, model, or report, ask where it came from, who owns it, how current it is, whether the person expects this use, and what happens if it is wrong. Define a safer fallback for missing or uncertain values. A company should be able to correct the record and trace the actions the old value caused. --- # Customer Lifecycle Marketing | Surface Glossary URL: https://surface.thesurface.network/glossary/customer-lifecycle-marketing Customer lifecycle marketing adapts communication, education, offers, and human outreach to a customer's changing relationship with a company. It commonly covers onboarding, activation, adoption, retention, renewal, expansion, advocacy, lapse, and reactivation, using account and product context rather than a fixed email schedule. Lifecycle marketing can include prospects and customers. Customer lifecycle marketing concentrates on the post-purchase period, where product use, service history, account health, contract timing, and role changes matter more than the original lead source. Marketing, customer success, product, support, and sales may all participate. Map the moments where communication can help a customer make progress. Define the state and evidence for each moment, decide which team owns the action, and coordinate channels so customers do not receive conflicting requests. The system should react to meaningful behavior while leaving room for account-specific judgment. 1. Define customer stages through observable changes in need or value, such as activation, first successful use, adoption threshold, renewal window, or loss of activity. 2. Identify the questions and risks at each stage. Use support records, product behavior, customer interviews, renewals, and success notes to understand what blocks progress. 3. Design communication and handoffs. Specify audience, trigger, exclusions, message, channel, owner, delay, exit, and the action a customer can take. 4. Coordinate systems and teams. Reconcile account and contact identity, protect consent and frequency limits, and make human outreach visible to automated programs. 5. Measure progression by cohort. Review activation, adoption, time to value, renewal, expansion, complaints, engagement, and the reasons customers stall or leave. Email engagement may help diagnose delivery and relevance, but customer outcomes lead. Measure the behavior or relationship the program intends to change, then compare eligible cohorts. Account for plan type, tenure, implementation model, customer size, and seasonality before attributing a difference to the campaign. Give each lifecycle program a business owner and an operational owner. The business owner defines the customer need and desired outcome; the operational owner maintains data, logic, testing, and exceptions. Customer-facing teams should be able to see why a person entered a program and stop it when the account context makes the message inappropriate. Maintain a lifecycle dictionary apart from temporary campaign status. A customer can be active while paused in one education sequence, or near renewal while a product user is still onboarding. Using one field for both concepts causes accidental exits and misleading reports. Review stage definitions when the product, contract model, or customer journey changes. - Which observable customer states require different communication or ownership? - Which product, contract, support, and relationship signals are trustworthy enough to use? - When should software act, create a task, wait, or defer to a person? - How will contact-level behavior roll up to an account-level decision? - Which customer outcome will determine whether a program continues? Frequency and tone should reflect the relationship. A customer working through an outage or unresolved support issue should not receive an upbeat expansion campaign because a usage threshold fired. Build suppressions for sensitive states and give customer teams a visible override. A common failure is translating a journey-map workshop directly into static drip sequences. Customers move at different speeds, hold several roles, and encounter exceptions the diagram did not include. The system keeps sending the planned content after the need has passed, while customer teams start separate communication that automation cannot see. Replace time-only steps with meaningful state changes, add exits and suppressions, and connect customer-facing activity to the shared record. Start with one stage where the team can observe progress. Review stalled and harmed accounts, then change the trigger, message, ownership, or product experience that created the result. Keep a small holdout or phased rollout when the program is large enough to support one. Where that is impractical, compare matched cohorts and combine the result with direct customer evidence. Document interventions from success, support, or product teams so marketing does not claim credit for movement created elsewhere in the relationship. Review customers who received the program at the wrong moment as carefully as successful cases. --- # Customer Research Methods | Surface Glossary URL: https://surface.thesurface.network/glossary/customer-research-methods Customer research methods are the techniques used to learn how customers understand a problem, choose among options, use a product, experience service, and evaluate results. Common methods include interviews, contextual inquiry, observation, diary studies, focus groups, surveys, usability tests, concept tests, customer advisory groups, support analysis, win-loss research, journey studies, and behavioral data analysis. Each method captures a different kind of evidence. Interviews reveal language and reasoning. Observation reveals work people may forget to mention. Surveys estimate the prevalence of a known pattern. Product and transaction data record behavior inside the systems being measured. Generative methods help teams discover needs, constraints, and possible explanations. Evaluative methods test a defined product, message, or experience. Qualitative methods provide depth and context. Quantitative methods measure distribution or difference. Longitudinal methods follow change over time, while a cross-sectional study captures one period. No method is universally superior. A large survey can measure the wrong concept precisely, and five thoughtful interviews cannot estimate an entire market. Begin with the decision and the uncertainty. Define whose experience matters, including users, buyers, administrators, former customers, and people who rejected the product. Select a method that can reach that population and produce the needed evidence. Plan recruitment, consent, incentives, recording, analysis, and storage before collection begins. Combine methods when the decision is consequential. Report disagreements between sources instead of smoothing them into one confident answer. A payroll platform sees customer churn after the first renewal. Support analysis finds recurring permission questions. Interviews show that administrators struggle to train managers. Usage data confirms low adoption of delegated workflows. A usability test then compares two permission designs. The team addresses training and interface problems because the combined evidence explains both the reported frustration and the observed behavior. Customer research can overrepresent people who are available, satisfied, vocal, or close to the team. Recruit according to the decision. Include new and mature customers, active and inactive users, buyers and administrators, successful and struggling accounts, or former customers when their experience matters. Record who declined or could not be reached. The sample boundary belongs beside every conclusion drawn from it. --- # Data and Analytics Governance | Surface Glossary URL: https://surface.thesurface.network/glossary/data-and-analytics-governance Data and analytics governance is the operating discipline used to keep analytical data, metrics, models, and reports understandable and dependable. It assigns ownership, defines business terms and calculation rules, controls access, documents lineage, monitors quality, manages change, and records how exceptions are resolved. Data governance covers information across operational and analytical use. Analytics governance concentrates on the layer where raw events become dimensions, cohorts, metrics, dashboards, forecasts, and decisions. A source field can be valid while the report remains wrong because a join, filter, window, attribution rule, or denominator changed. Teams lose confidence when two dashboards give different answers to the same question and neither shows its method. Quiet definition changes can rewrite historical performance or trigger automation from a metric that no longer means the same thing. Governance makes disagreement traceable and gives changes an accountable route into dependent work. Create metric contracts for high-impact measures. Record owner, business definition, formula, grain, source, timezone, cohort window, exclusions, dimensions, freshness, access, lineage, tests, and change history. Reconcile important totals with source systems and keep unmatched records visible. Give analysts an exception path when the governed definition cannot answer a legitimate new question. Prioritize metrics used for compensation, budget, forecasting, customer communication, routing, or executive reporting. Review access and retention alongside analytical quality. When a definition changes, assess the effect on historical comparison, models, alerts, and downstream teams, then communicate the break rather than smoothing it away. Marketing and sales publish different opportunity conversion rates. The audit finds one calculation uses created date while another uses stage-entry date, and each excludes reopened opportunities differently. The teams agree on two clearly named metrics, publish the formulas and cohort rules, and preserve both views for the decisions each one supports. Analytics governance does not remove disagreement. It makes definitions, evidence, and authority clear enough to resolve disagreement productively. It also preserves the history needed to explain why a familiar number changed. --- # Data Cleaning | Surface Glossary URL: https://surface.thesurface.network/glossary/data-cleaning-and-why-is-it-important Data cleaning is the process of finding and resolving errors that make data unreliable for a particular use. The work may standardize formats, correct invalid values, merge duplicates, map categories, repair relationships, fill approved gaps, or quarantine records that cannot be trusted. Cleaning is important because analytics and automation repeat whatever the source data says. A duplicate account inflates pipeline, a malformed country value breaks territory routing, and an outdated job title changes qualification. The goal is fit for use, not a dataset that merely looks tidy. A sound process preserves raw values, defines the intended record and field rules, profiles the dataset, applies transparent transformations, and validates the result against business outcomes. High-risk changes such as account merges or lifecycle rewrites should remain reviewable and reversible. 1. Define the intended use and its quality threshold. A newsletter list and an enterprise lead-routing queue do not need the same level of completeness, freshness, or identity confidence. 2. Profile the data for missingness, invalid types, unusual distributions, duplicates, stale values, and broken joins. Segment errors by source so the team can repair the collection process as well as the records. 3. Write explicit cleaning rules. Normalize dates, domains, countries, titles, and categorical values while preserving the original field and recording which rule produced the new value. 4. Review uncertain changes. Fuzzy account matches, inferred employers, and conflicting enrichment values need a confidence threshold and an exception path rather than silent replacement. 5. Validate downstream behavior. Reconcile counts, rerun routing and reporting tests, sample changed records, and monitor whether the same error returns after the pipeline resumes. Track error rates before and after cleaning, records changed by rule, uncertain records sent to review, duplicate reductions, join coverage, and downstream exceptions. Business measures such as routing acceptance, contact rate, and report reconciliation show whether the cleanup improved the operation rather than only the table. Operational review of data cleaning should follow a record through the systems that consume it. Start at collection, then inspect enrichment, normalization, matching, CRM sync, routing, reporting, and retention. Sample records that passed every validation as well as records sent to exceptions. A valid field can still be wrong for the person, account, or time period, and a clean table can still break when identifiers connect it to the wrong entity. Set the review cadence for data cleaning according to volatility and consequence. Fast-changing inputs may need weekly checks, while stable reference material may suit a quarterly factual review. The owner should inspect input quality, output quality, timing, exceptions, and business outcome. Record which finding changes the rule and which finding only needs observation. Do not let the primary tool, spreadsheet, or configuration become the only documentation. A plain-language record of purpose and consequences makes data cleaning easier to audit, teach, change, and retire. Maintain an exception log for data cleaning that is small enough to review and structured enough to learn from. Capture the input, expected behavior, actual result, consequence, immediate repair, and root cause. Group recurring exceptions by source, rule, segment, template, or integration. This makes data cleaning improve through evidence and prevents the same workaround from being rebuilt by several teams in different tools. Keep a short data cleaning limitations note with the current process. It should name missing evidence, unsupported cases, and dependencies that could invalidate the approved approach. - Which use case defines the required level of data quality? - Which original values must remain available for audit or recovery? - Which corrections can be deterministic and which require confidence or review? - How will conflicting sources be prioritized without erasing provenance? - Who owns recurring source problems after the one-time cleanup ends? Cleaning rules encode business judgment. A title-normalization table, account-match threshold, or definition of duplicate is a policy even when it lives inside a script. Document and version those rules so the next operator can understand why records changed. The common failure is destructive cleaning. A team overwrites raw fields, merges similar accounts automatically, fills nulls with plausible defaults, and removes outliers because they complicate a report. The resulting dataset appears complete while losing evidence, uncertainty, and sometimes real customers. Restore or reimport the source, create separate cleaned fields, and apply rules in an auditable sequence. Route uncertain cases to review, fix the upstream form or integration, and measure whether the error rate falls over time. --- # Data Cleansing and Transformation | Surface Glossary URL: https://surface.thesurface.network/glossary/data-cleansing-and-transformation Data cleansing and transformation are related steps in preparing data. Cleansing identifies and repairs errors such as duplicates, invalid formats, stale values, and broken relationships. Transformation converts data into a required structure or representation, such as normalizing units, mapping categories, joining tables, aggregating events, or calculating derived fields. One operation can do both. Converting many country spellings into a controlled code repairs inconsistency and transforms the field. The distinction remains useful because a valid source value may still need transformation for analysis, while an invalid value needs a quality decision before conversion. Separating the steps improves auditability. Analysts can preserve the source, show the cleaned field, and show the derived business field. When a report changes, reviewers can locate whether the cause was corrected data, a new mapping, a different join, or a changed formula. Build a staged pipeline with raw, cleaned, normalized, and derived layers. Document rules and source precedence, test row counts and joins between stages, and keep transformations reproducible. High-risk merges or inferences should carry confidence and review status. The operating record for data cleansing and transformation should show the original value, proposed or cleaned value, rule, confidence, source, timestamp, and reviewer where needed. That history makes corrections reversible. Choose a measure that follows the actual job. Validity, coverage, reviewer effort, conversion, response time, source quality, and revenue can describe different outcomes and should stay separate. A short decision record should state the current approach, evidence, owner, date, and condition for revision. That makes data cleansing and transformation useful beyond the person who first implemented it. A lead source contains employee counts as 51-200, 200+, approximately 80, and blank. Cleansing validates and standardizes the observed values. Transformation maps valid counts into the company's SMB, midmarket, and enterprise bands. The final segment remains traceable to the submitted or enriched source. Cleansing asks whether the value can be trusted. Transformation asks how the trusted value must be represented for the next job. Mixing the answers in one overwritten field makes errors harder to diagnose. --- # Data Cleansing | Surface Glossary URL: https://surface.thesurface.network/glossary/data-cleansing-and-why-is-it-important Data cleansing is the repeatable process of detecting and resolving records that are inaccurate, incomplete, inconsistent, duplicated, stale, malformed, or incorrectly related. It is important because business systems use those records to segment audiences, assign owners, personalize messages, calculate performance, and make automated decisions. Cleansing and cleaning are usually interchangeable terms. The work includes deterministic fixes such as date and country normalization, plus judgment-heavy tasks such as account matching and source conflict resolution. A good process keeps original values and uncertainty visible. Begin with the action the data must support, then define quality rules and consequences. Profile the source, apply transparent transformations, review low-confidence identity changes, validate downstream behavior, and repair the collection or integration that produced recurring errors. 1. Set the record grain, required fields, accepted formats, identifiers, freshness rules, and relationships for the intended use. Different workflows can have different thresholds. 2. Profile missingness, invalid values, duplicates, outliers, stale fields, and failed joins. Break results down by source, form, vendor, integration, and time period. 3. Normalize safe fields through documented rules while preserving raw data. Record the rule version, execution time, and whether the value came from submission, enrichment, calculation, or review. 4. Handle uncertain matches with confidence and human review. Account merges, employer inference, and contact identity can change ownership and attribution, so they deserve stricter controls. 5. Reconcile totals and test affected workflows. Monitor new records after launch to confirm that the underlying defect has been reduced rather than hidden by a recurring cleanup. Track completeness and validity for critical fields, duplicate rate, match coverage, conflict rate, records changed by rule, manual review volume, reversal rate, routing exceptions, and report reconciliation. Connect the cleanup to business measures such as accepted leads or response time when possible. Operational review of data cleansing should follow a record through the systems that consume it. Start at collection, then inspect enrichment, normalization, matching, CRM sync, routing, reporting, and retention. Sample records that passed every validation as well as records sent to exceptions. A valid field can still be wrong for the person, account, or time period, and a clean table can still break when identifiers connect it to the wrong entity. Keep the smallest useful scope for data cleansing until the operation has evidence to expand. Limit templates, segments, permissions, channels, or actions at first. Review errors and manual work, then add scope deliberately. This makes ownership and rollback practical and gives the team a baseline against which a broader version can be judged. The final artifact should show the current decision, the evidence behind it, and the condition that forces reconsideration. That is what makes data cleansing maintainable after the original operator moves to another project. Retirement belongs in the operating plan for data cleansing too. Define the signal that shows the process no longer serves its original audience, system, category, or decision. Archive the configuration and evidence, stop new entries safely, preserve required history, and update dependent reports or links. Unused processes create risk when they remain active simply because no one owns turning them off. Record where data cleansing remains uncertain and when that uncertainty becomes material. This gives the next operator a starting point instead of forcing another full audit. - Which business action determines the quality threshold? - Which raw fields, history, and provenance must remain intact? - Which source wins when submitted, enriched, CRM, and calculated values disagree? - Which changes can run automatically and which need review? - Who owns upstream prevention after the initial cleansing project? A clean value is a claim. The operation should be able to explain why that claim replaced or normalized the source. This matters most where records affect people, money, access, or customer communication. A common failure is optimizing for completeness. Unknown values are replaced with defaults, inferred values lose their confidence labels, and outliers are removed. Every row becomes full, yet the dataset has become less honest and the automation more confident. Restore unknown states, separate observed from inferred values, and place high-consequence decisions behind stricter validation. Report residual uncertainty and fix recurring sources before expanding automated use. --- # Data Cleansing Deduplication | Surface Glossary URL: https://surface.thesurface.network/glossary/data-cleansing-deduplication Data cleansing deduplication is the process of finding records that may represent the same person, account, product, or event and resolving the overlap safely. Exact matches use stable values such as a verified email or external identifier. Fuzzy matches compare names, domains, addresses, phone numbers, and other evidence when no single value is decisive. A duplicate is a claim about identity, not merely two similar rows. Two people may share a name, one company may own several domains, and a contact may use personal and work emails. Resolution can merge records, link them under a shared entity, suppress one operational copy, or send the case to review. Duplicates split history, inflate audience counts, send repeated messages, create competing owners, and distort attribution. A careless merge can be worse. It may attach consent, opportunity history, or customer activity to the wrong entity and make the original records difficult to recover. Define the entity and the consequence of a false match before setting rules. Preserve source records, standardize comparison fields, use stable identifiers where available, and assign confidence thresholds by action. Automatic merging should require stronger evidence than a suggestion for human review. Keep a merge log and a reliable way to reverse important identity changes. Test rules on known matches and known nonmatches from the systems that will use the result. Review performance by region, naming convention, company size, and source because one threshold rarely works equally well everywhere. Repair the form, integration, import, or enrichment process that repeatedly creates the same duplicate pattern. Two contacts share a full name and company, but their emails, departments, and phone numbers differ. The system links both to the same account and leaves the person records separate. A second pair shares a verified email and external contact ID across a webinar tool and CRM, so the system merges them while preserving both source histories. Deduplication should improve the identity model without erasing uncertainty. The right outcome is sometimes a link or review state rather than a merge. --- # Data Cleansing Strategy | Surface Glossary URL: https://surface.thesurface.network/glossary/data-cleansing-strategy A data cleansing strategy is a plan for improving and maintaining data quality across sources, systems, and workflows. It defines which records and fields matter most, what fit for use means, how defects are detected and resolved, which changes require review, and how recurring errors are prevented upstream. The strategy should follow consequence. Lead identity, consent, account matching, lifecycle, ownership, campaign source, and revenue relationships usually deserve more control than optional profile fields. A one-time cleanup without prevention quickly returns to the original state. Prioritization prevents teams from spending weeks standardizing low-value fields while misroutes, duplicates, and broken attribution continue. Strategy also protects raw evidence and uncertainty. The goal is trusted operations rather than a dataset with no blanks. Inventory critical data domains, profile quality by source, set measurable thresholds, preserve raw and cleaned layers, and assign owners. Use deterministic rules first, controlled inference for ambiguous cases, and human review where identity or financial consequences are high. Feed defects back to forms, integrations, vendors, and training. Apply a data cleansing strategy to a named data use case. Preserve raw values, identify source and recency, create separate normalized fields, and define which uncertain records must remain unknown or enter review. Keep the source beside the result and make changes reversible. This protects the operation when a definition, vendor, model, template, or buyer behavior changes after the original decision. The final review should ask what changed for a buyer or operator. If a data cleansing strategy only creates another field, page, prompt, or dashboard, its role remains incomplete. A revenue team prioritizes account identity, country, employee band, lifecycle stage, owner, and campaign source. It creates weekly validation, a review queue for uncertain account matches, source-precedence rules, and a dashboard of recurring defects by form and integration. Optional social fields remain lower priority. A cleansing strategy should reduce both current errors and the rate at which new errors arrive. If the same bulk repair runs every month, the organization has a maintenance ritual rather than a prevention system. --- # Data Cleansing System | Surface Glossary URL: https://surface.thesurface.network/glossary/data-cleansing-system A data cleansing system is the combination of software, rules, reference data, workflows, and human review used to find and resolve data-quality problems. It may standardize formats, validate values, map categories, identify duplicates, enrich missing fields, quarantine suspect records, and monitor recurring errors. The system should preserve where each value came from and what changed. Cleansing can happen at entry, during an integration, in scheduled batches, or before a specific analysis. Each location has a different purpose. Entry validation prevents known errors, while later reconciliation can compare several sources. A correction that is safe for reporting may be unsafe for an operational system where the original record has legal or customer-service significance. One-time cleanup projects make a dashboard look better until the same forms, imports, and integrations recreate the errors. A system connects detection to prevention and ownership. It also separates deterministic fixes, such as standard date formatting, from identity or consent decisions that need more evidence and may require approval. Define valid states and the consequence of each error before choosing tools. Keep raw values, normalized values, source, timestamp, rule version, confidence, and reviewer where applicable. Use reference tables for accepted mappings. Test matching rules against known matches and nonmatches, and measure incorrect changes as well as errors caught. Route uncertain cases to a queue instead of forcing a guess. Inspect coverage, precision, rollback, and recurrence. Monitor new invalid values, unresolved exceptions, merge reversals, source-specific error rates, and time to resolution. Give source owners feedback that points to the form, connector, import, or manual process creating the defect. Review permissions because cleansing tools often have broad write access across customer systems. A CRM contains duplicate accounts created through event imports and manual prospecting. The cleansing system normalizes domains, compares company names and locations, links probable matches, and sends uncertain subsidiaries to review. It never merges on name alone. The team records merge history and repairs the event connector that was ignoring existing account IDs. A cleansing system is dependable when it fixes known errors, exposes uncertain cases, and reduces the rate at which bad data returns. --- # Data Governance and Data Management | Surface Glossary URL: https://surface.thesurface.network/glossary/data-governance-and-data-management Data governance and data management divide authority from execution. Governance identifies who can define data, approve its use, accept risk, and resolve disagreement. Data management supplies the architecture, operations, and controls that keep data available through its working life. Both disciplines meet wherever a business rule must become dependable system behavior. The distinction helps teams route decisions. A warehouse owner can explain what a field contains. The domain owner decides what the field is allowed to mean in reporting or customer action. Governance owns domain scope, definitions, accountability, permitted use, access principles, quality expectations, change approval, and exception authority. Data management owns ingestion, modeling, integration, permissions, monitoring, backup, lineage, archival, and disposal. Privacy, security, legal, analytics, and business operators may contribute to both sides according to the decision. The roles should share one issue path. Operators need a way to report that an approved rule is impossible, ambiguous, or producing harm. Owners need evidence about affected systems and users before they change it. When a source is onboarded, governance approves purpose, owner, and use while management profiles and connects the data. During a schema change, governance reviews meaning and downstream obligation while management tests dependencies and release. During a quality incident, governance sets priority and acceptable correction while management traces, repairs, and monitors recurrence. Use the same pattern for access, retention, modeled fields, and deletion. The handoff should identify the decision, implementer, evidence, exception, and review date. A company wants to use product activity in lead scoring. Governance decides which events are appropriate, who owns their definitions, how long they remain relevant, and which customers or regions are excluded. Data management builds the event pipeline, validation, permissions, and monitoring. When an event changes after a product release, the technical alert returns to the owner before the scoring rule silently changes. Governance should approve meaning and authority. Management should implement and monitor the approved behavior. When a technical constraint makes the rule impractical, management returns the conflict rather than silently changing the definition. When a business owner requests an exception, governance records its scope and expiration. This two-way path keeps policy grounded in systems and keeps systems accountable to the business. --- # Data Governance Frameworks | Surface Glossary URL: https://surface.thesurface.network/glossary/data-governance-frameworks Data governance frameworks are organized models for deciding who owns data, what important terms mean, who may access or change records, how quality is measured, and how the organization responds to errors or policy changes. They turn data stewardship into named roles and repeatable decisions. A framework may be centralized, federated across business units, or hybrid. The label matters less than clear authority. Marketing, sales, RevOps, finance, product, legal, and security often share the same customer records while caring about different fields and risks. Governance prevents a workflow from acting on definitions no one approved. It also creates a route for disputes. When sales says a lead was misclassified, the team should know who owns the ICP rule, which source supplied the company data, and how the exception feeds into the next version. Start with high-consequence data domains and decisions. Name an accountable owner, operational steward, source system, allowed uses, quality measures, access rules, retention policy, and change process. Keep a catalog of important fields and relationships, then review it when a new tool or agent gains access. The operating record for data governance frameworks should show the original value, proposed or cleaned value, rule, confidence, source, timestamp, and reviewer where needed. That history makes corrections reversible. Review a sample of real cases before relying on an aggregate score. The sample should include incomplete, conflicting, and high-value records because averages often hide the failures with the largest business cost. Place the documentation for data governance frameworks beside the workflow or decision it affects. That keeps definitions, evidence, ownership, and later corrections available to the people who need them. A B2B company creates a governance group for lead and account data. RevOps owns lifecycle definitions, marketing owns campaign taxonomy, sales operations owns territory logic, and security owns access controls. A shared change log records rule updates, while a monthly exception review looks at misroutes and unmatched accounts. Governance should make ordinary work easier to explain. If the framework produces committees and documents but cannot answer who may change a routing field today, it has missed the operational problem. --- # Data Governance Model | Surface Glossary URL: https://surface.thesurface.network/glossary/data-governance-model A data governance model is the structure a company uses to assign authority, decision rights, and accountability for data. It defines roles such as executive sponsor, governance council, domain owner, data steward, system owner, analyst, and user. It also explains how those roles approve definitions, resolve quality issues, grant access, manage change, and enforce policy. Models may be centralized, federated, decentralized, or hybrid. The right choice depends on company size, regulatory exposure, domain expertise, system architecture, and how quickly teams need to act. Data problems often persist because several teams can change a field and no one owns the meaning. A model gives a named person or group authority to settle disputes and maintain standards. It also separates business ownership from technical custody. An operations leader may own the lifecycle definition while an engineering team manages the database where the field lives. The structure should match the consequence of the data. Consent, identity, revenue, and account ownership usually need stronger controls than optional campaign labels. Document the domains under governance, the owner for each, the decisions that require approval, and the path for exceptions. Specify stewardship duties, meeting or review cadence, access rules, issue escalation, change records, and service levels. Keep committees small enough to make decisions and give stewards enough time to do the work. Measure issue age, repeated defects, adoption of definitions, access turnaround, and the downstream effect of corrections. Governance should reduce uncertainty for operators rather than add an approval layer to every request. A software company uses a federated model. A central council sets identity, consent, security, and documentation standards. Revenue operations owns lead and account domains, finance owns booked revenue, and product owns usage events. Domain stewards review quality and propose changes. Cross-domain conflicts go to the council with evidence, an impact statement, and a named decision date. Use a centralized model when consistent control and scarce expertise matter most. Use a federated model when domains need local knowledge under shared standards. Decentralized authority can support speed in low-risk work, though it requires clear boundaries and escalation. Many companies use a hybrid: central rules for identity, consent, security, and finance, with domain owners deciding field definitions and quality thresholds closer to the work. --- # Data Governance Policy | Surface Glossary URL: https://surface.thesurface.network/glossary/data-governance-policy A data governance policy is an approved statement of how an organization expects data to be owned, defined, collected, accessed, used, shared, changed, retained, and removed. It sets mandatory principles and assigns authority. Standards, procedures, field rules, and technical controls translate the policy into day-to-day behavior. The policy should be specific enough to direct decisions and stable enough to survive a tool change. It does not need to contain every validation rule. A separate standard can define accepted country codes, while the policy states who owns the standard and how changes are approved. 1. **Set the scope and purpose.** Name the data domains, business activities, systems, people, and jurisdictions covered. Explain which risks and operating needs the policy addresses. 2. **Assign authority.** Define the executive sponsor, governance body, domain owners, stewards, system custodians, security or privacy roles, and users. State who can approve definitions, access, quality thresholds, retention, and exceptions. 3. **State the requirements.** Cover classification, minimum documentation, source and lineage, data quality, access, permitted use, sharing, change control, issue handling, retention, disposal, and audit. Link detailed standards instead of hiding them in a long policy paragraph. 4. **Define exceptions and enforcement.** Explain how someone requests an exception, who assesses it, what evidence is required, how long approval lasts, and what happens when the policy is ignored. 5. **Review and revise.** Give the policy an owner, effective date, review schedule, and version history. Trigger an earlier review after a material regulatory, system, business model, or data-use change. - Which requirements apply to every domain and which depend on sensitivity or consequence. - How business ownership and technical custody divide responsibility. - Which data uses require consent, additional review, or prohibition. - How quickly access, quality, and definition disputes must be resolved. - Which evidence demonstrates compliance inside normal workflows. - How acquired, partner, modeled, and third-party data fit the policy. Map each requirement to an owner, procedure, and control. A requirement to preserve source lineage may become required metadata, integration logging, and a review check. An access rule may become role-based permissions, approval, expiration, and quarterly review. A quality requirement may become validation, monitoring, and an exception queue. Train people at the point of use. A short instruction beside a sensitive export can be more effective than an annual presentation. Keep the policy available, then place the relevant rule in the workflow where someone makes the decision. Many policies are copied from a generic template, approved, and forgotten. They list broad values such as accuracy and security without naming decisions, owners, or evidence. Teams then create local rules because the official document cannot resolve a real disagreement. A useful policy has visible consequences. When marketing wants to use an inferred customer attribute, the document identifies the owner, permitted-use test, source requirement, approval path, and retention rule. The answer may vary by risk, but the method remains consistent. That consistency is the reason to govern the data. ## How to publish and maintain the policy Write for the people who must act. Use direct requirements, defined terms, named roles, and links to current procedures. Keep legal or regulatory language where necessary, then add an operational explanation or example. A marketer, analyst, engineer, and vendor manager should each be able to find the rule that applies to their work. Publish the effective version in one controlled location. Retain prior versions and communicate material changes to affected teams. Require acknowledgment only when it supports a real training or compliance need. Policy acceptance alone does not prove that systems, permissions, or habits changed. Review evidence from access requests, quality incidents, audits, exceptions, model use, and deletion work. If the same exception appears repeatedly, the rule, process, or system may be wrong. Policy maintenance should resolve recurring friction while preserving the risk control the requirement was meant to provide. Use scenario-based reviews instead of asking whether people have read the document. Give a steward an access request, a marketer a modeled field, or an analyst a deletion case and observe the decision path. Confusion reveals where definitions, training, controls, or ownership need revision. --- # Data Governance Processes | Surface Glossary URL: https://surface.thesurface.network/glossary/data-governance-processes Data governance processes are the recurring workflows that put governance decisions into practice. They include assigning ownership, defining data, approving access, onboarding sources, setting quality rules, resolving issues, changing schemas, managing metadata, reviewing usage, retaining or deleting records, and documenting exceptions. Policies state expectations. Processes show who does what, in which system, with which evidence, by when, and what happens when the normal path fails. Definition management gives each important field or metric an owner, meaning, examples, and change record. Access management reviews purpose, role, sensitivity, duration, and approval. Data-quality management detects defects, triages impact, corrects sources, and prevents recurrence. Change management assesses downstream dependencies before a field, integration, model, or rule changes. Retention and deletion apply lifecycle rules. Issue management provides one route for reporting, prioritizing, resolving, and learning from defects. Begin with high-consequence domains such as identity, consent, ownership, finance, and customer state. Map the current workflow and its delays. Assign a domain owner and steward, create service levels, and place evidence in the system where people work. Automate validation and routing when the rule is deterministic. Preserve review for ambiguous decisions. Track issue age, recurrence, exception volume, approval time, downstream errors, and adoption of changes. A campaign source field contains several names for the same partner. The issue process records affected reports and workflows. The domain owner approves a canonical definition and mapping. Data management corrects historical records without removing original values, updates form and integration controls, and alerts reporting owners. A monthly review checks for recurrence. The process fixes the source and the consequences instead of cleaning the dashboard alone. ## Maintain a process registry Document each governance process with its trigger, input, owner, approver, steps, evidence, service level, exception, system, and output. Link policies and standards instead of copying them into local instructions. Review whether people use the process and where work escapes into chat or private spreadsheets. A registry makes overlapping approvals visible and gives the organization a place to simplify controls without losing accountability. --- # Data Governance Strategy | Surface Glossary URL: https://surface.thesurface.network/glossary/data-governance-strategy A data governance strategy explains how an organization will make important data trustworthy, usable, secure, and accountable. It connects business priorities to decision rights, definitions, quality controls, access rules, lineage, retention, issue resolution, and investment. The strategy names which data domains come first and what measurable operating result governance should produce. Governance is often introduced after conflicting metrics, privacy risk, failed integrations, or unreliable automation becomes expensive. The work can span customer, product, finance, people, and supplier data, yet attempting to govern every field at once usually creates committees and documents that operators cannot apply. Strategy narrows the scope and sets an order based on consequence. Begin with decisions and workflows harmed by unreliable or poorly controlled data. Identify the records, fields, events, and metrics involved. Then assign authority and design controls close to where errors enter or decisions occur. Governance should change how people create, approve, transform, access, and retire data. A catalog or policy can support that work, but neither replaces operational ownership. 1. Choose a business priority and define the failure. Examples include duplicate leads delaying sales response, inconsistent customer status affecting renewal outreach, or disputed revenue definitions slowing planning. Record the current cost and affected users. 2. Map the data chain. Identify sources, identifiers, transformations, integrations, destinations, access paths, reports, and manual edits. Mark where meaning changes and where the organization loses lineage. 3. Assign decision rights. Name a business owner for meaning and acceptable use, a technical custodian for implementation, and operators who resolve exceptions. State who can approve definition, access, or retention changes. 4. Implement controls and an issue path. Use validation, reference values, permissions, monitoring, reconciliation, and review according to risk. Provide a visible queue for exceptions that rules cannot settle safely. 5. Measure the operating result and expand deliberately. Track error, rework, incident rate, resolution time, process delay, adoption, and downstream performance. Add another domain only after ownership and controls work in normal operations. Good governance measures are attached to the original failure. A duplicate-reduction program might track suspected duplicates, incorrect merges, routing delay, and manual review time. A metric-definition program might track reconciliation differences and time spent resolving disputes. Counting catalog entries or policy acknowledgments describes activity, not whether the governed data supports better work. Write definitions and rules where operators encounter them. A field should show its meaning, grain, source, permitted values, authority, refresh behavior, downstream use, and contact for questions. Change records should preserve the old definition, effective date, reason, approver, and affected systems. Review access and retention on a schedule suited to sensitivity. Publish issue status so teams can see whether a disputed record or metric is safe to use. Train new operators on the few governed choices they make, then inspect real cases to see where the written rule is unclear. - Which data domain and business outcome receive the first governance effort? - Who owns meaning, implementation, access, quality, and exception decisions? - Which controls can run automatically and which cases require review? - How will changes propagate across systems, models, and reports? - What evidence will show that the strategy reduced risk or operating cost? Authority should match the subject. Marketing should not redefine booked revenue alone, and engineering should not decide the business meaning of a qualified lead without revenue stakeholders. Shared definitions still need one decision path when groups disagree. Escalation, time limits, and temporary guidance keep a dispute from blocking work indefinitely. A common failure is starting with a company-wide council and a large glossary before choosing a business problem. Attendance fades, definitions remain optional, and source systems keep accepting the same invalid values. Another failure gives every domain equal priority, which spreads limited stewardship across data with very different consequences. Select one workflow where better data can produce a visible result. Trace its failures to the source, assign authority, implement a small set of controls, and publish the exception path. Retire fields and rules that nobody uses. The result should be observable in daily work before the strategy expands to another domain. --- # Data Management and Governance | Surface Glossary URL: https://surface.thesurface.network/glossary/data-management-and-governance Data management is the practical work of collecting, storing, integrating, securing, transforming, using, retaining, and disposing of data. Data governance sets the decision rights, policies, definitions, quality expectations, access rules, and accountability that direct that work. Management operates the lifecycle; governance decides what acceptable and responsible operation means. The two disciplines overlap in systems and daily workflows. A data engineer may implement a retention rule, while a governance owner approves its business and legal meaning. A CRM administrator may enforce allowed lifecycle values, while revenue leaders decide the definitions. Separating authority from implementation prevents technical convenience from silently becoming company policy. Management without governance can move data efficiently while spreading disputed meaning or excessive access. Governance without management can produce policies that never reach forms, pipelines, databases, and reports. Together they connect a business rule to the source, technical control, exception path, monitoring, and person accountable for the outcome. Map an important data workflow and label each decision. Governance covers who owns the subject, who can approve access, which definition applies, how long records remain, and what quality is sufficient. Management covers architecture, ingestion, transformation, backup, security operation, observability, and deletion. Some roles may perform both jobs in a small company, but the decisions should still be explicit. Choose one domain and translate each policy into a control or observable practice. Record fields, identifiers, sources, transformations, permissions, retention, issue handling, and downstream use. Give operators a way to flag a rule that is impossible or harmful in practice. Review incidents and exceptions with both business owners and technical custodians, then revise the rule or implementation with a dated change record. A company decides that closed customer accounts must be removed from marketing audiences within 24 hours while financial records remain for the required period. Governance defines account closure, permitted retention, and approvers. Data management implements status propagation, audience suppression, access restrictions, monitoring, and deletion jobs. An exception queue handles disputed closures without sending new campaigns. Governance supplies authority and boundaries; management turns those decisions into reliable data operations. --- # Data Strategy and Governance | Surface Glossary URL: https://surface.thesurface.network/glossary/data-strategy-and-governance Data strategy explains which business decisions and capabilities data should improve, which domains deserve investment, and how the organization will build toward that goal. Data governance defines the authority, standards, access, quality rules, change process, and accountability that keep those data products dependable. The two disciplines need each other. Without governance, a strategy may promise unified customer intelligence while every system uses a different account definition. Governance without strategy can accumulate committees, policies, and catalogs around data that no important workflow uses. The shared unit is a business decision supported by maintained information. Begin with a small set of decisions where data quality, access, or inconsistency creates material cost. Map the domains and systems behind those decisions, assign owners, define the critical records and metrics, then build controls proportional to the consequence of error. Expand after the operating model works on real cases. 1. Name the business outcomes and decisions. Describe who acts, which data they need, and how delay or error affects customers, compliance, cost, or revenue. 2. Map data domains, flows, and authority. Identify source systems, transformations, consumers, owners, and places where several tools can write the same field. 3. Create contracts for critical objects and metrics. Define grain, identifiers, allowed values, provenance, freshness, null behavior, access, retention, and quality thresholds. 4. Establish controls and exception paths. Validate at collection, monitor drift, log changes, route uncertain records, and provide a way to correct or reverse material decisions. 5. Measure use and revise priorities. Review incidents, manual work, adoption, decision quality, and the cost of maintaining each control before adding more scope. Useful measures include completeness and validity for critical fields, unresolved exceptions, time to correct, unauthorized access, metric disputes, lineage coverage, adoption of governed assets, and the downstream outcomes attached to them. High catalog counts say little if operators still export and repair records privately. Governance should live close to the work. Domain owners decide meaning and acceptable quality; technical stewards maintain implementation and lineage; workflow owners explain consequences; security and legal define access and retention where required. Write down who can approve a definition change and how dependent reports, models, automations, and teams receive that change. Keep raw, normalized, inferred, and manually approved values distinct. When two systems disagree, the resolution rule should remain visible and dated. Review high-impact samples such as lead ownership, consent, lifecycle stage, account hierarchy, and revenue attribution. Aggregate quality scores often hide the small set of errors that create the largest operational cost. - Which business decisions justify governance effort now? - Which source has authority for each critical field or metric? - Who owns definitions, technical implementation, access, and exceptions? - Which changes can run automatically, and which require approval? - How will downstream users learn about definition or schema changes? Apply stricter controls where a wrong value can send a customer message, change ownership, misstate revenue, violate consent, or train a model on the wrong entity. Optional profile attributes may tolerate looser handling. This consequence-based approach keeps governance from becoming equally heavy everywhere. Buying a catalog and declaring governance implemented is a common failure. The organization documents hundreds of tables while business definitions remain contested and operating systems continue to overwrite one another. Another failure writes policies in isolation, so teams build shadow spreadsheets because the approved data cannot support the pace or detail of their decisions. Choose one high-value workflow, resolve its definitions and authority, expose exceptions, and prove that the controls reduce error or manual work. Retire unused fields and duplicated rules. Strategy should explain why the next governed domain deserves attention; governance should make the claimed business result repeatable. Publish the definitions and exception path where operators work, then review actual disputes for one quarter. Policies that no one can find or apply will push decisions back into private spreadsheets. Use those disputes to clarify authority, repair upstream collection, and decide whether the next data domain deserves the same level of control. Leave the review date visible. --- # Demand Generation Metrics | Surface Glossary URL: https://surface.thesurface.network/glossary/demand-gen-metrics Demand generation metrics describe how a target audience moves from awareness and engagement into identifiable demand, pipeline, and revenue. No single formula captures the whole job. A useful measurement set combines audience quality, buyer behavior, capture, qualification, stage movement, time, cost, and commercial outcomes. Metrics should follow the same population and observation window. Mixing broad campaign reach with pipeline from a narrow account segment can make a program look more efficient than it is. Common formulas include: - Engagement rate = engaged people or accounts / reached people or accounts - Lead-to-opportunity rate = opportunities created / eligible leads captured - Pipeline per target account = sourced or influenced pipeline / target accounts reached - Cost per opportunity = eligible program cost / opportunities created Define every input. An engaged account might require two people and one high-intent action, or it might count any visit. Eligible cost may include media only, or media, production, software, events, and labor. Sourced and influenced pipeline should remain separate because they answer different questions. There is no universal good demand generation benchmark. Performance changes with segment size, contract value, sales cycle, channel mix, buying group, category maturity, and the time allowed for opportunities to appear. A small enterprise program may create fewer leads and more pipeline per account than a broad self-service campaign. Read the measures as a connected set. High reach with weak qualified engagement suggests an audience or message problem. Strong engagement with low capture may point to an offer or conversion path. Healthy opportunity conversion with slow response suggests an operating delay. Revenue outcomes may arrive months after the activity, so cohort reporting is safer than comparing unrelated calendar totals. A company spends $60,000 reaching 800 target accounts during a quarter. Two hundred accounts meet its engagement rule, 80 people become eligible leads, and 16 opportunities are created. The account engagement rate is 25 percent. The lead-to-opportunity rate is 20 percent. Cost per opportunity is $3,750. Those figures do not prove the program is profitable. The team still needs opportunity value, win rate, sales cycle, retained revenue, and comparison with other cohorts. It also needs to know whether the 16 opportunities were sourced by the program or already active and merely influenced by it. Record the audience, exclusions, attribution rule, cost scope, stage definitions, currency, reporting date, and maturity window beside the results. Keep raw counts visible next to rates. A dashboard becomes harder to misuse when a reader can see both the numerator and denominator behind every percentage. Do not combine people, accounts, leads, opportunities, and dollars inside one unlabeled rate. Deduplicate at the level the decision uses and state whether multiple contacts can contribute to one account result. Preserve both sourced and influenced views when the business needs them, then explain the attribution rule. Review mature cohorts again after the expected sales cycle so early channel comparisons do not punish programs whose buyers take longer to decide. --- # Types of Business Research | Surface Glossary URL: https://surface.thesurface.network/glossary/different-types-of-business-research The different types of business research are ways to organize evidence by where it comes from, how it is collected, what it measures, and which decision it supports. Primary research gathers new evidence for the current question. Secondary research analyzes material that already exists. Qualitative research explains language, motives, context, and process. Quantitative research measures frequency, size, difference, or relationship. These labels overlap. A primary interview study is qualitative. A secondary analysis of transaction records may be quantitative. The combination matters more than forcing a project into one box. Exploratory research helps a team understand an unclear problem and form better questions. Descriptive research measures what is happening, who is involved, or how common a pattern is. Comparative research examines differences between segments, messages, products, or periods. Causal research tests whether one change produces another outcome. Predictive research estimates what may happen under stated assumptions. Teams can also classify work by subject, including customer, market, product, competitor, brand, pricing, employee, operational, and financial research. Match the method to the uncertainty. Interviews can uncover an unknown buying process. A survey can estimate how widely a known pattern appears. An experiment can test message response. Sales records can reveal stage loss by segment. A market model can estimate opportunity using explicit assumptions. Use more than one source when the decision is consequential. Triangulation helps reveal where stated preference, observed behavior, and published market data disagree. A company sees declining trial conversion. Exploratory interviews reveal confusion during setup. Product analytics describe where people stop. A comparative usability test evaluates two onboarding designs. A controlled release measures whether the selected design changes activation. Each research type answers the next question created by the previous result, so the program moves from discovery to a measurable decision. Classify the work along more than one axis. State whether the source is primary or secondary, the evidence is qualitative or quantitative, and the purpose is exploratory, descriptive, comparative, causal, or predictive. Add the business subject and decision. This creates a useful description such as "primary qualitative exploratory research for a product-entry decision" instead of an ambiguous label such as "customer study." --- # Digital Lead Generation Strategies | Surface Glossary URL: https://surface.thesurface.network/glossary/digital-lead-generation-strategies Digital lead generation strategies are planned approaches for creating and capturing identifiable demand through online channels. They may combine search, content, paid media, social, email, webinars, virtual events, communities, partner distribution, assessments, calculators, chat, forms, scheduling, and product-led experiences. A channel becomes a strategy only when it connects to a defined audience, offer, conversion, qualification rule, owner, and business outcome. Driving traffic to a generic form is an activity. Choosing a comparison program for high-intent buyers, then routing qualified responses with page context, is an operating choice. Digital programs can produce large response volumes before anyone checks fit. Weak forms and disconnected systems then create duplicate records, slow follow-up, and reports that reward cheap conversions. Strategy ties media and content to the downstream capacity and economics of the company. Choose channels from buyer research and market concentration. Give each channel a role in demand creation, education, intent capture, proof, or conversion. Use the lowest-friction request that supports the next decision, preserve source context, and set response expectations. Compare sources through meetings, opportunities, customers, and payback as well as form totals. Plan connected paths rather than isolated campaigns. A search guide can lead to an assessment, support retargeting, give outbound a credible reason to contact, and equip sales after a meeting. Test audience, message, offer, page, form, routing, and follow-up separately enough to learn where the path changed. A cybersecurity vendor creates technical comparison pages, promotes a short readiness assessment through targeted search and partner newsletters, and sends qualified enterprise responses to a specialist calendar. Lower-fit responses receive the assessment findings and related guidance. The team stops a gated ebook campaign after high download volume produces little accepted demand. Digital lead generation works when the online experience and the operational handoff are designed as one path. The strategy should also explain how poor-fit demand exits without wasting the buyer's time or the sales team's capacity. --- # Digital Marketing and Lead Generation | Surface Glossary URL: https://surface.thesurface.network/glossary/digital-marketing-and-lead-generation Digital marketing and lead generation work together when online channels create useful attention and give interested people a clear way to identify themselves. Search, content, paid media, email, social, video, communities, and partner channels can build awareness or prompt action. Forms, registrations, trials, chats, referrals, and scheduling paths capture selected responses as leads. Digital activity does not automatically become a lead. Many buyers research anonymously, and many clicks have little commercial meaning. Lead generation begins when the company can connect a response to a person or account and decide what should happen next. Treating every channel metric as a lead metric can encourage premature gates and inflated reporting. Treating digital marketing as pure awareness can leave high-intent visitors without a useful conversion path. The program needs both open learning and intentional capture. The handoff also requires data quality, consent, qualification, ownership, and response. A campaign can produce strong form volume while failing if the records arrive late or lack the context sales needs. Map each audience and intent to a destination and next step. Use educational pages for early questions, proof and comparison for evaluation, and direct forms or scheduling for active requests. Preserve campaign and page context when a record enters the system. Measure reach, engagement, capture, qualification, response, opportunity, cost, and revenue as separate stages. Review what sales and customers report so marketing can revise targeting, content, and offers. A cybersecurity firm publishes a guide that earns search and newsletter traffic. Most readers stay anonymous, which the team measures as qualified engagement. Readers who want an assessment complete a short form. The system appends company context, checks existing ownership, and routes the request to a specialist. Marketing compares the assessment cohort with other entry paths instead of crediting every guide visit as generated pipeline. For each digital source, record its audience, intent, content or offer, destination, capture event, qualification, owner, response expectation, attribution rule, and review window. Keep channel engagement and captured leads as separate measures. This makes it possible to see whether weak performance came from discovery, conversion, data, routing, or follow-up instead of blaming the whole channel. --- # Digital Marketing Operations | Surface Glossary URL: https://surface.thesurface.network/glossary/digital-marketing-operations Digital marketing operations is the combination of people, processes, data, systems, standards, and controls used to plan, build, launch, measure, and improve digital marketing. It connects web, content, search, email, paid media, social, automation, analytics, lead management, and revenue feedback into repeatable work. The function may sit inside marketing operations, campaign operations, growth, content operations, or revenue operations. Its defining job is execution across digital channels with shared context. Strategy decides the market and campaign choice; operations makes assets, audiences, approvals, tracking, handoffs, and learning work together. Create a common operating path from campaign intake through revision. The path should preserve the business goal, audience, source evidence, message, asset versions, data requirements, approvals, launch checks, conversion, routing, reporting, and follow-up decisions. Standardize repeatable work while leaving room for campaigns with unusual risk or creative needs. 1. Translate strategy into an executable brief. Name the audience, outcome, position, offer, channels, owner, budget, timing, evidence, conversion, and sales or customer handoff. 2. Plan production and dependencies. Assign content, creative, pages, audiences, tracking, legal or brand review, integrations, and the sequence in which each item must become ready. 3. Build and quality-check the campaign. Test links, forms, events, consent, responsive layouts, audience logic, exclusions, routing, ownership, reporting, and rollback. 4. Launch with visible control. Record versions, approvals, release time, monitoring owners, expected volume, and the thresholds that require a pause or correction. 5. Measure and feed outcomes back. Connect channel signals to qualified demand, sales results, customer evidence, content updates, and the next campaign decision. Operational measures include time from approved brief to launch, rework, approval delay, defect rate, tracking coverage, routing time, exception backlog, asset reuse, and report readiness. Pair them with campaign and revenue outcomes. Faster production has little value if the team launches work that sales cannot use or measurement cannot explain. Assign authority by decision. A campaign owner controls the business brief; channel owners control execution standards; operations controls workflow and data integrity; brand, legal, security, or product reviewers approve claims within their domains. Record who may change a live audience, budget, workflow, or landing page and how that change reaches the rest of the system. Maintain a campaign record that survives the dashboard. It should contain the brief, asset and audience versions, source data, approvals, tracking plan, launch notes, incidents, results, and final decision. When a campaign ends, archive or retire its automations and audiences deliberately. Old workflows and stale segments create risk when they continue running without an owner. - Which campaign information must remain intact across every channel and handoff? - Which work deserves a template, and where does judgment need more room? - Who approves message, data use, launch, and live changes? - What defects or thresholds require a pause, rollback, or escalation? - How will sales and customer outcomes alter the next brief? Operations should reduce hidden coordination, not become a ticket queue that separates marketers from the customer problem. Keep requesters responsible for the business choice and evidence. Use templates to expose missing decisions early, then let operators challenge briefs that cannot support clean execution. A common failure is organizing the function around tools. One specialist owns email, another owns paid media, and another owns analytics, yet no one owns the complete campaign. Assets drift, audiences use different definitions, tracking arrives late, and lead context disappears at routing. Every system reports activity while the combined result remains difficult to explain. Choose one recurring campaign type and rebuild its complete path. Establish a shared brief, campaign identifier, source rules, approvals, test plan, handoff, and review. Measure rework and business outcomes, then expand the operating model to the next workflow. Tool configuration should follow the agreed process. After launch, hold a review that includes the people who built, received, and measured the campaign. Compare the approved brief with what shipped, inspect defects and manual repairs, and record the decision for the next version. This keeps process improvement tied to real work instead of abstract maturity scoring. --- # Direct Marketing Lead Generation | Surface Glossary URL: https://surface.thesurface.network/glossary/direct-marketing-lead-generation Direct marketing lead generation uses targeted communication and a measurable response path to create identifiable buyer interest. Channels may include email, direct mail, phone, messaging, paid audience lists, retargeting, catalogs, or account-specific outreach. The recipient receives a defined offer and a way to respond through a form, reply, call, code, registration, or scheduled conversation. The method differs from broad awareness because the team can connect the audience, message, response, and follow-up more directly. It still depends on permission, relevance, data quality, and local communication rules. The audience and offer matter more than message volume. A useful program selects people or accounts with a credible connection to the problem, explains why the communication is relevant, and gives them a next step that matches their likely stage. Lists acquired without clear provenance can damage deliverability, trust, and compliance. Response data should preserve campaign, creative, audience, timestamp, and original offer so later qualification has context. Define the segment, source, permitted use, message, frequency, offer, response mechanism, qualification, routing, and suppression. Coordinate channels so the same person does not receive conflicting outreach. Test list quality and delivery before scale. Set response service levels and a path for records that are real but early. Measure valid delivery, response, qualified conversations, opportunities, revenue, cost, complaints, opt-outs, and time to follow-up. A firm sends a short direct-mail package to operations leaders at 200 target accounts after a regulatory change. A unique landing page offers a readiness assessment. Responses enter the CRM with account and campaign context, then route to specialists. Email supports only contacts with an appropriate permission basis. The team compares qualified assessments and opportunities with total program cost rather than treating scans as completed demand. Maintain source and permission for every audience. Validate addresses, honor opt-outs, control frequency, and remove invalid or risky records. Use a separate plan for replies, complaints, and vulnerable recipients. Deliverability is an outcome of list quality and sending behavior, not a technical setting alone. A campaign that reaches more inboxes by ignoring audience expectation can reduce future access to the channel. --- # Enterprise Marketing Automation | Surface Glossary URL: https://surface.thesurface.network/glossary/enterprise-marketing-automation Enterprise marketing automation is the use of software and governed workflows to execute marketing across large databases, products, regions, brands, channels, and buying journeys. It often includes segmentation, email and messaging, lead scoring, lifecycle programs, campaign orchestration, personalization, CRM integration, consent, reporting, and administrative controls. Enterprise describes operating complexity as much as company size. A business may need several teams, languages, data regions, product lines, approval paths, and systems of record. The platform has to support scale without allowing every local workflow to redefine customer stage, consent, campaign source, or ownership. Start with business architecture and governance. Define global records and terms, identify which decisions can vary locally, and map integrations before migrating campaigns. Build shared components for consent, identity, routing, suppression, and measurement, then let teams configure within documented boundaries. 1. Map audiences, regions, products, channels, regulatory requirements, systems, and current workflows. Identify which differences are necessary and which are historical duplication. 2. Define shared identity, lifecycle, consent, campaign, account, and attribution models. Assign owners and source systems before moving automation into the platform. 3. Design roles, workspaces, permissions, approvals, templates, and reusable components. Separate drafting, approval, publishing, data administration, and execution authority where the risk justifies it. 4. Migrate in stages with reconciliation and rollback. Test volumes, time zones, languages, sync delays, duplicate records, opt-outs, unavailable owners, and manual sales changes. 5. Operate through monitoring and change control. Review deliverability, conversion, errors, exceptions, audit logs, data quality, platform cost, and workflow sprawl by business unit. Enterprise reporting should combine campaign and lifecycle outcomes with operational health. Track eligible audiences, delivery, engagement, stage movement, meetings, opportunities, revenue, suppression accuracy, sync latency, duplicate rate, exceptions, and time spent maintaining workflows. A platform that sends reliably can still underperform if data and handoffs are weak. The operating discipline for enterprise marketing automation is a chain from question to source to interpretation to decision. Preserve interview notes, survey instruments, queries, public records, and dated product evidence with enough context to audit the conclusion. Add a confidence statement and the observation that would reverse the recommendation. This avoids the familiar research failure where a clean slide outlives the evidence and continues to guide positioning after the market has changed. Keep the smallest useful scope for enterprise marketing automation until the operation has evidence to expand. Limit templates, segments, permissions, channels, or actions at first. Review errors and manual work, then add scope deliberately. This makes ownership and rollback practical and gives the team a baseline against which a broader version can be judged. The final artifact should show the current decision, the evidence behind it, and the condition that forces reconsideration. That is what makes enterprise marketing automation maintainable after the original operator moves to another project. Retirement belongs in the operating plan for enterprise marketing automation too. Define the signal that shows the process no longer serves its original audience, system, category, or decision. Archive the configuration and evidence, stop new entries safely, preserve required history, and update dependent reports or links. Unused processes create risk when they remain active simply because no one owns turning them off. Record where enterprise marketing automation remains uncertain and when that uncertainty becomes material. This gives the next operator a starting point instead of forcing another full audit. - Which definitions and policies must remain global across teams and regions? - Which local variation is necessary for market, language, product, or regulation? - Which system owns identity, consent, stage, campaign, account, and revenue history? - Which actions require approval, audit, rollback, or separation of duties? - How will the organization prevent unused workflows and fields from accumulating? The platform should reflect a deliberate operating model. Replicating every legacy campaign and exception into a new tool preserves the cost of the old system while adding migration risk. A common failure is centralizing software without centralizing definitions. Regions use the same platform but maintain different lifecycle stages, suppression fields, and campaign naming. Headquarters receives one dashboard assembled from several incompatible operating models. Create a small set of global contracts for identity, consent, stage, and measurement. Move local differences into governed configuration, archive unused assets, and give business units an exception process that records why a variation exists and when it should be reviewed. --- # Example of Structured Data | Surface Glossary URL: https://surface.thesurface.network/glossary/example-of-structured-data A simple example of structured data is a CRM lead record with fields for email, company, country, source, lifecycle stage, owner, and submission time. Each field has a known name and expected value, which lets software validate the record, compare it with other records, and trigger a workflow. A spreadsheet table, analytics event, SQL row, product catalog item, and JSON object can also be structured when they follow a defined schema. The file format alone does not settle the question. The useful property is predictable organization. A CSV with inconsistent columns and mixed meanings has a structure on paper but may still be unusable for reliable operations. To make the example concrete, consider a demo form. The form collects an email and product interest, an enrichment service adds company size, and the CRM assigns an owner. Each value should have a definition, type, allowed range, source, timestamp, and rule for missing data. Those details turn a set of fields into an operational data model. 1. Define the record and its purpose. A lead record supports qualification and routing, while a campaign record supports planning, spend control, and reporting. Mixing both jobs in one row makes the schema harder to interpret. 2. Name each field and its expected type. Email is text with validation, employee count is a number, submission time is a timestamp, and lifecycle stage belongs to a controlled list. 3. Record where the value came from. Visitor input, enrichment, a calculated score, and a sales update have different reliability and should not overwrite one another without a rule. 4. Validate the record before it triggers action. Missing country may be acceptable for nurture, while a missing owner should block a sales-routing handoff or send the record to an exception queue. 5. Keep an audit trail when important values change. The current lifecycle stage is useful, but the team may also need to know who changed it, when, and from which prior value. Data quality can be measured through completeness, validity, uniqueness, consistency, timeliness, and referential integrity. The relevant threshold depends on the action. A research dashboard may tolerate some missing firmographics, while a routing workflow needs the fields that determine territory and ownership to be present before assignment. Operational review of the CRM lead record should follow a record through the systems that consume it. Start at collection, then inspect enrichment, normalization, matching, CRM sync, routing, reporting, and retention. Sample records that passed every validation as well as records sent to exceptions. A valid field can still be wrong for the person, account, or time period, and a clean table can still break when identifiers connect it to the wrong entity. Set the review cadence for the CRM lead record according to volatility and consequence. Fast-changing inputs may need weekly checks, while stable reference material may suit a quarterly factual review. The owner should inspect input quality, output quality, timing, exceptions, and business outcome. Record which finding changes the rule and which finding only needs observation. Do not let the primary tool, spreadsheet, or configuration become the only documentation. A plain-language record of purpose and consequences makes the CRM lead record easier to audit, teach, change, and retire. Maintain an exception log for the CRM lead record that is small enough to review and structured enough to learn from. Capture the input, expected behavior, actual result, consequence, immediate repair, and root cause. Group recurring exceptions by source, rule, segment, template, or integration. This makes the CRM lead record improve through evidence and prevents the same workaround from being rebuilt by several teams in different tools. Keep a short the CRM lead record limitations note with the current process. It should name missing evidence, unsupported cases, and dependencies that could invalidate the approved approach. - Define the business object represented by the record. - Choose required fields, optional fields, and accepted null behavior. - Document the source and freshness expectation for each value. - Set validation rules before the record reaches an automated action. - Preserve changes that affect attribution, qualification, routing, or compliance. The schema should reflect the decisions the business actually makes. Adding fields because a vendor provides them can increase cost and confusion. A smaller set of trusted attributes usually supports better operations than a wide record filled with stale or unexplained values. A common failure is treating field presence as quality. The company field may be filled, yet contain a personal email domain, an outdated employer, or a free-text string that does not match an account. The record passes a completeness check and still routes incorrectly. Another failure occurs when enrichment silently replaces information the buyer supplied. Define source precedence, retain provenance, and validate the fields tied to material decisions. Use an exception state instead of forcing uncertain records into a confident category. When the schema changes, update forms, enrichment, CRM mappings, reports, and automation together. --- # Examples of Prompt Engineering | Surface Glossary URL: https://surface.thesurface.network/glossary/examples-of-prompt-engineering Examples of prompt engineering include classifying a lead against an ICP, extracting product fields from a document, summarizing approved research, drafting a campaign brief, critiquing a page against editorial rules, and returning a structured object for a downstream workflow. Each prompt is designed around a specific job and testable output. The best example depends on what is failing. A classification prompt needs clear labels and boundary cases. A research prompt needs approved sources and citation rules. A drafting prompt needs audience, purpose, evidence, and voice. A tool-using prompt needs permissions, action limits, and an escalation path. Concrete examples teach more than generic advice to be specific. They show where context belongs, how output requirements are expressed, and which decisions remain outside the model. They also make evaluation possible because reviewers can compare the result with a known task and expected behavior. Store examples with the input, intended output, scoring notes, prompt version, model, and date. Separate demonstrations shown to the model from test cases used to evaluate it. When the business definition changes, revise the examples and rerun the same held-out set before replacing a production prompt. Put prompt engineering examples under the same change discipline as other business logic. The owner should know the prompt version, data sources, model, tools, expected behavior, and the consequences of an incorrect output. Keep the source beside the result and make changes reversible. This protects the operation when a definition, vendor, model, template, or buyer behavior changes after the original decision. The final review should ask what changed for a buyer or operator. If prompt engineering examples only creates another field, page, prompt, or dashboard, its role remains incomplete. A lead-research prompt receives a company URL and approved source excerpts. It must return company summary, market, employee range, recent trigger, evidence links, and an uncertainty field as JSON. The prompt forbids unsupported estimates and instructs the system to return null when the sources do not support a value. Reviewers score field accuracy and source coverage. A useful prompt example includes clever wording and the operating boundary. It shows what the model may use, what it must produce, and what it should do when the task exceeds the evidence. --- # Features of Marketing Automation | Surface Glossary URL: https://surface.thesurface.network/glossary/features-of-marketing-automation Features of marketing automation are the capabilities used to coordinate repeatable marketing and lead workflows. Common features include audience segmentation, event triggers, schedules, branching rules, email and messaging, personalization, forms, lead scoring, enrichment, routing, CRM synchronization, campaign membership, testing, templates, approvals, consent controls, reporting, alerts, and audit history. Feature names vary by platform. A vendor may combine CRM and automation, while another relies on integrations for identity, advertising, product events, or scheduling. The most useful features support a defined journey and operating requirement. A simple email sequence may need reliable entry, suppression, and reporting more than advanced predictive scoring. A global lifecycle program may need identity resolution, regional consent, account context, versioning, and exception handling. Buyers should examine how a feature behaves when data is missing, rules conflict, or an integration fails. Happy-path demonstrations rarely show the work operators handle every week. Write use cases with real records and edge cases. Test data mapping, timing, permissions, approvals, observability, retries, exports, and audit trails. Confirm which system owns each field and action. Review limits on contacts, events, API calls, branches, users, and history. Include the labor required to maintain workflows and clean data. Score the product against requirements rather than counting capabilities on a page. A company wants to follow up on demo requests within five minutes. The required features are form capture, validation, account matching, existing-owner lookup, routing, scheduling, alerts, suppression, and response-time reporting. A platform with hundreds of campaign templates but weak ownership logic is a poor fit. The evaluation focuses on the complete request path and its exceptions. Keep vendor features in one column and operating requirements in another. A visual journey builder may support the requirement to manage branching, but the team still needs to test limits, permissions, versioning, and error recovery. Ask vendors to run a representative workflow with messy records and conflicting rules. This reveals whether the capability works under the conditions the organization actually has. --- # Forms of Content Marketing | Surface Glossary URL: https://surface.thesurface.network/glossary/forms-of-content-marketing ## What are the forms of content marketing? Forms of content marketing are the repeatable formats and experiences a company uses to communicate with an audience. Articles, research studies, newsletters, videos, webinars, podcasts, templates, comparison pages, case studies, courses, and interactive tools can all qualify. The format alone does not make an asset content marketing. The asset also needs a defined audience, useful substance, and a business reason for existing. B2B teams encounter the choice while planning a campaign or content portfolio. A search question may suit an article, while a buyer evaluating risk may need a case study or live demonstration. Distribution also changes the decision. Material designed for an email subscriber behaves differently from a page intended to earn search traffic over several years. ## Why choosing the right content form matters Treating every idea as a blog post creates a shallow library. Some questions need a compact answer, some need evidence, and others are easier to understand through a visual or interactive experience. Format affects production cost, shelf life, discoverability, accessibility, and the amount of attention required from the reader. It also affects whether sales can reuse the material during an active deal. A useful classification starts with the job. Discovery content helps an audience find and frame a problem. Evaluation content helps buyers compare approaches and examine proof. Enablement content helps a buying group explain the choice internally. Customer content supports adoption, retention, and expansion. One format may serve several jobs, but the team should name the primary one. ## How to plan a mix of content forms Map recurring buyer questions against the journey, current distribution, available expertise, and conversion path. Then choose the lightest format that can answer each question well. Reuse source material where the audience and context permit it. For example, a recorded expert interview might supply a written guide and sales excerpt, yet each version still needs editing for its channel. Review the portfolio for missing decisions instead of chasing a fixed ratio of formats. Consider a security software company with strong traffic to technical definitions and weak conversion among enterprise buyers. The team keeps the reference pages, commissions a benchmark study for risk leaders, records a product workshop for evaluators, and gives sales a short implementation brief. Each asset answers a different question, so success is measured through the behavior expected after that answer. Choose a content form that fits the audience's decision, the evidence available, and the channel where the material will be used. --- # Generative AI Content Marketing | Surface Glossary URL: https://surface.thesurface.network/glossary/generative-ai-content-marketing ## What is generative AI content marketing? Generative AI content marketing is the use of models that create text, images, audio, video, code, or structured outputs within a content marketing program. Teams may use them to synthesize research, propose briefs, draft material, adapt formats, personalize variants, support distribution, and analyze response. Generation is a capability rather than a strategy. A model can produce a plausible article without knowing whether the company should publish it, whether the source evidence is current, or whether the page adds anything the market lacks. Those decisions belong to the content operation. ## Why generative AI content marketing matters Generative tools reduce production friction and make weak choices easier to scale. Teams need stronger selection, source discipline, review, brand judgment, and information architecture as output becomes cheaper. Otherwise the archive grows faster than authority, trust, or conversion. Assign models narrow jobs, supply approved evidence, preserve prompt and source versions, and require human review where claims or public voice matter. Connect assets into hubs and campaigns, plan conversion and distribution, and measure quality, visibility, engagement, lead impact, and maintenance cost. ## How to use generative AI content marketing in practice Use generative AI content marketing to support one named decision. Record the population, market boundary, source type, collection date, method, and limitations so a later reader can judge whether the evidence still applies. Keep the source beside the result and make changes reversible. This protects the operation when a definition, vendor, model, template, or buyer behavior changes after the original decision. The final review should ask what changed for a buyer or operator. If generative AI content marketing only creates another field, page, prompt, or dashboard, its role remains incomplete. A team records three customer interviews, uses a model to extract recurring implementation concerns, and turns the evidence into outline options. A product expert chooses the argument. AI helps draft the guide and create sales and email versions, while an editor verifies every claim and rewrites language that flattened the customers' distinctions. The valuable unit is the marketing system that produces and learns from content. Generation earns its place when it increases useful coverage or reduces manual work without weakening evidence and judgment. --- # Go-to-Market Team | Surface Glossary URL: https://surface.thesurface.network/glossary/go-to-market-team A go-to-market team is the cross-functional group that brings a product or service to a defined market and manages the path from market understanding to revenue and customer value. It may include product marketing, demand generation, sales, revenue operations, partnerships, customer success, product, finance, and leadership. The exact membership depends on the business model and decision. The team is defined by shared outcomes and dependencies rather than a universal org chart. A launch team may be temporary. A standing GTM organization may own segment strategy, pipeline, revenue, retention, or expansion across several products. 1. **Choose the market and objective.** Define the segment, problem, offer, commercial goal, time horizon, and evidence behind the choice. Record assumptions about demand, pricing, competition, and the buying process. 2. **Build one operating model.** Connect positioning, campaigns, content, channels, qualification, routing, sales plays, onboarding, customer outcomes, and measurement. Clarify where specialized teams own execution. 3. **Assign decision rights.** Name who decides market scope, message, price, launch readiness, lead definitions, account ownership, exceptions, and changes to the plan. Cross-functional should not mean ownerless. 4. **Coordinate the handoffs.** Define service levels and shared records for marketing-to-sales, sales-to-implementation, and customer feedback. Make delays and conflicts visible. 5. **Run a learning cadence.** Review market signals, campaign evidence, sales conversations, product use, customer outcomes, revenue, and cost. Change the next decision when a repeated pattern appears. - Which business outcome the GTM team owns and which outcomes remain with functions. - Who represents product, buyer, commercial, operational, and customer evidence. - Which decisions require the whole team and which belong to one accountable owner. - How plans, definitions, risks, and changes are documented. - Which leading and lagging measures suit the sales and customer cycle. - How capacity constraints affect the market promise and launch timing. Internal coordination can become the team's entire job. Meetings multiply, plans look aligned, and customer evidence reaches the room only through summaries. A GTM team needs direct access to research, sales calls, product use, support, win-loss findings, and partner feedback. Use the evidence to revise assumptions, not to decorate a decision already made. A launch date, segment, or message should be allowed to change when the market and operating readiness do not support it. The common failure is consensus without accountability. Every function comments on every decision, deadlines slip, and no one can say who has final authority. The team may also optimize its own launch checklist while buyers encounter a weak handoff, missing proof, or slow response. A better model gives one owner to each consequential decision and uses the cross-functional group to supply evidence, expose dependencies, and commit resources. The team reviews the complete customer and revenue path. Its value comes from coordinated judgment and execution, not the number of functions represented in the meeting. Use separate forums for execution, learning, and major decisions. A weekly operating review can resolve campaign, routing, capacity, and launch blockers. A monthly market and revenue review can examine segment movement, sales evidence, customer behavior, forecast, and resource changes. A quarterly strategy review can revisit the market choice and investment thesis. Keep the materials concise and decision-centered. Each issue should include the owner, evidence, implication, options, and due date. Record decisions where affected teams can find them. Avoid making every participant attend every forum. Bring the people whose evidence or authority the decision needs. Track unresolved assumptions as carefully as tasks. A launch can complete every production item while its pricing or market premise remains weak. The GTM team should know which assumptions it accepted, which evidence would challenge them, and when the review will occur. A product-led company may place product and lifecycle roles near the center. An enterprise sales motion may rely more on product marketing, account work, implementation, and customer success. Partner-led growth changes the evidence and handoffs again. Build the team around the chosen path to market, then revisit the structure when that path changes. --- # Goal of Market Research | Surface Glossary URL: https://surface.thesurface.network/glossary/goal-of-market-research The goal of market research is to reduce uncertainty around a market decision. Research helps a team understand demand, customers, competitors, alternatives, needs, prices, messages, channels, buying behavior, or outcomes well enough to choose and act. It does not remove risk or produce certainty on command. The practical goal changes with the decision. A company may need to discover an unknown problem, describe a segment, compare concepts, estimate opportunity, explain lost deals, or evaluate a launch. The research succeeds when the evidence improves the decision and remains clear about its limits. 1. **Name the decision.** State the owner, alternatives, deadline, and consequence of error. A topic such as "customer needs" becomes useful when tied to a product, segment, or message choice. 2. **Identify the uncertainty.** Separate what is known, assumed, disputed, and missing. Prioritize the gap that could change the decision. 3. **Set the evidence standard.** Decide which population, method, sample, source quality, and confidence the choice requires. A reversible campaign test may need less evidence than a market entry investment. 4. **Choose the method.** Match exploratory, descriptive, comparative, causal, or predictive work to the question. Combine sources when one method cannot represent the decision. 5. **Define the action.** Explain how different findings would affect the plan. Preserve the ability to accept an inconvenient result. 6. **Review the outcome.** After acting, compare what happened with the research expectation. Use the difference to improve the next study and decision. - Whether the work must discover, measure, compare, explain, predict, or evaluate. - Which buyers, users, nonbuyers, customers, or market participants belong in scope. - Which definitions and market boundaries must remain stable. - How much time and budget match the consequence of the choice. - Who interprets the findings and who owns the resulting action. - When changing conditions will make the evidence stale. Research can produce attractive reports that never challenge or change a plan. Prevent this by agreeing on the decision path before collection. Stakeholders should know what evidence would support, revise, delay, or stop an option. They should also know which questions the study cannot answer. Good research may reveal that no immediate decision is justified. A finding that the evidence remains weak is useful when it prevents a confident investment based on assumption. The common failure is treating research as confirmation. A preferred launch, message, or market already exists, and the study is asked to supply supportive quotations or percentages. Leading questions and selective samples then make the conclusion look inevitable. A stronger process includes competing explanations and records contrary evidence. Researchers show source, date, population, method, and uncertainty beside each conclusion. Decision makers still exercise judgment, but they can see where the market informed the choice and where the company accepted a risk. A discovery goal may use open interviews, observation, or source review to uncover possibilities. A measurement goal needs stable definitions, a credible sample, and quantitative analysis. A comparison goal needs equivalent exposure or matched groups. A causal goal requires a design that can rule out competing explanations. A forecasting goal needs historical data, assumptions, and validation. Do not ask one study to perform every job. A survey can measure reported preference without proving why the preference exists or whether it will produce purchase. An experiment can show a response difference without explaining the market mechanism. Sequence methods when the decision requires both explanation and measurement. State the smallest useful result before research begins. Sometimes the goal is to eliminate one option, clarify one segment, or discover which question deserves a larger study. This keeps the effort proportionate and gives teams a decision while the evidence is still current. Some research supports a continuing learning system rather than one launch decision. Customer panels, brand tracking, competitor monitoring, and win-loss programs can reveal change over time. These programs still need owners, stable definitions, review cadence, and decisions they are expected to inform. Ongoing research without a use becomes an archive that grows faster than anyone's ability to interpret it. --- # Good Market Research Questions | Surface Glossary URL: https://surface.thesurface.network/glossary/good-market-research-questions Good market research questions specify the uncertainty a study must reduce for a decision. They identify the population or market, the behavior or perception of interest, and the boundary of the claim. They are neutral enough to allow an unwelcome answer and concrete enough to guide a method. A research question is broader than the wording asked in an interview or survey. "Do customers like our product?" is weak because liking has no agreed meaning and the answer may not change an action. "Which onboarding step prevents new administrators at mid-market accounts from completing setup in the first week?" identifies a group, behavior, period, and operational choice. Several instrument questions and event analyses may support that one research question. A vague question produces a study that gathers interesting material without resolving the choice. A leading question turns research into approval seeking. Questions can also overreach by asking one method to prove more than it can, such as using interviews to estimate prevalence or asking a survey to explain causal behavior. Clear wording exposes those design errors before collection begins. Write the decision first, then list what the team currently assumes and which answer would change the plan. Classify the needed claim as exploratory, descriptive, comparative, predictive, or causal. Add the target population, relevant period, unit of analysis, and known exclusions. Break large questions into a small hierarchy, keeping one primary question that prevents the project from becoming an unrelated list. Ask whether a respondent or data source can answer from direct experience, whether the terms have one meaning, and whether the team can act on either result. Remove claims hidden inside the question. Avoid combining two subjects in one sentence. Before fieldwork, choose the evidence required, analysis approach, and condition that would weaken the current belief. Pilot instrument wording separately with members of the intended population. A company considering a lower-priced plan first asks, "Would small businesses buy a cheaper version?" The research team revises it to: "For US firms with 10 to 50 employees that evaluated the product in the past six months, which requirements prevented purchase, and how often was budget the primary barrier?" Interviews explore requirements, while a structured lost-deal review estimates frequency. A good research question gives the study a boundary and gives the business a decision it can make when the answer arrives. --- # Growth Marketing Discipline | Surface Glossary URL: https://surface.thesurface.network/glossary/growth-marketing Growth marketing is a cross-functional discipline for improving sustainable customer and revenue growth through evidence, intervention, and learning. It examines acquisition, activation, retention, expansion, and referral as connected parts of one system. Teams use customer research, journey analysis, channel work, product changes, lifecycle programs, and experiments to address the constraint that currently limits growth. The term does not mean pursuing every tactic that raises a number quickly. Sustainable growth accounts for customer fit, revenue quality, cost, margin, retention, capacity, consent, and experience. The function may live in marketing or product, yet it depends on shared work with sales, success, finance, engineering, and data teams when changes cross their boundaries. Start with a growth model that shows how customers enter, reach a useful outcome, remain, and create economic value. Audit whether its events and definitions can be trusted. Use the model to identify the largest current constraint, then combine quantitative patterns with direct customer and operator evidence. Select an intervention that can test a specific explanation while protecting the rest of the customer system. 1. Define the growth model. Specify customer units, segments, acquisition paths, activation behavior, retention window, expansion, revenue, cost, and capacity. Reconcile the model with finance and operational systems. 2. Locate the current constraint. Examine cohorts and journey transitions, then investigate the affected moment through interviews, observation, sales notes, support evidence, or usability work. 3. Prioritize an intervention. Estimate expected effect, confidence, effort, time to learn, customer risk, and dependencies. Reserve space for measurement repair and learning from previous work. 4. Implement with guardrails. Define assignment or comparison, exposure, quality checks, stop conditions, rollback, and owners. Monitor whether the change reached the intended population as designed. 5. Turn the result into system knowledge. Record segment effects, costs, side effects, uncertainty, and the next decision. Update the growth model and operating process rather than preserving a winning variant without context. Metrics should follow the growth model and the decision. A retention intervention may need cohort survival, meaningful product use, support demand, expansion, and margin over enough time to observe the effect. A conversion intervention may need qualified outcomes and later customer quality. Statistical uncertainty matters, and so does practical size. A detectable lift can still be too small or costly to implement broadly. Maintain a backlog connected to documented evidence and a register of completed interventions. For each item, preserve the problem, population, hypothesis, metric definition, comparison, implementation notes, result, decision, and owner. Review the mix of work across lifecycle stages and customer segments. Require more scrutiny for pricing, consent, eligibility, or product changes than for low-risk creative tests. Share negative and inconclusive results so the team does not repeat them under a new name. - Which model and customer outcome define sustainable growth for the business? - Which current constraint deserves attention before smaller opportunities? - What evidence, comparison, and time horizon can support the decision? - Which teams own implementation, customer risk, and downstream effects? - How will learning change the model, roadmap, or standard process? A company may choose speed during an early reversible test and demand stronger proof before a wide rollout. That choice should be visible. Growth teams also need a stopping rule for interventions that improve one metric while damaging lead quality, retention, service workload, accessibility, trust, or unit economics. Define who has authority to stop an active test when a guardrail fails, including outside normal review hours. A common failure is operating a test factory. The team changes buttons and messages because those are easy to randomize, while the main constraint sits in product value, sales capacity, or customer onboarding. Results accumulate without a shared model, and the same audience experiences overlapping tests that make interpretation impossible. Pause the backlog and rebuild the system view. Reconcile customer identity and lifecycle metrics, choose the largest defensible constraint, and interview the people closest to that moment. Retire tests with no decision owner. Resume with fewer interventions, explicit guardrails, and a review that connects each result to the next operating choice. --- # Growth Marketing Strategies | Surface Glossary URL: https://surface.thesurface.network/glossary/growth-marketing-strategies Growth marketing strategies are repeatable approaches used to improve a measurable stage of customer growth. They can address acquisition, activation, retention, expansion, referral, or the handoffs between them. The work combines market understanding, channel execution, product and lifecycle experience, experimentation, and cohort economics. The plural matters because growth rarely comes from one universal playbook. Companies with low category awareness may invest in education and distribution. Products with strong demand and weak activation may improve onboarding before buying more traffic. Sales-led businesses may focus on qualification and response time. Optimizing one stage can move the problem elsewhere. Aggressive acquisition may lower lead quality. Discounts can raise conversion and weaken payback or retention. Growth work needs a shared customer and revenue model so a local win does not create a larger downstream cost. Diagnose the constraint with quantitative and qualitative evidence. Choose a segment, behavior, mechanism, and metric, then write a hypothesis and expected time horizon. Set guardrails for quality, margin, consent, customer experience, and team capacity. Measure cohorts through the downstream outcome the strategy is supposed to improve. Keep a portfolio of experiments and durable programs. Experiments test uncertainty; successful ones still need operating ownership, data, documentation, and maintenance. Record null and negative results so teams do not repeat abandoned ideas. Review whether performance came from a temporary incentive, channel shift, measurement change, or a customer behavior likely to persist. For one collaboration product, efficient paid acquisition hides weak team activation. Marketing and product stop expanding spend, revise the invitation experience, add role-specific onboarding, and trigger help when an account stalls. Activation and retained usage improve, after which paid investment can grow without sending more customers into the same failure. Growth marketing strategies should begin with the current constraint and end with a result that survives beyond the first conversion. Keep the learning record after a test ends so future teams can distinguish an abandoned idea from an untried one. --- # Content Marketing and Sales | Surface Glossary URL: https://surface.thesurface.network/glossary/how-content-marketing-drives-sales ## How does content marketing drive sales? Content marketing drives sales when useful material changes a buyer's understanding or behavior in a way that contributes to a purchase. It can introduce a problem, answer an active question, establish category fit, supply evidence, address risk, or help a buying group reach internal agreement. The sales effect may occur before a lead identifies themselves or during an open opportunity. The connection is rarely a single click followed by a contract. B2B buyers may read several pages, return through search, share a guide with colleagues, attend an event, and speak with sales weeks later. Some content creates new interest while other content captures existing demand or improves conversion among known opportunities. Traffic and engagement can rise without affecting revenue. A page may reach the wrong audience, answer a question far outside the product's market, or end without a sensible next step. Conversely, a low-traffic comparison page may help several large deals. Teams need to identify the buyer decision each asset supports before selecting its success measure. Map content to a small set of commercial jobs: problem education, solution discovery, evaluation, proof, objection handling, implementation confidence, or customer expansion. Give each asset a primary audience and a next action suited to intent. Connect anonymous page behavior to aggregate conversion trends, and use identified engagement only where consent, identity quality, and sales usefulness justify it. ## How to measure content's contribution to sales Combine leading and downstream evidence. Search visibility, qualified visits, engaged reading, return behavior, and calls to action describe the path into a conversation. Accepted meetings, opportunity creation, stage movement, win rate, deal velocity, and seller use describe later influence. Compare cohorts and use controlled tests where possible. Attribution can organize touchpoints, but it cannot prove that one page caused the sale. A payroll platform publishes a state-by-state compliance hub. Organic visits grow, yet demo volume barely moves. Interview notes show that finance leaders worry most about switching risk. The team adds implementation timelines, migration checklists, customer evidence, and links to a focused consultation. Sales starts sharing the pages in active deals, and the company tracks influenced opportunities separately from first-touch leads. Content earns a place in the sales system when its audience, decision, next action, and downstream evidence are clear. --- # Content Marketing for SEO | Surface Glossary URL: https://surface.thesurface.network/glossary/how-content-marketing-helps-seo ## How does content marketing help SEO? Content marketing helps SEO by producing useful pages that search systems can discover, interpret, and match to real audience questions. Strong content can cover a topic deeply, earn links and references, strengthen internal paths, clarify a company's expertise and entities, and give organic visitors a reason to continue toward a commercial decision. Publishing volume alone does not improve search performance. Pages compete for attention, crawl, internal authority, and maintenance. Repeated definitions or thin posts can split relevance and leave readers without comparison, proof, or implementation detail. Content contributes when each asset has a distinct job inside a maintained system. ## Why content marketing for SEO matters SEO can identify demand and technical access, while content marketing determines what the company has worth finding. The two meet in page purpose, evidence, information architecture, internal links, distribution, and conversion. Search traffic is more useful when the page also teaches the category and supports the reader's next decision. Map audience questions to business-relevant topics, then assign one page to own each intent. Build hubs that connect definitions, methods, comparisons, proof, implementation, and product context. Use original evidence and expert review where the market lacks a good answer. Keep titles, canonicals, structured information, and internal links consistent with the visible page. ## How to use content marketing for SEO in practice Measure discovery and business movement separately. Track query coverage, rankings, clicks, citations, links, and indexation alongside engaged visits, internal movement, conversions, accepted leads, sales use, and pipeline influence. Refresh pages when the answer, product, market, or search presentation changes; consolidate pages that compete for the same job. A company has six short articles about lead routing. It consolidates repeated definitions into one operating guide, keeps a narrower page for routing rules, adds customer evidence and a troubleshooting page, and links the group to a relevant product workflow. Organic entry grows slowly, while sales begins using the guide in active evaluations. Content marketing helps SEO when it gives search systems and people a clear, credible body of work with useful paths beyond the first visit. --- # Content Marketing and Digital Marketing | Surface Glossary URL: https://surface.thesurface.network/glossary/how-does-content-marketing-support-digital-marketing ## How does content marketing support digital marketing? Content marketing supports digital marketing by creating the useful material that search, email, social, paid media, partnerships, sales, and website experiences distribute. It gives campaigns an idea, gives buyers a reason to pay attention, and gives the site a path from discovery through education, comparison, proof, and conversion. Digital marketing is the broader set of online channels, experiences, data, and operations used to reach and convert audiences. Content marketing is one strategic system inside it. The relationship works in both directions: channel and sales data reveal audience questions, while content turns those questions into assets the channels can use. ## How content marketing supports digital marketing in practice Start with the audience problem and business objective, then design a source asset and its connected adaptations. Build search architecture, paid landing experiences, email sequences, social formats, sales follow-up, and conversion pages from the same evidence while respecting the behavior of each channel. 1. Define the campaign or growth problem and the audience decision. Choose a content job such as education, category creation, comparison, objection handling, proof, or activation. 2. Create the source layer from research, product expertise, customer evidence, and a clear point of view. Record claims and internal links before adapting the material. 3. Publish the durable site asset with search, AI visibility, accessibility, conversion, and measurement needs in mind. Connect it to related pages instead of leaving it isolated. 4. Adapt the idea for email, social, paid creative, partner distribution, events, and sales. Preserve the central claim while changing length, format, and call to action for the channel. 5. Measure discovery, engagement, movement, conversion, sales use, and business outcome. Feed query data, comments, objections, and lead quality into the next content decision. Measure the content at asset and campaign levels. Search visibility, AI citations, reach, engagement, email response, landing conversion, accepted leads, sales usage, assisted pipeline, and customer feedback describe different parts of the system. Do not force every contribution into last-click attribution. For content marketing support for digital marketing, build a decision brief that keeps the market boundary and evidence types visible. List the population, geography, segment, period, inclusion rules, sources, dates, method, and assumptions. Separate direct observations, participant reports, vendor claims, modeled estimates, and internal interpretation. When sources disagree, show the disagreement and explain which definition or method creates it. A later reviewer should be able to update one assumption without rebuilding the entire argument. Create a short release checklist for content marketing support for digital marketing and assign each item to a role. Include source verification, permissions, privacy, required approvals, error visibility, downstream compatibility, and rollback. Keep the checklist close to the workflow so it changes when the workflow changes. After release, review exceptions before aggregate performance because an average can improve while a small number of high-value cases fail badly. Connect the local content marketing support for digital marketing workflow to the decision that follows it. Documentation should show what the next operator receives and which context must survive the handoff. Before expanding content marketing support for digital marketing, compare several outputs with the source material and with the decision made by a competent operator. Record false positives, false negatives, missing cases, and disagreements about definitions. Use that sample to update the rule, test set, documentation, or training rather than explaining every error as an isolated exception. The review should end with a named change and an owner, even when the change is to keep the current scope. For content marketing support for digital marketing, note unresolved questions beside the approved process. Visible limitations invite review; hidden assumptions tend to survive until a customer, report, or integration exposes them under worse conditions. - Which audience problem and digital objective should the content solve? - Which asset holds the durable source and which formats are adaptations? - How will each channel change the framing, evidence, and next action? - Which landing, proof, or product page continues the buyer's path? - Which feedback signals will change the next brief or campaign? Content should enter campaign planning early. Asking for a blog after the channel plan is complete usually produces a generic supporting asset. When the content argument and channel mechanics develop together, every touchpoint can carry more specific evidence. A common failure is treating content as top-of-funnel inventory. The blog team optimizes traffic, paid media creates separate landing pages, email rewrites the message, and sales builds its own deck. The company pays several times to express inconsistent versions of the same idea. Choose one campaign argument, build a shared evidence layer, assign distinct jobs to durable and channel assets, and connect all versions to the same buyer path. Review performance together so channel data improves content and content improves channel efficiency. --- # Importance of Clean Data | Surface Glossary URL: https://surface.thesurface.network/glossary/importance-of-clean-data Clean data is important because business systems turn stored values into decisions. Marketing segments audiences, sales prioritizes accounts, workflows assign owners, analytics calculates performance, and leaders allocate budget from those records. Errors at the source can travel through every downstream action. Clean does not mean complete or perfect. It means fit for a defined use, with known quality, provenance, and uncertainty. A missing field can be safer than an inferred value presented as fact. Different decisions require different thresholds. Trusted records reduce wasted work and customer friction. Reps receive leads that match their territory, campaign reports reconcile, customers leave acquisition sequences at the right time, and teams spend less time maintaining private repair spreadsheets. Clean data also makes real exceptions visible. Identify fields tied to high-consequence decisions, define their source and validation, preserve change history, and monitor defects by origin. Use raw and normalized fields separately, review uncertain identity changes, and assign owners to the forms and integrations that create recurring problems. Prioritize clean data by consequence. Identity, consent, ownership, account relationships, lifecycle, and revenue fields usually need stricter controls than optional profile attributes that do not trigger action. Keep the source beside the result and make changes reversible. This protects the operation when a definition, vendor, model, template, or buyer behavior changes after the original decision. The final review should ask what changed for a buyer or operator. If clean data only creates another field, page, prompt, or dashboard, its role remains incomplete. A company routes enterprise demo requests by employee count. Submitted values, enrichment values, and CRM account values disagree. The team records all three, defines a source-precedence rule with a recency check, and sends unresolved high-value accounts to review. Routing accuracy improves without erasing the conflicting evidence. Clean data earns trust through traceability. People should be able to see where a value came from, when it changed, and why the system used it. --- # Importance of Market Research | Surface Glossary URL: https://surface.thesurface.network/glossary/importance-of-market-research Market research is important because companies make decisions about people, demand, competitors, pricing, products, and messages with incomplete information. Research gives those assumptions a method, source record, and boundary. It can support a choice, narrow it, delay it, or show that the available evidence is too weak for the proposed commitment. Internal teams experience the market through different filters. Sales hears active buyers, support hears current customers, product sees measured use, and leaders hear selected strategic accounts. Each view is real and incomplete. Research defines the population and question so one vivid conversation or one aggregate metric does not quietly become a claim about everyone. Research deserves more attention when the decision is expensive, difficult to reverse, based on unfamiliar buyers, or sensitive to changing market conditions. Market entry, pricing, product direction, positioning, and large campaign investments fit that description. Lower-risk choices may need lighter evidence, especially when the company can test and recover quickly. The method should be proportionate to the consequence. The discipline also preserves institutional memory. A decision record can show which evidence was available, which sources conflicted, what remained uncertain, and why leaders acted. Later teams can update the relevant assumption instead of repeating the whole debate. This makes research an operating input rather than a presentation that disappears after approval. Invite the decision owner to define alternatives and the evidence that would change the plan. Choose a method that supports the intended claim, then keep raw material and limitations accessible. Present findings around the decision, including contradictory cases and uncertainty. Record the action, owner, review date, and early signal that would reopen the choice. Research without a decision path is easy to admire and easy to ignore. A company plans a national campaign around speed because existing customers praise fast setup. Research with lost prospects finds that security review, not setup, controls the buying timeline for larger accounts. The team keeps speed messaging for smaller firms, changes the enterprise campaign, and creates proof for security reviewers. One broad claim becomes two segment-specific choices grounded in different evidence. Market research matters when it changes how confidently and responsibly a company commits people, money, product effort, or reputation. --- # Inbound Lead Management | Surface Glossary URL: https://surface.thesurface.network/glossary/inbound-lead-management Inbound lead management is the process used to handle identifiable interest that arrives through a company's website, product, content, events, chat, phone, or other inbound channels. It covers capture, validation, identity and account matching, qualification, routing, response, nurture, status changes, rejection, recycling, and measurement. The process begins when a person or account creates a record or meaningful signal. A demo request, trial signup, webinar registration, contact message, and high-intent chat need different treatment. Some require immediate sales action, some belong in education, and others are customers, partners, students, vendors, or spam that should never enter a new-business queue. Inbound demand decays when ownership is unclear or context disappears between systems. Duplicate records may create several responses, enrichment can assign the wrong account, and a routing rule can leave a valid request without an owner. Lead volume therefore says little without acceptance, response time, meeting, opportunity, and rejection evidence by source and segment. Define each inbound signal, required data, eligibility, disqualification reasons, owner, service level, and fallback. Preserve the page, campaign, message, and stated request that created the record. Check existing customer and opportunity status before assigning new-business treatment. Use enrichment as supporting evidence and keep a review queue for ambiguous accounts or territories. Monitor the entire path, including failed form writes, delayed integrations, unmatched accounts, unassigned leads, response attempts, acceptance, recycling, and closed-loop outcomes. Give sales a small set of specific rejection reasons and review them with marketing. Test routing after territory, staffing, product, CRM, or form changes. Respect consent and channel preferences when moving a lead into nurture. A software company receives a pricing request from a director at an existing customer. The form creates a new contact because the email alias differs from the CRM record. Account matching finds the company and routes the request to the customer owner rather than the new-business queue. The source page and requested product remain visible, so the owner responds as an expansion conversation. Inbound lead management turns a captured signal into an owned, context-aware next action and preserves the outcome for learning. --- # Industry Analysis | Surface Glossary URL: https://surface.thesurface.network/glossary/industry-analysis Industry analysis is the systematic study of a defined sector's structure, customers, suppliers, competitors, substitutes, regulation, economics, technology, and change. Businesses use it to assess attractiveness, risk, positioning, entry, investment, partnerships, and strategic response. An industry is a chosen analytical boundary. The definition should state which products, buyers, geographies, and business models belong inside it. A narrow category can hide substitutes, while a broad label can combine companies with very different economics. Begin with the decision and boundary, then collect evidence across market size, growth, value chain, buyer power, supplier dependencies, rivalry, substitutes, entry barriers, regulation, and profit pools. Compare sources and dates, because industry estimates often disagree and vendor-sponsored reports may define the market to support a commercial narrative. 1. Define the industry, geography, customer, time period, and decision. List adjacent categories and substitutes that could make the chosen boundary misleading. 2. Map the value chain and major participant groups. Show who creates, distributes, pays for, regulates, and captures value rather than listing competitors alone. 3. Collect quantitative and qualitative evidence on demand, growth, pricing, costs, concentration, switching, regulation, technology, and buyer behavior. Label estimates and assumptions. 4. Analyze forces and scenarios. Identify which conditions support attractive economics, which could change quickly, and where the company has a credible advantage or exposure. 5. Translate findings into a decision, indicators to monitor, and a date for review. Keep the source record so changes can be compared with the prior baseline. The analysis should be judged by boundary clarity, source quality, assumption visibility, decision relevance, and how well monitored indicators explain later change. A single market-size number or competitor grid is too narrow to represent industry structure. The operating discipline for industry analysis is a chain from question to source to interpretation to decision. Preserve interview notes, survey instruments, queries, public records, and dated product evidence with enough context to audit the conclusion. Add a confidence statement and the observation that would reverse the recommendation. This avoids the familiar research failure where a clean slide outlives the evidence and continues to guide positioning after the market has changed. Set the review cadence for industry analysis according to volatility and consequence. Fast-changing inputs may need weekly checks, while stable reference material may suit a quarterly factual review. The owner should inspect input quality, output quality, timing, exceptions, and business outcome. Record which finding changes the rule and which finding only needs observation. Do not let the primary tool, spreadsheet, or configuration become the only documentation. A plain-language record of purpose and consequences makes industry analysis easier to audit, teach, change, and retire. Maintain an exception log for industry analysis that is small enough to review and structured enough to learn from. Capture the input, expected behavior, actual result, consequence, immediate repair, and root cause. Group recurring exceptions by source, rule, segment, template, or integration. This makes industry analysis improve through evidence and prevents the same workaround from being rebuilt by several teams in different tools. Keep a short industry analysis limitations note with the current process. It should name missing evidence, unsupported cases, and dependencies that could invalidate the approved approach. - Which category boundary and substitutes reflect the customer's actual choice? - Which economic and regulatory forces matter to the decision? - Which estimates are comparable, and where do source definitions differ? - Which scenario would reverse the current recommendation? - Who owns monitoring after the initial analysis? Industry analysis should reduce strategic surprise. The goal is a model of how the sector works and which signals would show that the model is becoming wrong. A common failure is producing a market map made of logos and funding totals. The artifact shows who exists but not who pays, where margins sit, how customers switch, which constraints limit growth, or why one position could be defensible. Rebuild around the value chain, customer decision, and economic forces. Add missing substitutes and regulation, reconcile source definitions, and connect each conclusion to an assumption the team can monitor. --- # Inside Sales Lead Generation | Surface Glossary URL: https://surface.thesurface.network/glossary/inside-sales-lead-generation Inside sales lead generation is the use of phone, email, video, social, chat, and other remote channels to identify and engage potential buyers. The work may include outbound prospecting, inbound response, qualification, meeting creation, account research, and early discovery. It is usually performed by sales development, business development, or inside sales teams working with marketing and revenue operations. The phrase describes the motion, not the quality of the lead. A contact becomes useful when the team has a legitimate reason to reach out, enough context for a relevant conversation, and a clear path after the response. Inside sales works at the person or account level and expects a direct response. Demand generation can shape awareness among a wider market that remains anonymous. The two connect when marketing signals, content, events, referrals, or product behavior give inside sales a reason and context for follow-up. Outbound work also creates its own leads through researched account selection and conversation. Define the target account, role, problem, trigger, offer, outreach rules, qualification, and handoff. Give representatives useful research and proof rather than a long personalization checklist. Preserve consent and regional requirements. Coordinate account ownership and suppress customers, active opportunities, partners, or recent contacts where appropriate. Measure contactability, conversations, accepted meetings, opportunities, time, cost, and disqualification beside activity volume. An inside sales team targets manufacturers hiring reliability engineers. The hiring signal suggests an active operational need, but the representative confirms product fit and current process before proposing a meeting. Marketing supplies a technical brief and account evidence. Operations prevents duplicate outreach to existing opportunities. The program evaluates productive conversations and pipeline by trigger, not the number of emails sent. Inside sales should return structured feedback on message response, account fit, timing, objections, and disqualification. Marketing can use the patterns to change audiences and offers. Operations can adjust data, sequencing, and routing. Keep activity targets from overwhelming this learning loop. Representatives who must maximize touches have little room to record why a conversation did or did not progress. --- # CSV as Structured Data | Surface Glossary URL: https://surface.thesurface.network/glossary/is-csv-structured-data CSV is usually treated as a structured data format because it organizes values into rows and columns. Each row can represent the same type of record and each column can represent a defined field. The format itself, however, stores plain text and does not enforce types, relationships, required values, or business meaning. A clean export with one lead per row and stable columns for email, company, source, and created date is structured. A CSV that mixes leads and accounts, changes the meaning of columns midway through the file, or stores several values in one free-text cell has a tabular shape without a reliable schema. The distinction affects imports and analysis. Spreadsheet software may guess that an identifier is a number, remove leading zeros, or interpret a date differently by locale. Commas, line breaks, encoding, and duplicate headers can also corrupt an otherwise simple exchange format. Define the row grain and column dictionary before sharing the file. Specify encoding, delimiter, header names, data types, null values, date format, unique identifier, and whether fields may contain line breaks. Validate the file against that contract before importing it into a CRM, warehouse, or automation. Teams can make CSV as structured data easier to maintain by treating it as a data contract. Name the object, its stable identifier, its permitted properties, and the source responsible for each value. Review a sample of real cases before relying on an aggregate score. The sample should include incomplete, conflicting, and high-value records because averages often hide the failures with the largest business cost. Place the documentation for CSV as structured data beside the workflow or decision it affects. That keeps definitions, evidence, ownership, and later corrections available to the people who need them. A team exports webinar registrants as CSV. The contract says one row per registration, timestamps use ISO format, country uses two-letter codes, consent is true or false, and registration ID is the unique key. The importer rejects rows with missing IDs and keeps the original file for audit rather than allowing spreadsheet guesses to rewrite values. CSV can carry structured data, but the schema lives in the agreement around the file. Without that agreement, rows and columns provide appearance rather than dependable meaning. --- # Lead Capture Forms | Surface Glossary URL: https://surface.thesurface.network/glossary/lead-capture-forms Lead capture forms are website or in-product forms that collect information from a person who wants something from a company. The request may be a demo, trial, event registration, report, consultation, newsletter, or contact response. The form turns anonymous activity into an identifiable record and supplies the data needed for the next action. A useful form asks only for information that changes fulfillment, qualification, routing, consent, or follow-up. Every extra field adds effort and creates another value the team must validate, store, protect, and maintain. The form sits at the boundary between marketing experience and operational data. A short form may convert more visitors while leaving sales without company, role, or intent context. A long form may improve routing inputs but discourage qualified buyers. Hidden fields, enrichment, progressive profiling, and account matching can reduce visible effort, though each method introduces its own accuracy and privacy requirements. Form design also controls expectations. The page should say what the person will receive, when the company will respond, and how the information will be used. Define the request type first. Select fields based on the decision that follows. Validate formats, preserve the original source, capture consent where required, and handle duplicates without creating competing records. Set clear success and error states. Test mobile use, accessibility, spam protection, CRM creation, ownership, alerts, suppression, and scheduling. Review abandonment, completion, data validity, routing speed, sales acceptance, and downstream conversion together. A higher completion rate is useful only if the resulting records can be served well. An enterprise demo form asks for work email, company, role, country, and a short description of the project. Enrichment supplies company size and industry after submission. Existing account ownership takes precedence over territory rules. If enrichment fails, the request still reaches a human queue instead of waiting silently. The team removes a phone field after learning that it did not change routing or meeting completion. Record the form owner, field purpose, validation, destination, consent language, source tracking, routing dependency, retention, and review date. Keep a test submission for every major path. When a field no longer changes a decision, remove it or explain why the business still needs it. This keeps the form aligned with the request rather than the history of past campaigns. --- # Lead Generation Process Flow | Surface Glossary URL: https://surface.thesurface.network/glossary/lead-generation-process-flow A lead generation process flow is the documented path from audience attention to an identifiable lead, qualification decision, owner, follow-up action, and commercial outcome. It connects campaign design with forms, enrichment, consent, CRM records, scoring, routing, sales response, nurture, and reporting. The flow should show where a record can pause, fail, merge, re-enter, or leave the process. Teams use the flow to expose handoffs that a campaign diagram misses. A form submission may look like the end of marketing work, yet the buyer still depends on validation, ownership, timely contact, useful context, and a next step that matches the request. 1. **Create qualified attention.** Marketing chooses an audience, problem, offer, channel, and destination. Tracking records the source and campaign without requiring every visitor to identify themselves before receiving value. 2. **Capture the response.** A form, event registration, chat, trial, referral, or partner handoff creates or updates a person and account record. The system records consent, request type, timestamp, page, campaign, and original values before enrichment changes them. 3. **Validate and qualify.** Rules check contactability, spam, duplicates, account fit, role, geography, and intent. Enrichment may add context. The team separates known facts from inferred fields and sends uncertain high-value records to review. 4. **Route and act.** The process applies account ownership, territory, segment, product, and availability rules. It creates the task, notification, or scheduling path and starts a response clock. A visible exception queue handles conflicts and missing information. 5. **Nurture or recycle.** Records that are real but not ready receive communication that fits their stage and consent. Clear exit and re-entry rules prevent people from remaining in the same sequence after their situation changes. 6. **Measure the result.** Marketing and sales connect source, qualification, response, meeting, opportunity, revenue, disqualification, and time-in-stage data. They use the results to change audience, offer, form, scoring, routing, or follow-up. - Which events create a lead and which remain anonymous engagement. - Which system owns identity, lifecycle stage, account, consent, and source. - What qualifies for immediate sales action, nurture, review, or rejection. - How existing account ownership interacts with territory and round-robin rules. - Which service levels apply to each request and who monitors exceptions. - How duplicate, incomplete, spam, partner, and customer records are handled. Assign an owner to every transition, including automated ones. Record the reason for qualification, reassignment, rejection, and recycling. Compare volumes at each step so records cannot disappear between a form count and a CRM report. Review time as well as conversion. A strong rate can hide a response that arrived after the buyer chose another vendor. Test the flow with realistic records before launch. Include an existing customer, open opportunity, duplicate contact, target account, missing country, personal email, opt-out, and conflicting owner. Repeat the test after field, integration, or territory changes. The most common failure is treating lead generation as a top-of-funnel volume program. Marketing optimizes submissions, operations optimizes automation, and sales decides independently which records deserve attention. Each local metric can improve while the buyer experiences delays and irrelevant follow-up. A better flow uses one set of stage definitions and preserves feedback from the final disposition. If sales rejects a lead, the reason should change scoring, targeting, or capture rules when the pattern repeats. The process becomes useful when the outcome informs the next campaign decision. Measure the count and elapsed time at every transition. Useful checks include visit-to-response conversion, valid-record rate, enrichment success, review volume, assignment time, acceptance, first contact, meeting completion, opportunity creation, and disqualification by reason. Keep raw counts beside rates so a small denominator cannot create a dramatic but misleading improvement. Use cohorts based on capture date and request type. A recent group has had less time to create opportunities than an older one. Separate high-intent requests from content registrations, partner referrals, product signups, and outbound responses because each path carries different expectations. Reconcile campaign, form, CRM, and sales totals at stable boundaries. The review should end with a process decision. A slow review queue may require a simpler rule or more ownership. Repeated bad matches may require better account identity. Weak meetings from one offer may require a different promise. Reporting earns its place when it changes the flow. --- # Lead Generation via Social Media | Surface Glossary URL: https://surface.thesurface.network/glossary/lead-generation-social-media-marketing Lead generation through social media marketing is the use of social platforms to create attention, start relevant conversations, and capture identifiable interest. The response may occur through a native lead form, event registration, direct message, profile link, landing page, referral, or a sales conversation prompted by the content. Organic and paid activity can both contribute. Organic posts build familiarity and reveal audience language over time. Paid campaigns can reach a defined segment and test offers more quickly. Neither channel removes the need for qualification after capture. A useful social lead has enough identity, fit, intent, and consent for the next action. A follower, like, or video view may signal interest without creating a lead. A native form can create a record with little effort, yet easy completion may also increase low-intent volume. The team should match follow-up to the strength of the signal. Platform context matters. A person responding to a technical discussion expects a different conversation from someone requesting a pricing consultation. Choose platforms based on audience behavior and the type of interaction needed. Build content around real questions, proof, and points of view. Give each campaign a clear offer and destination. Preserve the post, ad, conversation, and consent context when the lead enters the CRM. Set response rules for public comments, messages, native forms, and high-intent site actions. Measure qualified conversations, accepted leads, meetings, opportunities, cost, and response time beside platform engagement. A developer tools company publishes short engineering breakdowns on LinkedIn and invites readers to a live architecture review. Registration creates a lead, while post engagement remains an audience signal. The team prioritizes registrants from target accounts who asked a deployment question. Other attendees receive the recording and a technical follow-up. Sales sees the original question before making contact, so the response continues the conversation instead of starting with a generic pitch. Social platforms control reach, audience access, and much of the reporting. Preserve first-party consent and campaign context when a person responds. Do not copy sensitive profile details into a lead record without a valid purpose. Assign ownership for public replies and direct messages, including response time and escalation. A lead can lose trust before it ever reaches a form if the conversation is ignored or moved into an irrelevant script. --- # Lead Generation vs. Demand Generation | Surface Glossary URL: https://surface.thesurface.network/glossary/lead-generation-vs-demand-generation Demand generation builds and shapes interest in a problem, category, or company among a defined market. Lead generation captures information about people or accounts that show interest so a team can qualify, route, nurture, or contact them. Demand can exist without an identified lead, and a lead can be captured before meaningful demand exists. The distinction matters because the two jobs use different signals and time horizons. A research report, podcast, event, or educational page may increase recognition among future buyers who remain anonymous. A demo form, trial signup, event registration, or content request creates an identifiable record. Treating every demand activity as a lead source can force premature capture, while treating every form fill as demand can inflate pipeline expectations. Both practices begin with an audience and a business objective. They can share content, paid distribution, events, website experiences, lifecycle communication, account selection, and measurement. One campaign may create interest among many people and capture a smaller group for follow-up. The overlap is operational: the same buyer can move through both systems, and the handoff needs consistent identity, consent, definitions, and ownership. Demand generation is concerned with the market's attention, understanding, memory, and intent. Lead generation is concerned with the moment interest becomes identifiable and actionable. Their outputs, immediate measures, and common failure modes therefore differ. Lead generation Demand generation Captures identifiable interest for a follow-up process Creates or strengthens interest among a defined audience Requires a person, account, or response that can be recorded Often includes anonymous reach and repeated exposure Measures capture, qualification, acceptance, response, meeting, and opportunity outcomes Measures audience quality, engagement, branded demand, and later commercial movement Usually starts an immediate nurture, routing, or sales decision Can work over a long buying horizon The boundary is the operational commitment created by identification. Once a person submits information, the company must decide what the signal means, what communication is permitted, who owns the response, and how quickly action should occur. Before that point, the company can still influence demand through useful material and distribution, but it has less individual context and should avoid pretending anonymous attention is a sales-ready lead. Consider a cybersecurity company entering a new vertical. A benchmark study and executive webinar teach the market about an emerging risk. Most readers and viewers remain unknown, so the team measures qualified reach, repeat engagement, branded search, and later visits. The webinar registration and consultation form create leads. Those records are enriched, checked for account fit, and routed according to intent. Attendees who requested education receive nurture; buyers asking for an assessment receive prompt sales follow-up. Problems appear when one metric is made to stand in for both jobs. Gating every useful asset may raise lead count while reducing reach and trust. Running broad awareness with no capture path can leave active buyers without a next step. Plan demand creation, demand capture, and the handoff between them as connected parts with separate success measures. --- # Lead Generation Website | Surface Glossary URL: https://surface.thesurface.network/glossary/lead-generation-web-site A lead generation website is a site designed to turn relevant visitors into identifiable prospects through forms, scheduling, chat, subscriptions, assessments, trials, or other permission-based actions. Its job includes attracting the right audience, earning trust, collecting enough context, and moving each response to a useful next step. The site is more than a collection of landing pages. Educational content, comparisons, customer stories, product information, pricing context, documentation, and calls to action work together across a longer research journey. The best conversion varies by intent. A reader may need a guide before a demo, while a high-intent visitor may want immediate scheduling. Traffic without conversion produces attention that the company cannot continue. Conversion without qualification produces a queue sales does not trust. A lead generation site therefore needs content architecture and lead operations, including data quality, scoring, routing, response, and measurement. Map entry pages by intent, give each page one clear next action, reduce unnecessary form fields, capture consent and source data, enrich only where it changes a decision, and route high-intent requests quickly. Measure the path from visit through meeting and opportunity rather than stopping at form submission. Connect a lead generation website to the complete path from audience and offer through capture, qualification, ownership, response, and sales outcome. A tactic should not be evaluated only at the first form event. Review a sample of real cases before relying on an aggregate score. The sample should include incomplete, conflicting, and high-value records because averages often hide the failures with the largest business cost. Place the documentation for a lead generation website beside the workflow or decision it affects. That keeps definitions, evidence, ownership, and later corrections available to the people who need them. A buyer enters through a comparison article, reads an implementation guide, visits pricing, and opens a demo form. The form asks only for contact information, company, and product interest. Enrichment supplies firmographics, routing matches the buyer to the relevant rep, and the confirmation page offers immediate scheduling plus a customer story. A lead generation website should make the next step feel like a continuation of the research. Generic CTAs and slow handoffs waste the trust the content already earned. --- # Lifecycle Marketing | Surface Glossary URL: https://surface.thesurface.network/glossary/lifecycle-marketing Lifecycle marketing is the practice of adapting communication and offers to a person's stage, behavior, needs, and relationship with a company. Stages may include anonymous visitor, subscriber, lead, qualified buyer, opportunity, customer, active user, renewal, expansion, lapse, and reactivation. The lifecycle is a model rather than a universal funnel. People move backward, pause, hold several roles, or interact as both user and buyer. Good lifecycle design uses stage as one signal among intent, fit, product behavior, consent, recent activity, and account context. Teams define stages and entry criteria, identify the decision or need at each stage, design messages and handoffs, and specify how records leave or re-enter a program. Marketing automation can execute the sequence, while CRM and product systems provide state. Sales and customer teams need visibility into important transitions. 1. Map the real customer journey and the moments where useful communication changes. Do not begin with the default stage names supplied by a platform. 2. Define entry, exit, suppression, and re-entry rules for each stage. Include ownership, timestamps, consent, and the behavior when required data is missing. 3. Design content and actions around the person's current question. An early subscriber may need education, while a pricing-page return or product-usage threshold may justify direct help. 4. Connect email, ads, site experiences, sales tasks, and customer messages through shared records. Prevent several systems from sending contradictory communication at the same time. 5. Measure movement and value by cohort. Review conversion, time in stage, engagement, complaints, opportunity creation, retention, expansion, and the reasons people stall or exit. Stage conversion alone is insufficient. Teams should also track time between stages, cohort behavior, suppression and opt-out rates, sales acceptance, revenue, retention, and whether messages arrive after the relevant moment. A high email click rate can coexist with poor lifecycle movement. For lifecycle marketing, build a decision brief that keeps the market boundary and evidence types visible. List the population, geography, segment, period, inclusion rules, sources, dates, method, and assumptions. Separate direct observations, participant reports, vendor claims, modeled estimates, and internal interpretation. When sources disagree, show the disagreement and explain which definition or method creates it. A later reviewer should be able to update one assumption without rebuilding the entire argument. Create a short release checklist for lifecycle marketing and assign each item to a role. Include source verification, permissions, privacy, required approvals, error visibility, downstream compatibility, and rollback. Keep the checklist close to the workflow so it changes when the workflow changes. After release, review exceptions before aggregate performance because an average can improve while a small number of high-value cases fail badly. Connect the local lifecycle marketing workflow to the decision that follows it. Documentation should show what the next operator receives and which context must survive the handoff. Before expanding lifecycle marketing, compare several outputs with the source material and with the decision made by a competent operator. Record false positives, false negatives, missing cases, and disagreements about definitions. Use that sample to update the rule, test set, documentation, or training rather than explaining every error as an isolated exception. The review should end with a named change and an owner, even when the change is to keep the current scope. For lifecycle marketing, note unresolved questions beside the approved process. Visible limitations invite review; hidden assumptions tend to survive until a customer, report, or integration exposes them under worse conditions. - Which stages represent meaningful changes in need, ownership, or action? - Which data and timestamps determine entry and exit? - Who owns a person or account when marketing, sales, and customer success overlap? - Which messages require consent, suppression, frequency limits, or human review? - How will exceptions and manual overrides return to the shared record? Lifecycle definitions are business logic. They should be documented, versioned, and understandable outside the automation tool. If a stage exists only because one workflow needs a trigger, create a separate operational field instead of changing the customer model for everyone. The common failure is static drip marketing. Everyone who downloads one asset enters the same timed sequence, even after they book a demo, become a customer, change roles, or stop engaging. The automation sends messages reliably while the relationship it describes no longer exists. Rebuild around event and state changes, add clear exits and suppressions, reconcile lifecycle fields across systems, and review stalled cohorts. Use sales and customer feedback to update the content and timing rather than optimizing subject lines alone. --- # Lifecycle Marketing Campaigns | Surface Glossary URL: https://surface.thesurface.network/glossary/lifecycle-marketing-campaigns Lifecycle marketing campaigns are coordinated programs triggered by a person's or account's stage, behavior, timing, or relationship with a company. Examples include welcome, education, trial support, abandoned action, sales follow-up, onboarding, adoption, renewal, expansion, lapse prevention, and reactivation campaigns. The campaign should respond to a meaningful state. A generic monthly email may support a broader relationship. It qualifies as a lifecycle campaign only when the message or action changes according to the recipient's context. Buyers and customers need different information at different moments. Someone researching a category may need explanation. A person who requested a demo needs timely help. A new administrator may need setup guidance. An active customer approaching renewal may need evidence of value and a clear conversation with the account team. Lifecycle campaigns make those needs operational across marketing, sales, product, and customer teams. Define the state, entry event, required data, consent, timing, exit, re-entry, suppression, owner, and goal. Map the question the person is likely to have and choose the lightest message or action that helps. Coordinate email with ads, site experiences, product prompts, sales tasks, and customer outreach so several systems do not compete. Measure movement, time, complaints, sales acceptance, product use, retention, and revenue beside message engagement. Review exceptions and stale states. A trial program begins when a qualified user creates a workspace. The first message helps the user complete one setup task. Product activity determines the next guidance. A pricing visit creates a sales alert only for target accounts without an open owner conflict. Conversion ends the trial sequence and starts onboarding. Inactive users receive one recovery path, then leave the program rather than remaining in an endless reminder loop. Keep a registry of active lifecycle campaigns, target states, messages, owners, precedence, dependencies, and sunset dates. Review overlap before launching another sequence. A new onboarding message may already exist in product, support, and customer-success systems. The portfolio view helps the company coordinate one relationship instead of optimizing several disconnected send calendars. --- # Lifecycle Marketing Process | Surface Glossary URL: https://surface.thesurface.network/glossary/lifecycle-marketing-process A lifecycle marketing process is the operating system that adapts communication and action as a person or account moves from first interest through evaluation, purchase, use, renewal, expansion, lapse, or return. It combines stage definitions, behavioral signals, consent, customer data, content, automation, human handoffs, and measurement. The lifecycle is a model. Real people pause, move backward, change roles, use several products, or belong to an account whose relationship differs from their own. The process needs rules for uncertainty and exceptions rather than assuming a clean one-way funnel. 1. **Map meaningful states.** Define stages around changes that affect the message or owner. Use buyer and customer evidence rather than importing every default stage from a platform. 2. **Set entry and exit rules.** Name the required fields, events, time windows, consent, suppression, and precedence for each state. Decide how people re-enter and what happens when systems disagree. 3. **Choose the next useful action.** Match content, email, ads, site experiences, sales tasks, onboarding, or customer outreach to the current question. Some states need information, while others need a person to respond. 4. **Coordinate systems and teams.** Keep CRM, automation, product, billing, support, and data systems synchronized enough to avoid contradictory messages. Assign owners to transitions and exception queues. 5. **Measure movement and experience.** Review conversion, time in state, engagement, complaints, sales acceptance, retention, expansion, and reasons for exit by cohort. - Whether stages apply to people, accounts, opportunities, customers, or a documented combination. - Which system owns each stage and which events can change it. - How consent, region, customer status, and active sales work suppress communication. - When automation acts, when a person approves, and where exceptions wait. - Which content answers the question associated with each state. - How the team will detect stale records and conflicting states. Publish definitions and examples where operators can find them. Record the reason and timestamp for stage changes. Test the process with existing customers, open opportunities, multiple contacts at one account, dormant leads, opt-outs, and people who return after a long gap. Review the flow after product, territory, pricing, or consent changes. Use cohort reporting so recent entrants are not compared with records that had much longer to convert. Examine quality and timing beside volume. A nurture can earn clicks while delaying a buyer who wanted direct help. Teams often turn lifecycle marketing into a collection of email sequences owned by one platform. Stages become campaign labels, sales changes records without shared rules, and customers keep receiving prospect messages. The system appears automated because messages send on time, even though the underlying relationship is wrong. A better process treats the customer state as governed data. Messages and tasks follow that state, every important transition has an owner, and exceptions remain visible. Automation handles repeatable actions while people review ambiguous or consequential changes. The result is communication that reflects the relationship the company can actually observe. Lifecycle rules need version control because one field change can alter thousands of messages and tasks. Document the proposed change, affected populations, systems, owner, test cases, release date, and rollback. Review historical records that may enter a new path unexpectedly. Communicate definition changes to sales and customer teams before activation. Maintain a campaign and rule registry with entry, exit, suppression, dependencies, and active owner. The registry should show which program wins when several triggers fire. Without precedence, a buyer can receive a trial reminder, an opportunity follow-up, and a customer announcement under conflicting assumptions. Set a sunset condition for every lifecycle program. A product feature may disappear, a segment may change, or a message may stop helping. Monitor error queues, opt-outs, complaints, manual corrections, and unexpected re-entry beside conversion. These signals show whether the process respects the relationship it is meant to represent. Sample real journeys across several weeks. Read the messages in order, inspect the site and product states, and ask sales or customer teams what they saw. A rule can pass every technical test while the combined experience feels repetitive, late, or contradictory. Journey review catches problems that isolated campaign reports cannot show. --- # Market Information | Surface Glossary URL: https://surface.thesurface.network/glossary/market-information Market information is evidence about the environment in which a business sells and competes. It can include customer needs, buying behavior, segment size, search demand, competitor products, pricing, distribution, regulation, technology, partnerships, economic conditions, and sales outcomes. Information becomes useful only when its source, date, scope, and relationship to a decision are clear. A competitor pricing page is current first-party evidence about listed price, while an analyst estimate may model total market revenue. A sales note describes one deal. Those sources should not be treated as interchangeable. Organize market information around recurring questions and decisions. Record provenance, confidence, geography, segment, time period, and source type. Keep raw evidence connected to the summary, and establish a review cadence for facts that change quickly. 1. Define the business question, such as which segment to target, how to position, what price to test, or which competitor claim requires response. 2. Choose sources suited to the fact. Use direct customer research for motivation, product documentation for features, public records for filings, and observed performance for internal outcomes. 3. Collect and label evidence consistently. Preserve dates, URLs, participant context, methodology, and whether a number is observed, estimated, or inferred. 4. Compare sources and surface contradiction. Avoid averaging unlike estimates merely to produce one clean figure. 5. Translate the evidence into an implication, action, owner, and review trigger. Retire stale information rather than letting it remain silently available. A market-information system can track freshness, priority-question coverage, source traceability, contradiction resolution, stakeholder use, and decisions supported. The number of entries or documents measures storage activity rather than intelligence quality. For market information, build a decision brief that keeps the market boundary and evidence types visible. List the population, geography, segment, period, inclusion rules, sources, dates, method, and assumptions. Separate direct observations, participant reports, vendor claims, modeled estimates, and internal interpretation. When sources disagree, show the disagreement and explain which definition or method creates it. A later reviewer should be able to update one assumption without rebuilding the entire argument. Create a short release checklist for market information and assign each item to a role. Include source verification, permissions, privacy, required approvals, error visibility, downstream compatibility, and rollback. Keep the checklist close to the workflow so it changes when the workflow changes. After release, review exceptions before aggregate performance because an average can improve while a small number of high-value cases fail badly. Connect the local market information workflow to the decision that follows it. Documentation should show what the next operator receives and which context must survive the handoff. Before expanding market information, compare several outputs with the source material and with the decision made by a competent operator. Record false positives, false negatives, missing cases, and disagreements about definitions. Use that sample to update the rule, test set, documentation, or training rather than explaining every error as an isolated exception. The review should end with a named change and an owner, even when the change is to keep the current scope. For market information, note unresolved questions beside the approved process. Visible limitations invite review; hidden assumptions tend to survive until a customer, report, or integration exposes them under worse conditions. - Which information is material enough to maintain continuously? - Which source type is appropriate for each claim? - How will estimates, participant reports, and internal interpretations be labeled? - Who can change the summary and who reviews consequential updates? - What event or date forces revalidation? The useful unit is a claim with context. A number without geography, segment, date, source, and definition can travel quickly through briefs and decks while losing the conditions that made it true. A common failure is creating a research repository with no ownership or expiration. Teams keep copying an old market estimate and competitor claim because the document looks authoritative. Later plans inherit stale assumptions without realizing it. Add source and review fields, prioritize high-impact claims, and archive entries that cannot be revalidated. Build current decision briefs from the evidence rather than asking stakeholders to search a large undifferentiated library. --- # Market Research and Intelligence | Surface Glossary URL: https://surface.thesurface.network/glossary/market-research-and-intelligence Market research and intelligence is an operating practice that combines focused studies with continued collection of market evidence. The research side investigates a defined uncertainty through a planned method. The intelligence side maintains awareness of customers, competitors, categories, channels, regulation, and internal commercial signals between studies. Together they create a dated evidence base for market decisions. Companies often scatter this work across product marketing, strategy, sales, customer success, finance, and research teams. Each group sees part of the market. Sales hears live objections, finance sees pricing and retention, product sees usage, and external sources show category or competitor movement. An intelligence practice connects those perspectives without pretending they use the same unit or level of certainty. A stand-alone study can age quietly, while a monitoring program can generate constant updates without depth. Combining the practices gives strategic findings an expiration and gives recurring signals a route into deeper inquiry. It also reduces duplicate research when teams can search prior questions, source notes, samples, and decisions before commissioning new work. Build the evidence base around recurring decisions rather than around a feed of everything available. For each source, record provenance, date, population, method, market boundary, confidence, and permitted use. Use a regular review to identify changes that cross a threshold or conflict with existing beliefs. Commission research when the decision needs explanation, estimation, or validation beyond the monitored signal. Assign owners for source maintenance, analysis, and business decisions. Keep raw evidence accessible beside summaries. Tag findings by audience, competitor, market, question, and review date, while retaining contradictory cases. When a decision uses several sources, state how they differ and why the combined interpretation is reasonable. Retire alerts that do not lead to action and schedule review for claims likely to change. A cloud infrastructure company maintains a quarterly view of win-loss reasons, competitor releases, search demand, public hiring, and customer interviews. A sudden rise in security objections appears in both lost deals and support conversations. Rather than rewriting positioning immediately, the team studies the affected segment and finds that one procurement requirement changed. The intelligence watchlist then tracks that requirement by region. The combined practice turns isolated studies and passing signals into evidence that can be reviewed, challenged, and reused. --- # Market Research and Product Development | Surface Glossary URL: https://surface.thesurface.network/glossary/market-research-and-product-development Market research and product development work together when market evidence enters the product decisions that can still change. Research explains who experiences the problem, how they handle it today, what they value, how they buy, and which alternatives already compete. Product work contributes feasibility, usability, technical constraints, and evidence from actual use. The relationship is strongest when both sides share a decision calendar. A study completed after scope is locked can explain the market without influencing the product. An opportunity brief can combine market size, buyer roles, current behavior, and alternatives before a product team accepts a problem. Discovery work then tests the problem boundary. Concept reviews bring buyer comprehension and commercial context into solution choices. Release planning uses segment, price, channel, and proof research. After launch, acquisition, activation, retention, support, and win-loss evidence return to the roadmap. Each gate should state which assumption is being tested and what result would change the investment. The standard becomes stronger as commitment grows. Researchers own method, sample, evidence quality, and interpretation limits. Product teams own the product decision and technical tradeoffs. Marketing and sales contribute category, buying, message, and deal evidence. Customer teams contribute implementation and realized outcomes. One person may cover several roles in a small company, but the evidence should remain distinguishable. Store the decision with the research. Future teams need to know which recommendation was accepted, which risk remained, and what later product behavior showed. A platform team considers adding approval automation. Market interviews show that the economic buyer worries about auditability, while users want fewer manual handoffs. Product analytics shows where current approvals stall. Engineering identifies a reliable event trail but limited support for complex exceptions. The first release focuses on transparent routing and an audit record. Research, use data, and feasibility shape the same boundary instead of arriving as separate presentations. Product evidence often disagrees. Buyers may praise a concept while pilots show low use. Current customers may request a feature that new segments do not value. Record the population and decision represented by each source. Give greater weight to behavior when the same choice is observed under realistic conditions, but investigate why reported intent differs. The disagreement may reveal implementation friction, weak urgency, or a buying role whose needs the test ignored. --- # Market Research for Product Development | Surface Glossary URL: https://surface.thesurface.network/glossary/market-research-for-product-development Market research for product development is a set of studies designed to reduce uncertainty around a proposed product. It examines the target market, buyer and user roles, unmet problem, current alternatives, willingness to change, expected value, price context, distribution, and adoption barriers. The work complements product discovery, usability research, analytics, and technical feasibility. The research should correspond to a pending product decision. A team may need to choose a segment, test a concept, prioritize an outcome, set packaging, or prepare a launch. Problem interviews and observation reveal current work and consequences. Market sizing estimates the opportunity under explicit boundaries. Competitor and substitute research shows existing choices. Concept tests examine comprehension and appeal. Conjoint, pricing, or tradeoff studies can test preference under constraints. Prototype and pilot programs add behavioral evidence before a full launch. Each method has limits. Stated purchase intent is weaker than a paid commitment, and a successful usability task does not prove a market exists. Name the decision, target population, product stage, and evidence threshold. Recruit users, buyers, administrators, and former customers when their roles differ. Use neutral concepts and realistic tradeoffs. Record assumptions and competing explanations. Compare findings with sales, support, product use, and market data rather than asking one study to settle everything. Set a date or condition for review because demand and alternatives can change during a long development cycle. A logistics company considers a forecasting module. Interviews identify costly manual reconciliation, while market analysis shows a crowded category. A concept test finds stronger interest among companies with several warehouses. A prototype proves useful only when it connects to existing planning data. The team narrows the first release to multi-site operators and makes integration readiness part of qualification. Research changes the segment and product boundary before engineering commits to a broad build. Market research can establish context and reduce uncertainty, yet product judgment still weighs technical feasibility, company capability, strategic fit, ethics, and the cost of delay. Record where the recommendation depends on those internal choices. If the team proceeds against the strongest market evidence, state the reason and the risk. This keeps research useful without pretending it owns the whole product decision. --- # Market Research Methods | Surface Glossary URL: https://surface.thesurface.network/glossary/market-research-methods Market research methods are the techniques teams use to learn about a market, audience, competitor set, product problem, or buying decision. They include primary methods such as interviews, surveys, observation, experiments, and customer panels, plus secondary methods such as industry reports, public filings, search data, review analysis, and existing company records. Methods also divide into qualitative and quantitative work. Qualitative research explains language, motivation, sequence, and context. Quantitative research estimates prevalence, size, difference, or change. A good plan often uses both, because a dashboard can show that a segment converts poorly while interviews reveal why the offer feels risky. Choosing the method changes the claim the team can make. Ten thoughtful interviews can identify recurring objections but cannot establish a population percentage. A large survey can estimate that percentage, yet its result may be meaningless if the sample excludes the people who actually make the purchase. Begin with the decision, then choose the evidence capable of changing it. Define the population, sampling approach, question design, analysis method, and limits before collecting data. Combine sources when they answer different parts of the question, and preserve enough documentation for another person to understand where each conclusion came from. A useful application of market research methods separates observed facts, participant reports, modeled estimates, and internal interpretation. Those forms of evidence can inform the same decision without being treated as equivalent. Review a sample of real cases before relying on an aggregate score. The sample should include incomplete, conflicting, and high-value records because averages often hide the failures with the largest business cost. Place the documentation for market research methods beside the workflow or decision it affects. That keeps definitions, evidence, ownership, and later corrections available to the people who need them. A software company considers entering healthcare. It reviews public market reports and competitor positioning, interviews twelve operations leaders, surveys 300 qualified buyers, and tests two landing-page messages with a controlled paid audience. The sources do not collapse into one score. Each answers a different question about size, need, language, and response. Research quality depends less on the fashionable method than on fit between the question and the evidence. State what the method can support, what it cannot support, and which business decision follows from the result. --- # Market Research Questions | Surface Glossary URL: https://surface.thesurface.network/glossary/market-research-questions Market research questions are the questions a study is designed to answer about a market, buyer, behavior, alternative, demand pattern, or business choice. They guide the research design and are broader than the exact wording used in an interview guide or questionnaire. One research question may require several sources and methods. A question such as "Why do qualified buyers abandon the evaluation?" could draw on interviews, sales notes, product behavior, procurement evidence, and competitor research. Asking a survey respondent the same sentence would probably produce an oversimplified answer. Research questions define the uncertainty; instruments collect particular evidence about it. Weak questions produce large collections of interesting facts that never change a decision. Questions framed around a preferred solution also bias the study before collection begins. A useful question states the population, behavior or condition, context, and relationship the team needs to understand. Begin with the decision and list what must be true for each option to work. Turn the most uncertain and consequential assumptions into questions. Decide whether each question needs description, explanation, comparison, estimation, or causal evidence. Then choose methods, sources, samples, and analytical rules capable of supporting that type of answer. Common areas include market size and change, customer segments, problem frequency and cost, current behavior, buying roles, alternatives, willingness, channels, constraints, and competitive response. Phrase questions neutrally and include evidence that could challenge the current plan. Assign each question an owner and an action it can influence. A product team asks, "Which implementation condition predicts failure for midmarket customers in the first 90 days?" It combines onboarding records, support cases, churn interviews, and implementation-manager notes. The answer points to missing data access rather than training, so the company changes qualification and prelaunch requirements. Market research questions are useful when the answer can alter a real choice and the method can support the claim. Retire questions once the decision no longer depends on them, and write new ones when the market changes. --- # Market Research Questions for Startups | Surface Glossary URL: https://surface.thesurface.network/glossary/market-research-questions-for-startups Market research questions for startups are decision questions used to reduce uncertainty about a problem, customer, market, product, and route to growth. Strong questions investigate current behavior and constraints: who experiences the problem, what triggers it, how people handle it now, what the workaround costs, who approves change, and what would prevent adoption. A research question is broader than an interview or survey item. "Why do qualified teams keep the current process?" may require interviews, lost-deal evidence, product observation, and market data. Asking prospects whether they like a proposed product produces easy encouragement and weak evidence about future behavior. Startups face many unknowns and little time. Research should concentrate on assumptions capable of killing or reshaping the plan. Questions that collect compliments or broad market facts can consume weeks while leaving problem urgency, buyer authority, willingness to switch, and acquisition cost unresolved. List the current assumptions about customer, problem, alternative, value, buying process, channel, and constraint. Rank them by consequence and uncertainty. Convert the highest-risk assumptions into questions about past or present evidence. Match each question to a source, define the sample, and record what answer would change the product or market decision. Useful startup questions include: What happened the last time this problem occurred? Which people and systems were involved? What has the organization already tried? Who owns the budget and risk? Which alternative would a buyer remove or reduce? What evidence creates trust? Where does the buying process stall? Which customer should the company decline? A startup building an AI support tool assumes midmarket teams need faster ticket triage. Interviews show triage speed is acceptable; the expensive problem is reviewing AI-generated answers for policy errors. The founders change the first product and message toward controlled review, then test willingness with design partners who already pay people to do that work. The best startup research question can change the plan. Questions designed only to validate the idea rarely do. --- # Market Research Technology | Surface Glossary URL: https://surface.thesurface.network/glossary/market-research-technology Market research technology is the software and technical infrastructure used to plan studies, recruit participants, collect evidence, analyze results, manage research knowledge, and share findings. The category includes survey platforms, interview and usability tools, panel marketplaces, social listening products, analytics systems, transcription, qualitative coding, experimentation, data visualization, repositories, and research agents. The technology should serve a research design. A fast platform cannot repair a biased sample, a leading question, an unclear decision, or a measure that does not represent the concept being studied. Recruitment tools find and screen participants. Collection tools capture responses, behavior, recordings, or observations. Analysis tools clean, code, compare, model, and visualize evidence. Repositories store source material, decisions, findings, and reuse rules. Workflow products coordinate consent, incentives, review, privacy, and access. AI can assist with transcription, classification, clustering, search, and draft synthesis. Its output needs traceability to the source and a review path for ambiguous or consequential interpretation. Begin with the decisions and study types the team actually runs. Review sampling controls, identity and duplicate handling, accessibility, language support, consent, data retention, export, integrations, audit history, collaboration, and the ability to preserve raw evidence. Test analysis against a known sample before relying on automation. Account for operating cost as well as subscription price. Manual cleanup, poor exports, inaccessible recordings, and weak governance can make a cheap tool expensive. A product team runs interviews, concept tests, and quarterly surveys. It chooses one recruitment provider, a recording tool with consent controls, a survey platform, and a repository that links clips and findings to product decisions. An AI layer suggests themes but never removes the underlying transcript. Researchers review every theme, record contradictory evidence, and show product managers the source behind the conclusion. Technology is most useful when it shortens repeatable work while preserving access to evidence. It can schedule sessions, validate responses, transcribe interviews, calculate measures, surface source passages, and maintain a research repository. Keep human review where context or consequence is high. A model-generated theme should link back to the participants and quotations that support it, including evidence that does not fit the theme. --- # Market Share Analysis | Surface Glossary URL: https://surface.thesurface.network/glossary/market-share-analysis Market share analysis estimates a company's portion of a defined market and examines why that portion changes. The share may use revenue, units, customers, transactions, seats, or usage, provided the company figure and total market figure use the same boundary, period, and unit. The calculation is simple; the market definition rarely is. Depending on the measure, a company may gain revenue share while losing customer share, lead one geographic segment while remaining small globally, or appear stronger after a market estimate excludes an adjacent category. Analysis makes those choices visible and connects the percentage to price, volume, segment mix, competitors, and market growth. Market share (%) = Company value within the defined market / Total value of the same market x 100 The numerator is the company's comparable revenue, units, customers, or usage inside the market boundary. The denominator is the corresponding total for all providers in that same market. Both should use the same geography, customer segment, product scope, currency treatment, and observation period. Analysts may calculate relative market share by dividing a company's share by the share of the largest competitor. They may also compare share by segment or use proxy measures such as search interest when direct sales data is unavailable. Proxies should keep their own labels because attention share and revenue share answer different questions. Rising share can come from faster unit growth, higher prices, acquisition, competitor decline, or a narrower market estimate. Compare share with total market growth and the company's underlying inputs. Gaining one point in a contracting market describes a different position from gaining one point while the category expands quickly. Private-company revenue, bundled products, channel inventory, currency movement, and overlapping categories create uncertainty. Market share also says little by itself about profit, retention, customer satisfaction, or future advantage. Use a range when the denominator is modeled, and test how the result changes under alternate boundaries. Store the numerator, denominator, unit, sources, dates, exclusions, assumptions, and calculation version beside the reported percentage. Keep the market definition in plain language. Later analysts should be able to replace one source or extend the period without reconstructing the method from a presentation. Consider a company earning $36 million from compliance software sold to US regional banks during 2026. Researchers estimate the matching market at $540 million to $600 million. Revenue share is therefore 6.0 to 6.7 percent. If a second estimate includes compliance services and software sold to all financial institutions, it cannot be used as the denominator for the same claim. Market share analysis is defensible when the percentage remains attached to a dated market definition, comparable inputs, and an explanation of what moved. --- # Market Share Research | Surface Glossary URL: https://surface.thesurface.network/glossary/market-share-research Market share research estimates how much of a defined market belongs to a company, product, or brand during a stated period. Share may be based on revenue, units, customers, seats, transactions, usage, search demand, or another measure. The denominator must match the numerator and the market boundary. Market share is not one universal fact. A company can have high customer share and lower revenue share, or strong share in one segment and little global presence. Private-market research often relies on estimates, so the method and range matter as much as the reported percentage. For revenue share, the common formula is: `Market share = Company revenue in the defined market / Total revenue in the defined market x 100` Company revenue should include only the products, geography, customer segment, and period included in the market definition. Total market revenue must use the same boundary and currency treatment. Unit share replaces revenue with comparable units, while customer share requires a consistent definition of active customer. Researchers may triangulate public filings, vendor disclosures, channel data, customer surveys, analyst estimates, web or app usage, and modeled private-company revenue. Proxy measures such as search share or review share can describe visibility or activity, but they should not be labeled revenue share without evidence. Share can indicate position, concentration, and change, but it does not automatically show profitability, customer satisfaction, or competitive advantage. A company may gain share through heavy discounting. A niche provider may hold modest category share and strong economics within a narrow segment. State uncertainty and sensitivity to the market definition. Acquisitions, currency changes, channel inventory, multi-product bundles, and overlapping categories can distort comparisons. Use ranges when private-company inputs are modeled, and keep the estimate dated. Store the source values and calculation with the reported number. A reviewer should be able to see the unit, time window, cohort, exclusions, and uncertainty without searching a separate methodology deck. Recalculate market share when those definitions change. Record the calculation version and review date so later comparisons use the same method or explain the change. A company sells $42 million of workflow software in North America. Researchers estimate the matching market at $600 million to $700 million for the same year and customer segment. Revenue share is therefore about 6.0 to 7.0 percent. If the broader estimate includes adjacent project-management products, the denominator no longer matches the company's revenue definition. A defensible share estimate begins with the market boundary and comparable units. Publish the sources, assumptions, range, and proxy labels so decision makers know what changed when the percentage moves. --- # Market Size | Surface Glossary URL: https://surface.thesurface.network/glossary/market-size Market size is an estimate of the total economic opportunity within a defined market, geography, customer group, product boundary, and time period. It may be expressed as annual revenue, units purchased, number of potential customers, seats, transactions, or another measure tied to how the market buys. Market size does not state how much one company can win. Teams often distinguish total addressable market, serviceable available market, and serviceable obtainable market. Those labels are useful only when the assumptions and constraints behind each layer are explicit. A common bottom-up formula is: `Market size = Number of potential customers x Average annual spend per customer` The number of potential customers should match the defined segment, geography, and eligibility criteria. Average annual spend should reflect the relevant product or category, not the company's desired contract value. Unit-based models may instead multiply annual units by average price. Usage products may estimate customers, eligible users, activity, and price per action. A top-down estimate begins with a broader published market and applies defensible segment shares. A bottom-up estimate counts buyers or usage directly. A value-theory estimate begins with the economic value created and the portion a supplier might capture. Serious work compares methods and explains why they differ. There is no universally good market size. A smaller concentrated market may support efficient sales and strong pricing, while a large market may contain many buyers the company cannot reach or serve. Growth rate, fragmentation, switching behavior, regulation, channel access, and sales economics change the practical opportunity. Report a range rather than false precision when inputs are uncertain. Separate current spend from latent need and avoid counting the same revenue across overlapping segments. The estimate should state its date because category boundaries, prices, and buyer counts change. Report market size with a comparison that uses the same definition. Trend, segment, channel, or scenario comparisons become misleading when the numerator, denominator, geography, or observation window changes between periods. Record the calculation version and review date so later comparisons use the same method or explain the change. A company studies compliance software for 18,000 regulated midsize businesses in its target countries. Research suggests 60 percent fit the required technology environment, leaving 10,800 eligible accounts. Comparable annual spend ranges from $18,000 to $30,000. The estimated serviceable market is therefore $194.4 million to $324 million per year before applying sales reach or expected share. The useful output is the model, not the headline number. Decision makers should be able to change customer count, eligibility, price, and adoption assumptions and see which one drives the result. --- # Market Sizing Research | Surface Glossary URL: https://surface.thesurface.network/glossary/market-sizing-research Market sizing research estimates the scale of an economic opportunity within explicit boundaries. The result may be potential buyers, users, units, transactions, annual spend, or revenue. A useful estimate states the product or need, segment, geography, eligibility, time period, pricing basis, adoption assumption, and whether the number represents total, serviceable, or realistically obtainable opportunity. Market size is a model, not a fact found in one report. Different methods produce different results because they use different boundaries and assumptions. Top-down research starts with a broad published market and applies segment shares. Bottom-up research counts eligible buyers or usage and multiplies by realistic volume and price. Value-based sizing estimates the economic value created and the portion a supplier could capture. Supply-side work adds vendor revenue or units, while demand-side work estimates buyer spending. Strong studies compare methods and explain why their ranges differ. Define the market before collecting numbers. Use current sources, document every transformation, and avoid combining estimates with incompatible definitions. Separate current spend from latent demand. Check for double counting across segments, channels, and product bundles. Use ranges when inputs are uncertain and test which assumptions change the conclusion most. Review the model with product, finance, sales, and market experts who understand practical eligibility and reach. A company studies maintenance software for 24,000 industrial sites. Research shows that 40 percent use equipment and systems the product supports, leaving 9,600 eligible sites. Comparable annual spend ranges from $12,000 to $22,000. The serviceable market is estimated at $115.2 million to $211.2 million before accounting for regions the company cannot sell into, existing contracts, implementation capacity, or expected share. The range is more useful than one inflated headline. Show which inputs drive the estimate. Change buyer count, eligibility, usage, price, adoption, and time period across plausible ranges. A model whose conclusion changes after a small assumption shift deserves more research or a staged investment. Keep the base, low, and high cases tied to evidence rather than choosing percentages that create a comfortable spread. Update the model as real sales and use data arrive. --- # Market Study | Surface Glossary URL: https://surface.thesurface.network/glossary/market-study A market study is a structured investigation of a defined market for a business decision. It may examine market size and growth, customer segments, needs, buying behavior, competitors and substitutes, routes to market, pricing, regulation, technology, supply, and other forces that affect entry, investment, positioning, or planning. The scope depends on the decision. Companies considering market entry need evidence about reachable demand, barriers, competitive response, and their own right to win. Teams revising a product position may need a narrower study of buyer language, alternatives, and category structure. Calling both projects market studies does not make their evidence interchangeable. Write the market definition, decision, and uncertainty before collecting sources. Build the study around a small number of claims that can change the action. Use primary and secondary research according to the question, show disagreement between sources, and preserve assumptions behind modeled estimates. 1. Define the decision, market boundary, geography, customer, product scope, time period, and the conditions under which the recommendation could change. 2. Create an evidence plan. Assign methods and sources to questions about demand, buyers, segments, competitors, economics, channels, constraints, and trends. 3. Collect and normalize evidence. Record dates, definitions, units, sample frames, source incentives, transformations, and missing information. 4. Analyze scenarios rather than forcing one forecast. Test alternate market sizes, adoption rates, price assumptions, competitive responses, and execution limits. 5. Translate findings into a decision. State the recommendation, confidence, risks, leading indicators, owner, and next review point. Judge a market study by source traceability, boundary consistency, decision relevance, sensitivity to assumptions, and whether later evidence confirms its leading indicators. Page count and number of cited sources are weak substitutes. Track which assumptions drive the recommendation and how quickly they can become stale. Maintain a source register that distinguishes public facts, vendor claims, participant reports, internal data, analyst estimates, and the team's interpretation. Record when each source was accessed and which study claim it supports. For modeled numbers, keep the calculation and inputs available so a reviewer can replace one assumption without rebuilding the entire document. Invite subject experts to challenge the boundary and evidence before the conclusion hardens. Sales may know which alternatives appear in deals; product may know implementation limits; finance may challenge market economics; legal may identify constraints. Their input should remain attributable and should not silently override external evidence. - Which specific business choice will the market study inform? - How narrowly must the market be defined for that choice? - Which claims need direct buyer or customer evidence? - Which assumptions create the greatest change in the recommendation? - Who owns updates when the market, product, or source data changes? Market studies can conclude that the evidence does not support action yet. Decide whether uncertainty calls for a smaller experiment, additional research, a reversible entry, or no investment. Treating every study as a case for expansion turns research into internal sales material. Assembling a large deck from reports that use different market definitions is a common failure. Revenue for software, services, and adjacent categories is combined into one confident total, then a broad growth rate is applied to a niche segment. Competitor logos and trend slides add volume while the buyer and channel evidence remain thin. Rebuild the market boundary and trace every material figure to a matching definition. Remove evidence that cannot support the claim, use ranges for modeled inputs, and narrow the recommendation. If the remaining uncertainty is actionable, design a market test with explicit success and stopping conditions. The market test should target the assumption with the greatest effect on the decision. It might measure qualified response in one segment, procurement progress, implementation effort, or willingness to pay under a real offer. Record the audience, investment, time window, and threshold in advance. Small tests should reduce a named uncertainty instead of becoming improvised launches with no interpretable outcome. Preserve negative results and participant context, since both can prevent a later team from repeating the same unsupported bet. Date the resulting decision. --- # Marketing and Sales Collaboration | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-and-sales-collaboration Marketing and sales collaboration is the ongoing coordination of audience strategy, campaigns, buyer signals, qualification, handoffs, follow-up, enablement, and revenue feedback. It is more than a recurring meeting. The teams need shared definitions, visible work, usable evidence, and clear decisions about who acts when a buyer changes state. Collaboration appears in account selection, campaign planning, content review, lead routing, opportunity support, win-loss analysis, and forecasting. It works best when both teams can see how their choices affect the buyer and the next operator in the process. Marketing sees patterns across audiences, channels, and content. Sales hears how individual buyers describe urgency, alternatives, objections, and internal approval. When those perspectives stay separate, marketing can generate interest that sales does not value, while sales can repeat field lessons without changing the campaigns that created the conversation. Shared work turns feedback into an operating input. The teams can refine qualification, revise positioning, close content gaps, improve follow-up, and identify segments whose activity looks strong but rarely converts. Define the customer stages, acceptance criteria, routing rules, response expectations, and feedback fields together. Use a small set of recurring forums with distinct jobs. A weekly review might handle active campaign and lead issues, while a monthly review examines segment performance, opportunity themes, and changes to the plan. Record decisions in the systems people already use. Measure both handoff quality and business outcomes. Meeting attendance alone does not show collaboration. A company launches a campaign for finance leaders. Sales reports that most responses come from analysts researching on behalf of a buying group. Marketing adds content that helps analysts build the internal case, while sales changes its first response to ask about stakeholders and timing. The team also updates scoring so analyst engagement at target accounts remains visible without being mistaken for executive intent. Review collaboration through decisions and outcomes. Useful evidence includes accepted handoffs, response time, opportunity feedback, recurring objections, content use, segment conversion, and the number of issues resolved at the source. Keep a short decision log with an owner and due date. This prevents the same disagreement about stages, lead quality, or campaign fit from returning in every meeting. --- # Marketing and Sales Plan | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-and-sales-plan A marketing and sales plan is a shared operating plan for creating demand, converting buyer interest, and producing revenue within a defined period. It connects target segments, positioning, campaigns, channels, capacity, qualification, routing, sales plays, content, service levels, targets, budget, and review cadence. The plan should show how marketing activity reaches sales action and how sales outcomes return to marketing decisions. Separate departmental plans can still exist, but their assumptions need to reconcile at the handoff and in the revenue model. Define the market, audience, offer, sales motion, buying process, and expected sources of growth. State the objectives and the measures used for each stage. Map campaigns and programs to sales plays, territories, account lists, or product priorities. Include volume, conversion, timing, capacity, cost, and ownership assumptions. Record dependencies such as product launches, customer proof, data readiness, hiring, events, or partner commitments. Show what the team will stop or deprioritize so the plan remains credible. Build from a shared funnel or account model with explicit definitions. Review leading signals weekly and commercial outcomes at a cadence suited to the sales cycle. When results differ from plan, isolate the assumption that changed. The issue may be audience reach, lead quality, response time, sales capacity, win rate, price, or deal timing. Update decisions and forecasts without rewriting history. Preserve the original plan for comparison and note why the current view changed. A company targets 120 enterprise accounts in two industries. Marketing plans research, executive content, paid distribution, and small events around three account problems. Sales assigns account owners, maps buying groups, and commits to follow-up rules. The joint model estimates engagement, meetings, opportunities, value, win rate, and cycle length. Monthly reviews compare actual movement with each assumption and redirect effort toward the segment producing qualified conversations. The plan should identify the owner, baseline, assumptions, resource limits, stage definitions, campaign and sales calendar, decision cadence, and conditions for revision. Include the source behind major volume and conversion assumptions. Show ranges when uncertainty is material. If one team changes a definition or target, update the connected capacity and revenue implications so the shared model does not split into two versions. --- # Marketing Automation Architecture | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-automation-architecture Marketing automation architecture is the design of the systems and data flows that make automated marketing work possible. It shows where identities and events originate, which platforms store customer state, how triggers and rules are evaluated, what actions run, and where results return for reporting or follow-up. The architecture may include website forms, product events, CRM, a marketing automation platform, customer data infrastructure, enrichment, advertising, email, messaging, scheduling, consent services, a warehouse, analytics, and human review queues. A workflow can look simple in a campaign builder while depending on several systems. A page event may need identity resolution, consent, account matching, lifecycle context, ownership, and suppression before it can safely trigger a message. If those dependencies stay implicit, teams struggle to explain duplicate sends, stale stages, missing leads, or conflicting reports. Architecture makes boundaries and failure points visible before more automation is added. Map systems, objects, identifiers, fields, events, integration direction, timing, and systems of record. Show trigger evaluation, decision rules, actions, retries, alerts, approvals, and exception queues. Document access, consent, retention, change control, and observability. Mark batch and real-time paths accurately. Design around a few critical journeys first. Test record creation, update, merge, deletion, opt-out, ownership conflict, integration delay, and re-entry. Keep version history when rules or mappings change. A demo request enters through a web form. The architecture validates the email, checks consent, matches the account, queries existing CRM ownership, enriches missing firmographics, applies qualification rules, and routes the request. A successful assignment creates a sales task and stops prospect nurture. A conflict enters an operator queue with the original values and each rule result. Reporting receives timestamps for capture, validation, assignment, first response, meeting, and opportunity creation. Walk through important records from source to outcome with the operators who maintain each boundary. Ask what happens when the record is late, duplicated, incomplete, deleted, opted out, already owned, or attached to an active opportunity. Compare documented flow with logs and actual system behavior. Review the map after vendor, API, field, consent, and lifecycle changes. An architecture diagram becomes stale when it is treated as a launch artifact. --- # Marketing Automation Campaigns | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-automation-campaigns Marketing automation campaigns are repeatable programs executed through a marketing automation system using customer or account data, events, schedules, and workflow rules. Common examples include welcome, education, event follow-up, trial activation, lead nurture, re-engagement, renewal support, and customer expansion programs. The campaign is larger than the email sequence. It includes eligibility, audience state, content, timing, channels, ownership, suppression, exit, re-entry, sales or customer handoff, measurement, and the records each action may change. Campaigns can create tasks or update audiences even when they send no message. Automation campaigns make consistent response possible across a large audience and long buying cycle. They also collide easily. One person can qualify for a nurture, an event follow-up, and a sales sequence at once. Without shared lifecycle and frequency rules, each campaign behaves correctly in isolation and the customer receives a confused experience. Design campaigns around a customer decision or relationship state. Define the trigger, eligibility, exclusions, content, action, owner, delay, exit, re-entry, error behavior, and success measure. Keep permanent customer state separate from temporary campaign status. Test against open opportunities, customers, unsubscribed contacts, duplicates, missing owners, and late events. Manage campaigns as a portfolio. Establish priority and suppression rules across programs, document who can alter live logic, and review exceptions beside conversion. Retire old campaigns deliberately and remove dependent audiences or tasks. Use sales and customer evidence to update the message and timing when the intended movement does not occur. In one trial program, communication changes according to product use. New accounts receive setup guidance; activated accounts skip beginner content; stalled high-fit accounts create a customer-success task; accounts with an open sales conversation suppress promotional email. Every path exits when the trial ends, a subscription starts, or consent changes. Marketing automation campaigns should respond to the relationship as it exists now, not continue because a contact entered a sequence weeks ago. The campaign record should make that current state and every exit visible to its owner. --- # Marketing Automation for SaaS | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-automation-for-saas Marketing automation for SaaS uses software and documented rules to coordinate communication, data updates, and team actions around a subscription customer's lifecycle. Workflows may respond to content engagement, trial activity, product usage, account fit, renewal timing, or expansion signals. The goal is consistent treatment of people and accounts when a meaningful event occurs. Subscription businesses have recurring customer states rather than one final purchase. People may move through education, evaluation, activation, adoption, renewal, and expansion, sometimes with several colleagues involved. Marketing automation connects those states to appropriate messages and operational handoffs while preserving a record of what happened. Poorly designed automation creates friction at sensitive moments. Trial users may receive basic nurture after becoming active, an open opportunity may get a discount intended for cold leads, or a customer may be routed back to sales as a new prospect. Those errors come from stale lifecycle definitions, delayed product events, conflicting systems, or missing exit rules. Start with a small number of customer states that sales, marketing, success, and product can recognize. Name the system that controls each state, the events allowed to change it, and the action each team owns. Separate permanent facts, such as account identity, from temporary campaign status. Add suppression, re-entry, timeout, and error behavior before activating a workflow. Useful programs include trial onboarding, abandoned signup follow-up, education based on role, sales alerts for high-fit product activity, renewal preparation, and outreach when adoption falls. Choose signals that have an established relationship to the desired action. Test each workflow with customers, prospects, employees, duplicate contacts, missing owners, and late events. Review message volume across programs because each workflow can appear reasonable in isolation while the combined experience becomes excessive. A B2B analytics company starts a 14-day trial sequence. Product events record connection of a data source and completion of the first dashboard. Users who complete both receive advanced guidance; users who stall receive setup help. Enterprise accounts with repeated activity create a sales task, while current customers and active opportunities are excluded. The team compares activation and qualified meetings with a holdout group. SaaS automation works when lifecycle states, product signals, ownership, and exits are explicit enough to survive real customer behavior. --- # Marketing Automation for Startups | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-automation-for-startups Marketing automation for startups uses simple software rules to handle repeatable customer and team actions while the company is still learning its market. Early workflows often cover lead capture, meeting follow-up, basic nurture, trial or onboarding communication, and record updates. The purpose is dependable execution with a small team, not an elaborate stack. Startups have little historical data and their buyer journey changes often. A workflow based on last quarter's assumptions can become wrong after a pricing change, new segment, or founder-led sales lesson. Small contact volumes also make complex scores unstable. Operators need automation that can be inspected, edited, and retired quickly. Useful automation protects response time and prevents routine work from disappearing between roles. Excess automation creates another system to maintain and can make the team sound disconnected from early customers. A startup learns through direct conversations, so software should preserve those conversations and remove clerical delay rather than screen every person through a rigid model. Choose one painful workflow with a clear trigger and owner. Define the few lifecycle states everyone uses, keep the CRM as the authority for core account and opportunity fields, and document what other tools may write. Prefer observable rules, such as form completion or trial setup, over a complicated score assembled from weak signals. Add a manual review path for uncertain cases. Begin with confirmation, routing, reminders, and data capture around high-intent actions. Add nurture only when the team understands the questions that recur. Later, connect product events, customer states, and segment-specific programs as volume justifies them. Review every active workflow after changes to pricing, product, audience, sales coverage, or consent policy. Track saved manual time and customer outcomes together. A six-person software startup receives demo requests through two forms. It creates one workflow that validates required fields, checks existing ownership, posts the request to a shared queue, sends a useful confirmation, and alerts the founder if no one accepts it within 15 minutes. The team delays lead scoring until it has enough won and lost deals to study signal quality. Startup automation should make a known process reliable while leaving the company close enough to customers to keep learning. --- # Marketing Automation Goals | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-automation-goals Marketing automation goals are the outcomes a team expects automated rules, messages, and handoffs to improve. Useful goals may include faster response to high-intent inquiries, more relevant lifecycle communication, fewer manual campaign tasks, cleaner customer records, or better visibility into movement from interest to revenue. A feature such as lead scoring is a means. The goal explains what should change after the score exists. Teams set these goals before choosing workflows or platforms. Without them, automation programs tend to measure sends, tasks completed, or records processed while leaving the buyer experience and commercial result unclear. A clear goal determines the trigger, audience, timing, owner, success measure, and acceptable risk for a workflow. The goal also reveals where automation should stop. A low-risk reminder can run automatically, while an account reassignment or consent decision may require validation or human review. Goals give marketing, sales, RevOps, and customer teams a shared basis for evaluating the system. They can ask whether response time fell, whether qualified buyers advanced, whether messages arrived in the right context, and whether exceptions created extra work elsewhere. Start with a specific operating problem and its baseline. Name the affected audience, current delay or error, expected behavior, metric, and review window. Pair an efficiency measure with a quality or customer measure so speed does not hide damage. For example, track both routing time and the share of assignments that sales accepts without correction. Limit the first program to a small number of outcomes. Document the source systems, owner, suppression rules, and condition that would pause or revise the workflow. A B2B software company finds that demo requests wait six hours for assignment. Its goal is to route complete, qualified requests within five minutes while keeping incorrect ownership below 2 percent. The workflow validates the account, checks territory and existing ownership, creates the CRM task, and alerts an operator when the rules conflict. The company reviews speed, correction rate, contact rate, and meetings held after thirty days. --- # History of Marketing Automation | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-automation-history ## What is the history of marketing automation? The history of marketing automation is the shift from database-driven campaign execution toward connected systems that respond to customer state and behavior. Early programs used customer lists, segmentation, direct mail, and batch email to reach groups more consistently. Web analytics, forms, CRM integration, and email platforms later made it possible to capture digital behavior and coordinate follow-up. As B2B marketing adopted lead nurturing and scoring, automation platforms began managing campaigns across longer buying cycles. The category expanded again as customer data, advertising, product events, messaging, scheduling, and revenue reporting entered the same workflows. The first wave emphasized scale and repeatable outbound communication. The next connected campaigns to identifiable web activity and sales records. Lifecycle programs then extended automation beyond acquisition into onboarding, retention, expansion, and reactivation. Modern systems combine rules with models or agents that classify, recommend, generate, and act under defined controls. Each stage added capability and dependency. More channels required stronger identity, consent, integration, and governance. ## What the history explains today Many current problems come from layers added at different times. A company may have batch email lists, CRM stages, website forms, product events, and AI suggestions that never shared one data model. Buying a new orchestration layer can expose those differences without resolving them. Teams should examine inherited fields, campaigns, integrations, and definitions before modernizing. Some practices remain because a prior tool required them rather than because the customer journey still does. A software company has ten years of nurture programs. Early lists use campaign-specific fields, later workflows use lifecycle stages, and new product events use a separate customer identity. The modernization project maps this history, preserves necessary consent, retires obsolete fields, and establishes one ownership model before adding agent-driven decisions. Understanding the past prevents the new system from automating old contradictions. Automation still requires a clear audience, useful message, trustworthy data, ownership, permission, and measurement. New interfaces can make workflows easier to create without making the underlying decision better. Historical review helps teams recognize recurring promises of effortless personalization and scale. The durable work remains defining the customer state, choosing the next appropriate action, and correcting the process when evidence shows harm or waste. --- # Marketing Automation Implementation | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-automation-implementation Marketing automation implementation is the work of translating a marketing automation strategy into a functioning system. It includes data and lifecycle definitions, platform configuration, integrations, audience rules, consent, templates, workflows, lead handoffs, permissions, testing, reporting, documentation, and operator training. Implementation is broader than enabling a platform. Technically successful syncs can still spread a bad lifecycle definition or give two systems permission to overwrite lead ownership. The work is complete when people and systems can execute the intended process, detect errors, and recover without private knowledge from the original builder. Automation touches customer communication and business records at scale. Missing suppressions can contact the wrong audience; incorrect field mappings can break routing; untested re-entry rules can send the same sequence twice. Decisions made during implementation affect trust, measurement, and the amount of manual repair required later. Begin with the lifecycle and workflows, then map the systems and fields needed to support them. Name sources of truth and write permissions. Build in a nonproduction environment where possible, create representative test records, and validate normal cases as well as missing data, duplicates, consent changes, manual edits, delayed syncs, and rollback. Release in a limited scope, monitor every transition, and give exceptions a visible queue and owner. Keep a runbook with purpose, architecture, field mappings, workflow logic, test cases, launch approvals, change history, and retirement steps. Train operators on why the rules exist so later changes do not preserve syntax while breaking the business decision. During a webinar follow-up implementation, CRM controls account owner and opportunity stage; the event tool supplies registration and attendance; the automation platform controls campaign status and messages. Test records cover existing customers, open opportunities, bounced emails, duplicate contacts, no-shows, attendees, and people who book before the sequence ends. Strong implementations leave behind working automation and a process another operator can understand, test, change, and stop safely. Documentation and ownership have to survive the original launch team. --- # Marketing Automation Requirements | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-automation-requirements Marketing automation requirements are the conditions a team must satisfy before an automated campaign or operational workflow can work reliably. They cover the business use case, audience and consent rules, data fields, system ownership, triggers, content, handoffs, exceptions, testing, measurement, and ongoing maintenance. Platform features belong in the requirements only when they support one of those needs. The list should describe what the operation needs to do, which records it can trust, and what happens when normal conditions fail. It should also identify the people authorized to change the logic after launch. Automation multiplies the quality of the process it receives. An unclear lifecycle stage becomes an unclear trigger at scale. A duplicate account can send the same buyer down conflicting paths. A missing suppression rule can keep a sales-ready prospect inside an educational sequence. Requirements expose these dependencies while the team can still change the design cheaply. They also create a fair basis for choosing software. A requirements list helps buyers compare how products handle identity, integrations, branching, approvals, audit history, error queues, and reporting instead of scoring vendors by the length of a feature page. Write the required input, rule, action, owner, timing, and output for each workflow. Name the system of record for every field and define source precedence when systems disagree. Include entry, exit, re-entry, and suppression conditions. Record service levels, access controls, test cases, failure alerts, and the reporting definition for success. Review the document with marketing, sales, RevOps, legal or privacy owners, and whoever will maintain the workflow. A requirement without an owner is usually a wish. A webinar nurture requires a verified email address, recorded consent, event attendance status, account owner, lifecycle stage, and language preference. It must suppress open opportunities, stop after a demo request, and create a review task when ownership is missing. The team tests attendee, no-show, duplicate, opt-out, and existing-customer records before activation. Those requirements prevent a polished sequence from sending the wrong message to the wrong person. --- # Marketing Automation Strategy | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-automation-strategy A marketing automation strategy explains where software should use data, timing, and rules to move a person or account toward a useful next action. It connects business goals with lifecycle stages, entry and exit conditions, content, ownership, consent, measurement, and the systems allowed to update customer state. Buying a platform supplies capabilities rather than a strategy. Email builders, lead scores, audience syncs, and workflow canvases can execute decisions, but the company still has to define whom to contact, why the contact helps, what should happen after a response, and when automation should stop. Automation magnifies the quality of the underlying journey and data. Sound programs deliver timely education and hand high-intent demand to the right owner. Weak ones send stale nurture after a person becomes a customer, create duplicate tasks, or change lifecycle fields in ways that make reporting impossible to trust. Start with one lifecycle problem and one measurable outcome. Map the data and systems involved, define eligibility and suppression, design the action and handoff, then test every exit and exception. Separate customer state from temporary workflow state so completing an email sequence does not become a false statement about buying readiness. Keep a plain-language record for every automated program: purpose, audience, trigger, exclusions, actions, delays, owner, exit, re-entry, consent basis, write permissions, and success measure. Review conflicting campaigns together and cap frequency across channels. Use sales and customer feedback to change the strategy, not merely the subject line. After reviewing buyer behavior, one company replaces a generic 30-day download sequence with programs tied to behavior and account fit. Educational readers receive related material. High-fit visitors who return to pricing route to sales within minutes. Booked contacts exit promotional nurture, and customers move into onboarding communication controlled by the customer team. Marketing automation strategy should define the relationship and decision before software executes the next step. Revisit it whenever lifecycle definitions, sales capacity, consent requirements, or customer communication ownership changes. --- # Marketing Automation Workflow | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-automation-workflow A marketing automation workflow is a repeatable process in which a trigger and set of business rules cause software to take or propose actions. Examples include nurturing a new subscriber, routing a demo request, recovering an abandoned form, escalating pricing-page intent, updating a lifecycle stage, or suppressing a customer from acquisition messages. The visible emails are only part of the workflow. The system also depends on identity, source data, consent, timing, branching, ownership, CRM updates, exception handling, and measurement. A reliable workflow explains why each person entered, what happened, and how they leave. Write the workflow in ordinary language before configuring the tool. Define the business event, eligibility, exclusions, source fields, action sequence, delays, owner, exit, re-entry, and error behavior. Then build and test with records that represent normal, missing, duplicate, late, and conflicting inputs. 1. Choose a trigger tied to a meaningful event, such as a form submission, stage change, product action, or elapsed service-level timer. Record the event time and source. 2. Evaluate eligibility and suppression before taking action. Check consent, customer status, segment, owner, open opportunity, recent communication, and data confidence as relevant. 3. Execute the smallest useful action or branch. Send a message, create a task, assign an owner, enrich a record, draft a response, or wait for another event. 4. Handle exceptions and timeouts explicitly. Missing data, unavailable reps, failed syncs, duplicate records, and conflicting stages should enter visible states with owners. 5. Measure the workflow through delivery, movement, conversion, latency, error, and business outcome. Feed sales rejection and customer response back into the rules. Track eligible records, entry and completion, time between steps, message engagement, task completion, routing acceptance, stage movement, meetings, opportunities, revenue, opt-outs, and exceptions. Compare by cohort and workflow version because a rule change can alter both audience and outcome. The operating discipline for a marketing automation workflow is a chain from question to source to interpretation to decision. Preserve interview notes, survey instruments, queries, public records, and dated product evidence with enough context to audit the conclusion. Add a confidence statement and the observation that would reverse the recommendation. This avoids the familiar research failure where a clean slide outlives the evidence and continues to guide positioning after the market has changed. Keep the smallest useful scope for a marketing automation workflow until the operation has evidence to expand. Limit templates, segments, permissions, channels, or actions at first. Review errors and manual work, then add scope deliberately. This makes ownership and rollback practical and gives the team a baseline against which a broader version can be judged. The final artifact should show the current decision, the evidence behind it, and the condition that forces reconsideration. That is what makes a marketing automation workflow maintainable after the original operator moves to another project. Retirement belongs in the operating plan for a marketing automation workflow too. Define the signal that shows the process no longer serves its original audience, system, category, or decision. Archive the configuration and evidence, stop new entries safely, preserve required history, and update dependent reports or links. Unused processes create risk when they remain active simply because no one owns turning them off. Record where a marketing automation workflow remains uncertain and when that uncertainty becomes material. This gives the next operator a starting point instead of forcing another full audit. - Which event is reliable enough to begin the workflow? - Which fields and systems determine eligibility, branching, and suppression? - Which actions may run automatically and which require review? - Who owns exceptions, timeouts, manual overrides, and rollback? - Which outcome justifies keeping or expanding the workflow? Every branch is business policy. Store the reasoning beside the automation and give the rule an owner. A flow diagram without field definitions and exception behavior may look complete while hiding its most consequential choices. The common failure is a workflow that has entries and actions but no exits. Leads receive nurture after booking, customers stay in acquisition campaigns, and manual sales updates are overwritten by the next sync. No one wants to disable the flow because no one knows which records depend on it. Add explicit exit and suppression rules, centralize shared definitions, record action reasons, and test the flow from the customer's point of view. Pause branches that cannot explain their audience or outcome, then rebuild them from a smaller verified trigger. --- # Marketing Growth Strategy | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-growth-strategy A marketing growth strategy is a set of choices about how marketing will create durable business growth. It identifies the markets and audiences worth pursuing, the position and offer the company will take to them, the channels that can reach them, and the conversion system that turns attention into customers and revenue. The strategy sits above an annual campaign calendar. Campaigns express the choices for a period; the growth strategy explains why those choices belong together and what the company expects to learn. In B2B, it also accounts for sales capacity, deal economics, buying groups, implementation limits, retention, and expansion. Without a shared strategy, each channel can look busy while the business problem stays untouched. Paid media may increase form volume while sales lacks qualified opportunities. Content may earn search visibility around subjects that never enter a deal. Across those channels, the strategy supplies a common audience, economic goal, and feedback loop. Start with the growth constraint. Strong traffic paired with weak lead conversion calls for a different plan than entry into a new category with little awareness. Establish the baseline, choose the segment and growth mechanism, state the economic limits, then assign channels roles such as demand creation, demand capture, proof, conversion, or retention. Write the strategy as a small portfolio of decisions and hypotheses. For each one, record the audience, intended behavior, investment, owner, expected time horizon, evidence, and signal that would cause a change. Review channel metrics alongside meetings, opportunities, revenue, customer quality, and payback so local optimization does not outrun the business. Consider a vertical software company with healthy organic traffic but too few qualified meetings. Its next-quarter strategy puts less money into broad traffic acquisition and more into comparison pages, customer proof, shorter forms, enrichment, and immediate routing for high-intent visitors. The team measures accepted meetings and opportunity creation by segment, then uses sales rejection reasons to revise targeting and content. Marketing growth strategy is useful when it narrows the work. It should tell a team which growth problem comes first, which bets deserve resources, and which evidence will shape the next choice. --- # Marketing Intelligence and Marketing Research | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-intelligence-and-marketing-research Marketing intelligence is the ongoing collection and interpretation of market signals, while marketing research is a time-bounded study designed to answer a defined question. Intelligence may track competitors, customers, category movement, pricing, channels, and regulation. Research uses a planned method, sample, and analysis to reduce uncertainty around one decision. The two practices feed each other. An intelligence system may detect a pattern, such as a new competitor appearing in lost deals. A research project can investigate why that competitor is gaining consideration. The study then produces new questions or indicators for routine monitoring. Neither label establishes evidence quality on its own. Without ongoing intelligence, research teams can study questions that have already changed. Without focused research, monitoring can become a pile of alerts and screenshots with no decision attached. The distinction also clarifies expectations: intelligence is built for continuity and early detection, while research is built for depth around a specified uncertainty. Give intelligence a defined watchlist, cadence, source record, threshold, and owner. Give research a decision, question, population, method, instrument, field period, and review standard. Store both in a shared evidence system so an analyst can trace a strategic claim back to dated observations and see when a finding should expire. Run a regular review where operators classify signals as noise, known movement, or a question that deserves investigation. Select research projects by the likely consequence of being wrong and the evidence gap involved. After each study, decide which findings need continued monitoring. Avoid promoting one unverified competitor claim into a permanent market fact simply because it appeared repeatedly in copied sources. A payments company monitors win-loss notes and sees more buyers asking about usage-based pricing. The intelligence owner checks competitor pricing pages and sales-call evidence, then commissions interviews across won, lost, and stalled deals. The study finds that buyers care about cost predictability rather than the billing unit itself. Future monitoring tracks contract objections and pricing changes instead of counting mentions of one phrase. Marketing intelligence spots movement; marketing research examines a defined uncertainty closely enough to guide a decision. --- # Marketing Operations | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-operations - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Marketing Operations Management | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-operations-management Marketing operations management is the ongoing coordination of the people, processes, data, technology, budgets, and controls that allow marketing work to run. It covers intake, planning, campaign production, system administration, data quality, workflow design, measurement, vendor management, documentation, and service delivery to marketing and revenue teams. Strategy sets the operating choices and priorities; management turns them into day-to-day decisions. The function may sit in marketing, revenue operations, or a shared business-operations group. Its scope depends on company size, but the underlying job remains the same: make execution dependable and make performance evidence understandable. Marketing work crosses many handoffs. A campaign can stall in legal review, launch with inconsistent tracking, create records that sales cannot use, or reach customers who should have been excluded. Operations management makes those dependencies visible and gives recurring work an owner, service level, quality check, and path for exceptions. The manager balances planned initiatives, maintenance, incidents, and small requests. Useful routines include a visible intake queue, capacity review, launch checklist, change log, system health checks, data-quality monitoring, access review, metric governance, and post-launch analysis. Standardize the stable parts of work while leaving room for campaigns that have genuinely different requirements. Define service categories and publish what each requires. Prioritize by business effect, urgency, effort, dependency, and risk instead of requester seniority alone. Track queue age, cycle time, rework, errors, adoption, incident recovery, data quality, and stakeholder outcomes. Reserve capacity for repairs and documentation. Review the tool stack against actual workflows so renewal does not become the only reason a platform survives. A content team sends campaign requests through chat, email, and meetings. Operations creates one intake path with fields for audience, goal, owner, launch date, dependencies, data needs, and approval. Weekly triage exposes that most delays come from late landing-page copy, not automation setup. The team changes the briefing deadline and measures fewer launch reversals before considering another tool. Marketing operations management keeps the operating system useful after the strategy deck is finished and the first workflow goes live. --- # Marketing Operations Strategy | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-operations-strategy A marketing operations strategy sets the operating choices that allow marketing plans to run consistently. It defines ownership, planning rhythms, data standards, process boundaries, technology responsibilities, measurement rules, and the order in which operational problems will be solved. The strategy connects those choices to the company's marketing and revenue priorities. Marketing leaders usually need one when campaign demand outgrows the team's operating system. Requests arrive through several channels, tools hold conflicting records, launch work stalls in handoffs, and leadership cannot reconcile performance numbers. Buying another platform may change the symptoms without resolving the ownership and definition problems underneath them. Operations work can become an endless queue of urgent fixes. The strategy gives the team a basis for choosing which constraint deserves attention and which requests can wait. It also prevents local improvements from damaging another part of the system. For example, faster campaign launches have little value if rushed tracking makes the resulting pipeline impossible to attribute. Begin with the business outcomes and operating failures that block them. Map the workflows, decision rights, system boundaries, and data dependencies involved. Set principles for intake, prioritization, quality review, access, documentation, and change control. Convert the strategy into a sequenced roadmap with owners and measurable service levels, leaving room for maintenance and unplanned incidents. Keep the document specific enough to guide tradeoffs. Name the audiences the operating model supports, the work that receives a standard path, the systems of record, and the metrics whose definitions are governed. Record where human approval is required and where software can act safely. Review the roadmap with demand generation, content, sales operations, analytics, and finance so dependencies appear before implementation begins. A software company wants to double campaign output without adding operations headcount. Its strategy standardizes briefs and intake, limits campaign variants, creates reusable tracking conventions, and assigns one owner for lifecycle fields. The first quarter focuses on request visibility and launch quality. Automation follows only after the team measures rework, queue time, tracking errors, and adoption of the standard process. A marketing operations strategy turns scattered improvement requests into a deliberate operating model with an order, an owner, and a reason. --- # Marketing Research Questions | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-research-questions Marketing research questions define what a team needs to learn before changing an audience, message, channel, campaign, brand, offer, or customer program. They translate a marketing problem into evidence that can guide action. A dashboard question such as "Why did conversion fall?" becomes several research questions about traffic mix, audience fit, page experience, offer, measurement, and follow-up. The research question sits above the wording used in a survey, interview, test, or analysis. Several instruments may contribute evidence to one marketing question. Audience questions examine who experiences the problem, how groups differ, and where they seek information. Positioning and message questions examine category understanding, desired outcomes, credibility, and response to claims. Channel questions study reach, context, cost, and the behavior each source produces. Campaign questions examine offer, creative, destination, capture, and downstream quality. Brand questions examine awareness, association, trust, and consideration. Lifecycle questions follow the relationship after capture or purchase. They can study onboarding, adoption, retention, expansion, and the effect of communication across stages. State the decision and the metric or observation that created concern. Identify competing explanations before choosing a method. Name the population, period, exposure, and behavior. Ask what evidence would support each explanation and what action would follow. Avoid questions that ask respondents to diagnose the company's entire funnel. Combine their reported experience with campaign, sales, product, or customer evidence where appropriate. A paid campaign produces many leads and few accepted opportunities. The team asks whether the audience matches the target segment, whether the offer attracts research without buying intent, whether form data supports qualification, and whether response arrives on time. Ad records, form behavior, sales disposition, response timestamps, and interviews answer different parts. The questions direct the team toward a specific change instead of labeling the channel low quality. A research program may need one strategic question, several study questions, and many instrument questions. Keep the hierarchy visible. The strategic question sets the decision. Study questions divide the evidence needed. Interview or survey questions collect observations without announcing the desired conclusion. If a questionnaire item cannot be traced back to a study question, remove it or explain the separate use. --- # Marketing Tactics | Surface Glossary URL: https://surface.thesurface.network/glossary/marketing-tactics Marketing tactics are the specific actions a team uses to execute a strategy. They include campaigns, content, events, email, paid media, search, partnerships, social activity, sales enablement, offers, landing pages, experiments, and account programs. A tactic should have a defined audience, objective, owner, resource requirement, timing, and measure. Strategy sets the market choice and reason for action. Tactics express that choice in work. The same tactic can support very different strategies. A webinar might educate a new category, accelerate active opportunities, retain customers, or reach partners. The operating design changes with the job. 1. **Start with the strategic choice.** Name the segment, problem, position, commercial objective, and behavior the program needs to influence. Do not begin with a channel simply because the team has used it before. 2. **Choose a tactic that fits the audience.** Consider where buyers learn, how much attention the subject requires, what evidence is available, and whether the next step can occur in that channel. 3. **Design the complete path.** Connect the message, asset, distribution, destination, capture, follow-up, sales use, and measurement. Assign owners to handoffs and exceptions. 4. **Set a testable expectation.** State the input, expected behavior, metric, time window, and decision that follows. Preserve a comparison when possible. 5. **Review and revise.** Examine audience quality, experience, conversion, cost, sales feedback, and downstream outcomes. Continue, change, or stop the tactic based on the result and its strategic role. - Whether the tactic serves discovery, evaluation, conversion, adoption, retention, or expansion. - Which segment and buying role the execution addresses. - What proof the message needs and who can substantiate it. - Which channel owns the interaction and where the relationship continues. - How much production and operational work the tactic requires. - Which result would justify repetition, modification, or retirement. Individual tactics often depend on one another. Research shapes the message. Content gives an event substance. Email reinforces attendance. A landing page captures the request. Sales continues the conversation. Reporting connects the sequence to opportunity and revenue. Planning only the visible campaign asset leaves the operating work to chance. Maintain a portfolio rather than treating every tactic as a permanent program. Some actions build long-term discoverability, while others capture current demand. Their time horizons and measures should reflect those roles. The common failure is tactic-first planning. A leader asks for a podcast, the team produces episodes, and no one can explain which audience decision the series should change. The activity creates deadlines and channel metrics without contributing to a coherent market approach. A better team writes one sentence before committing resources: for this audience, this tactic will create this useful change because of this evidence. The sentence does not guarantee success. It gives the team a claim it can examine, a reason to design the path, and permission to stop work that no longer supports the strategy. Compare tactics on the job they perform. An educational guide may need months to build qualified discovery, while a high-intent search campaign can create immediate responses at a higher cost. A customer webinar may support retention and expansion rather than net-new lead volume. Place each tactic inside its intended time horizon and buyer stage. Use common economic definitions where the work is comparable. Include production, media, software, event, agency, and operator cost according to a stated scope. Measure the quality and maturity of the cohort alongside the number of responses. A low-cost lead source can become expensive after poor contact, acceptance, opportunity, or retention. Consider portfolio effects. Research can strengthen content, content can improve paid conversion, and events can give sales a reason to reopen accounts. Report these relationships without assigning the same revenue to several tactics. The purpose is to allocate resources with judgment, not to manufacture a perfect attribution story. Define the condition that ends or redesigns a tactic before launch. It may be cost, weak fit, poor sales acceptance, low retention, repeated complaints, or failure to reach the intended audience. A stop condition protects the team from maintaining activity because production has become familiar. --- # Martech | Surface Glossary URL: https://surface.thesurface.network/glossary/martech Martech, short for marketing technology, is the software and technical infrastructure used to research markets, create campaigns, publish content, attract demand, capture leads, automate communication, manage data, and measure performance. The category includes tools, integrations, schemas, workflows, and the people who operate them. A CRM, marketing automation platform, CMS, analytics tool, ad platform, form builder, enrichment service, scheduling system, and AI agent can all sit inside martech. Buying those products does not create a working system. The stack needs shared definitions, reliable data movement, clear ownership, and a reason for each handoff. A martech operation begins with the customer and lead journey, then maps the systems that support each stage. Teams should know which platform owns the record, where a decision occurs, how an exception appears, and which data the next tool receives. Tool selection follows the workflow rather than defining it. 1. Map the business motion from audience research through campaign, page visit, lead capture, qualification, routing, nurture, opportunity, and revenue. Mark the decisions and data created at each stage. 2. Inventory every tool, integration, field mapping, owner, contract, and critical dependency. Include spreadsheets and manual queues because informal systems often contain the most important business logic. 3. Choose systems of record and systems of action. A CRM may preserve account and opportunity history, while another layer handles form behavior, enrichment, routing, or campaign execution. 4. Document field definitions and handoffs. Test what happens when a value is missing, an integration is delayed, a rep is unavailable, or a user withdraws consent. 5. Measure business outcomes and operational health. Review conversion, latency, exception volume, duplicate rate, manual effort, tool cost, and the percentage of workflows someone can actually explain. Martech performance should include reliability and business impact. A workflow can be technically available while producing poor leads, slow response, or unreadable attribution. Pair system measures such as sync errors and processing time with funnel measures such as accepted leads, booked meetings, qualified pipeline, and revenue. Operational review of martech should reconstruct one record's journey from the event that started the automation to the outcome the business measures. Logs should show which rule fired, which data it used, what it changed, and whether a person intervened. Review abandoned branches and unused workflows on a cadence. Automation debt often survives because the flow still runs, even after its audience, owner, or business purpose has disappeared. Keep the smallest useful scope for martech until the operation has evidence to expand. Limit templates, segments, permissions, channels, or actions at first. Review errors and manual work, then add scope deliberately. This makes ownership and rollback practical and gives the team a baseline against which a broader version can be judged. The final artifact should show the current decision, the evidence behind it, and the condition that forces reconsideration. That is what makes martech maintainable after the original operator moves to another project. Retirement belongs in the operating plan for martech too. Define the signal that shows the process no longer serves its original audience, system, category, or decision. Archive the configuration and evidence, stop new entries safely, preserve required history, and update dependent reports or links. Unused processes create risk when they remain active simply because no one owns turning them off. Record where martech remains uncertain and when that uncertainty becomes material. This gives the next operator a starting point instead of forcing another full audit. - Which business capability is important enough to justify a tool or integration? - Which system owns each record and which system may take action on it? - Who maintains business rules, credentials, schemas, and exception queues? - What data may move between vendors, and how long should it be retained? - Which tools can be consolidated or removed without losing a required capability? The best stack is not necessarily the smallest or the largest. It is the one whose complexity matches the business and remains operable by the available team. A specialized tool earns its place when the benefit exceeds the integration, governance, and maintenance burden. The common failure is tool-led architecture. A team buys a platform for a feature, adds an integration for a gap, and builds a spreadsheet to repair the integration. Over time, several systems update the same field and no one knows which rule won. The stack looks sophisticated from the contract list and fragile from the lead's point of view. Trace one high-value journey end to end, expose the hidden business logic, and assign one owner to each decision. Consolidate duplicated actions, preserve the systems that hold trusted history, and remove integrations that cannot explain their purpose or failure behavior. --- # Martech Stack | Surface Glossary URL: https://surface.thesurface.network/glossary/martech-stack A martech stack is the collection of platforms and infrastructure a company uses to research audiences, manage content, run campaigns, capture and qualify demand, communicate with buyers, maintain customer data, and measure results. It includes integrations, schemas, permissions, business rules, and operators as well as software products. Common layers include CRM, marketing automation, CMS, analytics, advertising, forms, enrichment, lead routing, scheduling, email, experimentation, data warehouse, consent, and AI agents. The exact stack should match the business motion and team capacity. A diagram of vendor logos does not show how the operation works. Map capabilities and customer journeys before tools. Identify systems of record, action layers, data movement, rule locations, owners, credentials, exception queues, and measures. Evaluate each component by business value, reliability, overlap, maintenance, security, and switching cost. 1. Document the journey from market research and campaign creation through visit, capture, qualification, routing, nurture, opportunity, customer, and measurement. Mark every system and manual handoff. 2. Assign systems of record for customer, account, opportunity, campaign, consent, content, and product behavior. Name which tools may write each important field. 3. Inventory integrations, field mappings, workflow rules, owners, credentials, contracts, and failure alerts. Include spreadsheets, scripts, and manual queues that carry production logic. 4. Score components by required capability, usage, reliability, overlap, data risk, cost, and operational burden. Consolidate only when the replacement preserves the needed workflow and history. 5. Review the stack on a cadence and after major changes. Remove orphaned integrations, archive unused fields and workflows, and test high-value journeys end to end. Measure stack health through availability, sync latency, error and exception rates, duplicate records, data completeness, manual hours, tool adoption, cost, lead response, conversion, and report reconciliation. Technical uptime alone cannot show whether the stack creates qualified pipeline. For a martech stack, maintain a plain-language workflow contract beside the platform configuration. State the trigger, eligibility, exclusions, input fields, source systems, branch rules, action, owner, wait conditions, exit, re-entry, suppression, timeout, exception, and rollback. Record which system may update every affected field. Test the workflow with duplicates, delayed integrations, missing values, manual overrides, consent changes, unavailable owners, and people who already completed the desired action. Use separate measures for the correctness, reliability, efficiency, and business value of a martech stack. A process can be accurate on completed cases and still fail through delays or missing coverage. It can be reliable and still create little value. Report denominators, exclusions, time windows, and unresolved cases so leaders can see which part of the system actually improved. Review the process with the team that receives its output. Their acceptance, corrections, and workarounds reveal whether a martech stack functions in the real operating environment rather than only inside its source tool. Give the team receiving output from a martech stack a visible way to accept, correct, reject, or escalate it. Their response should return to the shared record with a reason and timestamp. Review those reasons by workflow version and segment. This feedback shows whether a martech stack is reducing work, moving the right cases, and preserving enough context for the next person to act. End the a martech stack review with open questions and their owners. An unresolved item can remain open, but it should not disappear into an apparently final configuration. - Which capabilities are required by the business motion? - Which system owns each record, field, decision, and action? - Which integrations and workflows carry material risk or revenue dependence? - Which overlap is useful resilience and which is accidental duplication? - Can the current team operate, audit, and change the stack safely? Tool count is a poor objective. Fewer tools can create brittle compromises, while many tools can create invisible handoffs. The stack should be as simple as the requirements allow and as explicit as the consequences demand. A common failure is buying point solutions around each visible symptom. A new form tool fixes conversion, a router fixes assignment, a spreadsheet fixes the router, and an enrichment vendor fixes missing fields. The journey accumulates latency and data loss at every connection. Trace one important lead or customer path, expose duplicated decisions, and centralize shared business logic. Preserve trusted systems of record, choose clear action owners, and retire components whose capability no longer exceeds their maintenance cost. --- # Martech Stack Optimization | Surface Glossary URL: https://surface.thesurface.network/glossary/martech-stack-optimization Martech stack optimization is the work of improving how marketing technology supports real workflows. It examines tool purpose, adoption, data movement, integration reliability, permissions, cost, overlap, maintenance, and business results. The goal is a smaller amount of operational friction, which may involve configuring an existing tool, changing a process, consolidating vendors, or adding a missing capability. Optimization begins with the work. A platform that looks underused may be unnecessary, poorly implemented, assigned to the wrong team, or capable of replacing several disconnected tools. Usage data alone cannot tell which explanation is true. Every tool creates a system boundary, data copy, access model, renewal, and maintenance obligation. Overlap can increase cost and give teams several ways to perform the same task. Gaps can force manual work or prevent a buyer signal from reaching the person who needs it. Fragile integrations make reports disagree and turn ordinary field changes into incidents. A disciplined review helps marketing invest in the constraints that affect campaign quality, lead response, content operations, measurement, and customer experience. Inventory the tools, contracts, owners, users, integrations, data objects, workflows, and renewal dates. Map critical journeys across systems and note where records are created, transformed, delayed, or lost. Review adoption by job, not by login count. Compare duplicate capabilities, switching cost, data portability, security, and the labor required to keep each platform useful. Prioritize changes by consequence and dependency. Fix identity, consent, ownership, and measurement foundations before adding complex orchestration. Assign an owner and success measure to every stack change. A demand team uses separate products for forms, enrichment, routing, scheduling, email, and reporting. The review finds that two systems enrich the same accounts, while neither owns correction handling. The company keeps the stronger enrichment source, moves exceptions into a visible queue, and retires the duplicate contract. It measures fewer conflicting fields, faster routing, lower spend, and less manual review rather than celebrating a smaller logo chart. Prioritize changes that remove a repeated failure or protect consequential data. A broken ownership sync deserves attention before a new personalization feature. Sequence consolidations around renewal dates, migration effort, reporting dependencies, and user training. Maintain a rollback and export plan for every retired tool. The optimized stack should make important work easier to explain and recover when something fails. --- # Effective Lead Generation Tactics | Surface Glossary URL: https://surface.thesurface.network/glossary/most-effective-lead-generation-tactics The most effective lead generation tactics are the ones that reach a specific buyer, earn enough trust for a response, and connect that response to a working conversion system. In B2B, common tactics include search and educational content, paid demand capture, webinars, events, partner programs, targeted outbound, customer referrals, tools, assessments, and product-led experiences. There is no universal ranking because channel economics, buyer concentration, sales cycle, deal size, and brand awareness change the answer. A high-volume ebook campaign may underperform a narrow comparison page if the business needs qualified demos. An event may look expensive by lead count and strong by opportunity value. Tactics fail when teams measure the first response and ignore the handoff. More form submissions do not help if records arrive incomplete, routing takes a day, or sales rejects the audience. Lead generation includes the path from message and offer through capture, qualification, ownership, and follow-up. Choose tactics from the buyer's research and decision process, set one primary conversion, and define quality before launch. Instrument source and campaign data, reduce unnecessary form friction, enrich only when it improves a decision, route high-intent leads quickly, and compare channels through meetings, opportunities, pipeline, and revenue as well as volume. Use effective lead generation tactics with an explicit audience, conversion, quality rule, owner, and service level. Preserve source and content context so the person receiving the lead knows what created the response. Review a sample of real cases before relying on an aggregate score. The sample should include incomplete, conflicting, and high-value records because averages often hide the failures with the largest business cost. Place the documentation for effective lead generation tactics beside the workflow or decision it affects. That keeps definitions, evidence, ownership, and later corrections available to the people who need them. A vertical SaaS company combines a category guide, two competitor comparisons, a monthly practitioner webinar, and tightly targeted search ads. Each path uses a short form, product-interest question, and immediate routing. The team drops a high-volume generic campaign after it produces many downloads and almost no sales-accepted leads. The effective tactic is the complete operating path, not the channel name. A modest source with clear fit and fast follow-up can create more pipeline than a large audience that enters a broken system. --- # New Product Market Research | Surface Glossary URL: https://surface.thesurface.network/glossary/new-product-market-research New product market research gathers and analyzes evidence for decisions about a proposed or recently launched offering. It can examine the target audience, problem, current alternatives, buying process, concept comprehension, expected use, willingness to pay, route to market, adoption barriers, and early customer behavior. The research should match the product decision that is still open. Different stages call for different evidence. Early discovery explores problems and existing behavior without asking people to predict a finished product. Concept work tests whether an idea is understood and credible. Prototype or pilot research observes use. After launch, cohort behavior and customer conversations show where acquisition, activation, retention, or positioning assumptions fail. Teams can become attached to a solution before proving that the problem is frequent, costly, and owned by a reachable buyer. Research makes those assumptions discussable and can narrow the product, segment, or launch before larger commitments. It cannot guarantee success, and positive reactions to a concept are weaker evidence than purchase, adoption, or repeated use. Write the next product decision and recruit people who have direct experience with it. Study current behavior and alternatives before presenting the concept. Use prototypes or realistic choice tasks where possible. Separate the user, buyer, approver, administrator, and economic owner in B2B research. Record sample limits, rejected cases, changed assumptions, and the evidence required for the next investment. Begin with secondary evidence and problem interviews, then move toward concept comparison, usability, pricing, pilot, and behavioral analysis as the product becomes concrete. Do not run every method automatically. Choose the smallest study that can change the next decision. Keep marketing claims, product requirements, and sales expectations linked to current evidence and assign review dates as the market and product change. A company considers an automated compliance assistant for regional banks. Interviews reveal that analysts already solve the task, while approval and audit history create the delay. The team tests a prototype focused on review workflow rather than automated answers, pilots it with two compliance teams, and measures completed reviews, corrections, and supervisor trust before building broader generation features. New product market research reduces the distance between what a team hopes buyers will do and what the available evidence supports. --- # Online Customer Acquisition Strategy | Surface Glossary URL: https://surface.thesurface.network/glossary/online-customer-acquisition-strategy An online customer acquisition strategy is a set of choices about how a company will use digital channels to attract, convert, and learn from new customers. It defines the audience, problem, offer, position, channel mix, content, destination, conversion path, follow-up, economics, and measurement. Channels may include search, content, paid media, social, email, communities, affiliates, partners, marketplaces, referrals, and product-led experiences. The strategy should reflect the buying process. A self-service product can convert inside the site, while an enterprise offer may use online activity to create a qualified conversation that continues with sales. Acquisition requires reach and conversion, but it also depends on fit, cost, speed, retention, and capacity. A channel with inexpensive signups can lose money when customers leave quickly. A high-cost channel can work when it produces durable, high-value accounts. Attribution can help compare activity, though it cannot prove every causal contribution. The strategy should combine demand creation with places where buyers already express intent. Define the target segment, customer value, sales motion, payback requirement, and capacity. Map buyer questions and digital touchpoints. Choose a small channel portfolio with distinct jobs. Build landing pages, proof, forms, trials, scheduling, routing, nurture, and onboarding as one path. Preserve source and cohort data through the customer lifecycle. Measure qualified acquisition, conversion, cost, cycle time, revenue, retention, and payback by channel and segment. Reallocate based on mature cohorts rather than early click volume. A B2B software company uses technical search content to create discovery, retargeting to return relevant visitors, comparison pages for evaluation, and a guided trial for qualified teams. Enterprise accounts can request a consultation that routes by existing ownership. The company compares activation, opportunity, revenue, retention, and total cost across cohorts. It reduces spend on a high-volume channel after learning that those customers rarely complete setup. Give each channel a role, budget, test period, and stop condition. Protect learning budget for new channels while keeping enough investment in established paths to measure mature performance. Account for interaction without assigning every conversion several times. Revisit the mix when customer economics, platform costs, privacy rules, competition, or product experience changes. A durable strategy can change channels without losing its audience and value logic. --- # Online Market Research | Surface Glossary URL: https://surface.thesurface.network/glossary/online-market-research Online market research is research conducted through digital channels or based on internet-accessible evidence. It includes online surveys, remote interviews, digital communities, website experiments, search and traffic data, social listening, review analysis, public datasets, competitor sites, product documentation, job posts, and online panels. Online describes the collection environment rather than the quality of the evidence. A large web survey can still have a poor sample. Social posts may overrepresent vocal users. Traffic estimates may use opaque models. Researchers should match each source to a question and preserve its date, scope, and limitations. Start with a narrow decision, build a source plan, and distinguish observed facts from modeled estimates or participant claims. Use primary and secondary sources together when they answer different parts of the problem. Capture URLs, screenshots where necessary, access dates, query methods, instruments, and sampling details. 1. Define the market, audience, decision, geography, and time period. Broad internet searching without a decision usually produces a pile of facts rather than research. 2. Choose sources by evidentiary job. Product pages describe current claims, public filings support company facts, interviews explore motivation, and surveys estimate reported behavior within a sample. 3. Design collection rules before gathering material. Record queries, inclusion criteria, dates, duplicates, paid access, and the way platform algorithms may shape what the researcher sees. 4. Analyze source quality and contradiction. Prefer primary records for current product facts, and keep estimates labeled when no direct count exists. 5. Translate findings into a decision record. State the evidence, uncertainty, implication, owner, and the next observation that would change the recommendation. Judge the project by coverage of the decision, source quality, sample fit, reproducibility, recency, contradiction handling, and whether a stakeholder can trace conclusions back to evidence. Speed and volume are secondary if the research cannot support the intended claim. For online market research, build a decision brief that keeps the market boundary and evidence types visible. List the population, geography, segment, period, inclusion rules, sources, dates, method, and assumptions. Separate direct observations, participant reports, vendor claims, modeled estimates, and internal interpretation. When sources disagree, show the disagreement and explain which definition or method creates it. A later reviewer should be able to update one assumption without rebuilding the entire argument. Use separate measures for the correctness, reliability, efficiency, and business value of online market research. A process can be accurate on completed cases and still fail through delays or missing coverage. It can be reliable and still create little value. Report denominators, exclusions, time windows, and unresolved cases so leaders can see which part of the system actually improved. Review the process with the team that receives its output. Their acceptance, corrections, and workarounds reveal whether online market research functions in the real operating environment rather than only inside its source tool. Give the team receiving output from online market research a visible way to accept, correct, reject, or escalate it. Their response should return to the shared record with a reason and timestamp. Review those reasons by workflow version and segment. This feedback shows whether online market research is reducing work, moving the right cases, and preserving enough context for the next person to act. End the online market research review with open questions and their owners. An unresolved item can remain open, but it should not disappear into an apparently final configuration. - Which sources are credible enough for each type of fact? - How will platform bias, self-selection, and modeled data be labeled? - Which claims require direct participants rather than public observation? - How will personal data, consent, screenshots, and access restrictions be handled? - Who reviews the interpretation before it becomes positioning or campaign strategy? Internet access can create the illusion of complete coverage. Search results, social feeds, and review sites are curated environments. Missing evidence may reflect the platform and query method rather than absence in the market. A common failure is copying visible competitor language into a market summary and calling it buyer research. The output describes how vendors position themselves, while saying little about buyer priorities or actual behavior. Another failure is using search volume as a direct estimate of market size. Separate vendor claims, buyer evidence, behavioral data, and market estimates into distinct source groups. Add interviews, surveys, or sales evidence where public material cannot answer the question, and narrow conclusions to what the sources support. --- # Online Market Research Process | Surface Glossary URL: https://surface.thesurface.network/glossary/online-market-research-process The online market research process is a structured way to collect and analyze market evidence through internet-based sources and methods. It can use digital surveys, remote interviews, online communities, search data, reviews, websites, public databases, social material, product analytics, pricing pages, documentation, and other dated online records. Online describes where evidence is found or collected, not whether it is representative or reliable. Search results favor visible and optimized sources. Review sites attract particular contributors. Website copy reflects a company's claims. Remote panels depend on recruitment and incentives. Each source needs a role and limitation inside the study. Begin with a decision and an evidence plan. Choose sources because they can answer a named question, record how and when they were collected, and validate important claims across methods where possible. Preserve raw material and search conditions so another researcher can understand what the online environment exposed at that time. 1. Define the decision, market, population, period, and claims the research should support. Rank the uncertainties by consequence. 2. Select online methods and sources. Match interviews, surveys, search behavior, public data, review analysis, website research, or product analytics to each question. 3. Create a collection protocol. Record queries, platforms, filters, dates, locations, device or account conditions, recruitment, incentives, and source inclusion rules. 4. Validate and analyze. Check identity, date, definition, sample bias, duplicates, conflicting sources, and whether the evidence supports observation, explanation, estimate, or causal claim. 5. Report the decision and preserve the record. Link findings to sources, state limitations, assign actions, and schedule review for facts likely to change. Quality measures include coverage of the intended population, source freshness, traceability, duplicate rate, sample completion, confidence, and consistency between independent sources. For ongoing monitoring, track changes in collection conditions because a platform redesign, search algorithm, API limit, or review policy may alter the observed data without a market change. Maintain a digital source log with URL or platform, publisher, publication and access dates, query or filter, geographic context, evidence type, claim supported, and known incentive. Screenshots or archived copies can help with volatile pages where terms permit. For participant research, retain the screener, consent, field dates, and instrument version. Separate observed online behavior from interpretation. Search volume can indicate recorded query demand; it does not reveal every reason behind it. Review frequency describes contributors to that platform; it does not establish category market share. When combining sources, explain what each contributes and where their populations differ. - Which decision and population determine the online research scope? - Which digital source can support each intended claim? - How will the team account for platform, publication, and recruitment bias? - Which volatile evidence needs an archive or review date? - Who will resolve conflicting sources and approve interpretation? Online research can move quickly, so set a stopping rule. Define enough coverage to act and the gaps that would block action. Without one, researchers can keep opening sources indefinitely or stop at the first page that confirms the prevailing opinion. A common failure is treating the top search results as a sample of the market. Researchers summarize highly visible articles, vendor lists, and review pages, then describe the result as buyer consensus. Repeated claims often trace back to one source, publication dates disappear, and quiet market segments remain invisible. Rebuild the source map around the population and claim. Trace repeated statements to their origin, add less visible primary evidence, recruit missing participants, and narrow conclusions that cannot be generalized. Keep the collection protocol so later changes can be compared under similar conditions. Repeat a small portion of the collection through a different route. Compare search results with public records, platform reviews with interviews, or self-reported behavior with analytics. The purpose is to find where the online source systematically overrepresents a group or incentive. Add that bias to the study record and adjust the conclusion accordingly. Save enough of the alternate collection for a reviewer to reproduce the comparison and challenge the adjustment. --- # Online Marketing Research | Surface Glossary URL: https://surface.thesurface.network/glossary/online-marketing-research Online marketing research is research conducted through digital sources and interactions to inform marketing decisions. It can include online surveys, remote interviews, digital communities, social listening, search analysis, website behavior, ad experiments, review mining, competitor monitoring, and analysis of CRM or product data. The phrase describes the research environment, while the business question still determines the method. Digital access can make recruitment and collection faster. It can also narrow the sample toward people who use a particular platform, agree to tracking, or respond to an online invitation. Teams use it to study audience language, category awareness, content demand, message response, channel behavior, conversion friction, competitor claims, and changes in buyer interest. Behavioral data shows what people did within the measured system. Surveys and interviews explain reported needs and reasoning. Public digital sources add market context. These sources should inform one another without being treated as equivalent. A search trend, sales note, click, and interview statement each carries a different kind of evidence. Define the population, question, and decision before choosing a tool. Record recruitment source, consent, observation period, exclusions, and platform limits. Preserve source material beside classifications or summaries. Check whether bots, duplicate respondents, cookies, attribution rules, or algorithmic feeds distort the result. Use offline or direct methods when the relevant population is hard to reach online or when the decision depends on context that digital traces cannot capture. A company wants to revise messaging for procurement leaders. It analyzes search questions and review language, interviews eight buyers remotely, surveys a larger screened panel, and tests two landing-page messages. Search data reveals vocabulary, interviews explain approval concerns, the survey estimates prevalence, and the experiment measures behavior. The company keeps the four sources separate in the report so one channel does not impersonate the whole market. Keep URLs, screenshots, query terms, platform settings, timestamps, exports, and recruitment sources with the analysis. Digital environments change quickly, and an analyst should be able to reconstruct what the team observed. When a platform provides modeled or sampled data, label it. A clean dashboard can still contain estimates whose coverage differs from the market the decision concerns. --- # Organization Schema Markup | Surface Glossary URL: https://surface.thesurface.network/glossary/organization-schema-markup Organization schema markup is structured data that identifies a company, nonprofit, institution, or other organization and describes stable public facts about it. Common properties include name, URL, logo, legal name, address, contact information, founding date, and verified profile links. The organization node often acts as an anchor for the rest of a site's entity graph. Articles can reference it as publisher, products can reference it as brand or manufacturer, and locations can connect to the parent organization. A stable @id keeps those references pointed at the same entity. Consistent Organization markup helps search systems separate the company from similarly named entities and understand which pages, products, authors, and profiles belong together. It also exposes internal inconsistency. If marketing, legal, recruiting, and product pages use different names or logos, the structured data implementation has no reliable fact to publish. Create the main node on an authoritative company page and reuse its identifier elsewhere. Include only maintained, relevant facts. Keep the canonical URL and logo stable, distinguish the public brand name from legalName when necessary, and review sameAs links before treating them as verified identity signals. Teams can make Organization schema markup easier to maintain by treating it as a data contract. Name the object, its stable identifier, its permitted properties, and the source responsible for each value. Keep the source beside the result and make changes reversible. This protects the operation when a definition, vendor, model, template, or buyer behavior changes after the original decision. The final review should ask what changed for a buyer or operator. If Organization schema markup only creates another field, page, prompt, or dashboard, its role remains incomplete. A consulting firm operates under the name Alder but is registered as Alder Research Group LLC. Its Organization markup uses Alder as name, the legal entity as legalName, the canonical homepage as url, and a stable logo asset. Every article references the same organization @id as publisher. A redesign updates the logo source once rather than changing dozens of independent nodes. Organization schema is closer to a maintained identity record than a company biography. It should favor stable facts and connections over promotional copy. --- # Podcast Structured Data | Surface Glossary URL: https://surface.thesurface.network/glossary/podcast-structured-data Podcast structured data is schema markup that identifies a podcast and its episodes for machines. A site may use types such as PodcastSeries, PodcastEpisode, AudioObject, Person, and Organization to describe the show, episode title, publication date, audio file, duration, host, guest, and publisher. The markup should mirror a real episode page and feed. Search platforms differ in the podcast features and schema properties they support, so teams should avoid promising a special presentation. The basic value is a consistent entity model that connects the series, episode, people, media, transcript, and canonical URL. Podcast pages often scatter important facts across an embedded player, show notes, transcript, image, and RSS feed. Structured data can make those relationships explicit. It also reveals when the website and feed disagree about titles, dates, episode numbers, or audio URLs. Create a stable identifier for the series, connect each episode to it, and generate values from the same source that publishes the feed. Include visible and maintained facts, ensure audio and image URLs are crawlable where appropriate, and update markup when an episode is corrected or removed. Teams can make podcast structured data easier to maintain by treating it as a data contract. Name the object, its stable identifier, its permitted properties, and the source responsible for each value. Choose a measure that follows the actual job. Validity, coverage, reviewer effort, conversion, response time, source quality, and revenue can describe different outcomes and should stay separate. A short decision record should state the current approach, evidence, owner, date, and condition for revision. That makes podcast structured data useful beyond the person who first implemented it. An episode page lists the title, host, guest, release date, duration, audio player, transcript, and show notes. Its JSON-LD describes one PodcastEpisode, links it to the PodcastSeries, identifies the Organization as publisher, and points to the same canonical audio asset used in the RSS feed. Podcast schema should reconcile the publishing system. A large block of markup cannot repair an inaccessible audio file, missing transcript, duplicate episode page, or feed that uses different identifiers. --- # Primary and Secondary Market Research | Surface Glossary URL: https://surface.thesurface.network/glossary/primary-and-secondary-market-research Primary and secondary market research form two evidence streams. Secondary work examines material that already exists. Primary work collects evidence for the current study. The value of the distinction is practical: it tells a team what can be learned from available sources, which gaps justify new collection, and where the two streams can corroborate or challenge one another. Existing internal records count as secondary when they were created before the current project. A new analysis does not change their origin. Start with a structured source scan. Establish definitions, market boundaries, historical context, known estimates, and the claims other organizations repeat. Trace important numbers to their original method. Build a gap map that lists what remains unknown, outdated, poorly matched, or inaccessible. Design primary work only for consequential gaps. Interviews can explain a buying process that public sources miss. A screened survey can estimate a pattern in a specific segment. Observation or an experiment can test behavior that published opinions cannot settle. The sequence limits unnecessary collection and makes instruments better informed. Use secondary evidence when credible sources match the population, date, definition, and decision closely enough. Invest in primary collection when company-specific language, current intent, decision roles, concept response, or cause matters. Consequential choices often need both. Reconcile disagreements instead of averaging them automatically. The conflict may come from different category boundaries, samples, dates, or incentives. A company evaluating a new country reviews establishment counts, regulatory material, competitor offers, and its international pipeline. The work defines an eligible segment and exposes an unanswered question about local procurement. Interviews with buyers and partners map the process. A survey then estimates how often the identified requirements appear. Secondary evidence frames the opportunity, while primary evidence resolves the decision-specific gap. For primary research, review recruitment, instrument design, missing responses, interviewer effects, and whether the sample covers the intended population. For secondary research, review authorship, incentive, method, definitions, date, and whether the source can be reproduced. In both cases, preserve contrary evidence and avoid false precision. The label primary or secondary says where evidence originated, not whether it is automatically trustworthy. --- # Primary Market Research Methods | Surface Glossary URL: https://surface.thesurface.network/glossary/primary-market-research Primary market research is the collection of original evidence for a specific question. Researchers gather it directly through interviews, surveys, observation, experiments, usability sessions, customer panels, diary studies, or other methods involving the target population or behavior. Secondary research analyzes material that already exists. Primary research gives a company control over the question and sample, but it also creates responsibility for recruitment, consent, instrument design, interviewer influence, analysis, and privacy. The method can uncover language and constraints that public market summaries miss. It can also test how common a pattern is when the sampling and survey design support that claim. The evidence should remain matched to the method. Interview themes are not population percentages. Define the decision, participant criteria, sample, method, questions, analysis plan, and limits before recruiting. Preserve raw notes and metadata, code themes transparently, and report contradictory cases. Combine the results with secondary evidence when the decision also depends on market size or competitor facts. Use primary market research to support one named decision. Record the population, market boundary, source type, collection date, method, and limitations so a later reader can judge whether the evidence still applies. Choose a measure that follows the actual job. Validity, coverage, reviewer effort, conversion, response time, source quality, and revenue can describe different outcomes and should stay separate. A short decision record should state the current approach, evidence, owner, date, and condition for revision. That makes primary market research useful beyond the person who first implemented it. A product team interviews churned customers to understand implementation failure, then surveys a larger qualified sample using themes from the interviews. The interviews reveal the sequence and language of the problem. The survey estimates how frequently those conditions appear in the selected population. Primary research is useful when the company needs an answer tailored to its decision and can reach the people with relevant experience. Its authority comes from method and scope, not from being collected firsthand. --- # Primary Market Research | Surface Glossary URL: https://surface.thesurface.network/glossary/primary-market-research-in-business Primary market research in business is research a company commissions or conducts to collect new evidence directly from the people, organizations, or behavior relevant to a decision. Interviews, surveys, observation, usability studies, customer panels, diary studies, and experiments are common methods. The work differs from secondary research, which analyzes evidence that already exists, such as industry reports, public filings, search data, reviews, or prior studies. Primary research can answer a question specific to the company, but the result depends heavily on sampling, question design, incentives, interviewer behavior, and analysis. Begin with the decision the research should change. Translate that decision into questions the chosen participants can answer from experience, then define the population and recruitment criteria. Use a method suited to the claim, preserve source notes, and state the limits before the findings reach a strategy deck. 1. Define the business decision and the uncertainty around it. A team choosing a segment needs different evidence from a team improving onboarding or testing a price message. 2. Specify the target population, screening rules, sample, and recruitment channel. Existing customers may explain current use while excluded prospects reveal barriers the product team rarely hears. 3. Choose the method and write a neutral instrument. Interviews explore language and sequence, surveys estimate distribution, observation reveals behavior, and experiments compare response under controlled conditions. 4. Collect evidence consistently and preserve context. Record dates, participant characteristics, question versions, consent, raw responses, and interviewer notes so themes can be traced back to real material. 5. Analyze against the original decision, report contradictory cases, and separate observed findings from interpretation. Recommend the next action and the evidence that would reverse it. Research quality is better judged through sample fit, completion, response quality, source traceability, consistency of coding, and relevance to the decision than through participant count alone. A small interview study can be useful when the claim stays qualitative. A percentage estimate needs a defensible sampling and survey design. The operating discipline for primary market research is a chain from question to source to interpretation to decision. Preserve interview notes, survey instruments, queries, public records, and dated product evidence with enough context to audit the conclusion. Add a confidence statement and the observation that would reverse the recommendation. This avoids the familiar research failure where a clean slide outlives the evidence and continues to guide positioning after the market has changed. Keep the smallest useful scope for primary market research until the operation has evidence to expand. Limit templates, segments, permissions, channels, or actions at first. Review errors and manual work, then add scope deliberately. This makes ownership and rollback practical and gives the team a baseline against which a broader version can be judged. The final artifact should show the current decision, the evidence behind it, and the condition that forces reconsideration. That is what makes primary market research maintainable after the original operator moves to another project. Retirement belongs in the operating plan for primary market research too. Define the signal that shows the process no longer serves its original audience, system, category, or decision. Archive the configuration and evidence, stop new entries safely, preserve required history, and update dependent reports or links. Unused processes create risk when they remain active simply because no one owns turning them off. Record where primary market research remains uncertain and when that uncertainty becomes material. This gives the next operator a starting point instead of forcing another full audit. - Which decision will change if the research produces a clear answer? - Which population has direct experience with the question? - Which method can support the intended type of claim? - How will incentives, consent, privacy, and recording be handled? - Who will review themes, outliers, and the final interpretation? The organization should decide in advance how much evidence is enough to act. Otherwise, leaders may demand more research when findings challenge a favored plan and accept a thin sample when the findings confirm it. A common failure is recruiting the easiest people and describing them as the market. Loyal customers, newsletter readers, or the sales team's favorite accounts may offer useful stories while excluding lost deals, noncustomers, and buyers with different constraints. Leading questions can then turn the study into a search for approval. Reframe the claim around the sample actually studied, recruit missing perspectives, and review the instrument for assumptions built into the wording. Pair the primary work with secondary evidence where size, trend, or competitor context matters. --- # Business Research Methods Process | Surface Glossary URL: https://surface.thesurface.network/glossary/process-of-business-research-methods The business research methods process is the sequence used to turn a business uncertainty into evidence that can support a decision. It covers problem definition, existing evidence, method and sample selection, collection, analysis, interpretation, recommendation, and later review. The method should follow the claim the team needs to make. Business research can use interviews, surveys, observation, experiments, public records, product data, sales evidence, market databases, or combinations of them. Each source answers a different kind of question. Interviews can explain experiences and language; a well-designed survey can estimate distribution in a defined population; behavioral data shows recorded actions without explaining every motive. Begin with the decision, the current belief, and the consequence of being wrong. Translate that uncertainty into answerable research questions, then select participants, sources, and methods that can support the intended conclusion. Keep observations, estimates, and interpretation separate through the final recommendation. 1. Define the decision and scope. State who will act, what choice is open, the deadline, the market boundary, and the evidence that would change the current plan. 2. Review what is already known. Audit internal data, prior studies, customer material, public sources, and important gaps before commissioning new collection. 3. Choose a research design. Match the method to the question, define the population and sample, write inclusion rules, and plan how conflicting evidence will be handled. 4. Collect and document evidence. Preserve source dates, instruments, notes, consent, field conditions, transformations, and the context needed to trace a finding back to its origin. 5. Analyze, challenge, and apply. Test alternate explanations, report contradictory cases, state limitations, recommend an action, and name the signal that would justify another study. Process quality depends on source fit, sample fit, completion, traceability, consistency, and usefulness to the decision. A large response count cannot repair biased recruitment or a question that measures the wrong construct. Track recontact, exclusion, missing-data, and disagreement rates where they expose weakness in the design. Keep a decision brief beside the source archive. It should show the research question, population, method, dates, evidence categories, analytical choices, limitations, confidence, and recommendation. Give every material claim a route back to notes, records, or calculations. When the work combines qualitative and quantitative evidence, explain how each influenced the conclusion instead of blending them into one vague statement of certainty. Assign one owner to the research decision and another reviewer who can challenge the method. The reviewer should look for convenient samples, leading wording, missing alternatives, and conclusions broader than the evidence. Record changes to the instrument or sample while fieldwork is active. If an early finding changes recruitment, preserve both versions and explain the effect. - Which business choice will the research support, and what happens if the team delays it? - Which population or evidence source has direct knowledge of the question? - What type of claim must the method support: explanation, estimate, comparison, or causal effect? - How much uncertainty is acceptable for this decision? - Who owns data protection, interpretation, approval, and the follow-up action? Set the action threshold before results arrive. Otherwise a preferred plan may survive unfavorable evidence through demands for one more study, while supportive evidence receives little scrutiny. The threshold can be practical rather than statistical, but it should state how confidence, cost, reversibility, and downside shape the decision. A common failure is choosing the method first. Someone asks for a survey because surveys look measurable, then the team writes questions around a decision it has not defined. The resulting percentages describe a convenience sample and answer several interesting side questions while leaving the actual choice unresolved. Another version begins with interviews and turns repeated stories into claims about prevalence. Return to the decision and rewrite the claim at the level the evidence can support. Add a method only where it closes a named gap. If the sample cannot be repaired, narrow the conclusion and document what remains unknown. A modest, honest result is more useful than a broad finding assembled from incompatible evidence. --- # Prompt Engineering for LLMs | Surface Glossary URL: https://surface.thesurface.network/glossary/prompt-engineering-for-llms Glossary · AI Search & Prompting The practice of writing inputs that get reliable, useful output from large language models — and why it now shapes how brands get found. [Back to glossary →](https://www.withsurface.com/glossary) On this page - [01What is prompt engineering?](#what-is-prompt-engineering) - [02Common techniques](#common-techniques) - [03Why it matters for marketing](#why-it-matters-for-marketing) Prompt engineering is the practice of designing the text you send to a large language model (LLM) so it returns the output you actually want. It spans the wording of a single question, the examples you include, the role and constraints you set, and how you chain several calls together. Because LLMs respond to patterns in their input, small changes — an explicit format, a worked example, a clear constraint — often move quality more than a bigger model would. - **Instruction clarity** — state the task, the audience, and the output format explicitly instead of hoping the model infers them. - **Few-shot examples** — show one or two examples of the input→output you want; the model matches the pattern. - **Role and context** — tell the model who it is and what it knows ("You are a GTM analyst…") to steer tone and depth. - **Constraints** — bound length, format, and what it must not do; ambiguity is where models drift. - **Chaining** — break a hard task into steps (draft → critique → revise) rather than asking for everything at once. LLMs are now a discovery surface. Buyers ask ChatGPT and Claude "what tool does X?" and the model answers from what it has read. Understanding how prompts surface and cite sources is the foundation of [AI search visibility](https://www.withsurface.com/ai-search-visibility) — the emerging discipline of earning a mention when a model, not a search engine, is doing the recommending. Surface's [AI Workforce](https://www.withsurface.com/product/ai-workforce) puts these techniques to work across your GTM motion. Related terms [TermBrand Marketing ResearchBrand marketing research studies awareness, associations, meaning, preference, trust, differentiation, and response to brand choices among defined audiences.Read definition](https://www.withsurface.com/glossary/brand-marketing-research)[TermGoal of Market ResearchThe goal of market research is to reduce decision uncertainty with credible evidence about a market, buyer, alternative, offer, or outcome.Read definition](https://www.withsurface.com/glossary/goal-of-market-research)[TermMarketing Research QuestionsMarketing research questions translate a business decision into specific questions that evidence can answer about markets, buyers, messages, channels, and outcomes.Read definition](https://www.withsurface.com/glossary/marketing-research-questions) Set up once ## See what Surface can do for your team. [Get a walkthrough](https://www.withsurface.com/book-a-demo) --- # Prompt Engineering Framework | Surface Glossary URL: https://surface.thesurface.network/glossary/prompt-engineering-framework A prompt engineering framework is a repeatable way to design and review prompts. Useful frameworks separate the goal, audience, source context, instructions, constraints, examples, output format, and evaluation criteria so teams can see which part of the system needs work. Frameworks are planning aids rather than magic acronyms. Their value comes from making implicit decisions visible. A strong structure can reveal that the team has no approved source, cannot define a correct answer, or expects one prompt to research, decide, write, fact-check, publish, and measure a campaign in a single pass. A shared framework makes prompt reviews faster and reduces personal prompt folklore. Teammates can compare two versions against the same task and test set. It also creates a clearer boundary between prompt text and the other system components, including retrieval, tools, permissions, model settings, and human approvals. Use a compact sequence: define the job, provide the evidence, state the decision rules, specify the deliverable, and name the evaluation. Add examples when they clarify a real boundary. Add tools when the task needs current data or action. Keep the prompt version next to its tests and change log. Put a prompt engineering framework under the same change discipline as other business logic. The owner should know the prompt version, data sources, model, tools, expected behavior, and the consequences of an incorrect output. Choose a measure that follows the actual job. Validity, coverage, reviewer effort, conversion, response time, source quality, and revenue can describe different outcomes and should stay separate. A short decision record should state the current approach, evidence, owner, date, and condition for revision. That makes a prompt engineering framework useful beyond the person who first implemented it. A research agent must summarize a prospect before a sales call. The framework records the goal, approved sources, recency window, required fields, unsupported-claim rule, output schema, and five scored test accounts. When the company adds a new market segment, the owner updates the source and evaluation sections instead of appending a vague line that says to be more strategic. The framework should help a reviewer answer three questions: what job is this prompt doing, which evidence may it use, and how will we know when it fails? If those answers remain unclear, more prompt wording will not stabilize the workflow. --- # Prompt Evaluation | Surface Glossary URL: https://surface.thesurface.network/glossary/prompt-evaluation Prompt evaluation is the process of testing a prompt against defined examples and scoring the resulting behavior. Depending on the task, an evaluation may measure factual support, classification accuracy, field extraction, instruction adherence, source coverage, format validity, escalation, tone, latency, cost, or reviewer effort. A prompt is only one part of the evaluated system. Results can change when the model, retrieved context, tools, data schema, examples, settings, or business definitions change. Production evaluation should record those versions so the team can distinguish a prompt improvement from a different model or source. Without evaluation, prompt editing becomes anecdotal. A reviewer fixes the last bad output and may break earlier cases. A stable test set reveals tradeoffs and regression. It also helps teams decide whether a model is ready to draft, recommend, or act within a real workflow. Build representative and adversarial cases from real work, define scoring before seeing the new result, and separate development examples from held-out tests. Combine deterministic checks with human review where judgment matters. Re-run the suite after material changes and monitor production exceptions that the test set missed. Use prompt evaluation inside a defined task rather than as an isolated piece of prose. Save the input, approved context, desired output, model, and test cases beside the prompt so later edits can be compared. Set an explicit review trigger rather than relying on memory. A product launch, schema change, prompt revision, new data source, campaign shift, or sales objection may justify a fresh check. The practical test for prompt evaluation is whether it improves a real decision without creating hidden definitions, unsupported confidence, or an unowned handoff to another team. A prompt extracts campaign name, channel, budget, date range, and owner from briefs. The evaluation contains normal briefs, missing fields, conflicting budgets, several date formats, and text that asks the model to ignore the schema. Automated checks score valid JSON and exact fields, while reviewers inspect whether uncertain values correctly return null. The evaluation should resemble the consequences of the job. A polished response is irrelevant if the workflow needs an exact field, an evidence link, or a safe refusal. --- # Prompt Testing | Surface Glossary URL: https://surface.thesurface.network/glossary/prompt-testing Prompt testing is the practice of running a prompt and its surrounding model workflow against a defined set of cases to see whether it behaves as intended. Tests may check accuracy, source use, format, safety, escalation, tone, latency, cost, tool selection, or reviewer effort. Testing differs from trying a few examples in a chat window. A useful test set is repeatable, includes difficult and ordinary cases, and records the model, prompt, retrieved context, tools, settings, and expected behavior. Production monitoring adds cases the original suite failed to anticipate. Prompts can regress when someone fixes the latest complaint, changes a source, adds an example, or moves to another model. Testing makes tradeoffs visible and gives teams a basis for rollback. It is especially important when the workflow changes records, publishes claims, or contacts customers. Create cases from real work, keep some held out from prompt development, define scoring before comparing versions, and use deterministic checks where possible. Add human review for meaning and judgment. Run the suite after prompt, model, tool, schema, or business-rule changes. The working unit for prompt testing is a prompt system with evidence and evaluation. Record what the model may use, what it must return, and which cases should lead to uncertainty or escalation. Review a sample of real cases before relying on an aggregate score. The sample should include incomplete, conflicting, and high-value records because averages often hide the failures with the largest business cost. Place the documentation for prompt testing beside the workflow or decision it affects. That keeps definitions, evidence, ownership, and later corrections available to the people who need them. A routing assistant maps free-text product requests to four queues. The suite includes direct requests, mixed products, misspellings, missing context, existing named accounts, and attempts to instruct the assistant to ignore routing rules. The team scores queue accuracy, uncertainty, and correct escalation rather than prose quality. A test should reflect the cost of being wrong. The more authority a prompt has, the more the suite needs exceptions, unauthorized requests, stale data, and recovery behavior. --- # Prompt Tuning | Surface Glossary URL: https://surface.thesurface.network/glossary/prompt-tuning Prompt tuning has two common meanings. In everyday product work, people use it to mean revising prompt wording, context, examples, and output rules to improve results. In machine learning research, soft prompt tuning is a parameter-efficient training method that learns continuous prompt vectors while leaving most or all model weights unchanged. The distinction matters because the resources and governance differ. Editing a text prompt can happen through a versioned evaluation workflow. Soft prompt tuning requires a training dataset, optimization process, model access, validation, and deployment support. It is closer to model adaptation than ordinary prompt writing. Teams that use the label loosely may prescribe an expensive method for a problem caused by missing data or unclear instructions. A prompt revision helps when the task or format is ambiguous. Retrieval helps when facts are missing. A trained adaptation may help when repeated behavior cannot be achieved reliably through context and examples alone. Define the failure, establish a test set, and try the least invasive change that addresses it. Revise task wording, separate stages, improve sources, adjust examples, or add deterministic validation before training anything. If soft prompt tuning is justified, preserve a base-model comparison and evaluate on held-out and safety cases. Put prompt tuning under the same change discipline as other business logic. The owner should know the prompt version, data sources, model, tools, expected behavior, and the consequences of an incorrect output. Review a sample of real cases before relying on an aggregate score. The sample should include incomplete, conflicting, and high-value records because averages often hide the failures with the largest business cost. Place the documentation for prompt tuning beside the workflow or decision it affects. That keeps definitions, evidence, ownership, and later corrections available to the people who need them. A classifier confuses two lead segments. The team first clarifies the definitions and adds boundary examples, which resolves most errors. Remaining failures reflect highly specialized language across thousands of records. Only then does the team consider a trained adaptation, with a separate test set and rollback to the text-prompt version. Ask what is being tuned before discussing prompt tuning. Text prompt iteration and learned soft prompts solve different problems and carry different costs. --- # Prompt Writing | Surface Glossary URL: https://surface.thesurface.network/glossary/prompt-writing Prompt writing is the practice of composing instructions and context for a language model or other generative system. A useful prompt states the job to perform, supplies the relevant input, names important constraints, and defines an output that a person or system can judge. Good prompt writing resembles a compact work brief. It cannot compensate for missing source material, unclear business definitions, or a task that no one has decided how to evaluate. The prompt is one component of a larger system that may also include retrieval, tools, examples, permissions, human review, and downstream automation. Start with the decision or artifact the output must support. Then separate durable instructions from request-specific material, give the model only the context it needs, and define what a successful answer contains. Test the prompt against ordinary cases, incomplete inputs, and cases where the correct response is to ask for information or refuse an unsupported claim. 1. Write the task as an observable action, such as classify these leads, extract these fields, or draft three campaign concepts from the attached brief. Avoid broad verbs that hide several jobs. 2. Supply source context and label it clearly. Distinguish facts the model may use from examples that show form, and state when the model should avoid filling a gap with a guess. 3. Set constraints that matter to the workflow. Name the audience, allowed sources, tone, length, fields, decision rules, and any action that requires human approval. 4. Define the output shape. A human-facing draft may need headings and links, while a system handoff may need valid JSON with fixed keys and explicit null values. 5. Evaluate several representative outputs and revise one variable at a time. Save the prompt version, test cases, and scoring notes so an improvement can be reproduced. Measure the behavior that matters for the task: factual support, field accuracy, instruction adherence, useful coverage, formatting validity, escalation behavior, latency, or reviewer effort. A prompt that sounds polished can still fail if it omits a required source, invents a value, or produces output another system cannot parse. For prompt writing, preserve a runnable test packet rather than a polished prompt alone. The packet should include normal cases, missing evidence, conflicting sources, an attempted instruction override, an unauthorized request, and a case where escalation is the correct result. Record the model, prompt, retrieval source, tool definitions, output schema, and scoring rubric for every comparison. When a new version improves one metric, inspect whether it increased unsupported claims, review time, latency, or failure on a different segment. Use separate measures for the correctness, reliability, efficiency, and business value of prompt writing. A process can be accurate on completed cases and still fail through delays or missing coverage. It can be reliable and still create little value. Report denominators, exclusions, time windows, and unresolved cases so leaders can see which part of the system actually improved. Review the process with the team that receives its output. Their acceptance, corrections, and workarounds reveal whether prompt writing functions in the real operating environment rather than only inside its source tool. Give the team receiving output from prompt writing a visible way to accept, correct, reject, or escalate it. Their response should return to the shared record with a reason and timestamp. Review those reasons by workflow version and segment. This feedback shows whether prompt writing is reducing work, moving the right cases, and preserving enough context for the next person to act. End the prompt writing review with open questions and their owners. An unresolved item can remain open, but it should not disappear into an apparently final configuration. - Identify which instructions stay fixed and which context changes with each request. - Choose the approved sources and the behavior for missing or conflicting evidence. - Define what the model may draft, recommend, approve, or execute. - Create a test set that includes edge cases and known failure patterns. - Assign an owner for prompt versions, evaluations, and change history. When a prompt becomes part of a recurring business process, treat it as versioned operational logic. A copy stored in someone's chat history is difficult to audit, compare, or roll back. The prompt, model, tools, data sources, and evaluation set should change under a visible process. The common failure is adding instructions whenever an output disappoints someone. The prompt becomes a long pile of exceptions with conflicting priorities and no test set. Results may improve for the last example while getting worse for earlier cases. Another failure is asking the model to infer company policy from a handful of stylistic examples. Return to the task definition, split compound jobs into stages, and score a small representative set before editing. Remove rules that do not change the result, move factual context into maintained sources, and add explicit escalation where the model lacks enough evidence. --- # Proven Lead Generation Strategies | Surface Glossary URL: https://surface.thesurface.network/glossary/proven-lead-generation-strategies Proven lead generation strategies are approaches that have repeatedly created qualified buyer responses under documented conditions. Common strategies include high-intent search, expert content, referrals, partner programs, events, targeted outbound, account programs, product-led trials, paid demand capture, tools, assessments, and customer advocacy. Their effectiveness depends on audience, category, offer, economics, and follow-up. "Proven" should describe evidence, not a universal promise. A channel that works for a low-cost self-service product may fail in an enterprise market where trust, implementation, and buying groups shape the decision. A credible strategy states the segment, message, offer, channel, capture method, qualification rule, response process, observation window, cost, and downstream outcome. It survives more than one campaign and produces results that remain useful after obvious outliers are removed. Evidence should include accepted leads, meetings, opportunities, revenue, time, and disqualification alongside clicks or submissions. Start with places where the audience already expresses a problem or seeks help. Match the offer to the intent and give the buyer a clear next step. Connect capture to identity, enrichment, routing, and timely response. Test one material assumption at a time when possible. Compare cohorts under the same definitions. Document where the strategy fails. Limits help another team know whether it can apply the result. A compliance company finds that generic ebook campaigns create inexpensive downloads and little pipeline. Small expert workshops for a narrow regulated segment create fewer responses but more opportunities. The team repeats the format across three topics, keeps qualification and cost definitions stable, and measures six months of pipeline. The workshop becomes a proven strategy for that segment. The company does not claim the same method will work for every audience or product. Repeat a successful program before calling it proven. Compare at least several cohorts, note material market or product changes, and document the conditions under which performance weakened. Look for survivorship and attribution bias. A strategy may receive credit because it touches most deals rather than because it changes them. Use experiments or credible comparisons where feasible, then retain honest limits in the playbook. --- # Quality Lead Generation | Surface Glossary URL: https://surface.thesurface.network/glossary/quality-lead-generation Quality lead generation is the creation and capture of identifiable buyer interest that can support an appropriate next action. Lead quality usually depends on fit, need, intent, authority or influence, timing, contactability, consent, and the context behind the response. The exact definition should reflect the company's market and sales motion. A high-quality lead does not need to be ready for a sales call. It needs to be real, relevant, and handled according to what the signal means. An early researcher at a target account may belong in nurture rather than an immediate outbound sequence. Lead volume can rise when forms become easier, targeting becomes broader, or incentives attract people who want the asset more than the product. Sales then spends time sorting records, response slows, and marketing loses trust in its own reporting. Tightening every gate can create the opposite problem by excluding legitimate buying-group members. Quality gives teams a shared way to balance access, qualification, and service. Define quality by downstream evidence such as accepted handoffs, productive conversations, opportunities, revenue, and disqualification reasons. Improve audience selection, offer clarity, form design, enrichment, identity matching, scoring, and routing together. Preserve the original action and page context so qualification does not rely only on a job title or company size. Review false positives and false negatives. A rule that removes bad records may also hide future buyers. A report campaign produces 600 downloads and 12 opportunities. Analysis shows that the strongest signals were target-account fit, repeat visits, and a pricing-page view within seven days. The team keeps the report open, asks fewer form questions, and uses behavior plus account context for follow-up. Sales receives fewer immediate tasks, while nurture retains promising researchers whose timing is earlier. Quality improves because action matches the evidence. B2B quality may exist at the account level even when one person lacks authority. A practitioner can reveal an urgent problem, an executive can own budget, and procurement can control the path. Track person fit and account fit separately. Preserve relationships among contacts so scoring does not discard useful researchers or treat several people from one account as unrelated lead volume. --- # Real-Time Market Research | Surface Glossary URL: https://surface.thesurface.network/glossary/real-time-market-research Real-time market research is the collection and analysis of current market signals with enough speed to affect an active decision. Sources may include search behavior, website activity, pricing changes, product releases, reviews, social discussion, sales conversations, surveys, transactions, customer support, and public data feeds. The label describes the decision speed, not a guarantee that every source updates instantly. Teams use this approach during launches, pricing changes, events, crises, fast-moving categories, or experiments where a monthly report would arrive too late. It can detect a change, show where attention is moving, reveal a new buyer question, or identify a campaign problem early. It is strongest for monitoring defined signals and triggering investigation. It is weaker at explaining cause without deeper analysis. Fast data also contains noise. Platform algorithms, bots, news cycles, tracking outages, and small samples can produce movement that does not represent the market. Define the signal, population, source, update frequency, baseline, threshold, and action before monitoring begins. Preserve timestamps and raw evidence. Distinguish alerts from conclusions. Require human review for ambiguous or consequential changes. Compare several sources when one platform could distort the result. Record which decisions can wait for stronger evidence. Speed should match consequence. A bid adjustment may tolerate an automated threshold, while a category repositioning decision needs a broader study. A software company launches a new integration. Search questions and site behavior show strong interest, but support chats reveal confusion about compatibility. The team updates the page and onboarding message within a day. It does not declare a new market trend. After two weeks, interviews and product usage confirm that compatibility was the main barrier. Real-time signals prompted the right question, and slower research established the explanation. An alert should state the signal, threshold, comparison, source, and owner. It should also name the next investigation or action. Avoid notifying several teams about every small movement. Use persistence, volume, or cross-source confirmation to reduce noise. Review false alarms and missed events. If no one acts on an alert, change its threshold, route, or existence rather than adding it to a dashboard. --- # Real-Time Marketing Automation | Surface Glossary URL: https://surface.thesurface.network/glossary/real-time-marketing-automation Real-time marketing automation is event-driven software that evaluates a current signal and takes an approved marketing or operational action within a defined latency. A page request, product event, form submission, account change, conversation, purchase, or consent update can trigger the evaluation. "Real time" may mean milliseconds, seconds, or minutes depending on the customer need and system design. The timing promise should match the job. Personalizing a page may require a response during the session, while routing a demo request may allow several seconds. A renewal reminder gains little from millisecond execution. Faster action also gives systems less time to reconcile identity and context, so high-consequence workflows need safe defaults and review paths. ## Why timing and context matter A timely message can help someone complete a task or receive a fast answer. The same system can repeat an offer after purchase, expose an inferred attribute, or contact a person who just changed consent. Event order, duplicate delivery, stale profiles, missing account matches, and several simultaneous workflows can all create incorrect treatment even when each rule appears sound. Define the event contract, identity, eligibility, current-state lookup, decision rule, action, latency target, deduplication window, suppression, timeout, retry, and fallback. Decide which fields may be read or written and which system has authority. Preserve the event, rule version, decision, action, and outcome for diagnosis. Test late and out-of-order events rather than assuming every signal arrives once. Use it when delay materially changes the customer or operating outcome, such as session guidance, high-intent routing, fraud-sensitive suppression, or immediate confirmation. Use scheduled or batch processing when the decision benefits from fuller data and timing is less sensitive. Monitor latency percentiles, action success, duplicate action, false eligibility, suppression, fallback, and downstream customer outcomes. A qualified buyer submits an enterprise pricing request. The event service checks consent, existing account ownership, open opportunities, territory, and rep availability. Within seconds it confirms the request and offers an appropriate scheduling option. If identity or ownership is uncertain, the system sends a neutral confirmation and places the record in a monitored review queue instead of guessing. Real-time automation is useful when a defined response window improves the outcome and the system can still make a safe, explainable decision. --- # Recommended Format for Schema Markup | Surface Glossary URL: https://surface.thesurface.network/glossary/recommended-format-for-implementing-schema-markup The recommended format for implementing schema markup is usually JSON-LD, a block of structured data placed in a script element with the type application/ld+json. Search engines can read the block without requiring the markup to wrap every visible heading, image, price, author name, or review on the page. JSON-LD is a format, while Schema.org supplies the vocabulary. A team may use JSON-LD to state that a page contains an Article, Organization, Product, Event, or another defined entity. Microdata and RDFa can also express Schema.org properties, but JSON-LD is generally easier for marketing and development teams to generate, review, and update across templates. A durable implementation starts with the page and its visible claims. The schema should describe what a visitor can actually find, use the most specific supported type, and keep important identifiers consistent across the site. The work belongs in the publishing system rather than in a one-time code snippet pasted into a handful of pages. 1. Choose the entity represented by the page. An article page may need Article or BlogPosting markup, while a company page usually needs Organization. Do not choose a type only because it has an attractive search feature. 2. Map visible facts to valid properties. Use the page title, canonical URL, author, dates, image, logo, offer, or other facts that the page already presents. Leave out properties the team cannot support or keep current. 3. Generate a JSON-LD block and place it in the page template. The script can appear in the head or body, but it should render reliably for crawlers and should not depend on a visitor action to load. 4. Validate the syntax and the search feature requirements. A Schema.org validator can catch vocabulary errors, while a search engine's rich-result test can show whether a supported enhancement is eligible and which recommended fields are missing. 5. Monitor production pages after release. Check rendered HTML, indexing reports, enhancement reports, template changes, and visible page data. Update the markup whenever the underlying claim changes. Success has two layers. The first is technical: valid JSON-LD appears on every intended canonical page and stays synchronized with visible content. The second is search behavior: eligible pages may gain enhanced presentation, clearer entity interpretation, or fewer markup errors. Rich results remain a search-engine choice, so eligibility should never be reported as guaranteed display. Treat schema markup implementation as part of the publishing contract. The page, canonical metadata, structured graph, sitemap, internal links, and source records should describe the same entity without relying on a plugin operator to reconcile them manually. Keep a small fixture set for major page templates and run it after CMS, rendering, URL, schema, and design changes. Record warnings separately from errors so optional properties do not become a reason to invent content or delay useful releases. Keep the smallest useful scope for schema markup implementation until the operation has evidence to expand. Limit templates, segments, permissions, channels, or actions at first. Review errors and manual work, then add scope deliberately. This makes ownership and rollback practical and gives the team a baseline against which a broader version can be judged. The final artifact should show the current decision, the evidence behind it, and the condition that forces reconsideration. That is what makes schema markup implementation maintainable after the original operator moves to another project. Retirement belongs in the operating plan for schema markup implementation too. Define the signal that shows the process no longer serves its original audience, system, category, or decision. Archive the configuration and evidence, stop new entries safely, preserve required history, and update dependent reports or links. Unused processes create risk when they remain active simply because no one owns turning them off. Record where schema markup implementation remains uncertain and when that uncertainty becomes material. This gives the next operator a starting point instead of forcing another full audit. - Decide which page templates deserve markup and which entity each template represents. - Assign ownership for business facts such as prices, dates, authors, logos, and ratings. - Define whether the CMS, a tag manager, or application code will generate the JSON-LD. - Set a validation gate for publishing and a monitoring process for production errors. - Document exceptions, especially pages that contain several entities or change frequently. The best location for the implementation is the place where the source facts already live. Product data should flow from the product record, author data from the author profile, and dates from the publishing system. Copying those facts into a separate spreadsheet makes drift almost inevitable. A common failure is treating schema as invisible SEO copy. The team fills every possible property, repeats keywords, marks up reviews that are not displayed, or adds types that do not match the page. The code may validate syntactically while still misrepresenting the content. Another version of the same problem appears when a redesign changes the page and leaves the old JSON-LD untouched. Recover by reducing the block to verified page facts, connecting each property to a maintained source, and testing the rendered production URL. A smaller accurate graph is more useful than a large brittle one. --- # Research and Market Intelligence | Surface Glossary URL: https://surface.thesurface.network/glossary/research-and-market-intelligence Research and market intelligence are the connected practices of collecting, analyzing, distributing, and updating evidence about customers, competitors, categories, technology, regulation, channels, and market conditions. Research often answers a defined question, while intelligence adds a recurring system for detecting and interpreting change. The work supports positioning, product strategy, campaigns, sales, partnerships, pricing, and investment. It should distinguish primary facts, participant claims, analyst estimates, and internal interpretation. A competitor's website is evidence of its current positioning, not proof of customer preference or product performance. Build the program around decisions and change signals. Define priority topics, approved sources, collection cadence, evidence standards, owners, and distribution. Store findings in a form that links conclusions to sources and records what would cause the recommendation to change. 1. Name the decisions the intelligence system supports, such as segment choice, positioning, campaign planning, product investment, or competitive response. Prioritize questions with real owners. 2. Create a source map across buyers, customers, sales calls, product data, competitors, public records, search behavior, industry experts, and relevant publications. Label modeled or self-reported evidence. 3. Collect on a cadence matched to volatility. Product pricing and messaging may need monthly checks, while broader market structure may change more slowly. 4. Analyze facts, patterns, contradictions, confidence, and implications. Separate the evidence record from the strategic recommendation so reviewers can challenge either one. 5. Deliver intelligence inside the workflow where decisions occur. Update briefs, battlecards, campaign plans, product reviews, and leadership notes rather than leaving findings in an isolated repository. Useful measures include source freshness, coverage of priority questions, time from signal to review, stakeholder use, decisions influenced, forecast accuracy where applicable, and the rate at which findings are updated or retired. Volume of collected links is a weak measure if no one can act on them. The operating discipline for research and market intelligence is a chain from question to source to interpretation to decision. Preserve interview notes, survey instruments, queries, public records, and dated product evidence with enough context to audit the conclusion. Add a confidence statement and the observation that would reverse the recommendation. This avoids the familiar research failure where a clean slide outlives the evidence and continues to guide positioning after the market has changed. Keep the smallest useful scope for research and market intelligence until the operation has evidence to expand. Limit templates, segments, permissions, channels, or actions at first. Review errors and manual work, then add scope deliberately. This makes ownership and rollback practical and gives the team a baseline against which a broader version can be judged. The final artifact should show the current decision, the evidence behind it, and the condition that forces reconsideration. That is what makes research and market intelligence maintainable after the original operator moves to another project. Retirement belongs in the operating plan for research and market intelligence too. Define the signal that shows the process no longer serves its original audience, system, category, or decision. Archive the configuration and evidence, stop new entries safely, preserve required history, and update dependent reports or links. Unused processes create risk when they remain active simply because no one owns turning them off. Record where research and market intelligence remains uncertain and when that uncertainty becomes material. This gives the next operator a starting point instead of forcing another full audit. - Which market questions deserve continuous monitoring rather than a one-time study? - Which sources support facts, estimates, behavior, or opinion? - How will confidence and contradiction be recorded? - Who owns interpretation and the decision that follows? - When does a signal justify an update, experiment, or escalation? Intelligence should arrive early enough to change a plan and remain specific enough to evaluate later. Vague statements that the market is shifting do little work unless the team can name the signal, affected assumption, and next decision. A common failure is competitor-news collection without a strategic model. The team tracks launches, hires, and slogans, then forwards a weekly digest that produces anxiety and reactive campaigns. Activity is mistaken for meaning. Return to a small set of business questions, define thresholds for meaningful change, and tie every brief to an assumption or action. Archive noise, preserve source history, and review whether prior interpretations were accurate. --- # Revenue Marketing Strategy | Surface Glossary URL: https://surface.thesurface.network/glossary/revenue-marketing-strategy A revenue marketing strategy is a coordinated approach for using marketing to create, capture, convert, and expand demand in ways that contribute to revenue. It links market selection, positioning, programs, content, channels, lead operations, sales handoffs, customer lifecycle, investment, and measurement. The strategy looks beyond lead volume to the quality, timing, cost, and commercial value of buyer movement. Marketing still has jobs that precede measurable pipeline, including category education, brand trust, and audience development. Revenue strategy gives those jobs a stated role and time horizon rather than forcing every activity into immediate attribution. Define the target segments, buying groups, offer, sales motion, customer economics, and expected sources of growth. Map how anonymous demand becomes identifiable, qualified, owned, and supported through purchase or expansion. Set shared stage definitions, response expectations, sourced and influenced measures, cost scope, and maturity windows. The model should reconcile marketing ambition with sales capacity, product readiness, and customer retention. Build a portfolio across long-term demand creation and current demand capture. Assign programs to specific audiences and funnel or lifecycle jobs. Measure audience quality, engagement, conversion, time, opportunity, revenue, retention, and cost by cohort. Use sales and customer outcomes to revise targeting, claims, content, capture, and follow-up. Review assumptions rather than reacting to every weekly fluctuation. Preserve uncertainty where attribution cannot support a precise claim. A company generates many small-business leads while enterprise revenue is the priority. Its revenue marketing strategy narrows paid demand capture, builds an enterprise proof program, improves target-account routing, and equips sales with technical content. The model tracks engaged accounts, meetings, opportunities, cycle length, deal value, and program cost. Marketing still reports broader awareness, but investment decisions use the segment and outcome the company chose to grow. Keep stage definitions, cost scope, attribution, and observation windows stable across programs. Report raw counts, rates, value, time, and uncertainty. Separate forecast, sourced pipeline, influenced pipeline, booked revenue, and retained revenue. Marketing can contribute to several without claiming sole credit. The strategy becomes more credible when reporting shows where evidence is strong and where a commercial outcome has several causes. --- # Rich Snippets and Schema Markup | Surface Glossary URL: https://surface.thesurface.network/glossary/rich-snippets-and-schema-markup Schema markup and rich snippets describe two different parts of search presentation. Schema markup is the structured data a site publishes. A rich snippet, more commonly called a rich result, is an enhanced search listing that may display details such as ratings, prices, event dates, recipe time, or other supported information. The causal language needs care. Markup can make a page eligible for a supported enhancement, but the search engine decides whether to show it for a particular query, device, location, and result set. Valid code is therefore evidence of correct implementation, not proof that a rich result will appear. The distinction changes reporting. An SEO team can own valid markup coverage and investigate eligibility. It cannot promise that every marked-up page will receive a visual enhancement. Keeping the terms separate also prevents teams from adding irrelevant schema simply because they want a more noticeable search listing. Start with the search engine's supported result types, confirm that the visible page meets the content rules, and map required fields to reliable source data. Test the rendered URL rather than a copied code block. After launch, monitor enhancement reports and compare search impressions and clicks by page type without treating every change as a schema effect. Teams can make rich snippets and schema markup easier to maintain by treating it as a data contract. Name the object, its stable identifier, its permitted properties, and the source responsible for each value. Set an explicit review trigger rather than relying on memory. A product launch, schema change, prompt revision, new data source, campaign shift, or sales objection may justify a fresh check. The practical test for rich snippets and schema markup is whether it improves a real decision without creating hidden definitions, unsupported confidence, or an unowned handoff to another team. A webinar page displays the title, start time, end time, attendance mode, location, and registration status. The site publishes matching Event markup. The code validates and the page becomes eligible for an event enhancement, yet many branded searches still show an ordinary blue link. Nothing is necessarily broken. The engine may choose a different presentation for those queries. Schema is an input and a rich result is a possible output. Teams make better technical and forecasting decisions when they measure those stages separately. --- # Sales and Marketing Alignment | Surface Glossary URL: https://surface.thesurface.network/glossary/sales-and-marketing-alignment Sales and marketing alignment is the set of shared definitions, data, workflows, service levels, content, and feedback loops that let both functions work toward the same customer and revenue outcomes. It covers target accounts, lifecycle stages, qualification, lead ownership, response expectations, rejection, recycling, opportunity creation, and attribution. Alignment is visible in the operating system. Meetings and good relationships help, but they cannot repair a CRM where marketing and sales use different meanings for qualified, source, or accepted. The handoff should preserve context and give both teams a way to challenge and improve the rules. Define the shared customer model and the decisions around it. Document lifecycle and qualification criteria, route ownership, response service levels, rejection reasons, recycle paths, data sources, and reporting. Use sales evidence to change targeting and content, and use marketing evidence to improve sales context and timing. 1. Agree on the target account and buyer groups using observable criteria. Keep aspirational segments separate from the rules that decide current routing and reporting. 2. Define lifecycle stages, qualification, acceptance, rejection, recycling, opportunity, and customer status. Assign the source fields and owner for each transition. 3. Design the handoff with required context, routing logic, response timer, fallback, and visible exception states. Give sales a structured way to return reasons rather than informal complaints. 4. Create shared reporting from the same records. Review volume, quality, response, acceptance, meetings, pipeline, revenue, and loss by segment and source. 5. Feed outcomes into campaigns, content, product messaging, scoring, and territory rules. Record changes so both teams know which version produced the result. Useful measures include accepted lead rate, response time, meeting rate, opportunity creation, rejection reasons, recycle performance, stage conversion, sales use of content, pipeline, revenue, and reconciliation between reports. Surveyed trust can add context but should not replace operating evidence. The operating discipline for sales and marketing alignment is a chain from question to source to interpretation to decision. Preserve interview notes, survey instruments, queries, public records, and dated product evidence with enough context to audit the conclusion. Add a confidence statement and the observation that would reverse the recommendation. This avoids the familiar research failure where a clean slide outlives the evidence and continues to guide positioning after the market has changed. Keep the smallest useful scope for sales and marketing alignment until the operation has evidence to expand. Limit templates, segments, permissions, channels, or actions at first. Review errors and manual work, then add scope deliberately. This makes ownership and rollback practical and gives the team a baseline against which a broader version can be judged. The final artifact should show the current decision, the evidence behind it, and the condition that forces reconsideration. That is what makes sales and marketing alignment maintainable after the original operator moves to another project. Retirement belongs in the operating plan for sales and marketing alignment too. Define the signal that shows the process no longer serves its original audience, system, category, or decision. Archive the configuration and evidence, stop new entries safely, preserve required history, and update dependent reports or links. Unused processes create risk when they remain active simply because no one owns turning them off. Record where sales and marketing alignment remains uncertain and when that uncertainty becomes material. This gives the next operator a starting point instead of forcing another full audit. - Which definitions and records will both teams use? - Who owns each stage change, handoff, exception, and service level? - Which sales feedback must be structured enough to influence marketing? - How will account context and active opportunities suppress or alter campaigns? - Which forum can change the rules and document the new version? Alignment requires a mechanism for disagreement. Sales should be able to reject a lead for a defined reason, and marketing should be able to inspect whether the reason matches the agreed criteria. Otherwise feedback becomes anecdote and the shared model never learns. A common failure is solving alignment through a new lead score. Marketing changes the formula, sales still distrusts the inputs, and accepted leads do not improve. The score hides the disagreement about target account, timing, and evidence under one number. Review a sample of real leads and deals together, rebuild the definitions from observed outcomes, and expose the source data behind qualification. Add response and rejection rules, then revisit the model on a set cadence. --- # Sales and Marketing Operations | Surface Glossary URL: https://surface.thesurface.network/glossary/sales-and-marketing-operations Sales and marketing operations are the shared operating practices that connect demand creation with sales execution. The work can include campaign process, lead capture, enrichment, scoring, routing, lifecycle definitions, ownership, service levels, CRM and automation administration, pipeline reporting, enablement, and feedback into future targeting and content. Some companies place the work under revenue operations; others retain separate sales and marketing operations teams with shared agreements. The label matters less than authority and handoffs. Someone must own the definitions and systems that cross the boundary, while each function remains accountable for decisions inside its expertise. Marketing can generate appropriate demand and lose it through delayed or incorrect routing. Sales can reject leads for valid reasons and fail to return those reasons in a form marketing can use. Disconnected operations turn those failures into recurring arguments about volume and quality. Define common objects, lifecycle stages, qualification rules, ownership, timestamps, service levels, and sources of truth. Preserve the campaign and content context a seller needs. Require structured acceptance, rejection, and recycle reasons. Review full cohorts from first response through opportunity and revenue, then connect the evidence to campaign and capacity decisions. Create a joint operating review around exceptions and outcomes, not competing dashboards. Sample good and bad records, inspect response time and owner capacity, reconcile metric definitions, and assign process changes. Keep operational status separate from buyer state so a queue or workflow step does not become a misleading lifecycle claim. A company discovers that high-intent demo requests wait overnight when the assigned territory owner is unavailable. Sales and marketing operations add capacity-aware routing, an escalation timer, and a visible exception queue. Sales records disposition within two days, and marketing uses the reasons to change targeting and form language. Sales and marketing operations make the revenue path legible enough for both teams to act on the same evidence. That shared record should survive reorganizations and changes in software ownership. --- # Sales Lead Form | Surface Glossary URL: https://surface.thesurface.network/glossary/sales-lead-form A sales lead form is a website or product form used to collect information from a person who wants a sales response. It usually records contact identity, company context, the nature of the request, consent, source, and submission time. The form may also collect or append information needed to route the request to the right team. The form sits at a sensitive point between buyer intent and company operations. Every required field adds effort, yet missing information can delay follow-up or send a request to the wrong owner. Hidden fields and enrichment can reduce typing, but they need transparent purpose, reliable sources, and fallback behavior when the data is absent or wrong. Form performance includes more than completion rate. A short form can increase submissions while burdening sales with poor-fit requests. A long form can exclude legitimate buyers, especially on mobile or when people do not know the requested details. Accessibility, privacy, security, spam prevention, confirmation, and response time affect whether the captured demand becomes a useful conversation. Begin with the response decision. Ask which fields sales needs immediately and which can wait for discovery or enrichment. Use plain labels, explain unusual questions, preserve campaign and page context, and validate without erasing entries after an error. Define duplicate handling, account matching, territory rules, owner fallback, service level, and what the submitter sees after completion. Measure view, start, field error, completion, spam, qualified acceptance, meeting creation, response time, and downstream opportunity by relevant segment. Review drop-off by device and field without treating correlation as proof. Pair the numbers with session observation and sales rejection reasons. Test routing whenever a territory, product line, CRM field, or enrichment source changes. An enterprise software company requires 11 fields before a demo request. Analysis shows heavy abandonment at annual revenue, and sales rarely uses the exact amount. The team replaces it with a broader company-size field, enriches account data after submission, and keeps a manual queue for unmatched firms. Completion rises while accepted-meeting rate stays stable, so the shorter form reduces friction without lowering fit. A sales lead form should collect enough trustworthy context for the next decision while respecting the buyer's time and data. --- # Schema Data | Surface Glossary URL: https://surface.thesurface.network/glossary/schema-data Schema data is information organized according to a defined schema of entities, properties, types, and relationships. In SEO, the phrase usually refers to structured data markup that uses the Schema.org vocabulary to describe visible page content. A page can identify an organization, product, article, event, person, job posting, breadcrumb, or another supported type in a machine-readable form. The schema tells a system how data is shaped and what each property means. The values must still come from the real page and business. Markup cannot make an unsupported rating, price, author, or event true. 1. **Choose the entity.** Identify the primary thing on the page and the purpose of the content. Select a Schema.org type that accurately represents it and is useful to the systems that will consume it. 2. **Map visible facts.** Connect names, URLs, identifiers, dates, offers, authors, images, addresses, and relationships to appropriate properties. Keep the markup consistent with what a person can see. 3. **Generate the syntax.** JSON-LD is commonly used for web markup because it can sit separately from the visible HTML. Microdata and RDFa attach attributes to HTML elements. The vocabulary and syntax solve different parts of the job. 4. **Validate the output.** Check syntax, required or recommended properties, canonical URLs, dates, and entity relationships. Use tools appropriate to the intended search feature, then inspect the rendered page and published source. 5. **Maintain the markup.** Connect dynamic values to authoritative systems where possible. Revalidate after template, CMS, product, pricing, event, or policy changes. - Which page template owns each entity and property. - Whether a value comes from the CMS, product system, commerce platform, or a manual field. - How entities connect across organization, author, product, article, and breadcrumb markup. - Who reviews structured data when visible claims change. - Which errors block release and which warnings require a documented judgment. - How the team monitors coverage and unexpected template regressions. ## Keep markup and content consistent Structured data should describe the page rather than act as a hidden second version of it. If an event date, product price, or author changes, both representations need the same source. Duplicate hardcoded values invite drift. Eligibility for a rich result does not guarantee that a search engine will display one. Measure technical validity, coverage, search appearance, and business outcomes separately. Do not treat markup volume as a visibility result. Teams often install a plugin, enable every available type, and assume the site now has a schema strategy. The result may include generic entities, missing identifiers, conflicting organizations, stale values, or markup for content that the page does not show. Validation can pass while the representation remains unhelpful. A better implementation starts with important templates and a clear entity model. It uses a small number of accurate types, connects them to maintained source fields, and assigns review. The structured data then reflects the site the organization actually operates. Schema data gives systems explicit entity and relationship clues, which can reduce ambiguity when page text uses several names or presents facts in a complex layout. It supports discovery and eligibility where a search product recognizes the vocabulary. It does not replace crawlable content, internal links, strong evidence, or a clear page purpose. For AI visibility, structured data is one part of a broader information system. Consistent organization, author, product, article, and breadcrumb entities can help machines connect pages, but an answer system may rely on visible text and external sources instead. Teams should avoid claims that markup guarantees citations or recommendations. Measure the implementation at three levels: technical validity, search or crawler interpretation, and business result. A valid graph can still describe the wrong entity. A correct entity can still earn no special appearance. The final test is whether the page and markup communicate the same trustworthy facts. Keep a registry of templates, types, data sources, validators, and owners. A blog, event, product, and organization template may share entities while drawing from different fields. Review their identifiers and relationships together. This prevents one deployment from creating several versions of the same company, author, or product. --- # Schema in Digital Marketing | Surface Glossary URL: https://surface.thesurface.network/glossary/schema-in-digital-marketing Schema in digital marketing usually refers to Schema.org vocabulary expressed as structured data on a website. It gives search systems explicit statements about the entities on a page, such as an organization, article, product, event, person, offer, or review, and the relationships among them. The job is narrower than many marketing claims suggest. Schema can clarify meaning and create eligibility for supported search features. It does not turn weak content into an authoritative source, force an AI assistant to cite the page, or guarantee a higher organic ranking. Marketers should treat it as part of technical publishing infrastructure. A marketing team begins with a page inventory and a small entity model. The model defines which business facts appear across templates, which system owns each fact, and how the same company, product, author, or event is identified consistently. Developers or CMS owners then express those facts in markup and connect validation to the release process. 1. List the important page classes, including company, product, article, author, event, and customer-proof pages. Each class needs a clear primary entity before anyone selects properties. 2. Choose a supported Schema.org type and map its useful properties to visible page fields. Use canonical URLs and stable identifiers so the same entity is not described as several unrelated objects. 3. Generate the markup from maintained data. A CMS template, product database, or event record is safer than manually rewriting facts inside a separate plugin field for every page. 4. Validate representative pages and test edge cases. Review an article without an author image, an event after its date changes, and a product with no public rating rather than testing only the perfect example. 5. Monitor errors and business changes. Revisit the schema when the brand name, logo, URL structure, product offer, author model, or publishing workflow changes. Technical coverage, validity, and consistency are the first measures. Search-enhancement impressions and click behavior may provide a second layer where a supported result type exists. For AI visibility, measure mentions, citations, and source inclusion separately because schema presence alone does not explain those outcomes. Treat schema in digital marketing as part of the publishing contract. The page, canonical metadata, structured graph, sitemap, internal links, and source records should describe the same entity without relying on a plugin operator to reconcile them manually. Keep a small fixture set for major page templates and run it after CMS, rendering, URL, schema, and design changes. Record warnings separately from errors so optional properties do not become a reason to invent content or delay useful releases. Set the review cadence for schema in digital marketing according to volatility and consequence. Fast-changing inputs may need weekly checks, while stable reference material may suit a quarterly factual review. The owner should inspect input quality, output quality, timing, exceptions, and business outcome. Record which finding changes the rule and which finding only needs observation. Do not let the primary tool, spreadsheet, or configuration become the only documentation. A plain-language record of purpose and consequences makes schema in digital marketing easier to audit, teach, change, and retire. Maintain an exception log for schema in digital marketing that is small enough to review and structured enough to learn from. Capture the input, expected behavior, actual result, consequence, immediate repair, and root cause. Group recurring exceptions by source, rule, segment, template, or integration. This makes schema in digital marketing improve through evidence and prevents the same workaround from being rebuilt by several teams in different tools. Keep a short schema in digital marketing limitations note with the current process. It should name missing evidence, unsupported cases, and dependencies that could invalidate the approved approach. - Name the owner of the entity model and the owner of each source field. - Decide which templates have enough stable data to support accurate markup. - Choose stable identifiers for the organization, products, authors, and other repeated entities. - Define how page changes trigger validation or a schema review. - Agree on what will be measured without promising ranking or citation lift. Marketing should own the meaning of claims, while engineering or the CMS owner should own reliable rendering. SEO can translate search requirements between those groups. The split matters because a technically perfect block can still express the wrong business fact, and a correct business model can still fail to appear in rendered HTML. The common failure is plugin-first implementation. A team installs a schema tool, enables every available type, and assumes the vocabulary will organize itself. Pages then contain duplicated Organization nodes, generic WebPage markup, stale logos, or product properties that have no source. The markup becomes another unowned layer of the site. Return to the page inventory, reduce the number of types, and connect every included property to a visible and maintained fact. Once the base is clean, expand only when a new page class or search use case justifies the extra data. --- # Schema Markup | Surface Glossary URL: https://surface.thesurface.network/glossary/schema-markup Schema markup means code that labels a web page's entities, properties, and relationships with a shared vocabulary. The most common vocabulary is Schema.org, and the most common implementation format for SEO is JSON-LD. Together they let a site make explicit statements such as this page describes an Organization, this person wrote the article, or this event starts at a specific time. The word schema refers to the model that defines which types and properties are available. Markup is the page-level expression of that model. The result is machine-readable context layered onto the visible page. It should describe the page accurately rather than introducing claims that visitors cannot verify. A team first identifies the page's main entity, chooses the matching type, and maps visible facts to properties. The markup is generated from maintained fields, rendered with the page, validated, and checked after deployment. Repeated entities such as the organization, product, and author should use stable identifiers across the site. 1. Name the page's primary subject in ordinary language. A post about a conference is still usually an article unless the page itself functions as the event record. 2. Choose the closest valid type and a restrained set of properties. Include facts that help define the entity and that the business can keep accurate. 3. Express those facts in JSON-LD or another supported syntax. Connect the values to CMS, product, author, or event fields instead of duplicating them manually. 4. Validate the rendered page and compare the block with the visible content. Fix warnings that reveal missing useful data, while recognizing that every optional warning does not require a field. 5. Maintain the markup as part of the template. A content edit, rebrand, URL migration, or product change may require the structured data to change too. A good implementation produces valid, consistent coverage across the intended templates. Search enhancement reports may show eligibility and errors for supported types. Organic presentation or AI interpretation may improve, but those outcomes also depend on content quality, authority, query fit, and the engine's presentation choices. For schema markup, the operating record should begin with one representative production page and trace every structured claim back to a visible field or maintained system. Record the entity type, canonical URL, stable identifiers, generation method, validation result, template owner, and the search feature or machine interpretation the team expects the markup to support. Repeat the review with an imperfect page, such as one missing optional data or containing several related entities. That second page usually reveals whether the template has a real data model or a hand-built happy path. Create a short release checklist for schema markup and assign each item to a role. Include source verification, permissions, privacy, required approvals, error visibility, downstream compatibility, and rollback. Keep the checklist close to the workflow so it changes when the workflow changes. After release, review exceptions before aggregate performance because an average can improve while a small number of high-value cases fail badly. Connect the local schema markup workflow to the decision that follows it. Documentation should show what the next operator receives and which context must survive the handoff. Before expanding schema markup, compare several outputs with the source material and with the decision made by a competent operator. Record false positives, false negatives, missing cases, and disagreements about definitions. Use that sample to update the rule, test set, documentation, or training rather than explaining every error as an isolated exception. The review should end with a named change and an owner, even when the change is to keep the current scope. For schema markup, note unresolved questions beside the approved process. Visible limitations invite review; hidden assumptions tend to survive until a customer, report, or integration exposes them under worse conditions. - Define which entity each template is responsible for describing. - Choose the system of record for every important property. - Assign responsibility for vocabulary changes and search-feature requirements. - Create a policy for stable @id values and canonical URLs. - Set review triggers for launches, migrations, redesigns, and rebrands. The markup should remain understandable to someone who knows the page but has never seen the implementation. If the team cannot explain where a value comes from or why a type was selected, the graph is probably more complex than the operation can support. A frequent failure is confusing more markup with more authority. Teams add several overlapping types, copy keyword-rich descriptions into hidden fields, and mark up every mention as a separate entity. The graph grows while its meaning becomes less clear. It may also drift from the visible page because no one owns the duplicated facts. Remove redundant nodes, keep the primary entity clear, and trace each property to a maintained visible source. Validate a representative sample after the cleanup, then add complexity only when a page or business requirement needs it. --- # Schema Markup for Reviews | Surface Glossary URL: https://surface.thesurface.network/glossary/schema-markup-for-reviews Schema markup for reviews is structured data that identifies a review, its subject, its author, and its rating. A page may describe one Review or summarize many ratings with AggregateRating when the page and the underlying data meet the applicable search guidelines. Marketing teams encounter review markup on product, software, book, course, recipe, and other eligible pages. The markup does not create a review and does not guarantee stars in a search result. It translates visible, genuine review information into a machine-readable format so a search engine can evaluate the page for supported presentation features. Review markup can make rating data less ambiguous, but its larger value is discipline. The team has to identify what is being reviewed, where the rating came from, how the scale works, and whether the page displays the same information. That protects the site from using a vague five-star claim with no review object, count, or traceable source. Use the most specific item type available for the reviewed subject and include only ratings that the business actually collects and displays. Keep ratingValue, bestRating, worstRating, reviewCount, and the reviewed item's identity synchronized with the source system. Company-authored praise about the company itself should not be disguised as independent review evidence. Teams can make schema markup for reviews easier to maintain by treating it as a data contract. Name the object, its stable identifier, its permitted properties, and the source responsible for each value. Choose a measure that follows the actual job. Validity, coverage, reviewer effort, conversion, response time, source quality, and revenue can describe different outcomes and should stay separate. A short decision record should state the current approach, evidence, owner, date, and condition for revision. That makes schema markup for reviews useful beyond the person who first implemented it. A B2B software company publishes a page for a specific training course. The page shows an average rating of 4.6 from 84 verified learners, explains that the scale runs from one to five, and includes several written reviews. Its JSON-LD describes the Course and attaches an AggregateRating using the same 4.6 value and 84 count. When another review arrives, the page and markup update from the same database field. If the visible page says 4.6 while the markup says 4.8, the implementation is already broken. Review schema works best as a structured reflection of maintained evidence, not as an extra promotional layer added after publishing. --- # Scrubbing Data | Surface Glossary URL: https://surface.thesurface.network/glossary/scrubbing-data Scrubbing data is another term for cleaning data. It means finding and correcting, standardizing, merging, or isolating records that do not meet the quality rules for a specific workflow. Typical problems include duplicates, malformed fields, stale values, inconsistent categories, missing identifiers, and broken relationships. The word can sound like deletion, but good scrubbing is usually conservative. It preserves source values, records transformations, and separates uncertain cases for review. Removing every unusual value may make the dataset look orderly while deleting legitimate edge cases. The process begins by defining the record and the intended action. The team profiles source data, writes rules for known error patterns, sets confidence thresholds for fuzzy matches, and validates downstream results. Recurring defects should lead back to the form, integration, vendor, or manual process that created them. 1. Set quality rules for the use case. Name required fields, accepted formats, identifier logic, freshness windows, and the errors that must block an automated action. 2. Profile the source and group issues by type and origin. Missing country values from one form need a different repair than stale employee counts from an enrichment feed. 3. Apply deterministic corrections first. Normalize casing, whitespace, dates, country codes, domains, and controlled categories while retaining the original value and rule name. 4. Review uncertain matches and conflicting evidence. Do not merge accounts, replace submitted values, or infer identities solely because a similarity score clears an arbitrary threshold. 5. Reconcile results with the source and the downstream system. Sample changed rows, compare totals, test automations, and monitor whether the defect returns after the cleanup. Useful measures include duplicate rate, valid-field rate, match coverage, records changed by each rule, review volume, reversal rate, and downstream exception rate. If routing acceptance or report reconciliation does not improve, the cleanup may be targeting cosmetic issues instead of operational ones. Operational review of data scrubbing should follow a record through the systems that consume it. Start at collection, then inspect enrichment, normalization, matching, CRM sync, routing, reporting, and retention. Sample records that passed every validation as well as records sent to exceptions. A valid field can still be wrong for the person, account, or time period, and a clean table can still break when identifiers connect it to the wrong entity. Keep the smallest useful scope for data scrubbing until the operation has evidence to expand. Limit templates, segments, permissions, channels, or actions at first. Review errors and manual work, then add scope deliberately. This makes ownership and rollback practical and gives the team a baseline against which a broader version can be judged. The final artifact should show the current decision, the evidence behind it, and the condition that forces reconsideration. That is what makes data scrubbing maintainable after the original operator moves to another project. Retirement belongs in the operating plan for data scrubbing too. Define the signal that shows the process no longer serves its original audience, system, category, or decision. Archive the configuration and evidence, stop new entries safely, preserve required history, and update dependent reports or links. Unused processes create risk when they remain active simply because no one owns turning them off. Record where data scrubbing remains uncertain and when that uncertainty becomes material. This gives the next operator a starting point instead of forcing another full audit. - Define which errors matter for the immediate workflow. - Choose whether a rule corrects, flags, quarantines, merges, or deletes a record. - Set source precedence and preserve provenance when values conflict. - Require review for high-value or low-confidence identity changes. - Assign an owner to fix upstream sources that keep producing the defect. Data scrubbing should be repeatable. A manual afternoon of editing cells may solve today's export and teach the organization nothing about tomorrow's records. Rules, thresholds, and exceptions need a maintained home. A common failure is using a bulk cleanup to force data into the reporting categories leadership expects. Nulls become zeros, unknown sources become organic, and unmatched accounts disappear. The dashboard reconciles because the uncertainty was erased, not because the underlying records improved. Restore the raw data, separate unknown from zero, keep unmatched records visible, and rebuild the cleaning sequence from documented rules. Report residual uncertainty alongside the cleaned result. --- # Search Volume | Surface Glossary URL: https://surface.thesurface.network/glossary/search-volume Search volume is an estimate of the number of searches for a keyword or query during a defined period, commonly reported as average monthly searches. Tools may model volume from advertising data, clickstream panels, search-console data, or proprietary sources, so two tools can report different numbers for the same term. Volume measures searches, not unique people, clicks, qualified visits, or buyers. One person may search several times. A result page may answer the question without a click. Keyword tools may combine variants, smooth seasonality, or report rounded ranges. When a tool has monthly observations, a simple average is: `Average monthly search volume = Total estimated searches across the period / Number of months` The estimate must specify query matching, country, language, device coverage, and date range. A twelve-month average can hide a recent spike or a highly seasonal market. Exact query data from a site's own search reporting answers a different question because it covers impressions for that site rather than all searches in the market. Some tools report global volume, local volume, desktop and mobile splits, or ranges rather than point estimates. Paid-search planners may group close variants. SEO platforms may apply clickstream models. Treat cross-tool comparisons as directional unless the methodologies align. A high-volume term may be broad, competitive, and weakly connected to revenue. A low-volume term may describe a decisive enterprise problem or produce valuable query fan-out coverage. Evaluate volume with intent, difficulty, traffic potential, result features, business fit, conversion path, and the company's right to answer. Search behavior also moves into AI assistants, social platforms, communities, marketplaces, and private research. Traditional keyword volume does not capture all demand. New categories may have little search volume precisely because buyers have not learned the category name. Treat uncertainty as part of search volume. Use ranges or sensitivity cases when important inputs are modeled, and identify which assumption moves the result most. A precise decimal cannot compensate for an uncertain market boundary or attribution rule. Record the calculation version and review date so later comparisons use the same method or explain the change. A glossary term shows 500 estimated monthly searches, while a related software comparison shows 80. The glossary term can support broad discovery, but the comparison page maps directly to active evaluation and converts at a higher rate. The content plan uses both, assigning different jobs instead of ranking ideas by volume alone. Search volume is a demand clue and a planning input. It becomes misleading when teams report it as an audience count or use it to choose content without intent and business context. --- # Secondary Market Research | Surface Glossary URL: https://surface.thesurface.network/glossary/secondary-market-research Secondary market research analyzes evidence that was already collected for another purpose or an earlier study. Sources may include government data, public filings, trade records, academic work, industry studies, news archives, reviews, search behavior, pricing pages, company records, and prior customer research. The researcher does not recruit new participants for the specific question. Secondary research is often the first step in a market project because it can establish definitions, history, known estimates, competitors, and evidence gaps before primary collection begins. It can also answer a question on its own when reliable sources match the decision closely enough. Internal data counts as secondary when analysts reuse it for a new question. Existing evidence can reduce cost and keep a team from asking the market questions that have already been studied. Its weakness is fit. A source may use a different geography, segment, category boundary, time period, or measurement method. Several websites may repeat one original estimate, creating the appearance of confirmation without independent evidence. Write inclusion criteria and a search record. For every source, capture the publisher, original collector, date, population, method, unit, definitions, exclusions, funding or commercial interest, and link. Trace copied claims back to the earliest available source. Compare numbers only after reconciling currency, period, category, and sample. Use ranges when credible sources disagree. Add interviews, surveys, observation, or experiments when existing material cannot answer the company-specific decision. Common gaps include current buyer language, reaction to a new concept, reasons behind observed behavior, or the distribution of a need in a narrowly defined segment. Secondary evidence should shape recruitment and questions, while primary findings should remain separate from broader market estimates unless their sample supports that use. A company estimates demand for scheduling software among US dental groups. Public establishment counts define the population, vendor pages describe current offers, and internal search data shows recurring needs. None of those sources explains who controls the purchase across multi-site groups. The team uses the secondary work to form the segment and then interviews administrators and owners about the buying process. Secondary market research is strong when the source, method, boundary, date, and connection to the decision remain visible. --- # SEO Analytics Reporting | Surface Glossary URL: https://surface.thesurface.network/glossary/seo-analytics-reporting SEO analytics reporting is the practice of measuring how pages are discovered through search, how users interact after arrival, and how organic visibility contributes to business outcomes. Common inputs include impressions, clicks, click-through rate, ranking distribution, indexation, crawl health, landing sessions, engagement, conversions, links, and revenue-related events. A useful report separates leading and lagging signals. Impressions may rise before clicks. Clicks may rise without qualified visits. Conversions may change because a form, offer, routing system, or product changed. The report should explain the path and preserve uncertainty rather than presenting one metric as the whole program. Reporting decides what the team optimizes next. A dashboard focused on aggregate traffic may reward generic topics and hide pages that influence high-value deals. Page-type, topic, intent, query, brand, device, country, and conversion segmentation reveal where the program creates useful demand. Define metrics and sources, preserve search and analytics dates, group pages through a maintained taxonomy, annotate releases, and reconcile conversions with the lead system. Combine site reporting with AI visibility where buyers also use generated answers, while keeping rankings, citations, mentions, and recommendations separate. Use SEO analytics reporting through a documented metric layer. Record the source, grain, time zone, cohort window, formula, exclusions, page taxonomy, and business event so another analyst can reproduce the reported result. Keep the source beside the result and make changes reversible. This protects the operation when a definition, vendor, model, template, or buyer behavior changes after the original decision. The final review should ask what changed for a buyer or operator. If SEO analytics reporting only creates another field, page, prompt, or dashboard, its role remains incomplete. A quarterly report shows organic impressions up 70 percent and clicks up 20 percent. The team segments the change and finds most new impressions come from glossary queries in low average positions. Product-comparison pages generate fewer sessions but triple the meeting rate. The next plan improves glossary click appeal while expanding the high-intent cluster. The report should end with a decision tied to evidence. A larger chart pack that cannot explain what the team will refresh, build, consolidate, or stop is analytics inventory. --- # SEO Automated Reporting | Surface Glossary URL: https://surface.thesurface.network/glossary/seo-automated-reporting SEO automated reporting uses software to collect search data, apply documented transformations, refresh metrics, and deliver reports without rebuilding the same spreadsheet by hand. Common inputs include Search Console, analytics, rank tracking, crawl data, indexation records, backlink tools, and conversion systems. Automation handles repetition. It does not decide whether a metric is valid, a page belongs to the right group, or a traffic change deserves action. Search data arrives at different grains and delays, so a dependable report still needs human ownership of definitions, source changes, anomalies, and interpretation. Manual reporting consumes time and invites copy errors, yet a flawed automated report spreads its error more consistently. Even a canonical URL change can split one page across rows. Likewise, a timezone mismatch can distort daily comparisons. If a dashboard hides excluded pages or late data, teams may respond to an artifact of the pipeline rather than a change in search demand. Define the reporting job before choosing the dashboard. Record each source, grain, refresh schedule, timezone, attribution rule, page taxonomy, and owner. Keep raw collection separate from transformations and presentation. Add checks for missing dates, sudden row-count changes, duplicate URLs, broken joins, and totals that no longer reconcile with the source interface. Use scheduled reports to surface decisions, not to email every available chart. Weekly views might show query and page movement, indexation issues, conversions, and the few changes outside expected variance. Preserve an annotation log for launches, migrations, tracking changes, and major content updates. When the underlying definition changes, label the break instead of silently rewriting history. For example, a content team refreshes a weekly report from Search Console and analytics. The pipeline normalizes canonical URLs, groups pages by cluster and template, and connects landing sessions to form submissions. An alert fires when one template loses impressions while the rest of the site remains steady. The operator checks recent releases and finds that a rendering change removed internal links from that template. The best automated SEO report shortens the path from a trustworthy signal to a specific page decision. It still needs someone who understands how the data was produced. --- # Steps in the Marketing Research Process | Surface Glossary URL: https://surface.thesurface.network/glossary/steps-in-marketing-research-process The marketing research process is a sequence for turning a marketing decision into trustworthy evidence and action. It begins with the decision and uncertainty, then moves through design, collection, analysis, interpretation, recommendation, and documentation. The process can support market selection, positioning, product launch, pricing, messaging, channel choice, customer experience, or campaign revision. The steps are iterative. Early evidence may reveal that the original question is too broad or based on a false assumption. Revising the design is stronger than forcing the study to answer a question it cannot support. 1. **Frame the decision.** Name the owner, decision date, alternatives, consequence of error, and evidence already available. Convert a vague topic into specific research questions. 2. **Define the population and concepts.** Identify whose experience or behavior matters. Clarify terms such as awareness, preference, intent, qualified account, or adoption so the study measures the intended idea. 3. **Choose the design.** Decide whether the work is exploratory, descriptive, comparative, causal, or predictive. Select primary and secondary sources, qualitative and quantitative methods, sample, recruitment, and observation window. 4. **Prepare collection.** Write instruments, screen participants, plan consent and incentives, test tools, train researchers, and pilot the questions. Set rules for storage, access, and sensitive information. 5. **Collect and monitor.** Preserve raw evidence and metadata. Watch response quality, quotas, duplicates, missing values, interviewer effects, and technical errors while correction is still possible. 6. **Analyze and challenge.** Clean the data, code qualitative evidence, calculate measures, compare segments, and examine contradictions. Separate observed results from interpretation and model assumptions. 7. **Recommend and decide.** Connect findings to the alternatives in the original decision. State limitations, unresolved questions, expected effect, owner, and next review point. 8. **Archive the learning.** Store instruments, sources, definitions, analysis, decisions, and outcomes. Later teams should be able to see what was known and whether the decision worked. - How much confidence the decision requires and how much time is available. - Which people are eligible for the sample and which groups need separate analysis. - Which measures are direct observations, participant reports, or modeled estimates. - How researchers will handle contradictory evidence and unexpected findings. - Who approves interpretation and who owns the resulting action. - When the research becomes stale enough to repeat or refresh. Agree on possible decisions before collection begins. A study should not promise to produce one predetermined answer, but stakeholders should know how different findings would affect the plan. This prevents a final presentation that is interesting and operationally inert. After action, compare the outcome with the research expectation. The review improves future questions, samples, measures, and judgment. It also reveals where the organization ignored evidence or overestimated its certainty. Teams often begin with a preferred method. Someone requests a survey, the questions are drafted, and only later does the team ask what decision the responses should support. The study collects opinions from an easy-to-reach sample and produces percentages that appear precise without representing the target market. A better process begins with the decision and chooses the lightest credible evidence that can reduce its uncertainty. The result may be interviews, an analysis of existing records, a market model, an experiment, or a combined design. Method follows the question. Lead with the decision, evidence, and recommendation. Show the population, source, dates, method, and sample near the conclusion they qualify. Separate observations from interpretation. Include contradictory or null results when they affect confidence. Avoid turning participant quotations into a frequency claim or presenting a modeled estimate as directly measured demand. Give decision makers enough detail to challenge the work without forcing them through every transcript or row. Append instruments, codebooks, calculations, source notes, and raw evidence under appropriate access. Record which assumptions remain unresolved and which follow-up evidence would change the recommendation. After the decision, store the outcome with the research. A repository full of findings and no actions makes it difficult to learn whether the organization asked good questions or used the answers well. When reporting qualitative work, keep quotations in context and explain how themes were developed. Avoid using one vivid comment as proof of prevalence. When reporting quantitative work, show denominators and uncertainty. Both practices let stakeholders understand the evidence without flattening people into convenient support for a recommendation. --- # Strategic Market Research | Surface Glossary URL: https://surface.thesurface.network/glossary/strategic-market-research Strategic market research is research designed to inform consequential, longer-horizon business choices. It may examine market boundaries, customer segments, unmet needs, category movement, competitors, regulation, willingness to pay, routes to market, or product direction. The work differs from a tactical study because it changes where the company will compete or how it will allocate meaningful resources. A strategic decision contains several connected uncertainties. Entering a market, for example, depends on demand, access, competition, product fit, economics, regulation, and organizational capacity. No single survey or market-size estimate resolves the whole choice. Research must connect several forms of evidence while keeping their definitions and confidence separate. Start with the decision and the commitments it would create. Build an uncertainty map before collecting more information, then sequence research according to consequence and reversibility. Early secondary work may eliminate an option cheaply. Primary research can examine needs and buying processes. Behavioral or experimental evidence may test a remaining assumption. Synthesis should show how the evidence changes the choice, not merely summarize every source. 1. Define the strategic choice, alternatives, deadline, owner, and cost of delay. State which commitments can be reversed and which would lock in capital, hiring, product work, or reputation. 2. List the assumptions that must hold. Group them under market, customer, competitive, product, economic, regulatory, and execution questions. Rank each assumption by uncertainty and consequence. 3. Design an evidence portfolio. Use existing internal and external material first, then add interviews, surveys, observation, experiments, or expert review where the current evidence cannot support the required claim. 4. Synthesize into scenarios. Define plausible market and response conditions, show evidence for each, and calculate where the decision changes under alternate assumptions. Preserve disagreements and weak evidence. 5. Make the decision and establish monitoring. Record the chosen option, rejected alternatives, assumptions, confidence, owner, early indicators, and the observation that would trigger reconsideration. Research quality is reflected in decision relevance, source traceability, sample fit, definition consistency, treatment of contradictory evidence, and sensitivity to alternate assumptions. Business impact can include a changed segment, avoided investment, revised launch order, better pricing boundary, or earlier stop. A project that confirms the original plan may still be useful, but reviewers should test whether the method gave disconfirming evidence a fair chance. Maintain a decision record beside the research archive. Every major claim should link to a dated source, method, population, and analyst note. Separate facts, estimates, interpretations, and recommendations. Invite reviewers with different incentives, including someone who does not own the proposed initiative. Update assumptions when the market moves, and mark old conclusions as superseded rather than silently replacing the material that supported them. - Which strategic choice and resource commitment will the research inform? - Which assumptions carry the greatest uncertainty and downside? - What evidence level is proportionate to the decision's reversibility? - Who can challenge market boundaries, samples, and sponsor bias? - Which indicators will reopen the decision after action begins? Research scope should be asymmetric. Spend more effort on assumptions that could reverse the choice and less on facts that would not change it. Leaders must also decide how much uncertainty they can accept by the deadline. Waiting for perfect knowledge is itself a strategic choice, with a cost that belongs in the analysis. Use staged commitments when evidence cannot arrive before the decision date. A limited launch can buy information while capping downside and preserving later options. A common failure is commissioning a broad market report with no explicit decision. The team gathers market size, trends, personas, and competitor profiles, then presents a long deck that does not state which option the evidence supports. Another failure chooses the market boundary after seeing which definition produces the largest number. Return to the choice and write the few assumptions that separate the alternatives. Reclassify existing material against those assumptions, discard decorative facts, and collect only the missing evidence that could change the result. If the evidence remains weak, narrow the commitment through a pilot, partnership, or staged entry and monitor the uncertain assumption directly. --- # Strategies for Sales and Marketing | Surface Glossary URL: https://surface.thesurface.network/glossary/strategies-for-sales-and-marketing Strategies for sales and marketing are coordinated choices about where a company will compete, how it will create demand, and how it will help buyers move toward a purchase. They may include segment focus, category education, account-based programs, product-led growth, partner channels, content-led demand, customer advocacy, paid demand capture, event programs, or targeted outbound. The strategy should connect marketing reach and persuasion with sales capacity, follow-up, proof, and deal work. It is more durable than a campaign and more specific than a revenue target. Marketing and sales need one view of the priority market, buying group, problem, value, alternatives, qualification, and expected path. They also need agreement on how opportunities will be created, supported, and measured. Without those choices, teams can optimize incompatible local goals. A shared strategy does not require identical work. Marketing may build category demand while sales concentrates on a smaller active account set. Use market research, customer evidence, product economics, sales history, competitive conditions, and operational capacity. State the strategic hypothesis and the conditions it depends on. Convert it into coordinated programs, handoffs, enablement, service levels, and a measurement model. Keep sourced, influenced, and sales-created outcomes distinct. Review the strategy at a cadence suited to the sales cycle. Change it when evidence challenges a core assumption, not whenever a weekly metric moves. A company has broad traffic and weak enterprise pipeline. Research shows that security teams value its audit history, but the site treats the feature as a technical detail. Marketing creates a focused enterprise narrative and proof library. Sales targets accounts with regulated workflows and uses the same evidence in discovery. Operations improves routing for those accounts. The strategy combines positioning, demand, account selection, and follow-up around one market belief. Choose a motion the organization can serve. A campaign that creates more qualified demand than sales can contact may damage buyer experience. An account strategy without research or content support can reduce to a list and an outreach quota. State headcount, expertise, budget, data, product, and implementation constraints inside the strategy. Capacity is part of the market promise. --- # Structured Data | Surface Glossary URL: https://surface.thesurface.network/glossary/structured-data Structured data is information organized according to a defined schema. Fields have names, values follow expected types or formats, and records share enough consistency for software to search, filter, join, validate, aggregate, and automate them. Examples include database tables, CRM records, analytics events, product catalogs, and well-formed JSON objects. In SEO, structured data often refers more narrowly to Schema.org markup embedded in a page. Both uses share the idea of explicit labels and relationships that machines can interpret without reading free-form prose. Creating structured data requires more than choosing columns. The team defines the business object, field meanings, identifiers, allowed values, source systems, relationships, and behavior for missing data. It then maintains that contract as forms, vendors, products, and reporting needs change. 1. Name the object represented by one record, such as lead, account, campaign, article, product, or event. A clear row grain prevents several different entities from being mixed together. 2. Define fields and types in ordinary language. State whether a value is submitted, enriched, calculated, or manually assigned, and identify the system responsible for the current version. 3. Create stable identifiers and relationships. Email alone may not identify a person forever, and company name alone may not join a lead to the correct account. 4. Validate records when they enter and change. Check required values, formats, allowed categories, duplicates, and relationships before the data triggers a consequential action. 5. Monitor quality and update the schema through controlled changes. Preserve mappings or migration logic so older records remain interpretable after a field or category changes. Useful quality measures include completeness, validity, accuracy, consistency, uniqueness, timeliness, and referential integrity. The priority depends on the workflow. A duplicate account can distort pipeline, while a stale territory field can send an active buyer to the wrong rep. For structured data, create a field-level contract for the records that drive real actions. The contract should state grain, type, source, provenance, freshness, allowed values, null behavior, identifier logic, transformation, and downstream use. Keep raw, normalized, inferred, and manually reviewed values distinct. When sources conflict, record the selected value and the rule that selected it. A reviewer should be able to reverse a merge or correction without reconstructing the original file from an old export. Use separate measures for the correctness, reliability, efficiency, and business value of structured data. A process can be accurate on completed cases and still fail through delays or missing coverage. It can be reliable and still create little value. Report denominators, exclusions, time windows, and unresolved cases so leaders can see which part of the system actually improved. Review the process with the team that receives its output. Their acceptance, corrections, and workarounds reveal whether structured data functions in the real operating environment rather than only inside its source tool. Give the team receiving output from structured data a visible way to accept, correct, reject, or escalate it. Their response should return to the shared record with a reason and timestamp. Review those reasons by workflow version and segment. This feedback shows whether structured data is reducing work, moving the right cases, and preserving enough context for the next person to act. End the structured data review with open questions and their owners. An unresolved item can remain open, but it should not disappear into an apparently final configuration. - Choose the grain and purpose of each structured record. - Assign a source of truth and provenance rule for every critical field. - Define identifiers, relationships, and duplicate handling. - Set validation thresholds according to the action the data will trigger. - Create ownership for schema changes, documentation, access, and retention. A schema always simplifies reality. Good design preserves the distinctions the business needs and leaves uncertain values uncertain. Forcing every lead, source, or objection into a convenient category may improve chart cleanliness while making the operation less truthful. A common failure is allowing each tool to define the same field differently. One platform uses lifecycle stage to mean buyer readiness, another uses it to mean sales ownership, and a report joins them as if they were equal. The rows remain structured, but the semantics are broken. Write the definitions, separate fields that carry different meanings, and trace critical metrics and automations to their source values. Keep raw and normalized data distinct so future reviewers can see what changed. --- # Structured Data Analysis | Surface Glossary URL: https://surface.thesurface.network/glossary/structured-data-analysis Structured data analysis is the examination of information organized in consistent rows, columns, objects, or relational tables. Analysts can filter, group, join, count, calculate rates, build time series, and test relationships because the dataset has an explicit schema. Marketing examples include comparing lead-to-meeting rates by source, measuring response time by territory, tracking content performance by topic, and reconciling campaign spend with pipeline. The schema enables calculation, while the business definitions determine whether the calculation means what the report claims. A repeatable analysis can expose where the operation loses value. It can also create false confidence when joins, exclusions, and timestamps stay hidden. A table with precise percentages may exclude unmatched leads or compare cohorts with different observation windows. Choose the unit of analysis, define the metric and time window, inspect missing and duplicate records, validate joins, and keep transformations visible. Reconcile key totals with source systems and report unmatched or excluded records. Use qualitative evidence to explain patterns the structured fields cannot. A practical review of structured data analysis should start with meaning before syntax. Identify what the item represents, which visible or operational facts define it, and which system can keep those facts current. Set an explicit review trigger rather than relying on memory. A product launch, schema change, prompt revision, new data source, campaign shift, or sales objection may justify a fresh check. The practical test for structured data analysis is whether it improves a real decision without creating hidden definitions, unsupported confidence, or an unowned handoff to another team. A team analyzes speed to lead. It keeps one row per valid demo submission, calculates minutes from submission to first human response, separates business hours from calendar hours, and reports median and distribution by segment. Records without a response remain visible instead of being dropped from the calculation. The analysis is only as clear as its grain and definitions. Document what one row represents, which records were included, and how every derived field was calculated. --- # Structured Data Analytics | Surface Glossary URL: https://surface.thesurface.network/glossary/structured-data-analytics Structured data analytics is the analysis of information stored in consistent fields, rows, tables, objects, and relationships. Marketing examples include grouping leads by channel, calculating conversion by lifecycle stage, comparing campaign spend with pipeline, and tracking changes in time to first response. The structure makes aggregation possible, but it does not guarantee a sound conclusion. A dashboard may calculate conversion perfectly from inconsistent stage definitions. A channel comparison may look precise while excluding records that failed a campaign join. Analysts still need to understand collection, missingness, identity, and business process. Structured analysis can turn large operational datasets into repeatable decisions. Teams can find segments with poor routing acceptance, pages that attract qualified accounts, or campaigns that create many leads and little pipeline. The results become more useful when analysts connect them with unstructured evidence such as call notes and buyer feedback. Start with a metric definition and grain. Decide whether each row represents a session, lead, account, opportunity, campaign, or time period. Validate identifiers and joins, keep raw fields separate from cleaned fields, and document exclusions. Reconcile important totals with the systems used by finance and sales. Teams can make structured data analytics easier to maintain by treating it as a data contract. Name the object, its stable identifier, its permitted properties, and the source responsible for each value. Choose a measure that follows the actual job. Validity, coverage, reviewer effort, conversion, response time, source quality, and revenue can describe different outcomes and should stay separate. A short decision record should state the current approach, evidence, owner, date, and condition for revision. That makes structured data analytics useful beyond the person who first implemented it. A team studies demo conversion by source. It uses one row per submitted form, joins each lead to its first meeting and opportunity, and calculates form-to-meeting rate within 30 days. The analyst separately reports unmatched leads and duplicate submissions. Sales-call notes are sampled to explain why one high-volume source produces weaker meetings. A chart is the end of a chain of definitions. Structured data analytics is trustworthy when a reviewer can trace the result back through the row grain, transformations, joins, exclusions, and original records. --- # Structured Data Formats | Surface Glossary URL: https://surface.thesurface.network/glossary/structured-data-formats Structured data formats are standardized ways to represent fields, values, types, and relationships so software can parse them consistently. On web pages, common structured-data syntaxes include JSON-LD, Microdata, and RDFa. These syntaxes can express vocabularies such as Schema.org. In broader data work, JSON, XML, CSV, relational tables, and other formats may carry structured records. Format and vocabulary solve different problems. JSON-LD describes how the data is written. Schema.org supplies terms such as Organization, Product, name, and offers. JSON-LD places linked data in a script block, separate from the visible HTML. It is often easier to generate and maintain from CMS fields. Microdata adds attributes directly to HTML elements. RDFa also uses HTML attributes and supports RDF relationships. All three can represent valid structured data when implemented accurately. Search feature support and platform guidance may favor one syntax for a particular use. Technical validity alone does not guarantee a rich result. Start with the consuming system, supported vocabulary, update workflow, and source of truth. Prefer a format the team can keep synchronized with visible content. Validate syntax, required properties, URLs, identifiers, dates, and relationships. Avoid creating several independent copies of the same price, author, or event data. Document the template owner and retest after CMS or page changes. An event page stores name, start date, location, image, status, and ticket URL in the CMS. The template renders those values for people and generates Event markup in JSON-LD from the same fields. Editors update one source. Automated checks flag missing dates and invalid URLs before publication. The format makes the facts readable to machines without becoming a hidden alternate version of the event. A file can be syntactically structured and still have a weak model. JSON with inconsistent names, missing identifiers, and ambiguous relationships is hard to use. A sound data model defines entities, properties, types, constraints, and relationships before choosing the transport or markup format. On the web, the visible page, CMS fields, vocabulary, and JSON-LD should express one maintained model rather than four loosely connected copies. --- # Structured Data in SEO | Surface Glossary URL: https://surface.thesurface.network/glossary/structured-data-in-seo Structured data in SEO is code that expresses page information through a defined vocabulary and format. Most SEO implementations use Schema.org terms in JSON-LD to identify a page's main entity and facts such as its author, publication date, price, rating, location, or event schedule. Search engines use structured data to understand content and, for supported page types, assess eligibility for enhanced results. The code supports interpretation. It does not replace crawlability, index eligibility, helpful content, links, or a clear page experience. A page can rank without schema, and valid schema can appear on a page that never earns a rich result. The process starts with search intent and page purpose, then moves into data modeling. An SEO lead should be able to explain why the page type deserves a particular entity, which visible fields supply the properties, and how the team will keep those fields accurate after launch. 1. Audit indexable templates and identify the main entity on each one. Avoid adding a specialized type to pages that only mention the entity in passing. 2. Match the page to an appropriate Schema.org type and any current search feature requirements. Required and recommended properties may differ from what the vocabulary technically allows. 3. Implement JSON-LD from the page's source data. Reuse stable organization, author, and product identifiers across templates so the graph describes consistent entities. 4. Validate both syntax and meaning. Inspect the rendered production page, compare every material property with visible content, and test pages with missing or unusual data. 5. Watch search reporting and template health. Markup errors, indexing changes, or declining enhancement impressions should lead to investigation rather than an automatic rewrite. Track valid coverage by template, error counts, pages eligible for supported enhancements, and the organic performance of those page groups. Use annotations when markup changes so the team can compare before and after behavior. The comparison remains observational unless the team runs a controlled test, since content, rankings, and search presentation change for many reasons. For structured data in SEO, the operating record should begin with one representative production page and trace every structured claim back to a visible field or maintained system. Record the entity type, canonical URL, stable identifiers, generation method, validation result, template owner, and the search feature or machine interpretation the team expects the markup to support. Repeat the review with an imperfect page, such as one missing optional data or containing several related entities. That second page usually reveals whether the template has a real data model or a hand-built happy path. Create a short release checklist for structured data in SEO and assign each item to a role. Include source verification, permissions, privacy, required approvals, error visibility, downstream compatibility, and rollback. Keep the checklist close to the workflow so it changes when the workflow changes. After release, review exceptions before aggregate performance because an average can improve while a small number of high-value cases fail badly. Connect the local structured data in SEO workflow to the decision that follows it. Documentation should show what the next operator receives and which context must survive the handoff. Before expanding structured data in SEO, compare several outputs with the source material and with the decision made by a competent operator. Record false positives, false negatives, missing cases, and disagreements about definitions. Use that sample to update the rule, test set, documentation, or training rather than explaining every error as an isolated exception. The review should end with a named change and an owner, even when the change is to keep the current scope. For structured data in SEO, note unresolved questions beside the approved process. Visible limitations invite review; hidden assumptions tend to survive until a customer, report, or integration exposes them under worse conditions. - Which page types have a clear search use case for structured data? - Which source system controls every property included in the markup? - Who approves changes to entity names, identifiers, dates, prices, and ratings? - Which validation failures block publishing and which can enter a repair queue? - How often will the team audit a representative sample of rendered pages? Structured data belongs in the same release conversation as canonical tags, metadata, internal links, and page rendering. Keeping it outside that process encourages drift. A quarterly spreadsheet audit cannot compensate for a template that generates incorrect values every day. Teams often measure the implementation by the number of properties or schema types deployed. That rewards complexity even when the extra fields are empty, unsupported, or inconsistent. Another failure appears when marketers mark up content that visitors cannot see, especially ratings, FAQs, or offers created solely for the code block. Simplify the graph, remove claims without a maintained source, and focus on the page classes that matter to discovery and conversion. Then use search reports as one diagnostic input alongside rankings, crawl data, content quality, and buyer behavior. --- # Structured Data in JSON-LD | Surface Glossary URL: https://surface.thesurface.network/glossary/structured-data-json-ld Structured data in JSON-LD is machine-readable information expressed with JavaScript Object Notation for Linked Data. On a web page, it usually appears inside a script element with the type application/ld+json and uses a vocabulary such as Schema.org to describe entities and relationships. JSON-LD separates the structured graph from visible HTML markup. That makes it easier to generate from CMS fields and maintain across templates than syntax that wraps individual page elements. The block still has to match visible content and render reliably for crawlers. The format supports stable identifiers and connections among organization, author, article, product, event, offer, and other nodes. It also reduces the temptation to tie the implementation to fragile CSS selectors or presentation markup. Valid JSON alone does not make the statements accurate. Choose the page's primary entity, map maintained facts to valid properties, and reuse @id values for repeated entities. Generate the block from source data, validate syntax and search-feature requirements, inspect the rendered production page, and monitor errors after template changes. A practical review of structured data in JSON-LD should start with meaning before syntax. Identify what the item represents, which visible or operational facts define it, and which system can keep those facts current. Choose a measure that follows the actual job. Validity, coverage, reviewer effort, conversion, response time, source quality, and revenue can describe different outcomes and should stay separate. A short decision record should state the current approach, evidence, owner, date, and condition for revision. That makes structured data in JSON-LD useful beyond the person who first implemented it. An article page emits a BlogPosting node with headline, canonical URL, publication and modification dates, author @id, publisher @id, and image. The author and publisher identifiers connect to maintained Person and Organization nodes rather than recreating anonymous objects on every post. JSON-LD is the container and linked-data syntax. Schema.org supplies the vocabulary, while the visible page and source systems supply the truth the block is allowed to express. --- # Structured Data Management | Surface Glossary URL: https://surface.thesurface.network/glossary/structured-data-management Structured data management is the practice of designing, collecting, storing, validating, integrating, securing, and maintaining data that follows a defined schema. In marketing and revenue teams, this includes lead, account, campaign, lifecycle, attribution, content, product, and activity records. The work sits behind routine actions. A demo request can route correctly only when country, company, segment, owner, and availability fields have consistent meanings. A pipeline report can reconcile with sales only when lifecycle changes, timestamps, and opportunity relationships are preserved across systems. Management prevents a shared field from becoming several private interpretations. Without definitions and ownership, source means first touch in one report and latest campaign in another. Employee count may come from the buyer, enrichment vendor, or CRM account. Automation then acts on whichever value happened to arrive last. Define business objects and field contracts, assign source systems, record provenance, validate data at entry, and monitor quality by workflow. Use controlled changes for schema updates and preserve a mapping layer when tools use different names or value sets. Retention, access, and deletion rules belong in the same design. For structured data management, begin with the page or record a machine must understand. Write down the primary entity, the maintained source for each fact, and the decision the structured representation should support. Review a sample of real cases before relying on an aggregate score. The sample should include incomplete, conflicting, and high-value records because averages often hide the failures with the largest business cost. Place the documentation for structured data management beside the workflow or decision it affects. That keeps definitions, evidence, ownership, and later corrections available to the people who need them. A company centralizes inbound lead data from three forms and two enrichment providers. It defines one lead schema, keeps the submitted and enriched company sizes in separate fields, calculates a normalized band, and records the timestamp and provider for each value. Routing uses the normalized field, while reviewers can still inspect the sources when a rep disputes an assignment. Structured data management succeeds when records support consistent decisions and can explain where their values came from. A wide warehouse with unclear semantics is organized storage, not a trusted operating layer. --- # Structured Data Set | Surface Glossary URL: https://surface.thesurface.network/glossary/structured-data-set A structured data set is a collection of records organized according to a consistent schema. Each row or object represents a defined unit, fields carry expected meanings and types, and identifiers or keys connect related records. Examples include a lead table, product catalog, campaign log, or analytics event stream. Structure makes the collection queryable, but quality still depends on the records. A dataset can follow the same columns and contain stale, duplicated, or incorrectly joined values. It can also hold free text inside a field while remaining structured at the record level. A well-defined dataset supports repeatable analysis, automation, and exchange between tools. It lets another person know what one record represents and how a value was collected. Without a data dictionary and provenance, a neat table can still produce several incompatible interpretations. Document the grain, field definitions, allowed values, units, timestamps, unique keys, relationships, source systems, refresh schedule, and known limitations. Keep raw data separate from cleaned or derived fields. When the schema changes, version the definition and explain how old records map to the new one. For a structured data set, begin with the page or record a machine must understand. Write down the primary entity, the maintained source for each fact, and the decision the structured representation should support. Keep the source beside the result and make changes reversible. This protects the operation when a definition, vendor, model, template, or buyer behavior changes after the original decision. The final review should ask what changed for a buyer or operator. If a structured data set only creates another field, page, prompt, or dashboard, its role remains incomplete. A content performance dataset uses one row per URL per day. It stores canonical URL, date, page type, topic, organic clicks, AI citations, sessions, form submissions, and source timestamps. Topic is a maintained category, while conversion rate is calculated from visible input fields rather than pasted as a separate unexplained number. A structured data set is a contract about records and meaning. The schema should make reuse safer, and the documentation should make the limits impossible to miss. --- # Structured Data Types | Surface Glossary URL: https://surface.thesurface.network/glossary/structured-data-types Structured data types can mean two related things. In databases and programming, types describe values such as text, integer, decimal, boolean, date, timestamp, array, or object. In web structured data, Schema.org types describe entities such as Organization, Person, Article, Product, Event, and Review. Both uses constrain meaning. A field typed as a date should hold a valid date, and an Event entity should use properties appropriate to an event. Choosing a type lets systems validate values and understand which operations or relationships make sense. Loose typing creates quiet errors. A campaign budget stored as formatted text cannot be summed reliably. A product price stored without currency is ambiguous. A page labeled as several unrelated Schema.org types may validate in pieces while failing to communicate a clear primary entity. Choose the narrowest type that reflects the real value or entity, document null behavior and units, and validate at entry. For web markup, start with the page's main subject and include only visible, maintained properties. For operational data, keep raw values when normalization or conversion changes them. A practical review of structured data types should start with meaning before syntax. Identify what the item represents, which visible or operational facts define it, and which system can keep those facts current. Set an explicit review trigger rather than relying on memory. A product launch, schema change, prompt revision, new data source, campaign shift, or sales objection may justify a fresh check. The practical test for structured data types is whether it improves a real decision without creating hidden definitions, unsupported confidence, or an unowned handoff to another team. A campaign record stores startDate and endDate as dates, budget as a decimal with a separate currency code, isActive as a boolean, and channel as a controlled category. A campaign article on the website remains an Article entity rather than being mislabeled as the campaign record itself. Types make data safer to use because they limit interpretation. The team still has to define the business meaning, source, and relationship behind each typed value. --- # Structured Data Validation | Surface Glossary URL: https://surface.thesurface.network/glossary/structured-data-validation Structured data validation is the process of checking data against defined rules. A validator may test syntax, required fields, data types, allowed values, ranges, formats, uniqueness, and relationships. On web pages, validation also checks whether schema markup uses valid vocabulary and matches visible content. Passing one validator does not prove the data is true. An email can match the expected format and still belong to the wrong person. JSON-LD can be syntactically valid and still describe a rating the page never displays. Validation needs both machine rules and business review. Validation stops predictable errors before they trigger routing, reporting, personalization, or search markup. It also makes exceptions visible. A record that cannot be classified should enter a review state rather than being forced into the nearest accepted value so the dashboard stays tidy. Apply cheap deterministic checks at entry, then use cross-field and source checks for material decisions. Keep error codes specific enough to diagnose the cause. Monitor failure rates by source and template, and test validation rules whenever a form, integration, schema, or business definition changes. For structured data validation, begin with the page or record a machine must understand. Write down the primary entity, the maintained source for each fact, and the decision the structured representation should support. Keep the source beside the result and make changes reversible. This protects the operation when a definition, vendor, model, template, or buyer behavior changes after the original decision. The final review should ask what changed for a buyer or operator. If structured data validation only creates another field, page, prompt, or dashboard, its role remains incomplete. A demo form requires a business email and country. The system checks syntax, blocks disposable domains, confirms that the country value belongs to an allowed list, and verifies that the selected territory has an active owner. If enrichment disagrees with the submitted country, the record routes to review and preserves both values. Validation protects the contract between systems. The strongest rules state what failed, preserve the original value, and give the workflow an explicit response to uncertainty. --- # Structured Database | Surface Glossary URL: https://surface.thesurface.network/glossary/structured-database A structured database stores information according to an explicit schema. The schema defines entities or tables, records or rows, fields or columns, data types, constraints, identifiers, and relationships. Relational databases are a common form, though structured storage can also use other models. The defining feature is that the shape and meaning of data are known enough for consistent validation and queries. Marketing and content systems use structured databases for accounts, contacts, campaigns, pages, queries, products, events, and performance records. Structure makes it possible to join an article to its topic, an account to its contacts, or a conversion to a dated campaign definition. That work depends on stable identifiers and grain. A field labeled "customer" remains ambiguous if nobody knows whether it describes a person, account, contract, or current lifecycle state. Design begins with the questions and operations the database must support. Model the real entities and their relationships, choose identifiers, and state the grain of each table. Then define data types, required values, uniqueness, references, timestamps, and update behavior. Applications read and write through controlled queries or interfaces, while indexes and physical design support expected access patterns. 1. Name the entities and use cases. Separate concepts such as person, company, domain, page, query, campaign, and event when they have different lifecycles or many-to-many relationships. 2. Choose primary identifiers and relationship fields. Avoid using a display name as identity. Decide how merges, splits, deleted records, aliases, and source-system identifiers will be preserved. 3. Define the schema and constraints. Set field types, allowed nulls, reference integrity, uniqueness, default behavior, timestamps, and units. Document business meaning beside technical structure. 4. Build ingestion and change paths. Validate writes, keep lineage, handle late or duplicate events, and version transformations. Provide quarantine or review for data that cannot be accepted safely. 5. Test queries, permissions, recovery, and performance. Use representative volumes and edge cases. Monitor slow queries, failed writes, constraint violations, unexpected row counts, access changes, and backup restoration. Database quality can be observed through validity, completeness, duplicate rate, relationship integrity, freshness, query reliability, latency, incident frequency, recovery time, and user trust in downstream outputs. Technical availability alone is insufficient if records use disputed definitions or important joins silently drop unmatched entities. Reconcile representative queries with source systems after schema or pipeline changes. Track unmatched relationships separately because a successful query can still omit the records that most need attention. Maintain a data dictionary that states each table's grain, field meaning, unit, source, authority, sensitivity, refresh, permitted values, downstream use, and owner. Schema migrations should name the reason, compatibility effect, rollback path, and dependent systems. Give access according to role and purpose. Analysts should use shared definitions for core entities rather than rebuilding customer or content logic in every query. - Which questions, transactions, and system actions must the database support? - What is the grain and stable identity of every entity? - Which rules belong in database constraints, application logic, or human review? - How will history, lineage, deletion, consent, and schema changes be handled? - Who owns technical operation and who owns business meaning? A structured database is different from structured data markup on a web page. A database organizes stored operational or analytical information. Web markup describes visible entities and relationships to machines that read the page. A content team may generate markup from a database, but the two layers have different validation, ownership, and failure paths. A common failure is placing several meanings in one flexible table because it is fast to launch. New fields accumulate, blanks mean different things, names become identifiers, and one row no longer has a consistent grain. Queries still run, which lets incorrect joins and duplicated counts travel into dashboards and automated decisions without obvious errors. Document current usage before changing the schema. Identify the entities and relationships hidden in the table, create stable identifiers, migrate one dependent workflow at a time, and reconcile outputs before switching authority. Preserve legacy mappings long enough to explain historical records, then retire writes to the old structure. --- # Structured vs. Unstructured Data | Surface Glossary URL: https://surface.thesurface.network/glossary/structured-vs-unstructured-data Structured data follows a defined model: fields have names, values occupy predictable locations, and records can be sorted, joined, or validated through known rules. Unstructured data does not arrive in a fixed table or object shape. Email bodies, call transcripts, documents, images, open-text form responses, and videos are common examples. The distinction matters because the two forms require different operations. A CRM can query an industry field directly. It cannot reliably answer what objections appear in sales calls until a person or system extracts those concepts from transcripts. Many marketing workflows turn unstructured evidence into structured fields, then keep a link to the source so the reduction can be audited. Both forms can describe the same customer, campaign, or event. A call transcript is unstructured, while the call date, account ID, speaker roles, objection category, and next-step status may be structured. JSON can contain well-defined fields and free-text notes in the same record. The boundary therefore describes the representation, not the inherent nature of the fact. Structured data Unstructured data Uses a defined schema with named fields and expected types Uses prose, media, or free-form content without a fixed field model Easy to filter, aggregate, join, and validate with explicit rules Usually requires reading, search, extraction, classification, or embedding before analysis Examples include CRM records, event tables, analytics rows, and product databases Examples include emails, PDFs, call transcripts, images, and open-ended survey answers Quality issues appear as missing values, invalid types, duplicates, or broken relationships Quality issues appear as ambiguity, missing context, poor transcription, unsupported interpretation, or inaccessible formats Typical owners include data, RevOps, analytics, and application teams Typical owners include research, content, sales, support, legal, and knowledge-management teams Structured data makes repeated computation easier because the system knows where each value belongs. Unstructured data preserves more of the original language and context, which is often where buyer motivation, uncertainty, and nuance live. Converting everything into fields can make reporting efficient while erasing the evidence that would explain the result. A practical data system often keeps both forms together. Store the structured fields needed for routing, reporting, and automation, then retain a reference to the original document, transcript, message, or media. When a model or analyst extracts a category from unstructured evidence, record the method, version, confidence, and source location. That lets the business use the label without pretending the interpretation was present in the original material. A demand generation team receives 2,000 demo requests. The form captures company size, country, product interest, and source in structured fields. It also asks, in an open text box, what the prospect wants to solve. Routing can use the structured fields immediately. To learn which problems are growing, the team classifies the free-text answers into a controlled set of themes, samples the original language for accuracy, and records both the theme and the source response. The workflow decision is rarely whether to keep only one form. Store structured fields for reliable operations and retain unstructured source material when its context affects interpretation. Define how extracted labels are reviewed, versioned, and traced back to the evidence. --- # Survey in Market Research | Surface Glossary URL: https://surface.thesurface.network/glossary/survey-in-market-research A survey in market research is a structured instrument used to collect self-reported information from a defined sample. Surveys can estimate awareness, behavior, experience, preference, consideration, or stated intention when the population, sampling method, questions, field conditions, and analysis support the claim. Surveys are strong at asking many people the same questions in a comparable form. They are weaker when respondents cannot accurately recall an event, interpret wording differently, or answer hypothetically about behavior they have never faced. Interviews, observation, experiments, and behavioral data may be better for those questions or may provide necessary context. Start with the decision and the population, then write the analytical plan before polishing question wording. Decide which variables must be measured, which groups need comparison, and what sample can support the intended precision. Pilot the instrument with people who resemble the target respondents and revise problems before full fielding. 1. Define the research decision and target population. State who qualifies, which claims the survey should support, and how the result could change an action. 2. Choose the sample and recruitment method. Document the frame, screener, quotas, incentives, expected response, and groups the method is likely to miss. 3. Design the questionnaire. Use ordinary language, one idea per question, balanced options, appropriate recall periods, and an honest way for respondents to say they do not know. 4. Pilot and field consistently. Test comprehension, length, randomization, mobile display, branching, duplicate protection, and data capture before launch. Preserve field dates and instrument versions. 5. Clean, analyze, and report within scope. Apply exclusions and weighting transparently, compare planned segments, review open responses, and keep sampling and measurement limits beside the findings. Survey quality is reflected in sample coverage, qualification, completion, breakoff, speed, straightlining, missingness, duplicate risk, open-response quality, and consistency across related items. A response rate alone does not establish representativeness. Weighting can correct known imbalances within limits; it cannot create missing opinions for groups the survey never reached. Maintain a survey record that includes the decision, questionnaire, answer options, branch logic, sample frame, recruitment source, quotas, incentives, field dates, exclusions, weighting, codebook, and final data. Store raw responses separately from cleaned fields. If a response is removed or recoded, preserve the rule and original value. Review the instrument with a subject expert and someone independent of the desired result. Look for assumptions inside the question, overlapping options, missing alternatives, vague time periods, and scales that push respondents toward agreement. For sensitive or commercial topics, explain who is asking, how answers will be used, and what identifying data is retained. - Which population must the findings describe? - Does the team need an estimate, a group comparison, or exploratory direction? - Which concepts can respondents report accurately in this format? - What sample size and recruitment method are defensible for the intended claim? - Who will approve exclusions, weighting, interpretation, and data retention? Write the tables and comparisons the team expects to use before collecting responses. This exposes questions that lack a clear purpose and segments too small for interpretation. It also limits the temptation to search through dozens of cuts until one supports the preferred story. A common failure is using a convenience audience and presenting the result as the market. Newsletter readers, existing customers, or social followers may answer honestly while differing sharply from lost deals or category buyers. Leading questions and forced-choice options can then manufacture apparent agreement around the company's existing language. Narrow the claim to the sampled group, disclose the recruitment method, and repeat collection if the missing population is material. Remove or rewrite biased items, report uncertainty, and use interviews to understand confusing results. When a survey cannot support a percentage claim, it may still provide directional themes if described honestly. Before publishing the revised result, compare it with the original decision threshold. If the correction changes the recommended action, state that plainly and preserve both versions. Survey credibility depends partly on whether the organization will amend a convenient conclusion when the method no longer supports it. --- # Technology Content Marketing | Surface Glossary URL: https://surface.thesurface.network/glossary/technology-content-marketing ## What is technology content marketing? Technology content marketing uses useful material to help people understand, evaluate, buy, implement, or operate a technology product or service. It can include technical guides, research, product comparisons, architecture explanations, demonstrations, documentation, customer evidence, webinars, newsletters, and tools. The intended reader may be a user, technical evaluator, business buyer, or internal champion. Technology purchases often involve people with different questions. An engineer may examine compatibility and failure behavior, security may require controls and evidence, finance may compare cost, and an executive may need the business case. One generic article rarely satisfies the whole buying group. Content needs a named reader and decision, even when several assets form one connected journey. Vague claims are easy to publish and hard for a buyer to verify. Technical audiences look for specific boundaries, examples, documentation, source material, and an honest account of tradeoffs. Content also creates expectations the product and sales team must meet. An unsupported performance claim can enter a deal, circulate internally, and damage trust long after the campaign ends. Build the program around recurring questions from search, sales calls, support, product usage, communities, and implementation work. Assign a subject-matter reviewer for claims that require expertise. Keep product facts linked to current documentation and version-sensitive screenshots. Separate category education from product positioning, then connect them through relevant next steps rather than forcing a sales pitch into every page. ## How to plan technology content Choose formats according to the evidence and task. A concise reference page may define a term, while an architecture guide needs diagrams and implementation constraints. Customer proof should state the situation and method behind an outcome. Set factual review dates for product, pricing, integration, security, and competitor claims. Measure qualified discovery, useful engagement, assisted evaluation, sales reuse, conversion, and maintenance cost. A data platform sees many prospects ask whether it can handle regional data residency. Instead of publishing broad security copy, the team creates a plain-language overview for procurement, a technical architecture page for security reviewers, and an implementation checklist for administrators. Product and legal approve the claims. Sales uses the right asset for each role and records which questions remain unresolved. Technology content earns trust through precise audience fit, verifiable claims, useful detail, and an operating plan for keeping facts current. --- # Three Types of Prompt Engineering | Surface Glossary URL: https://surface.thesurface.network/glossary/three-types-of-prompt-engineering A common three-part explanation of prompt engineering uses zero-shot, one-shot, and few-shot prompting. Zero-shot gives instructions without an example. One-shot supplies one demonstration. Few-shot supplies several demonstrations that show the desired pattern or clarify difficult boundaries. These are three example-based prompt patterns, not the complete field. Production systems may also use retrieval, tools, multi-stage routing, structured outputs, fine-tuned models, or human approval. The zero-one-few taxonomy remains useful because it shows how examples change a model's interpretation of a task. Examples can teach format and judgment faster than another paragraph of instructions. They can also introduce bias. A few-shot set that contains only easy enterprise leads may make the classifier unreliable for small companies, nonprofits, or incomplete records. The examples should cover meaningful boundaries rather than repeat the same obvious case. Begin zero-shot when the task and labels are clear. Add one example when the required shape is unusual. Use a small diverse set when the model needs to learn distinctions, tone, or edge-case handling. Evaluate all versions on the same held-out cases so the added examples earn their space. Put the three common types of prompt engineering under the same change discipline as other business logic. The owner should know the prompt version, data sources, model, tools, expected behavior, and the consequences of an incorrect output. Review a sample of real cases before relying on an aggregate score. The sample should include incomplete, conflicting, and high-value records because averages often hide the failures with the largest business cost. Place the documentation for the three common types of prompt engineering beside the workflow or decision it affects. That keeps definitions, evidence, ownership, and later corrections available to the people who need them. A prompt classifies customer comments as bug, feature request, billing, or unclear. The zero-shot version handles direct comments. The team then adds four examples showing ambiguous requests and mixed issues. Few-shot accuracy improves, but the owner keeps the test cases separate from the demonstrations to avoid scoring the prompt on examples it has already seen. Use the fewest examples that produce stable behavior. A larger prompt costs more, can anchor the model too tightly, and becomes harder to maintain when the business labels change. --- # Types of Competitors | Surface Glossary URL: https://surface.thesurface.network/glossary/types-of-competitors Types of competitors describe the different ways another option can compete for the same buyer, budget, or outcome. A direct competitor sells a similar product to a similar audience. An indirect competitor solves the same problem through a different product or service. A substitute changes how the buyer gets the job done, while a potential competitor has the capability to enter the market later. The status quo can also compete. A team may keep a spreadsheet, rely on an agency, assign the work internally, or decide the problem is not urgent. These choices matter in B2B markets because the hardest rival is often the buyer's current process rather than another vendor on a comparison page. Each type calls for different evidence. Direct competitors reveal category expectations, packaging, pricing language, and feature parity. Indirect competitors show alternative budgets and workflows. Substitutes expose the broader job the buyer is trying to complete. Potential competitors help a team watch partnerships, hiring, product releases, and adjacent customer bases that could change the market. A useful competitor set reflects the decision being studied. The list for a positioning project may differ from the list used for paid search, product planning, or a sales battlecard. One permanent list usually becomes too broad to guide action. Begin with buyer interviews, lost-deal notes, search results, review sites, sales calls, and public product information. Record why each option appears, which segment considers it, and where it enters the decision. Separate observed evidence from an internal guess. Revisit the classification when the product, audience, or buying process changes. The final map should help someone make a choice. It might shape a message, identify an overlooked substitute, explain a loss, or show where a new offer would face little direct competition. A workflow software company may name two other workflow platforms as direct competitors. A project management suite is an indirect competitor because buyers can configure it for part of the same job. Spreadsheets and manual coordination are substitutes. A large CRM vendor with a new automation product is a potential competitor. Sales can now ask which path the buyer is comparing instead of treating every deal as the same contest. --- # Types of Lead Generation | Surface Glossary URL: https://surface.thesurface.network/glossary/types-of-lead-generation ## What are the main types of lead generation? Types of lead generation describe the motions companies use to create and capture identifiable demand. Common categories include inbound content and search, outbound prospecting, paid media, events, partners, referrals, communities, product-led experiences, tools, and customer-led programs. Most B2B teams combine several rather than relying on one source. The categories can overlap. A webinar promoted through a partner and paid social has event, partner, and paid components. A comparison page may capture organic search demand and support outbound follow-up. For measurement, define the motion by its job and keep first touch, conversion source, and influenced activity separate. Each type has different speed, cost, reach, trust, and operating burden. Outbound can start quickly in a concentrated market but depends on list quality and sales capacity. Content compounds slowly and requires distribution. Referrals may convert well while remaining difficult to scale predictably. Choose the mix from buyer behavior, market concentration, deal value, sales cycle, brand awareness, and internal strengths. Give every motion a primary audience, offer, conversion, quality rule, owner, response target, and economic measure. Compare accepted demand, opportunities, customers, and payback alongside lead volume. Use a portfolio so the motions support one another. Content can educate and supply proof for paid or outbound. Events can deepen relationships created elsewhere. Partners can add trust in markets where the company lacks reach. Preserve the page, campaign, or conversation that caused the response so follow-up begins with context. A niche infrastructure vendor uses expert content for category education, targeted outbound for a finite account list, and partner webinars for credibility. Broad paid social produces cheap downloads and almost no qualified opportunities, so the team limits it to retargeting and shifts budget toward the motions that reach technical buyers. The useful type of lead generation is the complete motion from audience through ownership and customer outcome, not the channel label alone. Channel mix should follow that evidence. --- # Types of Market Research Surveys | Surface Glossary URL: https://surface.thesurface.network/glossary/types-of-market-research-surveys Types of market research surveys are distinguished by the decision they inform and the population they measure. Common forms include market awareness surveys, audience segmentation surveys, needs and pain-point surveys, concept tests, product or feature surveys, pricing studies, brand tracking, customer satisfaction studies, purchase-intent surveys, and win-loss or churn questionnaires. A survey type is not simply a template. The sample, timing, question order, response options, and analysis must fit the decision. The same question can produce different meaning when asked of prospects, customers, lost buyers, or the general market. Awareness and brand surveys measure recognition and associations. Segmentation surveys identify meaningful differences in needs or behavior. Concept and product surveys test reactions to a defined idea. Pricing methods explore willingness to pay and tradeoffs. Satisfaction and relationship surveys examine experience after use. Purchase-intent surveys record stated likelihood, which should not be treated as guaranteed behavior. Longitudinal trackers repeat a stable measure over time. One-time studies answer a current question. Pulse surveys trade depth for speed and are useful only when a small set of measures can support action. Define the target population and decision before drafting questions. Decide how respondents will be recruited, which groups need enough responses for comparison, and what bias the channel may introduce. Use plain language, balanced options, and an order that does not reveal the desired answer. Pilot the survey with people who resemble the sample. Pair stated answers with interviews, behavioral evidence, or sales data when possible. Surveys are strongest at measuring a well-framed pattern, not discovering every pattern from scratch. A payroll company considering a new compliance service first interviews finance leaders to learn their language. It then runs a needs survey across target industries, followed by a concept test that compares two service models. After launch, a relationship survey tracks ease of use and perceived risk reduction. Each survey has a separate population, instrument, and decision. Record the survey purpose, population, recruitment source, field dates, response count, completion rules, weighting, exclusions, and full question wording. Keep the questionnaire with the report. If tracking continues over time, preserve core questions and explain any change. A trend can reflect wording or sample movement rather than a real shift in the market. --- # Types of Marketing | Surface Glossary URL: https://surface.thesurface.network/glossary/types-of-marketing ## What is marketing? Marketing is the work of getting the right people to know, trust, and choose your product. "Types of marketing" is just the set of channels and motions teams use to do that — each with its own economics, feedback loop, and best-fit audience. There is no single correct type. Most B2B teams run a portfolio and shift budget toward whatever is compounding. ## The main types - **Content marketing** — publishing useful material (articles, guides, this glossary) so buyers find you while researching. Compounds slowly, then all at once. - **Inbound marketing** — the broader motion of pulling buyers in with content, SEO, and offers rather than interrupting them. - **Outbound marketing** — proactively reaching prospects through cold email, ads, or calls. Fast to start, pays only while you spend. - **Paid media** — buying attention on search and social. Predictable, measurable, and gone the day you stop. - **Product-led marketing** — the product itself drives acquisition through free tiers, trials, and sharing loops. - **Field & event marketing** — conferences, dinners, and webinars that trade reach for depth of relationship. - **Lifecycle marketing** — nurturing existing leads and customers toward the next action with email and in-product messaging. ## Why it matters Picking the wrong type burns budget. A niche, high-ACV product rarely wins on broad paid social; a self-serve tool rarely needs a field team. The job is to match the motion to how your buyers actually decide — and to stop funding channels that don't compound. Whatever mix you run, the payoff shows up as leads — so how you [capture, qualify, and route them](https://www.withsurface.com/product/forms-and-workflows) matters as much as the channel. See more playbooks on the [Surface blog](https://www.withsurface.com/blog). --- # Types of Marketing Automation | Surface Glossary URL: https://surface.thesurface.network/glossary/types-of-marketing-automation Types of marketing automation are categories of recurring marketing work that software can execute under defined rules. Common groups include audience and lead capture, nurture and education, customer lifecycle communication, sales handoffs, campaign operations, data maintenance, and measurement. Vendors package these capabilities differently, so the workflow is a more stable classification than the product label. One platform may send email, score leads, update CRM fields, schedule social posts, build audiences, and create reports. Calling all of those "email automation" hides different risks and owners. A message sequence affects customer experience, while a field update can change routing or revenue analysis even if no customer sees it. The category helps teams set review and control according to consequence. Publishing a scheduled post may need brand approval. Assigning an account owner needs reliable identity and territory rules. Changing consent status requires stricter authority and history. Classifying the workflow also shows where several tools act on the same record or customer moment. Start with the job, trigger, subject, action, and system affected. Acquisition automation captures and qualifies interest. Nurture automation responds to stage or behavior. Lifecycle automation supports onboarding, adoption, renewal, and expansion. Handoff automation creates tasks or routes records. Operations automation moves data and coordinates production, while measurement automation collects and transforms performance evidence. Automate work that is frequent, rule based, observable, and recoverable. Keep human judgment where context is incomplete or the action has a large customer or financial consequence. For every workflow, name eligibility, exclusions, source fields, delays, exits, retries, error handling, owner, and success measure. Test normal cases alongside duplicates, missing values, late events, manual changes, and people who qualify for several programs at once. A B2B company groups its workflows into lead capture, nurture, sales handoff, customer communication, and data upkeep. During review, the team finds three systems updating lifecycle stage. It gives the CRM authority, limits other tools to campaign status, and adds alerts for failed writes. Message automation becomes easier to trust because its underlying state is controlled. Classifying automation by the job and consequence makes ownership, testing, and tool overlap easier to see. --- # Types of Prompting | Surface Glossary URL: https://surface.thesurface.network/glossary/types-of-prompting ## What are the main types of prompting? Types of prompting are practical patterns for giving a model instructions and context. There is no single universal taxonomy. Common groups include zero-shot, one-shot, and few-shot prompting; role or persona instructions; retrieval-grounded prompts; structured-output prompts; multi-step workflows; and prompts that let a model call approved tools. The labels describe how the task is framed, not a quality ladder. A zero-shot classification prompt can outperform a long example set when the categories are clear. Few-shot examples can help with edge cases, but they can also teach accidental patterns. Tool use matters when the answer requires current data or an external action rather than fluent prose. Knowing the pattern helps a team choose the smallest amount of scaffolding needed for a reliable result. It also improves debugging. If the model misunderstands the output structure, add a schema or example. If it lacks facts, improve retrieval. If one request hides several decisions, split the workflow instead of making the instruction paragraph longer. Classify prompts by the problem they solve: task definition, context supply, demonstration, decomposition, retrieval, tool use, or output control. Teams can combine patterns. A research workflow might retrieve approved sources, use a few examples to classify evidence, and return a fixed JSON object for a downstream system. Use types of prompting inside a defined task rather than as an isolated piece of prose. Save the input, approved context, desired output, model, and test cases beside the prompt so later edits can be compared. Review a sample of real cases before relying on an aggregate score. The sample should include incomplete, conflicting, and high-value records because averages often hide the failures with the largest business cost. Place the documentation for types of prompting beside the workflow or decision it affects. That keeps definitions, evidence, ownership, and later corrections available to the people who need them. A content team asks a model to classify search queries by intent. The zero-shot version defines four labels and returns one label per query. After reviewers find confusion between comparison and purchase intent, the team adds five boundary examples. The prompt is now few-shot, while the task and output schema remain the same. Choose a prompting pattern because it addresses a known failure. Naming a sophisticated technique does little if the workflow still lacks reliable evidence or a measurable definition of success. --- # Market Analysis Components | Surface Glossary URL: https://surface.thesurface.network/glossary/what-does-a-market-analysis-include A market analysis includes the evidence needed to understand a defined market and act within it. The usual components are the market boundary, customer and buying behavior, demand and size, segments, competitors and substitutes, routes to market, pricing and economics, regulatory or technological forces, risks, and the implications for a specific business decision. The section list is a starting point. Depth should follow the decision. Pricing analyses may spend more time on willingness, packaging, procurement, and alternatives. Launch analyses may emphasize audience, problem urgency, channel access, competitive response, and implementation constraints. Generic templates can leave the decisive question underexamined. Define the decision and market before filling sections. Assign an evidence standard to each claim, then collect sources with matching definitions and dates. Analyze how the components interact: a large market may remain unattractive if channel access is expensive, regulation delays entry, or the product cannot satisfy the buying group's requirements. 1. State the market boundary and decision. Name the product scope, customer, geography, period, unit, and adjacent categories that remain outside the analysis. 2. Study buyers and demand. Examine needs, triggers, current behavior, buying roles, budgets, frequency, switching costs, and how much demand is reachable. 3. Analyze segments, competitors, and substitutes. Use consistent criteria and include the ways buyers solve the problem without purchasing from a direct vendor. 4. Assess channels, economics, and market forces. Review pricing, margin, acquisition path, partners, regulation, technology, supply, concentration, and plausible change. 5. Synthesize implications and scenarios. Explain what the evidence supports, which assumptions dominate, and what action, test, or additional research should follow. Measure the analysis by traceability and decision use. Each important conclusion should connect to a source, method, calculation, or clearly labeled inference. Track the freshness of volatile inputs such as pricing, product capabilities, regulation, funding, and market size. Review whether later outcomes confirm or reject the assumptions that drove the choice. Keep a table of claims with source, date, definition, unit, population, confidence, owner, and next review trigger. This makes disagreements easier to resolve because the team can challenge the market boundary or evidence rather than argue over a polished conclusion. Use ranges and scenarios where data cannot support one precise estimate. Write an implication after each major section. Buyer research should change the segment, message, or product requirement. Competitive research should affect positioning or proof. Channel analysis should alter reach and cost assumptions. If a section does not influence the decision, reduce it or remove it. - Which decision sets the required scope and depth? - What definition keeps size, demand, and competitor evidence comparable? - Which buyer roles and substitutes must the analysis include? - Which assumptions could reverse the conclusion? - What evidence will trigger an update after the decision? The output should make uncertainty usable. State what the team knows, what it estimates, and what remains unresolved. Then explain whether the decision is reversible and how much evidence is enough to proceed. Market analysis should support judgment, not conceal it behind a complete-looking framework. Treating the component list as a research plan is a common failure. The team fills every heading with easily available facts, produces a competitor matrix and total-market number, and leaves the central decision implicit. Evidence comes from mismatched years and definitions, while the final recommendation repeats what leadership wanted before collection began. Return to the choice and identify the two or three uncertainties capable of changing it. Reconcile market definitions, replace weak sources, and cut decorative sections. Present alternative scenarios and the evidence that separates them. The shorter analysis may carry more decision value because each part now has a job. End with a dated decision record. It should state the selected scenario, rejected alternatives, current confidence, responsible owner, and the first observable signal that would reopen the analysis. This gives later teams a way to learn from the choice rather than treating the finished document as permanent market truth. Link any market test or launch measurement back to the assumptions it was designed to examine. --- # Growth Marketing | Surface Glossary URL: https://surface.thesurface.network/glossary/what-does-growth-marketing-do Growth marketing finds and improves repeatable ways to acquire, activate, retain, and expand customers. The work combines customer research, channel execution, product or journey changes, measurement, and structured experimentation. Its unit of work is a growth problem with a measurable customer behavior, rather than a channel calendar that must be filled. A growth marketer may investigate why qualified visitors abandon a form, why trial users fail to reach an activation event, or why one segment retains longer than another. The answer might involve messaging, landing pages, onboarding, routing, lifecycle communication, pricing presentation, or product experience. Ownership often crosses the usual boundary between marketing and product, which makes decision rights important. The process begins with a constraint in the customer and revenue system. Teams examine quantitative patterns alongside conversations, support material, sales feedback, and journey observation. They choose a behavior that can move, form a specific explanation for the current problem, and design the smallest responsible test. Learning is recorded whether the change wins, loses, or produces an inconclusive result. 1. Define the growth outcome and population. Specify the segment, current behavior, desired behavior, business value, period, and guardrail metrics. "Increase growth" is too broad to guide a test. 2. Diagnose the constraint. Trace the journey, inspect drop-off by segment, review customer language, and check data quality. Separate a traffic shortage from a conversion, activation, retention, or capacity problem. 3. Write a hypothesis and prediction. State what will change, for whom, why it should work, the expected direction, and the observation that would weaken the explanation. 4. Run the intervention with a clear comparison. Define exposure, assignment, duration, sample limits, exclusions, implementation checks, and the decision rule before reading results. 5. Decide and preserve the learning. Adopt, revise, stop, or investigate further. Record the result, operating cost, segment differences, side effects, and follow-up owner. Measurement depends on the constraint. Acquisition work may use qualified conversion and customer acquisition cost; activation work needs a behavior tied to later retention; retention work needs cohorts and enough observation time. Guardrails can include lead quality, unsubscribe rate, support load, margin, sales capacity, and customer experience. A local metric should not improve by shifting cost or failure into another team. Keep an experiment register with the question, evidence, owner, audience, change, expected outcome, primary metric, guardrails, launch date, data checks, result, and decision. Review whether tests address the largest constraint or merely the easiest page to edit. Product, sales, success, finance, and data owners should join when the change affects their systems or customers. Repeated tests need a stable metric definition and a record of concurrent changes. - Which customer behavior and business outcome define the growth problem? - Who owns changes that cross marketing, product, sales, or customer success? - What comparison and observation period can support the decision? - Which customer, operational, and financial guardrails cannot be traded away? - Where will failed tests and inconclusive results remain available? Velocity should follow risk. A headline experiment can move quickly; a pricing, routing, consent, or onboarding change may affect contracts and customer trust. Give higher-consequence tests more review, rollback planning, and monitoring. The program should also reserve time for instrumentation repair because unreliable events can turn rapid experimentation into rapid confusion. Review the share of work devoted to each lifecycle stage and segment. A crowded acquisition backlog can persist even when retention is the binding economic constraint. Capacity belongs in that review as well. A common failure is calling every campaign a growth experiment. The team changes several elements at once, watches a dashboard rise, and writes a success story without checking mix, seasonality, implementation, or downstream quality. Another failure is maximizing signups while activation and retention deteriorate, which transfers the cost to product and sales. Rebuild the work around one named constraint and one decision. Restore a baseline, audit the event and population definitions, and choose a comparison that can separate the intervention from background change. If a causal test is impractical, state the weaker claim honestly and look for converging evidence before scaling. --- # Importance of Information Governance | Surface Glossary URL: https://surface.thesurface.network/glossary/why-is-information-governance-important Information governance is important because organizations create records, documents, messages, data, and knowledge that influence decisions and carry legal, privacy, security, and operational consequences. Governance assigns ownership and sets rules for classification, access, use, retention, change, and disposal across the information lifecycle. The scope is broader than database quality. It includes contracts, research recordings, email, campaign assets, customer records, policy documents, analytics, and any other information the organization must find, trust, protect, or remove. Without governance, teams keep conflicting versions, share sensitive material too widely, lose source context, retain information longer than needed, or delete records that should remain available. People spend time reconciling files and cannot explain which version supported a decision. Automated systems can make the problem move faster by copying uncertain information across tools. Good governance reduces these risks while making useful information easier to find and reuse. Classify information by purpose, sensitivity, owner, system, and retention need. Define who can create, approve, access, revise, export, and delete each class. Maintain source and version history for consequential records. Set exception and incident paths. Train people inside the workflows where the rules apply. Apply the strongest controls where errors cause the most harm. A public campaign image does not need the same treatment as customer consent, financial reporting, or a signed contract. A marketing team stores interview recordings, transcripts, research summaries, and product claims across shared drives and vendor tools. Its governance program assigns a research owner, limits raw recording access, records consent, sets retention periods, links approved claims to source clips, and removes outdated exports. Writers can still find evidence quickly, while the company can explain where a claim came from and whether it remains valid. Start with a bounded information class and a visible business problem. Research evidence, customer contracts, or campaign claims can each provide a practical first domain. Map where the information lives, who uses it, which decisions depend on it, and which requirements already apply. Fix ownership and retrieval before designing a large committee. Expand when the first controls reduce repeated errors or wasted search. --- # Importance of Structured Data | Surface Glossary URL: https://surface.thesurface.network/glossary/why-is-structured-data-important Structured data is important because it gives information a predictable shape. When fields have stable names, types, definitions, and relationships, software can filter records, join systems, calculate metrics, validate inputs, and trigger actions without interpreting every item from scratch. For a marketing team, structured data connects a campaign to a lead, a lead to an account, an account to an opportunity, and an opportunity to revenue. On a website, structured data can also express page entities for search systems. The common idea is explicit meaning that another system can process consistently. Reliable structure shortens the distance between evidence and action. A lead can route by territory, an email can branch by lifecycle stage, and a report can group pipeline by source. The same speed creates risk when the fields are wrong. Automation makes a bad definition repeat faster. Prioritize the fields tied to real decisions, document their source and allowed values, and validate them before use. Preserve timestamps and provenance where the value can change. Review joins and identifier rules, because a perfectly clean lead row still fails if it connects to the wrong account or campaign. A practical review of structured data should start with meaning before syntax. Identify what the item represents, which visible or operational facts define it, and which system can keep those facts current. Set an explicit review trigger rather than relying on memory. A product launch, schema change, prompt revision, new data source, campaign shift, or sales objection may justify a fresh check. The practical test for structured data is whether it improves a real decision without creating hidden definitions, unsupported confidence, or an unowned handoff to another team. A revenue team wants to compare pipeline from webinars and product demos. It defines campaign type, campaign ID, first-touch source, latest-touch source, lead ID, account ID, opportunity ID, and relevant timestamps. The report can now reproduce the path and explain why two attribution views differ instead of relying on a single ambiguous source field. Structure creates leverage when meaning stays stable. The practical goal is not to structure every available fact. It is to structure the facts the team needs to operate, measure, and audit. --- # Zero-Click Content | Surface Glossary URL: https://surface.thesurface.network/glossary/zero-click-content ## What is zero-click content? Zero-click content is content that delivers its useful point inside a search result, social post, email, AI answer, video feed, or other platform without requiring a click to the publisher's website. The audience may learn, remember, or repeat the idea while the site's analytics record no session. Examples include a complete LinkedIn post, a featured snippet, a search knowledge panel, an email brief, and an AI-generated answer that summarizes or cites a source. The format is not automatically bad for the publisher. It changes the value exchange and makes direct traffic an incomplete measure of whether the content reached the market. ## Why zero-click content matters Buyers often complete part of their research in interfaces that compress many sources. A company that withholds every useful detail until after the click may be ignored. A company that gives away the entire buying path without a memorable point of view or next step may create attention that never becomes preference. Design each piece to stand on its own and carry a recognizable claim, example, or method. Connect the on-platform value to a useful next action such as a deeper guide, comparison, tool, newsletter, or product proof. Track reach, saves, replies, citations, branded search, direct traffic, assisted conversions, and sales mentions instead of forcing all value into last-click sessions. ## How to use zero-click content in practice Use zero-click content as one layer of a wider discovery system. Connect technical clarity with useful pages, evidence, internal links, brand consistency, and direct measurement of mentions, citations, recommendations, and qualified visits. Set an explicit review trigger rather than relying on memory. A product launch, schema change, prompt revision, new data source, campaign shift, or sales objection may justify a fresh check. The practical test for zero-click content is whether it improves a real decision without creating hidden definitions, unsupported confidence, or an unowned handoff to another team. A content lead publishes a concise framework for measuring AI visibility as a LinkedIn post. The post explains mention rate, citation rate, and recommendation rate without hiding the definitions. Readers save and share it. A smaller group follows the linked reporting guide, while branded searches and sales-call references rise during the same month. Zero-click content should still create memory and movement. The pageview is one possible outcome, while category association, trust, subscription, later branded demand, and sales use are others. --- # Industries | Surface Labs URL: https://surface.thesurface.network/industries - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Surface for Financial Services URL: https://surface.thesurface.network/industry/financial-services Financial Services ## Marketing operations for regulated revenue teams. Banks, fintech, insurance, and wealth teams run on trust and compliance. Surface qualifies inbound, routes it to a licensed rep before it cools, and keeps a record of every touch, without ripping out your stack. ## Every applicant qualified. Every touch on record. Capture and enrich inbound the second it lands, score for fit and intent, and route to a licensed rep in under a second, with a clean audit trail behind every conversion. [Book a demo →](https://www.withsurface.com/book-a-demo) +37%lift in lead conversion, Nextiva ## High-value leads. High-stakes compliance. Leaking pipeline. fraud Junk and fraud fills waste licensed reps. Bot and low-intent applications flood the queue, and your most expensive people burn hours on leads that were never real. minutes Intent decays before follow-up. A high-intent applicant expects a fast, compliant response. Wait too long and they open an account with whoever called back first. TueWedFri ● competitor wins Wed ? Compliance can't see what marketing sent. No shared record of who was contacted, with what, and when, so proving the spend and staying audit-ready is manual guesswork. → 500 sent0 closed ## Qualify every applicant the moment they land. Capture and enrich on submit Every form fill becomes a full record (firmographics, intent, and fit) in real time. Score for fit and intent Real applicants rise to the top; bots and junk fall away before a licensed rep ever sees them. Audit trail on every touch Who was contacted, with what, and when, captured on one shared record for compliance. ## Route to a licensed rep before it cools. Sub-second routing Hot applicants reach the right licensed rep by territory and ownership rules, instantly. Sits on your stack Two-way sync with HubSpot, Salesforce, and Marketo. Align every channel, don't rip and replace. Attribution the CFO trusts Every campaign and touch tied to pipeline and closed revenue, so you can prove the spend. > “We're growing at the speed of light, and Surface is one of the few vendors keeping up with us. I'd pay whatever it takes to solve this problem, and Surface solved it.” PB**Pujun Bhatnagar** · CEO, Kintsugi +37% Nextiva lead conversion 150+ demos a month, Valley 12 days GovSpend live, no CRM migration ## The questions financial teams ask. Surface keeps a full record of every marketing touch and supports data residency controls, so compliance can see who was contacted, with what, and when. Book a demo to review your specific requirements. Set up once ## Compliance-safe marketing operations for financial services. [Book a demo](https://www.withsurface.com/book-a-demo) --- # Integrations | Surface Labs URL: https://surface.thesurface.network/integrations Integrations Surface connects to every tool in your GTM stack: no middleware, no broken syncs. CRM HubSpot Sync contacts, companies, and form submissions to your HubSpot account. Salesforce Create and update contacts, companies, and form submissions in Salesforce. Attio Create contacts, companies, notes, and more in your Attio CRM. Zoho Create contacts, companies, leads, and deals in your Zoho CRM. MarketoSoon Send form submissions to your Marketo programs and campaigns. Revenue HeroSoon Send form submissions to your Revenue Hero account. Communication Slack Send real-time lead alerts to your Slack channels. Discord Send real-time lead alerts to your Discord channels. Gmail Send emails and check for responses straight from Gmail. OutreachSoon Trigger Outreach sequences using form data. Scheduling Calendly Book meetings with customers on Calendly from your forms. Cal.com Book meetings with customers on Cal.com from your forms. Zoom Register leads for Zoom meetings and webinars from your forms. Zoom Scheduler Receive booking data from Zoom Scheduler via webhook. Automation HighLevel Sync form data and trigger actions in GoHighLevel. Surface CMS Author content types, entries, and lifecycle from MCP-aware agents and external tools. WordPress Create draft posts on your WordPress site. Ads Meta Ads View insights from your active Meta ad campaigns. LinkedIn Sync LinkedIn Lead Gen Forms and their leads into Surface as forms and responses. Enrichment Surface Enrichment Persona & company data provided by Surface. No API key required. Apollo B2B contact & company data from 275M+ contacts. Hunter Verify emails and append contact + company details. Lusha Accurate B2B contact (email, phone) and company data. ZoomInfo Enterprise B2B intelligence via the ZoomInfo API. Similarweb Company firmographics and website intelligence. Requires Similarweb Sales Intelligence. ClearbitSoon Real-time person & company enrichment by email or domain. People Data LabsSoon Person & company data from a 3B+ record graph. ClaySoon Waterfall enrichment on lead data from incoming form submissions. Ocean.ioSoon Enrich form submissions with persona and company-level data. Analytics DreamData Sync submissions and visitor attribution to DreamData, including drop-offs when partial-response capture is on. --- # Surface for HubSpot | Inbound Qualification and Routing URL: https://surface.thesurface.network/integrations/hubspot Surface for HubSpot ## Give HubSpot richer inbound context Keep HubSpot as the system your team knows while adding a configurable intelligence layer around the handoff. A conceptual flow from a website response, through Surface qualification, into a HubSpot workspace of contact, company, and owner records. 01 WebsiteA buyer submits an inbound response on your site. 02 Surface qualificationResearch, scoring inputs, and routing context are prepared. 03 HubSpot workspaceApproved context reaches the contact, company, and owner records your portal maps. ## A workflow shaped around your portal - What you configure Map the fields and lifecycle stages that matter, and limit write access to approved properties. Exact objects and operations depend on portal setup and implementation scope. - What Surface prepares Surface can use submitted inbound data and configured sources to prepare research, scoring inputs, and routing context. ## Common workflow pattern 1. ### Inbound response A buyer submits an inbound response. 2. ### Enrich and research Surface enriches and researches within the configured workflow. 3. ### Apply your rules Your fit, segment, and routing rules are applied. 4. ### Synchronize approved context Approved context is synchronized to mapped HubSpot records. Stops for human approval 5. ### Hand off the next step Ownership, scheduling, nurture, or a review queue handles the next step. Approved context is synchronized to mapped HubSpot records. ## Keep admins in control Define how duplicates, missing values, conflicts, failures, and manual overrides should behave before launch. An admin checklist covering least-privilege permissions, field mapping and ownership, a controlled test, monitoring, and a rollback plan. Set up once ## Give HubSpot richer inbound context [Book a Demo](https://www.withsurface.com/book-a-demo) --- # Surface for Salesforce | Inbound Intelligence and Routing URL: https://surface.thesurface.network/integrations/salesforce - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Intelligent Attribution for B2B Pipeline | Surface Labs URL: https://surface.thesurface.network/intelligent-attribution - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Marketing 101 | Surface Labs URL: https://surface.thesurface.network/marketing-strategy 01 ## Start with one metric: MQLs Early marketing fails more often from too many goals than too few. The fix is to pick one. Marketing qualified leads, MQLs, are the right first metric: qualified people who raised a hand. Get them by any means that works, and worry about the rest later. It is the right starting point because of what happens next. An MQL either becomes a sales qualified lead and then revenue, or it does not, but either way you now have a real signal to learn from. One metric you can act on beats a dashboard you only stare at. 02 ## Run it for two weeks, then judge Marketing is an experiment loop, not a plan you execute. Pick a channel, run it for about two weeks, then judge the leads it produced. Not the volume, the quality. Then decide: refine the channel that is working, or explore a new one. Three dimensions are worth toggling as you go. **Which channels.** Different motions reach different buyers. Test deliberately rather than spreading thin across all of them at once. **Lead quality per channel.** A channel that floods you with unqualified leads is worse than a quiet one that sends the right few. Judge each channel on what it sends, not how much. **How informed the lead is.** The more a lead already understands your value by the time they are an MQL, the more likely they are to buy. Content and positioning do that work upstream of the form. The durable habit underneath all of this is velocity. The teams that win keep experimentation speed very high. A culture of fast tests plus one or two metrics early is usually enough to figure the rest out. The marketing experiment loop. A human forms the hypothesis; the system runs it and grades it on qualified pipeline. 03 ## When growth stalls, diagnose, don't blame Later stage is a different problem. The loop that got you here stalls, and the temptation is to blame the nearest function. Resist it. Read the numbers and find where the funnel actually breaks. Often the break is not in marketing at all. If qualified leads are strong but they do not close, that points at sales or the product, not the top of the funnel. Good marketing is the glue between product, engineering and sales, so the honest move is to diagnose the real constraint, form a new hypothesis, and run the loop again. 04 ## What we've seen (the proof) This is not theory for us. We run the loop in-house and see it play out across the companies on Surface. 7,000 18,000 LinkedIn followers Four months of running marketing as a live experiment loop, not a fixed annual plan.1 100+ companies on Surface Their full funnel runs through us, so we can see lead quality by channel, not just lead counts.2 $40M+ pipeline processed We grade every experiment against qualified pipeline, not vanity metrics. 05 ## How Surface does this for you Surface gives you the one or two metrics that matter, MQLs and the pipeline they become by channel, plus the speed to read each experiment fast. You set the hypotheses. Surface tells you which ones worked. Sources 1. 1[Surface brand LinkedIn analytics, 2026.](https://linkedin.com/company/surface-labs) 2. 2[Aggregated Surface customer funnel data across 100+ customers, 2026.](https://withsurface.com/customers) --- # Paid Media for B2B 101 | Surface Labs URL: https://surface.thesurface.network/paid-media-b2b 01 ## Paid media scales what works Paid media is an amplifier, not an engine. It takes a message that already lands and puts it in front of more of the right people, faster. It does not fix a weak offer, a vague positioning, or a landing page that does not convert. Point spend at those and you simply lose money more efficiently. So the question is never _should we run ads_. It is _do we have something proven enough to pour fuel on_. In B2B, where deals are considered and the buying committee is small, that proof comes from your existing pipeline, not from a media plan. 02 ## Validate before you scale Validation is simple to state: show that a specific message and page already turn attention into pipeline, on a smaller scale, before you pay to multiply it. Three signals tell you it is ready. **One, it converts organically.** A page or message that earns demos from organic and outbound traffic has a real offer. If it cannot convert traffic you did not pay for, paid traffic will not save it. **Two, it pulls the right accounts.** Look at who actually converts, not how many. If your best-fit accounts are the ones engaging and booking, you have product-message fit worth scaling. **Three, it ties to revenue.** Track the source through to pipeline and closed revenue, not to clicks or form fills. A channel that produces cheap leads and no pipeline is a cost, not a win. 03 ## Going in blind is the expensive mistake The common failure is running ads as a first GTM channel because there is no other one. Budget goes out the door on the hope that paid will just work, with no validated funnel underneath it and no way to read the result. When it underperforms, and it will, you cannot tell what broke. Was it the creative, the targeting, the offer, or the page? Without a measured funnel you are guessing at all four at once, and the rude awakening is a quarter of spend with no pipeline you can point to. Validation first turns paid from a bet into a decision. You scale what is already working, and you read every dollar against revenue. The paid-media validation loop. A human decides which signals count; the system measures conversion to pipeline before and after spend. 04 ## What we've seen (the proof) The companies on Surface route their traffic through us, so we watch what converts before and after spend, not just what gets clicked. $40M+ pipeline processed We read paid the way the business does, on the pipeline it creates, not the leads it reports. 100+ companies on Surface Their spend and conversions run through us, so we can tell a channel that buys pipeline from one that just buys clicks.1 05 ## How Surface does this for you Surface ties every visitor and conversion to pipeline, so you validate what converts before you scale it and see a channel's real revenue contribution, not its click count. You decide where to spend. Surface shows you what is already working. --- # Paid Media for B2C 101 | Surface Labs URL: https://surface.thesurface.network/paid-media-b2c 01 ## B2C paid is a different machine Everything in the B2B guide still holds: paid amplifies what works, it does not create demand. But the machine is different enough that the tactics do not transfer. B2C funnels are short, the creative does most of the work, the volume is high, and the feedback comes back in hours instead of quarters. That speed is the opportunity and the trap. You can learn fast, and you can burn fast. The discipline that keeps you on the right side of that line is the same one B2B needs, applied to different signals: validate before you scale. 02 ## Validate before you scale Before you raise budget, prove three things on a small spend. **One, the creative resonates.** In B2C the ad is the front door. Early signals like hook rate, hold and click-through tell you whether the creative earns attention at all. Weak creative does not get better with more budget. **Two, the early conversion fires.** Watch the first real action: add to cart, signup, or first purchase. A click that never converts is a vanity metric. You want evidence that attention turns into intent. **Three, the unit economics work.** Compare acquisition cost to what a customer is worth: average order value, repeat rate and payback period. A channel that buys customers below their value scales. One that does not is a leak you would only widen. 03 ## Velocity is the engine Once the economics work, the engine is volume and iteration. B2C performance is won by producing many creative variants, killing the losers quickly, and feeding the winners more budget. The platforms optimize well when you give them clean signal and enough volume to learn from. The job is to keep that loop turning fast without losing the plot. A human still decides which signals count, what is on brand, and when a winning ad has fatigued. Speed without judgment just finds the wrong answer faster. The B2C paid loop. A human guards brand and judgment; the system tests creative and grades each variant on revenue. 04 ## What we've seen (the proof) We watch this play out across the B2C companies on Surface. The numbers below come from teams that closed the loop between click and revenue before they raised budget. 100+ companies on Surface We measure the full funnel from click to revenue, which is exactly the read B2C paid needs to compare cost to value.1 2–3× ROAS on validated channels Across our B2C customers, teams that validate unit economics before raising budget see two to three times the return on ad spend versus those that scale without proof.2 < 60 days median payback period B2C brands on Surface that close the click-to-revenue loop reach payback on new channels in under 60 days, roughly half the time of teams running spend without attribution.3 05 ## How Surface does this for you Surface ties click, conversion and revenue together, so you can prove unit economics before scaling and grade each creative on customers acquired. You run the creative. Surface tells you which spend paid for itself. Sources 1. 1[Aggregated Surface customer traffic and conversion data, 2026.](https://withsurface.com/customers) 2. 2[Aggregated Surface B2C customer attribution data, 2026.](https://withsurface.com/customers) 3. 3[Surface customer cohort analysis, B2C segment, 2026.](https://withsurface.com/customers) --- # Surface Partners | Build Growth Together URL: https://surface.thesurface.network/partners - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Agentic Enrichment for B2B Leads | Surface Labs URL: https://surface.thesurface.network/platform/agentic-enrichment Agentic Enrichment ## Your form captured an email, and sales still has to guess who that person is. ## You already have the email. The rest of the person should come with it. Surface reads the work email and fills name, title, company, and headcount so the form does not have to ask for fields you can look up. How it runs ## What happens after the form captures an email 1 ### Read the email Fill name, title, company, and size from it so those fields do not have to live on the form. 2 ### Try the next source If one vendor is empty on a field, another source can still write it. A gap in coverage should not mean a blank CRM cell. 3 ### Look up the account Public pages for funding, hiring, and launches get attached with a source, so the rep can see where the note came from. 4 ### Keep using the same record Later research writes onto that lead in the Lead Data Layer, which scoring, routing, and campaigns already read. ## Scoring and routing already read this record. If the fields are empty, scoring and routing are working off a name and an email. [ **Maddy Fennessy**Growth Marketing Lead, Metronome > “We feel pretty embedded in Surface, especially since we did the PLG stuff there. I would consider Surface to be like a pretty core part of what is running our website, which is a good thing.” ](https://www.withsurface.com/customers) [ **Shubh Agrawal**San Francisco, Valley > “If we turned off Surface tomorrow, we'd lose a lot of inbound. We're almost entirely inbound-driven, so Surface is a critical part of how we operate.” ](https://www.withsurface.com/customers/valley) [ **Alexandra Doan**San Francisco, Nextiva > “We actually saw that 37% more users on average converted with the new form that they built for us” ](https://www.withsurface.com/customers/nextiva) [ **Pujun Bhatnagar**CEO, Kintsugi > “We're growing at the speed of light, and Surface is one of the few vendors keeping up with us. I'd pay whatever it takes to solve this problem, and Surface solved it.” ](https://www.withsurface.com/customers/kintsugi) [ **Angela Kou**Chief of Staff, Juicebox > “Whenever I had a feature request, the Surface team would update me throughout the process and follow up after launch to make sure everything was working correctly. It really feels like a white-glove experience.” ](https://www.withsurface.com/customers/juicebox) [ **Ian Christopher**CEO, Galley > “We used Typeform in the early days. It was great but you can tell when a company outgrows it. Surface gives us the mechanics we liked from Typeform, but with enterprise-grade control over brand, format, and functionality.” ](https://www.withsurface.com/customers/galley) Set up once ## Want to see this on one of your leads? [BOOK A DEMO](https://www.withsurface.com/book-a-demo) --- # AI Search Visibility 101 | Surface Labs URL: https://surface.thesurface.network/platform/ai-visibility AI Visibility Engineering ## Be the company answer engines recommend AI Visibility product tour ## Explore AI Visibility Engineering. From buyer questions to visibility ## The AI visibility loop 1. 01 ### Track buyer questions Track prompts by topic, journey stage, intent, and revenue value. Pricing alternativesHIGH Implementation timeTRACKED Best fit for RevOpsTRACKED 2. 02 ### Measure every answer See where AI engines cite your brand and which sources shape their answers. Citations 42% Mentions +18% 3. 03 ### Find competitive gaps Compare competitor coverage and find missing questions or evidence. Your brand38% Category leader71% 4. 04 ### Turn gaps into action Create campaign work from the best gaps, then measure the result. Comparison pageRUNNING Buyer guideREADY Evidence updateREADY ## How it works Surface connects AI visibility measurement directly to campaign work. 01 ### Choose buyer prompts. Focus measurement on the questions that influence buying. Category81 Problem56 Comparison32 02 ### Measure your visibility. See citations, competitors, and gaps across AI engines. ChatGPT78Cited Perplexity64Cited Gemini41Gap 03 ### Act on the gaps. Turn the best opportunities into measurable campaign work. 01 Insight 02 Decision 03 Action 04 Learn The details ## FAQ What does Surface measure in AI search? Surface measures whether your brand is cited by prompt and answer engine, where it appears, how visibility compares with competitors, and which pages influence how your brand is understood. Which answer engines can Surface monitor? Surface measures visibility across major answer engines, including ChatGPT, Perplexity, Gemini, and AI-generated search experiences. Coverage can be organized by the engines and prompt groups that matter to your buyers. How does Surface choose which prompts to track? Prompt selection starts with the buying journey, real buyer language, intent, and business relevance. Prompt groups can be weighted and recalibrated as buyer behavior, competitors, and answer engines change. What happens after Surface finds a visibility gap? Surface turns the gap into reviewed campaign work. Agents can support research and production, people retain control over claims and brand judgment, and the system re-measures the result to inform the next cycle. Set up once ## See exactly how you show up in AI answers. [Get a free visibility report](https://www.withsurface.com/solutions/increase-inbound-conversion) --- # Build Your Own Marketing Agent | Surface Labs URL: https://surface.thesurface.network/platform/build-your-own ## Build the marketing agentyour workflow needs Agent builder ## Describe the job. Surface builds the agent. Start in plain language. Surface turns your instructions, context, and guardrails into a reusable agent. A user asks Surface to build a pipeline signal scout. Surface defines its objective, connects live context, adds approval guardrails, and outputs the completed agent specification. ## How it works Move from one clear instruction to a reusable marketing agent with live context and controlled actions. 1. 01 ### Define the agent's job. Describe the outcome, its context, and where it must stop. Outcome01 Context02 Guardrail03 2. 02 ### Connect live Surface context. Use Surface MCP for live campaigns, segments, and leads. Surface MCP01 Buyer data02 Campaign data03 3. 03 ### Run, measure, and improve. Direct it, approve key actions, and improve each run. Instruction01 Approval02 Learning03 ## Start with an agent your team will use every week Set up once ## Give your AI assistant a real marketing operating layer [Connect Surface MCP](https://www.withsurface.com/mcp) --- # Content Campaign Agents | Qualified Buyers | Surface Labs URL: https://surface.thesurface.network/platform/content-campaigns Cookies are small text files that can be used by websites to make a user's experience more efficient. The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies we need your permission. This site uses different types of cookies. Some cookies are placed by third party services that appear on our pages. You can at any time change or withdraw your consent from the Cookie Declaration on our website. Learn more about who we are, how you can contact us and how we process personal data in our Privacy Policy. Please state your consent ID and date when you contact us regarding your consent. --- # Conversion-Optimized B2B Forms | Surface Labs URL: https://surface.thesurface.network/platform/dynamic-lead-forms Surface Form Builder ## Intelligent Forms that 10x Conversions Surface Form Builder ## Give every buyer a shorter path to conversion. Adapt questions and steps using the context already known about the visitor and account. ## Implementation ### Start with one high-value form 1. ### Choose the form Choose the form with meaningful traffic, material abandonment, and a measurable sales outcome. 2. ### Document the workflow Document fields, branches, disclosures, enrichment, qualification, routing, scheduling, CRM writes, and failure paths. 3. ### Agree on measurement Agree on the baseline, eligible form starts, conversion event, partial-response definition, and minimum volume. Stops for human approval 4. ### Build and test Build and test the Surface form across devices, browsers, sources, edge cases, and consent states. 5. ### Launch Launch with monitoring, ownership, rollback, and a 30-day measurement plan. Set up once ## Convert 30% more of the traffic you already have. [Get a free traffic audit](https://www.withsurface.com/solutions/increase-inbound-conversion) --- # Form Intelligence | Surface Labs URL: https://surface.thesurface.network/platform/infrastructure/form-intelligence - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Traffic Intelligence | Surface Labs URL: https://surface.thesurface.network/platform/infrastructure/traffic-intelligence - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Intelligent Scheduling | Route & Book Leads | Surface Labs URL: https://surface.thesurface.network/platform/intelligent-scheduling Intelligent Scheduling ## Agents are here. But you're still paying for per-seat scheduling Intelligent Scheduling product tour Resolve the buyer and apply your fit, value, and eligibility rules. Routing and scheduling, together ## One system makes the decision and books the meeting. Replace disconnected qualification, routing, and scheduling tools with one governed inbound path. ### Qualification-aware routing Use buyer context and fit rules to decide who should enter the scheduling path. ### Ownership and territory rules Respect existing owners, territories, round robins, and approved exceptions. ### Instant calendar matching Find the correct rep and an available time without another handoff. ### Unlimited bookings Book meetings without usage caps, overage fees, or per-rep pricing. ### Fallbacks that keep leads moving Send unmatched or unavailable leads into a controlled review path. ### CRM write-back Sync the owner, decision, meeting, and supporting context to your CRM. [ **Maddy Fennessy**Growth Marketing Lead, Metronome > “We feel pretty embedded in Surface, especially since we did the PLG stuff there. I would consider Surface to be like a pretty core part of what is running our website, which is a good thing.” ](https://www.withsurface.com/customers) [ **Shubh Agrawal**San Francisco, Valley > “If we turned off Surface tomorrow, we'd lose a lot of inbound. We're almost entirely inbound-driven, so Surface is a critical part of how we operate.” ](https://www.withsurface.com/customers/valley) [ **Alexandra Doan**San Francisco, Nextiva > “We actually saw that 37% more users on average converted with the new form that they built for us” ](https://www.withsurface.com/customers/nextiva) [ **Pujun Bhatnagar**CEO, Kintsugi > “We're growing at the speed of light, and Surface is one of the few vendors keeping up with us. I'd pay whatever it takes to solve this problem, and Surface solved it.” ](https://www.withsurface.com/customers/kintsugi) [ **Angela Kou**Chief of Staff, Juicebox > “Whenever I had a feature request, the Surface team would update me throughout the process and follow up after launch to make sure everything was working correctly. It really feels like a white-glove experience.” ](https://www.withsurface.com/customers/juicebox) [ **Ian Christopher**CEO, Galley > “We used Typeform in the early days. It was great but you can tell when a company outgrows it. Surface gives us the mechanics we liked from Typeform, but with enterprise-grade control over brand, format, and functionality.” ](https://www.withsurface.com/customers/galley) Set up once ## Route the right buyer and book the meeting instantly. [BOOK A DEMO](https://www.withsurface.com/book-a-demo) --- # Lead Agents | Surface Labs URL: https://surface.thesurface.network/platform/lead-agents - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Lead Data Layer Product Tour | Surface Labs URL: https://surface.thesurface.network/platform/lead-data-layer Lead Data Layer ## Give every lead, campaign, and agent the same customer context Product tour ## See the shared context in action. Move from a buyer record to a live audience and a measurable campaign inside one connected system. From signal to action ## Give every agent the context to do its job. 1 ### Capture the buyer signal Surface records the visit, form interaction, campaign response, or product event while intent is fresh. 2 ### Build the buyer record Identity, company data, behavior, source, and engagement history come together on one current record. 3 ### Qualify and segment Fit and intent determine the buyer's score, audience, routing path, and next best action. 4 ### Activate the right workflow Surface sends context into campaigns, sales handoffs, scheduling, ads, and agent workflows. 5 ### Learn from the outcome Meetings and revenue return to the record, sharpening future qualification and campaign decisions. Kintsugi customer story 11K+ leads captured 91% enriched automatically > “Surface didn't just help Kintsugi grow. It gave us control over the entire inbound funnel.” Pujun Bhatnagar, CEO, Kintsugi [Read the customer story](https://www.withsurface.com/customers/kintsugi) ## Connect Surface to the systems you already run. [Explore all integrations →](https://www.withsurface.com/integrations) HubSpot Salesforce Marketo Slack Claude Codex Clay Chili Piper Calendly Zapier Google Analytics PostHog Revenue Hero Attio Apollo ZoomInfo Google Ads Meta Ads ## FAQ What is a Lead Data Layer? It is the shared buyer context that Surface uses across qualification, segmentation, campaigns, routing, and agents. Each workflow reads from the same current lead record. How does it work with our CRM? Your CRM remains the place sales works from. Surface captures and enriches buyer activity, then writes the fields, scores, owners, and outcomes your CRM needs. How is this different from a CDP or data warehouse? Surface is built around operational marketing work. It turns buyer context into live audiences, routing decisions, campaigns, and agent actions while the signal still matters. Which buyer signals can Surface capture? Surface can work with website activity, completed and partial forms, campaign engagement, scheduling events, CRM history, and product events sent through your connected systems. How quickly can a team get started? The first workflow can begin with one source and one outcome. Surface then adds more signals, rules, and destinations around the same lead record as your team expands its use. Set up once ## Build your first connected lead workflow with Surface. [BOOK A DEMO](https://www.withsurface.com/book-a-demo) --- # Lead Intelligence | Qualify & Route Leads | Surface Labs URL: https://surface.thesurface.network/platform/lead-intelligence Surface Lead Intelligence ## Capture more demandKnow which leads matterGet them to the right rep Surface Lead Intelligence ## Research beyond the data vendor. Combine identity coverage with live agent research so each lead arrives with evidence your team can use. ## One decision layer, from first touch to the right rep ## Work with HubSpot or Salesforce, not around them Existing lifecycle stages, fields, and sales processes remain the system of record while Surface improves the decisions moving through them. ## See where qualified inbound is leaking Measure the inbound journey as one funnel to find the next constraint. ## From lead intelligence to compounding growth Every accepted lead sharpens the picture of who converts and why. Campaign agents put that context to work. Set up once ## B2B teams on Surface see 30% more demos in 30 days. [Book a Demo](https://www.withsurface.com/book-a-demo) --- # System Agents | Surface Labs URL: https://surface.thesurface.network/platform/system-agents - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Podcast | Surface Labs URL: https://surface.thesurface.network/podcast Podcast ## Conversations with Marketing Leaders Exclusive interviews uncovering how today's top thought leaders are shaping the future of marketing. [Watch now](https://youtube.com/playlist?list=PLBM9bqnrEuVdj6gs5hlt6btrHBDwR_M8G&si=wWF0OF7IYyMxu6C_) ## Latest episodes Dave Riggs · Co-founder, Apex Growth ### From audits to automation: the future of performance marketing Saharsh Agrawal sits down with Dave Riggs, co-founder of Apex Growth, in a discussion about the evolving landscape of marketing agencies. Dave shares his journey from in-house roles to leading a performance marketing agency, offering insights into the challenges and opportunities in bridging B2C and B2B marketing. The conversation delves into the impact of AI on creative strategy and media buying, emphasizing the importance of human interaction in client relationships. Discover how strategic growth audits can uncover systemic issues and why brand building and networking are crucial for agency success in the AI era. Elaine Zelby · Co-founder & CRO, Tofu ### Elaine Zelby (Tofu) on navigating AI adoption, creative vs. automated marketing, and startup challenges Saharsh Agrawal interviews Elaine Zelby, co-founder and CRO of Tofu, a platform designed for B2B marketing teams to create hyper-personalized AI-driven campaigns. They discuss the evolution of Tofu, the balance between automation and creativity in marketing, the phases of AI adoption, and advice for young marketers entering the field. Elaine shares insights from her experience as an investor and the challenges of building in the generative AI space. Eric Siu · CEO, Single Grain ### Eric Siu (Single Grain) on SEO Shifts in a Post-AI World and Founder Resilience Saharsh Agrawal sits down with Eric Siu, CEO of Single Grain, to explore the evolving world of marketing in the age of AI. They dive into how traditional SEO has shifted toward "search everywhere optimization," why personal branding and distribution are now critical for founders, and how agencies must adapt to stay relevant in a tech-driven landscape. Eric also shares lessons learned from building and scaling Single Grain, the role resilience plays in long-term success, and how systems thinking can be applied to both personal health and business growth. Pranav Piyush · Co-founder & CEO, Paramark ### Pranav Piyush (Paramark) on Marketing Science and Entrepreneurship Saharsh Agrawal sits down with Pranav Piyush, co-founder and CEO of Paramark, to discuss the importance of scientific thinking in modern marketing. They dive into why early-stage startups should prioritize simple, evidence-backed metrics over complex systems, how traffic and search query volume can serve as critical health indicators, and the evolving role of measurement in a world increasingly shaped by AI. Pranav also shares insights from his entrepreneurial journey, highlighting the challenges startups face in defining marketing strategies, lessons learned from conversations with CMOs, and why understanding measurement principles is essential for both growth and resilience. Casey Hill · CMO, DoWhatWorks ### The future of conversion optimization with AI and data Saharsh Agrawal sits down with Casey Hill, Chief Marketing Officer at DoWhatWorks, to unpack the future of marketing and A/B testing in the AI era. They dive into why most split tests fail, how to make smarter data-driven decisions, and where AI-human collaboration will reshape conversion rate optimization. Casey also shares his journey from sales to marketing, lessons from scaling SaaS companies like ActiveCampaign, and the playbooks he's now applying at DoWhatWorks. Nalin Senthamil · Founder & CEO, Storylane ### How interactive demos transform SaaS sales and conversions Saharsh Agrawal sits down with Nalin Senthamil, Founder and CEO of Storylane, to explore how interactive demos are reshaping the SaaS buying experience. They discuss why letting prospects experience a product before a sales call dramatically improves conversion rates, how to build demos that qualify and educate simultaneously, and what the shift toward self-serve discovery means for modern B2B go-to-market teams. Coming Soon Aditi Joshi · CEO, Bamboo ### Adapting agencies to change: leadership, AI, and client relations Saharsh Agrawal sits down with Aditi Joshi, CEO of Bamboo, to discuss how marketing agencies are navigating a period of rapid change driven by AI. They explore how client relationships are evolving, what strong agency leadership looks like when the toolset shifts overnight, and how the best agencies are staying relevant by doubling down on strategic judgment rather than execution volume. Coming Soon Amrit Dhangal · Founder & CEO, Aero ### Scaling startups, pricing shifts, and the future of CRM Saharsh Agrawal sits down with Amrit Dhangal, Founder and CEO of Aero, to talk about what it really takes to scale a startup in a market being reshaped by AI. They cover how pricing strategy evolves as you grow, why CRM is becoming the central nervous system of modern go-to-market teams, and the operational decisions that separate startups that compound from those that plateau. Coming Soon Set up once ## B2B teams running on Surface see 30% more demos within 30 days. [SEE PRICING](https://www.withsurface.com/pricing) --- # Marketing Operations and Agent Pricing | Surface Labs URL: https://surface.thesurface.network/pricing Start with core marketing infrastructure on Basic, then add agents and forward-deployed experts as you scale. Save up to 23% with annual billing ## Basic $1,000/mo Core marketing operations without autonomous agents. - Forms, routing and scheduling - Enrichment and traffic intelligence - CRM and MAP sync - No agents included [Start with Basic](https://www.withsurface.com/book-a-demo) ## Agentic Marketing Operations $3,500/mo Agents that operate marketing workflows across a function. - Everything in Basic - Unlimited agents, systems and tools - 5,000 agent actions / mo - Shared FDE team [Book a demo](https://www.withsurface.com/book-a-demo) ## Marketing Superintelligence Custom A governed intelligence layer for multi-team marketing. - Everything in Agentic Marketing Operations - Custom action volume - Dedicated account FDE - SLA, SSO and audit log [Talk to sales](https://www.withsurface.com/book-a-demo) ## Agent action pricing Basic Not included Agentic Marketing Operations $0.20 / action After 5,000 included actions Marketing Superintelligence Custom ## Compare Tiers Feature Basic Agentic Marketing Operations Marketing Superintelligence Plans and usage Surface platform and workspaceThe shared workspace for building, running, and managing your marketing agents. Team seatsInvite teammates to collaborate in Surface without per-seat limits. Unlimited Unlimited Unlimited AgentsCreate and run specialized agents for your marketing workflows. — Unlimited Unlimited Systems and toolsConnect the systems and tools your agents need to complete their work. Unlimited Unlimited Unlimited Agent actions included / moThe monthly units of agent work included before additional usage charges apply. — 5,000 Custom Price per agent actionThe rate for each additional unit of agent work beyond your included volume. — $0.20 Custom ### Basic Plans and usage Surface platform and workspaceThe shared workspace for building, running, and managing your marketing agents. Team seatsInvite teammates to collaborate in Surface without per-seat limits. Unlimited AgentsCreate and run specialized agents for your marketing workflows. — Systems and toolsConnect the systems and tools your agents need to complete their work. Unlimited Agent actions included / moThe monthly units of agent work included before additional usage charges apply. — Price per agent actionThe rate for each additional unit of agent work beyond your included volume. — ### Agentic Marketing Operations Plans and usage Surface platform and workspaceThe shared workspace for building, running, and managing your marketing agents. Team seatsInvite teammates to collaborate in Surface without per-seat limits. Unlimited AgentsCreate and run specialized agents for your marketing workflows. Unlimited Systems and toolsConnect the systems and tools your agents need to complete their work. Unlimited Agent actions included / moThe monthly units of agent work included before additional usage charges apply. 5,000 Price per agent actionThe rate for each additional unit of agent work beyond your included volume. $0.20 ### Marketing Superintelligence Plans and usage Surface platform and workspaceThe shared workspace for building, running, and managing your marketing agents. Team seatsInvite teammates to collaborate in Surface without per-seat limits. Unlimited AgentsCreate and run specialized agents for your marketing workflows. Unlimited Systems and toolsConnect the systems and tools your agents need to complete their work. Unlimited Agent actions included / moThe monthly units of agent work included before additional usage charges apply. Custom Price per agent actionThe rate for each additional unit of agent work beyond your included volume. Custom --- # Privacy Policy | Surface Labs URL: https://surface.thesurface.network/privacy_policy ## 1\. Introduction Surface Labs operates a marketing operations platform in compliance with GDPR and CCPA regulations. This policy defines “Customers” (service users) and “Form Responders” (those completing forms created by our customers). By using our services, you agree to the collection and use of information in accordance with this policy. ## 2\. Data Collection We collect data necessary to provide and improve our services, including contact information, usage data, and analytics. For Form Responders, we collect information submitted through customer-created forms. ## 3\. Data Use Data is used to provide services, improve our platform, communicate with users, and comply with legal obligations. We do not sell personal data to third parties. ## 4\. Data Sharing We may share data with trusted service providers who assist in operating our platform, subject to confidentiality agreements. We may also disclose data when required by law. ## 5\. Data Retention We retain personal data for as long as necessary to provide our services and comply with legal obligations. You may request deletion of your data at any time. ## 6\. Your Rights Individuals may request access, amendments, or deletion of personal data under applicable privacy laws including GDPR and CCPA. To exercise your rights, please contact us at [privacy@withsurface.com](mailto:privacy@withsurface.com). ## 7\. Cookies We use cookies to analyze site traffic and improve your experience. For full details on our cookie use, please refer to our [Cookie Policy](https://www.withsurface.com/cookie-policy). ## 8\. Contact Us If you have any questions about this Privacy Policy, please contact Surface Labs at: - Email: [privacy@withsurface.com](mailto:privacy@withsurface.com) - Website: withsurface.com --- # Product Updates | Surface Labs URL: https://surface.thesurface.network/product-updates Product updates ## We build 100x faster than your marketing team. New features, improvements, and fixes, shipped every week. Release ## August 2026 Lead Segmentation (Beta) - Segments tab: build, save, and reuse lead segments across the platform. - Segment on scheduler activity with the new scheduler filter support. - Enrichment data is now available as a routing input, so segments and routes can share the same signals. LinkedIn Lead Sync (Beta) - Connect LinkedIn over OAuth from a dedicated integration card. - LinkedIn lead gen forms appear as top-level Surface forms alongside your own. - LinkedIn lead responses carry full UTM attribution into reporting and workflows. Routing & Scoring - Any Of and All Of set operators for routing conditions. - Route on the day of week a form is submitted. - Per-step AI lead scoring configuration, so each step can score on its own criteria. - Salesforce Account list conditional routing. Forms & Responses - Form Builder MCP v1: agent-driven form creation tools (Beta). - New component editor UIs for EmailForm and Marketing NextButton. - Transparent and translucent colors are now selectable in the color picker. - Archived view and restore for form responses. - Fixed an off-by-one error in dropdown variable resolution that sent incorrect values downstream. Data & Performance - Similarweb added as an enrichment provider. - Custom domain attribute support for Surface Tag. - Database load optimization, faster permission query sequencing, and background job tuning. - New Supabase database monitors, plus query and background job dashboards. - Tenant isolation and auth configuration reviewed and hardened across the platform. Release ## July 2026 Forms & Form Builder - Better self-serve form templates, so new accounts start from a working form instead of a blank canvas. - Reordering and adding fields is faster across Multiple Choice, Value Adds, FAQ, and Identity Info components. - Add and insert step flows redesigned, with horizontal scroll buttons on the steps overview row. - Spam controls moved into a dedicated tab in Form Settings. - Form renderer first paint optimized for faster perceived load. Workflows & Routing - Workflows can now be re-run and backfilled manually, individually or in bulk from the response table. - New disqualified trigger for form workflows. - Queued workflow run support, so runs no longer drop under load. - Form Journey now shows routing logic and resolved values when no condition matched. - Owner and host routing for the dynamic scheduler. Lead Intelligence & CRM Agents - Attio AI Agent, joining Salesforce, HubSpot, and Zoho. - Round-robin lead assignment for Salesforce and HubSpot agents, referencing your scheduler lists instead of re-typed emails. - CRM agent Enhance: side-by-side diff review with accept, reject, and inline edit. - AI lead scoring can be re-run, and now accepts feedback to improve over time. - CRM agent interface rebuilt for clearer setup and review. Traffic & Attribution - New lead traffic page, plus a rebuilt Traffic Analytics view. - Drill from any Conversion Funnel count straight to the exact leads behind it, including Form Completed, Qualified, Disqualified, and Meetings Not Booked. - New "All URLs" view in Conversion Funnel. - Surface Tag now persists first-touch UTMs and gclid across page movement, available in form workflows. - Control dynamic pixel firing from Surface with ad conversion rules, and fire Conversion Events on form events rather than steps only. Scheduling & Meetings - Zoom no-show detection rebuilt on booking data. - No-show email notifications to hosts, on by default with a toggle in Notifications. - Meetings view re-released with a faster, clearer layout. - Surface Tag detection status now visible on form responses. Platform & Security - Leads table pagination reworked to a rolling window, dropping the per-page count query. - Self-service CSV export for AI Visibility, and longitudinal visibility evidence exposed over MCP. - Every environment-scoped API route now wrapped with withAuth. - Slack AI webhook signatures verified, and CRM MCP tools require API key access. Release ## June 2026 Forms & Scheduler - Redesigned form builder with persistent steps, component editing, smoother transitions, and instant previews. - Create one-on-one Surface Scheduler events directly inside a form's Calendar step. - Round-robin scheduling now supports host availability, weighted or strict assignment, and host-specific Zoom links. - Booking journeys now inherit form styles, continue after confirmation, and display the assigned host. Workflows & Lead Intelligence - AI Lead Score now resolves before workflows for immediate routing and actions. - Research Agent combines buyer, company, and live web research for downstream CRM agents. - Connect enrichment providers, prioritize them, and use enriched fields throughout Surface. - Salesforce supports custom objects; HubSpot agents can use research and lead scores. AI Visibility & Content Ops - Generate downloadable AEO and GEO reports from prompts, competitors, citations, and visibility scores. - New or edited prompts automatically scan and refresh Strategy within minutes. - Attribute AI-referred pageviews from ChatGPT, Copilot, Gemini, Perplexity, and Claude. - Bulk-discover and auto-track URLs while Strategy connects prompts, traffic potential, and publishing progress. Leads & Platform - Faster response search cut observed email lookup time from 933 ms to 22 ms. - Response details now clearly group API calls, workflows, and Research Agent results. - Meeting Scheduled is now available in response tables, filters, and CSV exports. - Bulk invites, team roles, profile photos, and a focused Sales Rep view are now available. Release ## May 2026 Workflows & Logic - AI Lead Score in the variable selector: route, branch, and personalize anywhere using AI scores as a first-class variable. - Workflow logs drawer v2: redesigned logs view with toolbar parity across Leads, Responses, and Workflow runs. - Path conditions revamp: multi-select value picker, wider operator dropdowns, scrollable Manage Conditions dialog. - Empty Slack/Email Alert questions now include all fields by default, no more missing context in notifications. Scheduler - Standalone scheduler at scheduler.withsurface.com/\[slug\]: share a clean scheduler link without an embedded form. - Multi-host scheduling fixes and member-table scrolling for large teams. - Confirmation links are now domain-aware: cancel and reschedule respect custom domains. - No-show invite emails throttled to once per 24 hours. Forms & Editor - Asset Manager modal in the form editor sidebar. - Form Settings redesigned: grouped nav, responsive shell, unified HubSpot panel. - Multi-select dropdowns now support custom checkbox background colors. - "Reset" replaces the misleading "Undo" label on form and workflow headers. - Form analytics page redesigned with materialized CTEs for faster load. CRM & Integrations - CRM AI Agent (GA): instruction templates, validation badges, chat persistence, and design polish. - Zoho: Create or Update Lead & Contact workflow actions. - HubSpot sync drift detection with in-app alerts. - Apollo enrichment failures are now non-fatal, leads still capture. AI Visibility - Onboarding wizard, drafts, and dashboard manage UI. - First scan triggered automatically on profile creation with live progress. - Super-admin run scan + live progress for support. - Per-environment AI Visibility flag. Platform & Security - withAuth migration across the API surface: every environment-scoped route goes through unified auth and access control with SSRF guard. - Turnstile secret can be updated independently. - Lead capture: NUL bytes stripped from source URLs. - SSO/OAuth: invalid integration state environment IDs prevented. Release ## April 2026 Workflows & Logic Builder - Flat workflow editor: new node-based builder with measured layouts, redesigned add-action modal, and an end-to-end test workflow page. - AI error humanizer: workflow task failures explained in plain English. - Variable selector overhaul: corrected icons, copy, and source resolution; Lead Score variables resolve in path conditions. - Dynamic scheduler routing UI with a new variable selector inside it. - Workflow error emails batched into 30-minute digests instead of one-per-failure spam. MCP & Sidekick - Surface Sidekick: in-app AI assistant with persistent chat history. - MCP server moved to /mcp with OAuth 2.1 authorization for the Anthropic directory. - New MCP tools: generate\_form, import\_leads, submit\_feedback, invite\_member, get\_team\_info, plus AI-score filtering, UTM enrichment, daily-breakdown analytics, funnel data, and per-form filters. - PostHog event tracking on all MCP tool calls with environment context. Forms & Editor - Form editor header redesign. - Graphical options: image media type and orientation support, required validation. - Sidebar redesign with fade mask, stable layout, parallelized environment fetches. - Form renderer cached on Vercel CDN for faster first paint. Analytics & Performance - Google Analytics (GA4) integration with partitioned cookies for iframe embeds. - Form analytics speedup: new indexes and migrated materialized views. - Activity Log per environment: see who did what across the team. - Server-side initial data fetching for Responses and Leads tables with streaming and Suspense. Auth & Account - New auth flow: redesigned sign-in/sign-up with Google OAuth invitee account creation. - Invite lifecycle unified: single token model with consistent redirects through forgot-password. - Post-login redirects straight to environment home. Platform - Trigger.dev v4 migration. - Zod v4 migration across web, types, and database packages. - Next.js 15.5, Prisma v7, and Turbo v2.8 upgrades. - AI SDK v6 and OpenAI v3 with streaming API migration. - API rate limiting on public routes. - Speed Insights integrated. Release ## March 2026 Logic Builder - Logic Builder UI overhaul: routing conditions, variable selection, switch icons, node header features, and Disqualify Lead actions. - Rich JSON editor for HTTP Request configuration in workflows. - Identity Info text comparators restored in form logic. Forms & Editor - AI Lead Scoring in form logic: score leads at submit time. - Show/hide password toggle on PasswordCreatorInput. - Identity Info styling options and redirect URL params visible in editor. - Progress bar logo positioning and margin controls. - Tailwind v4 upgrade with refined animations across the app. Workflows - Email Alert enhancements: multi-template support, file uploader URLs in previews, timezone fixes. - Slack AI email response generation. - Gmail multi-inbox connection. - Soft-deleted responses skip workflows correctly. Leads & Responses - Import leads via button and bulk action in Leads Hub. - Leads table export. - Source column in the response table with bulk action triggers. - No-Show dashboard moved to new Prisma tables. AI Visibility - AI Visibility Dashboard launched: track how your brand shows up across AI search engines. Integrations - HubSpot AI Agent: infers HubSpot forms and payloads for submissions, new contact and company activity tools, more HubSpot functions in form logic. - CRM instruction templates for shared prompt setups. - Calendly iframe double-load and preconnect fixes. Admin & Platform - Spam Dashboard launched. - Environment-level timezone setting. - Usage enforcement and retryable idempotent usage tracking with Trigger.dev fallback. - Environment-level permissions. - Team name editing for owners and admins. - MCP Server initial release with auth. - Eval suites infrastructure for AI feature regression testing. Set up once ## B2B teams running on Surface see 30% more demos within 30 days. [SEE PRICING](https://www.withsurface.com/pricing) --- # Referral Program | Surface Labs URL: https://surface.thesurface.network/referral Surface customer referrals Earn up to $750 when you introduce a new customer to Surface. Last updated: July 26, 2026 ## Who is eligible to participate? The program is open to current Surface customers and approved Surface partners. Surface employees and their immediate family members are not eligible. ## How can I refer someone? Email the prospective customer's name, company, and contact details to [hello@withsurface.com](mailto:hello@withsurface.com?subject=Surface%20referral). Please make the introduction before the company begins an active sales process with Surface. Self-referrals, referrals for your own employer, and companies already in an active Surface sales process are not eligible. ## What is the reward? Rewards are based on the referred customer's first Surface subscription: **$250**For a new customer who subscribes to the Growth plan. **$750**For a new customer who signs an Enterprise agreement. Rewards are issued by PayPal or as an Amazon gift card within 60 days after the referred customer's first paid invoice, provided the account remains active and in good standing. ## How many customers can I refer? You may refer as many new customers as you like. Rewards apply only to net-new Surface customers; former customers are eligible only after 12 months of inactivity. ## What are my responsibilities as a referrer? Make sure each person has agreed to be introduced and to have their business contact details shared with Surface. Do not use spam, misleading claims, paid advertising, or unsolicited outreach to generate referrals. ## What conditions apply? The referred customer must remain subscribed for at least 60 days. Surface may withhold or cancel a reward when a referral is duplicate, fraudulent, abusive, cancelled, unpaid, or otherwise inconsistent with these terms. ## Can the program change? Surface may change or end the program at any time. Rewards already earned under the terms in effect when a qualifying referral was made will be honored. ## How can I get more information? Email [hello@withsurface.com](mailto:hello@withsurface.com?subject=Referral%20program%20question) with any questions about a referral or reward. ## Legal terms Surface reserves the right to determine eligibility, resolve duplicate referrals, and withhold or revoke payments when it reasonably suspects fraud or abuse. This includes referrals made solely to collect a reward without a genuine business relationship or accounts that follow a repeated subscribe-and-cancel pattern. Participants are responsible for any taxes associated with their reward. --- # B2B Inbound Growth Guides | Surface Labs URL: https://surface.thesurface.network/resources/guides - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # B2B Inbound Growth Reports | Surface Labs URL: https://surface.thesurface.network/resources/reports - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # B2B Inbound Growth Templates | Surface Labs URL: https://surface.thesurface.network/resources/templates - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # B2B Inbound Growth Webinars | Surface Labs URL: https://surface.thesurface.network/resources/webinars - Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. - [Google 1 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **test\_cookie**Used to check if the user's browser supports cookies. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **cookietest**This cookie is used to determine if the visitor has accepted the cookie consent box. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [ forms.withsurface.com consent.cookiebot.com 2 ](#) **CookieConsent \[x2\]**Stores the user's cookie consent state for the current domain **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - [ hsadspixel.net hs-banner.com forms.withsurface.com 9 ](#) **\_\_cf\_bm \[x9\]**This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie - [www.withsurface.com 1 ](#) **dmn\_chk\_#**Used to maintain the overall functionality of the website: Assigns the user to a server and detects potential errors on specific servers, allowing the website to reassign the users to another server. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [www.workatastartup.com 1 ](#) **XSRF-TOKEN**Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor. **Maximum Storage Duration**: Session**Type**: HTTP Cookie - Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in. - [Intercom 3 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **intercom-device-id-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-id-#**Allows the website to recoqnise the visitor, in order to optimize the chat-box functionality. **Maximum Storage Duration**: 271 days**Type**: HTTP Cookie **intercom-session-#**Sets a specific ID for the user which ensures the integrity of the website’s chat function. **Maximum Storage Duration**: 7 days**Type**: HTTP Cookie - [ js.intercomcdn.com www.withsurface.com 2 ](#) **intercom.intercom-state-# \[x2\]**Remembers whether the user has minimized or closed chat-box or pop-up messages on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. - [Google 2 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **\_ga**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie **\_ga\_#**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 2 years**Type**: HTTP Cookie - [HubSpot 4 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_hssc**Identifies if the cookie data needs to be updated in the visitor's browser. **Maximum Storage Duration**: 1 day**Type**: HTTP Cookie **\_\_hssrc**Used to recognise the visitor's browser upon reentry on the website. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_\_hstc**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie **hubspotutk**Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. **Maximum Storage Duration**: 180 days**Type**: HTTP Cookie - [ forms.withsurface.com www.withsurface.com 7 ](#) **ph\_#\_posthog \[x3\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTTP Cookie **ph\_#\_primary\_window\_exists \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage **ph\_#\_window\_id \[x2\]**Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator. **Maximum Storage Duration**: Session**Type**: HTML Local Storage - Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. - [Google 3 ](#)[Learn more about this provider](https://business.safety.google/privacy/ "Learn more about this provider Google's privacy policy - opens in a new window") Some of the data collected by this provider is for the purposes of personalization and measuring advertising effectiveness. The provider may use the IP Addresses for ads measurement and ads personalization. **pagead/1p-user-list/#**Tracks if the user has shown interest in specific products or events across multiple websites and detects how the user navigates between sites. This is used for measurement of advertisement efforts and facilitates payment of referral-fees between websites. **Maximum Storage Duration**: Session**Type**: Pixel Tracker **\_gcl\_au**Used to measure the efficiency of the website’s advertisement efforts, by collecting data on the conversion rate of the website’s ads across multiple websites. **Maximum Storage Duration**: 3 months**Type**: HTTP Cookie **\_gcl\_ls**Tracks the conversion rate between the user and the advertisement banners on the website - This serves to optimise the relevance of the advertisements on the website. **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [HubSpot 1 ](#)[Learn more about this provider](https://legal.hubspot.com/privacy-policy "Learn more about this provider HubSpot's privacy policy - opens in a new window") **\_\_ptq.gif**Sends data to the marketing platform Hubspot about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: Session**Type**: Pixel Tracker - [Intercom 1 ](#)[Learn more about this provider](https://www.intercom.com/terms-and-policies#privacy "Learn more about this provider Intercom's privacy policy - opens in a new window") **gtm\_id**Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. **Maximum Storage Duration**: 1 year**Type**: HTTP Cookie - Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies. - [Amazon 2 ](#)[Learn more about this provider](https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UTF8&nodeId=468496 "Learn more about this provider Amazon's privacy policy - opens in a new window") **\_\_test\_\_**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_reb2bloaded**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [cdn.jsdelivr.net 4 ](#) **A#**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage **surfaceLeadData**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage **surface\_journey\_id**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **surface\_recent\_visit**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie - [forms.withsurface.com 2 ](#) **cmn9cxtcl0009jr04131hhrbh\_pa**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **LOCAL\_SURFACE\_LEAD\_IDENTIFY\_DATA**Pending **Maximum Storage Duration**: Persistent**Type**: HTML Local Storage - [www.withsurface.com 1 ](#) **ph\_phc\_XrBy8zHermZlEtm1xqYUMPJuQtpx6u49C7DT5VlTuiE\_posthog**Pending **Maximum Storage Duration**: Session**Type**: HTML Local Storage - [www.workatastartup.com 2 ](#) **\_bf\_session\_exists**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie **\_bf\_session\_key**Pending **Maximum Storage Duration**: Session**Type**: HTTP Cookie --- # Security at Surface Labs URL: https://surface.thesurface.network/security Our approach ## Control the systems agents can reach, and what they can do. Surface brings lead data, campaign execution, and marketing agents into one governed layer. Security controls are designed around the full path from connection to decision to action. 01 ## Organizational security Security is a shared operating responsibility across Surface, not a final review added after a product ships. ### Program ownership Security responsibilities, policies, and review paths are defined across the people who build and operate Surface. ### Team practices Confidentiality, secure data handling, access hygiene, and security awareness are part of how our team works. ### Security reviews We support customer diligence with questionnaires, architecture discussions, data-processing terms, and available documentation. ### Incident readiness Our security process is designed around clear escalation, investigation, mitigation, and customer communication. 02 ## Cloud and data security Surface is designed to protect customer data throughout the systems that store, process, and move it. ### Protected data flows Connections are designed to protect data as it moves between Surface, your team, and authorized destinations. ### Workspace separation Customer and agency workspaces are designed to keep data, settings, and execution context separated. ### Monitoring and recovery Operational monitoring, backups, and recovery planning are part of the controls reviewed with customer security teams. ### Data lifecycle Retention, deletion, hosting, and subprocessor questions are handled as part of the security and contractual review. 03 ## Access security Access should be deliberate, limited, and removable, for both people and agents. ### Least-necessary access Connections can be scoped around the systems and actions a workflow needs instead of exposing the entire stack. ### Role-based control Workspace permissions help teams control who can configure connections, review work, and authorize actions. ### Human approval Teams can keep sensitive actions behind review gates before an agent publishes, routes, or changes a live workflow. ### Revocation Access can be removed by disconnecting systems, changing permissions, or stopping the workflow that uses it. 04 ## AI and agent governance Surface agents operate inside the rules, data access, and approval boundaries your team sets. ### Rules before execution Qualification policies, brand requirements, routing logic, and channel constraints can be defined before work begins. ### Reviewable work Research, decisions, and generated assets can be reviewed before they reach customers or production systems. ### Traceable actions Surface is designed to preserve the context behind agent decisions so teams can understand what happened and why. ### Controlled destinations Agents act through approved connections and workflows rather than operating outside your governed Surface workspace. 05 ## Vendor and risk management Security depends on the services around the product as well as the product itself. ### Vendor review Services that may process or support customer data are evaluated as part of the vendor approval process. ### Risk assessment Security and operational risks are reviewed as the product, infrastructure, and vendor footprint change. ### Customer diligence We work directly with security and legal teams to answer architecture, data handling, and contractual questions. ### Available evidence Current documentation and available reports are provided through the security review process. 06 ## Subprocessors Surface works with vetted third-party service providers to deliver and operate the platform. ### Published list We maintain a current list of subprocessors that may process or support customer data as part of Surface operations. [View our subprocessor list](https://www.withsurface.com/subprocessors). ### Vendor evaluation Each subprocessor is reviewed for security, data handling, and compliance before being approved to support Surface services. 07 · Contact and review ## Bring your security team into the conversation. We can walk through Surface's architecture, data flows, agent controls, contractual terms, and currently available security documentation. To report a security vulnerability or concern, please contact [security@withsurface.com](mailto:security@withsurface.com). [Request a security review](https://www.withsurface.com/book-a-demo) --- # Closed-Loop Growth | Improve Every Campaign | Surface Labs URL: https://surface.thesurface.network/solutions/closed-loop-growth ## Every qualified buyer makes the next growth decision smarter. What sales learns at the end of the funnel qualifies the next lead and shapes the next campaign. ## Click a closed deal and send it back to the next inbound rule. Won and lost both teach the system. Apply an outcome and the next lead is scored with that lesson. ## How it works Surface feeds every revenue outcome into the next campaign. 1. 01 ### Capture the outcome. Won, lost, and accepted leads write back onto the same record. Won 01 Lost 02 Accepted 03 2. 02 ### Update the rule. Feed that outcome into qualification, routing, and the next brief. Score 01 Route 02 Brief 03 3. 03 ### Run the next campaign. The next piece of work starts from what actually created revenue. Campaign 01 Audience 02 Learn 03 ## Then the outcome writes the next change. Won, lost, and accepted leads turn into the next rule, route, or campaign. ## Growth tools usually lose the thread When those systems remain disconnected, teams optimize each stage for its local metric and lose the buyer-level evidence that could improve the whole journey. ## One buyer journey, one compounding loop - ### Capture the partial response A prospect starts a form and leaves. Instead of letting the interaction disappear, Surface captures, enriches, and retains the permissioned information already provided. - ### Qualify the account, create the opportunity Lead Intelligence evaluates the account against approved ICP rules, and sales follows up. Scheduling, ownership, and outcomes synchronize with HubSpot or Salesforce. - ### Learn what mattered, create for similar buyers The opportunity becomes a new signal, and a Content Campaign Agent creates for similar buyers. The team reviews the campaign plan and connected assets before publishing. - ### Promote with the same context, measure the result Promotion uses the same buyer context; selected pilot customers get Ad Campaign Agent recommendations for human approval. New inbound is measured by quality and pipeline. ## One shared context, from buyer signal to qualified pipeline ## Agents turn the context into coordinated work Each workflow uses shared definitions and returns its result to the same system. Kintsugi ## How Kintsugi built a cleaner, faster path from visitor to meeting **11K+**leads captured **91%**enriched automatically [Read the story](https://www.withsurface.com/customers/kintsugi) The details ## FAQ What makes Surface a closed-loop growth system? Buyer signals inform qualification and campaigns, while sales acceptance, opportunities, and revenue outcomes flow back into the system to improve the next decision. How quickly can we get started? Most teams begin with one high-value workflow, connect the systems and context it needs, validate the output, and expand from there. Timing depends on the use case and existing data setup. Does Surface replace our CRM or marketing automation platform? No. Surface works alongside systems such as Salesforce and HubSpot, adding shared intelligence and agentic execution without requiring a rip-and-replace migration. How does Surface use AI agents? Surface agents research, reconcile data, detect signals, create campaign work, and coordinate next actions using the context and permissions available in your workspace. Can our team review work before it goes live? Yes. Agent actions can follow explicit permissions, approval paths, and human review so your team controls what is published or changed. What data does Surface need? Surface can use first-party website activity, forms, CRM records, campaign engagement, and revenue outcomes. The exact connections depend on the workflow you choose to launch. How is Surface priced? Surface is structured around platform scope and usage rather than charging for every teammate. Talk with the team for pricing based on your workflows and volume. Set up once ## Turn your next qualified outcome into your next growth advantage [Launch from Claude or Codex](https://app.withsurface.com/auth/signup) --- # Generate More Qualified B2B Demand | Surface Labs URL: https://surface.thesurface.network/solutions/generate-qualified-demand ## Create more of the demand that becomes pipeline Surface learns from the buyers sales accepts and the opportunities they create. ## Select the buyers sales already wanted. Build the next brief from them. This is not a blank campaign. Click the accepted records, then build a brief from the roles and questions they share. ## How it works Surface turns buyer evidence into the next campaign brief. 1. 01 ### Start from evidence. Use accepted leads and buyer questions, not a blank brief. Leads 01 Questions 02 ICP 03 2. 02 ### Write one brief. Lock audience, message, and the outcome sales wants again. Audience 01 Message 02 Outcome 03 3. 03 ### Measure qualified demand. Judge the campaign by inbound quality, not pageviews. Inbound 01 Meetings 02 Pipeline 03 ## Then the campaign starts from those buyers, not a blank page. Accepted leads and the questions they asked become the brief. ## Demand generation needs a quality signal Most campaign systems optimize what they can see quickly: impressions, clicks, submissions, and cost per lead. Surface connects campaign activity to fit, sales acceptance, opportunity, and revenue so the next campaign can be based on outcomes deeper in the funnel. ## Lead with content grounded in real buyers Content Campaign Agents use those signals to plan and produce reviewed campaigns for similar audiences. [Explore Content Campaigns →](https://www.withsurface.com/solutions/launch-campaigns-faster) ## How the loop works 1. ### Connect and analyze Connect qualified-lead, opportunity, ICP, source, and campaign context, and identify patterns worth testing without treating correlation as certainty. 2. ### Select and generate Select a buyer, problem, offer, channel, and measurable campaign outcome, then generate a plan and coordinated assets. 3. ### Review and publish Route each asset through human review and brand controls, then publish or export through supported connections. Stops for human approval 4. ### Measure and feed the loop Measure engagement, inbound quality, sales acceptance, and pipeline, and feed validated outcomes into the next campaign. ## Paid campaign workflows are in pilot For selected customers, Ad Campaign Agents can help: - Build audiences - Recommend creative and landing-page variants - Connect spend to qualified outcomes - Propose budget or targeting changes [Launch campaigns faster →](https://www.withsurface.com/solutions/launch-campaigns-faster) All actions operate within explicit spend, platform, brand, and approval guardrails; availability and supported ad platforms must be confirmed. ## Start where your data is strongest Numbers Station ## How Numbers Station connected lead intelligence to pipeline growth **30%**increase in pipeline **95%**leads enriched automatically [Read the story](https://www.withsurface.com/customers/numbers-station) The details ## FAQ How does Surface generate more qualified demand? Surface turns real buyer, content, conversion, and revenue signals into campaign direction, helping teams create demand around evidence instead of assumptions. How quickly can we get started? Most teams begin with one high-value workflow, connect the systems and context it needs, validate the output, and expand from there. Timing depends on the use case and existing data setup. Does Surface replace our CRM or marketing automation platform? No. Surface works alongside systems such as Salesforce and HubSpot, adding shared intelligence and agentic execution without requiring a rip-and-replace migration. How does Surface use AI agents? Surface agents research, reconcile data, detect signals, create campaign work, and coordinate next actions using the context and permissions available in your workspace. Can our team review work before it goes live? Yes. Agent actions can follow explicit permissions, approval paths, and human review so your team controls what is published or changed. What data does Surface need? Surface can use first-party website activity, forms, CRM records, campaign engagement, and revenue outcomes. The exact connections depend on the workflow you choose to launch. How is Surface priced? Surface is structured around platform scope and usage rather than charging for every teammate. Talk with the team for pricing based on your workflows and volume. Set up once ## Turn one qualified-buyer insight into a campaign [Get Started](https://app.withsurface.com/auth/signup) --- # Improve B2B Inbound Lead Quality | Surface Labs URL: https://surface.thesurface.network/solutions/improve-lead-quality ## Give sales inboundit wants to work ## Flip a rule and watch the same lead pass or fail. This is the shared inbound definition. Click a lead, then turn rules on and off. Sales and marketing see the same decision. ## How it works Surface evaluates every lead against a natural-language ruleset and sends research agents for the real-time evidence behind the decision. 1. 01 ### Define lead quality. Write the rules in the same language your team already uses. Fit 01 Intent 02 Value 03 2. 02 ### Research every lead. Verify company, role, and use case with source evidence. Company 01 Role 02 Use case 03 3. 03 ### Route with context. Send sales the score, rationale, and recommended next step. Score 01 Evidence 02 Owner 03 ## Then sales sees the same decision, with the evidence attached. Fit, exclusions, and research land on one record before anyone picks up the lead. The details ## FAQ How does Surface improve lead quality? Surface unifies first-party behavior, enrichment, fit, intent, and account context before a lead reaches sales, helping teams prioritize real buyers and filter low-quality demand. Does Surface replace our CRM or marketing automation platform? No. Surface works alongside systems such as Salesforce and HubSpot, adding shared intelligence and agentic execution without requiring a rip-and-replace migration. What data does Surface need? Surface can use first-party website activity, forms, CRM records, campaign engagement, and revenue outcomes. The exact connections depend on the workflow you choose to launch. How is Surface priced? Surface is structured around platform scope and usage rather than charging for every teammate. Talk with the team for pricing based on your workflows and volume. Set up once ## Build an inbound definition sales and marketing can share [Fix lead quality](https://www.withsurface.com/book-a-demo) --- # Increase B2B Inbound Conversion | Surface Labs URL: https://surface.thesurface.network/solutions/increase-inbound-conversion ## Inbound looks strong but pipeline doesn't? Surface improves the path from first response to qualified meeting, without losing the context sales needs. ## Change the form. Watch the same visitor finish or drop. Pick a visitor. Let the agent shorten the path, or force every field. Shorter forms convert more sessions into a meeting. ## How it works Surface turns every response into the right conversion path. 1. 01 ### Capture buyer intent. Dynamic forms keep useful responses and remove unnecessary fields. Form response 01 Buyer activity 02 Account data 03 2. 02 ### Qualify and route. Score each buyer and send them to the right next step. Enrich 01 Score 02 Route 03 3. 03 ### Learn from revenue. Use CRM outcomes to improve every future conversion path. Meeting 01 Opportunity 02 Revenue 03 ## Then the response becomes work, not a notification. A finished or partial form can enrich, route, notify, or book without a rebuild. The details ## FAQ How does Surface increase inbound conversion? Surface improves the path from first response to qualified meeting with more relevant forms, partial-response capture, enrichment, qualification, routing, and scheduling. What happens when someone starts a form but does not finish? Surface can preserve permitted partial-response context and use an agreed recovery workflow, helping your team recover real buyer intent that would otherwise disappear. Will increasing form conversion reduce lead quality? The goal is qualified pipeline, not more low-intent form fills. Surface keeps enrichment, qualification, sales acceptance, and downstream opportunity outcomes connected so conversion gains can be evaluated alongside lead quality. Does Surface work with our existing CRM and marketing stack? Yes. Surface works alongside systems such as HubSpot and Salesforce, adding conversion, enrichment, routing, and scheduling workflows without requiring a rip-and-replace migration. Set up once ## Find out which conversion leak is worth fixing first [Find your inbound leaks](https://www.withsurface.com/book-a-demo) --- # Launch Content Faster with AI Agents | Surface Labs URL: https://surface.thesurface.network/solutions/launch-campaigns-faster ## Publish the next great piece this week, not next quarter Surface turns real buyer insight into briefs, drafts, and publish-ready content, so your team can ship faster without lowering the bar. ## Draft each asset, then approve the ones that can ship. Click an asset, draft it, then approve it. Nothing publishes until a person signs the set. ## How it works Surface turns buyer evidence into reviewed content, then learns from what creates qualified demand. 01 ### Find the opportunity. Agents find what buyers need from search, sales, and revenue data. Sales calls18 Search demand42 CRM outcomes27 02 ### Create the campaign. Turn one approved brief into channel-ready assets. 01 Brief 02 Article 03 Landing page 04 Social 03 ### Publish and improve. Use qualified leads and pipeline to guide what comes next. Qualified visits+34% Accepted leads+21% Pipeline+16% ## Then one brief turns into the assets that need review. Landing page, emails, and supporting pieces sit on the same plan. ## Example prompts The details ## FAQ How does Surface decide what content to create? Surface can use qualified-buyer patterns already in your funnel, including the questions buyers ask, the messages that draw serious interest, and the content associated with opportunities. What content can Surface help create? Surface can turn approved buyer insight into briefs, articles, landing-page copy, social posts, and other scoped assets that share the same sources and message. Can our team review content before it is published? Yes. Teams define sources, brand and compliance rules, named approvers, and publishing permissions. Human review remains in the workflow before content moves into production. Does Surface replace our CMS or writing tools? No. Surface works alongside your existing CMS and supported content tools. Teams can also create from Claude or Codex while Surface supplies buyer context, permissions, and measurement. Set up once ## Turn buyer evidence into content ready to publish [Launch from Claude or Codex](https://www.withsurface.com/mcp) --- # Recover B2B Form Abandonment | Surface Labs URL: https://surface.thesurface.network/solutions/recover-form-abandonment ## An unfinished form can still contain a valuable signal Buyers pause for dozens of reasons: a question requires research, the form asks too much, or the timing changes. ## Keep the answers they already gave you. Click an unfinished session. Recover the high-intent ones. Leave the rest logged so nothing is invented and nothing is blasted. ## How it works Surface keeps unfinished intent and brings the buyer back. 1. 01 ### Keep the partial. Save every field the buyer already gave you. Email 01 Company 02 Use case 03 2. 02 ### Follow up in context. Resume the same session instead of starting from a blank form. Timing 01 Message 02 Channel 03 3. 03 ### Book or hold. Finish into a meeting, or hold the record with the reason attached. Meeting 01 Review 02 CRM 03 ## Then the unfinished session is still a record. Every answered field stays, so follow-up starts from what the buyer already gave you. ## Recover 30–50% of eligible partial responses Responses that would otherwise disappear when a buyer leaves before submitting. ## Know where demand disappears Aggregate completion rate can hide the real problem. ## A controlled recovery workflow 1. ### Capture permitted progress. Preserve partial information only where the team's disclosures, consent model, and applicable requirements allow it. 2. ### Resolve context and assess fit. Enrich with available company context, then apply the same qualification policy used for completed inbound. 3. ### Choose a proportionate action. Resume the experience, invite completion, route for review, add to an approved nurture, or take no action. Stops for human approval 4. ### Measure recovery honestly. Track recovered completions, sales acceptance, and opportunities, not merely emails sent. A partial response is not automatic permission for unrestricted outreach. Recovery rules must reflect consent, privacy, channel policy, and the buyer's demonstrated intent. ## Fix the form, not just the symptom Recovery is most useful when it reveals what to change. - Where high-fit visitors abandon. - Which questions add little qualification value. - Whether enrichment can replace manual fields. ## Give sales context, not scraps When an abandoned response qualifies for human follow-up, the record can include the qualification rationale and the recovery policy that triggered the handoff. A CRM timeline for one record: the partial response, the enrichment and qualification assessment, the review decision, and the booked outcome with its owner. Kintsugi ## How Kintsugi built a cleaner, faster path from visitor to meeting **11K+**leads captured **91%**enriched automatically [Read the story](https://www.withsurface.com/customers/kintsugi) The details ## FAQ How does Surface recover form abandonment? Surface identifies partial intent, preserves the context available at abandonment, and helps teams create appropriate recovery paths without treating every incomplete form as a qualified lead. How quickly can we get started? Most teams begin with one high-value workflow, connect the systems and context it needs, validate the output, and expand from there. Timing depends on the use case and existing data setup. Does Surface replace our CRM or marketing automation platform? No. Surface works alongside systems such as Salesforce and HubSpot, adding shared intelligence and agentic execution without requiring a rip-and-replace migration. How does Surface use AI agents? Surface agents research, reconcile data, detect signals, create campaign work, and coordinate next actions using the context and permissions available in your workspace. Can our team review work before it goes live? Yes. Agent actions can follow explicit permissions, approval paths, and human review so your team controls what is published or changed. What data does Surface need? Surface can use first-party website activity, forms, CRM records, campaign engagement, and revenue outcomes. The exact connections depend on the workflow you choose to launch. How is Surface priced? Surface is structured around platform scope and usage rather than charging for every teammate. Talk with the team for pricing based on your workflows and volume. Set up once ## See how much qualified intent is dropping out [Find your inbound leaks](https://www.withsurface.com/book-a-demo) --- # Intelligent Lead Routing & Scheduling | Surface Labs URL: https://surface.thesurface.network/solutions/route-and-book-leads-instantly ## Intelligent routing that adapts in real time Qualify, route, and schedule buyers in real time without complex routing logic or per-seat pricing. ## Pick a lead, pick an owner, book the slot. Territory and capacity decide who can take the meeting. Click through to write the booking back to the record. ## How it works Surface moves qualified buyers from response to meeting. 1. 01 ### Capture and qualify. Combine form data, buyer activity, and real-time research. Response 01 Context 02 Decision 03 2. 02 ### Route the buyer. Apply ownership, territory, capacity, and qualification rules. Territory 01 Owner 02 Capacity 03 3. 03 ### Book and sync. Show the right calendar and write every detail back to CRM. Calendar 01 Meeting 02 CRM 03 ## Then the owner and the calendar are the same step. Territory, capacity, and an open slot sit on the record that just qualified. The details ## FAQ What signals can Surface use to route a lead? Surface can evaluate form responses, enrichment, lead scores, account research, CRM ownership, territory, intent, and other criteria as the lead arrives. It then applies your routing rules using the full buyer and account context. How does Surface help qualified buyers book instantly? Once a buyer qualifies, Surface sends them directly to the appropriate scheduling path based on ownership and your routing criteria. The buyer can book without waiting for a separate manual handoff. Does Surface replace HubSpot or Salesforce? No. Surface works alongside your CRM and marketing automation systems. It adds real-time qualification, research, routing, and scheduling while preserving the systems your team already uses as its source of record. How easy is Surface routing to build and maintain? Describe the routing logic you need, test it clearly, and update it without rebuilding a maze of branches every time your go-to-market motion changes. Does Surface use seat-based pricing for routed reps? No. Route to one rep or one thousand. Surface scales with the work processed, not the number of salespeople who can receive a lead. How does Surface make real-time routing decisions? Surface adapts every route and scheduling path using lead scores, deep account research, CRM ownership, intent, territory, or any other criteria you choose. Set up once ## Map one inbound path from form to owner [Book a Demo](https://www.withsurface.com/book-a-demo) --- # Surface Studio | Everything we build URL: https://surface.thesurface.network/studio Surface Studio ## Surface Studio is the home for everything we build at Surface. [See Pricing](https://www.withsurface.com/pricing) [Surface App](https://app.withsurface.com/)[Intelligent CMS](https://cms.withsurface.com/)[Outbound](https://outbound.withsurface.com/)[Signals](https://signal.withsurface.com/)[TAM](https://tam.admin.withsurface.com/)[MCP](https://withsurface.com/docs/mcp-server/overview) [Surface App](https://app.withsurface.com/)[Intelligent CMS](https://cms.withsurface.com/)[Outbound](https://outbound.withsurface.com/)[Signals](https://signal.withsurface.com/)[TAM](https://tam.admin.withsurface.com/)[MCP](https://withsurface.com/docs/mcp-server/overview) --- # Subprocessors | Surface Labs URL: https://surface.thesurface.network/subprocessors Surface Labs, Inc. (“Surface”) engages the third-party subprocessors listed below to help deliver its services. A subprocessor is a third party that processes personal data on Surface's behalf in connection with providing the services to our customers. The tables below identify each subprocessor, the purpose of its processing, and where that processing takes place. This page reflects our current subprocessors and is maintained as our services evolve. Customers who have entered into a Data Processing Agreement with Surface may subscribe to notifications of changes to this list as set out in that agreement. ## Infrastructure and platform Infrastructure and platform Subprocessor Purpose of processing Processing location Amazon Web Services, Inc. Cloud infrastructure and hosting United States Vercel, Inc. Application hosting and deployment United States Cloudflare, Inc. CDN, edge network, and DDoS protection United States / Global Supabase, Inc. Database and authentication United States Upstash, Inc. Cache and message queue (Redis) United States Trigger.dev Ltd. Background jobs and workflow orchestration United States ## Data enrichment and validation Used to enrich lead records and validate contact data in connection with providing the services. Data enrichment and validation Subprocessor Purpose of processing Processing location MaxMind Geolocation United States ZeroBounce Email validation United States MillionVerifier Email validation Hungary / European Union Apollo B2B contact and company data United States Exa Web search and research United States ## AI model providers Used to power Surface's AI features, including lead scoring, enrichment, and agent workflows. AI model providers Subprocessor Purpose of processing Processing location OpenAI, LLC Large language model inference United States Anthropic, PBC Large language model inference United States ## Analytics and internal operations Analytics and internal operations Subprocessor Purpose of processing Processing location PostHog, Inc. Product analytics United States Slack Technologies, LLC Internal notifications and communications United States ## Model providers and training Model training Where Surface uses large language model providers to process customer personal data, that data is not used by those providers to train or fine-tune their models. Surface uses processing arrangements with these providers that prohibit such use. ## Changes to this list Surface may update its subprocessors from time to time. For customers with a Data Processing Agreement in place, Surface will provide notice of additions to this list, and an opportunity to object, in accordance with the terms of that agreement. ## Questions For questions about this list or Surface's data processing practices, contact [privacy@withsurface.com](mailto:privacy@withsurface.com). --- # Terms and Conditions | Surface Labs URL: https://surface.thesurface.network/terms_and_conditions ## Section 1: SaaS Services and Support Surface Labs commits to providing Services using commercially reasonable efforts. Customers establish administrative credentials during registration, which the company may refuse or cancel if deemed inappropriate. Technical support is offered consistent with standard industry practices. ## Section 2: Restrictions and Responsibilities Customers cannot reverse engineer, decompile, or attempt to discover underlying source code or algorithms. The service prohibits modification, derivative works creation, timesharing arrangements, or removal of proprietary notices. Regarding distributed software, Surface grants a “non-exclusive, non-transferable, nonsublicensable license” for service connection only. Export restrictions apply: customers must comply with U.S. Department of Commerce and Treasury regulations. Under FAR and DFAR provisions, the software qualifies as commercial items with restricted government use. Customers represent they'll follow company policies and applicable laws, indemnifying Surface against damages from violations. Customers remain responsible for maintaining Equipment security, account passwords, and file protection. ## Section 3: Confidentiality and Proprietary Rights Both parties protect each other's business and technical information. Confidentiality obligations expire after five years or when information becomes publicly available. Customers retain ownership of their data; Surface retains rights to the service, improvements, and related technology. Surface may “collect and analyze data relating to provision, use and performance” and use de-identified information to improve services and offerings. ## Section 4: Payment of Fees Customers pay fees per the Order Form. Surface may adjust fees with 30 days' notice. Billing disputes must be reported within 60 days of the statement. Invoices require payment within seven days; unpaid amounts incur 1.5% monthly finance charges plus collection expenses and may trigger immediate termination. ## Section 5: Term and Termination The agreement runs for the Initial Service Term with automatic renewal unless either party provides 30 days' termination notice. Either party may terminate for material breach with 30 days' notice (immediate for nonpayment). Surviving obligations include confidentiality, warranty disclaimers, and liability limitations. ## Section 6: Warranty and Disclaimer Surface maintains services “in a manner which minimizes errors and interruptions” using industry standards. However, the company “does not warrant that the services will be uninterrupted or error free” and disclaims all implied warranties including merchantability and fitness for particular purposes. ## Section 7: Indemnity Surface indemnifies customers against third-party infringement claims by the service itself. The company may replace, modify, obtain licenses, or terminate service if infringement occurs. Indemnification excludes non-Surface components, customer specifications, modifications, combinations, or non-compliant usage. ## Section 8: Limitation of Liability Except for bodily injury, Surface and suppliers “shall not be responsible or liable” for data loss, business interruption, or indirect damages. Total liability caps at fees paid in the preceding 12 months. ## Section 9: Miscellaneous The agreement is non-assignable by customers without consent; Surface may assign freely. California law governs; good faith dispute resolution applies. Parties must issue a mutually agreed press release within 90 days and establish a reference account relationship. --- # What can you do with Surface? URL: https://surface.thesurface.network/use-cases Surface use cases Here are some actions that either humans or AI agents can take on Surface ## Everything in Surface is built for both humans and agents. [ **Maddy Fennessy**Growth Marketing Lead, Metronome > “We feel pretty embedded in Surface, especially since we did the PLG stuff there. I would consider Surface to be like a pretty core part of what is running our website, which is a good thing.” ](https://www.withsurface.com/customers) [ **Shubh Agrawal**San Francisco, Valley > “If we turned off Surface tomorrow, we'd lose a lot of inbound. We're almost entirely inbound-driven, so Surface is a critical part of how we operate.” ](https://www.withsurface.com/customers/valley) [ **Alexandra Doan**San Francisco, Nextiva > “We actually saw that 37% more users on average converted with the new form that they built for us” ](https://www.withsurface.com/customers/nextiva) [ **Pujun Bhatnagar**CEO, Kintsugi > “We're growing at the speed of light, and Surface is one of the few vendors keeping up with us. I'd pay whatever it takes to solve this problem, and Surface solved it.” ](https://www.withsurface.com/customers/kintsugi) [ **Angela Kou**Chief of Staff, Juicebox > “Whenever I had a feature request, the Surface team would update me throughout the process and follow up after launch to make sure everything was working correctly. It really feels like a white-glove experience.” ](https://www.withsurface.com/customers/juicebox) [ **Ian Christopher**CEO, Galley > “We used Typeform in the early days. It was great but you can tell when a company outgrows it. Surface gives us the mechanics we liked from Typeform, but with enterprise-grade control over brand, format, and functionality.” ](https://www.withsurface.com/customers/galley) Set up once ## Turn your next growth problem into a connected workflow. [BOOK A DEMO](https://www.withsurface.com/book-a-demo) --- # AI Search Inbound Funnel | Surface Labs URL: https://surface.thesurface.network/use-cases/ai-search-inbound STEP 1 ## AI-optimized content that gets cited Surface's AI Content Agent writes blog posts, guides, and comparison pages optimized for AI citations. Structured data, answer formatting, and entity optimization ensure ChatGPT, Claude, and Perplexity cite your content when buyers ask questions. Blog PostSurface #### Best Lead Routing Software for B2B SaaS in 2026 Buyers asking AI assistants for recommendations cite the most structured, factual sources. Here's how the leading platforms compare on speed, routing logic, and integrations… AEO optimizedSEO score 92Schema.org AI Citation Score0% STEP 2 ## Get cited in AI-generated answers When a VP of Marketing asks ChatGPT “What's the best lead routing tool?” your content appears in the answer. Surface's AI Visibility Dashboard tracks citations across ChatGPT, Claude, Perplexity, and Gemini, so you know exactly where you're showing up. scanning ai engines... STEP 3 ## Content drives qualified traffic AI-referred visitors land on your blog posts and landing pages. Surface tracks the referral source (ChatGPT, Perplexity, etc.) so you know exactly which AI channel drives traffic, not just “direct” in your analytics. matching referral sources... STEP 4 ## Capture and qualify in seconds Surface Capture forms on your content pages collect the lead's information. The AI agent scores them against your ICP, enriches with company data, and filters spam, all in under 2 seconds. enriching lead data... STEP 5 ## Right rep, right meeting, right now Based on your routing rules, the qualified lead is assigned to the right AE and booked on their calendar. The rep gets a full brief: company data, AI referral source, form responses, and qualification signals. finding the right rep... STEP 6 ## See exactly which content drives revenue Surface Content Ops connects the dots: which blog post → which AI citation → which lead → which demo → which deal. Content attribution that proves ROI, not just traffic numbers. connecting content touchpoints... --- # Surface vs content agencies: an engine, not a retainer URL: https://surface.thesurface.network/vs/content-agencies Surface vs content agencies ## Agencies bill for hours. Surface engineers a system that compounds. A content agency ships deliverables and sends an invoice. Surface Content Ops builds a content engine (strategy, an AI content agent, AI-visibility tracking, and attribution) that gets better every month and ties every piece to pipeline. ## 3 reasons teams pick Surface over a content agency System vs deliverables ### You're renting output, not building an engine. **Content agencies.** Ships one-off deliverables against a retainer. **Surface.** Builds a content system that compounds, and it's yours to keep. Tied to pipeline ### Billed by the hour, not the outcome. **Content agencies.** Reports on drafts shipped and hours spent. **Surface.** Ties every piece to AI visibility, traffic, and pipeline. Own it forever ### When the retainer ends, the knowledge walks out. **Content agencies.** Strategy and institutional knowledge live with the agency. **Surface.** The strategy and training are yours. Keep running the software for a fraction of the cost. ## Capability by capability Yes Built inPartial PartialNo Not built in Capability Content agencies Surface Content strategy you own & keep No Yes AI content agent: drafts at scale No Yes AI-visibility tracking (AI-search citations) No Yes Attribution to pipeline No Yes Compounds month over month No Yes Hands-on bespoke human creative Yes Partial Built-in capabilities 1/ 6 5/ 6 ## Surface engineers what agencies bill for. When you want a content engine you own, not a retainer. Strategy plus an AI content agent that drafts at scale AI-visibility tracking across ChatGPT, Perplexity and the AI answers Attribution that ties every piece to pipeline Compounds every month instead of resetting each invoice Keep the system (and the strategy) when you scale down Content agencies When you want fully-outsourced, hands-on human creative. Bespoke deliverables against a monthly retainer Billed by the hour, reported in drafts shipped Strategy and knowledge live with the agency, not you No AI-visibility tracking or attribution built in Output stops the month the contract ends ## Use both. Agencies create, Surface systematizes. Keep your agency for hands-on creative, and run it on Surface Content Ops, so the strategy, visibility, and attribution compound and stay yours. Content agency Produces bespoke content on a retainer Surface Labs Turns it into a system that compounds and attributes Set up once ## Agencies bill hours. Surface builds an engine. [Book a demo](https://www.withsurface.com/book-a-demo) --- # Surface vs Profound: AI-search visibility into pipeline URL: https://surface.thesurface.network/vs/profound Surface vs Profound ## Profound shows where you stand. Surface turns it into pipeline. Profound measures your visibility in ChatGPT, Perplexity and the AI answers. Surface captures, qualifies and converts the inbound that visibility drives into booked demos. ## 3 reasons teams pick Surface over Profound Measure vs convert ### Visibility is the start, not the win. **Profound.** Tells you where you appear in AI answers. **Surface.** Converts that inbound into qualified, routed, booked demos. Whole funnel ### Mentioned doesn't pay. **Profound.** Stops at the citation. **Surface.** Captures, qualifies, routes and recovers the rows Profound leaves empty. Tied to revenue ### Graded on pipeline, not presence. **Profound.** Reports citations and visibility scores. **Surface.** Grades every move against pipeline, because the traffic runs through us. ## Capability by capability Yes Built inNo Not built in Capability Profound Surface Capture & de-anonymize inbound No Yes Qualify + block spam / low-intent No Yes Route to the right rep instantly No Yes Booked demos / converted pipeline No Yes Track brand visibility in AI answers Yes No Built-in capabilities 1/ 5 4/ 5 ## Surface converts what Profound finds. When you need that AI traffic turned into pipeline. Captures and de-anonymizes the inbound visibility drives Qualifies, scores and blocks spam and low-intent Routes the right leads to the right rep instantly Books demos and ties every move to pipeline Recovers the inbound that never converts Profound When you only need to measure where you appear in AI answers. Tracks visibility, but stops at the citation No capture or de-anonymization of inbound No qualification, scoring or routing No booking or pipeline attribution Measures, but doesn't convert ## Use both. Profound finds you, Surface converts. Keep Profound for measurement, and point that traffic at Surface to capture, qualify and book the demos. Profound Finds you in ChatGPT, Perplexity and the AI answers Surface Labs Captures, qualifies and books that inbound Set up once ## Everyone gets you mentioned. Surface gets you customers. [Book a demo](https://www.withsurface.com/book-a-demo) --- # Surface vs. Qualified Piper for B2B Inbound | Comparison URL: https://surface.thesurface.network/vs/qualified Surface vs. Qualified ## AI SDR engagement orfull lead intelligence?Start with the operating model For some teams, Piper is the right conversational conversion layer. For others, Surface is the broader intelligence and learning system. Verdict The lanes can also stack: Qualified as an engagement surface connected to Surface and the CRM. ## The short version - - You want an AI SDR to hold real-time website conversations and continue engagement in email. - Conversational qualification, content offers, instant meeting booking, and dynamic routing are the primary motion. - Salesforce is central to the architecture and you value Qualified's native Salesforce positioning. - - You need one lead-intelligence record spanning capture, identity, enrichment, sourced research, qualification evidence, routing, and downstream outcomes. - Permissioned partial-response capture and recovery are important parts of the website conversion strategy. - Sales needs a researched, evidence-backed account brief before engagement. - - Piper owns conversational web and email engagement while Surface provides a broader qualification, research, or measurement context. - Surface handles partial and completed inbound signals, then eligible buyers enter a Piper conversation or meeting flow. - Qualified activity and CRM outcomes can be returned to Surface for attribution, analysis, and closed-loop learning. Compare capabilities ## Capability comparison Capability Qualified Surface Website engagement Real-time AI conversations: text, voice, video, offers, qualification, meetings Adaptive inbound journeys: forms, capture, qualification, next steps Email engagement Piper sends and answers contextual inbound email, including nurture Governed campaign and follow-up workflows; not a like-for-like autonomous AI SDR inbox CRM context Deep native Salesforce connectivity; Piper for HubSpot uses HubSpot context Decision layer alongside HubSpot or Salesforce; the CRM stays the system of record Partial-response capture Reviewed materials describe form-triggered follow-up; confirm abandoned-form handling Permissioned capture of information collected before a multi-step form is completed Account research Connected GTM data, enrichment, intent, and a trained content knowledge base Agents answer approved account questions from sourced material, evidence attached Content campaigns Piper serves personalized offers and runs configured nurture campaigns Human-reviewed campaign plans and assets from qualified-buyer patterns Closed-loop qualified-buyer learning Qualified says Piper feedback modifies behavior toward pipeline goals Sales acceptance, opportunity, and revenue outcomes improve future decisions Intelligent Attribution Analytics support the pipeline motion; confirm attribution models and journey coverage Source-to-revenue journey connected, with assumptions and confidence visible Qualified capabilities above were checked against Qualified's official product materials on July 15, 2026. Packaging and availability can change; confirm current requirements with each vendor. ## Where Qualified is a strong fit Qualified has built Piper around the work of an inbound SDR. Agent Studio gives teams ways to onboard, train, guide, evaluate, and coach the agent. Salesforce remains a core strength in Qualified's positioning, with native infrastructure on Salesforce, and Qualified introduced Piper for HubSpot in September 2025. If the buying requirement reads “give every inbound buyer a responsive AI SDR across web and email,” Qualified deserves a direct evaluation. ## Where Surface extends the operating context Surface treats a meeting as one stage in the journey. Evidence chain from an inbound signal through cited research and qualification, engagement through sales outcome, to attribution and the next approved content campaign, looping back to capture. 01 Inbound signalComplete or eligible partial response. 02 Research and qualificationSources, unknowns, and the evidence behind the decision stay visible. 03 Engagement to sales outcomePiper or Surface takes the next step; acceptance or a rejection reason is recorded. 04 Attribution and next campaignMethod and confidence shown; new campaigns proposed from qualified-buyer patterns. Human reviewgate ## A practical coexistence architecture - Surface enriches, researches, and qualifies Preserve the evidence and approved fields that the next experience needs. - Surface closes the broader loop Use CRM outcomes and campaign history to evaluate qualified pipeline, attribution, and the next campaign. ## Questions to ask in a live evaluation Run the same buyers through both vendors and compare the replay, not the summary. - Can useful, consented intent be captured before final form completion? - How does website context carry into email and back again? - What prevents duplicate qualification, outreach, or booking when multiple systems coexist? - Which downstream outcomes change future agent, routing, or campaign behavior? - Which features require a specific CRM, plan, service, or implementation package? Set up once ## Evaluate the complete journey, not only the conversation [Book a Surface demo](https://www.withsurface.com/book-a-demo) --- # What is Surface? | Marketing Superintelligence URL: https://surface.thesurface.network/what-is-surface What is Surface? ## An intelligent marketing system that learns from revenue. ## Leads, Context, and Agents Together, they let Surface build almost any campaign at lightning speed, then learn from the result and improve the next one. ## What's included ### [Inbound Capture](https://www.withsurface.com/solutions/increase-inbound-conversion) - Traffic intelligence - Dynamic lead forms - Partial-response capture - Qualification and routing - Unlimited sales scheduling - CRM and MAP sync ### [Lead Intelligence](https://www.withsurface.com/platform/lead-data-layer) - Unified lead data layer - Real-time enrichment - Buyer research agents - AI lead scoring - Segments and audiences - Evidence-backed qualification ### [Marketing Operations](https://www.withsurface.com/for/marketing-operations) - Vault marketing context - System agents - Visual workflow builder - Agentic CMS - Permissions and governance - Revenue feedback signals ### [Campaign Engineering](https://www.withsurface.com/platform/content-campaigns) - Content campaign agents - SEO and AEO workflows - AI visibility monitoring - Reusable campaign templates - Multi-channel execution - Closed-loop optimization ## FAQ Who is this for? Surface is for B2B revenue teams that want to create more pipeline without adding disconnected tools or headcount. It gives founders, growth and demand generation teams, content and paid media teams, GTM engineers, and sales leaders one system for buyer intelligence, campaign execution, conversion, and revenue feedback. Can't we already do this in our CRM? Your CRM stores form data, ownership, and outcomes. Surface enriches the signals around those records, qualifies buyers with evidence, routes the right next step, and feeds the result back into the CRM. It acts on the data without replacing the system of record. How is Surface different from marketing automation? Traditional automation follows predefined branches using the fields it already has. Surface agents can research missing context, make evidence-backed decisions inside your rules, and coordinate campaigns, lead workflows, routing, and measurement across the stack. Does Surface replace our existing marketing stack? No. Surface connects to the systems your team already uses, including your website, CRM, scheduling, enrichment, analytics, and publishing tools. Your existing records, permissions, and ownership rules remain in place. Why not just run campaigns from Claude? Claude can help you think, research, and create inside a conversation. Surface gives that work the connected operating layer it needs to run in production: live buyer and revenue context, governed workflows, permissions, publishing, attribution, and feedback from every result. You can still work from Claude through Surface MCP, while Surface executes across your stack and preserves the context for the next campaign. Where should we start? Start with one measurable workflow, such as improving inbound conversion, qualifying and routing leads, or launching content faster. Once that workflow is producing results, Surface can expand across the rest of the marketing system. [Book a demo](https://www.withsurface.com/book-a-demo) Set up once ## Live in an afternoon. Then it runs. [See how it works](https://www.withsurface.com/mcp)