THE RAW VERSION, IN THE ORDER I WROTE IT

What I wrote down beats what I concluded

I took notes as the sessions happened rather than writing a tidy retrospective afterwards, and the difference matters. A conclusion is smooth. Notes keep the moment you changed your mind, which is the useful part. My structured review is here.

Early: the mechanic

First thing I wrote: the one-word comment is not a gimmick, it is a distribution trick. The platform wants comments and does not want you sending people away. Asking for a word feeds the first and delays the second until the conversation is private.

Margin note, same page: "clever, and old enough to be proven". That second half matters to me more than novelty does.

Disclosure while we are early: affiliate links, I earn a commission, your price is unchanged.

Why the notes are more useful than the verdict

Because a verdict compresses everything into a number, and the number hides the reasoning.

What I wrote down beats what I concluded. You can disagree with my reasoning if you can see it. You cannot disagree with four stars.

So here is the rest of it, in order.

Middle: the tools, and the thing I questioned

The generator impressed me less as software and more as a briefing system. Its value is not the text it produces, which any model produces. It is the questions it asks before it writes, because those are the questions an experienced marketer would ask you and a blank prompt never does.

The thing I questioned, and wrote in capitals: HOW MUCH OF THE WORK IS ACTUALLY REMOVED?

My answer after watching: the drafting, most of it. The deciding and the publishing, none of it. If you buy expecting the second, you will be annoyed by week two, and that is on the expectation rather than on the product. I would rather set it here than let a refund set it later.

Next note: the 27 structures are not captions. Each one specifies the first line, what the image carries and which word the reader is asked to type. That last detail decides whether the automatic reply reads like a conversation, and it is the part free tutorials skip because explaining it is boring.

Late: the demo, and the number

The 60 Day Demo is the piece I would watch hardest. Starting from zero on a new phone, in front of a paying class, for sixty days, is a real risk and almost nobody in this market takes it.

The number, quoted as Mark said it: he tells members to aim at $337 a day, and he is explicit that figures like that illustrate the model rather than forecast anybody's result. Then, almost in passing, he said the hardest climb is to $100 a week. About $14 a day.

I underlined that. Small number hard, large number easier, which inverts how everybody sells this. It is also why the program is built around a first small week.

Where I landed, and what I would check

"Is it worth it?" At $2,497 once, saving $485 against six payments of $497 totalling $2,982, that is about $48 a week across a year. For an ordered eight weeks plus tools and a cohort, I think that is fair, and I would buy it again.

"Could I do it free?" Yes, over a quarter of evenings, with a wrong turn somewhere around week three. That is the expensive route wearing a free label.

"What if I have no time?" Twenty minutes, named. If you cannot name it, that answer applies to everything on this market, not just this.

"What if I am wrong about myself?" Thirty days, on an honest attempt, which turns month one into the test rather than the purchase.

Imagine week eight with a page live, forty posts out and a routine you no longer argue with. Now imagine week eight with a fourth folder and the same three drafts from week one.

Two things I would check in the first month

Both are answerable inside the guarantee, which is the point of having one.

First, whether the modules unlock on the schedule described. The portal opens week by week, and a program that slips its own timetable in month one is telling you something about month six. That is a fact you can observe rather than a claim you have to trust.

Second, whether the demo reports on a fixed cadence, including the weeks where nothing much happens. A demonstration that only publishes the good weeks is an advertisement with a calendar attached, and I would grade it accordingly.

Neither of those is knowable from outside, which is exactly why I treat the first thirty days as the real decision. The purchase is reversible. The month of finding out is the part that is worth something either way.

What I would do next

Thank you for reading a review with its working shown. You now have my reasoning rather than my score, which is the only part you can actually argue with.

You came to find out whether this is worth it, because you want something small that keeps going. That has not moved.

What notes cannot give you is the sequence itself, with the tools briefed to it and a group at the same stage as you.

If you want it, this is what I would do. Click a button on this page last, just before paying, because credit follows the final link. Then send your receipt over to [email protected] with the subject bonus request. I reply myself, usually the same day, and the first item I deliver is the page the method needs, built and live on your own domain.

The cart is scheduled to close 24 September 2026, 11:59pm Pacific, with the founding bonuses attached to that window by Mark's own terms rather than mine.

One note I nearly left out

Halfway through the second session I wrote: "the cohort is doing more work than anyone admits."

It sounds soft next to tools and templates. It is not. Week three is where the novelty has gone and the first posts have not worked yet, and that is the week people quietly stop. A group of strangers who started on the same day, at the same stage, posting through the same flat patch, is the only part of this you cannot assemble alone at any price.

I would not buy a program for a community tab. I would buy one for a cohort with a start date, because those are different things and only one of them still exists in November.

My structured review. What other reviews leave out.