A buyer asks for five edited posts. Before you name a price, find out whether the source is ready, who checks the claims, and whether 'one revision' means a consolidated response or feedback from several people. The output count has barely changed, but the work behind it may have doubled.
Build the quote in two parts: a private estimate of what delivery costs you, and a written scope the buyer can accept or change. The hypothetical nine-hour worksheet below shows the calculation; the package example shows how to negotiate less work without dropping the checks that make it usable. Neither is a market-rate survey or a promise of sales.
If you have not selected an offer yet, begin with 15 AI services you can sell without coding. If you still need proof of your ability, create an honest sample with the no-client portfolio guide before asking a buyer to trust a large project.
Separate your cost floor from the client's quote
Your cost floor answers 'Can I afford to deliver this?' The quote answers 'What will the buyer receive for this price?' Keep both visible in your planning, but do not confuse them. A sensible internal estimate can still describe a service the buyer does not need.
An AI drafting step is only part of delivery. Source preparation, editing, verification, client decisions, revision and handoff still consume time. Include the licensing, privacy and accessibility work the assignment actually needs, rather than assuming faster generation removes it.
Count working time, project costs, applicable fees, overhead and taxes without counting the same expense twice. Add a reasoned allowance for uncertainty. The result is your floor for this scope, not a universal rate or necessarily the final offer price.
Count the complete delivery workload:
- Prepare: intake, clarification, permissions, research, files and tool setup.
- Produce and check: generation, selection, editing, fact-checking, visual inspection, testing and accessibility review.
- Finish: meetings, updates, agreed revisions, exports, editable files, documentation and handoff.
- Cost separately: expected tool, asset, platform and payment charges, plus an explainable complexity allowance—not an arbitrary surcharge.
Seven pricing mistakes beginners can avoid
Copying another freelancer's rate
Their scope, proof, costs, location, client type, demand, and review standard may be completely different from yours.
Pricing only the generated output
A word count, image count, or prompt count ignores discovery, QA, communication, revisions, and accountability.
Offering an undefined revision promise
Unlimited changes can turn a small delivery into an open-ended engagement with no shared finish line.
Discounting before understanding the brief
A low number offered too early can become impossible once formats, stakeholders, source quality, and deadlines are known.
Ignoring fees and direct costs
Platform fees, payment processing, paid assets, transcription minutes, specialist review, and taxes can reduce the amount you keep.
Treating every client as the same risk
A well-prepared brief with one approver is not equivalent to a high-stakes project with missing data and several decision makers.
Using a low price to replace evidence
A clear sample, narrow scope, and reliable process create more trust than a price so low that careful review becomes impossible.
A lower introductory price can be a deliberate choice when your scope is smaller and you are learning the workflow. Make the reduced scope visible. Do not advertise a comprehensive service and quietly remove the review steps needed to deliver it safely.
Choose hourly, project-based, or package pricing
The pricing model should match how predictable the work is. Hourly billing is useful when the scope may change and the client is comfortable approving time. A fixed project fee works when the deliverable, assumptions, and finish line are clear. Packages work when you repeatedly solve the same narrow problem and can standardize the options.
Platforms implement these models differently. Upwork documents hourly and fixed-price contracts, with fixed-price work commonly organized around funded milestones. Fiverr documents packages that can specify inclusions, delivery details, and revisions. Review the current official platform rules before publishing an offer because availability, fees, limits, and protections can change.
| Model | Works best when | Main strength | Main risk | Scope control |
|---|---|---|---|---|
| Hourly | The work is exploratory, ongoing, advisory, or difficult to predict | The quote adapts as approved work expands | The client may focus on hours instead of outcomes; efficiency can reduce billable time | Set an estimated range, weekly limit, reporting method, and approval point for extra time |
| Project-based | The deliverables, inputs, timeline, and acceptance criteria are defined | The client sees one clear price for a result | Underestimating hidden work makes the project unprofitable | Write assumptions, exclusions, revision limits, milestones, and a change-request process |
| Package | You repeatedly deliver a standardized service to a recognizable client type | Buyers can compare scope without a long proposal | Vague tiers can confuse clients or invite the wrong order | Differentiate tiers by meaningful deliverables, depth, turnaround, and support |
If the buyer cannot yet supply an approved source or decide what the finished work is for, quote a small paid discovery phase rather than inventing a fixed production price. Once the inputs and finish line are clear, a project fee becomes easier to defend. For larger projects, reviewable milestones keep the next commitment tied to an accepted stage; repeatable work can later become a package.
Estimate the real work before choosing a number
Start by writing the workflow as if another freelancer had to perform it. Estimate each stage separately, using your own sample runs when possible. Do not use the best-case time from a perfect demonstration. Include waiting-independent work such as checking source files, correcting output, naming exports, documenting decisions, and incorporating feedback.
Your private sustainable hourly floor is a planning input, even if the client receives a project price. It can reflect the compensation you need for working time plus your share of business overhead. The exact calculation depends on your circumstances and local tax obligations. Keep it internal unless hourly billing is the chosen model.
A simple project floor is: estimated working hours multiplied by your sustainable hourly floor, plus direct costs, plus an explicit complexity or risk allowance. Then compare that floor with the importance of the outcome, available alternatives, your evidence, and the client's constraints. If the buyer's budget is below the floor, reduce scope or decline; do not silently remove essential QA.
| Work stage | Planning estimate | What to include |
|---|---|---|
| Discovery and setup | 1.0 hour | Brief review, questions, permissions, files, tools, and success criteria |
| Production and iteration | 3.0 hours | Drafting, generation, selection, editing, and client-specific decisions |
| Verification and QA | 2.0 hours | Facts, links, language, formatting, rights, accessibility, and final testing |
| Communication and handoff | 1.0 hour | Updates, delivery notes, exports, source files, and acceptance guidance |
| Revision allowance | 1.5 hours | One consolidated round within the original brief |
| Administration buffer | 0.5 hour | Scheduling, invoicing, archiving, and a modest estimate allowance |
| Estimated work total | 9.0 hours | Multiply by your private sustainable hourly floor, then add direct costs and a justified risk allowance |
Read the example as 9 × your private hourly floor, plus direct costs and any justified risk allowance. The administration line is already included in those nine hours; do not add it again as unseen extra time. If a new reviewer is expected to add two hours of meetings and reconciliation, the planning total becomes eleven hours before costs. That is illustrative arithmetic, not an observed project. Show the changed review scope to the buyer before doing the additional work.
Adjust the quote for scope, complexity, and risk
Two projects with the same visible deliverable can require very different effort. A five-page document made from approved copy and a brand template is not equivalent to a five-page document built from scattered notes, disputed claims, and unlicensed images. Ask enough questions to expose the difference before you quote.
Deliverables
List quantities, formats, dimensions, channels, editable files, source documentation, and what the client will receive at each stage.
Revision scope
Define the number of rounds, who consolidates feedback, the response window, and the difference between correcting your error and changing direction.
Complexity
Account for poor inputs, specialist vocabulary, multiple audiences, integrations, data cleanup, accessibility, and the number of decisions required.
Commercial usage
Clarify where and how the work will be used, which files or licenses transfer, and whether broader usage creates additional review or rights work.
Rush delivery
Charge for a compressed schedule only when you can meet it responsibly; consider displaced work, added coordination, and reduced recovery time for problems.
Stakeholders
More reviewers, meetings, approval layers, and contradictory feedback increase communication and revision effort.
Quality and risk
High-consequence claims, sensitive data, brand scrutiny, or specialist review may require more checks, a qualified collaborator, or a decision to decline.
Costs and fees
Include paid assets, tool usage, contractors, platform fees, payment processing, storage, and other project-specific expenses you actually expect.
For the illustrative post package, correcting a claim that contradicts the approved source is a delivery defect. Adjusting tone within that same brief can be an included revision. Asking for a new audience, source set or output format changes the assignment. Define those boundaries in writing and estimate added work before starting it; do not treat your own error as a paid extra.
Commercial usage does not automatically justify an arbitrary multiplier. It is a prompt to understand rights, reach, duration, exclusivity, source-file transfer, and the consequences of failure. Get appropriate professional advice when contracts or intellectual-property questions exceed your competence.
Value matters, but it must be discussed honestly. A client may value an accurate launch asset more than an internal draft because the consequences are different. You can ask what the output supports, what happens if it is late or wrong, and what approval standard applies. Do not invent return-on-investment claims or pretend your work guarantees sales.
Build Starter, Standard, and Premium packages
Use tiers only when the scope differences help a buyer choose. In the example below, a small single-channel test, a larger source-to-post package and a two-channel campaign require different work. They are possible offer designs, not products already sold by AIvelihood.
Every tier keeps source and quality checks. Change quantities, research depth, channels, turnaround, files or support to change the price. A cheaper package should be smaller, not deliberately unfinished.
For a complete source-to-output example, the AI content repurposing service guide shows how permission checks, source review, channel editing, fact checks, revisions, and handoff create the real workload behind a package.
| Package | Defined input | Core delivery | Review boundary | Best fit |
|---|---|---|---|---|
| Starter | One approved short source asset | Three edited posts for one channel plus a delivery note | One consolidated revision round | A client testing a small, clearly bounded workflow |
| Standard | One approved long-form source asset | Seven edited posts, messaging map, and a simple publishing sequence | Two consolidated revision rounds | A client who needs a complete single-channel campaign |
| Premium | Two approved source assets and a brand brief | Twelve edited posts across two specified channels, content calendar, and handoff guide | Two consolidated rounds plus one scheduled review call | A client coordinating a broader campaign with multiple outputs |
For every package, state:
- Exactly what the client supplies before the delivery clock begins.
- The quantity, format, channel, and editable-file policy for each deliverable.
- What research, strategy, meetings, scheduling, publishing, or implementation is excluded.
- Delivery timing and how delays in client materials or feedback affect it.
- The number and meaning of revision rounds, including the feedback deadline.
- Any optional extras, such as rush delivery or an additional format, with their scope and timing.
Fiverr's official package guidance treats revisions, delivery details, and upgrades as package elements. That is useful as a structure even if you sell elsewhere. Before publishing, use the freelance platform guide and verify the current rules, limits, fees, and protections of the channel you choose.
Communicate the quote so both sides understand it
Give the buyer enough detail to approve a job, not just a number: the output, necessary inputs, schedule, acceptance checks and revision boundary. Separate optional items so a smaller budget has an honest smaller alternative.
If the buyer cannot afford the two-channel example, offer one channel or fewer outputs and explain what no longer comes with it. A longer schedule or one consolidated feedback round may also change your estimate. Keep the required source checks. A discount with unchanged obligations leaves you carrying the same job for less money.
A clear proposal can follow this order:
- Objective: the problem and intended use of the finished work.
- Deliverables: quantities, formats, dimensions, files, and completion criteria.
- Inputs and assumptions: what the client provides and what the quote relies on.
- Process: major stages, review points, responsible AI use, and quality checks.
- Schedule: start condition, milestone dates, client feedback windows, and final delivery.
- Revisions: included rounds, feedback method, and examples of new scope.
- Price and payment: the total or rate, milestones, currency, taxes where applicable, and platform terms.
- Exclusions and next step: what is not included and how the client approves the work.
Raise your price from evidence, not impatience
Track estimated versus actual time for every stage, the number and cause of revisions, direct costs, questions that delayed work, and which deliverables clients valued. After several comparable projects, your records will show where the package is under-scoped or where your process has become more capable.
A higher quote can be justified by a clearer specialty, stronger proof, more reliable QA, improved communication, greater demand for limited capacity, broader rights, or a more complex outcome. It should not depend on pretending the AI tool is rare or hiding reduced effort. Efficiency supports margin only when the delivered standard remains strong.
Update future proposals when your evidence supports a change, give repeat clients reasonable notice, and honor accepted agreements. If a current project expands, use the agreed change process rather than retroactively changing its price.
- Compare estimated and actual hours by stage, not only the project total.
- Record direct costs, platform fees, revision time, and unpaid administration.
- Identify recurring client questions that should become intake fields or exclusions.
- Check whether every quality-control step still fits within the price.
- Review current platform policies and fees before updating a listing.
- Keep the old price for an already accepted scope unless both parties agree to a change.
A five-step pricing workflow
Use this sequence before publishing a package or sending a custom quote. The objective is a defensible scope and a sustainable delivery, not a universal perfect number.
- Step 1
Define the outcome and deliverables
Name the client problem, intended use, inputs, quantities, formats, completion criteria, and exclusions. If these are unknown, quote discovery first.
- Step 2
Map and estimate every work stage
Include discovery, preparation, AI-assisted production, human review, communication, revisions, exports, handoff, and administration using your own measured evidence.
- Step 3
Calculate the sustainable floor
Multiply estimated time by your private hourly floor, then add expected direct costs and a justified allowance for complexity or risk.
- Step 4
Check client value and alternatives
Consider the consequence, urgency, usage, proof you provide, and comparable ways the client could solve the problem without inventing ROI or market averages.
- Step 5
Write and confirm the scope
Present the price with assumptions, revisions, schedule, payment, and change rules. Begin only after both sides understand the same delivery.
Put one quote through these steps now. Mark an unknown input, an excluded task and the condition that would change the price. If the service itself is still unclear, return to the Start Here path; use the 30-day freelance roadmap when you are ready to test the offer, not as a promised income schedule.
Final pricing checklist
- The buyer can identify the deliverables, formats, quantities, intended use and acceptance checks.
- Your floor includes all work stages, review, revisions, fees and handoff; no expense is counted twice and no unsupported market average or result is promised.
- The pricing model, included revisions and change-request rule match the remaining uncertainty.
- Inputs, feedback windows, start conditions, rush options, extra formats and files are explicit.
- Current platform/payment terms, confidentiality, rights, licenses and commercial use have been checked where relevant.
- Any AI, data-handling or specialist-review limits are disclosed, with enough time and budget for the review that still needs to happen.
Official sources to recheck
- Upwork Help - How hourly and fixed-price contracts are different
- Upwork Help - Understanding milestones on fixed-price contracts
- Upwork Resource Center - How to estimate fixed-price projects
- Fiverr Help Center - What are packages?
- Fiverr Help Center - Managing Gig extras, source files, and shipping
- U.S. Small Business Administration - Break-even point guidance
Frequently asked questions
Should I charge hourly or per project for AI freelance work?
Use hourly pricing when the work is exploratory, ongoing, or difficult to predict. Use a project fee when the deliverables, assumptions, timeline, and acceptance criteria are clear. Packages are useful after a narrow workflow becomes repeatable. The best model is the one that makes the remaining uncertainty visible and manageable.
Should AI make my freelance service cheaper?
Not automatically. AI may reduce time in one step, but your quote still covers discovery, judgment, source preparation, quality control, communication, revisions, tools, and responsibility for the result. Efficiency can improve your margin or turnaround without removing the need for a sustainable price.
How do I set a price when I have no clients yet?
Run a complete concept project, measure each work stage, calculate a private cost floor, and keep the first paid scope narrow. Build a clearly labeled sample rather than inventing client experience. Your first price is a reasoned starting point that should be reviewed against real delivery data, not a guarantee of demand.
How many revisions should I include?
Include the number you can estimate and support for the service, often as one or more consolidated rounds rather than unlimited individual changes. Define a revision as a change within the approved brief. A new audience, strategy, source set, format, or deliverable should trigger a new estimate.
How should I price rush delivery?
First confirm that the deadline allows responsible work. Estimate the displaced capacity, extra coordination, schedule risk, and any added costs. Present rush delivery as an optional scoped add-on with a clear start condition. Decline it if the compressed timeline would undermine verification or quality.
Should I charge extra for commercial usage or source files?
Address them explicitly because broader usage, exclusivity, editable files, or asset licensing can change the work and rights involved. There is no universal multiplier. Describe what transfers, what remains licensed, and any added preparation. Seek qualified advice when the rights question exceeds your competence.
What if the client says my quote is too high?
Ask about the priority and budget, then offer a smaller legitimate scope: fewer deliverables, one channel, a longer schedule, or fewer feedback rounds. Do not quietly remove essential QA. If the client's required outcome cannot be delivered sustainably within the budget, decline respectfully.
How do I account for platform fees?
Check the current fee shown by the platform for the specific proposal, offer, or contract, because policies can change and fees may vary. Include expected fees in your internal net-income calculation while following platform rules. Do not rely on an old percentage copied from another freelancer.
When is it reasonable to raise my price?
Review prices when measured delivery time, costs, demand, specialization, proof, scope, or quality requirements change. Update new quotes and give repeat clients reasonable notice. Honor accepted agreements, and use a written change request if an active project's scope expands.