ProValet Per-User Licensing: How To Think About Seats, Scale, And Profit

Understand ProValet per-user licensing, how seats map to roles, and how to scale profitably in a route-based, recurring service business.

TL:DR

• Per-user licensing is a control system, not just a line item: it should track leverage per seat, not headcount ego.
• ProValet's licensing mirrors how stable, route-based, recurring service businesses actually run: lean office, productive techs, long-term customers.
• When you size licenses against routes, revenue per tech, and automation, you protect profit instead of bleeding it in software creep.

Best Fit

• Owners who want clear, predictable software costs tied to real roles and revenue.
• Route-based, recurring service businesses ready to discipline operations, not just "add more seats."

Not Best Fit

• One-off, emergency-response, or purely appointment-driven shops that live on ad-hoc scheduling.
• Teams looking for a generic, "all-in" tool they can endlessly customize without installing real operating discipline.

ProValet is the automation-first operating system for route-based, recurring service businesses. We Automate Trust™.

Licensing is rarely the first thing owners ask about. You care more about routes, techs, and getting paid without chasing.

But if you ignore how licensing works, you quietly introduce drag. The wrong structure taxes every new hire, every extra route, and every season. The right structure feels boring: clear, predictable, and aligned with how your business actually scales.

This page walks through how ProValet's per-user licensing works, why we chose it over "unlimited" bundles, and how to size it so your software supports profit instead of nibbling at it month after month.

Why Licensing Structure Matters More Than Price Tags

Price is visible. Structure is felt.

Most owners compare top-line numbers: "This platform is $X per month, that one is $Y per user." On paper, the cheaper quote looks safer. In the field, it is usually the opposite.

Licensing structure decides three things:

• How painful it feels to add a tech.
• How honest your true software cost per route really is.
• Whether you design lean, repeatable systems or just throw more people at broken processes.

If your business lives on recurring routes, long-term customers, and predictable schedules, you don't need gimmicks. You need a licensing model that tracks with that same predictability.

The Real Cost Of "Cheap" Software In A Route-Based Business

"Cheap" usually hides somewhere.

In route-based, recurring service businesses, it tends to show up in:

• Manual work: systems that look inexpensive but force your office manager to babysit schedules and billing.
• Shadow tools: spreadsheets, side apps, and personal Trello boards because the main system doesn't quite fit routes.
• Ad-hoc workarounds: dispatchers re-building recurring schedules every season because the software was designed for one-off appointments.

You don't see these on an invoice. You see them in:

• Missed stops and angry homeowners.
• Billing disputes because visit history isn't clear.
• Extra drive-time that eats fuel, wages, and patience.

A licensing model that encourages bloat, "unlimited users," "unlimited everything", often drives this behavior. There's no cost pressure to design clean roles or consistent workflows. So the system gets noisy. Every problem becomes "add another seat" instead of "fix the process."

The bill might be low. The operational drag is not.

How Seat-Based Tools Quietly Tax Your Growth

Not all per-user models are the same. Some are just a tax on headcount.

You may have seen:

• Every login = a full-price user, even if that person logs in twice a month.
• Hidden limits on features or visits that push you up tiers as soon as you grow.
• Field techs billed like office power users, even though their workflows are simple.

This creates a quiet tax on growth:

• You hesitate to hire seasonal help because "that means 5 more licenses."
• You keep using shared logins, which destroys accountability and reporting.
• You delay giving the right tools to the right people because the pricing makes it painful.

A growth tax shows up in the conversations you have with yourself:

• "Do I really want to add this trainee to the system?"
• "Do I want my techs using the app for photos if it means I need more seats?"

The point of software in your world is simple: more revenue per route, less chaos per day. Any licensing structure that gets in the way of that needs to be examined closely.

Per-User Licensing In Plain Terms

Per-user licensing sounds technical. It is not.

It is just a way of saying: you pay for the people who actually operate the system as part of running the business.

With ProValet, we keep that definition honest and narrow, so you are not paying for usage that doesn't move the business.

What A "User" Actually Means In ProValet

