Partner scoping
Shape a branded recruiting experience.
If you serve multiple employers, tell us how Apex ATS would fit your service. We can review the workspaces, branding, support and connections your model needs.
A branded rollout is evaluated with Apex. Implementation scope, commercial terms and client responsibilities are confirmed in writing. Custom domains, SSO and payroll or HRIS connections require individual feasibility and provider review.
Scoping areas
Start with what your clients need.
Client workspaces
Review how each employer would use jobs, careers pages, applications and team access.
- Employer-specific workflow
- Data access and responsibilities
- Pilot acceptance checks
Brand requirements
Discuss which public and employer-facing surfaces need your identity and what configuration is feasible.
- Careers page presentation
- Domain and email requirements
- Support ownership
Connection review
Identify integrations and provider permissions before any commitment to a rollout.
- Job board accounts
- Messaging and calendar providers
- Data transfer and security review
Process
From idea to a scoped pilot.
- 01
Describe your model
Share the employers you serve, expected workflows and branding goals.
- 02
Review feasibility
Apex reviews workspace boundaries, provider dependencies and any integration requirements.
- 03
Confirm terms
Both teams agree in writing on scope, responsibilities, tests, timing and pricing before rollout.
Get in touch
Tell us about your clients.
A concise outline of your business model and first employer use case is enough to start the discussion.
- What does private label implementation cost?
- Apex has not approved public implementation tiers or wholesale rates. We review your use case and provide proposed scope and terms in writing.
- Can we use our own brand and domain?
- Branding and domain requirements are reviewed during scoping. The exact surfaces and technical setup must be agreed and verified before launch.
- Can Apex connect to our SSO, HRIS or payroll system?
- These connections are not standard public commitments. Share the systems and required data flow so feasibility, permissions and scope can be evaluated.
- Who supports end clients?
- Support and client ownership are defined in a written agreement for the proposed arrangement.
Contact Apex
Discuss the proposed rollout.
Include the number of employers, the first roles they hire for, branding needs and any systems that would need to connect. We will review what can be scoped.
Email [email protected] Use the contact page