Product and Website Design for 500 Global Portfolio Companies

A buyer may need to understand the offer before a user can experience it. Those can be different people with different questions. Looking at the website and product together helps identify where design attention belongs.

Use these example situations to frame your priorities. This is our proposed planning approach, not an assessment of your company or an official 500 Global framework.

Connect the customer, the website and the product

If your team is…	Clarify the audience	Check the website	Check the product	A possible first scope
If your team is…Introducing the product to a new buyer role	Clarify the audienceWho evaluates, buys and uses it?	Check the websiteDoes the page explain that buyer's use case?	Check the productCan the intended user complete the related task?	A possible first scopeOne use-case page and its connected workflow
If your team is…Moving from founder-led demos to self-serve evaluation	Clarify the audienceWhat must a prospect understand without your explanation?	Check the websiteAre the offer and next step clear?	Check the productWhat setup comes before the first useful action?	A possible first scopeAn entry page and a selected first-use flow
If your team is…Preparing for a named additional market	Clarify the audienceWhat differs, and what evidence supports it?	Check the websiteWhich terms, proof or offer details need review?	Check the productWhich content, formats or workflow assumptions need review?	A possible first scopeA bounded page or flow using your market inputs
If your team is…Adding a feature to an established product	Clarify the audienceWhich customer problem does it address?	Check the websiteIs the capability described accurately?	Check the productDoes its interaction fit existing patterns?	A possible first scopeOne feature journey and its website explanation

The discussion may lead to product design, website design or a connected scope. Both services are available independently.

Nomicam: a studio-owned product

Nomicam is Gestures Studio's own AI photo editor. Its public presentation connects the promise of creating and editing photos with a sequence: choose a template, add a photo and refine the image.

It is a useful example to inspect when considering how a product explanation relates to the actions in an interface. It is our own product, presented here as general work rather than a 500 Global client reference.

Explore Nomicam, or see selected collaborations across products and websites.

Define the role and task before choosing the screens. A team administrator inviting colleagues needs different information and controls from a person working alone.

Product design can cover the selected journey, navigation, interface hierarchy and reusable patterns. Agree which states matter, including permissions, empty views, errors and completion. A prototype can make a particular interaction easier to review.

For an existing product, bring customer questions, support themes or observations where available. Our guide can help you review the product journey before choosing changes. Research recruitment and user testing need their own agreed scope.

Explore product design for your team's next workflow.

Give each priority page a decision to support: what the product does, who it serves, how a use case works or what happens after someone requests a demo or starts a trial.

Website design can include information architecture, priority page layouts, art direction, responsive behavior and interaction direction. Real product material helps connect the explanation to what someone will encounter after the next step.

Define the page list and the people responsible for factual content and copy approval. Copywriting, translation, CMS setup, development and publishing are agreed separately from the design scope.

Explore website design around your buyer's questions.

Start with the particular customer and market you have chosen. Bring what you know about terminology, buying decisions and product requirements, and identify the assumptions that still need checking. We can discuss the resulting page or workflow design. Translation and local-market expertise require separately defined responsibilities.

Illustrative scenario: from individual users to teams

Imagine a SaaS product that serves individual users and is now being considered by team managers. Its website still explains personal use, while the product may need invitations and role assignment.

A first scope could connect one team-use page with the invitation flow. The page answers the manager's questions about team use; the flow shows how a colleague joins and receives the right access. Engineering input establishes what permissions the product can support.

This is a hypothetical planning example, not a client project or a tested result.

What to bring to the conversation

1. Your product and website URLs.
2. Your current customer and the customer you want to serve next.
3. One important task the product should support.
4. The page or message that introduces that task to buyers.
5. Customer questions, support themes or analytics, if available.
6. Existing product, brand and engineering materials.
7. A decision owner, technical dependencies and any target date.

These help the discussion. You can start a conversation without a completed research report or analytics setup.

First identify the gap between the buyer's expectation and the intended product task. Then choose the pages or flows, review points and deliverables. Assign the inputs and implementation work before design begins.

Agree the work, the inputs and the handover

Work area	Possible design output	Responsibility to agree
Work areaCustomer and use case	Possible design outputA page or flow shaped around the selected role and task	Responsibility to agreeWho supplies customer evidence and approves assumptions
Work areaWebsite	Possible design outputAgreed structure, page layouts and responsive direction	Responsibility to agreeCopy, translation, CMS, development and publication
Work areaProduct	Possible design outputSelected workflow, interface states and components	Responsibility to agreeData, permissions, technical feasibility and engineering review
Work areaReview and handover	Possible design outputAgreed files, notes and review sessions	Responsibility to agreeFile access, ownership, user testing and implementation acceptance
Work areaBuild and operation	Possible design outputAny separately scoped development work	Responsibility to agreeIntegrations, functional testing, release, external costs and maintenance

For a website project, prepare your website redesign brief to organize the pages and inputs.

You can cancel anytime; confirm the applicable billing and cancellation arrangements before starting.

These are Gestures' studio plan rates. Deliverables and any development work are defined for the engagement.

Tell us who the product serves today, who you want to serve next and where the website or product needs attention. Send your URL, first design need and any target date. We can discuss the work and whether an engagement is a suitable fit.

Prefer email? Email us, or discuss your product and website scope.