50. Website production created from information design
If you start with design, you will almost certainly go off track. First, solidify the information architecture and create the site from the "structure" where inquiries arise.
The success or failure of website creation is determined not by design, but by "information architecture." Information architecture is not about arranging pages, but about deciding "what," "where," and "how to present" information according to the order in which customers compare and evaluate. In B2B manufacturing, if the pathway from entry (search intent), exploration (in-depth investigation), comparison (selection criteria), approval (decision-making materials), to consultation (CTA) is not designed, inquiries will not occur even if there is traffic. In this service, we solidify the information architecture as a "blueprint" before starting production and construct the entire site with a consistent flow. As a result, rather than being confused after creation, we can confirm the winning strategy before building. ■ Provided Content (3 points) Information Architecture (Blueprint of the site) (Sitemap/Page roles/Flow) Content Design (What to say: Appeal axis/Comparison axis/Basis/FAQ) Production (Design/Implementation/Operational design) Deliverables: Information architecture document + complete site (Wireframes/Design/Implementation/Publication) *Please share the current URL (or materials). We will first diagnose "where you are stuck" structurally.
basic information
■Provided Content Information Design (Overall Structure) - Entrance: By issue/use/technology (container for search intent) - Navigation: Products → Case Studies → FAQs → Materials → Consultations (deep dive pathways) - Comparison: Selection criteria/comparison axes/differences from other methods (deciding factors) - Approval: Materials for decision-makers (risks, systems, guarantees, cost justification) - CTA: Consultation permission type → Estimate → Quotation (staged approach) Clarification of Page Roles (Preventing Confusion) - Fix the purpose of each page (what to make the reader do after reading) - Integrate pages with overlapping roles to reduce update burden Content Design (What to Say) - Extracting and verbalizing strengths - Terminology translation and simplification - Case study design (reproducibility) - Structuring FAQs (also serves as a foundation for AI responses) Operational Design (A Stable System) - Templates, categories, input rules - Update guidelines that ensure quality remains consistent even when personnel change ■Deliverables Information Design Document - Sitemap/page role list/navigation diagram/category design Wireframes (for key pages) Content Design (necessary elements, headings, rationale, CTA) Design (top + lower-level templates) Implementation (CMS/responsive/basic SEO) Publication and initial measurement setup (as needed) Operational Guide (templates, input rules)
Price information
3.5 million yen to 12 million yen (varies based on scale, database/search, and migration volume) - Small scale (up to 15 pages, focus on information design): 3.5 million to 5 million yen - Standard (up to 30 pages, including comparison/approval/FAQ): 5 million to 8 million yen - Expanded (product database, search, multilingual, large-scale migration): 8 million yen and above * "Estimate required" notation is also acceptable (to be confirmed based on requirements)
Delivery Time
Applications/Examples of results
■Concerns The design is beautiful, but inquiries are not increasing. Unable to decide what pages are necessary, causing production to stall. There are many products and technologies, and information is scattered. Stuck in comparison and internal approval, not progressing to negotiations. Updating causes the whole structure to collapse (no operational premise). ■Approach Pre-sharing: Current URL/product list/sales materials (as much as possible is okay). Design phase: Finalize information architecture (blueprint of the site). Production phase: Wireframe → Design → Implementation → Testing. Publication: Migration and release (staged release as needed). Post-publication: Improvement (optional monthly support available). ■Uses Increase in inquiries (creating from the blueprint of the flow). Advancement of comparisons and internal approvals (preparation of decision-making materials). Structure that can be updated (reduction of operational burden). A site where improvements can circulate (measurement premise). ■Examples of Achievements (Company name not required format) Precision machining × 80 employees × scattered pages → Improved navigation and inquiries through category design. Industrial equipment × 200 employees × lost orders due to comparisons → Improved win rate by adding selection criteria pages. Chemical materials × 500 employees × updates causing collapse → Standardized quality through template operation.
Recommended products
Distributors
A site that is just cheap ultimately increases costs and risks." We propose web development that maximizes business results while thoroughly addressing essential requirements. Are you creating a website like this? - It seems that the websites of competitors look better, but you don't know why. - Every update incurs additional costs, and before you know it, expenses have ballooned beyond expectations. - While the appearance is nice, it ignores laws and industry-specific rules, leading to complaint risks... - You want to attract customers and inquiries, but the production company only talks about design. - As a result of choosing a production that is simply cheap, you are overwhelmed with trouble handling and can't focus on your core business. Point 1. Avoid troubles with a design that has no "gaps or omissions." 2. Minimize operational costs with a design that assumes in-house updates. 3. Planning power that pursues business results. "Is the initial cost a bit high?" But in the long run, it's safe and cost-effective. We have prepared a plan to truly deliver results "correctly.