What Ten Hours a Week Actually Buys You in Six Months

Ten hours a week for six months is about 260 hours. That number is worth sitting with, because most people building on the side either wildly overestimate it or dismiss it as not being serious.

Both are wrong. 260 focused hours is not enough to build a scaled company. It is comfortably enough to find out whether you should.

What 260 hours cannot buy

Set the expectation properly first.

It will not build a polished product with a real design system, a mobile app, and an admin panel. It will not get you to meaningful revenue in most B2B categories, where sales cycles alone eat months. It will not let you out-execute a funded team of six working full time in the same market.

If your plan requires any of those inside six months, the plan is wrong, not your schedule.

What it reliably buys

Across a six month stretch, 260 hours is enough to produce all of the following, in this order:

A problem you can prove other people have. Fifteen to twenty real conversations at roughly forty minutes each, including scheduling and notes, is around 25 hours. That is under 10 percent of your budget and it is the highest-return spend available to you.

A working thing in front of real users. Not a product. A narrow, ugly, functioning slice that does one job. For most software ideas, 80 to 120 hours gets there if the scope is genuinely narrow.

Your first paying customer. Not a pilot, not a friend doing you a favour. Money moving from someone who owes you nothing. This is the single milestone that separates a project from a company.

A pricing decision you can defend. Made from what people actually agreed to pay, not from a competitor's website.

A clear go or no-go. Which is the real deliverable. The purpose of six months is to replace an opinion with evidence.

Where the hours actually go

A rough allocation that survives contact with reality:

• Customer conversations and synthesis: 40 hours
• Building the first usable version: 100 hours
• Getting it in front of people and watching them use it: 40 hours
• Selling, following up, closing: 50 hours
• Admin, incorporation, tooling, paperwork: 30 hours

Notice that building is under 40 percent. Almost everyone building on the side inverts this and spends 200 hours coding, because coding is the part that feels like progress and does not involve being told no.

Consistency beats intensity

Two people both put in 260 hours. One does ten hours every week for six months. The other does nothing for three weeks then 40 hours in a heroic weekend sprint.

The first person finishes far ahead, and it is not close.

Momentum compounds through other people. Customer conversations lead to introductions, which lead to more conversations, but only if you keep showing up while those threads are warm. A three week gap kills every thread you had open. You restart cold each time, and re-reading your own notes to remember where you were is pure overhead.

Six focused hours every week beats fifteen erratic ones. Protect the floor, not the ceiling.

The three things that waste the budget

Building before talking. The most expensive mistake available. Forty hours of building the wrong thing is 15 percent of your total, gone, and you usually cannot tell it is gone until much later.

Perfecting things nobody sees. The landing page redesign, the logo, the fourth CI refactor. This work is comfortable precisely because it cannot be rejected. That is the tell.

The research spiral. Reading about your market, watching founder interviews, filling a Notion doc. This feels like preparation and it is consumption. If a week produced no artefact and no conversation, it produced nothing.

A realistic week

What ten hours looks like when it works:

• Two weekday evenings, ninety minutes each: building or writing. Three hours.
• Two customer calls at 8pm or during a lunch break. Ninety minutes with notes.
• One weekend block of three to four hours: the harder thinking that needs uninterrupted time.
• Thirty minutes on a Sunday: what did I learn, what is next week's one outcome.

That last thirty minutes is the one people skip and the one that keeps the other 9.5 hours pointed somewhere.

The honest test

At the end of six months you will have one of two things.

A company with real customers, a defensible reason to exist, and enough evidence to decide what happens next.

Or a clear, well-earned no, arrived at in six months instead of three years, at a cost of 260 hours and nothing else.

The second outcome is not the failure case. Spending four more years half-wondering is the failure case.

Six months, ten hours a week, deliverables a mentor actually reviews, is precisely the shape of LVL1 Startup School.