# Marcus Ohlsson, VP of IT at Fieldpoint (270-person B2B logistics SaaS) — read of Enterprise Knowledge AI, 2026-05-19

> 14 years in IT, currently managing a Frankenstein stack across three acquired companies. Commute is 42 minutes each way on the Caltrain, which is basically my reading time. I have a 9-year-old who thinks I work "at computers."

## How I got here

A junior engineer pinged me Tuesday asking where the incident runbook for our Salesforce integration lived. I knew it existed. I had written half of it. It was somewhere in Notion or maybe an old Confluence space from the Meridian acquisition. I couldn't find it in 10 minutes so I Googled "AI enterprise knowledge search Slack Confluence" and this page was third result. I did not click an ad. I was not in a buying mood. I was annoyed.

## What I clicked first

The hero line got me: "Three hours per employee, every week, lost searching for what someone wrote." That number is either fabricated or it's from a McKinsey slide that gets quoted in every SaaS deck without attribution. But it felt close enough to true that I kept reading. The line "Ask a plain English question instead of pinging five people" is exactly the Tuesday afternoon I just had. So I stayed.

The "Under 48 hours Time to live" and "7 days, no contract Pilot terms" made me sit up a little. That's specific. Most vendors bury the pilot terms in a sales call.

## Where I paused

The comparison table. They put themselves against Confluence, Guru, and Notion AI and said "We are pre-revenue. We are also the only one of the four indexing Slack threads as a first-class source." Pre-revenue disclosed IN the table, not buried in a footnote. That's not a thing I see. I read it twice because I thought I was misreading it. Then I started scrolling faster to understand what this company actually is.

## What I distrusted

This is where it fell apart for me. The further I scrolled the more the page started feeling like two different documents stitched together. The top half reads like a real enterprise software pitch. The bottom half is a different product entirely.

"Honest disclosure: we don't have live customers on this idea yet. We shipped the strategy package; you ship the customer conversations."

And then: "Browse Free. Unlock for $5. Adopt for $99."

And this: "1 in 17 Meaningful-success odds (Fermi)."

So this isn't a product I can pilot. This is a startup idea for sale. I scrolled back up to the "Start the pilot" button feeling like an idiot for not catching it sooner. The page leads with enterprise IT language, SOC 2 talk, SSO/SAML, data residency, all of it, and you're 70% through before you realize you're on a marketplace that's selling you the recipe, not the food.

The "$-118,520 Year-1 take-home (Fermi)" is a negative number. The product they're selling me costs more to build than it returns in year one by their own Fermi estimate, and they're pitching it to me as a business opportunity. That's not dishonest exactly but it is a very weird pitch to aim at a VP of IT who came here to solve a Slack problem.

## What would convince me

If this is a real enterprise search product looking for early design partners: one 3-minute video of someone at a real company running a real query against their actual Slack and getting a sourced answer I could verify. Not a demo environment. Not a "John at a 300-person company" quote with no last name or logo. Show me a permission-aware query where one user gets a result and another doesn't because of ACLs. That would get my attention.

If this is the idea marketplace product it appears to actually be: I am not the customer. You want someone who wants to build an enterprise SaaS. I want to BUY one.

## What I'd ask in an email reply

Actually, I would not send an email because by the time I hit the $5 / $99 pricing section I understood I was not looking at a vendor. But if I had misread the page and thought this was real:

1. SOC 2 Type II "in flight" means what, exactly? What stage is the audit at and what's the realistic timeline to attestation? Because my security team will kill this in procurement if you can't give me a date.

2. How does the permission sync work when someone's Notion permissions change mid-week? Is the index stale for 24 hours? 5 minutes? That's the gap where you expose the CFO's comp doc to an IC.

3. You say "direct Slack channel with the founding team, average response under 90 minutes." How many accounts are you running right now and what happens to that SLA when you have 20?

## Verdict: dismissive

Not because the idea is bad. The top half of this page is well-written and the Slack-native indexing angle is genuinely differentiating. But I came here to solve a real problem and the page is selling blueprint documents for $99 to people who want to build this business. Those are two completely different buyers and the page tries to speak to both at once and ends up losing me as either one.

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