Why Wikipedia Engagements Don’t Fit an Hourly Model
One of the most common questions we receive from prospective clients is whether our Wikipedia work can be broken down into an hourly rate.
TL;DR
We use a resource-based methodology rather than an hourly billing model, aligning the level and type of resources with the demands of the engagement rather than a fixed allocation of time.
No two months in a Wikipedia engagement look the same. Some require lighter resource allocation, while others demand significantly more intensive effort.
We plan around this by budgeting for the resources required to achieve the client’s goals over time, rather than assigning fixed hours to individual months. These resources—both internal and external—are deployed based on the demands of the editing environment at any given stage.
As needs shift, we dynamically allocate and reallocate resources from the overall budget to ensure effort is applied where and when it has the greatest impact. This allows us to maintain momentum, respond to editorial developments, and stay aligned with the ultimate objective: a successful, policy-compliant outcome.
Wikipedia is not a traditional content platform, and managing a successful engagement requires a fundamentally different approach to time, resources, and outcomes. It’s a dynamic environment where costs and resources fluctuate from month to month.
The Reality of Wikipedia Work
Unlike standard consulting or content production, Wikipedia editing is not a linear process. Progress is influenced by a combination of internal effort and external factors, including:
- Independent editor review and scrutiny
- Notability and sourcing requirements
- Ongoing changes within the platform
- Editorial feedback cycles that are outside of anyone’s control
Because of this, the amount of time required to move an engagement forward can vary significantly from one phase—or even one month—to the next.
Why Hourly Billing Falls Short
Hourly billing assumes predictability. It suggests that effort can be forecasted in a straight line and that time spent directly correlates with results. In Wikipedia, that simply isn’t the case.
Two months within the same engagement can look completely different. For example:
- One month may be heavily focused on research, sourcing, and strategic positioning
- Another may require extensive back-and-forth with editors, revisions, and additional sourcing
- A third may involve minimal activity while awaiting editorial review, followed by a sudden need for concentrated effort
- We may need to find new editors, or manage push-back from third-party editors
We Use a Resource-Based Approach
Instead of billing by the hour, we structure our engagements around the resources required to responsibly and effectively manage the process.
This typically includes a combination of:
- Researchers to identify and validate independent sources
- Writers to develop neutral, policy-compliant content
- Editors to ensure alignment with Wikipedia standards
- Strategists to guide positioning and decision-making
- Project managers to coordinate workflow and timelines
The mix and intensity of these resources changes over time based on what the engagement requires at any given stage.
How Monthly Effort Can Vary
A key aspect of this model is flexibility. Different months require different levels of resources—sometimes more and sometimes less—depending on how the process unfolds.
For example:
- Early stages may require deeper research and strategic planning
- Mid-stage efforts often shift toward content development and submission
- Later phases may involve responding to editorial feedback or addressing challenges
- Some periods may require active intervention, while others involve monitoring and waiting for external actions
This variability is not inefficiency—it’s a direct reflection of how Wikipedia works.
Managing Toward Outcomes, Not Hours
Our model is designed around a simple principle: allocate the right resources at the right time to achieve the client’s goals.
Rather than tracking hours in isolation, we focus on:
- Advancing the engagement responsibly within Wikipedia’s guidelines
- Adapting to changes in the editorial environment
- Applying additional resources when challenges arise
- Reducing resource intensity when appropriate
This allows us to stay aligned with both the platform’s requirements and the client’s objectives—without being constrained by an artificial time structure.
The Bottom Line
Wikipedia engagements require adaptability, not rigid time tracking.
By structuring work around resources and outcomes instead of hourly inputs, we’re able to navigate the complexities of the platform more effectively—and deliver results that hold up over time.