Skip to content

EMI3News & insightPartners

Deploying a new site in 48 hours

The target that shapes how the platform is built: a certified partner standing up a new site without EMI on the ground.

Partners5 min read

A new site, configured rather than built
A new site, configured rather than built

Most enterprise software targets are about features. This one is about independence: any certified partner should be able to deploy at a new site within 48 hours, without EMI present.

It sounds like an operations goal. It is really a product constraint, and it rules things out.

What has to be true

  • Configuration, not customisation. If a new site needs code, 48 hours is impossible. Every industry and client is served through configuration and templates.
  • A real model library. Most common machines are already modelled, so a deployment starts from an existing model rather than a blank page.
  • Certification that means something. A partner certified against a real deployment, not a classroom, can be trusted to run one alone.
  • No bespoke forks. The moment one client runs different code, nobody can deploy anybody quickly again.

One execution model. Replicated under discipline.

The discipline costs something. It means occasionally declining work that would require a fork, and holding the line when a large client asks for one. What it buys is a platform where the hundredth site is no harder than the tenth.

Was this useful?

We read every response. It decides what we write next.