Tacit work has no invoice line
I described a service I had shaped around one client's way of working and my partner heard a growth plan. The thing that would actually have to move is the part that has not once made it onto a quote.
partial specification
Meaning
A partial specification is an incomplete set of formal requirements or instructions for a product, service, or process. It describes a situation where the explicit terms, requirements, or instructions for a task, product, or service do not fully cover all necessary details for its complete execution. It outlines some elements precisely but leaves other aspects either vague, unstated, or implicitly assumed, requiring the performer to fill in the gaps using judgment, experience, or tacit knowledge.
This incompleteness can arise from complexity, an inability to foresee all variables, or a deliberate choice to allow flexibility. The existence of a partial specification means that successful completion relies on an unstated agreement or a shared understanding of what is not written down. It highlights the boundary between explicit instruction and implicit operational practice.
Ambiguity Source
A partial specification inherently creates a source of ambiguity within an arrangement, as what is explicitly stated might be clear, but the absence of detail in other areas opens the door to multiple interpretations or unknown requirements. This ambiguity forces the operator to make assumptions or frequently consult the founder for clarification, introducing potential delays, rework, or even client dissatisfaction if assumptions prove incorrect. For a founder, recognizing a partial specification means acknowledging precisely where the formal description of work ends and where reliance on tacit understanding or personal judgment begins, marking a critical point of potential miscommunication and operational risk.
Unwritten Expectation
The gaps in a partial specification are often filled by unwritten expectations held by the founder or the client. These expectations are not formally documented but are derived from previous interactions, industry norms, or a shared, implicit understanding of quality and scope. When a service is provided under a partial specification, the founder is expected to implicitly understand and deliver against these unwritten requirements, often without explicit confirmation.
This reliance on unspoken standards places a burden on the provider to correctly interpret and execute against implicit agreements, which can be a source of significant tension and unbilled effort if not managed carefully.
Founder Load
Operating under partial specifications places a substantial load on the founder, who must consistently bridge the gap between explicit instructions and the unstated requirements. This involves extra hours spent in interpretation, clarification, or personally completing the unspecified tasks to meet client expectations and uphold service quality. The founder bears the cost in terms of increased mental energy, capacity drain, and the inability to fully delegate work that requires their unique, uncodified judgment.
This load accumulates because the work that makes a partially specified service “complete” rarely has an invoice line, becoming a hidden subsidy from the founder’s own time and effort, ultimately limiting the scalability of the service. For instance, a client might request a “good report” without detailing format, depth, or preferred metrics, leaving the founder to intuit and produce the actual deliverable that will be deemed acceptable, a process that consumes significant cognitive resources.