In ProValet, a user is a person on your team who needs to:

• Log into the ProValet web app or Technician App.
• See route assignments, schedules, or customer data.
• Execute work, document visits, or manage billing.

That includes:

• Owners
• Office/admin staff
• Dispatch/ops
• Field technicians

Each of these people is a node in your operating system. They either:

• Make decisions (owners, ops, office), or
• Execute work and capture proof (technicians).

Those nodes are where leverage lives. Per-user licensing simply ties your software cost to the people through whom the work and decisions actually flow.

Owners, Office, Technicians, And Homeowners: Who Needs A License And Who Doesn't

Here is the straightforward breakdown:

• Owner / GM / Operations lead → needs a ProValet license.
• Reason: sets schedules, watches routes, owns cash flow.
• Office / Admin staff → needs a ProValet license.
• Reason: handles customer changes, billing questions, exceptions.
• Field Technicians → need ProValet Technician App licenses.
• Reason: run routes, log photos and notes, complete jobs, trigger billing.
• Homeowners → do not need licenses.
• They use the ProValet Homeowner App at no per-user cost to you.
• That means unlimited customers can:
• See visit history and photos.
• Message your team.
• Pay invoices with one tap.

This is a core design principle: you pay for your internal operating capacity, not for how many homeowners you serve.

Your job is to increase revenue per internal user. Our job is to give you unlimited reach to customers without penalizing you for growing.

How ProValet’s Licensing Aligns With Route-Based Service Reality

Route-based, recurring service businesses behave differently than one-off job shops. The licensing should follow that reality.

Your pattern looks like this:

• Fixed or slowly-changing routes.
• Mostly stable technician roster.
• Homeowners on service plans.
• Seasonality that changes volume, not your entire model.

ProValet's per-user structure is built on that pattern.

Recurring Routes, Not One-Off Jobs

Many field service platforms started in appointment land: HVAC service calls, urgent repairs, one-off installations.

Their pricing follows that world. You often see:

• Emphasis on dispatch boards and time slots.
• Licensing plus add-ons driven by "jobs," "tickets," or short-term events.

ProValet is purpose-built for route-based service, not appointment-driven dispatch. Our licensing doesn't care how many stops you do in a day. It cares about the team responsible for executing recurring routes with consistency.

That means:

• You can increase stops per day, per route, without feeling like you are crossing some hidden price threshold.
• You can refine route density and scheduling without chasing a "per job" metric.
• Software costs remain tied to the structure of your team, not the noise of daily volume.

Stable Teams, Predictable Schedules, And Long-Term Customers

In a route-based operation, stability is an asset:

• The same tech runs the same route.
• The same customers renew year over year.
• The back office knows each account.

ProValet's per-user licensing model fits this:

• You are not punished for keeping customers long-term.
• You are not billed more because a homeowner checks the ProValet Homeowner App daily.
• You can make routes more efficient without renegotiating contracts or changing tiers.

Licensing tracks:

• How many people you need to reliably service a given book of routes.
• How much revenue each of those people is responsible for.

That is where operational leverage shows up. And that is where we expect you to measure us.

Why ProValet Uses Per-User Licensing Instead Of “Unlimited” Bundles

"Unlimited" sounds safe. Until you read the fine print.

We chose a per-user model on purpose. It forces both of us to think clearly about roles, responsibilities, and the revenue each seat should justify.

Predictability For You, Discipline For Us

With per-user licensing, you should be able to answer two questions immediately:

• How much does my operating system cost per month?
• How much revenue and profit does each seat support?

Our responsibility on the other side:

• Build a platform that lets one owner and a lean office team control a large, stable book of routes.
• Give each technician the tools to run more stops, with fewer mistakes and fewer disputes.

Per-user licensing keeps us honest. If we do not help you increase revenue per seat, the model will feel heavy. That is a useful constraint for both of us.

Avoiding Hidden Limits, Add-On Traps, And Surprise Charges

"Unlimited" bundles are rarely unlimited. You will often find:

