Branding and customization

Every ProxyRequest subscription includes the customer dashboard and base brand styling. Additional frontend customization is available only with six- or twelve-month prepayment and is always scoped and quoted separately.

Delivery boundary

Area	Included with every plan	Separately quoted on 6/12-month terms
Product identity	Your product name, logo or icon, and primary colors	A unique visual system, new layouts, or a bespoke component library
Domains and links	Customer-facing domain plus standard contact, status, and documentation links	Non-standard domain architecture or a separate marketing site
Interface copy	Standard product copy with your identity and service destinations	Business-specific labels, content structure, or extensive copy changes
Workflows	Existing customer and reseller workflows connected to the managed backend	New pages, roles, purchase flows, reseller actions, or integrations
Maintenance	Supported dashboard releases and configured base brand values	Custom-code maintenance as defined in the quoted scope

Open full size

Base brand styling identifies the supplied product; structural or behavioral changes remain a separate customization scope.

1. 1Name, logo or icon, and the configured color system identify the customer product.
2. 2The existing account workflow remains connected to the managed backend.

Base brand styling process

1. Provide final logo/icon assets, brand colors, the product name, and domain ownership details.
2. Confirm contact, status, documentation, legal, and support destinations.
3. Confirm the standard customer-facing links and domain that belong to the base configuration.
4. We configure a review environment and share it for acceptance.
5. You verify identity, links, authentication, package display, purchase behavior, email ownership, and responsive layouts.
6. Accepted settings are promoted with the backend and customer-domain launch.

Supply vector logo assets where possible, plus square icon variants and exact color values. Do not send production passwords, provider credentials, API keys, or payment secrets in a branding document.

When custom development is the right scope

With a six- or twelve-month term, request a separate estimate when the work changes product structure or behavior: a unique design, new navigation, new account roles, a different purchase model, additional pages, business-specific reseller actions, a third-party integration that is not supported, or a separate marketing site. Custom development is not offered on the monthly term.

The estimate should state deliverables, acceptance criteria, dependencies, migration impact, release ownership, and ongoing maintenance. The subscription continues to cover the managed platform; it does not make an open-ended frontend project part of base brand styling.

Brand styling starts after inputs are final

Incomplete assets, unverified domains, changing copy, payment-provider review, or a newly requested workflow can move the launch date. Use the dashboard launch checklist to prepare the required inputs.