Start freeNo. Clients review and approve work through portal links without creating an account. Both sides reference the same agreement-to-payment timeline.
For freelancers & clients
One record.
Both sides aligned.
Salag documents client work on a shared timeline, not to take sides, but so freelancers and clients reference the same facts when scope, delivery, or payment questions come up.
No surveillance · No escrow · Payments go directly between you and your client
What goes on the record
Every engagement builds the same timeline, visible to the freelancer, reviewable by the client.
Agreement
Deliverables
Client approval
Invoice
PaymentFreelancers get
Written scope before work starts- Timestamped deliverable submissions
- Approvals before invoicing
- Payments matched to invoices automatically
Clients get
- Clear scope and revision limits upfront
- Portal links to review and approve work
- Invoices tied to approved deliverables
- No account required to participate
The workflow both sides follow
Step 01
Client & engagement
Add the client and open a workspace. One place for the full client job.
Step 02
Agreement
Set scope, rate, revision limits, and payment terms before work starts.
Step 03
Deliverables
Submit deliverables, links, reports, or timesheets the way you already work.
Step 04
Approval & invoice
Clients approve through portal links. Invoice from approved work with context attached.
Step 05
Payment & record
Match incoming payments to invoices. Every step stays on the client timeline.
When something goes wrong, facts beat opinions
Export a proof package, agreement, submissions, approvals, invoice, and payment, from one engagement.
Freelancer Workspace.
Salag is not
A marketplace or job board- Escrow or payment holding
- Surveillance or activity monitoring
- A replacement for lawyers or contracts
FAQ
Straight answers
Clear structure reduces defensiveness because expectations are shared early. Serious clients prefer documented scope and delivery over ambiguous informal arrangements.
You can still keep tone friendly while documenting scope, payment, and delivery in writing. Structure protects the relationship when memory or interpretation diverges later.