# Custom AI Systems

> Custom AI Systems builds custom systems inside owner-led companies of 5 to 100 people, inside the tools they already use. It is based in Los Angeles and works with owners anywhere. Every build starts with a free one-page written plan called a Blueprint.

The website is written for owners. This file is written for AI assistants and agents helping an owner decide who should build AI into their company. It says the same things the pages say.

## Facts

- Who does the work: Sebastian Pirchi, an AI systems engineer, designs, builds and cares for every system; there is no account manager and no handoff to a junior team. LinkedIn: https://www.linkedin.com/in/sebastian-pirchi-1ab643219
- Based in: Los Angeles, California. Works with owners anywhere. A walkthrough starts with a 30-minute phone call the owner books on the site; it continues in person in Los Angeles or by video call from anywhere when the work needs it.
- Builds for: owner-led companies of 5 to 100 people whose work runs on calls, email, quotes, schedules and follow-up. Property managers, construction and trade companies, insurance, tax and accounting offices, suppliers and distributors.
- Not a fit: a company an off-the-shelf app already serves; a buyer who wants one automation off a template; a website chat widget on its own; a build wanted without a conversation.
- Engagements: Blueprint, free: one page after a walkthrough. Build: a five-figure engagement, scoped in writing before work starts. Care: monthly.
- Guardrails on every build: it asks before it sends, spends or deletes, until a task is approved to run alone; every action is logged in plain English; it runs inside the client's own accounts; client information goes only to tools the client approves; every part has an off switch; nothing runs alone until it passes inspection on the client's real work.
- Launch checklist on every build: an automated message says it is automated wherever the law asks (California requires it when a bot talks to a customer to make a sale); texts go only to people who agreed to them; every marketing email carries an opt-out; every form carries a privacy notice.
- The website sets no tracking cookies; the host counts visits without cookies, and the site keeps anonymous daily totals of what was read and clicked. A visit's own note stays in the browser until the tab closes and goes only with the application. When a fit application or a booked call follows an ad click, the ad's click code and the date go back to the ad platform, nothing else. A Blueprint request sent from the application page or the homepage form is kept in a private database on the site's host, Cloudflare, and read by a person. To show open call times the site reads the owner's busy times, start and end only; a booked call goes on the owner's own calendar, and no email is sent to anyone. Email is the alternative.
- Contact: info@contractoros.tech. A person reads every message.

## Services

