How to protect time for a product while delivering client work

Build your first expertise product inside a defined work budget. Start with the client commitments you must deliver, the operations that keep the business running, and the time you intend to keep for yourself. Give the product a specific share of what remains, then reduce its scope until research, production, review, and an initial release all fit.

This is a planning exercise for an established author who still earns income from consulting. It does not assume you should leave consulting, work every evening, or replace that income on a fixed timetable. Your first aim is to learn whether readers can use and value one paid application of your method without making promises your calendar cannot support.

A consulting appointment occupies more than its meeting slot. Preparation, analysis, delivery, revisions, and follow-up also need time. Your book business may already require newsletter writing, interviews, reader correspondence, and speaking preparation. Those obligations belong in the same capacity calculation.

Look at a recent ordinary week and a recent difficult one. Record actual time approximately; precision to the minute is unnecessary. The useful discovery is whether a supposedly free afternoon was already consumed by finishing a client report and answering readers.

Separate movable work from commitments. An optional redesign can wait. A delivery date you have already agreed with a client needs a different conversation. A product schedule that quietly depends on missing that date is not a viable schedule.

Also distinguish hours from attention. A spare thirty minutes may suit checking links. It may not suit deciding which parts of a chapter belong in a reader workflow. Put demanding work where you have a realistic chance of doing it well.

Consultant and builder Moe Hachem describes the problem candidly: “the correct intention and the wrong energy”. His account concerns developing his own software alongside consulting and family life; it is a personal experience, not evidence for a universal schedule. It is nevertheless a useful check on plans that treat every evening as interchangeable production time. Hachem's original build log.

Choose a work ceiling you intend to maintain. Then subtract existing obligations and a reserve for uncertainty. The reserve is not automatically available for adding features. It protects the plan when something takes longer than expected.

Consider a fictional author, Owen, whose book teaches small museums how to improve exhibition labels. He consults with museums and wants to test a paid companion that helps a reader prepare one label revision brief. It will not rewrite an entire exhibition or provide Owen's personal editorial approval.

Owen chooses a 32-hour workweek for this four-week experiment. The numbers below are invented planning assumptions, not recommended working hours or productivity benchmarks.

The product receives 24 hours across four weeks. That does not mean a finished commercial product can necessarily be built in 24 hours. It means Owen has authorized a 24-hour experiment, after which he must decide what the evidence and remaining work justify.

If you cannot identify even a small credible allocation, change an existing commitment, delay the experiment, or narrow it to discovery. Do not solve a capacity shortfall by writing a more ambitious task list.

Owen's first idea includes a companion for every chapter, a library of exhibition examples, several audience modes, and optional personal feedback. None of that follows automatically from the reader's immediate need.

He reduces the experiment to one outcome: a museum worker can prepare a revision brief for a single label, identifying its audience, intended point, missing context, and constraints. The worker still checks facts, makes the editorial decision, and follows the museum's approval process.

That boundary makes the calendar meaningful. Owen can develop one complete example, examine where readers misunderstand it, and decide whether the experience is useful. He does not need to build all possible applications of his book before learning anything.

Write the excluded work beside the outcome. In this example, whole-exhibition strategy, historical fact checking, translation, and personalized approval are excluded. These are scope choices for a fictional pilot, not claims about what any platform can or cannot do.

The worksheet assigns all 24 product hours. Substitute your own estimates and leave room to change the decision when the work reveals something new.

Discovery includes examining reader questions and arranging suitable conversations. Production includes the material needed for the chosen outcome. Review includes your own checks and readers attempting the task. Release preparation includes explaining the offer and its limits, not merely announcing a link.

The work need not occur in neat weekly stages. If week-one conversations reveal that readers lack essential source material, Owen may spend week two investigating that obstacle instead. The table is a budget and a decision aid, not an instruction to ship regardless of what happens.

For the actual quality checks, use a separate agent skill testing process. This schedule reserves time for testing; it does not replace it.

Turn the six-hour allowance into blocks that fit the work. Owen might reserve two two-hour production sessions and two one-hour research or review sessions. A reader conversation may require moving a block, but moving it should be visible.

Before each session, name its finish condition: “complete the worked label example” is clearer than “work on the product.” End by recording the next unresolved decision. That small handoff makes a short later session easier to use.

Jason Cohen recommends treating an internal product as a client: “The product is listed as a client just like all the rest.” His essay addresses consulting companies and contains older financial assumptions that are not used here. The quoted scheduling principle is useful for a solo author too: give your product an explicit allocation instead of relying on a future quiet period. Cohen's original essay.

Protecting the allocation does not mean ignoring client emergencies. It means recording the tradeoff when an emergency consumes it. Otherwise you may believe the product received a fair trial when it actually received two distracted hours.

Suppose Owen's third week needs five extra hours of agreed client work. His three-hour reserve absorbs three. He must find the remaining two hours by reducing or moving other work. If he uses two product hours, the experiment now has 22 available hours unless he deliberately changes a later allocation.

He should not erase two hours of review and still call the product ready. A better choice might be to move the invitation date, remove an optional example, or end the month with a prototype and a clear next research question.

Set this decision rule in advance:

If available time falls, reduce optional breadth or move the date before removing checks needed to make the promised outcome dependable.

The rule protects the reader as well as your schedule. A narrow, reviewed experience is easier to describe honestly than an ambitious offer whose critical assumptions have never been examined.

Avoid counting a postponed session twice. If Thursday's product block becomes client delivery, next week's calendar must show where the replacement block comes from. It cannot be both recovered development time and ordinary free capacity.

Review planned hours, actual hours, completed work, and what readers could accomplish. Ask whether the next investment is justified by the problem you observed. A useful experiment may produce a narrower product, a revised audience, or a decision to pause.

Also estimate the recurring work the offer would create. Selling a product with weekly personal reviews changes next month's capacity even if this month's production fits perfectly. Reserve ongoing support and maintenance before accepting commitments to buyers.

If the experiment is ready for a limited paid test, define the number of participants, included help, and review date. If it is not, describe the remaining uncertainty plainly. Finishing a four-week calendar is not the same as demonstrating that an offer works.

To explore a paid companion that fits around your existing author business, visit Skillfully and choose Book onboarding. Bring one reader outcome and the time you can realistically commit. Those constraints help shape a useful first offer.