For agencies

Many clients. One workspace. Per-client records.

Context, billing, and delivery stay separated by client.

After · Per-client project

With Arvad

Client run evidence

Receipts
Checks
  • Unit suite
  • Integration
  • Deploy health
Cited files
  • app/api/checkout.ts
  • lib/billing/invoice.py
  • tests/checkout.spec.ts
Blast radius

3 services · 11 files · 0 shared schemas

Share the client link: plan, preview, cost, checks.

Share the client link: plan, preview, cost, checks.

Per-client partition

The category

Agencies need per-client context, white-label delivery, and a shareable run the client can review without sitting in your chat tool.

  • Hard partition per client, no cross-client prompt bleed

  • Client-scoped share view with plan and preview

  • Cost and duration tagged to the client partition

  • White-label review surfaces under your brand

Who this is for

Short paths. Clear outcomes.

Client delivery without tool sprawl

Onboard a client partition, run their project, share one review link, and read margin from attributable cost, not scattered tabs and status emails.

Multi-client portfolio view

Onboard the client

Isolated context and billing so staff and runs stay scoped to one account.

Per-client workspace partition

Client project run

Run the build

Plan, generate, and checks on their project—same mechanics, separate tenant.

Client-scoped share view

Client-facing record

Receipts
Checks
  • Unit suite
  • Integration
  • Deploy health
Cited files
  • app/api/checkout.ts
  • lib/billing/invoice.py
  • tests/checkout.spec.ts
Blast radius

3 services · 11 files · 0 shared schemas

Checks green. Staging URL live. Spend recorded on the same thread.

Share for review

Share plan, preview, and cost in one link your client opens without your chat tool.

Share artifact is the run URL

Agency mechanics

Per-client context

No cross-client prompt bleed.

Hard partition per client workspace

White-label delivery

Ship under your brand.

Client-facing surfaces omit Arvad chrome where configured

Docs for sign-off

PRDs land where your client already reviews.

Doc sync attached to the client thread

Team seats

Staff the account without mixing tenants.

Membership scoped to client partition

Per-client billing

Cost and credits stay attributable.

Cost line items tagged by client

Utilization view

Hours saved and margin in one place.

Utilization derived from run duration and spend

Portfolio visibility

See every client run without tab chaos.

Portfolio list is the multi-client home

Plans for you and your team

Solo or team. Upgrade when usage grows.

Save 20% on Team.

Compare plans

Pick the plan that matches how you build.

Free

Start free

Starter

Choose plan

Professional

Choose plan

Enterprise

Choose plan
Credits included120 credits included240 credits Included500 credits Included
Projects per week1 mini project2 mini projects4 mini + 2 medium projects
Documentation accessEssentialStandardFull
Planning & task breakdown
Dependency resolution
Queue-based processing
Daily questionsLimitedUp to 10 / per dayUp to 25 / per day
Upgrade options----Large projectsLarge-scale projects
Price$0.0$25$50

Straight answers

Limits stated plainly. No demo theater.

One question

When the build finishes, can you show a teammate the plan, preview, tests, and deploy status without digging through chat?

If you cannot, you still have a chat log. Arvad keeps that work in one workspace.

Onboard the client. Keep their project clean.

Keep exploring

MVP in hours

Ship a client demo the same day.

Meetings

Turn a discovery call into tickets.

Auto-document

PRDs ready for client sign-off.