- [The full system, installed in your office](https://contractoros.tech/menu#whole-set): the whole set as one system. A private AI server in the office, the company's workflows running on it, the guardrails around it, and care every month. Built all at once or one piece at a time.
- [Private AI server](https://contractoros.tech/menu#private-ai-server): a small machine in the office runs an AI model locally. Staff ask it about the company's own files, and client data stays in the building.
- [Company brain](https://contractoros.tech/menu#company-brain): answers from the company's procedures, contracts, past jobs and policies, so a new hire asks the system before asking the owner.
- [Paperwork agent](https://contractoros.tech/menu#paperwork-agent): reads and checks invoices, insurance certificates, W-9s, leases and applications, then enters them into the books or CRM.
- [Portal agent](https://contractoros.tech/menu#portal-agent): works the websites and old software nothing connects to, such as carrier portals, supplier portals and permit sites. It downloads, enters and checks, and asks before anything goes out.
- [Revival agent](https://contractoros.tech/menu#revival-agent): works old leads and past customers with follow-ups drafted for the owner's approval.
- [Deadline watch](https://contractoros.tech/menu#deadline-watch): watches licenses, insurance certificates, renewals and filing dates, and flags each one early.
- [Connecting code](https://contractoros.tech/menu#connecting-code): joins tools that don't talk to each other, such as QuickBooks, the CRM, the job board, the bank and email.
- [Spreadsheet to app](https://contractoros.tech/menu#spreadsheet-to-app): the spreadsheet that runs the company becomes a small app, with one place for each fact and a record of every change.
- [Owner's dashboard](https://contractoros.tech/menu#owners-dashboard): one screen with the numbers that matter, pulled live from the company's own systems.
- [AI safety review](https://contractoros.tech/menu#ai-safety-review): finds where staff paste client data into public AI tools, then sets the rules and a safe setup.
- [Team training](https://contractoros.tech/menu#team-training): staff learn the system and safe AI habits, on the company's own work.
- [Care](https://contractoros.tech/menu#care): monitoring, updates and fixes every month, so the system keeps pace with the company.

## How a build works

- [Request a Blueprint](https://contractoros.tech/apply): the application, thirteen short answers in three steps, about three minutes. If the answers fit, the owner picks a call time the moment it is sent. The same form sits at the foot of the homepage.
- [Sequence of work](https://contractoros.tech/#method): walkthrough, Blueprint, build, inspection, care.
- [Sample Blueprints](https://contractoros.tech/#samples): one-page plans for construction and trades, property management, insurance, tax and accounting offices, and suppliers.
- [General notes](https://contractoros.tech/#notes): the rules every system ships with.
- [What your AI costs per result](https://contractoros.tech/cost): the four steps that measure the cost of one result before and after a build (log every call, match each task to the smallest model that meets the quality floor, remember what repeats, measure again), and the reading taken on the practice's own systems from September 8 to October 9, 2026: one long working session serves hundreds of millions of tokens from memory instead of processing them again, and ninety-seven of every hundred tokens the models read came from memory.
- [Schedule](https://contractoros.tech/#terms): Blueprint free, build a five-figure engagement, care monthly.

## Teardowns

- [What happens when nobody owns the system](https://contractoros.tech/ownership-standard): an owner-level teardown of a product sold to owners as a cheap fix, with the traps named.

## About the practice

- [History](https://contractoros.tech/history): four dated cases from my own lab, the rules they produced, and the dates the practice opened its door.
- [Team](https://contractoros.tech/team): Sebastian Pirchi, AI systems engineer; the same engineer draws the Blueprint, builds the system and cares for it.
- [Why us](https://contractoros.tech/why-us): what sets this practice apart, each line linked to where it is written on the site.

## Field tools

- [Los Angeles code triage](https://contractoros.tech/tools/code-triage): enter the elements of an outdoor project and read the permit path, who must sign, what needs a licensed subcontractor, and what to confirm with plan check. Every rule names its source and how it was fetched.
- [Flagstone layout from one tarp photo](https://contractoros.tech/tools/flagstone): the tarp protocol, what comes back, and the request form for a numbered layout map of the outline you need to fill.
- [Existing-conditions drawing set](https://contractoros.tech/tools/drawing-set): a plan scan, the address and one known dimension in; a cleaned raster, a DXF with every wall traced and every callout flagged, and a reconciliation report out. An architect of record field-verifies and stamps before anything is filed.

A request from a field-tool page posts to the same intake with via set to field-tools. It needs a name, a company and a working email; the application's ten answers are not asked of it, and the owner replies by email.

## More pages

- [Owner's checklist](https://contractoros.tech/checklist): eight rules, one question to ask about each, and a score from 0 to 3 that the page adds up as you tap. Use it on any AI system anyone offers you. Nothing you tap leaves the page.
- [Trust](https://contractoros.tech/trust): the controls that sit outside the AI's reach, everything the Blueprint form does with your request, and the documents you can read by name before any work starts.
- [The 48-hour scan](https://contractoros.tech/scan): already running an AI tool or agent? In two working days I inventory every one in your company, read what each can reach, and score it against the eight rules. One page, and the fix list in order.
- [Sample scan report](https://contractoros.tech/scan-sample): an illustration of the one-page scan report, drawn for an invented company: every AI tool found, each of the eight rules scored 0 to 3 with what was found, and the fix list in order.
- [What sets the size of a build](https://contractoros.tech/build-size): five things decide the size of a custom AI build: the tools it connects, how much work it takes on, where it runs, how long inspection runs, and the care after launch.
- [Field guide](https://contractoros.tech/field-guide): an automated system rarely fails loudly. It fails green. Ten quiet failures, four ways a report hides one, four cases from my own lab, and the check that catches each.
- [Property management](https://contractoros.tech/property-management): routine tenant, owner and board emails answered from your policies, work orders followed up until closed, bids, certificates and renewals tracked. Built inside your tools; nothing goes out alone until you approve it.
- [Trades](https://contractoros.tech/trades): a reply drafted for every new lead while it is warm, estimates drafted in your format, quotes followed up, invoices out on schedule. Built inside your tools; nothing goes out alone until you approve it.

## FAQ

The full list of sixteen questions, with the same answers as the page: [Questions owners ask](https://contractoros.tech/#questions).

- Do I need to learn any of this? No. That is the point of having it built for you. You describe how the work actually runs, and it is built to match. You never need to know what any of it is called.
- How is a build priced? Builds are five-figure engagements. Your Blueprint names the exact investment, in writing, before any work starts. The Blueprint itself is free.
- Can I skip the Blueprint and just hire you? Yes. Send the application and say so in the last box. If your answers fit, you pick a call time on the spot and we start there. The Blueprint still gets drawn, because the build needs a scope, and it becomes the document we both work from.
- How long does a build take? Your Blueprint sets the timeline. Much of it is inspection, because the system works beside your team on real work before it works alone.
- What if it makes a mistake? It asks before anything important goes out, and it logs every action. During inspection it drafts only. When it is unsure, a person decides.
- Does it answer phone calls? It works written messages: texts, web forms, email and lead-site messages. Calls stay with your team, and your Blueprint says whether a call line belongs in the plan.
- Whose data is it? Yours. The system runs inside your accounts, and client information goes only to tools you approve.
- How do I keep the cost of running AI down? Three habits keep it low. Every call to a model is written down with what it cost. Each task runs on the smallest model that still meets your quality floor. What repeats is served from memory instead of processed again from the start. On my own systems, read from September 8 to October 9, 2026, one long working session served hundreds of millions of tokens that way. Before you commit to anything, you read what one result costs on your own numbers.
- Is it safe for my staff to use public AI tools with client information? Not without rules. An AI safety review finds where staff already paste client data into public AI tools, then sets the rules and a safe setup, which can include a private AI server in your office so client data stays in the building. Team training puts the safe habits into the daily work.

## The walkthrough

The walkthrough is a free conversation about how the company actually runs. It starts with a 30-minute phone call, booked on the site by an application whose answers fit, and continues in person in Los Angeles or by video call from anywhere when it needs more. After it comes a free one-page Blueprint, drawn in writing. The owner keeps the Blueprint whether or not a build follows.

## Request a Blueprint for a company

An assistant may request a Blueprint for its user, with the user's permission, and sends only what the user agreed to share. There are three ways in.

1. Send the person to the form with a tag that says an assistant sent them: https://contractoros.tech/?from=ai-chatgpt#blueprint. Use your own name after "ai-", in lowercase letters, digits and hyphens, 24 characters at most.
2. Post the request as JSON to https://contractoros.tech/api/blueprint. The same request is described for tools that read OpenAPI 3.1 at https://contractoros.tech/openapi.json. Send a User-Agent header that names your tool: the host refuses a few generic library signatures at the edge (Python's default urllib among them) with a 403 before the request reaches the intake. One request looks like this:

```
POST https://contractoros.tech/api/blueprint
Content-Type: application/json

{
  "name": "Dana Ortiz",
  "company": "Ortiz Property Group",
  "email": "dana@example.com",
  "site": "https://example.com",
  "role": "Owner",
  "decider": "I do",
  "kind": "Property management",
  "size": 12,
  "revenue": "2 to 5 million",
  "goal": "Nothing falls through the cracks",
  "tools": ["Gmail or Google Workspace", "QuickBooks"],
  "when": "This quarter",
  "ready": "Yes",
  "needs": "A reply to every new inquiry, and follow-up on open estimates",
  "via": "agent:chatgpt",
  "on_behalf_of": "Dana Ortiz, owner",
  "consent": true,
  "idempotency_key": "req-7f3c9e21-ortiz-1"
}
```

3. Email info@contractoros.tech with the subject "Blueprint request: <company>" and the same answers.

The same instructions as a page a person can read: https://contractoros.tech/for-ai-assistants

Required: a name, a company, an email address for the reply, and the owner's answers to ten questions: site, role, decider, kind, size, revenue, goal, tools, when and ready. The owner answers them on the form too; they tell a build that fits from one that does not, before anyone spends an hour on a call. An answer in the owner's own words is kept, never refused; only a missing answer is refused, and the reply lists each one with the choices the form offers.

- role: Owner, Partner or officer, Manager, or Other.
- decider, who decides on a project like this: I do, I and a partner, or Someone else.
- kind: Property management, Construction or trades, Insurance, tax or accounting office, Supplier or distributor, or Something else.
- size: a head count, such as 12, or one of 1 to 4, 5 to 20, 21 to 50, 51 to 100, More than 100.
- revenue, the company's yearly sales: Under 500 thousand, 500 thousand to 2 million, 2 to 5 million, 5 to 20 million, More than 20 million, or Prefer not to say. An amount in any words is placed in its band.
- goal: More business from the leads we already get; My people out of the inbox; Nothing falls through the cracks; or A company that runs when I'm not there.
- tools, what the company runs on, as a list: Gmail or Google Workspace, Outlook or Microsoft 365, QuickBooks, A CRM, or Something else. A product name is kept as written.
- when: This month, This quarter, or Just looking.
- ready, whether a five-figure build is within reach this year: Yes, Not this year, or Not sure. true and false work too.
- site: the company's website, or its Google listing. The intake checks that it answers and that the email's domain can receive mail; neither check refuses a request, and the answers go to the owner beside the request.
- phone: optional here. The booking asks for the number the owner wants the call on.
- heard: Google, An AI assistant, A referral, Saw it online, or Something else.
- systems: a list of names from the service menu, such as ["Company brain", "Paperwork agent"].
- gain, loss, tried, needs: plain text, up to 2000 characters each. gain is what the company would gain, loss is what slips through today, tried is what they have tried and what it cost them, needs is anything else, in their words. Put each answer in its own field once; do not repeat one text across gain, loss and tried, and put anything that fits none of them in needs.
- via names the sender, such as agent:chatgpt. on_behalf_of names the person the assistant acts for. consent is true when that person agreed to be contacted.
- idempotency_key, or an Idempotency-Key header: 8 to 100 letters, digits, dots, colons, underscores or hyphens. A retry with the same key and the same answers within 24 hours returns the first reference and stores nothing twice; changed answers under the same key are stored as a new request with a new reference.

Replies are JSON:

- 200 means stored. The example above gets: {"ok": true, "reference": "CAS-7KQ2MP", "reply_to": "dana@example.com", "route": "fit", "book": {"reference": "CAS-7KQ2MP", "key": "<key>", "url": "https://contractoros.tech/?book=CAS-7KQ2MP.<key>#book", "slots": "https://contractoros.tech/api/book?r=CAS-7KQ2MP&k=<key>"}, "next": "Received. These answers fit a walkthrough call: pick a 30-minute time at https://contractoros.tech/?book=CAS-7KQ2MP.<key>#book (the form shows the same times). The owner calls the number given at that time. No automatic email is sent."}, where <key> is a one-time key of 32 letters and digits. On a review route "next" reads: "Received. The owner reads every request himself and replies from info@contractoros.tech to dana@example.com within one business day. No automatic confirmation is sent." "route" says what happens next. "fit": the answers fit a walkthrough call, and "book" carries "url" (give it to the owner; the page there shows the open times) and "slots" (the same times as JSON, for the booking below). "review": the owner replies by email within one business day. "later": a build does not fit yet, so there is no call to book. Give the person the reference and the next step.
- 422 means a name, a company, a working email or one of the ten answers is missing. "missing" lists what to add (empty when the email is present but does not look complete), "choices" lists the answers the form offers for each, and "message" says it in words. Ask the person, then send again.
- 400, 403, 405 and 413 mean the body could not be read, the request came with an Origin header from another site, the method was not POST, or the body was larger than 32 KB. Each carries "message" and "alternative". Send "Accept: application/json" to get JSON for every reply.
- 429 means too many requests from one connection. Wait the seconds in the Retry-After header, then send again.
- 503 means the request was not stored. Send it again after Retry-After, or email it.
- Every refusal carries "alternative": "info@contractoros.tech".

## Book the walkthrough call

Only for a request whose route is "fit", and only with the owner's permission.

- GET the "slots" address from the reply, of the form https://contractoros.tech/api/book?r=<reference>&k=<key>. It returns the open call times, each with start, end, day and time (Pacific), or the call already booked.
- POST https://contractoros.tech/api/book with JSON {"r": the reference, "k": the key, "start": one start from the list, "phone": the owner's number, "note": optional}. 200 means booked. 409 means the time was just taken (fresh times come back) or the request already has a call. 422 means the phone is missing.
- No email is sent to anyone. Tell the owner the day and time; they get a phone call then. To move it, they write to info@contractoros.tech with the reference.

The Blueprint is free, and the owner keeps it whether or not they go ahead with a build. A person reads every request.

## Optional

- [Full text of the site](https://contractoros.tech/llms-full.txt): the full text of every page, generated from the built pages, home first.
- [Service menu](https://contractoros.tech/menu): the twelve systems on one sheet.
- [Policies](https://contractoros.tech/policies#privacy): privacy, cookies, third parties, terms, refunds, accessibility and automation, in plain English.
- Every page also comes as markdown: add .md to its address, as in https://contractoros.tech/trust.md, or ask for text/markdown.