Our team

Twenty specialists, each with one job.

Not one assistant asked to do everything. Each of these has a single responsibility, a narrow set of tools, and one thing it refuses to do — and nothing any of them produces reaches a client unchecked.

Security and verification CassandraSecurity and QA Lead Reviews work before it ships and hunts for what is actually broken — security holes, silent failures, and claims nobody tested. Tests a login with the wrong password, not the right one.
NyxOffensive Security Researcher Attacks our own systems on purpose, inside an authorised scope, so weaknesses surface here rather than in front of a client. Penetration testing, vulnerability analysis and hardening by breaking.
BeckRelease Verification Engineer The go/no-go before anything goes live. Runs the whole system end to end from every seat that matters and reports whether it is safe to ship — including whether the owner can still get in.
Engineering TessaBack-End Engineer Everything behind the page — APIs, data models, authentication, sessions, and anything crossing a trust boundary.
MasonSoftware Engineer Writes and changes the code across every project, matching the existing style and proving it loads before handing it back.
WrenFront-End Engineer Front-end and interface work: layout, styling, interaction, and how a screen actually feels to use. Renders the result and looks at it rather than trusting that it works.
VegaVisuals Engineer Generative and audio-reactive visual work — the things on a screen that move and have to mean something rather than decorate.
OttoML Infrastructure Engineer Local model infrastructure — what runs on our own hardware instead of a metered cloud API, and the sizing decisions behind that.
ArgusSite Reliability Engineer Reports the true state of the running system: what is actually up, what the logs say, and what is failing quietly. Says plainly what could not be determined.
Web and reach NadiaAccessibility Specialist Accessibility and real-device quality. Checks whether a page genuinely works for people who cannot hear it, cannot see it well, or are not using a mouse.
SloaneSearch Visibility Specialist Search visibility — whether a page can be found at all, and by whom. Site architecture, structured data, crawlability and local search.
BramPlatform and Deployment Engineer Getting work live and keeping it there: hosting, DNS, TLS, deploys, rollbacks and what happens at three in the morning.
Strategy and words JunoMarketing Strategist Positioning and strategy — who the work is for, what it competes against, and what to stop saying. Refuses to accept everyone as an audience.
MarloweRevenue and Unit Economics Revenue and unit economics: what the work is worth, what to charge, and whether a deal still makes money once the cost of delivering it is counted.
CyrusCopywriter Writes the words — sites, proposals, emails, anything a client reads. Starts only once the positioning is settled.
PriyaAnalytics Lead Measurement. Sets up tracking before a campaign and reads the results after one, without dressing up a number that means nothing.
VeraCommunications Psychologist Communications review. Checks how a message will land on the person receiving it, and cuts what does not need to be there.
Operations DellaChief of Staff Keeps the work organised — what is genuinely open, what is next, and what was promised and never started.
DeweyArchivist Keeps the written record true: indexes in sync, links unbroken, nothing duplicated or quietly superseded.
RozInbox Manager Triage and filing across the inbox — working out the small set that genuinely needs a person and handling the rest.

The one who builds a thing is never the one who checks it, and the one who checks it is rewarded for finding it broken. That separation is deliberate, and it is the part worth paying for.