About Wrkbase: why we built it

Most growing teams end up running one tool for tasks, one for time tracking, one for chat, and one for payroll, each with its own login, its own data, and its own version of the truth. Reconciling them by hand at the end of the month is the actual job nobody signed up for. Wrkbase is one Postgres database and one permission model under twenty modules: tasks, time, chat, calendar, announcements, automations, the AI agent, employees, HR, attendance, shift scheduling, timesheets, leave, payroll, performance, leads, finance, reports, an audit log, and an API, instead of ten vendors and ten exports.

Move a task to "In Progress" and the timer starts on the same row in the same table the payroll export reads from. There's no sync job between a task tool and a time tool because there was never a second tool. Roles are checked server-side against the same record every request touches, not duplicated into a second permissions system that can drift out of sync. When we say "one data model," that's the literal mechanism, not a slogan.

Free is free for up to 5 members, no card on file. That's the whole plan, not a 14-day trial dressed up as free. Team is $8 per member per month, up to 50 members, and adds payroll and the AI agent. Enterprise is $18 per member per month for unlimited scale and dedicated support. Both paid tiers check out for real, no sales call required unless you want a custom deal.

We'd rather list what's not here yet than dress up the gaps: SSO and ready-made third-party integrations don't exist yet for any tier. An API with webhooks does, on Team and Enterprise, and so do custom roles: every plan can create its own roles and set permissions per role. What ships, and when, is tracked on the public changelog, not a highlight reel, the actual commit history.

"AI agent" has become a label people put on chatbots. Ours plans against your real data, lists every action it intends to take before anything happens, executes one step at a time so a single failure can't cascade, and re-checks permissions server-side at execution, not just when the plan was drafted. Every attempt, success or failure, lands in the same immutable audit log a human action would. That's covered in more detail on the security page, with the actual log visible, not just described.

Small, growing teams that have outgrown a spreadsheet and a group chat but aren't ready to pay for, or configure, five separate SaaS subscriptions: agencies, studios, and service businesses where one person often wears the founder, ops, and finance hat at once. If your team is under about 20 people and you're the one reconciling task lists against payroll by hand at month-end, that's the exact gap Wrkbase closes.

It's less of a fit if you already run a mature HRIS or ERP with deep integrations built around it, or if you need on-prem deployment: Wrkbase is hosted, multi-tenant, and opinionated about the workflow, not a toolkit you assemble to match an existing process.

Development happens in the open, one dated entry at a time, on the changelog. Near-term priorities are SSO for larger accounts, and deeper AI agent actions across performance and reporting. None of that is a promise with a date attached: it's the order we're working in, and the changelog is the record of what actually shipped versus what's still a plan.