The fkra blog
Product thinking · 10 min

What can you build with six hours a week?

A small service, a useful publication, a first workshop. The harder question is how much of next week each one will need.

Listen to this article

11:59
0:00

AI may have been used to generate this audio.

Press Space or K to play or pause, and J or L to go back or forward 15 seconds.

Sources checked 17 October 2026. All project schedules and time budgets are worked examples, not measured results or earnings forecasts.

There are ninety minutes free on Tuesday, another ninety on Thursday, and three hours on Saturday. You have a job, a few things you would like to make, and no intention of turning every evening into a second shift.

Six hours sounds like enough until you write down what the project involves. Someone has to make the thing. Someone has to find the people who might want it, explain it, answer their questions and fix the part that confused them. For now, all of those people are you.

In four weeks, the calendar offers twenty-four hours. That can accommodate a modest experiment if you already have the relevant skill and can reach a few potential users. It might produce a first customer, two useful editions of a newsletter, or a workshop that reveals what people actually struggle with. It might also tell you to stop.

There is no research finding that makes six hours the correct amount. It is a constraint worth taking seriously. What would you choose to build if the seventh hour were unavailable?

Spend the hours before you promise the result

Ali Abdaal’s advice for people starting businesses alongside a job includes reserving specific blocks for the new work. Justin Welsh begins his weekly review by asking what he can remove, then what he can simplify. These are useful practices from creators running businesses; neither establishes how much a beginner can accomplish in six hours. [1][2]

Try a provisional week with three hours for producing the work, ninety minutes for conversations and finding customers, thirty minutes for administration, and an hour left uncommitted. That last hour can absorb a revision, a late start or a task you underestimated. Sometimes it stays unused.

This leaves half the week for making. A project that needs six hours of production already exceeds the budget once it has readers or customers.

Six hours split into four kinds of work

Illustrative time-flow diagram. Ribbon widths show planned minutes on a common scale. The limit stays at 360 minutes; an overrun is shown explicitly.

The proportions should change with the project. Before anyone has agreed to a pilot, making a sample and arranging conversations may be the whole job. During delivery, a customer’s work takes more of the week. Keeping the total visible helps you notice when a new commitment displaces an old one.

Count the small jobs too. The ten-minute reply on Wednesday and the half-hour call on Friday belong in the same budget. If a six-hour project regularly uses ten hours, the extra four need to appear somewhere you can see them.

Your starting point also matters. An experienced editor can offer a small editing service much sooner than someone learning to edit. A person with an existing professional network can arrange conversations more easily than someone without those connections. A spare six hours does not make those differences disappear. In the first month, learning a necessary skill or finding access to a customer may be the entire project.

Give each session a piece it can finish

Three hours on Saturday can hold a different kind of work from six scattered half-hours. Drafting a lesson needs time to decide what belongs in it. Confirming three appointments can fit between other commitments.

Research by Gabriela Tonietto, Selin Malkoc and Stephen Nowlis helps explain one difficulty with short windows. Across eight studies, time before a scheduled task felt shorter than otherwise comparable unbounded time. People were less likely to start extended tasks that could still fit. Making a task easier to divide into smaller parts reduced the effect. This was research on time perception and use, not a trial of side businesses. [3]

For a ninety-minute evening, “work on the workshop” leaves too much to decide. “Write the exercise and try it with one person” gives the session an endpoint. If only thirty minutes survive a busy day, the exercise can become “write the opening question and the sample answer.”

Zoom until the task fits

Illustrative task sizing, not measured completion times. No fixed switching penalty or optimal session length is assumed.

Use the largest reliable block for work that needs sustained attention. Put replies, scheduling and collecting materials into shorter windows. Reliable matters here. Three hours you can use most Saturdays may be more useful for planning than an impressive morning routine that depends on nobody else in the house needing anything.

Three projects small enough to test

Consider a menu-editing service for independent cafés. You already know how to write clear Arabic and English descriptions. The first offer covers one menu, a short briefing, suggested wording and one revision. It has a defined end, which makes it possible to estimate the work and tell the owner what they will receive.

In a delivery week, three hours might cover reading the brief, editing the menu and walking the owner through the changes. Ninety minutes go to finding the next potential customer, thirty to messages and invoicing, with one hour available for overruns. These are starting estimates. If the first menu takes five hours, record that before offering the same scope again.

The pilot should answer whether owners want this particular help and whether you can deliver it within the promised scope. A request for menu photography, social posts and ongoing promotion is a request for a larger service. You can price and schedule it separately, or decline it. Quietly absorbing it makes the next week harder to plan.

A newsletter presents a different problem. Suppose you want to help parents find free or inexpensive weekend activities in one city. A first edition could contain five checked listings, with dates, booking requirements and age ranges. Checking matters: an attractive list with an expired registration link has failed at its main job.

Try two editions over the first month, sent to people who have agreed to receive them. Ask whether they used a listing, what was missing, and whether they want the next edition. Compliments alone will tell you little about the research burden or whether the newsletter is useful in practice. A reader who points out that every event is across the city has given you something specific to change.

