How to Price Time Before You Price a Project

Pricing is often introduced as the moment a creator chooses a number. In practice, the first useful question comes earlier: what work is actually being requested? A project can look simple from its final form while containing research, preparation, correspondence, versioning, technical setup, delivery, and follow-up. Naming those stages does not produce a universal rate, and this article is not financial advice. It does make the conversation less dependent on guesswork.

Start by describing the requested outcome in ordinary language. Then list what must happen for that outcome to be responsibly delivered. The list is not a promise to charge for every minute in the same way; it is a map of where attention will go. It also helps distinguish a compact assignment from one that only appears compact because its open decisions have not yet been discussed.

Make the invisible stages visible

Separate the work into discovery, production, revision, and delivery. Discovery can include reading a brief, clarifying an audience, locating source material, or deciding whether the request needs a different format. Production is the visible draft, shoot, edit, design, or recording. Revision is not just changing a file; it includes interpreting feedback and checking whether a requested change alters the original goal. Delivery can include preparing files, publishing support, or a clean handoff.

For example, an imaginary request for a short editorial package may include a conversation to clarify the angle, an outline, a first draft, one agreed review window, and formatted files. If the request later adds a second audience, extra interviews, or several new formats, it is no longer the same map. The creator does not need to argue that the work is harder; they can point to the changed stages.

Use assumptions as part of the scope

Every estimate rests on assumptions. State them simply: the source materials will be supplied by a certain point; feedback will be consolidated; a named decision-maker will respond; the deliverable has a defined format. These are not legal terms and do not replace a contract or professional advice. They are working conditions that let both sides see what the initial discussion covers.

An assumption is especially helpful when a task has an unknown. Rather than silently absorbing it, mark it as a question: “research depth to be agreed,” or “translation support not included in this draft.” That phrasing is neither adversarial nor evasive. It gives a collaborator a clear place to confirm, narrow, or expand the request.

Price the shape, then revisit the change

Once the stages and assumptions are clear, a creator can decide how to discuss a total fee, a time-based estimate, or another arrangement appropriate to their circumstances. There is no single correct method. What matters is that the chosen approach reflects the shape of the project rather than only the most visible artifact.

If the scope changes, return to the map before continuing. A useful message might say that the new request introduces additional research and review work, and ask whether the timeline, deliverables, or budget conversation should change. This keeps the focus on the project rather than on personal defensiveness. Clear scoping cannot remove every ambiguity, but it can prevent a vague request from becoming an unlimited obligation.

Pricing time before pricing a project is ultimately a practice of attention. It makes creative labor easier to explain, protects room for judgment, and gives collaborators a shared description of what they are asking for.