You receive
- A map of the selected workflow and failure points
- A working AI-assisted tool or automation
- Human-review and exception safeguards
- Testing with representative examples
- A concise operating and handoff guide
Two founding design-partner openings
Turn one repetitive workflow into working software in ten business days.
I am selecting two companies for a tightly scoped AI operations sprint. The first engagements are free or substantially discounted because I am building a public portfolio. You get a real implementation, not an AI strategy deck.
No software subscription. No obligation to continue after the sprint.
Operator-led, builder-executed
Built around the work your team already does.
I am Brandon Henes. My background spans high-volume operations leadership, financial technology, process improvement, and building software through automation. I focus on practical systems that support human decisions instead of replacing accountability.
The engagement
A bounded build with a clear exchange.
The scope stays intentionally small so both sides can tell whether the work is useful.
I need from you
- One accountable workflow owner
- Three focused working sessions
- Representative, appropriately handled sample data
- Fast feedback during the ten-day sprint
- Permission to document the outcome, anonymized if needed
Project selection
The best first workflow is repetitive, visible, and owned.
Customer and request intake
Classifying, routing, preparing, and tracking incoming work.
Documents and records
Extracting information, checking completeness, and preparing review.
Operational follow-through
Finding stalled work, preparing follow-ups, and surfacing exceptions.
Reporting and visibility
Combining recurring inputs into a decision-ready operating view.
Not a fit for the first sprint
High-risk automated decisions, undefined "show us AI" requests, or projects that require replacing a core operating system.
Evidence of execution
Real systems, without invented client results.
These are working products and internal systems. The design-partner program exists to add measured client outcomes.
AI Client Engine
Evidence-backed business-development operations
A durable workflow for prospect research, contact provenance, suppression, message approval, and reply handoff.
- Persistent relational data
- Exact-message approval
- Global opt-out protection
TeamLens
Workflow software for real-estate teams
A product-building project focused on turning fragmented team activity into a usable operational system.
- Operational workflow design
- Structured team data
- Decision-focused interface
Automation portfolio
Reliable systems across real workflows
Production work spanning scheduled intelligence briefs, data pipelines, family applications, and decision-support tools.
- Production deployment
- Monitoring and recovery
- Human-centered safeguards
Straight answers
Why the first engagement costs less.
Why waive the fee?
I am exchanging professional fees for access, feedback, and permission to document a real outcome. I will not pretend an internal build is a client case study.
Who pays for software?
You cover any approved third-party software or usage costs. I will identify them before anything is connected.
What happens afterward?
You receive the sprint handoff. If there is a worthwhile expansion, I will scope it separately. There is no obligation to continue.
Can the case study be private?
Sensitive business information stays private. The public version can anonymize the company, data, and implementation details.
Start with the workflow