For companies

Stop running a plugin estate. Start running a catalogue.

Most firms end up with automation nobody owns: scripts from a former employee, a plugin someone bought on a card, a Dynamo graph that only works in 2022. Routines turns that into something you can actually manage.

Paid plan access is arranged with the Routines team. Features marked planned are not included in current access. Each tool has its own licence and seat pool.

What changes

Plugins downloaded by whoever needed them

A reviewed catalogue with a named developer behind each tool

Twelve installers, twelve updaters, twelve licence files

One Hub that resolves the right build for each host version

Nobody knows which tools are actually used, or by whom

Personal run history today; team and project dashboards are planned

A leaver takes a licence with them

Seats held by the firm, reassigned in a click

An update breaks a live deliverable

Version-pinned rollouts and rollback are planned

Built for how firms actually operate

Central seat management

Assign and reassign purchased tool seats to active company members.

Team analytics (planned)

Personal run history is available. Team dashboards and ROI reporting are planned.

Curated catalogue

Browse a selection for company members. Enforced catalogue restrictions are planned.

Version pinning (planned)

Coordinated version pinning and rollback are not currently included.

Run history

Review your own runs and their outcomes. Organisation audit export is planned.

Private deployment (planned)

Internal-only tool distribution is not currently included.

Tool requests

Need something that doesn't exist? Ask for it.

Post the workflow you want automated. Developers on the platform respond with proposals, timelines and prices. You can commission it privately, or fund it and let it be published afterwards on terms you agree.

See the request board

How a request runs

  1. 01You describe the workflow and the software involved
  2. 02Routines reviews it for scope and feasibility
  3. 03Matching developers submit proposals
  4. 04You shortlist and pick one
  5. 05Development, testing, delivery
  6. 06Optionally published to the marketplace

Questions from BIM and IT teams