Show the factory
Production lines, equipment, quality checks and documented projects demonstrate capability.
← All industries
BIG FISH · Manufacturing
Websites for manufacturing
Corporate websites, technical catalogues and dealer portals for manufacturers and engineering businesses. Present production capabilities, support equipment selection and turn an enquiry into an agreed specification.
BIG FISH / INDUSTRIES
01Select equipment
02Build specification
03Check capacity
04Request quotation
Design × industry workflow
FROM WEBSITE TO SERVICE
Clear for customers.
Useful for your team.
An engineer’s catalogue
Filter by technical parameters, compare variants and find model-specific documents.
A buyer’s workspace
Specifications, account terms, order milestones and shipment documents.
INTERACTIVE EXAMPLE
Your workflow.
Try it in action.
Try the journey “Select equipment → Build specification → Check capacity → Request quotation”. Change the inputs to see when the next step becomes available.
An educational model with fictional companies, values and rules. All actions stay in the browser; no data is submitted. This illustrates a possible solution, not a connected system or a client case study.
INPUT
WORKFLOW RESULT
Enable JavaScript to use the example.
WORKFLOW
Every step connects
to an outcome.
01
Select equipment
02
Build specification
03
Check capacity
04
Request quotation
| Layer | Responsibility |
|---|---|
| Website and interface | Presents the product, explains conditions and guides the action. |
| Application server | Checks permissions, valid transitions and repeated requests. |
| Business systems | Confirm authoritative data within the agreed exchange scope. |
| Responsible people | Make decisions requiring professional assessment and approval. |
BIG FISH · MANUFACTURING
Complex equipment. Clear choices.
We design manufacturing websites and equipment catalogues around engineering decisions. Dimensions, materials, tolerances and compatibility come before sales copy. Component photographs, diagrams and specification comparisons help buyers define exactly what they need.
In a dealer portal, we show the approved configuration, production stage and order documents. The interface connects a quotation request to manufacturing and delivery, making the next action clear to both the account manager and the buyer.
SOLUTION GUIDE
Behind an interface
that works.
Design decisions, data, permissions and acceptance checks. Exact business rules and integrations are defined for your organisation.
Manufacturing / 01
Design and the user journey
Equipment buyers need more than attractive photography. Show the product in context, then explain power, materials, operating media and available variants. Factory images, manufacturing details and completed applications establish the scale of the business. On mobile, specification tables remain readable and the enquiry action follows the chosen configuration.
During design, document representative screens and expected user actions. For each decision, identify what editors maintain, what comes from another system and who owns its freshness.
Acceptance check: A first-time mobile visitor can find the relevant service and next step.
Manufacturing / 02
Workflow and states
The workflow connects these stages: Select equipment → Build specification → Check capacity → Request quotation. Each transition has an owner, inputs and a visible result. Before implementation, map the normal journey, correction, cancellation and repeated actions. Interface status must represent a confirmed state rather than a button click.
Acceptance check: Returns and retries preserve input without duplicating the result.
Manufacturing / 03
Data model and documents
A product has a series, item code, variant and technical parameters. Documents belong to a model revision; a previous variant’s datasheet must not appear under the new one. Separate finished stock from made-to-order capacity. Save the configuration, quantity and terms revision in the quotation request so later catalogue updates cannot silently alter an approved specification.
Acceptance check: Reference data changes do not overwrite an agreed document.
Manufacturing / 04
Roles and access boundaries
Public visitors see technical details and general documents. Dealers see their own prices and organisation’s orders. Engineers approve configuration, account managers approve commercial terms and production staff confirm feasibility. Changes after approval return the specification for review. Restricted drawings are available only to authorised project participants.
Acceptance check: A different organisation cannot retrieve a restricted file by direct URL.
Manufacturing / 05
Integrations and data ownership
Product codes and stock may come from an ERP, while technical descriptions come from a catalogue system. Assign one authoritative source to each field. Send the complete specification to CRM with the enquiry. If an upstream system is unavailable, retain a pending state instead of displaying invented stock or an unconfirmed delivery date.
Acceptance check: An unavailable source never appears as a confirmed success.
Manufacturing / 06
Errors, retries and recovery
For long operations, acknowledge receipt and retain the result identifier. Retrying after a connection loss must not create a second record. Separate user-correctable errors from cases requiring a specialist, preserving input under the agreed handling rules. Design empty, loading, forbidden and unavailable states before implementation rather than after launch.
Acceptance check: A repeated event does not apply an operation twice.
Manufacturing / 07
Content, search and discovery
Organise pages around product families, applications and meaningful selection criteria. Separate useful landing pages from endless filter combinations. Keep discontinued item pages with clear replacement guidance. A credible quotation journey explains the supply scope and next step rather than promising a price that has not been confirmed.
Acceptance check: Search and filters lead to useful pages without endless duplicates.
Manufacturing / 08
First release and evolution
The first release covers the complete journey from “Select equipment” to “Request quotation”, supporting pages and editable fields. Test mobile views, roles, forms, documents and integration failures in staging. Save the previous state and define rollback before switching. Handover includes editor instructions, the exchange design and a checklist for future releases.
Acceptance check: Recovery has been tested on a copy, and editors can maintain fields independently.
FAQ
Before we start
Can we launch the website before the portal?
Yes. Start with structure, design, content and a complete enquiry journey. Design catalogue entities and identifiers with the future portal in mind to avoid another data migration.
Can you connect our existing systems?
We first inspect the supported interface, permissions and test environment. Then agree data scope and system responsibilities. If no suitable API exists, assess an alternative and its limitations separately.
What determines cost and timing?
Page types, content volume, roles, integrations and first-release scope. Discovery produces a structure, prototype and staged estimate. This page’s demonstration is neither a finished system nor a fixed-price promise.
Let’s discuss your industry project.
Start with business objectives, website structure and the workflow that needs a better experience.