Software for a diary full of dogs and a phone that never stops.

It is one system for the salon day: the groomer diary, online booking, pet and owner records, vaccine and groom notes, reminders, checkout with tips, and payroll per groomer. The diary, the pet record, the message, and the payment all read from the same appointment, so a visit completed at the table updates everything at once.

The first release covers one complete path, from a booked appointment to a paid groomer: the diary, online booking, the pet record, reminders, checkout with tips, and payroll. Mobile vans, multi-location reporting, and loyalty come after the core salon day works.

Customers book from the service list with the groomer, the time, and the price shown up front, and the booking lands on the right diary with the pet record attached. A deposit can be taken at booking, and the slot closes everywhere at once, so the same chair is never promised twice. The groomer sees the cut notes and the temperament warnings before the dog arrives.

Every pet keeps its vaccine state on the record with the expiry date, and the system flags anything missing or out of date before the appointment. The front desk can ask for the record at booking instead of discovering the gap at the door. The record belongs to the pet, not to one groomer, so it follows the dog across chairs, vans, and locations.

Each dog carries its own notes: the cut, the blade and guard, the products used, the temperament warnings, and what worked last time. The notes are written at the table after the groom and read before the next one, so a new groomer can pick the dog up without asking the owner to explain the cut again. Notes never live in a groomer's head or on a paper card in a drawer.

Reminders go out automatically before the appointment, and a card on file lets the salon charge a staff-confirmed no-show fee when the policy allows it. The fee is set by the salon and confirmed by staff, not taken silently. Over time the record shows which customers no-show and which ones always confirm, so the reminder rules can be tuned to the customers who need them.

Tips and commission are calculated from the appointment itself: who groomed, who bathed, what was charged, and what was tipped. The breakdown is visible per groomer, per day, and per pay period, so payroll is read off the record instead of rebuilt from memory. The groomer who earned the most is paid right, and on time.

Payroll reads the same record as the diary: appointments completed, services done, products sold, tips taken, and commission earned. The salon sets the commission and the pay period once, and the report is ready when the period closes. A task that used to take an evening of cross-checking paper and digital reports becomes a report the owner reviews and approves.

Yes. Each van keeps its own diary, route, and pet records, and the owner sees all of them on one board. Route planning groups the day by neighbourhood so the van drives a tight loop, and the groomer works offline between stops and syncs when the signal returns. A mobile fleet is the usual point where a salon-only diary stops being enough.

Yes. Each location keeps its own diary, chairs, and groomers, and the owner sees all of them on one dashboard. A pet record follows the dog across locations, and a booking can never assign the same groomer to two places at once. The morning routine that breaks around the third location is the usual point where one shared record stops being optional.

Yes, for taking payments. Keep the reader you already use and connect each payment to the appointment it belongs to. The management system runs the salon around the till: the diary, the pet record, the reminders, the tips, and the payroll. The till takes the money; it does not know which groomer earned it or which dog was on the table.

The temperament warnings on the pet record are shown before the appointment, not discovered at the table. A difficult dog can be booked with the right groomer, the right time, and the right notes, or declined with the reason recorded. The record protects the groomer, the dog, and the salon, and it keeps a bad experience from repeating with a different groomer.

Buy a maintained platform when it covers the salon. Platforms built for grooming already handle the diary, online booking, pet records, reminders, checkout, and payroll, and that is the right call for most salons. Build custom when the operation breaks the template: a mobile fleet with route planning, several locations sharing one pet record, a franchise model with its own rules, or payroll and reporting your owners require. Compare the platform fee on every appointment against the cost of owning the system before you decide.

For a small, well-defined task with someone technical managing it, freelancers are often cheaper. The pattern that goes wrong is a non-technical buyer coordinating several freelancers becoming the project manager, the tester, and the person who discovers the pieces do not fit. A pet grooming management company earns its fee when the work needs coordination across the diary, the pet record, reminders, checkout, tips, and payroll: one accountable party, one phase price, and checkpoints against the whole day. If your need is one screen or one fix, hire the freelancer.

The first paid phase may cover a bounded audit, a proof of concept, a recovery plan, or a small first release. The final price depends on how many chairs, groomers, locations, and vans the system covers, whether mobile routes, multi-location reporting, and loyalty are in scope, what it needs to connect to, and whether data needs moving over. The agreed phase is priced in writing before it starts. Our build vs buy guide works through the cost bands for each phase in detail.

You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the salon routine agreed at the start: a booking from the customer side, a vaccine flag before the appointment, a no-show fee the staff can confirm, a tip breakdown per groomer, and a payroll report that matches the diary. Progress is reported in plain language: what changed, what's next, and what it costs. Because you own the code, the accounts, and the operating notes throughout, nothing about the work is locked inside our heads. Our job is to make the work checkable; your job is to check it against your business.

You own the code built for you and control where it lives, the cloud accounts, the data, analytics, and third-party subscriptions. Outside services and open-source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over.

We need one person who owns the operation, access to the relevant users and systems, timely answers on business rules, and someone who can accept or reject each milestone. A weekly working session is usually enough once the scope is stable. Your team should not have to manage developers day to day. The team that scopes your project is the team that does the work: no handoff to another vendor after you sign, and you can talk to the people doing the work directly.

Yes. Takeover is a common first engagement, and it always starts with an audit: where the code lives, how your data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live. Code that is understandable and fit for the next release stays; only the parts blocking reliability get replaced. AI-built prototypes from Lovable, Replit, Bolt, or v0 can be assessed as starting points. And if you already paid another vendor and have nothing working, the audit tells you which story you have before you spend more.

Ask for the quote to name everyone who will use the system, including your own groomers and front desk. Every platform has two products: what customers see, and what your people use all day: the diary, the pet record, the reminders, the checkout, the payroll, and a record of who did what. When that second product is quoted as an 'admin panel' on a single line, it becomes the overrun. Our quotes treat your team's screens as their own scope, with their own users. Then the phase names the workflow, what 'done' looks like, the price, and the exclusions, all before paid work starts. You review working software at agreed checkpoints, and when new information changes the scope, you hear the effect on price and timing before anything is approved.

Every launch includes post-launch warranty cover for defects in the agreed scope, release support, and small screen corrections. After that, work can continue as another fixed phase or an ongoing product engagement. The code and accounts stay under your control either way.