Let’s say we come to an agreement. What are your billing policies?
We have 2 standard billing policies:
- for fixed time contracts.
- for ongoing contracts.
Let’s start with fixed time contracts. How is it going to be?
Usually, fixed time contracts come with a set of milestones. The usual milestones are:
- signing of the contract
- Alpha version
- Beta Version
- Release Candidate
- Release and Code delivery
We usually map milestone accomplishment to issuing invoices. The procedure is -we declare a milestone accomplished, you (the client) confirm the accomplishment and we issue the invoice.
It is not mandatory that we respect all the milestones above, and we openly accept different milestones.
And how is this related to your rates on the other page?
When we make an estimate for a project, the actual work is to determine how many working hours we need. Then we apply the pricing policy like on the page you’ve mentioned and conclude to a budget and a final price.
Payment structure is to be discussed with you (the client), but it will surely be tied to some milestones.
What about the “ongoing contracts”?
These are usually easier to manage. At the end of each month, we send you a worklog report for the project. You then confirm all or part of the worked hours. If you confirmed only part of the hours, we should probably have a discussion to solve the eventual discrepancy. When we agree on the amount, we issue an invoice.
OK, understood. Anything else?
Due to past unpleasant experiences, sometimes we do charge some emergency rates. This only happens if “urgent requests” become very frequent. This “very frequent” phrase is subject to our own judgement, but it cannot be less than 5 times a month.
|
