9 min readBy

The 28-Day Gameplan: Your First Month

A week-by-week plan for the first month of a new web design agency, borrowing the phased, decision-point shape of NovraScale's own published method. No client, launch, or number promised by day 28: only what to decide, build, and start each week.

A first month is not a forecast. It is four weeks of decisions and actions. Each week closes before the next opens. Nothing below promises a client, a launch, or a number by day twenty-eight. It describes what to decide, register, build, and start reaching out with. The order gets the founding work done before the selling work starts. It leaves room to change course each week.

The shape of the plan, and where it comes from

NovraScale runs its own client engagements on a phased, 28-day method. It is published in full at our own method page. Five phases. Each one ends in a decision. Real work lands inside week one, rather than saved for a reveal at the end. This gameplan borrows that shape for a different problem: building the thing that earns a client, rather than onboarding one already signed:

  • Every week ends with something decided or built, not something promised.
  • The heaviest founding work happens first. That means structure, registration, and tools. It happens before a single outreach message goes out.
  • Outreach starts in week three, not week one, once there is a real site to point to.
  • The plan changes based on what weeks one and two actually produce. A rigid script that ignores that is worse than no plan.

The reason for a decision point at the end of each week is the same reason NovraScale runs its own engagements that way. A month with no checkpoint lets a bad week three go unnoticed. It might not surface until week six, when it is expensive to unwind. A month broken into four closed weeks surfaces a bad week while it is still one week, not three.

Week 1: decide the foundation, and register it

Four decisions and one piece of paperwork, in order:

  • The structure question comes first, and this page does not answer it. Sole proprietorship, single-member LLC and the S-corp election are the forms new agencies most often look at. See how web agencies are commonly structured for what each one actually changes, and for the questions worth taking to an attorney. That post describes the options. It answers none of them for any particular reader, and neither does this one.
  • Decide what you will build with. Price the baseline first. See what it actually costs before subscribing to anything.
  • An EIN is the federal tax number a business bank account or a payroll filing usually asks for. The IRS issues one online, in a single session, at no cost: “If it’s approved, we’ll issue your EIN immediately online.” The IRS is explicit that no legitimate site charges a fee for one. The session cannot be saved partway through. It expires after fifteen minutes of inactivity. Whether a particular business needs one, and when, is a question for the IRS’s own guidance or an accountant.
  • Buy the domain, and nothing else yet. A site that does not exist yet does not need hosting billed before it is built.

This is not legal or tax advice. NovraScale does not form your company and does not advise on entity selection. Talk to an attorney licensed in your state. Week one names the decisions and points at where each one is described. It makes none of them.

Nothing in week one requires a finished name. A working name, bought this week and changed in month three, costs a domain and a redirect. A structure decision changed in month three costs a re-filing. A pricing structure decided mid-negotiation, with an actual prospect, costs the negotiation itself. Spend the week’s attention on the decisions that are expensive to revisit. The name is not one of them.

Week 2: build the proof, and set the price structure

Two things a founder can build in a week that a client cannot yet see. One decision shapes every project after it:

The site built this week has one job. It should let a stranger judge the work, without asking you anything first. That is a different bar than “looks finished.” A single real page, built the way you would build a client’s, clears that bar. A template with the logo swapped does not. It demonstrates the template, not you.

Week 3: start reaching out

The channels below are described in full elsewhere. This week is about starting, not perfecting:

  • Start with the list that already trusts you. Widen from there. See where new web agencies actually find clients for the full channel list, and how to tell one is not working before it costs a month.
  • If any of it happens by email, three floor requirements apply. They apply from the first message, not the tenth. They apply whether the recipient is a person or a business. The CAN-SPAM Act requires “clear and conspicuous identification that the message is an advertisement or solicitation,” unless the recipient already agreed to receive it. It also requires a valid physical postal address for the sender. It requires an opt-out request honored within ten business days of receiving it.
  • Track what is reaching a real person, versus what is going nowhere. Do not judge a channel on one quiet week. Do not judge it as working on one busy week either.

A week is not enough time to know whether a channel works. It is enough time to know whether it is reaching anyone. That is a different, earlier question. Keep the two separate. A channel reaching people and producing silence is a message problem. A channel reaching nobody at all is a list problem. Fixing the wrong one wastes week four as well.

Week 4: write the process down, and review

The work that keeps month two from repeating month one’s mistakes:

  • Write down a simple intake process. Decide what you ask a prospect before quoting. Decide what a deposit covers. Decide how a change in scope gets handled once a project is underway. What terms of that kind generally do, and what contract law calls them, is described in the pricing post. Settle your own version before you are negotiating it live, for the first time, with a client waiting on an answer.
  • Review what actually happened, not what was supposed to happen. Which channel produced a real conversation? Which piece of the setup took longer than planned? What would you skip doing again?
  • Decide what continues into month two. Decide what gets dropped. None of the above requires a signed client by the end of month one to be worth doing again.

What changes if a week runs long

Some week will run long. That is not a sign the plan failed:

  • If week one runs long, the structure decision or the EIN application is what usually stalls it. Neither has to finish before week two’s build starts. Move on, and close the paperwork in parallel.
  • If week two runs long, the instinct is to keep polishing the site. Set a stopping point before you start. The site is done when a stranger can judge it. It is not done when you can no longer find anything to change.
  • If week three produces silence, that is information. It is not a verdict on the whole plan. Widen the channel before abandoning the week. Do not compress weeks one and two of the next month to make up the time.

What this plan does not promise

None of the four weeks above end in a guaranteed result. That is deliberate. A specific outcome, by a specific day, is not a plan. It is a forecast dressed as one, and this page is not in a position to make it. What happens after week four depends on the market you are in and the work you do. It does not depend on the calendar.

This is a plan, not a forecast. What it can promise: four decisions get made, and something real gets built, by the end of each week. What that produces afterward is not written here. Nobody publishing this page knows your market well enough to write it honestly.

Sources