compiling shaders · 000
a design studio that ships production software, and an engineering shop that cares what it looks like. one team from brief to live url, so the thing you signed off is the thing that ships.
01 / services
eight disciplines, one thread from brief to live url. tap a line to open it.
the front end people judge you on. real-time 3d sites, glass interfaces, marketing pages and full design systems, designed to convert and built to ship. you get live responsive product in a browser, not a flat mockup somebody still has to build, and it goes out indexable to search engines and readable by the answer engines people now ask instead.
agents that do the work rather than chat about it. research, outreach, qualification, follow-up and back-office tasks running on a loop with nobody in the seat. wired into your tools, with guardrails, logging and a human gate where it matters.
software your customers can talk to. phone agents and receptionists that answer, book, take details and follow up around the clock, plugged into your calendar and crm so nothing drops while you sleep.
the saas your industry never got round to building. operating systems for clinics, trades and legal firms still running on spreadsheets and inboxes. scoped, designed and shipped end to end, from data model to billing to the screens your team opens every morning.
the plumbing that turns output into revenue. outreach engines, qa agents, monitoring and data pipelines that move work between your systems and flag what needs a person. quiet infrastructure that runs in the background and keeps running.
the unglamorous software your team opens every day and nobody sells you. internal dashboards, admin panels, custom ai tooling wired to your own data. built to your stack and handed over with the keys, so it is capability you own rather than a subscription you rent.
the look, and the thing that shows the look moving. wordmarks, palettes, type systems and the rules that stop them drifting, then the launch film and the ad cuts that come after. designed and cut here rather than briefed out to a second supplier, so the brand and the build never arrive as two different opinions.
the mail your product sends, treated as a surface instead of an afterthought. branded transactional shells, onboarding and win-back sequences, operator digests, and an inbox that actually replies. sent from your own domain with the authentication set up properly, because the best email in the world is worthless in a spam folder.
02 / the edge
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.
we do not play every instrument. we decide what stays. most of what gets made gets cut before you ever see it, and what survives the cut is why the work looks designed rather than assembled. you are not buying our options. you are buying the judgement.
every commission gets its own client portal: progress, notes and live urls you can open at 2am. some clients live in it and pick the details with us. others read it on a sunday and leave the rest alone. we agree which one you are at kickoff, and you can move it either way once we start.
deployed means live somewhere real. shipped means a person completed the whole flow end to end without anyone stepping in. a build does not leave here until it clears both, which is why it still works after the launch week adrenaline wears off.
fixed scope, fixed price, agreed in writing before anything starts. one team from first sketch to deploy, so nothing waits on a handoff and nobody bills you for a meeting. build it, ship it, move on.
03 / selected work
most client work runs under nda, so these are the shapes rather than the logos. drag to move through them.
01 / 06livereal-time interfaces shipped as product in the browser. this page is one of them.
webgl2 · glsl · zero deps
02 / 06on a callnative 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.
expo · next.js · supabase
03 / 06livemulti-tenant vertical saas for clinics and trades. bookings, billing and reporting behind one login.
next.js · postgres · stripe
04 / 06privateintake, extraction and drafting with a human gate that cannot be skipped.
workers · queues · rag
05 / 06on a callphone agents wired to real calendars and real crms, escalating when confidence drops.
elevenlabs · twilio · sip
06 / 06portfoliooutreach engines and monitoring agents that run unattended, reporting into a single console that shows what each one last did.
node · cron · webhooks
04 / the standard
everything you moved through is the live thing running in your browser, 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.
built in the open.
05 / pricing
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.
every figure fixed on scope · deposit clears before build starts
we move in days, not quarters. the clock starts when your content lands, not when you pay.
06 / questions
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. this page is another. both are built to stay fast and stay indexable, which is where most 3d sites fall over.
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 wherever it matters. the part most demos skip is the stopping rule, so ours read their own result and know when to hand back.
yes. voice agents that pick up around the clock, book people in and follow up, sitting on top of your real calendar and crm. confidence gated, so when it is unsure it passes to a person instead of guessing.
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. we set the rhythm at kickoff and it is not fixed after that. what we do need from you is content and decisions, because those are the two things that actually hold a build up.
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 rather than the way a generic tool assumes you do.
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.
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.
