Work and projects

Every job has one owner and one queue.

Assign a client or a job to a team member and track the work in the same system that holds the deal, the contract, and the invoice. No separate project tool to keep in sync, so the work can never disagree with the record.

30 minutes, no slides. We map your current stack live. Dutch or English.

go.metiva.io/work
My Work: Sanne Koeman
Across every module
4 open
  • DeliverableQ3 campagne creatives
    De Vries Media
    Due todaySK
  • MilestoneKickoff sign-off
    Brouwer Retail
    Due in 2 daysJB
  • TicketTrackingpixel vuurt niet
    Noord Media
    Resolve in 4hSK
  • Deal taskVerlengingsvoorstel sturen
    Atelier Duin
    Due in 3 daysTV

Sample data, illustrative

A My Work queue across every module, with sample data, illustrative.

One owner per item

Assign a client or a job to a person.

A deal, a deliverable, a milestone and a ticket are all the same kind of thing in Metiva: a work item with one owner. You assign it to a person, or you let routing pick, and the item carries its client, its deal, and its history with it.

  • One work-item model spans deals, deliverables, milestones and tickets, so there is a single thing to assign.
  • Every item has exactly one owner, so nothing lives in the gap between two people.
  • Routing is automatic, by round-robin or by team, so new work lands on someone without a manual hand-off.
See roles and workload
go.metiva.io/work/assign
DeliverableQ3 campagne creatives
De Vries Media
Round-robin
Owner
SKSanne Koeman
SKSanne Koeman3 open
JBJeroen Bakker5 open
TVThomas Visser2 open
One owner per item, routed the moment it is created.

A work item routed to an owner, with sample data, illustrative.

One queue to start from

The day starts from one queue.

Because every module writes to the same spine, one My Work queue can hold a deal task, a deliverable, a milestone and a ticket side by side. SLA clocks keep them honest, and the repeatable steps run on rules you configure once.

  • My Work spans every module, so a person starts the day from one list instead of five tabs.
  • SLA clocks run on your business hours, so a target set to two hours does not tick overnight.
  • A breach sweep flags what is at risk before it is late, so nothing quietly slips a deadline.
  • Templates and trigger-condition-action rules handle the repeatable steps, so the routine runs itself.
See the automation builder
go.metiva.io/work/sla
SLA and business hours
Noord Media
Business hoursMon to Fri, 09:00 to 17:00
First response2 uur
Resolution1 werkdag
JBTicket 4821, De Vries Media At risk in 30m

Sample data, illustrative

SLA clocks on your business hours, with sample data, illustrative.

Progress in the open

Progress you and the client both see.

The work your team tracks internally is the same work the client watches from their side. One set of milestones, shown two ways: full detail for you, plain progress for them.

  • Milestones and deliverables are tracked work items on a clock, the same records your team manages internally.
  • The client follows that same progress read-only in their portal, instead of waiting on a status email.
  • What the client sees is progress per brand, never your internals or your other clients.
go.metiva.io/portal/progress
De Vries Media: onboarding
Shared with the client, read-only
On track
  1. Kickoff en toegangDone
  2. Merk en boodschapDone
  3. Campagne bouwenIn progress
  4. Livegang en overdrachtUpcoming
2 of 4 milestones complete50%

Sample data, illustrative

Configured per company

Set up to how your agency runs delivery, not sold as-is.

Metiva is not one dashboard sold a hundred times. During implementation we configure this module to how your agency actually works, on a core that stays maintained and upgraded for everyone. A one-time implementation, then a monthly service retainer (a supportabonnement, not software rental), priced by the client brands you manage with unlimited seats.

Configured per client

  • Work templates per job typeYour playbook
  • SLA clocks and business hoursMon to Fri
  • Routing rulesRound-robin
  • Deliverables per client brandPer brand

Isolated per client

Each client company's data is isolated by design, and every request binds to a tenant from a verified claim in the signed token. If it cannot resolve, it fails closed.

EU data residency

Your data is stored and processed in the EU, with right-to-erasure built in, because Dutch agencies answer to the AVG and so does Metiva.

Consent, deny-by-default

Tracking stays off until a visitor opts in, IP addresses are truncated and encrypted at rest, and EU identification stays company-level without consent.

The full picture lives in the Trust and Security Center.

Built on one system

1
My Work queue across every module

One place to start the day

4
Kinds of work item

Deal, deliverable, milestone, ticket

2
SLA clocks per item

First response and resolution

0
Per-seat fees

The whole team works the queue

Capability counts, not performance promises. We show you the rest live on the call.

Questions

Straight answers about work and projects.

Metiva is one system, priced per company, not per seat: a one-time implementation, then a monthly service retainer priced by the client brands you manage, with unlimited seats. The monthly is a service retainer, not software rental: hosting, maintained integrations, support, and accurate attribution. 12-month commitment, then cancel monthly, with two months free on annual prepay. Tell us how you run and we quote you directly, on WhatsApp or by email.

No. Work in Metiva sits on the same record spine as everything else, so the deal, the contract, and the work item share one client record. There is no separate project database to keep in sync, which is why the work can never disagree with the deal it belongs to.

Every work item has exactly one owner. You can assign it to a person directly, or let routing pick, automatically by round-robin or by team. Deals, deliverables, milestones and tickets are all the same kind of item, so they are all assigned and routed the same way.

Yes, read-only and per brand, inside their own portal. Milestones and deliverables are tracked work items, and the client follows their progress instead of waiting on a status email. They see progress, never your internals or your other clients.

No. Sensible defaults are seeded for you, and during implementation we configure the templates, SLA clocks, and trigger-condition-action rules to your playbook. You can adjust them yourself afterwards, but you do not start from a blank canvas.

One connected system

See your delivery running on one system.

Work and projects are one angle on the same system that runs your inbox, pipeline, contracts, and invoicing. We will show you the whole thing, with your real stack on the screen.

30 minutes. No slides. We map your current stack live. Dutch or English.