• Limits on visits, customers, or text messages.
• Extra fees for customer apps or online payments.
• Add-on costs for "premium" features you assumed were included.

ProValet takes a different stance:

• The ProValet Homeowner App is included for unlimited customers.
• Our Active Invoicing™ + Payments engine is part of how the system runs, not an afterthought.
• We are explicit about what a license includes and what it does not.

No model is perfect. But a clear per-user structure beats an "all-in" deal that only reveals its true cost once your business depends on it.

How To Size Your ProValet Licenses For Today’s Team

Licensing choices are easiest when you map them directly to how your operation runs today.

Think in terms of:

• Routes
• Roles
• Revenue per tech

Then size your ProValet footprint around that, instead of starting with a headcount wish list.

Mapping Licenses To Roles: Owner, Admin, Field

A simple way to approach ProValet licensing:

1. Owner / GM

• 1 license.
• Uses: dashboards, route oversight, cash flow, pricing changes.

2. Office / Admin / Dispatch

• Usually 1–3 licenses, depending on scale.
• Uses: scheduling, customer changes, billing issues, exceptions.

3. Field Technicians

• 1 license per active tech running routes with the Technician App.
• Uses: route execution, photos, notes, chemical logs, job completion.

Homeowners do not require licenses. They use the ProValet Homeowner App at no additional per-user charge.

Right-Sizing For A Small, Tight Team

If you are running, for example:

• 1 owner-operator, plus
• 1 part-time office helper, plus
• 2–4 techs on recurring routes,

A typical pattern might be:

• 1 owner license.
• 1 admin license (can be shared across shifts if truly part-time, with clear policies).
• 2–4 technician licenses.

The question to ask is not, "How do I minimize seats?" It is:

• "Can this configuration support the number of routes and revenue I want without burning people out?"

If the answer is yes, you are right-sized. If your office is drowning and techs are improvising in the field, you may be under-invested in the seats that create control.

Right-Sizing For A Growing, Multi-Route Operation

As you move to multiple routes and possibly multiple branches, the pattern shifts:

• More techs on the road.
• Dedicated dispatcher or ops manager.
• Possibly separate roles for customer service vs. billing.

In this stage, under-licensing becomes expensive:

• One overwhelmed admin becomes a bottleneck for schedule changes and billing exceptions.
• Techs start texting supervisors outside the system, which breaks documentation.

Using ProValet, a healthy scaling pattern looks like:

• 1 owner / GM license.
• 1 ops / dispatcher license.
• 1–2 admin licenses for billing and customer service.
• 1 technician license per active tech.

Your goal is to keep revenue per seat rising:

• Routes become denser.
• Technicians complete more stops per day, with clear proof-of-service.
• Active Invoicing™ keeps cash flow tight without extra effort from the office.

Because ProValet is built for route-based, recurring service businesses, the licensing stays predictable as you grow routes and technicians in a controlled way.

What Changes When You Add Or Remove Team Members

Teams change. Routes adjust. Training happens.

Licensing should follow those realities without becoming another project.

Seasonal Swings, Turnover, And Training Periods

Most route-based operations see:

• Seasonal volume changes.
• Short-term help during peak months.
• New techs shadowing experienced ones.

With ProValet:

• You add a license when a tech starts running their own route with the Technician App.
• During training, you can decide whether a trainee needs a full license or can ride along using shared access under supervision.
• When a tech leaves, you reassign that seat to the new hire.

The key is to treat licenses like vehicles:

• You do not park them just to "save" them.
• You assign them intentionally to people responsible for revenue and service.

Keeping Your System Clean As The Org Chart Shifts

Every time you add or remove someone, you have a choice:

• Let logins accumulate and confuse reporting.
• Or treat changes as a chance to tidy roles and responsibilities.

Good practice with ProValet:

• Deactivate users as soon as they leave.
• Reassign routes formally rather than informally "covering" them.
• Ensure each active user's role matches their permissions and daily work.

Because the ProValet Homeowner App is not licensed per user, none of this impacts the customer side. Homeowners continue to see visit history, photos, notes, and invoices without interruption. The internal structure can change: the external proof of care stays consistent.

