A furniture company’s website and a machine manufacturer’s website are not made of the same pages; their customers search for them with different words and ask for quotes in different ways. These pages describe what a website or app needs in each industry, where it is most often built wrong, and how we build it.
01Industries
Collection and catalogue structure, dimension and material data, showroom and dealer pages, quote and WhatsApp requests.
Product families with technical specs, datasheet downloads, application and sector pages, quote forms and a multilingual structure for export.
Product data and variants, category and filter structure, stock between shop and site, product feeds and the campaign calendar.
First-release scope, store review, privacy and support pages, account deletion, backend and admin panel.
Doctor and treatment pages, appointment requests, branches and local search, health advertising and patient data rules.
Room and facility pages, booking-engine connection, pages in the guest’s language, tour and activity pages, searches from abroad.
Project pages, unit types and floor plans, sales status, sales-office enquiries, construction progress and project-based advertising.
Programme and course pages, term and branch details, pre-registration forms, separate content for parents and students, search and ads timed to enrolment.
A menu page written as text, reservation links, branch and location pages, Instagram and local search.
Practice-area and team pages, articles with author and date, contact forms that ask for little, and copy that respects professional rules.
Service and specialist pages, a gallery of real work, appointment links, Instagram and neighbourhood searches.
Transport-mode and route pages, quote forms that ask for load details, a tracking entry linked to your system, and B2B search.
Vehicle listing pages, service booking requests, parts catalogues searchable by vehicle and city-level local search.
Collection and season structure, size charts and colour-size variants, wholesale versus retail, manufacturer catalogues.
Weekly class timetable, trial-class requests, membership and package pages, trainer and branch pages, neighbourhood-level local search.
Product, fee and security pages, iOS and Android app, admin panel, privacy texts, rule-bound advertising.
02What changes
03Common questions
Yes. These pages exist to explain up front how needs differ by industry, not to draw the boundary of where we work. Use the contact form to tell us about your business and the site or app you have today; we will discuss what is needed in the first conversation.
Our live work is on the Work page. Where an industry page has live work of ours, it links to it; where it does not, the page describes what such a site needs and how it is built. Either way, we start by writing down with you what the site has to do.
No. The industry pages show what we build and how, but the scope and proposal are prepared separately for each job. Two companies in the same industry can differ widely in product count, language needs and the systems they use.
We build the site so that it can be set up in line with the known rules: consent checkboxes, where the information texts sit, which data a form asks for and why. The legal content of those texts and the compliance assessment remain the responsibility of you and your legal adviser.
Rufy Studio
Add the address of your current site or app, if you have one.