Updated June 2026 · V360-internal reference document · Not for client distribution
1. Executive Summary
J.P.R. Combustions Ltd presents a rare combination: (a) a substantial, technically capable, 25-year-old commercial-and-domestic heating business operating at the bottom of the modern-firm digital posture league table, (b) a family relationship that gives V360 trusted access to the engagement, (c) a problem set that is structurally identical to that of every other ~5-engineer UK trade firm, and (d) a willing decision-maker (James, engineering director) already convinced the gap exists.
That combination is not coincidental. It is a strategic opening.
The recommendation: engage at £42,000 for Year 1, structured across three workstreams — full rebrand, modern AI-integrated marketing website, and bespoke AI-native operating platform with engineer mobile app — followed by a £24,000/year platform subscription from Year 2 onward. The engagement delivers immediate measurable value to JPR (£100,000–£250,000/year in latent revenue capture + recovered admin cost, per the audit) and, critically, produces the first validated installation of what becomes V360 Labs' next product — an AI-native operating platform for UK trade firms.
TAM: 10,000+ UK heating firms with 5+ engineers; addressable revenue at 1% adoption ≈ £2.4m/year recurring.
The risks are real but manageable: Cooper capacity (3–4 months of substantial engineering); co-owner cooperation (without it, the platform cannot be migrated to); scope creep (always elevated in family engagements); IP retention discipline (must be written in up front).
The strategic case for doing this is stronger than the family discount alone. The case for not doing it is essentially: capacity won't allow it right now. That is a real question — addressed in §8.
2. What JPR Actually Needs
A condensed summary of the audit findings (full audit at JPR-Combustions-Audit-for-James.md).
JPR is a £1.5–4m revenue heating and gas services firm with 5 engineers, Gas Safe / Worcester Bosch / Powrmatic accreditation, genuine commercial-and-industrial scope (Atag, Ideal, Vaillant, Hamworthy, Broag Remeha, Ambi-rad, Powrmatic plant; warm air; radiant tube; gas escape work; pipework design; load testing; meter housing). The engineering side is properly run.
The non-engineering side is operating at a 2018 standard. Visible facts:
Website unchanged since 2018, contains typos on the live commercial page (including misspelling their own Powrmatic accreditation), unfixed editor's notes left as bullet points, no mobile-first design, no schema markup, no online booking, no chat, no case studies, no commercial sector pages, no privacy notice.
Zero visible Facebook, Instagram or LinkedIn presence.
No visible Google Business Profile management discipline.
No content marketing.
Strongest commercial credential (Powrmatic, 25-year industrial-plant scope) buried three clicks deep behind a typo-ridden page.
Inferred: no FSM platform, no asset register, no annual-service reminder programme, no proofreading discipline, no marketing collateral library.
Competitive frame on the Isle of Wight:
F W Marsh (Ryde) — dominant FM-grade contractor, 4-division E&M, NICEIC/BAFE/ECA/SafeContractor
JPR has stronger engineering credentials than any peer except F W Marsh, and arguably the only Powrmatic-accredited firm of its size on the Island. None of that is visible in the digital posture. The gap is not capability — it is presentation, lead capture, and operational tooling.
Facebook / Instagram / LinkedIn business profiles launched
Why this matters: this is the front door for every domestic and commercial lead from month 3 onward. Done properly, JPR ranks for "commercial heating Isle of Wight" within 90 days and starts pulling enquiries that currently flow to Wight Heating.
3.3 Workstream C — JPR Operating Platform (months 2–6)
Lead: Cooper + JR on AI architecture · Support: Axiom (Operations & Systems)
This is the substantial workstream and the strategic asset.
Core platform features
Customer + asset database. Every customer, every property, every appliance / plant item, structured. Service history, certificate history, warranty status, next-service-due dates. Commercial clients: per-site plant registers with PPM schedules and document libraries.
Engineer mobile app. Schedule, today's jobs, customer history, asset history, plant manuals, photo capture, voice notes. Works offline (Island ferry dead-zones), syncs when connection returns.
Voice-to-job-sheet AI workflow. Engineer dictates 60–120 second voice note post-job. AI transcribes locally (faster-whisper, on-device privacy), structures it into a job sheet template, drafts customer-facing email summary, drafts follow-on quote if applicable, queues for office review. Pushes to database, invoice draft, calendar entry.
RAG-grounded technical assistant. Plant manuals (Powrmatic, Hamworthy, Worcester Bosch, Atag, Vaillant, Ideal, Broag Remeha) digitised and indexed. Engineer asks natural-language question; AI returns answer with cited source page.
AI tender / RAMS drafting. Tender knowledge base built from JPR's actual capability, past wins, case studies, references. New RFQ arrives → director briefs the AI → 25-page tender draft produced in 2 hours; director edits and signs. RAMS drafted from base templates customised by AI to specific site / scope.
AI quote generator. From engineer voice + photos → AI applies template → priced draft for director approval → sent within hours.
Automated customer journey. Booking confirmation → 24h reminder → "on my way" ETA → post-job summary + certificate + review request → annual reminder cycle. Different templates per buyer type.
GBP / review automation. Every job triggers review request via SMS; new reviews aggregated; AI drafts on-brand replies for director approval.
Customer portal. Customers see service history, certificates, next service date, can book online.
Claude API for LLM workflows (with prompt-library version-controlled)
Faster-whisper for local-first transcription (privacy-preserving)
Make.com / n8n for integration glue
Xero / Sage integration for invoicing
Google Workspace integration for calendar / GBP / Drive
Why this matters: this is not a "buy Joblogic" engagement. Off-the-shelf FSM platforms exist and they're fine. But none of them have native AI integration — voice-to-job-sheet, RAG-grounded engineer assistant, AI tender drafting. What V360 is building is the first AI-native version of the FSM category, with JPR as the alpha installation. That's the strategic asset.
4. Financial Model
4.1 What it costs JPR
Phase
Period
Scope
Price
Phase 1
Months 1–3
Full rebrand, marketing website, brand pack, Island photography day, GBP/social launch, commercial PDF
4.2 What JPR gets back — projected savings + revenue lift
Working from the audit's quantification, with conservative / realistic / optimistic ranges. All figures Year 1 effect.
Outcome
Conservative
Realistic
Optimistic
Engineer time recovered (admin friction removed)
£60k
£105k
£140k
Admin time saved (office function)
£15k
£25k
£35k
Annual-service retention uplift
£40k
£60k
£80k
Domestic lead capture (digital posture upgrade)
£150k
£260k
£400k
Commercial pipeline lift
£30k
£80k
£130k
Tender win-rate improvement
£20k
£60k
£100k
Total Year 1 impact
£315k
£590k
£885k
Year 1 investment
£42k
£42k
£42k
Net return Year 1
£273k
£548k
£843k
ROI Year 1
7.5×
14×
21×
Year 2 steady-state cost
£24k
£24k
£24k
Ongoing ROI
13×
25×
37×
These are aggressive but defensible numbers. The dominant variable is domestic lead capture — the gap between "no active digital posture" and "actively managed GBP + modern website + content + social" is genuinely an order-of-magnitude difference for a local trade firm.
4.3 What it earns V360
Year 1: £42,000 one-time + retainer revenue.
Year 2+ steady state: £24,000/year recurring subscription per JPR.
At 50 customers (Year 3–5 plausible scaling): £1.2m/year recurring.
The JPR engagement is a strong individual deal in isolation. As the alpha for a productised UK trades platform, it is the case study that buys V360 access to a £100k–£1m+ recurring revenue line within 24–36 months.
4.4 Hidden costs to V360 (honest accounting)
Cooper capacity: 3–4 months of substantial Cooper engagement. Displaces ~one Anti-World feature cycle, ~one V360 web property roll-out, or similar. Real opportunity cost.
JR personal time: ~2 days/week for the first 6 months on AI workflow architecture, brief writing, monthly reviews. After month 6, ~half-day/week steady-state.
Aria + Pixel + Nova + Atlas: total of perhaps 8–12 person-weeks across the year, blended across the team.
AI compute costs (Claude API, faster-whisper hosting): £200–£500/month at JPR's volume, covered within the subscription.
Hosting, services, third-party tools: £150–£400/month, covered within the subscription.
Even pricing the internal cost at £25,000–£35,000 of "true cost", Year 1 gross margin is meaningful and Year 2+ subscription is high-margin recurring. The economics work.
5. The Strategic Play — V360 Labs Productisation
JPR is interesting because it is a textbook example of a category that V360 could productise cleanly.
5.1 Why now
Three converging conditions:
The UK trade sector is digitally backward and increasingly under procurement pressure. Council, NHS, FM and managing-agent buyers are professionalising procurement faster than incumbent local firms can professionalise themselves. Firms that don't catch up lose the work to off-island contractors (Corrigenda being the visible local example). The market need is real.
The AI cost curve has crossed the line where a small firm can have a tender-drafting / RAMS-drafting / RAG-grounded engineer assistant at meaningful capability for <£500/month in compute. Two years ago this stack was a £500k enterprise build. Today it is a properly designed prompt library + API integration.
No incumbent FSM platform has gone properly AI-native. Joblogic, Commusoft, ServiceM8, BigChange, Simpro — all viable platforms, all retrofitting AI features as bolt-ons rather than building AI-native from the ground up. There is a window.
5.2 Addressable market — UK heating firms specifically
~10,000 UK heating firms with 5+ engineers
~25,000 plumbing firms (related category, similar tooling fit)
Even confining the play to heating-only, conservative scaling:
Adoption rate
Customers
Annual subscription
V360 ARR
0.5%
50
£24,000
£1.2m
1.0%
100
£24,000
£2.4m
2.0%
200
£24,000
£4.8m
These are not aspirational fantasy numbers — they reflect what a credible product-led SaaS in a previously-underserved trade vertical can plausibly achieve in 36 months with one good case study, one or two trade-press features, and steady inbound + referral motion.
5.3 Productisation pathway from JPR
The JPR engagement, played well, produces:
A working installation with real engineers using the AI features daily
Validated metrics — lead lift, retention lift, admin time recovered, tender win-rate change
A case study with permission to publish (anonymised metrics, photo and quote release from James)
A reference customer — James becomes a named or anonymised reference
A second customer recruited via demonstration — V360 walks into the next trade firm with "here's what we built for an Island heating firm; here's their measurable results"
Year 2 work — assuming JPR validation lands — would then split:
Continued JPR steady-state delivery
3–5 additional UK trade firms onboarded at £24k/year subscription each
Trade-press strategy: BESA, APHC, HVAC News, PHAM News, Heating & Ventilating Review — three or four feature pieces would seed national awareness
IoW Chamber of Commerce / Federation of Small Businesses regional play for further validation
Year 3 — if scaling works — TradeStack as a defined product line under V360 Labs / ProductWorks with its own marketing, sales motion, and possibly small dedicated team. At that point — and only at that point — does it justify its own brand / entity / agent dedicated to it. Not before.
5.4 IP retention — must be written in up front
For this play to work, V360 must retain ownership of the platform IP. JPR gets a perpetual licence to use the platform under the engagement; V360 retains the right to productise, configure, and resell.
Recommended contract structure:
V360 retains all platform IP (code, prompt libraries, AI workflow architecture, data models)
JPR data is JPR's data — never used to train models for other customers, never visible to other customers, never resold
JPR receives a perpetual licence to use the platform under the engagement, conditional on continued subscription
JPR receives "first customer" pricing lifetime — locked at £24k/year while market rate for the productised version would settle higher (£36–60k/year)
Optional small revenue share — 2–5% of net new TradeStack revenue for 24–36 months — only if James asks for more skin in the game; don't lead with it
Albert (Legal) should draft the engagement contract with these terms explicit. This is the single most important paragraph in the entire engagement and the one that most often gets fumbled by founders who feel awkward asking for IP retention from a family member. Get it written.
6. V360HQ Operating Model
JPR is delivered through V360HQ as the inaugural engagement under Path A (Consulting). No restructure of HQ required. The delivery team:
Role
Agent
Estimated time over 12 months
Engagement lead
JR
~1 day/week (months 1–6), then ~half-day/week
Orchestration
Victor
~half-day/week throughout
Business / contract / finance
Clara
~2 days total
Legal (engagement contract + IP)
Albert
~3 days total
Creative direction
Aria
~2 days/week months 1–3, then ~half-day/week
Design execution
Pixel
~2–3 days/week months 1–3, then occasional
Digital build (website + platform)
Cooper
~3 days/week months 1–6, then ~1 day/week
Content (website copy, blog, social)
Nova
~1 day/week throughout
Photography / video
Atlas
~3 days of session work + occasional shoots
Systems / ops / data hygiene
Axiom
~1 day/week months 2–6, then ~half-day/week
Not on this engagement: Solomon, Maggie, Cassie, Melissa (initially; Year 2 if trade-press strategy launches).
/CONSULTING/JPR/STATE.md — current engagement status, tracked by Victor
Reporting cadence inside HQ:
Weekly: Victor logs engagement status
Monthly: JR + Clara review against engagement plan
Quarterly: V360 advisory-style review with JR (and James, externally)
External sender posture (Phase 1): all external comms to James / JPR go via JR's identity, signed JD Robson, until Phase 2 unlock. Agent attribution invisible externally. Internally, agents own their workstreams.
The whole engagement is delivered under the existing V360HQ operational pattern. Nothing here requires new agents, new .md updates, or framework changes. The agents simply do their jobs on the brief in front of them.
7. The 12-Month Engagement Plan
Condensed view. (Detailed version becomes the engagement brief once approved.)
Month 1 — Set-up and rebrand kick-off
Engagement contract signed (Albert)
Access secured: GBP, customer list, current website logins, Companies House
Rebrand creative direction approved (Aria → JR → James)
Photography session scheduled and shot (Atlas, Island trip)
Customer / asset database export pulled and cleaned (Axiom)
Month 5 — Platform iteration + tender / RAMS AI live
Engineer-app feedback loop, iteration (Cooper)
AI tender drafting + RAMS drafting workflows live (Cooper + JR)
Annual-service reminder programme begins
First commercial PDF goes to a real prospect
Month 6 — Platform full deployment
Whole engineer team on the platform
Office staff on the new admin layer
Customer portal live
Subscription mode begins (£2,000/month)
First major review meeting with James + JPR directorate
Months 7–12 — Steady state
Content cadence: 2 articles/month + weekly social + GBP posts
Review collection running automatically
Monthly engagement review with James
Engineer-feedback-led platform iterations
Commercial pipeline tracked; tender support as required
Quarterly engagement summary report to James (with metrics)
Month 12 — Year 1 closeout
Full Year 1 performance report (savings + revenue lift attributed)
Year 2 subscription continuation discussion
Case study agreement (V360 to use for next customer)
If trajectory good: V360 Labs TradeStack project formally created
8. Risk Register
8.1 Cooper capacity (HIGH)
A 3–4 month substantial Cooper engagement is the largest single resource ask. Cooper's current load includes Anti-World Printify build, V360 web properties roll-out, hyperframes infrastructure, and at-the-margins LaughCut UI consideration.
Mitigation:
Pre-commit Cooper's calendar with JR before quoting James
Sequence so that JPR rebrand + website (months 1–3) gets Cooper's primary attention; platform build (months 3–6) sequences after the marketing layer ships
Anti-World Printify build status to be confirmed — parked-pending-artwork still?
If Cooper truly cannot absorb 3 days/week for 6 months, this becomes a Path 1 (£20k marketing-only) engagement, not Path 2 (£42k with platform). Don't pretend it's Path 2 if it isn't.
8.2 Co-owner cooperation (HIGH)
Identified in the audit. Without GBP admin access, customer database access, and willingness to migrate to the new platform, the engagement cannot succeed.
Mitigation:
Make this a gating question in the first conversation with James before any contract is signed
"Within 7 days I need: GBP admin access, customer list export, current systems' logins, and the directors' commitment to the team migrating to the new platform once it's live"
If James cannot get that commitment, engagement is downgraded to Path 1 or paused entirely
This is binary, not graduated
8.3 Scope creep (MEDIUM-HIGH)
Family engagements expand. "Could you also look at..." is the killer phrase.
Mitigation:
Written scope, written milestones, written payment schedule — in the engagement contract
Anything beyond scope is quoted separately as a change request
Year-end review is the natural extension point
50% on signature / 25% at week 8 / 25% on month 12 — payment milestones are protection
8.4 IP retention (MEDIUM but high-impact)
If the platform IP gets confused — "we built it for JPR, JPR paid for it, JPR owns it" — the productisation play dies.
Mitigation:
Get the IP clause written explicit in the engagement contract from day one (§5.4)
Albert drafts; JR signs; James signs as JPR director
Don't soft-pedal because it feels awkward to ask family. The whole strategic case rests on V360 retaining the right to productise.
8.5 Family dynamics (MEDIUM, ongoing)
Money + family + work is the classic triangle. Even handled well, this carries risk that the engagement strains the brother-relationship.
Mitigation:
Engagement contract treats JPR as a client, not as family. Clean rails.
All comms through professional channels (V360 email, formal documents) — not in casual family conversation
Monthly reviews are scheduled meetings, not over Sunday lunch
If a real dispute arises mid-engagement, escalate to written, formal, professional
Honest framing with James upfront: "I want to do this as a real engagement, not as a favour, because the favour version would be worse for both of us"
8.6 The "we'd rather just hire someone" outcome (LOW)
JPR receives the audit, recognises the gap, but decides to hire a local marketing coordinator at £30k/year rather than engage V360.
Why this is actually fine: if it happens, JR has done his brother a real service by surfacing the audit. V360 doesn't lose because the engagement was never going to be a slam-dunk. The audit + AI Implementation Report sits with James as the brief any external hire could execute against. JR's family cost: zero. V360's cost: time invested, which has produced a reusable template for future prospects.
The bad outcome is JPR commissioning and V360 underdelivering. That's the one to manage hardest. Scope discipline + Cooper capacity check + co-owner gating question all exist to prevent it.
9. Decision Framework — Go / No-Go
9.1 Hard conditions for GO
All of these must be true:
Cooper has confirmed capacity for ~3 days/week for months 1–6
JR has capacity for ~1 day/week for months 1–6
James commits to securing co-owner cooperation: GBP admin access, customer list, systems logins, team migration commitment, within 7 days of engagement
Engagement contract signed with V360-retained IP, written scope, written milestones, written payment schedule (Albert-drafted)
50% deposit paid at signature (£21,000)
Initial brief approved by JR + James + Aria within 14 days of signature
9.2 Soft conditions for GO
All of these should be true:
Anti-World Printify status confirmed not-currently-blocking Cooper
V360HQ Phase 1 cross-talk infrastructure stable (no Cross-Talk Watcher silent-death issues during engagement)
LaughCut shipped or in stable-iteration mode (no Cooper UI emergency expected)
Clara's bandwidth available for monthly billing + contract management
At least one trade-press / IoW Chamber of Commerce / B2B contact identified for Year 2 case-study amplification
9.3 Alternative — Path 1 fallback
If the platform workstream cannot be committed to, the alternative is Path 1: marketing-layer transformation only.
Phase 1 only (£12k) — rebrand + website + GBP + social + commercial PDF
6-month light retainer at £800/month — £4,800
Total: £16,800 for 12 months
Smaller scope, smaller payoff, no platform play, no productisation case study
Cleanest if Cooper capacity or family risk is the blocker
This is the safety valve. Better than not engaging at all.
9.4 The decision
Recommended: GO on Path 2 (£42k full engagement) subject to all hard conditions in §9.1 being met.
The strategic case for Path 2 is materially stronger than Path 1 because:
The economic case for JPR is overwhelming (7–25× ROI)
The strategic case for V360 (Labs alpha → TradeStack productisation) requires the platform build, not just the marketing layer
The case study value of "we built JPR an AI-native operating platform" is fundamentally more valuable than "we redid JPR's marketing"
The marginal cost of Path 2 over Path 1 is largely Cooper capacity, which is the single binary that determines feasibility
If Cooper cannot absorb the build, drop to Path 1. If Cooper can, GO on Path 2.
10. Next Steps
If JR (and Clara, if she's the second sign-off) say GO:
Today–48 hours: Cooper capacity confirmation. Honest. Not "we'll find a way". Real Y/N.
48 hours: Clara confirms engagement-billing readiness. Albert begins drafting engagement contract template (reusable for future consulting work).
Week 1: Pitch document delivered to James (JPR-Combustions-V360-Proposal-for-James). Schedule 30-min call within 7 days.
Call with James: present the proposal, run the gating questions (co-owner cooperation), agree in principle.