Catch the lead
Voice intake, forms, missed-call capture, follow-up notes, CRM handoff.
The Machine Layer
Threshold builds small custom AI systems for the places business work leaks: calls, paperwork, jobs, handoffs, and living demos.
Voice intake, forms, missed-call capture, follow-up notes, CRM handoff.
Invoices, receipts, PDFs, photos, extracted fields, review queues, exports.
Crew closeout, tickets, schedules, payroll review, manager dashboards.
Living sites, product demos, interactive explainers, branded portals.
One messy handoff. One useful system.
Bring one messy handoffLiving Sites / Small Demo
The video lives inside the experience now. Wake it when you want to see the doorway move.
Paid field-operations software for crew closeout, job tracking, manager review, and invoice-ready handoff.
Built around a real field-to-office workflow.
A live intake prototype that captures service details and turns a call into structured follow-up notes.
An AI invoice extraction demo that turns uploaded receipts and invoices into reviewable accounting fields.
A mechanics-focused living site and product surface for turning car issues into a guided triage flow.
A simple property-management proof of concept for voice intake, manager review, vendor routing, and portfolio context.
An interactive character experiment exploring puppet-style web presence, performance, and agent personality.
Open Puppet LabA state-based character scene where the subject reacts to pointer movement, built as a living interface study.
Open Alien PointerA small browser game prototype with pixel-world art direction, dialogue, HUD state, inventory goals, and keyboard controls.
Play prototypeA small tarot/lore interface from the character lab: playful, strange, and useful as a taste marker.
Open ArcanaThe Build Path
Bring one messy handoff. Threshold maps the inputs, builds the working system, and leaves you with a system your business can actually use.
A call script, inbox, spreadsheet, invoice pile, job board, or repeated manual task.
Inputs, rules, edge cases, people, tools, and handoffs. Review points before automation.
A testable version first: real screens, real flow, real enough data to judge.
Deploy it, document it, support it, or expand once the first machine earns its keep.
Every build should produce something you can touch: a map, a working system, and a next move.
Show me the handoffAccountability
Strange on purpose. Plain where it matters: one workflow, clear boundaries, human review, testable work.