Applications

People Supercube

Hiring, onboarding and the employee record, without the spreadsheet sprawl

PlannedRecruitingOnboardingHR administrationLeave managementPerformanceOffboarding

Planned. This suite is not available to install yet; the tables, agents, apps and connectors below are its design, not a running system.

What it is

In a company without an HR team, people administration happens to whoever is nearest: the office manager runs onboarding from a checklist, the founder reads CVs at midnight, leave lives in a shared calendar, and the review cycle happens the year someone remembers. The employee record is a folder of PDFs and a spreadsheet, and the question "who has completed their safety training" takes an afternoon.

The People Supercube installs a people function with the administration done by agents and the judgement kept by managers. It seeds tables for roles, employees, candidates, applications, interviews, offers, onboarding tasks, leave, reviews, training and documents. It declares agents that write job descriptions from the role profile, screen applications against the criteria the hiring manager set, schedule interviews, assemble offers, run onboarding checklists, administer leave and absence, prepare review cycles and keep the record complete. It publishes the apps people use: the careers pipeline, the new-starter portal, the leave calendar, the review workspace and the employee directory.

After installation, a hiring manager opens a role. The Recruiter agent drafts the job description from the role profile and the brand voice, posts it to the connected job boards on approval, screens each application against the manager's criteria with a short rationale, and offers interview slots from the panel's calendars. The manager decides who to interview and who to hire. The Onboarding Coordinator agent turns the offer into a start plan: contract for signature, equipment ordered through the Operations Supercube, accounts requested, first-week schedule, and a buddy assigned. On day one the new starter's portal knows their name.

Who it is for

Companies of 10 to 500 people without a full HR team, or with one or two HR generalists who spend their time on administration. Roles that use it are hiring managers, whoever owns HR, line managers, every employee for leave and reviews, and the finance manager for payroll inputs.

Agents

AgentRoleOwnsHarness preference
RecruitergeneralJob descriptions, posting, screening, scheduling, candidate communicationClaude Code
Onboarding CoordinatorgeneralOffers to start plans; checklists; accounts and equipment requests; first-month check-insClaude Code, then Hermes
HR AdministratorgeneralThe employee record; leave and absence; contract changes; document expiry; payroll inputsClaude Code
Performance PartnergeneralReview cycles, objective setting, feedback collection, development plansClaude Code, then pi
People AnalystanalystHeadcount, attrition, time to hire, leave patterns, pay equity reportsClaude Code

Data

TablePurposeKey fields
rolesRole profiles: purpose, responsibilities, criteria, pay bandtitle, department, level, criteria, band, reports_to
employeesThe employee recordname, role, manager, start, status, contract_type, location, work_email
employee_privateSensitive fields, separate table with restricted accessemployee, date_of_birth, address, bank, right_to_work, emergency_contact, medical
candidatesPeople who applied or were sourcedname, email, source, consent, status
applicationsOne per candidate per rolecandidate, role, applied_at, screen_score, rationale, stage, decision
interviewsScheduled interviews and feedbackapplication, panel, at, kind, feedback, recommendation
offersOffers made and their statusapplication, salary, start, terms, approver, status, signed_at
onboarding_tasksChecklist items per new starteremployee, task, owner, due, status
leaveLeave and absence requests and balancesemployee, kind, from, to, days, status, approver
reviewsReview cycles and each employee's reviewcycle, employee, objectives, self, manager, rating, plan
trainingTraining assigned and completed, with expiryemployee, course, required, completed_at, expires_at
documentsContracts, policies, certificates, with expiryemployee, kind, file, signed_at, expires_at
payroll_changesChanges to send to payroll each periodemployee, period, change, amount, approved_by
An ordinary Kyoube Data table as it runs today, with its own access levels. The suite's employee record, applications and leave balances would be tables like this one; the suite itself is planned.

