Clear answers before the next step.

Product support covers defects, regressions, and guidance for existing functionality included with your entitlement. Customization is new or changed behavior—workflow extensions, integrations, branding beyond configuration, or features not in the current product scope. Keeping them separate protects response expectations and pricing clarity. Describe outcomes when requesting customization; describe reproduction steps for support.

Customers create a portal account, verify marketplace purchase entitlement, and open product support tickets for entitled items. Purchase verification and support eligibility are connected to the relevant marketplace integration. Product support and paid customization are separate work types with different scopes. Include product version, environment, and reproduction steps per support guidance.

Launch is the start of operational ownership. Options include internal administration, product vendor support for entitled software, and RadialLeaf maintenance or improvement programs when agreed. Define hypercare windows, escalation paths, and who owns reconciliation for integrations. Documentation, runbooks, and training materials should transfer to your team. Without a named owner, software decays regardless of launch quality.

You can purchase eligible products through the RadialLeaf store with checkout, order confirmation, and portal access for downloads, updates, and invoices. Entitlement is tied to your portal account email. License terms and refund eligibility are described on the product page and in the legal policies. Marketplace purchases use separate verification flows—see knowledge-base guidance for Envato verification when applicable.

Yes. Suitable products can be adapted through configuration, custom modules, interface changes, reports, permissions, and integrations. The first step is a fit assessment to separate safe customization from changes that would be better handled as a custom solution. Bounded customization preserves upgrade paths; see the knowledge-base article on preparing for a customization discovery call before scheduling.

Timelines depend on fit-gap, integrations, data migration, and internal readiness—not a single industry average. Configuring a proven product for a focused workflow may take weeks; phased custom development or multi-system integration often spans months. RadialLeaf scopes work in phases with explicit acceptance criteria so “done” is measurable. Discovery should produce assumptions, exclusions, and a first phase you can validate before expanding.

Yes. Agencies and implementers use RadialLeaf products and services for client delivery—including customization, integrations, and long-term support models agreed per engagement. Clear client ownership after handover is required: who maintains custom code, who opens support tickets, and who approves scope changes. Contact the team with your delivery model and typical client profile.

Approach varies by engagement: hosted SaaS, self-hosted product, or custom build. Baselines include least-privilege access, encrypted transport, secrets not stored in tickets, backup and restore planning, and documented incident response for production systems. Data processing terms are covered in legal policies and contracts where applicable. Share compliance requirements early in discovery so architecture and hosting choices are evaluated realistically.