The example explained
One job. Everyone working
from the same picture.
A leaking tap is simple. Getting from the first call to a happy customer involves a whole business. Here’s where Spine starts.
The connection is the point.
Each step leaves something the next person needs: a checked booking, a recorded finding, an agreed quote, or a completion record.
AI can help prepare that work. Routine software can move it along. Neither gets to invent missing facts or take over decisions your team needs to make.
Try “Job done,” then report a problem. Routine messages pause and a person takes over. That return path matters as much as the happy path.
How we apply this with youExample: one plumbing job
Kitchen tap repair
Step 1 of 5
The details travel with the job.
A customer calls about a leaking kitchen tap. The office needs the details, not another message for the owner to decipher.
New enquiry
“The kitchen tap is leaking. Mornings are best for a visit.”
A checked job record goes to scheduling.
Who does what, and why?
- Software & AI
- Capture the details and prepare a job record.
- People
- The office checks urgency, service area, and whether to take the job.
- Job
- Leaking kitchen tap
- Customer preference
- Morning visit
- Call arrives: Software helps; a person decides.
- Qualify: Software helps; a person decides.
These choices belong to this example. Your team, customers, and working conditions determine yours.
Illustrative example. No messages are sent and no customer system is connected.
Try the decisions for yourself.
Follow the job through a refused quote, a missing finding, or a problem that comes back. See who decides and which actions must wait. This is a fictional simulation, with no connected business systems.
Explore the working exampleRead the job walkthrough
This fictional example illustrates proposed working arrangements. It is not a client result, live integration, or assessment of your business.
Enquiry: The details travel with the job.
A customer calls about a leaking kitchen tap. The office needs the details, not another message for the owner to decipher.
Software & AI: Capture the details and prepare a job record.
People: The office checks urgency, service area, and whether to take the job.
A checked job record goes to scheduling.
Visit: A reminder needs a real booking.
The office chooses a suitable slot. The technician gets the same job details, and the customer knows when to expect them.
Software & AI: Suggest a slot; send a reminder only after the booking is confirmed.
People: The office handles conflicts and assigns the technician.
The technician receives the problem, timing, and access details together.
Quote: AI can prepare it. People agree it.
The technician checks the tap in person. Their finding becomes a draft quote, instead of another call asking the owner what to send.
Software & AI: Draft the quote from the recorded finding and agreed pricing rules.
People: A technician diagnoses; a named person approves the quote; the customer agrees.
The agreed work and price stay attached to the job.
Job done: Finished work unlocks the next step.
The technician records the completed repair. Billing uses the agreed work, so the office does not have to reconstruct what happened.
Software & AI: Prepare the invoice and routine payment reminders from checked records.
People: The technician performs the repair. The office handles disputes personally.
Completion and payment status go with the job into follow-up.
Follow-up: Listen to what comes back.
A review request is one small automation. Listening to the answer—and changing the work when needed—is the rest of the system.
Software & AI: Send a routine request when the job is ready for follow-up.
People: Read and answer feedback. Use recurring problems to improve the work.
What the team learns informs the next job.
The real decisions depend on your people, your customers, and the consequences of getting a step wrong. We work those out with you.
Start with a conversation
What keeps landing
back on your desk?
Tell me a little about your business and where the work gets stuck. We can work out whether Spine is a fit—and what a sensible first step looks like.
Email Christianmandefrochristian@gmail.comChristian Mandefro
Developer and founder of Spine. You’ll speak directly with the person building the systems.
Spine is an early-stage service. No client engagement has been completed end to end yet.
More about Spine