Service pricing: cost helps set a boundary but does not explain value
Separate delivery cost, proposed price and customer value; define assumptions, alternatives and boundaries before publishing prices.
Article language: English

In this article
Suppose a sound studio is preparing a recorded conversation for publication. It can estimate editing, corrections and a final listen. The customer asks the price and the owner thinks: we know how long it takes. But what the owner actually knows is the effort expected on the studio's side. They have not yet established exactly what the customer is ordering or what alternative the customer will compare with the proposal.
The difference emerges when two different tasks accompany similar files. One is a company podcast episode with a fixed release date. The other is an archival interview not yet scheduled for publication. The producer's skill may be the same. The order conditions, significance of timing and work left to the customer will differ.
Three quantities not to hide in one amount
Delivery cost describes the resources the provider needs. Price is the amount proposed for a defined scope of cooperation. Value to the customer relates to what they find useful in their situation, compared with available alternatives and their own required effort. You cannot read it directly from the producer's hours.
In a 2015 study by Töytäri, Rajala and Brashear Alejandro, the authors distinguish pricing based on supplier cost, competitive prices and customer-perceived value. They studied five industrial firms moving toward services. Their account emphasises that perceived value depends on context of use and time; it does not provide a price list for Polish services.
In our example good sound alone may not complete the task. The podcast owner needs a file in the agreed format and at the agreed time to pass it on. An archivist may first need an assessment of what can be improved in the recording. The studio should recognise the difference before selecting one shared package rather than explaining it only after a discount request.
Do not attribute savings to the customer that they have not calculated or confirmed. “We will help you earn more” extends the promise far beyond editing. You can show the material delivered, how it will be accepted and the tasks it was prepared for. That supports a conversation about the work's significance without inventing its monetary effect for the recipient.
Cost needs a delivery scenario
Begin the internal work description with the conditions assumed for the effort estimate. Does the studio receive separate tracks or a finished mix? Has the client approved the selection of passages? Who checks proper names? If the estimate assumes a ready editing script but the material needs one created, the work has changed, not just the file length.
Include activities between the main stages: receiving material, questions, delivering versions and checking corrections. A template from earlier work is useful when its context is known. Do not transfer the time for the easiest recording to every future commission simply because each ends with an audio file. A file extension says remarkably little about the producer's work.
Business Queensland's pricing guide separates examination of own costs, competitor prices and target customers. For hourly pricing it notes business costs and available time, and for project pricing an agreed scope. This is general business guidance from Queensland's administration; we do not transfer Australian tax or legal rules from it.
Suppose the studio shortened technical editing with a better tool. It should determine which stage actually became faster and what still needs listening. Clicking export alone does not describe the whole job. The full cost of an AI process (in Polish) raises a similar issue: distinguish savings in one action from the effort needed to accept the result.
The owner can then decide how to use the change: arrange the package differently, devote time to checking or change the charging method. Shorter delivery alone does not decide whether or how the price should change. Nor is there a basis for presenting old effort to the client as work currently performed. The conversation should concern the current subject of the service.
The customer's alternative does not always have a competitor's price list
For an archival recording the alternative may be leaving the file as it is. For a podcast it might be simpler in-house editing, postponing the episode or choosing another studio. Each option raises different questions. Finding a similarly named item on a competitor's site is not enough to discover the right price for your own service.
Ask what the customer would do without the proposed work. If the answer is “nothing for now”, establish why the subject returned now. Perhaps a publication deadline, a new use or someone with time to work on the archive appeared. These are reasons to describe the commission, not permission to raise the amount arbitrarily because someone is in a hurry.
When comparing public offers, retain unit, scope and conditions. The price for an hour of recording may mean something different from an hour of a producer's work. A package may include content preparation or only editing specified passages. Also see what the customer must provide and who finishes preparing publication. Two identically named items can leave them with entirely different tasks.
An earlier decision about the unit in which a service is sold (in Polish) is especially useful. Are you selling a specialist's specified time, an accepted episode or continuous access to support? The chosen unit should not simultaneously pretend to guarantee the podcast's popularity. Each offer needs its own delivery boundary.
Who can confirm what the service means?
In the hypothetical studio, an editor sends the message and the owner of the company channel approves the commission. The editor wants fewer manual corrections. The owner needs to maintain the publication cycle. If the studio speaks only about voice quality, it may miss why the company is seeking help at all. That does not mean it should promise to run the channel. It should establish what further task its file must enable.

