Skip to main content
About Flow Forms

We didn't find this problem
from the outside.

Flow Forms was started by people who were already in the building, doing the work, feeling the friction, and deciding there had to be a better way.

Trusted by
MT Office of Public Instruction · Billings Public Schools · Columbia Falls Schools · Gallatin County · BOCES 5 · Oklahoma Wesleyan University · Hardin Public Schools · Zoo Montana · City of Apopka · Sheridan County SD #2 · Weston County SD #7 · MT Office of Public Instruction · Billings Public Schools · Columbia Falls Schools · Gallatin County · BOCES 5 · Oklahoma Wesleyan University · Hardin Public Schools · Zoo Montana · City of Apopka · Sheridan County SD #2 · Weston County SD #7
The founders

The people behind
the platform.

Terry

Terry

Co-Founder

Spent years inside Billings Public Schools building and managing the exact processes Flow Forms now automates. That background shapes every solution, not from a product roadmap, but from having been the person absorbing the friction.

Andrew

Andrew

Co-Founder

Computer science background from Rocky Mountain College, where he taught before turning that expertise toward building Flow Forms' platform and infrastructure. Focused on making complex workflows simple to use.

How it started

Two people who knew this problem from the inside.

Terry was working inside Billings Public Schools, building and managing the same kinds of processes Flow Forms now automates: routing requests, tracking approvals, collecting signatures across departments. He knew exactly where the friction was, because he was the one absorbing it.

Andy was teaching computer science at Rocky Mountain College, where he'd spent years thinking about systems, workflows, and how software should be built to serve real people rather than the other way around.

When they compared notes, the path forward was clear. Not a startup bet on a market opportunity, just two people who decided the problem they both understood deserved a proper solution.

How it grew

One process became two. Two became ten.

Schools and agencies started asking about workflows we hadn’t built yet. We built those too. The platform expanded because the problems kept coming, brought to us by the people living them.

Where we are now

Education, government, and business organizations.

From individual school districts to state agencies to universities, the common thread is organizations running important processes on paper, email, and good intentions.

What hasn’t changed

We still build every solution ourselves.

No templates handed off to a client portal. Every workflow is built by the same team that will support it after launch.

How we work

Small team.
Direct involvement.

Flow Forms is a team of six. When you work with us, you're not handed off to an account manager or a support queue.

01

We learn your process first

Before anything gets built, we spend time understanding how your process actually works — not how the form says it should work, but how it really moves through your organization.

02

We build it for you

You don't configure a template. We build your workflow — routing logic, approvals, notifications, signatures, filing — to match your process exactly.

03

We stay involved after launch

The people who built your process are the same people available when something changes or you're ready to build the next one.

Supported by a small team of builders and implementers who work directly on every account.

No offshore contractors. No generic support tickets. The same people who build your workflow are the ones who know it.

Let's talk

Have a process you want to talk through?

We're easy to reach and genuinely enjoy these conversations. Bring us a messy process, that's exactly what we're here for.

No sales pitch. Just a conversation about what you're working with.