Ask Claude for a leave tracker, expense claims, a booking log, approvals or a weekly check-in. Haechy puts a working copy online for your team in a minute or two, with sign-in and its own database. Then you ask Claude to change whatever you like.
Five starter apps are ready today. Each one is a small, complete app, not a form builder: you get its full code, so Claude can reshape it later.
People request holiday, sick leave or other leave, for a few days or half a day. Each person sees how much of their yearly allowance is left. You see who else is already off on those dates before you approve, and everyone gets a month calendar of who is away.
Someone photographs a receipt on their phone and submits the claim. You approve or reject it with a note, mark it paid when you have paid it, and download the month as a CSV for your bookkeeper.
Each person answers three short questions and picks a mood once a week. At 8 on Monday morning, a scheduled job emails you last week's answers, with anything blocking listed first.
Bookings is a shared log for things your team shares: a van, a meeting room, a projector. An admin adds each item with where it is and a note, such as where the key lives. Anyone opens an item, sees who has it hour by hour, and books a slot. If the time clashes with another booking, the app says who has it and when, and asks for another time. Two people clicking at the same moment cannot both get it. People can see and cancel their own bookings, and admins can cancel anyone's.
Opening hours are a setting (7:00 to 20:00 to begin with), and the times follow your time zone.
Set up a booking app on Haechy so my team can book the van and the meeting room.
Approvals suits purchases, discounts and anything else that needs a yes. Someone raises a request with a title, details, an optional amount and a needed-by date, and picks who should decide. The approver gets an email with a link, approves or denies (a comment is required to deny), and the requester is emailed back. Either side can comment, and the other is emailed. Every step stays in the request's history, and the requester can withdraw a request that is still waiting.
Nobody can approve their own request, admins included. Admins also see an all-requests list they can filter by status.
Set up an approvals app on Haechy where people send requests to an approver.
Set up a holiday and leave request app for my team on Haechy.Set up an expense claims app for my team on Haechy.Set up a weekly team check-in on Haechy that emails me a summary every Monday.Setting up your own Haechy account includes a one-time mobile number check. See the sign-in and sharing docs for who can open what.
A starter is where you begin. Because Claude has the whole app's code, you change it by asking. Some requests that fit these apps:
Claude changes the code and puts the new version online, and your data stays where it is. If a change goes wrong, ask Claude to put the previous version back.
A starter costs nothing extra. It takes one of your plan's app slots and uses the plan's allowances, like any app.
Say you want a leave tracker for a team of 20 who all sign in. Free allows 2 apps and 5 people who can sign in, so 20 people need Pro: $25 a month, or $250 a year, with room for 5 apps and 25 people. Add expense claims and a weekly check-in for the same team and that is three apps, still inside Pro. Pro also includes 5,000 app emails a month; Free includes 300.
A team of 5 or fewer can run up to two starters on Free. Prices as of November 2026; the pricing page is always current.
Knowing this saves you a wasted afternoon. A starter does not:
Most of these are changes you can ask Claude to make.
If you are checking this for your IT team: a starter is a normal Haechy app, so it runs with the same sign-in and the same limits on outside services as any other. The IT page has the detail, and regions says where an app's data is stored.