How many hours a week do you need to start a business?

The short answer

About ten focused hours a week is enough to launch a first version of most software or service businesses within a month or two, provided the hours go into launch-critical tasks: talking to customers, building the smallest sellable version, and putting it in public. Forty scattered hours lose to ten aimed ones.

The question usually hides a different one: 'can I do this without quitting my job?' For a first version of most businesses, yes. Plenty of real companies started as ten focused hours a week, and the graveyard is full of full-time founders who spent forty hours a week on logo revisions.

Where the hours have to go

The constraint is not the total; it is the allocation. Launch-critical work is a short list: conversations with potential customers, the smallest version someone can actually use or buy, and distribution experiments that put it in front of strangers. Everything else, including the company name, the perfect stack, and the incorporation question, is postponable. A useful weekly split for ten hours: four building, three talking to potential customers, two on distribution, one reviewing what happened and planning the next week.

The trap of unfocused hours

Hours without a forcing function leak into research and rearranging. This is why a dated plan matters more than a bigger time budget: when Tuesday's two hours have one named task with a deadline, the hours compound. GRILLR builds its 4-week plans around the hours you actually have, which it asks about during intake precisely so the plan survives contact with your real calendar, and then grades what you ship in those hours PASS or FAIL.

The full playbook for evenings-and-weekends founders, including how to protect the hours from your own employer and your own Netflix account, is in how to build a startup while working full time.