AjaxOPS is the intelligent operations layer for teams running complex, multi-site portfolios. It sits on top of the systems you already run and gives one operator a single view across every property.
Built by a 26-year building operator. Live on a full-service hotel property today.
See it in action
The problem
Every property has its own CMMS, its own PMS, its own BMS, plus the spreadsheets, the email threads, and the chief engineer's memory. None of it rolls up. If you're responsible for more than one building, you already know:
Asking "what's open across the portfolio right now?" means logging into six dashboards and calling three people. The answer is always stale by the time you assemble it.
The vendor history, the as-builts that actually match the building, the reason that valve is throttled, when the person walks, the knowledge walks with them.
Briefings, work-order triage, bid comparisons, scopes of work, vendor follow-up emails. Hours of drafting that keep your best operators at a desk instead of in the building.
The shift
AjaxOPS is not a system of record and there is no rip-and-replace. Your CMMS, PMS, and BMS stay exactly where they are. AjaxOPS sits above them, reading the building documents, the work orders, the emails, the prints, and gives your team one place to see, decide, and act.
Vertical-agnostic by architecture, hospitality, CRE, industrial, healthcare. Your systems stay. AjaxOPS reads across them.
Integrations
AjaxOPS sits on top of your existing stack, it does not replace it. It reads across the platforms your properties already run, grouped by what they do. Run something that is not listed? It is almost certainly on the roadmap or a short build away. Tell us your stack.
Sit on top of your building automation and the controllers under it: Tridium Niagara and JACE, Johnson Controls Metasys, Honeywell, Siemens Desigo, Automated Logic (ALC) WebCTRL, Distech, Schneider EcoStruxure, Delta Controls. Read points and alarms across buildings that were never meant to talk to each other.
HotSOS, Angus Anywhere, Building Engines, ServiceChannel, Corrigo, UpKeep, Limble, IBM Maximo. Triage, route and roll up work orders across every property in a single view.
Oracle OPERA, Infor HMS, Maestro and the property systems your front desk already runs. Tie building operations back to what is happening in the property.
ENERGY STAR Portfolio Manager, utility and submeter data, and building telemetry. Benchmark consumption and catch drift before it lands on the invoice.
Google Drive, Outlook and Exchange, SharePoint, plus a dedicated email address per property. Drawings, contracts and threads read into context, nothing stored server-side.
Yardi, MRI, Sage Intacct, QuickBooks. Line up scopes, bids and work orders with the numbers that actually get reported.
New connectors ship continuously. Your systems stay exactly where they are: no migration, no rip-and-replace.
How it works
"Ask the AI" is the wrong model for operations. AjaxOPS is a library of engineered actions, each one a button that already knows your property, your documents, and your history. One click produces work product, not a conversation.
Open work orders, overnight emails, vendor status, and what needs a decision today, assembled across the portfolio before your first coffee.
Drop in a stack of contractor bids. Get a clean side-by-side: scope gaps, exclusions, pricing anomalies, and the questions to ask each bidder.
From a photo, a punch list, or a description, a contractor-ready SOW built from the field reality, not a template.
What's urgent, what's routine, what's been sitting too long, and what pattern is forming, across every building at once.
Drafted chasers with full thread context, the quote that's two weeks late, the warranty claim, the proposal that needs clarification.
Print sets, contracts, and reports ingested and queryable. Ask which sheet shows the riser, get the sheet, not a guess.
Talk to your building from anywhere
Every property gets its own email address. No app to open, no login, no VPN. If you can send an email from your phone, you can put AjaxOPS to work standing in the mechanical room or sitting in the truck.
Snap a photo of a failing component and send it in. AjaxOPS reads the photo, pulls the prints that matter, and emails back a condition read, a draft scope, and the next move. The building answers you, wherever you are.
Copy your property address on the vendor quote, the RFI, the invoice, the thread that matters. AjaxOPS classifies it, extracts the attachments, and folds it into the building knowledge base. The institutional memory builds itself, so the next question you ask already knows the answer.
A teammate per property
Every property gets its own AjaxOPS teammate, scoped to that building's prints, history, and vendors, working in the channels your team already uses. It only ever sees its own building. Above them, the operator gets the portfolio roll-up that no single building can see.
Each property's teammate is connected to that property's documents and history. Memory and access stay per building, so one site's records never bleed into another's. Sensitive properties stay walled off.
Your engineers, PMs, and vendors hand it a task in the channel they already use, follow along as it works, and anyone can steer it or pick up where it left off. A shared teammate, not a personal chatbot.
Open capital items, risk, and status across every property in a single view, the cross-portfolio picture the building-level teammates are deliberately not given.
Proof
A chief engineer's photo of a failing balcony became a condition assessment, a structural-engineer scope of work, and outreach to licensed SE firms, in fifteen minutes. The engineer called back before the coffee was done.
Full-service hotel property · read the full story →
Hundreds of indexed drawing sheets, queryable in plain language. A chilled-water pressure problem worked to a sound interim fix without the as-builts in hand.
Live production deployments · hospitality portfolio
What to expect
Onboarding AjaxOPS is deliberately light. Your systems stay where they are, you hand over one property, and it goes to work. Here is the whole path.
Request access and tell us your properties and the systems you run. We set up your workspace, branded to your name and colors.
Hand over one property's print set and connect or forward from the systems you already run: CMMS, PMS, BAS, and email. Nothing is ripped out or migrated.
AjaxOPS reads the drawings sheet by sheet, builds the property knowledge base, and stands up the property's own email address. Usually days, not months.
Morning briefings, work-order triage, bid analysis, and SOW drafts, in the channels your team already uses. The 14-day trial converts automatically; cancel anytime during it.
No professional-services invoice, no six-month implementation. If it does not earn its keep in two weeks, walk away.
Tell us about your properties and the systems you run. We'll show you exactly what AjaxOPS does with them, no migration, no rip-and-replace, no six-month rollout.
Request access