Work got heavy. We’re fixing that.
Marketing got complicated because the tools got complicated. More dashboards, more prompts, more meetings about the work instead of the work. We think AI should do the heavy part so you can do the interesting part. That's it.
Why we bothered
We built Mojo because campaign strategy shouldn't require a PhD in your own data. The best marketers we know aren't slow because they lack ideas. They're slow because the work between the idea and the result is genuinely heavy. We're here to lift that.
Small team, few rules, one fur coat
Chief Unblocker
Makes sure the right things get to ship. Once spotted a competitive pivot in real time and dropped it in the channel same day.
Studied Comparative Literature and Russian at Brown. Somehow ended up running a B2B software company. Calls it 'the same skill set, different medium.'
CEO, Demandbase · Previously CRO · 14 years at Demandbase
The one who decides what Mojo actually is
Shapes the product vision and makes the hard calls about what makes the cut.
Previously at Nextdoor and Axios. Joined Mojo because the problem was real enough and the room was weird enough.
VP Product Management, Demandbase
Built the plumbing before the plumbing existed
Takes on the infrastructure problems that require inventing the solution instead of finding one.
Built one of the first DSPs in the industry. Has been doing AI since the '90s, long before it was a job title. Doesn't take up much space in a room. When he talks, everyone stops.
CTO Advertising, Demandbase
The reason things ship
Keeps engineering moving, from standup pre-reads and P1 burn-downs to the merge requests nobody sees but everyone benefits from.
Keeps score on things most people don't notice. Knows the velocity number before you ask.
Sr. Director Engineering, Demandbase
Mojo's #1 power user and unofficial translator
Finds new use cases, runs the analytics, and connects the product to the people actually using it.
Studied international relations and journalism in Wisconsin. Ended up in ad tech. Located in Vancouver. Still makes it make sense.
Sr. Director AdCloud, Demandbase
Makes the complex feel obvious
Leads product design and makes sure users never have to think about the machinery underneath.
You describe the outcome. She makes sure Mojo can take it from there.
Architect UX Designer, Demandbase
Finishes the feature before you finish the sentence requesting it
Owns the agentic infrastructure — routines, durable agent, workflow execution. Merges at midnight with a cowboy emoji.
Writes MR descriptions that are clearer than most product specs. His release notes are a genre.
Engineer, Demandbase
Obsessed with what the agent knows and can do
Builds the harness Mojo's agents work inside — what they know, and what keeps them going.
Relentless edge-case finder and permanent resident of the bleeding edge, with a need for speed. 🤓
Sr. Manager Engineering, Demandbase
Allergic to doing things the hard way
Makes sure our users never have to do things the hard way either, building out the chat action buttons that do the typing for you, as well as our global search.
An efficiency fanatic who wired our entire production deployment to a single Slack command. He followed that up by building an autonomous bug-hunting agent, because doing anything manually is out of the question 🚀
Sr. Engineer, Demandbase
The quiet one who just made something better
Keeps the product moving, from upload limits and testing environments to the issues that only show up once real people start using something.
Makes sure things break safely before they break publicly.
Sr. Engineer, Demandbase
Keeps the whole thing running without anyone noticing
Owns the infrastructure Mojo runs on.
Shows up in the channel, says something precise, disappears. Things are fine.
Principal DevOps Engineer, Demandbase
Tells the story and figures out who needs to hear it
Runs GTM, growth, and everything that gets Mojo in front of the right people.
Has spent enough time inside B2B marketing to know campaign strategy shouldn’t require a PhD in your own data.
Head of Marketing
The one obsessed with the architecture of our system
Goes deep on how the architecture actually fits together, then does whatever needs to be done to produce the perfect system — shipping features, resolving technical debt, refactoring the architecture — so what's left is coherent, cohesive, and resilient.
The clarity we build into the system is the clarity users feel when they use it.
Staff Engineer, Demandbase
Makes the agents smarter and the system bulletproof
Builds the intelligence layer that helps agents find the right connections and data. Enhances tools that make the whole engineering team move faster.
The kind of engineer who enhances agent connection suggestions and then seamlessly fixes integrations & connections. Notices the details that keep everything moving.
Engineer, Demandbase
Makes sure the agent can't break what it touches
Works on the capabilities that let Mojo act inside live marketing systems, and the guardrails that keep a wrong move from ever reaching production.
Treats write access as a safety problem first. Redacts what shouldn't be seen, refuses the retry that would apply a change twice, and would rather return a clear error than a confident guess.
Engineer, Demandbase
Helps the product feel connected all the way through
Builds the paths between product experience, agent context, and provider capabilities so Mojo can understand the ask and take the right next step.
Likes finding the small bits of context that make a complicated flow quietly start making sense.
Engineer, Demandbase
Golden retriever energy for new features
Owns the canvas creation layer and the guided campaign chat on top — where ideas become something you can work in, not just talk about. Keeps frontend standards tight so 'yes, and' doesn't mean slower. Never met an idea he didn't want to try.
Lives by; 'Yes, and — what if it also did this?'
Sr. Engineer, Demandbase
Keeps design, engineering, and customer feedback in sync
Sits right in the middle of design, engineering, and customer feedback to make sure we're building the right things in the right order.
Big fan of clean workflows, clear priority lists, and zero surprise edge cases.
Lead Product Manager, Demandbase
Demandbase has spent two decades inside B2B marketing: the campaigns, the attribution models, the edge cases, the Marketo-to-Salesforce sync failures, the UTM conventions that work and the ones that silently corrupt a quarter of pipeline data.
Mojo is what happens when that knowledge gets built into an AI teammate, not trained on documentation, but on how B2B marketing teams actually operate.
Join the beta. Connect your stack. Ask the question you've been meaning to ask.