Case Study
We Replaced an Engineering Practice's Ageing Website in 30 Business Days
Structy already had a site. It had stopped being maintained, so we rebuilt it rather than patched it.
What We Built
Structy is a civil engineering practice in Greece. They came to us with a website that already existed and had stopped being looked after. Rather than work around it, we rebuilt it as an information-led site. The work ran for 30 business days, counted from the signed scope document.
- Project Duration
- 30 Business Days
Where It Started
The Site Had Stopped Being Maintained
A website nobody updates does not stand still, it falls behind. The content ages, the software underneath it ages faster, and at some point the site stops representing the company whose name is on it.
Working Around It Cost More Than Replacing It
Past a certain age every change takes longer than the change is worth, because whoever makes it has to work around what is already there. Structy had reached that point.
Clients Read the Site Before They Call
Somebody looking for a civil engineering practice reads the website first and picks up the phone second. The site was not doing that job.
How We Approached It
Replace, Do Not Repair
When a site has been left long enough, rebuilding is quicker than repairing. We said so before the quote rather than after.
Built Around the Content
Structy sells engineering work, and what a prospective client wants from the site is information. The site is built around that content rather than around effects.
A Date That Came From the Scope
The work ran 30 business days. That date came out of the scope document, which is written after we have seen what the work involves rather than before.
How the Rebuild Ran
- 1
We Read What Was Already There
The existing site is read before anything is quoted, because the quote depends on what is found.
- 2
Repair or Replace Is Decided First
That decision is made and said out loud before the quote, not discovered halfway through the work.
- 3
The Scope Is Written Down
What the work covers, and what it does not, goes into a document that both sides sign.
- 4
The Date Comes Out of the Scope
Thirty business days, counted from the signed document rather than promised before anyone looked.
- 5
Handover Decides Who Maintains It
Who keeps the site current is settled at handover. The old site fell behind because that was nobody’s job.
What Changed
The Site Represents the Practice Again
Somebody reading the site before they pick up the phone is reading about the firm as it is now, not as it was a few years ago.
Changes No Longer Fight the Structure
A change now takes about as long as the change is worth. That was the whole argument for rebuilding instead of repairing.
Maintenance Is Somebody's Job Now
The old site did not fall behind because anyone decided to let it. It fell behind because it was nobody's job. That is a decision to make at handover rather than a year later.
Frequently Asked Questions
Can you take over a site somebody else built?
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.
How do you decide between repairing and replacing?
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.
Do we lose our search rankings when the site is replaced?
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.
Do you work with companies abroad?
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.
What happens after the site goes live?
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.
How long does a site like this take?
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.
How much does a project cost?
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.
Who owns the code?
The source code is yours. Ownership of the software transfers to you under the terms of the contract once development is complete and payment has been made in full. Those terms, and the confidentiality clauses, are in the contract signed before development begins.
Other Case Studies
Floorwise
Products, quotes, orders and delivery run in one system, and agents quote from wherever they are.
Read the Case StudyKurtsan
Dealers see their own product list, and the catalogue produces its own PDF.
Read the Case StudyToptanfactory
Manufacturers and buyers meet in one marketplace, with three separate roles.
Read the Case StudyPetHaritam
Owners, vets and pet shops use one platform for different reasons.
Read the Case StudyFacing Similar Problems?
Tell us what you have now. We read it first and tell you whether it is worth repairing or replacing, before anybody talks about a price.
On this project we worked on Web Development Services, Software Support and Maintenance, Custom Software Development.
Aynı iş günü içinde dönüş yapıyoruz