Hosting & DevOps services

VPS Setup is a hosting & devops service from Livin Services. In one line: get a hardened, properly configured server without paying enterprise cloud rates. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

VPS Setup covers current-state review and target architecture for vps setup, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing and runbook covering deploys, incidents and recovery. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: get a hardened, properly configured server without paying enterprise cloud rates. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying VPS Setup to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

AWS Infrastructure is a hosting & devops service from Livin Services. In one line: use the right AWS services instead of the ones the tutorial mentioned. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

AWS Infrastructure covers current-state review and target architecture for aws infrastructure, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing and runbook covering deploys, incidents and recovery. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: use the right AWS services instead of the ones the tutorial mentioned. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying AWS Infrastructure to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Cloudflare Setup is a hosting & devops service from Livin Services. In one line: put caching, DNS and attack protection in front of everything you run. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Cloudflare Setup covers current-state review and target architecture for cloudflare setup, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing and runbook covering deploys, incidents and recovery. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: put caching, DNS and attack protection in front of everything you run. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Cloudflare Setup to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

CI/CD Pipeline Setup is a hosting & devops service from Livin Services. In one line: make deploying boring, repeatable and reversible. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

CI/CD Pipeline Setup covers current-state review and target architecture for ci/cd pipeline setup, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing and runbook covering deploys, incidents and recovery. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: make deploying boring, repeatable and reversible. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying CI/CD Pipeline Setup to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Server Optimization is a hosting & devops service from Livin Services. In one line: make existing hardware handle far more before you pay for more. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Server Optimization covers current-state review and target architecture for server optimization, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing and runbook covering deploys, incidents and recovery. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: make existing hardware handle far more before you pay for more. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Server Optimization to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Website Migration to a New Host is a hosting & devops service from Livin Services. In one line: move your site to better hosting without a day of downtime or a week of broken email. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Website Migration to a New Host covers current-state review and target architecture for website migration to a new host, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing, runbook covering deploys, incidents and recovery, a full copy staged and tested on the new host before anything changes, dns ttl lowered in advance so the cutover is minutes, not hours and email, dns records and ssl verified after the move — the two things most migrations break. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: move your site to better hosting without a day of downtime or a week of broken email. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Website Migration to a New Host to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Database Administration is a hosting & devops service from Livin Services. In one line: fix the slow queries and backup gaps that hosting upgrades cannot solve. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Database Administration covers current-state review and target architecture for database administration, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing, runbook covering deploys, incidents and recovery, slow query log analysis with the queries actually costing you time, index and schema changes tested against a copy of production first and point-in-time recovery configured and verified by restoring it. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: fix the slow queries and backup gaps that hosting upgrades cannot solve. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Database Administration to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Backup & Disaster Recovery is a hosting & devops service from Livin Services. In one line: have backups you have actually restored, with a recovery time you have measured. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Backup & Disaster Recovery covers current-state review and target architecture for backup & disaster recovery, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing, runbook covering deploys, incidents and recovery, offsite, versioned backups held outside the account that hosts the site, a documented recovery time and recovery point objective you have seen proven and one full restore performed in front of you, because an untested backup is not a backup. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: have backups you have actually restored, with a recovery time you have measured. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Backup & Disaster Recovery to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Email Hosting & Deliverability is a hosting & devops service from Livin Services. In one line: stop your invoices and order confirmations landing in spam. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Email Hosting & Deliverability covers current-state review and target architecture for email hosting & deliverability, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing, runbook covering deploys, incidents and recovery, spf, dkim and dmarc configured and validated against real test sends, transactional mail moved off the web server onto a service built for it and reputation and bounce monitoring so a future problem surfaces early. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: stop your invoices and order confirmations landing in spam. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Email Hosting & Deliverability to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Azure Infrastructure is a hosting & devops service from Livin Services. In one line: build inside the Microsoft ecosystem your IT team already governs. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Azure Infrastructure covers current-state review and target architecture for azure infrastructure, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing and runbook covering deploys, incidents and recovery. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: build inside the Microsoft ecosystem your IT team already governs. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Azure Infrastructure to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Google Cloud Infrastructure is a hosting & devops service from Livin Services. In one line: run data and container workloads where Google tooling genuinely wins. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Google Cloud Infrastructure covers current-state review and target architecture for google cloud infrastructure, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing and runbook covering deploys, incidents and recovery. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: run data and container workloads where Google tooling genuinely wins. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Google Cloud Infrastructure to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

