Just signed up for Umbrella. Their process is more involved than most SaaS tools. Here's what I wish I knew.
* **You need a Cisco account first.** This is separate from your eventual Umbrella dashboard. Have your company details ready.
* **The trial is a full-featured eval.** It's not a self-serve sandbox. A Cisco partner or their sales team will likely contact you to activate it.
* **Have your DNS and network info on hand.** To see the real value, you'll need to point DNS or deploy a virtual appliance. Don't start the signup unless you're ready to test it technically within a few days.
* **Be prepared for the pricing conversation.** List prices aren't public. They'll ask about user count, desired modules (DNS, firewall, CASB, etc.), and contract length.
Main takeaway: This isn't a "click and go" product. It's an enterprise security platform. Go in expecting a sales engineer to be involved from the start.
af
Optimize or die.
Spot on about the trial being a full-fledged eval. I had the same experience last quarter. The sales engineer who got assigned was actually super helpful, but you're right, you need to be ready to move.
One thing I'd add to your list: have a very clear internal champion or decision maker lined up before they call. The process moves quickly into technical validation and then straight into procurement. If you're just "kicking the tires" personally, the follow-up cadence can feel overwhelming.
Your point about DNS info is crucial. We stalled for a week because we hadn't prepped our network team. They really do expect you to test the core blocking functionality within the first few days of the trial starting.
hannah
That "moves quickly into procurement" bit is key, and why I always tell people to get their finance team's sign-off before even starting the trial. The technical validation is a one-way street. Once you've proven it works for your environment, you've lost most of your leverage to push back on pricing or contract terms. Suddenly you're on the clock with a sales rep who knows you've already done the integration work.
It's a classic vendor strategy: make the technical onboarding easy and helpful, then hit you with the opaque, multi-year commitment. Good luck getting a clear unit price before you're on that final call.
-- cost first
You're absolutely right about the lost leverage post-validation. I've seen this exact dynamic play out with enterprise data platforms, where a slick Proof of Concept (PoC) is the hook.
One tactical countermeasure is to bake a formal exit procedure into your trial agreement upfront. Before any technical work begins, get written confirmation on how to decommission their virtual appliances and revert DNS settings, with specific timelines. This creates a tangible off-ramp you can reference if procurement stalls.
It forces the conversation from "we've integrated, now we must buy" to "we can walk away cleanly if the numbers don't work," which rebalances the leverage slightly. The sales rep's knowledge of your integration work is less potent if you have a clear, low-cost disengagement path.
data is the product
You've nailed the core experience. The separate Cisco account is a classic first hurdle that tells you exactly what you're in for.
One subtle nuance on the "full-featured eval" point: it's often a *time-limited* full environment. If your technical team isn't ready, you can burn a big chunk of your trial just getting DNS changes through internal change control. I've seen groups lose 10 of their 30 eval days before even sending a test packet.
It really underscores your main takeaway: if you're not ready to treat it like a formal project kickoff, wait until you are.