5 apps free for 3 days, no card

Build the AI your people team needs. No business case, no project, no headcount.

The handbook question that gets asked every week, the job description nobody has written, week one for whoever starts on Monday, the policy in the languages your team actually reads, the headcount numbers the board wants — each one an app you build yourself. Pick the job, make a few choices, and it is working this afternoon.

  • No coding
  • No prompt engineering
  • Answers quote the policy
  • Your files stay in your workspace
  • On-premise available

It answers, drafts and summarises. Decisions about people are still made by people.

Click. Click. Done. It is answering by this afternoon.

All the clever AI stuff happens behind the scenes. Nothing to configure, nothing to install, no system to implement, and no prompt to get right — you answer questions about the work, in the words you already use for it.

  1. Step 1

    Start from the job

    Answer policy questions, write the role, build the onboarding, turn the survey into a page, get the headcount numbers out of a spreadsheet. You pick the job; there is no blank page and no template to fill in.

  2. Step 2

    Make a few choices

    How it should sound, how far it may go when it edits, what it is allowed to read. Every step is a choice from a short list. Upload the handbook, the policies and the contracts template once and it works from those.

  3. Step 3

    Use it, and share it

    It opens ready to work. Add a standing instruction once you have seen a few results — always quote the policy, never guess at an entitlement — and share it with the managers so everybody gets the same answer.

The week that disappears into other people's questions

Each of these is one app, built from the same recipes everyone else uses and named for the job it does here. A couple of minutes each, and nothing to write.

  • Handbook Q&A

    Hand it the handbook, the policies and the benefits summaries. Anyone can ask in plain English and get the answer with the paragraph it came from quoted, so nobody is relying on how somebody remembered it in 2023.

    Leave and absenceExpensesNotice periods
  • Role & Letters Desk

    Say what the role is, or what needs announcing, and get the draft in the company's voice — the advert, the role description, the offer, the all-staff note — leaving a marked blank rather than inventing a salary band or a date nobody gave it.

    Job advertsRole descriptionsAnnouncements
  • Week One

    Turns what you already have into onboarding the new starter can actually work through: short lessons, a quiz at the end of each, their place kept between sessions. Built once, and it is the same week one for everybody.

    New startersPolicy refreshersRole handovers
  • Ask HR

    Answers the routine questions from your own policies, in your tone, and hands anything sensitive to a person instead of guessing at it. You read the drafts until you trust it, and it never invents an entitlement.

    Shared inboxManager questionsCommon requests
  • Survey & Exit Digest

    Hundreds of free-text answers in, the themes out, with the comments that made each one quoted underneath. What people actually said, at the length you asked for, rather than what the average of it looked like.

    Engagement surveysExit interviewsConsultations
  • Everyone's Language

    Move a policy, a safety notice or an announcement into the languages your team reads, at the register you chose, with names, figures, dates and structure left exactly where they were.

    PoliciesSafety noticesCompany updates
  • Headcount Dashboard

    Give it the export from your HR system and get a dashboard you can open and put in the board pack. Every number came out of your own data, and it will say the data is too thin rather than fill a gap.

    HeadcountAttritionTime to hire
  • Guidance Watch

    Look a question up properly and get a briefing with its sources attached: what was found, where each part came from, and what the material does not settle. Every page listed with its publisher and date.

    Guidance changesBenchmarksPolicy research
  • Before It Goes Company-Wide

    The last read before something lands in nine hundred inboxes. Mistakes only, a light tidy, or a proper sharpening — you decide at the outset how far it is allowed to go.

    All-staff emailsPolicy updatesIntranet posts
  • Anything else the function does

    Describe the job in your own words and build the app for it. An interview pack from a role description, a return-to-work checklist run against a case note, every question from an all-hands turned into one page — if you can say what goes in and what should come out, it can be built.

    Interview packsChecklistsAll-hands digests

One app can put the question to another

Tick which of your apps a new one may consult. It works out for itself, question by question, whether any of them would help — you never write a rule about when, and every answer names which was asked.

  • Each stays good at one thing

    Your handbook app keeps the policies and the standing instruction to quote them. Your writing app keeps the company's voice. Neither has to become a worse version of the other to cover both jobs.

  • The confidential stays confidential

    Consulting an app is not merging it. Each keeps its own documents, and anyone you share the caller with reaches only the apps they could already open themselves — so the app the managers use cannot read the one holding case files.

  • You can see what was asked

    Every answer shows which app was consulted and the exact question put to it. When an answer about someone's entitlement is repeated back to you, you can trace where it came from.

Honest pricing options that fit all budgets and needs

