AI Platform
An AI workforce.
Backed by industry knowledge.
One workspace, built on a shared memory of millions of construction codes and standards — with agents that work in parallel to put it to use. A person signs off before anything goes out the door.
Productivity in construction is down 40% since 1970.
The construction lifecycle is broken.
Every stakeholder works from their own inbox, spreadsheet, and copy of the plans. A code interpretation, a revision, a sign-off — each has to travel between desks with no shared system and no shared source of truth. Communication breaks down. Approvals stall.
Professionals and AI agents need a platform
Ichi is the AI platform for construction.
Agents scale with demand
When volume grows, Ichi spins up more agents — and every run trains them on real construction work. The more your team runs, the sharper it gets.
Construction memory is shared
Codes, standards, project history, the issues your team already solved — today nobody holds it all in one place. Ichi's goal is one memory, shared by everyone who touches the project.
People stay in charge
Agents prepare the work; the final call is always yours, made with the professional judgment no model replaces. Every decision feeds the memory, so both sides keep getting sharper.
The stack
Four layers, working together.
01
Code research & calculations
1 hour → 5 min
Plain-language questions, cited answers from licensed national, state and municipal books — including local amendments. The foundation every layer above calls.
02
Document analysis
hours → minutes
Construction documents run hundreds of pages and are notoriously hard for AI. Ichi reads them the way a professional does: block by block, page by page, with file citations back to the exact source.
03
Agentic workflows
8 hours → 15 min
Big jobs split across agents working in parallel, then recombined into one finished deliverable — a comment letter, a notice, a response table — in your own format.
04
Orchestration + integrations
weeks → hours
Agents taking the work end-to-end under human orchestration: drafting the document, running the checks, then queueing all of it for a person to approve — connected to your other systems through API and MCP.
File intelligence
The sets that break everything else.
A permit set is hundreds of sheets of drawings, schedules and title blocks — the format general-purpose AI handles worst. Ichi reads the whole set the way a reviewer does, sheet by sheet, and remembers which sheet said what.
A0.10 · Code data & occupancy
Occupancy B / S-1 · Type V-B · sprinklered
Reading the whole set. Not a summary of the first few pages — every sheet is opened, split into its parts, and filed with the coordinates of what was found. Ask a question 200 sheets later and the answer still knows it came from A0.10.
Whole sets, not samples
Upload the set as issued — hundreds of sheets across every discipline. No splitting it up first, no picking which pages matter.
Read like a professional
Block by block, sheet by sheet: drawings, schedules, title blocks and the notes in the margin. Not a summary of the first few pages.
Every answer points at a sheet
Findings cite the sheet they came from, so checking the work means opening one page — not hunting a PDF for something that may not be there.
Everything else too
Correction letters, specs, submittal packages, Word files, spreadsheets, site photos. Plansets are the hard part; the rest comes along.
How the reading actually works — location, visual understanding, markups, cloud sync — see the Files page →
Artifacts
It doesn't stop at the answer.
Chat gives you a reply. A workflow gives you the deliverable — drafted on your letterhead, in your format, with a citation under every claim. Sometimes it's the first draft. More often now, it's the whole thing, waiting for a signature.
What goes in
- 01Your comment-letter templatethe format your department already issues
- 02The review findingsevery issue, with the sheet it came from
- 03Your instructionssaid the way you'd say them out loud
- 04Letters you've signedso the tone matches the last one you sent
You never manage these. The workflow already holds your format, your standards and the documents your team has signed — which is why the draft sounds like you wrote it.
Provide the occupant load calculation for Suite 200 on sheet A0.30, including the function-of-space areas used.CBC 1004.5
Submit the special inspection program for the post-installed anchors shown on S3.01 prior to permit issuance.CBC 1705.3
+ 7 more findings, each cited
Versions, anchored comments, sharing, export — the document's whole life is on the Artifacts page →
Jurisdictions
- Comment letters, drafted
- Notices of violation
- Applicant emails and responses
- Plan review comment sets
Builders & architects
- RFI responses
- Submittal reviews
- Comment letter responses
- QA/QC drawing markups
Both sides
- Completeness reports
- Code determination memos
These lists are samples, not the catalog. Most of what runs in Ichi today was built for one team's specific job — there are a hundred more where these came from. See the custom workflows →
End to end
The workspace does the job, not just the answer.
One intake, end to end: the workflow runs on its own, every field cites its source sheet, and the one conflict goes to a person — who resolves it right in the thread. Then the finished record ships: link, export, or API.
A demo of the Ichi workspace. A permit-intake workflow runs on a 34-file submittal, ticking through its phases on its own. It compiles a unified project record — a table where every field cites the sheet it was read from — and flags one conflict between the application's valuation and the drawing set instead of resolving it silently. A colleague replies in the same thread that the drawings are current, the user asks Ichi to use the addendum value, and only that row updates, now cited to Addendum 02 and marked verified. The finished record is shared with the department, where six people see the same live table, and can be exported to CSV or PDF or served to a permit system through the API.
( 01 / 04 )
A workflow runs on its own
In production
Deployed in the real construction world.
From a city clearing its housing queue to a 170-person firm cutting code research to minutes — the same platform, trusted on both sides of the counter.
Questions
The ones every evaluation asks.
Go deeper on any layer.
Each of these has its own page.
Code Compliance
Licensed books, state amendments and local ordinances — the layer every answer stands on.
Files
Plansets read sheet by sheet, every block located, every answer citable to the spot.
Artifacts
The finished document: versioned, discussed, shared and exported without leaving Ichi.
Memory
Personal, company, project and jurisdiction knowledge, applied to every answer.
Integrations
Procore, SharePoint, OneDrive, SSO, API and MCP.
Security
Where the data lives, who can reach it, and what we will and won't claim.
See it on your own documents.
Bring your own documents if you'd like — or we'll use a sample set. Either way, it's the same platform for both sides of the counter.