DigitalOcean Setup is a hosting & devops service from Livin Services. In one line: get predictable pricing and simple ops for a straightforward application. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

DigitalOcean Setup covers current-state review and target architecture for digitalocean setup, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing and runbook covering deploys, incidents and recovery. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: get predictable pricing and simple ops for a straightforward application. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying DigitalOcean Setup to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Docker Containerization is a hosting & devops service from Livin Services. In one line: make local, staging and production behave identically for once. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Docker Containerization covers current-state review and target architecture for docker containerization, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing and runbook covering deploys, incidents and recovery. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: make local, staging and production behave identically for once. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Docker Containerization to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Kubernetes Setup is a hosting & devops service from Livin Services. In one line: run orchestration properly if you genuinely need it, and only then. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Kubernetes Setup covers current-state review and target architecture for kubernetes setup, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing and runbook covering deploys, incidents and recovery. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: run orchestration properly if you genuinely need it, and only then. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Kubernetes Setup to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

CDN Setup is a hosting & devops service from Livin Services. In one line: serve assets from the edge and cut load times worldwide. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

CDN Setup covers current-state review and target architecture for cdn setup, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing and runbook covering deploys, incidents and recovery. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: serve assets from the edge and cut load times worldwide. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying CDN Setup to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

DNS Management is a hosting & devops service from Livin Services. In one line: get records, mail authentication and failover right the first time. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

DNS Management covers current-state review and target architecture for dns management, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing and runbook covering deploys, incidents and recovery. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: get records, mail authentication and failover right the first time. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying DNS Management to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

SSL Certificate Setup is a hosting & devops service from Livin Services. In one line: automate certificates so nothing expires on a bank holiday. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

SSL Certificate Setup covers current-state review and target architecture for ssl certificate setup, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing and runbook covering deploys, incidents and recovery. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: automate certificates so nothing expires on a bank holiday. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying SSL Certificate Setup to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Linux Server Administration is a hosting & devops service from Livin Services. In one line: keep patching, users and services in order without drama. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Linux Server Administration covers current-state review and target architecture for linux server administration, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing and runbook covering deploys, incidents and recovery. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: keep patching, users and services in order without drama. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Linux Server Administration to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Nginx Configuration is a hosting & devops service from Livin Services. In one line: tune the layer every request passes through before anything else. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Nginx Configuration covers current-state review and target architecture for nginx configuration, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing and runbook covering deploys, incidents and recovery. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: tune the layer every request passes through before anything else. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Nginx Configuration to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Managed WordPress Hosting Setup is a hosting & devops service from Livin Services. In one line: get WordPress on hosting built for it, with caching and updates handled. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Managed WordPress Hosting Setup covers current-state review and target architecture for managed wordpress hosting setup, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing, runbook covering deploys, incidents and recovery, object and page caching configured for your actual plugin stack, staging environment with a one-click push to production and an honest comparison of managed hosting cost against a tuned vps. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: get WordPress on hosting built for it, with caching and updates handled. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Managed WordPress Hosting Setup to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Server Migration is a hosting & devops service from Livin Services. In one line: move an application between servers, providers or regions with a tested rollback. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Server Migration covers current-state review and target architecture for server migration, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing, runbook covering deploys, incidents and recovery, inventory of every service, cron job and credential on the old server, parallel run with both environments live before the switch and a rollback that has been rehearsed, not just written down. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: move an application between servers, providers or regions with a tested rollback. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Server Migration to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Uptime & Performance Monitoring is a hosting & devops service from Livin Services. In one line: find out before your customers do, from a person rather than a dashboard. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Uptime & Performance Monitoring covers current-state review and target architecture for uptime & performance monitoring, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing, runbook covering deploys, incidents and recovery, checks from multiple regions on the pages that earn money, not just the homepage, alerts routed to a phone with escalation, not to a shared inbox and thresholds tuned to stop alert fatigue, which is what makes monitoring useless. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: find out before your customers do, from a person rather than a dashboard. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Uptime & Performance Monitoring to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Cloud Cost Optimization is a hosting & devops service from Livin Services. In one line: cut the hosting bill nobody can fully explain, and know what caused it. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Cloud Cost Optimization covers current-state review and target architecture for cloud cost optimization, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing, runbook covering deploys, incidents and recovery, line-by-line attribution of spend to the service causing it, right-sizing, caching and storage-class changes ranked by saving against risk and our fee stated against the monthly saving, including when it is marginal. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: cut the hosting bill nobody can fully explain, and know what caused it. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Cloud Cost Optimization to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Staging Environment Setup is a hosting & devops service from Livin Services. In one line: test changes somewhere real before they reach customers. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Staging Environment Setup covers current-state review and target architecture for staging environment setup, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing, runbook covering deploys, incidents and recovery, a staging site matching production configuration, not an approximation, sanitised data so live customer records never sit in a test environment and access control and noindex headers so staging never gets crawled or indexed. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: test changes somewhere real before they reach customers. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Staging Environment Setup to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Load Balancing & High Availability is a hosting & devops service from Livin Services. In one line: survive a single server failing, if the cost is genuinely worth it to you. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Load Balancing & High Availability covers current-state review and target architecture for load balancing & high availability, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing, runbook covering deploys, incidents and recovery, health checks and failover tested by deliberately killing a node, session and file handling made stateless so failover does not log people out and the honest cost of each availability tier, so you choose rather than assume. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: survive a single server failing, if the cost is genuinely worth it to you. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Load Balancing & High Availability to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

