H&S TechnologiesQUÉBEC
FRSchedule a conversation

All trades

GarageOS

Auto repair shopConfigurable

The vehicle, the approval and the bay in one system — so nothing gets decided by text without leaving a record.

ConfigurableThe vehicle is a SECOND central object, and it carries money — something the standard offer explicitly excludes. Migrating service history from a legacy system is the heaviest item, and the only one nobody can size without seeing the file.

What leaks today

None of these observations is a measurement taken at a client: H&S has delivered none. They are mechanisms of the trade — any amounts shown are examples, never results obtained.

The call comes in while you're under a car

Nobody answers, nobody calls back, and the customer calls the next shop. The missed call leaves no record: it exists nowhere to be recovered.

Approval is given over the phone

The advisor calls, the customer says yes to the brakes but not the suspension, and the next day nobody knows exactly what was authorised. The argument over the invoice happens at pickup.

Estimates sit

An inspection surfaces $2,000 of work, the customer wants to think about it, and nobody follows up. The work goes elsewhere, or nowhere.

The bay waits, or overflows

Appointments are booked on theoretical duration, not real duration. An empty bay at 2 p.m. and three vehicles for 8 a.m. the next day.

The vehicle's history is in the mechanic's head

What was done two years ago, what was declined, the part flagged "watch this": none of it is attached to the vehicle, all of it is attached to a person.

Recurring service never recalls itself

A customer who comes twice a year is worth several who come once. The reminder depends on somebody thinking to send it on a quiet Tuesday.

The core takes the trade's shape

GarageOS — Configurable. The vehicle, the approval and the bay in one system — so nothing gets decided by text without leaving a record.

Sector operating model

The trade's vocabulary, objects and stages
  • Vehicle record
  • Service history
  • Inspection
  • Estimate
  • +8 more
H&S coreGarageOSThe vehicle, the approval and the bay in one system — so nothing gets decided by text without leaving a record.Configurable

Client configuration

What separates this business from its neighbour in the same trade
  • YOUR shop's stages
  • Labour rates and packages
  • Estimate and work-order templates

Ongoing operations

What happens afterwards
  • Hand-off to accounting
  • Shop dashboard
  • Multiple locations

Automations

The work that happens without anyone thinking about it
  • Missed-call recovery
  • Estimate follow-ups
  • Service reminders
  • Multi-channel follow-up
  • +1 more

Data

Migrating what exists and what the system will be able to say about the past
  • Service-history migration

Implementation

Actually going live

Nothing declared at this layer

ConfigurableThe vehicle is a SECOND central object, and it carries money — something the standard offer explicitly excludes. Migrating service history from a legacy system is the heaviest item, and the only one nobody can size without seeing the file.

Layers and modules read from the vertical's record — none is added to fill space.

What the system contains

Every module carries what it really is: included, available from the catalogue, dependent on an integration, or still to be built. A module that needs work says so where it is read.

