Pisgah Forest, NC
I consult selectively, run a market garden that supplies fresh produce to my community and brings me into local schools to deliver talks on the intersection of tech, sustainability, and agriculture, and am building a life skills course with my bestie — all at once, all on AI systems I designed and built myself. My edge is operational leverage that actually ships.
scroll to explore
About
I'm a consultant, farmer, and builder based in the Blue Ridge Mountains of Western North Carolina. I advise financial firms on AI governance and technology adoption, run a microgreens operation, and am building an online life skills course for the next generation — all at the same time.
My relationship with AI isn't theoretical. I've built the systems I run my work on — from the assistant that writes my daily brief to the automation layer that keeps three businesses moving without three times the overhead.
What drives me: the gap between what AI can do and what most people are actually using it for. I'm interested in closing that gap — starting with my own work, and eventually helping others do the same.
Consulting
Technology Advisory
AI governance and technology platform advisory for financial services firms. Architecture, compliance guidance, and workflow automation.
Operations
Schuelace Farms
Microgreens production in Pisgah Forest, NC. From seed to delivery — and AI-automated from the first harvest weight to the weekly sales report.
Education
Own Your Life
Life skills course for teenagers and young adults. Building the practical knowledge schools don't teach — finances, health, communication, decision-making.
Methodology
I don't touch tooling until I understand the problem. Every engagement, every build, every recommendation follows the same sequence — and I won't skip steps.
01 — DIAGNOSE
Map the actual workflow before proposing a solution. Identify where the friction is, where decisions stall, and what "solved" looks like in measurable terms. Most problems that look like technology gaps are process gaps in disguise.
02 — DESIGN
Architecture before code. Define the data model, integration points, failure modes, and success criteria before writing a single line. A system built on a clear design is one that can be maintained, explained, and handed off.
03 — DELIVER
Ship when it's right — not when it's fast. Real-world validation, monitored rollout, and iteration from live data. A working system on real inputs beats a polished spec that's never been tested against reality.
This is non-negotiable. Skipping diagnosis produces solutions to the wrong problem. Skipping design produces systems that work once and break under change. Skipping validation produces confidence without evidence. All three, every time.
Selected Builds
These aren't demos or side projects. They're production tools running on real data, solving real operational problems across my businesses.
A full AI operating layer across three businesses — consulting, farm, and course — delivered through a single Slack interface backed by Claude, Notion, SQL, and n8n. If you turned it off tomorrow, I'd immediately feel like I was working with one hand tied behind my back.
What it does
What I built
A conversational interface for Schuelace Farms that queries Notion and SQL in natural language — growth metrics, sales, upcoming tasks, inventory — and writes back to both systems.
What it does
A dictation-first app for logging harvest weights, planting dates, and packaging details by variety, size, and market — generating packaged-vs-sold reporting and weekly AI-assisted social media planning without manual tracking.
What it does
A fully automated overnight intelligence system for a financial services client. Monitors regulatory filings, industry publications, and competitive signals across three lanes — classifies each by tier, routes T1s as immediate Slack alerts, and archives everything to a structured Notion database. Zero manual monitoring. Nothing slips through.
n8n workflow architecture
Notion backend
What I built
Experience
Consultant
Independent
AI governance and technology advisory for regulated financial services clients. Architecture, compliance guidance, and workflow automation.
Senior Director, Solutions Engineering
Visory (formerly Swizznet)
Built and led a 5-person pre-sales function from scratch; standardized discovery and technical validation frameworks across enterprise deals, improving win rates by 30%.
Director, Product & Solutioning
Visory (formerly Swizznet)
Led cross-functional product and commercial strategy; supported the company's largest enterprise agreement at $4.2M ARR serving 600+ end customers.
Product Manager
Visory (formerly Swizznet)
Go-to-market strategy for managed services in regulated verticals; built solution frameworks that cut SE ramp time by 9 weeks across a 12-person sales org.
Senior Manager, Sales & Client Success
Visory (formerly Swizznet)
Built the client success function from the ground up; scaled a partner channel that drove 60% of new deal volume across 30 key partnerships.
Inside Sales Account Manager
Visory (formerly Swizznet)
Full-cycle sales and onboarding for SMB and mid-market accounts; built early foundations in value-based selling and translating technical capabilities for non-technical buyers.
How I think about AI
Most AI hype is about what AI could do. I'm interested in what it actually does — for a specific person, with specific data, solving a specific problem.
A system that fails silently is worse than no system. Everything I build degrades gracefully — failures are logged, fallbacks are explicit, and nothing breaks the day if a single node is down.
An insight that doesn't turn into an action is noise. Every output from my AI systems connects to a decision, a task, or a record — something that can be tracked and improved over time.
Generic AI answers are useless. The value comes from injecting the right data — your calendar, your commitments, your priorities — so the system knows what matters to you right now.
A working rough version beats a perfect spec. I build the minimum that's genuinely useful, run it on real data, and iterate from there — not the other way around.
Get in touch
I'm open to the right opportunity. If you're building a team around AI-native operations, solutions engineering, or partner success — I'd like to hear about it. Messages go straight to my Slack.
or reach me directly