A plumbing business may be able to earn additional income by licensing suitable job records for agreed uses. Whether that's worthwhile depends on what you've kept, what you can legitimately share, and how much work participation requires. A folder full of invoices doesn't automatically produce an income stream.
For an independent plumber, a sensible first move is to describe the records you already have to a platform such as OpenSet. You can ask for an initial assessment before spending evenings sorting files. Useful experience may be sitting in ordinary repair notes, parts records, and callback histories, even when you have no interest in running a separate data business.
What counts as plumbing job data?
Think about the paperwork surrounding a familiar callout. The customer reports a dripping tap. You record the agreed work, fit a replacement part, finish the visit, and send an invoice. A week later, another message arrives. Perhaps the original problem has returned. Perhaps the customer wants a different tap replaced.
Those records describe more than a transaction. Together, they can show what was requested, what happened, and whether another visit concerned the same problem. Keep the difference between the customer's description and your own findings clear. A reported leak isn't yet a confirmed cause.
Useful material to mention in an initial assessment could include:
- Job notes for a consistent service, such as tap repairs or toilet repairs
- Parts used, with dates and job references already recorded
- Original scope and later customer-approved additions
- Return visits linked to the earlier job
- Customer follow-up messages and their recorded outcomes
You aren't being asked to collect everything on that list. A small business may have reliable notes in one area and little elsewhere. Describe that honestly. Don't start taking extra photographs inside people's homes merely to create more material for a possible licensing opportunity.
Follow the callback, not just the invoice
A paid invoice tells you about payment. A completion note records what the plumber says was done. A later customer message may provide a different kind of evidence about the result. These facts are more informative when they remain connected.
Suppose your job system marks a visit complete as soon as the invoice is issued. That status won't necessarily reveal a return visit arranged through a separate message. Software can also split conversations. Zendesk's ticket documentation, for example, explains that replies can reopen solved tickets or create follow-up tickets after closure. Your own system may behave differently.
When discussing your records, explain where callbacks live. They might be linked automatically, entered under a new job number, or kept only in your diary. A platform needs to know about that gap before suggesting substantial preparation.
An unresolved case can still be a truthful record. “Return visit arranged, outcome not recorded” is preferable to guessing that the problem disappeared. Likewise, silence from a customer doesn't establish satisfaction.
A simple calculation shows why the distinction matters
Consider a hypothetical business reviewing 600 completed jobs, each with at least 30 days of follow-up available. Ninety jobs have a later customer contact. Of those, 30 contacts concern thanks or unrelated new work, while 60 describe the original problem remaining unresolved.
Counting every later contact gives 90 divided by 600, or 15%. Counting only the 60 confirmed unresolved original problems gives 10%. That's a five-percentage-point difference caused by how the contacts were classified.
The other 540 jobs aren't proven successful. Some customers may never have replied. This example also doesn't measure an industry callback rate or predict what anyone will pay for the records.
It shows why your ordinary knowledge matters. You may immediately recognize that a second visit was booked for another bathroom, while a bare spreadsheet makes it look like a failed repair. An accurate explanation of your existing process is useful. Reconstructing hundreds of missing explanations from memory may be impractical.
Keep customers' homes out of the commercial discussion
Plumbing records can contain surprisingly intimate information. A photo may show a room layout, family photograph, medication, or an address label. Messages can include alarm codes, holiday dates, and instructions for finding a spare key. None belongs in an introductory description of your records.
Start that conversation with categories, approximate volume, date range, and the software or file types involved. Avoid sending live customer conversations as your opening example. Ask what the platform requires and how any later sample should be reviewed and transferred.
The US Federal Trade Commission's business guidance recommends understanding where personal information is held, limiting what is retained, and protecting what remains. Treat an extra export as another copy requiring care. Leave your original operational records intact under your normal retention arrangements.
For UK businesses, the Information Commissioner's Office explains that replacing names with reference numbers can leave personal data, and anonymization itself requires a lawful basis. Its guidance is under review following legislative changes. Get appropriate advice for your location and proposed use before sharing. Removing names alone doesn't settle privacy or permission.
You should also identify records belonging to someone else. A property manager's tenant list, another contractor's report, or a manufacturer's document may carry separate restrictions. Having a copy in the job folder doesn't resolve those questions.
Could a one-person plumbing business participate?
Possibly, but there is no universal minimum number of jobs that makes records valuable. A sole trader's consistent history of one service may be easier to understand than a larger archive mixing several businesses and recording methods. That doesn't establish eligibility or commercial demand.
Give the platform a realistic picture of your capacity. Say whether you have an office administrator, whether you can export from your system, and how much time you can spare. Ask which existing formats it can assess and what you would need to do yourself. Don't commission software changes before receiving a clear answer.
If a small review is requested, agree its size first. As a hypothetical planning example, reading 12 job histories at five minutes each would take one hour. That excludes export setup, privacy review, and any specialist advice. Finding missing records can quickly add time. Stop and ask for clarification if a supposedly simple step keeps expanding.
Decide whether the extra income would justify the effort
Before participating, understand the proposed permitted uses, payment basis, any platform charges, and what continuing work would fall to you. Ask what happens if the records aren't suitable or no paid use follows. Clarify any requirements to provide future jobs, answer questions, or correct historical records.
Those details determine whether the opportunity fits around paid plumbing work. A possible future payment shouldn't become a reason to delay customer appointments or spend a week repairing an old archive.
For now, choose the part of your business with the clearest history and describe it to OpenSet for an initial assessment. “Domestic tap repairs, job notes and linked callbacks, held in our job system” is a useful starting point. Include known gaps. You can then decide whether the next step deserves your time, with your working day and customer trust still at the center of the decision.
