Eight Weeks to Launch. Six Months to Money.
Eight weeks at ten hours a week is a real build schedule. It produces a launched business, not an earning one, and confusing the two is why people quit.
Justin Allan, NP3 min read

Yes. Ten hours a week, eight weeks, and you can have this built and live while holding down a full professional workload.
That is a real number and it stands. What it does not tell you is what those eighty hours actually buy — which is not what most people hear, and the gap between the two is where this gets abandoned.
What eight weeks actually produces
A built business. Not an earning one.
At the end of it you have a product somebody can buy, a site they can buy it from, enough content that the site is not empty, and the machinery to take money. That is a genuine achievement and most people never get there.
What you do not have is customers, because nobody knows you exist yet. Expect three to six months after launch before anything resembling consistent revenue turns up — that is the normal shape, and it is the point at which most course businesses are abandoned, usually by people who did the build correctly.
So hold both numbers. Eight weeks to launch. Something like six months after that before the business starts paying you. Anyone quoting you only the first number is selling you something.
The build order
Roughly how I would spend the eighty hours, in this sequence, because the sequence matters more than the hours.
Value proposition first, and do not rush it. Which specific problem, for which specific people inside your profession. Everything downstream is built on this and changing it later means redoing the rest.
Then the flagship course. This is the bulk of the eighty hours and it should be. Build the product before anything public exists.
Then twelve pieces of content, written before you launch. This is the step everybody skips and the one I would defend hardest. Twelve articles or videos is roughly two months of publishing at a sustainable cadence, which means you launch with a buffer instead of launching and immediately falling behind. It also means somebody who arrives on day one finds a site with substance on it rather than a sales page and a promise.
Then the site, with the copy written by you. Not by a developer — nobody else can explain what you are proposing. Anyone landing on it should understand who it is for and what problem it solves within seconds.
Then the infrastructure. Entity, hosting platform, email, payment processing. Deliberately last among the build steps, because it feels productive while producing nothing.
Then start trickling ads. A few hundred dollars behind one thing, a few hundred behind another, and watch what happens. You are buying information at this stage, not customers.
Notes on doing this around a job
Do not go public before you have something to sell. The temptation is to start publishing early to build an audience while you finish the course. It backfires — people are impulsive and short of attention, and an audience gathered around nothing disperses before you have anything to offer it. Build the product, then open the doors.
Ten hours means ten hours. Not ten hours of having the tab open. In practice this is two weekday evenings and a weekend morning, and it survives only if it is scheduled like a shift.
Protect the content cadence above everything else. After launch, the single thing that will break first is publishing, because it is the only recurring commitment with no immediate consequence for missing it. That twelve-piece buffer exists precisely to absorb the week your actual job explodes.
Expect nothing to happen for a while, visibly. You will publish things that get no response at all. That is not evidence of anything. Some weeks land, most do not, and the only variable you control is whether you were still publishing when one did.
The eight-week trap
Here is the failure I would most like you to avoid.
Somebody hits the eight-week target, launches, sells three courses to people they know, and then watches four quiet months. They conclude the model does not work, or that their profession is different, or that they are not the kind of person this works for.
What actually happened is that they finished the build phase on schedule and then measured themselves against a revenue expectation that belonged to month nine. The eight weeks was not wrong. It was just the wrong finish line.
Plan for eight weeks of building and then six months of publishing, marketing and waiting, and the same result feels completely different — because at month four you are not failing, you are on schedule.