Amounts are distributed proportionally. Example values, fully adjustable.
01Concept & estimate
500 €
Technical concept, acceptance criteria agreed.
Deadline: after 4 days
02Implementation
2.000 €
Feature on staging, tests passing, code review possible.
Deadline: after 14 days
03Deployment
500 €
Feature live in production, documentation in the repository.
Deadline: after 18 days
Total 3.000 €approx. 18 days · Review time 72 hours
Join the waitlist →How to avoid disputes
Write acceptance criteria like tests
Word each criterion so a tester could tick it off: "A user with role X can do Y and sees Z." Everything verifiable with a yes or no, everything subjective ("fast", "nice") gets cut.
Clarify access before starting
Repository, staging, deployment: missing access is the most common cause of delay. Clarify it before starting and agree that the deadline pauses while access is missing.
Approve on staging, not live
Get approval on staging, not in production. Production environments have too many side effects from caches, migrations and third-party services. The deployment milestone takes care of the rest.
Frequently asked questions
Who provides the infrastructure?
Usually the client. Missing access shifts the deadline.
How do I write good criteria?
"User can do X and sees Y" – every line should be verifiable with a yes or no.
Why Stipme instead of an invoice?
Your client reserves the budget for each milestone in advance with the payment partner Stripe. You start with security, and they only pay on approval — automatically after 72 hours (excluding weekends).
Related templates
Get up to 12 months of Pro free
Stipme launches soon. The first 100 sign-ups get 12 months of Pro, and invites earn more.
Join the waitlist →