Hello — I’m the Harborfield Assistant. I can explain Harborfield, compare reports, or help you find a relevant starting point. Final product access is determined separately through eligibility.
Loading
Preparing the requested page…
Loading
Preparing the requested page…
Hello — I’m the Harborfield Assistant. I can explain Harborfield, compare reports, or help you find a relevant starting point. Final product access is determined separately through eligibility.
InsightsPricing
Pricing decisions are difficult partly because several different questions are often compressed into one:
What should I charge?
That wording suggests a single correct number exists and research only needs to discover it.
For many solo services, a more defensible approach is to build several pricing scenarios, document their assumptions, and compare the operational consequences.
A pricing recommendation implies that a particular number deserves preference.
A pricing scenario asks:
What changes if the assumed price is X rather than Y?
That distinction matters because price is connected to other variables:
A solo editor might, for example, compare hypothetical project prices of $400, $600, and $800.
Those values do not mean customers will pay them.
They are analytical inputs.
Pricing becomes difficult to analyze when the underlying unit is unstable.
Define:
A “website package” is difficult to compare when one provider includes five pages and another includes 20.
An “editing project” is equally difficult to compare when word count, editing depth, and correction structure differ materially.
Before comparing prices, compare units.
The professional supplies values they want to examine.
For example:
These should remain explicitly labeled as customer or analytical assumptions.
When enough reasonably comparable public prices exist, scenarios can be informed by their observed distribution.
A comparison might examine lower-quartile, median, and upper-quartile values from a qualifying sample.
This requires caution.
A percentile calculated from poorly comparable services creates numerical precision without analytical quality.
Before combining public prices, ask:
If many answers are no, list the observations individually and preserve their limitations.
Three scenarios are often enough to make trade-offs visible without suggesting false precision.
For each scenario, record:
Consider a simple capacity example.
A designer estimates that a defined service requires 10 delivery hours and that 80 hours per month are available for client delivery.
The deterministic capacity formula is:
monthly unit capacity = floor(available delivery hours / hours per service unit)
Using those assumptions:
80 / 10 = 8 service units of theoretical monthly delivery capacity.
That does not mean eight projects will be sold or completed.
It only describes the workload capacity implied by the stated time assumptions.
Different pricing scenarios can then be compared against the same eight-unit capacity without turning the exercise into a projected monthly revenue or earnings example.
A price can look reasonable in isolation while being attached to an impractical delivery model.
Another scenario may sit higher than many public observations but correspond to a deeper or more time-intensive scope.
The decision is therefore rarely just about the number.
It involves the relationship among:
| Variable | Scenario A | Scenario B | Scenario C |
|---|---|---|---|
| Assumed price | |||
| Delivery hours per unit | |||
| Monthly delivery hours available | |||
| Unit capacity | |||
| Public-price comparison | |||
| Main assumption | |||
| Main workload implication | |||
| Main trade-off |
This format makes uncertainty visible.
If delivery time is highly uncertain, the capacity conclusion should be treated as correspondingly uncertain.
A disciplined pricing analysis might state:
Evidence
Assumptions
Unknowns
The model remains useful because those distinctions are visible.
Statements such as these deserve skepticism:
“The market price is $950.”
“You should charge 20% more.”
“This is the optimal package.”
“Customers in this market will pay $1,500.”
Public pricing research generally does not establish those conclusions.
More defensible language is comparative:
Pricing analysis does not need to discover one correct price.
It should make the implications of different assumptions easier to examine.
That requires:
A pricing decision can then be treated as a structured trade-off rather than a guess presented as certainty.
The Solo Practice Positioning & Pricing Analysis uses validated assumptions and public reference observations to compare pricing and workload scenarios. Scenario figures are planning inputs; the analysis does not turn them into promises about customer volume, future billing, profit, or business performance.