The platform
One connected system, not ten tools wired together.
Your inbox, CRM, contracts, work, invoicing and attribution share one spine, so the whole state of your agency is one screen instead of a reconciliation meeting. Built and configured for your agency.
30 minutes, no slides. We map your current stack live. Dutch or English.

A real Metiva Command Center with demo data, not a render.
Integrates with
Real adapters at the edge. Your data stays on one first-party spine.
The shared spine
Why one connected system beats ten integrations.
Integrations move copies of your data between tools on a schedule, and copies drift. A spine means there are no copies. The inbox, the pipeline, the contracts and the reporting are the same records, seen from different angles.
- One record per person
- An anonymous visit, a WhatsApp message, a booked call, a Stripe payment and a typed lead all resolve to one canonical person.
- One funnel chain
- A lead becomes a contact, opens a deal, converts one-to-one into a signed contract and a paid invoice, joined by real foreign keys.
- One work engine
- A deal, a deliverable or a ticket routes to one owner with an SLA, and everyone starts the day from one queue that spans every module.
Ten tools each keep their own copy of the customer. Metiva keeps one.
The product tour
Everything your agency runs on, as one platform.
These are not nine apps in a bundle. Open any module and you are looking at the same people, deals and revenue as every other one.
Capture and convert
Every customer message, in one shared inbox.
A dozen channels land in one queue, each thread wired to the contact and the open deal behind the conversation. The AI assists your team inside the composer: draft, rewrite, shorten, translate. Assist for people, not an autonomous chatbot.
- A dozen channels in one queue: email, WhatsApp, Instagram, Telegram and more.
- Every conversation linked to the contact and the deal it belongs to.
- AI-assisted replies your team writes faster, with a person in control of every message.

Capture and convert
Capture a stranger and move them to a closed deal.
Score inbound leads automatically and move them across one drag-and-drop board from new lead to won deal. Because the pipeline sits on the same spine as the inbox and the invoicing, a single ad click can follow a person all the way to revenue.
- One drag-and-drop board from new lead to closed deal, with automatic scoring.
- Every deal carries its full history: the first ad click, the messages, the contract.
- Won deals feed the attribution loop, so ROAS means real revenue.

Close and get paid
Turn a signed proposal into a paid invoice.
A proposal becomes a signed agreement with a real evidence trail, then an invoice with the same line items. Retainers bill themselves and get paid through Stripe Checkout. Moneybird and Exact Online are on the roadmap.
- Contracts and e-signature with an evidence trail, converted one-to-one into invoices.
- Retainers that bill themselves, paid through Stripe Checkout.
- Overdue invoices surfaced in one collections queue, so nothing slips.

