Scope in writing
Before work starts you get a written list of what is in, what is out and what we need from you. Changes are welcome and are estimated before they begin.
The rules we play by.
These are commitments about how we work, not boasts about results. Hold us to them.
Ranges, then numbers
Early estimates are ranges because early knowledge is fuzzy. As blocks get clearer, ranges narrow. We never quietly widen them.
Builds every fortnight
During active work you can try something real at least every two weeks, with notes on what changed.
Bad news early
If a date or budget is wobbling, you hear it as soon as we know, together with options.
Accessibility target
WCAG 2.2 AA as standard. Known gaps are written down with reasons and plans.
Security basics, always
Dependencies kept current, secrets kept out of code, access kept minimal and reviewed.
Privacy by default
Collect only what a feature needs. No trackers unless you have a clear lawful reason and the visitor agrees.
Clean handover
Source code, accounts, credentials, documentation and a list of every external service. If you move on, we help the next team.
No borrowed glory
We do not show awards, client logos, statistics or testimonials on this site.
Ready to stack something?
Tell us what you have in mind. A paragraph is plenty; we reply with questions on the next working day.