Process

Two tracks.
One way of working.

Software and film run on different clocks, so we run them as separate tracks — same team, same standard, each with its own steps. Below is exactly what happens on each one: what we do, what you get at the end of every stage, and what we need from you along the way.

Software track Production track

How we work

The rules both tracks run on.

The steps change depending on whether we are shipping a platform or a film. The way we work does not. These four habits are what a project with us feels like from the inside, whichever track you are on.

One team, start to finish

The people in your first call are the people writing the code and cutting the footage. Nothing is handed to a delivery department after the pitch, and nothing gets lost in that handover — because there is no handover.

Show, do not report

Every cycle ends with something you can open, click, or watch — a running build, a clickable prototype, a rough cut. Progress you can see beats a status update you have to take on trust.

Scope in writing, changes in the open

What is included, what is not, and what a change costs are all written down before we start. When priorities shift mid-project, we tell you what it means for time and budget before we act on it, not after.

Built to be handed over

Your code, your accounts, your footage, your project files. We document what we build and set it up in your infrastructure, so staying with us is a choice you keep making rather than a lock-in you cannot leave.

Track 01

Software development

Six steps from a first conversation to a product we keep looking after. Each one ends with something concrete in your hands — a written scope, a clickable prototype, a working build, a deployed release — so you always know what you have paid for and what is coming next.

What we build

Discovery & Requirements

What it must do, and for whom. We map the users, the workflows the product has to support, and the constraints around it — existing systems, data, deadlines, budget. The output is a written scope with priorities, an architecture sketch, and an honest estimate, so nobody is guessing what "done" means.

UI/UX Design

Flows and screens before code. We design the journeys first, then the interfaces, and put a clickable prototype in front of you while changes still cost minutes instead of days. You sign off on the real thing, not on a description of it.

Development

Built in reviewable increments. We work in short cycles, each ending in a running build on a staging environment you can open yourself. Code is reviewed before it merges, and the priority list is re-checked every cycle so the plan tracks reality.

Testing & QA

Caught here, not by your users. Automated tests cover the logic that matters, and we test by hand across the browsers, devices and edge cases your users will actually hit — slow networks, bad input, the awkward path through a form. Fixes are verified before anything moves on.

Deployment

Shipped, monitored, documented. We set up the hosting, pipelines and backups in your accounts, release behind a repeatable deploy, and turn on error and uptime monitoring. You get the handover docs and the credentials — the product is yours from day one.

Maintenance & Support

We stay after launch. Dependency and security updates, monitoring we actually watch, and an agreed response time when something breaks. As the product grows, the same team builds the next round of features on top of code they already know.

Track 02

Video & drone production

Five steps from a brief to every cut and format you need to publish. Filming, aerial work, editing, colour and sound all happen in-house, which is why the plan we agree in pre-production is the plan that reaches the screen.

See the work

Briefing & Concept

The story before the camera. We start with what the video is for — who watches it, where it runs, and what it has to make them do. From that we write the concept, the treatment and the key messages, so every later decision has something to answer to.

Pre-production

Planning, scouting, permits. Shot lists, schedule, locations, crew and kit are settled before the shoot day. For aerial work we handle the airspace checks and flight permissions as licensed operators, and we build the plan around the weather and light rather than hoping for both.

Production

Filming and aerial capture. Ground and drone footage shot the same day by the same team, with audio recorded properly on set and footage backed up in duplicate before we leave. You are welcome on set, and you see the material as it comes in.

Post-production

Editing, colour, sound. We cut a rough version for your notes first, then lock the edit before colour grading, sound mixing, graphics and subtitles. Two rounds of revisions are included, and everything happens in-house so notes turn around in days.

Delivery

Every cut and format you need. The master, plus the vertical, square and short cuts for the platforms you publish on, exported to spec with captions and thumbnails. Raw footage and project files are archived and handed over on request.

Working together

What the weeks actually look like.

Most of the worry in a project is not about the craft — it is about not knowing where things stand. Here is the rhythm we keep so that never becomes a question.

A weekly checkpoint

One short call a week, plus a written summary of what moved, what is next, and anything waiting on you. No meeting marathons, no silence between invoices.

One channel, one owner

You get a single point of contact and a shared channel — email, Slack, or whatever you already use. Questions get an answer within a working day, not a ticket number.

Fixed scope or a running retainer

Defined projects are quoted as a fixed scope with a stated price and date. Ongoing work runs as a monthly retainer with an agreed number of days. We will tell you which one fits your job.

Honest estimates, early warnings

We estimate in ranges and revise them out loud. If something is going to slip, you hear it while there is still time to decide what to do — not on the delivery date.

Getting started

How a project begins.

Both tracks open the same way. You do not need a specification, a wireframe, or a shot list to talk to us — a description of the problem is enough to get to a useful answer.

Start a project

01
You tell us what you are making
A few paragraphs, a phone call, or an existing document — whatever you have. The goal is for us to understand the problem, who it is for, and what success looks like to you.
02
We come back with a scope
Within a couple of days you get an honest read: what we would build or shoot, roughly what it costs, how long it takes, and whether we are the right studio for it at all.
03
We agree, then we start
Scope, price, timeline and payment schedule are signed off in writing. From there you are on the track above, and the first checkpoint is usually a week away.