Does the app run payroll?

No. Payroll, employer contributions and government filings stay with your accountant or payroll provider. What the app delivers is an organised month's close, with hours worked, overtime, absences, holidays and sick notes for each employee, exported to a spreadsheet for whoever runs payroll.

Can I stop staff clocking in from home?

The app can record the location at every clock-in and flag on the timesheet the ones made far from the site. Blocking clock-ins outside a set radius is also possible, and worth asking for in the description. Location depends on the phone's permission, and the app asks for it at the right moment.

What about data protection for employee records?

The data sits in your app's database, and who sees what is decided there: employees see only their own file and timesheet, supervisors see their team and only HR sees salaries and documents. Sick notes are health data, which data protection law such as GDPR treats as sensitive, so restrict them to HR from the description onwards.

Use cases

HR and employee time tracking app

Employee records, clock in and out from the phone with location, time off balances, holidays, sick notes and shift schedules, in an app your staff actually use.

HR at a small company is made of loose paper: the timesheet signed at the end of the month, the sick note sent as a photo in a chat and the holiday request agreed in passing. Each of these becomes a problem when it goes missing, and it nearly always goes missing when payroll is being closed. In an app, the employee clocks in, sends the sick note and requests holiday from their phone, and you approve it on one screen, with everything stored with a date.

Build this app free See the templates

People reach this page looking for

HR software for small business
employee time clock app
clock in and out app for employees
employee management and leave tracking app

What gets built

Four things you could have working this week

Not a feature list. These are the apps people actually describe, and what the platform hands back when they do.

01

Clocking in from the phone with location

Start, end and breaks recorded with the server's time and the location at that moment, for staff who work on the road or across several sites. Employees see their own timesheet for the month.

02

Overtime balance and corrections with approval

Overtime and absences add up in a time balance. Forgot to clock in? The employee requests a correction with a reason, and it only counts once you approve it.

03

Holidays, sick notes and absences

Holiday requests with dates, sick notes sent with a photo and authorised absences, each pending, approved or declined, and a team calendar showing who is away.

04

Employee file and documents

Personal details, job title, salary, start date and attached documents, visible only to HR. Employees see and update only their own contact details.

Included

The parts nobody wants to build twice

Database, login, payments and publishing are part of the platform, not a list of services you go and wire up afterwards.

A real database, not a form dump

Every screen reads and writes models you can open, query and export. The data is a database of yours from the first minute, not a spreadsheet the app pretends to read.

Login for your own users

Email, magic link and Google sign-in, with roles and per-record ownership enforced by Postgres itself. A badly written screen cannot become a leak, because the database answers empty.

Payments that land in your account

Stripe, Pagar.me and Mercado Pago connect once. Card, Pix, boleto and subscriptions, with the card fields rendered by a hosted vault your app never touches.

Web, installable, and in the stores

One project published three ways: your own domain, an icon on the phone straight from the browser, and a signed binary submitted under your own store account.

Found in search, and by the models

Titles, metadata, sitemap, structured data and social images are generated with the app. Pages get found instead of only being linked.

React code you can take with you

Real React, edited line by line or by clicking the element on screen, exported as a ZIP or pushed to your GitHub. No lock-in you have to negotiate your way out of.

How it works

From a paragraph to a published app

Three steps, and the second one is the one people do not believe until they watch it.

Describe it in plain language

Say what the app does and what it has to remember. No diagram, no schema, no naming a single framework.

Watch it get built

Screens, data models, login and payments appear while you read. Anything you do not like, you say so and it changes.

Publish, then keep changing it

Live on your domain in seconds, with version history behind you. Tuesday's conversation is Tuesday's release.

Start here

A prompt you can paste right now

This is a complete first message, not a slogan. Paste it, change the nouns to yours, and you have an app to react to instead of a blank page.

Build an HR system for a commercial cleaning company with thirty employees spread across several client sites. Employees with personal details, job title, salary, start date, site and attached documents; work sites with an address; each employee's schedule by weekday and site; clocking in and out from the phone with start, end and breaks, recording the server's time and the location at that moment; a monthly timesheet the employee can see; a time balance adding up overtime and absences; timesheet correction requests with a reason, approved or declined by the supervisor; holiday requests with dates and sick notes sent with a photo, both with approval; a team calendar showing who is on holiday or off sick; a noticeboard; three roles: employee, who sees only their own data, supervisor, who approves their own team, and HR, who sees everything and exports the month's close to a spreadsheet for the payroll provider; and a dashboard only I can see, with who is in today per site, the week's late arrivals, the month's overtime and holiday allowances about to expire.

Ready to start from

Templates in this category

A template is a working app with data already in it. Open one, make it yours, publish it under your own account.

Lexara

HR & Legal

A drafting room for legal work: nine assistants, each carrying its own jurisdiction layer.

12 screens

Questions

Frequently asked questions

That depends on how you use it. Labour law in many countries sets specific requirements for electronic time-keeping, such as receipts for the employee or records in a prescribed format, so check with your accountant or employment lawyer. The app records time with the server's clock and the location, and it is a good internal control. Do not treat it as a certified legal timeclock.

Keep looking

Other things people build here

Most apps end up sitting between two categories. Nothing stops you from asking for both in the same paragraph.

Describe it. See it running. Publish it to the store.

Free to start, no credit card. You subscribe when you want your own domain without the badge or your app in the stores, and on the Builder plan you take the code with you if you ever want to.

Build this app free Use cases