Start with the workflow, not the software

October 7, 2026 · Chris Coulson

Coulson Solutions card listing the steps Capture, Route, Do the work, and Close the loop

Coulson Solutions builds custom software for companies that have outgrown a pile of spreadsheets, inboxes, and one-off tools. The first question is not which framework to use. It is how the work actually moves.

What we ask before we write code

We sit with the people who do the job and write down the path a single piece of work takes:

Where does it start?
Who touches it, and what do they decide?
Where does it stall, get retyped, or leave the building in an attachment?
What does done look like for the customer and for the team?

If that path is fuzzy, software will freeze the confusion in place. A clear path tells us what the system has to remember, what it can automate, and what still needs a person.

A small map beats a large spec

Here is the shape we sketch before a proposal:

Four steps from a request to a finished job: capture, route, do the work, close the loop

The drawing is intentionally plain. Boxes are the steps people already recognize. Arrows are the handoffs. Anything that is still a shrug becomes a question, not a feature.

More software does not fix a workflow nobody can describe.

What we build after that

Once the map is solid, the software can be ordinary on purpose:

One place to see the work in progress
The fields people were already writing down somewhere else
Reminders where the map shows a stall
A record the next person can trust

The projects on our work page started this way, whether the result was a safety board, an estimator, or a monitoring screen. The technology changed. The order of operations did not.

If you are staring at a process that only works because one person remembers it, tell us how the work moves. We will start there.