Harold

Overview

View markdownFeedback

What Harold does, who it serves, why teams adopt it, and how work flows from signal to controlled client output across pipeline, deals, documents, inbox, reporting, and distribution.

Operating model

Harold is deal-first software. Concepts explain the model, workflows show execution, and admin plus security cover control. Reference pages stay practical, concise, and decision-focused.

First success path

Start with observable wins: create a deal, ingest a document, generate a report, then distribute with controls. Add permissions, inbox integration, and admin review to lock quality.

Ingest → organise → analyse → distribute

These lanes show how teams run Harold daily. They are one connected operating flow, not separate products.

Ingest

Capture signals, threads, and files once, with clear context, so intake stays fast and deduplicated.

Organise

Attach artefacts to the deal spine, preserve ownership, and keep diligence aligned with transaction context.

Analyse

Turn approved templates into decision-ready outputs with review checkpoints that protect quality.

Distribute

Send the right narrative to the right audience with traceability, consistency, and controlled personalisation.

Product atlas

Modules are documented by outcomes first: purpose, users, inputs, and outputs. Reference depth is available when needed without slowing evaluation.

Security & governance

Security is first-class. Authentication, SSO, permissions, encryption, and audit expectations are written for buyers and admins. Formal assurance still follows your commercial and security review process.

Controls-first designEncryption in transitWorkspace permissions
Open security overview →

Machine-readable index

Fetch the complete documentation index at: https://docs.haroldproperty.co.uk/llms.txt

Use that file to discover public URLs before deeper crawling.

Was this page helpful?

Harold Property - Documentation