You've built structure. You've created checklists, documented processes, made it work - but the tools you're using to hold it together weren't built for this.
}
title="Pay processes are more complex than ever"
body="Endless steps over several days, in strict order, each needing review and sign-off from people outside the team. Keeping it on track falls to one person."
/>
}
title="Manual work with no home for the detail"
body="Payroll still runs by hand: communications, approvals, manual registers. The detail it generates (adjustments, overpayments, exceptions) has nowhere official to live."
/>
}
title="The memory trap"
body="Too much of how payroll runs lives in people's heads. When they're on leave or move on, the knowledge walks out the door with them."
/>
Paytools gives your team the schedule, the controls and the audit trail all in one place to run calm pay cycles, on time, every time.
{/* Row 1: Processing */}
Payroll processing
Pay days that end at 5pm
The whole pay cycle laid out for you. Every task for the main pay run, the ad hoc pays and the clean-up steps, in the order they need to happen, each one owned with deadlines and reminders. A complete record of who did what and when.
Complete real-time visibility means nothing gets missed, leadership never has to chase updates & pay day ends on time.
The state of your payroll operation in one view, not scattered across shared files, inboxes, calendars and people's heads. Obligations, risks, controls and issues, all tracked with owners and due dates.
When it's time to prove it, auditors get view-only access and find everything they need without your team lifting a finger.
When payroll runs across multiple streams and entities, the Head of Payroll needs one view of every team's status, a way to give each sub-team only the work that's theirs, and proof of who did what across the whole operation.
And for smaller teams, it's the same calm, structured process - without the old school spreadsheets and heavy mental load.
);
}
/* ===== WORKS WITH ===== */
function WorksWith() {
return (
{/* Layer diagram */}
The payroll operations layer
Paytools
Run the process. Prove it ran. Point to the evidence.
We don't calculate pay. Paytools runs alongside it — no integration needed.
File storage
Stores your files
SharePoint · Network / UNC drives · Google Drive
Paytools indexes and links your files where they live.
{/* Copy */}
Where Paytools fits
Built for what your payroll system can't do
Paytools runs and governs your payroll activities: task ownership, deadlines, compliance evidence and a complete record of who did what and when. We don't calculate pay, move money or host your files - your payroll system, your bank and your document stores keep doing exactly what they do today.
Plus native Microsoft Teams notifications, so stakeholders stay informed without needing a Paytools login.
);
}
/* ===== RESULTS ===== */
const STATS = [
{ target: 50, suffix: "%", text: "Less manual work when processing a pay run.", org: "ITW Construction" },
{ target: 4, suffix: " wks", text: "For new staff to run a pay run independently (previously 6 months).", org: "Cerebral Palsy Alliance" },
{ target: 10, suffix: "x", text: "Stronger governance practices for non-BAU tasks.", org: "Avivo" },
];
function useCountUp(target, duration = 1400) {
const [value, setValue] = React.useState(0);
const [started, setStarted] = React.useState(false);
const ref = React.useRef(null);
React.useEffect(() => {
const el = ref.current;
if (!el) return;
const obs = new IntersectionObserver(([entry]) => {
if (entry.isIntersecting) { setStarted(true); obs.disconnect(); }
}, { threshold: 0.4 });
obs.observe(el);
return () => obs.disconnect();
}, []);
React.useEffect(() => {
if (!started) return;
const start = performance.now();
let raf;
function tick(now) {
const progress = Math.min((now - start) / duration, 1);
const eased = 1 - Math.pow(1 - progress, 3);
setValue(Math.round(eased * target));
if (progress < 1) raf = requestAnimationFrame(tick);
}
raf = requestAnimationFrame(tick);
return () => cancelAnimationFrame(raf);
}, [started, target, duration]);
return [value, ref];
}
function StatCard({ stat }) {
const [value, ref] = useCountUp(stat.target);
return (
{value}{stat.suffix}
{stat.text}
{stat.org}
);
}
function Results() {
return (
Results from teams using Paytools
{STATS.map(s => )}
);
}
/* ===== FINAL CTA ===== */
function FinalCTA() {
return (
Up and running in a few short weeks
Bring a real process. 60 minutes and we'll show you exactly how it fits and how easy it is to get started.
);
}
/* ===== TESTIMONIALS ===== */
const TESTIMONIALS = [
{ initials:"BK", name:"Beti Kouloumendas", role:"Director of Operations", org:"Carer Solutions", quote:"\"I would strongly recommend Paytools, it's an amazing tool that has added significant value. Plus, it was one of the best implementations that I've ever sat through in my career.\"", link:"/blog/payroll-checklist-carer-soutions/" },
{ initials:"DW", name:"Daniel Watson", role:"Senior Manager, Payroll", org:"Cerebral Palsy Alliance", quote:"\"Before Paytools, we used to have to stay back until 7pm on pay days to complete all tasks. Now we can confidently leave at 5pm knowing everything has been completed accurately.\"", link:"/blog/cpa-payroll-management/" },
{ initials:"NS", name:"Nicole Watson-Spry", role:"Platform Payroll Lead", org:"ITW Construction, APAC", quote:"\"Paytools is a must-have. With features like the shared calendar, centralised registers and obligation library, it's far superior to using Microsoft Office tools and you should absolutely be using it!\"", link:"/blog/payroll-processing-time/" },
{ initials:"GD", name:"Gavin Day", role:"Financial Controller", org:"Avivo", quote:"\"With Paytools, we've been able to streamline two complex pay runs onto one airtight process. Plus, our governance practices are 10x better — especially with non-BAU tasks.\"", link:"/blog/avivo-payroll-operations/" },
{ initials:"MQ", name:"Mel Quinn", role:"Head of HR & Payroll", org:"University of Sydney", quote:"\"Paytools has allowed us to better identify and track our payroll compliance activities. It provides comfort and oversight to management that essential activities are being completed on time.\"", link:"/blog/assurance-into-payroll/" },
{ initials:"CF", name:"Chris Fletcher", role:"Chief Financial Officer", org:"Medical & Aged Care Group", quote:"\"With a new payroll team and a hybrid model, Paytools has been immensely beneficial. We're already experiencing many advantages of the tool, including the ability for anyone to seamlessly step in and complete a pay run.\"" },
];
function Testimonials() {
return (
);
}
/* ===== AI SECTION ===== */
function AISection() {
return (
Designed for what's coming
Ready for AI-assisted payroll?
Agentic AI needs governed workflows, structured data and a complete audit trail to operate safely. Paytools is building that layer (with direct read/write access for AI agents) via a Paytools MCP.
When your organisation moves toward AI-assisted payroll operations, this is an easy and safe way to get started.
John Smith only had a 7-hour break between shifts.
Suggest how I can improve my pay processing checklists.
Turn reviews into outcomes
“Confirm super file totals match” instead of “Review super”.
Duplicate check names
Two checks called “SLP” — rename to “SLP - STD” / “SLP - CHEL”.
Ask Paytools Copilot…
`}}/>
);
}
/* ===== FAQ ===== */
const FAQS = [
{ q:"Is Paytools difficult to set up?",
a:"No. Most teams are live within a few short weeks. We map your existing pay cycle, import your checklists and documented procedures, and configure owners and reminders with you." },
{ q:"Is Paytools a payroll system?",
a:"No, Paytools is a payroll operations platform. Think of your payroll system (like SAP, Workday or Chris21) as the engine that calculates the numbers. Paytools is the cockpit — it's where you manage the team, track the deadlines, document the procedures and house the governance that ensures those calculations are correct. We sit on top of your existing software to manage the 'human' side of the process." },
{ q:"How does Paytools handle our payroll data?",
a:"Paytools stores operational metadata — tasks, owners, deadlines, procedures and evidence — not the pay calculations themselves. Data is encrypted in transit and at rest, hosted in-region for AU/NZ." },
{ q:"What's wrong with using Microsoft Office to manage payroll operations?",
a:"Spreadsheets and shared docs have no ownership, no version history, no audit trail and no reminders. Critical knowledge lives in individuals' heads, and nothing connects the procedure to the task that uses it." },
{ q:"How does Paytools pricing work?",
a:"Pricing scales with the size of your payroll team and the number of pay groups you manage. Book a demo and we'll put together a tailored quote." },
{ q:"Does Paytools integrate with Microsoft Teams?",
a:"Yes — native Microsoft Teams notifications keep stakeholders informed without needing a Paytools login, and reminders land where your team already works." },
];
function FAQ() {
const [open, setOpen] = React.useState(0);
return (
FAQ
Common questions
Everything you need to know about getting set up, staying compliant, and running calmer pay days.
);
}
/* ===== FOOTER ===== */
function Footer() {
// Load HubSpot once wherever the footer renders. The account ID/snippet
// lives solely in /lib/hubspot.js — this just references it.
React.useEffect(() => {
if (document.getElementById("hs-loader")) return;
var s = document.createElement("script");
s.id = "hs-loader";
s.src = "/lib/hubspot.js";
s.defer = true;
document.body.appendChild(s);
}, []);
return (
<>
{/* Google Tag Manager (noscript) — body fallback; ID single-sourced in lib/gtm.js */}
))}