Solutions · Enterprise
Your spend is recorded. The reasoning behind it isn’t.
At portfolio scale the hard question stops being what the numbers did. It becomes who decided, on what evidence, at what stated confidence - and whether they turned out to be right. Datsutra records that by default, because a decision without a record is an opinion nobody can audit.
Enterprise engagements are scoped, not listed - you will get a number in the conversation, not after three of them.
Every decision on the record, with its reasoning.
A quarterly review usually reconstructs itself from a deck, a chat thread and someone’s recollection of why budget moved out of prospecting in March - the numbers survive, the reasoning rarely does. Datsutra writes the reasoning down as the decision is made: who decided, on what evidence, with what confidence, and what the outcome turned out to be. So next quarter starts from what was already learned.
What gets written down, every time
Not a log of what changed in the account - those already exist and nobody reviews them. A record of the judgment: what was proposed, how sure it was, what it rested on, who acted, and what happened.
What was proposed, and which business objective it served - reduce wasted spend, scale what's working, bring CPA down, protect something still performing.
High, medium or low - recorded at the moment of the decision, before the outcome was known. That ordering is the only one under which a confidence claim means anything.
The signals the conclusion rested on, and the competing explanations that were weighed and rejected.
Who committed, snoozed or dismissed it, and when. The engine proposes; a named person decides.
The metrics as they stood before the action, captured at the same time as the review window - so nobody chooses the comparison period after the fact.
When the window matures: improved, neutral, worse, or inconclusive, measured against that snapshot. Including the calls that were wrong.
None of it is reconstructed afterwards. That is the whole point: a record assembled after the outcome is known is a story, not evidence.
Control, at the level your governance actually operates
Roles and reporting lines
Admin, manager and marketer views, with a reports-to structure that mirrors your org. A manager's home is their line's queue - not a permissions matrix nobody maintains.
Separation of duties, by design
Datsutra has no authority to change a budget, pause a campaign, or execute anything. It cannot act, so every action in your accounts remains attributable to a person.
Portfolio structure
Brands, markets or business units set up as separate client accounts inside one workspace, each with its own economics - with a single platform authorisation paired to as many ad accounts as the portfolio needs.
Economic guardrails, versioned
Margin, COGS, AOV, LTV, sales cycle, constraints and priority KPIs recorded per business, with revision history and provenance on each field: what was set, by whom, and from when.
Declared blindness
Stale, thin or missing data is stated rather than smoothed over. No recommendation is ever more confident than the data underneath it - which is the property that makes the record reviewable at all.
Four audiences, one record
Operational, manager, executive and client reports are drawn from the same underlying record and differ only in what they expose. Internal reasoning, evidence and confidence levels never cross into a client-facing report - that boundary is structural, not a formatting choice.
Stable case references
Every investigation carries a per-client case number that never renumbers, so a decision can be cited in a review a quarter later and still resolve to the same thing.
What we’ll tell you before procurement asks
Enterprise pages in this category tend to open with a wall of compliance badges. Here is the straight version instead: ask us for our current data-handling posture and we will answer it in writing - what we store, where, for how long, how platform credentials are held, and what we have and have not certified to date.
Where the answer is “not yet”, you will get “not yet” and a date, not a logo. A tool whose entire claim is that it refuses to manufacture certainty does not get to start with its own security posture.
Read the privacy policyHow an engagement starts
A scoping call
Portfolio shape, the roles and reporting lines to mirror, and the questions your reviews actually have to answer. Half an hour is usually enough to know whether this is a fit.
Connection and structure
Brands or business units set up as client accounts, ad accounts paired, people placed into roles. Google Ads and Meta are live today; GA4, Shopify and CRM are on the roadmap and will be called live only when they are.
Economics before recommendations
Targets, margins and constraints recorded per business, so the first investigation is already held to your numbers rather than a platform default.
A review cadence
Decisions and their verdicts, in writing, at whatever interval your governance runs on. The record is a by-product of the work, not a reporting exercise bolted on top.
Scoped, not listed
Our published plans are self-serve and run up to twelve client accounts - if that is your shape, take them, they are the better deal. Enterprise begins where that stops: a larger portfolio, roles and reporting lines mirrored from your org, a security review, procurement, invoicing and a contract. Those we scope with you, because pretending otherwise would mean posting a number we would then have to renegotiate.
Questions, answered straight
Will it change anything in our ad accounts?
No - and this is architectural, not a setting. Datsutra reads, investigates and recommends. Every change is executed by a person who chose to make it, which is what keeps the decision record attributable.
Can it be scoped to one region or business unit?
Yes. Each brand, market or unit is its own client account with its own economics, and people are placed into roles and reporting lines so they see their own scope.
What about SSO, security review and procurement?
Raise them on the scoping call and you will get specific answers in writing rather than a badge wall - including where the honest answer is 'not yet'. We would rather lose a deal on a precise answer than win one on a claim we have not earned.
What happens to our data if we leave?
Data is retained while the account is active and deleted on request, subject to the backup and legal-retention terms set out in our privacy policy. Ask for the specifics in the scoping call and we will put them in writing.
Can you run it for us instead?
Yes - the same engine powers our own client work. That is a services engagement rather than a licence; see the Services page.