TreasureMap by Buried Wins — Benchmark Transcript #1
Deal Status: Closed Won
Contact: Sarah Chen, Director of Operations
Contact Company: Ridgeline Manufacturing
Interview Date: February 12, 2026

---

Buried Wins Moderator (00:00:12 - 00:00:18)
Hi Sarah, thanks for taking time today. How are you?

Sarah Chen (00:00:18 - 00:00:22)
Good, thanks. Happy to be here.

Buried Wins Moderator (00:00:22 - 00:00:38)
Great. Just to set context, we're doing research to understand how teams evaluate project management tools. Everything is anonymized and compiled with other interviews. Do I have your permission to record?

Sarah Chen (00:00:38 - 00:00:40)
Yes, absolutely.

Buried Wins Moderator (00:00:42 - 00:00:48)
Perfect. Can you start by telling me a bit about your role and what your team looks like?

Sarah Chen (00:00:50 - 00:01:32)
Sure. I'm Director of Operations at Ridgeline Manufacturing. We make industrial components — about 400 employees, spread across three facilities. My team is 12 people and we coordinate cross-functional projects between engineering, production, and sales. Before this evaluation we were managing everything in spreadsheets and email threads. It was a mess honestly. We'd lose track of dependencies, miss handoffs, and nobody had a clear picture of where things stood.

Buried Wins Moderator (00:01:34 - 00:01:40)
What prompted you to start looking at project management software?

Sarah Chen (00:01:42 - 00:02:28)
We had a product launch last spring that went sideways. Not because of the engineering or the product itself, but because three different teams were working off different timelines. Sales had committed to a date that production didn't know about. Engineering made a design change that nobody downstream was tracking. It cost us about six weeks of delay and a lot of credibility with a key customer. After that, leadership said okay, we need a real system. I was tasked with finding something that could give us visibility across teams without requiring everyone to become a project management expert.

Buried Wins Moderator (00:02:30 - 00:02:36)
Got it. Walk me through which solutions you evaluated.

Sarah Chen (00:02:38 - 00:03:45)
We looked at four options seriously. ProjectCommand was the first one our IT team suggested because they'd seen it at a previous company. It's the big enterprise player — very feature-rich, handles complex portfolios. We also looked at QuickPlan, which a couple of my team members had used at startups. It's more lightweight, really fast to get going. Then someone on the engineering side brought up Nexus PM because they liked the technical integration capabilities. And then TreasureMap came through a recommendation from another operations director I know in the industry.

Buried Wins Moderator (00:03:47 - 00:03:54)
Can you tell me about your first impressions of each? Starting with ProjectCommand.

Sarah Chen (00:03:56 - 00:04:52)
ProjectCommand was impressive on paper. The demo was polished, they had every feature you could imagine — resource leveling, portfolio dashboards, Gantt charts with fifty different configuration options. But honestly it felt overwhelming. My team isn't project managers by trade, they're operations people. When I asked the sales rep how long implementation typically takes, he said eight to twelve weeks with a dedicated admin. That was a red flag for us. We needed something that people would actually open on Monday morning without dreading it. The pricing was also significantly higher — they wanted a three-year commitment and the per-seat cost was almost double what everyone else was quoting.

Buried Wins Moderator (00:04:54 - 00:05:00)
What about QuickPlan?

Sarah Chen (00:05:02 - 00:05:58)
QuickPlan was the opposite experience. We signed up and had boards running within an hour. The interface is clean, really intuitive. My team loved how simple it was to drag tasks around and see what's in progress. But as we got deeper into the trial, we started hitting walls. The reporting was basically nonexistent — you could see a board but you couldn't roll things up across projects. There was no real way to handle dependencies between teams. And when we reached out to their support team with questions about scaling it for our use case, we got canned responses that didn't address what we were asking. It felt like a tool built for a five-person startup, not a 400-person company.

Buried Wins Moderator (00:06:00 - 00:06:06)
And Nexus PM?