Per-User Licensing And Profit: Where The Leverage Actually Comes From

Per-user conversations usually stop at, "How much per seat?" That is incomplete.

The better question is: "What is my revenue and profit per seat, and how does this system move that number?"

From "More Seats" To "More Revenue Per Seat"

In a route-based, recurring operation, profit doesn't come from hiring endlessly. It comes from:

• Higher route density.
• Fewer re-dos and complaints.
• Faster, cleaner billing and payments.

With ProValet, each licensed user should unlock more output:

• Owners see real-time performance and make route adjustments once, not every Friday in a panic.
• Office staff manage exceptions: the system handles the standard work.
• Techs document work with photos, notes, and timestamps in seconds.

That is why we care about revenue per seat far more than raw seat count.

Using ProValet To Increase Revenue Per Tech And Per Route

ProValet gives you tools that directly affect the economics of each route:

• Scheduling built for recurring routes, not one-off jobs, so techs waste less drive time.
• Active Invoicing™ + Payments so completed work reliably turns into cash without manual chasing.
• ProValet Homeowner App so customers see proof-of-service and pay faster, with fewer billing disputes.

The compounding effect:

• More stops per day because routes are tighter.
• Less unpaid time resolving "Did you really come?" questions.
• More predictable cash flow because AutoPay and configured convenience fees protect your margins.

Per-user licensing is simply the frame. The leverage comes from how that frame encourages you to run a tight, disciplined operation where each licensed user carries a clear slice of recurring revenue.

How ProValet’s Apps Fit Into The Licensing Model

Licensing is easier to understand when you see how the different ProValet apps behave in the field.

The split is simple:

• Internal users: paid seats.
• Homeowners: unlimited, no-seat access.

Technician App: Field Execution Without Extra Overhead

Each technician running a route gets access to the ProValet Technician App. That license covers everything they need to:

• See and run their optimized route.
• Capture photos, notes, chemical readings, or tasks.
• Timestamp visits and complete jobs.
• Trigger Active Invoicing™ automatically on job completion.

We designed the Technician App to be offline-first, fast, and focused. Techs are not doing office work on a tiny screen. They are confirming they were there, what they did, and that the job is complete.

This is where licensing meets operations:

• One technician app license should correspond to one consistently productive route.
• As routes become denser and more efficient, the revenue per technician license increases.

Homeowner App: Unlimited Customer Access Without Extra Seats

On the homeowner side, there is no meter running.

The ProValet Homeowner App:

• Is available for unlimited customers.
• Does not consume ProValet user licenses.
• Gives homeowners access to visit history, photos, notes, timestamps, and invoices.
• Enables two-way messaging and one-tap payments.

This structure matters:

• You can add as many homeowners as you like without checking a seat counter.
• You can push more communication into the app, reducing calls and texts to the office.
• You gain the best retention tool you have: visible proof-of-service on every visit.

The ProValet Homeowner App, combined with Active Invoicing™ and the Technician App, is how licensing turns into leverage. You pay for the internal engine: the customer-facing trust layer scales without extra cost.

How ProValet Compares To Other Pricing Models You May Have Seen

You have likely been pitched several different pricing models. Each has tradeoffs.

Our goal here is not to insult competitors, but to make the category differences clear so you can choose deliberately.

Flat-Rate, Per-Route, And Feature-Gated Models

You will often see:

• Flat-rate per company: One fee for "everything."
• Feels simple.
• Often hides feature or usage caps that show up as you grow.
• Per-route pricing: You pay based on route or truck count.
• Aligns loosely with operations.
• Can become blunt: not all routes carry equal revenue.
• Feature-gated tiers: Basic, Pro, Enterprise.
• Entry price is low.
• Key features (customer app, advanced billing, reporting) often sit in higher tiers.

Many of these models were designed for appointment-driven or generic field service, not for recurring route operations. The result is often a mismatch between how you earn money and how you pay for software.

