Every change request goes through one place.
Change requests scatter across email, Slack, and calls. This is one place for them: the client submits, you add the price and timeline, and both of you keep the record.
Free for one active client project. €15/month when Iterations becomes part of your regular workflow.
The client asks here
They write the request in the portal, in their own words. You do not reconstruct it from a thread.
You put a price on it
Qualify it against the original scope, add the impact, and send it back for approval.
A decision on the record
They approve or decline. Totals move only when they agree.
How it works
The client asks. You price it. The numbers move.
- 1
Open a project
Name the work, set the original scope, value, and deadline, then invite the client. Tell them this is where change requests go.
- 2
Client submits a request
They write what they want. It is structured against the original scope before it reaches you.
- 3
You qualify it
Add the price and timeline impact, then send it back. You can still propose a change yourself when you originate it.
- 4
Client approves or declines
The decision is recorded with who and when. Approved extras move the value and deadline; declined ones stay in the history.
Not a project manager
No boards. No chat. No files. The place requests go.
Iterations does not replace your tools for tasks, messages, or invoices. After kickoff it is the official channel: what was requested, what you priced, what they agreed, and what that did to the price and the date.
Free for one active project.
Enough to run the full workflow with a real client. Freelancer is €15/month when you run more.