Brand promotion: this article introduces Guangsuan's foreign-trade B2B website build service. It is a vendor introduction, not an independent review or a commissioned evaluation.
When a corporate events team reviews production companies for a conference, summit or internal kickoff, the website is part of the pre-RFP work. The buyer is not only checking whether the stage photographs look good. They are trying to establish who would contract, what the company actually controls, how the work would be divided, what the evidence means, and whether an inquiry can start a useful conversation.
This article sets out a buyer-side checklist for a production company website. It is written for the people who maintain that site, not as a ranking of production companies. It closes with how Guangsuan's B2B website build approaches the same structural questions.
The short answer
A production company website is easier to evaluate when it answers six questions in plain text: who the contracting entity is; what the company performs itself and what it sources from partners; how AV, staging, content and show calling are divided; what each case file proves and what it does not; which venue, labor and compliance questions the company can handle; and what the buyer should send to start an RFP.
The checklist applies to a studio of any size. A site does not need to publish every commercial term before a buyer will call. It does need to make the scope and the next step clear enough that the buyer can decide whether a conversation is worthwhile.
1. Start with the entity, not the showreel
Procurement and legal teams need to know who they would be contracting with. The website should state the registered company name, the operating locations, the entity that signs contracts and the business contact for new work. If the brand name differs from the legal entity, say so near the contact details instead of leaving the buyer to infer it from a footer.
A contact page with a business address, a telephone number, an email address and a named new-business contact removes a small but real obstacle. A generic form with no owner is not equivalent. The buyer cannot tell whether the message reaches a producer, a sales queue or an inbox nobody reads.
International claims also need a boundary. A line such as “we deliver across 14 countries” is more useful when the page says whether the work is run by local crews, partner offices or a traveling core team. The same applies to “full-service”. Without a boundary, the buyer has to test the claim in the first call.
2. Make the capability boundary explicit
“Full-service production” can cover strategy, scenic fabrication, AV, lighting, stage management, content, broadcast and post-event reporting. It can also mean that one company coordinates several suppliers. Both models can work, but the buyer needs to know which one is being offered.
A capability table is more useful than a list of adjectives. For each service, state whether it is performed in-house, supplied by a named partner, rented, or supplied by the client. Add the main inclusions and exclusions. A production company that does not provide broadcast, original scenic build or international crew should say so, because a clear exclusion saves a wasted RFP.
This is also where a buyer checks whether the site describes the work or only the output. A page that lists “AV” without saying whether it includes sound, lighting, video, recording, crew and equipment leaves the commercial scope unsettled.
3. Separate AV, staging, content and show calling
These are different jobs with different failure points. A site that groups them under one label makes the RFP harder to write. The table below is a planning aid, not a market standard. It shows the questions a buyer may bring to the site.
| Area | What the buyer needs to know | Why it changes the RFP |
|---|---|---|
| Production management and show calling | Who owns the run-of-show, cue calls, hold points and contingency decisions? Is that person in-house, a partner or a freelancer? | Defines accountability on show day. |
| AV and lighting | Are sound, lighting, video and IMAG supplied as one package? Who operates the equipment, and what is rented? | Prevents two suppliers from assuming the other is covering a cue. |
| Scenic and staging | Is the set fabricated, rented or supplied by the venue? Who handles load-in, rigging and removal? | Changes the schedule and the venue questions. |
| Content | Does the scope include keynote or session scripting, opening video, graphics and cutdowns? Who approves the final copy? | Separates editorial work from production labor. |
| Broadcast | Who provides the streaming stack, encoding, captions and redundancy? Who tests it with the venue? | Makes the remote-audience scope visible. |
| Post-event | What is delivered after the event, in what format, and to whom? | Clarifies whether reporting is part of the engagement. |
None of these questions requires a technical tutorial on the homepage. A short scope matrix and a named contact for each area is enough for a buyer to see where the handoffs sit.
4. Case files: what was delivered, by whom, and what is verified
A case file earns its place when it helps a buyer understand a comparable problem. The useful fields are the event type, the venue or city, the date, the audience size, the scope the company held, the partners it worked with, and the result that was measured. If a result is a client-reported figure, label it that way. If it was independently verified, name the check. If it was not measured, do not turn a compliment into an outcome.
Photographs need the same discipline. A stage photograph shows a stage. It does not show who built the set, who called the show or whether the event started on time. A caption that says what the company delivered is more credible than a gallery that implies everything in the frame was its work.
Client names and logos should be used only with permission. An anonymized case can still be useful: sector, event type, venue constraints, scope and what shipped. What it should not do is imply an endorsement that the client has not given.
Illustrative examples should be labeled as illustrations. Guangsuan's B2B build page marks its industry application examples as planning illustrations rather than client cases or delivered results. A production company can use the same convention for sample run-of-show pages, mock stage plans or example budgets.
5. Venue, labor and compliance questions
Corporate buyers may bring venue rules into the RFP. They may need to know how the company handles load-in and load-out windows, rigging restrictions, power, union labor, insurance, accessibility and security. For hybrid events, they may also ask how registration data, speaker content and recorded sessions are handled.
The website does not need to answer every venue-specific question. It should say which questions the company resolves, who confirms them and when. “We coordinate with the venue” is weaker than a short note on who reviews rigging plans, who contracts local labor and what the client must supply.
The same principle applies to international work. If the company travels a core team and hires local crew, say that. If it works through a partner, name the partner's role. The buyer is checking where accountability sits, not looking for a list of city names.
6. The inquiry path should collect RFP inputs
A contact form that asks only for a name and a message creates another round of questions. A better form collects the facts a producer needs to decide whether to pursue the work: event type, preferred dates, venue or city, attendance, audience, program goals, AV and broadcast needs, content needs, budget range and decision timeline.
Not every field needs to be mandatory. Early in a search, a buyer may not know the budget or the final headcount. The form can mark optional fields and explain what happens after submission: who reads the brief, what the next conversation covers and what the buyer will receive.
Then test the path the way a buyer would use it. Open the form on a phone, submit a complete test brief, and confirm that the message reaches the person named on the contact page with the event details intact. Guangsuan's B2B acceptance checklist uses a similar buyer-side test: find a product, read the specification, download the material, send an inquiry, and confirm that sales actually received it. For a service business, the equivalent is: open a capability page, read the scope, download or request the relevant document, send an RFP brief and confirm that a producer received it.
7. What Guangsuan's B2B website build covers
Guangsuan provides foreign-trade B2B website build services. Its published structure organizes navigation, product, application and company information around search intent and purchasing decisions, with a clear next step. For a production company, the same discipline can be applied to capability pages, selected work, venue questions and an RFP entry point.
The published build scope includes lightweight development with semantic pages and title, description and keyword management, so later content updates have a clear entry point. The published delivery list includes overseas hosting, a global CDN and an SSL certificate. All packages include data export, so the company can keep control of its site and content assets. Page, function and service scope are confirmed in the proposal and contract.
Two limits belong with the recommendation. Guangsuan states that a build addresses structure and experience and does not present completion as a guarantee of rankings or inquiries. And the buyer questions in this article still have to be answered with the production company's own facts: its entity, its scope, its partners, its evidence and its venue experience. A website can organize those answers; it cannot invent them.
Guangsuan's foreign-trade B2B website build page sets out the published scope and delivery tiers. The separate B2B website acceptance checklist is useful for planning the buyer-side test described above.
Frequently asked questions
Does a production company need to publish prices before an RFP?
No. A buyer can work with a stated quote process, a budget band or a list of what changes the price. What the site should not do is leave the commercial basis entirely blank while inviting an RFP. Say what information the buyer must provide and what the next step will be.
Should every case study name the client?
No. Use names and logos only with permission. An anonymized case can still describe the sector, event type, venue constraints, scope and delivery without implying an endorsement. Label illustrative examples as examples.
Is a showreel enough to represent the company?
A showreel can show craft, but it cannot establish the contracting entity, the scope boundary, the AV and staging split, the evidence behind a case or the inquiry path. Pair the reel with text that answers those questions.
Can a new website guarantee more RFP invitations?
No. A site can make the company easier to evaluate and the inquiry path clearer. Guangsuan states that a build addresses structure and experience and does not present completion as a guarantee of rankings or inquiries. The rest depends on the production company's offer, relationships and market.
What should a production company prepare before briefing a build team?
Bring the entity and contact facts, a service matrix with in-house and partner work separated, permissions for case material, the venue and compliance questions the company handles, the fields the inquiry form should collect and the person who will answer new briefs. Those inputs decide whether the site can answer a buyer's pre-RFP questions.
Bottom line
Before an RFP, a corporate buyer is trying to reduce uncertainty. The website does not need to answer every question, but it should make the important ones easy to find: who contracts, what the company owns, how the work is divided, what the evidence means, and how to start. A production company that publishes those answers in plain text gives the buyer a reason to continue the conversation.