Can I vibecode Workelo?
KINDA · weekend projectStrip away the branding and Workelo is a workflow engine: journey templates, tasks with owners and due dates relative to a start date, reminders, and a page the new hire actually sees. That part is genuinely a weekend build, and for a five person company a self-hosted version is fine. What breaks is everything at the edges: HRIS sync, Google Workspace and Slack account provisioning, equipment requests routed to IT, document signing, and the audit trail HR wants when someone leaves. Also worth naming the obvious: this is a tool for coordinating other people, so a personal build only pays off if you are the one running onboarding. If you are, you get most of the value; if you need it to talk to your HRIS, you will spend the weekend on OAuth instead of features.
Build a self-hosted employee onboarding and offboarding tracker. Empty folder, no scaffolding questions, just build it. Stack, non negotiable: Next.js 15 with the App Router and TypeScript, SQLite through Prisma, Tailwind for styling, server actions for all mutations. No external auth provider. No telemetry. No analytics. Data model: - Journey template: name, type (onboarding, crossboarding, offboarding), list of TaskTemplates. - TaskTemplate: title, description (markdown), owner role (manager, hr, it, employee), dayOffset (integer, negative means before the start or exit date), optional link. - Employee: name, personal email, work email, role, manager name, manager email, startDate, exitDate (nullable), status. - Journey: created by applying a template to an employee, snapshots the tasks so later template edits do not rewrite history. - Task: title, description, ownerEmail resolved at launch, dueDate computed from dayOffset plus the anchor date, done flag, completedAt. Features in scope: - CRUD for templates with a drag free ordering (just an integer sort field and up/down buttons). - Launch a journey: pick employee plus template, preview computed due dates, confirm. - Dashboard: all active journeys, percent complete, overdue count, sorted by nearest due date. - Per journey view grouped by week relative to the anchor date, checkboxes that complete tasks via server actions. - A tokenized public task page at /me/[token] so a new hire or manager can see and tick their own tasks without an account. Token is a random 32 char string on the journey, unguessable, no login. - A daily digest script (npm run digest) that finds tasks due or overdue and emails each owner one summary. Use nodemailer with SMTP_HOST, SMTP_USER, SMTP_PASS, MAIL_FROM from .env. If those are unset, print the emails to stdout instead of failing. - Seed script with one realistic onboarding template (about 15 tasks spanning day -7 to day +30) and one offboarding template (about 10 tasks). Explicitly out of scope: HRIS or ATS integrations, Slack or Google Workspace provisioning, e-signature, file uploads, multi tenancy, role based admin permissions. One admin, protected by a single ADMIN_PASSWORD in .env checked in middleware with a cookie. That is enough. Deliver a README with setup, .env.example, prisma migrate command, and a cron line for the digest. Make the /me pages look decent on a phone; that is the only surface an employee ever sees.
$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR
prompt copied. want to know what dies next week?
new verdicts + top votes, weekly. free. one-click out.
HR teams are not buying a task list, they are buying the fact that a start date in the HRIS makes eleven things happen across six systems without anyone remembering to do them. That plumbing is unglamorous, breaks silently, and needs an owner when it does. Add the compliance and audit angle for offboarding, plus the fact that the buyer is usually a two person People team with zero engineering budget, and a self-hosted alternative loses on total cost even when it wins on features.
xHRIS and ATS connectors, so employee records get typed in by hand
xAutomatic account and access provisioning in Google Workspace, Slack, and IT tools, plus the deprovisioning checklist on exit
xE-signature and document collection flows that a legal team will accept
xThe polished employee-facing portal and email design that makes day one feel intentional rather than homemade
xReporting, audit logs, and the GDPR paperwork story your HR lead will ask about
Nothing worth pointing at. That's why the prompt exists.
Can I vibecode Workelo?
Kinda. The core of Workelo is buildable in a weekend with the prompt on this page, but there are real gaps: HRIS and ATS connectors, so employee records get typed in by hand, Automatic account and access provisioning in Google Workspace, Slack, and IT tools, plus the deprovisioning checklist on exit. Read the honest list above before committing.
How much does Workelo cost?
Workelo's pricing is usage-based or varies by plan · No published price anywhere on the site; /en/pricing returns 404, CTAs are "Demander une demo" and free trial.
What do I lose by replacing Workelo?
Honestly: HRIS and ATS connectors, so employee records get typed in by hand; Automatic account and access provisioning in Google Workspace, Slack, and IT tools, plus the deprovisioning checklist on exit; E-signature and document collection flows that a legal team will accept; The polished employee-facing portal and email design that makes day one feel intentional rather than homemade; Reporting, audit logs, and the GDPR paperwork story your HR lead will ask about. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Workelo?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.