The weekly shipping log is the most underrated marketing artifact we publish

May 7, 2026

The weekly shipping log is the most underrated marketing artifact we publish

For most agencies, marketing is a loud activity. Hot takes, big claims, viral threads. The output reads like advertising even when it is dressed up as content. The weekly shipping log is the most underrated marketing artifact we publish, and it runs the opposite shape: a Friday changelog written for the senior operator who is trying to figure out whether your team is real. This piece is for founders and operators of services businesses who suspect their marketing is performing the wrong job, and want a concrete format that doubles as an operating discipline.

The mechanics generalise. Six sections, same shape every Friday, thirty minutes once the schema is muscle memory. The audience is smaller than a hot take and the conversion is wildly higher. What follows is the format, the failure modes, and a runbook for adopting it without turning it into another piece of marketing theatre.

Why the weekly shipping log outperforms hot takes for B2B services

A hot take competes against millions of other hot takes for thirty seconds of attention. A shipping log competes for the attention of one operator who is trying to figure out whether your team is real. The audience is smaller and the conversion is wildly higher. That is the entire arbitrage and it holds across services categories where the buyer is technical or operational.

Three things move when you ship the log every week. First, repeat readers grow disproportionately because the form is predictable. They know where the value is on the page and they read on the schedule the schedule trains them on. Second, the ask section converts at rates a generic CTA cannot match because the request is specific to the work. Most weeks we get one to three real inbound replies on the ask alone. Third, the team's operating discipline tightens because writing the log forces a review of what actually shipped. The week you have nothing to put in the Shipped section is the week the team finds out they had no week.

The format that compounds

Six sections, same shape every Friday. The shape is the marketing. The content is the substance. Together they are a receipt that the team that publishes this every Friday is also the team that ships every Friday. Substitute either side and the artifact stops working.

The audience problem most agency marketing solves wrong

Most agency marketing tries to produce content that looks like work to people who never see the work. A shipping log is for people who only care about the work. The format reads as a side effect of operating discipline because it is. Buyers who care about the work convert. Buyers who do not, never would have converted on a hot take either. The audience is the entire point.

The framework: six sections, same shape every Friday

Shipped. What landed in production this week. One line per item, with a number where there is one. New flow live on a brand. New agent in production. New page deployed. If a line is vague, the work is vague.

Broke. What failed and how it got fixed. The week with no incidents is also a flag; you either deployed nothing or you missed something. Naming the break is a credibility transfer that hot takes cannot match.

Numbers. Three operating metrics, the same three every week. The repetition is the discipline. Changing the metrics weekly is how this section turns into vanity.

Learned. One thing we got wrong AND adjusted on. Concrete, not aspirational. "We learned that customers value clarity" is not learning; it is press release tone. "The voice scanner refused legitimate drafts because the prompt was missing the brand glossary; we added the glossary and refusals dropped to near zero" is learning.

Ahead. What is on next week's ship list. Brief, not a plan. Three to five items. Reading it next Friday against the actual Shipped section is its own form of accountability.

Ask. One specific request to the reader. Talent, intro, feedback, client. Single ask, max. The specificity is what converts. "Looking for great clients" does not convert. "Looking for an intro to the head of retention at a beauty brand past the 30 to 50K EUR per month band" converts.

Time to write: 30 minutes once the schema is muscle memory. The first four weeks take 60 to 90 minutes each because you are inventing the categories. After that the form does the work.

Runbook: shipping the weekly shipping log for the next quarter

