How a project runs, from first call to handover.
Our process in plain terms: what happens at each stage, what you do, and what you get.
It starts with a conversation.
Tell us what you're building and we'll tell you plainly whether we're the right studio for it. If we are, we scope the work with you and agree a fixed price before we start.
Discovery.
We learn who your users are, what they need to do, and what the work has to achieve for your business.
Structure.
We map the structure around those tasks: the sitemap and pages for a website, the flows and screens for a product. We plan the content each part needs.
Design.
We design the key pages, screens and templates in Figma, then refine them with your feedback.
Build.
The same team that designed it builds it, in Webflow, Framer, WordPress, or custom code, chosen to fit how your team will edit it. Nothing gets lost between design and build.
Launch and handover.
We test across devices, set up redirects and metadata, launch, and hand over documentation so your team can run it.
Changes along the way.
Things change mid-project.
More detail, soon.
We're still documenting the specifics behind this process - feedback rounds, support periods, how a change request is raised and who your main contact is. Thank you for reading closely enough to notice. We'd rather publish that properly than fill the gap with placeholder copy, so it's coming as soon as it's ready.