ProValet uses per-user licensing because it more closely mirrors how route-based, recurring service businesses scale: through people running consistent routes and processes.

What To Watch For In Contracts And "All-In" Offers

When you evaluate any software, look past the headline number and into structure:

• Customer access: Is the customer app or portal extra? Are there limits on messages or logins?
• Billing and payments: Are AutoPay, convenience fees, and online payments included, or are they add-ons?
• Data migration: Is moving your existing customers and schedules into the new system a project billed separately?

With ProValet:

• ProValet Homeowner App access is included for unlimited customers and is central to reducing disputes.
• Active Invoicing™ + Payments is part of the core system, including support for configurable convenience fees to protect margins.
• Zero-Friction Data Migration™ is our structured process for launching you with clean, organized data.

You work hand in hand with a ProValet Success Manager, drag-and-drop your export, and get to a live system without data chaos. Zero-Friction Data Migration™ exists to eliminate switching fear, so licensing conversations are about the future, not anxiety about the past.

A Simple Framework For Deciding If ProValet’s Licensing Fits Your Business

You do not need a spreadsheet with 20 scenarios. You need a clear lens.

Here is a simple framework.

Questions To Ask About Your Team, Routes, And Revenue Per Tech

Ask yourself:

1. Team

• How many people actually need to touch schedules, billing, or field execution daily?
• Are any of them doing double-duty because the system is weak, not because the role requires it?

2. Routes

• How many active routes do you run today?
• How many could each tech realistically handle with better route density and fewer exceptions?

3. Revenue per tech

• What is your average monthly revenue per technician today?
• Where do you want that number in 12–24 months?

Then map that against licensing:

• "With this number of owner/office seats and technician seats, can I reasonably reach my target revenue per tech and per route?"

If ProValet's per-user model helps you answer "yes" with discipline (not wishful thinking), it is a good fit.

Designing For Calm Operations, Not Maximum Headcount

There is a temptation to treat "unlimited users" as a kind of safety blanket. More logins, less thinking.

In practice, that mindset creates:

• Fuzzy accountability.
• Noisy data.
• A system nobody fully owns.

ProValet's per-user licensing nudges you the other way:

• Define roles clearly.
• Assign seats to people who genuinely move routes, revenue, or retention.
• Expect every licensed user to rely on ProValet as their daily operating base.

The outcome is not maximum headcount. It is calm operations:

• Recurring schedules that run automatically.
• Technicians who know exactly what to do each stop.
• Homeowners who see proof-of-care through the ProValet Homeowner App.
• Billing that flows through Active Invoicing™ instead of manual pushes.

If that picture matches the business you are building, the licensing model is working for you, not against you.

Conclusion

Install A Licensing Model That Serves The Business You Are Building

Licensing is not exciting. But it quietly decides whether your software feels like a stable foundation or a creeping overhead line you resent.

For route-based, recurring service businesses, the job of licensing is simple:

• Tie cost to the people who run routes and make decisions.
• Encourage clear roles and disciplined processes.
• Stay neutral as you grow routes, tighten density, and deepen long-term customer relationships.

ProValet's per-user model is built on those principles. You pay for:

• Owners and office staff who control schedules, exceptions, and cash.
• Technicians who execute work and create proof-of-service.

You do not pay for:

• How often homeowners open the ProValet Homeowner App.
• How many years you retain a customer.
• How many visits your recurring routes complete.

Around that licensing, ProValet builds four structural advantages:

• Zero-Friction Data Migration™, hand in hand with a ProValet Success Manager, you drag‑and‑drop your export and launch quickly with clean, organized data.
• Purpose-Built for Route-Based Service, designed for recurring routes, not appointment-driven dispatch.
• Active Invoicing™ + Payments, hands-free billing, AutoPay, payment options, and margin protection with configurable convenience fees.
• Homeowner App, turns every visit into visible proof (photos, notes, timestamps, visit history, two-way messaging, one-tap payments). It is your best retention tool because it makes professionalism visible and reduces disputes.

These are not extras. They are how licensing converts into leverage instead of cost.

