Example data
Reach your members with one message.
One message can be sent to all enrolled members or a selected group, with higher open and response rates than the previous approach.
Field Automations
Your business is growing. Let's help you keep up.
I'm Pat. I build software and automation that connect field crews with the office, so updates get recorded and the right people know what needs doing.
When information gets lost between the crew and the office, I'd like to help you find a practical way forward.
You have systems. Some things still depend on you.
You've put processes in place. You've bought the software. But you're still forwarding updates, checking whether someone followed through, or piecing information together to answer a simple question.
I look at how updates, photos, time records, and requests move between the field and the office, then build the connections or missing pieces that make the work easier to manage.
- A request needs an owner. It arrived, but someone still has to work out who should take it.
- An approval holds things up. Work waits until someone remembers to ask about it.
- The work is done. The record isn't. Someone has to piece together notes, photos, and messages afterward.
- Something unexpected happens. It needs a decision, but nobody knows whose.
Practical systems, built around real problems.
Some of these systems are in everyday use. Others are working demonstrations of what's possible. Each started with a specific problem.
Example data
Actual installation
Know what's happening at your remote site.
Water-level alerts repeat until someone acknowledges them. Scheduled camera images give a remote view, with a check for missing snapshots.
Example data
Carryall: keep track of what needs doing.
A working productivity system for capturing information, organizing next actions, and reviewing open work. Used daily, with a public demo to explore.
Start with the part that keeps getting stuck.
Walk me through how you handle it today: who's involved, what tools you use, and where things slow down.
We'll look at what's worth keeping and what needs to change. That might mean connecting existing tools, simplifying a handoff, or building something specific.
If there's a useful project there, we'll agree on the scope, cost, and next steps before work begins.
Think beyond the first successful run.
A useful system needs to fit the people doing the work. These are the questions I work through when designing it:
- Who takes the next step? Make responsibility clear so work doesn't wait for someone to notice.
- What needs a person's judgment? Give people the information they need to review and decide.
- What happens when something fails? Plan how problems are noticed and who follows up.
- How will it be maintained? Work out documentation, ownership, and support as part of the project.
Capture it. Put it where it belongs. Follow through.
Getting Things Done has shaped how I think about work. I build around a simple loop:
- Capture the information where work happens
- Clarify what needs to happen next
- Dispatch to the right person or tool
- Act with the information at hand
- Review progress and what's still open
Carryall is one example: a working productivity system I use daily to capture information, organize next actions, and review my work.
What's getting harder to manage?
Tell me a little about your business and where the work gets tangled. You don't need a technical brief or a fully formed solution. A few sentences is a good place to start.