Why ShieldBook
Built inside a working service business.
ShieldBook started inside Service Shield, a working service company, because the tools available didn't match how the business actually ran. It's being built into the operating system for service businesses of every trade.
01The origin
Software written by the business that has to run on it.
Most field service software is designed from the outside, by people who imagine how a service business works. ShieldBook was designed from the inside, by a business that has to answer the phone, send the technician, collect the payment and do it all again tomorrow.
That changes the details. Approval and the sale are separate steps because a missed sale costs real money. The technician's screen is built for a phone in one hand because that's how the work is done. Every action has a name on it because when two people remember it differently, someone has to know.
Where it started
One service business, and tools that didn't fit
Service Shield's calls, visits, estimates, invoices and follow-ups lived in different places. The office spent its day moving information between them. So the company built its own system, and that first version is still in daily use.
Now
A full platform, proven on real days
ShieldBook is being rebuilt as a complete operating system and proven against Service Shield's real days in the field, on technicians' own phones, before anything is called finished.
Next
Every business that works in the field
The platform is preparing for broader use by service businesses in every trade: built on the same record, the same rules and the same honesty about what's finished.
02What we believe
Principles you can see in the product.
Each of these is a rule ShieldBook is built on, not a slogan. You'll find every one of them in the screens.
Approval is not a sale.
A customer's yes and a business's commitment are different facts. Software that blurs them loses work between the two.
The phone comes first.
The people doing the work are standing in driveways, attics and basements. Field workflows are designed for one hand and a bad signal.
Record facts. Show what they mean.
ShieldBook stores what happened and works out the status from it, so the screen can never disagree with the record.
Rules belong on the server.
Hiding a button isn't security. Every action is checked against the person's role, and recorded with their name.
One record, whatever the trade.
Customers, properties, jobs and invoices describe a service business, not a trade. Trades differ in their details, not their shape.
Say what's built.
This website labels everything that isn't finished. A product you'll run your business on should be described the way it is.
03How it's built
Careful, on purpose, in that order.
Built in slices, proven before the next
Each part of ShieldBook is built end to end, from the database to the phone screen, and checked by the owner on a real iPhone before the next part begins.
One action, many ways to call it
Every business action is written once. The screen, an integration and, one day, an AI agent all go through the same rules.
History that can't be rewritten
The activity history is append-only. What happened, who did it and when stays on the record.
Designed with the people it's for
The office staff and technicians whose days it's built around shape what gets built next.
04Where it's going
Operations first. Then growth, then AI.
ShieldBook is being developed and proven inside a working service business as it prepares for broader use. The daily operations are built. Scheduling on a full calendar and online payments are in development. A growth system and AI agents are the direction, built on the same record and the same rules.
Keep exploring
- Platform How ShieldBook carries one record through the whole service lifecycle: inquiry, customer, property, job, estimate, approval, scheduling, field work, invoice, payment, follow-up and repeat business.
- Industries ShieldBook is built for businesses whose work happens at customers' homes, buildings, properties and job sites: HVAC, plumbing, electrical, roofing, pest control, remodeling, handyman and more.
- Product Customers and properties, jobs and visits, estimates and approvals, invoices and payments, memberships, communication and permissions, in one connected system.
Talk with the people building it.
A demo is a walkthrough of ShieldBook on the work that matters to you, and an honest conversation about fit.
ShieldBook is being developed and proven inside a working service business as it prepares for broader use. A demo is a walkthrough and an honest conversation about fit.