There are two models for running a process-serving network. Model one is the gig platform: open the doors, let any registered server sign up, post jobs publicly, race to the bottom on price, and use star ratings as the only quality lever. Model two is what we do.
We picked model two on purpose. Here is what it costs us and what it gets the customer.
Tier 1: in-house staff
About a third of our serves are completed by W-2 employees of Servd. They have salary, health insurance, paid time off, and a clear career path that moves from junior server to senior server to dispatch ops. They drive Servd-branded vehicles, carry Servd-issued equipment (phone, body camera, printer for affidavits), and follow Servd's training and quality standards from day one.
Why? Because the highest-stakes cases — TROs, time-critical evictions, family law where personal safety is in play — need to land in the hands of someone whose primary job is doing this work correctly. Not someone who's also driving for Uber that week.
Tier 2: independent contractor partners
The other two thirds of our network are independent process servers — small one- or two-person shops, mostly — that we onboard as 1099 partners. Every Tier 2 partner goes through the same intake stack:
1. W-9 and our Independent Contractor Agreement — covers NDA, data handling, brand use, dispute resolution. Negotiable terms, but the framework is consistent. 2. License verification — every server provides their county process server registration. We verify with the county registrar, store a copy, and track the expiration. 3. E&O insurance certificate — Servd named as additional insured. Coverage minimums set in the IC agreement. 4. Background check — Checkr run before activation, refreshed annually. Charged to Servd, not the server. 5. Training module — Servd's voice-log standards, photo and GPS conventions, affidavit format, branding rules. 6. Test run — the first three jobs are admin-reviewed before the partner unlocks for live dispatch.
The intake takes about three to five days on the partner's end. We don't onboard everyone who applies. The drop rate at the background-check step is non-trivial.
What this gets the customer
A customer who orders service from Servd is buying Servd-branded service with Servd's quality guarantee. They are not picking a server from a marketplace. The dispatcher (AI proposes, ops confirms) picks the server based on:
- Geography and travel time
- Current workload
- Tier classification matched to case complexity
- Document specialty (family, eviction, federal)
- Historical success rate in that zip code
- Customer sensitivity (some firms only see senior servers)
- SLA urgency
- Cost preference (in-house first for margin)
The customer never sees the server's name in the chat surface until the affidavit is signed. The affidavit, per CCP §2015.5, identifies the server by legal name and license number. That is the record. The UX is "Servd."
What this gets the server
Tier 2 servers on Servd see a steady book of pre-screened work, fair per-job pay, weekly ACH payouts (Tuesdays), and no race-to-the-bottom bidding. Nationwide pay structure:
- Standard service: server payout $75-90 per job (separate from customer-facing $99 rate)
- Skip trace: $35-45 per job
- Rush bonus: +$25-40
- Same-day premium: +$20-30
- Wait time: $25-35 per hour separate
We pay above the gig-platform median in our markets. The trade is consistency on the server's end and quality on the customer's end.
What we won't do
We do not:
- Run an open marketplace where anyone can sign up
- Let customers pick servers
- Show customer-visible star ratings on individual servers (the affidavit identifies the server; the brand is Servd)
- Race other vendors to the bottom on per-job price
- Treat servers as fully fungible
We do not pretend this is what every customer wants. Some customers want the cheapest possible per-job price and don't care about the quality difference. Those customers should use a gig platform. We optimize for the firms and individuals who want the service done right the first time.
Quality enforcement
Suspension triggers for any Tier 2 partner:
- Two missed SLAs in a row
- Three affidavit-rework requests in a single month
- One validated customer complaint with admin-confirmed fault
Suspension is a 30-day pause from dispatch. Reinstatement requires a written response to the trigger and a refresher on the relevant training module.
Termination requires a more serious event — falsified affidavit, customer-safety incident, regulatory violation, three suspension cycles within twelve months. Termination is rare. We're picky at intake so the long-tail termination volume stays low.
Why this matters
If you've ever filed a UD with a defective affidavit because the server cut corners, you know why. If you've ever had a TRO miss its hearing because the server didn't get to the address, you know why. If you've ever called a process server for a status update and gotten voicemail at 10 a.m. on a Tuesday, you know why.
We built the network the way it is because we are tired of the alternative. Customers should be able to assume the service is good. The customer's job is the law. Our job is the paper.