Client relations
A CRM where the customer record is the work.
Everything about a client in one place: what you quoted, what the crew did, what they owe, and the thread you have been having with them. Plus a login of their own to approve quotes, pay, save a card and ask for more work.
$297/month, per company, unlimited users, no per-seat pricing. Month to month. Cancel anytime. No setup fee.
The real software, recorded against a demo landscaping company. Every figure on screen is theirs and the company is fictitious.
A contact card is not a customer record.
Most CRMs came out of sales, where the valuable thing is a person and a stage in a funnel. In this trade the valuable thing is a property and a history: what is planted there, what you charged last spring, which gate code, which dog, what they complained about in June, and whether the invoice from August ever got paid.
A system that stores the person but keeps the work somewhere else makes you open two things to answer one question, which is why so many of them end up unused next to a spreadsheet that has the answers.
One record, and the work hangs off it.
In Platy, a client holds the quotes, the jobs, the visits, the invoices and the messages. Opening the client is how you find out where things stand, because there is nowhere else for the answer to be.
When somebody calls and asks what you charged them last year, that is one screen. When a crew lead needs to know what the gate code is, it is on the stop in their app, because it is on the same record.
Texting, from the screen with the job on it.
Two-way texting with customers happens from the same screen as their work, so the thread and the job are not in different applications. Opt-outs are handled for you, which is not a convenience feature: unsolicited texting is regulated, and a system that lets you text somebody who asked you to stop is a system that hands you a problem.
What it does not do is run campaigns. There is no bulk send and no marketing sequence. This is the conversation you were already having, in the place the work lives.
And they get a login, which is where the repeat work comes from.
Every customer can open their own hub to approve a quote, pay an invoice, save a card and ask for more work. The last one is the one owners underrate. A request that arrives in the system is a job you can quote. The same request as a voicemail is something somebody has to remember.
Recurring maintenance repeats on its own cadence alongside all of it, so the relationship that is supposed to run all season does, without being rebooked by hand every few weeks.
What the client side gives you.
Shipped, and recorded above against a demo company.
- One client record holding quotes, jobs, visits, invoices and messages
- Two-way texting from the same screen as the job, with opt-outs handled for you
- A customer login to approve quotes, pay, save a card and ask for more work
- Requests arriving as work you can quote, not as voicemail
- Recurring maintenance that repeats on its own cadence
- The same record the crew sees on the stop, gate code and all
Questions owners ask
Is this a sales CRM with deal stages?
Can I text customers from it?
Does it send marketing or chase reviews?
What can the customer do in their own login?
Can I bring my client list over?
The rest of the same system
Platy is one system, so none of these is a separate product or a separate bill. They are the other jobs the same software is doing while it does this one.
Invoicing and payments
A finished job becomes a real invoice, and the card payment lands in your own account.
Scheduling and routing
Book the visit, assign the crew, and the day orders itself into a loop the truck can drive.
Quoting
Describe the job out loud and get a priced draft back, from your own numbers.
Open one client and see the whole history.
Load a handful of real clients and the work you did for them last season. The test is whether you can answer a customer’s question without opening anything else.