How we work
We learn the work before we write the software.
Every Bloom build runs the same way, whatever the trade. We spend the first days where the work actually happens, map the decisions your team is making by hand, and only then draw a screen. The method is the whole reason the result fits.
01
Discovery
02
The map
03
Design
04
Build
05
Launch & after
The first week is mostly listening.
The method
Five phases, in this order, every time
We do not quote a number of weeks here, because the honest answer depends on your trade. What does not change is the order, and what has to be true before a phase is finished.
Discovery
We come to the floor
The first days are spent on site — in the packhouse, at the reception desk, beside whoever is keeping the spreadsheet alive. We watch the work, ask what breaks, and write down what your team calls things.
- You end up with
- A written account of how the work runs today, including the parts nobody documents.
- Finished when
- We can describe your day back to you and nobody corrects us.
The map
We draw the work as it really runs
What we saw becomes a map of decisions, handoffs, and edge cases, then we walk it through with your team and argue about it. Features come out of that map. Nothing gets built because it looked good in somebody else's demo.
- You end up with
- A workflow map and a scoped plan, including what we are deliberately leaving out.
- Finished when
- The map survives a review with the people who actually do the job.
Design
We design in your vocabulary
Screens get drawn in the language of your trade. A stem is a stem and a cold room is a cold room. Layouts are shaped for the conditions the work happens in — gloves on, one hand free, a queue forming at the desk.
- You end up with
- Clickable screens for the paths your team walks every day.
- Finished when
- Someone who does the job can find their way through without a guide.
Build
We build in the open
Short cycles, and at the end of each one you get real software to open rather than a status report to read. The people who mapped your workflow are the people writing the code, so nothing is lost handing it to a team you have never met.
- You end up with
- A working build you can open and use, every cycle.
- Finished when
- Your daily paths run end to end on your own data, not sample data.
Launch & after
We stay after go-live
We are on site for launch, training on the floor instead of in a meeting room. Then we stay: fixes, changes as the operation shifts, and the support call two years from now.
- You end up with
- A live system, trained users, and a direct line to the people who built it.
- Finished when
- It does not end. That is rather the point.
While it runs
What the weeks actually feel like
One team, start to finish
The same people from the first conversation to the support ticket two years later. Nothing is subcontracted out.
A direct line
You talk to the person building your software. There is no account manager in between relaying messages.
Software, not slideware
Every cycle ends in something you can click. Progress is demonstrated, never just reported.
Your data stays yours
It is your operation's record. You can export it whenever you want, without asking us first.
Your side of it
What we ask of you
The method only works if it goes both ways. None of this costs money. All of it costs a little attention, and it is the difference between software that fits and software that gets tolerated.
Time on the floor
A few days with the people doing the work, not only the people who own the budget.
One person who can decide
Someone able to settle a question in the same week it gets asked.
Your real data
A messy export beats a clean sample every time. The edge cases are most of the job.
The awkward truths
The workaround, the shadow spreadsheet, the step everybody quietly skips. Those shape a build more than any wish list.
Phase one starts here
Show us how the work runs today.
A conversation about your floor, your vocabulary, and the spreadsheets holding it together. That is discovery beginning, and it is where every Bloom build starts.