cPanel & WHM Management is a hosting & devops service from Livin Services. In one line: run shared or reseller hosting properly without living in the control panel. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

cPanel & WHM Management covers current-state review and target architecture for cpanel & whm management, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing, runbook covering deploys, incidents and recovery, account, quota and package structure that matches how you actually sell, automated backups verified outside the panel that created them and php version and extension management per account without breaking sites. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: run shared or reseller hosting properly without living in the control panel. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying cPanel & WHM Management to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

Serverless & Edge Deployment is a hosting & devops service from Livin Services. In one line: deploy to Vercel, Netlify or Cloudflare and pay for traffic instead of idle servers. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

Serverless & Edge Deployment covers current-state review and target architecture for serverless & edge deployment, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing, runbook covering deploys, incidents and recovery, build pipeline with preview deployments on every branch, caching and revalidation configured so the edge actually serves the page and a clear statement of where serverless costs more than a server — long jobs and heavy egress. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

It fits teams where deploys happen at midnight because everyone expects breakage. The goal is simple: deploy to Vercel, Netlify or Cloudflare and pay for traffic instead of idle servers. If your situation is different, tell us and we will point you at the hosting & devops service that actually fits — including one we do not sell.

When the underlying problem sits somewhere else. Buying Serverless & Edge Deployment to fix something it does not touch is expensive and disappointing in equal measure. Tell us what outcome you are actually after and we will say plainly whether this is the right service, a different one, or nothing at all right now.

A good freelancer is often the right answer for a narrow, well-defined task, and cheaper. What an agency adds is continuity when someone is unavailable, a second pair of eyes on decisions, and accountability that survives the individual. Judge it on whether your project needs those things — plenty do not.

This service is scoped as a defined piece of work with a handover at the end, which is deliberate: it means the engagement has a finish line rather than drifting into an indefinite monthly cost. If you need continuing support afterwards we can arrange it, but it is a separate agreement you enter knowingly.

Revisions within the agreed scope are part of the work, not a numbered allowance to be rationed. What is charged separately is a change of direction — new requirements, a reversed decision, or work outside what was scoped. The distinction is written into the scope so it is not decided by argument later.

Sometimes, and sometimes not — it depends on whether the thing it fixes is actually what is holding you back. Smaller scopes are quoted the same way as large ones, with no minimum engagement, so size is not the barrier. Being honest about whether this is your highest-leverage move is more useful to you than a yes.

