Free · proposed
A useful starting point for basic Chats and shared review participation. Attachment, storage and AI limits remain to be defined.
Proposed plans separate everyday collaboration from more intensive AI and BIM processing. Packaging, limits and pricing are still being validated.
No final prices or feature entitlements are announced. These are planned access roles, not currently purchasable subscriptions.
A useful starting point for basic Chats and shared review participation. Attachment, storage and AI limits remain to be defined.
For individual Revit and drawing workflows: Eli, supported setup and PDF/DXF review, with defined processing allowances.
For deeper IFC coordination and issue workflows. Advanced comparison, BCF and combined IFC export remain subject to validation.
For administration, governed access and larger shared workflows. Billing, security options and onboarding need scope confirmation.
AI inference, IFC processing, storage, attachments and support all shape a sustainable plan. Final allowances and billing terms will be published before purchase.
The preferred direction lets reviewers join conversations without requiring a full technical seat.
Model review and AI processing may carry defined usage budgets rather than an unsupported unlimited promise.
Workspace permissions and administration should match real project responsibilities.
The intended access model supports a licensed technical reviewer working with colleagues around the same project, issue and revision. No entitlements are finalized.
Development previews connect local project files, comparison findings and conversation references. Cross-office delivery and the complete issue lifecycle are planned.
The proposed Revit AI software plans distinguish collaboration from more intensive model and drawing processing. Final prices and entitlements remain under review.
Consider who needs to discuss files and revisions, who performs AI-assisted Revit review, and who needs IFC coordination workflows. The aim is one connected environment with access suited to each role, rather than separate products that lose the project context.