Build a Service People Can Trust

A service is a promise about work another person will receive. “I offer creative solutions” may sound attractive but leaves a buyer guessing what is included. Start with the buyer's problem and an output you can actually deliver. Name the format, quantity, deadline, inputs you need and the point at which the work is considered complete.

Use a fictional writing service: one 300-word event description, one revision round and delivery as an editable document within three working days after the client supplies verified event details. The client can see what they are buying. The provider can estimate the work. “Unlimited changes until you love it” creates an uncertain obligation and an unclear endpoint.

Write exclusions alongside inclusions. The fictional service does not include event photography, legal review, translation or a promise of attendance. Exclusions should not conceal an essential part of the service. If a client reasonably expects a necessary step, explain who supplies it and when. Otherwise the offer may be technically narrow while practically unusable.

Choose an acceptance check. The description contains the supplied date, venue, purpose, booking method and agreed tone; the document opens and is editable; the revision request is addressed. That check gives both parties a shared way to evaluate delivery. If the work requires regulated professional competence you do not hold, change the offer or involve an appropriately qualified provider rather than using a confident label.

A price is not the same as earnings. Begin with a simple model: payment received minus costs directly caused by the job equals contribution before overheads, tax and other obligations. Count the time needed for briefing, production, revision, communication and handoff. Work that happens outside the visible deliverable still uses capacity.

In a fictional example, a job brings in R600. Direct cash costs are R80. The contribution before overheads and tax is R520. If the whole job takes four hours, that contribution is R130 per hour before overheads and tax. This is a planning figure, not a wage or take-home amount. It tells you whether the offer deserves a closer look.

Now test a difficult case. If two extra revision rounds add three hours, the same contribution is about R74.29 per hour across seven hours. The price did not change, but the workload did. Clear scope and an agreed change process protect the service from quietly becoming a different job. Do not hide foreseeable charges; show the buyer how a scope change will be quoted before it is performed.

Keep tax and statutory questions outside this beginner calculation. Do not infer registration, VAT treatment or deductibility from the example. Before charging real customers, confirm the actual legal entity, payment account, applicable obligations and operating costs. The exercise is to recognise uncertainty and make it visible, not to guess it away.

Reliable delivery starts before payment. Confirm the buyer's brief and the information needed to begin. Check that the provider has the skill, time and permission to do the work. Use the correct legal entity and payment account. A payment confirmation is evidence of a transaction; it is not evidence that the promised service has been delivered.

Build a short workflow: accept the agreed brief, record the order reference, confirm verified payment where payment is required, assign an owner, prepare the output, check it, deliver it and record acceptance or a correction request. Each step needs a person responsible and a piece of evidence. “Someone will handle it” is not an assignment.

For the fictional writing job, evidence might include the agreed event brief, the order reference, a dated draft, a completed quality checklist and the client's delivery acknowledgment. Record only information needed to operate the job. Keep the working document and messages private. Do not use a client deliverable as a public portfolio item without permission.

Plan the failure path. If a promised input is missing, tell the buyer what is missing and how it affects the schedule. If delivery will be late, communicate the revised date before the deadline where possible. If the output fails the acceptance check, record the correction rather than marking the job complete. A usable service includes a response to problems, not only a successful path.

Expansion multiplies both capability and unresolved problems. Before adding another offer, review whether the current one can be delivered consistently. Track a small set of measures: jobs accepted, jobs delivered on time, corrections requested, time used and contribution before overheads and tax. The measures should help you make a decision, not decorate a dashboard.

Create a fictional three-job review. One job was delivered on time, one was late because the brief was incomplete and one needed a correction because the booking link was wrong. The useful response is not a general promise to work harder. It is a revised intake check for complete information and a quality check that opens every link before delivery.

Use a simple incident note: what happened, who was affected, what immediate correction was made and what process change could prevent recurrence. Separate a buyer's dissatisfaction from an unsupported accusation about them. Preserve evidence, acknowledge the part you can establish and offer a response within the agreed service terms. Refund and complaint decisions must follow applicable obligations and the real agreement; this course does not set those terms for you.

Your final output is an operating card: the offer, capacity limit, owner, intake checklist, cost model, delivery evidence, correction route and review cadence. Run a desk simulation before accepting a real customer. If a simulation reveals a missing provider, licence, payment route or essential resource, treat it as a launch blocker rather than a future detail.