eJobSiteSoftware White-Label Portal Launch (Onboarding)

eJobSiteSoftware White-Label Portal Launch (Onboarding)

1. 01

   Confirm the $600 one-time Job Board Software purchase and pull the full source code plus branded Android/iOS app source into the agency's repo before any client work starts.

   The $600 USD fee covers the complete Enterprise Job Board application with ATS, 10 built-in themes, and no monthly fees, so the license is a fixed cost the agency can amortize across multiple client portals.

2. 02

   Install the platform on client-provided hosting and apply the first-year free hosting entitlement to avoid double-billing the client for infrastructure.

   Free first-year hosting is included in the purchase, so map the client's domain to the vendor-hosted instance during year one and document the migration path to self-hosted before renewal.

3. 03

   Open the admin dashboard and select one of the 10 built-in themes, then swap in the client's logo, color tokens, and portal name.

   Theme selection is a one-time configuration in the admin panel; changing themes after employer accounts are live forces re-testing of every registration and posting flow.

4. 04

   Connect Stripe or PayPal in the integrated e-commerce settings so employers can pay for job postings without manual invoicing.

   The platform ships with integrated e-commerce for both processors; pick one per client to keep reconciliation simple, and test a live $1 posting before handing the portal over.

5. 05

   Enable Google, Facebook, and LinkedIn social logins for both the job seeker module and the employer module.

   Social login reduces candidate drop-off at registration; verify each provider's redirect URI against the client's production domain, not the staging URL.

6. 06

   Configure the XML job backfill feed and map the client's target sources so the portal has listings on day one.

   XML backfill populates the board before the client's own employers post; set the refresh interval and confirm parsed fields (title, location, salary) land in the correct schema slots.

7. 07

   Run a sample employer and candidate through the ATS pipeline end to end, including AI resume parsing and resume-to-job matching.

   Create one test employer, post one role, upload one resume, and confirm the AI matching ranks the candidate against the open role before the client sees the portal.

8. 08

   Document admin procedures and hand the client a one-page runbook covering employer approval, posting moderation, and payment reconciliation.

   The runbook is the deliverable that converts a one-time build into a monthly retainer for portal management, theme updates, and backfill monitoring.