A typical VPS Setup engagement runs 3 days–1 week from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out VPS Setup isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical AWS Infrastructure engagement runs 2–8 weeks from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out AWS Infrastructure isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Cloudflare Setup engagement runs 3 days–2 weeks from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Cloudflare Setup isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical CI/CD Pipeline Setup engagement runs 1–3 weeks from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out CI/CD Pipeline Setup isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Server Optimization engagement runs 1–3 weeks from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Server Optimization isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Website Migration to a New Host engagement runs 2 days–1 week from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Website Migration to a New Host isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Database Administration engagement runs 1–3 weeks from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Database Administration isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Backup & Disaster Recovery engagement runs 1–2 weeks from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Backup & Disaster Recovery isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Email Hosting & Deliverability engagement runs 3 days–1 week from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Email Hosting & Deliverability isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Azure Infrastructure engagement runs 2–8 weeks from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Azure Infrastructure isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Google Cloud Infrastructure engagement runs 2–8 weeks from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Google Cloud Infrastructure isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical DigitalOcean Setup engagement runs 1–2 weeks from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out DigitalOcean Setup isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Docker Containerization engagement runs 1–4 weeks from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Docker Containerization isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Kubernetes Setup engagement runs 3–10 weeks from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Kubernetes Setup isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical CDN Setup engagement runs 3 days–1 week from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out CDN Setup isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical DNS Management engagement runs 2–5 days from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out DNS Management isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical SSL Certificate Setup engagement runs 1–3 days from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out SSL Certificate Setup isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Linux Server Administration engagement runs ongoing from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Linux Server Administration isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Nginx Configuration engagement runs 3 days–1 week from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Nginx Configuration isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Managed WordPress Hosting Setup engagement runs 3 days–1 week from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Managed WordPress Hosting Setup isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Server Migration engagement runs 1–3 weeks from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Server Migration isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Uptime & Performance Monitoring engagement runs 2–5 days from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Uptime & Performance Monitoring isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Cloud Cost Optimization engagement runs 1–3 weeks from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Cloud Cost Optimization isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Often, yes — and if we think so, we'll tell you. Bringing us in makes sense when your team hasn't done this particular thing before, when it's a one-off that doesn't justify a hire, or when time rather than skill is what you're short of. If it's that last one, be clear with yourself that you're buying time back, not expertise you don't have.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with AWS Cost Explorer, CloudWatch and Infracost for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

You do, outright, on final payment. Code, files, accounts, assets. Nothing sits on our infrastructure holding you in place and no licence quietly reverts to us. If you move to someone else next year, everything you need goes with you.

You get a handover: the work itself, documentation of how it is put together, and access to everything involved. We stay available for questions afterwards. There is no automatic rollover into a monthly fee — if you want ongoing support you ask for it, rather than having to cancel something you never chose.

That is the intention. The handover exists so your team is not dependent on us for routine changes. Where the work involves something your team genuinely cannot maintain, we say so during scoping rather than presenting it as a feature after the fact.

We'll guarantee the scope, the date and the quality of the work, because those are ours to control and they're written down. We won't guarantee an outcome that depends on your market, your competitors and platforms none of us own. Anyone promising you a specific number there is either guessing or selling.

We agree what success looks like before starting, and it has to be something measurable rather than a feeling. Whichever measure applies to your situation, you get the before figure as well as the after — reporting a result without a baseline is not evidence of anything.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

You get the before-and-after on whatever measure was agreed at the start, using the same method both times. Ongoing monthly reporting is a separate arrangement — a recurring report is a recurring cost, and it should be something you chose rather than something that appeared.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Staging Environment Setup engagement runs 3 days–1 week from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Staging Environment Setup isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Load Balancing & High Availability engagement runs 2–5 weeks from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Load Balancing & High Availability isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical cPanel & WHM Management engagement runs ongoing from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out cPanel & WHM Management isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

A typical Serverless & Edge Deployment engagement runs 1–3 weeks from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

Four things, roughly in order of how much they matter. How much is genuinely bespoke versus configuration. How many integrations and outside systems are in play. What state your starting point is in — inherited problems have to be sorted before anything new can sit on top of them. And how many people are in the approval chain. We'll name which of those apply to you in the quote, so you can see where the number came from.

No. Scoping and quoting are free, and so is the conversation to get there. If it turns out Serverless & Edge Deployment isn't what you need, you'll hear that for free too — rather than being sold a paid discovery phase that arrives at the same answer three weeks later.

If we underestimated something inside the agreed scope, we absorb it. That's what a fixed price means. If the scope itself changes because a new requirement turns up, we quote that separately and you decide whether to go ahead before anyone touches it. You won't get an invoice for something you didn't approve.

Agreed in writing before work starts, as part of the scope. There is no deposit taken to hold a slot in the calendar and no charge for the scoping conversation. If the engagement is stopped partway by either side, you pay for the work completed to that point and you keep it.

Depends entirely on what it is. Build work shows immediately because the thing either exists or it does not. Anything depending on user behaviour, search engines or list warm-up takes longer, and how much longer is a function of your traffic volume — low traffic means a longer wait before any change is distinguishable from noise. We say which category your work falls into up front.