Deliver and operate
One work engine, and rules that do the routing.
A single work item can anchor a deal, a deliverable, a milestone or a ticket to one owner with an SLA and automatic routing. Templates and trigger-condition-action rules handle the repeatable steps, so every person starts the day from one My Work queue that spans every module.
- One My Work queue across every module, with SLA clocks and automatic routing.
- Trigger-condition-action rules for the repeatable steps, no code required.
- AI assist for people inside the inbox, gated on an API key, never an unattended bot.
Work and automation
- My Work: one queue across deals, deliverables, milestones and tickets.
- SLA clocks and business hours, configured per client.
- Trigger, condition, action rules with sensible defaults seeded for you.
- AI-assisted drafting inside the inbox composer, a person always in control.
Deliver and operate
Roles, scorecards and an audit trail.
Eight tenant-scoped business roles from one source-of-truth registry, per-person scorecards, an approvals queue and an audit trail. The same person can be admin at one client and finance at another, enforced on the server.
- Eight tenant-scoped roles from one source-of-truth registry, enforced server-side.
- Per-person scorecards, and an approvals queue for the work that needs a sign-off.
- An audit trail across every module, so you can see who changed what.
Team and performance
- Eight built-in business roles, scoped to each client.
- Per-user permissions, plan-bounded and enforced on the backend.
- Per-person scorecards and an approvals queue.
- A full audit trail across every module.
Share with clients
A client login that shows the work, not your internals.
A separate, isolated client login where your client follows the work, pays an invoice, e-signs a contract and shares files. Read-only per brand, so a client sees their own results and nothing of your internals or your other clients.
- A separate, isolated login per client company, fail-closed by design.
- Clients follow the work, pay, e-sign and share files in one place.
- Read-only per brand: their results, none of your internals.
Client portal
- A separate, isolated login for each client company.
- Follow the work, pay invoices and e-sign contracts.
- Share and receive files in one place.
- Read-only per brand, so nothing of your internals leaks.
Multi-tenancy, access and sign-in
One identity model. Each client isolated by design.
Metiva is multi-tenant from day one, on a three-tier model: one agency, multiple brands, and contacts under each brand. The structure is the same for every client, and the boundaries are enforced, not assumed.
Isolated by design, fail-closed
Each client's data is isolated by design and fail-closed. The tenant is bound from a verified claim inside the signed token, never a header the browser sends. If the claim cannot resolve, the request fails closed rather than serving the wrong client's data.
Role-based access, tenant-scoped
Eight built-in business roles, scoped to each client, from one source-of-truth registry shared by the backend and the app. The same person can be admin at one client and finance at another, enforced on the server.
One secure sign-in
One central login service verifies credentials and mints a signed token. The app never serves its own login form, and the token secret stays on the backend. It is the same hand-off ServiceTitan and Procore use, modeled exactly.
Compliant by architecture
Consent is deny-by-default, IP addresses are truncated and encrypted at rest, right-to-erasure is built in, and production refuses to start without an encryption key. Built for the AVG, not bolted on afterwards.
Configuration over customization
Built and configured for your agency, not custom-coded for it.
Think of how a factory sets up one proven machine for a specific line, instead of welding a new machine every time. Metiva is the same core system, configured to how your agency actually works, on a base that stays maintained and upgraded for everyone. You get a system that fits, without forking the code. That is why one product can replace roughly ten tools instead of becoming an eleventh.
Configured per client
- Command Center tilesMRR, cash-in, +4
- Pipeline stages and scoring6 stages
- SLA clocks and business hoursMon to Fri
- Roles and permissions8 roles
- Branding and tracking domainyourbrand.nl
Priced per company
It starts with the Tool-Stack and Attributie Audit, a 5-day audit into a 0 to 365-day rollout plan. A one-time implementation, then a monthly service retainer. Priced by the client brands you manage, not per seat. The monthly is a service retainer (a supportabonnement), not software rental: hosting, maintained integrations, support, and accurate attribution.
Platform FAQ
The questions agencies ask first.
No. The inbox, pipeline, contracts, invoicing, work and reporting are the same records on one spine, not separate apps syncing copies. That is the difference between an operating system and a tool stack.
Each client's data is isolated by design and fail-closed. The tenant is bound from a verified claim inside the signed token, and if it cannot resolve, the request fails closed rather than serving the wrong client's data.
It is built to connect to both, and that adapter is on the roadmap rather than a live sync today. We will say so plainly until it ships. We never rebuild accounting.
Yes. Tiles, pipeline stages, routing, SLA clocks, roles, branding and your tracking domain are configured per client, without forking the code. Configuration over customization.
No. The AI assists your team inside the inbox composer (draft, rewrite, shorten, translate) and is gated on an API key. It is assist for people, not an unattended bot.
It is a service retainer (a supportabonnement), not software rental: hosting, maintained integrations, support, and accurate attribution. Metiva is priced per company, not per seat, and quoted directly on how your agency runs, on WhatsApp or by email.
One connected system
One system to run your whole agency on.
See your inbox, pipeline, contracts, work, invoicing and attribution on one screen. We map your current stack live and show you what one spine replaces.
30 minutes. No slides. We map your current stack live. Dutch or English.