Process Server Management Software

Process server software for every attempt on the record.

Your agency runs on an inbox, a spreadsheet, and texts to servers in the field. We turn that path, from a law firm's instructions to the signed affidavit, into software where each job has one record, each attempt is stamped with time and place, and clients can see the status without calling you.

See our work

Bring one stuck workflow. Leave with a build, buy, repair, or wait recommendation.

Trusted by

Perceptional logoMusgrave GroupUrShipper logoBrux Dental SolutionsBella Skin Institute LogoEnergia RewardsDraftly logoTuneClub LogoSekou LMS logoLogo of food order management app gulaSnelwegDealsGrubly logoPSi logoInstantor Rewards logologo of Mobile app for events, membership clubs, and communitiesAldiFest retail campaign logoVidmattic logoEMS Connect logoWorx Squad logologo of Online Web App For Making Intrologo of Referral and Viral Marketing PlatformConcurrences logoGE logoTicketstop logo

The brief

Start with what is not working.

Good software decisions begin with the constraint, not a list of features or a preferred technology.

01

Instructions arrive by email, the job lives in a spreadsheet, and the server gets a text.

02

Attempt notes come back on paper, then someone retypes them into the affidavit.

03

Law firms call for status because they cannot see their own jobs.

Plain answer

RaftLabs builds process server software around one job record that runs from a law firm's instructions to the signed affidavit. Servers log each attempt with time, place, and photos, the affidavit is drafted from that log, and clients follow status in their own portal. Scope and price are agreed in writing first.

What to remember

  • Use this when a missed attempt, a wrong address, or a weak affidavit record can undo a whole case.
  • The first release should complete one full path, from job intake to the signed affidavit.
  • Each attempt needs its time, place, outcome, and server recorded once, in words the affidavit can use.
  • Quote the office side as its own scope: dispatch boards, server pay, billing, and client accounts are a second product, not a single admin-panel line.
  • Buy a ready product when it fits your courts and clients. Build when your way of working is the part that does not fit.

Fit

Custom software should earn its place in your office.

A long feature list is not enough. The case is real when the same weak point shows up in retyped affidavits, status calls, or a record a court questions.

A fit

Jobs pass through an inbox, a spreadsheet, and texts, and the only full record of a serve is the affidavit typed at the end.

Client firms send you work every week, and your office retypes their instructions and fields their status calls.

You can name the person who owns this workflow and what done looks like for the first release.

Not a fit

A ready product already matches your courts, your affidavit forms, and your billing, with a cost that makes sense.

Your intake and field process is still changing each month, so software would freeze a process that is not settled yet.

The brief is a feature list with no single path, from intake to signed affidavit, named first.

Not sure which side you are on? Use the first call to make that decision. A useful answer may be to buy, connect, repair, or wait.

Start with the record, not the software.

A process serving agency sells one thing: proof. A firm hands you papers and trusts that, months later, you can show exactly who was served, where, when, and by whom. That proof is built from small pieces gathered along the way: the instructions, the assignment, each visit, and the sworn statement at the end.

Today those pieces live apart. Instructions sit in an inbox. The job sits in a spreadsheet. The server gets a text. Attempt notes come back on paper or in a message thread. Then someone in the office types the affidavit from scratch, using facts the file already held, and each retyping is a fresh chance to get a name, a date, or an address wrong.

A second product hides inside the first. Client firms see one side: send a job, follow its status, receive the affidavit. Your team lives in the other side: dispatch boards, server accounts, fee lists, billing, and pay. Quotes that squeeze all of that into one admin panel line are where budgets break, so we quote your team screens as their own job, with their own users, from the start.

Custom process server software makes sense when one owned record can hold that whole path together better than a ready product, a spreadsheet, or a process change. The first release should take one complete path, from a firm sending a job to the signed affidavit going back. It should not try to replace every tool you use at once.

We start where it hurts.

The screen is only one part of the job. The real scope includes the attempt record, the affidavit form for each court, who can see and change what, what happens when an address is wrong, and who runs the system after release.

Sworn attempt records with time and place

The server logs each visit at the address, from a phone. Time and place are captured with the outcome, notes, and photos, in set words every server uses the same way. A submitted attempt cannot be edited later. A correction is a new entry, and the first entry stays on the record.

Affidavits drafted from the attempt log

The affidavit is filled from the attempts already recorded: when service happened, who took the papers and in what role, and which documents were served. Your office reviews the draft, the server signs, and the firm gets the finished document without anyone retyping the field notes.

A client portal for law firms

Each firm gets its own login to send a job once, with the documents and its own reference attached, and to follow that job through attempts to the signed affidavit. Your office stops retyping emailed instructions, and firms stop calling for status they can read themselves.

Dispatch, routes, and server pay

Open jobs sit in one list with due dates showing. The dispatcher assigns work, servers see their jobs on a phone, and the day's stops can be ordered into a route. Pay is worked out from completed jobs on the same record, so the office is not rebuilding the month from message threads.

