# Marcus Okafor, Director of BD at LexAlign (legal workflow SaaS, ~55 employees) — read of Law Firm Lateral Hire Signal Feed, June 11, 2026

> 9 years selling into BigLaw and mid-market firms, used to run a legal staffing desk before jumping to tech. Coaches his daughter's U10 soccer team Saturday mornings, which means I am always behind on email by Sunday.

## How I got here

Someone in my LinkedIn network shared a post that said something like "found a product idea marketplace that actually shows negative revenue projections." That phrase stuck with me because every pitch deck I see projects hockey sticks. Went looking, ended up here. Spent maybe 12 minutes on the page before writing this.

## What I clicked first

The hero line "Track Partner Moves Before Incumbents Notice" got my attention because that is a real problem I have. When a partner moves firms, there is a 3-6 week window where everyone is scrambling and the new relationship is not locked yet. We have tried to catch these with Google Alerts and LinkedIn and it is sloppy. So the premise landed.

Then I saw "Zero false positives" and my eyes rolled a little. That is a claim with no mechanism attached to it. How? What counts as a false positive? A name match? A firm match? An announcement that turned out to be a rumor? I kept reading but that phrase flagged for me.

## Where I paused

"New partners are greenest in their first month. Capture the moment before competing vendors and incumbent relationships take root." That sentence I actually read twice. Not because it is fancy writing, it is not. But because it is accurate in a way that most lateral hire tools I have seen completely ignore. Everyone knows the signal. Almost no one has operationalized the timing window around it. That paragraph is the product's best argument for itself and it is buried mid-page.

The self-scoring section also stopped me. Seeing "$-10,000 Year-1 take-home (Fermi)" and "1 in 8 Meaningful-success odds" on a product's own homepage is either the most refreshing thing I have seen in a while or a hedge because the idea does not actually work. I genuinely cannot tell which yet.

## What I distrusted

"Sourced from NALP filings, bar admissions, and firm announcements." Okay, but NALP data is often months behind. Bar admission transfers are public record but the lag varies by state. "Firm announcements" is doing a lot of work in that sentence. Does that mean press releases? LinkedIn posts? Manually scraped firm websites? This is the core data question and the page does not answer it.

"Ready-to-call data" is exactly the kind of phrase that sounds like it means something but does not. Ready to call compared to what? My current cobbled-together process is also technically ready to call, it just takes 45 minutes per lead.

Also: the page scored itself "landing page quality: 2/10." That is self-aware in an interesting way but it also means I am making a $99 decision based on a page they admit is bad. That is a real thing to sit with.

## What would convince me

I want to see a sample feed. Not a description of what is in the feed, an actual sample. Give me 5 rows, redacted if needed, showing what a lateral event looks like in the data. Show me the bar ID field, show me what "corporate firm contact" means in practice (is it a name and email, or just a job title). That alone would tell me whether the data is actually ready-to-call or whether I would spend the same 45 minutes per lead I spend now.

I also want to know the publication lag. If a partner announces a move on Monday, when does it appear in the feed? If the answer is "within 48 hours" that is a product. If the answer is "within 3 weeks" that is a newsletter.

## What I'd ask in an email reply

1. What is the actual average lag between a partner move happening and it showing up in the feed? Not the best-case lag, the median.

2. When you say "zero false positives," what is the validation step? Is a human reviewing each record, or is this a rule-based filter that excludes certain edge cases?

3. The multi-tenant API angle is the part I am most interested in because we already have a customer base. What does the API response schema look like, and is there a sandbox I can test against before committing?

## Verdict: on-the-fence

The premise is real and the timing insight is sharper than most of what I have seen in this space. But I need one concrete proof of the data quality before I spend $99, and this page does not give it to me. A two-row sample CSV would probably close me.

---
*Memo by skeptic persona, generated 2026-06-11. Studio breaks own self-grading loop.*