The operating system for service businesses
The work happens out there. The business runs here.
ShieldBook puts every customer, job, estimate, invoice and payment on one record, so the technician's phone, the office's screen and the customer all see the same job.
- In the fieldMarcus starts the visit and finds the failed element.
- In the officeDana sees the visit and the approved estimate as they happen.
- With the customerElena chooses Option B and signs from her own phone.
01Who it's for
Built for the businesses that show up.
If your work happens in someone's home, building, property or job site, your business runs on the same things: customers, properties, jobs, people in the field, estimates, invoices and payments. ShieldBook is built on that shared core, not on one trade.
- PlumbingWater heater replacementScheduled · 8–10 AM
- ElectricalPanel upgradeOn the way
- HVACNo cooling, second floorIn progress
- RoofingLeak inspection after stormCustomer approved
- Pest controlQuarterly serviceVisit complete
- RemodelingKitchen estimate, three optionsScheduled · 12–2 PM
- HandymanPunch list, eight itemsPaid
- PaintingExterior repaintScheduled · 8–10 AM
- FlooringHallway and two bedroomsOn the way
- CarpetThree bedrooms, new padIn progress
- LandscapingIrrigation repairCustomer approved
- Pool serviceWeekly service and filter cleanVisit complete
- CleaningMove-out cleanScheduled · 12–2 PM
- Garage doorsSpring replacementPaid
- Appliance repairDryer not heatingScheduled · 8–10 AM
- RestorationWater damage, first visitOn the way
- ConcreteDriveway replacementIn progress
- DrywallCeiling patch and textureCustomer approved
- General contractingBathroom remodel, phase twoVisit complete
- Specialty contractingFence repair, 40 feetScheduled · 12–2 PM
Every job, in any trade, becomes one record
- CustomerElena Martinez
- Property418 Larkspur Ln
- EquipmentWater heater
- JobJOB-2048
- VisitTue 8–10 AM
- EstimateEST-1187
- InvoiceINV-1093, paid
- MembershipHome Care Plan
One record per customer and property, shared by every job, visit and invoice that follows. Trade-specific templates for concerns, equipment types and price books are On the roadmap
02How it works
From the first call to the next one.
In most service businesses the same customer is typed into four different tools. In ShieldBook the record moves with the work: the inquiry becomes the customer, the visit becomes the estimate, the approval becomes sold work, and the work becomes the invoice.
First call
The inquiry becomes the customer.
Capture who called, where the work is and how they found you. The customer, their property and the source are recorded once, and everything after builds on them.
- Customer
- Property
- Source
On site
The visit already knows the property.
The technician arrives with access notes, equipment and history in hand, starts the visit, takes photos and records what they found: concern, cause, correction, recommendation.
- Job
- Visit
- Photos
- Equipment
The decision
Options, not a single take-it-or-leave-it price.
Build options from your price book, present them on the technician's device, and record the customer's approval with a signature in person or through a secure link.
- Estimate
- Options
- Signature
Sold and scheduled
Approval is recorded. The sale is its own step.
The office sees what is approved but not yet sold, marks it sold, and schedules the work with an arrival window and a technician. Nothing waits in someone's head.
- Sold work
- Schedule
- Technician
Paid
The work becomes the invoice.
Sold work is billed as approved, deposits are credited, and every payment is recorded against the invoice: card, cash, check or split across several.
- Invoice
- Deposit
- Payment
The next visit
And the relationship keeps going.
A membership brings member pricing and planned visits. The next call starts with everything you already know about the customer, the property and the equipment.
- Membership
- History
- Next visit
Nothing re-entered. The same customer, property and equipment carry into every job that follows.
03The platform
One record at the core. The whole business around it.
ShieldBook is built in layers on one shared record, so every part of the business reads and writes the same customer, job and invoice. No layer is a separate product bolted on.
In development On the roadmapEverything else is built and working today.
Customers and properties
The record everything else builds on.
- Customers and contacts
- Properties and access notes
- Equipment, warranties and service history
- Activity history of every action
Field operations
The day, from the office board to the technician's phone.
- Jobs and job summaries
- Visits with arrival windows and outcomes
- The technician's day on the phone
- Job photos
- Office work queues
- (In development)Dispatch board and calendar
- (In development)On my way and Arrived updates
Sales
Options, presentation and a recorded decision.
- Estimates with options
- Tiered replacement options
- Present mode
- Approval and signature
- Price book
Money
From sold work to collected payment.
- Invoices
- Deposits
- Payments, split payments and refunds
- Estimate and invoice PDFs
- Receivables
- (In development)Online card payments and payment links
- (On the roadmap)QuickBooks Online
Recurring revenue
Memberships and the next visit.
- Memberships and member pricing
- (In development)Maintenance due
- (On the roadmap)Recurring work and renewals
Communication
Every message tied to the record.
- Email with delivery and opened status
- (On the roadmap)Two-way texting and reminders
- (On the roadmap)Automation rules
AI and growth
On the same foundation, with the same rules.
- Roles and server-enforced permissions
- Marketing source on every inquiry
- (On the roadmap)Permission-scoped AI agents
- (On the roadmap)Lead intake and nurture pipeline
- (On the roadmap)Closed-revenue attribution
- (On the roadmap)Business analytics
04Sales and estimating
Give customers real options. Record a real decision.
Options from your price book
Build as many options as the job deserves, from your own items, with discounts and member pricing where they apply.
Present on the technician's device
Walk the customer through what you found and what each option includes, with the total and what a member saves.
Approve and sign, anywhere
A drawn or typed signature in person, or approval later through a secure link the customer opens on their phone.
Approval is not a sale
The customer's approval and your decision to sell the work are separate steps, so the office always knows what still needs attention.
05Field operations
The same visit, from both sides.
The technician's phone and the office's screen show one record. When a visit ends in the field, the office already knows how, and what happens next.
In the field
- The current visit with access notes, gate codes, equipment and history
- Start the visit, take photos and write the job summary
- Eight ways a visit can end, each creating the right follow-up
- Call, text and get directions from the visit
In the office
- Today's visits with arrival windows, technicians and what is unassigned
- Approved but not sold, sold work to schedule, work done but not invoiced
- Schedule, reschedule and reassign from the record
In development Next for the field: a dispatch board and calendar with technician lanes, and On my way and Arrived updates for customers.
06Getting paid
From sold work to money in the bank.
Billed as approved
Sold work flows into the invoice exactly as the customer approved it. Deposits are credited on the invoice.
Every way people pay
Card, cash, check, Zelle or a mix. Split and partial payments, credits and refunds, all against the invoice.
Sent, delivered, opened
Estimates, invoices and receipts go out by email with a PDF, and you can see whether they arrived and were opened.
Know what is owed
Receivables shows every open balance and how many days it is past due.
Online payments In development
A pay page for the customer with card, Apple Pay and Google Pay, and payment links you can send from the invoice. Built and in testing before it goes live.
Recurring revenue
The next visit is already on the books.
Membership plans put member pricing on every estimate and plan the visits through the year, and the customer's record carries their properties, equipment and history into the next job.
In development Next: a maintenance-due list that shows which members are ready for their visit.
07AI in ShieldBook
AI that works inside your rules.
Not a chat window bolted onto your data. ShieldBook's direction is agents that understand the business's real context and act through the same permissions, rules and records as your people, with every action recorded and a person approving anything that matters.
Office assistant AI agent · acting for Dana
Follow up on the 2 estimates approved but not yet sold.
- Passed
Permission
May draft customer follow-ups. May not mark work sold.
- Passed
Business rules
Approval is not a sale. Drafts two emails, changes nothing else.
- Approve and send
Needs a person
Sending email is consequential. Dana reviews both drafts.
Activity
9:42 Email sent to Grant Whitfield, by Office assistant for Dana.
Its own identity
An agent is its own actor with its own permissions, never a shared staff login.
The same rules
Agents act through the same commands, permissions and business rules as your people. No shortcuts, no separate AI versions of actions.
Every action recorded
The activity history shows what an agent did, when, and who it acted for.
People approve what matters
Sending, refunds, voids, pricing and scheduling commitments wait for a person to approve them.
Your choice of AI
One controlled interface, not tied to a single AI provider.
The foundation is already in place.
Roles and permissions are enforced on the server, and every action already lands in an activity history with a name on it. Agents will use exactly that: the same rules, the same record, the same history. The agents themselves come next.
08Marketing and growth
Know which marketing actually paid.
Today every inquiry records how the customer found you. The direction is a growth system on the same record, so you can see not only where a lead came from, but which campaign created the customer, which jobs followed, and how much revenue it produced.
- CampaignSpring water heater adsSpend and creative(On the roadmap) Planned
- InquirySource: Google AdsRecorded on every inquiryIn ShieldBook today
- CustomerElena MartinezProperties and equipmentIn ShieldBook today
- Jobs2 jobsRepair visit, replacementIn ShieldBook today
- Revenue$2,928 collectedTraced back to the campaign(On the roadmap) Planned
Where ShieldBook's growth system is going On the roadmap
- Lead capture, follow-up and nurture
- Campaigns and advertising
- Websites, SEO and content
- Texting and voice AI
- Marketing agents
- Closed-revenue attribution
- Business analytics
09Why ShieldBook exists
Born 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. The call, the visit, the estimate, the invoice and the follow-up lived in different places, and the office spent its day moving information between them.
So Service Shield built its own system. ShieldBook is now being developed and proven there, as the platform prepares for broader use.
- Where it started
Built for one service business
Service Shield needed a system that matched how its work actually runs. The first version was built in-house and is still in daily use.
- Now
Proven inside a working company
ShieldBook is being rebuilt as a full platform and proven against Service Shield's real days in the field.
- Next
Built for the businesses that work in the field
The platform is preparing for broader use by service businesses in every trade.
The rules ShieldBook is built on
Approval is not a sale.
A customer saying yes and the business committing to the work are recorded separately, so nothing falls between them.
The phone comes first.
Field workflows are designed for a technician standing in a driveway with one free hand.
Record facts. Show what they mean.
ShieldBook stores what happened and works out the status from it, so the screen never disagrees with the record.
No false states.
No workflow makes you record something untrue just to move on. A locked gate is a visit outcome, not a finished job.
Every action has a name on it.
An append-only history records who did what, and when.
Permissions live on the server.
Five roles, enforced where the data is, not just hidden in the interface.
Request a demo
Every job starts with a first call.
Make this one yours. Tell us how your business runs, and we'll walk you through ShieldBook on the workflows that matter to you.
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.