Why OobiMax exists
Built by operators who needed a better decision layer
Paid media teams already have dashboards. OobiMax was built to answer the harder questions: what matters now, what should change, who approved it, and what happened next.
Evidence before recommendations
Approval before execution
Learning that survives account changes
Dashboards were not the missing piece
Campaign data lives across Google, Meta, analytics, spreadsheets, and chat. Platform recommendations often ignore the business behind the account, while approval history and campaign learning disappear into threads and memory.
- too much account data and too little prioritization
- generic platform advice without enough brand or business context
- approvals scattered across dashboards, Slack, Telegram, and spreadsheets
- useful account learning lost during handoffs, migrations, or account changes
OobiMax turns evidence into a controlled next move
OobiMax connects real paid media accounts, keeps each brand mapped to the right context, and turns current evidence into prioritized recommendations.
- find waste, missed opportunities, risks, and measurement gaps
- show the exact scope, reason, expected effect, and actionability
- keep supported changes behind explicit operator approval
- track execution, recovery, rechecks, and post-action learning
- preserve useful historical-account learning without treating old accounts as execution targets
Designed for accountable operators
OobiMax is for founders, performance marketers, growth teams, and agencies managing real campaigns and budgets. It helps them move faster without surrendering control to a black box.
Inbox remains the current decision record. Slack and Telegram mirror it. Measurement and AI advice inform the decision; they never authorize spend by themselves.
Built from real operating work
OobiMax is developed by Meidan Meshulam with Jillian Goldberg and Omprakash Singh. The product combines hands-on paid media operations, product building, growth strategy, enterprise systems, and security engineering.
A product-focused builder with a background in cybersecurity, networking, and enterprise software.
At Skybox Security, Meidan worked across product and engineering, translating complex systems into working environments for development and customer onboarding.
He also built an independent ecosystem across product, content, and manufacturing:
- Rexx Timepieces - custom mechanical watches and private-label development
- Meshberg Watches - small-batch experimental watchmaking
- Rexx StudioWorks - fabrication and production of engraved components
- The Watcher HQ - a content platform focused on technical storytelling and education
His work combines technical depth, hands-on execution, and product thinking.
inMeidan on LinkedIn
An operator and entrepreneur with extensive experience scaling companies, leading go-to-market strategy, and driving growth in complex environments.
As Chief Revenue & Investment Officer and a board member at GuardKnox, Jillian helped scale the company from stealth startup to a global Tier 1 supplier.
Her experience spans:
- global GTM strategy
- high-growth environments
- fundraising and investor relations
- building systems in ambiguity and zero-to-one stages
Her approach is direct and execution-focused: step in, solve problems, and move forward.
inJillian on LinkedIn
An early OobiMax technical partner focused on cyber risk, platform intelligence, product security, and complex digital systems.
Omprakash brings more than 20 years across network security, cloud environments, enterprise consulting, professional services, product R&D, and global engineering leadership.
His work sits between architecture, delivery, and escalation: helping teams design secure platforms, integrate complex data sources, and get unstuck when product, engineering, and customer issues cut across each other.
His experience spans:
- network security, firewalls, IPS/IDS, SASE, SDN, and OT environments
- cloud and security management platforms
- product security and platform R&D leadership
- complex delivery, escalation, and customer-facing architecture
inOmprakash on LinkedIn
The belief behind the product
Performance teams do not need more noise. They need a reliable way to understand the next move, approve it deliberately, recover when something fails, and keep the learning after the week is over.