Usually one of three reasons: a narrower scope than ours, a junior person delivering it, or exclusions that surface as change requests later. Ask both suppliers for the written scope and compare those rather than the totals. If theirs genuinely covers the same ground for less, take it — and we will tell you so.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Say what is happening now, what you want to be different, and by when. That is genuinely enough to get a scope back. You do not need to specify a solution — if you tell us the outcome, we will tell you what it takes, and sometimes that is less than you expected. What slows a brief down is a list of features with no stated problem behind them.

Five questions worth asking any supplier. Who will actually do the work, not who is in the meeting. What is explicitly excluded. What happens if it takes longer than quoted. Whose name the accounts are in at the end. And what they would talk you out of — the last one is the hardest to fake, and the most revealing.

Everything in the written scope delivered and verified, your team able to maintain it without us, and a recorded before-and-after on whatever measure you agreed at the start. Notably not: a slide deck, a vanity score, or a number with no baseline beside it.

Describe the symptom rather than the fix. If the symptom is one this service addresses, it is the right service. If it is not, we will name the one that is — including when that is a different discipline entirely, or nothing right now. Guessing at the service before naming the problem is how budgets get spent on the wrong thing.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Three real ones. The starting point turning out to be worse than it looked, which extends the work. A dependency outside our control — a platform, a plugin, a third-party API — changing mid-project. And decisions on your side taking longer than planned, which is the most common of the three by a distance. We name whichever apply to you in the scope rather than after.

That is the thing we test hardest against. Work happens on a copy or in a staging environment wherever the platform allows it, and we check the paths that already work before anything goes live. Where a change genuinely cannot be made without affecting something else, you hear that before it happens, not after.

It stays yours and it stays in your systems. We work inside accounts you own, we do not export customer data to our own tools, and access is created so you can revoke it the moment the project ends. If a piece of work genuinely requires handling personal data, we say what, why and for how long, in writing.

Yes, and without making it an event. Send yours over and we will sign it. We do not publish client names or work without permission either way — the example builds on this site are deliberately unnamed for that reason.

Yes. You pay for what has been completed and you take everything produced up to that point, including access and any partial documentation. Nothing is held back as leverage. We would rather stop a project that has stopped making sense than bill through to the end of it.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Ubuntu, Nginx, Fail2ban and Certbot for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with AWS, Terraform, CloudWatch and ECS for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Cloudflare, Workers, R2 and WAF for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with GitHub Actions, GitLab CI and Docker for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Nginx, Redis, PHP-FPM and MySQL for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with rsync, Cloudflare, Certbot and MySQL for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with MySQL, PostgreSQL, Percona Toolkit and pgBadger for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Restic, AWS S3, BorgBackup and Cron for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Google Workspace, Microsoft 365, DMARC and Postmark for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Azure, Bicep and Azure Monitor for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with GCP, Cloud Run, BigQuery and Terraform for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with DigitalOcean, App Platform and Spaces for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Docker, Docker Compose and GitHub Actions for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Kubernetes, Helm, ArgoCD and Prometheus for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Cloudflare, CloudFront and Fastly for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Cloudflare DNS, Route 53 and DMARC for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Certbot, Let's Encrypt and Cloudflare for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Ubuntu, Debian and Ansible for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Nginx, Brotli and HTTP/3 for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Kinsta, WP Engine, Cloudflare and Redis for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Ansible, Terraform, Docker and rsync for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with UptimeRobot, Grafana, Better Stack and Sentry for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Docker, GitHub Actions and Cloudflare Access for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Nginx, HAProxy, AWS ALB and Keepalived for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with cPanel, WHM, CloudLinux and JetBackup for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

Four stages, and none of them are a surprise. First a conversation about what you actually need. Then a written scope with a fixed price and a start date, sent before you commit to anything. Then the build, which you can see as it happens rather than being shown at the end. Then handover — documentation and everything you need to run it without us.

The people who scoped it. There is no arrangement here where a senior person wins the work and a junior delivers it — you will know who is on your project and you will speak to them directly rather than through an account manager relaying messages.

WhatsApp or email for day-to-day, whichever you prefer, plus a written update at each milestone. We do not require you to attend a standing weekly call to receive information that fits in a message. If something is going wrong you hear it when we find out, not at the next scheduled meeting.