The modules

  • Customer recordsIncludedOne record per person or fleet, with every vehicle attached to it.
  • Enquiry queueIncludedCalls, missed calls, forms and texts in a single queue.
  • Customer spaceIncludedThe customer sees their estimate, approves, and follows progress without calling.
  • Vehicle recordIncludedThe vehicle exists in its own right: it changes owner, its history stays.
  • Service historyIncludedWhat was done, what was declined, and what was flagged to watch.
  • InspectionIncludedA checklist of inspected items, with photos, that becomes the basis of the estimate.
  • EstimateIncludedSeparate lines, a clear total, and a validity date.
  • Line-by-line approvalIncludedWhat was authorised is written, dated, and nobody has to remember it.
  • Work orderIncludedIt contains only what was approved, and carries the time actually spent.
  • Bays, technicians and capacityIncludedThe day is visible on one screen: what's on a lift, what's waiting, what's overflowing.
  • Tire storageAvailableThe stored set is attached to the vehicle, with its location and its return season.
  • YOUR shop's stagesIncludedStages carry your words. A shop that says "on the lift" does not read "in production".
  • Labour rates and packagesIncludedYour rates, your service packages, your fleet discounts.
  • Estimate and work-order templatesIncludedYour documents, with your logo and your wording.
  • Missed-call recoveryIncludedA text goes out within the minute, with a booking link.
  • Estimate follow-upsIncludedAn unanswered estimate is chased on a written cadence, and stops on reply.
  • Service remindersIncludedBy date or by expected mileage, with no list to prepare.
  • Multi-channel follow-upAvailableThe message follows the channel the customer actually answers on.
  • Dormant customer reactivationAvailableThe list of vehicles not seen builds and chases itself.
  • Service-history migrationCustom buildThe vehicles' past comes into the new system instead of staying in the old one.An established shop's history exceeds the standard offer's migration template, and the old system rarely exports it cleanly. This gets quoted after seeing the file, never before.
  • Parts inventoryCustom buildKnowing what's on the shelf, what's reserved, what needs ordering.Inventory is not part of the standard offer. The system knows a part was fitted; it does not hold stock.
  • Supplier orderingRequires an integrationOrdering the part from the work order, and tracking its arrival.No connector to a parts distributor exists at H&S. The "part ordered" stage is tracked by hand until one does.
  • Standard repair timesRequires an integrationEstimating a job's duration from a published schedule rather than from memory.These schedules belong to third-party publishers and are licensed. H&S holds none and is connected to none.
  • VIN decodingRequires an integrationEntering the VIN and watching make, model, year and engine fill themselves in.No decoding service is integrated. The VIN is entered and stored; it fills nothing in on its own.
  • Hand-off to accountingRequires an integrationWhat is invoiced here reaches the accountant without retyping.The catalogue's accounting module is not sellable yet: its real cost has not been measured.
  • Shop dashboardIncludedWhat's coming in, what's stalling, what's on a lift, what's awaiting approval.
  • Multiple locationsAvailableEach location has its own bays and calendar; management sees the whole.

The same file, end to end

This is neither a timeline nor a measurement: it is the path of one file, in the trade's own words.

From enquiry to booking

From enquiry to booking

TriggerA call, a missed call, a form, a text, or someone at the counter.

  1. The enquiry landsStep 1 of 5
  2. Missed-call recoveryAutomatedStep 2 of 5
  3. The vehicle is identifiedStep 3 of 5
  4. The slot is bookedStep 4 of 5
  5. Reminder before the appointmentAutomatedStep 5 of 5

OutcomeA confirmed appointment, attached to an identified vehicle and a written reason.

From inspection to work order

From inspection to work order

TriggerThe vehicle is in the shop and the inspection is done.

  1. Findings are recordedStep 1 of 6
  2. The estimate is builtStep 2 of 6
  3. The customer receives itAutomatedStep 3 of 6
  4. They approve line by lineStep 4 of 6
  5. The work order opensStep 5 of 6
  6. No reply, dated follow-upAutomatedStep 6 of 6

OutcomeA work order where every line was approved or declined by the customer, with date and time.

Time in the shop

Time in the shop

TriggerThe work order is open.

  1. Bay and technician assignedStep 1 of 4
  2. Work progressesStep 2 of 4
  3. Extra work is discoveredStep 3 of 4
  4. The vehicle is readyAutomatedStep 4 of 4

OutcomeThe vehicle is ready, and the customer knows before having to call.

Handover and after

Handover and after

TriggerThe customer collects the vehicle.

  1. PaymentStep 1 of 4
  2. The review requestAutomatedStep 2 of 4
  3. Declined work becomes a reminderAutomatedStep 3 of 4
  4. The next serviceAutomatedStep 4 of 4

OutcomeThe file is closed, paid, and the next visit is already scheduled.

Waking dormant customers

Waking dormant customers

TriggerA vehicle has not returned within a window the shop chooses.

  1. The list builds itselfAutomatedStep 1 of 3
  2. The message goes outAutomatedStep 2 of 3
  3. Opt-out is honouredAutomatedStep 3 of 3

OutcomeA booking, or a written reason to stop chasing.

What happens without anyone thinking about it

