Twine | One Week From Decision to Result

Monday, Jul 13

3 entries

08:00 Report

Weekly report, pulled and forwarded

Trailing 30 days: $28.4k of spend, pacing 98% of the monthly envelope. Six changes applied last week: five measured positive, one still in its measurement window. Pulled from Reporting, copied for Slack, forwarded. Written for the person you report to.

Note

The week starts with the answer to “what changed and why?”, not with the question.

11:42 Auto-applied G

Added 6 negative keywords on Demand Gen Search

Matched a proven pattern: search terms with $50+ spend and zero conversions over 30 days. Pattern success rate in this account: 92% across 90 days.

within policy · daily auto-apply cap: 1 of 5 used · reversible from snapshot

Note

Auto-apply is not a mode you switch on. It is a privilege this one pattern earned over 90 measured days, and it is capped per day.

16:20 Auto-applied G

Excluded 3 low-quality Display placements

Matched a proven pattern: placements with $40+ spend and zero conversions over 30 days.

saves ~$240/mo

within policy · daily auto-apply cap: 2 of 5 used · reversible from snapshot

Tuesday, Jul 14

4 entries

08:57 Proposed Approved G

Add 14 negative keywords across Search

−14 search terms$410/mo · 0 conversions

+Negative listsBrand + Non-Brand

projected: saves ~$410/mo

08:57 proposed → 09:01 approved by sarah@ → 09:02 applied, snapshot kept

09:03 Proposed Approved in

Shift $40/day to Enterprise Pipeline

−Mid-Market Retarget$90/day · CPL $118

+Enterprise Pipeline$130/day · CPL $62

09:03 approved by sarah@ → applied · pacing was 12% under monthly target

09:05 Held G

Refresh stale creative on Brand Search

Three variants drafted with the landing page and campaign goal in context. Held by sarah@ for Thursday’s creative review.

drafts kept · resolves Thu 10:02

14:14 External change detected G

Bid strategy changed on Enterprise Search, outside Twine

−StrategyTarget CPA ($38)

+StrategyMaximize Clicks (no cap)

Actor: agency@mediaco.com, via Google Ads directly. Detected from change history 11 minutes later. Flagged: removes the CPA cap mid-flight. Left in place, observed click costs projected roughly $1,100/mo of overspend.

14:36 revert proposed → 15:02 approved by sarah@ → reverted to snapshot

Note

Nobody at Twine made this change. It was caught anyway, named, and offered back as a one-click revert. The ledger doesn’t care who you are.

Wednesday, Jul 15

2 entries

10:12 Blocked by policy in

Proposed +45% budget on ABM Retarget. Policy said no.

Three strong days supported a bigger swing. Your policy caps budget increases at +25% per week, so the apply path refused it before any human saw a button.

re-proposed at +25% → queued for review · policy: max_budget_change ≤ 25%/wk

Note

The system asked. The policy won. Ask any vendor to show you what their agent wanted to do but wasn’t allowed to, and who said no. This is what that looks like.

15:40 Proposed G

Three variants drafted for Competitor Terms

Drafted against the /enterprise landing page and the campaign goal. Current ad is 41 days stale. Queued for the next creative review, separate from Tuesday’s held refresh.

Thursday, Jul 16

4 entries · measurement day

09:30 Measured G

Jul 9 negative-keyword batch: verdict positive

Spend down $338/mo against projection of $360. Conversions held, 41 to 42. Outcome recorded against the proposal that caused it.

pattern confidence raised

09:31 Measured Rolled back G

Jul 9 bid increase on Competitor Terms: verdict negative

CPL rose 11% over seven days, $105 to $117, conversions flat. The change did not do what it was supposed to do.

09:33 rolled back to snapshot · pre/post metrics kept on the record

09:34 Reflection

Why it failed, on the record

“Bid increases on competitor terms underperform in this account: auction pressure absorbs the bid without rank gain. Belief recorded at 0.7 confidence. Auto-apply confidence for this pattern lowered: future instances require human review.”

The unflattering entry

A wrong call costs a week, gets reversed from a snapshot, and gets remembered instead of repeated. Ask your agency for this paragraph about their last wrong call.

10:02 Approved G

Tuesday’s held creative refresh, resolved

Variant A approved by sarah@ after one edit. Applied to Brand Search. Every version kept.

held Tue 09:05 → approved Thu 10:02 · nothing expired while it waited

Friday, Jul 17

3 entries

09:40 Approved in

Wednesday’s re-proposed budget increase, resolved

The +25% version of the swing the policy refused at +45%. Inside the cap, so this time it reached a human.

blocked Wed 10:12 at +45% → re-proposed at +25% → 09:40 approved by sarah@ → applied, snapshot kept

11:20 Proposed R

Expand beyond r/sysadmin

−1 communityfrequency 4.1 and climbing

+r/devops, r/msp, +2 moreCPL guardrail $45

est. +18% qualified reach

awaiting your yes · Reddit changes never auto-apply, by design

16:05 Holding: thin data in

Audience expansion on Mid-Market: not yet

Nine conversions in the window. The volume guard wants twenty before anyone draws a conclusion from this audience. Holding two more weeks rather than guessing with your money.

Note

It also knows when not to act. Thin data holds. An operator who never says “not enough signal yet” is guessing on someone’s budget.

Saturday and Sunday

0 changes

Monitoring only. Sync every four hours. Spend pacing 99% of plan. Nothing needed you, so nothing asked for you.

Monday, Jul 20

the week, closed

08:00 Report

Weekly report, pulled and forwarded

What changed, why, what it did to the numbers, and what’s queued next. One click to copy for Slack or export. Written to be forwarded.

The week, totaled

Proposals raised8

Approved by a human5

Auto-applied within policy2

Blocked by policy1

External changes caught1

Rolled back after measurement1

Projected monthly waste cut~$1,750

Approval time spent11 min

Every number above traces back to an entry in the week.

The work stays on the record. You spend your time on the decisions, not reconstructing what happened.