Access to the relevant systems, one person on your side who can make decisions, and any content or assets the scope depends on. The most common cause of delay on this kind of work is not the build — it is waiting on approvals and material from the client side, so we agree who owns those before we begin.

We work with Vercel, Netlify, Cloudflare Workers and AWS Lambda for this. If your stack differs we will tell you honestly whether we are the right team before you commit — we would rather turn work down than learn a platform on your budget.

Usually yes, and we prefer to. Rebuilding something that works is a cost with no return. We review what you have first and tell you plainly which parts are worth keeping, which need repair, and which are cheaper to replace than to maintain — including when the honest answer is that nothing needs to change.

Message us with what you need. One paragraph is plenty. You'll hear back within a business day, either with a written scope and a fixed price, or with a couple of questions if something important is missing. There's no form to fill in before you get to speak to a person.

Regularly, and it usually goes fine. What makes it work is a clear split of who owns what, written down before anyone starts. What makes it fail is two suppliers with overlapping scope and no agreed boundary, which turns into a blame conversation the first time something breaks.

Often yes. We will review what exists and tell you plainly whether it is worth continuing or cheaper to redo — and we will say "continue" when that is true, even though a rebuild is the larger invoice. What we will not do is quote a rescue without looking at the state of it first.

A walkthrough at handover is included, and the documentation is written for a person who was not in the build. If you want structured training beyond that — several sessions, multiple people, recorded material — say so during scoping and it goes in as a line item rather than being assumed either way.

The person doing the work, directly. There is no account manager relaying messages, and no ticket queue between you and the answer. If it is urgent, WhatsApp reaches someone faster than email during either office's working day.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

The basics are, and they are not optional extras: keyboard navigation, sensible labelling, and colour contrast that a person can actually read. A full WCAG audit and remediation is a bigger piece of work with its own scope — we will tell you which you need rather than quietly implying the basics are the same thing.

We check. Anything we add is measured on a real mid-range phone before and after, because that is the device most of your traffic is on and it is where slowness actually shows. If a requested feature would cost real performance, you get told the trade-off and you decide — rather than discovering it in a report later.

Where the work touches URLs, content or page structure, yes — and we plan for it. Redirects mapped, structure preserved, nothing silently dropped. Where it does not touch those things, it will not, and we will not claim it as an SEO benefit to make the quote look better.

On real devices, not just a resized desktop browser. The two are not the same: touch targets, keyboard behaviour on forms, and how it performs on a mid-range Android are all things a resized window will happily lie about.

You do, from the first day. Cloud accounts, domain registrar, DNS and hosting are all created in your name with you as owner, and we work under our own access. If you stop working with us, you remove our access and nothing stops. Nothing is held as leverage.

You do, outright, on final payment. Code, files, accounts, assets. Nothing sits on our infrastructure holding you in place and no licence quietly reverts to us. If you move to someone else next year, everything you need goes with you.

You get a handover: the work itself, documentation of how it is put together, and access to everything involved. We stay available for questions afterwards. There is no automatic rollover into a monthly fee — if you want ongoing support you ask for it, rather than having to cancel something you never chose.

If it is a defect in what we built, we fix it — that is not a support contract, it is finishing the job properly. If it breaks because something else changed, a platform update or a third-party service, we will tell you what happened and what it would take to resolve, and you decide.

That is the intention. The handover exists so your team is not dependent on us for routine changes. Where the work involves something your team genuinely cannot maintain, we say so during scoping rather than presenting it as a feature after the fact.

You get the before-and-after on whatever measure was agreed at the start, using the same method both times. Ongoing monthly reporting is a separate arrangement — a recurring report is a recurring cost, and it should be something you chose rather than something that appeared.

You do, outright, on final payment. Code, files, accounts, assets. Nothing sits on our infrastructure holding you in place and no licence quietly reverts to us. If you move to someone else next year, everything you need goes with you.

You get a handover: the work itself, documentation of how it is put together, and access to everything involved. We stay available for questions afterwards. There is no automatic rollover into a monthly fee — if you want ongoing support you ask for it, rather than having to cancel something you never chose.

That is the intention. The handover exists so your team is not dependent on us for routine changes. Where the work involves something your team genuinely cannot maintain, we say so during scoping rather than presenting it as a feature after the fact.

You get the before-and-after on whatever measure was agreed at the start, using the same method both times. Ongoing monthly reporting is a separate arrangement — a recurring report is a recurring cost, and it should be something you chose rather than something that appeared.

