How to Contact Green Mountain System Works About a Project

Updated

Green Mountain System Works (gmsw.com) invites prospective clients to start by telling them about the project. The site presents this as the entry point for a conversation rather than a formal intake form, and it pairs that invitation with a clear picture of who they work with: R&D organizations, researchers, and funded innovators facing complex mobile software challenges. The company is based in Colchester, Vermont, and states it works "everywhere." Because it reports keeping roughly five active client relationships at a time, expect a selective, conversation-first process rather than an open queue.

What to know before you reach out

The site's own framing tells you how to pitch your project. It describes the team as "not an IT shop" but "problem solvers," and it lists the areas where it specializes:

  • Field safety — apps for identifying, assessing, and mitigating hazards before work begins
  • Hardware integration — Bluetooth controllers, GPR antennas, Crestron smart home systems, OBD-II vehicle adapters, and similar wireless interfaces
  • Scientific data collection — software for researchers and labs
  • Systems that work without a manual — apps designed to fit the natural flow of a task

It also names its technical scope: mobile (iOS and Android), hardware integration, cloud and web services, and systems architecture. If your project sits outside these areas, the site gives you no reason to expect a fit.

Two signals are worth weighing before you write. First, the "~5 active client relationships at any time" figure suggests capacity is deliberately limited, so timing and fit matter. Second, the site emphasizes understanding the problem before writing code and working iteratively in close collaboration — meaning your initial message should describe the problem, not just request a quote.

How to start the conversation

The site's primary call to action is "Tell us about your project," alongside a secondary path to "See our work." The page evidence does not specify the exact form fields, email address, or phone number behind that invitation, so the reliable first step is to use the contact path on gmsw.com itself rather than guessing at an address.

A practical approach:

  1. Open gmsw.com and follow the "Tell us about your project" prompt.
  2. Describe the problem in plain terms — what the app must accomplish, who uses it, and the conditions it must work under (field, clinic, lab, no manual).
  3. Name any hardware the app must connect to, since integration is a stated specialty.
  4. State your stage — whether you are a funded innovator, researcher, or organization scoping a build — because the site positions itself for exactly those callers.
  5. Expect a conversation, not an automated quote. The site describes close, iterative collaboration from the start.

What happens after you make contact

Based on the site's description, the engagement begins with problem definition: "Before we write a line of code, we make sure we understand the problem — really understand it." From there, the stated process is collaborative and iterative, with technology choices made along the way. The company also says it selectively applies AI-assisted development, which it frames as a way for an experienced team to deliver more without cutting corners.

The site's portfolio illustrates the kind of work that results. One example is an energy hazard assessment tool for utility workers covering gravity, electrical, pressure, motion, and mechanical hazards, with GPS logging, severity calculations, and exportable reports (source: The Electric Power Research Institute, Inc., used with permission). Another is a field safety briefing app developed as a proof of concept with a task force of seven utilities, then built and piloted with a major Northeast utility. These examples are useful reference points when describing your own project.

Common sticking points

  • Assuming a standard vendor relationship. The site explicitly distances itself from being an "IT shop," so a generic request for staff augmentation or a fixed-scope bid may not land well.
  • Leading with budget or timeline before the problem. The stated process starts with deep problem understanding, so a problem-first message aligns better with how they describe their work.
  • Overlooking the capacity limit. With roughly five active relationships, a response may depend on current availability; the site offers no published turnaround time.
  • Expecting pricing on the site. The available page material contains no pricing information, so cost will presumably be part of the conversation rather than something you can look up in advance.

For a project in field safety, hardware-connected mobile apps, or research data collection, the path is straightforward: go to gmsw.com, use the project inquiry prompt, and describe the hard problem you need solved.