Services.
01 / Python · Julia · Rust
Scientific computing consulting.
Advice and hands-on help with numerical models, inference and research code.
Good for: Research groups, labs and science-led companies with a modelling problem, a slow analysis, or code that has outgrown a folder of scripts.
Typical work
- Choosing, implementing and validating numerical methods for a model.
- Bayesian inference, inversion, data assimilation and uncertainty quantification.
- Reviewing research code for correctness, reproducibility and speed.
- Turning notebooks and scripts into documented, reproducible tools.
- Speeding up slow analysis with Julia or Rust.
Examples
02 / Astro · TypeScript · Cloudflare
Websites for organisations.
Fast, low-maintenance websites for societies, productions and small organisations.
Good for: Groups that need a site volunteers can keep running: societies, charities, events and small businesses.
Typical work
- Static sites that are quick to load and cheap to host.
- Moving an existing site off WordPress.
- Event pages with ticket booking links and programme information.
- Pulling content in from data you already keep elsewhere.
Examples
03 / Swift · SwiftUI
Apps for iPhone, iPad and Mac.
Native SwiftUI apps that feel at home on Apple platforms.
Good for: Organisations that want a companion app, and ideas that need a working prototype to test.
Typical work
- Native apps for iOS, iPadOS and macOS from one SwiftUI codebase.
- Apps built on public APIs, with offline caching.
- Prototypes for testing an idea before committing to it.
- Privacy policies and support pages that match what the app actually does.
04 / Rust · Python · Shell
Developer tools and automation.
Small, sharp tools that save a team time every day.
Good for: Engineering and research-computing teams with a repetitive job that a tool could handle.
Typical work
- Terminal tools and dashboards in Rust.
- Monitoring for shared servers and workstations.
- Scripts and automation for repetitive workflows.
Examples
05
Process.
- 01
Talk.
A short call or a few emails to understand the problem, who it’s for and what “done” looks like.
- 02
Scope.
A written proposal covering what will be built, roughly how long it will take and what it will cost.
- 03
Build.
Small, demonstrable steps with regular check-ins, so you see working software early.
- 04
Hand over.
Documented code and clear instructions, so you can run and maintain it without depending on the studio.
06