FAQ

Identity, visual content, web design and production preparation can share one scope. We start with what the launch actually needs, then agree on sequencing and approvals so that messaging, colours and files stay consistent across channels.

Send a short description of your business, audience, goal, deadline and available materials through WhatsApp. We clarify missing details and agree on deliverables, budget and revisions before detailed production begins.

Cost depends on content volume, languages, formats, functional complexity, photography, asset rights and review rounds. A proposal should specify included work, external costs and how additions are approved. There is no single price suitable for every project.

The schedule follows the agreed scope, available materials and review timetable. A compact identity differs from a multilingual website or a location shoot. We plan reviewable stages and explain how new requirements or delayed approvals affect delivery.

Yes. We identify what needs to remain recognisable: the name, mark, colours or other established elements. A refresh may focus on typography, applications and usage guidance. Changes to an existing logo require explicit approval.

A logo is one identifying mark. A visual identity defines its relationship with typography, colours, imagery and layout. That system helps a website, printed materials and social content remain coherent when produced at different times.

The proposal defines the delivery list, which may include print PDF, vector SVG, transparent PNG and presentation JPG. Source files and font licences are not automatically included. Sizes, bleed and production requirements are checked with the supplier.

These are separate scope items. We agree on image quantities or video duration, formats, processing, languages and licensed audio sources. Additional aspect ratios and subtitle languages require additional production time.

Yes, with separate language paths and appropriate layout direction. Brand names, terminology and phone numbers need review within each language. Specialist and legal content should be approved by the business owner or a qualified reviewer before publication.

Usually a responsive website can serve all three with layouts suited to each screen. Navigation, image sizes and content order can adapt while the URL stays stable. Device-specific sites introduce additional maintenance and need a clear functional reason.

A catalogue presents products and collects enquiries, for example through WhatsApp. A shop adds payment, inventory and order fulfilment. A WhatsApp button does not itself process payment or reserve stock; the expected workflow must be specified.

A content dashboard can be included for pages, projects and media. Image dimensions and draft publishing help maintain consistency. Editing permissions, backups and responsibility for operational updates should be defined as part of handover.

SEO supports discovery and understanding in search. GEO describes efforts to make information useful to generative answer engines. Both depend on accurate content, direct answers, appropriate sources and clear structure. Neither guarantees ranking or citation.

Useful service detail matters more than repetition: scope, deliverables, requirements and realistic answers. Repeated keywords or near-identical location pages offer little help to readers. Keyword planning should follow the audience, offer and available evidence.

Protected content is generally unavailable to public search engines. Before public launch, access controls, robots directives, noindex and the sitemap need review. SEO preparation can happen during development, but visibility measurement follows public availability.

No. Text enlargement, contrast and reduced-motion controls can help, but do not replace semantic structure, keyboard support, form labels and screen-reader testing. Any formal conformity claim requires an appropriate assessment of the complete site.

A supported installable website can be added to the home screen. It is different from an app distributed through Apple or Google stores. Offline features, notifications and camera access need separate scope and device-support checks.

No. A display model may contain details or wall thicknesses unsuitable for printing. Scale, mesh closure, material and orientation need review. Parts requiring accurate fit may need a physical prototype and revision after measurement.

We agree on approval stages and review rounds, preferably with consolidated feedback from one decision-maker. The agreement specifies usage rights, source files and licensed assets. A new direction after approval or extra deliverables requires a scope review.

Design, content and web work can be coordinated remotely through references and clear approval stages. We agree on communication language, time zone and delivery formats. Photography, printing and transport require separate location and supplier arrangements.