Show both people the same description of the proposed result. Ask what they will do after receiving it and what remains on their side. If the editor expects a ready publication while the owner orders editing alone, the revealed difference concerns scope. A more attractive amount will not resolve it. First agree the work both sides have in mind.
For an interview archive the significance may instead lie in preserving material for future use. The team does not yet know a release date, so do not add benefits from a timely premiere. The description can stay with what was actually agreed: preparing specified files for listening and further selection. That result has its own usefulness even if the client does not intend to publish all recordings now.
Sometimes defining scope first requires examining the material. Separate a standalone diagnosis before a project (in Polish) from preparing the offer itself. The client should know in advance whether they will receive an assessment of the recordings and possible directions or only questions the studio needs to make a proposal. Do not issue an invoice after a conversation for a stage nobody ordered.
The same craft, different risk
Return to the two files. For an episode with a release date, the client wants to know when a listening version will arrive and the deadline for corrections. For an archive, they may accept an order of work dependent on other tasks. Describe the agreed deadline, opportunity to listen and conditions for submitting corrections.
Also separate correcting a delivery error from changing a content decision. If the studio omitted an agreed cut, it returns to the approved scope. If, after listening, the client chooses a different episode structure, new work must be defined. Without that distinction, “corrections included” explains neither cost nor what the client actually buys.
Before sending a proposal, check what the provider controls. The studio can prepare a file against agreed criteria. It does not manage the client's whole campaign or listeners' decisions. The offer should allow its own work to be accepted and describe the expected downstream effect within the right scope. Evidence for B2B offer claims (in Polish) helps with this.
Do not treat uncertainty as one mandatory surcharge on every amount. First name what is unknown. Missing information about file quality may sometimes be clarified with a short sample. A missing agreed script needs a different decision. “Difficult material” does not tell the client what they can provide to make a proposal more precise.
When the three perspectives do not form an offer
The scope important to the customer may require work the studio cannot deliver on terms acceptable to both parties. Do not solve this by adding value to a presentation. See whether the task can change: prepare one episode instead of a series, separate content selection from editing or agree another deadline. The change must retain meaning for the recipient.
In another case a client expects full preparation but compares it with technical editing alone. Show the difference in work and result. Saying the competitor is less thorough is not enough. They may be correctly providing a narrower scope that the client actually needs. Recognising this helps make an honest proposal or end the conversation without inventing advantages.
When negotiating package conditions (in Polish), check what changes with the amount. If you remove a control listen, you cannot leave an unchanged description that includes it. If the client selects passages, they need to know how to provide them. A lower-priced proposal should still clearly describe its work.
Sometimes a company knowingly accepts different terms for a first job. Record the reason and boundary within your team. A one-off trial should not accidentally become a promise for the entire catalogue. The person conducting the next conversation must know whether they describe the current service model or repeat a special agreement from another order.
After several jobs, revisit the assumptions: what material was expected, what arrived and what work followed. Compare similar tasks. If every difference ends with “demanding client”, the description is too vague. Perhaps passage selection was missing, the approval point changed or the studio had not explained acceptance in advance.
Only now can price have a place on the page
Before publishing prices, establish who confirms scope and when to return to the estimate. An internal document may contain effort assumptions that do not need to be copied for the customer. The public description should explain the unit, contents of the proposal, required customer contribution and how cases differing from the standard are assessed.
This is a separate editorial task. A B2B service price list on a website (in Polish) helps decide how to show an approved amount or how it is determined. It does not replace the prior decision about scope and pricing logic. A form should not force a customer to guess which materials the studio considers prepared.
At Aeneia Design, an offer defined in this way can be translated into a clear page: variants, boundaries, needed information and contact. The starting point is the company's decisions about what it sells. Website design helps an audience understand them and ask the right question.
For the next enquiry the studio can ask for an excerpt, the goal and the way content is approved. It can then recognise whether it is preparing technical editing alone or broader work. Only then can it assign its own effort and a proposed price to that scope.










