Proof · the person and the stack behind Wire AI

Full-stack engineer and AI solutions architect.
I turn complex workflows into production software — and then run it.

Wire AI is one engineer, not an agency. Everything on this site — the sites, the booking engines, the AI receptionist you can ring, the chat bubble in the corner — is designed, built, deployed and operated by me. Below: four real builds, what each one fixed, and how I work.

ReactNode.jsExpressTypeScriptPostgreSQLPHPPythonSQLite LLM orchestrationAnthropic ClaudeGroqGeminiOllama Meta Graph APIGenerative image & videoBrowser automationPipecatDeepgramCartesiaTwilioStripe
Proof · not a mockup

Real builds — from a high-street studio to a factory floor.

Four very different jobs, one point: I build the whole working system and then run it. Each one started as a problem somebody was living with.

Live now

Seoul Lashes

A Korean lash-lift studio in South Yorkshire. The owner had a booking platform taking a cut of every appointment and a client list she didn’t really own. Now she has her own site, her own booking system, and an admin screen she runs every day.

The platform tax
Fresha-style tools wanted a monthly fee and a slice of each booking. I built her own booking engine: £0 per booking, and the client list is hers.
No-shows and forgotten rebooks
A text the day before each appointment, and a friendly nudge six weeks later when the lift needs redoing. Sent automatically, from her studio’s name.
She isn’t technical
Every admin screen explains itself in plain English, with clear status. She has never needed to call me to use it.
Built with
PHP, SQLite, Twilio, Instagram API. Hand-written front end, no page builder.
100%
Custom-built
£0
Booking fees
24/7
Takes bookings
seoullashes.co.uk
Seoul Lashes
Live at seoullashes.co.uk
Seoul Lashes — live website
control room · on-prem · live floor screens
Ops Dashboard
Running on the factory floor
Factory production control room — live floor screens
In live use

Factory production control room

A manufacturer in South Yorkshire ran production off paper counts and a weekly spreadsheet nobody quite trusted. I built them a live control room, from scribbled drafts to a system the operations team now runs every shift.

Nobody knew the score until Friday
Output, downtime and rejects now show on screens on the floor, live, against target. Team leaders see a problem in the hour it happens, not the week after.
Who is actually on shift?
The agency’s roster arrived by email and was typed in by hand. Now the rota and the roll-call sit side by side: who was expected, who turned up, never merged into one number.
Messy inputs
Order books, KPI sheets and roster emails all come in different shapes. An AI layer reads them into clean records, and people check instead of retyping.
Their data, their building
It runs on the company’s own hardware. Nothing leaves site, and they can keep running it without me.
Built with
React, Node.js, PostgreSQL, Anthropic Claude.
Real-time
Live floor screens
Per-station
Status & targets
On-prem
Company owns the data
In live operation

AI content & social media pipelines

A year of building and running systems that create and publish content for social accounts without a person doing it by hand each night. Images, video, captions, scheduling, posting, and knowing when it quietly stops working.

Content by hand eats every evening
A pipeline takes a brief and delivers finished, on-brand images and video, scheduled and posted across accounts. Same look every time, no drift.
Posting silently stops
Platforms expire access, change rules, and restrict accounts without telling you. The system watches itself and tells me what broke and why, the same day.
The rules aren’t what the rules say
I’ve tested what each platform actually enforces and build to that, so accounts stay healthy instead of learning the hard way.
All on one home PC
Several AI models share one ordinary graphics card without tripping over each other. It runs overnight and is still up in the morning.
Built with
Python, Meta Graph API, several image and video engines, Claude, Groq and local models.
Render→post
Fully automated
Multi-engine
Image & video
Self-checking
Tells me when it breaks
pipeline · brief → content → publish → measure
wireai.one · this site, running itself
Live now · you are on it

Wire AI itself

This site is not a brochure. It is the product, working: an AI receptionist on a real number, a chat assistant that books, a scan tool that looks a business up and drafts a plan, and one CRM behind all of it.

“Does the receptionist actually work?”
Ring 01723 674864. Real number, real voice, and it books a real appointment. No demo video needed.
Leads scattered everywhere
Phone, chat, form and scan all land in one place with follow-up reminders, so nothing goes cold.
“What would you build for me?”
The scan tool finds a business on Google and drafts a tailored plan in seconds. It is how most conversations here start.
Built with
PHP, SQLite, Twilio, Deepgram, Cartesia, Groq, Stripe. Ordinary shared hosting.
3
Front doors, one CRM
Live
Ring it now
Owned
Not rented software
Rules learned on the floor

How I work.

Each of these cost real time before it became a rule. They are now how every system I build is designed.

Zero to one, with the users. Built next to the team leaders, salon owners and coordinators who run it, validated against their real sheets before anything is called done.
Planned and actual are two facts. A rota and a check-in, an order and an output, are never merged into one number. Show them side by side.
Validate at entry, not in an email. If a rule matters, make it a form constraint or a database check, so it cannot be broken politely.
Warn, never block. The person on the floor is never locked out by the system. It flags, records, and lets them get on.
Stable IDs, never matched on names. Every person and every order has an identifier that is never reused. Names are shown, not matched.
Pull, never push; upsert, never wipe. Integrations fetch on their own schedule and keep history. Nothing is deleted; things are marked gone.
Hold the minimum data. No reasons for absence, no biometrics, no payroll. If the system does not need it, it does not store it.
Ask what it can export before building against it. Every legacy device and spreadsheet gets looked at first; the real file is the spec.
Latest · straight from Instagram

Fresh from the studio.

This feed updates itself from my Instagram — I post once and it appears here, no double-posting. I build the exact same into your site, wired to Instagram, Facebook or TikTok.

Your business next

I build the real thing — and I'll prove it on your free audit.

📞 Call ✦ Audit