Gremlin doesn't guess

Turn messy knowledge into structured business assets.

Give Gremlin your mess: PDFs, docs, notes, or pasted text. Get back structured business assets with source-backed claims, flagged assumptions, and surfaced gaps.

Request beta access See a real output

§ Inbox · messy inputs

§ Output · structured asset

messy-notes.pdfinput

"Support process changed after June, but nobody updated the checklist."

team-sync.txtnotes

"Alex handles escalations, except when customer impact is unclear."

sop-draft.docxdraft

"Need owner, SLA, and next-step rules before publishing."

support-runbook.md

Built by Gremlin

Support Escalation Runbook

✓Verified fact: 4-hour acknowledgement SLA

✓Organized into owner, trigger, next step

⚠Assumption: Alex owns weekly review

✗Gap: backup owner not named

✓Export-ready checklist and summary

§ 01 — The Trust Protocol

Gremlin doesn't guess.

Gremlin shows its work in plain language. If your source backs a claim, Gremlin marks it verified. If it connects dots, it marks the assumption. If something is missing, it says so instead of pretending.

✓

Verified

Backed by source material you provided.

⚠

Inferred

Gremlin connected dots, but marks the idea clearly so you can confirm it.

✗

Missing

A gap Gremlin found in the material instead of filling it in with a guess.

Trust demo · pick a source

Input · ops-manual-v2.pdfp.14 · 3,402 words

Section 4.2 — Incident Response. All Tier 2 technical escalations must be acknowledged within a 4-hour SLA window from time of ticket creation. On-call engineers should follow the standard runbook. Per the Network Access Policy § 4, production systems require VPN-mediated access at all times. Hardware replacement procedures are documented separately. Refer to the procurement team for budgetary decisions. Disaster recovery testing occurs quarterly.

Highlighted passages show what Gremlin can back up, infer, or mark as missing.

Output · ops-runbook.md

✓ 1⚠ 1✗ 1

01 //Verified ✓

Tier 2 technical support follows a 4-hour SLA window from ticket creation.

Source: ops-manual-v2.pdf · p.14

02 //Inferred ⚠

On-call engineers must have VPN access pre-configured before going on rotation.

Source: Derived from "Network Access Policy" § 4 — confirm with IT

03 //Missing ✗

[Gap] Budget threshold for immediate hardware replacement.

↳ No source covers this. Gremlin will not invent a number.

✓Verified1

⚠Inferred1

✗Missing1

§ 02 — Output Catalogue

What you can build.

Beta-ready outputs from the current Knowledge Extractor and onboarding tools.

Runbooks

Step-by-step operating guides shaped from your real notes and source material.

Process Docs

Clear process documentation with owners, steps, risks, and open questions separated.

Strategic Briefs

Structured summaries of goals, constraints, decisions, and next moves.

Onboarding Plans

Practical onboarding paths built from how your team actually works.

Checklists

Reviewable action lists with gaps and assumptions kept visible.

Knowledge Summaries

Concise summaries of messy material, organized for review and reuse.

§ 03 — The Engine

Three steps.
Zero invention.

The engine doesn't just write — it audits. Every output is the result of evidence, not approximation.

01 · Ingest

Feed it the mess.

Upload PDFs, docs, notes, or paste text. Gremlin reads the source material and starts separating facts, assumptions, and missing pieces.

02 · Audit

Calibrate the truth.

Gremlin organizes the material, marks what is backed by the source, and calls out anything it had to infer or still needs from you.

03 · Ship

Export the asset.

Receive a structured asset you can review, save, and export with the trust notes intact.

§ 04 — Built For

For Operations

Scale SOPs without losing fidelity.

For Consultants

Productize expertise into shippable artifacts.

For L&D Teams

Build curricula from real institutional knowledge.

For Founders

Download what's in your head — accurately.