Missed call → textIncludedWhen — A call goes unanswered during opening hours.Then — A text goes out within the minute with a booking link, and the enquiry enters the queue.
Unanswered estimate → follow-upIncludedWhen — A sent estimate has received neither acceptance nor refusal.Then — It is chased on a written cadence, with the amount and the part being held, if any.
Appointment → reminderIncludedWhen — An appointment is approaching.Then — Confirmation then reminder, with the option to move it without calling.
Vehicle ready → customer notifiedIncludedWhen — The work order moves to "ready".Then — The customer gets the notice and the amount, and can pay in advance by link.
Handover → review requestIncludedWhen — The vehicle was handed over a few hours ago.Then — A message invites a review, with a link.
Service due → reminderIncludedWhen — The expected date or mileage is reached.Then — A reminder goes out with the expected work and what was declined last time.
Declined work → resurfaces next visitIncludedWhen — A vehicle with previously declined work returns to the shop.Then — The advisor sees the declined items before doing the inspection, not after.
Vehicle not seen → reactivationAvailableWhen — The window the shop chose has passed.Then — A reactivation campaign goes out, stopping automatically at the first sign of refusal.

H&S core

People recordsOne record per person, holding everything said and done, whoever on the team wrote it.
Company recordsThe client company exists separately from the people who work there: contacts change, the history stays.
Incoming enquiriesEverything that comes in — call, email, form, text — lands in one queue with its source attached.
Open opportunitiesWhat can still turn into money, with its stage, its owner and the date it must be picked up again.
Stages and lifecyclesStages carry the trade's vocabulary, and every move from one stage to the next is recorded with its date.
Tasks and remindersWhat has to be done today, by whom, with the reminder that fires on its own as the date approaches.
AppointmentsBooking, attendees, the agenda and what came out of it, all attached to the file.
ConversationsEmails, texts and calls attached to the right file, sent under your name and signature.
Documents and templatesThe documents the business sends are produced by the system, with its own fields, and stay attached to the file.
Access rightsEveryone sees what concerns them, and access for someone who leaves is removed in one move.
ApprovalsAnything that commits the business waits for a named approval, and the refusal is kept just as the consent is.
History and audit trailWho changed what, when, and from what state. It is what lets you answer six months later.
NotificationsThe system tells the right person at the right time, rather than waiting for someone to remember to look.
FormsWhat the customer fills in lands straight in the system, with no retyping and no copy-paste.
QuotesThe quote is built in the system, goes out dated, and its fate — viewed, accepted, declined — is tracked.
Client portalThe customer signs in with their own access, sees where their file stands, and writes in the same thread as the team.
DashboardsThe state of the week on one screen: what is coming in, what is stalling, what is waiting on an answer.
AutomationsFollow-ups, reminders and escalations go out without anyone thinking about it, and stop the moment the customer replies.
Taking paymentOnline payment, subscriptions, and reconciling what was paid against what was promised.

Neighbouring systems

An integration is never part of the standard offer, whatever its state here. “To be built” means it does not exist in our code yet.

Running at H&SEmail sendingEstimates, confirmations and written follow-ups under your name.
Tested dry-runText messagingThe channel a garage customer actually answers.
Integrated, not yet usedOnline paymentPaying in advance by link, and reconciling the payment against the work order.
To be builtReading and replying to public reviewsSeeing reviews received and replying from inside the system.H&S can SEND a review link by text — that is a message, nothing more. Reading or replying to reviews on a public platform requires a connector that does not exist.
To be builtExternal calendarSeeing shop appointments in a calendar already in use.No calendar sync is running at H&S.
To be builtParts distributorPrice, availability and ordering from the work order.No connector, and access depends on the shop's own commercial agreement with its distributor.
To be builtLegacy shop systemRecovering the history rather than leaving it behind.There is no connector: migration happens by file export, and its feasibility is judged on the actual file.
To be builtAccounting softwareAvoiding double entry between the shop and accounting.The module exists in the catalogue but is not sellable: its real cost has not been measured.

What size does it fit?

