Selected work
Systems built end to end, then run in production.
We build automation and AI infrastructure for agencies and their clients. Everything below was designed, built, deployed and maintained in-house. Nothing is outsourced. Most of it runs our own operation, which is how we know it holds up.
MultipleSystems in production
End to endDesigned, built, deployed
US hoursNative English, same-day
Live in production
Lead capture, scoring and CRM pipeline
Inbound leads sat in an inbox until somebody got to them. Response times ran into hours and some leads were never logged at all.
Form submit→
Validate→
Score→
CRM→
Auto-reply→
Team alert→
One webhook catches every submission from the site. A scoring step grades each lead on service type, budget signal and how complete the submission is, then writes it to the CRM with the score attached.
The lead gets a branded reply in under thirty seconds. The team gets an alert with the score already applied, so nobody triages from a blank slate. Duplicate protection on every write means retries never create a second record.
Workflow orchestrationRelational databaseCaching layerCRM integrationTransactional emailCustom scoring
Response time went from hours to seconds. Runs our own lead flow today.
Live in production
Client onboarding autopilot
Onboarding a new client meant the same fifteen manual steps every time. Copy the details across, write a welcome email, notify the team, remember to mark it done.
Approve→
Create record→
Welcome email→
Internal brief→
Mark done→
Approving a lead fires the whole sequence. The record moves to the client roster with every field carried across, a personalised welcome goes out, and the team gets an internal brief with the context they need for the first call.
The source row is marked complete on the way out, so the workflow is safe to re-run and nothing fires twice.
Workflow orchestrationEvent triggersTransactional emailIdempotent writes
Around three hours of manual work per client down to fifteen minutes of review.
Live in production
AI chatbot on self-hosted inference
Off-the-shelf chatbots either invent answers about your business or meter you per message at a rate that breaks the moment volume arrives.
Message→
Load knowledge→
Inference→
Parse→
Escalate?→
Reply→
A chatbot grounded in the company's own knowledge base, running on a self-hosted inference backend instead of a metered vendor endpoint. It holds conversation memory across a session, so it remembers what the visitor told it two messages ago.
It answers from real content and says so when it does not know. When a question needs a person, it flags the conversation and emails the team before it replies to the visitor.
Workflow orchestrationSelf-hosted inferencePrompt engineeringEscalation routing
Live on a production site. Grounded answers, human handoff, no per-message fee.
Live in production
Command Vault: shared knowledge base for AI agents
An AI agent is only as useful as what it can read. Most teams keep their knowledge scattered across drives, inboxes and people's heads.
Edit locally→
Version sync→
Server→
Agent reads→
Agent writes→
Back to team→
A multi-tenant knowledge base that people and agents both write to. Team members edit in a normal notes app on their own machines. Changes sync through version control to a server where the agent reads and writes the same files through a filesystem protocol layer.
The agent dashboard runs as a managed service on the box, reachable over a private network rather than the public internet. Sync runs both directions on a two minute cycle.
Version-controlled syncMulti-tenant storageAgent tool protocolPrivate mesh networkingManaged services
One source of truth that people and agents share, with 32 tools wired to it.
In build
Property management platform for a California brokerage
Property management software takes custody of rent. The money sits in a third party's account, payouts lag, and the brokerage carries the liability for funds it never actually sees.
Tenant pays→
Direct routing→
Owner account→
Ledger→
Owner report→
Rent moves straight from the tenant to the property owner. The platform routes and records every transaction but never holds a dollar, which removes an entire category of regulatory and liability exposure from the broker.
Around that sits maintenance intake with vendor assignment, state-specific compliance deadlines tracked per property, and an owner portal that reports performance against live market data. The referring agent is a first-class entity in the data model, so whoever brought the owner in stays attached to the relationship.
Typed web applicationRelational databasePayment routingCompliance trackingOwner reporting
Direct tenant-to-owner rent flow, with the platform never taking custody of funds.
Shipped
Pinnaclicks: content repurposing platform
One long video should become twenty pieces of content. Doing that by hand costs most of a working day per video.
Upload / RSS→
Transcribe→
Find moments→
Cut clips→
Write copy→
Publish queue→
A full SaaS product built end to end. Users upload a video or connect a feed. The platform transcribes it, identifies the strongest moments, cuts the clips and writes platform-specific copy for a dozen channels.
Long renders run through a background job queue so they never block the interface, and credits are metered per operation rather than per plan.
Typed web applicationBackground job queueAutomated copy generationSpeech to textCredit metering
Queue architecture, credit metering and multi-platform publishing, built in-house.
Shipped
Video processing microservice
Turning landscape video into vertical clips means either cropping blind and cutting the speaker's head off, or paying a vendor per minute of footage.
Video in→
Track speaker→
Reframe 9:16→
Detect scenes→
Burn captions→
Clips out→
A self-hosted service that tracks the speaker frame by frame and moves the crop window to follow them, with smoothing on both the tracker and the crop so the frame never jitters or snaps.
It compares frames to find natural cut points and burns styled captions from the transcript, including word-by-word highlighting. Packaged as its own container and called over HTTP from the main app.
Computer vision pipelineVideo encodingHTTP microserviceContainerised deployment
Face-tracked reframing, scene detection and five caption styles. No per-minute cost.
R&D
Qamara Intel: computer vision at the edge
Some vision work cannot leave the site. Data residency, patchy connectivity and latency all rule out shipping frames to a cloud API.
Camera feed→
Edge inference→
Geo-anchor→
AR overlay→
Detection models running locally on the customer's own hardware instead of a hosted endpoint, so footage never leaves the premises.
Includes a georeferenced augmented reality overlay that renders buried utility lines in position on a live camera feed, plus sensor selection and hardware specification for multi-sensor detection rigs.
Object detectionEdge inferenceDepth sensingGPS anchoringHardware specification
Detection, spatial anchoring and hardware specification, built in-house.
Our own venture. No external clients. Included as evidence of technical depth.
And more
This is a selection. More is in production and in build than we list here.