Cases that do not fit one name and one address

One case can hold several defendants, and each one is a separate job with its own addresses and attempts. A bad address drops out of the day's work. A blocked address waits instead of failing. Skip traces, occupancy checks, and filings sit on the same case record as the serves.

Which one is yours?

Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

Workflows

Built around the way a job actually moves.

Some steps only exist in this trade. The same rule applies to each one: keep the record in one place, make the next step clear, and show the proof when someone asks.

Intake from the covering email

Work arrives as an email with court papers attached. The job record is opened from that message: the firm and its reference, the court and case number, each person to be served with an address and a deadline, and the documents named as the court names them. A person in your office checks and approves the record before it becomes a job. Nothing is typed twice.

Rules that follow the court

Each court sets its own rules for how service may be made and what the proof must show. The record holds the rule set for the court on the job, with the dates each rule applies from. A job served under last year's rules is still judged against last year's rules. Firms that run their own matters in legal practice management software still need your record to stand on its own when service is challenged.

Billing from the same record

Attempts carry fees, mileage, and extra charges as the work happens, priced from your own fee list. A closed job drafts its invoice from the record, and your office approves it before it goes out. Unbilled work cannot hide in a notebook, because the bill is built from the same entries the affidavit was built from.

Proof

The fifth attempt became a product customers could keep using.

UrShipper had already worked with four development vendors. Its founder describes the communication and decisions during the recovery.

The case study documents a 14-week recovery, five carrier connections, a Shopify fulfilment workflow, and client-reported results. It is one comparable project, not a promise that every inherited codebase can follow the same plan.

Read the UrShipper case study

Which handoff worries you the most right now?

Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

How it works

Close one expensive risk before opening the next.

Each stage answers a buyer question and leaves behind a decision you can inspect. The next stage only opens when the expensive uncertainty in the current one is small enough to accept.

  1. 01
    Understand

    Trace one real job

    Where does the record break down today?

    Follow one job and one defendant from start to finish, with the people who do the work. Include the covering email, the spreadsheet row, the texts to the server, the paper attempt notes, and the calls firms make when they cannot see the status.

    Decision produced

    A map of one job from a firm's instructions to the signed affidavit, with each handoff, form, and phone call marked, and the weakest points named.

    Risk closed

    Paying to automate the visible symptom while the handoff that weakens the proof stays on paper.
  2. 02
    Shape

    Choose the first useful release

    What needs to exist together for one full path to work?

    Choose the path from the way your office works, not from a feature list. Name each user, each court form, the attempt log, who can see and change what, the steps that must be done before the affidavit can be drafted, and the result the first release must complete.

    Decision produced

    One complete path, from job intake to signed affidavit, with the users, courts, forms, and messages it needs, and a clear statement of what done looks like.

    Risk closed

    A small-looking feature list that quietly depends on firm logins, field tools, and billing that were never scoped.
  3. 03
    Prove

    Review working software

    Will it hold up with a real job on a busy day?

    Review the product against a real job, not a tour of finished screens. Test what happens when an address is bad, a server corrects an attempt, a firm submits a job with missing details, or service fails and a statement of attempts is owed instead.

    Decision produced

    Working checkpoints tested with your own job types, your own affidavit forms, and the people who will use the system each day.

    Risk closed

    Finding the gaps only after firms and courts depend on the new record.
  4. 04
    Transfer

    Release, measure, and hand over

    Did the new path cut retyping and status calls, and can another capable team run it?

    Start with one group of client firms or one team of servers. Compare status calls, affidavit retyping, and unbilled work with the starting point before adding the next workflow. The general approach behind this is the same one we use for custom software development.

    Decision produced

    A controlled release, a comparison with the starting point, operating notes, an account ownership map, and a recommendation for what should happen next.

    Risk closed

    Counting screens shipped instead of errors avoided, or depending on the first vendor to keep the system running.

What it costs

Every project starts at $10K.

The first phase turns the costliest patched workflow into a scoped build with written acceptance criteria.

Starting investment

Starts at $10K

Workflow complexity, systems to connect, data migration, and user roles set the scope. After a 30-minute call, you get a written build, buy, repair, or wait recommendation plus first-phase direction. Free, whether or not you build with us.

Work with us

Bring one stuck workflow. Leave with a decision.

In a 30-minute call, we will help you decide whether to buy, connect, repair, build, or wait. If custom software is not the sensible next move, that is still a useful answer.

  • One named workflow owner and one complete path for the first phase.
  • Scope, price, what done looks like, and exclusions agreed before paid work starts.
  • Code, cloud, data, and provider access remain under your control.
  • Post-launch warranty cover for defects in the agreed scope.

Frequently asked questions

Straight answers to what buyers ask before they scope. Still stuck? .

It holds one record for each job, from the firm's instructions to the signed affidavit. The record holds the court and case details, the person or company to be served, each address, the documents, every attempt with its time and outcome, the affidavit, and the bill. Office staff, servers in the field, and client firms each see the part that is theirs to see, instead of working from an inbox, a spreadsheet, and text messages.

