Theme

Bring repairs, parts, and follow-up into one working system.

Hitchaos is built for small repair shops that still run on paper, phone calls, shelves, and memory. Start with a real job and let the system form around the work.

Open the box Skip the pitch

No credit card. No onboarding calls. Start with the next repair.

Repair workspace

The work order stays alive

Status, notes, parts, estimate, tag and photos stay on the same repair.

Parts and stock

Inventory follows the job

Stock, missing parts and product records stay tied to actual repair work.

Assist in flow

Less typing. More signal.

Scanner flows, URL import and guided drafting reduce mess without becoming another app.

The hook

No demos. No manuals.

Most shop software asks you to stop and configure. Hitchaos starts in the job. The work order becomes the repair workspace, missing parts show up before they bury the day, and stock stays close to the bench.

The fast path

Skip the pitch. Open the box.

See the product first. Start the owner account when you are ready.

Open the box Start now

What usually breaks

Small shops lose time in the gaps between things.

Jobs stall in the gap

The repair lives in one place. The part request lives somewhere else. Pickup waits.

Ordering turns into guesswork

Something gets ordered twice, or not at all, because stock truth and shelf truth drift apart.

Follow-up disappears in the rush

Customer promises, bench notes and next actions fall into paper, texts or memory.

What changes here

The app keeps the thread together.

The work order becomes the workspace

Status, notes, estimate, tag, photos and parts stay on the same repair.

Missing parts become a real queue

Blocked work is visible before it turns into another forgotten phone call.

Inventory and history stay attached

What moved, what was added, and what still blocks the job stays in one thread.

Interactive teaser

Let people poke the product before they commit to it.

These are trimmed demo scenes inspired by the real app surfaces: work orders, inventory and team movement. Enough to feel the rhythm, not enough to become a second app inside the landing.

From intake to pickup

Repair work starts as a living queue, not a spreadsheet graveyard.

Tap a ticket, move the status, type a note, and you immediately understand the operational center of gravity.

What this reveals

Status signal

Status is not decorative. It is the fastest decision cue in the work-order lane, so the color and label have to read immediately.

What is inside

These are the working surfaces, not a demo shell.

The strongest parts of Hitchaos already center on repair work, inventory truth and missing-parts resolution.

Canonical repair workspace

Customer, item, problem, status, estimate, tag and media live on the same work order.

Waiting-parts resolution flow

The app resolves local stock, existing requests and draft input before it writes missing-part truth.

Products with stock and location

Products stay searchable by SKU, location and availability while still working as editable cards.

Repair-owned photos and evidence

If a photo belongs to the repair, it stays attached to the repair instead of disappearing into chat state.

Scanner and guided drafting

Scanner flows, URL import and human-confirmed AI drafting reduce data entry without taking control away.

The starting point is smaller, faster and cheaper.

Big systems sell complete setup. Small shops need the first repair under control, the parts visible, and the next action clear.

Start in minutes, not weeks.

Pay for what you actually use.

Build your system while you work.

Work first. System follows.

Assist inside the workflow

Help shows up where the work is.

Hitchaos uses AI as a server-side, human-in-the-loop layer. It drafts, resolves and enriches, but the operator still confirms business writes.

Missing-part drafting

Messy notes, photos and source URLs can be turned into structured draft input.

Product enrichment

Source URLs and assistant input help fill product records without a giant edit form.

Operational memory

Logs, media and repair context stay with the record instead of getting lost in a side channel.

Why this matters

The browser does not talk to the model directly. `chas-api` performs assistant calls, returns structured suggestions, and the operator still confirms writes. That keeps the assistant useful inside a repair workflow instead of turning it into a chat toy.

Ask your own assistant

Let your AI assistant pressure-test Hitchaos for your shop.

If you already use ChatGPT, Gemini or Claude, take the public Hitchaos brief there. Your own assistant may already know your business, tools, habits and pain points, so it can judge Hitchaos against your real day instead of a generic sales page.

What gets copied

A plain-language Hitchaos prompt with the core workflow and a single-file public brief first. No private data or internal docs.

Web fallback

Preview the prompt

You know my business context better than this website does. Based on what you already know about how I work, what slows me down, what tools I use, and what I actually need day to day, review this public Hitchaos knowledge map and tell me honestly whether it fits me.

Product context:
Hitchaos is a workflow system for small shops that need a public customer site, structured request intake, repair/work-order tracking, product and parts inventory, sales/rental requests, proforma invoices, manual payments and customer-visible notifications. CHAS is the assistant system inside Hitchaos: Context, History, Actions & Suggestions. Mechan.icu is the public tenant-domain layer for customer storefronts.

Public Hitchaos knowledge to use:
- Use the public Hitchaos knowledge if you can access the web.
- Start with the single-file brief first: https://www.hitchaos.com/llms-full.txt
- Focus on the real workflow: public intake, work orders, missing parts, inventory, invoices, manual payments, customer status, and CHAS assistant support.
- Judge fit against my actual shop instead of generic software talking points.
- Use https://www.hitchaos.com/llms.txt and https://www.hitchaos.com/knowledge/index.json only if you want more structure after the first read.
- If web fetching is unreliable, use the single-file brief and mark anything else as unverified.

Core product ideas:
- A customer-facing website can receive callback, repair, quote, sale and rental requests.
- Public requests are intake only: staff confirms customer, availability, price and next action before fulfillment.
- Work orders keep customer, machine, problem, status, notes, media, estimate and parts in one repair thread.
- Missing parts and inventory should stay connected to the work order so blocked jobs remain visible.
- Sale and rental requests should become editable proforma or invoice drafts after staff review, not automatic paid orders.
- Payments and refunds should be recorded against invoices, with manual payment methods supported before online payment providers.
- Customer notifications should send only on visible milestones, not every internal edit.
- CHAS assistance should draft and organize, but business writes stay human-confirmed.

Workflow areas to evaluate:
- Public website setup and service list
- Customer request inbox
- First real repair path and setup effort
- Repair/work-order lifecycle
- Parts, products, inventory and missing-part queues
- Sales, rentals, proformas, invoices and payments
- Customer dashboard and email notifications
- Staff onboarding and daily operations

If you have web access:
- Search for public Hitchaos, CHAS and Mechan.icu information instead of relying only on this pasted brief.
- Prioritize details that matter for my specific business type and ignore generic software-marketing points.
- If you cannot verify something publicly, mark it as unverified instead of assuming it is available.
- Do not treat filenames as the main user interface. Treat them as source material behind a plain-language product explanation.

Use what you know about me first. If anything is missing, ask me about:
- How customers find and contact the shop today
- Whether the first priority is repair intake, sales, rentals or mixed operations
- How work orders and parts are currently tracked
- Whether the shop needs a simple website first or accounting workflow first
- Which existing tools must stay in place

After that, tell me where Hitchaos would help, where it would be overkill, what I should test first, and what setup path would be practical for my business.

Owner entry

Start the shop with the next real repair.

Join creates the owner and workspace. The rest of the system grows from the actual work, not from a week of setup.

Owner first

Join creates the owner path. Team members come later from inside the app.

Trial starts automatically

The first workspace lands in the free-trial path without a sales call.

Draft resumes

If you already started, the flow picks up from the current onboarding step.

Owner first. Workspace next. Then the rest of the system grows from the work.

Thin path

Sign in without a password

Step 1 · Authenticate

Checking your existing session and onboarding state.