inner pocket.

A full staff,
kept close.

A private team of AI specialists, built around your business. They speak your language, cite their sources, and never share what’s yours — on call around the clock.

Private by design Cites its sources Metered to the penny
The Inner Pocket workspace on desktop and phone: a Regulations Expert answers a pretreatment-permit question with citations, the verbatim regulation text open beside it, while a Process Engineer conversation on the phone takes a dictated question and a photo.
🧮
Estimator
prices from your book
🧪
Chemist
fluent in your process
⚖️
Regulations Expert
reads the actual rules
🚚
Dispatcher
knows every route
🧾
Payroll
your state, your rules

Every team is designed to order — these are one shop's.

The idea

AI with a job description.

Off-the-shelf AI knows everything except your business. So we don’t install software — we staff a team of specialists. A machine shop gets an estimator. A clinic gets an intake coordinator. A manufacturer gets a regulations expert that’s read every rule that touches it. No menu, no template — your team is built from what your people ask all day.

1

We learn the business

A working session about what your people ask all day, which documents hold the answers, and — just as carefully — what must never leave the building.

2

We build the team

Each specialist gets its instructions, its knowledge, and the right AI model for the job — then we tune it against real questions from your floor until the answers hold up.

3

Your team just asks

A workspace under your name, on every desk and every phone, around the clock. Answers cite their sources, and every reply is metered to the penny.

What your people see

Inside the workspace.

Every screen below is the live product, showing the demo company's data. Your specialists, your documents, your name on the door.

A conversation with the Regulations Expert. The answer cites 40 CFR 413.14 and 433.15; the sources drawer shows the verbatim regulation text from the workspace's local copy.

Answers you can check. Every citation is a button — the actual regulation text opens beside the answer, from a copy kept on your own server. Nothing leaves the machine to show it.

The home screen: a greeting, the three conversations you were in most recently, and the five specialists on call.

Your staff, the moment you sign in. Pick up where you left off, or pick a specialist. Conversations name themselves and stay findable.

Company knowledge: uploaded documents with who added them and which specialists read them, the team's saved notes, and the regulation libraries kept on the server.

Your documents, read by every specialist. Drop in the permit, the spec sheet, the handbook — PDF, Word, or Excel — and answers start citing them by file and page.

The phone app mid-dictation: a photo of a pitted chrome rod attached, the spoken question transcribing live, and the Process Engineer's answer above.

Dictate, photograph, ask. An app on every phone — voice instead of typing, a photo of the part in question, one tap from the floor.

A question asked in Spanish is answered in Spanish by the Safety Coordinator, with the cited OSHA section shown verbatim in English in a bottom sheet.

In the language of the question. Ask in Spanish, get the answer in Spanish — and the regulation it cites, word for word, in the original.

The phone home screen with the two most recent conversations and the list of specialists.

Installed, not downloaded. It lives on the home screen like any app, under your company's name — no app store, no update nagging.

Private by design

Built like it's carrying something.

Your quotes, your customer list, your process — where does all that go when your team pastes it into a chatbot? Inner Pocket starts from the other end: what shouldn’t be in the system at all, and who controls the machine it runs on.

🏛️

Yours alone

Every client gets a dedicated, white-labeled workspace. No shared tenancy, no pooled data, nothing commingled with anyone else's business.

💾

One file, one disk

Conversations, people, and usage live in a single database file on a machine you control — not scattered across a vendor's cloud.

🚪

Some things never go in

Every business holds knowledge too valuable to hand any AI. We draw that boundary with you — and build the refusal into the specialists themselves.

🗝️

Access is granted, not assumed

Each person sees only the specialists they're granted. Deactivation is immediate, and an audit trail records every administrative action.

🧾

Metered to the penny

Every answer records who asked, which specialist, and what it cost. Monthly budgets per person and per specialist are enforced mid-conversation.

🤝

The fewest possible parties

Model providers are configured for no logging and no training on your data — and any specialist can route direct to its model maker when fewer hands should touch a request.

