Working together
The build that fits.
Not the biggest one.
Every project is hand-coded from scratch. Before you pay anything, you see real prototype screenshots. If they fit, we write the scope and start. If they do not, you walk away without an invoice.
Included with every project
- Free prototype screenshots before you pay anything
- A year of support: updates, small features, library upgrades, re-audits
- A year of your chosen domain, registered and pointed by us
- Full setup and deployment, documented so it stays yours
- No invoice until you approve the scope and the schedule
01How we quote
Prototype first. Then a price. Then the build.
01 · Step
Share the brief
A short email to [email protected]. The problem, who it is for, and any constraints you already know about.
02 · Step
Free prototype screenshots
Real screenshots of the direction we would take. No charge, no obligation, no account to create.
03 · Step
You approve the direction
If the screenshots fit, we write a scope and a price. If they miss, we iterate once more for free, or we part company.
04 · Step
We start building
The first invoice goes out after you approve the scope and the schedule. From there it is hand-coded delivery and regular progress reports.
02What we never ship
The short version.
- Themes or page builders
- Plug-and-play CMS lock-in
- Rented auth, portals or dashboards
- Licence-locked tooling you can't own
- Tracking pixels, cookie banners
- Fabricated metrics or outcome guarantees
03Security by design
What the security work covers, and when it happens.
Security is a shape, not a scan. Threats get modelled before the first line of code, and the attack surface stays deliberately small. The finished build is audited before launch, then re-audited on an agreed schedule through the support year. Findings come to you in writing, with the fixes already ranked.
04Progress & reporting
You hear about the work while it is happening.
An update as each milestone lands: what went live, what the next one is, and anything that changed the plan. Nothing happens off-screen and nothing is held back for a demo. You can steer at any point without booking a meeting first.
05Launch infrastructure
Modern infrastructure, or yours.
We launch on Cloudflare Pages, Vercel, Fly.io, Hetzner, a VPS or your own cloud, whichever suits the workload. Bring your own and we deploy there. The setup is documented end to end, so your team can run it without us.
06Upgrade an existing product
Already shipped something? We can take it over.
If your current website, portal or SaaS is slow, hard to maintain or stuck on an old stack, we can re-architect it for security and performance, upgrade the libraries and ship the next version without rewriting your business. Still prototype-first, still a year of support included.
Start with the decision
A website explains what you offer and guides an enquiry. A portal carries an ongoing workflow for one customer or a whole team. SaaS turns a service into software people log into. If an off-the-shelf tool already does the job, we will say so, even though that answer costs us the project.
Choose a service →An agreed delivery plan
The proposal sets out deliverables, dependencies, review points, assumptions and exclusions. Typical artefacts: a sitemap or flow map, interface designs, reusable components, the build, a security audit, and a launch checklist. Everything you receive is yours, including the code, the designs, the infrastructure and the documentation.
What shapes the cost
How ready the content is, how many templates or workflows are involved, what has to integrate, how much data needs migrating, and the accessibility and security requirements. Domains, hosting, paid tools and connected services are ongoing costs rather than invisible parts of a one-off build. The first year of domain and support is on us.
Reviews and change
We agree a review rhythm and name the person who decides. When a new requirement changes the scope, we explain what it does to the delivery date before we proceed, and you get that in writing. Progress reaches you while it is happening, so an invoice never turns out to be the first you hear of a delay.
Ownership and handover
The agreement covers source code, designs, deployment information and operating notes. We list the third-party licences and ongoing responsibilities, so your team knows exactly what it owns and how to maintain it.
After launch
Every project includes a year of support: updates, features added or removed, library upgrades, re-audits and performance tuning. Beyond that year, maintenance is optional and scoped separately.