Pricing Your Own Time: A Founder's Framework for Choosing Work Worth Doing
Most builders do not run out of ideas. They run out of hours, attention, and energy long before the ideas are exhausted. The real business lesson is not how to generate more opportunities but how to decide which ones deserve a share of a finite life. That decision is rarely made deliberately. It usually happens through drift: a request arrives, a shiny project appears, a friend asks for a favor, and months later the calendar reveals priorities that were never chosen. This article offers a framework for making the decision on purpose, drawing on general practices that founders, freelancers, and independent creators use when they want their effort to compound rather than scatter.
Start by Naming the Real Cost
Every yes is a no to something else. Before evaluating whether a project is good, estimate what it will displace. A two-week side project does not simply cost two weeks; it costs the follow-up work on your existing product, the draft you were writing, the conversations you meant to have with customers, and the recovery time afterward. Writing these displaced activities down next to the new commitment makes the trade visible.
A useful habit is to estimate the total hours rather than the headline hours. A project described as a few calls often includes preparation, follow-up, revisions, and context switching. Multiply your first estimate by a factor that reflects your own history of underestimating. Most people who track their past projects discover that their estimates are optimistic, and the correction is more valuable than any clever prioritization method.
Ask Whether the Work Compounds
Not all effort accumulates. Some work produces a one-time result that evaporates once the deliverable is shipped. Other work builds an asset: a reusable template, a documented process, an audience that returns, a relationship that opens future doors, or a body of knowledge you can apply again. When comparing options, ask which path leaves something behind that makes the next project easier.
Compounding work is not automatically superior, but it deserves a higher bar for interruptions. If a choice builds a system you will use for years, a modest short-term cost may be worth paying. If it produces a single deliverable with no reuse, the same cost deserves more scrutiny.
Question the Opportunity Before the Opportunity Questions You
Inbound opportunities feel urgent because someone is waiting. Urgency is not the same as importance. Build a short set of questions to put to each opportunity before you commit: What problem does this solve for me, specifically? Who benefits, and how will I know? What do I stop doing if I accept? What is the cheapest version of this I could test first? Would I still choose this if I were starting my week from scratch today?
The last question is especially useful. Many commitments are inherited from an earlier version of your goals. Asking whether you would choose the commitment fresh reveals which obligations are still aligned and which exist only because they were already in motion.
A Practical Checklist for Your Next Commitment
Use the following steps when a new project appears. First, write the estimated total hours and multiply by your personal correction factor. Second, list the two or three existing priorities this would displace. Third, label the work as one-time or compounding. Fourth, define one measurable signal that would tell you, within a set period, whether the project is working. Fifth, set a checkpoint date to review that signal and decide whether to continue, shrink, or stop.
The fifth step matters most. Many projects are never formally ended; they simply fade, consuming attention long after they stop producing value. A scheduled review turns an open-ended obligation into a decision you can actually revisit. Keep the review short, honest, and written down so you can compare what you expected with what happened.
Finally, revisit your portfolio of commitments every few months. Look at what you actually finished, what you started and abandoned, and which activities consumed time without producing learning. The pattern across several projects teaches more than any single outcome, and it gives your next decision better inputs than your enthusiasm alone can supply. For builders who publish their work openly, this kind of review can also become a useful public habit, since the reasoning behind choices is often more instructive to others than the results.