The server logs each visit from a phone at the address itself. The log captures the time, the place from the phone's location, the outcome picked from a fixed list, notes, and photos. A fixed list matters: every server describes the same outcome the same way, and those words are the words the affidavit needs later. A submitted attempt cannot be quietly edited. A correction is added as a new entry, and the original stays visible, because a sworn document rests on that record.

The affidavit is drafted from what the server already recorded: the date and time of service, who received the papers and in what role, how that person was identified, and which documents were served. Your office reviews the draft, the server signs it, and it goes back to the client firm as a finished document. Nobody retypes the attempt notes into a form, which is where names, dates, and addresses most often go wrong today.

Failed attempts still produce a record the court can rely on. The log holds each visit, its time and place, and what the server found, so a statement about the attempts made, sometimes called a due diligence record, can be drafted from the same entries. The office does not have to rebuild weeks of visits from a server's notebook when a firm asks what was tried.

Yes. Each client firm gets its own login. Firm staff enter the job once, attach the documents, and add their own reference. They can then see the status and attempts for their own jobs only, and download the signed affidavit when it is ready. Your office stops retyping instructions that arrive by email, and firms stop calling for updates they can read themselves.

Open jobs sit in one list the dispatcher works from, with due dates and rush jobs visible. A job is assigned to a server, who sees it on a phone with the address, the documents, and the deadline. Stops for the day can be ordered into a route the server can actually drive. When a server logs an attempt, the office sees it at once, so nobody has to phone the field to learn where a job stands.

Yes, and the record is built for it. A case can name several defendants. Each defendant is a separate job with its own addresses and its own attempts, because service on one person proves nothing about another. An address that turns out to be wrong is marked bad and drops out of the day's work. An address that is only blocked, such as a gate code you do not have yet, waits on standby instead of being treated as a failure.

They are jobs in their own right, with their own steps and their own proof. A skip trace job holds the searches run and the address they produced. An occupancy check holds the visit and what was found. A filing job holds what was filed and when. Each one sits on the same case record as the serves, so the firm sees the whole file in one place.

Yes. A job that falls outside your coverage can be placed with a contractor server, and it is tracked the same way as your own team's work: same job record, same attempt log, same affidavit path. You stay the agency your client deals with, and the record does not change shape because someone else made the visit.

The money sits on the same record as the work. Attempts carry the fees, mileage, and extra charges as they happen, priced against your own fee list. When a job closes, the invoice is drafted from that record and your office reviews it before it goes out. Server pay is calculated from the jobs that server completed, so month end is a check of work already recorded, not a rebuild from texts and notebooks.

You decide, client by client. Some firms want the full attempt record with location stamps and photos, because it helps them answer a challenge to service. Others only want the status and the affidavit. The portal shows each firm what you have set for that firm, and your servers see only their own jobs. Every view and change is recorded with who did it and when.

Yes. How papers may be served, who may receive them, and which form the proof takes all depend on the court the case belongs to. The job record holds the court and its rules with the dates they apply from, so a job is judged against the rules in force on the day of service, not the rules in force today. Your agency and your clients stay responsible for the legal call on each job. The software keeps the record straight and flags a job whose details do not match the rule set on file.

Buy a ready product when it matches your courts, your client firms, and the way you bill, and when its per-user or per-job cost makes sense at your volume. Build your own when the fit breaks down: your affidavit forms differ, you run contractors alongside staff, you need a client portal in your own name, or you need the record to connect to your billing in a way the ready product will not allow. If your process is still changing each month, wait and settle it first.

The first paid phase may cover a bounded review of your current process, a small test build, or a small first release. The final price depends on how many courts and job types you run, how many kinds of users it serves, whether client firms get their own logins, what it needs to connect to, and whether old job records need moving over. The agreed phase is priced in writing before it starts.

Timing depends on scope. One complete path, from a firm sending a job to the signed affidavit going back, is a smaller job than the same path with contractor dispatch, skip tracing, and billing added. The schedule is set once the first path and what done looks like are clear, and you review working software at agreed checkpoints along the way.

Yes. Most first jobs start from an inbox, spreadsheets, or an older tool that no longer fits. We start by following one real job through your office, noting each handoff, each form, and each place where the same detail is typed twice. Job records that are sound are moved over. The steps that cause errors, usually the affidavit typing and the status calls, are the ones we change first.

You judge what you can see, not the code. Each checkpoint is working software you use yourself, tested against a real job from your own office: a firm sends a job, a server logs attempts in the field, and the affidavit comes back drafted from that log. Progress is reported in plain language: what changed, what is next, and what it costs. You own the code and the accounts throughout, so nothing is locked inside our heads.

You own the code built for you and control where it lives, the cloud accounts, the data, and the third-party accounts. Outside services and open-source parts keep their own licence terms. The operating notes stay current so another capable team can take over if you ever choose to move.