Accelerate
Launch prepares the model. Accelerate prepares and manages the drawing set — disciplines, view variants, levels, scope boxes, templates, naming, sheets, and viewport placement, previewed in full before a single view is created.
What it does
Your drawing standard, expressed once and applied as a batch.
Disciplines & view variants
Architecture, Structural, Electrical, Mechanical, Plumbing, Coordination — each with its own variants: floor plans, RCPs, power plans, lighting, framing, roof. Structural can take a roof plan while Architecture skips it.
Preview before anything is created
The full proposed drawing set, as a matrix: discipline, variant, level, scope box, template, scale, proposed name, target sheet. Deselect any single row without disturbing the rest.
Scope-box subviews
Parent views per level plus dependent or independent subviews per scope box, with explicit identifiers — A, B, C. Each variant chooses parent only, subviews only, both, or no expansion.
Token-based naming
{PREFIX}{DISCIPLINE}-{VARIANT}-{LEVEL}{SUBVIEW}{SUFFIX}, editable at every level of the hierarchy. Live preview, with duplicates and invalid characters caught before execution.
Sheets & nine-point placement
Sheets from your title block with patterned numbers and names, and viewports positioned by nine anchors with inward offsets — or a defined usable region, with warnings when a viewport falls outside it.
Drawing Plan compliance
Save the configuration as a Drawing Plan, then re-open it later to find what's missing, misnamed, on the wrong template or scale, or placed incorrectly — and fix only those.
How it works
Configure, preview, validate, execute. The model is untouched until the last step.
-
1
Select levels & scope boxes
Pick the project levels and any scope boxes to expand into subviews, each with an editable identifier. Include a roof for one discipline and exclude it from another.
-
2
Add disciplines & variants
Add each discipline, then its view variants — templates, scales, naming tokens, and subview behaviour. Settings cascade down unless a child overrides them.
-
3
Review the preview matrix
Every proposed view and sheet, grouped discipline → variant → level → subview, with tri-state selection. Edit globally, per discipline, per variant, per level, or on a single row.
-
4
Configure sheets & placement
Title block, sheet number and name patterns, viewport type, anchor, and offsets. Sheets can be created without placing a view, or views placed onto existing sheets.
-
5
Validate
Duplicate names, existing-view conflicts, duplicate sheet numbers, missing templates, template-controlled scales, and out-of-region viewports are surfaced with a resolution for each — reuse, rename, increment, skip, or deselect.
-
6
Execute & report
The batch runs in transaction groups with deterministic rollback, then reports what was created, reused, skipped, and failed.
Compatibility
What runs, what's required, what's tested.
Security & licensing
The bits IT wants to see before they sign off.
Nothing changes until you execute
Configuration and preview generation are entirely separate from model execution. No transaction opens until you press Execute, and the batch runs in transaction groups with deterministic rollback.
Offline license validation
Licenses are JSON files signed with an Ed25519 private key held in Azure Key Vault. The add-in validates against an embedded public key with no network call.
No telemetry, no analytics
We do not collect usage data from inside the product. No phone-home, no kill-switch, no mandatory cloud check-in.
Per-firm, per-Revit-year
One organization license covers every seat at the company for one Revit year. Add a year as your firm adopts it.
Nothing is replaced silently
Existing content is reused, skipped, or renamed on your instruction — never destructively replaced. Configurations are versioned and validated before they load.
Signed installers, SAS-gated downloads
MSI installers are Authenticode-signed. Download URLs are short-lived Azure Blob SAS tokens scoped to your active license.
Pricing
Organization-wide licensing. The tier sets capability — Accelerate creates one view per sheet, Accelerate Pro adds multi-view sheets, placement regions, and bulk compliance corrections; the bundle sets how many Revit versions it covers.
Accelerate
Most popularPreviewed batch creation of views and sheets from your drawing standards — one view per sheet.
Accelerate Pro
Everything in Accelerate plus multiple views per sheet, reusable placement regions, schedules and legends, and the compliance dashboard with bulk corrections.
‡Central standards distribution ships with the Keystone integration; see the roadmap on the product page.
Version bundles
Buy multiple Revit versions together — each is still its own per-firm, lifetime license file.
Additional services
30-day money-back guarantee.
Buy the full license and use it on a real project. If it's not for you, email us within 30 days for a refund — no trials, no license to expire.
FAQ
How is this different from Launch?
Launch prepares the model — profiles, templates, worksets, browser organization, and project information at day one. Accelerate prepares and manages the drawing set — the views, sheets, and viewport placement that come afterwards. They share the same standards thinking and most firms run both, but neither requires the other.
What's the difference between Accelerate and Accelerate Pro?
Accelerate ($1,000) covers the full create-and-manage workflow with one view per sheet. Accelerate Pro ($2,500) adds multiple views per sheet, reusable placement regions and viewport types, schedules and legends, the graphical sheet-region editor, and bulk corrections from the compliance report.
Will it overwrite views we already have?
No. Existing content is never destructively replaced. When a proposed view collides with an existing one, you choose per row: reuse the existing view, rename the proposed one, append an increment, skip it, or cancel the batch. Nothing is created until validation passes.
What happens if a view template controls the scale?
Accelerate detects template-controlled parameters and shows the effective value in the preview rather than a value it cannot apply. You can accept it or pick a different template.
Can we share a configuration between projects?
Yes. Disciplines, variants, naming, sheet, and placement settings save as presets, and a whole Drawing Plan exports as a versioned JSON file. On import, missing Revit resources — view types, templates, title blocks, viewport types — are mapped rather than silently dropped. Central distribution through Keystone is on the roadmap.
Can we deploy it via Intune / GPO?
Yes. Ships as a standard signed MSI plus a .addin manifest. Drop the license file in %ProgramData%\Autodesk\Revit\Addins or push via your existing channel.