Rates and invoicing with explanation
Custom software costs depend on scope, risks, and the work required. We discuss rates in the context of the assignment and explain how we report and invoice the hours spent.
Time and materials based on real work performed
Monthly invoicing in arrears
Hour reporting with traceable context
What you can expect from an invoice
Invoicing based on hours worked
Our invoicing method is based on Glossary · In brieftime and materialsTime and materials billing calculates the price after work has been carried out, based on the actual hours worked and costs incurred at agreed rates.Read more for the hours actually worked on the project. We invoice monthly in arrears and, where possible, connect hour reporting to the context in which the work was done, for example through tickets or similar project sources.
With custom software, cost depends on Glossary · In briefscopeScope defines the boundaries of a project or assignment: which goals, activities and results are included and which are excluded.Read more, risk, integrations, and pace. So transparency mainly sits in how we report, explain, and adjust along the way.
Which agreements belong with this
Invoicing with clear ground rules
We send invoices afterward based on work actually performed. That matches how we also discuss progress and budget.
Where possible, hour reporting refers back to tickets or other traceable project context, so it remains clear where time was spent.
For tooling, hosting, and monitoring, we prefer procurement in the client's name. If 10KB still procures a service, we pass those costs through with specification.
We define payment terms and any annual indexation explicitly, so no haze forms around them later.
An hourly rate obviously exists, but we would rather discuss it together with scope, capacity, and collaboration model than as an isolated marketing number without context.
Work first, invoice after
Monthly invoicing in arrears
We send invoices afterward based on work actually performed. That matches how we also discuss progress and budget.
Why this works better
Visibility into hours and costs
For business-critical software, an explainable invoice is more useful than a nicely rounded amount that becomes less true the longer the project runs. Transparency means you can follow what work was done, how it fits the priorities of that moment, and what a change means financially.
We discuss rates and invoicing alongside scope, estimates, and monthly planning. That lets you compare costs with the work agreed and completed.
What this gives you
Monthly invoices that match real work performed
More insight into where hours and costs go
Fewer surprises around payment terms and external services
A rate discussion that stays connected to scope and collaboration
Frequently asked questions
Yes. For custom software, time and materials is our default because it aligns better with changing scope, risk, and priorities.
Yes. Hour reporting should be traceable and, where possible, refers back to tickets or other project context.
No. We prefer to place them directly in the client's name. If 10KB still procures them, the costs are passed through with specification according to the agreements made.
No. We discuss an hourly rate clearly, but a public price list would suggest too strongly that complex software projects can be judged separately from scope and context.
Is your question not listed here?
Get in touch