1. Pick the day and time. Friday afternoon is the default because it forces the review of the week while the week is still legible. Monday morning loses the texture. Stick to one slot for an entire quarter before changing. 2. Write the schema once and stop touching it. Six sections, fixed names, fixed order. The schema is the contract with the reader. Changing it weekly is how this turns back into newsletter content. 3. Pick the three operating metrics. Same three every week. They have to be metrics the team actually optimises against. If they are not, you will quietly stop reporting them after week six. 4. Run it for four weeks before deciding anything. The first four are slow and ugly. The form is not yet muscle memory. Push through. If the team cannot fill the Shipped section three weeks in a row, the issue is not the format; it is the operating cadence the format is meant to surface. 5. Publish unedited substance. The bar is "would you tell a client this happened." If a sentence would not survive a Slack message to a senior peer who already knows your stack, cut it. 6. Track inbound replies on the Ask section as the conversion metric. Not opens, not clicks. The number that matters is real conversations started by a specific request. 7. After a quarter, audit. Is the Shipped section getting denser. Are inbound replies on the Ask section running one to three a week or higher. Is the team's operating cadence sharper than it was on day one. If yes, keep shipping. If no, the format is performing as marketing and not as discipline, and the fix is upstream. 8. Resist the urge to optimise for shares. The format is intentionally unshareable. The point is the operating cadence, not the post.

When this is wrong: failure modes and trade-offs

Two failure modes, both common.

The log gets written like a press release. Marketing tone, vague claims, no numbers. Readers leave inside the first line. The fix is to write it like a Slack message to a senior peer who already knows your stack. If a sentence would not survive that audience, cut it.

The log fills with vanity. Updated copy on a page nobody reads. A refactor that did not change a metric. A demo that did not ship. The fix is to keep one bar: would you tell a client this happened. If not, it is not in the log. The discipline is the marketing.

A third failure mode worth naming: the log becomes the marketing, then becomes the work. Teams that pick a format and run it weekly sometimes start optimising the format instead of the substance. The Shipped section gets padded. The Ask gets generic. The form stays intact and the work behind it rots. The hedge is the same one: would you tell a client this happened. If not, the system has flipped and the fix is to cut hard.

What success looks like

Run it for a quarter before deciding whether it works. If you cannot fill the Shipped section three weeks in a row, the issue is not the format; it is the operating cadence the format is meant to surface. The log is the symptom that tells you to fix the system underneath. That is its highest value: it is a diagnostic instrument disguised as marketing.

When the format is doing its job, three signals show up. Repeat readership grows on the schedule. Inbound replies on the Ask section run one to three a week. The team's operating discipline tightens because writing the log forces the review. The qualitative band is meaningful: a small audience of operators who actually convert beats a large audience of casual readers who never will. On services engagements past the 30 to 50K EUR per month threshold on /websites-cro, the shipping log is one of the cheapest credibility-transfer artifacts in the stack.

FAQ

How long does the weekly shipping log take to write? Thirty minutes once the schema is muscle memory. The first four weeks take 60 to 90 minutes each because you are inventing the categories. After that the form does the work.

What if I have nothing to put in the Shipped section? That is the diagnostic the format gives you. The log is the symptom; the operating cadence is the cause. The fix is upstream of the writing.

Should the log be on the company blog or a newsletter? Both, ideally. Permanent home on the blog because that is where the archive lives and where SEO compounds. Friday-afternoon push to the newsletter because that is where the cadence shows up in inboxes. Same content, two surfaces.

Why is the format intentionally unshareable? Optimising for shares is what turns the log back into hot-take content. The audience is the senior operator who is trying to figure out whether your team is real. That audience does not share. They read on schedule. The form follows the audience.

Does this work outside of agency or services businesses? Yes for any team with a buyer who cares about how the work gets done. SaaS engineering teams shipping changelogs hit the same dynamic. Productised consulting practices hit it. The cleanest fit is any business where the buyer is operationally minded and trust transfers through receipts, not pitches.

- https://www.arthea.ai/article/sent-them-the-codebase - https://www.arthea.ai/article/three-agents-shipped-meaningful-work - https://www.arthea.ai/ai-lab

If you want a 30-minute review of whether the weekly shipping log fits your team, the calendar is here: arthea.ai/book.

Go back to Blog

Download the ressource