Deleg8
Tickets, your team and a client portal

Hand the work out.
Get it back done.

Write what needs doing as a ticket. Someone on your team takes it, does it, and closes it with proof. Your clients’ users send requests through their own portal and read only what you choose to publish. It runs on its own: your accounts, your database, your server.

T-41Rate limits on /uploaddoneSam · closed with a summary
T-42Phone layout for the file listworkingAna is on it
T-43Write the restore runbookopenDone when: a fresh box restores from last night’s backup
T-44Drop the old v0 routesopenPriority 4

Everything on one list

Deleg8 is small on purpose: boards of tickets, the people who work them, and the clients who ask for them.

Lists and tickets

Add tickets one at a time or paste a whole list. Give each one a priority, labels, a place to work, and what “done” means. Add your own fields: text, a number, a date, yes or no, or a dropdown.

Your team does the work

Assign a ticket to a person, or let anyone on the board take the next one. It is closed with what was done, and every step is on the ticket’s timeline. Break a big ticket into sub-tickets and link related ones.

A portal for your clients

Make a Client for each company you work for and invite its users. They send requests and read the updates you publish. Your internal notes and working stay private. They never see them.

Your team, your rules

Invite your team by email as an admin or a member, and share a board as Manager, Can work or Can view. Everyone sees the same board, live, on a phone or a desktop. An API, API keys and webhooks connect the rest of your tools.

How it works

1

Write it down

Say what needs doing and what done means. Share the list with the people who need it, or invite a client’s users to send requests into it.

2

Someone takes it

A person on the board takes the ticket, or you assign it. A script with a work token can claim one too; if it stops, the ticket goes back on the list.

3

Done means proof

The ticket is closed with a summary of what was done. You write the update, and the client reads that and nothing else.

The client portal

Your clients see a clean page. Not your workshop.

Each user signs in with their own email and password and sees one thing: their client’s requests. They write a request, you work it, and when you have news you publish an update in plain words.

  • Invite-only. There is no open sign-up.
  • You see a client’s request on your board like any other ticket.
  • Your internal notes and working are never sent to them.
  • They reply, and you see it marked “From” the client’s name.
You see

T-57 The logo is blurry on invoices

Internal note Their printer is the problem, not the file.

Assigned Sam, working

They see

The logo is blurry on invoices In progress

Update from you We have a sharper file and will send it on Friday.

What works today

Ready

  • Lists and tickets, with priorities, labels, places and “done when”
  • Your own fields on a list, to fill in, filter and sort by
  • Sharing by email as Manager, Can work or Can view
  • Sub-tickets and related tickets
  • Your team: owner, admins and members, with an audit log
  • The client portal: requests, photos, published updates, replies, each client on its own address
  • Your own objects and fields, shown to clients only as you choose
  • An API with keys and scopes, and signed webhooks
  • The web app on a phone or a desktop, installable, with notifications
  • Its own accounts: email and password, no other service needed

Text that looks like a password or a key is never stored on a ticket.