"We Deliver the Full Source Code" — Three Ways to Verify It's Actually Usable
"We deliver the complete source code of your website." — nine out of ten website providers will say this. But after a decade of inspecting goods in manufacturing, I know one thing cold: verbal promises don't count. What runs, counts.
The source code of a CMS template site and "complete code that runs independently outside the provider's environment" are two completely different things. Here are three tests you can run on the spot at delivery acceptance.
Test 1: Demand an independent deployment test
Say this sentence at delivery:
"Please hand over the source code and database (or data files) — I'll have a friend try deploying it on their server."
This is the most brutal test. If the delivery is genuinely complete, the other side agrees readily — the stuff is yours anyway. The ones who start hedging are exposed immediately, because a CMS template site's code is locked to the provider's environment: either it won't run on another server at all, or the homepage loads while the admin panel won't open and every product page 404s.
Pass criteria: deployed on a server with zero connection to the provider, every front-end and back-end function works normally.
Test 2: Check whether the data is complete
Some source code does run — but it's an empty shell. Product data, articles and customer inquiries all live in the provider's database, and what you received is just the code.
Your acceptance checklist needs a line that reads: "Deliverables include all content data." Check against these points:
- Is the text and imagery of every product page included?
- Are all uploaded files (images / PDFs) included?
- Is the admin account handed over to you (and can you change the password)?
Test 3: See whether the handbook lets a third party take over
A genuinely complete delivery has three components: source code + data + deployment handbook. The handbook passes one test: can a person who knows nothing about your company get the website running on another server just by following it?
If not, the delivery is a "semi-finished product" — whenever you want to switch providers or manage it yourself later, you'll have to go back and beg them.
None of this counts unless it's in the contract
All three tests shouldn't rely on the other side's conscience — they rely on the contract. Write this into the agreement at signing:
> Deliverables include complete source code, all content data, and a deployment handbook; the delivery must support independent deployment and operation outside the provider's environment.
The ones who dare write it in are making a real delivery. The ones who don't — you know the deal.
Our own rule: the three-component package is delivered at signing, and if you stop renewing, the website is still yours. This isn't nobility — it's just how things should be done.
Not sure whether what your provider gave you is real source code? Send it over and I'll take a free look — a 3-minute video will give you the answer.
*Follow WrenchSite on WeChat: reply 【Audit】+ your industry + website link, and receive a personal diagnosis video within 48 hours.*