Data sources

  • Job boards and applicant tracking. Applications from LinkedIn Jobs, Indeed, or an existing ATS such as Workable or Greenhouse, mirrored if the company already uses one.
  • Email and calendar. Panel availability and interview scheduling through Google Workspace or Microsoft 365; candidate correspondence in a shared recruiting mailbox.
  • HR and payroll systems. If the company runs BambooHR or Personio, the employee record mirrors from there; payroll changes go to Xero Payroll or Gusto.
  • Signature. Signed contracts and policy acknowledgements from DocuSign.
  • Uploads. CVs, certificates, right-to-work documents, existing policies; extracted into the record by the HR Administrator.
  • Other supercubes. Equipment from Operations, cost centres from Finance, capacity planning from General Management.
  • Derived. Screening scores and rationales, leave balances, review summaries, headcount and attrition analytics.

Apps

  • Careers pipeline. Roles and their applications by stage with screening rationale and interview feedback. Used by hiring managers and HR.
  • Interview scheduler. Panel availability and candidate slots; confirmations. Used by HR and panels.
  • New-starter portal. The plan for the first month, documents to sign, people to meet, a place to ask. Used by new starters.
  • Leave calendar. Request, approve, see who is out, balances. Used by everyone.
  • Employee directory. Who does what, reports to whom, where they sit. Used by everyone.
  • My record. An employee's own details, documents and training, editable within policy. Used by everyone.
  • Review workspace. Objectives, self-review, manager review, calibration view. Used by employees and managers during a cycle.
  • People dashboard. Headcount, hiring, attrition, leave, training compliance. Used by leadership and HR; feeds General Management.
Kyoube Apps as they run today: single-file, sandboxed and scoped to whoever is viewing. The suite's careers pipeline, new-starter portal and leave calendar would be published through the same layer; the suite itself is planned.

Connectors

GroupTarget systemsFlows inFlows out
Job boards and ATSLinkedIn Jobs, Indeed, Workable, GreenhouseApplications, candidate detailsJob postings, stage updates, rejections on approval
Calendar and emailGoogle Workspace, Microsoft 365Availability, correspondenceInterview invitations, candidate emails, onboarding schedules
HR systemsBambooHR, PersonioEmployee record, where the external system is the recordChanges on approval
PayrollXero Payroll, GustoPay periods, confirmationsApproved starters, leavers, changes, absence
SignatureDocuSignSigned statusContracts, policy acknowledgements
Identity and equipmentGoogle Workspace, Microsoft 365, via the Operations SupercubeAccount statusAccount and equipment requests
ChatSlack, Microsoft TeamsLeave requests, questionsReminders, welcome messages, review-cycle nudges

Process automations

Role to shortlist Trigger: a hiring manager opens a role. Steps: the Recruiter drafts the job description from the role profile, posts it on approval, screens each application against the criteria with a rationale and a score, and updates the pipeline. Checkpoint: the manager approves the posting and decides who to interview; the agent's score is advice. Output: a shortlist with reasons, candidates informed of their status.

Interview loop Trigger: a candidate is moved to interview. Steps: the Recruiter finds panel availability, offers slots, confirms, sends the panel the CV and the criteria, and collects feedback in the structured form after each interview. Checkpoint: the panel's recommendations; the manager's decision. Output: feedback recorded, decision made, candidate told.

Offer to day one Trigger: a hire decision. Steps: the Onboarding Coordinator assembles the offer within the band, routes it for approval, sends the contract for signature, then builds the start plan: accounts, equipment, first-week schedule, buddy, policy acknowledgements, required training. Checkpoint: the offer approver; the manager confirms the plan. Output: a new starter who has everything on day one.

Leave and absence Trigger: a leave request in the app or in chat. Steps: the HR Administrator checks balance and team cover, routes to the manager, updates the calendar and balance, and sends absence to payroll at period end. Checkpoint: the manager approves. Output: balances correct, payroll correct, team calendar correct.

Review cycle Trigger: routine, per the cycle calendar. Steps: the Performance Partner opens the cycle, collects objectives, sends self-review and manager-review prompts, gathers peer feedback where configured, prepares the calibration view, and drafts development plans from the reviews. Checkpoint: managers write and own their reviews; leadership calibrates. Output: a completed cycle with plans, on time.

