Give your team a tool that fits.
I sit with the people doing the work, map how it actually happens, and build around it.
How I built SaddleSyncI work with teams to understand how the work actually happens, then design, build, and support the software that makes it easier.



I sit with the people doing the work, map how it actually happens, and build around it.
How I built SaddleSyncTurn repeated copying, checking, and chasing into one workflow that keeps the source and the next action visible.
The Fieldnote prototypeWork through a task your team already handles. Learn where AI helps and what still needs a person.
An AI-assisted workflowI work with barn owners to design, build, and support SaddleSync: lessons, rider onboarding, and billing in one place.
Anonymized demonstration data.
Records, exceptions, and human review in one workspace. Try it with five fictional sheets.
Independent prototype · No account · No live AI

Electrical test review backed by evidence: source reports, equipment references, and human judgment in one workspace.
A spatial production workspace connecting 3D scenes, motion graphics, media, and Preview/Program.
A business model for custom-trained decision models and the forward-deployed work to run them.
In developmentA globe-first workspace for exploring global signals and the evidence behind them. Co-developed with a technical partner.
Two Crocs spec campaigns: human art direction, AI image and video generation, and editing in code.
Independent spec work. Not commissioned by or affiliated with Crocs, Inc.
In developmentAn explorable 3D workspace connecting source cameras, annotations, and a story timeline.

Reference research, editable geometry, independent review, and creative direction in one asset workflow.

Art direction, interactive chapters, and an original animated icon system for a connected product story.
Conversations with the people doing the work become a process map, a prototype, and a pilot report.
Every step is reviewed with the team before it changes how they work.
Sheets, email, scans, and the software already in place feed one tool instead of being replaced.
Time, errors, and correction effort are checked with the team before anything is called better.

I’m Nick. I build software close to the people who use it, and I came to engineering through 12 years of broadcast creative operations, leading design and production for FOX59 and CBS4 at Nexstar in Indianapolis.
That job meant understanding the whole system behind the work. Today it shows up as SaddleSync, built with barn owners and carried through design, code, and support, and prototypes like Fieldnote and TracePoint that start from a real workflow.
Choose one recurring task, one team, and a clear definition of better. I map the process, build a focused prototype, and test it with the people who use it.
What you leave with
Steps, handoffs, tools, and exceptions.
One agreed workflow on approved sample data.
Time, errors, and corrections, checked with the team.
Operating notes, known limits, and whether to expand, revise, or stop.
Deliverables, price, timeline, data access, and software costs are agreed before building. Rollout and ongoing support are scoped separately.
Forward-deployed, solutions, and product engineering roles where customer understanding, implementation, and design judgment belong together.
Talk about a roleCustom software, workflow automation, and applied AI, from the initial problem to tools your team can use.
Find a starting point