Solutions / Software development agencies

Named people, and a scope that moved.

Oct 24, 2026

Software shops sell a build or a team. The scope moves in standups. The invoice still comes from a spreadsheet.

A price, or people for a month

Some jobs are a fixed build. Some are named people for a month. Both need the same record: who is on it, what was signed, what changed, and what is billable.

A contractor who can log in is a member. The client is not a seat, even when they join the standup.

The standup is not a change order

A new endpoint, a new admin screen, a week of “just support.” If it is not a signed line, it is not in the fee. Ask AI can draft the change from the job. An owner approves it. The client signs a link. The line lands on the invoice.

Time, expenses, and rates hang off that same project. Allocation is a relationship on the job, not a second spreadsheet.

The next engagement

CRM holds the pursuit until it is signed. Once signed, projects, resources, and finance write onto the same job. A staffed month and a fixed build are not two products.

Invoices are a record and a PDF. Clients do not pay inside Blinkdots. They receive the invoice after an owner sends it.

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

Can one workspace hold fixed-scope builds and staffed months?
Yes. Both are jobs on the client. The signed paper, the people, the time, and the invoice sit on that job either way.
Who counts as a paid user on a staffed engagement?
A member who can log in, including a contractor. The client does not. Signers and binder viewers do not.
Will Ask AI tell the client the sprint slipped?
It can draft from the studio’s own record. The draft waits. An owner hits Approve before a sign link or an invoice email goes out. The voice line only speaks when someone calls.

Other industries

Run the studio from one job.

Signed scope, the change, the hours, and the invoice on the same record.

Or write admin@blinkdots.com.