Lefief Ticketing

The story

Lefief Ticketing is built around one goal: more software value per euro. POs and clients build out their own features with AI agents — they have a feature built and "show" it — while the developer keeps the overview through the dependency graph and only needs to step in at review. That cuts the dev time required, gives the client more value for less cost, and keeps one fixed point of contact with personal guidance. Under the hood is a graph-first ticket system where dependencies are the main view: you instantly see what is pickable and what it unlocks, with AI agents as first-class citizens. From Discord, a PO kicks off a feature with a single /lefief command; the analyst agent delegates to coder and deploy agents that build the product and test it on a dedicated per-branch feature/test environment via MCP, iterating until it works. Only then does it pass the human review gate — the developer corrects in review instead of in endless back-and-forth. A bring-your-own-agent system lets each developer plug in their own agents, repos, custom skills and auth scopes, so every platform fully benefits from specialized agents while keeping human oversight. The result is a hybrid workflow that minimizes communication and makes software value creation sharply competitive on price. Lefief built this in eight weeks as an in-house product, self-hosted on a single service plus Postgres, with prepaid or monthly billing through Stripe and Belgian VAT/Peppol.

Considerations

• A graph instead of a list

  Visualising dependencies shows at a glance what can be done now and what it unlocks, without meetings.

• Pickable tickets + cycle prevention

  A recursive query rejects circular references, so the "what is pickable now" marking is always reliable.

• AI agents as first-class citizens

  Coder, deploy, artifact, analyst and review run per project, gated by role with a human review gate before production.

• Clients build, the dev corrects in review

  POs and clients have a feature built out by agents that build and test it on a dedicated feature/test environment until it works; the developer only steps in at a fail-closed review gate — less dev time, less back-and-forth.

• Show a feature from Discord

  With a single /lefief command the analyst agent steers the project via agent delegations, has it tested on the feature/test environment and streams the result back live, so a PO can show a working feature instead of describing it.

• Bring your own agent

  Developers plug in their own agents, repos, custom skills and auth scopes per project, so every platform runs specialized agents with fine-grained permissions and lasting human oversight.

• Append-only billing ledger

  Every agent run is recorded as an immutable transaction with a cached balance; prepaid via Stripe, VAT and Peppol via Yuki.

• Realtime without an external broker

  Postgres LISTEN/NOTIFY with Server-Sent Events keeps everyone live in sync, without a separate Redis or message queue.

Result

Imagery

Possible extensions

How Lefief Ticketing could grow further.