Connected by designConnections through Iris
Connect the tools you already run through Iris, our library of self-serve connectors.
Explore integrations →Bring structure to the work — from projects and meetings to contracts, people and assets.
The operating system Arc Theory runs on. Every client build starts from this proven model.
Scope the work, keep decisions close, and connect delivery to the people and commitments behind it.
Who owns what, what's at risk, and who hears about it — held as structure rather than as meeting memory. The status report stops being a document someone writes on Thursday night.
The unit of delivery. Work items carry the doing, work orders carry the commitment behind them — and agents sit in the assignee field next to people, not in a separate panel bolted on the side. This is the same board we're in every day, and the one you're given.
Our Chrome extension submits tickets straight into the board from wherever you already are — with automated URL and screen capture attached.
Agenda in, transcript out, actions committed. Insights read what was actually said and turn it into work items, risks and decisions in the system — instead of notes someone re-types on Monday and half-remembers by Friday.
09:14 Lead — let's get the reporting export in before the demo.
09:15 Client — can we bulk-approve vendors too?
09:16 Lead — good idea. and a weekly digest, Monday mornings.
09:17 Client — love it. flag the at-risk items up top.
Add CSV export to the reporting view
Ship the weekly digest, Mondays 8am
As an admin, I can bulk-approve vendors
Surface at-risk items on the home dashboard
Everything with money attached, tied to the work that spent it. Time and delivery draw down contract balance as they happen, so the number in front of a client is current — not a month-end reconstruction nobody fully trusts.
One record per person and organization, shared by everything else. The stakeholder on a project is the same record as the contact on the invoice and the vendor on the purchase order. Contact sync keeps it two-way with the phone in your pocket, so the person you just met on site is in the system before you're back at your desk.
One record — M. Chen — reached from all three.
Your assets don't move. Janus tags them where they already sit — Drive, SharePoint, S3, a vendor portal, a physical location — and associates each one with the work item that produced it, the contract that paid for it, and the people who own it. The library is the index, not another place to upload things twice.
Tagged where they already sit. Nothing re-uploaded.
Connected by designConnect the tools you already run through Iris, our library of self-serve connectors.
Explore integrations →Janus isn't bound to a platform. What we implement is the model, so it runs wherever your team can actually operate it. Where we've deployed it so far:
Scope, sprints and retainer burn in one view.
RFIs, submittals and change orders against the field record.
Titles, options and notes across every stage of development.
Calendars, approvals and deliverables per channel.