# Marcus Telles, VP Sales Operations at Fieldrock (123-person B2B SaaS) — read of territory-workload-balancer-ai, May 22 2026

> 14 years in sales ops, the last 4 managing territory design for field and inside sales teams simultaneously. I have the spreadsheet I built in 2019 that still runs our quarterly rebalances. It's 1,400 rows. I hate it.

## How I got here

Someone in a RevOps Slack shared a link with the comment "someone finally built this." I clicked because territory planning is genuinely one of my most political, most hated quarterly tasks, and I'm always one deck.new() away from trying something. I was on my phone, waiting for my son's lacrosse practice to wrap. I gave the page maybe 4 minutes.

## What I clicked first

"Territory assignment should be data-driven, transparent, and automatic. Instead, it's political, ad-hoc, and broken."

That line hit. Specifically "political." That word earns a click because nobody ever writes it. Everyone says "manual" or "time-consuming." Political is the real word. Territory fights are about comp plan math and ego, and this page names that, which made me trust it for about 90 seconds.

## Where I paused

The honest disclosure section at the bottom. Specifically this: "we don't have live customers on this idea yet. We shipped the strategy package; you ship the customer conversations."

I had to read that three times. So this is not software. This is a strategy dossier for someone who wants to BUILD this software. I had been reading the whole page thinking I could buy a product. The pricing tiers above ("$199, up to 10 reps, monthly snapshot assignments") are describing what the HYPOTHETICAL product would charge, not what I'd pay today. And then below that there's a completely different pricing structure for unlocking a $5 PDF or a $99 code starter.

That is a confusing page. I do not think most people who land here understand what they are actually being sold until that bottom section.

## What I distrusted

The statistics have no provenance. "Disputes over territory assignments drop 80%." Says who? "Territory design that took 3 weeks now takes 3 hours." One customer? Backtesting? The founder's own experience? "Ramp time is 3 weeks faster." This one especially, because ramp time is downstream of like six other variables.

These numbers are written with the confidence of a case study that doesn't exist yet. The disclosure at the bottom admits there are no live customers. So where did 80% come from?

Also: the feature list reads like a product requirements doc, not a product page. "Role-based access (only managers see sensitive data)" is a checkbox, not a benefit. That line is there for completeness, not persuasion.

## What would convince me

If this were a real software product: one real customer quote from a VP Sales Ops or CRO at a 50-200 person SaaS shop saying specifically what changed after a quarter rebalance. Not a logo. Not "Company X saw 3x efficiency." A name, a title, a before/after that maps to something I recognize.

If this is what it actually is (an idea dossier): I'd want to see what the MVP scope actually recommends and whether it's realistic. The "speed to MVP: 3/10" score on the page is a red flag I'd want explained before paying even $5. That score is doing a lot of work in two characters.

## What I'd ask in an email reply

1. The 80% reduction in territory disputes: where does that number come from? Is that modeled, estimated, or observed somewhere?
2. The page sells two different things and I got confused about which one I was reading. Is there a version of this that's a live SaaS product I can use today, or is this purely a build-it-yourself kit?
3. What does "constraints are learned from your team's history" actually mean in the algorithm step? That's the only sentence in the How It Works section that feels like it's hiding something.

## Verdict: on-the-fence

The pain identification is genuinely good and the page earns early trust by using the word "political." But the structure confused me badly enough that I didn't know what I was being asked to buy until the very bottom, and the unattributed statistics undercut the credibility the honest disclosure tried to build back.

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