You do, outright, on final payment. Code, files, accounts, assets. Nothing sits on our infrastructure holding you in place and no licence quietly reverts to us. If you move to someone else next year, everything you need goes with you.

You get a handover: the work itself, documentation of how it is put together, and access to everything involved. We stay available for questions afterwards. There is no automatic rollover into a monthly fee — if you want ongoing support you ask for it, rather than having to cancel something you never chose.

That is the intention. The handover exists so your team is not dependent on us for routine changes. Where the work involves something your team genuinely cannot maintain, we say so during scoping rather than presenting it as a feature after the fact.

You get the before-and-after on whatever measure was agreed at the start, using the same method both times. Ongoing monthly reporting is a separate arrangement — a recurring report is a recurring cost, and it should be something you chose rather than something that appeared.

You do, outright, on final payment. Code, files, accounts, assets. Nothing sits on our infrastructure holding you in place and no licence quietly reverts to us. If you move to someone else next year, everything you need goes with you.

You get a handover: the work itself, documentation of how it is put together, and access to everything involved. We stay available for questions afterwards. There is no automatic rollover into a monthly fee — if you want ongoing support you ask for it, rather than having to cancel something you never chose.

That is the intention. The handover exists so your team is not dependent on us for routine changes. Where the work involves something your team genuinely cannot maintain, we say so during scoping rather than presenting it as a feature after the fact.

You get the before-and-after on whatever measure was agreed at the start, using the same method both times. Ongoing monthly reporting is a separate arrangement — a recurring report is a recurring cost, and it should be something you chose rather than something that appeared.

You do, outright, on final payment. Code, files, accounts, assets. Nothing sits on our infrastructure holding you in place and no licence quietly reverts to us. If you move to someone else next year, everything you need goes with you.

You get a handover: the work itself, documentation of how it is put together, and access to everything involved. We stay available for questions afterwards. There is no automatic rollover into a monthly fee — if you want ongoing support you ask for it, rather than having to cancel something you never chose.

That is the intention. The handover exists so your team is not dependent on us for routine changes. Where the work involves something your team genuinely cannot maintain, we say so during scoping rather than presenting it as a feature after the fact.

You get the before-and-after on whatever measure was agreed at the start, using the same method both times. Ongoing monthly reporting is a separate arrangement — a recurring report is a recurring cost, and it should be something you chose rather than something that appeared.

You do, outright, on final payment. Code, files, accounts, assets. Nothing sits on our infrastructure holding you in place and no licence quietly reverts to us. If you move to someone else next year, everything you need goes with you.

You get a handover: the work itself, documentation of how it is put together, and access to everything involved. We stay available for questions afterwards. There is no automatic rollover into a monthly fee — if you want ongoing support you ask for it, rather than having to cancel something you never chose.

That is the intention. The handover exists so your team is not dependent on us for routine changes. Where the work involves something your team genuinely cannot maintain, we say so during scoping rather than presenting it as a feature after the fact.

You get the before-and-after on whatever measure was agreed at the start, using the same method both times. Ongoing monthly reporting is a separate arrangement — a recurring report is a recurring cost, and it should be something you chose rather than something that appeared.

You do, outright, on final payment. Code, files, accounts, assets. Nothing sits on our infrastructure holding you in place and no licence quietly reverts to us. If you move to someone else next year, everything you need goes with you.

You get a handover: the work itself, documentation of how it is put together, and access to everything involved. We stay available for questions afterwards. There is no automatic rollover into a monthly fee — if you want ongoing support you ask for it, rather than having to cancel something you never chose.

That is the intention. The handover exists so your team is not dependent on us for routine changes. Where the work involves something your team genuinely cannot maintain, we say so during scoping rather than presenting it as a feature after the fact.

You get the before-and-after on whatever measure was agreed at the start, using the same method both times. Ongoing monthly reporting is a separate arrangement — a recurring report is a recurring cost, and it should be something you chose rather than something that appeared.

You do, outright, on final payment. Code, files, accounts, assets. Nothing sits on our infrastructure holding you in place and no licence quietly reverts to us. If you move to someone else next year, everything you need goes with you.

You get a handover: the work itself, documentation of how it is put together, and access to everything involved. We stay available for questions afterwards. There is no automatic rollover into a monthly fee — if you want ongoing support you ask for it, rather than having to cancel something you never chose.

