// Trellum — Home + Services pages const Page = ({ children }) =>
{children}
; const PageHeadingH1 = React.forwardRef(({ children, style, ...rest }, ref) => (

{children}

)); // ─────────── HOME ─────────── const goToServicesAnchor = (setPage, anchorId) => (e) => { if (e.defaultPrevented || e.button !== 0 || e.metaKey || e.ctrlKey || e.shiftKey || e.altKey) return; e.preventDefault(); setPage('services'); setTimeout(() => { const el = document.getElementById(anchorId); if (el) el.scrollIntoView({ behavior: 'smooth', block: 'start' }); }, 80); }; const Home = ({ setPage, h1Ref }) => ( {/* HERO */}
Operational Intelligence and AI Engineering for Facilities Management.

Trellum reads the contract, recognises the operational pattern, and engineers the tooling that holds the team's response together. PFI, block management, and contract-heavy estates — built by an FM operator, not a consultancy.

Operational Intelligence AI Engineering
{/* VERTICAL RECOGNITION STRIP */}
By regulatory context

If you're managing a PFI contract approaching expiry, a deduction dispute, or asset condition concerns at handback —

PFI engagements

If you carry Accountable Person duties, manage HRBs, or face BSR contact on the golden thread —

Block management engagements
{/* TWO PRACTICE PANELS */}
What Trellum does

Operational Intelligence

Trellum reads operational data — CAFM exports, compliance records, service performance returns — against the contract or the statutory regime that governs them. The work surfaces what the data shows versus what the operator or the records claim, and lodges the findings in a register the team can defend under scrutiny.

Across FM operations — sharpened in PFI as Payment Mechanism Audits, in block management as Golden Thread Gap Audits.

More on Operational Intelligence

AI Engineering

Trellum builds AI tooling into FM workflows — custom GPTs trained on the contract or the regulation, prompt libraries calibrated to the team's role, agentic workflows that turn unstructured operational data into structured outputs the team can defend. Built on whatever platform the team already owns. No vendor capture.

Across FM operations — sharpened for PFI workflows in paymech analysis and PMR review, for block management in golden thread evidence mapping and AP transitions.

