No. If you already run Clay, we build inside your environment. If you do not, we operate from our own instance during the pilot, and if the work continues, you would add Clay internally while we keep managing the engine for you. Clay licenses for firms start around $500 a month, and the supporting tooling a growth leader might need generally runs $150 to $300 a month.

Not necessarily, but the published bands start at ten people and $2M, so there is no table for you to read. Below that size the economics turn on your deal value and how many pursuits you run rather than on headcount, which makes it a conversation rather than a tier. A right-sized version is being reworked. Ask, and we will tell you straight whether it pays for itself at your numbers.

Yes. The firm-size bands run up through two hundred people and beyond. At that scale the problem is usually fragmented signal and tool sprawl rather than missing infrastructure, so the engagement often starts by taking stock of what you already have before adding anything.

The build runs four to six weeks: discovery, your signal taxonomy, calibration to your firm, and the first call-down sheets and dossiers in your people's hands. Conversations follow closely, as your people begin outreach against the engine's outputs. A measurable pipeline takes longer, typically four to six months, but the activity in the relationship pipeline should feel measurably different before that. This is a relationship game, and only about five percent of your future clients are in market in any given quarter. The engine puts your people in front of the right ones earlier and more often. It does not manufacture demand that is not there yet.

Yes, and that is often how it starts. The pilot covers a scoped set, usually a single practice, region, or office. The scoring model is designed to extend across the rest of the firm once proven.

Discovery takes three to four hours of growth or practice leadership time across one or two sessions. After that, we run the build. Weekly check-ins and occasional ad-hoc calls provide an opportunity for review of progress and adjustments to tune the engine and confirm where the output should land.

No, it layers on top and, depending on your tech stack, can orchestrate and optimize the value of your existing systems. The engine works with the CRM, the enrichment vendors, and the outreach tools you already run. Sometimes the pilot surfaces a tool that is adding cost without adding signal, and that becomes a candidate to consolidate. We make your stack more effective. We do not displace it.

Data platforms sell category-level data, the same feed to every firm in your space, so your competitor is working the same list. What we build is calibrated to your firm: the specific accounts, people, and triggers that actually predict work in your market, drawn from discovery with your team. A competitor cannot buy it from a vendor.

You can, and a capable operator can stand up a basic workflow. The hard part is the intelligence layer: the signal taxonomy, the enrichment architecture, the scoring, the calibration, and the ongoing tuning against real outcomes as the market shifts. Your practitioners are excellent at their craft and should not have to become data engineers to get in front of the right client. We do this work every day across firms, which is why our builds compress to weeks.

It is specific to your firm, set during discovery, and can adjust over time and based on learnings. Common ones for professional services: leadership transitions and new mandates, mergers, recapitalizations, and reorganizations, regulatory and market shifts in your sector, and renewal, expansion, and re-bid windows. The point is timing, reaching the right person when something has actually changed that warrants assessment and action.

The What We Do section on this site shows real examples: a weekly call-down sheet and a full contact and account dossier. We are happy to walk you through additional examples upon request.

Managed service means we run the engine with no set endpoint. Transition to internal means we run it first, then progressively hand execution to your team as their capability and capacity ensure no service disruptions. It is measured against readiness, not a calendar date. Both are fully supported. Indicate your preference or intent in scoping or during the engagement, and we build that into our approach and expectations.

No. Your relationships stay entirely yours, and so does every outreach. We work the intelligence in the background and tee up the right person, the right context, and the warm path. Any outreach content we generate includes a human in the loop at two stages: when we create it, and before we hand it to you. Then you have final edit before it is sent out, by you or your own outreach tools. You stay the only face, name, and voice the client ever sees.

No, it is the opposite. Nothing goes out on a spray-and-pray basis. Every touch is tied to a real trigger and a genuine reason to reach that person now, and your people, not an automation, decide to send it. The goal is fewer, sharper, warmer conversations, not more noise.

No. We manage the intelligence and hand your people a ready-to-use starting point. They own the outreach and the relationship. If you want help drafting sequences in your own voice and tone, we can do that, but the send and the relationship stay with your people. That line does not move.

Clay holds the commercial agreements with the data providers in its network, so sourcing compliance is handled at the platform level. When we work in your Clay environment, your data stays under your terms. When we run our own instance, your data is segregated, access is limited to your engagement team, and handling is documented in the agreement. At close, it is migrated to you or deleted, your call.

Discovery needs shared context on your best clients and your history. Connecting to your CRM so the output routes correctly is a standard API setup done with your ops lead. We do not hold your CRM records separately, and the handling is documented in the engagement terms.

If the engine was built in your Clay instance, it is yours, no migration needed. If we used ours, the full architecture is documented and we support the move to your environment. The taxonomy, the calibration, and the scoring logic are documented and transferable either way.

That is exactly what the transition-to-internal path is for. We build and run the engine, document the architecture as we go, train your team, and hand over operation as their capability grows. Name it as a priority in scoping and the engagement is structured around it.

Two things. First, the craft: Redline is a Clay Advanced Artisan Partner, and the signal detection, enrichment, and AI context work runs at scale every day. Second, and the part that matters most here, this is built by people who spent decades in relationship-led selling inside professional services firms, the same doer-seller motion you run. We know the work because we have done it. For a walkthrough of experience and output relevant to your firm, reach out, or view our leadership team page on redlinegrowth.com, where we also have our LinkedIn profiles linked.