Compliance and expiry Trigger: routine, weekly. Steps: the HR Administrator lists training, certificates, right-to-work checks and probation dates expiring within 60 days, reminds the employee and manager, and escalates anything overdue. Checkpoint: none. Output: nothing expires unnoticed.

Offboarding Trigger: a leaving date is recorded. Steps: the HR Administrator builds the leaver checklist: handover, access removal requests to Operations, equipment return, final pay inputs, exit interview scheduling. Checkpoint: the manager confirms; payroll approves final pay. Output: a clean exit and a complete record.

By industry

Professional services firm. Roles map to a career framework with levels; the review cycle feeds promotion decisions and the People Analyst reports utilisation alongside from the Operations Supercube. Recruiting runs through referrals and LinkedIn; professional certifications sit in training with expiry.

Hospitality group. High-volume hourly hiring per venue; the Recruiter screens for availability and right to work first; onboarding includes food safety and licensing training with expiry tracked per site. Rotas stay in the rota system, but absence flows from here to it.

Healthcare provider. Registrations, DBS checks and mandatory training carry strict expiry; the compliance routine is the heart of the supercube. Sensitive records are locked to HR and the registered manager. Agency staff are contractors with a different contract type.

Technology company. Structured interview loops with take-home tasks; offers include equity with an approval chain; onboarding provisions accounts through the identity provider and equipment through Operations. Reviews run on a six-month cycle with peer feedback.

Retail chain. Seasonal hiring waves planned from the General Management calendar; the Recruiter runs group assessment scheduling; store managers see only their store's people and leave.

Non-profit. Volunteers are a contract type with their own onboarding and training; funders' reporting requirements on staffing feed the People Analyst's reports; pay bands are transparent by policy.

Guard rails

  • Sensitive fields live in their own table with access limited to HR roles and the employee themselves; managers and agents other than the HR Administrator never read it. The screening and analytics agents work from the non-sensitive tables.
  • Agents recommend and administer; they do not decide who is hired, promoted, disciplined or dismissed, and their screening rationale is visible so a manager can disagree with it.
  • Screening criteria come from the role profile a person wrote, and the screening score is advice with reasons, never a filter that hides an application.
  • Offers, pay changes and leavers are approved by named people before they reach payroll.
  • Candidate data carries consent and a retention date; the HR Administrator deletes or anonymises when it is due.
  • Every read of a sensitive record is audited with the actor.

Not in the box

  • It is not a payroll system and does not calculate pay, tax or pensions. It sends approved inputs to the payroll provider.
  • It does not give legal advice on employment matters. Policies and templates are the company's own, reviewed by their adviser.
  • It does not make hiring or dismissal decisions and should not be configured to.
  • Rota and shift scheduling stays with a rota system; absence is shared with it.

Other suites

Suites share tables and compose, so the ones next to this one are the ones it works with.

  • Planned

    General Management Supercube

    The operating rhythm of the company, run by agents, owned by the leadership team

    Goals, KPIs, meeting cadence and decisions in one place, with agents that prepare every review and chase every action so leaders spend their time deciding, not collecting.

    • Leadership
    • Strategy
    • Planning
    • Reporting
    • +1 more
    5 industries · 9 target systemsSee what is inside
  • Planned

    Finance Supercube

    Books that close themselves, cash you can see, approvals that stay with people

    Accounts payable, receivable, month-end close, cash forecasting and management reporting run by agents against your own ledger data, with every payment and every journal approved by a person.

    • Accounts payable
    • Accounts receivable
    • Month-end close
    • Cash forecasting
    • +2 more
    6 industries · 12 target systemsSee what is inside
  • Planned

    Sales Supercube

    A pipeline that works itself while your people talk to customers

    Lead qualification, CRM hygiene, quoting, follow-up and forecasting handled by agents in your own customer tables, so salespeople sell and managers see a forecast they can trust.

    • Lead qualification
    • Pipeline management
    • Quoting
    • Account management
    • +1 more
    6 industries · 12 target systemsSee what is inside