Home / How we work
How we workClear process, written evidence, security by default
What working with us looks like, week by week, and the controls we apply to every change.
01 · Rhythm
Your weekly rhythm with us
| What | When | What you get |
|---|---|---|
| End-of-day note | Daily | Done today, planned tomorrow, blockers |
| Sync call | 2–3 times a week, in your morning | Priorities and decisions |
| Sprint demo | Every two weeks | Working software, not slides |
| Status report | Every Friday | Progress, metrics, risks and decisions needed |
| Steering review | Monthly, with your sponsor and our founder | Value delivered against baseline; next priorities |
02 · Engineering controls
Every change reviewed, scanned, approved and traceable
Reviewed code
Protected branches and peer review on every pull request. Authors never approve their own work.
Scanned builds
Static analysis, dependency, secret, Infrastructure as Code and container scanning in every pipeline.
Controlled releases
Change records, release checklists, tested rollback and production changes through pipelines only.
03 · Security
Security and data protection
- Background verification for every team member
- Company-managed, encrypted laptops with device management
- Single sign-on and multi-factor authentication everywhere
- Least-privilege access with quarterly access reviews
- Client data stays in client systems unless the contract says otherwise
- NDA and IP assignment for every team member
- Incident response with defined notification times
- ISO/IEC 27001 roadmap: [target date to be added]
04 · Standards
Standards and frameworks we work to
We use published, peer-reviewed or industry-standard frameworks rather than proprietary jargon.
| Area | Framework | How we use it |
|---|---|---|
| Delivery performance | DORA metrics | Baseline and report deployment frequency, lead time, change failure rate, recovery time and rework |
| Reliability | Google SRE practices | SLOs, error budgets, blameless postmortems |
| Cloud architecture | AWS Well-Architected Framework | Design and review against six pillars |
| Cloud cost | FinOps Framework (FinOps Foundation) | Inform, optimise, operate; allocation and unit economics |
| AI risk | NIST AI RMF 1.0 and Generative AI Profile | Govern, map, measure, manage |
| AI management | ISO/IEC 42001:2023 | Policy, roles, impact assessment and controls |
| LLM security | OWASP Top 10 for LLM Applications | Threat model for prompt injection, data leakage and excessive agency |
| Supply chain | SLSA | Build provenance and artefact integrity |
| Service management | ITIL 4 | Incident, change and problem practices for run phases |
Next step
Start with one problem.
Tell us what is slowing your team down. The first call is 30 minutes, with no slides and no obligation. If we're not the right fit, we'll say so.