Turn your design into a website
Build your approved design with Payload CMS, Next.js and agreed content fields your team can edit.
Explore Payload CMS: Turn your design into a websiteYou lead the client project. We handle the agreed development behind the scenes: Payload CMS and Next.js websites, landing pages or migrations of existing websites. Working remotely in English and German.
White-label web design means your agency commissions Con Radius Design for a defined part of a client project. We build the agreed website under your agency brand. Branding, contacts and approvals are agreed before work starts.
This suits agencies that lead design and client relationships and need development support. We review the actual brief before you commit scope and timing to your client.
A defined project or additional development capacity: the work starts with suitable requirements and an agreed scope.
Build your approved design with Payload CMS, Next.js and agreed content fields your team can edit.
Explore Payload CMS: Turn your design into a websiteWe review the source system and the move to Payload CMS and Next.js. Content, URL changes and the existing or new design are planned around the agreed scope.
Example: Webflow migration: Migrate an existing websiteCampaign landing pages, additional pages or functions as a defined package, with search fundamentals considered in planning.
Explore web design: Landing pages and extensionsClient contact and approvals. Your agency leads the project. Joint client calls are possible by agreement. One approval route prevents conflicting requests from reaching development without a decision.
Design and content. We agree who supplies designs, copy, images and translations and which tasks we handle. The responsible party approves specialist and legal statements.
Development and testing. Pages, features, device views and agreed contact journeys become part of scope and acceptance. Additional functionality or revision rounds are priced before they are implemented.
Handover and operation. Access, repository, content model and editor onboarding are agreed for the project. Hosting, external services, maintenance and ongoing SEO work have separately assigned responsibilities and costs.
This gives you a defined delivery scope for your client proposal. Partner pricing and a delivery date can only be confirmed after the brief has been reviewed.
These published projects show our work with Payload CMS and Next.js. They demonstrate technical delivery and are not presented as white-label commissions.
We agree a scope and an approval route. Timing depends on requirements, available inputs and development capacity.
Share the design status, page count, languages, required features and timing. For migrations, we review the existing site.
Define inputs, responsibilities, acceptance criteria and revision rounds. Our project proposal then becomes a basis for your client pricing.
We develop the agreed scope and share it for review. Feedback follows the agreed approval route; additional scope is discussed separately.
We hand over the agreed access and content. Launch, support and responsibilities after delivery are explicitly agreed.
Your agency leads the project. Before work starts, we agree whether we stay entirely behind the scenes or join technical calls. Communication and branding follow the agreed model; we do not independently approach your clients with additional offers.
Yes. You can provide approved designs, for example in Figma. We review pages, responsive states, functionality and the content model. If design elements or content are missing, we agree who supplies them before quoting. A design file alone does not define every development requirement.
By the agreed scope: pages, languages, features, migration, inputs and testing. You receive our proposal and set your own client price. Hosting, external services, ongoing support and later additions are discussed separately; there is no blanket partner discount promise.
We agree confidentiality, access and any reference use before the project starts. Partner projects are not used as public references without agreed approval. If you require a confidentiality agreement, we include that in preparations for the partnership.
Where useful, search fundamentals, content and SEO or GEO work can be included. Ongoing support has its own agreed scope. We distinguish technical delivery, published content and measured results; rankings and mentions in AI answers are not guaranteed.
Your designs or current website, required pages and languages, key features, target timing and your part in the project. Include who provides content and approvals and whether you need support after launch. We use this to identify questions, a suitable scope and next steps.
Share the design or website, pages and languages, features and target date. We will discuss which development approach fits your project.