with the skill
**Diagnosis: A.** The brief is one line with two facts (HRIS integrations, 2 weeks to 2 days). There is no existing voice, product name, proof, or traffic source, so I built the argument from those two facts. Anything I couldn't source is marked `[NEED]` or `[CONFIRM]`.
**Assumptions:** the primary action is booking a demo (typical for HR directors buying at this size), and the traffic is mixed (organic and direct).
---
## Page Copy
### Hero
**Headline**
Onboard new hires in 2 days instead of 2 weeks
**Subhead**
[Product] reads the new hire from your HRIS and starts every onboarding task the moment the hire is entered. It connects to [NEED: named HRIS list, e.g. Workday, ADP, UKG, BambooHR].
**Primary CTA:** See it on your HRIS
**Secondary CTA:** See how it works (anchor link)
**Proof bar:** [NEED: customer logos or "X companies, Y hires onboarded"]
Show the rest (112 more lines)
---
### Problem section
**Heading:** Two weeks is how long it takes when every team waits on the last one
**Body**
The offer is signed and the hire is in your HRIS. Then IT needs a ticket, payroll needs a form, the manager needs a checklist, and someone in HR is chasing all of it by email. Each step is small. The handoffs between them are what take two weeks.
If you run HR for 200 to 2,000 people, you're probably onboarding a few people a week while doing everything else HR does. Every hire you personally chase is time you aren't spending on retention, comp, or the rest of your plan.
*[CONFIRM: that handoff delay is where the 2 weeks goes, using your customer data.]*
---
### How it works
**Heading:** Enter the hire once. The rest starts on its own.
1. **Connect your HRIS.** [Product] links to your existing system. [NEED: typical setup time]
2. **Enter the hire as you do today.** The new hire record triggers onboarding. [CONFIRM: trigger mechanism]
3. **Every team gets its tasks at once.** IT, payroll, facilities, and the hiring manager work in parallel instead of in sequence. [CONFIRM]
4. **Day 2, the hire is ready to work.** [CONFIRM: define what "onboarded" means, e.g. accounts live, paperwork done, equipment shipped]
---
### Benefits
**Works with the HRIS you already have**
Your HRIS stays the source of truth. [Product] connects to [NEED: named list] and reads from it, so nobody re-keys hire data into a second system. Replacing your HRIS is not part of the project.
**Teams work in parallel**
Sequential handoffs are why onboarding runs long. When IT, payroll, and the manager all see their tasks on the first day, the critical path shrinks to the slowest single task. [CONFIRM]
**You see where each hire stands**
Open one view and find which hires are on track and which are waiting on a specific person. [CONFIRM: feature exists]
---
### Integrations section
**Heading:** Connects to every major HRIS
**Body**
Logos and a searchable list of supported systems. For anything not listed, [CONFIRM: custom integration or API option].
[NEED: published integration list. Without it, "every major HRIS" is a claim a skeptical HR director will check on the first call.]
---
### Testimonial slot
[NEED: named quote from an HR leader at a 200 to 2,000 person company, ideally with their before and after onboarding time.]
---
### FAQ
**Which HRIS systems do you integrate with?**
[NEED: list]
**Do we have to replace our HRIS?**
No. [Product] reads from your HRIS and leaves it as the system of record. [CONFIRM]
**How long does setup take?**
[NEED: real timeline and who is involved on our side]
**What does "2 days" include?**
[NEED: definition of onboarded, and whether this is an average, a median, or a typical result]
**Will IT have to build anything?**
[NEED]
---
### Final CTA
**Heading:** Bring us your next start date
**Body:** We'll connect to your HRIS and show you what that hire's first two days look like.
**CTA:** Book a demo
*[CONFIRM: the demo actually works this way. If it doesn't, use "Book a 20-minute demo" with the real length.]*
---
### Meta
**Title:** Employee onboarding automation that connects to your HRIS | [Product]
**Description:** Cut onboarding from 2 weeks to 2 days. [Product] connects to your HRIS and starts every onboarding task when the hire is entered. Book a demo.
---
## Annotations
- **Headline:** It passes the "Now you can" test ("Now you can onboard a new hire in 2 days"). It leads with the quantified outcome because that is your strongest fact. I wrote "instead of" rather than "not" to avoid a contrast-reveal construction.
- **Subhead:** It pairs the mechanism (reads from your HRIS, starts tasks on entry) with the integration differentiator, so the two facts support each other.
- **Problem section:** It names the felt discomfort in the HR director's own workload, which is the first beat of the Human Action Model. The strongest section runs longest on purpose, and the benefits stay short.
- **Integrations:** This is a full section because it is your differentiator and the first objection a buyer will raise.
## Claims I can't fully support yet
1. **"Integrates with all major HRIS systems."** This is stated as you gave it, but a skeptical HR director will ask which ones.
- **Closest supportable version:** name the systems you support.
- **Unlock:** a published integration list, with confirmation of which integrations are native and which are custom.
2. **"2 weeks to 2 days."** I used it as the headline, but it needs a source, and the headline is only as strong as the claim behind it.
- **Closest supportable version:** "Onboard new hires in 2 days" only if that is a real result you can point to.
- **Unlock:** the data behind it (average, median, or best case), the sample size, and a definition of "onboarded." A named customer with a before-and-after would be better still.
## Headline alternatives
- **A (used):** Onboard new hires in 2 days instead of 2 weeks. It is the clearest outcome statement.
- **B:** Your HRIS already has the new hire. Onboarding should start there. It leads with the integration differentiator, which suits HR leaders who are wary of adding another system.
- **C:** New hire entered Monday, fully onboarded by Wednesday. It is more concrete and visual, but it commits to a specific timeline you'd need