Workflow & technology assessment
Walk through the way your team works, identify the friction, and turn a vague technology problem into a practical set of next steps.
A useful starting pointA clear picture of the gaps and what to tackle first.
Public safety technology & systems integration
Your systems should support the way your department operates. I help public safety teams connect their tools, close workflow gaps, and turn everyday frustrations into practical solutions.
Work directly with Eric DiRosario.
Fire service experience. A practical approach to technology.
Software · forms · operational information
Find the gaps. Work out the right solution.
Information people can put to use.
Fire departments / Public safety teams / Municipal operations
A familiar problem
You already have systems. The trouble starts when they don’t talk to each other, a process doesn’t fit, or useful information takes too much work to find.
That’s where I come in: understanding what your team actually needs, then finding a sensible way to get there.
Entering the same information twice.
Working around a system instead of with it.
Knowing there’s a better way, but not where to start.
How I can help
Start with what needs to work better.
The scope follows the need.
Walk through the way your team works, identify the friction, and turn a vague technology problem into a practical set of next steps.
A useful starting pointA clear picture of the gaps and what to tackle first.
Explore how the tools you already use can share information and support a more consistent workflow, within the access and capabilities your vendors provide.
Make the connectionsLess repeated work. More useful information.
When an existing tool can’t fill a real gap, build something with a clear purpose. Keep the work manageable, understandable, and grounded in daily use.
Build what’s missingA tool that fits a specific operational need.
Translate operational needs into useful questions, review proposals, and help check whether an implementation does what your team needs it to do.
A practical perspectiveSupport on your side of the conversation.
The approach
You don’t need to arrive with a technical specification. Start with the part of the day that’s harder than it should be.
What happens now? Who uses the information? Where does the process slow down or break?
Identify a manageable scope, the limits of the existing systems, and what success would look like before committing to a build.
Work through the solution, test it against the actual workflow, and make the next steps and ongoing responsibilities clear.

The person behind the work
I came to technology through hands-on work in media, websites, and fire service operations.
Working in the fire service meant seeing the gap between what software offered and what people needed in the field. Finding a way across that gap became a recurring part of my work.
My approach is built on research, persistence, and understanding the process before choosing the tool. I’m interested in what makes the work clearer and more manageable for the people doing it.
That’s the perspective I bring to your project.
Before we talk
Not necessarily. The first step is understanding what your current tools can do, where their limits are, and whether a better connection or a change in process could solve the problem.
That can be part of the work. Integration depends on the documentation, permissions, and access each vendor makes available. Those constraints need to be understood before promising a solution.
That’s a good reason to start with an assessment. You can describe the problem in your own words; we can work out whether there is a practical next step and what it would involve.
Let’s talk
Tell me what isn’t working, what you’re using, and what would make the day easier. We can start with one workflow.
Please keep your first message general. Don’t include passwords, access codes, sensitive incident details, or confidential documents.