Profit First Strategic Partnership (Select Companies)

For a subset of companies, ProValet also works as a Profit First strategic partner.

In those cases, we help you:

• Map Profit First concepts onto real routes and technician economics.
• Set practical allocation rhythms that match seasonal cash flow.
• Use licensing and automation as constraints that protect profitability instead of chasing volume at any cost.

The goal is simple: cash discipline, clarity, and sustainable profitability in a model built on recurring service, not one-time jobs.

FAQs (Short And Direct)

Q1: Does every technician need their own ProValet license?

Yes. Any tech running routes in the Technician App needs a license. That keeps accountability, route data, and performance metrics clean.

Q2: Do my customers need licenses to use the ProValet Homeowner App?

No. Homeowners use the ProValet Homeowner App without consuming licenses. You can invite as many customers as you like at no additional per-user cost.

Q3: What happens if I add or remove a team member mid-season?

You add a seat when someone needs ongoing access and reassign or deactivate it when they leave. Licensing flexes with your org chart: your customers continue to see consistent proof-of-service.

Q4: Is data migration included, or is that a separate project?

ProValet's Zero-Friction Data Migration™ is part of how we launch you. You work with a Success Manager to move customers, schedules, and history over cleanly, so switching fear and data chaos do not block progress.

Q5: How does ProValet's pricing compare to "unlimited users" platforms?

Unlimited user offers can look lower upfront but often add costs through caps, add-ons, and manual work. ProValet's per-user licensing is designed so each seat supports clear revenue and profit, with no extra charge for homeowner access.

Q6: Is ProValet only for a specific trade?

ProValet is built for route-based, recurring service businesses: pool, lawn, pest, home watch, pressure washing, window cleaning, and similar models that run stable routes and long-term customer relationships.

Next Step

If you want licensing to be a simple, predictable part of a broader operating system, rather than a quiet tax on growth, the next move is a conversation, not a calculator.

Reserve a Demo: https://go.provalet.io/discovery-call-2505

Call Val: (239) 522-5440

ProValet Per-User Licensing: Frequently Asked Questions

What is ProValet per-user licensing and how does it work for my team?

ProValet per-user licensing means you pay for the internal people who actually run your operation: owners, office/admin, dispatch/ops, and field technicians using the Technician App. Homeowners never count as users. This keeps software costs tied to real operating capacity instead of raw headcount or job volume.

Who needs a ProValet license and who can use the system for free?

Owners, GMs, operations leads, office/admin staff, and each field technician running routes in the Technician App need ProValet licenses. Homeowners do not. They use the ProValet Homeowner App for visit history, photos, messaging, and payments at no per-user cost to your business, regardless of how many customers you serve.

How should I size ProValet per-user licensing for my current routes?

Start with routes, roles, and revenue per tech. Map one owner/GM, 1–3 office/admin seats (depending on complexity), and one technician license per active route-running tech. Then ask: “Can this configuration support my target routes and revenue per tech without burning people out?” Adjust seats where bottlenecks appear.

Can my team share logins to reduce ProValet per-user licensing costs?

Sharing logins is strongly discouraged. It destroys accountability, confuses route and performance reporting, and makes security harder to manage when people leave. ProValet is designed so each licensed user corresponds to a distinct role and revenue responsibility, making it easier to measure and increase revenue per seat.

How does ProValet per-user licensing compare to flat-rate or “unlimited users” pricing models?

Flat-rate and “unlimited users” offers can look cheaper but often hide limits on customers, visits, or key features like customer apps and payments. ProValet ties cost to internal users while providing unlimited homeowner access, Active Invoicing™ + Payments, and Zero-Friction Data Migration™, so each seat is expected to justify clear revenue and profit.

Is ProValet per-user licensing a good fit for my type of field service business?

ProValet is purpose-built for route-based, recurring service operations—like pool, lawn, pest, home watch, pressure washing, or window cleaning—where routes, techs, and customers stay relatively stable. It’s usually not ideal for one-off emergency response or purely appointment-driven shops that live on ad-hoc dispatching.