Skip to content
parius.

A little more clarity. A lot better together.

On the same page.
From start to paid.

A shared workspace for freelancers and clients. Keep the conversation, the agreement and the next step together.

Independent people. Shared understanding.

Less chasing.
More creating.

Good projects need more than another chat. Give every conversation a place to become a clear next step.

The conversation

Everything in context.

A dedicated space for the work, the questions, and the decisions in between.

Studio websiteMaya & Alex · Illustrative project
MMaya · Client

The direction looks great. Let’s keep the homepage simple and give the photography room to breathe.

Alex · Freelancer

Agreed. I’ve added the direction to our project brief.

Brief, agreement and milestones stay connected.
The commitment

Clear before you begin.

Deliverables, milestones and approvals. A shared understanding you can come back to.

Example agreement

Studio website

Prepared for Maya · By Alex

Design & development1,800 USDC
Five pages. Two revision rounds.
Changes need both people’s approval.

Illustrative project. Your workspace starts with your own people and work.

Take a closer look

How Parius fits together

From the first brief.
Through every next step.

Start a project, invite your client and keep the decisions with the work. Each step builds on what you have already agreed.

Start a private project.

Invite your client into a shared workspace. Keep the brief, questions and feedback together.

Agree on the details.

Set the scope, price and revision limits. Each person approves the same version before it becomes active.

Review changes together.

A new request can become a new proposal. Existing terms stay in place until both people approve the change.

For the “one small thing” that isn’t.

A new request.
A fair conversation.

Projects evolve. Ask Parius to review a new request against the approved scope, so you can discuss the difference between a revision and a new deliverable.

See the context, discuss a proposal, and agree on the next step together.

Both people approve. Always.
Read how approvals work
Illustrative scope review

A new request in the conversation

“Could we add a booking flow so customers can choose a time and pay online?”

Needs review

A new feature, outside the agreed deliverables.

Milestones, review and payment

Deliver the work.
Close the loop.

Break the project into milestones. Submit each deliverable for review, then let your client accept it or request changes with the agreement in view.

Accepting work and authorizing payment are separate decisions. Tatum checks the USDC transfer on Sui. The freelancer then reconciles the receipt against the invoice.

Explore the project workflow
Studio websiteIllustrative project

Design direction

Reviewed and accepted

Website design

Reviewed and accepted

Build & handoff

Ready for client review
Final payment900 USDC

Approval first. Verification next.

Payment concept · Nothing is paid or verified in this example.

A lesson worth keeping

“Revisions refine what’s agreed. A new feature needs a new conversation.”

Confirmed by you

Next project, better context.
Remember the lesson. Apply it carefully.

Illustrative lesson · Confirm, store and recall

A workspace that grows with you

Good context.
Better next projects.

Your experience shouldn’t disappear when a project ends. Confirm the lessons Parius should remember, then bring that context into a later scope review.

Useful understanding that carries forward, so your next project starts with the lessons from the last.

Meet the foundation

The foundation behind the work.

Lasting context and verifiable payments are part of the foundation. Here’s how each integration supports the work.

Walrus Memory

Confirmed lessons that persist across sessions and inform a later review. Learning must change the assistance you receive.

Confirmed lessons, recalled with evidenceExplore Walrus

Tatum × Sui

USDC payments checked against real Sui transactions. The recipient, currency, amount and successful execution must match the onchain record.

Verified Sui Testnet payment flowOur payment approach

Frequently asked questions

About the workspace, approvals and your next step.

What is Parius?

Parius is a shared workspace for freelancers and clients. It brings the project conversation, agreed scope, milestones and payment history into one place, so both people can see what was decided and what comes next.

What can I use today?

You can create a private project, invite a client, agree scope, review milestones, share files, issue invoices and verify Sui Testnet payments. Scope reviews can recall confirmed lessons from Walrus Memory. Parius is in development; the public preview uses clearly labelled fictional examples.

Can AI change an agreement or make a payment?

No. AI can help identify a request that may fall outside the agreed scope and draft a reply. Both people must explicitly approve agreement changes. Payment authorization remains a separate human action.

How does Parius learn across projects?

A scope review can suggest a useful lesson. The freelancer confirms, edits or dismisses it in Memory. Confirmed lessons are stored through Walrus and recalled when relevant in later reviews, including after a new session. Personal lessons stay private; project lessons stay within their project context.

Do my clients need to understand crypto?

The workspace uses familiar invitations, conversations and approvals. For Sui payments, Parius shows the token, recipient, amount and network before you authorize a transfer. The current payment flow uses Testnet. Wallet and gas sponsorship options depend on the configured provider.

Make room for
your best work.

Start with a conversation.
Build on a shared understanding.

Start a project