"What shouldn't the system know?" is the first question of every engagement — not a checkbox at the end.

Field notes · Buildout №1

What one team looks like.

Our first deployment: a specialty latex products manufacturer in Ohio. Five specialists, each built for a job their people actually have.

⚖️

Regulations Expert

Searches a local, on-disk copy of the actual rules — all of EPA's 40 CFR, OSHA's general-industry standards, FDA's device regulations, and Ohio EPA's administrative code, 30,000+ sections — and answers with verbatim citations, section by section.

Keeps the trains on the rails — no rule left unread.
🧪

Chemist

Fluent in latex compounding and process troubleshooting — with a standing rule written into the specialist itself: proprietary formulas never enter the system.

📊

Accounting

Month-end close, costing, and Ohio manufacturing tax questions, answered like a controller who has seen the books.

🤝

HR

Handbook-grade guidance on Ohio employment rules, hiring paperwork, and the conversations managers dread.

💬

Service Desk

Drafts customer replies in the company's voice — order status, spec questions, the gentle no.

That's their team — not a template. Yours might start with an estimator, a scheduler, a grant writer, or a coder. It starts with what your people ask all day.
See for yourself

Walk into a workspace.

Reading about it is one thing. So we built a workspace for a company that doesn't exist — Ridgeline Metal Finishing, a fictional Ohio electroplating shop — and left the door open. Real specialists, real regulation citations, real admin console. Fictional data. Open the pretreatment-permit conversation and click any citation — the actual regulation text opens beside the answer.

⚖️ Regulations Expert 🔧 Process Engineer 🧮 Estimator 🦺 Safety Coordinator 📋 Order Desk

A different team than the latex manufacturer's above — because every team is designed to order.

Enter the demo workspace →

Sign in as dana@ridgelinefinishing.example · password demo2026

A read-only demonstration on fictional data — the conversations inside are real answers from the live product, preserved as a tour. Your own workspace would be live, private, and yours alone.

The platform

Runs like something you'd own.

Manage

Plain-English control

Specialists are edited like documents — instructions, knowledge, starter questions — by whoever runs your office. No vendor ticket queue.

Models

The right model per job

Claude, GPT, or Gemini — the right model per specialist, swapped from a dropdown as better ones ship. One bill.

Spend

Budgets that hold

Monthly caps per person and per specialist, enforced mid-conversation with a courteous stop — never a surprise invoice.

Knowledge

Your documents, read by every specialist

Permits, spec sheets, the handbook, the SDS binder — PDF, Word, or Excel — indexed on your server and cited by file and page.

Reach

Anywhere your people are

Desktop and an installable phone app, from the front office to the plant floor to the truck. Dictate a question, photograph a part, ask in any language. One sign-in.

Record

A ledger, always

Usage, cost, and administrative changes — recorded as they happen and readable by the person who signs the checks.

The admin console overview: questions this month, people active, spend against the cap, answers rated; a feedback queue with actions to add a note for the specialist, add to the company file, or dismiss; spend by specialist; and a people table.

The console the owner actually uses. Who asked what, what it cost, and every 👎 as a queue — each one turns into a note the specialist will remember, a line in the company file, or nothing. No prompt engineering, no vendor ticket.

An engagement

Beginning to end, then onward.

01

Discovery

What your people ask, what documents answer it, what must stay out. One working session.

02

Buildout

Your team of specialists, assembled and tuned against real questions until the answers hold.

03

Deployment

On your infrastructure or a dedicated instance — your people onboarded, budgets set, access granted.

04

Stewardship

Knowledge kept current, new specialists as needs surface, models upgraded as better ones ship.

Tell us what your people ask all day.
That's the whole first meeting.

We'll come back with the team we'd build, what it should know, and where the private lines get drawn. Pricing is per buildout — no seats, no tiers, no surprise invoice.

Start a conversation

Or write us the old way: dweingart1@gmail.com