Clear answers

Tell us about your business, your audience and the outcome you want: enquiries, online sales or a simpler workflow. Add two or three example websites, any existing content and your budget or timing constraints. A short document is enough.

Yes. Describe a real situation: who has the problem and how they solve it today. We can separate the essentials from optional features and define a first step. You do not need a complete specification to start the conversation.

A website presents your business or enables purchases. A mobile app supports recurring tasks on a phone. SaaS delivers an online service with accounts and business workflows. Start with the actions your users need to complete, then choose the format.

A takeover starts with a review of the technology, available code, hosting, content and known issues. Send the website address and describe the difficulties. Technical access can then be shared through an agreed channel, never through a public form.

The quote breaks down the deliverables: pages or screens, design, features, integrations and content. Include the languages and tools you need to connect. A customer portal with several roles, for example, takes more work than a basic contact form.

The quote can contain two lines: one five-page package and seven additional pages. The price per extra page is stated in the quote. Booking tools, calculators or other custom features are scoped separately from a standard content page.

Depending on the project, allow for a domain, hosting, licences, maintenance and services such as email delivery or payments. Ask for one-off costs and subscriptions to be separated, with responsibility for payment stated. They are included only when the proposal says so.

The quote sets the payment schedule and terms; there is no single deposit percentage for every project. If you add a feature after approval, we clarify its cost and effect on the schedule before starting the extra work.

Home, about, services and contact are usually separate pages. A product page using an existing template does not necessarily count as a new design. The sitemap and included templates are listed in the quote so the scope is clear.

Mobile layouts are part of the planning: navigation, text, forms and buttons must remain usable on smaller screens. Key journeys are checked on the agreed screen sizes. Features specific to a phone may require additional work.

Prepare products, variants, prices, photos, stock and delivery rules. You also need payment methods and the commercial information to display. Product import quantities, integrations and payment provider fees are specified separately.

Yes, with the three versions included in the scope. Hebrew also requires checking right-to-left layouts, forms and mixed-language content. The quote specifies who writes, translates and approves each language, and which pages are included.

If you have them, share the source files, colours and fonts. Otherwise, visual identity can be scoped as part of the project. Designing a new logo and applying an existing logo to a website are different pieces of work.

We make a page-by-page list of required copy, images and translations. You can supply the content or include its creation in the quote. You still approve information about your business before it is published.

Yes, within the review stages and rounds stated in the quote. Group feedback by screen, explaining the issue and desired result. Adjusting a colour or spacing differs from changing the entire visual direction after it has been approved.

Design and printing are separate services unless the quote states otherwise. To prepare the files, provide the size and the printer’s specifications. Quantity, paper, finishes, delivery and production costs are agreed separately.

Choose one complete, useful journey, such as creating an account, submitting a request and tracking its response. We separate launch essentials from later additions. A smaller scope must still be usable, with access permissions and errors handled properly.

We check each tool’s integration options and required access. Specify which data should move, in which direction and how often. For example, creating an invoicing customer after signup. Third-party limits and subscription requirements need to be checked.

The quote should state whether account setup, listings, visuals and submission are included. Platform fees and account ownership are clarified at the start. Acceptance and review timing are controlled by the platforms, so technical delivery does not guarantee immediate publication.

List the roles and their actions: a customer sees their documents, a team member handles requests, an administrator manages access. We define visible data and allowed actions for each role. Invitations and revoking access also need to be planned.

The scope may cover titles, descriptions, page structure, internal links and technical crawl settings. An audit, regular articles and monthly monitoring are separate services. Ask for the actual list of included pages and tasks.

No. We can define actions and measure progress, but cannot guarantee a ranking. Tracking can cover relevant searches, visible pages and enquiries. Goals and metrics are chosen to fit your business.

Share the current page list and access to measurement tools if available. Work may include a URL inventory, a redirect plan and post-launch checks. This should be scoped before the old pages are replaced.

The quote specifies tasks, time allocation and deliverables, such as fixes, content recommendations or a report. Reviews distinguish completed work, observed results and next priorities. New content writing is included only when it is part of the agreed scope.

A typical project moves through scoping, content and journeys, design, development, acceptance testing and launch. Each stage has deliverables and approval points. A small website may combine stages; an app may progress through successive releases.

Consolidate feedback in the agreed channel through one main contact. For each point, name the page or screen, explain the issue and describe the desired outcome. Annotated screenshots and consolidated comments help avoid conflicting requests.

Missing content, unavailable access, late approvals and added features can shift milestones. The schedule identifies what is needed and who supplies it. When a dependency blocks progress, we review what can continue and adjust the timeline together.

Review copy and contact details, then test forms, links, languages and key journeys on desktop and phone. For a store, also check the basket, test payment and delivery. Acceptance criteria and the test environment are agreed before launch.

We clarify who owns the accounts, pays subscriptions and manages configuration. If you already have hosting, share its specifications so compatibility can be checked. Domain, hosting and maintenance are separate topics to cover in the proposal.

Maintenance covers agreed tasks such as updates, fixes or technical monitoring. Adding a booking module or a new workflow is a change to be scoped. The chosen plan specifies the period, included time and intervention arrangements.

Send the URL, steps to reproduce, expected result and a screenshot if useful. Include the device, browser and whether everyone is affected. Use the agreed support channel and do not include passwords or sensitive data.

Editable content, access and deliverables are listed during scoping: for example copy, images, source files or a handover guide. Training can be included. Rights and handover terms are those specified in your proposal, depending on the tools used.

Once your access is enabled, use the email address invited by the studio to request a sign-in link from the Client portal page. Check your spam folder too. If nothing arrives, contact your studio contact with the email address used, without forwarding your sign-in link.

The portal displays items shared with your account, not every internal studio document. A draft may not have been published yet. Ask your contact to check the document’s sharing settings and the email address linked to your access.

Send the studio the person’s name, work email and required role. Their access should be created with the appropriate permissions. Do not share your sign-in link: each member uses their own access, which can be removed when no longer needed.

Depending on what has been published and your permissions, you can view milestones, deliverables and project messages. When requesting a correction, identify the deliverable and the change you need. If something is missing, ask your contact whether it has been shared.