WEBVTT

1
00:00:10.000 --> 00:00:14.125
Most AI demos show you
a model having ideas.

2
00:00:14.175 --> 00:00:17.051
This one shows a worker finishing a job.

3
00:00:17.101 --> 00:00:19.502
A US launch for a hair serum,

4
00:00:19.552 --> 00:00:24.821
from a client brief to paused
campaigns in Google and Meta,

5
00:00:24.871 --> 00:00:28.148
with an agency in control the whole way.

6
00:00:28.198 --> 00:00:31.882
The brief and budgets
are demo assumptions.

7
00:00:31.932 --> 00:00:36.882
The workspace, the assets and
the campaign objects are real.

8
00:00:36.932 --> 00:00:41.566
Watch what a workplace lets an
AI worker actually complete.

9
00:00:42.950 --> 00:00:47.943
One agency job: a new US launch
for Ellātu’s Silky Touch Serum.

10
00:00:47.993 --> 00:00:52.194
The brief, audiences and
budgets are demo assumptions.

11
00:00:52.244 --> 00:00:55.881
The references, workspace and
campaign objects are real.

12
00:00:55.931 --> 00:01:01.720
This Gmail brief is staged; automatic
email intake is not demonstrated.

13
00:01:01.770 --> 00:01:06.761
Our question is what work can be
completed while the agency keeps control.

14
00:01:07.350 --> 00:01:11.027
Here is DEMO 018, the
workspace used for this job.

15
00:01:11.077 --> 00:01:14.755
The workspace matters
because the worker needs the

16
00:01:14.805 --> 00:01:18.556
right client knowledge and
access before it begins.

17
00:01:18.606 --> 00:01:22.060
This screen establishes
the workspace identity.

18
00:01:22.630 --> 00:01:26.502
Saved Context describes the
product, the US demo market,

19
00:01:26.552 --> 00:01:29.165
the premium visual direction
and supported claims.

20
00:01:29.215 --> 00:01:31.825
It also establishes the review boundary:

21
00:01:31.875 --> 00:01:36.861
internal review before client communication,
and approval before meaningful changes.

22
00:01:36.911 --> 00:01:40.201
This is the current Context used
before the new-account build.

23
00:01:40.251 --> 00:01:43.703
Saved knowledge does not
expand API permissions.

24
00:01:44.270 --> 00:01:46.596
The worker you're watching is Ollie,

25
00:01:46.646 --> 00:01:50.995
an AI worker plugin running
inside this Outloop workspace.

26
00:01:51.045 --> 00:01:54.883
Outloop gives Ollie the client
Context, approved access,

27
00:01:54.933 --> 00:01:59.328
connected systems and approval rules
it needs to actually finish the work.

28
00:02:00.830 --> 00:02:04.239
Research informs decisions
rather than filling a report.

29
00:02:04.289 --> 00:02:07.334
Official product information
sets the claims boundary.

30
00:02:07.384 --> 00:02:10.647
A dated competitor sample
helps with positioning.

31
00:02:10.697 --> 00:02:14.311
Retrieved keyword estimates
help group relevant searches,

32
00:02:14.361 --> 00:02:16.569
but they are not Ellātu performance.

33
00:02:16.619 --> 00:02:19.788
Hair-growth intent is
deliberately excluded

34
00:02:19.838 --> 00:02:22.842
because search demand does
not make a claim valid.

35
00:02:22.892 --> 00:02:27.563
Overlapping search estimates are
not added together as unique demand.

36
00:02:28.110 --> 00:02:31.535
The resulting Search
structure has two ad groups,

37
00:02:31.585 --> 00:02:35.839
ten keywords, fifty negatives
and one responsive search ad.

38
00:02:35.889 --> 00:02:41.836
Meta uses one campaign, one ad set and
one ad with the approved dark creative.

39
00:02:41.886 --> 00:02:45.625
The US audience and budgets
are demo assumptions.

40
00:02:45.675 --> 00:02:48.430
USD and ILS are shown separately.

41
00:02:48.480 --> 00:02:52.115
Every delivery object
is configured paused;

42
00:02:52.165 --> 00:02:55.271
a configured budget is
not permission to spend.

43
00:02:55.720 --> 00:02:58.899
So far the worker has
understood the client:

44
00:02:58.949 --> 00:03:03.358
the claims it may make, the
market, and what to leave out.

