A private build · for Ken Titcomb

Owner-controlled shop knowledge —
without replacing your systems.

One private place for the shop's information, with owner-level command over who sees what: controlled folders, role-based access, a clear record, and AI search that only answers from what each role is allowed to see. It sits beside the tools you already run.

A live, Titcomb-branded demo with synthetic shop data — nothing connected to anything you run.

The drag in a shop today

The shop's information isn't lost — it's scattered. And once it's scattered, you lose the one thing an owner actually needs: a clear view of who can see what.

🗂️

Information sprawls

Repair orders, estimates, vehicle photos, vendor docs, PDFs, texts — spread across folders, people, and logins. No single place that's actually the shop's.

🔓

Access is all-or-nothing

Either someone can get into everything or they're locked out and pinging you. There's rarely a clean middle where each role sees just its slice.

👤

Offboarding leaves residue

People move on, but their access lingers in shared drives and vendor portals. Stale logins are the quiet risk nobody's tracking.

No clear record

Ask "who can see the financials?" and the honest answer is a shrug. There's no chain of command for the information itself.

A better operating model

One private file layer the owner controls — additive, sitting beside what you already run. Nobody freelances with sensitive information, and you always know who has the conn.

🗄️

One private file layer

A single controlled place for the shop's information, organized into folders you set. It complements your current tools instead of competing with them — it doesn't become your system of record.

🔐

Role-based access

The owner sees everything. The front counter, a tech, accounting — each role sees only its slice. Set once, enforced underneath, easy to change.

📋

A clear record

A plain, readable view of who has access to what, and what changed. The answer to "who can see this?" stops being a guess.

🤖

Permission-aware AI search

Ask a question and get answers drawn only from the files that role is allowed to see. The AI helps you find things — it doesn't become your system of record. See a preview →

What to test in the demo

The system behind demo.titcomb.org is live and Titcomb-branded, loaded with synthetic shop data. Log in as the owner, then as a tech or the front counter, and watch the access change.

1

Sit in the owner seat

Open the controlled folders as the owner. You see the full shop — repair orders, estimates, vendor docs — in one place that answers to you.

2

Switch roles, watch access change

Log back in as a tech, then the front counter. Each role sees only its slice. That's permission enforced, not promised.

3

Ask the same question as each role

Run an AI search as the owner, then as a tech. The answers only ever come from what that role is allowed to see — nothing leaks across the line.

What this is — and isn't

It's built to lower your risk, not raise it. Everything here is additive and reversible.

Additive — sits beside your tools Reversible — nothing locked in demo data is synthetic No migration you own the information No per-seat bleed No third-party trackers
A note for Ken

Ken — I built this because I keep watching good operators get pushed into SaaS tools that create more dependency than control. I think that underserves people like you, so I wanted to show you a different way — not to replace what's working, just to give the owner one controlled place for the shop's information, with clear command over who sees what.

I set up a live, Titcomb-branded demo with synthetic shop data — no risk, nothing connected to anything you run. Log in as the owner, then as a tech or the front counter, and watch the access change.

I'd value your operator read more than a sales conversation: does this point at a real control-and-visibility problem in a shop like yours, or is it missing the mark?

— Jan Cichocki · ThreadSync