We Replaced an Engineering Practice's Ageing Website in 30 Business Days

Yes, and that is how this one started. We read what is already there first and tell you whether it is worth repairing or replacing, before quoting.

By what the next year of changes would cost. If working around the old structure costs more than replacing it, replacing it is the cheaper option even though it looks more expensive on the first day.

That is the part of a rebuild that has to be planned rather than discovered afterwards. Old addresses are redirected to their new equivalents, so what a search engine already knows about does not go missing.

Yes, a large part of our work is international. Structy is in Greece. Calls, documents and the comments inside the code are in English, and where there is a time difference we agree the overlapping hours at the start.

Maintenance is a separate arrangement, and it is the reason this project existed at all. A site nobody is responsible for drifts back to where this one started.

The scope document gives you a date, and it is written after we have seen what the work actually involves rather than before. What moves that date is usually not the building. It is how quickly content, logins and approvals come back from your side, so we agree who is responsible for what at the start.

There is no price list, because the scope decides it. How many screens there are, who logs in, which other systems it has to talk to and who maintains the content all move the number. After the first call and the technical review you get a document with the price and the timeline in it, and you read that before anything is signed.

You do. The code we write for you is yours, and that is stated in the contract that is signed before development begins, alongside the confidentiality terms.