Bryce Givans · OperatorThe operator
AI automation and operations specialist who turns messy, manual workflows into clean, repeatable systems for real estate, legal, and creator-led teams. Known for building CRM, lead, and content pipelines that improve follow-up speed, reduce admin time, and make day-to-day execution feel lighter for the team.
More about me
Manual lead research was slow, inconsistent, hours per batch, low quality.
Built an automated scraping + enrichment pipeline (Apify, Playwright, Clay AI) that captures, enriches, and ranks leads by conversion likelihood.
Impact: lead research cut from hours to minutes, higher lead quality, repeatable template for new markets.
Legacy legal services company on paper files and ad-hoc email; CEO working six days a week; no intake, CRM, or SOPs, and cases slipped through cracks.
Interviewed the CEO, mapped the case lifecycle, designed digital intake flowing into a CRM, automated status updates, built a living SOP repository in Notion.
Impact: ~80% digital operations, workload transparency, CEO down from six days to four.
Some personal projects you can check out
A 90-second career exposure test with instant scoring, a useful next move, and a result card built to travel.
→Pixel-art browser game built into the XP desktop.
→My old website: a fully working Windows XP desktop. Only visitors between 30 and 45 could navigate it; everyone else was lost. It stays up because it's still the most creative way I've displayed my work.
→Generative soundscapes for deep work. In production.
In the studioI think the next serious wave of software runs on your own hardware. Open-weight models like Llama and Mistral already run offline on consumer GPUs through tools like Ollama and llamafile, and quantization keeps shrinking the compute bill.
Privacy. Prompts, documents, and embeddings never leave the machine. There is no third-party retention policy to audit.
Reliability. No API outage, rate limit, or model deprecation can break your workflow. Software you host keeps working.
Control. You pin the model version and the weights, so behavior does not shift under you overnight.
The local-first software essay by Ink and Switch laid out the blueprint: your data lives on your device, and sync is a feature, not a dependency. Simon Willison tracks how fast local LLMs are closing the gap. The tools I release here will run local first.