Illustrative scenario: after you send a proposal, the client asks to pay per deliverable because that schedule fits its budget process. Before revising the quote, clarify whether the buyer wants a narrower scope, a different price basis, or a new payment schedule. Each choice changes a different part of the agreement: a fixed-fee project can use milestone payments, a retainer can define separately priced change orders, and repeatable deliverables can be grouped into a single request. The commercial structure allocates risk; the schedule sets when each amount becomes payable.
The key distinction
The pricing structure defines the work and its price. The billing schedule defines when payment becomes due.
- Fixed-fee project: One price for a bounded scope, with payment at delivery or through an agreed deposit and milestones. Main risks include estimation error and scope expansion.
- Per-deliverable: A price for each clearly defined unit, billed individually or in consolidated requests. Main risks include commoditization and administrative overhead.
- Retainer: A recurring fee for defined ongoing scope or reserved capacity, billed by recurring invoice or subscription. Main risks include scope creep and perceived underuse.
Milestones structure payment timing within a fixed-fee project, implementation, or another bounded engagement.
Fixed project price: clarity in exchange for estimation risk
A fixed project price gives the client one commercial commitment for a defined result. In B2B work, that makes the budget visible before work begins. The designer’s main exposure is estimating the effort accurately.
When the scope is bounded and delivery is efficient, the effective rate improves. If discovery reveals a larger problem than the brief described, the fixed price can compress margin quickly. Exclusions, revision limits, acceptance criteria, and a working change-order process keep new work visible and route it into a separate commercial decision.
A fixed price becomes difficult to manage when the scope remains open. For a brand identity engagement, define deliverable families, revision rounds, decision-makers, and the change process before the project starts. The agreement and scope document establish those boundaries; the invoice follows them.
Milestones: align payment dates with project checkpoints
A $12,000 identity project can use a fixed fee and three $4,000 milestones. The fee sets the total commitment; each milestone ties a portion of that amount to a payment date or agreed checkpoint. Staging can improve cash flow, reduce the balance due at the end of a long project, and connect payments to visible progress.
“Client approves concepts” is too vague. A usable checkpoint is closer to: “The client selects one of three presented directions or requests one consolidated revision round within the agreed review window.” The acceptance rule belongs in the agreement; the payment request simply follows once the checkpoint is completed. A milestone should answer five questions:
- What work is complete?
- What counts as acceptance?
- Who has authority to approve it?
- What happens when revisions are requested?
- When does that completed checkpoint become billable?
On Ruul, a conservative implementation is a sequence of one-off Payment Requests, with one request for each agreed checkpoint. The current beta Ruul contract generator offers on-delivery, a 30% upfront deposit, or milestone terms, with an option to invoice through Ruul. Define each checkpoint and amount in the agreement, then confirm how invoice timing will work in the current invoice creation flow. Use one-off requests for agreed checkpoints unless Ruul confirms an automated milestone workflow for the account.
The generator offers a 30% upfront option. Define its due date and how it applies to project start in the agreement, then align the invoice details with Ruul.
Per-deliverable pricing: useful when the unit is genuinely repeatable
This model fits repeatable units such as social asset sets, templated collateral, or standardized report graphics, where both parties agree on what each unit includes. The client can see the priced output; the designer should also account for the judgment and coordination behind it so the unit price reflects the work.
Full identity work is usually easier to price around a defined scope than a catalog of units. Check current Ruul transaction limits in the dashboard and support documentation before splitting a project into smaller requests.
For small units, consolidate payment requests when the buyer agrees and the workflow allows it. Each additional transaction adds reconciliation and administrative work, and may increase payment-method or failed-payment handling. Ruul says invoice and payout currencies can differ, with conversion at real-time rates and no separate foreign-exchange fee; confirm the displayed amounts before sending.
Retainer: recurring revenue built around reserved capacity
A retainer provides recurring revenue in exchange for defined ongoing scope or reserved capacity. For the client, it makes creative support a standing capability with a planned fee and service boundary.
Heavy usage can erode margin when the fee stays fixed; low usage can weaken renewal when the client perceives too little value in reserved access. Ruul supports more than one recurring mechanism.
Scheduled recurring Payment Requests generate monthly invoices for the client to settle manually. A subscription charges the client’s saved card automatically after approval; it can run weekly or monthly, and each period produces its own invoice. The subscription flow is card-only. Ruul explains scheduled invoices and subscription billing.
These mechanisms reduce repeated invoicing work. The agreement still defines the price, scope, and renewal case.
Choose a Ruul workflow for each commercial structure
- Fixed-fee project: Send a one-off Payment Request when payment is due. Ruul documents the request workflow; align timing with the agreement.
- Fixed fee with milestones: Send sequential one-off Payment Requests after the agreed checkpoints. This applies the documented request workflow to a milestone plan set in the agreement.
- Per-deliverable: Send one request per unit or consolidate several units when that suits the scope and current transaction limits.
- Retainer with recurring invoices: Schedule recurring Payment Requests; the client settles each request under its terms.
- Retainer with automatic card billing: Use a client-confirmed subscription on a weekly or monthly cycle. Subscription auto-pay is card-only.
Check Ruul’s current pricing page before calculating transaction costs.
Ruul’s current pricing page lists a 5% transaction commission, plus optional fees for crypto payouts and Early Pay. For ordinary Payment Requests, the professional chooses whether to pay the commission or pass it to the client. Subscription commission applies each period; Ruul says a card-processing fee may also appear at checkout. Review the displayed totals before quoting and distinguish optional services from the base commission.
Hybrid structures worth considering
Commercial structures can combine several pricing and payment choices. A brand identity project can use a fixed price with staged Payment Requests, then move to a separate retainer if the client develops an ongoing need. The agreement defines deliverables, acceptance, payment timing, and treatment of unused capacity; the platform processes the requests.
The commercial decision comes first
Choose the model that fits the work, approval process, and risk tolerance. Define scope, milestone acceptance, and recurring capacity in the agreement; use Ruul to issue and track requests.
