Solutions / Web development agencies
The statement of work is a PDF. The extra page is a ticket.
Oct 24, 2026
Web studios sell a scope, then live in the backlog. The milestone invoice still describes the PDF.
The backlog is not the contract
A page, an integration, a CMS field, a small animation. It lands in Jira or in Slack. The statement of work does not move. The milestone is billed because the calendar said so.
Fixed-fee sites leak when those tickets are treated as included. The hours are on a timer. The fee is on a PDF from the week the deal closed.
Scope, then a signature, then a line
Projects hold the job and the milestones. A change becomes a draft, then a sign link, then a line item. The client signs without an account. Finance invoices the signed lines, the billable time, and the expenses.
Jira can stay. It is optional capture, not the record. The record is the job: the paper, the people, and the money.
Margin before launch
Resources hold who is on the build and what they cost. Margin is signed paper against time and invoices, so a fixed-fee site shows the leak while there is still time to gate the next request.
Ask AI reads that tree when someone asks what is ready to invoice. The answer is the signed change and the open line, not the nearest ticket.
Seats and the voice line are on the pricing page. Clients are not seats. Book a demo to see the job on one record.
Questions
- Do we have to leave Jira?
- No. Jira is optional capture. The statement of work, the change order, and the invoice stay on the job in Blinkdots.
- How does a milestone invoice stay honest?
- It is drafted from signed lines, billable time, and expenses on that project. A page that was not in the statement of work is a change order first.
- Can the client sign a change without a login?
- Yes. They get a public sign link. A typed name is the acceptance on that change order. They never create an account.