Payment Rhythm Matters More Than Total Price: Designing Milestone Cash Flow for Outsourced Projects

Three Quotes Within 6% of Each Other, One Entire Project''s Worth of Risk Apart

A 60-person food trading company needed an inventory system plus a B2B ordering site: NT$850,000 over four months. Three quotes came in at 820K, 850K and 870K — a 6% spread. The payment terms read very differently: 50/50, 30/40/30, and five milestones. What matters is not the total price; it is what each payment buys you in independently verifiable terms. Here is what we see from the receiving end of the invoice, including the parts that do not flatter vendors.

Four Myths About Paying Vendors

Myth 1: The lower the deposit, the safer you are. A deposit under 20% means the vendor fronts four to six weeks of labour — so you get pushed to the back of the cash-flow queue, or an 8%–12% risk premium gets baked into the total.

Myth 2: Hold back 40% and the vendor will finish properly. Once the final payment exceeds 25%, the last 15% of hours is a net loss and senior people get moved to the next job.

Myth 3: Monthly payments are simpler. Time passes whether or not delivery happens; the delivery risk stays entirely with you.

Myth 4: Withholding payment until acceptance is maximum protection. With no acceptance deadline, withholding becomes open-ended and what slips is your launch date. Under Taiwan''s Civil Code provisions on contracts for work, remuneration is in principle due upon delivery (Civil Code Article 505).

The Core Framework: Four Rules for Milestone Cash Flow

Rule 1: Deposit = total price ÷ project months × 1.2. 850,000 ÷ 4 × 1.2 ≈ 255,000, roughly 30% — the vendor''s actual first-month labour cost.

Rule 2: No single milestone payment exceeds 25% of the total.

Rule 3: Every milestone is tied to an independently verifiable deliverable — not to a percentage or a date.

Rule 4: Final payment of 15%–20%, tied to 30 consecutive days live with zero P1 defects.

Milestone	Deliverable	Share	Amount (NT$)
M0 Kickoff	Frozen spec, DB schema, repo read access	25%	212,500
M1 Core	Inventory CRUD demoable on staging	20%	170,000
M2 Front end	B2B ordering flow + payment sandbox passing	20%	170,000
M3 UAT	Full feature set on staging, legacy data migrated	20%	170,000
M4 Stability	30 days live with no P1 defects	15%	127,500

Three Companies, Three Rhythms

A 20-person design studio, website rebuild, NT$180,000 over 6 weeks: five milestones would be a disaster — acceptance meetings alone eat 10% of the hours. Use two stages, 40/60, with the deposit tied to spec and wireframes.

A 300-person manufacturer, MES peripheral system, NT$3.2M over 10 months: monthly invoicing plus a 10% performance bond (NT$320,000) and a 5% retention released six months after go-live (ratios follow public-sector bond regulations).

The middle ground — NT$850,000 over four months — is the table above.

The Hidden Costs of Getting Payment Rhythm Wrong

Design error	Hidden cost
Deposit too low, schedule downgraded	3–6 week slip; PM chases status 4 extra hours a week: 6 × 4 × NT$800 = NT$19,200
More than 8 stages	10 stages × 2 hours × 6 people = 60 person-hours ≈ NT$48,000
Final payment above 30%	Wrap-up staffing downgraded; defect-fix cycles 2–3× longer
No acceptance deadline	A 21-day stall on average, costlier than the sum withheld
60-day payment terms	NT$170,000 per stage at 8% ≈ NT$2,240 per stage
Invoice timing out of sync	Business-tax filing-period disputes; issue on delivery (MOF E-Invoice Platform)

Payment Terms Scorecard (10 Dimensions)

Score each 0 (absent) / 1 (vague) / 2 (explicit):

Deposit between 20% and 35%
No single milestone payment above 25% of total
Every milestone has an independently verifiable deliverable
Acceptance deadline ≤10 working days, deemed accepted if missed
Final payment tied to a stability period
Change requests priced and paid separately
Invoice-to-payment ≤30 days
Termination clause settles completed work
Late-payment interest and stop-work rights reciprocal
IP transfer timing linked to payment

18+: sign. 13–17: fix the terms first. Below 12: change vendors.

Clauses You Can Paste Into a Contract

Acceptance: "Client shall complete acceptance and respond in writing within 10 working days of delivery. Written objections must itemise the specification clause not met and the concrete facts. Failure to respond constitutes deemed acceptance and entitles Vendor to invoice."
Final payment: "The final 15% is payable within 7 days after 30 consecutive days from go-live without a P1 defect. P1 means inability to complete a core transaction flow, or data corruption."
Reciprocal delay: "Either party in delay — of payment or of delivery — shall pay liquidated damages of 0.03% per day on that stage''s value, capped at 10%. If Client payment is more than 30 days overdue, Vendor may suspend work without liability."
IP and repository: "Source code shall be pushed continuously to Client''s designated repository from M0 onward, with Client holding read access. Economic copyright transfers to Client upon full payment."

How ScriptWalker Works, and What We Turn Down

Project uses the five milestones above; Retainer is prepaid monthly; Advisory is a prepaid hour block (20 hours minimum); Full outsourcing is quarterly prepaid with annual reconciliation.

Where we are the wrong fit, plainly:

Zero deposit with everything paid on completion — we cannot finance clients
Monthly terms of 90 days or more
Final payment above 30% with no acceptance deadline
Revenue-share instead of cash — we are a contractor, not an investor
Exploratory projects priced only after the work is done

Playbook: Two Weeks Before Signing to Day 90

Two weeks before signing: score the payment terms separately; below 13, fix the clauses first.
Month 1: M0 spec freeze, first payment, numbered change-request log.
Months 2–3: one 90-minute acceptance meeting per milestone, written conclusions within 3 working days.
Day 90: review change-request share, average milestone slip and invoice-to-cash days, then decide on a monthly retainer.

Decision Checklist

[ ] I can name the deliverable each payment buys
[ ] Deposit is 20%–35%
[ ] No single payment exceeds 25% of the total
[ ] Milestone count is 3–6
[ ] Acceptance deadline and the consequence of missing it are written
[ ] Final payment tied to a post-launch stability period
[ ] Change requests are priced separately
[ ] Settlement on termination is specified
[ ] Delay penalties are reciprocal
[ ] Source code reaches my repository from M0

Fewer than 8 ticked? Fix the contract before you sign.

FAQ

Can I pay no deposit at all and wait until the first milestone?

Yes, but the cost surfaces elsewhere: the vendor fronts four to six weeks of labour, then deprioritises your schedule or adds a risk premium. What protects you is tying the deposit to an independently verifiable deliverable.

Doesn''t a 40% holdback force the vendor to finish properly?

Usually it backfires. Above 25%, the final 15% of hours is a net loss and senior staff get reassigned. Use 15%–20%, tied to 30 consecutive days live without a P1 defect.

How many days should the acceptance window be?

Seven to ten working days, with deemed acceptance if no written objection is filed. Objections must map to specific specification clauses.

Want Your Contract Checked First?

Send us the payment terms on your desk and we will run them through the scorecard above. Thirty minutes, free, no pitch. Even if you go with someone else, the score is yours to keep.