Your First Thirty Days

Your First Thirty Days

Everything in this course compresses into one month of specific actions. The plan assumes roughly two hours a day; double the days if you have one, and adjust nothing else. Follow it as written the first time. The parts that feel skippable, the list, the follow-ups, the review notes, are the parts that produce the results.

Days 1 through 7: position and proof

Lock the lane and the client type using the lane lesson's filters, and write your one-sentence position. Install and configure your stack per the gear lesson, backup ritual included, and pick your primary editor. Then build the three portfolio samples: the before-and-after transformation, the style-match re-edit, and the finished-feeling package. Host them on the simple page and put the link in every profile you own.

Success check at day seven: a stranger could watch your three samples and state, in one sentence, what you do and for whom. If they could not, the samples are unspecific, not the sentence.

Days 8 through 14: the list and the first batch

Build the forty-name list with the three columns from the outreach lesson. Then cut and send the first batch of three free samples. Track every touch in the tracker worksheet: sent date, reply, next action. Send a second batch of three the same week. The volume feels small. It is deliberate: three excellent, specific samples outperform thirty generic ones, and you can sustain excellent at three.

Set up the marketplace profile in parallel, bio aimed at your exact client type, three gig packages with fixed scopes, your portfolio link at the top.

Days 15 through 21: convert and diagnose

The follow-ups from batch one and two go out at day five per prospect. Replies turn into short conversations and paid test projects, quoted per the sales lesson, small, full price, deposit taken. Meanwhile batches three and four go out. Yes, outreach continues while you deliver: the real-week lesson made Friday pipeline time a permanent habit, and this is why.

Day twenty-one is the honest checkpoint. The diagnosis table reads like this.

| Symptom by day 21 | Most likely cause | The fix | |---|---|---| | Sent 12+ samples, zero replies | Samples generic or targets wrong | Sharpen the observation in each message; re-check that every target publishes continuously in your lane | | Replies but no calls | The ask is buried or the clip missed | Lead with the clip, end with one clear line: "want a batch like this weekly?" | | Calls but no paid tests | Price fumbled or scope vague | Practice the test-project script aloud; quote, then silence | | Tests delivered, no retainers | Delivery or communication gap | Ask the client directly what held them back; fix that one thing |

Zero revenue at day twenty-one with the volume done is a fixable diagnosis, not a verdict. The editors who make it share one behavior with the editors who do not, and it is this table: they read the symptom, applied the fix, and sent the next batch.

Days 22 through 30: systematize and compound

Turn whatever worked into machinery. Your best outreach message becomes the template. Your test-project delivery gets the onboarding treatment: contract, invoice, review link, delivery date. Every finished client gets two sentences and one ask: "Loved working on this; if anyone in your space needs an editor, an intro means a lot." Referrals from happy clients are the cheapest pipeline you will ever have, and most editors never ask.

Close the month with the numbers in front of you: samples sent, reply rate, tests run, revenue, hours spent. That ratio, revenue over hours, is the business's true north, and every later decision, raising rates, taking a subcontractor, dropping a client, is made against it.

Thirty days in, you will know this business from the inside, whatever the scoreboard says.