That is the intention. The handover exists so your team is not dependent on us for routine changes. Where the work involves something your team genuinely cannot maintain, we say so during scoping rather than presenting it as a feature after the fact.

You get the before-and-after on whatever measure was agreed at the start, using the same method both times. Ongoing monthly reporting is a separate arrangement — a recurring report is a recurring cost, and it should be something you chose rather than something that appeared.

You do, outright, on final payment. Code, files, accounts, assets. Nothing sits on our infrastructure holding you in place and no licence quietly reverts to us. If you move to someone else next year, everything you need goes with you.

You get a handover: the work itself, documentation of how it is put together, and access to everything involved. We stay available for questions afterwards. There is no automatic rollover into a monthly fee — if you want ongoing support you ask for it, rather than having to cancel something you never chose.

That is the intention. The handover exists so your team is not dependent on us for routine changes. Where the work involves something your team genuinely cannot maintain, we say so during scoping rather than presenting it as a feature after the fact.

You get the before-and-after on whatever measure was agreed at the start, using the same method both times. Ongoing monthly reporting is a separate arrangement — a recurring report is a recurring cost, and it should be something you chose rather than something that appeared.

You do, outright, on final payment. Code, files, accounts, assets. Nothing sits on our infrastructure holding you in place and no licence quietly reverts to us. If you move to someone else next year, everything you need goes with you.

You get a handover: the work itself, documentation of how it is put together, and access to everything involved. We stay available for questions afterwards. There is no automatic rollover into a monthly fee — if you want ongoing support you ask for it, rather than having to cancel something you never chose.

That is the intention. The handover exists so your team is not dependent on us for routine changes. Where the work involves something your team genuinely cannot maintain, we say so during scoping rather than presenting it as a feature after the fact.

You get the before-and-after on whatever measure was agreed at the start, using the same method both times. Ongoing monthly reporting is a separate arrangement — a recurring report is a recurring cost, and it should be something you chose rather than something that appeared.

You do, outright, on final payment. Code, files, accounts, assets. Nothing sits on our infrastructure holding you in place and no licence quietly reverts to us. If you move to someone else next year, everything you need goes with you.

You get a handover: the work itself, documentation of how it is put together, and access to everything involved. We stay available for questions afterwards. There is no automatic rollover into a monthly fee — if you want ongoing support you ask for it, rather than having to cancel something you never chose.

That is the intention. The handover exists so your team is not dependent on us for routine changes. Where the work involves something your team genuinely cannot maintain, we say so during scoping rather than presenting it as a feature after the fact.

You get the before-and-after on whatever measure was agreed at the start, using the same method both times. Ongoing monthly reporting is a separate arrangement — a recurring report is a recurring cost, and it should be something you chose rather than something that appeared.

You do, outright, on final payment. Code, files, accounts, assets. Nothing sits on our infrastructure holding you in place and no licence quietly reverts to us. If you move to someone else next year, everything you need goes with you.

You get a handover: the work itself, documentation of how it is put together, and access to everything involved. We stay available for questions afterwards. There is no automatic rollover into a monthly fee — if you want ongoing support you ask for it, rather than having to cancel something you never chose.

That is the intention. The handover exists so your team is not dependent on us for routine changes. Where the work involves something your team genuinely cannot maintain, we say so during scoping rather than presenting it as a feature after the fact.

You get the before-and-after on whatever measure was agreed at the start, using the same method both times. Ongoing monthly reporting is a separate arrangement — a recurring report is a recurring cost, and it should be something you chose rather than something that appeared.

You do, outright, on final payment. Code, files, accounts, assets. Nothing sits on our infrastructure holding you in place and no licence quietly reverts to us. If you move to someone else next year, everything you need goes with you.

You get a handover: the work itself, documentation of how it is put together, and access to everything involved. We stay available for questions afterwards. There is no automatic rollover into a monthly fee — if you want ongoing support you ask for it, rather than having to cancel something you never chose.

That is the intention. The handover exists so your team is not dependent on us for routine changes. Where the work involves something your team genuinely cannot maintain, we say so during scoping rather than presenting it as a feature after the fact.

You get the before-and-after on whatever measure was agreed at the start, using the same method both times. Ongoing monthly reporting is a separate arrangement — a recurring report is a recurring cost, and it should be something you chose rather than something that appeared.

You do, outright, on final payment. Code, files, accounts, assets. Nothing sits on our infrastructure holding you in place and no licence quietly reverts to us. If you move to someone else next year, everything you need goes with you.