A milestone without a deliverable is just a date

A milestone is supposed to mark a piece of finished work. In too many contracts it marks a date instead. The invoice arrives, the client pays and nothing has actually been tested against a written standard. That gap between calendar and criteria is where budgets quietly leak.

You have probably signed one of these schedules without noticing. Payment one on kickoff, payment two after design, payment three after development, payment four on launch. Each payment sounds like progress. But if nobody wrote down what "design" or "development" must contain to count as finished, the milestone is measuring elapsed weeks, not delivered value.

What a deliverable actually needs

A deliverable needs a test you can apply without asking the person who built it what they meant. A component library is not a deliverable. "Twelve components matching the approved design file, each responsive at three breakpoints and checked against the brand guide" is a deliverable. The first description invites an argument about whether the work is done. The second settles it before it starts.

Write these tests before signing, not after the invoice lands. Ask what evidence proves the milestone happened: a staging link, a test report, a signed design file, a list of pages that load without error. If nobody can name that evidence in advance, the milestone is not a checkpoint. It is a countdown.

Why this matters more on a fixed price

At Yunaris we work at a fixed price, so milestones carry more weight for us than they do for studios billing by the hour. An hourly studio can absorb a vague milestone because every hour still gets paid regardless. A fixed price studio cannot, because the whole point of the arrangement is that the total is agreed before work starts. If the milestones inside that total are vague, the fixed price stops protecting either side of the agreement.

This is why every milestone in a Yunaris agreement is tied to something you can look at and check off: a working staging environment, a completed page, a form that submits and stores data correctly. You know what you are paying for at each stage, not only when you are paying for it.

If you are reviewing a proposal from any studio, ask one question before you sign. For each milestone, what document, link or test proves it is complete. If the answer is a shrug or a date on a calendar, you are not buying software. You are buying time, and time without a deliverable attached to it can stretch in ways that never quite reach the finish line.