OwlRole
A work-management tool for small teams that rely on contractors: tasks, daily check-ins, timesheets, hiring and invoices in one place, with each person's real name kept private from coworkers.
- 27
- named permissions behind every action
- 26
- tools an AI assistant can use, under its user's permissions
- 88
- database tables across tracking, time, hiring and billing
The problem
Teams that work with freelancers end up with tasks in one tool, hours in a spreadsheet, hiring in email and invoices in a folder. Owners can't see where work stands or what it costs without chasing people, and contractors' personal details get passed around more widely than they should.
What it does
OwlRole gives a team one place to hand out work, watch it move and see what it costs. There's an issue tracker with boards, cycles, saved views and an intake queue, project docs and a wiki, and a daily check-in where each person writes what they did, linked to the tasks it was for.
The money side is built in. People log their hours, leads approve them, and invoices are generated from the approved hours. Hiring lives here too: post a job, collect applications, move candidates through stages, keep a talent pool, and bring the hire straight into a project.
It connects to the tools teams already use, including GitHub, GitLab, Jira, Linear and Slack, and it has a built-in server that lets AI assistants read and file issues under exactly the same permissions as the person they act for. There's also a public feedback portal where customers can post and vote on ideas.
Key features
Names stay private
Contractors appear to coworkers under a handle, and each viewer can add their own private nickname, so real names don't spread beyond the people who need them.
Check-ins tied to tasks
A short daily note linked to the work replaces the status meeting, and an owner can read what happened in minutes.
Timesheets to invoices
Approved hours become an invoice directly, so nobody retypes hours or argues about what was billed.
Hiring pipeline
Jobs, applications, stages and a talent pool replace hiring by email, and the new hire joins a project without setting up anything again.
Plans that show their health
Cycles show what the team is doing now, and initiatives show whether bigger work will land by its date.
Ready for AI assistants
An assistant such as Claude can file and update issues through OwlRole's own sign-in, never with more power than its user.
Where it stands
A young product, first built in August 2026, that runs the studio's own teams day to day. There are no public customer or usage figures yet.
Under the hood: for the technically-minded
How it's built
One function decides how every person appears to every other person. Pages only ever receive a handle or the viewer's own nickname, so a bug on a screen can't leak a name it was never sent, and revealing a real name is a separate, admin-only action.
One function decides what anyone may do. Permissions are a fixed list of named capabilities mapped to roles, with project leads gaining extra powers only on their own projects. The AI server reuses the same checks and the same code the app uses for every change, so validation, audit and notifications apply to an assistant's actions too.
Sign-in has no passwords: Google, a passkey or an emailed link. For AI assistants, OwlRole runs its own OAuth 2.1 server with PKCE and rotating tokens, and third-party tokens are stored encrypted.
The hard problems
Privacy across imported data
Names also arrive from GitHub, Jira, Linear and Slack. External people go through the same identity layer: people mapped to a member are shown like members, and everyone else is scrubbed.
Letting AI act without extra power
An assistant must never do more than its user could. Tokens are scoped to read or write at consent and stored hashed, sign-in codes are single-use, and every tool runs the same permission check as the app.
Server code out of the browser
Shared rules, such as which capabilities exist and how plan health is scored, live in small client-safe modules, while anything touching the database stays in server-only files that can't be bundled into a page.
Built with
- React Router 7
- TypeScript
- PostgreSQL (Drizzle)
- Redis
- WebAuthn / passkeys
Building something in this space?
Work with us →