Where we work
One office, and an honest account of the distance.
Elarion is based in downtown Vancouver and works across Canada and United States. The analysis happens on site wherever we can get to you, because requirements live in how people actually work. The build runs remotely, led by the analyst who sat in the room.
Canada comes first, because that is where the office is and where being on site is ordinary. Everywhere else follows, by country. Each page says what it carries that the others do not, and how we get there.
Canada
- VancouverBritish Columbia
- The base. On-site discovery from downtown, the BC organisations in the lead analyst’s career, and BC privacy law designed into the specification.
- BurnabyMetro Vancouver
- Head offices, the Still Creek and Brentwood corridor and the Big Bend industrial lands. The provincial liquor distributor in our career history is headquartered here.
- LangleyFraser Valley
- The valley’s own business mix — agrifood, manufacturing, distribution and transport — and two separate municipalities that do not run the same way.
- VictoriaVancouver Island
- The seat of the BC public service, with two organisations from our career history headquartered here, and the coastal forest products operations up-Island.
Where else we can help
United States
- DenverColorado
- The cross-border case, without a claimed local presence: an hour of time difference, the Colorado Privacy Act, and where the data actually lives.
- San Francisco Bay AreaCalifornia
- The one US market with no time difference at all, scoped to the whole Bay Area. It carries California privacy law, including the service-provider terms this practice would itself sign.
How we decide whether to travel
- When we come to you
- Any engagement whose requirements live in a physical operation — a mill, a depot, a warehouse, a counter, a yard. Watching the work done where it is done is the only reliable way to find the workarounds nobody mentions in a meeting, and those workarounds are usually the specification.
- When we do not
- A well-defined change to a system we already understand, a code audit, or analysis of a process that happens entirely inside software. Charging you for travel that adds nothing is not a service.
- How it is priced
- Travel for discovery is agreed up front as part of the scope, so it is a line you approved rather than a surprise on an invoice.
- Who travels
- The analyst who writes your specification and leads the engineers who build it. Not an account manager, and not a junior sent to take notes.
Questions buyers ask
- How many offices do you have?
- One, in downtown Vancouver. The pages for other cities describe where we work and how we get there, not addresses we hold. Any firm listing a dozen city offices is usually listing a dozen mailboxes.
- Do you only work in these cities?
- No. These are the places we are asked about most often, so each has a page that says something specific. We work across Canada and the United States, and the engagement does not change because your city is not listed.
- Can you work with a US company from Canada?
- Yes, and we do. A Canadian operating entity contracting in English, invoicing in US dollars, on Pacific Time — which overlaps every US time zone’s working day. The Denver page goes through the cross-border detail, including where data is hosted.
- Is remote delivery worse?
- The analysis is worse remote, which is why discovery happens on site wherever we can get there. The build is not: it has been remote-first for years, and the specification is what keeps it honest either way.
- Which city page should I read?
- The one nearest you, for the local detail. If none is close, read the service or system page for the work you need — those are the same wherever you are, and the method does not change by postcode.
The work itself does not change by city
Start with a call, wherever you are.
30 minutes, free. Bring the problem, or the specification you already have.