Flat monthly price · No percentage of spend — See pricing
Twine
→ See Twine on your accounts→ See Twine
Menu
→ See Twine on your accounts
The decision ledger · interactive walkthrough · representative data

See every decision,
from the target to the report.

This representative week shows how Twine records the quarterly target, planning decisions, proposed changes, human approvals, blocked work, outside changes, launch health, and measured outcomes, including a decision that was wrong and rolled back, and the frozen report leadership receives.

DocumentDecision ledger, one week
AccountB2B SaaS · Google + LinkedIn + Reddit · ~$28k/mo
Quarterly target12 qualified opportunities · 9 observed · review Aug 14
PeriodMon Jul 13 to Mon Jul 20, 2026
SourceIllustrative reconstruction of typical operation. Representative numbers, not customer data.
10recommendations raised
4held or no action, recorded
1wrong call rolled back
13mhuman approval time
→ See this loop on your accounts ← Back to the overview

The first step is founder-run and read-only. Nothing can change.

Monday, Jul 13

6 entries · the target sets the boundary
08:00 Slack · the read
The Monday read, posted in the team’s channel
Twine posts the Monday read in the paid-media Slack channel: spend is pacing 98% of the monthly envelope, three opportunities are still maturing, and no budget decision is urgent. Sarah opens the attached target only because she wants the underlying evidence.
a quiet account does not demand a dashboard check · the full evidence stays one click away
Note
The week starts with the answer to “what changed and why?”, not with the question. It arrives where the team already works.
08:15 Target
Quarterly target reviewed before any spend moves
The quarter calls for twelve qualified opportunities from paid media. Nine are currently observed; three remain inside the sales-cycle lag. Sarah reviews the current target version and the base scenario before changing anything.
qualified opportunities: 12 target · 9 observed · 3 maturing · evidence tier: moderate · review date Aug 14 · target v3, immutable
08:22 Scenario
Base plan selected
Keep the current channel allocation. Hold $3,000 in reserve until the three open opportunities mature.
08:24 No action
No additional budget action justified today
The base scenario already funds the highest-confidence work. The no-action call is recorded against the target, with the review date attached.
What this proves
Twine connects account work to a business target. No action can be a reviewed decision. And the plan does not convert automatically into platform changes.
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

5 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 · supports target: protect qualified CPL while preserving coverage
Sarah8:58 AM · in the alert thread

Why now? We have had waste in that campaign for weeks.

Twine8:58 AM

The search terms crossed the account’s review threshold yesterday. The recommendation is based on $410 in spend over 90 days with no qualified conversions.

Google Ads pulled 8:51 AM · HubSpot synced 6:10 AM · links to the complete Decision Brief
08:57 proposed → staged from Slack for review → 09:01 approved by sarah@ in Twine → 09:02 applied, snapshot kept · Slack does not approve or apply
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
11:40 Proposed Approved G
New Enterprise trial campaign, staged and launched
Drafted from the /enterprise landing page: structure, targeting, copy, budget, measurement plan, and a $45 CPL guardrail. Readiness checks passed before anything staged: account access, platform capability, conversion tracking, policy.
LNCH-081 · 11:40 bundle proposed → 11:52 approved by sarah@ → applied · launch health checks begin → see Wednesday
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

3 entries · live does not mean verified
09:00 Measuring G
Tuesday’s launch: health check, not a victory lap
Expected: delivery within eight hours, recording the selected conversion event. Observed: active and delivering. The conversion event has not accumulated enough evidence to say anything about the business outcome.
Sarah9:02 AM · in the launch thread

Check again after the next CRM sync and let me know here.

Twine9:02 AM

I will follow up in this thread tomorrow after the sync.

follow-up recorded · returns to the same thread · rereads what the team discussed first
LNCH-081 · state: measuring · next check Thu 09:00 · no corrective action · the campaign is behaving as expected and the evidence is not mature
What this proves
Twine checks the result of execution, distinguishes delivery from business-outcome measurement, and does not manufacture a corrective change while evidence is pending. And the operator can delegate the follow-up instead of setting a reminder and repeating the context tomorrow.
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

5 entries · measurement day
09:28 Slack · promised return G
Twine returns to the thread it promised to return to
Twine9:28 AM

Following up as promised: the Jul 9 bid change is delivering, but qualified CPL is running above the stop threshold. I prepared a recommendation to restore the prior bid strategy.

source: Google Ads, pulled 9:26 AM · confidence: high · limitation: one-week window · links to the reviewable recommendation
the restoration follows the normal review path → resolved at 09:31 below
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:32 restore approved by sarah@ → 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 negative outcome lowers confidence in the pattern · it does not become a durable account belief until measured evidence supports that conclusion
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

4 entries · leadership gets the same evidence
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.
16:30 Report frozen
The week’s snapshot, frozen for leadership
Sarah freezes the reporting snapshot and shares the selected artifact in Slack. Observed facts stay separate from Twine’s interpretation, and next week’s possible budget move stays labeled as an unapproved proposal. The Slack summary and the complete report come from the same frozen evidence.
Observed fact

Search-term exclusions reduced spend by $383 while qualified conversion volume held.

Twine interpretation

The result supports continued search-term hygiene. Low conversion volume limits broader conclusions.

Operator decision

Keep the exclusions. Do not expand the rule to other campaigns yet.

Future proposal · not approved

Evaluate a $40 per day shift after the remaining opportunities mature.

frozen · SNP-0717 · corrections append later · the original stays visible
What this proves
Reporting is downstream of the operating record. Interpretation stays labeled. A future proposal cannot be mistaken for a decision or an applied change.

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 raised10
Approved by a human7
Auto-applied within policy2
Blocked by policy1
External changes caught1
Held or no action, on the record4
Rolled back after measurement1
Reporting snapshots frozen1
Projected monthly waste cut~$1,750
Approval time spent13 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.

See what Twine finds in your accounts. Keep the findings either way.

→ See Twine on your accounts → See pricing first