AI agents and internal apps for project and facilities teams
We build small tools that take routine work off project managers, engineers and facilities coordinators: status reports, RFIs and submittals, work orders, closeout, spec lookups. Each one is built around the systems you already use, and a person approves everything that matters.
Workflow 1 of 6
Weekly project status, assembled for you
Pulls schedule, cost and field notes into a draft report the project manager edits instead of writing from scratch.
- The job today
- A project manager opens the schedule, the cost report and a week of daily logs, copies the relevant lines into last week's template and rewrites the summary. Often a few hours every Friday, per project.
- What the tool does
- Reads the same sources on a schedule, assembles the draft in your template, flags what changed since last week and leaves the summary for the PM to edit.
- What a person still approves
- The project manager reads, edits and sends every report. Nothing goes to an owner unreviewed.
- What we'd measure
- Hours per report, per PM, per week; and how many edits the draft needs.
Workflow 2 of 6
RFI and submittal tracking that chases itself
Logs each item, drafts the response from your specs and past answers, and reminds whoever is holding it up.
- The job today
- Items live in an inbox and a spreadsheet. Someone checks the log by hand, chases the architect or the sub by email, and searches old projects for how a similar question was answered.
- What the tool does
- Logs each RFI or submittal as it arrives, finds the relevant spec sections and past answers, drafts a response, and sends reminders when an item sits past its due date.
- What a person still approves
- The responsible engineer or PM approves every response. The tool never answers the design team on its own.
- What we'd measure
- Days open per item, hours spent chasing, and items that went overdue.
Workflow 3 of 6
Work orders that arrive complete
Turns a tenant's email or a technician's photo into a properly coded work order in your facilities system.
- The job today
- Requests come in by email, phone and hallway conversation. A coordinator retypes them, guesses the asset and priority, and calls back for the details that were missing.
- What the tool does
- Reads the request, matches it to the building, space and asset, sets a proposed priority and trade, asks the requester for anything missing, and files it in your facilities system.
- What a person still approves
- A coordinator confirms the priority and assignment. Safety items always go to a person first.
- What we'd measure
- Minutes per work order entered, call-backs for missing details, and miscoded orders.
Workflow 4 of 6
Closeout packages without the scramble
Gathers warranties, O&M manuals and as-builts into one checked package before turnover.
- The job today
- In the last month of a project, someone chases every sub for warranties and manuals, checks them against the spec by hand, and finds the gaps a week before turnover.
- What the tool does
- Tracks every required closeout document against the spec from the start, requests what's missing, checks what arrives and assembles the package in the owner's format.
- What a person still approves
- The project manager signs off the package before it goes to the owner.
- What we'd measure
- Hours spent on closeout per project, and documents still missing at turnover.
Workflow 5 of 6
Ask-the-spec
Your staff ask a question in plain English and get an answer from your specs, standards and past projects, with the page it came from.
- The job today
- A field engineer calls the office, the office searches a spec book hundreds of pages long, or someone answers from memory.
- What the tool does
- Searches only the documents you give it, answers in plain English and always shows the section and page it used, so anyone can check.
- What a person still approves
- Answers are a pointer to the source, not a ruling. Engineering decisions stay with your engineers.
- What we'd measure
- Time to answer a spec question, and calls to the office for document lookups.
Workflow 6 of 6
Internal apps your staff actually open
Forms, checklists and dashboards that replace the shared spreadsheet, on the web and on the phone.
- The job today
- Inspections, punch lists and equipment logs live in a shared spreadsheet that breaks when two people edit it, and nobody fills it in on site.
- What the tool does
- A small web and phone app built for that one job, with sign-in, offline use on site where it matters, and the data in a place your other systems can read.
- What a person still approves
- Your team decides the fields, the rules and who sees what.
- What we'd measure
- Time per inspection or entry, and how many entries are complete the first time.
Apps
Web and phone apps for internal teams
Sometimes the right tool isn't an agent at all. It's a form that works on a phone on site, a checklist that can't be skipped, or one screen that replaces a spreadsheet four people edit at once. We build those as proper web and iPhone apps.
How we build
How we build
We start with a working prototype on your data, not a slide deck, so you see it run in days. What you get at the end is yours: the source code, the data and the accounts, in your systems where possible.
Next: how an assessment picks the first workflow, or what it costs.
Questions
Questions about what we build
What do you mean by an agent?
A program that does a defined piece of routine work on its own schedule, such as reading new RFIs, drafting a reply and reminding the person who owns it, and stops for a person to approve anything that matters. It is software with a job description, not a chatbot.
Which systems can you connect to?
Anything with an export, an API or an inbox: Microsoft 365 and SharePoint, Google Workspace, Procore, Autodesk Construction Cloud, most facilities and work-order systems, and spreadsheets. We confirm the specific connections during the assessment.
What happens when the tool gets something wrong?
A person catches it, because a person approves every output that matters. Every action is logged, so we can see why it happened and fix the cause.
Who owns what you build?
You do, including the source code.
Can you build a full app, not just an agent?
Yes. We build web and iPhone apps for internal teams: forms that work on site, checklists, and screens that replace shared spreadsheets.
Pick the workflow. We'll measure it.
Tell us which job eats the most hours. We'll reply within one business day with a yes, a no, or a question.