Capxul · The work queue · 24 August 2026
The foundation is finished. These are the things we add on top of it, each one a complete thing a person can do. They are grouped by what a customer is trying to achieve, because that is what explains the order.
The useful question is not how long something takes. It is how much of it already exists underneath. Almost everything here is already built below the surface.
The engine works and the screen exists. The two are not connected. This is most of the queue.
The engine works and nothing exposes it. Somebody has to build the way a person reaches it.
The capability itself does not exist yet. The smallest group, and none of it is in the core.
Two pieces start immediately because nothing blocks them. Everything else follows. An arrow means “needs this first”.
Most of these take a couple of days each. They run side by side wherever the arrows allow, so the queue is shorter than the list looks.
Signing up, getting an account, and reaching a dashboard that is honest about what you can do.
Sign up, verify, and get a working account with a wallet behind it, without ever touching crypto.
The system gives a straight answer about your permissions instead of guessing them.
Understanding what you hold, what arrived, and who sent it.
One consistent way to display an amount, what state a payment is in, and which network it sits on.
See every payment in and out, filter it, open one, and download a receipt.
Keep the people you pay, and pay them again without retyping anything.
One person, or the whole team, on demand or on a schedule.
Pay another Capxul user from your dashboard, personally or as an organisation.
Pay the whole team at once, from a saved list, with payslips and a record of every run.
Give somebody — a person or an agent — permission to spend on your behalf, safely and within limits you set.
Pay on a future date, or stream a salary continuously and let someone claim it as it builds up.
The heaviest piece in the queue, because part of it does not exist yet.
Send an invoice, and let a client pay it — including a client with no Capxul account.
See an invoice somebody sent you, and pay or decline it.
Funding an account, and taking money back out.
Set the addresses where money reaches you, and change one safely.
See what the organisation holds, and move money between its own accounts.
Remove somebody, resend an invitation, change what a person may do.
Move money out of Capxul — first to a crypto wallet, later to a bank or mobile money.
Worth being precise, because it is a short list and none of it is in the core.
The connections to banks and mobile-money providers. The part that routes money to them exists; the far-end connections do not.
Same picture. The routing is built, the connections are not.
Personal accounts can already do it. The organisation side needs building.
This exists and works, but in the wrong shape, so it is being rebuilt rather than extended. It does not affect payments between Capxul accounts.
Understood, written down, and deliberately not being worked on. Parked is not cancelled — each has a reason it is waiting.
Needs a decision about who holds a customer's bank details. Not being made while the core is still settling.
Showing value in your own currency, and price movement. The largest parked demand.
Where an organisation's money goes, by category, over a period.
Real counts and alerts. The badges on screen today are fixed numbers.
A dedicated surface for spending limits, beyond what permissions already carry.
Marked “coming soon” in the product direction itself.
Also marked “coming soon”.
A shareable page at your handle that anyone can pay you from.