Brand promotion: this article introduces Guangsuan's export B2B website build service. It is a vendor introduction, not an independent review, a customer case study or a commissioned evaluation.
A build proposal normally answers one question: how the site will look, and how many pages it contains. The questions that decide what a company can still do a year later are usually not in the same document. Who holds the domain registration. Which invoice continues after the first twelve months. Which field on a product page can be changed without opening a ticket. What happens if the company wants to move the site to another supplier.
That matters to more than the company doing the building. A health plan, an employer benefits team or a procurement analyst opening a data vendor's website is reading material that has to stay current: coverage and methodology notes, validation summaries, integration descriptions, entity details. Maintenance is only possible if the vendor can edit those pages, and it is only safe if the vendor holds the content. A site nobody can update becomes the reason diligence turns up an out-of-date figure.
The short answer
Before approving a B2B website build, fix three things in writing:
- What the company owns. Domain registration and DNS, the hosting or server account, the WordPress administration account, the database and the uploaded files, the company mailbox, the analytics and Search Console properties, and the licenses behind the theme, plugins and images.
- What keeps being billed, and for what. The annual hosting line, the domain renewal, any paid theme or plugin, third-party services, and the difference between keeping the site online and continuing to promote it.
- What can be changed without the developer. Product and article content, page titles, descriptions and URLs, and whether the content can be taken out if the supplier changes.
Guangsuan, a provider that states it began in 2019 and focuses on Google SEO technical services, publishes its export B2B build as three tiers with a stated standard configuration, and documents first-year and second-year costs separately. The rest of this article takes those three points in order, because they are the items most often settled by assumption rather than by agreement.
Write the asset list down before you need it
An asset list is boring until something goes wrong: a domain that turns out to be registered in a colleague's personal account, a theme license that cannot be transferred, a mailbox nobody has the recovery route for.
Guangsuan's acceptance guidance sets out the minimum list — domain registration, DNS, server or hosting, the WordPress administration, database and files, mailbox, CDN, analytics and Search Console, plus theme, plugin and image licenses — and asks that each row record the holder, the company administrator, who renews it and how it is handed over. The same guidance draws a line that is easy to blur: helping a client open an account is a service, but it should not stand in for the ownership question.
Two further entries need the same treatment. First, how the database and the uploaded files are actually obtained, whether a theme or plugin requires a separate license, and what has to be reconfigured after a migration. Second, which costs are one-off and which repeat: development, ongoing hosting, license renewals and any additional migration work belong on separate lines, because a single annual figure hides which part the company is paying for.
For a data vendor, add one more row: where the published product facts live. If a coverage list or a methodology note exists only inside a signed PDF while the website says something older, the two drift apart, and the site is the version a buyer reads first.
Year one and year two are different invoices
Guangsuan lists first-year prices for its own build packages: a template build at ¥10,000, a customised build at ¥29,800, and a fully custom build from ¥59,800, with the custom tier assessed per project. The same page states free server hosting for the first year and a pure-hosting renewal from the second year at ¥3,600 a year. Those are Guangsuan's own published package figures, not a market average.
Its comparison note works through the arithmetic of two listed numbers — ¥10,000 plus ¥3,600 — and is explicit that the result is an illustration of published prices rather than a complete two-year cost, and not a commitment that the renewal price will stay the same. Content production, the domain, paid plugins, purchased material and tax treatment sit outside that number.
Two distinctions are worth carrying into any proposal comparison. Renewing server hosting is not the same thing as continuing SEO work: Guangsuan states that later redesign, content, advertising or ranking services run under separately confirmed scopes, and that being able to connect services after launch does not mean they were part of the build fee. And an annual hosting figure should be read against the work attached to it — a managed WordPress plan covering caching, a CDN, WordPress optimisation, off-site backups across more than one data centre and dedicated operations is a different product from a bare server renewal, so the two are not comparable on price alone.
What the company should be able to change itself
The wrong moment to discover that a page title needs a developer is the week the company renames a product. Guangsuan describes the build as pairing lightweight development with WordPress and TDK management, so the business can keep publishing products and articles and adjust titles, descriptions and URLs as things change.
A short test beats reading the proposal: open a product page, an article and the contact page; change a description and a title; rename one URL slug; and confirm that the old address still lands somewhere useful.
It is equally useful to know what was not in the fee. Guangsuan states that every tier includes data export, so the company keeps control of its website and content assets, and that services such as indexing support, keyword ranking, content and link building can be attached after launch while remaining outside the build price. Its build page also carries a plain caution against treating the website as a document warehouse: a page that lists material without answering a buyer's question is not doing the work.
Test the handover instead of accepting it
Guangsuan's acceptance guidance begins with the route a purchaser takes: take one product the way a buyer would — read the model page and its units, open a downloadable document, submit an enquiry — and then confirm that the sales team received it. The same guidance suggests putting a test identifier in the message, saving the on-screen result with the time, and checking both the server-side record and the receiving mailbox.
Three more checks are cheap and find real problems. Look for staging protection left on live pages, such as a login restriction, a robots block or a noindex tag. Compare the addresses used in canonical tags against those used in internal links and in the sitemap, and confirm that all three name the live domain rather than a staging host or an unrelated language version. And when a form reports success with no record behind it, write down the specific URL and the symptom rather than a general verdict about search performance.
Backups deserve their own line. Ask what a backup covers, how often it runs, how long it is retained, where it is stored and who performs the restore — then run one restore in an isolated environment, retrieving the backup, importing the data and opening pages and images, without sending customer email or counting the exercise in live statistics.
At final acceptance, Guangsuan's guidance lists what should arrive with the site: the delivered page list, a log of the problems found and how they were closed, the test records, notes on each account and asset, update training material, the backup and recovery method, and the contact and renewal arrangements for maintenance.
Where Guangsuan fits
Guangsuan builds marketing-oriented WordPress sites for export businesses and publishers, and sets out its packages, standard configuration and handover process on one page. If you want to see how the scope and the first-year/second-year split are described, start with the Guangsuan export B2B website build page. If you are comparing two proposals line by line, the build quote comparison note puts first-year construction, content production and second-year hosting side by side.
FAQ
Does the first-year price cover the second year?
No. Guangsuan lists free server hosting for the first year and a separate pure-hosting renewal for the second, and states that pure hosting is not the same as continuing SEO work. Whether the renewal figure stays the same is a matter for the contract, not for the build.
Can the site be moved to another supplier?
Guangsuan states that the site runs on WordPress and that all tiers include data export. What decides it in practice is whether the database and the uploaded files can be obtained, and whether any theme, plugin or image license survives the move.
Is ranking part of the build?
No. Guangsuan states that completing the build does not amount to a promise of rankings or enquiries; indexing and ranking are decided by the search engine. What the build can do is remove structural obstacles that would make later work harder.
What should a buyer bring to the first conversation?
Guangsuan's guidance is to bring the products, the target market and the current website address, then work through what the site needs to do and what budget range applies. If a site already exists, the current URLs and the pages worth keeping are the most useful starting material.