More on AI Engineering
{/* PRACTITIONER PANEL */}
Who builds this work An FM operator, not a consultancy. Trellum is built by a working FM practitioner — someone who has held the contract, run the helpdesk, managed the deduction conversation, and built the digital tooling that runs underneath all of it. The career behind Trellum spans four layers — commercial, technical, contractual, and digital — and the practice is the combination, not any single layer. That matters because the work Trellum sells cannot be done at distance. Reading a payment mechanism schedule against twelve months of CAFM data takes operational depth that surveying credentials do not produce. Building AI tooling that survives the Monday after training week takes domain knowledge that generic Microsoft partners do not carry. Trellum holds both. More on the approach
{/* ENTRY POINTS */}
Three ways in Each ends with something that remains useable. {[ ['01', 'FM AI Engineering', 'Building AI tooling into FM workflows. Custom GPTs, prompt libraries, agentic workflows, and automations designed for the contract you hold and the systems you run.', ['4–8 weeks', 'Engineering']], ['02', 'FM Digital Adoption', 'Targeted adoption work for FM teams who already own the platforms. Role-specific change management — property managers, contract managers, helpdesk supervisors, PPM administrators.', ['3–6 weeks', 'Adoption']], ['03', 'Contract & Compliance Intelligence', 'A clause-level read of the obligation — PFI payment mechanism or BSA golden-thread regime. Mapping obligations against the evidence the organisation holds.', ['Scoped', 'PFI & BSA']], ].map(([n, title, body, tags], i) => ( setPage('services')} first={i === 0} cols="60px 1fr auto" /> ))}
setPage('contact')} /> ); // ─────────── SERVICES ─────────── const Services = ({ setPage, h1Ref }) => { const oiOfferings = [ { n: '01', title: 'Operational Diagnostic', body: "A structured read of an FM operation as it actually runs. Trellum reads three layers in parallel: the contract or statutory regime that governs the work, the data the operation produces against that regime, and the work itself — how tasks are being performed, where defined process and lived practice diverge, where work gets picked up, dropped, reclassified, or migrated between queues without the records capturing the move.\n\nThe diagnostic produces a prioritised roadmap the team can act on. Useful whether or not the engagement continues beyond it.", tags: ['3–5 days', 'Entry diagnostic'], brings: ['Access to the FM team and the contract or compliance documentation', 'Read access to CAFM and compliance records', 'Time on site — the diagnostic is run with the team, not at distance', 'A named sponsor for the engagement'], receives: ['A written diagnostic across the three layers — contract, data, work', 'A prioritised roadmap with named next actions', 'A debrief session covering findings and next-step options'], }, { n: '02', title: 'Contract & Compliance Intelligence', body: "A clause-level read of the obligation — a PFI payment mechanism, a BSA golden-thread regime, or another contract-and-compliance regime where the evidence requirement is heavier than the team's current capacity to meet it. The work maps obligations against the evidence the organisation holds and identifies where the two diverge.", tags: ['Scoped per engagement', 'Specialist'], brings: ['Contract documentation (PM schedule, lease, or compliance framework)', 'Operational data (helpdesk, PPM records, or compliance register)', 'Named point of contact'], receives: ['Named obligation register', 'Evidence gap analysis', 'Remediation owners identified'], }, { n: '03', title: 'Payment Mechanism Audit', body: "A scoped read of the PFI schedule's availability and deduction logic against the recorded service events the authority holds. Findings are framed as observations against the contract — the client draws the conclusion. The same document serves the authority's position and the operator's preparation.", tags: ['5–7 days', 'PFI sprint'], brings: ['The operative payment mechanism schedule', 'CAFM export covering at least twelve months', 'Accommodation schedule and recent FM monthly reports'], receives: ['A written audit document — executive summary, contract comprehension, operational pattern analysis, calculation exposure', 'A working register lodged in a format the team can extend', 'A debrief session, executive-summary-ready for non-specialist senior management'], }, { n: '04', title: 'Golden Thread Gap Audit', body: "A scoped read of the BSA Part 4 information requirements against the records the organisation currently holds. Findings are framed as observations against the statutory regime, categorised by gap type — absent, unstructured, undated, inaccessible. The output supports both the duty-holder's defensible position and the Accountable Person's criminal liability protection.", tags: ['5–7 days', 'Block sprint'], brings: ['Current evidence base — registers, plans, compliance records', 'AP/PAP designation documentation', 'Access to the property management or compliance lead'], receives: ['A written audit — statutory comprehension, evidence pattern analysis, gap register with remediation path', 'A working gap register the team can extend', 'A debrief session calibrated to AP duty-holder needs'], }, ]; const aieOfferings = [ { n: '01', title: 'Digital Readiness Assessment', body: "A structured read of an FM team's digital position before any AI engineering or adoption work. The assessment maps the platform stack the team owns, the data quality available for AI workflows, the role-by-role candidates for AI tooling and automation, and the change readiness in the team that will use what gets built.\n\nThe output is a prioritised roadmap that scopes the AI engineering or adoption work the team is actually ready for. Useful whether or not the engagement continues beyond it.", tags: ['3–5 days', 'Entry diagnostic'], brings: ['Existing platform stack documentation (M365, Workspace, CAFM, others)', 'Sample operational data the team produces in the workflows under review', 'Access to the roles the AI work would target', 'A named sponsor for the engagement'], receives: ['A written assessment across platform, data, use cases, and readiness', 'A prioritised roadmap scoping the AI engineering or adoption work the team is ready for', 'A debrief session with named recommendations'], }, { n: '02', title: 'FM AI Engineering', body: "Scoped engagements that build AI-powered tooling into FM workflows. Custom GPTs trained on the contract. Prompt libraries specific to PFI payment mechanisms or BSA evidence requirements. Agentic workflows that turn unstructured operational data — emails, reports, helpdesk logs — into structured outputs the team can defend. Delivered on the team's own platform stack — Microsoft 365, Google Workspace, the CAFM, or direct API. Platform-agnostic by design.", tags: ['4–8 weeks', 'Engineering'], brings: ['Named workflows in scope', 'Access to existing systems', 'Management sponsorship', 'A clear problem to solve'], receives: ['Working tools deployed in client environment', 'Documentation the team can extend', "Trained team members who can operate and maintain what's been built"], }, { n: '03', title: 'FM Digital Adoption', body: "Targeted adoption work for FM teams who already own the platforms. The engagement maps the actual FM tasks consuming the team's week against the platform features that could absorb them, and runs the role-specific change management to land the shift. Property managers, contract managers, helpdesk supervisors, PPM administrators — different roles, different workflows, different adoption paths.", tags: ['3–6 weeks', 'Adoption'], brings: ['Existing platform access (M365, Google Workspace, CAFM, or equivalent)', 'Named roles and workflows in scope', 'Management sponsorship'], receives: ['Role-specific adoption playbook', 'Use-case mapping by role', "Handover register tracking what's been adopted, by whom, with what evidence"], }, ]; const renderOffering = (o, i) => (
{o.n}

{o.title}

{o.body.split('\n\n').map((para, idx) => (

{para}

))}
{o.tags.map((t) => {t})}
What the client brings
What the client receives
); return ( {/* HEADER */}
Services Fixed-fee engagements. Defined scope. Deployable outputs.

Every engagement ends with an artefact your team can maintain. Not a deck filed after the meeting. Not an ongoing dependency.

{/* OFFERINGS — by practice */}
{/* Practice 01 — Operational Intelligence */} Practice 01 Operational Intelligence Reading the operation against a contractual or statutory regime. Pattern recognition in CAFM and compliance data. Contract literacy at the schedule level. The work of knowing what is actually happening in the operation — not what the records or the operator report says is happening. {oiOfferings.map((o, i) => renderOffering(o, i))} {/* Practice 02 — AI Engineering */}
Practice 02 AI Engineering Building AI tooling into FM workflows. Custom GPTs trained on the contract or the regulation. Prompt libraries calibrated to the team's role. Agentic workflows that turn unstructured operational data into structured outputs the team can defend. Built on whatever platform the team already owns. {aieOfferings.map((o, i) => renderOffering(o, i))}
{/* PRACTICE LINKS */}
Named specialisms Either side of the table. Trellum's PFI and block management work is built for either side of the obligation. The same engagement serves the contracting authority or the FM operator in PFI, the duty-holder or the managing agent in block management.
setPage('pfi')} cols="60px 1fr auto" /> setPage('block')} cols="60px 1fr auto" />
setPage('contact')} /> ); }; Object.assign(window, { Page, PageHeadingH1, Home, Services });