How Finout builds an inbound engine to turn demand into pipeline

Give every inbound signal a path to qualification.

Yifat Marcus started with a marketing challenge: turn the demand Finout was already creating into conversations sales could act on. She built the first skills and triggers in Swan; Brian Hernandez and the sellers extended that foundation into a shared inbound engine.

• Make marketing demand actionable. Website signals reveal interested accounts, including visitors who never fill out a form, and connect them to the right rep.
• Connect visibility to faster follow-up. Marketing can see the messages and responses, while shared context and automated workflows help sales act while interest is fresh.
• Give the whole team a shared starting point. Reps adapt each other’s plays, and new hires inherit the knowledge and skills already built into Swan.

Interest needs a clear path from marketing to sales.

Conferences, SEO, and paid campaigns were bringing relevant buyers to Finout. Yifat’s concern was the interest that sales could not see: people visited the website but left without a form fill. Marketing needed a way to identify those accounts, reach the right owner, and see what happened next.

Even when someone did fill out a form, follow-up took time. Brian measured a seven-hour median from submission to enrollment in an outreach campaign, with weekend submissions pushing the average to roughly three days. The team needed both visibility into demand and a faster way to act on it.

A GTM brain connects inbound context to the next sales action.

Yifat built Finout’s initial website-visitor skills and triggers. Swan classified the activity into high intent, low intent, competitors, partners, and customers, then used HubSpot ownership to bring the relevant account to its AE in Slack. Marketing could see which messages went out, who replied, and where follow-up stood.

Brian extended the engine with enrichment, scoring, and contextual messages sent on behalf of reps. Swan’s context and orchestration platform connects those workflows to the same account history and reusable skills. The people responsible for the next conversation can see why the account matters and decide how to act.

As sellers adopted Swan, they began creating their own territory monitors and plays. Yifat described AEs becoming more active users than she was; Brian described colleagues copying successful skills into their own territories. What began as a marketing initiative became GTM infrastructure the wider team could build on.

Systems, agents, and humans working together

• Systems Inbound forms, website signals, CRM account history, Slack, and Salesforce campaign tags connect the work from first interest to follow-up.
• Agents Swan enriches and scores accounts, prepares contextual messages, and sends follow-up through the configured workflows on behalf of reps.
• Humans Yifat shapes the marketing plays and visibility; Brian extends the automation and context. Reps adapt their own skills, review where needed, and handle qualification and customer conversations.

Marketing, sales, and RevOps build on the same GTM brain.

At Finout, 40 people across marketing, sales, GTM engineering, and RevOps have used Swan. Each team brings its own work into the same GTM brain, drawing on shared account history, signals, and playbooks.

Marketing & GTM engineering

Yifat built the initial inbound skills and triggers. Brian extends them with enrichment, scoring, and automated follow-up. Both build plays for colleagues as well as for themselves.

Sellers & sales leadership

AEs create territory discovery, hiring-signal, and closed-lost plays. The Head of EMEA Sales builds her own monitors and battlecards. Reps review the output and use it in outreach.

Marketing leadership

The VP Marketing asks who owns an account, whether a target company visited, and how leads are being routed. He also builds signal digests for sales.

RevOps & marketing operations

Attribution, routing, and outreach logging become shared skills that other people’s plays can call. An improvement to the shared foundation carries into the team’s work.

One improvement, shared across the team.

Finout’s knowledge becomes part of how the team executes. Shared skills capture how to research accounts, qualify signals, and prepare outreach. When someone improves a shared skill, the workflows using it benefit, giving colleagues a better starting point for their own work.

A more direct route from inbound interest to pipeline.

Yifat’s story starts with making marketing’s work visible and actionable: identify the accounts showing interest, connect them to the right rep, and see the follow-up through. Brian’s results show that engine becoming part of daily execution, with five-minute inbound form follow-up and pricing-form conversion rising from roughly 15% to roughly 35%.

The shared foundation serves 40 people across marketing, sales, GTM engineering, and RevOps. Reps build on each other’s skills, and new hires can begin working their territory in about a week. Brian described one SDR having the impact of a team of five.

Finout reports more than 50% of its pipeline influenced by Swan. Across both conversations, the common thread is how the team works together: marketing brings the demand and visibility, GTM engineering extends the system, and sellers act on shared context.

Results context

Based on separate conversations with Yifat Marcus and Brian Hernandez. The five-minute result covers inbound form follow-up; the seven-hour baseline measured submission to campaign enrollment. Pricing-form conversion is approximate. Pipeline influence and SDR capacity are customer-reported. The one-week onboarding milestone refers to working a territory confidently; the campaign-build comparison describes earlier work in Clay versus Brian’s current process with Swan.