Pay for approved time inside a clear work boundary.
This can suit a changing queue when a manager can set priorities and review output. The proposal still needs hour limits, reporting, and approval rules.
Hourly pricing pays for recorded time. Fixed-fee pricing pays an agreed amount for a defined package, but either model can disappoint when scope, review, and change rules are missing.
These are planning definitions, not contract rules. The provider's written proposal and contract control the actual price, scope, and remedies.
A rate and a project price answer different questions. Start with the work, then choose the price structure that makes changes and proof easier to see.
This can suit a changing queue when a manager can set priorities and review output. The proposal still needs hour limits, reporting, and approval rules.
This can suit a bounded result when inputs and acceptance are clear before the quote. The proposal still needs exclusions, change rules, and review rounds.
Neither model wins every time. Use the written scope, change process, evidence, and buyer review load to judge each offer.
You pay for recorded time inside an agreed role or task boundary. The work can change without rewriting a full project scope, but priorities still need an owner.
You pay an agreed amount for a named result or work package. The deliverables, inputs, exclusions, and completion test need to be clear before pricing.
List included work, excluded work, required inputs, and the person who may change priorities or scope.
A new request usually uses more paid time. Ask whether the provider needs approval before hours move beyond the plan.
A request outside the written scope may become a change order. Ask how the provider prices and schedules a change before the extra work starts.
Define a change, the approval owner, the notice method, and the price or schedule effect.
Billing may stop when there is no approved work, or a minimum commitment may still apply. The proposal should say which rule applies.
Idle time may sit inside the fixed price when your team delays an input or decision. The contract may also allow schedule or price changes after a buyer-caused delay.
Ask what happens when the provider is waiting for access, files, feedback, or a business decision.
Time records show effort, but they do not prove that an output is ready. Add task-level checks for important or repeated work.
Acceptance rules decide whether the deliverable is complete. Vague words such as done or approved leave room for disputes.
Name the reviewer, test, evidence, correction window, and sign-off method for each important output.
Useful reports connect hours to tasks, output, blockers, and rework. A timesheet alone can hide why the work took longer.
Useful reports connect milestones to evidence, open decisions, risks, and acceptance status. Percent-complete figures need a visible basis.
Set the report fields, delivery day, owner, and escalation trigger before work starts.
Ongoing support may need longer access to work systems. Use named accounts, limited permissions, review dates, and a removal plan.
Project access may be shorter but broader during setup or delivery. Match permissions to each stage and remove them after the handoff.
List every account, permission level, access owner, review date, and removal event.
The invoice should connect billable time to approved work and the agreed rate. Record how rounding, minimum blocks, overtime, and tools are handled.
The invoice should connect charges to agreed milestones or accepted outputs. Record deposits, holdbacks, taxes, tools, and change orders separately.
Require enough detail to match each charge to the proposal, approved change, time record, or acceptance evidence.
Your manager may spend more time setting priorities and checking a changing queue. Include that internal time when you compare cost.
Your manager still supplies inputs, decisions, and acceptance. A fixed fee does not remove buyer-side review or delay risk.
Estimate manager hours as a range and name the decisions that cannot move to the provider.
Use the current scope and manager, not a perfect future process. Ask every provider to explain how the same situation affects hours, price, changes, and review.
Hourly pricing may fit when tasks repeat but volume changes and an internal owner can set priorities. Add a weekly hour range, a stop point, and a rule for work that needs approval.
Fixed-fee pricing may fit when the input set, finished output, review rounds, deadline, and acceptance test can be written down. Price discovery separately when the provider cannot inspect the work before quoting.
A fixed setup package can sit beside hourly support after launch. Keep the two scopes separate so setup acceptance, ongoing hours, access, and invoice evidence do not blur together.
Copy this question into the same email you send each provider. Save the answer beside the price so a low headline number does not hide different assumptions.
"Please confirm whether this quote bills for time or for an accepted work package. List the included work, required inputs, hour or scope limit, change approval, blocked-time rule, acceptance evidence, review rounds, tool charges, invoice detail, and what would increase the price."
A fixed fee can hide missing scope, while an hourly rate can hide manager time and rework. Record the same inputs and evidence for every offer before judging price.
No. A fixed fee can make a defined package easier to budget, but unclear inputs, changes, or review rounds can add cost. Compare the same work and the same time period before choosing.
No. Agencies and managed providers may also bill by time, capacity, or a monthly hour commitment. The proposal should name the staffing, supervision, and output rules behind the rate.
Yes. A provider might charge a fixed fee for setup and hourly rates for ongoing changes or support. Use separate scopes, approval rules, access dates, and invoice lines for each part.
Ask for the rate, billing increment, minimum commitment, planned hours, approval limit, role scope, reporting fields, and tool costs. Also ask how the provider records blocked time and rework.
Ask for deliverables, assumptions, dependencies, exclusions, review rounds, acceptance tests, milestones, change rules, and handoff items. A price without those terms is hard to compare.
These federal procurement pages show how one formal buying system separates fixed-price and time-based contracts. Private outsourcing proposals can use the same labels differently, so the written provider terms still control.
Use OutsourcedU to write the role, SOPs, onboarding steps, and weekly review before you hire more people.