For the work that keeps the place running.

We build the processes that keep your organization moving. The forms, the routing, the approvals, the signatures, the follow-up, and the record. We build them around how your office already works, take them off your hands, and keep them moving.

Book a conversationAbout 30 minutes
Zero
Platforms for your staff to learn
One
Process is all it takes to get started
50+
Processes running at a single organization
In the building right now
Submissions on file
This week, partial
Ref2214
ProcessRequisition
Started byA teacher, high school
HandledTue 1:12 PM
StatusOrdered
Ref5498
ProcessChange of mailing address
Started byA resident, from home
HandledTue 9:04 AM
StatusOn file
Ref318
ProcessPersonnel action
Started byHuman resources
HandledMon 3:20 PM
StatusTo payroll
Ref2194
ProcessMaintenance request
Started byA head custodian
HandledMon 6:55 AM
StatusIn the shop
Ref2188
ProcessBus conduct report
Started byA driver, from the yard
HandledFri 4:07 PM
StatusAnswered
Five processes, five desks, one week. Nobody walked any of it anywhere.
01 · The condition

Every process has someone carrying it.

Somewhere in your organization, a person owns each of these: tracking it down, sending the reminder, walking it to the next desk, knowing which stack it lives in.

01The request that needs three approvals.
02The form waiting on someone's signature.
03The record someone will ask for in two years.

Going digital was supposed to end that. Mostly it just changed what was being carried.

02 · Two kinds of work

The work that moves the mission. And the work that keeps the lights on.

We handle the second so you can stay on the first.

Education

Nobody joins a district for the second kind. But the personnel files, purchase approvals, consent forms, and compliance paperwork still have to be carried by someone. We work with districts and the organizations that serve them, from the business office to special education.

Government

The second kind of work crosses departments that each keep their own systems and their own ways of doing things, and someone has to walk it between them. We build the routing that gets it approved, signed, and on record.

03 · How it gets built

Tell us how it works. We take it from there.

01
Talk it through with us.
Most processes don't live in a document. They live in the people who run them. So we start with a conversation: who touches it, who signs it, where it stalls, what you wish it did instead. You don't need it mapped or written down. Nobody does. Drawing it out is part of our job.
02
We build it with the people it touches.
Everyone whose name is on a step gets a say before anything goes live. The rethinking, the translating, the testing: that work happens on our side of the table. Your systems stay. You never configure the software. By the time your process launches, it already works the way your organization does, because it was built from it.
03
Your people just fill it out.
Nobody learns a platform. The person who starts it sees a form with a few clear fields and a submit button. The routing, the reminders, the signatures, the record: all of it happens on its own. They hit submit, and everything after moves without them.
04
And we stay.
Nothing like a typical software rollout. No IT project, no six-month timeline. We build it together around your process, and we stay on to make changes whenever you need them. When your process changes, tell us. The same team that built it is the team that answers.
04 · Tomorrow

It starts with one process.

One process · Tuesday
Carried by: nobody
8:02aThe form goes out
8:02aThe approvals route themselves
8:41aThe files come in attached to it
9:26aThe reminders send without anyone remembering them
11:30aThe signatures are gathered from whoever has to give them
1:12pThe record files where it belongs
All weekAnd the person who used to carry all of that just doesn't anymore
One process. Then the next one, when you are ready.

All of this, and all anyone does is fill out a form.

That's what it looks like when the work is moving and nobody is doing the carrying.

05 · In their own words

“Before Flow Forms, we struggled with the approval process—making sure the right people were involved, keeping track of steps, and constantly having to explain processes to new staff members. Now, that stress is gone.”

Stephen Schreibeis, Superintendent
Glendive Public Schools

“Flow Forms is seamless and transparent. Moving from one OPI department to the next to task completion now takes a fraction of the time. Open a window and you can clearly see where your project is in the queue to completion.”

Annette Young, CSPD Specialist
Montana Office of Public Instruction

“It is, by far, one of the most useful and beneficial investments the district has made to date.”

Tamra Covington, Director of Student Services
Billings Public Schools
From the register
What runs there
Glendive Public Schools
Every department. 12+ processes on file
Billings Public Schools
IEP parent signatures, two weeks to 48 hours
Belgrade Public Schools
HR paperwork, 75% less processing time in month one
Montana Office of Public Instruction
Agency procurement, department to department
Montgomery County, Kansas
Appraiser to Clerk to Treasurer, nine forms
City of Apopka, Florida
Personnel actions, 10 to 12 days down to about two
Columbia Falls Public Schools
Bus conduct, mechanic shop, building maintenance
Gallatin County Superintendent of Schools
Homeschool registration and educator licensure

Bring us the first one.

Come with the process that's costing you the most. We'll talk it through together and show you how it could work in your office. No slide deck. No generic walkthrough.

Book a conversationBuilt around your process. We do the setup.▊
06 · Where to next

Not ready for a conversation yet?

Here is where to go.

I work for a school district.

Every desk has its own page: the business office, special education, HR, transportation, facilities, student services. The processes that land there, and what they look like once they are running.

I work for a city, a county, or an agency.

The work crosses departments that each keep their own systems, and somebody walks it between them. That has its own page.

I want to understand how you build it before I talk to anybody.

The whole method, start to finish: the conversation, the build, what your people see, and what happens when the process changes.

I need something I can bring to my team.

Write-ups on the processes other districts and offices run, and what changed once they did.

I want to know who you are first.

A small team in Montana that has been building this work since 2019, and the people who answer when you call.

Still have a question?
hello@flowforms.io
A real person reads it