FOR DOCUMENT-HEAVY OPERATIONS

Turn the manual gap
between inbox and register
into a testable workflow.

From inbox to a review-ready record.

Test one high-volume case type with anonymised data. Measure routing, missing evidence, deadlines and cited guidance before connecting any live system.

Detail of an anonymised paper intake form
Validate with anonymised examples — no confidential data required upfront

One workflow. Four acceptance measures.

Success is not a feature count. We agree the operating outcome first, then decide whether the evidence supports a wider rollout.

01Routing accuracy
02Missing evidence
03Handling time
04Human approval
01Test email
02Field extraction
03SOP citation
04Human approval
WHAT I WORK ON

Improve one real handoff — not another replacement platform.

Start with the repeated work between email, attachments and approved procedures, then output a reviewable record for your existing register or system.

01Engineering consulting

Correspondence, submittals and drawing revisions

Identify project, document type, revision, attachments, owner and deadline without replacing the CDE.

02Property operations

Maintenance, compliance and resident requests

Turn property, urgency, missing evidence and ownership into a review-ready case.

03Compliance & advisory

SOPs, audit evidence and document versions

Answers cite approved documents. When evidence is insufficient, the system says so.

SIMULATED BUSINESS / VERIFIED EXECUTION

Document control for Northstar Engineering Advisory.

The company, volume and organisation are fictional. The n8n executions, extracted fields, RAG citations and review routing below come from the working local demo.

Simulated business

Public-works design, drawing submittals and contract-document control

Simulated baseline

Shared mailbox, Excel register and project folders

Simulated volume

50–120 messages per week across document control, PMs and contract administration

Operating gaps to remove
  • Project numbers, revisions and dates are re-keyed
  • Missing evidence is found too late
  • Owners struggle to locate current SOP guidance
  • Review decisions lack a consistent audit trail
Verified demo evidence

5n8n cases executed

5 / 5acceptance cases passed

5versioned SOP files

0external actions performed

Workflow delivered
01

n8n intake orchestration

Accept test email and attachment metadata and retain an execution record.

02

Extraction and risk checks

Extract case, type, project, deadline and attachments; route incomplete, sensitive or low-confidence cases to people.

03

Citable local RAG

Search five versioned SOPs and show file, version, section, text and relevance. Stop when evidence is insufficient.

04

Approval and register

Modify, approve or reject before writing SQLite and CSV records. No external action is allowed before approval.

Normal case / verified execution reportNormal case / verified execution report
PRJ-2026-014 was classified as an engineering drawing, with a 2026-08-05 deadline, two attachments, 0.96 confidence and a document-control owner recommendation.
Incomplete case / verified human-review reportIncomplete case / verified human-review report
RFI-2026-088 claimed to include a drawing and revision note but contained no attachments. Drawing and missing-evidence SOPs were cited and outbound response was blocked.
Client handover
  • Importable, execution-tested n8n workflow
  • Local RAG with replaceable SOPs and re-indexing
  • Test-email interface and human-review queue
  • SQLite audit trail, CSV export and acceptance report

Portfolio boundary: this is a de-identified simulated business case, not a client engagement. Live Gmail/Outlook, CDE, SharePoint, CRM and ERP systems are not connected.

SMALLER START / VERIFIED DELIVERY

Make CRM data import-ready and reviewable.

A smaller, fixed-scope starting point. Resolve column differences, duplicates and invalid values across two CSV or Excel files before considering scheduled imports, n8n or RAG.

14source rows
10consolidated master rows
4duplicate rows consolidated
6rows retained for review
01

Field mapping

Retain source context while standardising names, companies, email, phone and dates.

02

Duplicates and conflicts

Merge on stable identifiers and never overwrite an ambiguous value silently.

03

Human review queue

Missing, invalid and conflicting values retain their reason and source file.

04

Re-runnable handover

Deliver clean CSV, an Excel report, a change log and the Python workflow.

Execution summary / actual outputExecution summary / actual output
The acceptance report shows source, master, ready and review counts. Missing values are retained and flagged, never invented.
Review queue / reason per rowReview queue / reason per row
Every exception retains source files, quality status and conflict reasons so the client controls the final correction.
Fixed-scope data-quality packageFrom US$350

Up to two CSV or Excel files and 5,000 rows: consolidation, deduplication, common-field standardisation, review queue, clean master and change log.

Ask about data cleanup

This execution-tested case uses fictional data and contains no customer records. A live CRM or ERP import is outside this starting scope.

WORKING DEMO

Email workflow + RAG with changeable test cases.

This is not a page with hard-coded outcomes. The local demo processes a test email, attachments, SOP retrieval, citations and human-review routing.

MAILROOM / CASE-2026-014REVIEW REQUIRED
Input
Test sender, subject, message body and attachments
Processing
Field extraction, case classification, missing and sensitive-content checks
Evidence
SOP file, version, section, retrieved text and relevance
Control
Low-confidence, incomplete and sensitive cases require human review
HOW WE START

Buy evidence before committing to a rollout.

Before approval: zero outbound messages, zero deletion, zero production-system changes.

01

Understand the operation

Confirm case types, current register, decision rules, exceptions and actions that must remain manual.

02

Run an anonymised pilot

Use 3–20 de-identified examples in a fixed scope. No production account or live data is needed.

03

Integrate only after acceptance

Use accuracy, missing-evidence detection, corrections and handling time to decide what happens next.

NEXT STEP

Bring one repeatedly manual workflow.

Your first email only needs the company, workflow, current tools and approximate weekly volume. Please do not attach confidential or customer data.