The production promise deserves attention before the subscriber count. If two editions already consume the available hours, a daily newsletter is a different project. Advertising, paid tiers and a community each add work that the first schedule has not funded.

The third option is a live workshop on a skill you already use: photographing products with a phone, preparing for a job interview, or giving useful feedback on a draft. Pick one result a participant can practise during the session. For a product-photography workshop, that could be taking one better-lit photograph using a window, a table and an ordinary phone.

Spend the early sessions talking to a few intended participants and testing the exercise. Run one small workshop before recording a course. Watch where people hesitate. Someone who follows the instructions and still gets a dark photograph has exposed a teaching problem you can work on. A polished introduction video would not have revealed it.

Write the promise before adding features

Original worked examples. A trial may fail to attract participants or customers; that is information to review.

These examples assume existing competence and a reachable audience. They are deliberately narrow, and each has a visible result outside your own task list. A hobby can use a different measure: a finished essay, a repaired chair, six drawings. It does not need a customer to justify the hours. Decide what the project is for before borrowing a business’s measures of success.

Make the first month answer a question

For the menu service, a sensible first month might begin with conversations, move to one pilot, then use the remaining time to review the actual workload and try the revised offer. The weeks may slip if nobody is available. Waiting time is part of the experiment, even when it does not consume working hours.

Write down the question before you spend the month. For example: “Will a café owner agree to a paid trial of a clearly scoped menu edit?” Beside it, record what you offered, who you approached, what they said and what happened next. A refusal over price suggests a different next step from an owner who sees no problem with the menu.

A month in four scenes

An illustrative four-week sequence, up to 24 working hours. No reply or no customer is also a result; the dates can move.

There is research behind taking tests seriously, although it cannot validate this four-week schedule. A 2024 paper by Arnaldo Camuffo and colleagues reported four randomized trials involving 759 firms. Training entrepreneurs to formulate and test hypotheses increased the termination of ideas and affected how they changed strategy. The study supports treating abandonment as a possible result of better decision-making. It does not show that a few interviews predict a business’s success. [4]

Choose a review date and a modest decision you can actually make. You might continue with the same offer, narrow it after discovering an expensive revision step, or pause because you cannot reach the people you hoped to serve. Keep observations separate from explanations. “Nobody replied to eight messages” is an observation. “Nobody wants this service” is one possible explanation, alongside poor timing, the wrong recipients or an unclear message.

This is also why endlessly changing the idea after each conversation is unhelpful. You need enough consistency to learn what a response refers to. A month of five unrelated offers is difficult to interpret, even if it felt busy.

A successful project starts spending next week

The first customer creates delivery work. A newsletter creates a next edition. A workshop creates questions, cancellations and requests for another date. Some of this is welcome. It still needs time.

Imagine that, after a few pilots, each regular client needs an hour a week, including replies and revisions. Keep one hour for administration and one for unexpected work. With two clients, two hours remain for improving the service or finding new business. With four clients, those two hours have disappeared. With five, the plan exceeds six hours before any improvement work begins.

What does the next client cost in time?

Arithmetic model, not business performance data. Remaining minutes = 360 − 60 admin − 60 buffer − clients × minutes per client. Negative values mean the plan exceeds six hours.

The model is intentionally simple. Real clients do not all need the same time, and selling the next engagement is not always separate from delivering the current one. Its purpose is to make the recurring obligation visible before you accept it.

You can respond by limiting the number of customers, reducing the scope, lengthening the delivery window, or putting more time into the business by choice. Raising a price may change the economics, but it does not remove a promised hour of work. Hiring help also requires money, explanation and review; it should earn a place in the budget rather than appear as a frictionless escape from it.

For a publication, the equivalent decision might be fortnightly rather than weekly delivery. For a workshop, it might be one scheduled session a month, with questions answered during that session. The promise you make determines much of the work that follows.

When Tuesday disappears

Eventually an ordinary week will interrupt the plan. A late meeting, a sick child or a repair at home takes the evening you had reserved. Moving all the lost work into Saturday may be possible once. Repeating it changes the agreement you made with yourself and anyone who shares your time.

Tuesday disappears. What moves?

Worked example. Losing Tuesday removes 90 minutes. The revised plan keeps 180 minutes of delivery, 30 of admin and 60 uncommitted; outreach is deferred, not silently added to the evening.

Give the project a smaller version of the week. If a customer is already waiting, protect the agreed delivery and postpone outreach or improvements. If you have made no commitment, keep one short session to record the next action and move the experiment’s review date. A missed evening need not become a debt to the following evening.

After four weeks, compare the calendar with what actually happened. How much time went into delivery? What did readers or customers do? Which task kept growing? Would you willingly repeat the resulting week?

Then book the next session with its actual job attached. “Tuesday, 8:00–9:30: revise the café’s six unclear descriptions and send the agreed draft.” Leave the untested extras off the calendar until that fits.

Sources

50
127 views
ProductivityProduct discoveryStartupsDecision makingEvidence
Mosab Alrasheed
Get the next entry

One email when we publish. Research, product decisions, and what teams report back.

Now playingWhat can you build with six hours a week?