45
00:03:03.408 --> 00:03:06.798
Now it moves from understanding to making,

46
00:03:06.848 --> 00:03:10.774
using the client's own files,
not stock inspiration.

47
00:03:12.150 --> 00:03:16.469
The worker draws on approved
Drive files: the actual wordmark,

48
00:03:16.519 --> 00:03:19.436
product photography and
supporting references.

49
00:03:19.486 --> 00:03:22.633
These establish brand
and product identity.

50
00:03:22.683 --> 00:03:25.694
Ingredient references
support the composition.

51
00:03:25.744 --> 00:03:28.241
They do not replace the real product or

52
00:03:28.291 --> 00:03:31.319
turn inspiration into
an authoritative asset.

53
00:03:31.950 --> 00:03:35.500
The accepted creative package
keeps the product central,

54
00:03:35.550 --> 00:03:38.243
with restrained copy and
a clear call to action.

55
00:03:38.293 --> 00:03:42.716
We can compare dark and ingredient-led
variants and useful formats.

56
00:03:42.766 --> 00:03:47.130
These are generated campaign assets
using the approved references.

57
00:03:47.180 --> 00:03:49.644
Showing a landscape asset here does not

58
00:03:49.694 --> 00:03:52.086
mean it was installed
as a Google Display ad;

59
00:03:52.136 --> 00:03:54.723
the actual Google build is Search.

60
00:03:55.310 --> 00:04:00.306
These next emails are a staged demo
reconstruction of real approved decisions,

61
00:04:00.356 --> 00:04:03.590
not the original
historical email exchange.

62
00:04:03.640 --> 00:04:07.890
Ollie presents the package for internal
review before the client sees it.

63
00:04:07.940 --> 00:04:13.089
The Account Manager is asked for commercial
judgment: how to treat past purchasers,

64
00:04:13.139 --> 00:04:17.063
and what planning information
belongs in the client summary.

65
00:04:17.630 --> 00:04:20.106
The Account Manager supplies two rules:

66
00:04:20.156 --> 00:04:23.101
no discount-led messaging
to past purchasers,

67
00:04:23.151 --> 00:04:26.179
and no forecast figures
in client communication.

68
00:04:26.229 --> 00:04:30.893
The package and both rules are
approved for client review.

69
00:04:30.943 --> 00:04:33.111
Ollie confirms the corrected
package follows them.

70
00:04:33.161 --> 00:04:37.309
This internal approval does
not authorize campaign writes.

71
00:04:37.359 --> 00:04:40.574
The current Context already
contains these rules;

72
00:04:40.624 --> 00:04:43.838
these staged emails did
not save them again.

73
00:04:44.430 --> 00:04:50.551
The preserved original Outloop receipt
records revision 23 and both exact rules.

74
00:04:50.601 --> 00:04:55.121
This is historical receipt evidence, not
a recording of the old settings screen.

75
00:04:55.171 --> 00:04:57.759
The current Context is revision 34.

76
00:04:57.809 --> 00:05:01.838
The lesson is persistent
approved client knowledge,

77
00:05:01.888 --> 00:05:04.123
with the same permission boundary.

78
00:05:04.520 --> 00:05:09.783
Two decisions in that package
were commercial, not compliance.

79
00:05:09.833 --> 00:05:11.396
How to treat past purchasers.

80
00:05:11.446 --> 00:05:15.201
Whether a forecast belongs
in front of the client.

81
00:05:15.251 --> 00:05:16.542
Those are human calls.

82
00:05:16.592 --> 00:05:22.127
The Account Manager made them once,
the worker corrected the package,

83
00:05:22.177 --> 00:05:25.844
and the rules stayed in
the client's Context.

84
00:05:25.894 --> 00:05:29.814
That is what a workplace does
that a chat window cannot.

85
00:05:31.190 --> 00:05:33.982
We now return to a real received email.

86
00:05:34.032 --> 00:05:36.074
It describes the new-account
build and includes

87
00:05:36.124 --> 00:05:39.944
the scope document and
approved creative attachments.

88
00:05:39.994 --> 00:05:43.424
The client receives a concise
account of what is proposed,

89
00:05:43.474 --> 00:05:45.015
before the platform write.

90
00:05:45.065 --> 00:05:48.587
This email predates the
staged review reconstruction;

91
00:05:48.637 --> 00:05:52.040
the film groups the steps
to explain the workflow.

