OobiMax
OobiMax gives performance teams one place to decide what to do next.
See the next move without rebuilding context from dashboards, chat, screenshots, and memory.
See the next move without rebuilding context from chat.
The pain OobiMax removes
OobiMax turns scattered signal, policy evidence, approvals, and learning into one visible operating loop.
OobiMax turns signal into a reviewable recommendation, not another metric tile.
Policy calls should not live in screenshots, Slack threads, or memory. Campaign nature, market evidence, reviewer, source, confidence, and decision statement stay structured.
Old advice should dissolve when it is approved, rejected, resolved, or superseded. Rechecks and outcome states keep external mirrors from becoming a second truth.
AI, billing, measurement hints, and evidence never become silent spend authority. Draft, review, approve, apply, retry, recheck, launch, delivery, and spend stay deliberately separate.
Policy & Evidence Center
Policy questions get expensive when approval memory lives in screenshots, chat threads, or someone's head. OobiMax turns evidence into a visible gate before launch, delivery, or spend.
How It Works
Connect Google and Meta access paths without confusing sources for ad accounts.
OobiMax finds reachable ad accounts, then each brand chooses the right source and account.
See what matters, why it matters, and whether the next step is executable, review-only, or a plan.
Keep recommendations local or send selected items to Slack and Telegram, then watch what changes.
Product Preview
Every recommendation keeps its REC #, signal, evidence, approval state, delivery history, and freshness in one place.
The record stays attached before anyone sends, approves, or applies work.
Sources, accounts, and brand mappings stay clear before recommendations begin.
The change, reason, expected effect, evidence, approval state, and freshness stay together.
Policy, measurement, approval, and delivery state remain visible before work moves.
Existing campaign control
Open a synced campaign, compare current platform values against proposed edits, run Change Review, collect approval evidence, and apply only supported changes. Drafting is safe and free; spend-affecting actions stay behind explicit approval.
Campaign Editor is the safe place to review, approve, apply, retry, and recheck supported edits.
Status, budget, targeting, ads, keywords, and creative rows show collected platform state first.
Impact, risk, linked recommendations, approval needs, and verification stay visible.
After approved apply, old recommendations become resolved, superseded, or still relevant.
Our Architecture
The media map shows who OobiMax can reach: sources, accounts, and brands. The signal map shows what evidence exists: GA4, Search Console, Pixel/CAPI, and conversion proof. Keeping them separate keeps the product honest.
One isolated operating environment.
Google and Meta access stays mapped before recommendations begin.
Each brand chooses the right platform account.
Inbox holds the decision record.
Slack and Telegram mirror selected decisions only.
Brands, sources, approvals, delivery, and learning stay scoped.
MCC or direct account path
Discovered under source
Same or different source
Google + Meta mapped
Google mapped
Source of truth
Explicit send only
Explicit send only
Higher-tier feature
Campaign Builder brings creative, brand context, account signal, budget comfort, measurement checks, and platform previews into one editable plan. It does not silently launch spend.
Builder prepares structure. Existing campaign edits stay in Campaign Editor.
Links, uploads, approved assets, or connected Canva designs become the starting point.
Imported creative stays pending until inspection and selected-brand approval.
Account history can shape the plan. Creation, resume, and spend stay separate approvals.
Operator Trust
Dashboard, Slack, and Telegram must agree on the work, the decision, the execution state, and who handled it.
Brands, sources, accounts, delivery settings, and approvals stay inside the right workspace.
Operators can approve, reject, skip, retry, or open the Inbox from the right surface.
Already-handled actions show original operator, surface, status, and execution result.
Controlled Beta Access
OobiMax is onboarding selected teams first. Approved workspaces can subscribe or buy credits inside Billing; public visitors request access before checkout.
