# Rachel Sondergaard, Head of RevOps at Fieldline Health (Series B, ~90 people) — read of deal-velocity-optimizer, May 29 2026

> 11 years in sales ops, currently managing our Salesforce instance plus Gong plus a Clari pilot that's honestly underwhelming. Three reps are chronically sandbagging Q-end and I've been trying to automate the nagging.

## How I got here

Someone in my RevOps Slack community reposted a tweet that just said "negative projected year-1 income and they published it anyway, respect" with a link. That's the hook. I was not searching for a new tool. I clicked because I wanted to see what kind of company posts its own failure odds. I assumed it would be a landing page for a consultant or a ghost-written substack post. It was neither.

## What I clicked first

"Close deals 40% faster by surfacing stuck deals before they die" is the hero claim. The "40% faster" number is the kind of thing I see on every Clari competitor page and my eyes usually skip it. I kept reading because the Fermi stuff below it was weirder and more specific than a normal SaaS page. I also immediately noticed the live demo UI swap showing "Before" and "With Deal Velocity Optimizer" which I wanted to interact with but couldn't tell if it was real or a static image.

## Where I paused

The Fermi section. "$-28,000 Year-1 take-home." Negative. They bolded a negative number. That stopped me completely. Then "1 in 9 Meaningful-success odds." That is not how any startup pitches anything. I read it twice to make sure I hadn't misread the sign. Once I absorbed that this was intentional, I had to recalibrate what I was even looking at. This is not a tool for me to use. This is a business-in-a-box kit you buy and then go build and sell yourself. That realization came slowly. It was not immediately obvious from the top of the page.

## What I distrusted

Two things.

First, "Close deals 40% faster" is floating without any anchor. Faster than what baseline? 40% is a round number that marketers like. The rest of the page is full of specific, honest-sounding numbers, which makes the 40% stand out more, not less. It reads like they forgot to strip out the template claim when they were writing the rest of the honest copy.

Second, the scoring axes. "Pain intensity: 10/10. Buyer clarity: 10/10. Credibility: 10/10." All three strongest axes are a perfect 10. That pattern is what I'd call a self-grading problem. The weakest axes are the ones that actually tell me something: financial upside 3/10, market openness 5/10. Those scores made me more confident in the page than the 10s did. But three 10/10s in a row from the company grading its own idea does make me raise an eyebrow.

Also I still am not 100% sure what the $5 unlocks versus $99 versus "operator partnership." The pricing tiers are on the page but I had to read them a few times to understand I was not buying software. I was buying a plan to build software. That distinction should be more upfront.

## What would convince me

A single case study from one person who bought the $99 kit and shipped something. Not revenue numbers, not testimonials about the dossier quality. I want to see: person X, former role, bought the build kit, here is what they shipped in 90 days, here is whether the pain-intensity-10/10 claim held up when they started selling. Even if they failed. Especially if they failed. The honest framing suggests the studio can handle publishing a mixed result.

Also a 2-minute video of the actual product working in a real Salesforce or HubSpot environment. The "30-second explainer" link is above the fold but I didn't click it because I've learned those are usually animated slideshows with upbeat music.

## What I'd ask in an email reply

1. The $-28,000 Year-1 estimate: is that the builder's take-home after cost of acquisition, or the end-customer's ROI, or something else entirely? The sign confuses me because I can't tell if this is what I'd earn building it or what a buyer loses running it.

2. "We shipped the strategy package; you ship the customer conversations." That's a clean disclaimer but it also describes every business school professor. What specifically have people done wrong or right with previous kits you've sold? What's the most common mistake someone makes in week 2?

3. Is the "working code starter" in the $99-199 tier actual deployed code with auth and a data model, or is it a repo with a README and some scaffolding? I've bought "code starters" before that were 40 files of boilerplate and a Stripe integration that didn't work.

## Verdict: on-the-fence

The transparency is real and it bought goodwill. The negative year-1 number and the honest-disclosure callout are genuinely unusual and I'd rather read ten pages like this than one page that says "join 10,000 happy customers." But I still don't know if I'm a buyer here because I'm not sure if the product this page describes is one I'd use or one I'd build, and that confusion alone is worth flagging to whoever wrote the copy.

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