Snapfast
I designed an agent that reads real posts in a creator’s circle and recommends the next one. The creator still publishes.
A daily brief tied to real posts.
AI Agents & Workflows
Prototype AI agents and automated workflows. Validate before you scale.
For teams that want a working proof of an agent or workflow before they fund a platform.
Email me
Tell me what’s broken and where you’re stuck.
What you get
A working proof, early
Stakeholders and users react to a real prototype before a full build is on the table.
An agent with a job
Goals, tools, guardrails, and handoffs are defined around a real task, so the agent behaves inside the workflow people already have.
People stay in control
States, handoffs, and controls are designed so the team understands what the system did and trusts it enough to use it.
A stack your team can run
APIs and current AI tools, chosen to fit your environment and stay maintainable after handoff.
Specs engineering can extend
When the prototype holds up, you get requirements, UX specs, and front-end your team can ship and maintain.
How it works
- 01
Pick one job
We choose a single task the agent or workflow must complete. A demo with no job is out of scope.
- 02
Design the loop
Goals, tools, guardrails, and the handoff back to a person. The human stays in control until the data says otherwise.
- 03
Build a proof
A clickable or working prototype your stakeholders and users can react to. This is the test, not the platform.
- 04
Handoff or ship
If it holds up, you get specs and front-end your team can extend. If it does not, you stop before the expensive build.
Examples of this work
Title Resource Group
I put AI on document sorting, exam codes, and boundary sketches. A step is fully automated only after 99 of 100 examiner approvals.
Already 30% of the annual cost target.
BC Tool
I prototyped the workspace people could use: upload a wave, check it, publish the results.
Four years of brand tracking, side by side.
Fit
This is for
A real workflow, one agent
You have a repetitive job, an existing team, and you want a prototype people can trust before you scale.
This is not for
ChatGPT on the homepage
Not a fit if you want a generic chatbot with no workflow, or a full platform build with no prototype in between.
FAQ
Both, when the prototype earns it. Title Resource Group went from a front-end prototype to a production tool in three weeks. Most work starts as a proof so you can stop early if it fails.
Whatever fits your environment: current LLM APIs, the tools your engineers already run, and front-end they can maintain after I leave. I will not lock you into a stack you cannot run.
Even better. I design the agent, the UX, and the handoff. Your team extends and owns it. I am not here to replace an engineering org.
Email me the job you want automated and who does it today. I will tell you if it is a two-week proof or a longer build.