92
00:05:52.630 --> 00:05:58.022
Acting as the demo client, Adam approved
this exact new-account scope, paused only.

93
00:05:58.072 --> 00:06:00.204
That approval occurred in chat.

94
00:06:00.254 --> 00:06:04.687
The on-screen presentation is a labeled
transcription, not a Gmail reply.

95
00:06:04.737 --> 00:06:08.930
Internal approval and client
approval are separate gates.

96
00:06:09.470 --> 00:06:14.468
Once the client approves, Ollie doesn't
stop at a media plan or a recommendation.

97
00:06:14.518 --> 00:06:17.395
Through Outloop's approved access,

98
00:06:17.445 --> 00:06:22.042
it builds the campaign and pushes
it directly into the ad accounts:

99
00:06:22.092 --> 00:06:23.027
campaign structure,

100
00:06:23.077 --> 00:06:26.896
ad groups, ad sets, keywords,
negatives, targeting,

101
00:06:26.946 --> 00:06:31.404
budgets and creative, while keeping
everything PAUSED for review.

102
00:06:32.190 --> 00:06:37.203
In Google Ads, the worker built
the campaign, ad groups, keywords,

103
00:06:37.253 --> 00:06:39.730
negative list and responsive search ad,

104
00:06:39.780 --> 00:06:43.406
pushed the build into the
account, and kept it PAUSED.

105
00:06:43.456 --> 00:06:49.021
The negative list is attached as an
exclusion, not as permission to deliver.

106
00:06:49.071 --> 00:06:53.912
Then it read every object back
through the API to verify the setup.

107
00:06:53.962 --> 00:06:56.493
This is a fresh build in the new account;

108
00:06:56.543 --> 00:06:59.803
no older ad was recreated
to show retention.

109
00:07:00.350 --> 00:07:02.670
On Meta, it created the campaign,

110
00:07:02.720 --> 00:07:08.171
ad set and ad with the approved dark creative
inside an authorized demo ad account,

111
00:07:08.221 --> 00:07:10.150
not an Ellātu-owned account.

112
00:07:10.200 --> 00:07:14.517
Again configured PAUSED, and
verified through the API.

113
00:07:14.567 --> 00:07:18.582
The read-back reported the ad's
effective status as in process.

114
00:07:18.632 --> 00:07:22.057
That is not platform approval or delivery.

115
00:07:22.590 --> 00:07:25.597
For the specified September
19 reporting period,

116
00:07:25.647 --> 00:07:29.854
Google returned numeric zero
cost, impressions and clicks.

117
00:07:29.904 --> 00:07:31.790
Meta returned no reporting rows.

118
00:07:31.840 --> 00:07:36.701
No rows is not a measured zero, so
we do not describe it that way.

119
00:07:36.751 --> 00:07:41.174
These are dated observations, not a
promise about future account activity.

120
00:07:41.750 --> 00:07:44.731
The real completion email tells the client

121
00:07:44.781 --> 00:07:47.901
what was built and confirms
it remains paused.

122
00:07:47.951 --> 00:07:51.955
Its disclosure about UI inspection
was accurate when sent;

123
00:07:52.005 --> 00:07:55.604
the interface footage was captured later.

124
00:07:55.654 --> 00:07:59.625
The client gets a clear conclusion
grounded in the actual objects,

125
00:07:59.675 --> 00:08:02.920
without an invented performance forecast.

126
00:08:03.470 --> 00:08:07.055
Finally, both commercial
rules remain in Saved Context.

127
00:08:07.105 --> 00:08:09.982
The next job can use
that approved knowledge.

128
00:08:10.032 --> 00:08:15.140
Human judgment persists, while approval
and runtime permissions remain separate.

129
00:08:15.710 --> 00:08:20.011
That is the agency workflow:
approved knowledge, useful work,

130
00:08:20.061 --> 00:08:25.152
human review, client approval, real
paused execution and verification.

131
00:08:25.560 --> 00:08:28.154
AI workers need more than a model.

132
00:08:28.204 --> 00:08:32.840
They need a workplace: approved
knowledge, the right access,

133
00:08:32.890 --> 00:08:37.086
human review, and real systems
they can work in safely.

134
00:08:37.136 --> 00:08:38.282
That is Outloop.

135
00:08:38.332 --> 00:08:39.847
Start your free trial,

136
00:08:39.897 --> 00:08:46.331
or book an AI Workflow Review and we will
walk through one of your own workflows.