The sector model does not change; what changes is the configuration and the size of the rollout.

  • 2 to 5 people
  • 6 to 20 people
  • 21 to 75 people
  • Multiple locations

Why it is worth money

No percentages, no advertised return on investment. H&S has delivered no client on these systems: what follows describes a mechanism, not a result obtained.

The missed call stops being a silent lossAn unanswered call triggers a message within the minute and creates an enquiry in the queue. It becomes visible, therefore recoverable.
No estimate sits without a follow-upEvery estimate carries its date and its next follow-up. The follow-up fires on its own and stops on reply.
What was authorised is in writingApproval happens line by line, timestamped. The conversation at pickup is about a document, not two memories.
Declined work resurfacesDeclined items stay attached to the vehicle and appear at the next visit, before the inspection.
The customer stops calling to find outProgress is pushed to them, and their space is open. Every avoided call is advisor time.
The vehicle becomes the earning unitReminders by date or mileage, a full history, declined work retained: the same vehicle has several reasons to come back.

How it goes live

What we need from you before we start

  • An available decision-maker: they settle the stages and the vocabulary.
  • The list of bays, technicians and current rates.
  • An export from the old system, if there is one. Failing that, we start from the active customer base.
  • A domain and a sending address, with access to authenticate them.

The stages

  1. DiscoveryWe look at a real day: who answers, who estimates, who approves, who hands over.
  2. Sector modelVehicle, inspection, estimate, work order, bays. Objects before screens.
  3. ConfigurationYour stages, your rates, your templates, your roles.
  4. Data migrationImport, rejection report, correction, re-import. The rejection report goes back to the client, never to H&S.
  5. AutomationsRecovery, follow-ups, reminders — switched on one at a time, never all at once.
  6. Acceptance and trainingWe replay real files with the team before cutting over.
  7. CutoverThe new system becomes the only place anything is entered.

What pauses the clock

Named up front because they are not on our clock: while one of them is blocking, the schedule waits.

  • Write access to DNS, or a reachable domain holder.
  • Migration file corrected after the rejection report.
  • Decision-maker available for acceptance and training.
  • Document templates supplied in a usable format.

What can be added

Additional locationAvailableBays, calendar and team of the location's own, under one management.
Multi-channel follow-upAvailableThe follow-up follows the channel the customer answers on.
Dormant reactivationAvailableA campaign built on last visit, mileage or declined work.
Tire storageAvailableA location attached to the vehicle, and a scheduled seasonal return.

The investment

The foundation sold with this system

THE SYSTEMOne place where the information lives: every customer, every job, who does what and what has to go out today.From$9,500

The modules that make sense for this trade

Multi-channel follow-upFollow-up doesn't stop at email: text and social pick it up when nobody replies.
Dormant-customer reactivationCustomers who haven't bought in months get contacted by a written sequence, instead of staying a dead list.$1,200
Additional locationEach location has its own calendar, files and numbers, and management keeps the overall view.

What gets quoted separately, after analysis

  • Service-history migration beyond the standard template
  • Parts inventory
  • Connector to a distributor, a labour-time schedule, or a legacy shop system

See the amounts and the conditions

What we say before we are asked

Honesty

H&S has not delivered a single garage to date. The demo is an explorable prototype and its records are fictitious. What is sold is adapting the model to your shop.

Limit

The vehicle is a second central object, which the standard offer excludes. GarageOS is therefore sold with a written scope, settled after the audit — not off a catalogue.

Limit

No parts inventory. The system knows a part was fitted; it does not say what is left on the shelf.

Limit

No connector to a distributor, a labour-time schedule or a VIN decoder. These are entered by hand, or quoted separately.

Limit

The inspection checklist is the shop's own. It is not a regulatory inspection, and the system certifies none.

Limit

AI drafts text and summaries. No estimate, no diagnosis and no price is decided by it.

Limit

Contact consents are recorded with their date, and a refusal is honoured. That is a record, never a compliance guarantee.

What comes next

The demo can be explored with no appointment and no account. Pricing comes after an audit, never before.

See GarageOS working