Secure access and ownership
Inventory the domains, DNS, hosting, WordPress, analytics, Search Console, form delivery, media and existing supplier responsibilities. Take complete backups and agree who owns each account before changing anything.
Proposal prepared by Tom Adam
Proposal in brief
I propose to take responsibility for the Double Stone Steel website rebuild, migration and launch. The work would be delivered as a no-fee contribution, with Double Stone Steel covering only direct costs that it approves in advance. The immediate priority is to make sample requests dependable; the wider objective is a modern international website that the company owns and can improve without being locked into a long contract.
The safest approach is to separate the urgent commercial repair from the full rebuild. Double Stone Steel keeps its current services running while access, ownership and backups are confirmed. The sample-request journey is then repaired immediately, followed by a controlled rebuild and search-safe migration. Subject to timely access and approvals, the target for the initial full launch would be approximately 4–6 weeks. Coding speed is useful, but access, approvals, product accuracy and launch safeguards determine whether the result is dependable.
Inventory the domains, DNS, hosting, WordPress, analytics, Search Console, form delivery, media and existing supplier responsibilities. Take complete backups and agree who owns each account before changing anything.
Repair or replace the sample-request flow within the first 2–5 working days after access. Test submission, delivery, regional routing, confirmation, spam protection and measurement end to end.
Choose one primary global site with regional routes, or two regional surfaces on one shared foundation. Confirm which domains are primary, redirected or retained before design and migration begin.
Create the approved structure, visual system, product catalogue, finishes experience, technical resources, case studies and enquiry tools using reusable components and company-owned accounts.
Map existing URLs and content, preserve worthwhile pages, add redirects, carry metadata and structured content forward, and validate analytics, accessibility, performance and forms before launch.
Release in controlled stages, monitor errors and enquiries, document routine updates and leave Double Stone Steel with the code, credentials, backups and operating guide.
What good looks like
One person should coordinate feedback and one person should make final calls when opinions differ. This keeps a fast build from becoming a slow approval process.
Share the domain, DNS, hosting, WordPress, analytics, Search Console and form-delivery access, plus the current supplier agreement and renewal dates.
Approve the current finishes, product families, technical documents, lead destinations, delivery regions, legal details and the differences between UK/Europe and US enquiries.
Approve the structure, approve the visual direction and content, then approve the tested launch candidate. Feedback should be consolidated at each point.
Use reusable product, finish, case-study and resource components so regional differences do not create duplicate maintenance or two incompatible websites.
Make colours, finishes, substrates, applications and technical information easy to compare, with a clear path from inspiration to sample or project enquiry.
Use structured selections, validation, spam protection, regional routing, internal notifications, customer confirmation and analytics rather than an unmeasured contact form.
Retain the pages and topics that already earn visibility, remove obsolete branding carefully and build a redirect map before any domain or URL changes.
Keep the infrastructure lean, document it clearly and give the company an editing route for routine changes without exposing critical technical settings.
No professional fee
I would lead and complete the website work as a no-fee contribution to Double Stone Steel. My professional fee would be £0. The company would pay only approved direct costs—such as hosting, domains, email delivery, specialist software or licensed assets—and those would be kept in company-owned accounts wherever possible.
No long contract and no development invoice: only direct costs approved by Double Stone Steel before they are incurred.
Approve a 60–90 minute working session with Richard, Ian and the people who own the current website, domains and enquiries. The meeting should confirm the decision-maker, the domain model, access responsibilities and permission to repair the sample-request journey first. After that, I can return a final delivery plan and begin the first phase.