we build the hard part.
a design studio that ships production software, and an engineering shop that cares what it looks like. one brief in, eight disciplines, one live url out.
0 points, computed live on your graphics card.
scroll resolves it.
quick is the easy part. quick and it holds is the work.
anyone can get something on a screen in a week. the harder part is whether it still holds six months later, once the launch adrenaline wears off and it is just software your team has to live with. the design and the engineering come from the same hands here, which is why the second one does not quietly undo the first. most studios sell you a process. we sell you the finished thing.
taste is the filter
we do not play every instrument. we decide what stays. most of what gets made is cut before you see it, and what survives the cut is why the work looks designed rather than assembled.
as hands on as you want
every commission gets its own client portal: progress, notes and live urls you can open at 2am. live in it, or read it on a sunday. we agree which at kickoff and you can move either way.
shipped means finished
deployed means live somewhere real. shipped means a person completed the whole flow with nobody stepping in. nothing leaves here until it clears both.
days and weeks, not quarters
fixed scope, fixed price, agreed in writing before anything starts. nothing waits on a handoff and nobody bills you for a meeting. build it, ship it, move on.
the work, minus the logos.
most client work runs under nda, so these are the shapes rather than the logos. literally.
-
website building
real-time interfaces shipped as product in the browser. the beam at the top of this page is one of them.
livewebgl2, glsl, zero deps -
mobile and web apps
native ios and android taken through to testflight, with the web cockpit and backend that feed them. the nav is a consumer unit, because the people using it wire them.
on a callexpo, next.js, supabase -
saas and operating systems
multi-tenant vertical saas for clinics and trades. bookings, billing and reporting behind one login.
livenext.js, postgres, stripe -
legal and document tools
intake, extraction and drafting with a human gate that cannot be skipped.
privateworkers, queues, rag -
voice ai systems
phone agents wired to real calendars and real crms, escalating to a person when confidence drops.
on a callelevenlabs, twilio, sip -
oracle, the fleet console
outreach engines and monitoring agents that run unattended, reporting into one console that shows what each one last did.
portfolionode, cron, webhooks
you've been using the demo this whole time.
the beam at the top of this page is tens of thousands of points computed on your graphics card, not a video of it. this is the standard we hand over at. if a page about a studio held you this long, it will hold the people you are trying to sell to.
here is what it costs.
three tiers, whatever the discipline. two carry the number, one we price in writing. scope decides where in the range you land, and the figure is fixed before anything starts. no discovery call to find out the price of a discovery call.
£250-500
the easy way in
one page, one landing site, one agent, one automation. a single focused pass, delivered direct. no call, no onboarding, no retainer.
£700-950
full build
multi-page sites, voice agents, working software. brand direction where it needs it. you leave with something that looks like it cost five times more.
in writing
talk to us
bespoke apps, operating systems, full brand systems, anything multi-part. scoped and priced in writing before anything starts.
every figure fixed on scope. the deposit clears before the build starts, and the clock starts when your content lands, not when you pay. we move in days, not quarters.
the practical bit.
- can you build a 3d or webgl site?
- yes, it is home turf. the parametric turbofan on the demos page is a live one: no model files behind it, every blade and disc generated from numbers you can change while it runs. built to stay fast and stay indexable, which is where most 3d sites fall over.
- what is an agent, as opposed to a chatbot?
- a chatbot answers. an agent does the job. ours research, qualify, follow up and run back-office work on a loop, wired into your tools with a human gate where it matters. the part most demos skip is the stopping rule, so ours read their own result and know when to hand back.
- can you build something that answers the phone?
- yes. voice agents that pick up around the clock, book people in and follow up, sitting on your real calendar and crm. confidence gated, so when it is unsure it passes to a person instead of guessing.
- how involved do i have to be?
- as involved as you want. some clients are in the portal daily picking details with us, others send the brief and read the updates on a sunday. what we do need is content and decisions, because those are the two things that actually hold a build up.
- you have never worked in my field. is that a problem?
- usually the opposite. you bring the domain, we bring the build. the first pass is us learning your process well enough to argue with you about it, and what comes out is shaped like the way you already work.
- who owns it at the end?
- you do. code, repositories, accounts and keys are transferred on completion. nothing is licensed back to you, and nothing depends on us staying on a retainer for it to keep running.
- how much, and how long?
- fixed scope and a fixed price, set from the three tiers above. a landing site or a single agent is usually days. an app or an operating system runs from a few weeks to a few months, and you follow it in a live portal rather than waiting on a status call.
we build it. you ship it.
from brief to live url. fixed scope, fixed price, async friendly. or skip the form and book a call.