The project is the central record
The client is added once. The project’s details become the shared context, and each downstream record uses it — while files and activity stay attached to the engagement.
What lives inside a project
Everything a client engagement needs, grouped by how you actually work through it.
Planning
Scope & details
Give the project a title and description so the brief lives with the work, not in a separate document you have to hunt for.
Timeline
Set a start date and a delivery date, so the project carries its own schedule instead of dates buried in messages.
Project value
Record the total value of the engagement, and choose a one-time, milestone-based or custom payment structure.
Delivery
Milestones
Break the work into stages — as percentages or fixed amounts, each with its own due date. Templates like 50/50 or 30/30/40 give you a quick starting point.
Files
Upload deliverables and payment proofs to the project, and download or remove them later. They stay attached to the engagement they belong to.
Activity history
The project keeps a running history of what happened — so you can see how it progressed without reconstructing it from memory.
Commercial
Agreement
Generate a professional agreement as a PDF from the project details you already entered, so the scope and milestones stay consistent.
Invoices
Create an invoice linked to a milestone and download it as a PDF. Each milestone tracks whether its invoice is open, partially paid or paid.
Recorded payments
Record payments against an invoice, including the method and partial amounts. Invoice status is derived from what you record, so it stays accurate.
You can also share a read-only view of the project with your client, and mark a project complete or archive it when the engagement wraps up.
Scattered details vs. one project record
Enter the project information once, then carry it through the work. Remex doesn’t import from your other tools — the value is that the records stay connected inside it.
When project information is scattered
- Scope sits in a document
- Dates are in messages
- Milestones are in notes
- Files are in Drive
- Invoice amounts are re-entered
- Payment status is kept elsewhere
- Client updates mean gathering from several places
When the project is the source of truth
- Scope stays with the project
- Milestones carry the delivery and payment structure
- The agreement uses the project context
- Invoices connect to the relevant milestone
- Payments update invoice status
- Files and activity stay attached
- Client visibility reflects the records you maintain
How a project moves forward
Add the client
Start with the client the work is for. The project attaches to that record.
Create the project
Capture the scope, timeline and value. This becomes the shared context for everything else.
Define milestones
Split the value into stages so the delivery and payment structure is set up front.
Generate the agreement
Produce a PDF agreement from the same project details — no re-writing the scope.
Invoice as work becomes billable
Turn a milestone into an invoice when its stage is due; the amount carries over.
Record payment & keep the history
Log payments against the invoice, and the project retains the files and activity.
What you stop repeating
Instead of: Rebuilding project details for an agreement
You can: Generate the agreement from the details already on the project
Instead of: Typing milestone amounts into a separate invoice
You can: Create the invoice from the relevant milestone
Instead of: Checking a separate sheet for payment status
You can: Record payments against the invoice and read status from there
Instead of: Searching folders for the right file
You can: Keep project files attached to the engagement
Instead of: Reconstructing what happened on a project
You can: Review the activity history on the project
Instead of: Writing a manual status summary for the client
You can: Share a read-only project link that reflects your records
Who this is for
Independent professionals who scope client work, divide it into deliverables, bill for it and manage the engagement themselves.
Projects sit at the centre of the Remex workflow
Client information flows into a project, and the project connects milestones, agreements, invoices, payments and history. Seeing the full sequence makes the connection clearer.
Explore the freelancer workflow →Questions about projects
What is a project in Remex?
A project is the workspace for one client engagement. It holds the scope, timeline and value, and connects the milestones, agreement, invoices, payments, files and activity for that work.
Can I connect a project to a client?
Yes. A project is created for a specific client, so everything in the project stays tied to that relationship.
Can I create milestones inside a project?
Yes. You can divide a project into milestones using percentages or fixed amounts, each with its own due date, or start from a template.
Can I generate an agreement from project details?
Yes. Remex generates a professional agreement as a PDF using the scope and milestones you already entered on the project.
Can I create an invoice from a milestone?
Yes. Invoices are linked to milestones, and each milestone shows whether its invoice is open, partially paid or paid.
Can I record partial payments?
Yes. You can record payments against an invoice, including partial amounts, and the outstanding balance and status update accordingly.
Can I share a project with my client?
Yes. You can share a read-only link so a client can see project progress, milestones, invoices and files without needing an account.
Run your next client project in one connected workspace
Scope, milestones, agreement, invoice and payment — kept together on the project.