Opens in a new tab
Back
Three practices
01

Build

Websites that do a job

02

Automate

Integrations, workflows and custom builds

03

Care

Looked after, month after month

One standard across all three: accessible, fast, findable, secure.

Services

Every build lives on a plan.

A website nobody is looking after gets worse quietly: a plugin goes unpatched, a form breaks and nobody notices for a month, the one person with the passwords leaves. Managed Care is the opposite. You edit the content. We keep everything underneath it current, patched, watched, and guaranteed.

What's included

Your site gets better, not older.

Most sites get built, left alone for five years, then rebuilt. On a plan it goes the other way: kept modern, grown with the organization, and looked after by people who know you.

It stays modern

Sites don't break all at once. They fall behind. An old server version, a plugin nobody touched, a standard that moved. We keep the software, the server, and the accessibility and privacy rules moving forward, so the site you launched doesn't quietly age.

It grows with you

New needs get built on, not rebuilt. When the organization needs something new, like registration, a member area or a link to a tool you already run, it's built onto the site you have by the team that already runs it. Small changes are included. Bigger work is scoped and quoted first, with no vendor search and no starting over.

A partner, not a vendor

The same people, every month. They know your organization, not just your site. We stay accountable for the site after launch, and we plan it around where the organization is going, not around a support ticket.

Plans

Same infrastructure underneath. What changes is human attention.

Every plan runs on the same infrastructure. What changes is how much of our attention the site gets each month. The numbers come on the call, once we know what the site has to do.

  • Starter

    Hands off. Always on.

    Your site doesn't change much. We keep it safe, fast and up to date, and you don't have to think about it.

    Contact us
  • Professional

    Priority response. Proactive work.

    Your site is how you work. We're on it every day, nothing waits, and we help you plan what comes next.

    Contact us
How it runs

What working together looks like.

You see every step before we build it. Most workflow projects take [four to eight] weeks from approved brief to live; bigger integrations take longer, and we say so in the brief.

  • Understand, properly

    Before anything is built we sit with the people who do the work and map how it happens today: every step, every hand-off, every place it breaks. That becomes a short written map and a brief you approve, and it is where we tell you whether the fix is worth building.

  • Design the step, not the software

    We agree on what the new process is before we agree on a screen: who starts it, what they see, what happens automatically, who gets told, where the record lives. Most of the design is deciding what a person should never have to do again.

  • Build and connect

    Custom tools where nothing off the shelf fits, connections to the systems you already use where they do. Everything on a platform we run, so it is looked after under Care afterwards.

  • Test with the people who use it

    Your team runs the real process on the new tool before it goes live, with us watching. What confuses them gets changed. Then it goes live, and the old spreadsheet gets retired on purpose, not forgotten.

  • Care

    A workflow that runs the organization needs someone on call. Every build is looked after under Managed Care: monitored, kept current, and improved when your process changes.

Why Choose Us

Built for the long run.

We aren't here for one launch. We work with organizations for years, and we measure the work by how far the site and the organization have come, not by the day it went live.

  • In it for years, not a project

    Plans are month to month, but we plan in years: what the site needs this season, next year, and when the organization changes.

  • Your goals set the plan

    We start with where the organization is going, more members, fewer phone calls, less admin, and work back to what the site should do about it.

  • One team for all of it

    Hosting, the site, and anything built on it come from the same people. When something breaks, nobody points at another vendor.

  • Straight answers

    You hear what something costs before we start, and when you don't need something, we say so. Questions never cost anything.

What it is like to work with us.

In their words

[A quote from a client in this segment, about the audit, the board, or updating the site themselves. Remove this section until there is one.]

[Name]

[Role, organization]
@media (min-width:767px){
  .bm-testimonial-38__top {
    grid-template-columns: var(--grid-3-2) ;
  }
  
  .bm-testimonial-38-review {
    order:-1;
  }
  
}
Questions

Questions people ask before they call.

Plain answers to what comes up before a first call.

No. If your site is fine, we start here. The tools live on your site or alongside it, and we look after them either way.

Often, yes. Understanding the process first tells us whether the fix is a connection, a setting, or something built. We tell you which before you spend anything.

It stays yours, on systems you own or we run for you. Nothing of yours is used to train anything.

Under Managed Care, changing the workflow is part of the monthly improvement, not a new project.

Scoped from the brief, with a fixed price before we build. The brief itself is [included in the discussion / a fixed fee].

Get started

Tell us about your project.

We're excited to work with you.

GMNI's AI Policy

Learn about how we use AI at GMNI

Learn More