Sarah Chen (00:06:08 - 00:07:12)
Nexus was interesting. The engineering team liked it because it has strong integrations with development tools — connects to code repositories, has sprint planning built in. The API documentation was thorough and our developer who evaluated it said the technical foundations were solid. But for the rest of us it felt like a tool built by engineers for engineers. The interface was dense, lots of terminology that my operations and sales stakeholders wouldn't understand. Their onboarding process was self-serve — here's the docs, figure it out. When I asked about training for non-technical users, the response was basically that most of their customers handle that internally. Support was responsive when we had technical questions but they didn't seem to understand our use case as a cross-functional operations team.

Buried Wins Moderator (00:07:14 - 00:07:20)
And then TreasureMap. How did that evaluation go?

Sarah Chen (00:07:22 - 00:08:35)
TreasureMap felt different from the first call. The person we talked to actually asked about our team structure and our workflows before showing us features. They understood that we weren't a software company trying to manage sprints — we were an operations team trying to coordinate across departments. The setup was straightforward. We had a working workspace within a few days, not weeks. It wasn't as instant as QuickPlan but it also wasn't the twelve-week odyssey that ProjectCommand was describing. The interface struck a good balance — it had the depth we needed for cross-project dependencies and reporting, but it didn't overwhelm you with options you'd never use. My team actually started using it during the trial without me having to push them, which never happens.

Buried Wins Moderator (00:08:37 - 00:08:44)
What about the documentation and resources? How did TreasureMap compare there?

Sarah Chen (00:08:46 - 00:09:28)
The documentation was solid. Not as deep as Nexus PM's technical docs, but way more practical. They had guides written for different roles — here's how an operations lead uses this, here's how a sales team tracks handoffs. That was huge for us because I needed to get buy-in from people who weren't going to read API documentation. They also had a sandbox environment where we could test things without worrying about breaking our real workspace. QuickPlan had nothing like that. ProjectCommand had documentation but it assumed you had a certified admin interpreting it for you.

Buried Wins Moderator (00:09:30 - 00:09:38)
How did pricing factor into the decision?

Sarah Chen (00:09:40 - 00:10:22)
Pricing was a factor but not the deciding one. TreasureMap was in the middle — less than ProjectCommand by a significant margin, a bit more than QuickPlan but not dramatically. What mattered more was that TreasureMap's pricing was transparent and scaled with us. Per seat, monthly, no long-term lock-in required. ProjectCommand wanted that three-year contract. QuickPlan was cheap but we'd need to upgrade to their enterprise tier for the features we actually needed, which brought the price close to TreasureMap anyway. Nexus PM was comparable in price to TreasureMap but we felt like we'd be paying for technical depth we'd never fully use.

Buried Wins Moderator (00:10:24 - 00:10:32)
What was the deciding factor in going with TreasureMap?

Sarah Chen (00:10:34 - 00:11:18)
Honestly it was adoption. The tool only works if people use it. ProjectCommand was too heavy — my team would've revolted. QuickPlan was too light — we'd outgrow it in months. Nexus PM was too technical for half our users. TreasureMap hit the sweet spot where my operations people, the engineers, and even the sales team leads could all work in it without constant hand-holding. The support team also gave me confidence. When we had questions during the trial, we got a real person who understood our setup and gave us specific answers. That's not something you can fake.

Buried Wins Moderator (00:11:20 - 00:11:28)
Is there anything TreasureMap could improve?

Sarah Chen (00:11:30 - 00:12:05)
The mobile app is a bit behind. Some of my team works from the production floor and they need to update statuses from their phone. It works, but it's not as smooth as the desktop experience. And I'd love to see better integration with our ERP system — right now we export data manually for some of the manufacturing workflows. But those are nice-to-haves. The core experience is strong enough that we renewed before the trial even ended.

Buried Wins Moderator (00:12:07 - 00:12:12)
Great. Thanks so much for your time, Sarah. Really helpful.

Sarah Chen (00:12:12 - 00:12:14)
Happy to help. Thanks.