Pick the plan you’d want and we’ll come to you first when it opens.

  • Free trial

    Free

    See whether this actually works for your problem.

    • Build 5 apps of your own
    • Our sample apps, free and unlimited
    • 3 days to make up your mind
    • Every app type, nothing held back
    • No credit card
  • Individual

    Economical

    $29/month

    One person, with their own apps in daily use.

    • One account, just for you
    • Build up to 40 apps — dozens of jobs, each done properly
    • Around 200 runs a month, across all of them
    • Every app type, at full quality
    • 5 GB of your documents
    • Version history, restore, and email support
  • Teams

    Premium

    $99/month

    Up to five people, sharing everything they build — or one person who wants the lot.

    • Up to 5 people, sharing one pool of work
    • Build up to 200 apps — hundreds of jobs covered
    • Around 1,000 runs a month — 5× Individual
    • Everything in Individual, for everyone
    • 25 GB of your documents
    • Connect your own storage and model keys
  • Corporate

    Let’s talk

    Your documents can't leave your network, and you're buying for a group.

    • Your own storage and your own model endpoint
    • Usage on your provider account, not ours
    • Volume pricing across your teams
    • Single invoice, one agreement
    • A named contact, not a queue

App and run numbers are estimates. Short questions go further, long documents go less far. Change plan or cancel at any time. Your data and the results you produce are yours to keep.

Three jobs, start to finish

The same work, done by one app, two and three. Whichever one you open is the only one you deal with; anything it consults is named alongside the answer.

  • One app

    Most of it looks like this

    First example. A new leave policy goes live and forty people have questions about it. Handbook Q&A, built from the Chat with Documents recipe, works alone — every question is answered somewhere in the policy — and hands back the answer to each with the paragraph it came from quoted underneath.

    One app, two minutes to build, shared with the whole company. The fortieth person gets the same answer as the first.

  • Two apps

    When the announcement has to match the policy

    Second example. You ask for the note telling everyone what is changing about hybrid working from April. Role and Letters Desk, built from the Writer recipe, needs the actual change first, so it consults Handbook Q&A, built from the Chat with Documents recipe, on what is different between the current policy and the April one. It then drafts the announcement, quoting the clause.

    The writing app never had to hold the policies. The handbook app never had to learn the company's voice. Neither got worse at its own job.

  • Three apps

    And when the board wants an answer, not a number

    Third example. The board wants the people section of the pack, covering why attrition is up. Role and Letters Desk, built from the Writer recipe, consults three apps in turn: Headcount Dashboard, on what attrition has done by team and by tenure; Survey and Exit Digest, on what leavers gave as their reason; and Guidance Watch, on published turnover for the sector. It then drafts two pages with every claim naming its source, for a person to check. Each app was called directly, and none of them called any further.

    An evening's work, in the order you would have done it. What to do about it is the part the board is actually asking you for, and that part is still yours.

Questions people ask

Will it screen, score or rank candidates?
No, and this is not a setting you can turn on. The apps summarise, draft and answer from material you give them; none of them ranks people, scores an application or produces a recommendation about an individual. Every decision about hiring, promotion, pay or exit is made by a person, on the evidence, the way it was before — which is the only version of this that is safe for you and fair to them.
Is any of this employment law advice?
No. HundredOne is software you build tools with, not an adviser. An app you build here reads your handbook, your policies and the guidance you gave it and answers with the passage quoted — which is a good way to find out what your own documents say, and no substitute for your solicitor or your employment law helpline when the answer actually matters.
What about personal data and confidential files?
They stay in your workspace, visible to you and to anyone you deliberately share an app with. Answering a question sends the relevant passages to the AI model provider that answers it, and nothing is sold or shared with anyone else. That is the right basis for a handbook and the wrong basis for a grievance file or payroll data — treat an upload the way your own data protection policy treats sending a document to a processor, and if the answer is that it cannot leave your network at all, that is what the Corporate plan is for.
Can it work from our own handbook and contracts?
Yes, and that is what makes an app worth having. Upload the handbook, the policies, the benefits summaries or the templates and the app answers from those, quoting the paragraph each answer came from. It reads PDFs, Word, Excel, PowerPoint, and plain text, Markdown, CSV and JSON. Files are read in your browser, so the original never leaves your computer.
Does it connect to our HR system?
Not as an integration. What it takes is an export — a CSV or a spreadsheet — and what it gives back is a dashboard, a summary or a draft you put where it belongs. Your system of record stays exactly where it is, which also means nothing here can write to it. A deeper deployment is a Corporate plan conversation.
Can the managers and the wider team use the app?
The people you share an app with have to be in your workspace, on the seats your plan carries: Teams is $99 a month for up to 5 people sharing everything they build, which covers a people team and its managers. A whole company on one handbook app is a bigger number of seats and a conversation about the Corporate plan, not a checkbox — and we would rather say so here than after you have announced it. Individual is $29 a month, and before either there is a free trial: 5 apps for 3 days, no credit card.
Will it invent an entitlement or a policy that does not exist?
The apps answer from the material you give them and quote the passage each answer came from, so an answer with nothing behind it is visible rather than plausible. The writing apps leave a marked blank rather than inventing a figure they were not given. None of that removes the check: these are drafts and first answers, meant to be read by someone who would notice.
Do I need to know anything technical?
No. You pick the job you want done and answer a few questions, each one a choice from a short list described in terms of the work rather than of settings. We choose the AI model, write the instructions and handle the retrieval underneath. There is nothing to code, nothing to configure and nothing to install.

Build the AI this afternoon. The people part is still yours.

Build 5 apps, use them for 3 days, no credit card required.If they aren’t useful, you’ve lost a few minutes.If they are, the forty questions are answered and Monday's starter has a week one.